Alstom Bcu

Operator Interface
Technical Manual
System version: 5.0.5
OI/EN M/C57b
DS Agile OI Technical Manual
CONTENTS
INTRODUCTION OI/IT EN/C57a
SAFETY AND HANDLING OI/SA EN/C57
FUNCTIONAL DESCRIPTION OI/FT EN/C57
HARDWARE OI/HW EN/C57
INSTALLATION OI/IN EN/C57
ADJUSTMENTS OI/AJ EN/C57
APPLICATION OI/AP EN/C57b
HUMAN INTERFACE OI/HI EN/C57
MAINTENANCE OI/MF EN/C57
RECORD SHEET OI/RS EN/C57
TECHNICAL DATA OI/TD EN/C57b
GLOSSARY OI/LX EN/C57a

Product /Project name – Type of document
WARNING
This guide gives instructions for installation, commissioning and operation of the DS Agile OI. 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
OI/EN IT/C57A
DS Agile Operator Interface Introduction
Contents
1 INTRODUCTION 3
2 INTRODUCTION TO DS AGILE MANUALS 4

2.1 Chapter description 4
3 MAIN ARCHITECTURES 6
OI/EN IT/C57a IT-1

Introduction DS Agile Operator Interface
IT-2 OI/EN IT/C57a

1 INTRODUCTION
The present document is a chapter of the Alstom DS Agile Operator Interface documentation. It describes
the documentation’s chapters you can find in the different guides, the types of applications and how to use
the product. It is the Introduction (IT) chapter of this Product's manual.
OI/EN IT/C57a IT-3

2 INTRODUCTION TO DS AGILE MANUALS

This manual provides a functional and technical description of the DS Agile Operator Interface - DS Agile OI
- and a comprehensive set of instructions for DS Agile OI’s use and application.
Important note:
The MiCOM Alstom range of C264 substation and bay computers is being widened to encompass new applications.
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 document: It contains the description of each chapter of the DS Agile OI guides. It is a brief introduction
to DS Agile OI’s 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 of DS Agile OI.
Hardware Description (HW) Chapter
This chapter contains the hardware product description (product identification, case, electronic boards, etc.).
Installation (IN) Chapter
This chapter contains the installation procedures.
Adjustments (AJ) Chapter
This chapter contains the list of settings for DS Agile OI.
Application (AP) Chapter
This chapter contains instructions on how to configure the features of the DS Agile OI using SCE.
HMI: Local Control and User Interface (HI) Chapter
This chapter describes the operator interface: menu tree organisation and browsing, description of items.
Maintenance, Fault Finding, Repairs (MF) Chapter
This chapter advises on how to recognise failure modes, fault codes and describes the recommended repair
actions.
Commissioning Record Sheet (RS) Chapter
This chapter provides detailed record sheets to commission DS Agile OI.
IT-4 OI/EN IT/C57a

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 the lexical description of acronyms and definitions of the DS Agile.
OI/EN IT/C57a IT-5

3 MAIN ARCHITECTURES
Centralized architecture: A DS Agile OI Server (S2K Server) and a DS Agile OI Client installed on a single
PC.
Distributed architecture: Up to 8 DS Agile OI Clients working with the same DS Agile OI Server, each one on
a separate PC.
Examples:
 Architecture including one OI client co-hosted with OI Server, one OI client apart and one WTS client
(for Windows Terminal Server installation and configuration, refer to the chapter DS Agile/EN IN for
the PC and OI/EN IN for the software applications):
Note: An OI Client connected to an OI Server that is not redundant (neither as twin master, nor in hot redundancy) is
referred to as “standalone”.
IT-6 OI/EN IT/C57a

 Bay Local OI = DS Agile A500 + panel PC for local OI Client; as the DS Agile A500 memory capacity
is limited, the temporary files are stored on a file server (Fileserv).
DS Agile A300 with

S2K Server DS Agile C26x
DS Agile OI Client
Windows XP embedded
DS Agile OI Client
File server
S1014ENb
The panel PC may also complement a DS Agile C26x-Standalone:
OI/EN IT/C57a IT-7

IT-8 OI/EN IT/C57a

SAFETY & HANDLING
OI/EN SA/C57
DS Agile Operator Interface 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
OI/EN SA/C57 SA-1

Safety & Handling DS Agile Operator Interface
SA-2 OI/EN SA/C57

1 INTRODUCTION
The present document is a chapter of the DS Agile Operator Interface documentation. It describes the safety
procedures applicable to DS Agile Operator Interface software tools.
OI/EN SA/C57 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 OI/EN SA/C57

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.
OI/EN SA/C57 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 OI/EN SA/C57

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.
OI/EN SA/C57 SA-7

SA-8 OI/EN SA/C57

FUNCTIONAL DESCRIPTION
OI/EN FT/C57
DS Agile Operator Interface Functional Description
Contents
1 SCOPE OF THE DOCUMENT 3
2 GENERAL OVERVIEW 4
2.1 Architecture 4
2.2 Basic functions 6
2.2.1 Control 6
2.2.2 Supervision 6
2.2.3 Archiving and Logging 7
2.2.4 Languages 7
2.2.5 Pictorial representation 7
2.3 Bay Local OI 7
3 DETAILED FUNCTIONS 8
3.1 Operator access rights 8
3.1.1 Access authorization 8
3.1.2 User rights, user profiles and user account 8
3.1.3 Online definition and modification of user accounts 9
3.1.4 Password change 19
3.1.5 Password Policy 19
3.1.6 User log notification 20
3.2 Device controls and counter modification 20
3.2.1 Introduction and generic features 20
3.2.2 Direct Execute Mode, without control window 21
3.2.3 Direct Execute Mode, with control window 22
3.2.4 SBO Mode 27
3.2.5 Switching device locking 44
3.2.6 Switching device interlocking 44
3.2.7 Control result 45
3.2.8 Counter value change 47
3.3 Alarm processing 47
3.3.1 Alarm definition 47
3.3.2 Alarm processing 50
3.4 Manual operations on datapoints 61
3.4.1 Datapoint suppression/unsuppression 63
3.4.2 Datapoint substitution/unsubstitution 65
3.4.3 Datapoint forcing 67
3.5 Memo function 69
3.6 Discordance management 72
3.7 Time stamp 72
3.7.1 Time stamp set by the source 72
3.7.2 Time stamp set by the S2K server 72
3.8 Data logging 73
3.8.1 Printing mechanisms 73
3.8.2 Printing format 74
3.8.3 Sequence Of Event (SOE) 74
3.8.4 Log Book (LB) 75
3.8.5 Multi-screen snapshot tool 77
OI/EN FT/C57 FT-1

Functional Description DS Agile Operator Interface
3.9 Data archiving 78

3.9.1 General 78
3.9.2 Archiving 78
3.9.3 Backup 79
3.9.4 Archive restoration 82
3.9.5 Archive viewing 86
3.9.6 Reports generation 86
3.9.7 Summary 87
4 HOT REDUNDANCY CLUSTER 88

4.1 OI Server functions vs OI Server State 89
4.2 OI Server Fault Tolerance State Automation 90
4.3 OI Setting 93
4.4 OI System datapoints 93
4.5 Unknown state management 93
4.6 Redundancy performance 93
4.7 Consolidated Archive Files 93
5 APPENDIX: USE OF CRYSTAL REPORTS 95

5.1 How to create a report ? 95
5.1.1 Crystal Reports configuration 95
5.1.2 Create a button in SCE to launch a report 107
5.2 How to use a report created before version OI G.03.07 108
5.3 Create a template under Crystal Reports 111
FT-2 OI/EN FT/C57

1 SCOPE OF THE DOCUMENT

This document is a chapter of the DS Agile OI documentation. It describes the functions. The hardware
description is defined in chapter OI/EN HW. The product capabilities, as well as its performances and
environmental limits are summarized in chapter OI/EN TD (Technical Data).
OI/EN FT/C57 FT-3

2 GENERAL OVERVIEW
IMPORTANT:
All illustrations and views are examples: they may be modified according to the
customer’s requirements.
Some functions described below are dependent of the DS Agile project configuration and
their behavior may vary or the corresponding function may be unavailable.
2.1 ARCHITECTURE
The Operator Interface (DS Agile OI) is the graphical user interface of DS Agile. DS Agile OI allows the
operator to supervise, control and maintain the substations in a very easy and comfortable manner.
DS Agile OI is used as a local or remote workstation for HV and MV substations and for power plants. It can
also be used as a DS Agile OI for satellite substations.
The Operator Interface is installed on an Operator Workstation (OWS) that can support other applications:
• the System Management Tool (DS Agile SMT) is used to maintain and monitor the DS Agile system
itself
• the Setting Software is used to view and modify the settings of MiCOM Alstom devices
• other applications dedicated to particular functions (disturbance record analysis, etc…)
The DS Agile Operator Interface runs on Windows 2003 Server, Windows XP, Windows XP Embedded or
Windows 7 Ultimate 64 bits (in XP compatibility mode). Only the “bay local OI” type application (see later in
this document) may be installed on an XP embedded-based PC.
All Operator Interface functions can be accessed remotely through Internet, PSTN or dedicated links, using
the Windows Terminal Services function (WTS). To protect the system against external access, DS Agile can
be provided with a firewall.
DS Agile OI is based on the SCADA 2000 product.
It is based on a Microsoft COM architecture consisting of one or several first tier HMI Clients (DS Agile
OI Client, up to 8) connected to 1 or 2 (in case of redundancy) middle tier Servers (DS Agile OI Server). The
last tier consists of a Data Base repository with an SQL server.
The SQL 2005 server application can be installed on a PC distinct from the one which supports the
OI Server application.
OI Clients provide the user with an interface for all operational and engineering functions. In case of a
connection to multiple DS Agile OI Servers, the information will be displayed as if it were coming from a
single server. Connectivity between Clients and Servers is provided via the Station Bus, a dial-up connection
or through the Internet.
FT-4 OI/EN FT/C57

OI Clients
Internet
OI Servers
Alarm Historian Data Communication Controls

and Trends Processing
Events SQL Server
INFRASTRUCTURE
S0440ENa
A simple DS Agile OI architecture is based on a single PC which supports both client and server. A complex
architecture is based on a dedicated PC supporting the servers and other PCs supporting the clients.
OI/EN FT/C57 FT-5

2.2 BASIC FUNCTIONS
2.2.1 CONTROL
• alarms acknowledgement and clearing
• control of switching devices (circuit breaker, switchgear, …)
• locking of switching devices
• control of transformers
• control of secondary devices
• control of internal automation
2.2.2 SUPERVISION
• access authorization
• single line diagram topological view
• full graphic representation of switching devices
• full graphic representation of analogue values
• full graphic representation of additional process information
• display of automations state
• display and modification of counters
• display of alarms in list form
• display of events
• display of states
• display of archives
• viewing of curves for archived or real-time analogue and digital data
• Forcing, Substitution, Suppression of datapoints
• memo function
• discordance management
• directly accessible OI/EN HI chapter
• reports creation
• hardcopy
• tooltips
FT-6 OI/EN FT/C57

2.2.3 ARCHIVING AND LOGGING
2.2.4 LANGUAGES
DS Agile OI supports multiple languages as supported by:
• Windows 2003 Server,

• Windows XP,
• Windows 7.
Localization of DS Agile OI is possible, including Unicode languages such as Chinese or Korean due to
internal character representation using multiple-byte storage.
2.2.5 PICTORIAL REPRESENTATION

Refer to the OI/EN HI chapter.
2.3 BAY LOCAL OI

The Bay Local OI offers a color display to complement the DS Agile C26x LHMI. It can be a client of one or
several IEC 61850-8-1 servers. Its OI Server cannot be redundant.
The Bay Local OI has most of the regular OI capabilities, except that it does NOT manage:
• banners (except for Terna)

• audible alarms
• FSS indication
• local archives
A virtual keyboard is available.
Controls are accepted by a C26x in Local mode.
The OI can run without FILESERV, but in that case the Historian database cannot be used (neither events
nor archived events are available).
OI/EN FT/C57 FT-7

3 DETAILED FUNCTIONS
3.1 OPERATOR ACCESS RIGHTS
3.1.1 ACCESS AUTHORIZATION

After launching DS Agile OI, two behaviors are allowed:
• login is mandatory: using the Log-In / Log-Off button on the tool banner , the operator must
enter his/her user name and the associated password
• a pre-defined user, which has only view rights, is already logged in: this allows an operator to view the
current substation state without having to go through the login procedure. The operator must log-off
and then log-on with an appropriate user name, using the Log-In / Log-Off button on the tool banner,
if he/she wants to control the substation.
The choice of the type of login procedure is defined during the DS Agile OI installation process.
The login window is as follows:
The user must enter his user name and his/her password, then either press Enter or click OK.
Once logged in, the user name and corresponding profile are displayed on the header banner.
There is an option to automatically log off when there no operator activity occurs during a configured time-out
period.
Access may also be secured by the use of a card access mechanism.
3.1.2 USER RIGHTS, USER PROFILES AND USER ACCOUNT

A user account is defined by a user name, a password and a profile. A profile is an ensemble of user rights
which define permissions for all types of actions. A user right is the right related to a type of action.
User rights and user profiles are defined during database configuration and cannot be modified online. Users
are defined and can be modified online. Two specific users are created during configuration that cannot be
modified online: AdmOdyssey with administrator rights, and PublicOdyssey with viewing rights only.
3.1.2.1 USER RIGHTS AND USER PROFILES

The following user rights are available:
• General rights:
Administrator (allows launching SMT with administrator and user management rights)
Exit the DS Agile OI application
Audible alarm general stop
Hardcopy
DS Agile SMT launch (with viewer right)
Tools launch
FT-8 OI/EN FT/C57

• View rights: up to 64 levels for access to a specific mimic. These rights are defined separately for each
mimic.
• Control rights: up to 64 levels for control, lock, bypass and force / suppress / substitute purposes.
These rights are defined at the bay level, thus all the modules attached to a particular bay will have
the same control rights.
• Acknowledgement rights: up to 64 levels for individual alarm acknowledgement and clearing. These
rights are defined separately for each datapoint.
• Group acknowledgement rights: up to 64 levels for graphical alarm groups acknowledgement and
clearing. These rights are defined separately for each graphical alarm group.
These user rights are assigned to user profiles. Up to 20 user profiles can be defined during the
configuration process. A user profile is freely assigned: 0, 1 or several general rights, plus 0, 1 or several
view rights, plus 0, 1 or several control rights, plus 0, 1 or several acknowledgement rights.
After a database switch, if some profiles have been deleted / updated from the configuration, the users are
automatically updated with these new profiles.
Note: If, while being logged on as an administrator, you erroneously typed CTRL+Pause/Break, close the window
that subsequently popped up.
3.1.3 ONLINE DEFINITION AND MODIFICATION OF USER ACCOUNTS

The user names and the associated passwords are created / deleted online on DS Agile OI by a user with
administrator rights (except for the pre-defined user in case n°2 of the “access authorization” above and the
“super-user” who owns the administrator rights). A user is defined with an associated language (at the user
login, the DS Agile OI automatically switches to the corresponding language) and a profile to be chosen
among those defined in the configuration. Up to 10 user names can be defined.
OI/EN FT/C57 FT-9

3.1.3.1 CREATION OF A NEW USER ACCOUNT

In order to create a new user account, the user with administrator rights must:
1 Click the command banner’s Profiles button . This opens the user profile utility window that
displays the list of existing users with their associated language and profile:
FT-10 OI/EN FT/C57

2 Right-click on the window to display the contextual menu:
3 Choose New user in the contextual menu. This displays the following window:
4 Fill in the different fields:

User name (user log on)
Full name (optional, for information)
OI/EN FT/C57 FT-11

Language (when the user logs on, DS Agile OI automatically switches to his/her assigned
language).
WARNING: Several languages are listed but only the languages defined when the
database was configured may be used.
5 Assign a profile by selecting the chosen one in the list of Available profiles and clicking to
assign it to the user account, so that it appears in the Selected profiles box (in this example the
selected profile is “User profile”).
If the user wants to change profiles, the current profile must first be removed by selecting it and clicking .
A new profile can then be assigned.
FT-12 OI/EN FT/C57

6 Click OK to confirm the creation of the user account. The User Profile Utility window is then
displayed, updated to include the new user.
7 Click again on OK to confirm the new user creation.

The change is immediately taken into account and the new user can log on. The default password is the
user name (as the login) and it can be changed.
OI/EN FT/C57 FT-13

3.1.3.2 MODIFICATION OF A USER ACCOUNT

To change a user account attributes, the user with administrator rights must:
1 Click the command banner’s Profiles button . This opens the User Profile Utility window that
displays the list of existing users with their associated language and their profile:
FT-14 OI/EN FT/C57

2 Select the user account to be modified (except the 2 predefined users) and right-click on it to display
the contextual menu:
3 Choose Edit user in the contextual menu. This displays the following window:
OI/EN FT/C57 FT-15

The user can then modify his/her language or profile. If the user wants to change profiles, the current profile
must first be removed by selecting it and clicking . A new profile can then be assigned. In ths example
the user jonh has changed his language to French and his profile to shortPublic.
4 Click OK to confirm the modification of the user account. The user profile utility window is then
displayed, updated with these changes.
5 Click OK to accept this change.
FT-16 OI/EN FT/C57

3.1.3.3 DELETION OF A USER ACCOUNT

In order to delete a user account, the user with administrator rights must:
1 Click the command banner’s Profiles button . This opens the user profile utility window that
displays the list of existing users with their associated language and their associated profile:
2 Select the user account to be deleted (except the 2 predefined users) and right-click right to edit
contextual menu
OI/EN FT/C57 FT-17

3 Choose Remove User. The user account is immediately deleted.
4 Click OK to accept this change
FT-18 OI/EN FT/C57

3.1.4 PASSWORD CHANGE

The password can be changed via the tool banner by clicking Password. The following window is displayed:
The user must enter his/her current password and click Validate and enter the new password, click Validate
again, confirm the new password and click Validate again, then close the window.
If s/he clicks Clear, the character chain s/he is in the process of entering will be cleared.
3.1.5 PASSWORD POLICY

The OI password can be changed by the user using the Password Utility dialog box.
The newly entered password may or may not need to have its validity checked against a specific set of rules
defined in a registry entry.
The password policy is defined by a registry key. The registry entry is named "PasswordsPolicyLevel".
It is located in: HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\OI
In a new installation, the registry key is created with a low security level: Registry Key = 0.
The registry key can later be changed to a high security level: Registry Key = 1.
PasswordPolicyLevel:
1: with password validity check
0: without password validity check (default value)
In order to be valid, the new password must comply with the following rules:
Rules Character set
7 ≤ number of symbols ≤ 64
At least 1 digit [0-9]
at least 1 upper case letter Chinese No Password Policy
English [A-Z]
French [A-Z]
German [A-Z] Ä Ö Ü
Greek [A-Z] Ά [Έ-Ώ] [A-Y]
OI/EN FT/C57 FT-19

Rules Character set

Italian [A-Z]
Polish [A-Z] Ą Ę Ó Ć Ł Ń Ś Ź Ż
Portuguese [A-Z]
Romanian [A-Z] Â Ă Î Ş Ţ
Russian [Ё-Я]
Spanish [A-Z] Á É Í Ó Ú Ü Ñ
Swedish [A-Z]
Turkish [A-Z] İ Ö Ü Ç Ğ Ş
The password validation process is activated when the password is modified through the Password Utility
dialog box if the registry key is set to 1.
It has no effect on:
• the 2 preconfigured passwords (Administrator and ShortPublic)

• the default password assigned to a newly created profile
• the passwords that have been previously configured with the 0 Password Policy Level
3.1.6 USER LOG NOTIFICATION

It is possible to add an optional SPC datapoint which will indicate whether the OI workstation is currently
used by an operator: notify login/logoff SPC. It this feature is configured a control is automatically sent
onto an SPC datapoint indicating that a user has logged on or off an OI Client.
This notification can be used as part of a logic scheme.
3.2 DEVICE CONTROLS AND COUNTER MODIFICATION
3.2.1 INTRODUCTION AND GENERIC FEATURES

Control can take place in all displays where it is useful and configured. It is always possible to open a control
popup window, assuming the operator has the view right on the mimic which contains the popup. The control
can be executed either in “Select Before Operate” (SBO) or “Direct Execute” mode: this mode is defined
during the configuration process. Furthermore, in direct execute mode it is possible to use different control
popups or even only a button and no control popup at all.
The control popup can be closed during a control sequence: this does not cancel the sequence. Thus, if the
operator re-opens the popup during the control sequence, he/she will retrieve the current context of the
sequence. Only one control popup can be opened on an operator station at one time. The unauthorized
commands will be grayed out in the control popup.
A control acknowledgement pop-up is used to display negative control acknowledgements and to allow users
with appropriate rights to bypass the interlocking control check. In this case, the user can display the
interlocking equation and get the reason for the control’s rejection.
Some control condition checks are handled by DS Agile OI, others are checked at computer level.
FT-20 OI/EN FT/C57

The control condition checks handled by DS Agile OI include:
• the user rights

• the local / remote substation mode
• the local / remote / SBMC bay mode
• the automatic / manual state of the associated automation (for instance raise / lower controls on a tap
changer are forbidden while the ATCC is in operation)
Except for the first one (always active), each one of these checks can be enabled or not at configuration
level for each control. Access to control buttons in the popup depends on DS Agile OI’s control condition
checks.
A specific function, the synchrocheck function, can be used when closing a circuit breaker in order to avoid
interconnecting two unsynchronized power systems. The DS Agile synchrocheck function consists in
measuring two voltages (angle, frequency and magnitude) and closing the circuit breaker only when the
conditions predefined for these measurements are met.
3.2.2 DIRECT EXECUTE MODE, WITHOUT CONTROL WINDOW

In this mode a button configured in a mimic can be assigned to a control command (for example an OFF
control command). The control is sent immediately when the operator clicks the button.
For analogue controls, the sequence is somewhat different: a box appears to allow the operator to enter the
control value.
After a click the button, here oil temp, a small text area appears in place of the button.
OI/EN FT/C57 FT-21

The operator must enter the value that he/she wants to send and then press the Enter key. The window is
then automatically closed. An acknowledgement popup will be displayed only in the event of a control failure.
3.2.3 DIRECT EXECUTE MODE, WITH CONTROL WINDOW

In Direct Execute mode two direct control box formats are available (Direct Execute or Direct Execute with
SBO window, i.e. DE appearing in an SBO-like popup), the choice of this format is defined during the
configuration process. The logical sequence is identical for both formats..
In this mode, the control process, from DS Agile OI point of view, is composed of two commands:
• the graphic selection command that opens the control window

• the Direct Execute command itself
3.2.3.1 FORMAT 1: DIRECT EXECUTE CONTROL WINDOW
The Direct Execute Control window is made up of two boxes: the Direct Control Box which contains the
buttons and the Control Status box which explains why the control is not authorized in case of HMI negative
checks (in that case, the buttons are grayed out).
To sends the command he/she wants, all the operator has to do is click the corresponding button (thereafter
the button appears pressed).
FT-22 OI/EN FT/C57

An acknowledgement popup is displayed in case of failure only. Depending on the options defined in
configuration, the control popup is automatically closed or not. If it is not automatically closed, the operator
can either close it or issue a new control.
3.2.3.2 FORMAT 2: DIRECT EXECUTE WITH SBO WINDOW

The direct execute with SBO window is different from the previous one as the user must choose the
command before clicking Execute.
Moreover there can be an optional tab to allow manual operations on datapoints (see section 3.4 Manual
operations on datapoints):
OI/EN FT/C57 FT-23

3.2.3.3 GRAPHICAL SEQUENCE

After the opening the window, the user must select the command by clicking on it. Then, the chosen
command is highlighted and the Execute button becomes available. At this stage no control command has
been sent.
The operator sends the command by clicking Execute. The Execute button is displayed as pressed.
FT-24 OI/EN FT/C57

An acknowledgement pop-up is displayed only in case of failure. Depending on the options defined in
configuration, the control popup is automatically closed or not. If it is not automatically closed, the user can
either close it or send a new control command.
OI/EN FT/C57 FT-25

3.2.3.4 LOGICAL SEQUENCE

Graphic Selection Process
Unselected device
first operator graphic selection (only

if he has appropriate control rights)
Device with
« Select » graphic
attribute (optional,
defined in conf)
no
Immediate display of Time-out launching
the control pop-up
(config) Time-out
yes second operator

graphic selection
Display of the
control pop-up
Control
sequence
Control acknowledge
Control pop-up
already closed ?
yes Automatic closure of no

the control pop-up
(config) ?
Only if positive yes

acknowledge
(config) ?
no Positive no
acknowledgement ?
yes
Operator closure request
Closure of the
control pop-up
1
S0441ENa
FT-26 OI/EN FT/C57

Direct Execute Process
no
Control Authorised ?
Operator pop-up
closure request
Operator control choice yes
(click on open button,
close button, …) Closure of the
control pop-up
Send the execute

order Unselected device
(see graphical selection phase)
Operator pop-up
closure request
Note 1 : at the OI level, only
the interlocking by-pass is
allowed Closure of the
control pop-up
Control acknowledge
no Positive
acknowledgement ?
Display of the " control

acknowledge window " yes
1
no
By-pass authorised ?
(note 1) Operator " control ack.
yes window " closure
request
Operator by-pass choice
(click-on bypass button)
S0442ENa
3.2.4 SBO MODE

In this mode, the control process, from DS Agile OI point of view, is composed of two commands:
• the graphic selection command

• the SBO command itself
The control window is made up of two boxes: the Direct Control box which contains the buttons and the
Control Status box which explains why the control is not authorized in case of HMI negative checks (in that
case, the buttons are grayed out).
OI/EN FT/C57 FT-27

There are two optional tabs: the first one SynchroCheck when the control uses the synchrocheck function,
the second one FSS to allow manual operations on datapoints (see 3.4 Manual operations on datapoints).
The graphic selection phase is identical to the phase described in the Direct Execute mode.
There are two SBO modes:
• OPERATE ONCE: after the selection, only one execution is allowed and the control is automatically
unselected
• OPERATE MANY: after the selection, one or several executions are allowed, and the operator must
unselect the device manually
Moreover, a synchrocheck function can be used to manage the closing of the circuit breaker.
Note: The select command also contains the control value (i.e. open, close…).
FT-28 OI/EN FT/C57

3.2.4.1 SBO OPERATE ONCE WITHOUT SYNCHROCHECK

3.2.4.1.1 Logical sequence
SBO / Operate Once process
no
Select Authorised ?
Operator pop-up
closure request
yes
Operator control choice (open, close, …)
and click on the " Select " button Closure of the
control pop-up
Send the select

Operator cancel Operator pop-up

closure request
Send the cancel Closure of the

order control pop-up
② Select acknowledge
no Positive
acknowledge ? yes
acknowledge window " no
Execute Authorised ?
1
no
① Operator control choice (open, close, …)
yes
Negative spontaneous
(note 1)
and click on the " Execute " button acknowledgement
yes
Operator by-pass choice no
Send the execute acknowledge window "
(click-on bypass button)
order
①
closure request
Note 1 : at the OI level, only the Send the cancel Closure of the
interlocking by-pass is allowed order (note 2) control pop-up
Note 2 : the cancel order is taken into

account only for synchronised circuit
② Control acknowledge
breaker is the " close " digital output (with negative acknowledge)
has not been closed. In all other cases,
the cancel order is not processed. no Positive
acknowledge ?
1
no
(note 1)
yes
① (with negative ack.)
(click-on bypass button) Operator " control ack.
window " closure request
S0443ENa
OI/EN FT/C57 FT-29

3.2.4.1.2 Graphical sequence

1 After graphical selection the following control window is displayed:
2 The user can select the command by clicking on it (close for example). Then the chosen command is
highlighted and the Select button appears as available:
3 S/he can then select the device by clicking Select. If the selection is successful, the Execute and
Abort buttons are available.
FT-30 OI/EN FT/C57

4 The user can choose to abort, in which case a cancellation command is sent, or to execute, in which
case the Execute button is grayed out and the Abort button is still available.
An acknowledgement pop-up is displayed only in case of failure. Depending on the options defined in
configuration, the control popup is automatically closed or not. If it is not automatically closed, the user can
either close it or execute a new control sequence. In any case, control success or failure, the device is
unselected.
OI/EN FT/C57 FT-31

3.2.4.2 SBO OPERATE MANY (WITHOUT SYNCHROCHECK)

3.2.4.2.1 Logical sequence
SBO / OPERATE MANY process
no
Select Authorised ?
Operator pop-up
closure request
yes
Closure of the
and click on the " Select " button
control pop-up
Send the select


closure request
Send the cancel Closure of the

order control pop-up
② Select acknowledge
no Positive
acknowledge ? yes
acknowledge window " no
Execute Authorised ?
1
Operator control choice (open, close, …) yes
no
(note 1)
① and click on the " Execute " button negative spontaneous
acknowledgement
yes
Send the execute
Operator by-pass choice order Display of the " control
(click-on bypass button) acknowledge window "

closure request ①
Note 1 : at the OI level, only the Send the cancel
interlocking by-pass is allowed Closure of the
order (note 2) control pop-up
②
Note 2 : the cancel order is taken into
account only for synchronised circuit
breaker is the " close " digital output Control acknowledge
has not been closed. In all other cases,
the cancel order is not processed. no Positive yes
acknowledge ?

acknowledge window " Operator
unselection ?
no
1
no yes
(note 1) Send the unselect
yes order
(click-on bypass button) Control
acknowledge
yes
①
Positive
acknowledge ?
(with negative acknowledge)

acknowledge window "
Operator " control ack.

window " closure request
S0444ENa
FT-32 OI/EN FT/C57

3.2.4.2.2 Graphical sequence

1 After graphical selection the following control window is displayed:
2 The user can choose the command he/she wants to send by clicking on it (close for example). The
chosen command is then highlighted and the Select button appears as available:
3 S/he can then send a select command by clicking Select. If the selection is successful, the Execute
and Abort buttons are available.
OI/EN FT/C57 FT-33

4 The user can choose to

Abort: in this case a cancellation command is sent
Unselect: in this case an unselect command is sent
Execute: in this case the Execute and UnSelect buttons are grayed out, the Abort button is
always available.
5 An acknowledgement pop-up is displayed only in case of failure. Depending on the options defined in
configuration, the control popup is automatically closed or not. If the control fails the device is
unselected. If it is successful it is always selected. Thus if the control is successful the user can either
execute the chosen command again or unselect the device.
FT-34 OI/EN FT/C57

6 To unselect the device, the user only needs to click UnSelect. If the control fails an acknowledgement
popup is displayed, if the control is successful the UnSelect button is replaced by the Select button.
3.2.4.3 SBO OPERATE ONCE MODE WITH SYNCHROCHECK

It is possible to use an SC function to manage the closing of circuit breaker. This function must be predefined
in configuration and so must be the associated circuit breaker closing conditions. This function can be
manual or automatic depending on the configuration.
In the manual option, a specific window is used to enable or disable the SC function. Depending on the state of
that function: on or off, all the close commands sent will activate or not the SC function.
In the automatic option, there is no specific SC enable window: The user chooses directly at the control
window level whether to close with SC or close without SC. In the case of a close with SC command, the
SC function is activated.
When the SC function is used to send a control command, the usual control conditions are checked and if
they are met, the SC is activated. When it is activated, it continuously checks the closing conditions and
waits until the correct closing conditions are met to send the control, during which time the user can decide
to force or to cancel the control. The force sequence is optional and depends on the operator rights. There is
a configurable time-out for the SC function.
OI/EN FT/C57 FT-35

3.2.4.3.1 Manual Synchrocheck

3.2.4.3.1.1 Logical sequence
Select no
Authorised ?
Operator pop-up
closure request
control pop-up
Send the select

Operator pop-up
closure request
Closure of the
control pop-up
Select acknowledge
no Positive yes
acknowledge ?
no
Execute
Authorised ?
Click on the " Execute " button
negative
1 acknowledgement
no
① ③ no Close and
synchro set on
③
(note 1) Display of the " control
yes acknowledge window "
yes
(click-on bypass button) Send the execute
order close with
synchro ①
Operator pop-up
Operator Close control no closure request
cancel under synchro
yes Closure of the
Note 1: at the OI level, only the Send the cancel control pop-up
interlocking by-pass is allowed order (note 2) CB close forcing
allowed
Note 2: the cancel order is taken Thumbnail activated
into account only for synchronised Operator Closing Time out
circuit breaker is the «close» forcing condition OK
digital output has not been closed.
In all other cases, the cancel ② Control
order is not processed. (with negative acknowledge
acknowledge)
no Positive
acknowledge ?
Note 3 : in the case of an open
order or a set off synchrocheck Display of the " control
order cf. to the SBO once logical acknowledge window "
sequence. yes
no
1
yes
(note 1) ① (with negative ack.)
Operator by-pass
choice (click-on Operator «control
bypass button) ack. window» closure
request S0445ENa
FT-36 OI/EN FT/C57

3.2.4.3.1.2 Graphical sequence without forcing

1 The synchrocheck function must first be enabled in a dedicated window.
Once the function is enabled, the operator opens the switching device control window.
2 The operator sends a close command following the classical SBO sequence:
He/she chooses Order close and clicks Select. If the selection is successful the Execute button
becomes available.
He/she sends an execute command by clicking Execute. The synchrocheck is activated and waits
until the correct conditions are met to execute the close command. The Select and the Execute
buttons are grayed out.
OI/EN FT/C57 FT-37

3 If the control sequence is successful no acknowledgement popup is displayed. If the control sequence
has timed out (closing conditions were not met during the time allotted) or failed due to any other
reasons an acknowledgement popup is displayed. Depending on the options defined in configuration,
the control popup is automatically closed or not.
3.2.4.3.1.3 Graphical sequence with forcing

If the option is configured and if the user is granted the corresponding rights, he/she can force the
synchrocheck function, that is to say close the circuit breaker even if the defined closing conditions are not
met.
The user can carry out a forcing after having sent a select and execute close command, once the
synchrocheck function is enabled. The SynchroCheck tab is then available.
To force the synchrocheck function, the user must:

1 Click on the SynchroCheck tab to view the measurements and display the Manual Override button.
FT-38 OI/EN FT/C57

2 Click Manual Override to execute a close command. The operator can also choose to return to the
Control tab and cancel the command or wait until the end of the current sequences.
3 Like in a standard sequence, an acknowledgement popup will be displayed only in of the event of a
failure. Depending on the options defined in configuration, the control popup is automatically closed or
not.
In any case: control success or failure, the device is unselected.
OI/EN FT/C57 FT-39

3.2.4.3.2 Automatic Synchrocheck

3.2.4.3.2.1 Logical sequence
Select no
Authorised ?
Operator pop-up
closure request
Operator control choice (open, close, …) yes
control pop-up
Send the select

Operator pop-up
closure request
Closure of the
control pop-up
Select acknowledge
no yes
Positive
acknowledge ?
no
Execute
Authorised ?
Click on the " Execute " button negative
1 acknowledgement
no
① ③ no Close with
③
(note 1) synchro
yes acknowledge window "
yes
(click-on bypass button) Send the execute
order close with
synchro ①
Operator pop-up
Operator Close control no closure request
cancel under synchro
yes Closure of the
Note 1: at the OI level, only the Send the cancel control pop-up
interlocking by-pass is allowed order (note 2) CB close forcing
allowed
Note 2: the cancel order is taken Thumbnail activated
into account only for synchronised Operator Closing Time out
circuit breaker is the «close» forcing condition OK
digital output has not been closed.
In all other cases, the cancel ② Control
order is not processed. (with negative acknowledge
acknowledge) no Positive
acknowledge ?
Note 3 : in the case of an open
order or close without
synchrocheck order cf. to the Display of the " control
SBO once logical sequence. acknowledge window " yes
no
1
yes
(note 1) ① (with
( negative ack.)
Operator by-pass Operator «control
choice (click-on ack. window» closure
bypass button) request
S0446ENa
FT-40 OI/EN FT/C57

3.2.4.3.2.2 Graphical sequence without forcing

In the case of an automatic synchrocheck, the choice of whether or not to use the synchrocheck function is
made directly at the control window level: there are two available close commands: CLOSE or CLOSE
SYNCHRO (close with synchrocheck).
To send a close command using the synchrocheck function the user must:
1 Follow the classical SBO sequence using the CLOSE SYNCHRO command (otherwise the
synchrocheck function will not be used):
He/she chooses CLOSE SYNCHRO and clicks Select. If the selection is successful the Execute
button becomes available.
He/she sends an execute command by clicking Execute. The synchrocheck function is activated
and waits until the correct conditions are met to execute the close command. The Select and
Execute buttons are grayed out. As soon as the synchrocheck function is activated and the forcing
allowed, the SynchroCheck tab is available.
OI/EN FT/C57 FT-41

2 If the control sequence is successful no acknowledgement popup is displayed. If the control sequence
has timed out (the closing conditions have not been met during the time allotted) or failed for any other
reasons an acknowledgement popup is displayed. Depending on the options defined in configuration,
the control popup is automatically closed or not.
3.2.4.3.2.3 Graphical sequence with forcing
If the option is configured and if the user is granted the corresponding rights, he/she can force the
synchrocheck function, that is to say close the circuit breaker even if the defined closing conditions are not
fulfilled.
The user can carry out the forcing after having sent a select and execute close command, if the
synchrocheck function is enabled. In this case the SynchroCheck tab is available.
To force the synchrocheck function, the user must:

1 Click on the SynchroCheck tab to view the measurements if they are configured (up to three
measurements can be configured) and display the Manual Override button.
FT-42 OI/EN FT/C57

2 Click Manual override to execute the close command. The operator can also choose to return to the
Control tab and cancel the command or wait until the end of the current sequences.
3 Like in a standard sequence, an acknowledgement pop-up will be displayed only in the event of a
failure. Depending on the options defined in configuration, the control popup is automatically closed or
not.
In any case: control success or failure the device is unselected.
OI/EN FT/C57 FT-43

3.2.5 SWITCHING DEVICE LOCKING

The switching device locking function, if it was defined during the configuration process, make it possible to
deny all the control points control over the corresponding switching device. After locking, the symbol of the
switching device changes or an additional symbol appears (configurable) in the mimic view and control from
all the points is denied until the switching device is unlocked. After unlocking, the switching device symbol
changes or the additional symbol will disappear (configurable).
The lock/unlock control may be accessed using a specific control window. To lock/unlock a switching device
the user must:
1 Open the corresponding window:
2 Click Lock or Unlock, which will then appear pressed.
3 An acknowledgement popup will be displayed only in case of failure. Depending on the options
defined in configuration, the control popup is automatically closed or not.
3.2.6 SWITCHING DEVICE INTERLOCKING

Switching device interlocking, if it was defined during the configuration process, consists in adding conditions
to be verified during the control sequence. These conditions are defined in logical equations and apply to a
type of command on a device (close/open). The association of the logic state true/false (corresponding to
green/red color on the diagram) with the different variable states (i.e. jammed, motion, open) is predefined
and can be changed during the configuration process.
If the result check is positive, the control sequence continues.
FT-44 OI/EN FT/C57

If the result check is negative, an acknowledgement popup is displayed to explain that interlocking conditions
were not met.
The corresponding interlock equation can be viewed by clicking the button .
The upper square indicates the interlock equation result: red for NOK and green for OK. The remainder
details the interlock equation.
The interlock equation is detailed in a tree form: one level consisting in the different variables with their
true/false state and the logic symbol that links them together (and, or…). A logic symbol can link to other
symbols under which there can be other variables or symbols.
The interlock equation is updated in real-time.
The user can either cancel the control or, if he is granted the corresponding rights, bypass the interlock. In
the first case the control sequence is terminated (failure due to interlocking), in the second case the control
sequence continues.
3.2.7 CONTROL RESULT

If the control result is positive no acknowledgement pop-up is displayed. The control window can be
configured to be automatically closed (only for a positive acknowledgement, whatever the
acknowledgement), or never closed.
If the control result is negative an acknowledgement pop-up is displayed explaining why the control has
failed.
OI/EN FT/C57 FT-45

The user must click OK to close the acknowledgement pop-up. Thus, the control window is closed or not
according to the configuration options.
The different failure causes managed by the system are listed below. The message displayed at OWS level
can be modified at configuration level.
Acknowledgements Comments
Normal termination Positive acknowledgement
Incoherent request Unknown device, unknown or erroneous control
Computer not ready Control received during computer’s initialization
Bay-substation mode fault Control not permitted by the substation or bay mode (local/remote and SBMC)
Computer’s mode fault Computer in maintenance mode or faulty
Device locked Device locked by the user
Control in progress (only one control at a time is allowed for a device) or control
Control in progress
received before the inter-control delay times out
Interlock check NOK Control not permitted by interlocks check
Device already in position Requested position identical to the current position of the switching device
Hardware fault Hardware error on I/O board (see note)
Device position invalid Device in an invalid position
Time-out failed Selection time-out, or no response from the IED in the given delay
The control not allowed because an automatic function is activated for device
Automation running
monitoring
Device already selected Control request received while the switching device is already selected
Device not selectable Selection request received for a device controlled in direct execute mode
Control not allowed because it must respect control uniqueness at substation level
Uniqueness incoherence
or at bay level
Execution request received for a device control in SBO once or SBO many mode
Device not selected
that had not been selected previously
Operator cancel Control sequence cancelled by an operator request
External fault The BI giving the device position is not received in the configured delay
Acknowledgement failed order Station Bus acknowledgement failed
Bad TCIP The TCIP is not received in the configured delay
TCIP too long The TCIP pulse duration is abnormal
Bad tap position Bad tap position after the control
Min tap position “lower” control received while the TPI is in MIN position
Max tap position “raise” control received while the TPI is in MAX position
Device failed to operate Control to a disconnected IED
Synchrocheck NOK Control not allowed by the synchrocheck function
ATCC Off ATCC out of service: only the "ATCC on" control is allowed
FT-46 OI/EN FT/C57

Acknowledgements Comments
Too many transformers More than 4 transformers are connected: the ATCC cannot be managed
At least one device of the network is in invalid position: the topology cannot be
Invalid Topology
defined
Invalid TPI The transformer tap position is invalid
Transformer computer The computer which manages a transformer bay is disconnected from the Ethernet
disconnected network
MCB trip Trip by the transformer's miniature circuit breaker
Invalid transformer voltage The transformer voltage is invalid (out of range)
Invalid busbar voltage The busbar voltage is invalid (out of range)
Note: If the DOU board is located in an extension rack, the error may be caused by the feedback time-out being:
- less than twice the open or close time of the command and
- less than the open/close time plus 100 ms
3.2.8 COUNTER VALUE CHANGE

The counter value can be changed by an operator using the following control window:
• Click in the Set value box, enter the value to send (pulse * energy for one pulse), press Enter.
• Click Set; the value is divided by the energy for one pulse and set in the C26x/OI.
3.3 ALARM PROCESSING
3.3.1 ALARM DEFINITION

An alarm is a visual (and optionally audible) indication of the appearance and/or disappearance, within the
controlled electrical process or within the control system itself, of an event, defined during the configuration
process as “to be alarmed”.
These definitions, of what is to be alarmed and what it is not, are completely user-settable.
However the alarms in DS Agile have been introduced to inform the operators of “abnormal” or “special”
events or other miscellaneous events which must absolutely not be overlooked.
OI/EN FT/C57 FT-47

3.3.1.1 TYPES OF ALARMED DATA

An alarm can be generated by the following events:
• any Binary Input (SP, DP, MP, SI, IED input, Groups) state change
• any Measurement state change
• any TPI state or value change
• any metering state change
associated with “the reason for change” of these events.
For example, the OPENING of a circuit breaker can be un-alarmed if the state change is caused by a
control, and alarmed if it is due to another reason.
Furthermore, an alarm can be associated with a control acknowledgement. In this case, the alarm is
considered as “spurious”.
3.3.1.2 ALARM STATES DEFINITION

An alarm is generated by an event (i.e. a particular datapoint in a state defined during the configuration
process as “to be alarmed”).
While this event is still present (i.e. the previous particular datapoint is still in the same state) the alarm is
“active”.
When this event disappears (i.e. the previous particular datapoint is now in another, un-alarmed, state) the
alarm becomes “inactive”.
An existing alarm (active or inactive) can be acknowledged by an operator from the SCP via DS Agile OI to
indicate that it has been taken into account.
An alarm can have the following states:
• inactive: no transition, no event

• active-acknowledged: the cause is still present but the active state has been taken into account by the
operator
• active-unacknowledged: the cause is still present and the active state has not been taken into account
by the operator
• inactive-unacknowledged: the cause has disappeared but the inactive state has not been taken into
account by the operator (only available for events alarmed on both appearance and disappearance)
• inactive-acknowledged: the cause has disappeared and the inactive state has been taken into account
by the operator
• inactive-active-unacknowledged: the cause has disappeared but the active state (previous state) has
not been taken into account by the operator
FT-48 OI/EN FT/C57

3.3.1.3 PARAMETERS ASSOCIATED WITH AN ALARM

The following user-selectable parameters can be associated with each alarm definition. The values are set
during the configuration process and can be specific to each defined alarm:
• immediate or delayed:
an “immediate” alarm is displayed as soon as it has been detected.
a “delayed” alarm is displayed only after a user-selectable time-delay following its detection (the
event associated with the alarm must remain present during the time-delay; if not, the alarm will be
not displayed) ; this delay is in the range of 1 to 120 seconds and can be set to particular value for
each “delayed” alarm.
• gravity level: this level is defined for each alarm allowing a hierarchical classification to deal with the
urgency of the events; the gravity level value can be: 0, 1, 2, 3, 4 or 5, 5 being the most severe and 0
meaning that there is no gravity level.
• alarm generated:
only when the “associated” event appears
or
when the “associated” event appears and when it disappears
In this case the “delayed” parameter is taken into account only when event appears; when the event
disappears the new state of the alarm is displayed immediately.
• alarm clearing mode:

Manual: the clearing is executed only after an operator request (at SCP level via OI); this clearing
command is only allowed on inactive-acknowledged alarms.
Automatic: an alarm is automatically cleared when it reaches the appropriate state
• audible or not when detected by the system

• if audible:
1 immediate or delayed (after alarm display)
“Immediate” means that the audible alarm is triggered simultaneously with the alarm display on the
HMI (even the display was itself delayed after the appearance of the alarmed event).
“Delayed” means that the audible alarm is triggered after a user selectable time-delay starting with
the display of the alarm on the HMI; this delay can be set from 0 to 300 seconds.
2 automatic or manual acknowledgement of its audible signal (this parameter is defined at a the system
level, i.e. all alarms have the same “automatic / manual audible acknowledgement” parameter):
“automatic” means that the audible signal stops, without any operator action, after a user-settable
time-delay (range: 1 to 60 seconds)
“manual” means that only an operator action can stop the audible signal
Note 1: The acknowledgement of the audible signal affects only the “audible aspect” of the alarm and does not mean
acknowledgement of the alarm as described in the previous section; i.e. after an “audible acknowledgement” (automatic
or manual) the alarm is still displayed in the alarm list as a “not acknowledged” alarm.
Note 2: A klaxon may be attached to the audible alarms on a per voltage level basis.
Note 3: Audible alarms are not managed in Bay Local OI. An external klaxon cannot be associated to the audible
alarm.
OI/EN FT/C57 FT-49

3.3.2 ALARM PROCESSING
3.3.2.1 PROCESS DESCRIPTION (STATE TRANSITIONS)

3.3.2.1.1 Introduction
An alarm can, for example, be associated with each state of each datapoint.
Depending on the configuration a datapoint can have several different associated alarms with the
corresponding different gravity levels; e.g. a switching device position with three alarmed states:
“OPEN” (gravity level 1)
“JAMMED” (gravity level 2)
TOGGLING” (gravity level 2)
(the state “CLOSED” is not alarmed).
A parameter, set during the configuration process and global for the whole system, manages the state
transition process. Depending on its value, this parameter allows the simultaneous display (*) for a particular
datapoint of:
• one alarm for each state (“state-based” alarm processing)

• only one alarm for each gravity level (“gravity level-based” alarm processing): the previous one is
replaced by the current one with same gravity level
• only the last alarm (“data-based” alarm processing): the previous one is replaced by the current one
(*) “simultaneous display” means that different alarms associated with the same datapoint may potentially be
present simultaneously in the alarm list. In any case, all alarms managed in DS Agile are single instances.
Additionally, a fourth type of alarm processing is added for the spurious alarm.
These four types of alarm processing are described in the following sections (the dotted lines in the diagram
below represent the paths used only in case of manual clearing).
All the types of alarm processing are defined in the DS Agile OI. Only the “data-based” alarm processing
(type 3) is defined in the MiCOM computers.
3.3.2.1.2 Type 1: “State based” alarm processing
In this processing type all the different alarms associated with a datapoint can potentially be simultaneously
displayed, it means that for a particular datapoint more than one alarm event associated with this datapoint
may exist in the alarm list.
According to the previous example, the three alarmed states can be simultaneously displayed for the
switching device: e.g. “JAMMED” state (not acknowledged by the operator) followed by “OPEN” state (not
acknowledged by the operator) and finally “TOGGLING” state.
FT-50 OI/EN FT/C57

Event alarmed on appearance only:
Alarm inactive
/ cleared
0
AL+
Alarm active-
unacknowledged
AL- (auto)
1
ACK AL- AL+
Alarm active- Alarm inactive-

acknowledged active-
unacknowledged
2 3
AL- ACK
ACK (auto)
Alarm inactive-
acknowledged
CLEAR AL+
4
S0447ENa
OI/EN FT/C57 FT-51

Event alarmed on appearance and disappearance:
Alarm inactive
/ cleared
0
AL+
Alarm active-
unacknowledged
1
AL- AL+
AL+
ACK Alarm inactive-

active-
unacknowledged
3
ACK

acknowledged unacknowledged
2 AL- 5
ACK
ACK (auto)
Alarm inactive-
CLEAR acknowledged AL+
4
S0448ENa
Transition events:
• AL+ alarmed event appearance
• AL- alarmed event disappearance
• ACK operator acknowledgement of the alarm
• CLEAR operator clearing of the alarm
Note:
(AL-) “alarmed event disappears” means that the associated data is now in another state which can be alarmed or not
(if alarmed, an additional alarm associated with the same data appears in the alarm list).
Transition conditions:
• auto Automatic clearing
FT-52 OI/EN FT/C57

Transitions description:
The transition from alarm state "0" (in this state the data may have another unacknowledged alarmed state in
the list of alarms) to alarm state "1" is effective when the alarmed event appears (AL+).
The alarm state transitions "1 → 2", "3 → 4" and “5 → 3” are effective upon operator acknowledgement
actions. The time stamp of the alarm is unchanged.
The alarm state transitions "1 → 3" and “1 → 5” are effective when the alarmed event disappears (AL-). The
time stamp of the alarm is modified.
The alarm state transition "2 → 4" is effective when the event disappears (AL-) the alarm being configured to
be activated only "on appearance of the event". The time stamp of the alarm is modified.
be activated "on appearance and disappearance of the event". The time stamp of the alarm is modified and
the alarm will have to be acknowledged again.
The alarm state transitions "3 → 1", "4 → 1" and “5 → 1” are effective when the previous alarmed event
appears again (AL+). The alarm becomes active-unacknowledged. The time stamp of the alarm is modified.
be activated only "on appearance of the event" and “to be cleared automatically”. The alarm is suppressed
from the alarm list.
The alarm state transition "3 → 0" is effective on operator acknowledgement only if the alarm associated with
the event is configured as “to be cleared automatically”. The alarm is suppressed from the alarm list.
The alarm state transition "4 → 0" is effective on operator clearing action. The alarm is suppressed from the
alarm list.
3.3.2.1.3 Type 2: “Gravity level-based” alarm processing
In this process only the alarms with different gravity levels associated with a datapoint can potentially be
simultaneously displayed (the previous one with the same gravity level is replaced by the current one).
According to the previous example, two alarmed states can be simultaneously displayed for the switching
device: e.g. “JAMMED” or “TOGGLING” state (the last one not acknowledged by the operator) and “OPEN”
state.
OI/EN FT/C57 FT-53

Alarm inactive
/ cleared
0
AL+
Alarm active-
=LV+ unacknowledged AL+ or =LV+
AL- (auto)
1
=LV+ ACK AL-

unacknowledged
2 3
AL- ACK
ACK (auto)
Alarm inactive-
acknowledged
CLEAR AL+ or =LV+
4
S0449ENa
FT-54 OI/EN FT/C57

Alarm inactive
/ cleared
0
=LV+ AL+
AL+ or =LV+
Alarm active-
unacknowledged
=LV+
1
AL+
AL-
or
=LV+
ACK Alarm inactive-
active-
unacknowledged
5
ACK

2 AL- 3
ACK
ACK (auto)
Alarm inactive-
acknowledged
CLEAR AL+ or =LV+
4
S0450ENa
Transition events:
• AL+ (current) alarmed event appearance
• AL- (current) alarmed event disappearance
• =LV+ other alarmed event appearance with same gravity level (for the same data); after this
transition it becomes the “current” alarmed event
Note: In that case “alarmed event disappears (AL-)” means that the associated datapoint is now in another state
which can be alarmed or not with a different gravity level (therefore an additional alarm associated with the same
datapoint appears in the alarm list). The time stamp of the alarm is modified.
OI/EN FT/C57 FT-55

The state transitions are similar as those described in the previous chapter except for the following points:
• when starting the state processing from the state "0", the datapoint may already have other
unacknowledged associated alarms with different gravity levels in the list of alarms.
• the alarm state transitions "1 → 1" and "2 → 1" are effective when the state of the datapoint
associated with the alarm switches from a state which is flagged to be alarmed with a particular gravity
level to another state which is also flagged to be alarmed with the same gravity level (=LV+). In this
case the active alarm stays active but the time-stamp of the alarm is changed. The new alarm time
stamp corresponds to the last associated data state change. The alarm becomes unacknowledged if
not already unacknowledged.
• the alarm state transitions "3 → 1", "4 → 1" and “5 → 1” are effective when the previous alarmed event
appears again (AL+) or when another state which is also flagged to be alarmed with the same gravity
level (=LV+) appears. The alarm becomes active-unacknowledged. The time stamp of the alarm is
modified.
3.3.2.1.4 Type 3: “Data-based” alarm processing
In this processing type only one alarm (the last one) associated with a state change of a datapoint is
displayed. The previous one (concerning the datapoint) is replaced by the current one.
According to the previous example, only one from the three alarmed states can be displayed for the
switching device: e.g. JAMMED or TOGGLING or OPEN state (the last one to appear).
Alarm inactive
/ cleared
0
AL+
AL+
Alarm active-
unacknowledged AL+
AL- (auto)
1
AL+ ACK AL-

unacknowledged
2 3
AL- ACK
ACK (auto)
Alarm inactive-
acknowledged
CLEAR AL+
4
S0451ENa
FT-56 OI/EN FT/C57

Alarm inactive
/ cleared
0
AL+ AL+
AL+
Alarm active-
unacknowledged
AL+
1
AL+
AL-
ACK Alarm inactive-

active-
unacknowledged
5
ACK

2 AL- 3
ACK
ACK (auto)
Alarm inactive-
acknowledged
CLEAR AL+
4
S0452ENa
Transition events:
• AL- alarmed event disappearance
Note: In that case “alarmed event disappears (AL-)” means that the associated datapoint is now in another state
which is not alarmed. The time-stamp of the alarm is modified.
OI/EN FT/C57 FT-57

The state transitions are similar to those described in the previous section except for the following points:
• when starting the state processing from the state "0", the datapoint cannot already have another
unacknowledged associated alarm in the list of alarms.
• the alarm state transitions "1 → 1" and "2 → 1" are effective when the state of the datapoint
associated with the alarm switches from a state which is flagged to be alarmed with any gravity level
to another state which is also flagged to be alarmed with any gravity level (AL+). In this case the active
alarm stays active but the time-stamp of the alarm is changed. The new alarm time-stamp
corresponds to the last associated datapoint state change. The alarm becomes unacknowledged if it is
not already so.
• the alarm state transitions "3 → 1", "4 → 1" and “5 → 1” are effective when the previous alarmed event
appears again or when another state which is also flagged to be alarmed with any gravity level
appears (AL+). The alarm becomes active-unacknowledged. The time-stamp of the alarm is modified
3.3.2.1.5 Type 4: “Spurious” alarm processing
Spurious alarms are defined for events which appear but never disappear (control acknowledgement for
example).
Alarm inactive
/ cleared
0
AL+
Alarm active-
unacknowledged
1
(1)
Alarm inactive-
active-
unacknowledged ACK (auto)
3
ACK
Alarm inactive-
acknowledged
CLEAR
4
S0453ENa
FT-58 OI/EN FT/C57

Transition events:


The transition from alarm state "0" to alarm state "1" is effective when the alarmed event appears (AL+). It
then switches immediately to state “3” ((1) transition) from which the alarm can be acknowledged.
3.3.2.2 ACKNOWLEDGEMENT
An operator can acknowledge an existing alarm from the SCP or BCP to indicate that it has been taken into
account. The various interfaces to execute these operations are described later in this document.
The acknowledgement of alarms by an operator can be globally configured as to be printed or not printed.
Moreover, the destination Log Book printer can also be chosen by configuration.
3.3.2.3 CLEARING
Whatever the clearing mode is, the clearing of an alarm is immediately taken into account everywhere it is
involved: suppression from the alarm list, suppression from the last alarms window (if previously present),
update of the new graphical state in all the views where it is displayed.
Automatic Clearing:
An alarm can be configured as “to be cleared automatically”. It means that when this alarm reaches the
appropriate state, it is cleared automatically without any operator action. The cases of “automatic clearing”
are:
• the alarm is in the active-acknowledged state and the alarm disappears (for event alarmed on
appearance only)
• the alarm is in the inactive-active-unacknowledged state and the operator acknowledges it (for event
alarmed on appearance only and spurious alarm)
• the alarm is in the inactive-unacknowledged state and the operator acknowledges it (for event alarmed
on appearance and disappearance)
This feature can be configured on a per gravity level basis and on a per alarm basis; e.g.: all the alarms with
a gravity level lesser than 4 can be “globally” configured as to be cleared automatically while the alarms with
a gravity level of 4 and 5 can be individually configured to be or not to be cleared automatically.
Operator Request Clearing:
An alarm which is not configured as “to be cleared automatically” has to be cleared by an explicit operator
action (this action being only possible when it is in the “inactive-acknowledged” state). Otherwise it remains
present in the alarm list and in the different graphical views where it is displayed.
Clearing an alarm does not require any particular operator access right, other than the "acknowledge right".
The various interfaces to execute these operations are described later in this document.
As for acknowledgement done by an operator clearing of alarms by an operator can be configured as to be
printed or not printed.
A global clearing procedure, which allows to clear all “inactive-acknowledged” alarms in a single operation,
will be provided.
OI/EN FT/C57 FT-59

3.3.2.4 AUDIBLE ALARMS

An audible alarm can be associated with the “unacknowledged” states of an alarm. This facility is
configurable on a per gravity level basis and on per alarm basis (e.g. all the “unacknowledged” alarms with a
gravity level 2 or 3 can be configured “globally” to trigger an audible alarm, while only some of the other
gravity level “unacknowledged” alarms can have the same characteristic).
If the audible alarm is configured as immediate, it is triggered immediately after the appearance of the
unacknowledged state.
The audible alarm can be “delayed”, allowing the operator to acknowledge the alarm before the audible
alarm is triggered.
When triggered an audible alarm can be stopped at DS Agile OI level by three different means:
• if it is configured with an automatic acknowledgement of its audible signal, the audible signal stops,
without any operator action, after a user-selectable delay (range: 1 to 60 seconds)
• by clicking the tool bar stop horn button , which acknowledges the audible alarms (klaxons). This
“audible acknowledgement” can be done from any DS Agile OI station. It is global (i.e. it applies to all
the audible alarms present in the substation); it concerns only the audible aspect of the alarm (i.e. the
alarm state remains the same in the alarm list: “unacknowledged”)
• when the operator acknowledges all the alarms (which have an audible attribute) in the alarm list in
the OI or on the substation computer via its “local” HMI
From a hardware point of view, depending on the different DS Agile Systems architectures, the audible alarm
can be sounded:
• by a beeper on each PC on which the HMI software is running (in this case, only one “klaxon” exists,
i.e. there cannot be a klaxon for each voltage level), using a “.wav file”
or
• by a buzzer activated by relays controlled by each substation computer and by the PC's beeper
An operator can stop the klaxon using a dedicated icon displayed on the HMI.
All the items previously described in this chapter apply to a substation in Local Control Mode.
During the configuration process a parameter can be set, allowing a specific behavior for audible alarms
when the substation is in Remote Control Mode.
If not set, the behavior is the same both in Remote Control Mode and in Local Control Mode, as previously
described.
If the parameter is set to have a specific behavior when the substation is remotely controlled, the audible
alarms are treated as follows:
1 When the substation control mode changes from Local to Remote, the audible alarms are
automatically disabled: all the audible signals stop. This feature prevents useless triggering of audible
signals in remotely controlled substations without local operators.
2 When the substation control mode changes from Remote to Local, the audible alarms are
automatically re-enabled: all the audible alarms still present will start generating audible signals again.
FT-60 OI/EN FT/C57

3.4 MANUAL OPERATIONS ON DATAPOINTS

For binary inputs, tap position indicators and measurements, it is possible to carry out manual operations.
There are five types of Binary inputs:
• Single Point: derived from one Digital input

• Double Point: derived from two Digital inputs
• Multiple Point: derived from N Digital inputs
• System Input: information related to the control system, to configurable and built-in automations or to
electrical processes but without acquisition possibilities
• Group: logical combination of BIs

Manual operations are available only if they have been defined during the configuration process. There are
three types of manual operations:
• Suppressing
• Substituting
• Forcing
Two interfaces allow the operator to carry out these operations:
1 The SBO control window
The SBO control window can only perform FSS operations on datapoints managed by a
DS Agile C26x connected to the same network as DS Agile OI.
Via the FSS tab, it is possible to directly force, suppress, substitute the status of the controlled switching
device.
OI/EN FT/C57 FT-61

2 The FSS viewer
The FSS viewer can perform FSS operations on datapoints managed by a DS Agile C26x
or a DS Agile Gateway.
The FSS viewer is a mimic that allows the operator to suppress, force or substitute the state on input
datapoints. Specific viewers are ActiveX views, they have the same “look and feel” as the Alarm / State /
Event viewer (tool bar, browser, datapoints list). It is composed of:
• an FSS (Forceable/Substitutable/Suppressible) datapoint list

• a Browser (optional, identical to the Alarm browser)
• a Toolbar (not optional)
In the following example, the three FSS viewers have been configured:
Toolbar
"Force"
FSS Viewer
Toolbar
"Suppress"
FSS Viewer
Toolbar
"Substitute"
FSS Viewer
Browser Datapoint List S1003ENb
The Force / Suppress / Substitute functions must be defined in separate viewers.

The toolbar is used to:
• to print the displayed FSS datapoint lists

• to launch the window dedicated to datapoint forcing or datapoint substituting or datapoint suppressing.
FT-62 OI/EN FT/C57

3.4.1 DATAPOINT SUPPRESSION/UNSUPPRESSION

A datapoint can be suppressed by a command issued from an operator. The datapoint takes the
SUPPRESSED state and no subsequent change of state on the suppressed datapoint can trigger any
action, e.g. display, alarm, transmission until unsuppression. When the operator unsuppresses the datapoint,
it reverts to its actual state.
3.4.1.1 DATAPOINT SUPPRESSION/UNSUPPRESSION VIA THE SBO WINDOW

This interface is available only if an SBO control box associated with the corresponding datapoint has been
configured.
To suppress a datapoint the user must:
1 Open the SBO control box corresponding to the datapoint and select the FSS tab.
2 Click Suppress. No acknowledgement window nor error message is displayed, but when the
datapoint status has changed to suppressed, the Suppress button is replaced by the Unsuppress
button. The window remains opened. The user can either close the window or unsuppress the
datapoint.
To unsuppress the datapoint, the user must:

OI/EN FT/C57 FT-63

2 Click Unsuppress. Neither acknowledgement window nor error message is displayed, but when the
datapoint status has changed to its current state, the Unsuppress button is replaced by the Suppress
button
3.4.1.2 DATAPOINT SUPPRESSION/UNSUPPRESSION VIA THE FSS SPECIFIC VIEWER

The FSS specific viewer allows to suppress/unsuppress one datapoint.
To suppress/unsuppress a datapoint the user must:
1 Select one datapoint to suppress in the FSS list by clicking in the check-box.
2 Open the suppress/unsuppress window by clicking the object editor button

This window displays the datapoint reference, reminds the type of manual operation that it allows: suppress,
and displays the datapoint value: "1" if the datapoint is suppressed, "0" in the other cases.
3 Enter the value of the operation in the blue area: "1" to suppress and "0" to unsuppress. The Reset
button deletes the value entered.
4 Send the command by clicking Control. No acknowledgement window nor error message is
displayed, the operation value is reset, the datapoint status can be viewed in the Read value box.
Without closing the suppress window it is possible to change the datapoint by selecting another check box
on the FSS viewer.
FT-64 OI/EN FT/C57

3.4.2 DATAPOINT SUBSTITUTION/UNSUBSTITUTION

A datapoint can be substituted to a state manually set by an operator (state “SUBSTITUTED xxx”).The
datapoint remains in the state determined by the operator until he/she unsubstitutes it. When a datapoint is
substituted, no changes of state are transmitted, and computations, for instance groupings, are made with
the substituted state. When the datapoint is unsubstituted, the current state is transmitted to higher control
levels and subsequent state changes are transmitted again.
3.4.2.1 DATAPOINT SUBSTITUTION/UNSUBSTITUTION VIA THE SBO WINDOW

configured.
To substitute a datapoint the user must:
2 Select the substitution state, so that the Substitute button is available.
3 Click the Substitute button. Neither acknowledgement window nor error message is displayed, but
when the datapoint status has changed to substituted, the Unsubstitute button is activated. The
window remains open. The user can either close the window or unsubstitute the datapoint. When a
datapoint is substituted, it is possible to substitute it again with a new value.
To unsubstitute the datapoint, the user must
2 Click the Unsubstitute button. Neither acknowledgement window nor error message is displayed, but
when the datapoint status has changed to its current state, the Unsubstitute button is inactivated.
OI/EN FT/C57 FT-65

3.4.2.2 DATAPOINT SUBSTITUTION/UNSUBSTITUTION VIA THE FSS SPECIFIC VIEWER

The FSS specific viewer allows to substitute/unsubstitute one datapoint.
To substitute/unsubstitute a datapoint the user must:
1 Select one datapoint to substitute in the FSS list by clicking in the check-box.
2 Open the substitute/unsubstitute window clicking the object editor button

This window displays the datapoint reference, reminds the type of manual operation it allows:
substitute/unsubstitute, and displays the datapoint value: "1" if the datapoint is substituted, "0" in the other
cases plus in case of substitution the substitution value.
3 Enter the value of the operation in the blue area: "1" to substitute and "0" to unsubstitute. In case of
substitution, substitution value must be selected via a drop-down menu. The Reset button deletes the
values entered.
displayed, the operation value is reset, the datapoint status can be viewed in the Read Value area.
FT-66 OI/EN FT/C57

Without closing the substitute window it is possible to change the datapoint by selecting another check box
on the FSS viewer.
3.4.3 DATAPOINT FORCING

When an information is invalid (i.e. SELFCHECK FAULTY, TOGGLING, UNDEFINED or UNKNOWN), it can
be manually forced by an operator (state “FORCED xxx”). This feature is similar to the substitution but the
information is automatically updated when valid information is available again. A SUPPRESSED or
SUBSTITUTED datapoint cannot be forced.
Forcing could also be automatic: in this case, the invalid information automatically takes the state defined in
configuration.
3.4.3.1 DATAPOINT FORCING VIA THE SBO WINDOW

configured.
To force a datapoint the user must:
2 Select the forcing state, so that the Substitute button is available. The Force button is available only
if the datapoint is in an invalid state.
OI/EN FT/C57 FT-67

3 Click Force. No acknowledgement window nor error message is displayed, but when the datapoint
status has changed to forced, the Force button is disabled. The window remains open. The user can
choose to close it.
3.4.3.2 DATAPOINT FORCING VIA THE FSS SPECIFIC VIEWER

The FSS specific viewer allows to force one datapoint.
To force a datapoint the user must:
1 Select one datapoint to force in the FSS list by clicking in the check-box.
2 Open the force window by clicking the object editor button

This window displays the datapoint reference and reminds the type of manual operation it allows: force, and
displays the datapoint value: "1" if the datapoint is forced, "0" in the other cases and the forcing value.
3 Enter the value of the operation in the blue area: "1" to force and "0" to keep. The forced value must
be selected via a drop-down menu. The Reset button deletes the values entered.
displayed, the operation value is reset, the datapoint status can be viewed in the area Read value.
FT-68 OI/EN FT/C57

Without closing the force window, it is possible to change the datapoint by selecting another check box on
the FSS viewer.
3.5 MEMO FUNCTION

This function allows the operator to attach short memos to the display to a bay, a module (i.e. a switching
device or any primary devices) or a piece of equipment where this is useful and configured, assuming that
the operator has the appropriate access rights.
The memos contain the following information:
• name of the bay / module / equipment to the memo is or was attached

• user name of the operator who creates the memo
• date and time of creation
• user name of the operator who deletes the memo
• date and time of deletion
• text of the memo (free text)
A global memo status, in the general tool banner, gives a general indication on all current memos:
Icon animation Meaning
There is not yet a "Memo"
No "Memo" is still active, but there is one deleted
At least a "Memo" is now active and can be read
The memo is undefined (downgraded case)
These animations are also available for each memo.

A memo placed on one Operator Workstation is visible on all other Operator Workstations. Only one memo
may be attached to a module or equipment, and on a per mimic basis (i.e. a memo attached to a module in a
mimic will be not visible in another mimic in which the same module appears).
To create a new memo the user must:
1 Click on the memo icon where he/she wants place the text . The following window is then
displayed.
OI/EN FT/C57 FT-69

2 Click in the text box and enter the text.
3 Save the memo by clicking Save. The Creator and Date and time of creation fields are updated with
the user name and the current date.
FT-70 OI/EN FT/C57

4 Close the window. The memo icon has been changed to indicate that a memo is present: .
To delete a memo the user must:
5 Click on the memo icon he/she wants to delete . The following window is then displayed:
6 Click Suppress. The text of the memo is still present but the Deletor and Date and time of
destruction fields are respectively updated with the user name and the current date.
OI/EN FT/C57 FT-71

7 Close the window. The memo icon has been changed to indicate that a memo has been suppressed:
.
To modify a memo the user can either first suppress the memo and then write a new memo, or directly
modify the text of the memo. In both cases, saving the memo is allowed only if the text of the memo has
been changed (this is indicated in the status of the memo viewer field with the text “The memo has
changed”). When the user saves the memo, the Creator and Date and time of creation fields are updated
and if the memo has been first suppressed the Deletor and Date and time of destruction fields are deleted.
3.6 DISCORDANCE MANAGEMENT

The discordance is the fact that the state of a switching device has changed without reason (i.e. not following
a control from DS Agile).
A graphical representation of the discordance can be associated with a switching device during the
configuration process (a flashing triangle in IEC for example).
This graphical representation appears when the device presents a discordance. It disappears when the
associated alarm (in the alarm viewer) has been acknowledged (a datapoint associated with a discordance
must therefore be alarmed).
3.7 TIME STAMP

The time stamp is a digital value representing the date of a data point, command or another type of
information on the DS Agile system.
The time stamp is a date, stored on 8 bytes, with an accuracy of 10-7 second. It is propagated in the refresh
data flow and in the control data flow. A quality is defined for the time stamp; it is the time stamp validity field.
3.7.1 TIME STAMP SET BY THE SOURCE

The source sets the time stamp. In some particular cases, the source might be overridden by the S2K server.
3.7.2 TIME STAMP SET BY THE S2K SERVER

Reminder: the datapoint generated by the S2K server is time-tagged by itself.
Two cases can be encountered:
1. The object may have been already refreshed with a later date (“jump backward to the past”). This is
applicable to IED and S2K datapoints.
FT-72 OI/EN FT/C57

The S2K server sets the time stamp value by adding 1 ms to the previous event. The time validity is not
synchronized. To comply with the chronology, the time-stamp must be incremented whenever the object is
refreshed.
2. Object refreshed as a result of a local control operation: the S2K server sets the time stamp value and is
itself the source.
3.8 DATA LOGGING

The Data Logging function is the logging of DS Agile's information on printers. Three types of printers are
available:
• the SOE printers (Sequence Of Event)

• the LB printers (Log Book)
• the HC printers (Hard-Copy)
SOE and/or Log Book printers can be managed using a parallel or an Ethernet network printer.
Mixing parallel and network printers is not permitted.
DS Agile manages: a maximum of two redundant SOE printers (i.e. four SOE printers) and two redundant LB
printers (i.e. four LB printers) at the control system level, managed by the OI. They can be serial or network
printers.
Hard-copy printers allow printing screenshots of the Operator Workstation and reports.
Only text in the OI primary language, as defined in the SCE, can be printed out.
3.8.1 PRINTING MECHANISMS

The printers are managed in a real-time printing mode.
DS Agile printers mechanisms at system level ensure:
• Chronological printing: all synchronized information is printed in chronological order. A lag time is
configured to allow information sorting.
• printing reliability: no data is lost if the printer remains unavailable for a duration less than the printer’s
buffer length
• Printing availability, provided by printer redundancy. The first printer is designated “Main” printer, and
the second is designated “Spare” printer. The “Main” printer performs all printing operations whenever
it is available. If the “Main” printer fails, the “Spare” printer takes over and continues to print events
even if the “Main” printer becomes available again. The printed events are recorded during the
recovery length period (defined in configuration as a minimum value, this period must be consistent
with the error detection time of the printer spooler). If the current printer switches to faulty mode, the
spare printer prints all the events recorded during the recovery length period again.
Recovery Length
latency
Printers Buffer Length Data flow
S0395ENa
Events are printed with their time-stamp and a complete description (location and event description). Time-
stamping is done by the device that detected the event (time-stamping at the source).
OI/EN FT/C57 FT-73

Note1: In case of DS Agile OI Server redundancy, network printers are mandatory to avoid data loss in case one of the
two DS Agile OI Servers shuts down.
Note 2: In case of a Bay Local OI, all the information can be archived, but not printed (i.e. the Bay Local OI does not
manage printers).
3.8.2 PRINTING FORMAT

Header & Footer
A header and a footer can be printed on each page. They are composed of two optional lines, separated
from the events by a blank line.
The structure of each header / footer lines is defined in configuration, using the following properties:
• Site name
• Printer name
• Page number
• Free text
The page number is in the range [1..999]. It is reset to 1 after reaching 999, each new day.
Header line 1
Header line 2
<blank line>
<SOE>
<blank line>
Footer line 1
Footer line 2
S0454ENa
3.8.3 SEQUENCE OF EVENT (SOE)

Only Binary Inputs attached to the electrical process can be printed on the SOE printers (SP, DP and MP are
allowed, SI and Groups are not). The list of BIs to print is defined in configuration.
The list of BI states that will be printed can also be defined in configuration. States that will be not printed on
the SOE printers will be not printed on the LB printer (if the associated BI is also printed on the LB). A printed
information will be also archived.
The 5 following BI properties can be printed. Each property is separated from the other by one blank
character. The position of each property on the printed line (i.e. position 1, 2, 3, 4 or 5) is defined in
configuration:
• Chronology – 1 character that gives the “out of chronology” status of an event: “<blank>” if the event
is printed in the chronology, “C” if it is not.
• TimeStamp – 23 or 25 characters: the following formats are allowed:

<S> DD/MM/YY hh:mm:ss.mmm
FT-74 OI/EN FT/C57

<S> YY/MM/DD hh:mm:ss:mmm

<S> MM/DD/YY hh:mm:ss:mmm
<S> DD/MM/YYYY hh:mm:ss.mmm
<S> YYYY/MM/DD hh:mm:ss:mmm
<S> MM/DD/YYYY hh:mm:ss:mmm
the <S>character gives the synchronzed / not synchronized status of an event: “<blank>” for
synchronized, “*” (configurable) for not synchronized – It is issued from the source time stamping.
• Origin - 67 characters:
For BIs defined at the module level, the origin is <substation name>/<voltage level name>/<bay
name>/<module name>
For BIs defined at the bay level, the origin is <substation name>/<voltage level name>/<bay
name>
For BIs defined at the voltage level, the origin is <substation name>/<voltage level name>
For BIs defined at the substation level, the origin is <substation name>
Each <xxx name> is defined over 16 characters.
• ObjectName - 35 characters: contains the BI's name

• ObjectMessage - 16 characters: contains the BI's resulting state. Only the resulting states chosen in
configuration are printed. If the BI is also printed on LB, the same chosen states will be printed.
For example, one possible arrangement can be:
1 char. 23 or 25 char. 67 char. 35 char. 16 char.
Chronology TimeStamp Origin ObjectName EventMessage

S0397ENa
The selection of the SOE printer destination (1, 2, or both) is made by configuration on a per data basis.
3.8.4 LOG BOOK (LB)

The types of events can be:
• Binary inputs (SP, DP, MP, SI and Groups)

• Tap position indication
• Measurement
• Operator action:
Log-in and log-off,
Devices control
• Alarm acknowledgement / clearing

One or several types of events can be printed: the choice is made by configuration. The selection of the LB
printer destination (1, 2, or both, for printer at system level) is made by configuration on a per data basis.
The list of event states (for BI, Tap Position Indication and measurements) which will be printed can be
defined in configuration. A printed information will be also archived.
The 5 following properties can be printed. Each property is separated from the other by one blank character.
The position of each property in the printed line (i.e. position 1, 2, 3, 4 or 5) is defined in configuration:
OI/EN FT/C57 FT-75

• Chronology – 1 character: see section “SOE events”

• TimeStamp – 24 or 26 characters: see section “SOE events”
• Origin - 67 characters: for BI, TPI, measures, controls and alarms, the origin gives the access path to
the object (see section “SOE events”)
• ObjectName - 35 characters
• ObjectMessage – 16 characters. The format is "[CLIENT NAME – USER NAME]"
The Origin, ObjectName and ObjectMessage properties contain different indications depending of the
associated event type.
Printer Events Chronology TimeStamp Origin ObjectName ObjectMessage Comment

SOE, Time
Binary Input Chronology Origin BI Name BI resulting state
LB stamping
The value is
given only for
TPI in the
following state:
Tap Position Time
LB Chronology Origin TPI name TPI state and value valid, forced,
Indication stamping
substituted,
overrange,
threshold
violation
The value is
given only for
measure in the
following state:
Time Measure Measure state and
LB Measurement Chronology Origin valid, forced,
stamping name value
substituted,
overrange,
threshold
violation
Operator Name
Operator Log-in / Time Log-in
LB Chronology <blank> <blank>
Log-off stamping Operator Name
Log-off
Force, suppress
Time Select Control value and substitute
LB Control request Chronology Origin Control name
stamping Exec Control value requests are not
printed
Control Time Control
LB Chronology Origin Control name
acknowledgement stamping acknowledgement
Alarm Time
LB Chronology Origin Alarm name Acknowledgement
acknowledgement stamping
Time
LB Alarm clearing Chronology Origin Alarm name Clearing
stamping
Note 1: The labels for the Origin, ObjectName and ObjectMessage properties are defined in configuration, except for
labels in italic letters (these labels will be identical for all supported languages).
Note 2: In order to avoid printing valid measurement values, the valid states are tagged as “not printed” in configuration
FT-76 OI/EN FT/C57

3.8.5 MULTI-SCREEN SNAPSHOT TOOL

This function allows separate printing of screens in multi-screen configurations.
When launching the tool, a new popup window shows as many thumbnails as there are screens.
2-screen configuration
Each thumbnail includes a reduced image of a screen. All actions are accessible by right-clicking on the
thumbnail:
The action will be performed on the screen corresponding to the thumbnail, except for the Print all action
that prints all the screens.
Possible actions:
Action Description
A jpeg image of the captured screen is saved in the preconfigured directory. The name of the file
thus created is:
Save - DS AgileOI_screen<X>.jpg, if the Overwrite setting is set to true,
- DS AgileOI_screen<X>_<N>.jpg, if the Overwrite setting is set to false, where <X> is the screen
identifier, and <N> is used to avoid file overwriting
Print The corresponding screen is captured and a popup allows printer selection
The screen is captured, and a popup allows having a preview of the printed page before sending to
Print with Preview
printer
Refresh It refreshes the thumbnail of the corresponding screen
OI/EN FT/C57 FT-77

Action Description
All screens will be captured, and a popup allows printer selection. All screens are sent to printer,
Print All
one screen per page
3.9 DATA ARCHIVING

The Data Archiving function provides the history of DS Agile's information. DS Agile OI is in charge of central
archiving.
The choice of archived information is defined during the configuration.
3.9.1 GENERAL
The central archives are managed by an SQL Server 2005/2008 database.
Central archiving backup consists in transferring files to another location or onto another storage media
(disk, tape). The backup is made by the operator using Windows Backup tools.
The backup data can be restored then analyzed by the Archive Viewer.
The following picture shows the standard process for the Archive/Backup/Restore function:
Central Archive To-Be-Saved Archive Backup Archive Restored Archive Import into DB
(one site) Export Backup Restore
Manually Manually Import
Automatically Manually
Windows BACKUP Windows BACKUP
Data from the central Archive saved on a secure Data restored from a
archive corresponding storage (removable Disk or backup
to a period of time Tape), 10 mn after the
export
Historian
Historian restorized
Data Base Set of files
Set of files Data Base
S0456ENa
3.9.2 ARCHIVING
The archiving function consists in exporting automatically and periodically data in the form of .csv files into a
dedicated Archive directory: X\SharedWorkspace\ArchiveDSAgile where X is the Shared Workspace
path defined by the user during installation. The .csv files can be read using MS Excel. They are saved in a
directory named according to the corresponding period, for example 2005-03-25-00-
00_to_2005_03_26_00_00 means archived events between the 25th of March 0h00 and the 26th of March
0h00.
The scope of a backup archive is determined by the Time Range parameters defined during the
configuration process. It gives the number of days, of weeks or of months between archiving operations (the
minimum interval is one day).
The archive begins (and ends) at 0 hours/0 minutes/0 seconds:
• The first day of the Time Range if it is defined as a number of days,

• Sunday if the Time Range is defined as a number of weeks,
• The first day in a month if the Time Range is defined as a number of months.
The following table gives some examples:
Time Range To-Be-Saved Archive Backup at
30/10/2002 0:0:0 to 31/10/2002 0:0:0 31/10/2002 0:10:0
1 day 31/10/2002 0:0:0 to 1/11/2002 0:0:0
….. 1/11/2002 0:10:0
FT-78 OI/EN FT/C57

Time Range To-Be-Saved Archive Backup at

20/10/2002 0:0:0 to 3/11/2002 0:0:0 3/11/2002 0:10:0
2 weeks 3/11/2002 0:0:0 to 17/11/2002 0:0:0
….. 17/11/2002 0:10:0
1/10/2002 0:0:0 to 1/11/2002 0:0:0 1/11/2002 0:10:0
1 month 1/11/2002 0:0:0 to 1/12/2002 0:0:0
….. 1/12/2002 0:10:0
The ArchiveDSAgile directory is broken down as follows:
ArchiveDSAgile
XXX : Directory
Current Time Range 1 XXX : File
S2KHistorian
Historian
Table 1
Table 2
Table 3
Current Time Range 2

S0457ENb
Current Time Range directory:

This directory contains the data of the building archive for the Current Time Range.
There is one Current Time Range directory par Archives directory.
Example of Name: 2002-05-17-00-00_to_2002-05-19-00-00
3.9.3 BACKUP
Backup consists in transferring manually the archived file into the storage device (hard disk or tape) using
the Windows Backup tool. To carry out this operation the user must:
OI/EN FT/C57 FT-79

1 Click Start in the windows task bar to display the Start menu
2 Choose Run to display the run window and enter ntbackup then click OK.
In advanced mode the Windows Backup window is displayed:
3 Select the Backup tab

In the tree view show the ArchiveDSAgile directory and click on the check box to select the archive files
to backup.
DSAgile
4 Click Browse to select the backup media or file name
FT-80 OI/EN FT/C57

5 Click Open to accept the selection and close the browse window
DSAgile
6 Click Start Backup, a Backup Job Information window is then opened. Close the back-up window.
OI/EN FT/C57 FT-81

7 Click Start Backup, a Backup Progress window is then displayed.
8 Click Close once the backup is complete.

Once the backup is complete the user can suppress the archive file via Windows Explorer to avoid disk
saturation.
It is possible plan one or several backups using the Scheduled tab . In this case the user should choose to
backup the whole Archive DS Agile directory because the future archive directories have not yet been
created.
3.9.4 ARCHIVE RESTORATION

Archive restoration consists in transferring manually the archived file from the storage device (hard disk or
tape) to the DS Agile OI using Windows Back-up tool. To be able to be used (for example in archive viewer),
the restored archives have to be placed in a shared directory which sharing name is “ToRestore”.
Therefore, before restoring the archives, the user must create the archive restoration directory (for example
C:/To restore) and share it. To share it, the user must
1 Right-click on the created directory in Windows Explorer to display contextual menu
FT-82 OI/EN FT/C57

Select Sharing…. The share window is then displayed.
1 Select Share this folder, then enter ToRestore in the Share name field, and click OK.
Once the archive directory is created, the user can restore the archives. To carry out this operation the user
must:
2 Click Start in the windows task bar to display the Start menu
3 Choose Run to display the Run window and enter ntbackup then click OK.
The Windows Backup window is then displayed
OI/EN FT/C57 FT-83

4 Select the Restore tab. The different backups carried out are then displayed (refer to the information
backup window: section 3.9.3 Backup, item 8).
5 Using the check boxes, select the archive to restore. Only the archives corresponding to one media
can be restored at a time.
DSAgile
FT-84 OI/EN FT/C57

6 Select the location where the archive is going to be restored by selecting an alternate location. An
additional box is then displayed to select the location. The user can use the browser to select the
archive restoration directory.
DSAgile
7 Click Start Restore: a Confirm Restore window is then displayed:
8 Click OK: the backup file name corresponding to the media is then displayed.
9 Click OK to start restoration: the Restore Progress window is displayed
OI/EN FT/C57 FT-85

10 Click Close once the restoration is complete.

The user can then carry out another restoration or close the NTbackup window.
3.9.5 ARCHIVE VIEWING

The archive viewer is the tool that allows to view archived information. It is part of the alarm viewer.
3.9.6 REPORTS GENERATION

Reports are files in Excel format. These reports for which the content and the format are defined during the
configuration are generated using specific buttons. These buttons can be configured in a mimic. When a
report is launched by clicking the relevant button, the system connects to the system's SQL database to
retrieve the archived values and generates the file in the directory where the SCADA server is installed. With
a standard installation, the location is C:\Program Files\USDATA\S2K\Reports\Exported. The
report file name is built using the following information:
• Report name
• Write date
• Write time
For example: Report1_07_13_2004_13_52_49.xls
For the description of template creation using crystal reports, refer to the appendix.
FT-86 OI/EN FT/C57

3.9.7 SUMMARY
Automatic Windows Backup

Service on DAT Reports
OI Client Button:
Restore archive for 1
specific day
Daily automatic .cvs export

Historian
Trends Viewer
Automatic computation
Min/Average/Max
Events Viewer
VTQ Table Mimic Animation

Daily removal of all data older 40 bytes/event State Viewer
than X day, with X = 10 to 400
Alarm Viewer
Events Table
2000 bytes/event (full name)
S2K Acquisition
Agency
S1004ENa
OI/EN FT/C57 FT-87

4 HOT REDUNDANCY CLUSTER

The OI Server Redundancy is managed through a set of 2 OI Servers named Cluster.
The OI Clients can be connected on one of the 2 servers. Their configurations are such as
• at least one client must have its preferred server declared as Server 1
• at least one client must have its preferred server declared as Server 2
(reminder: each client has in its configuration the list of servers on which it has to be connected. The first
server in this list is the “preferred” server and the client will try to connect on it first).
After the configured inactivity period (used for the automatic logout if configured), an OI Client which is not
connected to its preferred server has to try to re-connect to its preferred server. A pop-up is displayed on the
OI Client to indicate this re-configuration.
Client A Client B Client C
Server 1 Server 2
SQL Database SQL Database
IEC61850 Station Bus
S1005ENa
Both servers perform datapoints acquisition from IEC 61850-8-1 servers simultaneously, and the redundancy
mechanism allows consolidating each datapoint change on each server, to make sure that real-time data
and historical data are the same on both servers.
FT-88 OI/EN FT/C57

4.1 OI SERVER FUNCTIONS VS OI SERVER STATE

A Master OI Server can:
• Perform acquisition from the IEC 61850-8-1 network servers

• Be connected to OI Client(s)
• Performs archives (SQL Historian), alarm processing.
• Accept controls from the OI Client directly connected to it, as well as controls issued from OI Client
connected to the OI Server Slave, and manage them (propagation to the IEC 61850-8-1 network)
A Slave OI Server can:

• Propagate controls from OI Client connected to it up to the Master OI Server which will manage the
control. The Slave OI Server does not manage directly controls and does not propagate them to the
IEC 61850-8-1 network
A Standalone OI Server can:

• Accept controls from the OI Client(s) connected to it, and manage them (propagation to the
IEC 61850-8-1 network). In this case, there is no control uniqueness management as both Standalone
OI Server can send commands on the IEC 61850-8-1 network (the uniqueness check will be
performed at C26x level).
Each of the 2 OI Servers manages its own parallel printer(s). Shared printers are not supported in case of an
OI redundancy.
OI/EN FT/C57 FT-89

4.2 OI SERVER FAULT TOLERANCE STATE AUTOMATION

OI Servers are managed via a state algorithm. Both servers are marked in configuration (Server 1 and
Server 2).
START UP
STANDALONE WAIT
SWITCHING TO
STANDALONE
MASTER SLAVE
SHUTDOWN
S0619ENb
START-UP: Starting of the OI Server application
• START-UP Æ WAIT: The starting OI Server is Server 2 and Server 1 is in Start-up state.
• START-UP Æ SLAVE: The starting OI Server has found the other OI Server in standalone mode.
• START-UP Æ STANDALONE: Several possibilities:
The starting server is not configured for redundancy ,
The other server is not running,
The starting server is Server 1 and the server 2 is starting.
WAIT: Only Server 2 can be in this state. It is waiting for Server 1 to switch to STANDALONE state
• WAIT Æ SLAVE: Server 1 switches to STANDALONE state with the same configuration.
• WAIT Æ STANDALONE: Server 1 is lost.
STANDALONE: The server is running alone. If it is configured for redundancy, it is able to accept the
connection from the other server and to detect the twin master failure.
• STANDALONE Æ MASTER: The other server is successfully connected and the internal state transfer
is done.
• STANDALONE Æ SHUTDOWN: The server receives a synchronized shutdown notification.
FT-90 OI/EN FT/C57

MASTER: The server is allowed to generate controls. It checks periodically the health of the other server.
• MASTER Æ GOING TO STANDALONE: The other server is lost or is shutting down, and there
remains a consolidating message to process
• MASTER Æ SHUTDOWN: The server is shutting down.

SLAVE: The server is not allowed to generate controls. It checks periodically the health of the other server.
• SLAVE Æ GOING TO STANDALONE: The other server is lost or is shutting down, and there remains
a consolidating message to process.
• SLAVE Æ SHUTDOWN: the server is shutting down.

GOING TO STANDALONE:
• GOING TO STANDALONE Æ STANDALONE: The last consolidating message received before the
loss of the other servers has been processed.
SHUTDOWN: The server is shutting down.
Start-up – Both OI Servers are connected to the Ethernet network and visible:
Server 1 Server 2
START-UP START-UP
STANDALONE WAIT
MASTER SLAVE
S1006ENa
OI Server Master shutdown and restart:
Server 1 Server 2
MASTER SLAVE
PC halted
SWITCHING TO
STANDALONE
STANDALONE
PC started
START-UP
SLAVE MASTER
S1007ENa
OI/EN FT/C57 FT-91

Start-up – At least 1 OI Server is not connected to the Ethernet network:
Server 1 Server 2
START-UP START-UP
STANDALONE STANDALONE
Ethernet connection
Case 1: No OI Client connected to OI Server 1
SHUTDOWN
START-UP
SLAVE MASTER
S1008ENa
Start-up – At least 1 OI Server is not connected on the Ethernet network:
Server 1 Server 2
START-UP START-UP
STANDALONE STANDALONE
Ethernet connection
Case 2: OI Server 2 with less OI Clients connected than OI Server 1

(the number of connected OI Clients is switched between Servers)
SHUTDOWN
START-UP
MASTER SLAVE
S1009ENa
In order to limit the impact of a server disconnection upon the clients, the server with the highest number of
clients automatically becomes the Master.
FT-92 OI/EN FT/C57

4.3 OI SETTING
In HOT redundancy mode, OI Server Watch software must be active.
It is needed to automatically restart the remote server in case of a double STANDALONE state and in case
of the loss of one the servers.
4.4 OI SYSTEM DATAPOINTS

Each server has to manage its own system datapoints, which do not have to be consolidated between
servers (i.e. server 1 system datapoints are independent of server 2 system datapoints, but each server must
be aware of the status changes in the system datapoints of the other server). The IEC 61850-8-1 server
Status Link datapoint is considered as an OI Server datapoint.
4.5 UNKNOWN STATE MANAGEMENT

An IEC 61850-8-1 server can be seen as disconnected from one OI Server and connected from the other
OI Server. In that case, the datapoints from this IEC 61850-8-1 server are seen in their current state.
4.6 REDUNDANCY PERFORMANCE

The loss of the Ethernet connection between 2 OI Servers is detected in less than 40 seconds.
The re-connection time of an OI Client to an OI Server is less than 120 seconds (i.e. disconnection from a
server + connection to a new server).
4.7 CONSOLIDATED ARCHIVE FILES

With the introduction of Hot Redundancy a new kind of CSV (Archive) files are generated in the
\SharedWorkspace\ArchiveDSAgile\ directory. They contain the consolidated data issued from the
Hot Redundancy mechanism. Their names have the suffix “_c” (standing for “consolidated”) to distinguish
them from the legacy CSV files that are still generated but which contain only the data from the local server
without any data consolidation between servers.
List of new CSV files generated:
• S2KEventMsg_Table_c
• S2KVTQ6_VTQTimeTable_c
• S2KDaily_VTQTimeTable_c
• S2KMonthly_VTQTimeTable_c
• S2KAnnual_VTQTimeTable_c
OI/EN FT/C57 FT-93

ArchiveDSAgile\2008-10-09-00-00_to_2008-10-10-00\S2KHistorian\Historian
DSAgile
Since they are generated via SQL scripts and not by the OI Server, these files are not written at the same
time as the legacy CSV files, they ensure data consolidation first before doing any writing.
WARNING:
While restoring the CSV files, only the legacy CSV FILENAMES are taken into account
(without the ‘_c’ suffix). Therefore, if any file with a ‘_c’ suffix is present in the
“ToRestore”directory during the restoration, an error message will appear in the
ScadaTrace:
“Table name '… _c' is not in accordance with to be archived Historian tables”
The other files will be correctly restored. In order to restore all the consolidated CSV
files, the new files should first be renamed so as to match the legacy CSV filenames
(delete the suffix ‘_c’).
FT-94 OI/EN FT/C57

5 APPENDIX: USE OF CRYSTAL REPORTS
5.1 HOW TO CREATE A REPORT ?

A specific button must be available on the workstation in order to generate the report that can be launched
when operators needs it. The system will connect to the SQL database for retrieving archived measurement
values and for generating a file in a standard format. The report is designed by the operator at the time of
configuration using Crystal Reports.
The aim of this appendix is to explain how to do this.
Crystal Reports aims to create configurable reports. Configurable reports are created in 2 steps:
• Creation of the Report template using Crystal Report

• Creation of the Report launching button using the SCE
5.1.1 CRYSTAL REPORTS CONFIGURATION

The first step requires that Crystal Reports be installed on the same PC as DS Agile OI. The DS Agile
database (which contains configuration, mean values, …) must be downloaded in DS Agile OI. DS Agile OI
must be launched at least once in order to initialize the SQL tables.
1 Launch Crystal Reports:
2 Select the option Using the Report Expert to create a new report template from the Expert list and click
OK:
OI/EN FT/C57 FT-95

3 Select the Standard report and click OK:
FT-96 OI/EN FT/C57

4 Click Database.
5 Select More Data Sources, then Microsoft SQL Server:
OI/EN FT/C57 FT-97

6 Enter the server name (dsagileoi9 in the example) and the User ID (always sa), and select the
Historian database. Click OK:
The list of available SQL tables appears in the

More Data Sources\Microsoft SQL Server\<server name> directory.
FT-98 OI/EN FT/C57

7 Select the required table(s) and click Add. When all the required tables have been added, click Close.
Useful tables for the measurement mean values:
Contains the last 60 monthly (i.e. 5 years) characteristic measurement
S2KAnnual_VTQTimeTable
values (mean, max and min values)
Contains the last 430 daily (i.e. 15 months) characteristic measurement
S2KMonthly_VTQTimeTable
values (mean, max and min values)
S2KDaily_VTQTimeTable Contains the last 35-day archives of measurement mean values
Contains the label, the origin and the type (mean, max, min) of each
archived measurement.
S2KVTQDictionnary_Table
This table is compulsory when using the Annual, Monthly and/or Daily
tables
OI/EN FT/C57 FT-99

Useful tables for the events:

S2KEventGroup_Table Contains the origin label of the events
S2KEventMsg_Table Contains the label, the date and the states of each event
These 2 tables must be used when creating an event report template.

The following items give information concerning the report template creation based on monthly archived
mean values.
1 After selecting the tables S2KMonthly_VTQTimeTable and
S2KVTQDictionnary_Table, the following window appears:
Click Next>>.
2 Select the field(s) to display in the report and click Add->.
FT-100 OI/EN FT/C57

Give each selected field a column name in Column Heading.
OI/EN FT/C57 FT-101

Useful fields for the tables S2KAnnual_VTQTimeTable, S2KMonthly_VTQTimeTable,

S2KDaily_VTQTimeTable:
OBJID Measurement cross-reference in S2KVTQDictionnary_Table
OBJVALUE Measurement value
Measurement time stamping. Must be used with the following formula:
OBJFILETIME FiletimeToString2({S2Kxxxx_VTQTimeTable.OBJID},{S2Kxxxx_VTQTimeTable.OBJFILETIME},”
“,”hh:mm:ss.tt”)
Useful fields for S2KVTQDictionnary_Table:

OBJID Measurement cross-reference in the S2KxxxxxVTQTimeTable
Property of the archived measurement:
AverageCycle for the mean value
OBJPROPNAME
PeakMinCycle for the minimal value
PeakMaxCycle for the maximal value
TABLENAME Name of the table in which the measurement is archived
OBJNAME Measurement label
OBJAREANAME Origin label of the measurement
Useful fields for S2KEventMsg_Table:

ObjectNameText Event label
Event time stamping. Must be used with the following formula:
EventFileTime FiletimeToString2({S2KEventMsg_Table.LocaleID},{S2KEventMsg_Table.EventFileTime},”
“,”hh:mm:ss.tt”)
EventMsgText Event state
AreaGroupID Event cross-reference in the S2KEventGroup_Table
Useful fields for S2KEventGroup_Table:

GroupID Event cross-reference in the S2KEventMsg_Table
GroupPathName Origin label of the event
Click Next>>.
FT-102 OI/EN FT/C57

3 The Group tab is used to group values depending on sorting rules and to apply a calculation on these
group values (optional):
OI/EN FT/C57 FT-103

4 The Chart tab is used to display data in a chart (optional):
FT-104 OI/EN FT/C57

5 The Select tab is used to select a subset of information to display (optional):
OI/EN FT/C57 FT-105

6 The Style tab is used to select a style for the report (optional):
7 Click Finish: a preview of the report is displayed:
FT-106 OI/EN FT/C57

The Design tab is used to customize the template. Refer to the Crystal Reports documentation for more
information on how to use all the features. The report template must be saved using an authorized name.
In Design mode, add in the report header a text object “TYPE=HISTORICAL”. Without this object, the
report cannot be used.
5.1.2 CREATE A BUTTON IN SCE TO LAUNCH A REPORT

You first need to configure a button associated with a Run Report launch action link as shown below:
The attributes “Application name” and “Export format type” are mandatory.
The Application name corresponds to the report filename (do not include the file extension).
The attribute "Export format" of a "Run Report" element must have the "Excel 8.0 (.XLS)" value. Others
export formats must not be used in this version.
You can define up to 255 different reports.
OI/EN FT/C57 FT-107

5.2 HOW TO USE A REPORT CREATED BEFORE VERSION OI G.03.07

st
1 part: Report action update (with SCE)
1 Refer to the preceding section 5.1.2 Create a button in SCE to launch a report. Replace the old Run
Application action links by the new Run Report action links.
2nd part: Report (.rpt) update (with Crystal Reports)
2 Open your report with Crystal Reports software. Sometimes this pop-window appears:
Fill in these fields:

Server: set your DS Agile OI Server PC name
UserID: sa (always)
Password: nothing (always)
Database: Choose Historian (always)
Click OK.
3 Check whether this field is present: @FileTimeToString. If this is not the case, no migration is
mandatory (report OK); close your report. Otherwise continue with the following steps.
4 Open Field Explorer: menu “Insert \ Field Object”.
FT-108 OI/EN FT/C57

5 Right click on the SQL Expression Fields item. A popup menu will be displayed.
6 In this popup menu, choose New ….
7 Type the SQL expression name: GetEventFileTimeStr in the popup window displayed. Then click OK.
8 Add the following formula line in the new window:

CAST (S2KEventReport_View.EventFileTime AS NVARCHAR)
OI/EN FT/C57 FT-109

9 Check that there are no errors by clicking Check syntax.
10 Click Save, then exit this window.
11 Close the Field Explorer window.

12 Right-click on the @FileTimeToString field.
13 In the popup menu displayed choose Edit Field Object.
14 In the window shown change the following formula line from the old format to the new one:
Old:
FiletimeToString2
({S2KEventReport_View.LocaleID},{S2KEventReport_View.EventFileTime},"","hh:mm:ss tt")
FT-110 OI/EN FT/C57

New:
FiletimeToString3
({S2KEventReport_View.LocaleID},{%GetEventFileTimeStr},"","hh:mm:ss tt")
15 Check that there are no errors by clicking Check syntax.

16 Click on the Save icon and then exit this window.
17 Click on the Save icon to save your newly updated report. Then exit the Crystal Reports software.
9 Your report is now updated.
5.3 CREATE A TEMPLATE UNDER CRYSTAL REPORTS

Save your new template file under one of these names:
“Report1.rpt” for the report to be attached to the button “Application name equal to Report1”
or “Report2.rpt” for “Application name equal to Report2” and so on.
The Report Header of user reports must contain the following text: TYPE=HISTORICAL
OI/EN FT/C57 FT-111

Place the .rpt files in the DS Agile OI Xml Parser directory - D:\S2K_HMI\Reports\ENU - where all the
templates reports are stored. At the time of generation all templates reports in this directory will be in a
databag.
Use a report request (or Report button):
After having launched your DS Agile OI Server and DS Agile OI Client you can execute a request report by
pressing the adequate button. All reports will be generated in the directory where your SCADA server is
installed. If you use a standard installation, the location is C:\Program
Files\USDATA\S2K\Reports\Exported.
Each time you press the Report button a request is sent to the SQL server and a report file is generated in
Excel format. The structure of the name of the report file is as follows:
• Report’s name
• Date of write
• Time of write
Report1_07_13_2004_13_52_49.xls
You can open it using Microsoft Excel.
FT-112 OI/EN FT/C57

HARDWARE
OI/EN HW/C57
DS Agile Operator Interface Hardware
Contents
2 INDUSTRIAL PC DESCRIPTION 4
2.1 Main features 4
2.2 Description 5
2.2.1 Dimensions 5
2.2.2 Front panel 6
2.2.3 Rear panel 6
3 PANEL PC FOR BAY LOCAL OI 7

3.1 Main features 7
3.2 Description 7
3.2.1 Dimensions 7
3.2.2 Lateral panel 7
3.2.3 Power supply 8
OI/EN HW/C57 HW-1

Hardware DS Agile Operator Interface
HW-2 OI/EN HW/C57


This document is a chapter of the DS Agile Operator Interface documentation. It is the chapter Hardware
Description (HW) of this Product.
PCs are used as hardware platform for Operator WorkStation.
Depending on the environmental operating conditions and customer requirements, these PCs may be a:
• Standard PC
• Industrial PC
• Notebook
• Panel PC (Local OI Client)
The clients and servers (OI and SQL 2005) may be installed apart.
If the OI server is hosted by the fanless embedded PC, the SQL 2005 application MUST be installed on
another PC.
To get further details about the PC hardware, refer to the User’s Manual supplied by the manufacturer.
OI/EN HW/C57 HW-3

2 INDUSTRIAL PC DESCRIPTION
2.1 MAIN FEATURES

To increase environmental capabilities, an industrial PC may be used. This type of PC has a steel rugged
chassis, especially designed to run a high reliability application in a harsh environment.
Alstom has selected 2 variants of an Advantech™ design, fitted with the following modules:
Designation Description
A505Q variant A507Q variant
Chassis 4U rack mountable chassis (black) Advantech ACP 4320Q
Power Supply 400W ATX/PFC auto-switching power supply (100 – 240 VAC, 60 – 50 Hz, 8 – 4 A))
CD/DVD drive Optical Driver: 18X SATA DVD ROM
Removable HDD trays 2 3.5" SATA HDD trays
USB ports 2 USB 2.0 ports on front panel, 4 USB 2.0 ports on rear panel
Parallel ports 1 parallel port on rear panel
Serial ports 2 serial ports on rear panel
Ethernet ports 2 RJ45 ports on rear panel
Video ports 1 VGA and 1 DVI, both on rear panel
PS/2 ports 1 for keyboard and 1 for mouse, both on rear panel
Air filter
Cooling
Fans: 1 (12 cm / 114 CFM) + 1 (6 cm / 28 CFM)
Cooler LGA1155/1156 CPU cooler
LGA1155 Intel® Core™ i7/i5/i3/Pentium ATX with DVI/VGA, Dual Gigabit LAN, DDR3,
Mother Board
SATA III
Intel® Core™ i5-2400, 3.1 GHz clock speed / Intel® Core™ i7-2600, 3.4 GHz clock speed /
Processor
6 MB cache 8 MB cache
Dual channel DDR3 SDRAM at 1333 MHz, SDRAM DDR3 at 1333 MHz,
RAM Memory
240-pin, 4 GB (1 x 4 GB module) 240-pin, 8 GB (2 x 4 GB modules)
Hard disks Seagate 3"5, 1 TB, 7000 rpm (2 HD in RAID 1 configuration on PCIe slot)
RAID controller card CPU board, Highpoint RAID 10 card, SAS 4 channels, (PCIe x 4)
LAN/NIC Additional NIC Card: Dlink / Intel Network Card 10/100/1000 M PCI Slot
Keyboard Standard keyboard according to location
Mouse Logitech® M100 3-Button USB Optical Mouse (Black)
Microsoft® Windows Embedded Microsoft® Windows 7 Ultimate 64 bits, MUI,
Operating System
XP Professional SP3 OEM BIOS on USB with secure boot
Test IPC System Installation and 8-hour burn-in-test included
Table 1: Industrial PC specification
Note: This PC cannot host ISaGRAF in a redundant architecture
HW-4 OI/EN HW/C57

2.2 DESCRIPTION
2.2.1 DIMENSIONS
482 mm x 526.4 mm x 177 mm
Figure 1: Industrial PC dimensions
OI/EN HW/C57 HW-5

2.2.2 FRONT PANEL
DVD-ROM
System reset button drive
Alarm reset button
Filter cover(*)
Two SATA
HDD trays
Dual USB ports
(*)
Filter cover: see PC
user manual for
instructions on how to
replace the filter S1045ENa
Figure 2: Front panel
2.2.3 REAR PANEL

You will need to reserve sufficient space at the back of the device to fit the wiring connections.
Fan Serial ports VGA screen RJ45 Ethernet Parallel

connector connectors port
Power supply Power supply Keyboard DVI-D screen

connector on/off switch connector connector USB ports PCI slots S1044ENb
Figure 3: Rear panel
HW-6 OI/EN HW/C57

3 PANEL PC FOR BAY LOCAL OI
3.1 MAIN FEATURES

The fanless Panel PC includes:
• Two 10/100Base-T RJ-45 ports and two USB 2.0 ports

• Industrial proven design:
Rugged Power Supply: range 1: 24 VDC to 48 VDC, range 2: 110 VDC to 220 VDC
0-50°C
2 GB of Flash memory in place of hard disk
Fanless design with no internal cabling
• OS: Windows® XP Embedded

• Screen:
640x480 resolution, option 800x600)
6.5’’ size TFT, option: 8”
3.2 DESCRIPTION
3.2.1 DIMENSIONS
6.5”: 183 mm x 143 mm (4 U). Depth: 64.6 mm
8”: 234 mm x 177 mm (suggested cut-out: 223 x 166). Depth: 43 mm
3.2.2 LATERAL PANEL

6.5”:
OI/EN HW/C57 HW-7

8”:
3.2.3 POWER SUPPLY

Circular sockets
HW-8 OI/EN HW/C57

INSTALLATION
OI/EN IN/C57
DS Agile Operator Interface Installation
OI/EN IN/C57 IN-1

Installation DS Agile Operator Interface
Contents
2 GENERAL OVERVIEW 5
2.1 Hardware 5
2.2 Software 5
2.3 DS Agile OI delivery package 6
3 DS AGILE OI GLOBAL INSTALLATION 7

3.1 Microsoft SQL Server Installation 8
3.1.1 Microsoft SQL Server 2005 8
3.1.2 Microsoft SQL Server 2008 R2 37
3.2 Size of the Historian Database 81
3.3 SCADA 2000 Complete Installation: Client and Server 83
3.3.1 Setup 83
3.3.2 SCADA security (MANDATORY) 85
3.4 DS Agile OI Complete Installation: Client and Server 88
3.5 Client Standalone Installation 92
3.5.1 Scada 2000 installation 92
3.5.2 OI client installation 93
3.5.3 Configuration of DS Agile OI 97
3.6 Other operations 99
3.6.1 Configuration of the SQL 2005 purge 99
3.6.2 Installation problems with Crystal Report v8.0 102
3.6.3 Windows XP Embedded (Bay local OI) 102
3.6.4 Hot redundancy set-up 104
3.6.5 OI Printer Configuration 113
3.7 OI Server Watch 120
3.7.1 Installation 120
3.7.2 Settings 121
4 INSTALLATION AS A SERVICE 122

4.1 OI Server under Windows 2003 R2 SP2 122
4.1.1 Setup 122
4.1.2 Installation as a service 124
4.1.3 WinPcap installation 125
4.2 OI Server under Windows XP SP3 and Windows 7 Ultimate 64 bits (XP compatibility
mode) 126
5 ALSTOM DS AGILE OI UNINSTALL 127

5.1 Alstom DS Agile OI – Server & Client 127
5.2 DS Agile OI – Server as a service under Windows Server 2003/ Windows XP/ Windows 7127
5.3 Deletion of the Historian database 128
5.4 OI Server Watch 130
6 AUTOMATIC EVENT EXPORT APPLICATION 131
IN-2 OI/EN IN/C57

OI/EN IN/C57 IN-3


This document is a chapter of the Alstom DS Agile Operator Interface (OI) documentation. It describes the
installation of this product.
The objective is to install all software and hardware required to run DS Agile OI. You will also need to install
the IEC 61850-8-1 SBUS Agency software. An uninstall procedure is provided at the end of this document.
This document applies to the installation of DS Agile OI in two different types of architecture:
• Monolithic architecture, with both a DS Agile OI Server and a DS Agile OI Client installed in a unique
PC,
• Distributed architecture, including up to 8 DS Agile OI Clients (referred to as “standalone”) working

with the same DS Agile OI Server. Each client is installed on a different PC. The Windows Terminal
Server service can be used for communications between the server and the clients.
IN-4 OI/EN IN/C57

2 GENERAL OVERVIEW
Important:
All installation operations must be performed by a user with administrator rights.
The 'Administrator' account must be password-protected. It must be identical on all the PCs of the
application.
In the DS Agile OI architecture, all the PCs (desktop or laptop) hosting DS Agile OI Server and/or DS Agile
OI Client must have appropriate hardware and software.
2.1 HARDWARE
The standard PC must match the following minimum requirements:
• PC Core II duo 2.66 GHz

• RAM: 2048 MB
• Hard disk: 120 GB – only one partition – NTFS formatting(*).
• Screen display: 1024x768 resolution minimum, colour number: 256
• Ethernet board
• CD-reader
(*)
NTFS formatting is required because FT32 formatting limits file size to 4 GB which SQL databases will
often exceed.
Other kinds of PC are allowed: refer to the chapter OI/EN HW.
2.2 SOFTWARE
Operating System:
• Windows XP SP3, Windows XP Embedded, Windows 7 Ultimate 64 bits (in XP compatibility mode) for
DS Agile Gateway, OI and SMT
• OR Windows 2003 Server R2 Enterprise Edition SP2 for DS Agile OI

Applications to install:
• DS Agile OI Server & Client

Microsoft SQL Server 2005/2008
SCADA 2000 Server & Client
DS Agile OI Server & Client
DS Agile SBUS Agency
• DS Agile standalone OI Client

SCADA 2000 standalone Client
DS Agile standalone OI Client
To install DS Agile SBUS Agency, refer to its installation document SBUS/EN IN.
OI/EN IN/C57 IN-5

For both a redundant DS Agile OI Server and Stand-alone DS Agile OI Clients, be sure to define the same
Windows user - with the same rights - on each PC or the same as DS Agile OI Server, and log-on all PCs
with this identical user.
.NET Framework 2.0 is necessary to use the Multiscreen snapshot tool. It is normally installed together with
SQL Server 2005 and SQL Server 2008 and a .NET Framework2.0 installer is still included with Windows XP
and Windows 7.
2.3 DS AGILE OI DELIVERY PACKAGE

The DS Agile OI delivery package is delivered as a zipped archive containing 2 folders:
• PROGRAMS
\OI: OI application set-up files
\S2K M4: SCADA 2000 application setup files
\XML Parser: OI XML Parser application setup files for installation with DS Agile SCE
• Tools
\additional dlls for XP Embedded folder
\Framework .net 2.0 folder with the dotnetfx.exe setup file
\OI Server Watch Vx.xx\PROGRAMS folder: setup files for OI Server Watch
\SocketLimitationExtension folder which contains a link to a website that provides a
workaround against the 10 concurrent TCP connection attempts limit imposed by Windows XP
\sql\CleanHistorianJob folder which contains the setup files for an SQL job that will
periodically flush the HistorianLog file
\Start Server as Service folder
Note: Check the date of the msxml.dll files in the C:\Windows\system32 or C:\Windows\sysWOW64 folder: If
they are different from the date of the files automatically installed at setup, replace them and do not install any third-
party applications afterwards.
If you cannot replace them, it is due to the Windows File Protection which retrieves the previous version of an
XML file every time one is overwritten in the system folder. To replace them, use a software that temporarily disables
Windows File Protection, making it possible to copy and paste the msxml files.
IN-6 OI/EN IN/C57

3 DS AGILE OI GLOBAL INSTALLATION

Quick Reference Chart:
Note: Restart the PC after installation/uninstallation.
OI/EN IN/C57 IN-7

3.1 MICROSOFT SQL SERVER INSTALLATION
3.1.1 MICROSOFT SQL SERVER 2005
Note: If SQL Server 2005 is installed in Windows 7, an error message is displayed during the setup procedure,
warning that Visual Studio 2005 has known compatibility issues with Windows 7. To ignore this warning and install
SQL Server 2005, click Run program and proceed normally.
3.1.1.1 INSTALLER
1 Insert the “Microsoft SQL Server 2005 Standard Edition” CD-ROM, which launches automatically.
The following message appears briefly,
followed by this window:
2 Click Server components, tools, Books Online, and samples.
Note: If the following message appears, refer to section 3.1.1.2 Microsoft Windows Installer 3.1 Install
IN-8 OI/EN IN/C57

3 The following End User License Agreement (EULA) screen should then appear:
4 Tick I accept the licensing terms and conditions and click Next.
SQL Server 2005 now inspects your PC and prepares a list of the prerequisites it needs prior to the
installation.
OI/EN IN/C57 IN-9

5 When the list is ready, click either on Install or Next.
Note: If you clicked Install, SQL Server 2005 is probably installing .NET FrameWork 2.0 among other things. Let it
perform its running tasks and when completed, click Next.
SQL then checks the system’s configuration:
This operation may take a few minutes.

6 SQL Server 2005 then displays a Welcome screen. Click Next.
IN-10 OI/EN IN/C57

This screen should show 0 errors, 0 Warnings and a Success status.

7 If there is a Warning message such as in the example below, click Next to bypass it:
OI/EN IN/C57 IN-11

8 There should normally be no errors nor warnings displayed in the System Configuration Check
screen. Please proceed by clicking Next.
9 The Server setup Wizard prepares itself with the following screen and prepares for registration as
follows:
Enter ALSTOM in both the Name and Company fields and the registration number indicated on the SQL
Server 2005 Installation CD below. Click Next:
IN-12 OI/EN IN/C57

The next screen lets you select the components to install with SQL Server 2005.
OI/EN IN/C57 IN-13

Select the following items:
• SQL Server Database Services

• Analysis Services (necessary for cubes & data warehouse)
• Notification Services
• Integration Services
• Workstation Components, Books Online and development tools
10 Click Next.
IN-14 OI/EN IN/C57

11 Select Default instance then click Next.
12 Select the Use the built-in System account option and choose Local system from the corresponding
drop-down list. Let SQL Server, Analysis Services & SQL Browser be checked. Click Next.
OI/EN IN/C57 IN-15

13 Select the Mixed Mode option.

Define a temporary password that will be erased later on, for instance “DCSPW2012”.
14 Click Next.
15 Tick Collation designator and sort order and Customize for each service account. Click Next.
IN-16 OI/EN IN/C57

Note: For non-latin alphabets, select the option Collation designator and sort order.
- Russian: select Cyrillic_General in the list, untick Case-sensitive, tick Accent-sensitive
- Greek: select Greek in list, untick Case-sensitive and tick Accent-sensitive
16 Leave the default settings as they are and click Next.
17 SQL Server 2005 is now ready. Click Install.
OI/EN IN/C57 IN-17

18 Cycle through the screens as follows:
IN-18 OI/EN IN/C57

19 When available, click Next. After a few minutes, a final screen is displayed:
OI/EN IN/C57 IN-19

20 Click Finish, then reboot the PC.
3.1.1.2 MICROSOFT WINDOWS INSTALLER 3.1 INSTALL

While installing SQL Server 2005, if you see the message below, you should proceed by installing “Windows
Installer 3.1”:
Note: The Internet address given in the message box is no longer in use. Use this address instead:
http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c&DisplayLang=en
Note: Should the above link fail, try to download from the Microsoft Download Center.
From the screen shown below, you should click Continue to validate your Windows version, then click
Download for “WindowsInstaller-KB893803-v2-x86.exe”.
IN-20 OI/EN IN/C57

After clicking Download, you will be asked to close all open programs:
OI/EN IN/C57 IN-21

Cycle through the screens.

On completion, restart your system if it is not done automatically.
3.1.1.3 INSTALLING WINDOWS IIS COMPONENT

In order to install the “Internet Information Services” component (IIS), select the Add/Remove Programs
icon in the Windows Control Panel., then select Add/Remove Windows components in the Add/Remove
Programs window.
IN-22 OI/EN IN/C57

To install IIS, tick the checkbox relative to IIS and click Next.
You may need to insert the Windows 2000/2003 or Windows XP installation disk to be able to continue.
Once Windows is satisfied that it has all it needs, the system is configured to setup the IIS component.
3.1.1.4 HOW TO ASSOCIATE SQL SERVER 2005 AND DS AGILE OI

3.1.1.4.1 Creation of a blank password
First open the SQL Server Management Studio program by following the link shown below:
Type in the server name (computer name of the server):

On Windows XP, the server names are:
• OWSMXP for the main DS Agile OI server.

• OWSRXP for a redundant server.
Click Connect:
OI/EN IN/C57 IN-23

In the left panel of the Microsoft SQL Server Management Studio screen:
• Double-click on the Security folder to open it.

• Double-click on the Logins folder to open it.
• Right-click on sa and select Properties from the contextual menu.
In the following screen, you MUST delete the former password (“DCSPW2012”) given during the SQL Server
2005/2008 installation.
IN-24 OI/EN IN/C57

For this purpose:
• Delete the password in the Password textbox.

• Delete the password in the Confirm Password textbox.
• UNTICK the Enforce password policy checkbox.
• Click OK.
• Confirm if applicable.
OI/EN IN/C57 IN-25

3.1.1.4.2 SQL Server agent service

The SQL server 2005 agent service must be started before creating a “historian” database.
In SQL Server Management Studio, select SQL server agent and right-click Start:
Right-click on Properties, then select General in the Object Explorer:

Select:
• Auto restart SQL Server if it stops unexpectedly

• Auto restart SQL Server agent if it stops unexpectedly
3.1.1.4.3 Creation of Historian database

Normally, DS Agile OI creates the Historian Database. If you want to modify the options of a Historian
Database already created by DS Agile OI, open Microsoft SQL Server Management Studio and follow the
applicable steps in the procedure below. You will need to launch DS Agile OI (Server and Client) later to
create the tables. This is especially important for a Hot redundancy setup.
IN-26 OI/EN IN/C57

To create the Historian Database:

1 From the Windows Start menu, click on Programs|Microsoft SQL Server 2005 or
Programs|Microsoft SQL Server 2008.
2 Click on Microsoft SQL Server Management Studio.
3 To connect to the SQL server, click on Connect:
4 Click on Databases
5 Right–click on New Database
6 In the Database name field, type Historian:
OI/EN IN/C57 IN-27

Historian and the Historian Log Databases have to be set. Recommended values depend on the DS Agile
version used on the project.
During the creation of the Historian Database, parameters concerning the size of the Parameters to set are:
• Maximum file size: represent the maximum size in Megabytes of the database. When this size is
reached, SQL stops writing events into tables.
• Space allocated (second column “Initial size” for SQL 2005): this represents the initial size assigned to
the database at its creation. To avoid fragmentation of the Hard Disk and processor consumption
during growth activity, we recommend setting this parameter to the same value as the Maximum file
size.
• File Growth: this parameter represents the percentage of growing each time the allocate memory is
full; it is no more used if the two others are equal
Set these parameters during the creation process of the Historian Database. If you want to modify these
parameters later, we recommend deleting and recreating the Historian Database.
1 Under Database files: for Historian, in the Autogrowth column, click […] to display the Change
Autogrowth for Historian window.
2 Select Enable Autogrowth: the data files automatically increase in size by the amount shown in the
options below: percent or megabytes.
3 Select the option In Percent and type 20 (percent).
4 Select the option Restricted File Growth (MB) and enter the size in MB that a data file can grow to:
6000.
5 Click OK.
6 Under Database files: for Historian_log, in the Autogrowth column, click […] to display the Change
Autogrowth for Historian_log window:
IN-28 OI/EN IN/C57

7 Select Enable Autogrowth: the data files automatically increase in size by the amount shown in the
options below: percent or megabytes.
8 Select the option In Percent and type 10 (percent).
9 Select the option Restricted File Growth (MB) and type the size in MB that a data file can grow to:
2000.
10 Click OK.
11 To accept and create the Historian Database, click OK.
Maximum file size:
This parameter should be set as follows:
• The Historian database: 6000 MB

• The Historian Log database: 2000 MB
Space allocated:
This parameter should be set as follows:
OI/EN IN/C57 IN-29

• The Historian database: 6000 MB

• The Historian Log database: 2000 MB
Explanation:
By default, the value of the Space allocated parameter is 1 MB. This value means that we allocate 1 MB in
the historian database to write the first events in different tables. When this size is reached, the file is going
to grow by 20% (file growth parameter) of the current allocated size (here: 0.02 * 1 MB = 0.02 MB).
During this operation, SQL server uses RAM memory to reallocate each time 20% of the file memory.
File growth:
When it is needed, the recommendation is to set the value to 20%.
3.1.1.4.4 Connection to the Historian DataBase
Select Start|Settings|Control Panel|Administrative Tools|Data Sources
IN-30 OI/EN IN/C57

Click on the System DSN tab and then select SQL Server in the list to create a new datasource. Click
Finish.
Type Historian in the Name field and in the Description field. In the Server list, choose or type in the server
name (for example, OWSM) and click Next.
OI/EN IN/C57 IN-31

Accept the default setting and click Next.
Tick the Change the default database to checkbox and select Historian from the drop-down list. Then click
Next.
IN-32 OI/EN IN/C57

Accept the default setting and click Finish.
Click Test Data Source.
OI/EN IN/C57 IN-33

After the message TESTS COMPLETED SUCCESSFULLY has been displayed, click OK.
To close the ODBC data source windows, click OK in each window.
3.1.1.4.5 SQL server 2005/2008 memory consumption
In order to prevent the SQL server process from using up a large amount of RAM memory, a limit has to be
set in the properties of SQL server.
This operation will prevent the PC hosting the OI Server from slowing down and crashing.
We recommend setting the limit value to half of the RAM memory available in the PC.
Generally, OI Server uses up several GB of RAM memory (see Computer name: Properties | Menu
Memory). We recommend setting the limit of SQL Server memory consumption to half the RAM size.
Note: Do not modify any other settings in SQL. As of today, we do not know the possible effects of all the parameters.
In SQL Sever Management Studio, set the value of Maximum server memory (in MB):
IN-34 OI/EN IN/C57

3.1.1.4.6 SQL server 2005 CPU Affinity Setting

To optimize OI Server performance, untick the box and set SQL affinity to the 2nd CPU.
OI/EN IN/C57 IN-35

3.1.1.4.7 Clean the Historian log

In the Tools\sql\CleanHistorianJob folder of the DS Agile OI delivery, launch the batch file named
installCleanLog.bat; this installs the cleanLogHistorian job on MS SQL Server. This new SQL Server
job periodically flushes the Historian_log file.
There is no uninstall procedure. If needed, delete it from Tools|sql in the PC.
3.1.1.4.8 Checking the SQL Server Agent

Open SQL Server Configuration Manager from the menu
Start|Programs|Microsoft SQL Server 2005|Configuration Tools or
Start|Programs|Microsoft SQL Server 2005|Configuration Tools.
Select SQL Server 2005 Services or SQL Server 2005 Services:

The SQL Server Agent must be in Running State and Automatic Start Mode.
If the settings are different, for instance as in this screen:
1 Right-click on the SQL Server Agent line and select Properties.
IN-36 OI/EN IN/C57

2 Click Start if applicable; this starts the service.

3 In the Service tab, set the Start Mode to Automatic, then click Apply and OK:
3.1.2 MICROSOFT SQL SERVER 2008 R2
3.1.2.1 INSTALLATION
1 Right-click on the “Setup.exe” file available in the “SQL-2008 R2" installation folder and select Run as
Administrator in the contextual menu. The following screen is then displayed:
OI/EN IN/C57 IN-37

2 Click on the Installation link on the left hand side. The installation options are displayed as shown
below:
IN-38 OI/EN IN/C57

3 Click on the New Installation or add features to an existing installation link on the right hand side. The
following dialog is then displayed.
4 Click Run. The Setup Support Rules windows is displayed after you click Show details:
5 If any check fails, click Show details if necessary, then correct the relevant issues using the
information provided in the Status column. Then click Re-run to check whether the issue is resolved.
After the checks are completed successfully, click OK.
Note: Minor warnings can be ignored if there are any.
OI/EN IN/C57 IN-39

6 The product key's text box will be automatically filled in. Click Next.
7 Read the Licensing details. Tick the I accept the license terms box and click Next.
IN-40 OI/EN IN/C57

8 Click Install.
9 After the installation of the Setup support files, the following page is displayed, with a warning from the
Windows Firewall:
OI/EN IN/C57 IN-41

10 The details of the warning can be seen by clicking on the Warning link in the Status column.
11 To correct the warning, open the Windows Firewall page (Control Panel|All Control Panel
Items|Windows Firewall).
12 Click on the Turn Windows Firewall on or off link on the left hand side.
IN-42 OI/EN IN/C57

13 Select the Turn off Windows Firewall (not recommended) radio button for all the available networks.
Click OK, then Re-run in the SQL Server installation page. The result should be as shown below.
Note: Microsoft.NET Application Security will display a warning if there is no internet connection. This warning can be
corrected by enabling internet connection and then running the rule check again.
It is not mandatory to correct this warning as it does not affect the normal operation of the DS Agile System.
14 Click Next.
OI/EN IN/C57 IN-43

15 Select the SQL Server Feature Installation radio button and click Next.
16 Select all the features by clicking Select All then click Next.
IN-44 OI/EN IN/C57

17 Check that the Installation Rules have been passed successfully, and click Next.
OI/EN IN/C57 IN-45

18 Select the Default Instance radio button and click Next.
IN-46 OI/EN IN/C57

19 Click Next.
OI/EN IN/C57 IN-47

20 Set the SQL server agent's Startup Type to Automatic.

21 Click the Use the same account for all SQL Server services button.
22 In the Account Name combo box, select the NT AUTHORITY\SYSTEM account and click OK.
IN-48 OI/EN IN/C57

23 Select the Collation tab and click Customize in the Database Engine panel.
OI/EN IN/C57 IN-49

24 Select Windows Collation designator and sort order.

25 Choose the language in the Collation designator list.
Note: Non-latin alphabets:
- Russian: select Cyrillic_General in the Collation designator list, untick Case-sensitive, tick Accent-sensitive
- Greek: select Greek in the Collation designator list, untick Case-sensitive and tick Accent-sensitive
IN-50 OI/EN IN/C57

26 Click Next.
27 Select the Mixed Mode radio button, enter and confirm the password (DCSPW2012). Click Add
Current User in the SQL server administrator section, then on Next.
OI/EN IN/C57 IN-51

28 Click Add Current User and then click Next.
IN-52 OI/EN IN/C57

29 Select the Install but do not configure the report server radio button and Next.
OI/EN IN/C57 IN-53

30 Click Next.
IN-54 OI/EN IN/C57

31 Check whether the Installation Configuration Rules check has been successfully completed, and click
Next.
OI/EN IN/C57 IN-55

32 Click Install.
IN-56 OI/EN IN/C57

33 Click Close and reboot the computer.
3.1.2.2 SQL SERVER 2008 NETWORK CONFIGURATION

1 To enable the network protocols, launch SQL Server Configuration Manager from the All Programs
menu.
2 The SQL Server Configuration Manager window will be opened as shown below.
OI/EN IN/C57 IN-57

3 In the tree view panel, select SQL Server Network Configuration\Protocols for MSSQLSERVER
In the main panel, enable:
Shared Memory;
Named Pipes;
TCP/IP.
To set the status to Enabled, right-click on the list item to open the Properties dialog.
Notes: VIA is not important.
No changes are required for SQL Network Configuration (32bit)
Client Protocols
1 In the tree view select SQL Native Client 10.0 Configuration\Client Protocols
In the main panel, enable:
Shared Memory;
Named Pipes;
TCP/IP.
To set the status to Enabled, right-click on the list item to open the Properties dialog.
Notes: VIA is not important.
No changes are required for SQL Network Configuration (32bit)
2 Close the window and restart the PC.
IN-58 OI/EN IN/C57

3.1.2.3 HOW TO ASSOCIATE SQL SERVER 2008 AND DS AGILE OI

3.1.2.3.1 Creation of a blank password
1 Launch the SQL Server Management Studio from the All Programs menu
OI/EN IN/C57 IN-59

2 The SQL 2008 R2 Management Studio window will be opened as shown below.
3 Click Connect.
IN-60 OI/EN IN/C57

4 Right-click on sa and select Properties from the contextual menu.
5 Clear the passwords and untick the Enforce password policy box. Click OK.
6 Click Yes in the confirmation dialog.
3.1.2.3.2 Creation of Historian database

1 Open the Microsoft SQL Server Management Studio.
2 Right-click on the tree node Databases
3 Select the New Database in the contextual menu.
OI/EN IN/C57 IN-61

4 Enter the Database name as "HISTORIAN".
5 Click the [...] button in the Autogrowth column of the database file.
6 Set the File growth percentage to 20 and Restricted File Growth (MB) to 6000.
7 Click OK.
IN-62 OI/EN IN/C57

8 Click the [...] button in the Autogrowth column of the database log file.
9 Set the File growth percentage to 10 and Restricted File Growth (MB) to 2000.
10 Click OK.
OI/EN IN/C57 IN-63

11 Click OK in the New Database dialog and make sure that no error message is displayed.
IN-64 OI/EN IN/C57

3.1.2.3.3 Connection to the Historian Database

1 Select Start|Settings|Control Panel|All Control Panel Items|Administrative Tools
OI/EN IN/C57 IN-65

2 Choose Data SourceS (ODBC)
3 Select the System DSN tab and then Click Add.
IN-66 OI/EN IN/C57

4 Select SQL Server in the driver list and click Finish.
5 Enter the name for the data source as HISTORIAN, Select the local server in the server combo box
and click Next.
OI/EN IN/C57 IN-67

6 Select the Authentication as With SQL Server authentication.... Enter Login ID as sa and leave
Password blank. Then click on the "Next" Button.
7 Change the default database to Historian and click Next.
IN-68 OI/EN IN/C57

8 Click Finish.
9 Click Test Data Source.
OI/EN IN/C57 IN-69

10 Ensure that the message "TESTS COMPLETED SUCCESSFULLY!" is displayed.

11 Then click Next.
12 Click OK.
IN-70 OI/EN IN/C57

13 Click OK in the ODBC Data Source Administrator dialog.
3.1.2.3.4 Clean the Historian log

In the Tools\sql\CleanHistorianJob directory of the DS Agile OI delivery, launch the batch file
installCleanLog.bat; this installs the cleanLogHistorian job on the MS SQL Server. This new SQL
Server job periodically flushes the Historian_log file. There is no uninstall procedure. If needed, delete it from
Tools|sql on the PC.
3.1.2.3.5 Surface Area Configuration Facet

1 To enable the Surface Area Configuration Facet, right-click on the instance name in SQL Server
Management Studio and select Facets from the contextual menu.
OI/EN IN/C57 IN-71

2 This will display the View Facets dialog box that will provide a drop down list of all the available facets
that can be configured for the instance.
IN-72 OI/EN IN/C57

3 Select Surface Area Configuration from the Facet drop down list and set Facet Properties to True as
shown above. Click OK.
3.1.2.3.6 Checking the SQL Server Agent

Launch SQL server Configuration Manager from Windows Start menu:
Programs\Microsoft SQL Server 2008 R2\Configuration Tools.
OI/EN IN/C57 IN-73

1 In the tree view select “SQL Server Services”

2 In the main panel select “SQL Server Agent”
3 Open the property menu (by right click)
IN-74 OI/EN IN/C57

4 A box appears, set this box as follows:
5 Select this account and fill field Account Name and Password with the data of the administrator
account.
6 Click Apply.
7 Click Yes in the displayed Confirm Account Change dialog.

8 Click OK in the SQL server Agent (MSSQLSERVER) Properties window.
3.1.2.4 PROCEDURE TO PERFORM CONSOLIDATION IN OI

This section describes the installation and configuration required for consolidation of the Historian database.
Before performing consolidation, you must take the following steps on both server PCs.
OI/EN IN/C57 IN-75

• stop S2KServer.
• delete the Historian database.
• S2KServer must run with a valid configuration and not with the default configuration, because
Historian tables have to be created.
• restart S2KServer to recreate a clean Historian database.

Follow these steps for both server PCs:
• Script Installation
• Configuration of remote access on SQL Server
3.1.2.4.1 Script Installation
In the file C:\Temp\Trace\HRSQLScripts\Installation\ InstallConsolidation.sql, find the
lines below:
• SET @localServer = 'here_The_Name_of_Local_Server'

• SET @remoteServer = 'here_The_Name_of_Remote_Server'
Here set the name of computer’s name, which contains the S2KServers.
Warning:
Make sure to input the correct names, and these names must be crossed on each server.
Example, at left the text on server OISM, at right the text on OISR
After setting the variables, save and close the file.

Execute the batch file C:\Temp\Trace\HRSQLScripts\install2.bat
3.1.2.4.2 Configuration of remote access on SQL Server
a) Server Properties
1 Launch the “Microsoft SQL Server Management Studio” application.
2 Select the ‘root’ on the tree view.
3 Open the properties dialog (via the contextual menu/right click):
IN-76 OI/EN IN/C57

In the Security page:
OI/EN IN/C57 IN-77

• Enable the proxy server account

• Use the login of the user which has administrator privilege for proxy account
• Tick CrossDataBase Ownership Chaining
Click OK.
IN-78 OI/EN IN/C57

In the Connections page:
• Tick Allow remote connection to this server

• Tick Require distributed transaction for server to server communication
• Set Remote timeout to 0 (no timeout)
Click OK.
b) Security options
From the “Microsoft SQL Server Management Studio” application: expand the tree view until reaching the
node ‘root’\Security\Logins
The following logins should be added:
• NT AUTHORITY\SYSTEM
• BUILTIN\ADMINISTRATORS
Open the Properties windows of each login by right-clicking on it from the tree view and selecting
Properties from the contextual menu. Follow the steps below for each login:
OI/EN IN/C57 IN-79

In Server Roles page:

Grant all rights (tick all the boxes in the Server roles panel)
In User Mapping:
For each database, tick the Map box, and all boxes in the Database role membership panel.
IN-80 OI/EN IN/C57

Close the Properties dialog.

Restart the computer for the new settings to be taken into account.
3.2 SIZE OF THE HISTORIAN DATABASE

Estimates:
• One digital state change registers in the Historian Database every 30 s

• One acknowledgement of alarm registers in the Historian Database every 30 s
• One analogue change registers in the Historian Database every 5 s
• One control registers in the Historian Database every minute
With these estimates, the size of the Historian Database must be of at least 5 GB per year.
To change the amount of memory that SQL Server uses, follow these steps:
1 Open the Microsoft SQL Server Management Studio program. In the Object Explorer, click Connect
then select SQL Server.
2 Right-click on Properties.
OI/EN IN/C57 IN-81

3 In the Server Properties window, select Memory. Change the Maximum server memory (in
MB) value to half of the PC memory with a minimum value of 1024 MB:
IN-82 OI/EN IN/C57

3.3 SCADA 2000 COMPLETE INSTALLATION: CLIENT AND SERVER
3.3.1 SETUP
Problem Uninstalling S2K on some systems
There is a permission problem in the registry that causes the following dialog to appear. We are working on
fixing this problem, but you may see this problem when uninstalling S2K M4. If it appears, just press the
Ignore button. This will leave one key in the registry, but it does not effect any subsequent operation.
It is strongly recommended to install SCADA2000 M4 on its default path (C:\Program Files\USDATA)

in order to avoid an anomaly (incorrect installation of oipolling.dll).
Click on
\\ <OIVersion> \CD-ROM\PROGRAMS\S2K M4\M4-<M4version>_setup.exe
Starting with the Welcome screen, cycle through the screens (buttons Next):
In the Setup Type dialog box, select the Custom radio button. (Do not change the Destination Folder).
Enter the Customer Information and select Anyone:
OI/EN IN/C57 IN-83

In the Select Features dialog, select the components to install as follows (in Modules, the OPC components
are reserved for use by the OPC protocol):
Check the Start Copying Files dialog box information before the installation:
IN-84 OI/EN IN/C57

When the installation is complete, click Finish then restart the PC in order to avoid DCOM errors.
3.3.2 SCADA SECURITY (MANDATORY)

1 Run dcomcnfg.exe and select DCOM Config
2 Select S2K.OpcServer, right-click and select Properties

3 Open the Security tab and select Use Default in the Launch and Activation Permissions and
Access Permissions boxes.
OI/EN IN/C57 IN-85

4 In the Configuration Permissions box, select Customize and click Edit…
To add the name of the user of the OI (Alstom in the example), click Add, enter part of the name and click
Check.
1 For all Group and User names, allow Full Control and Read, then click OK.
IN-86 OI/EN IN/C57

2 Do the same for SCADA2000 CS2KAlarmServer and SCADA 2000 Server.exe. In addition, open the
Location tab and tick Run application on this computer, then open the Identity tab and select The
interactive user.
3 Do the same (steps 2 to 5) for NewClusterMgt and USDATA Trend Datasource Server. In addition,
open the Location tab and tick Run application on this computer, and in the Identity tab, select
The interactive user
OI/EN IN/C57 IN-87

4 Click Apply , then OK.
3.4 DS AGILE OI COMPLETE INSTALLATION: CLIENT AND SERVER

You must select a complete installation of DS Agile OI and Factory Link SCADA 2000 (Server &
Client) for both server sides (primary and secondary).
Note: Do not use the shortcut "DS Agile OI Client Watch".
Run \\<OIVersion>\CD-ROM\PROGRAMS\DS Agile OI\Setup.exe
Cycle through the screens (buttons Next).

In the License Agreement dialog box, select the I accept the terms in the license agreement radio button.
IN-88 OI/EN IN/C57

In the Customer Information dialog box enter the User Name and Organization Name. Select the Anyone
who uses this computer (all users) radio button then click Next.
OI/EN IN/C57 IN-89

In the Setup Type dialog box select the Complete radio button.
In the Destination Folder for SCADA 2000 modules dialog box DO NOT change the default folder.
In the Ready to Install the Program dialog box, click Install.
In the Install Checkup dialog box, click Next (for Shared Folders and AutoLogon settings see next
section).
IN-90 OI/EN IN/C57

In the Install Checkup dialog box click Next (for Shared Folders and AutoLogon settings see next
section).
In the InstallShield Wizard Completed dialog box click Finish.
At last click Yes to restart the PC.
Multiscreen snapshot tool:
This tool requires that Framework.net 2.0 be installed.
OI/EN IN/C57 IN-91

3.5 CLIENT STANDALONE INSTALLATION
Note: For a Standalone OI Client, the msxml4 dll files must be installed.
3.5.1 SCADA 2000 INSTALLATION

Follow the instructions given in section 3.3 SCADA 2000 Complete Installation: Client and Server but when
the Select Features dialog box is displayed untick the tick-boxes as shown below:
Apply the security procedure described in section 3.3.2 SCADA security (MANDATORY). Some services are
missing as only a part of the S2K has been installed.
IN-92 OI/EN IN/C57

3.5.2 OI CLIENT INSTALLATION

Follow the instructions given in section 3.4 DS Agile OI Complete Installation: Client and Server until the
Setup Type dialog box is displayed.
In the Setup Type dialog box, select the Custom radio button (instead of Complete):
Do not change the default folder in any screen.

In the Custom Setup dialog box, click the icon next to Server Components and unselect it:
OI/EN IN/C57 IN-93

Click Next.
Click Next.
IN-94 OI/EN IN/C57

Click Next, then Install.
OI/EN IN/C57 IN-95

In the new box, click Logon; the AutoLogon dialog box is displayed.
The Server Name must be the Main server name, use the AutoLogon to define it:
In the AutoLogon dialog box, select the Enable Auto Logon checkbox, enter the Server Name then click
Apply.
Note: Be sure to define the same Windows user, with the same rights, on each PC, and log-on the PC with that user
name.
The InstallShield Wizard Completed dialog box is displayed; click Finish.

Lastly, click Yes to restart the PC.
When the PC has restarted:
• Refer to the chapter OI/EN MF, section 3 (Files hierarchy).

• Check the Multiscreen snapshot tool by launching the executable in the
\\DS AgileOI\Client\OISnapShot folder).
This tool needs the installation of Framework.net 2.0.
For Windows 2003 Server: the Tools\Framework.net 2.0 folder contains the file to install.
IN-96 OI/EN IN/C57

3.5.3 CONFIGURATION OF DS AGILE OI
3.5.3.1 SHARED FOLDERS

In Windows Explorer, select the menu Tools|Folders Options, and the View tab. Make sure that the last
line is ticked:
Click Share in the Install Checkup dialog box; this launches the Windows Explorer; scroll down to the
folders to share and right-click on them.
DIRECTORY SHARE NAME
C:\Program Files\Alstom\DCS\DSAgileOi\Server\MemoFolder MemoFolder
C:\SharedWorkspace SharedWorkspace
C:\Temp\Trace PersistanceDSAGILE
For each of them select Permissions and, for Everyone, allow Full Control, Change and Read:
OI/EN IN/C57 IN-97

3.5.3.2 AUTOLOGON
Launch Autologon from the installation folder.

Tick the box Enable Auto Logon.
IN-98 OI/EN IN/C57

The Windows auto-logon procedure applies to the current user, that is with the Windows user rights. It aims
to allow the restart of DS Agile OI Client on the PC power-on without a user log-in step:
either with a default user logged
or with a logon box (without default user).
Note : the Server Name text area is available ony for a Standalone OI Client.
3.5.3.3 DCOM SETTINGS

Refer to the DS Agile/EN IN chapter.
3.6 OTHER OPERATIONS
3.6.1 CONFIGURATION OF THE SQL 2005 PURGE
3.6.1.1 SQL SERVER AGENT SERVICE

If it not already done, in SQL Server Management Studio, select SQL server agent and right-click Start:
Right-click on Properties, then select General in the Object explorer:

Select:
OI/EN IN/C57 IN-99

• Auto restart SQL Server if it stops unexpectedly

• Auto restart SQL Server agent if it stops unexpectedly
3.6.1.2 PARAMETER CHECK FOR HISTORIC PERIODS

SCE parameters relevant to historic periods are loaded into SQL jobs. These jobs are launched periodically
by S2KServer to delete the old data in Historian database.
If you change these parameters in SCE, you will have to:
• Download the new database

• Stop S2K Server then delete and recreate the Historian database
• Restart S2KServer
or
• Manually set the various jobs to the new values

To check that the “Historic periods” parameters configured in SCE are correctly taken into account by SQL
server, check the screenshots below.
3.6.1.2.1 S2KEventMsg_Table (event historic period (day) = 14 days
Browser > Management \ SQL Server Agent \ Job
Window > PURGE S2KEventMsg_Table | Properties | Step Tab | Edit
IN-100 OI/EN IN/C57

3.6.1.2.2 S2KVTQ6_VTQTime table (value historic period (day) = 7 days)

Explorer > Management \ SQL Server Agent \ Job
Window > PURGE S2KVTQ6_VTQTimeTable | Properties | Step Tab | Edit
OI/EN IN/C57 IN-101

Note: If there is an important dataflow in the system and the jobs cannot delete enough events on time, a workaround
is to reduce the value of:
- event historic period (day) to 3 (for instance)
- value historic period (day) to 2 (for instance)
3.6.2 INSTALLATION PROBLEMS WITH CRYSTAL REPORT V8.0

If you have installed Crystal Report v8.0 on your computer before installing S2K, the S2K set-up fails
because the Crystal Report v8.0 set-up incorrectly sets the permission for the Interface under
Hkey_Classes_Root in the registry. This prevents some S2K COM components from being registered and
unregistered and therefore causes the installation or uninstallation to fail. This problem seems to be due to a
Crystal Report v8.0. bug. A similar problem will occur if you install Crystal Report v8.0 after installing S2K. In
this case, uninstalling S2K fails for the same reason.
The workaround is to manually reset the permission for the interface under Hkey_Classes_Root in the
Registry where you install Crystal Report. To do this:
• Launch regedit32.exe.
• Open the Interface key under Hkey_Classes_Root.
• Click Security then Permissions... in the Registry menu.
• Untick the tick-box located at the bottom in the Permission for Interface dialog box it was ticked.
• Click Apply in the dialog box (click OK in any subsequent dialog box).
• Tick again the previous tick-box.
• Click OK in the dialog box.
3.6.3 WINDOWS XP EMBEDDED (BAY LOCAL OI)

On OIXPE, install the software as usual: Agency, SCADA 2000 M4, DS Agile OI.
Only the traces are moved to the remote PC FILESERV. Other data such as users, memos, configuration
downloading, etc, are retained locally and accessed through the shared folders.
Use the same Windows user account/password on both computers: FILESERV and OIXPE.
The DoSave & Persistence files are written in the S2KServer start folder. This must not be changed as these
files are necessary for the real time features. You may however want to decrease the rate at which they are
written. Note that where Hot Redundancy is used, these files are neither created nor used.
3.6.3.1 INSTALLATION OF ADDITIONAL DLLS

Copy from the \Tools\additional DLLs for XP Embedded folder of the OI Delivery into the
C:\windows\system32 folder of the OIXPE computer:
• mobsync.dll
• msjava.dll
• npptools.dll
• query.dll
• w32topl.dll
• gpudate.exe
IN-102 OI/EN IN/C57

3.6.3.2 REMOTE FOLDER

1 On FILESERV, create a new folder called DeportedOIFiles (at any location) which will host all the
files from OIXPE.
2 Share this folder (any share name allowed) and give full access rights (read & write) to Everyone as
indicated in the section above.
3 Mount this shared folder on the OIXPE computer:
From the Windows Explorer menu, select Tools, then Map Network Drive.
In the Map Network Drive window, select any drive letter available (Ex: “P:”):
In the Folder field, enter the location of the DeportedOIFiles folder created on the FILESERV
Computer (Ex: \\FILESERV\DeportedOIFiles).
Select the Reconnect at logon option and click Finish: the FILESERV computer is now linked
through the “P:” drive.
Under P:\, create the following subfolders:
DBWin
ScadaTrace
UCA2
SharedWorkspace
Copy the files DB.exe and DBWin.bat from
C:\Program files\ALSTOM\DCS\61850agency\exe into the P:\DBWin folder.
Launch DbWin.bat from the OIXPE computer via P:\ (NEITHER via C:\Program Files, NOR
via the FILESERV computer).
OI/EN IN/C57 IN-103

3.6.3.3 REGISTRY EDITION

In order to redirect the other traces files to the network drive (P:\), it is necessary to edit some registry keys:
refer to OI/EN MF.
3.6.3.4 AGENCY CONFIGURATION

The SBUS agency cannot write its log files onto a remote computer. It is therefore necessary to disable trace
file creation.
For this purpose, using any text editor (ex: Notepad), open mms_log.cfg located in:
C:\Program Files\ALSTOM\DCS\OI\Server\Configuration\DBID1\S2kHMIConfig\
S2K-HMI-SRV\UCA2 (if the configuration was loaded under DBID1).
Note: To know if the configuration is loaded in DBID1 or DBID2, check

HKEY_LOCAL_MACHINE\Software\ALSTOM\DCS\OI\Current, see OI/EN MF.
Comment out the following line by adding a # symbol at the beginning of the line:
# FileLogEn # Log to a file
Use the same Windows user account/password on both the FILESERV and OIXPE computers.
3.6.3.5 OTHER SETTINGS
• Refer to OI/EN AJ.
3.6.4 HOT REDUNDANCY SET-UP

Refer to OI/EN FT for functional description of hot redundancy.
The OI Server Watch software must be active in order to automatically restart the remote server in case of a
double STANDALONE and in the event of the loss of either server.
On both servers:
1 Delete the Historian database.
2 Create a new one; select a file growth of 10% in place of 20% for the Historian database.
3 Launch the OI and download a databag into it; this creates the table in the Historian database.
3.6.4.1 SQL SERVER 2005/2008 CONFIGURATION

1 Execute the batch file C:\Temp\Trace\HRSQLScripts\install1.bat
where C:\Temp\Trace\HRSQLScripts is the PersistanceDSAgile shared directory
2 Wait until the DOS window closes.
3 From the Windows Start menu, start the SQL Server Configuration Manager:
Programs|Microsoft SQL Server 2005|Configuration Tools or
Programs|Microsoft SQL Server 2008|Configuration Tools
IN-104 OI/EN IN/C57

SQL Server Agent:

1 Select SQL Server 2005 Services or SQL Server 2008 Services.
2 Select SQL Server Agent (MSSQLSERVER).
3 To open the property dialog box for the SQL Server Agent, right-click on SQL Server Agent:
4 Select This account. In the Account Name, Password and Confirm password fields, enter the
Administrator account details. The Password is mandatory.
5 Click Apply and OK.
6 The server must start: Service status: shows Running. If the server does not start, click Start.
Protocols for MSSQLServer:
1 In the SQL Server Configuration Manager window, select SQL Server 2005 Network
Configuration or SQL Server 2008 Network Configuration.
OI/EN IN/C57 IN-105

2 Click two times on SQL Server 2005 Network Configuration or SQL Server 2008 Network
Configuration. The Protocols for MSSQLSERVER are displayed.
3 Select Protocols for MSSQLSERVER.
4 Under Protocol Name, right-click on the items to open the related Properties windows. If necessary,
right-click and set the Status to Enabled for:
Shared Memory
Named Pipes
TCP/IP
Note: The status for VIA is not important.
Client Protocols:
1 In the SQL Server Configuration Manager window, select SQL Native Client Configuration.
2 Click two times on SQL Native Client Configuration. The Client Protocols item is displayed.
3 Select Client Protocols.
IN-106 OI/EN IN/C57

4 Under Protocol Name, right-click on the items to open the related Properties window. If necessary;
right-click and set the Status to Enabled for:
Shared Memory
TCP/IP
Named Pipes
Note: The status for VIA is not important.
3.6.4.2 DATABASE CHANGE

1 Open (using Notepad) the text file
C:\Temp\Trace\HRSQLScripts\Installation\InstallConsolidation.sql
2 In this file, search the text below:
Find this line to set variable
3 In the next line, spot the two variables to set:
@localServer
@remote Server
4 Set the name of the computers that hosts the OI Servers.
CAUTION: MAKE SURE YOU INPUT THE CORRECT NAMES.

MAKE SURE THAT YOU CROSS THESE NAMES ON EACH SERVER.
Example, with the text on server OISM to the left and the text on server OISR to the right:
SET @localServer = ‘OISM’ SET @localServer = ‘OISR’
SET @remoteServer = ‘OISR’ SET @remoteServer = ‘OISM’
1 After setting the variable, save and close the file.

2 Execute the batch file C:\Temp\Trace\HRSQLScripts\install2.bat
3 Wait until the DOS window closes.
4 Restart the PC.
OI/EN IN/C57 IN-107

3.6.4.3 CONNECTION AND REMOTE ACCESS CONFIGURATION ON SQL SERVER 2005/2008

Server Properties:
1 Start the Microsoft SQL Server Management Studio application.
2 In the Object Explorer window, select the item <PC_NAME> (SQL Server…)
3 Right-click on Properties. The Server Properties – OISR window opens.
4 Select the Security page:
5 Select SQL Server and Windows Authentication mode

6 Select Failed logins only
7 Select Enable server proxy account
8 Click [ .. ] and retrieve the proxy account. Type the administrator Password.
IN-108 OI/EN IN/C57

9 Select Cross database ownership chaining.

10 Click OK.
11 Select the Connections page:
12 Select Allow remote connections to this server.

13 Set Remote query timeout (in seconds, 0 = no timeout) to 0 (no timeout).
14 Select Require distributed transactions for server-to-server communication.
15 Select Configured values.
16 Click OK.
OI/EN IN/C57 IN-109

Security options:
1 In the Object Explorer window, click two times on <PC_NAME> (SQL Server…). Two databases are
displayed: NT AUTHORITY\SYSTEM and BUILTIN\Administrators.
NT AUTHORITY\SYSTEM Database
1 Right-click on NT AUTHORITY\SYSTEM and right-click on Properties
2 For Server Roles, grant all rights: tick all the boxes.
IN-110 OI/EN IN/C57

3 For the page User Mapping -> Users mapped to this login -> Map, tick the Map box for each
database:
4 Select the first database: Historian. Under Database role membership for: Historian, select all of
the databases.
5 Select the second database: master. Under Database role membership for: master, select all of the
databases.
6 Do the same for each database.
7 Click OK.
BUILTIN\Administrators Database
1 In Object Explorer, right-click on BUILTIN\Administrators and right-click on Properties:
OI/EN IN/C57 IN-111

2 For Server Roles, grant all rights: tick all the boxes:
3 In the panel User mapping -> Users mapped to this login -> Map, tick the Map box for each
database:
4 Select the first database: Historian. Under Database role membership for: Historian, select all of
the databases.
5 Select the second database: master. Under Database role membership for: master, select all of the
databases.
6 Do the same for each database.
7 Click OK and close.
IN-112 OI/EN IN/C57

You have set the security options for the two databases: NT AUTHORITY\SYSTEM and
BUILTIN\Administrators. For the changes to take effect, restart the PC.
3.6.4.4 HOW TO STOP AN OI HOT REDUNDANCY (IF NEEDED)

To stop the OI Servers, right-click on the OI Server icon in the system tray and select either option:
a. Stop: this stops both servers (Master and Slave).
b. Stop local server: this stops only the server from where the stop request was issued.
3.6.5 OI PRINTER CONFIGURATION

SOE and/or Log Book printers can be managed using a parallel or Ethernet network printer.
Mixing parallel and network printers is not permitted.
Parallel printers should not be used in Hot Redundancy mode.
3.6.5.1 PARALLEL PRINTER: PRINTING SPOOLER CONFIGURATION

The printing service uses Windows's native functions (spooler). There are some requirements on spooler
configuration to ensure an optimal functioning:
1 Remote printers used in DS Agile OI must be declared in the local spooler,
2 For the printer, the printing mode is defined as follows:
In the Ports tab, the port timeout (Transmission retry) must be set to 2 in order to ensure faster
error detection,
In the Advanced tab, select the options as follows:
OI/EN IN/C57 IN-113

3.6.5.2 NETWORK PRINTER CONFIGURATION

When installing an SOE Network printer (Lexmark 2591n), the TCP/IP port used by the printer must start with
"IP_". This is not done by default, therefore, after installing the printer, add a new TCP/IP port as follows:
1 Open the Configuration Panel and go to Printer and Faxes.
2 Right-click on the installed SOE network printer and choose Properties.
3 Choose Add Port.
4 Choose Standard TCP/IP Port.
IN-114 OI/EN IN/C57

5 Choose New Port…; this launches a wizard.

6 Cycle through the screens.
7 Type the printer's IP address and click Next. Windows automatically adds the IP_ prefix to the port
number as the Port Name.
8 Select Generic Network Card and click Next.
9 Select Finish in the last screen.

10 Close the previously opened Printer Ports window.
11 In the Printer Properties, choose the port you have created and click Apply.
OI/EN IN/C57 IN-115

This attaches the SOE network printer to the newly created port.
12 In the Advanced tab, select the options as follows:
13 Click Apply then OK.
IN-116 OI/EN IN/C57

3.6.5.3 GRAPHIC PRINTER

To properly print some languages characters, the printing must be set in Graphic mode. The mode
automatically matches the locale as set in the configuration file. Currently, only Chinese language is
supposed to switch to graphic mode.
The following procedure provides graphic mode for Lexmark 2500 series, model 2591/2591n.
1 Ensure that you have installed the printer with its driver. The driver must appear as “Lexmark Forms
Printer 2591/2591n”.
If you plan to use wide paper, add a new form to the printers
2 Open the printer management windows:
3 Select the File|Server Properties menu:
4 Create a new form, with the name and dimensions according this example:
OI/EN IN/C57 IN-117

5 Save before leaving by pressing the Save Form button.

Set the printer default parameters
6 Open the printer’s Properties dialog box.
7 Select the Advanced tab
IN-118 OI/EN IN/C57

8 Click Printing Defaults…
9 Click Advanced …
OI/EN IN/C57 IN-119

10 Select the correct paper format.

11 Click OK in all the open windows.
3.7 OI SERVER WATCH
3.7.1 INSTALLATION
If you use DS Agile OI’s Hot Redundancy function, install OI Server Watch on EACH PC.
If this is a first installation, an Oiserverwatch.ini file is created in the OIServerWatch folder. Because
this file is meant to be set by the user, later installations WILL NOT replace it, but only adjust the path of
DS Agile OI, SMT or Station Bus agency if necessary (see below the case of an OI redundancy).
1 If a previous version of the OI Server Watch application is already installed, DO NOT uninstall it so as
to retain the same OIServerwatch.ini file: The new set-up will only adjust the path of DS Agile OI, SMT
or Station Bus agency if necessary.
2 Launch OIServerWatchSetup.exe and follow the on-screen instructions.
In standard installation OI Server Watch is installed automatically in the
C:\Program Files\ALSTOM\DCS\OIServerWatch folder.
A dialog box proposes the installation as a service:
IN-120 OI/EN IN/C57

Answer No. The installation as a service is described in another section. At the end of the installation
procedure, the following message is displayed:
If you choose Yes, OI Server Watch is launched using the Oiserverwatch.ini file present in the
installation directory.
3.7.2 SETTINGS
If needed, modify the OI Server Watch settings to define which applications should be supervised.
Note 1: The installation of OI Server Watch is mandatory on both PCs in the case of an OI Hot redundancy.
Note 2: DO NOT modify the corresponding registry keys (current_version field and location fields).
Refer to DS Agile/EN AJ.
OI/EN IN/C57 IN-121

4 INSTALLATION AS A SERVICE
The main goal of using DS Agile OI Server as a service is to access it from a remote WTS (Windows
Terminal Server). OI Server and OI Client may or may not be installed on the same machine.
When the user launches DS Agile OI Client from a WTS client PC, it will successfully communicate with
DS Agile OI Server only if the latter has been launched in a Windows service context (launched as a
Windows service or launched by a Windows service). This is due to due to WTS session mechanisms.
Refer to DS Agile/EN IN for the general configuration.
4.1 OI SERVER UNDER WINDOWS 2003 R2 SP2
Warning:
Using the control panel, make sure OI Server Watch is not installed. If it is, uninstall it
first using the control panel.
Pre-requisite: the program OI S2KSERVER (SCADA 2000 M4-J.01.XX) must NOT be installed. The
uninstallation should be done using the Windows Control Panel, select Add/Remove program (SCADA
2000 M4-<VERSION>).
4.1.1 SETUP
Follow this procedure STEP BY STEP:
1 Open the Control panel and launch Add/Remove Programs.

2 In the left-hand side menu, click Add New Programs.
3 Click the CD or Floppy button to launch the Install Program From Floppy Disk or CD-ROM Wizard.
IN-122 OI/EN IN/C57

4 Click Next; the wizard browses your CD-ROM drive.
5 If there is no disk nor diskette available, it prompts you to browse manually. In this event, browse to
the M4-J.01.XX_setup.exe file from the release folder CD-ROM\PROGRAMS\S2K M4 and click
Finish. Browse the appropriate install file. Note: You may need to change Files of type: to Setup
Programs.
6 Run the S2KServer setup. When that is done, click Next and finally click Finish.
OI/EN IN/C57 IN-123

4.1.2 INSTALLATION AS A SERVICE

1 Copy the file
Tools\Start Server as Service\IntallDSAgileSrv_WS2003.bat to the DS Agile
OI S2KServer installation folder. The default folder is
C:\Program Files\USDATA\S2K\Bin.
2 Copy the file
Tools\Start Server as Service\DS AgileSrvkeys_WS2003.reg to the DS Agile
OI S2KServer installation folder. The default folder is
C:\Program Files\USDATA\S2K\Bin.
3 Open the file DSAgileSrvkeys_WS2003.reg using Notepad, change the name of OI main server
(OI_PERF1) and, if the hot Redundancy mode is used, of OI back-up server (OI_PERF2), and save it:
/Server1: Server main (Network name as configured in SCE)
/Server2: Server Backup (Network name as configured in SCE)
The parameter “ImagePath” indicates the full path of S2KServer.exe:
ImagePath = D:\Program Files\USDATA\S2K\Bin\S2KServer.exe
/Root S2KRootContainer.1 /Application DS Agile
/Server1 OI_PERF1 /Server2 OI_PERF2 /PrsShare
PersistanceDSAGILE /LocateTime 20000 /WaitAloneTime
20000 /StartMode WARM.
Regardless of which one is active, /Server1 points to the main server and /Server2 to the backup server.
4 In the Run windows, select Browse, then select the DS Agile OI S2KServer installation folder and run
the command file InstalDSAgileSrv_WS2003.bat. This batch file registers S2Kserver and
TrendDSServer programs as service and sets up Register Keys.
5 Run regedit and check the value of the following key
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\S2KServer\]
IN-124 OI/EN IN/C57

4.1.3 WINPCAP INSTALLATION

The use of OI Server as service with Windows Server 2003 involves the installation of WinPcap 3.0 instead
of a newest version.
If the installed version of WinPcap is not version 3.0 (for instance, 4.0.1), uninstall it first from Windows.
Before the installation, stop the OI Server service.
Install WinPCap 3.0 from Tools/Start Server as Service (version 3.0 is provided after the
installation of Agency version V4.9D or later).
If the Agency version is older than V4.9D, WinPcap 3.0 can be downloaded from
http://www.winpcap.org/archive/
OI/EN IN/C57 IN-125

4.2 OI SERVER UNDER WINDOWS XP SP3 AND WINDOWS 7 ULTIMATE 64

BITS (XP COMPATIBILITY MODE)
WARNING:
Using the control panel, make sure DS Agile Watch is not installed. If it is, uninstall it
first. The uninstall should be done using Windows Control Panel, select Add/remove
programs (SCADA 2000 M4-<version>).
Pre-requisites:
• the program OI S2KSERVER (SCADA 2000 M4-J.01.XX) is installed

• the DCOM adjustments are as indicated in DS Agile/EN IN
Installation as a service:
1 Copy the archive Tools\Start Server as Service\srvany.zip to the local Windows folder
%SYSTEMROOT%\system32 and unzip it.
2 Copy the file Tools\Start Server as Service\IntallDS AgileSrv.bat to the DS Agile OI
Installation folder.
The default folder is C:\Program Files\USDATA\S2K\Bin.
3 Copy the file Tools\Start Server as Service\DS AgileSrvkeys.reg to the DS Agile OI
Installation folder.
The default folder is C:\Program Files\USDATA\S2K\Bin.
4 In the Run windows, browse to the DS Agile OI Installation folder and run the command file
InstalDS AgileSrv.bat.
IN-126 OI/EN IN/C57

5 ALSTOM DS AGILE OI UNINSTALL
5.1 ALSTOM DS AGILE OI – SERVER & CLIENT

• The uninstall procedure is a standard Windows XP or Windows 7 process, using the Control panel,
Add/Remove Programs tool.
• Select Alstom DS Agile OI, then click Remove.

• Select Alstom DS Agile S2K, then click Remove
After completing the removal of all installed DS AGILE Components, restart the PC and make sure that all
the folders created during installation and the registry entries are removed.
Folders to check:
• $:\Program Files\USDATA
• $:\Program Files\ALSTOM
• $:\S2K_HMI
• $:\SharedWorkspace
• $:\LocalWorkspace
• $:\Temp\Trace
Registry Keys to check:
• HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\OI
• HKEY_LOCAL_MACHINE\SOFTWARE\USDATA
If any of the folders or registry keys already exists, users have to manually remove all those folders and
keys. Otherwise a further reinstallation could result in faulty behavior by the DS Agile System.
5.2 DS AGILE OI – SERVER AS A SERVICE UNDER WINDOWS SERVER 2003/

WINDOWS XP/WINDOWS 7
1 Step 0: Stop OI Server
If OI Server is running, stop it.
2 Step 1: Open the Control Panel
Open the Control Panel and launch Add/Remove Programs…
3 Uninstall OI Server
OI/EN IN/C57 IN-127

Select SCADA2000 and uninstall by clicking Change/Remove.
Note: When OI Server is uninstalled all the Registry Keys will be removed automatically.
5.3 DELETION OF THE HISTORIAN DATABASE

After set-up, if a 'Historian 'DataBase' exists on your PC (Database created by a previous release of S2K
M4), you have to delete it. Use the 'SQL Server Management Studio ' menu in Start | All Programs to delete
it.
To delete the Historian database:
1 First open the “SQL Server Management Studio” program by following the link shown below:
2 Then click Connect.
IN-128 OI/EN IN/C57

Set in server name (Computer name),

that is OWSM or OWSR for Windows
2000 systems, OWSMXP or OWSRXP
or WindowsXp systems
3 Expand the SQL Server (OIM in the figure) & expand the Databases.
4 Right-click on Historian and select Delete.
5 The Delete Object window will appear with Historian selected. Click OK to delete.
OI/EN IN/C57 IN-129

5.4 OI SERVER WATCH

Uninstall OI Server Watch only if you wish to remove it once and for all from the PC. This can only be done
using the Control panel’s Add/remove programs function. Make sure that OI Server Watch is stopped
beforehand. “Uninstall OI Server Watch” only removes the files created upon installation. The files created
later while using OI Server Watch (such as Oiserverwatch.txt) are not deleted.
To cancel the use of OI Server Watch as a service without uninstallation and reinstallation, just set it to
Disabled in the Services manager.
IN-130 OI/EN IN/C57

6 AUTOMATIC EVENT EXPORT APPLICATION

"Automatic Event Export" is an add-on application delivered as part of the DS Agile OI package that allows
logging system events into a configurable text file.
The application generates text-format log files according to the structure defined in its associated xml file. A
text viewer is also included in order to display and print the generated log files.
Installation of the Automatic Event Export application
Under Windows XP, first make sure that .Net framework 3.5 is installed on the PC.
1 Install the Automatic Event Export application by running the setup file "DSAgile AEE 1.x.x.x.exe"
provided in the Programs directory of the DS Agile OI installation files
2 Click Next.
OI/EN IN/C57 IN-131

3 Keep or change the installation folder if required (this should not be necessary) then click Next.
4 Similarly, keep or change the path for the launch shortcut in the Windows Start/Programs menu, then
click Next.
IN-132 OI/EN IN/C57

5 If you would like a shortcut icon created on the desktop, tick the box Create a desktop icon, otherwise
leave it unticked. Click Next.
6 Click Install.
OI/EN IN/C57 IN-133

7 When the setup process is complete, click Finish.

When the application is installed, it can be launched from the chosen folder in the Windows Start menu,
using this icon:
IN-134 OI/EN IN/C57

TextViewer
The installation procedure for the TextViewer application is almost identical to that of the Automatic Event
Export application. To install the application, launch "DSAgile OI TextViewer 1.x.x.x.exe" from the same
Programs directory, then keep clicking Next (unless you want to change a path) until the last screen, click
Finish when the last screen is displayed.
The command line used to launch the TextViewer application must include either:
• the path of the folder containing the text files to view,

or
• the path and name of a specific text file, for instance the permanent output file as defined in the
EventExport.xml configuration file.
To customise the launch icon in the Windows Start menu, right click it and select Properties in the
contextual menu. Then in the Target field, add the path and name of the folder or file, using double quotation
marks. Examples:
"C:\Program Files\Alstom\DCS\OI\TextViewer\TextViewer.exe" "C:\Output"
"C:\Program Files\Alstom\DCS\OI\TextViewer\TextViewer.exe" "C:\Output\eventToday.txt"
The Viewer can also be configured to be launched from DS Agile OI as an external application, using buttons
or function keys (see OI/EN AP).
The path and name of the folder or file to display must be entered in the Parameters field of the Run Appli.
attributes window, as in the examples below:
OI/EN IN/C57 IN-135

Example of Event Viewer launched using buttons on the OI main view
IN-136 OI/EN IN/C57

Configuration of the log file format

If the default installation folder was not changed during setup, the configuration file, AutoEventExport.xml,
can be found in the folder: C:\Program Files\Alstom\DCS\OI\AutoEventExportApp.
Modify this configuration file according to the desired content and layout of the target log export file and
check its validity against the xml schema provided in the same folder: AutoEventExport.xsd. Most standard
xml editors will provide this facility. An alternative is to use the W3C xml schema validator on their website
(http://www.w3.org/2001/03/webdata/xsv).
The available structure and format options are described below.
EventExport.xml configuration file
If the default installation path was not changed during setup, this configuration file is available in the folder
C:\Program Files\ALSTOM\DCS\OI\EventExportApp\EventExport.xml
The XML file contains the following configuration:
Tag Name Description Example
Path and name of the folder into which the data is
OutputFolder <OutputFolder>C:\Output\</OutputFolder>
saved
EventFileName Name of the permanent output file (eventToday.txt) <EventFileName>eventToday.txt</EventFileName>
<DailyFileName> Event_dd-MM-
DailyFileName Name of the file to be generated daily at 12:00 AM
yyyy</DailyFileName>
Date format in the event file (e.g.: yyyy-MM-dd)
d - Day of the month, from 1 to 31.
dd - Day of the month, from 01 to 31.
M - Month, from 1 to 12.
MM - Month, from 01 to 12.
EvtDateFormat MMM - The abbreviated name of the month <EvtDateFormat>yyyy-MM-dd</EvtDateFormat>
MMMM - The full name of the month
y - Year, from 0 to 99.
yy - Year, from 00 to 99.
yyy - Year, from 000 to 999
yyyy - Year, as a 4-digit number
Time format in the event file (e.g.: HH:mm:ss.fff)
h - Hours, using a 12-hour clock from 1 to 12.
hh - Hours, using a 12-hour clock from 01 to 12.
H - Hours, using a 24-hour clock from 0 to 23.
HH - Hours, using a 24-hour clock from 00 to 23.
m - Minutes, from 0 to 59.
mm - Minutes, from 00 to 59.
EvtTimeFormat <EvtTimeFormat>HH:mm:ss.fff</EvtTimeFormat>
s - Seconds, from 0 to 59.
ss - Seconds, from 00 to 59.
f - Tenths of a second.
ff - Hundredths of a second.
fff - Milliseconds.
ffff - Ten-thousandths of a second.
fffff - Hundred-thousandths of a second.
ffffff - Millionths of a second.
Number of months after which the event file should be
FileDeletionInterval <FileDeletionInterval>6</FileDeletionInterval>
deleted
EventSeparator Symbol separating the events in the file (e.g. ";") <EventSeparator>;</EventSeparator>
OI/EN IN/C57 IN-137


Data elements which should be present in an event
line
A line can contain one or more child nodes called
"Items" <LineFormat>
The item child nodes can only contain the following <Items>Date</Items>
values <Items>Time</Items>
<Items>Origin</Items>
LineFormat • Date
<Items>ObjectName</Items>
• Time <Items>AreaName</Items>
• ObjectName <Items>EventMessage</Items>
</LineFormat>
• Origin
• AreaName (ie: <Origin>/<ObjectName>)
• EventMessage
Localisation data, to be inserted at the beginning of
Localisation <Localisation>ST10 BARKERYD</Localisation>
the event file.
<DefaultEvent>FT93 BARKERYD NYTT
DefaultEvent The First event to be added before the OI events.
DYGN</DefaultEvent>
Number of minutes between data retrievals. In order
to avoid a shortened last refresh time at the end of the
RefreshTime 24-hour period, it is recommended to choose a value <RefreshTime>15</RefreshTime>
that is a whole number divisor of 1440 (total number of
minutes in a 24-hour period).
Locale ID number for the language to be used in the
output file.
It must be either one of the two languages configured
in the database.
The Event messages will be created in both
languages in the Database.
The languages currently available are the following:
Chinese 2052
English 1033
LocaleID French 1036 <LocaleID>1033</LocaleID>
German 1031
Greek 1032
Italian 1040
Polish 1045
Portuguese 2070
Romanian 1043
Russian 1049
Spanish 1034
Swedish 1053
Turkish 1055
Number of minutes to wait before aggregating data for
the period defined at RefreshTime.
For instance:
RedundancyDelay If, when reading events dated up to 9:15 AM, this <RedundancyDelay>5</RedundancyDelay>
value is set to 5, the data will be collected at 9:20 AM.
This to ensure that all the data from both OIs is
collected in case of a redundancy lapse.
Number of minutes to wait before aggregating data
after the end of a day.
If the data was read at 12:00 AM, some of it could be
DayChangingOffset <DayChangingOffset>1</DayChangingOffset>
missed.
This delay is applied to ensure that all of the data for
the day is included in the file.
IN-138 OI/EN IN/C57


It contains the list of data points to be exported into
EventToday.txt
<DataList>
It can contain one or more child nodes called <DataPoint>
DataPoint <AreaName>TEST IEC 61850/Scs/Ethernet
The DataPoint structure is as follows: network/D0379</AreaName>
<ObjNameList>
DataList
<ObjName>OI client link</ObjName>
Child Node name Description <ObjName>Redundancy mode</ObjName>
Contains the area name to </ObjNameList>
AreaName </DataPoint>
be filtered
</DataList>
May contain one or more
ObjNameList
ObjName child nodes
xml file sample (default settings)

<?xml version="1.0"?>
Configuration
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="AutoEventExport.xsd">
<OutputFolder>C:\temp\</OutputFolder>
<EventFileName>eventToday.txt</EventFileName>
<DailyFileName>File_dd-MM-yyyy</DailyFileName>
<EvtDateFormat>yyyy-MM-dd</EvtDateFormat>

<EvtTimeFormat>HH:mm:ss.fff</EvtTimeFormat>

<FileDeletionInterval>6</FileDeletionInterval>
<EventSeparator>;</EventSeparator>
<LineFormat>
<Items>Date</Items>
<Items>Time</Items>
<Items>AreaName</Items>
<Items>EventMessage</Items>
</LineFormat>
<Localisation>ST10 BARKERYD</Localisation>
<DefaultEvent>FT93 BARKERYD NYTT DYGN</DefaultEvent>
<RefreshTime>15</RefreshTime>
<LocaleID>1033</LocaleID>
<RedundancyDelay>5</RedundancyDelay>
<DayChangingOffset>1</DayChangingOffset>
<DataList>
<DataPoint>
<AreaName>TEST IEC 61850/Scs/Ethernet network/D0379</AreaName>
<ObjNameList>
<ObjName>Redundancy Status</ObjName>
<ObjName>Redundancy mode</ObjName>
</ObjNameList>
</DataPoint>
<DataPoint>
<AreaName>TEST IEC 61850/Scs/Ethernet network/C264N5</AreaName>
<ObjNameList>
<ObjName>Device link</ObjName>
</ObjNameList>
</DataPoint>
</DataList>
</Configuration>
OI/EN IN/C57 IN-139

Running the Automatic Event Export Application

The application can be launched by executing the binary file "AutoEventExportApp.exe". In order to ensure
that is it permanently active, add its shortcut to the Programs|Startup menu.
The application will run as a tray application
If you right click its tray icon , the contextual menu contains 2 items:
• Exit – To close the application

• About – To display the About information window
Note: If the application is running in both the main OI and the redundant OI, set a redundancy delay on one PC and no
delay on the other. (RedundancyDelay in EventExport.xml) in order to avoid concurrent access to the file.
CHANGES TO THE XML CONFIGURATION FILE:

Any changes to the xml configuration file will only take effect after the Automatic Event
Export application is restarted.
Since changes to the xml file will affect the contents and layout of the exported log file,
we strongly advise that the event file be removed from the log folder before restarting the
application to avoid inconsistencies within the exported log file.
IN-140 OI/EN IN/C57

ADJUSTMENTS
OI/EN AJ/C57
DS Agile Operator Interface Adjustments
Contents
2 CUSTOMIZING THE DS AGILE OI TOOLS 4

2.1 TOOL.INI File structure 4
2.2 TOOL.INI Default Values 5
2.3 Multi-screen Snapshot tool 6
3 AUTOMATIC PRINT-OUT AT START-UP 7
4 DUAL NETWORK CARD ADJUSTMENTS 9
5 BAY LOCAL OI 19
5.1 Windows XP Embedded adjustments 19
5.1.1 SQL Configuration 19
5.1.2 CSV files 19
5.2 Agency 20
6 ADOBE READER ADJUSTMENTS 21
7 PC LANGUAGE AND CHARACTER SETS 23
OI/EN AJ/C57 AJ-1

Adjustments DS Agile Operator Interface
AJ-2 OI/EN AJ/C57


This document is a chapter of the DS Agile Operator Interface (OI) documentation. It describes the
parameters that you can modify for the DS Agile OI Tools.
• The installation of the application on Bay Local OI requires special adjustments.
OI/EN AJ/C57 AJ-3

2 CUSTOMIZING THE DS AGILE OI TOOLS

Using the DS Agile OI toolbar, the operator can launch various applications ("tools") in addition to the SMT.
The available applications can be accessed using the Tools button in the toolbar. In order to make
applications accessible from the Tools button, the relevant parameters must be set in the TOOL.INI file.
The Multi-screen snapshot tool is configured by editing an xml file.
2.1 TOOL.INI FILE STRUCTURE

The Tools.ini file is located in the C:\Program files\ALSTOM\DCS\OI\Client\Tools folder. Windows
Notepad can be used to open and edit the TOOL.INI file.
The structure of TOOL.INI must be as follows:
[SMT]
CmdLine=
ToolFullPath=<SMT full path>
WorkingDirectory=<optional working directory>
Arguments=<specific parameters>
Admin=<admin rights>
[TOOLS]
NumberOfTools=<number of configured tools>
Tool<n>=<name of the tool n>
[<name of the tool n>]
CmdLine=
ToolFullPath=<tool n full path>
WorkingDirectory=<optional working directory>
Arguments=<specific parameters>
Admin=<admin rights>
Definitions:
<SMT full path> and <tool n full path> are strings with no quotes. They describe the full path of
the executable program. These strings are set during the installation procedure and are required to configure
the DS Agile OI Client.
<optional working directory> is a string that describes whether the tool uses a specific working
directory. This string is not mandatory for the DS Agile OI Client.
<specific parameters> is a string that transmits additional parameters to the tool. This string is not
mandatory for the DS Agile OI Client.
<admin rights> is an integer in the range [1, 64]. It limits access in agreement with the rights of the
operator.
<number of configured tools> is an integer in the range [0,255]. Only the file generator uses this
integer. It represents the total number of tools that are available under the “Tools" button. The SMT tool is
always present. The value 0 shows that no tools other than the SMT are available.
<n> is the number of the tools. It is an integer between 1 and <number of configured tools>.
<name of the tool n> is the name of the tool <n> as it is shown under the "Tools" button.
AJ-4 OI/EN AJ/C57

2.2 TOOL.INI DEFAULT VALUES

By default, three applications are made available under the "Tools" button: Windows Notepad, Windows
Explorer and Microsoft Word:
[SMT]
CmdLine=
ToolFullPath=NOTEPAD.EXE
WorkingDirectory=C:\
Arguments=
Admin=58
[TOOLS]
NumberOfTools=3
Tool1=Notepad
Tool2=Explorer
Tool3=Word
Tool4=
Tool5=
Tool6=
Tool7=
Tool8=
Tool9=
Tool10=
[Notepad]
CmdLine=
ToolFullPath=NOTEPAD.EXE
WorkingDirectory=C:\
Arguments=
Admin=58
[Explorer]
CmdLine=
ToolFullPath=C:\WINNT\explorer.exe
WorkingDirectory=
Arguments=
Admin=58
[Word]
CmdLine=
ToolFullPath=C:\Program Files\Microsoft
Office\Office\WINWORD.EXE
WorkingDirectory=C:\temp
Arguments=
Admin=58
IMPORTANT:
The name of the applications must be spelled identically, including the case, in the
[TOOLS] list and in the corresponding parameter set headings (see above).
OI/EN AJ/C57 AJ-5

2.3 MULTI-SCREEN SNAPSHOT TOOL

Some of the Multi-screen snapshot tool parameters are settable. To do so, edit this xml file:
C:\Program Files\ALSTOM\DCS\OI\Client\OISnapShot\OISnapShot.exe.config
Parameters:
PARAMETER DESCRIPTION DEFAULT VALUE
The folder that contains the saved screenshots. Specify a Desktop: the saved files are
SaveRootPath
valid folder on the hard drive placed on the user’s desktop
A flag that indicates whether the PC should overwrite the False: the computer does not
Overwrite
files or if it should increment the filenames. overwrite the saved files
ThumbnailWidth The width in pixels of each screen thumbnail 160
ThumbnailHeight The height in pixels of each screen thumbnail 120
When the AutoRefresh option is enabled, this is the time, in
AutoRefreshDelay 2000
ms, between two refresh cycles
IMPORTANT:
If the autorefresh option is enabled, the Snapshot tool's thumbnail window reappears on
top of the mimic every time a NEW refresh cycle starts. This window is not included in
the screenshot and not printed.
AutoRefreshEnabled The auto-refresh feature for the thumbnails False
AJ-6 OI/EN AJ/C57

3 AUTOMATIC PRINT-OUT AT START-UP

When a DS Agile OI server or an IED reboots or restarts after powering down, only system events such as
the relevant disconnection/reconnection would normally be printed on the SOE printer.
By default, datapoints’ binary states retrieved by the general interrogation (GI) that follows will not be printed,
unless a specific adjustment is made.
In order to specifically allow general interrogation states to be automatically printed after a reboot or power-
up, it is necessary to add and the following key to the Windows registry:
HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\OI\PrintGiPolicy, type DWORD
• If this key is absent or different from 1, the GI’s states are not printed.
• If this key is present and set to 1, the GI’s states are printed.
Procedure
• Run “Regedit” from the Windows Start menu.

• Open the folder HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\OI\
If the registry key PrintGiPolicy is already present, set it to 1
If the registry key PrintGiPolicy is not present, create it:
Right-click on the OI folder, click New, then DWORD Value:
OI/EN AJ/C57 AJ-7

Name the newly created value PrintGiPolicy and set it to 1:
• Click OK, exit the Registry and reboot the PC.
AJ-8 OI/EN AJ/C57

4 DUAL NETWORK CARD ADJUSTMENTS

If any one of DS Agile OI main server, backup server and stand alone OI client is installed in PCs with dual
network cards and one of the network cards is configured with DNS, the following setting procedure must be
followed on all the PCs with dual network cards that host DS Agile software.
Windows XP:
• In the Control Panel, find Network Connections and click on the relevant icon.
• Select Advanced>Advanced Settings:
OI/EN AJ/C57 AJ-9

• In the window, use the arrow button to move the DS Agile network connection to the top of the list of
connections:
Windows first uses a host file to resolve network names before it uses the DNS server to resolve the names.
In the PC with dual network cards, the network names and IP addresses of the DS Agile configuration should
be added to the host file to ensure correct name resolution.
• Open the file C:\WINDOWS\system32\drivers\etc\hosts in Notepad and add the DS Agile

network name and corresponding IP address (do this on the main server and on the backup server,
add main and backup information on a standalone client):
AJ-10 OI/EN AJ/C57

• Select Start >Accessories > Command Prompt (or run cmd)

• In the CMD window, type the command “route print” and press Enter to get a routing table with the
addresses of the network cards used in the PC (“Interface” column) and their corresponding values
(“Metric” column):
The network card used for DSAgile must have the lowest metric value of all the networks.
To set the metric value, right-click the DSAgile network icon and select Properties in the
contextual menu:
Select the TCP/IP protocol and click the Properties button:
OI/EN AJ/C57 AJ-11

The TCP/IP protocol panel is displayed:
Click the Advanced button
AJ-12 OI/EN AJ/C57

Untick the Automatic metric box and set the Interface metric box to a value lower that the values
of the other networks:
Windows 7:
Place the DSAgile network connection first in the order of network adaptors
• In the Control Panel, click Network and Internet

• In the Network and Internet window, click Network and Sharing Center
• In the Network and Sharing Center window, click Change adapter settings:
OI/EN AJ/C57 AJ-13

• In the Network Connections window, either press the F10 key or select Advanced Settings in the
Advanced menu:
• Use the green arrow buttons to move the DSAgile network connection to the top of the list of
connections.
AJ-14 OI/EN AJ/C57

Add details of DSAgile machine network names and corresponding IPs in the windows host file.
Windows first uses a host file to resolve network names before it uses the DNS server to resolve the names.
In the PC with dual network cards, the network names and IP addresses of the DS Agile configuration should
be added to the host file to ensure correct name resolution.
• Open the file C:\WINDOWS\system32\drivers\etc\hosts in Notepad and add the DS Agile

network name and corresponding IP address.
In the “hosts” file of the PC hosting the main server, add the network name and IP address of the
backup server.
In the “hosts” file of the PC hosting the backup server, add the network name and IP address of
main server.
In the “hosts” file of the PC hosting the standalone clients, add the network names and
corresponding IP addresses of the main server and backup server.
OI/EN AJ/C57 AJ-15

Configure the Metric value for the DSAgile network
• Select Start >Accessories > Command Prompt

• In the CMD window, type the command “route print” and press Enter to get a routing table with the
addresses of the network cards used in the PC (“Interface” column) and their corresponding values
(“Metric” column):
The network card used for DSAgile must have the lowest metric value of all the networks.
AJ-16 OI/EN AJ/C57

If this metric value is not the lowest then follow the steps below to set a lower metric value:
• In the Control Panel, double-click Network and Internet

• In the Network and Internet window, double-click Network and Sharing Center
• In the Network and Sharing Center window, click Change adapter settings:
• In the Network Connections window, right-click the DSAgile network icon and select Properties in
the contextual menu:
• Select the TCP/IP protocol and click the Properties button.

• Click the Advanced button
• Untick the Automatic metric box and set the Interface metric box to a value lower that the values of
the other networks.
OI/EN AJ/C57 AJ-17

AJ-18 OI/EN AJ/C57

5 BAY LOCAL OI
5.1 WINDOWS XP EMBEDDED ADJUSTMENTS

Using a text editor, open the S2KLoader.xml file in
Program Files\ALSTOM\DCS\OI\Server\Configuration\DBID1\S2kHMIConfig\
S2K-HMI-SRV\S2KServer (if the configuration is in DBID1).
To find out whether the configuration is loaded in DBID1 or DBID2, check the
HKEY_LOCAL_MACHINE\Software\ALSTOM\DCS\Current key in the Windows Registry (see OI/EN MF).
This file defines the name of the SQL Server and the location of the CVS files.
5.1.1 SQL CONFIGURATION

Find the "SQLServerMachine" string. There are several occurrences like the one below:
<attribute>
<name dt:dt="string">SQLServerMachine</name>
<value dt:dt="string">OIXPE</value>
</attribute>
…
In each occurrence, replace OIXPE with FILESERV.
5.1.2 CSV FILES

Seek the "S2KArchive" string. The block looks like this:
<Object class="S2KArchive"pathname="Archives.ArchivesDSAgile">
<GUID dt:dt="string">{00000000-41f6-3f36-0317-5d54598b0460}</GUID>
<attribute>
<name dt:dt="string">ArchiveFolder</name>
<value dt:dt="string">\\OIXPE\SharedWorkspace\ArchiveDS Agile</value>
</attribute>
…
Change the value:

<value dt:dt="string">\\OIXPE\SharedWorkspace\ArchiveDSAgile</value>
to:
<value dt:dt="string">P:\SharedWorkspace\ArchiveDSAgile</value>
Save the file, and start DS Agile OI Server and OI Client.
OI/EN AJ/C57 AJ-19

5.2 AGENCY
Open the file:
Program Files/ALSTOM/DCS/61850agency/api/include/OdInclude.h
For the commands issued through Bay Panel OI to be considered by the computer as local commands (i.e.
front local panel) the xx_CONTROL field must be equal to 1.
enum __MIDL___MIDL_itf_rpcagency_0000_0027
ODD_NOT_SUPPPORTED = 0,
ODD_BAY_CONTROL = ODD_NOT_SUPPPORTED + 1,
ODD_STATION_CONTROL = ODD_BAY_CONTROL + 1,
ODD_REMOTE_CONTROL = ODD_STATION_CONTROL + 1,
ODD_AUTOMATIC_BAY_CONTROL = ODD_REMOTE_CONTROL + 1,
ODD_AUTOMATIC_STATION_CONTROL = ODD_AUTOMATIC_BAY_CONTROL + 1,
ODD_AUTOMATIC_REMOTE_CONTROL = ODD_AUTOMATIC_STATION_CONTROL + 1,
ODD_MAINTENANCE_CONTROL = ODD_AUTOMATIC_REMOTE_CONTROL + 1,
ODD_PROCESS_CONTROL = ODD_MAINTENANCE_CONTROL + 1}
AJ-20 OI/EN AJ/C57

6 ADOBE READER ADJUSTMENTS

The Help file of the DS Agile Operator Interface is a .pdf file that is opened using Adobe (Acrobat) Reader.
When using the most recent versions of this software, it is necessary to adjust the security settings so that it
can be launched via DS Agile OI.
Adobe Reader version X
In the Edit menu, select Preferences. In the General pane, make sure that the box Enable Protected Mode
at startup is unticked.
If it was selected and you had to untick it, a dialog will be displayed in which you will have to confirm this
action.
Adobe Reader will need to be restarted to this change to take effect.
OI/EN AJ/C57 AJ-21

Adobe Reader version XI

In the Edit menu, select Preferences. In the Security (Enhanced) pane, make sure that the box Enable
Protected Mode at startup is not ticked.
If it was selected and you had to untick it, a dialog will be displayed in which you will have to confirm this
action.
Adobe Reader will need to be restarted to this change to take effect.
AJ-22 OI/EN AJ/C57

7 PC LANGUAGE AND CHARACTER SETS

When DS Agile OI is to run on a PC set up for a language that requires a specific character set, such as
Swedish for instance, the PC should be configured for the same language 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:
OI/EN AJ/C57 AJ-23

• Go to the Advanced tab-pane, 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
AJ-24 OI/EN AJ/C57

APPLICATION
OI/EN AP/C57B
DS Agile Operator Interface Application
Contents
2 DS AGILE OI CONFIGURATION SCOPE 6

2.1 General DS Agile system configuration 6
2.2 DS Agile OI configuration 6
2.3 Spare object 7
3 DS AGILE OI CONFIGURATION 9
3.1 Setting general system configuration relevant to OI 9
3.2 Adding a DS Agile OI into a DS Agile architecture 13
3.2.1 Adding a DS Agile OI Server 14
3.2.2 Adding a DS Agile OI Client 17
3.2.3 Defining a Bay Local OI 19
3.2.4 Defining a redundant DS Agile OI Server (optional) 19
3.3 DS Agile OI printer 21
3.3.1 General 21
3.3.2 Types of printer 22
3.3.3 Sequence Of Event (SOE) printer 22
3.3.4 Log Book (LB) printer 23
3.3.5 Adding a DS Agile OI printer 27
3.3.6 Attributes of a DS Agile OI printer 27
3.3.7 Redundant DS Agile OI printer settings 31
3.3.8 Use of network printers together with OI Hot Redundancy 31
3.4 DS Agile OI on the SBUS 31
3.4.1 DS Agile OI Server connection to other SBUS sub-systems 31
3.4.2 Address mapping definition of SBUS 33
3.4.3 Overview of the LD0 of DS Agile OI Server in IEC 61850-8-1 mapping 34
3.4.4 Datapoint on SBUS addressing 34
3.5 DS Agile OI klaxon (Horn button) 35
3.6 Setting system information for DS Agile OI components 36
4 DATAPOINTS FOR DS AGILE OI 41

4.1 Short and long name datapoint updates 42
4.2 Datapoint profiles 42
4.2.1 Overview 42
4.2.2 Profile OI-specific attributes 43
4.3 Local archiving of datapoints by DS Agile OI 44
4.3.1 Local archiving definition of event datapoints by DS Agile OI 44
4.3.2 Local archiving definition of alarm datapoints by DS Agile OI 44
4.3.3 Local logging definition of event and alarm datapoints by DS Agile OI 44
4.3.4 Global Alarm Acknowledgement 44
4.3.5 Set the period value 46
5 COLORS, FONTS AND STROKES FOR DS AGILE OI 47

5.1 Color settings 48
5.2 Font settings 50
OI/EN AP/C57b AP-1

Application DS Agile Operator Interface
5.3 Stroke settings 51

5.4 Color settings for alarm management 52
6 DS AGILE OI WORKSPACE 54
6.1 DS Agile OI workspace definition 55
6.2 DS Agile OI window 56
6.3 Standard title banner 57
6.4 Standard command banner 57
6.5 Standard alarm banner 59
6.6 Default mimic of window definition 60
7 DS AGILE OI MIMIC 61
7.1 Mimic 61
7.2 Static part with basic shapes 62
7.2.1 Defining a rectangle property updates 63
7.2.2 Defining a circle 64
7.2.3 Defining a line 65
7.2.4 Defining a polyline 66
7.2.5 Defining a text 68
7.2.6 Defining a variable text 69
7.2.7 Defining an image 73
7.2.8 AutoClose of Mimics 74
7.3 Memo representation 75
7.3.1 Memo bitmaps configuration 75
7.3.2 Memo representation 75
7.3.3 Adding a Memo 76
7.3.4 Attributes of a Memo icon 77
7.4 Dynamic representation using datapoint multistates 78
7.4.1 Datapoint multistate 78
7.4.2 Discrepancy multistates 82
7.4.3 Alarm and audible multistates 84
7.4.4 Text symbol 87
7.5 Graphical object groups 88
7.6 Real-time animation of objects representing measurement values 91
7.7 Optimization 95
7.7.1 Principles 95
7.7.2 Procedure at specification time 96
7.7.3 Re-use procedure 97
8 VIEWERS 99
8.1 DS Agile OI ActiveX 99
8.2 Alarm / event / state viewer 99
8.2.1 Overview of the alarm/event/state viewers 99
8.2.2 Alarm/event/state viewer creation 105
8.3 Trend viewer 113
8.3.1 Overview of the trend viewer 113
8.3.2 Adding trend viewer 115
8.3.3 Setting pre-defined pens 116
8.4 FSS viewer 118
AP-2 OI/EN AP/C57b

8.4.1 Overview of the FSS viewer 118

8.4.2 Adding an FSS viewer 119
9 PROCESS CONTROL MIMIC AND POPUP 123

9.1 Launch action: Binary direct command 123
9.2 Launch action: Analogue direct command 125
9.3 Launch action: Open control popup 126
9.4 Launch action: Open counter popup 130
10 MIMIC CHAINING 132
11 SETTING SOFTWARE LAUNCH ON A SPECIFIC IED 134
12 EXTERNAL APPLICATIONS LAUNCH 136
13 REPORT LAUNCH 138

13.1 How do you do a report? 138
13.2 Create a button to launch a report 138
14 SHORTCUT FUNCTION KEYS 139
15 BAY LOCAL OI 141

15.1 General requirements 141
15.2 Specific configuration 142
15.2.1 Virtual keyboard 142
15.2.2 Configuration of the action buttons in a mimic 143
15.2.3 Configuration of graphic text 143
16 DS AGILE OI RIGHTS DEFINITION 145

16.1 User profiles 145
16.1.1 Overview of user profile modeling 145
16.1.2 View rights 145
16.1.3 Command rights 146
16.1.4 Acknowledgement rights 146
16.1.5 User profile 146
16.2 User right mapping definition on electrical and system topologies 151
16.2.1 Default user right mapping 151
16.2.2 User right mapping 152
16.3 User right mapping definition on mimic 152
OI/EN AP/C57b AP-3

AP-4 OI/EN AP/C57b


The present document is a chapter of the DS Agile OI manual. This document explains how to configure the
DS Agile OI using DS Agile SCE.
To create a template from an existing DS Agile OI, see chapter SCE/EN HI, menu Tools.
OI/EN AP/C57b AP-5

2 DS AGILE OI CONFIGURATION SCOPE
2.1 GENERAL DS AGILE SYSTEM CONFIGURATION

To define a complete DS Agile system, three aspects should be taken into account.
The first is the system topology. It consists in device components that manage the customer’s electrical
process. Generally, this part of the supply concerns Alstom and corresponds to Alstom’s system process
definition to meet customer’s needs.
The second is the electrical topology. It consists in the customer’s electrical process definition in term of
typed electrical devices (transformer, disconnector, circuit-breaker…) that are connected to one another
through busbars or lines. Generally, this part of the supply is relevant to the customer.
The third is the graphical topology. It consists in the mimics and their graphical animation descriptions that
appear at substation control-points (DS Agile operator interface) and bay control-points (LCD at C26x level).
When creating a new configuration using DS Agile SCE, these 3 topologies are automatically instantiated via
root objects:
 A ‘Site’ object for the electrical topology, containing one ‘Substation’ object
 A ‘Scs’ object for the system topology, containing one ‘Ethernet network’ object (Scs is of the acronym
for Substation Control System)
 A ‘Graphic’ object for the graphical topology.
Figure 1: General architecture of a DS Agile configuration in DS Agile SCE
2.2 DS AGILE OI CONFIGURATION

In a general DS Agile system configuration, DS Agile OI is affected by these three topologies:
 Electrical topology (Site): DS Agile OI manages logging, alarms, history of datapoints as defined in
this topology
 System topology (Scs):

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 the devices managing, monitoring and/or
protecting one or more electrical bays.
DS Agile OI consists in direct sub-components (DS Agile OI Server and DS Agile OI Clients) of a System
Group. Moreover, it manages logging, alarms, history of datapoints as defined in this topology. It can be
used as Bay Local OI.
AP-6 OI/EN AP/C57b

 Graphical topology (Graphic): DS Agile OI displays real-time mimics, alarm/event/state panels, real
time or archived trends.
2.3 SPARE OBJECT

At DS Agile SCE level, a spare object is an object created for possible ulterior use or in order to disable an
HMI command.
The label of a spare object is displayed in gray italic text in the Explorer window. The configuration of this
object and of its spare attribute is the same as that of any other object and attribute.
To configure an object as spare, simply set its ‘spare’ attribute to 'Yes'.
Spare objects are not passed on to the generator tools.
Object sparing follows these two rules:
 Objects O2, O3, O4, etc., not individually spared, are considered as spare objects if they are linked,
directly or not, to a spare composite parent object (O1):
OI/EN AP/C57b AP-7

 A relation defined on an object O1, not spare, and linked to a spare object O2, is considered as a
relation with no link:
AP-8 OI/EN AP/C57b

3 DS AGILE OI CONFIGURATION
3.1 SETTING GENERAL SYSTEM CONFIGURATION RELEVANT TO OI

System configuration is done at Scs root. It is relevant to some general behaviours of DS Agile devices.
It applies to these specific attributes:
 Common labels used for control acknowledgement, time quality logging, alarm management logging;
 Alarm management characteristics (alarm processing type, audibility delays, alarm clearing mode per
gravity level);
And to these specific relations:
 Designation of the master clock device in the system. This system device provides the time reference
to all the other devices through the station-bus network.
 Designation of default elementary action rights used by system datapoints of the Scs tree.
 Designation of the substation where the system devices are located.
 Designation of the buffer reports recipients (see section 3.4 DS Agile OI on the SBUS)
DS Agile OI can not be the master clock of the system.
Some attributes of Scs objects concern all the operator interfaces defined under the station network. Those
attributes are listed below:
(1) Order steps labels: labels regarding order execution steps (used for order logging)
(2) Control acknowledgement labels: used for order logging and alarm
(3) Timestamp quality labels: used for logging and alarm
(4) Default alarm processing type (State basis / Gravity level basis / Data basis):
 “state basis” alarm management: one alarm for each state is displayed
 “gravity level basis” alarm management: only one alarm for each gravity level is displayed. The
previous one is replaced by the current one with same gravity level
 “data basis” alarm management: only the last alarm is displayed; the previous one is replaced by
the current one
(5) Archived alarm (No/Yes): attribute indicating whether alarms are archived at DS Agile OI level
(6) Display of datapoint state
(7) Audibility acknowledgement mode (Manual/Automatic): this attribute indicates whether the klaxon
(relevant to the audible alarm) is automatically turned off after a given time period (see next attribute)
without any user action.
(8) audibility delay (1 to 60 s): Time-delay for audibility automatic acknowledgement mode (see previous
attribute)
(9) Substation mode dependency for audibility (No/Yes): If this attribute is set to Yes audible alarms are
treated as follows:
 When the substation control mode changes from Local to Remote, the audible alarms are
automatically disabled: all audible signals stop. This feature prevents useless triggering of audible
signals in remotely controlled substations without local operators,.
 When the substation control mode changes from Remote to Local, the audible alarms are
automatically re-enabled: all audible alarms still present will start generating audible signals again.
(10) Default alarm clearing mode for each gravity level (Manual/Automatic):
An alarm can be configured so as “to be cleared automatically”. It means that when this alarm reaches
OI/EN AP/C57b AP-9

the appropriate state, it is cleared automatically without any operator action. The cases for “automatic
clearing” are:
 the alarm is in the active-acknowledged state and disappears (for events set to trigger an alarm
only upon appearance)
 the alarm is in the inactive-active-unacknowledged state and the operator acknowledges it (for
events set to trigger an alarm only upon appearance and for spurious alarms)
 the alarm is in the inactive-unacknowledged state and the operator acknowledges it (for events set
to trigger an alarm upon appearance and disappearance)
This feature can be configured on a per gravity level basis (cf. these attributes) and on a per alarm basis;
e.g.: all the alarms with a severity level lower than 4 can be “globally” configured so as to be cleared
automatically while the alarms with a gravity level of 4 and 5 can be individually configured to be cleared
automatically or not.
(11) Computer routing attributes
Reserved for
C26x use
S0489ENc
Figure 2: General attributes of an SCS
AP-10 OI/EN AP/C57b

Reserved for
C26x use
(1)
S0490ENc
Figure 3: Labels attributes of an SCS
OI/EN AP/C57b AP-11

(2)
(3)
Figure 4: Labels attributes of an SCS (cont'd)
AP-12 OI/EN AP/C57b

(4)
(5)
(6)
(7)
(8)
(9)
(10)
Figure 5: Alarm attributes of an SCS
(11)
Figure 6: Computer routing attributes of an SCS
At DS Agile OI level, the default alarm processing type is not significant because alarm processing is always
done on a ‘data basis’ for the operator interface.
Audibility features defined at Scs level are not applicable to DS Agile OI’s configuration.
3.2 ADDING A DS AGILE OI INTO A DS AGILE ARCHITECTURE

There are two types of DS Agile OI:
 A Standard DS Agile OI is composed of at least of 2 applications:

 DS Agile OI Client which provides the display part of the operator interface. It must be connected to
a:
 DS Agile OI Server that feeds DS Agile OI Clients with process real-time values to animate mimics.
DS Agile OI Server manages centralized logging, archiving and alarm functions.
The protocol used between DS Agile OI Server and DS Agile OI Client is OPC. Generally, it is supported by
means of the station bus. Up to 8 DS Agile OI Clients can be connected to a DS Agile OI Server.
OI/EN AP/C57b AP-13

To simplify data modelling, DS Agile OI Clients are considered as being connected to the station bus, and so
is DS Agile OI Server. An extra relation defines which server feeds the client.
Even if DS Agile OI Client and DS Agile OI Server applications are installed on the same PC, they are
considered as separate system devices at DS Agile SCE level and must be configured individually.
 Bay (Local) OI:

The Bay Local OI is seen as a single device, composed of one client and one server. No new OI Clients can
be added. The server cannot be redundant.
3.2.1 ADDING A DS AGILE OI SERVER

A DS Agile OI Server is added under DS Agile SCE from the contextual Objects entry window associated
with the Ethernet network level by double-clicking on OI Server (or right-clicking on it and then on Add).
Figure 7: Adding an OI Server
AP-14 OI/EN AP/C57b

Default components of a DS Agile OI Server

After adding a DS Agile OI Server, its sub-tree with the default components is as follows:
(1)
Figure 8: Default components of an OI Server
(1) The folder System infos groups all general system datapoints for the DS Agile OI Server (see Setting
system information for DS Agile OI components)
3.2.1.1 ATTRIBUTES OF A DS AGILE OI SERVER

After adding a DS Agile OI Server on the Ethernet network, some of its attributes must be updated.
General attributes
Figure 9: General attributes of an OI Server
(1) short name and long name: used for logging, alarms, …
(2) default mean calculation period (5 / 10 / 15 / 30 minutes): base period used for mean calculation
when required
(3) TCP/IP address and network name (limited to 15 characters) of the DS Agile OI Server; the name
must be different than that of the HMI.
(4) backup range unit (None (no backup)/Day/Week/Month): DS Agile OI Server can backup its historic
(events and value) at a given time interval which unit is set by this attribute.
(5) backup range (range [1,60], step 1): this attribute defines the backup time interval if the previous
attribute is not set to 'None’.
OI/EN AP/C57b AP-15

(6) event historic period (day) and value historic period (day) (range [1, 600], step 1): these attributes
define for Event Historic Data Base and Value Historic Data Base the number of days during which
the oldest record is kept in these databases.
Configuration rules and checks
 The TCP/IP address value of a device must be unique among all the devices of an Ethernet Network
(except for DS Agile OI Server and DS Agile OI Client).
 The network name value of a device must be unique among all the devices of an Ethernet Network
(except for DS Agile OI Server and DS Agile OI Client).
Miscellaneous attributes
(1)
(2)
Figure 10: Miscellaneous attributes of an OI Server
(1) AP-Title: MMS parameter. Always set at the default value.

(2) AE-Qualifier: Extension of the IP address if several server applications are using the same agency. It
will start at 1 for the first application, then 2 for the second and so on… up to a maximum of 50.
Locating a DS Agile OI Server in a substation (mandatory)
Each DS Agile OI Server has to be located in a specific substation. This is done by entering the mandatory
relation (1) is located in:.
(1)
Figure 11: Locating an OI server in a substation
AP-16 OI/EN AP/C57b

3.2.2 ADDING A DS AGILE OI CLIENT

A DS Agile OI Client is added from the contextual Objects entry window associated with the Ethernet
network level by double–clicking on OI Client (or right-clicking on it and then on Add).
Figure 12: Adding an OI client
3.2.2.1 USER LOG NOTIFICATION

It is possible to add an optional SPC datapoint which will indicate whether the OI workstation is currently
used by an operator: notify login/logoff SPC. If this feature is configured, a command is automatically sent
onto an SPC datapoint indicating that a user has logged on (SET signal) or off (RESET signal) an OI Client.
This notification can be used as part of a logic scheme (ISaGRAF or FBD automation).
The notify login/logoff SPC datapoint is added from the contextual Objects entry window associated with
the OI client by double–clicking on notify login/logoff on: SPC Electrical datapoint (or right-clicking on it
and then on Add).
It can be configured even if the log-off operation is automatic (after an inactivity time-out).
The relation is optional but it must be defined under each OI Client for which the log information is required.
Regardless of whether the notify login/logoff SPC relation is added to one or several OI Clients, each one
must be linked to its own dedicated electrical SPC. These SPCs must have an IEC 61850-8-1 address.
The SPC(s) could then be linked to an automation input as in the example given in the figure below.
OI/EN AP/C57b AP-17

Figure 13: Linking a notify login/logoff SPC datapoint to an FBD input
3.2.2.2 DEFAULT COMPONENTS OF A DS AGILE OI CLIENT

After adding a DS Agile OI Client, its sub-tree with the default component is as follows:
Figure 14: Default component of an OI Client
(1) Folder System infos, that groups all general system datapoints of the DS Agile OI Client (see section
3.6 Setting system information for DS Agile OI components).
AP-18 OI/EN AP/C57b

3.2.2.3 ATTRIBUTES OF A DS AGILE OI CLIENT

After adding a DS Agile OI Client on an Ethernet network, some of its attributes must be updated. These
attributes are listed below.
(1)
(2)
Figure 15: General attributes of an OI Client
(1) short name and long name: used for logging, alarms, …
(2) TCP/IP address and network name: if DS Agile OI Client and DS Agile OI Server are installed on the
same PC, their alias names and TCP/IP addresses must be the same ones.
 The TCP/IP address value of a device must be unique among all the devices per Ethernet Network
(except for DS Agile OI Server and DS Agile OI Client if they are installed on the same PC).
 The network name value of a device must be unique among all the devices per Ethernet Network
(except for DS Agile OI Server and DS Agile OI Client if they are installed on the same PC).
A DS Agile OI Client must be linked to a DS Agile OI workspace that defines the template and the mimics
used at DS Agile OI Client level. This is done by entering the mandatory relation (2) has for workspace:
Figure 16: Setting workspace of an OI client
3.2.3 DEFINING A BAY LOCAL OI

A Bay Local OI is added from the contextual Objects entry window associated with the Ethernet network
level by double-clicking on Bay OI (or right-clicking on it and then on Add).
3.2.4 DEFINING A REDUNDANT DS AGILE OI SERVER (OPTIONAL)

To define a redundant DS Agile OI Server:
 Create the main DS Agile OI Server, considered as master one;

 Right-click on OI Server: a contextual menu opens: click on Create backup (1)
OI/EN AP/C57b AP-19

Figure 17: Defining a redundant OI Server (creation action)
Then:
 Another DS Agile OI Server (1), considered as the slave, is automatically created with an implicit
relation of backup (2) between the two DS Agile OI Servers.
 The attributes of the backup OI Server are the same as those of the main OI Server and are locked,
except for its short name, long name, TCP/IP address and network name which must be correctly
updated.
Figure 18: Defining a redundant DS Agile OI (once created)
AP-20 OI/EN AP/C57b

3.3 DS AGILE OI PRINTER
3.3.1 GENERAL
3.3.1.1 PRINTING MECHANISMS

The DS Agile OI printers are managed in a real-time printing mode.
DS Agile OI printers’ mechanisms at system level ensure:
 chronological printing: all synchronized information are printed in a chronological order. A latency
delay is configured to sort information.
 printing reliability: no data is lost if the printer remains unavailable for a duration less than the printer’s
buffer length; if the printer switches to faulty mode, when it is ready again it will reprint the events
recorded before failure during the recovery length period
 printing availability, afforded by printer redundancy. The first printer is designated “Main” printer, and
the second is designated “Spare” printer. The “Main” printer performs all printing operations whenever
it is available. If the “Main” printer fails, the “Spare” printer takes over and continues to print events
even if the “Main” printer becomes available again. The printed events are recorded during the
recovery length time period (defined in configuration as a minimum value, the recovery length time
period must be consistent with the error detection time of the printer spooler). If the current printer
switches to faulty mode, the spare printer prints all the events recorded during the recovery length
period again.
Recovery Length
latency
Printers Buffer Length Data flow
S0395ENa
Events are printed with their time-stamp and a complete description (location and event description). Time-
stamping is done by the device that detected the event (time-stamping at the source).
Note: In case of DS Agile OI Server redundancy, network printers should be used to avoid loss of data in case one of
the two DS Agile OI Servers shuts down.
3.3.1.2 HEADER & FOOTER STRUCTURE

A header and a footer can be printed on each page. They are composed of two optional lines, separated
from the events by a blank line.
The structure of each header / footer lines is defined in configuration, using the following properties:
 Site name
 Printer name
 Page number
 Free text
The page number is in the range [1..999]. It is reset to 1 after reaching 999, each new day.
OI/EN AP/C57b AP-21

Header line 1
Header line 2
<blank line>
<SOE>/<LB>
<blank line>
Footer line 1
Footer line 2
S0396ENa
3.3.2 TYPES OF PRINTER

There are two types of printers:
 Sequence Of Event (SOE) printer

 Log Book (LB) printer
SOE and/or Log Book printers can be connected using a parallel port or via the Ethernet network.
Parallel and network printers cannot be concurrently used.
In case of OI Hot redundancy, only Ethernet printers may be used.
Please refer to OI/EN TD for the list of compatible printers and their limitations.
3.3.3 SEQUENCE OF EVENT (SOE) PRINTER

Only Binary Inputs (BI) attached to the electrical process can be printed on the SOE printers (SPS, DPS and
MPS datapoints are allowed, System Information and Groups are not). The list of BIs to print is defined in
configuration.
The list of BI states to print can also be defined in configuration. States not printed on the SOE printers are
NOT printed on the LB printer either (if the associated BI is also printed on the LB). The printed information is
also archived.
The five following BI properties can be printed. Each property is separated from the other by one blank
configuration:
 Chronology:
1 character that gives the “out of chronology” status of an event: “<blank>” if the event is printed in the
chronology, “C” if it is not
 Time Stamp:
23 or 25 characters: the following formats are allowed:
 <S> DD/MM/YY hh:mm:ss:mmm
 <S> YY/MM/DD hh:mm:ss:mmm
 <S> MM/DD/YY hh:mm:ss:mmm
 <S> DD/MM/YYYY hh:mm:ss:mmm
 <S> YYYY/MM/DD hh:mm:ss:mmm
 <S> MM/DD/YYYY hh:mm:ss:mmm
AP-22 OI/EN AP/C57b

the <S>character gives the synchronized / not synchronized status of an event: “<blank>” for
synchronized, “*” (configurable) for not synchronized – It is issued from the source time-stamping.
 Origin:
67 characters:
 For BIs defined at the module level, the origin is <substation name>/<voltage level name>/<bay
name>/<module name>
 For BIs defined at the bay level, the origin is <substation name>/<voltage level name>/<bay name>
 For BIs defined at the voltage level, the origin is <substation name>/<voltage level name>
 For BIs defined at the substation level, the origin is <substation name>
Each <xxx name> is defined over 16 characters.
 ObjectName:
35 characters: contains the BI’s long name
 ObjectMessage:
16 characters: contains the BI’s resulting state. Only the resulting states chosen in configuration are
printed. If the BI is also printed on LB, the same chosen states are printed.
For example, one possible arrangement can be:
1 char. 23 or 25 char. 67 char. 35 char. 16 char.
Chronology TimeStamp Origin ObjectName EventMessage

S0397ENa
The selection of the SOE printer destination (1, 2, or both) is made by configuration on a per data basis.
3.3.4 LOG BOOK (LB) PRINTER

The types of events can be:
 Binary inputs (SPS, DPS, MPS, SI and Groups)

 Tap position indication
 Measurement
 Operator action:
 Log-in and log-off
 Devices control
 Alarm acknowledgement / clearing

One or several types of events can be printed: the choice is made by configuration. The selection of the LB
printer destination (1, 2, or both, for printer at system level) is made by configuration on a per data basis.
The list of event states (for BI, Tap Position Indication and measurements) to print can be defined in
configuration. A printed information is also archived.
OI/EN AP/C57b AP-23

The five following properties can be printed. Each property is separated from the other by one blank
configuration:
 Chronology:
1 character: see section 3.3.3 Sequence Of Event (SOE) printer
 Time Stamp:
24 or 26 characters: see section 3.3.3 Sequence Of Event (SOE) printer
 Origin:
67 characters: for BI, TPI, measures, controls and alarms, the origin gives the access path to the
object (see section 3.3.3 Sequence Of Event (SOE) printer)
 ObjectName:
35 characters
 ObjectMessage:
17 characters
On the printer, the object message format will be: "[CLIENT NAME – USER NAME]".
This functionality must be configured using the SCE.
Firstly:
Figure 19: Attributes of the OI printer – 1
This attribute must be set to short area name to leave enough space to print the new information (HMI client
name + operator name).
AP-24 OI/EN AP/C57b

Secondly:
Figure 20: Attributes of the OI printer – 2
The new information is concatenated at the end of object message field . To show this information, the
value of the rank must be different from 0.
OI/EN AP/C57b AP-25

Thirdly:
The user name must be shorter than 36 characters:
Figure 21: User name
Summary:
Program Attribute Value
SCE Origin column content Short area name (on 17 char)
SCE Object message column name ≠0
OI User name ≤ 36
The Origin, ObjectName and ObjectMessage properties contain information that depends on the
associated event type.
Time Object
Printer Events Chronology Origin ObjectName Comment
Stamp Message
SOE, Time BI resulting
Binary Input Chronology Origin BI Name
LB stamping state
The value is given only
for TPI in the following
Tap Position Time TPI state and
LB Chronology Origin TPI name state: valid, forced,
Indication stamping value
substituted, overrange,
threshold violation
The value is given only
for measurement in the
Measure
Time Measurement following state: valid,
LB Measurement Chronology Origin state and
stamping name forced, substituted,
value
overrange, threshold
violation
Operator
Operator Log-in / Time Name Log-in
LB Chronology <blank> <blank>
Log-off stamping Operator
Name Log-off
AP-26 OI/EN AP/C57b

Time Object
Printer Events Chronology Origin ObjectName Comment
Stamp Message
Select Control
value Force, suppress and
Time
LB Control request Chronology Origin Control name substitute requests are
stamping Exec Control not printed
value
Control
Control Time
LB Chronology Origin Control name acknowledge-
acknowledgement stamping
ment
Alarm Time Acknowledge-
LB Chronology Origin Alarm name
acknowledgement stamping ment
Time
LB Alarm clearing Chronology Origin Alarm name Clearing
stamping
Note 1: The labels for the Origin, ObjectName and ObjectMessage properties are defined in configuration, except for
labels in italic bold letters (these labels will be identical in all supported languages).
Note 2: In order to avoid printing valid measurement values, the valid states are tagged as “not printed” in configuration
3.3.5 ADDING A DS AGILE OI PRINTER

When configuring an SOE Network Printer (Lexmark 2591n), no specific action is required in the SCE (as
usual, the printer's name in the configuration should match the printer's name as defined in Windows).
For DS Agile SCE data modeling, the DS Agile OI printer is seen as a pool of up to two physical printers:
 A main printer
 An optional backup printer
A DS Agile OI printer is added from the contextual Objects entry window associated with the OI Server
level by double-clicking on OI printer (or right-clicking on it and then on Add).
Figure 22: Adding a printer to an OI Server
3.3.6 ATTRIBUTES OF A DS AGILE OI PRINTER
3.3.6.1 GENERAL ATTRIBUTES

(1) short name and long name: used for logging and alarm discrimination regarding status datapoints
managed by the DS Agile OI Server for each connected printer
OI/EN AP/C57b AP-27

(2) number (1 / 2): defines the number of printers

(3) printer type (Sequence Of Events / Log Book)
(4) Windows name for main: active printer name
(5) Windows name for backup: backup printer, only significant if a backup printer exists
(6) recovery length (s): see section 3.3.1.1 Printing mechanisms
(7) buffer length (s): see section 3.3.1.1 Printing mechanisms
(8) latency (s): see section 3.3.1.1 Printing mechanisms
Figure 23: General attributes of an OI printer
3.3.6.2 PRINTING FORMAT ATTRIBUTES

To control the way logging is formatted on the printer, set the following printer attributes:
(1) number of lines per page: (range [1,100], step 1)
(2) date formatting: (YY/MM/DD, YYYY/MM/DD, MM/DD/YY, MM/DD/YYYY, DD/MM/YY, DD/MM/YYYY)
(3) header lines format: (see tooltip for available encoding)
(4) ranks of the various columns used for printing format
(5) origin column content: (full area name (on 68 char.) /
short full area name (on 17 char.) / area name N-3 (on 68 char.) /
area name N-2 (on 51 char.) / area name N-1 (on 17 char.))
(6) ranks of the various columns used for printing format
(7) origin Ident. column size: (range [8, 33], step 1)
(8) footer lines format: (see tooltip for available encoding)
AP-28 OI/EN AP/C57b

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
Figure 24: Printing formats attributes of an OI printer
 The value of each … column rank attribute must be unique

3.3.6.3 EVENT PRINTER STATES
The event printer (Log Book or SOE printer) state is translated inside the OI into an MPS value. This MPS is
known as Printer Status.
This feature is available only if the printer is connected to LPT (parallel) or TCP/IP port (network) of the
DS Agile OI Server and it has been tested with a Lexmark 2500 series printer. If you plan to use another
printer, please ensure that the status display works properly.
WARNING: Lexmark 2591+ / 2591N+ printer:
Power Off/On: Since there is no power-off switch, the only way to power off the printer is
to disconnect its power supply. When the power supply is reconnected, the printer is
"OFF" (off-line) and can only be restarted by pressing the Start/Stop button.
Energy-saving mode: In compliance with EU ENERGY STAR specifications, the printer

will automatically switch to energy-saving mode after a preset inactivity time-delay. This
timeout can be disabled but the printer may revert to its default settings if the power
supply is disconnected. Therefore the settings should be checked after each power
supply disconnection in order to make sure that the timeout is still disabled, and, if
necessary, to disable it again.
OI/EN AP/C57b AP-29

3.3.6.3.1 Summary table of SNMP printers' status responses (network printers only)
EPSON LQ-2190N and
OKI 5791 eco +
Lexmark 2591N+ EPSON LQ-2190 + network
Network kit
kit
On Line X X X
Off Line X X X
Unknown / Other / Error X X X
Out of paper X X
3.3.6.3.2 Summary table of the printer states and the corresponding values of the MPS:
Parallel printer:
Lexmark 2591+ and Oki ML5791eco
Printer Status MPS State
Printer Ok STATE0
The printer is in an error state STATE2
The printer is offline STATE4
The printer is out of paper STATE8
The user must fix something STATE10*
Printer is power off or disconnected STATE11
Unexpected value STATE12
Network printer:
Lexmark 2591+ with network kit, and 2591N+
Printer Ok STATE0
The printer is offline or out of paper STATE4
The printer is powered off or disconnected STATE11
Epson LQ-2190** with network kit, LQ-2190N**, and Oki ML5791eco with network kit
Printer Ok STATE0
* When a printer reaches STATE 10, it cannot return to the status OK directly. It must be either set to offline
or powered off. This indicates that the user actually did intervene on the printer.
** Although the EPSON LQ-2190 and LQ-2190N printers are fitted with parallel ports, that connection is not
supported and these printers can only be used via the Ethernet network.
AP-30 OI/EN AP/C57b

3.3.7 REDUNDANT DS AGILE OI PRINTER SETTINGS

To create a redundant DS Agile OI printer:
 Define a DS Agile OI
 Update its general attribute ‘backup printer name’ with the correct name of the physical backup printer
 Add the extra system MPS datapoint BackupPrint stat at DS Agile OI printer level and configure it. (the
description of this datapoint is given in section 3.6 Setting system information for DS Agile OI
components)
Figure 25: Mandatory Backup status datapoint for an OI redundant printer
3.3.8 USE OF NETWORK PRINTERS TOGETHER WITH OI HOT REDUNDANCY

In case of a redundant OI Server architecture, the network printers are shared by both servers, meaning that
only the Master OI prints information.
In Standalone mode, each OI Server uses the printers.
3.4 DS AGILE OI ON THE SBUS

DS Agile OI’s connection to the station bus is implicitly created by hierarchically adding the DS Agile
OI Server and client to the Ethernet network and by setting the IP characteristic of the operator interface.
To assign the OI Server as the recipient of buffer reports, click in the Object entry at Scs level on the relation
has for buffered report client: OI Server.
then double-click on the relation in the hierarchy. For details, refer to C26x/EN AP.
3.4.1 DS AGILE OI SERVER CONNECTION TO OTHER SBUS SUB-SYSTEMS

To transmit information between DS Agile sub-systems, the IEC 61850-8-1 protocol is used.
The data modeling of IEC 61850-8-1 protocol is based on client-server architecture. Each IEC 61850-8-1-
communicating DS Agile sub-system (DS Agile OI Server, DS Agile C26x and DS Agile Gateway) owns an
IEC 61850-8-1 mapping of data which it is server of. A DS Agile sub-system is a server of a datapoint if it
manages it, that is to say it produces its real-time value (in the case of input datapoints such as status,
OI/EN AP/C57b AP-31

measurement, counter) or executes its real-time controls (in the case of output datapoints such as binary
controls and setpoints).
To connect an DS Agile OI (A) to a specific IEC61850-8-1 communicating sub-system (B) on the station-bus,
an extra relation ‘has for UCA2/IEC server’ must be created for (A) and point to (B). This means that
DS Agile OI (A) is a client of sub-system (B) and can access the data managed by sub-system (B), i.e. read
relevant real-time values from (B) and send real-time controls to (B).
Figure 26: Connecting DS Agile OI Server to other station-bus sub-systems
When adding the relation has for UCA/IEC server to DS Agile OI Server (A), the specific attribute of the
relation, modeling/goose usage (1), is not significant: use its default value (data model only).
During a loss of communication between a client and a server, all server datapoints are set to UNKNOWN on
the client.
AP-32 OI/EN AP/C57b

 A Client must not be linked to the same Server through multiple relations has for IEC 61850-8-1
server.
The C264 controller has

the OI Server for
IEC61850 client
The OI Server has the

C264 for IEC61850 server
(1)
S0491ENd
Figure 27: DS Agile OI Server as IEC client of DS Agile C26x
3.4.2 ADDRESS MAPPING DEFINITION OF SBUS

An IEC 61850-8-1 mapping is an aggregation of logical devices, composed of bricks. Generally, a brick
corresponds to an electrical device or function. It provides its real-time data (status, measurements, and
controls …) and some configuration aspects. To do that, a brick groups data by categories (Status,
measurement, Control, Configuration), called functional components.
A functional component groups data objects. A data object must be seen as a real-time equivalent of a
DS Agile datapoint. Thus, when a DS Agile sub-system (IEC 61850-8-1 client) needs the real-time value of a
datapoint managed by another sub-system (IEC 61850-8-1 server), the latter transmits the information via a
data object of its own IEC 61850-8-1 mapping. At DS Agile SCE data modeling level, IEC 61850-8-1 clients
must indicate which IEC 61850-8-1 servers it retrieves information from.
Generally, an IEC 61850-8-1 data object has a stereotype, called common class. Their structures are known
by all DS Agile’s IEC 61850-8-1-communicating sub-systems. For DS Agile sub-systems, the number and
structure of common classes are fixed. They are the terminal description of IEC 61850-8-1 DS Agile data
modeling.
In the IEC 61850-8-1 Mapping of a DS Agile sub-system, there is a native logical device LD0 with fixed and
hard-coded bricks (DBID, DI, GLOBE, and DIAG). When creating a DS Agile OI Server at DS Agile SCE
level, an IEC 61850-8-1 mapping with LD0 and its default bricks are also created. LD0 is a system logical
OI/EN AP/C57b AP-33

device that groups all system diagnostics and controls relevant to the DS Agile OI Server. Datapoints
addressed in the LD0’s brick are only relevant to system topology.
Extra logical devices cannot be created in the IEC 61850-8-1 mapping of a DS Agile OI Server. Their uses
are reserved for DS Agile C26x configuration.
3.4.3 OVERVIEW OF THE LD0 OF DS AGILE OI SERVER IN IEC 61850-8-1 MAPPING

The LD0 of DS Agile OI Server is fixed and composed of the following bricks:
 DBID (DataBase IDentity) used for C26x databases identification and management,
 DI (Device IDentity) used for C26x identification,
 GLOBE used for C26x mode management
 HMIDIAG brick, grouping statuses relevant to DS Agile OI Client links, DS Agile OI printers, archiving
managed by the DS Agile OI Server.
Figure 28: Standard LD0 for DS Agile OI Server
3.4.4 DATAPOINT ON SBUS ADDRESSING

For details, refer to the DS Agile C26x application documents.
AP-34 OI/EN AP/C57b

3.5 DS AGILE OI KLAXON (HORN BUTTON)

A DS Agile OI klaxon, that can either be local to DS Agile OI product or be a substation’s klaxon managed by
DS Agile OI Server, is added from the contextual Objects entry window associated with the OI Server level
by double-clicking on Klaxon (or right-clicking on it and then on Add).
Figure 29: Adding a klaxon to an OI Server
Once added, the following klaxon attributes must be updated:

(1) short name and long name: used for internal identification by DS Agile SCE
(2) audibility mode (Immediate / Differed)
(3) audibility delay (s) (range [1 s, 600 s], step 1 s): this attribute is significant if the previous attribute is
set to Differed. It defines the delay before the audible signal is issued
(4) audibility ack. mode (Manual / automatic): if this attribute is set to Manual the klaxon is stopped by
an operator action. If this attribute is set to Automatic the klaxon is stopped either by an operator
action or after a time period defined by the next attribute
(5) audibility ack. delay (s) (range [1 s, 60 s],step 1 s): this attribute is significant only if the previous
attribute is set to ‘Automatic’.
(1)
(2)
(3)
(4)
(5)
Figure 30: General attributes of an OI klaxon
When the klaxon is external to DS Agile OI, that is if it is set to run on/off with a specific SPC datapoint, an
extra relation is controlled by (1) must be added and defined at DS Agile OI klaxon level.
OI/EN AP/C57b AP-35

Figure 31: Controlling an external klaxon
For any klaxon creation, the corresponding electrical and system areas, voltage levels and IEC 61850-8-1
physical devices must be given by adding and filling in the relations warns audibly (2) at the klaxon level. By
default, upon the klaxon’s creation, one relation warns audibly is implicitly created at the voltage level.
A "Klaxon" refers to a set of datapoints. This set contains all the datapoints, which are in the sub-tree of each
Voltage level and UCA2/IEC physical device linked to the klaxon through the relation warns audibly.
In the set of datapoints, at least one datapoint must fulfill the following conditions:
 it must be linked to a datapoint profile which has its attribute Alarms / audible set to Yes.
 the DS Agile OI Server must be its Server or its Client
 it must not be the Main status MV system datapoint of a C26x.
The sets of datapoints of each Klaxon of a DS Agile OI Server must not share the same datapoints.
3.6 SETTING SYSTEM INFORMATION FOR DS AGILE OI COMPONENTS

When creating a DS Agile OI Server (resp. client), specific datapoints are automatically added in the ‘System
infos’ folder (1) (resp. (2)) at DS Agile OI level.
So it is when adding a DS Agile OI printer (3) attached to a DS Agile OI Server. In that case, the System
infos folder is located under the relevant printer.
For extra DS Agile OI Server functionality (printer redundancy), some optional datapoints can be required.
DS Agile SCE calls such System infos datapoints, system datapoints.
System datapoints provide real-time statuses and controls on system software or hardware components.
As datapoint, system datapoints must be linked to a profile. Depending on its type, the system datapoint and
its relevant profile have specific attributes to be set correctly to ensure a healthy behavior by the operator
interface. The datapoint and profile requirements for each type of system datapoint are listed below.
Generally system datapoints are automatically addressed in IEC 61850-8-1 mapping of the relevant DS Agile
OI at their creation. If manual addressing is necessary, it is stressed in following chapters by given the
associated available data object of a given DS Agile OI brick in LD0 (<brick name>.<data object name>).
AP-36 OI/EN AP/C57b

Figure 32: System infos folders and datapoints
When creating a DS Agile OI or one if its components (server, client, and printer), the following mandatory
datapoints are implicitly added and must be configured according to their described features:
(4) Auto archiving SPS: in case of successful automatic archiving, this datapoint is in SET state. If not, it is
in RESET state.
IEC 61850-8-1 addressing Available states
 HMIDIAG.ArchSt RESET:Failed
Automatic at datapoint creation SET: Successful
(5) Central archive MPS: this datapoint details the HMI Central Archive status.
STATE0: Normal
 HMIDIAG.HistSt STATE1: 90% full
Automatic at datapoint creation STATE2: Full
STATE3: Faulty
(6) Device link SPS: although this datapoint is under the DS Agile OI Server, it is not managed by it. Each
IEC 61850-8-1 client of an IEC 61850-8-1 server computes locally this datapoint status by supervising
the IEC 61850-8-1 real-time link with the IEC 61850-8-1 server. In particular, there are as many
Device link SPS per DS Agile OI Server as there are IEC 61850-8-1 servers connected to the DS Agile
OI Server. This datapoint is set in SET state if the device link with the IEC 61850-8-1 server is
operational.
Can not be addressed on IEC 61850-8-1. RESET:not OK
Managed locally by each IEC 61850-8-1 client SET: OK
OI/EN AP/C57b AP-37

(7) Log queue SPS: this datapoint is unused at DS Agile OI Server level, but must be configured for
IEC 61850-8-1 compliance.
 HMIDIAG.LogSt RESET:overflow
Automatic at datapoint creation SET: normal
(8) Operating mode MPS: this datapoint gives the current operating mode of the DS Agile OI Server.
STATE 0: Faulty
STATE 1: Operational/Run
 LLN0.ST.Mod STATE 2: Blocked
Automatic at datapoint creation STATE 3: Test
STATE 4: Test/Blocked
STATE 5: Maintenance
(9) Redundancy mode SPS: It is in ‘RESET state if DS Agile OI Server is in StandBy mode for
redundancy, else (including when there is no redundancy) it is in ‘SET’ state, corresponding to Active
mode.
 HMIDIAG.RedSt RESET:Standby
Automatic at datapoint creation SET: Active
The initial state is RESET.
(10) Synchronisation SPS: this datapoint is set in the SET state if DS Agile OI Server is synchronized.
 HMIDIAG.SyncSt RESET:not synchronized
Automatic at datapoint creation SET: synchronized
(11) Red. Status MPS: this additional datapoint gives the state of the DS Agile OI Server regarding the
switchover. Refer to chapter OI/EN FT – Hot redundancy.
STATE0: Starting
STATE1: Waiting
STATE2: Going to stand.
Can not be addressed on IEC 61850-8-1.
STATE3: Standalone
Managed by DS Agile OI Server
STATE4: Slave
STATE5: Master
STATE6: Shutdown
(12) Printer status MPS: this datapoint gives the state of the printer. This datapoint can be addressed on
IEC 61850-8-1:
 using ‘SBUS automatic addressing function’,
AP-38 OI/EN AP/C57b

 manually. In this case, the relevant data object given the status IEC 61850-8-1 address, must be
‘SOESt0’ (if the printer if an SOE printer) or ‘<SLBSt0’ (if the printer is an LB printer) in the
DS Agile OIHMIDIAG brick, where is an arbitrary printer number (1 or 2).
IEC 61850-8-1 addressing
 HMIDIAG.SOESt0
Manually addressed in IEC 61850-8-1 DIAG brick of the operator interface.
Or
SBUS Automatic addressing.
Parallel printer:
Printer OK STATE0
Printing is suspended STATE1
Unexpected value STATE12
Network printer:
Printer OK STATE0
Printing is suspended STATE1
The printer is offline or out of paper STATE4
The printer requires user intervention STATE10
(13) Backup print status MPS: this additional datapoint gives the state of the backup printer (if present).
This datapoint can be addressed on IEC 61850-8-1:
 using ‘SBUS automatic addressing function’,
 manually. In that case, the relevant data object given the status IEC 61850-8-1 address, must be
‘SOESt1’ (if the printer if an SOE printer) or ‘<SLBSt1’ (if the printer is an LB printer) in the
DS Agile OIHMIDIAG brick, where is an arbitrary printer number (1 or 2).
IEC 61850-8-1 addressing
 HMIDIAG.SOESt1
Manually addressed in IEC 61850-8-1 DIAG brick of the operator interface.
Or
SBUS Automatic addressing.
The MPS states are the same as above.

(14) OI Client link SPS: although this datapoint is under the DS Agile OI Client, it is not managed by it.
For each DS Agile OI Client, served by a DS Agile OI Server, the DS Agile OI Server computes this
datapoint, giving the communication status with the DS Agile OI Client. It is in SET state if device link
with IEC 61850-8-1 server is operational.
OI/EN AP/C57b AP-39


 HMIDIAG.HMISt RESET:Out of Service
Automatic at datapoint creation SET: In Service
AP-40 OI/EN AP/C57b

4 DATAPOINTS FOR DS AGILE OI

Electrical and system topologies share entities called Datapoints. A datapoint corresponds to an atomic
object with real-time value, status or control relevant to an electrical or system process. Moreover, a
datapoint supports extra system functions such as forcing, suppression, filtering, alarms and logging.
There are several types of datapoints:
 Input datapoint types used for supervision:

 SPS (Single Point Status), DPS (Double Point Status), MPS (Multiple Point Status)
 MV (Measurement Value or Operating MV), Counter
 Output datapoint types used for control:

 SPC (Single Point Control), DPC (Double Point Control)
 Setpoint
Input datapoints can be acquired through sensors (input channels) addressed on IEDs at IED legacy network
level or substation network level. They can also be calculated or derived by the system’s devices. They can
be sent to the SCADA by addressing them on the SCADA network.
Output datapoints can be controlled through relays (output channels) addressed on IEDs at IED legacy
network level or substation network level or on SCADA networks. They can also be managed by built-in or
user functions.
For details about:
 Configuration of datapoint acquisition via input channels and IED, refer to chapter C26x/EN AP
 Configuration of datapoint controlling via output channels and IED, refer to chapter C26x/EN AP
 Configuration of datapoint transmission to SCADA, refer to chapter C26x/EN AP and chapter GTW/EN
AP
 Configuration of datapoint transmission on SBUS, refer to chapter C26x/EN AP

At DS Agile SCE level, datapoints belonging to the system topology are called system datapoints, and those
of the electrical topology are called electrical datapoints.
Generally, system datapoint creation is automatic when adding system devices or sub-components to
system devices. They are never wired, except for system datapoints used for redundancy and usually
correspond to system diagnostics (device, printer board status, control of device mode, …).
Electrical datapoint creation is rarely automatic except when they are required for correct DS Agile system
behavior (for instance, ‘Order running SPS’ at bay level, ‘Computed switchgear position’ at circuit-breaker
level), or relevant to an electrical built-in function that imposes their existence.
Datapoint creation and configuration is mainly described in chapter C26x/EN AP.
The following sections list the datapoint attributes relevant to DS Agile OI configuration for logging, alarm,
archiving and display needs.
OI/EN AP/C57b AP-41

4.1 SHORT AND LONG NAME DATAPOINT UPDATES

The short name and long name attributes (1) of a datapoint that are relevant to logging, alarm or display
needs at DS Agile OI level must be updated:
Figure 33: Setting the short name and long name of a datapoint (example given at bay level for a generic SPS)
4.2 DATAPOINT PROFILES
4.2.1 OVERVIEW
A set of datapoints often share many common characteristics. For instance, all feeder breaker positions have
the same state labels, alarm and logging behaviour. To group these common characteristics, profiles are
included in the data modelling. For each type of datapoints (SPS, DPS,…) there exists a relevant profile
(SPS profile, DPS profile, …). Several datapoints of the same type can be linked to the same profile.
Be careful:
The profile attributes can be seen as the datapoint attributes as soon as this datapoint is linked to the
profile.
For input datapoints, the following characteristics are set in the profile:
 state labels and eventual unit label for MV and counter

 definition of the archived and logged states
 definition of the alarmed states (gravity, time delay, audibility)
 definition of state interlocking values
 definition of forcing/substitution/suppression (FSS) and SBMC features
 links to printers defined in the system topology for alarm and event logging purposes
For output datapoints, the following characteristics are set in the profile:
 order labels and eventual unit label for setpoints

 definition of the significant orders for SPC and DPC
 definition of the alarmed command failure (gravity, time delay, audibility)
 definition of the archived and logged transitions
AP-42 OI/EN AP/C57b

 SBO mode facility

 links to the printers defined in the system topology for alarm and event logging purposes
4.2.2 PROFILE OI-SPECIFIC ATTRIBUTES

To use the Profiles table, refer to the chapter C26x/EN AP.
In the State treatment tab, each OI printer is identified by a digit (1..2 for SOE printer, 1..2 for LB printer).
For MVs and Setpoints, only the LB printers are available.
Figure 34: Defining the event logging printer for an SPS profile
The use of each printer can be specified:

 SCE: Used / Unused
 LB: Unused / Events / Events and Alarms
Figure 35: Relations for an SPS profile
For OI treatment there are three options:
 no archive and no logging

 archive and logging (only this option allows changes to appear in the event viewer)
 archive and no logging
Figure 36: State treatment attributes of an SPS profile for “OI treatment on”
OI/EN AP/C57b AP-43

 If an OI printer is used in a Datapoint profile, then the at least one state must have its "OI treatment
on" attribute set to the "archive, logging" value.
 If the OI is configured to receive buffered reports (refer to C26x/EN AP), all the datapoints with the
quality Unknown must be neither archived, nor logged
For xPC control mode: for details about relevant control popup, see 9.3 Launch action: Open control popup)
4.3 LOCAL ARCHIVING OF DATAPOINTS BY DS AGILE OI
4.3.1 LOCAL ARCHIVING DEFINITION OF EVENT DATAPOINTS BY DS AGILE OI

DS Agile OI manages the archiving of all the datapoints that it is client or server for. For the operator
interface, event archiving is activated or not on a datapoint state basis, via its associated profile (refer to
previous section).
4.3.2 LOCAL ARCHIVING DEFINITION OF ALARM DATAPOINTS BY DS AGILE OI

DS Agile OI manages the archiving of the datapoints that it is client or server for. Alarm archiving at DS Agile
OI level is defined globally for all the operator interfaces at Scs object level.
4.3.3 LOCAL LOGGING DEFINITION OF EVENT AND ALARM DATAPOINTS BY

DS AGILE OI
DS Agile OI manages the logging of the datapoints that it is client or server for. At DS Agile OI level, any
logged datapoint is also archived.
For DS Agile OI, event logging is available or not on a datapoint state basis, via its associated profile.
4.3.4 GLOBAL ALARM ACKNOWLEDGEMENT
4.3.4.1 INTRODUCTION
A dedicated SPS can be used to acknowledge all the alarms present.
When the Global Ack SPS is set, all the alarms present are acknowledged. As long as the SPS remains in
this state, a periodic task acknowledges every newly created alarm.
As soon as the SPS is reset, the periodic task is stopped and the alarms can occur without being
automatically acknowledged.
AP-44 OI/EN AP/C57b

4.3.4.2 CONFIGURATION OF THE GLOBAL ACKNOWLEDGE SPS
Figure 37: SCE: Global alarm ack configuration
In SCE, the Global Acknowledge SPS is set in the configuration:
 in the object view window, electric view, select the substation object,
 in the objects entry window, open the sub tree Substation SPS Electrical datapoint,
 right click on Global alarm ack,
 select add
and follow the same configuration process as for an ordinary SPS
OI/EN AP/C57b AP-45

4.3.5 SET THE PERIOD VALUE

If you do not configure it, the automatic acknowledgement task at OI level has a default value of 15 [s].
If you want another period value, you must add it in the registry of the computer on which the OI Server is
installed.
Procedure:
 Click on Start/Execute
 Invoke the Regedit command
 Select the HKEY_LOCAL_MACHINE/SOFTWARE/ALSTOM/DCS key and add a new DWORD
value.
 Name it GlobAckPeriod. Make sure you respect the upper/lower case format as shown in the figure
below.
 Set the data value to the desired duration period in [ms]. Be careful to select the Decimal radio button.
The figure below shows a configuration for 2[s].
 You cannot set the value to less than 200[ms]. If you do, the period will have the default value of 15[s]
Figure 38: Registry: Duration period set to 2[s]
AP-46 OI/EN AP/C57b

5 COLORS, FONTS AND STROKES FOR DS AGILE OI

To define the mimics of a DS Agile OI Client, up to 256 colors, 64 fonts and 64 strokes can be used. Their
creation is implicit when creating a new DS Agile configuration at DS Agile SCE level and their definitions are
centralized in tables at graphic root level.
At mimic definition level, objects only reference these colors, fonts and strokes. It is an easy way to
propagate for instance a color change to all the objects that reference it.
Figure 39: Color, font and stroke tables
OI/EN AP/C57b AP-47

5.1 COLOR SETTINGS

The first 19 colors (color 0 to color 18) are pre-defined and cannot be changed. The easiest way to edit a
color table at DS Agile SCE level is to use the Table Color Editor (for details about it, refer to DS Agile SCE
documentation)
(1) (2) (3) (4)
Figure 40: Table color editor
For any editable color, the following attributes can be updated:

(1) long name, corresponding to a brief description of the color usage
(2) color: by clicking on icon (4), a specific popup appears to select the desired color with a WYSIWYG
behavior
AP-48 OI/EN AP/C57b

Figure 41: WYSIWYG color edition
(3) blinking period (0: no blinking, 400 ms, 1000 ms, 2000 ms, 3000 ms or 5000 ms)
OI/EN AP/C57b AP-49

5.2 FONT SETTINGS

The first four fonts (Font 0 to Font 3) are pre-defined and can not be changed. The easiest way to edit a font
table at DS Agile SCE level is to use the Table Font Editor (for details about it, refer to DS Agile SCE
documentation)
Figure 42: Table font editor
For any editable font, the following attributes can be updated:
 long name, corresponding to a brief description of the font use

 family, corresponding to an available police name
 size (5 to 90 pixels)
 style (Normal/Italic)
 weight (Normal/Bold)
AP-50 OI/EN AP/C57b

5.3 STROKE SETTINGS

The first five strokes (stroke 0 to stroke 4) are pre-defined and can not be changed. The easiest way to edit a
stroke table at DS Agile SCE level is to use the Table Stroke Editor (for details about it, refer to DS Agile
SCE documentation)
(1)
(2)
(3)
Figure 43: The table stroke editor
For any editable stroke, the following attributes can be updated:

(1) long name, corresponding to a brief description of the stroke usage
(2) width (1 to 50 pixels)
(3) dash (solid/dashed/dotted/dash-dot/ dash-dot-dot)
OI/EN AP/C57b AP-51

5.4 COLOR SETTINGS FOR ALARM MANAGEMENT

Definition of colors for alarm management is done at the graphical root (Graphic object).
(1)
(2)
(3)
(4)
(5)
(6)
Figure 44: General attributes of a graphic
(1) short name and long name

(2) Maximal delay for time consolidation (range [1 s, 60 s], step 1 s)
(3) memo icon size (10x10 / 15x15 / 20x20 / 25x25 / 30x30 / 35X35)
(4) mode (manual / automatic): this attributes defines the logoff mode
(5) inactivity time (range [-231 mn, 231 mn],step 1 mn): this attribute defines the time before the automatic
logoff.
(6) warning time (range [-231 s, 231 s],step 1 s) this attribute defines the time between the display of the
warning message and the automatic logoff.
For each available gravity (1 to 5) and for each available alarm state the following colors can be updated:
(7) Fill color (color of alarm text background)
(8) Text color (color of alarm text character)
AP-52 OI/EN AP/C57b

(7)
(8)
Figure 45: Gravity color attributes of a graphic
OI/EN AP/C57b AP-53

6 DS AGILE OI WORKSPACE
Each DS Agile OI Client of the system topology references a workspace that corresponds to a client builder
project.
A workspace, as a screen layout, is split in windows that are the support to predefined mimics or
configurable mimics.
The only settable characteristic of a workspace is its "display resolution", i.e. its total window size, in pixels.
Each window in the workspace has extra specific characteristics (position and size in the workspace,
presence of title bar, system menu, minimize and maximize buttons, …).
Below is an example of DS Agile OI standard workspace for DS Agile, composed of 5 windows:
 windows (1), (2) and (4) contain predefined mimic banners embedded in the DS Agile product
 windows (3) and (5) contain configurable mimics defined in DS Agile SCE
Figure 46: DS Agile OI Standard workspace
The standard title (1), command (2) and alarm (4) banners are predefined, with some degree of freedom. A
window can only contain a specific standard banner or exclusively a set of several configurable mimics
(‘Mimic’ object).
When a window is to contain several configurable mimics, one of these diagrams must be set as the default
page so that the client builder automatically opens it when the window is generated.
AP-54 OI/EN AP/C57b

Note: The point of origin (0,0) used to locate a window or a mimic is its top left corner.
6.1 DS AGILE OI WORKSPACE DEFINITION

A DS Agile OI workspace is implicitly created when creating a new DS Agile configuration in DS Agile SCE.
If an extra DS Agile OI workspace is required, it can be added using DS Agile SCE via the Objects entry
area at graphic level by double–clicking on OI workspace (or right-clicking on it and then on Add).
Figure 47: Adding an OI workspace
Once added, the following DS Agile OI workspace attributes must be updated:
 short name and long name: used for internal identification by DS Agile SCE
 display resolution (see screenshot below): non-standard resolutions (other than 1024x768 and
1280x1024) are obtained using specific multi-display managing boards (outputs for 2 or 4 displays);
800 x 600 is for Bay Local OI (except for Terna)
Figure 48: General attributes of an OI workspace
OI/EN AP/C57b AP-55

6.2 DS AGILE OI WINDOW

A DS Agile OI window is implicitly created when creating a DS Agile OI workspace.
An extra DS Agile OI window is added from the contextual Objects entry window associated with the OI
workspace level by double–clicking on Window (or right-clicking on it and then on Add).
Figure 49: Adding an OI window
Once added, the following DS Agile OI window attributes must be updated:

(2) x and y: absolute position of the window in the workspace
(3) width and height (in pixels): size of the window
(4) title bar (No/Yes)
(5) system menu (No/Yes)
(6) iconizable (No/Yes)
(7) maximizable (No/Yes)
(8) sizeable (No/Yes)
(9) moveable (No/Yes)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
Figure 50: General attributes of an OI window
AP-56 OI/EN AP/C57b

6.3 STANDARD TITLE BANNER

A standard title banner (pre-defined mimic) is added from the contextual Objects entry window associated
with the Window level by double–clicking on Std Title Banner (or right-clicking on it and then on Add).
Figure 51: Adding a standard title banner
Once added, the following attributes of the standard title banner must be updated:
 short name and long name: used for internal identification by DS Agile SCE
 date format appearing in the banner (MM/DD/YY, DD/MM/YY, YY/MM/DD)
Figure 52: General attributes of a standard title banner
6.4 STANDARD COMMAND BANNER

A standard command banner (pre-defined mimic) is added from the contextual Objects entry window at
Window level by double-clicking on Std Comm. Banner (or right-clicking on it and then on Add).
Figure 53: Adding a standard command banner
OI/EN AP/C57b AP-57

Once added, the following attributes of the standard command banner must be updated:
 short name: used for internal identification by DS Agile SCE

 memo option (No/Yes): must be set to Yes to display a Memo icon
 klaxon option (No/Yes): must be set to Yes to display a Horn icon
 web site option (No/Yes): must be set to Yes to display a Web site icon
 help option (No/Yes): must be set to Yes to display a Help icon
 about option (No/Yes): must be set to Yes to display an About icon
 profile option (No/Yes): must be set to Yes to display a Profile icon
 password option (No/Yes): must be set to Yes to set a Password icon
 tool option (No/Yes): must be set to Yes to display a Tool icon
 SMT option (No/Yes): must be set to Yes to display an SMT icon
 hard-copy option (No/Yes): must be set to Yes to display a Hard copy icon
 archives option (No/Yes): must be set to Yes to display an Archive con
Figure 54: General attributes of a standard command banner
AP-58 OI/EN AP/C57b

6.5 STANDARD ALARM BANNER

The standard alarm banner is a particular alarm list that is further described in section Alarm viewer and
alarm banner.
A standard alarm banner (pre-defined mimic with configurable alarm ActiveX) is added from the contextual
Objects entry window associated with the Window level by double clicking Std Alarm Banner (or right-
clicking it and then clicking Add).
Figure 55: Adding a standard alarm banner
Once added, the following attributes of the standard command banner must be updated:
(1) short name: used for internal identification by DS Agile SCE
(2) maximum line number (1 to 10) displayed in the list managed by the alarm ActiveX
(3) font (0 to 63):used in the list managed by the alarm ActiveX
(4) date format used in the list managed by the alarm ActiveX (YY/MM/DD, YYYY/MM/DD, MM/DD/YY,
MM/DD/YYYY, DD/MM/YY, DD/MM/YYYY)
(5) background color (0 to 255) of the list managed by the alarm ActiveX
(6) tooltips (No/Yes)
(7) column resizable (No/Yes)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
Figure 56: General attributes of a standard alarm banner
For each available column of the alarm list (Timestamp, origin, object name, object message, alarm state,
alarm gravity):
(8) time stamp column rank (0 to 9): its column rank (0 to 6) where 0 means unused
(9) Origin column rank (0 to 9)
OI/EN AP/C57b AP-59

(10) object name column rank (0 to 9):

(11) object message column rank (0 to 9):
(12) alarm gravity column rank (0 to 9):
(13) origin column content (full area name (on 68 char.) / short area name (on 17 char.) / area name N-
3 (on 68 char.) / area name N-2 (on 51 char.) /
area name N-1 (0n 34 char.)):
(8)
(9)
(10)
(11)
(12)
(13)
Figure 57: Column attributes of a standard alarm banner
6.6 DEFAULT MIMIC OF WINDOW DEFINITION

For windows containing user-defined mimics, i.e. not a standard banner, the default mimic (s) that is (are)
displayed in, must be set.
This is done by adding and filling in the relation has for default mimic at the Window level.
Figure 58: Adding default mimics to a window
AP-60 OI/EN AP/C57b

7 DS AGILE OI MIMIC
A configurable mimic is composed of graphical symbols.
A symbol can be:
 An elementary shape
 A multistate
 A text symbol used in multistate
 A Memo icon
 A group
7.1 MIMIC
A user-defined mimic is added from the contextual Objects entry window associated with the Window level
by double-clicking on Mimic (or right-clicking on it and then on Add).
Figure 59: Adding a user-defined mimic to a window
Once added, the following attributes of the mimic must be updated:

(2) x and y (in pixels): relative position of the mimic in its parent window (x and y values)
(3) width and height (in pixels): size of the mimic. If the mimic’s size is greater than its owner window
size, vertical and horizontal sliders appear automatically. If it is smaller, the unused area of the window
is colored yellow.
(4) background color
(5) title bar (No/Yes)
(6) system menu (No/Yes)
(7) iconizable (No/Yes)
(8) maximizable (No/Yes)
(9) sizeable (No/Yes)
(10) moveable (No/Yes)
(11) border (No/Yes)
OI/EN AP/C57b AP-61

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
Figure 60: General attributes of a user-defined mimic
7.2 STATIC PART WITH BASIC SHAPES

The static part of a mimic is described using basic graphical shapes:
 Rectangle (6)
 Circle (1)
 Line (3) and polyline (5)
Static text can be inserted into mimics using:
 Text (7), directly entered in the graphical editor

 Var. text (8), text support referring to
 ‘short name’, ‘Long name’ attribute value of an object of the electrical or system topology, or,
 real time value of an MV or Counter datapoint, or,
 state text associated with real-time status of SPS, DPS or MPS datapoint
Particular images can also be added via:
 Image (2), referring a gif or jpeg file

To make them easier to handle, all these objects can be grouped into an upper-level component, called a
‘group’ (9) object (see section 7.5 Graphical object).
The best practice to create the static part of a mimic is to use DS Agile SCE Mimic Editor and to adjust some
properties with the attribute editor. Any graphical shape can be directly created by clicking on the
corresponding icon in the DS Agile OI Mimic toolbar of the DS Agile SCE editor. For more details on the
Mimic Editor, see the DS Agile SCE user manual.
AP-62 OI/EN AP/C57b

Figure 61: Defining the static part of a mimic
7.2.1 DEFINING A RECTANGLE PROPERTY UPDATES

Once a rectangle has been added using the DS Agile SCE mimic editor, its following attributes can be
updated with DS Agile SCE attribute editor:
(2) x (in pixels): horizontal position of the upper-left corner of the rectangle in its parent window
(3) y (in pixels): vertical position of the upper-left corner of the rectangle in its parent window
(4) width (in pixels)
(5) height (in pixels)
(6) arc width (in pixels) of the corners of the rectangle
(7) arc height (in pixels) of the corners of the rectangle
(8) fill color (0 to 255): color used to fill the rectangle
(9) stroke color (0 to 255): color of the border of the rectangle
(10) stroke type (0 to 63): style of the border of the rectangle
OI/EN AP/C57b AP-63

(2 (3
(7
(5
(6
(4
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
Figure 62: General attributes of a rectangle
7.2.2 DEFINING A CIRCLE

A circle object can be defined as a circle or an ellipse, it can be filled or empty and it can be set as a partial
ellipse depending on its attributes.
Once a circle has been added using the DS Agile SCE mimic editor, its attributes can be updated using the
DS Agile SCE attribute editor:
(2) x (in pixels): horizontal position of the shape in its parent window
(3) y (in pixels): vertical position of the shape in its parent window
(6) angle start (in °): to obtain a partial ellipse (in order to obtain a complete circle or an ellipse this
attribute must be set to 0° and the next one set to 360°)
(7) angle extent (in °): to obtain a partial ellipse
AP-64 OI/EN AP/C57b

(8) fill color (0 to 255): color used to fill the shape

(9) stroke color (0 to 255): color of the border of the shape
(10) stroke type (0 to 63): style of the border of the shape
(3 (7
(6
(5
(2 (4
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
Figure 63: General attributes of a circle
7.2.3 DEFINING A LINE

Once a line has been added using the DS Agile SCE mimic editor, its attributes can be updated using
(2) x1 (in pixels): horizontal position of the first point of the line in its parent window
(3) y1 (in pixels): vertical position of the first point of the line in its parent window
(4) x2 (in pixels): horizontal position of the second point of the line in its parent window
(5) y1 (in pixels): vertical position of the second point of the line in its parent window
(6) stroke color (0 to 255): color of the line
(7) stroke type (0 to 63): style of the line
OI/EN AP/C57b AP-65

(3
(5
(2
(4
(1)
(2)
(3)
(4)
(5)
(6)
(7)
Figure 64: General attributes of a line
7.2.4 DEFINING A POLYLINE

A polyline object can be defined as an open polyline or as a polygon depending on its attributes.
By default a polyline is created with only two points: StartPoint (1) and Point (2) which have the following
attributes:
(4) x (in pixels): horizontal position of the point in its parent window
(5) y (in pixels): vertical position of the point in its parent window
AP-66 OI/EN AP/C57b

Figure 65: Default points of a polyline
These two default points only define a line: In order to define a polyline, it is necessary to add at least one
point. This is done from the contextual Objects entry window associated with the polyline by double–clicking
on Point (or right-clicking on Point and then on Add).
In the example given in the figure below, two points (1) have been added to the two default points.
Figure 66: Adding points to the default polyline
When all the attributes (short name, x and y) of each point have been updated (thus defining the shape of
the polyline), some general attributes of the polyline can be updated:
(2) closed (No/Yes): if set to ‘Yes’, the polyline becomes a polygon filled with ‘fill color’
(3) fill color (0 to 255): color used to fill the polygon (if the previous attribute is set to 'Yes')
(4) stroke color (0 to 255): color of the line
OI/EN AP/C57b AP-67

(5) stroke type (0 to 63): style of the line
Figure 67: General attributes of a polyline
To update the position of a point on a polyline, either modify its coordinates using the attributes editor or just
move it with the mouse in the Mimic editor.
7.2.5 DEFINING A TEXT

Once a text has been added using the DS Agile SCE mimic editor, its attributes can be updated using the
(2) x (in pixels): horizontal position of the text box in its parent window
(3) y (in pixels): vertical position of the text box in its parent window
(4) box width (in pixels)
(5) box height (in pixels)
(6) box color (0 to 255): color used to fill the text box
(7) Text value
(8) type (Standard / current time / current date / logged user / login state)
(9) justify (left / right / center)
(10) orientation (horizontal / vertical)
(11) margin width (in pixels): only significant if previous attribute is set to left or to right
(12) text color (0 to 255)
(13) font (0 to 63)
AP-68 OI/EN AP/C57b

(3)
(2)
(5)
(11)
(4)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
S1000ENa
Figure 68: General attributes of a text box
7.2.6 DEFINING A VARIABLE TEXT

Once a variable text has been added using the DS Agile SCE mimic editor, its attributes can be updated
using the DS Agile SCE attribute editor:
(2) x (in pixels): horizontal position of the text box in its parent window
(3) y (in pixels): vertical position of the text box in its parent window
(4) box width (in pixels)
OI/EN AP/C57b AP-69

(5) box height (in pixels)

(6) box color (0 to 255): color used to fill the text box
(7) justify (left / right / center)
(8) margin width (in pixels): only significant if previous attribute is set to left or to right
(9) use default format (No/Yes): useful for MV and counter real-time value representation. If it is set to
‘Yes’, the default format defined at datapoint profile level is used. If it is set to ‘No’, the next attribute
gives the representation format to be used.
(10) particular format: this attribute is a string composed of the following characters:
# display only significant figures
0 display non-significant zeros
~ suppress sign
% display in percentage mode
‘’ ‘’ display strings with reserved characters
\ display reserved characters
U display unit
. display decimal delimiter
(11) text color (0 to 255)
(12) font (0 to 63)
AP-70 OI/EN AP/C57b

(3)
(2)
(5)
(11)
(4)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
S1001ENa
Figure 69: General attributes of a variable text
To link a var. text graphical object to the short name or long name attribute value of an object in the
electrical or system topology:
(1) Add the corresponding relation refers to at var. text level
(2) Fill it with the associated electrical or system object
(3) Adjust the attribute property of the relation refers to
OI/EN AP/C57b AP-71

Figure 70: Linking var. text to an object property (e.g. for an MV datapoint)
The available objects and relevant displayable properties that can be assigned to a var. text attribute are
listed below:
AP-72 OI/EN AP/C57b

Object Displayable property

Bay
Board
Built-in function
DPC datapoint
IED (relay)
Legacy network
Module
Non UCA2/IEC physical device Short name
Printer Long name
SCADA network Father short name
Scs Father long name
Site
Slow automation
SPC datapoint
Substation
Substation network
UCA2/IEC physical device
Voltage level
Short name
SPS datapoint Long name
DPS datapoint Resulting state label
MPS datapoint Father short name
Father long name
Short name
Long name
Counter datapoint Resulting state label
MV datapoint Value
Father short name
Father long name
 No Var. text is allowed in the sub-tree of a Multi-State.

 For each Var.Text: 1, and only 1, relation refers to must be linked.
7.2.7 DEFINING AN IMAGE

Once an image has been added using the DS Agile SCE mimic editor, its attributes can be updated:
(2) x (in pixels): horizontal position of the upper-left corner of the image in its parent window
(3) y (in pixels): vertical position of the upper-left corner of the image in its parent window
(6) file name of the image (gif or jpeg extension)
OI/EN AP/C57b AP-73

(3
(2
(5
(4
(1)
(2)
(3)
(4)
(5)
(6)
Figure 71: General attributes of an image
7.2.8 AUTOCLOSE OF MIMICS

A mimic containing a Trend Archive can be closed automatically when the operator switches to another
mimic.
A mimic containing an AlarmViewer can be closed automatically when the operator switches to another
mimic.
The AutoClose indication is set in the mimic by the XML Parser tool when the configuration is generated,
depending on the value of the following entries in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\ ALSTOM\DCS\XmlParser
Value name Value type Comment
AutoCloseTrendA REG_SZ True: AutoClose is activated
False: No AutoClose
If the entry is missing: the default value is True
True: AutoClose is activated
AutoCloseAlarm REG_SZ False: No AutoClose
If the entry is missing: the default value is False
AP-74 OI/EN AP/C57b

The two AutoClose indications are ignored if the mimic contains a RealTime Trend.
7.3 MEMO REPRESENTATION
7.3.1 MEMO BITMAPS CONFIGURATION

In order to select the bitmaps to be used to animate the various states of a memo, define a new bitmap
under the Bitmap Tables, choosing as type: Memo for client. For each of the 4 states (unavailable, no note,
active, inactive) draw a new icon using the SCE editor or select an existing file. It is then necessary to set a
“reference index” for the new bitmap (group of 4 icons) and to set the same index for the “Bitmap reference”
of the memo that uses this bitmap.
Warning:
Do not use transparent areas when drawing memo icons using the SCE. Otherwise, these
areas will be displayed in black because the bitmap format itself does not support
transparency.
Therefore, it is advised to fill the memo icons background with the same color as used
for mimic background.
7.3.2 MEMO REPRESENTATION

The memo function allows the operator to place short memos on the display of a bay, a module (e.g.
switchgear, transformer, etc.) or other devices such as OI, computers, protection relays, gateway, etc. where
this is useful and configured, assuming the operator has been granted the appropriate access rights.
The memos contain the following information:
 free text
 name of the bay / module / device where the memo is or was connected
OI/EN AP/C57b AP-75

 user name of operator who creates the memo

 date and time of creation
 user name of operator who deletes the memo
 date and time of deletion
A global memo status, in the general tool banner, gives a general indication on all current memos:
Icon animation Meaning
There is not yet a "Memo"
No "Memo" is still active, but one has been deleted
At least a "Memo" is now active and can be read
The memo is undefined (downgraded case)
These animations are also available for each memo.

A memo placed on one DS Agile OI Client is visible on all other DS Agile OI Clients. Only one memo could
be attached to a module or a piece of equipment, and on a per mimic basis (i.e. a memo attached to a
module in a mimic will not be visible in another mimic in which the same module appears).
‘Memo’ objects are created at the graphic root level. DS Agile OI Server manages and stores their real-time
contents that can be entered by a DS Agile OI user. A ‘memo’ object can have several graphical
representations via ‘memo icons’ in mimics.
7.3.3 ADDING A MEMO

A DS Agile OI memo is added from the contextual Objects entry window associated with the Graphic level
by double–clicking on Memo (or right-clicking on it and then on Add).
Figure 72: Adding an OI memo
Once added, the following memo attributes can be updated:

(1)
Figure 73: General attributes of a memo
AP-76 OI/EN AP/C57b

Once created, the memo object must define to which bay, module or physical device it refers. This is done by
adding and filling in the relevant relation is memo of (2) at memo level.
Figure 74: Defining the memo’s owner
7.3.4 ATTRIBUTES OF A MEMO ICON

The best practice to create a Memo icon (1) is to use the DS Agile SCE mimic editor (via the DS Agile OI
mimic toolbar) and to adjust some attributes using the attribute editor. For more details about the mimic
editor, refer to the DS Agile SCE user’s manual.
(1)
OI mimic toolbar
S0495ENa
Figure 75: Memo icon of a mimic
Once a Memo icon has been added its attributes can be updated:
(2) x (in pixels): horizontal position of the upper-left corner of the memo icon in its parent window
(3) y (in pixels): vertical position of the upper-left corner of the image in its parent window
OI/EN AP/C57b AP-77

(4) Then, at the Memo icon level the mandatory relation has for memo: (4) must be filled in with the
memo object to which the memo icon refers.
Figure 76: General attributes of a memo icon
7.4 DYNAMIC REPRESENTATION USING DATAPOINT MULTISTATES
7.4.1 DATAPOINT MULTISTATE

The ‘multistate’ concept has been introduced in data modeling to define animations in mimics: it is a kind of
container used to define the dynamic graphical representations of a datapoint depending on its state.
A multistate is always typed according to the type of datapoint that it points to.
It contains several graphical representations, called symbols. Symbol displays are exclusive of one another
as each of them relates to a specific state of the datapoint type that the multistate refers to. A multistate can
AP-78 OI/EN AP/C57b

contain a default symbol, used for all the states of the datapoint that do not have symbol representation in
the multistate. When no default symbol is given in a multistate, there will be no display for datapoint states
not referenced in the multistate. A symbol can be a graphical basic shape, text, or a group composition
containing basic shapes and texts.
There is a set of specific symbols called ‘text symbols’ available for multistates. A ‘text symbol’ makes it
possible to display the real-time value of some text attributes belonging to the datapoint that manages the
multistate. These text attributes depend on the type of datapoint: ‘Short Name’, ‘Long Name’, ‘Resulting
State Label’ (for input datapoint), ‘Value’ (for MV and Counter). As far as DS Agile OI is concerned, integer
and floating values are considered as text values with specific formatting.
A multistate can also be seen as a symbol and embedded in another multistate. Multi-state objects can
belong to a ‘group’ object.
To define a multistate:
(1) create the entry point of the multistate with a right click on Objects entry at mimic level and update its
attributes (see next section)
(2) use basic shapes to define the associated symbol for each state to display (see section 7.2 Static part
with basic shapes) and groups (see section 7.5 Graphical object groups) in group edition mode of the
DS Agile SCE mimic editor at the multistate level (refer to SCE/EN HI). The group thus created
contains at its first hierarchical level all the required symbols overlaying each over.
(3) add all the required ‘xxx’ symbol relations at multistate level, where ‘xxx’ corresponds to the state to be
displayed in the multistate,
(4) fill in each ‘xxx’ symbol relation defined in step (3) with the correct symbol from step (2) (only symbols
inside the multistate can be filled for its ‘xxx’ symbol relations)
(5) fill in the ‘default’ symbol relation at the multistate level, if required (see previous description)
(6) fill in the relation ‘is managed by’ with the correct datapoint
A multistate can be seen as a particular group in which only sub-graphical objects linked to one of its ‘xxx’
symbol relations will be displayed in the ‘xxx’ state. So the group edition mode is very useful in the definition
of multistate symbols.
OI/EN AP/C57b AP-79

Figure 77: Defining a multistate symbol (example for a DPS multistate)
The following table gives for each type of datapoint the corresponding datapoint multistate (see previous
figure) with the available states and subsequently available ‘xxx’ symbol relations.
Type of Datapoint
Available states/symbols
datapoint multistate
RESET
SET
TOGGLING
SELFCHECK FAULT
UNKNOWN
SPS datapoint SPS MultiState (a)
SUPPRESSED
FORCED RESET
FORCED SET
SUBSTITUTED RESET
SUBSTITUTED SET
AP-80 OI/EN AP/C57b

Type of Datapoint
Available states/symbols
datapoint multistate
JAMMED
OPEN
CLOSED
UNDEFINED
TOGGLING
SELFCHECK FAULT
UNKNOWN
DPS datapoint DPS MultiState (b)
SUPPRESSED
FORCED JAMMED
FORCED OPEN
FORCED CLOSED
SUBSTITUTED JAMMED
SUBSTITUTED OPEN
SUBSTITUTED CLOSED
STATE
UNDEFINED
TOGGLING
SELFCHECK FAULT
MPS datapoint MPS Multi-State (c) UNKNOWN
SUPPRESSED
FORCED STATE
SUBSTITUTED STATE
Where 0  i  15
VALID
SELFCHECK FAULT
SUBSTITUTED
FORCED
SUPPRESSED
UNKNOWN
OVER RANGE
MV datapoint MV MultiState (d) UNDEFINED
OPEN CIRCUIT
HHH THRESHOLD VIOLATION
HH THRESHOLD VIOLATION
H THRESHOLD VIOLATION
LLL THRESHOLD VIOLATION
LL THRESHOLD VIOLATION
L THRESHOLD VIOLATION
VALID
SELFCHECK FAULT
UNKNOWN
Counter datapoint Cnter MultiState (e)
UNDEFINED
OVER RANGE
FORCED
NO COMMAND
COMMAND IN PROGRESS
Control datapoint (SPC, OPERATE CLOSE
Ctrl MultiState (f)
DPC or SetPoint) OPERATE OPEN
SELECT CLOSE
SELECT OPEN
7.4.1.1 GENERAL ATTRIBUTES OF A MULTISTATE

Once a Multi State has been added its following attributes can be updated:
(2) x (in pixels): horizontal position of the upper-left corner of the multistate in its parent window
(3) y (in pixels): vertical position of the upper-left corner of the multistate in its parent window
OI/EN AP/C57b AP-81

(4) resizable (No/Depends on hierarchy): this attribute is inherited from group aspect of the multistate
Example given hereafter is for a DPS MultiState
(3
(2
(1)
(2)
(3)
(4)
Figure 78: Attributes of a DPS multistate
7.4.2 DISCREPANCY MULTISTATES

There is a particular type of multistate, the discrepancy multistate, which can be linked to any SPS or DPS
datapoint of the electrical and system topologies.
The discrepancy is the fact that the state of a switching device has changed without reason (i.e. not in
response to a control command from DS Agile).
A graphical representation of the discrepancy can be associated with a device SPS/DPS position during the
configuration process (a flashing triangle for example).
This graphical representation appears when the device is in discrepancy. It disappears when the associated
alarm (in the alarm viewer) has been acknowledged (a SPS/DPS datapoint associated with a discordance
must therefore be alarmed).
A discrepancy multistate is added from the contextual Objects entry window associated with the Mimic level
by double-clicking on Discrepancy MS (or right-clicking on it and then on Add).
AP-82 OI/EN AP/C57b

Figure 79: adding a discrepancy multistate
The discrepancy multistate configuration is similar to the datapoint multistate configuration except that the
relation is managed by must be explicitly selected, added and filled in.
Figure 80: Defining the manager of a discrepancy multistate
The available symbol states for a discrepancy multistate are:
 Yes (there is a discrepancy)

 No (there is no discrepancy)
 For each MultiState: 1, and only 1, relation ’is managed by’ must be linked.
OI/EN AP/C57b AP-83

7.4.3 ALARM AND AUDIBLE MULTISTATES

There are two extra types of multistate, Alarm MultiState and Audible MultiState, which can be linked to
any node object of the electrical and system topologies. On any node, DS Agile OI Server builds an implicit
real-time synthesis of all alarms present in its hierarchy (main alarm status and audibility). Alarm MultiState
and Audible MultiState are a mean to define animation on this alarm synthesis. For instance, a bay in
DS Agile OI Server owns two real-time attributes, one giving the status of the most significant alarm of the
datapoints belonging to it, and the other one the presence of an audible alarm.
Moreover explicit real-time synthesis of alarms can be defined at DS Agile SCE level: directly under the
Graphic root, ‘alarm group’ can be created and linked to particular datapoints to produce a synthesis of alarm
on them and to allow animation on this synthesis.
An Alarm MultiState or an Audible MultiState is added from the contextual Objects entry window
associated with the Mimic level by double-clicking on the required multistate (or right-clicking on it and then
on Add).
Figure 81: Adding an alarm multistate or an audible multistate
The configuration of an Alarm MultiState or an Audible MultiState is similar to the configuration of a

datapoint MultiState except that the relation ‘is managed by’ must be explicitly selected, added and filled in.
AP-84 OI/EN AP/C57b

Figure 82: Defining the manager of an alarm multistate
The available symbol states for an Alarm MultiState correspond to the alarm state of the main alarm inside
the manager hierarchy:
 NO_SIGNIFICANT
 DISABLED
 INACTIVE
 INACTIVE_ACK
 ACTIVE_ACK
 INACTIVE_UNACKI
 INACTIVE_UNACKA
 ACTIVE_UNACK
The available symbol states for an Audible MultiState correspond to the audibility of the main alarm inside
the manager hierarchy:
 NO_AUDIBLE
 AUDIBLE
OI/EN AP/C57b AP-85

7.4.3.1 DEFINING AN ALARM GROUP

As described previously, an Alarm MultiState or an Audible MultiState can also be managed by an alarm
group, which is a specific user-defined synthesis of alarms on a set of datapoints.
An alarm group is added from the contextual Objects entry window associated with the Graphic level by
double clicking on Alarm group (or right-clicking on it and then on Add).
Figure 83: Adding an OI alarm group
Once added, the following alarm group attributes can be updated:

(1)
Figure 84: General attributes of an alarm group
Then the datapoint(s) used by the Alarm group must be defined. This is done by adding and filling in the
relevant relation uses: (2) at Alarm group level.
Figure 85: Defining datapoint(s) used by an alarm group
 For each Multi-State: 1, and only 1, relation is managed by must be linked.

 For an Alarm Group, at least 1 relation uses must be linked.
AP-86 OI/EN AP/C57b

7.4.4 TEXT SYMBOL

A ‘text symbol’ is a state symbol available for multistate. It makes it possible to display the real-time value of
some text attributes belonging to the manager of the multistate. These text attributes depend on the type of
manager.
The following table lists the different text symbols with:
 their available owner multistates and subsequent manager types

 the available manager text attributes.
Text symbol Owner multistate / manager Text attribute
Short name
SPS multistate / SPS datapoint Father short name
XPS txt symbol DPS multistate / DPS datapoint Long name
MPS multistate / MPS datapoint Father long name
Resulting state label
Short name
Father short name
MV multistate / MV datapoint Long name
C/MV txt symbol
Counter multistate / Counter datapoint Father long name
Resulting state label
Value
Short name
SPC multistate / SPC datapoint Father short name
Ctrl txt symbol
DPC multistate / DPC datapoint Long name
Father long name
Short name
Alarm multistate
Father short name
(see section 7.4.3 Alarm and audible multistates)
Grp txt symbol Long name
Audible multistate
Father long name
(see section 7.4.3 Alarm and audible multistates)
Main Alarm Gravity
A text symbol is added from the contextual Objects entry window associated with the Multi-State datapoint
level (DPS MultiState in our example) by double-clicking on xxx txt symbol (xPS txt symbol in our example)
(or right-clicking on it and then on Add).
Figure 86: Adding a text symbol (example for a DPS MultiState)
Once added, text symbol attributes can be updated. They are similar to var. text attributes (for details see
section 7.2.6 Defining a variable text), except that there is an extra attribute (1) used to define which text
OI/EN AP/C57b AP-87

attribute of the datapoint is displayed. The table above lists the available values of this attribute for each type
of multistate.
(1)
Figure 87: General attributes of an xPS text symbol
7.5 GRAPHICAL OBJECT GROUPS

For ease of use, graphical objects can be assembled in a Group (1).
A group is added from the contextual Objects entry window associated with the Mimic level by double-
clicking on Group (or right-clicking on it and then on Add).
Figure 88: Grouping graphical objects
AP-88 OI/EN AP/C57b

A graphical object is added to a group from the contextual Objects entry window associated with the Group
level by double-clicking on the selected graphical object, Circle in our example (or right-clicking on it and
then on Add).
Figure 89: Adding a graphical object to a group
Do not forget that a multistate can be seen as a particular group whose only sub-graphical objects linked to
one of its ‘xxx’ symbol relation will be displayed in ‘xxx’ state (see section 7.4 Dynamic representation using
datapoint multistates).
The best practice to create a group is using DS Agile SCE mimic editor in mimic edition mode. Once a group
created, it can be updated with the DS Agile SCE mimic editor in group edition mode. For more details about
DS Agile SCE mimic editor, refer to the DS Agile SCE technical documentation.
Once a group has been added with the DS Agile SCE mimic editor, its following attributes can be updated
with DS Agile SCE attribute editor:
(2) x (in pixels): horizontal position of the upper-left corner of the group in its parent window
(3) y (in pixels): vertical position of the upper-left corner of the group in its parent window
(4) Resizable (No/Depends on hierarchy):
- When set to No, the group cannot be resized with DS Agile SCE mimic editor.
- When set to ‘Depends on its hierarchy’, a group (B) contained in an other group (A) inherits from the
resizable property of the group (A). If the group (B) is not contained in another one, it is resizeable.
OI/EN AP/C57b AP-89

(3
(2
(1)
(2)
(3)
(4)
Figure 90: Attributes of a group
Note: To resize or move a sub-object of a group, the group edition mode must be enabled for this group.
AP-90 OI/EN AP/C57b

7.6 REAL-TIME ANIMATION OF OBJECTS REPRESENTING MEASUREMENT

VALUES
Graphic objects linked to electrical MV datapoints can be configured to either rotate or slide ("translate")
along a vertical or horizontal axis to offer a more meaningful and eye-catching image of the measurement
value that they represent.
The objects that can be animated are:
 lines,
 polylines*,
 rectangles*,
 circles*,
 groups containing any combination of these objects*.
Each object or groups supports only one animation.
* Although it is technically possible to rotate these shapes, some distortion may occur at certain angles,
mostly due to raster effect or pixellation. Using a straight line in a rotating animation will offer a more
aesthetical graphic display than with a more complex object.
Configuration
 Add and format a standard shape or group of shapes to the mimic.

 Select the shape or group in the Explorer window and add either a Rotation on MV or Translate on
MV function from the contextual Objects entry window.
 Fill in the relation is managed by that was implicitly added along with the function and link it to the
relevant electrical MV datapoint.
 Fill in the attributes of the animation.

Rotation on MV
 short name: only used for internal identification by DS Agile SCE
Parameters:
 value min: minimum value that can be represented for the associated MV datapoint. It would
usually be the same value as configured for the MV's minimum acquisition value, although that is
not compulsory: If the acquired value is lower than the setting for this attribute, the graphic will
display the value corresponding to this setting.
 value max: maximum value that can be represented for the associated MV datapoint. It would
usually be the same value as configured for the MV's maximum acquisition value, although that is
not compulsory: If the acquired value is higher than the setting for this attribute, the graphic will
 center x: horizontal position of the rotation centre, in pixels from the left hand side of the group to
which the object belongs, or from the left hand side of the mimic area if it does not belong to a
group
 center y: vertical position of the rotation centre, in pixels from the top of the group to which the
object belongs, or from the top of the mimic area if it does not belong to a group
 rotation angle for the min value: orientation of the object when the acquired measurement has its
lowest possible value
 rotation angle for the max value: orientation of the object when the acquired measurement has
its highest possible value
OI/EN AP/C57b AP-91

Figure 91: Rotation on MV settings
Notes: - The rotation can follow a clockwise or anticlockwise direction. This is selected when setting the
rotation angles for the minimum and maximum values: If rotation angle for the min value < rotation angle for the
max value, the direction is clockwise, and vice-versa.
- The rotation offset must be proportional to the measurement offset, i.e. the relation between the angle
and the value must be linear.
- The quality of the MV is not taken in account by the rotation animation. In case of a "SelfCheckFault"
or "Undefined" state on the MV datapoint, the animation displays the minimum value defined in the configuration.
Translate on MV
 short name: only used for internal identification by DS Agile SCE
Parameters:
 value min: minimum value that can be represented for the associated MV datapoint. It would
usually be the same value as configured for the MV's minimum acquisition value, although that is
not compulsory: If the acquired value is lower than the setting for this attribute, the graphic will
 value max: maximum value that can be represented for the associated MV datapoint. It would
usually be the same value as configured for the MV's maximum acquisition value, although that is
not compulsory: If the acquired value is higher than the setting for this attribute, the graphic will
 direction: select whether the object should slide horizontally (X) or vertically (Y)
 position min:
 if direction is set to X: horizontal position in pixels from the left-hand side of the group to which
the object belongs, or from the left-hand side of the mimic area if it does not belong to a group,
of the top-left corner of the animated object when the acquired measurement has its lowest
possible value
 if direction is set to Y: vertical position in pixels from the top of the group to which the object
belongs, or from the top of the mimic area if it does not belong to a group, of the top-left corner
of the animated object when the acquired measurement has its lowest possible value
 position max:
 if direction is set to X: horizontal position in pixels from the left-hand side of the group to which
the object belongs, or from the left-hand side of the mimic area if it does not belong to a group,
of the top-left corner of the animated object when the acquired measurement has its highest
possible value
AP-92 OI/EN AP/C57b

 if direction is set to Y: vertical position in pixels from the top of the group to which the object
belongs, or from the top of the mimic area if it does not belong to a group, of the top-left corner
of the animated object when the acquired measurement has its highest possible value
Figure 92: Translate on MV settings
Note: The quality of the MV is not taken in account by the animation function. In case of a "SelfCheckFault" or
"Undefined" state on the MV datapoint, the animation displays the minimum value defined in the configuration.
Example:
In the example below, both animated objects have been positioned on top of bitmaps: the vector replica
rotates on top of a dial image that shows an area of acceptable values and the cursor replica slides along a
horizontal scale, also a bitmap inserted behind the animation.
OI/EN AP/C57b AP-93

Figure 93: Example of animations using the values given in the screenshots above
Best practice
It is recommended to create the translation or rotation object inside a group, in order to avoid having to use
absolute values to set its position in the graphic area. The group can then be freely placed anywhere in the
graphic area.
Translation:
To set the positions of the minimum and maximum values of the translation inside the group, drag and drop
the linked object/sub-group to the position it is meant to assume when the MV has its minimum value, and
make a note of its x (horizontal translation) or y (vertical translation) position as they appear in the
Attributes of: panel. Repeat this operation for the MV's maximum value. If the object is a line, use x1 or
y1.
Select the Translate on MV animation in the menu tree view and fill in its value min and value max
attributes with the recorded values.
Rotation:
The rotating object is necessarily a line. It should be drawn so as to represent the minimum value of the
associated MV, and from the centre of the rotation towards the outside, so that x1/y1 represent the represent
the centre of the rotation. Make a note of its x1/y1 coordinates as they appear in the Attributes of: panel.
Select the Rotation on MV animation in the menu tree view and fill in its center x and center y attributes
with the recorded values for x1/y1.
Note: If the values of the attributes are changed for objects included in an animated object group, the objects should
be ungrouped then grouped again in order to avoid any incorrect behaviour of the animation.
AP-94 OI/EN AP/C57b

7.7 OPTIMIZATION
7.7.1 PRINCIPLES
A database can be created at the earliest stage of the project in order to establish an HMI specification. The
Application or Prototype engineer creates still mock-ups of the final mimic:
The System or Configuration engineer will use this picture – after deleting the objects to be animated – as
background for the final mimic:
OI/EN AP/C57b AP-95

The advantages of using a gif background are:
 fewer objects in the final database: static objects are grouped into 1 single image
 templates are simple animated objects
 faster database compilation
 faster display of the mimic on the OI (the gif format does not use up CPU time).
7.7.2 PROCEDURE AT SPECIFICATION TIME

The mimics must be designed at their actual final size.
In the final database, if for instance the size of the window is 1272 x 694 px; the size of the mimic must be
1262 x 684 in order to account for the borders displayed in the OI Client.
 In the initial database, choose a slightly larger size (1262+1) x (684+1) to compensate for the
shrinking caused by the export process.
 Insert at the bottom-right corner a text label containing the HMI specification release number to ensure
that the GIF image size will be 1262 x 684 after export:
 In order not to display the text ‘VAR’, place a spare text label over the ‘VAR’ text object. Since this text
label is a spare, it will not be displayed in the OI Client:
AP-96 OI/EN AP/C57b

 Finally save and click on the menu item Data/SCE data/Export.

 In the Export manager, scroll down to the mimic, check it, right-click on it, then choose Select sub-tree:
 Click the Export button

 Open the zipped file in the folder (C:/Temp), extract its contents into the Object folder
 Convert the png file into a gif file (using IrfanView for instance)
7.7.3 RE-USE PROCEDURE

 Create an image (refer to SCE/EN HI).
 Create a template (refer to SCE/EN HI) containing only the image object. The name should be
1-background so as to be top-ranked in the breakdown. Only the file name field is in DOF:
 In Object mode, enter the picture file name; then check the graphic view
OI/EN AP/C57b AP-97

 Place the missing object templates on the background blanks:
Templates still to fit Fitted templates
 Animate the instances: see section 7.4 Dynamic representation using datapoint multistates
AP-98 OI/EN AP/C57b

8 VIEWERS
8.1 DS AGILE OI ACTIVEX

The DS Agile OI Client product offers embedded standard ActiveX views that can be placed in mimics:
 Alarm/event/state viewer, for alarm viewing and management (acknowledgement, clearing, …) and
two optional extensions: the event viewer, relevant to the log book display function, and the state
viewer to display the real-time values of datapoints.
 Trend viewer, for curve display (based on archived or real-time values of MV datapoints) and analysis.
 FSS viewer, for the management of datapoint forcing suppression and substitution.
At DS Agile SCE level, ActiveX views are displayed as black boxes in mimics with various degrees of
freedom set by specific attributes (filtering, visualized columns,…). As ActiveX run-time displays are not
integrated in DS Agile SCE, they are displayed in the DS Agile SCE graphical editor as a rectangular shape
(container) which location and size follow those of the ActiveX controls, and colors (name and container) can
be customized when the mimic is edited.
Figure 94: Adjusting ActiveX representation in DS Agile SCE graphical editor (example for the alarm viewer)
8.2 ALARM / EVENT / STATE VIEWER
8.2.1 OVERVIEW OF THE ALARM/EVENT/STATE VIEWERS

These viewers make it possible for the operator to see process and system information from several points
of view:
 Event viewer: historical events in chronological order (a datapoint can thus appear several times with
different states and different time stamps)
 State viewer: current status of information (a datapoint will appear only one time, with its current state
and time stamp)
 Alarm viewer: alarmed information

These viewers are defined in the same ActiveX view through three different tabs (Alarms tab, States tab,
Events tab). During the configuration process, one or several ActiveX views can be configured with different
parameters: these ActiveX views always contain the Alarm tab; the Events and States tabs are optional.
These lists can be printed on the default Windows printer attached to the Operator Workstation (i.e. neither
the SOE printer nor the Log Book printer). All information currently displayed in the list is printed according to
a pre-defined Crystal Report template (the format of this template can be modified at DS Agile OI Client
level).
OI/EN AP/C57b AP-99

8.2.1.1 TEXT FORMAT

The format of information displayed in the Event and State viewers is described in OI/EN HI.
The arrangement and presence of the TimeStamp, Origin, Objectname and Objectmessage properties in
the viewers is defined during the configuration process, separately for each viewer.
8.2.1.2 ALARM VIEWER AND ALARM BANNER

A user-defined mimic displays the alarms present in the system. This mimic is called the “Alarm Viewer”.
Note:
The Alarm Viewer can also include an event and/or a state viewer. Refer to the next sections for more information on
these viewers.
The Alarm Viewer is composed of:
 an Alarm List
 an Alarm Browser (optional)
 a ToolBar (optional)
ToolBar
Alarm Browser Alarm List S0410ENa
Figure 95: Alarm viewer composition
Several “instances” of the Alarm Viewer can be configured in the mimics of the DS Agile OI. Each instance is
configured with its own parameters:
 with / without toolbar, and associated buttons

 with / without browser, and associated information
 with / without pre-defined filters
 with / without checkboxes (allowing alarm selection
 with / without operator confirmation of the acknowledgement / clearing actions
 with / without multi-alarm selection
AP-100 OI/EN AP/C57b

 allowing on-line sorting, or not

 list of the indications contained in the alarm list (see section 8.2.1.4 Line format and video attributes)
The pre-defined filters are typically used when an Alarm Viewer is configured in a dedicated view. These
filters are defined during the configuration process. For example:
View displayed Alarms displayed
Global Overview all the alarms
Voltage level overview alarms of the voltage level
System Overview all the alarms issued from System Inputs
Bay alarms of the bay
The Alarm Browser makes it possible to filter the Alarm List using the Area Path criteria. This browser can
also include, for each level:
 the number of alarms present (i.e. active and inactive alarms)

 the number of active alarms
The Toolbar allows the following actions:
 configure sorting / filtering criteria

 apply sorting / filtering criteria
 print the alarm list
 acknowledge the alarm selection
 acknowledge the alarm group (i.e. alarms selected through the browser)
 acknowledge the alarm page
 acknowledge all the alarms
 clear the alarm selection
 clear the alarm group
 clear the alarm page
 clear all the alarms
Access to these actions is controlled by the user rights (see section 16 DS Agile OI rights definition). The
“print alarm list” action allows printing of the currently displayed alarms (if a filter is applied, only the alarms
displayed with the filter will be printed) on a specific printer (i.e. not the SOE printer nor the Log Book
printer).
8.2.1.3 ALARM BANNER COLUMNS RESIZING

The columns of the Alarm Banner can be resized or not depending of the configuration.
When they are defined as resizable, a horizontal scroll bar is displayed.
8.2.1.4 LINE FORMAT AND VIDEO ATTRIBUTES

The components of this line can be modified during the configuration process (order of the fields, insertion
and removal of fields, in the limit of the default format described below).
A default format is provided by the DS Agile SCE at alarm viewer creation and can be modified by retrieving
or adding information or changing the order of the “fields”.
OI/EN AP/C57b AP-101

The default format of a line in the alarm list contains the following information:
TimeStamp Origin Objectname Objectmessage AlarmState AlarmGravity
Description of the fields:
 TimeStamp: the Date & Time format is defined in configuration. The default format is "dd/mm/yy
hh:mm:ss:msmsms".
 Origin: the origin gives the access path to the alarmed datapoint (for example <Substation
name>/<voltage level name>/<bay name> if the datapoint is defined at the bay level)
 Objectname: name of the alarmed datapoint

 Objectmessage: name of the current state of the data of which the current state is alarmed; e.g. for a
switching device position indication in English version: “OPEN”, “CLOSED”, “JAMMED”, etc.
 AlarmState: one character associated with each alarm state:

 “U” for active-unacknowledged
 “R” for inactive-unacknowledged
 “A” for active-acknowledged
 “I” for inactive-active-unacknowledged
 “space” for inactive-acknowledged
 AlarmGravity: 1 to 5
Moreover, each line has an associated video attribute depending on the state of the alarm and allowing the
operator to identify quickly the states of the remaining alarms in the list. These video attributes are user-
selectable during the configuration process and involve text and background colors. Up to 16 different video
attributes can be defined: one for each alarm state with a particular gravity level associated with it (see
section 5.4 Color settings for alarm management); for instance:
 active-unacknowledged with gravity level 3 = black on a red background

 active-unacknowledged with gravity level 2 = black on an orange background
 etc.
8.2.1.5 ALARM BANNER
The Alarm banner is a dedicated window in which the last “N” alarms that occurred within the system are
displayed whatever their current states or origins.
“N” is defined during the configuration process and can be set from 1 to 10.
The Alarm Banner has the same parameters as the Alarm Viewer, except that operator actions (clearing,
acknowledgement, use of sorting criteria) are not allowed.
This window is always displayed and has a fixed position. Its configuration is described in section 6.5
Standard alarm banner.
Figure 96: Standard alarm banner

8.2.1.6 EVENT VIEWER

The information displayed in the Event viewer comprises:
 Binary inputs (SP, DP, MP, SI and Groups)

 Measurement change of state and value
 Operator action:
 Log-in and log-off,
 Devices control and acknowledgement
To be displayed in the Event Viewer, this information must be configured as to be “archived” (see section
4.3.1 Local archiving definition of event datapoints by DS Agile OI).
The Event viewer is composed of:
 an Event list
 an Event browser (optional, identical to the Alarm browser)
 a Toolbar (optional, identical to the toolbar of Alarm viewer)
 the date of acknowledgement of the alarm
Toolbar
Event Browser Event List S0409ENa
Figure 97: The Event viewer
The Event viewer is configured with the same parameters than the Alarm viewer (refer to section
8.2.1.2 Alarm viewer and alarm banner).

8.2.1.7 STATE VIEWER

The information displayed in the State viewer includes all the real-time:
 states of Binary Inputs (SP, DP, MP, SI and Groups)

 states and values of Tap position indications
 states and values of Measurement changes
managed by the DS Agile OI.
The State viewer is composed of:
 a State list
 a State browser (optional, identical to the Alarm browser)
 a Toolbar (optional, identical to the toolbar of Alarm viewer)
Toolbar
Event Browser Event List S0408ENa
Figure 98: The state viewer
The State viewer is configured with the same parameters as the Alarm viewer.

8.2.2 ALARM/EVENT/STATE VIEWER CREATION

An alarm/event/state viewer is added from the contextual Objects entry window associated with the Mimic
level by double-clicking on Alm/state viewer (or right-clicking on it and then on Add).
Figure 99: Adding an alarm viewer
Once added, the following general attributes of the Alarm viewer must be updated:
(1) short name: only used for internal identification by DS Agile SCE
(2) x and y (in pixels): coordinates of the Alarm viewer in its parent window
(3) width and height (in pixels): size of the Alarm viewer
(4) font (0 to 63): Font used for any text in the alarm list
(5) date format for alarm display (YY/MM/DD, YYYY/MM/DD, MM/DD/YY, MM/DD/YYYY, DD/MM/YY,
DD/MM/YYYY)
(6) background color (0 to 255): for the alarm list
(7) horizontal scroll (No/Yes)
(8) vertical scroll (No/Yes)
(9) header (No/Yes): this attribute defines the presence of a header (column label) for each column of the
alarm list
(10) check boxes (No/Yes): this attribute defines the presence of check boxes in the alarm list. See
explanation below.
(11) confirmation ack/clear (No/Yes): if this attribute is set to Yes a dialog box is displayed for ack/clear
confirmation
(12) contextual menu (No/Yes): if this attribute is set to Yes a contextual menu is opened by right-
clicking each item of the alarm list
(13) double click (No/Yes): only significant if attribute (10) is set to Yes. See explanation below.
(14) multi selection (No/Yes): only significant if attribute (10) is set to Yes. See explanation below.
(15) sort (No/Yes)
(16) sort direction (Decreasing/Increasing): only significant if attribute ((15)) is set to Yes
(17) sort direction change (No/Yes): only significant if attribute ((15)) is set to Yes
(18) printer name: name of the printer used to print the alarms list.

Explanation for (10), (13) and (14)

If attribute ((10)) is set to Yes, a check box is displayed at the beginning of every line in the alarms list. Its
behavior depends on the attributes (13) double click and (14) multi selection:
 if multi selection = Yes

 if check box = Yes:
click on checkbox  selection
double click on item (if set to Yes)  selection
 if check box = False:
double click on item (if set to Yes)  display dialog window allowing item selection.
Simple click  nothing
 if multi selection = No
 if check box = Yes:
click on checkbox  selection
double click on item (if set to Yes)  selection
 if check box = False:
 nothing
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
Figure 100: General attributes of an alarm viewer
Then the following columns attributes of the Alarm viewer can be updated:
For each available column of the alarm list (timestamp, origin, object name, object message, alarm state,
alarm gravity, date of last alarm acknowledgement):
(1) column rank (0 to 9): where 0 means unused (not visible)

(2) origin column content: full area name (on 68 char.), Short area name (on 17 char.), area name N-3
(on 68 char.), area name N-2 (on 51 char.) and
area name N-1 (on 34 char.)
(1)
(2)
(1)
Figure 101: Column attributes of an Alarm viewer
The following Toolbar attributes of the Alarm viewer can then be updated:
(1) Usage (No/Yes): this attribute defines whether the toolbar is displayed. If it is set to Yes the following
attributes must be updated:
(2) position (up/left/right)
(3) position change (Yes/No) in real-time
(4) customization (Yes/No)
For each available button or separator in the toolbar:
(5) the rank (0 to 15) in the toolbar of each available button or separator. 0 means unused (not visible).
(1)
(2)
(3)
(4)
(5)
Figure 102: Toolbar attributes of an Alarm viewer

 there must be at least one column definition with a value different from 0.
 each column value (if different from 0) must be unique
The following Representation in SCE attributes of the alarm viewer can then be updated: These attributes
are valid only for the representation of the alarm viewer in the mimic editor of the SCE.
Figure 103: Representation in SCE of an Alarm viewer’s attributes
8.2.2.1 ADDING OPTIONAL LISTS TO ALARM/EVENT/STATE VIEWERS

The following optional lists can be added to an alarm/event/state viewer:
 Alarms list
 Archives list
 Events list
 States list
This is done from the contextual Objects entry window associated with the Alarm viewer level by double-
clicking the selected list (or right-clicking on it and then on Add).
Figure 104: Adding an optional list to alarm/state viewer

Once added, the following list attributes can be updated:

(3) sorted property (TimeStamp / ObjectName / ObjectMessage)
(4) automatic refresh (No/Yes): In automatic refresh mode the event list is updated periodically (every
5 seconds). It is however possible to freeze/unfreeze the display by clicking a dedicated button
(Suspend Updates button). In non automatic refresh mode the operator has to click another
dedicated button (Update List button) or to switch to another viewer (alarm viewer) in order to update
the events list.
(5) Content: the state viewer displays All / All information except measurements / Only measurements
(i.e. MVs excluding TPI and counters)

Figure 105: General attributes of optional lists

8.2.2.2 ADDING AN OPTIONAL BROWSER TO ALARM/EVENT/STATE VIEWER

A browser can be added to an alarm/event/state viewer from the contextual Objects entry window
associated with the Alm/state viewer level by double-clicking on Browser (or right-clicking on it and then on
Add).
Figure 106: Adding a browser to an alarm viewer
Once added, following browser attributes can be updated:

(2) size (width in pixels)
(3) resize (No/Yes)
(5) display count of present alarms (No/Yes)
(6) display count of active alarms (No/Yes)
(1)
(2)
(3)
(4)
Figure 107: Updating browser properties

8.2.2.3 DEFINING A PRE-FILTERING RELATION FOR AN ALARM/EVENT/STATE VIEWER

An alarm/event/state viewer can be pre-filtered on a specific:
 Bay
 Graphical alarm group (refer to section 7.4.3 Alarm and audible multistates)
 IED (protection device)
 Module
 Substation
 System topology
 IEC 61850-8-1 physical device
 Voltage level
This is done by adding and filling in a relation is pre-filtered on from the contextual Objects entry window
associated with the Alm/state viewer level by double clicking the selected relation (or right-clicking it and
then clicking Add).
Figure 108: Adding a filtering to an alarm/state viewer
 For an Alarm viewer, only 1 relation is pre-filtered on can be linked.

 If a pre-filtered relation is used, the alarm browser must be configured. This browser will be masked
whatever the defined parameters are for this browser.
8.2.2.4 EVENTS DATE FILTER SETTING

The default date filter is set automatically by the DS Agile OI XMLParser to 1 hour (01:00:00).
This default value can be modified by setting the entry EventsDateFilter in the Windows registry.
The EventsDateFilter entry is linked to the key:
HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\XmlParser\OdcConfigurationTool

Setting examples:
Entry Type Value DS Agile OI XMLParser behavior
The DS Agile OI XMLParser sets the default Events date filter
The entry is missing
to 1 hour (01:00:00). (upward compatibility)
EventsDateFilter REG_SZ 01:00:00
to 1 hour 01:00:00 (upward compatibility)
The DS Agile OI XMLParser removes the default Events date
EventsDateFilter REG_SZ
filter. Thus all the events are displayed
EventsDateFilter REG_SZ 720:00:00
to 30 days (720:00:00)
8.3 TREND VIEWER
8.3.1 OVERVIEW OF THE TREND VIEWER

This Active-X allows the visual analysis and observation of real-time / archived analogue / digital datapoints.
As for the Alarm / Event / State viewer, the Trend Viewer is an ActiveX view defined during the configuration
process. Several “instances” of the Trend Viewer can be configured in the mimics of the DS Agile OI. Each
instance is configured with its own parameters:
 the reference of the datapoint to be displayed (only for real-time viewer)

 the curve and axis colour
 the date / time format
The real-time viewer allows displaying of indications on a per event basis, i.e. the curve is updated for each
new value. Only one type of indication can be displayed on a per viewer basis.
The archive viewer allows displaying archived indications: the choice of the datapoint to be displayed and the
range of date is done on-line by the operator. A maximum of 8 curves can be displayed on the same viewer.
Curves have their own format depending of the state of the datapoint to display:
State
___________ VALID
SELFCHECK FAULTY, SUPPRESSED, UNKNOWN, SATURATED, UNDEFINED, OPEN
----------------
CIRCUIT
- - - - - - - OVERSHOOT[1..3]
……………….. UNDERSHOOT[1..3]

A box () is also displayed for each value. A tooltip is attached to each box: it allows displaying the
datapoint’s name, its time stamp, its value and its state.
Figure 109: 2 real-time viewers in the same mimic (example)
Figure 110: Archive viewer with several datapoints (example)

8.3.2 ADDING TREND VIEWER

A Trend viewer is added from the contextual Objects entry window associated with the Mimic level by
double-clicking on Trend viewer (or right-clicking on it and then on Add).
Figure 111: Adding a trend viewer
Once added, the following general attributes of the viewer must be updated:
(2) x and y (in pixels): coordinates of the Trend viewer in its parent window
(3) width and height (in pixels): size of the Trend viewer
(4) trend type (real time/archive): if set to ‘real time’, the viewer displays the evolution of the datapoint
real-time values. If set to ‘archive’, the viewer displays archived values of the datapoint.
(5) font (0 to 63): font used for the text in the viewer
(6) text color (0 to 255): colour used for the text in the viewer
(7) background color (0 to 255): background colour of the chart
(8) border color (0 to 255): border colour of the chart
(9) title: header to be displayed at the top of the chart
(10) time based (No/Yes): if set to Yes, values are plotted with Time on the X-axis. If set to No, this is an
event-based plot, with the event sequence number on the X-axis
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
Figure 112: General trend viewer attributes

Then the following Representation in SCE attributes of the trend viewer can be updated: these attributes
are valid only for the representation of the trend viewer in the mimic editor of the SCE.
Figure 113: Trend viewer attributes in SCE
8.3.3 SETTING PRE-DEFINED PENS

Once a trend viewer has been set, it is fully operational at DS Agile OI Client level, but datapoints (up to
eight) appearing in the viewer must be selected at run-time.
Sometime, trend viewers must be pre-filtered on given MV datapoints when displayed.
This is done by configuring pens at trend viewer level.
A pen (or series) corresponds to a particular line in the chart. It can be linked to a particular datapoint at
DS Agile SCE level.
By default, at trend viewer creation, one pen is created with X-axis and Y-axis sub-objects. Up to seven extra
pens can be added by double-clicking on Series from the contextual Objects entry window associated with
the Trend viewer (or right-clicking on Series and then on Add).
Figure 114: Adding a pen to a trend viewer
Once a pen has been added, its attributes can be set (pen attributes, X and Y axis attributes):
(2) pen color (0 to 255)
(3) short name of the X axis: only used for internal identification by DS Agile SCE
(4) color (0 to 255): color if the X axis
(5) label: label of the X axis

(6) time format for the pen on the X-axis (mm/dd/yyyy, dd/ mm/yyyy, mm/dd/yyyy – hh:mn:ss, dd/
mm/yyyy – hh:mn:ss, hh:mn:ss:mss, hh:mn:ss, hh:mn, mn:ss, ss:mss)
(7) short name of the Y axis: only used for internal identification by DS Agile SCE
(8) label: label of the Y axis
(9) decimal number (0 to 5): number of decimals for the Y axis
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
Figure 115: General pen attributes
To link a pen to a given MV datapoint:

(1) Add a Variable object at pen/series level
(2) Set its property value type (current / daily mean / monthly mean / annual mean) to select the desired
synthesis (current or mean value) of the datapoint
(3) At Variable level, add and fill in the mandatory relation refers (3) with a given MV datapoint.

(1)
(2)
(3)
Figure 116: Linking a pen to an MV datapoint
 If a Trend viewer has its trend type attribute set to real time, then it can have only one Series.
8.4 FSS VIEWER
8.4.1 OVERVIEW OF THE FSS VIEWER

The configuration of the Forcing, Suppression and Substitution (FSS) functions is described in the DS Agile
C26x Application chapter.
Two operator interfaces are available for the FSS function:
 the SBO control popup, which allows to directly force, suppress, substitute the datapoint referring to
the status of a device (refer to section 9.3 Launch action: Open control popup), applicable to
datapoints managed by DS Agile C26x only.
 the FSS viewer, applicable to datapoints managed by both DS Agile C26x and DS Agile Gateway.

The FSS viewer is an ActiveX view with a similar “look and feel” to that of the Alarm / State / Event viewer,
with different icons in its toolbar depending on the configured function (Force, Substitute or Suppress) and
no tabs (one pane per viewer). A layout example is shown below:
Toolbar
"Force"
FSS Viewer
Toolbar
"Suppress"
FSS Viewer
Toolbar
"Substitute"
FSS Viewer
Browser Datapoint List S1003ENb
Figure 117: FSS viewer composition
The Force / Suppress / Substitute functions must be defined in separate viewers.

The toolbar is used to:
 to print the displayed FSS datapoint lists

 to launch the window dedicated to datapoint forcing or datapoint substituting or datapoint suppressing.
8.4.2 ADDING AN FSS VIEWER

An FSS viewer is added from the contextual Objects entry window associated with the Mimic level by
double–clicking FSS viewer (or right-clicking on it and then clicking Add).
Figure 118: Adding an FSS viewer
Once added, the following general attributes of the viewer must be updated:

(2) x and y (in pixels): coordinates of the FSS viewer in its parent window
(3) width and height (in pixels): size of the FSS viewer
(4) function (Force / Suppress / Substitute): active function for the viewer
(5) browser usage (No/Yes)
(6) font (0 to 63): used for text in the FSS list
(7) date format (YY/MM/DD, YYYY/MM/DD, MM/DD/YY, MM/DD/YYYY, DD/MM/YY, DD/MM/YYYY)
used for the FSS list
(8) printer name
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
Figure 119: General attributes of an FSS viewer
The following attributes of the FSS viewer, relevant to the column definition, can then be updated:
For each available column of the FSS list (timestamp, origin, object name, object message):
(1) column rank (0 to 4): where 0 means unused (not visible)
(2) origin column content: full area name (on 68 char.), Short area name (on 17 char.), area name N-3
(on 68 char.), area name N-2 (on 51 char.) and area name N-1 (on 34 char.)

Figure 120: Columns attributes of an FSS viewer
The following Representation in SCE attributes of the FSS viewer can then be updated: these attributes
are only used to represent the FSS viewer in the mimic editor of the SCE.
Figure 121: SCE attributes of an FSS viewer
When adding an FSS viewer, a State list object is automatically created for which the following attributes
can be updated:
(2) sorted property (TimeStamp / ObjectName / ObjectMessage)

Figure 122: General attributes of a States list
 There must be at least one column definition with a value different from 0.
 Each column value (if different from 0) must be unique.

9 PROCESS CONTROL MIMIC AND POPUP

To control electrical process from mimics, DS Agile OI product gives standard command popup (single-
control popup, multi-control popup, counter popup) or direct command functionality.
In data modelling, these popup are only seen by a ‘launch action’ that can be placed on a static symbol or a
multistate.
Single-control and multi-control popups are modelled in the same ‘open control popup’ object. The context of
this object determines its aspect and behaviour:
 number of relations to an xPC datapoint to set a single- or multi-control popup

 in case of a single control, xPC datapoint characteristics (attribute SBOMode at the datapoint profile
level), context and meaning (open/close control of circuit breaker with or without synchrocheck) refines
control popup identification,
 relations to specific MVs to be displayed in a synchrocheck command context.

Counter popup is modeled in object ‘open counter popup’ and refers to only one counter datapoint.
9.1 LAUNCH ACTION: BINARY DIRECT COMMAND

Such a launch action is used to send directly an order value to a binary control (SPC or DPC datapoint)
without any popup display or confirmation. Only an acknowledgement popup will be displayed at the end of
the control execution.
A Launch action is added from the contextual Objects entry window associated with the multistate
datapoint level (DPS MultiState in the example) by double-clicking on the selected launch action (Send
order in the example) (or right-clicking on it and then on Add).
Figure 123: Adding a binary direct command (example for DPS MultiState)
Once added, the following general attributes of the launch action can be updated:
(2) event (Mouse click / Mouse double click / Mouse enter / Mouse leave / Mouse up / Mouse down)

(1)
(2)
Figure 124: General attributes of a "Send order" action
The datapoint (SPC or DPC) concerned by the launch action must then be inserted:
(1) add and fill in the relation acts on: at launch action level (two available relations exists depending on
datapoint type: SPC or DPC)
(2) set the attributes of the relation, indicating which order must be send (Open / Close for a DPC, Off/On
for a SPC)
(1)
(2)
Figure 125: Setting an xPC datapoint reference for a binary direct command
Finally, a command right reference must be set to accept the launch action in run-time mode (for details
about DS Agile OI rights, refer to section 16 DS Agile OI rights definition). This is done by filling in the
mandatory relation has for command right at the launch action level (3):

(3)
Figure 126: Setting a command right reference for a binary direct command
 No action is allowed under a Symbol or a MultiState located in the sub-tree of a MultiState.
9.2 LAUNCH ACTION: ANALOGUE DIRECT COMMAND

Such a launch action is used to send a control value to a SetPoint. It is done by entering the desired value
into a pre-defined popup in DS Agile OI Server.
Figure 127: Pre-defined popup to send an analog direct command
An ‘analogue direct command’ launch action is added from the contextual Objects entry window associated
with the multistate datapoint level (DPS MultiState in our example) by double-clicking on the selected launch
action (Send value in our example) (or right-clicking on it and then on Add).
Figure 128: Adding an analog direct command (example for a DPS multistate)

(2) event (Mouse click / Mouse double click / Mouse enter / Mouse leave / Mouse up / Mouse down)
(1)
(2)
Figure 129: General attributes of a "send value" launch action
The SetPoint datapoint concerned by the launch action must then be inserted:
(3) fill in the mandatory relation acts on: at launch action level
Finally, a command right reference must be set to accept the launch action in run-time mode (for details
about DS Agile OI rights, see section 16 DS Agile OI rights definition). This is done by filling in the mandatory
relation has for command right: at the launch action level (4):
(3)
(4)
Figure 130: Relations for the Send value launch action
9.3 LAUNCH ACTION: OPEN CONTROL POPUP

There are several types of control popups at DS Agile OI level depending on the way they are configured in
DS Agile SCE, and even more on the number and type of relevant SPC or DPC datapoints.

 ‘Direct execute’ behavior popup:
Figure 131: Direct execute popup
 ‘SBO execute’ behavior popup:
Figure 132: SBO popup
The first type of popup is used for mono-control SPC/DPC datapoint whose SBO mode is set to Direct
execute at SPC/DPC profile level.
The second one concerns the control of several SPC/DPC datapoints (via the command list), or single-
control SPC/DPC for which the SBO mode is set to SBO operate once, SBO operate many or Direct execute
with SBO control box at SPC /DPC profile level. Moreover, an SBO popup enables extra functions:
 synchrocheck bypass if the control relates to synchrocheck locking (for details about configuration of
synchronized circuit-breakers, refer to the DS Agile C26x application document,
 FSS actions which allows to directly force, suppress, substitute the datapoint referring to the status of
the controlled device.
An ‘Open Control Popup’ launch action is added from the contextual Objects entry window associated with
the multistate datapoint level (DPS MultiState in the example) by double-clicking on Open ctrl popup (or
right-clicking on it and then on Add).

Figure 133: Defining an open control popup (example for a DPS multistate)
(2) event (Mouse click / Mouse double click / Mouse enter / Mouse leave / Mouse up / Mouse down): this
attribute defines the mouse activation condition
(3) opening position (On the mouse click point / On the left /On the right / Up / Down / Up on the left / Up
on the right / Down on the left / Down on the right)
(4) opening mode (Open without confirm / Open with confirm)
(5) Automatic closure (No/Yes): this attribute defines, if it is set to Yes and in conjunction with the
attribute Only if positive ack, in which conditions the popup is automatically closed after a control
sequence. If this attribute is set to No the popup is not automatically closed after a control sequence,
whatever the setting for the attribute Only if positive ack.
(6) Automatic closure on select (No/Yes): If this attribute is set to Yes the popup is automatically closed
after the selection phase of an SBO sequence only if the selection acknowledgement is positive. If the
selection acknowledgment is negative the popup remains open and the negative acknowledgement
popup is displayed. If this attribute is set to No the popup is not automatically closed.
(7) Only if positive ack (No/Yes): this attribute is only significant if the attribute Automatic closure is set
to Yes. In this case and if this attribute is set to No, the popup is automatically closed after a control
sequence. If this attribute is set to Yes the popup is automatically closed only if the acknowledge
answer to the operate command is successful. If this attribute is set to Yes and if received
acknowledge is negative the popup is not automatically closed.
(8) Enabled lock (No/Yes): this attribute defines if a tab, which gives the possibility to lock the xPC
concerned by the command, is present in the popup
(9) Title format (module name / xPC name / Bay-module name): this attribute defines, in conjunction with
the level of the xPC concerned by the command, the header of the control popup:
 the xPC is under a module of a bay:
 header = <bay short name> < module short name>
 or header = <bay short name> < xPC long name>
 or header = <module short name>
 the xPC is under a bay
 header = <bay short name> < xPC long name >
 or header = < xPC long name >

 the xPC is higher than a bay (i.e substation or voltage level)

 header = < xPC long name >
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
Figure 134: General attributes of an open control popup
The SPC or DPC datapoint concerned by the launch action must then be inserted:
(10) Add and fill in the relation acts on at launch action level (two available relations exist depending on
the type of datapoint: SPC or DPC)
When a control relates to a synchrocheck bypass, up to 3 measurements can be displayed in the control
popup during the synchrocheck bypass action. To display these measurements:
(11) add and fill in (with the relevant MV datapoints) the relation visualizes for synchrocheck: at the
launch action level
(10)
(11)
Figure 135: Relations for an open control popup
 No action is allowed under a Symbol or a Multi-State located in the sub-tree of a MultiState.

 For an Open ctrl popup, all the Datapoints linked to the relation acts on, must fulfill 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)

 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
9.4 LAUNCH ACTION: OPEN COUNTER POPUP

The counter value can be modified by an operator using the following control popup:
Figure 136: Counter popup
An ‘open counter popup’ launch action is added from the contextual Objects entry window associated with
the multistate datapoint level (DPS MultiState in the example) by double–clicking on Open cnt popup (or
right-clicking on it and then on Add).
Figure 137: Defining an open counter popup (example for a DPS multistate)
attributes defines the mouse activation condition
(3) opening position (On the mouse click point / On the left /On the right / Up / Down / Up on the left / Up
on the right / Down on the left / Down on the right)

(1)
(2)
(3)
Figure 138: General attributes of an open counter popup
The Counter datapoint concerned by the launch action must then be entered:
(4) Fill in the mandatory relation acts on at the launch action level
(4)
Figure 139: Relations for an open counter popup

10 MIMIC CHAINING
To change a mimic, a specific launch action is available: A Change view object can be placed on a static
symbol or a multistate.
This action needs to refer to the new mimic to display. It appears in the window it belongs to.
A ‘change view’ launch action is added from the contextual Objects entry window associated with the
multistate datapoint level (DPS MultiState in our example) by double–clicking on Change view (or right-
clicking on it and then on Add).
Figure 140: Mimic chaining (example for a DPS multi-state)
(1)
(2)
Figure 141: General attributes of a Change view action
The new mimic concerned by the launch action must then be inserted:
(1) Fill in the mandatory relation has for new view at the launch action level

(3)
Figure 142: Setting a mimic reference for the Change view

 Each relation has for new view of a Symbol Change view action must be linked to a mimic different
from the one under which the symbol is located.

11 SETTING SOFTWARE LAUNCH ON A SPECIFIC IED

To use the setting software with a given IED (IED parameterization), a specific launch action is available:
Run Setting Soft object that can be placed on a static symbol or a multistate.
This action needs to refer to the IED to parameterize.
A Run Setting Soft launch action is added from the contextual Objects entry window associated with the
multistate datapoint level (DPS MultiState in our example) by double–clicking on Run Setting Soft (or right-
clicking on it and then on Add).
Figure 143: Setting software launch (example for a DPS multistate)
(1)
(2)
Figure 144: General attributes of a Run Setting Soft action
The IED concerned by the launch action must then be inserted:

(3) Fill in the mandatory relation parametrizes at the launch action level

(3)
Figure 145: Setting the IED reference for the setting software

12 EXTERNAL APPLICATIONS LAUNCH

To use an external GUI application during a DS Agile OI Client session, a specific launch action is available:
Run Appli object that can be placed on a static symbol or a multistate.
A Run Appli launch action is added from the contextual Objects entry window associated with the
multistate datapoint level (DPS MultiState in our example) by double–clicking on Run Appli (or right-clicking
on it and then on Add).
Figure 146: Launching external software (example for a DPS multistate)
Once added, the following general attributes of the launch action must be updated:
attribute defines the mouse activation condition
(3) Application name: the name of the executable file that launches the application
(4) Parameters: command line option(s) associated with the application, for instance path and name of a
specific file to open or particular login account; delete the default text and leave this field blank if no
options are required (any incorrect entry may prevent some applications from launching or cause
abnormal behaviour).
(5) WorkingDirectory: path of the folder containing the executable file
(6) start behavior (Normal / Iconic / Full Screen): starting mode of the application

(1)
(2)
(3)
(4)
(5)
(6)
Figure 147: General attributes for the running of an external application

Example: snapshot
Path: C:\Program Files\Alstom\DCS\OI\Client\OISnapShot\OISnapShot.exe

13 REPORT LAUNCH
13.1 HOW DO YOU DO A REPORT?

A specific button must be available on the workstation in order to generate a report that can be launched
when operators need it. The system connects to the SQL database to retrieve archived measurement values
and generate a file in a standard format. The report is designed by the operator at configuration time using
Crystal Reports.
The aim of this section is to explain how to do this.
13.2 CREATE A BUTTON TO LAUNCH A REPORT

First you need to configure a button with a Run Report launch action link as shown below:
The Application name and Export format attributes are mandatory.

The Application name is the report’s filename without file extension.
The attribute Export format of a Run Report element must have the "Excel 8.0 (.XLS)" value. Others
export formats cannot be used.
You can define up to 255 different reports.

14 SHORTCUT FUNCTION KEYS

The keyboard’s function keys can be configured to execute some of the launch actions described in the
previous sections:
 Change view: to display a specific mimic view

 Run Appli.: to launch an external application
 Run Report: to launch a report
Twelve shortcuts can be defined, one for each function key on the keyboard: F1 to F12.
Any function key from F1 to F12 can be assigned to any one and only one action of one of the 3 types listed
above.
Although the launch actions themselves are attached to objects placed in specific views, the associated
shortcut function keys will remain available whichever the active view, except if a modal window, such as an
SBO, DE or Memo window, is active: in that case, pressing a function key will have no effect.
To assign a shortcut function key to a launch action, first create and configure the launch action function
according to the procedure given in the relevant section of this manual, then:
 In the tree view, select the desired launch action (Change view in this example, but the procedure is
strictly identical for Run Appli. and Run Report).
 In the contextual Objects entry window, double-click has for shortcut : Shortcut. This adds a has
for shortcut : <Shortcut> relation to the launch action.
 Double-click that relation in order to display the Relation link editor window that contains the list of
available function keys.
 Select the appropriate function key and click OK.
Note:
The Trigger event attribute that can be seen in the contextual Attributes of: Change view/Run Appli./Run Report
window is only useful if the action is to be launched by clicking on a shape or group on the screen (see relevant action
creation section). Simply ignore it if only a shortcut function key is to be used.

C1096ENa
Figure 148: Linking a shortcut function key to a launch action

15 BAY LOCAL OI
15.1 GENERAL REQUIREMENTS

From a configuration point of view, the Bay Local OI is seen as a SINGLE machine, composed of one client
and one server. No new OI Clients can be added. The server cannot be redundant.
A Bay Local OI has an 800x600 resolution screen: Consequently, the banners (header, command, alarm)
cannot be configured and control popups and ActiveX windows are resized to fit this resolution.
Figure 149: Bay OI
Each Bay Local OI has its own graphical workspace. It can be a client of one or several IEC 61850-8-1
servers.
The FILESERV name (option) can be configured. If it is not used, the SQL server PC has the same name as
the OI Server.
The trend type must be of the ‘real time’ type with the exception of Terna.
The toolbar must contain only acknowledge and clear alarm management with the exception of Terna.
Limits checked by the SCE:
 A maximum of 500 Datapoints can be managed by the Bay Local OI

 Up to 5 mimics, 1 alarm/state/event viewer and 1 trend viewer can be defined
 The FSS viewer cannot be configured

15.2 SPECIFIC CONFIGURATION

Add the hierarchy window/mimic/shape-rectangle/Action:
15.2.1 VIRTUAL KEYBOARD

The virtual keyboard "osk.exe" is located in the "C:\Windows\system32" folder.
This virtual keyboard can be launched from the OI application, by configuring a Run Appli. button. Otherwise
the virtual keyboard would be launched from the menu "Start\All Programs\Accessories\Accessibility\On-
Screen Keyboard before launching DS Agile OI Client to be able to log-on.
Figure 150: Virtual keyboard configuration

15.2.2 CONFIGURATION OF THE ACTION BUTTONS IN A MIMIC

Select an Action and enter the attributes:
 Login / logoff
 Password modification
 Exit
 Profiles definition
Figure 151: Configuration of an Action button
Refer also to OI/EN ST.
15.2.3 CONFIGURATION OF GRAPHIC TEXT

This section lists some restrictions relating to the use of the bay panel workspace.
In SCE, special text types are defined:
 current time, to display the current time of DS Agile OI Client

 current date, to display the current date of DS Agile OI Client
 logged user, to display the name of the user
 login state, to display the login state of the session (YES/NO)

Figure 152: Configuration of graphic text
WARNING for these values:
 The box color must be of the Transparent type

 This text CANNOT BE grouped with other graphical symbols.
 For the login state value, box width, box height, orientation, margin width, text color and font are
NOT used.
 Refer also to OI/EN ST.

16 DS AGILE OI RIGHTS DEFINITION
16.1 USER PROFILES
16.1.1 OVERVIEW OF USER PROFILE MODELING

Operator rights are defined for all DS Agile OI sub-systems at the graphic root.
They are split in four sets:
 standard right: elementary right fixed by DS Agile OI product,

 view right: elementary right to visualize a mimic,
 command right: elementary right to control an output datapoint,
 acknowledgement right: elementary right to acknowledge an alarm.
Each DS Agile OI user has a user profile that can be shared with other users. Only user profiles are defined
at DS Agile SCE level. User definition, relevant to user profile configured at DS Agile SCE level, should be
done at DS Agile OI level, with on-line setting capabilities.
A user profile is always constituted of four categories:
 standard right category: definition of the valid standard rights,

 view right category: definition of the valid viewing rights,
 command right category: definition of the valid command rights,
 acknowledgement right category: definition of the valid acknowledgement rights.
Operator categories are defined by adding to each category the elementary rights that are authorized.
To ease configuration, each category object contains a flag attribute to embed all elementary rights. When
this flag is set to ‘True’ (default value), it is not necessary to add all the elementary rights.
16.1.2 VIEW RIGHTS

To ease configuration, 63 view rights are automatically created in the graphical root when the DS Agile SCE
database is created. The screenshot below shows their location.
To customize a given view right, simply set its short name and long name attributes (1)
(1)
Figure 153: General attributes of view rights

16.1.3 COMMAND RIGHTS

To ease configuration, 57 command rights are automatically created in the graphical root when the DS Agile
SCE database is created. The screenshot below shows their location.
To customize a given command right, simply set its short name and long name attributes (1).
(1)
Figure 154: General attributes of command rights
16.1.4 ACKNOWLEDGEMENT RIGHTS

To ease configuration, 64 alarm acknowledgement rights are automatically c in the graphical root when the
DS Agile SCE database is created. The screenshot below shows their location.
To customize a given acknowledgement right, simply set its short name and long name attributes (1).
(1)
Figure 155: General attributes of acknowledgement rights
16.1.5 USER PROFILE

A user profile is implicitly created when a new DS Agile configuration is created at DS Agile SCE level. By
default, it inherits all rights.

If an extra user profile is required, it can be added from the contextual Objects entry window associated
with the Usr profile list level by double-clicking on User profile (or right-clicking on it and then on Add).
These four categories are then automatically created:
(7) Alarm acknowledgement right category: definition of the valid acknowledgement rights.
(8) Command right category: definition of the valid command rights.
(9) Standard right category: definition of the valid standard rights.
(10) View right category: definition of the valid view rights.
Figure 156: Adding a user profile and defining categories
For a user profile the following attribute must be updated:

(1)
Figure 157: General attributes of a user profile
16.1.5.1 STANDARD USER RIGHT CATEGORY

Any user profile contains a standard user right category that can be updated. By default all standard rights
are granted to a user profile when it is created. To remove any specific right just set its value to ‘No’.
The settable attributes of a standard right category, and more particularly the standard rights existing in the
DS Agile OI product, are listed below:
(1) short name and long name: only used for internal identification by DS Agile SCE
 In the standard command banner:

(2) exit (No/Yes)
(3) hard copy (No/Yes)

(4) audible alarm stop (No/Yes)

(5) SMT administrator (No/Yes): to grant administrator rights using SMT
(6) SMT and analysis tools (No/Yes): enable SMT and analysis tools launching
 In the alarm viewer:

(7) print (No/Yes)
(8) archive viewing (No/Yes)
(9) filtering (No/Yes)
(10) sorting (No/Yes)
(11) setting saving (No/Yes)
(12) field resizing (No/Yes)
(13) field removing (No/Yes)
 In the trend viewer:

(14) print (No/Yes)
(15) panoramic zoom (No/Yes)
(16) add pen (No/Yes)
(17) start and stop (No/Yes)
(18) pen definition (No/Yes)

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
) (17)
(18)
Figure 158: Attributes of standard user rights
16.1.5.2 COMMAND, VIEW OR ACKNOWLEDGEMENT RIGHT CATEGORY

The following description is available for command, view or acknowledgement right category: in the text, <X>
can be replaced by command, view or acknowledgement.
Any user profile contains a <X> right category that can be updated. By default all <X> rights are granted to a
user profile when it is created. To cancel this global inheritance simply set the value of the attribute (2) to
‘No’.
The settable attributes of a standard right category, and more particularly the standard rights, existing in the
DS Agile OI product are listed below:
(1) short name and long name: only used for internal identification by DS Agile SCE
(2) all <X> rights (No/Yes)

(1)
(2)
Figure 159: General attributes of a command right category
When all <X> rights attributes are set to No, particular <X> rights (Ri) can be granted to the category (A) by
following these steps:
(1) At DS Agile SCE level, reach the particular <X> right object (Ri) that must be granted to the category
(2) Add the relation belongs to at the <X> right level
(3) Fill it in with the relevant category (A)
Figure 160: Granting a specific user right to a category (example for a command right category)

16.2 USER RIGHT MAPPING DEFINITION ON ELECTRICAL AND SYSTEM

TOPOLOGIES
From the DS Agile system point of view, command rights are refined. They also include the following rights:
 bypass right
 locking right
 forcing/suppression/substitution right (FSS right)
 control right (or command right)
At several levels of the electrical topology, linking the electrical object to the elementary right can set some
rights. Sometimes, setting the user right is only significant for the descendants of the object (in fine the
descendant datapoints): for instance, setting a bypass right at a Voltage level object is only significant for the
bays, the modules and the controls it contains.
The following table lists the availability of specific user rights for the various levels of the electrical topology.
Site Substation Voltage level Bay Module
Has for bypass right X (*) X X X
Has for locking right X (*) X X X
Has for forcing/ suppression/ substitution right X (*) X X X
Has for control right X (*) X X X
Has for acknowledgement / clear right X (*) X X X X
(*): mandatory for implicit inheritance by the descendants.
A similar approach can be done for the system topology, but without the bypass and locking rights possibility.
Scs DS Agile device
Has for forcing/ suppression/ substitution right X (*) X
Has for control right X (*) X
Has for acknowledgement / clear right X (*) X
(*): mandatory for implicit inheritance by the descendants.
16.2.1 DEFAULT USER RIGHT MAPPING

The definition of default user right mapping on electrical and system topologies is done by filling in the
following mandatory relations with the relevant rights:
 At Site level:
(1) has for Bypass right
(2) has for command right
(3) has for Forcing/Sub./Sup. right
(4) has for ind. AckClear right
(5) has for lock right
 At Scs level:
(6) has for command right
(7) has for Forcing/Sub./Sup. right
(8) has for ind. AckClear right

Figure 161: Setting the default user right mapping on electrical and system topologies
16.2.2 USER RIGHT MAPPING

To refine rights’ mapping on a particular electrical or system object, simply add and fill in the correct relation
has for <xxx> right (1) at the object level. In this case, all sub-objects will inherit this defined right, except if
inner refinement is done.
(1)
Figure 162: Refining the user right mapping on electrical and system topologies (example for a feeder bay)
16.3 USER RIGHT MAPPING DEFINITION ON MIMIC

Each mimic must be linked to an elementary view right.
This can be done by:
(1) Setting the mandatory relation has for view right at graphical root level, producing an implicit
inheritance on all sub-mimics.
(2) Adding and filling in a relation has for view right at the mimic level

(2)
(1)
Figure 163: Setting the user right mapping on a mimic


HUMAN INTERFACE
OI/EN HI/C57
DS Agile Operator Interface Human Interface
Contents
1 INTRODUCTION 3
1.1 Scope of the document 3
1.2 Main features 3
1.3 Keyboard shortcuts 3
2 PICTORIAL REPRESENTATION 4
2.1 Workspace organization 4
2.2 Tooltip 6
2.3 Mimic types 6
2.4 Measurement display 6
2.5 Counter display 6
2.6 Hardcopy 6
2.7 Access to other applications 7
2.8 Alarm display 7
2.8.1 Several levels of alarmed data graphical representation 7
2.8.2 Forms and colours 7
2.8.3 Acknowledgement and clearing interfaces 8
2.8.4 Individual alarm 8
2.8.5 Graphical group 8
2.8.6 Alarms viewer 8
3 VIEWERS 9
3.1 Event, state, alarm and archive viewers 9
3.1.1 Alarm Viewer and Alarm Banner 10
3.1.2 Event viewer 18
3.1.3 Event banner 19
3.1.4 State viewer 20
3.1.5 Archive viewer 21
3.2 Trend Viewer 24
3.2.1 Real time trend viewer 25
3.2.2 Archive trend viewer 30
3.3 Bay local OI 36
OI/EN HI/C57 HI-1

Human Interface DS Agile Operator Interface
HI-2 OI/EN HI/C57

1 INTRODUCTION
1.1 SCOPE OF THE DOCUMENT

This document is a chapter of DS Agile Operator Interface (OI) documentation. It describes its Human Interfaces:
main DS Agile OI and Bay Local OI.
1.2 MAIN FEATURES

As a main video display unit, one or several graphic monitors or LCD-Panels with a default resolution of 1280x1024
pixels are used (the 1024x768 resolution is also supported). For each DS Agile OI Client, up to 4 video display
units can be used.
Controls are performed using a mouse, trackball or track-point.
Press the key  to switch to the Windows menu.
A Bay Local OI displays 640x480 pixels, or 800x600 pixels to allow touch control.
1.3 KEYBOARD SHORTCUTS

All 12 function keys on the keyboard (F1 to F12) can be assigned “launch actions”, thus acting as shortcuts to
launch external applications, display specific mimic views or launch reports. Function key assignment is defined
during the configuration process.
OI/EN HI/C57 HI-3

2 PICTORIAL REPRESENTATION
For pictorial representation, a full graphic display system is used. The highest available screen resolutions are
3200 x 2400 for standard 4/3 display and 5120 x 1024 pixels for extra wide 5/1 display. The display can be spread
over as many monitors as the host computer's hardware and operating system will allow. It is possible to create
and handle more than 250 different diagrams with each containing up to 1000 process datapoints and an unlimited
number of graphical symbols. For each symbol or graphical object (circle, line, etc.) 256 different colours and
5 flashing frequencies can be defined.
This display system allows a simple, convenient and project-oriented preparation of process diagrams and
graphical symbols as well as the accessibility of datapoints through mimics, lists or reports.
2.1 WORKSPACE ORGANIZATION

The display includes 6 sections:
1 Title banner:
Title banner only displays information, no action are available from title banner. The information displayed is:
 Alstom’s logo
 name of the substation
 user name of the operator and its associated authorization profile
 date and time
 substation control mode
HI-4 OI/EN HI/C57

 connection status of the OI on the Station Bus (thumbnail / )

2 Tool banner (aka Command banner):
 user login / logoff (ref. operator access rights)
 password modification
The OI password can be changed by the user in the Password Utility dialog box.
The newly entered password can be submitted to a validation process or not, according to specific rules,
depending on a registry entry. For the AdmOdyssey user name, the password is Odyssey.
 profiles
 memo status
 application tools launcher (setting software, …)
 DS Agile SMT Client launcher
 horn (audible alarm klaxon) general stop
 screen / windows hardcopy
 Alstom Grid Website
 this chapter in Pdf format
The Acrobat Reader software must be installed on the PC in order to be able to view the OI help file (by Help in
the OI Client).
 About…
 archive restore
 OI Client application stop
All the buttons, except "user login / logoff" and "OI Client application stop", can be hidden by configuration.
3 Mimics
4 Short alarm / event list
5 Mimic access banner: the buttons defined in this banner allow the access to alarm and event lists, to mimics,
reports, curves… These buttons are configured using the SCE application.
6 This section appears in case of multiple screens: it is used to display mimics (e.g. section 3)
OI/EN HI/C57 HI-5

2.2 TOOLTIP
Tooltip is available for the tool banner icons: a clear text indicates the function of each icon.
2.3 MIMIC TYPES

Mimics are configured using the DS Agile System Configuration Editor. They are available in areas 3 and 6 of the
workspace. All mimics can be set to be movable, resizable and can be reduced (icon).
Depending on the different voltage levels and the number of bays per voltage level, the system can provide the
following mimics:
 substation overview with a logical switching device information summary per bay, specific analogue values
 a number of detailed overviews for different sections with all the necessary detailed information per bay
 a detailed overview for control of all transformers per voltage level (including all transformer bays and bus
coupler bays)
 system overview or detailed view, to display the status and links of all controlled devices
 gas status overview (for GIS substations)
or any kind of custom-defined views (if the information is available in the system and with respect to the constraints
given in the Product Specification document).
The representation of devices (switchgear, transformer…) in mimics can be configured using any customer
template. They are animated using the state and / or the value of the device.
In those mimics the following ActiveX viewers can also be configured:
 alarm list / event list / state list

 trend viewer
 reports (issued from Crystal Report tool)
 force / suppress / substitute (FSS) viewer
2.4 MEASUREMENT DISPLAY

Measurements can be displayed in the mimics with the following formats:
 Display only significant figures (yes / no)

 Display non-significant zeros (yes / no)
 Display in percentage mode (yes / no)
 Display unit (yes / no)
The format is defined during the configuration process.
Additionally, specific text and / or colour can be configured to display the measurement state.
2.5 COUNTER DISPLAY

Counter values can be displayed in the mimics. The measurement formats are also available for the counters.
2.6 HARDCOPY
A dedicated button in the tool banner allows printing a screenshot of the current screen or of the currently
active window.
HI-6 OI/EN HI/C57

The multiscreen snapshot tool (if installed) is launched when clicking Hardcopy from the Command banner. It can
be also launched from any button; refer to chapter OI/EN AP.
2.7 ACCESS TO OTHER APPLICATIONS

It is possible to define external applications in the configuration. This way, the user who has the corresponding
rights can launch those applications from the Command banner via the tools button .
2.8 ALARM DISPLAY

This section deals with the different potential representations of alarms at the DS Agile OI.
2.8.1 SEVERAL LEVELS OF ALARMED DATA GRAPHICAL REPRESENTATION

During the configuration process each alarm can have the following types of graphical representation:
 no graphical representation
 one graphical representation displayed in a particular view (e.g. in the detailed view of a bay)
 one graphical representation displayed in several different views (e.g. same representation in detailed view
of the bay and in the substation overview)
 several graphical representations displayed in different views (e.g. one graphical representation in detailed
view of the bay and a different one in the substation overview); however, for any given alarm, only one
graphical representation is allowed per view.
The concept of “graphical representation” is explained in the next section “forms and colors”.
Furthermore a set of individual alarms can be “associated” with the same representation. If one of the alarms is
raised the graphical representation changes. This feature is very useful to give a visual “synthetic” information of
the presence and the gravity level of alarms (e.g. for a bay, for a voltage level, for the whole substation).
The alarms belonging to a “graphical alarm group” are defined during the configuration process.
As for an individual alarm, the “graphical alarm group” can have one or several different graphical representations
depending on the views (types and levels). Each of these individual alarms can also have its own individual
graphical representation.
2.8.2 FORMS AND COLOURS

Any pictures, drawings, texts, forms and colours can be used to define a graphical representation. A graphical
representation can be composed of a single graphical state or of several different graphical states, each one being
itself composed of pictures, drawings, texts, forms and colours.
A graphical representation, with different graphical states, associated with an alarm can change depending on the
current state of the alarm. Example of an individual alarm graphical representation:
 “red triangle” when active-unacknowledged

 “red square” when active-acknowledged,
 “yellow triangle” when inactive-unacknowledged
 “yellow square” when inactive-active-unacknowledged
 no graphical representation when inactive-acknowledged or when inactive
OI/EN HI/C57 HI-7

Similarly, a “graphical alarm group” representation can change depending on the current state of the alarms,
components of the group; example of a graphical alarm group where the components are all the alarms of a bay:
 “red triangle” with the greater gravity level of active-unacknowledged alarms of the bay indicated ( => 6
graphical states)
 “yellow triangle” with the greater gravity level of inactive-unacknowledged alarms of the bay indicated (=> 6
graphical states)
 “red square” with the greater gravity level of active-acknowledged alarms of the bay indicated (=> 6 graphical
states)
 “yellow square” with the greater gravity level of inactive-active-unacknowledged alarms of the bay indicated
(=> 6 graphical states)
 nothing when all the alarms of the bay are inactive-acknowledged or inactive (=> 1 graphical state)
3 2
 The first picture indicates that there exists, within the bay, at least one “active-unacknowledged” alarm with a
gravity level of 3
 The second picture indicates that there exists, within the bay, at least one “active-acknowledged” without
gravity level (no present unacknowledged alarms and no active-acknowledged alarms with gravity level
greater or equal to one).
 The third picture indicates that there exists, within the bay, at least one “inactive-unacknowledged” alarm
with a gravity level of 2 (no active-unacknowledged alarms and no inactive-unacknowledged alarms with
gravity level greater than 2).
2.8.3 ACKNOWLEDGEMENT AND CLEARING INTERFACES

As for acknowledgement and clearing via the alarm list, an “acknowledgement” operator access right is required for
these operations.
2.8.4 INDIVIDUAL ALARM

A mouse click on the graphical representation of the individual alarm will display the Alarm Viewer. The operator
then uses the standard acknowledgement / clearing procedures to process this alarm list.
2.8.5 GRAPHICAL GROUP

A mouse click on the graphical representation of the alarm group will display the Alarm Viewer, pre-filtered on the
components of the alarm group. The operator then uses the standard acknowledgement / clearing procedures to
process this alarm list.
2.8.6 ALARMS VIEWER

Refer to the next section.
HI-8 OI/EN HI/C57

3 VIEWERS
3.1 EVENT, STATE, ALARM AND ARCHIVE VIEWERS

These viewers allow the operator to display process and system information from several points of view:
 Event viewer: historical events in chronological order (thus a datapoint might appear several times with
different states and different time-stampings)
 State viewer: current status of information (a datapoint appears only one time, with its current state and time-
stamping)
 Alarm viewer: alarmed information

 Archive viewer: historical events in chronological order from an archived file
These viewers are defined in the same ActiveX window through 4 different tabs (Alarm tab, Event tab, State tab,
Archived tab). During the configuration process, one or several ActiveX windows, with different parameters, can be
configured: these ActiveX windows will always contain the Alarm tab, whereas the Event, State and archived tabs
are optional.
The button is configurable for all viewers (alarms, states, events, archives) and is used to:
 Indicate that a filter/sort action is on-going

 Re-initialize all filtering/sorting criteria when clicking this button
This button has two pictures:
Inactive indicator: no filtering/sorting criterion is applied
Active indicator: a filter or a sorting criterion is currently applied.

The filtering/sorting criteria taken into account are:
 Modification of a column sorting order

 Modification of a filtering criterion
 Object selection in the browser
The filters are saved when the viewer is closed and will still be active when the viewer is opened again.
The sorting and filtering criteria defined for the Alarm viewer are also available for the Event, State and Archived
viewers but they are only applied on the tab for which they have been defined.
Each tab displays a list of events or alarms. The different fields of information about an event or an alarm (origin,
name, time tagging,…) are separated in columns. It is possible to define whether an information field
(corresponding to a column) is displayed or not and how the different fields are sorted during the configuration
process. In this document we describe the various tabs with all their information fields displayed.
The lists provided in those tabs can be printed on the default Windows printer attached to the Operator Workstation
(i.e. not the SOE printer nor the Log Book printer). All the information currently displayed in the list is printed
according to a pre-defined Crystal Reports template (the format of this template can be modified).
OI/EN HI/C57 HI-9

3.1.1 ALARM VIEWER AND ALARM BANNER
3.1.1.1 ALARM VIEWER

The Alarm Viewer is composed of:
 an Alarm List
 an Alarm Browser (optional), used to display only alarms belonging to the selected electrical or system level
 A ToolBar (optional), used to acknowledge/clear alarms, configure sorting/filtering or print the alarm list
ToolBar
Alarm Browser Alarm list S0459ENa
It is possible during the configuration process by specifying pre-defined filters to reduce the application field of the
alarm viewer to a bay, a voltage level, or to system information. Thus the alarm viewer only displays the alarms
belonging to that field.
Depending on the configuration settings, a contextual menu is displayed when the user right-clicks on the alarm
viewer. It is used to carry out usual actions (sorting/filtering, alarm acknowledgement/clearing, list printing).
Alarm display and printing
The indications displayed about an alarm are:
 Time of activity: time of alarm appearance. the Date & Time format is defined in configuration. The default
format is "dd/mm/yy hh:mm:ss.ccc".
 Origin: Access path to the alarmed datapoint (for example <Substation name>/<voltage level name>/<bay
name> if the datapoint is defined at the bay level)
 Name: name of the alarmed datapoint

 Status: state of the datapoint itself (and not the fact that the datapoint is alarmed)
 Alarm state. Represented by one character associated with each alarm state:
 “U” for active-unacknowledged
 “R” for inactive-unacknowledged
HI-10 OI/EN HI/C57

 “A” for active-acknowledged

 “I” for inactive-active-unacknowledged
 “space” for inactive-acknowledged
 Alarm level: level of gravity associated with this alarm. Alarm level is between 1 and 5
Each line has an associated video attribute depending on the state of the alarm and the alarm gravity. This
allows the operator to identify quickly the states of the alarms in the list and to highlight certain types of alarms.
These video attributes are user-selectable during the configuration process and involve text and background
colors. Up to 16 different video attributes can be defined: one for each alarm state with a specific associated
gravity level; e.g.:
 active-unacknowledged with gravity level 3= black on red background
 active-unacknowledged with gravity level 2= black on orange background
 etc.
If the alarm browser is not configured, the alarm tab always displays all the current alarms of the application field
(defined with pre-filters in the configuration).
If the alarm browser is configured, the alarms displayed depend on the field selected in the browser: Only the
alarms belonging to the selected level are displayed. The user will be able to display all the current alarms by
selecting the root of the desired level.
The browser is a tree view. The general tree view structure first contains the sites (one or several), then for every
site two branches: a system branch with information about the Ethernet network and the various devices, and an
electrical branch which contains process information (voltage level, bay level and module level).
It is possible to print the alarm list using the toolbar print button or using the contextual menu (displayed with a
right click on the alarm viewer) and selecting Print list. The printed list corresponds to the displayed list: in other
words it is sorted and filtered.
Alarm refreshment stop
It is possible to stop refreshing the alarm viewer using the toolbar Suspend updates button , for example to
permit display or alarm acknowledgement in case of an excessive amount of information.
Then the button is displayed as “pressed”, and the state bar at the bottom of the alarm viewer is red.
OI/EN HI/C57 HI-11

When alarm updates are suspended, actions such as filtering, sorting, acknowledgement, clearing are possible but
the alarm viewer is not refreshed, therefore the resulting changes will only be displayed when the suspend updates
function is cancelled. The other viewers, and in particular the alarm banner, are still being refreshed.
The suspend updates function is cancelled by clicking again on the suspend updates button . It is also
cancelled when the user clicks on another tab (events, states, archives).
Alarm Sorting and Filtering
It is possible to change the sort order of the alarm list or to reduce the number of alarms displayed according to
several criteria:
 Time of activity
 Name
 Status
 Alarm state
 Alarm level
In the drop-down list of the “sort/filter” configuration window, some criteria other than those mentioned above are
available (transition, user name,…): These criteria should not to be used.
The alarm list sort order can be changed in two different ways:
1 by clicking on the column heading corresponding to the chosen sorting criterion; it is always available
The list is sorted according to the chosen criteria and a small symbol is displayed in the column title
indicating the sorting direction:
 means ascending order
 means descending order

To change the sorting direction, click again on the column heading.
2 using the Configure Sort/Filters window; it is available only if the toolbar has been configured and the user
is granted the corresponding rights. This window is displayed by clicking the toolbar’s sorting/filtering button
or via the Configure sort/filter contextual menu. The following window is displayed:
HI-12 OI/EN HI/C57

The sorting criteria may be selected using the Sort by: drop-down menu (in the example above the selected
criteria is “time of activity”). To apply it to the alarm list, click Sort. To change the sorting direction (ascending or
descending), click Sort again.
In the drop-down menu, some sorting criteria other than those mentioned above are available (transition, user
name, …): These criteria should not be used.
The filtering criteria reduce the number of displayed indications (as compared with the whole current alarm list).
Then can be combined with sorting criteria.
Open the Configure Sort/Filter window; this displays the sort/filter configuration list with the current filters.
Choose a field and click on the Cond. column next to the field; this displays a drop-down list with various condition
operators.
OI/EN HI/C57 HI-13

Various Boolean operators are available depending on the field nature:

Operator Type Description Time String Level Boolean
>= monadic After/more than, or equals to x x x –
<= monadic Before/less than, or equals to x x x –
- dyadic Occurrence Timeslot with respect to present time x – – –
[] dyadic Between x x – –
= monadic Equals to x x x x
For example, to display only the alarms
 less than 30 minutes old: Operator: - Criteria: 0 00:30:00
 more than 30 minutes, but less than 1 h old Operator: - Criteria:00:30:00 01:00:00
 with a level equal to 1:
HI-14 OI/EN HI/C57

To cancel a filter:
1 select the filter he/she wants to cancel
2 click Clear Selected Filter or Reset Selected Filter
3 to accept this change, click OK (in this case the sort/filter configuration windows is closed) or Apply (in this
case the sort/filter configuration window remains open and it is possible to carry out other operations).
Two other buttons are available: Clear All Filters and Reset All Filters, it is recommended not to use them
because they delete configuration pre-defined filters.
To configure a filter:
1 select the filterable field alarm state
2 add the condition
3 select the criterion value.
For example, to display only unacknowledged alarms:
 Click on the Cond. column next to the alarm state, this displays a drop-down menu with the various choices.
Once the condition is selected, another box is displayed to propose various criterion values.
 To accept the new filter, click OK (in this case the sort/filter configuration is closed) or Apply (in this case the
sort/filter configuration stays open and it is possible to carry out other operations).
 To cancel the changes, click Cancel. For some filterable fields such as alarm level, no values are proposed
after the condition has been added. In that case, click on the criteria column next to the field and enter a
value.
Different filtering criteria can be combined.
OI/EN HI/C57 HI-15

Alarm clearing and acknowledgement

It is possible to acknowledge and clear the alarms from the alarm list; an “acknowledgement” operator access right
is required for those operations. The display of a confirmation window can be defined during the configuration
process.
The different steps for acknowledgement and clearing of individual alarms are:
1 Select one or several lines in the alarm list by ticking the corresponding the check-box(es). The
acknowledge selection and clear selection buttons become active.
2 Acknowledge or clear the selected alarms by clicking the dedicated toolbar button:
 acknowledge alarm selection:
 clear alarm selection:

Alarm acknowledgement/clearing is also possible using the contextual menu. Right-click on the alarm viewer and
then select acknowledge selection/reset selection.
The alarms will be acknowledged/cleared only if the acknowledgement/clearing action is available for the state they
are in (see OI/EN FT, section 3.3 Alarm Processing).
HI-16 OI/EN HI/C57

3.1.1.2 ACKNOWLEDGEMENT AND CLEARING OF A GROUP OF ALARMS

A group of alarms to acknowledge (resp. to clear) is defined by all the alarms in “unacknowledged” (resp. “inactive-
acknowledged”) state among the alarms currently displayed in the alarm list. The filtering criteria can be used to
reduce the list, as in the alarm browser.
The different steps include:
1 Define the group of alarms to process by ticking the alarm browser check-boxes. The acknowledge group
button and clear group button are then active.
2 Acknowledge or clear the selected group of alarms by clicking the dedicated toolbar button:
 acknowledge alarm group
 clear alarm group

Alarm group acknowledgement/clearing is also possible using the contextual menu. Right-click on the alarm viewer
and then select acknowledge group selection/reset group selection.
It is also possible to acknowledge / clear:
 the alarms of the currently displayed page

 all the alarms
3.1.1.3 ALARM BANNER
In this dedicated window the last “N” alarms which have appeared within the system are displayed whatever their
current states or origins: this window is called the Alarm Banner.
“N” is defined during the configuration process and can be set from 1 to 10.
The Alarm Banner has the same parameters than the Alarm Viewer, except that operator actions (clearing,
acknowledgement, use of sorting criteria) are not allowed.
This window is always displayed and has a fixed position.
OI/EN HI/C57 HI-17

3.1.2 EVENT VIEWER

The indications displayed in the Event viewer are:
 Binary inputs (SP, DP, MP, SI and Groups) states

 Operator actions:
 Devices’ control and acknowledgement

In order to be displayed in the Event Viewer, the information must be configured in SCE as archived AND logged.
The Event viewer is composed of:
 an Event list
 an Event browser (optional, identical to the Alarm browser)
 a Toolbar (optional, identical to the toolbar of the Alarm viewer)
ToolBar
Event Browser Event list

S0460ENa
The Event viewer is configured with the same parameters as the Alarm viewer’s.
HI-18 OI/EN HI/C57

3.1.2.1 EVENT DISPLAY AND PRINTING

The indications that can be displayed about an event are:
 Timestamp validity: A star means that the date of the event is not valid, no sign means that the date is
valid.
 Date: Date of the event. The Date & Time format is defined in configuration. The default format is "dd/mm/yy
hh:mm:ss.ccc".
 Origin: Access path to the datapoint that the event is associated with (for example <Substation
 Name: Name of the datapoint the event is associated with

 Event message: Message associated with the event.
 Origin category: Specifies the category of the originator that caused the change of value (control point,
automation …)
 Origin Ident: Identification of the originator that caused the change of value
During the configuration of an event list the refresh mode is defined: automatic or manual.
In automatic refresh mode the events list is refreshed periodically (every 5 seconds). It is however possible to
freeze the display by clicking the Suspend Updates button . By clicking it again the events list is updated.
In manual refresh mode click the Update List button or switch to another viewer (alarm viewer) to update the
events list.
It is possible to print the event list using the toolbar Print button or using the contextual menu (available with a
3.1.2.2 EVENTS SORTING AND FILTERING

The only operator actions possible for events are printing, filtering and sorting. Filtering and sorting actions can be
done via the toolbar or the contextual menu, the way to proceed is the same than for all the viewers. Refer to alarm
paragraph for more precision.
3.1.3 EVENT BANNER

The Event banner can list the “N” most recent events. This banner is displayed in the same window than the Alarm
banner (a tab for the Alarm, a tab for the Events).
OI/EN HI/C57 HI-19

3.1.4 STATE VIEWER

The information displayed in the State viewer is real-time:
 state of Binary Inputs (SP, DP, MP, SI and Groups),

 state and value of Tap position indications,
 state and value of Measurement changes,
managed by DS Agile OI.
The State viewer is composed of:
 a State list
 a State browser (optional, identical to the Alarm browser)
ToolBar
Event Browser Event list S0461ENa
The State viewer is configured using the same parameters as the Alarm viewer.
States display and printing
The indications that can be displayed about a state are:
 Timestamp validity:
 a star means that the date of the last state change is NOT valid
 a ‘!’ means that the date of the last state change is NOT valid AND that it has been updated by DS Agile
OI Server
 no symbol means that the date of the last state change is valid
 Date: date of the last state change. The Date & Time format is defined in configuration. The default format is
"dd/mm/yy hh:mm:ss.ccc".
 Origin: Access path to the datapoint (for example <Substation name>/<voltage level name>/<bay name> if
the datapoint is defined at the bay level)
 Name: name of the datapoint

 State message: value of the state
HI-20 OI/EN HI/C57

It is possible to print the state list using the toolbar Print button or using the contextual menu (available with a
State refreshment stop
It is possible to stop refreshing the state viewer using the tool bar Suspend updates button , for example to be
able to still see the different states in case of an excessive amount of information.
Then the button is displayed as “pressed”, and the state bar at the bottom of the state viewer is red.
When states updates are suspended actions such as filtering or sorting are possible but the state viewer is not
refreshed, therefore the changes will only be displayed when the suspend updates function is cancelled. The other
viewers, and in particular the alarm banner, keep on being refreshed.
The suspend updates function is cancelled by clicking again on the suspend updates button . It is also
cancelled when the user clicks on another tab (alarms, events, archives).
States sorting and filtering
The only operator actions possible on states are printing, filtering and sorting. Filtering and sorting actions can be
done via the toolbar or the contextual menu, the procedure is the same as for the other viewers. Refer to the alarm
section for more details.
Specific conditions:
Fields Operators Operand values
State message >=, <=, [ ], = string
Date >=, <=, [ ], ., = hh:mm:ss
Timestamp validity = ! * (out of synchro) void
Name >=, <=, [ ], = string
<= means Before (chronologically or alphabetically), >= means After, [ ] means Includes …
3.1.5 ARCHIVE VIEWER

Archive Viewer is used to display archived events files.
The indications displayed in the Archive viewer are the same as for the event viewer:
 Binary inputs (SP, DP, MP, SI and Groups) states

 Operator actions:
 Devices’ control and acknowledgement

The Archived viewer is composed of:
 an Archived Event list

 an Archived Event browser (optional, identical to the Alarm browser)
OI/EN HI/C57 HI-21

The Archive viewer is configured with the same parameters as the Alarm viewer’s. By default, the archive viewer is
empty. Archived files need to be edited in order to be made available for display.
3.1.5.1 ARCHIVED FILE EDITION

The files which can be edited are DS Agile OI automatically created files. The files contents are defined during the
configuration process and contain all the events defined as being archived every defined period (day, week,
month). If archiving was configured, these files are periodically created and saved under the
X\SharedWorkspace\ArchiveDSAgile directory where X is the SharedWorkspace path defined by the user during
the set-up process. They are saved under a directory which name indicates the corresponding period: For example
2005-03-25-00-00_to_2005_03_26_00_00 means events archived between March 25th at 0:00 and March 26th at
0:00.
These files are then often manually saved onto another media using the NTbackup tool and can be restored using
the same tool. The user can thus either edit files before back-up or edit files after restoration. To be editable the
restored archives must be placed in a shared directory named “ToRestore”. Therefore, before archives edition,
create the archive restoration directory (for example C:\To_restore) if it has not been created yet and share it.
Share procedure:
 Right-click on the relevant directory in Windows Explorer to display the contextual menu
 Select Sharing and security. The share window is displayed.
 Select Share this folder, then enter “ToRestore“ as sharing name and click OK.
HI-22 OI/EN HI/C57

Once the archive directory is created, archives can be edited by:

1 Copying/Restoring the archives directory corresponding to the period that he/she wants to display on the
restoration directory.
2 Click on the command banner archives icon so that the corresponding archived events are
displayed in the archive viewer.

It is possible to display several archived directories in the archive viewer.
3.1.5.2 ARCHIVED EVENTS DISPLAY AND PRINTING

The indications that can be displayed about an archived event are:
 Timestamp validity: A star means that the date of the event is not valid, no sign means that the date is
valid.
 Date: Date of the event. The Date & Time format is defined in configuration. The default format is "dd/mm/yy
hh:mm:ss.ccc".
 Origin: Access path to the datapoint that the event is associated with (for example <Substation
 Name: Name of the datapoint that the event is associated with

 Event message: Message associated with the event.
It is possible to print the archived event list using the toolbar Print button or using the contextual menu
(available with a right click on the alarm viewer) and selecting Print list.
OI/EN HI/C57 HI-23

3.2 TREND VIEWER

This display allows the visual analysis and observation of real-time / archived and analogue / digital datapoints.
As the Alarm / Event / State viewer, the Trend Viewer is an ActiveX window defined during the configuration
process. Two types of trend viewers are available: a real-time trend viewer and an archive viewer.
The real-time viewer allows to display information on an event basis, i.e. the curve is updated with each new value.
Only one datapoint at a time can be displayed on a viewer and this information must have been defined in
configuration.
The archive viewer allows to display archived information: the choice of the datapoint to be displayed and the range
of date is done on-line by the operator. A maximum of 8 curves can be displayed on the same viewer.
Several “instances” of the Trend Viewer can be configured in the mimics of DS Agile OI. Each instance is
configured with its own parameters:
 the reference of the datapoint to be displayed (only for real-time viewer)

 the curve and axis color
 the date / time format
Curves have their own format depending of the state of the displayed datapoint:
___________ VALID
---------------- SELFCHECK FAULTY, SUPPRESSED, UNKNOWN, SATURATED, UNDEFINED, OPEN CIRCUIT
- - - - - - - OVERSHOOT[1..3]
……………….. UNDERSHOOT[1..3]
State viewer
A box () is also displayed for each value. A tooltip is linked to each box: it allows displaying the datapoint name,
its time-stamping, its value and its state.
Several tools are available:
 A slider pans the display:

 along its current range,
 straight to the latest data, depending on the chart direction
HI-24 OI/EN HI/C57

 A button allows to select a zoom area by dragging a box with the mouse. If this area includes the current
time, the viewer remains in real-time mode if it was already in this mode; otherwise real-time updates stop.
“+” and “-“ buttons zooms in or out by 2.
 A button allows to return to the original, non-zoomed parameters

 The “Pause” and “Play” buttons allow stopping and restarting the real-time viewer. Starting real-time viewer
pans the display to the latest time.
3.2.1 REAL TIME TREND VIEWER
3.2.1.1 OVERVIEW
The Trend Display is a special animation that produces a display of up to 8 Registers (Measurement MV) or Bit
variables (SPS, DPS) plotted against time. You can embed any number of Trend Displays in a mimic, with the only
limitation the amount of physical space available. The limit to the number of Trend Displays that you can configure
should be evaluated at the time of validation.
A typical Trend Display is similar to this:
Toolbar
Curves tab
S0488ENa
Each Trend Display contains a configurable display buffer where a temporary historic record of the values for each
trace is stored. The values in the buffer can be displayed on the chart using the scrollbar.
When a mimic containing a Trend Display is initially opened, the buffer is empty. As the buffer fills up, the size of
the slider on the scrollbar changes to reflect the amount of data stored as a ratio of the chart length. For instance, if
the buffer contains ten minutes of data and the chart’s duration is two minutes, the slider is approximately one-fifth
the length of the scrollbar.
OI/EN HI/C57 HI-25

3.2.1.2 RUN-TIME MODE DISPLAY

In run-time mode, the Trend Display plots the value of a maximum of 8 database variables (bit or register) against
time. The horizontal axis represents time; the vertical axis represents the value.
The Trend Display operates in two modes during runtime. Each of these modes is described in a separate topic:
 Real Time Mode: traces are plotted on the chart in real time as the values of the variables they represent
change. You can configure a Trend Display so that it starts in real time or that it can be selected with the play
arrow on the toolbar at runtime.
 Pause Mode: traces are plotted on the chart from the values of variables recorded in the display buffer. You
can switch the Trend Display from real time to pause mode by selecting the pause arrow from the toolbar or
by using the scrollbar.
Trend Real-Time mode
In real-time mode, new values for each trace are plotted starting on the right side of the chart. Older data scrolls
across the chart, eventually disappearing off the left side.
The frequency at which the chart is refreshed depends on the configuration and on how often the data changes.
 The chart is always updated when the value of any variable changes.
 The chart is also refreshed at a background rate determined by the configuration of the Trend Display. For
example, if the background refresh rate is set to 5, the chart refreshes every 5 seconds even if none of the
variables has changed. The value of this parameter is set to 2 by default.
The Trend Display automatically switches to pause mode when you click and drag the slider button along the
scrollbar or when you select the pause tool.
In pause mode, the chart area is no longer updated in real-time; instead, it displays the temporary historic data
recorded in the display buffer. However, the buffer of the Trend Display is still updated in real-time, with the oldest
values being discarded. The effect of this is that the data being displayed on the chart is gradually moving through
the buffer. To represent this visually, the slider button on the scrollbar moves gradually toward the left. If you leave
the Trend Display in pause mode long enough, the data for the time period displayed is discarded.
When the Trend Display is in pause mode, you can scroll backward and forward through the data using the
scrollbar. You can also zoom in and out along both the X and Y axes using either the toolbar or the cursor.
Using the toolbar
The toolbar (to the left of the trend window) contains the tools used to select the mode and for simple zooming in
and out of the chart time axis.
Select Real-Time mode.
Select Pause mode.
Explode the time axis. The time axis is doubled.
Implode the time axis. The time axis is halved.
Restore the time axis to its original setting.
Print the Trend Display on the default printer.
Select Cursor mode.
Zoom in area.
Zoom in on time axis only.
Return to previous zoom level.
HI-26 OI/EN HI/C57

Select Real-Time mode.
Cancel all zooming.
Select the default cursor. Selecting this button disables the Cross Cursor.
Restore the trend to its original configuration.
Change the length for the time axis in units of seconds, minutes, hours, or days.
Select cross cursor mode. Selecting this button disables the Default Cursor.
Using the cursor

When in pause or historic mode, you can use the cursor to interact with the chart area. Using the cursor you can do
the following:
 Display the value of each trace at a particular point in time.

 Zoom in along the time (horizontal) axis.
 Zoom in simultaneously along both the time (horizontal) axis and the value (vertical) axis.
Select the operating mode for the cursor from either the toolbar or a pop-up menu displayed by right-clicking
anywhere in the chart area.
Cross cursor illustration:
Click anywhere in the chart area and a cross cursor appears. In this figure the value appears to the left (350) and
the timestamp at the bottom (06/09/2006 13:53:43).
OI/EN HI/C57 HI-27

Displaying the value of traces:
1 Select the cursor tool: the mouse pointer displays as a cross while it is over the chart area.
2 Click anywhere in the chart: the values for the traces at that point are displayed in the Legend area or in the
Scale area, if visible.
Zooming in along the time axis:
1 Select the zoom in on time axis tool: the mouse pointer changes to a magnifying glass while it is over
the chart area.
2 Click on the chart at the point that represents the new start time for the chart.
3 Hold down the mouse button and drag the cursor to the point that represents the new end time.
4 Release the mouse button.
Zooming in along both axes:
1 Select the zoom in on area tool: the mouse pointer changes to a magnifying glass while it is over the
chart area.
2 Click on the chart at the point that represents the new start time and maximum value for the chart.
3 Hold down the mouse button and drag the cursor to the point that represents the new end time and minimum
value.
4 Release the mouse button.
Using the scrollbar
Use the scrollbar to reach the display buffer data that you want to view in the chart. The width of the scroll button in
relation to the scrollbar length will indicate approximately how much more data is available in the buffer for display
in the chart.
The scrollbar tools behavior varies slightly depending on which mode the Trend Display is in, as described in the
following table:
Real-Time Mode Pause Mode
Switches to Pause mode and scrolls to the oldest data
Scrolls to the oldest data in the display buffer.
in the display buffer.
Switches to Pause mode and scrolls back through
Scrolls back through data in the display buffer.
data in the display buffer.
No action. Scrolls forward through the data in the display.
No action. Selects Real-Time mode.
Displays the Trace Toolbox. Displays the Trace Toolbox.

Selects Pause mode and scrolls through the data in
Scrolls through the data in the display buffer.
the display buffer.
HI-28 OI/EN HI/C57

Using the toolbox

Use the Curves tab to define the aspect of each trace in your Trend Display:
Set the following parameters to configure Curves for the Trend Display:
 Visibility – Temporarily hides individual traces. This can be useful when a trace obscures another.
 Color – Changes the color of each trace
 Name – Name for each trace
 Min/Max – Changes the range of each trace
 Real – Displays the received values
 Cursor – Displays the values at the cursor’s location
 Advanced Properties – Allows access to the Advanced Properties toolbox, all of which may be individually
enabled / disabled. Select from the following:
 Select Variable – Changes the variable for each trace. (See note below)
 Trace Width – Changes the width of each trace
 Trace Style – Changes the plotting style for each trace:
Each dot representing a change in value is connected to the previous one with a single line.
Each dot representing a change in value is connected to the previous one with a vertical and horizontal line.
Each dot representing a change in value is plotted with no interconnecting line.
Note:
Variable selection for each trace is done in a Variable Browser window. It allows, via an OPC browser, to find and select the
variable to trace.
OI/EN HI/C57 HI-29

3.2.2 ARCHIVE TREND VIEWER

The archive trend viewer displays one or several curves based on the archived data in the SQL Historian database.
Example of an archive viewer with several datapoints:
By default, no curve is displayed in the archive trend viewer. The user must define it in SCE.
The red vertical bar is used for time reference when zooming in or out.
HI-30 OI/EN HI/C57

3.2.2.1 CURVE DEFINITION WHERE OI SERVER AND CLIENT ARE CO-HOSTED

To define a new curve:
1 Click the toolbar configuration button (this button is not present in the toolbar of the real time trend
viewer). The configuration window is displayed:
2 Click Add pen. The Trend DataSource Selector is displayed:
3 Click Browse to select the datapoint value to display. The Historical Variable Browser is displayed:
The Historical Variable browser is similar to the alarm viewer’s, except that the “Roots” directory is replaced
with S2Ktrend and 2 additional directories are present. It is necessary to first select the datapoint using the
browser and then click on value item (the value item is only displayed after the datapoint has been selected).
OI/EN HI/C57 HI-31

4 Click OK to accept the selection so that the Trend DataSourceSelector is displayed with the value
datapoint reference in the Item Name area.
5 Click again on OK button. The configuration window is displayed, including the newly defined curve with its
default settings.
6 Close the window by clicking OK or change the settings.
HI-32 OI/EN HI/C57

3.2.2.2 CURVE DEFINITION FOR A STANDALONE OI CLIENT
1 Click the toolbar configuration button (this button is not present on the toolbar of the real time trend
viewer). The configuration window is displayed:
2 Click Add pen. The Trend DataSource Selector is displayed with the Browse button grayed out:
3 Click Add DS…; the Database Setup view is displayed with all its buttons grayed out:
4 Enter a Display Name (for instance “sfsfs”) and the buttons become available:
OI/EN HI/C57 HI-33

5 Select S2KTrend and check that the Server name is correct: it is the name of the DS Agile OI Server. If it is
not, type it in: for example PACP0005:
6 Click Apply, then Test to check the connection to the Database.

7 Select the last Database (the one that has just been added”) and click Remove.
8 Click Finish. The Browse button is now available in the Trend DataSource Selector view.
9 Browse the Database to select a variable as described in the previous section.
HI-34 OI/EN HI/C57

3.2.2.3 CURVE PARAMETERS MODIFICATION

Curve parameters may only be modified for the Archive Trend Viewer.
Curves can be customized using the configuration window (which is opened by clicking the toolbar button ).
It allows to modify:
 Curve display: Using the upper left visibility check box, curves can be selected/or deselected for display.
 Curve availability: The button deletes the corresponding curve
 Curve name
 Curve color: A color selector is displayed when the user clicks on the curve color square. To change the
color, simply select another:
 Background color: A color selector is displayed when the user clicks on the Graph color square. To change
the color, simply select another.
 Axis value display: The button hides/displays the curve value axis.
 Marker type: Choice of different marker types: cross, box, triangle…
 Datapoint value reference: The button opens the Trend DataSource Selector window. Then it is
possible to change the datapoint value reference using the same sequence as for curve addition (as seen
above).
All these modifications are immediately taken into account.
OI/EN HI/C57 HI-35

3.3 BAY LOCAL OI

A Bay Local OI HMI features:
 viewers
 mimics
 a virtual keyboard with the 8” touch screen option (800x600px resolution); it is generally launched via a
dedicated button.
Example:
Since there is no Command banner, the following operator actions may be configured using action buttons in a
mimic:
 Login / logoff
 Password modification
 Exit
 Profile definition
HI-36 OI/EN HI/C57

Example of a mimic with a control being requested (in local mode):
Additional information can be configured in a mimic:
 date and time

 logged user and login status (logon / logoff)
OI/EN HI/C57 HI-37

HI-38 OI/EN HI/C57

MAINTENANCE
OI/EN MF/C57
DS Agile Operator Interface Maintenance
Contents
2 DS AGILE OI REGISTRY KEYS 4

2.1 Configuration of DS Agile OI in the Windows Registry 4
2.1.1 Values after DS Agile OI set-up 5
2.1.2 Editing 7
2.2 DS Agile OI IEC 61850-8-1 Coupling Registry 8
2.3 DS Agile OI Equipment Coupling Registry 8
2.4 DS Agile OI Equipment Coupling Registry Information, OI XML Parser 9
3 FILE HIERARCHY 10
4 UTILIZATION OF TRACES 11
5 LOSS OF DS AGILE AGENCY 12
6 LOSS OF DS AGILE OI SERVER 13
OI/EN MF/C57 MF-1

Maintenance DS Agile Operator Interface
MF-2 OI/EN MF/C57


This document is a chapter of the DS Agile OI manual. It describes the maintenance (MF) procedures and
tools to debug DS Agile OI and manage traces.
This chapter explains how to use the DS Agile OI registry keys to control its behavior and to recover from
minor faults. It describes the files installed by the setup.exe procedure enabling you to check the installation.
OI/EN MF/C57 MF-3

2 DS Agile OI REGISTRY KEYS
2.1 CONFIGURATION OF DS AGILE OI IN THE WINDOWS REGISTRY

Run Regedit. Select the path: HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\OI
MF-4 OI/EN MF/C57

2.1.1 VALUES AFTER DS AGILE OI SET-UP

Key Default value Description
Type of process of agency:
0: agency through
AgencyInProc 1
W32Agency.exe,
1: agency through InProc dll.
Name of the agency’s dll library
AgencyInProcDllName OdAgency.dll
without its path
Absolute path for the location of
AgencyInProcPath C:\ProgramFiles\ALSTOM\DCS\61850agency\exe
the above dll library
The 1st digit of the IEC 61850-8-1
AgencyRev 5.x SBUS Agency must equal 5, the
value for the DS Agile release.
Identification Number of the
ClientID 0
OI Client.
Current configuration specification.
Current Default Its value is: Default, DBID1 or
DBID2
Path of the 1st configuration file
DBID1 \\Server\Configuration\DBID1\S2kHMIConfig
directory
Path of the 2nd configuration file
DBID2 \\Server\Configuration\DBID2\S2kHMIConfig
directory
Path of the default configuration
Default \\Server\Configuration\Default\S2kHMIConfig
file directory
DefaultUser 1
Cycle (in s) for the automatic
update of the Events in the
EventsAutoRefreshCycle 5
Events Viewer (if Autorefresh is
enabled)
IECQualityVersion 2
Path of the Memofolder directory,
MemoFolderLocalPath \\Server\MemoFolder
to share.
Name of Shared MemoFolder
MemoFolderRemotePath MemoFolder
directory
OdysseyHelpPath \\Client\DS AgileHelp\OI_EN_HI_C52.pdf Complete path of the OI Help file.
PasswordPolicyLevel *** 0 Level of Password policy
Name of the development project
Project * Odyssey
for DS Agile
Flag used by OI Client Watch to
RestartFlag 0 restart the OI Client when the
process crashes
Used by OI Server to launch
S2KCmdLineAppli * DS Agile
SCADA 2000
S2KCmdLineOpt
SCADA 2000
S2KCmdLineRedundancy
SCADA 2000
S2KCmdLineStdParam
SCADA 2000
Name of the Shared Persistence
S2KRed_PersistanceDir * PersistanceDSAGILE Directory, used by OI Server to
launch SCADA 2000
S2kSrvHostName PACP0020 OI Server name (IP name)
OI/EN MF/C57 MF-5

Key Default value Description

Scada2000 full path * C:\ProgramFiles\USDATA\S2k\Bin\S2KServer.exe Path of the SCADA 2000 directory
SftRev J.01.03 DS Agile OI software version
Path of the shared
SharedWorkspace C:\ SharedWorkspace "SharedWorspace" directory, this
directory must be shared
Standby configuration
Standby DBID1 specification. Its value is: Default,
DBID1 or DBID2
Compatibility between DS Agile’s
SystRev * 1
modules
ToolsFileLocalPath \\Tools\tools.ini Complete path of the tools.ini file
Name of the SCADA2K
TraceConf OdcS2KTraceConf.xml
configuration trace file
Directory of the SCADA 2K trace
TraceFile C:\Temp\Trace
file
UCA2_DataBagDirectory \\Server\S2Kmodules\UCA2Coupling\DataBag Not used
UCA2C_ErrorDirectory \\Server\S2Kmodules\UCA2Coupling\ErrorTrace Path of the trace files’ directory
Chronological number of trace file
UCA2C_ErrorFileChronoNumber 1
**
Root name of the traces file under
UCA2C_ErrorFileName UCA2Trace <UCA2C_ErrorDirectory>. No
extension
Authorization to replace an
UCA2C_ErrorFileReplaceMode Y
existing trace file
Maximum number of the trace files
UCA2C_KeptErrorFileNumber 10 to be kept. It is a decimal value
from 0 to 999
UCA2C_NamedHMI HMI Name of the HMI in Control
Heart Beat Period (in s) of the
UCA2C_ODHeartBeatPeriodicSc 5 IEC 61850-8-1 SBUS Agency.
Decimal value between 1 to 30.
Identifier of the server application.
UCA2C_ODSWmid 1
Decimal value between 0 to 255
Max number of traces in trace file.
UCA2C_TracingOn 25000 Decimal value. 0 disables tracing,
another value enables tracing.
Version 0
Workspace C:\LocalWorkspace OI Client configuration path
“\\” = “C:\Program Files\ALSTOM\DCS\OI\”
* Never change this key’s value
** Incremented by 1 each time the OI Server is launched.
Range: 0…<UCA2C_KeptErrorFileNumber>. Once the maximum value is reached, this
counter is reset and the old error file with the same number is overwritten by the new one,
except if <UCA2C_ErrorFileReplaceMode> is set to "N". In that case, the traces are not
stored in a trace file.
Full name of the trace file:
<UCA2C_ErrorFileName>.< UCA2C_ErrorFileChronoNumber>
*** 1: with password validation
0: without password validation (default value)
MF-6 OI/EN MF/C57

To be valid the new password must be in accordance with the following rules:
• 7 ≤ number of symbols ≤ 64
• at least 1 capitalized character
• at least 1 digit
The password validation process is activated only when the password is modified in the
Password Utility dialog box.
It has effect no on either of the 2 preconfigured passwords (Administrator and ShortPublic),
nor on the default password assigned to a newly created profile, nor on the passwords that
were previously created with the 0 Password Policy Level.
2.1.2 EDITING
To enable IECCoupling traces, create a String Value and name it IECCouplingTraceOn.
To disable trace creation, refer to section Log configuration file in SBUS/EN ST.
ScadaTrace
S2KCmdLineStdParam key: set the value of /TraceFilePath to
P:\ScadaTrace\ScadaTrace
Where:
P:\ScadaTrace\ = Location for storing the ScadaTrace files
ScadaTrace = Filename prefix that will followed by “_Date_Time”
The server will write its log files in the P:\ScadaTrace folder.
Uca2Coupling
UCA2C_ErrorDirectory key: set its value to P:\UCA2\
ComMgr.log
TraceFile key: set its value to P:\ScadaTrace\
OI/EN MF/C57 MF-7

2.2 DS AGILE OI IEC 61850-8-1 COUPLING REGISTRY

Path => HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\IECCoupling
KEY DESCRIPTION VALUES

Status of IEC 61850-8-1
CouplingRedStatus StandAlone | Master | Slave | Shutdown
Coupling
S2KRedStatus Status of S2KS Server StandAlone | Master (alone) | Master (2) | Slave (2) | Shutdown
Both show the status of IEC 61850-8-1 Coupling and S2K Server in the case of a redundant OI server.
2.3 DS AGILE OI EQUIPMENT COUPLING REGISTRY
KEY DESCRIPTION VALUES

Number of IEC 61850-8-1 reports
ActivatedReports must comply with the data model
Activated by the coupling
Connecting | Compatible | Connected | All reports activated
Status of the IEC 61850-8-1 | All reports deactivated | Not compatible | Disconnecting |
AssocStatus
association OI - Equipment Not Operational | Checking DB compatibility | Checking
ModeDS Operational
Comments
Number of IEC 61850-8-1 reports
InactivatedReports must comply with the data model
deactivated by the coupling
True (If Master in a redundant server), False (If Slave in
IsMaster Indicated if Server is Master or Slave
redundant server)
IsRedundant Indicated if Server is redundant or not True (if Redundant) , False (if not)
Name of Pair Server (redundant
PairName Name of Pair Server (in case of redundant server)
server)
MF-8 OI/EN MF/C57

2.4 DS AGILE OI EQUIPMENT COUPLING REGISTRY INFORMATION,

OI XML PARSER
A Mimic containing a Trend Archive Viewer can be closed automatically when the operator switches to
another Mimic.
A Mimic containing an Alarm Viewer can be closed automatically when the operator switches to another
Mimic.
The AutoClose information is set in the Mimic file by the XML Parser tool during the configuration generation
depending on the value of the following entries in the registry:
VALUE NAME VALUE TYPE COMMENT
AutoCloseTrendA REG_SZ True: AutoClose is enabled; False: No AutoClose
If the entry is missing : the default value is True
True: AutoClose is enabled; False: No AutoClose
AutoCloseAlarm REG_SZ
If the entry is missing: the default value is False
HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\OdcConfigurationTool
The two AutoClose functions are ignored if the Mimic contains a Real Time Trend Viewer.
OI/EN MF/C57 MF-9

3 FILE HIERARCHY
If DS Agile OI is installed in the Program Files default folder, here is the breakdown of the Program
Files\ALSTOM\DCS\OI tree structure:
The DBID1 and DBID2 folders contain the current and standby databases. It is possible to consult the
registry at anytime to check which one is used as the current database and which one is the standby
database:
HKEY_LOCAL_MACHINE\Software\ALSTOM\DCS\OI\Current
The agency.log files are in the UCA2 subfolder.
The following directories must be shared:
DIRECTORY SHARE NAME
C:\Program Files\ALSTOM\DCS\OI\Server\MemoFolder MemoFolder
C:\SharedWorkspace SharedWorkspace
C:\Temp\Trace PersistanceDSAgile
The second one is used at the end of DS Agile OI Client Standalone Installation:
Modify the registry on the PC that hosts the standalone OI Client: set
HKEY_LOCAL_MACHINE\SOFTWARE\ALSTOM\DCS\SharedWorkspace to the path of the
SharedWorkspace folder on the OI Server. If the key does not already exist, create it:
• Add a new String Value

• Set its name to SharedWorkspace
MF-10 OI/EN MF/C57

4 UTILIZATION OF TRACES
To display traces on the PC screen, run Dbwin32.exe. This file is delivered with DS Agile IEC 61850-8-1
SBUS Agency.
WARNING: dbwin does not work on with a PC that has OI Server running as A
service for Windows.
Otherwise, traces files are in the following folders:
• IEC61850 Coupling: C:\ProgramFiles\ALSTOM\DCS\OI\Server\

S2Kmodules\UCA2Coupling\ErrorTrace
Names of trace files: UCA2Trace.x (with x between 1 and 10).
• S2K server: C:\Temp\Trace

Names of trace files: ScadaTrace_mm_dd_yyyy_hh_mm_ss.txt
Note: Bay Local OI: To store the DBWin traces into the P:\DBWin folder (DeportedOIFiles\Dbwin folder on the
FILESERV computer), press the F2 key.
OI/EN MF/C57 MF-11

5 LOSS OF DS AGILE AGENCY

In case of a DS Agile IEC 61850-8-1 SBUS Agency loss, the IEC 61850-8-1 connection symbol change in
DS Agile OI Client’s title banner from to :
MF-12 OI/EN MF/C57

6 LOSS OF DS AGILE OI SERVER
In case of a DS Agile OI Server loss, visual animations are replaced with a red cross in a yellow triangle.
Moreover no event, alarm or state are displayed in the corresponding viewers.
OI/EN MF/C57 MF-13

MF-14 OI/EN MF/C57

RECORD SHEET
OI/EN RS/C57
DS Agile Operator Interface Record Sheet
Contents
1 DS AGILE OI SERVER 3
1.1 PC Characteristics 3
1.2 Installation 3
1.2.1 Software Delivery 3
1.2.2 General Installation 3
1.2.3 Optional Installation 4
1.2.4 Installation checking Checking 4
2 DS AGILE OI CLIENT 5
2.1 PC Characteristics 5
2.2 Installation 5
2.2.1 Software Delivery 5
2.2.2 General Installation 5
2.2.3 Installation checking Checking 6
OI/EN RS/C57 RS-1

Record Sheet DS Agile Operator Interface
RS-2 OI/EN RS/C57

1 DS AGILE OI SERVER
1.1 PC CHARACTERISTICS
PC Name
PC IP Address
PC Supplier
PC Micro-processor
Clock Frequency (GHz)
RAM Size (MB)
Windows Version
Windows Language
Service Pack Issue
1.2 INSTALLATION
1.2.1 SOFTWARE DELIVERY

DS Agile System Version
DS Agile SYSTEM Release Note Checked:
Yes
No
DS Agile OI Version
Microsoft SQL Version
DS Agile OI Release Note Checked:

Yes
No
DS Agile SBUS Agency Version
DS Agile SBUS Agency (IEC 61850-8-1) Release Note Checked:

Yes
No
1.2.2 GENERAL INSTALLATION

Microsoft SQL Installed using the chapter OI/EN IN:
Yes
No
DS Agile OI Installed using the chapter OI/EN IN:
Yes
No
OI/EN RS/C57 RS-3

Microsoft SQL first installation on this PC:

Yes
No
DS Agile OI first installation on this PC:
Yes
No
Microsoft SQL application installed:
Yes
No
SCADA 2000 patches installed:
Yes
No
DS Agile OI Installation directory:
Standard (C:\Program Files\Alstom\DCS\OI)
Other (precise): ____________________________
DS Agile OI Installed as:
Server
Client
Both
1.2.3 OPTIONAL INSTALLATION

OI Server Watch Installation (on OI server):
Yes
No
1.2.4 INSTALLATION CHECKING CHECKING

Check that the following files or folders are in the correct path (refer to chapter OI/EN IN):
OI version directory
S2K
SQL server
Oiserverwatch.ini (optional)
DS Agile OI Server redundancy:
Yes
No
DS Agile OI launched:
Yes
No
DS Agile OI database started:
Yes
No
RS-4 OI/EN RS/C57

2 DS AGILE OI CLIENT
2.1 PC CHARACTERISTICS
PC Name
PC IP Address
PC Supplier
PC Micro-processor
Clock Frequency (GHz)
RAM Size (MB)
Windows Version
Service Pack Issue
2.2 INSTALLATION
2.2.1 SOFTWARE DELIVERY

DS Agile System Version
DS Agile SYSTEM Release Note Checked:

Yes
No
DS Agile OI Version
DS Agile OI Release Note Checked:

Yes
No
2.2.2 GENERAL INSTALLATION

DS Agile OI Installed using the chapter OI/EN IN:
Yes
No
DS Agile OI first installation on this PC:
Yes
No
DS Agile OI Installation directory:
Standard (C:\Program Files\Alstom\DCS\OI)
Other (precise): ____________________________
OI/EN RS/C57 RS-5

2.2.3 INSTALLATION CHECKING CHECKING

Check that the following files or folders are in the correct path (refer to chapter OI/EN IN):
OI version directory
S2K
DS Agile OI launched:
Yes
No
RS-6 OI/EN RS/C57

TECHNICAL DATA
OI/EN TD/C57B
DS Agile Operator Interface Technical Data
Contents
2 MINIMUM REQUIREMENTS FOR THE HOST PC 4

2.1 DS Agile A505Q/A507Q industrial PC characteristics 4
2.2 Industrial/Standard PC minimum characteristics 6
2.3 Fanless Panel PC 6
2.4 Printers 6
2.5 Remote Access 7
2.6 Smart Card Reader 7
2.7 Microsoft SQL 2005/2008 Server 7
2.8 Crystal Reports 7
3 APPLICATION LIMITS 8
OI/EN TD/C57b TD-1

Technical Data DS Agile Operator Interface
TD-2 OI/EN TD/C57b


This document is a chapter of the DS Agile Operator Interface (OI) documentation. It describes the Technical
Data (OI/EN TD) of this product.
DS Agile OI is a software package installed on an industrial or laptop PC so as to increase environmental
capabilities. The technical characteristics of that PC are described in this document.
OI/EN TD/C57b TD-3

2 MINIMUM REQUIREMENTS FOR THE HOST PC

The tables below give the minimum requirements to correctly run the DS Agile OI application.
2.1 DS AGILE A505Q/A507Q INDUSTRIAL PC CHARACTERISTICS

Alstom's rugged DS Agile A505Q or A507Q industrial-type computers are recommended to run DS Agile OI
in harsh environments.
Their technical characteristics are as follows:
Operating conditions
Quantity Operating conditions
Operating: 0°C to +40°C
Temperature:
Non-operating: -20 to +60°C
Operating: 10 ~85% @ 40°C non condensing
Humidity:
Non-operating: 10 ~95% @ 40°C non condensing
Operating: 1 Grms
Vibration (5 ~500 Hz):
Non-operating: 2 G
400W ATX/PFC auto-switching power supply
Power supply:
(100 – 240 VAC, 60 – 50 Hz, 8 – 4 A )
Cooling including air filter: Fans: 1 (12 cm / 114 CFM) + 1 (6 cm / 28 CFM)
Operating: 10 G (with 11 ms duration, half sine wave)
Shock:
Non-operating: 30 G
Design
Quantity Size and weight
Dimensions (WxHxD) : 482 x 177 x 479 mm
Weight: 17.6 kg
Mechanical tests
Tests Standard Conditions
Random vibration (operation) IEC60068-2-64 1 Grms, 5-500Hz
Sine vibration (non-operation) IEC60068-2-64 2 G, 5-500Hz
Shock (operation) IEC60068-2-27 10G (Half sine wave, pulse duration 11ms)
Shock (non-operation) IEC60068-2-27 30G
EMC tests
EN 55022 (2006) +A2 (2010)
EN 55011 (2009) Power port: meet Class A limit
Conducted emission measurement
(Group 1 class A) Telecom port: meet Class A limit
EN 61000-6-4 (2007)
EN 55022 (2006) +A2 (2010)
EN55011 (2009)
Radiated emission measurement Meet Class A limit
(Group 1 class A)
EN 61000-6-4 (2007)
TD-4 OI/EN TD/C57b


EN 61000-3-2 (2006) + A2
Power harmonic measurement emission Meet Class A limit
(2009)
Voltage fluctuations and flicker emission EN 61000-3-3 (2008) Meets the requirements.
EN 61000-6-2 (2005),
EN 55024 (2010), Meets the requirements of Performance
Electrostatic discharge immunity
Criterion A
IEC 61000-4-2 (2008)
EN 61000-6-2 (2005),
Radiated emission immunity
IEC 61000-4-3 (2006) + A1 Criterion A
(2007) + A2 (2010)
EN 61000-6-2 (2005),
Electrical fast transient/burst immunity
IEC 61000-4-4 (2004) + A1 Criterion A
(2010)
EN 61000-6-2 (2005),
Surge immunity
Criterion A
IEC 61000-4-5 (2005)
EN 61000-6-2 (2005),
High frequency conducted immunity
Criterion A
IEC 61000-4-6 (2008)
EN 61000-6-2 (2005),
Power frequency magnetic field immunity EN 55024 (2010), 50Hz or 60Hz; 1A/m, 1 minute, Criterion A
IEC 61000-4-8 (2009)
Electrical tests
Meets the requirements of

Voltage dips:
1. 100% reduction Performance Criterion A
IEC 61000-4-11 (2004)
EN 61000-6-2 (2005)
Voltage Interruptions:
1. 100% reduction Performance Criterion C
AC Voltage dips and voltage variations
Meets the requirements of

Voltage dips:
1. >95% reduction Performance Criterion A
EN 55024 (2010)
Voltage Interruptions:
1. >95% reduction Performance Criterion C
OI/EN TD/C57b TD-5

2.2 INDUSTRIAL/STANDARD PC MINIMUM CHARACTERISTICS

DS Agile OI Server & DS Agile OI Client
Type of PC Standard desktop with Core II duo 2.66 GHz minimum
RAM 2048 MB RAM
Hard Disk 120 GB - FT32 format – 7200 rpm
Windows XP Professional current SP according to the language
Operating System Windows Server 2003 current SP according to the language
Windows 7 Ultimate 64 bits current SP according the language (in XP compatibility mode)
Graphical VGA screen 256 colours minimum, resolution 1024x768 pixels
Ethernet Ethernet port (100 Mb/s)
2.3 FANLESS PANEL PC

DS Agile Bay Local OI
Type of PC Panel PC
Flash disk (option) 2 GB
Operating System Windows XP embedded
Display TFT, resolution: 640 x 480. Touch screen option: 800 x 600
Ethernet Ethernet port (100 Mb/s)
Mechanical
Diagonal length 6.5". Option: 8”
Power Supply
Input Voltage 24 ~ 48 VDC, 110~ 220 VDC
Environment Specifications
Operating Temperature 0 ~ 50° C
2.4 PRINTERS
Three types of printers are available:
 The SOE printers (Sequence Of Event)

 The LB printers (Log Book)
 The HC printers (Hard-Copy)
SOE and/or Log Book printers can be connected using a parallel port or via the Ethernet network.
In case of OI Hot redundancy, only Ethernet printers may be used.
Parallel and network printers cannot be concurrently used.
The SOE and LB printers are 136 column printers; the supported printers are:
TD-6 OI/EN TD/C57b

Parallel port:
 LEXMARK 2591+ (see Warning below)

 OKI ML5791eco
RJ45 port (Ethernet):
 EPSON LQ-2190N
 EPSON LQ-2190 with network kit
 OKI ML5791eco with network kit
 LEXMARK 2591N+ (see Warning below)
 LEXMARK 2591+ with network kit (see Warning below)
Any type of graphic printer can be used for the Hard-Copy function. In the case of LEXMARK printers, page
code 1004 has to be selected in order to print accented characters.
Note: Although the EPSON LQ-2190 and LQ-2190N printers are fitted with parallel ports, that connection is not
supported and these printers can only be used via the Ethernet network.
WARNING:
Lexmark 2591+ / 2591N+ printer:
Power Off/On: Since there is no power-off switch, the only way to power off the printer is
to disconnect its power supply. When the power supply is reconnected, the printer is
"OFF" (off-line) and can only be restarted by pressing the Start/Stop button.
Energy-saving mode: In compliance with EU ENERGY STAR specifications, the printer
will automatically switch to energy-saving mode after a preset inactivity time-delay. This
timeout can be disabled but the printer may revert to its default settings if the power
supply is disconnected. Therefore the settings should be checked after each power
supply disconnection in order to make sure that the timeout is still disabled, and, if
necessary, to disable it again.
2.5 REMOTE ACCESS

DS AGILE OI Client can be installed on any type of remote PC.
2.6 SMART CARD READER

Calyx SSO license, by Calyx NetSecure, with a smart card reader (external USB reader, keyboard with card
reader).
2.7 MICROSOFT SQL 2005/2008 SERVER

DS Agile OI requires Microsoft SQL Server 2005 Standard Edition Runtime 2005 W32 EMBSYS English
OPK CD: Kit: X11-84660 or Microsoft SQL Server 2008 Standard Edition Runtime 2005 R2.
2.8 CRYSTAL REPORTS

Required only if reports are to be customized: Crystal Reports v8.5.
A standalone tool able to capture/print/save each screen individually is used.
OI/EN TD/C57b TD-7

3 APPLICATION LIMITS
Component Maximum authorised

OI Client 8
OI Server 1+ 1 redundant
Printers at OI level 4 (x 2 if redundant)
Visual Display Unit per OI Client 4
System Group 1
Station Bus equipment (controllers, gateways and IEDs) 150
Ethernet MiCOM Alstom/DS Agile switches 127
Site 1
Substations 40
4 if ATCC used
Voltage levels
(< number of electrical bays if no ATCC)
Electrical bays 512
Circuit breakers 512
Disconnectors 2048
Transformers 512
Digital Input Points 37500
Output Control Points 5000
Measurements 7500
Tap Position Indication 512
Counters 512
Setpoints (digital or analogue) 512
Animated objects per mimic 10 groups of bitmap images, 25 blinking items
Animated objects per database 200 groups of bitmap images, 500 blinking items
For Bay Local OI:

Component Maximum supported by SCE
IEC 61850-8-1 servers 5
DataPoints 500
Alarm/state/event viewer 1
Trend viewer 1
Mimics 5
TD-8 OI/EN TD/C57b

GLOSSARY
OI/EN LX/C57A
DS Agile Operator Interface 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.
OI/EN LX/C57a LX-1

Glossary DS Agile Operator Interface
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 OI/EN LX/C57a

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.
OI/EN LX/C57a LX-3

Double Point Status, information derived from 2 digital inputs
DPS
Usually used for Position indication of switching devices (OPEN, CLOSE).
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).
HMGA Horizontal Measurement Graphical Area
Human Machine Interface
HMI Can be DS Agile OI (Operator Interface) or C26x LCD (Local Control Display) or LEDs,
Mosaic...
LX-4 OI/EN LX/C57a

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).
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
OI/EN LX/C57a LX-5

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)
PRP Parallel Redundancy Protocol (defined in IEC 62439-3:2010)
PSL Programmable Scheme Logic
PSTN Public Switched Telephone Network
LX-6 OI/EN LX/C57a

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).
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.
OI/EN LX/C57a LX-7

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
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.
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.
LX-8 OI/EN LX/C57a

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 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
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 .
OI/EN LX/C57a LX-9

LX-10 OI/EN LX/C57a

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

Alstom Bcu

Uploaded by

Copyright:

Available Formats

Alstom Bcu

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

Alstom Bcu

Uploaded by

Copyright:

Available Formats

Operator Interface

System version: 5.0.5

INTRODUCTION OI/IT EN/C57a

SAFETY AND HANDLING OI/SA EN/C57

FUNCTIONAL DESCRIPTION OI/FT EN/C57

HARDWARE OI/HW EN/C57

INSTALLATION OI/IN EN/C57

ADJUSTMENTS OI/AJ EN/C57

APPLICATION OI/AP EN/C57b

HUMAN INTERFACE OI/HI EN/C57

MAINTENANCE OI/MF EN/C57

RECORD SHEET OI/RS EN/C57

TECHNICAL DATA OI/TD EN/C57b

GLOSSARY OI/LX EN/C57a

Refer to the System Release Notes for new features.

2 INTRODUCTION TO DS AGILE MANUALS 4

OI/EN IT/C57a IT-1

IT-2 OI/EN IT/C57a

OI/EN IT/C57a IT-3

2 INTRODUCTION TO DS AGILE MANUALS

2.1 CHAPTER DESCRIPTION

IT-4 OI/EN IT/C57a

Technical Data (TD) Chapter

OI/EN IT/C57a IT-5

IT-6 OI/EN IT/C57a

DS Agile A300 with

The panel PC may also complement a DS Agile C26x-Standalone:

OI/EN IT/C57a IT-7

IT-8 OI/EN IT/C57a

4 COPYRIGHTS & TRADEMARKS 6

5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS 7

OI/EN SA/C57 SA-1

SA-2 OI/EN SA/C57

OI/EN SA/C57 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 OI/EN SA/C57

OI/EN SA/C57 SA-5

4 COPYRIGHTS & TRADEMARKS

SA-6 OI/EN SA/C57

5 WARNINGS REGARDING USE OF ALSTOM PRODUCTS

OI/EN SA/C57 SA-7

SA-8 OI/EN SA/C57

1 SCOPE OF THE DOCUMENT 3

OI/EN FT/C57 FT-1

3.9 Data archiving 78

4 HOT REDUNDANCY CLUSTER 88

5 APPENDIX: USE OF CRYSTAL REPORTS 95

FT-2 OI/EN FT/C57

1 SCOPE OF THE DOCUMENT

OI/EN FT/C57 FT-3

FT-4 OI/EN FT/C57

Alarm Historian Data Communication Controls

OI/EN FT/C57 FT-5

2.2 BASIC FUNCTIONS

FT-6 OI/EN FT/C57