IEC 60870-5-102: Bridging IEC 102 Energy Metering SCADA with IIoT Gateways and Cloud

IEC 60870-5-102 is the international standard protocol designed specifically for remote energy metering, enabling utilities, substations, and industrial facilities to collect integrated energy totals from electricity meters across distributed networks. For operations teams managing large fleets of meters — across oil fields, wind farms, substations, or industrial campuses — achieving reliable IEC 102 energy metering SCADA integration is critical to billing accuracy, demand management, regulatory compliance, and digital transformation. This technical guide explains how the protocol works, where it fits in a modern industrial architecture, and how an IIoT gateway platform bridges meter data to SCADA systems, historians, and cloud platforms without custom coding.

What Is IEC 60870-5-102 and Why It Matters for Energy Metering

IEC 60870-5-102 is part of the IEC 60870-5 family of telecontrol standards developed by the International Electrotechnical Commission. While IEC 60870-5-104 is widely used for telecontrol over TCP/IP networks, IEC 60870-5-102 was specifically designed for the transmission of integrated totals — cumulative energy values such as active and reactive energy in kilowatt-hours — from remote electricity meters to control centers and SCADA systems.

The protocol operates over serial communication links (RS-232, RS-485) and supports polling-based communication, where a master station — typically the SCADA server or a concentrator — requests energy registers from slave meters at defined intervals. This makes it particularly suited for grid-connected installations, substations, industrial distribution networks, and any application where metered energy data must be periodically consolidated for billing, auditing, or operational visibility.

Industries that rely heavily on IEC 60870-5-102 include electric utilities, oil and gas (for energy consumption accounting at remote sites), mining (where high-voltage distribution demands precise metering), renewable energy (solar and wind farms require granular energy production data), and water and wastewater utilities managing pumping energy costs. Manufacturers such as Schneider Electric, ABB, and Siemens produce meter families — including the ABB A-Series and Schneider Electric PM series — that communicate natively via IEC 60870-5-102, making the protocol deeply embedded in operational infrastructure worldwide.

How IEC 60870-5-102 Works: Protocol Architecture

Understanding the protocol mechanics is essential to designing a reliable IEC 102 energy metering SCADA architecture. The standard defines a layered communication model with the following key elements:

Communication Model and Data Objects

IEC 60870-5-102 uses a master/slave model. The master station initiates all communication sessions; slave devices (the meters) respond only when polled. The protocol defines specific Application Service Data Units (ASDUs) that carry energy values, timestamps, and status information. Key data objects include:

1. Integrated totals (active energy) — cumulative kWh values representing active power consumption over a billing period
2. Integrated totals (reactive energy) — cumulative kVARh values for power factor analysis and reactive power penalties
3. Time-tagged records — energy values with associated timestamps for period-accurate billing and auditing
4. Meter status and diagnostics — tamper detection, communication fault flags, and meter health indicators
5. Control objects — remote demand reset and register synchronization commands from the master

Physical Layer Considerations

The protocol was originally designed for serial links, which presents integration challenges in modern IT/OT architectures. Serial RS-485 buses may connect dozens of meters in a daisy-chain topology across substations or industrial facilities. Over longer distances, serial-to-Ethernet converters or dedicated concentrators are used, but these add complexity unless a unified IIoT gateway manages the entire collection layer. For IEC 102 energy metering SCADA projects, the gateway layer becomes the critical translation and aggregation point.

Polling Intervals and Data Latency

Unlike process data protocols that demand sub-second refresh rates, IEC 60870-5-102 is optimized for interval-based polling — typically every 15 minutes to one hour for billing-grade data. This interval-driven nature means the gateway must reliably store each polled record and forward it to upstream systems, even when network connectivity to the SCADA or cloud is temporarily unavailable. This is precisely where Store and Forward capability in the gateway layer becomes non-negotiable.

Challenges in IEC 102 Energy Metering SCADA Integration

Despite the protocol’s maturity, integrating IEC 60870-5-102 data into modern SCADA, historian, ERP, and cloud environments presents a set of well-documented challenges that automation engineers encounter across industries from Ecopetrol-scale oil operations to municipal water utilities:

1. Protocol translation complexity — SCADA platforms and cloud services do not natively speak IEC 60870-5-102; custom drivers or middleware are typically required, increasing project cost and maintenance burden
2. Serial-to-IP bridging — many legacy meters only support RS-485 serial communication, requiring physical and logical conversion before data can travel over modern Ethernet or cellular networks
3. Data loss during connectivity gaps — remote sites frequently experience network interruptions; without buffering, polled energy records are permanently lost, compromising billing accuracy and regulatory reporting
4. Timestamp integrity — accurate time-tagging of energy totals is essential for period billing; clock drift or synchronization failures introduce errors that are difficult to retroactively correct
5. Multi-meter, multi-protocol environments — most real sites combine IEC 60870-5-102 meters with Modbus RTU meters, IEC 61850 protection relays, and DNP3 RTUs, requiring a single platform to handle all protocols simultaneously
6. Delivering data to multiple consumers — the same meter data may need to reach a local SCADA historian, a corporate ERP such as SAP, a cloud analytics platform, and a billing system — simultaneously and reliably
7. Cybersecurity in substation and utility environments — uncontrolled point-to-point connections between metering networks and IT systems violate segmentation principles aligned with ISA/IEC 62443 zone and conduit models

The Role of an IIoT Gateway in IEC 102 Energy Metering SCADA Architecture

A modern IIoT gateway platform addresses all of these challenges by acting as the intelligent edge layer between the metering field and every upstream data consumer. Rather than building custom integrations for each destination — SCADA, historian, cloud, ERP — a capable IIoT gateway acquires data from IEC 60870-5-102 meters once and distributes it simultaneously to all required destinations in the appropriate format.

For IEC 102 energy metering SCADA deployments, the gateway performs several critical functions: it polls meters on the IEC 60870-5-102 bus, parses and structures the integrated total ASDUs, applies timestamp validation, buffers records locally during network outages, and publishes the data upstream via modern protocols such as OPC UA, MQTT, or REST API — all without requiring custom software development.

Gateway Deployment in the Purdue Model

In the context of the Purdue Reference Model for industrial cybersecurity architecture, an IIoT gateway supporting IEC 60870-5-102 typically sits at Level 2 (close to the meter bus) or at Level 3 (site operations hub), with data flowing upward through a Level 3.5 Industrial DMZ to IT systems at Levels 4 and 5. This architecture — aligned with ISA/IEC 62443 zones and conduits — ensures that metering data crosses the OT/IT boundary in a controlled, auditable manner rather than through unmanaged point-to-point connections. The gateway’s ability to initiate reverse connections (outbound from the OT side) further reduces the attack surface at the DMZ boundary, a requirement referenced in frameworks such as NERC CIP and NIS2 for critical energy infrastructure.

Store and Forward: The Non-Negotiable for Energy Metering

Remote metering sites — substations in rural areas, offshore platforms, wind farm substations — routinely experience WAN connectivity interruptions. A gateway with built-in Store and Forward capability buffers every polled energy record locally and automatically transmits the backlog to the SCADA historian or cloud platform once connectivity is restored. For billing-grade applications this is not optional; missing even a single 15-minute interval record can trigger costly reconciliation processes or regulatory non-compliance. The MQTT protocol with QoS level 1 or 2, combined with local buffering, provides a robust delivery mechanism for this use case.

Multi-Destination Data Delivery

Once the gateway has structured the IEC 60870-5-102 meter data, it can simultaneously deliver it to multiple consumers:

1. Local SCADA — via OPC UA Server or Modbus TCP, making meter tags available to any OPC-compliant SCADA platform from Wonderware to Ignition
2. Industrial Historian — local time-series storage (MongoDB-based) for on-premise data retention and trend analysis
3. Cloud platforms — AWS IoT Core, Azure IoT Hub, or Google Cloud IoT via MQTT or REST API, enabling cloud-based analytics and machine learning on energy consumption patterns
4. ERP and billing systems — SQL/ODBC integration delivers aggregated energy values directly to SAP or other enterprise systems for automated billing workflows
5. BI and analytics tools — Power BI or Tableau dashboards receive structured energy data for operational reporting and demand management visualization

A real-world example of this multi-destination architecture is illustrated by the Infinity Power deployment, where vNode connected the Taiba N’Diaye Wind Power Station in Senegal to a control center in the UK using IEC 60870-5-104 alongside MySQL database integration — demonstrating how similar protocols in the IEC 60870 family, including IEC 60870-5-102, can support cross-continental energy data flows with full data integrity and TLS encryption.

IEC 102 Energy Metering SCADA: Key Integration Requirements

When evaluating an IIoT gateway for IEC 60870-5-102 integration, engineering teams should verify the following requirements are met without custom development:

1. Native IEC 60870-5-102 client support — including ASDU parsing for integrated totals, time-tagged records, and meter status objects
2. Serial and Ethernet connectivity — RS-232/RS-485 serial ports for legacy meters plus Ethernet for IP-connected concentrators
3. Store and Forward with configurable buffer size — local retention of polled records during upstream network outages, with automatic replay on reconnection
4. Multi-protocol simultaneous acquisition — ability to poll IEC 60870-5-102, Modbus RTU, DNP3, and IEC 61850 on the same gateway instance
5. No-code / low-code configuration — web-based setup that allows automation engineers to configure meter connections, tag mappings, and data destinations without writing software
6. Unlimited tag licensing — energy metering projects often involve hundreds or thousands of individual register tags; per-tag licensing models make these projects economically unviable
7. Cybersecurity-ready architecture — RBAC user management, encrypted communications, reverse connection support, and audit logs aligned with ISA/IEC 62443 and NERC CIP expectations

For deeper reference on OPC UA as a destination protocol for structured meter data, the OPC Foundation publishes companion specifications for energy management use cases that align well with IEC 60870-5-102 data models.

How vNode Solves This

The vNode Industrial Data Platform from Vester Business is purpose-built to solve exactly the challenges described in this guide. Rather than acting as a simple protocol converter, vNode provides a complete, no-code data platform that acquires IEC 60870-5-102 meter data, structures it, stores it locally, and delivers it simultaneously to every upstream consumer — SCADA, historian, cloud, ERP, and AI platforms — through a single, unified configuration interface.

Here is how vNode specifically addresses IEC 102 energy metering SCADA integration requirements:

1. Native IEC 60870-5-102 protocol support — vNode includes a built-in IEC 60870-5-102 client driver that polls meters, parses integrated total ASDUs, and maps energy values to structured tags without any custom development. It runs alongside IEC 60870-5-104, Modbus RTU/TCP, DNP3, IEC 61850, OPC UA, and more — all simultaneously on the same node.
2. Store and Forward — vNode’s MQTT module includes built-in Store and Forward, ensuring that every polled meter record is buffered locally and delivered to upstream brokers, cloud platforms, or historians even after WAN outages of hours or days. This is the non-negotiable capability for billing-grade energy metering at remote sites.
3. Unlimited tag licensing — vNode charges no per-tag fees. A substation with 5,000 metering tags costs the same as one with 50. This makes large-scale IEC 102 energy metering SCADA rollouts economically predictable, especially for system integrators managing multi-site deployments.
4. Historian module — vNode’s built-in industrial historian (MongoDB-based) stores time-series energy data locally at the site, with central aggregation capabilities. This provides on-premise data retention independent of cloud connectivity, critical for regulatory audit trails.
5. Multi-destination delivery — from a single IEC 60870-5-102 data acquisition session, vNode simultaneously publishes to OPC UA Server (for local SCADA), MQTT broker (for cloud or Sparkplug B), SQL/ODBC (for SAP/ERP), REST API (for web applications), and CSV/XML files (for reporting).
6. Cybersecurity-ready architecture — vNode supports deployment at the Industrial DMZ (Level 3.5), reverse connections from the OT side, Data Diode-compatible architectures, RBAC user management, and full communication logs — aligned with ISA/IEC 62443 zone/conduit models and NERC CIP requirements applicable to energy metering infrastructure.
7. No-code web configuration — automation engineers configure the entire IEC 60870-5-102 integration — meter polling, tag mapping, historian storage, MQTT publishing, OPC UA server exposure — through a browser-based interface. No programming, no SDK, no vendor-specific toolchain required.
8. Multiplatform deployment — vNode runs on Windows, Linux, and ARM embedded systems, enabling deployment on industrial PCs at substations, ruggedized edge hardware in the field, or virtual machines at site operations centers.

System integrators working on utility, oil and gas, or renewable energy metering projects can contact the vNode team to discuss specific IEC 60870-5-102 integration requirements. Full protocol and module documentation is available in the vNode user manual, and the latest platform capabilities are detailed in the vNode 1.22 release notes.

Frequently Asked Questions

What is the difference between IEC 60870-5-102 and IEC 60870-5-104 for energy metering SCADA?

IEC 60870-5-102 is specifically designed for integrated energy totals (cumulative kWh/kVARh) from electricity meters, typically over serial links, and is optimized for billing-grade interval data collection. IEC 60870-5-104 is a general-purpose telecontrol protocol for real-time process data over TCP/IP networks and is not specifically tailored to energy metering register structures. In modern IEC 102 energy metering SCADA architectures, both protocols often coexist — 102 at the meter level, 104 for site-to-control-center communication.

Can vNode connect IEC 60870-5-102 meters and publish data to cloud platforms simultaneously?

Yes. vNode acquires data from IEC 60870-5-102 meters via its native protocol driver and simultaneously publishes structured energy data to MQTT brokers (AWS IoT Core, Azure IoT Hub, Google Cloud IoT), OPC UA servers, SQL databases, and REST APIs — all from a single no-code configuration. The built-in Store and Forward module ensures no data loss during cloud connectivity interruptions, which is essential for remote metering sites.

How does an IIoT gateway handle data loss during network outages in energy metering applications?

A gateway with Store and Forward capability — such as vNode — buffers every polled meter record locally in persistent storage when the upstream network (SCADA, cloud, or historian) is unavailable. Once connectivity is restored, the gateway automatically replays the buffered records in chronological order, ensuring the complete time-series dataset reaches the destination with full timestamp integrity. This is critical for billing-grade IEC 102 energy metering SCADA applications where missing interval records create reconciliation and compliance issues.

Is IEC 60870-5-102 relevant for renewable energy and solar/wind farm metering?

Yes. While newer renewable energy projects increasingly adopt IEC 61850 and MQTT-based protocols, a large installed base of wind and solar farm substations — particularly in Latin America, Africa, and Southern Europe — uses IEC 60870-5-102 for energy production metering. The Infinity Power wind farm deployment in Senegal is an example of how IEC 60870 family protocols remain central to renewable energy data infrastructure, and vNode’s multi-protocol support ensures these meters integrate seamlessly into modern IEC 102 energy metering SCADA and cloud architectures.