Use case: data health # Know when plant data stops, before someone reads a wrong number Aditum Data opens an incident and emails the owners when a run fails, a source goes stale, a tag stops reporting or stops changing, a scheduled run is missed, data arrives but isn't stored, or an edge connector goes offline. Facts checked 24 October 2026 ## Which data problems are detected? Failed runs, stale sources, silent and stuck tags, renamed tags, missed schedules, data received but not stored, and offline connectors. - A tag whose value stops changing opens a "tag stuck" incident; a state tag held at a valid state is not called stuck. - When a tag is renamed at the source, the run reports it with the likely new name. - A connector that sends heartbeats but no data shows amber as "Heartbeats only", never green. - An edge connector shows as offline 3 minutes after its last heartbeat, and an alert opens within ten minutes. - A connector clock that is off by more than 30 seconds is reported on the connector card. ## Are the success counts honest? Yes: a run counts as successful only for the rows the destination actually accepted. Refused rows fail the run with the reason. Data checks (not empty, within a range, unique, allowed values, minimum rows) can stop a bad write before it lands. ## Where do alerts go? Email, email lists, Microsoft Teams, Slack, signed webhooks, PagerDuty and Opsgenie. - One cause gives one email: when a stopped connector makes several things stale, people get one email for the cause. - Threshold and "no data" rules can be set on one tag, or on every piece of equipment of one type. - Planned maintenance windows silence notifications; incidents can be snoozed, and unacknowledged incidents escalate after 30 minutes (adjustable). - Acknowledging in Aditum acknowledges the page in PagerDuty or Opsgenie. ## Questions **Do we have to set up rules before anything is detected?** No. Failed runs, stale sources, silent tags and offline connectors are checked without any rule. Threshold rules are added on top where you want them. ## Read next - [ConnectorsWhich plant and business systems Aditum Data reads and writes: OPC UA, MQTT and Sparkplug B, Modbus TCP, AVEVA PI, GE Proficy, SQL databases, InfluxDB, Kafka, S3, SAP OData and REST.](https://aditumdata.com/connectors) - [Aditum Data vs a DIY stackNode-RED, Telegraf, InfluxDB and Grafana are free and flexible if you have developers. Aditum Data gives plant teams the same path without code, plus data health and cross-site KPIs. Sourced comparison.](https://aditumdata.com/compare/node-red-telegraf) - [Aditum Data vs Kepware + a historianKepware Server (formerly KEPServerEX) connects PLCs; a historian stores the data. Aditum Data reads Kepware over OPC UA and adds pipelines, calculations, alerts and dashboards. Sourced comparison.](https://aditumdata.com/compare/kepware-historian) ## Discuss architecture with an industrial data specialist. Source compatibility, security boundaries, deployment and multi-site operation. Or request a 45-minute technical session to select one KPI and three sites and draft the acceptance criteria. [Book a technical demo](https://aditumdata.com/#contact)[sales@aditumdata.com](mailto:sales@aditumdata.com)