Grid and network software

Grid and network software helps network operators and asset owners monitor and control distribution assets, substations and connected generation. Check protocol support, cyber security certification and whether local control keeps working when the connection drops.

Platforms in this directory

What to look for

What good looks like

  • Deployments with utilities, DSOs or grid operators that have demanding requirements
  • Documented protocols, compliance and security for field and control integration
  • Clear handling of assets, telemetry and operational workflows

Red flags

  • Utility positioning comes without evidence from regulated markets.
  • Standards, compliance and security are thinly documented.
  • Broad grid language comes with little proof of field deployment.

Site visibility for grid and DER platforms

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, since each purpose may need its own data stream.

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 electricity monitoring range for electricity measurements and demand response for monitoring and control of site loads. 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. Agree the meaning of each payload field and confirm the operator accepts the data before go-live.

Edge sends data through integration flows configured for each service. 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

Protection, synchrophasor and other specialised network functions need their own specified equipment and qualification, so specify them separately from monitoring and local automation.

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 and VPP page links to project evidence and explains EpiSensor's role. The demand response guide has a more detailed checklist for measurements and commands.

Browse technology providers for context, then confirm the operator's requirements for your installation.

Exploring behind-the-meter visibility? Tell us about the site, existing equipment and the data or control workflow you want to build.

Browse by category

Buyer guides