The PE Energy Management functionality and the Energy Measurement data are accessible for Clients directly when browsing the components of the “EnergyManagement” folder. Figure 7 shows an overview of the structural organization of the energy related functionality.

Devices offering Energy Measurement functionality provide EnergyMeasurementType Objects. Each EnergyMeasurementType Object contains the measurement values belonging to a specific Metering Point. A device can support an arbitrary number of Metering Points.

Devices offering Standby Management provide EnergyStandbyManagementType Objects. Each EnergyStandbyManagementType Object contains an EnergySavingModes container Object referencing EnergySavingModeType Objects that represent all available Energy Saving Modes (the EnergySavingModeType Objects are not visible in the Figure 7).

A device might support multiple EnergyStandbyManagementType Objects. Each EnergyStandbyManagementType Object represents one Standby Management Entity.

By invoking the StartPause Method of the EnergyStandbyManagementType Object, Clients can initiate the transition into an Energy Saving Mode.

The EnergyDevicePowerOffType Object provides access to the devices’ Sleep Mode WOL if supported. Clients can initiate the transition into the Sleep Mode WOL by invoking the SwitchOffWOL Method.

Figure 7 – Structural organization of PE Energy Management related functionality

Figure 8 shows the relationship between the PE Energy Management model and the other functional parts of the application model. HasEnergyMeasurement References connect the functional parts of the model with related EnergyMeasurementType Objects providing Energy Measurement values. HasEnergyStandbyManagement References connect the functional parts of the model offering Standby Management functions with related EnergyStandbyManagementType Objects. The EnergyDevicePowerOffType Object has no Reference to a functional part since the entire device is affected by power off.

Figure 8 shows a device with two main functional parts: The DriveConveyor Object is a functional part supporting Energy Measurement only. The Heating Object is a functional part supporting Energy Measurement and Standby Management.

For EnergyDevicePowerOffType Objects no association with a functional part is appropriate.

Figure 8 – Relationship to functional application model

Figure 9 shows the detailed PE Energy Management’s Information Model with the whole Object structure and the related type definitions. The figure contains the three basic independent root Objects for energy Standby Management, Energy Measurement and Sleep Mode WOL.

A LockingServicesType Object (defined in OPC 10000-100) is part of the EnergyStandbyManagementType Object to ensure that only one Client can control the Standby Management related functions.

Figure 9 – PROFIenergy OPC UA Object structure