Can an existing energy meter be reused without replacement?

This depends on the model, interfaces and required data. An authorised export from the existing system may be sufficient. An additional meter connection requires assessment of available capacity and coexistence tests.

Can two systems share the same Modbus serial bus?

The Modbus serial guide specifies one master at a time on the bus. Two systems should therefore not independently poll that same bus. Data redistribution or a gateway architecture needs to be assessed for the equipment involved.

Must existing collection be interrupted?

This depends on the architecture and proposed change. Any interruption, its authorisation and rollback must be defined with operations. The presence of an interface alone cannot guarantee uninterrupted operation.

What documents are needed to assess reuse of meter data?

Gather meter and gateway references and manuals, the exchange diagram, variables and units, the existing acquisition interval, authorised access and the collection owner. Define the intended use and production constraints.

Reusing an energy meter already in service

An energy meter may already feed a PLC, a SCADA system or a service provider’s platform. Before adding energy monitoring, identify how that collection works. An additional connection may affect communication load, access or a gateway’s behaviour. The project must preserve existing uses and define how to verify this.

This guide proposes a preparation method. It does not describe a completed client assignment or guarantee integration without interruption. The decision depends on the meter model, its interfaces, the existing system and site authorisations.

Identify who already uses the meter

Start with operations and maintenance. Which device reads the meter? Who configures the reading? Where are records retained? Are they used for an alarm, control, internal reporting or a contractual relationship? A value visible in software does not describe the whole chain.

Record the meter reference, version, interfaces in use and available documentation. Include gateways and intermediate devices. For each flow, identify its owner, variables, configured acquisition interval and known dependencies. Separate documented information from observations still needed with authorised staff.

An energy metering plan defines measurement needs. This article addresses a narrower question: how to add a use to an acquisition chain that is already operating.

Compare existing data access with an additional meter connection

Assess two paths before choosing hardware.

Reuse data from the existing system. An authorised export or interface may provide the required measurements. Check available variables, quality, delays, usage rights and access terms. This creates a dependency on the system supplying the data.
Read an interface on the meter. The device, its configuration and the network must support the additional use. Identify available capacity, current exchanges and the tests needed.

Neither option suits every installation. An existing daily index may be sufficient for reporting but lack the detail needed to analyse operation. Equally, a limited requirement does not automatically justify direct meter access. Define the decision the data must support before requesting more frequent acquisition.

Distinguish serial communication from Ethernet access

The Modbus serial-line V1.02 guide, section 2.1, specifies one master at a time on the bus. Adding a second device that independently polls the same bus is therefore not a simple duplicate read. Examine redistribution through the existing system or a suitable gateway architecture.

For Ethernet, the Modbus TCP/IP implementation guide, section 4.4.2.1, describes processing limits that depend on the server implementation. A network port does not establish that a meter or gateway can accept an additional reader at the required rate. Model-specific documentation and tests remain necessary.

For a pulse output, M-Bus interface or proprietary protocol, consult the corresponding documentation. Do not infer its behaviour from Modbus. Compatibility must cover the full chain from meter to receiving software.

Define the meaning of each data point

Before comparing screens, list the quantity, unit, scale, counting direction and processing applied. Power in kW, a cumulative energy index in kWh and consumption calculated over a period are different data. Identify transformation ratios and sign conventions where relevant.

Where data passes through OPC UA, the OPC Foundation’s DataValue structure distinguishes the value, status and source and server timestamps. Retain this information when available. A recent receipt time alone does not establish that a measurement has just been refreshed.

Define behaviour for missing, invalid or delayed data. Avoid presenting an old value as a fresh measurement. Substitution, calculation and historical recovery rules should remain identifiable.

Prepare the change with the site’s responsible staff

Identify the owners of existing collection and the new interface, and who authorises the change. Specify access, reading or writing permissions and configurations to back up. A shared account or available network connection does not authorise a modification.

The NIST OT guide, SP 800-82 revision 3, addresses change management in the context of plant availability and safety constraints. This technical reference is not a Swiss regulatory requirement applicable to every project.

Agree on an intervention window where needed, criteria for stopping the trial and a workable rollback. A configuration copy is insufficient on its own: identify who can restore it and how restoration would affect active exchanges.

Verify that both uses can coexist

Before the addition, establish a reference with authorised tools: data received by the existing system, communication status, known faults and operating conditions. Agree acceptance criteria with operations for each system’s needs.

After the change, check both paths. A new dashboard can display a measurement while the original collection develops gaps. Check values, units, timestamps, faults and continuity. Communication-loss and recovery tests must be planned around site risks, rather than improvised on a running installation.

Record expected and observed results, the tested configuration and deviations. If a limit could not be verified, retain it as an acceptance reservation instead of concluding that the installation is generally compatible.

Keep historical records understandable

Document the cutover date, data sources, gaps and changes in processing. Retain access to original records under the site’s agreements. Do not automatically join series with different units or measurement boundaries.

The handover package contains the exchange diagram, point list, authorised access, configuration backups and test results. The energy integration deliverables guide places these in the wider project. Choosing OPC UA interfaces is a related question where several systems need the same data.

Vanguard Systems assesses energy interfaces and PLC/SCADA automation in French-speaking Switzerland. To scope a data integration project, share equipment references and the available architecture. The proposal will define access, tests and responsibilities. Maintenance follow-up is agreed for the installations covered.