1 -Power Monitoring Expert Architecture

Architecture

• The recommended architecture for Power Monitoring Expert is Standalone.
• This architecture involves using a single server to host both the application and the database.
• A distributed database architecture is an alternative option when the standalone approach is not feasible.
• In a distributed architecture, the application resides on one server, while the database is located on a separate server.
• The distributed architecture does not provide any performance benefits over standalone architecture.

Deployment Scenarios for Distributed Database Architecture

• Existing SQL server: If the customer already has an existing SQL server, a distributed architecture can utilize it.
• IT Requirements: If IT regulations prevent installing SQL server with another application on the same server, distributed architecture is necessary.
• Redundancy: If SQL server redundancy is required through SQL Clustering or third-party tools, a distributed database architecture is needed.
• Database Management: If specific database management rules are required, such as SQL jobs, backups, or data security, distributed architecture allows for separate management.

Client Types

• There are two types of clients: Engineering Client and Web Client.
• Both types require a Client Access license.

Engineering Client

• An administrative interface for configuring and managing the PME system.
• Installed on the main PME server as a thick client.
• Contains applications for system management, design, and configuration:
  • Management Console: For adding, removing, and configuring system components, such as devices.
  • Designer: For creating graphical representations of the power system, displaying real-time and historical data.
  • Configuration Tools: For configuring setup registers of PowerLogic ION meters and creating frameworks on ION devices or software nodes.

Web Client

• Provides access to applications like dashboards, diagrams, trends, alarms, and reports for daily power management tasks.
• Primary user application for viewing real-time, historical, and alarm data in a single interface.
• Applications include:
  • Dashboards: View high-level, historical, and real-time data in gadgets.
  • Diagrams: View low-level, historical, and real-time data in one-line diagrams and graphics.
  • Trends: View trends for real-time and historical data.

Network Types

• There are two basic network types: Ethernet and Serial.

Ethernet Networks

• Can be incorporated into regular corporate LANs or be independent networks.
• Devices are configured with fixed IP addresses (IPv4 or IPv6) and ports or based on device names.
• Ethernet communications rely on encapsulated Modbus or ION protocols and are not encrypted.

Serial Device Networks

• Require an intermediate converter or gateway to establish a network connection.
• Devices are configured by providing fixed IP addresses, ports, or through device names.
• Serial communications can limit overall system performance.
• Bandwidth needs are generally low but depend on the volume and type of data requested from devices by PME.

Power Monitoring Devices

• A variety of electrical monitoring devices are available for different applications.
• Devices offer multiple communication protocols, including Modbus, Ethernet, and IEC 61850.
• Key products include:
  • Easergy P1, P3, and P5: Offer basic to advanced capabilities for different power distribution systems.
  • Sepam Series 60-80, MiCOM Px10, Px20, Px30, and Px40: Provide comprehensive monitoring, protection, and automation functionalities.
  • Vamp 11: Designed for basic energy submetering in various applications.

System Integration

• PME can connect with external systems and software as both a server and a client.
• Data can be exchanged between PME and other systems, including real-time and historical information.
• Integration technologies include:
  • OPC DA server: Exports real-time data.
  • OPC DA client: Imports real-time data.
  • EWS server: Exports real-time, historical, and alarm data.
  • EWS client: Imports historical and alarm data.
  • ETL: Exports or imports historical data.
  • ODBC: Provides access to historical data for any ODBC-compliant application.
  • PQDIF: Exports power quality data in a standardized format for sharing power quality information between software applications.

Virtual Processor Service (VIP)

• A Windows-based service that runs on the PME server.
• Functions as a virtual device, operating within the server's memory, not as a remote device.
• Contains ION modules for processing information, providing coordinated data collection, processing, and control functions.
• Enables distributed operations, customized solutions, and data exporting for various industry needs.

EcoStruxure Integration

• PME integrates with EcoStruxureTM Power Operation (PO) and EcoStruxureTM Building Operation (EBO) for enhanced functionality and user experience.
• PME reports and dashboards are embedded within PO and EBO interfaces.
• The integration provides a seamless user experience by combining PME features within the respective EcoStruxure system interfaces.

Explore the architectural options for Power Monitoring Expert, focusing on standalone and distributed database architectures. This quiz delves into deployment scenarios where distributed database architecture might be necessary, such as IT requirements and existing SQL servers.