Energy integration: from metering to maintenance

An industrial energy integration project connects measurements, automation and operating conditions. Its scope may include meters, supervision, control changes and performance monitoring. When consulting a provider in French-speaking Switzerland, also define the tests, records and responsibilities expected after commissioning.

A dashboard alone does not cover that work. Identify who connects equipment, who programs the controls, who authorises changes and who takes over maintenance. The checklist below proposes deliverables to agree for your site. It is neither a universal regulatory checklist nor a promise of energy savings.

Start from the operating need

You may need to understand consumption outside production hours, change a ventilation sequence or coordinate several utilities. Describe the observed problem, affected equipment and decision the data should support. Record the production, quality and safety constraints that govern any intervention.

An industrial energy audit helps assess installations and prioritise actions. An energy metering plan defines useful measurements. The integration project then organises implementation: interfaces, installation work, programming, testing and handover to operations.

For building services, SwissEnergy describes selecting measures, implementing them and reviewing their results. An industrial project also needs to account for the process and the expertise required on each item of equipment.

Define work packages and responsibilities

A proposal should show where each company's work starts and ends. An integrator may provide architecture and programming without carrying out all electrical or mechanical work. The OEM may retain responsibility for certain machine changes. The site team is still needed for access, procedures and operating decisions.

This allocation prevents a connection, licence or test from being assumed included by both parties without an owner. Specialist work, shutdowns and site resources belong in the scope or exclusions. The external technical service models help distribute these roles with your team.

Specify the meter, PLC, SCADA and EMS interfaces

Here, EMS means energy management software. It uses data to monitor and analyse consumption. A PLC executes programmed equipment functions. SCADA provides supervision and, depending on configuration, operating controls. Their relationship depends on the existing architecture; an additional platform is not always necessary.

Naming a protocol such as OPC UA or Modbus does not fully specify an interface. Request a matrix identifying the source, destination, variable, unit, scaling, exchange direction and configuration owner. Include acquisition frequency, timestamps, read or write permissions and handling of missing data.

The OPC Foundation DataValue definition distinguishes the value, its status and source and server timestamps. These elements need to be interpreted together. A usable communication status does not establish meter calibration; an old source timestamp alone does not prove that communication has stopped.

Plan checks across the complete chain. A correct value on the meter display can become incorrect after unit conversion or aggregation. Check the distinction between power in kW and energy in kWh, the handling of cumulative readings and the periods actually being compared.

Separate data collection from control

Collecting consumption and changing a setpoint are separate functions to specify. If the project changes control logic, describe operating modes, permitted limits, command priorities and behaviour when data or communication is lost.

For each function, retain three separate states: programmed, connected and tested. A block in a PLC program does not establish that its sensor is connected or that the function has been checked under the intended conditions. Reserved functions should remain identifiable in the handover package.

Preparing the change includes identifying the baseline version, backups, affected interfaces and rollback conditions. The NIST OT guide, SP 800-82 Revision 3, recommends documenting configurations, controlling changes and checking recovery arrangements. These recommendations are neither Swiss legal requirements nor authorisation to change equipment.

Prepare tests before programming

An acceptance criterion should describe an observable result. For example: invalid data is indicated to the operator, an alarm states the expected action, or history allows an event period to be retrieved. Limits and operating conditions come from the site's requirements.

The official IEC 62381:2024 catalogue summary describes acceptance and integration tests as ways to verify requirements in the applicable specification. Activities and responsibilities need to be agreed for the installation. This does not mean every small project requires an identical FAT/SAT arrangement.

Where factory tests are useful, they can check sequences and simulated interfaces before installation. Site tests then check behaviour with the real equipment and connections. A simulated test does not establish field wiring; successful equipment startup does not establish that every function works.

For each test, retain the tested version, initial conditions, expected result, observed result and decision on deviations. Fault and recovery tests must follow authorised procedures without compromising safeguards or production. Acceptance should identify remaining reservations and their owners.

Illustrative scenario: ventilation running outside production hours

This is a fictional scenario. A trend shows continuing consumption after production stops. First relate that period to ventilation states and site requirements. Operation outside production hours may remain necessary for quality, hygiene or thermal conditions.

If a change is justified, the project describes the permitted sequence, conditions that inhibit it and information required in supervision. Tests check those situations and the return to normal operation. Energy measurements are then used to compare relevant periods. The scenario supports no promised percentage saving.

Hand over a package maintenance can use

The project handover should match the version in service. Agree on delivery of drawings, equipment lists, parameters, PLC/HMI backups and operator documentation. Source-code rights, licences and necessary engineering tools belong in the proposal and supplier agreements.

A backup should identify the equipment, version, date, location and owner. State what was backed up, what was checked and what remains to be tested. The ability to restore a file alone does not establish that the whole installation will restart correctly.

The transition to industrial maintenance includes agreed checks, access management, change tracking and support conditions. Response times, parts and OEM escalation need contractual terms. General availability shown on a website does not replace a commitment applicable to your installation.

Verify energy results after acceptance

Functional acceptance and savings measurement answer different questions. Acceptance checks the agreed functions. Savings measurement assesses the energy effect within a defined boundary and period.

EVO presents IPMVP as a measurement and verification framework tailored to each project. Savings are determined through before-and-after comparisons, with adjustments when conditions change. Production volume, operating hours or weather may need consideration depending on the installation.

Define the baseline, required data, calculation rules and comparison limits before the work. Record boundary changes and unusable periods. An observed reduction in consumption needs explanation before it can be attributed to the intervention.

Prepare a consultation in French-speaking Switzerland

For a site in Vaud or Valais, provide the affected equipment, available drawings, existing systems and access constraints. Request a proposal separating studies, installation work, programming, testing, documentation and maintenance, with assumptions and exclusions for each package.

Vanguard Systems works on energy integration, PLC/SCADA automation and maintenance in French-speaking Switzerland. Scope is defined with the operator and the partners needed. The published references describe assignments and their attribution. Describe your project to define interfaces, deliverables and handover conditions.