EcoSUI EN UM K5

EcoSUI
Human Machine Interface

User Manual
Version: EcoSUI/EN UM/K5

03/2023
Legal Information
The information provided in this document contains general descriptions, technical characteristics
and/or recommendations related to products/solutions.
This document is not intended as a substitute for a detailed study or operational and site-specific
development or schematic plan. It is not to be used for determining suitability or reliability of the
products/solutions for specific user applications. It is the duty of any such user to perform or have
any professional expert of its choice (integrator, specifier or the like) perform the appropriate and
comprehensive risk analysis, evaluation and testing of the products/solutions with respect to the
relevant specific application or use thereof.
The Schneider Electric brand and any trademarks of Schneider Electric SE and its subsidiaries
referred to in this document are the property of Schneider Electric SE or its subsidiaries. All other
brands may be trademarks of their respective owner.
This document and its content are protected under applicable copyright laws and provided for
informative use only. No part of this document may be reproduced or transmitted in any form or by
any means (electronic, mechanical, photocopying, recording, or otherwise), for any purpose,
without the prior written permission of Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the document or its
content, except for a non-exclusive and personal license to consult it on an "as is" basis.
Schneider Electric reserves the right to make changes or updates with respect to or in the content
of this document or the format thereof, at any time without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by Schneider

Electric and its subsidiaries for any errors or omissions in the informational content of this
document, as well as any non-intended use or misuse of the content thereof.
Disclaimer
No responsibility is assumed by Schneider Electric for any consequences arising out of the use of
this guide. This guide is not intended as an instruction manual for untrained persons. The guide
cannot cover all conceivable circumstances or include detailed information on all topics. In the
event of questions or specific issues, do not take any action without proper authorisation. Contact
Schneider Electric and request the necessary information.
There may be websites linked to and from this site that are operated or created by organizations
outside of Schneider Electric. Those organizations are solely responsible for the operation and
information (including the right to display such information) found on their respective websites.
The linking to or from this site does not imply on the part of Schneider Electric any endorsement or
guarantee of any of the organizations or information (including the right to display such
information) found on their respective websites.
Schneider Electric does not assume and is not responsible for any liability whatsoever for the
linking of any of these linked websites, the operation or content (including the right to display such
information) of any of the linked websites, nor for any of the information, interpretation, comments
or opinions expressed in any of the linked websites. Any comments or inquiries regarding the
linked websites are to be directed to the particular organization for whom the particular website is
being operated.
Contact information
Schneider Electric
35 rue Joseph Monier

92500 Rueil Malmaison
France
+33 (0) 1 41 29 70 00
https://www.se.com
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.
Failure to follow these instructions will result in death or serious injury.
WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.
Failure to follow these instructions could result in death, serious injury or equipment
damage.
CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.
Failure to follow these instructions could result in injury or equipment damage.
NOTICE
NOTICE is used to address practices not related to physical injury.
Failure to follow these instructions could result in equipment damage.

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.
Secure Disposal
It is recommended that incineration and disposal to water courses is avoided. The

equipment should be disposed of in a safe manner and with a secure disposal of
confidential embedded information.
Secure disposal refers to the process and result by which information, including
information held on the equipment, is irreparably destroyed so as to maintain the
security of the equipment and information during the process and up to the point of
irremediable destruction.
Any equipment containing batteries should have them removed before disposal,
taking precautions to avoid short circuits. Particular regulations within the country of
operation, may apply to the disposal of the equipment.
Announcement
EcoStruxure™ Power Automation System (EPAS)
In case of former brand names such as “EcoStruxure Substation Operation”, “ESO” or “PACiS”,
are lingered in this documentation, please consider them as linked to " EcoStruxure™ Power
Automation System".
The formerly known as "PACiS or "EcoStruxure™ Power Automation System-ESO" has been
rebranded to "EcoStruxure™ Power Automation System-EPAS". The new name is a result of a
rebranding effort designed to mirror the multi- segment, innovative and digital transformation
aspects of the offer. In case of former brand names such as or “PACiS” or "EcoStruxure™ Power
Automation System-ESO" are lingered in this documentation, please consider them as linked to
"EcoStruxure™ Power Automation System”.
Communication Gateway
The communication gateway offer has been rebranded to “EcoStruxure™ Power Automation
System Gateway” (EPAS-Gateway). In case any of former brand names are inadvertently
lingered in, please consider them as linked to “EcoStruxure™ Power Automation System” and/or
“EcoStruxure™ Power Automation System Gateway”.
PowerLogic range
The Easergy offer has been rebranded to "PowerLogic" (PowerLogic C5). In case any of former
brand names are inadvertently lingered in, please consider them as linked to “PowerLogic”.
INTRODUCTION (IT)
INTRODUCTION EcoSUI/EN IT/I
EcoSUI Documentation Page 1/3
CONTENT
1. Introduction to EcoSUI ...................................................................................... 2
2. Overview of EcoSUI User Guide....................................................................... 2

2.1 Chapter descriptions .............................................................................................................. 2
2.1.1 Chapter Safety (SA) .................................................................................................................................... 2
2.1.2 Chapter Introduction (IT) ............................................................................................................................. 2
2.1.3 Chapter Technical Data (TD) ...................................................................................................................... 2
2.1.4 Chapter Hardware Specifications (HW) ...................................................................................................... 2
2.1.5 Chapter Installation (IN) .............................................................................................................................. 2
2.1.6 Chapter HMI, Local control and user interface (HI) .................................................................................... 2
2.1.7 Chapter Communication (CT) ..................................................................................................................... 2
2.1.8 Chapter Settings (ST) ................................................................................................................................. 2
2.1.9 Chapter Cybersecurity (CS)........................................................................................................................ 2
2.1.10 Chapter Commissioning record sheet (RS) ................................................................................................ 2
2.1.11 Chapter Maintenance (MF) ......................................................................................................................... 2
2.1.12 Chapter Lexicon (LX) .................................................................................................................................. 2
3. Reference Documents ....................................................................................... 3
4. Files list used and indicated in the manual .................................................... 3
5. Understanding the use of EcoSUI Secured and EcoSUI Standard ............... 3

1. INTRODUCTION TO ECOSUI
EcoSUI software is an IEC 61850 based Human Machine Interface dedicated to the supervision and control of
electrical substation.
2. OVERVIEW OF ECOSUI USER GUIDE

The EcoSUI user guide provides functional and technical descriptions of the EcoSUI operator interface. It gives a
comprehensive set of instructions for the use and application of the EcoSUI software.
The EcoSUI user guide includes:

• Information about EcoSUI application and technical description of its features intended to protection and control
engineers who are concerned about how to select and apply EcoSUI for the configuration of their project or any
of the EcoSUI equipment.
• Information about how to install and commission the EcoSUI, and a maintenance section intended to site
engineers who are responsible to install, commission, and maintain the EcoSUI application.
2.1 CHAPTER DESCRIPTIONS

2.1.1 CHAPTER SAFETY (SA)
This chapter includes the safety instructions, handling and reception of electronic equipment, packing and
unpacking parts, Copyrights and Trademarks.
2.1.2 CHAPTER INTRODUCTION (IT)
This is the present document: it includes the description of each chapter of the EcoSUI guide. It is a brief
introduction to EcoSUI capabilities.
2.1.3 CHAPTER TECHNICAL DATA (TD)
This chapter includes the technical data for accuracy limits; recommended operating conditions; and ratings and
performance data. It also describes the environment specifications and compliance with technical standards.
2.1.4 CHAPTER HARDWARE SPECIFICATIONS (HW)
This chapter includes the hardware product descriptions: product identification, case, electronic boards, and so on.
2.1.5 CHAPTER INSTALLATION (IN)
This chapter includes the installation procedures.
2.1.6 CHAPTER HMI, LOCAL CONTROL AND USER INTERFACE (HI)
This chapter includes the operator interface description; Menu tree organization and navigation; and
Setting/configuration software.
2.1.7 CHAPTER COMMUNICATION (CT)
This chapter describes the parameterization files required for data acquisition in EcoSUI and provides a dedicated
procedure for the supported protocols.
2.1.8 CHAPTER SETTINGS (ST)
This chapter includes the procedure for setting up a configuration in EcoSUI.ini files.
2.1.9 CHAPTER CYBERSECURITY (CS)
This chapter includes recommendations for Cybersecurity.
2.1.10 CHAPTER COMMISSIONING RECORD SHEET (RS)
This chapter gives you the detailed record sheets required to commission the EcoSUI.
2.1.11 CHAPTER MAINTENANCE (MF)
This chapter provides an overview of EcoSUI Central DB and details how to maintain it.
2.1.12 CHAPTER LEXICON (LX)
This chapter includes definitions for technical terms and for acronyms.
3. REFERENCE DOCUMENTS
Please find below optional EcoSUI reference documents:
Document Title
EcoSUI_Configuration_EN_AN_H EcoSUI Configuration Application Note
C:\MCIS\BIN\MCIS.chm EcoSUI Formulas Manual
EcoSUI_EN_AN_ECOSUI-GTW EcoSUI Gateway Application Note
4. FILES LIST USED AND INDICATED IN THE MANUAL

Please find below the files used during the design of an EcoSUI system:
Files Comment
profile.xml Template of alarm, defined in each ring; e.g. C:\MCIS\Rings\TRANSFO_HTA
5. UNDERSTANDING THE USE OF ECOSUI SECURED AND ECOSUI

STANDARD
In this manual, EcoSUI application can be referred to as EcoSUI Secured or EcoSUI Standard:
● EcoSUI Secured refers to the EcoSUI application to be used within the scope of EPAS 6.4 or higher versions,
which embeds advanced cybersecurity features (with Firmware signature).
● EcoSUI Standard refers to the EcoSUI application to be used outside the scope of EPAS 6.4 or higher
versions, which embeds standard cybersecurity features (without Firmware signature).
TECHNICAL DATA (TD)
TECHNICAL DATA EcoSUI/EN TD/I
EcoSUI Documentation Page : 1/6
CONTENT
1 Scope of the Document ............................................................................ 2
2 Performances and Limitations .................................................................. 2

2.1 Capabilities ............................................................................................................................. 2
2.2 Control .................................................................................................................................... 2
2.3 EcoSUI HMI Client Capability................................................................................................. 3
2.4 Acquisition Instance Capability............................................................................................. 3
2.5 Archived Data ......................................................................................................................... 4
2.5.1 Database Size............................................................................................................................................. 4
2.5.2 Central DataBase Redundancy .................................................................................................................. 4
2.5.3 Multi-Central DataBase ............................................................................................................................... 5
2.6 Crisis dataflow ........................................................................................................................ 5
2.7 Time Synchronization ............................................................................................................ 6
1 SCOPE OF THE DOCUMENT

This document describes the EcoSUI technical capabilities and performance.
2 PERFORMANCES AND LIMITATIONS

Find in this list EcoSUI constraints concerning performance and limitation:
EcoSUI HMI Client Limits
LAN Dataflow Dataflow of a LAN

Overall Dataflow Sum of the dataflow of all LANs
Continuous Dataflow Steady dataflow for a long period of time
Crisis Dataflow Huge dataflow for a short period of time (caused by an electrical network
instability event (transient OR long lasting)
2.1 CAPABILITIES
SBUS Server Limits
Maximum quantity of Datapoints 120000
Maximum quantity IEC 61850 Servers 500
Maximum incoming continuous dataflow per second 400 measures + 100 digital signals
Maximum quantity of acquisition rings 12
2.2 CONTROL
• Delay to send Direct Execute Controls is near 0 whatever the dataflow.
• Delay to send SBO Controls is near 0 whatever the dataflow.
CAUTION
UNEXPECTED SYSTEM BEHAVIOR
Before using a new or modified configuration, make sure that the equipment configuration
is consistent with each other at system level.
Failure to follow these instructions can result in injury or equipment damage
CAUTION
Make sure that the control, to be triggered by Direct Order, can be executed without
confirmation.
Failure to follow these instructions can result in injury or equipment damage.

2.3 ECOSUI HMI CLIENT CAPABILITY

EcoSUI HMI Client Limits
Maximum number of HMI Clients 12

Maximum time to display a view 2 sec
Maximum time to display an alarm 2 sec
Maximum time to refresh information 1 sec
2.4 ACQUISITION INSTANCE CAPABILITY

Acquisition Instance Capability Limits
Maximum quantity of IEC 61850 Servers 128
Maximum Datapoints 36000
IEC 61850 Client 400 measures
Maximum Dataflow +
100 digital signals
Maximum OPC Servers 4
OPC Client Maximum Datapoints 1000
Maximum Dataflow 100 Data points/s
Maximum Modbus Servers 20
Modbus Client Maximum Datapoints 20000
Maximum Dataflow NA (polling)
Maximum SNMP Servers 40
SNMP Client Maximum Datapoints 1000
Maximum Dataflow NA (polling)
Maximum EFIP Servers 180
EFIP Client Maximum Datapoints 15000
Maximum Dataflow NA (cyclic)
2.5 ARCHIVED DATA

EcoSUI Software is capable of archiving various signals types such as digital information and measurement values
in a Database called Central DataBase (DB).
• One record of digital signal corresponds to 200 bytes in the Central DB.
• One record of measurement value corresponds to 70 bytes in the Central DB.
2.5.1 DATABASE SIZE

The storage capability directly depends on the size of the hard disk.
However, to keep high performances when extracting archives, the maximum recommended number of data is
shown here below:
Archived Data Limits

Maximum "Events" table size 5 GB (2.5 million of records)
Maximum "Values_X" tables size 90 GB (one billion of records)
NOTE:
• "Events" table records the digital signals.
• "Values_X" table records measurements values.
2.5.2 CENTRAL DATABASE REDUNDANCY

EcoSUI software architecture allows the use of non-redundant OR redundant Central DB.
NOTICE
LOSS OF DATA ON CENTRAL DB REDUNDANCY
Use redundant Central DB to help to ensure no loss of data in the case that MySQL
becomes out of service on one of the Central DB.
Failure to follow these instructions can result on loss of data of alarms, events and
measurements
2.5.3 MULTI-CENTRAL DATABASE

Multi-Central DataBase (DB) feature allows EcoSUI to send controls, acknowledge alarms notifications and to
display data coming from more than one connected substations.
To configure this feature, some parameters need to be set in the EcoSUI Servers.ini file. See how in the EcoSUI
Configuration Application Note.
Multi-Central DB Architecture
2.6 CRISIS DATAFLOW

In this chapter, the term ‘data’ will be used for recorded events and recorded measurements.
Before archiving data into the Central DB, SBUS Server stores it in an archiving buffer. The Archiving buffer size
is 200 000 data. The archiving buffer is used to absorb the crisis dataflow and help to ensure that there is no data
loss during a short period of time.
NOTICE
LOSS OF DATA BEYOND THE ARCHIVING BUFFER CAPABILITIES
Loss of data may occur when the data flow exceeds the overall acquisition instance
capability and the archiving buffer.
Failure to follow these instructions can result on loss of data of alarms, events and
measurements
2.7 TIME SYNCHRONIZATION

EcoSUI software is synchronized through an external master clock.
HARDWARE (HW)
HARDWARE EcoSUI/EN HW/I
CONTENT
1 Scope of the Document ............................................................................ 2
2 PC Description.......................................................................................... 3
2.1 Minimum Requirements ......................................................................................................... 3
2.1.1 Operating System ....................................................................................................................................... 3

This document presents the minimum hardware requirements to run EcoSUI application.
EcoSUI application architecture can be split on different PCs.
Fig1. EcoSUI Modules
Modules of EcoSUI Suite
User Interface software module. This is the operator interface that shows devices
EcoSUI HMI
states. Up to n EcoSUI HMI can be connected to the SBUS Server.
Also known as Acquisition module. Is client on IEC 61850 and legacy networks
SBUS Server
and serves data to EcoSUI modules.
Central DB MySQL Database that stores the signal list, alarms & events database
EcoSUI deployment software (to download databases, switch databases,

EcoSUI Supervisor
generate Confpackage). This module is not shown on the diagram below.
2 PC DESCRIPTION
2.1 MINIMUM REQUIREMENTS

Hardware
CPU Core i7
RAM 8 GB RAM
120 GB
Hard Disk
If Central DB: 500 GB
Graphics VGA screen resolution 1920*1080
Ethernet Ethernet port (Gigabit LAN)
If WebHMI installed on same machine, then refer to Hardware minimum requirement of WebHMI manual.
2.1.1 OPERATING SYSTEM

For standard version :
• Windows® 10 Build 1809 LTSC
• Windows® Server 2019

For secured version :
• Windows® 10 Build 1809 LTSC
INSTALLATION (IN)
INSTALLATION EcoSUI/EN IN/I
CONTENT
1. Scope of the Document ............................................................................ 2
1.1 Prerequisites........................................................................................................................... 2
1.1.1 Supported Platforms ................................................................................................................................... 2
1.1.2 Before Installation ....................................................................................................................................... 2
1.1.3 Third-party Tools ......................................................................................................................................... 3
1.1.4 Special requirements for Windows® 10 ..................................................................................................... 5
2. EcoSUI Suite Overview ............................................................................ 6

2.1 License .................................................................................................................................... 6
2.2 Installation Package ............................................................................................................... 6
2.2.1 EcoSUI HMI ................................................................................................................................................ 7
2.2.2 SBUS Server............................................................................................................................................... 8
2.2.3 EcoSUI Supervisor ..................................................................................................................................... 9
2.2.4 EcoSUI Manager ........................................................................................................................................ 9
2.2.5 Central DB .................................................................................................................................................. 9
3. Install EcoSUI ......................................................................................... 10

3.1 Introduction .......................................................................................................................... 10
3.1.1 Note for Authentication Certificate ....................................................................................................... 11
3.2 First installation and update ................................................................................................ 12
3.3 Installation ............................................................................................................................ 14
3.4 Central DB Installation ......................................................................................................... 17
3.4.1 Central DB Installation: Case EcoSUI Standard ....................................................................................... 18
3.4.2 Central DB Installation: Case EcoSUI Secured ........................................................................................ 19
3.5 Verify your EcoSUI installation............................................................................................ 21
3.6 Roll back ............................................................................................................................... 21
3.7 Uninstall ................................................................................................................................ 21
4. Customize EcoSUI.................................................................................. 22
4.1 Enable Windows and Internet Navigation ........................................................................... 22
4.2 Logbook printer (dotmatrix printer) .................................................................................... 22
4.3 Change of mysql data location ............................................................................................ 23
4.4 Print and Export files PDF tool ............................................................................................ 23
5. EcoSUI Configuration Deployment ......................................................... 24

6. Upgrade EcoSUI ..................................................................................... 24
6.1 EcoSUI upgraded versions installation .............................................................................. 24
7. Uninstall EcoSUI ..................................................................................... 34

1. SCOPE OF THE DOCUMENT

This document is a chapter of the EcoSUI documentation. It describes the installation of the packages required to
run EcoSUI application.
1.1 PREREQUISITES
1.1.1 SUPPORTED PLATFORMS

The supported platform is Windows® 10 Enterprise Build 1809 LTSC.
1.1.2 BEFORE INSTALLATION

Before installing EcoSUI, please check the following recommendations:
• The installation of an antivirus is highly recommended. Please refer to EPAS System Cyber Security (SCS)
User Guide for further details.
• Temporarily disable firewall and then reactivate firewall after EcoSUI installation:
To disable firewall:
▪ Click the Start Button and choose Control Panel.
▪ Click System and Security and click Windows Firewall.
▪ Select the Turn Windows Firewall on or off link.
▪ In the window that shows up, click the radio button Turn off
Windows firewall (not recommended).
▪ Click OK.
NOTE: remember to reactivate firewall after EcoSUI installation
• Windows Login Username & Password must be the same on all computers where EcoSUI is installed.
• EcoSUI runs under IPV4 as defined by the EPAS system.
1.1.3 THIRD-PARTY TOOLS

In order to run EcoSUI application, the following frameworks and packages must be installed on your machine
based on the language of your operating system.
Step Item Action

1 Pre- Launch the EcoSUI-Setup Prerequisites 2.2.exe provided with EcoSUI delivery
Prerequisites
This executable installs first all components needed by EcoSUI
2 .Net Framework Make sure that .Net Framework 3.5 & 4.7 is installed (Go to Control panel >
Programs > Programs and Features / Windows Features).
3 WinPCap Make sure WinPcap 4.1.3 is installed (Go to Control panel > Programs >
Programs and Features).
Note: If WinPcap is not present, please install it from EcoSUI installation
package (Tools folder).
Step Item Action

4 NTP For information, NTP is a Network Time Protocol to synchronize devices via
TCP/IP network.
Make sure that NTP is installed.
NOTE: If NTP is not present, please install it from EcoSUI installation package
(Tools folder).
Run the NTP setup.
In the license window that shows up, click I agree and follow instructions:
1. Choose the folder in which to install Network Time Protocol and click Next.
2. Choose the features of Network Time Protocol to be installed and click Next.
3. Check Create an initial configuration file with the following settings.
4. Put IP Address of NTP Servers in the entry field and click Next.
5. Check the Option Use SYSTEM account and click Next.
6. Click Finish to complete the Nework Time Protocol Setup Wizard.
1.1.4 SPECIAL REQUIREMENTS FOR WINDOWS® 10

The Windows User Account Control (UAC) must Turned off, please follow below procedure:
Step Description
1 From Control Panel of computer:

Access "Control Panel > System & Security”
NOTE: If you're prompted for an administrator password or confirmation, type the password or provide
confirmation.
2 User Account Control Settings
Check/Configure the user account control settings level :
Click "Change User Account Control settings"
Choose/check option "Never notify"
Click "OK"
NOTE: Restart computer to apply UAC turned off.

2. ECOSUI SUITE OVERVIEW

2.1 LICENSE
A 30-day trial period is given at first installation.
After the trial period, the customers have to contact the Schneider Electric Hub for Solutions department to get
the final license.
_________________________________________________________________________________
Trial period Note
The 30-day trial period is supported for Windows® User Account with Administrator user right only. The User
Account with Standard user right is not supported.
_________________________________________________________________________________
2.2 INSTALLATION PACKAGE

The EcoSUI installation package is delivered through the EcoSUI-Setup <version>.exe file for the EcoSUI
Standard or the EcoSUI-Setup <version>_Secured.exe for EcoSUI Secured.
There is only one EcoSUI installation package. It will install the following EcoSUI modules on the computer (even if
some of them are not used).
Fig 1: EcoSUI Modules
User Interface software module. This is the operator interface that shows devices states. Up to n
EcoSUI HMI
EcoSUI HMI can be connected to the SBUS Server.
Also known as Acquisition module. Is client on IEC 61850 and legacy networks and serves data
SBUS Server
to EcoSUI modules.
Central DB MySQL Database that stores the signal list, alarms & events database
EcoSUI deployment software (to download databases, switch databases, generate

EcoSUI Supervisor
Confpackage). This module is not shown on the diagram below.
EcoSUI Manager EcoSUI manager is an application monitoring EcoSUI software.
NOTE 1: Each module can be installed on only one computer (light project) or scattered around different computers.
NOTE 2: To interface EcoSUI with Gateway software (GTW), please refer to “Application Note EcoSUI Gateway"
documentation for details.
2.2.1 ECOSUI HMI

EcoSUI HMI is the operator interface of the EcoSUI suite. It allows the operator to supervise, control and maintain
the substations.
The EcoSUI HMI is used for HV and MV substation and for power plants as a local or remote workstation. It can also
be used as an HMI for satellite substations.
Its main functions are:
• Show status of field equipment (Breaker positions, Measurements, …)

• Send Controls to field equipment
• Navigation between views
• Alarm Management
• Event Extraction, Curves
• User Management (stored locally on each computer)
• Online Graphic Configuration
• Access to External Tools
• Log user actions
It communicates with other EcoSUI modules:
• SBUS Servers (Acquisition Module)

o Gets Live values from SBUS equipment
o Sends controls
• Central DB:
o Gets the configuration (the configuration is stored locally on each computer. When EcoSUI starts, it
first checks if a new configuration is available and downloads it if necessary)
o Gets the list of detected alarms, events and measurements
The EcoSUI HMI is installed on Operator Workstation (OWS) which can support other applications such as:
• the System Management Tool application used to maintain and monitor the system itself
• the Setting Software application used to visualize and modify the settings of MiCOM equipments
• other applications dedicated to particular functions (disturbance records analysis, …)
In case of connection to multiple servers, information will be displayed as if it is coming from a single server.
Connectivity between Clients and Servers is provided via Station Bus, dial-up connection or through the Internet.
2.2.2 SBUS SERVER

SBUS Server is the acquisition module of the solution. It currently supports IEC 61850 protocol (through ‘SBUS
Access’, the IEC 61850 acquisition layer of SBUS Server).
SBUS Server can perform direct acquisition on several LANs at the same time.
Its main functions are:
• IEC 61850 Frame interpretation
• Redirection of any datapoint event to event log
• Real time update of HMIs
• Real time alarm update on the Central DB.
• Control routing
• Refresh of “dead band” analog values periodically
• Debug facilities
• Central DB:
o Gets the configuration (the configuration is stored locally on each computer. When EcoSUI starts, it first
checks if a new configuration is available and downloads it if necessary)
o Gets the list of detected alarms, events and measurements
o Updates the alarm list (through a buffer to limit acquisition latency)
o Archives events and measurements (through a buffer to limit acquisition latency)
• EcoSUI HMI:
o Sends refreshed live values (through a buffer to limit acquisition latency)
o Receives Controls
• MiCOM C264 / IED (Through ‘SBUS Access’ Agency):

o Retrieves data
o Sends controls
The number of SBUS Server is limited to 2 per Ring.
The SBUS Server data and parameters are fully reachable by the operator through its dedicated Human Machine
Interface.
2.2.3 ECOSUI SUPERVISOR

EcoSUI Supervisor allows the generation of a configuration package and the deployment of this configuration
package over all HMIs on the network (automated process).
It is installed and started automatically (after installation and at windows startup) on each computer.
NOTE: When starting a project from scratch, you need to generate a configuration package to be used in EcoSUI.
This package uses different .Ini files that you can modify to configure your application, HMI views, LANs …
2.2.4 ECOSUI MANAGER
EcoSUI Manager is an application monitoring suite running at the same time with EcoSUI software suite i.e.
EcoSUI SBUS server, EcoSUI Supervisor, EcoSUI HMI, EcoSUI Gateway V5 Interface, EcoSUI security server and
MySQL server.
It displays and logs health status of EcoSUI software suite. It also detects when an application has stopped
unexpectedly or is frozen and so restart it.
2.2.5 CENTRAL DB
Based upon MySQL open source database, the central DB stores the configuration of the signals, alarms, events
and measurements of the system.
The main Central DB functions are:

• Physical storage of data
• Data server (events & alarms) for EcoSUI HMI
• Signal List
• Purge mechanism
The number of Central DB is limited to 2.
• SBUS Server
o Sends the latest signal list
o Receives & Stores events & measurements
o Receives & Stores alarm list updates
• EcoSUI HMI
o Sends the newest signal list
o Sends events, measurements & alarm list on EcoSUI demand
3. INSTALL ECOSUI
3.1 INTRODUCTION
There are two different installation packages:
• The EcoSUI Secured installation package. To be used with EPAS 6.4 and higher versions.
• The EcoSUI Standard installation package.
Both installation packages are summarized in the following table:
EcoSUI Secured installation package EcoSUI Standard installation package

(to be used with EPAS 6.4 and upper)
Installs EcoSUI application and components with Installs EcoSUI application and components with
advanced security features standard security features (without Firmware
Signature)
The setup file name for installation is identified as: The setup file name for installation is identified as:
“EcoSUI-Setup <version>_Secured.exe” “EcoSUI-Setup <version>.exe”
Example: Example:
EcoSUI-Setup 2.4.0.0_2.4.0.0_Secured.exe EcoSUI-Setup 2.4.0.0_2.4.0.0.exe
The EcoSUI installation package is delivered via the Schneider-Electric EAC FTP site. For support, please contact
the Schneider Electric Hub for Solutions department.
Remark that:
• Administrator rights are required for installing and using the EcoSUI package.
• No backup of configurations nor parameters is required for updating EcoSUI.
3.1.1 NOTE FOR AUTHENTICATION CERTIFICATE
The certificate allows to authenticate the origin and the period of validity of an executable (setup).
Before running the setup program, the user can manually perform a security authentication.
When starting setup, Windows checks the presence of the embedded certificate in the executable setup file.
The operator is informed by Windows:
• If the certificate is missing, an alert window will be displayed
• If the certificate is detected, a confirmation window appears with the associated informations
To check if an executable file is electronically signed:
• Select the installation executable file (setup)
EcoSUI installation executable file – secured version
• Click Right button on the executable file and select Properties from the menu
• Click on Digital Signature tab
• Select the name of the signatory = Schneider Electric
• Click on Details button to view the digital signature information
• Click on Display Certificate button to view the certificate information
• Click on General tab
• Authenticate the executable by checking the fields associated with the vendor's signature and its period of
validity.
3.2 FIRST INSTALLATION AND UPDATE

The procedure for a first installation and for an update is quite the same since the installation package will override
any existing installation.
EcoSUI First Installation EcoSUI Update

If EcoSUI is not installed on your If EcoSUI is already installed on your computer, then follow instructions:
computer, then follow
instructions:
If actual EcoSUI version < 2.1 Other cases
Install EcoSUI (described on the Uninstall actual EcoSUI before Install EcoSUI (see
next procedure). installing the new EcoSUI version procedure below).
in order to avoid incompatibility
problems.
Install new EcoSUI version
In any case, select and download the EcoSUI installation package (Standard or Secured) adapted to your needs as
explained in section 3.1:
Step Action
If MySQL is installed on your computer, then uninstall it:
If actual EcoSUI version < 2.1 Other cases

1 • On a standard platform, use the uninstall feature provided by Go to Step 2
Windows (Configuration panel) in order to uninstall MySQL.
• On a hardened platform, please, refer to the documentation EPAS
Hardening Guide (chapter EcoSUI hardening) and follow the
instructions.
Select and execute the EcoSUI installation package:

• On a standard platform, double-click on the executable file.
2
• On a hardened platform, please, refer to the documentation EPAS Hardening Guide (chapter EcoSUI
hardening) and follow the instructions.
Step Action
If another instance of EcoSUI is installed on

your system, the Setup wizard will inform
you that the EcoSUI processes are running.
In this case, you shall manually end the
processes before continuing.
Right-click on one of the processes

displayed by the Setup wizard and select
End process, then click Yes
3.a
Repeat the procedure for the second

process and click Retry
3.b
3.3 INSTALLATION
To install EcoSUI suite, start the Setup wizard and follow instructions:
Step Description
In the welcome window, click Next
Select the EcoSUI installation

folder and click Next.
2
Step Description
Select the folder in the Start menu

where the shortcuts will be created
and click Next.
The Setup program is ready to

install EcoSUI on your workstation.
To change any of the Setup
program settings, click Back.
Otherwise, click Install to begin
installing EcoSUI.
4
Step Description
The installation process is started:
Then the MySQL installation goes on:
The EcoSUI installation process is done,

Click Finish.
7
3.4 CENTRAL DB INSTALLATION

The system will now update the central database (DB) parameters (My SQL).
Central DB data and parameters are reachable via MySQL tools and SBUS Server Interface.
NOTICE
LOSS OF HUMAN MACHINE INTERFACE
• Follow the Schneider Electric recommendation policy to update MySQL software
• Do not install third party software not validated by Schneider
• Disable any automatic software update
Failure to follow these instructions can result in new installation of the product required.
3.4.1 CENTRAL DB INSTALLATION: CASE ECOSUI STANDARD
Step Description
Click Next in the popup window that

shows up
MySQL Configuration Update process

is started
Once MySQL Configuration Update

process is done, Click OK
NOTE: EcoSUI applications have to be restarted to retrieve the new password after an update. If not restarted,
databases connections will be lost.
3.4.2 CENTRAL DB INSTALLATION: CASE ECOSUI SECURED
Step Actions
MySQL Configuration Update

process is started
If the first installation of the EcoSUI

Secured, enter the new password
and click NEXT
Else choice between create a new

password or keep the current one
and click NEXT
3
Step Actions
Once MySQL Configuration Update

NOTE: EcoSUI applications have to be restarted to retrieve the new password after an update. If not restarted,
databases connections will be lost
3.5 VERIFY YOUR ECOSUI INSTALLATION

You can verify the correct installation of the EcoSUI package.
Step Action
The following EcoSUI Icons shall be present on Window desktop

1
The “EcoSUI” folder shall be present under the “Schneider Electric” folder in the Start menu
From the Start menu, choose Control Panel.

3
Under Programs, click Uninstall a Program.
Find EcoSUI application on program list and check the new version updated.
4
Example:
As an additional step, verify that the Ecosui.config is pointing towards the actual MySQL path.
5
This .config file is in the EcoSUI installation directory.
3.6 ROLL BACK

There is no specific roll-back procedure since the execution of an EcoSUI installation package will override the
existing version. In consequence, installing an older version will override an installed recent version.
Refer to the Installation section of this guide.
3.7 UNINSTALL
Learn how in Uninstall EcoSUI.
4. CUSTOMIZE ECOSUI
4.1 ENABLE WINDOWS AND INTERNET NAVIGATION

Once all packages are installed, add the following property to the General.ini file to enable Windows & Internet
navigation, disabled by default.
This file appears at the root of the EcoSUI installation folder (C:\MCIS):
[Dummy]
Dummy=1
4.2 LOGBOOK PRINTER (DOTMATRIX PRINTER)

• Install Windows Drivers
• Change the Windows printer name to match the name declared in C:\MCIS\General.Ini,[LogbookPrinter]
LogbookPrinterName.
• Uncheck “Enable Printer spooling” for this printer.
4.3 CHANGE OF MYSQL DATA LOCATION

MySQL stores events, alarms and signal configuration in folder C:\Program Files\MySQL\My SQL Server
5.5\data\pacis. The size of this folder can increase to several gigabytes, therefore it can be preferable to move this
folder to another drive.
We will use one Windows feature called ‘junction’ to do this. In this procedure, we will move data from
C:\Program Files\MySQL\My SQL Server 5.5\data\pacis to D:\datapacis (this folder must already exist).
1. Download junction freeware from Windows Sysinternals website (http://technet.microsoft.com/en-

us/sysinternals/bb896768)
2. Copy junction.exe to C:\Windows\System32 (and C:\Windows\SysWOW64 on Windows 64bits)
3. Open a Command Prompt (cmd.exe)
4. Execute ‘net stop mysql’ to stop mysql
5. Execute ‘cd “\Program Files\MySQL\My SQL Server 5.5\data\pacis”’
6. Execute ‘move *.* D:\datapacis’ to move data to D:\Datapacis
7. Execute ‘cd..’
8. Execute ‘rmdir pacis’ to remove the pacis folder
9. Execute ‘junction “C:\Program Files\MySQL\My SQL Server 5.5\data\pacis” D:\datapacis’ to create a junction
between both folder
10. Execute ‘net start mysql’ to restart mysql
Junction is now done between D:\datapacis and C:\Program Files\MySQL\My SQL Server 5.5\data\pacis. Files
are now located in d:\datapacis but they can still be accessed from folder C:\ Program Files\MySQL\My SQL Server
5.5\data\pacis.
Remark: On 64bits, replace Program Files by Program Files (x86)
4.4 PRINT AND EXPORT FILES PDF TOOL

A PDF tool is required for the following operations:
• to export the curves as in PDF format,

• to visualize the documents and the images in the PDF format,
• to print the curves and the files in PDF format
for these kinds of functional operations, the user can avail the existing PDF tools like Microsoft PDF printer
(recommended by R/D).
5. ECOSUI CONFIGURATION DEPLOYMENT

To deploy an EcoSUI configuration package over all HMIs on the network, refer to the procedure described in the
EcoSUI Configuration Application Note.
6. UPGRADE ECOSUI
To upgrade the current version of EcoSUI, please also refer to Installation chapter of the last updated version of
EcoSUI Release Note.
6.1 ECOSUI UPGRADED VERSIONS INSTALLATION

The general procedure for the installation of the EcoSUI is explained in the section 3 Install EcoSUI.
This section explains the installation of the Upgrade EcoSUI 2.6.x.x and its higher versions.
Step Description
For the installation of the EcoSUI

upgraded version 2.6.x.x, the EcoSUI-
Setup Prerequisites 2.4.exe is needed and
to be installed before.
1
In the welcome window click Next.
2
Step Description
The windows display the

installation of the MySQL 5.7.
Click on Next
The installation process started

and on going.
4
Step Description
The MySQL installation goes on:
The EcoSUI Setup Prerequisite

2.4 installation process is done,
Click Finish.
In the case if the user did not install the

EcoSUI Setup Prerequisite 2.4 and still
launch EcoSUI 2.6.x.x to install, a popup
message appears which indicates the
7
installation of Prerequisite 2.4 is required.
Step Description
For the installation of the

EcoSUI upgrade version
2.6.x.x, EcoSUI Setup 2.6.x.x
Standard.exe file is needed
8
In the welcome window of the

EcoSUI Setup, click Next
9
Step Description
Select the EcoSUI 2.6.x.x

installation folder and click Next.
10
Select the folder in the Start

menu where the shortcuts will be
created and click Next
11
Step Description
The Setup program is ready to

install EcoSUI 2.6.x.x on your
workstation. To change any of
the Setup program settings,
click Back. Otherwise, click
Install to begin installing
EcoSUI 2.6.x.x
12
EcoSUI 2.6.x.x Setup is

preparing to Install.
13
Step Description
The installation process started

and on going
14
The EcoSUI upgrade version

2.6.x.x installation process is
done, Click Finish.
15
Step Description
This window represents

that independent of the
database folder path or
a customised path of
the previous version,
where the MySQL
16 version 5.5 is installed,
to note that the
database of the
MySQL upgraded
version 5.7 is found in
this folder path
shown in the
highlighted image.
Click Next.
17
This popup message which appears during the installation of the EcoSUI version 2.6.x.x, signifies the start
of the update of the MySQL version from 5.5 to 5.7 which means the database of the MySQL version
5.5 will change to 5.7, for information, the backup copy of the database of the MySQL version 5.5
will be stored in the folder path highlighted in the image.
To note : The User has two choices either to select :
➢ Click YES by continuing the installation of the EcoSUI version 2.6.X.X and its superior versions
with an update of the MySQL version from 5.5 to 5.7.
➢ Click NO stops the upgrade of the MySQL version to 5.7 and the process of the installation of the
EcoSUI version 2.6.x.x, the user repeats / redo the installation of the EcoSUI version 2.5.X.X from
the beginning and this option will have no impact on the installation process of EcoSUI.
Step Description
MySQL Configuration
Update process is started
18
Once MySQL
Configuration Update
19
Supervisor starts
automatically after the
installation of EcoSUI is
completed.
20
Step Description
Click on Password
Managerment option, it
allows the user to
customize the folder path of
MySQL, Click on
Customize MySQL.
21
The popup message

appears which allows the
user to customize the folder
path of MySQL, permits to
change the directory of the
MySQL data.
22
7. UNINSTALL ECOSUI
The uninstallation procedure is done via EcoSUI uninstall program “unins000.exe” at the root of EcoSUI folder.
NOTE: It is recommended to install the new EcoSUI versions without uninstalling the previous ones.
1. Start the uninstallation program.

2. If one file is currently in use, the program will ask to close it before uninstalling EcoSUI. Once this file is closed,
click Retry.
3. In the popup that shows up, click Yes to remove EcoSUI and all of its components.
4. The system prompts the user to confirm the deletion of shared files. Check them all and click Yes or Yes to all.
5. The following popup prompts the user to confirm the deletion of all data files. Be aware that clicking Yes, will
also delete your configuration. This step is reserved for rare cases only :
6. The EcoSUI packages have been deleted. In the EcoSUI Uninstall window, click OK
HUMAN MACHINE
INTERFACE (HMI)
HUMAN MACHINE INTERFACE EcoSUI/EN HI/I
CONTENT
1 Introduction ............................................................................................... 7
1.1 Document purpose ................................................................................................................. 7
1.2 General overview .................................................................................................................... 7
1.2.1 EcoSUI HMI components ........................................................................................................................... 7
1.2.2 EcoSUI HMI Architecture ............................................................................................................................ 8
1.3 Basic functions overview ....................................................................................................... 9
1.4 Pictorial representation.......................................................................................................... 9
2 EcoSUI Main Concepts ........................................................................... 10

2.1 EcoSUI HMI Workspaces ..................................................................................................... 10
2.2 Child / Parent Relationship .................................................................................................. 10
2.3 Layers philosophy ................................................................................................................ 11
2.4 Graphical objects ................................................................................................................. 11
2.5 Template object .................................................................................................................... 11
2.6 Object list .............................................................................................................................. 12
2.7 Object Properties.................................................................................................................. 13
2.8 Configuration files location ................................................................................................. 13
2.9 Action Definition ................................................................................................................... 14
2.9.1 Multiple Actions ......................................................................................................................................... 14
3 Workspace Layout .................................................................................. 15

3.1 The Session Banner ............................................................................................................. 16
3.1.1 The Navigation Panel ............................................................................................................................... 17
3.1.2 The Tools Panel ........................................................................................................................................ 17
3.2 The Last Detected Alarms Workspace ................................................................................ 18
4 Language ............................................................................................... 19
5 User-oriented Functions ......................................................................... 20
5.1 Users and roles management .............................................................................................. 20
5.2 Access authorization: Login/Logout function .................................................................... 20
5.2.1 Login/Logout in the HMI ............................................................................................................................ 20
5.2.2 Login/Logout in the SBUS Server ............................................................................................................. 21
6 States View Functions ............................................................................ 22

6.1 States Viewer ........................................................................................................................ 22
6.1.1 How to add a customized (user-defined) column in the ViewersTime Stamping ..................................... 23
6.2 Filter States View .................................................................................................................. 23
6.2.1 Tree View Filter ......................................................................................................................................... 23
6.2.2 Description Filter ....................................................................................................................................... 23
6.2.3 Category Filter .......................................................................................................................................... 25
6.3 Print States ........................................................................................................................... 25
6.4 Export States ........................................................................................................................ 26
7 Event View Functions ............................................................................. 27

7.1 System Events ...................................................................................................................... 27
7.2 Event Viewer HMI Configuration ......................................................................................... 28
7.2.1 Page Mode Configuration ......................................................................................................................... 29
7.2.2 Page Mode – Navigation Action ............................................................................................................... 30
7.2.3 Page Mode – Dynamic Text function ........................................................................................................ 31
Get Current Page From Event Viewer ...................................................................................................31
Get Page Number from Event Viewer ...................................................................................................31
7.2.4 Event Viewer – External Action ................................................................................................................ 32
7.3 Event Viewer - Archive display ............................................................................................ 34
7.3.1 Time Stamping .......................................................................................................................................... 34

7.4 Event log Archive Tree View Filter ...................................................................................... 35
7.5 Event Log Archive Sorting ................................................................................................... 35
7.6 Event Log Archive Advance Filter ....................................................................................... 36
7.7 Filter Events .......................................................................................................................... 39
7.7.1 Filter Events According to Alarm Level ..................................................................................................... 39
7.7.2 Event delay filter with SCE ....................................................................................................................... 40
7.7.3 Event delay filter with SET ........................................................................................................................ 42
7.8 Configurable ComboBox filtering ....................................................................................... 43
7.9 Event Colorization ................................................................................................................ 44
7.10 Print Event Log Archive ....................................................................................................... 45
7.11 Export Event Log Archive .................................................................................................... 46
7.12 Extract Event Log Archive ................................................................................................... 46
7.13 Extract Event Log Date and Time ........................................................................................ 47
7.14 Event Log - Live Display ...................................................................................................... 48
7.15 Play Event Log Live.............................................................................................................. 49
7.16 Pause Event Log Live .......................................................................................................... 49
7.17 Print Event Log Live ............................................................................................................. 50
7.18 Export Log Live Export ........................................................................................................ 51
8 Events replay (VCR) ............................................................................... 52

8.1 Filter Events to Replay ......................................................................................................... 55
8.1.1 Tree View display ..................................................................................................................................... 55
8.1.2 Match Text or Criteria ............................................................................................................................... 57
8.2 Set Time Options .................................................................................................................. 59
8.2.1 Start & End Date ....................................................................................................................................... 59
8.2.2 Start & End Time ...................................................................................................................................... 60
8.2.3 Predefined Time slot ................................................................................................................................. 60
8.3 Play & Pause Event Sequence............................................................................................. 60
8.3.1 Play Events in Sequence .......................................................................................................................... 60
8.3.2 Play Events in a Loop ............................................................................................................................... 61
8.3.3 Stop Event Sequence ............................................................................................................................... 61
8.4 Update Curves ...................................................................................................................... 61
9 Alarms management............................................................................... 62
9.1 Alarm states definition ......................................................................................................... 62
9.2 Parameters associated with an alarm ................................................................................. 62
9.3 Alarm state transitions ......................................................................................................... 63
9.4 Acknowledgement ................................................................................................................ 63
9.5 Clearing ................................................................................................................................. 64
9.5.1 Automatic clearing .................................................................................................................................... 64
9.5.2 Operator request clearing ......................................................................................................................... 64
9.6 How to add Comments to Alarms (and Events) ................................................................. 64
9.7 Audible alarms ...................................................................................................................... 65
10 Alarms functions ..................................................................................... 66

10.1 Alarms Viewer....................................................................................................................... 66
10.1.1 Time Stamping .......................................................................................................................................... 67
10.2 Alarms tree filter ................................................................................................................... 68
10.3 Alarm Viewer HMI Configuration ......................................................................................... 68
10.3.1 Page Mode Configuration ......................................................................................................................... 70
10.3.2 Page Mode – Navigation Action ............................................................................................................... 71
10.3.3 Page Mode – Dynamic Text function ........................................................................................................ 72
10.3.4 Alarm Viewer – External Action ....................................................................................................................... 73
10.3.5 Alarm Control – Other Configuration ........................................................................................................ 76
10.4 Alarms Individual acknowledgement .................................................................................. 82
10.5 Alarms multi- acknowledgement ......................................................................................... 82
10.6 Alarms Page Clear Alarms ................................................................................................... 83
10.7 Bay Alarm Acknowledge & Clear ........................................................................................ 84

10.8 Hide Alarms .......................................................................................................................... 85
10.8.1 Hidden Alarms configuration..................................................................................................................... 88
10.9 Alarms Page Print................................................................................................................. 89
10.10 Alarms Page Export ............................................................................................................. 89
10.11 Stop buzzer function ............................................................................................................ 90
10.12 Toggle mute function ........................................................................................................... 90
10.13 Last Alarms Window Alarms Display .................................................................................. 91
10.13.1 Text files for alarm management .............................................................................................................. 91
10.14 Alarms Colorization.............................................................................................................. 93
10.15 Alarms Advance Filtering .................................................................................................... 97
11 Curves .................................................................................................... 99
11.1 Curves tool display .............................................................................................................. 99
11.2 Configure a set of curves ................................................................................................... 100
11.2.1 Select pen ............................................................................................................................................... 101
11.2.2 Active curve display ................................................................................................................................ 101
11.2.3 Signal selection ....................................................................................................................................... 101
11.2.4 Curves legend Options: Min/Max, Format and Unit................................................................................ 103
11.2.5 Color selection ........................................................................................................................................ 103
11.2.6 Coefficient selection ................................................................................................................................ 104
11.3 Curves Viewer HMI Configuration ..................................................................................... 104
11.3.1 Curves – External Action ........................................................................................................................ 104
Curve_Print .............................................................................................................................................104
Curve_Export ..........................................................................................................................................104
Curve_Forward .......................................................................................................................................104
Curve_Backward ....................................................................................................................................104
11.3.2 Curves –Show/Hide Action buttons ........................................................................................................ 105
Page control action .................................................................................................................................105
Toolbar icons ..........................................................................................................................................105
11.4 Create a new set of curves ................................................................................................ 106
11.5 Load a set of curves ........................................................................................................... 106
11.6 Save a set of curves ........................................................................................................... 107
11.7 Print curves......................................................................................................................... 108
11.8 Export curves ..................................................................................................................... 109
11.9 Set Date and Time .............................................................................................................. 111
11.10 Extract options ................................................................................................................... 112
11.11 Extract continuously options ............................................................................................ 112
11.12 Working with curves .......................................................................................................... 114
11.12.1 Selected curve display options ............................................................................................................... 114
11.12.2 Grids options ........................................................................................................................................... 116
11.12.3 Zoom options .......................................................................................................................................... 117
11.12.4 Curves information display ..................................................................................................................... 119
11.12.5 Scales options......................................................................................................................................... 119
12 Help views ............................................................................................ 121
13 Navigation............................................................................................. 122
13.1 Navigation with the navigation banner ............................................................................. 122
13.2 Navigation with the mimic button...................................................................................... 122
13.3 Navigation with mimic sensible areas .............................................................................. 122
13.4 Navigation with keyboard arrows ...................................................................................... 123
13.5 Navigation with keyboard shortcuts ................................................................................. 123
13.5.1 How to create keyboard shortcut ............................................................................................................ 124
14 Object Display ...................................................................................... 125
15 Controls ................................................................................................ 126

15.1 Generalities ......................................................................................................................... 126

15.2 Cyber Security .................................................................................................................... 127
15.3 Pop-up control windows .................................................................................................... 127
15.3.1 control popup auto close ......................................................................................................................... 128
15.4 Direct Execute Action ........................................................................................................ 129
15.5 Select Before Operate Actions .......................................................................................... 130
15.6 ‘Fake’ Select Before Operate ............................................................................................. 131
15.7 Bypass Interlock Action ..................................................................................................... 131
15.8 Bypass Synchrocheck Action ........................................................................................... 132
15.9 Suppress and Substitute Actions...................................................................................... 132
15.9.1 SUBSTITUTE / UNSUBSTITUTE, SUPPRESS / UNSUPPRESS Actions ............................................ 132
15.9.2 From the State Viewer ............................................................................................................................ 133
15.10 Setpoint Functions ............................................................................................................. 134
15.11 SNMP monitoring and control ........................................................................................... 135
15.11.1 SNMP monitoring and control preconditions .......................................................................................... 135
15.11.2 from the mimic editor .............................................................................................................................. 135
16 Mimic Object Editor............................................................................... 135

16.1 Edit Objects ........................................................................................................................ 136
16.2 Forbid Mimic Edition .......................................................................................................... 137
16.3 Common properties ........................................................................................................... 138
16.4 Tooltip ................................................................................................................................. 138
16.4.1 Tooltip Enable / Disable .......................................................................................................................... 138
16.4.2 Tooltip Description Property ................................................................................................................... 139
16.5 Rectangle ............................................................................................................................ 140
16.5.1 Create a Polyline .................................................................................................................................... 141
16.5.2 Dotted / Dashed Line Rectangle ............................................................................................................. 142
16.5.3 Animate the Rectangle Borders .............................................................................................................. 143
16.6 Static Picture ...................................................................................................................... 143
16.7 Static Text ........................................................................................................................... 144
16.8 Progress Bar ....................................................................................................................... 145
16.9 Dynamic Rectangle ............................................................................................................ 145
16.9.1 On SPS or DPS ...................................................................................................................................... 145
16.9.2 On MPS .................................................................................................................................................. 146
16.10 Dynamic Picture ................................................................................................................. 147
16.10.1 Show Memo ............................................................................................................................................ 147
16.10.2 On SPS or DPS ...................................................................................................................................... 148
16.10.3 On MPS .................................................................................................................................................. 149
16.10.4 Global parameter DynamicPicture .......................................................................................................... 149
DynamicPictureAllFilenames ..................................................................................................................149
DynamicPicture_Mnemonic ....................................................................................................................150
16.10.5 Show Popup Window .............................................................................................................................. 151
16.11 Dynamic Text ...................................................................................................................... 152
16.11.1 On SPS or DPS ...................................................................................................................................... 152
16.11.2 On MPS .................................................................................................................................................. 152
16.11.3 Show Signal Attributes ............................................................................................................................ 152
16.12 Analog Values..................................................................................................................... 153
16.13 Button.................................................................................................................................. 153
16.13.1 ButtonOrdered ........................................................................................................................................ 154
16.14 Flash Object ........................................................................................................................ 154
16.15 Web Browser ...................................................................................................................... 154
16.16 Load Shedding Grid ........................................................................................................... 155
16.17 Combo Box as a shortcut for predefined action .............................................................. 156
16.17.1 Combo Box configuration ....................................................................................................................... 156
16.17.2 Combo Box behavior .............................................................................................................................. 157
16.18 Wind Speed ......................................................................................................................... 158
16.19 Wind Direction .................................................................................................................... 159
16.20 Tank Feeder ........................................................................................................................ 160
17 EcoSUI Manager .................................................................................. 161

17.1 Purpose of EcoSUI Manager .............................................................................................. 161
17.2 How to start EcoSUI Manager ............................................................................................ 161
17.2.1 Login ....................................................................................................................................................... 161
17.2.2 Configure EcoSUI Manager .................................................................................................................... 162
17.2.3 Close EcoSUI Manager .......................................................................................................................... 162
17.3 How to use EcoSUI Manager ............................................................................................. 163
17.3.1 User profile view ..................................................................................................................................... 163
17.3.2 EcoSUI Manager Control Symbols ......................................................................................................... 163
17.3.3 EcoSUI component monitoring ............................................................................................................... 164
17.3.4 Log Status of EcoSUI components ......................................................................................................... 165
17.3.5 Extraction Reporting ............................................................................................................................... 165
18 MCIS Reporter ...................................................................................... 166

18.1 Measurements value reports ............................................................................................. 167
18.2 Measurement value new parameter “24HOURSHALF” .................................................... 167
18.3 Other existing parameters for EcoSUI reporter ................................................................ 168
18.3.1 BITMAPS ................................................................................................................................................ 168
18.3.2 DATES .................................................................................................................................................... 168
18.3.3 FORMATTING ........................................................................................................................................ 168
18.3.4 STATIC TEXT ......................................................................................................................................... 169
18.3.5 EVENTS .................................................................................................................................................. 169
18.3.6 INDIVIDUAL VALUES ............................................................................................................................ 170
18.3.7 CURVES ................................................................................................................................................. 171
1 INTRODUCTION
1.1 DOCUMENT PURPOSE
This document is addressed to the users of EcoSUI HMI, the graphical user interface of EcoSUI software. This
chapter focuses on the graphical aspects and describes the functionalities provided by the EcoSUI HMI.
NOTE: Illustrations and views in this document are given as examples. They can be modified on a per customer
basis. Some functions described below are dependant of the EcoSUI project configuration and their behavior can be
modified, or the function can be unavailable.
1.2 GENERAL OVERVIEW

The EcoSUI HMI allows the operator to supervise, control and maintain the substations in a quick and intuitive
manner.
The EcoSUI HMI is used for HV and MV substation and for power plants as a local or remote workstation. It can
also be used as an HMI for satellite substations.
1.2.1 ECOSUI HMI COMPONENTS

The EcoSUI HMI is a Windows® 10 application.
The hardware platform can differ from one project to another (notebook, standard or industrial PC) depending on
the environmental operating conditions and customer requirements.
EcoSUI HMI communicates with other EcoSUI modules:
• SBUS server
• Central DB
Each of these 3 modules can be installed on only one

computer (light project) or scattered around different
computers.
EcoSUI
NOTE: There is only one installation package. It installs

these 3 modules on the computer even if some of them
are not used.
The EcoSUI HMI is installed on Operator Workstation

(OWS) which can support other applications:
• the System Management Tool is the application
used to maintain and monitor the system itself
• the Setting Software is the application used to
visualize and modify the settings of MiCOM
equipments
• other applications dedicated to particular functions
(disturbance records analysis, …)
1.2.2 ECOSUI HMI ARCHITECTURE

The EcoSUI HMI provides the user with an interface for operational and engineering functions. In case of connection
to multiple servers, information will be displayed as if it is coming from a single server. Connectivity between Clients
and Servers is provided via Station Bus, dial-up connection or through the internet.
EcoSUI HMI is based on three parts architecture:
Architecture Feature
Type
EcoSUI The first part is composed of one or multiple HMI Client(s)

HMI Client (EcoSUI HMI Client, up to 24), connected to one or two
servers (in case of redundancy) for each substation.
One Global EcoSUI Client can connect to several remote

additional Central Databases, in order to collect data from one
to 32 substations maximum and displays the global real-time dataflow status (events and alarms).
Architecture Feature
Type
EcoSUI The second part is composed of SBUS Servers.

HMI Server
EcoSUI The third part is

Storage DB composed of storage
database with MySQL.
1.3 BASIC FUNCTIONS OVERVIEW

EcoSUI HMI allows supervising and controlling a substation. Here are the main basic functions:
• Control
o Detected alarms acknowledgement and clearing
o Control of electrical devices (circuit breaker, switch, …)
o Locking of electrical devices
o Control of transformers
o Control of secondary devices
o Control of internal automation
• Supervision
o Access authorization
o Topological view of single line diagram
o Graphic representation of switching devices
o Graphic representation of analog values
o Graphic representation of additional process information
o Display of automations state
o Display and modification of counters
o Display of detected alarms in a list
o Display of events
o Display of states
o Display of archives
o Viewing of curves for archived or real-time analog and digital data
o Forcing, substitution, suppression of datapoints
o Hypertext online help
o Reports creation
o Hardcopy
1.4 PICTORIAL REPRESENTATION

This visualization system allows a simple, convenient and project-oriented preparation of process diagrams and
graphical symbols as well as the accessibility of datapoints through mimics, lists or reports.
2 ECOSUI MAIN CONCEPTS

2.1 ECOSUI HMI WORKSPACES
A workspace can be static or movable.
Movable workspaces are typically used for control popup windows. If a mimic is specified, it is loaded at EcoSUI
HMI startup as a default mimic.
There is no limitation on the number of workspaces. If the standard basic application contains 5 workspaces (Session
banner, control banner, main mimic view, last alarms window and navigation banner), it is possible to create
applications with only one workspace, or more than ten workspaces (ten is not a limitation; there is no limitations on
the number of workspaces).
Workspaces properties are defined in Workspaces.ini file in \MCIS\Mimics\workspaces.ini:
2.2 CHILD / PARENT RELATIONSHIP

Each object can have a father. In that case, properties that are not declared in the child will be taken from the parent.
The relationship can be broken at any time. The relationship can be done again after.
2.3 LAYERS PHILOSOPHY

EcoSUI HMI is built with several workspaces.
Each workspace can be associated to a layer level, which makes workspace enabled or disabled depending on its
current layer level.
By creating a layer, user can easily configure in which workspace is working at a time.
Layer level behavior is ascending, which means for example if the highest level layer visible is 7 any other
workspace below this layer level will be disabled.
The highest layer level visible enables associated Workspaces and will be the active layer level.
The only way to go to a lower active layer is by closing associated Workspace.
For example, closing a workspace layer level 7 will lead to set active layer level to 6 (only if no other Layer level 7
is present) which will enable all associated Layer Level 6workspaces.
It is possible to set multiple Workspaces with same Layer Level, which means that 2 or more workspaces can be
enabled at the same time.
Red Rectangle means that Workspace is Disable
Green Rectangle means that Workspace is Enable
2.4 GRAPHICAL OBJECTS

EcoSUI HMI graphical configuration is based on graphical objects assembly. Objects can be static (they are not
animated) or dynamic (they change according to the status/value of a datapoint).
Each object has several ‘’standard’’ properties like

• Position (X, Y)
• Size (Width, Length)
• ZOrder -> Z Position on the view (background, foreground)
• ChildOf -> Name of the father
• Action -> Action to be executed when clicking on the button
• ActionProfiles -> Reserved for future evolutions
• ViewProfiles -> Reserved for future evolutions
2.5 TEMPLATE OBJECT

Template is a special object. In fact, a template is an instance of a view. With the template object, the user can then
insert views in a view. i.e. he can create a bay view and instantiate it several times via a template object in a bigger
view.
2.6 OBJECT LIST

Object Description
Static Text The caption of the text is defined at configuration level
Dynamic Text Text referring to a text variable, changing on events
Analog Value Text representing an analog value, directly linked to a MV
Static Picture Single picture
Dynamic Picture Set of pictures, representing the status of a datapoint
Rectangle Rectangles are dynamics, the color representing the status of a datapoint
Horizontal Line Lines are dynamics, the color representing the status of a datapoint
Vertical Line Lines are dynamics, the color representing the status of a datapoint
Diagonal Up Line Lines are dynamics, the color representing the status of a datapoint
Diagonal Down Line Lines are dynamics, the color representing the status of a datapoint
Circle Circles are defined inside a rectangle. Their colors are dynamic
Triangle Triangles are defined inside a rectangle. Their colors are dynamic
Button Button action, position, size, and color are configurable
Glass Button Glass Buttons are flash objects, linked to a particular action
Progress Bar Progress bar is linked to a MV. Min/Max values and associated colors are to be defined in the
object itself
BitField BitField is linked to a MV, with a bit field representation where bits 1 and 0 are represented by
different colors
Curve Curves are simple objects that can only be instantiated
Pie Pie is linked to a MV. Animated information about the filing level of a pie (sector)
PQ Diagram Graphic representation of a power in the form of active and reactive power
Text Box Zone in which is entered a text
Combo Box To select an item from a pre-defined list
Alarm List List of alarms
State Viewer To show status of signals
Event Viewer To extract archived events and show last events
DataGrid Data are represented as a grid (rows and columns). The data formats are of varied type
Flash Object A swf file type. The Flash object is similar to a static picture object.
Web browser HTML file displayed on the HMI (similar to a static picture object)
Wind Speed Wind Speed is linked to a MV. Animated information about the speed of the wind.
Wind Direction Wind Direction is linked to a MV. Animated information about the direction of the wind.
Tank Feeder Tank Feeder is linked to a MV. Animated information about the filling level of tank feeder.
2.7 OBJECT PROPERTIES

Each object has got its own properties set. Please refer to §15.
Some of them are standard, such as position x or y, other are specific to the type of object.
Mimic Editor showing the properties of a Circuit Breaker.
2.8 CONFIGURATION FILES LOCATION

Configuration files are located in C:\MCIS\Mimics folder.
Learn further configuration details in the EcoSUI Configuration Application Note.
2.9 ACTION DEFINITION

An “action” is the definition of what the software does when the user interacts with the graphical objects. In
this command the user passes a control, display a new mimic, display a popup to pass a command, execute a script
etc. It is a part of the standard parameters of the graphical objects.
Example of an ACTION: SHOW
Image represents the example of an Action command following its definition.
2.9.1 MULTIPLE ACTIONS

In the place of Action, the user can enter “one action” for example: SHOW one MIMICS on one
WORKSPACE which can do a local bar setting on one value. For MULTIPLE ACTIONS, while the same interaction
the user can have multiple chain of actions following one after the other, for example on one click the user can have
one, two, three multiple different SHOW actions.
The user to be able to do this MULTIPLE ACTIONS, there is a special character to insert between every
ACTION which is \n. This \n is special character in HMI defines the user that there is another action which follows
behind from the preceding action command.
With MULTIPLE ACTIONS, allows the user to sequence multiple actions and change the views to multiple
different workspaces.
Image represents the example of an Multiple Actions command

3 WORKSPACE LAYOUT
The graphical area of the EcoSUI HMI is split into different workspaces.
The standard basic application of EcoSUI HMI contains 5 workspaces: session banner, control banner, main mimic
view, last detected alarms window and navigation banner.
There is no limitation of the number of workspaces, although it is possible to have only one workspace.
In general views, workspaces 3 and 5 are merged in a unique workspace (=Workspace 8) that displays “on top of”
the 2 previous ones.
The workspace is made up of different frames:
• Session banner Workspace 1)
• Control banner (Workspace 2)
• Main Mimic (Workspace 3)
• Detected Alarm workspace (Workspace 6)
• Navigation banner (Workspace 7)
3.1 THE SESSION BANNER

The Session Banner appears at the top of the window (workspace W1). It shows information on the connected
operator’s session:
Schneider logo Shows the substation name, the workstation control mode Shows the time and
and the name of active server the date of the system
Navigation Shows the User and the associated Profile Tools/Functions
The Session banner shows the following information:
The Schneider Electric logo is displayed on the top left hand corner of the screen. It is used to log in
to the application. Further information on user & access rights is provided in chapter Access
Authorization: Login / Logout Function.
This button allows the user to switch between Electric and System views.
This button gives access to the Functions and Tools applied to the project (refer to chapter The Tool
Banner).
According to the user’s rights, it closes the EcoSUI application.

3.1.1 THE NAVIGATION PANEL

Navigation between views is done through the dedicated Views button on the left of the Session banner.
It allows quick access to Alarms, System and Electric views, and Legend views but also to external applications such
as specific protection relay softwares. These applications are customizable by editing the C:\MCIS\Mimics\Tools.ini
file.
The operator has just to click a button to access a view. In electrical views, dedicated zones will be configured to
allow direct access to detailed views of the area.
The operator can access detailed views by clicking the dedicated electrical device on Electrical views.
3.1.2 THE TOOLS PANEL

Accessing to the Tools panel is done through the dedicated Tools button on the left of the Session banner.
It allows quick access to the main functions and tools related to the project.
The Tools panel shows the following information:

The Schneider Electric logo is displayed on the top left hand corner of the screen. It is used to log in to the
application. Further information on user & access rights is provided in chapter Access Authorization: Login /
Logout Function
To change user passwords. Further information on user passwords is provided in chapter Password Modification
Depending on administration rights, this function makes it possible to create new users. Further information on
User profiles is provided in chapter User Rights & Profiles Edition
S To switch to the Alarm page. Refer to chapter Alarm Functions for further information
The States viewer allows the user to see Live Status of all datapoints of the system. Refer to chapter State
Functions for further information.
This button shows Event Log (Event Archive & Event Live). Refer to chapter Event Log Functions for further
information.
This button gives a direct access to curves. It allows the user to study trends of signals. Refer to chapter Curves
for further information.
This button makes it possible to extract and replay archives over a user-defined period of time. This function is
useful for analysis purposes or to determine the cause of an issue.
The “Language” function allows a user to select a language for EcoSUI HMI. Note that a language is not linked to
a user.
s It shows information on EcoSUI HMI, such as release or copyrights:
It takes an instant screenshot and prints it directly to the default printer. If multiple screens are present on the
computer, EcoSUI asks to print one or all screens, and then to select your printer preferences.
NOTE: The Keyboard print screen button is also running
3.2 THE LAST DETECTED ALARMS WORKSPACE

This workspace is visible whatever view or task is active in EcoSUI HMI. It permanently shows the ‘n’ last detected
alarms.
The number of row (n) is configurable.
4 LANGUAGE
On Tools panel, click Language button. A list of language appears, click on a language to select it.
Switching language
To configure language, refer to §Language on EcoSUI_EN_AN_Configuration document.

5 USER-ORIENTED FUNCTIONS
5.1 USERS AND ROLES MANAGEMENT
Users, roles, permissions and passwords are completely managed by the Cybersecurity Admin Expert (CAE) tool.
Any change such as user creation, password modification, or role assignment can only be performed from the CAE
tool. Refer to the “CAE User Guide” for more information.
5.2 ACCESS AUTHORIZATION: LOGIN/LOGOUT FUNCTION
5.2.1 LOGIN/LOGOUT IN THE HMI
Login button Logout button

Clicking the “Login” icon in the control banner allows the operator to log in to the system through an identification
popup. The login is verified by the Cybersecurity brick embedded in the EcoSUI. The EcoSUI HMI behavior will then
depend on the operator rights defined in the CAE tool.
Default usernames and passwords are available after the ECOSUI installation. These ones can be used even if
CAE tool has not been installed yet.
For more information on operator rights or on the default users and passwords, refer to the Cybersecurity chapter
of this manual.
After the EcoSUI launch, the login is mandatory by using the Login button of the tool banner.
The login window is the following:
The user has to enter the username, then the password and press ENTER or click OK. After a login, the username
is displayed in the session banner.
An optional automatic log-off is done if there is no operator activity during a configured period of time (refer to the
Security Policy section of the Cybersecurity chapter of this guide.
After login procedure, the logout icon substitutes to the login icon in the control banner and allows the user to close
the session.
5.2.2 LOGIN/LOGOUT IN THE SBUS SERVER

The user has to login on the SBUS Server user interface to do any action on it.
The username and password are also verified by the cybersecurity brick and the user rights definition is managed
by the CAE tool.
The login window is integrated on the SBUS Server user interface as shown in the following figure:
6 STATES VIEW FUNCTIONS

Switch to the States view by clicking the States button in the control banner
The States viewer presents the data points by name. A data point will appear only once, with its current state and
time stamping.
Use States viewer to get a picture of the real-time situation of the data point. Data point state can be issued either
from wired signals, IED data as well as from the system self-monitoring information.
The types of signals that can be displayed are:
• SPS (single point)
• DPS (double point)
• MPS (multiple point)
• State and value of Measurements
6.1 STATES VIEWER
The real-time status information displayed in this view comes directly from the SBUS Server.
The Information is displayed in the following columns:
• Origin: Access path of the datapoint (the default format is Substation Name / Voltage Level / Bay Name if the
datapoint is defined at the bay level)
• Description of the datapoint information
• Value: State message of the datapoint
• Quality of the signal
• Last update: date of the last state change (the default date format is yy/mm/dd hh:mm:ss:mmm)
The user can add up to 3 more user-defined columns. See how in How to add a customized (user-defined) column
in the Viewers
6.1.1 HOW TO ADD A CUSTOMIZED (USER-DEFINED) COLUMN IN THE VIEWERSTIME STAMPING

According to the source of the signal or the associated time quality, signals can be time stamped at different levels:
• Source: Time stamp is given by the equipment that generates the signal (ex: Digital input wired on a C264)
• Acquisition: Time stamp is given when Acquisition reads the signal on a different equipment through a
communication bus (ex: C264 polling signal status from an IED through a Modbus Network).
A Time Stamp can also have different qualities:
• Synchronized.
• Not Synchronized.
In EcoSUI State viewer, the data point date is marked according to the source of the signal or the quality of date:
Sign Description
* Time stamp is given by an equipment that is not synchronized
Example: 2014-03-10 15:14:56.123 (*)
C Time stamp is given by acquisition, not at source
6.2 FILTER STATES VIEW

The information in the States View can be filtered as follows:
6.2.1 TREE VIEW FILTER

Use the tree view on the left of the States View to filter the data.
Filter the information to be displayed by checking/unchecking the boxes in the tree view. Only checked boxes
information will be displayed:
6.2.2 DESCRIPTION FILTER

The Description filter is an additional filter added to the tree view to help users find signals by description.
In this example, the user searches information that refers to a Position. Typing Position immediately filters the
related datapoints:
6.2.3 CATEGORY FILTER

The Category filter is a complementary filter useful to find signals by the following categories:
• All
• All Digital Inputs
• Alarms Digital Inputs
• Events Digital Inputs
• Measurements
6.3 PRINT STATES

Pint the States page by clicking the Print button. It prints the States lines on the actual page.
Select printing preferences then click Print:
6.4 EXPORT STATES

Export States by clicking the Export button. It exports States of the actual page.
Two options are available:
• Export States of this page (visible on the screen) as a CSV file.
• Export States of this page (visible on the screen) as a PDF file.
7 EVENT VIEW FUNCTIONS

Switch to the Event Log View by clicking the Logs button in the Tools panel .
Event Log is split into two functional parts:
• Event Archive display
• Event Live display
These parts are totally independent. The
Event Archive display gets data from the
Central DB while the Event Live display
retrieves data from the SBUS server.
To reduce the data flow between
components and improve overall
performance, measurement variations can be
archived locally to the SBUS Server and not
in the Central DB.
To do so, some parameters need to be set in
Servers.ini file. Learn how in the EcoSUI
Configuration Application Note, in The
Servers.ini File chapter.
7.1 SYSTEM EVENTS

Specific System Events such as user operation or EcoSUI events are also automatically archived:
Type Archived Actions Location

User action Log-In Success HMI
User action Log-In Unsuccessful HMI
User action Log-Out HMI
User action HMI Exit HMI
User action Select Control HMI
User action Execute Control HMI
User action Cancel Selection HMI
User action Bypass Synchro-check HMI
User action Acknowledge One Alarm HMI
User action Acknowledge Page Alarms HMI
User action Acknowledge All Alarms HMI
User action Clear One Alarm HMI
User action Clear All Alarms HMI
User action Password Modification Succeeded HMI
User action Password Modification Unsuccessful HMI
Program Start-Up / Exit HMI
Program Start-Up / Exit SBUS Server
Program Start-Up / Exit Gateway
Program Start-Up / Exit Reporter
7.2 EVENT VIEWER HMI CONFIGURATION

Event Viewer has a Play/Pause option to freeze the display of the viewer.
A Pause icon appears when the viewer is paused.
There are two ways to navigate into the Event Viewer:
• The Standard behavior: the vertical navigation is done with scrollbar. All events are filled in the queue. This is
the default configuration.
• The Page Mode behavior: The number of events displayed in the Event Viewer is configurable. In this mode,
the Event Viewer has to be a static mimic, without toolbar and scrollbar, and without any button. The navigation
between the several pages is done by configuring buttons to navigate e.g. previous page/next page.
When page mode navigation is enabled, only the number fixed by property
EventViewer_PageModeNbEntriesPerPage are displayed. There is no more vertical scrollbar:
NOTE: All navigation buttons need to be placed in a different workspace than Event Viewer itself.
7.2.1 PAGE MODE CONFIGURATION

During Event Viewer configuration, find parameters named EventViewer_PageModeEnable.
Set to 1 to enable page mode navigation and set to 0 (default value) to disable it.
When Page Mode is enabled, user can configure number of shown events using parameter
EventViewer_PageModeNbEntriesPerPage.
By default, this parameter is set to 20, it means that only 20 events will be shown per page.
PARAMETER DESCRIPTION
Enable or Disable page mode navigation into Event Viewer
EventViewer_PageModeEnable 0 = Page Mode Navigation Disabled (Default)
1 = Page Mode Navigation Enabled
Number of alarms shown by page. Default is 20.
EventViewer_PageModeNbEntriesPerPage
Only a numerical
7.2.2 PAGE MODE – NAVIGATION ACTION

In order to change page, the following actions are available
• EventViewer_PreviousPage action let user to go to previous page
• EventViewer_NextPage action let user to go to next page
These actions take 2 parameters:

• WorkspaceId: Index of Workspace (as to be numerical)
• EventViewerName: Name of Event Viewer (findable on tree view during configuration)
These actions are available on the following objects:

• Analog
• BitField
• Button
• DynamicPicture
• DynamicText
• Glass Button
• Pie
• PQDiagram
• ProgressBar
• Rectangle
• StaticPicture
• StaticText
• TankFeeder
• Textbox
• WindDirection
• WindSpeed
Below an example of configuration:

User wants to create an action button to switch EventViewer0 from Workspace 3 to next page. He needs to
configure it like so
7.2.3 PAGE MODE – DYNAMIC TEXT FUNCTION

Only two functions inside Dynamic Text are available:
Get Current Page From Event Viewer
GetCurrentPageFromEventViewer to retrieve the current page from Event Viewer.

This function takes two parameters:
• WorkspaceId: Index of Workspace (numerical)
• EventViewerName: Name of Event Viewer (findable on the tree view during configuration)
See below an example of configuration

The user wants to retrieve the current page from EventViewer0 from Workspace 3:
Please note how parameters are surrounded of bracket
Get Page Number from Event Viewer
GetNbPagesFromEventViewer to retrieve number of available pages from Event Viewer.

This function takes 2 parameters:
• WorkspaceId: Index of Workspace (numerical)
• EventViewerName: Name of Event Viewer (findable on tree view during configuration)
See below an example of configuration

The user wants to retrieve number of available pages from EventViewer0 from Workspace 3:

7.2.4 EVENT VIEWER – EXTERNAL ACTION

• EventViewer_PlayPause allows user to pause or play events of Live Event Viewer depending of its current
state.
• EventViewer_Playing allows user to display the status of EventViewer_PlayPause action. Value is equal to 1
if the Event Viewer is playing and otherwise 0.
• EventViewer_NewEventAvailable allows user to display if new event is available. Value is equal to 1 if the
new event available and otherwise 0.
Those actions take 2 parameters:

- WorkspaceId: Index of Workspace (numerical)
- EventViewerName: Name of Event Viewer (findable on tree view during configuration)
• EventViewer_Print allows user to print list of events from outside the event viewer.
• EventViewer_Export allows user to print list of events from outside the event viewer.
Those actions take 3 parameters:

- WorkspaceId: Index of Workspace (as to be numerical)
- EventViewerName: Name of Event Viewer (Findable on Treeview during configuration)
- allPages: Value to define event to use; 0 to use current displayed page or 1 to use all events
Those actions are available on the following objects:

• Analog
• BitField
• Button
• DynamicPicture
• DynamicText
• Glass Button
• Pie
• PQDiagram
• ProgressBar
• Rectangle
• StaticPicture
• StaticText
• TankFeeder
• Textbox
• WindDirection
• WindSpeed

The user wants to play or pause EventViewer0 from Workspace 3:
7.3 EVENT VIEWER - ARCHIVE DISPLAY

The Archives display shows information in the following columns:
• Date of the event (The default date: yy/mm/dd hh:mm:ss:mmm. Refer to Time Stamping for details)
• Origin of the event
• Description of the type of information
• Message associated to the event
• Origin of the control
in the Viewers
The user can also decide to show the Signal Quality in the Event Viewer by using
EventViewer_ShowQualityColumn=1 parameter:
7.3.1 TIME STAMPING

• Source : Time stamp is given by the equipment that generates the signal (ex: Digital input wired on a C264)
• Acquisition : Time stamp is given when Acquisition reads the signal on a different equipment through a
communication bus (ex: C264 polling signal status from an IED through a Modbus Networt)
• Synchronized
• Not Synchronized
In EcoSUI Event viewer, the data point date is marked according to the source of the signal or the quality of date:
Sign Description
Example : 2014-03-10 15:14:56.123 (*)
7.4 EVENT LOG ARCHIVE TREE VIEW FILTER

The left part of the window displays a tree view of the database, which is used as a filter. Only events with checked
boxes display on the Event Log Archive Display.
NOTE: In the Global EcoSUI Client mode, the events retrieved from several remote Additional Central
Database(s) are displayed on a global view.
7.5 EVENT LOG ARCHIVE SORTING

Sorting options can be applied by clicking the column title:
• Sort by date
• Sort by origin
• Sort by description
• Sort by message
• Sort by control origin
7.6 EVENT LOG ARCHIVE ADVANCE FILTER

The advance filtering is implemented by a filtering bar (see figure below).
Advance filtering function is applied by clicking on filters:
• Text filter
• Date “From To” filter
• Current Day filter
• Custom Time filter
• Event filter (specific for Events Viewer)
1 3 5
2 4 6
NOTE:
• A witness button informs operator about the status of filtering / reset filters.
• By default, the filtering bar is set to hide.
• The filtering bar can be moved by mouse pointing on the left corner and click-left action.
• Press the button Extract to apply the filtering on Event View.
N° FILTER DESCRIPTION
Witness and reset filter:
This button allows user to signal the status of filtering:
• inactive = GREY color, all events are displayed on the view
1 • active= RED color, partial events are displayed on the view
Also, if click-on, will reset the current filtering.
Note: In active mode, a blinking effect can be set by EventViewer_AdvFilterBlinkButton parameter.

Text filter:
2 This filtering is applied for Description and Message columns only. Operator fills the “text string” in the
Filter field and press return. The event view is refreshed with “text string” only.
Event filter:
This filter is specific for Event Viewer.
Several options are available:

• Gravity: Shows events with Gravity levels = All OR selective
values = 0, 1, 2
• Bit Changes: shows events with bit changes = All or selective
values = To 0, To 1, To Invalid
3
• Events Types: show events with types = All OR selective

types = Process Events, User Controls, User
Acknowledgments, User Login, System Events.
• Preset: This function stores (or delete) custom Event filter criteria defined by operator in order to avoid
redefine it on HMI. After saving operation, operator creates name of custom criteria. Operator can
select a name from list to apply directory filtering.
Date From To filter:
This filtering displayed events from start to end dates. Operator sets time values by clicking on From and
4 To (calendar and Time buttons)
Current Day filter:

5 The button “Current Day” displays only events within the current date / today filtering (time from 00h00 to
23h59).
Custom Time filter:
This filtering displays latest events for custom time duration. Operator fills the
“Last” field with 2 digits and choose the temporal scale option:
• minutes
6 • hours
• days
• weeks
• months
• years
The Advance filtering bar is configured to show or hide filters. By default the filtering bar is hidden.
The configuration uses several parameters:
• EventViewer_AdvFilterConfiguration
• EventViewer_AdvLastConfiguration
• EventViewer_AdvFilterBlinkButton
Show or hide Advanced filters inside the toolbar
There are 6 values separated by a semi-colon (;)
Each value is:
• 0 = filter is hidden (by default)
• 1 = filter is visible
The first value hides / shows Wiltness and reset filter
The second value hides / shows Text filter
The third value hides / shows Event Filter
The forth value hides / shows Date From To filter
EventViewer_AdvFilterConfiguration The fifth value hides / shows Current Day filter
The sixth value hides / shows Custom Time filter
Setting example 1
EventViewer_AdvFilterConfiguration = 1;1;1;1;1;1
All filters are visible.
Setting example 2
EventViewer_AdvFilterConfiguration = 0;1;1;0;1;0
Text filter, Event filter and Current Day filter are visible.
NOTE: if all values are set to 0, the Advanced filter bar is hidden.
This parameter contains the Custom Time filter value. When viewer is
loaded, the Last XX filter will be automatically applied with the value.
The parameter has 2 values separated by a semi-colon (;)
The first value is the temporal duration on 2 digits
The second value is the temporal unit:
• minutes
• hours
EventViewer_AdvLastConfiguration
• days
• weeks
• months
• years
Setting example
= 20;minutes
Displays latest 20 minutes events
This parameter makes visual effect on button static / blinking
EventViewer_AdvFilterBlinkButton
The value is:
• 0 = button is not blinking (by default)
• 1 = button is blinking
7.7 FILTER EVENTS

The user can use events filter to filter:
• The event list according to their alarm level.
• The transient event by adding a delay on acquisition. The delay on an Event is applicable only if the related data
is Alarmed (100ms to 6hrs)
7.7.1 FILTER EVENTS ACCORDING TO ALARM LEVEL

The user can filter events according to their alarm level (0=event, 1=alarm, 2=warning specified in the profile.xml
file) by using the following parameter in the Event Viewer object property:
EventViewer_ShowGravityFilters=1
Then, the user will be able to select - from the Event Viewer interface - the category of events to be analyzed (All,
Events, Alarms, Warnings).
Please note that several items can be selected at the same a time (Events and Warnings for example)
7.7.2 EVENT DELAY FILTER WITH SCE

When the ring is configured with a SCE configuration, the configuration of the filtering delays is done through a file
named “FilteringEventDelays.csv”. This file is in the ring folder as the event filtering is done on a per ring basis (e.g.
c:\mcis\rings\hv_transfo_a).
If the file does not exist when the user imports the SCE configuration of the ring, the file is created according to the
datapoints defined in the SCE configuration. All the filtering delays are set to 0 in the file generated by default.
How to configure:
To configure a delay on an event, the user modifies the “FilteringEventDelays.csv” file and set a value from 1 to
2160000 as filtering delay.
Then, to apply the new settings
• Open the EcoSUI SBUS Server
• In Acquisition tab
o Stop the acquisition
o -> Tools… -> Advanced -> “Load filtering event delays”
o Validate the restart of the SBUS Server by the Yes button
Or, the user can simply load the SCE configuration again, the “FilteringEventDelays.csv” file will be loaded at the
end of the SCE configuration parsing automatically.
File description:
The “FilteringEventDelays.csv” file is a csv file with ‘;’ as separator.
• Lines beginning with a “#” are comments.
• Empty lines are ignored.
• There is one line per state to be filtered on a datapoint.
A line is composed of three columns:
• First column contains the full path of the datapoint.
• Second column contains the status on which the filtering has to apply.
• Third column indicates the number of hundreds of milliseconds to apply as filter (e.g. 2 for 200 ms).
Example:
One DPS with following profile:
Site | Substation | Voltage Level | GenericBay | Generic Module | Generic DPS;STATE2;2
Site | Substation | Voltage Level | GenericBay | Generic Module | Generic DPS;STATE0;2
For this DPS, the Jammed and Open event will be delayed of 200 ms, not the other ones.
Only the following states can be defined:
For SPS:
States Meaning
STATE0 Reset
STATE1 Set
For DPS:
States Meaning
STATE0 Open
STATE1 Close
STATE2 Jammed [0,0]
STATE3 Undefined [1,1]
For MPS:
States
STATE0
STATE1
STATE2
STATE3
STATE4
STATE5
STATE6
STATE7
STATE8
STATE9
STATE10
STATE11
STATE12
STATE13
STATE14
STATE15
After import of the “FilteringEventDelays.csv” file, one log is generated, named “FilteringEventDelays.log” in
which user will find the information about parsing operation. A “FilteringEventDelays.err” file may appear if wrong
data occur during parsing of the csv file. It will provide information about what went wrong (datapoint not found, state
invalid, bad filtering delay value…).
7.7.3 EVENT DELAY FILTER WITH SET

When the ring is configured with a SET configuration, the configuration of the filtering delays is done through a file
named “profiles.xml”. This file is in the ring folder as the event filtering is done on a per ring basis (e.g.
c:\mcis\rings\hv_transfo_a).
File description:
The new attribute “eventdelay “for each state of one profile is added to indicate the amount of hundreds of
milliseconds to apply as filter.
Example:
One DPS with following profile:
<DPS_POSITION>
<STATE0 label="Open" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0" alarmaudible="no" />
<STATE1 label="Closed" archived="yes" printed="yes" alarmlevel="0" alarmdelay="0" alarmaudible="no" />
<STATE2 label="Jammed" archived="yes" printed="yes" alarmlevel="1" alarmdelay="0" alarmaudible="yes"
eventdelay=”2” />
<STATE3 label="Undefined" archived="yes" printed="yes" alarmlevel="1" alarmdelay="0" alarmaudible="yes" />
</DPS_POSITION>
For this DPS, the Jammed event will be delayed of 200 ms, not the other ones
If the “profiles.xml” file does not contain the “eventdelay” attribute it will be set to 0 as a default value for the state.
How to configure:
Then, to apply the new settings
• Open the EcoSUI SBUS Server
• In Acquisition tab
o Stop the acquisition
o -> Tools… -> “Load Configuration from SignalList file”
o Choose the file to load and validate the restart of the SBUS Server
7.8 CONFIGURABLE COMBOBOX FILTERING

It is possible to configure a ComboBox to filter event of Event viewer and Archive Event viewer.
Example of ComboBox
User add ComboBox in Mimic and configure the action to filter the Event viewer.
The file is always loaded as default in the ComboBox menu in EcoSUI HMI.
The ComboBox is not editable at use. The list inside the ComboBox is configured in file setted on
ComboBox_ConfigurationFilename.
Each line corresponds to one filter. Filter have three parameters separated by a semi-comma. Only * is available
for regular expression.
Example of filters:
7.9 EVENT COLORIZATION

Events can be colorized according to their alarm level (0=event, 1=alarm, 2=warning specified in the profile.xml
file).
For each level, you can define a foreground color, background and blinking color using the following parameters:
EventViewer_GravityForeColorX
EventViewer_GravityBackColorX
EventViewer_GravityBlinkX
NOTE: Alarm Clearing/Acknowledgment will remain available only in the Alarm Viewer.
7.10 PRINT EVENT LOG ARCHIVE

Two options are available:
• Print all Events (print all filtered events)
• Print Events of this page (to print event of this screen)
7.11 EXPORT EVENT LOG ARCHIVE

Export of the Event Log Archive is possible by clicking the Export button.
Three options are available:
• Export all events (filtered events)
• Export events of this page as CSV file (events shown on the screen)
• Export events of this page as a PDF file (events shown on the screen)
7.12 EXTRACT EVENT LOG ARCHIVE

The “Extract” button processes the request on the central DB to create the report according to the dates and filters
set before.
In case of too long duration for the Extract request, clicking on the “STOP" button will stop the Archive Extract.
NOTE: The Event Extraction service connects to remote Additional Central Database(s). The tree view is the
same look and feel as a local Central Database. The extraction is executed on multiple remote central databases at
the same time.
7.13 EXTRACT EVENT LOG DATE AND TIME

This allows the user to select date and time picker available in events archive viewer only using the mouse.
The user can select « From..Date » using the calendar icon.
The user can select «From..time» by clicking on up or down arrows (hours: minutes: seconds: AM/PM).
The user can select « To..Date » using the calendar icon.
The user can select «To..time» by clicking on up or down arrows (hours: minutes: seconds: AM/PM).
Date and Time are separated, if the user reaches 00:00:00 and decrease the time then it will not change the date
to previous day. At the same time, if time is 23:59:59 and the user increases the time; it will not change the date to
the next day.
The user can select time period option from the list
• Last 5 minutes
• Last Hour
• Last Day
• Last Week
• Last Month
According to the current time, each date and time will be filled correctly. If the user selects Last hour then
« From..time » time will adjust with the difference of 1 hour related to « To..time». For example look at the above
image that time in « From..time » is 8.07.55 AM and in « To..time » time is 9.07.55 AM.
7.14 EVENT LOG - LIVE DISPLAY

The Event Log Live Display shows datapoints origin, description, message and date / time that happen in real time.
Click on the “Live” button to display this information. Event are shown when they are logged and are displayed in the
event viewer.
7.15 PLAY EVENT LOG LIVE

The “Play” button starts the Live event acquisition.
There is no filter neither sorting options in the Event Log Live Display, since events are coming chronologically.
7.16 PAUSE EVENT LOG LIVE

The “Pause” button stops the live event acquisition and freezes the event log display.
There is no filter neither sorting options in the Event Log Live Display, since events are coming chronologically.
7.17 PRINT EVENT LOG LIVE

The Event Log Live Print function is active only when the acquisition is paused. The available options are:
• Print all Events (filtered events)
• Print Events of this page (events of this screen)
7.18 EXPORT LOG LIVE EXPORT

Export of the Event Log Live is possible by clicking the Export button.
Three options are available:

• Export all events (filtered events)
• Export events of this page as CSV file (only events shown on the screen)
• Export events of this page as a PDF file (only events shown on the screen)
Users are prompted to enter the path and name of the file.
8 EVENTS REPLAY (VCR)

Click the (REC) button on the HMI view to launch the VCR tool.
EcoSUI stores each incoming event in a log file (central DB). After the events are recorded, events can be
extracted according to user-defined criteria and replay the sequence to reproduce activity that has been captured.
This function is useful for analysis and troubleshooting purposes.
You can start and close event replay as many times as you want.
VCR is a tool in the HMI which allows the user to extract all the sequence events which has occurred for a specific
date and period of time.
In the above image the user clicks the (REC) and the VCR tool window is displayed as shown in the figure below.
In the EcoSUI HMI, the date and time is in black colour which is the default colour.
The user selects the date and the specific time to replay the occurred events as shown in the following image below.
Click Extract and it extracts all the sequence of events with a Begin of records to the End of records.
To note that only when the user clicks the button Extract, it is in the VCR mode and while in this VCR mode
the user is no more in the real time view.
• To note that “When the VCR tool is running, the date and time changes according to what are the
events selected in the view and it also changes the color to notify the user while in the VCR mode, if
this color remains unchanged then the user is not in the VCR mode. The date and time in red color
displayed in the below image for the user’s notification while in the VCR mode”.
8.1 FILTER EVENTS TO REPLAY

Different filtering options are possible:
• Filter events from the tree-view of the database (double click on the vertical separator to show/hide pane)
• Sort events that match text or specific criteria (double click on the horizontal separator to show/hide pane)
• Extract events over a time window
These options are described in the following sections.
8.1.1 TREE VIEW DISPLAY

Double click the vertical separation bar to show/hide the tree view of the database (it will be used as a filter).
The database tree-view appears on screen:

Filter the events by checking / unchecking boxes in the navigation tree. Only events from checked boxes will
appear in the table with the following information:
• Date of the event (Note that the default date format is yy/mm/dd hh:mm:ss:mmm)
• Origin of the event
• Object Name
• Message associated to the event
System and electrical events are visually identified by a different background color:
• = system events
• = electrical events
NOTE :In the Global EcoSUI Client mode:

• The substations retrieved are displayed in their own “Site” Tree node.
• The system data points retrieved are displayed in different “Scs” Tree nodes.
8.1.2 MATCH TEXT OR CRITERIA

Double click the horizontal separation bar to show/hide the filtering panel:
Three entry fields appear on screen:
To replay events that match a specific status or criteria, enter the list items separated by a dot (.) in the Include entry
field and press Enter to validate. Events appear on screen accordingly (below event coming from Supervision appear
on screen).
To exclude a status or criteria:

• Enter the list items separated by a dot (.) in the Exclude entry field and press Enter to validate. Events that
contain the words you typed will not appear on screen.
To highlight specific events:

• Enter the list items separated by a dot (.) in the Highlight entry field. Events appear on screen and are highlighted
with a red background.
8.2 SET TIME OPTIONS
8.2.1 START & END DATE

The user define the time window for the events extract to replay :
• Click the From drop-down arrow and select the start date from the calendar:
• Then click the To drop-down arrow and select the end date of the desired time period.
Once the desired time window is set up, click the Extract button to filter events accordingly. Events that match the
start date appear on a green background.
Click Play to replay the sequence (refer to chapter PLAY & PAUSE EVENT SEQUENCE for further information).
8.2.2 START & END TIME

The start / end time (hh/mm/ss) can also be set using the up and down arrow in the appropriate entry field.
Click the Extract button to filter events accordingly.
8.2.3 PREDEFINED TIME SLOT

A predefined time slot can be selected by a click on the button to the right of the time entry fields.
Different time slot options are available:

• Last 5 minutes
• Last Hour
• Last Day
• Last Week
• Last Month
Select the desired time option and click Extract to filter events accordingly.
8.3 PLAY & PAUSE EVENT SEQUENCE
8.3.1 PLAY EVENTS IN SEQUENCE

Once the events to be played are extracted, click the Play button.
Clicking this item from the menu will cause the current event selection to start playing.
Events in the list are highlighted in sequence to show the chronological appearance of the events.
When EcoSUI plays a sequence, the Play function stops automatically when the end of the sequence is reached
(the last event of the selection).
8.3.2 PLAY EVENTS IN A LOOP

So that the Play function automatically loops back to the beginning of the play range whenever the last
event is reached, check the Cycle option.
8.3.3 STOP EVENT SEQUENCE

To stop playing a sequence (looping or not) click the Pause button
8.4 UPDATE CURVES

If an HMI view contains a curve, check the Update Curves option to reflect changes while playing event sequence.
9 ALARMS MANAGEMENT
9.1 ALARM STATES DEFINITION
An alarm is generated by an event (e.g. a particular datapoint with a state defined during the configuration phase as
«to be alarmed “).
An alarm can be associated with each state of each datapoint. A datapoint can have different alarms for different
states, for example, a Circuit Breaker position can generate an alarm level 1 for open status and an alarm level 2
for jammed status.
While this event is still present (e.g. the previous particular datapoint is still in the same state) the alarm is « active”.
When this event disappears (e.g. the previous particular datapoint is now in another non-alarmed state) the previous
alarm is « inactive “.
An existing alarm (active or inactive), can be acknowledged by an operator to signify that it has been acknowledged.
The acknowledgement is global (written on the Central DB), i.e. once an alarm has been acknowledged, it is seen
as “acknowledge” by any alarm list on any EcoSUI HMI connected to the central DB.
An alarm can have the following states:

• Inactive: no transition, no event
• Active-unacknowledged: the cause is still present, and the active state has not been acknowledged by the
operator
• Active-acknowledged: the cause is still present, but the active state has been acknowledged by the operator
• Inactive-unacknowledged: the cause has disappeared, but the inactive state has not been acknowledged by
the operator (only available for events alarmed on appearance and disappearance)
• Inactive-acknowledged: the cause has disappeared, and the inactive state has been acknowledged by the
operator
• Inactive-active-unacknowledged: the cause has disappeared but the active state (previous state) has not
been acknowledged by the operator
For each data, only the latest alarm with a data change state is displayed. The previous occurrence of the alarm
(concerning the same data) is replaced by the last one.
9.2 PARAMETERS ASSOCIATED WITH AN ALARM

The following user-selectable parameters can be associated with each alarm definition. The values are set during
the configuration phase and can be specific to each defined alarm:
• Immediate or Differed: an « immediate “alarm is displayed as soon as it has been detected, a “differed“ alarm is
displayed only after a selectable time delay following its detection. The event associated with the alarm have to
remain present during the delay; in the other case, then the alarm will not be displayed. the delay range is from
1 to 120 seconds and can be set to particular value for each « differed “ alarm.
• Gravity level: this level is defined for each alarm allowing a hierarchical classification to deal with the urgency of
the events; the gravity level value can be: 0, 1, 2, 3, 4 or 5 (5 is the highest level and 0 means that there is no
gravity level).
• Audible or not when detected by the system, eventually with a reset after a user-selectable delay (range: 1 to 60
seconds)
The coloring and approving alarms for circuit breaker, disconnector and earthing switch are set by using the gravity
level (1, 2, 3, 4) of alarms.
Each gravity level can be defined with colors and blinking. Please refer on the § Alarm Colorization for details.
9.3 ALARM STATE TRANSITIONS
Alarm Inactive /
Cleared
AL+
Alarm Active
Unacknowledged
AL- AL-
ACK
Alarm Inactive (1) Alarm Inactive (2)
Unacknowledged Alarm Active Active Unacknowledged
Acknowledged
AL+ ACK ACK AL+
AL-
(1) only event in alarm on

appearance and disappearance
(2) others
Automatic Clear Alarm Inactive
Acknowledged AL+
Transition events:
• AL+ alarmed event appearance
• AL- alarmed event disappearance
• ACK operator acknowledgement of the alarm
• CLEAR operator clearing of the alarm
• Automatic CLEAR: automatic clearing of the alarm when the alarm is acknowledged and inactive
NOTE: « alarmed event disappears (AL-) “means that the associated data is now in another state which is not
alarmed.
9.4 ACKNOWLEDGEMENT
An operator can acknowledge an existing alarm from the EcoSUI HMI to signify that it has been acknowledged.
The acknowledgement of alarms by an operator is recorded and shown on the alarm viewer, with the user name,
date and time. Only users with ‘alarm acknowledgment’ rights can acknowledge alarms.
Clearing of alarm requires the same operator access right as for acknowledge action. The operator can also
acknowledge / clear a group of alarms
NOTE: Alarms retrieve from several remote Additional Central Database(s). The Alarms acknowledged on the
Alarm viewer are reflected on the remote central database where they are stored.
NOTE: It’s strongly recommended to add a user confirmation when configuring alarm button acknowledgment.
It could be done by setting to 1 the button_Confirm property.
9.5 CLEARING
Whatever the clearing mode, the clearing of an alarm is immediately taken into account everywhere it is involved:
the alarm is removed from the alarm list, from the last alarms window (if previously present); an update of the new
graphical state is done in all views where it is displayed.
Only users with ‘alarm acknowledgment’ rights can clear alarms.
Two clearing modes exist, automatic clearing and operator request clearing. One mode has to be selected
and is applied to complete database alarm list.
9.5.1 AUTOMATIC CLEARING

When the alarms are configured as « to be cleared automatically “, it means that when this alarm reaches the
appropriate state, it is cleared automatically without any operator action.
The cases of “automatic clearing” are:
• the alarm is in the active-acknowledged state and the alarm disappears
• the alarm is in the inactive-active-unacknowledged state and the operator acknowledges it
• the alarm is in the inactive-unacknowledged state and the operator acknowledges it
9.5.2 OPERATOR REQUEST CLEARING

When the alarms are not configured as « to be cleared automatically “, they have to be cleared by an explicit operator
action. This action is only possible when it is in the « inactive acknowledged” state.
Otherwise, it remains present in the alarm list and in the different graphical views where it is displayed.
Clearing of alarm requires the same operator access right than the « acknowledgement right “.
A global clearing procedure, which allows clearing all “inactive-acknowledged” alarms in a single operation, is
accessible through a dedicated button.
9.6 HOW TO ADD COMMENTS TO ALARMS (AND EVENTS)

EcoSUI HMI users can add comments to substation datapoint alarms and events. A column which such comment
can be added in the Alarm and Event Viewers.
To enable Comment mode, go to the EcoSUI Configuration Application Note and in The General.ini File
section, see the following parameters:
• UseCommentFeatureExtension property to select the comment mode.
• CanClearCommentedAlarms (to be used together with UseCommentFeatureExtension). This property alters

the behavior of Clear Alarm function
To configure Alarms and Event Viewers to show comments, follow the instructions in How to add a customized
(user-defined) column in the Viewers.
The content of a Comment column depends on the commented/uncommented status of the datapoint associated
with the alarm or event:
• When an alarm or an event is uncommented, the content of this new column is a clickable link which allows the
user to type a comment.
• When an alarm or an event is commented, the content of this new column is the defined comment string.
9.7 AUDIBLE ALARMS

An audible property (e.g. PC Buzzer) can be associated to the alarmed data appearance and is triggered
simultaneously with the alarm display on OI Client.
The audible alarm is activated anytime a new alarm is coming.

Audible alarms can be stopped at EcoSUI HMI level by acknowledging the audible alarms the stop klaxon button in
the control banner. This “audible acknowledgement” can be done from any EcoSUI HMI.
It is global (i.e. it applies to all the audible alarms present in the substation); it concerns only the audible aspect of
the alarm (i.e. the alarm state remains the same in the alarm list: « unacknowledged “).
The audible alarm can be performed:

• by a beeper located at each PC where the HMI software is running
• by buzzer activated by relays controlled by each substation computer and by the PC beeper
An operator can stop the klaxon by a dedicated icon displayed on HMI.
When a new alarm is coming, all EcoSUI HMI (and dedicated external buzzer) will buzz. When audible alarm is
acknowledged on one EcoSUI HMI, all EcoSUI HMI (and dedicated external buzzer) will stop buzzing.
10 ALARMS FUNCTIONS
10.1 ALARMS VIEWER
Switch to the Alarm Page by clicking the “Alarms” button in the control banner
The information is displayed in the following columns.

• Date of appearance: the date when the alarm became active.
• Date of disappearance: Information about whether the alarm is Still Active or the date when it disappeared.
• Acknowledged: to acknowledge the datapoint alarm and, information about who and when acknowledged it.
• Origin: Access path of the datapoint (the default format is Substation Name / Voltage Level / Bay Name if the
datapoint is defined at the bay level)
• Description of the datapoint information
• Message: message of the datapoint
• Level of the signal
• State: Active + Acknowledged; Active + Not Acknowledged; Inactive + Not Acknowledged; Inactive +
Acknowledged.
in the Viewers
NOTE
In the Global EcoSUI Client mode, Alarms retrieves from several remote Additional Central Database(s) are
displayed on a global view.
Alarm viewer have a play/pause to freeze the display of the viewer.

A visual information (icon "pause") appears when the viewer is paused.
Once alarm viewer is on pause no user action has effect (acknowledgement, clear, comment etc…).
10.1.1 TIME STAMPING

• Source: Time stamp is given by the equipment that generates the signal (ex: Digital input wired on a C264)
• Acquisition: Time stamp is given when Acquisition reads the signal on a different equipment through a
communication bus (ex: C264 polling signal status from an IED through a Modbus Network)
• Synchronized
• Not Synchronized
In EcoSUI Alarm viewer, the data point date is marked according to the source of the signal or the quality of date:
Sign Description
Example: 2014-03-10 15:14:56.123 (*)
10.2 ALARMS TREE FILTER

The left part of the window displays a Tree, corresponding to the database, and used as a filter. Only the alarms of
a checked box will be displayed on the Event Log Archive Display.
10.3 ALARM VIEWER HMI CONFIGURATION

There is two way to navigate into Alarm Viewer;
• The standard behavior: the vertical navigation is done with scrollbar. All alarms are filled in the queue. This is
the default configuration;
• The page mode behavior: The number of alarms displayed into alarm viewer is configurable and fixed.
In this mode, the alarm viewer has to be a fix mimic, without toolbar and scrollbar, and without any button;
The navigation between the several pages is done by configuring buttons to navigate as previous page / next
page.
Remark: All navigation buttons need to be placed in a different workspace than Alarm Viewer itself.
ALARM VIEWER – PAGE MODE DISABLED

When page mode navigation is disabled, all alarms are filled in alarm viewer queue, and navigation is done with
vertical scrollbar
ALARM VIEWER – PAGE MODE ENABLED

When page mode navigation is enabled, only the number fixed by property
AlarmControl_PageModeNbEntriesPerPage are displayed. There is no more vertical scrollbar
10.3.1 PAGE MODE CONFIGURATION

During Alarm Control configuration, find parameters named AlarmControl_PageModeEnable, set to 1 to
enable functionality and set to 0 (default value) to disable it.
When Page Mode is enabled, user can configure number of shown events using parameter
AlarmControl_PageModeNbEntriesPerPage.
By default, this parameter is set to 20, it means that only 20 events will be shown per page.
Enable or Disable page mode navigation into Alarm Viewer
AlarmControl_PageModeEnable
• 0 = Page Mode Navigation Disabled (Default)
• 1 = Page Mode Navigation Enabled
Number of alarms shown by page. Default is 20.
AlarmControl_PageModeNbEntriesPerPage
Only a numerical
10.3.2 PAGE MODE – NAVIGATION ACTION

In order to change page, new actions are available.
• AlarmControl_PreviousPage action let user to go back to previous page
• AlarmControl_NextPage action let user to go to next page

- AlarmViewerName: Name of Alarm Viewer (findable on tree view during configuration)

• Analog
• BitField
• Button
• DynamicPicture
• DynamicText
• Glass Button
• Pie
• PQDiagram
• ProgressBar
• Rectangle
• StaticPicture
• StaticText
• TankFeeder
• Textbox
• WindDirection
• WindSpeed

User wants to create an action button to switch AlarmControl0 from Workspace 3 to next page, he has to configure
it like so
10.3.3 PAGE MODE – DYNAMIC TEXT FUNCTION

Only two functions inside Dynamic Text are available.
10.3.3.1 Get Current Page From Alarm Viewer

GetCurrentPageFromAlarmViewer let user to retrieve current Page from Alarm Viewer

- AlarmViewerName: Name of Alarm Viewer (findable on tree view during configuration)

User wants to retrieve Current Page from AlarmControl0 from Workspace 3, he has to configure it like so
10.3.3.2 Get Page Number From Alarm Viewer

GetNbPagesFromAlarmViewer let user to retrieve Number of Available Page from Alarm Viewer

- AlarmViewerName: Name of Alarm Viewer (Findable on Treeview during configuration)

User wants to retrieve Number of Available Page from AlarmControl0 from Workspace 3, he has to configure it like
so

10.3.4 ALARM VIEWER – EXTERNAL ACTION

Three new actions are available for object with possible action.
• Alarm Control – Ack Current Page
• Alarm Control – Clear Current Page
• Alarm Control – Stop Buzzer
• Alarm Control – Play/Pause
• Alarm Control – Playing
• Alarm Control – New alarm received

• Analog
• BitField
• Button
• DynamicPicture
• DynamicText
• Glass Button
• Pie
• PQDiagram
• ProgressBar
• Rectangle
• StaticPicture
• StaticText
• TankFeeder
• Textbox
• WindDirection
• WindSpeed
10.3.4.1 Alarm Control – Ack Current Page

AlarmControl_AckCurrentPage allows user to ack alarms of currently page shown in an Alarm Control
This action takes 2 parameters:

- AlarmControlName: Name of Alarm Control (Findable on Treeview during configuration)

User wants to ack current page of AlarmControl0 from Workspace 3, he has to configure it like so
10.3.4.2 Alarm Control – Clear Current Page

AlarmControl_ClearCurrentPage allows user to clear alarms of currently page shown in an Alarm Control

- AlarmControlName: Name of Alarm Control (findable on tree view during configuration)

10.3.4.3 Alarm Control – Stop Buzzer

AlarmControl_StopBuzzer allows user to stop buzzer of an Alarm Control

10.3.4.4 Alarm Control – Play/Pause

AlarmControl_PlayPause allows user to pause or play alarms of Alarm Viewer depending of its current state.

10.3.4.5 Alarm Control – Playing

AlarmControl_Playing allows user to display the status of AlarmControl_PlayPause action. Value is equal to 1 if
the Alarm Viewer is playing and otherwise 0.

10.3.4.6 Alarm Control – New alarm received

AlarmControl_NewAlarmAvailable allows user to display if new alarm is available. Value is equal to 1 if the new
alarm is available, otherwise 0.

10.3.5 ALARM CONTROL – OTHER CONFIGURATION

10.3.5.1 Alarm Control – Date Only inside Ack Column
A parameter named AlarmControl_DateOnlyAckColumn allows user to show date only under Ack Column.
Default is the operator’s name who ack alarm followed by date
Set to 1 to enable Date Only Ack Column, and 0 to disable it (Default is 0)
Use Case Description

AlarmControl_DateOnlyAckColumn = 0 Operator’s name and date are displayed into Acknowledge
column (Default)
AlarmControl_DateOnlyAckColumn = 1 Only date is displayed into Acknowledge column

10.3.5.2 Alarm Control – Hide click to Acknowledge
A parameter named AlarmControl_HideClickToAck allows user to hide “Click to Acknowledge” Link button
inside Alarm Viewer
Set it to 1 to hide “Click to Acknowledge” button

Set it to 0 to show it (Default is 0)

AlarmControl_HideClickToAck = 0 Click to acknowledge link is present into Acknowledge column
AlarmControl_HideClickToAck = 1 Click to acknowledge link is not present into Acknowledge column

10.3.5.3 Alarm Control – Show Date Disappearance only

A parameter named AlarmControl_DateOnlyDisappearanceColumn allows Alarm Control to be empty if alarm
hasn’t disappeared, on disappearance, date of disappearance is shown.
Set it to 1 to enable and only show Date when alarm disappeared

Set it to 0 to have normal disappearance behavior (Default is 0)

Date of disappearance appears in cells which
AlarmControl_DateOnlyDisappearanceColumn = 0
alarms has disappear.
Other cells where alarms have not been
disappeared are not empty
Date of disappearance appears only in cells

AlarmControl_DateOnlyDisappearanceColumn = 1
which alarms has disappear.
Other cells are empty
10.3.5.4 Alarm Control – Even & Odd Mode

Alarm Control background can be configured to have different color depending of even & odd rows.
Three parameters are available for Alarm Control
• AlarmControl_EvenOddBackColorMode
• AlarmControl_EvenBackgroundColor
• AlarmControl_OddBackgroundColor
Set to 1 parameter AlarmControl_EvenOddBackColorMode to enable Even / Odd Mode
Set to 0 parameter AlarmControl_EvenOddBackColorMode to disable Even / Odd Mode (Default is 0)
If AlarmControl_EvenOddBackColorMode is enabled, alarm list background color will be colored depending of

even and odd rows and so AlarmControl_BackColor will be ignored.
To configure background color of Even / Odd, 2 parameters are available, these parameters only work when
EvenOdd Mode is enabled.
- AlarmControl_EvenBackgroundColor: Set RGB color code for even rows. Default is 168;168;168
- AlarmControl_OddBackgroundColor: Set RGB color code for odd rows Default is 192;192;192

AlarmControl_EvenOddBackColorMode = 0 Without difference between even & odd rows
AlarmControl_EvenOddBackColorMode = 1 Even and Odd background color default
AlarmControl_EvenOddBackColorMode = 1 OddBackColor = 178,178,178

EvenBackColor = 60,174,65
10.3.5.5 Alarm control – Date Mode Coloring

A parameter named “AlarmControl_DateColorMode” for Alarm Control changes the way of how alarm
colorization working, only date column will be colored.
Set it to 1 to enable it, set it to 0 to disable it (Default is 0)
If enabled
- Colorization will only consider ForeColor and ignore BackColor
- Parameters is group as follow:
- AlarmControl_GravityActiveAckForeColorX
Acknowledge Date Column
- AlarmControl_GravityActiveAckBackColorX
- AlarmControl_GravityNotActiveAckForeColorX
- AlarmControl_GravityNotActiveAckBackColorX
- AlarmControl_GravityActiveNotAckForeColorX
Appearance Date Column
- AlarmControl_GravityActiveNotAckBackColorX
- AlarmControl_GravityNotActiveNotAckForeColorX
Disappearance Date Column
- AlarmControl_GravityNotActiveNotAckBackColorX
- AlarmControl_DateColorModeGravityForeColorX
All other column
(new parameter described below)
(where X is alarm Gravity, from 0 to 4)
With this mode, only Date Column are colored, user is allowed to modify other text color by using following
parameters
- AlarmControl_DateColorModeForeColor0
These parameters work only when Date Color Mode is activated.
AlarmControl_DateColorModeGravityForeColorX: Set RGB color code. Default is 0;0;0
10.4 ALARMS INDIVIDUAL ACKNOWLEDGEMENT

The user can acknowledge alarms following its rights to acknowledge alarms.
The individual acknowledgement of an alarm is simply done by clicking on the “Click to acknowledge” blue text on
the corresponding alarm. Once an alarm has been acknowledged, the “Click to acknowledge” blue text is replaced
by a white text describing the date and the name of the user that has acknowledged the alarm.
10.5 ALARMS MULTI- ACKNOWLEDGEMENT

If the user has got the acknowledgement rights, he can access 2 global acknowledgement functions:
• Alarms Page Current Page acknowledgement, that acknowledge every alarm present on the view
• Alarms Page Global acknowledgement, that acknowledge all the alarms selected on the tree filter
10.6 ALARMS PAGE CLEAR ALARMS

User, with alarm clearing rights, can clear inactive and acknowledged alarms by clicking the “Clear Inactive &
Acknowledged” button. The clearing is global to the entire alarm list, whatever the tree filter selection applied.

AutoClearAlarms = 0 If AutoClearAlarms value is set to 0, then “Clear Inactive & Acknowledge” button option is
visible in alarm viewer of EcoSUI
An "Operator" can "Clear Inactive and Acknowledged alarms" (NACT-ACK alarms)

AutoClearAlarms = 1 If AutoClearAlarms value is set to 1, then “Clear Inactive & Acknowledge” option is not visible
in alarm viewer of EcoSUI. As soon as "Operator" acknowledges NACT-NACK alarms,
, alarm will disappear automatically and Alarm viewer will look like
For information, NACT-ACK alarms are not available anymore.
NOTE: AutoClearAlarms is a setting on Servers.ini file. Please refer the EcoSUI Configuration Application
Note to learn more.
10.7 BAY ALARM ACKNOWLEDGE & CLEAR

Alarm displayed in an alarm page may be filtered to one bay. In that case the global acknowledgement and
clearing is reduced to the alarm from this dedicated bay.
• The AlarmControl_AckClearAlarmByBayName property must be set to 1.
• In the AlarmControl_Bayname property, specify the bay name to which the alarms shown belong to.
Find hereunder the behavior of the alarm page following the values of these 2 properties:
AlarmControl_AckClea AlarmControl_Ba Behavior
Note
rAlarmByBayName yname View Action
1 1 Empty View ALL alarms Actions are performed system wide (i.e. on
all alarms list)
2 1 [Bay Name] ONLY [Bay Name] ONLY on [Bay Name] alarms
alarms
1 0 Empty View ALL alarms Actions are performed system wide, (i.e. on
all alarms list)
3 0 [Bay Name] ONLY [Bay Name] Actions are performed system wide, (i.e. on
alarms all alarms list)
NOTE 1: Recommended values in case where the alarm page displays all alarms and the action is done on alarms
NOTE 2: Case where the alarm page displays only alarm(s) of the bay and the action applied on the alarm(s) of the
bay
NOTE 3: Case where the alarm page displays only the alarm(s) of the bay and the action applied on all alarms; this
case is only used when the user wants to display the alarm(s) of a bay but to apply the global acknowledge or
clearing all alarms of the system
Important:
If the alarm tree view is displayed (i.e. AlarmControl_TreeView = 1), the selection of any items in the tree
view won’t change the behavior of the action mentioned hereabove.
E.g. the actions are performed system wide and will influence the whole alarm page and not only what have
been filtered out.
10.8 HIDE ALARMS

As an operator on EcoSUI HMI, this function is done to be able to pause an alarm in the alarmlist for a specific time,
to avoid the alarm ringing. Primarily this function is valid and can be done only in the alarm views on HMI.
The user needs to be connected as an operator to use this feature and to hide the alarms.
Hide alarm available on the alarm viewer, the user needs to right click on the alarmlist as shown in the image below.
The user presets the time (example: 1h, 4h, 6h, 12h, 24h...) in the menu as shown in the image below.
If the user for example: after selecting the Hide for preset time → Hide for 1 hour, a popup message to add a comment
if needed, appears on the screen as shown in the image below.
The comment section is available for highlighting the reason to put the alarm on standby for 1 hour by the user.
If the user for example: after selecting the Hide until date a popup message to set the Date and Time and finally a
comment if needed, appears on the screen as shown in the image below.
Once the hide alarm is preset either for Hide alarm for 1 hour / Hide alarm until Date and Time, the alarm present in
the alarm list on the alarm views highlights in orange color to represent that the alarm is in standby as shown in the
image below.
The user can if right clicks on the preset hide alarm on the alarm list which enables the option Show Alarm.
Click Show alarm and a popup message appears on the screen which displays the time set for the specific alarm
as shown in the image below, which allows the user to unhide alarm with the added comment section.
The hide alarms are shown as the event in the Event Viewer of SBUS server and HMI.
The unhide alarms are shown as the event in the Event Viewer of SBUS server and HMI.
In the toolbar of the HMI and the SBUS server, Click Alarm Status which allows the user to filter the hidden alarms
list on the alarm viewer, by selecting Hidden as shown in the figure below.
The image below represents with no orange color indicates that the alarms are no more hidden.
NOTE: To use this Hide Alarm feature, it is necessary that the person has the right for alarm acknowledgement. By
referring the table in the reference table 4 in the section 3.3.1 Default RBAC of the chapter CYBERSECURITY (CS)
in this User manual, the only person who could use this feature is the OPERATOR, who has the right for alarm
acknowledgement. What defines an OPERATOR is the fact that he can acknowledge an alarm reception.
10.8.1 HIDDEN ALARMS CONFIGURATION

The following three parameters in the table below, allows the user, the possibility to configure the hidden alarm’s
color which is the background color and the text color of the acknowledged and not acknowledged hidden alarms.
The configuration of the three parameters can be done in the Alarms Mimics Editor.
Parameter Description Values

Configures the background 250,140,0 by default values, but it is
AlarmControl_HiddenAlarmBackColor color when the alarms are configurable according to the user’s
hidden. choice of color.
Configures the text color of 255,0,0 by default values, but it is
AlarmControl_HiddenAlarmAckForeColor the acknowledged hidden configurable according to the user’s
alarms. choice of color.
Configures the text color of 0,0,0 by default values, but it is
AlarmControl_HiddenAlarmForeColor the non-acknowledged configurable according to the user’s
hidden alarms. choice of color.
By default, the uniform color of the hidden alarms background and text color of acknowledged and not acknowledged
hidden alarms are shown in the following image.
The below image represents alarms viewer with the three different colors of the hidden alarms after the configuration
of the three parameters in the Mimics Editor of the Alarms.
Below image is another example of the representation of the alarm’s viewer in which the hidden alarms color for the
background color and the text color of the acknowledged and not acknowledged alarms.
10.9 ALARMS PAGE PRINT

Alarms printing functions are reachable through the Print button. The two options are:
• Print all Alarms (filtered alarms)
• Print Alarms of this page (print alarms shown on the screen)
10.10 ALARMS PAGE EXPORT

Alarms export functions are reachable through the Export button. The two options are:
• Export All Alarms to a .CSV file (filtered alarms)
• Export Alarms of this page to a .CSV file (only export alarms visible on the screen)
10.11 STOP BUZZER FUNCTION

Clicking on the “Stop Buzzer” button stops the Buzzer according to user rights. It is disabled if the operator has not
sufficient rights. The Audible alarm function is still active, and a new alarm will switch on again the buzzer.
Note that the Stop Buzzer function is spread to EcoSUI HMIs sharing the same database.
10.12 TOGGLE MUTE FUNCTION

Clicking on the “Toggle Mute” button deactivate the Audible alarm according to user rights. This option is useful in
case of maintenance operations for instance.
Note that the Toggle Mute function will only affect the EcoSUI HMI on which the user operates. It is not linked to a
specific user and is not visible outside the alarm page.
The above Toggle Mute function only activate/deactivate the local buzzer associated to the local HMI.
The buzzer is a central component of the alarm management, i.e. when an alarm status requires the buzzer to be
activated, all connected HMI will activate their own local buzzer.
The operator has the facility to mute the Buzzer (all connected HMI’s buzzer) without acknowledging associated
alarm, by set or reset the SPS “System / SUPERVISION / Buzzer Muted”. This system SPS status is only settable
by mean of the formula "SET" and "SETIN" (default: 0 = Buzzer deactivated / 1 = Buzzer activated).
10.13 LAST ALARMS WINDOW ALARMS DISPLAY

The last alarm window is always present on the EcoSUI HMI, whatever the view displayed, or the function called.
the alarm behavior is the same as the alarm one in the Alarm Page Alarms Display. A user with acknowledgement
rights can acknowledge alarms by clicking the “Click to acknowledge” blue text on the corresponding alarm.
Once an alarm has been acknowledged, the “Click to acknowledge” blue text is replaced by a white text describing
the date and the name of the user that as acknowledge the alarm.
10.13.1 TEXT FILES FOR ALARM MANAGEMENT

In addition to Alarms Page, alarms can be generated in text files. A heartbeat can be generated periodically and a
list of alarms is defined. Each time an alarm of the list or the heartbeat occurs a new text file is created. These alarms
are used as an input for any other system tools able to catch these text files.
The Operator has to edit the following configuration files:

• General.ini
• “ListofAlarmsFileAFE”.csv
Configuration files:
This feature is defined in General.ini file (C:\MCIS\General.ini)
The AlarmFileExport part, specifies the condition to generate alarms in text files
• EnableAlarmFileExport enables the feature (1) or disables (0: default)
• AlarmFilesFolderAFE defines the name of the folder which contains the text alarm files
• ListofAlarmsFileAFE defines the name of the configuration file which list the alarms to generate in text files; the
file is generated in the “AlarmFilesFolderAFE” folder
• Heartbeat enables the heartbeat generation (1) or disables (0: default)
• HeartbeatTick defines the heartbeat cycle time of generation of the heartbeat alarm text file (1-120 in minutes)
The list and the definition of the alarms to generate are defined in the “ListofAlarmsFileAFE” csv file in the
“AlarmFilesFolderAFE” folder.
• the Data point is the name of the information in alarm defined in EcoSUI
• the Alarm message is the free text to write in the field “alarm message“ of the text alarm file
• the Priority is the free number to write in the field “AlarmPriority“ of the text alarm file
• the Status is the status value of the alarm defined in EcoSUI
Alarm
message
Data Point Status
Priority
NOTE: In case of redundancy, Text Alarms Files are created in both servers. And the file “ListofAlarmsFileAFE”.csv
has to be duplicated in both servers.
Output alarm text files:
The alarm is generated in a text file created in the “AlarmFilesFolderAFE” folder. One file is created every time the
alarm occurs.
• A heartbeat alarm file:
• An alarm file:
10.14 ALARMS COLORIZATION

Alarms can be colorized according to their:
• Gravity Level (see note) and
• State (Active + Acknowledged, Active + Not Acknowledged, Inactive + Not Acknowledged, Inactive +
Acknowledged).
NOTE: The operator can choose / configure the gravity level for each alarmed state depending on the situation’s
criticality.
For each gravity level and each alarm state, operator can define a foreground color, background and blinking color
using the following mimic edition parameters:
ALARM ALARM ALARM DESCRIPTION

GRAVITY STATE COLOR / BLINK PARAMETERS
1 Active + AlarmControl_GravityActiveAckForeColor1 foreground color (RED by default)

Acknowledged AlarmControl_GravityActiveAckBackColor1 background color (WHITE by default)
AlarmControl_GravityActiveAckBlink1 blinking color of alarm state (no blinking
=0, blinking=1)
Active + AlarmControl_GravityActiveNotAckForeColor1 foreground color (WHITE by default)
Not Acknowledged AlarmControl_GravityActiveNotAckBackColor1 background (RED by default)
AlarmControl_GravityActiveNotAckBlink1 blinking color of alarm state (no blinking
=0, blinking=1)
Inactive + AlarmControl_GravityNotActiveNotAckForeColor1 foreground color (BLACK by default)
Not Acknowledged AlarmControl_GravityNotActiveNotAckBackColor1 background color (GREEN by default)
AlarmControl_GravityNotActiveNotAckBlink1 blinking color of alarm state (no blinking
=0, blinking=1)
Inactive + AlarmControl_GravityNotActiveAckForeColor1 foreground color (BLACK by default)
Acknowledged AlarmControl_GravityNotActiveAckBackColor1 background color (GREEN by default)
=0, blinking=1)
=0, blinking=1)
=0, blinking=1)
ALARM ALARM ALARM DESCRIPTION

GRAVITY STATE COLOR / BLINK PARAMETERS
=0, blinking=1)
=0, blinking=1)
=0, blinking=1)
=0, blinking=1)
=0, blinking=1)
=0, blinking=1)
NOTE: Colors for the gravity level = 5 are defined by default and are not modifiable.
To change parameters value, please follow the procedure:
ACTION NOTE
• EcoSUI HMI Login with the configuration
1
Administrator only.
• Access to the ALARMS viewer
• Activate the “Edit Mode” - CTRL + SHIFT + ALT +
2
F12.
• A popup window prompts the user to enter his
3
password (the same as the one used to log to the
system)
• Button OK twice
• Right-click anywhere in the HMI view,

4
• Select Unlock Mimic,
• Double-click on Alarms Viewer; The Mimic Editor
window is displayed
• Edit parameter(s) from tree AlarmControl >

5 Parameters start with AlarmControl_Gravity prefix
AlarmControl0
Please see Figure below
• Quit the Mimic Editor Window
6
• Right-click
7
• Select Lock Mimic
Parameters are saved.

10.15 ALARMS ADVANCE FILTERING

The advance filtering is implemented by a filtering bar (see figure below).
Advance filtering function is applied by clicking on filters:
• Text filter
• Date “From To” filter
• Current Day filter
• Custom Time filter
• Alarms Status (specific for Alarms viewer)
1 3 5
2 4 6
NOTE
• A witness button informs operator the status of filtering / reset filters.

• By default, the filtering bar is set to hide.
• The filtering bar can be moved by mouse pointing on the left corner and click-left action.
Witness and reset filter:
This button allows user to signal the status of filtering:
• inactive = GREY color, all alarms are displayed on the view

1
• active= RED color, partial alarms are displayed on the view
Also, if click-on, will reset the current filtering.
Note: In active mode, a blinking effect can be set by AlarmControl_AdvFilterBlinkButton parameter.
Text filter:
2 This filtering is applied for Description and Message columns only. Operator fills the “text string” in the Filter field
and press return. The event view is refreshed with “text string” only.
Alarm Status filter:
This filter is specific for Alarms
Viewer, and is applied to column
State.
Options available:
• All: Shows All alarms OR shows Active, Inactive, Acknowledge, Not Acknowledge
• Preset: This function stores (or delete) custom Event filter criteria defined by operator in order to avoid redefine
it on HMI. After saving operation, operator creates name of custom criteria. Operator can select a name from
list to apply directory filtering.
Date From To filter
4 This filtering displayed events from start
to end dates. Operator sets time values by clicking on From and To (calendar and Time buttons)
Current Day filter:
5
The button “Current Day” displayed only events within the current date / today filtering (time from 00h00 to 23h59).
Custom Time filter:
This filtering displayed latest events for custom time duration. Operator fills the
“Last” field with 2 digit and choose the temporal scale option:
• minutes
6
• hours
• days
• weeks
• months
The Advance filtering bar can be configured to show or hide filters. By default, the filtering bar is hidden.
The configuration uses several parameters:
• AlarmControl_Advanced Filtering
• AlarmControl_AdvFilterConfiguration
• AlarmControl_AdvLastConfiguration
• AlarmControl_AdvFilterBlinkButton
Show or Hide the Advanced filtering bar
The value is:
AlarmControl_Advanced Filtering
• 0 = filtering bar is hidden (by default)
• 1 = filtering bar is visible
Show or hide Advanced filter(s) inside the toolbar
There are 6 values separated by a semi-colon (;)
Each value is:
• 0 = filter is hidden (by default)
• 1 = filter is visible
The first value hides / shows Witness and reset filter
The second value hides / shows Text filter
The third value hides / shows Alarm Status Filter
AlarmControl_AdvFilterConfiguration The fourth value hides / shows Date From To filter
The fifth value hides / shows Current Day filter
The sixth value hides / shows Custom Time filter
Setting example 1
AlarmControl _AdvFilterConfiguration = 1;1;1;1;1;1
All filters are visible.
Setting example 2
AlarmControl_AdvFilterConfiguration = 0;1;1;0;1;0
Text filter, Alarm Status filter and Current Day filter are visible.
NOTE: if all values are set to 0, the Advanced filter bar is hidden.
This parameter contains the Custom Time filter value. When viewer is
loaded, the Last XX filter will be automatically applied with the value.
The parameter has 2 values separated by a semi-colon (;)
The first value is the temporal duration on 2 digits
The second value is the temporal unit:
• minutes
AlarmControl_AdvLastConfiguration • hours
• days
• weeks
• months
Setting example
= 20;minutes
Displays latest 20 minutes alarms
This parameter makes visual effect on button static / blinking
AlarmControl_AdvFilterBlinkButton The value is:
• 0 = button is not blinking (by default)
• 1 = button is blinking
11 CURVES
Curves tool allows the user to study trends of any signals supervised by the EcoSUI
Curves tool can display up to 8 curves on a single display. Two options are possible:
• Curves set by configuration, not user customizable. This type of curve appears in detailed views. Navigation
buttons allow direct access to curves
• Curves tool page with menu, giving the user the ability to create / modify its curves settings
By default, curves are modifiable (signals, period of time…) according to user privileges. The following information
concerns the user configurable curves option.
11.1 CURVES TOOL DISPLAY

The following picture shows an example of a user configurable curves window.
The function menu on the top bar is hidden in the case of non configurable curve window.
To display trend curves, two options are possible here:

• Configure a new set of curves (and save it if useful)
• Load an existing set of curves
A time duration is required and the “Extract” button update automatically the chosen set of curves.
11.2 CONFIGURE A SET OF CURVES
To configure a new set of curves, click on the tool curve button and select “Properties”:
Then the user can specify

the following parameters for
the selected curve:
The following parameters could be assigned to a curve:

• Signal origin: Link to the IEC 61850 analog to be represented
• Legend
• Min value / Max value
• Format (decimals)
• Unit
• Colors
• Scaling Coefficients applied to the values
Clicking the button applies the parameters selection to the selected curve.
Clicking the button cancels the parameters selection and closes the window.
11.2.1 SELECT PEN

The user can assign properties to one of the 8 possible curves from the scrolling bar. Here
11.2.2 ACTIVE CURVE DISPLAY

When the “Active” property is checked, the selected curve is displayed on the trends display; when it is unchecked,
the selected curve is not visible.
11.2.3 SIGNAL SELECTION

The user choose the analog signal to display on the Curves page by clicking the “…” button will open the “Signal
Selection” dialog box.
Navigate in the signals list with the tree viewer and select the desired signal.
Double click on the highlighted signal to confirm your choice
User also can use the “Description Filter” to ease search. And/or use the “Signal Category” scrolling menu.
Printing and Export allows to print and export data.
The signal name and its legend are automatically filled. Legend can be modified as desired.
11.2.4 CURVES LEGEND OPTIONS: MIN/MAX, FORMAT AND UNIT

The user can customize the curve legend: Minimal and Maximal values, digit format and displayed unit.
V1
V1
200
kV
1 1
See below a graphical effect of the previous setting
11.2.5 COLOR SELECTION

The user can define the curve color for a better visualization. Click on the “…” button and a Color Selection window
appear as shown below. Select the desired color and press OK. Personal colors (RGB code) are available:
11.2.6 COEFFICIENT SELECTION

The user can apply a scaling coefficient to a curve. In the following example, a ¾ coefficient will be applied to the
selected curve.
Setting range for A & B coefficient is within the limits of the integer 32 bits.
11.3 CURVES VIEWER HMI CONFIGURATION
11.3.1 CURVES – EXTERNAL ACTION

Actions available:
• Trend viewer control - Curve_Print
• Trend viewer control - Curve_Export
• Trend viewer control - Curve_Forward
• Trend viewer control - Curve_Backward
• Button
• Rectangle
Curve_Print
Curve_Print allows user to print curve of a trend viewer control.
Curve_Export
Curve_Export allows user to export curve of a trend viewer control.
Curve_Forward
Curve_Forward allows user to move forward the trend viewer time scale.
Curve_Backward
Curve_Backward allows user to move backward the trend viewer time scale.
- CurveControlName: Name of Trend viewer Control (Findable on Treeview during configuration)
11.3.2 CURVES –SHOW/HIDE ACTION BUTTONS
Page control action
It is possible to show or hide buttons on Trend Viewer object. To show or hide buttons, use the corresponding
parameter.
Parameters:
• Curve_ShowPrevIcon set to 0 to hide the button, set to 1 to show the button action “Previous scale of curve”.
• Curve_ShowNextIcon set to 0 to hide the button, set to 1 to show the button action “Next scale of curve”.
The parameter Curve_ShowNextandPrevIcons have to be set to 1 to show any of these icons, otherwise icons are
hidden.
Toolbar icons
It is possible to show or hide the buttons of the Trend Viewer toolbar.

Use parameter Curve_AdvFilterConfiguration to show or hide button.
The format of value to set follow this pattern: 1;1;1;1;1;1;1. There is 7 value separated by dot comma character “;”.
Each value corresponds to an action or group of action, set value to 1 to show and 0 to hide:
• Value 1: show or hide icon “New set of Curve”
• Value 2: show or hide icon “Load set of Curve”
• Value 3: show or hide icon “Save set of Curve”
• Value 4: show or hide icon “Print”
• Value 5: show or hide icon “Export” and “Export as PDF”
• Value 6: show or hide icon “From to To Filter”
• Value 7: show or hide icon “Extract” and “Extract continuously”
Example:
Curve_AdvFilterConfiguration = 1;1;0;1;0;1;1
Meaning:
• icon "New set of Curve" => Shown
• icon "Load set of Curve" => Shown
• icon "Save set of Curve" => Hide
• icon "Print " => Shown
• icon "Export" and "Export As PDF" => Hide
• icon "From to To Filter" => Shown
• icon "Extract" and "Extract continuously" => Shown
11.4 CREATE A NEW SET OF CURVES

This button allows the user to create a new set of curve while erasing the previous one. If the user has configured a
set of curves previously, it has to be saved before clicking on the “New set of curve” button.
11.5 LOAD A SET OF CURVES

This allows the user to load a previously saved set of curves. Click on the “Load set of curves” button will open the
File Manager window. The file type for Curve configuration files is .CRV.
Choose the .CRV file on your computer storage devices then click “Open”. The Set of curves is loaded and
displayed.
11.6 SAVE A SET OF CURVES

This allows the user to save the current set of curves. Click on the “Save set of curves” button will open the File
Manager window.
Choose the location on your computer storage and type the name of the .CRV file to be saved then click “Save”.
11.7 PRINT CURVES

This allows the user to print the current set of curves or save it save in pdf format. Click on the “Print” button will
open the Printer window. Choose the printer, set the desired parameters, and then click on “Print”. It also allows the
user to export the files and export the curves in the PDF format.
11.8 EXPORT CURVES

This allows the user to export the properties of selected curves by generating a .CSV file containing the numeric
data of the selected curves.
• Click on the “Export” button will open the Export properties window.
• Check/Uncheck the Curve box to select curves then click “Export”.
Choose the location on your computer storage and type the name of the .CSV file to be saved then click “Save”.
See below the content of a CSV file:

11.9 SET DATE AND TIME

This allows the user to select date and time picker available in events archive viewer only using the mouse.
The user can select « From..Date » using the calendar icon.
The user can select «From..Time» by clicking on up or down arrows (hours: minutes: seconds: AM/PM).
The user can select « To..Date » using the calendar icon.
The user can select «To..Time» by clicking on up or down arrows (hours: minutes: seconds: AM/PM).
Date and Time are separated, if the user reaches 00:00:00 and decrease the time then it will not change the date
to previous day. At the same time, if time is 23:59:59 and the user increases the time, it will not change the date to
the next day.
The user can select time period option from the list
• Last 5 minutes
• Last Hour
• Last Day
• Last Week
• Last Month
According to the current time, each date and time will be filled correctly. If the user selects Last 5 minutes then
« From..time » time will adjust with the difference of 5 minutes related to « To..time». For example look at the time
in « From..time » is 11.04.12 AM and in « To..time » time is 11.09.12 AM.
11.10 EXTRACT OPTIONS

It extracts and shows the curves for the time period specified before with the calendar windows.
11.11 EXTRACT CONTINUOUSLY OPTIONS

It starts the permanent scrutiny of selected curves.
Different predefined period of time and recording rate are available:

• Extract 5 minutes every 2 seconds
• Extract 30 minutes every 10 seconds
• Extract last hour every minute
• Extract last day every 15 minutes
• Extract last 2 days every 30 minutes
11.12 WORKING WITH CURVES
11.12.1 SELECTED CURVE DISPLAY OPTIONS

A left click on any curve properties button highlights the selected curve:
Another mouse click will reset this display action.

Right clicking on any curve properties button, for instance, will open the selected curve display options
window:
The available options are:

Scale :
• Scale / Draw this Scale: Display this scale in the Legend
• Scale / Draw all Scales: Display the scales of all curves in the Legend
• Scale / Change Scale from Maximum to Minimum: Adjust the scale to Maximum and Minimum values of the
curve
• Scale / Change Scale to default: Reset scale to the default settings configured in Properties
Signal :
• Signal / Properties: Open the Curve Properties window to modify the curve configuration
• Signal / Show points: Show the recorded points on the curve
• Signal / Hide: Hide the curve (still active but hidden)
Note that EcoSUI cannot display separated curves (power, current, voltage) in the same display area.
11.12.2 GRIDS OPTIONS

A right click on the display area will open the following window:
The user can choose to display or not the horizontal grids by checking/unchecking the Draw Horizontal Grids box.
11.12.3 ZOOM OPTIONS

The Curves display offers Zoom Area possibility.
Using the mouse, the user defines the area he wants to zoom in.
This the zoomed area
The Zoom Out function is also available from the same right click window.
11.12.4 CURVES INFORMATION DISPLAY

The user can display curves points information by clicking on any curve. Clicking again on the curve will reset this
information display.
Here are displayed Time, Duration and Voltage for both curves.
11.12.5 SCALES OPTIONS

The Change all scales from Maximum to Minimum function adjusts the scale to maximum and minimum values
of all active curves.
Change all scales to default resets the scale to the default settings for all active curves.
12 HELP VIEWS
To better understand EcoSUI HMI, help views are available. They show the legend of the different SYSTEM and
ELECTRICAL equipments used in the different EcoSUI HMI views.
Typically, one help view is dedicated to the SYSTEM equipments, while the other one stands for the ELECTRICAL
devices.
Example of Help Views:

13 NAVIGATION
Navigation is the term used when switching from a view to another on EcoSUI HMI.
13.1 NAVIGATION WITH THE NAVIGATION BANNER
Navigation in the EcoSUI HMI can be done through the navigation banner:
Clicking a button displays the corresponding view on the main mimic window of the EcoSUI HMI. The Navigation
banner is customizable on a per project basis.
13.2 NAVIGATION WITH THE MIMIC BUTTON

It is possible to navigate directly from the any mimic window (here it is an example of a main mimic), by clicking on
a button on the mimic itself.
Navigation
buttons on the
mimic itself
13.3 NAVIGATION WITH MIMIC SENSIBLE AREAS

It is possible to navigate directly from the main mimic window (see below an example of a main mimic) by clicking
on a sensible area.
Sensible area
behaves like a
navigation button.
13.4 NAVIGATION WITH KEYBOARD ARROWS

Use keyboard arrows to move from one configured-action object to another highlighting them during the process.
When highlighted, press Enter key to perform object configured action.
Example:
An object with configured action SHOW 3 when highlighted and Enter key is pressed, MyMimic.cfg will load
MyMimic.cfg in Workspace 3.
The following list explains how navigation works when using the keyboard:
• Navigation will always start with the first object at the top left of the mimic.
• On grouped items, every configured-action object is detected, and HMI will navigate through them.
• On reaching end border, and going further than workspace:
o If another workspace is available, HMI will jump on it, and highlight first top left object.
o If no workspace is available, HMI will stay at position.
• On opening a new Mimic, it will select first top left configured-action object on the newly opened mimic.
To activate arrow navigation on EcoSUI HMI user has to configure a parameter named
EnableNavigationWithArrowKeys in [General] section inside General.ini file from Mimics folder (commonly
located under C:\MCIS\Mimics).
To enable EnableNavigationWithArrowKeys parameter, set value to 1:
…
[General]
EnableNavigationWithArrowKeys=”1”
…
13.5 NAVIGATION WITH KEYBOARD SHORTCUTS

User can create Keyboard Shortcuts to activate certain configured-action objects.
Keyboard shortcut feature is available for the following objects:
• ProgressBar
• Rectangle
• Button
• Glass Button
• StaticPicture
• DynamicPicture
• StaticText
• DynamicText
• Analog
• Pie
• PQDiagram
• BitField
• Textbox
• WindSpeed
• WindDirection
• TankFeeder
These objects have two parameters respectively named _Keyshortcut_KeyDown and _Keyshortcut_KeyUp:
13.5.1 HOW TO CREATE KEYBOARD SHORTCUT

Keyboard shortcut parameter is to be configured with Keycode. For example, if user wants to perform an action
using A key:
Button_Keyshortcut_Keydown 65
65 is the ASCII Keycode of A character, please find a common ASCII table of
This is an extract of the table of ASCII keycodes (in blue):
A 65 I 73 Q 81 Y 89
B 66 J 74 R 82 Z 90
C 67 K 75 S 83
D 68 L 76 T 84
E 69 M 77 U 85
F 70 N 78 V 86
G 71 O 79 W 87
H 72 P 80 X 88
1 49 9 57 Numpad 7 103 F5 116

2 50 0 48 Numpad 8 104 F6 117
3 51 Numpad 1 97 Numpad 9 105 F7 118
4 52 Numpad 2 98 Numpad 0 96 F8 119
5 53 Numpad 3 99 F1 112 F9 120
6 54 Numpad 4 100 F2 113 F10 121
7 55 Numpad 5 101 F3 114 F11 122
8 56 Numpad 6 102 F4 115 F12 123
User can use the following modifiers to create keyboard shortcut combinations (SHIFT, CTRL and ALT Keys):
Key Modifier
SHIFT 16
CTRL 17
ALT 18
Because of a limitation in EcoSUI HMI, to configure a keyboard shortcut combination, & character is used to
separate key codes. For example, to create CTRL + ALT + P keyboard shortcut combination, do as follows:
Parameter Keyboard shortcut combination

Button_Keyshortcut_Keydown 17&18&80
14 OBJECT DISPLAY
According to the rights associated to the user, any object (dynamic or static) can be displayed or not.
Objects are defined by their type, their position, and potentially a link to a file, a link to an IEC 61850 data or
whatever, depending on the object type.
EcoSUI HMI can display numerous types of data, such as:

• Single Point Status (SPS)
• Double Point Status (DPS)
• Multiple Point Status (MPS)
• Measurement Values (MV)
Datapoints status can be displayed on the EcoSUI HMI to represent dynamic objects, such as CB position, Analog
values, devices status, etc…
The datapoint actual value is read directly on the SBUS Server.
SBUS Server
EcoSUI HMI
CAUTION
Ensure that the graphical representation associated with the different states of datapoints
is clearly discriminable on the graphical user interface.

15 CONTROLS
According to the rights associated to the current user, any object (dynamic or static) accepts controls or not.
15.1 GENERALITIES
Each object defined in EcoSUI HMI has an Action property and an ActionProfile property.
Note: the ActionProfile is reserved for future evolutions.
EcoSUI HMI has Actions that let users send controls, delete/substitute datapoints. EcoSUI HMI exposes also
some Actions that let users Bypass Interlock/SynchCheck for some controls.
It’s possible to disable buttons with simple equations to avoid sending ‘useless’ controls (ie. Close control on
already closed device, Open control while restricted by the interlock…). In these equations, we can use any
datapoints like interlock SPS, order running SPS, open/close device position, etc…
Control Feedback is given through a special dynamicText object. Non exhaustive list of feedbacks:
• Success ! Order executed
• Order In Progress
• Failed ! Device is Disconnected
• Failed ! Device Failed to Operate
• Failed ! Position Reached
• Failed ! Command Already In Execution
• Failed ! Object not selected
• Failed ! Invalid Position
• Failed ! Blocked by Interlockings
• Failed ! Blocked by SynchroCheck
• Failed ! Blocked by Switching Hierarchy
• Failed ! Step Limit
• Failed ! The Limit is Over
• Failed ! Computer not Ready
• Failed ! Automation Running
• …
EcoSUI HMI sends the control to the SBUS Server and SBUS Server reports back the feedback status to EcoSUI
HMI.
Sends orders
Returns information
SBUS Server
EcoSUI HMI
CAUTION
Before using a new or modified configuration, make sure that the equipment configuration
is consistent with each other at system level.
15.2 CYBER SECURITY

If user doesn’t have right to make a control, a popup message appears.
For more information, please see Chapter Cyber Security (CS).
15.3 POP-UP CONTROL WINDOWS

Control buttons (Local/Remote control for instance) or sensible area around a controllable device (circuit breakers,
disconnectors for instance) are available on Views display area every time they are needed.
They are configured according to the project requirements to give the user the control of the substation. User rights
allow the user to control or not these devices.
Here are a few examples
15.3.1 CONTROL POPUP AUTO CLOSE

The control popup can be automatically closed without operator confirmation.
The auto close feature of the control windows on the EcoSUI HMI depends:
• If feedback is associated to the control
• On success or not success of the control
Two properties of the Mimic object specify the condition to auto close the popup window
• General_HidePopupOnCommandSuccess
• General_HidePopupOnCommandSuccessOrFailure
Find hereunder the behavior of the control popup window following the values of these 2 properties:
Note General_HidePopupOnCom General_HidePopupOnComman Behavior

mandSuccess dSuccessOrFailure Popup window auto close action
1 0 0 Never done, manual closing
2 1 0 Done if feedback and control success
3 0 1 Always done even if without feedback or
1 1 control without success
NOTE 1
Recommended values in case of popup windows only closed by an “Exit” or “Close” button
NOTE 2
Case where a feedback is associated to the control; the popup control window is closed automatically if positive
feedback and success of the control
NOTE 3
Recommended values if the behavior is to close the popup window whatever the result of the control
15.4 DIRECT EXECUTE ACTION

We have one Action.
DatapointName;0 or 1 -> Send 0 (OFF or RESET) or 1 (ON or SET) to the xPC
Remark: In the equation that permits to enable/disable the button, the configuration engineer may have to put:
• interlock xPS, to avoid sending the control if it is not allowed
• order running xPS, to avoid sending the control if the control has already been done
• device position xPS, to avoid sending a close control on a closed device or open control on an open device
CAUTION
Make sure that the control, to be triggered by direct order DO, can be executed without
confirmation.

15.5 SELECT BEFORE OPERATE ACTIONS

We have 3 different Actions.
SBO_SELECT DatapointName;0 or 1 -> Select xPC

SBO_EXECUTE -> Execute xPC
SBO_CANCEL -> Cancel xPS Selection
The common usage is a popup with 4 buttons:

• Button to Select Open
• Button to Select Close
• Button to Execute
• Button to Cancel
Remark: Like for Direct Execute, in the equation that permits to enable/disable the selection buttons, the configuration
engineer may have to put:
An additional signal can be put in the equation of execute and cancel buttons:
• Status of the selection (ie. Device is selected or not) to enable execute and cancel buttons only if the device is
selected.
CAUTION
Make sure that user access rights are granted in accordance with their roles.

15.6 ‘FAKE’ SELECT BEFORE OPERATE

For devices that do not propose Select Before Operate controls, it is possible to simulate this behavior. It is done
internally in EcoSUI HMI.
There is a shared token (for uniqueness) that avoids selection when a device is selected by another EcoSUI HMI.
We have 3 different Actions.
CMD_SELECT DatapointName;0 or 1 -> ‘Fake’ Select xPC

CMD_EXECUTE -> Execute xPC
CMD_CANCEL -> Cancel xPS Selection
The common usage is a Popup with 4 buttons:

• Button to Select Open
• Button to Select Close
• Button to Execute
• Button to Cancel
Remark: Like for Direct Execute, in the equation that permits to enable/disable the selection buttons, the configuration
engineer may have to put:
An additional signal can be put in the equation of execute and cancel buttons:
EcoSUI HMI Internal status of the selection (ie. xPC is selected or not) to enable execute and cancel buttons only if
the device is selected.
15.7 BYPASS INTERLOCK ACTION

With EcoSUI HMI, the bypass Action can be sent at anytime.
We have one Action.
BYPASS_INTERLOCK -> Commands (Direct or SBO) will be sent with the ‘bypass interlock’ attribute until the
popup is closed.
Of course, the Bypass button should have a special permission (for users with bypass rights).
The equation of this button should have:

interlock xPS. The button should be enabled only if the interlock is not allowed.
15.8 BYPASS SYNCHROCHECK ACTION

With EcoSUI HMI, the bypass Action can be sent at anytime.
We have one Action.
BYPASS_SYNCHROCHECK -> Commands (Direct or SBO) will be sent with the ‘bypass Synchrocheck attribute
until the popup is closed.
Of course, the Bypass button should have a special permission (for users with bypass rights).
WARNING
Ensure that the Bypass granting rules are set according to the user’s authorization level
and system criticity.
Failure to follow these instructions can result in death, serious injury, or equipment
damage.
15.9 SUPPRESS AND SUBSTITUTE ACTIONS

EcoSUI manages SUPPRESS and SUBSTITUTE (but doesn't manage FORCE).
The user can manage FSS actions through different ways:
• Using actions "SUBSTITUTE", "UNSUBSTITUTE", "SUPPRESS", "UNSUPPRESS"
• From the State Viewer
15.9.1 SUBSTITUTE / UNSUBSTITUTE, SUPPRESS / UNSUPPRESS ACTIONS

We have 2 Actions for SUPPRESS / UNSUPPRESS
SUPPRESS datapoint;value;quality
UNSUPPRESS
We have 2 Actions for SUBSTITUTE / UNSUBSTITUTE
SUBSTITUTE datapoint;value;quality
UNSUBSTITUTE
15.9.2 FROM THE STATE VIEWER

To use this feature from the State Viewer, you need first to enable it in the following StateViewer Object
Properties:
• ShowSubstituteInContextMenu
• ShowSuppressInContextMenu
Then start a State Viewer and right click a signal.

A pop-up will allow to suppress/unsuppress/substitue/unsubstitue the signal:
15.10 SETPOINT FUNCTIONS

With EcoSUI HMI the Setpoint actions can be sent.
Below the list of Actions for the Setpoint functions are as following:
"SETPOINT",
"SETPOINT_INT",
"SETPOINTEX",
"SETPONTEX_INT",
"SETPOINTFROMTEXTBOX",
"SETPOINTWITHCONSTANT",
"SETPOINT_TRANSMISSIONFORMAT".
Here,
❖ For the Action “SETPOINT”, the “Mnemonic”: Default Value: Coef. are used to send a Set Point.
• Mnemonic is the datapoint address.
• Default Value is the value set by default which the user wants to display on the textbox.
• Coefficient – are the co-efficients that will be applied to the value the user enters in the textbox before sending
it to the device.
• Use “SETPOINT_INT” for integer only Set Points. It means the set point the user wants to enter is only
integer, it sets a specific behavior for the textbox allowing only the integer and no digital.
❖ For the Action "SETPOINTEX", the “Mnemonic”: Min: Max: Coef. are used to send a Set Point.
• Min: Max: for this function the min/max values are allowed, if the user enter the value out of the min/max
value range, it notifies the user that the entered value is not correct and not within the min/max value range.
• Use "SETPONTEX_INT" for integer only Set Points.
❖ For the Action "SETPOINTFROMTEXTBOX", the “Mnemonic”: TextBoxID: Min: Max: Coef. are used.
• This “SETPOINTFROMTETBOX” is used to send a value for the set point taking a value from the existing
textbox that is on the HMI (Mimic). It will not display a new textbox to enter the value, it will take directly the
value entered in the textbox defined on the mimic to send a value for the set point.
❖ For the Action "SETPOINTWITHCONSTANT”, the "Mnemonic": Constant Value, sends a set point to the
Mnemonic.
• It sends a constant value, when the user clicks on the button to send a set point it takes the value defined in
the constant value.
❖ For the Action "SETPOINT_TRANSMISSIONFORMAT”
• Normally the user can configure a setpoint in datapoint from HMI, when the user sends a setpoint to IED,
he should specify the format of the sent value.
• To know the format of the setpoint, the information is found in the SCD. Before by default “float” is sent.
Now the user has the possibility to search the format information from SCD and force the setpoint format to
send the setpoint with this format to the IED correctly.
15.11 SNMP MONITORING AND CONTROL

EcoSUI manages the SNMP monitoring and control in SNMP ring. EcoSUI manage SNMP version V1, V2 and
V2C.
The user can manage the SNMP monitoring and control
• Using “SETSNMP” action.
• From Mimic editor, it is executed via button on the signal mnemonic by sending value compatible with the
mnemonic.
15.11.1 SNMP MONITORING AND CONTROL PRECONDITIONS

• SBUSServer and SNMP ring have to be configured. The ring will contain ring.ini, profiles.xml, signallist.
• SNMP device will have to be configured in a host file.
• Engineer have to check if the OID is writable.
NOTE: See EcoSUI Configuration Application Note.

1. Refer to the chapter 4 about signallist file to get additional information on the possible parameters.
2. Refer to the chapter 5 about ring.ini file to get additional information on the possible parameters.
3. Refer to the chapter 6 about profiles.xml file to get additional information on the possible parameters.
4. Refer to the chapter 10 about SNMP LAN to get additional information on the possible parameters.
15.11.2 FROM THE MIMIC EDITOR
Each object defined in EcoSUI HMI has an Action property. To use this feature from the mimic editor,
“SETSNMP” action is executed via button on the signal mnemonic by sending value compatible with this
mnemonic.
Another example of Button_Action: SETSNMP Tufanbeyli / prtGeneral / prtGeneralTable / prtGeneralEntry /

prtGeneralPrinterName; PrinterName1
16 MIMIC OBJECT EDITOR
CAUTION
• Avoid online modifications after the Site acceptance tests.

• Online modifications should be performed by an experienced user.
• Carefully evaluate the impact of online modifications before implementation.
16.1 EDIT OBJECTS

Editing an object is possible when EcoSUI HMI is in “Edit Mode” - CTRL + SHIFT + ALT + F12. Then, right-click
anywhere in the HMI view and select Unlock Mimic.
Double click the desired object in the Mimic to open a contextual menu that provides access to the general
properties.
A double-click on the object opens its specific properties

A right-click opens the edit menu then select “New object…” to add an object.
16.2 FORBID MIMIC EDITION

It is possible to restrict the mimic edition to the configuration administrator only. This parameterization is done via
the CAE tool.
When logged as an administrator of EcoSUI, press CTRL + SHIFT + ALT + F12 to turn the EcoSUI Edit mode on.
A popup window prompts the user to enter his password (the same as the one used to log to the system):
16.3 COMMON PROPERTIES

EcoSUI HMI Graphical configuration is based on graphical objects assembly: the objects have many common
properties.
Here is a list with a description:
PROPERTY DESCRIPTION
_X X coordinate
_Y Y coordinate
_ZOrder Z coordinate (0 = deepest)
_Width Object width
_Height Object height
_ ChildOf Name of the father including inheritance features
_Action Action to be executed when clicking on object
_Interlock Action is allowed depending on a boolean condition; this can be done by EVALUATE function
or SPS mnemonic
_ViewProfiles Reserved for future evolutions
_ActionProfiles Reserved for future evolutions
_Tooltip Tooltip text when dragging over object
_HideCond Visibility of object depending on Boolean condition; this can be done by EVALUATE function
or SPS mnemonic
16.4 TOOLTIP
The "_Tooltip" property is provided for all the “simple” graphical objects. When mouse cursor hovers on the object,
the message appears overprint during a few seconds.
This property contains the description associated with the object which be displayed with the tooltip. The user is in
charge of providing the description linked with the tooltip.
Here is the list of graphical objects on which the tooltip is available:
- Static text
- Dynamic text
- Analog value
- Static picture
- Dynamic picture
- Rectangle
- Horizontal line
- Vertical line
- Diagonal down
- Diagonal up
- Circle
- Triangle
- Button
- Glass button
- Progress bar
- Bit field
- Curve
- Text box
16.4.1 TOOLTIP ENABLE / DISABLE

There is no different property for enabling/disabling the tooltip. However, if the user provides the description for the
tooltip, the tooltip appears as enabled and if no description is given, tooltip is treated as disabled.
By default, the tooltip Description field is empty, and tooltip is in disabled state.
16.4.2 TOOLTIP DESCRIPTION PROPERTY

Tooltip Description Property is provided along with other properties of the graphical object in the property editor
window (the user is allowed to write the description associated with the tooltip).
Case 1:
"_Tooltip" property Description of the tooltip (example "Go to Transformer View")

If in the property editor, description for this property will be provided as above, then tooltip will appear as:
Example for a graphical object of type "Button"
The description of the tooltip can contain the special characters "\n", to go to next line:
Case 2: Default case
"_Tooltip" property
If in the property editor, no description is provided, then tooltip is considered as “disabled” and object will appear
without any tooltip as:

16.5 RECTANGLE
Rectangle object is the common object used to create lines vertical, horizontal, diagonal, polylines.
The type of rectangle is defined in the Rectangle_ShapeType property:
• 0 for a rectangle,
• 1 for diagonal down,
• 2 for diagonal up,
• 3 for a horizontal line,
• 4 for a vertical line,
• 5 for a circle,
• 7 for a polyline
A line is considered as a ‘thin’ rectangle.
A Static Rectangle object is typically defined by its position (x and y coordinates), his height, his length and his
color.
A Dynamic Rectangle object is typically defined by its position (x and y coordinates), height and length in the
global properties window, but additional properties can also be set:
• Rectangle Mnemonic: link to the IEC 61850 data that will control its color
• Rectangle_OnColor : color of the foreground when the value is “ON”
• Rectangle_OffColor : color of the foreground when the value is “OFF”
• Rectangle_UnknownColor : color of the foreground when the value is “UNKNOWN”
• Rectangle_OnBackColor : color of the background when the value is “ON”
• Rectangle_OffBackColor : color of the background when the value is “OFF”
• Rectangle_UnknownBackColor : color of the background when the value is “UNKNOWN”
In the case of an MPS, the 16 colors corresponding to the value are set in the Rectangle_OnColor property,
separated by “;”.
16.5.1 CREATE A POLYLINE

In EcoSUI, the Polyline object lets the operator build a shape made of straight segments.
To create a polyline in a MIMIC view:
• Set the object property Rectangle_ShapeType to 7 (7 for polyline).
• Enter the position of first point (x and y coordinates),

• In the Rectangle_PointList property, enter the list of points for the polyline. This property will contain the
drawing controls given to a “virtual” pen. This pen can be moved, made to draws shapes …
NOTE: To move pen to one point to another without drawing, use # before the point coordinates as explained in the
screenshot below; this create an invisible line:
16.5.2 DOTTED / DASHED LINE RECTANGLE

The operator can design a dotted / dashed line rectangle in a MIMIC view.
To create this effect and stylize the dashed outline as you want it to appear:
• Open the Rectangle object property Window
• Set the main border color in the MimicBorderColor property
• In the Rectangle_Style property, specify the sequence of dash/space/dot/space separated by “;”
Some examples:
• Rectangle style = 10;5;2;5
This setting will create a dashed/dotted line where:

• the first dash is 10 pixels,
• then a space of 5 pixels,
• then a dot of 2 pixels,
• then a space of 5 pixels.
This sequence repeats itself to the end of the line.
Other example:
• Rectangle style = 2;2
A setting that will result in a dotted line where the dashes are 2 pixels in size and the spaces are 2 pixels.
16.5.3 ANIMATE THE RECTANGLE BORDERS

It is also possible to animate the color of the rectangle border depending on conditions evaluations.
This is very convenient for busbars and lines colorizations.
The EVALUATE function can be called in Rectangle_Cond0(1,2,3). The syntax used in EVALUATE function is the
Formula syntax (see Formula manual for more details or refer to EcoSUI Configuration Application Note).
Another way is to animate the color of the rectangle border depending on popup window existence.
In the Rectangle_Cond0 property❶, specify the condition to set the color of the border:
• IsPopupOpenedOnBay ([substation name] / [< voltage level name] / [< bay name])
In the Rectangle_Cond0BorderColor property❷, specify the color of the border when the condition is true.
In the Rectangle_BorderColor property❸, specify the default color of the border when no conditions are true.
Rectangle_Cond0 -> IsPopupOpenedOnBay(^mastersubstation^ / ^mastervoltagelevel^ / ^masterbay^)
16.6 STATIC PICTURE

A Static Image has got quite the same definition as a rectangle, except that its color is
replaced by a link to the image file. Image file types can be JPEG, GIF, PNG or .BMP.
16.7 STATIC TEXT

A Static Text is defined by its position (x and y coordinates), its police, its color, its caption.
16.8 PROGRESS BAR

The Progress Bar refers to a measurement value. It is linked to a MV object and generally displays in detailed view.
Its properties must include the min, max values (for 0% to 100%), the min color, the middle color and the max
color.
16.9 DYNAMIC RECTANGLE
16.9.1 ON SPS OR DPS

A Dynamic Rectangle object is typically defined by its position (x and y coordinates), height and length in the global
properties window, but additional properties can also be set:
• Rectangle Mnemonic: link to the IEC 61850 data that will control its color
• Rectangle_OnColor : color of the foreground when the value is “ON”
• Rectangle_OffColor : color of the foreground when the value is “OFF”
• Rectangle_UnknownColor : color of the foreground when the value is “UNKNOWN”
• Rectangle_OnBackColor : color of the background when the value is “ON”
• Rectangle_OffBackColor : color of the background when the value is “OFF”
• Rectangle_UnknownBackColor : color of the background when the value is “UNKNOWN”
16.9.2 ON MPS
In the case of an MPS, the 16 colors corresponding to the value are set in the Rectangle_OnColor property,
separated by “;”.
• Rectangle Mnemonic: It uses an integer (value 0,1,2,3…). This value can also be calculated with a Formula as
shown on the screenshot below where EVALUATE(3) is a example to have 3 as the mnemonic value:
For Mnemonic=0: Rectangle_OffColor and Rectangle_OffBackColor apply
For Mnemonic=1: the 1st value of Rectangle_OnColor and Rectangle_OnBackColor apply

For Mnemonic=2: the 2nd value of Rectangle_OnColor and Rectangle_OnBackColor apply
For Mnemonic=1: the 3rd value of Rectangle_OnColor and Rectangle_OnBackColor apply

And so on ….
16.10 DYNAMIC PICTURE
16.10.1 SHOW MEMO

It is possible to display a Memo on a Mimic.
First declare the memo to be displayed in the object properties window:

• In the DynamicPictureMnemonic property, specify the memo to be displayed
o MEMO[MemoName] 1 if the memo is saved
o MEMO[MemoName] 0 if not saved
Then, in the DynamicPicture_Action property, specify the action to be used to display the memo:
• SHOW_MEMO[memoPath] to open a popup to edit memo

• SHOW_MEMO[memoPath]#[modifyProfile] to open a popup to edit memo. This action requires a user with
modifyProfile to edit/delete the memo.
Different pictures can be displayed depending on the MEMO value (saved or not):

Dynamic picture objects behave like Dynamic Rectangles. The difference is that, instead of having a list of colors
corresponding to the value states, it refers to a list of pictures. A datapoint controls the appearance of the dynamic
picture. e.g. a breaker position is shown with several pictures when it is closed, open, in jammed position…
• DynamicPicture_Mnemonic: link to the IEC 61850 datapoint that will control its appearance
• DynamicPicture_OnFilename: Picture to display when the value is “ON”
• DynamicPicture_OffFilename: Picture to display when the value is “OFF”
• DynamicPicture_UnknownFilename: Picture to display when the value is “UNKNOWN”
• DynamicPicture_JammedFilename: Picture to display when the value is “JAMMED” (DPS only)
• DynamicPicture_UndefinedFilename: Picture to display when the value is “UNDIFINED” (DPS only)
It is possible to use a second mnemonic for objects such as withdrawable breakers:

In such a case, DynamicPicture_Mnemonic selects DynamicPicture line (On,Off,Unknown …), and

DynamicPicture_Mnemonic2 selects the DynamicPicture column (image1, image2, …).
16.10.3 ON MPS
In the case of an MPS, 16 pictures corresponding to different values are set in the following properties:
• State0 in DynamicPicture_OffFilename property

• State1 to State15 in DynamicPicture_OnFilename property, separated by “;”.
16.10.4 GLOBAL PARAMETER DYNAMICPICTURE
DynamicPictureAllFilenames
DynamicPicture_AllFilenames is a global parameter to declare the dynamic picture conditions (open, close,
unknown...) on a same row.
Conditions Character Syntax
Open 0 0=Picture Filename for Open state
Close 1 1=Picture Filename for Close state
Unknown ? ?=Picture Filename for Unknown state
This global parameter replaces all separate parameters such as:

• DynamicPicture_OnFilename,
• DynamicPicture_OffFilename,
• DynamicPicture_UnknownFilename,
DynamicPicture_Mnemonic
DynamicPicture_Mnemonic and DynamicPicture_Mnemonic2 can be associated to SPS, DPS or MPS.

Combining DynamicPicture_Mnemonic and DynamicPicture_Mnemonic2 states in
DynamicPictureAllFilenames, results in a new state x.y computed , with:
• x= DynamicPicture_Mnemonic state
• y= DynamicPicture_Mnemonic2 state
For unknown mnemonic value, character “?” is used.
According to the resulting state to be animated, in DynamicPictureAllFilenames assign the resulting state to the
appropriate picture by applying the required syntax, separated by a “;”
If the resulting state is not associated with a picture, DynamicPicture_UnknownFilename will apply.
Example:
Explanation:
• If SPS is open and DPS is closed then_image.LEGEND_SYSTEM.101.png is displayed
• If SPS is set and DPS is closed then_image.LEGEND_SYSTEM.102.png is displayed
• If SPS is set and DPS is unknown then _image.LEGEND_SYSTEM.103.png is displayed
16.10.5 SHOW POPUP WINDOW
The instruction “SHOWPOPUP” allows the opening of a “popup” window via a click on a picture.
From a bay display, a click on the breaker opens the control detailed view. In addition, the use of
“IsPopupOpenedOnBay” instruction allows the colorization of the bay display rectangle while the popup remains
active (see §16.5.3 Animate the Rectangle Borders).
In the DynamicPicture_Action property, specify the action to be used to display the popup window:
• SHOWPOPUP 0 [PopupPictureName] [Sender DataPointPath]
SHOWPOPUP 0 OPENPOPUPCONTROL_ACTSON_DPC_SBO_Once.Cfg "SS_01 / 110_kv / FEEDER 1 / Q0 / SWITCHGEAR CONTROL DPC"

16.11 DYNAMIC TEXT

Dynamic Text object behaves like Static text, except that the caption is not unique, but varies according to a
Mnemonic value. The corresponding properties are:
• Text_Mnemonic: link to the IEC 61850 data that will control the object
• Text_TextOn: caption to display when the value is “ON”
• Text_TextOnColor: color of the caption to display when the value is “ON”
• Text_TextOnBackColor: color of the caption background to display when the value is “ON”
• Text_TextOff: caption to display when the value is “OFF”
• Text_TextOffColor: color of the caption to display when the value is “OFF”
• Text_TextOffBackColor: color of the caption background to display when the value is “OFF”
• Text_TextUnknown: caption to display when the value is “UNKNOWN”
• Text_TextUnknownColor: color of the caption to display when the value is “UNKNOWN”
• Text_TextUnknownBackColor: color of the caption background to display when the value is “UNKNOWN”
16.11.2 ON MPS
In the case of an MPS, the 16 captures corresponding to the value are set in the Text_TextOn property, separated
by “;”.
16.11.3 SHOW SIGNAL ATTRIBUTES

Signal attributes are configured in the SignalList.ini file (for further information, refer to the SignalList
document). Depending on your project’s requirements, you may want to display some specific attributes in EcoSUI
mimic views.
To do so, use the ATTRIBUTEMESSAGE function in Mnemonic parameter of any DynamicText Object:
ATTRIBUTEMESSAGE(Mnemonic;Attribute Index):
Where
• ‘Mnemonic’ represents the signal path (SS / VL / BAY / MODULE / SIGNAL)
• ‘Attribute Index’ represents a number
These attributes are also visible in:

• Event and State Viewer by using the parameter : EventViewer_ShowAttributeColumn=1
• Alarm Viewer by using the parameter: AlarmControl_ShowAttributeColumn=1
16.12 ANALOG VALUES

Analog Values are displayed on a dedicated object. Main properties are:
• Analog_Mnemonic: link to the IEC 61850 to display
• Analog_BackColor: background color
• Analog_ForeColor: foreground color
• Analog_UnknownForeColor: unknown foreground color
• Analog_Format: number format (ex:0.0)
• Analog_Coefficient: value scaling
• Analog_Unit: text to be displayed as ‘unit’
16.13 BUTTON
Button object can be displayed – or not – according user rights. Two kinds of buttons can be instantiated:
• Standard button, which is a rectangle and a text.
• Glass button that shows a flash object, and a text.
• Ordered button, which allows to specify an order at display.
On the button properties, the “Button Action” specifies the action to execute when pressed:
Action type Act on

CMD_SELECT
CMD_EXECUTE
CMD_CANCEL
SBO_EXECUTE
SBO_CANCEL
Controls
BYPASS_INTERLOCK, BYPASS_SYNCHROCHECK (see NOTE)
SUBSTITUTE, UNSUBSTITUTE
SUPPRESS, UNSUPPRESS
MULTIPLE_COMMANDS
SETSNMP
SHOW
SHOW_POPUP
SHOW_DISTURBANCES
SHOW_INBROWSER
Views
SHOW_REPORTS
SHOW_TOOLS
SHOW_VCR
HIDE_MIMIC
EXEC
PASSWORD
LOGIN
LOGOUT
END
HMI generals
RESET_COUNTER
SNAPSHOT
SWITCH_MUTE
SNOOZE
NOTE: Via protocol IEC 61850-1-8 Editions 1, 2 standard, BYPASS attribute order is defined as following:
BYPASS ATTRIBUTE Replaced by CHECK ATTRIBUTE via IEC 61850 Edition 2

BYPASS_INTERLOCK NO CHECK_INTERLOCK
BYPASS_SYNCHROCHECK NO CHECK_SYNCHROCHECK
16.13.1 BUTTONORDERED
The ordered button defines order of display from bottom to top.
Button_Zorder parameter
• Button_ZOrder: integer parameter from 0 to 16384. The button with the highest Button_ZOrder value appears
on top.
16.14 FLASH OBJECT

The Flash Object is similar to a Static Image object. The difference is that the file type is necessary swf.
An example of Flash Object is the “Glass Button”.
16.15 WEB BROWSER

The Web Browser object is similar to a Static Image object. It shows information about the selected device in an
.HTML or .PDF file. This object is parameterized during configuration.
16.16 LOAD SHEDDING GRID

It is possible to add a Load-shedding Grid object in EcoSUI Mimics in order to see and modify load shedding
parameters in the form of a grid.
In object edit mode, right-click the mouse and select Add DataGrid.
The DataGrid properties window appears on screen:
In the Datagrid_ConfigurationFilename parameter, select the datagrid configuration ini file.

This file should have been defined previously to setup the general parameters of the datagrid. For further
information, please refer to the EcoSUI Configuration Application Note.
16.17 COMBO BOX AS A SHORTCUT FOR PREDEFINED ACTION

The purpose of the option is to use a combo box in order to search in a pre-defined list with a quick index the
dedicated action to do without the use of the global HMI. This combo box does not replace "classic navigation", but
used as another way of looking for an action.
16.17.1 COMBO BOX CONFIGURATION

This combo box is added in the area chosen by the user (I.E. the main banner) like a standard combo box in the
mimic editor.
The search combo box is defined by:

• its associated configuration file which contains the list of items and actions to achieve.
• The properties ComboBox_ConfigurationFilename and ComboBox_TextboxEditable
Configuration file:
Actions can be any HMI action (CMD_SELECT, CMD_EXECUTE, SETPOINT, SHOW, SHOW_POPUP, EXEC,
…). List item action is set in the second column of combo box configuration file. Second column never appear in
drop-down list.
Each row represents a list item, each row has several columns, ‘;’ character is the column separator.
Action for each list item is shown in red rectangle. Actions are always located in 2nd column and hidden in combo
box.
Properties:
Some properties of the ComboBox object specify the behavior of the combo box:
• ComboBox_ConfigurationFilename: list items are defined in an .ini file. This property gives the path to this
file. A default file mycomboboxconfigurationfile.ini is automatically generated in the EcoSUI folder
\MCIS\Mimics “”.
• ComboBox_TextboxEditable: If set to 1, the item list will be filtered by characters found in the combo box. If
several columns are defined, filter is working on all columns (except action column that is not shown).
• ComboBox_ColumnsWidth: defines the width of each columns in the combo box.
The above configuration file will configure a combo box with 3 columns (see below)
16.17.2 COMBO BOX BEHAVIOR

When ComboBox_TextboxEditable is set to 1, the items of the combo box list are filtered as hereunder.
No character in combo box -> The full list is shown.
Character ‘u’ in combo box -> Only list items with character ‘u’ will be shown.
String ‘us’ in combo box -> Only list items with string ‘us’ will be shown.
If there are several words, the filtering shows the lines which contain one of the words.
NOTE: Case and key-words are not taken into account.

16.18 WIND SPEED

The Wind Speed object allows displaying animated information of the speed of the wind. The speed value is
provided by measurement and linked to a MV Object.
The Wind Speed is represented by a 180° analog display with pointer and displays information:
• The analog value of the actual measurement (with unit)
• The graphic value of the actual measurement (pointer position)
• The range of speeds
• The range of thresholds
• The colors for text, pointer, threshold ranges and the background
NOTE The range is defined from 0% to 100% with resolution 1%.

Properties are set:
Parameter Description
_WSMinRange Define the range of speed: Minimal and Maximum measurement values
_WSMaxRange
_WSGradientMinValue Define the range of 3 thresholds : Minimal, Medium and Maximum 20%, 80%, 100% (by
_WSGradientMidValue thresholds (in percentage of the range of speed) default)
_WSGradientMaxValue
_WSShowText Enable / disable text showing True (by default)
_TextFont The font of text
_WSTextUnit Define the unit of speed m/s (by default)
_WSTextForeColor Define color for text, background and pointer
_BackColor
_WSPointerColor
_WSGradientMinColor Define colors for range of thresholds. Green, Orange, Red (by
_WSGradientMidColor default)
_WSGradientMaxColor
16.19 WIND DIRECTION

The Wind Direction object allows displaying animated information of the direction of the wind. The direction value
is provided by measurement and linked to a MV Object.
The Wind Direction is represented by a 360° analog display with a pointer and displays information:
• The analog value of the actual measurement (angle in degree)
• The graphic value of the actual measurement (pointer position)
• The background image
• The color for text, pointer and the background
NOTE: The angle is displayed in degree (°) unit. The range is defined from 0° to
360° with resolution 1°.
Properties are set:
Parameter Description
_WMinRange Define the range of direction: Minimal and Maximum 0° and 360° (by default)
measurement values
_WMaxRange
_WShowText Enable / disable text showing True (by default)
_PointerColor Define color for pointer, text and background (without
background image file).
_WTextForeColor
_BackColor
_WImageFilename Define background image file None (by default)
16.20 TANK FEEDER

The Tank Feeder object allows displaying animated information of filling level of tank. The level value is provided
by measurement and linked to a MV Object.
The Tank feeder is represented by a vertical progress bar 0-100% within oval container and displays these
information:
• The analog filling level of the actual measurement (with unit)
• The graphic filling level of the actual measurement
(progress bar level)
• The background image
• The color for progress bar levels and the text
Properties are set:
Parameter Description Value

_TMinRange Define the range of the tank: Minimal and Maximum of filling level
_TMaxRange values.
_TShowText Enable / disable text showing True (by default)
_TTextForeColor Define color for text and background (without background image
_BackColor file).
_TImageFilename Define background image file None (by default)
_MinIndicationValue Define value for progress bar: Minimal, Medium and Maximum 20%, 80%, 100% (by default)
_MidIndicationValue values (in percentage of the range of the tank)
_MaxIndicationValue
_MinIndicationColor Define color for progress bar: Minimal, Medium and Maximum Green, Blue, Red (by default)
_MidIndicationColor ranges.
_MaxIndicationColor
_TTextUnit Define the unit of filling level Blank (by default)
_ProgressBarStartPos Define the start position and the end position of the progress bar 10% and 100% (by default)
_ProgressBarEndPos component (in percentage of the range of the tank)
17 ECOSUI MANAGER
17.1 PURPOSE OF ECOSUI MANAGER
EcoSUI manager is an application monitoring suite running at the same time with EcoSUI software suite i.e.
EcoSUI SBUS server, EcoSUI Supervisor, EcoSUI HMI, EcoSUI Gateway V5 Interface, EcoSUI security server and
MySQL server.
It displays and logs health status of EcoSUI software suite. It also detects when an application has stopped
unexpectedly or is frozen and so restart it.
17.2 HOW TO START ECOSUI MANAGER
Before starting EcoSUI manager, user checks that EcoSUI is installed in the PC. Launch EcoSUI manager and in
notification tray EcoSUI manager icon will be available as below image.
User performs right click action on the EcoSUI manager icon, user will see three options as shown in below image.
17.2.1 LOGIN
Clicking the Login allows the Operator/Engineer to log in to the system through an identification popup.
The login is verified by the Cybersecurity brick embedded in the EcoSUI.
The EcoSUI Manager behavior will then depend on the operator rights defined in the CAE tool. Default usernames
and passwords are available after the ECOSUI installation. These ones can be used even if CAE tool has not been
installed yet.
For more information on operator rights or on the default users and passwords, refer to the Cybersecurity, section
Privileges and Default Password of this manual.
The Login window is the following:
17.2.2 CONFIGURE ECOSUI MANAGER

User has to log on to change the configuration for EcoSUI Manager. Only user with configuration rights is able to
use EcoSUI Manager functionality.
Configuration for EcoSUI Manager
• User can select automatic Start of EcoSUI manager on Windows Startup
• User can set Time in seconds to try to restart crashed application
• User can set Maximum retry counter before EcoSUI Manager stop trying to restart application
17.2.3 CLOSE ECOSUI MANAGER

User has to log on to close the application.
• Click on “Close EcoSUI Manager”
• One question message will pop-up “Are you sure to shutdown EcoSUI Manager?”
• User can exit the application by clicking “Yes”
17.3 HOW TO USE ECOSUI MANAGER

When user performs mouse left click option on the EcoSUI Manager Icon then a small window appears on the
screen as shown below:
17.3.1 USER PROFILE VIEW

View Presentation
Observer view: Case of user is not logged on. The user can only
visualize the state of EcoSUI components.
Engineer and Operator view: Case of user is logged on with

Engineer or Operator profile. The user can make changes for
EcoSUI components.
• The user can enable/disable monitoring of the application
• The user can change the state (Start/Stop) of the application
• The user can restart application manually
• The user can automatically start/remove application from
Window startup
17.3.2 ECOSUI MANAGER CONTROL SYMBOLS

The following symbols help the user to understand the current status of the EcoSUI components:
Control Description
Enabled monitoring for the application
Disabled monitoring for the application
User can manually start the application. (Application is in stop state)
User can manually stop the application (Application is in start state)
User can manually restart application
Selected for automatic start from Windows startup
Selected for automatic stop from Windows startup

User enables monitoring

with a drag button on all
the EcoSUI applications
as shown here:
EcoSUI manager will restart the application(s) automatically in X minute/s after

an unexpected stop of the application:
17.3.3 ECOSUI COMPONENT MONITORING

EcoSUI components have three different states i.e. Running, Stopped and Not Responding. Based upon these
three states EcoSUI Manager has four use cases as defined in the below table.
Scenarios Tooltip message Color EcoSUI component

Indication
Case 1 EcoSUI HMI is Running • EcoSUI SBUS Server
If application is in running state, it will be
displayed as Running • EcoSUI Supervisor
EcoSUI • EcoSUI HMI
HMI • EcoSUI Gateway V5 Interface
• EcoSUI Security Server
• MySQL Server
Case 2 EcoSUI HMI is Stopped • EcoSUI SBUS Server
If application is not running or stopped, it
• EcoSUI Supervisor
will be displayed as Stopped
EcoSUI • EcoSUI HMI
• MySQL Server
Case 3 EcoSUI HMI is Not Responding • EcoSUI SBUS Server
If application is Not responding state, it will
EcoSUI • EcoSUI Supervisor
be displayed as Not Responding
HMI • EcoSUI HMI
• EcoSUI Gateway V5 Interface
Case 4 EcoSUI HMI is Not Responding, • EcoSUI SBUS Server
After retries if application is still Not
• EcoSUI Supervisor
responding than it will be signaled as User User Action Needed
action needed EcoSUI • EcoSUI HMI
• MySQL Server
NOTE:
1. EcoSUI manager restarts the EcoSUI components when they are stopped or in not responding stage.
2. When counter is reached then EcoSUI manager will stop trying to restart the application and counter will be
reset. EcoSUI manager notifies that a user action is needed.
3. User has to manually restart application(s) after a counter reaches its limit.
17.3.4 LOG STATUS OF ECOSUI COMPONENTS

EcoSUI manager monitors log
information with date and time
when any EcoSUI application
has changed status. It is a text
file log and available inside
C:\MCIS\EcoSUI Manager Log.
17.3.5 EXTRACTION REPORTING

The user can extract datapoints evolution from the SBUS Server. The extraction result (report .CSV file) is located
in C:\MCIS\Reports folder
There are two possible operation modes to extract:
• Manual reporting extraction
• Automatic reporting extraction
For manual reporting extraction:

• Open SBUS Server > Extraction tab
• Select signals on the Tree view situated on the left side of the window
• On central window, double-click to choose signal datapoints; the selected signals are dynamically displayed on
the below window: Selected Signals
• Choose the calendar area in order to extract data between two dates (From and To)
• Extract button to start extraction; A new file will be generated in C:\MCiS\Reports folder with the name as
Extraction_AAAAMDD_HHMMSS.csv:
• Clean button allows to delete all selected signals from Selected Signal window (reset the selected signals list)
• Load button allows to select a new ListOfSignalsToExtract from Reports folder with a new content
For automatic reporting extraction within a time period
Go to autoextract.ini file in C:\MCIS\Reports folder, and configure the automatic reporting extraction feature.
Learn how in the EcoSUI Configuration Application Note.
18 MCIS REPORTER
It allows the user to generate the report files.
The user executes the generation of the reporting files through the application MCIS Reporter.
Click Generate. It generates a report file.

An internal popup message displays on screen for the user to manually enter the date, the generated report always
takes the date of the day before. Refer the image below.
Advanced Menu Options
Click Ctrl + Alt + Shift + F12 to open and close the window advanced menu options.
It allows the user to operate the software and to configure the frequency of the report files with the other reports.
18.1 MEASUREMENTS VALUE REPORTS

The new parameter considered is “24HOURSHALF”, the MCIS reporter generates measurements value reports for
every 30 mins.
The reports are generated once per day, the report dated with the day before.
The data retrieves the intervals of 30 mins for the measurements in the place of 1 hour, for the reports.
The frequency of the reports does not change, what changes is the measurements request for 30 mins in the place
of 1 hours
It is still compatible with the old parameter “24HOURS”.
Basically, a reporter functions with two files:
➢ Platforme_O&G_CSV. rtp
➢ Platforme_O&G_CSV_Body .txt
Click on “Open Body” in the advanced menu option:

A Body.txt file opens as shown in below image, this file is created automatically with few modifications to enter
manually, like entering the new parameter “24HOURSHALF”.
In this Body.txt file, the user replaces the parameter “24HOURS” by “24HOURSHALF”, it generates a report where
the data is displayed with a sampling of 30 mins.
18.2 MEASUREMENT VALUE NEW PARAMETER “24HOURSHALF”
Functions / Parameters Description
{TABLESETTYPE (24HOUR)} Measurement value for every 1 hour
{TABLESETTYPE (24HOURHALF)} Measurement values for every 30 mins

18.3 OTHER EXISTING PARAMETERS FOR ECOSUI REPORTER
18.3.1 BITMAPS
{PICTURE (path of bitmap file)} Print a picture
{PICTURE_EX (path of bitmap file, x coordinates)} Print a picture
18.3.2 DATES
{PRINTCURRENTDATEFULL} Print the current date (i.e., Monday 24 April 2009)
{PRINTCURRENTDATETIME} Print the current date & time (i.e., 24/04/2009 15:23:12)
{PRINTCURRENTDATE} Print the current date (i.e., 24/04/2009)
{PRINTYESTERDAYDATE} Print the date of yesterday (i.e., 23/04/2009)
{PRINTLASTMONTHDATE} Print the last month (i.e., March 2009)
18.3.3 FORMATTING
{ENDLINE} Send a carriage return to the printer
{ENDPAGE} End page

18.3.4 STATIC TEXT
{FONT(fontname, fontsize, font Change font properties

properties)}
➢ fontname ➢ Windows Font (i.e., Courier New, Tahoma, Terminal, ...)
➢ fontsize ➢ Font Size (i.e., 8,10,12,14, ...)
➢ font properties ➢ B for Bold, U for Underline, I for Italic (items can be mixed)
{PRINT (string)} Print 'string' to the printer
18.3.5 EVENTS
{PRINTEVENTSHEADER1(Text)} Text to print as header of events (done after each new page)
{PRINTEVENTSHEADER2(Text)} Text to print as header of events (done after each new page)
{PRINTEVENTSFONT(fontname, fontsize, Change font properties used to print events

font properties)}
➢ fontname ➢ Windows Font (i.e., Courier New, Tahoma, Terminal, ...)
➢ fontsize ➢ Font Size (i.e., 8,10,12,14, ...)
➢ font properties ➢ B for Bold, U for Underline, I for Italic (items can be mixed)
{PRINTEVENTS (date, nb Max of Events, Print Events

filter)}
➢ Date ➢ YESTERDAY, TODAY, LAST_MONTH, THIS_MONTH

➢ nb Max of Events ➢ Limit the number of events. 0 for unlimited.
➢ filter ➢ Nothing -> No filter (Note: Use SQL statement to filter
d.desc_description, m.mess_message or o.object_origin)
18.3.6 INDIVIDUAL VALUES
{GETLASTVALUE (date, path to the value,

name of the value, tag)
➢ Date ➢ NOW (now), YESTERDAY (today at 00:00),

BEGIN_OF_THIS_MONTH (First day of this month at
00:00), BEGIN_OF_LAST_MONTH (First day of last month
at 00:00)
➢ Path to the value ➢ Pacis Path to the value

➢ Name of the value ➢ Pacis Name of the value
➢ Tag ➢ Internal name that represents the value (chosen by you
and reused in PrintValue, Add & Sub functions)
Example:
{GETLASTVALUE (YESTERDAY, LAFIABOUGOU / 30kV / Depart DARSALAM1 / M231, Energie active
Export, P1)}
Performs Addition and Subtraction:

{ADD (TagA, TagB, TagC)} Internal value TagA = TagB + TagC
{SUB (TagA, TagB, TagC)} Internal value TagA = TagB - TagC
{PRINTVALUE (tag, format)} Print a value retrieved by {GetLastValue()} in the specified
format
Tag Tag of the value used in {GetLastValue()}
Format Use Visual Basic format to format string. Put "x|" before the
format to adjust the size to x characters by adding spaces.
Example:
{PRINTVALUE(P1,000000)} (ie. Prints "000105") {PRINTVALUE(P1,6|0)} (ie. Prints " 105")
18.3.7 CURVES
{CURVESSETTYPE (type)} To set the period of the next curve
➢ Type ➢ LASTMONTH, LASTTWOWEEKS, LASTTWOYEARS,

LASTTWOWEEKS, LASTDAY
{CURVESADDSIGNAL Add a signal to the curve (Right now, only one signal for each curve)
(Path; Legend; Format; Unit; Min;
Max)}
{PRINTCURVES} Print the curve
Properties of action "CURVES"
➢ {FONT(Tahoma,10,)}
➢ {ENDLINE}
➢ {PICTURE (.\ArevaLog.Bmp)}
➢ {PICTURE_EX(.\ArevaLog.Bmp,14500)}
➢ {FONT(Tahoma,14,B)}
➢ {PRINT( Template Report)}
➢ {ENDLINE}
➢ {PRINT( Date : )}
➢ {PRINTCURRENTDATE}
➢ {ENDLINE}
➢ {PRINT( Page : )}
➢ {PRINTPAGENUMBER}
➢ {ENDLINE}
➢ {ENDLINE}
COMMUNICATION (CT)
COMMUNICATION EcoSUI/EN CT/I
CONTENT

1.1 Overview ................................................................................................................................. 2
COMMUNICATION EcoSUI/EN CT/I

This document is a chapter of the EcoSUI documentation. It describes the various standard communications
protocols implemented in EcoSUI.
1.1 OVERVIEW
EcoSUI supports different types of communications:
Communication Type Communication with

Legacy Communication IEC 61850 Devices over Ethernet IEC 61850-8-1 Edition 1 and Edition 2 protocols
Legacy IEDs over Ethernet MODBUS TCP/IP, EFIP, OPC protocols
Synchronization Devices over Ethernet SNMP V1/V2 protocol
Communication
Web Services on TCP/IP
SNTP
Whatever the type of protocol selected for your project deployment, EcoSUI requires the parameterization of
specific files, which are detailed in the EcoSUI Configuration Application Note.
IEC 61850-8-1 Editions 1 and 2 are supported by EcoSUI.
The certified documents applicable for EcoSUI Client are listed below:
Documents References
Model Implementation Conformance Statement (MICS) for the

EcoSUI_2.1.16272.50 - MICS - A1
IEC 61850 edition 2 interface document
Protocol Implementation Conformance Statement (PICS) for the
EcoSUI_2.1.16272.50 - PICS - A1
IEC 61850-8-1 edition 2 interface document
Protocol Implementation eXtra Information for Testing (PIXIT) of
EcoSUI_2.1.16272.50 - PIXIT - A1
the IEC 61850 document
Tissue Implementation Conformance Statement (TICS) for the
EcoSUI_2.1.16272.50 - TICS - A1
IEC 61850 interface document
Table 1: Certified IEC 61850 documents applicable to EcoSUI
The ACSI conformance statements are used to provide an overview and details about Gateway with version EPAS
V6:
• ACSI basic conformance statement
• ACSI models conformance statement
• ACSI service conformance statement
The statements define the communication features mapped to IEC 61850-8-1 Edition 2.
Please refer to above EcoSUI PICS document.

SETTINGS (ST)
SETTINGS EcoSUI/EN ST/I
CONTENT
2. EcoSUI Suite ............................................................................................ 3

2.1 EcoSUI File Structure ............................................................................................................. 4
2.2 EcoSUI Sample Files .............................................................................................................. 5
2.3 EcoSUI .ini Files...................................................................................................................... 6
3. Configure EcoSUI ..................................................................................... 7

3.1 Declare EcoSUI Computers ................................................................................................... 7
3.2 Specify the IP Address of Central DB servers ...................................................................... 8
3.3 Specify the IP Address of Additional Central DB ................................................................. 9
3.4 Declare local EcoSUI software modules ............................................................................... 9
4. Configure HMI Views .............................................................................. 10

4.1 Setup the MIMIC Files........................................................................................................... 10
4.2 Define Workspaces .............................................................................................................. 11
4.3 Configure Layers .................................................................................................................. 12
4.4 Import HMI View Files........................................................................................................... 13
4.5 Edit Graphic Objects from EcoSUI ...................................................................................... 13
5. Datapoint Configuration Database .......................................................... 14

5.1 Clear former Databases ....................................................................................................... 14
5.2 Import a Datapoint Configuration From an SCE Database ................................................ 15
5.3 Load Configuration From Signal List File ........................................................................... 16
6. Generate a ConfPackage ....................................................................... 17

7. Deploy EcoSUI Configuration ................................................................. 17
8. Customize EcoSUI Tools ........................................................................ 17
8.1 Tool.ini Default Values ......................................................................................................... 17

This document is a chapter of EcoSUI documentation. It describes how to configure and deploy an EcoSUI
Configuration from scratch.
This document provides a procedure oriented for new projects.
Prerequisites: Before using this procedure, the EcoSUI shall be installed as described in the Installation chapter
of this guide.
2. ECOSUI SUITE
EcoSUI is an HMI solution. The EcoSUI is a software suite that works with modules which interact with each other
as shows below:
Fig1. EcoSUI Modules
User Interface module. This is the operator interface that shows devices states. Up to
EcoSUI HMI
n EcoSUI HMI can be connected to the SBUS Server.
Acquisition module. This is the client on the IEC 61850 and legacy networks and
SBUS Server
serves data to EcoSUI modules.
Central DB MySQL Database that stores the signal list, alarms and events.
EcoSUI deployment software (to download databases, switch databases, generate

EcoSUI Supervisor
Confpackage).
NOTE:
• IEC 61850 LAN configuration has to be done with EPAS SCE or EPAS-E.
• Non-IEC 61850 LAN configurations have to be done using other tools.
2.1 ECOSUI FILE STRUCTURE

Once EcoSUI is installed, you will get the following file structure:
Storage folder for Supervisor
Gateway OPC folder
Configuration and view folder for HMI
SBUS Server data
By default, configuration files of the file structure contain sample values.

Configuration can be imported from EPAS SCE or EPAS-E configuration package via the EcoSUI Supervisor. The
above folders will contain .ini files related to your project.
Refer to the EcoSUI Configuration Application Note for more details on how to import an existing database.
The next chapters explain how to create an EcoSUI configuration package from scratch or from an example.
2.2 ECOSUI SAMPLE FILES

By default, an Examples folder is created when installing EcoSUI. It contains samples of configuration files
required for learning EcoSUI:
• Gateways_Examples.zip: Default signal list for SCADA and sample of Protocols.

• Mimics_SainteAnne.zip: Sample of HMI views and workspace from a user project.
• Rings_Example.zip: The Ring.ini file contains important SbusServer LAN properties.
• Standard Images.zip: Default EcoSUI icons and images.
• Standard Languages.zip Default Language icons that appear in EcoSUI.
• Standard Mimics.zip: Contains Mimics files.
• Standard Popups.zip: Default popup configuration and template files.
2.3 ECOSUI .INI FILES

.ini files are used to store specific configuration data. .ini files are divided into sections. Each section begins with a
section name, which can be followed by several Entries. An entry associates a keyname with a value.
The general format is:
[section]
keyname=value
Because .ini files use plain text, they can be edited using any text editor or word processor. We recommend using
Notepad++ which allows the syntax coloration of file sections.
3. CONFIGURE ECOSUI
3.1 DECLARE ECOSUI COMPUTERS

Modify the Package.ini file to declare the IP addresses of operating and engineering workstations and servers.
Any equipment on the LAN has to be declared the same way: one section per EcoSUI equipment.
• Go to C:\MCIS and open the Package.ini file.

• For each PC, create a dedicated [PC_NAME] section:
o Replace PC_NAME with the username (network name e.g. [IWS_81005])
o Specify the Types = HMI, GTW or SBUSServer
o Enter the IP Address
3.2 SPECIFY THE IP ADDRESS OF CENTRAL DB SERVERS

EcoSUI allows redundant configuration with two EcoSUI SBUS servers and two EcoSUI database servers.
The configuration of SBUS servers is done in the Servers.ini file where the user specify the IP address of the
main and backup servers.
• Go to C:\MCIS
• Open the file SERVERS.INI file at the root of the folder
• In the [CAEDatabases] section, enter for

- IP0: the IP address or host name of the main computer managing the first Config/Alarms/Events (CAE)
Database
- IP1: the IP address or host name of the backup computer managing the second Config/Alarms/Events
(CAE) Database shall be left empty if there is only one CAE Database.
3.3 SPECIFY THE IP ADDRESS OF ADDITIONAL CENTRAL DB

A Global EcoSUI client allows the connection to several Additional Central Databases.
The configuration of an Additional Central Database is set in Servers.ini file. Mainly, the operator has to specify
the IP address of the main and backup central databases.
The Addition Central Database(s) parameters are added on section [Additional CAEDatabases] section with the
keyname CAEDB_.
For further configuration details, please refer to the EcoSUI Configuration Application Note.
NOTE: The Global EcoSUI Client mode, disabled by default, is automatically enabled if one or more Additional
Central database(s) are added.
In this example, two Additional Central Databases have been configured:
Name Properties
CAEDB_0 First additional central database (redundant) EcoSUI Substation
CAEDB_1 Second additional central database (no redundant) XAT Substation
3.4 DECLARE LOCAL ECOSUI SOFTWARE MODULES

Modify the MCISEqpt.ini file in order to specify the device characteristics:
• Go to C:\MCIS
• Open MCISEqpt.ini file, duplicate the [Dummy_EQPT] section. and provide the information for each of the
equipment:
• Then provide the information for each of the equipments:

- HasLogbookPrinter=1 If the equipment uses a log book printer
- HasSBUSServer=1 if it makes data acquisition
- HasHMI=1 if it is a EcoSUI computer
- HasGateway=1 if it is an OPC gateway
- HasCentralDB=1 if it is an archive computer
4. CONFIGURE HMI VIEWS

To configure HMI Views, follow the steps described in this chapter:
1. Setup the MIMIC Files
2. Define Workspaces
3. Configure Layers
4. Import HMI View Files
5. Edit Graphic Objects from EcoSUI
4.1 SETUP THE MIMIC FILES

To add Mimic files to the EcoSUI project:
• Go to C:\MCIS\examples
• Extract the sample Mimics.Zip file and rename the folder created by the Mimics.zip file as Mimics
• Paste your folder to C:\MCIS\Mimics (replace the existing Mimics folder)
EcoSUI uses configuration files (.cfg) that contain parameters. It also contains template files (.tpl) that can be
edited to modify parameters like the position of a button.
4.2 DEFINE WORKSPACES

The graphical area is split into different workspaces.
EcoSUI uses a Workspaces.ini file to define workspaces used in the HMI.
This file defines how the Mimics and the System Views will be displayed on the operator screen:
To setup these workspaces according to your project

• Go to C:\MCIS\Mimics
• Open the Workspaces.ini file
• Add a workspace and change workspace dimensions or add a background image if needed
4.3 CONFIGURE LAYERS

To configure layers
• Open Workspaces.ini in folder C:\MCiS\Mimics
• If not available, add a new section named WorkspacesLayer with a key named EnableWorkspaceLayers set
to 1 as shown below:
Layers System is now activated

• Restart EcoSUI HMI
• Once EcoSUI HMI restarted, reopen workspaces.ini file
• Go to WorkspacesLayer section. A list of configured Workspaces is available as shown below:
• Set your own layers levels. By default, all values are set to 0:
Modifications are done directly, therefore it is not required to restart EcoSUI HMI to apply changes.
Value of each entry represent the Layer Level of associated Workspaces.
Below a schema of Layers and Workspaces
To learn more about layers philosophy, go to Layers Philosophy section of the HMI chapter of this guide.
NOTE: Be very attentive during the layers configuration, if the highest opened layer doesn’t have a HIDEMIMIC
action inside, there is no way to close it. In such a case, the only way to close it is by restarting the HMI.
Movable Workspace need to be set to highest level Workspaces Layer configuration.

Application example:
When Order popup is opened (configured with a layer level above others), all buttons which are configured into a
workspace with a layer below the popup layer level are inactive.
4.4 IMPORT HMI VIEW FILES

HMI graphical view can be done:
• Directly in EcoSUI
• Exported from the SCE (.mpc file) by using the Schneider-Electric Migration Tool
• Created from Schneider-Electric HMI Configuration tool.
For further information on these tools, please contact Schneider-Electric Support.
NOTE: Refer to the EcoSUI Configuration Application Note to learn how to export the graphical part from EPAS
SCE to EcoSUI.
4.5 EDIT GRAPHIC OBJECTS FROM ECOSUI

Once imported to EcoSUI, Mimics can be edited.
Refer to the HMI chapter of this guide to learn about the Mimics edition functions.
5. DATAPOINT CONFIGURATION DATABASE
5.1 CLEAR FORMER DATABASES

First of all, clear any database that might have been used by EcoSUI:
• In the Start menu, click Schneider Electric > EcoSUI > EcoSUI SBUS Server.
• Click the Data Acquisition tab.
• Stop data acquisition by clicking on Stop.
• Click the Other tab.
• Click the Tools… button and select Database Clean-up.
• From the list, select Clear All Rings And Objects. This process deletes any database template.
• Answer the confirmation messages that show up.

• Once the database is cleared, click the Dashboard tab and close EcoSUI SBUS server.
5.2 IMPORT A DATAPOINT CONFIGURATION FROM AN SCE DATABASE

In the following procedure, we assume that the electric database has been set up through SCE.
CAUTION
Ensure that the graphical representation associated with the different states of datapoints
is clearly discriminable on the graphical user interface.
Before importing a SCE database to SBUS Server, check that the SCL.zip is in the generated zip file.
• Copy the .zip file generated by the SCE in C:\MCIS\SCEConfiguration
• Get the configuration zip file. It is composed of several folders and several ini files. Unzip it in C:\MCIS.
• Connect to the EcoSUI SBUS Server.

• Click the Data Acquisition tab.
• Stop data acquisition by clicking on Stop.
• Click the Tools… button and select Load Configuration from SCE Zip.
• In the explorer window, browse and select the configuration file to be imported:
Click Open. This will download the SCE configuration into the EcoSUI database.
• Once the new configuration is loaded, click the Dashboard tab and exit the SBUS Server.
• Restart all EcoSUI software.
This ends the SCE configuration importation. The SBUS Server is configured along with SCE Alarm, State & Event
Viewer tabs.
5.3 LOAD CONFIGURATION FROM SIGNAL LIST FILE

Depending on your project’s need, you may want to load configuration from the Signal List File (IEC 61850,
SNMP…). This way is used when data come from EPAS-E. In this case, the bellow procedure is to be followed:
• From Data Acquisition tab, click the Tools button.

• Select Tools > Load Configuration from SignalList
Exit and restart SBUSServer.

6. GENERATE A CONFPACKAGE
When starting a project from scratch, you need to generate a configuration package to be used in EcoSUI. This
package will use the “.Ini” files you have just modified to configure your application, HMI views, rings, gateways…
The generation of the configuration package is done from the EcoSUI Supervisor.
For further information, please refer to the EcoSUI Configuration Application.
7. DEPLOY ECOSUI CONFIGURATION

EcoSUI Supervisor allows the deployment of an EcoSUI configuration package over all HMIs on the network
NOTE: EcoSUI configuration can also be deployed manually by importing - into the SBus Server - the configuration
.Zip file generated by the SCE or EPAS-E. This procedure is detailed in the EcoSUI Configuration Application
Note
8. CUSTOMIZE ECOSUI TOOLS

To edit internal data, EcoSUI uses several softwares. The parameters for the Tools are located in the Tools.ini
file. This file is initialized at installation and is located in the C:\MCIS\Mimics.
Use the Notepad++ software to edit this file.
8.1 TOOL.INI DEFAULT VALUES

By default, two tools are configured for the Tools mimic: Notepad, Explorer as shown below:
[Tool1]
Name=Explorateur
Executable=Explorer.exe
[Tool2]
Name=Bloc Note
Executable=Notepad.exe
Add the sections you need for the tools you want to install.
CYBERSECURITY (CS)
\
CYBERSECURITY EcoSUI/EN CS/I
EcoSUI Documentation Page 1
CONTENT
1. Scope of the document ............................................................................. 2
2. Documentation reference.......................................................................... 2
3. Cybersecurity Policy ................................................................................. 2

3.1 Applicability ............................................................................................................................ 3
3.2 User Account Management ................................................................................................... 4
3.2.1 Security Policy ............................................................................................................................................ 4
3.3 Password Change .................................................................................................................. 5
3.3.1 Default RBAC.............................................................................................................................................. 6
3.3.2 Default Password ........................................................................................................................................ 6
3.4 Security Logs Management ................................................................................................... 7
3.5 Backup to Factory .................................................................................................................. 8
3.6 Antivirus .................................................................................................................................. 8
3.7 Hardening................................................................................................................................ 8
3.8 Authentication Certificate ...................................................................................................... 9

This document describes the measures taken and tools to decrease the risk of attacks and to help to ensure
Confidentiality, Integrity, Availability / Authentication and Non-Repudiation.
2. DOCUMENTATION REFERENCE
Document Title
EPAS CS-SCS_EN EPAS System Cyber Security (SCS) User Guide
EPAS HARDENING_EN_AN EPAS HARDENING Application Note
CAE_EN_UG_2.2.0 Cybersecurity Admin Expert (CAE) User Guide

Table 1: Reference Documents
3. CYBERSECURITY POLICY
The minimum cybersecurity policy for EcoSUI includes:
• Disclaimer
• Password used with different profiles (or roles)
• Device hardening (unused ports)
• Security logs
• Antivirus
• Updates and Patches
• Backup and Restore
Cybersecurity good practices applied to communication protocols

MODBUS, IEC 61850-8-1, SNMP, OPC-DA, NTP and some IT protocols are unsecure.
The EcoSUI software in a system that supports these protocols does not have the capability to transmit
encrypted data using these protocols. If a malicious user gained access to the system network, transmitted
information could be disclosed or subject to tampering.
Security measures need then to be applied on the EcoSUI software to help prevent security breaches and
vulnerabilities when using these protocols. Refer to the EPAS HARDENING Application Note and follow the
recommendations.
3.1 APPLICABILITY
The EcoSUI cybersecurity requirements apply to:
Requirement Description
Profiles (password) Profiles are managed by CAE Tool
Profile lockout / Log off Yes
Unused ports Yes
Security Logs Yes
Table 2: Cybersecurity Requirements for EcoSUI
NOTE:
The configuration about the dpwscore.xml file which is used by the CS Brick to make the discovery of all the devices
and more precisely by the CS Brick as the server to expose its API to the client CAE Manager which will then browse
for all the devices on the network and checks for the DPWS settings.
If the same port is shared on the same computer for the two devices EcoSUI and Gateway, the CAE will discover
only one of the devices. Another port has to be setup manually by the user, for the DPWS on the EcoSUI side or on
the Gateway side.
3.2 USER ACCOUNT MANAGEMENT
3.2.1 SECURITY POLICY

The Security policy is the collection of all the security parameters that apply to the system.
Security policy parameters are setup by Security Administrator operator using the CAE tool.
Parameters Default Unit Min Max Possible

Value Value Value Value Value
Inactivity automatic disconnection timeout 15 Minute 1 99 Number
Maximum numbers of errors for password 5 - 1 99 Number
Password attempts timer
(Time before the attempt counter can be 3 Minute 1 30 Number
reset)
Allow user locking Yes - - - Yes / No
Automatic User Account unlocking Yes - - - Yes / No
Locking period duration 240 Second 1 86400 Number
IEEE None / IEEE 1686-2013/
Password Complexity - - -
1686-2013 NERC CIP-007-5
BDEW / E3 / NERC CIP-007-5 /
Security standards to apply to log and
BDEW - - - IEEE 1686-2013 /
monitoring
IEC 62351-8:2017 / CS_PH1
Syslog server IP address N/A - - - IP Address
SNMP Client IP Address N/A - - - IP Address
Inactivity automatic disconnection timeout 15 Minute 1 99 Number
Table 3: CAE Security Policy Parameters default definition
NOTE: Schneider Electric strongly recommends installing the device in a locked cubicle to reduce the
cybersecurity risk.
NOTE: Please refer to the documentation “CAE User Guide” for password and user account further details.
3.3 PASSWORD CHANGE

A password is required to place a control or set a parameter (whether from the front panel or via a PC-based
application). For this purpose, at some point, the user chooses a profile that depends on the intended activity.
Important
The Schneider Electric password policy is one of the key elements of the Cybersecurity Policy.
Here after are listed good practices to improve the Password definition:
• Use common Cybersecurity Good Practice for password complexity definition by using strong passwords.
• Change all passwords from their default value when taking the device into use and specially after the first login.
• Change Passwords regularly.
• Update password after a certain period of time.
• Use NERC Compliant password as much as possible.
• Enforce the use of strong and complexes Password containing: Caps characters + Lowercases characters +
Numbers + Special characters.
• Set the minimum password length to 10 characters.
• Disable all Communication ports unused on the device, if possible.
• Do not reuse old passwords.
• All devices installed before January 2020 should be checked separately case by case to confirm the
Cybersecurity conformity to Standard/country law.
Operator has to be aware of best practice concerning passwords; these include:
• Do not share any personal password.
• Do not display any password during password entry.
• Do not transmit any password in email or by other means.
• Do not save any password on PC’s or other devices.
• Do not write any password on any media.
• Do regular user reminding about best practices concerning password.
_________________________________________________________________________________
Access without a proper password is denied as soon as the security administrator has defined the passwords.
NOTE: Please refer to CAE User Guide for password configuration.

3.3.1 DEFAULT RBAC

NOTE: Please refer to EPAS System Cyber Security (SCS) User Guide, chapter FT and section RBAC Definition
with CAE for overview, and to CAE User Guide for password further details.
The table below contains the EcoSUI RBAC default definition:
EcoSUI RBAC default definition Permissions following Role

Functions VIEWER OPERATOR ENGINEER
Control order X
View navigation X X X
Close application X
Alarm acknowledgement X
Alarm Clearing X
View modification X X X
Memo Suppress X
Memo modification X
Memo creation X
Memo read X X X
Trend modification X
Print and export file X
External Software Execution X
Table 4: EcoSUI RBAC default definition
3.3.2 DEFAULT PASSWORD

The table below contains the default password value:
Role Default User Value Default Password

VIEWER DefaultViewer AAAAAAAA
OPERATOR DefaultOperator AAAAAAAA
ENGINEER DefaultEngineer AAAAAAAA
SECADM SecurityAdmin AAAAAAAA
Table 5: CAE Password default definition
The default users and passwords come with the installation of EcoSUI and can be used even if CAE tool has not yet
been installed.
NOTE: Viewer is an implicit user; every user can navigate inside views.
3.4 SECURITY LOGS MANAGEMENT

Security logs produced by application are archived to SysLog device. A Security Logs viewer allows displaying
security logs. The viewer allows sorting logs based on several criteria (ID, Security Level and UTC time).
Figure 1: Visualize Logs sample
NOTE: For the list of Security Logs produced by EcoSUI, please refer to documentation EPAS Hardening
Guide, chapter EcoSUI Hardening, section Windows Log Management.
3.5 BACKUP TO FACTORY

The “Factory mode” is the default configuration (RBAC and security policy) of any IED coming out of the factory.
A manual operation (reset order) allows to retrieve the factory mode configuration for EPAS component. This order
is available according to role and permissions.
EPAS component Method Back to Factory Mode
EcoSUI Operator resets by replacing with default configuration file
This below procedure allows to retrieve the EcoSUI RBAC factory mode configuration:
Step Action
Backup current RBAC configuration:
1 • Access to the RBAC folder
“C:\MCIS\Bin\Resources\factory_db\rbac”
• Select the three files “permissions.exi”, “roles.exi” and “users.exi” and copy them to the
destination folder
“C:\MCIS\Bin\Resources\sec_db\rbac\a”
NOTE: Please refer to EPAS System Cyber Security (SCS) User Guide, section Back to factory Mode for
details.
3.6 ANTIVIRUS
The Windows-based PCs are vulnerable to viruses.
The PCs hosting NON time-critical application EcoSUI can be permanently scanned.
NOTE: For PC guard with antivirus solution, please refer to the documentation EPAS System Cyber Security
(SCS) User Guide, section Hardening PC based solution.
3.7 HARDENING
NOTE: Please refer to EPAS HARDENING Application Note (sections Port reservation for EPAS
Application and Firewall Windows Parameters for EcoSUI) to learn hardening procedures
recommendations for EPAS System, and EPAS System Cyber Security (SCS) User Guide, section Device
Hardening.
3.8 AUTHENTICATION CERTIFICATE

The certificate allows to authenticate the origin and the period of validity of an executable (setup).
Before running the setup program, the user can manually perform a security authentication.
When starting setup, Windows checks the presence of the embedded certificate in the executable setup file.
The operator is informed by Windows:

• If the certificate is missing, a notification window will be displayed
• If the certificate is detected, a confirmation window appears with the associated information
To check if an executable file is electronically signed:

• Select the installation executable file (setup)
• Click Right button on the executable file and select Properties from the menu
• Click on Digital Signature tab
• Select the name of the signatory = Schneider Electric
• Click on Details button to view the digital signature information
• Click on Display Certificate button to view the certificate information
• Click on General tab
• Authenticate the executable by checking the fields associated with the vendor's signature and its period of
validity.
COMMISSIONING
&
RECORD SHEET (RS)
COMMISSIONING & RECORD SHEET EcoSUI/EN RS/I
CONTENT
1 Scope of the Document..................................................................................... 2
2 Commissioning Record Sheets........................................................................ 2

2.1 EcoSUI SBUS SERVER PC .................................................................................................... 2
2.1.1 PC Characteristics ...................................................................................................................................... 2
2.1.2 Installation ................................................................................................................................................... 2
2.1.2.1 Software Delivery ........................................................................................................................................2
2.1.2.2 General Installation .....................................................................................................................................3
2.1.2.3 Installation Check .......................................................................................................................................3
2.2 EcoSUI HMI PC ....................................................................................................................... 4
2.2.1 PC Characteristics ...................................................................................................................................... 4
2.2.2 Installation ................................................................................................................................................... 4
2.2.2.1 Software Delivery ........................................................................................................................................4
2.2.2.2 General Installation .....................................................................................................................................4
2.2.2.3 Installation Check .......................................................................................................................................4

This document is a chapter of EcoSUI documentation. It is a complement to the Commissioning chapter.
2 COMMISSIONING RECORD SHEETS

2.1 ECOSUI SBUS SERVER PC
2.1.1 PC CHARACTERISTICS
PC Name
PC IP Address
PC Supplier
PC micro-processor
Clock Frequency (GHz)
RAM Size (Kb)
Windows Version
Windows Language
Service Pack
2.1.2 INSTALLATION
2.1.2.1 Software Delivery
EcoSUI System Version
EcoSUI SYSTEM Release Note Checked:

 Yes
 No
EcoSUI HMI Version

MySQL Version
EcoSUI HMI Release Note Checked:

 Yes
 No
SBUS Agency Version
SBUS Agency (IEC 61850) Release Note Checked:

 Yes
 No
2.1.2.2 General Installation

MySQL installed using OI IN Manual:
 Yes
 No
EcoSUI HMI Installed using EcoSUI_ENIN Manual:

 Yes
 No
MySQL first installation on this PC:

 Yes
 No
EcoSUI HMI first installation on this PC:

 Yes
 No
MySQL application installed:

 Yes
 No
EcoSUI HMI Installation directory:

 Standard C:\MCIS\Mimics
 Other (precise): _____________________________
EcoSUI HMI Installed as:

 Server
 Client
 Both
2.1.2.3 Installation Check

Do a check that the files or directories that follow are in the correct path (compare with the EcoSUI_ENIN Manual):
 EcoSUI HMI version directory
 MySQL Server
EcoSUI HMI Server redundancy:

 Yes
 No
EcoSUI HMI launched:

 Yes
 No
EcoSUI HMI database started:

 Yes
 No
2.2 ECOSUI HMI PC
2.2.1 PC CHARACTERISTICS
PC Name
PC IP Address
PC Supplier
PC micro-processor
Clock Frequency (GHz)
RAM Size (Kb)
Windows Version
Service Pack
2.2.2 INSTALLATION
2.2.2.1 Software Delivery
EcoSUI System Version
EcoSUI System Release Note Checked:

 Yes
 No
EcoSUI HMI Version
EcoSUI HMI Release Note Checked:

 Yes
 No
2.2.2.2 General Installation

EcoSUI HMI Installed using EcoSUI_ENIN Manual:
 Yes
 No
EcoSUI HMI first installation on this PC:

 Yes
 No
EcoSUI HMI Installation directory:

 Standard C:\MCIS\Mimics
 Other (precise): _____________________________
2.2.2.3 Installation Check

Do a check that the files or directories that follow are in the correct path (compare with the EcoSUI_ENIN Manual):
 EcoSUI HMI version directory
EcoSUI HMI launched:

 Yes
 No
MAINTENANCE (MF)
MAINTENANCE EcoSUI/EN MF/I
Content
1 Scope Of Document ................................................................................. 2
2 Central DB Overview ................................................................................ 3

2.1 Software .................................................................................................................................. 3
2.2 Redundancy ............................................................................................................................ 3
2.3 Global EcoSUI Client .............................................................................................................. 3
3 Data exchange ......................................................................................... 4

3.1 Configuration .......................................................................................................................... 5
3.2 Alarms ..................................................................................................................................... 6
3.3 Events ..................................................................................................................................... 7
3.4 Live Values.............................................................................................................................. 8
4 Central DB Tables .................................................................................... 9

4.1 Configuration Table.............................................................................................................. 10
4.1.1 Objects Table ............................................................................................................................................ 10
4.1.2 ObjectStates Table ................................................................................................................................... 10
4.2 Archiving Tables................................................................................................................... 11
4.2.1 Event Table ............................................................................................................................................... 11
4.2.2 Values_X Tables ....................................................................................................................................... 11
4.3 Alarm Tables ......................................................................................................................... 12
4.3.1 Alarms Table ............................................................................................................................................. 12
4.3.2 AlarmAck Table......................................................................................................................................... 12
4.4 Alarms and Events Comments Table .................................................................................. 13
4.5 EcoSUI Parameters and Status Tables ............................................................................... 13
4.5.1 Parameters Table ..................................................................................................................................... 13
4.5.2 Rings Table ............................................................................................................................................... 13
4.5.3 McisEqpt Table ......................................................................................................................................... 13
5 SQL Administration ................................................................................. 14

5.1 Connection............................................................................................................................ 14
5.1.1 Version Prior to 2013 ................................................................................................................................ 14
5.1.2 Version After 2014 .................................................................................................................................... 14
5.2 Perform SQL Queries ........................................................................................................... 15
5.3 Backup .................................................................................................................................. 16
5.3.1 Create a backup project ............................................................................................................................ 16
5.3.2 Backup options ......................................................................................................................................... 17
5.4 PERIODICITY OPTIONS........................................................................................................ 18
5.5 Catalogs ................................................................................................................................ 19
6 EcoSUI Database Maintenance .............................................................. 20

6.1 Export/Import Database ....................................................................................................... 21
6.1.1 Export Central DB ..................................................................................................................................... 21
6.1.2 Clean Central DB ...................................................................................................................................... 23
6.1.3 Import Central DB ..................................................................................................................................... 24
7 Debug folder ........................................................................................... 25

1 SCOPE OF DOCUMENT
This document is a chapter of the EcoSUI documentation. It provides an overview of EcoSUI Central DB and
details on how to do the maintenance.
2 CENTRAL DB OVERVIEW
The central DB is the EcoSUI database in which are stored the configuration (signal list), the alarm list and the
archives.
In case of redundancy, a solution can have 2 Central DBs:
• Central DB 0 is the Main Central DB
• Central DB 1 is the Backup Central DB
MySQL is the database engine of a Central DB.

SBus Server has to be started on Central DB even if there is no acquisition on this computer. SBus Server that is
installed on the same computer as Central DB includes specific redundancy and purges features.
2.1 SOFTWARE
EcoSUI Central DB is based on MySQL Server 5.5.
2.2 REDUNDANCY
On one project, we can have 2 Central DBs.
2.3 GLOBAL ECOSUI CLIENT

One Global EcoSUI Client can connect to several Remote Central databases, in order to collect data from several
substations and displays the global real-time dataflow status (events and alarms).
Limit Value
Maximum substations (Remote Additional Central databases) managed by one Global 32

EcoSUI Client
3 DATA EXCHANGE
The Central DB connects to:
• SBUS Server
o Sends the latest configuration (signal list)
o Receives and stores events and measurements
o Receives and stores alarms list updates
• EcoSUI
o Sends the latest configuration (signal list)
o Sends events, measurements and alarm list on EcoSUI demand

3.1 CONFIGURATION
At startup, each software (SBUS Server, HMI EcoSUI, Gateway) downloads the latest configuration from
CentralDB.
WARNING
EcoSUI applications must be restarted each time you:
• Load a database
• Switch a database
Failure to follow these instructions can result in death, serious injury, or equipment
damage.
3.2 ALARMS
• SBUS Server feeds CentralDBs with alarm updates.
• The HMIs (EcoSUI) get the list of alarms from the CentralDBs. Then, the HMIs acknowledge and clear alarms
3.3 EVENTS
• SBUS Server feeds CentralDBs with Events / MV archiving.
• HMIs (EcoSUI) get Events / MV from the CentralDBs.
3.4 LIVE VALUES

• The HMI and the GTW directly connect to SBUS Servers to retrieve real-time values:
4 CENTRAL DB TABLES
The purpose and a description of these tables is provided in the following chapters.
4.1 CONFIGURATION TABLE

Two tables contain the signal list, objects and objectstates:
• The Objects table lists the signals
• The Objectstates table lists the different states of each signal (i.e. Set / Reset labels of SPS signals).
In SCE, each signal has a unique ID called GUID like ‘3F2504E0-4F89-11D3-9A0C-0305E82C3301’, coded on 128
bits.
In ECOSUI, each signal has a unique ID, called uid32, coded on 32 bits (−2,147,483,648 to 2,147,483,647).
ECOSUI’ Uid32 is computed from GUID.
4.1.1 OBJECTS TABLE

The objects table contains the nformation for each signal:
Item Description
object_uid32 Its UID32
object_ring_uid32 The ring to which the signal belongs to
object_signaltype Its type (0=SPS, 1= DPS, 2=MV, 4=MPS, 6=CTRL…)
object_origin The path to find the signal
(CS2 / 415V / ESWG-4401A-MS / A1-04 EQSP M6)
object_description Its description (TRIP CIRCUIT FAULT)
object_min, object_max, object_unit, object_format Measurement properties
object_opcpath Its OPC Path defined in SCE (Site-1.Subst-1.VoltLevel-1.GenericBay-
8.GenericModule-26.ModuleSPS-3)
object_alarmconfiguration Which states (Unknown, Set, Reset, Jammed…) are alarmed for this signal?
object_iecreportaddr IEC 61850 report address for main SBus Server
object_iecreportaddr2 IEC 61850 report address for backup SBus Server
object_iecsignaladdr IEC 61850 signal address
object_iecuid32 Unique ID, coded on 32 bits that represents the IEC 61850 signal address
object_ieceqptname Name of the IED
…
4.1.2 OBJECTSTATES TABLE

In the objectstates table, each state (represented by a number) of a signal (defined by its uid32) has a label. For
instance, for a SPS we can have the following:
• RESET (State 0)
• SET (State 1)
• SUPPRESSED (State 6)
• SELFCHECK FAULT (State 8)
• TOGGLING (State 9)
• UNKNOWN (State 11)
• SUBSTITUTED (State 13)
• FORCED (State 14)
4.2 ARCHIVING TABLES

Two tables store EcoSUI archives, events and values_x:
• The Event table (events)
• The Measurements table (values_x)
4.2.1 EVENT TABLE

The Event table shows the information for each event:
Item Description
Event_object_uid32 Unique ID that represents the signal
Event_datetime Date + Time (without millisecond) of this event. This is dated by the IED
Event_millisec Millisecond of this event. This is dated by the IED
Event_proc_datetime Date + Time (without millisecond) when SBus Server has processed this event
Event_proc_millisec Millisecond when SBus Server has processed this event
Event_state New state (number) of the signal
Event_orcat OrCat (see IEC 61850 specifications)
Event_orid OrId of this event (see IEC 61850 specifications)
Event_mess New label for this signal (same as we can find in objectstates)
…
4.2.2 VALUES_X TABLES

Measurement archiving is split over 100 tables called values_0 to values_99. This is done to limit the size of these
tables.
The 2 last digits of signal uid32 represent the table in which signal values will be stored, i.e. if a signal has its
uid32=12575265 then its measurements will be stored in Table value_65.
The Measurement table shows the information for each measurement:
Item Description
Value_object_uid32 Unique ID that represents the signal
Value_datetime Date + Time (without millisecond) of this measurement. This is dated by the IED
Value_millisec Millisecond of this measurement. This is dated by the IED
Value_quality Quality of the value
Value_value Value
Value_meantype Not used
…
MAINTENANCE EcoSUI/EN MF/H
4.3 ALARM TABLES

4.3.1 ALARMS TABLE
In the Alarms table, each signal appears only once.
• If it is not present, it means that it is not alarmed.
• If it is present, it can have several states (Active/Inactive, Acknowledged/Not Acknowledged).
Each alarm contains the following information:
Item Description
Alarm_uid32 Unique ID that represents the signal
Alarm_appearance_datetime Date + Time (without millisecond) of this alarm. This is dated by the IED
Alarm_appearance_millisec Millisecond of alarm appearance
Alarm_processed_datetime Date + Time (without millisecond) when SBus Server has processed this alarm
Alarm_processed_millisec Millisecond when SBus Server has processed this alarm
Alarm_active Is this alarm still active?
Alarm_acknowledged Is this alarm acknowledged?
Alarm_acknowledged_by Who has acknowledged this alarm?
Alarm_acknowledged_datetime Date + Time (without millisecond) when alarm was acknowledged
Alarm_cleared Is this alarm cleared?
Alarm_message Message of this alarm
Alarm_state State of this alarm
…
4.3.2 ALARMACK TABLE

The AlarmAck table is used to trace user acknowledgment.
Each AlarmAck contains the following information:
Item Description
Alarmack_uid32 Unique ID that represents the signal
Alarmack_appearance_datetime Date + Time (without millisecond) of this alarm. This is dated by the IED
Alarmack_appearance_millisec Millisecond of alarm appearance
Alarmack_acknowledged Is this alarm acknowledged?
Alarmack_acknowledged_by Who has acknowledged this alarm?
Alarmack_acknowledged_datetime Date + Time (without millisecond) when alarm was acknowledged
…
4.4 ALARMS AND EVENTS COMMENTS TABLE

Each Comment contains the following information:
Item Description
comment_uid32 the datapoint unique ID

comment_text the comment’s text, limited to 512 characters
comment_datetime the comment’s timetag
comment_user the comment’s author, as an EcoSUI username
4.5 ECOSUI PARAMETERS AND STATUS TABLES

4.5.1 PARAMETERS TABLE
This table stores several parameters like the current version of the database.
4.5.2 RINGS TABLE

This table stores statuses of EcoSUI rings.
Each Ring contains the following information:
Item Description
Ring_uid32 Unique ID that represents the Ring
Ring_type Type of the Ring (IEC 61850 - Efip - …)
Ring_ss0name Name of the main SBUS Server
Ring_ss0version Version of the SCD on the main SBUS Server
Ring_ss0State Status of the main SBUS Server
Ring_ss0lastupdate Date of the last update of the main SBUS Server
Ring_ss1name Name of the backup SBUS Server
Ring_ss1version Version of the SCD on the main SBUS Server
Ring_ss1State Status of the main SBUS Server
Ring_ss1lastupdate Date of the last update of the main SBUS Server
Ring_dbversion Version of the configuration (signal list) in this Central DB
…
4.5.3 MCISEQPT TABLE

This table stores statuses of EcoSUI equipments.
Each Equipment contains the following information:
Item Description
Mciseqpt_name Name of this equipment
Mciseqpt_type Type of this equipment (SBUS Server or ECOSUI)
Mciseqpt_eqptversion Software version
Mciseqpt_eqptversion2 Software version 2
Mciseqpt_lastupdate Date of the last update
…
5 SQL ADMINISTRATION
MySQL is the EcoSUI database engine. MySQL provides several useful statements that allow the user to
maintain EcoSUI database tables effectively. Those statements make it possible to analyze, optimize, check, and
repair database tables.
MySQL can be administrated through standard tools, depending on MySQL version installed:
5.1 CONNECTION
5.1.1 VERSION PRIOR TO 2013
You can manage MySQL from:
• MySQL Administrator and MySQL Query browser
o Username: root
o Password: no password for versions prior to 2013
o Default Schema: pacis
5.1.2 VERSION AFTER 2014

You can manage MySQL from:
• MySQL Administrator and MySQL Query browser
o Username: mcisadmin
o Password: s$e!P!C!L@2014
o Default Schema: pacis
5.2 PERFORM SQL QUERIES

Start MySQL Query Browser to perform queries on the database:
5.3 BACKUP
Creating backups of your MySQL database should be a regular and scheduled task.
This can be done via MySQL Administrator tool.
NOTE: A scheduled backup requires a stored connection. Use the connection manager accessible from MySQL
Administrator >Tools > Options menu to create one and use it then for the login.
5.3.1 CREATE A BACKUP PROJECT

To create a backup project:
• Start MySQL Administrator and click Backup (1)
• Click New Project (2) and enter a name for this backup project in the Project Name entry field (3).
• Select the EPAS database and click the right-pointing arrow (4). The backup content of the selected database
appears on screen.
44
2
5.3.2 BACKUP OPTIONS

Click the Advanced options tab to set up the database backup options:
• In the Backup Execution Method area, click for the desired backup type (5).
• Check the desired Output File options (6)
6
5.4 PERIODICITY OPTIONS

Click the Advanced options tab to set up the database backup periodicity and the destination file:
• To schedule the database backup, enable the Schedule this backup project option (7).
• Then, select the target folder, which can be an external disk for instance (8)
• In the Execution time area, check the desired weekday options and time (9)
• Click Execute Backup Now (10)
8
9
10
5.5 CATALOGS
The Catalogs function in MySQL Administrator allows you see at a glance the size of each table present in
EcoSUI database along with the number of rows.
• To do so, start MySQL Administrator and click Catalogs (1)
• Select the EPAS database (2). The Schema Tables appear on screen.
2
6 ECOSUI DATABASE MAINTENANCE

The EcoSUI database maintenance can be configured at software level in the Servers.ini file. This file can be
found at the root of C:\MCIS.
To set up the EcoSUI database parameters according to your requirements, go to the following sections of the
Servers.ini file:
• [CentralDB]
• [CAEDatabases]
• [AdditionalCAEDataBases]
Learn how in the EcoSUI Configuration Application Note, in The Servers.ini File section.
6.1 EXPORT/IMPORT DATABASE

6.1.1 EXPORT CENTRAL DB
To export a database, do the following:
Step Action
1 On main view of EcoSUI SBUS Server application.
Click on “Tools” to show the menu for export/import database:
2 Click on “Export Database” of menu Manual Import/Export sub-menu:
3 Select the CentralDB to export. Automatic is selected by default, it is the current DB.
Step Action
4 Select the destination folder.
5 Select Dates range to export.
6 Click on Export
7 A popup shows at end of Export:
NOTE: The first export can last several hours. Do another export from the time the first export started till now (this
shall be very fast).
NOTE: For this second export the user must choose the period for at least 24Hours (From – To) to assure the
export of the last events.
6.1.2 CLEAN CENTRAL DB

NOTE: Before cleaning the DB, make an archive of CentralDB 0 and CentralDB 1 with function Export.
The Database Clean-Up function works on both CentralDB 0 and CentralDB1.
To clean a database, do the following:
Step Action
Click on “Tools” to show the menu for Database Clean-Up.
2 Click on “Clear Events” of menu Database Clean-Up sub-menu:
3 Click “OK” on next confirmation popup.

4 At end, a popup to confirm events clean-up shows.
5 Click on “Clear Measurements” of menu Database Clean-Up sub-menu:
6 Click “OK” on next confirmation popup.

7 At end, a popup to confirm measurements clean-up shows.
6.1.3 IMPORT CENTRAL DB

To import a database, do the following:
Step Action
Click on Tools to show the menu for export/import database:
2 Click on Import Database of menu Manual Import/Export sub-menu:
3 Select the CentralDB destination, Automatic is selected by default, it is the current DB.
4 Select the folder containing a previous export.

5 Click on Import
6 A popup shows at end of Import:
7 DEBUG FOLDER
The user can find logs files in the Debug folder in C:\MCIS.
The following files are available:
• [MySQL]Errors.log: This is the error logs file of MySQL
• [SBUSServer].dbg: This is the logs file of the SBUSServer.
• [MCIS].dbg: This is the logs file of EcoSUI HMI.
• [Interop].dbg: This is the logs file of Interop module. This is a commun module of all EcoSUI applications
(SBUS Server, MCIS, …)
LEXICON (LX)
LEXICON EcoSUI/EN LX/I
EcoSUI Documentation 1/9
Abbreviation Signification
AC Alternating Current
Acquisition Data Acquisition module also called “SBUS Server”. It allows data acquisition from
IEDs connected through IEC 61850 or legacy protocols. As Client or Master it allows
the transmission of controls coming from SCADA.
A/D Analog/Digital
ADC Analogue to Digital Converter
AE qualifier Application Entity qualifier (Used internally by IEC 61850 to identify a server
Application)
AI Analogue Input (Measurement Value including state attribute)
Commonly Voltage or current DC signals delivered by transducers, and representing
an external value (refer to CT/VT for AC).
AIS Air Insulated Substation
Alarm This is an event describing a substation abnormal operating condition that needs an
intervention. Alarming is a process to attract operator attention by signaling this
event using specific message and/or an external horn.
AO Analogue Output
Value corresponding to a desired output current applied to a DAC.
AOU Computer MiCOM C264 Board name for Analogue Output
API Application Programming Interfaces
AR Auto-Reclose
ASCII American Standard Code for Information Interchange
ATCC Automatic Tap Change Control
Automation charged to regulate secondary voltage, more specific than AVR
AVR Automatic Voltage Regulator
Automatism used to regulate secondary voltage by automatic tap changer control
(see ATCC). Set of features can be added, see chapter MiCOM C264 FT
Bay Set of LV, MV or HV plants (switchgears and transformers) and devices (Protective,
Measurement…) usually around a Circuit Breaker and controlled by a bay computer.
BCP Bay Control Point
Name given to the device or part used to control a bay. It can be Mosaic Panel,
MiCOM C264 LCD… Usually associate with Remote/Local control.
BI Binary Input (or Information)
Name given into Computer MiCOM C264 of information already filtered, before it
becomes an SPS, DPS… with time tag and quality attributes
CB Circuit Breaker
Specific dipoles switch with capability to make line current and break fault current.
Some have isolation capability (nominal-ground at each side)
CC Complemented Contact
Central DB Stores the signal list, alarms & events database
SQL Database that stores archives, signals, live status, alarms & events. A project
can have 2 Central DBs for redundancy purposes.
Client Define in IEC 61850 as: entity that requests a service from a server and that
receives unsolicited messages from a server
CM CoMissioning
Configuration Package Zip file containing configuration of
• The database (Export Folder)
• SBUS Servers (Rings.zip)
• EcoSUI HMI (Mimics.zip)
• The project (Servers.ini, General.ini)
• The package itself (Package.ini)
CRC Cyclic Redundancy Check
Coding result send with packet of transmitted data to help to ensure their integrity.
Usually result of a division of transmitted data by polynomial.
CT Current Transformer
Basically the electric device connected to process and extracting a current
measurement. By extension part of a device (MiCOM C264) that receives AC values
and converts it to numerical measurement value.
CT/VT Current and Voltage transformers
(Conventional)
Datapoint Datapoints can be physical (hard-wired acquisition or controls) or virtual data
(acquired from communication protocols or internally derived (computation) shared
by electrical and system topologies. Datapoints are continuously updated with real-
time values, measures, or controls relevant to electrical or system process.
DB DataBase
Tool or set of data that define the configuration of a system or specific device like
computer. Opposed to setting or parameter DB has a structure that cannot be
modified online. DB are versioned.
DBID Databases Identity Brick
DC Direct Current
DPC Double Point Control
Located at device level (electric device or IED). Two digit and/or relays outputs used
for device control with complementary meaning (OPEN, CLOSE). It should have its
own Remote/Local switch.
DCF77 External master clock and protocol transmission
LF transmitter located at Mainflingen, Germany, about 25 km south-east of
Frankfurt/Main, broadcasting legal time on a 77.5 kHz standard frequency.
DCO Double Control Output
DCS Digital Control System
Generic name of system based on numeric communication and devices, to be
opposed to traditional electrically wired control.
DCT Double CounTer
Counter based on 2 DI with complementary states (counting switchgear maneuver
for example)
DE Direct Execute
Device Term used for one of the following unit:
Protective relays, metering units, IED, switchgear (switching device such as CB,
disconnector or Earthing switch), disturbance or quality recorders.
DI Digital Input
Binary information related to the presence or to the absence of an external signal,
delivered by a voltage source.
DIN Deutsche Institut für Normung
The German standardization body.
DIU DC Input Unit
Computer MiCOM C264 Board name for Digital Input
DLL Dynamic Link Library. Available on Windows.
A feature that allows executable code modules to be loaded on demand and linked
at run time. This enables the library-code fields to be updated automatically,
transparent to applications, and then unloaded when they are no longer needed.
DM Digital Measurement
Is a measurement value which acquisition is done by DI and a specific coding BCD,
Gray, 1 among N…
DO Digital Output
Used to apply a voltage to an external device via a relay, in order to execute single
or dual, transient or permanent controls.
DOF Degree Of Freedom
Used for a template attribute, that can be modified or not when used. An attribute
has a degree of freedom if a user can modify its values on its instances
DP Double Point
Information/control derived from 2 digital inputs/output; usually used for position
indication of switching devices (OPEN, CLOSE).
DPC Double Point Control
DPS Double Point Status
Position indication of switching devices (OPEN, CLOSE).
EcoSUI Human Machine Interface. It is a suite of software modules that can be installed on
different PC.
EcoSUI Central DB Stores the signal list, alarms & events database
EcoSUI Equipment EcoSUI software modules (HMI, Server, Gateway, Supervisor, Central DB) can be
installed on different PCs., they are called EcoSUI Equipments.
EcoSUI HMI EcoSUI Human Machine Interface
EcoSUI Supervisor EcoSUI software module used to import SCE / SET databases and to download
databases to EcoSUI equipments.
EFIP EFIway protocol
EMC Electro-Magnetic Compatibility
Event An event is a time tagged change of state/value acquired or transmitted by a digital
control system.
EPAS EcoStruxure Power Automation System (former PACiS)
EWS Engineering WorkStation
FAT Factory Acceptance Test
Validation procedures execution with the customer at factory.(i.e. SAT)
FBD Functional Block Diagram

One of the IEC 61131-3 programming languages (language used to define
configurable automation).
FIFO First In First Out
FO Fiber Optic
FP Front Panel
GHU Graphic Human interface Unit
GIS Gas Insulated Substation
GMT Greenwich Mean Time
Absolute time reference
GOOSE Generic Object Oriented Substation Event
GPS Global Positioning System
Based on triangulation from satellite signal, that transmit also absolute GMT time
used to synchronize a master clock
Group Logical combination of BI (i.e. SP, DP, SI or other groups).
GSSE Generic Substation Status Event
Hand Dressing Facility for an operator to set manually the position of a device (acquired by other
means) from the HMI at SCP level; e.g. from OPEN to CLOSE (without any impact
on the “physical” position of the electrical switching device).
HMGA Horizontal Measurement Graphical Area
HMI Human Machine Interface
Can be EcoSUI HMI.
HSR High Speed auto-Recloser, first cycles of AR
HTML Hyper Text Mark-up Language
Used as standard for formatting web display
HV High Voltage (for example 30kV to 150kV)
I/O Input/Output
ICD IED Capability Description (IEC 61850-6 standardized xml file)
IEC International Electro-technical Commission
IEC 61850 Standards for the design, configuration, communication and testing of electrical
substation
IED Intelligent Electronic Device
General expression for a whole range of microprocessor based products for data
collection and information processing.
In EcoSUI context, this is an equipment connected to an EcoSUI ring. EcoSUI
Server acquires data from IEDs. Such IEDs needs to be declared in “Electric Rings”
configuration files.
IP Internet Protocol
IRIG-B Inter-Range Instrumentation Group standard format B. This is an international
standard for time synchronization based on analogue signal.
JAMMED Invalid state of a Double Point:

Occurs when the 2 associated digital inputs are still in state 0 after an user
selectable delay, i.e. when the transient state “ motion ” is considered as ended
LAN Local Area Network
L-BUS Legacy Bus
Generic name of Legacy or field networks and protocols used to communicate
between MiCOM C264 (Legacy Gateway function) and IED on field bus.
LSB Least Significant Bit
LED Light Emitting Diode
Live Values Live Values are real-time values (Measurements & signal states) that are shown on
EcoSUI HMI views
LOC Local Operator Console
Dedicated to maintenance operation
Local DB Local SQL Database that stores a copy of the configuration (signal list, …)
L/R Local / Remote
Local/Remote control When set to local for a given control point it means that the controls can be issued
mode from this point, else in remote control they are issued from distant devices.
Logbook Printer Part of a SBUS Server that manages one printer
Manager
LV Low Voltage
MCB Mini Circuit Breaker. Its position is associated to tap changer.
MDIO Management Data Input/Output
A standard driven, dedicated-bus approach that is specified in IEEE 802.3
Measurement Values issued from digital inputs or analogue inputs (with value, state, time tag)
Metering Values computed depending on the values of digital or analogue inputs during
(non-tariff) variable periods of time (time integration).
Metering Values computed depending on the values of digital or analogue inputs during
(tariff) variable periods and dedicated to the energy tariff. These values are provided by
dedicated “tariff computer” which are external to the MiCOM Systems.
MIB Short for Management Information Base, a database of objects that can be
monitored by a network management system. SNMP uses standardized MIB formats
that allows any SNMP tools to monitor any device defined by a MIB.
MIDOS Schneider Electric Connector: Used for CT/VT acquisition
MIMICS HMI Views. They provide the operator with an animated representation of devices in
the form of static or dynamic (depending on the device current state).
MMC Medium Modular Computer
MMS Manufacturing Message Specification (ISO 9506)
ModBus Communication protocol used on secondary networks with IED or with SCADA RCP.
2 versions exist with standard MODICON or Schneider Electric one.
Module Word reserved in EPAS SCE for electric HV devices. It groups switch-gears,
transformer, motors, generators, capacitors, …
MOTION Transient state of a Double Point
Occurs when the two associated digital inputs are momentarily in state 0 (e.g.
position indication when an electrical device is switching). The concept of
“momentarily” depends on a user selectable delay.
MPC Protection Module for Computer
MPS Multi Point Status
MV Measurement Value
MV Substation Medium Voltage
MVAR Mega Volt Ampere Reactive
MySQL Open source database used by “Central DB“
NBB Numerical Busbar Protection
NC Normally Closed (for a relay)
NO Normally Open (for a relay)
OI Operator Interface
OID Short of Object Identifier, it’s an identifier used to name and point to an object in the
MIB hierarchy. SNMP-enabled network devices (e.g. printer, switches, etc.)
maintains database of system status, availability and performance information as
objects, identified by OIDs.
OLE Object Linking and Embedding
OLE is a Microsoft specification and defines standards for interfacing objects.
OLTC On Line Tap Changing
OMM Operating Mode Management
OPC OLE for process control
OPC is a registered trademark of Microsoft, and is designed to be a method to allow
business management access to plant floor data in a consistent manner.
Operation hours Sum of time periods, a primary device is running under carrying energy, e.g. circuit
breaker is in Close state and the current is unequal 0 A.
OS Operating System
OSI Open System Interconnection
Split and define communication in 7 layers : physical, link, network, transport,
session, presentation, application
OWS Operator WorkStation
PC Personal computer and associated Hardware and Operating system.
Popup A control window that suddenly appears when the operator selects an option with a
mouse or clicks a special function key. Usually, the pop-up window contains controls
and stays on the screen only until the operator selects one of the controls. It then
disappears.
Client / Server Protocol Communication protocol model in which a server program responds to requests from
a client program, and the peer-to-peer model, in which either of the two devices
involved can initiate a communication session.
Master / Slave Protocol Master/slave is a model for a communication protocol in which one device or
process (known as the master) controls one or more other devices or processes
(known as slaves). Once the master/slave relationship is established, the direction of
control is always from the master to the slave(s).
PSL Programmable Scheme Logic
Queue A queue is a particular kind of collection in which the entities in the collection are
kept in order and the principal (or only) operations on the collection are the addition
of entities to the rear terminal position and removal of entities from the front terminal
position. This makes the queue a First-In-First-Out (FIFO) data structure.
RCC Remote Control Centre
Is a computer or system that is not part of MiCOM system. RCC communicates with
and supervises MiCOM system using a protocol.
RCP Remote Control Point
Name given to the device or part used to control remotely several bay or sub-station.
Usually associate with Remote/Local sub-station control. It is a SCADA interface
managed by the MiCOM system through Telecontrol BUS. Several RCP’s can be
managed with different protocols.
Remote Control Mode When set for a control point it means that the controls are issued from an upper level
and are not allowed from this point.
Remote HMI Remote HMI is a client of the substation HMI server. The client may provide all or
part of functions handled by the substation HMI.
Ring Physical group of IEDs connected on the same physical network. The “Sbus Server”
can be connected to multiple rings.
RJ-45 Registered Jack-45
A 8-pin female connector for 10/100 Base-T Ethernet network
RMS Root Mean Square
RRC Rapid ReClosure
RSE Régime Spécial d’Exploitation
French grid function when works are being done on a HV feeder
RSVC Relocatabled Static Var Compensator
RTC Real Time Clock
SAT Site Acceptance Test
Validation procedures executed with the customer on the site.
SBO Select Before Operate
A control made in two steps, selection and execution. Selection phase give a
feedback. It can be used to prepare, reserve during time, configure circuit before
execution. Controls are done into a protocol, or physical (DO select with DI Select
then DO execute).
S-BUS Station Bus
Federal network between EcoSUI devices.
SBUS Access IEC 61850 Acquisition Module of SBUS Server
SBUS Axs Same as SBUS Access
SBUS Server Name of the Acquisition software module : see “Acquisition” definition
SCADA Supervisory Control And Data Acquisition
SCD Substation Configuration Description (IEC 61850-6 standardized xml file)
SCE System Configuration Editor
SCL Substation automation System Configuration Language (IEC 61850-6)
SCP Substation Control Point
Name given to the device or part used to control locally several bays or sub-station.
Usually associate with Remote/Local sub-station control. It is commonly EcoSUI
Operator Interface.
SCS Substation Control System
SCT Single Counter
SER Sequence of Event Recorder
Combines SOE with accurate Time synchronization and Maintenance facilities over
Ethernet communication
Server Define in IEC 61850 as: entity that provides services to clients or unsolicited issues
messages
Setpoints (analogue) Analogue setpoints are analogue outputs delivered as current loops. Analogue
setpoints are used to send instruction values to the process or auxiliary device
Setpoints (digital) Digital values sent on multiple parallel wired outputs Each wired output represent a
bit of the value. Digital setpoints are used to send instruction values to the electrical
process or to auxiliary devices.
SFC Sequential Function Chart
One of the IEC 61131-3 programming languages (language used to define
configurable automation).
SI System Indication
Binary information that do not come from external interface. It is related to an
internal state of the computer (time status, hardware faults…). It is the result of inner
functions (AR, …), PSL, or ISaGRAF automation.
SIG Status Input Group
SNMP Short for Simple Network Management Protocol, a set of protocols for managing
complex networks. SNMP works by sending messages, called protocol data units
(PDUs), to different parts of a network. SNMP-compliant devices, called agents,
store data about themselves in Management Information Bases (MIBs) and return
this data to the SNMP requesters.
SOE Sequence Of Events
Other term for the event list.
SP Single Point
SPS Single Point Status
SPC Single Point Control
Supervisor EcoSUI Tool that allows the rapid deployment of an EcoSUI configuration package
over all HMIs on the network (automated process).
Table Set of data elements (values) that is organized using a model of
vertical columns and horizontal rows
Thread A portion of a program that can run independently of and concurrently with other
portions of the program
TI Tele Interface
TM Analogue Measurement
TPI Tap Position Indication (for transformers).
Frequently acquired via a Digital Measurement
TS Logic position
UTC Universal Time Co-ordinates (or Universal Time Code)

Naming that replace GMT (but it is the same)
VMGA Vertical Measurement Graphical Area
Voltage level Set of bays whose plants & devices are dealing with same voltage (e.g. 275kV)
VT Voltage Transformer
WYE Three phases + neutral AI values
xPC Single Point Control or Double Point Control
xPS Single Point Status, Double Point Status or Multi Point Status
Schneider Electric
35 rue Joseph Monier
92500 Rueil Malmaison
France
+33 (0) 1 41 29 70 00
https://www.se.com
As standards, specifications, and designs change from time to time,

please ask for confirmation of the information given in this publication.
© 2010 - 2022 Schneider Electric. All Rights Reserved..
EcoSUI/EN UM/K5_RC2

EcoSUI EN UM K5

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EcoSUI EN UM K5

Uploaded by

Copyright:

Available Formats

EcoSUI

Human Machine Interface

Version: EcoSUI/EN UM/K5

To the extent permitted by applicable law, no responsibility or liability is assumed by Schneider

35 rue Joseph Monier

The addition of either symbol to a "Danger" or "Warning" safety label

Failure to follow these instructions will result in death or serious injury.

Failure to follow these instructions could result in injury or equipment damage.

Failure to follow these instructions could result in equipment damage.

It is recommended that incineration and disposal to water courses is avoided. The

2. Overview of EcoSUI User Guide....................................................................... 2

3. Reference Documents ....................................................................................... 3

4. Files list used and indicated in the manual .................................................... 3

5. Understanding the use of EcoSUI Secured and EcoSUI Standard ............... 3

2. OVERVIEW OF ECOSUI USER GUIDE

The EcoSUI user guide includes:

2.1 CHAPTER DESCRIPTIONS

4. FILES LIST USED AND INDICATED IN THE MANUAL

5. UNDERSTANDING THE USE OF ECOSUI SECURED AND ECOSUI

2 Performances and Limitations .................................................................. 2

1 SCOPE OF THE DOCUMENT

2 PERFORMANCES AND LIMITATIONS

EcoSUI HMI Client Limits

LAN Dataflow Dataflow of a LAN

Failure to follow these instructions can result in injury or equipment damage

Failure to follow these instructions can result in injury or equipment damage.

2.3 ECOSUI HMI CLIENT CAPABILITY

Maximum number of HMI Clients 12

2.4 ACQUISITION INSTANCE CAPABILITY

2.5 ARCHIVED DATA

2.5.1 DATABASE SIZE

Archived Data Limits

• "Events" table records the digital signals.

• "Values_X" table records measurements values.

2.5.2 CENTRAL DATABASE REDUNDANCY

2.5.3 MULTI-CENTRAL DATABASE

2.6 CRISIS DATAFLOW

2.7 TIME SYNCHRONIZATION

1 SCOPE OF THE DOCUMENT

Fig1. EcoSUI Modules

Modules of EcoSUI Suite

EcoSUI deployment software (to download databases, switch databases,

2.1 MINIMUM REQUIREMENTS

2.1.1 OPERATING SYSTEM

• Windows® Server 2019

2. EcoSUI Suite Overview ............................................................................ 6

3. Install EcoSUI ......................................................................................... 10

5. EcoSUI Configuration Deployment ......................................................... 24

7. Uninstall EcoSUI ..................................................................................... 34

1. SCOPE OF THE DOCUMENT

1.1.1 SUPPORTED PLATFORMS

1.1.2 BEFORE INSTALLATION

1.1.3 THIRD-PARTY TOOLS

Step Item Action

Step Item Action

1.1.4 SPECIAL REQUIREMENTS FOR WINDOWS® 10

1 From Control Panel of computer:

NOTE: Restart computer to apply UAC turned off.

2. ECOSUI SUITE OVERVIEW

2.2 INSTALLATION PACKAGE

Fig 1: EcoSUI Modules

Modules of EcoSUI Suite