EcoStruxure™

Power Operation 2021 with Advanced

Reporting and Dashboards
System Guide
7EN02-0462-03
08/2022
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 System Guide

Contents
Contents 4
Safety Precautions 28
Support and version information 29
Documentation 29
Version information 29
Other support 29
Version Information 29
What's new 30
Support contacts 34
Plan 35
For designers with a Citect background 35
Components and single-site architectures 36
Components overview 36
Time synchronization 37
Power Operation Server component 38
Server component architecture 39
Built-in architectural redundancy 39
Making changes while online 40
Ethernet network redundancy 40
Power Operation Client Access component (HTML5 client) 40
Client Access component architecture 41
Event Notification Module component 43
Advanced Reporting and Dashboards component 44
Advanced Reporting and Dashboards architectures 44
Additional Advanced Reporting and Dashboards Modules component 47
Activating software module licenses 48
Mapping EcoStruxure Power to Advanced Reporting modules 48
Multi-site architectures 50
Connected devices and protocols 52
Power Operation Tool Suite 53
Waveform file share access and permissions 54
Supported power devices 55
Computer requirements 56
Server CPU and RAM requirements 56
Client CPU, RAM, and disc requirements 58
Server disk storage 59
Network requirements 59
Supported operating systems 60
Supported SQL Server versions 60
Virtualization 61
Web Client versus Thick Client 62

Page 4 of 1312 7EN02-0462-03

System Guide Contents

Translation 64
Commercial references 66
Integrating with Advanced Reporting and Dashboards 67
Advanced reporting customizations 68
Device communication 69
Single-mastering devices 70
Multi-mastering devices 71
Interoperability 72
Power Operation OPC UA 72
EcoStruxure Building Operation 74
EcoStruxure Web Services (EWS) 76
Power Operation OPC DA 76
Extending Power Operation 78
Smart Connector Overview 79
Smart Connector Architectures 80
Smart Connector Requirements 82
Smart Connector Virtualization 82
EcoStruxture Anywhere 83
EcoStruxture Anywhere component 83
EcoStruxture Anywhere architectures 85
OFS system time stamping 88
Architecture selection 90
Time synchronization 92
Event resolution 94
SOE architecture design 95
Data flow design 96
Install and upgrade 97
Getting the latest version of Power Operation 97
Installing 97
Before installing 98
Supported environments 99
Compatible Windows Operating Systems 99
Windows OS and Server configuration 100
IIS configuration 100
SQL Server 102
Windows Services in Power Operation 102
Preparing servers 102
Component selection 102
Core components selection 103
Add-ons selection 103
System software order of installation 104
Installing the software 106
Installing the ETL Administration Tool 107

7EN02-0462-03 Page 5 of 1312

Contents System Guide

Install Power SCADA Anywhere Server 108

Installing CAE 109
After installing the software 110
Maintaining system currency 110
Getting started with Power Operation 110
Uninstall and reinstall Power Operation 110
Upgrading 111
Upgrade method 113
Upgrade path 113
Offline upgrade 114
Offline upgrade in test environment 120
Migrating to production 121
Troubleshooting offline upgrade 122
Online upgrade 122
Upgrading from v2020 and v2020 R2 125
Upgrading from v8.1 and v8.0 SR1 125
Upgrading from v7.30 SR1, v7.40, v7.40 SR1 and v8.0 128
Upgrading from v7.20 and v7.20 SR1 131
Troubleshooting online upgrade 134
Migration Tools 135
Using the Power Operation Migration Utility 135
Using the Plant SCADA Migration Tool 139
TGML Upgrade Utility 141
Remove obsolete memory and alarm devices 142
Memory devices 142
Alarm devices 142
Converting memory variables 143
Inserting new local variables 143
Deleting variable tags 143
Deleting obsolete I/O devices 144
Creation of roles for existing users 144
Migrate included projects 144
Default scale 145
Verify notifications 145
Migrating from Plant SCADA (formerly Citect SCADA) 145
Backing up and restoring a Power Operation system 146
Backing up a Power Operation system 147
Before you begin 147
Installation media and license backup 147
Backup directory location 147
System passwords 147
Backing up Power SCADA 147
Backing up Power Operation automatically 148

Page 6 of 1312 7EN02-0462-03

System Guide Contents

Backing up the Power Operation passwords and device profiles 149

Power Operation Server password 149
Device Profiles 151
Backing up redundant Power Operation systems 151
Backing up Power Monitoring Expert 151
Power Monitoring Expert databases 152
Power Monitoring Expert config folder 152
Power Monitoring Expert diagnostics 152
Deleting old backups 152
Restoring a Power Operation system 153
Restoring Power Operation 153
Restoring Power Operation from an automated backup 153
Restoring a redundant Power Operation system 154
Restoring Power Monitoring Expert 154
Replace the Config Folder 155
Connect the old databases 155
Detach the default databases 155
Remove, rename, or delete the factory databases 156
Restore the databases from the old system 156
Start the Power Monitoring Expert services 160
Post-restoration checks 160
Backing up and restoring scripts 160
Backing up and packaging archive files 160
Restoring and unpackaging archived files 162
Licensing 163
License keys 163
Activating licenses 165
Dynamic Point Count 165
Specify the required point count for a computer 167
Run the software in demo mode 167
Configure 168
Configuration prerequisites 169
Changing configuration on a running system 169
Server CPU load balancing 171
Configuration tools 171
Application Configuration Utility 172
Application Services Host—Citect Data Platform 173
Set up data acquisition parameters 174
Configuring service layer components 175
Profile Editor typical workflows 177
Profile Editor main menu options 180
SCADA Projects 181
Before you add a project 182

7EN02-0462-03 Page 7 of 1312

Contents System Guide

Add a project using Project Setup 182

Launch Project Setup 182
System Definition 183
Servers and Web Client 184
Users 186
Menus and Display Pages 187
Summary 188
Device Profiles 188
Devices 190
Finish 190
Project Setup – Changed Parameters 191
Compile the project 193
Restoring a project 194
Backing up a project 195
Delete information from Power Operation 195
Devices 196
Profile Studio overview 196
Profile Studio setup 196
IEC 61850 engineering workflow 196
Configuring devices for IEC61850 compliance 197
Configuring equipment 198
Configuring datapoints 199
Associating datapoints with profiles 201
Customizing datapoint descriptions in Profile Studio 202
Associating device links 202
Creating virtual datapoints 203
Generating reports 204
Including enum tag state values for export 206
Exporting configuration packages 206
Comparing templates 208
Configuring Profile Studio settings 208
The Profile Editor 209
Launch the Profile Editor 210
About device profiles and tags 211
Reviewing default device types and tags 211
Supported device types and protocols 211
Define Device Type Tags 212
Define Device Type Tags tab 213
Managing device types 217
Edit a device type 219
Delete a device type 220
Assign tags to generic I/O points 220
Create custom device types 221

Page 8 of 1312 7EN02-0462-03

System Guide Contents

Printing the .CSV file 221

Managing device type categories 221
Edit functional addresses 223
Creating custom tags 224
Editing tag addresses 224
Edit generic tag addresses 230
Setting up custom tags 230
Edit a custom tag 234
Delete a custom tag 234
About tags 234
Tag naming convention 235
Define an enumeration 236
Format code definitions 237
About logic codes 240
Block writes 241
How do drivers work? 241
Create Device Profiles 242
Create Device Profiles tab 242
Enable Waveforms 244
Managing device profiles 245
IEC 61850 system setup workflow 248
Create IEC 61850 Device Type 248
Managing IEC 61850 datasets 250
Edit IEC 61850 Report control blocks 251
Edit driver parameters 253
Set Up Trend Intervals 253
Select Trend Intervals 254
Trend tag scan intervals 254
Disk storage calculation for trends 255
Create composite device profiles 255
Creating a third party Modbus Device Type 255
Creating a composite device type 256
Creating a data concentrator 258
Setting up a G3200 gateway 259
DNP3 protocol support 260
Set Up Projects 260
Set Up Project screens and workflow 261
About project files 262
Add, edit, or delete a project 262
Customize tag names 264
Add project parameters 264
Export a project 265
Edit and delete information in a project 266

7EN02-0462-03 Page 9 of 1312

Contents System Guide

Import and export project files 266

Before you export a project 266
Profile Editor export 267
Moving files when the Profile Editor is not on the server 267
SCL export 268
Reuse projects created in the Profile Editor 268
Import files into the Profile Editor 269
Import Filter screen 271
Import Reconciliation screen 272
Re-match Items within a Logical Node 274
Using import templates 275
Manage I/O devices in a project 277
Before adding I/O devices 277
Port names 277
Add Redundant NetworkTagsDev and zOL Devices 278
Define one I/O device in a project 279
Adding a TCP device 279
Adding a serial device 281
Adding a DNP3 TCP device 282
Adding an IEC 61850 device 283
Adding and configuring SNMP devices 284
Removing an I/O device from a project 287
Define multiple devices using a CSV file 288
Create a CSV file to add multiple devices 288
Add multiple devices to a project using a CSV file 291
CSV file samples 292
Updating devices in a project 293
Compile the project 294
Work with alarms 294
Alarms overview 294
Add setpoints and delays 295
Set up an alarm based on an enumeration 295
Change an alarm severity 295
Waveform management 296
Waveform storage 296
Waveform database and special waveform tags 297
Enabling waveforms for onboard alarms 297
Set parameters for event log length and historical logging of events 298
Adding an onboard alarm tag 298
Set up audible alarms 298
Power Operation Runtime 300
Open firewall ports for Power Operation Runtime 300
Power Operation Runtime menus 300

Page 10 of 1312 7EN02-0462-03

System Guide Contents

Add pages to project Menu Configuration 301

Add one-line pages 302
Adding Alarm Pages 302
Add the Tag Viewer page menu item 303
Add Menu Items for LiveView Data Tables 303
Add a Page menu item to Launch a WebDiagram 304
Basic Reports 305
Set up the Power Operation Runtime for basic reports 306
Set up a display client for basic report viewing 307
Enable Windows Authentication for basic reporting 307
Configure email settings to send basic reports 308
Configure basic reports for email 309
Email basic reports 310
URL routing for basic reports 313
Set up IEC 61850 advanced control 313
Create Real-Time Data Views 314
LiveView Viewer 314
Where's My Device? 316
Set up LiveView 317
Create menu item for LiveView page 318
Create a LiveView template 319
LiveView Formatting 319
LiveView Placeholders 320
LiveView Formulas 321
LiveView Thresholds 322
Modify LiveView template 323
Duplicate LiveView template 323
LiveView delete 323
Enable Windows Authentication for LiveView 324
Compile the Project and Launch the Power Operation Runtime 325
Notifications 325
Prerequisites 326
Migrate notifications 327
Configure notifications 328
Configuring the Email Server 328
Configuring SMS Text Notification 328
Notifications Settings 330
Using Maintenance Mode 330
Create notifications 331
Notification components 332
Managing notification components 332
Creating a notification workflow 332
Opening Notifications Settings 333

7EN02-0462-03 Page 11 of 1312

Contents System Guide

Notifications in a redundant system 334

Creating a notification 334
About Alarm Filters 335
Creating basic alarm filters 341
Creating advanced alarm filters 342
Adding alarm filters to a notification 346
Managing Contact Groups 347
Managing recipients 350
Set schedules 350
Managing schedules 350
About Message Templates 351
Adding a message template 351
Managing message templates 352
Enabling and testing notification delivery 352
Managing notifications 353
Renaming a notification 353
Duplicating a notification 353
Deleting a notification 354
Suppressing floods 354
Creating summary notification reports 355
Troubleshooting notifications 356
Notification reports 356
Notifications Settings FAQs 356
Web Applications 357
Alarms configuration 357
Adding a new Alarms view 359
Copying an Alarms view 359
Editing an Alarms view 360
Moving an Alarms view 361
Deleting an Alarms view 361
Setting a default Alarms view 361
Creating alarm menus 362
Exporting alarm menus 368
Importing alarm menus 370
Diagrams configuration 374
Graphics pages 374
Graphics pages prerequisites 374
Adding graphics pages 375
Adding custom components 376
Changing the background color of a graphics page 377
Changing the background color of a component 377
Defining the Diagrams menu structure 377
Interactive TGML graphics 378

Page 12 of 1312 7EN02-0462-03

System Guide Contents

Turning off credential requirements for control components 379

TGML Sample to User Interactive Write 380
Conditional Write 390
On Demand Read 396
Single or Multiple DataPoint Write 400
Write and Confirm 407
Write and Confirm User Interactive 414
User Input Write Operation 421
Analog Write Operation 429
Read and Write Alarm Properties 435
Alarm property keywords 438
Linked TGML graphics 438
TGML templates 438
Configuring MTZ graphics devices 439
Creating TGML graphic pop-ups 439
Updating a generic pop-up to an MTZ device pop-up 444
Rendering error conditions in PopUp using presentation value 445
Rendering error conditions in PopUp using getValue() function in script 446
Invoking a PopUp 447
WebReach Diagram Design 448
Rendering error conditions in WebReach Diagrams 448
Configuring a NewTab component 449
Configuring a NewWindow component 451
Opening links from TGML components 453
Opening URL links in Web Applications 458
Invoke function 467
Adding a diagram to the menu bar 484
TGML snippets 487
TGML snippet examples 488
Control snippet example 490
Link snippet example 503
NewTab snippet example 508
NewWindow Snippet 514
PopUp snippet example 519
URL snippet example 526
URL in Same Window 531
Advanced Tag Debugger 536
Configuring the Advanced Tag Debugger 536
Opening the Advanced Tag Debugger 538
Using the Advanced Tag Debugger 540
Reading a data point 540
Writing data points 542
Advanced one-line diagrams 543

7EN02-0462-03 Page 13 of 1312

Contents System Guide

Advanced one-line flow chart 543

Creating a one-line on a graphics page 544
Configuring a meter 545
Configuring a source 545
Configuring a circuit breaker or switch 546
Configuring an automatic transfer switch (ATS) 546
Configuring a transformer 547
Configuring a motor 547
Enable lockout/tagout 548
Assigning one-line colors 549
Multi-Source Coloring 549
Alarm integration 550
Designing an Alarm TGML 550
Alarm count grouping 551
Trends configuration 551
Adding a new trend 552
Editing a trend 553
Sharing a trend 553
Moving a trend 554
Deleting a trend 554
Web Applications settings 555
Alarm Views 555
Personal Preferences 557
System localization 557
System Theme 557
Authorized Hosts 559
Session timeout 560
Web redundancy 560
Applications 562
Thermal Monitoring of Medium Voltage Substations Application 563
Overview 563
Components 563
Prerequisites 563
Limitations 564
Design 564
Configuration 565
Adding a thermal monitoring Include to a Power Operation Project 565
Configuring a thermal monitoring device profile 566
Adding a thermal monitoring Device to a Power Operation project 568
Configuring a thermal monitoring device popup in a graphic 575
Waveform Extractor 578
Configuring the Waveform Extractor 578
Exporting waveform configurations 579

Page 14 of 1312 7EN02-0462-03

System Guide Contents

Configuring a Waveform Extractor project 583

Customize default behaviors 587
Customize a project using Cicode 587
PLSProviderEngine.ci Module 587
Clear cache and refresh platform 589
Localizing Power Operation 590
Localizing Power Operation Runtime 591
Localizing SCADA applications 592
Translating device information 593
Running Power Operation as a Windows Service 593
Configuring the Power Operation service 594
Windows Service Operation 595
Launch Power Operation from a Remote Client 595
System startup and validation checks 597
Log in with YubiKey 597
Verify that I/O Devices are Communicating 597
Distributed systems 602
Setting up more than two I/O Servers per cluster 602
Using single sign-on and passwords 604
Add single sign-sn settings to Citect.ini 604
Configure Single Sign-On (SSO) 605
Certificate requirements for webpages 606
Set up the Advanced Reporting and Dashboards Server 607
Install Advanced Reporting and Dashboards Module 607
Add Devices on Advanced Reporting and Dashboards server 607
Configure ETL 608
Adding Advanced Dashboards and Reports into Web Applications 608
Setting up trusted certificates between PO and Advanced Reporting 609
Add advanced dashboards and reports into Power Operation Runtime 614
Add the WebReach Server Parameter 614
Get the Advanced Reports Report ID 614
Getting the device name and testing the WebReach Diagrams URL 615
Add the Advanced Reports Root Page Menu Item 615
Add Advanced Reports page menu items 616
Add the Dashboards Page Menu Item 617
Finish Advanced Reports Page Menu Items 618
Add a Menu Item to Open a Web Diagram 618
Finish WebDiagram Page Menu Items 619
Add Web Diagrams to Equipment Popups 619
Add EcoStruxure Building Operation in Web Applications 620
Configure the Power SCADA Anywhere Server 623
Connect to EcoStruxture Anywhere 625
EcoStruxure Web Services setup 626

7EN02-0462-03 Page 15 of 1312

Contents System Guide

Time synchronization 627

Time zone settings 628
OFS system time stamping 628
System time stamping 630
Selection 632
Architecture selection 632
Time synchronization 634
Event resolution 637
Design 637
SOE architecture design 638
Data flow design 639
Configuration 639
PAC configuration 639
OFS configuration 645
Power Operation configuration 646
Implementation 651
PAC implementation 651
Operation 652
Configure Power Operation as an OPC-DA Server 652
Configure Power Operation as an OPC-DA Client 653
Multi-site multi-clustered architectures 654
Server architecture 655
SCADA project structure 656
Project development structure 657
Configuration guidelines 658
Multi-site multi-cluster example projects 660
Setting up a multi-cluster master project 661
Setting up a multi-site master global client project 664
Redundant systems configuration 668
Configure the Power Operation Primary Server 668
Back up the Power Operation Studio project 668
Back up Application Configuration Utility settings 669
Export One-Line Engine Encryption 669
Export and import One-Time Password settings 670
Configure the Power Operation Secondary Server 670
Restore the Power Operation Studio project 671
Import the One-Time Password 671
Import the Advanced One-Line Encryption (AES) File 671
Updating on redundant systems 672
Updating TGML diagrams on redundant systems 674
Updating analog alarm thresholds on redundant systems 675
Cybersecurity 676
IEC 62443 677

Page 16 of 1312 7EN02-0462-03

System Guide Contents

Product defense-in-depth 677

Cybersecurity capabilities 677
Protected environment assumptions 679
Potential risks and compensating controls 680
Hardening 681
Configuring cybersecurity 681
Default security settings 683
Viewing security settings 684
Default port numbers 684
Windows Active Directory 686
Mapping Windows Active Directory groups to CAE 687
Allowlisting 687
Managing certificates 689
Configuring third-party certificates 691
Encryption, locking USB ports, and hardening servers 693
Configuring two-factor authentication 697
Configuring projects for network segmentation 705
Threat Intelligence 705
Using the Security Viewer Filter 707
Cybersecurity Admin Expert 708
Default CAE security settings 710
Enabling CAE cybersecurity 712
Configuring CAE cybersecurity 712
Working with CAE projects 717
Threat intelligence and CAE 720
Windows Updates 721
User accounts and passwords 722
User account roles and privileges 722
Managing user accounts, role names, and mapping 726
Managing user account lockouts and timeouts 728
Passwords 728
Using single sign-on and passwords 728
Two-factor authentication 728
Using CAE for user accounts and paswords 729
Managing CAE user accounts 729
Managing user account lockouts and timeouts 731
Managing CAE passwords 731
Managing CAE user account lockouts and timeouts 733
Managing CAE models 734
Managing CAE user roles 735
Operate 737
Log in to Power Operation Runtime 737
Log in with YubiKey 737

7EN02-0462-03 Page 17 of 1312

Contents System Guide

Interface overview 738

Viewing Alarms and Events 740
Event/Alarm Log Columns Table 743
Alarm/Event filter form 745
Analysis Page 747
Equipment Pop-Up Page 749
IEC 61850 advanced control 753
Tag Viewer 755
Basic Reports 756
Single Device Usage Reports 757
Multi Device Usage Reports 757
Tabular Reports 758
Tabular Report Exports 759
Trend Reports 760
Use basic reports 760
Create and view basic reports 761
Read, Export, Print, and Edit Basic Reports 763
Email basic reports 765
Rapid Access Labels (QR codes) 768
Web Applications 770
Alarms 772
About Alarms 775
Viewing alarms 778
Acknowledging alarms 778
Enable and Disable Alarms 781
Shelve and Unshelve Alarms 782
Creating alarm menus 782
Displaying alarms in the runtime banner area 789
Incidents 792
Viewing incidents 794
Events 794
Viewing events 795
Disturbance Direction 795
Viewing Disturbance Direction 796
Load Impact 796
Viewing Load Impact 797
Load Impact calculations 799
Timeline analysis 799
Viewing a timeline analysis 800
Waveforms 800
Viewing waveforms 801
Waveform Analytics 801
Logging Module 804

Page 18 of 1312 7EN02-0462-03

System Guide Contents

Diagrams 809
Display View 810
Display configuration 812
Designing TGML graphics 814
Designing TGML graphic templates 815
TGML graphics templates for multiple equipment 817
Creating custom scripts for TGML graphics 817
Navigate to associated graphics page 824
Trends 832
Trends configuration 833
Graphics Editor 836
Using Graphics Editor 837
TGML File Format 839
Supported File Formats 839
SVG Support 840
Adjusting the Graphic Work Area 842
Zooming in and out 842
Testing a Graphic 842
Figures Overview 843
Inserting Pictures 844
Adjusting a Picture 845
Adding Text and Textboxes 845
Adding an Animated Picture 847
Attributes Overview 848
Graphic Object Attributes 850
Generic Attributes 850
Inherited Attributes 850
Defining Inheritance 854
Setting Up Inherited Attributes 854
Exposed Attributes 855
Adding an Expose Element 855
Exposing an Attribute 856
Modifying the Behavior of a Component 856
Binds and Links 857
Object Binding 857
Adding a bind 859
Object Linking 860
Adding a Link 860
Dynamic Updates 860
Activating a Binding with a Dynamic Update Attribute 861
Layers Overview 861
Using Layers 863
Controlling Layer Visibility 865

7EN02-0462-03 Page 19 of 1312

Contents System Guide

Groups Overview 865

Using Groups 868
Components and Snippets Overview 870
Components Overview 870
Designing Components 870
Inhibiting Clipping 871
Controlling the Appearance of the Component 871
Grouping Drawing Objects as a Component 872
Adding a Component 872
Creating a new component 873
Editing a Component 873
Saving as a Component 874
Snippets Overview 874
Adding a Snippet 875
Saving as a Snippet 875
Categories Overview 875
Creating a Category 876
Selecting a Category 876
Hiding a Category 876
Displaying a Hidden Category 877
Importing a Components Category 877
Importing a Snippets Category‌ 877
Exporting a Category 877
Troubleshooting 879
Application Services Logging 879
About the Status tool 879
Accessing the Status tool 881
Status tool data fields 881
One-line errors and warnings 893
When alarms do not display correctly 895
Web Applications 897
Frequently Asked Questions (FAQs) 898
Decommission 912
Decommission 912
Decommissioning procedures 913
Reference 920
Upgrade references 920
Cicode Functions 920
Citect.ini Parameters 920
General Upgrade Information 920
Upgrade Information for versions 8.1 and 8.0 SR1 922
Upgrade Information for versions 7.40 and 8.0 926
Upgrade Information for Version 7.30 926

Page 20 of 1312 7EN02-0462-03

System Guide Contents

Upgrade Information for Version 7.20 929

Cicode Functions in version 8.2 931
Cicode Functions in versions 8.1 and 8.0 SR1 932
Cicode Functions in 7.40 and 8.0 933
Cicode Functions in 7.30 935
Cicode Functions in 7.20 943
Citect.ini parameters in 8.2 950
Citect.ini parameters in 8.1 and 8.0 SR1 950
Citect.ini parameters in 7.40 SP1 953
Citect.ini parameters in 7.40 954
Citect.ini parameters in 7.30 955
Citect.ini parameters in 7.20 960
Plant SCADA Migration Information 967
Required Steps 967
Create a New Project 967
Import Citect Customizations 968
Create Device Type Tags and Devices 969
Export Alarm History 969
Enable Waveforms 969
Optional Steps 969
Re-create One-line Animation 970
Add Notifications 970
Add Basic Reports and LiveView 970
Set Up Two-Factor Authentication 970
Configure references 970
Citect INI Parameters 971
Parameters Database 971
General Power Operation parameters 972
Performance Tuning Parameters 979
Security Parameters 986
Waveform parameters 986
Alarm Parameters 988
Data replication parameters 988
Graphics library parameters 989
MicroLogic modules configuration parameters 990
Sepam event reading parameters 992
Sepam device driver INI configuration settings 992
PLC Parameters 993
Logic code definitions 993
Default Genie Library 1025
Deadbands and ignored devices and topics 1034
Add engineering unit templates, units, and conversions 1035
Set up engineering templates and select conversions 1036

7EN02-0462-03 Page 21 of 1312

Contents System Guide

Add or edit a base engineering unit or conversion 1040

LiveView Tables 1043
LiveView Basic Readings Summary 1043
LiveView Power Flow Summary 1044
LiveView Energy Summary 1044
LiveView Energy Readings 1044
LiveView Fundamental Phasor Readings 1045
LiveView THD Current Summary 1045
LiveView THD Voltage Summary 1045
LiveView Uptime Summary 1046
LiveView Incremental Reactive Energy Summary 1046
LiveView Incremental Real Energy Summary 1046
LiveView Harmonic Apparent Power Flows 1047
LiveView Harmonic Reactive Power Flows 1047
LiveView Harmonic Real Power Flows 1048
LiveView Demand Current Summary 1049
Live View Demand Voltage Summary 1049
Notifications references 1049
Notifications UI 1050
Notifications Components UI 1051
Settings and Diagnostics UI 1051
Alarm Filter System Views 1052
Power Modbus (PwrModbus) Driver for Modbus Devices 1052
Benefits of PwrModbus 1053
ETL for Power Operation 1053
Before using the ETL Administration Tool 1054
Allowing ETL remote access to the PO Server 1054
Opening the ETL Administration Tool 1055
Upgrading a PO to PME ETL job 1055
Creating a PO to PME ETL job 1056
Configuring the PO to PME extract task 1058
Grouping 1061
PO to PME ETL job performance 1062
Configuring the PO to PME transform task 1064
Configuring the PO to PME load task 1065
Configuring PO to PME mappings 1069
Editing PO to PME mappings 1071
Tips for working with mappings 1073
Testing your ETL job 1076
Running an ETL job 1077
Manage ETL jobs 1079
Enabling ETL logging 1079
Confirming the ETL job 1080

Page 22 of 1312 7EN02-0462-03

System Guide Contents

Cloning an ETL job 1080

Renaming an ETL job 1081
Removing a task from an ETL job 1081
Switching between ETL jobs 1081
Configuring ETL to accommodate failover 1081
Synchronizing devices 1082
Verifying PO sources in PME 1084
Editing a PO to PME ETL job 1084
Resetting and resending data 1085
Verifying PO data transfer to PME 1086
Web Applications references 1087
Alarms and Incidents customization 1087
System and personal localization settings 1088
Operate references 1089
Alarms references 1090
Alarms UI 1090
Waveforms UI 1102
Timeline Analysis UI 1107
Alarm to Incident Mapping 1110
Alarms terminology 1112
Diagrams references 1114
Library Components 1114
Circuit Breaker 1115
Motor 1116
Switch 1117
Automatic Transfer Switch 1119
Lockout/Tagout 1119
Generator 1120
Transformer 1120
Utilities 1121
Busbar 1122
Trends references 1122
Trends UI 1122
Trends options 1123
Graphics Editor references 1126
Saving a Graphic 1126
Printing Graphics 1126
Graphics Editor Libraries 1127
Graphics Editor Keyboard Shortcuts 1128
Graphics Editor Console 1130
Graphic Object Position 1130
Drawing Tools Overview 1130
Drawing a Line 1131

7EN02-0462-03 Page 23 of 1312

Contents System Guide

Drawing a Polyline 1131

Drawing a Curve 1132
Editing a Curve 1133
Drawing a Polygon 1133
Drawing a Rectangle 1134
Drawing a Square 1135
Drawing an Ellipse 1136
Drawing a Circle 1136
Drawing an Arc or Pie 1137
Editing an Arc or Pie 1138
Editing Text or Textboxes 1138
Graphics Editing Tools Overview 1138
Organizing Objects 1139
Moving Objects 1140
Aligning Objects 1140
Arranging Objects 1141
Distributing Objects 1141
Arranging a table like layout 1142
Duplicating objects 1143
Resizing Objects 1144
Rotating Objects 1144
Skewing Objects 1145
Flipping Objects 1145
Copying an Object 1146
Editing Objects 1146
Deleting an Object 1147
Adding Custom Colors 1148
Gradients Overview 1149
Adding a Linear Gradient 1153
Adjusting a Linear Gradient 1153
Adding a Radial Gradient 1154
Adjusting a Radial Gradient 1154
Adding Animations 1155
Adding Paths 1158
Creating a Text Path 1158
Editing a Text Path 1159
Using the Grid 1159
Documenting and Saving a Component 1161
Graphics Editor 1161
Graphics Editor Menu Bar 1163
Graphics Editor File Menu 1163
Graphics Editor File Menu — New Submenu 1164
Graphics Editor File Menu — Open Submenu 1165

Page 24 of 1312 7EN02-0462-03

System Guide Contents

Graphics Editor File Menu — Save As Submenu 1166

Graphics Editor File Menu — Print Submenu 1166
Graphics Editor File Menu — Settings Submenu 1167
Graphics Editor View Menu 1167
Categories Context Menu 1168
Graphics Editor Drawing Toolbar 1169
Graphics Editor Options Toolbar 1171
Graphics Editor Panes 1174
Equipment Pane 1175
Components Pane 1175
Snippets Pane 1175
Graphics Editor Objects Pane 1176
Graphics Editor Properties Pane 1177
Graphics Editor Statistics Pane 1178
Graphics Editor Test Pane 1179
Graphics Editor Binds and Links Pane 1180
Graphics Editor Layers Pane 1180
Document Properties Dialog Box 1181
Unsupported Characters 1182
Workflows 1182
Configuring Arc Flash Graphics 1190
Control Operation 1192
Configure and operate controls 1192
Setting a component or snippet zoom level 1198
Disabling Zoom for an entire TGML page 1199
Selectively disabling pan and zoom for a TGML page 1199
Pop-Ups 1200
Configure a pop-up 1200
TGML references 1202
TGML Overview 1203
TGML Properties and Attributes 1204
TGML Coordinate System 1205
TGML Rendering Model 1206
TGML Types and Enumerations 1207
Arrays 1209
TGML Code Snippets 1209
TGML Common Attributes 1210
TGML Components 1210
TGML Document Structure 1211
TGML Scripting 1212
TGML About Data Types 1212
TGML Common Event Methods 1213
TGML Mouse Event Methods 1214

7EN02-0462-03 Page 25 of 1312

Contents System Guide

TGML SignalChange Event Methods 1215

TGML DOM Methods 1215
TGML Standard DOM Methods (Commonly Used) 1216
TGML JavaScript Functions 1218
Basic TGML Elements 1223
TGML Document Type Element and Metadata 1223
Document Type Element 1223
TGML Grouping Elements 1225
TGML Grouping: <Group> 1225
TGML Components: <Component> 1225
TGML Layers: <Layer> 1227
TGML Basic Shapes 1228
TGML Line 1229
TGML Polyline 1231
TGML Polygon 1233
TGML Rectangle 1234
TGML Ellipse 1237
TGML Segment Shapes 1239
TGML Elliptical Arc: <Arc> 1239
TGML Elliptical Pie: <Pie> 1241
TGML Elliptical Chord: <Chord> 1242
TGML Curves and Paths 1244
TGML Cubic Bezier Curve 1244
TGML Path Element 1246
TGML Raster Images 1247
TGML Image Element: <Image> 1247
TGML Animated Images (GIF89a): <AnimatedImage> 1248
TGML Text 1249
TGML Text Line: <Text> 1250
TGML Text Flow: <TextBox> 1251
TGML Gradients 1254
TGML Linear Gradient 1254
TGML Radial Gradient 1256
TGML Gradient Stop 1257
Interactive TGML Elements 1259
TGML Transformations 1260
TGML Rotation 1260
TGML Skewing: <SkewX> and <SkewY> 1261
TGML Scaling: <Scale> 1263
TGML Translations: <Translate> 1263
TGML Link Element 1264
TGML Animations 1265
TGML Animation 1265

Page 26 of 1312 7EN02-0462-03

System Guide Contents

TGML Sequences: <Sequence> 1267

TGML Dynamics 1268
TGML Signal Binding 1270
TGML Value Conversion: <ConvertValue> 1272
TGML Text Value Conversion: <ConvertText> 1274
TGML Value Range Conversion: <ConvertRange> 1274
TGML Custom Conversion: <ConvertCustom> 1276
TGML Status Conversion: <ConvertStatus> 1277
TGML Attribute Exposure 1277
TGML Expose Element: <Expose> 1278
TGML Scripting 1278
TGML Script Element: <Script> 1279
TGML Script Context 1281
TGML Target Area Element: <TargetArea> 1281
TGML Appendices 1283
TGML Format Specifications 1283
TGML Appendix A: User-Defined Descriptions of Custom Attributes 1283
TGML Appendix B: TGML View Object 1284
TGML Element Summary 1286
TGML Limitations 1298
Displaying the TGML version 1299
Global Scripts in TGML Graphics 1299
Panel Navigation 1300
Glossary 1302

7EN02-0462-03 Page 27 of 1312

Safety Precautions System Guide

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 or 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.

Page 28 of 1312 7EN02-0462-03

System Guide Support and version information

Support and version information

Documentation
Go to www.se.com, search for Power Operation, and select the Catalogs & User Guides
checkbox. In the search results, you will find the most current versions of:
• EcoStruxure Power Operation Release Notes – PDF

• EcoStruxure Power Operation System Guide – PDF

• EcoStruxure Power Operation IT Guide – PDF

• EcoStruxure Power Operation eBrochure – PDF (What's New)

• Power Monitoring Expert – IT Guide – PDF (Advanced Reporting Module)

Documentation for previous versions can be found on se.com by searching for the version of
Power Operation you have and refining the search results.

See Frequently Asked Questions for links to previous versions of Power Operation Help online.

Version information
See Version information for steps on identifying the version of Power Operation installed.

Other support
• Schneider Electric Exchange:

Design & Quote tools, including:

PO Software Assurance Calculator.

PO Disk Sizing Calculator.

PO Commissioning Time Tool.

EcoStruxture Anywhere documents.

• Documentation for Legacy Graphics Builder can be found in previous versions of Power
Operation Help online. See Frequently Asked Questions for links.
• Go to the AVEVA Knowledge & Support Center website for information on PLANT SCADA or
to generate upgrade authorization codes using the online license generator.
• Go to Schneider Electric Cybersecurity Support Portal for the latest cybersecurity news.
Includes security notifications, and where you can report a vulnerability, or a security or data
privacy event.
• Schneider Electric FAQs.

• Schneider Privacy Policy.

• If your license is out of support, contact your Schneider Electric account manager or email
[email protected] with your license and site ID details.

Version Information
To identify the version of Power Operation installed:

7EN02-0462-03 Page 29 of 1312

Support and version information System Guide

1. Open Power Operation > Power Operation Studio.

2. Click the program icon on the top left:

3. Select About EcoStruxure Power Operation > Technical Info tab.

Power Operation version Plant SCADA file version

PO 2021 R1 8.3
PSO 2020 R2 8.21
PSO 2020 8.2
PSO 9.0 8.10.0.2086
PSE 8.2 8.0.0.2065
PSE 8.1 7.50.0.4150
PSE 8.0 SR1 7.50.0.4107
PSE 8.0 7.40.1.239
PSE 7.40 SR1 7.40.1.239
PSE 7.40 7.40.1.239
PSE 7.30 SR1 7.30.0.601, 7.30.1.94
PSE 7.20 SR1 7.20.4.38
PSE 7.20 7.20.1.33

What's new
This topic lists the highlights of functionality found in the latest release of Power Operation.

Power Operation 2021 CU3 release – August 2022

Power Operation 2021 with Advanced Reporting and Dashboards Cumulative Update 3 is a minor
release that introduces several improvements. We highly recommend you upgrade your existing
Power Operation system to version 2021 CU3.

Highlights:
• In Profile Studio, you can now configure which enum tag state values matter to you and will,
therefore, be included in your equipment.profile file upon exporting a configuration
package.
• Users can now use the Status tool to monitor the performance of their Power Operation
system, understand how it is organized, and troubleshoot issues.
• Email and SMS notification can now be sent to Contact groups with multiple recipients.

Page 30 of 1312 7EN02-0462-03

System Guide Support and version information

Power Operation 2021 CU2 release – March 2022

Highlights:
• In Profile Studio, you can now :

Customize labels and descriptions for datapoints within SCD files using EPAS or third-
party IEC 61850-compliant system configuration tools.

Customize descriptions for datapoints on the Datapoint tab within Profile Studio.
• Users can now turn off credential requirements for individual control components, as per their
discretion.
• The Waveform Extractor utility was added, which allows users to download waveforms from
their meters using FTP or sFTP protocols.
• Multi-site and multi-cluster example projects were added to PO, along with instructions to
guide you through set up.

Power Operation 2021 CU1 release – November 2021

Highlights:
• Several improvements were made to Profile Studio. You can now:
Export ICD files.

Export IID files.

Activate or deactivate datapoint template entry models.

• The Alarms feature has been updated to better reflect and support disabled and shelved
alarms.
• The following drivers were added:
PM2000 Device Driver

Easergy P5

Power Operation 2021 (initial release) – August 2021

Highlights:
• Power Operation OPC UA server protocol added.

• Support for Smart Connector, which allows data sharing with systems in which Power
Operation does not already have built-in communications support.
• Power Operation became IEC 61850 DNV certified.

• Several improvements were made to licensing, including:

Improved licensing compatibility with virtualization products.

Simplified license activation by requiring fewer license activation IDs.

• Several additions were made to backing up, restoring, and upgrading, including:

7EN02-0462-03 Page 31 of 1312

Support and version information System Guide

Archived files containing backup files from Power Operation and a manifest that captures
the state of the files when archived. These files are packaged, encrypted, and password
protected.

The ability to back up and package archive files.

TGML Upgrade utility will update restored TGML files to the latest version.

Upgrade Reference Component Definitions checkbox, which updates graphics

components to the latest version used in the project.
• Several additions were made to support the IEC 61850 workflow, including:

Upgrade Reference Component Definitions checkbox, which updates graphics

components to the latest version used in the project.

Faster deployments through IEC 61850 standard engineering workflows, offering the
ability to import SCD files using Profile Studio.

Integration with EPAS-E (SET) through Profile Studio.

• The ability to configure TGML to read or write alarm properties using web graphics was
added.
• Improved cybersecurity compliance, including:

Power Operation 2021 is 4-2 SL2 certified to comply with IEC 62443 standard at the
component level:

IEC 62443-4.1: Assesses a supplier’s product development lifecycle for Industrial

Automation and Control Systems (IACS).

IEC 62443-4.2: Defines the security requirements for components of an IACS.

Added Cybersecurity Admin Expert (CAE) software tool. CAE is a software tool used to
configure and apply security settings to both Power Operation and Schneider Electric-
connected products. Using CAE with EcoStruxure Power Operation is optional.
• Several improvements were made to incidents, alarms, and events, including:

Added the ability to view Load Impact on alarm cards, allowing automatic identification of
voltage sags that cause loss of electrical loads, voltage sags caused by the startup of an
electrical load, and load reversals due to circuit reconfiguration after a voltage sag.

Added the ability to quantify event impact through Load Impact in alarm cards. Load
Impact badge will only display on alarm cards if impact is greater than 5% of pre-event
load.

New logging module added to provide developers detailed system data during
debugging, and support Flat file-based logging and Syslog server-based logging.

Added ability to enable or disable alarms from the All Alarms, Active Alarms, or
Unacknowledged Alarms pages.

Added ability to shelve or unshelve alarms for minutes, hours, or days from the All
Alarms, Active Alarms, or Unacknowledged Alarms pages.

Page 32 of 1312 7EN02-0462-03

System Guide Support and version information

Added disturbance direction detection (DDD) to assist in identifying the origin of a voltage
disturbance (sag/swell/transient).

Added waveform analytics to help determine the potential cause of voltage sag events
within an electrical system.

Added waveform analysis information, including load change in kW and percent,

minimum and maximum RMS voltage, minimum and maximum RMS current, and voltage
sag duration.

Added custom columns pre-populated based on alarm tags tied to device profiles created
using Profile Editor.
• Several improvements were made to Graphics Editor, including:

Added support for SVG elements. Enhancements include:

Newer file formats accepted.

Animate, ClipPath, Pattern, Style, Symbol, tspan, Use elements supported.

Configurable graphics visibility levels for Pan and Zoom.

More efficient graphics resuse through 'Referenced TGML'.

• The WebHMI was made available in the following languages:

Spanish

Swedish

Russian

Portuguese

Norwegian

Italian

Polish

German
• Support was added for the following drivers:

Easergy P5

Galaxy VS UPS

PowerTag 63A/HR/Rope

Acti9 Active

MTZ 4.0 driver

Panel Server

Product name changes

The following table contains the previous and new product name:

7EN02-0462-03 Page 33 of 1312

Support and version information System Guide

Previous name New name

EcoStruxure Power SCADA Operation EcoStruxure Power Operation
Citect SCADA Plant SCADA
Citect Anywhere Power SCADA Anywhere
Power SCADA Runtime Power Operation Runtime
Power SCADA Studio Power Operation Studio
Control Client Client Access

Support contacts
Use the following links to obtain support if you can't find what you're looking for in this help or on
the Schneider Electric Exchange:
• Schneider Electric - Contact Support (Technical Support)

• mySchneider app

24/7 support. Mobile catalog. Access to expert help.

• Software Licensing Support

Offline license activation, license returns

• 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 an SRC for
troubleshooting license issues or to get new licenses. They are not able to help with these
issues.

Page 34 of 1312 7EN02-0462-03

System Guide Plan

Plan
Power Operation is uniquely designed to let you take advantage the power of a SCADA for Power
Management Applications.

Power Operation with Advanced Reporting and Dashboards enables the Facilities Team in Power
Critical Facilities to monitor, control, and troubleshoot issues in real-time with their electrical
distribution systems.

Use the information provided in this chapter to prepare for an installation or upgrade of a Power
Operation system.

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

Topic Content
"Components and single-
Information on design considerations for components and
site architectures" on page
component architectures.
36
"Multi-site architectures"
Discusses scaling your system with multi-site architectures.
on page 50
"Connected devices and Information on Power Operation's support for concurrent protocol
protocols" on page 52 communication.
"Computer requirements" Information on hardware and software requirements for Power
on page 56 Operation.
"Web Client versus Thick Discusses the web client features compared to the thick client
Client" on page 62 features.
Information on which languages Power Operation components
"Translation" on page 64
are localized.
"Commercial references"
Lists commercial references.
on page 66
"Integrating with Advanced
Information on integrating with the Advanced Reporting and
Reporting and
Dashboards module.
Dashboards" on page 67
"Interoperability" on page Provides information on integrating Power Operation with other
72 systems.
"EcoStruxture Anywhere" Provides details on the Power SCADA Anywhere component and
on page 83 architectures.
"OFS system time
Provides information on time stamping and related topics.
stamping" on page 628

For designers with a Citect background

Engineers developing Power Operation with a background in Plant SCADA and process
automation may be unaware of the importance of the differentiated Power Operation
development tools and the Power Applications that Power Operation is used for.

7EN02-0462-03 Page 35 of 1312

Plan System Guide

NOTICE
INOPERABLE SYSTEM
Ensure that you have received training and understand the importance of the Power Operation
productivity tools and workflows.

Failure to follow these instructions can result in overly complex projects, cost
overruns, rework, and countless hours of support troubleshooting.

NOTE: Power Operation is built on Power Operation Studio and includes productivity tools that
are designed and optimized to create the tags you need to configure power-based
SCADA projects. If you have prior experience using Power Operation Studio, do not rely
exclusively on Citect tools to build a SCADA project.

Ensure that you and your engineers are aware of Power Operation’s unique tooling and
workflows. The following features only are supported using Power Operation tooling and
workflows:
• HTML5 built-in graphics, alarms, and waveforms

• Event Notification Module

• Interoperability with Advanced Reporting (specifically ETL for PME)

• Interoperability with EcoStruxure™ Building Operation (specifically Power Operation EWS

implementation for EBO)
• LiveView

• Basic Reports

• One-line configuration

• Power Operation power graphics libraries, i.e. genies

• I/O Device Manager

• ION and Power Modbus drivers will be complex to set up without Power Operation tooling

Components and single-site architectures

This section provides information on the design considerations for Power Operation 2021 with
Advanced Reporting and Dashboards components as well as component architectures.

Components overview
Power Operation with Advanced Reporting and Dashboards is comprised of the following
components:

Page 36 of 1312 7EN02-0462-03

System Guide Plan

Refer to the topics in this section for detailed information on component purpose, licensing
options, design considerations, and architectures.

Time synchronization

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.

When using multiple machines in Power Operation systems as outlined in this section, it is
important that all machines hosting Power Operation components are synchronized to the same
NTP server (public or private). If you do not synchronize time across Power Operation
components, alarms and notifications may be delayed.

Do not confuse time synchronization with enabling Sequence of Events analysis and recording
across devices in a Power Management system that may also be using time synchronization,
including PTP and IRIG-B.

7EN02-0462-03 Page 37 of 1312

Plan System Guide

Power Operation Server component

The Power Operation Server is the required base component of any Power Operation system
responsible for data acquisition, alarming and trending of historical data. The Server includes:
• Power Operation engineering tool suite

• Open data exchange protocols/tools (OPC UA client/server, OPC DA client/server, OPC AE

server, EcoStruxure Web Services (EWS) for interoperability w/ EBO, CtAPI)
Each Server supports up to 10 concurrent OPC, 10 concurrent OLED8, and 10
concurrent CtAPI connections.
• Device drivers (Modbus primary, ION, IEC 61850 primary, IEC 60870-5-104 primary,
BACnet/IP primary, DNP3 primary, SNMP v.2, etc.)
• Basic reporting (Multi-Device Usage Reports, Rapid Access Labels, Single Device Usage
Reports, Tabular Reports, Tabular Report Exports, Trend Reports)

Licensing options

Licensed by number of points or tags (options include: 500, 1500, 5000, 15000 and Unlimited
tags). For more information on licensing, see "License keys" on page 163.
Design considerations

Server redundancy is achieved by licensing additional Servers in the design.

How points are calculated

EcoStruxure™ Power Operation counts all I/O device addresses dynamically at runtime. This
includes all tags used by alarms, trends, reports, events, pages, in Super Genies, use of the
TagRead() and TagWrite() Cicode functions, or read or written to using DDE, ODBC, or the
CTAPI. A variable tag is only counted towards your point count the first time it is requested. That
is, even though you may have configured a certain tag on a page in your project, unless you
navigate to that page and request the data, the variable tag will not be counted towards your point
count.

In addition to this, the following changes were made to the licensing structure in Power Operation:
• I/O point count is now tag based not address based. For example, two tags that use the same
PLC address will be counted twice. If two trend tags use the same variable tag, it will be
counted once. The same applies to alarms.
• For the multi-process mode, each server component will accumulate its own point count. The
server component point count is the count added up from all server components. If two server
components use the same tags, say alarm and trend, the tags will be counted twice when the
point count gets summed.
• For the multi-process mode, the client component will also accumulate its own point count
including super genie and CTAPI tags.
• For the multi-process mode, the machine point count will be the point count on the client
component or the point count added up from all server components, whichever is bigger. For
example, if the total point count for all server components is 100, and the client component
point count including CTAPI and super genies is 95, the kernel "General" window will show

Page 38 of 1312 7EN02-0462-03

System Guide Plan

100. If the client component point count reaches 120 later and the server component point
count remains 100, the kernel "General" window will show 120.
• Reading properties of a tag with TagGetProperty() will cause that tag to be included in the
point count, even if the value is not read.
• Writing to local variables or disk I/O variable tags via OPC etc will also increase the point
count. For example, if you use an OPC client to write to a local variable, each local variable
will be counted once, the first time it is used.

Server component architecture

Built-in architectural redundancy
Power Operation supports full server redundancy and full communication redundancy. When the
Primary Server becomes unavailable, the Standby Server automatically takes over in 2 to 3
seconds.

There is also full data synchronization between servers and historical backfill. If primary goes
down and a secondary becomes active, when the primary returns to active state the secondary
fills in the primary with any missed information.

NOTE: Multiple NICs are supported on each server and a device may have two communication
paths.

7EN02-0462-03 Page 39 of 1312

Plan System Guide

Making changes while online

Certain changes and updates to a production Power Operation system require a restart of the
Power Operation Server processes. For example:
• Adding and removing devices

• Adding and removing tags

For this reason, if the customer requires changes to be made without interruption of service
(restarting Power Operation Server), a redundant architecture is required.

In a redundant architecture, changes can be made without interrupting service by:

1. Making a change on Secondary Server

2. Restarting Secondary Server

3. Making the updated Secondary Server the Primary Server

Ethernet network redundancy

When network redundancy is being considered, the most common approach is: Second LAN in
parallel to first. If LAN1 becomes inoperative, components will maintain connection using LAN2.

Power Operation Client Access component (HTML5 client)

Purpose

The Client Access is an optional component that allows operators to access the Power Operation
runtime from a machine other than the Server machine. Clients can be run as either a Windows
desktop application or as a built-in HTML5 web client. The Client Access can be used to perform
control and/or acknowledge alarms. The Client Access license allows up to 2 concurrent CtAPI
connections. Customers can have a mix of Windows desktop clients and built-in HTML5 web
clients.
Licensing options

Client Access is licensed by number of points/tags (options include: 500, 1500, 5000, 15000 and
Unlimited tags). For systems with Server redundancy, it is recommended to license an equal
number of redundant client access licenses for the stand-by Server.
Design considerations

Clients can use one of the following license models:

Page 40 of 1312 7EN02-0462-03

System Guide Plan

• Floating license model: limited number of licenses can be shared between a number of
concurrent users and computers.
• Static license model: license reserved for set number of computers.

Client Access component architecture

Architecture #1: Server redundancy with static Client Access

The following example architecture illustrates server redundancy with static Client Access:

Server redundancy is achieved by installing and licensing a secondary Power Operation server
with the same point/tag count as the primary.

Server software and licenses are installed on the Primary and Secondary Server machines.

Client Access software and license is hosted on Client machine.

Placing the Client license on the Client machine limits the Client access to Windows desktop
application access only, instead of HTML5 web client access if the static license model is used.

Architecture #2: Server redundancy with floating Client Access

The following example architecture illustrates server redundancy with floating Client Access:

7EN02-0462-03 Page 41 of 1312

Plan System Guide

Server software and licenses are installed on the Primary and Secondary Server machines.

By placing Client Access icense on Server machine (floating license model), the client could be
accessed via HTML5 web client or Windows desktop application.

Client connectivity limited to one simultaneous connection due to having one Client license.

Architecture #3: Server redundancy with two floating Client Access

The following example architecture illustrates server redundancy with 2 floating Client Access:

Server software and licenses are installed on the Primary and Secondary Server machines.

By placing Client Access license on Server machine (floating license model), the Client could be
accessed via web client or Windows desktop application.

Page 42 of 1312 7EN02-0462-03

System Guide Plan

Client connectivity limited to two simultaneous connections due to having two Client licenses.

Event Notification Module component

Event Notification Module (ENM) is an optional component. ENM delivers event/alarm information
from the Power Operation Server to users via SMTP (email) or SMS (text message). It can be
configured to send notifications upon specific events/alarms occurring and to specific users.
Licensing options

Single license.For systems with Server redundancy, a second ENM license is required for stand-
by Server.
Design considerations

ENM configuration can be run from thick Power Operation clients. Configuration not available
from HTML5 web client.

For SMTP support, requires access to SMTP Server (not sold with PO).

For SMS, factory tested serial modem models should be used. See "Factory tested serial
modems" on page 43 for more information.

Factory tested serial modems

The following are factory tested SMS serial modems:
• Multi-Tech MTC-H5-B03-KIT

• Multi-Tech MTR-H5-B07-US-EU-GB

• Multi-Tech Quick Carrier USB-D USB Cellular Modem, MTD-H5

Other serial modem models may work with Event Notification Module. Teams should test other
serial modem models before deploying to customer.

IP modems are not currently supported.

7EN02-0462-03 Page 43 of 1312

Plan System Guide

Advanced Reporting and Dashboards component

Advanced Reporting and Dashboards Module is a variant of Power Monitoring Expert (PME) that
is included on the Power Operation installation media and can be optionally licensed with Power
Operation. In an architecture with Power Operation, the Reports and Dashboards components of
PME are integrated with the Power Operation Runtime to deliver feature rich “Energy Monitoring
Application” experience for the system. Additionally, WebReach diagrams are commonly
integrated into the Power Operation Runtime as well.
Licensing options

Single license. For more information on licensing, see "License keys" on page 163.

NOTE: Requires at least one Power Operation Server and one Client Access license for
purchase. No additional PME client or device licenses are required for this module as the Power
Operation Server and Client Access licenses cover the device licenses (i.e. PME DLs) and client
connectivity to the reports and dashboards.

Design considerations

Advanced Reporting and Dashboards (PME) component does not support redundancy. See
"Integrating with Advanced Reporting and Dashboards" on page 67.

Advanced Reporting and Dashboards architectures

Architecture #1: Simple system without redundancy

The following example architecture illustrates the Advanced Reporting and Dashboards Module
in a system with a single Power Operation Server.

The Power Operation Server and Advanced Reporting Module are installed on the same
machine. Additionally at least one additional Client Access license is required to enable remote
web client access if hosted on the Primary Server machine.

Page 44 of 1312 7EN02-0462-03

System Guide Plan

Architecture #2: Large system without redundancy

The following example architecture illustrates the Advanced Reporting and Dashboards Module
installed on a separate server from the Power Operation Server.

This architecture is typically used for performance reasons. Systems with over 150,000 tags or
600 devices should have Advanced Reporting and Power Operation Server on separate
machines.

The Advanced Reporting Server contains both the Advanced Reporting software (PME) and the
software key.

Architecture #3: Advanced Reporting with Server redundancy

NOTE: This is the recommended Advanced Reporting architecture.

The following example architecture illustrates the Advanced Reporting and Dashboards Module
in a system with Power Operation Server redundancy.

7EN02-0462-03 Page 45 of 1312

Plan System Guide

The Advanced Reporting Server contains both the Advanced Reporting software (PME) and the
software key.

NOTE: The ETL used to send information from Power Operation to PME is installed on the
Advanced Reporting machine.

NOTE: The ETL does not support the concept of communicating with a redundant Power
Operationsetup. For this reason, if the Power Operation Primary Server failed, then the ETL on
the Advanced Reporting Server would need to be reconfigured manually to point to the
Secondary Server.

Redundancy Scenario: ETL used for Server redundancy

The following image shows an example where the Primary Server becomes inoperable and the
Advanced Reporting ETL is not reconfigured to point to the Secondary Server. In our example,
the Primary Server becomes inoperable on June 1 and is restarted on June 3.

Page 46 of 1312 7EN02-0462-03

System Guide Plan

The Secondary Server has taken over the alarming and one-line diagram visualization. Since
Advanced Reporting is still running with reports, dashboards, and WebReach diagrams, the
functionality of Power Operation and PME would largely remain active from June 1 to 3.

However, when running reports during June 1-3 while the Primary Server is down, reports and
dashboard data would NOT be present for this time period. Data previous to June 1 would be
present.

Once the Primary Server is recovered on June 3, the Secondary Server will fill the Primary Sever
with the missed trend and historical data.

The Advanced Reporting ETL would start pulling data from the Power Operation’s Primary trend
file system. Depending on system size, this June 1-3 data would eventually be available in the
reports and dashboards.

Additional Advanced Reporting and Dashboards Modules component

Additional software modules compatible with the Advanced Reporting and Dashboards Module
are included on the Power Operation installation media and can be optionally licensed with Power
Operation. These modules address a variety of electrical network, asset, and energy
management needs.
Licensing options

Each module is licensed individually and requires at least one Advanced Reporting and
Dashboards license. For more information on licensing, see "License keys" on page 163.

You can license the following software modules on the same system as the Advanced Reporting
and Dashboards Module using the License Configuration Tool:

Commercial reference Software module

PSA104112 Advanced Reporting and Dashboards Module

7EN02-0462-03 Page 47 of 1312

Plan System Guide

Commercial reference Software module

PSA104114 Energy Billing Module
PSA104115 Breaker Performance Module
PSA104116 Energy Analysis Reports Module
PSA104121 Capacity Management Module
PSA104124 Power Quality Performance Module
PSA104125 Insulation Monitoring Module
PSA104126 Backup Power Module
PSA104130 Energy Analysis Dashboards Module

For more information on licensing software modules, see Activating software module licenses.
Design considerations

See "Integrating with Advanced Reporting and Dashboards" on page 67 for details.

Activating software module licenses

Each software module requires a unique license to be activated on the same server as Advanced
Reporting and Dashboards.

For detailed information on software module licensing, see Additional Advanced Reporting and
Dashboards Modules component.
Prerequisites:
• Advanced Reporting and Dashboards installed on a server.

To activate a software module license:

1. On the Advanced Reporting and Dashboards server, open the License Configuration Tool.

2. Click Activate License.

TIP: You can find the License Configuration Tool in ...\Schneider Electric\Power Monitoring
Expert\License Configuration Tool.

3. In the message box, click OK. The Activate License page opens.

4. On the Activate License page, enter the Activation ID, and then click Activate. The license
appears in the License Configuration Tool.

5. When you have completed activating each desired license, close the tool.

Mapping EcoStruxure Power to Advanced Reporting modules

The following table maps Advanced Reporting modules to EcoStruxure Power applications:

EcoStruxure Power application Advanced Reporting module

Insulation Monitoring Insulation Monitoring Module
Capacity Management Capacity Management Module

Page 48 of 1312 7EN02-0462-03

System Guide Plan

EcoStruxure Power application Advanced Reporting module

Power Quality Monitoring PQ Performance Module
Breaker Settings Monitoring Breaker Performance Module
Energy Analysis Reports Module
Energy Usage Analysis
Energy Analysis Dashboards Module
Energy Analysis Reports Module
Energy Efficiency Compliance
Energy Analysis Dashboards Module
Cost Allocation Energy Billing Module
Utility Bill Verification Energy Billing Module
Backup Power Testing Backup Power Module

NOTE: The Power Monitoring Expert 2021 – System Guide contains detailed information on
how to configure the Advanced Reporting modules.

Advanced Reporting module descriptions

The following table provides short descriptions for the Advanced Reporting software modules.

Advanced Reporting
Category Description
module
Improve Operational Efficiency, Energy
Energy Analysis Reports
Performance and help achieve ISO 50001
Module
compliance.
Efficiency and
Energy Analysis Advanced analysis and visualization gadgets.
Reliability
Dashboards Module Sankey, heatmap/carpet, pareto and ranking.
Flexible rate engine and reports for cost
Energy Billing Module
allocation, bill verification and tenant billing.
Insulation Monitoring Monitor insulation levels for power Isolated
Module panels (IEC and ANSI).
Reliability and Capacity Management Monitor the capacity loading of electrical
Safety Module equipment (UPS, Generators, multi-circuits).
Simple, global overview of the impact of power
PQ Performance Module
quality on your facility’s operations.
Breaker status diagrams and reports including
Breaker Performance
electrical ageing and mechanical wear, for
Asset Module
proactive maintenance.
Compliance and
Monitor the parameters of your generator,
Reliability
Backup Power Module ATSs and UPSs. Automated results for
emergency power supply systems.

7EN02-0462-03 Page 49 of 1312

Plan System Guide

Multi-site architectures
A multi-site architecture (or multi-clustered system) allows you to scale your system as your
needs evolve. It gives you the ability to monitor multiple systems from a central location. You can
roll up data, graphics, and controls under a central HMI and you can add servers and clusters of
servers to expand or distribute systems.

• Monitor and control multiple independent systems from single runtime client for
geographically co-located customers.
• System organized into separate sites (also known as clusters).

• Each site is controlled by local operators and supported by local redundant PO servers.

• From central control site, one can simultaneously manage all the sites by viewing ‘federated’
data from multiple PO servers.

Licensing options

When using HTML5 web clients, you need to have a full PO Server license at Central Site. When
using thick clients, you need to have a Client Access license at Central Site.

For more information on licensing, see "License keys" on page 163.

Page 50 of 1312 7EN02-0462-03

System Guide Plan

Design considerations
Geographically distributed systems

Power Operation requires a constant, high bandwidth (for example: Ethernet), and a reliable
connection. We recommend against doing real-time control from the central control room in this
architecture without having first performed a Final Acceptance Test (FAT) prior to hand-off.

NOTE: Ensure a stable communication between PO clusters and connected products that is
always-connected and has sufficient bandwidth.

Devices in multiple time zones

Power Operation Servers can contain different devices that can be distributed across several
sites or time zones. Instead of attempting to connect devices directly via a remote connection, a
PO Server is placed at each site. In an architecture distributed across time zones, ensure that
devices are configured for UTC time. Ensure a stable communication between PO clusters and
connected products that is always-connected and has sufficient bandwidth.
Maintaining/upgrading the system

All PO sites must be using the same version of the PO software for communication between
systems to occur. For example, Central Site cannot be running PSO 2020 with underlying sites
running PO 2021.

Advanced Reporting and software modules

Architecture option #1 - Single Advanced Reporting server

7EN02-0462-03 Page 51 of 1312

Plan System Guide

Install Advanced Reporting at central site and connect directly to devices located at individual
sites. Allows for central historical reporting across all sites. Ensure in this architecture that you do
not exceed device limits on Advanced Reporting.

Architecture option #2 - Advanced Reporting at each individual site

Install Advanced Reporting at each individual site. Architecture would be considered if overall
system size was beyond scale of single Advanced Reporting server.

Connected devices and protocols

Power Operation supports concurrent protocol communication; one Power Operation server can
communicate using multiple protocols.

Power Operation 2021 supports the following protocols:

• IEC 61850 Primary (sometimes called Master) Edition 2

• DNP3 Primary

• ION

• Modbus Primary

• IEC 60870-5-104 Primary

• KNX

• SNMP

• BACnet/IP

Page 52 of 1312 7EN02-0462-03

System Guide Plan

Power Operation supports the following Open Data Exchanges:

• OPC UA 1.01 (Client and Server)

• OPC DA version 2, version 2.05a (Client and Server)

• OPC AE version 1 (Server)

Go to the AVEVA Knowledge & Support Center website for information on PLANT SCADA.

Power Operation Tool Suite

NOTICE
INOPERABLE SYSTEM
Ensure that you have received training and understand the importance of the Power Operation
productivity tools and workflows.

Failure to follow these instructions can result in overly complex projects, cost
overruns, rework, and countless hours of support troubleshooting.

NOTE: Power Operation is built on Power Operation Studio and includes productivity tools that
are designed and optimized to create the tags you need to configure power-based
SCADA projects. If you have prior experience using Power Operation Studio, do not rely
exclusively on Citect tools to build a SCADA project.

Deploy projects faster with the Power Operation Tool Suite, including tools that are unique to
Power Operation and critical to project success.

The suite includes:

• Simple SCADA Project Setup

• Centralized SCADA Project Deployment

• Power Operation Studio

• Power Device management

• IO Devices Comms Optimization

The following Power Operation features are supported only using Power Operation tools and
workflows:
• HTML5 built-in graphics, alarms, and waveforms

• Event Notification Module

• Interoperability with Advanced Reporting (specifically ETL for PME)

• Interoperability with EBO (specifically PO EWS implementation for EBO)

• LiveView

• Basic Reports

7EN02-0462-03 Page 53 of 1312

Plan System Guide

• One-line configuration

• Power Operation power graphics libraries (genies)

• I/O Device Manager (both UI and Excel)

• The ION and Power Modbus drivers are complex to setup without the use of Power Operation
tooling

Waveform file share access and permissions

Waveforms are stored in a file share repository on the Power Operation Server.

The following waveform file share permissions are required:

• The account running Citect on Power Operation Server requires Full permission
(Read/Write/Modify)
• Windows user accounts that are used to log-into remote machines using HTML5 web clients
require Read Only permission.
• Windows user accounts must be linked to Power Operation user roles that allow Remote
Procedure Call (RPC).

NOTE: This is required to get a list of waveforms from the Server.

Architecture #1: HTML5 Web Client

Page 54 of 1312 7EN02-0462-03

System Guide Plan

Architecture #2 EcoStruxture Anywhere

Supported power devices

Power Operation offers built-in support for many Schneider Electric devices to simplify the set up
and acquire power event data types:
• Power event waveforms (sag, swell, transients, etc.)

• Onboard alarms and time-stamps, events, and data logs

Third-party devices
Third-party devices can be supported via a variety of protocols using productivity tools not
available in the core Plant SCADA platform

Onboard alarm
Tools used during
Protocol Real time data Onboard data logs time stamps and COMTRADE waveforms
commissioning
logs

Power Modbus Yes No No via FTP * Profile Editor

IEC 61850 Ed. 2 Yes Yes * Yes * Yes * Profile Editor

IEC 60870-5-104 Yes No Yes * via FTP * Profile Editor

DNP3 Yes No Yes * via FTP * Profile Editor

SNMP v2 Yes No No n/a Power SCADA Studio

BACnet/IP Yes No No n/a Power SCADA Studio

* If supported by the device.

7EN02-0462-03 Page 55 of 1312

Plan System Guide

Third-party device support resources

Browse to 3rd Party Device Support (Box link) for information on how to integrate the following
devices with Power Operation:
• 3rd party Modbus devices

• 3rd party IEC-61850 devices

• DNP3 devices

• SNMP v.2 devices

• Cyber Sciences devices

Plant SCADA drivers

Plant SCADA drivers can be used with Power Operation. For a complete list of Citect drivers that
are compatible with Power Operation, see the Connectivity Hub page in the AVEVA Knowledge
& Support Center (requires login.)

Driver information also contains release notes and currently supported operating systems.

NOTE: Most drivers are licensed via Plant SCADA and are provided at no additional cost.
However, there are some exceptions where the driver requires an additional purchase cost to
license it. Any drivers that require a purchase cost are only commercially available for Plant
SCADA and are not commercially allowed for use with Power Operation.

Computer requirements
This section provides information on the hardware and software requirements for a Power
Operation with Advanced Reporting and Dashboards system.

Server CPU and RAM requirements

Power Management software needs to be installed on dedicated machines, so that other non-
Power Management software applications do not consume machine resources.

When selecting server hardware, carefully review the PassMark® score and CPU Clock Speed.
The required processor is defined according to an average CPU mark given by PassMark
Software. To check CPU performance, for example a Core i3 CPU, type "PassMark Core i3" in the
search engine of a web browser. This will return the CPU's calculated performance as compared
to other similar well-known processors.

CPU and RAM recommendations for various

system architectures
• The requirements listed in this topic are minimum requirements; we recommend that you
consider doubling the RAM requirements listed.
• EcoStruxture Anywhere server must have a CPU with SSE2 instruction set support.

Page 56 of 1312 7EN02-0462-03

System Guide Plan

Power Operation server (medium and large systems)

The following table lists the number of CPU cores and RAM required for a Power Operation
system.

NOTE: Use the tag or device number that is higher of the two numbers. For example, if you have
a system using 120,000 tags with 300 devices, use six CPU cores and 16 GB of RAM.

NOTE: These are minimum requirements. We recommend that you consider doubling the
RAM requirements listed.

Use the larger

CPU PassMark Score # CPU Cores RAM (GB)
figure below
1,500 tags or 50
2,000 2 8
devices
15,000 tags or
4,500 4 16
100 devices
50,000 tags or
8,000 6 16
200 devices
100,000 tags or
8,000 6 16
400 devices
150,000 tags or
8,000 8 32
600 devices
200,000 tags or
10,000 8 48
800 devices
250,000 tags or
10,000 12 48
1,000 devices
300,000 tags or
10,000 16 64
1,200 devices
350,000 tags or
10,000 20 64
1,400 devices
400,000 tags or
10,000 24 96
1,600 devices
450,000 tags or
10,000 24 96
1,800 devices
500,000 tags or
10,000 30 96
2,000 devices

Power Operation and Power Monitoring Expert on the Same Machine

The following table lists the number of CPU cores and RAM required for a Power Operation and
Power Monitoring Expert system on the same machine.

7EN02-0462-03 Page 57 of 1312

Plan System Guide

NOTE: Use the tag or device number that is higher of the 2 numbers. For example, if you have a
system using 120,000 tags with 300 devices, use 16 CPU cores and 28 GB of RAM.

NOTE: These requirements are based on product testing at the factory. They are intended as
recommendations on system sizing. However, some customers may find that based on their
system's design or usage they require more or less resources than what is recommended by this
guide.

Use the larger

CPU PassMark Score # CPU Cores RAM (GB)
figure below
50,000 tags or
8,000 14 40
200 devices
100,000 tags or
8,000 16 48
400 devices
150,000 tags or
8,000 18 64
600 devices

For systems greater than 150,000 tags or 600 devices, we recommend a distributed architecture
with separate physical machines for Power Operation and Power Monitoring Expert.

Power Operation and Power Monitoring Expert on separate machines

Refer to the Power Monitoring Expert 2021 – System Guide for specific CPU and RAM
requirements when installing Power Operation and Power Monitoring Expert on separate
machines.

Client CPU, RAM, and disc requirements

Power Operation Clients used as Windows desktop thick clients have the following minimum
requirements:
• CPU PassMark: 2000

• CPU: 2 Cores

• RAM: 4 GB

• Disk storage: 10 GB

• Screen resolution: 1920 x 1080

Monitoring CPU for running systems

Optimal performance is achieved when all computers in your Power Operation network use
approximately 40% or lower CPU in normal state. If you have any concerns about system
responsiveness or its ability to handle abnormal situations, consider adding resources to lower
overall CPU utilization.

Page 58 of 1312 7EN02-0462-03

System Guide Plan

Power Operation Graphics Adapter

Minimum requirements:
• DirectX 9 or later with WDDM 1.0 Driver

• 128 MB of dedicated VRAM (for systems of any size)

Server disk storage

The main consumers of historical data in PO are:

1. Advanced Reporting and Dashboards Module (PME) historical data for display in reports
and dashboards.

2. PO historical data stored for PO alarm viewer, trend viewer, and built-in basic reports.

Advanced Reporting and Dashboards data is stored in Microsoft SQL databases. PO data is
stored in file system flat files (no SQL required).

Required disk space without Advanced Reporting

When planning a Power Operation system without Advanced Reporting (Power Monitoring
Expert), you can fine tune your disk storage requirements based on how Power Operation stores
data.

Power Operation has two major consumers of disk storage space:

1. Alarm information which is stored in a propriety database that may grow over time to a size
of 1-2 GB.

2. Historical data stored in trend files (flat files on the disk) used by PO built-in reports and
trend viewer. The size and number of these trend files depend on number of tags in system,
logging interval, and number of years to store data.

Trend files are pre-allocated (reserved) on the hard disk the first time that Power Operation is
started. Hard disk space does not "grow" over time by acquiring trend data. In other words, if the
hard drive is not big enough for the number of years of trending that you plan for, the system will
tell you.

Calculating disk storage

To calculate disk storage size for your system, use the Power Operation Disk Sizing Calculator.
Go to the Schneider Electric Exchange for more information.

NOTE: These values include a 2 GB alarm database size and assume that you configure trends
to be stored in separate files each week.

Network requirements
Use Ethernet whenever possible. For best system performance with devices, we recommend
minimum 1 Gigabit Ethernet communication.

If you are using serial communication, use a minimum baud rate of 19.2K.

7EN02-0462-03 Page 59 of 1312

Plan System Guide

Supported operating systems

The following table lists the compatible operating systems for Power Operation, ENM, and
Advanced Reporting. Columns for version 2021, 2020, 9.0, and 8.2 represent super-set of all PO
components including Servers, Clients, and Advanced Reporting and Dashboards (PME).

NOTE: 64-bit operating systems are recommended for best performance.

Operating System Power Operation Version

2021 2020 9.0 8.2 8.1

Windows Server 2019 – – –

Windows Server 2016 –

3 2 1
Windows 10

Windows Server 2012 R2

Windows 8.1 – – –

Windows Server 2012 – –

Windows Server 2008 R2 – – –

Windows 7 – –

1: Available with 8.1 update 6 or later

2: Requires Windows 10 version LTSB 1607 and later (64-bit only)

3: Requires Windows 10 version LTSB 1607 and later (64-bit only) or Windows 10 1803 and later

(64-bit only)

Supported SQL Server versions

Power Operation with Advanced Reporting and Dashboards requires a Microsoft SQL Server
database. Power Operation with Advanced Reporting and Dashboards supports the following
SQL Server versions:
• SQL Server 2019 Express/Standard/Enterprise/Business Intelligence

• SQL Server 2017 Express/Standard/Enterprise/Business Intelligence

Page 60 of 1312 7EN02-0462-03

System Guide Plan

• SQL Server 2016 Express/Standard/Enterprise/Business Intelligence

• SQL Server 2014 Express/Standard/Enterprise/Business Intelligence

• SQL Server 2012 Express/Standard/Enterprise/Business Intelligence, SP2

NOTE: Power Operation 2021 without Advanced Reporting and Dashboards does NOT require
a SQL Server database.

Power Operation with Advanced Reporting and Dashboards installation media includes SQL
Server 2019 Express that can be used with Advanced Reporting.

Virtualization
The following table lists the virtualization support for installation and operation of Power Operation
with Advanced Reporting and Dashboards:

Microsoft Hyper-V VMWare vSphere

Power Operation Server (including web server
Yes Yes
host)
Power Operation Client Access (this refers to
Yes Yes
Windows Desktop clients)
Mobile Notifications (Event Notification
Yes Yes
Module)
Advanced Reporting and Dashboards (Power
Yes Yes
Monitoring Expert)

NOTE: Power Monitoring Expert is validated with additional virtualization systems, see the
Power Monitoring Expert 2021 – System Guide for additional details.

Virtualization planning notes:

• Set all resource allocation (CPU, memory, and disk) to fixed; dynamic is not supported.
Do not share resources between virtual machines via over-allocation.The total of all
individual VM resources should not exceed that which is available from the host.

NOTICE
UNINTENDED DATA LOSS OR LOSS OF SOFTWARE FUNCTION
Do not exceed device limits.

Failure to follow these instructions can result in irreversible damage to

software and databases.

• If you are using shared drive storage, use Fiber SAN storage. If you are not using Fiber SAN
storage, use a direct attached, dedicated hard drive used by Power Operation only.
• You must have a fixed-size disk virtual machine.

7EN02-0462-03 Page 61 of 1312

Plan System Guide

• Set host (for example: ESX host) power management to “High Performance”.

• Adjust Quality of Service (QoS) to allow precedence to Power Operation over less time-
critical applications.
• Create your Power Operation virtual machine on a host without other time-critical
applications.

Additional virtual machine configuration guidelines vary by hypervisor.

When running virtual machines, licenses remain trusted during the following scenarios:
• Changes to the NIC card MAC address of the physical host or virtual machine.

• Changes to the physical host or virtual machine RAM

• Changes to physical host hard disk or virtual machine disk

• Changes to the OS clock (within +/- 2 hours)

• The physical host or virtual machine is rebooted.

• The virtual machine is paused or resumed.

• The virtual machine is restored from a snapshot.

• The virtual machine is live migrated/moved (eg. VMotion) for common migration scenarios.

Virtual machine live migration/move scenarios that may cause licenses to go untrusted include:
• VMWare moving from one vCenter to another (cross-vCenter migration).

• Microsoft Hyper-V moving from one System Center Virtual Machine Manager to another.

Web Client versus Thick Client

The HTML5 Web client and Thick client both have unique graphics engines. Legacy graphics
pages built using 'classic' graphics builder will only run in the Windows Thick client application.
Conversely, Web client graphics with pan/zoom capabilities will only run using a web browser.

A single Power Operation Server can provide both a Windows runtime experience and an HTML5
web client operator experience. However, graphics cannot be reused between the Windows Thick
client and HTML5 Web client.

Windows Thick client runtime options HTML5 Web client

Operator access via Windows application: Remote operator access via web browser:
• HTML5 web client functionality for
• The traditional way operators access the
remotely accessing graphics, alarms, and
Power Operation system.
trending.
• Legacy graphics are raster-based, without • Graphics package with pan/zoom and
pan/zoom or decluttering capabilities. decluttering capabilities.

Page 62 of 1312 7EN02-0462-03

System Guide Plan

Windows Thick client runtime options HTML5 Web client

• Basic alarming capabilities lack:
• Alarm interface with latest Power Events
automatic Smart Alarms grouping
Analysis features (Smart Alarms, timeline
timeline visualization capabilities
analysis, natural language waveform
natural language waveform analytics, analytics, etc).
etc.
• The recommended option versus the
Windows thick client.

Web Client versus Thick Client feature comparison

Thick client
Feature HTML5 Web client capability
capability
Yes (plus pan/zoom scalable graphics
Graphics monitoring only Yes
and decluttering)
Yes (plus Smart Alarm grouping,
Alarms Yes timeline analysis, natural language
waveform analysis, shelving, disabling)
Waveforms Yes Yes (plus waveform comparison)
Yes (plus ability to navigate to alarm
Alarm banner annunciator
Yes views and ability for end users to
with audible alarms
configure
Ability to navigate from
Yes Yes
graphic to associated alarms
Client side scripting Yes (using CiCode) Yes (using JavaScript)
Graphics monitoring and
Yes Yes
control
Trend viewer (real time and
Yes Yes
historical)
Runtime container Partial (plus ability for end users to
Yes
customization configure)
Ability for local teams to No (various languages available with
Yes
translate end user runtime EPO 2021)
Two-factor authentication
Yes No
support
Role-based access control of
Yes No
various web components
Client automatically switching
to secondary server during Yes No
failover

7EN02-0462-03 Page 63 of 1312

Plan System Guide

Thick client
Feature HTML5 Web client capability
capability
No
Configuration/tools: ENM
(end users using web client as primary
configuration and PO
Yes interface can use thick client runtime to
diagnostics tool (functionality
use ENM configuration and diagnostics
introduced in PSO 9.0)
functionality)
Configuration/tools: Tag
Viewer and Tag Debugger Partial (end users using web client as
(functionality typically used by Yes primary interface can use thick client
engineers or tech support for runtime to use Tag Viewer/Debugger)
diagnostics/troubleshooting)
No (end users using web client as
Configuration/tools: primary interface can use thick client
Yes
Scheduler configuration runtime to use ENM configuration and
diagnostics functionality)

HTML5 Web client browser support

Microsoft
Google Chrome Mozilla Firefox Apple Safari
Edge
Power Operation
graphics pages
including one-line
Yes Yes Yes Yes
diagram/engine
using pan/zoom
graphics
PO 2021 Alarms
Yes Yes Yes Yes
and Trends
PME reports and
Yes Yes Yes Yes
dashboards
Power Operation
Yes Yes Yes Yes
Basic Reports
LiveView (Power
Operation Real
Yes Yes Yes Yes
Time Tables
implementation)

NOTE: Graphics pages built using classic graphics builder will only run on Windows Desktop
clients.

Translation
The following table lists languages in which Power Operation components are available:

Page 64 of 1312 7EN02-0462-03

System Guide Plan

web client
runtime with thick runtime
Advanced web operator engineering System Guide with Event
Language
Reporting documentation tools documentation Notification
and Module
Dashboards
Can be done
and has been
done
successfully
by country
organizations
– – – – – (DBF files can
be updated by
application
engineers;
this includes
the alarm
text.)

English –

Simplified (excluding –
Chinese Graphics
Editor)

French (excluding –
Graphics
Editor)

Spanish – – –

Swedish – – –

German – – –

Russian – – –

Portuguese – – –

Norwegian – – –

Italian – – –

7EN02-0462-03 Page 65 of 1312

Plan System Guide

web client
runtime with thick runtime
Advanced web operator engineering System Guide with Event
Language
Reporting documentation tools documentation Notification
and Module
Dashboards

Polish – – –

Commercial references
Power Operation Server
• PSA101199 – Power Operation Server, Unlimited Points

• PSA101115 – Power Operation Server, 15000 Points

• PSA101114 – Power Operation Server, 5000 Points

• PSA101113 – Power Operation Server, 1500 Points

• PSA101112 – Power Operation Server, 500 Points

• PSA10111599 – Server, Expansion 15000 to Unlimited Points

• PSA10111415 – Server, Expansion 5000 to 15000 Points

• PSA10111314 – Server, Expansion 1500 to 5000 Points

• PSA10111213 – Server, Expansion 500 to 1500 Points

Power Operation Clients

• PSA102099 – Power Operation Client Access, Unlimited Points

• PSA102015 – Power Operation Client Access, 15000 Points

• PSA102014 – Power Operation Client Access, 5000 Points

• PSA102013 – Power Operation Client Access, 1500 Points

• PSA102012 – Power Operation Client Access, 500 Points

• PSA102099P5 – Client Access, Unlimited Points, 5 Pack

• PSA102099P10 – Client Access, Unlimited Points, 10 Pack

• PSA102099UL – Power Operation Unlimited Client Access

• PSA10201599 – Client Access, Expansion 15000 to Unlimited Points

• PSA10201415 – Client Access, Expansion 5000 to 15000 Points

• PSA10201314 – Client Access, Expansion 1500 to 5000 Points

• PSA10201213 – Client Access, Expansion 500 to 1500 Points

Page 66 of 1312 7EN02-0462-03

System Guide Plan

• PSA104113 – Event Notification Module

• PSA105100 – Power SCADA Anywhere, 5 User Pack

Advanced Reporting & Dashboards and Software Modules

• PSA104112 – Advanced Reporting and Dashboards Module

• PSA104114 – Energy Billing Module

• PSA104115 – Breaker Performance Module

• PSA104116 – Energy Analysis Reports Module

• PSA104121 – Capacity Management Module

• PSA104124 – Power Quality Performance Module

• PSA104125 – Insulation Monitoring Module

• PSA104126 – Backup Power Module

• PSA104130 – Energy Analysis Dashboard Module

Energy Analysis Reports Module is available for purchase using the Sales Order portal.

Software Assurance
• PSA109137 – Power Operation Software Assurance

Developer License
• PSA109502 – Power Operation Development License

Integrating with Advanced Reporting and Dashboards

The Advanced Reporting and Dashboards Module offers a broad array of reports, dashboard
visualizations, and customizable report subscriptions.
• Power Monitoring Expert Reporting

Best in class reporting with more than 30 default reports, including Power Quality reports

Reports that can be triggered manually, scheduled, or event-triggered

Save reports as PDF, HTML, or CSV

• Power Monitoring Expert Dashboards
End user configurable dashboard view of historical data

Ability to embed external web content in a dashboard

Kiosk views to let teams see KPI Energy values that are relevant to them
• Power Monitoring Expert WebReach diagrams
Diagram-based view of real time device data
• Provide historical data to Power Advisor for analytics

When Power Operation and Power Monitoring Expert are integrated, historical applications from
PME (Reports and Dashboards) are integrated into the Power Operation runtime. WebReach
diagrams are also frequently integrated with Power Operation resulting in a seamless end user
experience.

7EN02-0462-03 Page 67 of 1312

Plan System Guide

The following table lists how components are used in combined solution:

Real time
information Historical
OPC UA and
(graphics, Alarms ENM Waveforms reports and
SMNP
tables, dashboards
trends)
Basic
Enabled
Reports
animated 1-
Enabled
line, Enabled when large built-in
LiveView,
used for data drivers within
Power Power
Enabled Enabled sequence acquisition Power
Operation Operation
of events such as 1 Operation
real time
analysis minute used
and
logging is
historical
required by
trends
customer
Enabled
Disabled
PME Web
Disabled Enabled
Power Vista, PME Reports and
Monitoring real time Disabled not used by Dashboards N/A
Expert and configured PME PQ integrated
historical with PME reports into Power
trends Operation
runtime

NOTE: Power Operation with Power Monitoring Expert must be the same product version to be
integrated.

Advanced reporting customizations

Power Monitoring Expert reports help customers better understand their electrical network.
Sometimes these reports require further customization. Report customization can be divided into
the following tiers:
• Basic – Colors, logo, toggle on/off report components, target lines.

• Advanced – Modify the format/layout of existing report templates, create new basic ones.
Excel and Power BI integration.
• Expert – Custom report creation. Create completely new reports with existing and new view
providers (data sets).

Page 68 of 1312 7EN02-0462-03

System Guide Plan

Device communication
The following device communication architectures can be used when integrating Power
Operation and Power Monitoring Expert:
• Multi-mastering all devices – Setting up device communications in both Power Operation
and Power Monitoring Expert
• Single-mastering all devices – Setting up device communications with Power Operation
and then transferring device data to Power Monitoring Expert using an Extract, Transform,
and Load (ETL) tool
Historical trending is assigned to Power Operation for most devices

Having Power Operation solely acquire data from meters provides the following benefits:
Improved performance: Power Operation trend acquisition can be assigned a lower
priority than real-time and alarm data thereby reducing CPU/RAM loads

Increased functionality: Allows PME reporting to be run on devices with protocols not
intrinsically supported by PME (e.g.: IEC-61850, DNP3, SNMP, BACnet, etc.)

Simplified deployments and maintenance: Devices are set up and maintained in

Power Operation only. Meaning there is no risk that device names between Power
Operation and PME are inconsistent.

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

Using ETL for communication with other

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

7EN02-0462-03 Page 69 of 1312

Plan System Guide

Single-mastering devices
When using single-mastering with Power Operation:

1. Power Operation acquires historical (trend) data from all devices.

2. The Extract-Transform-Load (ETL) tool transfers historical data from Power Operation to
Power Monitoring Expert for use in Power Monitoring Expert reports and dashboards.

NOTE: ETL is licensed as part of Advanced Reporting Module

Single-mastering is the preferred device communication architecture for the following reasons:
• Improved performance – Power Operation trend acquisition can be assigned a lower priority
than real-time and alarm data thereby reducing CPU and RAM loads
• Increased functionality – Allows PME reporting to be run on devices with protocols not
intrinsically supported by PME (for example: IEC-61850, DNP3, SNMP, BACnet, etc.)
• Simplified deployments and maintenance – Devices are set up and maintained in Power
Operation only. There is no risk that device names between Power Operation and PME are
inconsistent.
• Recovery from failure scenarios – If the Power Monitoring Expert Server or Power
Operation Primary Server become unavailable, the ETL can still transfer the data.

In test scenarios where PME communication was unavailable for 1.5 days and then became
available again, the ETL when triggered manually took the following times to catch up and re-
establish steady state for the following system sizes:
35,000 tags logged every 15 minutes: On average, the system took 30 minutes to recover
the lost 1.5 days' worth of data

105,000 tags logged every 15 minutes: On average, the system took 95 minutes to
recover the lost 1.5 days' worth of data

Page 70 of 1312 7EN02-0462-03

System Guide Plan

NOTE: When using single mastering, it is recommended that you increase the RAM beyond the
minimal RAM requirements for the system size.

There are exceptions where single-mastering cannot be used. See "Multi-mastering devices" on
page 71 for details.

Multi-mastering devices
The devices and Advanced Reporting and Dashboards Modules that require multi-mastering are
listed here.

Devices
Power Operation cannot single-master the following device types; they must communicate with
Power Operation and Power Monitoring Expert:
• ION9000, ION7650, and PM8000 (Power Quality meters)

Power Monitoring Expert requires a direct connection to these devices to provide data depth
in Power Quality Reports.
• BCPMs and PM5350 (multi-channel meters)

Power Monitoring Expert provides Branch Circuit Reports that leverage hierarchy information.

NOTE: Trending BCPMs and PM5350 can be reconfigured in the field. For example, instead
of using channels 1 to 10, BCPMs can be reconfigured to use channels 1 to 20. This
reconfiguration requires restarting the Power Operation Server.

NOTE: BCPM historical trends should only be gathered by Power Monitoring Expert, and
should be disabled in Power Operation. If you try to use the ETL to transfer branch circuit
power monitor (BCPM) trend data to the Advanced Reports Server, the amount of branch
circuit device data can overwhelm the ETL process.

NOTE: Disable trends in the Power Operation profile for any branch circuit meters unless
the customer would like to see real-time trending in Power Operation.

• Any meter that you want to view using WebReach diagrams.

WebReach diagrams require data acquisition from Power Monitoring Expert to provide real
time information.

Advanced Reporting and Dashboards

Modules
Certain Advanced Reporting Modules require devices to be setup in both Power Operation and
Power Monitoring Expert.

The following table list the modules and devices that require multi-mastering and the reason why:

7EN02-0462-03 Page 71 of 1312

Plan System Guide

Module Devices required on both servers Reason

Breaker Real-time vista diagrams leveraged
All Micrologic trip units
Performance by module
Energy Billing * Any device required for billing Requires data from Hierarchy
VIP is used to calculate the total kW
Power Efficiency Any device used in PUE calculation and interval energy for the PUE
calculation
Power Quality
All devices Due to the way PQ algorithms work
Performance

NOTE: This is addition to ION9000, ION7650, PM8000, PM5350, and BCPM.

* The Energy Billing Module relies on an energy billing ETL to export Power Monitoring Expert
data to be used in 3rd party billing software packages. Since the energy billing export ETL
requires data from the customer hierarchy, any devices required for the ETL should be added in
Power Monitoring Expert and Power Operation.

Interoperability
This section provides information on the different approaches and technologies for integrating
Power Operation with other systems and for extending and customizing your system.

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

Topic Content
"Power Operation OPC Standalone and redundant united architectures for data
UA" on page 72 exchange.
"EcoStruxure Building Integration architecture, component usage, data flows, and
Operation" on page 74 communication design.
"EcoStruxure Web
EWS for sharing Power Operation data with EcoStruxure Building
Services (EWS)" on page
Operation (EBO) and Power Monitoring Expert (PME).
76
Power Operation OPC DA Standalone and redundant architectures and data flow.
Extending Power
Extending Power Operation using CiCode scripting and CtAPI.
Operation

Power Operation OPC UA

Architecture #1: Simple system without redundancy

The following image illustrates the simple system that can be configured for a third-party
application that is consuming or sending OPC UA information to the Power Operation Server.

Page 72 of 1312 7EN02-0462-03

System Guide Plan

NOTE: OPC UA client/server is included and hosted on the Power Operation Server.

The OPC UA Server can support up to 100,000 tag subscriptions with 50,000 tag changes a
second to the OPC UA client.

Architecture #2: OPC UA client/server with Server redundancy

The following image illustrates a redundant Power Operation system that is sending and
consuming data from OPC UA to a third-party application.

The OPC UA Server for Power Operation does not support connecting to a client that supports
redundancy.

NOTE: OPC UA client/server is included and hosted on the Power Operation Server.

7EN02-0462-03 Page 73 of 1312

Plan System Guide

The OPC UA Server can support up to 100,000 tag subscriptions with 50,000 tag changes a
second to the OPC UA client.

EcoStruxure Building Operation

EcoStruxure Building Operation (EBO) integrated with Power Operation with Advanced Reporting
and Dashboards combines electrical and mechanical systems into a single advanced solution.

The main integration points in the EcoStruxure Building Operation and Power Operation with
Advanced Reporting and Dashboards architecture are:
• Power Operation EcoStruxure Web Services (EWS) provides alarm data and high level real
time data from Power Operation to EcoStruxure Building Operation graphics screens.

NOTE: On average, expect to a 10 second alarm and real-time data update time between
EBO and EPO systems.

• The EcoStruxure Building Operation to Power Monitoring Expert ETL sends mechanical data
to the historical database for display in dashboards and reports within PO or EBO.
• Integration of Reports and Dashboards from Power Monitoring Expert to EcoStruxure
Building Operation to view electrical data

The following table lists how components are used in a combined solution:

Page 74 of 1312 7EN02-0462-03

System Guide Plan

EcoStruxure Building Power Monitoring

Power Operation (EPO)
Operation Expert
Real time Enabled
information Enabled Disabled
(graphics, (graphics screens for
(animated one-line, (Vista, PME real time
tables, macro level real-time
LiveView) and historical trends)
trends) data and EBO trending)

Enabled

Alarms (EBO aggregates alarms Enabled Disabled

from PO and PME using
EWS)
Enabled
Disabled

ENM Not applicable (configured to

(not configured with
communicate with
PME)
Power Operation)
Enabled
Enabled
(used for Power Events
Waveforms Not applicable analysis alarming (used by PME Power
grouping and Quality reports)
visualization)
Basic Reports Enabled Enabled
Historical (PME Web Reports and
(when large data
reports and Not applicable Dashboards integrated
acquisition such as 1
dashboards into EBO or
minute logging is
required by customer) EPO runtime)

Enabled
OPC UA and (built-in drivers within
Not applicable Not applicable
SNMP Power Operation are
used)

Architecture #1: Simple EcoStruxure Building Operation system without

redundancy
The following image represents the simplest system that can be configured for Power Operation
and EcoStruxure Building Operation. EcoStruxure Building Operation is installed on a separate
machine from Power Operation.

NOTE: We do not support EBO on the same machine as Power Operation.

NOTE: EBO does not support redundant Power Operation architectures.

7EN02-0462-03 Page 75 of 1312

Plan System Guide

EcoStruxure Web Services (EWS) sends Power Operation alarm data to EcoStruxure Building
Operation. EcoStruxure Building Operation operators can acknowledge these alarms.
EcoStruxure Building Operation acknowledgments are then sent back to Power Operation.

NOTE: EWS for Power Operation must always be installed on a Power Operation Server.

EcoStruxure Web Services (EWS)

EcoStruxure Web Services (EWS) for Power Operation shares real-time, historical, and alarm
data with EcoStruxure™ Building Operations (EBO) and historical data with Power Monitoring
Expert (PME). Do not confuse this feature with the EWS Server that was released as a part of
PowerSCADA Expert/Vijeo Citect version 7.40 (which is for tag level process data).

EWS uses web-based HTTP protocol to transfer data. It enables two-way data transfers, which
allows the acknowledgment of alarms from EBO. To include this new EWS implementation in your
installation, select the EWS Server check box during installation.

EWS is set up and configured using the Application Configuration Utility.

Power Operation OPC DA

Architecture #1: Simple system without redundancy

The following image illustrates the simplest system that can be configured for a 3rd party
application that is consuming or sending OPC information to the Power Operation Server.

NOTE: OPC DA client/server is included and hosted on the Power Operation Server.

Page 76 of 1312 7EN02-0462-03

System Guide Plan

Architecture #2: OPC DA client/server with Server redundancy

The following image illustrates a redundant Power Operation system that is sending and
consuming data from OPC DA to a 3rd party application.

The ability to support the redundant Power Operation architecture depends on the 3rd party
application. If the 3rd party application does not have a concept of working with redundant
systems, then you should connect to the Primary Server, as pictured. Otherwise you can
configure the 3rd party application to connect to both Primary and Secondary Servers.

NOTE: OPC DA client/server is included and hosted on the Power Operation Server.

7EN02-0462-03 Page 77 of 1312

Plan System Guide

Extending Power Operation

Power Operation offers several means to extend and customize your system.

CiCode scripting
CiCode allows you to access all real-time data within Power Operation. It is a built-in and well-
documented scripting language requiring no previous programming experience to use.

CtAPI
CtAPI is an Application Program Interface (API) for programmers to create applications that
extend Power Operation by using industry standard programming languages such as C, C#, etc...
Using CtAPI requires programming experience.

NOTE: CtAPI data can be obtained from the Power Operation Server or thick Client. A Power
Operation Server or Client can support up to 10 concurrent CtAPI connections.

Architecture #1: Simple system without redundancy

The following image illustrates the simplest system that can be configured for a 3rd party
application that is consuming CtAPI data from the Power Operation Server:

CtAPI documentation can be obtained from this download link.

Architecture #2: CtAPI client with Server redundancy

The following image illustrates a redundant Power Operation system that can be configured for a
3rd party application that is consuming CtAPI data from the Power Operation Server or Client:

Page 78 of 1312 7EN02-0462-03

System Guide Plan

The ability to support the redundant Power Operation architecture depends on the 3rd party
application. If the 3rd party application does not have a concept of working with redundant
systems, then you should connect to the Primary Server (as pictured). Otherwise you can
configure the 3rd party application to connect to both Primary and Secondary Servers or a
separate Client.

CtAPI data can be obtained from the Power Operation Server or thick Client. A Power
Operation Server or Client can support up to 10 concurrent CtAPI connections.

Other extensibility resources

A complete list of Power Operation extensibility points can be obtained from the Power Operation
Integration Map. (download link)

Smart Connector Overview

Smart Connector unlocks data sharing with systems in which Power Operation does not already
have built-in communication support. Smart Connector is an open, extensible, and documented
application framework that simplifies integrations with third-party systems or data sources.

Using the Smart Connector development kit, software developers can create extensions to share
Power Operation real time and alarm data with other systems.

7EN02-0462-03 Page 79 of 1312

Plan System Guide

Options for Smart Connector extension development

• Have Schneider Electric do it for you: Those without software development capabilities
can contact the Digital Energy Center of Excellence to quote potential projects.
• Do it yourself: Customers, EcoXperts, and Digital Power Application Centers with software
development capabilities can download the Developers Guide for Smart Connector. Go to the
Schneider Electric Exchange for more information.

Smart Connector development overview

1. Learn about Smart Connector.

2. Develop extensions via .NET.

3. Install and Deploy Smart Connector Framework/Runtime and custom extension.

Smart Connector Architectures

Architecture #1: Smart Connector without redundancy

The following example architecture illustrates a simple Power Operation system without
redundancy using Smart Connector to send data to a third-party system:

Both Power Operation Server and Smart Connector are installed on the same physical or virtual
machines.

Architecture #2: Smart Connector with server redundancy

The following example architecture illustrates a redundant Power Operation system using Smart
Connector to send data to a third-party system that supports receiving redundant
communications:

Page 80 of 1312 7EN02-0462-03

System Guide Plan

Both Power Operation Server and Smart Connector are installed on the same physical or virtual
machines.

The ability to support the redundant Power Operation architecture with Smart Connector depends
on the third-party system. If the third-party system does not have a concept of working with
redundant systems, then you should only connect to the Primary Server.

NOTE: This system would require two sets of Power Operation Server and Smart Connector
licenses.

Architecture #3: Smart Connector distributed with server redundancy

The following example architecture illustrates a redundant Power Operation system using a
distributed Smart Connector architecture to send data to a third-party system that supports
receiving redundant communications:

7EN02-0462-03 Page 81 of 1312

Plan System Guide

Power Operation servers and Smart Connectors are distributed (installed on different physical or
virtual machines). This distributed architecture may be considered in order to achieve additional
scalability/performance of the system by isolating the streaming functionality of Smart Connector.

The ability to support the redundant Power Operation architecture with Smart Connector depends
on the third-party system.

NOTE: This system would require two sets of Power Operation Server and Smart Connector
licenses. Additionally, this system would require a Client Access license to be installed on each
separate Smart Connector instance. This Client Access provides the redundant communication
connection back to the Power Operation servers.

Smart Connector Requirements

Smart Connector requires a Microsoft SQL Server. Smart Connector integrations are only
supported with Power Operation 2021.

Supported Windows operating systems

• Windows 10 (64-bit only)

• Windows Server 2021 R2

• Windows Server 2016

• Windows Server 2019

Supported SQL Server versions used with Smart Connector

• Microsoft SQL Server 2012 Express/Standard/Enterprise/Business Intel

• Microsoft SQL Server 2014 Express/Standard/Enterprise/Business Intel

• Microsoft SQL Server 2016 Express/Standard/Enterprise/Business Intel

Hardware Requirements
Physical and virtual machine CPU and RAM requirements for Smart Connector will vary based on
a number of factors, including:
• Number of tags being shared with the third-party system.

• Data exchange rate of tags being shared with the third-party system.

• Specific third-party system end point requirements.

As a result, CPU and RAM requirements will vary by project.

Smart Connector Virtualization

Smart Connector supports both Microsoft Hyper-V and VMWare vSphere.

Virtualization configuration notes:

Page 82 of 1312 7EN02-0462-03

System Guide Plan

• Set all resource allocation (CPU, memory, and disk) to fixed; dynamic is not supported.

Do not share resources between virtual machines via over-allocation.

NOTICE
UNINTENDED DATA LOSS OR LOSS OF SOFTWARE FUNCTION
Do not exceed device limits.

Failure to follow these instructions can result in irreversible damage to

software and databases.

• If you are using shared drive storage, use Fiber SAN storage. If you are not using Fiber SAN
storage, use a direct attached, dedicated hard drive used by Smart Connector only.
• You must have a fixed-size disk virtual machine.

• Set host (for example: ESX host) power management to “High Performance”.

• You may need to adjust Quality of Service (QoS) to allow Smart Connector precedence over
less time-critical applications.
• Host a Smart Connector virtual machine on a host without other time-critical applications.

Additional virtual machine configuration guidelines vary by hypervisor.

EcoStruxture Anywhere
Power SCADA Anywhere is an HTML5 streaming application that allows for the visualization of
the Power Operation Runtime from any HTML5 compliant browser (Edge, Chrome, Firefox, etc)
by streaming a remote desktop application from a Client Access. This is a legacy solution that is
being substituted with the new HTML5 PO 2021 web client.

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

Topic Content
A description of the EcoStruxture Anywhere component, including
"EcoStruxture Anywhere purpose, what's new, upgrade considerations, supported
component" on page 83 operating systems, host requirements, browser requirements,
licensing options, and design considerations.
"EcoStruxture Anywhere
Example EcoStruxture Anywhere architectures.
architectures" on page 85
"Web Client versus Thick A comparison of features available in the thick client
Client" on page 62 (EcoStruxture Anywhere) and the HTML5 web client.

EcoStruxture Anywhere component

Power SCADA Anywhere is a legacy solution that is being substituted with the new HTML5
PO 2021 web client.

7EN02-0462-03 Page 83 of 1312

Plan System Guide

EcoStruxture Anywhere is an optional component. It is an HTML5 streaming application that

allows for the visualization of the Power Operation Runtime from any HTML5 compliant browser
(Edge, Chrome, Firefox, etc) by streaming a remote desktop application from a Client Access.

Upgrade considerations

Upgrade considerations from version 1.0 and 1.1 to version 1.2:

• License upgrade is not required if you are upgrading from Anywhere 1.x.

• For instructions on upgrading Power SCADA Anywhere Server, refer to the "Upgrading to a
New Version" section of the Power SCADA Anywhere Server Installation and Configuration
Guide.

Supported operating systems

Power SCADA Anywhere Server 1.2 software has been tested to run on:
• Microsoft Windows Server 2019

• Microsoft Windows Server 2016

• Microsoft Windows Server 2012 R2

• Microsoft Windows Server 2012

• Microsoft Windows Server 2008 R2 SP1

Host requirements

Power SCADA Anywhere host requirements for disk, CPU and RAM are negligible.

Power SCADA Anywhere host must have CPU with SSE2 instruction set support.

Browser requirements

Page 84 of 1312 7EN02-0462-03

System Guide Plan

EcoStruxture Anywhere is supported in the following browsers:

• Internet Explorer 11

• Edge

• Chrome

• Safari

When using the Power SCADA Anywhere client, we are assuming that the various components
listed below are integrated into a runtime experience that is being used in a Client Access such as
Power SCADA thick client graphics pages including 1-line diagram/engine built with Citect
graphics:
• PME reports, PME dashboards and PME WebReach Diagrams

• Power Operation Basic Reports

• LiveView (Power SCADA Real Time Tables implementation)

• Event Notification Module (configuration tools)

When these components are integrated into a runtime that is being streamed using Power
SCADA Anywhere all HTML5 client browsers listed above are supported.

Multiple instances of Power SCADA Anywhere can be opened at the same time in a web browser.
Windows Active Directory support

EcoStruxture Anywhere users can only be managed via Windows Active Directory. The machine
hosting EcoStruxture Anywhere must be installed on a machine that is part of a Windows domain.
Licensing options

Each EcoStruxture Anywhere license allows up to 5 concurrent connections to the runtime via
HTML5 web browsers. For more information on licensing, see "License keys" on page 163.
Design considerations
• EcoStruxture Anywhere requires an equal number of Power Operation Client Access to be
licensed.
• EcoStruxture Anywhere requires a domain to use Windows Remote Desktop licenses.

The EcoStruxture Anywhere host cannot be installed on a domain controller.

• Since EcoStruxture Anywhere uses Windows remote desktop connections, it requires an
equal number of Windows Remote Desktop Services (RDS) client access licenses to be
purchased.

EcoStruxture Anywhere architectures

NOTE: EcoStruxture Anywhere uses Windows Remote Desktop Services licenses. Also,
EcoStruxture Anywhere requires a domain. EcoStruxture Anywhere host may be a domain
controller.

7EN02-0462-03 Page 85 of 1312

Plan System Guide

Architecture #1: EcoStruxture Anywhere without redundancy

The following example architecture illustrates the simplest EcoStruxture Anywhere architecture.
All software and licenses are installed on the Server machine including Client Access (Control
Clients), Windows Remote Desktop Services, and EcoStruxture Anywhere.

Architecture #2: EcoStruxture Anywhere with Power Operation Server

redundancy
The following example architecture illustrates EcoStruxture Anywhere with Power
Operation Server redundancy:

Page 86 of 1312 7EN02-0462-03

System Guide Plan

All software and licenses are installed on the Server machine including Client Access, Windows
Remote Desktop Services, and EcoStruxture Anywhere.

Architecture #3: Isolated EcoStruxture Anywhere with Server redundancy

The following example architecture illustrates an isolated EcoStruxture Anywhere with Server
redundancy:

7EN02-0462-03 Page 87 of 1312

Plan System Guide

EcoStruxture Anywhere components are isolated using a 3rd machine (EcoStruxture Anywhere
Server) with software and licenses installed for Client Access, Windows Remote Desktop
Services, and EcoStruxture Anywhere.

Architecture #4: EcoStruxture Anywhere redundancy with Power

Operation Server redundancy
Use a stand-by set of EcoStruxture Anywhere Servers in case components on EcoStruxture
Anywhere Server #1 stopped working and policies prevented client use on the Power
Operation Server machines.

NOTE: EcoStruxture Anywhere clients would use different IP addresses to access EcoStruxture
Anywhere Server #1 vs. EcoStruxture Anywhere Server #2.

OFS system time stamping

Power Operation provides the System Time Stamping method for the electrical distribution
monitoring and control system.

System Time Stamping helps the user analyze the source of abnormal behaviors in an
automation system.
The benefits of the system time stamping mode are:
• No PAC programming required: All the time stamped events are managed and transferred
automatically by OFS
• Direct communication between the time stamping modules and the client: The available
communication bandwidth in the PAC is preserved

Page 88 of 1312 7EN02-0462-03

System Guide Plan

• Advanced diagnostic functions:

Signaling of uncertain SOE (sequence during which some events may be lost) to the
client

Time quality information is associated with each time stamped event

• No loss of events in normal operating conditions:
An event buffer stores the events in each event source module. The event buffer behavior
is configurable

Both rising and falling edge transitions can be stored for both discrete I/O and PAC
internal variables
• Works with both a redundant hot-standby PAC and redundant SCADA

The current limitations of the system time stamping are:

• A communication path between OFS and the time stamping sources is required, so, routing is
necessary in multi-layer architectures.
• 2 OPC servers (running for HMI and SCADA) cannot simultaneously access the same time
stamping source. A reservation mechanism is implemented.
• No detection of transition edges; the event detection is processed only on both edges.

The following table describes the main features and differences between these two methods.

7EN02-0462-03 Page 89 of 1312

Plan System Guide

Process System Time Stamping

1. Synchronize the time ERT module is synchronized by IRIG-B/DCF77 link and x80CRA
clock & M580 CPU are synchronized by the NTP server

2. Time stamping of events I/O events are stamped by x80 ERT modules & CRA
generation Internal variable values are stamped by the M580 CPU
3. Manage the time
Events are managed and transferred to Power Operation
stamped events in PAC
automatically by OFS
buffer
4. Transfer time stamped
Events are managed and transferred to Power Operation
events from PAC to
automatically by OFS
SCADA

Architecture selection

There are three types of modules which are supported by the system time stamping solution,
including the M340/eX80ERT, eX80CRA, and M580 CPU. In the system time stamping
architecture, OFS is used to automatically transfer the events from the time stamping module to
the SCADA. As the time stamping module and OFS are on separate subnets, it is necessary to
select a router to link these two subnets.

Page 90 of 1312 7EN02-0462-03

System Guide Plan

• In the standalone architecture, either select the NOC control module or a third-party router
connected to the CPU service port/NOC module which is linked to RIO network to set up the
connection between OFS and the time stamping module.

• In the HSBY architecture, either select the NOC control module as a router, or select a third-
party router directly connected to the RIO network to set up the connection between OFS and
the time stamping module.

7EN02-0462-03 Page 91 of 1312

Plan System Guide

Time synchronization
• The external NTP server provides the time clock for the CPUs and CRAs. Configure the NTP
server’s IP address and polling period for each NTP client. In the M580 architecture, the M580
CPU can act as an NTP server to synchronize its CRA module’s time clock.

Page 92 of 1312 7EN02-0462-03

System Guide Plan

• The IRIG-B 004/5/6/7 or DCF77 signals generated by the GPS receiver are used to
synchronize the ERT module’s time clock.

7EN02-0462-03 Page 93 of 1312

Plan System Guide

Event resolution
The resolution time is an important parameter for the time stamping application as it impacts the
precision of the sequence of events. Below is the list of the resolution times depending on where
the events are detected.

TS Events recorded by Events recorded by two

Events recorded by
source two modules of the modules of different
one module
module same type types

M340/x80
ERT

Min 2ms with IRIG-B

Depends on CRA or M580
Min 1ms resolution 004/5/6/7 Min 4ms with
scan time
DCF77

Page 94 of 1312 7EN02-0462-03

System Guide Plan

TS Events recorded by Events recorded by two

Events recorded by
source two modules of the modules of different
one module
module same type types

(e)X80
CRA

CRA scan time, average Depends on CRA or M580

Average 10ms resolution
3ms scan time

M580
CPU

CPU MAST task scan Depends on large M580 Depends on CRA or M580
time scan time scan time

SOE architecture design

This guide uses the M580 HSBY architecture as an example to design an SOE function.

7EN02-0462-03 Page 95 of 1312

Plan System Guide

In the above diagram, a cooling control system includes a circuit breaker, a contactor, a motor
controller, a motor, and a fan. The fan is used to cool down the system temperature when the
temperature is higher than the pre-set value. For the process automation monitoring, some device
statuses and process values need to be acquired by the PAC. Meanwhile, these statuses need to
be time stamped by the PAC for building an SOE service. The first step to designing the SOE
function is to define which time stamping module will be used to monitor the status of the devices,
and the process for generating the time stamping events. The table below shows which time
stamping module is associated with which event.

Event level Event name Source devices TS module

Process High temperature System temperature
events alarm instrument M340/eX80 ERT module
Motor alarm Motor
Overload Contactor
eX80 CRA with RIO
Fan status System cooling fan
Device events module
Over temperature Motor controller
M580 CPU with RIO
Manual operation Circuit breaker
module

Data flow design

The following image shows the flow of the time stamped data from the devices to the SCADA
using the system time stamping solution:

1. Events are detected and time stamped by the time stamping module

2. Manage the time stamping events using OFS

3. Transfer these events to SCADA using OFS, and display them on the SCADA pages

Page 96 of 1312 7EN02-0462-03

System Guide Install and upgrade

Install and upgrade

This section provides information about installing and upgrading.

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

Topic Content
"Getting the latest version
of Power Operation" on Describes how to get the latest version of the software.
page 97
Discusses how to install Power Operation, the files needed, and
"Installing" on page 97
prerequisites.
How to upgrade to the current or previous versions online or
"Upgrading" on page 111
offline.
"Offline upgrade in test
Provides information on setting-up test environments.
environment" on page 120
"Backing up and restoring
Discusses backing-up and restoring requirements and
a Power Operation
procedures.
system" on page 146
"Migration Tools" on page
Provides information on running migration tools after upgrading.
135
Provides information on activating Power Operation using license
"Licensing" on page 163
keys.

For more detailed resources on upgrading, see the Upgrade references section.

Getting the latest version of Power Operation

Go to www.se.com to download the most recent software ISO file for Power Operation. To find the
most recent Power Operation ISO file, search for Power Operation and refine your search results
by selecting the Software/Firmware checkbox.

See Version info to identify the version of Power Operation installed.

If your license is out of support, contact your Schneider Electric account manager or email
[email protected] with your license and site ID details.

Go to the AVEVA Knowledge & Support Center website for information on PLANT SCADA.

Installing
You can install Power Operation with Advanced Reporting and Dashboards as a new product
only.

Power Operation does not support different versions running side-by-side. If you are upgrading
from an earlier version of Power Operation, back up your existing project files. These files include
LiveView templates; reporting configurations (such as email addresses); and Profile Editor
custom tags, device types, profiles, and units (in the Program Data folder).

Uninstall prior versions before installing v2021.

7EN02-0462-03 Page 97 of 1312

Install and upgrade System Guide

Remove existing Power Operation License Configuration Tool installations before installing the
new version.

Before proceeding with the installation of Power Operation with Advanced Reporting and
Dashboards and optional components, refer to "Before installing" on page 98 for detailed
installation prerequisite information.

Before installing
This section describes the requirements for hardware, operating system software, and system
configuration prior to installing Power Operation with Advanced Reporting and Dashboards and
any of its components.

These requirements vary based on the components of Power Operation with Advanced Reporting
and Dashboards that you install on any computer. This section identifies the basic system
software requirements, as well as requirements specific to each component. Refer to "Core
components selection" on page 103 to determine the components that you want to install.

WARNING
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
Apply all Windows security updates on machines running Power Operation and Power
Monitoring Expert.

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

Before you begin to install Power Operation with Advanced Reporting and Dashboards, install the
latest updates from Microsoft for your operating system and system software. See "Preparing
servers" on page 102 for more information. Also see the Operating System Matrix that shows the
operating systems that are compatible with various versions of Power Operation.

Pre-installation checks
Depending on your operating system version, your SQL Server edition, and the setup type (server
or client) that you select for installation, the installer performs some or all of the following tasks
prior to the installation of the software:
• Check for .NET Framework 4.7 and automatically installs it if required.

• Uninstall previous versions. If a previous version of the software is installed, installation will
stop.
• Verify that the SQL Server Agent is installed. If not found, the installer will install SQL Server
Express. (Advanced Reporting and Dashboards only.)
• Validate that a supported SQL Server edition and service pack level are installed (Advanced
Reporting and Dashboards only).
• Check the database location. The database must be local for some installation types and
remote for others. (Advanced Reporting and Dashboards only.)
• Check for 32-bit SQL Server edition (Advanced Reporting and Dashboards only).

Page 98 of 1312 7EN02-0462-03

System Guide Install and upgrade

• Check for the presence of ASP.NET.

• Verify that the appropriate account permissions are defined, for example, that the SQL Server
system administrator (sa) account is set with Administrator as the user (Advanced Reporting
and Dashboards only).
• Verify that the Windows account that the SQL Server service runs under has the proper folder
permissions to proceed (Advanced Reporting and Dashboards only).

Supported environments
Review the "Computer requirements" on page 56 section to ensure that your hardware and
system software meet the requirements for your selected installation.

Compatible Windows Operating Systems

The following table illustrates the compatible operating systems for all versions of Power
Operation with Advanced Reporting and Dashboards:

NOTE: 64-bit operating systems are recommended for best performance.

Operating System Power Operation Version

2021 2020 9.0 8.2 8.1

Windows Server 2019 – – –

Windows Server 2016 –

3 2 1
Windows 10

Windows Server 2012 R2

Windows 8.1 – – –

Windows Server 2012 – –

Windows Server 2008 R2 – – –

Windows 7 – –

1: Available with 8.1 update 6 or later

7EN02-0462-03 Page 99 of 1312

Install and upgrade System Guide

2: Requires Windows 10 version LTSB 1607 and later (64-bit only)

3: Requires Windows 10 version LTSB 1607 and later (64-bit only) or Windows 10 1803 and later

(64-bit only)

Windows OS and Server configuration

Each version of Power Operation is tested against latest Microsoft Windows OS patches up until
the date of each software version's release.

Apply Windows patches to the operating system hosting the Power Operation installation. When
applying Windows patches do so periodically and verify proper functioning of the Power SCADA
server immediately after patch installation. With redundant Power SCADA servers update one
server at time; if a Windows patch causes the Power SCADA server to function improperly the
redundant server will maintain monitoring and control of the system until the problem is resolved.

For instructions about Windows services or SQL server, see the Power Monitoring Expert –
IT Guide.

IIS configuration

Component Category Component

Common HTTP Features
Static Content
Default Document
Web Server
HTTP Errors
HTTP Redirection
ASP.NET 3.5
ASP.NET
.NET Extensibility
Application Development ASP (Power Operation only)
ISAPI Extensions
ISAPI Filters
HTTP Logging
Health & Diagnostics
Tracing

Page 100 of 1312 7EN02-0462-03

System Guide Install and upgrade

Component Category Component

Basic Authentication

Windows Authentication

Digest Authentication
Security

URL Authorization

Request Filtering

IP Security

Performance Static Content Compression

Dynamic Content Compression

IIS Management Console

Management Service (Power Operation only)

Web Server Management
Tools
IIS Management Scripts and Tools

IIS Metabase and IIS 6 Configuration Compatibility

Windows Process WAS-Process Model

Activation Service
WAS-NetFxEnvironment

WAS-ConfigurationAPI

NetFx4Extended- WCF-HTTP-Activation45 (Advanced Reports and Dashboards

ASPNET45 only)

For details about IIS configuration, see the following table:

Application Pool Application

EcoStruxure™ Web Services
AppMods LiveView Viewer
Power Operation Basic Reporting
PlatformServerAppPool PlatformServer
PsoWebserviceAppPool PsoWebservice
WebHmiAppPool WebHmi, PsoDataService

7EN02-0462-03 Page 101 of 1312

Install and upgrade System Guide

SQL Server
Power Operation with Advanced Reporting and Dashboards requires SQL Server to host several
databases.

Windows Services in Power Operation

Service Description
Obtains configuration data, real-time process data, historical trends,
Schneider Electric
and alarms from the PowerSCADA I/O, Alarm, Trend and Report
CoreServiceHost
servers (citect32.exe)
Aveva Deployment Process project deployment requests on the deployment client in a
Client Service PSO system
Aveva Deployment Process project deployment requests on the deployment server in a
Server Service PSO system
Aveva Runtime Runs PowerSCADA I/O, Alarm, Trend, and Report servers
Manager (citect32.exe) as a Windows service.

Preparing servers
The software Installer performs several of the setup and configuration tasks during installation to
ensure that the prerequisites for your Power Operation with Advanced Reporting and Dashboards
system are met. Complete the following before proceeding with the installation.

Updating the operating system

WARNING
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
Apply the latest updates and hotfixes to your Operating System and software.

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

Run the Windows Update service to install the latest security patches and hotfixes from Microsoft.

Advanced Reporting and Dashboards

Module Server
For more information on server requirements and preparation, see the "Advanced Reporting and
Dashboards component" on page 44.

Component selection
Decide which Power Operation with Advanced Reporting and Dashboards components and add-
ons you want to install.

Page 102 of 1312 7EN02-0462-03

System Guide Install and upgrade

Core components selection

The installer provides a list of options to help you select the appropriate components during
installation. The options are described here.

Runtime Environment
Selects Runtime, Sentinel Driver, and Communications Drivers for installation. It is an installation
that installs the runtime components for both a Server and Client. This installation includes
runtime infrastructure files, Client and I/O Server, Alarm Server, Trend Server, and Reports
Server.

Select this option if this is an installation of Power Operation that will act as a server to service
many client installations.

Configuration and Development Environment

Installs the design-time configuration environment. Users who have sufficient security privileges
can set up graphics pages, create reports, and the like. The configuration tools include: Power
Operation Studio, Application Configuration Utility, IO Device Manager, Project Setup, Project
Backup/Restore, and the Power Operation Runtime.

Deployment Client
Installs the Deployment Client component, which allows projects to be deployed to this machine
remotely.

Deployment Server
Installs the Deployment Server component, which allows projects to be administered, versioned,
and deployed to other remote Deployment Client machines from this machine. The server can roll
out project changes to the various computers in your project.

Add-ons selection
After you select the core components that you want to install, select any add-ons that you want to
include in your installed system. The options are described here:

Project DBF Add-in for Excel

Installs an Add-In for Microsoft Excel. When this Add-In is loaded into Excel, it allows you to
browse, open, edit and save Power Operation .dbf files in the correct format. This is only available
for selection if Microsoft Excel 2007 or above is installed on the computer. Otherwise, it is visible
but is deselected and disabled.

Power Operation Web Server for IIS

Installs a Web Server running on Microsoft Internet Information Service (IIS). The Web Server
performs the server-side functionality of a Web Service to the Web Client. As well as facilitating
communication, it directs a client to the graphical and functional content of a Power Operation
project, and the location of the runtime servers. This information is stored on the Web Server
when a Power Operation project is deployed. A Web Server can contain multiple deployments.

7EN02-0462-03 Page 103 of 1312

Install and upgrade System Guide

NOTE: If the Web Server and Power Operation Server are set up on different machines, and it is
not possible to establish a trust relationship between them, the two machines need to be on the
same domain so that the Web Server can access the directory on the Power Operation Server
that is hosting the web deployment files.

If a trust relationship is established between the Web Server and the Power Operation server,
they can be on different domains if the Web Server has read access to the project folder on the
Power Operation Server.

Power Operation Reporting

Installs the Power Operation basic reports.

The Power Operation Profile Editor

Installs the Profile Editor. Profile Editor lets you create tags, device types, devices, and projects
outside of the Power Operation Studio environment.

The Power Operation LiveView

Installs LiveView. LiveView lets you create table templates for real-time system readings.

System software order of installation

This section provides an overview of the general steps required to install:
• Power Operation

• Advanced Reporting and Dashboards Module files: Advanced Reporting and Dashboards

• Extract, Transform, and Load (ETL): Use this module to extract historical data from Power
Operation and transform it into a format that can be used in the Advanced Reporting and
Dashboards Module.
• EcoStruxture Anywhere

Before you begin, you need the following items:

• Installation medium for Power Operation with Advanced Reporting and Dashboards and
Power Operation 2021 Installation Guide.
• Installation medium for ETL and EcoStruxture Anywhere (included on the Power Operation
with Advanced Reporting and Dashboards ISO).
• Installation medium for .NET Framework 4.7.2, downloaded from Microsoft.

• Installation for Microsoft SQL Server.

NOTE: SQL Express is included on the Power Operation with Advanced Reporting and
Dashboards ISO. Microsoft SQL Server must be obtained from Microsoft.

On the Power Operation Server Computers

The following table lists software that you will install on each of the servers and clients in your
project.

Page 104 of 1312 7EN02-0462-03

System Guide Install and upgrade

Advanced Reporting
Power Operation Power Operation EcoStruxture
and Dashboards
Primary Server Secondary Server Anywhere
Server
Power Operation
Power Operation Power Operation
2021 client access SQL Server
2021 2021
only
Advanced Reporting
EcoStruxture and Dashboards
Anywhere (from the Power
Operation ISO)
Windows Terminal
Services must be ETL
enabled.

Power Operation Server Computers

Install all operating system updates before you install Power Operation.

On the server that you will use for Power Operation, install software in the following order:
• Verify that you have the correct Internet Explorer version for your operating system. See Web
Client versus Thick Client for more information.
• Install .NET 4.7.2

• If you want to have Matrikon Explorer on the computer, install Matrikon before you install
Power Operation.
• Install Power Operation.

On the Advanced Reporting and Dashboards Computer

On the server that you will use for the Advanced Reporting and Dashboards Module, install the
software in the following order:
• Microsoft SQL Server: You must install SQL Server on the Advanced Reporting and
Dashboards server. Refer to the Power Monitoring Expert 2021 – System Guide for
information.
• Advanced Reporting and Dashboards Module: Use the Power Operation with Advanced
Reporting and Dashboards installation medium and installation guide.
• On the Advanced Reporting and Dashboards Module server only, install ETL. See "Installing
the ETL Administration Tool" on page 107 for details.

NOTE: The installation medium is located on the same DVD or .ISO as the Power Operation
installation, in the Advanced Reporting and Dashboards Module folder.

On the EcoStruxture Anywhere Server Computers

You need to install EcoStruxture Anywhere on a remote client computer. See "Configure the
Power Operation Secondary Server" on page 670 for directions.

7EN02-0462-03 Page 105 of 1312

Install and upgrade System Guide

Installing the software

When you begin the installation, if any required system software is not detected, you must install it
before you can begin the Power Operation with Advanced Reporting and Dashboards installation.
For example, if you have not yet installed .NET Framework 4.7.2, you will be prompted to install it
first.

Required for this procedure:

• Do not have Windows Update running when you install.

• Microsoft .NET Framework 4.7.2 installed.

1. Go to www.se.com and download the software ISO file. To find the most recent software
ISO file, search for Power Operation and refine your search results by selecting the
Software/Firmware checkbox.

2. Extract the ISO files.

3. Open MainSetup.exe: The Power Operation installer opens.

4. Select the Core Components you want > select Next. See "Core components selection" on
page 103 for a description of each component.

5. Select the Add-ons you want > select Next. See "Add-ons selection" on page 103 for a
description of each add-on component.

NOTE: Project DBF Add-in for Excel can only be selected if Microsoft Excel 2003, 2006,
2010, or 2013 is installed on the computer.

6. Select Destination Folders for the files > select Next.

7. Enter a password for the Database Engine > select Next. The password cannot contain the
following special characters: $ %

8. Enter a password for the Power Operation Database > select Next. The Check System
screen opens. The password cannot contain the following special characters: $ %

If the installation is unsuccessful:

a. Select Open Log to review where the installation stopped.

b. Note the files that need to be corrected, and correct them in the order they are

Page 106 of 1312 7EN02-0462-03

System Guide Install and upgrade

presented.

c. After you make the corrections, select try again to re-install PO.

d. Repeat this step, as necessary, until all problems are solved.

9. When System Verified is displayed on the Check System screen, select Next. The Ready
to Configure screen opens.

10. Review the component list > select Install.

11. Select Close when the installation is complete.

Depending on your system architecture, complete the installation of the Power Operation with
Advanced Reporting and Dashboards system components.

Refer to Plant SCADA help for information about configuring a system management server,
deployment server, and TLS certificate management.

Installing the ETL Administration Tool

The ETL tool extracts historical data from and transforms it into a format that loads it into Power
Monitoring Expert. Install ETL on the machine hosting Advanced Reporting and Dashboards.

Go to the Schneider Electric Exchange and download the ETL Administration tool.

Install ETL on the machine hosting Advanced Reporting and Dashboards. Install the ETL
Administration Tool on the Power Monitoring Expert server using a Windows Administrator
account.
To install ETL for PO:

1. In Windows Explorer, navigate to \Power Operation with Advanced Reports ETL.

2. Copy the PO to PME ETL EXE to the PME server.

3. Double-click SegApps_ETL_PowerSCADA-xxx.exe.

(Where xxx is the build number.)

4. Application Language: Select your preferred application language from the drop-down list
and click Next.

NOTE: The ETL Administration Tool supports English only.

5. Welcome: Review the steps and click Next.

6. License Agreement: Read the End User License Agreement and if you accept the terms of
the agreement, click I Agree to proceed.

7. Setup Type: ETL: Power Operation 2021 can only be installed with the Standalone Server
option. Click Next.

8. File Destination: Click Next to install the ETL tool to the default location. To select a
different location, click the ellipsis button and then select a new location. Click OK.

7EN02-0462-03 Page 107 of 1312

Install and upgrade System Guide

9. Check System: The installer checks the operating system. If a condition affecting
installation is detected, the installer notifies you to correct it. When verification is successful,
click Next.

10. Ready to Configure: A summary of your configuration choices for the installation. Ensure
that all items are correct before proceeding.

11. Click Install to continue or click Back to move back through the installer and change any
items.

The Copy Files screen appears and the ETL files are copied to the system.

12. Configure System: The selected configuration settings are applied.

13. Click Next.

14. Complete: The Complete page appears after the install is successful. Click Installation
Log to view details recorded for the installation process.

15. Click Close to finish.

After installing the ETL (PO to PME) you will need to allow the ETL to remotely access the Power
Operation Server. See "Allowing ETL remote access to the PO Server" on page 1054 for details.

Install Power SCADA Anywhere Server

EcoStruxture Anywhere allows a remote desktop session using a Web browser to the Power
Operation Server. It is accessible only in the Power Operation Runtime.

EcoStruxture Anywhere is a rebranded name for Citect Anywhere. The term Power SCADA
Anywhere will appear only in the end user-facing Web browser, at the login screen and the launch
screen. Everything that is not end user-facing will be referred to as Citect Anywhere, including the
installer, the configuration tool, and various file paths. EcoStruxture Anywhere is available for
download on the Schneider Electric Exchange.
Prerequisites
• Before installing EcoStruxture Anywhere, you must first install the EcoStruxture Anywhere
Server.
• Install a Power Operation Client Access. For the Power Operation Client Access, run the
Power Operation install and select the client access-only installation. This installation requires
a floating license. It must be on one of the following operating systems: Windows Server 2008
R2 SP1 Standard, Enterprise (64-bit)
Windows Server 2012 Standard

Windows Server 2016

Windows Server 2019

To install EcoStruxture Anywhere:

1. On the machine where the EcoStruxture Anywhere server is installed, open the installer
from the EcoStruxture Anywhere installation folder: double-click setup.exe.

2. Click Citect Anywhere Server:

Page 108 of 1312 7EN02-0462-03

System Guide Install and upgrade

3. Accept the license agreement and click Next on each screen of the installation. If a
prerequisite is missing, it will be installed for you.

4. When installation is complete, you see a confirmation screen. Click Finish to close the
install.

For detailed instructions on installing and using the EcoStruxture Anywhere Server, see the
following documents:
• EcoStruxture Anywhere Quick Start Guide.pdf

• EcoStruxture Anywhere Installation and Configuration Guide.pdf

These documents in the EcoStruxture Anywhere Installer folder.

Installing CAE
Cybersecurity Admin Expert (CAE) software tool installation requirements:
• Windows® 10 Pro 32-bit or 64-bit.

• Windows Server 2019, Windows Server 2016 64-bit, or Windows Server 2008 R2 64-bit

• Cybersecurity Admin Expert ZIP file.

ZIP file x86 for Windows 10 Pro 32-bit.

ZIP file x64 for Windows 10 Pro 64-bit.

• Other software components automatically installed in order to properly run CAE.

• Windows administrator username and password sign-in credentials.

7EN02-0462-03 Page 109 of 1312

Install and upgrade System Guide

1. Right-click the Cybersecurity Admin Expert ZIP file and select Extract All... > Extract.

2. Double-click the EXE file. The Cybersecurity Admin Expert wizard opens.

3. Select language > OK.

4. Click Install.

5. Click Next to go through the screens and select the options you want.

6. Click Install.

7. Click Finish. Cybersecurity Admin Expert icon is created on the desktop.

See Configuring CAE cybersecurity for detailed steps on configuring CAE.

After installing the software

Maintaining system currency
After you install and configure Power Operation 2021 with Advanced Reporting and Dashboards
and deploy it as your production system, it is very important that you keep your software up to
date. Schneider Electric will periodically publish updates in the form of service releases, hot fixes,
or advisories relating to safety, security, and functionality of Power Operation.

Getting started with Power Operation

Power Operation is a suite of tools that lets you develop, design, and deploy SCADA systems.
Built on the Plant SCADA platform, Power Operation Studio is the main SCADA development
portal. Use Power Operation Studio to:
• Create, manage, and customize SCADA projects

• Create and manage I/O devices

• Design Power Operation Runtime elements

• Manage user access

• Open other SCADA productivity tools.

Power Operation is shipped with a project that has example page configuration.
To open Power Operation Studio:
• Click Start > Schneider Electric > Power Operation Studio

OR
• From the desktop, open the Power Operation folder and then open Power Operation Studio.

Uninstall and reinstall Power Operation

Use Add/Remove Programs in the Windows Control Panel to uninstall these programs:
• Power Operation v2021 (if you uninstall this, you also uninstall the Profile Editor)

• Power Operation Profile Editor

• Any additional Power Operation programs, such as the WebServer, that you installed

Page 110 of 1312 7EN02-0462-03

System Guide Install and upgrade

If you uninstall programs after you have already created projects, the project data will not be
deleted. It is in [Project Drive]\ProgramData\Schneider Electric\Power
Operation\v2021\User. The first time you open the application after you re-install it, it will
locate the project data and re-link it.

Uninstall does not remove all files from the system. Decommissioning removes Power Operation
files from your system to prevent potential disclosure of sensitive, confidential, and proprietary
data and software from your Power Operation system. You risk disclosing your power system
data, system configuration, user information, and passwords if you don’t decommission. We
strongly recommend you decommission your system at the end of its' life. See "Decommission"
on page 912 for more information.

Upgrading
Use this section upgrade an existing installation of Power Operation to Power Operation 2021 R1
(Citect SCADA File v8.3).

It is recommended to upgrade using the latest version. Before installing, check that you have the
most recent software ISO file. There may be additions or updates to the files.

For instructions related to previous versions of Power Operation, use the documentation for that
version.

See Version info to identify the version of Power Operation installed.

How to get upgrade files

• Go to www.se.com and download the most recent software ISO file. To find the most recent
Power Operation ISO file, search for Power Operation and refine your search results by
selecting the Software/Firmware checkbox.
• If you use Power Monitoring Expert for Advanced Reporting and Dashboards, download the
ETL Administration tool. See Installing the ETL Administration Tool for more information.

Upgrade information
For version Power Operation v7.20 and later, cross version compatibility is not available for
alarms.

Prerequisites
• Verify source and destination paths while backing up projects. Path names may be different
from those used in previous versions.
• Backup existing projects to later restore them in the upgraded version.

NOTICE
LOSS OF DATA
Backup your project and other relevant historical data files from all servers in the system.

Failure to follow these instructions can result in a loss of data.

7EN02-0462-03 Page 111 of 1312

Install and upgrade System Guide

• Confirm hardware, operating system, and software on each computer meet requirements for
production servers and clients. See Installing for information.
• Add additional computer resources when using Advanced Reports and Dashboards modules
to Power Operation servers.
• Upgrade license keys for the project.

• Identify server and client license key serial numbers. Generate upgrade authorization codes
using the online license generator and save the codes and the serial numbers to a text file.
This ensures the production site can upgrade and operate Power Operation. It also ensures
all the keys are registered to the correct site.
• Identify the version of Power Operation in use at the production site. See Version information
for details.
• Choose the upgrade options you want:
Integration of Diagnostics feature.

Integration of Advanced Reports and Dashboards.

Modify persistent memory devices currently using the DISKXML driver, by updating them
to use the IEC61850N driver. As shown below, set the following properties:
Protocol: IEC61850N.

Startup Mode: Primary or StandbyWrite if configuring a redundant instance of the

device.

Memory: TRUE.

Priority: 1 or 2 if configuring a redundant instance of the device.

Persist (extended field enabled by pressing F2): TRUE.

Persist Period (extended field enabled by pressing F2): Default is 10 minutes

(00:10:00) or set to a different value based on how frequently this memory device's
data is cached to disk.

Upgrade steps
1. Choose an Upgrade method: Offline or Online.

2. Determine the Upgrade path.

3. Perform an Offline upgrade in test environment to upgrade and migrate the existing project
to Power Operation v2021. Upgrade in a test environment before going to the production
site or upgrading.

4. Complete the upgrade in a Production environment.

Refer to Upgrade references for detailed information on the steps you may need to perform before
and after the upgrade process. Review the information up to and including the version to which
you are upgrading.

Go to the AVEVA Knowledge & Support Center website for information on PLANT SCADA Cicode
functions and Citect INI changes with each release.

Page 112 of 1312 7EN02-0462-03

System Guide Install and upgrade

Upgrade method
Before upgrading, determine if your SCADA system can go offine for the upgrade and what
availability is required for historical information.

There are two upgrade methods. Click an option and follow the instructions:
• Offline upgrade: system shut down is required during upgrade. If your SCADA system can go
offline during the upgrade or the availability and loss of historical information is not an issue,
use this method.
• Online upgrade:

System shut down is not required during upgrade. If your SCADA system cannot go
offline during the upgrade or the availability and loss of historical information is not an
issue, use this method.

At least one pair of redundant servers must be in use and available.

system shut down is not required during upgrade.

Upgrade path
The upgrade path to get to the version you want may include upgrading to other versions first.

When you perform an online upgrade to the latest version, the Accept encrypted and non-
encrypted connections (mixed mode) setting is on by default on the configurator's Encryption
page. You can clear this option prior to performing the upgrade if you want to use unencrypted
communications. You can also configure your system to use encryption after the upgrade process
is complete.

Upgrade path requirements based on method

• Offline upgrade : upgrade your project directly into the latest version from v7.20 SR1 and
after.
• Online upgrade: runtime and historical data are migrated and upgraded, you need to follow an
upgrade path that depends on your starting version.

Upgrade path requirements and notes based on version

• v2020 R2, v2020, v9.0, v8.1 or v8.0 SR1: When doing an online upgrade, check that any
pre-7.20 Alarm Save files are removed from the v2021 project folders. For example, <project_
cluster>_ALMSAVE.DAT and <project_cluster>_ALMINDEXSAVE.DAT.
• v7.30 or v7.30 SR1: Restore your project to v7.40. Compile and run your project to restore
and convert your historic alarm data. If the existing project uses the ES_StartAdvOneLine()
function, instead use PLS_StartAdvOneLine available in all Power Operation versions since
v7.30.
• v7.20 SR1 and earlier: Upgrade to v7.20 SR1. Compile and run your project to restore and
convert your historic alarm data. After v7.20, the dynamic one-line animation engine and
related genies are different, so updates may need to be made to a v7.20 project you are
upgrading to ensure correct operation of the dynamic one-line animation in the project.

Upgrade path requirements based on Advanced Reporting and Dashboards

7EN02-0462-03 Page 113 of 1312

Install and upgrade System Guide

• Advanced Reporting and Dashboards Module v2021 must be used with Power Operation
2021 R1.
• An upgrade might be required for the Advanced Reporting and Dashboards software (Power
Monitoring Expert).
• Versions of Power Operation and Power Monitoring Expert must be the same.

Offline upgrade
Use this procedure to perform an offline upgrade to Power Operation 2021 R1.

Perform the offline upgrade process in a test environment and before traveling to the production
site. Doing this will identify potential conflicts in the upgrade process that can be fixed before
attempting an online upgrade. This will minimize server downtime in the online upgrade process
or save time and effort if completing an offline upgrade in the Production environment.

Page 114 of 1312 7EN02-0462-03

System Guide Install and upgrade

1. Backup your current project and other relevant files from all servers in the system:

File to backup Description

This is the main file to back up. For information about backing up
Project backup (.ctz a project, refer to your current version's online help. You need to
file) have the Save sub-directories and Save configuration files
options selected in the Backup dialog.
Citect.ini This file is in the config folder.
If you have deployment configured, back up the following files:
Deployment • SE.Asb.Deployment.Server.WindowsService.exe.config
configuration files • SE.Asb.Deployment.Node.WindowsService.exe.config.
These are in the path [CtEdit]Config.
Data directory This file is found on the path [CtEdit]Data
This is in the Deployment directory. For example:
Deployment database
%PROGRAMDATA%\AVEVA Plant SCADA 2020 R2\Deploy

ALMSAV.DAT and <ProjectName>_<ClusterName>_ALMSAV.DAT and

ALMINDEXSAVE.DAT <ProjectName>_<ClusterName>_ALMINDEXSAVE.DAT.
(For v7.20) These files contain alarm configuration data as well as runtime
data. Their path is defined in the Citect.INI file. The default path
OR is same as the data directory path.
Alarm Database (for The Alarm Database is located in the Data directory:
v7.30SR1, v7.40, [Data]\<Project Name>\<ClusterName.AlarmServerName>.
v7.40SR1, v8.0, For each alarm server you have in your system, a corresponding
v8.0SR1, v8.1, v8.2, Alarm Database will exist. You need to backup all alarm
and v8.3) databases.
The path and names of these files are defined on the trend tag
itself and created in the Data directory defined in [CtEdit]Data.
Trend files: *.HST and
The files will be named after the trend name and number of files.
*.00X
For example, if the trend name is CPU, file names will be
CPU.HST, CPU.001, CPU.002, etc..
These files contain the code that is executed on your reports,
Report Files
and are in the [CtEdit]User\<Project Name> folder.

7EN02-0462-03 Page 115 of 1312

Install and upgrade System Guide

File to backup Description

Power Operation includes some ActiveX controls, which are
available with this version, but you need to take a backup of your
custom ActiveX controls.

Check your ActiveX.dbf file in the [CtEdit]User\<Project Name>

folder. This file contains a list of the ActiveX controls in your
Custom ActiveX project and their GUID. Using the GUID, find the path of an
Controls (.OCX) ActiveX control using the Windows Registry key:

KEY_LOCAL_
MACHINE\SOFTWARE\Classes\CLSID\"GUID"\InProcServer3
2\.

The default value for this key is a path to the .DLL or .OCX file
you need to back up.
Backup the main <Project Folder>\Analyst Views and <Project
Process Analyst files
Folder>\Dictionary folders.
These files contain any logging (alarm logs, report logs) you
Device logs have configured in your project. You will find their location in the
Devices dialog.
Check your Citect.ini file or use the Setup Editor | Paths
section as it could contain runtime files used by custom code in
the project.
Additional Files It is also recommended to search C:\ or other volumes where
multiple hard disks are installed, in the Power Operation
Studio > Find and Replace tool. These search results will
display any paths in use by all project components.
If you are aware of any driver hotfix in your system, backup this
driver DLL which is in the Bin directory where Power Operation
is installed.

NOTE: The fixes contained in this hotfix might be included in

Driver Hotfixes
the drivers which ship with this version.

Go to the Power Operation Schneider Electric Exchange for

additional driver downloads or Citect Driver Web for additional
driver downloads.

2. Upgrade your licenses.

Have a valid support agreement, or purchase an upgrade license, and upgrade your key or
soft license using the online license generator.

If your license is out of support, contact your Schneider Electric account manager or email
[email protected] with your license and site ID details.

Page 116 of 1312 7EN02-0462-03

System Guide Install and upgrade

3. Uninstall the current version and install the latest version and proceed with upgrading and
migrating the project configuration for later use in the production environment. See Upgrade
path for details on upgrade requirements based on version.

If upgrading in a production environment as part of an Offline or Online upgrade

process: Uninstall the current version of Power Operation and install the next version
specified in your upgrade path.

If this is step is done in a test environment: It is unnecessary to install the next software
version in the upgrade path. Upgrade directly. Go to the Power Operation Schneider
Electric Exchange for downloads.

4. Configure the Server Password using the Computer Setup Wizard. See Power Operation
Server password.

5. Configure the System Management Server: In the Plant SCADA help search box, type
Configure a System Management Server and click the search icon.

6. Restore your project and select all included projects if available. PLS_Include will be
restored.

7. Upgrade your project.

As a default, when you restore your project from a previous version, Power Operation
will force an update, and you will get a warning message. Click Yes to proceed with
project upgrade. If this message is not displayed, you can force an update of all projects
by setting the [CtEdit]Upgrade INI parameter to 1 and restarting Power Operation.
After you restart, you will get a warning message.

Pack all projects in the Power Operation Studio > Projects screen and Pack Libraries in
Active and Included projects in the Graphics Builder > Tools menu.

8. Migrate your project.

The automatic project upgrade does not fully upgrade your projects, and needs to be
followed by the Migration tool. The Citect and Power Operation Migration Tools are separate
applications that must be run manually after the project upgrade has been executed, and
adds computers from the existing topology. You might need to run the Citect Migration tool
separately for other components. Refer to the online help for more information about running
the Citect Migration tool.

Run the Citect and Power Operation Migration Tools.

Confirm that all IO devices in the project have been assigned Equipment names.

9. Merge your .INI file.

In addition to the INI settings below, identify other custom INI settings that might be
required for the proper operation of the upgraded software project. The Computer Setup
Editor tool is especially useful for comparing the old and new INI files. Select "Compare
INI Files" from the Computer Setup Editor > Tools menu.

7EN02-0462-03 Page 117 of 1312

Install and upgrade System Guide

When upgrading a standby server, first merge the standby server's existing .INI into the
upgraded version .INI. Then compare this result to the upgraded, merged .INI from the
primary server to confirm they are consistent; the two files should have consistent
[Alarm], [Trend], [Report] and driver parameters. Other parameters that include
<Server>, <Cluster> or <Device> names will have different parameter names but similar
values.

If you have defined the following parameters in your Citect.INI file, merge them into the
new version's INI file:

Parameter Description
Without this parameter, you will encounter the Tag not
[General] defined compiler error. Setting this to 1 allows you to
TagStartDigit=1 define tag names that begin with a number or a
symbol.
Without this parameter, you could encounter the 'Bad
Raw Data' or other tag address related errors. Setting
[General] this to 0 allows defining variable tags of the same data
CheckAddressBoundary=0 type in odd or even addresses. When this parameter is
set to 1 all variable tags from the same data type need
to be defined on odd OR even addresses.

[General] Without this parameter, compile will fail in a multi-

cluster system. Setting this parameter to 1 will enable
ClusterReplication=1 tag/tag reference replication in a multi-cluster system.
[CtDraw.RSC] This allows you to open popup pages from Graphics
ListSystemPage=1 Builder.

[CtDraw.RSC] This allows you to edit super genie pages from

AllowEditSuperGeniePage=1 Graphics Builder.

This allows you to set the maximum number of

[CtEdit] .DBF files that can open simultaneously. Allowable
values are between 50 to 32767 with the default set to
DbFiles=100 100. Increase the value of this parameter for larger
projects.

Merge any driver parameters from your old .INI file as they will most likely be necessary to
interface with your I/O network. For a list of changes to .INI parameters, see "Upgrade
references" on page 920.

10. Compile your project.

After upgrading your project and running the Migration tool, compile your project to ascertain
that runtime functionality works as expected. It is likely that you will encounter errors when
you compile your project. One of the most common sources of errors when upgrading is
Cicode functions. This is because functions changed, were deprecated, or because the
compiler code has been updated to prevent runtime errors.

Page 118 of 1312 7EN02-0462-03

System Guide Install and upgrade

After fixing any errors, do the following:

a. Use the Power Operation Studio > Options menu to deselect Incremental Compile.

b. Pack the project from Power Operation Studio > Projects screen.

c. Update Pages and Pack Libraries in the Active/Include projects from the Graphics
Builder.

d. Compile the project again.

11. Run the Setup Wizard.

Before running your project, run the Setup Wizard (known as Computer Setup Wizard in
previous versions) to configure the Runtime Manager and other settings that are relevant to
the runtime process. The Setup Wizard will automatically determine the role of your
computer based on the network addresses defined in your project. After finishing the Setup
Wizard, restore your historic data and other files, and run your project.

Be sure to enter the Server Password obtained or created before the upgrade on the Server
Authentication screen of the wizard. See Online upgrade for prerequsites.

12. Restore runtime files.

After compiling your project, place the files necessary for runtime in the correct directories.
Refer to step one in this topic for the list of files you need to place in the corresponding
directories as defined in your Citect.INI file and project configuration.

13. Restore historical data files (necessary if upgrading in the production environment).

Restore the historical data files before running your upgraded projects. It is not required to
restore these files when performing the Online upgrade or if upgrading the project in a test
environment. During an Online upgrade these files will be restored automatically through
Primary-Standby server synchronization.

NOTE: Consideration should be given to the size of the alarm and trend files. Automatic
Primary-Standby server synchronization can take a long time, depending on the size of
these files.

Alarms (v7.20 SR1 and earlier)

Before you can upgrade to Power Operation 2021, perform the following steps to convert
your <Project Name>_<Cluster Name>_ALMSAV.DAT and <Project Name>_<Cluster
Name>_ALMINDEXSAVE.DAT files to a format that can be read by the new alarm server
architecture introduced in v7.30:

Make sure that the [Alarm]SavePrimary parameter points to the directory in which you have
placed your backed-up ALMSAV.DAT and ALMINDEXSAVE.DAT

For Alarms in v2020, v2020 R2, v9.0, v7.30SR1, v7.40, v7.40 SR1, v8.0, v8.0 SR1 and v8.1,
convert your Alarm Database in the Data directory:
a. Confirm your backed-up Alarm Database is in the directory defined by the [CtEdit]Data
parameter.

b. Before starting runtime, confirm that the directory [Alarm]SavePrimary does NOT
contain ANY ALMSAV.DAT nor ALMINDEXSAVE.DAT files.

7EN02-0462-03 Page 119 of 1312

Install and upgrade System Guide

14. Follow these steps to convert the files:

a. Create the same file hierarchy on the new system.

b. Place the files in the same folders.

c. If you want to change the folder location, or you cannot replicate the same file hierarchy,
use the trend renaming tool available on the Schneider Electric Exchange.

15. Run your project.

Run your project to check that the functionality works as intended:

Check any Cicode that you needed to modify to compile your project.

Test communications to your I/O devices, alarm triggering, and trend capture.

16. Install Power Operation 2021.

After you have completed all the steps in your "Upgrade path" on page 113, install this
version and repeat steps 4 to 12.

17. Update settings in the Application Config Utility.

The authentication settings in the Citect Data Platform and settings of the One-Line Engine
screens need to be completed. Confirm that your redundancy parameters are set for the
one-line engine in a redundant system.

18. (Optional) Add Upgrade options in Upgrading to the project, recompile, and test.

Offline upgrade in test environment

Perform the offline upgrade to Power Operation 2021 R1 in a test environment before traveling to
the Production site. Complete the offline or online upgrades in the production environment.

Test environment activities:

• Use the Migration Tools for Citect and Power Operation to migrate the existing project
configuration to the next product version in the upgrade path and finally to the version you
want.
• Fix any compile errors and warnings that appear during project upgrade and migration.

• Validate the merge of the existing Citect.INI file into the upgraded version Citect.INI steps.

• Discovery of hard-to-find files listed in Offline Upgrade steps.

To perform the Offline Upgrade steps in a test environment:

1. Complete all steps of the Offline Upgrade:

a. In step 3 be sure to install Power Operation 2021 R1 and skip step 13. This action
upgrades the current version of the project directly.

b. Skip step 11. In this step, runtime data and historical data from the existing system are
restored, but it is only necessary to do this later when completing the offline or online
upgrade procedures in the production system (while located at the Production site).

The project should now be upgraded.

2. Address any project compile issues.

Page 120 of 1312 7EN02-0462-03

System Guide Install and upgrade

3. Test project functionality, verifying that key features of the solution function as expected.

4. (Optional) Add Upgrade options in Upgrading to the project, recompile and test.

5. Backup the upgraded 2021 project, upgraded include projects, sub-directories, and
configuration files.

NOTICE
LOSS OF DATA
Backup your project and other relevant historical data files from all servers in the system.

Failure to follow these instructions can result in a loss of data.

Migrating to production
Review the following information to complete the offline upgrade process and apply the changes
to your production system.

Testing Considerations
Perform system testing of the new project version after the upgrade and configuration changes to
the project are complete. This is to check that functionally and operation behaves as expected
before applying the new project to the production environment.

Server Addresses
During a migration with an existing system, use a new set of IP addresses and computer names
for the new version. This is typically done when there is a need to provide isolation between the
system project versions to allow the two systems to individually co-exist on the network for a
period of time. When isolated, the systems will be independent and not cross communicate or
synchronize between the existing and new versions. This type of upgrade would have the new
version start with a snapshot of the historical data from the previous system and then run in
parallel.

Communication Drivers
If the project is using specialty drivers, back up the driver files located in the product bin directory.
Existing specialty drivers that are used may be required to be installed for the new version. The
driver web can be checked for availability and compatibility with the new version at the DriverWeb.

Specialty Software
The project might be using specialty software to provide certain system functionality. These
applications might be required to be updated or re-installed during the upgrade process and
considered in the context of the upgrade.

Format File
The project may be using custom configuration forms in the product. This configuration is located
in the FRM file which may be required in the new installation.

7EN02-0462-03 Page 121 of 1312

Install and upgrade System Guide

Trend and Alarm Data

A project upgrade might also require the trend and alarm data to be updated based on the new
product features. It is recommended to keep a backup of the existing production trend data files
and the alarm save data file from the original.

Once the data files have been upgraded, the updated data files may not be compatible with the
previous version.

Do not change the directory path of the trend data files during the project upgrade as this may
affect the trend operation. The default data directory may be changed between product versions
and may need to be considered in the context of the install and upgrade with regards to the trend
file location.

Troubleshooting offline upgrade

This section lists common issues during an offline upgrade.

Go to the AVEVA Knowledge & Support Center website for information on PLANT SCADA.

Not able to upgrade license key

• Ensure the:
Latest versions of CiUSafe and Sentinel Driver were correctly installed.

Authorization code matches the Key you are trying to upgrade.

Compiler errors and warnings not related to deprecated functions

As Power Operation evolves, the compiler feature becomes stricter to ensure project quality and
runtime success. Getting compiling errors that were not appearing before is because of stricter
compilation, which will result in more predictable and stable runtime. Refer to the error code in the
error message to resolve any errors and warnings.

Online upgrade
Use this procedure to perform an online upgrade to Power Operation 2021 R1.

In an online upgrade, the two SCADA systems, the current and the new versions, are running
side-by-side. The current version is decommissioned after the new version has been fully tested
and validated.

If the offline upgrade was earlier performed in a test environment, the upgraded project will be
migrated to production during the online upgrade process as the final step in the Upgrade path
when Power Operation 2021 R1 is installed on production servers.

Go to the AVEVA Knowledge & Support Center website for information on PLANT SCADA.

Prerequisites
• Review Upgrading.

• Backup the alarm and trend database files from the standby server before synchronizing an
upgraded primary to the standby still running an older software version, in case any

Page 122 of 1312 7EN02-0462-03

System Guide Install and upgrade

unforeseen problems arise, and modifications are unintentionally made to the databases on
the standby server.

NOTICE
LOSS OF DATA
Backup your project and other relevant historical data files from all servers in the system.

Failure to follow these instructions can result in a loss of data.

• Project files that were upgraded in the test environment.

• At least one pair of redundant servers: This is to upgrade one server at the time while the
redundant server assumes primary operation, avoiding downtime and loss of data.
• Server Authentication Password: For the upgraded primary server to synchronize with the
standby server, the Server Password from the Server Authentication screen of the Computer
Setup Wizard must be known. If it is not known, it must be reset to a known password on both
servers using the Computer Setup Wizard before beginning the online upgrade process.
• Upgraded project: Check that your project runs and works on Power Operation 2021 before
migrating to production and starting the online upgrade. If your project is complex or if you are
upgrading from a version earlier than v7.20 SR1, it is recommended that you have a test
environment as the offline upgrade could be complex and could involve a long server
downtime if done on your production system.
• Restore runtime files: Check that you have restored the necessary files for runtime onto the
appropriate directories to avoid any disturbances on the upgraded live system.
• Capture data files: To allow historic data to be restored into the new version, you need to
assess and move data files to the required location during the upgrade process. This is
described in detail in the online upgrade steps in the relevant sections.
• Computer Setup Wizard Screens: It can be helpful to make screen capture images of the
Computer Setup Wizard screens from servers the existing system. This will help later in the
upgrade process if a mistake is made or if you would like to validate the settings when running
through the Computer Setup Wizard.
• Configure your running system for online upgrade: To allow this process to be as smooth as
possible, we recommend leveraging of your current redundant system and adding the
following Citect.INI parameters before the online upgrade.
[LAN] EarliestLegacyVersion: Use values for this parameter according to the table
below. For example, use 7200 for upgrades from v7.20, v7.20 SR1 and v7.30 SR1. This
will allow your upgraded servers to accept connections from the older version.

Product Version Earliest Legacy Version

7.20 7200

7.20 SR1 7200

7EN02-0462-03 Page 123 of 1312

Install and upgrade System Guide

Product Version Earliest Legacy Version

7.30 SR1 7300

7.40 7400

7.40 SR1 7400

8.0 7400

8.0 SR1 7500

8.1 7500

8.2 8000

9.0 8100

2020 8200

2020 R2 8210

[Alarm]EnableStateLogging: Set this parameter to 1 to allow logging the alarm

synchronization messages into the syslog.

[Alarm.<ClusterName>.<AlarmServerName>]ArchiveAfter: This parameter is

specific for an upgrade to v2015. If this parameter is not set to Citect 2015, the alarm
server will not start up. This is configured for each Alarm Server instance. When
configuring this parameter, you need to decide what time period of data you wish to
maintain during upgrade. For example, if you set this parameter to 1 week, it means that
during the upgrade process you will lose any summary data that is older than 1 week. If
you do not want to lose any data, you need to set this parameter to the earliest data in
your summary (v7.20) or SOE (v7.30 and v7.40)

(Optional) [Debug] Kernel = 1: Enable this to monitor the kernel during the upgrade.
• Disabled Alarms: If any alarms have been disabled in the project runtime, capture screen
shots of the Disabled Alarms page in the runtime. If there are problems with the Online
upgrade, it will be necessary to manually disable those alarms to put the system back in its
original state.
• Disabled IO Devices: If any IO devices have been disabled in the project runtime be sure to
double check the [DisableIO]<Device name> or [DisableIO]<Server name>
parameters to ensure the devices remain disabled after the upgrade.

Validate Hardware and Software Requirements for Power Operation 2021

Validate that the server hardware running the current Power Operation project on both the
primary and standby servers meets the Power Operation 2021 minimum requirements listed in
"Computer requirements" on page 56. The CPU and memory allocated to the machine should be
validated against the project design, that is the number of I/O Servers, tags per I/O Server, etc.

Page 124 of 1312 7EN02-0462-03

System Guide Install and upgrade

Upgrading from v2020 and v2020 R2

1. Check that you have the RTM version and the latest update installed.

2. Check that you have added the following parameters on the .INI file to all your server nodes
before you start the online upgrade:

v8.2: [LAN]EarliestLegacyVersion = 8200.

Restart the servers after adding the parameter for the changes to take effect.
3. Shutdown runtime on the primary server.

4. Upgrade Power Operation on this server according to the "Offline upgrade" on page 114.

5. Set up the Server Password in the Configurator, Power Operation, Computer Setup page.

6. Configure the System Management Server and encryption settings. The encryption settings
in version 2020 R2 need to be configured to align with the settings as they were in 2018 R2,
otherwise communications may not be successful.

7. Place the backed-up Alarm database in the [CtEdit]Data directory. This will allow a quicker
synchronization of alarm servers.

8. Restart the primary server.

9. Check the Server Authentication section of the Computer Setup page in Configurator,
under Power Operation. If you have selected Configure Server Password, make sure you
use the same password as the one defined in previous steps.

10. Shutdown runtime on the standby server.

11. When the newly upgraded version 2020 R2 server assumes the primary server role it will
migrate the entire alarm database to the new format, and you should now be able to see
Alarm Summary data on all migrated clients.

12. Upgrade Power Operation on this server according to the offline upgrade procedure.

13. Set up the Server Password in the Configurator, Power Operation, Computer Setup page.

14. Configure your System Management Server and encryption settings based on your
requirements.

15. Restart the standby server, which is now upgraded.

16. Check functionality of the system as a whole.

17. Test redundancy by switching off the primary server and checking that the standby takes
over and clients switch over.

18. On both servers, remove upgrade-related parameters that were set in prerequisites for an
Online upgrade and parameters noted in Troubleshooting online upgrade.

Upgrading from v8.1 and v8.0 SR1

1. Check that you have added the following parameters on the .INI file to all your server nodes
before you start the online upgrade:

7EN02-0462-03 Page 125 of 1312

Install and upgrade System Guide

[LAN]EarliestLegacyVersion = 7500.
2. Restart the servers after adding the parameter for the changes to take effect.

3. On the primary server:

a. Before stopping the primary runtime, validate dynamic one-line pages, device
communications, and Event Notification Module (ENM) operation, if installed

b. Shut down runtime on the primary server.

c. Validate one-line pages, device communications, and Event Notification operation on

the standby server. You should see a messages similar to this in the ENM diagnostics
tab (http://localhost:85) on the standby when it becomes active.

d. If the standby server has not assumed ENM operations the primary server will have to
be brought back online. You will have to troubleshoot the system redundancy.

4. Upgrade the primary server according to the "Offline upgrade" on page 114.

5. Configure the Server Password using the Computer Setup Wizard. For more information,
see Power SCADA Server password.

6. Configure the System Management Server. For more information, open the Power SCADA
Studio and click Display the Help to open the Plant SCADA help.

a. In the Plant SCADA help search box, type Configure a System Management Server
and click the search icon.

b. Follow the instructions for configuring the System Management Server.

Power Operation 2021 should not have encryption enabled with Accept encrypted and
non-encrypted not selected, otherwise the servers will not be able to communicate.
Mixed Mode should be used, or encryption should be disabled.

7. Place the backed-up Alarm database in the [CtEdit]Data directory. This will allow a quicker
synchronization of alarm servers.

8. Restart the primary server. It is now upgraded.

9. Check all functionality on the new Power Operation 2021 primary server:
Check the dynamic one-line operation, device communications, pop-up graphics, the
alarm log, and any other critical functionality. Validate that the ENM emails are being
sent through the ENM standby server (Diagnostics tab, Email Sent... messages). If
possible, validate the emails from other alarms.

10. Power Operation 2021 server will synchronize its alarm database with the running older
version standby server.

Wait for the synchronization process to finish. This will depend upon the size of your alarm
database. The synchronization information is available from the main kernel window of the
Alarm Process as well as the syslog.

Check the status of the alarm server synchronization using the Alarm Server Kernel, on the
main window:

Page 126 of 1312 7EN02-0462-03

System Guide Install and upgrade

When the Alarm Servers synchronization starts you should see the following message:
Alarm: Peer update request sent.

Then you should see a number of messages with update packets (number is dependent
on your Alarm historic events and configuration).
Alarm: Update packet XXXX received.

The following messages will indicate that the synchronization has been finalized
successfully:
Alarm: Database objects state synchronization completed.
Alarm: Database is initialized, preparing to Start the Alarm Engine.
Alarm: Starting Alarm Engine
Alarm: Server startup complete.

Trends from the Standby server will fill the time period the primary server was offline.
Monitor the kernel pages PAGE QUEUE TrnRdn.GapFillDelayQue and PAGE QUEUE
TrnRdn.GapFillSentQue. Wait for the queues to be empty before shutting down and
upgrading the standby server, if possible.
11. "Verify notifications" on page 145 functionality on the primary server.

12. The Power Operation 2021 server will synchronize its alarm database with the running
v2020 R2 server. You need to wait for the synchronization process to finish, and this will
depend on the size of your alarm database. The synchronization information is available
from the main kernel window of the Alarm Process as well as the syslog.

13. Upgrade your client nodes one by one. On each client complete the steps 1 through 3 and 7
of the "Offline upgrade" on page 114. In step two, only the citect.ini file is relevant for client
machines. When the newly upgraded v2016 server assumes the primary server role it will
migrate the entire alarm database to the new format, and you should now be able to see
Alarm Summary data on all migrated Clients.

Leave one client on the existing version of the software in case there is anything not
functioning properly in the new version. This helps to verify if anything was negatively
affected by the upgrade versus having been non-functional prior to the upgrade. Once both
servers have been upgraded, these clients will need to be upgraded as well.
14. Configure your System Management Server and encryption settings based on your
requirements.

15. Shut down the standby server and confirm operation of the new Power Operation 2021
primary server. Validate one-lines, device communications, and event notification operation
on the primary server.

16. When the newly upgraded version Power Operation 2021 server assumes the primary
server role, it will migrate the entire alarm database to the new format, and you should now
be able to see Alarm Summary data on all migrated clients.

17. Upgrade Power Operation on the standby server according to the "Offline upgrade" on page
114.

18. Set up the Server Password in the Computer Setup Wizard.

7EN02-0462-03 Page 127 of 1312

Install and upgrade System Guide

19. Configure your System Management Server and encryption settings based on your
requirements.

20. Now that the standby server is upgraded, restart it and check system functionality:
a. Check for hardware alarms when it is connected to the primary server.

b. Check dynamic one-line operation, device communications, popups, alarm log, etc.
Validate that the heartbeat notifications are being sent from the primary server's event
notifications system. If possible, validate emails from other alarms as well.

c. If there are issues with the advanced one-line displays, begin troubleshooting with the
AdvOneLineStatusLog, found in your project folder.

21. Restore and check event notifications on the Standby server:

On the Primary Server, open the event notification settings and save the settings.
Accept the prompt to automatically synchronize the configuration to the Standby Alarm
Server. See Creating Notifications.

"Verify notifications" on page 145

22. Check functionality of the system. Check the log files in the [Logs] folder on both servers.
There may be errors about deprecated parameters being used, invalid file paths, logins from
clients that weren't upgraded, untrusted connections (clients/servers with different Server
Passwords), or other errors.

23. Test redundancy by switching off the primary server and checking that the standby server
takes over Event Notification and Power SCADA clients all switch over.

24. On both servers remove upgrade-related parameters that were set in prerequisites for an
Online upgrade and parameters noted Troubleshooting online upgrade.

When doing an online upgrade from v8.0 SR1 or v8.1 to v2021 check that any pre-7.20 Alarm
Save files are removed from the v2021 project folders. For example, <project_cluster>_
ALMSAVE.DAT and <project_cluster>_ALMINDEXSAVE.DAT.

Upgrading from v7.30 SR1, v7.40, v7.40 SR1 and v8.0

1. Check that you have added the following parameters on the .INI file to all your server nodes
before you start the online upgrade:

2. Add the following parameter on the .INI file to all your server nodes before you start the
online upgrade.

For v7.30: [LAN]EarliestLegacyVersion = 7300.

For the other versions: [LAN]EarliestLegacyVersion = 7400.

3. Restart the servers after adding the parameter for the changes to take effect.

4. On the primary server:

a. Before stopping the primary runtime, validate dynamic one-line pages, device
communications, and Event Notification Module (ENM) operation if installed.

Page 128 of 1312 7EN02-0462-03

System Guide Install and upgrade

b. Shut down runtime on the primary server.

c. Validate one-line pages, device communications, and Event Notification operation on

the standby server. You should see a messages similar to this in the ENM diagnostics
tab (http://localhost:85) on the standby when it becomes active.

d. If the standby server has not assumed ENM operations the primary server will have to
be brought back online. You will have to troubleshoot the system redundancy.

5. Upgrade the primary server according to the "Offline upgrade" on page 114.

6. Place the backed-up Alarm database in the [CtEdit]Data directory. This will allow a quicker
synchronization of alarm servers.

7. Restart the primary server. It is now upgraded.

8. Check all functionality on the new Power Operation 2021.

Check the dynamic one-line operation, device communications, pop-up graphics, the
alarm log, and any other critical functionality. Validate that the ENM emails are being
sent through the ENM standby server (Diagnostics tab, "Email Sent..." messages). If
possible, validate the emails from other alarms.

9. Power Operation 2021 server will synchronize its alarm database with the running older
version standby server.

Wait for the synchronization process to finish; this will depend upon the size of your alarm
database. The synchronization information is available from the main kernel window of the
Alarm Process as well as the syslog.

Check the status of the alarm server synchronization using the Alarm Server Kernel, on the
Main Window:

When the Alarm Servers synchronization starts you should see the following message:
Alarm: Peer update request sent.

Then you should see a number of messages with Update packets (number is dependent
on your Alarm historic events and configuration).
Alarm: Update packet XXXX received.

Finally, the following messages will indicate that the synchronization has been finalized
successfully:
Alarm: Database objects state synchronization completed.
Alarm: Database is initialized, preparing to Start the Alarm Engine.
Alarm: Starting Alarm Engine.
Alarm: Server startup complete.

Trends from the Standby server will fill the time period the Primary server was offline.
Monitor the Kernel pages PAGE QUEUE TrnRdn.GapFillDelayQue and PAGE QUEUE
TrnRdn.GapFillSentQue. Wait for the queues to be empty before shutting down and
upgrading the standby server, if possible. Go to the AVEVA Knowledge & Support Center
website for information on PLANT SCADA.
10. Verify event notification functionality on the Primary Server.

7EN02-0462-03 Page 129 of 1312

Install and upgrade System Guide

11. Upgrade your client nodes one by one. On each client complete the steps 1 through 3 and 7
of the "Offline upgrade" on page 114. In step 2, only the citect.ini file is relevant for client
machines. When the newly upgraded v2021 server assumes the primary server role it will
migrate the entire alarm database to the new format, and you should now be able to see
Alarm Summary data on all migrated Clients.

It is helpful to leave one client on the existing version of the software in case there is
anything not functioning properly in the new version. This is also helpful in order to verify if
anything was negatively affected by the upgrade versus having been non-functional prior to
the upgrade. Once both servers have been upgraded, these clients will need to be upgraded
as well.
12. After you are confident that synchronization of alarms, trends etc., is complete, and that your
v2021 clients are working correctly, shut down the standby server and confirm operation of
the new Power Operation 2021 primary server. Verify correct operation of dynamic one-
lines, device communications, and event notification operation on the primary server.

13. Now that the standby server is upgraded, restart it and check system functionality:
a. Check for hardware alarms when it is connected to the primary server.

b. Check dynamic one-line operation, device communications, popups, alarm log, etc.
Validate that the heartbeat notifications are being sent from the primary server's event
notifications system. If possible, validate emails from other alarms as well.

c. If there are issues with the advanced one-line displays, begin troubleshooting with the
AdvOneLineStatusLog, found in your project folder.

14. Restore and check event notifications on the Standby server:

On the Primary Server, open the event notification settings and save the settings. Accept the
prompt to automatically synchronize the configuration to the Standby Alarm Server. See
Creating Notifications.

Verify event notification functionality on the Standby Server.

15. Check functionality of the system as a whole. It is a good idea to check the log files in the
[Logs] folder on both servers. There may be errors about deprecated parameters being
used, invalid file paths, logins from clients that weren't upgraded, untrusted connections
(clients/servers with different Server Passwords), or other errors.

16. Finally, test redundancy by switching off the primary server and checking that the standby
server takes over Event Notification and Power SCADA clients all switch over.

17. On both servers remove upgrade-related parameters that were set in prerequisites for an
Online upgrade and parameters noted Troubleshooting online upgrade.

Special Considerations
Alarm Summary

The 2021 Summary feature will be disabled when connecting to a v7.30 server. You may still see
summary records for active alarms.

Alarm Save Files

Page 130 of 1312 7EN02-0462-03

System Guide Install and upgrade

When doing an online upgrade from v7.30 to 2021 check that any pre-7.20 Alarm Save files are
removed from the 2021 project folders (e.g. <project_cluster>_ALMSAVE.DAT and <project_
cluster>_ALMINDEXSAVE.DAT)

Historical Alarm Events

Set the [Alarm.<Cluster Name>.<Server Name>]ArchiveAfter .INI parameter to a date prior to the
earliest historical event date from which you want to migrate.

Upgrading from v7.20 and v7.20 SR1

When upgrading from v7.20, you will NOT need to restore the alarm data files (ALARMSAV.DAT
and ALRMSAVEINDEX.DAT) under most circumstances. Power Operation 2021 is equipped to
read this information from the redundant v7.20 SR1 server that is still not upgraded.

To upgrade from v7.20 or 7.20 SR1:

1. Add the following parameter on the .INI file to all your server nodes before you start the
online upgrade.

[LAN]EarliestLegacyVersion = 7200.
2. Restart the servers after adding the parameter for the changes to take effect.

3. On the primary server:

a. Before stopping the primary runtime, validate dynamic one-line pages, device
communications, and Event Notification Module (ENM) operation if installed.

b. Shut down runtime on the primary server.

c. Validate one-line pages, device communications, and Event Notification operation on

the standby server. You should see a messages similar to this in the ENM diagnostics
tab (http://localhost:85) on the standby when it becomes active.

d. If the standby server has not assumed ENM operations the primary server will have to
be brought back online. You will have to troubleshoot the system redundancy.

4. Upgrade the primary server according to the "Offline upgrade" on page 114.

5. Restart the primary server. It is now upgraded.

6. Check all functionality on the new Power Operation 2021 primary server:
Check the dynamic one-line operation, device communications, pop-up graphics, the
alarm log, and any other critical functionality. Validate that the ENM emails are being
sent through the ENM standby server (Diagnostics tab, "Email Sent..." messages). If
possible, validate the emails from other alarms.

7. Now, the Power Operation 2021 server will build the new alarm database, and will import the
historic data from the Standby v7.20 server.
Trends from the Standby server will fill the time period the Primary server was offline.
Monitor the Kernel pages PAGE QUEUE TrnRdn.GapFillDelayQue and PAGE
QUEUE TrnRdn.GapFillSentQue. Wait for the queues to be empty before shutting
down and upgrading the standby server, if possible. go to the AVEVA Knowledge &
Support Center website for information on PLANT SCADA.

7EN02-0462-03 Page 131 of 1312

Install and upgrade System Guide

8. Check the status of the alarm server synchronization using the Alarm Server Kernel, on the
Main Window:
When the Alarm Servers synchronization starts you should see the following message:
Alarm: Peer update request sent.

Then you should see a number of messages with Update packets (number is dependent
on your Alarm historic events and configuration).
Alarm: Update packet XXXX received.

Finally, the following messages will indicate that the synchronization has been finalized
successfully:
Alarm: Database objects state synchronization completed.
Alarm: Database is initialized, preparing to Start the Alarm Engine.
Alarm: Starting Alarm Engine.
Alarm: Server startup complete.

9. If you find that your Alarm Server synchronization is not completing successfully, place the
ALARMSAV.DAT and ALRMSAVEINDEX.DAT on the [Alarm]SavePrimary directory.

10. Upgrade ENM to version 8.3.3 - Uninstall the current version of ENM through the Control
Panel > Programs and Features. Install ENM 8.3.3 by running the install executable.

11. On the newly-upgraded primary server, migrate the ENM configuration to Power Operation
notifications. See Migrating notifications for more information.

12. Decommission ENM on the Primary server by uninstalling ENM 8.3.3 through the Control
Panel > Programs and Features. Stop and uninstall SQL Server if it is no longer needed by
other applications.

13. Verify event notification functionality on the Primary Server.

14. Upgrade your client nodes one by one. On each client complete the steps 1 through 3 of the
"Offline upgrade" on page 114. In step 2, only the citect.ini file is relevant for client machines.

It is helpful to leave one client on the existing version of the software in case there is
anything not functioning properly in the new version. This is also helpful in order to verify if
anything was negatively affected by the upgrade versus having been non-functional prior to
the upgrade. Once both servers have been upgraded, these clients will need to be upgraded
as well.
15. After you are confident that synchronization of alarms, trends etc., is complete, and that your
v2021 clients are working correctly, shut down the standby server and confirm operation of
the new Power Operation 2021 primary server. Verify correct operation of dynamic one-
lines, device communications, and event notification operation on the primary server.

16. Now that the standby server is upgraded, restart it and check system functionality:
a. Check for hardware alarms when it is connected to the primary server.

b. Check dynamic one-line operation, device communications, popups, alarm log, etc.
Validate that the heartbeat notifications are being sent from the primary server's event
notifications system. If possible, validate emails from other alarms as well.

c. If there are issues with the advanced one-line displays, begin troubleshooting with the
AdvOneLineStatusLog, found in your project folder.

Page 132 of 1312 7EN02-0462-03

System Guide Install and upgrade

17. Restore and check event notifications on the Standby server:

On the Primary Server, open the event notification settings and save the settings. Accept the
prompt to automatically synchronize the configuration to the Standby Alarm Server. See
Creating Notifications.

Verify event notification functionality on the Standby Server.

18. Check functionality of the system as a whole. It is a good idea to check the log files in the
[Logs] folder on both servers. There may be errors about deprecated parameters being
used, invalid file paths, logins from clients that weren't upgraded, untrusted connections
(clients/servers with different Server Passwords), or other errors.

19. Finally, test redundancy by switching off the primary server and checking that the standby
server takes over Event Notification and Power SCADA clients all switch over.

20. On both servers remove upgrade-related parameters that were set in prerequisites for an
Online upgrade and parameters noted in Troubleshooting > Remove Upgrade Parameters.

Special Considerations

Custom Alarm Filtering

The AlarmSetQuery Cicode function was deprecated in v7.30. This means that if you are using
custom alarm filtering code, you will most likely need to convert it.

Historical Alarm Events

Set the [Alarm.<Cluster Name>.<Server Name>]ArchiveAfter.INI parameter to a date prior to the

earliest historical event date from which you want to migrate.

Alarm server synchronization during online upgrade

In the event that there is a disconnection or timeout during synchronization between the v2021
and v7.20 alarm servers, follow these steps:

1. Shutdown your 2021 server.

2. Delete the alarm database and re-start it.

3. Wait for the synchronization between servers to finish.

Also, you can increase the timeout using the [Alarm]StartTimeout .INI parameter. This will allow
the 2021 server to wait for connection from the v7.20 server.

If you find that the synchronization between the two servers is experiencing interruptions, delete
the alarm database, and place your ALARMSAV.DAT and ALARMSAVINDEX.DAT in the
[Alarm]SavePrimary directory and the 2021 server will convert the data. However, we recommend
always trying the peer synchronization first.

Changes during the upgrade process

Because of the differences between Power Operation 2021 and v7.20, any actions that happen
during the online upgrade process are subject to incompatibilities that are not reconcilable
between versions. However, the scenarios are quite particular and should not have a great
impact, if any, on your SCADA system. Here is a list of such scenarios:

7EN02-0462-03 Page 133 of 1312

Install and upgrade System Guide

• UserLocation field: In Power Operation 2021, a record of the UserLocation, that is the
IP address, for alarm operations such as acknowledge is available. If an acknowledge occurs
on the v7.20 server during the upgrade, the 2021 server will be unable to record the
UserLocation, which will be displayed as "0.0.0.0".
• Summary Comments during the upgrade: Comments that you add to an alarm summary
record on the v7.20 server during the online upgrade will not be available in the upgraded
version.

Troubleshooting online upgrade

This section lists common issues you could encounter during an online upgrade.

Redundant servers fail to communicate

I cannot make my redundant servers communicate and I keep getting the hardware alarm
“Redundant Server not found”.

1. Check the [LAN]EarliestLegacyVersion parameter value.

If upgrading from v7.20 use [LAN]EarliestLegacyVersion=7200.

If upgrading v8.0SR1 or v8.1 use [LAN]EarliestLegacyVersion=7500.

If upgrading v8.2 use [LAN]EarliestLegacyVersion=8000.

Run the Setup Wizard and set both servers to Networked mode.

2. Set the same server password on both servers in the Setup Wizard (see Configure Server
Password in installed help).

System is performing slowly even though hardware and software requirements

are met
Check your system’s power options: Control Panel > Hardware and Sound > Power Options >
Create a Power Plan > select High performance.

Remove Upgrade related parameters

After completing the upgrade process and confirming that runtime is fully functional, remove or
update the following .INI parameters.

NOTE: You will need to restart the servers after changing the parameters for the changes to take
effect.

• [Alarm]SavePrimary: remove this parameter.

• [Alarm]SaveStandby: remove this parameter.

• [Debug]Kernel = 0: this is to enhance security and keep operators out of the kernel.

• [LAN]EarliestLegacyVersion: remove this parameter.

Page 134 of 1312 7EN02-0462-03

System Guide Install and upgrade

The next time a user's passwords is changed after removing the EarliestLegacyVersion
parameter, change all the passwords on one server and then roll out the updated project in the
same order in which you conducted the online upgrade (primary server, clients, and then standby
server).

Migration Tools
The automatic update that occurs when you initially open Power Operation 2021 does not fully
upgrade your projects, and needs to be followed by using the Migration Tools. If you are migrating
from v7.x, this is particularly noteworthy. The automatic update is a passive action which updates
the database field definition for any database that has been changed between the two versions
and copies new files that are necessary in 2021.

There are two main migration tools: one for Plant SCADA and one for Power Operation. Both
must be run manually after the automatic upgrade has been executed. You can do this after you
have prepared the project for final migration.

WARNING
UPGRADE ALTERS COMMUNICATIONS CONFIGURATIONS
After upgrading, confirm and adjust the configuration of I/O devices in your project.

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

Using the Power Operation Migration Utility

The Migration Utility lets you migrate previous versions of Power Operation to the current version.
You only need to run this utility one time. Before you run the migration utility, back up your system.

To migrate your project:

7EN02-0462-03 Page 135 of 1312

Install and upgrade System Guide

1. Open the Power Operation Migration Tool: In Power Operation Studio > click Projects

2. Click the Migration Tool drop-down and then click Power Operation Migration Tool.

3. From the Master.dbf Location, choose the location for the Master.dbf.

4. From Select Project, choose the project that you are migrating.

5. Select the check boxes you want. See the Power Operation Migration Utility Options table
for details.

6. Click Migrate.

7. Verify the project backed up.

8. Click Yes.

9. If there is already a PageMenu.dbf file that is creating a menu for your graphics pages, you
see a message telling you that the PageMenu.dbf is not empty. Click Yes to override this
file, which overwrites the menu, leaving it blank. Click No to retain the menu for version
2021.

When the migration is complete, a summary screen lists the results of the
migration, including updates and errors.

10. In Power Operation Studio Projects activity, click Pack and then click Compile.

11. After you install Plant SCADA, you need to:

a. Back up the project.

b. Uninstall (if you are using the same computer to reinstall).

Page 136 of 1312 7EN02-0462-03

System Guide Install and upgrade

c. Install the new version.

d. Add the one-line device.

e. Run the Advanced One-Line tool.

12. If you are going to upgrade to a later version, you need to:
a. Back up your project.

b. Uninstall Plant SCADA.

c. Install the new version.

d. Restore your project.

Power Operation Migration Utility Options

The items with asterisks will be updated in the Equipment.profiles file at every migration.
When you select an item with an asterisk, it will also update the Profile so that future information
added to it will be coordinated with the current version. For example, if you run the migration and
check Update Variable Tag Names, future variable tags will be correctly formatted for the current
version.

If after migration you want to use the Equipment tab in the Graphics Editor, you must select a
device profile Type in the Add/Edit Device Profile screen. For more information, see the Add,
edit, or delete device profile section.

Element Description Behavior

Power Operation v2021 R1
TGML Upgrade Use this tool to update restored
Utility TGML files to the latest version.
Power Operation v9.0 and earlier
Update item Adds item names to variable tags to
Updates all item names.
names work with Web Applications.
Power Operation v8.2 and earlier
This causes the default Allow
Allow RPC for all Allows performing remote MsgRPC
RPC value (FALSE) to be changed
servers and ServerRPC calls.
to TRUE.
Set Alarm This setting is required for
Extended memory on Alarm servers.
servers to 64-bit Notifications.
Power Operation v8.0 and earlier
Updates I/O descriptive names that
Update Digital Updates all DIGITAL tags in
were renamed to the latest standard
Tag Format Variable.dbf to FORMAT ##.
name.
Power Operation v7.40 and earlier
Update Rack Updates the tag addresses of Corrects the tag addresses of
Status Micrologic rack status tags. Micrologic rack status tags.

7EN02-0462-03 Page 137 of 1312

Install and upgrade System Guide

Element Description Behavior

Update variable Updates edited tag names to Updates tag names to the latest
tag names standard tag names. standard name.
Power Operation v7.30 and earlier
This causes digital tags in Power
Update Digital Update all DIGITAL tags in
Operation to display without
Tag Format Variable.dbf to FORMAT ##.
decimals: 1 or 0, but not 1.000.
Check this box to rename all new
Update Alarm
Renames all existing tags to the new convention names. For example, the
and Variable Tag
convention names. old Sepam Not Reset is now Generic
Names
Not Reset.
Power Operation v7.20 and earlier
TagPrefix field added. It is now used
to build tags.

Equipment Name is the equipment If the TagPrefix field is empty,

Populate Tag IODevice name is used to populate
hierarchy name (can no longer be
Prefix-Equip.dbf Tag Prefix. If IODevice name is also
used to build tag names).
empty (in a composite device),
EquipmentName is used IF there are
no periods in the name.
The Parent field (previously used to The Composite field replaces the
Populate
determine the parent piece of Parent field. The Composite field will
Composite Field
equipment) has been removed from display the Parent field information, if
- Equip.dbf
the .dbf file. applicable.
The Cicode function StrToLocal no
longer allows partially translated
text. For example, in @ All custom fields in alarm tags will
(Protection),2, "Protection" must be remove the ID part (1-8) of the field,
Fix Metadata
translated. IF the translation identifier is present.
ID Compiler
Thus, in @(Protection), 2 the "2" is
Warnings Also, 2 is the metadata ID; in all removed; it will be changed to @
custom fields (1-8) of all alarm tags, (Protection).
the ID part of the field must be
removed.
Other
Update
Reference When selected, this updates all Cascades changes to custom
Component graphics components to the latest components to all Pages in the
Definitions check version used in Projects. Project.
box

Page 138 of 1312 7EN02-0462-03

System Guide Install and upgrade

Using the Plant SCADA Migration Tool

NOTE: Before you use the Plant SCADA Migration Tool, familiarize yourself with the process it
performs, and the preparatory steps you need to carry out with your existing projects.

To run the Plant SCADA Migration Tool:

1. Backup the projects that you need to migrate.

2. In Power Operation Studio, click Project, select Home > Migration Tool to display the
Citect Migration Tool dialog.

3. Either accept the project displayed in the edit box, or browse for the project that you wish to
upgrade.

4. Specify the changes you would like to implement during the migration process by selecting
from the options described in the following table.

7EN02-0462-03 Page 139 of 1312

Install and upgrade System Guide

Option Description
Select this check box if you wish to delete these types of
devices after successful migration (see "Remove obsolete
memory and alarm devices" on page 142).

Remove obsolete NOTE: Do not select this check box when you run the tool for
Memory and Alarm the first time on a project that contains any included projects
devices which are shared with more than one primary project. If you
want to delete obsolete devices under these circumstances,
you can run the tool a second time using this option if the
migration is successful after it is run the first time.

Use this option to append information about the migration

process to the existing Migration Tool log file (located in Power
Append to existing log file
Operation's User directory). If this option is not selected, a
new log file will be created when migration is complete.
Select this option if you want to migrate the user database
Create roles from User
from an existing project (see "Creation of roles for existing
security information
users" on page 144).
Select this option to convert legacy menu entries to the format
necessary for the new menu configuration system. By default,
Copy XP_Style menu
this option is unchecked to avoid potential compile errors that
into Tab_Style menu
may occur if the legacy menu.dbf contains functions which
have been removed.
Select this option to migrate the included projects associated
Migrate included projects with the selected project (see "Migrate included projects" on
page 144).
Select this option if you have an existing database that you
want to migrate into this version. When upgrading from an
earlier version, and the "PARENT" field of the equipment table
was used, you should select this check box. Otherwise
Migrate equipment existing data from the PARENT field will be ignored. If runtime
database browsing is used, the PARENT field will return the equipment
parent (the substring of the equipment name without the last '.'
and anything after that).

To retrieve information that was stored in the previous

"PARENT" field the "COMPOSITE" field should be used.

Page 140 of 1312 7EN02-0462-03

System Guide Install and upgrade

Option Description
Select this option if you want to migrate devices that currently
use the ABCLX driver to the OPCLX driver. Select the
Configure button to indicate which I/O devices you would like
Migrate ABCLX to
to migrate.
OPCLX
NOTE: You should confirm that the OPCLX driver is installed
before you use this option.

If you select this option, the storage method will be set to

scaled (2-byte samples) for all trends that have no storage
method defined. Use this option to stop the compiler error
Migrate Trend/SPC
message "The Storage Method is not defined". In previous
storage method
versions, a blank storage method would default to scaled.
However, this is no longer supported, resulting in the compile
error message.
If you select this option, computers will be created from the
Create computers from servers and network addresses that you have configured for a
Network Addresses project and its include projects. This option distinguishes
whether a computer has multiple IP addresses.

NOTE: If 'Copy XP Style menu into Tab_Style Menu' and 'Migrate Included Projects' are
both selected when the migration tool runs, the following message will be displayed:
"Copying menus of included projects may lead to conflicts. Any conflicts will need to be
manually corrected". To avoid this from occurring, it is recommended you run the migration
tool twice. In the first instance just select the option 'Copy XP_Style menu into Tab_Style
Menu', and in the second instance just select the option 'Migrate Included Projects'.

5. Click Migrate to begin the migration process.

A progress dialog will display indicating the stage of the conversion and the name of the
project being migrated. If you wish to cancel the migration at this point click the Abort
button.

NOTE: Aborting a migration will stop the migration process, and any changes already
completed will not be rolled back. You will have to restore your project from the backup
created in the first step.

When the migration is complete, an information window displays information indicating the
number of variables converted and the number of I/O devices deleted (if device deletion was
selected at the start of migration), and where the resulting log file is stored.
6. Click the Close button to close the dialog.

TGML Upgrade Utility

Use this tool to update restored TGML files. It is only required when upgrading to Power
Operation 2021 R1.

7EN02-0462-03 Page 141 of 1312

Install and upgrade System Guide

1. Open the Power Operation folder.

2. Open the TGML Upgrade Utility program.

3. Enter a location for Path to .tgml and .tgmlcomponent files. This is the location of TGML
files and components.

4. Click Upgrade.

Remove obsolete memory and alarm devices

When you use Power Operation Migration Tool, the Remove obsolete Memory and Alarm
devices option adjusts the following:

Memory tags to local variables: tags that are on an I/O device that are configured to use a
'memory' port.

NOTE: If there are real I/O devices in your project that have been set to use a 'memory' port
during testing, these can be changed before running the migration tool to avoid those tags
getting adjusted.

Alarm devices: can remove I/O devices that have a protocol set to 'Alarm', which was needed in
earlier versions to enable alarm properties as tags. In version 7.x, the alarm properties are
enabled via a setting on the alarm server configuration form.

Memory devices
In previous versions of Power Operation, an I/O Device could be defined as a memory device by
setting the port value to "Memory". This was generally done for one of the following purposes:
• To provide for future devices that were not currently connected to the system, but their points
needed to be configured at this stage of project.
• For virtual devices where there was no corresponding physical I/O Device and you needed
data storage with the entire functionality normally associated with I/O variables, such as
alarms.
• To act as a variable which was local to the process being used in place of Cicode global
variables.

You can still use I/O Devices for future or virtual devices in version 7.0, but manually set the Port
parameter to an unused value other than Memory, and set the Memory property of the device to
True to indicate that it is an offline in-memory device before running the Migration Tool.

You need to review your project to identify which memory I/O Devices are local variable holders
and which ones need to be changed to non-memory so that the Migration tool does not convert
their variables.

The Migration Tool will set any I/O Device's port that is identified as a Memory device to the new
Local Variable, and the original device record will be deleted

Alarm devices
In previous versions of Power Operation, Alarm devices were defined as devices with their
Protocol property set to "Alarm". In version 7.0 the function of configuring such a device is now
replaced by setting the Publish Alarm Properties property to True on the Alarm Server.

Page 142 of 1312 7EN02-0462-03

System Guide Install and upgrade

Alarm devices with their Protocol property set to "Alarm" will be deleted from I/O Devices table by
the Migration Tool.

The Migration tool can delete memory and alarm device records. If you want to delete the devices
later, deselect the "Remove obsolete Memory and Alarm Devices" option.

NOTE: Alarm devices with their Protocol property set to "Alarm" are no longer used and will be
removed by the Migration Tool. All Alarm Servers will now publish Alarm Properties.

Converting memory variables

A memory variable is a variable with its I/O Device Port property set to either "Memory" or "MEM_
PLC".

If there are multiple I/O Devices with the same name, possibly on different I/O Servers, the device
would not be considered as a memory device regardless of its port value. In other words, the
Migration tool will not process the variables for memory devices with duplicate names.

Inserting new local variables

When the Migration Tool runs, a local variable record will be inserted for each identified memory
variable, and the variable data will be copied into the new local variable.

Local variables have fewer fields than variables; the following table shows the mapping from
variable to local variable when copying their data.

Variable Tag Parameter

Local Variable Parameter
or Constant Value
Variable Tag name Name
Data Type Date Type
(Empty) Array Size
Eng. Zero Scale Zero Scale
Eng. Full Scale Full Scale
Comment Comment

Except for the Array Size, which was introduced in version 7.0 exclusively for local variables,
every field receives its value from the same or similar field.

Deleting variable tags

Once the Migration Tool has created the local variable records it will insert those variable tag
records that have been converted in the previous step, and delete the original variable tag.

If an error is detected during the insertion of the local variables, the deletion of the variable tags
will not be performed. If this occurs it is possible to have two records with same name and data,
one in the local variable (the newly inserted record) and one in the variable tags (the original
record that has not been deleted). You need to delete either of the variables manually, or restore
the backed-up project after removing the cause of the error then run the Migration Tool again.

7EN02-0462-03 Page 143 of 1312

Install and upgrade System Guide

Deleting obsolete I/O devices

Deleting obsolete I/O Devices is an optional step in the Migration Tool and will be performed after
the memory variables are converted. If the delete option is chosen, obsolete Memory devices and
Alarm devices will be deleted as the final step of the Migration Tool operation.

Creation of roles for existing users

When upgrading an existing project using the Migration Tool, a new role will be created (if
needed) for every existing user. The new role will have the same security settings that were
defined for that user and be given a generic name such as Role_1, Role_2 etc. During the
upgrade process, if a role exists with the same security settings as the user, then the existing role
will be assigned to the user being upgraded. For example; If Role_1 exists and matches the
security settings of the upgraded user then that user will be assigned Role_1 also.

If you do not want to migrate users from an existing project, clear the option Create Roles from
User security information from the migration tool dialog before running it.

Migrate included projects

Each project may contain multiple included projects. Additionally, any included project may
contain its own included project, creating a cascading project.

The Migration Tool needs to process the original project and included projects in a single step.
The reason for this is that variables can be defined in one project that refer to I/O Devices defined
in another included project.

The Migration Tool performs this procedure sequentially on the "primary" project then each
included project.

In the case where two primary projects share the same project as an included project, you should
not click Remove obsolete Memory and Alarm devices when you process a project that
contains shared included projects. This is because the removal is performed after the migration
process on each primary and included projects sequentially. This could cause the deletion of an
I/O Device in the first primary project which is referenced by a tag in a shared included project
which is processed in a later step.

If two separate "primary" projects contain the same included project, run the Migration Tool on
each "primary" project without selecting to delete obsolete devices.

WARNING
UPGRADE ALTERS COMMUNICATIONS CONFIGURATIONS
After upgrading, confirm and adjust the configuration of I/O devices in your project.

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

Page 144 of 1312 7EN02-0462-03

System Guide Install and upgrade

To remove obsolete devices, it is recommended that once the Migration Tool has completed
successfully (without the check box being selected), run it a second time with the check box
selected. This will safely remove the devices since every tag conversion were completed in the
first pass of the Migration Tool.

Default scale
The Scale properties in both variable tags and local variables are optional. If a Scale value is not
specified, the default value is indicated by a parameter in the Citect.ini file. The parameter name is
"DefaultSliderScale" under the [General] section in the Citect.ini file. The default values for Scale
is 0-32000, unless the default slider scale is true in which case the default value depends on the
type, for example, Integer, String, or so on.

The Migration Tool will read this parameter and if it is not set, or set to false, then it will explicitly
set any empty Scale property to a value in to the range of 0 to 32000. This will be done even if
either of the Zero Scale or Full-Scale parameters have a value, in which case the empty Scale
parameter will receive the default value.

If the DefaultSliderScale in the Citect.ini file set to True, the Scale parameters will not be
populated with a default value if they are empty, rather they will be interpreted at runtime.

Verify notifications
On a newly installed Power Operation server:

1. Create, compile, and run a simple project.

2. Open the Notification Settings. See Creating Notifications.

3. Add at least one recipient.

4. Add the settings for at least one delivery method. See Configure SMS Text Notification or
Configure the Email Server.

5. Use the Test button to send a test message to the recipient. See Enable and Test Delivery.

Migrating from Plant SCADA (formerly Citect SCADA)

NOTICE
LOSS OF DATA
Backup your project and other relevant historical data files from all servers in the system.

Failure to follow these instructions can result in a loss of data.

Before the introduction of Power Operation, some customers used Citect SCADA for power
management edge control applications. Customers using pre-7.x versions of Citect SCADA can
migrate their systems to Power Operation to take advantage of the power management features
unique to Power Operation.

7EN02-0462-03 Page 145 of 1312

Install and upgrade System Guide

Power Operation is built on Power Operation Studio and includes productivity tools that are
designed and optimized to create the tags you need to configure power-based SCADA projects. It
is important to use these productivity tools when migrating a pre-7.x Citect SCADA system to
Power Operation.

The following Power Operation features are only supported using Power Operation productivity
tools and workflows:
• PwrModbus driver

• Profile Editor and I/O Device Manager

• Advanced One-line Configuration

• Waveforms (Comtrade)

• Built-in Notifications

• Power Diagnostics tools (PSO 9.0)

• Basic Reports

• Advanced Reporting and Dashboards Module

• Interoperability with EcoStruxure Building Operation

• LiveView

• Power Operation Power Graphic Libraries

• Support for 2-factor authentication and Single-Sign-On with Advanced Reporting and
Dashboards Module
• Historical data from Power Operation to Advanced Reporting and Dashboards Module
database via ETL (Extract, Transform, Load) tool
• Thermal Monitoring Application

For instructions on migrating from Plant SCADA, see "Plant SCADA Migration Information" on
page 967.

Backing up and restoring a Power Operation system

A Power Operation system can be backed up and then restored if the original Power Operation
system is no longer available.

The procedures outlined in this document describe how to backup and restore standalone and
redundant Power Operation systems, and include Power Monitoring Expert (Advanced Reporting
and Dashboards).

NOTE: This procedure does not support distributed PME systems.

The Power Operation system components and modules you will need to back up will vary,
depending on your system architecture and whether your system is redundant.

NOTE: When backing up and restoring a project, ensure that "Include Subdirectories" is
checked so that your graphics and advanced one-line configuration is included.

Page 146 of 1312 7EN02-0462-03

System Guide Install and upgrade

Backing up a Power Operation system

This section includes the tasks required to create automated backups of a Power Operation
system. It also lists the installation media you need to back up, and the steps you should complete
to prepare for the backup process.

NOTE: Some procedures in this section cite scripts you can use to automate the backup and
restore process. Refer to www.se.com or the Schneider Electric Exchange for the backup and
restore scripts specific to your Power Operation system version.

Before you begin

Before you backup or restore a Power Operation system, review the steps below to prepare for
the processes.

Installation media and license backup

Back up the following installation media and license files at least one time:
• Power Operation installation media (the ISO file used for installation).

• Power Operation License Activation IDs if using software licenses.

• If Power Monitoring Expert (PME) is present on your system:

PME installation media

PME License Activation IDs

PME Custom Report Pack install files

Backup directory location

Create a directory structure in a secure location on your network that can be accessed if you can
no longer access the original Power Operation system. This backup directory location will contain
all the backup files required to restore your system. It must be accessible and have relevant
permissions for the Administrator account to create the backup files.

System passwords
You will need to access system passwords to recover your Power Operation system. However, it
is beyond the scope of this document to provide guidance on how you should manage your
passwords for backup situations. If you are uncertain how you should back up passwords, consult
your IT Department.

Backing up Power SCADA

You can automate backing up Power Operation to include most of the components that will be
required to restore a system. Because Power Operation passwords cannot be automatically
backed up, you must back them up manually.

.NET 4.5.2 and WMF 5.1 are required to run the provided scripts. WMF 5.1 is available as an
offline windows update installer.

1. Run PowerShell and enter the following command to determine what version of WMF is
installed before proceeding:
$PSVersionTable.PSVersion

7EN02-0462-03 Page 147 of 1312

Install and upgrade System Guide

2. Verify PS Version is 5.1 or greater. If an older version is detected, see the below table for
updating to the required version. The WMF installation is available as an offline windows
update (.msu) and will require a reboot after installation.

Download the WMF 5.1 package for the operating system and architecture on which you want to
install it:

Operating System Package Link

Windows Server 2019 Built-in
Windows Server 2016 Built-in
Windows Server 2012 R2 Win8.1AndW2K12R2- KB3191564-x64.msu
Windows Server 2012 W2K12-KB3191565- x64.msu

Backing up Power Operation automatically

To automate the Power Operation backup process, you can run the script to copy the required
Power Operation project folders to the backup directory location. You can also create a scheduled
task to run the script. Go to www.se.com or the Schneider Electric Exchange for more information.
for the backup script specific to your Power Operation system version.

NOTE: The automated Power Operation backup does not include every Power Operation
component that needs to be backed up. The server password key must be manually backed up.
After you complete the automated Power Operation back up, see Backing up the Power
Operation Passwords and Device Profiles for details.

After you automatically back up your Power Operation system, periodically check the backup
directory drive to make sure there is sufficient space for the copied backups. See Deleting Old
Backups to automate your system to delete old backups.

To automate the Power Operation backup process:

1. In a text editor, open the PSEvx.x_Backup.ps1 script for your version.

2. Edit the file for your system:

a. For <$destinationDir>, enter your backup directory location.

b. If you did not install Power Operation to the default install location, edit the <$pseBin>
and <$pseData> to reflect the installed location path.

3. Save the file as PSE_Backup.ps1 in the following location:

C:\Program Files (x86)\Schneider Electric\BackupTasks

4. Run PowerShell as Administrator and set the execution policy with the following cmdlet:
Set-ExecutionPolicy Bypass.

5. Open Windows Task Scheduler and create a new task under Schneider Electric with a
trigger to run once a week at midnight.

6. Define the new action:

a. For Action, click Start a program.

b. In Program/script, enter the following:

C:\Windows\syswow64\WindowsPowerShell\v1.0\powershell.exe

Page 148 of 1312 7EN02-0462-03

System Guide Install and upgrade

c. In Add arguments, enter the following:

-noninteractive -nologo -file " C:\Program Files (x86)\Schneider
Electric\BackupTasks\PSEv8.1_Backup.ps1"

NOTE: Run the scheduled task to confirm that it copied the components to your backup location.
This will also help you verify that you can access the backup location.

Backing up the Power Operation passwords and device profiles

Because Power Operation passwords and device profiles cannot be automatically backed up, you
must back them up manually.

NOTE: The encrypted file that stores this password cannot be transferred from one machine to
another, so it is very important that you store this password somewhere secure where it can be
retrieved.

Power Operation Server password

WARNING
POTENTIAL COMPROMISE OF SYSTEM AVAILABILITY, INTEGRITY, AND
CONFIDENTIALITY
Use cybersecurity best practices for password creation and management.

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

Cybersecurity policies that govern passwords vary from site to site. Work with the facility IT
System Administrator to ensure that password management adheres to the site-specific cyber
security policies.

To back up the Power Operation Server password:

1. Open the Citect Computer Setup Wizard.

A. Power Operation 2021, Power SCADA Operation 2020, Power SCADA Operation
9.0, or PowerSCADA Expert 8.2:
In Power Operation Studio, in the Projects menu, click Setup Wizard.

7EN02-0462-03 Page 149 of 1312

Install and upgrade System Guide

B. Power SCADA Expert 8.1:

In the Project Editor, click Tools > Computer Setup Wizard.

2. Select Express Setup and click Next.

Page 150 of 1312 7EN02-0462-03

System Guide Install and upgrade

3. Update the password and save it to the backup directory location.

Device Profiles

1. In Windows Explorer, navigate to the folder containing the device profiles. The default
location is:
C:\ProgramData\Schneider Electric\PowerSCADA Expert\vx.x\Applications\Profile Editor

2. Copy the entire folder and then paste it to the backup directory location.

3. To restore profiles, copy the backed-up device profiles from the backup location to the
following location on the Destination Server:
C:\ProgramData\Schneider Electric\PowerSCADA Expert\vx.x\Applications\Profile Editor

Backing up redundant Power Operation systems

For a redundant system only, on the secondary system repeat Backing Up Power Operation
automatically.

Backing up Power Monitoring Expert

This description of backing up Power Monitoring Expert (PME):
• Applies to a standalone server implementation.

• Expects that the new PME server has the same name as the original.

• Expects that the same version of PME and SQL Server are used on both the new and old
servers.
• Does not include the following items which can be configured again for a new instance:
Dashboard Images

Dashboards

Data Center Edition Images

Database archives

7EN02-0462-03 Page 151 of 1312

Install and upgrade System Guide

EWS config

Report Subscriptions

SQL Script Files

Power Monitoring Expert databases

The following PME databases must be backed up to a location off the PME server:
• ION_Data (PME backs up weekly)

• ION_Network (PME backs up daily)

• ApplicationModules (PME backs up daily)

For details, see Scheduled jobs in the Windows Task Scheduler section of the PME System
Guide.

Power Monitoring Expert config folder

To reproduce the system in the case of a catastrophic failure, a copy of the \config folder should
be stored in an off PME server location. This holds all the files that make your PME system
unique. The copy of the \config folder only needs to be done once unless subsequent changes are
made to the system.

Power Monitoring Expert diagnostics

Run a diagnostic capture using the Diagnostics Tool available in PME. Doing so stores
information about the source PME system—including server specifications and OS/SQL
versions—that are necessary to rebuild the system. Store the resulting .cab file in the off PME
server location.

Deleting old backups

Backups can quickly fill up your backup directory drive. You can automate your system to delete
old backups. The following procedure demonstrates how to delete backup files that are older than
15 days.

To delete backup files that are 15 days or older:

1. In a text editor, open Delete_old_Backups.ps1

2. Edit the file for your system:

a. For Power Operation backups: enter the path of the PSE_Backups folder. For example:
C:\PSE\PSE_Backups

3. Save the file as Delete_old_Backups.ps1 under:

C:\Program Files (x86)\Schneider Electric\BackupTasks

4. Create a Windows scheduled task to trigger this script to run weekly once at midnight.

Page 152 of 1312 7EN02-0462-03

System Guide Install and upgrade

5. Define the new action:

a. For Action, click Start a program.

b. In Program/script, enter the following path:

C:\Windows\syswow64\WindowsPowerShell\v1.0\powershell.exe

c. In Add arguments, enter the following:

-noninteractive -nologo -file " C:\Program Files (x86)\Schneider
Electric\BackupTasks\Delete_old_Backups.ps1"

Restoring a Power Operation system

This section describes the tasks that are required to restore a Power Operation system on a new
Destination server.

NOTE: After restoring, you may need to manually reconfigure a system management server,
deployment server, and TLS certificate management. For more information, see the Citect Help
Post Installation Configuration section.

Restoring Power Operation

The following must be verified before restoring the backups on the Destination Power Operation
Server:
• Power Operation is installed and working on the designated Destination Server.

• The licenses are activated on the destination system.

• All the relevant software and OS updates have been applied to the Destination Server.

Restoring Power Operation from an automated backup

If you have a redundant system, you must also restore the redundant servers. See Restoring a
redundant Power Operation system for details.

To restore Power Operation from an automated backup on the Destination Server:

1. Copy the PSEvx.x_Restore.ps1 script on to the server.

2. Edit the file for your system:

a. For <$sourceDir>, enter your backup directory location.

b. If you did not install to the default install location, edit the <pseBin> and <$pseData> to
reflect the installed location path.

3. Run PowerShell as Administrator and set the execution policy with the following cmdlet:
Set-ExecutionPolicy Bypass.

4. Right-click on the script file and run with PowerShell.

5. If the server IP address changed, update the IP address:

A. Power Operation 2021, Power SCADA Operation 2020, Power SCADA Operation 9.0,
or Power SCADA Expert 8.2:
In Studio, click Topology > Edit and then select Network Addresses from the drop-

7EN02-0462-03 Page 153 of 1312

Install and upgrade System Guide

down menu:

B. PowerSCADA Expert 8.1:

In the Project Editor, click Servers > Network Addresses.

6. Update the IP address.

7. Compile the project.

Restoring a redundant Power Operation system

For redundant Power Operation systems, the following must be performed on the Destination
Secondary server:

1. Copy PSEvx.x_Restore.ps1 script and backup directory to secondary server.

2. Edit the file for your system:

a. For <$sourceDir>, enter your backup directory location.

b. If you did not install Power Operation to the default install location, edit the <$pseBin>
and <$pseData> to reflect the installed location path.

3. Run PowerShell as Administrator and set the execution policy with the following cmdlet:
Set-ExecutionPolicy Bypass.

4. Right-click on the script file and run with PowerShell.

5. Once all the files are restored, pack and compile the project.

Restoring Power Monitoring Expert

This section includes the tasks required to restore Power Monitoring Expert (PME) backups on
the Destination server.

Verify the following before restoring the backups on the Destination PME Server:

Page 154 of 1312 7EN02-0462-03

System Guide Install and upgrade

• PME is installed and working on the new PME Server.

• The new server should have the same name as the original PME Server.

• The SQL Server version of the new system needs to be the same or newer as that of the old
system.
• The licenses are activated on the new system.

• All the relevant software and OS updates have been applied to the new PME Server.

Replace the Config Folder

1. Stop all ION Services:
a. In Control Panel\Administrator Tools\Services, stop the ION Network Router service.
This stops all ION services.

b. Stop the ApplicationModules CoreServicesHost service. This stops all

ApplicationsModules services.

2. Copy the backed up \config folder to the C:\Program Files (x86)\Schneider Electric\Power
Monitoring Expert folder. This will update the \config folder with all the files that were unique
to the original installation.

3. Leave the ION and ApplicationsModules services stopped to restore a database (Restoring
the Databases from the Old System).

Connect the old databases

You need to detach, and then remove, rename, or delete the factory (new) database files before
you can connect the old database files to the new system.

Detach the default databases

Before you can remove, rename, or delete the factory installed ION_Data, ION_Network, and
ApplicationModules databases on the new PME system with the copies made from the old PME
system, you must first detach the factory installed databases.

To detach the ION_Data database from the new system:

1. Go to SQL Server Management Studio and right-click ION_Data > Tasks > Detach.

NOTE: If you cannot detach a database because of active connections, click Drop
Connections in the detach dialog in SQL Server Management Studio.

For example:

7EN02-0462-03 Page 155 of 1312

Install and upgrade System Guide

2. Follow the same steps to detach the ION_Network and ApplicationModules databases.

Remove, rename, or delete the factory databases

Detaching the databases will not remove the database files from the new PME folder structure.
Since the old databases that you need to upgrade must be in the same location as the factory
ones, you need to delete, remove, or rename the factory database files.

1. Navigate to the location where you installed the factory database files.

NOTE: The default installation location is ...\Schneider Electric\Power Monitoring

Expert\Database. However, you might have picked a different location during installation.

2. Rename the factory database files. For example:

Restore the databases from the old system

Restore the backed-up databases to the new PME system at their installation location.

To restore copies of the backed up PME databases into the new PME system:

1. In SQL Server Management Studio, right-click Databases and then click Restore
Database.

Page 156 of 1312 7EN02-0462-03

System Guide Install and upgrade

2. Click Device and then click the ...(ellipsis) button.

3. Click Add.

4. In the Locate Backup File dialog, navigate to the location where the backup database files
are stored and enter the database name in the File name field.

7EN02-0462-03 Page 157 of 1312

Install and upgrade System Guide

For example:

5. Click OK.

6. Make sure that Restore is checked:

Page 158 of 1312 7EN02-0462-03

System Guide Install and upgrade

7. Click on the Files tab on the upper left of the window, select Relocate all files to folder,
and then select the location for restoring the database:

8. Select the default location for the PME databases. For example:

9. Click OK.

10. Repeat Steps 1 to 9 for the remaining database files (ION_Data and ION_Network).

7EN02-0462-03 Page 159 of 1312

Install and upgrade System Guide

The following image shows the restored databases:

Start the Power Monitoring Expert services

This is best done by rebooting the Power Monitoring Expert server. Alternatively, you could
manually restart all Automatic startup type Application Module and ION Services.

Post-restoration checks
1. Check the system log in the Management Console for errors.

2. Log in to Web Applications and ensure all applications work. For example, run the System
Configuration Report.

3. Check the Vista diagrams and correct any Query Server or VIP links, if necessary.

Backing up and restoring scripts

Go to www.se.com and search for the FAQ How to automatically backup a PowerSCADA Expert
system to get backup and restore scripts specific to your Power Operation system version.

Backing up and packaging archive files

Archived files are packaged, encrypted, and password protected. Archived packages contain
backup files from Power Operation and a manifest that captures the state of the files when they
were archived.

An archive package contains:

• Files obtained from backup.

• A manifest archive file that contains a list of all archive files in the set.

• A table of contents toc.txt file is available after the archive is unpacked. It contains an entry for
every file or folder from the configuration.

A Log.txt file is created after the archive file is unpacked.

Recommendations:
• Ensure Windows maximum path length limitations are met.

• Use complex passwords or passphrases with a minimum length of eight characters.

• Document and store passwords and user names in a protected location.

Page 160 of 1312 7EN02-0462-03

System Guide Install and upgrade

• Follow backup tasks as described by your organization or contact your network administrator.

• Plan a backup location to store archived packages for future use.

1. Define configuration settings for an archive package using:

The Archives.yml file in the Power Operations Applications program folder.

A text and source code editor, such as Notepad++.

Example configuration settings:

2. Verify backup name, path, search pattern, and location settings are correct in the in the YML
file.

3. Open a command-line interpreter, such as Windows Command Prompt.

NOTE: You can also write a batch file or use Windows Task Scheduler.

4. At the command prompt, enter path to Archiver.exe and pack -- help to view available
options.

Example path and command:C:\Program Files (x86)\Schneider

Electric\Power Operation\v2021\Applications\Archiver.exe pack --help
to view available options.

5. At the command prompt, enter a packing command for input and output using the desired
folder paths.

Example packing command: C:\Program Files (x86)\Schneider

Electric\Power Operation\v2021\Applications\Archiver>Archiver.exe
pack --configuration c:\input\pack\Archives.yml --output
c:\restore\pack

6. Enter password. Archiver packs backups into packages.

7EN02-0462-03 Page 161 of 1312

Install and upgrade System Guide

7. Look at packing results:

Packing result Action

Archiver packed
None
files successfully
Open the Log.txt file in the output folder and
Archiver failed to
search for [WRN] indicating return of 0 file, and
pack files
re-enter command line for packing.

8. Store archived packages, containing manifest and backup files, for future use.

Restoring and unpackaging archived files

Run a command line utility before restoring an encrypted backup to verify it has not been
tampered with or compromised. Information required for post-incident forensic activity, for
example, audit logs, is included in the backup. This procedure can take up to 15 minutes to run
depending on the size of the archive file.

Recommendations:
• Follow restore tasks as described by your organization or contact your network administrator.

Required for this procedure:

• Archive package with backup and manifest files in an accessible location.

• Password for the archive package.

1. At the command prompt, enter a path to the manifest and a path to the desired output folder
to the same command line.

Example command: C:\Program Files (x86)\Schneider Electric\Power

Operation\v2021\Applications\Archiver>Archiver.exe unpack --
manifest c:\input\pack

Example path: --output c:\unpackbackups\

2. Check the toc.txt saved with your backup to verify the contents of the backup are what is
wanted to restore before you unpackage. Open a command-line interpreter, such as
Windows Command Prompt.

3. Select Tab. The manifest AES file is located and added to the command line.

4. Enter password. Archiver unpacks archived files.

5. Review unpacking results:

Page 162 of 1312 7EN02-0462-03

System Guide Install and upgrade

NOTICE
UNINTENDED DATA LOSS OR LOSS OF SOFTWARE FUNCTION
• Only overwrite files and folders you are certain are from Power Operation with
Advanced Reporting and Dashboards.
• Back-up important files from other software before overwriting Power Operation with
Advanced Reporting and Dashboards.
Failure to follow these instructions can result in irreversible damage to software
and databases.

Packing result Action

Archiver unpacked
Restore files.
files successfully
Backup.aes will not be unpacked because it has
been modified after it was originally archived. If
any part of the package was tampered with, do
Error
not restore files and follow cybersecurity tasks as
described by your organization or contact your
network administrator.

6. Open Power SCADA Studio.

7. Click Backup > Restore. The Backup Project dialog box opens.

8. Click Browse.

9. Select the CTZ backup file that contains the files you want to restore and click OK.

Licensing

NOTICE
LOSS OF COMMUNICATION
• Activate product and component licenses prior to the expiry of the trial license.
• Activate sufficient licenses for the servers and devices in your system.
Failure to follow these instructions can result in loss of data.

A point limit is allocated to each type of license included in your license agreement. These license
types include:
• Full Server Licenses

• Client Access Licenses

If required, you can specify how many points will be required by a computer. See Specify the
required point count for a computer.

License keys
Every Power Operation component purchased must have an associated license.

7EN02-0462-03 Page 163 of 1312

Install and upgrade System Guide

Power Operation component and license hosting

All components have software key license option availability.

Power Operation Component Location where license can be hosted

Server On machine where Server is installed.
Floating license model: On machine where Primary
Server is installed.
Client (control or view-only)
Static license model: On machine where Client is
installed.
Redundant Client (when server
On machine where Stand-by Server is installed.
redundancy is used)
Event Notification Module On machine where Server is installed.
EcoStruxture Anywhere On machine hosting Power SCADA Anywhere.
Advanced Reporting On machine hosting Advanced Reporting.
Additional Advanced Reporting
On machine hosting Advanced Reporting.
modules

Mapping commercial names and license

keys
Power Operation key version information displayed in the PO software does not match PO
commercial version names.

For those with Plant SCADA (formerly Citect SCADA) experience, this PO key version information
does not necessarily align with the respective Citect SCADA key versions, (for example, Citect
2015 used key version 7.50).

Before v8.0, all PO key version numbers aligned with the PO commercial name/number and the
Citect SCADA key versions. Starting with v8.0, PO aligns commercial version names/numbers
with PME instead of Citect.

License key version information

PO Plant SCADA
PO key
commercial commercial Comments
version
name/number name/number
– Power Operation 2021 licenses
Power
8.3 Plant SCADA 2020 R2 are not backwards compatible
Operation 2021
with older versions
PSO 2020 R2 8.2 Citect 2018 R2.1 –
PSO 2020 8.2 Citect 2018 R2 –
PSO 9.0 8.1 Citect 2018 –
PSE 8.2 8.0 Citect 2016 –

Page 164 of 1312 7EN02-0462-03

System Guide Install and upgrade

PO Plant SCADA
PO key
commercial commercial Comments
version
name/number name/number
PSE 8.1 8.0 Citect 2015 –
PSO key versions were ‘shipped
as’ 7.5 but all licenses were re-
PSE 8.0 SR1 8.0 Citect 2015 programmed in License Portal as
8.0 in mid-2016 to enable free
upgrade to PSE 8.1.
PSO key versions were ‘shipped
as’ 7.5 but all licenses were re-
PSE 8.0 8.0 Citect 7.40 programmed in License Portal as
8.0 in mid-2016 to enable free
upgrade to PSE 8.1.
PSE 7.40 7.40 Citect 7.40 –

Activating licenses
If your Power Operation system uses FLEXERA Softkey Licensing, you need to activate your
licenses to allocate the computers in your system. To do this, you use the Schneider Electric
Power Operation License Configuration Tool.

If you purchased softkey licenses for your Power Operation system, the required activation codes
will be emailed to your from [email protected].

Required for this procedure:

• License activation ID from the purchase confirmation email.

1. Click Start on the taskbar.

2. Select Schneider Electric > Power Operation License Configuration Tool.

3. Click Activate.

4. Select an Activation Method > click Next.

5. Enter an Activation ID.

6. Click Next to navigate through the screens and finish installation. License(s) can be viewed
in the License Configuration Tool.

Dynamic Point Count

Power Operation counts I/O device addresses dynamically at runtime.
The client process keeps track of the dynamic point count. This includes variable tags used by the
following:
• Alarms

• Trends

• Reports

7EN02-0462-03 Page 165 of 1312

Install and upgrade System Guide

• Events

• OPC DA Server

• EWS Server

• Pages and Super Genies

• Cicode functions (TagRead, TagWrite, TagSubscribe, TagGetProperty and TagResolve)

• Any tag referenced by Cicode

• Reads or writes using DDE, ODBC, CTAPI or external OPC DA clients.

A variable tag is only counted towards your point count the first time it is requested. Even if you
configured a certain tag on a page in your project, the variable tag will not be counted towards
your point count unless you navigate to that page and request the data.

You should also be aware of the following:

• A dynamic point count is tag based, not address based. For example, two tags that use the
same PLC address will be counted twice.
• For the multi-process mode, each server component will accumulate its own point count
which will add to the total of the client dynamic point count.

If two trend tags use the same variable tag, it will be counted once. If two server components
use the same tag(s) (say alarm and trend), the tags will not be counted twice when the point
count gets totaled in the client process.
• For the multi-process mode, the client component will also accumulate its own point count,
which will include all the variable tags that are used by the process.
• For the multi-process mode, the machine point count will be the point count of the client
component, or the point count added up from each server component, depending on
whichever is bigger. If the server point count is greater than 500, the client component point
count is disregarded.
• Reading properties of a tag with TagGetProperty() or TagSubscribe() will cause that tag to be
included in the point count, even if the value is not read.
• Persisted I/O (memory devices), local variables and disk I/O variable tags will not count
towards the dynamic point count, unless they are written to by an external source (via OPC,
DDE, ODBC, or CTAPI). For example, if you use an OPC client to write to a local variable,
each local variable will be counted once the first time it is used.

Notes:
• You can use the CitectInfo() Cicode function or the General page in the Power Operation
Kernel to determine the point count status of a client process.
• You can specify the point count required by a client computer by using the
[Client]PointCountRequired INI parameter.

Page 166 of 1312 7EN02-0462-03

System Guide Install and upgrade

Specify the required point count for a computer

The available point count for a Power Operation computer is determined by the type of license to
which it is entitled. This is based on the role assigned to the computer by the
[Client]ComputerRole parameter (which is typically set via the Computer Role page of the Setup
Wizard).

Normally, the computer will get the first available matching point count. However, you can specify
the point count required by a client computer by using the [Client]PointCountRequired INI
parameter.

When any remote clients disconnect, the corresponding licenses that have been served to them
can be reclaimed.

NOTE: An INI parameter is also available to control IP address aging. It is used to indicate how
long to reserve a license for a given IP address in cases when a remote client connection is lost.
This does not apply to full server licenses. The parameter is
[General]LicenseReservationTimeout.

Run the software in demo mode

You can run Power Operation without the hardware key in demonstration (demo) mode. Demo
mode lets you use all Power Operation features normally, but with restricted runtime and I/O.

The following demo modes are available:

• 15 minutes with a maximum of 50,000 real I/O.

• 10 hours with a maximum of 1 dynamic real I/O. This is useful for demonstrations using
memory and disk I/O. Power Operation starts in this mode if no hardware key is available. If
the system detects that you are using more than 1 real I/O point at runtime then it will swap to
the 15 minutes demo mode.

NOTE: Writing to any tag through DDE, CTAPI, or ODBC will cause that tag to contribute to
the dynamic point count even if it is a memory or disk I/O point. If you write to more than 1
point through these interfaces, it will swap to the 15-minute demo mode.

• 8 days with unlimited tags. This is only available through special Power Operation
Development keys.

7EN02-0462-03 Page 167 of 1312

Configure System Guide

Configure
This section describes the different tools and tasks for configuring Power Operation.

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

Section Description
Things to consider to help you prepare for configuring a Power
Configuration prerequisites
Operation project.
Changing configuration on Describes configuration changes that can be made on a running
a running system system.
Configuration tools An introduction to the Power Operation configuration tools.
Creating a Power Operation project using Project Setup, as well
SCADA Projects
as compiling, backing up, an restoring a project.
Information and tasks on how to configure and work with:
• Device profiles

• Device types

• Device tags
Devices
• Profile Editor projects

• Profile Studio projects

• Adding I/O devices to the project

• Alarms

How to configure and work with:

• Graphics pages

• Animated one-lines

Power Operation Runtime • Menus and pages

• Basic reports

• LiveView

• Notifications

How to configure and work with:

• Alarms
Web Applications
• Diagrams

• Web Applications settings

Information on extending the capabilities of Power Operation by

Applications
configuring applications.
Managing user accounts,
Configure and manage user access.
roles, and mapping

Page 168 of 1312 7EN02-0462-03

System Guide Configure

Section Description
Cybersecurity Cybersecurity considerations including: two-factor authentication
configuration (one-time password) and McAfee white listing.
Customize default How to use Cicode to customize a project, localizing a project, and
behaviors running PO as a Windows Service.
System Startup and
How to validate your configured system on startup.
Validation Checks
How to configure:
• Advanced Reporting and Dashboards Module

• EcoStruxture Anywhere

Distributed systems • EcoStruxure Web Services

• Time synchronization and time zone settings

• OFS time stamping

• OPC-DA Server and Client

Redundant systems How to configure a redundant server.

For more detailed resources on configuration, see the Configure references section.

Configuration prerequisites
• Review the system development process provided in this document.

• Gather the supporting documents that you may need.

• Create a system architecture drawing, including the servers, devices, and all connectivity.
Define the IP addressing for each gateway and device.
• Order the appropriate equipment, including computers, software, and system devices.

• Ensure that all devices that will communicate through this system are set up and properly
addressed.
• Have a copy of the Example.CSV file for adding devices to the system. You will use this file if
you need to manually add multiple devices to your project.
• Set up the Server and Client computers that you need for your system.

• Ensure that the IT team has opened the appropriate firewall ports. See the Power Operation
with Advanced Reporting and Dashboards – IT Guide for details.
• Ensure that all license keys have been purchased and are ready to be installed.

Changing configuration on a running system

This section describes configuration changes that you can make on a running system. You do not
have to restart the system.

7EN02-0462-03 Page 169 of 1312

Configure System Guide

Adding I/O devices, variable tags

In an architecture that has redundant or multiple I/O servers, new I/O devices and variable tags
can be added to the project while it is running and online. Add the devices and tags, re-compile
the project and restart just the associated I/O server processes to which the I/O devices were
added. In the redundant architecture, this means you should restart the associated primary I/O
server process, while the associated standby I/O server remains up and running. After the primary
I/O server is running again, restore the updated project on the secondary Power Operation server
machine and restart the associated standby I/O server process.

Alarms, trends, reports

In the project, design an administration page containing a button that executes the
ServerReload Cicode function.

NOTE: Ensure that this page is only accessible by a logged-in user with the highest
Administrator privileges.

While the project is running, ensure that the [LAN]AllowRemoteReload parameter is set to "1"
in the Citect.INI file located on the target Power Operation server machine. Use the administrative
ServerReload button to load subsequent changes to alarms, trends, and reports. For a list of
supported changes to alarms/reports/trends fields, see the Power Operation PC-based help file,
"Server-Side Online Changes" topic. Keep in mind that ServerReload is not restarting the
Alarm/Trend/Report server processes, nor is it rebooting the physical server machine. It simply
re-loads the configuration databases into the running alarm/trend/report server processes.

Graphics pages
After modifying a graphics page, save the page and re-compile the project. In the HMI client,
reload the page by navigating away from it and then returning to it. The updates to the page can
then be seen in the HMI client, all while the project remains running.

New graphics pages

After adding new graphics pages, save the pages and re-compile the project. Restart the HMI
client only. It is not necessary to restart any other server processes.

Other changes to project configurations

Changes to other configurations such as users, roles, menus, and Cicode require a full system
restart of all server processes.

Debug logging
The following PWRMODBUS driver parameters can be changed without needing to restart the
associated I/O server:
• DebugCategory

• DebugLevel

• DebugUnits

Page 170 of 1312 7EN02-0462-03

System Guide Configure

Server CPU load balancing

Ensure that you are aware of how Power Operation Server loading balancing works.

WARNING
UNINTENDED EQUIPMENT OPERATION
• Do not exceed more than 50,000 tags or 200 devices per I/O Server.
• When tag and device counts indicate two different I/O server counts, use the larger number
of I/O servers as your requirement.
• Assign and balance the tags or points that the Power Operation Server are managing across
multiple CPU cores.
Failure to follow these instructions can result in death or serious injury.

While a Server machine may have sufficient overall CPU processing power, if all tags are being
managed and processed by a single CPU core, the Power Operation Server could become
overloaded and could unexpectedly stop running. Important events and alarm notifications would
not be received.

Configuration tools

NOTICE
INOPERABLE SYSTEM
Ensure that you have received training and understand the importance of the Power Operation
productivity tools and workflows.

Failure to follow these instructions can result in overly complex projects, cost
overruns, rework, and countless hours of support troubleshooting.

NOTE: Power Operation is built on Power Operation Studio and includes productivity tools that
are designed and optimized to create the tags you need to configure power-based
SCADA projects. If you have prior experience using Power Operation Studio, do not rely
exclusively on Citect tools to build a SCADA project.

Power Operation configuration tools consist of:

• Profile Editor: Use this tool to select tags to be used by device types (tags must be
consistent with IEC 61850 naming conventions), create device profiles for individual devices,
and create projects that include the device profiles to be used in a single installation. You can
specify real-time tags, PC-based alarm tags, onboard alarm tags, trend tags, and reset tags
to be generated for this device.
• Application Configuration Utility: Use this utility to configure many features that would
require more time-consuming effort if performed by editing INI settings.

7EN02-0462-03 Page 171 of 1312

Configure System Guide

• I/O Device - Wizard: Using this wizard, you will import device profile information from the
Profile Editor into a project. This tool is simply a means of moving device profile information
into the project and converting it into formats that Power Operation can use.
• Power Operation Studio: Use Power Operation Studio for basic navigation. From here, you
also choose the active project. Use the Power Operation Studio for entering database-type
information, such as adding clusters and servers, creating new users, and editing tags within
projects.

NOTE: It is recommended that you run your system in normal mode. When possible, refrain
from running applications in Administrator mode to help prevent shellcode from being
successfully executed.

• Graphics Builder (design time): Use the Graphics Builder to create one-line drawings that
users can view in the runtime environment. These drawings are populated with interactive
objects that are generated by genies. You can also use the graphics tool to set up system
alarms and trends.
• One-Line Configuration Utility: You can review genie configurations, and then make
necessary repairs before you compile your project.

When a Power Operation system is deployed, the Power Operation Runtime lets users view the
one-line drawings, including alarms, events, and history data. With the appropriate degree of
password-controlled authority, users can also perform advanced tasks, such as changing alarm
setpoints and racking devices in and out.

Application Configuration Utility

Use the Application Configuration Utility to configure many features that would require more time-
consuming effort if performed by editing INI settings.

Options that are available on every page are:

• Project Name: Located at the top of the page, this option allows you to choose the project.
Unless you change it, this project will then remain selected for each window in the Application
Configuration Utility.
• Display Selected Settings: Click this link to display the settings that have been entered in
specific area of the Application Configuration Utility (Application Services, Application
Services Host, Applications, Security) that you are viewing.
• Display All Settings: Click this link to view the settings that have been entered for the entire
Application Configuration Utility.
• Search: Click this link to open a search window. Type the key word or phrase you want to
search on, then click to view the list of screens on which the word or phrase are found. Click
a screen name, and the screen displays. Click the 'x' in the upper right corner of the search
results to close the search window.
• Tooltips: To view help for an individual field, point your mouse and hover over the field.

Page 172 of 1312 7EN02-0462-03

System Guide Configure

Application Services Host—Citect Data Platform

This section relates to how the Schneider Electric CoreServiceHost connects to Power Operation.

Use this page to link a Power Operation user name and password to be used when the Schneider
Electric CoreServiceHost services connect with runtime.

Before you begin:

• Add the username/password to the Power Operation project.

• Have the project running in runtime mode.

Follow these steps:

1. In Citect.ini, set [ctAPI] Remote = 1.

2. Open Application Configuration Utility and then click Application Services > Citect Data
Platform > Connection tab.

3. In Citect I/O Server Address choose the server address for the project that is running. If
Citect requires encryption, this must be the computer name.

4. In Citect User Name enter the user name for this user.

5. In Citect Password enter the password for this user.

6. Click Test Credentials to verify these credentials. If you see an error, verify the name and
password, and that runtime is running, and then try again.
When your project is running and the credentials are valid, you see Connection Successful.
The user name and password can be used to connect to Power Operation.

7. To set up web redundancy, select the Key Management tab. Use the Export Key and
Import Key buttons to save an encryption key and export it to another computer as an AES
file. This supports the token validation key for redundant web clients. Please keep this file
secured at all times.

NOTE: To provide extra security you can run Power Operation as a service. Both Power
Operation and CoreServiceHost must be running as a service on Session 0.

1. In Citect.ini, remove [ctAPI] Remote or set it to 0.

2. Leave Citect I/O Server Address blank.

3. Leave Citect User Name blank.

4. Leave Citect Password blank.

5. Click Test Credentials, and the test will fail. However, you can verify that the service has
started by viewing the Event Log.

NOTE: If unable to successfully connect to Power Operation, check the following:

1. In Citect.ini, set [ctAPI] Remote = 1 if required.

2. In the Power Operation Studio, confirm the Network Address 'Address' field is set to a
computer name or IP Address. Localhost or 127.0.0.1 is not compatible with Citect
encryption enabled.

7EN02-0462-03 Page 173 of 1312

Configure System Guide

3. In the Power Operation Studio, confirm the Computer 'DNS Name' field is set to a
computer name.

4. Run the Computer Setup wizard and confirm the 'Network Setup' is configured properly for
the system. If 'Networked' is selected, confirm the 'Address Type' and 'Address Scope' is
correct.

5. Changes to the project, ini settings, or Computer Setup Wizard requires the project to be
restarted.

Set up data acquisition parameters

Credentials configured in the Citect Data Platform allow applications to run externally and allow
Citect to get data from basic reports, LiveView, the EWS Server, and the ETL.

This section relates to how the core service host connects to the live, running Power Operation
project.

Before you begin:

• Add the username/password to the Power Operation Studio project.

• Have Power Operation Studio running in runtime mode.

To link a user name and password that will be used when the Schneider Electric CoreServiceHost
services connect with runtime:

1. a. Open the Application Configuration Utility:

In Power Operation Studio: click Projects > Power Applications

> Application Config Utility.

OR
From the Start menu: Click Schneider Electric > Application Config Utility.

b. In Application Configuration Utility, expand Applications Services Host and then click
Citect Data Platform.

2. In Citect I/O Server Address, enter the server address for the project that is running.

NOTE: This can be left blank if you are using a local connection and you are running Power
Operation as a service.

3. In Citect User Name, enter the user name of a user configured in the project.

4. In Citect Password, enter the password for the Power Operation Studio project user
entered above.

5. Click Test Credentials to verify these credentials.

If you see an error, verify the name and password, the Power Operation Runtime is running,
and try again.

When your project is running and the credentials are valid, a Connection Successful
message appears. The user name and password can be used to connect to Power
Operation Studio.

Page 174 of 1312 7EN02-0462-03

System Guide Configure

Citect Licensing Details: This is a read-only field that displays the license key currently in
use on the Power Operation Studio server machine.

Configuring service layer components

You must configure Power Operation to use the service layer components. For calls to be
forwarded properly from service-to-service, configure the Web Application, PsoWebService, and
Platform Server components as described below.

Configuring the web application

If you want to change the machine name or port, you must configure the web application to know
how to reach PsoWebService. The web application consists of two separate IIS services:
PsoDataService and WebHmi.

It is not recommended to edit web.config files. Incorrectly modifiying these files can lead to loss of
functionality for the WebHmi.

NOTICE
UNINTENDED DATA LOSS OR LOSS OF SOFTWARE FUNCTION
• Only overwrite files and folders you are certain are from Power Operation with Advanced
Reporting and Dashboards.
• Back-up important files from other software before overwriting Power Operation with
Advanced Reporting and Dashboards.
Failure to follow these instructions can result in irreversible damage to software and
databases.

To edit the web application configuration:

1. Navigate to the respective web.config files:

C:\Program Files (x86)\Schneider Electric\Power
Operation\v2021\Applications\Web\SystemDataService\Web.config
and:
C:\Program Files (x86)\Schneider Electric\Power
Operation\v2021\Applications\Web\WebHMI\Web.config

2. In the appSettings section of each web.config file, find the line:

<add key=”PsoWebService” value=”localhost:23200”/>
This value is the address at which the web application can contact PsoWebService, in the
form
IPAddress:Port.

3. Configure the IP address with the same machine name as the one used to generate the SSL
certificates.

Configuring PsoWebService
You must configure PsoWebService to know its own address.

To edit the PsoWebService configuration:

7EN02-0462-03 Page 175 of 1312

Configure System Guide

1. Navigate to the appsettings.json file:

C:\Program Files (x86)\Schneider Electric\Power
Operation\v2021\Applications\Services\Pso Webservice

2. Configure the Endpoint, ConnectionTimeoutSeconds, and Host sections as follows:

• Endpoint: Use the same machine name and port configured in the web.config file above.

• ConnectionTimeoutSeconds: PsoWebService constantly receives calls from each

connected PlatformServer. Set the number of seconds after which PsoWebService will
consider a Platform Server to be disconnected. If a Platform Server doesn’t call
PsoWebService within that time frame, it is marked Disconnected.
• Host: Use the same machine name as Endpoint. The port numbers should not change unless
there is a port conflict.

NOTE: If there is a port conflict, PsoWebService will not start, and will log a message stating
the application has been terminated. To resolve the issue, reconfigure PsoWebService to
use a different port.

Configuring PlatformServer
Because the PlatformServer communicates with Citect to read data by default, you do not need to
configure it.

To edit the PlatformServer configuration:

1. SimulationMode: false.

NOTE: Do set to anything other than false in a production environment.

2. Identity / Endpoint: Set to the IPAddress:Port of the machine where the PlatformServer
is running.

3. Responsibilities: "RealtimeData", "AlarmData", "DocumentData",

"EquipmentData", "AuthenticationData", and "WaveformData". Details what types
of calls from PsoWebService this PlatformServer can handle. When you configure a
responsibility, it advertises this information to its PsoWebService(s) by a ping call that
PlatformServer makes up to PsoWebService. This information is recorded by
PsoWebService so that it knows if it can route particular kinds of calls to the PlatformServer.

NOTE: There are currently six types of responsibilities, and their RequestType values
must be spelled exactly as they appear above (case-sensitive). Each responsibility also
has a Priority value, where 1 is the lowest priority, and a lower value indicates a higher
priority. For example, if you have three PlatformServer instances on three separate
machines, you could configure one to be “Priority”: 1, another 2, and the other 3.
When a call comes in for that type of request to PsoWebService, if it sees multiple
PlatformServer instances that service that type of request, it will send the request to the
PlatformServer that has the lowest numerical value for “Priority”.

4. PingInterval: A number in units of seconds that indicates how much time passes between
ping calls to the PsoWebServices.

Page 176 of 1312 7EN02-0462-03

System Guide Configure

5. WebServices: A json array of IPAddress:Port addresses of PsoWebService instances

to which the PlatformServer should ping or connect. These should match the Endpoint
values in their corresponding PsoWebService appsettings.json files.

6. Host: Configure with the same machine name used under Endpoint. The port numbers
should not change unless there is a port conflict.

Profile Editor typical workflows

The following flow charts illustrate how to use the Profile Editor. The first illustration provides an
overview, while the subsequent workflows show:
• Creating/editing a device type

• Creating/editing a device profile

• Creating/editing unit templates

Workflow overview

7EN02-0462-03 Page 177 of 1312

Configure System Guide

Create/edit device type

Page 178 of 1312 7EN02-0462-03

System Guide Configure

Create/edit device profile

7EN02-0462-03 Page 179 of 1312

Configure System Guide

Create/edit unit templates

Profile Editor main menu options

The main menu options (File and Settings) on each of the major tabs of the Profile Editor are
described in the following table:

Field Name/Valid Entries Comments

File > Save Saves any current changes.
Creates a CSV file of basic tag data. Store the file in a folder
File > Create CSV file
you designate. The file can be viewed in Excel.
Displays a print preview of all of the tags for this device type.
File > Print Tag Selections
You can then print the spreadsheet.
Import projects from other instances of the Profile Editor.
These must be PLS or ICD files.
File > Import
For more information, see "Import and export project files" on
page 266.

Page 180 of 1312 7EN02-0462-03

System Guide Configure

Field Name/Valid Entries Comments

Export a PLS or ICD file to be used in another instance of the
Profile Editor, or to be used as a backup.
File > Export
For more information, see "Import and export project files" on
page 266
Settings > Display Advanced
Causes additional “advanced information” columns to display.
Properties
Delete any import template that has been added to the project.
Settings > Remove Import
To add import templates, see "Using import templates" on
Templates
page 275.
Settings > Set Up Custom Displays the Add/Edit Custom Tags screen. See for a
Tags description of this screen.
Displays the Set Up Device Type Categories. See "Managing
Settings > Set Up Device
device type categories" on page 221 for a description of this
Type Categories
screen.
Displays the Set Up Engineering Unit Templates screen. Click
Settings > Set Up
"Set up engineering templates and select conversions" on
Engineering Unit Templates
page 1036 for a description of this screen.
Settings > Set Up Trend Displays the Set Up Trend Definitions screen. Click for more
Definitions information.

SCADA Projects
SCADA projects are repositories that hold the configuration information for your system that
includes information such as servers and other system components, I/O devices, tags, alarms,
and graphic pages that are used to build a runtime system, and Cicode/CitectVBA.

The configuration for a runtime system can be spread across multiple projects depending upon
the scale of operations. Small, simple operations may require only a single project that houses all
components required for runtime. For larger, complex operations or multi-site operations, several
projects can be created based on specific plant areas, engineering processes or libraries, which
are “included” together to form a single merged configuration used at runtime.

This section includes the following project-related topics:

• Restore a project

• Use the Migration Utility

• Before you add a project

• Add a project using Project Setup

• Compile a project

• Backup a project

In the Plant SCADA help file ( ...\Program Files (x86)\Schneider Electric\Power

Operation\v2021\bin\Help\SCADA Help), see also:

7EN02-0462-03 Page 181 of 1312

Configure System Guide

• Plant SCADA Projects for information about the components that make up a project. This
topic also discusses physical layout, requirements such as architecture and security, and
project design.
• Project Types for information on preparing for a project.

Before you add a project

Before you start adding data in the project, make sure that you have:
• Used the Profile Editor to add all of the device types, device profiles, and projects.

• Created a project; from the Power Operation Studio, added clusters, network addresses, and
servers.
• Exported devices from the Profile Editor.

• Added devices into the Power Operation project, using the I/O Device Manager.

Add a project using Project Setup

Project Setup lets you quickly set up a Power Operation project. Using Project Setup, you can:
• Create and name a project

• Select screen resolution and contrast

• Specify primary and secondary server connections

• Specify the Advanced Reports and Dashboards connection

• Add users and link user roles to Windows authentication

• Add devices to a project

• Add default pages

• Add runtime menus

• Choose the landing page for each monitor in a multi-monitor project

After you create the project and define its features, you can also use Project Setup to change
other settings, such as devices in the CSV file, and to update your project.

For a list of project-related parameters that are created using Project Setup, see "Project Setup –
Changed Parameters" on page 191

Launch Project Setup

1. Launch Power Operation Studio.

2. Click Projects, click Add > Create and Configure Project.

Page 182 of 1312 7EN02-0462-03

System Guide Configure

The Introduction page appears.

The Introduction page lists optional components that you might want to include in your project. If
you are using optional components, you need to install them separately. The install files are on
the root of the Power Operation2021 installation media.
• Advanced Reports and Dashboards – Lets you view advanced reports and dashboards
from Power Monitoring Expert. Install this component from the Power Operation installation
media.
• Extract Transform Load tool (ETL) – Use this component to extract reporting information
from Power Operation and transfer it to Power Monitoring Expert, for use in reports. For best
performance during data load operations the ETL should be installed on an Advanced
Reporting and Dashboards Module server.

To create a new Power Operation project, or edit an existing project, click Next.

TIP: For help on any of the Project Setup pages, click "?" to the left of the top line to view the
entire Power Operation help file or hover your mouse over fields to read tooltips

System Definition
Use System Definition to set the project display settings.

7EN02-0462-03 Page 183 of 1312

Configure System Guide

To set the project display settings:

1. For Name, click either Create New or Edit Existing.

a. If you click Create New, enter a project name. Use only alphanumeric characters and
underscores.

b. If you click Edit Existing, choose a project from the list.

2. Under Resolution, choose the screen resolution that you want for the graphics pages in this
project. This should match the resolution of the monitor that will display graphics pages.

3. Under Style, choose the contrast. Standard uses a white background. High Contrast uses a
black background, which makes it easier to view graphics pages.

NOTE: You can also set high contrast using the parameters in the Power Operation Studio.
Open your project in the Power Operation Studio, then click Settings > Parameters. The
parameter name is IsHighContrast. 0 = standard; 1 = high contrast.

4. Click Next.

NOTE: After you click Next, the project is created. You cannot change or delete the project in
Project Setup . To change or to delete it, use the Power Operation Studio.

Servers and Web Client

Use Servers and Web Client to define the server information for your primary server, and for the
Advanced Reports and Dashboards server.

Page 184 of 1312 7EN02-0462-03

System Guide Configure

Project Setup detects the number of servers that are in your starter project. If you only have one
server—for example, using the loopback IP address—you see all the fields in the following image.
If you are using a project that has two or more servers identified, you only see the bottom section,
Advanced Reports and Dashboards.

To define the server information:

1. Enter the Server Name or IP Address for the project's primary server, or select it from the
list.

2. (Optional) If this is a redundant system:

a. Click Redundant System.

b. Enter the server name or IP address of the standby server, or select it from the drop-
down list.

3. (Optional) If you installed the Advanced Reports and Dashboards module:

a. Click Advanced Reports and Dashboards.

b. Enter the Advanced Reports Server Name or IP Address, or select it from the list.

c. In the User Name/Password fields, enter the user name and password used for the
Advanced Reports and Dashboards Server. Re-enter the password in the Confirm
Password field.

NOTE: WebReach is also assumed to be on this server.

4. Click Next.

For more information on Power Operation with Advanced Reporting and Dashboards server
configuration, see Servers.

7EN02-0462-03 Page 185 of 1312

Configure System Guide

Users
Use Users to add the Power Operation user information for each user who will access the runtime
pages in this project.

To add a user account:

1. Click Add User. A blank row displays in the list of users.

If you are editing a user, click the user name row.

2. Click the Role column for the user, and then select the appropriate role.

NOTE: You must assign a role to each user.

3. In the Password and Confirm Password fields, enter and confirm the password to be used
by this user.

4. (Optional) Enter a full name for the user. This field lets you enter a more descriptive user
name; it is not used to log on to the system.

5. (Optional) Under Windows Authentication, assign a role to a Windows group.

This provides central management of users through Windows. It also means that Windows
users who are in the specified Windows group will have the privileges that are assigned to
this role.

For more information on Windows users, see the Use Windows Integrated Users.

6. Click Next.

To delete a user that you previously added:

1. Highlight the user line and then click Delete Selected.

Page 186 of 1312 7EN02-0462-03

System Guide Configure

For more information on Power Operation user access configuration, see Managing user
accounts, role names, and mapping.

Menus and Display Pages

Use Menus and Display Pages to add top-level menus that display in the runtime human-
machine interface (HMI). The HMI is the view that users see. You can also define the default
runtime page that will display on a monitor.

To add menus and landing pages:

1. Under HMI Menus, click the top-level menu items that you want to include in the HMI.

NOTE: You can add more menu levels in the Power Operation Studio Menu Configuration
page: Visualization > Menu Configuration.

2. (Optional) If you have multiple monitors in your system:

a. Under Monitors, enter the number (up to 8) of monitors in the Total Monitors field. You
can also click the plus and minus buttons to increase or reduce the number.

b. Under Runtime Landing Page, the corresponding number of monitors are enabled.

c. For each monitor, select landing page you want to see when this monitor views Power
Operation

3. Click Next.

For more information on Power Operation menu configuration, see "Power Operation Runtime
menus" on page 300.

7EN02-0462-03 Page 187 of 1312

Configure System Guide

Summary
Use Summary to verify that the project information is correct for your system.

The Summary page is read-only. If you need to change something, click Previous to return to that
screen.

When you are satisfied with the information, click Save and Continue.

Device Profiles
Use Device Profiles to add device profiles to the project.

Page 188 of 1312 7EN02-0462-03

System Guide Configure

NOTE: Device Profiles displays device profiles that are available to use in the project. Device
profiles are displayed only if they exist in the project. If a device profile that you want to use is not
listed here, you must optionally create it, add it to the project, and then export it to the project
using the Profile Editor.

To add a device profile to your project that is missing from this list:

1. Click Open Profile Editor.

2. Click the Set Up Projects tab.

3. Under Project, select the project to which you want to export the device profiles, and then
click Add/Edit.

In the Add / Edit Project window:

a. Add the device profiles you want to export to your project by selecting them in the
Device Profile list, and then click the arrow button to move them into the Selected
Device Profile list.

NOTE: If the device profile you want to use is not in the Device Profiles list, you must
create it. See for more information.

b. Click Save & Exit.

4. In the Profile Editor, click Export Project.

5. Click OK to close the Export Summary window.

6. Close Profile Editor.

7. In Project Setup, click Refresh Device Profiles.

The device profiles you added in the Profile Editor are now available to use in your project.

7EN02-0462-03 Page 189 of 1312

Configure System Guide

8. Click Next.

For more information on Power Operation with Advanced Reporting and Dashboards device
profile configuration, see "Create Device Profiles" on page 242

Devices
Use Devices to add one or more devices from your system into the project.

To add one or more devices to your project:

1. Click either:
a. Import Devices From CSV and then use Manage Multiple Devices to import multiple
devices. For more information, see "Define multiple devices using a CSV file" on page
288

OR

b. Manage a Single Device and then create the device using the I/O Device Manager. For
more information, see "Define one I/O device in a project" on page 279.

2. Click Next.

For more information on Power Operation device configuration, see "Manage I/O devices in a
project" on page 277.

Finish
Use Finish to compile and run the project.

Page 190 of 1312 7EN02-0462-03

System Guide Configure

Click Compile and Run Project to view the project in the Power Operation Runtime. In runtime,
verify correct device communication using the Tag Viewer screen or by viewing any
Communication Failure Alarms.

You can also use Finish to open the following Power Operation project development tools to
further customize your project:
• Open Power Operation Studio to make a variety of changes to the project.

Many of the settings made by Project Setup are included in the Parameters file: Power
Operation Studio > Settings > Parameters. You can also change these parameters in that file.

NOTE: If you cannot make the newly-added project active, close, and then re-open Power
Operation Studio.

• Open Graphics Builder to create and edit the project graphics pages.

• Open Application Config Utility to edit or set up many project features.

When you are finished, click Finish to close Project Setup.

Project Setup – Changed Parameters

Project Setup lets you quickly set up a variety of project information. The following parameters are
organized according to the Project Setup page that lets you edit them.

System Definition screen

Project Setup Setting Section Parameter Name

Resolution MultiMonitors Resolution
Style MultiMonitors IsHighContrast

7EN02-0462-03 Page 191 of 1312

Configure System Guide

Servers

Project Setup Setting Section Parameter Name

Advanced Reports Server Applications Hostname

Menus in Project Setup

For each page selected in Project Setup (Step 5), the menu configuration items are added.

Project Setup Setting Section Parameter Name

Monitor Count MultiMonitors Monitors
Monitor 1 Landing Page MultiMonitors StartupPage1
Monitor 2 Landing Page MultiMonitors StartupPage2
Monitor 3 Landing Page MultiMonitors StartupPage3
Monitor 4 Landing Page MultiMonitors StartupPage4
Monitor 5 Landing Page MultiMonitors StartupPage5
Monitor 6 Landing Page MultiMonitors StartupPage6
Monitor 7 Landing Page MultiMonitors StartupPage7
Monitor 8 Landing Page MultiMonitors StartupPage8

In addition to parameters, you can do the following:

Servers, Network Addresses, and Computers

Project Setup Location Item

Add I/O, Alarm, Trend, and Report Servers, primary and
redundant
Step 3: Servers
NOTE: Clusters are also added here.

Step 3: Servers Add network addresses, primary and redundant

Step 5: Display: Menus and
Create HMI menus: setup for graphics pages
Display Pages
Step 5: Display: Menus and Determine runtime landing pages at various monitors
Display Pages used in the project
Step 7: Device Profiles Choose device profiles
Add I/O devices; including equipment, ports, boards, I/O
Step 8: Devices
devices, variable tags, alarm tags, trend tags
Step 9: Finish Compile and run the completed project

Final - Compile and Run Project

When you click Compile and Run Project on the final screen, the following changes are made to
the citect.ini file:

Page 192 of 1312 7EN02-0462-03

System Guide Configure

Section Parameter Name Value

Lan TCPIP 1
CTEDIT Run (Project's path)
CTEDIT LASTDATABASE (Project's name)
CTEDIT LASTDATABASEPATH (Project's path)
Client ComputerRole 0
Client FullLicense 0
Client PartOfTrustedNetwork 1
(Comma separated
list of available
Client Clusters
clusters for the
project)
CtSetup CustomSetup 0
Internet Server 0
Alarm SavePrimary (Project's path)
Report InhibitEvent 1
Report RunStandby 1
Trend InhibitEvent 1
Event Server 0
Win AltSpace 1
Server AutoLoginMode 1
Server EWSAllowAnonymousAccess 0
PLS_
StartAdvOneLine()

(ServerType.Cluster.ServerName) StartupCode *This is set on one

IO server on each
server machine in
the project
(Comma separated
list of available
(ServerType.Cluster.ServerName) Clusters
clusters for the
project)

Compile the project

After you install the software and create the project—along with clusters, network addresses, and
servers—compile the project. You will also need to compile your project periodically during
system setup.

7EN02-0462-03 Page 193 of 1312

Configure System Guide

Pack your project before you compile. In Power Operation Studio, click the Projects activity, click
Pack.

In Power Operation Studio, click Compile . If you are promoted to save your changes, click
Save.

If there are errors or warnings after the project is compiled:

1. At each error, click GoTo, which opens the location where the error occurred.

2. Using the information in the error message, correct the error.

3. After all errors are addressed, re-compile to verify that the errors are removed.

For additional information, click Help at the error screen.

Restoring a project
Restore a project from a backup and overwrite its current settings.

After restoring a project:

• Update restored TGML files using the TGML Upgrade Utility. See TGML Upgrade Utility for
detailed steps.
• Update Graphics Editor components using the EcoStruxture Power Operation 2021 R2.1
Migration Tool. See Using the Migration Utility for detailed steps.

Restore a project
1. Open Power Operation Studio.

2. Click Projects .

3. Click the Backup drop down and then click Restore.

4. Beside the Backup file text field, click Browse, and then browse to the location of the
project file you will use to restore.

5. (Optional) Click Select all included projects, with the exception of the PLS_include
project.

6. In the To area, click Current Project.

7. In the Options area:

a. Click Configuration files to restore backed up INI files and the TimeSyncConfig.xml file
(used to store time synchronization settings).

b. If you backed up the sub-directories under the project, the directories will be listed under
Select all sub-directories to restore. You can restore all or no sub-directories, or you
can select specific sub-directories to restore.

8. Click OK.

Page 194 of 1312 7EN02-0462-03

System Guide Configure

Backing up a project
To back up a Power Operation project file:

1. In Power Operation Studio, click Projects .

2. Click Backup.

3. From the Name drop down, choose the project you want to back up.

4. (Optional) Click Select all included projects.

5. Click Browse and then browse to the location where you want to store the project backup
file.

6. In the Options area, click Save configuration files. This saves the citect.ini file.

7. Click OK.

The backup CTZ file is written to the location that you choose during backup. This is a Citect Zip
file; you can open it with WinZip.

NOTE: To back up a Profile Editor project file, see "Profile Editor export" on page 267.

Delete information from Power Operation

If you need to delete any data that you entered (clusters, servers, genies, and so on), see Plant
SCADA Help for information on how to delete the data, then use the Pack command to completely
delete it. To do this, in Power Operation Studio, from the Projects tab, click Pack.

7EN02-0462-03 Page 195 of 1312

Configure System Guide

Devices
Profile Studio is used for configuration of Power Operation when aligning with IEC 61850-
standard engineering workflows, using tools like EPAS-E.

Profile Editor creates device types and device profiles outside of the IEC 61850 engineering
workflow.

Use the Power Operation Profile Editor to create and manage device type tags and tag
addresses, and use tags as building blocks for device types.

You can also create device profiles for unique devices. Once all your device tags are created, you
save them as a Profile Editor project, which can then be exported for use in Power
Operation projects.

Profile Studio overview

Profile Studio translates S-BUS (Station Bus protocol) system architectures (IEC 61850) and L-
BUS system architectures (Modbus and T104) into human-comprehensible vocabulary for HMIs
(human-machine interface). This is done by importing IEC 61850 SCD (Substation Configuration
Description) files from EPAS-E or third-party IEC 61850-compliant providers and generating a
topology that aligns with IEC 61850 electrical processes. Profile Studio detects the types of
datapoints inside the SCD file, such as alarms, setpoints, positions, etc.

Use Profile Studio to manage data acquisition by assigning profiles to datapoints and editing their
descriptions. You can assign profiles automatically or manually. You can also use Profile Studio
to create device links and virtual datapoints for EPAS projects.

After configuration, export a configuration package in the form of a ZIP file for all equipment, or for
selected equipment only. See Exporting configuration packages for more information on
exporting.

A Profile Studio project file is saved as an XPE file. An XPE file is XML for Profile Editor.

See Profile Editor for device configuration.

Profile Studio setup

During setup, you can determine whether to configure your devices for EcoSUI and EcoGTW by
choosing EPAS, or for Power Operation by choosing EPO. This defines which HMI is used with
the stated IP address.
• If Power Operation Studio is installed on the same system as Profile Studio, EPO will be
selected by default.
• If EcoSUI is installed on the same system as Profile Studio, EPAS will be selected by default.

Project data in your Profile Studio project comes from your SCD file, which is provided or
generated by EPAS-E or another program. You can import an SCD file during setup.

IEC 61850 engineering workflow

The following diagram illustrates the IEC 61850 engineering workflow and the role of Profile
Studio.

Page 196 of 1312 7EN02-0462-03

System Guide Configure

Using EPAS-E, create an Electrical Application Scheme, including the necessary

1
functions to be performed, and create communication networks with corresponding IEDs.
Export ICD files from Profile Studio and import them into EPAS-E. Link the Electrical
2 Application Scheme Functions with the available IED Functions and configure the dataflow
between the IEDs.
Export SCD files from EPAS-E and import them into Profile Studio. Now the IEDs know
3 their role, as described in the SCD file, such as the electrical section they will manage and
the data they will send/receive from other IEDs in different communication subnetworks.
Make local changes to IED configuration and export from Profile Studio as IID files. This
4
helps to maintain a consistent Single Source of Truth for overall system configuration.
After configuration of an IED is complete, download the configuration to the IED. A
5 proprietary format is allowed, though a SCL-based CID file is recommended for easy
maintainability.

Configuring devices for IEC61850 compliance

Use Profile Studio to configure devices to comply with IEC 61850.

7EN02-0462-03 Page 197 of 1312

Configure System Guide

Exporting ICD files

Profile Studio can produce an IED Capability Description (ICD) file, which defines the capability of
a given IED, including the functions and objects it supports. Depending on whether the project
type is EPO or EPAS, Profile Studio will export a corresponding ICD file.
To export an ICD file from Profile Studio:

1. Select Export > Export ICD File.

2. Browse to select a location for your ICD file.

Importing SCD files

Profile Studio detects the types of datapoints inside an SCD file, such as alarms, setpoints,
positions, etc.

Import an SCD file into Profile Studio during project creation.

• In the Create new project dialog, in the Import devices and datapoints section, enable the
IEC61850 SCD files radio button.

Exporting IID files

An IID file provides specific details about the configuration of your IEDs, communication
parameters, and IED data type templates, and can be used to communicate this information to the
System Configuration Tool.
To export an IID file from Profile Studio:

1. Select Export > Export IID File.

2. In the Export one or more IID Files dialog, select Select Folder and browse to select a
location for your IID file.

3. Select Browse SCD to select your SCD source file.

4. In the IHMI List, enable the checkboxes of the IEDs you want to export back to the system
level.

5. Select Export.

For full export options, see Exporting configuration packages.

Configuring equipment
Equipment refers to Intelligent Electronic Devices (IEDs) that receive data from datapoints. In
Profile Studio, the Equipment pane reflects the IEDs in your project. These are grouped by
subnetworks, such as 8-MMS (IEC 61850), T104, Modbus-Serial, Modbus-IP, etc. The purpose of
the Equipment pane is to configure each subnetwork with its matching protocol.

Logical Node Classes are grouped by subnetwork. The IEDs are grouped by equipment types:
• ITCI: List of gateways

• IHMI: List of HMIs (for example: PC equipment with an EcoSUI view)

• IED: List of devices

For each device, the following columns are present:

Page 198 of 1312 7EN02-0462-03

System Guide Configure

Column Description Action

The devices are
divided by
subnetworks. The
subnetwork name is For MODBUS-IP, select the matching private protocol
Subnetworks
an aggregate of its from the drop-down list.
type and the name
given to it by the
user.
The physical
IP address address of the Double-click to modify.
device (for S-BUS).
The selected product
will affect which
Used as Click to select a product from the drop-down list.
configuration files
are exported.
Displays the device Depending on the subnetwork, this may be editable or
IED type
type. read-only.
When the Used as
column is set to
ECOGTW, the Pidd
Pidd version Double-click to modify.
version drop-down
list becomes
available.
The protocols used
Double-click to modify, or right-click to remove the
for data transfers (for
protocol. Select a protocol from the drop-down list. In
L-BUS or T-BUS).
the Configuration pane Equipment tab, select the HMI
When the Used as
Prot 0 to 7 from the Name drop-down list. On the Protocols tab,
column is set to
name, value, and description are displayed for each
ECOGTW, protocol
parameter. Click the Value field to configure it based on
settings become
instructions in its Description field.
available.

SCADA/LEGACY buttons: Configure protocols, Prot 0 to 7. For T-BUS (Telecontrol Bus protocol),
enable the SCADA button. For L-BUS, enable the LEGACY button.

L-BUS (Legacy Bus protocol) is not an IEC 61850 protocol, but does cover Modbus, T103, etc.

See Exporting configuration packages for information on exporting selected devices in the
Equipment tab.

Configuring datapoints
Datapoints function like tags, providing information published or subscribed by a device. Profile
Studio provides datapoints for human-machine interface (HMI) data acquisition, display,
monitoring, etc. Datapoints must be configured correctly in order to retrieve information readable
by the HMI.

7EN02-0462-03 Page 199 of 1312

Configure System Guide

On the Datapoints tab of Profile Studio, you can configure settings affecting the status of
datapoints.

Datapoint status
On the Datapoint tab, while in Grid view (pictured in the following image), each row represents a
datapoint.
• Gray text in a datapoint row indicates data that cannot be modified, such as Address,
LnClass, etc.
• Black text in a datapoint row indicates data that can be modified, such as the Description field.

• Green text in a datapoint row indicates that the datapoint has an associated profile, is
subscribed, and can be exported.

Datapoints with associated profiles

You can use Profile Studio to manually or automatically associate profiles with datapoints. A
profile determines a datapoint's status, such as open, closed, unknown, whether it is an alarm,
etc. A profile provides an HMI the vocabulary necessary to communicate example states, labels,
units, formats, etc, rather than just an address for the datapoint.

The profiles available for a selected datapoint appear in the Configuration pane Profiles tab.
Types of profiles include:
• SPS: Single Point Status

• DPS: Double Point Status

• MPS: Multiple Point Status

• MV: Measurement Value

• String

• SETPOINTS

• SPC: Single Point Control

• DPC: Double Point Control

Page 200 of 1312 7EN02-0462-03

System Guide Configure

The number of datapoints associated with the profile appear in brackets next to the name of the
profile. An alarm icon indicates an alarmed profile.

In the lower section of the Configuration pane Profiles tab, details appear for the selected profile.
These include:
• Key: States name

• Label: States label

• Archived: Yes or no

• Printed: Yes or no
• Alarm Level: Alarmed (1) or not (0)

• Alarm Delay: Delay in seconds

• Alarm Audible: Yes or no

For more information, see Associating datapoints with profiles.

Datapoint labels and descriptions

You can customize the labels and descriptions for datapoints within SCD files using EPAS or
third-party IEC 61850-compliant system configuration tools. Descriptions that are not customized
prior to import into Profile Studio can also be customized within the Datapoint tab. However,
labels can only be customized using EPAS or similar tools.

Labels and descriptions defined in EPAS or other third-party IEC 61850-compliant system
configuration tools will be read-only on the Datapoints tab and will appear in gray. To customize
descriptions in Profile Studio, see Customizing datapoint descriptions in Profile Studio.

Virtual datapoints
To create formulas using datapoints as inputs, see Creating virtual datapoints.

Spare datapoints
Datapoints have two states: spared or unspared. A spare datapoint is ignored for all treatments,
such as acquisition, calculations, etc. You can spare a datapoint in the SignalList, a CSV file
containing all datapoints, device links, or virtual datapoints. Toggle this on and off by right-clicking
a datapoint and selecting Spare or Unspare from the context menu.

Associating datapoints with profiles

Use Profile Studio to manually or automatically associate profiles with datapoints. For more
information, see "Datapoints with associated profiles" on page 200.

To associate profiles with datapoints

1. In the main menu, click the Auto assign Profiles button .

2. In the Automatic Profiles Association dialog, under Datapoints source, choose one of the
following:

7EN02-0462-03 Page 201 of 1312

Configure System Guide

Project

Datagrid

Selection

3. Under Settings, enable or disable the following:

Assign already assigned datapoints

Assign unassigned datapoints

Unassign already assigned datapoints

4. Click OK.

To manually associate a profile with one or more datapoints

1. In the Datapoints tab, select one or more datapoints.

2. Select the profile from the Configuration pane Profiles tab.

3. Do one of the following:

Click the button.

Drag the profile and drop it onto the datapoint in the list.

To unassign a profile with one or more datapoints

1. In the Datapoints tab, select one or more assigned datapoints.

2. Click the button.

Customizing datapoint descriptions in Profile Studio

Datapoint descriptions that are not customized prior to import into Profile Studio can be
customized within the Datapoint tab.
To customize a description for a datapoint in Profile Studio:

1. With an SCD file loaded into the project, on the Datapoints tab, select the datapoint you
would like to edit.

2. In the Description column, enter a description. An editable description will appear in black.

Associating device links

Device links are signals that permit IEDs to notify IHMIs whether or not they are connected. In
Profile Studio, the Device links tab works with the Configuration pane Device links tab. The
Configuration pane Device links tab displays a list of IEDs, which can be assigned to a node.

NOTE: This feature is only available for an EPAS system.

To associate IEDs with nodes

1. In the Navigation pane, select the electric node you would like to associate.

2. In the Configuration pane Device links tab, do one of the following:

Select an IED and click the Auto Assign IEDs button to automatically assign it to all
electric nodes of the project.

Page 202 of 1312 7EN02-0462-03

System Guide Configure

Select an IED and click the button to assign.

The assigned IED appears in the Device links tab.

To unassociate an IED
1. On the Device links tab, select the IED from the list.

2. Click the button.

Creating virtual datapoints

In Profile Studio, create formulas using datapoints as inputs. These are called virtual datapoints.

NOTE: This feature is only available for an EPAS system.

To create virtual datapoints

SPS2DPS is a DPS type created from an SPS.

1. Select a location in the Navigation pane below the root node.

2. In the Virtual datapoints tab, right-click and choose one of the following from the context
menu:

SPS

SPC

DPS

DPC

MPS

MV

SPS2DPS

The virtual datapoint appears in the Virtual datapoints tab.

To define virtual datapoint inputs and formulas

1. Select your virtual datapoint.

2. In the Configuration pane Virtual datapoints tab, click the Edit inputs button.

3. In the Information dialog, click OK.

4. In the Datapoints tab, select a datapoint with an associated profile (in black).

5. Click the button. The datapoint is associated with the virtual datapoint you created.

6. Click the Edit formula button.

7. In the Virtual datapoint editor, define a formula to calculate the virtual datapoint's value from
the associated datapoint.

8. On the Signal quality drop-down list, select one of the following:

AlwaysValid: The formula is always valid.

ValidIfAllSignalsAreValid: The formula is valid when all signals (input) are valid.

7EN02-0462-03 Page 203 of 1312

Configure System Guide

ValidIfOneSignalIsValid: The formula is valid when one of the signals (input) is valid.

9. Click OK.

Generating reports
Generate a report file to reflect your current project's status in Profile Studio.

NOTE: This feature is only available for an EPAS system.

To generate a report
1. In the Menu bar, click the Generate reports button.

2. Do one of the following:

(Optional) On the EPCM Connection page, enter your Schneider Electric credentials
and click OK.

On the EPCM Connection page, click Skip.

3. On the Project information page:

Select a project type from the Project type drop-down list.

Enter your information into the Properties number and Task force fields.

4. Click Next.

5. On the Select reports page, select one or more of the following options to populate your
report:

Datalist: List of inputs/outputs

Goose: List of publishers/subscribers

Network: SCD network analysis

Specifications: SCD specification analysis

6. Click Next.

7. If you selected Goose, Network, or Specifications, proceed to step 8.

If you selected Datalist:

Page 204 of 1312 7EN02-0462-03

System Guide Configure

Configure the options on the Reports settings page, on the Excel Properties tab:

Substations List Creates a new sheet displaying the substation list.

Voltage Levels Creates a new sheet displaying the voltage level
List list.
Profiles List Creates a new sheet displaying the profile list.
One Excel Sheet
Creates a new sheet per subnetwork.
per SubNetwork
Sheets
One Excel Sheet
Creates a new sheet per IED.
per IED
One Excel Sheet
Creates a new sheet per bay.
per Bay
One Excel Sheet
Creates a new sheet per bay template.
per Bay Template
Export column for Creates a new column that displays test results.
Tests results (Applies to bay sheets only.)
Columns
SignalList Cell Colors every second line in the IEC Equipment and
color IED sheets section of the report.
Displays information with double point status
Display two lines
Settings (DPS) on two separate lines. (Applies to bay
for double points
sheets only.)
Types to be displayed on controls Select the datapoint types to include. (Applies to
division bay sheets only.)

Information Group Groups sections for bay sheets.

Group & Freezes the sheet header. (Applies to bay sheets
Freezpanes Freezpanes
only.)

Configure the options on the Datapoints Properties tab:

Types to be displayed Select the types of datapoints to display in the

on status division status division. (Applies to bay sheets only.)
Status
Displays spared datapoints in the status
Export Spared Signals
section.
Types to be displayed Select the types of datapoints to display in the
on measurements measurement section. (Applies to bay sheets
division only.)
Measurements Displays spared datapoints in the
Export Spared Signals
measurement section.
Export Low Threshold Displays low threshold datapoints.
Export High Threshold Displays high threshold datapoints.
Types to be displayed Select the types of datapoints to display in the
on strings division strings section. (Applies to bay sheets only.)
Strings
Displays spared datapoints in the strings
Export Spared Signals
section.

7EN02-0462-03 Page 205 of 1312

Configure System Guide

Types to be displayed Select the types of datapoints to display in the

on controls division Controls section. (Applies to bay sheets only.)
Controls
Displays spared datapoints in the Controls
Export Spared Signals
section.

8. Click Next.

9. On the Generate Reports page, select your language and a destination on your harddrive for
the report.

10. Click the Generate button. Your generated XLSX file is located in the harddrive destination
specified in Step 9.

Including enum tag state values for export

When you export a configuration package using Profile Studio, one of the files contained within
the package is the equipment.profiles file. The equipment.profiles is an XML file that
contains descriptions of the capabilities of devices and tag (datapoints) definitions that Power
Operation Studio will use. Depending on the enumtype, which is defined by the Substation
Configuration Description (SCD) file, a tag could contain multiple enum tags.

Use Profile Studio to configure which enum tag state values matter to you and will, therefore, be
included in your equipment.profiles file.
To include enum tag state values in your export package:

1. After importing into Profile Studio, open the SCD file.

2. In the SCL > DataTypetemplates > EnumTypes section, note the tag types you want to
include in the equipment.profiles file.

3. In Profile Studio, go to Settings > Open .config location.

4. In a text editor, open the [your project name].config file.

5. Next to "EnumTypeIds", enter the tag values you want to include in the
equipment.profiles file. To add multiple tags, separate the tags using a comma.

In the following example, ["Dbpos"] and ["ModKind"] are added by the user:

1 {
2 "EnumTypeTagsWhitelist":
3 {
4 "EnumTypeIds":["Dbpos"],["ModKind"],
5 }
6 }

6. Save the file.

7. In Profile Studio, choose Project > Export full configuration package.

For more information, see Exporting configuration packages.

Your equipment.profiles file will contain your included enum tag state values.

Exporting configuration packages

In Profile Studio, check your project for errors and completeness prior to export.

Page 206 of 1312 7EN02-0462-03

System Guide Configure

Validate a project
• In the main menu, click the Validate configuration button.

The Check errors tab appears in the Main View pane if errors are found.

A completed project can contain:

• Assigned profiles that exist.

• Datapoints that exist, are associated with profiles, have unique descriptions.

• SignalList, a CSV file containing all datapoints, device links, or virtual datapoints.

• Device links that exist, are associated with profiles, have unique descriptions.

• Virtual datapoints that exist, are associated with profiles, have unique descriptions.

• Virtual datapoints with inputs that exist.

After configuration, export a configuration package in the form of a ZIP file.

HMI used Package contains:

• Your SCD file, provided by EPAS-E, which does not get modified.

• Your SignalList in the form of a CSV file, which contains equipment and
devices with IP addresses and servers.
EcoSUI • Your Equipment.profiles file, an XML file containing descriptions of the
capabilities of your devices for acquisition. This profile file defines tags
(datapoints) to be used by Profile Studio or to be delivered to Power
Operation Studio.
• EcoSUI Pack (all of the files included in the EcoSUI package)
EcoGTW • A ScadaList file containing a list of datapoints associated with profiles for
transmission (T-BUS for EcoGTW only).
• Your SCD file, provided by EPAS-E, which does not get modified.

• Your equipment.profiles file, an XML file containing descriptions of the

Power
capabilities of your devices. This profile file defines tags (datapoints) to be
Operation
used by Profile Studio or to be delivered to Power Operation Studio.
• Your device profiles CSV file.

You can export a configuration package for all equipment, or a configuration package for selected
equipment only.

Export modified configuration packages

1. In the main menu, click the Export configuration full package button.
If one or more of your exported datapoints share the same description, the SCL export
options dialog appears. Enable or disable the following options:

Ignore check errors: Enable to ignore errors found during validation.

Spare duplicate description: Enable to exclude the duplicate description(s).

Rename duplicate description: Enable to rename the duplicate description(s).

7EN02-0462-03 Page 207 of 1312

Configure System Guide

2. Click OK.

3. Select a location for your finished package.

Your ZIP is exported to the selected location.

Export selected configuration packages

You can import your configuration package into Power Operation Studio by loading it into the I/O
Device Manager. Modified IHMIs are exported.

1. In the Equipment tab, select the IHMIs you wish to export by right-clicking the device name.
Hold down CTRL to select multiple devices.

2. Choose Export equipment configuration package from the context menu.

3. Select a location for your finished package.

Your ZIP(s) are exported to the selected location.

See Devices for information about importing devices from a CSV file.

Before importing into Power Operation Studio, you will need to open your CSV file and add the
absolute path of the SCD file to the PrimarySclFileName column. You also have the option of
modifying the Cluster and Primary IO Server Name columns at the same time. See Create a CSV
file to add multiple devices for more information about the columns in your CSV file.

Comparing templates
In Profile Studio, use the Bay Templates tab to compare templates. Templates are derived from
bay modeling and are automatically created when an SCD file is imported.

The Templates pane displays a list of templates available in your IEC 61850 project.

Compare templates
• Drag a template from the Templates pane to the green Drop your templates here area.
Repeat this process in the additional area.

The compared templates display XML in one of the following colors:

Configuring Profile Studio settings

Use the options under the Settings button in the Main menu to configure Profile Studio.

Display all datapoints from the parent node

• Select Settings > Extended view.

Include globally unique identifiers in export

When exporting, the signalList file will include the associated globally unique identifier (Guid) for
each datapoint.
• Select Settings > Export signalList with Guid.

Page 208 of 1312 7EN02-0462-03

System Guide Configure

Export scadaList file with only associated profiles

When exporting a configuration package for EcoGTW, this option will produce a scadaList file
containing only datapoints with associated profiles.
• Select Settings > Export scadaList (Only full configured datapoints).

Include spared datapoints in export

When exporting, the signalList file will include spared datapoints.
• Select Settings > Export signalList with Spared.

The Profile Editor

The Profile Editor lets you create device types, device profiles, and set up projects.

NOTE: To avoid potential communication errors, use the Profile Editor to create all custom tags
that will communicate with equipment.

The Profile Editor consists of the following tabbed panes:

• Define Device Type Tags – Use this pane and its screens to add and edit information for
real-time, onboard alarm, control and reset tags and to create and edit device types. See
"Define Device Type Tags" on page 212 for complete instructions.

Power Operation uses the IEC 61850 tag-naming convention to create tags that measure
device quantities. Although most of the tags you will use are already entered into the system,
you can add custom tags. For more information, see "About tags" on page 234.
• Create Device Profiles – Use this pane and its screens to add and edit individual profiles for
specific devices. A device profile is a subset of the possible variable tags, alarm tags, and
trend tags for a particular device type. See "Create Device Profiles" on page 242 for complete
instructions.
• Set Up Project – Use this pane and its screens to bring together all of the system attributes
for a single customer or installation.

For example, the customer installation will include a certain combination of device profiles
(depending on the devices installed at the site). The project allows a specific unit template to
be applied, converting units (such as watts) into units used by the customer (such as
megawatts). This causes tags to display in the converted format. Projects also allow you to
rename tags to suit a customer’s needs (for example, Current A could be renamed to Current
Phase A). See "Set Up Projects" on page 260 for details.

TIP: For more information on how to use the Profile Editor screens, click the help link (?) at the
top of the page. The help file will open to instructions for the Profile Editor screen you are
viewing.

Related references:
• "Profile Editor typical workflows" on page 177

• "Profile Editor main menu options" on page 180

7EN02-0462-03 Page 209 of 1312

Configure System Guide

Launch the Profile Editor

NOTE: To avoid potential communication errors, use the Profile Editor to create all custom tags
that will communicate with equipment.

There are several ways to open the Profile Editor:

• From the Start menu:
Start > All Programs > Schneider Electric > Power Operation > Config Tools > Profile
Editor.

Start > Apps > Schneider Electric > Profile Editor.

• From the desktop: Double-click the Profile Editor shortcut.

• In Power Operation Studio > Topology activity, click I/O Devices > Device Profile Editor.

The Profile Editor screen displays with the Set Up Projects tab selected. There are two other
tabs, used to create device type tags and profiles.

Locked and custom icons

Two icons may appear to the right of the Add / Edit button on some screens: the locked icon and
the custom icon.

The Locked Icon :

Page 210 of 1312 7EN02-0462-03

System Guide Configure

This icon indicates that the selected file (e.g., device type, profile, or project) cannot be edited. All
standard device types (for example, Circuit Monitor 4000, MicroLogic Type P, Power Meter 800)
are automatically locked; they cannot be unlocked.

The Custom Icon :

This icon indicates that a device type or profile is user-created. It may have been created new,
created from an existing device type or profile, or created by editing an unlocked custom device
type or profile.

Set the screen resolution

Depending on the screen resolution you use, some of the Profile Editor screens may take up the
entire viewing area. We recommend that you use at least 1024 x 768 resolution. You can also
auto-hide the taskbar to provide more room.

TIP: For more information on how to use the Profile Editor screens, click the help link (?) at the
top of the page. The help file will open to instructions for the Profile Editor screen you are
viewing.

About device profiles and tags

By default, Power Operation includes a large number of device types and their associated tags.
You can use these device types as is or as templates to create your own custom device types.

Before you create your own device types, review the topics in this section. The device types and
tags that you want may already be created for you.

Reviewing default device types and tags

By default, Power Operation includes a large number of device types and their associated tags.
Before you create custom device types and tags, verify that the device type does not already exist
in Power Operation.

To review the default device types and tags:

1. Open the Profile Editor.

2. On the Define Device Type Tags tab, select a device type name from the Device Type
Name drop-down list.

The available tags display in the body of the page. There are several sub-tabs for real-time
tags, onboard alarms, control tags, and reset tags. The tags that are selected for the device
type display there.

3. If you do not find the device type or tags that you need, you can:

"Create custom device types" on page 221

"Creating custom tags" on page 224

Supported device types and protocols

When you install Power Operation, you are prompted to choose the drivers that you will use. A
certain number of generic drivers are installed by default (including PowerLogic device types),
and you are not prompted for them. Device types and protocols supported in Power Operation

7EN02-0462-03 Page 211 of 1312

Configure System Guide

are:
• Generic MODBUS (includes BCPM and any device, such as a PLC or UPS, that
communicates via MODBUS). When adding a controllable device in the Profile Editor, such
as a circuit breaker, use the “Controllable Device” driver; otherwise, use the “Generic Power
Device” driver. For JBus devices, select Generic JBus Device.
• Sepam 20, 40, and 80 Range, 2000

• Masterpact MicroLogic 5P and 6P, A, H

• Compact NSX (MicrologicV)

• CM2000

• CM4000 series

• PM650

• PM800 series

• PM5000 series

• PM700 series

• ION protocol devices

• IEC 61850 protocol devices

• IEC 870-5-104

• DNP3

• BCPMA (branch circuit power meter, full feature support)

• CSI SER (Cyber Sciences SER)

• ProTime 100 SER (Monaghan Engineering)

Define Device Type Tags

Define Device Type Tags and its related screens are used to define the following device-related
data: custom tags, device types and device type categories, and base units/conversions:

Page 212 of 1312 7EN02-0462-03

System Guide Configure

On the Profile Editor > Define Device Type Tags tab, follow these general steps to add tags and
devices to your system:

1. Manage the units and unit conversions that you will use (such as amperes into
milliamperes), see Add or Edit a Base Engineering Unit or Conversion.

2. Add and edit custom tags, see "Setting up custom tags" on page 230.

3. Add or edit device types, see "Managing device types" on page 217.

4. Establish device type categories and subcategories, used in reporting, see "Printing the
.CSV file" on page 221.

5. Edit tag addresses, see “"About tags" on page 234”.

Define Device Type Tags tab

The Define Device Type Tags tab displays device types and the tags that may be associated
each device type. This includes real-time, onboard alarm, control, and reset tags. Most of the
fields on this tab are read only (they can be changed on other screens). The following table
describes this tab. The tags listed assume that Advanced Properties has been checked. Not all
elements appear on every sub-tab.

7EN02-0462-03 Page 213 of 1312

Configure System Guide

Field Name/Valid Entries Comments

Each device type includes a different number of tag
categories, which also changes the list of tags that
Device Type Name (Select the display.
device type)
The device list includes the default device types, as well
as any that have been created for this system.
Provides a means of adding new device types and editing
Add / Edit button: Click to open
custom device types (user-created device types). Also
the Add / Edit Device Type
provides a means of adding new custom tags and editing
screen.
existing tags.

Locked/Custom icons: Locked icon indicates that the list of selected tags cannot
be edited. Custom icon indicates that the device type was
created by a user. See "Locked and custom icons" on
page 210 for complete information.
Tag groups (left-hand pane)
Each tag belongs to a group. The group is determined
when the device is added to the system. For custom tags,
this is on the Add/Edit Custom Tags screen. Tags for
standard device types are pre-determined and cannot be
changed.)

Select a tag group; the tags NOTE: If a tag group displays in red copy, there is at
included in that group display on least one address that is not valid for the tag to which it
the right. is assigned. To correct this issue, click the tag group,
ensure that Display Advanced Properties is selected,
then scroll down through the tags in the right-hand
column. The tags that have invalid addresses will have
the “Edit...” displayed in red. Click this field to open the
Edit Address page; correct the errors in the address.

Tag tabs: Real Time, OnBoard Alarm, Control, and Reset

Click a tab to view the tags of that type that are included for the selected device type.

If the device type is not locked, you can use the Add/Edit Device Type screen to edit the list
of tags.
This is the tag name, hard-coded for standard tags. For
Tag Description (all tag
custom tags: The name is from the Tag Name field in the
types)/Display only
Add/Edit Custom Tags screen.
Lists the abbreviation, added when creating the
Units/Display only
engineering unit template.
Tag name that conforms to IEC61850 standard. See
IEC Tag Name/Display only
"About tags" on page 234 for more information.

Page 214 of 1312 7EN02-0462-03

System Guide Configure

Field Name/Valid Entries Comments

Type (Real Time only)/Display
Displays the data type chosen when the tag was created.
only
Address (not Control tags)/
Displays the address information for this tag, including
To edit, click the Edit Address elements such as type of register, number of registers,
link. and scaling and bitmasking data. "About tags" on page
234 for a detailed description of address construction.

For a control with one command, writing a 1 to the tag will

cause the command to occur. (This option is greyed out.)

Normally Closed (Control tags For a control with two commands that is either static or
only)/ normally open, writing a 1 to the tag will cause the first
command to occur; writing a 0 will cause the second to
Check the box to invert the occur. (Check box not checked.)
functionality of the control. See
description. For a control with two commands that is normally closed,
writing a 1 to the tag will cause the second command to
occur; writing a 0 will cause the first command to occur.
(Check box checked.)
Provides the means of changing the elements of an
unlocked real-time tag address (for example, the number
Edit Addr/Click to display Edit of registers, their numbers, and whether they are
Address screen. (Real Time consecutive).
and Onboard Alarm only)
See "Editing tag addresses" on page 224. for detailed
information.
This field contains first register used to store this tag. If
there are additional registers, they are indicated in the
address. The total number of registers is listed in the Num
Registers column. This field allows you to verify and/or
Register 1/Display only (Real change the value of Register 1 without having to open the
Time tags only) Edit Address screen.

NOTE: If you enter a number that is not compatible with

other address settings, you are prompted to go to the
Edit Address screen.

Num Registers/Display only

Displays the number of registers used by this tag.
(Real Time tags only)

7EN02-0462-03 Page 215 of 1312

Configure System Guide

Field Name/Valid Entries Comments

After you change formatting for a tag and move the cursor
to another field, you are asked whether you want to open
Formatting/Select the format
the Address Editor. If you click No, the format is
type from the drop-down list
unchanged; if you click Yes, the Edit Address screen
(Real Time tags only)
opens for you to enter the appropriate changes for this
tag. See "Editing tag addresses" on page 224.
This is entered in the Edit Address screen, but it can be
edited here. It is the register used to read the value for
Scaling Register/View or enter scaling.
the register number (Real Time
tags only) NOTE: If you enter a number that is not compatible with
other address settings, you are prompted to go to the
Edit Address screen.

Functional Address/Display If you have added a functional address for this tag, it
only (Real Time, Onboard displays here. To add or edit this address, use the Edit
Alarm, Control, and Reset tags) Functional Address field.
Typically used for data concentrators, the functional
address is a means of entering the individual data points
needed to define multiple addresses. Entered as a
formula (must be in C#), it will contain the variables the
user must enter when the block is instantiated by the I/O
Device Manager.
Edit Functional Address/Add
A simple example:
the code for the address
Address =

"T:MV;m:" + (startingpoint + 1005).ToString() + ";L:P:22"

You would then define "startingpoint" when instantiating

the profile in the I/O Device Manager.
Tag ID/Display only/Display Assigned by the system when the tag was created. If this
only is a custom tag, it will be a negative number.
Category Type (real-time only)

Utility Type (real-time only) Each of these types is a real-time filter, added when the
Statistical Type (real-time only) tag was created. See for more information.

Quantity (real-time only)

Page 216 of 1312 7EN02-0462-03

System Guide Configure

Field Name/Valid Entries Comments

Categorization (onboard alarm
only)

Subcategorization (onboard
alarm only)

Alarm Type (onboard alarm Each of these is an onboard alarm folder, added when the
only) tag was created. See for more information.

Alarm Group (onboard alarm

only)

Alarm Level (onboard alarm

only)

Managing device types

Use the Add / Edit Device Type screen to begin adding, editing, or deleting a device type from the
system. See "Edit a device type" on page 219 and "Delete a device type" on page 220 for
instructions on editing or deleting device types.

To open Add / Edit Device Type:

In Profile Editor, click Define Device Type Tags, then click Add / Edit (to the right of the Device
Type Name field.)

The following table describes the parts of the Add / Edit Device Type screen.

Field Name Valid Entries Comments

Click to add a device type that is not based on an

Create New
existing type.

Click one of the

Create From Click to copy an existing device type.
radio buttons to
Edit Existing select the Click to edit an unlocked device type.
action you want
to take. Click to delete an unlocked device type and any
Delete Existing
associated custom profiles.

Device Type (to Create Select the device type that you want to create from,
select type
From/to Edit/ to Delete) edit, or delete.
Active when you choose Create From. Check this
box if to copy the addressing of the “from” device.
Copy Addressing This gives each tag in the new device type the same
address string as the matching tag in the “from”
device.

7EN02-0462-03 Page 217 of 1312

Configure System Guide

Field Name Valid Entries Comments

Type or select
the name:
If creating a device type, type the name. If editing a
maximum 32 device type, the device type that was selected for
Device Type Name
characters, editing displays here. You can change the name
here.
do not use \ / : *
?<>|
To create categories, see "Printing the .CSV file" on
page 221

Choose the In addition to predefined categories, you can add

Device Category category for custom categories. See "Managing device type
this device. categories" on page 221 for instructions. Categories
are used in the Device Creation wizard, and are a
means of shortening the list of devices you must
view.
Default options are Monitoring Device, PLC, or
Protection Device. Depending on the device you
Choose the select at the top of the page, this field is filled in for
subcategory for you.
Subcategory
this device, if
needed.
As with categories, subcategories are created in the
"Printing the .CSV file" on page 221 screen.
Predefined drivers are created for all PowerLogic
compatible devices, though you may need to use
these drivers for multiple device types. For example,
Select the you would use the CM4000 driver for a CM3000.
Driver driver for the
device type. Use the Generic Power Device driver for third-party
devices. The Controllable Device driver is currently
not used. Use Generic JBus Device driver for JBus
devices.
(Active only in
Edit mode)

Click to display
Display Associated a list of profiles This list shows the profiles that are associated with
Profiles that are the selected device type.
associated with
the selected
device type.

Page 218 of 1312 7EN02-0462-03

System Guide Configure

Field Name Valid Entries Comments

This list includes all tags that have been added to the
system, standard tags as well as custom tags that
IEC Tags n/a
you have added. Tags are listed in their groups
(such as 100ms, Onboard Alarm, Power Factors).
You can move single tags or entire tag groups. They
Select tags
must be moved one at a time (cannot Shift+click to
from Tags; click
select).
Selected Tags the right arrow
to move them NOTE: You cannot deselect tags for a device type
to this box. if that device is associated with a device profile.

Live when creating or editing a tag. Opens the

Add/Edit Custom Tags screen. See "Edit a custom
Click to begin tag" on page 234 for instructions.
Add/Edit Custom Tags adding a
custom tag. If you add a custom tag here, you are prompted to
save the device type. After adding the tag, you have
the option of adding that tag to the device type.

Edit a device type

If you want an edited version of a locked device type, you must create a new device type from it.
Certain “standard” device types can be used to create new types, but they cannot be deleted.
Examples: Circuit Monitor 4000, Power Meter 800, and Sepam S42.

NOTE: You cannot edit any locked device type. When a device type is locked, the locked icon
displays on the Define Device Type Tags tab:

To edit a device type:

1. Open Add / Edit Device Type: In Profile Editor, click Define Device Type Tags, then click
Add / Edit (to the right of the Device Type Name field.)

There are two ways to edit device types:

1. In Define Device Type Tags, select a device type and then make the following changes:
a. Edit the functional address (see "Edit functional addresses" on page 223).

b. In Real Time Tags you can edit the address (see "Editing tag addresses" on page 224)
and choose a different format.

2. In Define Device Type Tags, select the device type you want to edit, then click Add / Edit.
Follow through the screens to edit additional information:
a. In the Device Type Options box, click Edit Existing.

b. Click the Device Type to Edit list to display the Select Device box. Select the device
type that you want to edit.

c. You can change the device type name, category, subcategory, and driver.

d. Select tags and tag groups and move them into or out of the Selected Tags list.

7EN02-0462-03 Page 219 of 1312

Configure System Guide

e. If a device type is associated with a device profile, you cannot deselect tags.

f. After all of the appropriate changes are made, click Save to save your current settings.

g. To create additional custom tags, click Add / Edit Custom Tags; otherwise, click Save
& Exit to save your settings and close the window.

If you add a tag to a group that is already included in a device type, you must then individually add
the tag to that device type.

Delete a device type

Standard device types do not display in this option because you cannot delete them.

To view a list of profiles associated with a device type:

1. Switch to the Edit Existing view, then select the device type you want to delete.

2. Click List Profiles associated with this Device Type to display all associated profiles.

To delete a device type:

1. In Define Device Type Tags, click Add / Edit.

2. In the Device Type Options box, click Delete.

3. From the drop-down list, select the device type you want to delete (the list includes only
unlocked device types; you cannot delete any of the standard device types).

4. Click Delete. A list of associated profiles will appear in the Confirm prompt. Click Yes to
delete the selected device type and any associated profiles.

Assign tags to generic I/O points

Device types have default tags that have the appropriate formatting and addressing assigned for
all the generic I/O points. It may be necessary to redefine a generic I/O point by assigning it to a
tag that has a specific meaning.

Example 1: The Branch Circuit Monitor 42 has been configured to read 42 current channels. To
assign channel 1 to Current A:

1. From the Branch Circuit Monitor 42 device type, choose the “Ch.01 Current tag.”

2. Note the addressing and formatting for the tag.

3. Locate and add the standard tag that you want to assign to this channel. In the example
above, you would add “Current A.”

4. Edit the address of the Current A tag to match the address of Channel 1.

Example 2: If the Sepam I11 / I12 have been configured to represent circuit breaker position, you
may choose to redefine the tag name:

1. From the Sepam 40 Series device type, choose tags “Input Status I11” / “Input Status I12.”

2. Note the addressing and formatting for each tag.

3. Locate and add the standard tag that you want to assign to these I/’O points. In the example
above, you would add “Device Closed.”

Page 220 of 1312 7EN02-0462-03

System Guide Configure

4. Edit the address of the Device Closed tag. In order to create the “device closed”
functionality, you must combine inputs 11 and 12 into an enumerated status (choose the
Enumerated Status logic code for the indicated address for I11 and I12),

Create custom device types

A custom device type is any device type that is not included in the standard Power Operation set
of devices. Typically, this is a third-party device type that communicates through a protocol such
as IEC 61850 or DNP3. Each protocol requires a slightly different process.

The help file describes the process for each of these protocols:
• IEC 61850

• Modbus third party

• DNP3

• Composite device type

To create a new custom device type:

1. Open the Profile Editor.

2. In the Define Device Type Tags pane, click Add / Edit.

3. In Add/Edit Device Type, complete the information for the device, following instructions in
the help file for the protocol the device uses.

Printing the .CSV file

For each device type, device profile, or project, you can create and print a CSV file that includes
the following data:

Type of File Data Included

Device Type tag descriptions, IEC tag names, type, and address
Device Profile tag descriptions, IEC tag names
Project data profiles and custom tag names included in the project

To create and print the CSV file:

1. Display the device type, profile, or project for which you want the file. For example, to create
a CSV file for the Sepam 42 Full device profile, select the Create Device Profiles tab and
choose Sepam S42 Full from the drop-down list.

2. Click File > Create CSV File.

3. In the Save As window, choose a location for the file and optionally rename it. Click Save.

The file is created in the location you specified.

4. View and print the file in Microsoft Excel.

Managing device type categories

Use Set Up Device Type Categories to add, edit, and delete categories. These categories are
used in the I/O Device Manager to logically group the list of profiles that display, and to make them
easier to locate.

7EN02-0462-03 Page 221 of 1312

Configure System Guide

When you add device types in the Add/Edit Device Type screen, you associate a category and
subcategory with each device.

To view the Set Up Device Type Categories screen, click Settings > Set Up Device Type
Categories.

The following table describes the parts of this screen. Detailed instructions are after the table.

Field Name Valid Entries Comments

Create New Click to begin adding a new device type that is not
based on an existing type.

Click to begin editing the category or subcategory

Edit Existing
name.
Click to begin deleting a category. You cannot
Delete Existing delete a category that is associated with a device
Categories
type.
Options box
If new: Type the name.

If editing or deleting, select the name from the

drop-down menu.
Category Name
Predefined categories do not display. Currently,
there is one predefined category: Schneider
Electric.
If new: Type the name.

If editing or deleting, select the name from the

drop-down menu.
As with categories,
Subcategories You cannot delete a subcategory that is
you can create new,
Options box. associated with a device type.
edit existing, or delete.
Predefined subcategories do not display.
Currently, the predefined subcategories are:
Protection Device, Monitoring Device, and PLC.

Adding a category or subcategory

To add a category or subcategory:

1. Click Create New in the appropriate box (Categories or Subcategories).

2. In the Name field, type the name of the new category or subcategory.

3. Click OK to save the new entry and close the screen.

Editing a category or subcategory name

To change the name of a category or subcategory:

1. From the appropriate box, click Edit Existing.

2. From the dropdown menu, select the category or subcategory that you want to edit.

Page 222 of 1312 7EN02-0462-03

System Guide Configure

3. Type the new name for this category or subcategory.

4. Click Save to make the change, or click Save & Exit to save changes and close the screen.

Deleting a category or subcategory

Predefined categories and subcategories, or those associated with a device type, do not display
for deletion.

To delete a device type associated with a category or subcategory:

1. Change to the Edit view

2. Select the category or subcategory, then click List Device Types.

3. Note the device types and go to the Add / Edit Device Types screen.

4. Change the category or subcategory on that page.

5. Return to the Set Up Device Type Categories screen to delete the category/subcategory.

To delete a category or subcategory:

1. From the appropriate box, click Delete Existing.

2. From the dropdown menu, select the category or subcategory that you want to delete.

3. Click Delete.

4. Click Yes to confirm the deletion.

5. Click Save to save the change, or click Save & Exit to save changes and close the screen.

Edit functional addresses

Use this feature to add variables to addressing. You can re-use a variable by copying and pasting
parts of it into other addresses, then making changes to the code for use in other tags. You will be
prompted for these variables in the I/O Device Manager.

To access the Edit Functional Address screen, click Edit Functional Address for a real time
tag, onboard alarm tag, control tag, or reset tag. The fields on this screen are used in this way:
• Tag Name and Original Address: These fields display from the tag you selected; you
cannot edit this information.
• Device Variables: Click New to begin adding new variable properties. The following fields
become live:
• Name: This name must be in format %NNN%, where NNN includes only letters or
underscores.
• Description: This required field is free-form. It displays in the I/O Device Manager and will
help you ensure that you have the correct information entered.
• Regular Expression: You can use one of the pre-defined expressions, or you can create
your own
• Test Value: This will become the default in Citect; use it here for testing the new address.

• Help: Use this optional field to add more definition to this address. It displays in the I/O
Device Manager.

7EN02-0462-03 Page 223 of 1312

Configure System Guide

• Code Body: Enter the code in C# to define the action you want to take place.

• Return: Type the return statement that you want from C# code. It might look like:

string.FormatFormat("SomeString{0}SomeOtherString", someVariable)
• Result: Click Test in the lower right corner of the screen. If there is a compile error, check
your C# code. Otherwise, the result displays. Verify that it is what you wanted.

Creating custom tags

Power Operation comes with most of the tags that are needed for each device type. However, you
can create custom tags to assign to device types and device profiles. A custom tag is a unique
measurement that is assigned to a device type, or is an existing tag for which the tag address is
changed. You can also edit address attributes for any tag.

NOTE: To avoid potential communication errors, use the Profile Editor to create all custom tags
that will communicate with equipment.

To create a custom tag:

1. In Profile Editor > Define Device Type Tags pane, click Add/Edit and then click Add/Edit
Custom Tags.

2. Enter the information for the new tag.

TIP: On the Add / Edit Custom Tags screen, click the help link (?) at the top right of the screen.
The help leads you through adding, editing, or deleting custom tags.

For more information on adding custom tags, see:

• "Setting up custom tags" on page 230

• "Edit generic tag addresses" on page 230

Editing tag addresses

Use the Edit Address screen to edit the attributes of a single tag address. If a device type is
locked, you cannot edit any of its tag addresses; they will be grayed out. A thorough discussion of
IEC 61850 tags and their construction is included in "About tags" on page 234 and "About logic
codes" on page 240.

NOTE: Case and order are critical in the tag address. Be careful to observe the exact address
order. For address order, see "About logic codes" on page 240. Also, be sure you use the correct
case. For example, use M for register numbers in hexadecimal, and use m for register numbers
in decimal.

To view the Edit Address screen:

1. In the Profile Editor, click Define Device Type Tags.

2. Choose the device type, then click the Edit... field for the tag that you want to change.

The Edit Address screen is different for real-time and alarm tags.

Each type of tag (real-time, onboard alarm, reset, and control) is described separately in the
following tables.

Page 224 of 1312 7EN02-0462-03

System Guide Configure

Real-time tag addresses

The following table describes the fields of the Edit Address screen for real-time tags.

Field Name Entry Comments

You can edit this field in the Add/Edit Custom
Data Type For display only
Tags screen.
High, Normal, or Low You can edit this field either here or in the
Priority
Logic Code: Add/Edit Tag screen.

The logic code list depends on the Data Type

Select the logic code for
Logic Code for this tag. For more information about logic
this tag.
codes, see "About logic codes" on page 240.
Display Click the radio button for the way you want to
hexadecimal/decimal
Registers in: view register information.
Choose the type of module in which the tag is
Module Select module
used. Used for Micrologic at this time.
Select the type of register that is to be written
Register Type Select register type
or read.
Select the total number of
registers for this address
(1-10).
Number of Enables for editing the appropriate registers
Registers Is Consecutive, check if in the lines below.
the registers are to be
consecutive (determined
in the logic code).
A fixed scale is the actual value of the scale. A
register scale is the register address where
the scale is held.
Fixed
Click the radio button for The value will be scaled in this manner: Value
Scale/Register
the correct type of scale. x 10x
Scale
where X = the scale.

Scales can only be –10 to 10.

7EN02-0462-03 Page 225 of 1312

Configure System Guide

Field Name Entry Comments

Conversion factors are used for straight
multiplication with the value. The conversion
factor could also be changed in the Add/Edit
Units screen (Settings > Select Units >
Enter the multiplier to Add/Edit Units.
Conversion
convert the base units to
Factor Conversion factors take this form:
the desired conversion.
####E##. For example,

123E-2 becomes 123x10-2

which becomes 1.23.

y = the final value reported by PLSCADA
b = the offset
m = the conversion factor
x = the original value in the meter
Offset y = ,x + b b = rarely used, mainly in temperature
conversion

The offset is added to the final value (after the

conversion factor is applied).
Be aware of whether you chose hexadecimal
Register 1-4 Enter the register number.
or decimal. Use the same format here.
When all bits match exactly the pattern in the
register, the status is True. When any one bit
For digital input/output does not match the pattern in the register, the
tags: Set the bits to 1 or 0 status is False.

Bitmask for to match the pattern for

NOTE: On PM8s and CM4s, there is a
Register 1-4 “True” in the device
device-specific format, DIgIn and DigOut. In
register.
each case, you must first specify the
indicator register (which becomes the first
register). The second register will have the
mask.

Will turn False to True or vice versa; typically

Invert Result Check this box to invert.
used for Normally Open or Normally Closed.

Onboard alarm tag addresses

The following table describes the fields of the Edit Address screen for onboard alarm tags.

Field Name Entry Comments

This is the tag name, which cannot be
Tag Name For display only
changed.

Page 226 of 1312 7EN02-0462-03

System Guide Configure

Field Name Entry Comments

This is the file number for the alarm file on
File Number Select the number. the device.(Sepam has no file number;
enter 0.)
Choose the type of module in which the tag
Module Select the module.
is used. Used for Micrologic at this time.
This unique identifier must be used to
ensure that alarms will annunciate
correctly. For CM4, PM8, PM5000, and
Unique ID Choose the identifier. Micrologic, the unique ID must be decimal.
For Sepam, the unique ID is the coil bit
address that indicates the alarm; it must be
in hexadecimal.
Check this box if you want to display the ID
Hexadecimal check box
in hexadecimal, rather than decimal.
Check if this tag has a unique sub-identifier
Has Unique Sub ID check box (Micrologic, CM4000, PM800, and
PM5000 devices).
Enter the unique sub-identifier. Active only
Unique Sub ID Enter the Sub ID.
if Unique Sub ID box is checked.

Reset tag addresses

NOTE: Once the tag is set up, writing a 1 to the tag will cause the “write” to occur.

Standard device types include some pre-defined resets. These pre-defined commands cause
proprietary functions within the device. Do not edit these commands.

To add a custom reset that will operate by writing to a register, do the following:

1. From the Add/Edit Custom Tags screen, set the Group to Resets and the Data Type as
Digital.

2. Save the tag.

3. Add the new tag(s) to the appropriate device type(s).

4. From the Define Device Type Tags tab, locate the tag and click Edit.

The following table describes the fields of the Edit Address screen for reset tags.

Box Name Field Name Comments

Command Type The Command Type and Command to Edit are
Tag Information
Command to Edit already selected.

7EN02-0462-03 Page 227 of 1312

Configure System Guide

Box Name Field Name Comments

Data Type: for display You can edit this field in the Add/Edit Custom
only Tags screen.
Data Information
Priority: High (default) Cannot be edited.
box
Logic Code: Select the Choose the appropriate logic code for this tag.
logic code for this tag. See "About logic codes" on page 240.
Display Registers in: Click the radio button for the way you want to
hexadecimal/decimal view register information.
Device Choose the type of module in which the tag is
Module
Information box used. Used for Micrologic at this time.
Select the type of register that is to be written or
Register Type
read.
There is only one
Number of Enables for editing the appropriate registers in
register for this
Registers the lines below.
address.
Fixed
Scale/Register n/a Not used for digital logic codes.
Scale
Conversion
n/a Not used for digital logic codes.
Factor
Enter the register Be aware of whether you chose hexadecimal or
Register 1
number. decimal. Use the same format here.
When all bits match exactly the pattern in the
register, the status is True. When any one bit
For digital input/output does not match the pattern in the register, the
tags: Set the bits to 1 or status is False.
Bitmask for 0 to match the pattern
Register 1 for “True” in the device NOTE: On PM8s and CM4s, there is a device-
register. specific format, DIgIn and DigOut. In each case,
you must first specify the indicator register
(which becomes the first register). The second
register will have the mask.

Invert Result n/a Not used for resets.

Control tag addresses

NOTE: For a control with one command, once the tag is set up, writing a 1 to the tag will cause
the “write” to occur. For a control with two commands that is either static or normally open,
writing a 1 to the tag will cause the first command (ON) to occur; writing a 0 will cause the second
(OFF) to occur. For a control with two commands that is normally closed, writing a 1 to the tag
will cause the second command (OFF) to occur; writing a 0 will cause the first command (ON) to
occur.

Page 228 of 1312 7EN02-0462-03

System Guide Configure

Standard device types include some pre-defined controls. For example, Operate (ENERGIZE).
These pre-defined commands cause proprietary functions within the device. Do not edit these
commands.

To add a custom control that will operate by writing to a register, do the following:

1. From the Add/Edit Custom Tags screen, set the Group to Controls and the Data Type as
Digital.

2. Save the tag.

3. Add the new tag(s) to the appropriate device type(s).

4. From the Define Device Type Tags tab, locate the tag and click Edit.

The following table describes the fields of the Edit Address screen for control tags.

Box Name Field Name Comments

For commands that have an opposite (such as On
and Off), choose Normally Open/Normally Closed
Command Type or Static with Off Command. For commands with
only one action, choose Static without Off
Tag Information
Command.
If you are editing a command with two parts, use the
Command to Edit Command to Edit drop-down menu to select the On
Command.
Data Type: for display You can edit this field in the Add/Edit Custom Tags
Data only screen.
Information box Logic Code: Select the Choose the appropriate logic code for this tag. See
logic code for this tag. "About logic codes" on page 240.
Display Registers in: Click the radio button for the way you want to view
hexadecimal/decimal register information.
Device Choose the type of module in which the tag is used.
Module
Information box Used for Micrologic at this time.
Select the type of register that is to be written or
Register Type
read.
Number of Enables for editing the appropriate registers in the
n/a
Registers (1) lines below.
A fixed scale is the actual value of the scale. A
register scale is the register address where the
Fixed Click the radio button scale is held.
Scale/Register for the correct type of The value will be scaled in this manner: Value x 10x
Scale scale.
where X = the scale.

Scales can only be –10 to 10.

Conversion
n/a Not used for digital controls.
Factor

7EN02-0462-03 Page 229 of 1312

Configure System Guide

Box Name Field Name Comments

Enter the register Be aware of whether you chose hexadecimal or
Register 1
number. decimal. Use the same format here.
When all bits match exactly the pattern in the
register, the status is True. When any one bit does
For digital input/output not match the pattern in the register, the status is
tags: Set the bits to 1 or False.
Bitmask for 0 to match the pattern
Register 1 for “True” in the device NOTE: On PM8s and CM4s, there is a device-
register. specific forma, DIgIn and DigOut. In each case,
you must first specify the indicator register (which
becomes the first register). The second register
will have the mask.

Invert Result n/a Not used for digital controls.

Editing address information

To edit address information for a real-time tag:

1. From the Define Device Type Tags tab, choose a device type (cannot be locked). From the
Real Time Tags sub-tab, highlight the tag whose address you want to edit.

2. In the Edit Address column, click Edit for the address you want to edit.

3. The Edit Address screen displays.

4. You can change any of the tag address attributes. See the preceding table for descriptions
of each field.

5. Click OK to save changes and close the screen.

Add a new tag address

You can also add a tag address, when none exists. As with editing addresses, click the Edit
Address column for a tag; then follow instructions in the table above.

Edit generic tag addresses

This window displays when you click Edit for an address of a non-PowerLogic compatible device
type, such IEC 61850 or DNP3.

The variable tag properties used in this screen are described in a topic in the Plant SCADA help
file. For detailed information, see Add a Variable Tag in the Plant SCADA 2021 help file:
...\Program Files (x86)\Schneider Electric\Power
Operation\v2021\bin\Help\SCADA Help

Setting up custom tags

Use the Add / Edit Custom Tags window to create, edit, and delete custom tags.

To create custom tags:

Page 230 of 1312 7EN02-0462-03

System Guide Configure

1. Open the Add / Edit Custom Tags window using one of the following methods:

At the bottom of the Add / Edit Device Type window, click Add / Edit Custom Tags.

In Profile Editor, click Settings > Set Up Custom Tags.

2. Set up the custom tag using the Add / Edit Custom Tag fields.

The following table describes the Add / Edit Custom Tag fields.

NOTE: See "Edit a custom tag" on page 234 and "Delete a custom tag" on page 234 for
instructions on how to edit or delete custom tags.

NOTE: Starting in Power Operation 2021, item names have an increased importance. They
drive binding in web graphics, and determine the availability of those bindings in the Graphics
Editor. It is important for tags that will be used in graphics to have item names.

Field Name Valid Entries Comments

Create New Click to begin adding a new tag.
Click to begin adding a new tag that is based on
Create From an existing custom tag. For example, you might
want to change metadata for another custom tag.
Edit Existing Click to edit the attributes of an existing tag.
Click to delete a tag (tag cannot be associated
Delete Existing
Custom Tag with a device type).
Options Tag to Create
From
From the drop-down menu, select the tag you
Tag to Edit want to create from, edit or delete.

Tag to Delete
Live only when Delete Existing is selected. Click
Delete button to delete the tag. You can only delete custom tags
not associated with a device type.
Live only when in Edit mode. Click to list device
types that are associated with this custom tag.
Click to display Note the device types so that you can delete the
Display Associated device types that tag from them (in the Add/Edit Device Type
Device Types are associated with screen) before you delete the tag.
this tag.
See "Delete a custom tag" on page 234 for
instructions on using this button.
Type the new tag
Maximum 32 characters; can include any alpha or
name; or type the
numeric character, as well underscore (_) and
Tag Name changed name for
backslash (\). Must begin with either an alpha
a tag you are
character of underscore.
editing.

7EN02-0462-03 Page 231 of 1312

Configure System Guide

Field Name Valid Entries Comments

Type the name that
You can use this field for additional information on
you want to display
the Add/Edit Custom Tags screen. For example,
Display Name when selecting the
you could describe the data that it logs. It does not
tag and in other
display anywhere else in the system.
displays.
Type the item Maximum 45 characters; can only include
Item Name
name for the tag. alphanumeric characters. Must begin with a letter.
Includes all the real-time groups (such as 100ms,
Group Select the group. controls, currents) plus onboard alarms, resets,
and controls.
These are Power Operation tag data types. They
affect the logic codes that are available for display
Select the data
Data Type in the Edit Address screen. See "About logic
type.
codes" on page 240 for the data type that
matches each logic code.
Select the base These are the base engineering units for tags; the
Eng. Units
unit. values come from Engineering Unit Setup.
Check to cause the
system to ignore Causes reporting to be according to the base unit,
Ignore Unit
any conversions rather than the conversion that was chosen for
Conversion
that were added for this tag in the template that is being used.
this tag.
Click to open the
Add/Edit Units
screen, to add a Provides a quicker means of adding an
Add Eng Unit
new engineering engineering unit that had been overlooked.
unit and/or
conversion.
This is used for display purposes in Power
Operation graphics pages. It determines where
the decimal displays.
Select the
Citect Format Choose the reporting format, to be used in Power
numerical format.
Operation, from ## to #0.#####. For example, if
you select #.##, the number 8.12579 would be
displayed as 8.12.
Indicates the level of priority Power Operation
uses when reading data from devices.
Low, Normal, or
Polling Priority
High NOTE: In the address field, a priority of 1 = High,
2 = Medium, 3 = Low.

Page 232 of 1312 7EN02-0462-03

System Guide Configure

Field Name Valid Entries Comments

For onboard
alarms only: enter
Alarm On Text This text displays on the Create Device Profiles
the text for when
tab for the onboard alarm tag, when it is selected
the alarm is On.
for the device type in the profile. It also displays in
For onboard the Alarm Log.
alarms only: enter
Alarm Off Text
the text for when
the alarm is Off.
Check to display
additional filter Displays several additional filter options on the
Display ‘Advanced’
options in the Real two “Filter” tabs. These options will be useful in
filter selections
Time Filter and the future for reporting purposes.
Alarm Filter tabs
You can include additional filters for either real time filters or alarm filters. Though not currently
used, these filters will provide metadata for later reporting. Standard tags have some of these
filters selected.

A typical usage for these filters might be: when creating a custom tag from an already existing
standard tag, you can create matching metadata by using the filters that have been built in to
the standard tag.
Real Time Filters tab (dropdown lists are expanded when “Display ‘Advanced’ filter selections”
is checked)
Select a category This field provides metadata about the tag. It will
Category Type
for this tag. be used in future reports.
Utility Type Select a utility type. Metadata for future use in reporting.
Select a statistical
Statistical Type Metadata for future use in statistical reporting.
type.
Quantity Select a quantity. Metadata for future use in statistical reporting.
Alarm Filters tab (dropdown lists are expanded when “Display ‘Advanced’ filter selections” is
checked)
Select the alarm Used for filtering and sorting alarm data, and
Categorization
category metadata for future use in statistical reporting.
Select the alarm Used for filtering and sorting alarm data, and
Alarm Type
type. metadata for future use in statistical reporting.
Used for filtering and sorting alarm data, and
Alarm Group Select the group.
metadata for future use in statistical reporting.
Select a Used for filtering and sorting alarm data, and
Subcategorization
subcategory. metadata for future use in statistical reporting.
Select the severity Used for filtering and sorting alarm data, and
Alarm Level
level of the alarm. metadata for future use in statistical reporting.

7EN02-0462-03 Page 233 of 1312

Configure System Guide

Edit a custom tag

You can edit any custom tag.

To edit a tag:

1. Open the Add / Edit Custom Tags screen: from the Add / Edit Device Type screen, click
Add / Edit Custom Tags.

2. In the Custom Tag Options box, click Edit Existing.

3. You can change any of the tag attributes. (This does not change the tag’s assignment
status; if it is selected for a device type, it does not move back to the IEC Tags list.)

4. Click Save to save changes, or click Save & Exit to save changes and close the screen.

Delete a custom tag

You can delete any custom tag that is not associated with a device type.

1. If the tag is associated with a device type, you must first deselect the tag:

2. Change the option to Edit Existing and display the tag you want to delete.

3. Click Display Associated Device Types to display all device types that include this tag.
Make a note of the device types.

4. Return to the Add/Edit Device Type screen. For each device type listed, deselect the tag
that you want to delete.

Continue deleting the tag:

1. Open the Add/Edit Custom Tags screen.

2. In the Custom Tag Options box, click Delete Existing.

3. From the drop-down menu, choose the tag you want to delete.

4. Click Delete.

5. Click Yes to confirm the deletion.

6. Click Save to save the change, or click Save & Exit to save changes and close the screen.

About tags
Power Operation includes a variety of tag types: real-time, alarm, and trend. Most of the tags that
you will need are already added. However, you can add custom tags to suit special needs. This
section describes how tags are constructed and provides further specific information about the
construction of format codes, logic codes, and addresses.

The Power Operation tag naming convention follows the IEC 61850 standard. IEC 61850 tags are
flexible, which allows them to specify how functions are implemented in devices. The IEC 61850
tag was developed for medium-voltage and high-voltage applications, such as monitoring,
control, and substation automation.

Some of our devices include data and functionality that are not yet covered by IEC 61850. For
these devices, the general IEC 61850 formatting was followed when creating tags.

Page 234 of 1312 7EN02-0462-03

System Guide Configure

If you are writing Cicode, see "Customize a project using Cicode" on page 587. You will need to
know the IEC 61850 tag name that you added to the device profile for that device. You can print
the CSV file to view tag names, (see "Printing the .CSV file" on page 221). Apart from that, you
would only need to add tags if you are installing a third-party device that is not standard to Power
Operation. If you do need to add tags, create any category you wish, and follow the format shown
below.

For detailed information on tag naming, see "Tag naming convention" on page 235.

Tag naming convention

Tag names cannot exceed 79 characters. Use a backslash as a separator between tag parts.
Tags are constructed in this manner:

EquipmentName\Logical_Node\Data Object\Data Attribute (may have more than

one)

For detailed information on tag syntax, see Tag Name Syntax in Plant SCADA Help.

The following table lists the main categories for the common IEC 61850 logical nodes. After the
table, the most commonly used category (Mxxx: metering and measurement) is described.

Category
Description
Name
Axxx automatic control; e.g., ATCC (tap changer), AVCO (voltage control)
Cxxx supervisory control; e.g., CILO (interlocking), CSWI (switch control)
Gxxx generic functions; e.g., GGIO (generic I/O)
Ixxx interfacing/archiving; e.g., IARC (archive), IHMI (HMI)
Lxxx system logical nodes; e.g., LLNO (common), LPHD (physical device)
metering and measurement; e.g., MMXU (measurement), MMTR (metering),
Mxxx MSTA (metering statistics), MSQI (sequence and imbalance), MHAI (harmonics
and interharmonics)
protection; e.g., PDIF (differential), PIOC (instantaneous overcurrent or rate of
Pxxx
rise.), PDIS (distance), PTOV (time-overvoltage)
Rxxx protection related; e.g., RREC (auto reclosing), RDRE (disturbance)
Sxxx sensors, monitoring; e.g., SARC (arcs), SPDC (partial discharge)
Txxx instrument transformer; e.g., TCTR (current), TVTR (voltage)
Xxxx switchgear; e.g., XCBR (circuit breaker), XCSW (switch)
Zxxx other equipment; e.g., ZCAP (cap control), ZMOT (motor)

The following example illustrates the IEC 61850 tag for current A:
EquipmentName\MMXU1\A\PhsA

where:

M = the category

MXU = measurement of currents, voltages, power, and impedances

7EN02-0462-03 Page 235 of 1312

Configure System Guide

1 = the instance (there could be multiple MMXU tags)

A = the data object, current

PhsA = the attribute that further defines the data object, phase A

All of the tags that are currently used in the system can be viewed from the Profile Editor > Define
Device Type Tags tab. Click Settings > Display Advanced Properties to display the full tag
names.

Define an enumeration

An enumeration is a single value (0-15) that is used to define a condition that is determined by
multiple-bit input. You will add enumerations to handle scenarios that are more complicated than
simply true-false, to allow for dynamic contingencies. For example, when you need to use multiple
bits to describe the position of a circuit breaker, you might do the following:

Bit y (closed) | Bit x (open). Note that the least significant bit is register 1.

Bit x | Returned
Status Circuit Breaker Position
Bit y Value
0|0 Indeterminate Circuit breaker is neither open nor closed 0
0|1 Open Circuit breaker is open. 1
1|0 Closed Circuit breaker is closed. 2
Circuit breaker is reporting both open and
1|1 Error closed condition. 3
Possible device/wiring error

Using the enumerated status, we place the register and bitmask for the open position in register 1
(least significant) and the register and bitmask for the closed position in register 2 (most
significant).

Use special tags to control circuit breaker

status
When you want to include a device that does not have a pre-defined device profile (such as a
third-party circuit breaker), you must identify the registers that the device uses for the operations
you want, then choose the correct tags and tag addresses to write to these registers. Finally,
when creating the one-line on the graphics page, you will choose the appropriate genie:

1. Determine the device registers used for the open and close operations on the circuit
breaker.

2. In the Profile Editor, choose the tag needed for each operation.

3. Ensure that tag address references the correct action and register(s).

4. When adding a genie for the circuit breaker on the graphics page, choose from the default
library.

Page 236 of 1312 7EN02-0462-03

System Guide Configure

Format code definitions

The address field is part of the tag. It includes a variety of attributes, some of which are required,
and some optional. The following tables list the attributes, whether they are required, and their
possible modifiers. All parts of a tag are case sensitive. The order of the fields is fixed; and all
fields are separated by semi-colons. See "About logic codes" on page 240 for templates of
constructed tags.

Real-Time Format Code Definitions

Attributes Modifiers Comments
SS = single status

DS = double status
enumeration

ST = string

UT = UTC time
T (type)
MV = measured
Required value (float)

CM = complex
measured value Temporarily, this may return a string; when Power
(float) Operation is upgraded to handle large integers,
this will change.
BC = binary counter
(integer)
B = BCM
D (module— P = PM
Micrologic
devices) M = MM

C = CCM

7EN02-0462-03 Page 237 of 1312

Configure System Guide

Attributes Modifiers Comments

M = holding
registers in
hexadecimal

m = holding
registers in decimal

S = input coil (status

register) in
hexadecimal

s = input coil (status

register) in decimal
M/m/S/s/C/c/I/i C = output coil
(register type) (writable only) in
hexadecimal

c = output coil
(writable only) in
decimal

I = input register
(read only) in
hexadecimal

i = input register
(read only) in
decimal
After the modifier, there may be a number
indicating scaling factor. See “V,” below in this
table. Used for conversion to SI units, this number
will be:
u## = ## registers RegisterValue x scale
are unsigned, ## is
Register Number For SS and DS: there must be a 1U default; the
a decimal
Modifiers (register modifier will be a bitmask:
number from 1–4) s## = ## registers
- The mask must use hex only, 16 bits/register
are signed; ## is a
decimal - Attach the ones, then the zero mask, to the
register; if you only have ones masks, just attach
them

- Only one register cases can be inverted. Add :I

after the masks for inversion.
numerical entries; N defines a constant scale; the logic code knows
N (scale)
range is -10 to 10 how to use it.

Page 238 of 1312 7EN02-0462-03

System Guide Configure

Attributes Modifiers Comments

R (scale register) the register number R defines the holding register where the scale is
in decimal held; the logic code knows how to use it.

single digit: 1, 2, or
3; default 2 is used
if this is not included Defines the priority Power Operation uses in
E (priority)
processing data.
(1 = high, 2 =
normal, 3 = low)

Use scientific Examples: 354E-3 = 0.354

V (conversion
notation without the 354E1 = 3540
factor)
decimal. Will be multiplied before the value is returned.
L:P (logic code)
The number that is L:P is the logic code for PowerLogic. Other codes
Required used comes from may follow, such a L:I for ION.
the Logic Codes For logic code descriptions, see "About logic
table. codes" on page 240

Alarm format code definitions

Attributes Modifiers Comments
T (type)
ALM = alarm
Required
B = BCM

D (module—optional for P = PM BCM is straight addressing, and

Micrologic devices) M = MM therefore, optional.

C = CCM
F (file) File number will be in
Required decimal, up to 5 digits

Q (unique ID) Unique ID will be in

This number can be huge.
Required decimal.

Control format code definitions rules of

operation
These rules are true for predefined and custom codes:

Address structure Result

C:N;(action) If 1, perform action. If 0, undefined.

7EN02-0462-03 Page 239 of 1312

Configure System Guide

Address structure Result

C:N;(action1);(action2)
If 1, perform action1. If 0, perform action 2.
C:NO;(action1);(action2)
C:NC;(action1);(action2) If 1, perform action2. If 0, perform action1

Predefined control format codes

Attributes Modifiers Comments
NO = normally
open
C (command) NC = normally
Required closed
Normal operation does not have a
N = normal closed/open status.
operation
OPERATE (command
n/a Two required for NO and NC.
word)

Predefined reset format codes

Attributes Modifiers Comments
Reset (command Entering a one to this tag causes the reset to take
n/a
word) place.

Custom control and reset format codes

Attributes Modifiers Comments

NO = normally open
C (command)
NC = normal closed
Required Normal operation does not
N = normal operation
have a closed/open status.
Followed by one or two entire “write” addresses; used only for logic codes 101, 102, 103. For
logic code descriptions, see "About logic codes" on page 240.

Write Address format: T:SS;m:##:#;L.:P:101

Example: C:NO;T:SS;m:1234:1;L:P101;T:SS;m:3456:1;L:P101

About logic codes

Logic codes tell Power Operation how to mathematically operate on the values in device registers
to give users the desired values. For detailed information on each logic code and its related
information, see "Logic code definitions" on page 993.

Page 240 of 1312 7EN02-0462-03

System Guide Configure

Block writes

Block writes represent blocks of registers that are updated in a single write operation. There are
two types of block writes:
• Fixed: fully specified and compiled before run time. Writing the value of ‘1’ to such a variable
tag causes the specified fixed values to be written to the specified registers.
• Variable: specified on the fly. The registers and the values to be written are not fixed; they are
specified during run time by the user.

Fixed block writes have the following format:

T:BWF;[D:{B|C|M|P};]S:<start_register>,<values>

where
B, C, M,or P are applicable only to Micrologic devices (otherwise the D: section is omitted)
and is the module (manager) identifier (Circuit Breaker, Chassis, Metering, Protection).

<start_register> is the first register number for a contiguous block of registers.

<values> is a comma-separated list of up to 10 values that will be written to the registers

starting from <start_register>.

For example:
T:BWF;S:100,1,2,3,4,-5

Variable block writes have the following format:

where
B, or C, or M, or P is applicable only to Micrologic devices (otherwise the D: section is omitted
altogether) and is the module (manager) identifier (Circuit Breaker, Chassis, Metering,
Protection)

For example:
T:BWV;

The start register and the values to be written follow exactly the same rules and syntax as the
definition for the Fixed Block Write, however, these are specified at the time the write operation is
performed. For example, specifying “S:100,1,2,3,4,-5” as the write value for the tag
“T:BWV;“ would write values 1,2,3,4, and -5 to the registers 100, 101, 102, 103, and 104.

How do drivers work?

For each unique tag request made, the I/O server adds one point to the point count. Tag
subscriptions are limited based on the point count in the license. Exceeding the subscribed point
count will ultimately cause the I/O server to shut down.

Two subscription types

There are two subscription types one used between the graphics level and I/O Server, and one for
polling devices and cache refreshing. The subscription between drivers and polling devices does
not increase point count. Only the subscription that begins at a client system and ends up in the

7EN02-0462-03 Page 241 of 1312

Configure System Guide

I/O server will increase point count. Via this subscription, requests are sent to the drivers with
value changes propagating all the way back to the client system. The client system could be the
display client, alarm server, trend server and so on. What a driver then chooses to do with the
requests—in terms of coupling this to a physical request to a field device—can differ, depending
on the protocol. Some simple protocols propagate the request straight through to the field device;
others have their own polling scheme to the field device and merely service the driver requests
from a cache.

Subscription expirations
If a tag is no longer being read, the cache refreshes in this manner: Graphics client subscriptions
are immediately unsubscribed when the graphics page is closed. Although most drivers release
subscriptions if no client is requesting them, the I/O Server is capable of background polling
(configurable on a per-device basis). These tag subscriptions are not released, and the driver still
polls them. However, they are not counted anywhere, because nothing is consuming the data for
those tags on the I/O Server. On the other hand, once a subscription goes against the point count,
it remains in the count as long as the project is running.

Expiration is immediate if no clients are subscribed to the tag. An "expiration time-out value" is not
configurable.

Create Device Profiles

Use the Create Device Profiles screens to view and edit profiles for individual devices. Profiles
are predefined for the standard devices; you will mostly use this feature to add third-party device
profiles.

After device types are added to the project, use the Create Device Profiles windows to view and
edit profiles for individual devices. Because profiles are defined for the standard devices, use this
feature to add third-party device profiles. On these windows, you can make changes to a standard
device type, and then save the device as a profile that is included in your project.

Before you create profiles, you need to be sure that all of the tags and device types that you need
are created (see "Define Device Type Tags" on page 212). Also make sure that you have added
any new units or conversions and device type categories and subcategories that are needed.

Create Device Profiles tab

The Create Device Profiles tab displays all of the tags that are included in each device type
profile. It is the starting point for creating/editing device profiles for individual devices. Most of the
data on this screen displays for information only; however, to enable waveforms, you need to
check the Waveform box (see "Enable Waveforms" on page 244 for more information).

The following table describes the fields on this tab. The tags listed assume that Advanced
Properties has been checked. Not all elements appear on every sub-tab. Detailed instructions
are after the table.

Page 242 of 1312 7EN02-0462-03

System Guide Configure

Field Name Valid Entry Comments

Click a group to display the
To associate tags and tag groups with a
Tag Groups (left- groups of tags that have
device type (thus creating a device
hand pane) been selected for the chosen
profile), click Add/Edit.
device profile.
Choose the device for which Device Profiles are created on the
Device Profile you want to view profile Add/Edit Device Profile screen (click
details. Add/Edit).
Use that screen to add device profiles
Click to display the Add/Edit
Add/Edit button and to associate PC-based alarms and
Device Profile screen.
trends.
Click to display the selected
Tag type sub-tabs tags for each type of tag:
real-time, trend, PC-based Organized according to tag groups.
alarm, onboard alarm,
control, or reset.
This is the tag name used when adding
Tag Description n/a
the tag.
This is the IEC 61850-compatible name
IEC Tag Name n/a
created when the tag was added.
You must also set up the alarm and
Waveform Check this box as part of the
waveform capture in the onboard files of
process of enabling
(Onboard Alarm) the device. Waveforms will then be
waveform viewing.
viewable in the runtime environment.
Category Type
n/a
(Real Time)
Utility Type
n/a
(Real Time) These are real-time filters. They provide
Statistical Type metadata to be used in future reporting.
n/a
(Real Time)
Quantity
n/a
(Real Time)

7EN02-0462-03 Page 243 of 1312

Configure System Guide

Field Name Valid Entry Comments

Categorization
(PC Based and n/a
Onboard Alarm)
Subcategorization

(PC Based and n/a These are alarm filters. They can be
Onboard Alarm) used for filtering and sorting alarm data
in the runtime environment. They also
Alarm Type
provide metadata to be used in future
(PC Based and n/a
reporting.
Onboard Alarm)
Alarm Group

(PC Based and n/a

Onboard Alarm)
Alarm Level If PC-based and/or onboard alarms are
From the drop-down list, you
(PC Based and set for this profile, you can change their
can edit the alarm level.
Onboard Alarm) levels here.

To view profile information:

1. Select the device profile from the drop-down menu.

2. Use the tag tabs (such as real-time, trend) to view the tag groups included in this device
profile.

To begin adding, editing, or deleting a profile, click Add/Edit.

Enable Waveforms
On the Create Device Profiles tab, in the Onboard Alarm Tags sub-tab, there is a Waveform
check box. Check the box for each alarm tag for which you want to be able to view waveforms. On
the device, the alarm must also be set up for the waveform to be captured on event and stored in
one of the device’s data logs.

Page 244 of 1312 7EN02-0462-03

System Guide Configure

To acquire waveforms for Sepam, use the CET manual. For PowerLogic devices, refer to the
PMCU help file.

As device information is polled and received by Power Operation, the waveform becomes
available for viewing. See The Alarm Log in "Viewing Alarms and Events " on page 740 for
information on viewing waveforms in the Power Operation Runtime.

Managing device profiles

Use the Add/Edit Device Profile screen to add device profiles to the system. To view this
screen, go to the Create Device Profiles tab.

Adding device profiles

1. Open the Create Device Profiles tab: from the Create Device Profiles tab, click Add / Edit.

2. In the Profile Options box, click Create New or Create From.

If you are creating from another device profile, choose it from the Device Profile to Create
From drop-down menu.

3. Click Next to make the name and description fields live.

4. Type a unique Device Profile Name using a maximum of 32 characters; do not use \ / : * ? <
>|

5. (Optional) Type a device description. This will display as a tool tip in later screens.

7EN02-0462-03 Page 245 of 1312

Configure System Guide

6. Select a device profile Type. The default associated component will be selected and shown
below in an image next to a button with the component name.

NOTE: To associate a device profile with a different component, click the button to open
the Graphics Editor Component Library and select a different component.

7. Click Next again to make the remaining fields live.

8. From the Available Devices list, highlight the first device or device group (Protection,
Monitoring, Composite) to be included in this profile. Click the right arrow button to move it
to the Selected Devices box. You must select and move devices or device groups one at a
time (no shift+click to select multiples).

9. If you will want to import this project into another instance of the Profile Editor, see "Add
project parameters" on page 264.

10. When you have all of the devices you want, click Next.

11. From the Device Type Tags list on the left, select the tags you want to include in this profile.
You can select entire tag groups or individual tags from a group; but you must select them
one at a time.

12. After each addition, the tag or tag group displays in the Selected tags box. You can override
any tag name (typically for generic I/O devices with multiple tags, such as inputs, for which
names alone would not be intuitive in runtime. To override a tag, select it, then click Override
Tag Name. Choose the tag you want. Click OK. The new tag will correctly display the value
of the original tag, but will take the appearance of the override tag (such as description,
metadata).

13. The final column, Is Device Tag, displays only for composite devices. Check this box to tie a
tag back to its actual physical device. For example, if the same tag is in three devices, and
you set PC-based alarms for each device, you need to be able to determine which device
has a problem in runtime. To prevent confusion, check Is Device Tag to cause Power
Operation to report the tag for its physical device, rather than the composite device.

14. When you have selected all tags, click Next.

NOTE: If you have duplicate tags from multiple devices, you need to resolve this by using
an override for one of the tags.

15. On the next page, choose whether each tag will have a PC-based alarm and/or trend
associated with it. Click Finish.

When the project is added to the project, PC based alarms are added to the Analog Alarms
or Digital Alarms file. When the project is added to the project, historical trends are added to
the Trend Tags file. Logging will automatically begin when the tag is added to the project.

By default, there are two different intervals for scanning trend tags. All selected tags are
scanned every 15 minutes with FIFO storage of 12 months. For the following tags, there is
an additional “short” scanning interval of 5-seconds, with FIFO storage of two weeks:

Current A, Current B, Current C, Voltage A-B, Voltage B-C, Voltage C-A, Power Factor
Total, Apparent Power Total, Reactive Power Total, Real Power Total, and Frequency.

Page 246 of 1312 7EN02-0462-03

System Guide Configure

For instructions on changing the “short” scan interval settings, see "Trend tag scan intervals"
on page 254.

16. The Driver Parameters box contains options that you can check for IEC 61850 devices. If a
device includes datasets and report control blocks, you can edit the information on the
"Managing IEC 61850 datasets" on page 250 and "Edit IEC 61850 Report control blocks" on
page 251 screens.

17. Check the Close Wizard box, and click Finish to return to Create Device Profiles tab. Or,
leave it unchecked, and click Finish to return to the Add/Edit Device Profile screen.

Editing device profiles

Only unlocked profiles are available for editing.

1. Open the Create Device Profiles tab: from the Create Device Profiles tab, click Add/Edit.

2. In the Profile Options box, click Edit Existing.

3. From the drop-down menu, choose the profile you want to edit.

4. You can change any of the attributes that have been selected for this profile.

5. Click Save to save the change, or click Save & Exit to save changes and close the screen.

There are two ways to edit tags:

1. From this first screen, you can select a profile and then:

Trend Tags sub-tab: choose trend intervals (to create or edit intervals, see ).

PC Based Alarms or Onboard Alarms sub-tabs: change alarm levels (this will
override the default that is set in ).

Onboard Alarms sub-tab: enable waveform capture for on-board alarms (see
"Enabling waveforms for onboard alarms" on page 297 for complete instructions on
enabling these waveform captures).

Onboard Alarms sub-tab: add Alarm On and Alarm Off text. What you enter here will
override the default setting that comes from the custom tag (see for more information).

Parameters sub-tab: Edit parameters for IEC 61850 driver parameters (see "Edit driver
parameters" on page 253 for more information).

2. Click Add/Edit to progress through several screens to edit all aspects of the profile. See the
tables below for detailed instructions.

Deleting device profiles

You cannot delete standard profiles or custom profiles that have been associated with projects.
To delete a custom profile that is associated with a project, you need to go to the Set Up Project
tab.

1. Open the Create Device Profiles tab; from the Create Device Profiles tab, click Add/Edit.

2. In the Profile Options box, click Delete Existing.

3. From the drop-down menu, highlight the profile you want to delete.

4. Click Delete.

7EN02-0462-03 Page 247 of 1312

Configure System Guide

5. Click Yes to confirm the deletion.

6. Exit the screen.

IEC 61850 system setup workflow

These are the basic steps you need to follow to set up an IEC 61850 device in your project.

1. List all of the SCL files (ICD, CID) for the IEC 61850 devices in your installation. ICD files are
preferred. Pay special attention to data concentrated devices (for example, the G3200 with
multiple devices communicating through it; see "Setting up a G3200 gateway" on page 259).

2. Import the first ICD file into the Profile Editor (see "Import Filter screen" on page 271).
a. Create the device type.

b. Match or verify tags for Power Operation.

c. Complete the import.

3. Create a device profile for the IEC 61850 device type (see "Adding an IEC 61850 device" on
page 283).
a. If needed, add/edit datasets and report control blocks (see "Managing IEC 61850
datasets" on page 250 and "Edit IEC 61850 Report control blocks" on page 251).

b. Select the appropriate tags for Power Operation to monitor for this device.

4. Repeat steps 2 and 3 for additional ICD files.

5. Create a Profile Editor project, adding the device profiles. Configure as needed.

6. Export to Power Operation, and to SCL.

Power Operation creates the equipment.profiles file for the I/O Device Manager or Manage
Multiple Devices window.

SCL will create an IID file for the profile. If newly added datasets and/or report control blocks
are to be used, this IID file is required for step 7. Otherwise, you can use the original ICD file.

7. Use the appropriate IEC 61850 configuration tool for the device to configure a CID file from
the ICD/IID file. Then download it to the device.

8. Create the project:

a. From within Power Operation, add a new project.

b. Add the appropriate clusters, networks, and servers.

9. Using the I/O Device Wizard, add your devices to Power Operation.

10. When you are prompted for the SCL file, use the CID file you created in step 7. For more
information, see "Adding an IEC 61850 device" on page 283.

11. Compile and run the project.

Create IEC 61850 Device Type

The first step in creating an IEC 61850 device type is to import the device SCL files, after which
you can make any necessary changes.

Page 248 of 1312 7EN02-0462-03

System Guide Configure

Import the SCL File

You can only import SCL files that meet the schema requirements for Ed 1.4 of IEC 61850. If an
SCL file does not meet these requirements, an error message will display, telling you that the
scheme must validate against the scheme of Ed. 1.4. The Profile Editor will accept SCL files that
use either Ed. 1 or Ed. 2 data structures; but it will apply data structures only as defined in Ed. 2.

During this import, you need to reconcile mismatches; and data will be available for creating
device types, device profiles, and projects. If you import an SCL for a PM700, note that all tags for
date and time are excluded by default.

You can save the information in one of two ways:

• IID file: This IID file will maintain all of the configuration and communication information that
comes from its device. The only items you can change are:
You can delete datasets and control blocks, and add new ones.

You can edit buffered and unbuffered control blocks (provided you have created them in
the Profile Editor).
• Power Operation profile: The data will then follow the normal rules for the profiles in this
project.

The Import Filter Screen

This screen displays after you choose an IEC 61850 file to import (.ICD, .CID, or .IID extension)
and click Start Import. Use this screen to begin filtering data for import. You choose whether to
filter on functional constraints or report control blocks. We recommend that you use report control
blocks:

Report Control Blocks

1. Click the Report Control Block button.

The list of devices and their related report control blocks that are included in the import file
displays in the middle column.

2. Check the devices and/or related report control blocks that you want to include in the import.
If you check a device, all of the report control blocks under it are included.

The right-hand column displays the IEDs/report control blocks that you have selected.

NOTE: Use the filter above the middle pane to search. You can enter partial names
separated by dots to further shorten the list.

3. When you have selected either the functional constraints or report control blocks, click
Continue. The data is filtered on the last filter option that you chose (you cannot combine
filters). The Import Reconciliation screen displays.

4. Use the Reconcile Import Screen to find matches for the items you are importing and to filter
import tags to determine whether items are matched or not matched.

7EN02-0462-03 Page 249 of 1312

Configure System Guide

Edit IEC 61850 Datasets

To add and edit IEC 61850 tag datasets to a profile, display the Create Device Profiles tab for a
device that includes ICD files. Click the Parameters sub-tab, then click Edit on the DataSets line.

NOTE: Not all ICD files allow you to add, edit, or delete datasets. If all fields are greyed out, you
will not be able to change the set.

In the upper left corner are the device profile name and device type names that come from an
imported ICD file. All of the entry fields are initially greyed out. The device type datasets (upper
box) are resident in the ICD. The device profile datasets (lower box) have been created or copied
from other datasets in the device type or device profile.

Create and Edit DataSets

If you need to create or edit IEC61850 datasets to a profile, see "Managing IEC 61850 datasets"
on page 250.

Managing IEC 61850 datasets

Use this screen to add and edit IEC 61850 tag datasets to a profile.

To access this screen:

1. Display the Create Device Profiles tab for a device that includes ICD files.

2. Click the Parameters sub-tab, then click Edit on the DataSets line.

NOTE: Not all ICD files allow you to add, edit, or delete datasets. If all fields are greyed out, you
will not be able to change the set.

In the upper left corner are the device profile name and device type names that come from an
imported ICD file. All of the entry fields are initially greyed-out. The device type datasets (upper
box) are resident in the ICD. The device profile datasets (lower box) have been created or copied
from other datasets in the device type or device profile.

Creating a new dataset

1. Click Create New beside the Device Profile DataSets box.

The fields on the right side of the screen are enabled.

2. Type a name and description for the new dataset. These are free-form fields, but they must
comply with IEC 61850 standards.

3. Choose the appropriate logical device, then choose the logical node for that device.

4. Choose the functional constraint for the content. This will filter the display of device type
objects/topics in the box below.

When you choose All, you must then choose an object that already has a functional
constraint in it. If you choose a specific constraint, the list of available objects is filtered to
display only those that include that constraint.

Page 250 of 1312 7EN02-0462-03

System Guide Configure

5. From the Device Type Objects, choose the appropriate objects for this profile.

6. Click OK.

The new dataset is added in the lower left, to the Device Profile list.

Creating a dataset from an existing dataset

You can create a new dataset either from one that resides in the ICD (from the device type) or
from the device profile.

To create a dataset from another block:

1. Click the dataset (either device type or device profile) to be used as the starting point for the
new dataset.

2. Click Create From.

3. Make the appropriate changes. You must change the name. All datasets in a single profile
must have unique names.

4. Click OK.

The new name displays under the Device Profile List.

Copying a dataset to a Device Type

This feature will not typically be used. If, however, you delete a dataset from the device type, but
later decide you want to add it back, follow this procedure. (You cannot delete datasets that are
used by a report control block.)

1. From the Device Type DataSets box, highlight the dataset you want to add back.

2. Click Copy To.

The dataset displays under the Device Type list in the Device Profile DataSets.

Editing and deleting datasets

You cannot edit or delete datasets that are being used by a report control block or those that
belong to the device type.

To edit a dataset, highlight its name, then click Edit. Make the desired changes, then click OK.

To delete a dataset, highlight its name. Click Delete, then click OK.

Edit IEC 61850 Report control blocks

Use this screen to edit report control blocks for device type information that comes from imported
ICD files.

To access this screen:

1. Display the Create Device Profiles tab for a device that includes ICD files.

2. Click the Parameters sub-tab, then click Edit on the Report Control Blocks line.

7EN02-0462-03 Page 251 of 1312

Configure System Guide

NOTE: Not all ICD files allow you to add, edit, or delete report control blocks. If all fields are
grayed out, you will not be able to change the set.

In the upper left corner are the device profile name and device type names that come from an
imported ICD file. All of the entry fields are initially grayed out. The device type report control
blocks (upper box) are resident in the imported ICD file. The device profile report control blocks
(lower box) have been created or are copied from report control blocks in the device type or
device profile.

Creating a New Report Control Block

To begin creating a new report control block:

1. Click Create New beside the Device Profile Report Control Blocks box.

The fields on the right side of the screen are enabled

2. Type a name and description for the new report control block, conforming to the IEC 61850
naming conventions.

3. Choose the appropriate dataset for this block. Datasets are added/edited in the Add/Edit
DataSets screen, accessed from the Parameters sub-tab on the Create Device Profiles tab.

4. Type a report ID, again conforming to the IEC 61850 convention.

5. ConfRev determines the version number of the report control block.

6. If this is a buffered block (BRCB), check Buffered and enter the time and integrity period.
(Indexing is currently unavailable in Power Operation).

7. Check the appropriate boxes for trigger conditions and report content.

8. Click OK.

The new report control block is added in the lower left, to the Device Profile list.

Creating a Report Control Block from an Existing Report Control Block

You can create a new report control block either from a block that resides in the ICD (from the
device type) or from the device profile.

To begin creating a block from another block:

1. Click the report control block (either device type or device profile) to be used as the starting
point for the new block. Click Create From.

2. Make the appropriate changes. You must change the name. All report control blocks in a
single profile must have unique names.

3. Click OK.

The new name displays under the Device Profile List.

Page 252 of 1312 7EN02-0462-03

System Guide Configure

Copying a Report Control Block to a Device Type

This feature will not typically be used. If, however, you delete a report control block from the
device type, but later decide you want to add it back, follow this procedure.

1. From the Device Type Report Control Blocks box, highlight the block you want to add
back.

2. Click Copy To.

The report control block displays under the Device Type list in the Device Profile Report
Control Blocks.

Editing and Deleting Report Control Blocks

You cannot edit or delete datasets that belong to the device type.

To edit a report control block, highlight its name, then click Edit. Make the desired changes, then
click OK.

To delete a report control block, highlight its name. Click Delete, then click OK.

Edit driver parameters

Certain IEC 61850 devices may have driver parameters associated with them. You can edit the
datasets and report control blocks that will then be exported to Power Operation.

To begin editing driver parameters: from the Create Device Profiles tab, click the Parameters sub-
tab.

To begin editing datasets, click Edit in the DataSets line. Follow instructions in "Managing IEC
61850 datasets" on page 250 for help.

To begin editing report control blocks, click Edit in the Report Control Blocks line. Follow
instructions in "Edit IEC 61850 Report control blocks" on page 251 for help.

Set Up Trend Intervals

For any of the trend definitions that are in the system, you can add, edit, or delete trend intervals.

To add a trend interval:

1. In Profile Editor, click Settings > Set Up Trend Definitions.

2. From the Set Up Trend Definitions screen:

a. Click New to begin adding a new trend

b. Select a trend, then click Copy to create a new trend from an existing trend.

3. Enter a Name: must begin with either an alpha character (A-Z or a-z) or the underscore
character (_). Any following characters must be either alpha characters (A-Z or a-z), digit
characters (0 - 9), backslash characters (\), or underscore characters (_).

4. Type the appropriate information in the following fields. For detailed information, see Trend
Tag Properties in the Plant SCADA help.

To edit a trend interval

7EN02-0462-03 Page 253 of 1312

Configure System Guide

1. From the Set Up Trend Definitions screen, select the trend name, then click Edit.

2. You can edit any of the fields except the trend name.

To delete a trend interval

1. From the Set Up Trend Definitions screen, highlight the name of the trend to be deleted.

2. Click Delete, then click Yes when you are asked to confirm.

Select Trend Intervals

Use the Select Trend Intervals screen to edit settings for existing trends for specific device
profile/tag combinations. To create new trends, see "Set Up Trend Intervals" on page 253.

To change a trend interval, follow these steps:

1. On the Create Device Profiles tab, choose the device profile, then click the Trend Tags
sub-tab.

2. Locate the tag for which you want to change the trend. Click Edit.

3. In Select Trend Intervals screen, you can select one or all of the interval options.

4. Click OK.

Trend tag scan intervals

When you select a trend tag for a device profile (Add / Edit Device Profile screen), the tag will be
scanned at the “long” interval” (every 15 minutes, with FIFO storage of 12 months); but certain
trend tags have an additional “short” scan interval. This interval is set by default at 5 seconds, with
FIFO storage of two weeks.

The default tags are: Current A, Current B, Current C, Voltage A-B, Voltage B-C, Voltage C-A,
Power Factor Total, Apparent Power Total, Reactive Power Total, Real Power Total, and
Frequency. When you choose one of these tags for trending, you will get both long and short
interval trending. The long interval trend will use the trend tag name from the Profile Editor. The
short interval trend tag will have the same name as the long tag with an “s” appended to it.

You can edit the Profile Editor.exe.config file to add or delete tags that will have short scan
intervals, and to change the short scan interval for all of the tags that are listed.

To edit short scan interval settings:

1. In Notepad, open Profile Editor.exe.config. It is located in: [Project

Drive]\ProgramData\Schneider Electric\Power
Operation\v2021\Applications\Profile Editor

2. To change the short scan interval:

a. Scroll to the "TrendShortIntervalSamplePeriod" setting. The default value is 00:00:05, or
5 seconds (HH:MM:SS). Changing this rate will change the interval for all of the tags that
are listed in the setting in step 3.

3. To change the tags that are included in the short scan interval:
a. Scroll to the "TrendShortIntervalTags" setting. The numbers listed (defaults:
1003,1004,1005,1050,1046,1042,1014,1015,1016,1001,1034) are the tag IDs. You can

Page 254 of 1312 7EN02-0462-03

System Guide Configure

add or delete tags. Tag IDs are listed on the Define Device Type Tags tab (when the
Advanced Properties option checked).

NOTE: If you choose a device that includes the tags in this list, you will always have these
short scan interval tags included.

For example, if you wanted to change the scan interval to ten seconds and add Overcurrent
A for a CM4000, you would edit these two lines in this way:

"TrendShortIntervalSamplePeriod" value="00:00:10"

"TrendShortIntervalTags"
value="1003,1004,1005,1050,1046,1042,1014,1015,1016,1001,1034,19"

Disk storage calculation for trends

There are two methods of calculating disk space usage for trends: scaled and floating point. The
Profile Editor uses floating point by default. For more information on these calculations, see
Calculating Disk Storage in the Plant SCADA help file ( ...\Program Files
(x86)\Schneider Electric\Power Operation\v2021\bin\Help\SCADA Help).

Create composite device profiles

A composite device profile includes more than one device type. Each device type can use its own
protocol for communication.

With the composite device type, the user can use two devices for a single monitoring point. For
example, a circuit breaker and a monitoring device can provide data to this single point. Because
Power Operation combines the functionality of the multiple devices, end users only need to
consider a single device when analyzing a location in their system.

The following links provide instructions for specific device types:

• "Creating a third party Modbus Device Type" on page 255

• "Creating a composite device type" on page 256

• "Creating a data concentrator" on page 258

• "Setting up a G3200 gateway" on page 259

Creating a third party Modbus Device Type

To create a third party Modbus device and add it to your Power Operation project:

1. Find the Device Modbus Reference. This should be included in a document from the
manufacturer for the device you want to add.

2. Familiarize yourself with the manner that the Modbus device specification.

3. Verify the Power Operation supports the device:

The following table lists allowed values for each data type:

7EN02-0462-03 Page 255 of 1312

Configure System Guide

Data Type Variable Size Allowed Values

String string 256 bytes (maximum) ASCII (null terminated)
Digital digital 1 bit or 1 byte 0 or 1
Long long integer 4 bytes –2,147,483,648 to 2,147,483,647
Real floating point 4 bytes –3.4E38 to 3.4E38

4. Verify that the tags you want to use are compliant with Power Operation. To ensure that data
is reported for reporting, LiveView tables, and breaker graphics. Refer to the Common Data
Model (CDM), which is located in [Project Drive]\ProgramData\Schneider
Electric\Power Operation\v2021\Applications\AppServices\bin.

5. Find the best fit tags: From the Profile Editor tag library, find the tag that comes closest to the
quantity you want to measure.

6. Verify the tag you have chosen by comparing it with the CDM.

7. Create the device type in the Profile Editor: Use PwrModbus as the driver.

8. Select the appropriate tags (CDM).

9. Configure the Modbus tags: Continuing on the Define Device Type Tags tab, edit the tag
addresses to map them to the Modbus register of the device (these tags will be red). You
can locate instructions on editing addresses in the Power Operation help file.

10. Create the device profile: Click Add/Edit to launch the Add/Edit Device Profile window.
Create the new profile and choose the device(s) that you want.

11. On the next screen, move the tags into the Selected Tags pane. Select Trend for all tags that
require it.

12. Continue with setting up the project and exporting as you do with other device profiles.

Creating a composite device type

A composite device is a device profile that includes more than one device type. Each device type
can use its own protocol for communication.

With the composite device type, the user can use two devices for a single monitoring point. For
example, a circuit breaker and a monitoring device can provide data to this single point. Because
Power Operation combines the functionality of the multiple devices, end users only need to
consider a single device when analyzing a location in their system.

NOTE: For instructions on setting up and using Cyber Sciences Sequence of Events Recorder
(SER), refer to the system technical note (STN) entitled How can I Use Cyber Sciences SERs
with Power SCADA Expert?

To create the composite device type:

1. From the Create Device Profiles tab, click Add/Edit.

2. At the Add/Edit Device Profile screen, choose whether you are creating a new device or
creating from an existing device. If you are creating from a device type, select it. Click Next.

Page 256 of 1312 7EN02-0462-03

System Guide Configure

3. Still on the Add/Edit Device Profile screen, give the composite device type a name.
Optionally, add a description (which will become a tool tip display in later screens). Click
Next.

4. Choose the device types to be in the composite. Click Next.

The Add/Edit Device Profile displays with only device type tags available for selection.
5. Add the tags you need for each device type listed on the left. To add all of the tags for a
device type, highlight the device type name and click the right green arrow.

The Add/Edit Device Profile displays with only device type tags available for selection.

You may find, especially when dealing with generic I/O, that the tag name is not descriptive
enough to determine what it is when reading data in runtime mode. Thus, you may want to
override the generic name with something more meaningful.

For example, a device may have ten inputs: Ind1, Ind2, Ind3, and so on. Using those names,
you have no idea what each input is reading. If you override the tag, the tag's value will still
come from the original tag (it still keeps the addressing from the device); however the tag's
appearance (name, metadata, display name) will be taken from the new tag.
6. To override a tag:
a. Highlight the tag, then click Override Tag Name.

b. From the Select Tag window, choose the tag you want. If necessary, enter a search
term, then click Search to display related tags.