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
- Features
- Metric reconciliation
Metric reconciliation
Calculate reviewed results from eligible readings and keep the original result when a source changes.
OverviewMetric results to inspect×
IoT Data Analytics · Metric reconciliation
New
Metric results to inspect
Metric results
| Metric | Period start | Period end | Value | Status | Reason | |
|---|---|---|---|---|---|---|
| MD-5756 | 19 Oct | 22 Oct | 330 | Suppressed | Suppressed mr-366 | |
| MD-2963 | 09 Oct | 11 Oct | 830 | Invalid | Invalid mr-529 | |
| MD-8932 | 11 Oct | 20 Oct | 370 | Suppressed | Suppressed mr-496 | |
| MD-9358 | 26 Oct | 04 Nov | 880 | Invalid | Invalid mr-306 | |
| MD-4846 | 09 Oct | 13 Oct | 830 | Suppressed | Suppressed mr-488 |
6 of 6 records
Suppressed mr-366Metric results · MR-25158
SuppressedMetricMD-5756
Period start19 Oct
Period end22 Oct
Value330
RunOR-67700
What you can do
Calculate and reconcile a metric
The Measurement Steward maintains metric definitions with a grain, numerator and denominator expressions, aggregation method, unit and version. The Operations Analyst uses an approved definition and the eligible readings for one source. The manual reconciliation workflow computes the observed conversion rate, protects a zero denominator and stores a result linked to its operation run.
How the work is organized
- Rule. The Measurement Steward maintains the approved definition, grain and version.
- Scope. The Operations Analyst selects eligible readings for the source and period.
- Result. The calculation stores its numerator, denominator, status and linked run.
The run connects the calculation to an input hash and source revision. The Operations Analyst can compare the earlier and successor results by period, definition version and included reading scope. That trail explains a changed number on the operational overview. The Measurement Steward checks that the approved rule and aggregation method still fit the source; the analyst keeps each saved result with its own run.
What to agree during setup
Agree which approved definition applies to a stream and time window. Record how eligible readings are selected and what a zero denominator means for the result status. The team should decide how a corrected source revision is compared with the earlier persisted result.
Rehearse the same period with eligible readings and then with a zero denominator. The Operations Analyst checks which readings entered the scope and whether the saved status and reason explain the result. The Measurement Steward checks the definition version used for that period.
Check the handoff on an actual case
For a stream with accepted observations in a coverage window, the analyst checks the approved definition and the included reading scope. The calculation records numerator, denominator, value and source row count. If the denominator is zero, the result must explain its outcome without presenting an ordinary rate. A later correction gets a successor source revision and a new run; the original result remains available.
After a correction, the Operations Analyst runs reconciliation again and locates both results. Compare their source revisions, run identities, periods and source row counts. Neither result should silently replace the other.
What your team sees
- Metric results to inspect — Results needing attention, with their reason and source run.
- Approved metric definitions — Metric rules with grain, version and aggregation method.
Follow the work through
See the related process for the handoff and the data model for the connected records.
What it keeps track of
Data model- Metric definitions
- Approved metric definitions with grain, expressions and aggregation method.
- Metric results
- Calculated metric results persisted once per approved definition and window.
- Sensor readings
- Consented observation-level session and conversion event facts.
- Sensor streams
- Measured web properties with lifecycle status and observed outcome fields.
- Operation runs
- Workflow execution runs with frozen revision, input hash and result identity.
Who uses it
Permissions- Measurement Steward
- , Operations Analyst, Independent Reviewer.
Set up IoT Data Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.