SCE Enm C60

System Configuration Editor
Technical Manual
System version: 5.1.0
SCE/EN M/C60
DS Agile SCE Technical Manual
CONTENTS
INTRODUCTION SCE/IT EN/C60
SAFETY AND HANDLING SCE/SA EN/C60
FUNCTIONAL DESCRIPTION SCE/FT EN/C60
INSTALLATION SCE/IN EN/C60
ADJUSTMENTS SCE/AJ EN/C60
APPLICATION SCE/AP EN/C60
HUMAN INTERFACE SCE/HI EN/C60
MAINTENANCE SCE/MF EN/C60
PROBLEM ANALYSIS SCE/PR EN/C60
RECORD SHEET SCE/RS EN/C60
TECHNICAL DATA SCE/TD EN/C60
GLOSSARY SCE/LX EN/C60

Product /Project name – Type of document
WARNING
This guide gives instructions for installation, commissioning and operation of the DS Agile SCE. However,
the guide can not cover all conceivable circumstances or include detailed information on all topics. In the
event of questions or specific problems, do not take any action without proper authorization. Please,
contact the appropriate Alstom technical sales office and request the necessary information.
Refer to the System Release Notes for new features.
Any agreements, commitments, and legal relationships and any obligations on the part of Alstom,
including settlement of warranties, result solely from the applicable purchase contract, which is not
affected by the contents of the guide.
INTRODUCTION
SCE/EN IT/C60
DS Agile System Configuration Editor Introduction
Contents
1 INTRODUCTION TO DS AGILE 3
2 INTRODUCTION TO DS AGILE MANUALS 4

2.1 Chapter description 4
3 INTRODUCTION 6
SCE/EN IT/C60 IT-1

Introduction DS Agile System Configuration Editor
IT-2 SCE/EN IT/C60

1 INTRODUCTION TO DS AGILE
The DS Agile range will continue to be expanded. The general features of DS Agile will also be enhanced, as
we are able to adopt new technology solutions.
For up-to-date information on any DS Agile product, visit our website: www.grid.alstom.com
SCE/EN IT/C60 IT-3

2 INTRODUCTION TO DS AGILE MANUALS

This manual provides a functional and technical description of the DS Agile System Configuration Editor and
instructions for the DS Agile SCE’s use and application.
Important note:
The MiCOM Alstom range of C264 substation and bay computers is being widened to encompass new
applications such as the process bus Ethernet network. On this occasion, the name of the range becomes
DS Agile. Because new models will soon be available, the name C264 is replaced by C26x in the manuals.
Similarly, the C26x setting software will now be called DS Agile S1 instead of MiCOM Alstom S1.
Please note that this is a phased evolution, and where the text in the manual refers to software labels, there
may still some references to the previous names until the software update is completed.
In addition, the C26x units will now be referred to as "controllers" rather than "computers" in order to avoid
any confusion with the PC-type computers used in other DS Agile sub-systems.
2.1 CHAPTER DESCRIPTION

Introduction (IT) Chapter
This is this document containing the description of each chapter of the DS Agile SCE guides. It is a brief
introduction to DS Agile SCE capabilities.
Safety (SA) Chapter
This chapter contains the safety instructions, handling and reception of electronic equipment, packing and
unpacking parts, Copyrights and Trademarks.
Functional Description (FT) Chapter
This chapter contains a description of the product. It describes the functions included in DS Agile SCE.
Installation (IN) Chapter
This chapter contains the installation procedures.
Adjustments (AJ) Chapter
This chapter contains the list of adjustments required by the DS Agile SCE.
Application (AP) Chapter
This chapter contains the fundamentals of ISaGRAF workbench.
HMI, Local control and user interface (HI) Chapter
This chapter contains the operator interface description, Menu tree organisation and navigation,
Setting/configuration software.
Maintenance, Fault finding, repairs (MF) Chapter
This chapter lists warnings and notes automatically generated by SCE and their causes.
Problem analysis (PR) Chapter
This chapter provides practical examples of problem solving and company contact information. It includes all
information on the self-checking features and diagnostics of DS Agile SCE.
Record Sheet (RS) Chapter
This chapter provides detailed record sheets to record DS Agile SCE installation data.
IT-4 SCE/EN IT/C60

Technical Data (TD) Chapter

This chapter contains the technical data including, accuracy limits, recommended operating conditions,
ratings and performance data.
It also describes environment specification, compliance with technical standards.
Glossary (LX) Chapter
This chapter contains lexical description of acronyms and definitions of the DS Agile SCE.
SCE/EN IT/C60 IT-5

3 INTRODUCTION
DS Agile SCE is defined to handle all system structured data and to generate databases loaded on DS Agile
System main equipment:
 DS Agile OI, the Operator Interface for local HMI

 DS Agile SMT, the System Management Tool that download databases
 DS Agile Gateway, the separate Tele-control Interface to the SCADA
 DS Agile C26x controllers (Bay Control Units, Protection and Control Units, Remote Terminal Units)
The tool is designed to be used for several system pieces of equipment working together with their exchange
communication data, or only one of them. For example it can generate the database of a DS Agile C26x-
Standalone RTU.
The DS Agile SCE applications are mainly defined in the Application chapter (AP) of each DS Agile sub-
system (DS Agile C26x, DS Agile Gateway, DS Agile OI).
IT-6 SCE/EN IT/C60

SAFETY & HANDLING
SCE/EN SA/C60
DS Agile System Configuration Editor Safety & Handling
Contents
1 INTRODUCTION 3
2 SAFETY 4
2.1 Health and Safety 4
2.2 Explanation of symbols and labels 4
2.3 Installing, Commissioning and Servicing 4
3 WARRANTY 5
4 COPYRIGHTS & TRADEMARKS 6

4.1 Copyrights 6
4.2 Trademarks 6
5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS 7
SCE/EN SA/C60 SA-1

Safety & Handling DS Agile System Configuration Editor
SA-2 SCE/EN SA/C60

1 INTRODUCTION
The present document is a chapter of the DS Agile system documentation. It describes the safety
procedures applicable to DS Agile SCE software tools.
SCE/EN SA/C60 SA-3

2 SAFETY
Warning:
This Safety Section should be read before commencing any work on the equipment.
2.1 HEALTH AND SAFETY

The information in the Safety Section of the DS Agile System documentation is intended to ensure that
products are properly installed and handled in order to maintain them in a safe condition. It is assumed that
everyone who will be associated with the DS Agile System equipments will be familiar with the contents of
the different DS Agile System Safety Sections and all Safety documents related to the PC and
Communication networks.
2.2 EXPLANATION OF SYMBOLS AND LABELS

The meaning of symbols and labels may be used on the DS Agile System equipments or in the DS Agile
System product documentation, is given below.
2.3 INSTALLING, COMMISSIONING AND SERVICING
Equipment operating conditions

The DS Agile System equipments should be operated within the specified electrical and
environmental limits.
Fibre optic communication

Optical LED transceivers used in Switch boards are classified as IEC 825-1 Accessible Emission
Limit (AEL) Class 1 and consequently considered eye safe.
Optical power meters should be used to determine the operation or signal level of the device.
SA-4 SCE/EN SA/C60

3 WARRANTY
The media on which you receive Alstom’s software are warranted not to fail to execute programming
instructions, due to defects in materials and workmanship, for a period of 90 days from date of shipment, as
evidenced by receipts or other documentation. Alstom will, at its option, repair or replace software media that
do not execute programming instructions if Alstom receives notice of such defects during the warranty
period. Alstom does not warrant that the operation of the software shall be uninterrupted or error free.
A Return Material Authorization (RMA) number must be obtained from the factory and clearly marked on the
package before any equipment will be accepted for warranty work. Alstom will pay the shipping costs of
returning to the owner parts which are covered by warranty.
Alstom believes that the information in this document is accurate. The document has been carefully reviewed
for technical accuracy. In the event that technical or typographical errors exist, Alstom reserves the right to
make changes to subsequent editions of this document without prior notice to holders of this edition. The
reader should consult Alstom if errors are suspected. In no event shall Alstom be liable for any damages
arising out of or related to this document or the information contained in it.
Except as specified herein, Alstom makes no warranties, express or implied, and specifically disclaims any
warranty of merchantability or fitness for a particular purpose.
Customer's rights to recover damages caused by fault or negligence on the part of Alstom shall be limited to
the amount therefore paid by the customer. Alstom will not be liable for damages resulting from loss of data,
profits, use of products or incidental or consequential damages even if advised of the possibility thereof.
This limitation of the liability of Alstom will apply regardless of the form of action, whether in contract or tort,
including negligence. Any action against Alstom must be brought within one year after the cause of action
accrues. Alstom shall not be liable for any delay in performance due to causes beyond its reasonable
control.
The warranty provided herein does not cover damages, defects, malfunctions, or service failures caused by
owner's failure to follow the Alstom installation, operation, or maintenance instructions; owner's modification
of the product; owner's abuse, misuse, or negligent acts; and power failure or surges, fire, flood, accident,
actions of third parties, or other events outside reasonable control.
SCE/EN SA/C60 SA-5

4 COPYRIGHTS & TRADEMARKS
4.1 COPYRIGHTS
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or
mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in
whole or in part, without the prior written consent of Alstom.
4.2 TRADEMARKS
Alstom, the Alstom logo and any alternative version thereof are trademarks and service marks of Alstom.
The other names mentioned, registered or not, are the property of their respective companies.
SA-6 SCE/EN SA/C60

5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS

Alstom products are not designed with components and testing for a level of reliability suitable for use in or in
connection with surgical implants or as critical components in any life support systems whose failure to
perform can reasonably be expected to cause significant injuries to a human.
In any application, including the above reliability of operation of the software products can be impaired by
adverse factors, including -but not limited- to fluctuations in electrical power supply, computer hardware
malfunctions, computer operating system, software fitness, fitness of compilers and development software
used to develop an application, installation errors, software and hardware compatibility problems,
malfunctions or failures of electronic monitoring or control devices, transient failures of electronic systems
(hardware and/or software), unanticipated uses or misuses, or errors from the user or applications designer
(adverse factors such as these are collectively termed "System failures").
Any application where a system failure would create a risk of harm to property or persons (including the risk
of bodily injuries and death) should not be reliant solely upon one form of electronic system due to the risk of
system failure to avoid damage, injury or death, the user or application designer must take reasonably steps
to protect against system failure, including -but not limited- to back-up or shut-down mechanisms, not
because end-user system is customised and differs from Alstom testing platforms but also a user or
application designer may use Alstom products in combination with other products.
These actions cannot be evaluated or contemplated by Alstom; thus, the user or application designer is
ultimately responsible for verifying and validating the suitability of Alstom products whenever they are
incorporated in a system or application, even without limitation of the appropriate design, process and safety
levels of such system or application.
SCE/EN SA/C60 SA-7

SA-8 SCE/EN SA/C60

FUNCTIONAL DESCRIPTION
SCE/EN FT/C60
DS Agile System Configuration Editor Functional Description
Contents
1 DS AGILE SCE ARCHITECTURE 3

1.1 General Description 3
1.2 Functional Specification 3
1.2.1 DS Agile SCE Users 4
1.2.2 DS Agile SCE Template & Object 4
1.2.3 Database creation process 5
1.2.4 Version & release 6
1.3 External Interfaces 6
SCE/EN FT/C60 FT-1

Functional Description DS Agile System Configuration Editor
FT-2 SCE/EN FT/C60

1 DS AGILE SCE ARCHITECTURE
1.1 GENERAL DESCRIPTION

The System Configuration Editor (DS Agile SCE) is the central tool in charge to manage the DS Agile system
database for the DS Agile equipment. The system configuration database contains the configuration data for
the DS Agile system equipment:
 DS Agile OI, the Operator Interface

 DS Agile SMT, the System Management Tool used to download databases
 DS Agile Gateway for remote control
 DS Agile C26x controller
The DS Agile SCE allows some authorised personnel to interact with the DS Agile system configuration:
 modelling of coherent system configuration data: devices, electrical topologies, graphical mimics,
automations
 generation of configuration data-file for IEC 61850-8-1 devices of the DS Agile project
To generate any equipment database, the DS Agile SCE manages:
 Inner data of the device itself (structure and parameters values)

 Exchange data of the device with other system devices
 Exchange data of the device with non-system devices
With the 3rd case, the DS Agile SCE manages the communication with all non-DS Agile devices with typically
IED or protection devices on Legacy BUS or system network. It is only by the configuration of communication
mapping that DS Agile SCE can handle non-DS Agile devices.
1.2 FUNCTIONAL SPECIFICATION

The DS Agile System Configuration Editor is a tool that:
 helps in definition/edition of equipment data with specific editors (attribute, mimic, ISaGRAF) or with
queries on configuration
 generates equipment databases

The definition of data is done firstly by the definition by developer experts of templates or models of data.
These templates are then stored and delivered in DS Agile SCE libraries. In a second time, the models can
be loaded and instanced as a clever kind of duplication to create object data customised to the application
case.
When all data of the concrete case are defined, the DS Agile SCE generates a coherent set of databases
that can be loaded into each system device.
SCE/EN FT/C60 FT-3

1.2.1 DS AGILE SCE USERS

Control access of an operator is realised through a login and password capture.
Different levels of operators are distinguished depending on its role:
 Level 1 allows the modification of an existing configuration by adjustment of parameters, settings or

graphical representations. The users of level 1 can also add or remove elements derived from the user
template libraries. They can generate DS Agile application databags. Level 1 users are typically final
users.
 Level 2 allows the modification of an existing configuration by adding or removing elements derived
from the user templates libraries. They can break the links between the templates and the instantiated
objects. Like level 1 users they can generate DS Agile application databags. Level 2 users are
Integrators and VARs.
 Level 3 users have the capability to modify and create new templates derived from the existing
template libraries. They can generate DS Agile application databags but also template libraries. User
of level 3 will be all DS Agile specialists.
 Level 4 users are DS Agile SCE experts. They can modify and create the templates directly from the
structural database elements. Their DS Agile SCE user level allows also the management of all
template databases and the administration of the structural database. The level 4 users are the DS
Agile SCE administrators.
Such categories is only an outline of DS Agile SCE users since several of its tools thanks to specific editors,
or report managers, can provided the records needed by other tasks: commissioning cubicle, mapping
extraction, etc.
1.2.2 DS AGILE SCE TEMPLATE & OBJECT

A database is basically a collection of persistent data. In the DS Agile SCE framework, a database is a
collection of objects. Any object has its specific attributes, organised in categories and subcategories. The
objects are organised in the database by following pre-defined association rules.
The structural database defines object types and association types. Association types are hierarchical
link types and relation link types between object types. Hierarchical links are defined for father/child
associations. Relation links are defined for other associations, and may hold attributes. Cardinalities are
defined for all associations.
A library database contains templates. A template is a collection of objects/associations instantiated from
the structural database or from others templates.
A configuration database contains objects/associations instantiated from types of the structural database
or from templates. It also contains its own templates, created specifically for the configuration, or imported
from a library database. A configuration database defines all data needed by system devices to feel up
customer application.
All the database elements support internationalisation (multiple languages).
FT-4 SCE/EN FT/C60

1.2.3 DATABASE CREATION PROCESS

To create the database downloaded to system devices, the common way is to:
 Import a template from an external library into current database (in its template area)
 Customise the template if needed in DB template area
 Instantiated the template from template to Object part of the database
 Fill up the predefined attribute known as degree of freedom (for example the name)
 Generate devices databases
The link between template and instantiated object can be kept. Nevertheless this relation can be broken for
deep object modifications.
During all this creation process, the DS Agile SCE does a check of data coherency with its Data Model. The
checks are made with templates and objects. The checks are made during configuration edition and/or by a
check action. They are done on:
 Attribute input
 Relation creation
 Generation
Configuration database
Library = Collection of Models

Local templates Configuration Objects =
Configuration
Instance 1
Import Template Instance 2
Instance n
S0126ENa
Figure 1: Configuration Process
SCE/EN FT/C60 FT-5

1.2.4 VERSION & RELEASE

Over time, the system’s device features have evolved and their inner data base structure is subject to
modification. DS Agile SCE needs to fill the new requirement and has also evolutions and corrections
referenced by version.
A unique reference determines the coherent set of system equipment database and soft/hard equipment that
DS Agile SCE can use.
DS Agile SCE can compare two referenced versions of a configuration.
1.3 EXTERNAL INTERFACES
Interface
files
Data Model
External tools
Xml files
CMT C26x
ISaGRAF
fully integrated SCE SMT OI
workbenches
System
FBD databag
Gateway
Equipment
Simulator
Template Configuration
libraries S0478ENb
Figure 2: External interfaces
There are no software interfaces between DS Agile SCE and other external tools or DS Agile devices.
External interfaces are implemented through files:
 Xml files: the user can export or import a whole configuration or only a subset. A DS Agile SCE
exchange Xml format is defined for describing files which are:
 exported from SCE to an external tool
 imported from an external tool to DS Agile SCE
FT-6 SCE/EN FT/C60

 System databag: from a referenced version of a configuration, DS Agile SCE generates an application
databag for each DS Agile devices. The application databags are bagged in a System databag. The
system databags are used by DS Agile SMT to download application databag in each DS Agile
devices. This system databag can be used by DS Agile ES.
 Reports: the user selects a whole configuration or only a subset and asks a report. A predefined report
in pdf format is delivered with DS Agile SCE.
Notes:
All IEC 61850-8-1 clients must be defined in the SCD file during an export, in order to know the defined client / server
relation(s).
From a SCL point of view, an IEC 61850-8-1 client is an IED with an “Access Point” structure without “Server” element.
The MiCOM Alstom Px4x Phase 2 provide ICD files in which Virtual Inputs are defined (a Virtual Input is an abstract
element which allows to define an attachment to a GOOSE in MiCOM Alstom IED).
The SCE, during an ICD import, creates these Virtual Inputs in a specific area of the IED IEC 61850-8-1 mapping.
Then, these Virtual Inputs can be associated to datapoints (using relations) defined in the electrical area.
Importing graphical object whose level is lower or equal to mimic is not supported.
SCE/EN FT/C60 FT-7

FT-8 SCE/EN FT/C60

INSTALLATION
SCE/EN IN/C60
DS Agile System Configuration Editor Installation
Contents
1 SCOPE OF THE DOCUMENT 3
2 INSTALLATION REQUIREMENTS 4
3 DS AGILE SCE INSTALLATION 5

3.1 Cyber-Security 5
3.2 DS Agile SCE core software 5
3.2.1 Summary 6
3.2.2 DS Agile SCE Detailled Installation Description 6
3.2.3 Check installation 8
3.2.4 vcredist_X86.exe 9
3.2.5 Troubleshooting 9
3.2.6 Windows 7 9
3.3 DS Agile XML Parser 11
3.4 ISaGRAF software 14
3.4.1 ISaGRAF workbench 14
3.4.2 ISaGRAF data access 16
3.4.3 ISaGRAF upgrade 16
3.5 msxml.dll 17
4 DS AGILE SCE UNINSTALL 18
5 INSTALLATION OF GROOVY ENVIRONMENT 19
SCE/EN IN/C60 IN-1

Installation DS Agile System Configuration Editor
IN-2 SCE/EN IN/C60

1 SCOPE OF THE DOCUMENT

This document is a chapter of the DS Agile System Configuration Editor (SCE) documentation. It describes
the installation of this engineering tool.
SCE/EN IN/C60 IN-3

2 INSTALLATION REQUIREMENTS
DS Agile SCE can be installed onto desktop or laptop PC depending on the use of it:
 checking data
 parameter modification
 prototyping substation
 template/model development
 full substation data definition
 equipment database generation
For data base development purpose, the needed PC is defined with:
 CPU Core II duo 2.66 GHz

 RAM: at least 2 GB with Windows XP, at lease 4 GB with Windows 7
 Required hard disk space: at least 400 MB without IsaGRAF, 1 GB with IsaGRAF
 Screen display: 1024*768 resolution minimum
DS Agile SCE itself uses less than 400 MB but the optional documentation (data model) and versioned
databases require far more space ( several GB, depends on databases).
DS Agile SCE runs on Microsoft XP Pro SP3 or Windows 7 Ultimate. There are no extra requirements for its
installation.
To install the package, log on as an administrator (DCS_Master, see DS Agile Network and System Security
Guide (DS Agile/EN CS)).
IN-4 SCE/EN IN/C60

3 DS AGILE SCE INSTALLATION

The DS Agile SCE software installation is broken down into several parts depending on the license
agreement:
 DS Agile SCE core software

 DS Agile Operator Interface XML Parser (option for OI, available in the OI package)
 CJ International ISaGRAF Pro for configurable automation (option)
 DS Agile SCE Report generating tools (MSXML.dll optional library)
Optional DS Agile SCE Libraries of customized templates and data bases are also available upon request.
They are not discussed here.
After the installation, some parameters need to be set as described in chapter SCE/EN AJ.
Note:
Acrobat Reader 5.0 or higher is required to display the documentation.
3.1 CYBER-SECURITY
Caution:
Before starting to configure the PC and install applications, you should be
thoroughly familiar with the DS Agile Network and System Security Guide
(DS Agile/EN CS).
Before installing the DS Agile software, a number of pre-requisite steps are needed in order to properly
secure the system.
These steps are documented in the DS Agile Network and System Security Guide.
The Network and System Security Guide is available both as a chapter of the DS Agile technical manual and
as a stand-alone document. This guide describes the security-related steps that must be implemented
BEFORE, DURING and AFTER the installation and adjustments of DS Agile software applications.
Before moving on to installing the DS Agile software, make sure these pre-requisite steps are executed.
3.2 DS AGILE SCE CORE SOFTWARE

The versioned DS Agile SCE software is installed via a set-up wizard. The default items are the most
common ones.
In case of upgrade, read the release note carefully as it explains optional upgrade procedures. The software
will be copied under a new directory.
The software version is displayed all installation phase long; it is expressed for example by:
 5.1.7:
 5: the 1st number is the DS Agile system version with fixed features set and Data model version
 1: the 2nd number is an iteration number for the given version (that includes minor evolution)
SCE/EN IN/C60 IN-5

 7: the ending number is an optional release number.
3.2.1 SUMMARY
Standard installation takes less than 5 minutes. It mainly creates the directory C:\Program
files\Alstom\DCS\sce that includes two sub-folders:
 Java that includes jrex.y.z with Java Run Time Engine (or JRE). For instance, jre1.4.2
 x.y.z that includes the versioned software product
3.2.2 DS AGILE SCE DETAILLED INSTALLATION DESCRIPTION

First double click on sce_installer_x.y.exe. This launches InstallAnywhere software:
Figure 1 - Installation of installer
The InstallAnywhere asks then for the appropriate installation language. A scrolling list shown in Fig 2 helps
select it.
Figure 2 - Selecting “InstallAnywhere” Installation Language
After language selection it is proposed to cancel installation or to go ahead clicking Next.
IN-6 SCE/EN IN/C60

Figure 3 - InstallAnywhere installation completed
Next screen proposes to accept the terms of the Licence Agreement. Next button is enabled only if the
choice “I accept…” has been done.
InstallAnywhere software is then installed and proposes the SCE installation. There is no choice for selecting
the directory of Java Real-Time Engine, but DS Agile SCE can be installed anywhere thanks to a “Choose”
option. Nevertheless it seems more appropriate to use the default ALSTOM/DCS directory, where other
DS Agile tools may be installed. All installation is then done on C: (100MB for SCE, 90 MB for JRE libraries,
400 MB for documentation in option Complete installation).
Next screen propose to choose the DS Agile SCE software main directory. A subdirectory will be anyway
created, and named sce/x.y (with version reference). From this screen the window header or title repeats the
version to install.
SCE/EN IN/C60 IN-7

Figure 4 - DS Agile SCE directory selection
Select the Next button leads to define what can be installed: software only / software+ html catalogue of
attributes.
Figure 5 - Selection of installation scope
Click Next. When the summary is displayed, all installation settings are entered. It is still possible to stop the
installation via the cancel button.
3.2.3 CHECK INSTALLATION

During installation, Java heap max size is automatically set at 2/3 of ram size, max 1.3 GB.
Configure the software as described in chapter SCE/EN AJ.
IN-8 SCE/EN IN/C60

3.2.4 VCREDIST_X86.EXE
Run the vcredist_X86.exe file located in
C:\Program files\ALSTOM\DCS\sce\<SCEVersion>\data\cal\setting\vcredist_x86
If it is not correctly installed, the setbuilder program producing the setting files for the DS Agile C26x might
not work.
3.2.5 TROUBLESHOOTING
If the SCE does not start, try these actions:
 modify the sce.lax file (available in the installation folder) to update the
lax.nl.java.option.java.heap.size.max attribute according to the memory size of your PC (to 400 MB
if the memory size is 1GB)
 check the dates of the msxml.dll files located in the C:\Windows\system32 or

C:\Windows\sysWOW64 folder: if they are different from those provided, replace them and do not
install any third-party applications afterwards.
3.2.6 WINDOWS 7
If the SCE is installed on a PC with the Windows 7 OS, the .mpx compressed folder that the SCE generates
when the user checks in a database contains a .odt file. That extension is also used by Open Office for their
Word Processing files and in Windows 7 it is added to the search index list by default.
In order to avoid compatibility issues, it is necessary to remove the .odt extension from Windows 7's search
index. To do so:
1 Open the menu
2 Type "index" in the search box and Enter

3 Open Indexing Options in the list that is then displayed
4 Click Advanced
5 Select the File Types tab and scroll down to the "odt" extension
6 Make sure the corresponding box is NOT ticked
7 Click OK
SCE/EN IN/C60 IN-9

IN-10 SCE/EN IN/C60

3.3 DS AGILE XML PARSER

If the host PC is used for generating DS Agile OI databases, the software DS Agile XML Parser is required.
For DS Agile XML Parser, double click on
\\ <OIVersion> \PROGRAMS\XML Parser\setup.exe
An InstallShield wizard welcome screen is displayed. Click on Next >:
SCE/EN IN/C60 IN-11

Accept the terms of the license agreement then click on Next >:
Select the Complete installation, then click on Next >:
IN-12 SCE/EN IN/C60

Finally the DS Agile OI XML Parser is stored in D:\S2K_HMI\XSL

Restart your computer to ensure that XML Parser will run correctly.
SCE/EN IN/C60 IN-13

3.4 ISAGRAF SOFTWARE
3.4.1 ISAGRAF WORKBENCH

ISaGRAF is a tool for the definition of automation. This software use is subject to license.
1 Launch the installer and select Install ISaGRAF
2 Select install all ISaGRAF components, then Next and finally Install
IN-14 SCE/EN IN/C60

3 Depending on previous software installations on the PC, it may be suggested installing OPC Core
Components Redistributable. Unless this function is used for another purpose, it is not necessary to
install it. Select Cancel.
4 Finally accept to reboot the PC
If you have chosen to install the workbench in a folder different than C:\Program Files\ICS Triplex ISaGRAF,
change the ISaGRAF path in the SCE menu Tools > Options. Refer to the chapter SCE/EN AJ.
SCE/EN IN/C60 IN-15

3.4.2 ISAGRAF DATA ACCESS

To compile ISaGRAF project from DS Agile SCE and if Microsoft Access 97 is not installed, you need MS
Office 97 ValuPack.
Install the ODBC driver (dataacc.exe) provided in the MS Office 97 Value Pack. You can download the MS
Office 97 Value Pack from:
 http://www.microsoft.com/ and search for these key words “Office 97 ValuPack”. Make sure that you
spell ValuPack the Microsoft way: it is a registered trademark name.
 http://www.microsoft.com/downloads/en/details.aspx?familyid=BEFD7842-602E-42B0-89D2-
6BE39F1167C1&displaylang=en
Office 97 SR-2b is a free update to Office 97, consisting of a series of recent fixes and designed to make it
even easier for customers to deploy Office 97. SR-2b includes currently available downloads such as the
Microsoft Excel 97 for Windows Auto-Recalculation Patch.
3.4.3 ISAGRAF UPGRADE

If you have a dongle for ISaGRAF 5.13, you can upgrade it to 5.22.
To do this, install license manager. Then, insert the dongle for 5.13 and launch license manager. Do this
procedure for each dongle, one at a time.
 Download and install the dongle management software Sentinel Protection on the ISaGRAF USB
dongle. This dongle software is available at:
http://c3.safenet-inc.com/downloads/0/F/0FE57DCB-3A4A-4197-9728-
EDF352C04562/Sentinel%20Protection%20Installer%207.2.2.exe
 Install the License Manager application.

 Insert the dongle for 5.22
 Start the License Manager application.
 The License Manager window shows that the dongle is for ISaGRAF 5.1X:
IN-16 SCE/EN IN/C60

 Click OK. The License Manager window shows:
 To claim your upgrade from ISaGRAF Version 5.13 to ISaGRAF Version 5.22, click Send... The
License Manager sends the User codes 1 and 2 to ISaGRAF support:
[email protected]
 ISaGRAF sends you the Registry keys 1 and 2.

 Type the Registry keys 1 and 2 in the License Manager. Click Proceed.
 The Upgrade of the dongle is complete. Remove the dongle.
Note: The User codes are not regenerated if you change your dongle before upgrade it.
3.5 MSXML.DLL
Check the msxml.dll file dates in the Windows/system32 or C:\Windows\sysWOW64 folder: if they are
different from those provided in Tools / msxml_dlls.zip file (in DS Agile CD-ROM folder), replace them and do
not install any third-party applications afterwards.
SCE/EN IN/C60 IN-17

4 DS AGILE SCE UNINSTALL

DS Agile SCE can be uninstalled directly with the menu Start | All Programs | Alstom | DCS.
For other software, use Windows tools:
“Start | Control panel | Add or Remove Programs“ and select:
 DS Agile XML Parser for HMI

 ISaGRAF PRO
 …
IN-18 SCE/EN IN/C60

5 INSTALLATION OF GROOVY ENVIRONMENT
1 Install the JAVA JRE version as per SCE Release Note (download the required JAVA JRE version at
http://java.com/). It's normally done by the SCE set-up program.
2 In the Windows Configuration Panel of the SCE machine using the JAVA console check the system
and user JAVA JRE version
SCE/EN IN/C60 IN-19

3 In the Windows Configuration Panel using the JAVA console configure JAVA Updates to never check
for updates automatically
IN-20 SCE/EN IN/C60

4 Open the webpage http://groovy.codehaus.org/Download?nc

5 Scroll down to Groovy 1.6.9
6 Select Download: Binary Release
7 Save the zip file (groovy-binary-1.6.9.zip) to your hard drive
8 Unzip the file to {DS AGILE_SCE_DIRECTORY}\ScriptsManager\
9 Run {DS AGILE_SCE_DIRECTORY}\ScriptsManager\groovy-1.6.9\bin\groovyConsole.bat
The Groovy Console is launched.
SCE/EN IN/C60 IN-21

IN-22 SCE/EN IN/C60

ADJUSTMENTS
SCE/EN AJ/C60
DS Agile System Configuration Editor Adjustments
Contents
2 DS AGILE SCE ADJUSTMENTS 6

2.1 Lax file (Off-line) 6
2.2 Paths (On-line) 6
2.3 Alstom DS Agile SCE settings import 8
2.4 ISaGRAF adjustments for a redundant WACU 8
3 REGISTRY KEYS 11
4 PC LANGUAGE AND CHARACTER SETS 12
SCE/EN AJ/C60 AJ-3

Adjustments DS Agile System Configuration Editor
AJ-4 SCE/EN AJ/C60


This document describes the adjustments - or on-line - parameters, which can be modified during the
installation time or in SCE runtime.
SCE/EN AJ/C60 AJ-5

2 DS AGILE SCE ADJUSTMENTS
2.1 LAX FILE (OFF-LINE)

 To force clean (that is compact) & save during a database upgrade, add in SCE.lax:
Dsce.CleanOnUpgrade="true"
 To disable the merge of ISaGRAF functions when a PLC contains only one function, add this line to
the file SCE.lax:
Dsce.NoPLCMergeForOneFunction="true"
 To optimize management of the PC RAM, it is necessary to adjust Java heap size.

During installation, Java heap max size is automatically set with 2/3 of ram size, max 1.3 GB.
After installation, Java heap max size could be updated manually: modify the parameter
lax.nl.java.option.java.heap.size.max (bytes) in file sce.lax. This parameter must not exceed 1.3
GB. File sce.lax is in the installation directory.
After ram size updating (add or remove ram), run script UpdateLaxFile.vbs in install directory: this script
updates Java heap min size with 32 MB and max size with 2/3 of new ram size, max 1.3 GB..
Note: Some PC BIOS do not allow to assign more than 1.25 GB to a single application. Check with your PC technical
document before setting the PC memory in the sce.lax.
2.2 PATHS (ON-LINE)

After installation, give DS Agile SCE the external tools paths. Start it:
Start | All Programs | Alstom | DCS | Configuration Editor x.y/SCE
Then in DS Agile SCE window, select in menu bar the “Tools/Options…” item.
Figure 1: Alstom DS Agile SCE Setting after Installation
A window “Setting Manager” opens with all DS Agile SCE settings.

The tool paths installed as options have to be entered. Their values must be updating according to their
installation folders. It is especially the case for:
 ISaGRAF Workbench path setting: the installation folder of ISaGRAF tool.

 Acrobat Reader Application path: the binary file path of Acrobat Reader.
The other settings do not depend of other tools or others installations:
 General part settings: the properties of DS Agile SCE (read only).

 Status bar part settings: the displaying options of status bar.
 Graphic part settings: the graphical editors (mimic editor, bay mimic editor,…) options.
 Access part settings: default working paths.
 Miscellaneous part setting: device generation options or general edition options.
AJ-6 SCE/EN AJ/C60

Figure 2: Alstom DS Agile SCE Setting Manager
The path can be entered directly, or by selecting the associated button to start an explorer and choose a
directory.
SCE/EN AJ/C60 AJ-7

2.3 ALSTOM DS AGILE SCE SETTINGS IMPORT

A settings set can be imported from a previous version of DS Agile SCE. This operation avoids modifying
default settings after each DS Agile SCE installation.
This feature is available through the Import button of DS Agile SCE Setting Manager dialog box.
The following Select dialog box is then displayed. A settings file of a previous DS Agile SCE version must be
chosen.
Figure 3: Alstom DS Agile SCE Setting import
After its selection, the settings of the opened DS Agile SCE are updated with these settings.
2.4 ISAGRAF ADJUSTMENTS FOR A REDUNDANT WACU

To connect ISaGRAF workbench to both redundant WACUs hosting ISaGRAF (for example in the aim of
target loading, debug or monitoring…), it is possible to set network properties with mirror target IP
addresses.
AJ-8 SCE/EN AJ/C60

STEP EXPLANATION DISPLAY
In ISaGRAF Workbench, “Hardware

architecture”, select connection between
01 ETCP network and configuration.
By a right click, select “Properties”.
On the first tab “Network Parameters”, set

02
primary WACU IP address.
SCE/EN AJ/C60 AJ-9


On the second tab “Mirror targets”, click on
“Add” button in order to set secondary WACU IP
address.
It is necessary to build/rebuild project/library in
order to take into account network settings
03
NOTE:
If needed, it is possible to add other addresses
in order to connect ISaGRAF workbench to
other resources targets.
Connect to one of the WACU by clicking:
 “Download” ;
 “Debug Target” ;
 “Simulation”
The window allows the user to choose to
04 connect to one of the targets (the main target or
one of the mirror targets).
NOTE:
The “ETCP.EXE” and “ISAGRAF.EXE”
processes have to be launched on WACU in
order to establish communication with ISaGRAF
workbench.
AJ-10 SCE/EN AJ/C60

3 REGISTRY KEYS
The DS Agile SCE application records a registration key:
HKEY_LOCAL_MACHINE\SOFTWARE\Alstom\DS AGILE\System Configuration Editor\5.0
which has the following strings value:
Name Type Data Usage
InstallDir REG_Z C:\Program Files\Alstom\DCS Where to find the SCE executable
This key is issued by the installation procedure of a patch to erase files of an already installed version.
SCE/EN AJ/C60 AJ-11

4 PC LANGUAGE AND CHARACTER SETS

When a database is to be generated for use with a DS Agile OI running on a PC set up for a language that
requires a specific character set, such as Swedish for instance, the PC running SCE should be configured
for the same language when the database is generated in order to ensure compatibility and avoid any
potential text display problems.
To do so, follow these steps (Swedish is used as an example):
Windows 7
 Go to Start → Control Panel.

 Select Region and Language Options. The Region and Language window appears.
 Change the current system locale to Swedish in the Administrative tab-pane
 Change the current location to Swedish in the Location" tab-pane
Windows XP
 Go to Start → Control Panel.

 Select Regional and Language Options. The Regional and Language Options window appears.
 Select the Standard and Formats and choose Swedish. Set the location to Sweden:
AJ-12 SCE/EN AJ/C60

 Go to the Advanced tab-pane and set Language for non-Unicode programs to Swedish and select
the appropriate character code in the Code page conversion tables box, 20107 (IA5 Swedish) in this
example:
Without this operation, minor text display problems such as in the example below could occur:
Text string displayed when the regional option is set

to Swedish (special character correctly displayed)
Text string displayed when the regional option is not

set to Swedish (special character replaced with a
standard letter)
S1057ENa
SCE/EN AJ/C60 AJ-13

AJ-14 SCE/EN AJ/C60

APPLICATION
SCE/EN AP/C60
DS Agile System Configuration Editor Application
CONTENTS
2 DATABASE UPGRADE 4
2.1 Important migration notes 4
2.1.1 System hierarchy organisation 4
2.1.2 SBUS automatic addressing 4
2.1.3 IEC 60870-compliant circuit-breaker management 6
2.2 Individual migration 7
2.3 Batch migration 7
2.4 Profile migration 7
3 ALSTOM DS AGILE IEC 61850-8-1 PROJECTION 8

3.1 Logical Device Rules 10
3.2 Logical Node Rules 11
3.3 DataObject Rules 12
3.4 GOOSE Rules 19
3.5 Driving the import process through command lines 21
4 FBD EDITOR 24
4.1 Overview 25
4.2 FBD Editor Views 26
4.2.1 FBD Editor View 26
4.2.2 The FBD Overview 27
4.2.3 Toolbar 27
4.2.4 Library Toolbar 28
4.2.5 Logging View 28
4.2.6 Key Functions 29
4.3 Understanding FBD 30
4.3.1 Graphical component on the Editor View 30
4.3.2 Language Elements 31
4.3.3 Text Annotations 34
4.3.4 Evaluation strategy 34
4.4 Equation Viewer 34
4.4.1 FBD document 34
4.4.2 Navigation Features 35
4.4.3 Zoom Features 36
4.4.4 Selection Model 37
4.4.5 Functions and Function Blocks 40
4.4.6 Signal Flow Lines (SFL) 43
4.4.7 Slots 45
4.4.8 FBD Network 46
4.4.9 FBD Graphical Controls 49
4.4.10 FBD Semantical Controls 51
4.4.11 Working with Literals 51
4.4.12 Working with Text Annotations 53
4.4.13 Printing FBD Documents 54
4.4.14 Popup Activity Lists 55
SCE/EN AP/C60 AP-1

Application DS Agile System Configuration Editor
4.5 Defining an FBD fast automation 57

4.5.1 Creating an FBD fast automation (header definition) 57
4.5.2 Creating FBD input plug (header definition) 58
4.5.3 Creating FBD output plug (header definition) 59
4.5.4 Using FBD editor (body definition) 59
4.5.5 Linking datapoints to FBD inputs and outputs 61
5 COUPLING SCE DATA MODEL AND ISAGRAF 63

5.1 ISaGRAF presentation 63
5.1.1 ISaGRAF workbench description 63
5.1.2 Directories structure of ISAGRAF 64
5.1.3 Uploaded files towards the target 65
5.2 Usage of SCE datapoints in ISaGRAF 65
5.2.1 Hierarchical relation: Function management DPs 66
5.2.2 Server relation 66
5.2.3 Client relation 66
5.2.4 Access rights summary table 67
5.2.5 Equivalence of SCE datapoint in ISaGRAF 67
5.2.6 ISaGRAF variables and dictionary data structures 68
5.2.7 Kernel Interface API 72
5.2.8 Prototype and usage of Alstom DS Agile functions for ISaGRAF 73
5.3 Caveats 83
5.4 WACU redundancy with ISaGRAF 83
5.4.1 Switch automation for redundancy 83
5.4.2 ISAGRAF programmation best practices 84
5.5 Defining an ISaGRAF slow automation 85
5.5.1 Creating an ISaGRAF slow automation (header definition) 85
5.5.2 Adding specific datapoints to a slow automation (interface definition) 87
5.5.3 Creating an ISaGRAF client link (interface definition) 87
5.5.4 Linking a datapoint to an ISaGRAF client link 89
5.5.5 Defining Isagraf IO prefix for an input 89
5.5.6 Creating ISaGRAF server link (interface definition) 90
5.5.7 Linking a datapoint to an ISaGRAF server link 91
5.5.8 Defining ISaGRAF IO prefix for an output 92
5.5.9 Using ISaGRAF editor (body definition) 93
AP-2 SCE/EN AP/C60


The present document describes:
 the way to regenerate a database after an SCE upgrade

 the station bus automatic addressing of datapoints. The SBUS protocol implemented in DS Agile
Station Bus complies with the IEC 61850-8-1 standard. The non-DS Agile IEDs are out of the scope of
this document.
 the command lines

 the FBD editor
 the ISaGRAF workbench
SCE/EN AP/C60 AP-3

2 DATABASE UPGRADE
Most of the time, between two consecutive versions of DS Agile SCE, database upgrade is made only by
starting a new DS Agile SCE version, and loading the old database. A message upgrade is displayed. The
saved database is upgraded to the new DS Agile SCE version.
Good practice: Store DB from a special DS Agile SCE version, in a separate directory that includes DS Agile
SCE DB version and name DB with DS Agile SCE version included.
Between major releases of the DS Agile SCE (that is with different major version numbers), the structural
database might change.
2.1 IMPORTANT MIGRATION NOTES
2.1.1 SYSTEM HIERARCHY ORGANISATION

As of DS Agile version 5.0.5, there are only 2 types of objects at the root of the Ethernet network in the
System hierarchy:
 the SMT (System Configuration Tool):

The SMT object is unique. It is automatically added when a database is created (as of DS Agile version
5.0.4) or imported from an earlier version (before DS Agile version 5.0.4), and must be configured (see
SMT/EN AP for details).
 the System Group:

The System Group contains all the sub-systems and devices other than the SMT. It can contain the
devices managing, monitoring and/or protecting one or more electrical bays. It does not impact actual
functionality and does not impair a device's ability to manage several electrical bays.
As of DS Agile version 5.0.5, one empty System Group is automatically added when a database is
created. It is not possible to add more. Devices and sub-systems are then added to the System Group
from the contextual Objects entry window.
When importing a database created with an earlier version of DS Agile (in which the system devices were
placed at the root of the Ethernet network branch), a System Group is created and all the existing device
and sub-system objects (spared or not), except for the SMT object, are placed in that System Group.
2.1.2 SBUS AUTOMATIC ADDRESSING

As of version 5.0.5 of the DS Agile System, SBUS Automatic Addressing is incremental: The addresses of
non-spared, unmodified datapoints with existing valid addresses are left unchanged and unused addresses
are assigned to as yet unaddressed datapoints and datapoints with invalid addresses if there are any.
Existing invalid addresses in a database migrated from an earlier version of DS Agile SCE could in some
cases be duplicated after the first incremental SBUS automatic addressing operation. If this happens, the
corresponding errors will appear in the Checks window (after pressing F6) with the error code 13020,
indicating which sub-system has duplicated addresses:
AP-4 SCE/EN AP/C60

To prevent this problem, delete the address maps of all the DS Agile sub-systems immediately after
database migration:
and then run SBUS automatic addressing again.
SCE/EN AP/C60 AP-5

2.1.3 IEC 60870-COMPLIANT CIRCUIT-BREAKER MANAGEMENT

As of version 5.1.0 of the DS Agile System, the configuration of circuit-breakers and other switchgear is
modified for compliance with the IEC 60870-7-4 standard, as certified by Kema. As a result, database
migrations from previous versions will involve some reconfiguration:
 Some IEC 61870-8-1 addresses have been removed, and some datapoints that did not use to have
one, now have an IEC 61870-8-1 address. This means that it is necessary to run SBUS automatic
addressing after migration.
 The SPS datapoints used for open/close controls (Switch Ctrl SPC, Switch phA/B/C SPC) and their
feedbacks (Switchgear pos., PhA/B/C pos. SPS) have been removed. They must be replaced with
DPS datapoints.
 The attribute circuit-breaker type has been replaced by a choice between two objects to add under
the circuit-breaker node: Single phase and Triple phase. Where the attribute circuit-breaker type
was previously set to Triple phase CircuitBreaker or Single phase CircuitBreaker, the corresponding
Single phase/Triple phase objects are automatically created under the circuit-breaker node when
importing the database. The value Other is no longer valid and no equivalent is provided in the new
format.
 For circuit-breakers only, the wired DPS switchgear datapoints (formerly Switchgear pos. for 3-pole
CBs and Switch phA/B/C pos. for 1-pole CBs) have been moved. New Switchgear pos. DPS are
automatically inserted under the Single phase\Phase x and Triple phase nodes. They need to be
redefined: Relations, including "wiring", must be recreated and their profiles need to be re-assigned
manually.
 New datapoints have been added under the circuit-breaker/switchgear objects and it will be necessary
to create and assign profiles to these new datapoints.
Note:
The CB Healthy SPS datapoint that could previously be used to prevent the initiation of a Type 1 auto-reclosing cycle
has been removed. No equivalent datapoint is available at this time.
Do not try to use the new CB Healthy MPS datapoint instead. It is reserved for future use and HAS NO EFFECT on the
auto-recloser.
Note:
Because the redefinition of circuit-breakers is fairly extensive, it is recommended to open a copy of the original
database in its associated version of DS Agile SCE in order to match the configuration step by step.
AP-6 SCE/EN AP/C60

2.2 INDIVIDUAL MIGRATION

To upgrade a database, install an instance of all the intermediate major SCE releases and proceed
iteratively.
Example: migration from system version 4.6 to 4.7:
1 Export DB from the oldest SCE version (e.g. 4.56.x.x)
 Launch the oldest SCE version
 Open the DB to upgrade
 Select the menu File/ Prepare Upgrade & Save (save DB with additional data); take care not to
save again the database with the menu File/Save.
 Close this SCE version
2 Import DB into a newer SCE version (e.g. 4.72.x.x) and export the DB
 Launch the newer SCE version
 Open the upgraded DB
 Select the menu File/Check
 Correct the potential errors
 Select the menu File/ Save for mandatory upgrade; take care not to save again the database with
the menu File/Save
 Select the menu File/Create a copy to put it into the 4.72 directory
 Close this SCE version
3 Import DB into the newest SCE version (e.g. 4.73.x.x) and export the DB
 Launch the newest SCE version
 Open the latest upgraded DB
 Select the menu File/Check
 Correct the potential errors
 Select the menu File/Create a copy to put the file into the 4.73 directory
2.3 BATCH MIGRATION

Two scripts are available in C:\Program Files\Alstom\DCS\sce\4.xx\batch:
 prepareUpgradeDB.bat: to open and save for mandatory upgrade the database

 UpgradeDB.bat: to open, upgrade and save the database
2.4 PROFILE MIGRATION

Select the menu Data/Upgrade to indiced profile to compute the new profile reference of each datapoint
(object and template) to the profile table (refer to chapter C26x/EN AP).
SCE/EN AP/C60 AP-7

3 ALSTOM DS AGILE IEC 61850-8-1 PROJECTION

The IEC 61850-8-1 mapping of an IED is an aggregation of Logical Devices (LD), composed of Logical
Nodes (LN), Functional Components (FC) and Data Objects (DO). This mapping is used to model the subset
of substation’s electrical devices managed by the server.
IEC 61850-8-1 DS Agile device
+ has for IEC 61850 client + has for IEC 61850 server
0..n 0..n
+ has for IEC 61850 server 0..n 0..n + has for IEC 61850 client
IEC 61850-8-1 IED IEC 61850-8-1 DS Agile device
1 1
IEC 61850-8-1 mapping
1..n Datapoint
Logical device
0..1
1..n + is IEC 61850 address of

Logical node
1..n
Functional component
+ has for IEC 61850 address

1..n
0..1
Data object
S0470ENb
AP-8 SCE/EN AP/C60

Electrical plant items are modelled according to the following structure:
Site
Datapoint
0..*
1
0..* 0..*
Substation 0..*
0..n
+ is default IEC 61850 server for 1..*
Voltage level
0..n
+ is default IEC 61850 server for 1..*
Bay
+ manages
0..n
0..*
+ has for default IEC 61850 server
1 0..1 1 1 Module
+ is managed by + is managed by + is managed by
DS Agile BCU DS Agile Gateway IEC 61850 IED
S0471ENb
SBUS Automatic addressing consists in creating or updating an IEC 61850-8-1 map, in particular linking
DataObjects to Datapoints. This process follows rules that are defined per hierarchical level: Logical Devices,
then Logical Nodes then DataObjects.
As of version 5.0.5 of the DS Agile System, SBUS Automatic Addressing is incremental: The addresses of
non-spared, unmodified datapoints with existing valid addresses (for instance, in case of version upgrade or
system extension) are left unchanged and unused addresses are assigned to as yet unaddressed datapoints
and datapoints with invalid addresses if there are any. By allowing existing datapoints to keep their
IEC 61850-8-1 addresses when new datapoints are added (and addressed), this evolution can be especially
useful where an existing system is being expanded or to integrate non-DS Agile devices.
SBUS automatic addressing only applies to datapoints produced by DS Agile devices (C264, OI, Gateway,
etc...). It does not process IEC 61850-8-1 addresses for non-DS Agile devices, such as for instance
protection IEDs or measurement centres: Those must be added manually from an import datalist file.
In effect, a new SBUS automatic addressing operation will make no changes to a non-spared datapoint with
a valid IEC 61850-8-1 address nor to a datapoint managed by a non-DS Agile IEC 61850-8-1 IED, even if:
 its destination changes (e.g.: a datapoint that was sent to a DS Agile OI is now being sent to a DS
Agile Gateway only),
 the IEC 61850-8-1 address of another datapoint changes when its configuration is modified (i.e.:
datapoint type change, MV configuration change, feedback added to an xPC, etc...),
 SBUS automatic addressing removes the IEC 61850-8-1 addresses of spared or deleted datapoints,
 SBUS automatic addressing re-assigns the addresses of spared or deleted datapoints to new
datapoints of the same type (SPS, DPS, etc...),
 the database is upgraded to a newer version of DS Agile SCE.
SCE/EN AP/C60 AP-9

Process
For each DS Agile device, Automatic addressing proceeds as follows:
 it removes any IEC 61850-8-1 addresses that are no longer compatible with the linked datapoints,
 it removes incomplete IEC 61850-8-1 addressing relations (e.g.: where a relation "has for
IEC 61850-8-1 address" has been manually added but not filled in),
 it links relevant datapoints to new IEC 61850-8-1 addresses.

Exception
System datapoints used for diagnostic reports by the DS Agile devices ("DIAG" bricks, except "IEDDIAG")
have their IEC61850-8-1 addresses re-assigned upon each new SBUS automatic addressing operation.
These addresses may therefore change if system datapoints are added or deleted but this is of no
consequence because they are internal to the DS Agile system and have no effect on substation control.
Dataset/Report
Third-party devices subscribed directly to a Logical Node:
In this case, if a datapoint is added or deleted, the Logical Node may be altered by SBUS automatic
addressing. This can have an impact on the completeness of the report exchanged with a non-DS Agile
device.
If a datapoint transmitted in a report is deleted or removed from that report, it is possible to replace that
datapoint with a fake datapoint of the same type (SPS, DPS, etc...) in the report so that the position of other
datapoints is not impacted by that removal and the report remains compliant with what any client third party
device(s) would expect..
If a new datapoint is added to a report, the Logical Node is impacted and all the devices that subscribe to
this Logical Node should be reconfigured.
3.1 LOGICAL DEVICE RULES

 One Logical Device LD0 is created for each Alstom DS Agile SBUS devices.
LD0 is pre-defined for each type of IED (C26x, Gateway, OI) and contains some system information of
the IED: an LN DIAG (only for Gateway and OI), an LN LLN0 and two empty LNs DBID and LPHD are
defined and used by system datapoints of the device.
Each LN DIAG contents all device status.
For the OI, there is the DataObjects of status (relative to SPS datapoint OI Client link) referenced by
index of each OI Client linked to this OI Server.
 One Logical Device SYSTEM is created for the C26x and for its Extensions (Legacy IED, SCADA
Network and Extension Rack).
Under this LD SYSTEM is defined a DIAG Logical Node named as:
 C26xDIAG for the C26x,
 IEDDIAGy for a legacy IED y with y in the interval [1, n],
 TCIDIAGy for a SCADA Network y with y in the interval [1, n],
 C26xEDIAGy for an Extension Rack y with y in the interval [1, n].
The DIAG contains DataObjects on the state of the communication between OI Client and OI server. For
the C26x and its Extension Racks, each input or output of board has its DataObject of status referenced
by index.
For the C26x and its Legacy IED, the LD SYSTEM contains also an LN LLN0 and an empty LN LPHD.
AP-10 SCE/EN AP/C60

During edition, this LD is named only SYSTEM. Nevertheless during generation of .dm file for the Legacy
IEDs, this Logical Device is prefixed by the <IED_name> (e.g. IEDMB1SYSTEM).
 One Logical Device CONTROL is created for each DS Agile C26x unit. It contains Logical Nodes and
DataObjects used for mapping Electrical objects (Substation / Voltage Level / Bays / Module /
Datapoints).
 One Logical Device PROTECTION is created for a DS Agile C26x protection and control unit that
manages Relay Built-in functions.
 One Logical Device MEASUREMENT is created for a C26x that manages:

 measurements computed by a C26x TMU200 or TMU210 or TMU220 board
 measurements linked to an Energy counting function.
3.2 LOGICAL NODE RULES

 All Logical Nodes are suffixed by a number: default value is 1, range is [1..9 999 999];
except for LLN0 and some LNs of LD0.
 A Logical Node name must be unique in the whole IEC 61850-8-1 mapping, except LLN0, DBID &
LPHD. The uniqueness is done with number suffix (see previous rule).
 One Logical Node SYSTEM/C26xDIAG is created for each C26x.

 One Logical Node SYSTEM/IEDDIAG is created for each C26x Legacy IED.
 One Logical Node SYSTEM/TCIDIAG is created for each C26x SCADA protocol.
 An LN SYSTEM/RDRE is created for the Legacy IED SPS ‘disturbance file ready’.
 A Logical Node CONTROL/GBAY is created for each bay that is managed by a server and that
contains some particular bay datapoints.
 A Logical Node is created for each module of bay that is managed by a server:
Bay module IEC 61850-8-1 LD and LN
Circuit breaker CONTROL/CSWI or CONTROL/XCBR
Switchgear CONTROL/CSWI
Capacitor CONTROL/ZCAP
Converter CONTROL/ZCON
Generator CONTROL/ZGEN
Motor CONTROL/ZMOT
Transformer CONTROL/YPTR
Auto-recloser CONTROL/RREC
Synchro-check CONTROL/RSYN
ATCC CONTROL/ATCC
Tap Changer CONTROL/YLTC
AVR CONTROL/AVCO
 A Logical Node CONTROL/GAPC is created for each User function/Slow Automation (ISaGRAF)
under the server where the automation runs (relation ‘runs on:’).
 Some Logical Nodes CONTROL/GGIO are created for generic modules. A generic module is a non-
typed module. Numerical suffix is used when several GGI0 exists. The number of GGIO is
SCE/EN AP/C60 AP-11

minimized with the following assertion:

No more 50 ST DataObjects could be defined under the same GGIO.
No more 50 MX DataObjects could be defined under the same GGIO.
No more 50 SP DataObjects could be defined under the same GGIO.
No more 50 CO DataObjects could be defined under the same GGIO.
 A Logical Node CONTROL/CILO is created for all xPC datapoints for which Interlocking datapoints
are defined.
 A Logical Node CONTROL/RDRE is created for the C26x SPS ‘disturbance file ready’.
 A LN is created for each threshold of bay relay function that is managed by a server.
Bay relay built-in function IEC 61850-8-1 LD and LN / threshold
[27] Phase undervoltage PROTECTION/PTUV
[32N] Earth wattmetric PROTECTION/PDOP
[37] Phase under current PROTECTION/PTUC
[46] Seq inv overcurrent PROTECTION/sqPTOC
[49] Thermal overload PROTECTION/PTTR
[50BF] Breaker failure PROTECTION/RBRF
[59] Phase overvoltage PROTECTION/phPTOV
[59N] Earth over voltage PROTECTION/gndPTOV
[67] Phase dir overcurrent PROTECTION/phPTOC
[67N] Earth dir overcurrent PROTECTION/gndPTOC
[81U] Under Frequency PROTECTION/PTUF
[81O] Over Frequency PROTECTION/PTOF
[81R] Range Frequency PROTECTION/PFRC
General Trip PROTECTION/PTRC
Automation PROTECTION/GGIO
3.3 DATAOBJECT RULES

 Default dataObject naming rule: a dataObject (DO) is created with a name and a common class
under a Functional Component and a Logical Node. This Logical Node represents the parent of the
datapoint: a bay, a module, a built-in function or a user function. Logical Node rules are defined in the
previous section.
Datapoint could be linked to another datapoint through relation ‘has for feedback’.
With SBO or without SBO is the SBO mode value of the datapoint profile.
The column Functional Component (FC) indicates the data objects created for one
datapoint: a dataObject by component. SV components are optional.
The column DataObject Common classes (CDC) indicates the common class used for each
dataObject of datapoint.
AP-12 SCE/EN AP/C60

SCE Datapoint class FC DO default Name IEC 61850-8-1 CDC

SPS_ST, SPS_SV
ACT_ST, ACD_ST
ACx_ST_Phs.general
SPS without associated xPC ST, SV Ind ACx_ST_Phs.phsA,
ACx_ST_Phs.phsB,
ACx_ST_Phs.phsC,
ACx_ST_Phs.neut
SPS with linked xPC without SBO ST, SV SPCSO SPC_Orig_ST, SPS_SV
SPS with linked xPC with SBO ST, SV SPCSO SPC_Orig_ST, SPS_SV
DPS without associated xPC ST, SV Ind DPS_ST, DPS_SV
DPS with linked xPC without SBO ST, SV DPCSO DPC_Orig_ST, DPS_SV
DPS with linked xPC with SBO ST, SV DPCSO DPC_Orig_ST, DPS_SV
INS8_ST, INS_SV (INC_ST)
ACD_ST_Phs.dirGeneral,
Mod,Beh, Health, ACD_ST_Phs.dirPhsA,
MPS (16 states max) ST, SV
AutoRecSt, IntIn, … ACD_ST_Phs.dirPhsB,
ACD_ST_Phs.dirPhsC,
ACD_ST_Phs.neut
MPC (16 states max) CO Mod, FanCtl, … INC8_Direct, Direct_CF
MV_MX, MV_SV, MV_CF
CMV_MX
WYE.phsA, WYE.phsB, WYE.phsC ,
MV without associated Setpoint MX, SV, CF AnIn
WYE.neut
DELTA.phsAB, DELTA.phsBC,
DELTA.phsCA
MV with linked Setpoint MX, SV, CF AnIn APC_Orig_MX, MV_SV, APC_CF
Tap position MV with linked Raise/lower
ST, SV TapChg BSC_Orig_ST, BSC_SV
DPC (=BSC)
Accumulator ST, CF Cnt BCR_ST, BCR_CF
INS Generic integer status without linked OpCnt, FltNum, IntIn,
ST, SV INS_ST (32 bits), INS_SV
INC (operation counter) …
INS Generic integer status with linked
ST, SV OpCntRs, ISCSO, … INC_Orig_ST (32 bits), INS_SV
INC (resetable operation counter)
INC without SBO Controlable Integer CO, CF OpCntRs, ISCSO, … INC_Direct, Direct_CF
INC with SBO Controlable Integer CO, CF OpCntRs, ISCSO, … INC_SBO_Sec, SBO_CF
SPC without SBO CO, CF SPCSO SPCDPC_Direct, SBO_CF
SPC with SBO CO, CF SPCSO SPCDPC_SBO_Sec, SBO_CF
DPC without SBO CO, CF DPCSO SPCDPC_Direct, SBO_CF
DPC with SBO CO, CF DPCSO SPCDPC_SBO_Sec, SBO_CF
Raise/Lower DPC(BSC) for TPI without
CO, CF TapChg BSC_Direct, BSC_CF
SBO
Raise/Lower DPC(BSC) for TPI with
CO, CF TapChg BSC_SBO_Sec, BSC_CF
SBO
Analog Setpoint without SBO CO, CF APC_Direct, APC_CF
Analog Setpoint with SBO CO, CF APC_SBO_Sec, APC_CF
 Particular dataObject naming rule is refined for some datapoints. The Logical Node under which the
DataObject is created depends on the Logical Node rules.
Only common classes different from the default common classes are re-defined in this table. The
default common class is derived from the type of the datapoint and the previous table. The type of
datapoint is indicated by the last part of datapoint mnemonic. For example AR_Status_MPS is an
MPS.
SCE/EN AP/C60 AP-13

Specific
Datapoint Datapoint DataObject
Parent common
mnemonic name Name
classes
LocRemSubstation Local/remote DPS LocSubst
Substation
LocRemSubstation_DPC Loc/rem ctrl DPC LocSubst
LocRemBay Local/remote DPS Loc
LocRemBay_DPC Loc/rem ctrl DPC Loc
Bay OrderInProgress (SPS) Order running OrdRun SPS_ST
SBMCBay SBMC SPS SBMCDS
SBMCBay_SPC SBMC control SPC EnaSBMC
LockModule Lock SPS Lock
Module LockModule_SPC Lock control SPC Lock
OrderInProgress (SPS) Order running OrdRun SPS_ST
Select (SPS) Phys. selection Sel
Switch_DPC_PhA Switch phA DPC PosA
Switch_DPC_PhB Switch phB DPC PosB
Circuit breaker
Switch_DPC_PhC Switch phC DPC PosC
Switch_DPC Switch Ctrl DPC Pos
ComputedSwitchPos_DPS Comp. swit. pos. Pos
Select (SPS) Phys. selection Sel
Switchgear Switch_DPC Switch Ctrl DPC Pos
SwitchPos Switchgear pos (DPS) Pos
CS_AcceptForcing_SPS Accept forcing ForcAlw
CS_AuthoState_SPS Possible closing EnaCls
CS_CloseOrderState_SPS Close order ClsOpSt
CS_CtrlOnOff_DPC on/off ctrl DPC Ena
CS_CtrlOnOff_SPC on/off ctrl SPC Ena
Synchrocheck CS_Locked_SPS CS locked LockSt
built-in function CS_OnOff_DPS on/off DPS Ena
CS_OnOff_SPS on/off SPS SyncSt
CS_VoltageAbsence_SPS Voltage absence VAbs
CS_VoltagePresence_SPS Voltage presence VInd
CS_VoltageRefAbsence_SPS Ref. U absence VRefAbs
CS_VoltageRefPresence_SPS Ref. U presence VRefInd
AR_CtrlOnOff_DPC on/off ctrl DPC Ena
AR_FaultReason_MPS Autorecloser flt ARFlt
Autorecloser AR_OnOff_DPS on/off Ena
built-in function AR_Status_MPS Autorecloser st ARSt
Trip_SPS Trip 3 phases Trip3P
Ctrl3PhaseTrip_SPC Force trip 3P Trip3P
Tap changer TAPHigherPos_SPS Higher position HiTapPos
built-in function
TAPInProgress_SPS Tap in progress TCIP
TAPLowerPos_SPS Lower position LoTapPos
TAPSelect_SPC TAP Select SPC TapPos
MCBCtrlOpen_SPC MCB open SPC OpnMCB
SPI Tap pos ind TapChg BSC_ST
AP-14 SCE/EN AP/C60

Specific
Parent common
mnemonic name Name
classes
BSC_DIRECT
RaiseLower_DPC Raise/lower DPC TapChg BSC_SBO_Sec
BSC_CF
XX_thresholdY_inst
With : XX = function number * inst. Str ACD_ST
Y = threshold number
Relay built-in XX_threshold_Y_mode
INC8_ST
function With : XX = function number * mode Mod
Direct_CF
threshold Y = threshold number
XX_thresholdY_temp
With : XX = function number * temp. Op ACT_ST
Y = threshold number
Relay [49] built- 49_th_alarm 49 th alarm AlmThm ACT_ST
in function 49_th_overload 49 th overload Op ACT_ST
Relay [67N] 15A_over_current 15A over-current Op15Amps ACT_ST
built-in function
1_2_s_over_current 1.2 s over-cur. OpTmRSEA ACT_ST
– optional
EPATR function EPATR_RSE_Mode EPATR RSE mode RSEMod INS_ST
Relay [50] built- 50BF_breaker_failure break fail OpIn ACT_ST
in function 50BF_breaker_failure_mode Break fail mode Mod INC8_ST
ATCC built-in ATCC_Alarmed_SPS ErrorLog AtcFlt
function
ATCC_BusbarCtrlOnOff_SPC ATCC on/off ctrl EnaBus1
ATCC_BusbarCtrlTarget1_SPC ATCC targ 1 ctrl EnTg1Bus1
ATCC_BusbarInhibited_SPS ATCC inhibited BusInh1
ATCC_BusbarInterTargetRunning
ATCC to target TargIP1
_SPS
ATCC_BusbarInvalidModule_SPS ATCC inv module BusDvInv1
ATCC_BusbarInvalidVoltage_SPS ATCC inv voltage BusVInv1
ATCC_BusbarMaxTRFReached_
ATCC max transfo MoreTrf1
SPS
ATCC_BusbarOnOff_SPS ATCC on/off EnaBus1
ATCC_BusbarTarget1Running_S
ATCC target 1 EnTg1Bus1
PS
PS
PS
PS
PS
ATCC_BusbarVoltage_MV BusBar voltage Vbus1
ATCC_CtrlClearAlarm_SPC ATCC clear alarm ClearFlt
ATCC_CtrlOnOff_SPC ATCC on/off ctrl Ena
SCE/EN AP/C60 AP-15

Specific
Parent common
mnemonic name Name
classes
ATCC_DBIOverride_SPS DBI override DBIOver
ATCC_MCBPos_DPS MCB position DPS MCBPos
ATCC_MCBPos_SPS MCB position SPS MCBPos
ATCC_MCBTrip_SPS MCB trip MCBTr1
ATCC_OnOff_SPS on/off Ena
ATCC_TAPBadTCIP_SPS TAP bad TCIP BadTCIP1
ATCC_TAPInvalidTCIP_SPS TAP invalid InvPos1
ATCC_TAPLongTCIP_SPS TAP long TCIP LongTCIP1
ATCC_TAPRunAway_SPS Run away RunAway
ATCC_TXFFaultOnEqptDisc_SPS ATCC disc eqpt DcnxTrf1
ATCC_TXFFaultOnLocalBay_SP
ATCC local bay LocTrf1
S
ATCC_TXFHoming_MPS ATCC homing HomTrf1
ATCC_TXFHunting_SPS ATCC hunting HuntTrf1
ATCC_TXFInvalidVoltage_SPS ATCC inv voltage Vinv
ATCC_TXFLowerActivePower_M
Second. active P PTrf1
V
ATCC_TXFLowerCurrent_MV Second. current ITrf1
ATCC_TXFLowerReactivePower_
Second. react. Q QTrf1
MV
ATCC_TXFLowerVoltage_MV Second. voltage VTrf1
ATCC_TXFOnOff_SPS ATCC on/off ModTrf1
ATCC_TXFOverCurrent_SPS ATCC overcurrent OCTrf1
ATCC_TXFOverVoltage_SPS ATCC overvoltage OVTrf1
ATCC_TXFUnderVoltage_SPS ATCC low-voltage UVTrf1
ATCC_TargetNotReached_SPS target unreached TarNach
OpenIntlkSPS Open intlk SPS EnaOpn
xPC
CloseIntlkSPS Close intlk SPS EnaCls
 Particular dataObject naming rule is refined for some datapoints:

 MV computed by TMU200,TMU210 or TMU220,
 Counter which integrates energy (function energy counter)
For a C26x, only one Logical Node rmsMMXU, powMMXU, effMMXU and MMTR exists.
The table below gives the IEC 61850-8-1 objects (LD, LN, FC, DO) for each type of MV/counter.
Common DataObject DataObject MV type MV type
classes Parent path (LD/LN/FC/DO) Name Name id
phsA VAN, RMS value of the voltage phase A 0
WYE_MX,
MEASUREMENT/rmsMMXU1/MX phsB VBN, RMS value of the voltage phase B 1
WYE_CF,
/phV phsC VCN, RMS value of the voltage phase C 2
WYE_SV
neut Vr, RMS value of voltage 3
DEL_MX, phsAB VAB, RMS value of the voltage phase AB 4

MEASUREMENT/rmsMMXU1/MX
DEL_CF, phsBC VBC, RMS value of the voltage phase BC 5
/PPV
DEL_SV
phsCA VCA, RMS value of the voltage phase CA 6
AP-16 SCE/EN AP/C60

Common DataObject DataObject MV type MV type

classes Parent path (LD/LN/FC/DO) Name Name id
phsA IA, RMS value of the current phase A 7
WYE_MX,
MEASUREMENT/rmsMMXU1/MX phsB IB, RMS value of the current phase B 8
WYE_CF,
/A phsC IC, RMS value of the current phase C 9
WYE_SV
neut Ir, RMS value of current 10
MV_MX,
MV_CF, MEASUREMENT/rmsMMXU1/MX Hz network frequency 36
MV_SV
MV_MX,
MV_CF, MEASUREMENT/powMMXU1/MX TotW Pt, total active power 26
MV_SV
MV_MX,
MV_CF, MEASUREMENT/powMMXU1/MX TotVAr Qt, total reactive power 27
MV_SV
MV_MX,
MV_CF, MEASUREMENT/powMMXU1/MX TotPF cos φt: Power factor 29
MV_SV
phsA mod Ia (ADC) 184
WYE_MX,
MEASUREMENT/effMMXU1/MX/ phsB mod Ib (ADC) 185
WYE_CF,
A phsC mod Ic (ADC) 186
WYE_SV
neut mod Io (ADC) 187
DEL_MX, phsAB mod Vab (ADC) 188

MEASUREMENT/effMMXU1/MX/
DEL_CF, phsBC mod Vbc (ADC) 189
PPV
DEL_SV
phsCA mod Vca (ADC) 190
DataObject DataObject Counter

Common classes
Parent path (LD/LN/FC/DO) Name Name
Counter which integrates Reactive Energy of an
TotWh
BCR_ST, BCR_CF MEASUREMENT/MMTR1/ST MV
TotVArh Counter which integrates Active Energy of a MV
INC_Orig_St, INC_SV MEASUREMENT/GGIO OpCntRS Operating Counter (feedback of Setpoint
Setpoint having as feedback an Operating
INC_Direct, Direct_CF MEASUREMENT/GGIO OpCntRS
Counter
INC_ST, INC_SV MEASUREMENT/GGIO OpCnt Operating Counter (alone)
 DataObjects of datapoints linked with ‘has for feedback’ relation have the same name: the
dataObject name of the xPC.
 Coupling between DataObjects linked to the same datapoint is done by naming: theses DataObjects
located under different Functional Components (SV, CF) have the same name.
 SV dataObject is optional. It exists if flag ‘enable Force/Subst/Sup’ of profile of datapoint is set to

‘Yes’.
 Only non-spared datapoints are taken into account in automatic addressing. If a formerly spared
datapoint is "unspared", then an automatic addressing operation must be done again.
 Some datapoints are out of scope of automatic addressing. These datapoints are identified by their
data model mnemonic and their short name.
SCE/EN AP/C60 AP-17

Parent Excluded mnemonic datapoint Excluded Datapoint name

SynCheck_Close_DPC Sync CB close
SynCheck_Close_SPC Sync CB close
Select_SPC Selection SPC
Switch_SPC_Ph[A|B|C] Switch ph[A|B|C] SPC
Module Circuit breaker
SwitchPos_SPS_Ph[A|B|C] Switch Ph[A|B|C] pos.
SwitchPos (DPS) Switchgear pos.
SwitchPos_SPS Switchgear pos.
PhaseNotTogether_SPS Ph not together
External automatic synchrocheck built-in CS_CtrlOnOff_DPC on/off ctrl DPC
function CS_CtrlOnOff_SPC on/off ctrl SPC
XX_thresholdY_trip
with XX = function number * Trip
Y= threshold number
XX_thresholdY_inst_dir_rev
Relay built-in functions with XX = function number * in di rev
Y= threshold number
XX_thresholdY_interlock
with XX = function number * interlock
Y= threshold number
Relay [automation] built-in function start_disturbance start dist ctrl
Relay [49] built-in function 49_trip_th_overload 49 trip th over
EPATR_DSP_RSE_Mode EPATR DSP RSE
EPATR_enable_disable EPATR.ON.OFF
Relay [67N] built-in function – optional
EPATR_in_out_service EPATR.IN.OUT.SER
EPATR function
EPATR_Tri EPATR.TRI
EPATR_State EPATR.STATE
Electre built-in functions ElecARS_tccyc1p bCYC.MONO
Wild char (*) or pseudo regular expression ([A|B|C]) is used to specify several datapoints.
 Some computed measurements are out of scope of automatic addressing. Theses MV are
identified by their type name and their type id.
MV type name MV type id

mod Vo (ADC) 307
mod I1 (ADC) 308
mod I2 (ADC) 309
mod V1 (ADC) 310
mod V2 (ADC) 311
thermal status 312
AP-18 SCE/EN AP/C60

3.4 GOOSE RULES

Only MX/ST/LSP DataObjects under Functional Components MX, ST and LSP can be goosed. A dataObject
is GOOSE-transmitted if the linked DP is used in a remote automation (FBD, ISaGRAF). ‘Remote’ means
that the server of the DP is not the server of the automation.
The following datapoints are always GOOSE-transmitted:
 ‘Global Alarm Acknowledgement’ SPS

 ‘Main status MV’ SPS (FailSt) for C26x units in redundancy (main + backup)
 IEC 61850-8-1 communications between main and backup C26x units; the attribute ‘goose usage’ of
this relationship client/server is forced to ‘Goose only’
The Automatic Goose transmission flag of a dataObject contains these conditions.
The Manual Goose transmission flag of a dataObject is set manually (relation ‘has for IEC address’).
Between 2 automatic addressing operations, this flag value is kept if the dataObject still exists.
A DataObject is GOOSE-transmitted if Automatic or Manual Goose transmission flags are true.
If a Goose datapoint with an IEC 61850-8-1 address is deleted or removed from a GOOSE, then it is
possible to replace that datapoint with a virtual GOOSE datapoint of the same type (SPS, DPS, etc...) and
same GOOSE rank in order to maintain the system's compatibility with third party devices.
The Capacity of each goose (one for ST, one for MX, three for LSP) is limited to 1000 bytes.
For each type of object, the GOOSE-transmitted data might differ. Here is the list of data leaves transmitted
using goose for each type of Data Object:
Data Object Data leaves
SPS_ST
SPC_ST, SPC_Orig_ST
DPS_ST
stVal
DPC_ST, DPC_Orig_ST
q
INS_ST, INS8_ST, INS16_ST
INC_ST, INC8_ST, INC16_ST, INC_Orig_ST, INC8_Orig_ST, INC16_Orig_ST,
INCSel_ST
ACT_ST general
ACD_ST q
general
phsA
ACT_ST_Phs phsB
ACD_ST_Phs phsC
neut
q
actVal
BCR_ST frVal
q
valWTr.posVal
BSC_ST, BSC_Orig_ST
q
mag.f
MV_MX range
q
SCE/EN AP/C60 AP-19

Data Object Data leaves

phsA.cVal.mag.f
phsA.range
phsA.q
phsB.cVal.mag.f
phsB.range
phsB.q
WYE_MX
phsC.cVal.mag.f
phsC.range
phsC.q
neut.cVal.mag.f
neut.range
neut.q
phsAB.cVal.mag.f
phsAB.range
phsAB.q
phsBC.cVal.mag.f
DEL_MX phsBC.range
phsBC.q
phsCA.cVal.mag.f
phsCA.range
phsCA.q
mxVal.f
APC_MX, APC_Orig_MX
q
LSP stVal
AP-20 SCE/EN AP/C60

3.5 DRIVING THE IMPORT PROCESS THROUGH COMMAND LINES

The SCE is delivered with sample scripts and documentation that allow launching silent mode commands
such as OPEN, IMPORT, EXPORT, CHECK IN, CHECK OUT, GENERATE, AUTO-ADDRESSING,
AUTOLINK, SAVE, CLOSE, VALIDATE using an appropriate scripting manager environment.
Note:
For Installation of Groovy Environment, refer to chapter SCE/EN IN
The SCE Scripting Manager allows processing
 Alstom DS Agile data bases

 The Open a data base action
 The Open data base library action
 The importing an FCS file
 The importing an XML file
 The Check a data base action
 The Automatic addressing a data base action
 The Auto-link a data base action
 The CheckIn a data base action
 The Generate a versioned data base action
 The Close a data base action
 The Save a data base action
 The CheckOut a data base
Example: Open and generate a standard DS AGILE db

1 Run the batch file {DS AGILE_SCE_DIRECTORY}\ScriptsManager\launchGroovy.bat
2 Groovy Console appears as shown below:
SCE/EN AP/C60 AP-21

3 Open Groovy script from file menu of the Groovy console
4 Run the Script
AP-22 SCE/EN AP/C60

5 Groovy will execute the action as per script and it will generate new database.
Note:
1) If database which is in Read/Write MPC file DB with no errors nor warnings then Groovy return error as:
ERROR_SCE_SCRIPT_MNGR_SAVE_DATABASE_NOT_READONLY.
2) If database which is Read Only DB with errors but no warnings then Groovy return error as:
ERROR_SCE_SCRIPT_MNGR_GENERATE_CHECK_ON_ERROR
3) If database which is Read Only DB with errors but no `warnings without check then Groovy return error as:
ERROR_SCE_SCRIPT_MNGR GENERATE ERROR ON_EQUIPMENT
SCE/EN AP/C60 AP-23

4 FBD EDITOR
The Logical Equation Viewer is an application that allows the edition of one equation (FBD logic diagram).
It is launched from the menu item Workbenches/FBD Edit.
 either at the creation: only with the I/O slots declared as I/O parameters in DS Agile
 or at the modification: with the schema already entered and eventually a redefinition of the
inputs/outputs.
The Function Block Diagram language combines functions and function blocks interconnected by signal
flow lines in order to define function block diagram networks.
The Equation Viewer allows the programmer to build equations by taking existing blocks from libraries,
defining data flow between functions, …
The application can print a view on as many folios as required to cover the full content of this view.
Boundaries of printed folios are clearly indicated on the FBD view.
The application is also able to open on-line help following the chosen language.
In addition, text annotations may be used to document the logic.
AP-24 SCE/EN AP/C60

4.1 OVERVIEW
The views exposed by this application are several FBD Views of the same document.
Through these views it is possible to edit the equation logic.
 a Logging View that shows warnings and error messages when the equation is saved,
 an FBD Overview that shows the whole content of the FBD view,
 a Library Toolbar containing the whole set of FBD blocks of the library.
An FBD document gathers a lot of FBD networks needed to achieve functionality.

FBD documents are divided into pages. Page boundaries are set in order to have for instance almost 40
blocks on a page. Pages are the smallest entities that can be printed.
SCE/EN AP/C60 AP-25

4.2 FBD EDITOR VIEWS

It displays the part of the equation logic that is currently edited.
The Editor View acts as a peephole to the document that may be too large to allow display of all FBD logic at
once.
With the scrolling facilities, this peephole can be moved across the document to reveal different portions of
it. Acting on the Overview or on the Editor View horizontal and vertical scroll bars may do this.
With the zooming facilities, it is possible to modify the zoom level of the Editor View for an improved
readability. This may be achieved by acting on the Overview or on the Zoom dialog box.
4.2.1 FBD EDITOR VIEW

Close: Like any window: you click on the cross at the upper right coin of the window.
Scroll: Scroll bars are available (horizontal and vertical) to move the peephole through the FBD document;
this movement is visible in the Overview window by the corresponding movement of the blue rectangle. You
can also move the screen one page at a time by clicking left inside the scroll bar (see "Navigation Features").
Zoom: Resizing the Editor view leads to show a larger or lower part of the FBD Document. The size of the
displayed graphical components is not modified when resizing the Editor view.
On the other hand, the size of the displayed components is modified if you change the zoom ratio with the
Overview blue rectangle manipulation (see "Zoom Features").
AP-26 SCE/EN AP/C60

User Interactions
Edition: You can create a network by:
 dropping Blocks on the Editor view,

 linking these blocks with Signal Flow Lines, Connecting lines and Connections,
 defining input/output operands using slots and literals.
For more details about it, see § 4.4.5 Functions and Function Blocks.
Status Bar: The status bar may be toggled on and off at the bottom of the window by using the Status Bar
option in the View menu.
The status bar displays information about the activity associated to toolbar icons when the mouse cursor
stays on these icons (standard behaviour of toolbar).
4.2.2 THE FBD OVERVIEW

The Overview displays the whole content of the document.
On this Overview, a blue rectangle shows the current relative size and position of the active Editor View.
Resize & Move the Overview: you can move the overview like any window. On the other hand, resizing the
overview has automatically an action vertically and horizontally.
Drag the blue rectangle or click any location inside the Overview in order to change the Editor view
content: click left in the blue rectangle and, without releasing the mouse button, move the mouse to put the
rectangle to another location or click left any location in the Overview ; the blue rectangle comes at this place
and the Editor view is updated.
Resize the rectangle in order to change the Editor view zoom level: Select the bottom right corner of the
blue rectangle: a double arrow appears. Without releasing the mouse button, resize the blue rectangle. The
Editor view zoom ratio and content are updated.
Show the associated overview Choose the menu option Window and the item Overview.
4.2.3 TOOLBAR
The Toolbar may be toggled on and off at the top of the window by using the Tool Bar option in the View
menu. It may also be moved (standard behaviour of toolbar).
allows to save the current view.
allows to cut the selected element(s).
allows to copy the selected element(s).
allows to paste the element(s) held in the clipboard
allows to undo the last action.
allows to print the current view.
SCE/EN AP/C60 AP-27

allows to display the Overview.
clears the current mouse function.
4.2.4 LIBRARY TOOLBAR

The Library Toolbar may be toggled on and off at the top of the window by using the Library Toolbar option
in the View menu.
The Library toolbar contains all the buttons corresponding to the available function blocks. Two libraries are
available: one for FBD Automation, another for FDB Interlock (with only Boolean function blocks).
Figure 1 - FBD Automation library
Figure 2 - FBD Interlock library
Boolean operators: AND, OR, XOR, NOT

Bistable function blocks: RS
Timer function blocks: TON, TOF
4.2.5 LOGGING VIEW
The Logging View will be mainly used to log messages from the ST translation process.
Each time an FBD document is saved an equivalent structured text (XML file) form is created.
Translation warnings and errors are logged into the logging view.
MaxLines: You can set the maximum number of lines that can be displayed in the Logging View:
 Right-click in the background of the Logging View,

 Select the MaxLines item,
In the edit field that appears, enter the maximum number of lines to display,
AP-28 SCE/EN AP/C60

 Press OK to confirm.
CleanUp: You can clear the content of the Logging View:
 Right-click in the background of the Logging View,

 Select the CleanUp item.
File Save As: You can save the content of this window in a file. This file must be defined with a file chooser.
4.2.6 KEY FUNCTIONS

Keyboard shortcuts are available for many functions in the FBD Editor window.
These functions and the corresponding keystrokes are grouped below by type.
4.2.6.1 MOVING AROUND IN THE FBD EDITOR VIEW

KEYS FUNCTION
Move the view up by a smooth scroll
Move the view down by a smooth scroll
Move the view left by a smooth scroll
Move the view right by a smooth scroll
Ctrl Move the view up by a half page
Ctrl Move the view down by a half page
Ctrl Move the view left by a half page

Ctrl Move the view right by a half page
Page-Up Move the view up by an entire page
Page-Down Move the view down by an entire page
Home Move the view at the upper right corner of the document
End Move the view at the lower left corner of the document
4.2.6.2 USING FILE FUNCTIONS

CTRL + S: To save the current equation
CTRL + P: To print the current equation
4.2.6.3 GETTING HELP

F1: Access to Online Help for the active window (help about the Equation Viewer) or the selected functional
block (help about the selected block).
SCE/EN AP/C60 AP-29

4.3 UNDERSTANDING FBD

The Equation Viewer allows the programmer to build equations by taking existing blocks from libraries,
assigning their input/output parameters, defining data flow between functions…
In addition, text annotations may be used to document the logic.
4.3.1 GRAPHICAL COMPONENT ON THE EDITOR VIEW
4.3.1.1 GRAPHICAL COMPONENT SUMMARY

FBD Language Elements
Slots, Functions, Function Blocks, Connecting Lines, Signal Flow Lines, Horizontal/Vertical Connections,
Literal
Annotations
Text Annotations
4.3.1.2 PROPERTIES
(1) Slots describe input/output parameters of Functions or Function Blocks.

(2) A Function or Function Block is a FBD instruction which, when executed, yields one or more values.
(3) A Function, Function Block or Slot can have one or more Connecting lines.
(4) Signal flow lines represent the data flow between Blocks: head and tail of a SFL may either be put on a
Slot, a Function or Function Block CL or on a H/V C. Only one Signal Flow Line may be routed from one
connecting line.
(5) A Signal Flow Line may be derived in many locations of its path inserting Horizontal/Vertical
connections at these locations.
Inserting an H/V C in the SFL path break down this SFL into two new SFL connected to the H/V C. A H/V C
may not stay alone on the Editor view.
(6) Literal may be used to customize Function or Function Block inputs.
Note: For Alstom DS Agile V3, only duration literal is available.
(7) Network evaluation sequence index is automatically calculated.
AP-30 SCE/EN AP/C60

(8) Text annotations are useful to the equation.
Note: Graphical components can be put anywhere on the FBD Editor view. Graphical overlapping and page
boundaries crossing checks are made.
Edition is Language Sensitive and allows only the building of semantically meaningful FBD networks.
4.3.2 LANGUAGE ELEMENTS
4.3.2.1 FUNCTION (F)

Definition: A Function is defined as a FBD instruction which, when executed, yields exactly one data
element.
Functions are stateless (invocation of a Function with the same arguments shall always yield the same
output value).
Drawing: The illustration shows the features of a Function.
Name or abbreviation Network evaluation

of the Function 7 sequence indice
AND
In1 Q
Connecting Line In2
S0195ENa
More details
 about Function usages in "Functions and Function Blocks",

 about the Block pop-up menu in "Activity List of Blocks".
4.3.2.2 FUNCTION BLOCK (FB)

Definition: A Function Block is an FBD instruction which, when executed, yields one or more values.
Multiple copies, named instances, of a Function Block can be created.
All the values of the output parameters and of the internal variables shall persist from one execution of the
Function Block to the next; therefore, invocation of a Function Block with the same arguments needs not
always yield the same output values.
Output parameters shall be accessible outside an instance of a Function Block.
Drawing: The illustrations below show the features of a Function-Block
Name or abbreviation
of the Function Block Network evaluation
7 sequence indice
TON
IN Q
Connecting Line PT ET
S0196ENa
SCE/EN AP/C60 AP-31

More details
 in "Functions and Function Blocks",

 about Block pop-up menu: "Activity List of Blocks".
4.3.2.3 CONNECTING LINES (CL)
Connecting lines represent graphically the input and output signals of a Function or a Function Block.
Connecting lines are typed.
Examples: BOOL, TIME
More details
 about the CL usage in "Signal Flow Lines (SFL)" and in "Working with Literals",
 about the CL pop-up menu: "Activity List of Connecting Lines".
4.3.2.4 SIGNAL FLOW LINES (SFL)
Signal flow lines represent the data flow between Blocks: head and tail of an SFL may either be put on a
Slot, a Function or Function Block CL or on a H/V C.
An SFL is created by left clicking on a CL or a H/V C without releasing the mouse button, moving the mouse
up to reach another CL or H/V C.
Routing is made automatically.
The SFL route can be adjusted translating SFL segments.
A signal flow line must be connected on its two ends to a Function, Function Block CL or a H/V C.
Head and tail must be connected to CL having the same type and the same variable symbol name. If not, the
connection fails.
More details
 about the SFL usage in the chapter "Signal Flow Lines (SFL)"
 about the SFL pop-up menu: "Activity List of Signal Flow Lines"
AP-32 SCE/EN AP/C60

4.3.2.5 HORIZONTAL/VERTICAL CONNECTIONS (H/V C)
Horizontal/Vertical Connections represent signal connections between Signal Flow Lines.

H/V connections allow quick understanding of line crossing with or without connections.
A new H/V connection is added by breaking down a horizontal or vertical signal flow line into two segments
and allows the connection of a respectively vertical or horizontal new one. It can also be added at an SFL
bend.
More details
 about the H/V C usage in "

 FBD Network",
 about the H/V C pop-up menu: "Activity List of H/V Connections".
4.3.2.6 SLOTS
Slots describe the equation input/output parameters defined by Alstom DS Agile. Therefore, new Slots can
not be created.
More details
 about the Slots usage in "Slots",

 about the Slots pop-up menu: "Activity List of Slots".
SCE/EN AP/C60 AP-33

4.3.3 TEXT ANNOTATIONS
Text annotations (TA) are used in FBD documents. A Text Annotation is a comment that you can write in
the background of the FBD document.
Text annotations may be left anywhere on the edition view sheet except on page boundaries.
For manipulations, see "Working with Text Annotations".
TA pop-up menu is described in "Activity List of Text Annotations".
4.3.4 EVALUATION STRATEGY

In an FBD document, each Function Block is marked with an execution order number. FBD editor gives
itself all the sequence indexes to all the F and FB.
This number is called "Network evaluation sequence index" and is automatically calculated (see
description of "Function (F").
This automatic calculation is founded upon the IEC standard. The most important rule of the IEC standard
is the obligation to evaluate at once, all the FB linked with the input Connecting Lines of the current FB to
evaluate.
4.4 EQUATION VIEWER
4.4.1 FBD DOCUMENT

An FBD Document gathers a lot of FBD networks needed to achieve equations.
The whole document is visible in the Overview.
The document is divided into pages that are delimited by dashed lines (page boundaries) in the Overview
and in the Editor view.
Page ranges on X and Y are from 1 to 4 allowing a maximum matrix of 12 pages (3*4/2*6).
AP-34 SCE/EN AP/C60

The document control panel allows resizing the FBD document matrix by specifying the number of pages.
Note: It is impossible to reduce a document size if it involves the removing of non-empty pages: it is necessary to
delete or move these FBD networks before.
4.4.2 NAVIGATION FEATURES

There are different ways to change the Editor view content, from the Editor view itself or from the Overview:
To shift the view with a smooth scroll:
 Use the arrow keys:

 Use the mouse: left-clicking on the vertical/horizontal scroll bars arrows
To shift the view by half-page:
 Use the arrow keys:

 Use the mouse: click the free part of the scroll bar
To shift the view by an entire page:
 Use the keys: buttons PgUp and PgDn

 Use the mouse: click the blue rectangle and move it up to the next page
To shift the view in the middle of the document
 Use the keys: button 5 of the keypad in Num Lock position

 Use the mouse: click the blue rectangle and move it up to the middle
SCE/EN AP/C60 AP-35

To shift the view at the beginning and at the end of the document
 Use keys:
Home: the blue rectangle goes to the top left corner of the document overview.
End: the blue rectangle goes to the bottom right corner of the document overview.
 Use the mouse: click the blue rectangle and move it up to the top left corner or the bottom right corner
of the document
In all cases with the mouse you can:
 shift the view anywhere by left clicking on the blue rectangle and move it where you want in the
document, keeping the left click on
 click anywhere in the document Overview window and the blue rectangle comes where you have
clicked
4.4.3 ZOOM FEATURES

It is possible to adjust the Zoom level of the Editor view in order to have the best compromise between the
amount of information displayed and their readability.
Edition is possible for any Zoom ratio.
For example: working with a high Zoom ratio is useful for structural operation (subnetwork duplication, ...)
AP-36 SCE/EN AP/C60

The Zoom unit is a page.

The Zoom minimum value is 1/120th of a page.
The Zoom maximum value is the page number fixed by the user (see "FBD document").
The current Zoom value is displayed in the edit field.
There are different means to modify the Zoom ratio:
The arrows and double arrows are used to modify Zoom more precisely.
< and > modify the Zoom ratio of a tenth (1/10) of a page.
<< and >> modify the Zoom ratio of a half page.
|< and >| set the minimum and maximum Zoom ratio.
"Edition quality" sets the Zoom ratio to have the best readability of Blocks and comments on the chosen
view. The Default button has the same behaviour.
The "one" button sets the Zoom ratio to "one page per view".
If you have chosen to work with the Zoom ratio set for a maximized window:
You have to select the option "for a maximized window" like in the example above.
In this case you can also modify the Zoom ratio by moving the blue rectangle in the Overview.
If you modify the Editor window size, the Zoom ratio stays the same and more or less FBD logic is visible.
If you have chosen to work with whatever size of window:
You have to select "whatever size of the window".
In this case, it is not possible to modify the Zoom ratio by the overview.
If you modify the Editor view size, the same content will be displayed with another Zoom ratio.
4.4.4 SELECTION MODEL
4.4.4.1 SELECTION OF A GRAPHICAL COMPONENT

All graphical components may be individually selected by a left-click or by a right click. In the second case, a
pop-up activity list is also displayed.
a In response to this explicit selection, a selection feedback is provided.
Slot: the border becomes blue.
SCE/EN AP/C60 AP-37

F & FB: the border colours are reversed.
SFL, CL & H/V C: a gray border is displayed around the graphical component.
TA: the text is displayed in embedded form.
b To cancel the selection

Any left click on the background cancels previous selection.
Any left click on another graphical component selects this one cancelling the previous selection.
Ctrl key + left click.
AP-38 SCE/EN AP/C60

c Actions on the selected component

Depending on the selected component, some actions are or are not allowed.
Example: Cut or Copy are not allowed on a SFL.
Depending on the selected component and the action, some non-explicitly selected graphical
components may be affected and no feedback is provided for them.
Effects of this type of selection is indicated in another way.
Example: CL are moved and SFL are re-routed when moving a selected function block.
WYSIWYG (What You See Is What You Get) effect is provided during Move/Copy operations: dashed
graphical components represent the operation result at the drop time.
More Details
See "Block manipulation" or "Move/Copy-Paste/Cut-Paste operation for Network region".
4.4.4.2 SELECTION OF A SUBNETWORK

A subnetwork is a set of graphical components that have a functional meaning.
d To select a subnetwork
A subnetwork can be selected drawing a focus rectangle around it:
you left-click anywhere in the document and with the mouse button maintained on, you fully surround all
the components you want in the subnetwork (the focus rectangle is composed of dashed lines).
For each graphical component fully included inside the focus rectangle, a selection feedback is provided
as described in "Selection of a graphical component".
e To aggregate several objects
Click the first object and for the others, click holding down the Ctrl key. All these not contiguous objects
create a set that can be copied, cut or deleted as the subnetwork described below.
f To aggregate several subnetworks
You can also add a new subnetwork to the previous selection set by drawing a focus rectangle (as above)
around this new subnetwork while pressing the Ctrl key.
g To cancel the selection:
Any left click on the background cancels the previous selection.
SCE/EN AP/C60 AP-39

Any left click on another graphical component selects this one cancelling the previous selection.
Ctrl key + left click.
Ctrl key + a focus rectangle to cancel a part of the selection.
h Actions on the selected subnetwork
See "FBD Network".
WYSIWYG effect is available as described in "Selection of a graphical component".
4.4.5 FUNCTIONS AND FUNCTION BLOCKS
4.4.5.1 HOW TO GET A BLOCK

To add an FBD Block, choose the block by left clicking on the corresponding button in the FBD toolbar and
place it in the document by left clicking in the FBD View where it must be placed.
After the selection of the block, the cursor (usually an arrow) is replaced by a cursor representing the block.
When the block is added to the document, it can be moved or duplicated by drag & drop.
4.4.5.2 BLOCK MANIPULATION

Right-click a Block to select it and also display a pop-up activity list whose items are explained below; then it
becomes possible to do some manipulations with the selected Instruction.
To move a Block, select the chosen block and move the mouse holding down the left button (drag and drop).
The borders are then drawn in dashed lines as the linked SFL which stay attached and are automatically
rerouted.
AP-40 SCE/EN AP/C60

The drawing stays with dashed lines until you drop the left-click. The instruction is then re-drawn in its new
location.
Cut and paste operations:
Select the chosen block.
Press Ctrl+X
or
Select the "Cut" item in the Edit menu
or
Select the "Cut" item in the pop-up menu (right click)
Click any location of the Editor view.
Press Ctrl+V
or
Select the "Paste" item in the Edit menu
or
Select the "Paste" item in the Editor view pop-up menu (right click).
Note: By cut and paste, both source and target networks are modified; the Instruction loses its connected SFL lines.
To duplicate a Block
* Drag and drop operation
Select the chosen block by a left-click.
Move the mouse holding down the left button and the Ctrl key.
The new F or FB is copied without its connected SFL lines and is drawn in dashed lines (as above).
The drawing stays with dashed lines until you drop the left-click. The new block is then drawn in the current
place.
SCE/EN AP/C60 AP-41

or
* Copy and paste operations
Select the chosen F or FB
Press Ctrl+C or
Select the "Copy" item in the Edit menu or
Select the "Copy" item in the pop-up menu (right click)
Click anywhere in the Editor view.
Press Ctrl+V or
Select the "Paste" item in the Edit menu or
Select the "Paste" item in the Editor view pop-up menu (right-click)
(copy is also made without SFL lines).
Note: If you drop/copy on a wrong area, the element remains displayed dashed red. It is now possible to initiate a
new drag&drop/copy operation in order to move the element in a right area.
To delete an F or FB, select the chosen Instruction and one of these options:
 Press the "Delete" key: the Instruction is definitely deleted

 Press Ctrl+X: "Cut" operation without following "Paste"
 Select the wanted operation in the Edit menu: "Cut" or "Delete"
 Select the "Delete" item in the pop-up menu (right click)
4.4.5.3 EXTENSIBILITY
Extensibility is supported on some Boolean operators. This means that you can extend the number of inputs
CL of a block by duplicating the last one.
 Select the input CL you want to duplicate.

 Select the Duplicate item in the pop-up menu of the CL.
The new input CL is created, with the same attributes as the duplicated one.
 If the need arises, delete a duplicated input CL by using the Delete CL item in the CL pop-up menu
AP-42 SCE/EN AP/C60

4.4.5.4 NEGATION
It is possible to negate an input or output Boolean CL, by using the Toggle Negation item in the pop-up
menu of the CL.
This item will obviously toggle the negation on and off.
4.4.5.5 HOW TO GET HELP ABOUT A BLOCK

The on-line help may be launched (F1 key) from any FBD block of the FBD View.
4.4.6 SIGNAL FLOW LINES (SFL)
4.4.6.1 SFL HANDLING

To draw an SFL from an F or FB to another one:
 Left click on the chosen CL of the original F or FB: it initiates a new “Signal Flow Lines (SFL)” routing;
the feedback is the CL becomes white.
 Move the cursor until the CL of the ending F or FB (holding down the left button); the SFL is drawing in
dashed line(s).
 release the left click when the cursor is on the destination CL; the SFL is now drawn in continuous
lines and in selected mode.
Note: Head and Tail must be connected to CL having the same type. In this case the feedback is a white dashed
SFL.
If not, an error is displayed by a red dashed line feedback and a "not entry" sign.
SCE/EN AP/C60 AP-43

Information about "Literal manipulation (Paste/Delete/Cut/Copy".

Each time an SFL routing is necessary, it is made automatically but roughly.
It is efficient enough for the most frequently operations made on networks.
Meanwhile, the SFL route can be adjusted by translating segments:
 select the SFL segment left by clicking it

 keep the left click and move the mouse until having the right routing.
The SFL is drawn in dashed lines during the operation
 release the left click to have the final route; the SFL is drawn in continuous lines.
To definitely delete an SFL:
 select the chosen SFL and then:

 press the "Delete" key or
 select the item "Delete SFL" of the pop-up activity list (right click) or
 select the "Delete" operation in the Edit menu
To change the SFL drawing thickness, right click and select "Toggle thickness" in the SFL pop-up activity
list.
The result is shown below:
4.4.6.2 SFL DERIVATION: H/V C

A H/V C connection breaks down an horizontal or vertical Signal Flow Line into two segments and allows
connection of respectively vertical or horizontal new one. It allows quick understanding of line crossing with
or without connections.
AP-44 SCE/EN AP/C60

To insert a Horizontal/Vertical Connection in a SFL, you have to do the following actions:
 select the SFL where you want insert a H/V C

 right-click with the mouse and a pop-up activity list is displayed
 select the item "Insert H/V C" and the H/V C symbol is displayed at the cursor location on the SFL
drawing
To delete a Horizontal/Vertical Connection, you have to do the following actions:
 select the H/V C

 right-click with the mouse and a pop-up activity list is displayed
 select the item
"Delete H/V C & SFL": the selected H/V C and all the SFL linked to are deleted
"Delete H/V C, SFL & symbol": the selected H/V C, all the SFL connected to and the corresponding
symbol are deleted
4.4.7 SLOTS
Slots are graphical FBD elements representing input/output list.
That list is written in the XML input file by the DS Agile Environment before the calling of the Equation Viewer
application. Slots are represented as shown:
SCE/EN AP/C60 AP-45

Each slot has a Connecting Line that is a link between:
 an input slot and the input of a block or function block (SFL)

 an output of a block or function block and an output slot (SFL)
The orientation of the Slots can be toggled thanks to the Left and Right items of their pop-up menu.
4.4.8 FBD NETWORK
4.4.8.1 MOVE/COPY-PASTE/CUT-PASTE OPERATION FOR NETWORK REGION

The general mechanism is quite the same using clipboard or drag and drop facilities:
Select a network region on the Editor view (see "Selection of a subnetwork").
Initiate a Cut-Paste/Copy-Paste or drag and drop operation.
Terminate this operation either by cancelling it or by entering it (you can stop the operation by pushing on the
Esc key or by dropping in a "no entry" area).
To move a network region
* Drag and drop operation
 Select the network.

 Click one of selected objects.
 Move the mouse holding down the left button.
AP-46 SCE/EN AP/C60

The borders are then drawn in dashed lines as the linked SFL which stay attached and are automatically
rerouted.
The drawing stays with dashed lines until you drop .The subnetwork is then re-drawn in its new location.
OR
* Cut and paste operations
 Select the subnetwork.

 Press Ctrl+X or select the "Cut" item in the Edit menu
 Move the cursor where you want in the Editor window and left-click on.
 Press Ctrl+V or select the "Paste" item in the Edit menu
Note: Connexion (SFL) between the cut subnetwork and the remaining network are lost.
To duplicate a subnetwork
* Drag and drop operations
Select the subnetwork and Move the mouse holding down the Ctrl key.
The new subnetwork loses all its connected SFL lines with the remaining network.
It is drawn in dashed lines (as below). The draw stays with dashed lines until you drop (WYSIWYG effect).
The new instruction is then drawn in continuous lines at the current place.
During the copy operation, the subnetwork is displayed red as long as it is in a wrong area.
OR
SCE/EN AP/C60 AP-47

* Copy and paste operations

Select the subnetwork.
Press Ctrl+C or select the "Copy" item in the Edit menu.
Move the cursor where you want in the Editor window and left-click on.
Press Ctrl+V or select the "Paste" item in the Edit menu
(SFL lines are lost).
Note: If you drop/copy on a wrong area, the subnetwork remains displayed dashed red.
It is now possible to initiate a new drag&drop/copy operation in order to move the subnetwork in a right area.
To delete a subnetwork, select the subnetwork and one of these options:
 Press the "Delete" key: subnetwork is definitely deleted

 Press Ctrl+X: "Cut" operation
 Select the wanted operation in the Edit menu: "Cut" or "Delete"
4.4.8.2 WORKING WITH SEVERAL EDITOR VIEWS
When you are working in a document, you can probably have to move or copy a Block or a subnetwork from
a document area to another or to draw a SFL from a Block to another.
If the two areas or blocks are not visible in the same view, you have two options:
6 Drag-scroll through the document with the drawback of not seeing the beginning AND the end of your
operation at the same time.
7 Open another view of the same document:
In the main toolbar, select the "New Window" item of the "Window" menu.
A second window of the same document is opened and is independent of the first one.
You can choose different Zoom ratios, focus on different document areas, ...
DOCUMENT
VIEW 1
VIEW 2
S0365ENa
Now, it is possible to drag and drop, SFL drawing, ... from one view to the other but in the same document
and seeing the two views at the same time.
AP-48 SCE/EN AP/C60

DOCUMENT 1 DOCUMENT 2
VIEW 1 VIEW 2 S0371ENa
Note: The sequence index is automatically modified, adapted to the new network. SFL connections are not allowed
between different documents.
4.4.9 FBD GRAPHICAL CONTROLS

You cannot put FBD graphical elements anywhere in the Editor window:
 either on or quite near a Block or a Text Annotation,

 or on the page boundaries.
In these cases, FBD returns a feedback to show the problem:
RED dashed lines to indicate what draw part is in a forbidden zone, with a "no entry" sign.
YELLOW dashed lines to indicate the objects which becomes unacceptable because of the attached wrong
(RED) object.
SCE/EN AP/C60 AP-49

Example 1: MOVE operation
During the Move operation, these colours (red and yellow) are displayed as long as the moved object is in a
wrong area. If you drop in a wrong situation, the drawing is like before the move operation and the colour
dashed lines are removed.
Example 2: Copy/Paste between two Editor windows
During the Copy operation, the graphical element is displayed red as long as it is in a wrong area. If you drop
it on this wrong area, the element remains displayed dashed red. It is now possible to initiate a new drag &
drop operation in order to move it on a right area.
AP-50 SCE/EN AP/C60

4.4.10 FBD SEMANTICAL CONTROLS
4.4.10.1 PROTOTYPICAL FBD NETWORK NOTION

In the description of a Function or a Function Block, each connecting line has definite characteristics which
fix the data types choice possibilities for each of them.
The Equation Viewer controls that the edited variable meets the CL criteria.
Connecting Lines prototypes are characterized by Data type. A CL can accept variables of one or several
data types (ex: Bool, Time, ...). Supported data types depend on target types.
Two CLs of two F or FB which has to be linked by an SFL must have compatible data types; if not, the
Equation Viewer doesn't allow the SFL drawing as explained in "Prototypical Controls".
4.4.10.2 PROTOTYPICAL CONTROLS

The Equation Viewer controls that two linked CLs have compatible characteristics.
Example with no compatible data type: Error feedback
4.4.11 WORKING WITH LITERALS

The Equation Viewer allows the creation of boolean and duration literals.
When assigning a literal, users will be prompted to enter its value:
Duration:
duration::= (T| t )#[-]) interval
interval::= days| hours | minutes | seconds | milliseconds
fixed_point::= integer[.integer]
days:: = Fixed_Point ( d |D)
hours:: = Fixed_Point ( h | H)
minutes:: = Fixed_Point ( m | M)
seconds::= Fixed_Point (s | S)
milliseconds::= Fixed_Point (ms | MS)
Example: T#100ms, t#10H30m15s
When the user assigns a literal to a function or function block input parameter, checks are made in order to
evaluate if the data type complies with this one expected on this parameter.
If not, the assignment fails.
4.4.11.1 ASSOCIATE SYMBOL

Double click the left mouse button on the CL or you click the right mouse button and select the Associate
symbol item in the activity list of a SFL, a CL or a H/V C.
An edit field is then opened where you can type the literal you wish to associate to the CL. Near the name of
the CL, in square brackets, is the data type which can be associated.
SCE/EN AP/C60 AP-51

As you enter a literal which does not match the duration type constraint, the following error message pops
up:
As the right literal is in the field, press the Enter key. The literal is then associated to the CL and an edit field
is automatically shifted to the next CL to define (if there is one…).
4.4.11.2 LITERAL MANIPULATION (PASTE/DELETE/CUT/COPY)

To move a literal
Drag and drop operations:
Initially, the literals are put around the F or the FB, but they may be moved anywhere on the sheet according
graphical and semantic control:
 Select the literal by clicking the left mouse button.

 move the literal by maintaining the left mouse button clicked on, up to another place (drag and drop
operation).
Cut and paste operations:
 Select the chosen literal.

 Press Ctrl+X,
or Select the Cut item in the Main Edit menu,
or Select the Cut symbol item in the literal pop-up activity list (click the right mouse button on the
literal.
 Move the cursor to another CL, SFL or H/V C in the Editor window and click the left mouse button on
it.
 Press Ctrl+V,
or Select the Paste item in the Edit menu,
or Select the Paste symbol item in the CL or SFL or H/V C pop-up activity list.
Arrange symbol is an operation of the pop-up activity list obtained by clicking the right mouse button on an
F or an FB.
The result is a display in normal form and near the current F or FB, at the initial position of the symbol.
To duplicate a literal
Drag and drop operations:
AP-52 SCE/EN AP/C60


 Move the mouse with the left mouse button clicked on while pressing the Ctrl key.
The drawing stays within dashed lines until you drop. The new literal is then drawn in the current place.
Copy and paste operations:

 Press Ctrl+C, or Select the Copy item in the Edit menu,
or Select the Copy symbol item in the literal pop-up activity list (click the RH mouse button on literal).
 Move the cursor to another CL, SFL or H/V C in the Editor window and click the left mouse button on
it.
 Press Ctrl+V, or Select the Paste item in the Edit menu,

or Select the Paste symbol item in the CL or SFL or H/V C pop-up activity list.
To remove a literal assignment, select the chosen literal; then select one option:
 to press the Delete key: the literal is definitely deleted,

 to press Ctrl+X (cut operation),
 to select the desired operation in the Edit menu: Cut or Delete,
 to select the Delete symbol item in the literal, CL or H/V C pop-up activity list.
4.4.11.3 LITERAL CONTROLS

If you try to move or copy a literal on a CL which has not the same type
Or If you try to move or copy a literal:
 on or quite near an F or FB,

 on or quite near an annotation (TA),
 on the window boundaries,
 between two equation logics,
the Equation Viewer gives you a feedback as below: the literal is displayed in red dashed line with the "no
entry" sign and when you release the left mouse button, the literal stays at its initial position.
4.4.12 WORKING WITH TEXT ANNOTATIONS
4.4.12.1 CREATION OF TA
Right click on the Editor view background; this displays an activity list.
Select the option "Insert Text Annotation"; an Edit field is displayed at the left-top of the active view, enter
your text there.
Move by drag & drop the entered text at the location you want in the active view or in another view.
SCE/EN AP/C60 AP-53

4.4.12.2 MANIPULATIONS OF TEXT ANNOTATION

These manipulations are the same as those described in "Literal manipulation (Paste/Delete/Cut/Copy)" and
as the use of the Paste option in the Activity List of the Editor View.
To modify a TA, double-click the TA; an Edit field appears which is initialized by the current TA. It is so
possible to modify it.
4.4.13 PRINTING FBD DOCUMENTS

Print, Print Preview and Print Setup features will be provided in order to allow printing of documents.
When printing a document, a Print Mode dialog prompts user to choose one of the following topics:
Print Overview
To print the whole document into one sheet of paper
Print Partial Overviews
To print as many sheet as there are matrix of 4x4 pages into the equation logic
Print Pages
To print as many sheet as there are pages in the document
AP-54 SCE/EN AP/C60

4.4.14 POPUP ACTIVITY LISTS
4.4.14.1 ACTIVITY LIST OF THE EDITOR VIEW
Paste: Displays in the Editor View what has been stored by a Cut or a Copy instruction
Undo: Cancels the last operation
Insert Test Annotation: "Working with Text Annotations".
4.4.14.2 ACTIVITY LIST OF BLOCKS
Arrange symbol: "Literal manipulation (Paste/Delete/Cut/Copy"

Cut/Copy/Delete: "Literal manipulation (Paste/Delete/Cut/Copy"
4.4.14.3 ACTIVITY LIST OF SLOTS
Left/Right: "Slots".
4.4.14.4 ACTIVITY LIST OF CONNECTING LINES
Associate symbol: "Working with Literals"

Paste symbol/Delete symbol: "Literal manipulation (Paste/Delete/Cut/Copy"
Arrange symbol: "Literal manipulation (Paste/Delete/Cut/Copy"
SCE/EN AP/C60 AP-55

Delete SFL/Delete SFL & symbol: "SFL "

Delete CL: "Extensibility"
Duplicate: "Extensibility"
Toggle negation: "Negation"
4.4.14.5 ACTIVITY LIST OF SIGNAL FLOW LINES
Insert H/V C: "

SFL derivation: H/V C"
Toggle thickness: "SFL "
Delete SFL: "SFL "
4.4.14.6 ACTIVITY LIST OF H/V CONNECTIONS
Delete H/V C & SFL: "

SFL derivation: H/V C"
4.4.14.7 ACTIVITY LIST OF TEXT ANNOTATIONS
Cut/Copy/Delete: "Manipulations of Text Annotation"
4.4.14.8 ACTIVITY LIST OF THE LOGGING VIEW
MaxLines: "Logging View"

Cleanup: "Logging View"
File Save As: "Logging View"
AP-56 SCE/EN AP/C60

4.5 DEFINING AN FBD FAST AUTOMATION

To define an FBD fast automation, the three following steps must be done:
 FBD interface definition at SCE level:

 FBD function ‘header’ creation
 creation of input plugs, that will be linked to SPS, DPS, MV, MPS, SPC or DPC (fast automations
take into account the logical value of these datapoints, defined for interlocking management),
added as sub-objects to this header.
 creation of output plugs, that will be linked to SPC, DPC (control of relays) or to a SPS (production
of SPS real-time value), added as sub-objects to this header.
 FBD body (coding in PSL) definition via launching at SCE level the FBD editor (contextual menu on
the FBD interface object) and doing diagram edition of boolean, timer and bistable functions, and links
to input/output plugs.
 Effective linking of input and output plugs to existing datapoints
4.5.1 CREATING AN FBD FAST AUTOMATION (HEADER DEFINITION)

The addition of an FBD fast automation is done via the “Objects entry” window at any level of the electrical
topology (except Site) by clicking on mouse’s right button.
For more details about the creation of an electrical topology, refer to the Application guide for the C26x
computer.
Figure 3: Adding an FBD Fast Automation (e.g. for Feeder bay level)
Once added, the FBD fast automation features must be set:

(1) Edit the relation ‘runs on’, to set computer PLC manages the automation. This relation is automatically
established by SCE if FBD automation is located under a bay whose manager has ever been entered
(inheritance mechanism).
(2) Type the short name and long name of the fast automation used for internal SCE identification.
SCE/EN AP/C60 AP-57

Figure 4: Setting FBD Fast Automation features
4.5.2 CREATING FBD INPUT PLUG (HEADER DEFINITION)

The addition of an FBD input plug is done via the “Objects entry” window at the FBD automation level by
clicking on mouse’s right button.
Figure 5: Adding a FBD input plug
Once added, FBD input plug features must be set at SCE level:
(3) short name and long name of the fast automation used for identification in FDB editor
AP-58 SCE/EN AP/C60

Figure 6: Setting general FBD input attributes
4.5.3 CREATING FBD OUTPUT PLUG (HEADER DEFINITION)

The addition of a FBD output plug is done via the “Objects entry” window at the FBD automation level by
clicking on mouse’s right button.
Figure 7: Adding an FBD output plug
Once added, FBD output plug features must be set:

(4) short name and long name: used for identification in FDB editor
Figure 8: Setting an FBD output plug attributes
4.5.4 USING FBD EDITOR (BODY DEFINITION)

The launching of the FBD editor is done at FBD automation level via its contextual menu (right click).
SCE/EN AP/C60 AP-59

Figure 9: Launching the FBD Editor
Once launched, FBD editor allows diagram edition of the automation. For details about FBD, refer to the
chapter SCE/EN AP.
FBD Boolean is Boolean type (True / false) input.

FBD Input is an input to FBD (Type – SPS, DPS etc.)
And Gate
TON Ton delay timer
FBD Output is output of FBD ( type SPS, SPC etc)
Figure 10: Using the FBD Editor
AP-60 SCE/EN AP/C60

4.5.5 LINKING DATAPOINTS TO FBD INPUTS AND OUTPUTS

To assign a datapoint to an FBD input:
 Add the relation ‘uses <XXX>’ (1) at FBD input level, where XXX corresponds to the datapoint type
(SPS, DPS, MPS, MV, SPC or DPC)
 Fill the relation with the relevant datapoint
(1)
Figure 11: Linking a FBD Input to a Datapoint
To assign a datapoint to an FBD output:
 Add the relation ‘controls <XXX>’ (1) or ‘produces SPS’ at FBD input level, where XXX corresponds to
the control datapoint type (SPC or DPC)
 Fill the relation with the relevant datapoint
(1)
Figure 12: Linking an FBD Output to a Datapoint
Several datapoints can be assigned to the same FBD output.
SCE/EN AP/C60 AP-61

Configuration rules and checks
 For one "FBD input" plug, only one relation is allowed.

 For one "FBD output" plug:
- the count of relations towards DPC or SPC datapoints must be  4
- the count of relations towards SPS datapoints must be  4
 A "DPC" or "SPC" datapoint can be linked to an Output plug of a FBD Automation through the relation
"controls DPC" or "controls SPC". These relations are not compatible with the following ones:
- relations defining the Control Source, except the "…wired on" relation(s)
- relation "has for IEC address" whatever the link type
- relation "has for SCADA address".
- relation "is controlled on state change of".
- relation "has for AutoManu dependency".
- relation "has for feedback".
- relation "has for local/remote dependency".
 A "DPC" or "SPC" datapoint can be linked to an Input plug of an FBD Automation through the relation
"uses DPC" or "uses SPC". These relations are not compatible with the following ones:
 relations defining the Control Source : "…wired on"
 relation defining the Control Source : "has for IED address"
AP-62 SCE/EN AP/C60

5 COUPLING SCE DATA MODEL AND ISAGRAF
5.1 ISAGRAF PRESENTATION

Installed versions:
Target
C26x Gateway
Application
RT exe 5.21 5.22
Workbench integrated into the SCE 5.22 5.22
5.1.1 ISAGRAF WORKBENCH DESCRIPTION

 The workbench is used to design and develop distributed process control applications. These
applications are organised in projects
 A project gathers the whole of all program elements and is composed of configurations
 A configuration is a hardware platform which supports kernels that execute resources. In our version
there is only one resource
 A resource is composed of several units of program (POU). In the current version there is exactly one
resource per configuration
 The POUs (Program Organisation Unit) can be programs, functions or functional blocs. They are
described using the IEC1131-3 compliant textual or graphic languages. They are organised on a
hierarchical basis architecture
 The kernel or virtual machine is the real time software that runs the resource code
 A target (C26x or Gateway) is attached to a configuration. It must be installed on a platform that
supports a multi-task operating system such as XPe or VxWorks
 A user function is a function called in automatic control programs (right-click on Insert/Set block) and
executed on the target
 The dictionary includes all the variables (input, output or internal), all the function parameters
definitions, all the types (simple or user defined) and all the defined words (constants definition)
 The languages can be either graphic or textual. They are used to describe the Program organisation
units (POU). They are compliant with the IEC1131-3 standard.
 SFC: Sequential Function Chart (grafcet)
 FBD: Function Block Diagram (functional diagram)
 LD: Ladder Diagram (Boolean logic based language)
 ST: Structured Text
 IL: Instruction List
There is another graphic language in the workbench: FC (Flow Chart) in addition to those in the standard.
The automation functions can be designed using any of the graphic or textual languages available in
ISaGRAF. Depending on the problem that the automation has to solve, one language can be better adapted
than another. All languages except the SFC can be instantiated, i.e. they can be used to create a functional
block.
SCE/EN AP/C60 AP-63

Hardware
platform
PROJECT
CONFIGURATION TARGET
RESOURCE KERNEL
Exchange PRJLIBR ARY .MDB file *.STF files

diagrams
Dictionary POU
Graphical
Dictionary Language Editors
The workbench contains an exchanges diagram (display of the resources and their possible links), a view of
material architecture (presentation of the configurations with their resources), the data dictionary and the
graphic editors which allow to visualise the POUs (SFC editor, FC editor and multi-language editor for FBD,
LD, ST and IT languages).
5.1.2 DIRECTORIES STRUCTURE OF ISAGRAF

When the workshop is installed, the following directories tree structure is created:
<root directory>
Bin Executables
Grp Windows Groups
Help
Prj Projects
<project name> single project directory
config1 1 directory  1 config.
resource1 1 directory  1 resource
Simul
Tmp
Tpl projects models
<project name> model name
<configuration>
<resource>
A project is composed of:
 the MS Access database file in the root directory of the project

 the source files of the POU of the resource in the repertory /config1/ressource1
All the data dictionary is saved in the MS Access database file.
The POU files have the STF extension.
When a POU is added into a resource, an STF file is created in the resource folder. It contains the graphic
description (elements coordinates in the editor) as well as the algorithms.
Prj
PROJECT NAME
PRJLIBRARY.MDB
Config1
Ressource1
POU1.STF
POU2.STF
ISAGRAF PROJECT STRUCTURE
AP-64 SCE/EN AP/C60

The compilation of a project produces several files such *.XTC embedding the TIC code. The TIC code is the
“interpretable code” of the automation.
5.1.3 UPLOADED FILES TOWARDS THE TARGET

During upload, the workbench transfers several files to hardware platforms.
The files that are transferred are the following ones:
 Resource (for each resource of that platform):

 A resource configuration file is downloaded.
Name of that file on workbench = RESOURCENAME_Conf.xtc.
Name of that file (or memory module) on hardware platform = ISPxxx03 (with xxx being resource
number in hexadecimal).
 A file containing resource symbols (variable names and so on) will be downloaded if ‘embed
symbol table’ option has been checked in resource properties).
Name of that file on workbench = RESOURCENAME_SymbolsTarget.xtc (this table is complete or
reduced according to resource properties option at last compiling).
Name of that file on target = IDSxxx01
 Pou (for each POU of a resource):

 All POU TIC code files on workbench (file name = ResourceName_POUName_xtc) will be
concatenated into a single file.
 Order for the concatenation is the one given by workbench file ResourceName_DWLOrder.xtc.
 On hardware platform side, the name of that file will be ISPxxx01.
 Hardware platform:
 The hardware configuration file is downloaded.
 On workbench, file is stored in the project configuration directory, (not in a resource directory).
 The workbench file name is: ConfigName_NetworkConf.xtc.
 On hardware platform side, the name of that file is ISPffe0d.
Note This document does not say which files are transferred in on-line modification case (ISPxxx15).
Thus, the files must be modified before download to the target:
 RESOURCE1_Conf.xtc must be renamed as ISP00103

 RESOURCE1_SymbolsTarget.xtc must be renamed as IDS00101
 Config1_NetworkConf.xtc must be renamed as ISPffe0d
All POU TIC files will be concatenated in file ISP00101 in the order described the DwlOrder.txt file.
5.2 USAGE OF SCE DATAPOINTS IN ISAGRAF

The DataPoints (DP) are defined inside the SCE. They are used by the automation as I/Os. An automation
can interact with the system only via these DataPoints.
Any DP used in the code of an automation must be defined beforehand in the SCE.
There are three different types of relation between an automation and DataPoints:
SCE/EN AP/C60 AP-65

 The function owns the DataPoint (hierarchical relation)

 The function is server of the Data Point (server relation)
 The function is client of the Data Point (client relation)
For the interface definition, refer to the chapter C26x/EN AP or GTW/EN AP.
5.2.1 HIERARCHICAL RELATION: FUNCTION MANAGEMENT DPS

In the electrical tree structure these DPs are defined under the function. The function is the owner of the DP.
Examples:
 ON/OFF command of the automation

 functions parameters
 current values and current state of the automation
The function has the following rights on the real time attributes of the DP:
 status (SPS, DPS, MPS, SPC, DPC, SetPoint): read/write

 value (MV, TPI, Counter): read/write
 quality (all DP except SPC, DPC, SetPoint): read/write
 threshold value (MV, Counter): read
 alarm (global alarm status): read

The hierarchical relation implies that the DP can be seen as input as well as output of the function.
5.2.2 SERVER RELATION

The DPs are supplied by the function. They are not attached to the tree structure of the function. Their
parents are components from the electric tree structure or the system tree structure (bay, module, physical
device). The function is charged to update the status/value and quality attributes of these DPs.
Examples:
 DP resulting from a logical or analogue mathematical formula which is implemented by an automation

 synthesis DP (for example a device position)
 commands received and treated by the automation
The function has the following rights on the real time attributes of its supplied DPs:
 status (SPS, DPS, MPS, SPC, DPC, SetPoint): read/write

 value (MV, Counter, TXT): read/write
 quality (all DP except SPC, DPC, SetPoint): read/write
 threshold value (MV, Counter): read
5.2.3 CLIENT RELATION

The function is client of the DP. The DP is not attached to the tree structure of the function. Its parent is a
component from the electric tree structure or the system tree structure (bay, module, physical device).
The function reads and uses the status/value and quality attributes of the DP.
AP-66 SCE/EN AP/C60

If the type of the DP is SPC, DPC or SetPoint, the function can also send command requests. In this event,
the equipment that manages the DP acknowledges this request, executes the command and updates the
status and value attributes.
The command requests include parameters and quality modification. This is done in the same way
(acknowledge + attributes updates by the equipment that manages the DP). Thus, the DP is known as
controllable.
Examples:
 commands sent by an automation toward a device

 devices or bay state influencing the automation execution
 threshold modification request
 forcing, deletion, substitution request
 extended counter driving
The function has the following rights on the real time attributes of the DPs which the function is client of:
 status (SPS, DPS, MPS) read
 status (SPC, DPC, SetPoint): read/control
 value (MV, Counter, TXT): read
 quality (all DP except SPC, DPC, SetPoint): read/control
 threshold value (MV, Counter): read/control
5.2.4 ACCESS RIGHTS SUMMARY TABLE

ISaGRAF
DataPoint type Access types
variables type
any DP read/write input/output
The function owns the DP
Threshold, alarm read input
The function serves the DP (the function any DP read/write input/output
provides values) Threshold, alarm read control
SPS, DPS, SPS read input
SPC, DPC, SP read & control input/output
The function is client of the DP
MV read input
(the function reads the values)
COUNTER read & control input/output
Threshold, alarm read input
5.2.5 EQUIVALENCE OF SCE DATAPOINT IN ISAGRAF

The DataPoints are represented by variables inside the ISaGRAF projects. The type of these variables is
chosen according to the access type to the DataPoint.
The input DPs correspond to read-only variables of a structured type. These structures contain only the
DataPoint attribute usable inside the automations (see further).
Within the calculators ISaGRAF kernel, the output DPs are reached by C functions, using an ID. Therefore,
the DPs are projected in the ISaGRAF workbench by an integer which represents the address of the DP (its
ID). This integer is stored in the equivalences table. In an ISaGRAF project, this table contains some aliases:
a name and its value. Theses aliases must be used in the ISaGRAF programs to identify a variable. The
SCE/EN AP/C60 AP-67

name of an equivalence is made with the name of the variable, plus the suffix ADR. The value of an
equivalence is the address of the DP. The final values are set during the compilation of PLC project. An
equivalence is added automatically when a datapoint is added from the SCE application. The input/output
DPs (read/write access) are represented as input as well as output the workbench.
Relation Variable name Defined word (ref_dp) Signal Flow
Alstom DS
When xPS MV Counter xPC SP
AgileDPtype
ISaGRAF “is client of” DP <prefix>_in_XX <prefix>_in_XX_ADR KernelISaGRAF ISaGRAFKernel
DP belongs to ISaGRAF
<prefix>_in_out_XX <prefix>_in_out_XX_ADR ISaGRAFKernel KernelISaGRAF
UserFctDP
DP “is managed” by ISaGRAF <prefix>_in_out_XX <prefix>_in_out_XX_ADR ISaGRAFKernel KernelISaGRAF
<prefix>: optional free text given by the user in SCE

XX: incremented number fixed by the SCE
All “DP variables” have unique Ids stored in the equivalences table. The I/O symbols of the ISaGRAF
workbench must correspond to the configuration DPs of the SCE. They must be unique, easily recognisable
to facilitate the programming in the workbench but they must be short enough not to weigh down the
diagrams and the POUs texts either.
To give a name to the variables inside the ISaGRAF projects, consider that:
 The name must be unique

 ISaGRAF is not case sensitive
 The maximum length of name is 128 characters
 The first character must be a letter
 The following characters must be either a letter, a digit or an underscore
So the identifier of I/O symbols is made by concatenation of a prefix given by the user, a prefix automatically
given by the SCE (in, out, in_out) and an identifier number.
In the workbench, the user will have an alias made up of the short names of the bay, module and DataPoint
in the form bay_module_datapoint. The used short name language will be the one which is declared as
“automata language”, i.e. one of the 4 basic languages: English, French Spanish or German. Complete
identifier SCE appears in the data dictionary of the workbench inside the comment field. The dictionary is
provided through the menu Workbenches > ISaGRAF Edit and the icon Parchment.
The “DP variables” are located in different groups according to their type and relation to the function. These
groups are not created to prevent the user from adding variables to them.
In SCE, the address is stored as an attribute of the link between the function and the DP. This attribute is
updated during the fusion of the functions projects towards the PLC project and the equivalence table is
updated with the new values of the variables addresses.
5.2.6 ISAGRAF VARIABLES AND DICTIONARY DATA STRUCTURES

The base types are:
SCE ISaGRAF Usable
1 Status Int32 Status DINT x
2 Quality Int32 Quality DINT x
3 GlobalAlarmStatus char Alarm SINT x
4 Value, threshold float Value, threshold REAL x
AP-68 SCE/EN AP/C60

A structure is a complex data type defined as set of members. They can have various data types or be
themselves a structure. The variables are created from structures with attributes:
strXps includes 1, 2, 3, strXpc: 1, 3, strIecMv: 3 and 4, strIecCounter: 2 and 4
To improve ISaGRAF applications source code readability & maintainability, a set of Defined words is also
defined for each type of DP in the project template used by SCE. Status words prefixed by DP type:
DS Agile
ISaGRAF type Status field Value
type
SPS_RESET
SPS_FORCED_RESET 1
xPS: structure strIecXps SPS_SUBSTITUTED_RESET
SPS
Quality field Value SPS_SET
SPS_FORCED_SET 2
VALID 0 SPS_SUBSTITUTED_SET
SELFCHECK_FAULTY 1 DPS_MOTION00 3
UNKNOWN 2 DPS_OPEN
FORCED 4 DPS_FORCED_OPEN 4
DPS_SUBSTITUTED_OPEN
SUPPRESSED 8 DPS
DPS_CLOSED
SUBSTITUTED 16 DPS_FORCED_CLOSED 5
TOGGLING 32 DPS_SUBSTITUTED_CLOSED
DPS_UNDEFINED=SELFCHECK_FAU 6
When the field Quality is different of VALID, the Status ANY
field has no meaning MPS_STATE1
1 …16
MPS MPS_FORCED_STATE1
0…15
MPS_SUBSTITUTED_STATE1
(comp.)
SPC_OFF 0
SPC_ON 1
SPC_SELECT_OFF 4
SPC_SELECT_ON 5
SPC
SPC_SELECT_RAISE 8
SPC_SELECT_LOWER 9
SPC_RAISE 6
SPC_LOWER 7
xPC: structure strIecXpc DPC_OFF 0
DPC_ON 1
DPC_SELECT_OFF 2
DPC_SELECT_ON 3
DPC
DPC_SELECT_RAISE 4
DPC_SELECT_LOWER 5
DPC_RAISE 6
DPC_LOWER 7
SP
SCE for MV and TPI: structure strIecMv ISaGRAF Usable

Value Value REAL x
HHHThresholdValue Threshold_hhh REAL x
HHThresholdValue Threshold_hh REAL x
HthresholdValue Threshold_h REAL x
SCE/EN AP/C60 AP-69

SCE for MV and TPI: structure strIecMv ISaGRAF Usable

LthresholdValue Threshold_l REAL x
LLThresholdValue Threshold_ll REAL x
LLLThresholdValue Threshold_lll REAL x
Quality Quality DINT x
GlobalAlarmStatus Alarm SINT
SCE for Counter: structure strIecCounter ISaGRAF Usable

Value Value REAL x
FrozenCumulativeValue FrozenCValue REAL
HHHThresholdValue Threshold_hhh REAL
HHThresholdValue Threshold_hh REAL
HthresholdValue Threshold_h REAL
LthresholdValue Threshold_l REAL
LLThresholdValue Threshold_ll REAL
LLLThresholdValue Threshold_lll REAL
Quality Quality DINT x
ISaGRAF type DS Agile type Quality field Value

VALID 0
SELFCHECK FAULTY 1
UNKNOWN 2
FORCED 4
SUPPRESSED 8
SUBSTITUTE 16
SATURATED 64
MV MV, TPI UNDEFINED 128
OPEN CIRCUIT 256
L_THRESHOLDVIOLATION 512
LL_THRESHOLDVIOLATION 1024
LLL_THRESHOLDVIOLATION 2048
H_THRESHOLDVIOLATION 4096
HH_THRESHOLDVIOLATION 8192
HHH_THRESHOLDVIOLATION 16834
VALID 0
SELFCHECK FAULTY 1
Counter Counter UNKNOWN 2
OVERRANGE 64
UNDEFINED 128
One value is possible at a time (e.g.: cannot be FORCED and THRESHOLDVIOLATION). Thresholds have
low priority: they are signaled only when the quality is VALID.
For ISaGRAF redundancy in WACU management, two other structures exist:
AP-70 SCE/EN AP/C60

TrdnGeneralState:
Base
Attribute Definition Values
type
1 = Primary
unit_nb Primary or secondary WACU determination UDINT
2 = Secondary
0 = Idle state
primary_gtw_state Primary WACU state: Master, Standby, Idle UDINT 1 = Master
2 = Standby
0 = Unknown
1 = Operational
Complementary information relative to primary 2 = Standalone
primary_complementary_state UDINT
WACU redundancy state 3 = Discordant
4 = Failure
5 = Forced
Validity of redundancy information dedicated to 0 = Invalid
primary_validity UDINT
primary WACU 1 = Valid
0 = Idle state
secondary_gtw_state Secondary WACU state: Master, Standby, Idle UDINT 1 = Master
2 = Standby
0 = Unknown
1 = Operational
Complementary information relative to secondary 2 = Standalone
secondary_complementary_state UDINT
WACU redundancy state 3 = Discordant
4 = Failure
5 = Forced
Validity of redundancy information dedicated to 0 = Invalid
secondary_validity UDINT
secondary WACU 1 = Valid
0 = Absent
auxiliary_state Auxiliary link state UDINT
1 = OK (present)
0 = Unvalid
auxiliary_state_validity Information validity dedicated to Auxiliary link UDINT
1 = Valid
“TrdnGeneralState” structure version. It permits
structure_version to copy data to application without risk to erase UDINT 0..n
other information of the application
TProtocolState:
Base
Attribute Definition Values
type
Protocol communication state on local TRUE = Comm. established
CommSt_local BOOL
WACU FALSE = No communication
TRUE = Master FALSE= Stand-
RedST_local Protocol redundancy state on local WACU BOOL
by
Complementary information relative to
TRUE = Valid
Valid_local validity state of local WACU CommSt & BOOL
FALSE = Invalid
RedST
Protocol communication state on distant TRUE = Comm. established
CommSt_remote BOOL
WACU FALSE = No communication
TRUE = Active
RedST_ remote Protocol redundancy state on distant WACU BOOL
FALSE= Stand-by
Complementary information relative to
TRUE = Valid
Valid_ remote validity state of distant WACU CommSt & BOOL
FALSE = Invalid
RedST
SCE/EN AP/C60 AP-71

When Primary or Secondary WACU validity is equal to 0 (Invalid), complementary_state & gtw_state are also set
to 0.
5.2.7 KERNEL INTERFACE API

This part details API available to the system engineer while designing the ISaGRAF application to exchange
data and commands with the kernel. 2 mechanisms are used:
Direct access to the dictionary when DP is of type xPS, MV, Counter
Flow Role Description
At the cycle end, if an event has been received for the DP since the previous
Reading cycle, the new value is copied into the ISaGRAF variable. Only one event is
KernelISaGRAF
xPS/MV extracted for a given DP at each cycle; the execution starts when all DPs for
which an event has been received have been updated
The IEC1131 application writes in the DP structure. The ISaGRAF output hook
checks for variables that have changed during the cycle, and sends
Writing
ISaGRAFKernel corresponding messages to kernel. For MV: to avoid sending messages for very
xPS/MV
small changes in the value (lower than a deadband), some parameters are
associated by the SCE, and sent in isa.bin
Explicit call for functions from the ISaGRAF application to read or write a DP
 Receiving commands from outside (via kernel) for DP using the relation "User Function DP":
Functions group 1 Used when
Wait_Binary_Order ISaGRAF module must wait to the execution of an order on a SPC or a DPC
Wait_Digital_Order ISaGRAF module must wait to the execution of an order on a setpoint
PLC manages a datapoint feedback of an expected command (Wait_xxx_Order). It permits
Send_Ack_Order
to acknowledge the received order
 Sending commands to outside (via kernel) for DP using the relation "is client" or "manages":
Function group 2 Usable for which DP
• SPC, DPC
Send_Binary_Order
• Select part of an SBO on AO
AO datapoint and Setpoint
Send_Digital_Order
The select of SBO is done using Send_Binary_Order function
Send_Quality_Order Allows the FSS and relates to xPS, MV, COUNTER datapoints
Send_Threshold_Order MV whose ISaGRAfF wants to modify threshold(s)
Wait_Ack_Order ISaGRAF module must wait for the acknowledgement of one of its order (Send_xxx_order)
 Sending other datapoints to outside (via kernel):

Set_xPS, Set_MV and Set_LSP (Load Shedding Priority) are used by the ISaGRAF module to modify all
the attributes of, respectively, the xPS, MV, LSP, that it manages.
It allows transmitting the corresponding attributes to the computer that holds the runtime.
Set_xPS, Set_MV are for DP using the relation "User Function DP".
Set_LSP is for DP using the relation "is client" or "manages".
 Is_Connected_To is used to know if two nodes are connected.
AP-72 SCE/EN AP/C60

Functions general use:

Flow Function Description
Group 1 The command received by the kernel remains in the stack until the
KernelISaGRAF
Is_Connected_To ISaGRAF application explicitly reads and acknowledges it
Group 2 Sending commands
ISaGRAFKernel
Set_xxx Writing outputs
5.2.8 PROTOTYPE AND USAGE OF ALSTOM DS AGILE FUNCTIONS FOR ISAGRAF

IMPORTANT
 All the following described functions must never be called in ISaGRAF SFC transitions but only in
actions.
5.2.8.1 SEND_BINARY_ORDER
This function concerns the following DP used in ‘is client of’ or ‘manages’ relations:
 SPC, DPC
 Select part for SBO on SetPoint
This function allows the ISaGRAF automatic control application to send selection or execution commands to
equipment on the SBUS network.
The link between the automatic control application and the command configured in the SCE is provided by a
variable configured in ISaGRAF workshop. This variable must be one of the following DS Agile types: SPC,
DPC or RAISE_LOWER and have a user address which must be entered in the Ref_DP field.
Note: The user address therefore defines the ISaGRAF variable to be used and consequently the usual SCE
variable, to which the command relates. However, the order variable can be anything. The user is not obliged to give
the name of the ISaGRAF variable corresponding to Ref_DP. It will be sufficient to read the report back from the
function.
Parameter/ C Type
Name Comment Access Available values
return code (IEC Type)
Unsigned char FALSE : KO
Return code Output
(BOOL) TRUE : OK
0 : SPC_OFF
1 : SPC_ON
4 : SPC_SELECT_OFF
5 : SPC_SELECT_ON
Order Order Parameter Input Char (SINT)
6 : SPC_RAISE
7 : SPC_LOWER
8 : SPC_SELECT_RAISE
9 : SPC_SELECT_LOWER
Masks :
1 = Interlock bypass
2 = Locking bypass
4 = Mode bypass
Forcing
Bypass Parameter Input Long (DINT) 8 = Uniqueness bypass
(unused if Order=SELECT)
16 = Automation bypass
32 = Synchrocheck bypass
Several masks can be set
simultaneously
SCE/EN AP/C60 AP-73

Parameter/ C Type
Internal reference of the DP Use equivalent word linked to the
Ref_DP Parameter Input Long (DINT)
in host equipment datapoint (<var>_ADR)
Ref_cmd Command Identifier Parameter Output Long (DINT) Use a local variable
Prototype C:
Unsigned char Send_Binary_Order(char Order, long Bypass, long Ref_DP ,long Ref_Cmd )
The state of this function is FALSE if the number of controls in progress is larger than
NB_MAX_ISA_CONTROL (currently 1000). Read the log file.
The function Send_Binary_Order must be into a P1 step (run only one time) as illustrated in the Grafcet that
follows (it includes several digital outputs in the same step):
5.2.8.2 SEND_DIGITAL_ORDER
This function concerns SetPoints used in ‘is client of’ or ‘manages’ relations.
Select for SBO is done via function Send_Binary_Order.
Parameter/ C Type
Return code Output
(BOOL) TRUE : OK
Order Value order Parameter Input Float (REAL)
AP-74 SCE/EN AP/C60

Parameter/ C Type
Use equivalent word linked
Internal reference of the DP in
Ref_DP Parameter Input Long (DINT) to the datapoint
host equipment
(<var>_ADR)
Ref_cmd Identifier of the command Parameter Output Long (DINT) Use a local variable
Prototype C:
Unsigned char Send_Digital_Order(float Order, long Ref_DP, long Ref_cmd)
The state of this function is FALSE if the number of controls in progress is larger than
NB_MAX_ISA_CONTROL (currently 1000). Read the log file.
The function must be into a P0/P1 step. An example of programs is given in section 5.2.8.7.
5.2.8.3 SEND_QUALITY_ORDER
This function concerns SPS, DPS, MPS, MV, TPI, COUNTER used in ‘is client of’ or ‘manages’ relations for
Forcing/Suppression/Substitution functionality.
Parameter/ C Type
FALSE : KO
Return code Output Unsigned char (BOOL)
TRUE : OK
1 : FORCING
2 : SUBSTITUTING
3 : UNFORCING
Quality Asked quality Parameter Input Char (SINT)
4 : UNSUBSTITUTING
5 : SUPRESSING
6 : UNSUPRESSING
SPS
1 : Reset
2 : Set
DPS
3 : JAMMED
4 : Open
5 : Close
MPS
7 : State1
8 : State2
9 : State3
Forcing or
10 : State4
Binary_Value substitution value for Parameter Input Char (SINT)
11 : State5
SPS, DPS, MPS
12 : State6
13 : State7
14 : State8
15 : State9
16 : State10
17 : State11
18 : State12
19 : State13
20 : State14
21 : State15
22 : State16
Forcing or
Digital_Value substitution value for Parameter Input Float (REAL)
MV, TPI, COUNTER
Internal reference of
the DP in host device
(<var>_ADR)
SCE/EN AP/C60 AP-75

Parameter/ C Type
Identifier of the
Ref_cmd Parameter Output Long (DINT) Use a local variable
command
Prototype C:
Unsigned char Send_Quality_Order(char Quality, char Binary_Value, float Digital_Value, long Ref_DP, long
Ref_cmd)
Note: This function works correctly only if ISaGRAF changes quality of its own C26x.
5.2.8.4 SEND_ACK_ORDER
This function is used when the automatism manages a DP to answer an awaited command
(Wait_xxx_Order). It allows acknowledgement of received order. It is only used for "User Function DP".
Parameter/ C Type
Return code Output
(BOOL) TRUE : OK
Use equivalent word linked to the
Ref_DP the DP in host Parameter Input Long (DINT)
datapoint (<var>_ADR)
equipment
Order of the run Order received by the Wait_Binary_Order
Order Parameter Input Char (SINT)
command function
Order received by the Wait_Digital_order
Value Digital order value Parameter Input Float (REAL)
function
Acknowledgement
Ack_code Parameter Input Long (DINT) See hereafter
code
Prototype C:
Unsigned char Send_Ack_Order(long Ref_DP, char Order, real Value, long Ack_code)
Available acknowledgement codes
1 ACK_OK - positive acknowledgement
2 INCOHERENT_REQUEST - incoherent command
3 DS Agile C26x COMPUTER_NOT_READY - command when DS Agile C26x is initializing
4 BAY_SUBST_MODE_FAULT - error on substation or bay Local/remote mode
5 CONTROL_MODE_FAULT - command when DS Agile C26x is in maintenance/faulty
6 DEVICE_LOCKED - locked device
7 REQUEST_IN_PROGRESS - command in progress for the device or reception of a command during
delay of forbidden command (inter-control delay)
8 INTERLOCK_NOK - refused by interlock
9 DEVICE_ALREADY_IN_POS - command similar to device current state
10 HW_FAULT - DO board fault
11 POS_INVALID - invalid position of device
12 TIMEOUT_FAILED - time-out between selection & execution or time-out in IED answer
AP-76 SCE/EN AP/C60

13 AUTOMATION_RUNNING - device locked by relevant AutoManu information

14 DEVICE_ALREADY_SELECTED - reception of a selection request as device is still selected
15 DEVICE_NOT_SELECTABLE - reception of a selection request as device is Direct Execute
16 UNIQUENESS_INCOHERENCY - failure in command uniqueness
17 NO_SELECTED - reception of a execution demand as device is not yet selected
18 OPERATOR_CANCEL - cancel operator
19 EXTERNAL_FAULT - time-out on feedback
20 ACK_FAILED_ORDER - acknowledgement failed
21 ACK_BAD_TCIP - time-out waiting presence of TCIP SPS
22 ACK_TCIP_TOO_LONG - time-out waiting OFF state of TCIP information
23 ACK_BAD_TAP - bad tap position following a command
24 ACK_MIN_TAP - reception of order "lower" as TPI is on Min value
25 ACK_MAX_TAP - reception of order "raise" as TPI is on Max value
26 DEVICE_FAILED_TO_OPERATE - command towards disconnected IED
27 SYNCHRO_NOK – command refused by synchrocheck
28 GLOBAL_ATCC_OFF - ATCC stopped.
29 TOO_MANY_TRANSFORMER
30 INVALID_TOPOLOGY
31 INVALID_TPI
32 TRANSFORMER_BAY_DISCONNECTED
33 MCB_TRIP
34 INVALID_TRANSFORMER_VOLTAGE
35 INVALID_BUSBAR_VOLTAGE
36 PARAMETER_CHANGE_IN_EXECUTION - IEC61850
37 ELECT_FAILED
38 ICT_OPEN
5.2.8.5 WAIT_BINARY_ORDER
This function is used when the ISaGRAF module must wait for an execution order relevant to SPC or DPC. It
is only used for "User Function DP".
Parameter/ C Type
Return code Output
(BOOL) TRUE : OK
0 : SPC_OFF
1 : SPC_ON
4 : SPC_SELECT_OFF
5 : SPC_SELECT_ON
6 : SPC_SELECT_RAISE
Order Order Parameter Output Char (SINT)
7 : SPC_SELECT_LOWER
8 : SPC_RAISE
9 : SPC_LOWER
SCE/EN AP/C60 AP-77

Parameter/ C Type
in host equipment datapoint(<var>_ADR)
Prototype C:
Unsigned char Wait_Binary_Order(char Order, long Ref_DP)
If the order has a SBO type, the Select will be computed outside ISaGRAF (so Select can only be soft). A
Wait_Binary_Order must be followed by a Send_Ack_Order.
Return code:
The returned value is FALSE when no order is received for this DP. When an order is received by the kernel,
the return code is TRUE for the first call after the order receipt. The order is then un-stacked from the kernel,
and the order value is returned by the function to the ISaGRAF application in the parameter “Order”.
An input parameter can be used as a function output value.
5.2.8.6 WAIT_DIGITAL_ORDER
This function is used when the ISaGRAF module must wait for an execution order relevant to SetPoint. It is
only used for "User Function DP".
Parameter/ C Type
Return code Output
(BOOL) TRUE : OK
Order Order Parameter Output Float (REAL) Value of the order received
in host equipment datapoint (<var>_ADR)
Prototype C:
Unsigned char Wait_Digital_Order(float Order, long Ref_DP)
If the order is of SBO type, the Select is computed out of ISaGRAF (so Select must be soft).
A Wait_Digital_Order must be followed by a Send_Ack_Order.
When an action calls the function Wait_Ack_Order, the subsequent transition must at least test the TRUE
value of the function return code (indicating that control has been well received)
5.2.8.7 WAIT_ACK_ORDER
This function is used when the ISaGRAF module is waiting for an acknowledgement of one of its commands
(Send_xxx_order). It concerns the DP used in ‘in client’ or ‘manages’ relation.
Parameter/ C Type
Return code Output
(BOOL) TRUE : OK
Command reference on Use the variable associated to
Ref_cmd which acknowledgement is Parameter Input Long (DINT) Ref_cmd used in the function
awaited Send_xxx_order
Ack_code Acknowledgement code Parameter Output Long (DINT) Cf. Send_Ack_Order
AP-78 SCE/EN AP/C60

Prototype C:
Unsigned char Wait_Ack_Order(long Ref_cmd, long Ack_code)
It’s possible to have several Wait_Ack_Order (maximum 10) in the same step, under the condition to get
back the return value in an intermediary variable. Once the acknowledgement is returned, the reference of
the control is suppressed and doesn’t exist any more, so every new call of this function sends the FALSE
return value.
The function Wait_Ack_Order must be into an N step (run every cycle). See Grafcet above.
Example of SFC program invoking this function after send_binary_order:

if VTestNb = 1 then
if VStep_Nb = 1 then
(* sending of selection command *)
(*Vref_dp_etap1 := 1;*) (* user address *)
(*SPC_SELECT_ON = 5*)
order := 5;
return := send_binary_order(order , bypass, ref_dp_udint, ref_cmd);
VStep_Nb := 2;
end_if;
(* waiting the selection acknowledgment *)
return := wait_ack_order(ref_dp, ack_code_wait_ack_order);
if (return = TRUE) then
VStep_Nb := 3;
end_if;
end_if;
(* sending of order *)
(*Vref_dp_etap1 := 1;*) (* user address *)
(*SPC_ON = 1*)
order := 1;
return := send_binary_order(order , bypass, ref_dp_udint, ref_cmd );
VStep_Nb := 4;
end_if;
(*waiting the order acknowledgment *)
return := wait_ack_order(ref_dp, ack_code_wait_ack_order);

if (return = TRUE) then
VStep_Nb := 5;
end_if;
end_if;
end_if;
SCE/EN AP/C60 AP-79

5.2.8.8 SET_XPS
This function is used to give to the host equipment the SPS, DPS, MPS whose all attributes can be updated
by ISaGRAF module. This function uses "User Function DP".
Parameter/ C Type
Return code Output
(BOOL) TRUE : OK
Status field:
SPS :
1 : Reset
2 : Set
DPS :
3 : Jammed
4 : Open
5 : Close
6 : Undefined
MPS :
7 : State1
8 : State2
9 : StatE3
strIecXps {
10 : State4
long Status (DINT);
11 : State5
DP_value DP to update Parameter Input long Quality (DINT);
12 : State6
char Alarm (SINT);
13 : State7
}
14 : State8
15 : State9
16 : State10
17 : State11
18 : State12
19 : State13
20 : State14
21 : State15
22 : State16
Quality field:
0 : VALID
1 : INVALID
Alarm field:
(not significant)
Internal reference of the
DP in host equipment
(<var>_ADR)
Prototype C:
Unsigned char Set_xPS(struct_xPS DP_Value, long Ref_DP)
For DPS managed through Set_xPS function, the non-complementarity delays (00 and 11) must be set to 0
in configuration.
AP-80 SCE/EN AP/C60

5.2.8.9 SET_MV
This function is used to give to the host equipment the MV whose all attributes can be updated by ISaGRAF
module. This function uses "User Function DP".
Parameter/ C Type
FALSE : KO
Return code Output Unsigned char (BOOL)
TRUE : OK
strIecMv { Value field:
float Value (REAL); any real value
float Threshold_hhh (REAL); compatible with
float Threshold_hh (REAL); configuration data
float Threshold_h (REAL); of the DP
DP_value DP to update Parameter Input float Threshold_l (REAL); Quality field:
float Threshold_ll (REAL); 0 : VALID
float Threshold_lll (REAL); 1 : INVALID
long Quality (DINT); Threshold_xxx &
char Alarm (SINT); Alarm fields:
} (not significant)
Use equivalent
word linked to the
Ref_DP the DP in host Parameter Input Long (DINT)
datapoint
equipment
(<var>_ADR)
Prototype C:
Unsigned char Set_MV(struct_MV DP_Value, long Ref_DP)
5.2.8.10 SET_LSP
This function is used in FLS function to set several bits simultaneously in a 16-bit word.
Parameter/ C Type
return code (CEI Type)
Return code Output
(BOOL) TRUE : OK
Integer (DINT){
long
Status (DINT);
DP_value DP to modify Parameter Input long 0x0000…0xFFFF
Quality (DINT);
char Alarm (SINT);
}
Use “Defined word” for the
DP Internal reference in
Ref_DP Parameter Input Long (DINT) datapoint
host equipment
<prefix>_in_out_XX_ADR
Prototype C:
Unsigned char Set_LSP(long DP_Value, long Ref_DP)
SCE/EN AP/C60 AP-81

5.2.8.11 IS_CONNECTED_TO
This function determines in FLS function if two electrical nodes are connected or not.
Parameter/ C Type
return code (CEI Type)
0: TOPO_UNCERTAIN
Return code Output Integer (SINT) 1:TOPO_UNCONNECTED 2:
TOPO_CONNECTED
Long (DINT){
long
Status (DINT);
Node1 Node number 1 Parameter Input long
Quality (DINT);
char Alarm (SINT);
}
Node2 Node number 2 Parameter Input Long (DINT)
Prototype C:
int is_connected_to(long node1, long node2)
2 nodes are connected if it exists at least one chain of devices between the 2 nodes which are closed, forced
closed or substituted closed.
2 nodes are unconnected if all chains of devices between the 2 nodes are open, forced open or substituted
open. In all other cases, the status between two nodes is uncertain (the SUPPRESSED status is taken into
account as the UNKNOWN status).
5.2.8.12 REDUNDANCY_GET_STATE
This function is dedicated to redundancy for WACU.It allows the ISaGRAF automatic control application to
obtain the general state of the redundant WACUs.
Parameter/ C Type
Unsigned char
Retour Return code Output alwaysTRUE
(BOOL)
Redundant General
RdnGeneralState Parameter Input TrdnGeneralState
state of the gateway
Prototype C:
Unsigned char Redundancy_get_state(TrdnGeneralState RdnGeneralState)
5.2.8.13 REDUNDANCY_SWITCH
cause the switchover of the redundant WACUs.
Parameter/ C Type
FALSE : KO (issue at transmission of
Unsigned char
Retour Return code Output command to redundancy driver)
(BOOL)
TRUE : OK
Prototype C:
Unsigned char Redundancy_switch()
AP-82 SCE/EN AP/C60

5.2.8.14 PROTOCOL_GET_STATE
know the communication state and protocol activity for each redundant WACU.
Parameter/ C Type
Unsigned char FALSE : KO (access disabled)
Retour Return code Output
(BOOL) TRUE : OK
Upper protocol: 0..3 acc. conf.
Unsigned long
instance Instance of protocol Parameter Input Lower protocol: 5 for T101 master
(UDINT)
(mandatory)
Communication and
vState redundancy state of the Parameter Input TProtocolState
protocol
Prototype C:
Unsigned char Protocol_get_state(Unsigned long instance,TProtocolState vState)
5.3 CAVEATS
Isagraf does not support some characters:
Slash: “ / ”
Comma: “ , ”
Space: “ “
Single quote “ ‘ “
Break “ … “
5.4 WACU REDUNDANCY WITH ISAGRAF
5.4.1 SWITCH AUTOMATION FOR REDUNDANCY

The application designer must write a call for each protocol instance to monitor. S/he must declare a variable
vState for each instance. First, s/he must import the redundancy_protocol.txt file onto the ISaGRAF
workbench.
Creating the variable vStateProtocole2, based on TProtocolState type in the ISaGRAF database and writing:
Retour := protocolGetState(2,vStateProtocole2);
in an ISaGRAF Program Operating Unit (POU) is sufficient to see CommSt and RedSt of each WACU for the
concerned protocol (refer to the chapter GTW/EN AP).
The ISaGRAF WACUs are not switched by the system. The application designer must invoke
redundancy_switch() to have active ISaGRAF on the WACU on which the protocol is active.
For instance, to switch the WACU if protocol 2 is active on the standby WACU, the code might be as follows:
retour := protocol_get_state(0, VProtocolState_0);
retour := Protocol_get_state(1, VProtocolState_1);
SCE/EN AP/C60 AP-83

if (((RdnGeneralState.UNIT_NB =1 ) AND ( RdnGeneralState.PRIMARY_GTW_STATE =

1)) OR ((RdnGeneralState.SECONDARY_GTW_STATE = 1) AND
(RdnGeneralState.UNIT_NB =2))) then
if vProtocolState_0.Valid_local = TRUE then

if vProtocolState_0.Valid_remote = TRUE then
if (vProtocolState_0.RedSt_local = FALSE) AND (vProtocolState_0.CommSt_remote
= TRUE) AND (vProtocolState_0.RedSt_remote = TRUE) then
retour := redundancy_switch();
end_if;
end_if;
end_if;
end_if;
WARNING: Redundant WACU configuration check
The user must have loaded the same configuration database on both WACUs (check is done at WACU start-
up).
If the two WACU configuration databases are not identical, synchronization is not possible. In this
case, both WACUs stay in IDLE state (MASTER IDLE state & STAND-BY IDLE state) so switch-over is
not possible.
5.4.2 ISAGRAF PROGRAMMATION BEST PRACTICES

The following best practices are given for programs implementing User Functions dedicated to using WACU
redundancy features.
5.4.2.1 SEND_BINARY_ORDER AND SEND_DIGITAL_ORDER COMMANDS
 Execute “redundancy_get_state(RdnGeneralState)” function at the program beginning

“RdnGeneralState” is a variable incorporating “TrdnGeneralState” structure
 Check the WACU and, to send the command, state:

 IF unit_nb = 1 (primary) AND primary_gtw_state = 1 (Master or Active) AND primary_validity = 1
(valid) THEN the command can be sent
 IF unit_nb = 2 (secondary) AND secondary_gtw_state = 1 (Master or Active) AND
secondary_validity = 1 (valid) THEN the command can be sent
5.4.2.2 REDUNDANCY_SWITCH COMMAND TO SWITCH A GATEWAY TO STANDBY
 Execute “redundancy_get_state(RdnGeneralState)” function at the program beginning

 Check the WACU and, to send the command, state:
 IF unit_nb = 1 (primary) AND primary_gtw_state = 1 (Master or Active) AND primary_
complementary_validity = 1 (operational) THEN the command can be sent
 IF unit_nb = 2 (secondary) AND secondary_gtw_state = 1 (Master or Active) AND
secondary_complementary_validity = 1 (operational) THEN the command can be sent
5.4.2.3 CONNECTION TO BOTH WACUS

In order to monitor both WACU applications at the same time, the user has to:
AP-84 SCE/EN AP/C60

Generate ISaGRAF project on one PC.

Then copy the “prjlibrary.mdb” on another PC (equipped with ISaGRAF workbench in the same release).
Then it is possible to open each project at the same time on both PC and connect one to the primary WACU
and the other to the secondary WACU.
Ensure that the project is closed before copying the project.
5.5 DEFINING AN ISAGRAF SLOW AUTOMATION

The core of the slow automation modelling is a ‘Slow automation’ object that corresponds to an ISaGRAF
project. Slow automation can own datapoints for status, control of automation itself (automation
management); for instance, a load shedding automation can have a control to put it in/out of service and a
relevant status.
They also reference via links datapoints located in system or electrical topologies. There are two types of
link:
 ‘client’ link, that means that the slow automation uses the datapoint that is acquired or managed
outside the ISaGRAF automation. For instance, the load shedding automation can be client of some
‘circuit-breaker status’ input datapoints and some ‘circuit-breaker control’ output datapoints.
 ‘server’ link, that means that the slow automation produces or manages the datapoint. For instance, a
slow automation can be used to produce the sum of feeder measurements. This sum is also a
measurement at voltage level for ex.
To define a slow automation, do the steps that follow:
1. define the slow automation interface:
 create the slow automation ‘header’
 if required, create the datapoints at slow automation level, used for the function management
 create the client links for the slow automation
 create the server links for the slow automation
2. define the slow automation body launching from the SCE the ISaGRAF editor (contextual menu on the
slow automation interface object) and using available languages and previously client/server defined links
3. establish the effective client/server links entering to existing datapoints.
5.5.1 CREATING AN ISAGRAF SLOW AUTOMATION (HEADER DEFINITION)

To add an ISaGRAF slow automation, tap into the “Objects entry” window at any level of the electrical
topology (except Site and module): select ‘Slow automation’ and right click Add.
Figure 13: Adding an ISaGRAF slow automation (e.g. for Feeder bay level)
SCE/EN AP/C60 AP-85

ISaGRAF slow automation features must be set in SCE:

(1) Fill the relation ‘runs on’, giving which computer PLC manages the automation. This relation is
automatically filled by SCE if slow automation is located under a bay whose manager has ever been
entered
(2) short name and long name of slow automation used for logging & alarm
Figure 14: Setting ISaGRAF Slow Automation Features
AP-86 SCE/EN AP/C60

5.5.2 ADDING SPECIFIC DATAPOINTS TO A SLOW AUTOMATION (INTERFACE

DEFINITION)
To add a slow automation datapoint, tap into the Objects entry window at slow automation level by clicking
on mouse’s right button.
Figure 15: Adding Datapoints to a Slow Automation
A slow automation datapoint is integrally produced or managed by the slow automation and subsequently by
ISaGRAF. It cannot be linked to another acquisition or control source and the ISaGRAF project must
update/run its value changes or controls.
Slow automation input datapoints are stored in a WACU computer's or Bay controller's non-volatile memory
to restart on their latest known values in the event of a reboot.
5.5.3 CREATING AN ISAGRAF CLIENT LINK (INTERFACE DEFINITION)

To add an ISaGRAF client at the slow automation level, right-click a ‘is client of’ relation in the Objects entry
contextual window and select Add (alternative: double-click the relation):
Choose the correct relation depending on the type of datapoint to use.
SCE/EN AP/C60 AP-87

Figure 16: Adding an ISaGRAF Client Link
AP-88 SCE/EN AP/C60

5.5.4 LINKING A DATAPOINT TO AN ISAGRAF CLIENT LINK

To link a datapoint to an ISaGRAF client link, define the relation 'is client of'. For that double click this
relation (1). The Relation Link Editor is then displayed. Expand the tree view to list all the available SPS
datapoints. Click the one you want to link (2) then click the Ok button. (In the example given hereafter the
link has be done with the VoltageLevel SPS datapoint). The relation is then displayed as defined (3).
Figure 17
5.5.5 DEFINING ISAGRAF IO PREFIX FOR AN INPUT

Click this 'is client of' relation to display the associated attributes window. Only the 'Isagraf IO prefix'
attribute (4) can be modified by the user. This attribute defines the prefix of the identifier of this datapoint
when used in ISaGRAF workbench as an input signal of this automation. It is the concatenation of the prefix,
SCE/EN AP/C60 AP-89

an underscore (if the prefix exists) and the input IO reference automatically given by the SCE: In the
example given hereafter the identifier of this link will be: MY_INPUT_PREFIX_in_2
(4)
Figure 18: Defining an ISaGRAF IO Prefix for an Input
Configuration rules and checks
 first character: letter only

 following characters: capital, digit or underscore
 maximum length: 80 characters
5.5.6 CREATING ISAGRAF SERVER LINK (INTERFACE DEFINITION)

To add an ISaGRAF server, tap into the “Objects entry” window at the slow automation level by clicking on
mouse’s right button and adding a ‘manages’ relation. Choose the correct relation depending on datapoint
type to manage.
AP-90 SCE/EN AP/C60

Figure 19: Adding an ISaGRAF Client Link
5.5.7 LINKING A DATAPOINT TO AN ISAGRAF SERVER LINK

To link a datapoint to an ISaGRAF server link the relation 'manages' must be defined. For that double click
this relation (1). This displays the Relation Link Editor. Expand the tree view to list all the available DPS
datapoints. Click the one you want to link (2) then click the Ok button. (In the example given hereafter the
link has be done with the Substation DPS datapoint).
The relation is then displayed as defined (3).
SCE/EN AP/C60 AP-91

Figure 20: Linking a Datapoint to an ISaGRAF Server Link
5.5.8 DEFINING ISAGRAF IO PREFIX FOR AN OUTPUT

Click this manages' relation to display the associated attributes window. You can modify only the 'Isagraf IO
prefix' attribute (4). This attribute defines the prefix of the identifier of this datapoint when used in ISaGRAF
workbench as an output signal of this automation. It is the concatenation of the prefix, an underscore (if the
prefix exists) and the output IO reference automatically given by the SCE: In the example given hereafter the
identifier of this link is: My_Output_Prefix_out_0
AP-92 SCE/EN AP/C60

Figure 21: defining isagraf io prefix for an output
Configuration rules and checks:
 first character: letter only

 following characters: capital, digit or underscore
 maximum length: 80 characters
.
5.5.9 USING ISAGRAF EDITOR (BODY DEFINITION)

To launch the ISaGRAF editor at Slow automation level, right click ISaGRAF Edit.
Figure 22: LAUNCHING ISAGRAF EDITOR
ISaGRAF editor allows diagram edition of the automation.

In order to connect ISaGRAF workbench to both redundant computers (for example in the aim of target
loading, debug or monitoring…), it is possible to set network properties with mirror target IP addresses.
SCE/EN AP/C60 AP-93

In ISaGRAF Workbench, “Hardware architecture”, select

connection between ETCP network and configuration.
01
By a right click, select “Properties”.
On the first tab “Network Parameters”, set

02
primary computer IP address.
On the second tab “Mirror targets”, click on “Add” button in

order to set secondary computer IP address.
It is necessary to build/rebuild project/library in order to
03
take into account network settings
AP-94 SCE/EN AP/C60


Connect to one of the computer by clicking:
 “Download” ;
 “Debug Target” ;
 “Simulation”
The window allows the user to choose to connect to one of
the targets (the main target or one of the mirror targets).
04
Note:
In case of connection to a WACU, the “ETCP.EXE” and
“ISAGRAF.EXE” processes have to be already launched
on WACU to establish communication with ISaGRAF
workbench.
SCE/EN AP/C60 AP-95

AP-96 SCE/EN AP/C60

HUMAN INTERFACE
SCE/EN HI/C60
DS Agile System Configuration Editor Human Interface
Contents

1.1 Using DS Agile SCE 5
1.1.1 DS Agile SCE Users 6
1.1.2 Devices handled by DS Agile SCE 6
1.1.3 DS Agile SCE Components 6
1.1.4 DS Agile SCE Data hierarchy 7
1.1.5 DS Agile SCE Template & Object 8
1.1.6 Database creation process 9
2 GENERAL DESCRIPTION 10
2.1 Launching DS Agile SCE 10
2.2 Leaving DS Agile SCE 10
2.3 DS Agile SCE General Display 11
2.3.1 Title Bar 13
2.3.2 Menu Bar 13
2.3.3 Tool bars 14
2.3.4 Windows 14
2.3.5 Status Bar 20
2.4 Management under Windows XP/Windows 7 uLTIMATE 20
2.4.1 Windowing 20
2.4.2 ToolTip 20
3 DS AGILE SCE DETAILED WINDOWS DESCRIPTION 21

3.1 Tools Bar 21
3.1.1 Common Tools 21
3.1.2 OI Mimic Tools 22
3.1.3 Controller Mimic Tools 23
3.2 Docking a Window 23
3.2.1 Docking Window Management 23
3.2.2 Selecting displayed areas in working window 24
3.2.3 Moving/placing areas into working window area 25
3.3 Navigator 26
3.4 Components List 28
3.5 Attributes List Editor of Object/Template 29
3.6 Database Entries 31
3.6.1 Templates list 31
3.6.2 Templates entry 32
3.6.3 Objects entry 32
3.7 Graphic Area 33
4 DS AGILE SCE MENU COMMAND 34

4.1 File Menu 34
4.1.1 File/New… 36
4.1.2 File/Open… 38
4.1.3 File/Close 40
4.1.4 File/Save 41
4.1.5 File/Save for mandatory upgrade 41
SCE/EN HI/C60 HI-1

Human Interface DS Agile System Configuration Editor
4.1.6 File/Clean & Save 42

4.1.7 File/Create a copy 42
4.1.8 File/Check in… 43
4.1.9 File/Check out 46
4.1.10 File/Check 47
4.1.11 File/Generate… 48
4.1.12 File/Properties 52
4.1.13 File/Exit 52
4.2 Edit Menu 53
4.2.1 Edit/Cut 54
4.2.2 Edit/Copy 55
4.2.3 Edit/Paste 57
4.2.4 Edit/Replace 57
4.2.5 Edit/Delete 57
4.2.6 Edit/Select all 58
4.2.7 Edit/Edit relations 59
4.2.8 Edit/Reach 62
4.2.9 Edit/Search… 64
4.2.10 Edit/Switch Mode 65
4.2.11 Edit Commands available in contextual menu (right click on relevant object) 67
4.3 User Menu 96
4.3.1 User/Change Application 97
4.3.2 User/Administration 99
4.4 Graphic Menu 101
4.4.1 Graphic palettes 102
4.4.2 OI mimic 117
4.4.3 Computer (i.e. controller) mimic 130
4.4.4 Graphic/Utility sub-menu 136
4.5 Workbenches Menu 138
4.5.1 Workbenches/ISaGRAF Edit … 138
4.5.2 Workbenches/ISaGRAF Compile 140
4.5.3 Workbenches/FBD Edit … 140
4.6 Tools Menu 142
4.6.1 Tools/Options 143
4.6.2 Tools/Create Template… 145
4.6.3 Tools/Advanced Search 146
4.6.4 Tools/Languages… 153
4.6.5 Tools/Dictionary… 156
4.7 Data Menu 158
4.7.1 Data/SCE Data/Export, Import sub-menu 159
4.7.2 Data/SCE Data 159
4.7.3 Data/Sce data/Report… 166
4.7.4 Data/External Data/Export FBD 167
4.7.5 Data/SCE Data/Import FBD 174
4.7.6 Data/External data/Export IOMapping… 178
4.7.7 Data/ External data/Export Wiring 181
4.7.8 Data/ External data/Export SCADA 183
4.7.9 Data/IEC61850/Export SCL 184
4.7.10 Data/IEC61850/Import SCD/IID… 186
4.7.11 Data/IEC61850/Manage IED… 189
HI-2 SCE/EN HI/C60

4.7.12 Data/ Upgrade to indexed profile & Data/ Indexed profiles merge 192
4.8 Window 192
4.8.1 Search tool bar 192
5 TRACES WINDOW 195

5.1 Trace saving 195
5.2 Trace Log File Checking 197
SCE/EN HI/C60 HI-3

HI-4 SCE/EN HI/C60


This document describes all User Interface or Human Machine Interface of the SCE engineering tool.
1.1 USING DS AGILE SCE

DS Agile System Configuration Editor is a tool that:
 Helps in definition/edition of all system data with its equipment.

 Generates each piece of DS Agile equipment databases.
At first, the data definition is done by experts through templates or models of data. These templates are
then stored and delivered in DS Agile SCE libraries.
In a second time, the models can be loaded and instantiated as a clever kind of duplication to create object
data customised to the application case.
In a third time users can makes modification on its object database.
When all data of the concrete case are defined, the DS Agile SCE generates a coherent set of databases,
named system databag, which can be loaded into each system item of equipment by DS Agile SMT, the
DS Agile maintenance tools.
DS Agile SCE can export/import XML files to/from external tools and generate reports.
Interface
files
Data Model
External tools
Xml files
CMT C26x
ISaGRAF
fully integrated SCE SMT OI
workbenches
System
FBD databag
Gateway
Equipment
Simulator
Template Configuration
libraries S0478ENb
Figure 1: DS Agile SCE data flow
SCE/EN HI/C60 HI-5

1.1.1 DS AGILE SCE USERS

This brief definition of DS Agile SCE using shows several kind of user:
 Expert template developers who maintain a set of libraries adapted to specified equipment, a protocol
mapping, a graphical representation, or an electric automation…
 Prototypes engineers who should build quickly the draft of a specific substation with its devices, its
main functionality and graphic views, in order to evaluate implementation solutions.
 Configuration engineers, who customise, detail and update all structured data of a specified
application case, and generate the databases downloaded to the system devices.
 Maintenance technicians who need to modify or adjust parameters prior of new database download.
Such categories is only an outline of DS Agile SCE users since several of its tools thanks to specific editors,
or report managers, can provide the records needed by other tasks: commissioning cubicle, mapping
extraction, …
Because of these different users, DS Agile SCE has several “levels” in its HMI interface. This manual
describes all of them whatever could be option or license limitations.
The projection of these user categories on DS Agile SCE is not implemented.
1.1.2 DEVICES HANDLED BY DS AGILE SCE

DS Agile is designed to generate a database for DS Agile devices:
 DS Agile OI, the Operator Interface

 DS Agile SMT, the System Management Tool that downloads Databases
 DS Agile Gateway, the separate Gateway or Tele-control Interface to SCADA
 DS Agile C26x control unit
To generate any equipment database, the DS Agile SCE manages:
 Inner data of the device itself (structure and parameters values)

 Exchange data of the device with other system devices
 Exchange data of the device with non system devices
With the 3rd case, the DS Agile SCE manages the communication with all non-DS Agile devices with
typically IED or protection devices on Legacy BUS or system network bus. It is only by the configuration of
communication mapping that DS Agile SCE can handle non-DS Agile devices. DS Agile SCE does not
generate databases or settings for these non-DS Agile devices.
1.1.3 DS AGILE SCE COMPONENTS

Like most configuration tools, the DS Agile SCE is composed of two main software parts with:
 HMI (Human Machine Interface) of DS Agile SCE and associate tools

 Data Model that includes association rules, attributes range, and generators.
The aim of this part is the description of Human Machine interfaces. For a full description of the data model
and its use, refer to chapters Application of each DS Agile device. Nevertheless, a good understanding of
the user interface needs at least the few notions expressed below.
HI-6 SCE/EN HI/C60

1.1.4 DS AGILE SCE DATA HIERARCHY

First of all, Data Model defines structure and structured data. Any piece of information belongs to a
hierarchy of information often referenced from browsing point of view as a tree. This abstraction of data is
named object.
In DS Agile SCE all data belong to only one of the three following tree structures:
 Electric process.
 System (device characteristics and communication).
 Graphic definition of Operator Interface with Archives, Graphic, Printing…
Figure 2: DS Agile SCE Data Hierarchy
In the other hand, the piece of information is structured data, with list of attributes. For example, C26x
object has a set of configurable attributes like TCP/IP address or network name.
SCE/EN HI/C60 HI-7

Figure 3: Attributes of a C26x
1.1.5 DS AGILE SCE TEMPLATE & OBJECT

All data are defined in data model structure. In DS Agile SCE, this notion is fully exploited with the possibility
for a user to create models called templates. Models are duplicated and modified for concrete cases called
Object database. This last one is used to generate all DS Agile devices databags.
DS Agile SCE is then composed of two parts:
 template part,
 object part.
The template part is a list of separate models used or not. A model has its own hierarchy data, with
process, system and/or graphic data.
Figure 4: Object Model / Template
The template is used as a model to create new data in object part. The data which come from a template
are linked to this template. When template is modified, these modifications are propagated to all its linked
objects.
At any moment, user can switch between Template and Object parts using the icon .
Current mode Template or Object is always displayed (right of state Bar).
HI-8 SCE/EN HI/C60

Access to Template functions is only possible for Level 3 and 4 users.
1.1.6 DATABASE CREATION PROCESS

To create the database downloaded to system devices, the common way is to:
1 Import a template from an external library into current database (in its template area)
2 Customise the template if needed in database template area
3 Instantiate the template from template to Object part of the database
4 Modify predefined attribute(s) known as Degree Of Freedom, for example the name.
5 Generate devices databases
It is recommended to work as much as possible with template and to keep the link between template and
instantiated object. Nevertheless, this relation can be broken for deep object modifications. This broken link
operation should remain an exception.
During all this creation process, the DS Agile SCE makes control in data consistency with its “Data Model”.
The checks are made with templates and objects. They are done on:
 Attribute input
 Relation creation
 Generation
Note: Use of templates is not mandatory. A database could be configured with no template, directly with objects.
SCE/EN HI/C60 HI-9

2 GENERAL DESCRIPTION
For installation, please refer to the chapter SCE/EN IN and SCE/EN AJ.
2.1 LAUNCHING DS AGILE SCE

As a Windows application, DS Agile SCE can be started for example by:
1 Desktop shortcut:
2 Windows Explorer selection
3 Start | Run option and browsing to DS Agile SCE
4 Start | All Programs | Alstom | DCS | Configuration Editor X.Y/ SCE
2.2 LEAVING DS AGILE SCE

To stop DS Agile SCE, use the File/Exit option.
HI-10 SCE/EN HI/C60

2.3 DS AGILE SCE GENERAL DISPLAY

At initial start-up or after installation of new version, the DS Agile SCE application display can be seen as
represented below (as far as user has all DS Agile SCE rights and licences). It should be noticed that all
parts are not necessary needed for all kinds of user.
Figure 5: DS Agile SCE Display at start-up
The starting view is empty. Explanation of each area is given below with some information on it. For
displaying information it is needed to load an example or delivered database. This loading explained in detail
later is done.
Menu bar: File/Open and classic window search of a database.
SCE/EN HI/C60 HI-11

After loading a database, the DS Agile SCE application looks like this in navigator perspective:
Figure 6: Navigator perspective with a loaded database
The display is composed of 5 areas:
 Title Bar
 Menu Bar
 Tool Bar
 Object view
 Set of optional windows, displayed as a mosaic of docked (last figure)/floating window or a cascade:
 Main/Second Template
 Objects/Templates entry
 Template/Object Navigator
 Contents (of selected item in Navigator)
 Attributes (of selected Item in Navigator)
 Graphic area
 Profiles table
HI-12 SCE/EN HI/C60

 Wiring table
 Traces list
 Check list
 Report viewer
 Status Bar
2.3.1 TITLE BAR
Figure 7: Title bar
This Title bar provides:

 the name of the product DS Agile Configurator synonym of System Configuration Editor
 the full file name of the active database (including its path)
 as an option if database is read only
On the right of title bar are displayed three window standard buttons
Set application as icon in Window Task Bar
Maximise/minimize application windows
Close/Exit the application

When the DS Agile SCE window is minimised its size remain unchanged, covering fully the screen. Resizing
corners and hedges are usually hidden by Windows Application Bars. To resize the minimised DS Agile SCE
window, it is needed to select the title bar and move it. It is then possible to select window border for a resize
operation.
2.3.2 MENU BAR

The menu bar is composed of 8 Sub-Menus described in detail in next chapter
Figure 8: Menu Bar
File All Files operations including generation

Edit All Edition operations
User DS Agile SCE access control right management
Graphic All graphical actions (done in Graphic Area)
Workbenches All relations with ISaGRAF and FBD editors
Tools DS Agile SCE parameters
Data DS Agile SCE internal tools
Window All DS Agile SCE work areas management
Help Release number
SCE/EN HI/C60 HI-13

2.3.3 TOOL BARS

Three tool bars are available. They could be independently displayed and positioned.
The tool bars display is managed by Menu/Window/Common, OI mimic and Computer (controller) mimic
Toolbar.
Figure 9: Common, OI Mimic and Computer (Controller) Mimics Tool Bars
2.3.4 WINDOWS
Areas are viewers driven by:
 Navigator perspective Tree Viewer: presents a hierarchical view of the configuration. Three roots are
defined: electric (Site), system (Scs) and graphic. Its behaviour is the same as the left part of an
explorer.
Figure 10: Navigator
HI-14 SCE/EN HI/C60

 OI Mimic Editor: this editor is displayed in the graphic area and is used to edit the OI mimics.
Figure 11: OI Mimic Editor
SCE/EN HI/C60 HI-15

 Controller Mimic Editor: this editor is displayed in the graphic area and is used to edit the bay mimic
of C26x HMI.
Figure 12: Controller Mimic Editor
HI-16 SCE/EN HI/C60

 Bitmap Editor: this editor is displayed in the graphic area and allows editing the bitmap file which is
used during Controller mimic edition. The bitmaps are stored in a bitmap table.
Figure 13: Bitmap editor
 Template navigator: presents the list of all templates defined in the current configuration database.
Figure 14: Template list
SCE/EN HI/C60 HI-17

When selecting object (click, enter) all viewers are “refreshed” with corresponding data:
 Template Entry List: views the existing templates which can be added under the selected object
Figure 15: Template entry LIST
 Object Entry List: displays the list of objects which can be added under the selected object. This list
is presented in a tree view: for example: all boards which can be added under a C26x are presented
under a folder named Board. The content of this view depends on existing objects under the selected
object: if the maximum number of cards with a specific type is reached, this kind of card is deleted
from this helper view.
Figure 16: Object entry window associated to a controller
HI-18 SCE/EN HI/C60

 Components List: objects/relations under selected object. Its behaviour is the same than the right
part of a window explorer.
Figure 17: Components list
 Attributes List: the configurable attributes of the selected object.
Figure 18: Attributes of an object
SCE/EN HI/C60 HI-19

2.3.5 STATUS BAR

At the bottom of the screen, is displayed a set of information relative to Alstom DS Agile SCE Application run
time messages.
Figure 19: State Bar
With 4 contextual labels from left to right:

1 DS Agile SCE Application run time message or selected Object/Template name and type.
2 Read/Write property of the object.
3 Object / Template mode.
4 Coordinates of cursor in the OI or Controller Mimic editor.
2.4 MANAGEMENT UNDER WINDOWS XP/WINDOWS 7 ULTIMATE
2.4.1 WINDOWING
The DS Agile SCE application follows windowing behaviour. As presented before it has all options to set as
an icon, maximise/minimise, or close/exit.
Each internal window (included tool bar) is managed with the following dock/float window features:
 dock window anywhere,

 window can be fixed in the screen,
 change dock/float states by double clicking,
 window can be either attached to or detached from the tabbed components,
 save and load dock/float states when user exits and enters in the DS Agile SCE Application.
When window is minimised it can be resized by its border or corner, and displaced by dragging of title bar.
This behaviour is also down with sub windows.
2.4.2 TOOLTIP
When mouse pointer remains on tool bar icon or menu, a tool tip appears with a short message explaining
the function.
HI-20 SCE/EN HI/C60

3 DS AGILE SCE DETAILED WINDOWS DESCRIPTION
3.1 TOOLS BAR

The tool bar can have separate groups of tools displayed by Menu/Windows/Tools option. The associated
functions are detailed in following chapter.
3.1.1 COMMON TOOLS

Set of statistically most commonly used control (also defined in menu bar)
Figure 20: Common Tool Bar
Switch between Template and Object Mode

New File Database or Library
Open Database or Library
Save current File (Database or Library)
Cut Selected Object/Template
Copy Selected Object/Template
Paste/Duplicate Selected Object/Template
Delete Selected Object/Template
Add Mimic Editor Area into Dock window
Reset the default perspective of Dock / Float windows
Switch Dock window focus on Navigator Perspective
Switch Dock window focus on Graphical Perspective
Show/Hide the grid
Zoom +
Zoom -
Anti-aliasing effect
Undo
Redo
SCE/EN HI/C60 HI-21

3.1.2 OI MIMIC TOOLS

Set of statistically most commonly used graphic control (also defined in menu bar) for OI Mimic graphical
editor.
Figure 21: OI mimic graphical editor tool bar
Create a line
Create a rectangle
Create a circle
Create a polyline
Create a text
Create a variable text
Create a memo icon
Create an image
Group edition
Exit group edition
Group Selected Graphic Objects
Ungroup Graphic group object
Rotation 90°
Flip
Mirror
Graphic Object at Bottom plane
Graphic Object at Backward plane
Graphic Object at Forward plane
Graphic Object at Top plane

Scrolling list of alignment functions
Scrolling control
Align Horizontal Top
Align Horizontal Centre
Align Horizontal Bottom
Align Horizontal Side by Side
Align Vertical Left
Align Vertical Centre
Align Vertical Right
Align Vertical Side by Side
HI-22 SCE/EN HI/C60

3.1.3 CONTROLLER MIMIC TOOLS

Set of statistically most commonly used graphic control (also defined in menu bar) for Controller Mimic
graphical editor.
Figure 22: DS Agile C26x Mimic Editor tool bar
Create an horizontal line
Create a vertical line
Create a text
Insert a bitmap
Create a module
Create a transformer module
Module edition
Exit module edition
3.2 DOCKING a WINDOW
3.2.1 DOCKING WINDOW MANAGEMENT

The main working area uses a display principle called docking. It is made for flexible management of
several sub-areas
 inserted with dependency in the docking window or

 in a separate window.
A docked area supports any kind of editor: tree browser, list, graphic, As window sub-object, area can be
resized by its edge, moved by its title bar, or closed by the cross on upper right corner.
When the docked area is a separate window, it is handled like any window and can be dragged to separate
screen display (when PC has multiple screens), or on extended virtual desktop part. The separated window
remains over its parent DS Agile SCE application window, like a more known pop-up. This window can not
be set in icon.
When the docked area remains in dock window, its size is adjusted to other docked area and especially a
main docked area. The main docked area is selected in the Window Menu. It is proposed the object/template
navigator perspective or the graphical area perspective which supports all graphical editors. All other
docked areas are automatically adjusted from this first area.
An area could be pinned or not: if it is pinned, its view is permanent, if it is not pinned; the area is displayed
only when the mouse points on it.
An area could be attached to or detached from the tabbed components: several areas are displayed on the
same window, the user works on each area through its tab button.
SCE/EN HI/C60 HI-23

3.2.2 SELECTING DISPLAYED AREAS IN WORKING WINDOW

The menu bar in sub menu Windows helps to select or deselect the areas seen in working window area.
When an item is clicked, a tilde appears before all activated area. Another click deselects the given area
from the working window area.
Figure 23: Available areas
Area unselecting can be done also by a click on its cross on upper right corner, except for the main area
(navigator or graphic editor).
HI-24 SCE/EN HI/C60

3.2.3 MOVING/PLACING AREAS INTO WORKING WINDOW AREA

The size of the DS Agile SCE application determines the size of its inner docking windows.
Most of the time, DS Agile SCE window is maximised. When new docking areas are added by menu bar,
they are displayed as “docked”, in the docking window, at default location. Then all docked areas are
resized.
Working with DS Agile SCE, a user may need to:
 resize docked area or

 modify docked position relatively one to others.
To resize docked area without changing disposition of areas, a mouse click on border or edge allows a
resizing of this area in horizontal or vertical direction. As docking window size is then fixed, other docked
areas are then resized in same directions.
To modify the area disposition or how they are placed relatively one to the other, the user has to click on
one area header. Since a rectangle appears. While still right mouse pressed, the rectangle representing area
can be dragged. This control rectangle can change in shape or colour.
If mouse pointer is released when control rectangle is still blue, the moved area while be dropped in docking
window. If the key is release when rectangle is grey, the moved area becomes a moveable window out of
dock window and DS Agile SCE main window.
If control rectangle is blue and dragged to the boundary of docked area it changes its shape. New shape is
still rectangle but different sizing, square, flat vertical or flat horizontal. The new shape in blue is a “proposal”
new positioning of the moved area into the docking window, relatively to other docked areas. A key release
drops then the moved area in new relative position in docking window.
It is possible at any moment to get back the default configuration of windows by select Reset Perspective
item in Window menu.
SCE/EN HI/C60 HI-25

3.3 NAVIGATOR
It is the main window to select template/object. It is the central area in docking window management (like
also graphic area) when the Navigator Perspective (Windows menu) has been chosen. This area should
not then become a stand-alone window.
Figure 24: Object view in Navigator perspective
In any case the main interest is on the selected object (here the object Substation is in grey background).
All other docked area refers to this object.
The navigator has a panel at its top to browse into the list of the last visited objects.
There are seven buttons which have the following functions:
Favourite: reaches to the favourite object, if it is defined. The combo list allows to visualise the path of the
favourite object and to set a new one
Back: reaches to the previous selected object, if it is defined. The combo list allows to visualise the complete
list of the previous visited objects and to select one of them
Forward: reaches to the next selected object, if it is defined. The combo list allows to visualise the complete
list of the next visited objects and to select one of them
Collapse sub tree: collapses the current selected object and all components of this object. Allow to free
memory used by its components
Sort: sorts all short names of the children components of the selected object with alphabetic order
This button is used to toggle the last sub-trees that have been viewed.
HI-26 SCE/EN HI/C60

Favourite: reaches to the favourite object, if it is defined. The combo list allows to visualise the path of the
favourite object and to set a new one
Click this button to display the following submenu:
1st box used to show (when selected) / hide (when unselected) the complete relations
2nd box used to show (when selected)/ hide (when unselected) uncompleted relations
3rd box used to show (when selected) / hide (when unselected) the spare objects or spare templates
These buttons are used in all tree representations of Alstom DS Agile SCE; with the same behaviour. This
behaviour is not re-defined elsewhere in this document.
The navigator is a standard tree viewer allowing with + and – to expand, reduce browsing of object
components.
Icon indicates properties of objects.
They are different in template or object mode.
Icons Database Properties
Template Main Electric Parent
Template Main System Parent
Template Main Graphic Parent
Both Configurable component
Both Folder or Binder
Both Template Anchor (Parameter)
Both Template Instance Anchor (Parameter)
Both Template root

Both Complete or Full Filled Relation
Both Incomplete Relation
Both Complete and Fixed Relation
Relation representation is defined via toggle buttons, and . Theses buttons allows to filter or to display
relations on navigator.
A double click on an object expands it.
In navigator and content window, the labels of Spare objects are greyed and italic. For sparing an object, set
the Object attribute spare to Yes.
SCE/EN HI/C60 HI-27

3.4 COMPONENTS LIST
Figure 25: Components List Viewer
The components list gives the same sub-object that navigator expands. But it provides two other columns
with the object type, and object description.
Sorting can be made by Name, Type or Description by clicking on header.
Relations, content drawings are the same that navigator, with same visibility rules. The behaviour of mouse
operation is the same. A click on an object changes focus. A double click on a relation opens the Relation
link editor dialog box..
Figure 26: Relation link editor
HI-28 SCE/EN HI/C60

3.5 ATTRIBUTES LIST EDITOR OF OBJECT/TEMPLATE

Attributes are displayed in the editor as a table. Attributes are organised in categories (different tables with
tabs) and sub-categories (different separators within a table).
Figure 27: Attributes list editor
Relation attributes are displayed as normal attributes in a tab Relation. The path of linked object is also
displayed as an attribute in a category Relation. If the relation is filled (i.e. the link is defined), the attributes
of linked object are also displayed and editable while the relation edition. This allows minimizing the
navigation between objects.
Figure 28: Relation attributes list editor
If the relation is filled (i.e. the link is defined), the attributes of linked object are also displayed and editable
while the relation edition. This allows minimizing the navigation between objects.
SCE/EN HI/C60 HI-29

Figure 29: Relation attributes of a linked object
Attribute value modification is done by selecting a value in a list, or by double-clicking in the field to edit.
The value representation is different for:
 Attribute not linked to a template:

 Read/write: white,
 Read-only: greyed.
 Attribute linked to a template:

 Read/write: white, its short name font colour is blue in the template mode,
 Read-only: greyed.
Parameters are displayed as attributes in the Parameter category.
Figure 30: Parameters list editor
HI-30 SCE/EN HI/C60

The contextual menus, available with a right click, are:
 Cut: initiate the Cut action

 Copy: initiate the Copy action
 Paste: initiate the Paste action
 View linked attributes
3.6 DATABASE ENTRIES

The Database entry is composed of three areas whose purposes are different in the cases listed below.
3.6.1 TEMPLATES LIST

The Templates list contains all templates that are in the opened database(s).
The main database is the first opened database. It can be opened in update mode (work version) or read-
only mode (referenced version).
Figure 31: Template list area
The second database is the 2nd opened database. It is mandatory opened in read-only mode. The System
allows opening the 2nd database only if the main one is opened in update mode.
Figure 32: Template list area with a second opened database
These templates are split in two tabbed panes, one for main database, and other for second database. If
only main database is opened, the second tabbed pane is not visible. The tabbed panes have a ToolTip
which give the name of opened database.
SCE/EN HI/C60 HI-31

The Templates list and Templates entry are defined as a flat list of templates. The list root is specialised for
the Templates Lists and the Templates entry (contains the type of the object/template selected in the
Navigator).
The list is organised as follows:
 Electrical, then System, then Graphical templates.

 Alphabetical order on Anchor template type.
 Alphabetical order on Anchor template short name.
The list root ToolTip contains the name of the corresponding database (main database in Main Template
List, second database in Second Template List).
This area is used to:
 Select a template to edit, in template mode,

 Transfer a template from 2nd database to the main one: the template must be selected from 2nd
database templates list. On this template a contextual menu Add allows to copy this template to the
main one. The template is added into main database templates list.
3.6.2 TEMPLATES ENTRY

The Templates entry contains the templates that can be added as a child of the selected element in the
Navigator. It is therefore a contextual area.
A contextual menu item allows to add the current template under the current selected object from the
navigator. Hereafter, an example of a templates entry area.
Figure 33: Template entry area
It represents all templates which can be added under a voltage level. This voltage level is the selected object
in the Navigator view.
3.6.3 OBJECTS ENTRY

The Objects entry contains the types (objects/templates and relations) that can be added as a child of the
selected element in the Navigator. It is therefore a contextual area. These types are displayed as a tree, and
organised with abstract types.
A contextual menu item allows to create an object with the selected type under the current selected object
from the navigator.
Hereafter, an example of an objects entry area for a voltage level object represents all objects which can be
added under a voltage level. This voltage level is the selected object in the Navigator view.
HI-32 SCE/EN HI/C60

Figure 34: Object entry area
3.7 GRAPHIC AREA

This graphic area is represented by a moveable window.
It is the central area in docking window management (like also Navigator) when Graphic Perspective
(Windows menu) has been chosen.
It can receive various editors in according to the selected object in the Navigator and the selected attribute
in the attributes editor.
 As all objects, the graphic objects can be manipulated from the Navigator. Nevertheless, the graphic
editor is helpful to create graphic objects, by showing a graphical representation of the objects.
Currently, the available editors are:
 OI Mimic Editor: to build the OI Mimics used by the operator interface,

 Controller Mimic Editor: to build the Controller Mimics used by the DS Agile C26x's front panel HMI.
 Bitmap Editor: to build the bitmaps also used by the DS Agile C26x's front panel HMI.
 A complete description of these editors is given in section 4.4 Graphic menu.
SCE/EN HI/C60 HI-33

4 DS AGILE SCE MENU COMMAND

All Alstom DS Agile SCE actions are available through the menu bar items and/or contextual menu items.
Availability of theses items is contextual. For example, Edit/Paste is enabled if an object has been cut/copy
before and a potential parent object has been selected in navigator. Theses conditions are described for
each action.
4.1 FILE MENU
Figure 35: File Menu
A database is either a configuration database or a library database. A configuration database contains

templates and a configuration which uses theses templates. A library contains only templates.
Database could have some different storing format:
 a compressed file: the database is a compressed file that contains all files of the database.
 a sub tree directory: the database is a directory and its files sub tree.
The storing format of a database is indicated by its file/directory extension. e.g.:
 .mpc: database configuration file

 .mpl: database library file
 .dpc: database configuration directory
 .dpl: database library directory
Each database is composed of several versions: a working version and some referenced versions. The
working version can be updated (read and write), whereas referenced versions are frozen (read only). A
Check In mechanism is used to reference the working version: it becomes a referenced version. A Check
Out mechanism is used to transfer a referenced version to the working version.
HI-34 SCE/EN HI/C60

No more than two databases can be opened simultaneously in the Alstom DS Agile SCE:
 The first opened database is the main database. It can be the working version (opened in update
mode) or a referenced version (opened in read-only mode).
 The second opened database is the second database. It can be opened only if the main database is
the working version. It can be the working version or a referenced version (both opened in read-only
mode). This second database is only used to transfer template from a database to the main database.
This second database could be a configuration database or a library database. In both case, only the
template part of this database is used to transfer some template from second database to the main
database.
The item of menu file applies only to the main database, except the Open and Close actions that may also
apply to the second database:
second db is opened in the save action is

readonly mode. applied on t he MAIN db
It could be a working or and not on the second
frozen version db (opened in readonly
mode)
only save the main
db : the working
version
save
only working
version before ALL save
a working db and a
action (on the
second db are opened
working version), a
no database backup copy is
open RW save
(db) is opened open done.
close close only t he

a working db second db
is opened
new
creat e a new db,

if t he db has been
and an initial
updated, a save action
version : a working
is applied after
version
operator confirmation,
then the main db is
frozen open R close the closed.
version main db
close
no database
a referenced db close (db) is opened
is opened
S0211ENa
Figure 36: Main / second databases
The naming rule of database is the following:
Referenced version is a file/directory with indices: v.r[.m]. e.g.:

databaseName.1.1.3.mpc
indices range is 0..99,
third index (m) is optional and is used for partial generation use case.
database name contains any alphabetic or numeric character or “_” or “-“. Blank character is forbidden. This rule must
be applied for database path also.
SCE/EN HI/C60 HI-35

Work version of the configuration has no indices.

databaseName.mpc
4.1.1 FILE/NEW…
Purpose:
 Create a new working library(.mpl, .dpl) or configuration database (.mpc, .dpc)

Availability:
 No database loaded, or no working database.

Other call:
 Shortcut: Ctrl+N
 Toolbar
Operating:
 The action is available from start-up or if all loaded database have been closed. After this new action it
is possible to open second database to pick-up data/templates.
4.1.1.1 CREATE A NEW DS AGILE CONFIGURATION.
 Before creation, the default application type DS Agile must be set. Then the present HMI is kept: a
file chooser appears.
Figure 37: File/New database
1 Browse the drive and directories selections to define where to store new file or directory
HI-36 SCE/EN HI/C60

2 Enter a name for the New database in “File Name” area

3 Select the kind of database in “File Type” area with: mpc for configuration, or mpl for library
4 Validate by clicking the New button or enter in “file name” area
A first working file or directory is created. An empty working database is available under DS Agile SCE
interface.
With previous naming rules, the name is free, but a good practice is to put DS Agile SCE software
version at the beginning.
Example: 04_71_myDb.mpc
Path of database must contain only alphabetic or numeric character or “_” character or “-“ character.
If the given name is wrong a warning message is displayed:
Figure 38: Wrong file name format
4.1.1.2 CREATE A NEW C26X-STANDALONE CONFIGURATION.

A C26x-Standalone can be now configured with SCE. C26x-Standalone application type must be used.
When you use the SCE to create a configuration Standalone, the SCE hide automatically some actions,
functions and data of Alstom DS Agile.
The application type C26x-Standalone allows you to:
 In the electric part :

 create only generic and transformer bays or modules,
 create FBD and slow automations
 In the system part :

 create only one C26x controller,
 create all boards except for TMU2xx,
 create SCADA protocols (Modbus, T101, T104, HNZ),
 create legacy networks with protocols (Modbus, T101, T103, T104)
In the graphic part :
 create controller workspaces with bay mimics,
 use the bitmap table.
Use of File/New. When default application type is Standalone, a creation wizard appears and helps user
to create this new database: from scratch or from S9R file.
SCE/EN HI/C60 HI-37

4.1.2 FILE/OPEN…
Purpose:
 Open an existing library/configuration database as main or second database. If no database already

opens, it opens a main working database. If a work database is already opened, a second database is
opened in read only, for copy of object to the working database.
Availability:
 Only two databases can be opened simultaneously

Other call:
 Shortcut: Ctrl+O
 Toolbar
HI-38 SCE/EN HI/C60

Operating:
 The action is available from start-up, or when a main database is already defined. A pops up appears
for selecting the database.
Figure 39: File/Open database
1 Browse directories to select the file to load with drive selection and directories
2 Select a filter with the kind of database in “File Type” area with: mpc for configuration, or mpl for library
3 Click on file name or enter the name of the database to load in “File Name” area
4 Check comments in write panel
5 Validate the selected file by clicking the Open button
The database is opened in a temporary directory (.mpx). By default, this temporary directory is an
uncompressed copy of database that is created under the directory where the database is stored.
This directory where this temporary directory is created could be set explicitly via two DS Agile SCE settings
(tools/option).
The temporary directory could be directly the directory of database. This option is set by a DS Agile SCE
setting (tools/option) and is available for directory database format (.dpc, .dpl) only.
The read/write mode is displayed in title bar.
SCE/EN HI/C60 HI-39

When DS Agile SCE reads the open database, it checks with which DS Agile SCE version it has been
saved. If the DS Agile SCE version was older, then some upgrades can be necessary: for example, adding
a new attribute to an object, modifying the cardinality of an object, etc. In this case, the following dialog box
is displayed:
Figure 40: File/open with database conversion
If answer is “Yes”, then database is automatically upgraded to the new DS Agile SCE data model. This
upgrading is available only for a working version.
The upgrading process could be more complex, especially when new structure of databases is incompatible
with the structure of database to open. In this case, the database must be saved with a special command:
“prepare upgrade & save”. Then opening this kind of database is available.
4.1.2.1 OPEN A DATABASE WITHOUT APPLICATION TYPE

When user opens a database from an old version which hasn’t application type, the SCE determine
automatically which application type has to be used.i.e (DS Agile or C26x-Standalone)
The two application types are computed by searching specific objects in database, with following rules:
 If database contain only one computer without IEC mapping in object part, and no IEC mapping in
template part the application type is set to C26x-Standalone.
 If database is not C26x-Standalone, it is DS Agile.
4.1.3 FILE/CLOSE
Purpose:
 Close opened library/configuration database as main or second database.

Availability:
 when a database has been opened.

Other call:
 Main window close button
HI-40 SCE/EN HI/C60

Operating:
 The name of the database is already defined from Open/New. If main database is a working database
and some modifications have been done, it asks to Save the database:
Figure 41: File/Close Asking for save work database
 If a second database is opened, it’s closed and the working database is still opened.
4.1.4 FILE/SAVE
Purpose:
 Save the working opened library/configuration database. Second database can not be modified and
does not need a save action.
Availability:
 Only the working version of a database (read/write) can be saved

Other call:
 Shortcut: Ctrl+S
 Toolbar
 Main window close button if database has been modified
Operating:
 Only the working version of a database (read/write) can be saved
4.1.5 FILE/SAVE FOR MANDATORY UPGRADE

Purpose:
 Save the main opened library/configuration database and put into the database file an xml form of the
database. This xml form could be used during opening operation if the structure of the data model has
been changed (see File/ Open)
Availability:
 Only the working version of a database (read/write) can be saved with this option
Other call:
 None
Operating:
 An xml backup of the database is done. This xml backup is stored in .mpc file.
SCE/EN HI/C60 HI-41

4.1.6 FILE/CLEAN & SAVE

Purpose:
 Compact the main opened library/configuration database and save it. The compaction consists to
delete the space not used in database file: when an object is deleted, its space is not freed.
Availability:
 Only the working version of a database (read/write) can be cleaned and saved.
Other call:
 None
Operating:
 An xml backup of the database is done. This xml backup is stored in .mpc file.
4.1.7 FILE/CREATE A COPY

Purpose:
 Copy the main library/configuration database into a new database.

Availability:
 Always
Other call:
 None
Operating:
 The action starts a pop-up to enter new file name where is stored the copy and eventually modify the
store format of the database (.mpc <> .dpc or .mpl <> .dpl):
HI-42 SCE/EN HI/C60

Figure 42: Copy file chooser
 The current database remains the same and needs to be saved later if modifications have been done.
To switch to the database copy, it is needed to save and close the main database, then open the
copied database.
4.1.8 FILE/CHECK IN…

Purpose:
 Save the current working database (template or configuration) in a referenced file version. The
working database is not saved but only copied. The “check in” file is named like work database with
increment of database version. Check in file is then read only from Alstom DS Agile SCE until a check
out.
SCE/EN HI/C60 HI-43

save A s action allows to

copy of a db version in a
new db and the working
A frozen
version of this new db.
version
save As
checkin MULTIPLE
save, save As
version are
available
THE working checkout

version
only ONE vorking version for a

db : so some warning are done
during checkin/checkout
operat ion t o prevent some data
crash.
S0209ENa
Figure 43: Check in / check out mechanism
Availability:
 Only with working version of a database

Other call:
 None
HI-44 SCE/EN HI/C60

Operating:
Figure 44: File/Check In working database
1 Select new reference identifier

2 Write comments
3 Confirm check-in by clicking the OK button
A pop-up window asks for identifier increment with major or minor evolution. Alstom DS Agile SCE
computes directly the proposed identifier from current one. In example it starts from 0.0. If current identifier is
3.5 it proposes 3.5.0, 3.6, and 4.0. This reference is added to the file name.
A field text area allows to precise the content or the modification of the version. This comment is stored in
the database file. It is possible at any moment to read it with File/Properties.
A good practice is to keep reference 0.x for development, and 1.x, 2.x for major steps of project life:
prototype, Factory version, site version… Major index modification can be also a consequence of Alstom
DS Agile SCE software evolution.
Three indices versions (for example 3.5.1) are used for partial generation of database: only a subset of
devices are taken into account during device configuration files process (file/generate).
The loaded database is still the working database.
‘Check in’ does not mean Check: a referenced version (with a check in) is not mandatory a full consistent
database (test done with Check operation). An inconsistent database can be referenced but a warning
message is then displayed. During opening operation, if the working version does not come from the latest
referenced version of database, the following warning dialog box is displayed:
SCE/EN HI/C60 HI-45

Figure 45: File/Open and Check In working database
4.1.9 FILE/CHECK OUT

Purpose:
 A referenced database could not be modified (read only). The check out action allows to transform the
referenced database into a working database.
s ave As A frozen
version
s ave As
c hec kin
THE work ing check out

version
myDb.mpc myDb.0.1.mpc
myDb.0.2.mpc
myDb.0.3.mpc
myDb.0.5.mpc
myDb.1.0.mpc
myDb.1.1.mpc
myDb.2.0.mpc
... .
S0210ENa
Figure 46: File/Check Out database, example
Availability:
 Only with loaded referenced version of a database

Other call:
 None
Operating:
 The referenced version is copied into the working version. The previous working version is overwritten.
If the referenced version to check out is not the latest version, a warning dialog box is displayed:
HI-46 SCE/EN HI/C60

Figure 47: File/Check Out warning
4.1.10 FILE/CHECK
Purpose:
 Check the main library/configuration database consistency. The action starts testing on whole
database. The templates and the spared objects are not taken into account by the check function. The
complete definition of errors/warnings is available in chapter SCE/EN MF.
All errors/warnings are displayed in the following table of the Trace panel ("Checks" tab):
Figure 48: Error / Warning check table
Table rows: each row corresponds to one check operation whose result is an error or a warning.
SCE/EN HI/C60 HI-47

Table columns:
 Level: it displays an icon for error or warning.

 Type: it contains the identifier of the check operation displayed in the row.
Example: "DataObjectPhases" is a check consisting in verifying that all the phases under a GenWYE
or GenDELTA DataObject, is linked, through the "has for IEC61850 address" relation, to distinct
Datapoints.
 Reference: for each check operation, an object implicated in the check operation, is considered as the
main object. The column displays the path of this object. If the user activates the "Reach" action on
the row, this object is retrieved in the Alstom DS Agile SCE navigator and selected. This action is also
available with double-click.
 Message: it displays a message explaining the error/warning for the check operation.
 First column: the user can check On/Off this column to remember which error/warning he tried to
correct.
The panel of the Table contains also the following buttons:
 Errors filter toggle button: if this button is selected, the Error traces are not displayed (they are
filtered). Else they are.
 Warnings filter toggle button: if this button is selected, the Warning traces are not displayed (they are
 Info filter toggle button: if this button is selected, the Info traces are not displayed (they are filtered).
Else they are.
 Checked traces filter toggle button: if this button is selected, the Checked traces are not displayed
(they are filtered). Else they are.
Availability:
 For referenced or working version of a database

Other call:
 Shortcut: F6
Operating:
1 Before the beginning of the check, DS Agile SCE clears the Check Traces tab, displays it and
displays a waiting popup
2 During the check computing, DS Agile SCE displays the found errors or warnings in the Check Traces
tab. The number of errors and warning are updated at the top of Check Traces tab
3 After the check, the content of the Check Traces tab is saved in the check.txt file in the folder of the
configuration. This file is a text file. It can be displayed in Microsoft Excel with the file type: Text
(separator: tabulation), or in any text editor.
4 DS Agile SCE notifies that the Configuration Database is modified and has to be saved (check.txt file
and Configuration settings are to be saved).
4.1.11 FILE/GENERATE…
Purpose: Generate from DS Agile SCE current database the equipment database to load into system
devices. This equipment database is a Zip file which is used by the SMT (System Management Tool). It’s
called System Data Bag (*.sdb). There is no software interface between SMT and DS Agile SCE. The
exchanges are done manually with files.
HI-48 SCE/EN HI/C60

This System Data Bag contains all device configuration files which are named Application Data Bags
(*.adb). There’s an Application Data Bag for each equipment configuration to be generated. For each
equipment, there’s also a Maintenance Data Model (*.dm) for SMT to access the equipment through the
Station Bus.
For the simulation application (equipment simulator and process simulator), the application databags are
directly the configuration files of the simulators: .xml for the equipment simulator, .zip for the process
simulator.
SCE generates the setting file (setting.xml) taking into account the protection functions defined in the
configuration. Only the settings corresponding to functions defined in the configuration are generated in the
file.
The XmlSetBuilder in SCE converts this file to a DS Agile S1 readable file.
XmlSetBuilder uses the model.xml file that describes all the parameters of the DS Agile C26x. The format of
this file is described in the PIDD setting .The PIDD setting defines the rules of visibility for parameter. This
document permits SCE to apply those rules.
SCE will generate a databag that contains:
 DS Agile C26x configuration file,

 DS Agile C26x.set file
 DS Agile C26x client.dm files
In the case of protective function, in the SCE, all thresholds are disabled by default and can be modified only
by DS Agile S1 (They are not present in the DB).
In the case of built-in and automatism, the default value of each parameter is defined by the user in the SCE.
It can also be modified by DS Agile S1.
Availability:
 Only for referenced configuration database version. The library database and the working database
version are not available.
 If the referenced configuration has not been consistent (file/check has been done with no error),
File/generate action is not available.
Figure 49: Check Warning for no-consistent or obsolete consistent check
Other call:
 Shortcut: F7
Operating:
1 File/Open a referenced (and check in) version. This means that in common cases, the user may have
to:
 check in its working database,
 notice the check in the new version reference,
 save the working database for future modification,
 close the working database,
SCE/EN HI/C60 HI-49

 open the database with new referenced version.

2 Select File/Generate…
3 A Generation dialog box lists all SBUS devices available on database and allows to select a part or all
of them. The spare devices are not displayed.
4 Only if referenced version has a third index, select the devices. Otherwise all devices are pre-selected.
5 Select the output directory, where the System Data Bag will be generated, with the … button.
6 Click the Run button.
Figure 50: File/Generate Dialog Box
7 The action progression is displayed graphically. This progression can be followed in 3 ways:
8 the progress bar is animated to display the percentage of achievement of the process (the value is a
ratio of number of treated items),
9 the messages displayed on status bar which are specific of each using,
 the nodes of the browser change in function of their processing state to follow processing.
HI-50 SCE/EN HI/C60

Figure 51: File/Generate Progression
At the end of generation the final result of generation is presented.
Figure 52: File/Generate … Successful
Figure 53: File/Generate … Error
A third result is a warning that indicates that some DS Agile C26x configuration files could be too big for
downloading into the DS Agile C26x by the SMT. It is only a warning and the System Data Bag is created.
So, If generation succeeds, the *.zip generated file is to be provided to SMT equipment that download
equipment databases from the .zip
A good practice is to launch a generation only for a checked referenced version which has no
consistency error.
SCE/EN HI/C60 HI-51

4.1.12 FILE/PROPERTIES
Purpose:
 Display all properties of the database:
Figure 54: File/Properties Setting Manager on work database
Only Languages used during File/Generate for OI and C26x localization may be updated. Theses fields may
be also updated through Tools/Languages.
Availability:
 When database has been opened

Other call:
 None
Operating:
 Leave this display by Ok or Cancel. Cancel button restore the previous value of editable field, i.e.
Description.
4.1.13 FILE/EXIT
Purpose:
 Leave DS Agile SCE application

Availability:
 Always
Other call:
 Shortcut: Alt+F4
 Window quit button or double click on title left icon
HI-52 SCE/EN HI/C60

Operating:
 If main database is a working database and some modifications have been done, it asks to Save the
database:
Figure 55: File/Exit and Pending Modified Database
 If answer is Yes, current working database is saved before exit,

 if answer is No, exit DS Agile SCE application with no save,
 if answer is Cancel, cancel exit operation, come back to edition mode.
4.2 EDIT MENU

This menu defines all available items while data edition: a data can be an object, an attribute, a graphic
representation of an object, etc. The edition can occur in the different areas of DS Agile SCE: navigator,
components list, attribute editor, graphical editors, etc.
Most of these items are contextual and don’t appear directly in menu Edit: they are defined by a
contextual menu which depends on the type of selected object. This contextual menu is available with a right
click on the focus element (node of navigator, item of list entry, graphical representation in mimic editor …).
Figure 56: Edit Menu
SCE/EN HI/C60 HI-53

4.2.1 EDIT/CUT
Purpose:
 Cut the selected object/attribute to clipboard. The cut selection is moved to a new parent object.
Availability:
 Context dependent
Other call:
 Shortcut: Ctrl+X
 Toolbar
 Contextual menu (Mouse right click)
Operating:
1 Select the object/attribute to cut and choose cut item. In Navigator, only one object can be selected;
in Components list, multi-selection is available (left click and shift, left click and ctrl).
Figure 57: Edit/Cut
2 The object icon is greyed to indicate that a cut/paste operation is in progress. Any copy or another
cut operation cancels the current cut/paste operation and the object icon is normal again.
HI-54 SCE/EN HI/C60

Figure 58: Edit/Cut result
3 Select the new parent object/attribute where the cut object will be moved and choose paste item. The
cut object is then moved to its new parent. If an object already exists with the same name under the
same parent, the pasted object is renamed with an increment.
Figure 59: Edit/Cut-Paste result
4.2.2 EDIT/COPY
Purpose:
 Copy the selected element to clipboard for further Paste action

Availability:
Other call:
 Shortcut: Ctrl+C
 toolbar
Operating:
1 Select in any area the object (1 left click) or attribute (2 left click) to copy/Paste
SCE/EN HI/C60 HI-55

Figure 60: Edit/Copy
2 Copy the object/attribute

3 Select the object under which, or the attribute to paste
4 Edit/Paste (may be used several times) to paste copied object.
Copy action stores all objects and all hierarchy below it. Copy action tries to keep referenced relations.
Figure 61: Edit/Paste
HI-56 SCE/EN HI/C60

Figure 62: Edit/Copy-Paste result
4.2.3 EDIT/PASTE
Purpose:
 Paste the selected element from clipboard. This clipboard content comes from a cut action or a copy
action. See Edit/Copy and Edit/Cut.
Availability:
Other call:
 Shortcut: Ctrl+V
 Toolbar
Operating:
 Select object under which the paste operation should be done, then paste. Paste can be used several
times after a copy action. It inserts all hierarchy below copied object, all attributes and all relations.
4.2.4 EDIT/REPLACE
Purpose:
 Replace the selected element by the content of the clipboard.

Availability:
 Depending on the selected element and associated conditions

Other call:
 Contextual menu (Mouse right click) in Navigator, Components list, Templates list
4.2.5 EDIT/DELETE
Purpose:
 Delete the selected element: object, template, Unified Template, Parameter…

 A general setting allows confirming or not any delete operation.
SCE/EN HI/C60 HI-57

Figure 63: Edit/Delete Confirmation setting
If this option is set to True, before each delete operation, the following dialog box is displayed:
Figure 64: Edit/Delete Confirmation dialog box
Availability:

Other call:
 Shortcut: Del
 Toolbar
 Contextual menu (Mouse right click) in Navigator, Components list, Templates list
4.2.6 EDIT/SELECT ALL

Purpose:
 Select all graphic objects in graphic viewers (OI Mimic viewer or Controller Mimic viewer).
Availability:
 The graphic viewer must have the focus.
HI-58 SCE/EN HI/C60

Other call:
 Contextual menu of graphic viewer (Mouse right click)

 Shortcut: Ctrl+A.
 Be care: when Navigator has the focus, Ctrl+A moves the current selection to the root.
Operations:
1 Click to the graphic viewer or select a graphic object in the viewer.
2 Choose Select All item: all graphic objects of mimic are selected.
Figure 65: Edit/Select All
4.2.7 EDIT/EDIT RELATIONS

Purpose:
 The relation editor is a dialog providing multiple relations creating with automatic linking with
objects.
Availability:
 Depending on the selected element

Call:
 Contextual menu (Mouse right click) in Navigator, Components List

Operations:
1 Select an object from Navigator or Components list. Choose the Edit relations item.
SCE/EN HI/C60 HI-59

2 This modal dialog box appears:
Figure 66: Relation link editor
On top, the working object is remembered to know where user is working.

On bottom, two buttons: the first allows to apply modification and the other closes dialog box.
Two main parts:
 the relation list which displays all relations available for the selected object,
 the object tree which displays all objects available for the current selected relation.
A relation between two objects has a direction. So, the relation list is composed of two tabbed panes:
 “From” which gives relations for which the working object is the main object,
 “To” which gives relations for which the working object is the second object.
HI-60 SCE/EN HI/C60

"to" relation :
the origin of the
relation is
another objet
linked object working object linked object
"from" relation :
the origin of the
relation is the
working object
Figure 67: Relation Direction
The relation label is the name of the relation, followed by the type of object which could be linked and then,
the cardinality of the relation ([min .. max]).
User can select more than one object by checking check boxes, and when apply modification, it creates one
relation for each new selected object and removes relation with new unselected objects, after controlling the
cardinality.
So, if cardinality is respected by selection, after apply, there’s one relation for each selected object, and no
relation with others.
SCE/EN HI/C60 HI-61

The object tree could be view as an object list:
Figure 68: Relation link editor with objects list
As user could select more than one object, the list provides same check boxes seen in tree view, and four
new icons:
 Uncheck: which uncheck selected objects,
 Check: which check selected objects,
 Uncheck All: which uncheck all objects of the list,
 Check All: which check all objects of the list.
4.2.8 EDIT/REACH
Purpose:
 Go to the linked object

Availability:

Call:

 Shortcut: Ctrl+G
HI-62 SCE/EN HI/C60

Operations:
1 Select relation of an object in Navigator

2 Select Reach item in the contextual menu:
Figure 69: Edit/Reach item
SCE/EN HI/C60 HI-63

3 The tree view is extended to the linked object. The linked object becomes the current object:
Figure 70: Elapse of navigator to the linked object
4.2.9 EDIT/SEARCH…
This menu is no longer available ; it has been replaced with the Quick search and Advanced search in the
Tools menu (see § 4.6.3)
HI-64 SCE/EN HI/C60

4.2.10 EDIT/SWITCH MODE

Purpose:
 Switch between Object mode and Template mode.

Availability:
 Always
Other call:
 Toolbar
Operations:
1 Select switch mode item:
 in Object mode, the navigator displays the complete object configuration and the current selected
object;
Figure 71: Object Mode
 in Template mode, the navigator displays the selected template of Templates list area;
SCE/EN HI/C60 HI-65

Figure 72: Template Mode
 for Template mode and Object mode, the other areas are updated in accordance with the current
selection of the navigator.
2 switch again: the current selection of template or object is saved.
HI-66 SCE/EN HI/C60

4.2.11 EDIT COMMANDS AVAILABLE IN CONTEXTUAL MENU (RIGHT CLICK ON

RELEVANT OBJECT)
4.2.11.1 MOVE
Purpose:
 Move an object. Same behaviour as a sequence cut/paste, with a modal editor. This editor allows to
choose the new parent of the object.
Figure 73: Edit/Move Dialog Box
Availability:

Call:
 Contextual menu (Mouse right click) in Navigator and Components list.
4.2.11.2 REPLACE
Purpose:
 Replace the selected object by the content of the clipboard if objects are compatible
Availability:
Call:
 Shortcut: Ctrl+H
 Contextual menu (Mouse right click) in Navigator and Components list.
4.2.11.3 ADD
Purpose 1:
 In a working database, add the Templates/Objects Entry selected element as a child of the active
Navigator element
SCE/EN HI/C60 HI-67

Purpose 2:
 Add the Second Templates List selected Unified Template to the main database
Availability:
Call:
 Contextual menu (Mouse right click) in Entry helper or Template list area (second database tab)
 Double-click on element to add
Operation 1:
1 Select object in navigator area
2 Select template into template entry or object entry automatically corresponding to navigator selected
object
Figure 74: Edit/Add in Object/Template Entry Area
3 Make Edit/Add or right mouse click or double-click.

4 Added object is put under navigator selected object.
HI-68 SCE/EN HI/C60

Operation 2:
1 Select a template in second database tab in Template list area.
2 Choose Edit/Add or right mouse click or double-click.
Figure 75: Edit/Add in Templates List Area
3 Selected template is copied from template library (second database) to the current database.
4.2.11.4 DUPLICATE
Purpose:
 In Templates list area, duplicate (copy/paste) the selected template.

Availability:
 Template mode is selected.

 Template is selected in Templates list area.
 Database is opened in read/write mode (working database).
Call:
 Contextual menu (Mouse right click) in templates list area

Operation:
1 Select a template in Templates list area.
2 Choose duplicate item. The selected template is cloned in the Templates list.
SCE/EN HI/C60 HI-69

Figure 76: Edit/Duplicate in Templates List Area
HI-70 SCE/EN HI/C60

4.2.11.5 CANONIC FORM

Purpose:
 View an FBD interlock equation in two forms (developed and factorised). It is used to visualise all
the content of the logical equation selected into a normalised view (sum of products) and into the
original view (factorised). See the example below.
 The view is divided in two parts, one to represent the whole automation diagram and one two
represent the developed equations which will be generated to implement the automatism. The
developed equation is displayed in Alstom DS Agile OI when a control is refused because of
interlocks.
 The development of an equation must generate much combinations of operands that can be easily
simplified using basic Morgan rules (e.g.: A AND A = A, A OR A = A, A AND NOT(A) = 0), so the
resulting developed equation can be lighter than the factorised. More, if all the operands are
cancelled, the developed equation displayed is empty, revealing that the original equation contains a
conception mistake.
Figure 77: Edit/Canonic Form
SCE/EN HI/C60 HI-71

Availability:
 on FBD interlock object

Call:

Operating:
1 Select in navigator area under process part, FBD object
2 Select Canonic form item
3 Pop up appears to see two forms of the equation
Equation is shown in factorised (compact) and developed (uniqueness) format in Tree Viewer where each
node replaces the factorisation ( ). Except for NOT, all terms are displayed in list below given operator.
Operators are:
Data Point Input
Not Operator
OR operator
AND Operator
NOR Operator
NAND Operator
XOR Operator
NotXOR Operator
4.2.11.6 BREAK ALL INNER TEMPLATE LINK

Purpose:
 In Object mode, break the link between an object which is an instance of template and this template.
Any template modification does not impact anymore the object. Object attributes and its component
can be modified. If this instance of template contains another instances of template (inner templates),
their template links are also broken.
Availability:
 On an instantiated template
Call:

Operations:
1 Select an object which is an instance of a template. This object must be the root anchor of template:
HI-72 SCE/EN HI/C60

Figure 78: Edit/Break all Inner Template Links
2 Choose Break all inner template link item. A confirmation dialog box appears: this message indicates
that this selected object is concerned by the operation but also the template other components. Click
Yes to continue the operation. Click No to cancel.
Figure 79: Edit/Break Template Link Confirmation
3 The link with its template is broken. Its icon becomes normal object icon. All attributes becomes RW
and its components could be edited: add, remove a component.
SCE/EN HI/C60 HI-73

Figure 80: Edit/All Template Links Have Been Broken
4.2.11.7 BREAK UPPER TEMPLATE LINK

Purpose:
 In Object mode, break the link between an object which is an instance of a template and this template.
Any template modification does not impact anymore the object. Object attributes and its component
can be modified. If this instance of template contains other instances of template (inner templates),
their template links are kept. So only the upper level of template is concerned by this action.
Availability:
 On an instantiated template
Call:

Operations:
1 Select an object which is an instance of a template. This object must be the root anchor of template:
Figure 81: Edit/Break Upper Template Link
HI-74 SCE/EN HI/C60

2 Choose Break upper template link item. A confirmation dialog box is displayed: this message indicates
that this selected object is concerned by the operation but also the others components of the template.
Click on Yes to continue the operation. A click on No cancels the operation.
Figure 82: Edit/Break Template Link Confirmation
The link with its template is broken. Its icon becomes normal object icon. All attributes becomes RW and its
components could be edited: add, remove a component. The inner instances of templates are not updated.
4.2.11.8 VIEW LINKED ATTRIBUTES

Purpose:
 In object mode or template mode, view the linked attributes to a Parameter

Availability:
 An attribute which is linked to a parameter or a parameter must be selected. The parameters of

template are available inside tab Parameters with Attributes Editor when the root anchor of template is
selected in Navigator.
Call:
 Contextual menu (Mouse right click) in Attributes Editor

Operations:
1 Select a parameter or an attribute which is linked to a parameter
SCE/EN HI/C60 HI-75

Figure 83: Edit/View Linked Attributes
2 Choose view linked attributes: all attributes linked to the selected parameter are displayed in the
following dialog box:
Figure 84: Tree of Linked Attributes
3 A list form is available with button:
HI-76 SCE/EN HI/C60

Figure 85: List of Linked Attributes
4 The Reach button allows to elapse the navigator to the selected object and to select in the Attribute
editor the selected attribute.
4.2.11.9 VIEW TEMPLATE INSTANCES

Purpose:
 View the instances of the selected template

Availability:

Call:
 Contextual menu (Mouse right click) in Templates List, Templates Entry.

Operations:
1 Select a template in Templates list area or in Template entry area
SCE/EN HI/C60 HI-77

Figure 86: Edit/View All Instances
2 Choose View template instances item. This dialog box appears:

The content of the tree show all instances of the selected template in template list or template entry. Only
main object of the template are shown and where it’s instantiated.
A list form is available.
Figure 87: Template Instances
HI-78 SCE/EN HI/C60

4.2.11.10 VIEW TEMPLATE CONTENT

Purpose:
 View all components of a template instance. This feature is useful if the template has several
components: graphic, electric or system.
Availability:

Call:

Operations:
1 Select a component of a template instance, the template anchor or any other component of the
template instance:
Figure 88: Edit/View Template Content
2 Choose View template content item. This following dialog box appears:
SCE/EN HI/C60 HI-79

Figure 89: Template Viewing
In tree view:
 template part shows the original template,
 objects part shows all components of the template instance.
The Reach button allows to browser the selected object in Navigator.
An object list view is also available with .
4.2.11.11 CREATE BACKUP

Purpose:
 Create a backup device for a C26x, Gateway or OI IEC 61850-8-1 device: for redundant equipment,
clone the equipment as a backup and associate the created backup to its existing main equipment.
This association is done with a specific relation “has for backup:”.
 Backup equipment is read-only. So, user can’t create, modify or delete any thing inside it. The read
only state is displayed with a different icon, like templates.
 The only possibility of change is system information, like TCP/IP address and network name.
 The cloned information in backup equipment is the system datapoint which can be used in a system
mimic definition to animate the states of the backup.
 A complementary description of this feature is done in chapter AP of DS Agile C26x and Alstom
DS Agile OI.
Availability:

Call:
HI-80 SCE/EN HI/C60

Operations:
1 Select a device that can already be redunded: C26x and OI Server.
2 Choose Create Backup item:
Figure 90: Edit/Create Backup
SCE/EN HI/C60 HI-81

3 The selected equipment is cloned. A new relation between the two devices is created: “is backup of”.
Its components are read-only except its name or network attributes:
Figure 91: Backup Equipment
4.2.11.12 NEW
Purpose 1:
 Create a new Unified Template

Purpose 2:
 Create a new Parameter in the selected Unified Template
HI-82 SCE/EN HI/C60

Availability:

Call:
 Contextual menu (Mouse right click) in Attributes Editor (Parameter tab), Templates List
Operation 1:
1 Only in template mode, select the root of Templates list area and choose New item:
Figure 92: Edit/New Template
2 A new template is created with a default name. Its name will be set after the creation of its first
component: the first created component of a template is the anchor of the template. The name of the
template is the name of its anchor. An anchor is the object from which the template can be
instantiated.
SCE/EN HI/C60 HI-83

Figure 93: A New Template
Operation 2:
1 Only in template mode:
 select a template in Templates list,
 then select the anchor of a template in Navigator,

 then select the parameter tab in Attribute editor. Choose New item:
Figure 94: Edit/New Parameter
2 A new parameter is created with no linked attribute. The name of its parameter can be changed with
a double click on its first column.
HI-84 SCE/EN HI/C60

Figure 95: An Empty Parameter
4.2.11.13 DEFINE
Purpose 1:
 Define a comment available on ToolTip for a template

Purpose 2:
 Define a comment available on ToolTip for a parameter

Availability:

Call:
 Contextual menu (Mouse right click) in Attributes Editor (Parameter tab), Templates List
SCE/EN HI/C60 HI-85

Operation 1:
1 Only in template mode, in Templates list area, select a template and choose define item:
Figure 96: Edit/Define Template
2 A text field editor appears. Type template comment. HTML tags can be used.
Figure 97: Template Definition Editor
HI-86 SCE/EN HI/C60

3 This comment will be displayed as ToolTip in Templates list area.
Figure 98: Template Definition ToolTip
Operation 2:
1 Only in template mode:
 select a template in Templates list,
 then select the anchor of a template in Navigator,

 then select the parameter tab in Attribute editor. Choose Define item:
SCE/EN HI/C60 HI-87

Figure 99: Edit/New Parameter
2 A text field editor appears. Type parameter comment. The HTML tags can be used.
Figure 100: Parameter Definition Editor
3 This comment will be displayed as ToolTip in Attributes editor, tab parameter:
HI-88 SCE/EN HI/C60

Figure 101: Parameter Definition Tooltip
4.2.11.14 ASSOCIATE PARAMETER

Purpose:
 Associate the selected attribute as a new parameter or as an existing parameter.

 A parameter is a link between several attributes. When an element of this set is modified, the other
are also modified. This shortcut allows to modify only one attribute instead of modifying n times with
same value n attributes.
Availability:

Call:

Operations:
1 Select an attribute in Attribute editor, in template Mode only
2 Choose Associate item parameter. This item is enabled if a parameter is available for the selected
attribute:
 an empty parameter with no linked attribute,
 or a parameter already linked to another compatible attribute.
SCE/EN HI/C60 HI-89

Figure 102: Edit/Associate Parameter Item
3 The following dialog box appears. It propose available parameters which can be linked to the selected
attribute.
Figure 103: Link to Parameter Editor
4 After selection of a parameter, click the Ok button. The selected parameter is now linked to the
chosen parameter: any modification of one among them is propagated on the other(s). This
indication appears in the status bar when the attribute is selected. See also EDIT/View linked
attributes to visualise the set of linked parameter and attributes.
HI-90 SCE/EN HI/C60

Figure 104: Linked Parameter
4.2.11.15 DOF STATUS

Purpose:
 Toggle the selected attribute or parameter as a Degree Of Freedom (DOF).

 In that case, in object mode, for the template instance, the target object attribute/parameter value can
be modified even if the object is linked to its template. The font colour of an attribute DOF label is blue
in the template and black in the target object.
Availability:

 Template mode only
Call:

Operations:
1 Select an attribute or a parameter in Attribute editor, in template mode only. If the attribute is linked
to a parameter, the item is not enabled: item is enabled only for the linked parameter.
SCE/EN HI/C60 HI-91

Figure 105: Edit/DOF Status Item
2 Choose DOF Status item. The DOF status of the attribute/parameter is inverted:
Figure 106: Toggle DOF Status
3 In object mode, the DOF attribute/parameter becomes updateable:
Figure 107: Object Mode And DOF Status
HI-92 SCE/EN HI/C60

4.2.11.16 SBUS AUTOMATIC ADDRESSING

Purpose:
 Create automatically the SBUS mapping of a particular SBUS Alstom DS Agile device.
 The creation rules and its limitations are described in chapter AP.
Availability:
 The procedure is available in the contextual menu of DS Agile station bus devices (C26x, Gateway,
OI...), System Group or Ethernet network, only for Object mode.
Call:

Operation:
1 Right-click a DS Agile SBUS device (OI, C26x, Gateway) in the Object view.
2 Select the contextual menu item SBUS Automatic Addressing.
Figure 108: Edit/SBUS Automatic Addressing for SBUS Device
3 The SBUS mapping of the selected device is created or updated according to the DS Agile
IEC 61850-8-1 projection rules.
or
4 Right-click the System Group in the Object view
SCE/EN HI/C60 HI-93

Figure 109: Edit/SBUS Automatic Addressing for Ethernet Object
6 The SBUS mapping of all DS Agile SBUS devices (OI, C26x, Gateway) attached to the System Group
are created or updated according to the DS Agile IEC 61850-8-1 projection rules.
or
7 Right-click the Ethernet network object in the Object view
Figure 110: Edit/SBUS Automatic Addressing for Ethernet Object
HI-94 SCE/EN HI/C60

9 The SBUS mapping of ALL of the DS Agile SBUS devices (OI, C26x, Gateway) in the network are
created or updated according to the DS Agile IEC 61850-8-1 projection rules.
4.2.11.17 AUTO LINK CLIENT SERVER

The Auto link process manages the creation of all relations client/server between all pieces of equipment of
the database. Using the client/server rules of the datapoints (see SCE/EN MF), relations “Has for IEC61850
server” are created under clients equipment and link to their servers. The attribute ‘modelling/goose usage’ is
updated with right value: Data model only, Goose only, or Data model and goose.
The function auto-link is available from the contextual menu by right-clicking Ethernet Network.
4.2.11.18 UNUSED TEMPLATES

Purpose:
 In Templates list area, hide/show templates that are unused at objects level or upper template level.
Availability:

Call:

Operation:
2 Choose Unused templates item. If this item was not previously ticked it is "ticked": the Templates list
contains used and unused templates. If this item was previously ticked it is "unticked": the Templates
list contains only the used templates.
SCE/EN HI/C60 HI-95

Figure 111: Unused Templates Contextual Menu
4.2.11.19 UNUSED TEMPLATES REFRESH

Purpose:
 Refresh the Templates list area according to the state (ticked or unticked) of the Unused templates
item.
Availability:

Call:

Operation:
2 Choose Unused templates refresh item.
4.3 USER MENU
Figure 112: User Menu
HI-96 SCE/EN HI/C60

4.3.1 USER/CHANGE APPLICATION

Purpose:
 Allows to log in the DS Agile SCE application giving a user name and the password. The user has
profile of available actions with DS Agile SCE that filter information relatively to the profile. At session
start, there is a default right defined by product options and licenses.
Availability:
 Always
Figure 113: User/Login pop-up
Operation:
This window is modal.
 User name: a text field to enter the login name. If it is not the first time that the DS Agile SCE is
launched, the login name of the previous user is already entered.
 Password: when the user enters his password, only stars are displayed in order to hide the password
actually entered.
 Profile: the profile that the user wants to use in the current session. The last used profile, is selected
by default. Only the profile available for the user set in the Username field are selectable in the combo
box.
Three application types are defined:
1 DS Agile
2 Poste-d (customer-specific application)
3 C26x-Standalone
These types are used to filter out some data.
For example, only "Poste-d" applications display "Poste-d"-specific protection functions;
Similarly C26x-Standalone applications do not display OI and IEC 61850-8-1 data.
This default type is used during the creation of configuration to set its type.
The default type can be changed when there is no open database, with User/Change Application.
SCE/EN HI/C60 HI-97

The previous user profiles have been replaced by the applications types.
Three pre-defined user names have been defined, with their own default application type:
 DS Agile: can define "DS Agile", "C264-Standalone" and "Poste-d" applications.
 Electre: can define only Poste-d and C264-Standalone applications.
 C264-Standalone: can define only C264-Standalone applications.
To manage theses users, User/Administration should be used.
The standard HMI is used but it is simplified so as not to display unused functionality.
Display the current application type:
 When no database is open, the default application type is displayed in the SCE title.
 When a database is open, the application type of the database is now displayed in the SCE title before
its path.
HI-98 SCE/EN HI/C60

4.3.2 USER/ADMINISTRATION
Purpose:
 Manages the authorised users on DS Agile SCE. The management includes adding or removing a
user, changing passwords or profile, modify users relative description.
 Let point that the administrator user cannot remove him.

Availability:
 Only user with the administration profile.
Figure 114: User/Administration pop-up
Add defines a new user with his/her profile and description. Remove acts on the selected user. “Properties”
button is a separate definition of profiles, as “Set Default” used when no Login is required. Password is a
facility display below to re-enter forgotten password.
Operations:
This window is modal. It displays the user list and allows to make some updates on it.
SCE/EN HI/C60 HI-99

 Checkbox Login required:

 if selected: the login is set as mandatory. The users must use a user name and a password to
enter in DS Agile SCE.
 if not selected: the login is set as optional; the passwords can be “empty” strings. the users can
enter in the DS Agile SCE without login. In this case, a default profile (administrator) is given for
this session.
 User table: display the list of the registered users with their profile and a description field. It is possible
to select a user (the line is highlighted).
 Add Button: leads to the “user properties” dialog box and allows to add a new user.
Figure 115: User Properties pop-up
 Remove button: remove the selected user.

This button is disabled if:
 no user is selected,
 the selected user is the logged one,
 the logged user does not hold administration rights.
HI-100 SCE/EN HI/C60

 Properties button: leads to the “user properties” dialog and allows to modify the current properties of
the currently selected user.
This button is disabled if no user is selected.
If the selected user is the only one which has the “administration” profile, it will be impossible to
change the profile.
 Password button: leads to the “change password” dialog box and allows to change the password of
the selected user. This button is disabled if no user is selected.
Figure 116: User/Administration redefining password
 Set Default button: set the selected user as the default user.
 Close button: close this dialog window.
4.4 GRAPHIC MENU

Graphic menu is the collection of items which implements DS Agile SCE graphic features:
 Graphic editors which are specialised for each kind of target equipment: OI mimic and Controller
mimic. The data model and the edition constraints of each of them are different.
 Graphic palettes: colour, font, stroke, and bitmap. Theses palettes are used to define the graphical
attributes of each graphic object of mimics.
Items are activated when a graphic object is selected in navigator.
The graphic menus are classified from the kind of graphic objects. A graphic object could be a part of an OI
mimic or a Controller mimic. Two different graphic editors can be edited them: OI mimic editor and
Controller mimic editor.
General menu items (Grid, Zoom, and Anti-aliasing) are independent of this classification. Theses items
can be applied to an OI mimic or to a Controller mimic.
Graphic palettes can be modified at any moment.
SCE/EN HI/C60 HI-101

Figure 117: Graphic/Menu
List of items:
OI Mimic All specialised menu items for OI mimic graphical objects
Controller Mimic All specialised menu items for Controller mimic graphical objects
Grid Toggle to activate Magnetic Grid
Zoom factors used for the current editor (OI mimic editor or Controller mimic
Zoom
editor).
Anti-aliasing
Colour editor The editor of colour palette
Font editor The editor of font palette
Stroke editor The editor of stroke palette
4.4.1 GRAPHIC PALETTES

A palette is a collection of predefined graphical attributes. Each element of a palette is identified by a
number.
When a graphical object is defined, the graphical attributes of this object is precise with using theses
palettes.
When an element of a palette is modified, all users of this element, i.e., all graphical objects which use a
reference (its number) to this element are impacted by this modification.
For example, colour 21 is used for circles C1, C2, rectangles R1, R2, and R3. When colour 21 is modified in
colour palette, C1, C2, R1, R2, R3 are also modified.
Colour, font, stroke palettes are based on the same editor with two parts: left part is the list of palette
element, right part is the description of the selected element in the list.
Bitmap palettes use the navigator and the attribute editor to define it. A bitmap editor allows to edit, pixel
by pixel, the selected bitmap.

4.4.1.1 GRAPHIC/COLOR EDITOR

Purpose:
 A colour editor helps to define colour palette: 256 colours. The 19 first colours are fixed. Specific
colour palette can be set also as template in order to reuse it with several configurations. A number
identifies each colour of the palette.
Figure 118: Graphic/Color Editor
Availability:
 Always
Other call:
 Select a graphical object with a colour attribute and click on button .

For example a circle and fill colour attribute. The colour editor allows to edit the palette and also to
choose an already defined colour. The index of colour is displayed in the attribute editor between two
parentheses.

Figure 119: Color Attribute and Color Palette
Operation:
1 Launch color editor from menu graphic
2 Select the color to modify (since 19)
3 Click on Definition/Color or enter directly the new value
Modify the different attributes of the colour at the right part of the table. This part contains the definition of the
selected colour at the left part: long name, colour, and blinking period. The graphical representation of the
colour is updated at the left part:
Figure 120: Color General Definition
The pop-up for colour definition propose definition in RVB, HSB format. The samples help to play with
front/back policy.

Figure 121: Color Definition

4.4.1.2 GRAPHIC/FONT EDITOR

Purpose:
 A font editor helps to define font palette: 64 fonts. The 4 first fonts are predefined and can not be
modified. Specific font palette can be set also as template in order to reuse it with several
configurations. A number identifies each font of the palette.
Figure 122: Graphic/Font Editor
Availability:
 Always

Other call:
 Select a graphical object with a font attribute and click on button .

For example a text and font attribute. The font editor allows to edit the palette and also to choose an
already defined font. The index of font is displayed in the attribute editor between two parentheses.
Figure 123: Font Attribute and Font Palette
Operation:
1 Launch font editor from menu graphic
2 Select the font to modify (since 4)
Modify the different attributes of the font at the right part of the table. This part contains the definition of the
selected font at the left part: long name, family, size, style and weight. The graphical representation of the
font is updated at the left part:
Figure 124: Font Modification
3 At any moment, the test text can be modified: edit it with the field at the bottom of the font editor, then
the font column is modified with the new value.

Figure 125: Font Testing

4.4.1.3 GRAPHIC/STROKE EDITOR

Purpose:
 A stroke editor helps to define stroke palette: 64 strokes. The 5 first strokes are predefined and can
not be modified. Specific stroke palette can be set also as template in order to reuse it with several
configurations. Each stroke of the palette is identified by a number.
Figure 126: Graphic/Stroke Editor
Availability:
 Always

Other call:
 Select a graphical object with a stroke attribute and click on button .

For example a circle and its stroke type attribute. The stroke editor allows to edit the palette and also
to choose an already defined stroke. The index of stroke is displayed in the attribute editor between
two parentheses.
Figure 127: Stroke Attribute and Stroke Palette
Operation:
1 Launch stroke editor from menu graphic
2 Select the stroke to modify (since 4)
Modify the different attributes of the stroke at the right part of the table. This part contains the definition of the
selected stroke at the left part: long name, width, and dash. The graphical representation of the stroke is
updated at the left part:
Figure 128: Stroke Definition

4.4.1.4 BITMAP TABLE AND BITMAP EDITOR

Purpose:
 The bitmap table is a bitmap palette. It contains 150 bitmaps maximum. Each bitmap is identified by
a number, its identifier. Bitmap is used during Controller mimic definition, with this unique reference
(see Controller mimic section).
There is no specific editor to edit bitmap table: use navigator and attribute editor to edit it. The data
model of this palette is the same than the three other palettes. Bitmap table is an object of Graphical
tables of Graphical views. Each bitmap is a component of bitmap table. So for adding a bitmap, use
object entry and for deleting one, use edit/delete menu item.
A good practise is to name the bitmap with identifier as a prefix.
Figure 129: Bitmap palette through navigator
 A bitmap is implemented in DS Agile SCE by one or several files with *.png format.
A bitmap file is stored into the configuration database (.mpl or .mpc).
A bitmap file could be imported with another format (.jpg, .jpeg, .gif or .png) but it is always transcribed
into .png format.
A bitmap could be a single bitmap or multiple bitmap.

Single bitmap is displayed in a mimic without any animation, only one file is necessary to define this
kind of bitmap.
5-uple bitmap or multi-state bitmap is used to represent an object with different states: a bitmap file
by state. A specific multi-state bitmap is defined with 5 pre-defined states: default, open, closed,
withdrawn open, withdrawn closed.

The bitmap file can be edited by an external tools and import it. It can be also edited inside
DS Agile SCE with a bitmap editor.
Availability:
 Always
Operation:
1 Select the bitmap through the navigator. After this selection, a bitmap editor is displayed in graphic
area to edit it. It displays the default bitmap file.
Figure 130: 5-uple Bitmap Selection

Figure 131: Single Bitmap Selection
2 Select the bitmap file to modify from Attribute editor. It is not necessary for Single bitmap because only
one file can be edited for this kind of bitmap.

Figure 132: Bitmap File Selection for 5-uple Bitmap
3 After its creation, bitmap file name is not filled:

 You can define it with using of bitmap editor (see below),

 Or import it through a file chooser: click the button .
A file chooser appears: the bitmap files library is displayed. This library is local to the current
configuration: it is included in .mpc file.
You can choose among them a file or choose another directory and a bitmap file to import.
button allows to return to the local bitmap files library.
Figure 133: Bitmap File Chooser
4 Edit the selected bitmap file with bitmap editor. It is a standard pixel editor. It is composed of three
parts:

Figure 134: Bitmap Editor
 left part contents the draws tools (pencil, dropper, paint, eraser, and hand to move), the predefined
shapes (line, oval, rectangle, rounded rectangle and full oval, full rectangle, full rounded rectangle)
and the specific colour palette.
Note: The edited bitmaps are used in controller bay mimics displayed on DS Agile C26x front panel
HMI. Otherwise, the DS Agile C26x front panel HMI is black & white. So the specific colour palette of
bitmap editor is not useful for its actual application.
 central part contents the pixel editor or pixel view.

 right part contents the bitmap pre-viewer, the general function (resize view, erase view, save as
action) and then handling tools to rotate, move or flip the current bitmap.
5 Available operations with bitmap editor:
Objective Operations
Select one paint tool ( or ) in the tool box on the left,

Modify the colour of one or
several pixels at the same time select a colour in the palette on the left.
Click on the pixel or on a bitmap area to change the colour.
Select the eraser tool ( ) in the tool box on the left,

Erase the pixel colour in the pixel view, press the mouse button, drag the mouse to erase the desired pixels,
and release the mouse button.
Select one shape tool ( , , , , , , ) in the tool box on the left,

Draw a predefined shape in the pixel view, press the mouse button, drag the mouse until the desired dimension,
Select the hand tool ( ) in the tool box on the left,

Move the bitmap in the pixel view, presses the mouse button, drag the mouse until the desired position,
Move the bitmap pixel by pixel Click on one arrow ( , , , , , , , ) in the tool box on the right.
Rotate the bitmap Click on one rotation button ( or ) in the tool box on the right
Flip the bitmap Click on one flip button ( or ) in the tool box on the right
click on the resize button ( ) in the main tool box on the right.
Resize the bitmap A dialog box appears and the user can modify the width and/or the height of the bitmap.
If the user validates these modifications, then the bitmap is resized.

Objective Operations
Click on the erase View button ( ) in the main tool box on the right.
Erase the bitmap a confirmation dialog box appears. If the user validates its choice, then the bitmap is
erased but the physical file if it exists, isn't removed from hard disk.
The save of the modified bitmap is run automatically when one among following actions
is done:
 select an other attribute,
 select an other object,
 switch the mode,
Save the bitmap
 close the configuration database,
 exit of DS Agile SCE.
If the attribute of the modified bitmap is without value, then a dialog box appears and
asks the file name. The user clicks on OK and the save is done with this name if this
name isn't already use, else the name is incremented automatically (For example: open
*.png becomes open1.png).
Click on the Save As button ( ) in the main tool box on the right.
A dialog box appears and asks the new file name. The user clicks on OK and the save
Save the bitmap with an other is done with this new name, if it isn't already used, else the name is incremented
file name automatically (For example: open *.png becomes open1.png). A new bitmap file is
created. There is no specific constraint on the file name.
The user can also click on the Cancel button in order to cancel his action and in this
case nothing is done.
4.4.2 OI MIMIC
As all objects, the OI Mimic graphic objects can be manipulated from the Navigator and Attribute Editor.
Nevertheless, the OI Mimic Editor is helpful to create graphic objects, by showing a graphical
representation of the objects. The OI Mimic menus items allow to create and modify OI Mimic objects
through OI Mimic Editor.
Before a full description of theses items, a brief description of OI mimic editor:
View and specific toolbar
The OI mimic is displayed in the graphical area. A specific toolbar can be displayed with window/OI mimic
toolbar item. This toolbar contains some OI mimic item shortcuts.

Figure 135: OI MImic editor and its toolbar
 Content
The content of OI Mimic depends on the selected object in the Navigator.
 If the selected object is a mimic or a component of a mimic, the OI Mimic Editor contains the
graphical representation of the mimic.
 otherwise, the graphic area is empty.
The Navigator and the OI Mimic Editor are linked together: any modification done in the OI Mimic Editor is
also visible in the Navigator and/or in the Attributes Editor. Reversibly, any modification done in the
Navigator or in the Attributes Editor is also visible in the OI Mimic Editor (if the modification has a
graphical effect).
 Selection
The selected object in the OI Mimic Editor depends on the selected object in the Navigator. More
precisely:
 If the selected object is a mimic, no object is selected in the OI Mimic Editor.
 If the selected object belongs to a group or a multistate, the corresponding group or multistate is
selected in the OI Mimic Editor.
 If the selected object is a feature (as animation, action, …), the owner object is selected in the OI
Mimic Editor.
Multi-selection is available with a key-sequence: shift / left mouse click.
Unselect an object in a multi-selection is available with the same key-sequence: shift / left mouse click.

 List of items
Figure 136: Graphic/OI MImic Items
Hereafter, a full description of theses items with this classification:

 creation,
 transformation and rotation,
 group management,
 alignment,
 layer management.
4.4.2.1 GRAPHIC/CREATION SUB-MENU
Figure 137: Graphic/OI Mimic/Creation Items

Purpose:
 Create a basic graphic object. Creation is interactive: the position and the size of created object are
given by the user with mouse. The new object is added at bottom of navigator parent object list.
Availability:
 When a graphic object or a mimic is selected from navigator or from Mimic viewer.
Other call:
 OI Mimic toolbar.
 Object entry area: select the type of object to add. This way is not interactive. The object is created
with default values at the upper left corner. If an object already exists at this position, the new object
position is translated below the existing object(s).
List of available basic objects:
Line
Rectangle
Circle
Polyline
Text Text field

Variable text: the content of this text field is defined on run-time. This kind of object can be
Var.Text
linked to a datapoint, and the text is then the current value/state of this datapoint.
The icon is animated by memo messages entered on run-time at Alstom DS Agile OI. This
Memo.Icon
creation is not interactive: the new memo icon is created at the upper left corner.
Image Insert picture/Photo from file

Operation:
1 Select Parent graphic object: a mimic or another graphic object.
Figure 138: OI Mimic interactive creation
2 Select the type of object to create (line in example).

3 A cross cursor appears in OI Mimic editor: press the mouse button at the desired position, drag the
mouse until the desired dimension, and release the mouse button. The line is created at the given
position with the given size.
4 The object Line appears in navigator below its parent.
5 Attribute editor is updated with the attributes of the new object. Object attributes can be adjusted. For
a line, its position, stroke type or stroke color.

Figure 139: OI Mimic interactive creation result
4.4.2.2 GRAPHIC/TRANSFORMATION SUB-MENU AND ROTATION ITEM
Figure 140: Graphic/OI Mimic/Transformation Sub-Menu

Purpose:
 Transform a graphic object:

Flip Symmetry upon horizontal axis
Mirror Symmetry upon vertical axis

Horizontal Line Projection of line on Vertical axis
Vertical Line Projection of line on Horizontal axis
Square Rectangle is forced to be perfect square
Round rectangle Rectangle corner is rounded
Perfect Circle Circle is forced to be perfect circle
Arc Circle arc is forced to be semi-arc
Open polyline Linear segment between last and first polyline point is not drawn
Close polyline Linear segment between last and first polyline is drawn
Rotate from 90° the selected object, left direction. Any basic graphic object could
Rotate 90°
be rotated except text, var.text and Image objects.
In bold, the type of object for which the transformation is applied.

Availability:
 Depending on the selected element.

Other call:
 OI Mimic Toolbar for Flip, Mirror or Rotate 90°

 Contextual menu of the selected graphic object to transform. For example:
Figure 141: OI Mimic transformation call
Operation:
1 Select the graphic object to transform.
2 Select the available transformation for this kind of object. See the description table. In bold, the good
type of object for the transformation.

3 The transformation is applied to the selected object. Its graphical representation is updated. For
example for the previous line and Horizontal line transformation:
Figure 142: OI Mimic Transformation Result
4.4.2.3 GRAPHIC/GROUP SUB-MENU
Figure 143: Graphic/OI Mimic/Group Items
Purpose:
 Manage groups of graphic objects.

A group is a container of graphic objects. A graphic object could be also a group. So, you can have
a group of group, recursively...
A group can be handled as a basic graphic object: move, resize, cut, copy, paste, etc.
Figure 144: A Group In Navigator and OI Mimic Viewer
 A specialised group has been defined for Alstom DS Agile SCE application: a multiState. A multiState
is a group of symbols. Each symbol represents the state of a datapoint. A symbol could be a basic
graphic object, a group or another multiState. A complete description of its application and its relations

is done in chapter Application of equipment OI. The creation of a multiState is available only from
Object entry area. It is not possible to ungroup a multiState.
Figure 145: A specialised group: the multistate
 When a group is selected, these components can not be edited individually: move, resize, etc. A
special edition mode is available to edit the components of an existing group.
Figure 146: Group Edition
Availability:
 Group: when at least two graphic objects are selected. Multi-selection is available with shift / left
mouse click.
 Ungroup: when a group is selected. This item is not enabled for MultiState.
 Group edition: when a group or a multiState is selected. The selected object can be an inner group: a
group of group. In this last case, the selection must be done with navigator; OI mimic viewer
represents only first level group.
 Exit group edition: when a group or a multiState is going to edit.

Other call:
 OI Mimic ToolBar.
 Contextual menu when a group is selected (right click): ungroup and group edition
Operation:
Select several graphic objects with mouse: shift / left mouse click
Select group item. A new group is created. The selected objects are moved under this new
group. The mimic viewer and the navigator are updated.
Group

Select a group
Select ungroup item. The group is deleted. The objects of the group are moved at the same
level as the deleted group.
Ungroup
Select a group or multiState.

Select group edition item: the mimic viewer is cleared and is filled with the objects of the
selected group or multiState.
Edit and arrange all children of edited group or multiState:
Group edition
While in group edition, select Exit group edition: the mimic viewer is cleared and filled with the
whole mimic. The components of the group can not be edited yet:
Exit group
edition

4.4.2.4 GRAPHIC/ ALIGNMENT SUB-MENUS
Figure 147: Graphic/OI Mimic/Vertical Alignment Items
Figure 148: Graphic/OI Mimic/Horizontal Alignment Items
Purpose:
 Align selected graphic objects

Availability:
 Two graphic objects must be selected at least in OI mimic viewer.

Other call:
 OI Mimic Toolbar
Left Align left selected objects
Centre Centre selected objects
Right Align right selected objects
Side by side Reorganise objects side by side
Top Align top selected objects
Centre Centre selected objects
Bottom Align top selected objects
Side by side Reorganise objects side by side
Operation:
1 Select the graphic objects to align, at least two objects. Multi-selection is available with shift / left
mouse click.

Figure 149: OI Mimic Alignment Preparation
2 Select the alignment rule to apply.

3 The alignment is applied to the selected objects. The position of each selected object is updated with
the given rule. Their graphical representation is updated. For example, with :
Figure 150: OI Mimic Alignment Result
4.4.2.5 GRAPHIC / LAYERS SUB-MENU
Figure 151: Graphic/OI Mimic/Layers Items
Purpose:
 modifies the stack position of graphic objects which are superposed. This defines which objects will be
on top or behind the selected object. This mechanism can be represented by a stack: the bottom of
the stack is behind the top of the stack.
Availability:
 only one graphic object is selected.

Other call:
OI Mimic Toolbar
Lower Set the object at the bottom of the stack
Upper Set the object at the top of the stack
Backward Move back the object of one position in the stack
Forward Move up the object of one position in the stack
Operations:
1 Select one graphic object.
In the following example, the selected object, the middle red circle, is in second position in the stack. Left
white circle is in top position, right blue circle is in third position and blue rectangle is in bottom position.
Figure 152: OI Mimic Stacked Object Selection
2 Select the layer item. The stack position of the selected object is modified. The graphical
representation of the selected object and of the stacked objects is updated. For example, with ,
lower, middle red circle is then in last position:
Figure 153: OI Mimic Layers Result
4.4.3 COMPUTER (I.E. CONTROLLER) MIMIC

As all objects, the Controller Mimic graphic objects can be manipulated from the Navigator and Attribute
Editor. Nevertheless, the Controller Mimic Editor is helpful to create graphic objects, by showing a
graphical representation of the objects. The Controller Mimic menus items allow to create and modify
Controller Mimic objects through Controller Mimic Editor.
Only the available items of the Controller mimic are described and not the way to configure completely a bay
mimic. This way is described in the Application chapter of the DS Agile C26x user manual. That chapter
describes how to configure a controller and its bay mimic. In particular, it describes all links of a bay mimic
and its components with electric topology (bay, module, datapoint).
Before a full description of theses items, a brief description of Controller mimic editor:
 View and specific toolbar

The Controller mimic is displayed in the graphical area. A specific toolbar can be displayed with
window/Controller mimic toolbar item. This toolbar contains some Controller mimic item shortcuts.
Figure 154: Controller Mimic Editor And Its Toolbar
 Content
The content of Controller Mimic depends on the selected object in the Navigator.
 If the selected object is a bay mimic or a component of a bay mimic, the Controller Mimic Editor
contains the graphical representation of the bay mimic.
 If the selected object belongs to a module , the corresponding module is selected in the
Controller Mimic Editor.
The Navigator and the Controller Mimic Editor are linked together: any modification done in the Controller
Mimic Editor is also visible in the Navigator and/or in the Attributes Editor. Reversibly, any modification
done in the Navigator or in the Attributes Editor is also visible in the Controller Mimic Editor (if the
modification has a graphical effect).
 Selection
The selected object in the Controller Mimic Editor depends on the selected object in the Navigator. More
precisely:
 If the selected object is a bay mimic, no object is selected in the Controller Mimic Editor.
 If the selected object belongs to a module, the corresponding module is selected in the Controller
Mimic Editor.

Multi-selection is available with a key-sequence: shift / left mouse click.

Unselect an object in a multi-selection is available with the same key-sequence: shift / left mouse click.
 List of items
Figure 155: Graphic/Controller Mimic Items
Hereafter, a full description of theses items with this classification:

 creation,
 module management
4.4.3.1 GRAPHIC/CREATION SUB-MENU
Figure 156: Graphic/Controller Mimic/Creation Items
Purpose:
 Create a basic graphic object. Creation is not interactive: the object is created with a default position
and a default size. The new object is added at bottom of navigator parent object list.
Availability:
 When a graphic object or a mimic is selected from navigator or from Mimic viewer.
Other call:
 Controller Mimic ToolBar.

 Object entry area: select the type of object to add.
List of available basic objects:
Horizontal Line
Vertical line
Text A text field. The text must be defined by the user.
Predefined text Some predefined text fields are available from Object Entry area.
Bitmap Bitmap defined from bitmap palette (single)

Generic module Specialised group that represents a generic module.

Transformer module Specialised group that represents a transformer module.
Operation:
1 Select Parent graphic object: a bay mimic or another graphic object.
Figure 157: Controller Mimic creation (Before)
2 Select the type of object to create (Generic module in example).

3 The object Generic module appears in navigator below its parent and the Controller mimic viewer is
updated with its graphical representation. The module is created with a default position and a default
bitmap. This object can be handled like all graphical objects with mouse.

Figure 158: Controller Mimic creation (After)
4.4.3.2 GRAPHIC/MODULE SUB-MENU
Figure 159: Graphic/Controller Mimic/Module Items
Purpose:
 Manage specialised groups of bay mimic: the generic module and the transformer module.
 A group is a container of graphic objects.
A group can be handled as a basic graphic object: move, cut, copy, paste, etc.
 Two specialised groups have been defined for Alstom DS Agile SCE application and bay mimics:
these groups are the graphical representation of electric module.
A complete description of their application and their relations is done in the Application chapter of the
C26x user manual.
 Generic module has two fixed components: the module name and its graphic representation
(LHMI xPS MultiSt) for which a bitmap is referenced from bitmap palettes.

 Transformer module has two fixed components: the module name and its graphic representation
(LHMI TPI MultiSt) for which a bitmap is referenced from bitmap palettes. Some optional
component can be added with Object Entry Area.
Figure 160: Specialised Groups: Generic & Transformer Module
 When a module is selected, these components can not be edited individually. A special edition mode
is available to edit the components of an existing module.
Figure 161: Module Edition
Availability:
 Module edition: when a module is selected.

 Exit module edition: when a module is going to edit.
Other call:
 Controller Mimic ToolBar.

 Contextual menu when a group is selected (right click): group edition

Operation:
select a module
select module edition item: the mimic viewer is cleared and is filled with the objects of the
selected module.
edit, add new components and arrange them:
module edition
while module edition, select Exit module edition: the mimic viewer is cleared and filled with the
whole mimic. The components of the module can not be edited yet:
Exit module
edition
4.4.4 GRAPHIC/UTILITY SUB-MENU
Figure 162: Graphic/utility Items
Figure 163: Graphic/ Zoom Items
Purpose:
 Apply general settings upon graphical objects. Theses items are available for Controller Mimic Editor
and for Controller Mimic Editor.

Availability:
 Always
Other call:
 Common toolbar
Toggle to activate Magnetic Grid. Grid is displayed in the viewer. Any moving with
mouse is aligned with the magnetic grid.
OI Mimic: the grid is displayed and activated with the grid settings defined with
Grid
tools/setting function.
Controller Mimic: the grid is displayed. The grid is always activated for this editor
even if the grid is not displayed.
The available zoom factors are different for:
Zoom OI Mimic: 25%, 50%, 75%,100%, 150%, 200%, 400%, 800%
Controller Mimic: 50%, 100%, 200%, 400%, 800%
Anti-Aliasing Smoothing or anti-alias function
The following copies illustrate anti-aliasing action.
Figure 164: Graphic/Anti-aliasing effect

4.5 WORKBENCHES MENU
Figure 165: Workbenches Menu
The aim of this menu is to drive actions linked to external tools. The presented tools are:
 ISaGRAF from CJ international used to edit custom automation in IEC61131. This tool could be an
option and subject to license.
 FBD
 editor used to edit Function Block Diagram.
 This section describes only how launching theses tools.
 A complementary description of ISaGRAF is available in the chapter SCE/EN AP.
4.5.1 WORKBENCHES/ISAGRAF EDIT …

Purpose:
 Launch ISaGRAF PRO Workbench, with all element already entered and needed for the tool:
 name of automation,
 list of interface variables into dictionary.
Availability:
 ISaGRAF Pro must be installed with its Dongle.

Other call:
 Contextual menu when type of selected object is Slow Automation or C26x PLC
Operations:
1 Select ISaGRAF edit item.

Figure 166: Tools/ISaGRAF Edit from Slow Automation Object
Figure 167: Tools/ISaGRAF Edit from C26x PLC Object

2 The ISaGRAF workbench is launched with modal mode. Edit the slow automation, save it and quit
workbench to come back to DS Agile SCE.
4.5.2 WORKBENCHES/ISAGRAF COMPILE

Purpose:
 Compile/Check ISaGRAF PRO automation made with its Workbench, to verify syntax and make the
target files. This operation is made automatically in DS Agile SCE File/Generate.
Availability:
 ISaGRAF Pro must be installed with its Dongle.

Other call:
 Contextual menu when type of selected object is Slow Automation or C26x PLC. See Tools/ISaGRAF
edit.
Operations:
1 Select ISaGRAF compile on the available object,
2 A popup indicates the result of compilation.
4.5.3 WORKBENCHES/FBD EDIT …

Purpose:
 Launch FBD editor which allows to define Function Block Diagram:

 for logical equation used by interlock,
 for FBD automation.
Availability:
 Always
Other call:
 Contextual menu when type of selected object is FBD Automation or FBD interlock.
Operations:
1 Select FBD edit item on the available object

Figure 168: Tools/FBD Edit from FBD Automation

Figure 169: Tools/FBD Edit from FBD Interlock
2 The FBD editor is launched for the selected FBD with modal mode: the DS Agile SCE main editor is
hidden during FBD edition. Edit it, save it and quit FBD editor to come back to Alstom DS Agile SCE.
4.6 TOOLS MENU
Figure 170: The Tools Menu

4.6.1 TOOLS/OPTIONS
Figure 171: Tools/Option Setting manager on DS Agile SCE Application

Purpose:
Display and allow modification of DS Agile SCE settings. The settings are:
 DS Agile SCE Version (including creation date, JDK, data model version),
 parameters upon visibility in status bar,
 parameters upon mimic graphic editors (colour, Mimic editor option,...),
 parameter upon DS Agile SCE access directories (tools, component, working directories,…).
Availability:
 Right dependent
Other call:
 File/Properties and select tab Configurator

Operations:
1 Select Tools/Options item
2 Modify the value of updateable setting (white background): * indicates then that the setting has been
modified.
3 Restore the previous value of the modified setting with contextual Restore (right click on the modified
setting).
4 Save the modifications with Close button or cancel it with Cancel button.
5 A setting of a previous version of DS Agile SCE can be imported with Import button. From the
displayed file chooser, select the DS Agile SCE_setting.xml file from installation directory of this old
version; then click on Select button.

4.6.2 TOOLS/CREATE TEMPLATE…
Figure 172: Tools/Create Template Creation
Purpose:
 Create a new template from the objects hierarchy.

Availability:
 Right dependent
Other call:
 None
Operation:
1 Select Tool/Create template item: a tree view of all objects show
2 Select objects that are parts of the new template
3 Select an object that is the anchor of the new template. Be careful, while an anchor is not defined, the
Create button is disabled
4 Click the Create button: a new template is added in Templates List. This template contains all
selected object. Its name is the name of anchor object

4.6.3 TOOLS/ADVANCED SEARCH

Purpose:
Creation of query from all configuration data. For a complete description of a query and its result, refer to §
4.2.9
Availability:
 Right dependent
Other call:
 None
Operation:
 Advanced search is available with the menu item tools/Advanced search or the button of the common
toolbar or the shortcut ctrl-F
This HMI has two main parts:
 The definition of the query and its management

 The results of the query: a table that represents all results and allows their edition.
Select Tools/Advanced Search … item. The following dialog box is displayed. For a complete description of
this dialog box and the next operations, see refer to section 4.2.9

Figure 173: Tools/Query item
 Object type must be selected from type browser.

 When this type is selected, the list of its attributes and relations are displayed.
 A subset of the attributes/relation must be selected with the buttons.
This subset defines on what the query will be done. The same subset is used to display the results into a
table: a table column for each attribute/relation.
 For each element of this subset, a filter can be defined: with an operator and for some operator, a
value
 An element is pre-defined: the path of the object – the path of the object parent.
For example, for a bay datapoint, it will be the path of its bay.
To fill a filter for path, the copy action of an object from navigator could be used: the path of the selected
object is copied into the system clipboard and could be paste into the field value of the path filter.

4.6.3.1 STORE A QUERY

When a query is defined, it could be saved with this button.
A new saved query could be defined with the save as option. Text field allows defining its name.
The selected query could be updated and re-saved with this save option.
Saved queries are available from this combo.
At any moment, the last query is available with default query last: it is the last new executed query.
The selected query could be deleted with the Delete button.
The query is saved into a file sce_queries.xml of SCE installation directory.

This file could be moved to another SCE version to share a library of queries.
This operation could be done with a copy of the file from the origin SCE and a move to the target SCE.
The file could be edited with a text editor or an xml editor. Xml Schema queries.xsd is available into sub-
directory data/dtd of SCE installation directory.
The mnemonic of types/attributes could be obtained from documentation that is included into SCE installer.

4.6.3.2 EXECUTE A QUERY

When a query is defined or loaded, it could be executed with this button.
Search tab is updated with the number of found objects.
The result table is then updated with the found objects: a column is created for each selected
attribute/relation.
Theses columns could be:
 sorted: multi-sort is available with ctrl-click sequence.

 and filtered: quick search feature is available for looking for the filter.

4.6.3.3 HIDE QUERY

Query part of an Advance search tab could be hidden / displayed by this button.
A tooltip (on a yellow background) of parameters field displays a summary of the current executed query.
4.6.3.4 EDIT THE RESULT OF A QUERY

The result table could be edited:
 Attribute by a direct edition of its value.
 Relation by the link or the relation editor and a double-click to launch it.

Copy/paste from/to System clipboard is available for attribute and relation cell.
4.6.3.5 SPECIAL QUERY TO FIND THE OWN ATTRIBUTE OF A RELATION

For example, it’s the relation ‘has for IEC61850 server…’ and attached attribute ‘modeling/goose usage’.
This kind of relation (=relation with attached attribute) is displayed into Types browser and could be
handled like other type.
A special default filter element is defined, ‘path relation to’: with the ‘path’ element, they represent the two
linked objects.

4.6.3.6 HOW TO NUMBER A SUBSET OF RESULTS

When a subset of result has been selected, the number of selected objects is displayed into SCE status
bar. This feature is available for quick and advanced search.
4.6.4 TOOLS/LANGUAGES…
Purpose:
This dialog box allows the user to manage the configuration and HMI languages. This window allows to
modify the following languages:
 Current languages: the language used to display user interface and database contents or creation
(names, labels, etc).; the selection in the second drop-down list allows automatic switching in case a
dictionary has been created
 Database languages: languages that are defined in a database; they are used in the Dictionary for
creation of a multi-lingual glossary
 Generation languages: used to localize C26x and OI devices

Availability:
The dialog box is always available, even if no database is opened. Available actions depend on context:

 no database is opened:
Figure 174: Languages Setting when no database is opened
 a database is opened:
Figure 175: Languages setting when a database is opened

 a released database is opened:
Figure 176: Languages setting when a released database is opened
Cancel button is always available and close the dialog box without applying modifications.
OK button is available only if allowed modifications have been done in language selection. Modifications are
identified by an asterisk (‘*’) for each modified field. Clicking on OK validates the modifications.
Other call:
 None
Operation:
Current languages
Two combo-boxes are available:
Configurator’s language stands for the language used to display the user interface (i.e. the menus, dialog
boxes, the button tool tips, labels…),
Database’s language has two meanings, depending on context:
 if no database is opened, the language indicates in which language a database must be created
 if a database is opened, it indicates in which language the database content must be displayed (i.e.
the values of attributes)
When a database is opened, the displayed database language is set to current configurator’s language if the
language is defined in database, or else, the first created language of the database is chosen.
Database languages
All languages of the current configuration appear in the list Configuration languages.
The remaining available languages appear in the list Available languages.
Add button: to add the selected languages from the “available” list to the configuration. When a language is
added all its multi-languages attributes are copied from the current configuration language to the new one if

its value is different than default value: if the attribute hasn’t been updated by user, the translated default
value is used for the new language.
Remove button: to remove the selected languages from the “selection” list. The current language of the
DS Agile SCE cannot be removed.
Adding and removing are effective only when OK button is clicked.
Generation languages
These languages are used to localize the generated databases for DS Agile OI and DS Agile C26x units.
The languages list is a subset of selected languages. As of this version, the C26x does not support Turkish
language.
4.6.5 TOOLS/DICTIONARY…
Purpose:
 Open a dictionary editor with all configurable labels that can be translated.
Availability:
 Right dependent
Other call:
 None
Operations:
1 Select Tools/Dictionary item
2 Select the languages to edit and the reference language.
Figure 177: Dictionary languages selection
3 Click the Next>> button: the following modal dialog box appears:

Figure 178: Tools/Dictionary … dictionary manager
Tool bar:
 The upper tool bar is used to select the labels that must be displayed in the edition area. The
selected letter corresponds to the first letter of the label in the reference language.
 Only the letters that actually correspond to existing labels in the reference language are showed.
For instance, if there is no word beginning by the ‘a’ letter in the reference language then the ‘A’
letter will not be present in the tool bar.
 The ”ALL” word allows displaying all the entries of the dictionary.
Edition area:
 The greyed parts can not be edited by the user. The reference language labels are greyed, unlike
the target languages labels.
 The first column shows a “mark” if the translation of the corresponding entry was modified.
 A contextual menu allows to cancel the modifications of this entry and thus to retrieve the initial
values of all translations.
 The user can directly edit a translation inside the cell of a target language column.
 The max length column contains the maximum length of the label translations.
 The attribute column shows the attributes number that are associated with this label. A button
allows to display a windows tree structure with all attributes holding this label. This button is
contextual and it is displayed when the entry is selected.
Buttons area:
 The Previous button leads to the dictionary language selection dialog box in order to change the
languages to the current dictionary. This button is greyed if at least one entry is marked as modified
by an asterisk in the first column.
 The Apply button updates the configuration database with the last modifications without closing the
window. After pushing this button, all asterisks are removed from the first column.
 The Close button closes the dialog window. If there is some modified field, the DS Agile SCE asks
to the user to save the data before closing windows.
 The Cancel button closes the window discarding the last modifications.

 The Export button saves the dictionary as an XML file.

 The Import button allows entering a dictionary from an XML file.
Figure 179: Extract of a Dictionary Xml File
4.7 DATA MENU
Figure 180: Tools Export, import and report actions

4.7.1 DATA/SCE DATA/EXPORT, IMPORT SUB-MENU

The export/import actions allow to export/import a subset of configuration data to/from XML files.
Several kinds of export/import are available:
 Standard export/import: a DS Agile SCE standard XML format has been defined to exchange any
data from/to DS Agile SCE.
 IO mapping export: a specialisation of standard XML export. This export is limited to controllers and
their mappings: all datapoints and their linked info (profiles, addresses, …) that are managed by
controllers.
 SCL 61850 export: use of IEC 61850-8-1 standard to export SBUS data.
For export use cases, the subset of configuration data is defined by user and depends on the kind of
exports:
 Standard export: a browser allows to select/deselect some objects/templates sub tree. The result
query allows this selection too.
 IO Mapping export: a browser allows to select/deselect some controllers.

 SCL 61850 export: a browser allows to select/deselect some IEC 61850-8-1 devices.
Some Extra configuration files attached to data are excluded from any import and export actions:
 ISaGRAF and FBD files (Fast and slow automation description)

 Image files included in OI mimics and bay controller mimics
The others Extra configuration files attached to data are included from any import and export actions:
 XML files of FBD (Fast automation description)

 Image files of FBD (*.png)
4.7.2 DATA/SCE DATA
4.7.2.1 DATA/SCE DATA/ IMPORT & EXPORT SCHEMA DEFINITION

Tools/Import and Tools/Export use the same exchange format.
Object is the central XML element of this format:

 Name is the DS Agile SCE attribute short name of the object,

 id is the internal DS Agile SCE id of the object;
 idType is the type id of the object;
 ExtId is the object path name, also called External Id. This path name identifies the object and its
parents. It’s a concatenation of short name of each parents of the object;
 Attribute(s) is a DS Agile SCE attribute of the object with:

 id is the internal mnemonic of the attribute,
 Name is the label that is used by DS Agile SCE Attribute editor,
 Value is the value of the attribute,
 ReadOnly is a flag that indicates the attribute is read only or not
 and eventually Desc is the textual description of an enumerate value.
In the following example, an attribute is displayed in each line, so 8 attributes are displayed:
 Relation(s) is the definition of a link between this object and another object:
 this link or relation is typed;
 the other object is defined by its identifiers (internal and external);
 and, optionally, relation has its own attribute(s).
In the following example, the relation describes the link client/server between two devices. This kind of link
has an attribute, DataModelAndGooseUsage, which defines the type of SBUS communication between
theses two devices.

The description of DS Agile SCE exchange format is completely defined by schema file (*.xsd) in DS Agile
SCE installation directory: DS Agile SCEx.y/data/dtd/ExportDb.xsd
4.7.2.2 DATA/SCE DATA/EXPORT…

Purpose:
Export in XML zipped files the selected part of current database.
The selection of data is made in a browser displaying the three categories of objects (electrical, system and
graphical) and templates split in the 3 previous categories, corresponding to the main entry point of the
template.
The exported data can be issued from the result of a query.
Standard export produces multiples XML files:
 One file for each type of exported objects and one file for each type of exported templates.
Notes: - Each XML file uses the standard DS Agile SCE XML format.
- One file contains only one type of objects.
- Two sub-directories are exported, one contains all objects files, and the other all templates files.
In the following example, the file UCA2Computer.xml contains three controllers. A header element defines
the context of this export.

 The Extra configuration files: for the FBD objects or templates, a sub-directory (Fbd) is exported and
it contains all XML files image files of FBD.
Standard export produces also some files used only for reporting use cases. Theses files are not used by
import use cases.
 Hierarchy.xml: XML file containing all the object/template hierarchy exported.

 Catalog.xml: XML file containing the list of files exported for each object/template types.
 ExportDB.xsd: schema of exported XML files. Only for info.
Availability:
 Right dependent
Other call:
 None
Operation:
1 Select Data/Sce Data/Export item
2 A browser appears. Select the part of work database to export.

Figure 181: Data/SCE Data/Export Selection
3 Click the Export button.

4 A window pop-up to define directory and name of zip file
5 The exported files are stored in this ZIP file.
4.7.2.3 DATA/SCE DATA/IMPORT…

Purpose:
Import XML files. The following actions are taken into account during this import:
 object attributes and relations modifications,
 object creations,
 object instantiation from template,
 object deletions.
Standard import is available for one XML file or for ZIP file that contains several XML files. In this case, the
XML files are imported with file name alphabetic order.
In an XML file, only Object elements are taken into account during import process, with file reading/parsing
order. The XML element Type which could group objects with the same type is not taken into account. The
Object elements that represent DS Agile SCE template are not imported.
Import format is the standard DS Agile SCE XML format. So, the complete XML description (attributes,
relations) of a DS Agile SCE object, is the result of the Standard export use case.
By default, Object is imported in creation/updating mode: if the object already exists, it is updated,
otherwise it is created.

Some other explicit actions are available during import:
 instantiate a template. An attribute op with key word “inst” as value is defined. Another attribute extIdT
contains the identifier of template to instantiate.
 delete an object. An attribute op with key word “del” as value is defined. It indicates that object must
be deleted.
Note 1:
XML Attribute Name is optional. It is used to modify the DS Agile SCE attribute Shortname of the object. If
XML Attribute Name is not defined, ExtId must be defined; the last part of ExtId is used instead of XML
Attribute Name.
Note 2:
XML Attribute id and sub-element ExtId are both optional, but one at least must be defined to identify the
object during import into database. To search the object in database, XML Attribute Id is used at first. If Id is
not defined, ExtId sub-element is used. When ExtId is used, if two objects at the same hierarchical level
have the same external Id, an extra discrimination is done based on its idType. This idType is used to
determine the basic class of the object. The external Id + this determined class must define a unique key.
Note 3: (relative to Extra Configuration files of FBD)
In the sub-directory Fbd, the XML files of FBD are imported only if the corresponding diagram exists in
database. Each XML file of FBD has an "FBType" element with the "ExtId" attribute that is the external Id of
its corresponding diagram in order to find it.

Availability:
 Right dependent
Other call:
 None
Note: the Import function is NOT fit for importing databases especially the graphics.
Operation:
1 Save the current work (importing a file with graphics might cause SCE to close as importing graphical
object whose level is lower or equal to mimic is not supported)
2 Select Data/SCE Data/Import item
3 A file chooser appears. Select one or more xml files or archive files. The import treatment is then
applied on all selected files.
Figure 182: Data/SCE Data/Import File Chooser

4.7.3 DATA/SCE DATA/REPORT…

Purpose:
 Creation of a report from an archive file created by Data/Query or Data/Export function. The format
of the report is *.pdf.
Availability:
 Right dependent
Other call:
 None
Operation:
 Select Data/SCE Data/Report… item. A file chooser appears.
Figure 183: Data/SCE Data/Report Archive File Selection

 Choose an archive that has been created by a previous Data/SCE Data/Export action.
 A pdf report document is then displayed with a pdf reader. A pdf file is created in the same directory
than the selected archive with the same name. This report contains a full description of all data of the
selected archive.
Figure 184: Data/SCE Data/Report PDF File Result
Figure 185: Tool/Report Object Description Format
4.7.4 DATA/EXTERNAL DATA/EXPORT FBD

Purpose:
 Export in XML format FBD automations or FBD interlocks.

The exported files are stored in a ZIP file which can contain in according to the user choice:
 One XML file per FBD describing the FBD plus one XSD file describing the schema of a FBD XML
file. The XML file is linked to an XSD schema: therefore it must be valid. This file is used after
updating by the FBD Editor (The EqViewer software); it contains:
 the general data
 the interface data (inputs, outputs)
 the Function Block data (type, location)
 the connection data (source, destination)

 One PNG file per FBD which is the graphical representation of the FBD. Even if the FBD has been
created on 2 or 4 pages in the FBD Editor, only one PNG file is generated. The image size
depends on the useful area of FBD.
 One PDF file which is a report of all selected FBD in the dialog box. It is generated in A4 format
with the landscape orientation. It contains
 a cover page (see figure 186)
 a the FBD list ( see figure 187)
 For each FBD
 the diagram picture ( see figure 188)
 the input list ( see figure 189)
 the output list ( see figure 190)
Availability:
 Right dependent
Other call:
 None
Operation:
 Export of FBD can be done by two ways: One by one and globally
Note: The following explanations concern an FBD automation but are valid too for an FBD interlock

 Export one by one:

 Right-click the FBD to export. Then in the contextual menu click Export FBD….
Figure 186: Selection of the FBD to Export

 A Save dialog box is displayed in order to choose the destination folder and the filename (extension
xml). When done click the Save button.
Figure 187: Selection of the Destination Folder and the Filename

 Export globally:
 Click Data/External data /Export item: the FBD Export dialog box is then displayed
 Select the check box of the FBD to export
 Select the output file format ( XML, PNG, PDF)
 Click the Run button.
Figure 188: Global FBD Export Dialog Box
 A Save dialog box is displayed in order to choose the destination folder and the filename (extension
zip). When done click the Save button. A popup window informs that the export is running.

The followings figures give an example of some pages of the pdf file generated by the FBD Export function:
Figure 189: The cover page of the FBD automation report
Figure 190: The list of exported FBD

Figure 191: The diagram of FBD1
Figure 192: The inputs and outputs lists of FBD1
 Export to file:
The user can access to this function by clicking in tools\Export FBD menu.
A dialog box presents all FBD available on database and allows selecting all or part of them. The spare
and template objects are not available.

The user has to define the output file, the FBD type to create (XML, MNG or PDF file) and also has to select
which FBD he wants to export. The display of FBD can be based on Tree mode or List mode.
4.7.5 DATA/SCE DATA/IMPORT FBD

Purpose:
 Import in XML format FBD automations or FBD interlocks.

Availability:
 An FBD (automation or interlock) is present in the working database

Other call:
 None
Operation:
 Import of FBD can be done by two ways: One by one and globally.
Note: The following explanations concern an FBD automation but are valid too for a FBD interlock

 Import one by one:

 Add an FBD automation to the selected level (in the example given hereafter the selected level is
Feeder). This is done via the “Object entry” area associated to the selected level ( Feeder in our
example) by expanding User function then double-clicking FBD automation ( or right-clicking it and
then clicking Add)
Figure 193: Adding an FBD automation to a Feeder

 Right-click the newly created FBD. Then in the contextual menu click Import FBD….
Figure 194: Selection of the FBD to import

 An Open dialog box is then displayed in order to choose the origin folder and the name of the xml file
to import (FBD_TS_03.xml in our example). When done click the Open button.
Figure 195: Selection of the xml file to import
 The FBD automation is then present at the Feeder level.
Figure 196: The imported FBD automation

 Import globally:
 Click Data/SCE Data/Import item
 An Open dialog box is then displayed in order to choose the origin folder and the name of the zip file
to import (Two_FBD.zip in our example. This file has been previously created with the Tools/Export
function and contains two FBD: FBD 1 and FBD 2). When done click the Open button.
 FBD 1 and FBD 2 are present at the feeder level
Figure 197: The globally FBD import function
4.7.6 DATA/EXTERNAL DATA/EXPORT IOMAPPING…

Purpose:
 This export is a specialization of standard export: it allows to export the IO mapping of C26x
devices.
It uses the same XML schema but the exported files and the data selection are different.
The exported files are stored in a ZIP file.
IO Mapping Export produces multiple XML files:
 1 file for all profiles named <1 – Profiles.xml>,

 1 file for all selected C26x, named <2 – Equipement.xml>,
 n files, one for each selected C26x, named <3 – computer's short name.xml>.
Each XML file respects the standard DS Agile SCE XML format and hierarchy.
Profiles:
This file is build with all profiles found directly under Scs root and which respect the pattern *_[n].
Equipment:
This file is built with all equipment of the database (even if not selected in dialog box) and describes each
one:
 for a C26x, it gives all cards, SCADA networks, Legacy networks (IED) and printers,
 for a Gateway, it gives all SCADA networks,
 and for OI, it gives all printers.

Controller(s):
The last files are built for each selected C26x and define all datapoints managed by this controller and their
addresses (linking + SCADA + IED). They contain the following information:
 SCADA address (of other devices or of the controller) used by datapoints managed by the controller,
 IED address of the controller,
 Voltage Level,
 datapoints on Voltage Level,
 Bays managed by controller,
 datapoints on Bays level,
 Modules,
 datapoints on Modules level
Note 1:
In each file, the objects are sorted by their external id (= ExtId = path of short names of the hierarchy of the
object).
Note 2:
If an object is an instance of a Template and is the main object, XML attributes op and extIdT are added: op
with “inst” as value and extIdT with external id of template to instantiate as value. The external id of a
template is the name of template that is displayed in template navigator. For example, if a C26x is an
instance of template Scs-C26x-C26x
Model:
Note 3:
The relations are factorized. For example, an object “Group SPS” has several relations with other SPS; each
one uses the same type of relation. In this case, only one XML element Relation contains all sub-element
TargetObjectExtId. Each TargetObjectExtId sub-element defines the external identifier of each linked object.

Availability:
 Right dependent
Other call:
 None
Operation:
1 Select Data/External data /Export IOMapping item
2 A dialog box presents all controllers available on database and allows to select a part or all of them.
The spare and templates objects are not available.
3 Select the C26x units to export. Two representations (tree or list) are available. Shortcuts could be
used for selection.
Figure 198: Tools/Export IOMapping selection
4 Select the output file by clicking the "…" button

5 Click the Run button
6 The action progression is displayed graphically. This progression can be followed in three ways:
 the progress bar is animated to display the percentage of achievement of the process (the value is
a ratio of number of treated items),
 the messages displayed on status bar which are specific of each using,

 the nodes of the browser change in function of their processing state to follow processing.
Figure 199: Tools/Export IOMapping running
7 The Export action could be cancelled at any moment.

8 The exported files are stored in the given ZIP file.
4.7.7 DATA/ EXTERNAL DATA/EXPORT WIRING

Purpose:
 Export the wiring information of the selected controller(s)

Availability:
 A database is open
Other call:
 None
Operation:
1 Select Data/ External data/Export Wiring item: the Wiring Export dialog box is then displayed.
2 Select the output file, its format (XML or PDF) and the controller(s) whose wiring is (are) to be
exported.
A dialog box presents all Controllers available and allows selecting all or part of them. The spare and
template objects are not available

Figure 200: Tools/Export wiring selection
The action progression is displayed graphically. This progression can be followed in three ways:
 the look of the selected nodes of the browser change according to their processing state
The user has to define the output file to be created (XML PDF file) and also has to select which Controller he
wants to export. The display of Controllers can be based on Tree mode or on List mode.
When this export operation is complete the related files are created and can be opened. The "pdf" file is
generated in A3 format with the "landscape" orientation. it contains:
 a cover page: title, name of the database, SCE version number, date and time of the file
 a the list of the controllers
 for each controller: composition of the rack and for each board the name of each datapoint wired to
an pin of the connector of the board.

4.7.8 DATA/ EXTERNAL DATA/EXPORT SCADA

Purpose:
 Export in standard SCE) XML format the information related to the selected SCADA protocol(s)
Availability:
Other call:
 None
Operation:
1 Select Data/ External data/Export Scada item: the Scada Export dialog box is then displayed.
2 Select the output file and the SCADA protocol(s) which is (are) to be exported.
Figure 201: Tools/Export scada selection
The action progression is displayed graphically. This progression can be followed in three ways:
 the look of the selected nodes of the browser change according to their processing state

4.7.9 DATA/IEC61850/EXPORT SCL

Purpose:
This export is used to export a database (electric and system topology) in one or several XML files with a
schema defined by IEC 61850-8-1 standard:
 electric topology: electro-technical view of the substation with links between different modules
(topology),
 system topology: devices definitions and their IEC 61850-8-1 mapping.

The database can then be complemented with customer data and imported back to SCE.
Three export modes are available:
 a complete export (.SCD, System Configuration Description), that contains all the information
pertaining to the configured system, only one XML file;
 an IEC 61850-8-1 IED export (.IID, Instantiated IED Description), that contains all the information
pertaining to an IED, one XML file per IED;
 an IEC 61850-8-1 IED Model export (.ICD, IED Capability Description), that contains an IED template
to create IEDs based on the same model; one XML file per IED.
The XML format is described in the IEC61850 standard, part 6.
The exported files are stored in a ZIP file.
Availability:
 Right dependent
Other call:
 None
Operation:
1 Select Data/IEC61850/ExportSCL item
2 A dialog box displays all IEC 61850-8-1 devices, except OI Server and Gateway devices. It allows
selecting a part or all of them. The spare and templates objects are not available.
3 Select the devices to export. Two representations (tree or list) are available. Shortcuts may be used
for selection.

Figure 202: Tools/Export IEC 61850-8-1 selection
4 Enter the name of the output file in the Output file field ( zip extension)
5 Select the SCL file type to create: .SCD, . IID or .ICD. If .SCD is chosen all devices are selected.
6 Click Run
7 The action progression is displayed graphically. This progression can be followed in three ways:
a ratio of the number of processed items),
 the messages displayed on the status bar,
 the nodes of the browser change according to their processing state to follow its progress.

Figure 203: Tools/Export IEC 61850-8-1 running
8 The Export action may be cancelled at any moment.

9 The exported files are stored in the ZIP file shown at the bottom left of the dialog.
4.7.10 DATA/IEC61850/IMPORT SCD/IID…

Purpose:
 This import is used to update a set of IEC 61850-8-1 IEDs in the SCE database with data configured
outside the SCE in an IEC 61850-8-1 configuration file (.scd and .iid extension)
Availability:
Other call:
 None
Operation:
1 Select Data/IEC61850/Import SCD/IID… item. The SCD/IID import dialog box is displayed. In this
dialog box are listed all the IEDs of the database (spare and template objects are not listed).

Figure 204: SCD/ IID import dialog box
2 Click the browse button (1) to open a Select file dialog box. When the scd file is selected its name is
displayed in the Input file field (2).The IEDs whose network name is present in the SCD file ( IED
name field) are automatically selected and associated to the related description (3).
Figure 205: SCD/ IID IMPORT dialog box
3 By right-clicking on a no-associated IED a contextual menu is displayed (4). In this menu are listed the
no-yet associated descriptions present in the SCD file. By clicking the wanted IED (5) the association
is done (6).
Note: The first item of this contextual menu is Remove association if the right-click is done on an associated IED. This
item is of course used to remove an existing association.

Figure 206: SCD/ IID import dialog box: association done
4 After having defined the associations the user can select/unselect the IEDs to update in the the
database. Only associated IEDs can be selected.
5 The user ends this import operation by clicking the Run button. The selected IEDs are checked for
coherency with imported ones. If all IEDs are compliant they are updated with data found in the SCD
file: network name, IP address and goose information If at least one IED is not compliant the import is
not done and all non compliant IEDs are displayed in red. For these IEDs the non compliant elements
of imported IED are logged in the Trace panel.

4.7.11 DATA/IEC61850/MANAGE IED…

Purpose:
 manage the list of IEC 61850-8-1 IED model files (which are xml files)
Availability:
 Right dependent
Other call:
 None
Operation:
 Select Data/IED61850/Manage IED… item. The following modal dialog box appears:
Figure 207: Tools/IED Management…
In this dialog, there are two parts:
 the list of available model files,

 the list of existing IEC 61850-8-1 IED.
The list of existing IEC 61850-8-1 IED is always displayed, and for each, the current model is indicated if it
exists.
When a model is selected, the IEC 61850-8-1 IED that has the selected model is ticked.

Then, five actions are possible through this dialog box. When the database is read-only, only Export action is
possible.
 Import: to append model files (XML or ICD files)

 Export: to save his models outside of the database directory
 Remove: to delete unused models form the library. When a model is used by an IED, the Remove
button is not active.
 Set: to associate (change or add) a model to an existing IED.

 IED Mapper: to update mapping of private classes of the IED to DS Agile common classes. The IED
Mapper button is active when a model is selected. The update of a model make all IEDs which use
this model to be updated to allow structure modification if needed. When importing a model file, if it’s
an ICD file, it is automatically transformed to an XML file. Then, for all imported model file, the IED
Mapper is called to review classes association if needed.
4.7.11.1 THE IED MAPPER

By clicking the IED Mapper button the following dialog box is displayed:
Figure 208: The IED Mapper dialog box

This window allows user to associate private classes of a non DS Agile IED to common classes defined in
DS Agile.
This work is necessary for DS Agile equipment to understand what other equipments say.
This association map an unknown type of data (called Private Class) to a known one (called Common
Class). It works on attributes defined for these data to matching them.
The title bar of this dialog displays the currently edited file. In this way, when importing multiple files, the user
knows on which he work.
There are three panels:
 The private class presents the list of private classes in tree view, to view the contents of each class,
 The common class presents the list of classes known by DS Agile equipment, in tree view too,
 The bottom panel is a log of actions.
The goal of this dialog is to associate a private class to a common class. To do this the user has five actions
represented by five buttons:
 “Associate” is used to associate the private class selected in left panel to common class selected in
right panel,
 “Dissociate” remove association of currently selected private class

 “Search exact CDC” indicate to user the common class which match exactly the selected private class,
if it exists, select it in common class list, and write it in log panel,
 “Search similar CDC” indicate to user the common classes which looks like the selected private class,
if it exists, select the first one in common class list, and write them in log panel,
 “Associate Auto” launch a process which search all matching common classes for all private ones and
associate them automatically if found.
The two latest buttons are use to quit IED mapper, the first without saving, and the second with saving the
model.
When a private class (or sub-class) is associated to a common class, it’s shown by adding the common class
name on left of the arrow (->)
When an association is done manually, if some sub-classes are not automatically mapped, a subclass
association dialog box is displayed to allow user mapping them manually:

Figure 209: Subclass Association Dialog Box
It works like main dialog box, but specialized for a subset of classes.
After closing this dialog box, the association is done.
4.7.12 DATA/ UPGRADE TO INDEXED PROFILE & DATA/ INDEXED PROFILES MERGE
Refer to the chapter C26x/EN AP.
4.8 WINDOW
For a full description of this menu, see section 3.2.2 Selecting displayed areas in working window
4.8.1 SEARCH TOOL BAR

The Search tool bar allows searching quickly some objects inside the navigator. The search key is the
short name or the long name of the displayed objects. Simple shortcuts allow navigating through theses
found objects into the navigator.
The set of found objects can be displayed into a table and copied for pasting in Excel for example.
Search Criterion
A dedicated toolbar allows defining the quick search criterion:
1 Type in the string to search; the search is NOT case sensitive. The string can match only a part of the
target attribute (shortname or longname)
2 To add options, click the Magnifier button:

and select the domain of the search:

 Global requires to search in the database tree for the current mode (template / object)
 Local limits the search to the database sub-tree of the currently selected node
To set a local sub-tree, check the line (the check sign turns into when passing the mouse over
the line):
and/or the choice of the target attribute and the target object type:
 Short name: available for all kind of object. It represents the object into navigator
 Long name: applicable only for datapoint. Only datapoints and their long name are taken into
account during the searching.
Execution
1 Click the green icon :
If no result has been found, the background turns red as long as the mouse is on the icon:
Otherwise, the first match appearing in the navigator get selected.

2 To pass from a match to the following, click the yellow icon  or 
When the last match is reached, the background turns blue as long as the mouse is on the
icon:

Table Display & Navigation

3 Click the right button; a table lists all found objects in a tab of the Search window; the number of
matches displays in the tab label: Quick “<string>” (number)
To adjust a column width, pass the cursor over the border in the header till the cursor turns to ; then drag
and drop.
To locate a match in the navigator, double-click the object row.
The Search criteria can be refined in this tab: all criteria are displayed and can be updated. The quick search
can then be re-executed.
4 To sort out the rows alphabetically/numerically/hierarchically in decreasing order, click each column
header several times till the arrow  shows after the column label.
5 To filter the rows according to a column field, click the button v and select one value in the combo
list; as a result, a funnel shows before the column label. To suppress the filter, select the value (All).
6 To export the table to a spreadsheet editor like Excel, select the rows and copy/paste them using the
contextual menu; for headers, use the menu item Copy columns header

5 TRACES WINDOW
This area of the docking window is reserved for database developers. The aim is to study trouble at
maintenance level, and to keep precise traces of database modifications (for example between two
database evolutions asked by customer).
Figure 210: Trace window display
The display is based on 5 resizable columns with:

1 The Level field is one of the following trace levels: Information, Error, Warning, Debug, Fatal Error.
2 The Date field is the recording date/time of the trace.
3 The User field is the identification of the logged user.
4 The Source field is the DS Agile SCE class component that generates the trace. It is displayed only
when Debug traces are displayed.
5 The Message field is the text message of the trace.
Trace management is driven by 4 icons:
Save the displayed traces in a file selected through a file chooser.
Clear the table. Traces are saved in the log file of the open configuration
Toggle for DEBUG traces: If this button is selected, the DEBUG level traces are not displayed (they are
Toggle for traces from event manager of the DS Agile SCE software (operator actions…)
5.1 TRACE SAVING

User saving:
The User can save the displayed traces in a file selected through a file chooser. The current log file is then
saved into the given file. The file could be edited by an text editor. Field separator is a tab character.
Specific saving for configuration upgrades:
During opening of a configuration, an upgrade can be occurred (see File/Open). The traces sent by the
upgrade process are automatically saved in a specific file. The file name is log<v.r>.txt, where <v.r> is the
release number of the target configuration. It’s stored in the configuration file. This file is a zip file.

Example:
A configuration database conf.mpx is opened with Alstom DS Agile SCE with a release number 3.34. This
operation needs an upgrade of the configuration database. The upgrading operations are logged in a file
log3.34.txt. This file is stored in configuration database file conf.mpc which is a zip file.
With this feature, all upgrading operation of configuration database in stored in its file and could be
consulted. The files of .mpc are the following:
Figure 211: MPC contents and Upgrading Actions Log Files
Automatic saving:
The maximum number of traces in the table is configured in the General Settings.
When this maximum is reached, the non DEBUG level traces are automatically saved in the log file of the
open configuration and the table is cleared. The file name is log.txt. It's stored in the configuration zip file.
If the size of the current log.txt file is greater than 15 MB, then this file is saved as log(i).txt (where i is an
incremented number) and a new log.txt file is created for the new traces.
When the Check-In action is applied to a configuration, the traces are automatically saved in the frozen
configuration, the log file of the current configuration is reset.
When the Check-Out action is applied to a configuration, the new work configuration is created from the
frozen one, but the trace file (if any) is discarded.
configure Save Close

conf.mpx conf.mpx conf.mpc conf.mpx conf.mpc
if count of traces > max Save in conf.mpx\log.txt Clear traces table

then
Save in conf.mpx\log.txt
+
Clear traces table
Figure 212: Log and File Operations (1/3)

Open
conf.mpc conf.mpx
Loads the last max/100 traces

from the conf.mpx\log.txt file (if
max < 100, loads max traces).
+
Checks checksum of each log
file.
Check In Check Out

conf.mpx conf.0.1.mpc conf.mpc
Save the conf.mpx\log.txt

No conf.mpx\log.txt in
+
the new work
Saves the content of the mpx in the
configuration.
conf.0.1.mpc
+
Deletes the log files of the current
configuration (in the mpx)
5.2 TRACE LOG FILE CHECKING

An ADLER32 checksum is associated to each log file (except upgrading log files).
When a configuration is opened, all the log files are checked. If one of them is missing or has its checksum
not matching the one registered, then an error trace is displayed:
Corrupted traces log file
This feature prevents some external wrong manipulation of log files: any external modifications (add,
suppress, modification of a log line; or add, suppress of a log file) are traced by this error.


MAINTENANCE
SCE/EN MF/C60
DS Agile System Configuration Editor Maintenance
Contents
1 GENERATED FILES 3
2 CHECKS 4
2.1 Check user interface 4
2.2 Graphic symbols used in this document 5
2.3 General checks 6
2.3.1 Internal error 6
2.3.2 Objects in Temporary area 6
2.3.3 Capacity limits 6
2.3.4 Variant attributes value 8
2.3.5 Relations 8
2.3.6 Templates 10
2.4 System checks 10
2.4.1 TCP/IP definition on Ethernet Network 10
2.4.2 SNTP servers 11
2.4.3 IEC 61850-8-1 Physical Devices 11
2.4.4 Wave Records of DS Agile C26xs 28
2.4.5 Channels 31
2.4.6 Gateway server 33
2.4.7 Legacy Networks 33
2.4.8 SCADA Networks 39
2.4.9 Command arbitration for SCADA Networks 47
2.4.10 Taking Control function 48
2.4.11 Non DS Agile IED on IEC 61850-8-1 50
2.5 Electrical checks 51
2.5.1 Substation 51
2.5.2 Voltage Level 51
2.5.3 Bay 51
2.5.4 Bay Mimic 52
2.5.5 Switchgear 53
2.5.6 Circuit Breaker 53
2.5.7 Automation 59
2.5.8 Tap Changer 62
2.5.9 AutoRecloser function 63
2.5.10 Synchrocheck function 67
2.5.11 ATCC function 68
2.5.12 Protection module 69
2.5.13 Topology 71
2.5.14 Fast Load Shedding 71
2.5.15 Load shedding/ Load Curtailement 71
2.5.16 I²t function 71
2.5.17 AVR Function 72
2.5.18 VTFuse Function 73
2.6 Graphical checks 74
2.6.1 O I Workspace 74
2.6.2 OI Window 75
2.6.3 OI Mimic 75
SCE/EN MF/C60 MF-1

Maintenance DS Agile System Configuration Editor
2.6.4 Bay Mimic symbols 76

2.6.5 Standard Command Banner 78
2.6.6 OI symbols 78
2.6.7 Bitmaps 83
2.6.8 Alarm Groups 87
2.6.9 User Profile 87
2.6.10 Memo 87
2.7 Datapoints checks 88
2.7.1 Datapoint Profiles 88
2.7.2 Acquisition / Control Source definition 94
2.7.3 Client / Server definition 101
2.7.4 Datapoints constraints 114
MF-2 SCE/EN MF/C60

1 GENERATED FILES
In the folder set by the field Path to export files (C:\Temp by default): a log file dw.log records each database
opening session; when any exception occurs, a new popup displays this exception and the displayed trace is
added to the log file.
In the folder set by the field Path to save databases: an .err file is created in event of error.
SCE/EN MF/C60 MF-3

2 CHECKS
This section presents the list and the corresponding explanations of the error/warning messages displayed
the checks tab of the log window.
Theses errors or warnings are raised during the comprehensive consistency check of the current
configuration. The check function is available via menu item file/check (shortcut F6).
Checks are performed according to the following steps:
 General checks
 System checks
 Electrical checks
 Graphical checks
 Datapoints checks
Spare objects are not processed.
Objects in Temporary area are not processed.
Referenced document is SCE Check Specification-DSL2-Issue B1.
2.1 CHECK USER INTERFACE

The system displays check traces in the following table of the Traces panel ("Checks" tab):
Figure 1: Check result table
MF-4 SCE/EN MF/C60

Table rows:
 Each row corresponds to one check operation whose result is an error or a warning or information.
Table columns:
 First column:
The user can check On/Off this column to remember which error/warning he tried to correct.
 Level:
Icon of error, warning or info.
 Code:
Identifier of the error, warning or info message. Each code and its level are defined below.
 Type:
Identifier of the check operation.
Example: "CircuitBreaker" is a check consisting in verifying the configuration of a Circuit breaker
(missing datapoints, … ).
 Reference:
For each check operation, an Object implicated in the check operation, is considered as the main
Object. The column displays the external Id of this Object. If the user activates the "Reach" action on
the row, this Object is retrieved in the SCE browsers and selected.
 Message:
It displays a message explaining the error/warning/info for the check operation.
The panel of the Table contains also the following buttons:
 Errors filter toggle button:

If the button is selected, the Error traces are not displayed (they are filtered). Else they are.
 Warnings filter toggle button:

If the button is selected, the Warning traces are not displayed (they are filtered). Else they are.
 Info filter toggle button:

If the button is selected, the Info traces are not displayed (they are filtered). Else they are.
 Checked traces filter toggle button:

If the button is selected, the Checked traces are not displayed (they are filtered). Else they are.
2.2 GRAPHIC SYMBOLS USED IN THIS DOCUMENT

Check messages are written here with the following indications:
 the Error ( ) or Warning ( ) flag
 the error or warning code

 the check identification
 the check message
The User Interface of the check table is described in the chapter SCE/EN HI.
Relation and Attribute representation in figures:
SCE/EN MF/C60 MF-5

 A relation is marked with a (R).

In the example below, the "Feeder" is linked to the DS Agile C26x bay controller unit by the "is
managed by" relation.
Feeder (R) is managed by C264
 An attribute is marked with a (A).

In the example below, the "spare" attribute of the "Feeder" is set to the "No" value.
Feeder (A) spare No
The configuration of Relations and Attributes is described in the User Manual of Alstom DS Agile SCE.
2.3 GENERAL CHECKS
2.3.1 INTERNAL ERROR

In case of an exceptional error, internal to the check process, the stack trace is displayed with the following
message:
00001 / CheckAbort / Check internal error
2.3.2 OBJECTS IN TEMPORARY AREA

The temporary area must not contain any object which is not spare.
01002 / TemporaryObjects / There are objects in temporary area
2.3.3 CAPACITY LIMITS
Component Maximum authorised

OI client on a per OI server basis (1) 8
OI server 1+ 1 redundant
Printers OI level 4 (* 2 if redundant)
Printers controller level (1) 1
IED on a per Legacy Bus basis (1) 16
IEC devices (Controllers and Generic IEDs) 150
SCADA Networks in the system 16
For a whole Alstom DS Agile system:

Logical Plant Item Maximum authorised
Substation (1) 40
Voltage Level 4 if ATCC used
Bays 512
Circuit breakers (XCBR) 512
Disconnectors (SWIT) 2048
Transformers (TXF) (2) 512
Generic modules 4096
MF-6 SCE/EN MF/C60


Datapoints 48000
Digital Input Points (SPS, DPS, MPS) 37500
Measurements (MV) 7500
Invalid count of server/client measurement datapoints for this controller (count, max):
Counter 512
TPI 512
Output Control Points (SPC, DPC) 5000
Setpoint Outputs (digital or analogue) 512
Run Report 255
LSP data point 300
For one C26x controller:

Logical Module Maximum authorised
Transformers (TFX) per controller 128
Circuit Breakers (XCBR) per controller 128
Disconnectors (SWIT) per controller 512
Measurements per controller (Client and Server MV) 2400
Measurements datapoints wired on AIU per controller 48
Process Bus IED subscriptions 15
(1) Locked by the Structural Database.
(2) The Structural Database locks the count of Transformers per Bay-Transformer to 1. So the maximum
count of Transformers follows the count of Bay-Transformers.
Additional checks:
The check of the count of Symbols per "Comp. workspace" and per "Bay mimic" is described in section
2.6.4.1 Symbols.
02003 / CapacityLimits / The count of … components is not valid (count, maximum)

Examples:
02003 / CapacityLimits / The count of OI server components is not valid (count, maximum)-> [3, 1]
Error if the count of measurement datapoints wired on AIU per controller is greater than 48
02378 / CapacityLimits / Invalid count of measurement datapoint wired on AIU for this computer
(count, max)->[50, 48]
Case of Gateway as buffered report client:
Error if the relation "Has for buffered report client" is connected to a gateway AND there is more than one
gateway and the related backup
02339 / CapacityLimits / The number of gateways is not coherent with the relation 'has for buffered report
client' configured on gateway
SCE/EN MF/C60 MF-7

2.3.4 VARIANT ATTRIBUTES VALUE
Note: These checks are not processed for backup devices.
An attribute value can be dependent of another attribute value.

In the following example, the "C26x SCADA Prot." has 2 attributes: "protocol" and "address structure".
The set of possible values for "address structure" depends on the selected value for "protocol".
C264
C26x SCADA Prot (A) protocol
- T101
depends of - DNP3
- T104
(A) address structure
- Address on 8 bits (1 byte)
- Address on 16 bits (2 bytes)
- Address on 8 bits.8 bits
- Address on 8 bits.8 bits.8 bits
At the User Interface, the modification of the "protocol" value may lead to an incompatible "address structure"
value.
06101 / AttributeValue / The attribute value is not valid

Example:
06101 / AttributeValue / The attribute value is not valid-> [Scs | Ethernet network | C264 | C26X SCADA prot
| address structure]
2.3.5 RELATIONS
The check of a relation depends on its definition in the Structural Database.
 A "Mandatory" flag is set to NO on a relation for which the link can be omitted.
Object
(R)
Relation link No link
Mandatory = NO OR
Spare link
If the relation is not linked, then the following message is displayed:
03008 / RelationLinkNull / The optional relation has no link

Examples:
03008 / RelationLinkNull / The optional relation has no link-> [Site | Substation | Voltage level | Feeder | has
for lock right: <null>]
If the relation is linked to a spare object, then the following message is displayed:
04010 / RelationLinkSpare / The optional relation has a spare link
MF-8 SCE/EN MF/C60

Examples:
04010 / RelationLinkSpare / The optional relation have a spare link-> [Site | Substation | Substation DPC |
has for AutoManu dependency: Substation DPS]
Some optional relations may have a specific rule which does not produce a warning if not filled. These rules
are listed below:
 C26x SCADA protocols have the relation with a “main comm. port” which does not have to be filled in
case of T104 protocol,
 GHU200 Boards have a relation with a workspace which does not have to be filled when HMI type is
Simple.
 Virtual Inputs under IEC61850 Gen IED have a relation with input datapoints which does not have to
be filled
A "Mandatory" flag is set to YES on a relation for which the link is mandatory.
Object (R)
Relation link No link
Mandatory = YES Or
Spare link
If the relation is not linked, then the following message is displayed:
03007 / RelationLinkNull / The mandatory relation has no link

This check is not treated if the relation is:
 a UCA2 addressing relation

 a “UserFunction_RunsOn_PLC” of an Interlock FBD that belongs to a bay managed by a non DS Agile
IEC 61850-8-1 IED
Examples:
03007 / RelationLinkNull / The mandatory relation has no link-> [Site | has for Bypass right: <null>]
If the relation is linked to a spare object, then the following message is displayed:
04009 / RelationLinkSpare / The mandatory relation has a spare link

Examples:
04009 / RelationLinkSpare / The mandatory relation have a spare link-> [Site | Substation | Substation DPC |
has for profile: DPC profile]
 If a filter is defined for a relation, the link must be compatible with the filter definition.
Object
(R)
Relation link
Filter link  Filter
05011 / RelationLinkFilter / The relation link is not compatible with the filter
Examples:
05011 / RelationLinkFilter/The relation link is not compatible with the filter-> [Site | Substation | Voltage level |
Feeder 1 | circuit breaker | Comp. swit. pos. | 'open' wired on: DI # 0]
SCE/EN MF/C60 MF-9

2.3.6 TEMPLATES
The goal of these checks is to warn user about template coherency. For templates, check if all components
are present in all instances or clones.
This check indicates the template and instance concerned, and the component which are missing. If the
component is a template clone, indicate only the main template.
The way to correct this error is to delete the missing component in the template and to recreate it.
68213 / Templates / One instance of the template is not coherent with the template definition (Template,
Instance, missing component)
Example:
68213 / Templates / One instance of the template is not coherent with the template definition (Template,
Instance, missing component) -> [Site-Feeder-Feeder1 | Feeder1, Site | Substation | Voltage level | Feeder
1, Circuit breaker]
68215 / Templates / One instance of the template is not coherent with the template definition, a root
component is missing (Template, Instance, missing component)
A template can only use 1 sub-level of template, i.e. a maximum level of inner template is 2.
68254 / Templates /Number of inner templates reached (number, maximum)
2.4 SYSTEM CHECKS
2.4.1 TCP/IP DEFINITION ON ETHERNET NETWORK
Ethernet Network (A) TCP/IP address

C264 255.255.255.255
OI server
Bay OI (A) network name NW_NAME
IEC gateway
IEC gen IED
OI client
Each device connected to an Ethernet Network has 2 attributes "TCP/IP address" and "network name".
 The "TCP/IP address" value of a device, must be unique among all the devices per Ethernet
Network.
 The "network name" value of a device, must be unique among all the devices per Ethernet
Network.
 The network name (alias TCP/IP) must not be reserved by operating system.
Exception:
Unicity is not required between an OI server and an OI client embedded in the same physical device.
Therefore, if an "OI client" is linked to an "OI server" through the relation "has for HMI server", then it is not
checked.
It is not required either for a T104 IED that has the same IP address under the main and standby Gateway.
07012 / TCPIPattribute / The attribute value is not unique

Examples:
07012 / TCPIPattribute / The attribute value is not unique-> [TCP/IP address, 255.255.255.255]
07012 / TCPIPattribute / The attribute value is not unique-> [network name, NW_NAME]
MF-10 SCE/EN MF/C60

07164 / TCPIPattribute / The network name is reserved by operating system
2.4.2 SNTP SERVERS

On SCS object, it is possible to configure the TCP/IP addressing for SNTP server (primary and auxiliary
addresses).
These addresses may reference an existing device in database or devices outside the Alstom DS Agile
system.
Some rules must be followed for these addresses.
 If one of both IP addresses is configured and represent a DS Agile device, this device must be a
controller.
07249 / TCPIPattribute / The DS Agile SNTP server must be a computer (IP address, device)
 If auxiliary IP address is configured primary address must be configured too.

07250 / TCPIPattribute / The primary SNTP address must be configured if auxiliary is configured
 Primary and auxiliary addresses must be different when configured.

07251 / TCPIPattribute / The two SNTP addresses must be different (IP address)
If the SNTP server (main or auxiliary) is a controller having its synchronisation source as “IRIG-B”, the
datapoint “External clock status” is mandatory for it:
07292 / TCPIPattribute / The datapoint “External clock status” is required on the computer running a
SNTP server service
2.4.3 IEC 61850-8-1 PHYSICAL DEVICES
2.4.3.1 REDUNDANCY
2.4.3.1.1 DS Agile redundancy
(R) has for backup

C264 (main) C264 (backup)
(R) is backup of
(R) has for backup

C264C (main) C264C (backup)
(R) is backup of
(R) has for backup

OI server (main) OI server (backup)
(R) is backup of
 For a device, the relations "has for backup" and "is backup of" are mutually exclusive.
30044 / Redundancy / The relation types are not compatible-> [has for backup, is backup of]
A main and its backup must be devices of the same type.
30073 / Redundancy / The main and the backup are not of the same type
Examples:
30073 / Redundancy / The main & the backup are not of the same type-> [OI server, C264]
SCE/EN MF/C60 MF-11

 A main device and its backup must be under the same parent.
30406 / Redundancy / The main and the backup are not under same parent ‘component or section’
respectively
2.4.3.1.2 C26x-Standalone redundancy
Redundancy of a C26x-Standalone is managed by the attribute “number of masters”. If it is set to 2, it is
considered as redundant.
A redundant C26x-Standalone mustn’t manage ISaGRAF or FBD functions.
78267 / C264R / A redunded C264R mustn’t manage Isagraf or FBD functions.

2.4.3.1.3 Incompatible components for controllers in redundancy architecture
For a C26x in redundancy architecture, the objects that follow are not compatible:
 TMU 210 board

 Redundant T101 master
30297 / Redundancy / Scs / Ethernet network | C264 | TMU210 / Not compatible component on a C264
redounded
2.4.3.2 CLIENT - SERVER RELATION ON IEC 61850-8-1
 A Client must not be linked to the same Server through multiple relations "has for IEC server".
(R) has for IEC server

C264_1 (client) C264_2 (server)
(R) has for IEC client
08013 / RelationClientServer / Multiple links to the same server

Examples:
08013 / RelationClientServer / Multiple links to the same server-> [has for IEC server: C264_2]
 Case of "OI server" Client:

The attribute "goose usage", of the relation "has for IEC server", must be set to the "Data model only" value.

OI server (client) OI server 2 (server)
(A) modeling / goose usage

- Data model only
- Goose only
- Data model and Goose
08107 / RelationClientServer / The relation attribute value is not valid. It must be: Data model only
MF-12 SCE/EN MF/C60

Examples:
08107 / RelationClientServer / The relation attribute value is not valid. It must be: Data model only-> [has for
IEC server: OI server, modelling/goose usage = Goose only]
 For a relation client-server with data model usage = data model with or without GOOSE, a DS Agile
C26x cannot have more than 10 clients and/or 50 servers. The client-server relations with GOOSE
only are out of the scope of this rule.
Notes: With the maximum number of 10 clients, non-configured clients such as the equipment simulator (no longer
supported) are not taken into account. The number of non-configured clients is defined by a constant in the settings.
With the maximum number of 10 clients, non-configured clients such as SMT are always taken into account.
For a given controller, the user can establish up to 9 actual client relations.
Exception: GOOSE client-server relations which are out of the scope of this rule.

C264_1 (client) C264_2 (server)
(R) has for IEC client
<08141> / RelationClientServer / More than 9 clients for the same computer server
<08140> / RelationClientServer / More than 50 servers for the same computer client
2.4.3.3 IEC 61850-8-1 MAPPING ON ETHERNET NETWORK

2.4.3.3.1 Mapping definition
Note: These checks are only processed for non-backup devices.
SCE/EN MF/C60 MF-13

Example of IEC61850Mapping in a Controller:
(A) protocol
Ethernet network IEC 61850
C264
c26x IEC Map
IECxLD
GenLN
CO
DPCxSBOxS
belongs to the list of generic
IEC LD0 - C26x LogicalDevices of the "c26x IEC Map"
C26xDIAG
IEC ST for C26xDIAG
AIUSt0
T103 (Legacy Network)

T103_IED
ext IEC Mapping
LDxIED
IEDDIAG
IEC ST IEDDIAG
CommSt
c26x SCADA Prot (SCADA Network) continuation of

ext IEC Mapping LD0 definition
IEC LD0 - TCI
TCIDIAG
IEC ST TCIDIAG
CommSt
 For each Physical Device on the "Ethernet network":

 1, and only 1, IEC 61850-8-1 Mapping, is allowed.
 this Mapping must be compatible with the value ("IEC61850") set to the "protocol" attribute of the
"Ethernet network".
During auto-addressing, the IEC61850 mapping would be created only for the objects. For any instantiated template,
the user needs to add the IEC mapping table in the template before performing auto-addressing.
13110 / EthernetMapping / The component is missing
13109 / EthernetMapping / The component is not allowed

Examples, for an IEC 61850-8-1 "Ethernet network" protocol:
13109 / EthernetMapping / The component is not allowed-> [C26x IEC Map.]
 For each Legacy Device on a Legacy Network and, for each SCADA Network:
 1, and only 1, IEC 61850-8-1 extended Mapping, is allowed.
 this extended Mapping must be compatible with the value ("IEC61850") set to the "protocol"
attribute of the "Ethernet network".
13110 / EthernetMapping / The component is missing
13109 / EthernetMapping / The component is not allowed

Examples, for an "IEC61850" protocol:
13109 / EthernetMapping / The component is not allowed-> [ext IEC Mapping]
MF-14 SCE/EN MF/C60

 For each Logical Device defined under the IEC Mapping:

 its name must be unique in the mapping. LD name is prefixed by Alias TCP IP and by IED name
(uniquely for legacy IED LD).
 For DS Agile IED, if the Logical Device is a generic one, its name must not contain the sub-string
"LD0" (reserved for system Logical Devices).
Examples:
In the "c26x IEC Map" mapping: "IECxLD" name must be unique among all the generic Logical Devices of
the "c26x IEC Map" + of all the "ext IEC Mapping" of Legacy Devices, and it must not contain the sub-string
"LD0".
13020 / EthernetMapping / The name is not unique
13021 / EthernetMapping / The name is not valid

Examples, for an IEC 61850-8-1 "Ethernet network" protocol:
13020 / EthernetMapping / The name is not unique-> [LD]
13021 / EthernetMapping / The name is not valid-> [genLD0]
 For each Brick/LogicalNode defined under a Logical Device:

 its name must be unique in the Logical Device
Examples:
 In the "c26x IEC Map" mapping:

"GenLN" name must be unique among all the Logical Nodes of the "IECxLD" Logical Device.
"C26xDIAG" and "TCIDIAG" names must be unique among all the Logical Nodes of the "LD0" Logical
Device (i.e., among all the Logical Nodes of "IEC LD0 - C26x" + of "IEC LD0 - TCI").
 For each Data Object defined under a Functional Component (CO):

 its name must be unique in the Functional Component
Examples:
 In the "c26x IEC Map" mapping:

"DPCxSBOxS" name must be unique among all the Data Objects of the "CO" Functional Component.
 For each Data Object defined under a Functional Component:

 Only one relation "has for IEC address" is allowed (0 or 1)
27113 / EthernetAddressing / Multiple links
 For the following Functional Component types of a C26x:

 MX
 ST
the maximum count of DataObjects is 50.

Examples:
02003 / CapacityLimits / The count of OI server components is not valid (count, maximum)-> [3, 1]
2.4.3.3.2 IEC Goose
SCE/EN MF/C60 MF-15

For a given C26x, the size of the goose for SPS,DPS, MPS must be less or equal to 1250 bytes. Idem for the
size of the goose for measurements and counters.
<54142> / GooseLimits / Goose limit is reached for binary inputs
<54143> / GooseLimits / Goose limit is reached for measurements

For a given C26x the size of the goose for LSP must be less or equal to 3750 bytes.
<54243> / GooseLimits / Goose limit is reached for LSP

In a database, all Goose ID must be unique for a network.
58170 / GooseUnicity / Goose ID (AppID) must be unique for network

In a C26x IEC 61850-8-1 mapping, the Goose Rank attributes of each ST and MX goosed DataObject (Auto
or Manu) must be consecutive, starting from 1, and unique (without duplication).
Exception:
A DataObject linked to a DataPoint typed ‘Module_nMPS’ datapoint type is not affected by the 3 following
checks : 32332, 32333 and 32334.
32332 / HoleInGooseRanks / There are holes at Goose Rank attributes level [device, goose type]
32333 / DuplicationInGooseRanks / There are duplications at Goose Rank attributes level [device,
goose type]
32334 / GooseRankNotAllocated / There are goosed dataobjects with a Goose Rank of 0 [device, goose
type]
Examples:
32332 / HoleInGooseRanks / There are holes at Goose Rank attributes level [device, goose type]-> [Scs
|SBUS| CTE_TG225kV, ST ]
32333 / DuplicationInGooseRanks / There are duplications at Goose Rank attributes level [device, goose
type] -> [Scs |SBUS| CTE_TG225kV, MX ]
32334 / GooseRankNotAllocated / There are goosed dataobjects with a Goose Rank of 0 [device, goose
type] -> [Scs |SBUS| CTE_TG400kV, ST ]
2.4.3.3.3 IEC Goose of Functional Components ST or MX
<xxxxx> / Goose ranks contiguous

When a DtObj shows as NOT 'transmitted by goose', its Goose rank sets to an undefined value or
When there is a gap in the Goose ranks and they are not contiguous as occurs in event of DtObjs not
'transmitted by goose' any more.
<xxxxx> / Goose ranks identical

When the Goose rank is identical for two DtObjs.
<xxxxx> / Goose ranks not allocated

When some DataObjects have their Goose Rank to 0.
You can fix it using the SCE search with Types= IEC STDataObject (or MXDataObject) and Attibutes =
Goose characteristics
Change the value ‘goose rank’ directly in the table. Please refer to the snapshot that follows.
MF-16 SCE/EN MF/C60

2.4.3.3.4 Addressing of OI printer System Datapoints
OI server
HMI IEC Map.
LD0 for OI
HMIDIAG
ST for HMIDIAG
SOE1St0
SOE1St1
SOE2St0
SOE2St1
SLB1St0
SLB1St1
SLB2St0
SLB2St1
(A) printer
OI printer Sequence of Events
System infos (R) has for IEC address
Printer status SOESt
(R) has for IEC address
BackupPrint stat SOESt
(A) printer
OI printer Log Book
Printer status SLBSt
BackupPrint stat SLBSt
 If the "OI printer" has its attribute "printer type" set to the "Sequence of Events" value, then its system
Datapoints "Printer status" and "BackupPrint stat." must be linked to an IEC address named
"SOESt". Only 1 relation is allowed.
 If the "OI printer" has its attribute "printer type" set to the "Log Book" value, then its system Datapoints
"Printer status" and "BackupPrint stat." must be linked to an IEC address named "SLBSt". Only 1
relation is allowed.
27050 / EthernetAddressing / The relation link is not valid

2.4.3.3.5 Addressing of OI client System Datapoints
SCE/EN MF/C60 MF-17

OI server
HMI IEC Map.
LD0 for OI
HMIDIAG
ST for HMIDIAG
HMISt0
HMISt1
HMISt2
HMISt3
HMISt4
HMISt5
HMISt6
HMISt7
(R) has for HMI server
OI client
OI client link HMISt
 The system Datapoint "OI client link" of an "OI client" must be linked to an IEC address named
"HMISt". Only 1 relation is allowed.
27050 / EthernetAddressing / The relation link is not valid

Example:
27113 / EthernetAddressing / Multiple links-> [has for IEC address : HMISt0]
27113 / EthernetAddressing / Multiple links-> [has for IEC address : HMISt2]
2.4.3.3.6 Addressing of Controller boards Status Datapoints
C264
C26x IEC Map.
LD0 for C26x
C26xDIAG
ST for C26xDIAG
DIUSt0
DIUSt1
DIUSt2
DIUSt3
…
(A) physical board number 0
DIU200
DIU status DIUSt0
 The status Datapoint of a Controller board must be linked to an IEC address with a name matching the
board type and ending with the value of the attribute "physical board number". Only 1 relation is
allowed.
27067 / EthernetAddressing / The address in not compatible with the board number
Example:
27067 / EthernetAddressing / The address in not compatible with the board number-> [has for IEC address:
DIUSt1, DIU200.physical board number = 0]
MF-18 SCE/EN MF/C60

2.4.3.4 C26X BOARDS
Note:
These checks are only processed for non-backup Controllers..
Count of boards in a 80TE controller:

A B C D E F G H I J K L M N O P Q
BIU CPU
Slots from C to Q may contain a board of the following types:

 AIU2xx
 DOU2xx
 DIU2xx
 CCU2xx
 AOU200
Slot Q may contain 1 TMU200/TMU210/TMU220 board or 1 board of the above types.
 If a TMU200/TMU220 is present, then the maximum number of other boards is  14

 If a TMU210 is present, then the maximum number of other boards is  13
 If no TMU2xx is present, the maximum number of boards is  15
Count of boards in a 40TE controller:
A B C D E F G H
BIU CPU
Slots from E to F may contain a board of the following types:
 AIU2xx
 DOU2xx
 DIU2xx
 CCU2xx
 AOU200
Slots G & H may contain 1 TMU200/TMU210/TMU220 board or 2 boards of the above types.
 If a TMU200/TMU220 board is present, then the maximum number of other boards is  4

 If a TMU210 board is present, then the maximum number of other boards is  3 (the CPU's DSPIO
daughter board is in slot C)
 If no TMU2xx is present, the maximum number of boards is  6
09144 / ComputerBoards / The count of TMU boards is not valid (count, maximum)
09145 / ComputerBoards / The count of AIU boards is not valid (count, maximum)
09003 / ComputerBoards / The count of Board components is not valid (count, maximum)
SCE/EN MF/C60 MF-19

Examples:
09003 / ComputerBoards / The count of Board components is not valid (count, maximum)-> [6, 4]
 Attribute "physical board number" of a board.
C264 (A) board number

AIU200 1
DOU200
DIU200
CCU20x
For boards AOU200, AIU201, AIU210, DIU200, DIU210, DOU200, CCU200, the "board number" attribute
values must be unique and contiguous. This board number is a user defined physical number.
For boards DIU211, DOU201, CCU211 (boards managing the slot number), the board number is a computed
logical number. It is unique and contiguous by board type.
09015 / ComputerBoards / The attribute value is not unique for the board type
09016 / ComputerBoards / The attribute values are not contiguous for the board type (board type,
attribute)
Examples:
09015 /ComputerBoards / The attribute value is not unique for the board type-> [physical board number, 1]
09016 / ComputerBoards / The attribute values are not contiguous for the board type (board type, attribute)->
[CCU200, physical board number]
09346 / ComputerBoards / For each type of board, the smallest “Board Number” attribute values must be
equal to the value 0.
For each type of all cards (e.g.: DIU, DOU, CCU, AIU, AOU), the smallest “Board Number” attribute values
must be equal to nought value.
 Attribute "slot number" of a board managing the slot number.
C264 (A) slot number

DIU211 C
DOU201
CCU211
For boards managing the slot number, the "slot number" attribute values must be unique.
09282 / ComputerBoards / The attribute value is not unique for boards of rack
Example:
09282 / ComputerBoards / The attribute value is not unique for boards of rack -> [slot number, C]
 GHU200 board.
The GHU200 board has an attribute "HMI type" and a relation "has for workspace".
MF-20 SCE/EN MF/C60

C264 - Simple
(A) HMI type
GHU200 - Complete
Led # 4 - Old
(R) has for workspace
(R) displays state of Graphic

Comp. workspace
SPS
DPS
 If the value of the "HMI type" attribute is different from "Complete", then the relation "has for
workspace" must not be linked:
09078 / ComputerBoards / The relation link is not compatible with the board type-> [has for workspace:
Comp. workspace, HMI type = Simple]
If the default panel for start or inactive is Graphical Bay Panel ‘n’, ‘n’ must be lesser or equal to number of
Graphical Bay Panel configured:
09306 / ComputerBoards / The usage of the graphical bay panel 'n' as default is allowed only if up to 'n'
graphical bay panel are configured (number of graphical bay panel) -> [12]
 If the value of the "HMI type" attribute is "Simple", then "Led#5" must not be used (no relation link from
"Led#5" to a Datapoint):
35077 / BoardLeds / The use of this LED is incompatible with the board type (type)-> [HMI type =
Simple]
 If the value of the "HMI type" attribute is "Simple", Led object cannot have a “displays state of ”
relation with attribute “Led behaviour” equal to “used for alarm”:
35217 / BoardLeds / The attribute “Led behavoir” on relation “has displays state” can be “used for alarm”
only when GHU200 board is “Complete”.
 A led can be used by a data point only if this data point is managed by the same controller than the
controller bearing the led:
35227 / BoardLeds / Board led can be use only by data point managed by the led server
 Only led #14 to led #17 can be used by a data point if the led allocation is set to predefined at the
GHU board level:
35281 / BoardLeds / The use of this LED is incompatible with the predefined led allocation
 TMU200, TMU210 and TMU220 boards

These boards are exclusive one another for the same controller.
<09139> / ComputerBoards / TMU200, TMU210 and TMU220 cannot belong to the same computer.
 TMU210 board
When used, its DO channel can only be wired to the open or close states of the Switch Control DPC of a
breaker.
DO#0 (DO#1 (NO)) can only be wired on open state. DO#4 (DO#5 (NO)) can only be wired on closed state.
09180 / ComputerBoards / DO channels of TMU210 can only be used for open (DO_1) or close (DO_5)
states of the Switch Control DPC of a breaker
SCE/EN MF/C60 MF-21

When used, the protection function “automatism” is mandatory because the SPS “synthesis of
instantaneous” defined under it is mandatory.
This check is not done for following cases:
 SCE is ‘Poste d’application (i.e., lax flag sce.Poste_d is set).

 an internal Synchrocheck of type 2 is configured in SCE
09197 / ComputerBoards / when TMU210 is configured, protection function “automatism” is mandatory
for SPS “synthesis of instantaneous”
 AOU200 board
When a C26x is configured as redundant, AOU200 board is not allowed.
<09270>/ComputerBoards/When a computer is redunded, AOU200 board is not allowed.
 Attribute "board location" of a TMU220 board

If "Remote board" is selected for the "board location" attribute of a TMU220 board, the SCE allows
configuring 4 SPS dedicated to the activation of SVU Channels Arrangement Set:
 SPS "Arrang. 1 active"
These 4 SPS are optional in configuration and are located in the "System infos" folder of the TMU220 remote
board.
If SPS "Arrang. 2 active" is configured, SPS "Arrang. 1 active" have to be configured too.
<09397> / ComputerBoards / ‘Arrang. 2 active' datapoint can be present only if 'Channels Arrangement 1
active' is present
If the third SPS is configured, the second and the first ones have to be configured too.
<09397> / ComputerBoards / ‘Arrang 3 active' datapoint can be present only if 'Channels Arrangement 1
active' and 'Channels Arrangement 2 active' are present
If the fourth SPS is configured, the third, the second and the first ones have to be configured too.
<09397> / ComputerBoards / ‘Arrang 4 active' datapoint can be present only if 'Arrang. 1 active', 'Arrang
2 active' and 'Arrang. 3 active' are present
2.4.3.5 CONTROLLER EXTENSION RACKS
Note: These checks are only processed for non-backup controllers.
 Attribute "rack number" of an extension rack.
C264 (A) physical board number

AIU200 1
DOU200
DIU20x
CCU20x
MF-22 SCE/EN MF/C60

For the set of the extension racks of a controller, the "rack number" attribute values must be unique and
contiguous.
80279 / Extension rack / The attribute value is not unique for the extension rack
80280 / Extension rack / The rack numbers are not contiguous

In case of C264-Standalone application, only 16 hardware extension racks are allowed under a C264.
80403 / Extension rack / Invalid count of extension racks for this computer (count, max)->[17, 16]
2.4.3.6 CONTROLLER SETTINGS
Note: This check is only processed for non-backup controllers.
A controller has the following attributes:
(A) BI filtering / debouncing delay (ms)

C264 1
(A) BI filtering / filtering delay (ms)
0
(A) Measurements / debouncing delay (ms)
(A) Measurements / filtering delay (ms) 1
0
(A) Counter / debouncing delay (ms)
(A) Counter / filtering delay (ms) 1
0
For each attribute category (BI filtering / Measurements / Counter), if the attribute "debouncing delay" is set
to value 0, then the attribute "filtering delay" must be set to value 0.
10096 / ComputerSettings / The attribute values are not compatible

Examples:
10096 / ComputerSettings / The attribute values are not compatible-> [BI filtering/deboucing delay (ms), BI
filtering/filtering delay (ms)]
2.4.3.7 CONTROLLER KLAXON
A controller may have the following relation:
(R) has its klaxon controlled by

C264 SPC C264
DOU200
(R) wired on
DO # 0
The "SPC" link of the relation "has its klaxon controlled by" must be wired on a DO channel of the Controller.
10033 / ComputerSettings / The relation link is not a wired datapoint
10034 / ComputerSettings / The relation link is not a datapoint wired on the Computer
Examples:
10033 / ComputerSettings / The relation link is not a wired datapoint-> [has its klaxon controlled by: Bay SPC
SCE/EN MF/C60 MF-23

10034 / ComputerSettings / The relation link is not a datapoint wired on the Computer-> [has its klaxon
controlled by: Bay SPC
2.4.3.8 CONTROLLER PRINTERS
 Log Management attributes of a Serial Printer
C264
(A) buffer size
Serial printer 1000
(A) nb of events to suppress when saturated 300
The following constraint between the two attributes values must be respected:
"buffer size" > "nb of events to suppress when saturated"
29105 / Printers / buffer size (events) is not greater than nb of events to suppress when saturated
Examples:
29105 / Printers / buffer size (events) is not greater than nb of events to suppress when saturated-> [200,
300]
 Printing format attributes of a Serial Printer
C264
(A) Chronology column rank
Serial printer 1
(A) Time Stamp column rank
2
(A) Origin column rank
3
(A) Object Name column rank 4
(A) Object Message column rank 5
The value of each "… column rank" attribute must be unique.
29072 / Printers / The column rank is not unique

Example:
29072 / Printers / The column rank is not unique-> [Chronology column rank, Object Message column rank,
Object Name column rank, Origin column rank, Time Stamp column rank, 1]
 Adding a printer to the C26x

A serial printer cannot be added to a redundant C26x (2 masters in C26x-Standalone configuration or
back-up controller in standard configuration).
29350 / C264 / A C264 having a redundant C264 cannot contain a serial printer
2.4.3.9 OI SERVER
 In Hot Redundancy mode the OI Server must have the datapoint ‘Redundancy Status’.
77258 / OI / On OI Server in Hot Redundancy mode datapoints Red.Status must be present under OI
Server.
MF-24 SCE/EN MF/C60

 In Hot Redundancy mode, if there are more than one OI Clients, each OI Server is an HMI server for
at least one OI client.
77260 / OI / In Hot Redundancy mode if exist more than one OI Client, each OI Server is HMI server for
 In Twin Redundancy mode, each OI client must have a main OI Server as HMI server.
77261 / OI / In twin redundancy mode each OI client must have OI Server main as HMI server.
 An OI server requires at least one OI client.

77325 / OI / The OI server requires at least one OI client.
2.4.3.10 OI SERVER PRINTERS
Note: These checks are only processed for non-backup OI servers.
 Count of OI Printers for an OI server
OI server
(A) printer type Sequence Of Events
OI printer 1
(A) printer type
OI printer 2 Sequence Of Events
(A) printer type Log Book

OI printer 3
(A) printer type
OI printer 4 Log Book
For an "OI server": the maximum count of OI Printers, typed as "Sequence Of Events", is 2.
For an "OI server": the maximum count of OI Printers, typed as "Log Book", is 2.
29004 / Printers / The count of OI printer components is not valid (type, count, maximum)
Examples:
29004 / Printers / The count of OI printer components is not valid (type, count, maximum)-> [Sequence Of
Events, 4, 2]
 Log Management attributes of an OI Printer
OI server
(A) buffer length
OI printer 60
(A) recovery length 45
The following constraint between the two attributes values must be respected:
"buffer length" > "recovery length"
29105 / Printers / buffer length (s) is not greater than recovery length (s)
Examples:
29105 / Printers / buffer length (s) is not greater than recovery length (s)-> [60, 61]
SCE/EN MF/C60 MF-25

 Printing format attributes of an OI Printer
OI server
(A) Chronology column rank
OI printer 1
(A) Time Stamp column rank
2
(A) Origin column rank
3
(A) Object Name column rank
(A) Object Message column rank
4
(A) Origin Cat. column rank
5
0
(A) Origin Ident. column rank
0
The value of each "… column rank" attribute different than 0 must be unique.
The maximum number of characters by printing line is 154
29072 / Printers / The column rank is not unique

Example:
29072 / Printers / The column rank is not unique-> [Chronology column rank, Object Message column rank,
Object Name column rank, Origin column rank, Time Stamp column rank, 1]
29203 / Printers / The size in character of the printing line is too long
Example:
29203 / Printers / The size in character of the printing line is too long -> [205, 154]
2.4.3.11 OI SERVER SYMBOLS
Note: These checks are only processed for non-backup OI servers.
 Count of Send Order actions for an OI server
(R) has for HMI Client (R) has for workspace

OI Server Oi Client OI Workspace
Window
Mimic
Symbol
Send Order
An OI Server cannot manage more than 1024 Send Order in all of his mimics.
Count all Send Order of all mimics of all workspaces of all clients of the Server.
Doesn’t treat a workspace twice if set as workspace of two clients.
02003 / CapacityLimits / The count of Send Order components is not valid (count, maximum)
2.4.3.12 IEC GEN IED DATA MODEL REFERENCE
(A) model file name

IEC gen IED model.xml
The value of the attribute "model file name" is mandatory.
MF-26 SCE/EN MF/C60

34101 / DataModelReference / The attribute value is not valid-> [model file name]
2.4.3.13 CYCLIC SPS
Up to eight cyclic SPS can be managed per controller basis
59003 / CalculatorCyclicSPS / The count of cyclicSPS components is not valid (count, maximum)
2.4.3.14 CONTROLLER AM ACQUISITION

For each C26x the delta between Delta between 'long AI scanning cycle' and 'short AI scanning cycle' must
be greater or equal to 500 ms.
76263 / C264 AM Acquisition / Delta between 'long AI scanning cycle' and 'short AI scanning cycle' must
be greater or equals to 500 ms.
2.4.3.15 OI SERVER
 In Hot Redundancy mode the OI Server must have the datapoint ‘Redundancy Status’.
Red.Status must be
present in Hot Redundancy
Mode
77258 / OI / On OI Server in Hot Redundancy mode datapoints Red.Status must be present under OI
Server.
SCE/EN MF/C60 MF-27

 In Hot Redundancy mode, if exist more than one OI Clients exists, each OI Server is HMI server for at
least one OI client
Has for Backup
77260 / OI / In Hot Redundancy mode if exist more than one OI Client, each OI Server is HMI server for
2.4.4 WAVE RECORDS OF DS AGILE C26XS
Note: These checks are only processed for non-backed-up DS Agile C26xs.
2.4.4.1 COMMON CHECK FOR FAST AND SLOW RECORDS

For a Fast or a Slow Waveform, a datapoint cannot be configured more than once for the same relation
(record, trigger and analog channel lists).
36195 / WaveRecording / multiple links to the same datapoint -> [external id of the relation]
A Wave Record can only record datapoints physically wired to the same server as the controller that
manages the Wave Record. It cannot record datapoints acquired by an IED.
36234 / WaveRecording / Data point register by wave record must be managed by the same C264 as
wave record C264 and not acquire on IED -> [Path of the record relation]
C264
DREC ready
Wave fast/slow record
MF-28 SCE/EN MF/C60

36246 / WaveRecording / The datapoint 'DREC ready' must be present if a Wave recording is
configured
2.4.4.2 WAVE FAST RECORD
C264
Wave fast record (A) pre-trigger cycle 0
(A) total cycles
480 | 240 | 120 | 60
(A) number of files
1|2|4|8
The following constraints between the attributes must be respected:
 "pre-trigger cycle"  "total cycles"

 "number of files"  "total cycles"  480 cycles
36102 / WaveRecording / pre-trigger cycle is greater than total cycles
36103 / WaveRecording / number of files * total cycles is not lower than 480
Examples:
36102 /WaveRecording / pre-trigger cycle is greater than total cycles-> [2, 1]
36103 / WaveRecording / number of files * total cycles is not lower than 480-> [8, 480]
The number of Records linked to a Fast WaveForm must be lower than or equal to 128.
36361 / WaveRecording / The count of records linked to WaveForm is not valid (current, max)
The following criteria are valid configurations for a fast waveform record:
1 Presence of at least one relation ‘records: CI channel’ OR ‘records: VI channel’
2 The linked object of the relation (‘records: CI channel’ OR ‘records: VI channel’) should be only from
either TMU210 or TMU220 board
36402 / WaveRecording / At least one record of CI or VI channel (from TMU210 or TMU220) must be
present
2.4.4.3 WAVE SLOW RECORD
C264
Wave slow record (A) pre-trigger cycle 0
(A) total records
480 | 240 | 120 | 60
(A) number of files
1|2|4|8
 "pre-trigger cycle" < "total records"

 "number of files"  "total records" ≤ 5000 records
36103 / WaveRecording / pre-trigger cycle is not lower than total records
36080 / WaveRecording / number of files * total records is greater than 5000

Examples:
36103 / WaveRecording / pre-trigger cycle is not lower than total records-> [2, 1]
SCE/EN MF/C60 MF-29

36102 /WaveRecording / number of files * total records is greater than 5000-> [50, 1000]
The following checks depend on the value of the attribute "electrical frequency":
(A) Measurements / electrical frequency

C264
50 Hz 60 Hz
(A) integration time
Wave slow record [1..180000] [1..216000]
(R) records
(R) records DPC

SPC
DPS
SPS
 If "electrical frequency"  50 Hz:

 The "integration time" value must be in the range [1..180000].
 If the "integration time" value is > 5, then no DPC, SPC, DPS, SPS recording is allowed.
36104 / WaveRecording / integration time is not in the range [1..180000]
36129 / WaveRecording / The relation type is not allowed

Examples:
36104 / WaveRecording / integration time is not in the range [1..180000]-> [180001]
36129 / WaveRecording / The relation type is not allowed-> [records: Bay DPC]
 If "electrical frequency"  60 Hz:

 The "integration time" value must be in the range [1..216000].
 If the "integration time" value is > 6, then no DPC, SPC, DPS, SPS recording is allowed.
36104 / WaveRecording / integration time is not in the range [1..216000]
36129 / WaveRecording / The relation type is not allowed

Examples:
36129 / WaveRecording / The relation type is not allowed-> [records: Bay DPC]
The number of DI/DO Records linked to a Slow WaveForm must be lower than or equal to 48 whatever the
board used, TMU210 or TMU220. (SDB restriction: The number of recorded measurements is limited to 24.)
36361 / WaveRecording / The count of records linked to WaveForm is not valid (current, max)
For a slow wave form recording with TMs computed by a TMU 210 board, only the following TM “computed
by” measurement types are allowed:
 VAN, RMS voltage value for phase A
 VBN, RMS voltage value for phase B
 VCN, RMS voltage value for phase C
 Vr , RMS value for residual voltage
 VAB, voltage value for phases AB (RMS if delta)
 VBC, voltage value for phases BC (RMS if delta)
MF-30 SCE/EN MF/C60

 VCA, voltage value for phases CA (RMS if delta)

 IA, RMS current value for phase A
 IB, RMS current value for phase B
 IC, RMS current value for phase C
 Pt, total active power
 Qt, total reactive power
 St, total apparent power
 cos φt : total power factor
 frequency difference (Standard Synchrocheck)
 voltage difference (Standard Synchrocheck)
 phase difference (Standard Synchrocheck)
 Zero Sequence Voltage (Vo)
 Vbusbar RMS 1 value for busbar voltage
 line frequency
 busbar frequency
57375 / UCA2Computer / The type of measurement is not valid with TMU 210 and slow wave
formTriggers of Wave Record
Any trigger datapoint of a given Wave record must have the same server as the DS Agile C26x managing
this wave record.
36223 / WaveRecording / The trigger datapoint has not the same server as its associated wave record
(servers)
2.4.5 CHANNELS
Example of relations connecting Legacy Network / SCADA Network / Serial Printer / Datapoint to a Channel:
C264 C264
BIU200
DNP3 master (Legacy Network) (R) has for main comm. port
RS232/485 port 1 (Comm. Channel)
(R) has for aux. comm. port RS232/485 port 2 (Comm. Channel)
(R) has for main comm. port

C26X SCADA prot (SCADA Network)
(R) has for aux. comm. port
(R) has for comm. port

Serial printer
SCE/EN MF/C60 MF-31

IEC gateway IEC gateway

(R) has for main comm. port Gateway channels
Usual protocol (SCADA Network) Gateway chan. 1 ( Gateway Channel )
(R) has for aux. comm. port Gateway chan. 2 ( Gateway Channel )
Gateway chan. 3 ( Gateway Channel )
(R) has for main comm. Gateway chan. 4 ( Gateway Channel )
GI74 protocol (SCADA Network) Gateway chan. 5 ( Gateway Channel )
(R) has for aux. comm. port1
Gateway chan. 6 ( Gateway Channel )
(R) has for main comm. port2 Gateway chan. 7 ( Gateway Channel )
(R) has for aux. comm. port2 Gateway chan. 8 ( Gateway Channel )
(R) has for main comm. port3
(R) has for main comm. port4
C264
(R) 'bit 00' wired on DIU200
MV DI#0 (Channel)
(R) 'bit 01' wired on
DI#1 (Channel)
A Channel must be used only once.
11017 / RelationHasForCommPort / Multiple links to the same communication port
12018 / RelationHasForChannel / Multiple links to the same channel

Examples:
11017 / RelationHasForCommPort / Multiple links to the same communication port-> [is main comm. port of:
C26X SCADA prot]
12018 / RelationHasForChannel / Multiple links to the same channel-> ['bit 00' channel for: Bay MV]
The T101-SAS Protocol cannot have an auxiliary communication port.
11252 / RelationHasForCommPort / Auxiliary communication port is not allowed for this protocol (comm.
port)
Attribute "plug com. number" of Gateway channels:
IEC gateway IEC gateway

(R) has for main comm. port Gateway channels (A) plug com. number
Usual protocol Gateway chan. 1 1
(R) has for aux. comm. port Gateway chan. 2
Gateway chan. 3
Gateway chan. 4
Gateway chan. 5
Gateway chan. 6
Gateway chan. 7
Gateway chan. 8
Under a Gateway, each channel used by a non-GI74 protocol, must have a unique value for its "plug com.
number" attribute.
31019 / GatewayCommPorts / The attribute value is not unique for the gateway
Example:
31019 / GatewayCommPorts / The attribute value is not unique for the gateway-> [plug com. number, 1]
MF-32 SCE/EN MF/C60

Attribute "baud rate" of Gateway channel:

Under a Gateway, channel baud rates 100, 200, 38400 are available only for T101 protocol.
31104 / GatewayCommPorts / Baud rate is not in the range [300..19200]

Channel baud rates 100, 200 are also available for SAS protocol.
31104 / GatewayCommPorts / SAS baud rate is not in the range [100..19200]
2.4.6 GATEWAY SERVER

Check for a gateway used as Bay manager:
The object Redundant T101 Master is not compatible with a redundant Gateway used as a Bay manager.
86317 / GtwServer / Not compatible component on a GTW (used as Bay manager) redounded
A datapoint managed by a gateway cannot be linked to a graphical part, except for the datapoints that have
a DIAG address or if they are set to either “OperatingMode” or “CommDevice”.
86371 / GtwServer / A datapoint managed by gateway could not be linked to graphical object
A datapoint managed by gateway that has a DIAG address or is set to either “OperatingMode” or
“CommDevice” cannot have an Alarmed, Logged or Archived profile.
86372 / GtwServer / A datapoint managed by gateway could not have alarmed, logged or archived state
2.4.7 LEGACY NETWORKS
Note: These checks are not processed for Legacy Networks of backup devices.
The general interrogation period of a T103 acquisition type should be equal to 0 or greater than 600 s
17276 / LegacyIED / The general interrogation period should be equal to 0 or greater than 600 s
The port used by a T103 legacy network must have an even parity.
17277 / LegacyIED / Even parity is required for T103 usage on the port
2.4.7.1 IEDS ON LEGACY NETWORKS
C264
Legacy networks
DNP3 master (A) network address
DNP3_IED 0
DNP3_IED (A) network address
0
Modbus Mod.
(A) network address
MODB_IED 0
T103 (A) network address

T103_IED 0
T101 master
(A) network address
T101_IED 0
For each IED, per Legacy Network:
SCE/EN MF/C60 MF-33

 its "network address" attribute value must be unique

 its "short name" attribute value must be unique
17035 / LegacyIED / The address of the IED is not unique on the Legacy Network
17036 / LegacyIED / The name of the IED is not unique on the Legacy Network
Examples:
17035 / LegacyIED / The address of the IED is not unique on the Legacy Network-> [network address, 0]
17036 / LegacyIED / The name of the IED is not unique on the Legacy Network-> [short name, DNP3_IED]
C264
Legacy networks
DNP3 master
DNP3_IED
DNP3 acq type
Modbus Mod.
MODB_IED
MODBUS acq type
T103
T103_IED
T103 acq type
T101 master
T101_IED
For each Device, and for all its Legacy Networks, the maximum count of "xxx acq type" components is 10.
02003 / CapacityLimits / The count of IED acquisition type components is not valid (count, maximum)
Examples:
02003 / CapacityLimits / The count of IED acquisition type components is not valid (count, maximum)-> [11,
10]
If an IED has an automatic disturbance set to YES, then the datapoint “IED DREC ready” must be present.
17344 / LegacyIED / The datapoint 'IED DREC ready' must be present if IED has automatic disturbance
Only for Gateway:
For a gateway, the maximum count of legacy protocol is 4.
02003 / CapacityLimits / The count of legacy protocol on the gateway is not valid (count, maximum)
2.4.7.1.1 IED on Legacy T101 Network
Only for C26x:
17349 / LegacyIED / The T101 Master with a main and an auxiliary communication port must use one
and only one T101 IED
Only for Gateway:
The attribute 'Common ASDU address' is used by the IED and the IED mapping address if their field has
default value -1. At level of IED this field cannot have the default value and must be configured.
17367 / LegacyIED / The attribute 'Common ASDU address' for the gateway T101IED must be different
from -1
2.4.7.1.2 IED on Legacy T103 Network
MF-34 SCE/EN MF/C60

For each T103 IED, if the MPS datapoint POC exists, the MPS PSE must also exist.
17167 / LegacyIED / The MPS datapoint PSE is missing

For each T103 IED, if MPS datapoints POC or PSE exists, and one of them is SBMC-dependent, the relation
“is relay of” must exists on the IED.
17186 / LegacyIED / The IED must have the relation Is Relay Of, because PSE and/or POC is SBMC
dependent
2.4.7.1.3 IED on Legacy MODBUS Network
Under a Legacy MODBUS a maximum of 15 ABB IEDs can be used. ABB flexgate manage a maximum of
15 IEDs.
02003 / CapacityLimits / The count of ABB IED components is not valid (count, maximum)-> [16, 15]
For any IED under a Modbus network, the associated IED acquisition type imposes its synchronisation
defined at network level.
17273 / LegacyIED / The IED requires a ALSTOM synchronisation (IED network, IED)
17274 / LegacyIED / The IED requires a SEPAM synchronisation (IED network, IED)
17275 / LegacyIED / The IED requires a FLEXGATE synchronisation (IED network, IED)
2.4.7.2 IED MAPPING

2.4.7.2.1 Case of DNP3 IED
In the IED Mapping, the address identification of each "xxx addr. on IED" must be unique.
The address identification is the value of the attribute "address" of the "xxx addr. on IED".
DNP3_IED
IED Mapping
IED DPC Mapping

DPC addr. on IED (A) address 0
IED DPS Mapping

(A) address
DPS addr. on IED 0
IED SPC Mapping

SPC addr. on IED (A) address 1
IED SPS Mapping

SPS addr. on IED (A) address 2
IED MPS Mapping

MPS addr. on IED (A) address 3
IED Counter Mapping (A) address

Counter addr. on IED 4
IED MV Mapping
MV addr. on IED (A) address 5
IED SetPt Mapping

SetPt addr. on IED (A) address 6
18037 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the Mapping
SCE/EN MF/C60 MF-35

Examples:
18037 /xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the Mapping-> [address,
0]
2.4.7.2.2 Case of Modbus IED
For each "xxx addr. on IED", the address identification is made of either of the following combinations of its
attribute values:
 { "mapping address" , "function" , "bit number" }
 { "mapping address" , "function" }
MODB_IED
IED Mapping
IED DPC Mapping (A) mapping address , (A) function , A: bit number
DPC addr. on IED 0,0,0
IED DPS Mapping (A) mapping address , (A) function , A: bit number
DPS addr. on IED 0,0,0
IED SPC Mapping

(A) mapping address , (A) function , A: bit number 0,0,1
SPC addr. on IED
IED SPS Mapping

SPS addr. on IED
IED MPS Mapping (A) mapping address , (A) function , A: bit number
MPS addr. on IED 0,1,1
IED Counter Mapping (A) mapping address , (A) function

Counter addr. on IED 0,0
IED MV Mapping (A) mapping address , (A) function

MV addr. on IED 0,0
IED SetPt Mapping (A) mapping address , (A) function

SetPt addr. on IED 0,1
Examples:
18037 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the Mapping->
[mapping address/function/bit number, 0/0/0]
[mapping address/function, 0/0]
 In the IED Mapping, the address ‘bit number’ attribute must be lower than 16 ( 0..15) for
SPS/DPS/MPS/SPC/DPC MODBUS IED Address.
18232 / xxxAddressOnIED / The address of the 'Bit number’ on IED MODBUS address must be lower
than 16
2.4.7.2.2.1 Case of ABB Flexgate Modbus IED
 In all of the IEDs Mappings of type ABB Flexgate, the address identification of each "xxx addr. on
IED" must be unique at Legacy MODBUS level.
attribute values :
{ "mapping address" , "function" , "bit number" }
MF-36 SCE/EN MF/C60

{ "mapping address" , "function" }
MODB_IED_1_ABB
IED Mapping
IED SPC Mapping

SPC addr. on IED
IED SPS Mapping

SPS addr. on IED


MV addr. on IED 0,0
IED SetPt Mapping

(A) mapping address , (A) function
MODB_IED_2_ABB
IED Mapping
IED SPC Mapping (A) mapping address , (A) function , A: bit number
SPC addr. on IED 1,0,1
IED SPS Mapping (A) mapping address , (A) function , A: bit number
SPS addr. on IED 1,0,1


MV addr. on IED 1,0
IED SetPt Mapping (A) mapping address , (A) function

18262 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the legacy
MODBUS for all ABB IED-> [mapping address/fonction/bit number, 57/1/1, Scs | Ethernet network | C264 |
Modbus Mod. (LB)]
Under a Legacy MODBUS a maximum of 15 ABB IED can be use. ABB flexgate manage 15 IED maximum.
SCE/EN MF/C60 MF-37

02003 / CapacityLimits / The count of ABB IED components is not valid (count, maximum)-> [16, 15]
2.4.7.2.3 Case of T103 IED
For each "xxx addr. on IED", the address identification is made of one of the following combinations of its
attribute values:
 { "ASDU number" , "function type" , "information number" , "common address of ASDU" , "index in
the ASDU" }
 { "ASDU number" , "function type" , "information number" , "common address of ASDU" }
 { "ASDU number" , "function type" , "information number" }
T103_IED
IED Mapping
IED DPC Mapping (A) ASDU number , (A) function type, (A) information number
(A) ASDU number , (A) function type, (A) information number,
IED DPS Mapping (A) common address of ASDU
DPS addr. on IED 0,0,0,0
IED SPC Mapping

(A) ASDU number , (A) function type, (A) information number
SPC addr. on IED 0,0,0
IED SPS Mapping
(A) common address of ASDU
SPS addr. on IED
0,0,0,1
IED MPS Mapping (A) ASDU number , (A) function type, (A) information number
IED Counter Mapping

Counter addr. on IED
IED MV Mapping (A) common address of ASDU, (A) index in the ASDU
MV addr. on IED
0,1,1,0,0
IED SetPt Mapping (A) ASDU number , (A) function type, (A) information number
SetPt addr. on IED 0,1,1
Examples:
18037 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the Mapping-> [ASDU
number/function type/information number, 0/0/0]
number/function type/information number/common address of ASDU, 0/0/0/1]
number/function type/information number/common address of ASDU/index in the ASDU, 0/1/1/0/0]
2.4.7.2.4 Case of T101 and T104 IED
attribute values:
 { "information object address" , "common address of ASDU" }
 { "information object address" }
MF-38 SCE/EN MF/C60

T101_IED
IED Mapping
IED DPC Mapping (A) information object address, (A) common address of ASDU
DPC addr. on IED 0,0
IED DPS Mapping

(A) information object address
DPS addr. on IED 0
IED SPC Mapping

(A) information object address, (A) common address of ASDU
SPC addr. on IED 0,1
IED SPS Mapping (A) information object address 0
SPS addr. on IED
IED MPS Mapping (A) information object address

MPS addr. on IED
IED Counter Mapping (A) information object address, (A) common address of ASDU
Counter addr. on IED
IED MV Mapping (A) information object address

MV addr. on IED
IED SetPt Mapping (A) information object address

SetPt addr. on IED
Examples:
[information object address, 0]
[information object address/common address of ASDU, 0/0]
Only for Gateway:
In the IED Mapping, the IED MPS Mapping Address "xxx addr. on IED" is forbidden to be mapped to any
datapoint.
18405 / xxxAddressOnIED / The gateway T101M or T104M IED doesn't manage the MPS datapoints->
[IED MPS Mapping]
2.4.7.2.5 Case of MiCOM Px2x IED
18348 / xxxAddressOnIED / A Modbus IED with MICOM Px2x acquisition type must have a network
address between the min value authorized and the max value authorized [0, 247]
2.4.8 SCADA NETWORKS
Note: These checks are not processed for SCADA Networks of backup devices.
2.4.8.1 SCADA MAPPING

SCADA Mappings are defined for SCADA networks of Controller and Gateway physical devices.
Note: the following checks, except the check of feedback addresses, do not process GI74 protocol.
SCE/EN MF/C60 MF-39

2.4.8.1.1 Address value, in SCADA Mapping of C26x units and Gateways
C264 - T101
SCADA networks - DNP3
(A) protocol
C26X SCADA prot - T104
-MODBUS
Gtw SCADA Map. (A) SOE file address
255
Gtw Counter Map (A) object address
Gtw Counter addr 255
Gtw DPC Map
(A) object address
Gtw DPC addr. 255
Gtw DPS Map
(A) object address
Gtw DPS addr. 254
Gtw SPC Map
Gtw DPC addr. (A) object address 253
Gtw SPS Map
Gtw DPS addr. (A) object address 252
Gtw MV Map
Gtw MV addr. (A) object address
251
Gtw SetPt Map
Gtw SetPoint addr. (A) object address 250
UCA2/IEC gateway - T101 - CDC II

SCADA networks - DNP3 - SAS
(A) protocol - T104
Usual protocol
- MODBUS
Gtw SCADA Map. (A) SOE file base address
255
Gtw Counter Map (A) object address
Gtw Counter addr 255
Gtw DPC Map
(A) object address
Gtw DPC addr. 255
Gtw DPS Map
(A) object address
Gtw DPS addr. 254
Gtw SPC Map
Gtw DPC addr. (A) object address
253
Gtw SPS Map
Gtw DPS addr. (A) object address
252
Gtw MV Map
Gtw MV addr. (A) object address
251
Gtw SetPt Map
Gtw SetPoint addr. (A) object address
250
An address identification is the value of the attribute "object address" of a "Gtw xxx addr.", plus the value of
the attribute "SOE file address" defined on the protocol.
In a SCADA Mapping, the address identification of each "Gtw xxx addr." must be unique.
Particular case of a "Gtw DPS addr." in DNP3 protocol of DS Agile C26x:
Two addresses are used. Their values are given by:
 the attribute "object address" value

 the attribute "object address" value + 1 (reserved address).
MF-40 SCE/EN MF/C60

Particular case of "Gtw DPS addr." in MODBUS protocol of DS Agile C26x:

If ‘Double address usage’ value is ‘Yes’
Two addresses are used :
 open state address

 closed state address
This couple of address must be unique in SCADA mapping
19038 / xxxAddressOnSCADANetwork / The address of the 'Gtw xxx address' is not unique in the
Mapping
If ‘Double address usage’ value is ‘Yes’ attribute ‘open state address’ and ‘closed state address’ must be
different on each ‘Gtw DPS addr’
19247 / xxxAddressOnSCADANetwork / Attribute 'open state address' and 'Closed state address' must
be different for double addressing configuration
For CDCII SCADA addresses, the address structure depends on datapoint kind:
 for SPS and DPS in static mode: CHN.SQN.OFF (concatenation of 3 attributes)

 for SPS and DPS in event mode: CHN.PPU.EVT (concatenation of 3 attributes)
 for MV and counter: CHN.SQN (concatenation of 2 attributes)
 for SPC, DPC and SetPoint: CHN.SQN (concatenation of 2 attributes)
Mapping
Examples:
19038 / xxxAddressOnSCADANetwork / The address of the 'Gtw xxx address' is not unique in the Mapping->
[object address, 255]
19038 / xxxAddressOnSCADANetwork / The address of the 'Gtw xxx address' is not unique in the Mapping->
[SOE file address, 255]
Particular cases of T101, T104 and DNP3 protocols (for DS Agile C26x and Gateways):
 The unicity constraint is applicable only for addresses of the same type. Addresses of different
types can have identical addresses and therefore this does not lead to an error but to a warning.
 Address for Disturbance uploading and Buffer Overflow (only for T101 and T104) to SCADA are
also taken into account in the unicity check.
 The type for T101 and T104 is same as defined in SCE (SPS, DPS, SPC…) and for DNP3, is
grouping simple and double (TS, TC, TM, Counter and SetPoint)
Mapping
For SCADA addresses of MPS POC or PSE, the address must be bitstring.
18169 / LegacyIED / The SCADA address format for PSE/POC must be bitstring
For CDCII SCADA addressing, SQN value attribute must respect following constraints:
 for SPS and DPS: 0<= SQN <=63
 for MV: 130<= SQN <=255
 for Counter: 64<= SQN <=95
SCE/EN MF/C60 MF-41

 for SPC and DPC: 0<= SQN <=63

 for SetPoint: 0<= SQN <=15
19189 / xxxAddressOnSCADANetwork /Bad value for SQN attribute of CDCII address (value, min max)
For T101-SAS protocol, the TC addresses are not allowed
19253 / xxxAddressOnSCADANetwork / For T101- SAS protocol, the Command addresses are not
allowed
2.4.8.1.2 Address structure, in SCADA Mapping of Controllers and Gateways
C264 - T101
(A) protocol - DNP3 depending of
C26x SCADA prot
- T104
Gtw SCADA Map.
- Address on 8 bits (1 byte)
Gtw xxx Map - Address on 16 bits (2 bytes)
Gtw xxx addr. - Address on 24 bits (3 bytes)
(A) object address
255.255.255
An "object address" value is formatted according to the "address structure" value selected in the protocol
definition.
The set of possible "address structure" values depends on the protocol type.
Exception: for the DNP3 protocol type, the "address structure" is a fixed format: 16 bits in the range
[1..65535].
The "object address" value of a "Gtw xxx addr." must be compatible with the value selected for the "address
structure".
19039 / xxxAddressOnSCADANetwork / The address is incompatible with the address structure of the
protocol
Examples:
protocol (Address on 8 bits.8 bits.8 bits)-> [object address, 255]
2.4.8.1.3 BufferOverflowAddress structure in SCADA T101 / T104 of Computers & Gateways
MF-42 SCE/EN MF/C60

C264 - T101
(A) protocol - T104 depending of
C26x SCADA prot
GTW
Usual protocol - Address on 8 bits (1 byte)
(A) buffer overflow address - Address on 8 bits.16 bits
255.255.255
The "Buffer overflow address" value is formatted according to the "address structure" value selected in the
protocol definition.
The set of possible "address structure" values depends on the protocol type.
The "buffer overflow address" value must be compatible with the value selected for the "address structure".
protocol
Examples:
protocol (Address on 8 bits.8 bits.8 bits)-> [object address, 255]
2.4.8.1.4 MV Address format on DNP3 protocol, of Controllers and Gateways
On a DNP3 protocol, a "Gtw MV addr.", which is the SCADA address of a "Tap pos ind" datapoint, must
have its "Format" attribute set to the "Natural" value.
C264
(A) protocol DNP3
C26x SCADA prot
Gtw SCADA Map.
Gtw MV Map
Gtw MV addr. (A) Format
Natural
Transformer (Bay)
(R) has for SCADA address transformer
Tap Changer
Tap pos ind (MV)
19123 / xxxAddressOnSCADANetwork / The attribute value is not compatible with the relation
Examples:
19123 / xxxAddressOnSCADANetwork / The attribute value is not compatible with the relation-> [Format =
Adjusted, is SCADA address of: Tap pos ind]
2.4.8.1.5 SOE file attributes, in SCADA Mapping of Controllers
These attributes are defined for a Controller SCADA protocol.
SCE/EN MF/C60 MF-43

C264 (A) SOE file nb of events

C26x SCADA prot 100
(A) 'full' SOE file nb of events 75

"SOE file nb of events" > "'full' SOE file nb of events"
20103 / SCADA_Networks / 'full' SOE file nb of events is not lower than SOE file nb of events
Examples:
20103 / SCADA_Networks / 'full' SOE file nb of events is not lower than SOE file nb of events-> [175, 100]
2.4.8.1.6 T104 protocol attributes, of Controllers and Gateways
(A) protocol T104
C264 (A) T1: APDU time-out

C26x SCADA prot (A) T2: acknowledgement time-out 15
10
(A) T3: test frame time-out
20
(A) K: sent unack. frames (APDU) 12
(A) W: ack. recieved frames (APDU) 8

"T2" < "T1"
"T3" > "T1"
"W"  "K"
20103 / SCADA_Networks / T2: acknowledgement time-out (s) is not lower than T1: APDU time-out (s)
20103 / SCADA_Networks / T1: APDU time-out (s) is not lower than T3: test frame time-out (s)
20102 / SCADA_Networks / W: ack. received frames (APDU) is greater than K: sent unack. frames
(APDU)
Examples:
20103 / SCADA_Networks / T2: acknowledgement time-out (s) is not lower than T1: APDU time-out (s)->
[20, 15]
20103 / SCADA_Networks / T1: APDU time-out (s) is not lower than T3: test frame time-out (s)-> [15, 14]
20102 / SCADA_Networks / W: ack. received frames (APDU) is greater than K: sent unack. frames (APDU)-
> [12, 11]
For C26x-Standalone only, when the C26x is redundant (numbers of masters = 2), then the value of
following attributes cannot be other than ‘0.0.0.0’.
 socket IP #2,
 socket IP #3 and
 socket IP #4.
20101 / SCADA_Networks / The attribute value is not valid  [Attribute, Invalid value, Valid value]
Example:
20101 / SCADA_Networks / The attribute value is not valid  [socket IP #2, 197.196.195.194, 0.0.0.0]
MF-44 SCE/EN MF/C60

2.4.8.1.7 Feedback addresses on GI74 protocol, of Gateways

A "GI74 DPC addr." (or a "GI74 SPC addr.") must have 1, and only 1, link to a "GI74 DPS addr." or "GI74
SPS addr." feedback address.
IEC gateway
GI74 protocol
GI74 SCADA Map.
GI74 DPC Map

(R) has for feedback
GI74 DPC addr. 1
GI74 DPC addr. 2
GI74 DPS Map
GI74 DPS addr. 1
GI74 DPS addr. 2
GI74 SPS Map

GI74 SPS addr. 1
GI74 SPS addr. 2
GI74 SPC Map (R) has for feedback

GI74 SPC addr. 1
GI74 SPC addr. 2
14022 / RelationHasForFeedback / The link to feedback is missing
14023 / RelationHasForFeedback / Multiple links to feedbacks

Example:
14023 / RelationHasForFeedback / Multiple links to feedbacks-> [has for feedback: GI74 DPS addr., has for
feedback: GI74 SPS addr.]
2.4.8.1.8 Addressing of MPS on T101/T104 of DS Agile C26x
MPS addressing in refused on T101/T104 SCADA network of DS Agile C26x.
19255 / xxxAddressOnSCADANetwork / MPS addressing refused on C264 T101/104 SCADA network
2.4.8.2 NUMBER OF SCADA NETWORKS

On a DS Agile C26x, up to four SCADA networks can be created. When more than two exists, DS Agile
C26x must be based on CPU3 hardware.
The two CPU270 Ethernet ports can be configured as follows:
N° Port 1 Port 2 Comments
IEC 61850-8-1 SBUS + 2 independent SCADA protocols with different
1 SCADA IP 2
SCADA IP 1 database
2 independent SCADA protocols with different
2 SCADA IP 1 SCADA IP 2
database
3 IEC 61850-8-1 SBUS SCADA IP
IEC 61850-8-1 Station Bus, if configured, is always on port 1.

One or two IP SCADA protocols can be configured on port 1 and/or 2.
The existing IS SCADA protocols are DNP3 and T104. DNP3 is mono-client. T104 is multi-clients (up to 4
clients) with only one active at one time. One protocol is binded on one (and only one) Ethernet port.
SCE/EN MF/C60 MF-45

02206 /Capacity limits/ The maximum number of SCADA and legacy protocols on the main rack for a
computer has been reached (max number, count of protocols)
02206 /Capacity limits / This error replace the previous error 20206 / SCADA_Networks /
20383 / SCADA_Networks / At least one SCADA protocol has to be defined

Example:
20383 / SCADA_Networks / At least one SCADA protocol has to be defined-> [Scs | Ethernet network |
GTW1]
2.4.8.3 PROTOCOL TYPE COHERENCY WITH HARDWARE PORT TYPE

Coherency must exist between the protocol type and the hardware port type according the following table:
Prot type (Hardware port) Protocol type (SCADA networks) Coherency
Usual protocol T101, T104, DNP3, MODBUS, CDCType II OK
GI74 protocol GI74 OK
V35 ACKSYS-MCX T101 OK
20209 / SCADA_Networks / The coherency between this protocol type (protocol type) and this gateway
port (gateway port) is failed.
2.4.8.4 REDUNDANCY TYPE OF T101

On a controller, no active line on traffic can be used if unbalanced mode (Applicable T101).
20335 / SCADA_Networks / no active line on traffic can be used if unbalanced mode
2.4.8.5 COMPUTER REDUNDANCY WITH T104 SCADA PROTOCOL

On a redundant computer, a T104 SCADA protocol is incompatible.
20399 / SCADA_Networks / T104 SCADA protocol and C264 redundancy are not compatible
2.4.8.6 COMMUNICATION PORT OF A SCADA NETWORK

A SCADA network cannot use a communication port of an extension rack.
20303 / SCADA_Networks / Scada Network cannot use a communication port of an extension rack
MF-46 SCE/EN MF/C60

C264
Extension rack
BIU241
Port 1
Port 2
Has For aux. comm. port
SCADA Network
Has For Main comm. port
2.4.9 COMMAND ARBITRATION FOR SCADA NETWORKS

The command arbitration feature is available on up to 3 protocols on the same C26x and only if the various
SCADAs are communicating with the same physical C26x rack.
The valid application cases are:
 2 x protocols T101 + 1 x protocol T104 implemented in the C26x

 1 x protocol T101 + 1 x protocol T104 implemented in the C26x
 2 x protocols T101 implemented in the C26x
For all other application cases the feature is not available.
20362 / SCADA_Networks / The count of SCADA T101 and T104 protocols is not correct to activate the
command arbitration on the C264 (nb T101, nb T104)
The SPS datapoint “Request in progress” is optional, and only available with T101 or T104 protocol
20363 / SCADA_Networks / The SPS datapoint 'SCADA Request in progress' must only be present on a
SCADA T101 or T104 and if the command arbitration is activated on the C264
If the command arbitration feature is active on a C26x, the SPS datapoint “Request in progress” must be
present at least with a T101 or T104 protocol
20364 / SCADA_Networks / At least 1 SPS datapoint 'SCADA Request in progress' must be present on a
SCADA T101 or T104 if the command arbitration is activated on the C264
2.4.9.1 FORBIDDEN DATAPOINTS UNDER C264 SCADA NETWORKS
 Only if a SCADA T101 is configured under a C264, datapoints "Main Link Fail" and "Aux Link Fail" are
allowed, otherwise both are forbidden
20398/ SCADA_Networks / The datapoint is not allowed for this protocol-> [datapoint, protocol]
SCE/EN MF/C60 MF-47

Examples:
20398/ SCADA_Networks / The datapoint is not allowed for this protocol -> [Main Link Fail, T104]
20398/ SCADA_Networks / The datapoint is not allowed for this protocol -> [Aux. Link Fail, DNP3]
2.4.9.2 PROTOCOL IP ADDRESSING
Ethernet Network
IEC61850 gateway
SCADA Networks TCP/IP address
61850 protocol 255.255.255.255
An IEC 61850-8-1 Protocol connected to an IEC 61850-8-1 gateway has an attribute "TCP/IP address".
 The "TCP/IP address" value of an IEC 61850-8-1 protocol must be different from its default value
(255.255.255.255).
07101 / TCPIPattribute / The attribute value is not valid-> [TCP/IP address, 255.255.255.255]
2.4.10 TAKING CONTROL FUNCTION
Substation Ethernet network

Taking Control C264
(R) is taken control of
Taking Status C26X SCADA prot

Taking Control UCA2/IEC gateway
Taking Status Usual protocol

Taking Control UCA2/IEC gateway
Taking Status GI74 protocol
(R) is taken control of GI74 port 2
 If, at least, one SCADA network is linked to a Taking Control function, all the SCADA Networks of the
system, except IEC 61850-8-1 and SAS Usual Protocol, must be linked to a Taking Control function.
52131 / TakingControl / The relation link is missing-> [has for taken control]
MF-48 SCE/EN MF/C60

 If a "Taking Status" datapoint is linked to a SCADA Network, it must also be linked to a "Taking
Control" datapoint through the relation "has for feedback".
52131 / TakingControl / The relation link is missing-> [is feedback of]
 A "Taking Control" datapoint must be linked to a "Taking Status" datapoint through the relation "has for
feedback".
 The "Taking Control" datapoint must have its "activation mode" attribute set to a "Permanent…" value.
The "Taking Status" datapoint must have its "detection mode" attribute set to the "Permanent" value.
Substation
(A) activation mode - Permanent
Taking Control - Permanent until feedback
Taking Status (A) detection mode
- Permanent
52101 / TakingControl / The attribute value is not valid

Examples:
52101 / TakingControl / The attribute value is not valid-> [activation mode, Transient]
52101 / TakingControl / The attribute value is not valid-> [detection mode, Transient]
 Both "Taking Control" and "Taking Status" datapoints must be linked to a SCADA address in the
mapping of their SCADA network.
Substation
Ethernet network
Taking Control C264
Taking Status
C26X SCADA prot
GtwSCADAMap
(R) has for SCADA address
Gtw SPC Mapping
Gtw SPC addr.
Gtw SPS Mapping
Gtw SPS addr.
52133 / TakingControl / The datapoint is not linked to a SCADA address

Example:
52133 / TakingControl / The datapoint is not linked to a SCADA address of Scs | Ethernet network | C264 |
C26X SCADA prot
SCE/EN MF/C60 MF-49

 If the Taking Control function is defined in the system, the substation "Loc/rem ctrl DPC" datapoint
must be present and not wired.
Substation DO channel
(R) 'open' wired on
Loc/rem ctrl DPC
(R) 'closed' wired on DO channel
Taking Control
Taking Status
52089 / TakingControl / The datapoint is missing-> [Loc/rem ctrl DPC]
52100 / TakingControl / The datapoint is wired
2.4.11 NON DS AGILE IED ON IEC 61850-8-1
2.4.11.1 VIRTUAL INPUT OF IEC 61850-8-1 IED

Any virtual input and its associated used datapoint cannot have the same server, that is to say the
IEC 61850-8-1 containing the virtual input.
82283 / IED virtual input / The virtual input and the associated used datapoint cannot have the same
server
2.4.11.2 REPORT BY CLIENT LIMIT

For each non DS Agile IED, check if there’s enough report for all clients needs.
83284 / Indiced reports Not enough reports for all clients (Server path, Client path, List of DataObject
missing)
2.4.11.3 DATASET CREATION LIMIT

For each non DS Agile IED, check if all needed datasets may be created (regarding capability of the IED).
83285 / Indiced reports / Number of DataSet to create for this IED is greater than the maximum number
allowed (Server path, max number of DataSet allowed, dataSet number to create)
2.4.11.4 USE OF REPORTS INSTANCES

If there are several instances of a report, the first ones should be given priority.
This warning should prevent an inconsistency between the configuration and the SCL exported element
“ClientLN”, present under “RptEnabled” element.
83408 / IED Indiced reports / This report instance should be used in priority (to be consistent with SCL
exported element ClientLN)-> [IED_1System/LLN0$RP$urcbB01]
MF-50 SCE/EN MF/C60

2.5 ELECTRICAL CHECKS
2.5.1 SUBSTATION
 The default server of the Substation should be located in that Substation only
88011 / Substation / The relation link is not compatible with the filter -> [‘Site | Substation’ has a default
IEC61850 server: ‘Scs | Ethernet network | System Bay | C264’]
2.5.2 VOLTAGE LEVEL
 The default server of the Voltage level should be located in its parent Substation only
89011 / Voltage Level/ The relation link is not compatible with the filter -> [‘Site | Substation | Voltage
level’ has a default IEC61850 server: ‘Scs | Ethernet network | System Bay | C264’]
2.5.3 BAY
A Bay managed by a Gateway must be a Generic Bay.
85365 / Bay / A bay managed by a gateway must be a generic bay (bay, bay type)
Example:
85365 / Bay / A bay managed by a gateway must be a generic bay (bay, bay type)-> [Site | Substation |
Voltage level | Bay, Feeder]
The possible contents of a Generic Bay managed by a Gateway are limited to the components below:
 the specific datapoints ‘order running’, L/R, SBMC

 the generic bay datapoints
 the generic modules,
 the generic module datapoints,
 the RT User Function,
 the datapoints of RT User Function.
85366 / Bay / The contents of the bay managed by a gateway isn't valid (bay, component not authorized)
Example:
85366 / Bay / The contents of the bay managed by a gateway isn't valid (bay, component not authorized)->
[Site | Substation | Voltage level | GenBayByGtw, Site | Substation | Voltage level | GenBayByGtw | Day
cyclic SPS]
 A datapoint under a bay managed by a gateway must have a relation to ISaGRAF or a legacy IED
address, except for MPS datapoints that must have a relation to ISaGRAF but not to any legacy IED.
85368 / Bay / Site | Substation | Voltage level | bay_GTW | A datapoint under a bay managed by a
gateway must have a relation to Isagraf or a legacy IED address
 A datapoint managed by gateway could not be linked to graphical object

85371 / Bay / Site | Substation | Voltage level | bay_GTW | A datapoint managed by gateway could not
be linked to graphical object
SCE/EN MF/C60 MF-51

 A datapoint managed by a gateway cannot have alarmed, logged or archived states

85372 / Bay / Site | Substation | Voltage level | bay_GTW | A datapoint managed by gateway could not
have alarmed, logged or archived state
 A bay managed by a gateway cannot be linked to a graphical object

85373 / Bay / Site | Substation | Voltage level | bay_GTW | A bay managed by gateway could not be
linked to graphical object
 The Bay Manager should be located in same Substation in which the bay is located
85011 / Bay / The relation link is not compatible with the filter -> [‘Site | Substation | Voltage level |
Generic bay’ is managed by: ‘Scs | Ethernet network | System Bay | C264’]
2.5.4 BAY MIMIC
Graphic
(R) has for workspace C264 (1) (A) HMI type - Simple
Comp. workspace GHU200 - Complete
(R) represents - Old
Bay mimic (1) (R) is managed by
Feeder (1) C264 (2)
(R) represents
Bay mimic (2)
(R) is managed by
Feeder (2)
(A) graphical reference

[1..8], 65535
(A) graphical reference
[1..8], 65535
(A) mimic rank for the set of bay mimic

1
(A) mimic rank for the set of bay mimic 2
 The controller ("C26x (2)" ) managing a bay ( "Feeder (1)" ) represented by a "Bay mimic" must be the
same as the one linked to the "Comp. workspace" ( "C26x (1)" ) of this "Bay mimic".
33076 / BayMimic / The BayMimic and its Workspace are not linked to the same computer
Example:
33076 / BayMimic / The BayMimic and its Workspace are not linked to the same computer-> [Scs | Ethernet
network | C264, Scs | Ethernet network | C264]
 A bay ("Feeder (1)" ) can be represented by 0, 1 or 2 "Bay mimic". Each "represents" relation has an
attribute "mimic rank for the set of bay mimic". In the case of 2 relations, each attribute value must be
unique.
33106 / BayMimic / The relation attribute value is not unique (relation, attribute)
Example:
33106 / BayMimic / The relation attribute value is not unique (relation, attribute)-> [is represented by: Bay
mimic, mimic rank for the set of bay mimic, 1]
MF-52 SCE/EN MF/C60

 For a Controller, the maximum count of managed bays (relation "is managed by") which are linked to a
"Bay mimic" (relation "represents"), is 12.
This check is performed only if the Controller GHU200 board has its attribute "HMI type" set to the
"Complete" value.
33005 / BayMimic / The count of graphically displayed Bays is not valid (count, maximum)
Example (from the Controller point of view):
33005 / BayMimic / The count of graphically displayed Bays is not valid (count, maximum)-> [13, 12]
2.5.5 SWITCHGEAR
Switchgear
Switch Ctrl SPC mutually exclusive
Switch Ctrl DPC
Switchgear pos. SPS mutually exclusive

Switchgear pos. DPS
The same type of datapoints which can be single or double (like "Switch Ctrl DPC" and "Switch Ctrl SPC") are
mutually exclusive
70066 / Switchgear / The datapoints are not compatible -> [Switch Ctrl SPC, Switch Ctrl DPC]
2.5.6 CIRCUIT BREAKER
2.5.6.1 PHASES OF CIRCUIT BREAKER
(A) circuit-breaker type

circuit breaker - Single phase CircuitBreaker
- Triple phase CircuitBreaker
Switch Ctrl DPC - Other CircuitBreaker
Switch Ctrl SPC
Switch phA DPC
1 Switch phB DPC
Switch phC DPC
Switch phA SPC
2 Switch phB SPC
Switch phC SPC
Switch PhA pos. DPS
3 Switch PhB pos. DPS
Switch PhC pos. DPS
Switch PhA pos. SPS
4 Switch PhB pos. SPS
Switch PhC pos. SPS
Switchgear pos. SPS
Switchgear pos. DPS
Ph not together SPS
 • The objects “Single Phase” and “Triple Phase”, respectively containing mandatory dataPoints for a
circuit breaker single phase or triple phase are mutually exclusive:
40404 / CircuitBreaker / Circuit breaker configuration inconsistent: one and only one 'Single phase' or
'Triple phase' object is allowed
SCE/EN MF/C60 MF-53

If the circuit breaker is a "Single phase CircuitBreaker”, then the computed DPS and the Switch Control DPC
are mandatory for each phase:
40093 / CircuitBreaker / The datapoints set is not complete for the phases A,B,C-> [Switch phA DPC]
If the circuit breaker is a "Triple phase CircuitBreaker", then none of the datapoints referencing a phase (phA,
phB or phC) is allowed.
40094 / CircuitBreaker / The datapoint is not allowed-> [Switch phA DPC]
 All the SPS, SPC, DPS and DPC datapoints of a circuit breaker should be wired, except for:
 "Comp. Switch Pos", “Comp. PhA pos.”, “Comp. PhB pos.”, “Comp. PhC pos.” and "Order
Running" as these are computed datapoints that cannot be wired
 DataPoints under the I²t function for a triple phase circuit breaker
 "Switch Ctrl DPC" for a single phase circuit breaker.
 The wiring definition of a circuit breaker datapoints is:

 Relation “is wired on:” (wired on digital / analog channel)
 Relation “has for IED address:”
 Relation “is computed by:”
40099 / CircuitBreaker / The datapoint is not wired
2.5.6.2 SYNCHROCHECK OF CIRCUIT BREAKER
Substation
(R) is synchrocheck of
Ext manual CS
Feeder
Circuit breaker
Sync CB close SPC

Ext auto CS
Ext manual CS
Int synchrocheck
 The Circuit Breaker must be linked only once to a Synchrocheck function (relation "is synchrocheck
of").
42098 / Synchrocheck / Multiple links to synchrochecks

Example:
42098 / Synchrocheck/Multiple links to synchrochecks-> [has for synchrocheck: Ext auto CS]
 If the Circuit Breaker is linked to a Synchrocheck function (relation "is synchrocheck of"), then its
"Sync CB close" SPC Datapoint must be present.
42094 / Synchrocheck / The datapoint is not allowed-> [Site | Substation | Voltage level | BAY_CBO |
circuit breaker | Sync CB close]
If the Circuit Breaker is linked to a internal automatic Synchrocheck function (relation "is synchrocheck of"),
then its "Sync CB close" SPC Datapoint must not have a feedback xPS.
MF-54 SCE/EN MF/C60

42049 / Synchrocheck / The relation is not valid-> [Site | Substation | Voltage level | BAY_CBO | circuit
breaker | Sync CB close | has for feedback : Switchgear pos.]
If the Circuit Breaker is linked to external Synchrocheck or internal auto synchrocheck function (relation "is
synchrocheck of"), then its "Sync CB close" SPC Datapoint must be present.
In case of Internal Manual Synchrocheck this datapoint is optional.
42089 / Synchrocheck / The datapoint is missing-> [Sync CB close]
 If a Circuit Breaker has a xPC "Sync CB Close" and a Gateway device is present within the database,
then a datapoint “Switch Ctrl xPC” must exist under the breaker.
42089 / Synchrocheck / The datapoint is missing-> [Switch Ctrl xPC]
 If a Circuit Breaker linked to an external Synchrocheck or an internal automatic synchrocheck function

(relation "is synchrocheck of"), has a xPC "Sync CB Close", datapoint “Switch Ctrl xPC” and that a
Gateway is present, then the datapoint “Switch Ctrl xPC” must have a 'has for IEC address:' relation
link.
73401 / Datapoint / The ‘Switch Control xPC’ must have an IEC address when a ‘xPC Sync CB Close’ is
present
 If a circuit-breaker has a xPC "Sync CB Close" and if a Gateway device is present within the database,
then a datapoint “Switch Ctrl xPC” must exist under the circuit-breaker.
42089 / Synchrocheck / The datapoint is missing-> [Switch Ctrl xPC]
 If a Circuit Breaker linked to external Synchrocheck or internal automatic synchrocheck function

(relation "is synchrocheck of"), has a xPC "Sync CB Close", datapoint “Switch Ctrl xPC” and if a
Gateway device is present, then the datapoint “Switch Ctrl xPC” must have a 'has for IEC address:'
relation link.
73401 / Datapoint / The ‘Switch Control xPC’ must have an IEC address when a ‘xPC Sync CB Close’ is
present
 if a circuit-breaker has got a xPC "Sync CB Close" managed by a "CtrlPopup", then a datapoint
“Switch Ctrl xPC” must exist under the breaker and be managed by this "CtrlPopup".
42156 / Synchrocheck / The datapoint is missing (popup usage) -> [Switch Ctrl xPC]
47157 / Symbol / The ctrl popup must act on the following datapoint -> [Switch Ctrl xPC]
Type 3 synchrocheck can manage up to 3 circuit breakers. The three ranks of circuit breakers are: "CB1 in
diameter topology", “CB2 in diameter topology" and "CB3 in diameter topology". It is mandatoty that the CBs
are ranked as follows:
 CB 1: "CB1 in diameter topology"

An error message is generated for each erroneous configuration of CB rank:
42389 / Synchrocheck / Site | Substation | Voltage level | BAY_SC | Synchrocheck / If a synchrocheck

type 3 has one circuit breaker, the circuit breaker should have "rank of the circuit breaker" = " CB1 in
diameter topology "
SCE/EN MF/C60 MF-55


type 3 has two circuit breakers, the circuit breakers should have "rank of the circuit breaker" = " CB1 in
diameter topology”, “CB2 in diameter topology s"

type 3 has three circuit breakers, the circuit breakers should have "rank of the circuit breaker" = " CB1 in
diameter topology”, “CB2 in diameter topology",“CB3 in diameter topology "
You can also have this error if you configured third circuit breaker of a synchrocheck (using relation ”is
synchrocheck of CB3”) without having configured the second CB:
42389 / Synchrocheck / Site | Substation | Voltage level | BAY_SC | Synchrocheck / It is not possible for
a synchrocheck to manage third circuit breaker if it does not manages second one
 If a synchrocheck type 3 is used with a TMU220 board, the only MVs available are the following
"measurement type" attribute values":
 VAN, RMS value of the voltage phase
 VBN, RMS value of the voltage phase
 VCN, RMS value of the voltage phase
 Vbusbar RMS1 value of the busbar
 signed dV
 signed dF
 signed dPhi
 signed dV for CB2
 signed dF for CB2
 signed dPhi for CB2
 signed dV for CB3
 signed dF for CB3
 signed dPhi for CB3
42393 / Synchrocheck / Scs | Ethernet network | C264 CS type3 | TMU220 / No computed MV on a

TMU 220 used with a synchrocheck type 3
MF-56 SCE/EN MF/C60

Synchrochecks have mandatory, optional, and forbidden datapoints. The green tick mark indicates that the
datapoint is permitted, the red cross that it is forbidden, O/M/C = Optional/Mandatory/Conditional:
SCE short name SCE long name SC1 SC2 SC3 O/M/C
on/off sec. SPS on/off secondary SPS    O
on/off ctrl SPC on/off ctrl SPC
   C(1)
on/off ctrl DPC on/off ctrl DPC
Voltage presence Presence of voltage   x M
Ref. U presence Presence of reference voltage   x M
Voltage absence Absence of voltage   x M
Ref. U absence Absence of reference voltage   x M
Fuse fusion first U Fuse fusion of first voltage   x O
Fuse fusion ref. U Fuse fusion of reference voltage   x O
Accept forcing Accept forcing   x O
Possible closing Possible closing   x M
CS locked CS locked   x O
busbar V choice busbar voltage choice  x x O
Bypass Bypass check volt x  x O
Scheme LD/BD Close scheme LD/BD x  x O
Scheme LD/BL Close scheme LD/BL x  x O
Scheme LL/BD Close scheme LL/BD x  x O
Scheme Locking Close scheme Locking x  x O
Scheme Coupling Close scheme Coupling x  x O
Delta drift Delta drift  x x O
CS in progress Synchrocheck in progress    M
Locking mode Locking mode  x x O
Split sync mode Split synchro mode  x x O
CB1 with VT-B0 CB1 with VT-B1 x x  O
CB1 with VT-L1 CB1 with VT-L1 x x  O
CB1 with VT-NU0 CB1 with VT-NU1 x x  O
on/off main SPS on/off main SPS    M
on/off main SPC on/off main control SPC    M
(1)
: For “on/off ctrl SPC” and “on/off ctrl DPC”, it is mandatory to have one and only ne of the two commands
(see check 42066). One of the datapoints is mandatory for manual synchrocheck, both are forbidden for
automatic.
SCE/EN MF/C60 MF-57

If one of the mandatory datapoints is missing, the following message is displayed:

type 3 has four circuit breakers, the circuit breakers should have "rank of the circuit breaker" = "linked to A-B
VTs", "linked to B-C VTs", "linked to C-Busbar VTs", "linked to Busbar-A VTs"The datapoint is missing for a
synchrocheck type 1 (SPS)-> [Possible closing]
If a forbidden datapoint has been configured, the following message is displayed:
42391 / Synchrocheck / Site | Substation | Voltage level | BAY_SC | Synchrocheck / The datapoint is not
allowed for a synchrocheck type 3 (SPS)-> [Delta drift]
For type 1 synchrocheck, the wiring mode of the synchrocheck must be consistent with the TMU network
topology or TMU network localization:
Synchrocheck TMU wiring Allowed
Star on both side Remote or star yes
Star on both side Delta no
Delta on both side Remote or star no
Delta on both side Delta yes
Star on line – delta on busbar Remote or star no
Star on line – delta on busbar Delta yes
Delta on line – star on busbar Star yes
Delta on line – star on busbar Remote or Delta no
If this is not the case, the error message 42390 indicates that the wiring mode does not match the network
topology or the board localization.
42390 / Synchrocheck / Site | Substation | Voltage level | BAY_SC | Synchrocheck / The wiring mode
should be star for a remote TMU board (wiring mode)-> [delta on both side]
42390 / Synchrocheck / Site | Substation | Voltage level | BAY_SC | Synchrocheck / The wiring mode is
incoherent regarding the TMU network topology (wiring mode, electrical network topology)-> [delta on both
side, Star]
If the wiring mode is different from “Star on both side” and “Delta on both side” on a TMU220, the feature
with 2 circuit breakers and 2 Busbar voltages managed by the synchrocheck is not available.
So for Synchrocheck Type1, if the selected wiring mode is “star on line - delta on busbar” or “delta on line -
star on busbar” a check error will occur if the Synchrocheck manages more than 1 circuit breaker.
42395 / Synchrocheck / Site | Substation | Voltage level | BAY_SC | Synchrocheck / For a Synchrocheck
Type 1, if wiring mode is not "Star on both side" or "Delta on both side", the Synchrocheck cannot manage
more than 1 Circuit Breaker
MF-58 SCE/EN MF/C60

2.5.7 AUTOMATION
2.5.7.1 FBD AUTOMATION

2.5.7.1.1 FBD status
(A) FBD status

FBD automation - Modified
- Correct
- Failure
 The value of the attribute "FBD status" must be "Correct".

38101 / Automation / The attribute value is not valid
Example:
38101 / Automation / The attribute value is not valid-> [FBD status, Modified]
 The developed equation cannot contain more than 256 datapoints.

38160 / Automation / The developed equation is to big (do not exceed 256 datapoints)
 A controller must not manage more than 200 FBD/interlocks

38288 / Automation / Too much FBD/Interlock for a computer (count, max)
 FBD must not contain TON/TOFF block with a timer value lower than t#50ms.
38252 / Automation / FBD contains at least one timer value lower than 50 miliseconds (lower value)
2.5.7.1.2 Input/Output plugs
(R) uses DPS DPS

FBD automation (R) uses SPS SPS
(R) uses MPS MPS
FBD inputs (R) uses MV MV
FBD input (R) uses DPC DPC
(R) uses SPC SPC
FBD outputs (R) controls DPC DPC

FBD output (R) controls SPC SPC
(R) produces SPS SPS
 For one "FBD input" plug, only one relation is allowed.

39088 / AutomationIOPlug / Multiple links to datapoints
Example:
39088 / AutomationIOPlug / Multiple links to datapoints-> [uses DPS: Bay DPS]
 For one "FBD output" plug:

 the count of relations towards DPC or SPC Datapoints must be  4
 the count of relations towards SPS Datapoints must be  4
 a SPC/DPC datapoint cannot be linked more than once to the same FBD output
SCE/EN MF/C60 MF-59

39088 / AutomationIOPlug / Multiple links to datapoints

Example:
39088 / AutomationIOPlug / Multiple links to datapoints-> [controls DPC: Bay DPC]
 Any input or output of FBD automatism that is not served by the controller managing the FBD, must
have ‘goose usage’ attribute set to ‘true’ at data object level of the associated datapoint.
 bloc MASK accepts only LSP datapoint on entry “nMPS”. (Error 39219)
 FBD bloc MASK doesn’t accept LSP datapoint on “bit” entry (0 to 15) (Error 39220)
Only LSP datapoint
No LSP datapoints
39219 / AutomationIOPlug / Fbd Mask nMPS entry must be direct-link with LSP (Uses data point)
Example:
39219 / AutomationIOPlug / Fbd Mask nMPS entry must be direct-link with LSP (Uses data point)-> [Site |
Substation | Voltage level | Generic bay | Generic module | Module MPS]
39220 / AutomationIOPlug / Fbd Mask bit entry must not be link with LSP (Uses data point) (Uses data
point)
Example:
39220 / AutomationIOPlug / Fbd Mask bit entry must not be link with LSP (Uses data point)-> [Site |
Substation | Voltage level | Generic bay | Generic module | LSP]
Any Fbd Input/Output must be link with at least one data point
39226 / AutomationIOPlug / Fbd input/output must be link with one data point
Any input or output of FBD automatism that is not served by the controller managing the FBD, must have
‘goose usage’ attribute set to ‘true’ at data object level of the associated datapoint.
22149 / DatapointClient / The client-server relation must be goosed for Automation/Mapping usage at
client level (server, client)
22150 / DatapointClient / The IEC relevant address must be goosed for Automation/Mapping usage
MF-60 SCE/EN MF/C60

 Any Fbd Input/Output must be used in the diagram

39271 / AutomationIOPlug / The IOPlug must be used in FBD diagram
2.5.7.1.3 FBD consistency

In some degraded cases, an FBD may be inconsistent. There are 3 possible results:
 the XML file doesn’t exist

 the XML file is not correct
 the inputs/outputs or settings defined in XML file are not present in SCE database
38273 / Automation / The FBD's XML file doesn't exists -> [XML file]
38274 / Automation / The FBD's XML file is corrupt -> [XML file]
38275 / Automation / The FBD has inconsistent input, output or setting -> [XML file]
When such problem raise, the FBD is corrupted, and must be deleted.
For instance objects or template clones, the check is done on template source
2.5.7.1.4 Datapoint used by FBD at DS Agile C26x level
At DS Agile C26x level, a datapoint cannot be used more than 255 times in the set of its PSLs.
38222 / Automation / The datapoint is used more than 255 times in the PSLs of MICOM C264 [C264, nb
tims >255]
2.5.7.1.5 Settings DS Agile S1 used by FBD at DS Agile C26x level
By DS Agile C26x, the number of Boolean settings DS Agile S1 used in FBD cannot be greater than 100.
38253 / Automation / The number of FBD boolean settings MicomS1 for this C264 is too great [C264, nb
> 100]
By DS Agile C26x, the number of Timer settings DS Agile S1 used in FBD cannot be greater than 100.
38254 / Automation / The number of FBD timer settings MicomS1 for this C264 is too great [C264r, nb >
100]
By DS Agile C26x, the number of settable FBD cannot be greater than 50.
38269 / Automation / The number of settable FBD for this C264 is too great [C264, nb > 50]
For each FBD operator the maximum number of boolean setting per operator basis (AND, OR …) is 1.
38293 / Automation / There are more than one boolean setting for the operator
For each timer and accurate timer, the default value must be between the minimum value and maximum
value.
38312 / Automation / The default value is not between minimum and maximum value
For each timer and accurate timer, the default value must be a multiple of step value.
Example: a step of 15 allows a default value of 15, 30, 45, 60, etc…
38320 / Automation / Default value for FBD timer must be a multiple of step value
SCE/EN MF/C60 MF-61

For each FBD function block (TON, TOFF, TON_A, TOFF_A and RS) it is not allowed to have a boolean
setting.
38314 / Automation / The function block cannot have a boolean setting as input
2.5.7.2 SLOW AUTOMATION

2.5.7.2.1 Modified flag
(A) modified
Slow automation - Yes
- No
The value of the attribute "modified" must be "No".
38101 / Automation / The attribute value is not valid

Example:
38101 / Automation / The attribute value is not valid-> [modified, Yes]
2.5.7.2.2 Input/Output
Any input or output of slow automation that is not served by the controller managing the automation, must
have ‘goose usage’ attribute set to ‘true’ at data object level of the associated datapoint.
22149 / DatapointClient / The client-server relation must be goosed for Automation usage at client level
(server, client)
22150 / DatapointClient / The IEC relevant address must be goosed for Automation/Mapping usage.
2.5.7.2.3 Settings DS Agile S1 used by UserFunctions (Slow Automation) at C26x level
By DS Agile C26x, the number of settings DS Agile S1 (Boolean, Integer, Float) used in Isagraf cannot be
greater than 100.
38341 / Automation / The number of Isagraf settings MicomS1 for this C264 is too great [C264, nb > 100]
By DS Agile C26x, the number of settable Isagraf functions cannot be greater than 50.
38268 / Automation / The number of settable Isagraf function for this C264 is too great [C264 nb > 50]
 For an Isagraf settings MicomS1 of type Enum, the default index value must be smaller than the last
index used.
38363 / Automation / The default index value must be smaller than the last index used [default index
value, last index used]
2.5.8 TAP CHANGER
2.5.8.1 POSITION INDICATOR
Transformer 0
transformer (A) Value features / minimum value
Tap changer (A) Value features / maxmum value
Tap pos ind 0
The following constraint between the two attributes must be respected:
MF-62 SCE/EN MF/C60

("maximum value"  "minimum value"  1)  [1..64]
37087 / TapChanger / The result of Value features/maximum value - Value features/minimum value + 1
is not in [2..64]
Moreover for analog TPI the following constraints must be respected:
 current valid range (% maximum value) > (2 / (maximum acq. value - minimum acq. value))
37212 / TapChanger / The constraint is not valid:[current valid range (% maximum value) > (2 /
(maximum acq. value - minimum acq. value))]
 current valid range (% maximum value) < (100 / (maximum value - minimum value))
37212 / TapChanger / The constraint is not valid:[current valid range (% maximum value) < (100 /
(maximum value - minimum value))]
37363 Min and max value of transformer don't belong to the interval minimum value - maximum value of
the TPI (MinUsablePosition < MinScaledValue and/or MaxUsablePosition > MaxScaledValue)
2.5.8.2 RAISELOWER / GOTOMINMAX COHERENCE
Transformer
transformer
Tap changer (R) has for profile (A) SBOMode ?
Raise/lower DPC DPC profile
Goto min/max DPC
On Tap changer, if the Raise/lower DPC is SBO Many, forbid the Goto min/max DPC
37178 / TapChanger / When Raise/lower DPC is SBO Many, Goto min/max DPC is not allowed
2.5.9 AUTORECLOSER FUNCTION
- Not used
- 1P
- 1P-3P
- 1P-3P-3P
(A) functioning mode (1 ph trip) - 1P-3P-3P-3P
Feeder (A) functioning mode (3 ph trip)
Autorecloser - Not used
- 3P
- 3P-3P
- 3P-3P-3P
- 3P-3P-3P-3P
(A) 1st period monophased 500

(A) 1st period triphased 500
(A) 2nd period triphased 5000
(A) 3rd period triphased 5000
(A) 4th period triphased 5000
 The two attributes "functioning mode (1 ph trip)" and "functioning mode (3 ph trip)" must not be both
set to "Not used" value.
41096 / Autorecloser / The attribute values are not compatible-> [functioning mode (1 ph trip) = Not used,
functioning mode (3 ph trip) = Not used]
SCE/EN MF/C60 MF-63

 If "functioning mode (1 ph trip)" value is set to "1P-3P-3P-3P", then the following rules must be
respected:
 "1st period monophased" < "2nd period triphased"
 "1st period monophased" < "3rd period triphased"
 "1st period monophased " < "4th period triphased"
If "functioning mode (1 ph trip)" value is set to "1P-3P-3P", then the following rules must be respected:
 "1st period monophased" < "3rd period triphased"
If "functioning mode (1 ph trip)" value is set to "1P-3P", then the following rule must be respected:
41103 / Autorecloser / 1st period monophased (ms) is not lower than 2nd period triphased (ms)
41103 / Autorecloser / 1st period monophased (ms) is not lower than 3rd period triphased (ms)
41103 / Autorecloser / 1st period monophased (ms) is not lower than 4th period triphased (ms)
 If "functioning mode (3 ph trip)" value is set to "3P-3P-3P-3P", then the following rules must be
respected:
 "1st period triphased" < "2nd period triphased"
 "1st period triphased" < "3rd period triphased"
 "1st period triphased" < "4th period triphased"
If "functioning mode (3 ph trip)" value is set to "3P-3P-3P", then the following rules must be respected:
 "1st period triphased" < "3rd period triphased"
If "functioning mode (3 ph trip)" value is set to "3P-3P", then the following rule must be respected:
41103 / Autorecloser / 1st period triphased (ms) is not lower than 2nd period triphased (ms)
41103 / Autorecloser / 1st period triphased (ms) is not lower than 3rd period triphased (ms)
41103 / Autorecloser / 1st period triphased (ms) is not lower than 4th period triphased (ms)
MF-64 SCE/EN MF/C60

- Not used
- 1P
- 1P-3P
- 1P-3P-3P
Feeder (A) functioning mode (3 ph trip)
Trip PhA - 3P
Trip PhB - 3P-3P
Trip PhC (A) unlocking way
- 3P-3P-3P
- 3P-3P-3P-3P
on/off ctrl DPC
on/off ctrl DPS
lock/reinit SPC - Not used

lock/reinit SPS - Reinitialization
- Manual close
- Both ways
 If "functioning mode (1 ph trip)" value is different from "Not used", then at least one of the three SPS
datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is mandatory.
41090 / Autorecloser / One of the datapoints is missing-> [Trip PhA, Trip PhB, Trip PhC]
 If "functioning mode (1 ph trip)" value is set to "Not used", then none of the three SPS datapoints {
"Trip PhA", "Trip PhB", "Trip PhC" } is allowed.
41097 / Autorecloser / The attribute value is incompatible with the datapoints-> [functioning mode (1 ph
trip) = Not used, Trip PhA, Trip PhB, Trip PhC]
 The two datapoints { "on/off ctrl DPC", "on/off ctrl DPS" } are mutually exclusive and, at least one of
them is mandatory.
41066 / Autorecloser / The datapoints are not compatible-> [on/off ctrl DPC, on/off ctrl DPS]
41090 / Autorecloser / One of the datapoints is missing-> [on/off ctrl DPC, on/off ctrl DPS]
 The two datapoints { "lock/reinit SPC", "lock/reinit SPS" } are mutually exclusive. If the "unlocking way"
attribute value is set to "Reinitialization" or "Both ways" then at least one of the two datapoins is
mandatory.
41066 / Autorecloser / The datapoints are not compatible-> [lock/reinit SPC, lock/reinit SPS]
41090 / Autorecloser / One of the datapoints is missing-> [lock/reinit SPC, lock/reinit SPS]
SCE/EN MF/C60 MF-65

- Not used
- 1P
- 1P-3P
- 1P-3P-3P
Feeder
(R) is autorecloser of (A) functioning mode (3 ph trip)
- 3P
Circuit breaker - 3P-3P
- 3P-3P-3P
(A) circuit-breaker type - 3P-3P-3P-3P
- Single phase CircuitBreaker

- Triple phase CircuitBreaker
- Other CircuitBreaker
 If "functioning mode (1 ph trip)" value is different from "Not used", then the "circuit-breaker type" must
be set to "Single phase CircuitBreaker".
41096 / Autorecloser / The attribute values are not compatible-> [functioning mode (1 ph trip) = 1P, Site |
Substation | Voltage level | Feeder | circuit breaker | circuit-breaker type = Triple phase CircuitBreaker]
 If "functioning mode (3 ph trip)" value is set to "Not used", then the "circuit-breaker type" must be set to
"Single phase CircuitBreaker".
41096 / Autorecloser / The attribute values are not compatible-> [functioning mode (3 ph trip) = Not used,
Site | Substation | Voltage level | Feeder | circuit breaker | circuit-breaker type = Triple phase CircuitBreaker]
 The Autorecloser cannot be placed in a bay managed a C26x other than the one managing the circuit
breaker.
41011 / Autorecloser / The relation link is not compatible with the filter ->
[‘Site | Substation | Voltage level | Generic bay | AR’ is managed by:
‘Site. | Substation | Voltage level | Generic bay | Circuit breaker’]
MF-66 SCE/EN MF/C60

2.5.10 SYNCHROCHECK FUNCTION
Substation
Ext manual CS
on/off ctrl DPC
mutually exclusive + wired
on/off ctrl SPC
on/off DPS
on/off SPS mutually exclusive
Feeder
Ext auto CS
on/off ctrl DPC
on/off ctrl SPC mutually exclusive
on/off DPS
Ext manual CS
on/off ctrl DPC mutually exclusive + wired
on/off ctrl SPC
on/off DPS
Int auto CS
on/off ctrl DPC forbidden
on/off ctrl SPC
on/off SPS
Int manual CS
on/off ctrl DPC mutually exclusive
on/off ctrl SPC
on/off SPS
 As shown in the picture, under a Synchrocheck function, some Datapoints are mutually exclusive and
some must be wired.
Note: Here, the term "wired" means that the datapoint must be linked to a digital/analogue channel of a controller, or
linked to an IED address.
42066 / Synchrocheck / The datapoints are not compatible-> [on/off ctrl DPC, on/off ctrl SPC]
42066 / Synchrocheck / The datapoints are not compatible-> [on/off SPS, on/off DPS]
42099 / Synchrocheck / The datapoint is not wired
 For a "Int manual synchrocheck" function, the "on/off ctrl DPC" or "on/off ctrl SPC" Datapoint must be
present.
42090 / Synchrocheck / One of the datapoints is missing-> [on/off ctrl DPC, on/off ctrl SPC]
 Only one internal synchrocheck can be configured on a per controller basis.

42151 / Synchrocheck / More than one internal synchrocheck on the same computer
SCE/EN MF/C60 MF-67

 For an internal synchrocheck, all associated circuit-breakers must be managed by the same controller
than the synchrocheck.
 42152 / Synchrocheck / The internal synchrocheck and the breaker have not the same manager
 For an internal synchrocheck, the controller managing the synchrocheck must have a TMU200 or a
TMU220 board.
42159 / Synchrocheck / A TMU200 Board , TMU220 or TMU210 board is missing for internal
synchrocheck type 1 use at computer level
 For an internal synchrocheck, if the datapoint CS_BusBarVChoice_SPS exists under the

synchrocheck, the associated TMU board must be a TMU220
42204 / Synchrocheck / The TMU220 board is missing for datapoint usage in reference
 For an internal synchrocheck, if set as type 2, the associated TMU board must be a TMU210
42264 / Synchrocheck / The TMU210 board is missing for synchrocheck of type 2
For an internal synchrocheck, if coupling function is set, the value of Ta cannot be null.
42326 / Synchrocheck / The value of Ta cannot be null for the coupling function usage
2.5.11 ATCC FUNCTION
Substation
ATCC
(A) ATCC existence - Yes
Voltage level (1) - No
Transformer
transformer
ATCC fct needs
Tap changer (R) has its primary on

Raise/lower DPC or
(R) has its secondary on
MCB position DPS
MCB position SPS
BusBar
ATCC fct needs
Voltage level (2)
 If there is no ATCC under the Substation, then:

 a "Voltage level" must not have its "ATCC existence" attribute set to "Yes".
 the "ATCC fct needs" is allowed neither under a "transformer" nor under a "BusBar".
26101 / ATCC / The attribute value is not valid-> [ATCC existence, Yes]
26109 / ATCC / The component is not allowed-> [ATCC fct needs]
 If there is an "ATCC fct needs" under a "transformer", then:

 the "Tap changer" with its "Raise/lower DPC" Datapoint are mandatory.
MF-68 SCE/EN MF/C60

 one of the two Datapoints { "MCB position DPS", "MCB position SPS" } is mandatory. They are
mutually exclusive.
 the "transformer" must be linked to a Voltage level through one and only one of the relations { "has
its primary on", "has its secondary on" }. The Voltage level must be different from the one under
which the transformer is located.
26110 / ATCC / The component is missing-> [Tap changer]
26089 / ATCC / The datapoint is missing-> [Raise/lower DPC]
26090 / ATCC / One of the datapoints is missing-> [MCB position DPS, MCB position SPS]
26066 / ATCC / The datapoints are not compatible-> [MCB position DPS, MCB position SPS]
26111 / ATCC / The link to primary or secondary voltage level is missing
26044 / ATCC / The relation types are not compatible-> [has its primary on, has its secondary on]
26050 / ATCC / The relation link is not valid-> [has its primary on: Voltage level]
 If an ATCC is defined, then all Switchgears and Circuit Breakers must have a Switchgear Position
datapoint.
26090 / ATCC / One of the datapoints is missing -> [Switchgear position]
 If an ATCC is defined, then the voltage MV of transformer or BusBar ATCC functions cannot be wired
both:
 If voltage MV of transformers are wired (in board or on IED), voltage MV of BusBar must be
computed.
 If voltage MV of BusBar are wired (in board or on IED), voltage MV of transformers must be
computed.
26176 / ATCC / The voltage MV wiring of an ATCC function is not compliant full ATCC description
 The ATCC and the circuit breaker managing that ATCC should be in same Substation
26011 / ATCC / The relation link is not compatible with the filter -> [‘Site | Substation | Voltage level |
Generic bay | ATCC’ is managed by: ‘Site | Substation | Voltage level | Generic bay | Circuit breaker’]
2.5.12 PROTECTION MODULE

The following checks concerns protection functions embedded in DS Agile C26x protection and control unit.
They required the presence of the TMU210 board for the DS Agile C26x protection and control unit.
 As soon as one or several bays managed by a DS Agile C26x protection and control unit have a
integrated protection function, this DS Agile C26x protection and control unit must contain a TMU210
board.
<09153>/ Calculator boards / The TMU210 board is missing for protection function usage
SCE/EN MF/C60 MF-69

 For the set of bays managed by a DS Agile C26x protection and control unit, each kind of protection
function can be present only once.
<55154> / Module protection / Kind of protection module is defined more than once for the computer.
For the set of bays managed by a DS Agile C26x protection and control unit:
 as soon as one of them uses a protection function, the “relay automatism” function must be present.
 if a 81U exists, a 81O must also exist
 if a 81O exists, a 81U must also exist
 if a 81R exists, both 81U and 81R must exist
<55155> / Module protection / “relay automatism” function is missing.
<55156> / Module protection / “81O” function is missing.
<55157> / Module protection / “81U” function is missing.
<55158> / Module protection / “81O”or “81U” function is missing.
<55329> / Module protection / “81O”or “81U” functions muusy have the same trip usage values.
2.5.12.1 EPATR FUNCTION (RESISTIVE EARTH FAULT PROTECTION)

When a TMU210 is configured with attribute ‘EPATR tore type‘ set to a value different from ‘not used’, the
EPATR function is active for this board. Subsequently, the following checks are implemented:
For the set of bays managed by the relevant controller, the protection function ‘67N’ is required.
<71215> / EPATR / the protection function 67N is missing for EPATR usage
The following datapoints are required under the 67N protection function:
15A_over_current, 1_2_s_over_current, EPATR_RSE_Mode, EPATR_DSP_RSE_Mode
<71216> / EPATR / the datapoint is missing for EPATR usage: <required datapoint short name>
2.5.12.2 BUILT-IN FUNCTION TRIP CURRENT MEASUREMENTS
 To use the trip current measurement built-in function, it is necessary to add the 3 trip current MVs
under the automatism relay, only the neutral current is optional.
55376 / automatism / For the built-in function 'trip current measurements' the 3 phases measurements (a,
b, c) are mandatory and In measurement is optional
 It is possible to add these measurements only if one or more overcurrent protection function
[67/50/51/67N/50N/51N] is defined for the controller managing the automatism relay.
 If the [67] or [67N] protection fuction is used, the 3 SPS datapoints “Ia phase fault” , “Ib phase fault”
and “Ic phase fault” must be added to the automatism built-in function. The earth fault datapoint “In
phase fault” is optional.
55377 / automatism / The built-in function 'trip current measurements' requires one or more MAXI
protection [67/50/51/67N/50N/51N]
MF-70 SCE/EN MF/C60

2.5.12.3 BUILT-IN FUNCTION PHASE SEGREGATION
 To use the built-in function phase segregation you must add the 3 SPS “Ia phase fault”, “Ib phase
fault” and “Ic phase fault”. The earth “In phase fault” is optional.
55382 / automatism / For the built-in function 'phase segregation' the 3 phases faults (a, b, c) are
mandatory and In earth is optional
 If the 3 SPS datapoints “Ia phase fault”, “Ib phase fault” and “Ic phase fault” are used, the [67] or [67N]
protection function must be added.
55382 / automatism / The protection function 67 or 67N is missing for the ‘overcurrent phase
segregation' usage
2.5.13 TOPOLOGY
The following checks concern the electrical topology, i.e. nodes values existing at electrical module level.
They are run when an ATCC function or a Fast Load Shedding function is configured. In the folloqing, used
node means node whose value is different from 65535
The used nodes of a module cannot have the same value.
<74239> / Topology / the nodes of a module cannot have the same value
Two modules cannot have the same set of used nodes.
<74240> / Topology / two modules cannot have the same node values
For a transformer, its adjacent non-generic modules located in the same Transformer bay should have at
least 2 used nodes.
<74241> / Topology / node values are missing for modules (at least 2 values are required)
2.5.14 FAST LOAD SHEDDING

If LSP datapoints exist in configuration data base the relation ‘has for main FLS server’ is mandatory at site
level
<75244> / Fast load shedding / Site / Relation 'Has for main FLS server' mandatory to manage LSP
datapoints
2.5.15 LOAD SHEDDING/ LOAD CURTAILEMENT

A controller can manage only one load shedding function and/or only one load curtailment function. Load
function are configured at bay level.
79278 /Load function / RTU | Computer | C264_LS / Invalid number of load curtailment managed by the
computer, only one load curtailment function must be configured per computer (load curtailment functions)->
[Site | Substation | Electrical Bay | Generic bay | Load function 1,
Site | Substation | Electrical Bay | Generic bay 1 | Load function,
Site | Substation | Electrical Bay | Generic bay 1 | Load function 1]
2.5.16 I²T FUNCTION

When I²t function is configured, the 67 relay function must exist.
81280 / I²t function / Site | Substation | Voltage level | Generic bay | I²t function / The protection module
'67' is missing for the computer, mandatory for I²t function.
TMU210 board must exist at controller level if I²t function is configured.
SCE/EN MF/C60 MF-71

09153 / ComputerBoards / Scs | Ethernet network | C264 / The TMU210 board is missing for protection
module usage at computer level.
TMU210 board must compute the MV below if I²t function is configured.
 IT_phase_A
 IT_phase_B
 IT_phase_C
 IT_total
 I2T_phase_A
 I2T_phase_B
 I2T_phase_C
 I2T_total
81281/ I²t function / Site | Substation | Voltage level | Generic bay | I²t function / Missing mandatory
computed MV for I²t function (Computed MV)-> [I²T: IT_phase_A]
Only one I²t function can be configured per controller.
55154/ Protection module / Site | Substation | Voltage level | Generic bay 1 | I²t function
The kind of protection module is defined more than once for the computer-> [Scs | Ethernet network | C264].
2.5.17 AVR FUNCTION

Controller can manages one and only one AVR function
Bay 1
Manages
AVR
Manages
Bay 2 C264
AVR
84298 / AVR / Scs | Ethernet Network | C264 / Invalid count of AVR managed by the same computer
(count,max,managed AVR functions)
In same configuration database AVR must be configured with same mode : Stand Alone XOR Master
Follower in parallel XOR MCC
84299 / AVR / Substation / AVR functions with different working mode is not compatible
Maximum of four AVR function configured in Master Follower in parallel or MCC
84300 / AVR / Substation / Invalid count of AVR function for Master follower in parallel mode or MCC
mode (count, max)
MF-72 SCE/EN MF/C60

For AVR function configured in Master Follower in parallel or MCC mode, one and only AVR with role
“Master” must be configured an a maximum of 3 “Follower” can be configured.
84301 / AVR / Substation / Invalid count of AVR master (count of master, min of master, max of master)
84302 / AVR / Substation / Invalid count of AVR slave (count of slave, min of slave, max of slave)
Bay 1
AVR Role = Only one Master AVR
Bay 2
AVR Role = Follower
Bay 3
AVR Role = Follower Maximum of 3 AVR followers
Bay 4
AVR Role = Follower
84096 / AVR / Site | Substation | Voltage level | AVR | AVR / Transfo in // / Transformer in parallel
When the AVR RPF used attribute is true then AVR Transformer in parallel attribute must be false
84096 / AVR / Site | Substation | Voltage level | AVR | AVR / Voltage / Double wound
When the AVR RPF used attribute is true then AVR Double wound attribute must be false
 Built-in function AVR and the associated Tap function should be in same Substation
84011 / AVR / The relation link is not compatible with the filter -> [‘Site | Substation | Voltage level |
Generic bay | AVR’ is managed by: ‘Site | Substation | Voltage level | Transformer | transformer | Tap
changer’]
2.5.18 VTFUSE FUNCTION

If a VTFuse is managed by a TMU210 board, there is a constraint with the TMU network type:
87387 / VTFuse / Scs | Ethernet network | C264 | TMU210 / When a VTFuse is on a bay managed by a
c264 having a TMU210, the TMU210 cannot have network type set as '2 Vpn + V0 (partial star)', '3 Vpp + V0
(partial delta)' or '3 Vpp + Vb (delta)'
SCE/EN MF/C60 MF-73

2.6 GRAPHICAL CHECKS
2.6.1 O I WORKSPACE
Scs
Ethernet network (R) has for workspace Graphic
OI bay OI workspace #1
OI Server OI workspace #2
OI Client (R) has for workspace
2.6.1.1 DISPLAY RESOLUTION

An OI Workspace which has for display resolution 800x600 must be used only by an OI Bay
78267 / OI Workspace / The displayed resolution 800x600 must be used only by an OI Bay
2.6.1.2 LIMITATIONS
An OI workspace shouldn’t contain more than 150000 graphic objects (i.e. graphical symbols).
78313 / OI Workspace / The number of graphical objects by OI Workspace exceed the acceptable limit
(count of objects, max value)
2.6.1.3 OI BAY LIMITATIONS

A workspace used by an OI Bay must respect some constraints.
Alarm, Title and Command banners are not allowed in 800x600 resolution.
78268 / OI Workspace / The Alarm, Title and Command banners are not allowed in a 800x600
workspace -> [forbidden component]
Up to five mimics are allowed by workspace.
78269 / OI Workspace / Up to five mimics are allowed in an OI Bay workspace -> [mimic count]
The count of ActiveX must respect the following rules:
 Only one alarm viewer and one trend viewer can be configured
 FSS viewer is not allowed
78270 / OI Workspace / The count of an activeX type is not good in an OI Bay workspace -> [ActiveX
type, allowed, count]
The workspace of an OI Bay in 800x600 resolution must have at least actions Login and Exit (actions are
specific launch actions):
78277 / OI Workspace / The mandatory action type is not defined for the 800x600 workspace -> [action
type]
MF-74 SCE/EN MF/C60

2.6.2 OI WINDOW
Graphic Scs
OI workspace (R) is workspace of Ethernet network
Window OI client
Mimic
Std Alarm Banner
Std Comm. Banner
Std Title Banner
An OI "Window" which has its "OI workspace" linked to at least 1 "OI client", must not be empty.
It must contain at least one of the following components:
 Mimic(s)
 one Standard alarm banner
 one Standard command banner
 one Standard title banner
43117 / Window / The Window is empty

An OI "Window" must not contain invalid components i.e.
 TitleBanner + CommandBanner
 CommandBanner + AlarmBanner
 TitleBanner + AlarmBanner
 Mimic + (any) Banner
43370 / Window / The content of the window is not valid
2.6.3 OI MIMIC
2.6.3.1 SYMBOLS
 Coordinates of symbols
Graphic
OI workspace
window (A) width / (A) height
1000 / 700
Mimic (A) x / (A) y
AlarmViewer 0, 0
(A) x / (A) y
AlarmMultiState 0, 70
Circle (A) x / (A) y
0, 140
Group (A) x / (A) y
10, 150
Circle (A) x / (A) y
Text (A) x / (A) y 10, 150
… 10, 150
The coordinates (x, y) of a symbol must not be located outside the mimic area.
47122 / Symbol / The symbol is outside the mimic area

Example:
47122 / Symbol / The symbol is outside the mimic area (1000, 700)-> [x = 1085, y = 55]
SCE/EN MF/C60 MF-75

 Limits of the count of Symbols :
Graphic
OI workspace
window
Mimic
Group
Shape
Multistate
MultiState Max = 1500 / mimic
Shape
…
The number of symbols (shapes or multistates) cannot exceed 1700 inside a mimic. This count is done
recursively. The groups are not count, but their sons yes.
02003 / CapacityLimits / The count of Symbol components is not valid (count, maximum)
2.6.4 BAY MIMIC SYMBOLS
2.6.4.1 SYMBOLS
 Hidden Symbols:
Graphic
Comp. workspace
width = 128 / height = 128 (fixed values)
Bay mimic
LHMI Transformer (A) x / (A) y 0, 65
LHMI Gen module (A) x / (A) y 0, 85
LHMI bitmap (A) x / (A) y 0, 45
LHMI line (A) x / (A) y
(A) x / (A) y 40, 10
LHMI text
… 0, 40
The coordinates (x, y) of a symbol must not be located outside the mimic area.
47122 / Symbol / The symbol is outside the mimic area

Example:
47122 / Symbol / The symbol is outside the mimic area (128, 128)-> [x = 145, y = 6]
 Limits of the count of Symbols:

Graphic
Comp. workspace
Bay mimic max = 24 / Comp. workspace
LHMI Transformer max = 9 / Bay mimic
LHMI Gen module
LHMI bitmap max = 5 / Bay mimic
LHMI line max = 30 / Comp. workspace max = 18 / Bay mimic
LHMI text max = 5 / Bay mimic (1 is reserved for the Bay name) + 1 reserved
… for the Bay name
Some limit exceeding are prevented by the Structural Database rules. The others leads to the following
errors:

Examples:
02003 / CapacityLimits / The count of LHMI Gen module, LHMI Transformer components is not valid (count,
maximum)-> [10, 9]
MF-76 SCE/EN MF/C60

02003 / CapacityLimits / The count of LHMI bitmap, LHMI line, LHMI text components is not valid (count,
maximum)-> [21, 18]
02003 / CapacityLimits / The count of LHMI line components is not valid (count, maximum)-> [35, 30]
 Empty texts:
Graphic
Comp. workspace
Bay mimic
LHMI Transformer
(A) short name
Name
LHMI Gen module
(A) short name
Name
(A) fixed text value
LHMI text
(A) short name
EQL BP (A) short name
L/R
(A) short name
S/C BP
SBMC (A) short name
LHMI labels (A) all labels
The text of a symbol or labels must not be empty. The check is done for languages use by controller
generator.
47187 / Symbol / The text symbol of a Local HMI mustn't be empty (Language)
47188 / Symbol / The local HMI label mustn't be empty (Label name, Language)
2.6.4.2 VISUALIZED MV DATAPOINTS
Graphic Feeder
Comp. workspace (R) represents … - Cyclic long period

(A) transmission on event - Cyclic short period
Bay mimic MV - According to a % of full scale value
(R) visualizes
- According to a % of current value
 An MV Datapoint visualized in a "Bay mimic" (relation "visualizes") must be produced by a TMU board.
33168 / BayMimic / The MV datapoint must be produced by TMU board for bay DISPLAY
 An MV Datapoint visualized in a "Bay mimic" (relation "visualizes") must belong to the bay represented
by the "Bay mimic" (relation "represents").
33125 / BayMimic / The datapoint does not belong to the bay (datapoint, bay)-> [visualizes: Voltage
Level MV, represents: Feeder]
 For each visualized MV Datapoint, the "transmission on event" attribute must be set neither to "Cyclic
short period" value nor to "Cyclic long period" value to avoid overflow of the Bay mimic input buffer.
33123 / BayMimic / The attribute value is not compatible with the relation-> [transmission on event =
Cyclic short period, is visualized by: Bay mimic]
SCE/EN MF/C60 MF-77

2.6.5 STANDARD COMMAND BANNER
2.6.5.1 OI BAY
The Klaxon usage value on a Standard Command Banner of an OI Bay must be set to No, because OI bay
doesn’t manage Klaxon option.
76255 / OI Bay/ Klaxon usage value on Standard Command Banner of an OI Bay must be set to No (OI
Bay)
2.6.6 OI SYMBOLS
2.6.6.1 MULTI-STATES
Graphic
OI workspace
window Bay
Mimic (R) is managed by Board
Alarm MultiState IED
Audi. MultiState Module
Discrepancy MS …
For each Multi-State: 1, and only 1, relation "is managed by" must be linked.
49130 / MultiState / At least one relation must be linked-> [is managed by]
49113 / MultiState / Multiple links-> [is managed by: …]

Example:
49113 / MultiState / Multiple links-> [is managed by: Feeder]
Multistate cannot have another MultiState as parent (at any level)
49218 / MultiState / A multistate must not be a sub-object of another mulitstate (Parent Object)
Exemple :
SPS multistate is under an

another Multistate Object
(MPS Multistate) = Error
49218
SPS multistate is under an

another Multistate Object
(MPS Multistate) = Error
49218
Figure 2: Multistate
A multistate can only use symbol defined inside itself
49231 / MultiState / A multistate must reference only symbol defined inside it (Symbol)
MF-78 SCE/EN MF/C60

2.6.6.2 VAR TEXTS
Graphic
OI workspace
Bay
window
(R) refers to Board
Mimic
IED
Var. text
Module
…
For each "Var.Text": 1, and only 1 relation "refers to" must be linked.
For each "Launch Action": 1, and only 1 relation "acts on" must be linked.
47130 / Symbol / At least one relation must be linked-> [refers to]
47113 / Symbol / Multiple links-> [refers to: …]

Example:
47113 / Symbol / Multiple links-> [refers to: Feeder]
2.6.6.3 TREND VIEWER
Graphic
OI workspace
window
Mimic (A) trend type - real time
Trend viewer - archive
Series (1)
Series (2)
If a "Trend viewer" has its "trend type" attribute set to "real time", then it can have only 1 "Series".
45003 / TrendViewer / The count of Series components is not valid (count, maximum)
Example:
45003 / TrendViewer / The count of Series components is not valid (count, maximum)-> [2, 1]
In case of usage by an OI Bay in 800x600 resolution, there’s some limitations.
Scs
Graphic (R) is workspace of Ethernet network
OI workspace OI Bay
window
Mimic
Trend viewer
 The trend viewer type must be set to ‘real time’

45275 / TrendViewer / The trend type must be set to ‘real time’ in a 800x600 workspace
SCE/EN MF/C60 MF-79

2.6.6.4 ALARM/STATE VIEWER
Graphic
OI workspace
window
Mimic (R) is pre-filtered on
Bay
Alarm viewer Voltage level
…
For an "Alarm/state viewer", only 1 relation "is pre-filtered on" can be linked.
46112 / AlarmViewer / Multiple links to filters-> [is pre-filtered on: …]

Example:
46112 / AlarmViewer / Multiple links to filters-> [is pre-filtered on: Feeder]
For an “alarm/state viewer”, at least, one list must be defined.
46194 / AlarmViewer / Missing a defined list for alarm/state viewer
Graphic
OI workspace (A) display count of active alarms
window
Yes
Mimic (A) display count of present alarms
Alarm viewer Yes
For an “alarm/state viewer” which has a browser counting alarms, the alarm list must be defined.
46245 / AlarmViewer / The alarm list must be defined for alarm/state viewer browser which count alarms
In case of usage by an OI Bay in 800x600 resolution, there’s some limitations.
Scs
Graphic (R) is workspace of Ethernet network
OI workspace OI Bay
window
Mimic
Alarm viewer
The alarm viewer must be pre filtered
46271 / AlarmViewer / A relation “is pre-filtered on” must be defined in a 800x600 workspace
The alarm viewer mustn’t contain event list or archive list
46272 / AlarmViewer / The list of the alarm viewer is not allowed in a 800x600workspace -> [list]
The alarm viewer mustn’t have a contextual menu defined (contextual menu attribute must be set to ‘No’)
46273 / AlarmViewer / The contextual menu attribute must be set to ‘No’ in a 800x600workspace
The alarm viewer toolbar must contain only Acknowledge and Clear buttons or separators (toolbar attributes
for other buttons must be set to ‘0’)
46274 / AlarmViewer / A button of the toolbar mustn’t be used (the rank must be set to ‘0’) in an OI Bay
workspace -> [button attribute]
MF-80 SCE/EN MF/C60

2.6.6.5 ACTIVEX COLUMNS
(A) timestamp column rank

Graphic (A) origin column rank [0..6]
OI workspace (A) object name column rank [0..6]
window (A) object message column rank [0..6] ( 0 means "not used" )
Mimic (A) alarm state column rank [0..6]
(A) alarm gravity column rank [0..6]
Alarm viewer [0..6]

(A) origin column rank [0..4]
(A) object name column rank [0..4]
[0..4] ( 0 means "not used" )
(A) object message column
FSS viewer
rank [0..4]
(A) origin column rank [0..6]
(A) object name column rank [0..6]
(A) object message column rank [0..6] ( 0 means "not used" )
(A) alarm state column rank [0..6]
(A) alarm gravity column rank [0..6]
Std Alarm Banner [0..6]
For each ActiveX:

 there must be at least one column definition with a value different from 0.
 each column value (if different from 0) must be unique
44118 / ActiveX / No column is selected
44119 / ActiveX / Multiple use of the same column rank

Example:
44119 / ActiveX / Multiple use of the same column rank-> [object name column rank, origin column rank,
object message column rank, timestamp column rank, 1]
2.6.6.6 GRAPHIC AND LAUNCH ACTIONS
Graphic
OI workspace
window
Mimic (1)
Rectangle
Change view
(R) has for new view
Mimic (2)
Each "has for new view" relation of a Symbol "Change view" action must be linked to another Mimic than the
one under which the symbol is located.
47120 / Symbol / The initial and target mimics are identical

Example:
47120 / Symbol / The initial and target mimics are identical-> [has for new view: Mimic (1)]
SCE/EN MF/C60 MF-81

Graphic
OI workspace
window
Mimic
Circle
(R) acts on (R) has for profile
Open ctrl popup DPC DPC profile
(R) acts on
(R) has for profile
SPC SPC profile
For an "Open ctrl popup", all the Datapoints linked to the "acts on" relation, must fulfil the following
conditions:
 all of them, or none, are linked to the same Datapoint through the relation "has for feedback"
 all of them, or none, are linked to the same Datapoint through the relation "has for AutoManu
dependency"
 all of them have their attribute "Substation mode dependency" set to the same value (if the attribute is
available , up to four attributes may be configured))
 all of them have their attribute "bay mode dependency" set to the same value (if the attribute is
available)
 all of them have their attribute "SBMC mode dependency" set to the same value (if the attribute is
available)
 all of them have the attribute "SBO mode" of their Profile set to the same value
 if the Open Control Popup authorizes the Lock function, and if one or several of them have at the
same level the following datapoints: LockModule (SPS) and LockModule_SPC, then all of them must
belong to the same module.
47121 / Symbol / The linked datapoints have incompatible definitions (relations)-> [acts on]
For an "Open ctrl popup" authorizing the Locking function, the datapoints of locking "LockModule" and
"LockModule_SPC" for the controlled datapoint should be present.
47191 / Symbol / The locking datapoints should be present (relations)-> [acts on]
Graphic
OI workspace
window
Mimic
Circle SPS (R) has for profile SPS profile
(R) acts on
Send FSS Order or or
DPS DPS profile
For a UserAction "Send FSS Order", the datapoint (SPS or DPS) linked to the "acts on" relation must have a
profile with the attribute "EnableFSS" set to true.
47171 / Symbol / The linked datapoint profile isn't FSS enable (relations)-> [acts on]
One and only one “Launch Action” can be configured under a Graphical symbol object
MF-82 SCE/EN MF/C60

Graphic
OI Workspace
Window
Mimic
Symbol
Launch Action [0..1]
47289 / Symbol / Graphic | OI workspace | Window | Mimic | Circle / Only one launch action allowed
under graphical symbol object
2.6.6.7 TEXT
Graphic
OI workspace
window
Mimic
Text
(A) Type
(A) Box color
A text which is defined as non standard type must be transparent.
47276 / Symbol / The text color is not allowed for this type -> [type, bad color, allowed color]
Try to avoid putting a SendOrder under a Text.
47304 / Symbol / It’s better to avoid putting a Send Order under a Text symbol.
2.6.6.8 IMAGE
On image object the attribute “file name” must be defined.
47296 / Symbol/ Graphic | OI workspace | Window | Mimic | Image 2 / The attribute "file name" of an
Image object must be defined
2.6.6.9 ANIMATION ON MV
A symbol can only have one Animation for an MV.
47384 / Symbol / The symbol have two or more animation on the MV

A Rotation on an MV must have its center in the mimic
47385 / Symbol / The center of the rotation is outside the mimic area
A Translation on an MV must have the maximum position in the mimic
47386 / Symbol / The position max of the translation is outside the mimic
2.6.7 BITMAPS
All the Bitmaps of a configuration are defined in the "Bitmap table" of the configuration.
SCE/EN MF/C60 MF-83

2.6.7.1 BITMAP INDEX
Graphic
Graph. Tables
Bitmap table (A) reference index
Bitmap (1) 0
(A) reference index
Bitmap (2) 1
Bitmap (3) (A) reference index
2
The "reference index" attribute value of each "Bitmap" of the "Bitmap table" must be unique.
48115 / Bitmap / The attribute value is not unique in the Bitmap Table
Example:
48115 / Bitmap / The attribute value is not unique in the Bitmap Table-> [reference index, 0]
2.6.7.2 BITMAP SIZE
Graphic
Graph. Tables
Bitmap table - Simple
(A) type - 5-uple
Bitmap
(A) file name by default
(A) file name for 'open' state file1.png
(A) file name for 'closed' state file2.png
file3.png
(A) file name for 'withdrawn open' state
file4.png
(A) file name for 'withdrawncclosed' state file5.png
Depending on the "type" attribute value, 1 or 5 PNG file(s) can be linked to a Bitmap.
For each one, the bitmap size must be  512 bytes.
48124 / Bitmap / The bitmap size in bytes is not valid (file, size, max)
Example:
48124 / Bitmap / The bitmap size in bytes is not valid (file, size, max)-> [file name by default = file1.png, 519,
512]
MF-84 SCE/EN MF/C60

2.6.7.3 REFERENCE FROM BAYMIMIC ELEMENTS TO BITMAP
Graphic
Comp. workspace
Bay mimic (A) bitmap reference
LHMI bitmap 0
LHMI Gen module

(A) multi-bitmap reference
LHMI xPS MultiSt 1
LHMI Transformer
(A) bitmap reference
LHMI TPI MultiSt 2
Graph. Tables
Bitmap table
(A) reference index
Bitmap (1) 0
Bitmap (2) (A) reference index 1
Bitmap (3) (A) reference index 2
The link from an element to its bitmap is defined with the attribute: "bitmap reference". The value of this
attribute must refer to an existing bitmap in the "Bitmap table".
33116 / BayMimic / The reference does not exist in the Bitmap Table
Example:
33116 / BayMimic / The reference does not exist in the Bitmap Table-> [multi-bitmap reference, 10]
Graphic
Comp. workspace Feeder
Bay mimic Circuit breaker
LHMI Gen module Withdrawn SPS
(R) is managed by
LHMI xPS MultiSt xPS
(A) multi-bitmap reference
Graph. Tables
Bitmap table
(A) reference index
Bitmap 0
(A) type 5-uple
(A) file name by default
(A) file name for 'open' state file1.png
(A) file name for 'closed' state file2.png
file3.png
(A) file name for 'withdrawn open' state
file4.png
(A) file name for 'withdrawn closed' state file5.png
The "Bitmap" linked to a "LHMI xPS MultiSt" MultiState must be defined as follows:
 its "type" attribute must be set to "5-uple" value
 its three first file names { "file name by default", "file name for 'open' state", "file name for 'closed'
state" } are mandatory and each one must be unique.
Furthermore, if the MultiState is linked to a SPS or DPS Datapoint of a module containing a "Withdrawn"
SPS Datapoint, through the "is managed by" relation, then the following constraints are added to the
"Bitmap" definition:
 its two file names { "file name for 'withdrawn open' state", "file name for 'withdrawn closed' state" }
are both mandatory and each one must be unique.
33126 / BayMimic / The attribute value of the referenced bitmap is not valid
SCE/EN MF/C60 MF-85

33127 / BayMimic / The attribute value of the referenced bitmap is missing
33128 / BayMimic / Multiple use of the same attribute value in the referenced bitmap
Example:
33126 / BayMimic / The attribute value of the referenced bitmap is not valid-> [Graphic | Graph. Tables |
Bitmap table | Bitmap | type, Single]
33127 / BayMimic / The attribute value of the referenced bitmap is missing-> [Graphic | Graph. Tables |
Bitmap table | Bitmap | file name by default]
33128 / BayMimic / Multiple use of the same attribute value in the referenced bitmap-> [Graphic | Graph.
Tables | Bitmap table | Bitmap | file name by default, file1.png]
33127 / BayMimic / The attribute value of the referenced bitmap is missing-> [Graphic | Graph. Tables |
Bitmap table | Bitmap | file name for 'withdrawn open' state]
33128 / BayMimic / Multiple use of the same attribute value in the referenced bitmap-> [Graphic | Graph.
Tables | Bitmap table | Bitmap | file name for 'withdrawn open' state, file4.png]
2.6.7.4 MEMO BITMAPS

A memo is a specific type of bitmap. They are used by Memo Icons.
Graphic
OI workspace
Window
Mimic (R) has for memo Graphic
Memo icon Memo
(A) bitmap reference
Graph. Tables
Bitmap table
(A) reference index
Bitmap 0
(A) type Memo for OI client
(A) file name for ‘unavailable’ state
(A) file name for 'no note' state file1.png
(A) file name for 'active' state file2.png
file3.png
(A) file name for 'inactive' state
file4.png
 Only a Memo icon can reference a memo bitmap, and only this type.
64126 / Memo icon / The attribute value of the referenced bitmap is not valid
33126 / BayMimic / The attribute value of the referenced bitmap is not valid
Example :
64126 / Memo icon / The attribute value of the referenced bitmap is not valid-> [Graphic | Graph. Tables |
Bitmap table | Bitmap | type, Single]
33126 / BayMimic / The attribute value of the referenced bitmap is not valid-> [Graphic | Graph. Tables |
Bitmap table | Bitmap | type, Memo for OI client]
 In a Memo Bitmap, all referenced bitmaps must be filled

48127 / Bitmap / The attribute value of the referenced bitmap is missing
Example :
48127 / Bitmap / The attribute value of the referenced bitmap is missing-> [file name for 'no note' state]
MF-86 SCE/EN MF/C60

 In a Memo Bitmap, all referenced bitmaps must have same size

48205 / Bitmap / The bitmap sizes are not equal (file 1, file 2)
Example :
48205 / Bitmap / The bitmap sizes are not equal (file 1, file 2) -> [file name for 'no note' state = file1.png
(16x16), file name for 'active' state = file2.png (8x16)]
2.6.7.5 PARTICULAR FORMAT FOR VARTEXT SYMBOL AND VARTEXT

For VarText symbol and VarText, the attribute 'particular format' (used at OI client level) should have the
same value for the database languages.
06325 / Attributevalue / The format should have the same value for all the database languages
2.6.8 ALARM GROUPS
Graphic
(R) uses
Alarm group Datapoint
For an "Alarm Group", at least 1 relation "uses" must be linked.
50130 / AlarmGroup / At least one relation must be linked-> [uses]
Graphic
(R) uses
For an "Alarm Group", data point used must be alarmed
73265 / AlarmGroup / Data point used by alarm group is not alarmed-> [Graphic | ALR.GRP.NOT.OI]
2.6.9 USER PROFILE

A User Profile cannot be called “Administrator”
60181 / UserProfile / User Profile name is not allowed (name) -> [name]3
2.6.10 MEMO
Graphic
Memo
Bay
(R) is memo of Module
(non)IEC physical device
For each "Memo" : 1, and only 1 relation "is memo of" must be linked.
SCE/EN MF/C60 MF-87

72130 / Memo / At least one relation must be linked-> [is memo of]
72113 / Memo / Multiple links-> [is memo of : …]
2.7 DATAPOINTS CHECKS
2.7.1 DATAPOINT PROFILES
2.7.1.1 EVENTS LOGGING
Scs
Ethernet network
Scs OI server
Dpt (R) has for profile (R) has events logged on
Dpt profile OI printer
(A) State treatment / treatment on event
- No archive, no logging
- Archive and logging
- Archive only
If a Datapoint profile is linked to an OI or controller printer through the "has events logged on" relation, then
its "treatment on event" attribute must be set to the " Logging for OI and/or controller" value.
In the case of profiles having several attributes "treatment on …", at least one of them must respect the rule.
23082 / DatapointProfile / The logging definition is not compatible with the relation-> [has events logged
on: OI printer]
Scs
Ethernet network
(R) has for profile Scs (R) has alarm events logged on OI server
Dpt Dpt profile OI printer
(A) State treatment / treatment on event
- No archive, no logging
- Archive and logging
(A) Alarms / defined - Archive only
- Yes
- No
If a datapoint profile is linked to an "OI printer" through the "has alarm events logged on" relation, then:
 it must respect previous rule
 its alarms "defined" attribute must be set to "Yes".
23082 / DatapointProfile / The logging definition is not compatible with the relation-> [has alarm events
logged on: OI printer]
MF-88 SCE/EN MF/C60

23083 / DatapointProfile / The alarm definition is not compatible with the relation-> [has alarm events
logged on: OI printer]
2.7.1.2 SBO MODE
 Profile per Datapoint type:
Substation Scs
(R) has for profile (A) SBO mode Direct Execute
Loc/rem ctrl DPC DPC profile
(R) has for profile (A): SBO mode
Feeder SPC profile Direct Execute
Loc/rem ctrl DPC
(R) has for profile (A) SBO mode
Setpoint profile Direct Execute
Circuit breaker
Selection SPC (R) has for profile
Setpoint
ATCC (R) has for profile (A) SBO mode Direct Execute
SPC (R) has for profile SPC profile
(A) SBO mode
DPC DPC profile Direct Execute
BusBar
ATCC fct needs (R) has for profile (A) SBO mode Direct Execute
SPC SPC profile
DPC DPC profile Direct Execute
Transformer
transformer
ATCC fct needs (R) has for profile (A) SBO mode Direct Execute
SPC SPC profile
DPC (R) has for profile DPC profile (A) SBO mode
Direct Execute
Tap changer (R) has for profile (A) SBO mode
Raise/lower DPC DPC profile SBO Operate Many
Scs
Ethernet network
C264 (R) has for profile (A) SBO mode
Loc/rem ctrl DPC DPC profile Direct Execute
SCE/EN MF/C60 MF-89

Substation (R) has for synchrocheck Scs

Ext manual CS
Feeder 1
Circuit breaker (R) has for profile (A) SBO mode
Sync CB close (SPC) SPC profile Direct Execute
Feeder 2 (R) has for synchrocheck

Ext manual CS

Ext auto CS
Sync CB close (SPC) SPC profile SBO Operate Once

Int manual synchrocheck (R) has for profile
on/off ctrl DPC DPC profile (A) SBO mode
(R) has for profile Direct Execute
on/off ctrl SPC SPC profile
Circuit breaker

Int auto synchrocheck
(R) has for profile
on/off ctrl DPC DPC profile (A) SBO mode
on/off ctrl SPC (R) has for profile Direct Execute
SPC profile
Circuit breaker
Sync CB close (SPC) (R) has for profile (A) SBO mode
SPC profile SBO Operate Once
The possible values of the "SBO mode" attribute of the profile of a Datapoint are:
 SBO Operate Many

 SBO Operate Once
 Direct Execute
 Direct Execute with SBO popup
The following table shows the constraints on the value of the "SBO mode" attribute of the profile of a list of
Datapoints:
Datapoints "SBO mode" attribute value
"SBO Operate Many":
"Raise/lower DPC" Datapoint is allowed only for this Datapoint.
It is forbidden for any other Datapoint.
Allowed values are:
"Loc/rem ctrl DPC" Datapoint of Substation, Bays,
"Direct Execute"
Controllers
Direct Execute with SBO popup
MF-90 SCE/EN MF/C60


SPC / DPC Datapoint of a "Circuit breaker" linked to a "Ext
manual CS" or " Ext manual bay CS " synchrocheck built-in
function
LockModule SPC
Select SPC
Switch SPC
Switch SPC PhA Allowed values are :
Switch SPC PhB "Direct Execute"
Switch SPC PhC Direct Execute with SBO popup
Switch DPC
Switch DPC PhA
Switch DPC PhB
Switch DPC PhC
Sync CB close
SPC / DPC Datapoint of a "Circuit breaker" linked to a "Ext
auto CS" or "Int auto synchrocheck" synchrocheck built-in
function
LockModule SPC
Select SPC
Switch SPC
Switch SPC PhA Allowed value is :
Switch SPC PhB "SBO Operate Once"
Switch SPC PhC
Switch DPC
Switch DPC PhA
Switch DPC PhB
Switch DPC PhC
Sync CB close
SPC / DPC Datapoint of a "Circuit breaker" except "Sync
CB close" linked to a " Int manual synchrocheck "
synchrocheck built-in function
LockModule SPC
Select SPC
Switch SPC
Switch SPC PhA Allowed value is :
Switch SPC PhB "SBO Operate Once"
Switch SPC PhC
Switch DPC
Switch DPC PhA
Switch DPC PhB
Switch DPC PhC
Allowed values are :
"Sync CB close" Datapoint of a "Circuit breaker" linked to a
"Direct Execute"
"Int manual synchrocheck" synchrocheck built-in function
Allowed values are:
SPC and DPC Datapoints of the "ATCC" function "Direct Execute"
SCE/EN MF/C60 MF-91


Allowed values are:
SPC and DPC Datapoints of "ATCC fct needs" of BusBar
"Direct Execute"
and Transformers
Allowed values are:
Setpoint Datapoints which are wired on DO channels of
"Direct Execute"
Controller
Allowed values are:
"Sync CB close" Datapoint of an "Int synchrocheck"
"Direct Execute"
synchrocheck built-in function
73404 / Datapoint / Relations ‘is Transmitted on IEC 61850 SCADA network’ and ‘has for SCADA
address’ are invalid for a datapoint with ‘SBO operate many’
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)
Example:
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)-> [Scs | DPC profile |
SBO mode, SBO Operate Many]
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)-> [Scs | SPC profile |
SBO mode, SBO Operate Once]
 Order type of IED address:
(R) has for profile Scs

(A) SBO mode
SPC SPC profile SBO Operate Once
DPC DPC profile SBO Operate Once
Setpoint Setpoint profile SBO Operate Once
C264
DNP3 master
DNP3_IED
(R) has for IED address IED SPC Mapping (A) order type
SPC addr. on IED - SBO
- Direct Execute
For each SPC, DPC or Setpoint datapoint linked to an IED address through the "has for IED address"
relation: the "order type" attribute value of the IED address must match the "SBO mode" attribute value of the
datapoint profile.
23086 / DatapointProfile / The attribute value does not match the datapoint profile (attribute, profile
attribute)-> [order type = Direct execute, SBO mode = SBO Operate Once]
MF-92 SCE/EN MF/C60

2.7.1.3 FORCING/SUBSTITION/SUPPRESSION ENABLING
(R) has for profile Scs (A) enable Force/Subst/Sup

SPS SPS profile - No
DPS DPS profile - Yes
MPS MPS profile
MV MV profile
Counter Counter profile
The profile of a Datapoint of the System topology must have its "enable Force/Subst/Sup" set the "No" value.
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)
Example:
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)-> [Scs | SPS profile |
enable Force/Subst/Sup, Yes]
2.7.1.4 ALARMING/ARCHIVING/LOGGING/MEANVALUE COMPUTATION FOR NON ADDRESSED

DATAPOINTS
A datapoint which is not addressed cannot be alarmed/archived/logged or computed by OI. Warn user if
profile says other.
The datapoint non addressing possible causes are following:
 IEC 61850-8-1 address is not available for this kind of datapoint
 datapoint is out of scope of IEC 61850-8-1 auto-addressing
 datapoint must be IEC 61850-8-1 addressed
2.7.1.4.1 Alarmed Datapoints
(R) has for profile Scs (A) Alarms / defined

Dpt Dpt profile Yes
23172 / DatapointProfile / The Datapoint is alarmed in OI but has no IEC 61850-8-1 address
2.7.1.4.2 Logged Datapoints
Scs
Ethernet network
(R) has for profile Scs (R) has events logged on OI server
(R) has alarm events logged
Exception: Buffer overflow data points.
23173 / DatapointProfile / The Datapoint is logged in OI but has no IEC 61850-8-1 address
2.7.1.4.3 Mean value computation Datapoint
SCE/EN MF/C60 MF-93

(R) has for profile Scs (A) Mean value / computation

MV MVProfile Yes
(R) has for profile (A) Mean value / computation
Counter CounterProfile Yes
23174 / DatapointProfile / The Datapoint has mean value computed by OI but has no IEC 61850-8-1
address
2.7.1.4.4 Archived Datapoint
(R) has for profile Scs (A) State treatment / treatment on event
Dpt Dpt profile - Archive and logging
- Archive only
23175 / DatapointProfile / The Datapoint is archived in OI but has no IEC 61850-8-1 address
2.7.1.5 DEFAULT FORMAT FOR MV AND COUNTER PROFILES

For MV and counter format, the attribute ‘default format’ (used at OI client level) should have the same value
for the database languages.
06325 / Attributevalue / The format should have the same value for all the database languages
2.7.2 ACQUISITION / CONTROL SOURCE DEFINITION

For a Datapoint, the Acquisition/Control source is defined through relations.
Prior to the checks definitions, the figures hereafter introduce those relations, per Datapoint type, as they are
defined by the SCE Data Design.
Note: If the Acquisition source is defined with the "is managed by" relation, then the Datapoint is considered as a
"System" Datapoint.
Figure 3: Acquisition Control Source definition - Counter
MF-94 SCE/EN MF/C60

Figure 4: Acquisition Control Source definition - SPS
Figure 5: Acquisition Control Source definition - DPS
SCE/EN MF/C60 MF-95

Figure 6: Acquisition Control Source definition - MPS
Figure 7: Acquisition Control Source definition - MV
MF-96 SCE/EN MF/C60

Figure 8: Acquisition Control Source definition - SPC
Figure 9: Acquisition Control Source definition - DPC
(*) up to 2 ‘closed’ wired on and 2 ‘open’ wired on relations can be set (i.e. up to 4 DO channels for the same
DPC).
SCE/EN MF/C60 MF-97

Figure 10: Acquisition Control Source definition - SETPOINT
Figure 11: Acquisition Control Source definition – Load Shedding Preselection
The relation "has for IEC address" must be compatible with the "Ethernet network" protocol (IEC 61850-8-1).
21114 / DatapointServer / The relation is not compatible with the Ethernet network protocol
Example, for an IEC Ethernet Network protocol:
21114 / DatapointServer / The relation is not compatible with the Ethernet network protocol-> [has for IEC
address : ACDxST]
Only 1 Acquisition/Control source can be defined per Datapoint.
21043 / DatapointServer / Multiple control sources (server, relation)
21041 / DatapointServer / Multiple acquisition sources (server, relation)
MF-98 SCE/EN MF/C60

Example:
21043 / DatapointServer / Multiple control sources (server, relation)-> [Scs | Ethernet network | C264, has for
IED address : DPC addr. on IED]
A datapoint must be addressed on the DS Agile C26x which manages it.
i.e.: the automatic addressing generate addresses of a bay datapoint on the DS Agile C26x which manage
the bay, but if the datapoint is produced by an automation which is managed by another DS Agile C26x,
there’s a problem to determine which DS Agile C26x is server.
21045 / DatapointServer / The relation link is not compatible with the datapoint server
Example:
21043 / DatapointServer / The relation link is not compatible with the datapoint server -> [has for IED
address : DPC addr. on IED]
Counter Datapoint:
Only 1 relation "has for IEC address" is allowed. It must be compatible with the "Ethernet network" protocol
(IEC 61850-8-1).

If the relation "secondary input wired on" is linked, then the relation "primary input wired on" must be linked
too.
21062 / DatapointServer / 'primary input' is not wired

It is possible to acquire up to 16 counters (wired) per Extension Rack. The maximum acquisition frequency
will not exceed 20 Hz and the total frequency for the 16 counters will not exceed 160Hz
A maximum of 128 counters can be defined for a full C26x. Up to 8 counters can be wired on the main rack
(no modification).
MV Datapoint:
(IEC 61850-8-1).

If the Acquisition Source is defined on DI channels then the Acquisition Source type is Digital, otherwise it is
Analog.
If the server of the datapoint is an IEC/IEC gateway or a T104Master IED, the source type can be digital.
The value (Analog or Digital) of the "type" attribute of the MV Datapoint must be compatible with the
Acquisition Source type.
21070 / DatapointServer / The acquisition source is incompatible with the datapoint type
Example:
21070 / DatapointServer / The acquisition source is incompatible with the datapoint type-> [type, Analogue]
Several Bit relations are available : "bit<i> wired on", with i  [00..63].
Among these relations, <i> values must be contiguous and start from 00.
If some of these relations are defined, then the relation "wired on" is forbidden, and vice versa (these two
types of relations are incompatible acquisition sources).
21051 / DatapointServer / Wired bits are not contiguous
21041 / DatapointServer / Multiple acquisition sources (server, relation)
SCE/EN MF/C60 MF-99

DPC Datapoint:
Only 1 relation or "has for IEC address" is allowed. It must be compatible with the "Ethernet network"
protocol (IEC 61850-8-1).

If the relation "open wired on" is linked, then the relation "closed wired on" must be linked too, and vice
versa.
21055 / DatapointServer / 'open' is not wired on channel
21054 / DatapointServer / 'closed' is not wired on channel

A "DPC" Datapoint can have up to 2 reIations "has for IED address". In the case of 2 relations, they are
considered as only 1 Control Source definition.
When a DPC is wired on DO channels, all concerned channels must belong to the same board.
<21158> / DatapointServer / 'open' and 'closed' are not wired on the same board
If the relation "open wired on" is double-linked, then the relation "closed wired on" must be double-linked too,
and vice versa.
<21137> / DatapointServer / 'open' is not double-wired on DO channels
<21138> / DatapointServer / 'closed' is not double-wired on DO channels

SPS Datapoint:
(IEC 61850-8-1).

DPS Datapoint:
(IEC 61850-8-1).

If the relation "open wired on" is linked, then the relation "closed wired on" must be linked too, and vice
versa.
21055 / DatapointServer / 'open' is not wired on channel
21054 / DatapointServer / 'closed' is not wired on channel

If the relation "has open state given by" is linked, then the relation "has closed state given by" must be linked
too, and vice versa. The two links must be different.
21057 / DatapointServer / 'open' state is missing
21056 / DatapointServer / 'closed' state is missing
21058 / DatapointServer / 'open' and 'closed' states are linked to the same datapoint
A "DPS" Datapoint can have up to 2 reIations "has for IED address". In the case of 2 relations, they are
considered as only 1 Acquisition Source definition.
MPS Datapoint:
(IEC 61850-8-1).
MF-100 SCE/EN MF/C60

Several State relations are available : "state<i> wired on", with i  [00..15].
21052 / DatapointServer / Wired states are not contiguous

Setpoint Datapoint:
(IEC 61850-8-1).
Several Bit relations are available : "bit<i> wired on", with i  [00..47].
21051 / DatapointServer / Wired bits are not contiguous

If the Acquisition Source is defined on DI channels then the Acquisition Source type is Digital, otherwise it is
Analog.
If the server of the datapoint is an IEC/IEC gateway or a T104Master IED, the source type can be digital.
The value (Analog or Digital) of the "type" attribute of the Setpoint Datapoint must be compatible with the
Acquisition Source type.
21071 / DatapointServer / The acquisition source is incompatible with the datapoint type
Example:
21071 / DatapointServer / The acquisition source is incompatible with the datapoint type-> [type, Analogue]
LSP Datapoint:
For LSP datapoint, the server datapoint must be the same than the FLS server defined at site level by
relation ‘Has for FLS server’.
21045 / DatapointServer / The relation link is not compatible with the datapoint server
2.7.3 CLIENT / SERVER DEFINITION

For a Datapoint, the Server and Clients identification is based on general rules (see section 2.7.3.1 General
definitions ) which can be overwritten by specific rules depending of the Datapoint type (see section 2.7.3.2
Detailed definitions).
These definitions are based on the SCE Data Design.
2.7.3.1 GENERAL DEFINITIONS

For a Datapoint, 1, and only 1, Server device must be defined.
21047 / DatapointServer / The server is missing
21040 / DatapointServer / The server is not unique (server, relation)

Example:
21040 / DatapointServer / The server is not unique (server, relation)-> [Scs | Ethernet network | C264, has
for IED address: DPC addr. on IED]
Special case:
SCE/EN MF/C60 MF-101

Substation (R) is managed by C264

Voltage level C26x IEC Map.
…
Feeder IEC@
Dpt (1)
Dpt (2) (R) has for IEC address
For a Datapoint having no Server explicitly defined, then:

 if the Datapoint is located under a Bay, the device managing the Bay is automatically considered
as the Server ("is managed by" relation link).
 if the Datapoint is located above a Bay, the device managing the associated voltage level,
substation or site (via has for default server relation set at the corresponding level) is automatically
considered as the Server except if it has an IEC address on a specific server.
A device is Client of a Datapoint, if, and only if, it is not Server of this Datapoint.

Datapoint
Client Server

Device A Device B
 A Datapoint must be linked to an address, in the mapping of its Server device, with the "has for IEC
address" relation.
This, if:
 the Datapoint has at least 1 Client device
 the relation is available for the Datapoint type (i.e., it is defined by the Structural Database rules).
 A device, Client of a Datapoint, must be linked to the Server of the Datapoint through the "has for IEC
server" relation.
21046 / DatapointServer / The datapoint is not linked to an address of the server (server)
22048 / DatapointClient / The client-server relation is missing (server, client)

Example:
21046 / DatapointServer / The datapoint is not linked to an address of the server (server)-> [Scs | Ethernet
network | C264]
22048 / DatapointClient / The client-server relation is missing (server, client)-> [Scs | Ethernet network |
C264, Scs | Ethernet network | OI server]
2.7.3.2 DETAILED DEFINITIONS

2.7.3.2.1 Controller
2.7.3.2.1.1 System Datapoints

C264
System infos
SystDpt
Board
System infos
SystDpt
SCADA Networks
C26X SCADA prot
System infos
SystDpt
Legacy Networks
Leg_Network
IED
System infos
SystDpt
The Controller "C264" is Server of each System Datapoint "SystDpt".

2.7.3.2.1.2 Acquisition/Control Sources
C264
DIU200
(R) …wired on
Dpt (1) DI # 0
(R) is computed by TIU200
Dpt (2)
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
Dpt (3)
IED_@
The Controller "C264" is Server of each Datapoint "Dpt(1)", "Dpt(2)", "Dpt(3)".

2.7.3.2.1.3 SCADA address
C264
C26X SCADA prot
Gtw SCADA Map.
Dpt GtwSCADA@
The Controller "C264" is Client of the Datapoint "Dpt".

Moreover, a C26x which supports gateway function must receive information through reports: it cannot have
a relation "goose only" with other C26x which provides it this information.
22193 / DatapointClient / The report usage for client-server relation is missing for gateway or grouping at
2.7.3.2.1.4 FBD automation
C264
(R) runs on
FBD automation PLC
Input (R) uses

DPS | SPS | MPS | MV | DPC | SPC (1)
Output (1) (R) controls
DPC | SPC (2)
Output (2) (R) produces
SPS (3)
The Controller "C264" is Client of the used Datapoints (1).

The Controller "C264" is Server of the controlled Datapoints (2).

The Controller "C264" is Server of the produced Datapoint (3)".
2.7.3.2.1.5 Slow automation
C264
(R) runs on PLC
Slow automation
(R) is client of
UserFunction Dpt (3)
DPC | DPS | SPC | SPS | MPS | MV | Setpoint | Counter (1)
(R) manages
DPC | DPS | SPC | SPS | MPS | MV | Setpoint | Counter (2)
The Controller "C264" is Server of the "Slow automation" Datapoints (3) and of the managed Datapoints
(2).
The Controller "C264" is Client of the used Datapoints (1).
2.7.3.2.1.6 Bay Built-in functions
(R) is managed by C264

Feeder
Autorecloser
(R) is autorecloser of
AR_Dpts
Ext auto CS
Accept forcing
Ext manual CS
Accept forcing
Int synchrocheck
IS_Dpts
Circuit breaker (1)

Circuit breaker (2)
Circuit breaker (3)
Circuit breaker (4)
The Controller "C264" is the manager of the Bay containing the Circuit-breakers, therefore it is the Server of
the Datapoints belonging to each Built-in function: "Autorecloser", "Ext auto CS", "Ext manual CS" and "Int
synchrocheck".
If, for a Built-in function Datapoint, another Server is explicitly defined, then the Controller "C264" is Client of
this Datapoint.
2.7.3.2.1.7 Substation Built-in function
Substation (R) is synchrocheck of

Ext manual CS
Accept forcing
(R) is managed by
(R) is synchrocheck of C264 (1)
Voltage level
(R) is managed by
Feeder C264 (2)
Circuit breaker (1)
Circuit breaker (2)
The Controller "C264(1)" is the manager of the Built-in function "Ext manual CS", therefore it is the Server of
the Datapoints belonging to this Built-in function.

The Controller "C264(2)" is the manager of the Bay containing the Circuit-breakers, therefore it is the Client
of the Datapoints belonging to the Built-in function "Ext manual CS".
2.7.3.2.1.8 DPS-SPS association
(R) has 'closed' state given by Server

DPS SPS (1) C264
(R) has 'open' state given by Server
SPS (2)
The Controller "C264" is the Server of "SPS(1)" and "SPS(2)" Datapoints, therefore it is also the Server of
the "DPS" Datapoint.
For this, both "SPS(1)" and "SPS(2)" Datapoints must have the same Server device.
21040 / DatapointServer / The server is not unique (server, relation)

Examples (from the DPS point of view):
21040 / DatapointServer / The server is not unique (server, relation)-> [Scs | Ethernet network | C264, has
'closed' state given by: SPS(1)]
21040 / DatapointServer / The server is not unique (server, relation)-> [Scs | Ethernet network | C264(2), has
'open' state given by: VoltageLevel SPS(2)]
2.7.3.2.1.9 Group SPS
(R) is managed by
Feeder C264
Group SPS (R) contains the SPS
(R) contains the DPS SPS
DPS
The Controller "C264" is the Server of the "Group SPS" Datapoint, and it is Client of the two Datapoints
"SPS" and "DPS".
Moreover, a C26x which supports grouping function with inputs from other controllers must receive these
inputs through reports: it cannot have a relation "goose only" with other C26x which provides it these
information.
22193 / DatapointClient / The report usage for client-server relation is missing for gateway or grouping at
2.7.3.2.1.10 State Change
(R) controls on state change Server

SPS SPC C264
(R) controls on state change
DPS DPC
A "SPS" (or "DPS") Datapoint can be linked to a "SPC" (or "DPC") Datapoints through relations "controls on
state change".
The Server of the "SPC" (or "DPC") Datapoint is Client of the "SPS" (or "DPS") Datapoint.
Note: An "SPC" (or "DPC") Datapoint can be the link of 1, and only 1 "controls on state change" relation.
15113 / RelationControlsOnStateChange / Multiple links

Examples (from the DPS point of view):
15113 / RelationControlsOnStateChange / Multiple links-> [is controlled on state change of: Substation SPS]
15113 / RelationControlsOnStateChange / Multiple links-> [is controlled on state change of: Substation DPS]

An xPC must be controlled only one time by same xPS
15248 / RelationControlsOnStateChange / The xPC is controlled by an xPS more than one time (mutliple
link with same xPS) (linked xPS)
An xPC (except the ‘block protection’ SPC datapoint) controlled by an xPS cannot be mapped on legacy IED
15044 / RelationControlsOnStateChange / Therelation types are not compatible [is control on state
change of, has for IED address]
A controlled xPC by an xPS must be wired
15305 / RelationControlsOnStateChange / The use of a relation 'controls on state change' for xPC not
wired is not authorized.
2.7.3.2.1.11 Auto/Manu dependency
C264
Server
(R) has for AutoManu dependency SPS

SPC
(R) has for AutoManu dependency
DPC DPS
A "SPC" (or "DPC") Datapoint can be linked to a "SPS" (or "DPS") Datapoint through relation the "has for
AutoManu dependency".
The Server of the "SPC" Datapoint is Client of the "SPS" and "DPS" Datapoints.
2.7.3.2.1.12 Order running
(A) default uniqueness

Substation Substation level
Voltage level (R) is managed by
Feeder C264
Order running SPS
The Controller "C264" is the Server of the "Order running" SPS Datapoint.
If the attribute "default uniqueness" of the "Substation" is set to the "Substation level" value, then all the
controllers are Clients of the "Order running" SPS Datapoint.
2.7.3.2.1.13 ATCC function
Note: hereafter, the term "wired" for a Datapoint means that the Datapoint has one of the following relations: "…wired
on", "has for IED address", or "has for IEC address" to an IEC generic IED.
Main ATCC:
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
The Controller "C264(1)", managing the main "ATCC", is the Server of all the Datapoints of this latter
("ATCC_Dpts").

BusBar ATCC function:
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
(R) is managed by C264 (2)
BusBar (Bay)
ATCC fct needs
ATCC inhibited
ATCC inv module
ATCC inv voltage
ATCC max transfo
ATCC on/off
ATCC on/off ctrl
ATCC targ 1 ctrl
ATCC targ 2 ctrl
ATCC targ 3 ctrl
ATCC targ 4 ctrl
ATCC targ 5 ctrl
ATCC target 1
ATCC target 2
ATCC target 3
ATCC target 4
ATCC target 5
ATCC to target
BusBar voltage
In the case of all the Datapoints of the "ATCC fct needs", except the "BusBar voltage" Datapoint:
 they cannot be wired. As a result, the controller "C264(1)", managing the main "ATCC", is their
Server.
In the case of the "BusBar voltage" Datapoint:
 if it is not wired then the controller "C264(1)", managing the main "ATCC", is its Server.
 if it is wired then the controller "C264(2)", managing the BusBar bay, is its Server and the controller
"C264(1)", managing the main "ATCC", is its Client.

Transformer ATCC function:
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
Voltage level (R) is managed by C264 (2)

Transformer
transformer
ATCC fct needs
ATCC disc eqpt
ATCC homing
ATCC hunting
ATCC inv voltage
ATCC local bay
ATCC low-voltage
ATCC on/off
ATCC overcurrent
ATCC overvoltage
MCB trip
Run away
Second. active P
Second. current
Second. react. Q
Second. voltage
TAP bad TCIP
TAP invalid
TAP long TCIP
In the case of all the Datapoints of the "ATCC fct needs", except the "Run away", "Second. active P",
"Second. current", "Second. react. Q", "Second. voltage" Datapoints:
 they cannot be wired. As a result, the controller "C264(1)", managing the main "ATCC", is their
Server.
In the case of the "Run away" Datapoint:
 it cannot be wired. But, the controller "C264(2)", managing the Transformer bay, is its Server and
the controller "C264(1)", managing the main "ATCC", is its Client.
In the case of the "Second. active P", "Second. current", "Second. react. Q", "Second. voltage" Datapoints:
 they can be wired or not. If wired, the controller "C264(2)", managing the Transformer bay, is their
Server and the controller "C264(1)", managing the main "ATCC", is their Client. If not wired, the
controller "C264(1)" managing the main "ATCC", is their Server.
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
Voltage level (R) is managed by C264 (2)

Transformer
transformer
ATCC fct needs
ATCC on/off
Tap changer (R) has for AutoManu dependency

Raise/lower DPC
MCB position DPS

MCB position SPS

Case of the "Raise/lower DPC" Datapoint:

 if it is present then the "ATCC on/off" Datapoint must be linked to it through the relation "has for
AutoManu dependency".
26031 / ATCC / The link to AutoMany dependency is missing

Case of "MCB position DPS" and "MCB position SPS" Datapoints:
 they are mutually exclusive
 they must be wired
 The controller "C264(2)", managing the Transformer bay, is their Server and the controller
"C264(1)", managing the main "ATCC", is their Client.
26066 / ATCC / The datapoints are not compatible-> [MCB position DPS, MCB position SPS]
21042 / DatapointServer / The acquisition source is missing

IEC servers:
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
(R) is managed by C264 (2) (R) has for IEC server
BusBar (Bay)
ATCC fct needs
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
Voltage level (R) is managed by C264 (2) (R) has for IEC server
Transformer
transformer
ATCC fct needs
The controller "C264(2)", managing the BusBar or Transformer bay, must be linked to the controller
"C264(1)", managing the main "ATCC", through the relation "has for IEC server". Moreover the link must at
least use report mode.
22048 / DatapointClient / The client-server relation is missing (server, client)-> [Scs | Ethernet network |
C264(1), Scs | Ethernet network | C264(2)]
22192 / DatapointClient / The report usage for client-server relation is missing for ATCC at client level
(server, client)

2.7.3.2.1.14 LHMI
Graphic (R) has for workspace C264

Comp. workspace GHU200
(R) represents (R) is managed by
Bay mimic Feeder
LHMI Gen module

LHMI xPS MultiSt (R) visualizes
MV
LHMI Transformer
LHMI TPI MultiSt (R) is managed by
SPS
DPS
(R) is managed by
transformer
Tap changer
Tap pos ind
The Controller "C264" is the Server of the Datapoints: "MV", "SPS or DPS", "Tap pos ind".
2.7.3.2.1.15 Local/Remote
Substation
Server
Local/remote DPS C264
Loc/rem ctrl DPC
If the two Datapoints "Local/remote DPS" and "Loc/rem ctrl DPC" are present, they must have the same
Server device.
24063 / Datapoint_LocalRemote / The Local/Remote datapoints have not the same server (servers)
2.7.3.2.1.16 Taking-Control function
Substation
Server
Local/remote DPS C264 (1)
Loc/rem ctrl DPC
(R) is taken control of C264 (2)

Taking Status (SPS) C26X SCADA prot
Taking Control (SPC)
C264 (3)
(R) is taken control of C26X SCADA prot
Taking Status (SPS)
Taking Control (SPC)
If a Taking-Control function is defined then the "Loc/rem ctrl DPC" must be present.
52089 / TakingControl / The datapoint is missing-> [Loc/rem ctrl DPC]

The Server of the Local/Remote Datapoints ("C264(1)") is the Server of each Datapoints couple "Taking
Status" / "Taking Control".
All the devices ("C264(2), C264(3)") having a SCADA network linked to a Taking-Control function are:
 Clients of each Datapoints couple "Taking Status" / "Taking Control".

 Clients of the Datapoints couple "Local/remote DPS" / "Loc/rem ctrl DPC".

2.7.3.2.2 OI server
OI server
System infos
SystDpt
OI printer
System infos
SystDpt
The "OI server" is Server of each System Datapoint "SystDpt".

2.7.3.2.2.2 Alarmed Datapoints
(R) has for profile Scs (A) Alarms / defined

Dpt Dpt profile Yes
All the "OI server" devices (except backups and datapoints which are not auto-addressed) are Clients of
each Alarmed Datapoint.
2.7.3.2.2.3 Logged Datapoints
Scs
Ethernet network
(R) has for profile Scs (R) has events logged on OI server
(R) has alarm events logged
The "OI server" is Client of the Datapoint "Dpt", except datapoints which are not auto-addressed.
2.7.3.2.2.4 Mean value computation Datapoint
(R) has for profile Scs (A) Mean value / computation

MV MVProfile Yes
(R) has for profile (A) Mean value / computation
Counter CounterProfile Yes
each Datapoint having a Mean Value computation.
2.7.3.2.2.5 Archived Datapoint
(R) has for profile Scs (A) State treatment / treatment on event
Dpt Dpt profile - Archive and logging
- Archive only

each archived Datapoint.
2.7.3.2.2.6 Datapoint used by a graphic animation
(R) is workspace of (R) has for HMI server

OI workspace OI client OI server
Window
Mimic
Var. text (R) is graphically used by
Dpt
(R) manages
DPS MultiState DPS (1)
(R) manages
Discrepancy MS DPS (2)
Circle (shape) (R) is controlled by

Open Ctrl popup DPC
(R) is controlled by
Send order SPC
Open cnt popup (R) is controlled by
Counter
Send value (R) is controlled by SetPoint
The "OI server" is Client of all the Datapoints used by a graphical animation.
2.7.3.2.2.7 Datapoint used by Alarm Group
Graphic
(R) is used by
Alarm group Dpt
All the "OI server" devices (except backups) are Clients of each Datapoint used by an "Alarm group".
2.7.3.2.3 OI client
(R) has for HMI server

OI client OI server
System infos
OI client link
The "OI server" is Server of the System Datapoint "OI client link" of the "OI client".
(R) notify login/logoff on

OI client SPC
The SPC datapoint target that is the target of the relation “notify login/logoff on” must have an IEC 61850-8-1
address for XMLParser generation
69384 / SPCDatapoint / The SPC linked to OI client with relation 'notify login/logoff on' must have an IEC
address

2.7.3.2.4 OI Bay
 A bay OI cannot be the client of more than 500 datapoints.

02256 / OI Bay / An OI bay cannot be clients of more than 500 datapoints (current number of datapoints)
2.7.3.2.5 IEC 61850-8-1 generic IED
IEC gen IED
System infos
SystDpt
The "IEC gen IED" is Server of each System Datapoint "SystDpt".

2.7.3.2.5.2 IEC addressed Datapoint
IEC gen IED

IEC IED Map.
… (R) has for IEC address
IEC@ Dpt
The "IEC gen IED" is Server of each Datapoint linked to an IEC address of its mapping.
2.7.3.2.6 IEC Gateway
IEC gateway
System infos
SystDpt
Usual protocol
System infos
SystDpt
The "IEC gateway" is Server of each System Datapoint "SystDpt".

2.7.3.2.6.2 SCADA addressed Datapoint
IEC gateway
Usual protocol
Gtw SCADA Map.
…
SCADA@ Dpt
The "IEC gateway" is Client of each Datapoint linked to a SCADA address of its mapping.

2.7.3.2.6.3 IEC 61850-8-1 addressed Datapoint
IEC gateway
(R) is transmitted on IEC 61850
61850 protocol Dpt
The "IEC gateway" is Client of each Datapoint transmitted to an IEC 61850-8-1 protocol.
2.7.3.2.7 OI Bay
The maximum number of data points displayed on OI panel must be lower or equal to 500.
02256 / OI Bay / An OI bay cannot be clients of more than 500 datapoints (current number of datapoints)
The Klaxon usage value on a Standard Command Banner of an OI Bay must be set to No, because OI bay
doesn’t manage Klaxon option.
76255 / OI Bay Klaxon usage value on Standard Command Banner of an OI Bay must be set to No (OI
bay),
The alarm group used in a Mimic of an OI bay must have at least one datapoint client of this OI Panel.
Graphic
(R) uses
76264/ OI Bay / Alarm group used by the OI bay must have at least one datapoint client of OI bay->
[Graphic | ALR.GRP.NOT.OI],
2.7.3.2.7.1 IEC 61850-8-1 addressed Datapoint
IEC gateway
(R) is transmitted on IEC 61850
61850 protocol Dpt
The "IEC gateway" is Client of each Datapoint transmitted to an IEC 61850-8-1 protocol.
2.7.4 DATAPOINTS CONSTRAINTS
2.7.4.1 MV DATAPOINTS SENT ON 'SET' OR 'CLOSE' STATE
(R) is sent on set state of

MV SPS
(R) is sent on closed state of
DPS
The two relations "is sent on set state of" and "is sent on closed state of" are mutually exclusive.
28069 / RelationSentOnSetOrClosedState / The relations, sent on 'set' and 'closed' states, are exclusive

2.7.4.2 MV DATAPOINTS DIGITAL ACQUISITION
(A) type Digital …

MV
(A) Digital acquisition / validation delay
50
(A) Digital acquisition / stabilization delay 10
If the attribute "type" of the "MV" Datapoint is set to a "Digital…" value, then the following constraint between
the two attributes must be respected:
"validation delay"  5  "stabilization delay"
51081 / MV_Acquisition / validation delay (x 10 ms) is not greater than 5 * stabilization delay (x 10 ms)
Moreover, avoid using a cyclic transmission for digital measurement:
57256 / MVDatapoint / Avoid cyclic transmission for digital measurement
2.7.4.3 MV DATAPOINTS VALUE FEATURES AND SCALING CHECKS

A “MV” datapoint must be configured for its value features and scaling.
The maximum value must be strictly greater than the minimum value (value features tab):
57235 / MVDatapoint /The max value of a MV must be strictly greater than the min value (min value, max
value)
Examples:
value) -> [0.0, 0.0]
The maximum acquisition value must be strictly greater than the minimum acquisition value (scaling tab):
57236 / MVDatapoint / The max acquisition value of a MV must be strictly greater than the min
acquisition value (min value, max value)
Examples:
57236 / MVDatapoint / The max acquisition value of a MV must be strictly greater than the min acquisition
value (min value, max value) -> [120.0, 50.0]
The threshold configuration must follow some rules (value features tab):
Considering computed value ‘diff’ with following formula
Diff = ( ( maximum value - minimum value ) * hysteresis ) / 100
and considering low threshold as L, LL and LLL and high threshold as H, HH, HHH
3 For configured threshold, each threshold must be greater than previous one (HHH>HH>H>L>LL>LLL)
4 all configured H thresholds must be greater than previous configured one by at least ‘diff’
(HHH>HH+diff and HH>H+diff)
5 all configured L thresholds must be greater than previous configured one by at least ‘diff’ (L>LL+diff
and LL>LLL+diff)
6 first configured H threshold must be greater than last configured L threshold by at least ‘diff’ * 2
(H>L+diff*2 or HH>L+diff*2 etc.)
57237 / MVDatapoint / Threshold must be greater than previous configured one with at least given
difference (threshold, current value, previous value, difference)

Examples:
57237 / MVDatapoint / Threshold must be greater than previous configured one with at least given difference
(threshold, current value, previous value, difference)-> [low-low threshold, 50.0, 30.0, 25.0]
Dead Band value Constraints
For a MV the dead band value can be equal to zero only for MV issued from T103 IED with an ASDU value
equal to 4. (MV of tap position and MV Main Internal Status are excluded from this check).
57266 / MVDatapoint / Only MV issue from IEC 103 IED with ASDU number equals to 4 can have a
deadband value equals to 0.
A MV datapoint is not logged and archived, then the archive trend viewer of the OI will not display anything.
57359 / MVDatapoint / A MV datapoint linked to a Trend Viewer is not archived

MV datapoint mapped on INS/INC
MV datapoint mapped on INS/INC IEC address cant’ have a SCADA address. Can only be transmitted by
Gateway IEC/IEC.
57327 / MVDatapoint / MV mapped on INC/INS cannot be transmit on SCADA network
2.7.4.4 DPC AND DPS DATAPOINTS LINKED TO IED ADDRESSES
C264
DNP3 master
DNP3_IED
IED Mapping
(R) has for IED address (A) contact type
DPC IED_@ (1) - Unused
(R) has for IED address IED_@ (2) - open
- close
(R) has for IED address
DPS IED_@ (3)
(R) has for IED address IED_@ (4)
A "DPC" or "DPS" Datapoint can have 1 or 2 relation(s) "has for IED address".
 In the case of 1 IED address the attribute "contact type" of the IED address must be set to the
"Unused" value.
 In the case of 2 IED addresses the attribute "contact type" of one of the IED addresses must be set to
the "open" value, and the attribute "contact type" of the other IED address must be set to the "close"
value.
18134 / xxxAddressOnIED / The attribute value of the referenced IED address is not valid
Examples:
18134 / xxxAddressOnIED / The attribute value of the referenced IED address is not valid-> [Scs | Ethernet
network | C264 | DNP3 master | DNP3_IED | IED Mapping | IED DPC Mapping | DPC addr. on IED | contact
type, Unused]

2.7.4.5 DPC/SPC DATAPOINTS LINKED TO OUTPUT PLUGS OF FAST/FBD AUTOMATIONS
Fast/FBD automation
(R) controls DPC
Output (1) DPC
(R) controls SPC SPC
Output (2)
A "DPC" or "SPC" Datapoint can be linked to an Output plug of a Fast (or FBD) Automation through the
relation "controls DPC" or "controls SPC".
These relations are not compatible with the following ones:
 relations defining the Control Source, except the "…wired on" relation(s)
 relation "has for IEC address" whatever the link type
 relation "has for SCADA address".
 relation "is controlled on state change of".
 relation "has for AutoManu dependency".
 relation "has for feedback".
 relation "has for local/remote dependency".
39044 / DatapointServer / The relation types are not compatible

Examples:
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: Output, has for IEC
address: GenDCO]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: Output, has for SCADA
address: Gtw DPC addr.]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: Output, has for IED
address: DPC addr. on IED]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: FBD output, is controlled
on state change of: Substation DPS]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: FBD output, has for
AutoManu dependency: Substation DPS]
feedback: Substation DPS]
local/remote dependency: Local/remote DPS]
2.7.4.6 DPC/SPC DATAPOINTS LINKED TO INPUT PLUGS OF FBD AUTOMATIONS
FBD automation
(R) uses DPC
Input (1) DPC
(R) uses SPC SPC
Input (2)
A "DPC" or "SPC" Datapoint can be linked to an Input plug of a FBD Automation through the relation "uses
DPC" or "uses SPC".

These relations are not compatible with the following ones:

 relations defining the Control Source: "…wired on"
 relation defining the Control Source: "has for IED address"
39044 / DatapointServer / The relation types are not compatible

Examples:
39044 / DatapointServer / The relation types are not compatible-> [is used by: FBD input, 'open' wired on:
DO # 1 (NO)]
39044 / DatapointServer / The relation types are not compatible-> [is used by: FBD input, 'closed' wired on:
DO # 0 (NO)]
39044 / DatapointServer / The relation types are not compatible-> [is used by: FBD input, has for IED
address: DPC addr. on IED]
2.7.4.7 RELATION "HAS FOR FEEDBACK"
DPC DPS
SPS
SPC DPS
SPS
SetPoint MV
(R) has for feedback MPS
For each "DPC", "SPC" or "Setpoint" Datapoint, 2 relations "has for feedback" are available, but they are
mutually exclusive.
14023 / RelationHasForFeedback / Multiple links to feedbacks

An xPC cannot have a transient feedback
14278 / RelationHasForFeedback / the xPC cannot have a transient feedback

A MV datapoint that is a feedback of a SetPoint cannot have a profile with FSS Enable set to true.
14294 /RelationHasForFeedback / The MV feedback of a SetPoint cannot have a FSS profile

A Datapoint and its feedback Datapoint must comply with the following rules:
 both must have the same Server device
14026 / RelationHasForFeedback / The datapoint and its feedback have not the same server (servers)
 if the Datapoint is a "Wired" Datapoint, then its feedback Datapoint must be "Wired" too.
14028 / RelationHasForFeedback / The datapoint and its feedback are not both wired
To prevent the check warning 14028 from appearing, the attribute “status check for command” of the relation
“has for feedback” can be set to “No check”
 if the Datapoint is a "System" Datapoint (not wired), then its feedback Datapoint must be "System"(not
wired) too.
14027 / RelationHasForFeedback / The datapoint is system but not its feedback

 if one of them is linked to an "IEC gen IED" through the relation "has for IEC address", this relation
must also be defined for the other one.
This rule does not concern the CB Computed Pos datapoint when it is feedback of a wired SPC/DPC control
of a breaker.
Note:
Here, the term "Wired" means that the datapoint is linked to a digital or analogue channel of a controller, or linked to an
IED address, else it is "System".
In order to prevent the display of check warning 14028 the attribute “status check for command” of the
relation “has for feedback” can be set to “No check”
14029 / RelationHasForFeedback / The datapoint and its feedback are not both linked to an address of a
Generic IED
This rule does not concern the Computed Switch Pos datapoint of a circuit breaker when it is the feedback of
a wired SPC/DPC control of a circuit-breaker.
14224 / RelationHasForFeedback / The xPS is feedback of several xPC

This rule does not concern the Computed Switch Pos datapoint of a circuit-breaker.
Case of the Circuit-breaker "Lock control SPC" Datapoint and Double Point Control (DPC) Datapoint:
Feeder
Circuit breaker
Lock control SPC DPS
(R) has for feedback SPS
One relation "has for feedback" is mandatory.

Case of the Synchrocheck On/Off Command Datapoints:
Substation
Ext manual CS (R) has for feedback
(R) has for feedback on/off ctrl DPC
on/off ctrl SPC
on/off DPS
on/off SPS
Feeder
Ext manual CS (R) has for feedback
on/off ctrl SPC
on/off DPS
on/off SPS
Ext auto CS (R) has for feedback

on/off ctrl SPC
on/off DPS
on/off SPS
Int synchrocheck (R) has for feedback

on/off ctrl SPC
on/off SPS
If the "on/off ctrl DPC" or "on/off ctrl SPC" Datapoint of a Synchrocheck function is linked to a feedback
through the relation "has for feedback", then the feedback must be the "on/off DPS" or "on/off SPS"
Datapoint of the same Synchrocheck function.
14050 / RelationHasForFeedback / The relation link is not valid

Feedback execution timeout:
(A) activation mode

DPC (A) close duration Transient
500
(A) open duration 500

DPS
SPS
(A) execution timeout 200
For a "DPC" Datapoint, if its attribute "activation mode" is set to the "Transient" value, then the following rule
must be respected:
"execution timeout" > max [ "open duration" , "close duration" ]
14024 / RelationHasForFeedback / The feedback execution timeout (x ms) is lower than the max[ open
duration (ms), close duration (ms) ]-> [200, 500, 500]

(A) activation mode

SPC (A) order on duration Transient
500
DPS
SPS
(A) execution timeout 200
For a "SPC" Datapoint, if its attribute "activation mode" is set to the "Transient" value, then the following rule
must be respected:
"execution timeout" > "order on duration"
14025 / RelationHasForFeedback / The feedback execution timeout (ms) is lower than the order on
duration (ms)-> [200, 500]
14166 / RelationHasForFeedback / A computed MV cannot be the feedback of a SetPoint.
2.7.4.8 RELATION "HAS FOR AUTOMANU DEPENDENCY"
DPC DPS
SPS
SPC DPS
SPS
SetPoint DPS
(R) has for AutoManu dependency SPS
For each "DPC", "SPC" or "Setpoint" Datapoint, 2 relations "has for AutoManu dependency" are available,
but they are mutually exclusive.
16032 / RelationHasForAutoManuDependency / Multiple links to AutoMany dependencies

Case of the "Raise/lower DPC" Datapoint:
Refer to section 2.7.3.2.1 Controller
2.7.4.9 RELATION "HAS FOR SCADA ADDRESS DEPENDENCY"

Check for each controller that the number of scada relation links of the MV are not greater than 512.
02368 / TooManyMVScadaRelationPerComputer / Invalid count of Scada Relation Links on MV data

point for this computer (count, max)
Check for each controller that the number of scada relation links of the TS (SPS, DPS, and MPS) are not
greater than 5048.
02369 / TooManyTSScadaRelationPerComputer / Invalid count of Scada Relation Links on TS (SPS,

DPS, and MPS) data points for this computer (count, max)

2.7.4.10 LOCAL/REMOTE DATAPOINTS

Substation Mode Datapoints:
Substation
Local/remote DPS
Loc/rem ctrl DPC
Operating Mode MPS
Note: Hereafter, the term "wired" means that the datapoint must be linked to a digital channel of a controller.
 if "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it is the feedback)
 if "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is mandatory
 if "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it is present, it must be
wired.
24089 / Datapoint_LocalRemote / The datapoint is missing-> [Local/remote DPS]
24089 / Datapoint_LocalRemote / The datapoint is missing-> [Loc/rem ctrl DPC]
24099 / Datapoint_LocalRemote / The datapoint is not wired
 The two datapoints for operating mode of the substation are exclusive (Local/Remote Substation DPS
and Operating mode MPS)
62196 / Operating mode / Datapoints for operating mode are exclusives (Local/Remote Substation DPS
and Operating mode MPS)
 Moreover, for any SCADA protocol attached to a substation via a controller or a gateway, the
substation operating mode is mandatory ( "Local/remote DPS" or "Operating Mode MPS").
62165 / Datapoint_LocalRemote / The datapoint is required for SCADA link -> [Local/remote DPS or
Operating Mode MPS]
Bay Local/Remote Datapoints:
Feeder
Local/remote DPS
Loc/rem ctrl DPC
Note: Hereafter, the term "wired" means that the datapoint must be linked to a digital channel of a controller.
 if "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it is the feedback)
 if "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is not mandatory but, if it is present, it must
not be wired.
 if "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it is present, it must be
wired.
24100 / Datapoint_LocalRemote / The datapoint is wired
24099 / Datapoint_LocalRemote / The datapoint is not wired

Bay Local/Remote DPS and LHMI:
(R) is managed by
Feeder (1) C264 (A) HMI type
Local/remote DPS GHU200 Simple
(R) is managed by
Feeder (2)
Local/remote DPS
If the "GHU200" board of a controller has its attribute "HMI type" set to the "Simple" value, then the
"Local/remote DPS" Datapoints of the bays managed by this controller must be all be "Wired" or all
"System".
24064 / Datapoint_LocalRemote / The acquisition sources of the Local/remote DPS datapoints are
mismatched for the simple LHMI
Local/Remote dependency:
Substation
Local/remote DPS
Operating mode MPS
Voltage level
Feeder
Local/remote DPS (A) Substation mode dependency
Yes
DPC (A) bay mode dependency Yes
(A) Substation mode dependency

Yes
SPC Yes
(A) bay mode dependency
If, under a Substation, a "DPC" or "SPC" Datapoint has one attribute "Substation mode dependency" set to
"Yes", then the Substation "Local/remote DPS" or “operating mode MPS” Datapoint datapoint must be
present.
There are four substation mode dependency attributes:
 Local substation dependency
 Remote substation dependency
 Mode 2 substation dependency
 Mode 3 substation dependency
These attributes define the command authorizations for SCADA or OI. When a command is refused, this
command is dependent of the substation mode.
62089 / Operating mode / The datapoint is missing-> [Local/remote DPS or Operating mode MPS]
If, under a Bay, a "DPC" or "SPC" Datapoint has its attribute "bay mode dependency" set to "Yes", then the
Bay "Local/remote DPS" Datapoint must be present.
2.7.4.11 SBMC DATAPOINTS
Feeder
SBMC SPS
SBMC control SPC

 if "SBMC SPS" is present and not wired, then "SBMC control SPC" must be present
 if "SBMC control SPC" is present, then "SBMC SPS" must be present
25089 / Datapoint_SBMC / The datapoint is missing-> [SBMC control SPC]
25089 / Datapoint_SBMC / The datapoint is missing-> [SBMC SPS]

SBMC dependency:
Feeder
SBMC SPS
(A) SBMC mode dependency Yes
DPC
(A) SBMC mode dependency
SPC Yes
(R) has for profile (A) SBMC dependent Yes
DPS DPS Profile
(R) has for profile (A) SBMC dependent
SPS SPS Profile Yes
If a "DPC" or "SPC" Datapoint has its attribute "SBMC mode dependency" set to "Yes", then the "SBMC
SPS" Datapoint must be present in the electrical bay that it is attached to.
If a "DPS" or "SPS" Datapoint has the attribute "SBMC dependent" of its profile set to "Yes", then the "SBMC
SPS" Datapoint must be present in the electrical bay that it is attached to.
25089 / Datapoint_SBMC / The datapoint is missing-> [SBMC SPS]

“SBMC control SPC” is not supposed to be transmitted to remote control points for security reasons. The
only permitted case is when the SBMC belongs to a bay that is managed by a Gateway, as “SBMC control
SPC” cannot be controlled at a lower level”.
25407 / Datapoint SBMC control SPC /The relation is invalid for ’SBMC control SPC’ managed by other
than gateway
2.7.4.12 DATAPOINTS OF OI SERVER KLAXONS
OI Server (R) warns audibly

Klaxon VoltageLevel
(R) warns audibly UCA2/IECPhysicalDevice
A "Klaxon" refers to a set of Datapoints. This set contains all the Datapoints which are in the sub-tree of each
"VoltageLevel" and "IEC PhysicalDevice" linked to the klaxon through the relation "warns audibly".
In the set of Datapoints, at least 1 Datapoint must fulfil the following conditions:
 it must be linked to a Datapoint Profile which has its attributes "Alarms / defined" and "Alarms /
audible" set to the "Yes" value.
 the "OI Server" must be its Server or its Client

 it must not be the "Main status MV" System Datapoint of a controller.
The sets of Datapoints of each "Klaxon" of an "OI Server" must not share the same Datapoints.
53135 / OIKlaxon / The Klaxon is not associated to audible Datapoints

53136 / OIKlaxon / The Klaxons share the same Datapoints

A given Voltage level or IEC PhysicalDevice cannot be linked more than once to the same klaxon.
<53147> / OIKlaxon / The same voltage level is associated more than once to the same klaxon
<53148> / OIKlaxon / The same IEC PhysicalDevice is associated more than once to the same klaxon
2.7.4.13 SPC MANAGING A KLAXON
OI Server (R) is controlled by

Klaxon SPC
(R) has its klaxon controlled by
Computer SPC
The klaxons can be managed by any SPC. These SPC has to be permanent.
<69214> / SPCDatapoint / When an SPC datapoint manages a klaxon, it must be permanent
2.7.4.14 SPC AND DPC DATAPOINTS

Any SPC/DPC datapoint defined as ‘permanent until feedback’ must be linked to an SPS/DPS via a
feedback relation.
<14146> / RelationHasForFeedback / The feedback must be defined for xPC is permanent until
feedback
2.7.4.15 COUNTER DATAPOINTS

A controller can manage a maximum of 128 counters. For a C26x-Standalone the maximum number of
counter is 128 on main rack and all extensions rack.
02279 / CapacityLimits / Scs | Ethernet network | C264 / Invalid count of counter datapoint for this
computer (max, count)-> [128, 143]
Main rack or standalone can manage up to 8 wired counter, and extension racks up to 16.
02291 / CapacityLimits / Invalid count of wired counter datapoint for this computer or rack (count,
maximum)-> [32, 16]
Main rack cannot have wired counter datapoints when it has extension racks.
02322 / CapacityLimits The main rack of the computer cannot have wired counter datapoints when he
has extension racks.
2.7.4.16 SETPOINT DATAPOINTS

Check for each controller that the number of setpoint datapoints is not greater than 256
02374 / CapacityLimits / Scs | Ethernet network | C264 / Invalid count of setpoint datapoints for this
computer (count, max) -> [258, 256]

2.7.4.17 ENERGY COUNTER DATAPOINTS

Any counter datapoint defined as energy counter (attribute Type is set to Import or Export Energy) must be
linked to an MV via an integration relation and then a counter which integrates an MV must be an energy
counter.
<56161> / CounterDatapoint / The Energy Counter must integrate an MV
<56162> / CounterDatapoint / An Energy Counter which integrate an MV must be Import or Export

When an MV datapoint is integrated by two energy counters, these two counters must not be of same type
(import or export).
<57163> / MVDatapoint / An integrated MV cannot be integrated by two energy counter with same type
(Import or Export)
2.7.4.18 DATAPOINTS LINKED TO SCADA ADRESSES

A datapoint must have only one SCADA address on a same SCADA network.
Exception: the DPS and DPC can have 2 addresses for DNP3 network.
19177 / xxxAddressOnSCADANetwork / The datapoint has two addresses in same SCADA network
[SCADA Network, max address]
A datapoint in substation or voltage level with a SCADA address must have an IEC address
19182 / xxxAddressOnSCADANetwork / A datapoint in substation or voltage level with a SCADA

address must have an IEC address
This case is treated for a user profile type different from C26x-Standalone.
2.7.4.19 XPS GROUPING

Any SPS group cannot contain more than 255 datapoints.
<02179> / CapacityLimits / The maximum number of datapoints in an xPS group is reached (group,
count, maximum)
Any group SPS cannot contain more than 8 cascading levels of group SPS.
<02287> / CapacityLimits / Too many cascading levels of group SPS (>8)

Any group SPS cannot contain loop with cascading grouping SPS.
<02286> / CapacityLimits / Loop with cascading grouping SPS detected
2.7.4.20 DATAPOINT PROFILE ORDER USAGE

For transient SPC with control popup, the “Order off usage” must be set to No
This check is not done for specific case of “on/off ctrl SPC” of an internal manual synchrocheck.
<23183> / DptProfile / A profile of a transient SPC with control popup, must have “Order off usage” set to
No (SPC)
For SPC datapoint with control popup, both of the “order off usage” and the “order on usage” must not be to
No.
<23339> / DptProfile / Datapoint profile link with Open Ctrl Popup cannot set both of OrderUsageOn and
OrderUsageOff to No.

2.7.4.21 TM COMPUTED BY TMU BOARD.

On a TMU board, it cannot be two TM “computed by” with same measure type
<57184> / DptMV / Only one measure type is allowed by TMU board (fixed by relation) (measure type,
TMU board)
On a TMU200 or TMU220 board, in case of Delta topology, the following TM “computed by” measurement
types are not allowed:
 active power phase A, B or C
 reactive power phase A, B or C
 apparent power phase A, B or C
 power factor phase A, B or C
 phase angle phase A, B or C
On a TMU210 board, in case of Delta topology, some TM “computed by” measurement types are not
allowed. More precisely, for the delta topologies "2 Vpp + V0" and "3 Vpp + V0" and "3 Vpp + Vb" (attribute
"type of connection" of TMU210), the following TM “computed by” measurement types are not allowed:
 VAN, RMS value of the voltage phase A
 VAN, RMS value of the voltage phase B
 VAN, RMS value of the voltage phase C
Moreover, for the particular delta topology "3 Vpp + Vb", the TM “computed by”, this measurement type is not
allowed :
 Vr, RMS value of residual voltage
<57190> / DptMV / The measure type is not allowed for delta topology (measure type, TMU210 board)
On a TMU210 board, the following TM “computed by” measurement types are not allowed with relation ‘is
transmitted on IEC 61850-8-1 SCADA network’:
 mod Vo (ADC),
 mod I1 (ADC),
 mod I2 (ADC),
 mod V1 (ADC),
 mod V2 (ADC),
 thermal status
<57221>/ DptMV / This MV data point type cannot be transmitted on IEC 61850 SCADA Network (MV
data point type)
On a TMU210 board if the type of connection equals 3Vpp+Vb, the following TM “computed by” measure
type are not allowed:
 VAN, RMS value of the voltage phase A
 VBN, RMS value of the voltage phase B
 VCN, RMS value of the voltage phase C
 Vr, RMS value of the residual voltage
On TMU200 / TMU220, additional measurement values are available:
 fundamental (H1 harmonic) of phase A current
 fundamental (H1 harmonic) of phase B current

 fundamental (H1 harmonic) of phase C current

 fundamental (H1 harmonic) of phase A voltage
 fundamental (H1 harmonic) of phase B voltage
 fundamental (H1 harmonic) of phase C voltage
2.7.4.22 COMMAND PANEL ASSIGNMENT

For Raise/Lower DPC, if it is SBO Many, the Command Panel Assignment must be set to No
<61185> / DptRaiseLower / A Raise/Lower DPC SBO Many, must have Command Panel Assignment set
to No
2.7.4.23 DATAPOINT MAPPING FUNCTION
Origin Dpt Target Dpt

(R) is mapped on
SPS MappingSPS
MappingDPS
(R) is mapped on
DPS MappingSPS
MappingDPS
(R) is mapped on
MPS MappingSPS
(R) is mapped on
MV MappingSPS
Any configuration database cannot contain more than 100 Origin datapoints.
63198 / MaxOriginDpt / The maximum number of Origin Datapoints is reached (count, maximum)
Any Origin datapoint cannot be mapped on more than 10 Target datapoints.
63199 / MaxTargetDpt / The maximum number of Target Datapoints per Origin datapoint is reached
(count, maximum)
Any Target datapoint must map only one Origin datapoint.
63200 / UnicityOriginDpt / A MappingxPS datapoint (target) must map only one Origin Datapoint.(count,
maximum)
Site
Server
Origin datapoint C264-1
(SPS | DPS | MPS | MV)
Has for Client
(R) IsMappedOn
Mapping datapoint Server C264-2

(SPS | DPS)
If the Server of the Origin Dpt (Example C264-1) is different of the Server of Mapping Dpt (Example C264-2)
then C264-1 has for client C264-2.
22149 / DatapointClient / The client-server relation must be goosed for Automation/Mapping usage at

22150 / DatapointClient / The IEC relevant address must be goosed for Automation/Mapping usage
2.7.4.24 MV DATAPOINTS VALUE FEATURES AND SCALING CHECKS

A “MV” datapoint must be configured for its value features and scaling.
The maximum value must be strictly greater than the minimum value (value features tab):
value)
Examples:
value) -> [0.0, 0.0]
The maximum acquisition value must be strictly greater than the minimum acquisition value (scaling tab):
57236 / MVDatapoint / The max acquisition value of a MV must be strictly greater than the min
acquisition value (min value, max value)
Examples:
57236 / MVDatapoint / The max acquisition value of a MV must be strictly greater than the min acquisition
value (min value, max value) -> [120.0, 50.0]
The threshold configuration must follow some rules (value features tab):
Considering computed value ‘diff’ with following formula
Diff = ( ( maximum value - minimum value ) * hysteresis ) / 100
and considering low threshold as L, LL and LLL and high threshold as H, HH, HHH
1 For configured threshold, each threshold must be greater than previous one (HHH>HH>H>L>LL>LLL)
2 all configured H thresholds must be greater than previous configured one by at least ‘diff’
(HHH>HH+diff and HH>H+diff)
3 all configured L thresholds must be greater than previous configured one by at least ‘diff’ (L>LL+diff
and LL>LLL+diff)
4 first configured H threshold must be greater than last configured L threshold by at least ‘diff’ * 2
(H>L+diff*2 or HH>L+diff*2 etc.)
57237 / MVDatapoint / Threshold must be greater than previous configured one with at least given
difference (threshold, current value, previous value, difference)
Examples:
57237 / MVDatapoint / Threshold must be greater than previous configured one with at least given difference
(threshold, current value, previous value, difference)-> [low-low threshold, 50.0, 30.0, 25.0]
2.7.4.25 MV DATAPOINTS DEADBAND VALUE

A MV datapoints with ‘deadband’ value equal to 0 and transmission on event configured on ‘According to a
‰ of full scale’ or ‘According to a ‰ of current value’ value must be issued from IEC 103 IED and must have
‘ASDU number‘ equal to 4 on its IED address.
57266 / MV Datapoint / Only MV issue from IEC 103 IED with ASDU number equals to 4 can have a
deadband value equals to 0

2.7.4.26 DATA POINT SHORT NAME AND LONG NAME CONSTRAINTS

Datapoint must not has a comma character (“,”) in Short name or Long name attribute in any languages.
Figure 12: Name constraints
73229 / Datapoint / Invalid character find in datapoint attribute (Attribute, Invalid character, OI language)-
> [long name, ',', US English]
2.7.4.27 DEVICE LINK DATAPOINT CONSTRAINT

The device link datapoint of an OI server cannot be use in a mimic.
OI Server Mimic
Device link Symbol
Is controled by
Send FSS order
manages
SPS Multistate
manages
Discrepancy MS
Is graphically used by
Var. Text
73238 / Datapoint / Device link datapoint of OI server cannot be used in a mimic (graphical element)
2.7.4.28 SWITCHGEAR POS. (SPS/DPS) DATAPOINTS AND OPERATING MODE DATAPOINT

CONSTRAINT
For datapoint Switchgear pos.(SPS: SwitchPos_SPS, DPS: SwitchPos) must not has relation ‘is transmitted
on IEC 61850-8-1 SCADA network’ if they are created under a ‘Circuit breaker’ (XCBR) module.

Check Error
73253.
Impossible to
have this relation
under this
datapoints under
a circuit breaker
module.
Figure 13: Switchgear Pos
73253 / Datapoint / Relation 'is Transmitted on IEC 61850 SCADA network' is invalid for this datapoint
The datapoint ‘Operating mode’ must not have the relation ‘is transmitted on IEC61850 SCADA network’ if it
is created under a Gateway.
Check Error
73253.
Impossible to
have this
relation under
this datapoint.
73253 / Datapoint / Relation 'is Transmitted on IEC 61850 SCADA network' is invalid for this datapoint
2.7.4.29 ACTIVATION MODE VALUE CONSTRAINT FOR SWITCHCTRLDPC OF XCBR

If the datapoint ‘Switch Ctrl DPC’ of XCBR is wired on a TMU210 board, its attribute ‘activation mode’ must
not be set to ‘Permanent’
73400 / Datapoint / The attribute value is not valid-> [activation mode, Permanent]


PROBLEM ANALYSIS
SCE/EN PR/C60
DS Agile System Configuration Editor Problem Analysis
Contents
1 INITIAL PROBLEM IDENTIFICATION 3
2 ERROR CODE DURING OPERATION 4
3 MANAGING WINDOWS 5
SCE/EN PR/C60 PR-1

Problem Analysis DS Agile System Configuration Editor
PR-2 SCE/EN PR/C60

1 INITIAL PROBLEM IDENTIFICATION

Consult the table below to find the description that best matches the problem experienced, then consult the
section referenced to perform a more detailed analysis of the problem.
Symptom Refer to section
Position of the windows in the main window application can be now more
MANAGING WINDOWS
moved to the right place
Device Reboots during normal operation ERROR CODE DURING OPERATION
Error during normal operation ERROR CODE DURING OPERATION
SCE/EN PR/C60 PR-3

2 ERROR CODE DURING OPERATION

A checking error code is an error or a warning message displayed in a dedicated table, after a consistency
database check. The checking error codes are completely defined in the chapter SCE/EN MF: error code
description and checked consistency rule definition.
Error while an import action: This error could occur during the import of .xml files. The import errors are
completely defined in chapter Human Machine Interface (SCE/EN HI, tools/import section). Workaround:
check the validity of the imported file with an xml editor like xml spy.
Memory fault: during operation that needs lot of memory, a Java software error/exception [memory fault]
could occur. Workaround: Adjust the Java heap size with your ram size. Follow instructions described in
chapter installation (SCE/EN IN).
Other exception: apply a bug report procedure.
PR-4 SCE/EN PR/C60

3 MANAGING WINDOWS
Managing dockable windows: after many user manipulations, the position and the displaying of dockable
windows could be inconsistent.
Workaround: click on the button that is located in the main toolbar or choose the menu item window/reset
perspective. The default perspective is displayed again.
SCE/EN PR/C60 PR-5

PR-6 SCE/EN PR/C60

RECORD SHEET
SCE/EN RS/C60
DS Agile System Configuration Editor Record Sheet
Contents
1 WORKSTATION CHARACTERISTICS 3
1.1 PC Characteristics 3
1.2 OS Characteristics 3
2 INSTALLATION 4
2.1 Software Delivery 4
2.2 DS Agile SCE Installation 4
2.2.1 General Installation 4
2.2.2 Optional components 4
2.3 Installation checking 5
2.3.1 General Checking 5
2.3.2 Settings Checking 5
SCE/EN RS/C60 RS-1

Record Sheet DS Agile System Configuration Editor
RS-2 SCE/EN RS/C60

1 WORKSTATION CHARACTERISTICS
1.1 PC CHARACTERISTICS
PC Name
Clock Frequency (GHz)
RAM Size (MB)
HD Size (MB)
1.2 OS CHARACTERISTICS
WINDOWS XP SERVICE PACK
WINDOWS 7 ULTIMATE 64 BITS SERVICE PACK
SCE/EN RS/C60 RS-3

2 INSTALLATION
2.1 SOFTWARE DELIVERY

DS Agile SYSTEM VERSION
DS Agile SYSTEM Release Note Checked:
 Yes
 No
DS Agile SCE VERSION
DS Agile SCE Release Note Checked:
 Yes
 No
2.2 DS AGILE SCE INSTALLATION
2.2.1 GENERAL INSTALLATION

DS Agile SCE Installed using DS Agile SCE IN Manual:
 Yes
 No
DS Agile SCE Installation directory:
 Standard (C:\Program Files\Alstom\DCS\SCE)
 Other (precise):
DS Agile SCE Installation Choice:
 Complete (Software & Documentation)
 Documentation
 Software
DS Agile SCE Installation problem:
 Yes
 No
2.2.2 OPTIONAL COMPONENTS

Crystal Report
 Yes
 No
DS Agile OI XML Parser
 Yes
 No
DS Agile OI XML Parser VERSION
Automation ISaGRAF data access Installation (if MS access 97 is not installed)
 Yes
 No
RS-4 SCE/EN RS/C60

ISaGRAF PRO Installation

 Yes
 No
ISaGRAF PRO VERSION
2.3 INSTALLATION CHECKING
2.3.1 GENERAL CHECKING

Check that the following files or directories are in the correct path (cf. DS Agile SCE IN Manual):
 SCE version directory
 j2re (java directory)
 msxml.dll file dates in the Windows/system32 or C:\Windows\sysWOW64 folder: they must be
identical to those provided in the Tools\msxml_dlls.zip file.
 ISaGRAF (optional)
Check that the following items are in the Start Menu:
 DS Agile SCE
 ISaGRAF PRO (optional)
2.3.2 SETTINGS CHECKING

SCE.lax setting values: open SCE.lax file and report the following values:
lax.nl.java.option.java.heap.size.max
DS Agile SCE launched:
 Yes
 No
Check in DS Agile SCE setting manager (Menu Tools, Options) the following values:
JDK’s version
DS Agile SCE version
SCE/EN RS/C60 RS-5

RS-6 SCE/EN RS/C60

TECHNICAL DATA
SCE/EN TD/C60
DS Agile System Configuration Editor Technical Data
Contents
1 REQUIREMENTS 3
2 CAPABILITIES 4
SCE/EN TD/C60 TD-1

Technical Data DS Agile System Configuration Editor
TD-2 SCE/EN TD/C60

DS Agile System Configuration Editor Technical Data
1 REQUIREMENTS
For the minimum hardware requirements to operate the DS Agile SCE application, please refer to the table
that follows:
Type of PC Standard desktop with CPU Xeon 2.8 GHz
RAM 2048 MB or more
Hard Disk 80 GB – FT32 format or more
CD-ROM Reader
Operating System Windows 2003, Windows XP Professional SP3 or Windows 7 Ultimate 64 bits
Applications XML parser
Graphics VGA screen 256 colours minimum, resolution 1024*768 or higher
Optional Ethernet port, USB port, CD-Writer for database exchange
SCE/EN TD/C60 TD-3

Technical Data DS Agile System Configuration Editor
2 CAPABILITIES
The capabilities of the DS Agile SCE application allow you to define the maximum configuration of a DS
Agile project. You can find a description of the capacity limits of the different devices of a DS Agile project in
the DS Agile SCE/EN MF chapter. Please refer to the topic, Capacity limits.
TD-4 SCE/EN TD/C60

GLOSSARY
SCE/EN LX/C60
DS Agile System Configuration Editor Glossary
Term/Acronym Description
100Base Fx Fiber optic ports are full/half duplex at 100 Mbps only.
The copper ports are full/half duplex and auto-sense the transmission speed. They will auto-
10Base Tx and negotiate with the connected device to determinate the optimal speed. When the connected
100Base TX device is only capable of transmitting at 10 Mbps, the Ethernet switch unit or board follows
10 Mbps.
BRCB Buffered Report Control Block
LPHD Logical node PHysical Device
URCB Unbuffered Report Control Block
A/D Analog/Digital
A/R Auto-Reclose(r)
Abstract Communication Service Interface
ACSI Mapping from standard IEC 61850 abstract specification of a communication service to a
concrete communication infrastructure based on the CORBA standard.
ADC Analog to Digital Converter
AE qualifier Application Entity qualifier (Used internally by IEC 61850 to identify a server Application)
Analogue Input (Measurement Value including state attribute)
AI Usually voltage or current DC signals delivered by transducers, and representing an external
value (refer to CT/VT for AC).
AIS Air Insulated Substation
Analogue Input Unit
AIU
C26x controller's board for DC analogue inputs
Alarm An alarm is any event set as alarmed during the configuration process
Analogue Merging Unit
Interface device which acquires analogue signals from conventional CTs and VTs and
AMU performs digital signal processing to generate and distribute output sampled value streams
according to IEC 61850-9-2LE standardised definitions for communication with substation IEDs
and controllers
Analogue Output
AO
Value corresponding to a desired output current applied to a DAC
AOU Analogue Output Unit (C26x controller's board for analogue outputs)
ApccI Accumulator Input
API Application Programming Interfaces
ASCII American Standard Code for Information Interchange
Application Specific Data Unit
ASDU
Name given in the OSI protocol for applicative data (T101, T103, T104)
Automatic Tap Change Control
ATCC
Automation of secondary voltage regulation, more specific than AVR
Automatic Voltage Regulator
AVR Automation used to regulate secondary voltage using an automatic tap change control (see
ATCC). A set of features can be added, see C26x/EN FT
Set of LV, MV or HV apparatus (switching devices and transformers) and IEDs (Protection,
Bay
Measurement…) usually built around a Circuit Breaker and controlled by a Bay Controller Unit.
Binary Coded Decimal
C26x-supported coding on a set of Digital Inputs that determines a Digital Measurement, then
BCD
a Measurement value (with a specific invalid code when coding is not valid). Each decimal digit
is coded over 4 binary digits.
Bay Control Point
BCP Name given to the device or part used to control a bay. It can be a Mosaic Panel, a C26x unit's
LCD,… Usually associated with Remote/Local control.
SCE/EN LX/C60 LX-1

Glossary DS Agile System Configuration Editor
Bay Control Unit
BCU
Name given to the C26x that manages a bay. Usually as opposed to “Standalone” (RTU).
BGD BackGrounD scan (low priority scan of status in T101/T104)
Binary Input (or Information)
BI Name given in the C26x controller to information that has already been filtered, before it
becomes an SPS, DPS… with time tag and quality attributes.
Basic Interface Unit
BIU
C26x controller's board for auxiliary power supply, watchdog relay, redundancy I/O.
BNC Bayonet Neill–Concelman: RF connector for coaxial cables.
Category 5 unshielded twisted pair (UTP) cabling. An Ethernet network operating at 10 Mbps
(10BASE-T) will often tolerate low quality cables, but at 100 Mbps (10BASE-Tx) the cable must
be rated as Category 5, or Cat 5 or Cat V, by the Electronic Industry Association (EIA). This
Cat. 5
rating will be printed on the cable jacket. Cat. 5 cable contains eight conductors, arranged in
four twisted pairs, and is terminated with an RJ45 type connector. In addition, there are
restrictions on the maximum cable length for both 10 and 100 Mbps networks.
Circuit Breaker
CB Specific dipole switch with capability to make line current and break fault current. Some have
isolation capability (nominal earth on each side)
Compact Bay Controller, small capacity Bay Controller Unit for Medium Voltage applications,
CBC
typically C26x in 40TE case
Complemented Contact
CC A double counter is acquired from two contacts. One is called the true contact (TC), the other is
the complemented contact (CC). Normally these contacts have complementary states.
Circuit breaker Control Unit
CCU
C26x controller's board dedicated to switch control with 8 DIs, and 4 DOs
Conceptual Data Modeling
Modeling of system/device data using a hierarchy of structured data (called object of class)
CDM
with their attributes, method or properties and the relations between them. It maps common
data to devices or components of devices, with a guaranty of interoperability.
Defined in IEC 61850 as the description of a set of objects that share the same attributes,
Class
services, relationships, and semantics.
Defined in IEC 61850 as an entity that requests a service from a server and that receives
Client
unsolicited messages from a server.
Cluster Pair of two redundant controllers or computers
CMT Controller Management Tool
CO Command, logic information Output (Functional Component) / Contact Open
COMTRADE COMmon format for TRAnsient Data Exchange (IEC 60255-24 international standard)
Central Processing Unit
CPU
C26x controller's main board, based on a PowerPC micro-processor.
Cyclic Redundancy Check
CRC Coding result send with packet of transmitted data to guarantee their integrity. Usually the
result of a division of data transmitted using a polynomial code.
Character Separate Values
CSV
ASCII values separated by a predefined character or string as in Excel or Comtrade ASCII.
Current Transformer
Basically the device connected to the electrical process used to extract a current
CT
measurement. By extension part of a device (C26x) that receives AC values and converts it to
a numerical measurement value.
CT/VT Current and Voltage transformers
conventional By extension, it is the C26x controller's TMU board.
DAC Data Acquisition component of the GPT
Digital to Analogue Converter
DAC
Used to generate analogue signals (usually DC) from a digital value.
LX-2 SCE/EN LX/C60

Double Attached Node implementing PRP (defined by IEC 62439-3)
DANP
Such an IED sends the messages over two separate networks.
DataBase
Tool or set of data that define all the configuration of a system or specific device such as a
DB
substation computer or bay controller. Contrary to setting parameters, a DB has a structure
that cannot be modified on-line. DBs are always versioned.
DB-9 A 9-pin family of plugs and sockets widely used in communications and computer devices.
Don’t Believe It
DBI Term used to describe the undefined state of a double point when its inputs are not
complementary. DBI00 is state motion or jammed. DBI11 is undefined.
DBID Database Identity Brick
External master clock and protocol transmission
DCF77 LF transmitter located at Mainflingen, Germany, about 25 km south-east of Frankfurt ,
broadcasting legal time on a 77.5 kHz standard frequency.
DCO Double Control Output
Device Control Point
DCP
Located at device level (electric device or IED). It should have its own Remote/Local switch.
Digital Control System
DCS Generic name of system based on numeric communication and devices, to be opposed to
traditional electrically wired control.
Double CounTer
DCT Counter based on 2 DIs with complementary states (counting switchgear operations for
example).
DE Direct Execute
DELTA MV Phase–phase analogue values received from the "delta" winding connections of a transformer.
DFT Discrete Fourier Transform
Digital Input
DI Binary information related to the presence or to the absence of an external signal, delivered by
a voltage source.
DC Input Unit
DIU
C26x controller's board hosting digital inputs
Dynamic Link Library. Available with Windows XP. Feature allowing executable code modules
to be loaded on demand and linked at run time. This enables the library-code fields to be
DLL
updated automatically, transparent to applications, and unloaded when they are no longer
needed.
Digital Measurement
DM
Measurement value acquired from DIs with a specific encoding: BCD, Gray, 1 among N…
Distributed Network Protocol
DNP3.0 DNP3 is a set of communication protocols used between components in process automation
systems.
Digital Output
DO Used to apply a voltage to an external device via a relay, in order to execute single or dual,
transient or permanent commands.
Degree Of Freedom
DOF Used for a template attribute, that can be modified or not when used. An attri-bute has a
degree of freedom if a user can modify the values of its instances.
Digital Output Unit
DOU
C26x controller's board hosting digital outputs.
DP Data Point, low-level object in the structure, wired or not, with or without links
Double (Point) Control
DPC Two digit and/or relays outputs with complementary states (OPEN, CLOSE) used for device
control.
DPC Double Point Control, control sent over 2 digital outputs.
SCE/EN LX/C60 LX-3

Double Point Status, information derived from 2 digital inputs
DPS
Usually used for Position indication of switching devices (OPEN, CLOSE).
DPU Digital Process Unit: BCU board used to interface with switchgear control units (SCU).
Extended Communication Unit
ECU External module connected to the CPU board. This module converts non-insulated RS232
signals into optical or insulated RS485/RS422 signals.
Transmission protocol dedicated to time synchronisation and standardised by EDF.
EH90
Specification document: D.652/90-26c, March 1991.
"Ensemble de Protection Ampèremétrique de Terre Résistante" (French legacy very resistive
EPATR
earth current module).
EQL Equation Logic, especially for interlocking.
An event is a time-stamped change of state/value acquired or transmitted by a digital control
Event
system.
Fast Ethernet An Ethernet system that is designed to operate at 100 Mbps.
Factory Acceptance Test
FAT
Validation procedures executed with the customer at the factory.(i.e. SAT)
Functional Block Diagram
FBD One of the IEC 61131-3 programming languages (language used to define configurable
automations).
FIFO First In First Out
FLS Fast Load Shedding
FO Fibre Optic
FP Front Panel
FSS Force Suppress Substitute
FTP Foil Twisted Pair
Level 6 session of OSI, the gateway can be any device transferring data between different
networks and/or protocols. The RTU function of the C26x behaves like a gateway at the
Gateway
SCADA or RCP level. The DS Agile Gateway is a separate PC-based application dedicated to
this function.
Graphic Human interface Unit
GHU
C26x controller's front panel interface (LCD, buttons, front RS port)
GIS Gas Insulated Substation
GIS-Watch Monitoring and control device for GIS substations
GLOBE GLOBE hard-coded brick used in DS Agile IEC 61850 mapping for C26x mode management
GMT Greenwich Mean Time, former absolute time reference. Replaced by UTC.
GOOSE Generic Object Oriented Substation Event
Global Positioning System
GPS Based on triangulation from satellite signal, that transmit also absolute GMT time used to
synchronise a master clock.
GPT Generic Protocol Translator software, supplied by ASE
Group Logical combination of BIs (i.e. SP, DP, SI or other groups)
GSSE Generic Substation Status Event
A system that allows packets to transmitted and received, but not at the same time. Contrasts
Half-duplex
with full-duplex.
Facility for an operator to set manually the position of a device (acquired by other means) from
Hand Dressing the HMI at SCP level; e.g. from OPEN to CLOSE (without any impact on the “physical” position
of the electrical switching device).
HBU High Break Unit: BCU board used in applications requiring high rupture capacity.
HMGA Horizontal Measurement Graphical Area
LX-4 SCE/EN LX/C60

Human Machine Interface
HMI Can be DS Agile OI (Operator Interface) or C26x LCD (Local Control Display) or LEDs,
Mosaic...
HSR High Speed auto-Reclose, i.e. first shot of an AR cycle
Hyper Text Mark-up Language
HTML
Used as standard for formatting web display.
HV High Voltage (for example 30 kV to 150 kV)
I/O Input/Output
ICD IED Capability Description
IEC International Electro-technical Commission
Intelligent Electronic Device
IED Global term covering a whole range of microprocessor-based products capable of data
collection and information processing.
Inter-Range Instrumentation Group standard format B. This is an international standard for
IRIG-B
time-synchronisation based on an analogue signal.
Invalid state of a Double Point:
JAMMED Occurs when the 2 associated digital inputs are still in state 0 after a user- settable time-delay,
i.e. when the transient state “motion” is considered as ended.
Kbus (Kbus Courier) Term used to designate the Courier protocol on a K-Bus network (similar to RS422)
L/R Local / Remote
When set to local for a given control point it means that the commands can be issued from that
L/R Control Mode
point, else in remote control are issued for upper devices.
Legacy Bus
Generic name of Legacy or field networks and protocols used to communicate between C26x
L-BUS
(Legacy Gateway function) and IED on field bus. Networks are based on (RS232,) 422, 485.
Protocols are IEC 60850-5-103 (T103 or VDEW), Modbus.
LC Fibre optic snap-on connector, IEC 61754-20-compliant, for high density connection.
LCD Liquid Crystal Display on the C26x front panel HMI
Ladder Diagram, one of the IEC 1131-3 programming languages (language used to define
LD
configurable automations).
Logical Device, defined in IEC 61850 as: An entity that represents a set of typical substation
LD
functions.
LHMI Front panel Local HMI
Logical Node
LN
Defined in IEC 61850 as an entity that represents a typical substation function.
LOC Local Operator Console, dedicated to maintenance operations
LSB Least Significant Bit
LSP Load Shedding Pre-selection
LV Low Voltage
The Media Access Control address is a unique 48-bit hardware address assigned to every
MAC address
network interface card. Usually written in the form 01:23:45:67:89:ab
MC Modular Controller
Miniature Circuit Breaker. In the SCE configuration, its position is associated with the tap
MCB
changer.
Management Data Input/Output
MDIO
A standard driven, dedicated-bus approach that is specified in IEEE802.3
MEAS Values acquired through digital or analogue inputs (with value, state, and time stamp)
Metering Values computed depending on the values of digital or analogue inputs during variable periods
(non-tariff) of time (time integration).
SCE/EN LX/C60 LX-5

Values computed depending on the values of digital or analogue inputs during variable periods
Metering
and dedicated to energy tariff metering. These values are provided by dedicated “tariff
(tariff)
computers” which are external to the control system.
MIDOS connector Alstom 28-pin terminal block used for CT/VT acquisition
MMS Manufacturing Message Specification (ISO 9506)
Communication protocol used on secondary networks with IEDs or with a SCADA RCP. There
Modbus
are 2 versions: standard MODICON and Alstom.
Term used in DS Agile SCE to encompass all electrical HV devices: switchgear, transformers,
Module
motors, generators, capacitors, …
Transient state of a Double Point
Occurs when the two associated digital inputs are momentarily in state 0 (e.g. position
MOTION
indication when a switching device is operating). The acceptable duration of the transient state
is user-settable.
MPC Protection Module for Controller
Merging Unit
Interface device which takes signals from the instrument transformer sensors and performs
MU digital signal processing to generate and distribute output sampled value streams according to
IEC 61850-9-2LE standardised definitions for communication with substation IEDs and
controllers.
MV Medium Voltage or Measurement Value
MVAR Mega Volt Ampere Reactive
NBB Numerical BusBar protection
NC Normally Closed (for a relay/contact)
Non-Conventional Instrument Transformers
New generation of captor-based, for example using light diffraction under an electric field,
NCIT
CT/VTs, without spires, that provide direct voltage and current numerical values to the
communicating IEDs.
NO Normally Open (for a relay/contact)
One Box Solution
Controller that provides protection & control functions with local HMI. Mainly intended for use in
OBS substations up to distribution voltage levels, although it may also be used as backup protection
in transmission substation. Likewise the OBS may be applied to the MV part of a HV substation
that is being controlled by the same substation control system.
OI Operator Interface
Object Linking and Embedding
OLE
OLE is a Microsoft specification and defines standards for interfacing objects.
OMM Operating Mode Management
OLE for Process Control
OPC 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.
Sum of time periods under which a primary device is running whilst carrying energy, e.g. circuit
Operation hours
breaker is in Close state and the current is not null.
Open System Interconnection
OSI ISO standard that splits and defines communication in 7 layers : physical, link, network,
transport, session, presentation, application.
OWS Operator WorkStation (DS Agile OI)
OSI Physical Layer: The physical layer provides for transmission of cells over a physical
PHY
medium.
Programmable Logic Control: Includes PSL and ISaGRAF
PLC Within the PLC-programs are defined the configurable control sequences or automations used
by DS Agile IEDs and Gateway (ISaGRAF only).
PPC Power PC, chip on the CPU270 board (MPC8270VR)
LX-6 SCE/EN LX/C60

PRP Parallel Redundancy Protocol (defined in IEC 62439-3:2010)
PSL Programmable Scheme Logic
PSTN Public Switched Telephone Network
Remote Control Centre: computer or system that is not part of the substation control system.
RCC
RCC communicates with and supervises the DS Agile system using a protocol.
Remote Control Point
Name given to the device or part used to remotely control several bays or substations. Usually
RCP
associated with Remote/Local substation control. It is a SCADA interface managed through the
Telecontrol BUS. Several RCPs can be managed with different protocols.
RedBox PRP Redundancy Box
When set for a control point it means that the commands are issued from an upper level and
Remote Control Mode
are not allowed from that point.
Remote HMI is a client of the substation HMI server. The client may provide all or part of
Remote HMI
functions handled by the substation HMI.
Read Inhibit, output that indicates the availability of an analogue output (e.g. during DAC
RI
processing time).
Registered Jack-45
RJ-45
An 8-pin female connector for 10/100 Base-T Ethernet networks.
Root Mean Square
RMS
Average value of a sinusoid that is used for calculations.
Short for remote monitoring, a network management protocol that allows network information
to be gathered at a single workstation. Whereas SNMP gathers network data from a single
type of Management Information Base (MIB), RMON 1 defines nine additional MIBs that
RMON provide a much richer set of data about network usage. For RMON to work, network devices,
such as hubs and switches, must be designed to support it. The newest version of RMON,
RMON 2, provides data about traffic at the network layer in addition to the physical layer. This
allows administrators to analyze traffic by protocol.
Recommended Standard 232
RS-232
A standard for serial transmission between computers and peripheral devices.
Standard for serial interfaces that extends distances and speeds beyond RS-232 capability.
RS-422
Intended for use in multipoint lines.
Standard for serial multipoint communication lines. RS485 allows more nodes per line than
RS-485
RS422
Régime Spécial d’Exploitation
RSE
French grid function to indicate that there are works in progress on an HV feeder.
RSVC Relocatable Static Var Compensator.
RTC Real Time Clock
Remote Terminal Unit
RTU Standalone controller that acquires data and transmits it to RCP or SCADA. Typically it is the
C26x-Standalone. The RTU is attached to the T-BUS.
Single Attached Node (defined by IEC 62439-3). Unlike DANP, such an IED requires a
SAN
REDundancy Box to send the messages over two separate networks.
SAN Singly Attached Node (PRP unaware)
Site Acceptance Test
SAT
Validation procedures performed on site with the customer.
Site-Based Maintenance Control mode
A bay in SBMC mode does not take into account the commands issued from the RCP;
SBMC
moreover, some of its digital points and measurements (defined during the configuration
process) are no longer sent to the RCP (they are “automatically” suppressed).
SCE/EN LX/C60 LX-7

Select Before Operate
Control made of two steps, selection and execution. The selection step returns a feedback. It
SBO can be used to select a circuit before execution of the command. Commands are included in a
protocol frame between the Operator Interface and the BCU and sent over wired outputs to the
switching device (e.g. DO select with DI Select, then DO execute).
S-BUS Station Bus, federal network between DS Agile devices.
SCADA Supervisory Control And Data Acquisition, equivalent to RCC.
scd Description file extension (in SCE)
SCE System Configuration Editor
SCL System Configuration Language (IEC 61850-6) for substation automation
Substation Control Point
Name given to the device or part used to control locally several bays or substations. Usually
SCP
associated with Remote/Local substation control. It normally refers to DS Agile’s Operator
Interface.
SCS Substation Control System
SCSM Specific Communication Service Mapping
SCT Single Counter
SCU Switchgear Control Unit used in Process Bus applications.
Sequence of Event Recorder: combines SOE with accurate Time synchronisation and
SER
Maintenance facilities over Ethernet communications.
Defined in IEC 61850 as an entity that provides services to clients or issues unsolicited
Server
messages.
Analogue setpoints are analogue outputs delivered as current loops. Used to send instruction
Setpoints (analogue)
values to the process or auxiliary device.
Digital values sent on multiple parallel wired outputs. Each wired output represent one bit of the
Setpoints (digital) value. Digital setpoints are used to send instruction values to the electrical process or to
auxiliary devices.
Sequential Function Chart
SFC
IEC 61131-3 programming language (used to define configurable automation)
Small Form-factor Pluggable transceiver
SFP Hot-pluggable transceiver used for both telecommunication and data communications
applications.
Single Input or System Indication:
Binary information that does not come from an external interface, but is related to an internal
SI
state of the controller (time status, hardware faults…) or the result of an inner function (AR, …)
PSL or ISaGRAF.
SIG Status Input Group (idem MPS)
SINAD Signal-plus-Noise-plus-Distorsion to Noise-plus-Distorsion ratio, in dB
SIT Status Input Double Bit (idem DPS)
Simple Network Management Protocol: protocol governing network management and
SNMP
monitoring of network devices and their functions.
SNTP Simple Network Time Protocol
SOE Sequence Of Events, i.e. the event list
SP Single Point
SPS Single Point Status
SPC Single Point Control
SPI Step Point Indication (same as TPI)
Switch Redundancy Protocol, PRP Ethernet switch board fitted in H38x Ethernet switch and in
SRP
C26x BCU.
Structured Text
ST
An IEC 61131-3 programming language to define configurable automation.
LX-8 SCE/EN LX/C60

STP Shielded Twisted Pair.
Substation controller Bay controller used at substation level
Suppression A binary information belonging to a bay in SBMC mode is automatically suppressed for the
(Automatic) remote controller. However changes of state are indicated locally, at SCP level.
A binary information can be suppressed by a command issued by an operator. No subsequent
Suppression (Manual) change of state on a “suppressed information” can trigger any action such as display, alarm or
transmission.
Sample Value Unit
SVU IEC 61850-9-2LE-compliant C26x controller's board interfacing with analogue merging units
through the substation's Process Bus.
SWitch for Dual homing
SWD
C26x controller's board acting as an Ethernet switch on a redundant Ethernet star network.
SWitch Redundant
SWR
C26x controller's board acting as an Ethernet switch on a redundant Ethernet ring network.
SWitch for Teaming
SWT C26x controller's board acting as an Ethernet switch with hot standby redundancy between an
Ethernet network and end nodes
SWitch Unit
SWU
C26x controller's board acting as an Ethernet switch on a single Ethernet network.
T10x Term used to designate IEC 60870-5-10x protocols (x= 1, 3, 4)
TBC / TBD To Be Completed / Defined
Telecontrol Bus, generic name of networks and protocols used for communications between
DS Agile Gateway or the C26x Telecontrol Interface function and the RCP. Networks use
T-BUS
RS232, RS485, or Ethernet (T104). Protocols are IEC 60850-5-101 (T101) or MODICON
Modbus.
True Contact
TC A double counter is acquired on two contacts. One is called the true contact (TC), the other is
the complemented contact (CC). Normally these contacts have complementary states.
TCIP Tap Changer In Progress
Total Demand Distortion, similar to the THD but applied to currents and with a rated current (In)
TDD
used as reference.
TG Telecontrol Gateway
THD Total Harmonic Distortion, sum of all voltage harmonics.
TM Tele-Measurement (remote measurement)
TMU Transducerless Measurement Unit
Interlocking algorithm, based on the evaluation of topological information on the switchgear
Topological interlocking arrangement in the HV network, the type of switchgear and its location, as well as defined rules
for controlling this type of switchgear (e.g. power supply continuity).
Tap Position Indication (for transformers).
TPI
Frequently acquired via a Digital Measurement.
Tele-Signalling
TS
Logic position transmitted by a remote signal
Utility Communications Architecture
UCA
Communications standard mainly used in the US
Unit Per Impulse
UPI Counter parameter used to convert a number of pulses into a measurement value. Both data
(integer and scaled floating point) are in a common class UCA2 accumulator.
Universal Time Co-ordinates (or Universal Time Code)
UTC
UTC replaces GMT and it is identical.
VdBS Versioned data Base System, SCE-generated databag ready for download.
VDEW German subset of the IEC 60870-5-103 protocol.
VMGA Vertical Measurement Graphical Area
SCE/EN LX/C60 LX-9

Voltage level Set of bays in which plants and devices operate at the same voltage (e.g. 275 kV).
Voltage Transformer
Basically the device connected to the electrical process used to extract a voltage
VT
measurement. By extension part of a device (C26x) that receives this AC value & converts it to
a numerical measurement value. VTs are wired in parallel.
Wide-Area Control Unit
WACU
High-level controller
WTS Windows Terminal Server, Microsoft’s remote desktop connection.
Phase-neutral analogue values received from the "wye"(also known as “star”) winding
WYE MV
connections of a transformer .
LX-10 SCE/EN LX/C60

Alstom Grid
© - ALSTOM 2014. All rights reserved.

Information contained in this document is
indicative only. No representation or warranty
is given or should be relied on that it is
complete or correct or will apply to any
particular project. This will depend on the
technical and commercial circumstances. It is
provided without liability and is subject to
change without notice. Reproduction, use or
disclosure to third parties, without express
written authority, is strictly prohibited.
Alstom Grid Worldwide Contact Centre
www.alstom.com/grid/contactcentre/
Tel: +44 (0) 1785 250 070
www.alstom.com

SCE Enm C60

Uploaded by

Copyright:

Available Formats

SCE Enm C60

Uploaded by

Document Information

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

SCE Enm C60

Uploaded by

Copyright:

Available Formats

System Configuration Editor

System version: 5.1.0

INTRODUCTION SCE/IT EN/C60

SAFETY AND HANDLING SCE/SA EN/C60

FUNCTIONAL DESCRIPTION SCE/FT EN/C60

INSTALLATION SCE/IN EN/C60

ADJUSTMENTS SCE/AJ EN/C60

APPLICATION SCE/AP EN/C60

HUMAN INTERFACE SCE/HI EN/C60

MAINTENANCE SCE/MF EN/C60

PROBLEM ANALYSIS SCE/PR EN/C60

RECORD SHEET SCE/RS EN/C60

TECHNICAL DATA SCE/TD EN/C60

GLOSSARY SCE/LX EN/C60

Refer to the System Release Notes for new features.

2 INTRODUCTION TO DS AGILE MANUALS 4

SCE/EN IT/C60 IT-1

IT-2 SCE/EN IT/C60

SCE/EN IT/C60 IT-3

2 INTRODUCTION TO DS AGILE MANUALS

2.1 CHAPTER DESCRIPTION

IT-4 SCE/EN IT/C60

Technical Data (TD) Chapter

SCE/EN IT/C60 IT-5

 DS Agile OI, the Operator Interface for local HMI

IT-6 SCE/EN IT/C60

4 COPYRIGHTS & TRADEMARKS 6

5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS 7

SCE/EN SA/C60 SA-1

SA-2 SCE/EN SA/C60

SCE/EN SA/C60 SA-3

2.1 HEALTH AND SAFETY

2.2 EXPLANATION OF SYMBOLS AND LABELS

2.3 INSTALLING, COMMISSIONING AND SERVICING

Equipment operating conditions

Fibre optic communication

SA-4 SCE/EN SA/C60

SCE/EN SA/C60 SA-5

4 COPYRIGHTS & TRADEMARKS

SA-6 SCE/EN SA/C60

5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS

SCE/EN SA/C60 SA-7

SA-8 SCE/EN SA/C60

1 DS AGILE SCE ARCHITECTURE 3

SCE/EN FT/C60 FT-1

FT-2 SCE/EN FT/C60

1 DS AGILE SCE ARCHITECTURE

1.1 GENERAL DESCRIPTION

 DS Agile OI, the Operator Interface

 Inner data of the device itself (structure and parameters values)

1.2 FUNCTIONAL SPECIFICATION

 generates equipment databases

SCE/EN FT/C60 FT-3

1.2.1 DS AGILE SCE USERS

 Level 1 allows the modification of an existing configuration by adjustment of parameters, settings or

1.2.2 DS AGILE SCE TEMPLATE & OBJECT

FT-4 SCE/EN FT/C60

1.2.3 DATABASE CREATION PROCESS

Library = Collection of Models