Energy systems integration
We connect PCS, BMS, protection relays, inverters, meters and control systems into one data layer. SCADA integration or IoT platform delivery designed so that adding the next device is a configuration change, not another integration project.
System integration services for energy operators
We work with PV, BESS, cogeneration and local distribution operators. The three types of engagement we see most often:
- Multi-technology integration on a single site — one dashboard for PCS, BMS, protection and metering, vendor-agnostic. Unifying data across equipment vendors is the foundation for any optimisation work later.
- SCADA integration into a cloud platform — when local SCADA already handles control but a consolidated portfolio view is missing. We build the bridging layer that pushes data into a central platform and takes dispatch setpoints back.
- Bridging energy systems into ERP / EMS — REST / OPC UA / MQTT interfaces between operational data and third-party systems (aggregators, trading platforms, reporting).
SCADA, industrial systems and IoT integration
Industrial integration in energy is never about a single protocol. A real project mixes Modbus TCP on the PCS, IEC 61850 on protection relays, proprietary CAN on the BMS and REST API on the aggregator. Our IoT platform, built on Azure IoT Hub and ECC, covers:
Modbus TCP / RTU
Native support, hot-reloadable register maps, batched reads. 913 operations across 9 devices in production — one edge module, one configuration.
IEC 61850
Protection relay integration (ABB REF615, SIPROTEC) via MMS / GOOSE gateway. Protection functions stay local; events and measurements flow to the cloud.
OPC UA / MQTT
Bridges to existing SCADA (Zenon, WinCC, Wonderware) and aggregators. No need to swap the control system — we add the data layer alongside it.
REST / webhook
Interfaces for ERP, trading platforms and dispatch. Every API call is logged into a cryptographically verifiable audit chain.
Remote control and dispatch
Integration is not only about reading data. Operators increasingly need remote control — PCS setpoints, protection blocking, dispatch commands from PV to trading platform. We cover this topic in depth on a dedicated page:
→ Remote control of energy assets: setpoints, dispatch and the safety of remote writes
Why route it through the ECC platform
An integration project without a platform underneath means you build the same thing again next year — for a different customer, a different vendor, a different site. ECC is multi-tenant: integration written once for Sinexcel PCS or ABB Emax2 serves every project after that. Practically:
- Register maps as data, not code — adding a new device is a JSON commit, not a new container release.
- Multi-tenant isolation — one deployed system, N customers, hard data separation.
- NIS2-ready audit chain — every integration action gets a cryptographically verifiable record. Certified logging without a binder.
- Offline-resilient edge — data buffers locally and catches up when connectivity returns. Uplink loss is not telemetry loss.
Frequently asked
How long does integrating a new device type take?
For a standard Modbus TCP device with usable documentation, 1–3 days including tests. For non-standard protocols (proprietary CAN, serial RTU via gateway), 1–2 weeks. The number holds because register maps are data, not code — every subsequent integration is faster than the previous one.
Can you integrate third-party SCADA?
Yes — via OPC UA, Modbus TCP bridge or REST API. Most often we build a bridging layer that leaves local SCADA in charge of protection functions and duplicates the data into the central platform for reporting and alerting.
What's the ceiling on devices and sites?
Architecturally per-tenant Azure IoT Hub → effectively no cap. Production today is one site, 9 devices, 913 operations every 30 seconds. Target 2026–2029 is 25 sites / 5 customers on the same platform.
Who owns cybersecurity of the integration?
ECC meets NIS2 requirements on logging, RBAC and audit. Pentest reports and security review artefacts are provided before deployment. Security architecture is documented at /legal/security.
Can we take over operations after handover?
Yes. You either run the platform yourselves (self-hosted on your own Azure tenant) or as SaaS. Integrator role and operator role are separated by design — handover to the customer or an internal O&M team is part of the standard delivery.