Device communication

The following device communication architectures can be used when integrating Power Operation and Power Monitoring Expert: 

• Multi-mastering all devices – Setting up device communications in both Power Operation and Power Monitoring Expert
• Single-mastering all devices – Setting up device communications with Power Operation and then transferring device data to Power Monitoring Expert using an Extract, Transform, and Load (ETL) tool
  • Historical trending is assigned to Power Operation for most devices
  • Having Power Operation solely acquire data from meters provides the following benefits:
    • Improved performance: Power Operation trend acquisition can be assigned a lower priority than real-time and alarm data thereby reducing CPU/RAM loads
    • Increased functionality: Allows PME reporting to be run on devices with protocols not intrinsically supported by PME (e.g.: IEC-61850, DNP3, SNMP, BACnet, etc.)
    • Simplified deployments and maintenance: Devices are set up and maintained in Power Operation only. Meaning there is no risk that device names between Power Operation and PME are inconsistent.

The following image illustrates the recommended device communication architecture for Power Operation with Advanced Reporting and Dashboards:

Using ETL for communication with other applications

The following image shows an example architecture for using ETL for communication with other applications, such as 3rd party billing applications or DCO.