EcoStruxure™

Power Monitoring Expert 9.0

IT Guide
7EN42-0168-00
09/2018
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 bulletin 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 a hazardous situation which, if not avoided, will result in death or serious
injury.

WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.

CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.

NOTICE
NOTICE is used to address practices not related to physical injury.

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.
Contents
Safety Precautions 6
Introduction 7
Resources 8
Overview 10
System Architecture 11
Client Types 13
Engineering Client 13
Web Client 13
Licensing 15
License Activation 15
License Types 15
System backups 18
IT Requirements 20
Computer Hardware 21
Choosing Computer Type, CPU, and RAM 21
Choosing Hard Disk Drives (HDDs) 23
Operating Environment 27
Windows Updates 28
Localization 28
Operating System Considerations 28
SQL Server Considerations 29
Network Connectivity 31
Network Communication 31
Network Shares 31
Windows Domain Compatibility 31
IPv6 Compatibility 31
IP Port Requirements 31
Device Networks 34
Device networks overview 35
Network Types 36
Network Performance 37
Time synchronization 38
Tools 39
Other IT Considerations 40
PME Server Name Limitations 40
Display Resolution 40
Cybersecurity 41
Planning 41
Network security 41
Data encryption 41
Malware detection 41

7EN42-0168-00 Page4
 IT Guide

Account and password management 42

PME Services 43
Hardware Ports 43
Diagnostics and Usage Feature 43
Network Shares 44
Installation and upgrade 44
Keep the PME System Key secure 44
Do not use a Web Client on the server computer 44
Change the Share permissions on the product directory 44
Configuration 44
Configure PME users and user groups 44
Change the SQL Server Express sa account password 45
Application control (whitelisting) software 45
Operation 45
Session timeout 45
Administration 46
Windows and SQL Server Updates 46
User account maintenance 46
Reference 47
Accounts and services 48
Windows accounts 48
SQL Server accounts 50
PME Windows services 52
IIS Application Pools 59
Databases 60
PME Databases 60
Trial license limitations 61
Database growth calculations 62
Factory default measurement logging 62
Custom measurement logging 62
Power quality event logging 62
Configuring session timeout settings 64
Adding idle detection to custom Web Application links 65

Page 5 7EN42-0168-00
IT Guide Safety Precautions

Safety Precautions
During installation or use of this software, pay attention to all safety messages that occur in the
software and that are included in the documentation. The following safety messages apply to this
software in its entirety.

WARNING
UNINTENDED EQUIPMENT OPERATION
• Do not use the software or devices for critical control or protection applications where human
or equipment safety relies on the operation of the control action.
• Do not use the software to control time-critical functions.
• Do not use the software to control remote equipment without proper access control and status
feedback.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.

WARNING
INACCURATE DATA RESULTS
• Do not incorrectly configure the software or the devices.
• Do not base your maintenance or service actions solely on messages and information
displayed by the software.
• Do not rely solely on software messages and reports to determine if the system is functioning
correctly or meeting all applicable standards and requirements.
• Consider the implications of unanticipated transmission delays or failures of communications
links.
Failure to follow these instructions can result in death, serious injury, equipment
damage, or permanent loss of data.

WARNING
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
Use cybersecurity best practices to help prevent unauthorized access to the software.

Failure to follow these instructions can result in death, serious injury, equipment
damage, or permanent loss of data.

Work with facility IT System Administrators to ensure that the system adheres to the site-specific
cybersecurity policies.

7EN42-0168-00 Page 6
Introduction IT Guide

Introduction
Power Monitoring Expert (PME) is a client-server, on-premise software application that collects
power monitoring data through a network of connected devices. The power monitoring data is
processed and stored using Microsoft SQL Server and can be accessed by users in a variety of
formats through different user interfaces.

This document is intended for IT professionals who support the PME system installation. It provides
information on possible deployment architectures, supported operating environments, required
access permissions, IT and device network considerations, cybersecurity, the PME installer, as
well as general dependencies and prerequisites.

Page 7 7EN42-0168-00
IT Guide Introduction

Resources
Download Center

NOTE: The EcoStruxure™Power Monitoring Expert System Guide includes the content of the
following guides: What's New Guide, IT Guide, Web Applications Guide, and the OR Isolated
Power Interface User Guide.

The following EcoStruxure™Power Monitoring Expert9.0 documents are available on the Schneider
Electric Download Center:

l System Guide (English) – Document number 7EN02-0411

l What's New Guide (English) – Document number 7EN12-0314

l OR Isolated Power Interface User Guide (English) – Document number 7EN02-0412

l Web Applications Guide (Multilingual) – Document number 7EN02-0409

Exchange Extranet

l EcoStruxure Power Monitoring Expert portal

l Downloads (Software Installers, Service Packs, Device Drivers, and so on)

l Power Monitoring Expert Design and Quote tools:

Daisy Chain Calculator

Commissioning Time Calculator

Database Growth Calculator

Secondary Server Calculator

l Power Monitoring Expert Install and Maintain documents:

IT Guide (English)

Before Installing Your Software (English)

Using the SQL Server 2016 DVD Guide (English)

ETL 5.0 – Installation and Configuration Guide

ETL for 3rd Party Billing – Administration Guide

ETL for Data Center Operation – Administration Guide

EGX300 and Com'X 510 to PME – ETL Data Migration Guide

PME Upgrade tools and resources

Other

l PME Licensing Portal

l Schneider Data Privacy and Cookie Policy

7EN42-0168-00 Page 8
Introduction IT Guide

Technical Support

l Technical Support by country:

Use the My Schneider App or contact your local country office.

l Software Licensing Support

[Offline license activation, license returns]

l Software Registration Centers

[Global contact information. Contact a Software Registration Center (SRC) if you exceed the
license return limit, or if a license has become untrusted. Do not contact a SRC for
troubleshooting license issues or to get new licenses. They are not able to help with these
issues.]

External Resources

Microsoft® technical documentation:

l How to choose antivirus software to run on computers that are running SQL Server

l How to determine which versions and service pack levels of the Microsoft .NET Framework are
installed

l Microsoft .NET Framework 3.5 Deployment Considerations

Page 9 7EN42-0168-00
IT Guide Overview

Overview
This section provides an overview of the PME system.

Use the links below to find the content you are looking for:

System Architecture
Client Types
Licensing
System backups

7EN42-0168-00 Page 10
Overview IT Guide

System Architecture
PME is a client-server, on-premise software application that collects power monitoring data through
a network of connected devices. The power monitoring data is processed and stored using
Microsoft SQL Server and can be accessed by users in a variety of formats through different user
interfaces.

PME is deployed in one of two basic architectures: Standalone or Distributed Database.

Standalone architecture
In a Standalone architecture, all PME system files, the SQL Server database, and any other tools or
utilities are installed on the same computer. You access the power monitoring data through clients.

Distributed Database architecture

In a Distributed Database architecture, all PME system files, tools, and utilities are installed on one
computer. The database server is installed on a second computer. There are no PME system files
installed on the database server except for the historical database files. You access the power
monitoring data through clients.

The following example diagram shows both architectures in the context of the overall system,
including the monitoring devices:

Page 11 7EN42-0168-00
IT Guide Overview

Which architecture should you choose?

We recommend you use the Standalone architecture. It is easier and more cost effective to deploy,
and there are no performance advantages in using a Distributed Database architecture.

However, in some cases it might be necessary to use the Distributed Database architecture, such
as:

l Your customer wants to use an existing SQL server.

l Your customer IT requirements do not allow a Microsoft SQL Server to be installed with another
application on the same server.

l The application requires Microsoft SQL Server redundancy with SQL Clustering or other third-
party tools.

l The application requires specific rules for database management, for example SQL jobs, back-
ups, data security,... .

7EN42-0168-00 Page 12
Overview IT Guide

Client Types
In PME you use clients to access the configuration tools and the applications for viewing data.
There are two different types of clients:

l Engineering Clients are used to configure and administer the system.

l Web Clients are used to view power monitoring information.

Engineering Client
An Engineering Client is an administrative interface in PME that is used to configure and administer
the system. Engineering clients include tools such as the Management Console, Vista, and
Designer.

One Engineering Client is installed, by default, on the PME server. Additional Engineering Clients
can be installed on other computers, for example on a portable notebook computer, that are more
accessible than the server. Engineering Clients require an Engineering Client license.

Web Client
A Web Client is used to view power monitoring information such as real-time data, historical
information, and alarms which are used in day-to-day power management tasks.

Web Clients access the data on the server through a Web browser. No installation is required. Web
Clients can run on any computer on the network. Web Clients require a Web Client license.

Web Clients can access the Web Applications (Dashboards, Diagrams, Trends, Alarms, and
Reports) in PME.

To set up a Web Client, enter the fully qualified domain name of the PME server or its IP address,
followed by /Web into your browser.

Examples:
l [Link]
l [Link]

NOTE: Web is the default root directory. The root directory is configurable and can be changed
during installation.

By default, the first application on the navigation bar in Web Applications opens in the browser. To
specify which application should open first, add one of the following application parameters to the
Web address: (Note that the parameters are case-sensitive.)
#Dashboards, #Diagrams, #Trends, #Alarms, #Reports

Page 13 7EN42-0168-00
IT Guide Overview

For example, [Link] opens the Alarms

application in the browser.

NOTE: For cybersecurity and performance reasons, we recommend that you do not use a Web
Client on the PME server computer.

7EN42-0168-00 Page 14
Overview IT Guide

Licensing
PME is a proprietary software that uses licensing to control its use and distribution. The licensing is
enforced through mechanisms that disable certain software functions if no valid license has been
activated.

To use PME, you must purchase software licenses and activate them in the system. The licenses
give you the right to use the software according to the terms and conditions described in the
software End User License Agreement (EULA). The licenses generally do not expire, unless stated
otherwise in the software EULA. PME licenses are per site. If you have multiple sites, you must
purchase licenses for each site. Multi-site, or enterprise licenses are not available.

PME uses a modular licensing structure where different licenses enable different functions in the
software. Some of these functions are optional, others are required. The licenses are cumulative,
meaning that you can add additional licenses to a system, to enable additional functionality.

License Activation
Purchased licenses must be activated either through online or offline methods. An Internet
connection for the PME server is required for online activation. Offline activation must be done from
an alternate Internet-connected computer or smart-phone with Web access.

Licenses are tied to the host computer (physical or virtual). If PME needs to be moved to a new
computer, the licenses must first be returned and then reactivated on the new computer. Licenses
can only be returned and reactivated twice per calendar year.

License Types
The following table shows the different licenses that are available for PME.

Type Description
New system installations include a time limited trial license.

The trial license:

l enables most of the PME features (see Trial license limitations for
details)

l includes an unlimited device license

l expires after 90 days

Trial license
l cannot be extended or reinstalled

l includes client licenses that can only be used on the primary server,
not on a client computer

l remains active until its expiry even if other licenses have been
activated

l aggregates together with other active licenses

Page 15 7EN42-0168-00
IT Guide Overview

This is a required license. It enables the PME server functions. Without

the Base license the system is not functional. The same Base license can
Base license be used for Standalone or Distributed Database systems.

The Base license includes the use of one Engineering Client and two Web
Clients.
This is a required license. It enables the use of monitoring devices in PME.
The licenses are sold in bundles of 5, 25, 50, 100, 200, unlimited. At least
one license bundle must be activated in the system. The following
licenses exist:
Device license
l Entry DL (for entry-level device types)

l Medium DL (for mid-level device types)

l Standard DL (for advanced device types)

This is an optional license. It enables the use of Engineering Clients and
Web Clients. The following applies:

l Web Client licenses can be purchased independent of Engineering

Client license Client licenses.

l An Engineering Client license includes one Web Client license.

l Unlimited client licenses are available.

This is an optional license. It enables the use of a Software Module. Each
Software Module requires its own, specific license. The following Software
Modules exist in PME:

l Backup Power Management Module

l Billing Module

l Breaker Performance Module

Software Module
license l Capacity Management Module

l Energy Analysis Module

l Event Notification Module

l Insulation Monitoring Module

l Power Quality Performance Module (includes Power Quality gadgets)

This is an optional license. It enables the use of Dashboard Gadgets. Each

Gadget Pack requires its own, specific license. The following Gadget
Packs exist in PME:

Gadget Pack license l Energy Usage Gadget Pack (included gadgets: Sankey, Pareto,
Aggregated Pareto, Heat Map, Consumption Ranking, Aggregated
Consumption Ranking)

OPC DA Server This is an optional license. It enables the use of the OPC server
license component in PME.

7EN42-0168-00 Page 16
Overview IT Guide

This is an optional license. This is a license for a Microsoft SQL Server

which can be purchased from Schneider Electric. You can also use the
SQL Server license free SQL Server Express version that is included with the PME installer,
use an existing SQL Server, or purchase a SQL Server license directly
from Microsoft.
Developer/Demo
This is a special license. Contact Schneider Electric for details.
license

Page 17 7EN42-0168-00
IT Guide Overview

System backups
Database Backups
Backup the PME databases to be able to recover the live databases if they become unusable.

A backup is a copy of a live database, for example ION_Data in PME. By default, PME
automatically backs up its databases on a daily (ION_Network) or weekly (ION_Data and
ApplicationModules) basis, and keeps two backups of each database in the main installation
folder:
...\Schneider Electric\Power Monitoring Expert\Database\Backup

NOTE: Change the folder location if the default location has insufficient free disk space.

You can perform additional, manual backups using standard SQL Server backup procedures.

Database Archives
Archive data from the live ION_Data database to reduce the database size.

An archive is a copy of a subset of data from the live ION_Data database based on a date range and
the type of data (Data Records, Waveforms and Events). When an ION_Data archive is created it
remains attached to the SQL Server database engine so that its data is still accessible to Vista and
Diagrams. However, the data is not available to other applications in the Web Applications
component.

After you have archived the data, you must trim this same data from the ION_Data database to get
the size reduction.

NOTE: When you trim data from an SQL database, the database file size remains unchanged.
However, the database will first fill the new free space before growing the database file size again.
If you want to reduce the database file size, you must shrink the database after trim, using
standard SQL Server tools.

7EN42-0168-00 Page 18
Overview IT Guide

Considerations for Archives

In most cases archiving is not recommended since it fractures the data into multiple databases.
PME is unable to query multiple databases at the same time to make comparisons in the data. (It is
possible to run reports against an archived database, but it can only be done on one database at a
time.)
However, the ION_Data database may need to be reduced in size for the following reasons:

l SQL Server Express is used as the database engine, which has a database size limit of 10 GB.

l SQL Server (Standard or Enterprise edition) is used as the database engine and the ION_Data
database has become so large that query performance is poor.

l There is not enough free hard drive disk space left and a larger disk cannot be installed.

Page 19 7EN42-0168-00
IT Guide IT Requirements

IT Requirements
This section provides information on specifications and requirements related to information
technology (IT) components, such as computer hardware, operating environment, and networking.

Use the links in the table below to find the content you are looking for:

Computer Hardware Computer types, CPU, RAM, and HDDs.

OS, DB server, Web browser, and other
Operating Environment
compatible software.
Required network shares, Windows domain
Network Connectivity compatibility, IPv6 compatibility, and IP port
requirements.
Other IT Considerations Computer name limitations, display resolution.

7EN42-0168-00 Page 20
IT Requirements IT Guide

Computer Hardware
The performance of a computer is determined by the following factors:

l Computer type (desktop, workstation, or server)

l Central processing unit (CPU)

l Random-access memory (RAM)

l Hard disk drive (HDD)

When choosing the computer hardware for your PME system, you need to consider the following:

l Number of devices in the system

l Number of concurrent users

l System performance expectations

l Data exchange with other systems

l Historical data logging needs

NOTE: Undersized computer hardware is a common source of performance issues with PME
systems.

Choosing Computer Type, CPU, and RAM

The computer type, CPU, and RAM determine the overall performance and reliability of the system.
CPU is important for device communications and RAM affects SQL Server performance.

As a starting point for the selection of these components, we are defining two different system
categories, Basic Systems and Advanced Systems. Decide which category best describes your
system needs and then use the information provided in the tables below to define your computer
hardware specifications.

Basic Systems
A basic system is defined by the following characteristics:

l Factory default measurement logging (logging frequency >= 15 minutes)

l No custom applications

l No Power Quality Performance monitoring

l Only a small number of branch circuit monitor devices in the system

l A device type mix of approximately:

70% entry level devices (for example iEM3xxx)

20% intermediate level devices (for example PM8xxx)

10% advanced level devices (for example ION9000)

Minimum recommended computer hardware for servers in Basic Systems:

System Size Devices Users Computer hardware

Page 21 7EN42-0168-00
IT Guide IT Requirements

Desktop
Small ≤ 100 ≤5 Intel Core i5 (2 core)
8 GB (RAM)
Workstation
≤ 250 ≤ 10 Intel Xeon W-21xx (4 core)
16 GB (RAM)
Medium
Server
≤ 600 ≤ 10 Intel Xeon E3-12xx (6 core)
24 GB (RAM)
Server
Large ≤ 2500 ≤ 10 Intel Xeon E3-12xx (10 core)
32 GB (RAM)

Advanced Systems
An advanced system is defined by the following characteristics:

l Custom measurement logging with <15 minute intervals

l Custom applications using the VIP module

l Power Quality Performance monitoring

l Large number of concurrent users

l High percentage of advanced level devices in the system

l Large number of branch circuit monitor devices in the system

l Large scale data exchange with third party systems (for example through OPC or EWS)

l Other resource intensive software systems installed on the same computer

Minimum recommended computer hardware for servers in Advanced Systems:

System Size Devices Users OPC Tags HW

Workstation
Small ≤ 100 ≤ 15 5000 Intel Xeon W-21xx (4 core)
16 GB (RAM)
Server
≤ 250 ≤ 20 10000 Intel Xeon E- 12xx (6 core)
24 GB (RAM)
Medium
Server
≤ 600 ≤ 35 30000 Intel Xeon E3-12xx (10 core)
32 GB (RAM)
Server
Intel Xeon Scalable Silver (12
Large ≤ 2500 ≤ 50 50000
core)
64 GB (RAM)

7EN42-0168-00 Page 22
IT Requirements IT Guide

Client Computers
Since all the data processing is done on the server, the client computer hardware recommendations
are the same for Basic Systems and Advanced Systems.

Minimum recommended computer hardware for clients:

l Engineering Client
Intel Core i3 (2 core or better)

4 GB of RAM

l Web Client
2 GHz, Dual Core processor

4 GB of RAM

Monitor resolution of 1024 x 768

NOTE: To improve the information display, we recommend a minimum monitor resolution of

1440 x 900.

Choosing Hard Disk Drives (HDDs)

The HDDs determine the historical data access performance and the amount of historical data that
can be stored in the system. HDD configurations are also important for system availability and
recovery.

HDD Size
The HDD must have enough space for the different programs and applications that are running on
the computer. This includes space for the historical data that is recorded by the system and some
free space as a buffer.

The following table shows the estimated HDD space that is required, without the historical data
logs. The estimates are rounded up and allow for updates and system maintenance.

Component HDD space

Windows Operating System software 100 GB
Microsoft SQL Server software 2 GB
PME software 5 GB
PME system databases 5 GB
PME historical database (see below)
Free space 30% of the HDD size

PME historical database

The HDD space that is required for the historical database (ION_Data), is equal to five times the
size of the main database file (ION_data.mdf).

It can be broken down into the following components:

Page 23 7EN42-0168-00
IT Guide IT Requirements

Component HDD space

Main database
(1x) ION_data.mdf size
file (.mdf)
Transaction log
(1x) ION_data.mdf size
file (.ldf)
Backups (2x) ION_data.mdf size
Free Space for
Backups or (1x) ION_data.mdf size
tempDB
Total (5x) ION_data.mdf size

The estimates above are based on the following assumptions:

l The .ldf file is typically just 10% of the .mdf size, but occasionally expands to 100% during nor-
mal operation.

l The system default is to keep two database backups.

l 100% of the .mdf size is required for free space. The tempDB will occasionally expand to 100%
of the total .mdf size, but not at the same time as a backup. If the backups and tempDB are on
different hard drive groups, they each require x1 .mdf in hard drive space.

Main Database File Size (ION_data.mdf)

Unlike the system software, the historical database size is continuously growing. Its size and
growth can be estimated based on the amount of:

l Factory default measurement logging

l Custom measurement logging

l Power quality event logging

Also, the database occasionally grows by 10% to create room for additional measurements. This
growth operation can occur at any time and you need to consider it in the database size
calculations.

NOTE: Use the Database Growth Calculator tool to estimate the database growth for your
system. The tool is available through the Exchange Community. See Resources for link
information.

HDD Configuration
HDDs can be configured as single drives or drive groups. For a small Basic Systems, a single HDD
is sufficient. For all other systems, we recommend that you separate the major components into
different HDD groups.

RAID Systems
In addition to separating the software components into different hard drive groups, redundant arrays
(RAID) can be used to add simple redundancy. In a RAID 1 configuration, one HDD is a complete
copy of a second HDD. If either of the two HDDs stops operating, the other takes over without any
data loss. The faulty HDD can then be replaced to restore the RAID configuration.

Recommended RAID 1 configurations:

7EN42-0168-00 Page 24
IT Requirements IT Guide

Group 0
Component
HDD1 + HDD2
2x OS ü
HD tempDB ü
D MDF ü
LDF ü
Backups ü
Group 0 Group 1
Component HDD1 + HDD3 +
HDD2 HDD4
4x
OS ü
HD
tempDB ü
D
MDF ü
LDF ü
Backups ü
Group 0 Group 1 Group 2
Component
HDD1 + HDD2 HDD3 + HDD4 HDD5 + HDD6
6x OS ü
HD tempDB ü
D MDF ü
LDF ü
Backups ü
Group 0 Group 1 Group 2 Group 3
Component HDD1 + HDD4 +
HDD3 HDD6
HDD2 HDD5
6x
OS ü
HD
tempDB ü
D
MDF ü
LDF ü
Backups ü
Component Group 0 Group 1 Group 2 Group 3
HDD1 + HDD3 + HDD5 + HDD7 +
HDD2 HDD4 HDD6 HDD8
8x
OS ü
HD
tempDB ü
D
MDF ü
LDF ü
Backups ü

NOTE: Plan for system growth by having a computer with space for additional HDDs. This makes
it easy to add additional HDDs as the system grows.

Page 25 7EN42-0168-00
IT Guide IT Requirements

NOTE: It is possible to use other RAID configurations, such as RAID 0 or RAID 5. These
configurations are not discussed in this document.

7EN42-0168-00 Page 26
IT Requirements IT Guide

Operating Environment
PME supports the following environments and software:

NOTE: The operating system and SQL Server combination you choose must be supported by
Microsoft. This applies to edition, version, and 32-/64-bit.

Software Supported versions

Windows 7 Professional/Enterprise (for Engineering clients
only)
Operating system Windows 10 Professional/Enterprise
Windows Server 2012 R2 Standard/Enterprise
Windows Server 2016 Standard
SQL Server 2012 Express
SQL Server 2014 Express
SQL Server 2016 Express (included with PME)
SQL Server 2017 Express
SQL Server 2012 Standard/Enterprise/Business
Intelligence
Database system**
SQL Server 2014 Standard/Enterprise/Business
Intelligence
SQL Server 2016 Standard/Enterprise/Business
Intelligence
SQL Server 2017 Standard/Enterprise/Business
Intelligence
VMWare Workstation 10
VMWare ESX1 6.0
Oracle Virtual Box 5.0.4
Microsoft Hyper-V from Windows 8.1, Windows Server
Virtual environment***
2012
Citrix XenServer 6.2
Parallels Desktop 10
QEMU-KVM
Microsoft Excel Microsoft Excel 2010, 2013, 2016
Microsoft Internet Explorer 11
Microsoft Edge
Desktop Web browser Google Chrome version 42 and later
Mozilla Firefox version 35 and later
Apple Safari versions 7 or 8 and later
Safari on iOS8.3+ operating systems, Chrome on Android
Mobile Web browser
systems
4.6 for PME
.NET Framework 3.5 (or 3.5 SP1) for the PME installer
4.0 for the Power Monitoring Expert licensing component

** PME includes a free version of SQL Server Express. You have the option to install this Express
version during the installation of PME, if you don't want to use a different SQL Server.

Page 27 7EN42-0168-00
IT Guide IT Requirements

*** You must configure virtual environments with a supported Windows operating system and SQL
Server edition. It is possible to mix virtual and non-virtual environments for PME server and clients.

Windows Updates
Critical and routine Windows Updates can be applied to the operating systems hosting the PME
server and clients without prior approval by Schneider Electric.

Localization
PME supports the following languages:

English, Chinese (Traditional and Simplified), Czech, French, German, Italian, Polish, Portuguese,
Russian, Spanish, and Swedish.

A non-English version of PME only supports an operating system and SQL Server of the same
locale. For example, a Spanish version of the product must be used with a Spanish version of SQL
Server and an operating system with a regional setting of Spanish.

The English version of PME can be used with a supported language, non-English operating system
and SQL Server as long as both have the same locale. For example, an English version of the
product can be used with a German version of SQL Server and an operating system with a regional
setting of German.

Operating System Considerations

Windows or Windows Server?
PME supports both Windows and Windows Server operating systems. However, we recommend
you use the Windows Server for the following reasons:

l Windows Server can use server-class computer hardware. It can access more CPUs and more
RAM than Windows. For example, Windows 10 is limited to two physical CPUs.

l Windows Server offers better performance for running PME services.

32-bit or 64-bit systems?

PME is a 32-bit software that can run on both 32-bit and 64-bit systems. We recommend you use a
64-bit system (OS + SQL Server) for the following reasons:

l The SQL Server 64-bit performance is higher than the 32-bit version.

l 32-bit operating systems are limited to just 4 GB of RAM, 64-bit versions are not.

l 32-bit systems are a legacy technology for operating environments.

NOTE: The operating system and SQL Server combination you choose must be supported by
Microsoft. This applies to edition, version, and 32/64 bit.

7EN42-0168-00 Page 28
IT Requirements IT Guide

SQL Server Considerations

Express Version or Full version?
Microsoft SQL Server is available as a free, scaled down Express version, and as a priced, full
server version. You can use both versions with PME. However, the Express version has the
following built in limitations:

l Maximum database size of 10 GB.

l No SQL Server Agent service.

l Limited to lesser of 1 socket or 4 cores.

l Limited to use a maximum of 1 GB of the total system RAM.

In addition, PME has the following limitations when used with SQL Server Express:

l Only supported for Standalone systems, not for Distributed Database systems.

l Not supported for systems with Power Quality Performance module.

NOTE: PME includes a free version of SQL Server Express. You have the option to install this
Express version during the installation of PME, if you do not want to use a different SQL Server.

Existing or New SQL Server?

You can use PME with an existing SQL Server, or you can install a new one. The following table
lists the installation requirements for new and existing SQL Server types:

Type Description
PME requires a certain configuration of the
New SQL Server Standard
SQL Server.
PME includes a free version of SQL Server
New SQL Server Express Express. You have the option to install this
Express version during the installation of PME.
To use an existing instance of SQL Server
Standard , the SQL Server setup wizard must
Existing SQL Server Standard
be rerun to configure the software correctly for
use with PME.
The PME installer can add a new instance to
Existing SQL Server Express an existing SQL Server Express for use with
PME.

NOTE: The operating system and SQL Server combination you choose must be supported by
Microsoft. This applies to edition, version, and 32-/64-bit.

SQL Server Clustering

Clustering refers to a group of two or more SQL Servers that work together and appear as a single
server to the outside. When a client connects to an SQL Server cluster, it appears that there is only
a single SQL Server. In case of a server failure, the remaining servers take over without an
interruption. Using clustering increases system availability.

Page 29 7EN42-0168-00
IT Guide IT Requirements

PME can be used in a clustered environment when deployed in a Distributed Database architecture.

l The Application Server is deployed in a non-clustered environment.

l The SQL Server component is deployed in the clustered environment.

NOTE: SQL Server clustering is only supported for Distributed Database systems, not for
Standalone systems.

7EN42-0168-00 Page 30
IT Requirements IT Guide

Network Connectivity
Network Communication
The PME server, database server, and clients must be able to communicate with each other over
the network using TCP/IP protocol. The licensing component of PME requires that PME clients and
server can resolve each other’s address by name (not just fully qualified domain name or IP
address). If a proxy server is used on the network, then a local address bypass must be configured
on the PME server.

An Internet connection is not required for PME to function correctly.

Network Shares
Engineering Clients require that the Power Monitoring Expert folder on the PME server is shared
with full read and write permissions. File and Printer Sharing must be enabled.

Windows Domain Compatibility

Domain membership is not required for PME to function.

l PME can be installed on servers in a domain environment, however it cannot be installed on

domain controllers. If PME is installed on a server that is subsequently changed to a domain
controller, the software ceases to function correctly.

l For Distributed Database installations of PME, the Database Manager tool can only be used if
the database server and the PME application server are in the same domain. The Database
Manager cannot be used, in a distributed database installation, if the database server and the
PME application server are in workgroups.

l A domain account is required for Side-by-Side upgrades of distributed systems using the Con-
figuration Manager Tool. This domain account must be:
A member of the Administrators group on the PME server

Added as a Login in SQL Server with sysadmin role in the database instance.

l PME supports Windows Active Directory services for user account sharing.

IPv6 Compatibility
PME supports IPv6 (and IPv4) for communications with metering devices. The software
components of PME require IPv4. That means PME can be used on computers with single stack
IPv4 or dual stack IPv4/IPv6 network adapters.

IP Port Requirements
PME depends on certain ports for the communication between its components and the connected
devices. Which ports are required for a specific installation depends on the system configuration
and the monitoring devices used.

The following table lists all relevant ports and their functions:

Page 31 7EN42-0168-00
IT Guide IT Requirements

Location Function Protocol Ports Configurable Direction*

SQL Server
TCP 1433 No Inbound
Database instance
Server SQL Server
UDP 1434 No Inbound
Browser
HTTP 80 Yes Inbound
IIS Server
HTTPS 443 No Inbound
Application
Module Web TCP 23102 No Inbound
Services
13667
PME Diagnostics
13671
Viewer (on TCP No Inbound
6000-99
Engineering client)
57779
13666
PME Vista (on
TCP 13670 No Inbound
Engineering client)
57777
PME
PME Designer (on
Server TCP 13666 No Inbound
Engineering client)
PME Management
Console (on TCP 13666 No Inbound
Engineering client)
PME OPC Client OPC 135 No Inbound
File and Printer
Sharing for NetBIOS/SMB 139/445 No Inbound
Engineering client
Ecostruxure Web
HTTP 80 No Inbound
Services
Licensing Vendor
TCP 27010 Yes Inbound
Daemon
Modbus TCP 502 No Inbound
Power Meter Modbus RTU 7701 No Inbound
communication ION 7700 No Inbound
PML 3721 No Inbound
Power Telnet 23 No Inbound
Meter FTP 20/21 No Inbound
Power Meter TFTP 69 No Inbound
access SMTP 25 No Outbound
HTTP 80 No Inbound
HTTPS 443 No Inbound
Ethergate
Gateway communication Modbus/ION/PML 7800-03 No Inbound
gateway

7EN42-0168-00 Page 32
IT Requirements IT Guide

* The direction of a port is determined by the communication initiation request which will establish
the communication socket.

The following image shows the ports and the components they are associated with:

Page 33 7EN42-0168-00
IT Guide IT Requirements

Device Networks
This section provides information on the communication links between the software and the
monitoring devices.

Use the links in the table below to find the content you are looking for:

Device network basics and the supported

Device networks overview
protocols and device types.
Network Types Ethernet and serial communication networks.
Ways to improve the device communication
Network Performance
performance.
Time synchronization on the monitoring device
Time synchronization
network.
Tools The Daisy Chain Calculator tool.

7EN42-0168-00 Page 34
IT Requirements IT Guide

Device networks overview

PME is a software application that processes, stores, analyzes, and displays power system data
and information. PME collects the source data from devices that are installed in the electrical
system that is being monitored. Each device must be connected to a communication network
through which the software initiates the data retrieval.

Examples of monitoring devices include:

l Power and energy monitoring devices

l Contactors and protection relays

l Circuit breaker trip units

l Smart panels

l Power quality mitigation equipment

l Programmable Logic Controllers (PLCs)

PME supports the following communication protocols:

l Modbus™ TCP

l Modbus™ RTU

l ION™

l OPC DA

For a device to be compatible with PME, it must support one of these communication protocols.

Page 35 7EN42-0168-00
IT Guide IT Requirements

Network Types
The two basic types of communication networks for PME are Ethernet and serial.

Ethernet Networks
Ethernet device networks can be integrated into regular corporate LANs or they can be separate,
independent networks, providing a higher level of security and availability.

Devices are configured in PME by providing fixed IP addresses (IPv4 or IPv6) and ports, or based
on device names. Device names must be used for devices with dynamic address assignment, for
example using the DHCP protocol. When device names are used in PME, then a form of name
resolution mechanism is required on the network.

Device communications are based on encapsulated Modbus or ION protocol and are not encrypted.
Bandwidth requirements per device are typically low, but depend heavily on the amount and type of
data requested from the device by PME.

Ethernet networks are in many ways superior to serial networks and we recommend that you use
Ethernet networks whenever possible.

Serial Device Networks

Serial communication is the traditional way of connecting devices to PME. Serial communications
require an intermediate converter or gateway, for example a Link150, to establish a network
connection. The performance of a serial communication network can become the limiting factor for
the overall system performance.

NOTE: If you use an ION meter as a gateway, with Ethergate protocol, you loose the ability to
multi-master the serial devices.

Serial device communications are based on Modbus RTU or ION protocol and are not encrypted.
See Tools for information on how to design a serial network.

PME also supports communication through telephone modems.

Reasons for using serial networks include:

l The device type only supports serial communications.

l A serial communication network is already in place.

l The existing Ethernet networks do not allow the connection of monitoring devices.

Ethernet networks are in many ways superior to serial networks and we recommend that you use
Ethernet networks whenever possible.

7EN42-0168-00 Page 36
IT Requirements IT Guide

Network Performance
Communications between the software and the devices consist of :

l On demand, real-time data requests, for example for Diagrams or Dashboards displays.

l Periodic polling and uploading of data logs, events, and waveform records.

To optimize the on demand and background polling performance, consider the following when
designing the system and the communication network:

l Real-time data polling periods should be set to meet the user needs. Do not poll with high speed
when it is not needed. Real-time data clients include Vista, Diagrams, OPC, VIP, Trends, and
EWS.

l Disable devices that are not presently commissioned or functional. This includes devices that
are inoperable, or that have a communication error rate >5%.

l Connect high-end devices with power quality monitoring features, such as the ION9000, dir-
ectly through Ethernet, not serial. These devices can generate large amounts of logged data,
such as power quality data, which requires a high bandwidth connection to the monitoring soft-
ware. If a direct Ethernet connection is not possible, then connect the devices through small
serial loops, with one or two devices per loop.

l Setup the devices to only log those measurements that are needed to meet the user needs.

l Schedule the log uploads to occur at times when the system usage is low, for example during
night time or off hours.

l Use the Daisy Chain Calculator tool to determine the maximum number of devices in a serial
loop for your system. See Tools for more information.

l In most applications, Ethernet networks will provide a better performance than serial networks.

Page 37 7EN42-0168-00
IT Guide IT Requirements

Time synchronization
To maintain accurate time in the monitoring system, the devices must be time synchronized.
Depending on the synchronization mechanism, different levels of time accuracy can be achieved.
PME has the ability to synchronize devices to the PME server computer clock. This can be done
over serial networks and Ethernet networks.

The time synchronization to the computer clock using the regular communications protocols can
maintain a system time accuracy in the range of seconds. This is accurate enough for many
applications. However, for applications such as power event analysis or protection coordination
studies, that require high absolute and relative time accuracy, you need to use other time
synchronization methods for the devices, such as PTP or GPS time synchronization.

7EN42-0168-00 Page 38
IT Requirements IT Guide

Tools
Use the Daisy Chain Calculator tool to design your serial communication networks. This tool helps
you estimate the communication utilization for serial daisy chains. You can use it for new system
design and for optimizing existing systems.

NOTE: The Daisy Chain Calculator is available through the Exchange Community. See
Resources for link information.

Page 39 7EN42-0168-00
IT Guide IT Requirements

Other IT Considerations
PME Server Name Limitations
The computer name for the PME server must have 15 characters or less, and use only letters,
numbers, or the "_" (underscore) character.

NOTE: The computer name must not be changed after the PME software is installed. If the
computer name is changed after the install, the software ceases to function correctly. Should this
occur, contact Technical Support for assistance.

Display Resolution
The minimum display resolution for PME user interfaces is 1024 x 768 pixels.

7EN42-0168-00 Page 40
Cybersecurity IT Guide

Cybersecurity
The information in this section is organized by the following life-cycle stages:

l Planning

l Installation and upgrade

l Configuration

l Operation

l Administration

Planning
Network security
PME is designed for an intranet environment within a secured network infrastructure. PME is NOT
designed for direct Internet connection.

Data encryption
At Rest
PME protects the passwords of its user accounts, as well as the Windows and SQL Server
accounts using SHA-256 and AES-256 cryptography. PME uses a unique encryption key for each
installation. The key is generated during the installation of PME. The PME installer offers
functionality for exporting/importing encryption keys for the installation of PME clients or system
upgrades.

The power monitoring data that is collected by PME, and system configuration data are not
encrypted.

In Transit
PME uses Transport Layer Security (TLS) 1.2 for an encrypted, authenticated connection using
HTTPS between the server and the Web clients. Both self-signed and authority issued certificates
are supported. PME is installed with a self-signed certificate and a self-signed certificate is
configured automatically. We recommend that you replace this with a security certificates from a
Certificate Authority (CA).

The communication between PME and connected monitoring devices is not encrypted.

Malware detection
PME can be used with antivirus (AV) software. AV software can have a significant impact on
system performance if not set up correctly. In particular, SQL Server performance can be affected if
data and log files are not excluded from on-access scans. We have seen issues during the
installation of PME, where AV scan delays caused timeouts and failures in the installation process.

PME can be used with whitelisting software products such as McAfee Applicaton Control software.
See Application control (whitelisting) software for more information.

Page 41 7EN42-0168-00
IT Guide Cybersecurity

Anti-virus software on your SQL Server

We recommend that you run anti-virus software on your SQL server. Follow the recommendations
described in Microsoft Support article (ID: 309422). See Resources for link information.

NOTE: Special configuration of the AV and whitelisting software might be required. Follow the
instructions of the software vendor for installing, configuring, and operating the AV and whitelisting
software.

Account and password management

The following types of accounts are required for a PME system:

PME Users
A user account in PME provides access to the system. There are 3 different types of users -
standard users, Windows users, and Windows groups. Each user has an access level, which
determines the actions the user is allowed to perform in PME. There are no pre-configured user
accounts or user groups in the system. One supervisor account is created with a user defined
password during the installation of the software. Additional user accounts and groups must be
created manually after installation. PME supports Windows Active Directory integration for
Windows users and groups.

TIP: Use Windows users and groups to take advantage of Windows account security features
such as maximum login attempts or minimum password requirements.

Windows accounts used by PME

PME uses Windows accounts for report subscriptions and database maintenance. The accounts
are created automatically during the installation of the software. The accounts share the same
password, which is set at install time and can be changed at any time through the installer.

If PME is configured to use SQL Integrated Authentication, then an additional Windows account is
required for database access. This Windows account is also used to run the PME services and the
IIS Application Pools. This account must be created manually and account details must be provided
during the installation of the software.

See Windows accounts for more information.

SQL Database server accounts

If PME is configured to use Mixed Mode database authentication, then SQL server accounts are
required for database access. The accounts are created automatically during the installation of the
software. The accounts share the same password, which is set at install time and can be changed
at any time through the installer.

If SQL Server Express is installed, with Mixed Mode authentication, through the PME installer, a sa
account with a unique, default password is created automatically during install. The password can
be changed at any time through SQL Server Management Studio.

See SQL Server accounts for more information.

7EN42-0168-00 Page 42
Cybersecurity IT Guide

EcoStruxure Web Services account

If EcoStruxure™ Web Services (EWS) are used, data exchange credentials must be defined. The
credentials consist of a single username and password. The EWS credentials are set manually in
the Web Applications > SETTINGS area of the software.

PME Services
PME uses a number of services to perform the background server tasks. The services use the
Local System account, or the Windows account used for SQL Integrated Authentication if that is
configured.

See PME Windows services for more information.

Hardware Ports
Computer ports and inputs, such as USB ports or DVD drives are not required for PME to function
correctly. These inputs can be permanently disabled if necessary. The same applies to the AutoRun
and AutoPlay functionality which can also be disabled without affecting the operation of the
software.

Diagnostics and Usage Feature

Diagnostics and Usage is a feature in PME, that collects basic usage statistics and anonymously
sends this data to a secure server. Schneider Electric uses this data to help improve our software
by understanding how you use it. This operation is enabled by default.

To disable the sending of data:

1. Open Web Applications, click Settings > Diagnostics and Usage.

2. Select Disable in the dropdown list and click Save to apply the change.

The following diagnostic and usage data is collected when it is enabled.

Diagnostic data Usage data

l Power Monitoring Expert version l Total number of devices

l Operating system version and type (32- or 64-bit) l Device type count

l Number of CPU cores l Number of users

l System memory (RAM)

l .NET Framework version

l SQL Server version

l Distributed or local database

l City or region

l Number of monitors in use

l Client screen resolution

l Screen DPI

Page 43 7EN42-0168-00
IT Guide Cybersecurity

The diagnostics and usage service collects and sends data to Schneider Electric weekly on
Monday at 2:00 a.m. (server time), over HTTPS at port 443. Each time the service runs, it creates a
log file in the system\bin folder in the Power Monitoring Expert install location.

NOTE: All diagnostics and usage data is sent to Schneider Electric anonymously. None of the
collected information identifies you or your company. For more information on Schneider Electrics
Privacy Policy, see the Schneider Data Privacy and Cookie Policy. See Resources for link
information.

Network Shares
PME Engineering Clients require that the Power Monitoring Expert folder on the PME server is
shared with full read and write permissions. File and Printer Sharing must be enabled as well.

Installation and upgrade

Keep the PME System Key secure
During the installation of PME, a system key is generated and a copy of this key is exported as a
.key file. This system key is the encryption key used by the software to encrypt user and system
credentials. A PME server securely retains the original key in the registry. The exported copy is
needed for the installation of Engineering clients and Secondary servers. It is also needed in case of
a future side-by-side system upgrade or migration.

As long as the PME server has the original key stored securely in the registry it is possible to export
a copy at any time using the installer. However, should the original key get deleted from the server
somehow, it cannot be recreated or exported. Keep the exported system key in a safe location,
protected from unauthorized access.

Do not use a Web Client on the server computer

Using a Web Client on a server computer increases the vulnerability of the server and the network.
Configure Web Clients on client computers only, not on the server.

Change the Share permissions on the product directory

All share permissions are automatically set to “Read” permissions for the “Everyone” group; this
includes the PME share (the product's installation directory).

Change the product directory's share permission to Read/Write for users of Engineering Client
computers who need to modify files, such as Vista diagrams.

Configuration
Configure PME users and user groups
There are no pre-configured user accounts or user groups in a newly installed system. One
supervisor account was created, with a user defined password, during the installation of the
software. Create additional user accounts and groups after installation. PME supports Windows
users and groups for integration with Windows and Active Directory.

For information on creating users and user groups, and on setting user access levels, see User
Manager help.

7EN42-0168-00 Page 44
Cybersecurity IT Guide

Change the SQL Server Express sa account password

If SQL Server Express is installed, with Mixed Mode authentication, through the PME installer,
change the sa account password after the installation is complete.

Application control (whitelisting) software

McAfee Applicaton Control is a dynamic whitelisting program that is used to prevent unauthorized
applications from running on your system.

When you deploy Application Control to protect a system, it scans the system and creates a
whitelist of all executable binaries and scripts present on the system. The whitelist also includes
hidden files and folders.

The whitelist lists all authorized files and determines trusted or known files. In Enabled mode, only
files that are present in the whitelist can execute. All files in the whitelist are protected and cannot
be changed or deleted. An executable binary or script that is not in the whitelist is said to be
unauthorized and is prevented from running.

Consider the following when using application control software with PME:

l Complete the system configuration before before setting up and enabling application control
software.

l Any program or script that should be able to update the system will need to be configured as an
updater.

l After solidification, no driver packs or summary report packs may be installed.

l Disable Application Control to make changes to the system. Enable it again after the change.

l Follow the instructions in the Application Control product guide.

Operation
Session timeout
PME automatically times out inactive client sessions. Web Applications clients are logged out and
Windows application clients (Vista, Designer, Management Console) are locked after a period of
inactivity. The timeout period is configurable, it is set to 20 minutes by default. See Configuring
session timeout settings for details.

To restart or unlock the session you must enter the login credentials. A session is considered
inactive, if none of the following actions are detected:

l Mouse movement

l Mouse click

l Keyboard activity

l Touch screen activity

NOTE: If custom content links are added to the Web Applications framework, then the custom
content must either implement the idle detection, or activity on that content is not registered and
the Web client session can time out unexpectedly. See Adding idle detection to custom Web
Application links for details.

Page 45 7EN42-0168-00
IT Guide Cybersecurity

Administration
Windows and SQL Server Updates
Critical and routine Windows and SQL Server updates can be applied to the operating systems
hosting the PME server and clients without prior approval by Schneider Electric.

User account maintenance

Review PME user accounts on a regular basis. Update passwords and user permissions, and
remove unused accounts as required.

7EN42-0168-00 Page 46
Reference IT Guide

Reference
Use the links below to find the content you are looking for:

Accounts and services

Databases
Trial license limitations
Database growth calculations
Configuring session timeout settings
Adding idle detection to custom Web Application links

Page 47 7EN42-0168-00
IT Guide Reference

Accounts and services

Windows accounts
The following tables provide information on the Windows accounts used by Power Monitoring
Expert (PME):

User/Account Role/Group/Permissions Notes

- No group membership. - Automatically created during the installation of
- Has PME.
IONUser
List/Read/Write/Execute - Used to run report subscriptions.
(account)
permissions on the PME - Needs access to the folder where subscriptions
share folder. are saved.
- Automatically created during the installation of
IONMaintenance PME.
Member of Users group
(account)* - Used to run database maintenance jobs in
Windows Task Scheduler.
- Manually created by the user.
Needs to be a member of
Login used to run - Used to log into Windows to run the PME installer
local Administrators
the PME installer - If possible, the local Administrator account should
group
be used.
Login used to - Manually created by the user.
Needs to be a member of
access PME - Used to log into Windows to run the PME Web
Users group
applications Applications or Engineering Client applications.
- Manually created by the user.
Login to run Needs to be a member of
- Used to log into Windows to run PME application
application local Administrators
engineering tools. An example is the Configuration
engineering tools group
Manager Tool, used for system upgrades.
- Manually created by the user.
Login to run the Needs sysadmin - Used to log into Windows to run the PME
Database permissions on SQL Database Manager tool.
Manager tool database instance. - This Windows account needs to be added to the
SQL server database.
Must have access to the database folder(s) and the
SQL Server NT
installer user’s Temp folder during installation.
Agent service AUTHORITY\SYSTEM
Permissions can be lowered after PME is installed.
SQL Server Must have access to the database folder(s) and the
NT
Database installer user’s Temp folder during installation.
AUTHORITY\SYSTEM
Engine service Permissions can be lowered after PME is installed.

* This account is only created on standalone servers where the SQL Server software and PME are
installed on the same computer.

For installations using SQL Integrated Authentication, the following additional accounts and
permissions are required.:

User/Account Role/Group/Permissions Notes

7EN42-0168-00 Page 48
Reference IT Guide

- Needs to be a member
Account used of local Administrators
for group - Manually created by the user.
SQL Integrated - Needs 'Log on as a - Used by PME to access the SQL server databases.
Authentication service' privilege on
application server
This is not an additional user account. It is just an
Login used to added requirement for the Logins used to access the
access PME Needs sysadmin server Engineering Client applications (Vista, Designer,
Engineering role for the PME Management Console, Management Console tools).
Client databases.
applications The PME databases are: ApplicationModules, ION_
Data, ION_Network, ION_Systemlog

NOTE: When PME is installed with SQL Integrated Authentication, then the Windows account
that is used to access the database, is also used to run the PME services and the IIS Application
Pools.

Page 49 7EN42-0168-00
IT Guide Reference

SQL Server accounts

The database server hosts several databases for Power Monitoring Expert (PME). The following
tables lists the SQL Server logins and permissions created for PME:

For installations with Mixed Mode Authentication:

Server
Login Authentication Database Membership
Role
AMUser SQL Public ApplicationModules AMApplicationRole
ApplicationModules db_owner
ION_Data db_owner
ION_Network db_owner
ION SQL Public ION_SystemLog db_owner
SQLAgentOperatorRole,
msdb * SQLAgentReader Role, SQL
AgentUserRole
ION_Data ION_DSD_Reader
ionedsd SQL Public
ION_Network NOM_DSD_Reader
db_backupoperator, db_
ApplicationModules
ddladmin, Maintenance
db_backupoperator, db_
ION_Data
ddladmin, Maintenance
IONMaintenance** Windows Public
db_backupoperator, db_
ION_Network
ddladmin, Maintenance
db_backupoperator, db_
ION_SystemLog
ddladmin, Maintenance

* In SQL Standard version only.

** This account is only created on standalone servers where the SQL Server software and PME are
installed on the same computer.

For installations with SQL Integrated Authentication:

Server
Login Authentication Database Membership
Role
ApplicationModules db_owner
ION_Data db_owner
Account used for ION_Network db_owner
SQL Integrated Windows Public ION_SystemLog db_owner
Authentication SQLAgentOperatorRole,
msdb* SQLAgentReader Role,
SQL AgentUserRole

7EN42-0168-00 Page 50
Reference IT Guide

db_backupoperator, db_
ApplicationModules
ddladmin, Maintenance
db_backupoperator, db_
ION_Data
ddladmin, Maintenance
IONMaintenance ** Windows Public
db_backupoperator, db_
ION_Networks
ddladmin, Maintenance
db_backupoperator, db_
ION_SystemLog
ddladmin, Maintenance

* In SQL Standard version only.

** This account is only created on standalone servers where the SQL Server software and PME are
installed on the same computer.

NOTE: When PME is installed with SQL Integrated Authentication, then the Windows account
that is used to access the database, is also used to run the PME services and the IIS Application
Pools.

Other
PME must have access to the master and tempdb System Databases.

The PME Database Manager tool requires that the Windows account that is used to run it has
sysadmin permissions on the PME SQL Server instance. The Database Manager is an optional
tool, used for managing the PME databases.

Page 51 7EN42-0168-00
IT Guide Reference

PME Windows services

All PME applications without a user interface run as Windows services. The following table lists all
PME services:

Startup Log on
Service Name Description
type Account
Receives and processes
high-priority alarm and
event notifications
coming from modem
connected meters on
remote power monitoring
locations. When this
Local
ION Alert Monitor Manual happens, the Alert
System *
Monitor initiates a
communications
connection to the remote
modem site to download
additional logged data
(for example, data,
events, and waveforms).
Allows the Event
Notification Module
(ENM) to read alarms
ION Application directly from the ION_
Local
Modules Alarm Manual Data database.
System *
Services Host Starts on demand from
other services (for
example, from the Event
Notification Module).
Hosts common web
ION Application
Local services used by the
Modules Core Automatic
System * Web Applications
Services Host
component.
Hosts web services that
provide low-level access
to system data (that is,
ION Application
Local real-time, historical,
Modules Data Automatic
System * alarming, and
Services Host
authentication) for the
Web Applications
component.

7EN42-0168-00 Page 52
Reference IT Guide

Hosts web services that

ION Application
Local provide data processing
Modules Provider Automatic
System * for the Web Applications
Engine Host
component.
ION Cloud Agent Local Manages interaction with
Automatic
Service System * cloud services.
Locates local and remote
product components.
ION Component Local Starts shortly after
Manual
Identifier Service System * startup by request of
ION Connection
Management Service.
Determines the
connection status of
sites and devices in the
system, and handles
allocation of resources
such as modems. This
service manages the
state of site and device
connectivity for the
system. In order to
establish the most
ION Connection appropriate state for the
Local
Management Manual system, each
System *
Service connection and
disconnection request is
evaluated against the
overall state of the
system and availability
of communications
channels.

Starts shortly after

startup by request of
ION Network Router
Service.

Page 53 7EN42-0168-00
IT Guide Reference

Collects basic, non-

identifying information
from the Power
Monitoring Expert
ION Diagnostics and Local system and uploads it to
Automatic
Usage Service System * a secure location on the
cloud for data mining by
Schneider Electric.
Customers can opt-in or
opt-out at any time.
Monitors system events
ION Event Watcher Local for conditions specified
Automatic
Service System * in Event Watcher
Manager.
Provides historical data
collection for the power
monitoring system (that
ION Log Inserter Local
Automatic is, devices and Virtual
Service System *
Processor), and stores it
in the ION_Data
database.
Transfers data received
Automatic
ION Log Subsystem Local from power monitoring
(Delayed
Router Service System * devices to storage and
Start)
processing.
This service is used to
create individual real-
ION Managed Circuit Local
Automatic time and historical data
Service System *
sources for multi-circuit
meters.

7EN42-0168-00 Page 54
Reference IT Guide

Routes all ION requests

between the software
components, such as
client workstations, the
Real Time Data Service,
Log Inserter, and the
Query Server. The
ION Network Router Local service dynamically
Automatic
Service System * detects changes to the
network configuration,
including the addition of
new servers. It can also
recognize new software
nodes, such as Vista,
that are added to an
existing server.
Serves real-time OPC
data (that is, OPC DA) to
OPC client applications.
ION OPC Data Local
Manual Starts on an OPC client
Access Server System *
request for data, if the
OPC DA server license
has been activated.
Translates power quality
data from the ION_Data
ION PQDIF Exporter Local database into PQDIF file
Manual
Service System * format and manages
scheduled PQDIF
exports.
Provides historical data
retrieval from the ION_
Local Data database for client
ION Query Service Automatic
System * applications (for
example, Vista and
Diagrams).
Manages and provides
access to real-time data
ION Real Time Data Local
Automatic for all client applications
Service System *
(Vista, Diagrams,
Trends, and so on).

Page 55 7EN42-0168-00
IT Guide Reference

Runs Reports
subscriptions according
Automatic to user-defined
ION Report Local
(Delayed schedules.
Subscription Service System *
Start)
Starts several minutes
after the server starts.
Manages
communication links to
and from the product.
ION Site Service is
responsible for handling
packet communications
to system devices and
controlling direct device
communications. The
Local
ION Site Service Automatic service reacts to
System *
changes in network
configuration: for
example, changes to
certain channels,
configuration
parameters, ports, or
device parameters can
often interrupt a
connection.
Performs evaluations
Automatic
ION Software Data Local based on real time data
(Delayed
Processing Service System * from the power
Start)
monitoring system.
Enables software data
services via
ModbusTCP/IP, and is
ION Software
Local treated like a device in
Modbus Gateway Manual
System * Management Console.
Service
For example, the Circuit
Breaker Aging Service
uses this service.
Provides aggregation,
ION Virtual control, and
Local
Processor Service - Automatic mathematical analysis of
System *
[Link] power monitoring
system data.

7EN42-0168-00 Page 56
Reference IT Guide

Serves data for the

Power Quality
ION Virtual Performance diagrams.
Local
Processor Service – Automatic Functions only when the
System *
[Link] Power Quality
Performance module is
licensed and configured.
Manages subscriptions
to XML data for Vista
user diagrams. This
service is used only by
the Diagrams
application. When you
ION XML Local
Automatic open a Vista user
Subscription Service System *
diagram in a web
browser, the ION XML
Subscription Service
creates a subscription
and delivers the real-time
data in XML format.
Stores XML data
subscriptions for the
ION XML power monitoring
Local
Subscription Store Automatic devices on the network.
System *
Service This service is used only
by the Diagrams
application.
This service runs the
Local
ImadminSchneider Automatic FlexNet Publisher
Service
License Server Manager.
Provides storage,
processing and
controlled access of
data, and rapid
Local transaction processing
SQL Server (ION) Automatic
System * for the ION_Data, ION_
Network, ION_
SystemLog, and the
ApplicationModules
databases.
Provides scheduling for
report subscriptions in
SQL Server Agent Local non-SQL Server Express
Automatic
(ION)** System * systems. (This service
is not part of SQL Server
Express.)

Page 57 7EN42-0168-00
IT Guide Reference

* When PME is installed with SQL Integrated Authentication, then the Windows account that is
used to access the database, is also used to run the PME services, instead of the Local System
account.
** This service only exists on systems with SQL Server, not SQL Server Express.

7EN42-0168-00 Page 58
Reference IT Guide

IIS Application Pools

The Power Monitoring Expert installer enables and configures IIS to host the different Web
applications. The following table lists the application pools and applications:

Application Pool Identity Application

Dashboards

EWS (Ecostruxure Web Services)

Hierarchy Manager
Application Modules App
Local System * Slideshow
Pool
System Data Service

Trends

Web
Alarm Configuration

ION ION/diagrams
ION App Pool Local System *
ION Report Data Service

Web Services
Rate Editor
Web Reporter App Pool Local System *
Reporter

* When PME is installed with SQL Integrated Authentication, then the Windows account that is
used to access the database, is also used to run the IIS Application Pools, instead of the Local
System account.

Page 59 7EN42-0168-00
IT Guide Reference

Databases
PME Databases
Power Monitoring Expert (PME) uses four databases to store device communication parameters,
system configuration settings, and logged historical data.

ION_Network database
Sometimes called the NOM (Network Object Model), the ION_Network database stores device
information, such as, device name, device type and connection address (for example, IP address
and TCP/IP port or device/Modbus ID). It also contains information about the optional Application
Module settings, other ION Servers, Sites, Dial Out Modems, and Connection Schedules. There is
only one ION_Network per system.

ION_Data database
The ION_Data database contains the historical data, events and waveforms from devices
connected to the system. This includes: onboard logging configured on devices; and, PC-based
logging configured in the device translators and the Virtual Processors.

Application Modules database

The Application_Modules database contains configuration settings (for example, layouts, colors,
application events, and so on) and cached historical data for some of the Web Applications (for
example, Dashboards and Trends).

ION_System log database

The ION_SystemLog database holds system events and their timestamps, which is accessible to
view in Management Console. Event priorities can range from 0-255 and are grouped into
Diagnostic (0 - 5), Information (6 - 20), Warning (21 - 63), Error (64 - 191), and Critical (192 - 255)
categories. System events can include:

l ION Service stopped or is starting or user connection to an ION Service is lost.

l Device has been declared offline / online.

l ION Site Service connected, disconnected or failed to a Site in Management Console.

l ION User logs on / off Vista or Designer.

l ION User saves a Vista or Designer node diagram.

l Plus many other Warnings and Errors relating to PME system functions.

7EN42-0168-00 Page 60
Reference IT Guide

Trial license limitations

The following features and functions are not enabled by the trial license:

Reports:

l Generator Test EPSS Report

l Generator Battery Health Report

l Generator Battery Health Export

l Generator Activity Report

l UPS Auto Test Report

l UPS Battery Health Report

l Generator Load Summary Report

l Consumption Ranking Report

l PUE Summary Report

l Isolated Power Report (ANSI)

l Isolated Power Report (IEC)

l Energy by IT Customer

l Branch Circuit Power

l Generator Capacity Report

l UPS Power Report

l Equipment Capacity Report

l Generator Power Report

l Power Losses Report

Page 61 7EN42-0168-00
IT Guide Reference

Database growth calculations

Factory default measurement logging
A measurement record in the database uses approximately 75 bytes of disk space. Based on the
factory default data logging configurations, we can calculate the database growth for data logged
from different device types.

Example

Device Daily Growth Number of Total Daily Total Annual

Type Rate (kB) Devices Growth (MB) Growth (GB)
ION7650 780 10 7.62 2.72
PM8000 950 20 19.00 6.94
PM3200 85 70 5.81 2.07
TOTAL - 100 32.43 MB 11.84 GB

NOTE: Use the Database Growth Calculator tool to estimate the database growth for your
system. The tool is available through the Exchange Community. See Resources for link
information.

Custom measurement logging

Custom measurement logging can be configured in the monitoring devices and, as software based
logging, in PME. A measurement record in the database uses approximately 75 bytes of disk
space.

The following shows the database growth estimate for logging of a single measurement every 15
minutes:

NOTE: Use the Database Growth Calculator tool to estimate the database growth for your
system. The tool is available through the Exchange Community. See Resources for link
information.

Power quality event logging

Power quality (PQ) events and waveform capture recording is event driven, which makes it
impossible to accurately predict their impact on database growth. In our experience, power quality
data accounts for approximately 10% - 20% of the total database size.

7EN42-0168-00 Page 62
Reference IT Guide

NOTE: Use the Database Growth Calculator tool to estimate the database growth for your
system. The tool is available through the Exchange Community. See Resources for link
information.

Page 63 7EN42-0168-00
IT Guide Reference

Configuring session timeout settings

PME automatically times out inactive client sessions. Web Applications clients are logged out and
Windows application clients (Vista, Designer, Management Console) are locked after a period of
inactivity. The timeout period is configurable, it is set to 20 minutes by default.

To configure the session timeout settings:

1. From a PME Web client, browse to [Link] host-

name>/systemdataservice/timeoutsettings, to open the Session Timeout Settings
page.

2. On the Session Timeout Settings page, enter the timeout period for Web clients and Windows
clients.

3. Click Save.

4. Restart Internet Information Services (IIS) on the PME server.

5. Restart any Web Applications client browser sessions.

Related Topic:

l Adding idle detection to custom Web Application links

7EN42-0168-00 Page 64
Reference IT Guide

Adding idle detection to custom Web Application links

PME automatically times out inactive client sessions. If custom content links are added to the Web
Applications framework, then the custom content must implement the idle detection, or activity on
that content is not registered and the Web client session can time out unexpectedly.

Prerequisite: The custom application must be in the same Application Pool as the regular PME
applications, and must use the same authentication configuration.

To add idle detection to custom content:

1. In the custom Web application, Add references to jquery and [Link].

2. Create an IdleDetection object when the document has loaded.

NOTE: If you want your application to take part in keeping PME non-idle, but you do not want
your application to log itself out after the idle period, you can add the following JSON as a
parameter to the idle() method: {enableLogoutRedirection: false;}

Example [Link] for an application in the PME Application Pool:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<[Link]>
<compilation debug="true" targetFramework="4.6" />
<httpRuntime targetFramework="4.6" requestValidationMode="2.0"
enableVersionHeader="false" />
<authentication mode="Forms">
<forms name=".APPLICATIONFRAMEWORK"
loginUrl="/SystemDataService/Auth"
defaultUrl="/SystemDataService/Auth/GenerateAuthUrl" timeout="2880"
protection="All" enableCrossAppRedirects="true" />
</authentication>
<machineKey decryption="AES" decryptionKey="AutoGenerate"
validation="HMACSHA256" validationKey="AutoGenerate" />
<authorization>
<deny users="?" />
</authorization>
</[Link]>
</configuration>

Example minimal page that has idle detection added to it:

Page 65 7EN42-0168-00
IT Guide Reference

Related Topic:

l Configuring session timeout settings

7EN42-0168-00 Page 66
Schneider Electric
35 rue Joseph Monier
92500 Rueil Malmaison – France

Phone: +33 (0) 1 41 70 00

[Link]

As standards, specifications, and designs change from time to time, please

ask for confirmation of the information given in this publication.

© 2018 Schneider Electric. All Rights Reserved.

7EN42-0168-00 09/2018