How can dashboards and reports share equipment data?

When energy figures on a dashboard differ from a month-end report, managers need to trace the discrepancy. Items to check include period boundaries, equipment scope, missing-data rules, and records received after the report was generated.

Sharing equipment data also requires shared metric definitions and calculations. Live views and period documents can present information differently while keeping their figures traceable.

Define each metric consistently

The same metric name can conceal different scopes. Define its equipment, unit, period, time zone, and calculation method. Assign responsibility for approving rule changes.

Metric type	Definition to share
Current power	Measurement point, direction, unit, and last valid time
Period energy consumption	Start and end times, meter differences or integration method, and gap handling
Alert count	Events or notifications counted, cross-period events, and duplicate handling
Work-order status	State definitions, closeout conditions, and statistical cutoff

One source can support several metrics, each with its own calculation. Depending on the available data, period energy can use meter differences or integrate power over time. Define sampling and averaging separately for average power. See the shared equipment data model guide for measurement meanings and units.

Share calculations and preserve query conditions

A data service can provide agreed metrics and query parameters to both dashboards and reports. Users select equipment and periods for a view; exports carry those selections into the document.

Record the equipment scope, reporting period, generation time, and rule version. Disputed figures can then be queried under the same conditions. Preserve source links and transformations where metrics need detailed traceability. The W3C PROV Primer describes data derivation and revision relationships that can inform this design.

Distinguish view updates from report cutoffs

A live view generally reflects recently received data. A period report uses a defined cutoff. Late records may require a revised report, so decide whether an output is a fixed snapshot or a version that can be regenerated.

A snapshot preserves the inputs and results used at generation time. A revision records its time, reason, and differences. Show data update times on the dashboard so readers can compare them with the report cutoff.

Handle missing and backfilled values consistently

Separate missing intervals, communication failures, and valid zero readings. Where estimation is needed, define its method and mark estimated intervals in both outputs.

Assign backfilled records to their original measurement periods and detect duplicates using agreed rules. If new records change an issued report, make the revision visible. Meter resets and equipment replacements also need explicit handling rules.

Reconcile one metric from view to document

Choose a regularly used metric and fix the equipment, period, and data cutoff. Compare the data query, dashboard, and export. Test day boundaries, gaps, duplicates, and backfills as well as normal records. Each difference should be explainable through the defined rules.

Expand to other metrics after this path works. See the Modbus, MQTT, and API integration guide for data connections and the inspection digitization guide for documents derived from field records.

lvsota’s equipment and data integration service supports dashboards, alerts, and reports. Bring current views, sample reports, and metrics to reconcile to discuss shared data and output needs.