Data Center Power Management 8.2 - Design Guide

Data Center Power Management
Design Guide
StruxureWare™ Power Monitoring Expert
StruxureWare PowerSCADA Expert
Schneider Electric – Data Centers

04/2017
MRP# 7EN42-0151-00
Legal Information
The Schneider Electric brand and any registered trademarks of Schneider
Electric Industries SAS referred to in this guide are the sole property of
Schneider Electric SA and its subsidiaries. They may not be used for any
purpose without the owner's permission, given in writing. This guide and its
content are protected, within the meaning of the French intellectual property
code (Code de la propriété intellectuelle français, referred to hereafter as "the
Code"), under the laws of copyright covering texts, drawings and models, as well
as by trademark law. You agree not to reproduce, other than for your own
personal, noncommercial use as defined in the Code, all or part of this guide on
any medium whatsoever without Schneider Electric’s permission, given in
writing. You also agree not to establish any hypertext links to this guide or its
content. Schneider Electric does not grant any right or license for the personal
and noncommercial use of the guide or its content, except for a non-exclusive
license to consult it on an "as is" basis, at your own risk. All other rights are
reserved.
Electrical equipment should be installed, operated, serviced and maintained only

by qualified personnel. No responsibility is assumed by Schneider Electric for
any consequences arising out of the use of this material.
As standards, specifications, and designs change from time to time, please ask
for confirmation of the information given in this publication.
Safety information
Important information
Read these instructions carefully and look at the equipment to become
familiar with the device before trying to install, operate, service or maintain
it. The following special messages may appear throughout this manual or
on the equipment to warn of potential hazards or to call attention to
information that clarifies or simplifies a procedure.
The addition of either symbol to a “Danger” or “Warning” safety label indicates

that an electrical hazard exists which will result in personal injury if the
instructions are not followed.
This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety messages that follow this symbol to avoid possible
injury or death.
DANGER
DANGER indicates an imminently hazardous situation which, if not avoided, will result
in death or serious injury.
WARNING
WARNING indicates a potentially hazardous situation which, if not avoided, can result
in death or serious injury.
CAUTION
CAUTION indicates a potentially hazardous situation which, if not avoided, can result
in minor or moderate injury.
NOTICE
NOTICE is used to address practices not related to physical injury. The safety alert
symbol shall not be used with this signal word.
Please note
Electrical equipment should be installed, operated, serviced and maintained only
by qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material. A qualified person is one who
has skills and knowledge related to the construction, installation, and operation of
electrical equipment and has received safety training to recognize and avoid the
hazards involved.
A qualified person is one who has skills and knowledge related to the construction,
installation, and operation of electrical equipment and has received safety training
to recognize and avoid the hazards involved.
Data Center Power Management 8.2 – Design Guide Schneider Electric
Contents
Legal Information ................................................................................................................................................................................................... 2
Safety information .................................................................................................................................................................................................. 2
Important information .................................................................................................................................................................................................................. 2
Please note ................................................................................................................................................................................................................................... 2
Contents .................................................................................................................................................................................................................. 3
1 Introduction ..................................................................................................................................................................... 6
2 Data Center Power Management Architectures ............................................................................................................... 7
2.1 Which Offer and Architecture Should I Choose? ....................................................................................................................................... 7
2.2 Part Name to Solution Module Mapping .................................................................................................................................................. 9
2.3 Power Monitoring Expert Data Center Edition ........................................................................................................................................ 10
2.3.1 Software Architecture ................................................................................................................................................................................................. 10
2.3.2 Server Architecture (server specs provided in IT Infrastructure section) ...................................................................................................................... 11
2.4 PowerSCADA Expert with Advanced Reports .......................................................................................................................................... 12
2.4.1 Software Architecture ................................................................................................................................................................................................. 12
2.4.2 Server Architecture (server specs provided in IT Infrastructure section) ...................................................................................................................... 13
2.5 Building Management System + Power Management............................................................................................................................ 14
2.5.1 Software Architectures ................................................................................................................................................................................................ 14
2.5.1.1 PSE with Advanced Reports + SBO ................................................................................................................................................................... 14
2.5.1.2 PME-DC + SBO.................................................................................................................................................................................................. 15
2.5.2 Server Architectures (server specs provided in IT Infrastructure section) ..................................................................................................................... 16
3 Reference Architecture .................................................................................................................................................. 17
3.1 Overview ................................................................................................................................................................................................ 17
3.1.1 Medium Voltage Substation ........................................................................................................................................................................................ 18
3.1.2 Data Hall 1 .................................................................................................................................................................................................................. 19
3.1.3 Data Hall 1 IT Distribution ........................................................................................................................................................................................... 20
3.1.4 Data Hall 2 .................................................................................................................................................................................................................. 21
3.1.6 Data Halls 3 and 4 ....................................................................................................................................................................................................... 23
3.1.9 Data Hall 5 .................................................................................................................................................................................................................. 25
3.1.11 Data Hall 6 .................................................................................................................................................................................................................. 27
3.2 Power Equipment Description ................................................................................................................................................................ 28
3.3 IEC Consideration.................................................................................................................................................................................... 29
4 Design Considerations by Solution Module..................................................................................................................... 30
4.1 Summary of Metering by Solution Module ............................................................................................................................................. 30
4.2 Power Monitoring and Control (Base) .................................................................................................................................................... 34
4.2.1 View Real-Time Power System Status and Trends ....................................................................................................................................................... 34
4.2.1.1 Power Monitoring Expert Data Center Edition ................................................................................................................................................. 34
4.2.1.2 PowerSCADA Expert with Advanced Reports ................................................................................................................................................... 37
4.2.1.3 Recommended Meter Types ............................................................................................................................................................................ 40
4.2.1.4 Required Measurements.................................................................................................................................................................................. 40
4.2.2 Analyze Power System Events ..................................................................................................................................................................................... 40
4.2.2.5 Sequence of Events Recording (SER) ................................................................................................................................................................ 42
4.2.2.6 SER Recommended Hardware and Meters....................................................................................................................................................... 43
4.2.2.7 Time Sync Protocols and Required Cables ........................................................................................................................................................ 45
4.2.2.8 Suggested Breaker Contacts............................................................................................................................................................................. 46
4.2.3 (Optional) Get Power System Alarm Notifications ....................................................................................................................................................... 47
4.2.3.3 Recommended Alarm Points ............................................................................................................................................................................ 49
4.2.4 Analyze Power Quality Issues ....................................................................................................................................................................................... 49
4.2.4.3 Required Meter Types and Frameworks .......................................................................................................................................................... 50
4.2.5 Collect and Manage Data from Intelligent Devices ...................................................................................................................................................... 50
4.2.5.1 (Optional) PME-DC Using KEPServerEX............................................................................................................................................................. 50
© 2017 Schneider Electric. All rights reserved. For Internal Use Only Page 3
Schneider Electric Data Center Power Management 8.2 – Design Guide

4.2.6 Share Data between Software Systems ....................................................................................................................................................................... 51
4.2.6.1 ETL for Data Center Operation (DCO) ................................................................................................................................................................ 51
4.2.6.2 ETL for PowerSCADA Expert Integration ............................................................................................................................................................. 54
4.2.7 (Optional) HTML 5 Remote Desktop Application ........................................................................................................................................................ 55
4.2.7.1 PowerSCADA Expert with Advanced Reports................................................................................................................................................... 55
4.3 Capacity Management ........................................................................................................................................................................... 56
4.3.1 Branch Circuit Power ................................................................................................................................................................................................... 56
4.3.1.3 Required Meter Types...................................................................................................................................................................................... 57
4.3.2 Generator Power ......................................................................................................................................................................................................... 58
4.3.3 UPS Power ................................................................................................................................................................................................................... 60
4.4 Equipment Performance ......................................................................................................................................................................... 62
4.4.1 Generator Performance................................................................................................................................................................................................. 62
4.4.1.5 Other Considerations ....................................................................................................................................................................................... 64
4.4.2 Breaker Performance .................................................................................................................................................................................................. 66
4.4.2.3 Supported Circuit Breakers and Trip Units........................................................................................................................................................ 67
4.5 IT Billing .................................................................................................................................................................................................. 67
4.5.1 Energy by IT Customer ................................................................................................................................................................................................ 67
4.5.1.3 Required Meter Types...................................................................................................................................................................................... 68
4.5.2 Billing Module ............................................................................................................................................................................................................. 69
4.5.3 ETL for Export to Third Party Billing .............................................................................................................................................................................. 71
4.6 System Efficiency .................................................................................................................................................................................... 73
4.6.1 Power Losses ............................................................................................................................................................................................................... 73
4.6.2 Power Usage Effectiveness (PUE) ................................................................................................................................................................................. 76
4.6.3 Energy Analysis ........................................................................................................................................................................................................... 80
5 SBO Integration.............................................................................................................................................................. 82
5.1 SBO + PowerSCADA Expert with Advanced Reports ................................................................................................................................ 83
5.1.1 Alarm and Real-Time Data in SBO from PSE ............................................................................................................................................................... 84
Page 4 For Internal Use Only © 2017 Schneider Electric. All rights reserved.
5.1.2 SBO to PME ETL .......................................................................................................................................................................................................... 85

5.1.3 Dashboards and Reports Integrated into SBO ............................................................................................................................................................ 85
5.2 SBO + Power Monitoring Expert Data Center Edition ............................................................................................................................. 87
5.2.1 Alarm and Real-Time Data in SBO from PME.............................................................................................................................................................. 88
5.2.2 SBO to PME ETL .......................................................................................................................................................................................................... 88
5.2.3 Dashboards and Reports Integrated into SBO ............................................................................................................................................................ 89
6 System Communication Design ...................................................................................................................................... 90
6.1 Real Time Data and Alarming Performance ............................................................................................................................................ 90
6.1.1 Real Time Data – PME Only ......................................................................................................................................................................................... 90
6.1.2 Real Time Data – PME + PSE ........................................................................................................................................................................................ 90
6.1.3 Alarming – PME Only .................................................................................................................................................................................................. 91
6.1.4 Alarming – PME + PSE ................................................................................................................................................................................................. 91
6.1.5 Alarming – PSE only .................................................................................................................................................................................................... 91
6.1.6 Alarm Notification....................................................................................................................................................................................................... 91
6.1.7 Daisy Chain Calculator for PME ................................................................................................................................................................................... 91
7 IT Infrastructure ............................................................................................................................................................. 92
7.1 Supported Operating Systems and Other Software.................................................................................................................................. 92
7.1.1 Power Monitoring Expert 8.2 – Data Center Edition .................................................................................................................................................... 92
7.1.1.1 Application and Database Servers (Secondary Installs blocked in DC) .............................................................................................................. 92
7.1.1.2 Engineering Client ............................................................................................................................................................................................ 92
7.1.1.3 Microsoft Excel................................................................................................................................................................................................. 93
7.1.1.4 Supported Browser Versions for Web Clients .................................................................................................................................................. 93
7.1.1.5 Language Support in PME-DC 8.2 .................................................................................................................................................................... 93
7.1.2 PowerSCADA Expert 8.2 with Advanced Reports ......................................................................................................................................................... 94
7.1.3 StruxureWare Building Operation 1.9.x ....................................................................................................................................................................... 94
7.2 Server Specification ................................................................................................................................................................................. 95
7.2.1 Power Monitoring Expert Data Center Edition............................................................................................................................................................. 95
7.2.1.1 Systems with up to 50 Devices ......................................................................................................................................................................... 95
7.2.1.2 Systems with up to 250 Devices ....................................................................................................................................................................... 96
7.2.1.3 Systems with more than 250 Devices ............................................................................................................................................................... 96
7.2.1.4 PME Client (Engineering and Web)................................................................................................................................................................... 97
7.2.2 PowerSCADA Expert with Advanced Reports ................................................................................................................................................................ 97
7.2.3 StruxureWare Building Operation ............................................................................................................................................................................... 97
7.3 Hard Drive Sizing .................................................................................................................................................................................... 98
7.4 Server Virtualization................................................................................................................................................................................ 99
7.4.1 Virtual Machine Recommendations ............................................................................................................................................................................. 99
7.5 Network Switches ................................................................................................................................................................................... 99
7.5.1 Main Server Switch ...................................................................................................................................................................................................... 99
7.5.2 Switchboard Network Switches .................................................................................................................................................................................... 99
8 Commissioning Time Estimates .................................................................................................................................... 102
Appendix A: Description of Test System ................................................................................................................................ 104
Appendix B: How to calculate PUE ......................................................................................................................................... 104
Power Usage Effectiveness Calculations .............................................................................................................................................................. 104
Total Data Center Load .............................................................................................................................................................................................................. 104
Dedicated Data Center .......................................................................................................................................................................................................... 104
Data Center in a Mixed-Use Facility ....................................................................................................................................................................................... 104
IT Load ................................................................................................................................................................................................................ 105
Factored PUE Calculations ................................................................................................................................................................................... 105
Appendix C: Resources for Data Center Redundancy information.......................................................................................... 105
Appendix D: Example IT Power Distributions ......................................................................................................................... 105
Room PDU Distribution ........................................................................................................................................................................................ 106
In-Row PDU Distribution ..................................................................................................................................................................................... 107
PDU and RPP Distribution .................................................................................................................................................................................... 108
IT Panelboard Distribution .................................................................................................................................................................................. 109
IT Busway Distribution......................................................................................................................................................................................... 110
Appendix E: PME Hierarchy Configuration ............................................................................................................................. 111
Appendix F: PME DC/Standard Edition Differences ................................................................................................................ 112
References ............................................................................................................................................................................. 113
Terms and Definitions ............................................................................................................................................................ 114
1 Introduction
This design guide is intended to be used when designing or quoting StruxureWare™ Power Monitoring Expert,
StruxureWare™ Power Monitoring Expert Data Center Edition, StruxureWare PowerSCADA Expert with Advanced
Reports in a Data Center, and the Building Management System + Power Management offer. This is an internal
document and is not intended to be shown outside of Schneider Electric.
It is assumed that the reader understands how to quote a generic Power Monitoring Control System (PMCS). This
guide does not provide recommendations on protective devices for the purposes of protection. The focus will be
on the metering provided by these protection devices. The protection system should be designed by a qualified
engineer independent of this guide.
Sections that refer to “Power Monitoring Expert Data Center Edition” throughout the document also apply to
Power Monitoring Expert Standard Edition. For a list of the differences between PME Data Center Edition and PME
Standard Edition see Appendix F.
The Design Guide covers:
Architectures – Descriptions of Power Monitoring Expert Data Center (PME-DC) Edition, PowerSCADA Expert with
Advanced Reports in a Data Center, and StruxureWare Building Operation (SBO) with PME-DC or PSE with Advanced
Reports.
Design Considerations by Solution Module – Deep dive on the Data Center base and optional modules. How to select
the correct metering, per module, for a Data Center power system to ensure the correct measurements/inputs are
available for the software.
System Communication Design – Design considerations for real-time data and alarming performance.
IT Infrastructure – Server sizing based on the number of metering and protection devices. Supported Operating
System and SQL Server versions. Recommendations for server redundancy, RAID, and Hard-drive sizing.
Commissioning Time Estimates – Time estimates for commissioning tasks.
2 Data Center Power Management Architectures

2.1 Which Offer and Architecture Should I Choose?
The first step in designing a system is selecting either PME, PME Data Center Edition or PSE with Advanced Reports.
The following table provides a comparison between the two offers which should help guide the decision:
Functionality PME / PME-DC PSE with Advanced Reports
Real Time Screen Update Time ≤ 4 seconds* ≤ 2 seconds
Alarm Response and 30 Second Alarm Display / 2 to 10 second Alarm Display possible /
Basic Alarm Management / Advanced Alarm Management / Active
Management Alarm Tab for Viewing * Alarms in all Views
Limited Graphics Flexibility / Data

Enhanced Graphics
Graphics Functionality Center Templates provided / No One- Flexibility / Animated One Lines
Line Animation
System Redundancy No Redundancy Native PSE Redundancy
Major changes and Meter Adds while Major Changes Require shutting runtime
System Modifications system remains connected to devices down. Redundant systems remain online
“SER Lite” – No Device Time Accuracy “Full” SER – Includes Time Accuracy Flag
Sequence of Events Recording Flag in Software in Software
Modbus, ION, OPC Modbus, ION, IEC61850, DNP3, IEC60870-

Protocol Support Optional SNMP through KEPServerEX 5-104, OPC, SNMP, BacNet, and KNX
Power System Control No Yes
*See Appendix A for more information on the Ethernet devices outlined in the Data Center Reference Design
and Test System.
PME, PME-DC and PSE with Advanced Reports can be integrated with SBO. Regardless of the offer and
architecture selected we deliver the same value to the customer through the base and four optional
solution modules:
The details of the base and each optional module are covered in the “Design Considerations by Solution
Module” section.
Note: It is possible to build a Data Center solution using the Standard Edition of PME. For a list of the
differences between PME Data Center Edition and PME Standard Edition see Appendix F.
2.2 Part Name to Solution Module Mapping

Most of the functionality described in the “Power Monitoring and Control (Base)” section is unlocked
through specific meter selection, and the base licenses for PME or PME Data Center Edition, and PSE
with Advanced Reports.
The following table lists the recommended part references for the base and optional solution modules
for the Data Center offer:
Solution Module Corresponding Part Reference Description
“SNMP OPC Server” (optional)

Base “Event Notification Module” (optional)
PowerSCADA Anywhere is ordered as part of PSE (optional)
“Generator Performance Module”

Equipment Performance “Breaker Performance Module”
“Power Efficiency Module”

System Efficiency “Energy Analysis Module”
Capacity Management “Power Capacity Module”
IT Billing “IT Billing Module”
“EPSS Module” and “UPS Performance Module” are not recommended in data centers. “EPSS
Module” offers the same functionality that is available in the “Generator Performance Module”.
The “UPS Performance Module” was designed for the healthcare segment and does not apply to
data centers.
2.3 Power Monitoring Expert Data Center Edition

2.3.1 Software Architecture
To speed commissioning and help standardize deployments we have made available data center specific
real-time screen templates and graphics, data center reports, and the ability to export data to Schneider
Electric’s StruxureWare Data Center Operations.
In PME 8.2 and PME-DC 8.2 the user will view all information through PME applications:
User Views
SNMP
Real Time One-line Real Time
Reports Dashboards Alarms Waveform SER ENM Device
Information Diagrams Trend
Support
SER Light - Supported +
PME
Vista / WebReach / Vista / PME Alarm/Event Possible
Vista / WebReach PME/Web PME/Web Event/Alarm PME/Web KEPServerEX
Real Time Tables WebReach Logs (no Time Embedded
Log
Quality column) Config View
2.3.2 Server Architecture (server specs provided in IT Infrastructure section)

The recommended server architecture for PME-DC is a single physical server or virtual machine:
In previous versions of PME-DC, Avance or everRun was recommended if server level hardware
redundancy was required. Limitations were found with disk I/O that impacted system performance. As a
result, if redundancy is required, PSE with Advanced Reports should be specified.
2.4 PowerSCADA Expert with Advanced Reports

2.4.1 Software Architecture
In PSE 8.2 the user views information through the following:
User Views
SNMP
Support
PME Web PSE Waveform SER Full – Supported +
PME Dashboards
PSE animated one- Reports Viewer / PME PSE Event Log Embedded Native in
PSE Graphics Screens integrated into PSE Alarm Log PSE Trending
lines integrated into Integrated PQ (Time Quality Config View in PSE
PSE Runtime
PSE Runtime Reports column supported) PSE
Notes about the combined system:
• All devices are added to PSE for real-time data and alarms.
• PME connects to devices with waveform data used in Power Quality (PQ) Reports (ION 7650
and PM8000), multi-circuit meters that feed the PME data center hierarchy (BCPM, iBCPM,
PM5350 IB/PB), any Devices used as part of PUE calculations in the VIP, and Micrologic Trip
Units when used with the optional breaker performance application module.
• In some cases, PME can also serve Diagrams for multi-circuit meter devices to simplify PSE graphics.
2.4.2 Server Architecture (server specs provided in IT Infrastructure section)

A basic redundant architecture for PSE with Advanced Reports is recommended. Separate servers should be
used for each software:
2.5 Building Management System + Power Management

The StruxureWare Building Operation (SBO) + PSE with Advanced Reports, SBO +PME and SBO + PME-DC
offers provide an advanced monitoring solution that combines both electrical and mechanical systems.
2.5.1 Software Architectures

2.5.1.1 PSE with Advanced Reports + SBO
*For a summary of what devices are added to PME and what devices are added to PSE see the notes in the
“Software Architecture” section of the “PowerSCADA Expert with Advanced Reports” section above.
In a combined SBO + PSE with Advanced Reports system the user interacts with the following:
User Views
SNMP
Support
SBO Graphics Screens SBO
for “Macro” level real- PME Dashboards aggregates
Animated one- Reports Viewer / PME PSE Event Log Embedded Native in
times integrated into Alarms from SBO Trending
lines in PSE integrated into Integrated PQ (Time Quality Config View in PSE
(data from PSE EWS) SBO or PSE PME and PSE
SBO Reports in SBO column supported) PSE
through EWS
2.5.1.2 PME-DC + SBO
In a combined SBO + PME or SBO + PME-DC system the user interacts with the following:
User Views
SNMP
Support
SBO Graphics Screens SBO SBO through
SBO Graphics PME Web SER Light - Supported +
(data from PME EWS PME Dashboards aggregates integrated PME
(data from Reports PME Alarm/Event Possible KEPServerEX
Server and PME device integrated into Alarms from Reports and SBO Trending
PME EWS integrated into Logs (no Time Embedded in PME
diagram integration) SBO PME through Device
Server) SBO Quality column) Config View
EWS Diagrams
2.5.2 Server Architectures (server specs provided in IT Infrastructure section)
1) In the combined PSE with Advanced Reports + SBO architecture we recommend a dedicated
server for each software:
2) PSE with Advanced Reports can be installed in a redundant setup as well. There could be four or more
servers/virtual machines in this architecture:
3 Reference Architecture
This section of the design guide describes our data center reference architecture that will be used as an
example throughout the document when discussing the design of the system.
We provide tables that list the metering types used, but for a complete reference, see the tables in the
“Summary of Metering by Solution Module” section.
3.1 Overview
The following is a block diagram for the example data center. We will go into detail on the medium voltage
substation, Data Halls one, two, and six, and each of the different IT distributions in the Data Halls:
Data Halls 1 through 5 have redundancy. Data Hall 6 does not have redundancy.
In Data Halls 1, 5, and 6 the IT distribution is Busway. Data Halls 1 and 5 use Busway metering while Data Hall 6
uses RackPDUs.
Data Halls 2, 3, and 4 use PDUs at the IT distribution level but vary in the type of branch circuit metering used.
A PDF of the complete architecture is provided with this design guide if you would like to zoom in and see
additional details.
3.1.1 Medium Voltage Substation
The hardware icons in the image above represent the following meter types:
Abbreviation Display Icon Meter Type
ION 7650
PQM
PM8000
RLY Sepam Series 40
The substation feeds five MV Transformers on side A and five on side B. A normally open tie breaker
separates the two sides and would close in the event of a utility outage. This transfer scheme is controlled
by the ATS controller.
Each MV Transformer steps the voltage down from 12,470-480Y/277 Volts.
3.1.2 Data Hall 1
Data Hall 1 is fed from Transformers 1A and 1B. The Data Hall contains main switchboards on both sides.
Each main switchboard has a utility and generator incomer, and feeder breakers for the each 600kW IT UPS,
Mechanical Switchboards, House Loads Panel, and Computer Room Air Handler (CRAH) Unit distribution
panel. The IT UPS feeds the Critical Bus switchboard. This switchboard feeds the IT load.
The IT design capacity for this Data Hall is 2400 kW. The IT redundancy is 2N with an IT usable capacity of
1200 kW, this way the side A or side B MV transformer could supply both sides during an outage.
Also, note the location of the six LV Transformers directly above the Critical Bus switchboards. These
transformers step down 480V to 410V.
The Mechanical Main Switchboards on side A and side B feed Mechanical UPSs that supply power to chiller
controls. The UPS keeps the controls active during the delay between utility and generator. So, the entire
mechanical load is not supported by UPS, just the controls.
3.1.3 Data Hall 1 IT Distribution
Busway Distribution is used in Data Hall 1. There are ten 400A busway runs on side A and ten on side B. In each
400A run there is an end tap box and eight Plug-In Units. An IT rack in this Data Hall would be dual cord fed
from a side A and side B tap can. All circuits in this Data Hall are 1 pole.
3.1.4 Data Hall 2

With the exception of the location of the LV transformers, Data Hall 2 is virtually identical to Data Hall 1:
PQM PM8000
Micrologic 6.0 P
TU
Micrologic 6.2/6.3 E
Symmetra MW
EM
Smart-UPS VT
The LV transformers are found in each PDU (seen at the IT Distribution level in the next section). The purpose
in this variation from Data Hall 1 is to show variety in the types of electrical design that could be found in the
field. With LV transformers in each PDU it significantly increases the number of transformers required, but this
is a typical PDU configuration for the ANSI market.
PM PM5320
- BCPM-E
*Line side of PDU transformers are metered for capturing LV transformer losses. An enhanced Enercept meter could be substituted for
line side meter if desired.
Data Hall 2 has ten side A PDUs (top row) and ten side B PDUs (bottom row). Each PDU contains a
transformer that steps down 480V to 410V LL / 230V LN. Racks in this Data Hall are dual corded and each
rack is fed from a 1-pole circuit on a panel in a side A PDU and a 1-pole circuit from a panel in a side B PDU.
A Veris BCPM-E 84 is used to monitor circuit level data on two 42 circuit panels in each PDU.
3.1.6 Data Halls 3 and 4

Data Halls 3 and 4 are identical to Data Hall 2.
PM PM5320
- EnerSure iBCPM
*Line side of PDU transformers are metered for capturing LV transformer losses. An enhanced Enercept meter could be substituted
for line side meter if desired
The LV transformers in Data Hall 3 PDUs step 480V down to 208V LL / 120V LN. The IT Racks in this data hall are
dual fed from 2-pole circuits, one from a side A PDU, and one from a side B PDU.
An 84 circuit TrendPoint iBCPM is used to monitor circuit level data on two 42 circuit panels in each PDU.
PM PM5110
- BCPM-A
*Line side of PDU transformers are metered for capturing LV transformer losses. An enhanced Enercept meter could be substituted
for line side meter if desired.
The LV transformers in Data Hall 3 PDUs step 480V down to 208V LL / 120V LN. The IT Racks in this data hall
are dual fed from 1-pole circuits, one from a side A PDU, one from a side B PDU.
A Veris BCPM-A 84 circuit is used to monitor circuit level data on two 42 circuit panels in each PDU.
3.1.9 Data Hall 5
Data Hall 5 is fed from side A MV Transformer 5. The redundancy in this Data Hall is N+1 as we have an IT design
capacity of 1200kW but we assign an IT usable capacity of 600kW. This means we can lose one IT UPS (each rated
a t 600kW) and still support the full IT load.

Data Hall 5 has ten 400A Busway runs:
In each 400A run there is an end tap box and eight Plug-In Units. An IT rack in this Data Hall would only be
single fed from a 1-pole circuit in one of the Plug-In Units.
3.1.11 Data Hall 6

Data Hall 6 is identical to Data Hall 5 only it is fed from Side B MV Transformer 6. The IT usable capacity in this
data hall is 1200kW instead of 600kW which makes this Data Hall non-redundant.
Data Hall 6 uses ten 400A Busway runs only the metering is with RackPDUs. Each Plug-In Unit is a 3-pole
breaker so per Busway run you would have 8 rack PDUs with three phase power available. Racks are single
corded; therefore, each IT Rack has 1 RackPDU.
3.2 Power Equipment Description

The basic functionality of each piece of power equipment is described below:
Medium Voltage Substation and MV Transformers

The Utility MV Switchgear (also referred to as a Medium Voltage Substation) is the top level power distribution
component. MV Switchgear lineup has two incomers (incoming utility feeds). This is to accommodate feeds from
multiple Utilities. Although this is a possible scenario it is not necessarily common to all data centers worldwide.
Regardless of the feed topology, the primary purpose of this set of switchgear is to provide power to the MV
Transformer.
The MV Transformer converts the 12.470V 3P,3W primary voltage to 480Y/277V, which is the low voltage
distribution level for this ANSI based design.
Unit Substation
A Unit Substation is a packaged Medium Voltage Disconnect, Medium Voltage to Low Voltage Transformer, and LV
Switchboard. While not found in the ANSI reference architecture, a unit substation is referenced in this design
guide.
Generator and Generator Switchboards

Backup generators are essential to ensuring availability of power to the IT loads of a data center. In the case of a
catastrophe the backup generators must be ready to pick up the load. As such, they must have a reliable
monitoring and control system.
The control of the generators is managed by the generator controller, and the metering and protection is usually
accomplished with an ION7650 and Micrologic trip unit.
Load Bank
A Load Bank is used to simulate a load for a power source. They are mainly used when testing power equipment.
In our example data center, the load bank is used to load the generators during test.
Main LV Switchboards
Once the voltage has been transformed to the low levels (< 600V) it can be distributed throughout the facility.
The Main Switchboards are critical components of the electrical distribution system and provide power to the IT
loads, Mechanical loads, and auxiliary loads. The size of the switchboards depends on the size of the facility and
redundancy design.
IT UPS Input Switchboards

Some data centers may have an IT UPS input switchboard which is used for distributing the UPS supply into the 3
different feeds: Main UPS, Static Bypass Switch and manual bypass.
IT UPS
The IT UPS is used to protect IT loads from momentary power disruptions (carry the load until the generators can
come on). They also condition the power being delivered to the IT load.
IT UPS Output Switchboards (Critical Bus Switchboard)

Once the power has been transformed and conditioned by the UPS, or the UPS has been bypassed, it is fed to the IT
UPS Output Switchboard. The purpose of this switchboard is to distribute the UPS power to each of the IT loads. In
this architecture, there are three possible sources of power. The first is the main output of UPS 1, the second is the
main output of UPS2, and the third input is the manual bypass which is used to completely bypass the UPS unit when
it needs maintenance or is otherwise unavailable.
Power Distribution Units (PDUs)

A Power Distribution Unit (PDU) is a specialized low voltage panelboard for distributing electrical power
to IT racks. A PDU is specifically built for data center environments in terms of power capacity, features,
and form factor.
Mechanical UPS Switchboard (Input and Output) + Mechanical UPS

The main purpose of having a mechanical UPS is to ensure the critical cooling loads such as Computer
Room Air Conditioners (CRACs) and Computer Room Air Handlers (CRAHs) stay powered during system
events. These units provide precise temperature and humidity control for mission critical environments
and so any disturbance to their supply power could negatively affect the operation of the facility.
Our reference design does not use an input or output mechanical UPS switchboard.
Mechanical Switchboard
A mechanical switchboard is used to distribute power to the various mechanical loads throughout the
facility. This includes chillers, Heating Ventilation and Air Conditioning (HVAC) units, compressor,
Computer Room Air Conditioners (CRACs) and Computer Room Air Handlers (CRAHs).
Auxiliary Switchboard
The auxiliary switchboard is used to power miscellaneous loads throughout the facility such as generator control
panels, building lights, and any other loads that typically are not mission critical.
3.3 IEC Consideration

For illustration purposes, we have used an ANSI architecture with varying IT distribution types. In IEC switchboards,
it is common to use disconnect switches where circuit breakers would be used in ANSI. With disconnect switches
there is no opportunity for monitoring the electrical circuits from a trip unit. In the metering selection section this
should be considered where trip units are specified. For an IEC design, a power meter that provides the same
metering as the specified trip unit should be selected.
4 Design Considerations by Solution Module

This section of the design guide describes the Data Center base and optional modules in detail and helps
select the necessary metering for each. We recommend specific meter types but also list the measurements
required for users that want to verify that another meter type provides the necessary data for the
application.
The data center reference architecture will be used to illustrate how metering should be assigned. The
reference architecture provides a reference point from which adaptations can be made, regardless of the
size of the data center.
This section should be used to design metering for a complete system as opposed to an individual
module. You risk losing functionality of the complete system if designing in isolation. For example:
• In the “Utility MV Switchgear” we recommend using Sepam T42s to monitor and protect the MV
circuit breakers. Although another type of relay would work, the “T” provides temperature
monitoring of the MV Transformer, which is an important alarming point in our example system.
• Selecting a meter that does not provide PQ data when PQ reports are required.
4.1 Summary of Metering by Solution Module

The tables in this section provide a quick overview of the metering points required for the base and each
solution module. General device types for UL/NEMA and IEC are also provided for quick reference.
Detailed sections describing the base module, each optional module, the meter types, and measurements
required can be found immediately after this summary section.
BASE OPTIONAL SOLUTION MODULES
Equipment System Capacity

IT Billing
Performance Efficiency Management
Power Usage Effectiveness

Generator Performance
Energy by IT Customer
Breaker Performance
Power System Losses
Branch Circuit Power

METERING Power Monitoring
POINT and Control
Generator Power
Energy Analysis
Billing Module
UPS Power
Medium Voltage Substation X1 X X X6 X X X
MV Transformer X1 X6
Generator Switchboard X1 X X6
Main LV Switchboards X1 X2 X7 X X6
IT UPS Input Switchboard X1 X X6
IT UPS X1 X3 X X6 X
IT UPS Output Switchboard X1 X7 X X6
PDUs or Busway X1 X4 X6 X X X
Mechanical UPS Switchboard X1 X5 X6
Mechanical UPS X1 X X6
Mechanical Switchboard X1 X6
Auxiliary Switchboards X1 X6
1. Each customer will have different real-time monitoring requirements so the base module does not require
metering in all locations. For a complete monitoring system it is recommended.
2. If there is no generator switchboard, the correct metering must be selected in the main LV switchboard.
3. Our recommended architecture includes metering at the UPS and Busway level. If your architecture does not
include metering at the UPS level, you must provide a meter at the main of the IT UPS Output Switchboard.
4. Our recommended architecture includes Metering on each IT PDU. If your architecture uses Busway or RPPs then
you must meter accordingly.
5. Monitoring required in this Power Equipment if the Mechanical UPS does not include metering functions.
6. Metering not necessary in all locations. However, a complete monitoring system is recommended for use with the Reports
in this application module.
7. In addition to Micrologic Trip Units, a specific list of supported circuit breakers is required. The supported list of breakers can be
found in the “Breaker Performance” section of the Application Modules configuration guide available on the Exchange
Community.
General recommendation of device types used for metering and protection - UL/NEMA:
UL/NEMA
Power Equipment Device Type Device Models Location in system
(or equivalent)
Utility MV Switchgear Digital Power Quality Meter Schneider Electric ION7650 MV Mains
Generator MV Switchgear Digital Relay Schneider Electric SEPAM MV Mains
Digital Power Quality Meter Schneider Electric PM8000 MV Feeders
Digital Relay Schneider Electric SEPAM MV Feeders
Sequence of Events I/O Cyber Sciences SER 3200 n/a
Unit Substation Digital Temperature Controller Schneider Electric Model 98 MV Transformer
Digital Trip Unit Schneider Electric PM8000 LV Main
Digital Trip Unit Schneider Electric Micrologic 6.0 P LV Main / Tie / Feeders
Generator Generator Controller 3rd Party Generator
Generator LV Switchboard Digital Power Quality Meter Schneider Electric ION7650 LV Mains
Digital Trip Unit Schneider Electric Micrologic 6.0 P LV Mains / Tie / Feeders
Load Bank LV Switchboard Digital Trip Unit Schneider Electric Micrologic 6.0 P1 LV Mains / Feeders
IT UPS Input LV Switchboard Digital Power Quality Meter Schneider Electric PM5110 / PM53202 LV Main
Digital Trip Unit Schneider Electric Micrologic 6.0 P LV Feeders
IT UPS Module Embedded Power Meter Schneider Electric UPS UPS
IT UPS Output LV Switchboard Digital Trip Unit Schneider Electric PM8000 LV Mains / Tie
Digital Power Meter Schneider Electric PM5110 / PM53203 LV Feeders
Critical Power Path (PDU, RPP, IT Sequence of Events I/O Cyber Sciences SER 3200 n/a
Busway)
Power Distribution Unit (PDU) Digital Power Meter Schneider Electric PM5110 / PM5320 LV Transformer (pri)
Digital Branch Circuit Meter Schneider Electric BCPM “E” model4 LV Panels + Branch Circuits
Remote Power Panel (RPP) Digital Branch Circuit Meter Schneider Electric BCPM “E” model LV Branch Circuits
IT Busway Digital Power Meter Schneider Electric PM5350 LV Feeder
Digital Power Meter Schneider Electric PM5350 (busway) LV Tap Box
Mech. UPS Module Embedded Power Meter Schneider Electric UPS UPS
Mech. UPS Output LV Digital Power Quality Meter Schneider Electric PM8000 LV Mains / Tie
Switchboard Digital Power Meter Schneider Electric PM5110 / PM53203 LV Feeders
Mech. Distribution LV Digital Trip Unit Schneider Electric Micrologic 6.0 P LV Main / Tie
Switchboard Digital Power Meter Schneider Electric PM5110 / PM53203 LV Feeders
Notes:
1. Alternative metering options for load bank LV Switchboards:
• Schneider Electric PM5110 / PM5320
2. Alternative metering options for the IT UPS Input LV Switchboard:
• Schneider Electric PM8000
3. Alternative metering options for LV Switchboard Feeders:
• Schneider Electric Enercept (ideal for retrofit applications)
• Schneider Electric Micrologic 6.2 E trip unit (viable if the expected load doesn’t drop below 20% of breaker frame rating)
4. Alternative metering options for metering the secondary side of the LV transformer and the output breakers for data centers that use
a “gallery design” for PDUs:
• Schneider Electric EM4800
• Schneider Electric MCM
General recommendation of device types used for metering and protection - IEC
IEC
Power Equipment Device Type Device Models Location in system
(or equivalent)
Utility MV Switchboard Digital Power Quality Meter Schneider Electric ION7650 MV Incomers
Generator MV Switchboard Digital Relay Schneider Electric SEPAM MV Incomers
Digital Power Quality Meter Schneider Electric PM8000 MV Feeders
Digital Relay Schneider Electric SEPAM MV Feeders
Generator Generator Controller 3rd Party Generator
Main LV Switchboard Digital Power Quality Meter Schneider Electric PM8000 LV Incomers / Tie
Digital Trip Unit Schneider Electric Micrologic 6.0 P LV Incomers
Digital Trip Unit Schneider Electric Micrologic 6.0 P Tie / Feeders
IT UPS Input LV Switchboard Digital Power Quality Meter Schneider Electric ION7550 LV Incomers
IT UPS Module Embedded Power Meter Schneider Electric UPS UPS
IT UPS Output LV Switchboard Digital Power Quality Meter Schneider Electric PM8000 LV Incomers / Tie
IT Panelboard Digital Power Quality Meter Schneider Electric iEM 3X50 LV Incomers / Tie
Digital Branch Circuit Meter Schneider Electric BCPM “E” model LV Branch Circuits
IT Busway Digital Power Meter Schneider Electric PM5350 LV Feeder
Digital Power Meter Schneider Electric PM5350 (busway) LV PIU
Mech. UPS Module Embedded Power Meter Schneider Electric UPS UPS
Mech. UPS Output LV Switchboard Digital Power Quality Meter Schneider Electric PM8000 LV Incomers / Tie
Mech. Distribution LV Switchboard Digital Power Quality Meter Schneider Electric ION7550 LV Incomers / Tie
Notes:
1. Alternative metering options for the LV Switchboard Feeders:
• Schneider Electric Micrologic 6.1 / 6.2 E trip unit (viable if the expected load doesn’t drop below 20% of breaker frame rating)
4.2 Power Monitoring and Control (Base)
4.2.1 View Real-Time Power System Status and Trends

4.2.1.1 Power Monitoring Expert Data Center Edition
StruxureWare PME-DC installs a variety of Vista diagram templates that can be used as a starting
point for building real-time data screens. See “Design Requirements” in the “Vista Screens”
section of the PME-DC Edition Commissioning Guide for more detail on the Vista template screens
available. IEC one line templates only are available currently. A few example templates are shown:
KPI Templates – The KPI template screens can be linked to the logical devices created as part of
commissioning the Data Center VIP. There is a main summary screen which links to detail pages for PUE
and Power Loading.
Electrical One-line – The one-line templates provide a starting point for building out real-time data
screens that represent the customer’s electrical one-line diagram. The one-line templates must be
linked to registers, device diagrams, and/or equipment screens. 5 Templates are provided: Main
Overview, Genset Switchboard, Mechanical Distribution, Mechanical/IT UPS + Auxiliary, and IT UPS
Output. Only IEC one-line templates are provided; however, we do provide ANSI symbols which can be
swapped into the IEC one-line templates.
Equipment Details – Display the details pertaining to each piece of equipment monitored in the system.
Templates are available for a Main Overview, MV Switchgear, LV Switchgear, Generators, PDUs, UPSs,
Transformers, etc.
Alarm Status Panel – The Status Panel provides a graphical overview of the operating state of the electrical
system. To notify of a problem, a status object is used in Vista that will turn red. The user can click on the
alarm to go to the equipment details page for that piece of equipment.
Default device diagrams and an extensive graphics library are also included to help build out real-time data screens in
PME.
Dashboards, Real-Time Tables, and Real-Time Trending are also part of the real-time data features in PME-
DC web applications:
Dashboards:
Real-Time Tables:
Real-time trending:
The real-time trending in PME-DC provides continuous updates and can provide 90 days’ worth of data. There are
tools for creating thresholds and data labels as well.
4.2.1.2 PowerSCADA Expert with Advanced Reports

The real-time data screens and animated one-line graphics are built according to the
customer’s one-line diagram. Template graphics screens are not provided. An example of a
PSE real-time screen with animated one-lines and a device popup:
Device popups are included in PSE 8.2 for certain device types and provide more real-time
information for a particular meter.
PME Device diagrams can be integrated into PSE graphic screens for devices that have been added to
PME or PME-DC. This is useful when there is no PSE device popup available for a certain device type or
when “drill down” views for additional details such as ad-hoc trends are desired (access to data log
viewers to trend historical data).
LiveView, available in a web browser, provides data tables based on trend data. There are 14 preset tables and the
user can configure additional tables.
And finally, Dashboards from PME or PME-DC can be integrated into PSE runtime screens:
4.2.1.3 Recommended Meter Types

Each customer will have different real-time monitoring requirements; however, the tables in the “Summary of
Metering by Solution Module” section provides the recommended types in ANSI and IEC. There should be
monitoring in each piece of power equipment.
4.2.1.4 Required Measurements

Any measurement or status provided by a meter can be displayed in a real-time interface.
4.2.2 Analyze Power System Events

Alarm and Event Analysis is core functionality offered in PME and PME-DC 8.2. This is found in the Alarms section
of the Web Interface:
The Alarm and Event Viewer should display a complete list of all alarms and events.
For data centers, high priority alarms from a PLC can be sent out for notification through ENM but they
should also be configured by using a setpoint module in the VIP to appear in the Alarm and Event viewer.
Where this gets a little complex is if, for example, a Micrologic Trip Unit is also reporting a breaker
open/close alarm in PME for a breaker that is also wired to the PLC for high speed notification. In this case,
no setpoint module would be needed in the VIP, otherwise the user would see this event twice.
Alarms may also have to be configured using setpoint modules in the VIP for any UPS, PDU, or Generator etc.
Without the setpoint in the VIP, only status objects would change in real-time screens and there would be no
historical log for the alarm.

An Alarm Log and Event Log can be built into the PSE project runtime screens. Device Profiles need to be
created at commissioning time with all the desired alarms and events.

Metering should be included in each piece of power equipment in the architecture to provide alarm and event
analysis. Each device type has its own set of alarms and events that can be configured on the device or in the
software and pulled into the Alarm and Event viewer.
PME-DC and PSE with Advanced Reports can provide the Sequence of Events Recording (SER) application
which provides millisecond resolution accuracy of events. See the “Sequence of Events Recording” section
on the next page for design considerations.
Note: The MES114 module must be specified for all Sepam devices to accept the 1per10 time sync signal
from the STR-100. The MES114E and MES114F modules will not work as they do not accept 24V DC which is
the output voltage for the 1per10 signal from the STR-100.

Alarms – like Voltage Sags or Swells, Over/Under Current, or Communication Loss – are just a few examples of
information customers may want to see in the Alarm and Event Viewer.
4.2.2.5 Sequence of Events Recording (SER)

SER is the event log viewer in either PME/PME-DC or PSE with Advanced Reports with specific meters
assigned throughout the power system, all time synchronized from a GPS clock and time sync network.
The difference between SER in PME/PME-DC and PSE with Advanced Reports is that the event log in PSE
supports the time quality flag that can be associated with a digital input event. Devices that provide the
time quality flag are the ION 7650 with firmware version v373, the SER 3200 and the SER 2408. It is
important to note that the time quality flag is not logged with a power quality event such as a sag or
swell. This is specifically for status alarms wired to digital inputs. However, if the 7650 or PM8000 is
being time synchronized accurately PQ events should be to the millisecond, there will just be no
indication of the amount of time drift on the event.
Sample PME Event Log:
Sample PSE Event Log:
Note the “Clock In Sync” message that is reported in the Time Quality column above. “No Time Sync
Information” is displayed in this column for digital input events from the PM8000 as time quality is not
supported in this device yet.
We will discuss an example SER design as it relates to our reference architecture. Note that Cyber
Sciences provides many useful Technical Notes around system design. Visit http://www.cyber-
sciences.com/ and see the “Support” > “Tech Library” section. TN-101 “SER System Architectures” is a
good starting point.
Key design topics are:
• Determine the required status inputs for critical points in the power distributions system. Typical
status points can include circuit breaker auxiliary contacts, alarm contacts, protective relay
auxiliary contacts, breaker control switches and breaker rack out status.
• Select the correct metering types and determine the time sync protocol that each meter uses.
• Ensure the correct number of digital inputs is available for the number of breakers to be
monitored.
• Select the correct cable for each time protocol.
4.2.2.6 SER Recommended Hardware and Meters

SER is a very specialized design; it is best to validate any design decisions directly with Cyber Sciences.
The “SER Wiring and IO points” document contains the details of the SER design as it would apply to the
reference design. The following meter and hardware recommendations apply to that design specifically but
provide a base from which adaptations can be made.
TM
Trimble Acutime GG Smart GPS Antenna:
Available from Schneider Electric or directly from Trimble. Provides STR-100/IRIG-B with GPS time sync signal. The
Antenna must be mounted where it can see at a minimum 4 satellites. A lightning arrestor is also recommended.
More information can be found on Trimble’s website. The cable for the antenna must also be purchased from
either Schneider Electric or Trimble. The cable comes in varying lengths depending on the mounting location.
Ideally, only one antenna is needed that can feed a master STR-100 that can be daisy chained to other STR-100s.
STR-100:
Available from Schneider Electric or Cyber Sciences. Used to provide the 1per10 time sync signal to Sepams.
*Each STR-100 is rated at 36W and requires a Class 2, 24Vdc power supply
STR-100/IRIG-B:
Available from Cyber Sciences only. Acts as master clock in our design and is daisy chained to other STR devices.
This device also provides 24V IRIG-B output for longer distance wire runs to the STR-IDM modules.
*Each STR-100/IRIG-B is rated at 36W and requires a Class 2, 24Vdc power supply
STR-IDM:
Available from Cyber Sciences only. Used for 24Vdc IRIG-B time sync signals over longer distances. In our
reference architecture, there is roughly one STR-IDM per piece of switchgear. This allows the 5Vdc IRIG-B signal
at the output of the STR-IDM to be run over shorter distances.
*Power is supplied from the STR-100 so no additional power supply is required.
SER-3200:
Available from Cyber Sciences only. Found in each main switchboard, this device provides 32 digital inputs for
alarming different circuit breaker contacts. A 5Vdc IRIG-B time sync signal is fed to the SER-3200 from an STR-IDM
module through an EZC-IRIG-B connector.
*Each SER-3200 draws roughly 10W so a 24Vdc power supply is required
SER-2408:
Available from Cyber Sciences only. This device is only used in the MV Sub to provide the ASCII RS-485 output
time sync signal to the ION 7650s. This signal is fed into either COM1 or COM2 on the ION 7650. Each SER-2408
accepts 5Vdc IRIG-B through the EZC-IRIG-B connector.
*Each SER-3200 draws roughly 10W so a 24Vdc power supply is required.
EZC-IRIG-B:
Available from Cyber Sciences. This is a small connector required to wire the 5Vdc IRIG-B time sync signal to an
SER 3200 or SER-2408 device. One connector required per SER-3200 or 2408.
4.2.2.7 Time Sync Protocols and Required Cables
ION 7650 – Uses ASCII, over RS-485. Time Synchronized through a COM port configured as GPS Arbiter.
PM8000 – Uses Unmodulated 5Vdc IRIG-B time protocol. A digital input on the meter is required for the time
sync signal.
Sepam S42 – Uses 1per10 time sync protocol wired to Logic Input I21 on the relay. See Cyber Sciences TN-104.
See TN-101 on the Cyber Sciences web site for a summary of time sync protocols and their corresponding
cables. A screenshot from this web site is provided here:
4.2.2.8 Suggested Breaker Contacts
For all LV Breakers, the customer could monitor the following contacts with 6 digital inputs: OPEN, CLOSED,
TRIPPED, Connected (CE), Disconnected (CD), and Test
For all MV Breakers the customer could monitor the following contacts with 7 digital inputs: OPEN, CLOSED,
TRIPPED, Connected (CE), Disconnected (CD), Test, and Breaker Control.
See “SER Wiring and IO points” available on the Exchange Community for details.
In the Data Center Reference Design, in the medium voltage substation, we would need to ensure there are
enough digital inputs to monitor:
13 Circuit Breakers * 7 contacts per breaker = 91 alarm points
There are 8 digital inputs on both 7650s (16 digital inputs total) and 3 on each PM8000 (10 * 3 = 30 digital inputs
total). Considering one digital input on each PM8000 is required for the time sync signal there are only 20 digital
inputs available.
There are 24 digital inputs available on the SER-2408 as well but we still fall short of 91. I/O cards will need to be
added to the ION 7650s or the PM8000s but remember the time quality flag is only supported on the SER devices
and ION 7650s with firmware version v373.
4.2.3 (Optional) Get Power System Alarm Notifications

The Event Notification Module (ENM) should be installed on the same server as PME or PME-DC.
The goal should be to minimize the number of alarms configured in ENM to only the critical alarms wired to
an alarming PLC or Ethernet connected meters. The customer may also want to be notified of the following
alarms as well:
• Summary Alarms from the VIP

• Software Alarms from the PME Alarm Configuration setup
The orange path highlights PLCs, Ethernet devices, and branch circuit meters that will log events to the PME
EventLog2 database and use the alarm proxy service to trigger notification in ENM.
The blue path highlights software alarms configured in PME that are inserted directly into the database by
the ION Software Alarm Service.
The red path above represents summary alarms generated using a VIP framework available in PME-DC.
These events are logged to the PME database and sent to ENM through the alarm proxy service.
When an event is written to the database in PME and detected by ENM a notification is triggered. ENM has
filtering to ensure only events of interest are noted. This method has the advantage of not generating any
extra data traffic on the communications system(s). The disadvantage is that ENM can only detect events
after they are written into the database. The PME service that performs this is the Log Inserter service and
is configured by default to poll a device every 30 seconds for new events. That means the worst-case delay
from an event occurring to the notification being launched is slightly greater than 30 seconds.
For alarms that need to be available for the notification system in at least 10 seconds, ENM should be used with alarming in
PowerSCADA Expert.

In PSE with Advanced Reports, two redundant PSE servers could be used. If so, two ENM licenses are required
for a redundant ENM setup. SQL 2014 Express is included with ENM and would be installed on both PSE servers.
The following figure shows the recommended setup:
Note that ENM will failover to the standby ENM if the PSE primary fails, but software redundancy in ENM itself is
not supported at this time.
4.2.3.3 Recommended Alarm Points

The critical alarms we recommend in our Reference Architecture can be found in the “Data Center Reference
Design - Alarm List” spreadsheet found on the Schneider Electric Exchange Community.
4.2.4 Analyze Power Quality Issues

Power Quality Analysis contains the seven PQ reports offered in PME:
• EN50160:2000
• EN50160:2000 Mains Signaling
• EN50160:2010
• EN50160:2010 Mains Signaling
• IEC61000-4-30
• Power Quality
• Harmonic Compliance

The same reports listed above can be integrated into PSE runtime screens using the Cicode functions available in
PSE 8.2 for integrating PME web reports. The devices must be added to PME in addition to PSE for data logging
purposes.
4.2.4.3 Required Meter Types and Frameworks

An ION 7650 or PM8000 with the appropriate PQ framework must be used for these reports to have the
necessary logged data.
All necessary frameworks for both meters are provided in the …<PME install directory>\Schneider
Electric\Power Monitoring Expert DC Ed\config\fmwk\nd folder.
The framework files for the PM8000 and ION7650 with “519” in the title of the fwn are compatible with the
Harmonic Compliance report and Power Quality Report only.
The framework file for the PM8000 with “PQ” in the title of the fwn is compatible with the two EN50160:2010
reports, the Power Quality Report and the 4-30 report.
The framework file for the ION7650 with “PQ” in the title of the fwn is compatible with the two EN50160:2000
reports, the Power Quality Report and the 4-30 report.
To summarize:
Report
EN50160 2000 EN50160 2010 Basic Power Quality 4-30 Harmonics Compliance
7650 – PQ Yes** Yes* Yes Yes No
7650 – 519 No No Yes No Yes
PM8000 – PQ No Yes Yes Yes No
PM8000 – 519 No No Yes No Yes
*7650 must have firmware version 410, hardware revision 05 (serial number ending in “-05”), and PQ framework v410
** Firmware/Framework version should be < 410. If firmware/framework v410 is used, report will be incomplete
While some meters may provide information such as Harmonics, for real-time purposes, they will not provide
the data necessary for the reports.
4.2.5 Collect and Manage Data from Intelligent Devices

Both PME-DC and PSE with Advanced Reports can communicate with a wide variety of device types such as
power quality meters, trip units, and relays to name a few. Both systems can download alarm, historical, and
waveform data, as well as display real-time information.
When it comes to SNMP devices, both systems collect data in different ways.
4.2.5.1 (Optional) PME-DC Using KEPServerEX

KEPServerEX is third-party software by Kepware that translates SNMP data to OPC. OPC client devices can
then be used to bring data into PME-DC. This can be used for real-time data screens in PME.
The installer for KEPServerEX v5.12.142 is provided on the PME-DC ISO but a license must be purchased
through the licensing portal.
Additionally, a VIP framework can be created to log data from these OPC client devices.
The following image shows the Kepware software where SNMP tags are configured:

SNMP v2 is supported natively in PSE. No additional software is required.
4.2.6 Share Data between Software Systems

4.2.6.1 ETL for Data Center Operation (DCO)
Power Monitoring Expert Data Center Edition

The base module includes an ETL job that exports data from the PME historical database to DCO:
The DCO ETL is dependent on a properly configured PME-DC hierarchy (Customer > Rack > Circuit (default)
or Customer > Circuit). Each PME-DC hierarchy template contains an “Electrical Equipment” view and a
“Customer” view.
*More information on the PME-DC hierarchy tool is available in Appendix E.
For the “Customer” view, Circuits map to Racks which map to Customers (the first three tabs in the picture above). A
branch circuit meter is a single “device” in management console but logs circuit level data under multiple “sources” in
the database. There is one “source” per circuit and that circuit can be single pole, two pole, or three pole. This is true
for devices such as the BCPM, BCPM Flex Cct, EnerSure iBCPM, and the PM5350 IB/PB to name a few. The “Circuits”
tab in the hierarchy is where a user would link a “source” in the database to a “circuit node” that could then map to a
rack and onto a customer.
For the “Electrical Equipment” view a “source” in the database maps to one electrical equipment hierarchy node
such as a PDU or a UPS. This view is meant for meters such as a PM5350 in Power Meter mode or a PM8000
monitoring a load that needs to be exported to DCO, but does not fit into the “Customer” view described
previously.
These two views are important because the ETL will look for data from sources that are mapped to hierarchy
nodes created in either the “Customer” view or the “Electrical Equipment” view. From the ETL to DCO extract
task settings:
PowerSCADA Expert with Advanced Reports

It is possible to extract trend data from IO Devices in PSE that are not added in PME/PME-DC and load that data
into the PME/PME-DC database. Once there it could be exported to DCO provided the correct mapping has been
created in the PSE to PME ETL.
Recommended Meter Types

Any meter capable of logging (either on-board or software logging) the measurements listed in the “Required
Measurements” section can be used.
Since the application engineer could add measurements to the supported lists below (excluding per-phase
energy), it is possible for many meter types to be used. Be aware that extra commissioning time
(approximately a day) would be required in this case.
Required Measurements
Any Power or Current value exported to DCO from PME is a “previous 24 hour sliding window” value. This
means that starting from the current time, go back to the most recent “top of hour” (end of time range) and
from there go back 24 hours (start of the time range). To calculate this value for a source quantity pair the
following measurements are used by default in the PME database:
Power:
CDM Measurement Unit Quantity Name in ION Database ION Register Label
Block Demand Active Power kW Active Power Sliding Window Demand Real
Demand Delivered-Received Power
Block Demand Active Power Into kW Active Power Sliding Window kW sd del
The Load Demand Delivered
Active Power Mean kW Active Power Mean kW tot mean
Active Power kW Active Power kW tot
Per Phase Power:

Active Power A kW Active Power Phase A kW a, Real Power A
Active Power B kW Active Power Phase B kW b, Real Power B
Active Power C kW Active Power Phase C kW c, Real Power C
Current:
Current Average Mean A Current Phase Average Mean I avg mean
Block Demand Current Avg Into A Current Phase Average Sliding Amps Avg Dmd
the Load Window Demand Delivered
Current Avg A Current Phase Average Current Avg
All energy measurements that are exported to DCO are “previous day” values. This means that starting
from the current time, we go back to the previous midnight (end of time range), and from that point go
back 24 hours to the midnight before (start of time range). Only the most recent previous day value is
stored in the DCO staging database, so a historical record is not kept in DCO, just the last 24 hours. To
calculate this value for a source quantity pair the following measurements are used by default in the PME
database:
Energy:
Active Energy kWh Active Energy Delivered – Received kWh del-rec
Active Energy Into the Load kWh Active Energy Delivered Active Energy Delivered
Per Phase Energy:

Active Energy into the Load A kWh Active Energy Delivered Phase A kWh a del
Active Energy into the Load B kWh Active Energy Delivered Phase B kWh b del
Active Energy into the Load C kWh Active Energy Delivered Phase C kWh c del
Note that Power, Energy, Per Phase Power, and Current measurements can be edited to support more than the
quantities listed above. The steps to do this are explained on the Schneider Electric Exchange Community. Search
for the term “Topic Equivalency” and find the discussion on adding a custom current quantity
4.2.6.2 ETL for PowerSCADA Expert Integration

Available on the PowerSCADA Expert DVD, this ETL is specific to the PSE with Advanced Reports offer. It gives
the user the option of transferring data from trend files in PSE to the historical data base in PME. From there
the user can create dashboards and run reports on this data.
Trend tags must be created in the PSE device profiles. The ETL can then auto create the mappings of trend tags
to quantities in PME. The user must validate these mappings are correct.
The recommendation is that any meter providing PQ data, data for a hierarchy, real-time data to the VIP as
part of a PUE calculation, and any trip unit that is part of the breaker performance optional module be added
as a device in PME. This ETL is useful for serial connected devices such as Micrologic trip units where it may
be more beneficial to have a single Modbus master.
If the ETL for PSE is used, special attention must be paid to the data required for reports and other features in
PME. For example, the Power System Losses Report uses power logged by a Micrologic P trip unit. The
“Required Measurements” listed in the Power System Losses section in this guide must be mapped to the
correct trend tag for each Micrologic P device.
See the “Commissioning Time Estimates” section for estimates around the PSE to PME ETL. The bulk of the
commissioning time would be spent validating the correct trend tags are mapped to supported quantities. This
would be done after running the auto-mapping in the ETL:
The application engineer would have to validate that the values in the Target Measurement column match the
quantities listed in the corresponding Required Measurements section of this guide for the feature of interest.
If the Target Measurement is not supported by default in the feature being commissioned, the application
engineer may be able to add the Target Measurement to the supported list as well.
For other ways to get data in and out of PSE see the Integration Map on the Schneider Electric Exchange
Community:
https://exchangecommunity.schneider-electric.com/docs/DOC-15489
4.2.7 (Optional) HTML 5 Remote Desktop Application

“PowerSCADA Anywhere” allows you to remotely access a running PowerSCADA Expert client within a web
browser. This gives users the ability to interact with the PSE runtime client through a secure web browser without
needing to install PSE.
For security reasons, we recommend installing PowerSCADA Anywhere on a different server than the primary or
standby. In this scenario, PowerSCADA Anywhere would be installed on the same server as a PowerSCADA Expert
Control Client.
For supported operating systems see the “Install and Configure the PowerSCADA Anywhere Server“ section in the
“PowerSCADA Expert 8.2 with Advanced Reporting and Dashboards - System Development Guide” available on
the Schneider Electric Exchange Community.
4.3 Capacity Management
4.3.1 Branch Circuit Power

Branch Circuit Power Report provides average and maximum loading (current and power) values of each
circuit as well as the percentage load compared to the breaker size.
The Branch Circuit Power Report requires a hierarchy to be configured using the data center hierarchy
templates (Customer > Rack > Circuit (default), or Customer > Circuit).
* See Appendix E for more information on hierarchy configuration.

• Features in the Branch Circuit Power application module are enabled in PSE by integrating the
web reports from PME-DC
• Meters for this application module should be added to PME-DC for historical data collection and to
PSE for real-time purposes. Branch Circuit data should not be loaded into PME-DC from PSE using
the ETL. In fact, it is recommended to disable any trends in the PSE profile for any branch circuit
meters unless the customer would like to see real-time trending in PSE.
4.3.1.3 Required Meter Types

The Branch Circuit Power Report requires circuit level monitoring data from any of the following meter types:
Power Equipment Meter Recommendation Communications

Power Distribution Units BCPM-E TCP
LV Busway PM5350 (multi-circuit mode) Serial through EGX 100

When data is retrieved from the database for a given circuit, the following measurements are used. The
order of measurements listed is the order of look-up preference:
Demand:
Current:
Note that Demand and Current measurements can be added to the quantities listed above, but additional
commissioning time should be added. The steps to do this are explained on the Schneider Electric Exchange
Community. Search for the term “Topic Equivalency” and open the discussion about adding a custom current
quantity.
4.3.2 Generator Power

The purpose of this report is to show the available redundancy compared to the system's designed redundancy.
N, N+1, N+2, 2N, 2(N+1), and 2(N+2) redundancy configurations are supported. This report considers the entire
load that is powered by the utility main(s) and all the generators which provide backup to it.
The Generator Power module also contains a configuration utility which is used to define the source for the total
data center load and generator ratings:

• Features in the Generator Power application module are enabled in PSE by integrating the web
reports from PME/PME-DC.
• Meters for this application module are added to both PME and PSE, however if a meter other than
the 7650 is selected (for example a meter that did not require a PQ framework or a serial meter) it
would be possible to only add the devices to PSE and use the PSE to PME ETL to transfer the data to
PME. If using the ETL the trending in PSE would have to be mapped to the correct measurements
listed in the “Required Measurements” section below.
Power Equipment Meter Recommendation

Medium Voltage Substation ION 7650
Required Measurements
The Generator Power Report uses a priority table to determine which measurement to use for querying power
data for a load. The table is stored in the PME database and is listed below. The order of measurements listed is
the order of look-up preference.
Measurement Name Physical ID

Active Power Sliding Window Demand Delivered 116
Active Power Sliding Window Demand Delivered-Received 107
Active Power Mean 128
Active Power 193
The report can use different measurements than those listed above but the database must be edited at
installation and commissioning time.
4.3.3 UPS Power

Loading the UPS system to the point of compromising the redundancy design can easily occur over time,
particularly when there is pressure from IT to add more equipment. This business pressure often results in
overloaded UPS systems, at least from a redundancy design perspective. The purpose of the UPS Power module
is to ensure that the redundancy design is not compromised due to IT loading on the UPSs.
The UPS Power Configuration Utility allows you to create, edit, and manage one or more UPS systems that will
be used for reporting on the power capacity of those systems.

• Features in the UPS Power application module are enabled in PSE by integrating the web reports
from PME-DC.
• Since PSE supports SNMP natively it is recommended to add the devices to PSE only. Trending
should be enabled in the profile and the ETL used to load historical data into PME. When mapping
the trend data to PME quantities in the ETL, the application engineer should verify the quantities
(listed in the Required Measurements section below) that the report expects are being loaded into
PME.

IT UPS APC Symmetra MW Modbus RTU through Link150
The only metering location required for the UPS Power module is at the IT UPS. UPS load data can also be derived
from a power meter or Micrologic trip unit on the UPS input breaker, provided the device captures the UPS load and
provides the power measurements below. If a different UPS is already in place the Modbus map or SNMP map
must be inspected to ensure the correct measurements are available. If an MDI device is created, the ION
Register Labels listed in the table below ensure that the correct t measurements will be logged in the database.
If PSE is not used and the customer’s UPS communicates using SNMP, the KEPServerEX option in the base module
can be purchased. A simpler approach for 3rd party customer UPS is adding a communications card to enable
Modbus RTU or TCP communications. With this approach, UPS data can be integrated to PME-DC using the
Modbus device importer or a device driver (if available).

The UPS Power Report uses a priority table to determine which measurement to use for querying power data
for each IT UPS. The table is stored in the PME database and is listed below. The order of measurements listed
is the order of look-up preference.
Quantity Name Physical ID ION Register Labels
Active Power Sliding Window Demand 116 kW tot, kW total, Real Power Total, Panel-
Delivered Main Real Power Total
Active Power Sliding Window Demand 107 Real Power Total mean, Active Power
Delivered-Received Total mean, kW tot mean
Active Power Mean 128 kW demand, kW sd del, kW tot SD
Active Power 193 Demand Real Power – Sliding, Demand
Real Power, Panel-Main Demand Real
Power, kW sd del-rec, kW swd, kW tot
swd, kW Dmd del-rec
The report can use different measurements than the ones listed above but the database will have to be edited at
installation and commissioning time.
Note: If an MDI device has to be created for a third-party UPS, extra commissioning time must be added for the
Application Engineer. The Default Measurement Logging Analyzer spreadsheet (the latest version is available on the
Schneider Electric Exchange Community; search for “Default Logging”) is available to help the Application Engineer
select the correct register labels that map to the measurements listed above.
4.4 Equipment Performance
4.4.1 Generator Performance

Generator Performance provides the ability to automatically record and document the backup Generator
System test. It provides a standard methodology for testing the generators and provides a detailed report of
the generator operation during the test.
There are 4 Reports available in Generator Performance: Generator Test Report, Battery Health Report, Generator
Activity Report, and Load Summary Report.
Generator Test and Battery Health:
Generator Activity and Load Summary:
There is also a Generator Test Configuration Utility:

• Features in the Generator Performance application module are enabled in PSE by integrating the
web reports from PME-DC.
• Meters are added to both PME and PSE for the Generator Performance application module.
Power Equipment Meter Recommendation

Generator Switchboards or Main Switchboard ION 7650 or ION 7550 for each generator
The ION7550 or ION7650 should have digital and analog inputs to bring in data from the generator.
The PM8000 could be specified if the battery health report is not necessary. The PM8000 does not have the V4
contact necessary for sampling the battery voltage.
Also note that the SER-3200 or 2408 could be used to log status measurements for the generators. However, the
reports require electrical data as well, so a power meter capable of logging 1-minute intervals on an event would
also need to be specified.
“Gen Cranking” is required for the battery health report to trigger the waveform capture of the battery starting.
The V4 contact on the ION7550/ION7650 must be available so it can be wired to the +ve terminal of the battery.
The analog inputs are not absolutely necessary and will depend on the data the generator is capable of
providing.

The following table lists the I/O points that must be logged for the Generator Performance module to work.
The data should be logged for each generator at a one minute interval only during the test run:
4.4.1.5 Other Considerations

A PM850 or PM870 can be used instead of the ION meters on each generator with the appropriate I/O card to log
Generator Run/Stop Status and any Analog values. It should be noted that the Battery Health Report is not
supported in this case. An additional limitation for PM850 and PM870 meters is the time stamp accuracy of the meter
digital inputs. If these are used for status then the time stamp accuracy resolution is one second.
If used, PM800 meters require the following generator data to be logged at a one minute interval during the test:
4.4.2 Breaker Performance

Breaker Performance provides a report that displays aging and wear for all breakers defined in the system
and real-time summary screens that display breaker aging and wear parameters by group or equipment.
There is also a VIP framework that can be configured to provide real-time status alarms in the vista
diagrams:
A configuration tool is also provided where each trip unit must be configured.

• Features in the Breaker Performance application module are enabled in PSE by integrating the
web reports from PME-DC. The real-time vista diagrams for Breaker Performance can also be
integrated into the PSE runtime screens.
• All Trip Units that are used as part of Breaker Performance must be added to PME and PSE. The
ETL from PME to PSE is not supported with this application module (untested).
4.4.2.3 Supported Circuit Breakers and Trip Units

A specific list of circuit breakers and trip units are supported depending on the country. The most up-to-date list
can be found in the supported devices section of the “Breaker Performance” section in the Power Monitoring
Expert Application Modules – Configuration Guide available on the Schneider Electric Exchange Community.
4.5 IT Billing
4.5.1 Energy by IT Customer

Energy by IT Customer contains a report that will display the energy usage for IT customers within a Data
Center. The report will show correct allocation of energy usage and, therefore, allow you to support billing
functions for each user’s energy use.
The Energy by IT Customer Report requires a Hierarchy to be configured using the data center specific
templates (Customer > Rack > Circuit (default) or Customer > Circuit). The report pre-requisite page has a
“Timestamp Coincident” option where the user can select “with Customer Peak” or “with Data Center
Peak”. The data center peak option requires main incomer meters to be defined in the “Electrical
Incomers” tab in the hierarchy.
* See Appendix E for more information on hierarchy configuration.

• Features in the Energy by IT Customer application module are enabled in PSE by integrating the
web reports from PME-DC
• Meters for this application module should be added to PME-DC for historical data collection and to
PSE for real-time purposes. Branch Circuit data should not be loaded into PME-DC from PSE using
the ETL. In fact, it is recommended to disable any trends in the PSE profile for any branch circuit
meters unless the customer would like to see real-time trending in PSE.
4.5.1.3 Required Meter Types

The Branch Circuit Energy Report requires metering at the utility level in addition to the branch circuit level. The
utility metering is required if data center peak values are desired as opposed to a customer peak value.

Utility MV Switchgear ION 7650 TCP
Power Distribution Units BCPM-E TCP
LV Busway PM5350 (multi-circuit mode) Serial through EGX 100

When data is retrieved from the database for a given circuit, the following measurements are used. The
order of measurements listed is the order of look-up preference.
Energy:
Current:
Note that Energy and Current measurements can be added to the quantities listed above. The steps to do this
are explained on the Schneider Electric Exchange Community; search for the term “Topic Equivalency” and
open the discussion about adding a custom current quantity.
4.5.2 Billing Module

The Billing Module is a complete billing summary, multi-tenant management, custom formatting, and data
saving tool. There are 4 reports in this module: Billing Report, Billing Summary Report, Multiple Billing Export
Report, and the Multiple Billing Report.
The “Billing Module Toolkit 2.0” is available on the Schneider Electric Exchange Community and contains video
tutorials, FAQ, report examples etc. Here is an example showing a collocation billing summary report:
The Billing Module reports require a Hierarchy in PME-DC. The report above could also be exported to XML
format using the Multiple Billing Export Report.

• Features in the Billing Module are enabled in PSE by integrating the web reports from PME-DC
• Since the Billing Module requires data from the Hierarchy, any devices required for billing should
be added in PME and PSE.

To provide data to either the “Electrical Equipment” or “Customer” view in the hierarchy manager use the
recommended meter types listed in the tables in the “Summary of Metering by Solution Module” section.

Six measurements are implicitly defined in the Sample WAGES rate file. Additional measurements and
measurement types can be added to this list below but extra commissioning time should be added.
Power:
CDM Measurement Unit Quantity Name in ION Database

Block Demand Apparent Power Total kW Apparent Power Sliding Window Demand Delivered+Received
Block Demand Reactive Power kW Reactive Power Sliding Window Demand Delivered - Received
Block Demand Active Power kW Active Power Sliding Window Demand Delivered-Received
Energy:
CDM Measurement Unit Quantity Name in ION Database

Apparent Energy Total kW Apparent Energy Delivered + Received
Reactive Energy Into the Load kW Reactive Energy Delivered
Active Energy Into the Load kW Active Energy Delivered
4.5.3 ETL for Export to Third Party Billing

This ETL extracts energy, demand, and current data from the PME historical database and exports it to a
CSV file format that can be imported into a third party billing application.
The ETL Export expects customers to be configured in a Tenant > Rack > Circuit hierarchy in PME. Therefore, a
hierarchy must also be configured for this ETL.
Similar to Energy by IT Customer, the energy billing export requires a hierarchy to be configured using the
data center hierarchy templates (Customer > Rack > Circuit (default) or Customer > Circuit). The energy
billing export is configured to look for “Customers” from the hierarchy.
A user can run the ETL manually, or configure it to run daily or monthly.

Since the energy billing export ETL requires data from the Hierarchy “Customer” view, any devices
required for the ETL should be added in PME and PSE.

Any meter that can provide the measurements listed in the “Required Measurements” section can be used
for the ETL export. Typically, Energy and Demand data is exported from circuit level data provided by
BCPMs. The ETL can also be configured to export current.

The following tables are in order of look-up preference:
Power:
Energy:
Current:
4.6 System Efficiency
*To import Temperature data into PME-DC see the TVD “How Can I Import Weather Feed Data into PME” on the
Schneider Electric Exchange Community.
4.6.1 Power Losses

PME-DC provides quantification of power system losses and inefficiencies due to transformers (MV and LV) and
UPS modules. The Power Losses module provides the breakdown of the cost of various losses throughout a
Data Centers power system.
Some key features of this Application Module include:

• Breakdown of Power System losses for MV, LV Transformers and UPS Modules
• Reporting losses in kWh
• Reporting losses in currency using blended rate
This module also includes the Power Losses Configuration Utility which allows you to create, edit, and manage
the different logical sources that represent transformers and UPS modules.

• Features in the Power Losses application module are enabled in PSE by integrating the web
reports from PME-DC. The real-time vista screens can also be integrated into PSE runtime.
• The PM8000s are added to PME and PSE but for any of the other devices in this application
module trending could be configured in PSE and the Required Measurements loaded into the
PME-DC historical database (using the PSE to PME ETL).

The Power System Losses report requires energy and power data to be logged above and below all
Transformers and UPSs for the calculations to be carried out. In our Example Architecture, we have Medium
Voltage Transformers, LV Bypass Transformers, IT UPSs and Mechanical UPSs.
MV Transformers

MV Substation PM8000 on each feeder into the transformer TCP
Main LV Switchboards PM8000 on each utility incomer TCP
To calculate the power losses due to the MV transformers a metering point on the primary and
secondary of each MV transformer must be present in the system. Therefore, the PM8000s in the MV
substation along with the PM8000s in on the utility incomer in each Main Switchboard (in each
Data Hall) is required.
LV Transformers (At Input of Critical Bus Switchboards)

Main LV Switchboards Micrologic P Serial through PM8000 as gateway
Critical Bus Switchboards PM8000s on each incomer TCP
LV Transformers (in PDUs)

PDU Depending on Data Hall, PM5320 or PM5110 TCP
PDU Depending on Data Hall BCPM-E, BCPM-A or iBCPM TCP
IT and Mechanical UPS

IT UPS APC Symmetra MW Modbus RTU through Link150
Mechanical UPS APC MGE UPS Galaxy 5000 SNMP or serial through Link150
*External power meters could also be used on the input and output sides of each UPS provided they log the
measurements listed in the “Required Measurements” section below.
By enabling communications to all mechanical and IT UPSs it is easy to configure the Power Losses application
module to report all the efficiencies over time in the customer’s facility. Most UPSs report both input and
output power from which energy can be calculated in the VIP. When energy and power are logged for each
UPS in the system, the Power Losses application module has all it needs to report the efficiency of the UPS
over time.
If the Symmetra MW device is used, the energy must be calculated and logged in the VIP.
If a third party UPS is used the Modbus map or SNMP map would have to be inspected for input power and
output power registers.

These are the energy and power measurements the Power Losses report will look for in the database to
perform its calculations. A description of the calculations done by the report can be found in the “Power
Loss, Cost of Power Loss, and Efficiency Calculations” section in the Reference of the Power Monitoring
Expert Application Modules – Configuration Guide available on the Schneider Electric Exchange Community.
Measurements can be added to these lists using SQL queries. The order of measurements listed is the order
of look-up preference.
Energy:
Active Energy Delivered 129
Active Energy Delivered-Received 135
Power:

Active Power Sliding Window Demand Delivered 116
Active Power Sliding Window Demand Delivered-Received 107
Active Power Mean 128
Active Power 193
4.6.2 Power Usage Effectiveness (PUE)

Power Usage Effectiveness (PUE) consists of a single-page report that displays PUE and average power
consumed for a data center facility, along with average power consumed for the IT equipment running in the
facility. Additionally, two graphical trends are displayed that correspond to the facility PUE values and to the
energy consumption of the facility. The PUE module follows The Uptime Institute – Recommendations for
Measuring and Reporting Overall Data Center Efficiency recommendations for calculating PUE. PUE Category 1
and 2 are supported.
As well as the KPI Vista screen template for PUE:

• Features in the PUE application module are enabled in PSE with Advanced Reports by integrating
the web reports from PME-DC. Any real-time PUE vista screens or dashboards can also be
integrated into PSE runtime.
• Because the VIP is used to calculate the total kW and interval energy for the PUE calculation, any
device that is part of the PUE calculation must be added to both PME and PSE systems.
PUE Category 1

MV Substation ION 7650 TCP
PDU APC Symmetra MW Modbus RTU through Link150
The figure above shows just the IT UPSs in data hall 1 but all twenty IT UPSs in the design would
need to be monitored. A single meter on each utility feed coming into the building combined with
the data from all UPS units will provide the metering necessary for the report, dashboard and KPI
real-time screens.
If the customer uses a different UPS that does not provide total kW measurements (which are linked into
the VIP framework to calculate Energy), the metering point at the incomers of the Critical Bus Switchboards
(highlighted in purple above) should be used to bring total kW in to the VIP.
PUE Category 2
Power Equipment Meter R ecom menda ti on Communications

MV Substation ION 7650 TCP
PDU Depending on PDU PM5320 or PM5110 TCP or serial through Link150
Energy metering on the PDU main(s) is required for the following applications:
• Critical power alarming

• Capacity management (actual vs. rated + phase balancing)
• “Big Power” energy billing
• Electrical system troubleshooting
• Supporting electrical system maintenance activities
Note: If the PDUs have embedded energy metering (e.g. Metering that is at a minimum 1% accurate and
can provide energy, power, voltage, and current data via an industry standard communications protocol)
then it is not necessary to add “loose” metering to monitor the PDU main(s).
PUE Category 1
The VIP framework aggregates total kW values from all Main Incomer Meters and then calculates and logs 3
values that can be selected in the report and used in the Vista KPI screens: kWh del, kWh del int, and kW SWD.
The VIP framework also aggregates total kW values from all UPS Meters and then calculates and logs 3 values
that can be selected in the report and used in the Vista KPI screens: kWh del, kWh del int, and kW SWD.
PUE Category 2
The VIP framework aggregates total kW values from all Main Incomer Meters and then calculates and logs 3
values that can be selected in the report and used in the Vista KPI screens: kWh del, kWh del int, and kW SWD.
The VIP framework also aggregates total kW values from all PDU Meters and then calculates and logs 3 values
that can be selected in the report and used in the Vista KPI screens: kWh del, kWh del int, and kW SWD.
See Appendix B for more information on how to calculate PUE.
4.6.3 Energy Analysis

The Energy Analysis Application Module contains six reports:
Duration Curve Report:
Energy Regression Analysis Report:
This report gives the user the ability to correlate energy usage with external variables. To import weather
data into PME-DC see the TVD “How Can I Import Weather Feed Data into PME?” on the Schneider Electric
Exchange Community.

• The Energy Analysis application module is enabled in PSE with Advanced Reports by integrating
web reports from PME DC into the runtime screens.
• Data can be sent from PSE to PME using the ETL to provide data for these reports.

General metering is required for the Energy Analysis module. See the recommended meters listed in the
“Summary of Metering by Solution Module” section as a guideline.

Basic Energy, Power, Demand, and Current measurements should be logged for use with these reports.
5 SBO Integration
StruxureWare Building Operation 1.9.x can be integrated with either PME/PME-DC or PSE with Advanced
Reports to provide a building management plus power management system for the end user. The details of
the integration with each offer are covered below.
The metering required for the power management side of the design would be identical to what is covered
in the “Design Considerations by Solution Module” section. For the building management system, the
Exchange Download Center is a good starting point for system design ( https://ecobuilding.schneider-
electric.com/)
The PME and SBO Integration Toolkit is available on the Schneider Electric Exchange Community. Despite
the name the toolkit is also used when integrating SBO and PSE with Advanced Reports:
• The PME and SBO Integration Toolkit.zip contains:
• The Integration Utility that easily integrates Reports, Dashboards, Diagrams,
and EWS real-time and alarm data from Power Monitoring Expert in
StruxureWare Building Operation.
• The installer for the ETL package that allows you to transfer energy data
from StruxureWare Building Operation to Power Monitoring Expert.
• Components for the SBO Graphics Editor and SBO WorkStation.
• PME and SBO Integration – Configuration Guide
Also, available for download from the Schneider Electric Exchange Community is the PME and SBO
Integration – Design Guide
5.1 SBO + PowerSCADA Expert with Advanced Reports

The main integration points in this architecture are:
1) PSE EWS server provides alarm data and high level real time data to SBO graphics screens
2) The SBO to PME ETL sends mechanical data to the historical database for display in
dashboards and reports within PSE or SBO.
3) Integration of Reports and Dashboards from PME to SBO to view electrical data
User Views
SNMP
Support
SBO Graphics Screens SBO
for “Macro” level real- PME Dashboards aggregates
Animated one- Reports Viewer / PME PSE Event Log Embedded Native in
times integrated into Alarms from SBO Trending
lines in PSE integrated into Integrated PQ (Time Quality Config View in PSE
(data from PSE EWS) SBO or PSE PME and PSE
SBO Reports in SBO column supported) PSE
through EWS
5.1.1 Alarm and Real-Time Data in SBO from PSE

SBO retrieves alarms and events from the PSE EWS server to provide alarms from the building management
system and power management system in one view:
The EWS server in PSE also provides real-time data to SBO and those values can be linked to SBO graphics at
commissioning time. The following screenshot shows an example of how the components for the SBO Graphics
Editor and SBO workstation (available in the PME and SBO Integration Toolkit) can be used when integrating SBO and
PSE:
Because PSE has a strong animated one-line engine, a customer should be going to PSE for that functionality. As
of PSE 8.2, the integration of any animated one-line graphics pages is not supported.
5.1.2 SBO to PME ETL

Mechanical data from SBO can be sent to the historical database in PME (using the ETL provided in the
Integration Toolkit). Reports and Dashboards from PME can then be integrated into PSE runtime to view
mechanical data within the power management system.
An example screenshot showing dashboards with mechanical data (provided to PME via the ETL) and
integrated into PSE:
*This dashboard could also be integrated into SBO using the Integration Utility.
5.1.3 Dashboards and Reports Integrated into SBO

With all historical data available in PME, Reports and Dashboards with electrical data can be integrated into SBO
using the Integration Utility:
5.2 SBO + Power Monitoring Expert Data Center Edition

The main integration points in this architecture are:
1) PME EWS server provides alarm data and real time data to SBO graphics screens
2) The SBO to PME ETL sends mechanical data from SBO to the PME historical
database
3) Integration of Dashboards and Reports (mechanical and electrical) from PME to
SBO.
User Views
SNMP
Support
SBO Graphics Screens SBO SBO through
SBO Graphics PME Web SER Light - Supported +
(data from PME EWS PME Dashboards aggregates integrated PME
(data from Reports PME Alarm/Event Possible KEPServerEX
Server and PME device integrated into Alarms from Reports and SBO Trending
PME EWS integrated into Logs (no Time Embedded in PME
diagram integration) SBO PME through Device
Server) SBO Quality column) Config View
EWS Diagrams
5.2.1 Alarm and Real-Time Data in SBO from PME

Animated one-lines are built in SBO graphic screens using the components installed by the PME
and SBO Integration Toolkit. Those components are then linked to real-time values provided by
the PME EWS server. Binding templates also provided in the Toolkit assist with the mapping of PME
EWS values to SBO graphics components:
The Integration Utility handles the integration of alarms from PME into SBO.
5.2.2 SBO to PME ETL

Mechanical data from SBO can be sent to the historical database in PME using the ETL provided in the
Integration Toolkit. This mechanical data can then be used in Reports and Dashboards.
5.2.3 Dashboards and Reports Integrated into SBO

The Integration Utility integrates Dashboards, Reports, and WebReach diagrams into SBO:
6 System Communication Design

The System Communication Design section serves as a reference to anyone with the responsibility of designing a
system that will meet a specific level of performance. If a specific level of performance is not required by the
customer, these guidelines do not have to be followed strictly.
For the network drawing of the reference architecture see the PDF on the Schneider Electric Exchange
Community titled “Data Center Reference Design – Network Diagram”.
6.1 Real Time Data and Alarming Performance

If you deviate from the following recommendations your performance may be different.
6.1.1 Real Time Data – PME Only

To achieve a 4 second update period in Vista:
• Configure Vista diagrams for 3s updates (due to site server cache polling at a different rate than data being
pushed to clients of the real-time data service).
• All Ethernet devices tested in this architecture met the 4 second specification without additional
tuning.
• For serial devices, limit the number of devices per daisy chain as per the following table:
Device Type Max Number of Devices Tested

per Serial Loop - PME
Sepam S42 6
Micrologic A/E Compact NSX 6
Micrologic P 4
6.1.2 Real Time Data – PME + PSE

With the addition of the PSE to PME ETL we can eliminate connecting both PME and PSE to Modbus devices that
are historically slow such as the Micrologic Trip Units. In the case where serial devices must be connected to both
systems (used for a PUE calculation in the VIP or to add to the PME Hierarchy) we can achieve a 4 second update
period in PSE graphics screens and WebReach.
To achieve this real-time data performance:

• PSE device profiles modified/created as per the PowerSCADA Expert 7.30 Test System Device Profiles
document.
• Configure Vista diagrams for 3s updates for WebReach integration in PowerSCADA Expert.
• All Ethernet devices tested in this architecture met the 4 second specification without further tuning
• For serial devices, limit the number of devices per daisy chain as per the table below
Max Number of Devices Tested

Device Type per Serial Loop – PME + PSE
Sepam S42 3
Micrologic A/E Compact NSX 3
Micrologic P 2
When PowerSCADA Expert is the only master to devices in the network, use the PSE 8.2 Design Guide to design
for specific real-time data performance. The design guide can be found in the Design and Quote section of the
PSE Guidebook on the Schneider Electric Exchange Community.
6.1.3 Alarming – PME Only

The following applies to the PLC-based alarms only.
In our specification, we have a 3 second Alarm Register Update Time in Vista. To achieve a 3 second Alarm Register
Update Time in Vista:
• PLC is Ethernet Connected

• Vista diagram update period is configured for 1 second
6.1.4 Alarming – PME + PSE

The following applies to high-priority PLC alarms only.
In our specification, we have a 3 second Alarm Register Update Time in PSE.
To achieve this performance:

• PLC is Ethernet Connected
6.1.5 Alarming – PSE only

For Ethernet connected devices a 2 second device response time for alarms can be achieved
For serial connected devices, a 1 second response time per device on the daisy chain (e.g. 4 seconds for 4 serial
devices on a gateway) for alarms can be achieved.
6.1.6 Alarm Notification

To achieve 10 second Alarm Notification Time (the time that the alarm is available for the notification system. Note
that the time for delivery of the email/SMS notification will be longer and is not in control of the power monitoring
system):
• Use the Event Notification Module with PowerSCADA Expert with Advanced Reports
• Devices providing alarms are Ethernet connected
6.1.7 Daisy Chain Calculator for PME

A tool has been designed that helps estimate communication utilization for serial daisy chains. This tool can be
used for both new system design and for optimizing existing Power Monitoring Expert systems for existing serial
daisy chains.
See “Daisy Chain Calculator for Serial Devices” section of the PME v8.2 Design Guide.
When using the daisy chain calculator for PME only a target utilization of 50% is usually acceptable. For PME +
PSE a target utilization of 25% is more likely to result in acceptable performance. This often means that you
design for half the number of devices in the daisy chain in a combined PME and PSE system.
7 IT Infrastructure
A proper IT infrastructure architecture is essential to a data center monitoring system to provide
customers with the expected software experience. To meet this requirement, the IT infrastructure
(servers, network, switches, software, etc.) must be properly specified at the time of the project bid. If
not, it can result in the data center monitoring and alarming not functioning properly and not meeting
customer expectations.
This section covers:

• Supported Operating Systems and SQL Server Versions
• Server Specifications
• RAID Configuration and Hard-Drive groups
• Calculating the size of the live database
• Server Virtualization
• Switches
7.1 Supported Operating Systems and Other Software

7.1.1 Power Monitoring Expert 8.2 – Data Center Edition
7.1.1.1 Application and Database Servers (Secondary Installs blocked in DC)
Note: 32-bit and 64-bit versions are supported. Bitness must match between SQL Server and Windows OS
(32-bit SQL on 32-bit Windows, 64-bit SQL on 64-bit Windows).
Operating System Editions Service Pack
Windows Server 2016 Standard -
Windows Server 2012 R2 Standard -
Windows Server 2012 Standard / Enterprise -
Windows Server 2008 R2 Standard / Enterprise SP1
*if installing KEPServerEX on the PME server, do not use Windows Server 2016
The supported versions of SQL Server:

SQL Server Version Editions Service Pack
SQL Server 2016 Standard / Enterprise / Business Intelligence SP1
SQL Server 2008 R2 Standard / Enterprise SP3
7.1.1.2 Engineering Client
7.1.1.3 Microsoft Excel
7.1.1.4 Supported Browser Versions for Web Clients
7.1.1.5 Language Support in PME-DC 8.2
Power Monitoring Expert 8.2 Data Center Edition can be installed in English, French, German, Spanish, Italian,
Polish, Czech, Russian, Simplified Chinese, Traditional Chinese.
7.1.2 PowerSCADA Expert 8.2 with Advanced Reports

For supported operating systems see the PSE 8.2 Design Guide available on the Schneider Electric Exchange
Community (found in the PSE Guidebook “Design and Quote” section).
While several operating systems are supported, for data centers we recommend Windows Server 2012 R2.
7.1.3 StruxureWare Building Operation 1.9.x

Refer to the “Information Technology System Planning Guide” available on the Exchange Download Center.
Supported web browsers are also available in that document.
7.2 Server Specification

7.2.1 Power Monitoring Expert Data Center Edition
For Data Centers where PME is being applied use the “advanced” system server recommendations from the
Power Monitoring Expert 8.2 – Design Guide. PME-DC Edition is considered an advanced system because it can
use custom VIP applications, report generation, OPC Server tags, Branch Circuit and PQ meters, and general SQL
server loading from the four possible ETL jobs in the offer.
The Power Monitoring Expert 8.2 – Design Guide discusses why CPU and RAM are important, the
advantage of a 64-bit operating system, and Windows versus Windows Server
The Power Monitoring Expert 8.2 – Design Guide also discusses important hard drive considerations and
provides an explanation around the recommended hard drive groups and RAID configurations in our server
specifications (e.g. Space for Windows OS and other components, hard drive contention, etc.) This is an
important consideration for data centers especially when there are a significant number of branch circuit meters
and the live database can grow quite large.
For each system the size of the live ION_Data database must be calculated as this will determine the size of the
hard drives required. An example will be discussed in the next section
7.2.1.1 Systems with up to 50 Devices

“Advanced 2” system from the Power Monitoring Expert 8.2 – Design Guide.
Computer Type: Server

OS: Windows Server 2012 R2
SQL: 2014 Standard SP1
CPU: Intel Xeon E5 2603 (4 core), or better
RAM: 16+ GB
Hard Drives and RAID: RAID 1 with 2 Groups of hard drives (total of 4 drives)
Group 0 Group 1
Component HDD1 + HDD2 HDD3 + HDD4
OS1 
tempDB2 
MDF3 
LDF4 
Backups5 
1
Includes the Operating System, page file, Power Monitoring Expert, and any other applications.
2
SQL Server temporary system database.
3
SQL Server main databases.
4
SQL Server transaction log files.
5
Power Monitoring Expert database backups.
7.2.1.2 Systems with up to 250 Devices

“Advanced 3” system from the Power Monitoring Expert 8.2 – Design Guide. Note that more than 250 devices
could be supported with this particular server but it depends on the device types in the system and intended
usage.

CPU: x2 Intel Xeon E5 2603 (4 core), or better
RAM: 24+ GB
Hard Drives and RAID: RAID 1 with 3 Groups of hard drives (total of 6 drives)
Group 0 Group 1 Group 2

Component HDD1 + HDD2 HDD3 + HDD4 HDD5 + HDD6
OS1 
tempDB2 
MDF3 
LDF4 
Backups5 
1
2
3
4
5
7.2.1.3 Systems with more than 250 Devices

“Advanced 4” system from the Power Monitoring Expert 8.2 – Design Guide.

CPU: x2 Intel Xeon E5 4607 (6 core), or better
RAM: 32+ GB
Hard Drives and RAID: RAID 1 on 3 groups of hard drives. RAID 10 on 1 hard drive group
Group 0 Group 1 Group 2 Group 3

Component HDD1 + HDD2 HDD3 + HDD4 HDD5 + HDD6 HDD7 + HDD8 +
HDD9 + HDD10
OS1 
tempDB2 
MDF3 
LDF4 
Backups5 
1
2
3
4
5
7.2.1.4 PME Client (Engineering and Web)

See the “Client Types” section of the Power Monitoring Expert 8.2 – Design Guide for a description of an
Engineering client and a Web Client. The server specification for both clients can be found in that section as well.
7.2.2 PowerSCADA Expert with Advanced Reports

As a general rule, for every 250,000 tags and/or 1000 devices 1 server with 8 cores and 16GB or RAM is used.
For more details on server sizing in PSE see the PSE 8.2 Design Guide available on the Schneider Electric
Exchange Community (found in the PSE Guidebook “Design and Quote” section).
7.2.3 StruxureWare Building Operation

The “Enterprise Server Specification Sheet” should be used for server sizing in SBO and can be found on the
Exchange Download Center.
7.3 Hard Drive Sizing

To size the hard drives used for the PME server it is important to understand the number of devices in the
system and the daily growth rate for each device type. The “Hard Drive Considerations” section of the
Power Monitoring Expert 8.2 – Design Guide contains a lot of important information for specifying hard drives.
As an example, if you use the Database Growth Calculation Tool available on the PME Exchange Community
and plug in the numbers for a large data center system with 116 Micrologic A Compact NSX, 24 Micrologic E
Compact NSX, 2 7650, 700 BCPM, 55 Micrologic A, 22 Micrologic H, 360 PM5350, 58 PM820, and 41 Sepam
40 the Annual Database Growth comes out to ~365 GB.
If two years’ worth of data is required in the live database for reporting purposes the total database size would
be ~730GB. This is the recommended hard drive group configuration:
Group 0 Group 1 Group 2 Group 3

Component HDD1 + HDD2 HDD3 + HDD4 HDD5 + HDD6 HDD7 + HDD8 +
HDD9 + HDD10
OS 
tempDB 
MDF 
LDF 
Backups 
Group 0
The “Hard Drive Space for Software Components” section of the Power Monitoring Expert 8.2 - System Design Guide
specified ~130GB. Therefore, 300GB drives were selected to allow for future space requirements.
Group 1
TempDB lives on this group and can grow to the size of the mdf (on upgrades for example). Therefore 1.2TB
drives were selected. See Group 2 for mdf size calculation.
Group 2
To account for PQ Data we added 20% of the live database size = 730 + (0.20 * 730) = 876 GB
Then to account for free hard-drive space we used another 30% = 876 + (0.30 * 876) = 1139 GB
Therefore 1.2 TB drives were selected.
Group 3
We decided to only store 1 database backup instead of the default 2. Room is required for the backup (1.2 TB), the
ldf which can grow to the size of the mdf (1.2TB), and the free space required to create the backup (1.2TB).
In total 12 drives were selected. The 700 BCPM count definitely drives the size of the drives up in this particular
example, so this is a bit of an extreme case. The PME System Design Guide contains a smaller system’s example
and other considerations that may apply to your customer’s set up.
Hard Disc savings can be realized by transferring the database backup to an external drive (such as in a SAN).
7.4 Server Virtualization

Most enterprises are moving to virtual server environments due to their high density, low cost, and flexibility.
Each piece of software that is part of the StruxureWare Power Monitoring Data Center Edition offer can run in
virtual environments. However, it is important that the virtual environments are not undersized to save server
costs. If undersized virtual machines are used to run the software the system will not work properly and
customers will be unsatisfied.
Each Virtual Server Environment should have its own documentation in regards to replicating the hardware
recommended in PME-DC Edition.
7.4.1 Virtual Machine Recommendations

Guidelines for Virtual Machines:
• For best processing performance, a 1 VCPU to 1 logical CPU ratio is recommended. For example, if the
physical server has two 6 core processors, allocate 12 VCPUs to the VM. With hyper threading enabled,
allocate 24 VCPUs.
• For best read/write performance use separate drive groups for each VM drive partition. Do not create
one large RAID drive and split it into logical volumes in the OS.
7.5 Network Switches

Network switches are required throughout the communications network to direct requests and responses from
the various devices in the system. Generally, a customer may already have such hardware in place but if not
then giving them guidance will help ensure the reliability and availability of the communications network.
7.5.1 Main Server Switch

The main server switch needs to be a high bandwidth switch and have the capability to limit the traffic to and
from devices in the power monitoring network. The high bandwidth requirement is essential because the switch
will direct traffic from multiple users to the power management server. To respond to all the data requests
from clients throughout the corporate network it is important that the uplink speed of the switch be at least 1
Gigabit (Gbit) Ethernet. The individual port speeds can be as low as 100 Megabit (Mbit) without any
performance issues. However, more bandwidth is recommended for ports that feed multiple dense metering
connections.
7.5.2 Switchboard Network Switches

Multiple gateways may be required for switchboards that contain many metering devices. The number of
devices on each serial line should be limited. For switchboards that contain many metering devices this would
require running multiple Ethernet cables which can be expensive and time consuming. Instead another option
would be to use an industrial network switch inside the switchboard and distribute the network locally. The
recommended switchboard networking architecture is depicted in the following figure:
The ConneXium Ethernet switch is the recommended Schneider Electric product for such an application. The
ConneXium Ethernet switches support industrial designers looking to employ industrially rugged switches
directly onto machines or within their plant floor environment. Additionally, they support Gigabit speed
technology that allows the construction of faster backbones, greatly increasing the bandwidth in heavily
congested applications. An eight port ConneXium Ethernet switch is shown below.
ConneXium Ethernet Switch DIN Rail Mountable
The other key feature is that the ConneXium Ethernet switches are DIN rail mountable so installing them into
existing switchboards is convenient and easy. This is ideal for retrofits as there is usually some left over space on
the DIN rails in most switchboard designs. An example installation of a ConneXium switch is shown below:
8 Commissioning Time Estimates

The following estimates are based on commissioning our in-house test system described in Appendix A.
PLC programming and the development/testing of the PowerSCADA Expert project are not listed here but also
require commissioning time.
CommissioningTask Time Estimate
General Configuration
Existing equipment metering, protection and gateways Already Configured
Loose / New Metering Configuration 15 minutes / device
Loose / New gateways 15 minutes / device
IT Server Configuration 1 Day
SQL Server + Service Pack install 30 minutes
Windows and SQL Updates 3 hours
PowerSCADA Expert 8.2 install 30 minutes
PME-DC Edition install 20 minutes
Add / Test sites and devices in PME 250 / hour
Configuration of Base
PME vista screen development using DC templates 0.5 day / diagram
Hierarchy configuration for DCO ETL 30 minutes + 1 hour/500 devices
Configure + Test ETL for DCO Export 5 minutes / device
ENM install 15 minutes (PME) or 45 minutes (Redundant PSE)
ENM Configuration 15 minutes + 1 minute / alarm
PSE/PME Web Reporter integration + testing 1 hour
PSE/PME dashboard integration + testing 1 hour
PME-DC Edition Data Center VIP configuration 1 hour
PME-DC Edition Data Center alarming VIP configuration 10 minutes per device
Kepware SNMP to OPC Gateway configuration + testing 0.5 day / device
Configure web reports in web client 5 minutes / report
Install and Configure PowerSCADA Anywhere 1 hour install + 1 hour test
Capacity Management Configuration

Hierarchy config + testing for Branch Circuit Power (if not 30 minutes + 1 hour/500 devices
done for Energy by IT Customer or DCO ETL)
Generator Power 30 minutes + 5 minutes per generator
UPS Power 30 minutes + 5 minutes per UPS
Equipment Performance Configuration

Configure ION meters with frameworks 45 minutes / generator
Define generators 15 minutes / generator
Define equipment 5 minutes / equipment
Configure Reports 10 minutes
Configure battery health 15 minutes
Configure breaker performance 30 minutes / trip unit
IT Billing Configuration
Hierarchy config + testing for Branch Circuit Power (if not 30 minutes + 1 hour/500 devices
done for Energy by IT Customer or DCO ETL)
Configure Billing Module 1 day
Configure + Test ETL for Billing Export 1 day
System Efficiency Configuration

PME-DC Edition Data Center VIP configuration 15 minutes
PUE Report setup + testing 15 minutes
PUE vista diagram 30 minutes
Define Transformers/UPSs + Power Losses Report Setup 15 minutes + 5 minutes / Transformer or UPS
Import Weather Feed Data TVD setup 2 hours
For SBO Integration time estimates see the “Commissioning Time Estimates“ section for Architecture 2 in the PME and SBO
Integration – Design Guide available on the Schneider Electric Exchange Community.
Appendix A: Description of Test System

See Validation Lab – Test System Design and Results on the Schneider Electric Exchange Community.
Appendix B: How to calculate PUE

This appendix explains how to calculate PUE in two situations: when the monitoring system is for a dedicated
data center, and when the monitoring system is for a data center in a mixed-use building.
Steps to calculate PUE are provided below. The suggested metering points are described in the Power
Monitoring Architecture section for the PUE Solution to function properly.
Power Usage Effectiveness Calculations

PUE is an important measurement to data center customers and is one of the primary outputs of the PUE
Solution. This section shows the calculations necessary to properly compute this value. It will start with the
high-level PUE description and drill through each component.
Total Data Center Load

The calculation of total data center load depends upon the data center type. The calculation for a data center in
a mixed-use building differs from the calculation for a dedicated data center.
Dedicated Data Center

In a dedicated data center facility, total data center load equals the facility load. All energy consumed by the
building is either consumed by the IT whitespace or is consumed by components supporting the whitespace.
Data Center in a Mixed-Use Facility

If the data center is in a mixed-use building, the total data center load calculation must factor out all non-IT-
related energy consumption. This includes any office building loads (plugs, lights, etc.) as well as the HVAC
necessary to condition the office building portion.
Where:
If Total HVAC power is unmetered, it can be calculated as follows:
IT Load
For the PUE Solution, assume the IT load will always equal the sum of the UPS units’ output. This is true, no
matter the building type.
Factored PUE Calculations

For a dedicated facility:
For a mixed-use facility:
Appendix C: Resources for Data Center Redundancy

information
White Paper 75 – Comparing UPS System Design Configurations:
http://www.apcmedia.com/salestools/SADE-5TPL8X/SADE-5TPL8X_R3_EN.pdf
Appendix D: Example IT Power Distributions

Terminology used in Diagrams:
PDU – Power Distribution Unit. There are two styles of PDUs. One type has 42-pole panels inside it. The other
type has output breakers that feed RPPs.
RPP – Remote Power Panels. RPPs have 2 or more 42 pole panels contained within them. These units are
usually located quite close to the IT racks, often “in-row”.
Low Voltage (LV) Busway – An electrical power distribution system found in datacenters that uses PIU’s to
connect devices
PIU – Plug In Unit. This is a device that sits on an LV Busway and distributes power to devices in the facility such
as IT Racks.
Room PDU Distribution
In-Row PDU Distribution
PDU and RPP Distribution
IT Panelboard Distribution
IT Busway Distribution
Appendix E: PME Hierarchy Configuration

The hierarchy component in Power Monitoring Expert Data Center Edition can be configured using a CSV
import file:
1) The application engineer can export a template csv file using a command line tool after all devices
have been added to Management Console. This exports the list of sources in PME that are not
already mapped to hierarchy nodes (should be all sources at initial commissioning time). The
application engineer then fills out the CSV file. There are columns associated with the
Circuit>Rack>Tenant Hierarchy which the Branch Circuit Power and Energy by IT Customer reports
use. There are also columns for the Electrical Equipment Hierarchy that is for the ETL export to DCO.
The completed CSV file can be imported using the same command line tool as was used during
export.
2) Opening the Hierarchy Configuration manager through Management Console lets the user see the
imported hierarchy information. In the Circuits tab, the user can see what underlying device(s) the
circuit hierarchy node is mapped to as well as the Rack each circuit belongs to.
3) Racks are shown here along with which circuit nodes and customers each Rack is associated with.
4) Finally, the customer view which contains a list of Racks that belong to each customer. The billing ID
here is used in the Billing Module and when using the 3rd party billing ETL.
For more information, see the Schneider Electric Exchange Community for a video tutorial on configuring
the Data Center Hierarchy.
Appendix F: PME DC/Standard Edition Differences

The standard and data center versions of PME are very similar. In PME 8.2 it is possible to build a data center
solution from the standard PME edition including all the same modules.
The following table lists the differences between data center and standard PME:
PME-DC PME Standard
PME-DC Data Center Hierarchy

Installed Available through commissioning
Template
PME-DC Vista diagram Available for download from the Exchange

Installed
templates and Graphics community
PME-DC VIP Frameworks and

Installed Not Available
logical device scripts
KEPServerEX V5.12 Included on DVD Must be download from Kepware website
Schneider UPS OPC device types

(MGE, SmartUPS, Symmetra)
Schneider Symmetra Modbus

device type
PME-DC Data Center Branding Installed Not Available
Report Client Installs Not Supported Supported
Secondary Installs Not Supported Supported
SQL Express Not Supported Supported
PSE with Advanced Reports Not on DVD – would have to be ordered

On DVD
Module separately
References
1) The Uptime Institute - Recommendations for Measuring and Reporting Overall Data Center Efficiency -
Version 2 – Measuring PUE for Data Centers
Publication Date: May 17, 2011
2) Schneider Electric: PowerLogic™ SEPAM™ Digital Relay Catalog
3) Schneider Electric: Masterpact NT™ and NW LV power circuit breakers and switch-disconnectors– Catalog
4) Schneider Electric: Compact NSX™ - Circuit breakers and switch disconnectors – Catalog
5) Schneider Electric: PowerPact™ H-, J-, and L-Frame Circuit Breakers – Catalog
6) Schneider Electric: PowerLogic™ Series 800 Power Meter - Installation Guide
7) Schneider Electric: PowerLogic™ Series 800 Power Meter - User Guide
8) Schneider Electric: PowerLogic™ Power Meter PM5350 - Installation Guide
9) Schneider Electric: PowerLogic™ Power Meter PM5350 -User Guide
10) PowerLogic PM8000 series - User Manual
11) PowerLogic ION7550/ION7650 Power and Energy Meters - User Guide
12) Data Center Reference Design – Alarm Points
13) Data Center Reference Design – Metering and Protection
14) Data Center Reference Design – Network Diagram
15) Data Center Reference Design – SER Wiring and IO points
16) PME and SBO Integration Design Guide
Terms and Definitions

Generator A standby diesel or natural gas generator intended to provide
backup power to the data center in the case of a Utility
outage.
Low Voltage (LV) For the IEC electrical market, this refers to voltages above 220V
and below 1,000V (1kV)
Medium Voltage (MV) For the IEC electrical market, this refers to voltages above
1,000V (1 kV) and below 30,000V (30kV)
Power Distribution Unit (PDU) A specially designed panelboard fitted with multiple outputs
designed to distribute electric power to IT racks.
Revenue Grade Meter A power meter that meets one of the following adhere to
international standards for metering accuracy:
• IEC 62053-22 Class 0.5S
• IEC 62053-22 Class 0.2S
Surge Protection Device (SPD) A device that limits the voltage supplied to the electrical
distribution system to within expected design parameters. This
device is used to mitigate the damaging effects of transient
voltages on electronic equipment.
Schneider Electric Reference Design A complete, data center electrical design created by
Schneider Electric
Total Harmonic Distortion (THD) The total harmonic distortion, or THD, of a signal is the root
sum of the square of the amplitude of all harmonic
components to the amplitude of the fundamental frequency
component of the signal.
Total Demand Distortion (TDD) The total demand distortion, or TDD of a signal (typically
electrical Current) is the ratio of the root sum of the square of
the amplitude of all harmonic components to the amplitude of
the maximum demand load.
Uninterruptible Power Supply (UPS) A power distribution component that “cleans” the power being
supplied to sensitive electronic equipment and provides
enough ride through during a Utility outage to allow the
backup generator system to engage.
Utility For the purposes of this document, “Utility” refers to an

electrical utility provider
Bandwidth The available data transfer rate of a given network in
Mbit/s.
Ethernet Networking technology used for local area networks and uses
various mediums to transmit data at high speeds.
Ethernet Gateway A device that converts Ethernet based communications to

serial communications.
Transmission Rate The speed at which data is transmitted. Typically in bit/s.

SerialCommunications Networking technology used for point to point
communications and typically uses copper conductors as the
data transmission medium.
Response Time The time difference between a request for data from a
device and the response.
Real-Time Screen Update Period The period at which data on a real-time screen is
refreshed.
Transmit Delay The time delay between a master station receiving data from a
device and then sending another request for data.
Transmission Rate The speed at which data is transmitted. Typically in bit/s

Central Processing Unit (CPU) The hardware within a computer system which carries out
the instructions of a computer program by performing the
basic arithmetical, logical, and input/output operations of
the system.
Multi-core processor A multi-core processor is a single computing component with

two or more independent actual processors (called “cores").
Random Access Memory (RAM) A form of computer data storage often associated with
volatile types of memory.
Redundant Array of Independent A storage technology that combines multiple disk drive
Discs (RAID) components into a logical unit.
Storage Area Network (SAN) A dedicated network that provides access to

consolidated, block level data storage.
WebReach Historical name for the “Device Diagrams” feature in the web
applications of PME
Gallery Design An ANSI market design where the PDU is split into two pieces:
1) The main breaker and panel main breakers (+transformer
if used) are one unit and located in the electrical room
adjacent to the IT floor
2) The panels with the MCBs are mounted on the walls or
in-row on the IT floor
Schneider Electric
35 rue Joseph Monier
92500 Rueil Malmaison – France
www.schneider-electric.com
As standards, specifications, and designs change from time to time, please

ask for confirmation of the information given in this publication.
Copyright 2017 Schneider Electric. All rights reserved.

7EN42-0151-00 04/2017

Data Center Power Management 8.2 - Design Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Data Center Power Management 8.2 - Design Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Data Center Power Management

Schneider Electric – Data Centers

Electrical equipment should be installed, operated, serviced and maintained only

The addition of either symbol to a “Danger” or “Warning” safety label indicates

4.2.5.2 PowerSCADA Expert with Advanced Reports ................................................................................................................................................... 51

5.1.2 SBO to PME ETL .......................................................................................................................................................................................................... 85

The Design Guide covers:

Commissioning Time Estimates – Time estimates for commissioning tasks.

2 Data Center Power Management Architectures

Functionality PME / PME-DC PSE with Advanced Reports

Real Time Screen Update Time ≤ 4 seconds* ≤ 2 seconds

Limited Graphics Flexibility / Data

System Redundancy No Redundancy Native PSE Redundancy

Modbus, ION, OPC Modbus, ION, IEC61850, DNP3, IEC60870-

Power System Control No Yes

2.2 Part Name to Solution Module Mapping

Solution Module Corresponding Part Reference Description

“SNMP OPC Server” (optional)

“Generator Performance Module”

“Power Efficiency Module”

Capacity Management “Power Capacity Module”

IT Billing “IT Billing Module”

2.3 Power Monitoring Expert Data Center Edition

2.3.2 Server Architecture (server specs provided in IT Infrastructure section)

2.4 PowerSCADA Expert with Advanced Reports

In PSE 8.2 the user views information through the following:

Notes about the combined system:

2.4.2 Server Architecture (server specs provided in IT Infrastructure section)

2.5 Building Management System + Power Management

2.5.1 Software Architectures

2.5.1.2 PME-DC + SBO

2.5.2 Server Architectures (server specs provided in IT Infrastructure section)

3.1.1 Medium Voltage Substation

Abbreviation Display Icon Meter Type

RLY Sepam Series 40

Each MV Transformer steps the voltage down from 12,470-480Y/277 Volts.

3.1.2 Data Hall 1

3.1.3 Data Hall 1 IT Distribution

3.1.4 Data Hall 2

Abbreviation Display Icon Meter Type

3.1.5 Data Hall 2 IT Distribution

3.1.6 Data Halls 3 and 4

3.1.7 Data Hall 3 IT Distribution

3.1.8 Data Hall 4 IT Distribution

3.1.9 Data Hall 5

3.1.10 Data Hall 5 IT Distribution

3.1.11 Data Hall 6

3.1.12 Data Hall 6 IT Distribution

3.2 Power Equipment Description

Medium Voltage Substation and MV Transformers

Generator and Generator Switchboards

IT UPS Input Switchboards

IT UPS Output Switchboards (Critical Bus Switchboard)

Power Distribution Units (PDUs)

Mechanical UPS Switchboard (Input and Output) + Mechanical UPS

3.3 IEC Consideration

4 Design Considerations by Solution Module

4.1 Summary of Metering by Solution Module

BASE OPTIONAL SOLUTION MODULES

Equipment System Capacity

Power Usage Effectiveness

Power System Losses

Branch Circuit Power

IT UPS Input Switchboard X1 X X6