Match the data to the decision
Historical energy analysis, asset scheduling and real-time operating decisions do not necessarily need the same measurements or reporting interval. Define the decision first, then agree the input data and how fresh it needs to be.
Avoid choosing a design from a headline sampling rate. Measurement acquisition, reporting interval, transport latency and arrival at the receiving system are different stages. Verify the complete path under the intended operating conditions.
Establish the measurement boundaries
For a site with generation, storage and loads, distinguish the site total from each asset's contribution. Record where each meter sits and agree units, timestamps and power-direction conventions.
The ZEM family provides electricity monitoring; its current datasheet and configuration determine the available measurements. Review the ZDR family when demand-response monitoring or control functions are needed.
Supported equipment telemetry can add operating state and other asset-specific information. Confirm the interface and mapping for the actual equipment rather than assuming external metering reveals every internal state.
Use Edge locally and connect the required service
Edge runs on the Gateway and provides dashboards, data exploration, calculated readings and local automation. It is not limited to forwarding raw readings.
Use a pre-built or partner-built integration flow to supply the external service with the required data. Confirm its endpoint, authentication, schema and delivery behaviour. Generic protocol support is a starting point, not proof of a completed integration.
The partner service remains responsible for its optimisation model, commercial decisions and any market-facing processes. Installing monitoring hardware does not itself establish market access or settlement eligibility.
Preserve data quality through the handoff
Document accumulated versus interval energy values, missing-data handling and any transformations. Keep original readings distinguishable from estimates or calculated values. Agree what the receiving service should do with delayed, duplicated or out-of-order messages.
Compare a representative sample at the source and destination before increasing volume. Measure delivery delay separately from the sensor's reporting interval, and establish an owner for failed delivery or unexplained differences.
Treat control as a separate qualification
If the service issues asset commands, define permitted actions, limits, acknowledgement, local overrides and communication-failure behaviour. Verify the resulting physical action as well as the software response.
For the wider design, read the VPP integration guide and battery storage guide. Bring the asset list, decision requirements and existing platform to a project discussion.