C264 Enap C30

Application C264/EN AP/C30
MiCOM C264/C264C
APPLICATION
MiCOM C264/C264C Page 1/318
CONTENT
1. SCOPE OF THE DOCUMENT 5
2. REQUIREMENTS 6
3. COMPUTER CONFIGURATION SCOPE 7

3.1 General PACiS system configuration 7
3.2 Computer configuration in general PACiS system configuration 7
3.3 Sparing object 8
4. DEFINING COMPUTER CONFIGURATION IN SYSTEM

ARCHITECTURE 9
4.1 Setting general system configuration relevant to computers 9
4.2 Adding a computer in the system architecture 13
4.3 Setting general attributes of a computer 14
4.3.1 Configuring binary input (BI) filtering 15
4.3.2 Configuring measurement acquisition and transmission 16
4.3.3 Configuring counter acquisition 17
4.3.4 Configuring computer internal fault characteristics 17
4.3.5 Locating computer in a substation (mandatory) 17
4.3.6 Defining a computer as system master clock 18
4.3.7 Defining a redundant computer (optional) 19
4.4 Adding computer hardware components 21
4.4.1 Adding boards 21
4.4.2 Setting specific attributes to computer boards 22
4.4.3 Adding extra communication channels to CPU board 24
4.4.4 Configuring a communication channel 25
4.4.5 Configuring an AI channel 27
4.4.6 Adding a printer 28
4.5 Networking computer on the station-bus network 31
4.5.1 Connecting computer to others station-bus sub-systems 31
4.5.2 Defining addressing mapping of station-bus network 33
4.6 Networking IED on computer legacy network 36
4.6.1 Creating a legacy network of IED 36
4.6.2 Defining addressing mapping of a legacy IED 44
4.6.3 Addressing a datapoint on an IED legacy network 61
4.7 Networking SCADA on computer SCADA network 62
4.7.1 Creating a SCADA network 62
4.7.2 Defining addressing mapping of SCADA network 70
4.7.3 Addressing datapoint on SCADA legacy network 84
C264/EN AP/C30 Application
Page 2/318 MiCOM C264/C264C
4.8 Defining wave record file management 85

4.8.1 Defining management of disturbance file for IED 85
4.8.2 Defining T103 IED extra information for disturbance file 87
4.8.3 Defining management of wave record file for computer CT/VT board 89
4.9 Defining a computer klaxon 97
4.10 Setting system information for computer components 98
4.10.1 Setting general system information of a computer 99
4.10.2 Setting system information of board 103
4.10.3 Setting system information of legacy IED 105
4.10.4 Setting system information of serial printer 106
4.10.5 Setting system information of a SCADA network 107
5. DEFINING DATAPOINT 108

5.1 Creating a datapoint 108
5.1.1 Overview of binary input processing 108
5.1.2 Defining a SPS datapoint 109
5.1.3 Defining a DPS datapoint 111
5.1.4 Defining a MPS datapoint 113
5.1.5 Overview of measurement processing 115
5.1.6 Defining a TPI datapoint 120
5.1.7 Defining a Counter datapoint 123
5.1.8 Overview of control sequence processing 127
5.1.9 Defining a SPC datapoint 127
5.1.10 Defining a DPC datapoint 132
5.1.11 Defining a SetPoint datapoint 136
5.2 Linking a datapoint to a profile 142
5.2.1 Defining a SPS profile 144
5.2.2 Defining a DPS profile 148
5.2.3 Defining a MPS profile 153
5.2.4 Defining a MV profile 159
5.2.5 Defining a Counter profile 165
5.2.6 Defining a SPC profile 169
5.2.7 Defining a DPC profile 173
5.2.8 Defining a SetPoint profile 177
5.3 Defining computer local archiving of datapoint events 180
5.4 Defining computer local archiving of datapoint alarms 180
5.5 Defining computer local logging of datapoint events and alarms 180
5.6 Defining acquisition source for input datapoints 181
5.6.1 Acquiring input datapoint via input channels 181
5.6.2 Acquiring input datapoint via an IED legacy network 186
5.6.3 Acquiring input datapoint via non-PACiS IEC61850 communicant IED 187
5.6.4 Producing input datapoint 188
5.7 Defining control source for output datapoints 190

5.7.1 Controlling output datapoint via output channels 190
5.7.2 Controlling output datapoint via an IED legacy network 193
5.7.3 Controlling output datapoint via non-PACiS IEC61850 communicant IED 194
5.7.4 Producing output datapoint 195
6. DEFINING COMPUTER CONFIGURATION IN ELECTRICAL

ARCHITECTURE 200
6.1 Defining an electrical topology 200
6.1.1 Defining a Site 202
6.1.2 Defining a Substation 202
6.1.3 Defining a Voltage level 207
6.1.4 Defining a Bay 209
6.1.5 Defining Module 215
6.2 Defining a Synchrocheck function 226
6.2.1 Completing circuit-breaker definition for synchrocheck 226
6.2.2 External synchrocheck behaviour 230
6.2.3 Internal synchrocheck behaviour 230
6.2.4 Automation description of internal synchrocheck 230
6.2.5 Creating a synchrocheck function 233
6.3 Defining an Auto-recloser built-in function 239
6.3.1 Auto-recloser behaviour 239
6.3.2 Creating an auto-recloser function 239
6.4 Defining a Tap changer built-in function 246
6.4.1 Tap changer behaviour 246
6.4.2 Creating a tap changer built-in function 247
6.5 Defining an Automatic Voltage Regulation (AVR) built-in function 249
6.5.1 AVR behaviour 249
6.5.2 Creating an AVR function 249
6.6 Defining an electrical regulation by user function 262
6.6.1 Defining a FBD fast automation 262
6.6.2 Defining an ISaGRAF slow automation 268
6.6.3 Defining a group 276
6.6.4 Controlling xPC by xPS change of state 278
6.6.5 Producing a DPS from two SPS 279
6.6.6 Defining interlocking 279
6.6.7 Defining an automatic/manual dependency 281
7. DEFINING COMPUTER LOCAL HMI 282

7.1 Defining a bitmap table 282
7.2 Defining a computer workspace 285
7.2.1 Settings LHMI labels 285
7.2.2 Creating a workspace 285
7.3 Defining a computer bay mimic 286

7.3.1 Creating a computer bay mimic 286
7.3.2 Defining static part: line, bitmap, fixed text 289
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation,
transformer representation 292
7.3.4 Assigning MV to bay mimic 299
7.4 Displaying datapoint status with Led 300
8. ANNEX A: COUPLING SCE DATA MODEL AND ISAGRAF 301

8.1 ISaGRAF presentation 301
8.1.1 ISaGRAF workbench description 301
8.1.2 Directories structure of ISAGRAF 302
8.1.3 Uploaded files towards the target 303
8.2 Usage of SCE datapoints in ISaGRAF 304
8.2.1 Hierarchical relationship: Function management DPs. 304
8.2.2 Server relationship 304
8.2.3 Client relationship 305
8.2.4 Access rights summary table 305
8.2.5 Equivalence of SCE datapoint in ISaGRAF 306
8.2.6 ISaGRAF dictionary data structure 307
8.2.7 Prototype and usage of PACiS function for ISaGRAF 310
1. SCOPE OF THE DOCUMENT

The present document is a MiCOM C264/C264C section of the documentation binder. This
document is intended to present you how to configure the Computer. It is the section
Application (AP) of this Product.
2. REQUIREMENTS
First, if it is not already done, you will need to install the PACiS SCE (System Configuration
Editor), see the chapter IN (Installation) of this product.
This document presents you the objects and the attributes of a referenced database made
with the PACiS SCE. For understanding this document you first need to be familiar with
PACiS SCE and PACiS computer C264.
To add an IEC-61850 computer into an existing system you need to have the mapping of the
system (IP address, Network names of equipment…).
To generate a template, for an existent IEC-61850 computer, see the chapter Functional
Description of the SCE product.
3. COMPUTER CONFIGURATION SCOPE

3.1 General PACiS system configuration
To define a complete PACiS system, three aspects should be taken into account.
The first one is the system topology. It consists of device composition that manages the
customer’s electrical process. Generally, this part of furniture is relevant to AREVA and
corresponds to AREVA system process definition to respond customer’s needs.
The second one is the electrical topology. It consists of the customer’s electrical process
definition in term of typed electrical devices (transformer, disconnector, circuit-breaker…)
that are connected each other through busbars or lines. Generally, this part of furniture is
relevant to the customer.
The third one is the graphical topology. It consists of the mimic and their graphical animation
descriptions that appear at substation control points (operator interface) and bay control
points (computer local HMI).
When creating a new configuration using SCE, these three 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 an abbreviation of Substation Control System).
− A ‘Graphic’ object for the graphical topology.
FIGURE 1: GENERAL ARCHITECTURE OF A PACIS CONFIGURATION IN SCE

3.2 Computer configuration in general PACiS system configuration
In general PACiS system configuration, computer is concerned by the three topologies:
− System topology (Scs): computer is a direct sub-component of the Ethernet network

used for communication at station bus level.
− Electrical topology (Site): computer manages bays and relevant modules or substation
information.
− Graphical topology (Graphic): computer can own a LCD display used for animated
graphical bay panel representation and others list panels.
3.3 Sparing object

At SCE level, a spare object is an object having its spare attribute set to true. The
configurations of this object and of its spare attribute are the same as for any other object
and attribute. Any objects can be spare and particularly those concerning the computer
configuration.
Spare objects are not provided to the generator tools, respecting the following rules:
− An object O2, not spare, linked directly or not to a spare composite parent object O1,
is considered as spare.
O1 (Spare = Yes)
O2 (Spare = No)
S0387ENa
− A relation defined on an object O1, not spare, and linked to a spare object O2, is
considered as a relation without link.
O1 (Spare = No)
link
Relation O2 (Spare = Yes)
S0388ENa
4. DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE

4.1 Setting general system configuration relevant to computers
System configuration is done at SCS root. It is relevant to some general behaviour of PACiS
devices.
It concerns those specific attributes:
− Common labels used for control acknowledgement, time quality logging, alarm
management logging, computer board management.
− Alarm management characteristics (alarm processing type, audibility delays, alarm

clearing mode per gravity basis).
And those specific relations:
− Designation of the master clock computer(s) in the system. Up to two computers can
be declared as System Master Clock. A System Master Clock computer gives the time
reference to all others devices connected to the station-bus network through SNTP
(Simple Network Time Protocol). A System Master Clock computer is always located
in a substation.
− Designation of elementary action rights by default used by system datapoints of the

SCS tree.
− Designation of the substation where the system devices are located.

Some attributes of SCS objects concern all the computers defined under the station network.
Hereafter, are listed these attributes:
1. time zone: used for timestamp information.
2. behaviour on DOU failure (Control refused on faulty board / computer goes in faulty
mode).
3. computer password : local HMI password by default.
4. Default board labels and status.
5. Control acknowledgement labels used for order logging.
(1)
(2)
(3)
(4)
(unused at
computer
level)
C0161ENb
FIGURE 2: GENERAL AND LABELS ATTRIBUTES OF SCS

(5)
unused at
computer
level
C0162ENb
FIGURE 3: LABELS ATTRIBUTES OF SCS (CONT’D)

unused at
computer
level
(6)
C0163ENb
FIGURE 4: ALARM ATTRIBUTES OF SCS

6. Gi (1•i<:5) default alarm clearing mode (Manual / Automatic)
At computer level, default alarm processing type is not significant, because alarm processing
is always ‘data basis’ for computer.
Audibility features are not applicable to computer configuration.
(7)
FIGURE 5: COMPUTER ROUTING ATTRIBUTES OF SCS

7. Routing attributes:
− Gateway TCP/IP address
− Target TCP/IP address

4.2 Adding a computer in the system architecture

The addition of a computer definition is done via the “Objects entry” window at Ethernet
network level by clicking on mouse’s right button as the following:
FIGURE 6: ADDING A COMPUTER IN THE SYSTEM ARCHITECTURE

Default components of computer
When you add from the “Objects Entry” window, for example a C264 computer, you will
obtain the following sub-tree of the computer definition with the default components as
follows:
(1)
(2)
(3)
(4)
FIGURE 7: DEFAULT COMPONENTS OF THE COMPUTER

1. Binder ‘Hardware’, that groups all defined boards and printers of the computer.
2. Binder ‘System infos’, that groups all general system datapoints of the computer.
3. ‘PLC’ object for Programming Logic Chart that corresponds to ISAGRAF and PSL
project directory.
4. ‘IEC Mapping’ object, that describes the station-bus network addressing mapping of
datapoints managed by the computer.
4.3 Setting general attributes of a computer

When adding a computer on the Ethernet network, some of its attributes must be set and
verified. Hereafter are listed these attributes.
(1)
(2)
(3)
(4)
(5)
FIGURE 8: GENERAL ATTRIBUTES OF A COMPUTER

1. short name and long name: used for logging, alarms, …
2. rack model (80 TE / 40 TE): there exist two models of computers: C264 and C264C.
The C264 is a large size computer (80TE) and C264C is the compact one (40TE). The
height of both computers is 4U.
3. date format: this attribute defines the date format used in the computer HMI (LCD).
4. synchronisation source (None / IRIG-B): indicates if the computer is synchronized
through IRIG-B. The relation at SCS level “has for master clock” defines which device
is the master clock in the system. A master clock computer is necessary synchronized
through IRIG-B.
5. TCP/IP address and network name of the computer.
Configuration rules and checks
• The "TCP/IP address" value of a device must be unique among all the devices per
Ethernet Network (except for OI server and OI client).
• The "network name" value of a device must be unique among all the devices per
Ethernet Network (except for OI server and OI client).
4.3.1 Configuring binary input (BI) filtering

There exist two types of input signal handling:
• Debouncing: the start transition is signalled with the correct time, the following
changes within the debounce time are ignored. The range of the debounce time is
from 0 to 20 ms (with a 1 ms step). The event is time tagged at the instant of the first
transition.
• Filtering: the transition is only signalled if the signal is stable for minimum as long as
the filtering time. The range of the filtering time is from 0 to 20 ms (with a 1 ms step).
The filtering is allowed only if the debouncing is applied (i.e. the filtering cannot be
applied if there is no debouncing before). The event is time tagged at the instant of the
first transition.
Filtering time
Debouncing
time
t0 t1 t2
C0127ENa
FIGURE 9: DEBOUNCING AND FILTERING

A value of 0 means that no filter is applied: a change of state is validated as soon as it is
detected.
Three couples of delays (debouncing/filtering) are defined:
• one for all Digital Inputs which will be used as Binary Inputs.
• one for all Digital Inputs which will be used as Digital Measurements.
• one for all Digital Inputs which will be used as counters.
(1)
(2)
(3)
FIGURE 10: SETTING BI ACQUISITION ATTRIBUTES

1. debouncing delay (range [0, 20 ms], step 1 ms).
2. filtering delay (range [0,.20 ms], step 1 ms.
3. Toggling attributes are defined as the following:

A digital input (DI) is said to be toggling if its state has changed more than N times in a
given period of time T1.
A toggling DI returns in the normal state if its state has not changed within another
period of time T2.
N (toggling transition number), T1 (toggling delay) and T2 (toggling end delay) are
parameters determined during the configuration step on a per computer basis.
• If the attribute "debouncing delay" is set to 0, then the attribute "filtering delay" must
be set to 0.
4.3.2 Configuring measurement acquisition and transmission
(1)
(2)
(3)
(4)
FIGURE 11: MEASUREMENTS VALUES ATTRIBUTES FOR A COMPUTER

1. Debouncing delay and filtering delay: used for digital measurements.
2. Analogue measurements acquired on AIU board: acquisition samples ranges for long
scanning (range [500 ms, 10000 ms], step 500 ms) and short scanning (range [100
ms, 1000 ms], step 100 ms). For each channel of AIU board, short or long scan period
should be chosen (refer to section 4.4.5 Configuring an AI channel).
3. Acquisition on TMU board with CTVT fundamental 50 or 60 Hz (number of harmonics
is fixed to 16).
4. Short transmission period on station bus (range[0,.60 s],step 100 ms) and long
transmission period given by a multiple of the short period ([0..600]x short
transmission period).
be set to 0.
4.3.3 Configuring counter acquisition
(1)
FIGURE 12: COUNTER ACQUISITION ATTRIBUTES OF A COMPUTER

1. debouncing delay and filtering delay: used for digital counters (see 4.3.1 for details)
be set to 0.
4.3.4 Configuring computer internal fault characteristics
(1)
FIGURE 13: MISCELLANEAOUS ATTRIBUTES OF A COMPUTER

1. Number of software faults allowed in a given period else the computer remains in
HALT mode. Computer reboots automatically as long as it does not reach the ‘fault
max number’ in the ‘fault detection time’ period. When this critera is reached computer
remains in HALT mode.
4.3.5 Locating computer in a substation (mandatory)
As said in section 4.1 (Setting general system configuration relevant to computers), each
system device has to be located in a specific substation. This is done by defining the
mandatory relation (1) “is located in:“ for each system device, especially computers.
(1)
FIGURE 14: LOCATING COMPUTER IN A SUBSTATION

4.3.6 Defining a computer as system master clock

As said in section 4.1 (Setting general system configuration relevant to computers), up to two
computers can be master clock for the system. This is done by defining the mandatory
relation (1) “has for master clock:“ at SCS level. By double clicking this relation the
Relation link editor dialog box opens and lists the computers (2) which can be declared as
master clock (by clicking it and then by clicking the Ok button). In our example computer
C264_A has been selected as System master clock (3). If a second master clock is needed
a second "has for master clock:" relation (4), available in the object entry window
associated to the Scs level, has to be added and defined by the same way as the first one. In
this case the Relation Link editor lists only the three remaining computers. When two
computers have been declared as master clock the "has for master clock:" relation is no
more available in the object entry window associated to the Scs level.
(2)
(1)
(3)
(4)
FIGURE 15: DEFINING A (TWO) COMPUTER(S) AS SYSTEM MASTER CLOCK

4.3.7 Defining a redundant computer (optional)

To define a redundant computer:
• Create the main computer, considered as master one.
• Via the contextual menu of the computer, run “Create backup” (1).
Then:
• An extra computer (considered as slave one) is automatically created with an implicit

relation of backup between the two computers.
• Extra relation ‘has for UCA2/IEC server’ is automatically created for the main
computer.
• Once the backup computer has been created, its attributes and constitution are locked
for updating and follow the main computer ones. The only exceptions are its short
name and long name and network identification (IP address and network name) that
must be correctly updated. When an object is added to ( resp. removed from ) the
main computer the same object is added to (resp. removed from) the backup
computer but attributes cannot be modified..
(1)
FIGURE 16: DEFINING A REDUNDANT COMPUTER (CREATION ACTION)

Automatic creation of
"has for UCA2/IEC
server" relation for the
main computer
Slave computer created

after manual updating of
its short and long names,
and IP characterisitics
Automatic creation of
"backup" relation between
the two computers
C0166ENc
FIGURE 17: DEFINING A REDUNDANT COMPUTER (ONCE CREATED)

4.4 Adding computer hardware components

4.4.1 Adding boards
PACiS computers are composed of boards, responding to specific functions:
• DIU200-210 - Digital input boards with 16 digital input channels:

- digital and counter acquisition
- digital measurement acquisition
• AIU201 - Analogue input boards with 4 analogue input channels:

- analogue measurement acquisition
• AIU210/AIU211 - Analogue input boards with 8 analogue input channels:

- analogue measurement acquisition
• TMU200/TMU210 - CT and VT input boards with 4 CT and 4 VT input channels:

- ct/vt sampling acquisition,
- MV computations based on acquired samples
• DOU200 - Digital output boards with 10 digital output channels:

- execution of single or dual, transient or permanent commands
- setting of digital setpoints
• CCU200 - Mixed digital 8 input and 4 output boards with digital input and output
channels (take good care the DO 4,5,6,7 are defined but not used):
- Circuit breaker Control Unit
• CPU260, BIU241 - CPU and communication boards with communication channels (or
communication ports)
• GHU200 - Graphical panel boards with led channels

Computer hardware definition is done in SCE by adding typed boards below computer
object. Mandatory boards (CPU260, GHU200, BIU241) are automatically created at
computer’s creation. Implicit typed channel creations are done at board’s creation.
Linking datapoint to channels does datapoint wiring.
The addition of a board definition is done via the “Objects entry” window by clicking on
mouse’s right button as the following:
FIGURE 18: ADDING A BOARD TO THE COMPUTER


Slots and boards in a C264 computer
A B C D E F G H I J K L M N O P Q
BIU CPU
• Slots from C to P may contain a board of the following types: AIU201, AIU210,
DOU200, DIU20x, DIU210 or CCU20x
• Slot Q may contain one TMU200 board or one board of the above types.
• If a TMU200 is present, then the maximum count of boards must be ≤ 14; else the
maximum count of boards must be ≤ 15.
• If present the Ethernet boards (SWU20x, SWR20x, SWD20x) are to be installed in

slots C or D.
Slots and boards in a C264C computer
A B C D E F G H
BIU CPU
• Slots from C to F may contain a board of the following types: AIU201, AIU210,
DOU200, DIU20x or CCU20x
• Slots G and H may contain one TMU200 board or two boards of the above types.
• If a TMU200 is present, then the maximum count of boards must be ≤ 4; else the
maximum count of boards must be ≤ 6.
• If present the Ethernet boards (SWU20x, SWR20x, SWD20x) are to be installed in

slots C or D.
4.4.2 Setting specific attributes to computer boards
4.4.2.1 Setting common attributes to computer board
For each board of the computer the short name attribute (1) may be updated for correct
logging and alarm discrimination concerning board status datapoint.
For boards AIU2xx, CCU200, DIU2x0, DOU200 the physical board number attribute (2)
must be updated.
For boards CPU260, BIU241, GHU200, TMU2x0 this attribute is forced to 0 by the SCE and
is not displayed in the attributes window
(1)
(2)
FIGURE 19: GENERAL ATTRIBUTES OF A BOARD

• Per board type (AIU201, AIU210, DOU200, DIU20x, CCU20x), the physical board
number attribute values must begin from 0, be unique and contiguous.
4.4.2.2 Setting specific features of a GHU200 board

For GHU board, the specific attribute ‘HMI type’ (1) has to be set to:
• ‘Simple’ if GHU board without LCD is used.
• ‘Complete’ if GHU board with LCD is used.
(1)
FIGURE 20: GENERAL ATTRIBUTES OF A GHU200 BOARD

NOTE: The value ‘Old’ for ‘HMI type’ must not be used. It is still proposed for
maintenance reason.
For complete HMI, the extra relation ‘has for workspace’ (1) must be
filled at board level. For details about computer workspace, refer to
section 7.2 Defining a computer workspace.
(1)
FIGURE 21: DEFINING WORKSPACE FOR COMPLETE GHU200 BOARD

For computer LED configuration, refer to section 7.4 Displaying datapoint status with Led.
• If the value of the "HMI type" attribute is "Simple", then "Led#4" must not be used (no
relation link from "Led#4" to a datapoint).
• If the value of the "HMI type" attribute is different from "Complete", then the relation
"has for workspace" must not be linked.
4.4.2.3 Setting specific attributes of a TMU200 board

For TMU200 board, the following attributes have to be set for correct CT/VT computation of
extra measurements:
1. electrical network topology (Star / Delta).
2. reference phase (Phase A / Phase B / Phase C).
3. reference phase side (Phase A, B, C wired line side / Phase A, B, C wired busbar
side).
4. nominal current and nominal voltage.
Extra attributes are reserved for future use.
(1)
(2)
(3)
(4)
FIGURE 22 TMU200 BOARD SPECIFIC ATTRIBUTES

If reference phase signal is absent, values transmitted by TMU board are set to invalid.
4.4.3 Adding extra communication channels to CPU board
At CPU260 board level, the frontal RS232 port is mandatory and automatically created at
board creation. Two extra communication channels can be added from SCE objects entry
window.
FIGURE 23: ADDING COMMUNICATION CHANNELS

4.4.4 Configuring a communication channel

A communication channel is a physical port available on CPU or the BIU board at their
creation or manually added as option.
A communication channel can be used exclusively for:
1. Communication with an IED legacy network.
2. Communication with a SCADA network.
3. Communication with a serial printer.
(1)
(2)
mandatory frontal port
(3)
C0167ENb
FIGURE 24: USAGE OF COMMUNICATION CHANNEL

Once used by a communication link, the physical port has to be set relatively to the
communication link characteristics:
1. RS type (RS232 / RS485).
2. baud rate (bits/s) (50 / 100 / 200 / 300 / 600 / 1200 / 2400 / 4800 / 9600 / 19200 /
38400 / 56000 / 64000)
Note: this attribute must be set to the same value for ports 3 and 4 of the CPU260.
3. parity (No parity / Odd parity / Even parity)
4. number of stop bits (1 bit / 2 bits)
5. nb. bits per char (7 bits / 8 bits)
6. Tx carrier management (Switched / Constant / Soft):
− Switched: when the computer has to send a frame it sets the RTS line and
waits for the CTS line to be set by the receiver. It then waits during a time
defined by attribute (9) before starting the transmission of the frame. At the end
of the transmission the computer waits during a time defined by attribute (10)
before resetting the RTS line
− Constant: the RTS line is always set by the computer. When it has to send a
frame it waits for the CTS line to be set by the receiver to start the transmission.
− Soft: the RTS and CTS line are not managed by the computer.
7. CTS wired (No / Yes): this attribute must be set to YES if the TX carrier
management attribute is set to Switched or to Constant
8. CD wired (No / Yes): in order for the DCD line to be managed by the computer this
attribute must be set to YES if the TX carrier management parameter is set to
Switched.
9. pre TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore significant
only if attribute (6) is set to Switched.
10. post TX time (range [0, 1 s], step 1 ms): this attribute is visible and therefore
significant only if attribute (6) is set to Switched.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10
)
FIGURE 25: GENERAL AND TRANSMISSION ATTRIBUTES OF A COMMUNICATION

CHANNEL
4.4.5 Configuring an AI channel

An AI channel is an analogue input available on AIU201 and AIU210 boards at their creation.
AI channels are used for analogue measurement acquisition.
implicit AI#0 to
AI#3 channels
creation on
AIU200 board
C0168ENb
FIGURE 26: USAGE OF ANALOGUE CHANNELS

Once used by a MV, the AI has to be set relatively to the acquisition characteristics:
1. sensor range (-20 mA …+20 mA / -10 mA …+10 mA / -5 mA …+5 mA / -1 mA …+1
mA / 0 mA …+1 mA / 0 mA …+5 mA / 0 mA …+10 mA / 0 mA …+20 mA / 4 mA …+20
mA / -10 V … +10 V / -5 V … +5 V / -2.5 V … +2.5 V / -1.25 V … +1.25 V)
2. acquisition period (short period / long period): refer to section 4.3.2 Configuring
measurement acquisition and transmission.
(1)
(2)
FIGURE 27: CONFIGURING AN AI CHANNEL

4.4.6 Adding a printer

SCE data modelling describes printers used in PACiS system for ‘sequence of events’ and
log book functions at operator interface level and computer level.
A printer at computer level must be a serial one connected to a communication channel of
the computer.
To create a computer printer:
• Add a serial printer from object entry available at computer level.
FIGURE 28: ADDING A SERIAL PRINTER
• Update its ‘has for communication port’ relation (1) and its attribute ‘printer control’ (2).
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 29: UPDATING THE COMMUNICATION PORT RELATION FOR A SERIAL PRINTER
To control the way logging is managed and formatted on a serial printer, updating printer
attributes is necessary:
3. page size (range [20 lines, 65535 lines ], step 1 line).
4. buffer size (range [100 events, 3000 events ], step 100 events)
5. number of events to suppress when buffer is saturated (.range [30 events, 1000
events ], step 10 events)
6. Rank of the different columns used for printing formats.
• The following constraint must be respected : buffer size > nb of events to suppress
when saturated
Hereafter an extract of logging that illustrates the different columns used for printing formats:
origine
time stamp object name
chronology object message
C0169ENa
FIGURE 30: THE DIFFERENT COLUMNS USED FOR PRINTING FORMATS

• The value of each "… column rank" attribute must be unique.

4.5 Networking computer on the station-bus network

Computer connection to the station-bus is implicitly done by adding the computer
hierarchically to the Ethernet network (see section 4.2 Adding a computer in the system
architecture) and by setting the IP characteristic of the computer (see 4.3 Setting general
attributes of a computer).
4.5.1 Connecting computer to others station-bus sub-systems
To transmit information between PACiS sub-systems, IEC-61850 protocol is used.
The data modelling of IEC-61850 protocol is based on client-server architecture. Each IEC-
61850 communicant PACiS sub-system (OI server, PACiS computer, and telecontrol
gateway) owns an IEC-61850 mapping of data which it is server of. A PACiS sub-system is
server of a datapoint if it manages it, that is to say it produces its real-time value (in case of
input datapoint such as status, measurement, counter) or executes its real-time controls (in
case of output datapoint such as binary controls and setpoints).
To connect a computer (A) to a specific IEC-61850 communicant sub-system (B) on the
station-bus, an extra relation ‘has for UCA2/IEC server’ must be created for (A) and point to
(B). That means computer (A) is client of sub-system (B) and can access to data managed
by the sub-system (B), i.e. read relevant real-time values from (B) and send real-time
controls to (B).
FIGURE 31: CONNECTING COMPUTER TO OTHERS STATION-BUS SUB-SYSTEMS

Computer A has
for IEC- 61850
server computer B
Computer B has
for IEC- 61850
client computer A
(1)
C0170ENb
FIGURE 32: COMPUTER (A) AS UCA2/IEC CLIENT OF COMPUTER (B)

When adding the ‘has for UCA2/IEC server’ relation to computer (A), a specific attribute of
the relation, modelling/goose usage (1), can be set to precise the way data are transmitted
from server (B) to computer (A). There are three possibilities:
• Data model only (or report mode only).
• Goose only.
• Data model and goose.

Basically, the Report mode is used to transmit filtered data for displaying, printing and
archiving. The Goose mode is used to transmit data as soon as possible after their
acquisition and as quickly as possible, for automation purpose.
Goose transmission must be used if computer (A) uses BIs served by computer (B), for
ISaGRAF, FBD or interlock computation (refer to section 6.6 Defining an electrical regulation
by user function).
During a loss of communication between a client and a server, all server BIs are set to
UNKNOWN on the client.
• A client must not be linked to the same server through multiple relations "has for
UCA2/IEC server".
Report based mode

Via its IEC-61850 address, a BI (see section 5.1.1 Overview of binary input processing) can
be configured to be transmitted in Report mode. In this mode, a confirmed change of status
is spontaneously transmitted to the subscribers.
The BI information transmitted in a report is:
• the state and quality (the BI resulting state is split in state and quality on IEC-61850)
• the time stamping (in GMT time) and time quality
• the reason for change, which could be one of the below values :
− change of data (set if the state has changed, before persistence or motion filtering)
− change of quality (set if the quality has changed, before persistence or motion
filtering)
− change due to control (set if the state or quality change is due to a control)
From one server, all BI reports are not transmitted in a chronological order (it is an IEC-
61850 client feature to put, if needed, all information in a chronological order).
During a loss of communication, the events detected on the computer are not buffered.
GOOSE based mode
A BI (only SPS and DPS) can be configured to be transmitted in GOOSE mode. In this
mode, the change of status is transmitted in multicast to the configured receivers. Only the
BI unfiltered states are transmitted, the time stamping and the reason for change are not.
Due to GOOSE format, all BI resulting states given below cannot be transmitted. So, the
following mapping is applied:
BI Resulting State GOOSE value

RESET, FORCED RESET, SUBSTITUTED RESET, 01
CLOSE, FORCED CLOSE, SUBSTITUTED CLOSE
SET, FORCED SET, SUBSTITUTED SET, 10
OPEN, FORCED OPEN, SUBSTITUTED OPEN
JAMMED 00
UNDEFINED, TOGGLING, SELFCHECK FAULTY, 11
SUPPRESSED, UNKNOWN
A measurement can be configured to be transmitted in GOOSE mode as well ( refer to

section 5.2.9 of chapter C264/EN FT).
4.5.2 Defining addressing mapping of station-bus network
An IEC 61850 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, measurements, Control, Configuration), called functional
components.
A functional component groups data objects. A data object must be seen as a real-time
equivalent of a PACiS datapoint. So, when a PACiS sub-system (IEC 61850 client) needs
the real-time value of a datapoint managed by another sub-system (IEC 61850 server), this
last one transmits the information via a data object of its own IEC 61850 mapping. At SCE
data modelling level, IEC 61850 clients must precise which IEC 61850 servers it retrieves
information from (see section 4.5.1 Connecting computer to others station-bus sub-systems).
Generally, an IEC 61850 data object has a stereotype, called common class. The structures
of these ones are known by all PACiS IEC 61850 communicant sub-systems. For PACiS
sub-systems, the number and structure of common classes are fixed. They are the terminal
description of IEC 61850 PACiS data modelling.
In IEC 61850 Mapping of PACiS sub-system, there is a native logical device LD0 with fixed
and hard-coded bricks (DBID, DI (LPHD), GLOBE (LLN0), and DIAG). When creating a
PACiS computer at SCE level, an IEC 61850 mapping with LD0 and its default bricks is also
created. LD0 is a system logical device that groups all system diagnostics and controls
relevant to the computer. Datapoints addressed in the brick of LD0 are only relevant to
system topology.
Extra logical devices can be created in the IEC 61850 mapping of a computer. Generally,
there is one logical device for each bay managed by the computer, and, in each logical
device, there is one brick for each module or built-in function.
4.5.2.1 SBUS automatic addressing
“SBUS automatic addressing” function is based on the substation electrical topology and
especially on bays.
The easiest way to create application logical devices relevant to electrical bays managed by
a computer is to run “SBUS automatic addressing function” for the computer. The contextual
menu (mouse right click) of the computer (1) can launch this function.
(1)
FIGURE 33: SBUS AUTOMATIC ADDRESSING

Notes: Only no-Spared datapoints are taken into account in automatic
addressing. If a datapoint is unspared then an automatic addressing
treatment must be done again
• Some datapoints are out of scope of automatic addressing. Theses datapoints are
identified by their data model mnemonic and their short name. They are listed in the
following table
Excluded datapoints
Parent object
mnemonic name
Module Circuit breaker SynCheck_Close_DPC Sync CB close
SynCheck_Close_SPC Sync CB close

Select_SPC Selection SPC
Switch_SPC_PhA Switch phA SPC
Switch_SPC_PhB Switch phB SPC
Switch_SPC_PhC Switch phC SPC
SwitchPos_PhA (DPS) Switch PhA pos.
SwitchPos_PhB (DPS) Switch PhB pos.
SwitchPos_PhC (DPS) Switch PhC pos.
SwitchPos_SPS_PhA Switch PhA pos. SPS
SwitchPos_SPS_PhB Switch PhB pos. SPS
SwitchPos_SPS_PhC Switch PhB pos. SPS
SwitchPos (DPS) Switchgear pos.
SwitchPos_SPS Switchgear pos.
PhaseNotTogether_SPS Ph not together
External automatic CS_CtrlOnOff_DPC on/off ctrl DPC
synchrocheck built-in function
CS_CtrlOnOff_SPC on/off ctrl SPC
Relay [XX] function XX_thresholdY_trip XX tY trip
examples:
With :XX = function number
46 t1 trip
Y = threshold number 67 t3 trip
XX_thresholdY_inst_dir_rev XX tY in di rev
examples:
With :XX = function number
67 t1 in dir rev
Y = threshold number 67 t3 in dir rev
XX_thresholdY_interlock XX tY interlock
With :XX = function number example:
67 t1 interlock
Y = threshold number
Relay [automatism] start_disturbance start dist ctrl
Relay [49] function 49_trip_th_overload 49 trip th over.
• Some measurements computed by a TMU 210 are out of scope of automatic

addressing if the measure type ( measure type attribute of the relation "is computed
by" linked to the related MV) is one of the followings:
− mod Vo (ADC)
− mod I1 (ADC)
− mod I2 (ADC)
− mod V1 (ADC)
− mod V2 (ADC)
− thermal status
Note: For the datapoints which are excluded of the automatic addressing it
is possible to add the relation "has for IEC address and then define it.
4.6 Networking IED on computer legacy network
4.6.1 Creating a legacy network of IED
Generally, specific devices called relays or IEDs insure protection of electrical modules and
bays. IED connection to PACiS system is commonly done via IED legacy networks managed
by PACiS computer as master.
At SCE data modelling level, up to four IED legacy networks (relevant to a specific protocol)
can be located under a PACiS computer C264 or C264C. Each IED legacy network has to
be linked to communication port embedded in computer boards. Up to sixteen IED can be
added under a legacy network.
4.6.1.1 Adding a legacy network

To create a legacy network on a computer:
• Add a legacy network relevant to a specific protocol from object entry available at
computer level (1),
• Update the legacy network attributes relevant to its protocol characteristics,
• Update its ‘has for main comm. port’ relation and the communication port
characteristics (see section 4.4.4 Configuring a communication channel),
(1)
FIGURE 34: ADDING A LEGACY NETWORK

4.6.1.2 Setting general attributes of a legacy network
Whatever the kind of legacy network, its short name and long name attributes (1) must be
updated for correct logging and alarm discrimination concerning IED status datapoint
connected to the legacy network.
(1)
FIGURE 35: GENERAL ATTRIBUTES OF A LEGACY NETWORK

4.6.1.3 Setting acquisitions attributes of a T103 legacy network

When adding a T103 legacy network, the following attributes, available for all its IEDs, must
be updated:
1. number of retries (range [1, 10]): number of tries of the same frame without IED
response, the computer will send it before setting it disconnected.
2. acknowledgement time-out (range [100 ms, 30 s], step 100 ms): maximum delay an
IED answer is awaited when the computer asks it a information.
3. synchronisation cycle (range [10 s, 655350 s]): time synchronisation period of the
IED by the computer.
4. downgraded cycle (range [1 s, 10 s], step 100 ms): if an IED is set disconnected by
the computer, it tries to re-connect it regularly at this cycle.
5. inter frame duration (range [1 , 50 ], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames.
(1)
(2)
(3)
(4)
(5)
FIGURE 36: SETTING ACQUISITION ATTRIBUTES OF A T103 LEGACY NETWORK

4.6.1.4 Setting acquisition attributes of a T101 legacy network
When adding a T101 legacy network, the following attributes, available for all its IEDs, must
be updated:
1. number of retries (range [1, 10], step 1): corresponds to the number of tries of the
same frame without IED response, the computer will send it before setting it
disconnected.
2. station address size (range [1 byte, 2 bytes]): size of the IED addresses
3. ASDU address size (range [1 byte, 2 bytes]): size of the ASDU.
4. info address size (range [1 byte, 3 bytes]): size of the information addresses.
5. transmission cause size (range [1 byte, 2 bytes]): size of the transmission cause.
6. frame length (range [64 bytes, 255 bytes]): if an IED cannot manage frame whose
length is superior to 255, the frame length attribute must be set to the available length
for the IED.
IED answer is awaited when the computer asks it an information.
8. synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation
period of the IED by the computer.
10. Type of link (Balanced / Unbalanced): if unbalanced link, only master (here computer)
asks IED. If balanced link, IED can also ask the master (here computer) without
sollicitation.
11. test frame time-out (range [1 s, 255 s], step 1 s): in case of ‘balanced link’ (cf.
attribute (10)), a life message (test frame) is sent periodically between computer and
IED. This attribute corresponds to maximum delay to receive this life message, to
computer’s point of view. If no reception within this delay, IED is set disconnected.
12. inter frame duration (range [1, 50 ], step 1): this attribute represents the minimum
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
FIGURE 37: SETTING ACQUISITION ATTRIBUTES OF A T101 LEGACY NETWORK

4.6.1.5 Setting acquisition attributes of a Modbus legacy network
When adding a Modbus legacy network, the following attributes, available for all its IEDs,
must be updated:
disconnected.
IED answer is awaited when the computer asks it an information.
3. synchronisation (none / AREVA / SEPAM) : refer to section 4.3.5.2 of chapter
C264/EN CT for details and to the reference document of the connected IED).
period of the IED by the computer. Only significant if attribute (3) is set to ‘AREVA’ or
to SEPAM.
5. downgraded cycle (range [1s, 10 s], step 100 ms): if an IED is set disconnected by
6. inter frame duration (range [1, 50], step 1): this attribute represents the minimum
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 38: SETTING ‘ACQUISITION’ ATTRIBUTES OF A MODBUS LEGACY NETWORK

4.6.1.6 Setting acquisition attributes of a DNP3 legacy network

When adding a DNP3 legacy network, the following attributes, available for all its IEDs, must
be updated:
1. master address : computer address on the DNP3 legacy network.
IED answer is awaited when the computer asks it a information.
disconnected.
4. application time-out (range [0 s, 255 s], step 1 s): time-out used by the computer, at
application layer of DNP3 protocol.
5. class 0 polling period (range [0 s, 3600 s], step 1 s): emission period of the general
request message. If this attribute equals zero, no general request message is sent.
period of the IED by the computer.
8. inter frame duration (range [1, 50], step 1): this attribute represents the minimum
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 39: SETTING ACQUISITION ATTRIBUTES OF A DNP3 LEGACY NETWORK

4.6.1.7 Adding an IED to a legacy network

To create an IED on a legacy network:
• Add an IED from object entry available at ‘Legacy networks’ level (1).
• Update the IED attributes relevant to its protocol characteristics.
• For DNP3, T103, or Mobdus IED, update the ‘has for acquisition profile’ relation with a
previously created IED acquisition type.
(1)
FIGURE 40: ADDING AN IED TO A LEGACY NETWORK
updated relation
netween IED and
IED acquisition type
C0176ENb
FIGURE 41: LINKING IED ACQUISITION PROFILE TO AN IED

4.6.1.8 Setting attributes of a legacy IED
Whatever the kind of IED, the following attributes must be updated:
1. short name and long name: used for correct logging and alarm discrimination
concerning IED status datapoint.
2. network address of the IED on the legacy network (4 byte-address).
3. automatic disturbance (No / Yes): unavailable for DNP3 IED.
4. localisation for disturbance file: non-significant for DNP3 IED, used for basic file
name upload by SMT on OWS hard disk: <localisation>_N#.
(1)
(2)
(3)
(4)
FIGURE 42: SETTING GENERAL ATTRIBUTES OF A LEGACY IED

• For each IED, its "network address" and "short name" attributes value must be unique,
per Legacy Network.
4.6.1.9 Adding an IED acquisition type to a legacy network
Common acquisition and communication characteristics are shared by IEDs. These ones are
grouped in an object called ‘IED acquisition type’, similar to acquisition profile. It is available
for DNP3, T103 and Modbus protocols.
To create an IED acquisition type on a legacy network:
• Add an IED acquisition from object entry available at legacy network level (1).
• Update the IED acquisition type attributes relevant to its protocol characteristics.
(1)
FIGURE 43: ADDING AN IED ACQUISITION TYPE TO A LEGACY NETWORK

(E.G. FOR DNP3)
• For each computer and all its Legacy Networks, the maximum count of "xxx acq type"
components is 10.
4.6.1.10 Setting attributes of a T103 acquisition type

When adding a T103 acquisition type, the following attributes, available for all its linked IEDs,
must be updated:
1. IED type (T103 standard IED / Px3x Serie / Px2x Serie / REG-D / Tapcon 240)
2. function type (range [0, 255]: function type number used for acquisition: see IED
documentation to set correctly this attribute
3. general interrogation period (range [0, 24 h], step 1 s): cycle used to fetch regularly
statuses and measurements from IED and to avoid loss of event information
4. MV reduction coefficient (1.2 / 2.4 ): used for scaling (ASDU 3 usage): refer to T103
documentation for details about this scaling
5. Four sets of three nominal values (voltage, current and frequency) used for scaling.
Refer to International Standard IEC 60870-5-103 for details about this scaling.
(1)
(2)
(3)
(4)
(5)
FIGURE 44: SETTING ATTRIBUTES OF A T103 ACQUISITION TYPE

4.6.1.11 Setting attributes of a MODBUS acquisition type

When adding a Modbus acquisition type, the following attributes, available for all its linked
IEDs, must be updated:
1. IED type (Modicon / M300 / MICOM S20 / M230 / WAGO): by default use ‘Modicon’.
2. MODBUS function (1 / 2 / 3 / 4 / 7 / 8 ): function number used for polling frame: To
test the IED connection, this attribute gives which Modbus function is used. For
AREVA IED product, the function 7 is generally used.
3. mapping address (range [0, 232-1]): associated to attribute (2), it gives which start
address is used to test the IED connection
− if MODBUS function is set to 1 or 2 this attributes defines a bit address
− if MODBUS function is set to 3 or 4 this attributes defines a word address
− if MODBUS function is set to 5 this attributes is not significant
− if MODBUS function is set to 8 this attributes defines a sub-code
− if MODBUS function is set to 7 this attributes is not significant

4. size to read (range [0, 2048]: associated to attribute (3), it gives which length is used
to test the IED connection.
− if MODBUS function is set to 1 or 2 this attributes defines a number of bits
− if MODBUS function is set to 3 or 4 this attributes defines a number of words
− if MODBUS function is set to 7 or 8 this attributes is not significant

5. data frame length (range [2 bytes, 256 bytes]): if an IED cannot manage frames
longer than 256 bytes, this attribute must be set to the available length for the IED.
(1)
(2)
(3)
(4)
(5)
FIGURE 45: SETTING ATTRIBUTES OF A MODBUS ACQUISITION TYPE

4.6.1.12 Setting attributes of a DNP3 acquisition type

When adding a DNP3 acquisition type, some attributes available for all its linked IEDs must
be updated:
1. global class usage (No / Yes): used for addressing. Not yet implemented. Always
considered as ‘yes’ at computer level.
2. synchronisation type (Network synchronisation / External synchronisation): in case
of network’ synchronisation, computer synchronises the time of the IED, otherwise the
synchronisation is assumed independently by an external equipment directly
connected to the IED. Not yet implemented. Always considered as ‘Network
synchronisation’ at computer level.
3. CROB parameters (Usage of 'code' field / Usage of 'Trip/Close' field / Usage of 'code'
and 'trip/close' fields):
(1)
(2)
FIGURE 46: SETTING ATTRIBUTES OF A DNP3 ACQUISITION TYPE

4.6.2 Defining addressing mapping of a legacy IED
To transmit information between IED and PACiS system, an IED legacy network connected
to a PACiS computer is used.
To receive or send information between legacy IED and PACiS system, each concerned
data must have a specific address on the legacy network relatively to its protocol. General
modelling of legacy network address mapping can be done. At SCE level, an IED of a legacy
network owns an “IED mapping” object, that is split in categories of mapping on a per
datapoint kind basis. In each category of mapping, elementary IED addresses can be
created. For details about datapoint, refer to section 5 DEFINING DATAPOINT. This
mapping is implicitly created during IED adding at legacy network level. Addressing a MPS
datapoint on legacy IED is not available.
created DO
C0355ENa
FIGURE 47: STRUCTURE OF THE ADDRESSING MAPPING OF LEGACY IED

(E.G. FOR T101 IED)
For details about addressing mapping of a given IED on a specific protocol, refer to relay
documentation.
In the IED Mapping, the address identification of each "xxx addr. on IED" must be unique.
• DNP3: address identification is given by the attribute "address" of the "xxx addr. on
IED".
• MODBUS:address identification is made of the following combinations of its attribute

values:
- { "mapping address" , "function" , "bit number" }
- { "mapping address" , "function" }
• T103:address identification is made of the following combinations of its attribute

values:
- { "ASDU number" , "function type" , "information number" , "common address of
ASDU" , "index in the ASDU" }
- { "ASDU number" , "function type" , "information number" , "common address of
ASDU" }
- { "ASDU number" , "function type" , "information number" }
• T101:address identification is made of the following combinations of its attribute

values:
- { "information object address" , "common address of ASDU" }
- { "information object address" }
4.6.2.1 Defining an IED address for a SPS datapoint

The addition of an IED address for a SPS datapoint is done via the “Objects entry” window at
IED SPS mapping level by clicking on mouse’s right button.
FIGURE 48: ADDING AN IED SPS ADDRESS (E.G. FOR T101 IED)
Once added, IED SPS address attributes must be set at SCE level:
1. short name: used for internal SCE identification.
For Modbus protocol:
2. mapping address (range [0, 65535],step 1): word address or bit address depending
on the bit number attribute.
3. bit number (range [0, 65535],step 1): used only if word read or status read is used
(see function attribute).
4. fonction (range [0, 65535],step 1): number of the Modbus function used to read the
SPS:
- 1, 2 : read bit,
- 3, 4 : read word,
- 7 : read status
For T101 protocol:
5. information object address (range [0, 16777215],step 1).
6. common address of ASDU (range [-1, 65535],step 1): by default (–1) is equal to IED
address (see section 4.6.1.8 Setting attributes of a legacy IED).
For T103 protocol:
7. ASDU number (range [0, 65535],step 1):
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
8. fonction type (range [0, 65535],step 1).
9. information number (range [0, 65535],step 1).
address (see section 4.6.1.8 Setting attributes of a legacy IED.).
For DNP3 protocol:

11. address (range [0, 65535],step 1).
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103 (7)
(8)
(9)
(10
)
DNP3
(11
)
FIGURE 49: DEFINING AN IED ADDRESS FOR A SPS DATAPOINT

4.6.2.2 Defining an IED address for a DPS datapoint

The addition of an IED address for a DPS datapoint is done via the “Objects entry” window at
IED DPS mapping level by clicking on mouse’s right button.
FIGURE 50: ADDING AN IED DPS ADDRESS (E.G. FOR T101 IED)
Once added, IED DPS address attributes must be set at SCE level:
1. short name of the address: used for internal SCE identification.
2. mapping address (range [0, 65535],step 1): Word address or Bit address depending
on bit number attribute.
3. bit number (range [0, 65535],step 1): Used only if Word read or status read is used
(see function attribute).
4. fonction (range [0, 65535],step 1): Modbus function to use to read the DPS:
- 1, 2 : read bit,
- 3, 4 : read word,
- 7 : read status
For T101 protocol:
For T103 protocol:
- 1, 2 (for all IED)
- 65,66,67,68 (Only for Px3x)
8. fonction type (range [0, 65535],step 1): refer to relay documentation.
9. information number (range [0, 65535],step 1): refer to relay documentation.
For DNP3 protocol:
For all protocol types, DPS acquisition on IED can also be done via two different addresses.
In that case, two ‘DPS address on IED’ must be created for this DPS. For each of them, the
attribute contact identifier (12) must be set to ‘Open’ or ‘Closed’, to precise which state of
the DPS is concerned by the IED address. If DPS status is given by only one IED address,
set ‘contact identifier’ value to ‘unused’.
Modbus
(1)
(2)
(3)
(4)
(12
)
T101
(5)
(6)
(12
)
T103
(7)
(8)
(9)
(10
(12 )
)
DNP3
(11
)
(12
)
FIGURE 51: DEFINING AN IED ADDRESS FOR A DPS DATAPOINT

4.6.2.3 Defining an IED address for a MV datapoint
The addition of an IED address for a MV datapoint is done via the “Objects entry” window at
IED MV mapping level by clicking on mouse’s right button.
Once added, IED MV address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): Word address
3. fonction (range [0, 65535],step 1): Modbus function to use to read the MV:
- 3, 4 : read word,
- 7 : read status
4. data format: see following paragraph (Measurement formats that can be used with
the MODBUS protocol).
For T101 protocol:

For T103 protocol:
- 3, 4, 9 (for all IED)
- 21 (for acquisition of measurement with "generic Services"
- 77 (Only for Px2x)
- 73 (Only for Px3x)
8. fonction type (range [0, 65535],step 1).
9. information number (range [0, 65535],step 1).
10. index in the ASDU (range [0, 65535],step 1).
address.
12. unit of the MEAS (Voltage / Current / Power / Frequency / No Unit).
13. substituted if unknown (No / Yes)
For this protocol it is possible to perform acquisition of measurements only using the Generic
Services of IEC 60870-5-103 protocol by polling. This can be done by setting some
parameters as follows:
− ASDU number: 21
− function type 254
− information number: 244
− index in the ASDU: Generic Identification Number given by the mapping of the IED
For DNP3 protocol:
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103
(7)
(8)
(9)
(10
(11 )
) (12
(13 )
)
DNP3
(14
)
FIGURE 52: DEFINING AN IED ADDRESS FOR A MV DATAPOINT

Measurement formats that can be used with the MODBUS protocol

Because the Modbus norm only describes the transmission of 16 bits values (transmission of
the high order byte first), new formats must be defined to describe the different ways to
transmit 32 bits values (what ever their type: signed or unsigned integers, real values) or 8
bits values.
So the format to apply to an analog input depends on the way it is transmitted and
consequently on the representation of the value in the memory of the device.
In the following table, the “transmission order” column (4) indicates the way a value is
transmitted, i.e. the order in which the bytes of the value are transmitted. The bytes are
numbered from 1 (lowest order byte) to 4 (highest order byte).
Transmission
Format Description
order
INT8_LB Transmission of an 8 bit signed integer in a 16 bit value. /
The significant byte is the low order byte of the word.
INT8_HB Transmission of an 8 bit signed integer in a 16 bit value. /
The significant byte is the high order byte of the word.
UINT8_LB Transmission of an 8 bit unsigned integer in a 16 bit value. /
The significant byte is the low order byte of the word.
UINT8_HB Transmission of an 8 bit unsigned integer in a 16 bit value. /
The significant byte is the high order byte of the word.
INT16 Transmission of a 16 bit signed integer. The high order 2-1
byte is transmitted first (see Modbus norm)
UINT16 Transmission of a 16 bit unsigned integer. The high order 2-1
byte is transmitted first (see Modbus norm)
INT32_LW_LB Transmission of a 32 bit signed integer. The low order 1-2-3-4
word of the long value is transmitted first. The low order
byte of each word is transmitted first.
INT32_LW_HB Transmission of a 32 bit signed integer. The low order 2-1-4-3
word of the long value is transmitted first. The high order
INT32_HW_LB Transmission of a 32 bit signed integer. The high word of 3-4-1-2
the long value is transmitted first. The low byte of each
word is transmitted first.
INT32_HW_HB Transmission of a 32 bit signed integer. The high order 4-3-2-1
UINT32_LW_LB Transmission of a 32 bit unsigned integer. The low order 1-2-3-4
UINT32_LW_HB Transmission of a 32 bit unsigned integer. The low order 2-1-4-3
UINT32_HW_LB Transmission of a 32 bit unsigned integer. The high order 3-4-1-2
UINT32_HW_HB Transmission of a 32 bit unsigned integer. The high order 4-3-2-1
REAL32_LW_LB Transmission of a 32 bit real value. The low order word is 1-2-3-4
transmitted first. The low order byte of each word is
transmitted first.
Transmission
Format Description
order
REAL32_LW_HB Transmission of a 32 bit real value. The low order word is 2-1-4-3
transmitted first. The high order byte of each word is
transmitted first.
REAL32_HW_LB Transmission of a 32 bit real value. The high order word is 3-4-1-2
transmitted first. The low order byte of each word is
transmitted first.
REAL32_HW_HB Transmission of a 32 bit real value. The high order word is 4-3-2-1
transmitted first. The high order byte of each word is
transmitted first.
M230_T5_TYPE Transmission of a 32 bit : Unsigned Measure 4-3-2-1
Bit 31to 24 decimal exposant (signed 8 bytes)
Bit 23…00 binary unsigned value 24 bytes
M230_T6_TYPE Transmission of a 32 bit : Signed Measure 4-3-2-1
Bit 31to 24 decimal exposant (signed 8 bytes)
Bit 23…00 binary signed value 24 bytes
M230_T7_TYPE Transmission of a 32 bit: power factor 4-3-2-1
Bit 31to 24 Signed :Import / Export (00/FF)
Bit 23…16 Signed :Inductive / capacitive (00/FF)
Bit 15…00 Unsigned value (16 bytes)
ION_MODULUS_ Transmission of a 32 bit: ION Energy values 4-3-2-1
10000_unsigned
Bit 31to 16 reg Hight: RH= unsigned value/10000
Bit 15…00 reg Low : RL = unsigned value modulus 10000
Value = RH*10000+RL
ION_MODULUS_ Transmission of a 32 bit: ION Energy values 4-3-2-1
10000_signed
Bit 31to 16 reg Hight: RH= signed value/10000
Bit 15…00 reg Low : RL = signed value modulus 10000
Value = RH*10000+RL
Both reg high and low are signed
4.6.2.4 Defining an IED address for a Counter datapoint

The addition of an IED address for a Counter datapoint is done via the “Objects entry”
window at IED Counter mapping level by clicking on mouse’s right button.
FIGURE 53: ADDING AN IED COUNTER ADDRESS (E.G. FOR T101 IED)
Once added, an IED Counter address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): word address.
3. fonction (range [0, 65535],step 1): Modbus function used to read the MV:
- 3, 4 : read word
4. data format: similar to MV.
For T101 protocol:
address.
For T103 protocol:
8. function type (range [0, 65535],step 1):
9. information number (range [0, 65535],step 1):
10. index in the ASDU (range [0, 65535],step 1):
11. common address of ASDU (range [-1, 65535],step 1):
For DNP3 protocol:
12. address (range [0, 65535],step 1):
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103
(7)
(8)
(9)
(10
)
(11
DNP3
)
(12
)
FIGURE 54: DEFINING AN IED ADDRESS FOR A COUNTER DATAPOINT

4.6.2.5 Defining an IED address for a SPC datapoint

The addition of an IED address for a SPC datapoint is done via the “Objects entry” window at
IED SPC mapping level by clicking on mouse’s right button.
FIGURE 55: ADDING AN IED SPC ADDRESS (E.G. FOR T101 IED)
Once added, IED SPC address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): Bit address for function 5 or 15, Word
address for function 6.
3. bit number (range [0, 65535],step 1): Used only if Function 6 is used (see function
attribute).
4. function (range [0, 65535],step 1): Modbus function to use to send the SPC:
- 5 : write 1 bit (Mapping address indicates the address of the bit),
- 6 : write 1 word (Mapping address indicates the address of the word, bit number
indicates the number of the bit in the word),
- 15 : write N bits (used to set only 1 bit at a time, Mapping address indicates the
address of the bit)
For T101 protocol:
address.
For T103 protocol:
- 20 (for all IED)
- 45,46 (Only for Px3x)
8. function type (range [0, 65535],step 1): refer to relay documentation.
For DNP3 protocol:
Modbus (1)
(2)
(3)
(4)
unused
T101
(5)
(6)
unused
T103 (7)
(8)
(9)
unused
DNP3
(10)
)
unused
C0178ENb
FIGURE 56: DEFINING AN IED ADDRESS FOR A SPC DATAPOINT

4.6.2.6 Defining an IED address for a DPC datapoint

The addition of an IED address for a DPC datapoint is done via the “Objects entry” window
at IED DPC mapping level by clicking on mouse’s right button.
FIGURE 57: ADDING AN IED DPC ADDRESS (E.G. FOR T101 IED)
Once added, IED DPC address attributes must be set at SCE level:
2. mapping address (range [0, 65535],step 1): Bit address for function 5 or 15, Word
address for function 6.
3. bit number (range [0, 65535],step 1): used only if Function 6 is used (see function
attribute).
4. function (range [0, 65535],step 1): Modbus function to use to send the DPC:
- 5 : write 1 bit (Mapping address indicates the address of the bit),
indicates the number of the bit in the word),
- 15 : write N bits (used to set only 1 bit at a time, Mapping address indicates the
address of the bit)
For T101 protocol:
address.
For T103 protocol:
- 20 (for all IED)
- 45,46 (Only for Px3x)
For DNP3 protocol:
For all protocols:

11. contact type (open / close / unused): For all protocol type, DPC control on IED can
also be done via two different addresses. In that case, two ‘DPC address on IED’ must
be created for this DPC. For each of them, this attribute must be set to ‘Open’ or
‘Close’, to precise which order of the DPC is concerned by the IED address. If DPC
control is given by only one IED address, set ‘contact type’ value to ‘unused’.
Modbus (1)
(2)
(3)
(4)
(unused)
(11
)
T101
(5)
(6)
(unused
(11 )
)
T103 (7)
(8)
(9)
(unused)
(11)
DNP3
(10)
(unused)
(11)
C0179ENb
FIGURE 58: DEFINING AN IED ADDRESS FOR A DPC DATAPOINT

4.6.2.7 Defining an IED address for a SetPoint datapoint

The addition of an IED address for a SetPoint datapoint is done via the “Objects entry”
window at IED SetPoint mapping level by clicking on mouse’s right button.
FIGURE 59: ADDING AN IED SETPOINT ADDRESS (E.G. FOR T101 IED)
Once added, IED SetPoint address attributes must be set at SCE level:
SetPoint address on Modbus is only available for WAGO relay, where output format is fixed
to UINT16.
2. mapping address (range [0, 65535],step 1): Word address for function 6.
3. function (range [0, 65535],step 1): Modbus function to use to send the SetPoint:
indicates the number of the bit in the word).
For T101 protocol:
5. output format (REAL32 (IEEE 754) / Normalized / Scaled).
For T103 protocol:
6. SetPoint address on T103 is only available for REGD relay, where output format is
configurable.
7. ASDU number (range [0, 65535],step 1): refer to relay documentation.
10. output format (INT8 / UINT8 / INT16 / UNIT16 / REAL32 (IEEE754))
For DNP3 protocol:
For all protocol type, values of SetPoint control on IED must be verified and scaled
depending on output format, before transmission. This is done via two extra attributes
‘minimal value’ (11) and ‘maximal value’ (12).
Modbus (1)
(2)
(3)
(unused)
(11)
(12)
T101 (4)
(unused)
(5)
(11)
(12)
(6)
T103
(7)
(8)
(unused)
(9)
(11)
(12)
DNP3 (10)
(unused)
(11)
(12)
C0180ENb
FIGURE 60: DEFINING AN IED ADDRESS FOR A SETPOINT DATAPOINT

4.6.3 Addressing a datapoint on an IED legacy network
Refer to sections:
• 5.6.2 Acquiring input datapoint via an IED legacy network
• 5.7.2 Controlling output datapoint via an IED legacy network

4.7 Networking SCADA on computer SCADA network

4.7.1 Creating a SCADA network
An electrical substation can be supervised and controlled from many points inside the
substation via PACiS operator interfaces (Substation Control Point or SCP) and/or PACiS
computer bay panels (Bay Control Point or BCP), and outside the substation. Generally, the
distant control of the substation (Remote Control Point or RCP) is done via specific networks
called SCADA legacy network.
Several SCADA legacy networks can be connected to a PACiS system, via PACiS computer
or PACiS telecontrol gateway sub-systems. SCADA legacy networks are managed as
master by distant SCADA and can be redundant for safety reason. A PACiS computer can
manage up to two SCADA networks.
At SCE data modelling level, only SCADA legacy networks and their protocol are modelled
and connected to gateway sub-systems. Each SCADA network has to be linked to a main
communication port and eventually an auxiliary communication port in case of redundancy.
4.7.1.1 Adding a SCADA network
To create a SCADA network on a computer:
• Add a SCADA network from object entry available at computer level (1),
• Update the SCADA network attributes relevant to its protocol characteristics (see
section 4.7.2 Defining addressing mapping of SCADA network).
• If SCADA does not use the substation network to communicate with the computer,
update its ‘has for main communication port’ relation and the communication port
characteristics.
• For DNP3 and T101 protocol on serial line, SCADA link can be redundant. To create a
redundant SCADA link, just add the relation ‘has for auxiliary communication port’ (2)
extra relation on computer SCADA network and fill it with the relevant serial port.
• A computer can manage up to two T104 SCADA clients. These two clients have
separate configurations but may have same data. On the SCADA port, up to four front
ends can be defined, corresponding to one active port and three backup ports. So, up
to four IP addresses will be defined during the configuration of each T104 client (
attributes (13) in section 4.7.1.6 Setting specific attributes of a T104 SCADA
network.) If both clients are communicating with the computer, they must manage
thein own redundancy for doing controls with coherency.
(1)
FIGURE 61: ADDING A SCADA NETWORK

(2)
FIGURE 62: CREATING A REDUNDANT SCADA LINK

4.7.1.2 Setting general attributes of a SCADA network
Whatever the kind of SCADA network, its short name and long name attributes (1) must be
updated for correct logging and alarm discrimination concerning status datapoints managed
by the computer for each connected SCADA network. Then the supported protocol (2) must
be selected (T101 in the example given hereafter). So the SCADA attributes tab-panes
(Protocol, SOE and Disturbance) are refreshed relatively to the selected protocol.
(1)
(2)
(3)
(4)
FIGURE 63: SETTING GENERAL ATTRIBUTES OF A SCADA NETWORK

4.7.1.3 Setting general attributes of a T101 SCADA network
When adding a T101 SCADA network its general attributes must be updated (refer to the
previous figure)
3. redundancy type (Active line after GI received / Active line after Reset line received /
Active line on trafic):
4. time reference (UTC / local):
4.7.1.4 Setting specific attributes of a T101 SCADA network

When adding a T101 SCADA network, the following attributes available for this protocol must
be updated (Protocol and SOE tab-panes):
1. link address length (1 byte / 2 bytes)
2. link address (range [1, 65534], step 1)
3. ASDU common address length (1 byte / 2 bytes)
4. ASDU common address (range [1, 65534], step 1)
5. address structure (Address on 8 bits (1 byte) / Address on 16 bits (2 bytes) / Address
on 8 bits.8 bits / Address on 8 bits.16 bits / Address on 16 bits.8 bits / Address on 8
bits. 8 bits. 8 Bits / Address on 24 bits (3 bytes))
6. frame max length (range [1, 255], step 1)
7. cause of transmission length (Address on 8 bits / Address on 16 bits)
8. MV periodic cycle (range [0 s, 65534 s], step 1 s)
9. binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
10. background scan cycle (range [0 s, 65535 s], step 1 s)
11. type of link (unbalanced / balanced)
12. T3: test frame time-out (range [1 s, 255 s], step 1 s)
13. SBO time-out (range [0 s, 65535 s], step 1 s)
14. interframe duration (range [1, 50], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames
15. validity for 'Jammed' state (Valid / Invalid)
16. SOE file support (No / Yes)
17. SOE file address: this attribute is visible and significant only if attribute SOE file
support is set to Yes
18. SOE file format (T101 / S900) this attribute is visible and significant only if attribute
SOE file support is set to Yes
19. SOE file nb of events (range [0, 1000], step 1) this attribute is visible and significant
only if attribute SOE file support is set to Yes
20. 'full' SOE file nb of events (range [0, 1000], step 1) file message sent to SCADA
(this attribute is visible and significant only if attribute SOE file support is set to Yes)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18 )
(19)
(20)
FIGURE 64: SETTING PROTOCOL AND SOE ATTRIBUTES OF A T101 SCADA NETWORK
The following constraints between the attributes must be respected :
"SOE file nb of events" > "'full' SOE file nb of events".
4.7.1.5 Setting general attributes of a DNP3 SCADA network
In the following figure the selected protocol for the SCADA link is ‘DNP3’ (1).
(1)

When setting a DNP3 SCADA network, some specific attributes available for the protocol
must be updated (Protocol tab-pane):
1. TCP/IP usage (No / Yes): set to ‘Yes’ if substation network is used by the DNP3
SCADA to communicate with the computer
2. Link address: not significant if TCP/IP usage is set to ‘Yes’
3. SPS/DPS class ( 1 / 2 / 3)
4. MV class ( 1 / 2 / 3)
5. Counter ( 1 / 2 / 3)
6. MV format (32 bits / 16 bits)
7. static MV (without flag / with flag)
8. event MV (without time, with time)
9. counter format (32 bits / 16 bits)
10. static counter (without flag / with flag)
11. event counter (without time, with time)
12. SBO time-out: maximum time between select orde and execute order
time, expressed in number of characters, that must exist between two frames
14. spontaneous message enable ( No / Yes): this attribute defines if the unsolicited
mode is allowed or not for the protocol. If this attribute is set to No there is possibility
to allowed it from the SCADA. If this attribute is set to Yes the computer can send
unsolicited messages as soon as the SCADA is initialiazed. Furthermore the SCADA
may disable or enable this unsolicited mode.
15. spontaneous message class ( none / class 1 / class 2 / class 1 & 2 / class 3 / class 1
& 3 / class 2 & 3 / class 1 & 2 & 3): This attribute is only significant if the previous
attribute is set to Yes. This attribute defines which class(es) is (are) concerned by this
unsolicited mode.
Setting SOE information SOE tab-panes, for DNP3 SCADA network is not significant (not
implemented).
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
) (14)
(15)
FIGURE 66: SETTING PROTOCOL ATTRIBUTES OF A DNP3 SCADA NETWORK

4.7.1.6 Setting specific attributes of a T104 SCADA network

In the following figure the selected protocol for the SCADA link is ‘T104’ and the selected
time reference is UTC.
(1)

When setting a T104 SCADA network, some specific attributes available for the protocol
must be updated (Protocol and SOE tab-panes):
1. ASDU common address (range [1, 65534], step 1)
2. address structure (Address on 8 bits.16 bits / Address on 16 bits.8 bits /
Address on 8 bits.8bits.8bits / Address on 24 bits (3 bytes)):
3. frame max length (range [1, 255], step 1)
4. MV periodic cycle (range [0 s, 65534 s], step 1 s)
5. binary time size (CP24Time2A (3 bytes) / CP56Time2A (7 bytes))
6. background scan cycle (range [0 s, 65535 s], step 1 s)
7. T1: APDU time-out (range [1 s, 255 s], step 1 s)
8. T2: acknowledgement time-out (range [1 s, 255 s], step 1 s)
9. T3: test frame time-out (range [1 s, 255 s], step 1 s)
10. K: sent unack. frames (APDU) (range [1, 255], step 1)
11. W: ack. received frames (APDU) (range [1, 255], step 1)
12. max command delay (range [0 s, 32767 s], step 1 s)
13. socket IP #i (i ∈ [1, 4])

14. SBO time-out (range [0 s, 65535 s], step 1 s)
15. validity for 'Jammed' state (Valid / Invalid)
16. Switchover (Automatic switchover / Manual switchover)
17. SOE file support (No / Yes)
18. SOE file address (this attribute is visible and significant only if attribute SOE file
support is set to Yes)
19. SOE file format (T101 / S900) (this attribute is visible and significant only if attribute
SOE file support is set to Yes)
20. SOE file nb of events (range [0, 1000], step 1) (this attribute is visible and significant
only if attribute SOE file support is set to Yes)
21. 'full' SOE file nb of events (range [0, 1000], step 1) file message sent to SCADA
(this attribute is visible and significant only if attribute SOE file support is set to Yes)
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10
(11 )
) (12
(13 )
) (14
(15 )
) (16
)
(17
) (18
(19 )
) (20
(21 )
)
FIGURE 68: SETTING SPECIFIC ATTRIBUTES OF A T104 SCADA NETWORK

• The following constraints between the attributes must be respected :

"SOE file nb of events" > "'full' SOE file nb of events"
"T2" < "T1"
"T3" > "T1"
"W" ≤ "K"
4.7.1.7 Setting specific attributes of a MODBUS SCADA network

In the following figure the selected protocol for the SCADA link is ‘Modbus’.
(1)
FIGURE 69: SETTING PROTOCOL TYPE OF A SCADA NETWORK

When setting a MODBUS SCADA network, some specific attributes available for the protocol
must be updated (Protocol tab-pane):
1. TCP/IP usage (No / Yes): set to ‘Yes’ if substation network is used by the MODBUS
SCADA to communicate with the computer.
2. link address: not significant if TCP/IP usage is set to ‘Yes’.
For a MODBUS SCADA network SOE tab-panes attributes are not significant (not
implemented).
(1)
(2)
(3)
FIGURE 70: SETTING PROTOCOL ATTRIBUTES OF A MODBUS SCADA NETWORK

4.7.2 Defining addressing mapping of SCADA network

To transmit information between PACiS system and SCADA, a SCADA legacy network is
used. To receive or send information between legacy IED and PACiS system, each
concerned data must have a specific address on the legacy network relatively to its protocol.
General modelling of SCADA legacy network address mapping can be done. At SCE level, a
SCADA legacy network owns a “SCADA mapping” object, that is split in categories of
mapping on a per datapoint kind basis. In each category of mapping, elementary SCADA
addresses can be created. For details about datapoint, refer to section 5 DEFINING
DATAPOINT. This mapping is implicitly created during IED adding at legacy network level.
WARNING: ADDRESSING A MPS DATAPOINT ON A SCADA NETWORK IS NOT
AVAILABLE.
Entry point
of SCADA
mapping
Categories
per datapoint
kind basis
C0181ENb
FIGURE 71: STRUCTURE OF THE ADDRESSING MAPPING OF A SCADA NETWORK

• In the SCADA Mapping, the address identification of each "Gtw xxx addr." must be
unique. In the particular cases of T101 and T104 protocols, the uniqueness constraint
is applicable only for addresses of the same type. Addresses of different types can
have identical addresses and therefore this does not lead to an error but to a warning.
• On a DNP3 protocol, a "Gtw MV addr.", which is the SCADA address of a "Tap pos
ind" datapoint, must have its "Format" attribute set to the "Natural" value.
4.7.2.1 Defining a SCADA address for a SPS datapoint
The addition of a SCADA address for a SPS datapoint is done via the “Objects entry”
window at SCADA SPS mapping level by clicking on mouse’s right button.
FIGURE 72: ADDING A SCADA SPS ADDRESS

Once added, SCADA SPS address attributes must be set at SCE level:
1. shortname of the address used for internal SCE identification.
2. object address - register
For T101/T104 protocol:
3. object address.
4. Event (No / Yes with time tag / Yes witout time tag): when set to ‘Yes with time tag’,
indicates that change of state of the datapoint are transmitted spontaneously with time
Tag.
5. Event record ( Does not involved in a transfert of file / Create a RECORD EVENT if
there is not it current / Add to the current record EVENT / Create a RECORD EVENT
and adds to the current record EVENT): when set to a value different from ‘Does not
involved in a transfer of file’, indicates if change of state of the datapoint must be
saved in Sequence of Event file. At computer level, values different from ‘Does not
involved in a transfer of file’ are associated to the same treatment, because only one
SOE file is managed by computer. The set of available values is maintained for
compatibility with MiCOM gateway addressing in MiCOM gateway.
6. Inversion (No / Yes): Indicates that the datapoint value needs to be inverted before
transmission.
7. Background scan (No / Yes): indicates if the datapoint belongs to the background
scan cycle.
8. Group ([0..16)] / 0=no group): indicates to which “T101/T104 General Interrogation
group” the datapoint is assigned. 0 means ‘no group’ assignation.
For DNP3 protocol:

9. object address - index.
10. Event (No / Yes with time tag): when set to ‘Yes with time tag’, indicates if change of
state of the datapoint are transmitted spontaneously with time Tag.
11. Inversion (No / Yes): indicates that the datapoint value needs to be inverted before
transmission.
Modbus
(1)
(2)
T101/T104
(3)
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
FIGURE 73: DEFINING A SCADA ADDRESS FOR A SPS DATAPOINT

4.7.2.2 Defining a SCADA address for a DPS datapoint

The addition of a SCADA address for a DPS datapoint is done via the “Objects entry”
window at SCADA DPS mapping level by clicking on mouse’s right button.
FIGURE 74: ADDING A SCADA DPS ADDRESS

Once added, SCADA DPS address attributes must be set at SCE level:
1. short name: used for internal SCE identification
2. double address usage (No / Yes): only available for Modbus SCADA protocol. If set
to ‘Yes’, DPS is transmitted to SCADA via two distinct SCADA address, one for the
open state, the other one for the close state.
3. object address - register: used if ‘Double address usage’ is set to ‘No’.
4. open state address: used if ‘Double address usage’ is set to ‘Yes’. This attribute
defines the SCADA address for the open state of the DPS.
5. Closed state address: used if ‘Double address usage’ is set to ‘Yes’. This attribute
defines the SCADA address for the closed state of the DPS.
6. Event (No / Yes with time tag /Yes without time tag): when set to ‘Yes with time tag’,
indicates if change of state of the datapoint are transmitted spontaneously with time
Tag.
7. Event record (Does not involved in a transfert of file / Create a RECORD EVENT if
there is not it current / Add to the current record EVENT / Create a RECORD EVENT
and adds to the current record EVENT): when set to a value different from ‘Not
involved in a transfer of file’, indicates if change of state of the datapoint must be
saved in Sequence of Event file. At computer level, values different from ‘Not involved
in a transfer of file’ are associated to the same treatment, because only one SOE file
is managed by computer. The set of available values is maintained for compatibility
with MiCOM gateway addressing in MiCOM gateway.
transmission.
9. Background scan: (No / Yes): indicates if the datapoint belongs to the background
scan cycle.
10. Group ([0..16)] / 0=no group): indicates to which “T101/T104 General Interrogation
group” the datapoint is assigned. 0 means ‘no group’ assignation
11. object address (index)
For DNP3 protocol:
state of the datapoint are transmitted spontaneously with time Tag
transmission
14. object address - index
Modbus
(1)
(2)
(3)
(4)
(5)
T101/T104
(6)
(7)
(8)
(9)
(10
)
(11)
DNP3
(12)
(13)
(14)
FIGURE 75: DEFINING A SCADA ADDRESS FOR A DPS DATAPOINT

4.7.2.3 Defining a SCADA address for a MV datapoint

The addition of a SCADA address for a MV datapoint is done via the “Objects entry” window
at SCADA MV mapping level by clicking on mouse’s right button.
FIGURE 76: ADDING A SCADA MV ADDRESS

Once added, SCADA MV address attributes must be set at SCE level:
1. short name of the address used for internal SCE identification.
3. Format (Natural / Unsigned normalized / Signed normalized /Real IEEE754 – little
endian / Real IEEE754 – big endian): transmission format.
4. Precision (8..16): number of transmitted bits.
5. object address.
6. Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’,
indicates that change of state of the datapoint are transmitted spontaneously with time
Tag.
7. Event record ( No / Yes): indicates if change of state of the datapoint must be saved
in Sequence of Event file or not..
8. Format (Normalized / Adjusted / Float):transmission format.
9. cycle type (None / Periodic / Background scan): indicates which transmission cycle
the MEAS belongs to.
10. Group ([0..16)] / 0=no group): indicates which “T101/T104 General Interrogation
group” the datapoint is assigned to. 0 means ‘no group’ assignation.
For DNP3 protocol:

11. object address
13. Format (Natural / Adjusted).
Modbus
(1)
(2)
(3)
(4)
T101/T104
(5)
(6)
(7)
(8)
(9)
(10)
DNP3
(11)
(12)
(13)
FIGURE 77: DEFINING A SCADA ADDRESS FOR A MV DATAPOINT

4.7.2.4 Defining a SCADA address for a Counter datapoint

The addition of a SCADA address for a Counter datapoint is done via the “Objects entry”
window at SCADA Counter mapping level by clicking on mouse’s right button.
FIGURE 78: ADDING A SCADA COUNTER ADDRESS

Once added, SCADA Counter address attributes must be set at SCE level:
3. Format (Natural / Unsigned normalized / Real IEEE754 – little endian / Real IEEE754
– big endian): transmission format.
4. object address.
5. Event (No / Yes with time tag / Yes without time tag): when set to ‘Yes with time tag’,
indicates if changes of state of the datapoint are transmitted spontaneously with time
Tag.
6. Group ([0..4] / 0=no group): indicates which “T101/T104 General Interrogation group”
the datapoint is assigned to. 0 means ‘no group’ assignation.
For DNP3 protocol:
7. object address.
Modbus
(1)
(2)
(3)
T101/T104
(4)
(5)
(6)
DNP3
(7)
(8)
FIGURE 79: DEFINING A SCADA ADDRESS FOR A COUNTER DATAPOINT

4.7.2.5 Defining a SCADA address for a SPC datapoint
The addition of a SCADA address for a SPC datapoint is done via the “Objects entry”
window at SCADA SPC mapping level by clicking on mouse’s right button.
FIGURE 80: ADDING A SCADA SPC ADDRESS

Once added, SCADA SPC address attributes must be set at SCE level:

2. object address - register.
3. object address
4. SCADA execute order type (Select execute / Direct execute): precise if SCADA uses
a ‘Select execute” or a ‘Direct execute’ sequence to send control on the datapoint.
For DNP3 protocol:
5. object address
6. SCADA execute order type (Select execute / Direct execute):precise if SCADA uses
a ‘Select execute” or a ‘Direct execute’ sequence to send control on the datapoint.
Modbus
(1)
(2)
T101/T104
(3)
(4)
DNP3
(5)
(6)
FIGURE 81: DEFINING A SCADA ADDRESS FOR A SPC DATAPOINT

4.7.2.6 Defining a SCADA address for a DPC datapoint

The addition of a SCADA address for a DPC datapoint is done via the “Objects entry”
window at SCADA DPC mapping level by clicking on mouse’s right button.
FIGURE 82: ADDING A SCADA DPC ADDRESS

Once added, SCADA DPC address attributes must be set at SCE level:
3. object address.
4. SCADA execute order type (Select execute / Direct execute): precises if SCADA
uses a ‘Select execute” or a ‘Direct execute’ sequence to send control on the
datapoint.
For DNP3 protocol:
5. object address in [0..65535].
datapoint.
Modbus
(1)
(2)
T101/T104
(3)
(4)
DNP3
(5)
(6)
FIGURE 83: DEFINING A SCADA ADDRESS FOR A DPC DATAPOINT
4.7.2.7 Defining a SCADA address for a SetPoint datapoint

The addition of a SCADA address for a SetPoint datapoint is done via the “Objects entry”
window at SCADA SetPoint mapping level by clicking on mouse’s right button.
FIGURE 84: ADDING A SCADA SETPOINT ADDRESS

Once added, SCADA SetPoint address attributes must be set at SCE level:

3. format.(signed 16 bits / Real IEEE754 – little endian / Real IEEE754 – big endian)
4. object address.
5. SCADA execute order type (Select execute / Direct execute): this attibute defines if
SCADA uses a ‘Select execute” or a ‘Direct execute’ sequence to send control on the
datapoint.
6. Minimal value: available minimal value on the protocol (used for scaling and checks).
7. Maximal value: available maximal value on the protocol (used for scaling and
checks).
8. Format (Normalized / Adjusted / Float).
For DNP3 protocol:
9. object address [0..65535].
datapoint.
11. minimal value: available minimal value on the protocol (used for scaling and checks).
12. maximal value: available maximal value on the protocol (used for scaling and
checks).
13. format (Natural / Adjusted).
Modbus
(1)
(2)
(3)
T101/T104
(4)
(5)
(6)
(7)
(8)
DNP3
(9)
(10)
(11)
(12)
(13)
FIGURE 85: DEFINING A SCADA ADDRESS FOR A SETPOINT DATAPOINT

4.7.2.8 Defining a SCADA address for bypass synchrocheck

For details about synchronised circuit-breakers, refer to section 6.2 Defining a Synchrocheck
function.
Synchronised circuit-breaker can be controlled through SCADA network. In that case, the
SPC (resp. DPC) control of the synchronised breaker is linked to a SCADA SPC (resp. DPC)
address. Unfortunately, bypass synchrocheck is not implemented in SCADA protocol. To
solve this problem, an extra SCADA SPC (resp. DPC) address that will bypass the
synchrocheck must be given to the SPC (resp. DPC) control of the breaker. At SCE level,
this extra address is linked to the SCADA address of the SPC (resp. DPC) control of the
synchronised breaker.
To define a SCADA address for bypass synchrocheck:
• Create the SCADA SPC (resp. DPC) address (A) to send SPC (resp. DPC) control of
the synchronised breaker.
• Create a SCADA SPC (resp. DPC) address (B) for bypass synchrocheck in the
SCADA mapping.
• Add the relation ‘has for bypass synchrocheck address’ via the “Objects entry” window
at SCADA address (A) and fill it with the SCADA address (B).
address (A)
address (B)
C0347ENa
FIGURE 86: ADDING A BYPASS SYNCHROCHECK ADDRESS TO A SCADA SPC/DPC ADDRESS (E.G.
FOR SCADA DPC ADDRESS)
4.7.3 Addressing datapoint on SCADA legacy network

For details about datapoint, refer to section 5 DEFINING DATAPOINT.
To exchange datapoint values between station-bus sub-systems and SCADA, datapoints
should be linked to specific SCADA addresses, by adding at datapoint level the relation ‘has
for SCADA address’ (1) and filling it with the corresponding SCADA address in a pre-
configured SCADA addressing mapping (refer to section 4.7.2 Defining addressing mapping
of SCADA network, for SCADA mapping definition).
Addressing a MPS datapoint on the SCADA legacy network is not available.
(1)
FIGURE 87: REALISING SCADA ADDRESSING OF A DATAPOINT

(E.G. FOR BAY SPS DATAPOINT)
4.8 Defining wave record file management

The C264/C264C computers manage two kinds of wave recording file:
• IED connected to computer legacy network can produce disturbance files. In that
case, computer monitors their availability. As soon as available, they are uploaded
and stored at computer level. Computer computes for System Management Tool
(SMT) a real-time data per IED basis that gives the availability of a disturbance file, via
station-bus network. Then, SMT downloads it from computer. At the end of successful
downloading, computer erases the real-time data of availability.
• Via a CT/VT board (TMU200), computer can manage its own waveform record files.
Waveform channels are directly acquired on CT/VT board channels and buffered.
Triggered by pre-defined change of state, associated buffers are flushed on files that
correspond to waveform record files. In that case computer computes for SMT a real-
time data that gives the availability of a computer waveform record file, via station-bus
network. Then processing is similar to IED’s one.
4.8.1 Defining management of disturbance file for IED
Allowing computer to manage IED disturbance is done at IED configuration level by:
• Setting its ‘automatic disturbance’ attribute to yes.
• Adding RDRE brick (1) for the IED in LD0 logical device of the IEC-61850 mapping of
the computer.
• Adding the system SPS datapoint ‘DREC ready’ (2) at IED level, linked to a pre-
defined datapoint profile.
• Fill the mandatory IEC address for this datapoint, with the relevant data object of the
RDRE brick (3).
(2)
(1)
FIGURE 88: ADDING RDRE BRICK AND DREC READY DATAPOINT FOR IED
(3)
FIGURE 89: SETTING IEC-61850 ADDRESS OF DREC READY DATAPOINT FOR IED
For T103 IED extra information must be configured to process correct disturbance file
COMTRADE structure at computer level (see following section).
4.8.2 Defining T103 IED extra information for disturbance file

T103 extra informations for disturbance file are located at T103 acquisition type and concern
definition of analog and digital channels, stored in disturbance file, relatively to COMTRADE
format.
4.8.2.1 Adding an analog channel definition
The addition of an analog channel definition for T103 is done via the “Objects entry” window
at T103 acquisition type level by clicking on mouse’s right button. Up to 15 analog channels
can be created under a T103 acquisition type.
FIGURE 90: ADDING A T103 ANALOG CHANNEL DEFINITION

Once added, channel definition attributes must be set at SCE level:
1. channel label.
2. long name of the channel used for internal SCE identification.
3. phase name: label of the phase corresponding to the channel.
4. channel number: (cf. mapping IED– field ACC in IEC 60870-5-103 documentation).
5. unit: unit corresponding to the channel.
6. coefficient (0: not used): value which the samples must be multiplied by in order to
get the real value (0: not used). Generally, data uploaded from IED allows to compute
this ‘multiply coefficient’. Unfortunately, some IED don’t give correct data. In this case,
this coefficient must be set here.
7. shift time (range [0 s, 1 s], step 1 µs): elapsed time since the beginning of the
sampling period.
8. maximal sample value (range [0 , 32767], step 1).
9. minimal sample value (range [-32768, 0], step 1)..
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 91: SETTING T103 ANALOG CHANNEL DEFINITION

For more details about the analog channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
4.8.2.2 Adding a digital channel definition

The addition of a digital channel definition for T103 is done via the “Objects entry” window at
T103 acquisition type level by clicking on mouse’s right button. Up to 255 digital channels
can be created under a T103 acquisition type.
FIGURE 92: ADDING A T103 DIGITAL CHANNEL DEFINITION

Once added, channel definition attributes must be set at SCE level:
1. channel label.
2. long name of the channel used for internal SCE identification.
3. function number (range [0 , 255], step 1): corresponds to function type of the channel
in T103 protocol.
4. information number (range [0 , 255], step 1): corresponds to information number of
the channel in T103 protocol.
5. default state (Off / On).
(1)
(2)
(3)
(4)
(5)
FIGURE 93: SETTING T103 DIGITAL CHANNEL DEFINITION

For more details about the digital channel definition, refer to COMTRADE (IEEE C37.11)
external documentation.
4.8.3 Defining management of wave record file for computer CT/VT board
Allowing computer to manage its own wave record file is done at computer configuration
level by:
• Defining a fast and/or slow waveform recording (see following sections):
− fast waveform recording gives access to samples acquired via CT/VT board.
− slow waveform recording gives access to analogues (MV) and digital values
(SPS, DPS, SPC, DPC) file recording.
• Adding RDRE brick (1) for the computer in LD0 logical device of the IEC-61850
mapping of the computer.
• Adding the system SPS datapoint ‘C26x DREC ready’ (2) at computer level, linked to
a pre-defined datapoint profile.
• Fill the mandatory address for this datapoint, with the relevant data object of the
RDRE brick (3).
(2)
(1)
FIGURE 94: ADDING A RDRE IEC-61850 BRICK AND A DREC READY DATAPOINT FOR A COMPUTER
(3)
FIGURE 95: SETTING IEC 61850 ADDRESS OF DREC READY DATAPOINT FOR COMPUTER
4.8.3.1 Defining fast waveform recording

The inputs for the fast waveform records are up to 4 CT samples and 4 VT samples, and the
values of selected digital SPS, DPS, SPC or DPC datapoints (for more details about
datapoints, refer to section 5 DEFINING DATAPOINT). Up to 128 digital datapoints may be
captured. The choice of selected inputs/outputs is defined in configuration.
The waveform recorder provides up to 8 CT/VT channels and up to 128 digital datapoints for
extraction by SMT.
A maximum of 480 cycles (9,6 seconds at 50 Hz) of measurements samples, with 32
samples per cycle, can be stored, divided in 1, 2, 4 or 8 files saved in flash disk.
A timer channel is also required to provide accurate timing information for each sample. The
delay between each sample is assumed constant over a single cycle.
Number of Files Number of cycles

8 60
4 120
2 240
1 480
The waveform recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of binary inputs (SPS or DPS datapoint)
• Changes in state of digital outputs (SPC or DPC datapoint)
• Measurement threshold violations (MV datapoint)
• Operator request
Only one re-trig is allowed: it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are available in COMTRADE 2001 format.
The addition of a fast waveform recording is done via the “Objects entry” window at
computer level by clicking on mouse’s right button. Only one fast waveform recording can be
created under a computer.
FIGURE 96: ADDING A FAST WAVEFORM RECORDING

Once added, fast waveform recording attributes must be set at SCE level:
1. short name and long name: used for internal SCE identification.
2. pre-trigger cycle (range [0 , 480], step 1): corresponds to number of cycles (up to
480), that are stored before triggering.
3. total cycles (range [0 , 480], step 1): see previous description.
4. number of files (1 / 2 / 4 / 8): see previous description.
(1)
(2)
(3)
(4)
FIGURE 97: SETTING FAST WAVEFORM RECORDING

To define the inputs of a fast waveform recording, just add the relevant relation (1) available
at recording level and fill the relation with proper CT/VT channel or datapoint. Be careful,
only CT/VT channels and datapoints acquired on the computer can be defined as input of its
fast waveform recording.
(1)
FIGURE 98: DEFINING INPUTS OF FAST WAVEFORM RECORDING

To define the triggers of a fast waveform recording, just add the relevant relation (2)
available at recording level and fill the relation with proper datapoint. Be careful, only
datapoints acquired on the computer can be defined as input of its fast waveform recording.
(2)
FIGURE 99: DEFINING TRIGGERS OF FAST WAVEFORM RECORDING

Depending on the datapoint type, extra attributes must be set for ‘has for trigger’ relation.
These attributes gives the datapoint states (or thresholds for MV) that trig the record (see
following figure).
Triggering state for DPS:

Open,Close or Open+Close

Triggering threshold for MV:

For each threshold:
- no trigger
- trigger on threshold hold
- trigger on threshold reset
and reset
Triggering state for SPC:

Reset Set or Reset + Set
Triggering state for SPS:

Off, On or Off + On
C0183ENb
FIGURE 100: DEFINING TRIGGER CONDITIONS OF FAST WAVEFORM RECORDING


- "pre-trigger cycle" ≤ "total cycles"
- "number of files" ∗ "total cycles" ≤ 480 cycles
4.8.3.2 Defining slow waveform recording

The inputs for the slow waveform records are:
• MV datapoint coming from CT VT computation.
• MV datapoint coming from AIU boards.
• SPS or DPS datapoints.
• SPC or DPC datapoints.

The slow wave form manages up to 24 analogues (MV) and 48 digital values (SPS, DPS,
SPC, DPC).
MiCOM C264 stores at maximum 5000 integrated values as follow:
Number of Files Number of integrated values

1 5000
2 2500
5 1000
10 500
20 250
50 100
The integrated value has duration up to one hour. It is defined in configuration.

For analogue, the stored value is the average value during integrated period.
For digital, the stored value depends also on the average:
If average value > x then the stored value is 1 else it is 0, x is defined in configuration and it
is a value between 0.1 and 0.9.
The slow waveform recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of binary inputs (SPS or DPS datapoint)
• Changes in state of digital outputs (SPC or DPC datapoint)
• Measurement threshold violations (MV datapoint)
• Operator request
• Periodically (i.e. every day at 00h00)

The addition of a slow waveform recording is done via the “Objects entry” window at
computer level by clicking on mouse’s right button. Only one slow waveform recording can
be created under a computer.
FIGURE 101: ADDING A SLOW WAVEFORM RECORDING

Once added, slow waveform recording attributes must be set at SCE level:
1. short name and long name of the recording used for internal SCE identification.
2. pre-trigger cycle (range [0 , 5000], step 1): corresponds to the number of cycles (up
to 480) that are stored before triggering.
3. total records (range [0 , 5000], step 1): see previous description.
4. number of files (1 / 2 / 5 / 10 / 20 / 50): see previous description.
5. arbitration period (range [0 , 100], step 1): this data represents the percentage of
time during which the logical data must be set to 1 to consider the integrated data set
to 1.
6. integration time (range [0 , 216000], step 1): see previous description.
Data unit is number of cycles and has the following range:
- [1, 180000] if electric network frequency is 50 Hz
- [1, 216000] if 60 Hz
(for network frequency configuration, refer to section 4.3.2 Configuring measurement
acquisition and transmission)
7. activation period (Non periodic trigger / Daily trigger / weekly trigger / Daily and
weekly trigger): see previous description.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 102: SETTING FAST WAVEFORM RECORDING

To define the inputs of a slow waveform recording, just add the relevant relation (1) available
at recording level and fill the relation with proper datapoint. Be careful, only datapoints
acquired on the computer can be defined as input of its slow waveform recording.
(1)
FIGURE 103: DEFINING INPUTS OF SLOW WAVEFORM RECORDING

To define the datapoint-triggers of a slow waveform recording, just add the relevant relation
(2) available at recording level and fill the relation with proper datapoint. Be careful, only
datapoints acquired on the computer can be defined as input of its slow waveform recording.
A slow waveform can be configured without any datapoint-trigger, if a daily or weekly
activation period has been defined for it.
(2)
FIGURE 104: DEFINING TRIGGERS OF FAST WAVEFORM RECORDING

Depending on the datapoint type, extra attributes must be set for ‘has for trigger’ relation.
These attributes give the datapoint states (or thresholds for MV) that trig the record (see
following figure).


Triggering threshold for MV:

For each threshold:
- no trigger
- trigger on threshold reset
and reset
Triggering state for SPC:

Reset Set or Reset + Set
Triggering state for SPS:

Off, On or Off + On
C0184ENb
FIGURE 105: DEFINING TRIGGERS CONDITIONS OF SLOW WAVEFORM RECORDING


- "pre-trigger cycle" < "total records"
- "number of files" ∗ "total records" < 5000 records
• If "electrical frequency" ≡ 50 Hz :
- The "integration time" value must be in the range [1..180000].
- If the "integration time" value is > 5, then no DPC, SPC, DPS, SPS recording is
allowed.
• If "electrical frequency" ≡ 60 Hz :
- The "integration time" value must be in the range [1..216000].
- If the "integration time" value is > 6, then no DPC, SPC, DPS, SPS recording is
allowed.
4.9 Defining a computer klaxon

A computer can manage up to one external klaxon, that is started as soon as an audible
local alarm is raised on computer (to define audible alarm refer to section 5 DEFINING
DATAPOINT). The external klaxon is managed by a specific SPC datapoint wired on the
computer (‘ON’ order starts the klaxon, ‘OFF’ order stops it).
To define an external klaxon at computer level, just add the relation ‘has its klaxon managed
by’ at computer level and fill it with the relevant SPC.
FIGURE 106: DEFINING COMPUTER KLAXON

• The "SPC" link of the relation "has its klaxon controlled by" must be wired on a DO
channel of the Computer.
4.10 Setting system information for computer components

When creating a computer, specific datapoints are automatically added in ‘system infos’
binder (1) at computer level or PLC sub-component.
So it is when adding a board (2), an IED on legacy network (3), a serial printer (4), or a
SCADA network (5) attached to a computer. In that case, the ‘system infos’ binder is located
under the relevant added object.
For extra computer functionalities (wave recording, redundancy) some optional datapoints
can be required.
SCE calls such ‘system infos’ datapoints, system datapoints.
System datapoints provide real-time statuses and controls on system software or hardware
components, and generally can not be wired on board channels except for redundancy
function.
As datapoint, system datapoints must be linked to a profile. For details about datapoint and
datapoint profile configuration, refer to section 5 DEFINING DATAPOINT). Depending on its
kind, the system datapoint and its relevant profile have specific attributes to be set correctly
to insure healthy behaviour of computer. Hereafter, are listed the datapoint and profile
requirements for each kind of system datapoint.
Generally system datapoints are automatically addressed in IEC-61850 mapping of the
relevant computer at their creation. If manual addressing is necessary, it is stressed in
following sections by given the associated available data object of a given computer brick in
LD0 (⇔<brick name>.<data object name>). For details about SBUS addressing see section
4.5 Networking computer on the station-bus network.
(2)
(4)
(3)
(5)
(1)
FIGURE 107: ‘SYSTEM INFOS’ BINDERS FOR A COMPUTER

4.10.1 Setting general system information of a computer

When creating a computer, the following mandatory datapoints are implicitly added.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
FIGURE 108: MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR A COMPUTER

These datapoints must be configured (see section 5 DEFINING DATAPOINT) according to
their described features:
• Controls and statuses for functioning mode
− Mode control DPC (9): this datapoint is only used by the SMT to turn device
functioning mode to Maintenance or Operational/Run.
The available states of this datapoint are:
“OPEN” for the Maintenance mode
“CLOSED” for Operational mode
An IEC address for this datapoint is defined by using SBUS automatic addressing.
− Operating mode MPS (10): this datapoint is the MPS equivalence of Device mode
DPS (4).
“STATE 0” for the Faulty mode
“STATE 1” for Operational mode
“STATE 3” for Test mode
“STATE 5” for Maintenance mode
− Test control DPC (18): this datapoint is only used by the SMT to turn device
functioning mode to Test or Normal.
“OPEN” for the Test mode
“CLOSED” for Normal mode
This datapoint has no IEC-61850 address
• Control and status for local/remote
− Local/remote ctrl DPC (5): this datapoint is required by IEC-61850 protocol but is
meaningless for the computer.
“OPEN” for Remote
“CLOSED” for Local
This datapoint has no IEC address
− Local/remote DPS (6):
“OPEN” for Remote
“CLOSED” for Local
− Local/remote SPS (7):
“RESET” for Local mode
“SET” for Remote mode
This datapoint has the "RESET" state if the Local/remore DPS datapoint of all the
bays managed by the computer have the "OPEN" state and has the "SET" state if
at least the Local/remore DPS datapoint of one bay managed by the computer has
not the "OPEN" state.
The IEC-61850 address of this datapoint is defined by using SBUS automatic
addressing.
• Control and status for database management
− Database incoherency SPS (1): this datapoint is put in ‘SET’ state if current
database is not self-consistent. In that case, computer enters the Maintenance
mode.
“RESET” for coherent database
“SET” for incoherent database
− Database switch control SPC (2): this datapoint is only used by the SMT to turn
device functioning mode to Maintenance or Operational/Run.
The available state of this datapoint is:
“ON” for Switch
• Synchronisation status
− Synchronisation SPS (17): this is put in ‘SET’ state if device is synchronised.

“RESET” for not synchronised device
“SET” for synchronised device
An IEC-61850 address for this datapoint is defined by using SBUS automatic
addressing.
• Communication status
− Device link SPS (3): although this datapoint is under the computer, it is not
managed by it. Each IEC-61850 client of the computer computes locally this
datapoint status by supervising the IEC-61850 real-time link with the computer. In
fact, there are as many ‘Device link SPS’ per computer basis as IEC-61850 clients
connected to the computer. Is put in ‘SET’ state if device link is operational.
“RESET” for not OK
“SET” for OK
This datapoint has no IEC address
• Health statuses
− DI acquisition stopped SPS (4): in case of saturation of the internal file used for
acquisition of wired digital inputs and gooses, acquisition is automatically stopped
and this datapoint is put in ‘SET’ state. As soon as this internal file is un-saturated,
this datapoint is reset and acquisition restarts.
“RESET” for acquisition running
“SET” for acquisition stopped
addressing.
− Software error SPS (16): in case of software error, this datapoint is set and
computer enters the Faulty mode.
“RESET” for software running
“SET” for software error
− Watchdog SPS (19): in case of software watchdog time-out, this datapoint is put in
‘SET’ state and computer enters the Faulty mode.
“RESET” for watchdog OK
“SET” for watchdog time-out
− ISaGRAF status MPS (20):

“STATE 0”: Isagraf is running normally
“STATE 1”: Not activated
“STATE 2”: Cycle too long
“STATE 3”: Queue overflow (Isagraf queue has reached overflow limit)
“STATE 4”: An Isafraf POU (Program Organisation Unit) is faulty
addressing.
• Control and statuses for redundancy management:
The four following datapoints are used internally by computer if it is redunded. These
datapoints must be linked to datapoint profiles by default for proper behaviour of
redundancy.
− Redundancy change mode SPS (11)

− Redundancy change status SPS (12)
− Redundancy mode control SPC (13)
− Redundancy status control SPC (14)
These datapoints have no IEC-61850 address.
− Main status MV (8)

addressing.
At computer level, the following optional datapoint can be added.
(21)
(22)
(23)
(24)
FIGURE 109: OPTIONAL ‘SYSTEM INFOS’ DATAPOINTS FOR A COMPUTER

− Counter Top SPS (21): this datapoint is used to launch the transmission of
counters value on IEC-61850 and SCADA networks. Launching is done when the
datapoint goes in ‘SET’ state. This datapoint is generally wired.
“RESET” for no transmission
“SET” for transmission
An IEC-61850 address can be manually added to this datapoint.
− DREC ready SPS (22): this datapoint indicates the availability of a waveform
record file for the computer (for details, refer to section 4.8 Defining wave record
file management).
“RESET” for no waveform record available
“SET” for waveform record file available
addressing.
− External clock status SPS (23): this datapoint indicates the status of the IRIG-B
synchronisation. This datapoint is mandatory if ‘synchronisation source’ attribute at
computer level is set to IRIG-B (for details, refer to section 4.3 Setting general
attributes of a computer). The available states of this datapoint are:
“SET” for lack of IRIG-B signal
“RESET” for IRIG-B signal is present
An IEC-61850 address can be manually added to this datapoint.
− Device mode DPS (24): this datapoint gives the current functioning mode of the
computer.
“JAMMED” for the Test mode
"OPEN" for the Maintenance mode
"CLOSED" for the Operational mode
“UNDEFINED” for the Operational mode
This datapoint has no IEC-61850 address.
4.10.2 Setting system information of board

When creating a board (except CPU board) the following mandatory datapoint is implicitly
added.
(1)
FIGURE 110: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A BOARD

(E.G. FOR AIU BOARD)
− Board status MPS (1): this datapoint indicates the status of the board. Addressing
this datapoint can be done:
1) by using SBUS automatic addressing.
FIGURE 111: AUTOMATIC IEC ADDRESSING OF A BOARD STATUS DATAPOINT

2) Manually. In that case, the relevant data object given the IEC address of the
status, must be coherent with the board number (e.g. if AIU board number is 3,
corresponding data object is AIUSt3).
“STATE 0” for board OK
“STATE 1” for self-check failure
“STATE 2” for configured but missing
“STATE 3” for not configured but present
“STATE 4” for board not present
FIGURE 112: MANUAL IEC ADDRESSING OF A BOARD STATUS DATAPOINT

4.10.3 Setting system information of legacy IED

When creating a legacy IED, the following mandatory datapoints are implicitly added.
(1)
(2)
FIGURE 113: MANDATORY ‘SYSTEM INFOS’ DATAPOINTS FOR A LEGACY IED

− IED communication status SPS (1): is put in ‘SET’ state if communication with the
IED is operational.
“RESET” for communication not OK
“SET” for communication OK
− IED synchronisation status SPS (2): is put in ‘SET’ state if IED is synchronised.
“RESET” for IED not synchronised
“SET” for IED synchronised
At IED level, the following optional datapoint can be added.
(3)
FIGURE 114: OPTIONAL ‘SYSTEM INFOS’ DATAPOINT FOR A LEGACY IED
− IED disturbance status SPS (2): this datapoint indicates the availability of a
disturbance file for the IED (for details, refer to section 4.8.1 Defining management of
disturbance file for IED). This datapoint is put in ‘SET’ state if a disturbance file is
available.
“RESET” for no disturbance file available
“SET” for disturbance file available
4.10.4 Setting system information of serial printer

When creating a serial printer, the following mandatory datapoint is implicitly added.
(1)
FIGURE 115: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A SERIAL PRINTER
− Printer status MPS (1): this datapoint indicates the status of the printer.
“STATE 0” for printer OK
“STATE 1” for self-check failure
“STATE 4” for printer not present
4.10.5 Setting system information of a SCADA network

When creating a SCADA network, the following mandatory datapoints are implicitly added.
(2)
(1)
FIGURE 116: MANDATORY ‘SYSTEM INFOS’ DATAPOINT FOR A SCADA NETWORK
− SCADA communication status SPS (1): this datapoint is put in “SET” state if
communication with the SCADA is operational.
“RESET” for communication with the SCADA not OK
“SET” for communication with the SCADA OK
− SCADA redundancy status SPS (2): this datapoint is put in “SET” state if
redundancy with the SCADA is active.
“RESET” for standby
“SET” for active
5. DEFINING DATAPOINT
5.1 Creating a datapoint
Electrical and system topologies share entities called datapoints. A datapoint corresponds to
an atomic object with real-time value, status or control relevant to electrical or system
process. Moreover, datapoints support extra system functions like forcing, suppression,
filtering, and alarms, logging.
Several kinds of datapoint exist:
• Input datapoints used for supervision:
− SPS (Single Point Status), DPS (Double Point Status), MPS (Multiple Point
Status)
− MV (Measurement Value), Counter
• Output datapoints used for control:
− SPC (Single Point Control), DPC (Double Point Control)

− Setpoint
Input datapoints can be acquired through sensors (input channels), addressed on IED at IED
legacy network level or substation network level. They can also be calculated or deduced by
the system devices. They can be sent to SCADA by addressing them on SCADA networks.
Output datapoints can be controlled through relays (output channels), addressed on IED at
IED legacy network level or substation network level or on SCADA networks. They can also
be managed by built-in functions or user functions.
At SCE level, datapoints belonging to the system topology are called system datapoints, and
those of the electrical topology are named 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 datapoint used by
redundancy and more often 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
PACiS system behaviour (for instance, ‘Order running SPS’ at bay level, ‘Computed
switchgear position’ at circuit-break level), or relevant to an electrical built-in function that
imposes their existence.
Be careful:
(Refer to section 4.5.1 Connecting computer to others station-bus sub-systems, for Client /
Server definition).
In the set of all the computers of a SCS, the previous described SPS attributes (except short
name and long name) are only useful and given to the computer that serves the datapoint
because the relevant functions are always done at computer server level.
5.1.1 Overview of binary input processing
Binary input processing is described in section 5.1 of chapter C264/EN FT
By extension, at SCE level:
• System inputs (SI) are seen as particular SPS, DPS or MPS depending on the number
of elementary information they represents (for details about SI, see section4.10
Setting system information for computer components).
• Group binary input is seen as particular SPS.

5.1.2 Defining a SPS datapoint

5.1.2.1 SPS processing
Processing of a SPS is described in section 5.1.2 of chapter C264/EN FT.
5.1.2.2 Creating a SPS datapoint
To create a SPS datapoint:
• Add a SPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of SPS exist. They are
used for specific needs at electrical topology level (for details see relevant section in 6
DEFINING COMPUTER CONFIGURATION IN ELECTRICAL ARCHITECTURE) or
system topology level (for details see section 4.10 Setting system information for
computer components).
• Update the SPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPS.
• Update its relation ‘has for profile’ to point to a specific existing profile (2). See section
5.2 Linking a datapoint to a profile, for details about profile definition and setting.
(1)
FIGURE 117: ADDING A SPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
(2)
FIGURE 118: LINKING A SPS DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
Updating SPS attributes (description for generic SPS)

When adding a generic SPS datapoint, some general attributes must be updated:
1. short name and long name of the datapoint used for logging, alarms ...
2. detection mode (Permanent / Transient / Permanent with computer auto-reset): when
this attribute is set to "Permanent with computer auto-reset" the SPS is reset
automatically after 1 ms.
3. stable state time reference (Start of filtering / End of filtering)
4. reset confirmation delay (range [0 s, 120 s], step 100 ms]: confirmation delay for
stable ‘reset’ state.
5. set confirmation delay (range [0 s, 120 s], step 100 ms]: confirmation delay for
stable ‘set’ state.
6. forcing management (Not automatic / Automatic to reset state / Automatic to set
state): when a SPS goes in invalid state, computer can force or not its status to set or
reset state automatically. This attribute defines the way this forcing management is
done. Automatic forcing management is independent of FSS facility gives at user by
the SPS profile.
7. state panel assignment (No / Yes): set to ‘yes’ to enable SPS state display at
computer local HMI level.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 119: SETTING GENERAL ATTRIBUTES OF A SPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPS)
5.1.3 Defining a DPS datapoint

5.1.3.1 DPS processing
Processing of a DPS is described in section 5.1.3 of chapter C264/EN FT.
5.1.3.2 Creating a DPS datapoint
To create a DPS datapoint:
• Add a DPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of DPS exist. They are
• Update the DPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPS.
(1)
FIGURE 120: ADDING A DPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPS)
(2)
FIGURE 121: LINKING DPS DATAPOINT TO ITS PROFILE

Updating DPS attributes (description for generic DPS)

When adding a generic DPS datapoint, some general attributes must be updated:
2. stable state time reference ( Start motion / End motion): this attribute defines the
time reference for a stable state: at start of motion filtering or end of motion filtering
3. complementary delay jammed (range [0 s, 60 s), step 100 ms): this attribute defines
the delay for the MOTION00 (JAMMED) state filtering. It corresponds to parameter T00
mentioned in § 5.1.3.1 of chapter C264/EN FT
4. complementary delay undefined (range [0 s, 60 s), step 100 ms): this attribute
defines the delay for the MOTION11 (UNDEFINED) state filtering. It corresponds to
parameter T11 mentioned in § 5.1.3.1 of chapter C264/EN FT
5. open confirmation delay (range [0 s, 60 s), step 100 ms): this attribute defines the
confirmation delay for the OPEN state. It corresponds to parameter TO mentioned in §
5.1.3.2 of chapter C264/EN FT
6. closed confirmation delay (range [0 s, 60 s), step 100 ms): this attribute defines the
confirmation delay for the CLOSE state. It corresponds to parameter TC mentioned in
§ 5.1.3.2 of chapter C264/EN FT
7. forcing management (Not automatic / Automatic to reset state / Automatic to set
state): when a DPS is in an invalid state, the computer can force or not its status to set
or reset state automatically. This attribute defines the way this forcing management is
done. Automatic forcing management is independent of FSS facility given to the user
by the DPS profile.
8. state panel assignment (No / Yes): set to ‘yes’ to enable the display of the DPS state
at the computer local HMI level.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 122: SETTING GENERAL ATTRIBUTES OF A DPS DATAPOINT

5.1.4 Defining a MPS datapoint

5.1.4.1 MPS processing
Processing of a MPS is described in section 5.1.4 of chapter C264/EN FT.
5.1.4.2 Creating a MPS datapoint
To create a MPS datapoint:
• Add a MPS from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of MPS exist. They are
• Update the MPS attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of MPS.
(1)
FIGURE 123: ADDING A MPS DATAPOINT (SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
(2)
FIGURE 124: LINKING MPS DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
-Updating MPS attributes (description for generic MPS)

When adding a generic MPS datapoint, some general attributes must be updated:
2. filtering delay (range [0 s, 6553,5 s), step 10 ms).
3. inhibition delay (range [0 s, 6553,5 s), step 10 ms).
4. forcing management (Not automatic / Automatic to state (i ∈ [0, 15])): when a
MPS goes in invalid state, computer can force or not its status to set or reset state
automatically. This attribute defines the way this forcing management is done.
Automatic forcing management is independent of FSS facility gives at user by the
MPS profile.
5. state panel assignment (No / Yes): set to ‘yes’ to enable MPS state display at
(1)
(2)
(3)
(4)
(5)
FIGURE 125: SETTING GENERAL ATTRIBUTES OF A MPS DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MPS)
5.1.5 Overview of measurement processing

Processing of a measurement is described in section 5.2 of chapter C264/EN FT.
Features of digital measurements are described in section 4.6 of chapter C264/EN FT.
5.1.5.1 Analogue measurement acquisition
Analogue measurements are acquired via input analogue channel (AI) of AIU board. These
AI are voltage or current DC signals (only current for AIU210 board) delivered by
transducers, and representing an external value.
Input characteristics
The saturation value, for each range, is the following:
Range Saturation values

± 10 V -12.6 V / +12.6 V
±5V -6.3 V / +6.3 V
± 2.5 V -3.2 V / +3.2 V
± 1.25 V -1.26 V / +1.26 V
0 - 1 mA 1.26 mA
± 1 mA -1.26 mA / +1.26 mA
0 – 5 mA 6.3 mA
± 5 mA -6.3 mA / +6.3 mA
0 – 10 mA 12.5 mA
± 10 mA -12.5 mA / +12.5 mA
0 – 20 mA 25 mA
± 20 mA -25 mA / +25 mA
4-20 mA 26 mA
Acquisition
Acquisition cycle
The analogue inputs are acquired on a periodical basis. Each channel on a board can be
assigned one of these cycles independently of the others channels (see section 4.4.5
Configuring an AI channel).
There exists two acquisition cycles:
− a short cycle (Nsc x 100 ms, Nsc configurable from 1 to 10 with a default value of 1).
− a long cycle (Nlc x 500 ms, Nlc configurable from 1 to 20, with a default value of 2).
AD conversion
The Analogue to Digital Converter has a 16 bits resolution (15 bits + sign bit).
The zero offset value is computed by the conversion of a 0 V voltage reference.
The gain is adjusted automatically by software by connecting a known voltage reference to
the amplifier.
The zero offset values and the gain are adjusted regularly in order to compensate for the
deviations caused by variations of temperature and ageing.
Self-checks
Two two kinds of self-checks are performed:
• the board address coherency
• the complementarity control of the measured value

These self-checks are performed at each scan (defined during the configuration phase).
Time tagging
An AI is time stamped with the date/time of the scanned value.
5.1.5.2 Adding a MV datapoint
To create a MV datapoint:
• Add a MV from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of MV exist. They are
• Update the MV attributes (see following sections); some attributes can be fixed or
masked depending on the pre-defined kind of MV.
(1)
FIGURE 126: ADDING A MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC MV)
(2)
FIGURE 127: LINKING A MV DATAPOINT TO ITS PROFILE

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC MV)
5.1.5.3 Setting ‘General’ attributes of a MV datapoint

When adding a generic MV datapoint, some general attributes must be updated:
1. short name and long name: used for logging, alarms ...
2. type: available values are:
− Analogue (used for analogue acquisition, IED acquisition, CT/VT calculation or

system input)
− Digital coded ‘BCD’ (only used for digital acquisition)
− Digital coded ‘pure binary’ (only used for digital acquisition)
− Digital coded ‘gray’ (only used for digital acquisition)
− Digital coded ‘1 among n’ (only used for digital acquisition)
− Digital coded ‘decimal’ (only used for digital acquisition)
For details about digital encoding see section 4.6.3 of chapter C264/EN FT.
3. IDRC: not significant
4. automatic forcing (No / Yes): when a MV goes in invalid state, computer can force or
not its value automatically. Automatic forcing management is independent of FSS
facility gives at user by the MV profile.
5. value for automatic forcing: MV value when automatic forcing
6. transmission on event (Cyclic long period / Cyclic short period / According to a ‰ of
full scale value / According to a ‰ of current value)
7. deadband (‰ variation) (range [0,255], step 1): this attribute is significant only if the
previous parameter is set to ‘According to a ‰ of ...’: this attribute corresponds to ‘p’
parameter described in section 5.2.9.2 of chapter C264/EN FT.
8. MV panel assignment (No / Yes): set to ‘yes’ to enable MV value displayed at
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 128: SETTING GENERAL ATTRIBUTES OF A MV DATAPOINT

5.1.5.4 Setting ‘Value features’ attributes of a MV datapoint

When adding a generic MV datapoint, some ‘Value features’ attributes must be updated:
1. minimum value (range [-3.4e38, 3.4e38]: used for full scale calculation and scaling
2. maximum value (range [-3.4e38, 3.4e38]: used for full scale calculation and scaling.
(Full scale = maximum value - minimum value)
3. zero value suppression (% of full scale value) (range [0,10], step 0.1): this parameter
is used to define the zero suppression area for the zero value suppression processing
(refer to section 5.2.3 of chapter C264/EN FT for details)
4. Hysteresis used for threshold detection (see section 5.2.4 of chapter C264/EN FT for
details)
For each available threshold (see section 5.2.4 of chapter C264/EN FT for details):
5. Threshold usage (No / Yes)
6. Threshold value
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 129: SETTING VALUE FEATURES ATTRIBUTES TO MV DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC MV)
5.1.5.5 Setting ‘Scaling’ attributes of a MV datapoint
When adding a generic MV datapoint, some ‘Scaling’ attributes must be updated:
1. scaling rule: available values are (see section 5.2.2 of chapter C264/EN FT for
details):
− Linear
− Quadratic
− Quadratic with offset
− Linear per pieces
2. minimum acq. value (used for scaling)
3. maximum acq. value (used for scaling)
In case of multi-segment scaling:

4. Ai coefficient
5. Bi coefficient
(1)
(2)
(3)
(4)
(5)
FIGURE 130: SETTING SCALING ATTRIBUTES OF A MV DATAPOINT

5.1.6 Defining a TPI datapoint

5.1.6.1 Overview of Tap Position Indicator processing
Tap Position Indicator (TPI) is described section 5.3 of chapter C264/EN FT
Tap Position Indicator (TPI) must be seen as MV with specific features:
• Its value is an integer in the range [1..64],
• Acquisition can be done via AI channel of AIU board.
• Acquisition can be done on digital channels of DIU board (up to 64 DI channels). In

that case, available digital MV type are: Decimal, Gray, BCD or ‘1 among n’
5.1.6.2 Adding a TPI datapoint
TPI datapoint is automatically created when adding a tap changer built-in function under a
mandatory transformer module of a transformer bay. For details about transformer bay,
module or tap changer function creation see section 6 DEFINING COMPUTER
CONFIGURATION IN ELECTRICAL ARCHITECTURE.
Once a TPI has been created by adding a tap changer built-in function (1):
• Update the TPI attributes (see following sections).
• Update its relation ‘has for profile’ to point to a specific existing MV profile (2). See
section 5.2 Linking a datapoint to a profile, for details about profile definition and
setting.
Bay transformer
Mandatory transformer module
(1) Tap changer built-in function
Mandatory TPI
C0191ENb
FIGURE 131: AUTOMATIC TPI CREATION FOR TAP-CHANGER BUILT-IN FUNCTION
(2)
FIGURE 132: LINKING TPI DATAPOINT TO ITS PROFILE

5.1.6.3 Setting ‘General’ attributes of a TPI datapoint

For a TPI datapoint, some general attributes, similar to MV attributes, must be updated:
2. type: available values are:
− Analogue tap position

− Digital tap position coded ‘1 among N’ (only used for digital acquisition)
− Digital tap position coded ‘decimal’ (only used for digital acquisition)
− Digital tap position coded ‘gray’ (only used for digital acquisition)
− Digital tap position coded ‘BCD’ (only used for digital acquisition)
For details about digital encoding see section 4.6.3 of chapter C264/EN FT.
3. MV panel assignment (No / Yes): set to ‘yes’ to enable MV value display at computer
local HMI level.
(1)
(2)
(3)
FIGURE 133: SETTING GENERAL ATTRIBUTES OF A TPI DATAPOINT

5.1.6.4 Setting ‘Value features’ attributes of a TPI datapoint
Refer to section 5.1.5.4 Setting ‘Value features’ attributes of a MV datapoint
• The following constraint between the two attributes must be respected :

("maximum value" − "minimum value" + 1) ∈ [1..64]
5.1.6.5 Setting ‘Tap position’ attributes of a TPI datapoint
For a TPI datapoint, some specific attributes must be updated:
1. Filtering delay (range [0 , 655,35 s], step 10 ms):
− for digital TPI, corresponds to Tstab of digital measurement

(Refer to section 4.6 of chapter C264/EN FT for attribute meaning)
− for analog TPI, corresponds to a delay to filter transient UNDEFINED state (delay
to confirm UNDEFINED state)
2. current valid range (% maximum value) (range [0 , 20 %], step 1 %): only used for
analogue TPI corresponds to N parameter described in section 5.3 of chapter
C264/EN FT.
(1)
(2)
FIGURE 134: SETTING TAP POSITION ATTRIBUTES OF A TPI DATAPOINT

5.1.6.6 Setting ‘Scaling’ attributes of a TPI datapoint
For an analogue TPI datapoint, some ‘Scaling’ attributes appears and must be updated:
1. minimum acq. value: corresponds to Imin parameter described in section 5.3.2 of
chapter C264/EN FT.
2. maximum acq. value: corresponds to Imax parameter described in section 5.3 of
chapter C264/EN FT.
(1)
(2)
FIGURE 135: SETTING SCALING ATTRIBUTES OF A TPI DATAPOINT

5.1.7 Defining a Counter datapoint

5.1.7.1 Overview of counter processing
Single counters and double counters are described in section §4.5 of chapter C264/EN FT.
Continuous register Scaling

From counters
acquisition
+
+1
Accumulator Transmission
= To RCP
To HMI
To archive
Periodic register Scaling To automation
in
24h - FIFO
C0195ENa
FIGURE 136: COUNTER PROCESSING
• The accumulator is incremented at each valid counter pulse.
• The periodic register is used to store the accumulator value of the previous period.
• The continuous register is used to store the accumulator value since the origin.
• The FIFO memory is used to store the periodic register of each period (up to 16
counters), during 24h.
Periodic processing
A period is defined either:
• By an external pulse on a digital input.
• By the internal clock : the period length is settable : 10', 15', 30', 1h to 24h , each
period begins at a regular hour: 12:00 , 12:30 , 13:00 ...
This choice is defined during the configuration phase on a per computer basis. The period
delimiter is also defined at configuration time for each counter.
At each period:
• The content of the accumulator is added to the continuous register.
• The content of the accumulator is transferred to the periodic register.
• The content of the periodic register is inserted into the FIFO queue.
• The accumulator is reset to 0 (a pending pulse is not lost ).
• Either the continuous register or the periodic register is transmitted. The choice is
made by configuration on a per accumulator basis.
If the chosen transmitted register reaches its maximum value (232), the counter status is set
to OVERRANGE. Only a counter modification can re-validate the counter.
Scaling
Scaling is used for printing or displaying a counter. EPI is a parameter giving the amount of
energy in KW-h or KVAR-h equivalent to a pulse. The displayed value is:
N x EPI KW-h
Where N is the value of a counter.
Counter resulting states
The state of a counter can be :
State Comment
VALID not in one of the below states
SELFCHECK Due to the SELFCHECK FAULTY of the DI
FAULTY
UNKNOWN If the counter is acquired via a transmission link, the
information is unknown when the link is disconnected.
UNDEFINED Due to a counting failure of DCT (non-complementarity of
the 2 contacts)
OVERRANGE when the maximum value is reached
Transmission
The counters are transmitted on a client-server basis on the IEC-61850 network using the
report mechanism.
During a loss of communication between a client and a server, all server counters are set to
UNKNOWN on the client.
The counter informations transmitted in a report are:
• the number of pulses (i.e. accumulator value before scaling).
• the real value.
• the time stamping (in GMT time) and time quality.
• the resulting state (mapped on the quality field on IEC-61850).
• the reason for change, which could be one of the following values :
− cyclic change (set if the value has changed)

− change of quality (set if the quality has changed)
− change due to control (set if the value or quality change is due to a control)
Counter modification
When an accumulator value is modified, the request is immediately taken into account. The
continuous register is set with the accumulator value.
The modification could be a reset of the counter.
5.1.7.2 Adding a Counter datapoint
To create a Counter datapoint:
• Add a Counter from object entry available at the wished system or electrical object
level (1). Depending on the object level, different pre-defined kinds of counter exist.
They are used for specific needs at electrical topology level (for details see relevant
section in 6 DEFINING COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see section 4.10 Setting
system information for computer components).
• Update the Counter attributes (see following sections).

(1)
FIGURE 137: ADDING A COUNTER DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC COUNTER)
(2)
FIGURE 138: LINKING COUNTER DATAPOINT TO ITS PROFILE

5.1.7.3 Setting ‘General’ attributes of a Counter datapoint
When adding a generic Counter datapoint, some general attributes must be updated:
2. counter type (Standard, Energy import, Energy export): when this attribute is set to
"Standard" associated attributes are Validation duration (3), Invalidity duration (4), IED
value already totalled (5), Cumul period (6) and Reset at cumulative period (7). When
this attribute is set to Energy import or Energy export associated attributes are energy
type (9), Scale factor (10), Transmission period (11) and reset after transmission (12).
3. validation duration (range [0, 10 s], step 1 ms): corresponds to Tcount parameter
described in section 4.5 of chapter C264/EN FT.
4. invalidity duration (range [5, 10 s], step 1 ms): corresponds to Tdef parameter
described in section 4.5 of chapter C264/EN FT.
5. IED value already totalled (No / Yes): attribute must be set to Yes if counter value
acquired on IED must not be totalled periodically (total done at IED level)
6. cumul period (10 mn / 15 mn / 30 mn / N h (N ∈ [1, 24])): corresponds to period

length of internal clock parameter described in section1.
7. reset at cumulative period (No / Yes): when set to ‘Yes’ that the way to transmit the
periodic register, if not the cumulative register is transmitted.
8. MV panel assignment (No / Yes): set to ‘yes’ to enable Counter value display at
9. scale factor.
10. energy type (Activ energy, Reactiv energy).
11. transmission period (10 mn / 15 mn / 30 mn / N h (N ∈ [1, 24])).

12. reset after transmission (No, Yes).
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
FIGURE 139: SETTING GENERAL ATTRIBUTES OF A COUNTER DATAPOINT

5.1.8 Overview of control sequence processing

This section is an introduction to SPC, DPC and SetPoint datapoint definition. It deals with
general control sequence and features associated to these kinds of datapoints, for better
comprehension of their configuration.
There are four types of Binary outputs:
• Single Point Status (SPC): derived from one Digital output.
• Double Point Status (DPC): derived from two Digital outputs.
• System output: control information related to the system, to configurable and built-in
automations or to electrical process but without acquisition possibilities.
• Setpoint (SetPoint): derived from n Digital outputs.

SPC, DPC and SetPoints are mainly controlled via digital output boards (DOU board) or via
IEDs connected by a serial link (for details see section 5.6).
By extension, at SCE level, system outputs are seen as particular SPC or DPC depending
on the number of elementary information they represent (for details about system outputs,
see section 4.10 Setting system information for computer components).
Control sequences are described in section 6 of chapter C264/EN FT (Functional
Description).
5.1.9 Defining a SPC datapoint
To create a SPC datapoint:
• Add a SPC from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of SPC exist. They are
• Update the SPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SPC.
(1)
FIGURE 140: ADDING A SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SPC)
(2)
FIGURE 141: LINKING A SPC DATAPOINT TO ITS PROFILE

5.1.9.1 Setting ‘General’ attributes of a SPC datapoint
When adding a generic SPC datapoint, some general attributes must be updated:
2. activation mode (Permanent / Transient / Permanent until feedback).
3. order on duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the contact is closed
before re-opening.
4. hold duration (range [0, 10 s], step 10ms): this attribute is only available if the
activation mode is set to Permanent until feedback. It defines the time while the
contact is held in the requested position after reception of the confirmation of the
position of the device.
5. time between two orders (range [0, 10 s], step 100ms): this attribute corresponds to
the inter-control delay defined in section 6.1.6.1 of chapter C264/EN FT and use also
used for execution checks (see section 6.1.8 of chapter C264/EN FT).
6. command panel assignment (No / Yes): set to ‘yes’ to enable SPC control at
(1)
(2)
(5)
(6)
(1)
(2)
(3)
(5)
(6)
(1)
(2)
(4)
(5)
(6)
FIGURE 142: SETTING GENERAL ATTRIBUTES OF A SPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC SPC)
5.1.9.2 Setting ‘Dependencies’ attributes of a SPC datapoint
When adding a generic SPC datapoint, some ‘dependencies’ attributes must be updated,
that correspond to:
• substation and bay mode controls and bay uniqueness control defined in section 6.1.6
of chapter C264/EN FT and use also for execution checks (see section 6.1.8 of
chapter C264/EN FT), if SPC datapoint is located under a bay.
• substation mode control and substation uniqueness control, if SPC level is higher than
bay level.
Substation/Bay control uniqueness is globally set at substation level (see section 6.1.2
Defining a Substation). When substation uniqueness is set, bay uniqueness is implicitly set
for all bays.
Dependencies for SPC level lower than or equal to bay level

1. Substation mode dependency (No / Yes).
2. bay mode dependency (No / Yes).
3. SBMC mode dependency (No / Yes).
4. bay control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to bay at substation level.
(1)
(2)
(3)
(4)
FIGURE 143: SETTING DEPENDENCIES ATTRIBUTES OF A SPC DATAPOINT

Dependencies for SPC level higher than bay level
1. Substation mode dependency (No / Yes)
2. Substation control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to substation at substation level.
(1)
(2)
FIGURE 144: SETTING DEPENDENCIES ATTRIBUTES OF A SPC DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC SPC)
5.1.9.3 Defining a SPC feedback
For correct execution behaviour and control acknowledgement, a SPC datapoint can be
linked to a SPS or DPS datapoint that corresponds to a feedback. For instance a circuit-
breaker control SPC is linked to the circuit-breaker status DPS.
To define a SPC feedback:
− Add the relation ‘has for feedback’ at SPC level: choose exclusively one of the two
relations ‘has for feedback: SPS datapoint’ (1) or ‘has for feedback: DPS datapoint’ (2)
depending on the kind of feedback datapoint.
− Fill the relation with the relevant SPS or DPS datapoint.
− If necessary update the relation attributes:

(1)
(2)
FIGURE 145: DEFINING SPC FEEDBACK

3. execution time-out (range [0, 6000 s], step 100 ms): in this given delay, feedback
must change relatively to the control. If not, a negative acknowledgement is sent for
the control (for details see section 5.1.8 Overview of control sequence processing).
4. status check for command (No check / Control authorized only if the device is in the
opposite state / Control authorized only if the device is in the opposite state, jammed
or undefined / Control refused if the device is in the same state) : this attribute
corresponds to the ‘current status check for the device’ described in section 6.1.6.8 of
chapter C264/EN FT and used also for execution checks (see section 6.1.8 of chapter
C264/EN FT).
(3)
(4)
FIGURE 146: SETTING ATTRIBUTES OF A SPC FEEDBACK RELATION

• For each "SPC", two relations "has for feedback" are available, but they are mutually
exclusive
• A datapoint and its feedback datapoint must comply with the following rules :
- both must have the same Server device
- if one of them is a "Wired" datapoint, the other one must be "Wired" too (Here, the
term "Wired" means that the datapoint is linked to a digital or analog channel of a
computer, or linked to an IED address, else it's "System")
- if one of them is a "System" datapoint, the other one must be "System" too.
- if one of them is linked to an "UCA2/IEC gen IED" through the relation "has for
UCA2/IEC address", this relation must also be defined for the other one
• For a "SPC" datapoint, if its attribute "activation mode" is set to the "Transient" value,
then the following rule must be respected:
"execution timeout" > "order on duration"
5.1.10 Defining a DPC datapoint

To create a DPC datapoint:
• Add a DPC from object entry available at the wished system or electrical object level
(1). Depending on the object level, different pre-defined kinds of DPC exist. They are
• Update the DPC attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of DPC.
5.2.7, for details about profile definition and setting.
(1)
FIGURE 147: ADDING A DPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC DPC)
(2)
FIGURE 148: LINKING A DPC DATAPOINT TO ITS PROFILE

5.1.10.1 Setting ‘General’ attributes of a DPC datapoint
When adding a generic DPC datapoint, some general attributes must be updated:
2. activation mode (Permanent / Transient / Permanent until feedback).
3. close duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the DPC is held in the
"close" state before returning to the "open" state.
4. open duration (range [0, 15 s], step 10ms): this attribute is only available if the
activation mode is set to Transient. It defines the time while the DPC is held in the
"open" state before returning to the "close" state.
5. hold duration (range [0, 10 s], step 10ms): this attribute is only available if the
activation mode is set to Permanent until feedback. It defines the time while the
contact is held in the requested state after reception of the confirmation of the position
of the device.
6. time between two orders (range [0, 10 s], step 100ms): this attribute corresponds to
the inter-control delay defined in section 6.1.6.1 of chapter C264/EN FT and use also
used for execution checks (see section 6.1.8 of chapter C264/EN FT).
7. command panel assignment (No / Yes): set to ‘Yes’ to enable SPC control at
(1)
(2)
(6)
(7)
(1)
(2)
(3)
(4)
(6)
(7)
(1)
(2)
(5)
(6)
(7)
FIGURE 149: SETTING GENERAL ATTRIBUTES OF A DPC DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR A GENERIC DPC)
5.1.10.2 Setting ‘Dependencies’ attributes of a DPC datapoint

When adding a generic DPC datapoint, some ‘dependencies’ attributes must be updated,
that correspond to:
• substation and bay mode controls and bay uniqueness control (defined in section
6.1.6 of chapter C264/EN FT) and also used for execution checks if DPC datapoint is
located under a bay.
• substation mode control and substation uniqueness control, if DPC level is higher than
bay level.
for all bays.
Dependencies for DPC level lower than or equal to bay level
(1)
(2)
(3)
(4)
FIGURE 150: SETTING DEPENDENCIES ATTRIBUTES OF A DPC DATAPOINT

Dependencies for DPC level higher than bay level
1. substation mode dependency (No / Yes).
2. substation control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to substation at substation level.
(1)
(2)
FIGURE 151: SETTING DEPENDENCIES ATTRIBUTES OF A DPC DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC DPC)
5.1.10.3 Defining a DPC feedback

For correct execution behaviour and control acknowledgement, a DPC datapoint can be
linked to a SPS or DPS datapoint that corresponds to a feedback. For instance a circuit-
breaker control DPC is linked to the circuit-breaker status DPS.
To define a DPC feedback:
• Add the relation ‘has for feedback’ at DPC level: choose exclusively one of the two
relations ‘has for feedback: SPS datapoint’ (1) or ‘has for feedback: DPS datapoint’ (2)
depending on the kind of feedback datapoint.
• Fill the relation with the relevant SPS or DPS datapoint.
• If necessary update the relation attributes:

3. execution timeout (range [0, 6000 s] step 100 ms): in this given delay, feedback
must change relatively to the control. If not, a negative acknowledgement is sent for
the control (for details see section 5.1.8 Overview of control sequence processing).
4. status check for command (No check / Control authorized only if the device is in the
opposite state / Control authorized only if the device is in the opposite state, jemmed
or undefined / Control refused if the device is in the same state) : this attribute
corresponds to the ‘current status check for the device’ described in section 6.1.6.8 of
chapter C264/EN FT and also used for execution checks (see section 6.1.8 of chapter
C264/EN FT).
(1)
(2)
FIGURE 152: DEFINING A DPC FEEDBACK
(3)
(4)
FIGURE 153: SETTING ATTRIBUTES OF A DPC FEEDBACK RELATION

• For each "DPC", two relations "has for feedback" are available, but they are mutually
exclusive
• For a "DPC" datapoint, if its attribute "activation mode" is set to the "Transient" value,
then the following rule must be respected:"execution timeout"> max ["open duration" ,
"close duration" ]
5.1.11 Defining a SetPoint datapoint
5.1.11.1 Overview of SetPoint processing
Digital setpoints are described in section 4.9 of chapter C264/EN FT.
SetPoints are used to send instruction values to the process or to ancillary devices. MiCOM
Computers manage three types of SetPoints:
• Digital SetPoints.
• SetPoints to IEDs.
• System SetPoints.
Digital SetPoints
Digital SetPoints are executed via DO channels of Digital Output boards. This type of
controls is managed in “Direct Execute mode” only.
The checks performed during execution phase for SetPoints are:
• Substation and bay modes: check user selectable.
• Uniqueness : check user selectable.
• Device Locked : check user selectable.
• Automatism running control: check user selectable.

Digital SetPoints may be configured with digital “refresh DO” (see following topic)
The configuration allows also to define two methods of activation of the SetPoint relays:
• Raw activation: all activated relays which must be open are deactivated, all relays
which must be closed are activated. If a “read inhibit DO” is configured this one must
be deactivated during the relay positioning (see following topic).
• Incremental activation: the restitution of the SetPoint and relays can be done by
successive increments from the initial value to the final one. The value of increments
and the duration of the activation are user selectable. If a “read inhibit DO” is
configured this one must be deactivated during every incremental activation (see
following topic).
Digital SetPoint encoding
Described in section 4.9.1 of chapter C264/EN FT.
Read inhibit signal for digital SetPoint

A dedicated binary output can be used to allow or forbid the reading of the value by the
external device.
There is one (or none) read inhibit (RI) output per value.
If the RI output is a logical one (external polarity applied), the reading is permitted.
The procedure used to output a value with a RI output is :
• Reset the RI output to a logical 0 : read forbidden.
• Wait for N ms.
• Output the value.
• Wait for N ms.
• Set the RI output to a logical 1 : read permitted.

The 0 to 1 transition on the RI output can be used by the external device as a trigger,
indicating that a new value is available.
Value
RI
C0210ENa
FIGURE 154 : READ INHIBIT SIGNAL FOR DIGITAL SETPOINT

Refresh DO for digital SetPoint
SetPoints can be configured with a refresh period, this means that the SetPoint request must
be sent periodically by the transmitter.
If a request on the SetPoint is not received before the end of the refresh period, the SetPoint
is set to non-refreshed and an alarm is raised but and the last received SetPoint is
maintained.
Once a new SetPoint request is received, the SetPoint is set to refreshed, DO are activated
and the alarm is reset.
SetPoints to IEDs
SetPoints controls towards IEDs are managed in “Direct execute mode”. Execution phase is
identical to the digital SetPoints. The execution is performed via the communication protocol
of the concerned IED.
System SetPoint
SetPoints can be locally managed by computer as a system control for automation for
instance. Execution phase is identical to the digital SetPoints.
5.1.11.2 Adding a SetPoint datapoint

To create a SetPoint datapoint:
• Add a SetPoint from object entry available at the wished system or electrical object
level (1). Depending on the object level, different pre-defined kinds of SetPoint exist.
They are used for specific needs at electrical topology level (for details see relevant
section in 6 DEFINING COMPUTER CONFIGURATION IN ELECTRICAL
ARCHITECTURE) or system topology level (for details see section 4.10 Setting
system information for computer components).
• Update the SetPoint attributes (see following topic); some attributes can be fixed or
masked depending on the pre-defined kind of SetPoint.
5.2.8 Defining a SetPoint profile, for details about profile definition and setting.
(1)
FIGURE 155: ADDING A SETPOINT DATAPOINT

(SAMPLE GIVEN AT BAY LEVEL FOR GENERIC SETPOINT)
(2)
FIGURE 156: LINKING A SETPOINT DATAPOINT TO ITS PROFILE

5.1.11.3 Setting ‘General’ attributes of a SetPoint datapoint
When adding a generic SetPoint datapoint, some general attributes must be updated:
2. type:
− Analogue: SetPoint is managed by IED or is a system output

− Digital coded BCD
− Digital coded ‘Pure binary’
− Digital coded ‘Gray’

− Digital coded ‘1 among N’
− Digital coded ‘decimal’
For details refer to section 4.9.1 of chapter C264/EN FT.
3. progressive step usage: only used for digital SetPoint. No corresponds to Raw
activation, Yes to Incremental Activation, described in section Defining a SetPoint
datapoint.
4. minimum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
5. maximum value (range [-3.4E38, 3.4E38]): used for value control and scaling.
6. command panel assignment (Yes / No): set to ‘yes’ to enable SetPoint control at
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 157: SETTING GENERAL ATTRIBUTES OF A SETPOINT DATAPOINT

• A Setpoint datapoint wired on DO channels of a computer, must be digital and have its
profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute with SBO
popup”.
5.1.11.4 Setting ‘Dependencies’ attributes of a SetPoint datapoint
When adding a generic SetPoint datapoint, some ‘dependencies’ attributes must be updated,
that correspond to:
• substation and bay mode controls and bay uniqueness control defined in section 6.1.6
of chapter C264/EN FT and use also for execution checks (see section 6.1.8 of
chapter C264/EN FT), if a Setpoint datapoint is located under a bay.
• substation mode control and substation uniqueness control, if SetPoint level is higher
than bay level.
for all bays.
Dependencies for SetPoint level lower than or equal to bay level

(1)
(2)
(3)
(4)
FIGURE 158: SETTING DEPENDENCIES ATTRIBUTES OF A SETPOINT DATAPOINT

Dependencies for SetPoint level higher than bay level
1. substation mode dependency (No / Yes)
2. substation control uniqueness dependency (No / Yes): only significant if control
uniqueness is set to substation at substation level
(1)
(2)
FIGURE 159: SETTING DEPENDENCIES ATTRIBUTES OF A SETPOINT DATAPOINT

(SAMPLE GIVEN AT VOLTAGE LEVEL FOR GENERIC SETPOINT)
5.1.11.5 Defining a SetPoint feedback
For correct execution behaviour and control acknowledgement, a SetPoint datapoint can be
linked to a MV datapoint that corresponds to a feedback.
To define SetPoint feedback:
• Add the relation ‘has for feedback’ (1) at SetPoint level
• Fill the relation with the relevant MV datapoint.
• If necessary update the relation attributes:

2. execution timeout (range [0, 999 s], step 1 s): in this given delay, feedback must
change relatively to the control. If not, a negative acknowledgement is sent for the
control (for details see section 5.1.8 Overview of control sequence processing).
(1)
FIGURE 160: DEFINING SETPOINT FEEDBACK
(2)
FIGURE 161: SETTING ATTRIBUTES OF A SETPOINT FEEDBACK RELATION

5.2 Linking a datapoint to a profile

Many common characteristics are often shared by a set of datapoints. For instance, all
feeder breaker positions have got the same state labels, alarm and logging behaviour. To
group these common characteristics, profile concept has been embedded in data modelling.
For each kind of datapoints (SPS, DPS,…) there exists a relevant profile (SPSProfile,
DPSProfile, …). Several datapoints of the same kind are link-able 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 ease of explanation, this short-cut will be done in this document.
For input datapoints, the following characteristics are set at profile level:
• state labels and eventual unit label for MV and counter.
• definition of the archived and logged states.
• definition of the alarmed states (gravity, delay, audibility).
• definition of state interlocking values.
• definition of forcing/substitution/suppression (FSS) and SBMC facilities.
• links to printers defined in the system topology for alarm and event logging purpose.
For output datapoints, the following characteristics are set at profile level:
• order labels and eventual unit label for setpoints.
• definition of the significant orders for SPC and DPC.
• definition of the alarmed order failure (gravity, delay, audibility).
• definition of the archived and logged transitions.
• SBO mode facility.
• links to printers defined in the system topology for alarm and event logging purpose.
‘Profile’ objects can be put at any level of the system topology but never in the electrical
topology: they concern only system characteristics. For details about the system topology,
see section 4 DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE.
A profile object can be added at the following levels of the system topology:
• SCS.
• Ethernet network.
• Any instance of computer.
• Any instance of computer board.
• Any computer printer.
• Any SCADA network managed by a computer.
• Any IED managed by a computer.

When configuring a computer, the best practice is to group all profiles relevant to its system
datapoints at computer level or eventually its sub-components. Upper levels (Ethernet
network or SCS) can be used to define profiles if sharing datapoint profile between several
computers is wished.
For electrical datapoints, different approaches can be done:
• Grouping datapoint profiles at computer level per bay basis it manages.
• Grouping datapoint profiles at SCS level by kind of bays/modules managed by the

system.
• Mixing the two previous approaches, particularly for profiles relevant to datapoints
whose level is upper than bay or belonging to same kind of bays fed by several bay
computers.
Be careful:
(Refer to section 4.5.1 Connecting computer to others station-bus sub-systems, for Client /
Server definition)
In the set of all the computers of a SCS:
• the following profile functional characteristics logging, alarm, archiving and FSS, are
only useful and given to the computer that serves the linked datapoints because these
functions are always done at computer server level. So, a computer A using a
datapoint acquired on a computer B will never log, alarm or archive events relevant to
this datapoint.
• the following profile functional characteristics ‘state interlocking values’ are given to
server and client computers using a datapoint, because interlock evaluation is a
distributed function done on every computer that needs it before controlling its own
electrical modules.
• the following profile functional characteristics ‘SBMC facilities’ are given to server or
client computers using a datapoint exchanged on a SCADA network they manage,
because SBMC filtering is a distributed function done on computers managing SCADA
networks.
• the following profile characteristics ‘state/order labels’ are given to server or client
computers using a datapoint but are only used by the server: computer bay mimics,
logging, alarm definitions are reduced to datapoints that the computer is server of.
5.2.1 Defining a SPS profile

5.2.1.1 Adding a SPS Profile
To create a SPS profile:
• Add a SPS profile from object entry available at the wished system object level (1).
• Update the profile attributes (see following sections).
• Define if necessary on which printers event logging of linked SPS datapoint is done,
via adding and filling the relation ‘has events logged on’ at profile level (2).
• Define if necessary on which printers alarm event logging of linked SPS datapoint is
done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).
(1)
FIGURE 162: ADDING A SPS PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
(2)
FIGURE 163: DEFINING EVENT LOGGING PRINTER FOR SPS PROFILE
(3)
FIGURE 164: DEFINING ALARM LOGGING PRINTER FOR SPS PROFILE

5.2.1.2 Setting ‘General’ attributes of a SPS Profile

When adding a SPS profile some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE.
And for linked SPS datapoints:
2. enable Force/Subst/Sup (No / Yes).
3. SBMC dependant (No / Yes).
4. SBMC state substitution value (Suppressed / Set / Reset): significant and visible if
SBMC dependant is set to Yes.
5. toggling filtering (No / Yes): useful for a datapoint acquired on a DI board to filter
toggling.
6. initial status (Reset / Set): used for computer software initialisation especially for
system datapoints.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 165: SETTING GENERAL ATTRIBUTES OF A SPS PROFILE

• The profile of a datapoint of the System topology must have its enable
Force/Subst/Sup attribute set to No.
5.2.1.3 Setting ‘State labels’ attributes of a SPS Profile
When adding a SPS profile, some State labels attributes must be updated (1). They are
used for events and alarm management at computer level (logging, display).
(1)
FIGURE 166: SETTING ‘STATE LABELS’ ATTRIBUTES OF A SPS PROFILE

5.2.1.4 Setting ‘State treatment’ attributes of a SPS Profile

When adding a SPS profile, some State treatment attributes must be updated, for each
available state of the linked datapoints (1).
Available attribute values are:
• OI & C264: no archive, no logging:

• OI & C264: archive, logging:
• OI & C264: archive, no logging:
• only C264: no archive, logging:
• only C264: archive, logging:
• only C264: archive, no logging:
• only OI: archive, logging:
• only OI: archive, no logging:
For computer configuration, a more synthetic vision of logging and archiving is deduced from
these attributes: for details refer to sections 5.3 Defining computer local archiving of
datapoint events and 5.5 Defining computer local logging of datapoint events and alarms.
(1)
FIGURE 167: SETTING ‘STATE TREATMENTS’ ATTRIBUTES OF A SPS PROFILE

5.2.1.5 Setting ‘Alarms’ attributes of a SPS Profile
When adding a SPS profile some Alarms attributes must be updated, for each available
state of the linked datapoints.
1. generation condition (Appearance / Appearance and disappearance): this attribute is
common for all the states of each SPS linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable:
2. defined (No / Yes).
3. masking due to control (No / Yes): this attribute must be set to ‘Yes’ to manage
correctly discrepancy (alarm only appears in case of spontaneous change of state
without previous control).
4. delay (range [0 s, 120 s], step 1 s): to avoid alarm generation if alarm condition
disappears within this delay.
5. gravity (range [1, 5], step 1).
6. audible (No / Yes): to activate a klaxon.
7. clearing mode (Manual / Automatic / Gravity basis): to precise the way alarm is
cleared when alarm condition disappears:
− Manual: users must explicitly clear the alarm ,

− Automatic: no user intervention is needed to clear the alarm,
− Gravity basis: the clearing mode is deduced from the one given at Scs object
level for the relevant gravity
For ‘Set’ and ‘Reset’ state, extra attribute spurious is settable ((8) and (9)). This information
is only significant when the user wants to alarm a spurious SPS datapoint on a particular
event Set or Reset. In fact, the datapoint has got no state, but generates an event. It is
useful to alarm trip information of relays for instance. When setting a spurious alarm, only the
relative state must be defined as alarmed; the other states must be set to ‘not defined alarm’.
For computer configuration, all attributes are significant for datapoints it is server of.
(1)
(2)
(8)
(3)
(4)
(5)
(6)
(7)
(9)
FIGURE 168: SETTING ‘ALARMS’ ATTRIBUTES OF A SPS PROFILE

5.2.1.6 Setting ‘Interlocking’ attributes of a SPS Profile

For each possible state of a SPS linked to this profile and belonging to an interlocking
equation the user chooses among three values (Invalid, False, True) which one will be used
for evaluation of the interlocking equation.
FIGURE 169: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A SPS PROFILE

5.2.2 Defining a DPS profile
5.2.2.1 Adding a DPS Profile
To create a DPS profile:
• Add a DPS profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked DPS datapoint is done,
• Defines if necessary on which printers alarm event logging of linked DPS datapoint is
(3).
(1)
FIGURE 170: ADDING A DPS PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)

(2)
FIGURE 171: DEFINING EVENT LOGGING PRINTER FOR DPS PROFILE
(3)
FIGURE 172: DEFINING ALARM LOGGING PRINTER FOR DPS PROFILE

5.2.2.2 Setting ‘General’ attributes of a DPS Profile
When adding a DPS profile, some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE.
And for linked DPS datapoints:
4. SBMC state substitution value (Suppressed / Open / Closed / Jammed), significant
and visible if SBMC dependant is set to Yes.
5. toggling filtering (No / Yes): useful for datapoint acquired on DI board to filter
toggling.
6. initial status (Motion / Open / Closed / Undefined), used for computer software
initialisation especially for system datapoints.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 173: SETTING GENERAL ATTRIBUTES OF A DPS PROFILE

5.2.2.3 Setting ‘State labels’ attributes of a DPS Profile
When adding a DPS profile, some State labels attributes must be updated (1). They are
(1)
FIGURE 174: SETTING ‘STATE LABELS’ ATTRIBUTES OF A DPS PROFILE

5.2.2.4 Setting ‘State treatment’ attributes of a DPS Profile
When adding a DPS profile, some State treatment attributes must be updated, for each

(1)
FIGURE 175: SETTING ‘STATE TREATMENT’ ATTRIBUTES OF A DPS PROFILE

5.2.2.5 Setting ‘Alarms’ attributes of a DPS Profile
When adding a DPS profile some Alarms attributes must be updated, for each available
For each state, following alarm information are settable:
common for all the states of each DPS linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable:
2. defined (No / Yes)
without previous control)
disappears within this delay
6. audible (No / Yes): to activate a klaxon
− Manual: users must explicitly clear the alarm.

− Automatic: no user intervention is needed to clear the alarm.
level for the relevant gravity.
For ‘Open’ and ‘Closed’ states, extra attribute spurious is settable ((8) and (9)). This
information is only significant when the user wants to alarm a spurious DPS datapoint on a
particular event Open or Closed. In fact, the datapoint has got no state, but generates an
event. It is useful to alarm trip information of relays for instance. When setting a spurious
alarm, only the relative state must be defined as alarmed; the other states must be set to ‘not
defined alarm’.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 176: SETTING ‘ALARMS’ ATTRIBUTES OF A DPS PROFILE

5.2.2.6 Setting ‘Interlocking’ attributes of a DPS Profile

For each possible state of a DPS linked to this profile and belonging to an interlocking
FIGURE 177: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A DPS PROFILE

5.2.3 Defining a MPS profile
5.2.3.1 Adding a MPS Profile
To create a MPS profile:
• Add a MPS profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked MPS datapoint is done,
• Defines if necessary on which printers alarm event logging of linked MPS datapoint is
(3).
(1)
FIGURE 178: ADDING A MPS PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)

(2)
FIGURE 179: DEFINING EVENT LOGGING PRINTER FOR MPS PROFILE
(3)
FIGURE 180: DEFINING ALARM LOGGING PRINTER FOR A MPS PROFILE

5.2.3.2 Setting ‘General’ attributes of a MPS Profile

When adding a MPS profile, some general attributes must be updated:
1. short name and long name: only used for profile identification in SCE.
And for linked MPS datapoints:
2. enable Force/Subst/Sup (No / Yes)
4. SBMC state substitution value (Suppressed / Open / Closed / Jammed): significant
and visible if SBMC dependant is set to Yes.
(1)
(2)
(3)
(4)
FIGURE 181: SETTING GENERAL ATTRIBUTES OF A MPS PROFILE

5.2.3.3 Setting ‘State labels’ attributes of a MPS Profile
When adding a MPS profile, some State labels attributes must be updated (1). They are
(1)
FIGURE 182: SETTING ‘STATE LABELS’ ATTRIBUTES OF A MPS PROFILE

5.2.3.4 Setting ‘State treatment’ attributes of a MPS Profile

When adding a MPS profile, some State treatment attributes must be updated, for each

(1)
FIGURE 183: SETTING ‘STATE TREATMENT’ ATTRIBUTES OF A MPS PROFILE

5.2.3.5 Setting ‘Alarms’ attributes of a MPS Profile

When adding a MPS profile some Alarms attributes must be updated, for each available
state of the linked datapoints.:
common for all the states of each MPS linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable
without previous control).
6. audible (No / Yes): to activate a klaxon.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 184: SETTING ‘ALARMS‘ ATTRIBUTES OF A MPS PROFILE

5.2.3.6 Setting ‘Interlocking’ attributes of a MPS Profile

For each possible state of a MPS linked to this profile and belonging to an interlocking
FIGURE 185: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A MPS PROFILE

5.2.4 Defining a MV profile

5.2.4.1 Adding a MV Profile
To create a MV profile:
• Add a MV profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked MV datapoint is done,

• Defines if necessary on which printers alarm event logging of linked MV datapoint is

(3).
(1)
FIGURE 186: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A MPS PROFILE
(2)
FIGURE 187: DEFINING EVENT LOGGING PRINTER FOR MV PROFILE

(3)
FIGURE 188: DEFINING ALARM LOGGING PRINTER FOR MV PROFILE

5.2.4.2 Setting ‘General’ attributes of a MV Profile
When adding a MV profile, some general attributes must be updated:
1. short name and long name: only used for profile identification in SCE.
And for linked MV datapoints:
3. SBMC dependant (Yes to suppressed / No).
4. unit :used for display, logging and alarm at computer level.
5. default format: Reserved for Substation control point usage.
(1)
(2)
(3)
(4)
(5)
FIGURE 189: SETTING GENERAL ATTRIBUTES OF A MV PROFILE

5.2.4.3 Setting ‘State labels’ attributes of a MV Profile

When adding a MV profile, some State labels attributes must be updated (1). They are used
for events and alarm management at computer level (logging, display).
(1)
FIGURE 190: SETTING ‘STATE LABELS’ ATTRIBUTES OF A MV PROFILE

5.2.4.4 Setting ‘State treatment’ attributes of a MV Profile
When adding a MV profile, some State treatment attributes must be updated, for each

(1)
FIGURE 191: SETTING ‘STATE TREATMENTS’ ATTRIBUTES OF A MV PROFILE

5.2.4.5 Setting ‘Alarms’ attributes of a MV Profile
When adding a MV profile some Alarms attributes must be updated, for each available state
of the linked datapoints.
For each state, following alarm information are settable:
common for all the states of each MV linked to this profile. It defines when alarm are
generated.
For each state the following attributes are settable
5. audible (No / Yes): to activate a klaxon
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 192: SETTING ‘ALARMS’ ATTRIBUTES OF A MV PROFILE

5.2.4.6 Setting ‘Interlocking’ attributes of a MV Profile
For each possible state of a MV linked to this profile and belonging to an interlocking
(1)
FIGURE 193: SETTING ‘INTERLOCKING’ ATTRIBUTES OF A MV PROFILE

5.2.4.7 Setting ‘Mean value’ attributes of a MV Profile

When adding a MV profile, some ‘Mean value’ attributes must be updated. They are
reserved for substation control point usage.
1. computation (No / Yes)
2. reference hour (range [0, 23], step 1)
3. reference day (range [0, 31], step 1)
(1)
FIGURE 194: SETTING ‘MEAN VALUE’ ATTRIBUTES OF A MV PROFILE

5.2.5 Defining a Counter profile

5.2.5.1 Adding a Counter Profile
To create a Counter profile:
• Add a Counter profile from object entry available at the wished system object level (1).
• Defines if necessary on which printers event logging of linked Counter datapoint is

done, via adding and filling the relation ‘has events logged on’ at profile level (2).
• Defines if necessary on which printers alarm event logging of linked Counter datapoint
is done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).
(1)
FIGURE 195: ADDING A COUNTER PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
(2)
FIGURE 196: DEFINING EVENT LOGGING PRINTER FOR COUNTER PROFILE
(3)
FIGURE 197: DEFINING ALARM LOGGING PRINTER FOR COUNTER PROFILE

5.2.5.2 Setting ‘General’ attributes of a Counter Profile

When adding a Counter profile, some general attributes must be updated:
1. short name and long name : only used for profile identification in SCE.
And for linked Counter datapoints:
2. SBMC dependant (Yes to suppressed / No).
3. energy equivalent to a pulse (range [-3.4E38, +3.4E38].
4. unit used for display, logging and alarm at computer level.
5. default format: Reserved for Substation control point usage.
(1)
(2)
(3)
(4)
(5)
FIGURE 198: SETTING GENERAL ATTRIBUTES OF A COUNTER PROFILE

5.2.5.3 Setting ‘State labels’ attributes of a Counter Profile
When adding a Counter profile, some ‘State labels’ attributes must be updated (1). They are
(1)
FIGURE 199: SETTING ‘STATE LABELS’ ATTRIBUTES OF A COUNTER PROFILE

5.2.5.4 Setting ‘State treatment’ attributes of a Counter Profile
When adding a Counter profile, some ‘State treatment’ attributes must be updated, for each


(1)
FIGURE 200: SETTING ‘STATE TREATMENT’ ATTRIBUTES OF A COUNTER PROFILE

5.2.5.5 Setting ‘Alarms’ attributes of a Counter Profile
When adding a Counter profile, some ‘Alarms’ attributes must be updated, for each available
Globally to all Counter states, the attribute ‘generate condition’ (1) defines when alarms are
generated for the datapoint: ‘appearance of the event’ or ‘appearance and disappearance of
the event’.
For each state (Valid, SelfCheckFault, Unknown, Forced, Overrange, Undefined) the
following alarm attributes are settable:
5. audible (No / Yes), to activate a klaxon.

(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 201: SETTING ‘ALARMS’ ATTRIBUTES OF A COUNTER PROFILE

5.2.5.6 Setting ‘Mean value’ attributes of a Counter Profile
When adding a Counter profile, some ‘Mean value’ attributes must be updated (1). They are
reserved for substation control point usage.
(1)
FIGURE 202: SETTING ‘MEAN VALUE’ ATTRIBUTES OF A COUNTER PROFILE

5.2.6 Defining a SPC profile

5.2.6.1 Adding a SPC Profile
To create a SPC profile:
• Add a SPC profile from object entry available at the wished system object level (1).
• Define if necessary on which printers event logging of linked SPC datapoint is done,
• Define if necessary on which printers alarm event logging of linked SPC datapoint is
(3).
(1)
FIGURE 203: ADDING A SPC PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
(2)
FIGURE 204: DEFINING EVENT LOGGING PRINTER FOR SPC PROFILE
(3)
FIGURE 205: DEFINING ALARM LOGGING PRINTER FOR SPC PROFILE

5.2.6.2 Setting ‘General’ attributes of a SPC Profile

When adding a SPC profile, some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE
And for linked SPC datapoints:
2. SBO mode (for details see section 6.1.2 of chapter C264/EN FT)
Available values are:
− Direct execute
− SBO operate once
− SBO operate many
− Direct execute with SBO control box (reserved to substation control point
usage), similar to ‘Direct execute’ for computer
3. SBO timeout (range [0, 600 s], step 1s), significant if SBO mode is set to ‘SBO
operate once’ or ‘SBO operate many’.
(1)
(2)
(3)
FIGURE 206: SETTING GENERAL ATTRIBUTES OF A SPC PROFILE

5.2.6.3 Setting ‘Order labels’ attributes of a SPC Profile
When adding a SPC profile, some ‘Order labels’ attributes must be updated. They are used
for events and alarm management at computer level (logging, display) and for correct SPC
order management:
1. ‘Order off’ usage (No / Yes)
2. ‘Order on’ usage (No / Yes)
3. ‘Order off’ label
4. ‘Order on’ label
(1)
(2)
(3)
(4)
FIGURE 207: SETTING ‘ORDER LABELS’ ATTRIBUTES OF A SPC PROFILE

5.2.6.4 Setting ‘State treatment’ attribute of a SPC Profile

When adding a SPC profile, A ‘State treatment’ attribute must be updated globally for all
available control and acknowledgement steps of the linked datapoints (1).

this attribute: for details refer to sections 5.3 Defining computer local archiving of datapoint
events and 5.5 Defining computer local logging of datapoint events and alarms.
(1)
FIGURE 208: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF A SPC PROFILE

5.2.6.5 Setting ‘Alarms’ attributes of a SPC Profile
When adding a SPC profile, some ‘Alarms’ attributes must be updated, for the correct alarm
management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm information are settable:
3. gravity (range [1, 5], step 1)
4. audible (No / Yes), to activate a klaxon

(1)
(2)
(3)
(4)
(5)
FIGURE 209: SETTING ‘ALARMS’ ATTRIBUTES OF A SPC PROFILE

5.2.6.6 Setting ‘Interlocking and FBD’ attributes of a SPC Profile
When adding a SPC profile, some ‘Interlocking and FBD’ attributes can be updated for
boolean evaluation of interlocking equation, if the SPC belongs to an interlock equation or if
the SPC is an input of FBD automation (see sections 6.6.1 Defining a FBD fast automation
and 6.6.6 Defining interlocking):
The following attributes are settable:
1. ‘On order’ interlock value (Invalid / False / True): this attribute defines the value
affected to the On order state of the SPC for evaluation of an interlock equation or a
FBD using this SPC.
2. ‘Off order’ interlock value (Invalid / False / True): this attribute defines the value
affected to the Off order state of the SPC for evaluation of an interlock equation or a
FBD using this SPC.
(1)
(2)
FIGURE 210: SETTING ‘INTERLOCKING AND FBD’ ATTRIBUTES OF A SPC PROFILE

5.2.7 Defining a DPC profile

5.2.7.1 Adding a DPC Profile
To create a DPC profile:
• Add a DPC profile from object entry available at the wished system object level (1).
• Define if necessary on which printers event logging of linked DPC datapoint is done,
• Define if necessary on which printers alarm event logging of linked DPC datapoint is
(3).
(1)
FIGURE 211: ADDING A DPC PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)
(2)
FIGURE 212: DEFINING EVENT LOGGING PRINTER FOR DPC PROFILE

(3)
FIGURE 213: DEFINING ALARM LOGGING PRINTER FOR DPC PROFILE

5.2.7.2 Setting ‘General’ attributes of a DPC Profile
When adding a DPC profile, some general attributes must be updated:
1. short name and long name: only used for profile identification in SCE
And for linked DPC datapoints:
2. SBO mode
− Direct execute
− SBO operate once
− SBO operate many
usage), similar to ‘Direct execute’ for computer
(1)
(2)
(3)
FIGURE 214: SETTING GENERAL ATTRIBUTES OF A DPC PROFILE

5.2.7.3 Setting ‘Order labels’ attributes of a DPC Profile

‘Order labels’ attributes of a DPC profile are used for events and alarm management at
computer level (logging, display) and for correct SPC order management:
1. ‘Order open’ (set to 01) usage (No / Yes)
2. ‘Order close’ (set to 10) usage (No / Yes)
3. ‘Order open’ (set to 01) label
4. ‘Order close’ (set to 10) label
(1)
(2)
(3)
(4)
FIGURE 215: SETTING ‘ORDER LABELS’ ATTRIBUTES OF A DPC PROFILE

5.2.7.4 Setting ‘State treatment’ attribute of a DPC Profile
When adding a DPC profile the treatment on event attribute must be updated globally for all
available control and acknowledgement steps of the linked datapoints (1).

(1)
FIGURE 216: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF A DPC PROFILE

5.2.7.5 Setting ‘Alarms’ attributes of a DPC Profile

When adding a DPC profile, some ‘Alarms’ attributes must be updated, for the correct alarm
management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm informations are settable:
(1)
(2)
(3)
(4)
(5)
FIGURE 217: SETTING ‘ALARMS’ ATTRIBUTES OF A DPC PROFILE

5.2.7.6 Setting ‘Interlocking and FBD’ attributes of a DPC Profile
When adding a DPC profile, some ‘Interlocking and FBD’ attributes can be updated for
boolean evaluation of interlocking equation, if the SPC belongs to an interlock equation or if
the DPC is an input of FBD automation (see sections 6.6.1 Defining a FBD fast automation
and 6.6.6 Defining interlocking):
The following attributes are settable:
1. ‘Open order’ interlock value (Invalid / False / True): this attribute defines the value
affected to the Open order state of the DPC for evaluation of an interlock equation or a
FBD using this DPC
2. ‘Close order’ interlock value (Invalid / False / True): this attribute defines the value
affected to the Close order state of the DPC for evaluation of an interlock equation or
a FBD using this DPC
(1)
(2)
FIGURE 218: SETTING ‘INTERLOCKING AND FBD’ ATTRIBUTES OF A DPC PROFILE

5.2.8 Defining a SetPoint profile
5.2.8.1 Adding a SetPoint Profile
To create a SetPoint profile:
• Add a SetPoint profile from object entry available at the wished system object level
(1).
• Define if necessary on which printers event logging of linked SetPoint datapoint is

done, via adding and filling the relation ‘has events logged on’ at profile level (2).
• Define if necessary on which printers alarm event logging of linked SetPoint datapoint
is done, via adding and filling the relation ‘has alarm events logged on’ at profile level
(3).
(1)
FIGURE 219: ADDING A SETPOINT PROFILE (SAMPLE GIVEN AT COMPUTER LEVEL)

(2)
FIGURE 220: DEFINING EVENT LOGGING PRINTER FOR SETPOINT PROFILE
(3)
FIGURE 221: DEFINING ALARM LOGGING PRINTER FOR SETPOINT PROFILE

5.2.8.2 Setting ‘General’ attributes of a SetPoint Profile
When adding a SetPoint profile, some general attributes must be updated:
1. short name and long name of the profile only used for profile identification in SCE
And for linked SetPoint datapoints:
2. SBO mode: available values are:
− Direct execute
− SBO operate once, reserved for future use
− SBO operate many, reserved for future use
usage), similar to ‘Direct execute’ for computer, reserved for future use
4. unit used for display, logging and alarm at computer level.
(1)
(2)
(3)
(4)
FIGURE 222: SETTING GENERAL ATTRIBUTES OF A SETPOINT PROFILE

5.2.8.3 Setting ‘treatment on event’ attribute of a SetPoint Profile
When adding a SetPoint profile, the ‘treatment on event’ attribute must be updated globally
for all available control and acknowledgement steps of the linked datapoints (1).
The available values for this attribute are:

(1)
FIGURE 223: SETTING ‘STATE TREATMENT’ ATTRIBUTE OF A SETPOINT PROFILE

5.2.8.4 Setting ‘Alarms’ attributes of SetPoint Profile

When adding a SetPoint profile, some ‘Alarms’ attributes must be updated, for the correct
alarm management in case of a negative acknowledgement concerning control of the linked
datapoints.
The following alarm informations are settable:
(1)
(2)
(3)
(4)
(5)
FIGURE 224: SETTING ‘ALARMS’ ATTRIBUTES OF A SETPOINT PROFILE

5.3 Defining computer local archiving of datapoint events
A computer manages only archiving of the datapoints it is server of (Refer to section 4.5.1
Connecting computer to others station-bus sub-systems, for Client/Server definition).
For computer, archiving is available or not for all the events appearing on a given datapoint.
Archiving is activated as soon as one ‘state treatment’ attribute is set to ‘Archive and logging’
or ‘archive only’ at datapoint profile level (see relevant section of 5.2 Linking a datapoint to a
profile).
5.4 Defining computer local archiving of datapoint alarms
A computer manages only archiving of the datapoints it is server of (Refer to section 4.5.1
Alarm archiving at computer level is defined globally for all the computers at Scs object level
(see section 4.1 Setting general system configuration relevant to computers - point (6))
5.5 Defining computer local logging of datapoint events and alarms
A computer manages only logging of the datapoints it is server of (Refer to section 4.5.1
For computer, event logging is available or not for all the events appearing on a given
datapoint.
Event logging is activated as soon as the datapoint profile is linked to the local printer of the
computer via the relation ‘has events logged on’. To link a datapoint profile to a printer, see
relevant section of 5.2 Linking a datapoint to a profile.
Alarm logging is activated as soon as the datapoint profile is linked to the local printer of the
computer via the relation ‘has alarm events logged on’. To link a datapoint profile to a printer,
see relevant section of 5.2 Linking a datapoint to a profile.
To create a computer printer, see section 4.4.6 Adding a printer.
5.6 Defining acquisition source for input datapoints
Input datapoints have real-time values, fed by several ways exclusive each other:
• Acquisition via input channel(s)
• Acquisition via IED legacy network
• Acquisition via non-PACiS IEC61850 communicant IED
• (virtual) acquisition via software production:
− diagnostic and control of system components
− datapoints relevant to built-in function and user’s function
− MV or counter datapoint relevant to CT/VT board computation

5.6.1 Acquiring input datapoint via input channels
At SCE level, linking datapoint to specific channels (DI or AI channels) belonging to PACiS
computer’s DIU200-210, CCU200, AIU201 or AIU210 boards does input datapoint wiring.
5.6.1.1 Wiring a SPS datapoint, via one DI channel
A wired SPS is in the SET or in the RESET state, depending on the state of the associated
Digital Input and of the mode, normal or inverted (defined in configuration), of the SPS.
DI state Mode SPS state

ON Normal SET
OFF Normal RESET
ON Inverted RESET
OFF Inverted SET
Faulty * SELFCHECK FAULTY
To wire a SPS datapoint on a DI channel:
• Add the relation ‘wired on’ (1) at SPS datapoint level.
• Fill the relation with the relevant DI channel:

When datapoint level is lower than or equal to bay level, only DI channels from DIU
boards belonging to the computer that manages the bay, are available. To define the
computer that manages a bay, refer to section 6.1.4 Defining a Bay.
• If necessary update the relation attribute ‘inverted value’ (2), whose meaning is given
previously.
(1)
FIGURE 225: WIRING ONE SPS DATAPOINT VIA ONE DI CHANNEL
(2)
FIGURE 226: UPDATING THE WIRING OF A SPS DATAPOINT

5.6.1.2 Wiring a DPS datapoint via two DI channels
To wire a DPS datapoint on two DI channels:
• Add the relations ‘closed' wired on (1) and 'open' wired on (2) at DPS level.
• Fill the relations with the relevant DI channels:

When datapoint level is lower than or equal to bay level, only DI channels from DIU
boards belonging to the computer that manages the bay are available. To define the
computer that manages a bay, refer to section 6.1.4 Defining a Bay.
(1)
(2)
FIGURE 227: WIRING A DPS DATAPOINT VIA TWO DI CHANNELS

5.6.1.3 Wiring a MPS datapoint via n DI channels
MPS datapoint wiring is done via 3 or more DI channels (up to 16) for each state, and an
optional DI channel for ‘read inhibit’ indication.
To wire a MPS datapoint on n DI channels (n <=16):
• Add the relations ‘state wired on’ (1) at MPS datapoint level, for each available
state of the MPS (i begins from 0).
• Fill the relations with the relevant DI channels: when datapoint level is lower than or
equal to bay level, only DI channels from DIU boards belonging to the computer that
manages the bay, are available. To define the computer that manages a bay, refer to
section 6.1.4 Defining a Bay.
• If a read inhibit signal exists for the MPS, add the relations ‘read inhibit wired on’ (2) at
MPS datapoint level.
(2)
(1)
FIGURE 228: WIRING A MPS DATAPOINT VIA N DI CHANNEL

5.6.1.4 Wiring MV and TPI datapoint

MV and TPI datapoint wiring is done via 1 AI channel (analogue measurement) or via up to
64 DI channels (for digital measurements) and two optional DI channels for ‘read inhibit’
indication and sign bit.
To wire a MV or TPI datapoint on AI channel:
• Add the relation ‘wired on’ (1) at MV or TPI datapoint level.
• Fill the relation with the relevant AI channel: when datapoint level is lower than or
equal to bay level, only AI channels from AIU boards belonging to the computer that
• To define sensor range of the AI channel, refer to section 4.4.5 Configuring an AI

channel.
(1)
FIGURE 229: WIRING A MV DATAPOINT OR A TPI DATAPOINT VIA ONE AI CHANNEL

To wire a MV or TPI datapoint on n DI channels (n <=64):
• Add the relations ‘bit wired on’ (1) at MV or TPI datapoint level, for each available
bit channel of the MV or TPI (i begins from 0).
• Fill the relations with the relevant DI channels: when datapoint level is lower than or
• If a read inhibit signal exists for the MV or TPI, add the relations ‘read inhibit wired on’
(2) at MV or TPI datapoint level.
• If a sign bit exists for the MV, add the relations ‘sign bit wired on’ (3) at MV datapoint
level.
(1)
(2) (3)
FIGURE 230: WIRING MV OR TPI DATAPOINT, VIA N DI CHANNEL

5.6.1.5 Wiring a Counter datapoint
A "standard" Counter datapoint ("counter type" attribute set to "standard") wiring is done via
one DI channel (simple standard counter) or two DI channels (double standard counter).
To wire a Counter datapoint on DI channel:
• Add the relation ‘primary input wired on’ (1) at Counter datapoint level.
• If it is a double counter, add the extra relation ‘secondary input wired on’ (2) at
Counter datapoint level.
• Fill the relations with the relevant DI channel: when datapoint level is lower than or
• When the counter is used as an energy counter ("counter type" attribute set to "Energy
import" or "Energy Export") no wiring is needed but the relation "integrate: MV
electrical datapoint" (3) must be added to define the input of the counter. This relation
must be filled with the relevant MV datapoint.
(1) (2)
(3)
FIGURE 231: WIRING COUNTER DATAPOINT, VIA DI CHANNEL

5.6.2 Acquiring input datapoint via an IED legacy network

At SCE level, IED wiring is not described. Acquiring input datapoint issued from IED is done
by giving it a communication address in the relay’s legacy network mapping. This addressing
can be seen as a virtual wiring regardless to channel wiring.
Addressing a MPS datapoint on an IED legacy network is not available.
Depending on legacy network type, addressing information can be different.
See section 4 DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE for
further details about IED legacy network creation and addressing mapping definition.
To link an input datapoint to an existing IED address in an IED mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level. Generally, only one
relation adding is available for datapoint, except for DPS datapoint where up to 2
relations can be added, corresponding to each elementary bit of the DPS if the legacy
protocol does not support the DPS feature. In that case, the DPS is split in two SPS
regarding to the legacy protocol.
• Fill the relation with the relevant IED address: when datapoint level is lower than or
equal to bay level, only IED addresses from IEDs belonging to the computer that
(1)
FIGURE 232: ACQUIRING INPUT DATAPOINT VIA IED LEGACY NETWORK

(E.G. SPS DATAPOINT)
• A "DPS" datapoint can have one or two relation(s) "has for IED address":
- In the case of one IED address, the attribute "contact type" of the IED address must
be set to the "Unused" value.
- In the case of two IED addresses, the attribute "contact type" of one of the IED
addresses must be set to the "open" value, and the attribute "contact type" of the other
IED address must be set to the "close" value.
5.6.3 Acquiring input datapoint via non-PACiS IEC61850 communicant IED

At SCE level, IED wiring is not described. Acquiring input datapoint issued from IEC61850
IED is done by giving it a communication address in the relay’s IEC61850 mapping. This
addressing can be seen as a virtual wiring regardless to channel wiring (implicit association
is done at IED level).
See relevant application guide for further details about IED creation and corresponding
UCA2/IEC addressing mapping definition (nevertheless, similar UCA2/IEC addressing
mapping is described in section 4.5.2 Defining addressing mapping of station-bus network of
the present guide).
To link an input datapoint to an existing IEC61850 IED address in the IED mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level
• Fill the relation with the relevant IEC61850 address

Do not confuse:
• Give an IEC61850 address to a datapoint, still wired on a computer, via ‘has for IEC
address’ relation adding.
• Give an IEC address to a datapoint on an IEC IED. In that case the datapoint can not
be wired, because it is seen as produced or managed by the IEC IED.
(1)
FIGURE 233: ACQUIRING INPUT DATAPOINT VIA NON-PACIS IED

(E.G. SPS DATAPOINT)
5.6.4 Producing input datapoint

Another way to produce input datapoint real-time values is to allow software functions to
generate them.
This is done at several software levels:
• Supervision of IEC61850 PACiS system device, where system datapoints are produced
to indicate mode device, synchro device, database status,…
• Supervision of IEC61850 PACiS system device board (board status diagnostics).
• Supervision of legacy network and IED managed by PACiS computers (communication
status diagnostics).
• Supervision of redundancy between two PACiS computers (redundancy status
diagnostics).
• Supervision of logging printers managed by OI server or PACiS computer (printer status
diagnostics).
• Supervision of archiving managed by OI server (archiving status diagnostics).
• Facilities given by built-in electrical and grouping functions or user’s function, in PACiS
computers.
5.6.4.1 Implicit system input datapoint via system decomposition
In data modelling many components of the system topology own input datapoints. Their
creation is generally implicit when creating the component: they belong to its hierarchy.
Most of system input datapoints when transmitted on station bus network are addressed in
IEC61850 diagnostics bricks.
The list of such system datapoints are given in section 4.10 Setting system information for
computer components.
5.6.4.2 Implicit electrical input datapoint via built-in function
Implicit input datapoints can be embedded in built-in function creation. For details refer to the
following sections:
• 6.2 Defining a Synchrocheck function,
• 6.3 Defining an Auto-recloser built-in function,
• 6.4 Defining a Tap changer built-in function,
• 6.5 Defining an Automatic Voltage Regulation (AVR) built-in function.

Generally, these electrical datapoints are transmitted on station bus network in a specific
IEC61850 brick of built-in function.
5.6.4.3 Explicit electrical input datapoint via user function
By setting output plug, fast automation can produce real-time value for electrical input
datapoint (see section 6.6.1 Defining a FBD fast automation).
So can slow automation when it manages electrical datapoints or owns management input
datapoints (see section 6.6.2 Erreur ! Source du renvoi introuvable.).
For group needs, an electrical SPS containing the group result must be created (see section
6.6.3 Defining a group).
For SPS-DPS association, the resulting DPS is the product of the two SPS associations (see
section 6.6.5 Producing a DPS ).
To define (open or close) interlocking equation on SPC or DPC datapoint, an extra (open or
close) SPS should be produced, whose result is interlocking equation computation (see
section 6.6.6 Defining interlocking).
5.6.4.4 Explicit electrical input datapoint via CT/VT computation

Another way to produce a MV electrical datapoint is to link it to a CT/VT computer board.
Then, a specific link attribute must be filled to precise which MV computation is concerned
(power, harmonic ...).
Data produced by CT/VT board computation concern:
• RMS Values of phase voltage
• RMS values of busbar voltage
• RMS values of phase current
• RMS values of residual voltage and current
• Fundamental sequence components
• Active Power
• Reactive Power
• Apparent Power
• Frequency
• Harmonics levels ( expressed as a ratio of the magnitude of the fundamental voltage

or fundamental current)
To link a MV datapoint to a CT/VT computation:
• Add the relation ‘is computed by’ (1) at datapoint level.
• Fill the relation with the relevant CT/VT board. When datapoint level is lower than or
equal to bay level, only the CT/VT board belonging to the computer that manages the
bay, is available. To define the computer that manages a bay, refer to section 6.1.4
Defining a Bay.
• Update the relation attribute ‘measure type’ (2), giving the computation type.
(1)
FIGURE 234: DEFINING CT/VT COMPUTATION FOR A MV DATAPOINT

5.7 Defining control source for output datapoints

Output datapoints have real-time control values, managed by several ways exclusive each
other:
• control via output channel(s)
• control via IED legacy network
• control via non-PACiS IEC61850 communicant IED
• (virtual) control via software production:
− control of system components
− datapoints relevant to built-in function and user’s function

5.7.1 Controlling output datapoint via output channels
At SCE level, linking datapoint to specific channels (DO channels) belonging to PACiS
computer’s DOU200 or CCU200 boards does output datapoint wiring.
5.7.1.1 Wiring a SPC datapoint via one DO channel
To wire a SPC datapoint on a DO channel:
• Add the relation ‘wired on’ (1) at SPC datapoint level.
• Fill the relation with the relevant DO channel: when datapoint level is lower than or
equal to bay level, only DO channels from DOU boards belonging to the computer that
(1)
FIGURE 235: WIRING A SPC DATAPOINT VIA ONE DO CHANNEL

5.7.1.2 Wiring DPC datapoint via two or four DO channels
To wire a DPC datapoint on two or four DO channels:
• Add the relations ‘closed wired on’ (1) and ‘open wired on’ (2) at DPC datapoint level
(these relations can be added twice in case of 4 DO channels use).
• Fill the relations with the relevant DO channels: when datapoint level is lower than or
(1)
(2)
FIGURE 236: WIRING A DPC DATAPOINT VIA TWO DO CHANNEL

5.7.1.3 Wiring SetPoint datapoint
SetPoint datapoints can only be wired on digital channels (up to 48 DO channels) and two
optional DO channel for ‘read inhibit’ indication and sign bit.
To wire a SetPoint datapoint on n DO channels (n <=48):
• Add the relations ‘bit wired on’ (1) at SetPoint datapoint level, for each available bit
channel of the SetPoint (i begins from 0)
• Fill the relations with the relevant DO channels: when datapoint level is lower than or
• If a read inhibit signal exists for the SetPoint (see section 5.1.11.1 Overview of
SetPoint processing), add the relations ‘read inhibit wired on’ (2) at SetPoint datapoint
level.
• If a refresh signal exists for the SetPoint (see section 5.1.11.1 Overview of SetPoint
processing), add the relations ‘refresh wired on’ (3) at SetPoint datapoint level.
• If a sign bit exists for the SetPoint, add the relations ‘sign bit wired on’ (4) at SetPoint
datapoint level.
(1)
(2)
(3) (4)
FIGURE 237: WIRING A SETPOINT DATAPOINT VIA N DO CHANNEL

• A Setpoint datapoint wired on DO channels of Computer, must be digital and have its
profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute with SBO
popup”
5.7.2 Controlling output datapoint via an IED legacy network

At SCE level IED wiring is not described. Controlling output datapoint issued from IED is
done by giving it a communication address in the relay’s legacy network mapping. This
addressing can be seen as a virtual wiring regardless to channel wiring (implicit association
is done at IED level).
Depending on legacy network type, addressing information can be different.
See section 4 DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE for
further details about IED legacy network creation and addressing mapping definition.
To link an output datapoint to an existing IED address in an IED mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level. Generally, only one
relation adding is available for a datapoint, except for a DPC datapoint where up to
two relations can be added, corresponding to each elementary bit of the DPC if the
legacy protocol does not support the DPC feature. In that case, the DPC is split in two
SPC regarding to the legacy protocol.
• Fill the relation with the relevant IED address: when datapoint level is lower than or
equal to bay level, only IED addresses from IEDs belonging to the computer that
(1)
FIGURE 238: ACQUIRING OUTPUT DATAPOINT VIA IED LEGACY NETWORK

(E.G. SPC DATAPOINT)
• A "DPC" datapoint can have one or two relation(s) "has for IED address":
- In the case of one IED address, the attribute "contact type" of the IED address must
be set to the "Unused" value.
- In the case of two IED addresses, the attribute "contact type" of one of the IED
addresses must be set to the "open" value, and the attribute "contact type" of the other
IED address must be set to the "close" value.
5.7.3 Controlling output datapoint via non-PACiS IEC61850 communicant IED

At SCE level, IED wiring is not described. Controlling output datapoint issued from IED is
done by giving it a communication address in the relay’s IEC61850 mapping. This
addressing can be seen as a virtual wiring regardless to channel wiring.
See relevant application guide for further details about IEC61850 IED creation and
corresponding IEC addressing mapping definition (nevertheless, similar IEC addressing
mapping is described in section 4.5.2 Defining addressing mapping of station-bus network of
the present guide).
To link an output datapoint to an existing IED address in the IED IEC mapping:
• Add the relation ‘has for IED address’ (1) at datapoint level
• Fill the relation with the relevant IEC address

Do not confuse:
• Give an IEC address to a datapoint, still wired on a computer, via ‘has for IEC
address’ relation adding.
• Give an IEC address to a datapoint on an IEC IED. In that case the datapoint can not
be wired, because it is seen as produced or managed by the IEC IED.
(1)
FIGURE 239: ACQUIRING OUTPUT DATAPOINT VIA NON-PACIS IEC IED

5.7.4 Producing output datapoint

Another way to produce output datapoint real-time control values is to allow software
functions to generate them.
This is done at several software levels:
• Supervision of IEC61850 PACiS system device, where system datapoints are produced
to control mode device, database switch.
These output system datapoints are only used by System Management Tool.
• Supervision of redundancy between two PACiS computers (redundancy controls).
• Facilities given by built-in electrical and grouping functions or user’s function, in PACiS
computers.
5.7.4.1 Implicit system output datapoint via system decomposition

In data modelling, only PACiS devices of the system topology own output datapoints for
device mode management and database switch. Their creation is implicit when creating the
device: they belong to its hierarchy.
Computer redundancy needs specific output typed datapoints that must be manually added
in computer’s hierarchy.
Most of system output datapoints when transmitted on station bus network are addressed in
IEC61850 diagnostics bricks.
The list of such system datapoints are given in section 4.10 Setting system information for
computer components.
5.7.4.2 Implicit electrical output datapoint via built-in function
Implicit output datapoints can be embedded in built-in function creation. For details refer to
the following sections:
• 6.2 Defining a Synchrocheck function,
• 6.3 Defining an Auto-recloser built-in function,
• 6.4 Defining a Tap changer built-in function,
• 6.5 Defining an Automatic Voltage Regulation (AVR) built-in function.

Generally, these electrical datapoints are transmitted on station bus network in a specific
IEC61850 brick of built-in function.
5.7.4.3 Explicit electrical datapoint via user function
By setting output plug, fast automation can produce real-time order value for electrical output
datapoint (see section 6.6.1 Defining a FBD fast automation).
So can slow automation when it manages electrical output datapoints or owns management
output datapoints (see section 6.6.2 Erreur ! Source du renvoi introuvable.).
For xPS-xPC association, an electrical output SPC or DPC linked to the SPS or DPS must
exist and sometimes be created (see section 6.6.4 Controlling xPC ).
5.8 Defining datapoint association

This functionality allows to create a link between two datapoints so that the state of one
datapoint (called the target datapoint) is defined by the state of the other datapoint (called
the original datapoint).
Target datapoints can be one of the following types: SPS or DPS. They are available with
default name Mapping SPS and Mapping DPS at each level of the Electrical topology. In
the example given here after these two "target" datapoints are shown at the Substation level
(1).
(1)
FIGURE 240: THE TWO TARGET DATAPOINTS OF THE SUBSTATION LEVEL

Original datapoints can be one of the following types: SPS, DPS, MPS, MV.
5.8.1 Adding a target datapoint
Addition of a target datapoint is done via the “Objects entry” area associated to the
required electrical level ( Substation in our example) by double clicking the Mapping xPS ( or
right-clicking it and then clicking Add).
5.8.2 Linking the target datapoint to the original datapoint

To link the target datapoint to the original datapoint a relation 'is mapped on' (1) must be
added to the selected "original" datapoint ( order running at generic bay level in our
example). When added the undefined relation is present in the "Contents of" window
associated to the order running datapoint (2).
(1)
(2)
FIGURE 241: LINKING THE TARGET DATAPOINT OF THE ORIGINAL DATAPOINT

To select the target datapoint double-click the undefined relation "is mapped on:" (3). In the
Relation link editor dialog box are displayed all the available Mapping DPS datapoints (4).
Click the Mapping DPS datapoint you want to be associated to the order running datapoint
( Subs Mapping DPS in our example) then click the OK button.
(3)
(4)
FIGURE 242: SELECTING THE TARGET DATAPOINT

5.8.3 Defining the states associations

For every possible state of the original datapoint the user can define the corresponding state
of the target datapoint. To perform this association click the now defined relation "is mapped
on:" (5) in the "Contents of:" window associated to the "order running" datapoint. In the
"Attributes of:" window associated to this relation are listed all the possible states of the
original datapoint (6) and for each one the user has to select the corresponding state of the
target datapoint (7).
(5)
(6)
(7)
FIGURE 243: DEFINING THE STATES ASSOCIATIONS

• Up to 10 target datapoints can be associated to an original datapoint
• Up to 100 datapoints can be defined as original datapoints
• The original datapoint and the target datapoint can belong to different computers. In
this case the states of the original datapoints are transmitted through GOOSE
messages
• A target datapoint is managed as any other datapoint: transmission, used in

automation, alarms, …
• A SPS original datapoint can be associated to a SPS or a DPS
• A DPS original datapoint can be associated to a SPS or a DPS
• A MPS original datapoint can only be associated to a SPS ( the relation "is mapped
on: Mapping DPS Electrical datapoint" is not available in the "Object entry" window
associated to a MPS)
• A MV original datapoint can only be associated to a SPS ( the relation "is mapped on:
Mapping DPS Electrical datapoint" is not available in the "Object entry" window
associated to a MV)
6. DEFINING COMPUTER CONFIGURATION IN ELECTRICAL

ARCHITECTURE
6.1 Defining an electrical topology
At SCE data modelling level, the entry point of electrical topology is the ‘Site’ object. At the
moment, a ‘Site object’ (1) can be composed of only one ‘Substation’ object.
A substation (2) is constituted of ‘Voltage level’ objects, each of them corresponding to an
electrical partitioning of the substation by voltage level value (in kV).
A voltage level (3) is an aggregation of ‘Bay’ object (4), grouping of electrical devices, called
module (5). Generally this grouping is electrically self-safety, i.e. can be isolated from others
bays by switchgears for maintenance and managed by only one PACiS computer. There are
different kinds of bays: feeder, transformer, busbar, bus coupler, bus section, capacitor bank
and generic bay.
Coupling two voltage levels is commonly done via transformer. To respect SCE data
modelling electrical partitioning, this transformer must belong to a transformer bay (6)
arbitrary put in one of both voltage levels (generally its primary). An extra relation on
transformer defines to which voltage level its secondary (or primary) belongs.
Final electrical components are modules composing bays. There are different kinds of
modules: circuit breaker, switchgear, transformer, motor, generator, battery, capacitor,
inductor, converter and generic module. An extra module exists to describe substation
external connection (external line).
Every level of the electrical topology, except Site level, can own datapoints whose features
and configuration are described in section 5 DEFINING DATAPOINT.
(1) : Site
(2): Substation
n
(3) : Voltage level
(4) : Bay 'Feeder'
datapoints
(5) : Module 'Circuit breaker'
(6): Bay 'Transformer'
C0211ENb
FIGURE 244: ELECTRICAL TOPOLOGY DEFINITION (E.G.)

Feeder bay
Bus coupling bay
Transformer bay
Busbar bay
Bus section bay
C0212ENa
FIGURE 245: BAY SAMPLES
Switchgear
module
Q1
Circuit-breaker
module
Q0
Switchgear
module Q9
Switchgear Q8
Module (earth)
External line
module
C0213ENa
FIGURE 246: MODULE SAMPLES

6.1.1 Defining a Site

When creating a new configuration with the SCE, the electrical topology is automatically
instantiated via a ‘Site’ root object, containing a mandatory ‘Substation’ object.
A Site object corresponds to customer project identification: its attributes short name and
long name (1) can be entered at SCE level. At the moment, these attributes are not used.
(1)
FIGURE 247: SETTING ATTRIBUTES OF A SITE

6.1.2 Defining a Substation
When creating a new configuration using SCE, the electrical topology is automatically
instantiated via ‘Site’ root object, containing a mandatory ‘Substation’ object.
A Substation object corresponds to customer substation identification: its attributes short
name and long name (1) must be entered at SCE level, for proper logging formatting and
datapoint identification, at computer and operator interface levels.
At substation level, the attribute ‘default uniqueness’ (2) defines the way control uniqueness
is managed for the whole substation. Available values are:
• None: no control uniqueness is provided by PACiS system for the substation.
• Substation level: control uniqueness is provided by PACiS system for the whole
substation, i.e. two simultaneous controls are refused within the substation, except for
control datapoints configured as substation uniqueness independent (see sections
5.1.9.2 Setting ‘Dependencies’ attributes of a SPC datapoint, 5.1.10.2 Setting
‘Dependencies’ attributes of a DPC datapoint, 5.1.11.4 Setting ‘Dependencies’
attributes of a SetPoint datapoint.
• Bay level: control uniqueness is provided by PACiS system for an entire bay, i.e. 2
simultaneous controls are refused within the same bay, except for control datapoints
configured as bay uniqueness independent (see sections 5.1.9.2 Setting
‘Dependencies’ attributes of a SPC datapoint, 5.1.10.2 Setting ‘Dependencies’
attributes of a DPC datapoint, 5.1.11.4 Setting ‘Dependencies’ attributes of a SetPoint
datapoint).
(1)
(2)
FIGURE 248: SETTING ATTRIBUTES OF A SUBSTATION

Bay and substation uniqueness are managed by computer by synthesis of mandatory SPS
datapoints ‘Order running’, automatically added under a bay at its creation (see section 6.1.4
Defining a Bay).
• When control uniqueness is set to substation, all computers of substation must be

IEC-61850 client of all ‘order running’ SPS datapoints defined for all the bays. So,
proper IEC-61850 configuration must be done for all computers to insure that feature.
For details about IEC-61850 configuration, refer to section 4.5 Networking computer
on the station-bus network.
6.1.2.1 Adding a substation generic datapoint
The addition of a substation typed datapoint is done via the “Objects entry” window at
substation level by clicking on mouse’s right button. Here are listed generic datapoint
(standard usage) out of scope of the specific substation functions:
• Local/remote for substation (see section 6.1.2.2 Defining Local/Remote for substation)
• Taking Control for substation and SCDA links (see section 6.1.2.3 Defining Taking
Control for substation and SCADA links)
For more details about datapoints and their configuration, refer to section 5 DEFINING
DATAPOINT.
(2)
(1)
FIGURE 249: ADDING GENERIC DATAPOINT TO A SUBSTATION

Note: A Global alarm ack SPS (1) can be added to the substation level in
order to automatically acknowledge the new alarms in the C264 and
also in the OI. The detection mode attribute of this SPS must be set
to "Permanent" or "Permanent with computer auto-reset". This SPS
may be any wired SPS or SPS activated by a control ( by using the
Glb alm ack ctrl SPC(2)) from the SCADA or generated by any PSL.
It is also possible to launch a global alarm acknowledment at a fixed
time by using a cyclic SPS ( described in section 6.1.4.1 Adding bay
generic datapoint)
6.1.2.2 Defining Local/Remote for substation

A substation can be in remote or local control mode.
The Remote mode indicates that the substation is controlled from Remote Control Point
(RCP), via gateway. No controls can be sent from Substation Control Point level (except if
the concerned bay is in SBMC mode, see section 6.1.4.3 Defining SBMC for bay).
The Local mode indicates that the substation is controlled from PACiS Operator Interface
(Substation Control Point). The controls issued from RCP are not taken into account by the
system, they are refused.
Some controls, defined during the configuration phase, can be independent of the substation
control mode : it means they can be issued from SCP or RCP whatever the current control
mode is. Controls from configurable automation (see section 6.6 Defining an electrical
regulation by user function) are accepted whatever was the mode. For details about the
configuration of this dependency attribute, refer to sections:
• SPC: 5.1.9.2 Setting ‘Dependencies’ attributes of a SPC datapoint,
• DPC: 5.1.10.2 Setting ‘Dependencies’ attributes of a DPC datapoint,
• SetPoint: 5.1.11.4 Setting ‘Dependencies’ attributes of a SetPoint datapoint.

In Local or Remote mode the information acquired by computers and IEDs are always sent
to RCP and PACiS Operator Interface.
The automatic “Forcing of Invalid BI” function is used to avoid processing of invalid states of
the substation mode (the local or remote replacement state is defined in configuration). The
“Forced Local” state is processed as the “Local” state. The “Forced Remote” state is
processed as the “Remote” state.
Moreover, all IEC61850 clients (i.e. Operator Interface, gateway, computers) will
automatically forced the substation mode to “Forced Local” or “Forced Remote” if it takes the
UNKNOWN state (due for example to the loss of communication between the computer
which manages the substation mode and the IEC61850 clients).
To activate Local/remote substation facilities:
• add the optional datapoints ‘Local/remote DPS’ (1) and/or ‘Loc/rem ctrl DPC’ (2), via
the “Objects entry” window at substation level by clicking on mouse’s right button,
• configure them (see section 5 DEFINING DATAPOINT),
• if necessary, do not forget to link via ‘has for feedback’ relation, the control of the
Local/remote with the Local/remote status datapoint.
(2)
(1)
FIGURE 250: DEFINING LOCAL/REMOTE FOR SUBSTATION


Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
computer.
• If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback).
• If "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is mandatory.
• If "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.
• If, under a Substation, a "DPC" or "SPC" datapoint has its attribute "Substation mode
dependency" set to "Yes", then the Substation "Local/remote DPS" datapoint must be
present.
• If the two datapoints "Local/remote DPS" and "Loc/rem ctrl DPC" are present, they
must have the same Server device.
• "Loc/rem ctrl DPC" datapoint must have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”.
6.1.2.3 Defining Taking Control for substation and SCADA links
This facility allows a Remote Control Point (RCP) to force the mode of the substation from
LOCAL to REMOTE and to define on which link the SCADA controls must be accepted.
To activate Taking control facilities for a given SCADA network:
• add the optional datapoints ‘Taking Control’ (2) and ‘Taking status’ (1), via the
“Objects entry” window at substation level by clicking on mouse’s right button.
• configure them (see section 5 DEFINING DATAPOINT).
• add the relation ‘is taken control of’ at ‘Taking status’ datapoint level (3), and fill it with
the relevant given SCADA network.
• do not forget to link via ‘has for feedback’ relation, the control with the status
datapoint.
(2)
(1)
(1)
FIGURE 251: DEFINING TAKING CONTROL FOR A SCADA LINK

• If, at least, one SCADA network is linked to a Taking Control function, all the SCADA
Networks of the system must be linked to a Taking Control function.
• If a "Taking Status" datapoint is linked to a SCADA Network, it must also be linked to a

"Taking Control" datapoint through the relation "has for feedback".
• A "Taking Control" datapoint must be linked to a "Taking Status" datapoint through the
relation "has for feedback".
• The "Taking Control" datapoint must have its "activation mode" attribute set to a
"Permanent…" value. The "Taking Status" datapoint must have its "detection mode"
attribute set to the "Permanent" value.
• Both "Taking Control" and "Taking Status" datapoints must be linked to a SCADA
address in the mapping of their SCADA network.
• If a Taking-Control function is defined then, the "Loc/rem ctrl DPC" for substation must
be present and not wired.
• The Server of the Local/Remote datapoints is the Server of each datapoints couple
"Taking Status" / "Taking Control".
• All the devices having a SCADA network linked to a Taking-Control function are:
- Clients of each datapoints couple "Taking Status" / "Taking Control".
- Clients of the datapoints couple "Local/remote DPS" / "Loc/rem ctrl DPC".
6.1.2.4 Adding a user function to a substation
The addition of a substation user function is done via the “Objects entry” window at
substation level by clicking on mouse’s right button.
For more details about user function usage and their configuration, refer to section 6.6
Defining an electrical regulation by user function.
FBD user function
ISAGRAF user function
C0214ENb
FIGURE 252: ADDING USER FUNCTION TO SUBSTATION

6.1.3 Defining a Voltage level

At substation level, several ‘voltage level’ objects can be added. A voltage level corresponds
to a substation area whose electrical bays and sub-modules refer to the same nominal
voltage. There is an exception for transformer bay, coupling 2 different voltage levels, that
must be arbitrary located on one of the both.
To create a voltage level, add it from object entry available at substation level, as following:
FIGURE 253: ADDING A VOLTAGE LEVEL

When adding a voltage level, some general attributes must be updated:
2. nominal value in kV
3. ATCC existence (No / Yes): when set to ‘yes’, an extra tab-pane appears for the
voltage level, to enter specific ATCC regulation feature for the voltage level. For
details about ATCC configuration and this attribute, refer to section 6.5 Defining an
Automatic Voltage Regulation (AVR) built-in function
(1)
(2)
(3)
FIGURE 254: SETTING GENERAL ATTRIBUTES OF A MV DATAPOINT

6.1.3.1 Adding voltage level generic datapoint

The addition of a voltage level typed datapoint is done via the “Objects entry” window at
voltage level by clicking on mouse’s right button. Here are listed the generic datapoints
(standard usage).
For more details about datapoints and their configuration refer to section 5 DEFINING
DATAPOINT.
FIGURE 255: ADDING VOLTAGE LEVEL GENERIC DATAPOINT

6.1.3.2 Adding user function to voltage level
The addition of a voltage level user function is done via the “Objects entry” area at voltage
level by clicking on mouse’s right button.
FBD user function
C0214ENb
FIGURE 256: ADDING A USER FUNCTION TO VOLTAGE LEVEL

6.1.4 Defining a Bay

At ‘voltage level’ level, several ‘bay’ objects can be added. A voltage level corresponds to a
substation area whose electrical bays and sub-modules refer to the same nominal voltage.
There is an exception for transformer bay, coupling two different voltage levels that must be
arbitrary located on one of the both.
To create a bay:
• Add a typed one from object entry available at voltage level (1).
• Update the bay attributes.
• Update its ‘is managed by’ relation, to define which computer manages the bay (2).
(1)
FIGURE 257: ADDING A TYPED BAY
(2)
FIGURE 258: DEFINING COMPUTER MANAGING A BAY

When adding a bay, some general attributes must be updated:
1. short name and long name of the bay used for logging, alarms ...
2. control uniqueness used for output datapoints under the bay.
− None: no control uniqueness is provided by PACiS system for output datapoints

under the bay.
− See substation definition: control uniqueness is inherited from attribute ‘default

uniqueness’ at substation level (see section 6.1.2 Defining a Substation).
(1)
(2)
FIGURE 259: SETTING GENERAL ATTRIBUTES OF A BAY

(SAMPLE GIVEN FOR BAY TYPE ‘FEEDER’)
When adding a bay, a mandatory SPS datapoint ‘order running’ is automatically created at
bay level. This datapoint allows PACiS system to manage control uniqueness at substation
and bay level: it is set when a control is in progress on a bay.
• When control uniqueness is set to substation, all computers of substation must be

IEC61850 client of all ‘order running’ SPS datapoints defined for all the bays. So,
proper IEC61850 configuration must be done for all computers to insure that feature.
For details about IEC61850 configuration, refer to section 4.5 Networking computer on
the station-bus network.
Typed bay features
Using typed bay allows implicit sub-component creation. Hereafter are listed all typed bays
with their sub-component features:
• Feeder: a circuit-breaker and external line modules are mandatory and implicitly
created,
• Transformer: a transformer module is mandatory and implicitly created,
• Bus coupler: a circuit-breaker module is mandatory and implicitly created,
• Bus section: a circuit-breaker module is mandatory and implicitly created,
• Capacitor bank: a capacitor module is mandatory and implicitly created,
• Shunt: a circuit-breaker module is mandatory and implicitly created,
• Busbar: no module is available. This typed bay must be seen as a single electrical
node. A specific attribute ‘node reference’ used for electrical topology definition for
ATCC function can be entered for a busbar. For details about ATCC configuration and
this attribute, refer to section 6.5 Defining an Automatic Voltage Regulation (AVR)
built-in function.
• Generic bay: no sub-component constraint. Used for general usage outside the scope
of other previous typed bays.
6.1.4.1 Adding bay generic datapoint

The addition of a bay typed datapoint is done via the “Objects entry” window at bay level by
clicking on mouse’s right button. Here are listed generic datapoint (standard usage) out of
scope of the specific bay functions:
• Local/remote for bay (see section 6.1.4.2 Defining Local/Remote for bay)
• SBMC for bay (see section 6.1.4.3 Defining SBMC for bay)
• Group computation (see section 6.6.3 Defining a group)

DATAPOINT.
(1)
(2)
FIGURE 260: ADDING GENERIC DATAPOINT TO A BAY

Note: In a C264, up to eight transient SPS ( 1) can be defined as cyclic (day cycle). They can
be used to activate a periodic treatment. For these SPS the user has to configure, in addition
to the usual attributes of a SPS (previously listed in section 5.1.2.2 Creating a SPS
datapoint) two specific attributes (2) which define the time when activation of the SPS will
occur.
6.1.4.2 Defining Local/Remote for bay

Each bay can be independently in Remote or Local mode.
The Remote mode indicates that the bay is controlled from the upper level, i.e. Remote
Control Point (RCP) or Substation Control Point (SCP) depending on the current substation
control mode. No controls can be sent from Bay Control Point (BCP) level, i.e. operator
interface at the computer that manages the bay.
The Local mode indicates that the bay is controlled from BCP. The controls issued from
upper level are not taken into account by the bay.
Some controls, defined during the configuration phase, can be independent of the bay
control mode: it means they can be issued from any control points whatever was the current
control mode. Controls from configurable automation (ISAGRAF) are accepted in remote
mode. For details about the configuration of this dependency attribute, refer to sections:

In Local or Remote mode, the information issued from the bay is always sent to SCP and
RCP.
The automatic “Forcing of Invalid BI” function is used to avoid processing of invalid states of
the bay mode (the local or remote replacement state is defined in configuration). The
“Forced Local” state is processed as the “Local” state. The “Forced Remote” state is
processed as the “Remote” state.
To activate Local/remote bay facilities:
• add the optional datapoints ‘Local/remote DPS’ (1) and/or ‘Loc/rem ctrl DPC’ (2), via
the “Objects entry” window at bay level by clicking on mouse’s right button
• if necessary, do not forget to link via ‘has for feedback’ relation, the control of the
Local/remote with the Local/remote status datapoint.
(2)
(1)
FIGURE 261: DEFINING LOCAL/REMOTE FOR BAY


Hereafter, the term "wired" means that the datapoint must be wired on digital channel(s) of a
computer
• If "Loc/rem ctrl DPC" is present, then "Local/remote DPS" must be present (it's the
feedback).
• If "Local/remote DPS" is not wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must not be wired.
• If "Local/remote DPS" is wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.
• If, under a Bay, a "DPC" or "SPC" datapoint has its attribute "bay mode dependency"
set to "Yes", then the Bay "Local/remote DPS" datapoint must be present.
• "Loc/rem ctrl DPC" datapoint must have its profile attribute “SBO mode” set to "Direct
If the "GHU200" board of a computer has its attribute "HMI type" set to the "Simple" value,
then the "Local/remote DPS" datapoints of the bays managed by this computer must be all
be "Wired" or all "System".
6.1.4.3 Defining SBMC for bay
Each bay can be set in SBMC mode (Site Based Maintenance Control mode).
In SBMC mode, a bay does not take into account the commands issued from Remote
Control Point (RCP), even if the substation is in remote control (see section 6.1.4.2 Defining
Local/Remote for bay). Some controls, defined during the configuration phase, can be
independent of the SBMC mode. For details about the configuration of this dependency
attribute, refer to sections:

This function provides a facility to control selected bays from the Substation Control Point
(SCP) and optionally to suppress or force to a pre-defined state, datapoint for the RCP while
the substation is in Remote mode. If configured as SBMC dependant at its profile level, a
datapoint belonging to a bay in SBMC mode takes the state defined in the profile
configuration for the RCP, but is still processed normally in the SCS (e.g. all processes
inside the system are unaffected by the state modification of an information at the RCP
interface).
The state of a datapoint sent to RCP is defined in its profile configuration. For each type of
datapoint, they are:
SPS SUPPRESSED, SET, RESET

DPS SUPPRESSED, OPEN, CLOSE, JAMMED
MPS SUPPRESSED, UNDEFINED
MV, TPI and Counter SUPPRESSED
To activate SBMC facilities at bay level:
• add the optional datapoints ‘SBMC SPS’ (1) and ‘SBMC control SPC’ (2), via the
“Objects entry” window at bay level by clicking on mouse’s right button,
• do not forget to link via ‘has for feedback’ relation, the control of the SBMC with the
SBMC status datapoint.
(2)
(1)
FIGURE 262: DEFINING SBMC FOR BAY

• If "SBMC SPS" is present, then "SBMC control SPC" must be present.
• If "SBMC control SPC" is present, then "SBMC SPS" must be present.
• If "SBMC control SPC" is present, then its attribute "bay mode dependency" must be
set to "No".
• If a "DPC" or "SPC" datapoint has its attribute "SBMC mode dependency" set to "Yes",
then the "SBMC SPS" datapoint must be present.
• If a "DPS" or "SPS" datapoint has the attribute "SBMC dependant" of its profile set to
"Yes", then the "SBMC SPS" datapoint must be present.
6.1.4.4 Adding a user function to a bay
The addition of a bay user function is done via the “Objects entry” window at bay level by
clicking on mouse’s right button.
FBD user function
C0216ENb
FIGURE 263: ADDING USER FUNCTION TO BAY

6.1.5 Defining Module

This section deals with general module configuration. Configuring specific typed module is
described in following relevant section.
At ‘bay’ level, several ‘module’ objects can be implicitly or explicitly added. A module
corresponds generally to a substation electrical device.
To create explicitly a module:
• Add a typed one from object entry available at bay (1)

For implicit or explicit module:
• Update the module attributes (see following sections)
(1)
FIGURE 264: ADDING EXPLICITLY A TYPED MODULE

When adding a module, some general attributes must be updated:
1. short name and long name of the module used for logging, alarms ...
2. ‘node reference’, used for electrical topology definition for ATCC function. For details
about ATCC configuration and this attribute, refer to section 6.5 Defining an Automatic
Voltage Regulation (AVR) built-in function
(1)
(2)
FIGURE 265: SETTING GENERAL ATTRIBUTES OF A GENERIC MODULE

Typed module features

Using typed module specialises module configuration. Hereafter are listed all typed modules
with their main configuration features:
• Capacitor, Inductor:
− Specific attribute ‘reactive power value’ (in MVA), used for ATCC regulation. For
details about ATCC configuration and this attribute, refer to section 6.5 Defining
an Automatic Voltage Regulation (AVR) built-in function.
− Not lockable module.
• Convertor, generator, motor:
− Not lockable module.
• Transformer:
− Lockable module.
− Supports Tap changer built-in function.
− Supports ATCC function needs. For details about ATCC configuration and this
attribute, refer to section 6.5 Defining an Automatic Voltage Regulation (AVR)
built-in function.
• Circuit-breaker module:
− Supports synchrocheck and autorecloser built-in functions.
− May support withdrawing if exists.
• Switchgear module
− May support withdrawing if exists.
• External line:
− Only support SPS and DPS attribution.
• Generic module:
− Used for general usage outside the scope of other previous typed modules.
6.1.5.1 Adding a module generic datapoint
The addition of a module typed datapoint is done via the “Objects entry” window at module
level by clicking on mouse’s right button. Here are listed generic datapoint (standard usage)
out of scope of the specific module functions:
• Group computation (see section 6.6.3 Defining a group).
• Locking module (see section 6.1.5.3 Defining a lockable module).
• Specific features and configuration of typed modules (see following sections).

DATAPOINT.
FIGURE 266: ADDING A MODULE GENERIC DATAPOINT

(E.G. FOR GENERATOR MODULE)
6.1.5.2 Adding a user function to a module
The addition of a module user function is done via the “Objects entry” window at module
Module does not support ISAGRAF function.
FBD user
FIGURE 267: A USER FUNCTION TO A MODULE (E.G. FOR GENERATOR MODULE)

6.1.5.3 Defining a lockable module
According to PACiS system, locking module is a system function running on the computer
that manages the bay containing the module.
When a module is locked, any subsequent control acting on it, is refused. Locking is checked
during control sequence processing at computer level (see section 5.1.8 Overview of control
sequence processing).
At SCE level, only following types modules are lockable:
• Circuit-breaker,
• Switchgear,
• Transformer,
• Generic module.
To configure such a module as lockable:
• Add the pre-defined SPS datapoint ‘Lock SPS’ at module level (1) and configure it
(see section 5 DEFINING DATAPOINT),
• Add the pre-defined SPC datapoint ‘Lock control SPC’ at module level (2) and
configure it (see section 5 DEFINING DATAPOINT),
• Define the ‘Lock SPS’ as feedback of the ‘Lock control SPC’ by adding and filling ‘has
for feedback’ relation at the SPC level (see section 5.1.9.3 Defining a SPC feedback).
(2)
(1)
FIGURE 268: DEFINING A LOCKABLE MODULE

Lock SPS and Lock control SPC are datapoints fed and controlled directly by the computer
that manages the module. They can not be wired.
• For “Lock control SPC“, the feedback to “Lock SPS“ is mandatory

6.1.5.4 Defining withdrawable circuit-breaker or switchgear
To define a withdrawable circuit-breaker or switchgear:
• add the pre-defined SPS ‘withdraw’ at module level
• configure it (see section 5 DEFINING DATAPOINT)

Withdraw information is useful for bay mimic animation at computer LCD level. For more
details see section 7.3 Defining a computer bay mimic.
(1)
FIGURE 269: DEFINING A WITHDRAWABLE MODULE

(E.G. FOR CIRCUIT BREAKER)
6.1.5.5 Defining a circuit-breaker
This section deals with general circuit-breaker features and available associated input and
output datapoints at computer level.
If the circuit-breaker is synchronised by internal or external synchrocheck, extra datapoints

exist. For more details refer to section 6.2 Defining a Synchrocheck function.
General module features described in section 6.1.5 Defining Module are applicable to circuit-
breaker module and not reviewed here.
When adding a circuit-breaker module, the following specific general attribute must be
updated:
1. Circuit-breaker type:
− Single phase circuit-breaker, where the 3 phases can be managed independently
− Triple phase circuit-breaker, where the 3 phases can only be managed together.
− Other circuit-breaker: obsolete
(1)
obsolete
C0218ENb
FIGURE 270: SETTING CIRCUIT-BREAKER TYPE

The following tables give inputs and outputs circuit breaker’s features controlled by the
computer for triple phase and single phase circuit-breaker. For each datapoint its SCE
identification is given by a number, referenced in the following figure.
When creating a circuit breaker module implicitly or explicitly (cf. section 6.1.4 Defining a
Bay), the mandatory pre-defined DPS datapoint ‘computed switch position’ (20) is
automatically created.
To configure correctly a circuit-breaker module:
• Add the relevant datapoints, relatively to the following tables,
• do not forget to link via ‘has for feedback’ relation, the control(s) (1), (11) or (10) of the
breaker with the computed switch position (20) datapoint.
Triple phase circuit-breaker

OUTPUTS CB TYPE A OUTPUTS CB TYPE B (iv) INPUTS CB ALL TYPES
DEVICE (1) DPC control for (11) SPC control for open of (8) DPS or (19) SPS physical
CONTROL open/close of device device position of the device (1
phase)
(10) SPC control for close of
device (14) SPS (optional) phase not
together information
(20) system DPS the
feedback of the control (i)
DEVICE (9) SPC (optional) control of (9) SPC (optional) control of (15) SPS (optional) device
SELECTION device selection device selection selection position information
(HARDWARE)
Single phase circuit-breaker

DEVICE (1) DPC control for (2) DPC or (11) SPC control (16) SPS or (5) DPS physical
CONTROL open/close of device for open phase A position of phase A
(3) DPC or (12) SPC control (17) SPS or (6) DPS physical
for open phase B (pulse) position of phase B
(4) DPC or (13) SPC control (18) SPS or (7) DPS physical
for open phase C position of phase C
(1) DPC control for close of (14) system SPS phase not
device together information (ii)
(20) system DPS: the
feedback of the control (iii)
SELECTION device selection device selection selection position information
(HARDWARE)
(i) The computed double signal is equal to the physical status if the phase not together
status is equal to “false” else the computed signal is equal to “jammed”.
(ii) The computed “phases not together” is equal to “false” if all phases are in the same
position else it is equal to “true”.
(iii) The computed signal is equal to the phase A status if the phase not together status is
equal to “false” else the computed signal is equal to “jammed”.
(iv) Only the “DPC close “ is known by the other IEC61850 devices :
- For open the device they send the “DPC close” with “open” request
- For close the device they send the “DPC close” with “close” request
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(21)
(21)
FIGURE 271: AVAILABLE PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER

• The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive.
None is mandatory
• If physical position of the device is given by an SPS (19), phase not together
information (14) is mandatory
• Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}
If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then :
- in a set, if one datapoint is present for a phase, then the two others must be present
as well.
- the datapoints of the two sets (1) and (2) are mutually exclusive.
- if the datapoint "Switchgear pos." is present, but none of the three datapoints "Switch
PhA pos", "Switch PhB pos", and "Switch PhC pos" then the SPS datapoint "Ph not
together" is mandatory.
If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then :
- none of the datapoints referencing a phase (phA, phB or phC) is allowed.
• "Selection SPC" datapoint must have its profile attribute “SBO mode” set to "Direct
Execute" or “Direct Execute with SBO popup”
Control sequence of non-synchronised circuit breakers
Circuit breakers devices are managed in “direct execute mode” and in “SBO once mode”.
Refer to the generic description in section 5.1.8 Overview of control sequence processing.
Control sequence of synchronised circuit breakers
Refer to section 6.2 Defining a Synchrocheck function.
6.1.5.6 Defining a switchgear
This section deals with general switchgear features and available associated input and
General module features described in section 6.1.5 Defining Module are applicable to
switchgear module and not reviewed here.
When adding a switchgear module, the following specific general attribute must be updated:
1. Switchgear type:
− Busbar disconnector
− Disconnector
− Bypass disconnector
− Transfer busbar disconnector
− Earth switch
(1)
obsolete
C0219ENb
FIGURE 272: SETTING SWITCHGEAR TYPE

The following tables give inputs and outputs switchgear’s features controlled by the
computer. For each datapoint its SCE identification is given by a number, referenced in the
following figure.
To configure correctly a switchgear module:
• do not forget to link via ‘has for feedback’ relation, the control (3) of the switchgear (if it
exists) with the switch position (1) or (5) datapoint.
Switchgear
OUTPUTS TYPE A INPUTS CB ALL TYPES
DEVICE (3) DPC control for (1) DPS or (5) SPS physical
CONTROL open/close of device position of the device (1
phase) (v)
DEVICE (2) SPC (optional) control of (4) SPS (optional) device

SELECTION device selection selection position information
(HARDWARE)
(1)
(2)
(3)
(4)
(5)
FIGURE 273: AVAILABLE PRE-DEFINED DATAPOINTS FOR SWITCHGEAR

Control sequence of switchgears
Switchgear devices are managed in “direct execute mode” and in “SBO once mode”. Refer
to the generic description in section 5.1.8 Overview of control sequence processing.
6.1.5.7 Defining a transformer
This section deals with general transformer features and available associated input and
General module features described in section 6.1.5 Defining Module are applicable to
transformer module and not reviewed here.
When adding implicitly a transformer module via transformer bay creation (refer to 6.1.4
Defining a Bay), the following general attribute must be updated:
1. transformer type:
− Double wound: a double wound (or two winding transformer) is a transformer with
galvanic isolation between primary and secondary coil. Tap Changer (with
additional winding) is usually located at HV-neutral side for economic reasons.
Tapping-up (raise order) reduces primary winding and increase LV tension.
− Auto transformer: an auto transformer (or Auto-wound or single wound) is a

transformer without galvanic isolation between primary and secondary. Secondary
coil follows primary coil, (winding are serial). Tap Changer (with tap of additional
winding) is serial. Increasing tap position (raise order) acts simultaneously on
primary and secondary, it reduces transformer ratio then voltage at LV side. So for
this type of transformers the raise order must be inverted (consider as low order).
2. power value (range [1 to 300 MVA), useful for ATCC regulation
(refer to section 6.5 Defining an Automatic Voltage Regulation (AVR) built-in function)
3. impedance, whose unit is a percent of value for S=100 MVA (range [0,01 to 24,99 by
step 0,01) , useful for ATCC regulation (refer to section 6.5 Defining an Automatic
Voltage Regulation (AVR) built-in function)
(1)
(2)
(3)
FIGURE 274: SETTING TRANSFORMER TYPE

Transformer is used for coupling two voltage levels. To respect SCE data modelling
electrical partitioning, this transformer must belong to a transformer bay arbitrary put in one
of both voltage levels (generally its primary). An extra relation must be set on transformer
refining which voltage level its secondary (or primary) belongs to.
To create such a relation:
• Add the correct relation at transformer level
• Fill the relation with the relevant voltage level
(1)
FIGURE 275: COMPLETING PRIMARY/SECONDARY OF TRANSFORMER

When adding a transformer, some optional datapoints can be created at module level and
must be configured (see section 5 DEFINING DATAPOINT):
1. MCB position DPS: used for AVR function (see section 6.5 Defining an Automatic
Voltage Regulation (AVR) built-in function), to give Mini Circuit-Breaker position of
associated tap-changer, via DPS datapoint
2. MCB position SPS: used for AVR function (see section 6.5 Defining an Automatic
Voltage Regulation (AVR) built-in function), to give Mini Circuit-Breaker position of
associated tap-changer, via SPS datapoint
(1)
(2)
FIGURE 276: TRANSFORMER OPTIONAL DATAPOINTS

When it exists, tap position of transformer is controlled by a specific built-in function ‘Tap
changer’ available at transformer module level. For details about transformer control via tap
changer function, refer to section 6.4 Defining a Tap changer built-in function.
6.2 Defining a Synchrocheck function

6.2.1 Completing circuit-breaker definition for synchrocheck
The following tables give inputs and outputs circuit breaker’s features controlled by the
computer for triple phase and single phase circuit-breaker, when it is concerned by
synchrocheck function. For each datapoint its SCE identification is given by a number,
referenced in the following figure or relevant to the synchrocheck configuration (for
datapoints (22), (23), (24) and (25)).
These tables are complements to those described in section 6.1.5.5 Defining a circuit-
breaker.
To configure correctly a circuit-breaker module with synchrocheck:
• add the relevant datapoints, relatively to the following tables.
• do not forget to link via ‘has for feedback’ relation, the control(s) (1), (11) or (10) of the
breaker with the computed switch position (20) datapoint.
• link the circuit-breaker with an existing synchrocheck function created at bay or

substation level. This link is done at synchrocheck level (for details see 6.2.5 Creating
a synchrocheck function). Up to 2 circuit breakers can be linked to the same internal
synchrocheck.
• configure properly the synchrocheck function itself (for details see 6.2.5 Creating a
synchrocheck function).
Triple phase circuit-breaker with synchrocheck

DEVICE (1) DPC control for (11) SPC control for open (8) DPS or (19) SPS
CONTROL open/close of device of device physical position of the
device (1 phase)
(23) SPC or (22) DPC (10) SPC control for close
control for close with of device (14) SPS (optional) phase
synchrocheck not together information
(23) SPC or (22) DPC
control for close with (20) system DPS the
synchrocheck feedback of the control (i)
SELECTION device selection device selection selection position
information
(HARDWARE)
SYNCHROCHECK (24) SPC or (25) DPC (24) SPC or (25) DPC (26) SPS or (27) DPS
SET ON / SET OFF (optional) control of on/off (optional) control of on/off (optional) on/off
synchrocheck synchrocheck synchrocheck information
Single phase circuit-breaker with synchrocheck

DEVICE (1) DPC control for (2) DPC or (11) SPC control (16) SPS or (5) DPS
CONTROL open/close of device for open phase A physical position of phase A
(23) SPC or (22) DPC (3) DPC or (12) SPC control (17) SPS or (6) DPS
control for close with for open phase B (pulse) physical position of phase B
synchrocheck
(4) DPC or (13) SPC control (18) SPS or (7) DPS
for open phase C physical position of phase C
(1) DPC control for close of (14) system SPS phase not
device together information (ii)
(23) SPC or (22) DPC (20) system DPS: the

control for close with feedback of the control (iii)
synchrocheck
SELECTION device selection device selection selection position
information
(HARDWARE)
SYNCHROCHECK (24) SPC or (25) DPC (24) SPC or (25) DPC (26) SPS or (27) DPS
SET ON / SET (optional) control of on/off (optional) control of on/off (optional) on/off
synchrocheck synchrocheck synchrocheck information
OFF (v)
(i) The computed double signal is equal to the physical status if the phase not together
status is equal to “false” else the computed signal is equal to “jammed”.
(ii) The computed “phases not together” is equal to “false” if all phases are in the same
position else it is equal to “true”.
(iii) The computed signal is equal to the phase A status if the phase not together status is
equal to “false” else the computed signal is equal to “jammed”.
(iv) Only the “DPC close“ is known by the other IEC61850 devices :
- For open the device they send the “DPC close” with “open” request
- For close the device they send the “DPC close” with “close” request
(v) Wired SPC and SPS for external synchrocheck and system SPC and SPS for internal
synchrocheck. If is not configured the external synchrocheck module or the
synchrocheck automatism is considered always “set on”. DPC and DPS are used only
for manual synchrocheck.
(1)
(2)
(3)
(4)
(22)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(23)
(14)
(15)
(16)
(17)
(18)
(19)
(21)
(20
)
FIGURE 277: AVAILABLE PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER BREAKER

WITH SYNCHROCHECK
Do not forget to define ‘Comp. swit. pos.’ mandatory SPS at circuit-breaker level as
feedback of Sync CB close SPC/DPC.
• The two datapoints "Switch Ctrl DPC" and "Switch Ctrl SPC" are mutually exclusive.
None is mandatory.
• If physical position of the device is given by an SPS (19), phase not together
information (14) is mandatory.
• Set1: {Switch phA DPC, Switch phB DPC, Switch phC DPC}
Set2: {Switch phA SPC, Switch phB SPC, Switch phC SPC}
Set3: {Switch phA pos. DPS, Switch phB pos. DPS, Switch phC pos. DPS}
Set4: {Switch phA pos. SPS, Switch phB pos. SPS, Switch phC pos. SPS}
If the "circuit-breaker type" is set to the "Single phase CircuitBreaker" value, then :
- in a set, if one datapoint is present for a phase, then the two others must be present
as well.
- if the datapoint "Switchgear pos." is present, but none of the three datapoints "Switch
PhA pos", "Switch PhB pos", and "Switch PhC pos" then the SPS datapoint "Ph not
together" is mandatory.
If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then:
- none of the datapoints referencing a phase (phA, phB or phC) is allowed.
• A Circuit Breaker must be linked only once to a Synchrocheck function (relation "is
synchrocheck of").
• If a Circuit Breaker is linked to a Synchrocheck function (relation "is synchrocheck of"),

then its "Sync CB close" SPC datapoint must be present.
• "Sync CB close" datapoint of a "Circuit breaker" linked to a "Ext manual CS" or "Int
synchrocheck" synchrocheck must have its profile attribute “SBO mode” set to "Direct
• "Sync CB close" datapoint of a "Circuit breaker" linked to a "Ext auto CS"

synchrocheck must have its profile attribute “SBO mode” set to " SBO Operate Once”.
“Open” control sequence of synchronised circuit breakers
This sequence remains identical to the non-synchronised circuit-breaker (refer to section
6.1.5.5 Defining a circuit-breaker).
“Close” control sequence of synchronised circuit breakers
This sequence is different according to the configuration the synchrocheck type:
• External synchrocheck: the closure of the device is assumed by an external

synchrocheck module.
• Internal synchrocheck: the closure of the device is assumed by an internal

synchrocheck automatism in the computer.
Close control sequence can be configured with:
• Manual set on of the external synchrocheck module or internal synchrocheck

automatism.
• Automatic set on of the external synchrocheck module or internal synchrocheck

automatism.
Furthermore, waiting closes the CB by the external module the initiator of the request can:
• Cancel the request.
• Close the device by forcing request.

6.2.2 External synchrocheck behaviour

This functionality is described in section 6.3.2 of chapter C264/EN FT.
6.2.3 Internal synchrocheck behaviour
This functionality is described in section 6.3.3 of chapter C264/EN FT.
6.2.4 Automation description of internal synchrocheck
For each parameter of the internal synchrocheck, its SCE identification is given by (param
), referenced in Figure 287: SETTING ‘default settings’ attributes of an INTERNAL
SYNCHROCHECK.
Principle
The synchrocheck function can work in the following schemes:
Operator manual Operator Auto-recloser

closure Synchrocheck
closure
Network locking on both voltages X X X
presence and test of deltas (param 26) (param 20) (param 31)
Network coupling on both voltages X
presence and test of deltas (param 19)
Presence of only the line voltage X X X
(param 28) (param 22) (param 33)
Presence of only the busbar voltage X X X
Absence of both voltages X X X
The authorised schemes are defined during the configuration phase. The operator
synchrocheck closure behaviour is described in following sections.
Logic of authorisation of interlocking
The absolute values of the two voltages (Vline and Vbusbar) must be above or below settable
thresholds, to permit the circuit breaker closing. The following voltage controls are available:
• Vline and Vbusbar for network coupling
• Vline and Vbusbar for network locking
• Vline and not(Vbusbar)
• not(Vline) and Vbusbar
• not(Vline) and not(Vbusbar)

with Vline and Vbusbar TRUE if the measured voltage is above the threshold V> (param 15 and
param 17), and not(Vline) and not(Vbusbar) TRUE if the measured voltage is below the threshold
V< (param 16 and param 18). These threshold are given in % of the nominal voltage value,
updated at TMU200 board level (refer to section 4.4.2.3 Setting specific attributes of a
TMU200 board).
The selection of the voltage control is made during the configuration phase.
Schemes using Vline and not(Vbusbar) / not(Vline) and Vbusbar voltage controls
In case of the absence of one of the two voltages, at the end of a settable delay T2 (param
2), the authorisation of closing is given:
Vline
T2 0
& Closing authorization
Not(Vbusbar)
C0227ENa
FIGURE 278: VLINE AND NOT(VBUSBAR) VOLTAGE CONTROL
Vbusbar
T2 0
Not(Vline)
C0228ENa
FIGURE 279: NOT(VLINE) AND VBUSBAR VOLTAGE CONTROL

If, during the T2 delay time, one of the 2 criteria is lost, the timer is reinitialised and is
launched again on reappearance of all the criteria.
Schemes using not(Vline) or not(Vbusbar)voltage control
In case of the absence of both voltages, at the end of a settable delay T3 (param 1), the
authorisation of closing is given:
Not(Vline)
T3 0
Not(Vbusbar)
C0229ENa
FIGURE 280: NOT(VLINE) AND NOT(VBUSBAR) VOLTAGE CONTROL

If, during the T3 delay time, one of the 2 criteria is lost, the timer is reinitialised and is
launched again on reappearance of all the criteria.
Schemes using Vline and Vbusbar voltage control
Locking scheme
The closing authorisation will be given if the following conditions are fulfilled:
• Presence of both voltages , confirmed after a given delay (param 3) AND
• The difference in amplitude (algebraic) between the two voltages (∆V) is lower than
the seized threshold (Evect) (param 5) AND
• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 6) and
Fmax (param 7) are the extreme acceptable frequencies AND
• The difference between the two frequencies (∆F) is lower than the seized threshold
(Efreq) (param 8) AND
• The phase difference between the two voltages (∆ϕ) is lower than the seized threshold
(Ephase) (param 9)
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorise the CB closing.
If during the delay time T1 one of these criteria is lost, T1 is reinitialised and is relaunched on
reappearance of all the criteria.
T1 depends on the way circuit breaker is controlled (manual closure, manual synchronised
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param
30), (param 35).
Fmin < Fline < Fmax

Fmin < Fbusbar < Fmax
Vline
Vbusbar
& T1 0 Reclosing authorization
∆F <Efreq
∆ϕ < Ephase
∆V < Evect
C0230ENa
FIGURE 281: LOCKING SCHEME

Coupling scheme
In the coupling scheme, the CB can be closed only when the ∆ϕ is equal to 0.
But, in order to authorise the closing, it is first necessary that the following conditions are
fulfilled:
• Presence of both voltages AND
• The difference in amplitude (algebraic) between the two voltages (∆V) is lower than
the seized threshold (Evect) (param 10) AND
• The frequencies are as Fline and Fbusbar are such Fmin<F<Fmax where Fmin (param 11) and
Fmax (param 12) are the extreme acceptable frequencies AND
• The difference between the two frequencies (∆F) is lower than the seized threshold
(Efreq) (param 13)
These criteria must be still met before the time-out of a delay T1 started on the criteria
appearance else the synchrocheck function will not authorise the CB closing.
If during the delay time T1 one of these criteria is lost, T1 is reinitialised and is relaunched on
reappearance of all the criteria.
T1 depends on the way circuit breaker is controlled (manual closure, manual synchronised
closure, automatic with auto-recloser), given 3 parameters at SCE level: (param 25), (param
30), (param 35).
Fmin < Fline < Fmax

Fmin < Fbusbar < Fmax
Vline T1 0 Autorisation to check ∆ϕ
&
Vbusbar
∆F <Efreq
∆V < Evect
C0231ENa
FIGURE 282: COUPLING SCHEME
Then, since a CB has a response time, it is necessary to wait a known ∆ϕ in order to

anticipate the response time and to close the breaker with a ∆ϕ equal to 0.
Therefore, the closing authorisation will be sent when ∆ϕ = ∆F*360*Ta ± ∆(∆ϕ) where Ta
(param 4) is the anticipation time or response time of the circuit breaker and ∆(∆ϕ) (param
14) is the acceptable mistake on ∆ϕ. There is a delay for such a coupling given in
configuration (param 24).
6.2.5 Creating a synchrocheck function

Synchrocheck function can be created at several levels of the electrical topology:
• Substation level, in case of the synchrocheck function is shared by several breakers,
• Bay level, in case of the synchrocheck function dedicated to a particular breaker of the
bay, or shared by two breakers in two different bays managed by the same computer.
The addition of a synchrocheck is done via the “Objects entry” window at substation or bay
For more details about bay creation, refer to section 6.1.4 Defining a Bay.
Several types of synchrochecks exist:
1. External automatic synchrocheck
2. External manual synchrocheck
3. Internal automatic synchrocheck
4. Internal manual synchrocheck
At substation level, only ‘external manual synchrocheck’ is available.
Only following typed bays allows synchrocheck creation:
• Busbar,
• Bus coupler,
• Bus section,
• Feeder,
• Transformer,
• Generic bay.
(1)
(2)
(3)
(4)
FIGURE 283: ADDING A SYNCHROCHECK AT BAY LEVEL (E.G. FOR FEEDER)

(2)
FIGURE 284: ADDING A SYNCHROCHECK AT SUBSTATION LEVEL

Once added, synchrocheck general features must be set at SCE level:
1. Fill the relation is synchrocheck of, giving which circuit-breaker module is concerned
by the function. For substation synchrocheck, several relations ‘is synchrocheck of’
can be added and filled for all concerned breakers by the same synchrocheck. For bay
synchrocheck, two relations ‘is synchrocheck of’ can be filled for breakers of two
different bays. Nevertheless, these bays must be managed by the same computer,
and the same synchrocheck parameters will be used for the two breakers closure.
2. short name and long name of the synchrocheck used for logging, alarms ...
3. automatic out of service (No / Yes): defines if the synchrocheck is set off manually
(No) or automatically (Yes). When manually set off, an extra sequence is done by
computer (see previous sections). For automatic synchrocheck, this attribute is fixed
to ‘Yes’.
4. running time (range [0, 60s],step 1 s): this attribute appears in case of automatic out
of service. It corresponds to a latency time before setting out of service the
synchrocheck after successful or unsuccessful closure of the synchronised breaker.
(1)
(2)
(3)
(4)
FIGURE 285: SETTING SYNCHROCHECK GENERAL FEATURES

(E.G. FOR EXTERNAL MANUAL SYNCHROCHECK AT BAY LEVEL)
In case of internal synchrocheck, extra configuration information must be set (see section
6.2.5.1Setting default settings of internal synchrocheck).
When adding a synchrocheck, the following mandatory datapoints is automatically created at
function level and must be configured (see section 5 DEFINING DATAPOINT):
1. Accept forcing: SPS datapoint, given the authorisation to force synchrocheck. It is a
system datapoint: it cannot be wired and is managed by the computer running
synchrocheck sequence. Any automation or operator interface asking for a
synchrocheck forcing, should be client of this datapoint and test its status before
forcing. So, proper IEC61850 configuration must be done for all clients (computer,
operator interface) to insure that feature.
(1)
FIGURE 286: ACCEPT FORCING MANDATORY DATAPOINT FOR SYNCHROCHECK

(E.G. FOR EXTERNAL MANUAL SYNCHROCHECK AT BAY LEVEL)
6.2.5.1 Setting default settings of internal synchrocheck
Default settings of internal synchrocheck are relevant to parameters of automation
description (see section6.2.4 Automation description of internal synchrocheck)
When adding an internal synchrocheck, the following specific attributes must be updated:
General attributes
• absence deltas test duration (ms)
• presence test duration (ms)
• presence deltas test duration (ms)
• close time of the Circuit Breaker (ms)

Acceptance Conditions
• voltage delta threshold for locking (%)
• minimum frequency for locking (Hz)
• maximum frequency for locking (Hz)
• frequency delta threshold for locking (Hz)
• phase delta threshold for locking (°)
• voltage delta threshold for coupling (%)
• minimum frequency for coupling (Hz)
• maximum frequency for coupling (Hz)
• frequency delta threshold for coupling (Hz)
• phase delta threshold for coupling (°)

Voltage presence conditions
• line voltage over threshold (%)
• line voltage under threshold (%)
• bus voltage over threshold (%)
• bus voltage under threshold (%)

Used control schemes
• manual synchro close : coupling
• manual synchro close : locking
• manual synchro close : Line Dead and Bus Live
• manual synchro close : Line Live and Bus Dead
• manual synchro close : Line Dead and Bus Dead
• manual synchro close delay for coupling (s)
• manual synchro close delay (ms)
• manual close : locking
• manual close : Line Dead and Bus Live
• manual close : Line Live and Bus Dead
• manual close : Line Dead and Bus Dead
• manual close delay (ms)
• automatic close : locking
• automatic close : Line Dead and Bus Live
• automatic close : Line Live and Bus Dead
• automatic close : Line Dead and Bus Dead
• automatic close delay (ms)

(param 1)
(param 2)
(param 3)
(param 4)
(param 5)
(param 6)
(param 7)
(param 8)
(param 9)
(param 10)
(param 11)
(param 12)
(param 13)
(param 14)
(param 15)
(param 16)
(param 17)
(param 18)
(param 19)
(par am 20)
(param 21)
(param 22)
(param 23)
(param 24)
(param 25)
(param 26)
(param 27)
(param 28)
(param 29)
(param 30)
(param 31)
(param 32)
(param 33)
(param 35) (param 34)
C0237ENb
FIGURE 287: SETTING ‘DEFAULT SETTINGS’ ATTRIBUTES OF AN INTERNAL SYNCHROCHECK

When adding an internal synchrocheck, some mandatory system datapoints are

automatically created at function level and must be configured (see section 5 DEFINING
DATAPOINT). They give information about internal synchrocheck context (both voltage
presences and absences) and statuses. They are managed by the computer that runs the
internal synchrocheck.
1. Close order: transient SPS set as soon as a synchronised closure is in progress
2. on/off SPS: see section 6.2.5.2 Adding synchrocheck specific datapoints
3. Possible closing SPS: in locking mode, all the conditions after delay are met to
authorise synchronised closure
4. Ref. U absence SPS
5. Ref. U presence SPS
6. Voltage absence SPS
7. Voltage presence SPS
(1)
(2)
(3)
(4)
(5)
(6)
(7)
FIGURE 288: INTERNAL SYNCHROCHECK MANDATORY DATAPOINTS

6.2.5.2 Adding synchrocheck specific datapoints
To assume previous described behaviour of synchrocheck, when adding an auto-recloser,
some optional datapoints can be created at function level and must be configured (see
section 5 DEFINING DATAPOINT):
1. on/off control DPC: to control in / out of service of the synchrocheck via DPC
2. on/off control SPC: to control in / out of service of the synchrocheck via SPC
3. on/off DPS (unauthorised on internal synchrocheck): giving in/out of service status of
the synchrocheck via DPS
4. on/off SPS (mandatory on internal synchrocheck and implicitly created): giving in/out
of service status of the synchrocheck via SPS
Do not forget to define on/off SPS/DPS as feedback of on/off control SPC/DPC if they exist.
(1)
(2)
(3)
(4)
FIGURE 289: SYNCHROCHECK OPTIONAL DATAPOINTS

• As shown in the following picture, under a Synchrocheck function, some datapoints

are mutually exclusive and some must be wired. Here, the term "wired" means that the
datapoint must be linked to a digital/analog channel of a computer, or linked to an IED
address
Substation
Ext manual CS
on/off ctrl DPC
mutually exclusive + wired
on/off ctrl SPC
on/off DPS
on/off SPS mutually exclusive
Feeder
Ext auto CS
on/off ctrl DPC
on/off ctrl SPC mutually exclusive
on/off DPS
Ext manual CS
on/off ctrl DPC mutually exclusive + wired
on/off ctrl SPC
on/off DPS
(A) automatic out of service - Yes

Int synchrocheck
on/off ctrl DPC - No
mutually exclusive
on/off ctrl SPC
on/off SPS
S0280ENa
• For an "Int synchrocheck" function, having its "automatic out of service" attribute set to
the "Yes" value, the "on/off ctrl DPC" or "on/off ctrl SPC" datapoint must be present.
• "on/off ctrl DPC" or "on/off ctrl SPC" datapoint of "Int synchrocheck" synchrocheck
must have its profile attribute “SBO mode” set to "Direct Execute" or “Direct Execute
with SBO popup”
6.3 Defining an Auto-recloser built-in function
6.3.1 Auto-recloser behaviour
The auto–Recloser built-in function is described in section 3.1.2 of chapter C264/EN FT.
6.3.2 Creating an auto-recloser function
The addition of an auto-recloser is done via the “Objects entry” window at bay level by
Only following typed bays allows auto-recloser creation:
• Busbar,
• Bus coupler,
• Bus section,
• Feeder,
• Transformer,
• Generic bay.
FIGURE 290: ADDING AN AUTO-RECLOSER AT BAY LEVEL

Once added, auto-recloser general features must be set at SCE level:
1. Fill the relation ‘is auto-recloser of’, giving which circuit-breaker module is concerned
by the function.
2. short name and long name of the auto-recloser used for logging, alarms ...
3. functioning mode (1 ph trip) (Not used / 1P / 1P-3P / 1P-3P-3P / 1P-3P-3P-3P):
useable only for single phase circuit-breaker. Up to 4 cycles where the first one is
single phase and the others three phase.
4. functioning mode (3 ph trip) (Not used / 3P / 3P-3P / 3P-3P-3P / 3P-3P-3P-3P):
useable for single and triple phase circuit-breaker. Up to 4 cycles where all are three
phase.
5. unlocking way (Not used / Reinitialisation / Manual close / Both ways). For details
refer to previous description of ‘lock of auto-recloser’ in section 6.3.1 Auto-recloser
behaviour.
6. Fast 3 P reclose enable (No, Yes): if a synchrocheck exists for the breaker, auto-
recloser can bypass it during the 3-phases first cycle if the attribute is set to ‘Yes’.
7. 1st period monophased (range [100 ms, 5 s], step 10 ms): timer of the first single-
phase cycle.
8. 1st period triphased (range [1 s, 60 s], step 10 ms): timer of the first 3-phases cycle.
9. 2nd period triphased (range [1 s, 3600 s], step 1 s): timer of the second 3-phases
cycle.
10. 3rd period triphased (range [1 s, 3600 s], step 1 s): timer of the third 3-phases cycle.
11. 4th period triphased (range [1 s, 3600 s] step 1 s): timer of the fourth 3-phases cycle.
12. reclaim delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimc recovering timer’
previously described in ‘launch recovering timer’ of section 6.3.1 Auto-recloser
behaviour.
13. unlock delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimml recovering
timer’ previously described in ‘lock of auto-recloser’ of section 6.3.1 Auto-recloser
behaviour.
14. manual close delay (range [1 s, 600 s], step 1 s): corresponds to ‘reclaimmc
recovering timer’ previously described in ‘lock of auto-recloser’ of section 6.3.1 Auto-
recloser behaviour.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
obsolete (12)
(13)
)
(14)
FIGURE 291: SETTING AUTO-RECLOSER FEATURES

• The two attributes "functioning mode (1 ph trip)" and "functioning mode (3 ph trip)"
must not be both set to "Not used" value
• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P-3P", then the following rules
must be respected :
- "1st period monophased" < "2nd period triphased"
- "1st period monophased" < "3rd period triphased"
- "1st period monophased " < "4th period triphased"
• If "functioning mode (1 ph trip)" value is set to "1P-3P-3P", then the following rules
must be respected :
- "1st period monophased" < "3rd period triphased"
• If "functioning mode (1 ph trip)" value is set to "1P-3P", then the following rule must be
respected :
• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P-3P", then the following rules
must be respected :
- "1st period triphased" < "2nd period triphased"
- "1st period triphased" < "3rd period triphased"
- "1st period triphased" < "4th period triphased"
• If "functioning mode (3 ph trip)" value is set to "3P-3P-3P", then the following rules
must be respected :
- "1st period triphased" < "3rd period triphased"
• If "functioning mode (3 ph trip)" value is set to "3P-3P", then the following rule must be
respected :
• If "functioning mode (1 ph trip)" value is different from "Not used", then the "circuit-
breaker type" must be set to "Single phase CircuitBreaker"
• If "functioning mode (3 ph trip)" value is set to "Not used", then the "circuit-breaker
type" must be set to "Single phase CircuitBreaker"
To assume previous described behaviour, when adding an auto-recloser, some mandatory
datapoints are automatically created at function level and must be configured (see section 5
DEFINING DATAPOINT):
1. Autorecloser flt: is a MPS datapoint, given the failure reason of auto-recloser
function. This a system datapoint whose available states are:
− State0: failure due to the synchrocheck
− State1: failure to hardware, lock of device or another running automation linked to

the device
− State2: failure due to interlocking function
− State3: no failure
2. Auto-recloser st: is a MPS datapoint which gives the status of the auto-recloser
function. This is a system datapoint whose available states are:
− State0: auto-recloser is in service, unlocked and no cycle is in progress
− State1: auto-recloser is waiting CB opening
− State2: the first single-phase cycle is in progress
− State3: the first 3-phases cycle is in progress
− State4: the second 3-phases cycle is in progress
− State5: the third 3-phases cycle is in progress
− State6: the fourth 3-phases cycle is in progress
− State7: the auto-recloser is waiting CB closing
− State8: the Reclaimc timer is launched
− State9: auto-recloser locking due to a max number of reclosing cycles
− State10: an auto-recloser locking
− State11: the reclaimml timer is launched
− State12: the reclaimmc timer is launched

3. Force trip 3 P: is a SPC, used during a 3 phase cycle as mentioned in ‘Waiting CB
opening’ in section 6.3.1 Auto-recloser behaviour
4. on/off : is a status DPS, corresponding to in / out of service status of the auto-recloser
5. Trip 3 phases: is a SPS, giving information 3-phase trip provided by a relay
(1)
(2)
(3)
(4)
(5)
FIGURE 292: AUTO-RECLOSER MANDATORY DATAPOINTS

To assume previous described behaviour, when adding an auto-recloser, some optional

datapoints can be created at function level and must be configured (see section 5 DEFINING
DATAPOINT):
1. blocking SPS: corresponds to the ‘AR_BLOCKING’ BI described in section 6.3.1
Auto-recloser behaviour
2. lock/reinit: is a SPS used to lock / unlock the auto-recloser via SPS. Corresponds to
the ‘AR_LOCK’ signal described in section 6.3.1 Auto-recloser behaviour
3. Trip PhA: is a SPS corresponding to trip status for pole A
4. Trip PhB: is a SPS corresponding to trip status for pole B
5. Trip PhC: is a SPS corresponding to trip status for pole C
6. lock/reinit SPC: Signal to lock/unlock the auto-recloser via SPC. Corresponds to the
‘AR_LOCK’ signal described in section 6.3.1 Auto-recloser behaviour
7. on/off ctrl DPC: to control in/out of service of the auto-recloser via DPC
8. on/off ctrl DPS: to control in/out of service of the auto-recloser via DPS
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 293: AUTO-RECLOSER OPTIONAL DATAPOINTS

• If "functioning mode (1 ph trip)" value is different from "Not used", then at least one of
the three SPS datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is mandatory
• If "functioning mode (1 ph trip)" value is set to "Not used", then none of the three SPS
datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is allowed
• The two datapoints { "on/off ctrl DPC", "on/off ctrl DPS" } are mutually exclusive and,
at least one of them is mandatory
• The two datapoints { "lock/reinit SPC", "lock/reinit SPS" } are mutually exclusive. If the
"unlocking way" attribute value is set to "Reinitialization" or "Both ways" then, at least
one of the two datapoints is mandatory
To assume previous described behaviour, when adding an auto-recloser, some mandatory
datapoints are automatically created at circuit-breaker level and must be configured (see
section 5 DEFINING DATAPOINT):
1. CB Healthy: corresponds to the ‘CB HEALTHY’ BI described in
section 6.3.1 Auto-recloser behaviour
(1)
FIGURE 294: AVAILABLE CB HEALTHY PRE-DEFINED DATAPOINTS FOR CIRCUIT-BREAKER

6.4 Defining a Tap changer built-in function

6.4.1 Tap changer behaviour
The control sequence of a transformer is described in section 6.5 of chapter C264/EN FT.
The control of a transformer is done via tap changer built-in function and can be performed in
the three modes “Direct Execute”, ”SBO once” and “SBO many mode” (refer to section 5.1.8
Overview of control sequence processing).
TCIP feature:
The TCIP input information is used to confirm the right execution of the low/raise execution.
When adding a TCIP at tap changer level, the two configurable delays must be set at TCIP
datapoint level for the correct TCIP management:
1. reset confirmation delay (range [0 s, 120 s], step 100 ms]: this delay corresponds to
time-out TR given in section 5.1.2.1 Persistence filtering of chapter C264/EN FT.
2. set confirmation delay (range [0 s, 120 s], step 100 ms]: this delay corresponds to
time-out TS given in section 5.1.2.1 Persistence filtering of chapter C264/EN FT.
3. start confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must
appear before the time-out of this delay
4. stop confirmation delay (range [1 s, 60 s], step 100 ms): the TCIP information must
disappear before the time-out of this delay
(1)
(2)
(3)
(4)
FIGURE 295: SETTING TCIP GENERAL ATTRIBUTES OF A TCIP

TPI feature:
Because the TCIP input information is not always configured, the tap control is performed by
using only the Tap Position Indication (TPI) value to verify the right execution of the request.
The TPI value must change in the given delay.
Control of a transformer with TCIP
This functionality is described in section 6.5.2.1 of chapter C264/EN FT.
Control of a transformer without TCIP
Suppression, Forcing or Substitution of the TPI

6.4.2 Creating a tap changer built-in function
Tap changer is considered as a function because it verifies maximal and minimal useable
positions of tap position indicator. It is like a sub-module of transformer module and owns the
tap position indicator and optional controls (Raise/Lower, Goto Min/Max).
To create a tap-changer built-in function, add it from object entry available at transformer
module level (1).
(1)
FIGURE 296: ADDING A TAP CHANGER BUILT-IN FUNCTION TO TRANSFORMER

When adding a tap changer function, the following general attributes must be updated:
1. short name and long name of the tap changer used for logging, alarms ...
2. minimal usable position (range [1, 64], step 1).
3. maximal usable position (range [1, 64], step 1): must be greater than attribute (2).
4. execution timeout (range [0, 60 s], step 100 ms): It is the maximum delay in which
tap position must have changed relatively to the current tap control in progress. If
delay expired bad acknowledgement is sent for tap control.
(1)
(2)
(3)
(4)
obsolete
C0244ENb
FIGURE 297: SETTING TAP CHANGER ATTRIBUTES

When adding a tap changer function, the mandatory datapoint ‘Tap position indicator’ (TPI)
is automatically created at function level (8).
The following table gives inputs and outputs tap changer’s features controlled by the
computer. For each datapoint its SCE identification is given by a number, referenced in the
following figure.
To configure correctly the tap changer of a transformer module:
Tap changer for transformer

OUTPUTS INPUTS
DEVICE (2) DPC raise/lower (8) TPI value

CONTROL (1) DPC (optional) goto (7) SPS (optional) tap change
min/max in progress
DEVICE (4) SPC (optional) transformer (i) SPS (optional) selection

SELECTION selection position information
(HARDWARE)
(i) This SPS is a generic one added at transformer module level and configured as
feedback of SPC transformer selection (4).
1. Goto min/max DPC: this datapoint is not managed by the tap changer built-in
function. If it is needed an ISAGRAPH automation has to be used.
2. Raise/lower DPC: this datapoint is managed by the tap changer built-in function.
3. MCB open SPC: this datapoint is managed by the tap changer built-in function.
4. TAP Select SPC: this datapoint is managed by the tap changer built-in function
5. Higher position: this SPS is not taken into account by the tap changer built-in
6. Lower position: this SPS is not taken into account by the tap changer built-in
7. Tap in progress: this SPS is taken into account by the tap changer built-in function.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 298: AVAILABLE PRE-DEFINED DATAPOINTS FOR TAP CHANGER

• "Raise/lower DPC" datapoint must have its profile attribute “SBO mode” set to "SBO
Operate Many"
6.5 Defining an Automatic Voltage Regulation (AVR) built-in function

6.5.1 AVR behaviour
The AVR built-in function is described in section 7.1.4 of chapter C264/EN FT.
6.5.2 Creating an AVR function
AVR (or ATCC) is a complex built-in function for it concerns specific modules, bays, voltage
levels (transformer, busbar, voltage level) constituting the substation. At SCE level, AVR
modelling is split in different objects (ATCC function needs) located under each electrical
component relevant to it. The set of these objects corresponds to the parameterisation of
AVR substation built-in function.
Adding ‘ATCC function needs’ object under electrical component permits automatic
datapoint creation. These datapoints concerns AVR real-time information and controls
relevant to this electrical component.
Voltage levels managed by AVR do not need specific datapoints for the AVR function. So,
specific attributes put at voltage level objets are preferred to give extra AVR function needs
for each voltage level.
In the following sub-sections, required datapoints for AVR function are prefixed with an
identifier, refered in section 6.5.1.1 of chapter C264/EN FT.
• If there is no ATCC under the Substation, then:
− a "Voltage level" must not have its "ATCC existence" attribute set to "Yes".
− the "ATCC fct needs" is allowed neither under a "transformer" nor under a
"BusBar".
• If there is an "ATCC fct needs" under a "transformer", then :
− the "Tap changer" with its "Raise/lower DPC" datapoint are mandatory.
− one of the two datapoints { "MCB position DPS", "MCB position SPS" } is
mandatory. They are mutually exclusive
− the "transformer" must be linked to a Voltage level through one and only one of the
relations { "has its primary on", "has its secondary on" }. The Voltage level must be
different from the one under which the transformer is located.
6.5.2.1 Defining ATCC function needs at substation level
The entry point of ATCC configuration is done at substation level.
This is done via the “Objects entry” window at substation level by clicking on mouse’s right
button.
(1)
FIGURE 299: ADDING AN AVR FUNCTION AT SUBSTATION LEVEL

Once added, ATCC features must be set at SCE level:
1. Fill the relation ‘is managed by’, giving which computer runs and supervises AVR
function at substation level.
2. short name and long name of the AVR used for logging, alarms ...
‘General’ attributes:
‘calculation’ attributes
3. calculation period: corresponds to parameter “period of AVR calculation” listed in
section 7.1.4.7 (List of configurable parameters) of chapter C264/EN FT.
4. calculation mode: corresponds to parameter “calculation mode” listed in section
7.1.4.7 of chapter C264/EN FT.
‘Homing’ attributes
5. active homing: corresponds to parameter “Homing ON/OFF” listed in section 7.1.4.7
(List of configurable parameters) of chapter C264/EN FT.
6. homing deadband: corresponds to parameter “percentage of the Homing deadband”
listed in section 7.1.4.7 of chapter C264/EN FT.
‘ATCC mode changing’ attributes
7. mode on group interconnection: corresponds to parameter “mode group
interconnexion” listed in section 7.1.4.7 of chapter C264/EN FT.
8. mode on bay in local: corresponds to parameter “mode if bay in local“listed in section
‘Compounding’ attributes
9. compounding method: corresponds to parameter “compounding method” listed in
section 7.1.4.7 of chapter C264/EN FT.
Delays’ attributes:
‘Nominal’ attributes
10. fixed initial tap delay: corresponds to parameter “initial tap time delay fixed/or not”
11. initial tap delay (in ms): corresponds to parameter “initial tap time delay:T1” listed in
12. inter tap delay (in ms): corresponds to parameter “inter tap time delay:T2 listed in
‘Homing’ attributes
13. homing initial tap delay (in ms): corresponds to parameter “Initial tap time delay:T3”
14. homing inter tap delay (in ms): corresponds to parameter “Inter tap time delay:T4”
listed in section 7.1.4.7 of chapter C264/EN FT
‘Hunting’ attributes
15. hunting window (in ms): corresponds to parameter “Hunting window : T5” listed in
16. opposite max tap changes: corresponds to parameter “Maximal number of
successive taps in opposite direction for hunting (default value: 4 )” listed in section
7.1.4.7 of chapter C264/EN FT
‘Inhibition’ attributes
‘Inhibition conditions’ attributes

17. max voltage difference (ratio): corresponds to parameter “Percentage of accepted
difference between secondary voltages for transformers in the same group. (default
value: +2%)” listed in section 7.1.4.7 of chapter C264/EN FT
18. tolerable nominal under voltage (ratio): corresponds to parameter “Under-voltage:
percentage of nominal voltage under which AVR or Homing is inhibited (default value:
80%)” listed in section 7.1.4.7 of chapter C264/EN FT
19. tolerable nominal over voltage (ratio): corresponds to parameter “Over-voltage:
percentage of nominal voltage over which AVR or Homing is inhibited (default value:
120%)” listed in section 7.1.4.7 of chapter C264/EN FT.
‘Busbar voltage’ attributes
Coefficients for busbar voltage calculation attributes: correspond to parameter “Coefficients
for 1, 2, 3 and 4 transformers (default value: 1)” listed in section 7.1.4.7 of chapter C264/EN
FT
20. voltage coefficient for 1 transfo
21. voltage coefficient for 2 transfos
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
FIGURE 300: SETTING GENERAL FEATURES OF AN AVR

(10)
(11)
(12)
(13)
(14)
(15)
(16)
FIGURE 301: SETTING ‘DELAYS’ ATTRIBUTES OF AN AVR
(17)
(18)
(19)
FIGURE 302: SETTING ‘INHIBITION’ ATTRIBUTES OF AN AVR
(20)
(21)
(22)
(23)
FIGURE 303: SETTING BUSBAR VOLTAGE ATTRIBUTES OF AN AVR

When adding an AVR to a substation, the following mandatory datapoints are automatically
created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Sub 1) ATCC clear alarm SPC
(DPT_Sub 2) ATCC on/off control SPC
(DPT_Sub 3) AVR defect alarm SPS
(DPT_Sub 4) DBI override SPS
(DPT_Sub 5) ErrorLog SPS
(DPT_Sub 6) On/off SPS
(DPT_Sub 7) Target unreached SPS
(DPT_Sub 1)
(DPT_Sub 2)
(DPT_Sub 3)
(DPT_Sub 4)
(DPT_Sub 5)
(DPT_Sub 6)
(DPT_Sub 7)
C0246ENb
FIGURE 304: MANDATORY DATAPOINTS FOR AVR AT SUBSTATION LEVEL

6.5.2.2 Defining ATCC function needs at voltage level
For each voltage level containing a transformer concerned by an AVR function, extra AVR
configuration must be done.
This is done under SCE at voltage level, by setting the attribute ‘ATCC existence’ to ‘Yes’
(1).
Then an extra ‘ATCC’ tab-pane appears with the following attributes to update:
‘voltage targets’ attributes
2. voltage target by default: corresponds to (param 40) listed in section 7.1.4.7 of
chapter C264/EN FT.
3. voltage target 1: corresponds to parameter “Target voltage 1” listed in section 7.1.4.7
of chapter C264/EN FT.
‘regulation’ attributes
8. voltage target ramping rate (kV/mn): corresponds to parameter “Target voltage
ramping rate” listed in section 7.1.4.7 of chapter C264/EN FT.
9. max tap change rate (kV/min): corresponds to parameter “Max voltage change rate”
10. voltage deadband to end tapping: corresponds to parameter “Voltage deadband1”
11. voltage deadband to initiate tapping: corresponds to parameter “Voltage
deadband2” listed in section 7.1.4.7 of chapter C264/EN FT.
When a voltage level is concerned by an AVR function, do not forget to set correctly its
attribute ‘nominal value (kV)’ (refer to section 6.1.3 Defining a Voltage level). It is used for
transformer nominal ratio computation.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
FIGURE 305: SETTING AVR FUNCTION ATTRIBUTES AT VOLTAGE LEVEL

6.5.2.3 Defining ATCC function needs at busbar level

For each busbar bay concerned by an AVR function, extra AVR configuration must be done.
For details about busbar bay creation, refer to section 6.1.4 Defining a Bay.
This is done via the “Objects entry” window at busbar level by clicking on mouse’s right
button.
(1)
FIGURE 306: ADDING AVR FUNCTION NEEDS AT BUSBAR LEVEL

Once added, AVR busbar features must be set at SCE level:
1. setpoint ponderation: corresponds to parameter “SetPoint value” listed in section
2. priority: corresponds to parameter “Priority“listed in section 7.1.4.7 of chapter
C264/EN FT.
‘line drop compensation (if setpoint adjustement)’ attributes
3. resistive coefficient: corresponds to parameter “Resistive multiplier” listed in section
4. reactive coefficient: corresponds to parameter “Reactive multiplier” listed in section
‘line drop compensation (if voltage adjustement)’ attributes
5. transfo-busbar resistive coefficient: corresponds to parameter “Resistive multiplier“
6. transfo-busbar reactive coefficient: corresponds to parameter “Reactive multiplier“
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 307: SETTING GENERAL BUSBAR FEATURES OF AN AVR

When adding an AVR function needs at busbar level, the following mandatory datapoints are
automatically created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Bb 1) ATCC inhibited
(DPT_Bb 2) ATCC inv module
(DPT_Bb 3) ATCC inv voltage
(DPT_Bb 4) ATCC max transfo
(DPT_Bb 5) ATCC on/off
(DPT_Bb 6) ATCC on/off ctrl
(DPT_Bb 7) ATCC targ 1 ctrl
(DPT_Bb 12) ATCC target 1
(DPT_Bb 17) ATCC to target
(DPT_Bb 18) BusBar voltage
(DPT_Bb 1) (DPT _Bb 2)
(DPT_Bb 3) (DPT_Bb 4)

C0348ENa
FIGURE 308: MANDATORY DATAPOINTS FOR AVR AT BUSBAR LEVEL

6.5.2.4 Defining ATCC function needs at transformer level

For details about transformer bay (and subsequent transformer module) creation, refer to
sections 6.1.4 Defining a Bay.
For each transformer concerned by an AVR function, extra AVR configuration must be done
at several levels:
• Set properly the following features for transformer module:
− ‘Transformer type’ attribute: corresponds to parameter “AVR transformer type“

− ‘Power value’ attribute: (range [1, 300 MVA]): corresponds to parameter “AVR
transformer rating” listed in section 7.1.4.7 of chapter C264/EN FT.
− ‘Impedance’ attribute, whose unit is a percent of value for S=100 MVA (range
[0,01 to 24,99 by step 0,01): corresponds to parameter “AVR transformer
impedance on nominal tap on 100 MVA base” listed in section 7.1.4.7 of chapter
C264/EN FT.
− MCB position SPS or DPS is mandatory
• Add and configure a Tap-changer built-in function for the transformer module (refer to
section 6.4 Defining a Tap changer built-in function), with the following features:
− Raise/Lower DPC is mandatory
− Tap in progress SPS is mandatory
− MCB open SPC is mandatory
• Add and configure an ‘ATCC fct needs’ object for transformer, via the “Objects entry”
window at transformer module level by clicking on mouse’s right button (1):
(1)
FIGURE 309: ADDING AVR FUNCTION NEEDS AT TRANSFORMER LEVEL

Once added, the features of AVR function needs for transformer must be set at SCE level:
‘Tpi range’ attributes
1. up range: corresponds to parameter “AVR tapping range – upper value” listed in
2. down range: corresponds to parameter “AVR tapping range – lower value” listed in
‘Inhibition conditions’ attributes:
3. Overcurrent ratio: corresponds to parameter ”Overcurrent setting” listed in section
(1)
(2)
(3)
FIGURE 310: SETTING GENERAL TRANSFORMER FEATURES OF AN AVR

When adding AVR function needs at transformer level, the following mandatory datapoints
are automatically created and must be configured (see section 5 DEFINING DATAPOINT):
(DPT_Trf 1) ATCC on/off
(DPT_Trf 2) ATCC homing
(DPT_Trf 3) ATCC hunting
(DPT_Trf 4) TAP bad TCIP
(DPT_Trf 5) TAP long TCIP
(DPT_Trf 6) TAP invalid
(DPT_Trf 7) Run away
(DPT_Trf 8) ATCC disc eqpt
(DPT_Trf 9) ATCC local bay
(DPT_Trf 10) MCB trip
(DPT_Trf 11) ATCC overcurrent
(DPT_Trf 12) ATCC overvoltage
(DPT_Trf 13) ATCC low-voltage
(DPT_Trf 14) ATCC inv voltage
(DPT_Trf 15) Second. voltage
(DPT_Trf 16) Second. current
(DPT_Trf 17) Second. active P
(DPT_Trf 18) Second. react. Q
(DPT_Trf 1) (DPT_Trf 2)
C0349ENa
FIGURE 311: MANDATORY DATAPOINTS FOR AVR AT TRANSFORMER LEVEL

6.5.2.5 Defining an electrical topology for AVR function
For correct behaviour of AVR function, electrical topology of the LV side, including
connection of the transformer to the busbar and coupling of busbars into the LV level must
be defined.
Any electrical topology can be defined by modules interconnected by nodes.
A node is in relation with at least on module. The most common “node” is busbars.
Electric modules are mostly dipoles. Switchgears and circuit-breakers are connected to two
nodes. Special module cases are:
• motor/generator that are connected to only one node,
• Line arrival that is a node,
• special (german) double switch that is in fact association of earth switch and
disconnector,
• transformer connected to three nodes but the third node is reserved to neutral
compensation.
At SCE level, nodes are special attributes of module, whose values are given by integers.
Each identified node in the electrical topology has a unique arbitrary value. Two
interconnected modules share the same node value. The best practice to value nodes is to
do it directly from the substation electrical diagram.
obsolete
FIGURE 312: IDENTIFYING NODES IN ELECTRICAL DIAGRAM (E.G.)

Then, this manual approach of nodes identification must be projected at SCE electrical
object level:
• “Busbar” bay, where one node reference must be filled (1),
• “External line” module of “Feeder” bay, where one node reference must be filled (2),
• “Circuit-breaker” and “Switchgear” module, where two node references must be filled
(3),
• “Transformer” module, where at least two node references must be filled, and a extra
one in case of neutral compensation (4),
• “Capacitor” and “inductor” module, used for neutral compensation , where one node
reference must be filled (5) and corresponds to the neutral node of the associated
transformer. Attention !! il manque la figure illustrant cet exemple
(1)
FIGURE 313: SETTING BUSBAR NODE REFERENCE (AVR FUNCTION)

(2)
FIGURE 314: SETTING EXTERNAL LINE NODE REFERENCE (AVR FUNCTION)
(3)
FIGURE 315: SETTING CIRCUIT-BREAKER NODE REFERENCES (AVR FUNCTION)
(4)
FIGURE 316: SETTING TRANSFORMER NODE REFERENCES (AVR FUNCTION)

6.6 Defining an electrical regulation by user function

PACiS allows the user to configure specific control sequences or automations (e.g. switching
sequences, busbar transfer, load shedding, GIS-pressure supervision, etc …) during the
configuration phase.
To do that, there are two main solutions:
• Using ISaGRAF workbench for slow automations, where the execution of the
automation is cyclic, based on a cycle that can not be less than 50 ms.
• Using extended logical function modelling (boolean, timer, bistable functions) via FBD
workbench, where the execution is event-driven.
User function can be put at any level of the electrical topology except Site. Moreover, slow
automation is unavailable at module level. User function must always specify on which
computer it runs.
Extra solutions for simpler needs exist at configuration level (they could be seen as
restriction of particular FBD functions):
• Group modelling: SPS production based on a pre-defined boolean function working on

a set of datapoint.
• xPS-xPC association: on a particular state of xPS, ability to control a given xPC.
• SPS-DPS association: DPS production based on the synthesis of 2 SPS.
• Interlocking definition: production of virtual SPS datapoints used to control opening

and/or closure of modules. These virtual datapoints are defined through specific FBD
logical diagrams where inputs are generally breaker and switch positions.
• Automatic/manual dependency set at control level (SPC, DPC or SetPoint): when a

control is linked to a SPS or DPS via the automatic/manual dependency, control is
refused if the SPS (resp. DPS) is in the SET (resp. CLOSED) state.
6.6.1 Defining a FBD fast automation
To define a FBD fast automation, the three following steps must be done:
• FBD interface definition at SCE level:
− FBD function ‘header’ creation.
− creation of input plugs, that will be linked to SPS, DPS, MV, MPS, SPC or DPC
(fast automations take into account the logical value of these datapoints, defined
for interlocking management), added as sub-objects to this header.
− creation of output plugs, that will be linked to SPC, DPC (control of relays) or to a
SPS (production of SPS real-time value), added as sub-objects to this header.
• FBD body (coding in PSL) definition via launching at SCE level the FBD editor
(contextual menu on the FBD interface object) and doing diagram edition of boolean,
timer and bistable functions, and links to input/output plugs.
• Effective linking of input and output plugs to existing datapoints

6.6.1.1 Creating a FBD fast automation (header definition)
The addition of a FBD fast automation is done via the “Objects entry” window at any level of
the electrical topology (except Site) by clicking on mouse’s right button.
For more details about electrical topology creation, refer to section 6.1 Defining an electrical
topology.
FIGURE 317: ADDING A FBD FAST AUTOMATION (E.G. FOR FEEDER BAY LEVEL)
Once added, FBD fast automation features must be set at SCE level:
1. Fill the relation ‘runs on’, giving which computer PLC will manage the automation. This
relation is automatically filled by SCE if FBD automation is located under a bay whose
computer manager has ever been entered (for details about computer manager of a
bay refer to section 6.1.4 Defining a Bay).
2. short name and long name of the fast automation used for internal SCE
identification.
(1)
(2)
FIGURE 318: SETTING FBD FAST AUTOMATION FEATURES

6.6.1.2 Creating FBD input plug (header definition)
The addition of a FBD input plug is done via the “Objects entry” window at the FBD
automation level by clicking on mouse’s right button.
FIGURE 319: ADDING A FBD INPUT PLUG

Once added, FBD input plug features must be set at SCE level:
1. short name and long name of the fast automation used for identification in FDB
editor
(1)
FIGURE 320: SETTING GENERAL FBD INPUT ATTRIBUTES

6.6.1.3 Creating FBD output plug (header definition)
The addition of a FBD output plug is done via the “Objects entry” window at the FBD
FIGURE 321: ADDING A FBD OUTPUT PLUG

Once added, FBD output plug features must be set at SCE level:
1. short name and long name: used for identification in FDB editor
(1)
FIGURE 322: SETTING FBD OUTPUT PLUG ATTRIBUTES

6.6.1.4 Using FBD editor (body definition)
The launching of the FBD editor is done at FBD automation level via its contextual menu
(right click).
(1)
FIGURE 323: LAUNCHING FBD EDITOR

Once launched, FBD editor allows diagram edition of the automation. For details about FBD
user manual refer to <the PACiS-SCE Documentation>
FIGURE 324: USING FBD EDITOR

6.6.1.5 Linking datapoints to FBD inputs and outputs
To assign a datapoint to a FBD input:
• Add the relation ‘uses <XXX>’ (1) at FBD input level, where XXX corresponds to the
datapoint kind (SPS, DPS, MPS, MV, SPC or DPC)
• Fill the relation with the relevant datapoint
(1)
FIGURE 325: LINKING A FBD INPUT TO A DATAPOINT

To assign a datapoint to a FBD output:
• Add the relation ‘controls <XXX>’ (1) or ‘produces SPS’ at FBD input level, where XXX
corresponds to the control datapoint kind (SPC or DPC)
(1)
FIGURE 326: LINKING A FBD OUTPUT TO A DATAPOINT

Several datapoints can be assigned to the same FBD output.
• For one "FBD input" plug, only one relation is allowed.
• For one "FBD output" plug:

- the count of relations towards DPC or SPC datapoints must be ≤ 4
- the count of relations towards SPS datapoints must be ≤ 4
• A "DPC" or "SPC" datapoint can be linked to an Output plug of a FBD Automation

through the relation "controls DPC" or "controls SPC". These relations are not
compatible with the following ones:
- relations defining the Control Source, except the "…wired on" relation(s)
- relation "has for UCA2/IEC address" whatever the link type
- relation "has for SCADA address".
- relation "is controlled on state change of".
- relation "has for AutoManu dependency".
-relation "has for feedback".
- relation "has for local/remote dependency".
6.6.2 Defining an ISaGRAF slow automation

A "DPC" or "SPC" datapoint can be linked to an Input plug of a FBD Automation through the
relation "uses DPC" or "uses SPC". These relations are not compatible with the following
ones:
- relations defining the Control Source : "…wired on"
- relation defining the Control Source : "has for IED address"
Slow automation modelling is articulated around a ‘Slow automation’ object that corresponds
to an ISaGRAF project.Slow automation can own datapoints for status, control of automation
itself (automation management). For instance, a load shedding automation can have a
control to put it in/out of service and a relevant status.
They also reference via links datapoints located in system or electrical topologies. There are
two kinds of link:
• ‘client’ link, that means that the slow automation uses the datapoint that is acquired or
managed outside the ISaGRAF automation. For instance, the load shedding
automation can be client of some ‘circuit-breaker status’ input datapoints and some
‘circuit-breaker control’ output datapoints.
• ‘server’ link, that means that the slow automation produces or manages the datapoint.
For instance, a slow automation can be used to produce the sum of feeder
measurements. This sum is also a measurement located at voltage level for instance.
To define a slow automation, the three following steps must be done:
• interface definition of the slow automation at SCE level:
− slow automation ‘header’ creation.
− if required, creation of datapoints at slow automation level, used for the function
management.
− creation of the client links for the slow automation.
− creation of the server links for the slow automation.
• slow automation body definition via launching at SCE level the ISaGRAF editor
(contextual menu on the slow automation interface object) and using available
languages and previously client/server defined links.
• Effective client/server links entering to existing datapoints.

6.6.2.1 Creating an ISaGRAF slow automation (header definition)

The addition of an ISaGRAF slow automation is done via the “Objects entry” window at any
level of the electrical topology (except Site and module) by clicking on mouse’s right button.
topology.
FIGURE 327: ADDING AN ISAGRAF SLOW AUTOMATION AUTOMATION

(E.G. FOR FEEDER BAY LEVEL)
Once added, ISaGRAF slow automation features must be set at SCE level:
1. Fill the relation ‘runs on’, giving which computer PLC will manage the automation. This
relation is automatically filled by SCE if slow automation is located under a bay whose
computer manager has ever been entered (for details about computer manager of a
bay refer to section 6.1.4 Defining a Bay)
2. short name and long name of the slow automation used for logging and alarm
(1)
(2)
FIGURE 328: SETTING ISAGRAF SLOW AUTOMATION FEATURES

6.6.2.2 Adding specific datapoints to slow automation (interface definition)

The addition of a slow automation datapoint is done via the “Objects entry” window at slow
DATAPOINT.
FIGURE 329: ADDING DATAPOINTS TO SLOW AUTOMATION

Slow automation datapoint is integrally produced or managed by the slow automation and
subsequently by ISaGRAF. It can not be linked to another acquisition or control source and
the ISaGRAF project must update/run its value changes or controls. Slow automation input
datapoints are stored in a non-volatile memory at computer level to restart on their last
known values in case of computer reboot.
6.6.2.3 Creating ISaGRAF client link (interface definition)

The addition of an ISaGRAF client is done via the “Objects entry” window at the slow
automation level by clicking on mouse’s right button and adding a ‘is client of’ relation.
Choose the correct relation depending on datapoint kind that will be used.
FIGURE 330: ADDING AN ISAGRAF CLIENT LINK

6.6.2.4 Linking a datapoint to an ISAGRAF client link

To link a datapoint to an ISAGRAF client link the relation 'is client of' must be defined. For
that double click this relation (1). The Relation Link Editor is then displayed. By expanding
the tree view all the available SPS datapoints are listed. Click the one you want to link (2)
then click the Ok button. (In the example given hereafter the link has be done with the
VoltageLevel SPS datapoint). The relation is then displayed as 'defined' (3).
(1)
(2)
(3)
FIGURE 331
6.6.2.5 Defining Isagraf IO prefix for an input

By clicking this 'is client of' relation the associated attributes window is displayed. Only the
'Isagraf IO prefix' attribute (4) can be modified by the user. This attribute defines the prefix
of the identifier of this datapoint when used in ISAGRAF workbench as an input signal of this
automation. It is built by concanetating the prefix, an underscore (if the prefix exists) and the
input IO reference automatically given by the SCE: In the example given hereafter the
identifier of this link will be: MY_INPUT_PREFIX_in_2
(4)
FIGURE 332: DEFINING ISAGRAF IO PREFIX FOR AN INPUT

• The first character must be a letter
• The following characters must be either a letter in upper case, either a digit or an
underscore.
• The maximum length is 80 characters

6.6.2.6 Creating ISaGRAF server link (interface definition)
The addition of an ISaGRAF server is done via the “Objects entry” window at the slow
automation level by clicking on mouse’s right button and adding a ‘manages’ relation.
Choose the correct relation depending on datapoint kind that will be managed.
FIGURE 333: ADDING AN ISAGRAF CLIENT LINK

6.6.2.7 Linking a datapoint to an ISAGRAF server link

To link a datapoint to an ISAGRAF server link the relation 'manages' must be defined. For
that double click this relation (1). The Relation Link Editor is then displayed. By expanding
the tree view all the available DPS datapoints are listed. Click the one you want to link (2)
then click the Ok button. (In the example given hereafter the link has be done with the
Substation DPS datapoint).
The relation is then displayed as 'defined' (3).
(1)
(2)
(3)
FIGURE 334: LINKING A DATAPOINT TO AN ISAGRAF SERVER LINK

6.6.2.8 Defining Isagraf IO prefix for an output

By clicking this manages' relation the associated attributes window is displayed. Only the
'Isagraf IO prefix' attribute (4) can be modified by the user. This attribute defines the prefix
of the identifier of this datapoint when used in ISAGRAF workbench as an output signal of
this automation. It is built by concanetating the prefix, an underscore (if the prefix exists) and
the output IO reference automatically given by the SCE: In the example given hereafter the
identifier of this link will be: My_Output_Prefix_out_1
(4)
FIGURE 335: DEFINING ISAGRAF IO PREFIX FOR AN OUTPUT

• The following characters must be either a letter in upper case, either a digit or an
underscore.
• The maximum length is 80 characters

6.6.2.9 Using ISaGRAF editor (body definition)
The launching of the ISaGRAF editor is done at slow automation level via its contextual
menu (right click).
(1)
FIGURE 336: LAUNCHING ISAGRAF EDITOR

Once launched, ISaGRAF editor allows diagram edition of the automation. For details about
ISaGRAF workbench and SCE datapoint coupling, refer to section 8 Annex A: Coupling SCE
data model and ISaGRAF.
FIGURE 337: USING ISAGRAF EDITOR

6.6.3 Defining a group
A group is a logical OR, AND, NOR or NAND combination of components whose kind is
SPS, DPS or groups. A component can belong to several groups. Resulting datapoint
associated to a group is a SPS object called ‘Group SPS’ in data modelling.
Group SPS can only belong to bays or modules. The computer that manages the bay (of
eventually the bay of the module) always computes it. Its composition description is done via
linking it to SPS, DPS, or Group SPS.
A group SPS can be seen as a particular fast automation reduced to one boolean function
with one implicit output plug (the group SPS itself) and input plugs corresponding to each
component of the group.
The addition of a group SPS is done via the “Objects entry” window at bay or module level of
the electrical topology by clicking on mouse’s right button.
topology.
FIGURE 338: ADDING A GROUP SPS (E.G. FOR FEEDER BAY LEVEL)
Once added, Group SPS features must be set at SCE level, as SPS datapoint. For details
about SPS datapoint configuration, refer to section 5.1.2 Defining a SPS datapoint.
Nevertheless, the specific attribute ‘group type’ (1) must be set for the group. It corresponds
to the logical function (OR, AND, NOR or NAND) applied on all the components of the group.
(1)
FIGURE 339: SETTING ‘GROUP TYPE’ ATTRIBUTE OF A GROUP SPS

To assign a component to a group (SPS, DPS or group):
• Add the relation ‘contains the <XXX>’ (1) at Group SPS level, where XXX corresponds
to the datapoint kind (SPS or DPS)
(1)
FIGURE 340: ADDING A COMPONENT TO A GROUP

6.6.4 Controlling xPC by xPS change of state

For specific needs, some SPS or DPS can acts on SPC or DPC. This relation is called xPS-
xPC association. Such an acted xPC does not necessary need a channel for wiring. It can be
a xPC used for automation management for instance.
The link defines for each state of the xPS which order must be sent.
To create such a relation:
• Add the relation ‘controls on state change’ (1) at SPS/DPS level; two relations are
available depending on control kind to act (SPC or DPC). Choose the correct one.
• Fill the relation with the relevant SPC or DPC (2).
• Set the relation attributes (3) giving for each state of the xPS, the order to send: None,
Open (resp. Off) or Close (resp. On) for DPC (resp. SPC).
(1)
(2)
(3)
FIGURE 341: CONTROLLING XPC THROUGH XPS (E.G.)

6.6.5 Producing a DPS from two SPS

For specific needs, two SPS (one for open state, and the other for closed state) can be used
to manage a DPS. This relation is called SPS-DPS association.
To produce a DPS from two SPS:
• Create the three datapoints and configure them (see section 5 DEFINING
DATAPOINT)
• At the DPS level, add the relations ‘has open state given by’ (1) and ‘has closed state
given by’ (2)
• Fill the two relations with the previously created SPS datapoint
(1)
(2)
FIGURE 342: PRODUCING DPS FROM 2 SPS (E.G.)

6.6.6 Defining interlocking
Any DPC (or SPC) belonging to a bay or module can have interlocking equation for opening
order (Off order for SPS) and/or closing order (On order for SPC).
Interlocking equation corresponds to a logical function that must be ‘true’ to send the order.
In data modelling, interlocking equation are put under SPC or DPC by adding specific SPS:
• ‘Off interlock SPS’ and ‘On interlock SPS’ for SPC
• ‘Open interlock SPS’ and ‘Close interlock SPS’ for DPC

These SPS contain the logical function definition of the interlocking that is coded with the
FBD editor.
Interlocking equation diagrams seem FBD fast automation diagrams, except that:
• timer, bistable function are unusable
• there is no output plug

The addition of an interlock SPS is done via the “Objects entry” window at SPC/DPC
datapoint level by clicking on mouse’s right button (1).
topology.
(1)
FIGURE 343: ADDING AN INTERLOCK SPS (E.G. FOR MODULE DPC LEVEL)
Once added, interlock SPS features must be set at SCE level, as SPS datapoint. For details
about SPS datapoint configuration, refer to section 5.1.2 Defining SPS datapoint.
To define interlocking equation for an interlock SPS:
• Add at interlock SPS level, a FBD interlock object (1)
• Configure this FBD interlock (refer to section 6.6.1 Defining a FBD fast automation),
with the existing following restrictions:
− only input plugs are available for its interface definition.

− For its body description via FBD editor, timer and bistable functions do not exist.
(1)
FIGURE 344: DEFINING INTERLOCKING EQUATION FOR AN INTERLOCK SPS

6.6.7 Defining an automatic/manual dependency

Automatic/manual dependency can be set at control level (SPC, DPC or SetPoint):
When a control is linked to a SPS or DPS via the automatic/manual dependency, control is
refused if the SPS (resp. DPS) is in the SET (resp. CLOSED) state.To create an
automatic/manual dependency:
• Add the relation ‘has for AutoManu dependency’ (1) at control level; two relations are
available depending on the input kind setting the dependency (SPS or DPS). Choose
the correct one.
• Fill the relation with the relevant SPS or DPS (2).
(1)
FIGURE 345: DEFINING AN AUTOMATIC/MANUAL DEPENDENCY (E.G.)

• For each "DPC", "SPC" or "Setpoint" datapoint, 2 relations "has for AutoManu
dependency" are available, but they are mutually exclusive.
7. DEFINING COMPUTER LOCAL HMI

All kinds of computers (except C364), can have a GHU200 board for led managing and
possible local bay mimic panel animations in case of complete GHU200 board (refer to
section 4.4.2.2 Setting specific features of a GHU200 board),.
7.1 Defining a bitmap table
To define computer bay mimics, bitmaps are used. Their definition is located at graphic root
of the data modelling.
At computer bay mimic definition level, objects only reference these bitmaps. So it is an
easier way to propagate a bitmap change for instance to all objects that reference it.
At SCE level, bitmap object definition is extended to embed animation: up to 5 elementary
static bitmaps can be grouped in a bitmap object:
• one (mandatory) for default representation
• one for ‘open’ (or reset) representation
• one for ‘closed’ (or set) representation
• one for ‘open withdrawn’ representation
• one for ‘closed withdrawn’ representation

Each representation corresponds to a filename containing the static bitmap definition.
The addition of a bitmap definition is done via the “Objects entry” window at Bitmap table
level of the graphical topology by clicking on mouse’s right button.
FIGURE 346: ADDING A BITMAP

Once added, bitmap attributes must be set at SCE level:
1. short name and long name: used for internal SCE identification.
2. reference index (range [0, 150]: that must be unique for the set of defined bitmaps.
This index will be used in bay mimic definition as described previously.
3. type (Single / 5-uple): single is used for static bitmap definition, 5-uple allows dynamic
bitmap definition as described previously.
4. file name by default: corresponds to the filename containing the bitmap definition
used for default representation.
5. file name for 'open' state : visible only if type is set to 5-uple: corresponds to the
filename containing the bitmap definition used for open state representation.
6. file name for 'closed' state : visible if type is set to 5-uple: corresponds to the
filename containing the bitmap definition used for closed state representation.
7. file name for 'withdrawn open' state: visible if type is set to 5-uple: corresponds to
the filename containing the bitmap definition used for withdrawn open state
representation.
8. file name for 'withdrawn closed' state: (visible if type is set to 5-uple): corresponds
to the filename containing the bitmap definition used for withdrawn closed state
representation.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
FIGURE 347: SETTING BITMAP ATTRIBUTES

Attributes (7) and (8) can be omitted if breakers and switchgears represented in bay mimic
are not concerned with withdrawn information.
To set a file name (attributes (4) to (8)) and define graphically a bitmap:
• select the attribute
• edit graphically a bitmap using the bitmap editor at SCE level
• save the graphical definition of the bitmap by giving a file name in bitmap editor
For details about bitmap editor usage refer to SCE user’s manual.
FIGURE 348: USING BITMAP EDITOR

Color usage in bitmap editor is not significant for computer monochrome LCD.
• The "reference index" attribute value of each "Bitmap" of the "Bitmap table" must be
unique.
• Depending on the "type" attribute value, 1 or 5 PNG file(s) can be linked to a Bitmap.
For each one, the bitmap size must be ≤ 512 bytes.
7.2 Defining a computer workspace

Via a complete GHU200 board (refer to section 4.4.2.2 Setting specific features of a
GHU200 board), each computer with local HMI references a workspace that groups its bay
mimic definitions. Computer workspaces can not be shared by several computers because
mimics are local to bays managed by a specific computer.
Up to 24 bay mimics can be put in a computer workspace, and up to 2 mimics can be linked
to the same bay.
Usual labels are used by computer local HMI (LHMI). They are located for all computers
LHMI in one object grouping all translatable labels, located in “computer workspaces” folder
in Graphic topology.
7.2.1 Settings LHMI labels
To modify a usual label used at computer LHMI level, just select and update the
corresponding attribute at LHMI labels object.
FIGURE 349: SETTINGS LHMI LABELS

7.2.2 Creating a workspace
The addition of a workspace is done via the “Objects entry” window at graphic level by
FIGURE 350: ADDING A COMPUTER WORKSPACE

Once added, computer workspace general features must be set at SCE level:
• Precise which GHU200 board is concerned by created workspace by filling the relation
‘has for workspace’ at concerned GHU board level (refer to section 4.4.2.2 Setting
specific features of a GHU200 board).
• Setting the short and long name (1) attributes of the workspace used for internal SCE
identification,
• Setting ‘local/remote password usage’ (No / Yes) attribute (2), to precise if password is
required to set Local/remote for bays managed by the computer.
(1)
(2)
FIGURE 351: SETTING COMPUTER WORKSPACE ATTRIBUTES

7.3 Defining a computer bay mimic
7.3.1 Creating a computer bay mimic
The addition of a computer bay mimic is done via the “Objects entry” window at computer
workspace level by clicking on mouse’s right button.
FIGURE 352: ADDING A COMPUTER BAY MIMIC

Once added, bay mimic general attributes must be set at SCE level:
1. short name of the bay mimic used for internal SCE identification.
2. bargraph representation ( none / Horizontal / Vertical): this attributes defines which
representation is used for bargraph associated to a MV datapoint assigned to a bay
mimic (refer to section 7.3.4 Assigning MV to bay mimic).
3. module name display (No / Yes) this attribute defines if module short names are
displayed at mimic level when a module is represented on bay mimic (refer to section
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation,
transformer representation).
4. Fill the relation ‘represents’, giving which bay is represented by the mimic (for details
about bay refer to section 6.1.4 Defining a Bay).
5. If necessary, set the attribute ‘mimic rank’ of the ‘represents’ relation to correct value.
This attribute is used when 2 mimics are configured to display an entire bay: as bay is
split in 2 representations, the ‘mimic rank’ attribute gives their display rank at computer
LHMI level (1 or 2).
(1)
(2)
(3)
(4)
(5)
FIGURE 353: SETTING BAY MIMIC FEATURES

When adding a bay mimic at workspace level, its core structure (canvas) is automatically
created and displayed at SCE level, via bay mimic editor and in SCE tree browser. Its core
structure consists of:
1. Reserved zone for bay name display
2. Reserved zone for bay local/remote display ((2’) in tree browser)
3. Reserved zone for ‘interlocking bypass in progress’ information ((3’) in tree browser)
4. Reserved zone for ‘synchrocheck bypass in progress’ information ((4’) in tree browser)
5. Configurable zone for graphical representation of the bay (static and dynamic parts)
6. Reserved zone for message
(1)
(2)
(3)
(4)
(5)
(3’)
(2’)
(4’)
FIGURE 354: CORE STRUCTURE OF BAY MIMIC

For more details about computer LCD usage, refer to document User Interface (coded HI for
Human Interface) of MiCOM C264 documentation binders.
The configurable zone of a bay mimic can be split in two parts:
• A static part with no real-time animation
• A dynamic part with real-time animated representations.

• The computer managing a bay represented by a "Bay mimic" must be the same as the
one linked to the "Comp. workspace" (computer workspace) of this "Bay mimic".
• A bay can be represented by 0, 1 or 2 "Bay mimic". Each "represents" relation has an

attribute "mimic rank for the set of bay mimic". In the case of 2 relations, each attribute
value must be unique.
• For a Computer, the maximum count of managed bays (relation "is managed by")
which are linked to a "Bay mimic" (relation "represents"), is 12.
• Limits of the count of symbols:
Graphic
Comp. workspace
Bay mimic max = 24 / Comp. workspace
LHMI Transformer max = 9 / Bay mimic
LHMI Gen module
LHMI bitmap max = 5 / Bay mimic
LHMI line max = 30 / Comp. workspace max = 18 / Bay mimic
LHMI text max = 5 / Bay mimic (1 is reserved for the Bay name) + 1 reserved
… for the Bay name
S0285ENa
7.3.2 Defining static part: line, bitmap, fixed text

The static part of a computer bay mimic is described via graphical basic shapes:
• LHMI line: horizontal or vertical line with configurable thickness and length
• LHMI bitmap: bitmap that references a bitmap object in the bitmap table (see 7.1
Defining a bitmap) where default representation is only taken into account
• Fixed text: multi-lingual fixed text

Once added, these elements automatically appear in the window of the bay mimic editor at
SCE level.
• The coordinates (x, y) of a symbol must not be located outside the mimic area.
7.3.2.1 Adding a line
The addition of a line in bay mimic is done via the “Objects entry” window at bay mimic level
by clicking on mouse’s right button.
FIGURE 355: ADDING A LINE IN COMPUTER BAY MIMIC

Once added, line attributes must be set at SCE level:

1. short name of the line used for internal SCE identification
2. x ( range [0, 127 pixels], step 1 pixel): abscissa
3. y ( range [0, 127 pixels], step 1 pixel): ordinate
4. length ( range [1 pixel, 127 pixels], step 1 pixel)
5. orientation ( Horizontal / Vertical)
6. thickness ( range [1 pixel, 8 pixels], step 1 pixel)
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 356: SETTING LINE ATTRIBUTES

Abscissa, ordinate, length and thickness of a LHMI line can be directly adjusted with the
mouse in bay mimic editor (for detail, refer to SCE user’s manual)
7.3.2.2 Adding a bitmap
The addition of a bitmap in bay mimic is done via the “Objects entry” window at bay mimic
FIGURE 357: ADDING A BITMAP IN COMPUTER BAY MIMIC

Once added, bitmap attributes must be set at SCE level:

1. short name of the line used for internal SCE identification
4. bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1
Defining a bitmap table)
(1)
(2)
(3)
(4)

Abscissa and ordinate of a bitmap can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE user’s manual)
• The link from an element to its bitmap is defined with the attribute "bitmap reference".
The value of this attribute must refer to an existing bitmap in the "Bitmap table".
7.3.2.3 Adding a fixed text
The addition of a fixed text in bay mimic is done via the “Objects entry” window at bay mimic
FIGURE 359: ADDING A FIXED TEXT IN COMPUTER BAY MIMIC

Once added, fixed text attributes must be set at SCE level:

1. fixed text value: text to display at mimic level
(1)
(2)
(3)

Abscissa and ordinate of a fixed text can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE user’s manual). Text area length at bay mimic is automatically
deduced from text value length (attribute (1)).
7.3.3 Defining dynamic part: pre-defined dynamic text, generic module representation, transformer
representation
To define dynamic part of computer bay mimics, 3 kinds of objects are available:
• Pre-defined dynamic text, used:
− to display local/remote and SBMC status of the bay

− to manage Synchrocheck and interlock bypass during control sequence on the
bay
− to display time and synchronisation status
Generic module representation: used to display module status, linked to a specific SPS or
DPS electrical datapoint. Implicit link to possible xPC associated datapoint is given to
computer for command purpose at local HMI level, via the existence of the relation ‘is
feedback of’ between the xPS and the xPC.
• A generic module is composed of 2 sub-objects:
− a name for display (mandatory)
− a ‘xPS muti-state’ for dynamic module state display (mandatory), referencing a

dynamic bitmap object in the bitmap table, and whose relation to a xPS
datapoint (SPS or DPS) has to be filled up to precise animation datapoint
• Transformer representation: used to display transformer module; linked to a optional

Tap Position Indicator. Transformer is composed of 5 sub-objects:
− a name for display (mandatory)
− a ‘TPI muti-state’ for transformer display (mandatory), referencing a dynamic

bitmap object in the bitmap table, and whose relation to a TPI datapoint can be
filled up to precise the concerned datapoint for the following animation
− an optional ‘current TPI value’ object to display dynamically the current value of
the TPI,
− an optional ‘max TPI value’ object to display upper available value for the TPI
− an optional ‘min TPI value’ object to display lower available value for the TPI
7.3.3.1 Adding time information

The addition of the time information in bay mimic is done via the “Objects entry” window at
bay mimic level by clicking on mouse’s right button.
FIGURE 361: ADDING TIME INFORMATION IN COMPUTER BAY MIMIC

Once added, time information attributes must be set at SCE level:
1. short name of the time information area used for internal SCE identification
(1)
(2)
(3)
FIGURE 362: SETTING TIME INFORMATION ATTRIBUTES

Abscissa and ordinate of time information can be directly adjusted with the mouse in bay
mimic editor (for detail, refer to SCE user’s manual)
7.3.3.2 Positioning Local/Remote status, Synchrocheck bypass or Interlock bypass
When creating a bay mimic, the following objects are implicitly created in the mimic at a pre-
defined location:
1. Interlock bypass ‘button’
2. Local/remote status
3. Synchrocheck bypass ‘button’
Depending on customer’s need, these data can be positioned at a different location:
• directly by using mouse drag and drop in bay mimic editor
• by editing the abscissa and ordinate attributes of the object

(1)
(2)
(3)
FIGURE 363: POSITIONNING PRE-DEFINED TEXT INFORMATION IN BAY MIMIC

7.3.3.3 Adding SBMC information
The addition of the SBMC information in bay mimic is done via the “Objects entry” window at
bay mimic level by clicking on mouse’s right button.
FIGURE 364: ADDING SBMC INFORMATION IN COMPUTER BAY MIMIC

Depending on customer’s need, SBMC information can be positioned at any location in bay
mimic:
• by editing the coordinates of the object

7.3.3.4 Adding a generic module representation
In bay mimic, ‘LHMI Gen module’ is used for module dynamic representation. A ‘LHMI Gen
module’ is a graphical group constituted of:
• the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS
datapoint and to a dynamic bitmap in bitmap table
• the graphical name of the module (Name), always located on the right of the module
representation
The addition of a generic module representation in bay mimic is done via the “Objects entry”
window at bay mimic level by clicking on mouse’s right button.
FIGURE 365: ADDING A GENERIC MODULE IN COMPUTER BAY MIMIC

Once added, the representation features must be set at SCE level:
1. short name of the representation used for internal SCE identification
4. control availability (No / Yes): attribute to precise if control of the module can be
directly done via bay mimic. This attribute is significant if SPS/DPS linked to the
generic module representation (via (5) relation) is feedback of a control SPC or DPC.
If so, control availability concerns this SPC/DPC
5. Relation ‘is managed by’ that must be filled to precise which SPS or DPS is used for
bitmap animation
6. multi-bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1
Defining a bitmap table)
7. module name value: text displayed on LCD (up to 4 characters)
(1)
(2)
(3)
(4)
(5) (7)
(6)
FIGURE 366: SETTING FEATURES OF GENERIC MODULE REPRESENTATION

Coordinates (x and y) of a generic module can be directly managed by using mouse in bay
mimic editor (for detail, refer to SCE user’s manual).
• The link from an element to its bitmap is defined with the attribute : "bitmap reference".
• The "Bitmap" linked to a "LHMI xPS MultiSt" MultiState must be defined as follows:
- its "type" attribute must be set to "5-uple" value
-its 3 first file names { "file name by default", "file name for 'open' state", "file name for
'closed' state" } are mandatory and each one must be unique.
Furthermore, if the MultiState is linked to a SPS or DPS datapoint of a module
containing a "Withdrawn" SPS datapoint, through the "is managed by" relation, then
the following constraints are added to the "Bitmap" definition :
- its 2 file names { "file name for 'withdrawn open' state", "file name for 'withdrawn
closed' state" } are both mandatory and each one must be unique.
7.3.3.5 Adding a transformer representation

In bay mimic, ‘LHMI Transformer’ is used for dynamic transformer representation. A ‘LHMI
transformer’ is a graphical group constituted of:
• the dynamic representation itself (LHMI Gen module), that is linked to SPS or DPS
datapoint and to a dynamic bitmap in bitmap table
• the graphical name of the module (Name), always located on the right of the module
representation
The addition of a transformer representation in bay mimic is done via the “Objects entry”
window at bay mimic level by clicking on mouse’s right button.
FIGURE 367: ADDING A GENERIC MODULE IN COMPUTER BAY MIMIC

Once added, the representation features must be set at SCE level:
1. short name of the representation used for internal SCE identification.
4. control availability (No / Yes): attribute to precise if control of the transformer can be
directly done via bay mimic. This attribute is significant if Raise/Lower DPC control
exists for Tap changer built-in function containing the TPI datapoint used for
transformer animation (via (5) relation). If so, control availability concerns this DPC.
5. Relation ‘is managed by’ that must be filled to precise which TPI is used for
transformer animation.
6. bitmap reference: corresponds to a link in the bitmap table (refer to section 7.1
Defining a bitmap table).
7. module name value: name of the transformer: text displayed on LCD (up to 4
characters).
(1)
(2)
(3)
(4)
(5) (7)
(6)
FIGURE 368: SETTING FEATURES OF TRANSFORMER REPRESENTATION

Abscissa and ordinate of a transformer can be directly adjusted with the mouse in bay mimic
editor (for detail, refer to SCE user’s manual)
When adding a transformer representation, extra values about associated TPI datapoint can
be placed in the bay mimic:
• Current TPI value (dynamic)
• Maximal TPI value
• Minimal TPI value

The addition of such TPI information in bay mimic is done via the “Objects entry” window at
transformer representation level by clicking on mouse’s right button.
FIGURE 369: ADDING A TPI INFORMATIION IN COMPUTER BAY MIMIC

Once added, TPI information can be positioned at a different location:
• by editing the X-coordinate and Y-coordinate attributes of the object

• The link from an element to its bitmap is defined with the attribute : "bitmap reference".
7.3.4 Assigning MV to bay mimic
A MV datapoint is assigned to a specific bay mimic by adding the relation ‘visualizes’ at bay
mimic level and filling it with the MV.
FIGURE 370: ASSIGNING MV DATAPOINT TO BAY MIMIC

Once the relation added and filled, its attributes ‘scale’ must be set at SCE level:
1. scale (120% / 200% / No bargraph), to precise which representation is used for the
MV in the bay mimic
(1)
FIGURE 371: SETTING MV REPRESENTATION IN BAY MIMIC

• A MV datapoint visualized in a "Bay mimic" (relation "visualizes") must belong to the

bay represented by the "Bay mimic" (relation "represents").
• For each visualized MV datapoint, the "transmission on event" attribute must be set
neither to "Cyclic short period" value nor to "Cyclic long period" value to avoid overflow
of the Bay mimic input buffer.
7.4 Displaying datapoint status with Led

SPS and DPS datapoint status can be displayed via leds of GHU200 board by adding the
relation ‘has state displayed on’ at datapoint level (1). Only datapoint managed by computer
can be displayed via the Leds of its GHU200 board.
(1)
FIGURE 372: DISPLAYING DATAPOINT STATUS WITH LED (E.G. FOR BAY SPS DATAPOINT)
Once added at SPS (resp. DPS) level, the relation must be filled with the relevant associated
led and the following relation attributes should be updated:
1. Led status for ‘Set’ state (resp 'Closed'): ( Off / On / Blinking slow / Blinking fast)
2. Led status for ‘Reset’ state (resp 'Open'): ( Off / On / Blinking slow / Blinking fast)
3. Led status for ‘Invalid’ state : ( Off / On / Blinking slow / Blinking fast)
(1)
(2)
(3)
FIGURE 373: SETTING LED STATUS FOR A DATAPOINT (E.G. FOR SPS DATAPOINT)
• If the value of the "HMI type" attribute is "Simple", then "Led#4" must not be used (no
relation link from "Led#4" to a datapoint).
8. ANNEX A: COUPLING SCE DATA MODEL AND ISAGRAF

8.1 ISaGRAF presentation
The SCE will use the 4.11 version of the ISaGRAF software from CJ-International (Altersys
Incorporation).
The 4.11 version is actually a 4.10 upgraded version with specific software developments for
the AREVA company.
8.1.1 ISaGRAF workbench description
• The workbench is used to design and develop distributed process control

applications. These applications are organised in projects.
• A project gathers the whole of all program elements and is composed of

configurations.
• A configuration is a hardware platform which supports kernels that executes

resources. In our version there is only one resource.
• A resource is composed of several units of program (POU). In the current version

there is exactly one resource per configuration.
• The POUs (Program Organisation Unit) can be programs, functions or functional

blocs. They are described using the IEC 1131-3 compliant textual or graphic
languages. They are organised on a hierarchical basis architecture.
• The kernel or virtual machine is the real time software that runs the code of a
resource.
• A target is attached to a configuration. It must be installed on a platform that support a

multi-task operating system such NT or VxWorks.
• The dictionary includes all the variables (input, output or internal), all the function
parameters definitions, all the types (simple or user defined) and all the defined words
(constants definition).
• The languages can be either graphic or textual. They are used to describe the
Program organisation units (POU). They are compliant with the IEC 1131-3 standard.
− SFC : Sequential Function Chart (grafcet)

− FBD : Function Block Diagram (functional diagram)
− LD : Ladder Diagram (Boolean logic based language)
− ST : Structured Text
− IL : Instruction List
There is another graphic language in the workbench: FC (Flow Chart). Nevertheless, it is not
in the standard.
The automatism functions can be designed from any of the graphic or textual languages
proposed by ISaGRAF. According to the problem which the automata must solve, a
language can be better adapted than another.
All languages except the SFC can be instantiated, i.e. they can be used for creation of a
functional block.
Hardware
platform
PROJECT
CONFIGURATION TARGET
RESOURCE KERNEL
Exchange PRJLIBRARY.MDB file *.STF files

diagrams
POU
Dictionary
Graphical
Dictionary Language Editors
C0251ENa
FIGURE 374: ISAGRAF WORKBENCH DESCRIPTION

The workbench contains a exchanges diagram (display of the resources and their possible
links), a view of material architecture (presentation of the configurations with their
resources), the data dictionary and the graphic editors which allow to visualise the POUs
(SFC editor, FC editor and multi-language editor for FBD, LD, ST and IT languages).
8.1.2 Directories structure of ISAGRAF
When the workshop is installed, the following directories tree structure is created :
<root directory>
Bin Executables
Grp Windows Groups
Help
Prj Projects
<project name> single project directory
config1 1 directory 1 config.
resource1 1 directory 1 resource
Simul
Tmp
Tpl projects models
<project name> model name
<configuration>
<resource>
A project is composed of:
• the MS Access database file in the root directory of the project
• the source files of the POU of the resource in the repertory /config1/ressource1
All the data dictionary is saved in the MS Access database file.
The POU files have the STF extension.
When a POU is added into a resource, a STF file is created in the resource folder. It contains
the graphic description (elements coordinates in the editor) as well as the algorithms.
Prj
PROJECT NAME
PRJLIBRARY.MDB
Config1
Ressource1
POU1.STF
POU2.STF
ISAGRAF PROJECT STRUCTURE
The compilation of a project produces several files such *.XTC embedding the TIC code. The
TIC code is the “interpretable code” of the automatism.
8.1.3 Uploaded files towards the target

During upload, the workbench transfers several files to hardware platforms.
The files that are transferred are the following ones:
• Resource (for each resource of that platform):
− A resource configuration file is downloaded.

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

ResourceName_POUName_xtc) will be concatenated into a single file.
− Order for the concatenation is the one given by workbench file
ResourceName_DWLOrder.xtc.
− On hardware platform side, the name of that file will be ISPxxx01.
• Hardware platform:
− The hardware configuration file is downloaded.

− On workbench, file is stored in the project configuration directory, (not in a
resource directory).
− The workbench file name is : ConfigName_NetworkConf.xtc.
− On hardware platform side, the name of that file is ISPffe0d.
Note that this document does not speak about which files are transferred in on-line
modification case (ISPxxx15)
Thus, the files must be modified before download to the target:
• RESOURCE1_Conf.xtc must be renamed as ISP00103
• RESOURCE1_SymbolsTarget.xtc must be renamed as IDS00101
• Config1_NetworkConf.xtc must be renamed as ISPffe0d

All POU TIC files will be concatenated in file ISP00101 in the order described the
DwlOrder.txt file.
8.2 Usage of SCE datapoints in ISaGRAF

The DataPoints (DP) are defined inside the SCE. They will be used by the slow automation
as I/Os. An automation can interact with the system only via these DataPoints.
Any DP used in the code of an automation must be defined beforehand in the SCE.
There are three different kinds of relation between a slow automation and DataPoints:
• The function owns the DataPoint (hierarchical Relation):

see chapter 6.6.2.2 Adding specific datapoints to slow automation
• The function is server of the Data Point (Relation server):

see chapter 6.6.2.4 Creating ISaGRAF server lik (interface definition)
• The function is client of the Data Point (Client relationship):

see chapter 6.6.2.3 Creating ISaGRAF client link (interface definition)
8.2.1 Hierarchical relationship: Function management DPs.
In the electrical tree structure these DP are defined under the function. The function is the
owner of the DP.
For instance these DP can be:
• ON/OFF command of the automatism

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

• value (MV, TPI, Counter): read/write
• quality (all DP except SPC, DPC, SetPoint): read/write
• threshold value (MV, Counter): read
• alarm (global alarm status): read
The hierarchical relationship implies that the DP can be seen as input as well as output of
the function.
8.2.2 Server relationship
The DPs are supplied by the function. They are not attached to the tree structure of the
function. Their parents are components from the electric tree structure or the system tree
structure (bay, module, physical device). The function is charged to update the status/value
and quality attributes of these DPs.
• DP resulting from a logical or analogic mathematical formula which is implemented by

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

• value (MV, Counter, TXT): read/write
• quality (all DP except SPC, DPC, SetPoint): read/write
• threshold value (MV, Counter): read
8.2.3 Client relationship

The function is client of the DP. The DP is not attached to the tree structure of the function.
Its parent is a component from the electric tree structure or the system tree structure (bay,
module, physical device).
The function reads and uses the status/value and quality attributes of the DP.
If the type of the DP is SPC, DPC or SetPoint, the function can also send command
requests. In this case, the equipment that manages the DP acknowledges this request,
executes the command and updates the status and value attributes.
The command requests include parameters and quality modification. This is done in the
same way (acknowledge + attributes updates by the equipment that manages the DP). Thus,
the DP is known as controllable.
• commands sent by an automatism toward a device
• devices or bay state influencing the automatism execution
• threshold modification request
• forcing, deletion, substitution request
• extended counter driving

The function has the following rights on the real time attributes of the DPs wich the function
is client of:
• status (SPS, DPS, MPS) read
• status (SPC, DPC, SetPoint): read/control
• value (MV, Counter, TXT): read
• quality (all DP except SPC, DPC, SetPoint): read/control
• threshold value (MV, Counter): read/control

8.2.4 Access rights summary table
DataPoint type Access types ISaGRAF

variables type
The function owns the DP whatever DP read/write input/output
Threshold, alarm read input
The function serves the DP whatever DP read/write input/output
(the function provides values) Threshold, alarm read control
The function is client of the SPS, DPS, SPS read input
DP
SPC, DPC, SP read and control input/output
(the function read the values)
MV read input
COUNTER read and control input/output
Threshold, alarm read input
8.2.5 Equivalence of SCE datapoint in ISaGRAF

The DataPoints are represented by variables inside the ISaGRAF projects. The type of these
variables is chosen according to the access type to the DataPoint.
The input DPs correspond to read-only variables of a structured type. These structures
contain only the DataPoint attribute useable inside the automatisms (see section 8.2.6
ISaGRAF dictionary data structure ).
Within the calculators ISaGRAF kernel, the output DPs are reached by C functions, using an
ID (see section 8.2.7 Prototype and usage of PACiS function for ISaGRAF). Therefore, the
DPs are projected in the ISaGRAF workshop by an integer which represents the address of
the DP (its ID). This integer is stored in the equivalences table. In an ISaGRAF project, this
table contains some aliases : a name and its value. Theses aliases must be used in the
ISaGRAF programs to identify a variable. The name of an equivalence is made with the
name of the variable, plus the suffix ADR. The value of an equivalence is the address of the
DP. The final values are set during the compilation of PLC project. An equivalence is added
automatically when a datapoint is added from the SCE application. The input/output DPs
(read/write access) are represented as input as well as output the workbench.
All “DP variables” have unique Ids stored in the equivalences table. The name of the variable
is in conformity with to the following rules:
The I/O symbols of the ISaGRAF workshop must correspond to the configuration DPs of the
SCE. They must be unique, easily recognisable to facilitate the programming in the
workshop but they must be short enough not to weigh down the diagrams nor the POUs
texts.
To give a name to the variables inside the ISaGRAF projects, we must consider that:
• The name must be unique
• ISaGRAF is not case sensitive
• The maximum length of name is 128 characters
• The following characters must be, either a letter, either a digit or an underscore
So the identifier of I/O symbols is made by concatenation of a prefix given by the user, a
prefix automatically given by the SCE (in, out, in_out) and an identifier number ( refer to
sections 6.6.2.5 Defining Isagraf IO prefix for an input and 6.6.2.8Defining Isagraf IO prefix
for an output).
In the workshop, the user will have an alias made up of the short names of the bay, module
and DataPoint in the form bay_module_datapoint. The used short name language will be the
one which is declared as “automata language”, i.e. one of the 4 AREVA T&D basic
languages: English, French Spanish or German. Complete identifier SCE will appear in the
data dictionary of the workshop inside the comment field.
The “DP variables” are located in different groups according to their type and relationship to
the function. These groups are not created in order to prevent the user from adding variables
in these groups.
In the SCE application, the address is stored as an attribute of the link between the function
and the DP. This attribute is updated during the fusion of the functions projects towards the
PLC project and the equivalence table is updated with the new values of the variables
addresses.
8.2.6 ISaGRAF dictionary data structure

Each following table corresponds to a structure at ISaGRAF dictionary level.
8.2.6.1 SPS, DPS and MPS
SCE ISaGRAF
Status Status DINT
Quality Quality DINT
GlobalAlarmStatus Alarm SINT
Status attribute for SPS
• RESET / FORCED RESET / SUBSTITUTED RESET = 1

• SET / FORCED SET / SUBSTITUTED SET = 2
Status attribute for DPS
• MOTION 00 = 3
• OPEN / FORCED OPEN / SUBSTITUTED OPEN = 4
• CLOSED / FORCED CLOSED / SUBSTITUTED CLOSED = 5
NOTE: UNDEFINED state is seen as INVALID (see Quality attribute)
Status attribute for MPS
• State1 / FORCED state1 / SUBSTITUTED state1 = 7

• State6 / FORCED state6 / SUBSTITUTED state6 =12
• State7 / FORCED state7 / SUBSTITUTED state7 =13
Quality attribute
• VALID = 0
• INVALID ≠ 0 (TOGGLING, UNKNOWN, SELFCHECK FAULTY, SUPPRESSED,
UNDEFINED)
If Quality attribute is INVALID, Status attribute is non-significant.
Alarm attribute
Unusable
8.2.6.2 SPC, DPC
SCE ISaGRAF
Status Status DINT
Status attribute for SPC
• OFF = 0
• ON = 1
Status attribute for DPC
• OPEN = 0
• CLOSE = 1
Alarm attribute
unusable
8.2.6.3 SetPoint
SCE ISaGRAF
Status Status DINT
Not yet implemented

8.2.6.4 MV, TPI
SCE ISaGRAF
Value Value REAL
HHHThresholdValue Threshold_hhh REAL
HHThresholdValue Threshold_hh REAL
HthresholdValue Threshold_h REAL
LthresholdValue Threshold_l REAL
LLThresholdValue Threshold_ll REAL
LLLThresholdValue Threshold_lll REAL
Quality attribute
• VALID = 0
• SELFCHECK FAULTY = 1
• UNKNOWN = 2
• FORCED = 4
• SUPPRESSED = 8
• SUBSTITUTE = 16
• SATURATED = 64
• UNDEFINED = 128
• OPEN CIRCUIT = 256

• L_THRESHOLDVIOLATION = 512
• LL_THRESHOLDVIOLATION = 1024
• LLL_THRESHOLDVIOLATION = 2048
• H_THRESHOLDVIOLATION = 4096
• HH_THRESHOLDVIOLATION = 8192
• HHH_THRESHOLDVIOLATION = 16384
At a given time, only one value is available. FORCED and SUBSTITUTED states have
higher priority than threshold violation states.
Alarm attribute
Unusable
8.2.6.5 Counter
SCE IsaGRAF
Value Value REAL
FrozenCumulativeValue FrozenCValue REAL
HHHThresholdValue Threshold_hhh REAL
HHThresholdValue Threshold_hh REAL
HthresholdValue Threshold_h REAL
LthresholdValue Threshold_l REAL
LLThresholdValue Threshold_ll REAL
LLLThresholdValue Threshold_lll REAL
Quality attribute
• VALID = 0
• SELFCHECK FAULTY = 1
• UNKNOWN = 2
• OVERRANGE = 64
• UNDEFINED = 128
At a given time, only one value is available.
The attributes FrozenCValue, Threshold_hhh, Threshold_hh, Threshold_h, Threshold_lll,
Threshold_ll, Threshold_l et Alarm are unusable.
8.2.7 Prototype and usage of PACiS function for ISaGRAF

IMPORTANT
• All the following described functions must never be called in ISaGRAF SFC transitions
but only in actions.
• When an action calls the function Wait_Ack_Order, the following transition must at
least test the TRUE value of the function return code (indicating that control has been
well received)
8.2.7.1 Send_Binary_Order
This function concerns the following DP used in ‘is client of’ or ‘manages’ relations:
• SPC, DPC
• Select part for SBO on SetPoint
Name Comment Parameter/return Acces C Type Available values

code (CEI Type)
Return code Output Unsigned FALSE : KO
char TRUE : OK
(BOOL)
Order Order Parameter Input Char (SINT) 0 : OFF / OPEN
1 : ON / CLOSE
4 : SELECT OFF / OPEN

or SELECT Setpoint
5 : SELECT ON / CLOSE
Bypass Forcing Parameter Input Long (DINT) Masks :
1 = Interlock bypass
(unused if
Order=SELECT) 2 = Locking bypass
4 = Mode bypass
8 = Uniqueness bypass
16 = Automation bypass
32 = Synchrocheck
bypass
Several masks can be set
simultaneously
Ref_DP Internal reference of Parameter Input Long (DINT) Use equivalent word
the DP in host linked to the datapoint
equipment (<var>_ADR)
Ref_cmd Identifier of the Parameter Output Long (DINT) Use a locale variable
command
Prototype C:
unsigned char Send_Binary_Order(char Order, long Bypass, long Ref_DP ,long Ref_Cmd )
8.2.7.2 Send_Digital_Order
This function concerns SetPoints used in ‘is client of’ or ‘manages’ relations.
Select for SBO is done via function Send_Binary_Order.
Name Comment Parameter/retur Acces C Type Available values

n code (CEI Type)
char (BOOL) TRUE : OK
Order Value order Parameter Input Float (REAL)
command
Prototype C:
Unsigned char Send_Digital_Order(float Order, long Ref_DP, long Ref_cmd)
8.2.7.3 Send_Threshold_Order
This function concerns the MV and COUNTER used in ‘is client of’ or ‘manages’ relations.
Name Comment Parameter/ Acces C Type Available values

return code (CEI Type)
char (BOOL) TRUE : OK
Threshold_used Mask of thresholds Parameter Input char (SINT) bit 0 :
to update THRESHOLD_HHH
bit 1 :
THRESHOLD_HH
bit 2 : THRESHOLD_H
bit 3 : THRESHOLD_L
bit 4 :
THRESHOLD_LL
bit 5 :
THRESHOLD_LLL
Threshold_HHH Threshold high- Parameter Input Float (REAL)
high-high
Threshold_HH Threshold high-high Parameter Input float (REAL)
Threshold_H Threshold high Parameter Input float (REAL)
Threshold_L Threshold low-low- Parameter Input float (REAL)
low
Threshold_LL Threshold low-low Parameter Input float (REAL)
Threshold_LLL Threshold low Parameter Input float (REAL)
Ref_DP Internal reference Parameter Input long (DINT) Use equivalent word
of the DP in host linked to the datapoint
command
Prototype C:
unsigned char Send_Thresholds_Order(char Threshold_used, float Threshold_HHH, float
Threshold_HH, float Threshold_H, float Threshold_L, float Threshold_LL, float
Threshold_LLL, long Ref_DP, long Ref_cmd)
8.2.7.4 Send_Quality_Order
This function concerns SPS, DPS, MPS, MV, TPI, COUNTER used in ‘is client of’ or
‘manages’ relations for Forcing/Suppression/Substitution functionality.

Return code Output Unsigned char FALSE : KO
(BOOL) TRUE : OK
Quality Asked quality Parameter Input Char (SINT) 1 : FORCING
2 : SUBSTITUTING
3 : UNFORCING
4 : UNSUBSTITUTING
5 : SUPRESSING
6 : UNSUPRESSING
Binary_Value Forcing or Parameter Input Char (SINT) SPS
substitution
1 : RESET
value for SPS,
2 : SET
DPS, MPS
DPS
3 : JAMMED
4 : OPEN
5 : CLOSE
MPS
7 : STATE1
8 : STATE2
9 : STATE3
10 : STATE4
11 : STATE5
12 : STATE6
13 : STATE7
14 : STATE8
15 : STATE9
16 : STATE10
17 : STATE11
18 : STATE12
19 : STATE13
20 : STATE14
21 : STATE15
22 : STATE16
Digital_Value Forcing or Parameter Input Float (REAL)
substitution
value for MV,
TPI, COUNTER
Ref_DP Internal Parameter Input Long (DINT) Use equivalent word
reference of the linked to the datapoint
DP in host (<var>_ADR)
equipment
command
Prototype C:
unsigned char Send_Quality_Order(char Quality, char Binary_Value, float Digital_Value,
long Ref_DP, long Ref_cmd)
8.2.7.5 Send_Ack_Order
This function is used when the automatism manages a DP to answer a awaited command
(Wait_xxx_Order). It allows acknowledgement of received order. It is only used for "User
Function DP".

(BOOL) TRUE : OK
Ref_DP Internal Parameter Input Long (DINT) Use equivalent word linked to the
reference of datapoint (<var>_ADR)
the DP in host
equipment
Order Order of the Parameter Input Char (SINT) 0 : OFF / OPEN
run command 1 : ON / CLOSE
4 : SELECT OFF / OPEN or

SELECT Setpoint
5 : SELECT ON / CLOSE
Value digital order Parameter Input Float (REAL)
value
Ack_code Acknowledge Parameter Input Long (DINT) See hereafter
ment code
Prototype C:
unsigned char Send_Ack_Order(long Ref_DP, char Order, real Value, long Ack_code)
Available acknowledgement codes
0. ACK_OK - positive acknowledgement
1. INCOHERENT_REQUEST - incoherent command
2. MICOM C264 COMPUTER_NOT_READY - command when MiCOM C264 Computer is
initializing
3. BAY_SUBST_MODE_FAULT - error on substation or bay Local/remote mode
4. CONTROL_MODE_FAULT - command when MiCOM C264 Computer is in maintenance
or faulty
5. DEVICE_LOCKED - locked device
6. REQUEST_IN_PROGRESS - command in progress for the device or reception of a
command during delay of forbidden command (inter-control delay)
7. INTERLOCK_NOK - refused by interlock
8. DEVICE_ALREADY_IN_POS - command similar to device current state
9. HW_FAULT - DO board fault
10. POS_INVALID - invalid position of device
11. TIMEOUT_FAILED - time-out between selection and execution or time-out in IED
answer
12. AUTOMATION_RUNNING - device locked by relevant AutoManu information
13. DEVICE_ALREADY_SELECTED - reception of a selection demand as device is still
selected
14. DEVICE_NOT_SELECTABLE - reception of a selection demand as device is Direct

Execute
15. UNIQUENESS_INCOHERENCY - failure in command uniqueness
16. NO_SELECTED - reception of a execution demand as device is not yet selected
17. OPERATOR_CANCEL - cancel operator
18. EXTERNAL_FAULT - time-out on feedback
19. ACK_FAILED_ORDER - acknowledgement UCA2 failed
20. ACK_BAD_TCIP - time-out waiting presence of TCIP SPS
21. ACK_TCIP_TOO_LONG - time-out waiting OFF state of TCIP information
22. ACK_BAD_TAP - bad tap position following a command
23. ACK_MIN_TAP - reception of order "lower" as TPI is on Min value
24. ACK_MAX_TAP - reception of order "raise" as TPI is on Max value
25. DEVICE_FAILED_TO_OPERATE - command towards disconnected IED
26. SYNCHRO_NOK – command refused by synchrocheck
8.2.7.6 Wait_Binary_Order
This function is used when the ISaGRAF module must wait for an execution order relevant to
SPC or DPC. It is only used for "User Function DP".

(BOOL) TRUE : OK
Order Order Parameter Output Char (SINT) 0 : OFF / OPEN
1 : ON / CLOSE
Ref_DP Internal reference of Parameter Input Long (DINT) Use equivalent word linked to
the DP in host the datapoint (<var>_ADR)
equipment
Prototype C:
Unsigned char Wait_Binary_Order(char Order, long Ref_DP)
If the order has a SBO type, the Select will be computed outside ISaGRAF (so Select can
only be soft).
A Wait_Binary_Order must be followed by a Send_Ack_Order.
8.2.7.7 Wait_Digital_Order
This function is used when the ISaGRAF module must wait for an execution order relevant to
SetPoint. It is only used for "User Function DP".

Return Output Unsigned char FALSE : KO
code (BOOL) TRUE : OK
Order Order Parameter Output Float (REAL)
Ref_DP Internal reference Parameter Input Long (DINT) Use equivalent word linked
of the DP in host to the datapoint
Prototype C:
Unsigned char Wait_Digital_Order(float Order, long Ref_DP)
If the order has a SBO type, the Select will be computed outside ISaGRAF (so Select can
only be soft).
A Wait_Digital_Order must be followed by a Send_Ack_Order.
8.2.7.8 Wait_Ack_Order
This function is used when the ISaGRAF module is waiting for an acknowledgement of one
of its commands (Send_xxx_order). It concerns the DP used in ‘in client’ or ‘manages’
relation.

(BOOL) TRUE : OK
Ref_cmd Command Parameter Input Long (DINT) Use the variable associated
reference on which to Ref_cmd used in the
acknowledgement function Send_xxx_order
is awaited
Ack_code Acknowledgement Parameter Sortie Long (DINT) Cf. Send_Ack_Order
code
Prototype C:
Unsigned char Wait_Ack_Order(long Ref_cmd, long Ack_code)
8.2.7.9 Set_xPS
This function is used to give to the host equipment the SPS, DPS, MPS whose all attributes
can be updated by ISaGRAF module. This function uses "User Function DP".

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

Return code Output Unsigned char (BOOL) FALSE : KO
TRUE : OK
DP_value DP to update Parameter Input Struct_MV { Value field:
float Value (REAL); any real value
float compatible with
Threshold_hhh (REAL) ; configuration data
float of the DP
Threshold_hh (REAL) ;
float
Threshold_h (REAL) ; Quality field:
float Threshold_l (REAL) ; 0 : VALIDE
float 1 : INVALIDE
Threshold_ll (REAL) ;
float Threshold_xxx &
Threshold_lll (REAL) ; Alarm fields:
long Quality (DINT); (not significant)
char Alarm (SINT);
}
Ref_DP Internal reference Parameter Input Long (DINT) Use equivalent
of the DP in host word linked to the
equipment datapoint
(<var>_ADR)
Prototype C:
Unsigned char Set_MV(struct_xMV DP_Value, long Ref_DP)
8.2.7.11 Set_Counter
This function is used to give to the host equipment the Counters whose all attributes can be
updated by ISaGRAF module. This function uses "User Function DP".

Return code Output Unsigned char (BOOL) FALSE : KO
TRUE : OK
DP_value DP to update Parameter Input Struct_Counter { Value field:
float Value (REAL); any real value
float compatible with
FrozenCValue (REAL); configuration data
float of the DP
Threshold_hhh (REAL) ;
float Threshold_hh
(REAL); Quality field:
float 0 : VALIDE
Threshold_h (REAL) ; 1 : INVALIDE
float Threshold_l (REAL);
float Threshold_xxx &
Threshold_ll (REAL) ; Alarm fields:
float (not significant)
Threshold_lll (REAL) ;
long Quality (DINT);
char Alarm (SINT);
}
Ref_DP Internal reference Parameter Input Long (DINT) Use equivalent
of the DP in host word linked to the
equipment datapoint
(<var>_ADR)
Prototypage C:
Unsigned char Set_Counter(struct_Counter DP_Value, long Ref_DP)

C264 Enap C30

Uploaded by

Copyright:

Available Formats

You might also like

C264 Enap C30

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

C264 Enap C30

Uploaded by

Copyright:

Available Formats

Application C264/EN AP/C30

MiCOM C264/C264C Page 1/318

1. SCOPE OF THE DOCUMENT 5

3. COMPUTER CONFIGURATION SCOPE 7

4. DEFINING COMPUTER CONFIGURATION IN SYSTEM

Page 2/318 MiCOM C264/C264C

4.8 Defining wave record file management 85

5. DEFINING DATAPOINT 108

MiCOM C264/C264C Page 3/318

5.7 Defining control source for output datapoints 190

6. DEFINING COMPUTER CONFIGURATION IN ELECTRICAL

7. DEFINING COMPUTER LOCAL HMI 282

Page 4/318 MiCOM C264/C264C

7.3 Defining a computer bay mimic 286

8. ANNEX A: COUPLING SCE DATA MODEL AND ISAGRAF 301

MiCOM C264/C264C Page 5/318

1. SCOPE OF THE DOCUMENT

Page 6/318 MiCOM C264/C264C

MiCOM C264/C264C Page 7/318

3. COMPUTER CONFIGURATION SCOPE

− A ‘Graphic’ object for the graphical topology.

FIGURE 1: GENERAL ARCHITECTURE OF A PACIS CONFIGURATION IN SCE

− System topology (Scs): computer is a direct sub-component of the Ethernet network

Page 8/318 MiCOM C264/C264C

3.3 Sparing object

MiCOM C264/C264C Page 9/318

4. DEFINING COMPUTER CONFIGURATION IN SYSTEM ARCHITECTURE

− Alarm management characteristics (alarm processing type, audibility delays, alarm

− Designation of elementary action rights by default used by system datapoints of the

− Designation of the substation where the system devices are located.

Page 10/318 MiCOM C264/C264C

FIGURE 2: GENERAL AND LABELS ATTRIBUTES OF SCS

MiCOM C264/C264C Page 11/318

FIGURE 3: LABELS ATTRIBUTES OF SCS (CONT’D)

Page 12/318 MiCOM C264/C264C

FIGURE 4: ALARM ATTRIBUTES OF SCS

FIGURE 5: COMPUTER ROUTING ATTRIBUTES OF SCS

− Gateway TCP/IP address

− Target TCP/IP address

MiCOM C264/C264C Page 13/318

4.2 Adding a computer in the system architecture

FIGURE 6: ADDING A COMPUTER IN THE SYSTEM ARCHITECTURE

FIGURE 7: DEFAULT COMPONENTS OF THE COMPUTER

Page 14/318 MiCOM C264/C264C

4.3 Setting general attributes of a computer

FIGURE 8: GENERAL ATTRIBUTES OF A COMPUTER

MiCOM C264/C264C Page 15/318

4.3.1 Configuring binary input (BI) filtering

FIGURE 9: DEBOUNCING AND FILTERING

• one for all Digital Inputs which will be used as counters.

FIGURE 10: SETTING BI ACQUISITION ATTRIBUTES

Page 16/318 MiCOM C264/C264C

3. Toggling attributes are defined as the following:

FIGURE 11: MEASUREMENTS VALUES ATTRIBUTES FOR A COMPUTER

MiCOM C264/C264C Page 17/318

4.3.3 Configuring counter acquisition

FIGURE 12: COUNTER ACQUISITION ATTRIBUTES OF A COMPUTER

FIGURE 13: MISCELLANEAOUS ATTRIBUTES OF A COMPUTER