These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- IoT Data Analytics
- Who it's for
- Device operations
Device operations
Device operations teams can compare device count, session count and accepted readings for a measured source. The collection basis explains how those quantities were gathered. The Stream Owner identifies the source; the Operations Analyst checks reading outcomes and the calculation scope before a metric result is used.
How IoT Data Analytics is set up for you
Keep identity stable
Retain the source record identity and each reading's source reference when data arrives from the measurement system.
Check the scope
Separate pending and rejected readings from the eligible observations used by reconciliation.
Explain the result
Link the calculated value to its approved definition, source window and operation run.
Device operations teams can compare device count, session count and accepted readings for a measured source. The collection basis explains how those quantities were gathered. The Stream Owner identifies the source; the Operations Analyst checks reading outcomes and the calculation scope before a metric result is used.
Start with one device stream and readings for a known period. The Stream Owner confirms the definition, source identity and collection basis. The Operations Analyst registers a reading, repeats its operation key and checks that the existing run is reused. They then mark outcomes and inspect the validated transition in state history.
Use an approved metric definition to reconcile eligible readings. Compare the result's numerator, denominator, source row count and status with the run. Also rehearse a zero denominator: the saved result needs a reason instead of an ordinary rate. If an input is corrected, calculate against the successor source revision while retaining the earlier result.
An anomaly outside the stream bounds gets its own review and read-back. When a reviewer decision is required, the Independent Reviewer decides on the exact revision and checks evidence. See [implementation](/iot-data-analytics/implementation) for a pilot sequence and [integrations](/iot-data-analytics/integrations) for source mapping.
Features to start with
Roles on the team
- Stream Owner
- Owns source configuration and the collection cycle for assigned streams.
- Operations Analyst
- Validates readings, investigates anomaly outcomes and reconciles metrics.
- Independent Reviewer
- Decides source-revision reviews and checks supporting evidence.
- Follow-up Owner
- Works assigned corrective actions to a recorded resolution.
- Measurement Steward
- Maintains definitions, source mappings and approved metric rules.
Set up IoT Data Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.