Measured energy data for carbon reporting

Give the reporting team a clear record of what was measured, where and when. EpiSensor supplies site measurements and local tools; carbon accounting needs its own boundaries, methods and supporting evidence.

Separate energy measurement from emissions accounting

An electricity reading is activity data, not a complete carbon footprint. Reporting teams must also establish the inventory boundary, appropriate calculation method and emissions factors. Metering does not replace those decisions or the other records they require.

The GHG Protocol Scope 2 Guidance addresses accounting for purchased electricity, steam, heat and cooling. Use the applicable guidance and your reporting team's requirements; this guide does not certify a reporting method or promise compliance.

Define the measurement boundary

List the facilities, meters and energy uses relevant to the reporting workflow. Record which points are site totals, submeters or generation measurements so the receiving system does not double-count consumption.

For new measurements, review the hardware range. The ZEM family covers electricity monitoring, while ZPC pulse counting may be appropriate for compatible pulse-output meters. Confirm the source meter, pulse meaning, units and installation requirements before configuring a conversion.

Preserve context and traceability

Keep a stable identity for each meter and a record of its location and purpose. Agree timestamps, reporting intervals and whether energy readings are cumulative or interval quantities.

Document changes such as meter replacement, reset or a revised scaling factor. Identify missing data and estimates explicitly rather than silently replacing them with zero. The reporting team should be able to distinguish source readings from later calculations and adjustments.

Use Edge operationally as well as for delivery

Edge provides local dashboards, data exploration, calculated readings and automation on the Gateway. Site teams can use those tools to understand consumption while the reporting workflow uses the relevant data externally.

Choose a pre-built or partner-built integration flow for the receiving service. Agree the authentication, format, units, interval boundaries and delivery schedule. A platform accepting a CSV file still needs the correct columns, point mapping and import configuration.

Reconcile before relying on the feed

Compare a representative period with the source records using the same measurement boundary. Explain differences caused by interval alignment, missing readings or other known adjustments. Retain the information the reporting team needs to repeat that comparison.

Assign responsibility for source configuration, delivery failures and receiving-system changes. A successful import alone is not an audit opinion or evidence that every required disclosure is complete.

See the energy-management integration guide and reporting and BI guide, or discuss your data requirements.