Application guide · 13 September 2026. Illustrative project guidance; verify device, version and license compatibility separately.
Define the measurement boundary
Which line or utility does each meter cover? If several processes share a supply, assigning all consumption to one product may mislead. Record physical scope, unit and measurement type. Distinguish cumulative energy readings from instantaneous power values and make that distinction visible in the reporting model.
Align the timelines
Process production counts, shift boundaries and meter data using an agreed time-zone convention. Keep measurement time separate from receipt time. Decide whether late arrivals can revise a completed shift report. Clock synchronization problems can associate consumption with the wrong production interval.
Handle resets and missing readings
A negative difference between cumulative readings may indicate a reset, rollover or replacement rather than negative consumption. Verify meter behavior against its documentation. Do not replace missing samples with zero consumption. Distinguish estimated values from measurements and expose coverage in the report.
Use the data for a defensible decision
Consumption per unit requires the numerator and denominator to cover the same line, period and production scope. Reconcile one pilot shift against field readings and production reports. Evaluate Kepware for device access and OPC Router for integration workflows. Demonstrate savings with measured project data; connectivity software alone does not promise a saving percentage.
Review with your team
- Meter scope and units recorded.
- Shift and time-zone conventions aligned.
- Reset and missing-data rules defined.
- Pilot shift records reconciled.
