Define the boundary of the project
A customer-site monitoring project is different from replacing network protection, substation control or utility metering. Identify the required information, where it is measured and which system will use it.
Distributed energy resource management and network operations platforms may need site totals, individual asset telemetry or evidence of a commanded response. Establish those requirements with the operator rather than assuming one data stream serves every purpose.
Bring the site data together
Edge provides a local workspace for supported devices, dashboards, data and configured automation. It runs on the Gateway, connecting EpiSensor wireless monitoring and supported wired equipment.
Review the ZEM family for electricity measurements and the ZDR family for demand-response monitoring and control. Current datasheets define the available functions and configurations.
Where equipment already exposes useful measurements, assess its interface and mapping before adding independent hardware. Record the measurement location and whether the value represents a site total, generation, storage or a particular load.
Specify the receiving interface
Agree the destination system, authentication, point identifiers, units, timestamps, reporting intervals and quality indicators. A supported transport does not establish the meaning of its payload or the operator's acceptance of that data.
Edge supports pre-built and partner-built flows. If a project requires a particular utility or industrial protocol, verify that requirement against the actual installed integration and equipment. Do not infer support, or its absence, from a general marketing list.
Keep monitoring and protection distinct
A monitoring value or local automation rule is not evidence that a system fulfils a protection, synchrophasor or other specialised network requirement. Those functions need their own specified equipment and qualification.
For timing requirements, distinguish sampling, event recording, detection, transmission and physical actuation. Record which point in the system each figure describes. Test the full asset and communications path for the intended service.
Plan operation as well as commissioning
Agree who owns site configuration, credentials, updates, alarms and support. Document connection-loss behaviour and how the receiving system recognises stale or missing data. Exercise the agreed failure cases before expanding beyond the pilot.
The Demand Response & VPP application page links to project evidence and explains EpiSensor's role. The demand-response integration guide provides a more detailed checklist for measurements and commands.
Browse technology providers for context, then discuss the operator's requirements. A profile or case study is not a substitute for acceptance of your installation.