System Devices Configuration

DS Agile Training Level 2

Global Systems Engineering
03/05/2012

GRID

GSE

SAM
 Summary

1) DS Agile OI Device Configuration Page 3

2) MiCOM C264 Device Configuration Page 10

3) DS Agile GTW Device Configuration Page 19

4) Miscellaneous Page 22

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 2
 1.1) Add / Configure DS Agile OI Server

1) Under SCS/Ethernet Network

Add from Object Entry window

Note : use OI configured in starting database

2) DS Agile OI Server Attributes Follow Good Practice for addressing

MV computation period

Network name (Never HMI) + IP@

Periodic SQL Historian DB backup
15 Max number of presence days for
5 event/value in SQL Historian
Good Practice database
GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 3
 1.2) DS Agile OI Server Sons (1)

1) Basic = System Infos + IEC Mapping

List of System Information :

Operating Mode, Synchronisation Status,
...
Note : use OI configured in starting database, all
system information are already configured

IEC 61850 Mapping

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 4
 1.2) DS Agile OI Server Sons (2)

2) Possible sons
Klaxon for audible alarm
Serial Printer

2.1) Printer
Sequence of Events / System Log Book

Printer Name as installed on the PC

(spool name)
for main and backup
Used during ordering process of dated events Used when main printer breaks down during
starting of backup printer

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 5
 1.2) DS Agile OI Server Sons (3)

2.2) Klaxon

Klaxon action (immediate/differed) and acknowledgement

(auto/manu).

Klaxon can be executed on one SPC in one C264

(horn).
If not configured => DS Agile OI Server PC uses
the buzzer

Note : Relation “warns audibility” to determine which alarms are triggering the klaxon

Note2 : The SPC must be direct execute, without dependency, without interlock, with “on” and
“off” orders possibility.
GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 6
 1.3) Add / Configure DS Agile OI Client

1) Under SCS/Ethernet Network

Add from Object Entry window

2) DS Agile OI Client Attributes

Network name + IP@

same if installed on same PC as OI
Server

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 7
 1.4) DS Agile OI Client Sons and Relations

1) Basic = System Infos + Relation to OI Server + Relation to

graphic part
Link Status :
Status of the Link between OI Client and OI Server.

Link to OI Server
-all clients are linked with DS Agile OI
Server Main or Backup.
-At least 1 OI Client has to be connected
on each OI Server.

Link to graphic part

the client will show the views configured
under the chosen workspace

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 8
 Summary

1) DS Agile OI Device Configuration Page 3

2) MiCOM C264 Device Configuration Page 10

3) DS Agile GTW Device Configuration Page 19

4) Miscellaneous Page 22

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 9
 2.1) Add MiCOM C264

1) Under SCS/Ethernet Network

Add from Object Entry window

Note1 : use C264 configured in starting database

Note2 : create new C264 by copy/paste of existing one

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 10
 2.2) MiCOM C264 Attributes (1)

1) General Tab

Computer Name
80TE=C264 / 40TE=C264C

IRIG-B signal or not

Network name + IP@

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 11
 2.2) MiCOM C264 Attributes (2)

2) BI Filtering Tab

Debouncing / Filtering => signal

validation
Toggling parameters
Note : used for SPS, DPS and MPS acquisition on DI board

Debouncing / Filtering => signal validation

F ilte r in g tim e Timetag => t0 or t2 (configurable)
D e b o u c in g
tim e

t0 t1 t2

Toggling applied on validated signal

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 12
 2.2) MiCOM C264 Attributes (3)

3) Measurements Tab

Debouncing / Filtering => signal validation for

Digital Measurements
AI board acquisition cycle

CT/VT board acquisition frequency

(neighbourhood of 0)

MV transmission cycle on SBUS and LHMI

Long period = N x short period

Note 1 : Transmission periods are used if MV is declared as “periodic”

Note 2 : too small transmission periods values has strong impact on SQL Historian database
filling => default values are too small

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 13
 2.2) MiCOM C264 Attributes (4)

4) Counter Tab

Debouncing / Filtering => signal

validation for counted Digital Input
Note : Applicable for single or double counters

5) Miscellaneous Tab

Avoid endless C264 reboot on fault

detection, define a number of faults
acceptable during a period.

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 14
 2.3) MiCOM C264 Sons (1)

1) Basic = System Infos + 3 boards (CPU,BIU,GHU) + IEC Mapping

I/O Boards :
Naming Good Practice :
Slot#_<board type>_<board nb>

IEC 61850 Mapping

Created by Automatic Addressing function

PLC Object
C254 Automations

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 15
 2.3) MiCOM C264 Sons (2)
1) Basic = System Infos + 3 boards (CPU,BIU,GHU) + IEC Mapping

List of System Information :

Operating Mode, Synchronisation Status,
...
Note : use C264 configured in starting database,
all system information are already configured

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 16
 2.3) MiCOM C264 Sons (3)

2) Possible sons = Object Entry Window

Local C264 printer

Hardware

TBUS
LBUS per protocol

3) Add / Configure I/O board

Note : another method is to copy/paste existing board

Physical Board Number

Status of the board given by a MPS

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 17
 Summary

1) DS Agile OI Device Configuration Page 3

2) MiCOM C264 Device Configuration Page 10

3) DS Agile GTW Device Configuration Page 19

4) Miscellaneous Page 22

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 18
 3.1) Add / Configure DS Agile Gateway

1) Under SCS/Ethernet Network

Add from Object Entry window

Note1 : use GTW configured in starting database

2) DS Agile GTW Attributes

Network name + IP@

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 19
 3.2) DS Agile GTW Sons

1) Basic = System Infos + 8 serial ports + IEC Mapping

8 serial communication ports

1 to 4 protocols with the relevant

SCADA mapping

List of System Information :

Operating Mode, Synchronisation
Status, ...
Note : use GTW configured in starting
database, all system information are already
configured
IEC 61850 Mapping GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 20
 Summary

1) DS Agile OI Device Configuration Page 3

2) MiCOM C264 Device Configuration Page 10

3) DS Agile GTW Device Configuration Page 19

4) Miscellaneous Page 22

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 21
 4.1) System Information profiles (1)

1) All Devices Operating Mode (OI, C264, GTW) => MPS

Note 1 : TEST Mode N/A for OI and GTW

Note 2 : Useful for graphical animation

2) MiCOM C264 Boards status => MPS

Note 1 : Applicable for all kind of boards
Note 2 : Special status
Missing = in configuration not in rack
Too Many = in rack not in configuration
OK Empty = used at SMT only

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 22
 4.1) System Information profiles (2)

3) ISaGRAF Status => MPS (under C264/PLC)

Note :
Not Activated = No ISaGRAF configured
Cycle too long = cycle > 2s
Queue Overflow = ISaGRAF overflow

4) DS Agile OI Printer Status (SOE/LOG) => MPS

Note 2 : N/A for C264 printer

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 23
 4.1) System Information profiles (3)

5) Central Archive => MPS (under OIS)

6) DS Agile OI Redundancy Status => MPS (under OIS)

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 24
 4.2) Create Redundant device (1)

1) Create Redundant C264

1.1) Select C264 and “Create Backup”

1.2) Redundant C264 parameters

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 25
 4.2) Create Redundant device (2)

2) Create Redundant OI Server

2.1) Select OI Server and “Create Backup” by a right click on the contextual
menu
2.2) Redundant OI Server parameters

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 26
 4.3) Hot Redundancy for OI Server (1)

1) On DS Agile, Hot redundancy principle :

1.1) OI Client is connected to “preferred” OI Server. If not possible it
will try after inactivity period to reconnect.

1.2) Both OI server perform DP acquisition simultaneously. There is a

consolidating mechanism insuring all data are the same on both.
GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 27
 4.3) Hot Redundancy for OI Server (2)

1.3) Each OI server is managing its own system DP. These are not
consolidating because each server is aware of status of the other one.
1.4) Master OI can :
- acquire DP from IEC servers.
- be connected to OI Client.
- perform archives (Historian) and manage alarms.
- accept and manage controls from any OI Client (directly
connected to itself or connected to OI Slave).
- Print events on SOE printers
1.5) Slave OI can :
- acquire DP from IEC servers.
- be connected to OI Client.
- perform archives (Historian) and manage alarms.
- propagate controls from its OI Client (directly connected to
itself) to OI Master which will manage the controls.

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 28
 4.3) Hot Redundancy for OI Server (3)

1.6) Standalone OI can :

- acquire DP from IEC servers.
- be connected to OI Client.
- perform archives (Historian) and manage alarms.
- accept and manage controls from its OI Client (directly
connected to itself) as the other Standalone OI; but in that case Control
Uniqueness is done at C264 level.

1.7) Performances (typical switching time) :

OI server failure OI Client switching time

PC power off Less than 20s
Application stop Less than 20s
Ethernet disconnection Less than 60s

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 29
 4.3) Hot Redundancy for OI Server (4)

Both OI are connected on Ethernet and visible. OI Master shuts down then restarts

OI is proceeding consolidating messages before

going to Standalone.

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 30
 4.3) Hot Redundancy for OI Server (5)

One OI is not connected and reconnects One OI is not connected and reconnects

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 31
 4.3) Hot Redundancy for OI Server (6)

1.8) Fault Tolerance automation : principle of MASTER/SLAVE election

1. The 1st server that starts is MASTER

2. In case of Ethernet reconnection, the criteria for MASTER election are, from highest
priority to lowest :
a. There is a control in progress on one server
b. The quantity of connected clients
c. The first one configured in SCE

The client connection to preferred server principle and the MASTER/SLAVE election have
no correlation

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 32
 4.3) Hot Redundancy for OI Server (7)

1.9) SQL consolidation

Objective : ensure both OI servers Historian database are in line

How :
At SQL level only
Every 2 minutes (based on clock time : 8h00, 8h02, 8h04, …) :
• Compare both databases
• Fix discrepancies (if any)
• Tag every consolidated event
• Next consolidation starts from 1st event not tagged

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 33
 4.3) Hot Redundancy for OI Server (8)

2) On DS Agile, Hot redundancy configuration :

1. Preferred server of OI Client is chosen using relation “Has for HMI server”
2. Good Practice is to select at least 1 OI Client per OI Server.
3. Files “servers.dat” are automatically created by SCE during generation.
There is no need to manually install it after DB switch.

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 34
 4.3) Buffered reports

Buffered reports is used to retrieve max 1000 events stored in C264 in case of C264
disconnection from OI Server (DS Agile GTW support buffered reports)

Add relation under SCS : Has for buffered report client : <OI server>

Functionality can be tested on OI event viewer (printer is depending on its own buffer)

A Buffer overflow DP is reached in that case.

GSE
L2 - 01-SYSTEM DEVICES CONFIGURATION - Rev G - P 35
 www.alstom.com

GRID

GSE
SAM