Sce 5.14.10#build1 Checks

CONFIDENTIAL. All rights reserved. SCHNEIDER ELECTRIC.
Passing on and copying of this document, use and communication of its contents are not permitted without prior written
authorization.
DISTRIBUTION
PACiS
CHECKS SPECIFICATION
System Configuration Editor
Control Category
Controlled Not Controlled
Confidentiality Category Error:

Restricted Normal
Reference source not
Error: foundError:
Reference source not Reference source not
foundError: Reference foundError:
source not foundError:
CONFIDENTIAL. All rights reserved. SCHNEIDER ELECTRIC. Passing on and copying of this document, use and communication of its contents are not permitted without prior written

foundError:
foundError: Reference
source not foundError: Reference source not
Reference source not foundError:
foundError: Reference Reference source not
source not found foundError:
found
Identification number Identification letters
Avenue de Figuires, BP 75
2070290 RN
34975 LATTES Cedex (France)
authorization.
Energy Automation
RECORD OF REVISION
ISSUE DATE AUTHOR REF. COMMENTS

1 07/05/2004 Marinella KHALDY First issue
2 24/05/2004 Marinella KHALDY Updates after first Reader/Author cycle.

2.3.27 - Alarm Groups
2.3.22.1 Symbols
2.3.24.6 - Graphic and Launch
Actions
2.4.4.15 - Datapoints of OI Server
Klaxons
2.2.4.9 - Computer Klaxon
2.2.4.10 - Computer Printers
2.3.5.1.1 - FBD consistency
Checks.doc Identification Number: 2070290
CHECKS SPECIFICATION Page: 3/182

Energy Automation
3 14/06/2004 Marinella KHALDY Updates after second Reader/Author

cycle
2.1.2 - Objects in Temporary area
2.2.4.3 - Client - Server relation
2.2.4.6 - Computer Boards
2.2.5.3 - Wave Slow Record
2.2.7.1 - IEDs on Legacy Networks
2.3.2 - Bay and Bay Mimic
2.3.5.1.5 - Settings Micom S1 used by
FBD at computer level
2.3.7 - AutoRecloser function
2.3.20 - OI Window
2.3.24.6 - Graphic and Launch
Actions
2.3.25.3 - Reference from BayMimic
elements to Bitmap
2.4.1.3 -
Forcing/Substition/Suppression
enabling
2.4.3.2.1 - Computer Taking-Control
function
2.3.4.1 - Phases of Circuit Breaker
2.3.24.2 - Var Texts
2.2.4.5.1 - Mapping definition
New checks : Ethernet Protocol
IEC61850
Modification of UCA2 check messages.
2.2.4.5 - UCA2/IEC Mapping
2.4.1.2 - SBO mode Deselection
address
2.4.2 - Acquisition / Control Source
definition
2.3.21 - OI Mimic
New checks : Synchrocheck function

2.3.8 - Synchrocheck function
2.4.1.2 - SBO mode
2.4.4.11 - Relation "has for feedback"
Updated checks : FBD automation

2.4.3.2.1 - Computer FBD
automation
2.4.4.9 - DPC/SPC Datapoints
linked to Output plugs of Fast/FBD
automations
2.4.4.10 - DPC/SPC Datapoints
linked to Input plugs of FBD
automations
Check messages identification with

error/warning codes.

Energy Automation
4 01/09/2004 Christophe THIEBAUT Adding bookmarks in this document.

Adding macro "cuttingInHtmlFiles" in
order to generate a set of HTML files
using the defined bookmarks.
A 18/08/2005 F VERWEE Deletion of FastAutomation checks

Deletion of Old HMI checks
General update following TODO part
intgration in the document
B1 20/08/2005 Luc GRANDGIRARD 36102 / WaveRecording / number of
files * total records is greater than 5000
03/10/2005 C BLOCH 42159 / Synchrocheck / The manager

of the internal synchrocheck have not a
TMU200 Board
38160 / Automation / The developed
equation is to big (do not exceed 256
datapoints)
Remove check 30049 / Redundancy /
The relation is not valid
56161 / CounterDatapoint / The Energy
Counter must integrate an MV
<56162> / CounterDatapoint / An
Energy Counter which integrate an MV
must be Import or Export
<57163> / MVDatapoint / An integrated
MV can't be integrated by two energy
counter with same type (Import or
Export)
17/11/2005 Luc GRANDGIRARD <13020> / LD name is prefixed by

Alias TCP IP and by IED name
(uniquely for legacy IED LD)
05/12/2005 C BLOCH Fix error number 21048 to good
number 22048 in Datapoint Client-
server checks
12/01/2006 C. THIEBAUT
<14166> / RelationHasForFeedback /
A computed MV can't be the feedback
of a SetPoint
12/01/2006 F. VERWEE 17167 / LegacyIED / The MPS

datapoint PSE is missing
25/01/2006 F.VERWEE 33168/BayMimic/The MV datapoint
must be produced by TMU board for
bay visualization
31/01/2006 F.VERWEE 18169/SCADAAddress/The SCADA
address format for PSE/POC must be
bitstring

Energy Automation
17/02/2006 C.BLOCH 58170 / GooseUnicity / Goose ID

(AppID) must be unique for network
28/02/2006 C. THIEBAUT 47122 / Symbol / The linked datapoint
profile isn't FSS enable (relations)->
[acts on]
03/03/2006 C.BLOCH 2.4.4.2 checks 47130 + 47113, make
these checks for launch actions and
acts on relation
07/03/2006
2.5.3.2.2 datapoints which are not
auto-addressed are not said as server
of S2K considering alarm / archiving /
logging or MeanCalculation
2.5.1.4 : add checks 23172 to 23175
for alarm/archived/logged and mean
value computed datapoint without IEC
address
B2 13/03/2006 C. BLOCH 2.2.5.2.1 DNP3 address check :
check unicity of addresses by type
2.2.6.1.1 SCADA address unicity
check : add particular case for DNP3
2.5.4.12 : SCADA addresses of
datapoint check 19177 /
xxxAddressOnSCADANetwork / The
datapoint has two addresses in same
SCADA
27/03/2006 F VERWEE 59003 / CalculatorCyclicSPS / The
count of cyclicSPS components is not
valid (count, maximum)
28/03/2006 F VERWEE Change error by warning for goose
usage relevant to inputs of FBD
automatisms
13/04/2006 C. BLOCH 2.5.3.2.5.3 IEC61850 addressed
Datapoint : new rule for client
datapoints, add IEC/IEC gateways
21/04/2006
2.3.4 Update TapChanger checks
for GotoMinMax and RaiseLower
datapoints coherency
30/05/2006 C. THIEBAUT 02179 / XpsGrouping / The maximum
number of datapoints in a group is
reached (group, count, maximum)
01/06/2006 F. VERWEE 09180 / ComputerBoards / DO channel of
TMU210 can only be used for open control
of a breaker
05/06/2006 C. BLOCH 60181 / UserProfile / User Profile name
is not allowed (name) -> [name]
09/06/2006 C. BLOCH 19182 / xxxAddressOnSCADANetwork /
A datapoint in substation or voltage level
with a SCADA address must have an
IEC address

Energy Automation
12/06/2006 C. BLOCH 23183 / DptProfile / A profile of a

transient SPC with control popup, must
have Order off usage set to No (SPC)
57184 / DptMV / Only one measure
type is allowed by TMU board (fixed by
relation) (TMU board, measure type)
13/06/2006 2.3.3.2.2 add check for slow
automation input/ouput regarding
goose comunication
61185 / DptRaiseLower / A
Raise/Lower DPC SBO Many, must
have Command Panel Assignment set
to No
B3 11/08/06 C. BLOCH FR_3926 2.2.5.3 add check for IsRelayOf :
17186 / LegacyIED / The IED must have
the relation Is Relay Of, because PSE
and/or POC is SBMC dependent
21/08/06 F. VERWEE CRA_319 19189 /

xxxAddressOnSCADANetwork /Bad
value for SQN attribute of CDCII
address (value, min ,max)
26/08/06 C. BLOCH FR_2452 47187 / Symbol / The text symbol of a
Local HMI mustn't be empty (Language)
47188 / Symbol / The local HMI label
mustn't be empty (Label name,
Language)
20/09/06 L. GRANDGIRARD NA 53135 / a datapoint is audible if one of
its states, at least, is alarmed and
audible.
18/10/06 L. GRANDGIRARD FR_4500 31104 / GatewayCommPorts / Baud
rate is not in the range [300..19200] :
for channel used by usual protocol than
T101
19/10/06 C. THIEBAUT FR_4389 47121 / Symbol / The linked datapoints
have incompatible definitions : Add a
new constraint at this check.
47191 / Symbol / The locking
datapoints are missing : New check.
23/10/06 F. VERWEE FR_4235 22192 / DatapointClient / The report
usage for client-server relation is
missing for ATCC at client level (server,
client)
22193 / DatapointClient / The report
usage for client-server relation is
missing for Gateway or grouping at
client level (server, client)
24/10/06 F. VERWEE FR_4307 46194 / alarm viewer / Missing a
defined list for alarm/state viewer

Energy Automation
16/11/06 L. GRANDGIRARD FR_4650 27113 / Multiple links : 2.2.2.3.1, only

1 relation "has for IEC address" is
allowed between a dataobject and a
datapoint.
05/12/06 F VERWEE FR_4608 Maximum of series in real-time trend
viewer set to 8
CC 27/12/06 C. BLOCH Poste d 62196 / Operating mode / Datapoints
ref. for operating mode are exclusives
(Local/Remote Substation DPS and
Operating mode MPS)
27/12/06 F VERWEE FR_4766 36195/ WaveRecording / multiple links
to the same datapoint -> [external id of
the relation]
28/12/06 C. BLOCH Poste d 09197 / ComputerBoards / when
TMU210 is configured, protection
function automatism is mandatory for
SPS synthesis of instantaneous
2.5.4.9 update: SBMC SPC is
mandatory only if SPS not wired
2.1.5: Add specific rules for optional
relations (comm. Port of T104 and
workspace of GHU board)
2.5.1: update check of logging printer
to add C264 cases
08/01/07 C. BLOCH FR_4942 2.4.2.1: Add warning if number of
symbols under a mimic is greater than
1700
08/01/07 C. BLOCH FR_4944 2.2.2.9: Add error check if number of
Send Order foran OI Server is greater
than 1024
24/01/07 L. GRANDGIRARD CRA_758 2.2.6.1.1 : add Buffer overflow
address into unicity check of T101 and
T104 SCADA addresses
16/02/07 C. THIEBAUT FR_4589 2.5.4.19 : add checks for the
CRA_717 datapoints Mapping function.
2.5.4.19 : the existing message for
warnings 22149 and 22150 has been
completed for Mapping.
27/02/07 F. VERWEE FR_4816 36202/ WaveRecording / Slow wave
record is not compatible with a
TMU210 board usage
27/02/07 C. BLOCH FR_5128 09201 / ComputerBoards / Port 3 and 4
of CPU260 must have same baud rate
when used.
02/03/2007 C.THIEBAUT DE_5014 29072 / Printers / The column rank is
not unique ==> Take into account two
new column Command Originator for
OI Printer.
29203 / Printers / The size in character
of the printing line is too long

Energy Automation
06/03/2007 F. VERWEE PTR2007 42204 / Synchrocheck / The TMU220

board is missing for datapoint usage in
reference
09/03/2007 C. BLOCH FR_5240 Review checks for Substation Mode to
include operating mode MPS:
24165 become 62165: for SCADA
link, the substation operating mode
is mandatory, DPS or MPS
62089 (new): when check
substation dependency of a
datapoint look for four dependency
attributes, and llok for DPS or MPS
47121 (update): update checkof
Open control popups to control all
substation dependency attributes
compatibility
14/03/2007 C. BLOCH FR_5325 Add checks for new type of bitmaps:
Memo for OI
64126 / Memo icon / The attribute
value of the referenced bitmap is
not valid
33126 / BayMimic / The attribute
value of the referenced bitmap is
not valid
48127 / Bitmap / The attribute value
of the referenced bitmap is missing
48205 / Bitmap / The bitmap sizes
are not equal (file 1, file 2)
12/04/2007 C. BLOCH FR_5501 Add checks for count of SCADA

networks on a Computer (2.2.6.2)
20206 / SCADA_Networks / The
maximum number of SCADA
protocols for a computer has been
reached (max number, count of
protocols)
number of SCADA protocols
required a computer based on
CPU3 hardware (max number,
count of protocols)
24/04/2007 F. VERWEE FR_4862 Add checks for Electre function ARS

25/04/2007 A.DESBOIS CR_5461 Add checks for coherency protocols
type
27/04/2007 F. VERWEE FR 5415 Update + add new checks for TPI
Add checks for signalisations
intersaison and hiver of Electre
function PSL and PDA

Energy Automation
27/04/2007 F. VERWEE FR_5335 09197 / ComputerBoards / when

TMU210 is configured, protection
function automatism is mandatory for
SPS synthesis of instantaneous/
This check is de-acitvated for Poste_d

application.
09/05/2007 C. BLOCH NA Add description of following check
error:
21045 / DatapointServer / The relation
link is not compatible with the datapoint
server
23/05/2007 C. BLOCH FR_5281 Add check for template coherency
68213 / Templates / One instance of
the template is not coherent with the
template definition (Template, Instance,
missing component)
25/05/2007 C. BLOCH FR_5599 Add check for SPC managing klaxon
69214 / SPCDatapoint / When an SPC
datapoint manages a klaxon, it must be
permanent
25/05/2007 C. BLOCH FR_3193 Fix checks of Synchrochecks:
42089 (2.3.2.2): remove check for
internal manu CS
23065 (2.5.1.2): update SBO mode
for internal manual synchrocheck
42090 (2.3.6): Change check to set
on/off ctrl xPC mandatory for Manual
(40090) and forbidden for Auto (42094)
47121 (2.4.4.6): for the Open ctrl
popup acts on relation, add specific
case of circuit breaker close
23183 (2.5.4.16): do not do this check
for ctrl of internal manual CS
29/05/2007 C. BLOCH FR_5678 Add check for exclusion of datapoints
of same type but Single or Double
(2.3.2 & 2.3.3) #40066 & #70066
14/06/2007 F. VERWEE PTR2007 New checks for EPATR
25/06/2007 C. BLOCH FR_5501 Update checks for count of SCADA
networks on a Computer (2.2.6.2) to
limit up to 4 scada only in case of T104
on CPU3
10/07/2007 G. ESTIMBRE PTR0710 Check for Led behaviour value. The
Led behaviour value must not be used
for alarm when GHU200 board HMI
type is not Complete.
11/07/2007 G. ESTIMBRE PTR0714 A multistate object cant be a child (at
any level) of another MultiState Object

Energy Automation
11/07/2007 G. ESTIMBRE PTR0714 Uses of nMPS in FBD. The nMPS must

be directly only on a Mask entry
03/08/2007 F. VERWEE PTR2007 Implementation of new logging
modelisation (attributes used on profiles
instead of relations)
Update labels for check of logging
printer for 2.5.1
New check relative to the uniqueness
of OI printer numbers:
29228 / Printers / More than one printer
with same number is defined for OI
server (number) -> [<number>]
23/08/2007 G. ESTIMBRE SCE5129 Check to forbid relation is transmit on
IEC 61850 SCADA network under, MV
data point of type checked :
MV type name MV type id
mod Vo (ADC) 307
mod I1 (ADC) 308
mod I2 (ADC) 309
mod V1 (ADC) 310
mod V2 (ADC) 311
thermal status 312
<57221> / DptMV / This MV data point

type can't be transmitted on IEC 61850
SCADA Network (MV data point type)
23/08/2007 F. VERWEE SCE5716 Add new checks for memo:
<72130> / Memo / At least one relation
must be linked-> [is memo of]
<72113> / Memo / Multiple links-> [is
memo of : ]
23/08/2007 F. VERWEE SCE5766 Add new checks for datapoint used in
PSL of a computer
29/08/2007 F.VERWEE SCE5220 Add new check for trigger datapoint:
>36223> / WaveRecording / The

trigger datapoint has not the same
server as its associated wave record
(servers)
29/08/2007 C. THIEBAUT SCE6245 Add new check for the multiple xPC for a
same feedback xPS.
14224 / RelationHasForFeedback /
The xPS is feedback of several xPC

Energy Automation
31/08/2007 C. BLOCH FR_6258 Add check for template coherency

68225 / Templates / One instance of
the template is not coherent with the
template definition , a root component
is missing (Template, Instance's main
component, missing root component)
07/09/2007 G. ESTIMBRE FR_6406 Add check for FBD IO which are not
link with any data point.
39226 / AutomationIOPlug / Fbd
input/output must be link with one data
point
10/09/2007 G. ESTIMBRE FR_6410 Add a check on Boards leds which can
be used bay data point managed by
the same server
35227 / BoardLeds / Board led can be
use only by data point managed by the
led server
03/10/2007 G. ESTIMBRE FR_6567 Add a check on Datapoint which
contains invalid character (,) in Short
name or LongName
73229 / Invalid character find in
datapoint attribute (Attribute, Invalid
character, OI language)
05/10/2007 F. VERWEE DE_6166 Add a check for:
number of Run report <=255
19/11/2007 F. VERWEE FR_6821 Add a check for TMU210:
<57230> / DptMV / The measure type
is not allowed for the 3Vpp+Vb
connection type (measure type,
TMU210 board)
26/11/2007 G. ESTIMBRE DE 5781 Update check of Season configuration
for Electre functions (PDA + PSL)
26/11/2007 C. BLOCH FR 6654 Add check for multistate symbol usage
10/12/2007 G. ESTIMBRE FR6533 Add check on IED MODBUS Address
Bit number must be lower than 16
11/12/2007 C. THIEBAUT PTR2007 Add new check on Datapoint profile
23233 / DatapointProfile / All datapoints
of a SPS Profile must have the same
Detection Mode (Permanent | Transient)
21/01/2008 G. ESTIMBRE FR7210 Add check on Wave Record,
36234 / WaveRecording / Data point
register by wave record must be wired
physically on same computer than wave
record computer -> [Path of the record
relation]

Energy Automation
22/01/2008 C. BLOCH FR 6899 Add check on MV Min/Max value

57235 / MVDatapoint / The max value of
a MV must be strictly greater than the
min value (min value, max value)
57236 / MVDatapoint / The max acq
value of a MV must be strictly greater
than the min acq value (min acq value,
max acq value)
FR 6465 57237 / MVDatapoint / Threshold must
be greater than previous configured
one with at least given difference
(threshold, current value, previous
value, difference)
23/01/2008 C. BLOCH FR 7144 73238 / Datapoint / Device link
datapoint of OI server cant be used in
a mimic
24/01/2008 F. VERWEE FR 6958 Add new checks for tologoly
25/01/2008 G. ESTIMBRE FR 7250 Add a check on maximum number of
LSP possible in data base
configuration (Maximum : 300)
25/01/2008 G.ESTIMBRE FR7213 Add a check on maximum Goose LSP
maximum size.
25/01/2008 G.ESTIMBRE FR6857 Change Limits of symbol under mimic
from 1700 to 1500
28/01/2008 G. ESTIMBRE FR6964 Check on LSP server must equals with
FLS server defined at site level.
28/01/2008 G. ESTIMBRE FR6964 Add check on presence of relation Has
for main FLS server if LSP datapoints
present in configuration
28/01/2008 C. BLOCH FR6092 Add check for Alarm Viewer when
browser count alarms
46245 / AlarmViewer / The alarm list must
be defined for alarm/state viewer
browser which count alarms
29/01/2008 G. ESTIMBRE FR7377 Add a check to verify DREC ready
present under Calculator if a Wave
recording is configured.
01/02/2008 G. ESTIMBRE FR7239 Update check on uniqueness of
MODBUS SCADA address add check
on DPS using double address.
04/02/2008 C. BLOCH FR7396 Update checks for control on state
change
15248 /
RelationControlsOnStateChange / The
xPC is controlled by an xPS more than
one time (mutliple link with same xPS)
(linked xPS)
05/02/2008 C. THIEBAUT CR1045 Complete check on Acquisition/Control
Source definition because now
Setpoints can be wired on AOU200.

Energy Automation
05/02/2008 C. BLOCH FR6452 Add checks for SNTP server addresses

(07249 / 07250 / 07251)
11/02/2008 C. BLOCH CR884 Update baud rate check for SAS
31104 / GatewayCommPorts / SAS
baud rate is not in the range
[100..19200]
Add check for aux comm. port on SAS
11252 / RelationHasForCommPort /
Auxiliary communication port is not
allowed for this protocol (comm. port)
Add check for TC not allowed in SAS
19253 / xxxAddressOnSCADANetwork
/ For SAS protocol, the Command
addresses are not allowed (command
address)
11/02/2008 G. ESTIMBRE DE6454 Add check on TON/TOFF timer which
value is lower than 50ms
14/02/2008 G. ESTIMBRE FR7367 Add a check on SwitchPos and
SwitchPos_SPS under XCBR must not
has relation is transmitted on
IEC61850 SCADA network
21/02/2008 G. ESTIMBRE FR7539 Modify check on Wave Record,
36234 / WaveRecording / Data point
register by wave record must be
manage bysame computer than wave
record computer and not acquire on
IED -> [Path of the record relation]
29/02/2008 F. VERWEE FR7412 Add a check for max inner template level
06/03/2008 G. ESTIMBRE STAB0805 Add a check on OI Server in Hot
Redundancy mode datapoints
Redundancy Status must be present
under OI Server.
Add a check on OI Server in Hot
Redundancy mode, at least two OI
Clients exists and each OI Server is
linked with at least one server.
Add a check on OI Server in twin mode
each OI client must be link with OI
Server main
13/03/2008 F. VERWEE FR7812 Add a check to refuse MPS addressing
for T101/T104 on computer
13/03/2008 C. THIEBAUT CR1101 Add checks for number of settings
Micom S1 by computer (38252 / 38253
/ 38254)
14/03/2008 F. VERWEE FR7685 Add a new check to warn user if digital
measurement has got a cyclic
transmission

Energy Automation
19/03/2008 G. ESTIMBRE FR7579 Add a check on maximum count of

ABB flexgate IED under MODBUS
Legacy
The count of ABB IED components is not
valid (count, maximum)-> [16, 15]
Add a check on Unicty of IED address

for ABB flexgate IED at Legacy Level.
21/03/2008 G. ESTIMBRE FR7376 Add a check on AI scanning cycle
value fro C264
Delta between 'long AI scanning cycle'
and 'short AI scanning cycle' must be
greater or equals to 500 ms-> [300]
01/04/2008 G. ESTIMBRE PTR_OIBAY Add check on OI panel to verify that
alarm group used on OI panel has at
least one DP clients of the OI panel.
Add check on alarm group to verify
used data point is alarmed.
03/04/2008 G. ESTIMBRE PTR_OIBAY Add checks on OI Panel to limits client
DP to 500 and to verify the Standrad
Command Bar of an OI Panel must has
attribute Klaxon Usage to No
16/05/2008 C. BLOCH SCE2.0 Add check for redunded C264-R
10/04/2008 C. BLOCH CR1123 Update Synchrocheck checks
42159 : allow usage of a TMU210 board
42264 : add check for TMU210 for
synchrocheck of type 2
42265 : add check to avoid using of
BusBar V Choice in type 2
Update TMU210 checks
09139 : update label of TMU exclusion
09180 : update check of TMU210 DO
usage
09197 : update check of protection
function
29/05/2008 C. THIEBAUT CR1117 Add exception for the check 03007
12/06/2008 C. BLOCH PTR_OIBAY Add check 78267 for bad OI resolution
Add checks for OI bay graphics
limitations (78268 to 78270)
Add checks for AlarmViewer limitations
(46271 to 46274)
Add check for TrendViewer limitation
(45275)
Add check for text color in case of non
standard texts (47276)
Add checks for presence of login and
exit actions in OI bay (78277)

Energy Automation
16/06/2008 C. THIEBAUT DE 8438 Dont treat checks 08140 and 08141

for C264 used as PCCN Gateway.
09/07/2008 F. VERWEE FR8694 Complete checks for number of
settings Micom S1 by computer (38268
/ 38269)
09/07/2008 C. BLOCH FR8613 Add check for forbidden AOU borad on
redunded computer (09270)
10/07/2008 F. VERWEE FR8692 Add check for forbidden AOU borad on
redunded computer (09270)
11/07/2008 G.ESTIMBRE FR8839 Add a check on SCADA under C264,
only one SCADA of type DNP3
configured on IP.
11/07/2088 G. ESTIMBRE FR6945 Remove check on Craphic action
under multistate (2.4.5.6)
11/07/2008 G. ESTIMBRE FR8005 Remove check on Var Text object
under multistate ( 2.4.5.2)
06/08/2008 F. VERWEE SCE2.0 Add check for Modbus synchro
coherency between IED acq type and
Modbus network
13/08/2008 F. VERWEE FR7960 add check (15044): a controlled xPC
by an xPS can not be mapped on
legacy IED
19/09/2008 G. ESTIMBRE CR1087 Add check on Load function
(shedding/curtailment)
22/09/2008 F. VERWEE CR1087 Add checks for extension rack unicity
and contiguousness
Add check for led usage and led
affectation
25/09/2008 C. BLOCH FR9736 Add checks for FBD inconsistency
(38273 to 38275)
20/10/2008 G. ESTIMBRE CR1207 Add check on SynchroCheck function
of type 2 for mandatory datapoint
22/10/2008 F. VERWEE FR9530 Add check for relay configuration
consistency (55156 to 55158)
23/10/2008 F. VERWEE FR9756 add check (14278): the xPC can not
have a transient feedback
30/10/2008 G. ESTIMBRE CR669 add check on limit of counter per
computer (128 max)
30/10/2008 G. ESTIMBRE PTR08-07 add check for It function, mandatory
computed MV, mandatory TMU 210,
mandatory 67 relay function.
21/11/2008 C.THIEBAUT add check (09282) : the attribute value
is not unique for boards of rack
(attribute SlotNumber).
Complete checks 09015 and 09016 in
order to take into account the TMU210
board.
05/12/2008 F. VERWEE PTR08-13 Add check for IED virtual input (82283)

Energy Automation
06/01/2009 C. THIEBAUT PTR08-20 Modify constant max client by C264

(check 08141).
Modify constant max server by C264
(check 08140).
08/01/2009 C. BLOCH PTR08-13 Add checks for IED indiced reports
(83284 & 83285) for client/report limits
and dataset limits
20/01/2009 F. VERWEE PTR08-20 Add new checks for grouping SPS
(02286 and 02287)
03/02/2009 C. BLOCH FR9879 Review max of check 38160
38288 / Automation / Too much
FBD/Interlock for a computer (count,
max)
04/02/2009 C. BLOCH FR10585 02291 / CapacityLimits / Invalid count
of wired counter datapoint for this
computer or rack (count, maximum)
06/02/2009 G. ESTIMBRE FR10324 Exclude TPI from check 57266 and
add the documentation of this check
which missing.
16/02/09 F. VERWEE FR10686 07292 / TCPIPattribute / The datapoint
External clock status is required on
the computer running a SNTP server
service
17/02/2009 F. VERWEE FR10909 38293 / Automation / There are more
than one boolean setting for the
operator
18/02/2009 F. VERWEE FR6970 14294 /RelationHasForFeedback / The
MV feedback of a SetPoint can not
have a FSS profile
05/03/2009 G. ESTIMBRE PTR09-465 Add check on AVR period for week end
day conformity
09/03/2009 G. ESTIMBRE FR10320 Add check on image, attribute image
file name must be defined
09/03/2009 G. ESTIMBRE FR10869 Add check on C264 with backup forbid
component TMU210
18/03/2009 G. ESTIMBRE PTR09-465 Add check on AVR function
30/03/2009 F. VERWEE PTR09-17 No more check relevant to DNP3 on IP
06/04/2009 C. BLOCH AVR Add checks 09304, 09305 and 09306
for GHU panels
08/04/2009 T. FRANKENMOLEN FR10168 47304 / Add check to avoid Send Order
under a text graphical symbol
21/04/2009 F VERWEE PTR09-153- 85305 / Add check for SCL compliancy
2
12/05/2009 L. GRANDGIRARD PTR09-17 Precision for no more check relevant
to DNP3 on IP
20/05/2009 C. THIEBAUT PTR09-221a 38307 / Automation / Too much
accurate timer of FBD for a computer
(count, max)

Energy Automation
20/05/2009 G. ESTIMBRE PTR09-221a 38308 / Automation /Invalid setting

timer used for timer block (setting path,
allowed timer setting, used timer
setting)
25/05/2009 G. ESTIMBRE PTR09-153- 27309 Add check for Functional
3 naming mode.
28/05/2009 G. ESTIMBRE PTR09-153- Add check on Functional naming Id,
3 check uniqueness for object of same
level 27310
Add check on Functional naming Id,
Concatenation of module and sub
equipment Functional Naming Id must
be lower or equal to 6 character
29/05/2009 C. BLOCH FR11692 15305 / add check for control on state
change on xPC not wired
01/06/2009 T. FRANKENMOLEN FR11382 38312 / add check on timers when
default value is not between the
minimum and maximum value.
04/06/2009 F. VERWEE Suppress check #23233
05/06/2009 C. BLOCH FR 9615 78313 / OI Workspace / The number of
graphical objects by OI Workspace
exceed the acceptable limit
05/06/2009 G. ESTIMBRE FR8642 Add check on SynchroCheck and Sync
FR8641 CB Close Dpt
05/06/2009 G. ESTIMBRE FR10950 Fix check on CB configuration

05/06/2009 G. ESTIMBRE MA-20081203 Add check on device capacity under
Bay Mimic
09/06/2009 T. FRANKENMOLEN FR8939 38314 / Add check on FBD Boolean
settings that are not allowed on
Function Blocks
11/06/2009 C. THIEBAUT PTR09-221a 38315 / Add check on the timer value
of an accurate block timer.
08/07/2009 F. VERWEE FR11058 06325 / Add check for format used at
OI level that should have the same
value for all the database languages
14/08/2009 T. FRANKENMOLEN PTR09-153 83316 / 83317 / 83318 / Add checks for
indiced reports
27/08/2009 F. VERWEE PTR09-271 55329 / Add check on trip contact
usage of 81O and 81U protection
function
14/08/2009 T. FRANKENMOLEN PTR09-153 13330 / Add checks for functional
naming coherency
17/11/2009 G. ESTIMBRE FR13267 Add checks for functional naming
coherency
30/11/2009 F. VERWEE FR8086 do not take into account IEC61850
protocol for TakingControl checks

Energy Automation
02/12/2009 T. FRANKENMOLEN FR12581 37332 / Add check when a RaiseLower

DPC is in Direct Execute and a TAP
Selection is under the transformator
FR9462 20333 / add check for redundant GTW.
02/12/2009 T. FRANKENMOLEN FR10013 47334 / add check for Text under a
group
03/12/2009 T. FRANKENMOLEN FR12270 83290 / add check to document
06/01/2010 C. BLOCH CB- Functional naming: review this part to
20100106-1 SCL naming
08/02/2010 C. THIEBAUT FR13990 25089 / Datapoint_SBMC / The
datapoint is missing-> [SBMC SPS] :
becomes an Error instead of a
Warning.
12/02/2010 C. THIEBAUT FR12958 15335 /DirectExecuteInControlMode /
add check on the relation "controls on
state change".
15336 / SameServerInControlMode /
add check on the relation "controls on
state change".
15/02/2010 F.PLISSON PTR08-20 Modify constant max server by C264 to
50 (check 08140).
25/02/2010 C. THIEBAUT FR14062 Add warning Check (20337) on the
presence or no of the "Redundancy SPS"
under a SCADA protocol.
25/03/2010 C. THIEBAUT PTR09-33 New Checks for RTUsrFct :
38339 / Automation / A RTUsrFct must
belong to a bay managed by a
Gateway device.
38340 / Automation / For all RTUsrFcts
of a same resource number, one and
only one must be Master Resource.
08/04/2010 F.PLISSON FR14142 Modify check 27311 to adapt the label

15/04/2010 G. ESTIMBRE FR10951 Add check to limit number of MV client
or Sever on a computer to 2400
21/04/2010 C. LIEBART FR14775 Add error instead of warning on check
38101
Change check 38252 to 38341
21/04/2010 C. LIEBART FR12227 Add check 38342 : no boolean settings
are allowed on output slots
23/04/2010 C. LIEBART FR14773 Update check 19038 with OPC
protocol
26/04/2010 C. THIEBAUT FR13771 Check 47191 becomes Error instead of
Warning
30/04/2010 C. LIEBART FR10977 Update check 36195 to display multiple
relations

Energy Automation
30/04/2010 C. LIEBART FR15191 Add check 86317 : The gateway server

can not be redunded when managing
bays
07/05/2010 C. LIEBART FR13753 Set dataset size max of goose from
1250 to 1300 (check 54142)
21/05/2010 C. LIEBART FR14303 add check 20335 : no active line on
traffic to be used if unbalanced Mode
(Applicable T101)
18/05/2010 N. MAURICE FR14213 add check for mandatory wiring on dpt
'Select_SPC'
31/05/2010 F.PLISSON FR14755 add check 79279 : The Load Function
needs at least one group
16/05/2010 N.MAURICE FR15623 No check error for missing
"Locale/Remote" or "SBMC" datapoint
on a Bay managed by an IED
Gateway, (no check error 24089 and
25089).
21/05/2010 N.MAURICE FR12008 Add check 84096 - When the AVR RPF
used attribute is true then AVR
Transformer in parallel attribute must
be false
21/05/2010 N.MAURICE FR12008 Add check 84096 - When the AVR RPF
used attribute is true then AVR Double
wound attribute must be false
21/06/2010 N.MAURICE CR1595 Add check 42348 / Synchrocheck /
When the Control Uniqueness attribute
isnt compatible with Synchrocheck
configuration
24/06/2010 F.PLISSON FR13699 38343 / Automation / add check to
upgrade Isagraf projects
15/07/2010 C. LIEBART FR15800 17344 / LegacyIED / The datapoint
'IED DREC ready' must be present if
IED has automatic disturbance
26/07/2010 N. MAURICE PTR09-30A 18345 / Gateway Legacy Networks /
Modbus Legacy / xxxadresse on IED /
The function of the 'xxx address on
IED' is not valid
The OPEN 'xxx address on IED' are not
the corresponding CLOSE 'xxx adress
on IED'
The CLOSE 'xxx address on IED' are
not the corresponding OPEN 'xxx
adress on IED'

Energy Automation
28/07/2010 N. MAURICE FR15771 19182 / xxxAddressOnSCADANetwork

/ A datapoint in substation or voltage
level with a SCADA address must have
an IEC address. This case is treated for
a user profile type not equals to C264-
STANDALONE
29/07/2010 N. MAURICE FR16096 Add checks for count of SCADA and
legacy networks on a Computer
maximum number of SCADA and
legacy protocols for a computer has
been reached (max number, count
of protocols)
02206 / Capacity limits / This error
replace the previous error 20206 /
SCADA_Networks /
09/08/2010 C. THIEBAUT PTR09-33 Add checks for Bays managed by
Gateway
88349 / Bay / A bay managed by a
gateway must be a generic bay
(bay, bay type)
88350 / Bay / The contents of the
bay managed by a gateway isn't
valid (bay, component not
authorized)
10/08/2010 N.MAURICE CR1595 Replace check 42348 / Synchrocheck /
by the following checks :
Check 42352 / Synchrocheck / When
the Datapoint Control Uniqueness
attribute value is not consistent with
synchrocheck configuration
the Bay Control Uniqueness attribute
value is not consistent with
the Substation Control Uniqueness
attribute value is not consistent with
24/08/2010 N. MAURICE FR16040 09346 / CalculatorBoards / One of DIU
or DOU type card must have for board
number attribute value equal to nought
25/08/2010 N. MAURICE FR16172 09356 / CalculatorBoards / Check if the
sum of the number of characters of the
Banner line attribute values is less
than the minimum value authorized
27/08/2010 F.PLISSON FR15842 29347 / Printers / add check about
printer wired on extension rack

Energy Automation
30/08/2010 N. MAURICE FR14380 18348 / xxxAddressOnIed / A Modbus

IED with MICOM Px2x acquisition type
must have a network address between
0 to 247
20/09/2010 N. MAURICE FR14435 Add check 02359 / Capacity limits /
The number of bays managed by a
same computer is oversize
27/09/2010 N. MAURICE FR12015 78360 / C264R / A C264 redundant
can't contain a serial printer
30/09/2010 N. MAURICE FR14063 Add check 19061 /
xxxAddressOnSCADANetwork / The
SCADA address is not valid
05/10/2010 F.PLISSON FR12753 84362 / AVR / Invalid count of AVR
backup
84364 / AVR / Values of the AVR dont
belong to the transformers values
84365 / AVR / All the AVR functions
must have the same min and max
values for the TAP
37363 / TapChanger / Min and max
value of transformer dont belong to the
interval minimum value maximum
value of the TPI
13/10/2010 N. MAURICE FR17227 Add check 89366 / GTW / A MODBUS
Legacy protocol cant be used in an
IEC/IEC GTW
15/11/2010 G. ESTIMBRE CR1671 Add check on MV mapped on INS/INC
Add check on bit field
57351, 57352, 57353, 57354, 57355
17/11/2010 F.PLISSON NA Check 54142, 54143 and 54243 :
change in warning when its a non
PACiS IED
29/12/2010 G. ESTIMBRE FR18053 Add T101Master into list of excluded
object from C264 redunded
30/12/2010 M.AUBERT FR16867 Check 76357: OI Bay has not a
800*600 resolution workspace with
MemoIcon
Check 76358 : A Memo can't be memo
of OI Bay which 800*600 resolution
workspace
03/01/2011 M.AUBERT FR17848 Add check 57360 on MV Bay linked
with TrendViewer not archived
05/01/2011 F.PLISSON FR18144 Add check 38359 if a FBD id is
duplicated
11/01/2011 M.AUBERT FR16557 Add check 23339 : Datapoint profile
link with Open Ctrl Popup cant set
both of OrderUsageOn and
OrderUsageOff to No.

Energy Automation
17/01/2011 M.AUBERT FR11026 Add check 02003 : Number of SetPoint

DataPoint linked to a C264 must be
less or equal than 256
19/01/2011 M.AUBERT FR17778 Add check 36361 : Fast Wave form
must have a count of record less or
equal than 128.
21/01/2011 T. FRANKENMOLEN FR18451 Add check 52368 : more than one
SCADA addresses on a taken control
SPC
31/01/2011 C. LIEBART FR18387 Add check 20369 and 20370 : no SP
FR18762 and MPS addresses are allowed under
a Modbus SCADA protocol
10/03/2011 C. LIEBART CR1699 Add check 89341 : add check on
number of legacy networks on a GTW
23/09/2010 T. FRANKENMOLEN CR1421 Add three checks (32332, 32333,
32334) relative to the coherency of
Goose Rank of ST and MX goosed
DataObjects of C264.
31/03/2011 F.HERBRETEAU PTR10-SUI- Add check on Default alarm processing
A4 type when at least one SUI server is
configured.
08/04/2011 F.HERBRETEAU FR19611 Add check on T101M when the ack
time out is less than the minimum (30)
in balanced mode.
13/05/2011 Y.ROBIN FR17520 Modify checks 23172 and 23175 on
System Datapoints without IEC
address in IO Server
13/05/2011 Y.ROBIN FR19927 Add check 91371 for voltage levels
containing no bay
23/05/2011 F.HERBRETEAU FR19387 Add check 43372 for Window with
mimic and stdtitleBanner
09/06/2011 S. PFENDER DFR16314 Add check on attribute timestamped
'unknown' for SCADA in case of an
IEC61850 ring
14/06/2011 Y.ROBIN FR20026 Add check 18373 for Invalid 'Data
Format' on IED MODBUS address
managed by a gateway
13/07/2011 C. LIEBART PTR2011-06 Change check 89341 from 2 to 16
legacy networks
20/07/2011 S. PFENDER FR19530 Add check 91375 to check that all
nodes are defined on the same voltage
level
01/08/2011 E.DIAS FR20364 Modify check 43372
Add check 43376 on a window with 2
Banners
07/09/2011 E.DIAS PTR2011- Add check 89378 to set the max
06-5 number of IED under a GTW to 200
16/09/2011 E.DIAS PTR2011- Add check 06379 on value Event Table
06-5 Number for a Modbus Ack Type

Energy Automation
19/09/2011 E.DIAS PTR2011- Add check 06380 on IED Type for a

06-5 Modbus Ack Type
13/10/2011 E.DIAS FR18321 Add check 41378 : The AR Bay and
the CB Bay can't be managed by 2
differents computers
17/10/2011 Y.ROBIN FR20895 Modify check 91375
21/10/2011 S.EL-MOUTAOUKIL FR18064 add check for IP Scada Network having
relation with serial port
26/10/2011 S.EL-MOUTAOUKIL FR21306 Remove the check warning that
MODBUS legacy is configured on an
IEC/IEC GTW
28/10/2011 S.EL-MOUTAOUKIL FR21026 Add a check warning the presence of
an IEC/IEC gateway
05/12/2011 S.EL-MOUTAOUKIL FR21191 Add check 24390 of missing
Local/Remote DPS if command Bay
Dependant
16/12/2011 E.DIAS FR19922 Add check 57388 when an operating
MV has a SCADA address
20/12/2011 Y.ROBIN FR19863 Add check 87392 for IED Model files
containing obsolete commonClass
16/01/2012 S.EL-MOUTAOUKIL FR22115 Add check 06391for duplicated
long&short names
20/01/2012 S.EL-MOUTAOUKIL FR17647 Add check 54393 for limit of MV in
goose
23/01/2012 E.DIAS FR21958 Add checks errors
38394,38395,38396,38397 : add
limitations of SR Latch, SPS + DPS,
MEASURES, and MPS by Fbd
30/01/2012 MN.DEEPTHI FR21464 Add check 37388 while thresholds are
configured under TPI
09/02/2012 E.DIAS CR1698 Add check 77383 for redunded
Gateway V4
22/02/2012 F.HERBRETEAU DFR21266 Add three checks (77401, 77402,
77403) relative to the gateway IEC with
goose
27/02/2012 E.DIAS FR22602 Add check 20395 for HNZ Protocol in
PACIS Mode
28/02/2012 S.EL-MOUTAOUKIL PTR2011-05 Add check 93400 for a relation not
used anymore
28/02/2012 S.EL-MOUTAOUKIL PTR2011-05 Add check 18401 for contact field
unused
28/02/2012 S.EL-MOUTAOUKIL PTR2011-05 Add check 18402 for open address
with no closed one
28/02/2012 S.EL-MOUTAOUKIL PTR2011-05 Add check 18403 for closed address
with no open one

Energy Automation
02/03/2012 MN. DEEPTHI FR21598 Add check when a Redundancy SPS

datapoint is added from SCADA
Networks of IEC61850 gateway of
System topoloy
08/03/2012 E.DIAS FR22755 Add check 06374 for Timestamp

unknown for SCADA when a SUI OPC
client is present in the configuration
12/03/2012 Y.ROBIN CR1759 Add checks 92393 92394 92395 92396
for buffered reports
14/03/2012 E.DIAS CR.FR21266 Add check 84404 for attribute
transformer_in_parallel of AVR
Add check 84405 for attribute
parallel_method of AVR
master_follower_role of AVR
Add check 84407 to set a limit number
of follower
master_failure_management of AVR
20/03/2012 S.EL-MOUTAOUKIL FR22040 Add check 23409 for multiple profiles
with the same name
21/03/2012 V.JOSEPH FR22406 18349 / Gateway Legacy Networks /
The usage of "Unused" contact type for
the address of double TS is not
allowed in Gateway
30/03/2012 MN. DEEPTHI FR22723 Add a check error when LHMI
Multistate under a LHMI transformer is
in spare context
13/04/2012 B.RAVI KUMAR FR20371 Add check 39410 for datapoint use by
interlock FBD must have an IEC
address
18/05/2012 MN DEEPTHI FR23282 Add a Check error 02412 when the
number of serial SCADA protocol on
gateway exceeds 4
18/05/2012 B. RAVI KUMAR FR23324 Add a check error 02415 when the
number of serial legacy and serial
scada protocol on gateway exceeds 20
25/05/2012 V.JOSEPH FR20776 Add a check error 18413, SBO is
forbidden for Modbus; all Commands
must be DE (Direct Execute).
13/04/2012 C.LIEBART CR1771 Add checks (24404, 24405, 24406,
24410, 24411) relative to Local/Remote
managed by Gateway and C264

Energy Automation
19/04/2012 Y.ROBIN CR1794 Add check 94375, 94376, 94377and

94378 for FLS integer Setpoints
Update check 57352 for FLS integer
MV
15/06/2012 Y.ROBIN CR1771 Add check 24414 for DPS under bay
managed by GTW using bay mode
dependency
22/06/2012 B. RAVI KUMAR FR23490 Add check error 37400 for removing
hasforfeedback relation from
Raise/Lower DPC
21/06/2012 Y.ROBIN PTR2011- Add check 31415 for COM port already
04-2 used by gateway for redundancy
Add checks 30416 and 30417 for
redundancy link on gtw
29/06/2012 M.AUBERT FR23667 Add check 94401 and 94402 to prevent
ValMax lower than ValMin
02/07/2012 C.LIEBART FR23689 Add check 20418 for datapoints not
mapped on diag system transmitted on
a scada
12/07/2012 V.JOSEPH FR23554 Add check 77419 for upper gateway
configurations HasForServer
relation."modeling/goose usage"
attribute value should be Goose Only
13/07/2012 Y.ROBIN FR23562 Add check 73420 for datapoints
transmitted on IEC 61850 protocol of a
lower gateway in goose only
30/07/2012 L.MATHEW FR 23281 Add check 02377 for the SPS
'Redundancy SPS' must be present for
the redundancy able SCADA protocols
30/07/2012 B.RAVI KUMAR FR 23865 Add check 06420 for Event Table
Number can't be set to {0} for a{1}
SEPAM Type
02/08/2012 C. LIEBART FR 23551 Add check 57400 for TPI as FBD input
(check missing from FR 22589)
28/09/2012 MN.DEEPTHI FR 24039 Add check 18421 when C264 IEDs
have the same bit number, and
function numbers are 6 or 16.
26/09/2012 Y.ROBIN FR 22883 Add Check 95422 for gooses with
Numerical AppID set to 0000
18/10/2012 F.HERBRETEAU FR FH- Add check on IEDs location
20121018
09/11/2012 TC. SREEKRISHNA FR 24085 Add check 49424 when CtrlMutlstate
IsManagedBy relation is mapped to
the datapoint ModeDevice_DPC.
11/07/2012 Y.ROBIN PTR2011- Add checks 32335, 97337, 97336 and
04-2-RedSt 54338 for gooses of gateways
30/11/2012 TC.SREEKRISHNA FR24746 Modify check error message 19039

Energy Automation
30/11/2012 TC.SREEKRISHNA FR24210 Add check 02425 : added a check error

if in a Legacy IED T103 under a C264,
mapped counter addresses number is
greater than 16
30/11/2012 V.JOSEPH FR24305 Add check 52425 : added a check error
when a taking control status is
configured under a gateway which is
managing a local remote substation
21/12/2012 B.RAVI KUMAR FR24993 Add check 18426 : added check error
when the DNP3IED set point address
managed by a gateway is not valid
21/12/2012 TC.SREEKRISHNA FR24924 Add check 73346 : added check error
for the gtw system datapoints or
datapoints from LBUS are not goosed
04/01/2013 V.JOSEPH FR24783 Add Check 38427 : added check error
for the fbd to restrict constant mapping
on fbd input.
29/01/2013 A.KOEPPEL FR20702 Add Check 23428 for C264 state
treatments
30/01/2013 A.KOEPPEL FR25319 add condition suppressing check 09356
if "LHMI_Type" is "Simple"
15/03/13 B.RAVI KUMAR FR24953 add check 06430: added a check error
if short name of the datapoint on SUI
server is empty
17/04/2013 A.KOEPPEL FR25708 Add check error if there are brackets in
a datapoint short name in presence of
SUI.
29/07/2013 F.HERBRETEAU FR25827 Removed check 18346 and 18347
31/07/2013 F.HERBRETEAU FR26514 Added check on hasForMainCommPort
relation for C264 legacy protocols.
11/09/2013 A.KOEPPEL CR_LoadSh Add Check 98429 for LoadSharing
aring relations which should be lower or
equal to 33.
11/09/2013 A.KOEPPEL CR_LoadSh Add Check 02430 for C26x nodes
aring whose sum should be lower or equal to
1000.
12/09/2013 F.HERBRETEAU FR26030 Changed check 02003 on SetPoints to
Warning
13/09/2013 F.HERBRETEAU FR26043 Added check for Isagraf resources for
FR26365 gateway
25/09/2013 F.HERBRETEAU FR26344 Modified check 18349 to add double
TC
07/10/2013 F.HERBRETEAU CR2031 Added check for Gateway SNTP server
25/07/2013 F.HERBRETEAU FR25992 Add check error for relation
HasPrimaryOn or HasSecondaryOn on
TXF
27/02/2014 F.HERBRETEAU CR2055 Aded 2 checks on MV display (84452
and 84453)

Energy Automation
27/02/2014 F.HERBRETEAU FR27750 Modified check gravity from warning to

error on symbols out of mimics for
LHMI
APPROVAL
Name Function
A.COULON PACiS Project Manager
F. VERWEE SCE Project Manager

Energy Automation
TABLE OF CONTENTS
1 Introduction.......................................................................................................................33
1.1 Purpose.................................................................................................................................33
1.2 References.............................................................................................................................33
1.3 Graphic symbols used in this document.............................................................................33
2 Checks...............................................................................................................................33
2.1 General checks.....................................................................................................................34
2.1.1 Internal error....................................................................................................................................34
2.1.2 Objects in Temporary area..............................................................................................................34
2.1.3 Capacity limits................................................................................................................................34
2.1.4 Variant attributes value....................................................................................................................35
2.1.5 Relations..........................................................................................................................................36
2.1.6 Templates........................................................................................................................................37
2.1.7 IED Model file containing obsolete CommonClass........................................................................37
2.2 System checks.......................................................................................................................38
2.2.1 TCP/IP definition on Ethernet Network..........................................................................................38
2.2.1.1 Device IP addressing...................................................................................................................38
2.2.1.2 SNTP servers...............................................................................................................................38
2.2.2 IEDs location...................................................................................................................................39
2.2.3 Alarm...............................................................................................................................................39
2.2.3.1 Default alarm processing type.....................................................................................................39
2.2.4 UCA2/IEC Physical Devices..........................................................................................................39
2.2.4.1 Redundancy.................................................................................................................................39
2.2.4.1.1 PACiS redundancy................................................................................................................39
2.2.4.1.2 C264-R redundancy..............................................................................................................40
2.2.4.1.3 GATEWAY redundancy.......................................................................................................40
2.2.4.1.4 Incompatible component for redounded computer..............................................................41
2.2.4.2 Goose transmition.......................................................................................................................41
2.2.4.3 Client - Server relation on UCA2/IEC........................................................................................41
2.2.4.4 Management of bays...................................................................................................................42
2.2.4.5 UCA2/IEC Mapping on Ethernet Network.................................................................................42
2.2.4.5.1 Mapping definition...............................................................................................................42
2.2.4.5.2 UCA2 Goose Rank of Data Object......................................................................................45
2.2.4.5.3 IEC Goose............................................................................................................................46
2.2.4.5.4 Addressing of OI printer System Datapoints.......................................................................48
2.2.4.5.5 Addressing of OI client System Datapoints.........................................................................48
2.2.4.5.6 Addressing of Computer boards Status Datapoints..............................................................49
2.2.4.5.7 SCL naming..........................................................................................................................50
2.2.4.6 Computer Boards........................................................................................................................52
2.2.4.7 Computer extension racks...........................................................................................................55
2.2.4.8 Computer Settings.......................................................................................................................56
2.2.4.9 Computer Klaxon........................................................................................................................56
2.2.4.10 Computer Printers...................................................................................................................57
OI Server.....................................................................................................................................................58
2.2.4.11 OI server Printers....................................................................................................................60
2.2.4.12 OI server Symbols...................................................................................................................61
2.2.4.13 UCA2/IEC Gen IED data model reference.............................................................................62
2.2.4.14 Cyclic SPS...............................................................................................................................62
2.2.4.15 Computer AM Acquisition......................................................................................................62
2.2.4.16 Timestamped unknown for SCADA...................................................................................62
2.2.5 Wave Records of computers............................................................................................................63
2.2.5.1 Common check for fast and slow records...................................................................................63

Energy Automation
2.2.5.2 Wave Fast Record.......................................................................................................................63

2.2.5.3 Wave Slow Record......................................................................................................................64
2.2.5.4 Triggers of Wave Record............................................................................................................65
2.2.6 Channels..........................................................................................................................................65
2.2.7 Legacy Networks............................................................................................................................67
2.2.7.1 IEDs on Legacy Networks..........................................................................................................67
2.2.7.2 IED Mapping...............................................................................................................................69
2.2.7.2.1 Case of DNP3 IED...............................................................................................................69
2.2.7.2.2 Case of MODBUS IED........................................................................................................70
2.2.7.2.3 Case of ABB Flexgate MODBUS IED................................................................................71
2.2.7.2.4 Case of T103 IED.................................................................................................................72
2.2.7.2.5 Case of T101 IED.................................................................................................................73
2.2.7.2.6 Case of MICOM Px2x IED..................................................................................................74
2.2.7.3 IED on Legacy T103 Network....................................................................................................74
2.2.7.1 IED on Legacy MODBUS Network...........................................................................................74
2.2.8 SCADA Networks...........................................................................................................................77
2.2.8.1 SCADA Mapping........................................................................................................................77
2.2.8.1.1 Address value, in SCADA Mapping of Computers and Gateways......................................77
2.2.8.1.2 Address structure, in SCADA Mapping of Computers and Gateways................................80
2.2.8.1.3 MV Address format on DNP3 protocol, of Computers and Gateways................................80
2.2.8.1.4 SOE file attributes, in SCADA Mapping of Computers......................................................81
2.2.8.1.5 T104 protocol attributes, of Computers and Gateways........................................................81
2.2.8.1.6 Feedback addresses on GI74 protocol, of Gateways............................................................82
2.2.8.1.7 Addressing of MPS on T101/T104 of Computers................................................................82
2.2.8.2 Number of SCADA networks.....................................................................................................83
2.2.8.3 Protocol type coherency with hardware prot type.......................................................................84
2.2.8.4 Redundancy type of T101...........................................................................................................84
2.2.8.5 Communication port of a SCADA Network...............................................................................84
2.2.8.6 Presence of the Redundancy SPS under a SCADA Network.....................................................85
2.2.8.7 Modbus protocol.........................................................................................................................85
2.2.8.8 Datapoint transmission................................................................................................................85
2.2.9 Taking Control function..................................................................................................................85
2.2.10 Non PACiS IED on IEC61850........................................................................................................87
2.2.10.1 Virtual input of IEC61850 IED...............................................................................................87
2.2.10.2 Report by client limit..............................................................................................................88
2.2.10.3 Dataset creation limit..............................................................................................................88
2.2.10.4 Main and backup client dont share the same report preference.............................................88
2.2.10.5 No report available according to Equipment preference.........................................................88
2.2.10.6 SCL compliancy......................................................................................................................88
2.2.10.7 Obsolete CommonClass..........................................................................................................88
2.2.11 IEC61850 Control Block Management...........................................................................................89
2.2.11.1 Report by client limit..............................................................................................................89
2.2.11.2 Dataset creation limit..............................................................................................................89
2.2.11.3 Dataset capacity......................................................................................................................89
2.3 Electrical checks...................................................................................................................90
2.3.1 Voltage Level and bay.....................................................................................................................90
2.3.2 Bay and Bay Mimic........................................................................................................................90
2.3.2.1 Bay..............................................................................................................................................90
2.3.2.2 Bay Mimic...................................................................................................................................91
2.3.3 Switchgear.......................................................................................................................................92
2.3.4 Circuit Breaker................................................................................................................................92
2.3.4.1 Phases of Circuit Breaker............................................................................................................92
2.3.4.2 Synchrocheck of Circuit Breaker................................................................................................93
2.3.5 Automation......................................................................................................................................94
2.3.5.1 FBD automation..........................................................................................................................94
2.3.5.1.1 FBD consistency..................................................................................................................94
2.3.5.1.2 FBD status............................................................................................................................95

Energy Automation
2.3.5.1.3 Input/Output plugs................................................................................................................96

2.3.5.1.4 Datapoint used by FBD at computer level...........................................................................98
2.3.5.1.5 Settings Micom S1 used by FBD at computer level............................................................98
2.3.5.2 Slow automation..........................................................................................................................99
2.3.5.2.1 Modified flag........................................................................................................................99
2.3.5.2.2 Input/Output.........................................................................................................................99
2.3.5.2.3 Settings Micom S1 used by UserFunctions (Slow Automation) at computer level...........100
2.3.5.2.4 Dictionnary coherency.......................................................................................................100
2.3.5.2.5 Isagraf files existence.........................................................................................................100
2.3.5.2.6 Isagraf version....................................................................................................................100
2.3.5.2.7 Real Time UserFunctions...................................................................................................101
2.3.6 Tap Changer..................................................................................................................................101
2.3.6.1 Position indicator......................................................................................................................101
2.3.6.2 RaiseLower / GotoMinMax coherence.....................................................................................102
2.3.6.3 RaiseLower / TAP Selection coherence....................................................................................102
2.3.7 AutoRecloser function..................................................................................................................102
2.3.8 Synchrocheck function..................................................................................................................105
2.3.9 ATCC function..............................................................................................................................107
2.3.10 Protection module.........................................................................................................................108
2.3.10.1 EPATR function.....................................................................................................................108
2.3.11 Electre function ARS.....................................................................................................................109
2.3.12 Electre function PSL.....................................................................................................................109
2.3.13 Electre function PDA....................................................................................................................110
2.3.14 Topology........................................................................................................................................110
2.3.15 Fast load shedding.........................................................................................................................111
2.3.16 Load shedding/ Load Curtailement...............................................................................................111
2.3.17 It function.....................................................................................................................................111
2.3.18 AVR Function................................................................................................................................112
2.3.19 OI Workspace................................................................................................................................115
2.3.19.1 Display resolution.................................................................................................................115
2.3.19.2 Limitations............................................................................................................................115
2.3.19.3 OI Bay limitations.................................................................................................................115
2.3.20 OI Window....................................................................................................................................116
2.3.21 OI Mimic.......................................................................................................................................116
2.3.21.1 Symbols.................................................................................................................................116
2.3.22 Bay Mimic symbols......................................................................................................................117
2.3.22.1 Symbols.................................................................................................................................117
2.3.22.2 Visualized MV datapoints.....................................................................................................119
2.3.23 Standard Command Banner..........................................................................................................119
2.3.23.1 OI Bay...................................................................................................................................119
2.3.24 OI symbols....................................................................................................................................119
2.3.24.1 Multi-States...........................................................................................................................119
2.3.24.2 Var Texts................................................................................................................................120
2.3.24.3 Trend viewer.........................................................................................................................121
2.3.24.4 Alarm/State viewer................................................................................................................121
2.3.24.5 ActiveX columns...................................................................................................................122
2.3.24.6 Graphic and Launch Actions.................................................................................................123
2.3.24.7 Text........................................................................................................................................125
2.3.24.8 Image.....................................................................................................................................126
2.3.25 Bitmaps.........................................................................................................................................126
2.3.25.1 Bitmap index.........................................................................................................................126
2.3.25.2 Bitmap size............................................................................................................................126
2.3.25.3 Reference from BayMimic elements to Bitmap....................................................................126
2.3.25.4 Memo bitmaps.......................................................................................................................128
2.3.25.5 Particular format for VarText symbol and VarText...............................................................129
2.3.26 Memo............................................................................................................................................129
2.3.27 Alarm Groups................................................................................................................................129
2.3.28 User Profile...................................................................................................................................130

Energy Automation
2.3.29 Buffered reports............................................................................................................................130

2.4 Datapoints checks...............................................................................................................130
2.4.1 Datapoint Profiles..........................................................................................................................131
2.4.1.1 Events logging...........................................................................................................................131
2.4.1.2 SBO mode.................................................................................................................................131
2.4.1.3 Forcing/Substition/Suppression enabling..................................................................................135
2.4.1.4 Alarming/Archiving/Logging/MeanValue Computation for non addressed datapoints...........135
2.4.1.4.1 Alarmed Datapoints :.........................................................................................................135
2.4.1.4.2 Logged Datapoints :...........................................................................................................135
2.4.1.4.3 Mean value computation Datapoint :.................................................................................136
2.4.1.4.4 Archived Datapoint :..........................................................................................................136
2.4.1.5 C264 state treatments values....................................................................................................136
2.4.2 Acquisition / Control Source definition........................................................................................137
2.4.3 Client / Server definition...............................................................................................................143
2.4.3.1 General definitions....................................................................................................................143
2.4.3.2 Detailed definitions...................................................................................................................144
2.4.3.2.1 Computer............................................................................................................................144
2.4.3.2.2 OI server.............................................................................................................................153
2.4.3.2.3 OI client..............................................................................................................................155
2.4.3.2.4 OI Bay................................................................................................................................155
2.4.3.2.5 UCA2/IEC generic IED.....................................................................................................155
2.4.3.2.6 UCA2/IEC Gateway...........................................................................................................156
2.4.3.2.7 OI Bay................................................................................................................................156
2.4.4 Datapoints constraints...................................................................................................................157
2.4.4.1 MV Datapoints sent on 'set' or 'close' state...............................................................................157
2.4.4.2 MV Datapoints digital acquisition............................................................................................158
2.4.4.3 MV Datapoints value features and scaling checks....................................................................158
2.4.4.4 Integer MV for FLS..................................................................................................................159
2.4.4.5 SetPoint datapoint mapped on INC_DIR..................................................................................160
2.4.4.5.1 Integer SetPoint for FLS....................................................................................................160
2.4.4.6 Restrictions Value......................................................................................................................160
2.4.4.7 DPC and DPS Datapoints linked to IED addresses..................................................................161
2.4.4.8 DPC and DPS Datapoints linked to IED addresses..................................................................161
2.4.4.9 DPC/SPC Datapoints linked to Output plugs of Fast/FBD automations..................................161
2.4.4.10 DPC/SPC Datapoints linked to Input plugs of FBD automations.........................................162
2.4.4.11 Relation "has for feedback"..................................................................................................163
2.4.4.12 Relation "has for AutoManu dependency"............................................................................165
2.4.4.13 Local/Remote Datapoints......................................................................................................165
2.4.4.14 SBMC Datapoints.................................................................................................................168
2.4.4.15 Datapoints of OI Server Klaxons..........................................................................................169
2.4.4.16 SPC managing a Klaxon.......................................................................................................170
2.4.4.17 SPC and DPC Datapoints......................................................................................................170
2.4.4.18 Counter Datapoints................................................................................................................170
2.4.4.19 Energy Counter Datapoints...................................................................................................170
2.4.4.20 Datapoints linked to SCADA addresses................................................................................171
2.4.4.21 Xps grouping.........................................................................................................................171
2.4.4.22 Datapoint profile Order Usage..............................................................................................171
2.4.4.23 TM computed by TMU board...............................................................................................172
2.4.4.24 Command Panel Assignment................................................................................................172
2.4.4.25 Datapoint Mapping function.................................................................................................172
2.4.4.26 Data point Short Name and Long Name constraints.............................................................173
2.4.4.27 Device link datapoint constraint............................................................................................174
2.4.4.28 Switchgear pos. (SPS/DPS) datapoints constraint................................................................174
2.4.4.29 Datapoints transmitted on gateway IEC/IEC........................................................................175

Energy Automation
1 Introduction
1.1 Purpose
This document describes the specification and the user interface of the PACiS v4 SCE Check
function.
Only the list of checks is drawn up here. The user interface of the checks table is described in the
document : PACiS System Configuration Editor DSL.
The check function deals only with errors and warnings which are not prevented by the Structural
Database rules or by the locks/filters processed by the SCE user interface packages.
1.2 References
[1] SCE Data model embedded into PACiS SCE issue 4.38.
[2] PACiS System Configuration Editor DSL Issue K2 Id: 2070290.
[3] PS01 : PACiS Product Specifications Systems Overview Issue F Id: 2059660
1.3 Graphic symbols used in this document
Check messages are written here with the following indications :

the Error ( ) or Warning ( ) flag
the error or warning code
the check identification
the check message
The User Interface of the check table is described in the User Manual of the SCE.
Relation and Attribute representation in figures :
A relation is marked with a .

In the example below, te "Feeer" is linked to the C264 computer by te "is managedby" relation.
(R) is managed by
Feeder C264
An attribute is marked with a (A).

In the example below, te "spre" attribute of te "Feeer" is set to te No" value.
Feeder (A) spare No
The configuration of Relations and Attributes is described in the User Manual of the SCE.
2 Checks
Checks are performed according to the following steps :
General checks

Energy Automation
System checks
Electrical checks
Graphical checks
Datapoints checks
Spare objects are not processed.

Objects in Temporary area are not processed.
2.1 General checks
2.1.1 Internal error
In case of an exceptional error, internal to the check process, the stack trace is displayed with the
following message :
00001 / CheckAbort / Check internal error
2.1.2 Objects in Temporary area
The temporary area must not contain any object which is not spare.
01002 / TemporaryObjects / There are objects in temporary area
2.1.3 Capacity limits
The two following lists are taken from the document PS01.
Component Maximum authorised

OI client on a per OI server basis (1) 8
OI server 1+ 1 redundant
Printers OI level 4 (* 2 if redundant)
Printers computer level (1) C264: 1 / C264C: 1 / C364: 0
IED on a per Legacy Bus basis (1) 16
UCA2/IEC equipments (Computers and Generic IEDs) 96
SCADA Networks in the system 16
IED under a Gateway 200
For a whole PACiS system

Logical Plant Item Maximum authorised
Substation (1) 40
Voltage Level 4 if ATCC used (VL must be under
same Substation with ATCC
existence attribute to yes)
Bays 512
Circuit breakers (XCBR) 512
Disconnectors (SWIT) 2048
Transformers (TXF) (2) 512
Generic modules 4096
Datapoints 48000
Digital Input Points (SPS, DPS, MPS) 37500
Measurements (MV) 7500

Energy Automation
Measurements per computer ( Client and Served MV) 2400

Counter 512
TPI 512
Output Control Points (SPC, DPC) 5000
Setpoint Outputs (digital or analogue) 512
Run report 255
LSP data points 300
(1) Locked by the Structural Database.

(2) The Structural Database locks the count of Transformers per Bay-Transformer to 1. So the
maximum count of Transformers follows the count of Bay-Transformers.
Additional checks :
The check of the count of Symbols per "Comp. workspace" and per "Bay mimic" is described in
chapter 2.3.22.1 Symbols.
02003 / CapacityLimits / The count of components is not valid (count, maximum)
Examples :
02003 / CapacityLimits / The count of OI server components is not valid (count, maximum)-> [3, 1]
Number of SetPoint DataPoint linked to a C264 must be less or equal than 256
02003 / CapacityLimits / Scs / Ethernet network /The count of SetPoint datapoint components is
not valid (count, maximum)
02377 / CapacityLimits / Maximum count of SCADA Protocol (both IP and Serial) for gateway has
been reached
CR1911 : gateway capacity limits
02432 / CapacityLimits / Maximum datapoints of given type reached for legacy IED
02433 / CapacityLimits / Maximum datapoints of given type reached for SCADA network
02434 / CapacityLimits / Maximum datapoints of given type received by gateway from sbus server
02435 / CapacityLimits / Maximum datapoints of given type managed by gateway reached
1- Limits SCE in place of Gateway SBUS IEC61850 Mapping: SpecificationDescription

1.1 - xPS shall be smaller than (<=) 5100 per SBUS IEC61850 Server connected to
the Gateway;
1.2 - MV(TPI included) + Counter shall be smaller than (<=) 2500 per SBUS
IEC61850 Server connected to the Gateway;
1.3 - xPC + SetPoint shall be smaller than (<=) 5000 per SBUS IEC61850 Server
connected to the Gateway;
CAUTION we remind that independently of the Gateway limits (255 Servers) there
is a system limits at 96 Servers IC61850 for a given SCE SBUS.
Limits Gateway LBUS MODBUS (master TCP anSpecificationDescriptiond Serial)

2 - Limits Gateway LBUS MODBUS (master TCP anSpecificationDescriptiond Serial):
2.1 - xPS shall be smaller than (<=) 65535 per IED Slave connected to the
Gateway;

Energy Automation
2.2 - MV(TPI excluded) and Counter shall be smaller than (<=) 2500 per IED Slave
2.3 - xPC shall be smaller than (<=) 800 per IED Slave connected to the Gateway;
2.4 - TPI (SPI) shall be smaller than (<=) 256 per IED Slave connected to the
Gateway;
2.5 - SetPoint shall be smaller than (<=) 256 per IED Slave connected to the
Gateway;
Limits Gateway LBUS T101 (master)

3 - Limits Gateway LBUS T101 (master): SpecificationDescription
Gateway;
3.2 - MV(TPI excluded) shall be smaller than (<=) 512 per IED Slave connected to
the Gateway;
3.3 - xPC shall be smaller than (<=) 256 per IED Slave connected to the Gateway
3.4 - TPI (SPI) shall be smaller than (<=) 512 per IED Slave connected to the
Gateway;
Gateway;
3.6 - Counter shall be smaller than (<=) 64 per IED Slave connected to the
Gateway;
Limits Gateway LBUS DNP3 (Over IP et Serial)

4 - Limits Gateway LBUS DNP3 (Over IP et Serial): SpecificationDescription
Gateway;
4.2 - MV(TPI included) shall be smaller than (<=) 65535 per IED Slave connected
to the Gateway;
4.2.1 - AI(TPI included) shall be smaller than (<=) 32767 per IED Slave
4.2.2 - CT shall be smaller than (<=) 32767 per IED Slave connected to the
Gateway;
4.3 - xPC shall be smaller than (<=) 256 per IED Slave connected to the Gateway;
Gateway;
Limits Gateway SCADA T101/T104

5 - Limits Gateway SCADA T101/T104: SpecificationDescription
5.0 Number of xPS Substation local/remote per scada protocol shall be smaller
than (<=) 100
5.1 - xPS shall be smaller than :
5.1.1 SPS (or MPS splitted: 16 SPS by MPS max) shall be smaller than (<=)
65535;
5.1.2 DPS shall be smaller than (<=) 65535;
5.1.3 MPS shall be smaller than (<=) 65535;
5.2 - MV shall be smaller than:
5.2.1 MV floatting (32bit + IEEE) shall be smaller than: (<=) 65535;
5.2.2 MV normalized (16 bit between [-1;1] by step of 2-15.) shall be smaller
than: (<=) 65535;
5.2.3 MV scaled (16 bit between [215.+215-1] by step of 1) shall be smaller
than: (<=) 65535;
5.3 - xPC shall be smaller than :
5.3.1 SPC shall be smaller than (<=) 65535;

Energy Automation
5.3.2 DPC shall be smaller than (<=) 65535;
5.4 - TPI (SPI) shall be smaller than (<=) 65535;

5.5 - SetPoint shall be smaller than (<=) 65535;
5.6 - Counter shall be smaller than (<=) 65535;
Limits Gateway SCADA SAS

6 - Limits Gateway SCADA SAS: SpecificationDescription
than (<=) 100
6.1 - xPS shall be smaller than :
6.1.1 SPS (or MPS splitted: 16 SPS by MPS max) shall be smaller than (<=)
65535;
6.1.2 DPS shall be smaller than (<=) 65535;
6.1.3 MPS shall be smaller than (<=) 65535;
6.2 - MV shall be smaller than:
6.2.1 MV floatting (32bit + IEEE) shall be smaller than: (<=) 65535;
6.2.2 MV normalized (16 bit between [-1;1] by step of 2-15.) shall be smaller
than: (<=) 65535;
6.2.3 MV scaled (16 bit between [215.+215-1] by step of 1) shall be smaller
than: (<=) 65535;
6.3 - xPC not allowed on SAS
6.4 - TPI (SPI) shall be smaller than (<=) 65535;
6.5 - SetPoint shall be smaller than (<=) 65535;
6.6 - Counter shall be smaller than (<=) 65535;.
Limits Gateway SCADA DNP3 (Serie, over IP) and MODBUS Modicon (Serie, TCP)
8 - Limits Gateway SCADA DNP3 (Serie, over IP) and MODBUS Modicon (Serie, TCP):
SpecificationDescription
than (<=) 100
8.1 - SUMMATION ( Nombre SPS addresses + Nombre de MV(including TPI,AI and
counter) addresses + Nombre de xPC (including Setpoint) addresses shall be
smaller than (<=) 65535;
Limits per Gateway (because of EcddGen and EcddConv)

12 - Limits per Gateway (because of EcddGen and EcddConv) :
SpecificationDescription
12.1 - Total per Gateway for xPS shall be smaller than (<=) 37500 ;
12.2 - Total per Gateway for MV(TPI included) + Counter shall be smaller than (<=)
7500;
12.3 - Total per Gateway for xPC + SetPoint shall be smaller than (<=) 5000;
12.4 - Number of Satellit (including SDHMI, protocols, Isagraf,goose croosing ) shall
be smaller than (<=) 24;
2.1.4 Variant attributes value
Note : These checks are not processed for backup devices.

An attribute value can be dependent of another attribute value.
In the following example, the "C26x SCADA Prot." has 2 attributes : "protocol" and "address structure".
The set of possible values for "address structure" depends on the selected value for "protocol".

Energy Automation
C264
C26x SCADA Prot (A) protocol
- T101
depends of - DNP3
- T104
(A) address structure
- Address on 8 bits (1 byte)
- Address on 16 bits (2 bytes)
- Address on 8 bits.8 bits
- Address on 8 bits.8 bits.8 bits
- Address on 24 bits (3 bytes)
At the User Interface, the modification of the "protocol" value may lead to an incompatible "address
structure" value.
06101 / AttributeValue / The attribute value is not valid
Examples :
06101 / AttributeValue / The attribute value is not valid-> [Scs | Ethernet network | C264 | C26X
SCADA prot | address structure]
06430 / AttributeValue / The short name of the data point should not be empty
Example:
06430/AttributeValue/Site | Substation | Voltage level | BAY1: SUI server is configured: short name
of the data point should not be empty
06431 / AttributeValue / Brackets are not allowed in a datapoint short name in presence of SUI.
Example:
06431 / AttributeValue / Scs | Ethernet network | SUI Clt/Server | OPC protocol | SCADA [SPS
com] / Brackets are not allowed in a datapoint short name in presence of SUI.
2.1.5 Relations

The check of a relation depends on its definition in the Structural Database.
A "Mandatory" flag is set to NO on a relation for which the link can be omitted.
Object
(R)
Relation link No link
Mandatory = NO OR
Spare link
If the relation is not linked, then the following message is displayed:

03008 / RelationLinkNull / The optional relation has no link
Examples:

Energy Automation
03008 / RelationLinkNull / The optional relation has no link-> [Site | Substation | Voltage level |
Feeder | has for lock right : <null>]
If the relation is linked to a spare object, then the following message is displayed:
04010 / RelationLinkSpare / The optional relation has a spare link
Examples:
04010 / RelationLinkSpare / The optional relation has a spare link-> [Site | Substation | Substation
DPC | has for AutoManu dependency : Substation DPS]
Some optional relations may have a specific rule which doesnt produce a warning if not filled. These
rules are listed below:
- C26x SCADA protocols have the relation with a main comm. port which hasnt to be filled in
case of protocols on IP (T104, DNP3 on IP, ).
- GHU200 Boards have a relation with a workspace which hasnt to be filled when HMI type is
Simple.
A "Mandatory" flag is set to YES on a relation for which the link is mandatory.
Object (R)
Relation link No link
Mandatory = YES Or
Spare link
If the relation is not linked, then the following message is displayed:

03007 / RelationLinkNull / The mandatory relation has no link
This check isnt treated in the following cases (exception) :

- Case 1 : The relation is an UCA2 addressing relation.
Case 2 : The relation is "UserFunction_RunsOn_PLC" of an Interlock FBD belonging at a Bay
managed by an IED 61850 no-PACiS.
Examples:
03007 / RelationLinkNull / The mandatory relation has no link-> [Site | has for Bypass right : <null>]
If the relation is linked to a spare object, then the following message is displayed:
04009 / RelationLinkSpare / The mandatory relation has a spare link
Examples:
04009 / RelationLinkSpare / The mandatory relation has a spare link-> [Site | Substation |
Substation DPC | has for profile : DPC profile]
If a filter is defined for a relation, the link must be compatible with the filter definition.
Object
(R)
Relation link
Filter link Filter
05011 / RelationLinkFilter / The relation link is not compatible with the filter
Examples:
05011 / RelationLinkFilter / The relation link is not compatible with the filter-> [Site | Substation |
Voltage level | Feeder 1 | circuit breaker | Comp. swit. pos. | 'open' wired on : DI # 0]

Energy Automation
98429 / LoadSharingRelations / Sum of is computed by relations and is provided part of

relations for a specified Built-in should be lower or equal to 33.
2.1.6 Templates
The goal of these checks is to warn user about template coherency.
For templates, check if all components are present in all instances or clones.
This check indicate the template and instance concerned, and the component which are missing. If the
component is a template clone, indicate only the main template.
The way to correct this error is to delete the missing component in the template and to recreate it.
68213 / Templates / One instance of the template is not coherent with the template definition
(Template, Instance, missing component)
68225 / Templates / One instance of the template is not coherent with the template definition , a
root component is missing (Template, Instance's main component, missing root component)
Examples:
68213 / Templates / One instance of the template is not coherent with the template definition
(Template, Instance, missing component) -> [Site-Feeder-Feeder1 | Feeder1, Site | Substation |
Voltage level | Feeder 1, Circuit breaker]
Any template can only use one sub-level of template, i.e. maximum level of inner template is 2.
68254 / Templates / Number of inner templates reached (number, maximum)
2.1.7 IED Model file containing obsolete CommonClass
Check all the model files included in the database to look for obsolete CommonClass due to IEC61850
follow up for PACiS System. To fix error remove the obsolete Model files from the database.
87392 / / Obsolete CommonClass found into a Model file. Please remove this file from the
database (Invalid file)
2.2 System checks
2.2.1 TCP/IP definition on Ethernet Network
2.2.1.1 Device IP addressing
Ethernet Network (A) TCP/IP address

C264 255.255.255.255
OI server
UCA2 gateway (A) network name NW_NAME
UCA2 gen IED
OI client

Energy Automation
Each device connected to an Ethernet Network has 2 attributes "TCP/IP address" and "network
name".
The "TCP/IP address" value of a device, must be unique among all the devices per Ethernet
Network.
The "network name" value of a device, must be unique among all the devices per Ethernet
Network.
The network name (alias TCP/IP) must not be reseved by operating system.
Exception :
The unicity is not required between an OI server and an OI client embedded in the same physical
device. Therefore, if an "OI client" is linked to an "OI server" through the relation "has for HMI
server", then it's not checked.
07012 / TCPIPattribute / The attribute value is not unique
Examples :
07012 / TCPIPattribute / The attribute value is not unique-> [TCP/IP address, 255.255.255.255]
07012 / TCPIPattribute / The attribute value is not unique-> [network name, NW_NAME]
07164 / TCPIPattribute / The network name is reserved by operating system
2.2.1.2 SNTP servers
On SCS object, it is possible to configure the TCP/IP addressing for SNTP server (primary and
auxiliary addresses).
This addresses may reference an existing device in database or a devices outside the PACiS system.
Some rules must be followed for these addresses.
If one of both IP addresses is configured and represent a PACiS device, this device must be a
computer.
07249 / TCPIPattribute / The PACiS SNTP server must be a computer or a gateway (IP address,
device)
If auxiliary IP address is configured primary address must be configured too.

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

07251 / TCPIPattribute / The two SNTP addresses must be different (IP address)
If the SNTP server (main or aux) is a computer, the datapoint External clock status is mandatory for
it:
07292 / TCPIPattribute / The datapoint External clock status is required on the computer running
a SNTP server service
Gateway SNTP server :

Energy Automation
A gateway defined as SNTP server must have relation IsSynchronizedBy defined, and linked to one
of its own DNP3 scada protocol
07433 / TCPIPattribute / Scs | Ethernet network | GTW / The SNTP server gateway doesn't have
synchronization source defined
07434 / TCPIPattribute / Scs | Ethernet network | GTW The synchronization source of a gateway
must be situated under this gateway
07435 / TCPIPattribute / Scs | Ethernet network | GTW / The synchronization source of a gateway
must be a DNP, T101 or T104 scada protocol
2.2.2 IEDs location
All IEDs contained under the Ethernet network must be located into the same substation, which is the
substation associated to current configuration (ie not imported through gateway IEC/IEC)
96423 / IedLocation / All IEDs of ethernet network must be situated into the same substation
2.2.3 Alarm
2.2.3.1 Default alarm processing type
When at least one SUI server is configured, the parameter DefaultAlarmProcessingType can not
take value Gravity Level Basis
90101 / SUI / The attribute value is not valid-> [default alarm processing type, Gravity Level Basis]
2.2.4 UCA2/IEC Physical Devices
2.2.4.1 Redundancy
2.2.4.1.1 PACiS redundancy
(R) has for backup

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

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

OI server (main) OI server (backup)
(R) is backup of
For a device, the relations "has for backup" and "is backup of" are mutually exlusive.
30044 / Redundancy / The relation types are not compatible-> [has for backup, is backup of]

Energy Automation
A main and its backup must be devices of the same type.
30073 / Redundancy / The main and the backup are not of the same type
Examples :
30073 / Redundancy / The main and the backup are not of the same type-> [OI server, C264]
2.2.4.1.2 C264-R redundancy
Redundancy of a C264R is managed by the attribute number of masters. If it is set to 2, it is

considered as redounded.
A redunded C264R mustnt manage Isagraf or FBD functions.
78267 / C264R / A redunded C264R mustnt manage Isagraf or FBD functions.
2.2.4.1.3 GATEWAY redundancy
When a gateway is redundant, only the SCADA protocols T101, T104 and IEC61850 manage
redundancy. For all other protocols, the redundancy must be managed physically. (i.e. not thru the
SCE)
20333 / SCADA_Networks / Only SCADA protocols T101, T104 and IEC61850 are managed for
redundant gateways.
No LBus permit under a redunded gateway in V4 Mode
77383 / Gateway Server / Function is not allowed on redunded Gateway V4 (Not allowed
functions).
On a not redunded gateway the system datapoint Redundancy link is not allowed
30416 / Redundancy / The system datapoint 'Redundancy link' is only allowed on redunded
gateways V5
On a redunded gateway V5 the system datapoint Redundancy link is mandatory
30417 / Redundancy / The system datapoint 'Redundancy link' is mandatory on redunded

gateways V5
2.2.4.1.4 Incompatible component for redounded computer
For a C264 redounded the following objects are not compatible:
- TMU 210 Board

- T101 Master legacy

Energy Automation
30297 / Redundancy / <OBJECT PATH> / Not compatible component on a C264 redounded
2.2.4.2 Goose transmition
It is not possible to have Gooses objects under a gateway V4, or a gateway V5 with goose activation
flag set to no. This is also applicable for upper gateway (represented by generic IED), where the
goose activation flag is the attribute GSEControl creation under IEC61850 Capabilities tab.
User must auto address the gateway to delete them.
77401 / Gateway / Gooses are defined under a gateway without gooses activated. An auto
adressing is necessary
77419 / Gateway / For upper gateway, the has for server relations ModellingAndGooseUsage
attribute value should be Goose Only
2.2.4.3 Client - Server relation on UCA2/IEC
A Client must not be linked to the same Server through multiple relations "has for UCA2/IEC
server".
(R) has for UCA2/IEC server

C264_1 (client) C264_2 (server)
(R) has for UCA2/IEC client
08013 / RelationClientServer / Multiple links to the same server
Examples :
08013 / RelationClientServer / Multiple links to the same server-> [has for UCA2/IEC server :
C264_2]
Case of "OI server" Client :
The attribute "goose usage", of the relation "has for UCA2/IEC server", must be set to the "Data model
only" value.

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

- Data model only
- Goose only
- Data model and Goose
08107 / RelationClientServer / The relation attribute value is not valid. It must be: Data model only
Examples :

Energy Automation
08107 / RelationClientServer / The relation attribute value is not valid. It must be: Data model only-
> [has for UCA2/IEC server : OI server, modeling/goose usage = Goose only]
for a relation client-server with data model usage = data model with or without GOOSE, a C264
cannot have more than 16 clients and/or 50 servers.
Nota :
In the max of 16 clients, the non-configured clients such as the equipment simulator arent taken
into account. A constant in the settings defines the number of non-configured clients.
Exceptions :
The relations client-server with goose only are out of scope this rule.
This rule is also out of scope for C264 used as PCCN Gateway (called ###CT###).

C264_1 (client) C264_2 (server)
(R) has for UCA2/IEC client
<08141> / RelationClientServer / More than 16 clients for the same computer server
<08140> / RelationClientServer / More than 50 servers for the same computer client
2.2.4.4 Management of bays
02359 / Capacity limits / The number of bays managed by a same computer is oversize (Number
of bays, Maximum authorized)
Example :
02359 / CapacityLimits / The number of bays managed by a same computer is oversize (Number of
bays, Maximum authorized) -> [129, 128]
2.2.4.5 UCA2/IEC Mapping on Ethernet Network
2.2.4.5.1 Mapping definition
Note : These checks are only processed for non-backup devices.

Example of UCA2 Mapping in a Computer :

Energy Automation
(A) protocol
Ethernet network UCA2
C264
c26x UCA2 Map
LD
GenBrick
CO
GenDCO
LD0 for C26x

C26xDIAG
ST for C26xDIAG
AIUSt0
T103 (Legacy Network)

T103_IED
ext UCA2 Mapping continuation of LD0 definition
LD0 for IED
IEDDIAG
ST for IEDDIAG
CommSt
c26x SCADA Prot (SCADA Network)

ext UCA2 Mapping continuation of LD0 definition
LD0 for TCI
TCIDIAG
ST for TCIDIAG
CommSt
Example of IEC Mapping in a Computer :
(A) protocol
Ethernet network IEC 61850
C264
c26x IEC Map
IECxLD
GenLN
CO
DPCxSBOxS
belongs to the list of generic
IEC LD0 - C26x LogicalDevices of the "c26x IEC Map"
C26xDIAG
IEC ST for C26xDIAG
AIUSt0
T103 (Legacy Network)

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

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

- 1, and only 1, UCA2 or IEC61850 Mapping, is allowed.
- this Mapping must be compatible with the value ("UCA2" or "IEC61850") set to the "protocol"
attribute of the "Ethernet network".
13110 / EthernetMapping / The component is missing


Energy Automation
13109 / EthernetMapping / The component is not allowed
Examples, for an UCA2 "Ethernet network" protocol :

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

13109 / EthernetMapping / The component is not allowed
Examples, for an "UCA2" protocol :

13110 / EthernetMapping / The component is missing-> [ext UCA2 Mapping]
13109 / EthernetMapping / The component is not allowed-> [ext IEC Mapping]
For each Logical Device defined under the UCA2/IEC Mapping :

- its name must be unique in the mapping. LD name is prefixed by Alias TCP IP and by
IED name (uniquely for legacy IED LD).
- For PACiS IED, if the Logical Device is a generic one, its name must not contain the sub-string
"LD0" (reserved for system Logical Devices)
Examples :
- In the "c26x UCA2 Map" mapping : "LD" name must be unique among all the generic Logical
Devices of the "c26x UCA2 Map" and it must not contain the sub-string "LD0".
In the "c26x IEC Map" mapping : "IECxLD" name must be unique among all the generic
Logical Devices of the "c26x IEC Map" + of all the "ext IEC Mapping" of Legacy Devices, and it
must not contain the sub-string "LD0".
13020 / EthernetMapping / The name is not unique
13021 / EthernetMapping / The name is not valid
Examples, for an UCA2 "Ethernet network" protocol :

13020 / EthernetMapping / The name is not unique-> [LD]
13021 / EthernetMapping / The name is not valid-> [genLD0]
For each Brick/LogicalNode defined under a Logical Device :

- its name must be unique in the Logical Device
Examples :
- In the "c26x UCA2 Map" mapping :

"GenBrick" name must be unique among all the Bricks of the "LD" Logical Device.
"C26xDIAG","IEDDIAG" and "TCIDIAG" names must be unique among all the Bricks of the
"LD0" Logical Device (ie, among all the Bricks of "LD0 for C26x" + of "LD0 for IED" + of "LD0
for TCI").
- In the "c26x IEC Map" mapping :

"GenLN" name must be unique among all the Logical Nodes of the "IECxLD" Logical Device.

Energy Automation
"C26xDIAG" and "TCIDIAG" names must be unique among all the Logical Nodes of the "LD0"
Logical Device (ie, among all the Logical Nodes of "IEC LD0 - C26x" + of "IEC LD0 - TCI").
For each Data Object defined under a Functional Component (CO) :

- its name must be unique in the Functional Component
Examples :
- In the "c26x UCA2 Map" mapping :

"GenDCO" name must be unique among all the Data Objects of the "CO" Functional
Component.
- In the "c26x IEC Map" mapping :

"DPCxSBOxS" name must be unique among all the Data Objects of the "CO" Functional
Component.
For each Data Object defined under a Functional Component :
Only 1 relation "has for UCA2 address" or "has for IEC address" is allowed (0 or 1)
27113 / EthernetAddressing / Multiple links
For the following Functional Component types of a Computer :

- CO (only before PACIS v4)
- MX
- ST
the maximun count of DataObjects is 50.
02003 / CapacityLimits / The count of DataObject components is not valid (count, maximum)
Examples :
02003 / CapacityLimits / The count of DataObject components is not valid (count, maximum)->
[101, 100]
For each Computer, the maximun count of Node is 1000.
02430 / CapacityLimits / The count of Node for C264 should be lower or equal to 100.
2.2.4.5.2 UCA2 Goose Rank of Data Object
Note : This check is processed only for UCA2 protocol.

Energy Automation
(A) protocol
Ethernet network UCA2
C264
c26x UCA2 Map
LD
GenBRIC
ST (A) goose transmission
GenSI - Manual DNA vector
(A) rank in goose - Manual user status vector
10
(A) goose transmission
GenSIT - Manual DNA vector
(A) rank in goose - Manual user status vector
10
Among all the SI and SIT Data Objects having their attribute "goose transmission" set to the "Manual
DNA vector" value, the value of the attribute "rank in goose" must be unique.
Among all the SI and SIT Data Objects having their attribute "goose transmission" set to the "Manual
user status vector" value, the value of the attribute "rank in goose" must be unique.
32074 / GooseRanks / The attribute value is not unique in the mapping for DNA transmission
Examples :
32074 / GooseRanks / The attribute value is not unique in the mapping for DNA transmission->
[rank in goose (x pair of bits), 10]
2.2.4.5.3 IEC Goose
Note : This check is processed only for IEC protocol.

For a given IED, the size of the goose for SPS,DPS, MPS must be less or equal to 1300 bytes. Idem
for the size of the goose for measurements and counters.
Its a warning for a non PACiS IED else its an error.
<54142> / GooseLimits / Goose limit is reached for binary inputs

<54143> / GooseLimits / Goose limit is reached for measurements
For a given IED, the size of the goose for LSP, must be less or equal to 3750 bytes.
Its a warning for a non PACiS IED else its an error.
<54243> / GooseLimits / Goose limit is reached for LSP
For a given IED, the size of goose for MV must be less than 64
<54393> / GooseLimits / Goose limit is reached for MV
In a database, all Goose ID must be unique for a network.
58170 / GooseUnicity / Goose ID (AppID) must be unique for network


Energy Automation
The Numerical AppID attribute of gooses cant be set to 0000. The attribute must have a
hexadecimal value between 0001 and 3FFF.
95422 / Goose / The Numerical AppID of goose can't be set to '0000' (min, max)-> [0001, 3FFF]
49424 / MultiState / Graphic | OI_CLIENT | MIMIC_BANNER | C264_39 | Ctrl MultiState / The

Mode control DPC datapoint cannot be mapped to "IsManagedBy" relation [Scs | Ethernet network |
GTW_IECM | Mode control DPC]
In an IEC Mapping of C264, the Goose Rank attributes of each ST and MX goosed DataObject (Auto
or Manu) must be consecutive from 1 and unique (without duplication).
Exception :
The DataObject linked to the DataPoint of type Module_nMPS datapoint type isnt concerned by
twice following checks : 32332 and 32333.
32332 / HoleInGooseRanks / There are holes at level Goose Rank attributes [device, goose type]
32333 / DuplicationInGooseRanks / There are duplications at level Goose Rank attributes

[device, goose type]
32334 / GooseRankNotAllocated / There are goosed dataobjects with a Goose Rank to 0 [device,
goose type]
Examples :
32332 / HoleInGooseRanks / There are holes at level Goose Rank attributes [device, goose type]-
> [Scs |SBUS| CTE_TG225kV, ST ]
32333 / DuplicationInGooseRanks / There are duplications at level Goose Rank attributes [device,
goose type] -> [Scs |SBUS| CTE_TG225kV, MX ]
32334 / GooseRankNotAllocated / There are goosed dataobjects with a Goose Rank to 0 [device,
goose type] -> [Scs |SBUS| CTE_TG400kV, ST ]
In an IEC Mapping of a redunded gateway V5 managing gooses:
The Goose Rank attribute of the data object RedSt must be 1.
32335 / GooseRank / The data object 'RedSt' must have the gooserank '1' in all gooses
The data object RedSt must be in all the gooses ST of the gateway (it must have relations
Has for goose linked to each goose ST). It is not possible to create the relations manually;
they are created by the auto-addressing.
97337 / Gooses gateway / On a redunded gateway managing gooses, the data object RedSt
must have a relation 'Has for goose' for each gooses ST. Please run an auto-addressing.
In an IEC Mapping of a gateway V5 managing gooses, all the data objects ST or MX with a goose
rank > 0 must have a relation Has for goose linked to a goose of the gateway.
97336 / Gooses gateway / A data object with the gooserank > 0 must have a relation 'Has For
Goose' linked to a goose
A gateway goose can not have a dataset with size superior of 1300.

Energy Automation
54338 / GooseSize / Goose limit is reached (size, maximum)
02425 / CapacityLimits/ Scs | Ethernet network | X21_C264 | T103 (LB) | X21_C434/ Invalid count
of counter datapoint defined on T103 legacy protocol (count, maximum) -> [24, 16]
2.2.4.5.4 Addressing of OI printer System Datapoints
Note : The figure shows an UCA2 Mapping, but the checks are identically processed for UCA2 and
IEC61850 Mappings.
OI server
HMI UCA2 Map.
LD0 for OI
HMIDIAG
ST for HMIDIAG
SOE1St0
SOE1St1
SOE2St0
SOE2St1
SLB1St0
SLB1St1
SLB2St0
SLB2St1
(A) printer
OI printer Sequence of Events
type
System infos (R) has for UCA2 address
Printer status SOESt
BackupPrint stat (R) has for UCA2 address
SOESt
(A) printer
OI printer type Log Book
Printer status SLBSt
(R) has for UCA2 address
BackupPrint stat SLBSt
If the "OI printer" has its attribute "printer type" set to the "Sequence of Events" value, then its
system Datapoints "Printer status" and "BackupPrint stat." must be linked to an UCA2/IEC address
named "SOESt". Only 1 relation is allowed.
If the "OI printer" has its attribute "printer type" set to the "Log Book" value, then its system
Datapoints "Printer status" and "BackupPrint stat." must be linked to an UCA2/IEC address named
"SLBSt". Only 1 relation is allowed.
27050 / EthernetAddressing / The relation link is not valid

Examples :
27050 / EthernetAddressing / The relation link is not valid-> [has for UCA2 address : SLB1St0]
27113 / EthernetAddressing / Multiple links-> [has for UCA2 address : SOE1St0]

27113 / EthernetAddressing / Multiple links-> [has for UCA2 address : SOE2St0]
2.2.4.5.5 Addressing of OI client System Datapoints

Energy Automation
IEC61850 Mappings.
OI server
HMI UCA2 Map.
LD0 for OI
HMIDIAG
ST for HMIDIAG
HMISt0
HMISt1
HMISt2
HMISt3
HMISt4
HMISt5
HMISt6
HMISt7
(R) has for HMI server
OI client
OI client link HMISt
The system Datapoint "OI client link" of an "OI client" must be linked to an UCA2/IEC address
named "HMISt". Only 1 relation is allowed.
27050 / EthernetAddressing / The relation link is not valid

Example :
27113 / EthernetAddressing / Multiple links-> [has for UCA2 address : HMISt0]
27113 / EthernetAddressing / Multiple links-> [has for UCA2 address : HMISt2]
2.2.4.5.6 Addressing of Computer boards Status Datapoints
IEC61850 Mappings.
C264
C26x UCA2 Map.
LD0 for C26x
C26xDIAG
ST for C26xDIAG
DIUSt0
DIUSt1
DIUSt2
DIUSt3

(A) physical board number 0
DIU200
DIU status DIUSt0
The status Datapoint of a Computer board must be linked to an UCA2/IEC address with a name
matching the board type and ending with the value of the attribute "physical board number". Only 1
relation is allowed.
27067 / EthernetAddressing / The address in not compatible with the board number

Energy Automation
Example :
27067 / EthernetAddressing / The address in not compatible with the board number-> [has for
UCA2 address : DIUSt1, DIU200.physical board number = 0]
2.2.4.5.7 SCL naming
For SCL, all IEC names must be defined for electrical objects substation, voltage level, bay, module
and datapoint.
To get IEC name, an attribute may be filled in each object, or short name may be normalized if thi
attribute is not filled.
The normalization of a short name keep only alphabetical and numerical characters (in case of
character with accent, the accent is removed).
After looking dedicated attribute and normalized short name, if both of them give an empty string,
an error is raised.
27309 / EthernetAddressing / Invalid value for SCL name: SCL Name attribute or normalized short
name can not empty.
For SCL name, for module which have sub-equipment (Tap function) the concatenation of the 'SCL
Name' of this two objects cant be more than 6 characters.
27311 / EthernetAddressing / Concatenation of 'SCLName attribute of Module and of sub

equipment size is not valid (Value, current size, maximum size)
For Functional Naming, in electrical part object of same level must have a unique SCL Name.
All Substations 'SCL Name' must be different under the Site object
All Voltage level ''SCL Name' must be different under the same Substation object
All Bays SCL Name' must be different under the same Voltage level object
All Modules 'SCL Name' must be different under the same Bay object
All Sub-equipments (Only TapFct) 'SCL Name' must be different under the same Module
object
27310 / EthernetAddressing / Value for SCL Name' must be unique for object of same level
Functional Naming Coherency check
This check verifies that the mapping is still coherent with the electrical topology. The coherency can be
broken when moving, deleting or renaming the IEC name of a substation, voltage level, bay, module or
a sub-equipment
Usually, in functional naming:

The logical device name is a concatenation of substation, voltage level and bay iec name.
The logical node name is the class name with a prefix if the datapoint is under a module or a
sub-equipment. (For more details, see IEC documentation).
For a logical device error message:
13333 / EthernetMapping / Mapping of the logical device is not consistent with electrical topolgy
(mapping, topology)
For a logical Node error message:


Energy Automation
13334 / EthernetMapping / Mapping of the logical node is not consistent with electrical topolgy
(mapping, topology)
The mapping parameter shows what the actual mapping name is.
The topology parameter shows what the mapping name should be to be coherent with the electrical
topology.
Particular case of non PACiS IED
Non PACiS IED has two capabilities for functional naming describe by attribute LD Name editable
and LN prefix editable
These two parameters enable or disable capability for IED to update his mapping by renaming logical
device name and logical node prefix.
If incoherency is detected in IED mapping and capability to rename the error object (logical device or
logical node) is not enabled, an error is raised.
For logical device:
13331 / EthernetMapping / The functional naming of the IED is incoherent and logical device
name edition is not allowed by IED (mapping, topology)
For logical node:
13332 / EthernetMapping / The functional naming of the IED is incoherent and logical node prefix
edition is not allowed by IED (mapping, topology)

Energy Automation
2.2.4.6 Computer Boards
Note : These checks are only processed for non-backup computers.
Count of boards in a C264 computer :
A B C D E F G H I J K L M N O P Q R
BIU CPU
Slots from E to P may contain a board of the following types :

- AIU2xx
- DOU2xx
- DIU2xx
- CCU2xx
Slot C may contain 1 DSPio board or 1 Switch board or 1 board of the above types.
Slot D may contain 1 Switch board or 1 board of the above types.
Slots Q and R may contain 1 TMU200 board or 1 board of the above types to slot Q only.
If TMU210 is present, then

the maximum count of boards must be 13 (because DSPio must be present in slot C)
else if a TMU200 or TMU220 is present, then
the maximum count of boards must be 14
else
Count of boards in a C264C computer :
A B C D E F G H
BIU CPU
Slots from E to F may contain a board of the following types :

- AIU2xx
- DOU2xx
- DIU2xx
- CCU2xx
Slot C may contain 1 DSPio board or 1 Switch board or 1 board of the above types.
Slot D may contain 1 Switch board or 1 board of the above types.
Slots G and H may contain 1 TMU200 board or 2 boards of the above types.
If a TMU210 is present , then

the maximum count of boards must be 3 (because DSPio must be present in slot C)
else if a TMU200 or TMU220 is present, then
else
09144 / ComputerBoards / The count of TMU boards is not valid (count, maximum)
09145 / ComputerBoards / The count of AIU boards is not valid (count, maximum)
09003 / ComputerBoards / The count of board components is not valid (count, maximum)

Energy Automation
Examples :
09003 / ComputerBoards / The count of Board components is not valid (count, maximum)-> [6, 4]
Attribute "physical board number" of a board.
C264 (A) board number

AIU200 1
DOU200
DIU200
CCU20x
For boards AIU201, AIU210, DIU200, DIU210, DOU200, CCU200, the "board number" attribute
values must be unique and contiguous. This board number is a physical number defined by the user.
For boards DIU211, DOU201, CCU211, (boards managing the slot number) the board number is a
computed logical number : It is unique and contiguous by board type.
09015 / ComputerBoards / The attribute value is not unique for the board type
09016 / ComputerBoards / The attribute values are not contiguous for the board type (board type,
attribute)
Examples :
09015 / ComputerBoards / The attribute value is not unique for the board type-> [physical board
number, 1]
09016 / ComputerBoards / The attribute values are not contiguous for the board type (board type,
attribute)-> [CCU200, physical board number]
09346 / ComputerBoards / One of DIU or DOU type card must have for board number attribute
value equal to nought
For each type of card (DIU or DOU), the smallest Board Number attribute values must be
equal to nought value.
09356 / ComputerBoards / Check if the sum of the number of characters of the Banner line
attribute values is less than the minimum value authorized
The sum of number of characters of all Banner line attribute string values must be equal or
more than the minimum value authorized for this concatenation.
Check raised only if LHMI_Type is not Simple.
Attribute "slot number" of a board managing the slot number.
C264 (A) slot number

DIU211 C
DOU201
CCU211
For boards managing the slot number, the "slot number" attribute values must be unique.
09282 / ComputerBoards / The attribute value is not unique for boards of rack

Energy Automation
Examples :
09282 / ComputerBoards / The attribute value is not unique for boards of rack -> [slot number, C]
GHU200 board.
The GHU200 board has an attribute "HMI type" and a relation "has for workspace".
C264 - Simple
(A) HMI type
GHU200 - Complete
Led # 4 - Old
(R) has for workspace
(R) displays state of Graphic

Comp. workspace
SPS
DPS
- If the value of the "HMI type" attribute is different from "Complete", then the relation "has for
workspace" must not be linked.
09078 / ComputerBoards / The relation link is not compatible with the board type-> [has for
workspace : Comp. workspace, HMI type = Simple]
- If the AVR panel is configured, the computer must manage an AVR function
09304 / ComputerBoards / The usage of the AVR panel is allowed only if computer manage an
AVR function
- If the AVR panel is used as default panel for start or inactive, the AVR panel must be configured
09305 / ComputerBoards / The usage of the AVR panel as default is allowed only if AVR panel is
configured
- If the default panel for start or inactive is Graphical Bay Panel n, n must be lesser or equal to
number of Graphical Bay Panel configured
09306 / ComputerBoards / The usage of the graphical bay panel 'n' as default is allowed only if up
to 'n' graphical bay panel are configured (number of graphical bay panel) -> [12]
- If the value of the "HMI type" attribute is "Simple", then "Led#5" must not be used (no relation link
from "Led#5" to a Datapoint).
35077 / BoardLeds / The use of this LED is incompatible with the board type (type)-> [HMI type =
Simple]
- If the value of the "HMI type" attribute is "Simple", Led object cant has displays state of relation
with attribute Led behaviour equals to used for alarm
35217 / BoardLeds / The attribute Led behavoir on relation has displays state can be used for
alarm only when GHU200 board is Complete.
- A led can be used by a data point only if this data point is managed by the same computer than the
led computer.

Energy Automation
35227 / BoardLeds / Board led can be use only by data point managed by the led server
- Only led #14 to led #17 can be used by a data point if the led allocation is set to predefined at the
GHU board level
35281 / BoardLeds / The use of this LED is incompatible with the predefined led allocation
TMU200, TMU210 and TMU220 board

This three boards are exclusive each other for the same computer.
09139 / ComputerBoards / TMU220, TMU210 and TMU200 can not belong to the same computer.
TMU210 board
When used, its DO channels can only be wired to a the open or close states of the Switch Control
DPC of a breaker
The DO_0 can be wired on open state and DO_4 on channel state
09180 / ComputerBoards / DO channels of TMU210 can only be used for open (DO_0) or close
(DO_4) states of the Switch Control DPC of a breaker
When used, the protection function automatism is mandatory because the SPS synthesis of
instantaneous defined under it is mandatory
This check is not done for following cases:
- SCE is Poste d application (i.e., lax flag sce.Poste_d is set).
- an internal Synchrocheck of type 2 is configured on the computer
09197 / ComputerBoards / when TMU210 is configured, protection function automatism is

mandatory for SPS synthesis of instantaneous
CPU260 board
When port 3 and 4 are both used, they must have same baud rate.
<09201> / ComputerBoards / Port 3 and 4 of CPU260 must have same baud rate when used.
AOU200 board
When a computer is redunded, AOU200 board is not allowed.
<09270> / ComputerBoards / When a computer is redunded, AOU200 board is not allowed.
2.2.4.7 Computer extension racks
Attribute "rack number" of a extension rack.

Energy Automation
C264 (A) physical board number

AIU200 1
DOU200
DIU20x
CCU20x
For the set of the extension racks of a computer, the "rack number" attribute values must be unique
and contiguous.
80279 / Extension rack / The attribute value is not unique for the extension rack
80280 / Extension rack / The rack numbers are not contiguous
2.2.4.8 Computer Settings
Note : This check is only processed for non-backup computers.

A computer has the following attributes :
(A) BI filtering / debouncing delay (ms)

C264 1
(A) BI filtering / filtering delay (ms)
0
(A) Measurements / debouncing delay (ms)
(A) Measurements / filtering delay (ms) 1
0
(A) Counter / debouncing delay (ms)
(A) Counter / filtering delay (ms) 1
0
For each attribute category (BI filtering / Measurements / Counter), if the attribute "debouncing delay"
is set to 0 value, then the attribute "filtering delay" must be set to 0 value.
10096 / ComputerSettings / The attribute values are not compatible
Examples :
10096 / ComputerSettings / The attribute values are not compatible-> [BI filtering/deboucing delay
(ms), BI filtering/filtering delay (ms)]
2.2.4.9 Computer Klaxon

A computer may have the following relation :
(R) has its klaxon controlled by

C264 SPC C264
DOU200
(R) wired on
DO # 0
The "SPC" link of the relation "has its klaxon controlled by" must be wired on a DO channel of the
Computer.
10033 / ComputerSettings / The relation link is not a wired datapoint

10034 / ComputerSettings / The relation link is not a datapoint wired on the Computer

Energy Automation
Examples :
10033 / ComputerSettings / The relation link is not a wired datapoint-> [has its klaxon controlled
by : Bay SPC
10034 / ComputerSettings / The relation link is not a datapoint wired on the Computer-> [has its
klaxon controlled by : Bay SPC
2.2.4.10 Computer Printers
Log Management attributes of a Serial Printer
C264
(A) buffer size
Serial printer 1000
(A) nb of events to suppress when saturated 300
The following constraint beetween the two attributes values must be respected :
"buffer size" > "nb of events to suppress when saturated"
29105 / Printers / buffer size (events) is not greater than nb of events to suppress when saturated
Examples :
29105 / Printers / buffer size (events) is not greater than nb of events to suppress when saturated-
> [200, 300]
Printing format attributes of a Serial Printer
C264
(A) Chronology column rank
Serial printer 1
(A) Time Stamp column rank
2
(A) Origin column rank
3
(A) Object Name column rank 4
(A) Object Message column rank 5
The value of each " column rank" attribute must be unique.
29072 / Printers / The column rank is not unique
Example :
29072 / Printers / The column rank is not unique-> [Chronology column rank, Object Message
column rank, Object Name column rank, Origin column rank, Time Stamp column rank, 1]
Wiring a Printer on an extension rack
When the Master rack is configured to 2 in SCE under C264. (numbers of rack = 2 for C264
standalone or back-up otherwise) the printer cant be wired on an extension rack.
29347 / Printers / The log-book printer can be connected on a serial line only in case of single
Main configuration

Energy Automation
78350 / C264R / A C264 redundant can't contain a serial printer.

Energy Automation
OI Server
In Hot Redundancy mode the OI Server must have the datapoint Redundancy Status.
Red.Status must be present in Hot

Redundancy Mode
77258 / OI / On OI Server in Hot Redundancy mode datapoints Red.Status must be present under
OI Server.

Energy Automation
In Hot Redundancy mode, if exist more than one OI Clients exists, each OI Server is HMI
server for at least one OI client.
Has for Backup
77260 / OI / In Hot Redundancy mode if exist more than one OI Client, each OI Server is HMI
server for at least one OI client.

Energy Automation
In twin redundancy mode each OI client must have OI Server main as HMI server.
Has for Backup
77261 / OI / In twin redundancy mode each OI client must have OI Server main as HMI server.
2.2.4.11 OI server Printers
Note : These checks are only processed for non-backup OI servers.
Count of OI Printers for an OI server
OI server
(A) printer type Sequence Of Events
OI printer 1
(A) printer type
OI printer 2 Sequence Of Events
(A) printer type Log Book

OI printer 3
(A) printer type
OI printer 4 Log Book
For an "OI server" : the maximum count of OI Printers, typed as "Sequence Of Events", is 2.
For an "OI server" : the maximum count of OI Printers, typed as "Log Book", is 2.
29004 / Printers / The count of OI printer components is not valid (type, count, maximum)
Examples :
29004 / Printers / The count of OI printer components is not valid (type, count, maximum)->
[Sequence Of Events, 4, 2]
Number attribute of OI Printers for an OI server
For an "OI server" : the number attribute of its printers must be unique

Energy Automation
29228 / Printers / More than one printer with same number is defined for OI server (number) ->
[<number>]
Log Management attributes of an OI Printer
OI server
(A) buffer length
OI printer 60
(A) recovery length 45
The following constraint beetween the two attributes values must be respected :
"buffer length" > "recovery length"
29105 / Printers / buffer length (s) is not greater than recovery length (s)
Examples :
29105 / Printers / buffer length (s) is not greater than recovery length (s)-> [60, 61]
Printing format attributes of an OI Printer
OI server
(A) Chronology column rank
OI printer 1
(A) Time Stamp column rank
2
(A) Origin column rank
3
(A) Object Name column rank
(A) Object Message column rank
4
(A) Origin Cat. column rank
5
0
(A) Origin Ident. column rank
0
The value of each " column rank" attribute different of 0 must be unique.
The maximum number of characters by printing line is 154.
29072 / Printers / The column rank is not unique
Example :
29072 / Printers / The column rank is not unique-> [Object Message column rank, Object Name
column rank, 3]
29203 / Printers / The size in character of the printing line is too long
Example :
29203 / Printers / The size in character of the printing line is too long -> [205, 155]
2.2.4.12 OI server Symbols
Note : These checks are only processed for non-backup OI servers.
Count of Send Order actions for an OI server

Energy Automation
(R) has for HMI Client (R) has for workspace

OI Server Oi Client OI Workspace
Window
Mimic
Symbol
Send Order
An OI Server can not manage more than 1024 Send Order in all of his mimics.
Count all Send Order of all mimics of all workspaces of all clients of the Server.
Doesnt treat a workspace twice if set as workspace of two clients.
02003 / CapacityLimits / The count of Send Order components is not valid (count, maximum)
2.2.4.13 UCA2/IEC Gen IED data model reference
(A) model file name

UCA2/IEC gen IED model.xml
The value of the attribute "model file name" is mandatory.
34101 / DataModelReference / The attribute value is not valid-> [model file name]
2.2.4.14 Cyclic SPS

Upto 8 cyclic SPS can be managed per computer basis
59003 / CalculatorCyclicSPS / The count of cyclicSPS components is not valid (count, maximum)
2.2.4.15 Computer AM Acquisition
For each C264 the delta between Delta between 'long AI scanning cycle' and 'short AI scanning cycle'
must be greater or equals to 500 ms.
76263 / C264 AM Acquisition / Delta between 'long AI scanning cycle' and 'short AI scanning cycle'
must be greater or equals to 500 ms.
2.2.4.16 Timestamped unknown for SCADA

In an SCE database, if there is a Gateway IEC/IEC client or an OPC DA SUI, the attribute
timestamped unknown for SCADA of this gateway shall be forced to No.
06371 / Attribute value / Attribute timestamped 'unknown' for SCADA cannot be activated for an
IEC/IEC gateway
In an SCE database, If there is a SUI OPC Client, the attribute 'Timestamp unknown for SCADA'
should be set to NO
06374 / Attribute value / Attribute 'Timestamp unknown for SCADA' should not be equal to 'yes' if
there is a SUI OPC client in the configuration

Energy Automation
The timestamp configuration should be the same for all the Gateway PC, SUI server and C264 in an
IEC61850 ring.
06372 / C264 / Attribute 'UNKNOWN' transitions timestamped by SCADA should be set to No
because there is an IEC/IEC gateway
06388 / GTW / Attribute timestamped 'UNKNOWN' for SCADA should be set to No because of the
presence of an IEC/IEC gateway
06373 / SUI / Attribute timestamped 'unknown' for SCADA should be set to No because there is an
IEC/IEC gateway
2.2.5 Wave Records of computers
2.2.5.1 Common check for fast and slow records
For a Fast or a Slow Wafeform, a datapoint can not be configurated more than once for the same
relation (record, trigger and analog channel lists).
36195 / WaveRecording / multiple links to the same datapoint -> [external id of the relation,
external id of the other relation]
A Wave Record can only registrer data point wired physically on the same server tha the computer
which mange the Wave Record.
A Wave Record can only registrer data point managed by wired physically on the same server
than the computer which mange the Wave Record, and not acquire on IED.
36234 / WaveRecording / Data point register by wave record must be manage by same computer
than wave record computer, and not acquire on IED -> [Path of the record relation]
C264
DREC ready
Wave fast/slow record
36246 / WaveRecording / The datapoint 'DREC ready' must be present if a Wave recording is
configured
2.2.5.2 Wave Fast Record

Energy Automation
C264
Wave fast record (A) pre-trigger cycle 0
(A) total cycles
480 | 240 | 120 | 60
(A) number of files
1|2|4|8
The following constraints beetween the attributes must be respected :

"pre-trigger cycle" "total cycles"
"number of files" "total cycles" 480 cycles
36102 / WaveRecording / pre-trigger cycle is greater than total cycles

36103 / WaveRecording / number of files * total cycles is not lower than 480
Examples :
36102 /WaveRecording / pre-trigger cycle is greater than total cycles-> [2, 1]
36103 / WaveRecording / number of files * total cycles is not lower than 480-> [8, 480]
Fast Waveform must have a count of record less or equal than 128.
36361 / WaveRecording / The count of records linked to WaveForm is not valid (current, max)
2.2.5.3 Wave Slow Record
C264
Wave slow record (A) pre-trigger cycle 0
(A) total records
480 | 240 | 120 | 60
(A) number of files
1|2|4|8
The following constraints between the attributes must be respected :

"pre-trigger cycle" < "total records"
"number of files" "total records" 5000 records
36103 / WaveRecording / pre-trigger cycle is not lower than total records

36102 / WaveRecording / number of files * total records is greater than 5000
Examples :
36103 / WaveRecording / pre-trigger cycle is not lower than total records-> [2, 1]
36102 /WaveRecording / number of files * total records is greater than 5000-> [50, 1000]
The following checks depend on the value of the attribute "electrical frequency" :
(A) Measurements / electrical frequency

C264
50 Hz 60 Hz
(A) integration time
Wave slow record [1..180000] [1..216000]
(R) records
(R) records DPC

SPC
DPS
SPS

Energy Automation
If "electrical frequency" 50 Hz :
- The "integration time" value must be in the range [1..180000].
- If the "integration time" value is > 5, then no DPC, SPC, DPS, SPS recording is allowed.
36104 / WaveRecording / integration time is not in the range [1..180000]

36129 / WaveRecording / The relation type is not allowed
Examples :
36104 / WaveRecording / integration time is not in the range [1..180000]-> [180001]
36129 / WaveRecording / The relation type is not allowed-> [records : Bay DPC]
If "electrical frequency" 60 Hz :
- The "integration time" value must be in the range [1..216000].
- If the "integration time" value is > 6, then no DPC, SPC, DPS, SPS recording is allowed.
36104 / WaveRecording / integration time is not in the range [1..216000]

36129 / WaveRecording / The relation type is not allowed
Examples :
36129 / WaveRecording / The relation type is not allowed-> [records : Bay DPC]
A slow wave record is not compatible with a TMU210 board existing on the same computer
36202/ WaveRecording / Slow wave record is not compatible with a TMU210 board usage
2.2.5.4 Triggers of Wave Record
Any trigger datapoint of a given Wave record most have the same server than th computer managing
this wave record.
36223 / WaveRecording / The trigger datapoint has not the same server as its associated wave
record (servers)
2.2.6 Channels
Example of relations connecting Legacy Network / SCADA Network / Serial Printer / Datapoint to a
Channel :
C264 C264
BIU200
DNP3 master (Legacy Network) (R) has for main comm. port
RS232/485 port 1 (Comm. Channel)
(R) has for aux. comm. port RS232/485 port 2 (Comm. Channel)
(R) has for main comm. port

C26X SCADA prot (SCADA Network)
(R) has for aux. comm. port
(R) has for comm. port

Serial printer

Energy Automation
UCA2/IEC gateway UCA2/IEC gateway

Gateway channels
(R) has for main comm. port
Usual protocol (SCADA Network) Gateway chan. 1 ( Gateway Channel )
(R) has for aux. comm. port Gateway chan. 2 ( Gateway Channel )
Gateway chan. 3 ( Gateway Channel )
(R) has for main comm. Gateway chan. 4 ( Gateway Channel )
GI74 protocol (SCADA Network) port1 Gateway chan. 5 ( Gateway Channel )
(R) has for aux. comm. port1
Gateway chan. 6 ( Gateway Channel )
(R) has for main comm. port2 Gateway chan. 7 ( Gateway Channel )
(R) has for aux. comm. port2 Gateway chan. 8 ( Gateway Channel )
(R) has for main comm. port3
(R) has for main comm. port4
C264
(R) 'bit 00' wired on DIU200
MV DI#0 (Channel)
(R) 'bit 01' wired on DI#1 (Channel)
A Channel must be used only once.
11017 / RelationHasForCommPort / Multiple links to the same communication port

12018 / RelationHasForChannel / Multiple links to the same channel
Examples :
11017 / RelationHasForCommPort / Multiple links to the same communication port-> [is main
comm. port of : C26X SCADA prot]
12018 / RelationHasForChannel / Multiple links to the same channel-> ['bit 00' channel for : Bay
MV]
The SAS Protocol cant have an auxiliary communication port.
11252 / RelationHasForCommPort / Auxiliary communication port is not allowed for this protocol
(comm. port)
Attribute "plug com. number" of Gateway channels :
UCA2/IEC gateway UCA2/IEC gateway

(R) has for main comm. port Gateway channels (A) plug com. number
Usual protocol Gateway chan. 1 1
(R) has for aux. comm. port Gateway chan. 2
Gateway chan. 3
Gateway chan. 4
Gateway chan. 5
Gateway chan. 6
Gateway chan. 7
Gateway chan. 8
Under a Gateway, each channel used by a non-GI74 protocol, must have a unique value for its "plug
com. number" attribute.
31019 / GatewayCommPorts / The attribute value is not unique for the gateway

Energy Automation
Example :
31019 / GatewayCommPorts / The attribute value is not unique for the gateway-> [plug com.
number, 1]
Under a Gateway V5, a channel used by a non-GI74 protocol, cant use the "plug com. number" used
for redundancy. The Redundancy Mode of a gateway V5 can be DI/DO, COM1 or COM2.
31415 / GatewayCommPorts / This COM port is already used by gateway for redundancy
Attribute Baud rate of Gateway channels :

Under a Gateway, channel baud rates 100, 200, 38400 are available only for T101 protocol.
31104 / GatewayCommPorts / Baud rate is not in the range [300..19200]
Channel baud rates 100, 200 are also available for SAS protocol.
31104 / GatewayCommPorts / SAS baud rate is not in the range [100..19200]
2.2.7 Legacy Networks
Note : These checks are not processed for Legacy Networks of backup devices.
The general interrogation period of a T103 acquisition type should be equal to 0 or greater than 600 s
17276 / LegacyIED / The general interrogation period should be equal to 0 or greater than 600 s
Acknowledgment time out is insufficient for T101M in balanced mode

17343 / LegacyIED / Acknowledgment time out insufficient for T101M balanced (actual, min)
The port used by a T103 legacy network must have an even parity.
17277 / LegacyIED / Even parity is required for T103 usage on the port
A Gateway cant have more than 200 IED (all protocols combined)
89378 / Gateway / The maximun number of IED's under a gateway has been reached
A gateway legacy network with serial communication must have relation hasForMainCommPort
relation defined
17438 LegacyIED Scs | Ethernet network | C264 | Serial TunnelingThe relation has for
main comm port is missing on legacy network
2.2.7.1 IEDs on Legacy Networks

Energy Automation
C264
Legacy networks
DNP3 master (A) network address
DNP3_IED 0
DNP3_IED (A) network address
0
Modbus Mod.
(A) network address
MODB_IED 0
T103 (A) network address

T103_IED 0
T101 master
(A) network address
T101_IED 0
For each IED, per Legacy Network :

- its "network address" attribute value must be unique
- its "short name" attribute value must be unique
17035 / LegacyIED / The address of the IED is not unique on the Legacy Network
17036 / LegacyIED / The name of the IED is not unique on the Legacy Network
Examples :
17035 / LegacyIED / The address of the IED is not unique on the Legacy Network-> [network
address, 0]
17036 / LegacyIED / The name of the IED is not unique on the Legacy Network-> [short name,
DNP3_IED]
C264
Legacy networks
DNP3 master
DNP3_IED
DNP3 acq type
Modbus Mod.
MODB_IED
MODBUS acq type
T103
T103_IED
T103 acq type
T101 master
T101_IED
For each Device, and for all its Legacy Networks, the maximum count of "xxx acq type" components is
10.
02003 / CapacityLimits / The count of IED acquisition type components is not valid (count,
maximum)
Examples :
02003 / CapacityLimits / The count of IED acquisition type components is not valid (count,
maximum)-> [11, 10]
If an IED has an automatic disturbance set to YES, then the datapoint "IED DREC ready" must be
present.

Energy Automation
17344 / LegacyIED / The datapoint 'IED DREC ready' must be present if IED has automatic
disturbance
2.2.7.2 IED Mapping
2.2.7.2.1 Case of DNP3 IED
In the IED Mapping, the address identification of each "xxx addr. on IED" must be unique for a specific
type (TS, TC, TM, Counter or SetPoint).
The address identification is the value of the attribute "address" of the "xxx addr. on IED".
DNP3_IED
IED Mapping
IED DPC Mapping

DPC addr. on IED (A) address 0
IED DPS Mapping

(A) address
DPS addr. on IED 0
IED SPC Mapping

SPC addr. on IED (A) address 1
IED SPS Mapping

SPS addr. on IED (A) address 2
IED MPS Mapping

MPS addr. on IED (A) address 3
IED Counter Mapping (A) address

Counter addr. on IED 4
IED MV Mapping
MV addr. on IED (A) address 5
IED SetPt Mapping

SetPt addr. on IED (A) address 6
18037 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the Mapping
Examples :
18037 /xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the Mapping->
[type, address, 0]
Check for filled relation of DNP3_1GenIED under a gateway
93400 / Relation / This relation should not be filled
Check if the Contact type of a IEDDPCGenAddress or IEDDPSGenAddress is set to Unused
18401 / xxxAddressOnIED / Contact field should not be unused
Check if a IEDDPCGenAddress or IEDDPSGenAddress with open contact has no corresponding

closed address

Energy Automation
18402 / xxxAddressOnIED / This open address does not have a closed one
Check if a IEDDPCGenAddress or IEDDPSGenAddress with closed contact has no corresponding

open address
18403 / xxxAddressOnIED / This closed address does not have a open one
18421 / xxxAddressOnIED / Scs | Ethernet network | C264 | Modbus | MODB_IED | IED Mapping |
IED DPC Mapping | DPC addr. OPEN / The bit number of the IED is not unique in the mapping->
[function/bit number, 6/1]
2.2.7.2.2 Case of MODBUS IED
In the IED Mapping, the address identification of each "xxx addr. on IED" must be unique.
For each "xxx addr. on IED", the address identification is made of the following combinations of its
attribute values :
- { "mapping address" , "function" , "bit number" }
- { "mapping address" , "function" }
MODB_IED
IED Mapping
IED DPC Mapping (A) mapping address , (A) function , A: bit number
DPC addr. on IED 0,0,0
IED DPS Mapping (A) mapping address , (A) function , A: bit number
DPS addr. on IED 0,0,0
IED SPC Mapping

(A) mapping address , (A) function , A: bit number 0,0,1
SPC addr. on IED
IED SPS Mapping

SPS addr. on IED
IED MPS Mapping (A) mapping address , (A) function , A: bit number
MPS addr. on IED 0,1,1
IED Counter Mapping (A) mapping address , (A) function

Counter addr. on IED 0,0
IED MV Mapping (A) mapping address , (A) function

MV addr. on IED 0,0
IED SetPt Mapping (A) mapping address , (A) function

SetPt addr. on IED 0,1
06379 / AttributeValue / Event Table Number can't be set to 70 for a S20 SEPAM Type
06380 / AttributeValue / This IED Type is not supported by the relevant gateway
Examples :
06380 / AttributeValue / This IED Type is not supported by the relevant gateway-> [MICOM Px2x]

Energy Automation
06420 / AttributeValue / Event Table Number can't be set to {0} for {1} SEPAM Type
Examples :
06420 / AttributeValue / Event Table Number can't be set to 70 for S80 SEPAM Type
Examples :
18037 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the Mapping-
> [mapping address/fonction/bit number, 0/0/0]
> [mapping address/fonction, 0/0]
In the IED Mapping, the address bit number attribute must be lower than 16 ( 0..15) for
SPS/DPS/MPS/SPC/DPC MODBUS IED Address.
18232 / xxxAddressOnIED / 'Bit number' on IED MODBUS address must be lower than 16
18373 / xxxAddressOnIED / Invalid 'Data Format' on IED MODBUS address managed by a

gateway
These data formats are not supported by Gateway:

- 18 M230_T5_TYPE
- 19 M230_T6_TYPE
- 20 M230_T7_TYPE
- 21 ION_MODULUS_10000_unsigned
- 22 ION_MODULUS_10000_signed
- 23 KITZ202_K8
2.2.7.2.3 Case of ABB Flexgate MODBUS IED
In all of the IEDs Mappings of type ABB Flexgate, the address identification of each "xxx addr.
on IED" must be unique at Legacy MODBUS level.
attribute values :
- { "mapping address" , "function" , "bit number" }
- { "mapping address" , "function" }

Energy Automation
MODB_IED_1_ABB
IED Mapping
IED SPC Mapping

SPC addr. on IED
IED SPS Mapping

SPS addr. on IED


MV addr. on IED 0,0
IED SetPt Mapping

(A) mapping address , (A) function
MODB_IED_2_ABB
IED Mapping
IED SPC Mapping (A) mapping address , (A) function , A: bit number
SPC addr. on IED 1,0,1
IED SPS Mapping (A) mapping address , (A) function , A: bit number
SPS addr. on IED 1,0,1


MV addr. on IED 1,0
IED SetPt Mapping (A) mapping address , (A) function

18262 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the legacy
MODBUS for all ABB IED-> [mapping address/fonction/bit number, 57/1/1, Scs | Ethernet network |
C264 | Modbus Mod. (LB)]
2.2.7.2.4 Case of T103 IED

Energy Automation
attribute values :
- { "ASDU number" , "function type" , "information number" , "common address of ASDU" , "index in
the ASDU" }
- { "ASDU number" , "function type" , "information number" , "common address of ASDU" }
- { "ASDU number" , "function type" , "information number" }
T103_IED
IED Mapping
IED DPC Mapping (A) ASDU number , (A) function type, (A) information number
(A) ASDU number , (A) function type, (A) information number,
IED DPS Mapping (A) common address of ASDU
DPS addr. on IED 0,0,0,0
IED SPC Mapping

(A) ASDU number , (A) function type, (A) information number
SPC addr. on IED 0,0,0
IED SPS Mapping
(A) common address of ASDU
SPS addr. on IED
0,0,0,1
IED MPS Mapping (A) ASDU number , (A) function type, (A) information number
IED Counter Mapping

Counter addr. on IED
IED MV Mapping (A) common address of ASDU, (A) index in the ASDU
MV addr. on IED
0,1,1,0,0
IED SetPt Mapping (A) ASDU number , (A) function type, (A) information number
SetPt addr. on IED 0,1,1
Examples :
> [ASDU number/fonction type/information number, 0/0/0]
> [ASDU number/fonction type/information number/common address of ASDU, 0/0/0/1]
> [ASDU number/fonction type/information number/common address of ASDU/index in the ASDU,
0/1/1/0/0]
2.2.7.2.5 Case of T101 IED
attribute values :
- { "information object address" , "common address of ASDU" }
- { "information object address" }

Energy Automation
T101_IED
IED Mapping
IED DPC Mapping (A) information object address, (A) common address of ASDU
DPC addr. on IED 0,0
IED DPS Mapping

(A) information object address
DPS addr. on IED 0
IED SPC Mapping

(A) information object address, (A) common address of ASDU
SPC addr. on IED 0,1
IED SPS Mapping (A) information object address 0
SPS addr. on IED
IED MPS Mapping (A) information object address

MPS addr. on IED
IED Counter Mapping (A) information object address, (A) common address of ASDU
Counter addr. on IED
IED MV Mapping (A) information object address

MV addr. on IED
IED SetPt Mapping (A) information object address

SetPt addr. on IED
Examples :
> [information object address, 0]
> [information object address/common address of ASDU, 0/0]
2.2.7.2.6 Case of MICOM Px2x IED
18348 / xxxAddressOnIED / A Modbus IED with MICOM Px2x acquisition type must have a
network address between the min value authorized and the max value authorized [0, 247]
2.2.7.3 IED on Legacy T103 Network

For each T103 IED, if the MPS datapoint POC exists, the MPS PSE must also exist.
17167 / LegacyIED / The MPS datapoint PSE is missing
For each T103 IED, if MPS datapoints POC or PSE exists, and one of them is SBMC dependent, the
relation is relay of must exists on IED.
17186 / LegacyIED / The IED must have the relation Is Relay Of, because PSE and/or POC is
SBMC dependent
2.2.7.1 IED on Legacy MODBUS Network
Under a Legacy MODBUS a maximum of 15 ABB IED can be use. ABB flexgate manage 15 IED
maximum.

Energy Automation
02003 / CapacityLimits / The count of ABB IED components is not valid (count, maximum)-> [16,
15]
For any IED under a Modbus network, the associated IED acq type imposes its synchronisation
defined at network level.
17273 / LegacyIED / The IED requires a ALSTOM synchronisation (IED network, IED)
17274 / LegacyIED / The IED requires a SEPAM synchronisation (IED network, IED)
17275 / LegacyIED / The IED requires a FLEXGATE synchronisation (IED network, IED)
18345 / Gateway Legacy Networks / Modbus legacy / xxx addresse on IED /

The function of the 'xxx address on IED' is not valid
18349 / Gateway Legacy Networks / Modbus legacy / xxx addresse on IED /

The usage of "Unused" contact type for the address of double TS/double TC is not allowed in
Gateway
18426 / xxxAddressOnIED / Invalid 'Output Format' on IED DNP3 address managed by a gateway
TS :
SINGLE DI,
Function 1 & 2 :
MODBM_TS_BASIC_ADDRESS_OPEN address a single DI.
MODBM_TS_BIT_ADDRESS_OPEN = 255 (not used)
MODBM_TS_BASIC_ADDRESS_CLOSE = 65535 (not used)
MODBM_TS_BIT_ADDRESS_CLOSE = 255 (not used)
Function 3 & 4:
[MODBM_TS_BASIC_ADDRESS_OPEN, MODBM_TS_BIT_ADDRESS_OPEN] address a single DI
([word, bit])
[MODBM_TS_BASIC_ADDRESS_CLOSE, MODBM_TS_BIT_ADDRESS_CLOSE] =[65535, 255] not
used
DOUBLE DI,
Function 1 & 2:
o Open and Close configured
MODBM_TS_BASIC_ADDRESS_OPEN address the open contact.
MODBM_TS_BIT_ADDRESS_OPEN = 255 (not used)
MODBM_TS_BASIC_ADDRESS_CLOSE address the close contact. The value shall be
MODBM_TS_BASIC_ADDRESS_OPEN + 1
MODBM_TS_BIT_ADDRESS_CLOSE = 255 (not used)
o Unused configured(Only for C264)
Function 3 & 4:
o Open and Close configured
[MODBM_TS_BASIC_ADDRESS_OPEN, MODBM_TS_BIT_ADDRESS_OPEN] address the open
contact ([word, bit])
[MODBM_TS_BASIC_ADDRESS_CLOSE, MODBM_TS_BIT_ADDRESS_CLOSE] address the close
contact ([word, bit]). The value shall be
MODBM_TS_BASIC_ADDRESS_CLOSE = MODBM_TS_BASIC_ADDRESS_OPEN
MODBM_TS_BIT_ADDRESS_CLOSE = MODBM_TS_BIT_ADDRESS_OPEN + 1

Energy Automation
o Unused configured(Only for C264)
TC :
SINGLE DO,
Function 5 & 15 :
MODBM_TC_BASIC_ADDRESS_OPEN address a SINGLE DO.
MODBM_TC_BIT_ADDRESS_OPEN = 255 (not used)
MODBM_TC_BASIC_ADDRESS_CLOSE = 65535 (not used)
MODBM_TC_BIT_ADDRESS_CLOSE = 255 (not used)
Function 6 :
MODBM_TC_BASIC_ADDRESS_OPEN address a SINGLE DO.
MODBM_TC_BIT_ADDRESS_OPEN = address the Close contact bit number
NOTE: With function 6 its only possible to send a Close Order on SPC ( For a system needing both ON
and OFF order, its obliged to configured one SPC for ON and another SPC for OFF)
DOUBLE DO,
Function 5 & 15:

Open and Close configured
MODBM_TC_BASIC_ADDRESS_OPEN address the open contact.
MODBM_TC_BASIC_ADDRESS_CLOSE address the close contact.. The value shall be
MODBM_TC_BASIC_ADDRESS_OPEN + 1.
Unused configured(Only for C264)
Function 6 :
MODBM_TC_BASIC_ADDRESS_OPEN address the Open contact Register.
MODBM_TC_BIT_ADDRESS_OPEN = address the Open contact bit number
MODBM_TC_BASIC_ADDRESS_CLOSE = address the Close contact Register
MODBM_TC_BIT_ADDRESS_CLOSE = address the Close contact bit number
DO PROFIBUS specificity
Function 203
For PROFIBUS DO Function to be used is 203

(Function number 203 as been chosen arbitrarily in order not to be usable for MODBUS master)
ANALOG OUTPUT,
Function 6:

Energy Automation
MODBM_TC_BASIC_ADDRESS_OPEN address a ANALOG OUTPUT.

2.2.8 SCADA Networks
Note : These checks are not processed for SCADA Networks of backup devices.
2.2.8.1 SCADA Mapping
SCADA Mappings are defined for SCADA networks of Computer and Gateway physical devices.
Note : the following checks, except the check of feedback addresses, do not process GI74
protocol.
2.2.8.1.1 Address value, in SCADA Mapping of Computers and Gateways
C264 - T101
SCADA networks - DNP3
(A) protocol
C26X SCADA prot - T104
-MODBUS
Gtw SCADA Map. (A) SOE file address
255
Gtw Counter Map (A) object address
Gtw Counter addr 255
Gtw DPC Map
(A) object address
Gtw DPC addr. 255
Gtw DPS Map
(A) object address
Gtw DPS addr. 254
Gtw SPC Map
Gtw DPC addr. (A) object address 253
Gtw SPS Map
Gtw DPS addr. (A) object address 252
Gtw MV Map
Gtw MV addr. (A) object address
251
Gtw SetPt Map
Gtw SetPoint addr. (A) object address 250

Energy Automation
UCA2/IEC gateway - T101 - CDC II

SCADA networks - DNP3 - SAS
(A) protocol - T104
Usual protocol - OPC
- MODBUS
Gtw SCADA Map. (A) SOE file base address
255
Gtw Counter Map (A) object address
Gtw Counter addr 255
Gtw DPC Map
(A) object address
Gtw DPC addr. 255
Gtw DPS Map
(A) object address
Gtw DPS addr. 254
Gtw SPC Map
Gtw DPC addr. (A) object address
253
Gtw SPS Map
Gtw DPS addr. (A) object address
252
Gtw MV Map
(A) object address
Gtw MV addr. 251
Gtw SetPt Map
Gtw SetPoint addr. (A) object address
250
An address identification is the value of the attribute "object address" of a "Gtw xxx addr.", plus the
value of the attribute "SOE file address" defined on the protocol.
In a SCADA Mapping, the address identification of each "Gtw xxx addr." must be unique.
Particular case of a "Gtw DPS addr." in DNP3 protocol of computer :

Two addresses are used. Their values are given by :
- the attribute "object address" value
- the attribute "object address" value + 1 (reserved address).
Particular case of "Gtw DPS addr." in MODBUS protocol of computer :

If Double address usage value is Yes
Two addresses are used :
- open state address
- closed state address
Particular case of "Gtw DPS addr." and "Gtw DPS addr." in OPC protocol of computer :
If Double address usage value is Yes
Two addresses are used :
- open state address
- closed state address
This couple of address must be unique in SCADA mapping

19038 / xxxAddressOnSCADANetwork / The address of the 'Gtw xxx address' is not unique in the
Mapping
If Double address usage value is Yes attribute open state address and closed state address must
be different on each Gtw DPS addr
19247 / xxxAddressOnSCADANetwork / Attribute 'open state address' and 'Closed state address'
must be different for double addressing configuration
For CDCII SCADA addresses, the address structure depends on datapoint kind:
for SPS and DPS in static mode: CHN.SQN.OFF (concatenation of 3 attributes)
for SPS and DPS in event mode: CHN.PPU.EVT (concatenation of 3 attributes)
for MV and counter: CHN.SQN (concatenation of 2 attributes)

Energy Automation
for SPC, DPC and SetPoint: CHN.SQN (concatenation of 2 attributes)
Mapping
Examples :
Mapping-> [object address, 255]
Mapping-> [SOE file address, 255]
Particular cases of T101, T104 and DNP3 protocols (for Computers and Gateways) :
The unicity constraint is applicable only for addresses of the same type. Addresses of different
types can have identical addresses and therefore this does not lead to an error but to a warning.
Addresses for Disturbance uploading and Buffer Overflow (only for T101 and T104) to SCADA are
also taken into account in the unicity check.
The type for T101 and T104 is same as defined in SCE (SPS, DPS, SPC) and for DNP3, is
grouping simple and double (TS, TC, TM, Counter and SetPoint)
Mapping
For SCADA addresses of MPS POC or PSE, the address must be bitstring.
18169 / LegacyIED / The SCADA address format for PSE/POC must be bitstring
For CDCII SCADA addressing, SQN value attribute must respect following constraints:
for SPS and DPS: 0<= SQN <=63
for MV: 130<= SQN <=255
for Counter: 64<= SQN <=95
for SPC and DPC: 0<= SQN <=63
for SetPoint: 0<= SQN <=15
19189 / xxxAddressOnSCADANetwork /Bad value for SQN attribute of CDCII address (value, min
max)
For SAS protocol, the TC addresses are not allowed
19253 / xxxAddressOnSCADANetwork / For SAS protocol, the Command addresses are not
allowed
19061 / xxxAddressOnSCADANetwork / The SCADA address is not valid [Attribute name, Value,
Min authorised value, Max authorised value]
The SCADA address must be in the range of authorized values
Example :
19061 / xxxAddressOnSCADANetwork / The SCADA address is not valid [object address - register,
65536, 0, 65535]

Energy Automation
89366 / GTW / A MODBUS Legacy protocol cant be used in an IEC/IEC GTW
Its not possible to configure a MODBUS legacy protocol on an IEC/IEC GTW
89341 / GTW / Number of Legacy Networks is invalid (count, maximum)-> [x, 16]
Its not possible to configure more than 16 Legacy Networks for a Gateway.
89342 / GTW / Number of IED is invalid for T101 Master (count, maximum) -> [x, 1]
Its not possible to configure more than 1 IED on a T101 Master balanced for a Gateway.
2.2.8.1.2 Address structure, in SCADA Mapping of Computers and Gateways
C264 - T101
(A) protocol - DNP3 depending of
C26x SCADA prot
- T104
(A) address structure
Gtw SCADA Map.
- Address on 8 bits (1 byte)
Gtw xxx Map - Address on 16 bits (2 bytes)
Gtw xxx addr. - Address on 24 bits (3 bytes)
(A) object address
- Address on 8 bits.8 bits.8 bits
255.255.255
An "object address" value is formated according to the "address structure" value selected in the
protocol definition.
The set of possible "address structure" values depends on the protocol type.
Exception : for the DNP3 protocol type, the "address structure" is a fixed format : 16 bits in the range
[1..65535].
The "object address" value of a "Gtw xxx addr." must be compatible with the value selected for the
"address structure".
19039 / xxxAddressOnSCADANetwork / The address is incompatible with the address structure of

the protocol
Examples :
19039 / xxxAddressOnSCADANetwork / The address is incompatible with the address structure of
the protocol (Address on 8 bits.8 bits.8 bits)-> [object address, 255]
2.2.8.1.3 MV Address format on DNP3 protocol, of Computers and Gateways

Energy Automation
On a DNP3 protocol, a "Gtw MV addr.", which is the SCADA address of a "Tap pos ind" datapoint,
must have its "Format" attribute set to the "Natural" value.
C264
(A) protocol DNP3
C26x SCADA prot
Gtw SCADA Map.
Gtw MV Map
Gtw MV addr. (A) Format
Natural
Transformer (Bay)
(R) has for SCADA address transformer
Tap Changer
Tap pos ind (MV)
19123 / xxxAddressOnSCADANetwork / The attribute value is not compatible with the relation
Examples :
19123 / xxxAddressOnSCADANetwork / The attribute value is not compatible with the relation->
[Format = Ajusted, is SCADA address of : Tap pos ind]
2.2.8.1.4 SOE file attributes, in SCADA Mapping of Computers
These attributes are defined for a Computer SCADA protocol.
C264 (A) SOE file nb of events

C26x SCADA prot 100
(A) 'full' SOE file nb of events 75

"SOE file nb of events" > "'full' SOE file nb of events"
20103 / SCADA_Networks / 'full' SOE file nb of events is not lower than SOE file nb of events
Examples :
20103 / SCADA_Networks / 'full' SOE file nb of events is not lower than SOE file nb of events->
[175, 100]
2.2.8.1.5 T104 protocol attributes, of Computers and Gateways
(A) protocol T104
C264 (A) T1: APDU time-out

C26x SCADA prot (A) T2: acknowledgement time-out 15
10
(A) T3: test frame time-out
20
(A) K: sent unack. frames (APDU) 12
(A) W: ack. recieved frames (APDU) 8

"T2" < "T1"
"T3" > "T1"
"W" "K"

Energy Automation
20103 / SCADA_Networks / T2: acknowledgement time-out (s) is not lower than T1: APDU time-
out (s)
20103 / SCADA_Networks / T1: APDU time-out (s) is not lower than T3: test frame time-out (s)
20102 / SCADA_Networks / W: ack. received frames (APDU) is greater than K: sent unack.
frames (APDU)
Examples :
20103 / SCADA_Networks / T2: acknowledgement time-out (s) is not lower than T1: APDU time-
out (s)-> [20, 15]
20103 / SCADA_Networks / T1: APDU time-out (s) is not lower than T3: test frame time-out (s)->
[15, 14]
20102 / SCADA_Networks / W: ack. received frames (APDU) is greater than K: sent unack. frames
(APDU)-> [12, 11]
2.2.8.1.6 Feedback addresses on GI74 protocol, of Gateways
A "GI74 DPC addr." (or a "GI74 SPC addr.") must have 1, and only 1, link to a "GI74 DPS addr." or
"GI74 SPS addr." feedback address.
UCA2/IEC gateway
GI74 protocol
GI74 SCADA Map.
GI74 DPC Map

(R) has for feedback
GI74 DPC addr. 1
GI74 DPC addr. 2
GI74 DPS Map
GI74 DPS addr. 1
GI74 DPS addr. 2
GI74 SPS Map

GI74 SPS addr. 1
GI74 SPS addr. 2
GI74 SPC Map (R) has for feedback

GI74 SPC addr. 1
GI74 SPC addr. 2
14022 / RelationHasForFeedback / The link to feedback is missing

14023 / RelationHasForFeedback / Multiple links to feedbacks
Example :
14023 / RelationHasForFeedback / Multiple links to feedbacks-> [has for feedback : GI74 DPS
addr., has for feedback : GI74 SPS addr.]
2.2.8.1.7 Addressing of MPS on T101/T104 of Computers
MPS addressing in refused on T101/T104 SCADA network of computer.
19255 / xxxAddressOnSCADANetwork / MPS addressing refused on computer T101/104 SCADA

network

Energy Automation
2.2.8.2 Number of SCADA networks
On a computer, up to four SCADA networks can be created.
02206 / Capacity limits / The maximum number of SCADA and legacy protocols for a computer
has been reached (max number, count of protocols)
02206 / Capacity limits / This error replace the previous error 20206 / SCADA_Networks /

Energy Automation
2.2.8.3 Protocol type coherency with hardware prot type
Between protocol type and hardware port type, it must have a coherency:
Prot type (Hardware port) Protocol type (SCADA networks) Coherency

Usual protocol T101, T104, DNP3, MODBUS, OK
CDCType II
GI74 protocol GI74 OK
V35 ACKSYS-MCX T101 OK
20209 / SCADA_Networks / The coherency between this protocol type (protocol type) and this
gateway port (gateway port) is failed.
Hnz protocol should be configurable only in poste d or standalone mode but not in Pacis.
20395 / SCADA_Networks / Hnz protocol is not authorized in PACIS Mode (Only in Poste-d or
Standalone Mode)
2.2.8.4 Redundancy type of T101
On a computer, no active line on traffic can be used if unbalanced mode (Applicable T101).
20335 / SCADA_Networks / no active line on traffic can be used if unbalanced mode
2.2.8.5 Communication port of a SCADA Network
A SCADA network cant use a communication port of an extension rack.
C264
Extension rack
BIU24
1
Port 1
Port 2
Has For aux. comm. port
SCADA Network
Has For Main comm. port
20303 / SCADA_Networks / Scada Network can't use a communication port of an extension rack
.

Energy Automation
On a Scada Network, if we have a relation with a [DNP3, MODBUS or T104] which is based on
protocol other than Serial Port Communication, a check should appear to warn it.
31386 / SCADA_Networks/ IP Scada Network cant have relation with serial port
2.2.8.6 Presence of the Redundancy SPS under a SCADA Network
The Redundancy SPS must be present under a SCADA Network for all redundancy able protocols,
that is T101, T104 and IEC61850.
20337 / SCADA_Networks / The SPS "Redundancy SPS" must be present for the redundancy
able SCADA protocols (protocol)
For all others protocols, this SPS must not used.
20337 / SCADA_Networks / The SPS "Redundancy SPS" musn't be used if the SCADA protocol
does not support the redundancy (protocol)
.
2.2.8.7 Modbus protocol
For a Modbus SCADA protocol, no SP addresses and no MPS addresses are allowed under a SCADA
protocol.
20369 / SCADA Networks / no SP addresses are allowed under a Modbus SCADA protocol
20370 / SCADA Networks / no MPS addresses are allowed under a Modbus SCADA protocol
2.2.8.8 Datapoint transmission
For a system datapoint of backup not mapped on a DIAG/SYSTEM, the transmission on a SCADA (or
IEC/IEC protocol) is not allowed.
20148 / SCADA Networks / A datapoint not mapped on DIAG/SYSTEM can not be transmitted on
a SCADA
2.2.9 Taking Control function
Substation Ethernet network

Taking Control C264
(R) is taken control of
Taking Status C26X SCADA prot

Energy Automation

Taking Control UCA2/IEC gateway
Taking Status Usual protocol

Taking Control UCA2/IEC gateway
Taking Status GI74 protocol
(R) is taken control of GI74 port 2
If, at least, one SCADA network is linked to a Taking Control function, all the SCADA Networks
except IEC61850 of the system must be linked to a Taking Control function.
52131 / TakingControl / The relation link is missing-> [has for taken control]
If a "Taking Status" datapoint is linked to a SCADA Network, it must also be linked to a "Taking
Control" datapoint through the relation "has for feedback".
52131 / TakingControl / The relation link is missing-> [is feedback of]
A "Taking Control" datapoint must be linked to a "Taking Status" datapoint through the relation "has
for feedback".
52131 / TakingControl / The taken control SPC can have only one SCADA address
A "Taking Control" datapoint must have one and only one SCADA address
The "Taking Control" datapoint must have its "activation mode" attribute set to a "Permanent"
value.
The "Taking Status" datapoint must have its "detection mode" attribute set to the "Permanent"
value.
Substation
(A) activation mode - Permanent
Taking Control - Permanent until feedback
Taking Status (A) detection mode
- Permanent
52101 / TakingControl / The attribute value is not valid
Examples :

Energy Automation
52101 / TakingControl / The attribute value is not valid-> [activation mode, Transient]
52101 / TakingControl / The attribute value is not valid-> [detection mode, Transient]
Both "Taking Control" and "Taking Status" datapoints must be linked to a SCADA address in the
mapping of their SCADA network.
Substation
Ethernet network
Taking Control C264
Taking Status
C26X SCADA prot
GtwSCADAMap
(R) has for SCADA address
Gtw SPC Mapping
Gtw SPC addr.
Gtw SPS Mapping
Gtw SPS addr.
52133 / TakingControl / The datapoint is not linked to a SCADA address
Example :
52133 / TakingControl / The datapoint is not linked to a SCADA address of Scs | Ethernet network |
C264 | C26X SCADA prot
If the Taking Control function is defined in the system, the substation "Loc/rem ctrl DPC" datapoint
must be present and not wired.
Substation DO channel
(R) 'open' wired on
Loc/rem ctrl DPC
(R) 'closed' wired on DO channel
Taking Control
Taking Status
52089 / TakingControl / The datapoint is missing-> [Loc/rem ctrl DPC]

52100 / TakingControl / The datapoint is wired
52425 / TakingControl / Taking control mechanism is not allowed under a gateway which is
managing loc/rem substation
2.2.10 Non PACiS IED on IEC61850
2.2.10.1 Virtual input of IEC61850 IED
Any virtual input and its associated used datapoint can not have the same server, that is to say the
IEC61850 containing the virtual input.
82283 / IED virtual input / The virtual input and the associated used datapoint can not have the
same server

Energy Automation
2.2.10.2 Report by client limit
For each IED, check if theres enough report for all clients needs.
83284 / Indiced reports Not enough reports for all clients (Server path, Client path, List of
DataObject missing)
2.2.10.3 Dataset creation limit
For each IED, check if all needed datasets may be created (regarding capability of the IED).
83285 / Indiced reports / Number of DataSet to create for this IED is greater than the maximum
number allowed (Server path, max number of DataSet allowed, dataSet number to create)
2.2.10.4 Main and backup client dont share the same report preference
If main equipment has a backup, and if that backup doesnt have the same report preference (buffered
or unbuffered) than the main equipment. This can happen when there are no more reports available
for a given preference.
83316 / Indiced reports : The main equipment and his backup dont share the same report
preference (buffered or unbuffered) (Server path, Client path, List of DataObject missing)
2.2.10.5 No report available according to Equipment preference
A non PACiS equipment client can choice if he prefers a buffered or an unbuffered report. But if there
are no reports available to corresponding choice, the following check error are shown:
83317 / The Equipment has a preference for a buffered report, but no buffered reports are
available, so he obtained an unbuffered report
83318 / The Equipment has a preference for an unbuffered report, but no unbuffered reports are
available, so he obtained a buffered report
2.2.10.6 SCL compliancy
The SCL versions referred at IED level must be compliant. If not, the SCD will not be generated.
85305 / SCL / The SCL versions referred at IED level are un-compliant (the SCD will not be
generated)
If IID is missing for a non PACiS IED, raise error that the file is missing in DB.
83290 / SCL / Missing SCL model file for the IED
2.2.10.7 Obsolete CommonClass
For Non PACiS IED check the model file to look for obsolete CommonClass due to IEC61850 follow
up for PACiS System. To fix error run an IED Mapper Auto Association.

Energy Automation
87338 / IEC61850 IED / Obsolete CommonClass found into Model file. Please run IED Mapper
Auto Association to update mapping (Invalid CommonClass list)
2.2.11 IEC61850 Control Block Management
2.2.11.1 Report by client limit
For each PACIS IED, check if theres enough report for all clients needs.
83284 / Indiced reports Not enough reports for all clients (Server path, Client path, List of
DataObject missing)
2.2.11.2 Dataset creation limit
For each PACIS IED, check if all needed datasets may be created.
2.2.11.3 Dataset capacity
For each PACIS IED, check if the number of DataObject by DataSet isnt greater than the maximum.

Energy Automation
2.3 Electrical checks
2.3.1 Voltage Level and bay
A voltage level must contain at least one bay (BusBar, Generic Bay).
91371 / Voltage Level \ No bay defined under voltage level, generated SCD files will not be well
formed.
All topological nodes of a device must be defined on the same voltage level (except for a transformer).
The node 0 used for the ground can be used on several voltage levels.
91375 / Voltage Level / All nodes shall be defined on the same voltage level
2.3.2 Bay and Bay Mimic
2.3.2.1 Bay
A Bay managed by a Gateway must be a Generic Bay.
88349 / Bay / A bay managed by a gateway must be a generic bay (bay, bay type)
Example :
88349 / Bay / A bay managed by a gateway must be a generic bay (bay, bay type)-> [Site |
Substation | Voltage level | Bay, Feeder]
The contents of a Generic Bay managed by a Gateway isnt valid. The possible components under
this bay are :
- the datapoint order running,
- the generic datapoints of bay
- the generic module,
- the generic datapoints of generic module,
- the RT User Function,
- the datapoints of RT User Function.
88350 / Bay / The contents of the bay managed by a gateway isn't valid (bay, component not
authorized)
Example :
88350 / Bay / The contents of the bay managed by a gateway isn't valid (bay, component not
authorized)-> [Site | Substation | Voltage level | GenBayByGtw, Site | Substation | Voltage level |
GenBayByGtw | Day cyclic SPS]

Energy Automation
2.3.2.2 Bay Mimic
Graphic
(R) has for workspace C264 (1) (A) HMI type - Simple
Comp. workspace GHU200 - Complete
(R) represents - Old
Bay mimic (1) (R) is managed by
Feeder (1) C264 (2)
(R) represents
Bay mimic (2)
(R) is managed by
Feeder (2)
(A) graphical reference

[1..8], 65535
(A) graphical reference
[1..8], 65535
(A) mimic rank for the set of bay mimic

1
(A) mimic rank for the set of bay mimic 2
The computer ( "C264 (2)" ) managing a bay ( "Feeder (1)" ) represented by a "Bay mimic" must be
the same as the one linked to the "Comp. workspace" ( "C264 (1)" ) of this "Bay mimic".
33076 / BayMimic / The BayMimic and its Workspace are not linked to the same computer
Example :
33076 / BayMimic / The BayMimic and its Workspace are not linked to the same computer-> [Scs |
Ethernet network | C264, Scs | Ethernet network | C264]
A bay ( "Feeder (1)" ) can be represented by 0, 1 or 2 "Bay mimic". Each "represents" relation has
an attribute "mimic rank for the set of bay mimic". In the case of 2 relations, each attribute value
must be unique.
33106 / BayMimic / The relation attribute value is not unique (relation, attribute)
Example :
33106 / BayMimic / The relation attribute value is not unique (relation, attribute)-> [is represented
by : Bay mimic, mimic rank for the set of bay mimic, 1]
For a Computer, the maximum count of managed bays (relation "is managed by") which are linked
to a "Bay mimic" (relation "represents"), is 12.
This check is performed only if the Computer GHU200 board has its attribute "HMI type" set to the
"Complete" value.
33005 / BayMimic / The count of graphically displayed Bays is not valid (count, maximum)
Example (from the Computer point of vue) :

Energy Automation
33005 / BayMimic / The count of graphically displayed Bays is not valid (count, maximum)-> [13,
12]
2.3.3 Switchgear
Switchgear
Switch Ctrl SPC mutually exclusive
Switch Ctrl DPC
Switchgear pos. SPS mutually exclusive

Switchgear pos. DPS
The same type of datapoints which can be single or double (like " Switch Ctrl DPC" and "Switch Ctrl SPC")
are mutually exclusive
70066 / Switchgear / The datapoints are not compatible -> [Switch Ctrl SPC, Switch Ctrl DPC]
2.3.4 Circuit Breaker
2.3.4.1 Phases of Circuit Breaker
(A) circuit-breaker type

circuit breaker - Single phase CircuitBreaker
- Triple phase CircuitBreaker
Switch Ctrl DPC - Other CircuitBreaker
Switch Ctrl SPC
Switch phA DPC
1 Switch phB DPC
Switch phC DPC
Switch phA SPC
2 Switch phB SPC
Switch phC SPC
Switch PhA pos. DPS
3 Switch PhB pos. DPS
Switch PhC pos. DPS
Switch PhA pos. SPS
4 Switch PhB pos. SPS
Switch PhC pos. SPS
Switchgear pos. SPS
Switchgear pos. DPS
Ph not together SPS
Select SPS
The same type of datapoints which can be single or double (like " Switch Ctrl DPC" and "Switch Ctrl
SPC") are mutually exclusive.
40066 / CircuitBreaker / The datapoints are not compatible-> [Switch Ctrl DPC, Switch Ctrl SPC]
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.
- the Datapoints of the two sets (3) and (4) are mutually exclusive.

Energy Automation
- 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.
40093 / CircuitBreaker / The datapoints set is not complete for the phases A,B,C-> [Switch phA
DPC]
40092 / CircuitBreaker / The datapoint sets are incompatible-> [ (Switch phA DPC,Switch phB
DPC,Switch phC DPC) , (Switch phA SPC,Switch phB SPC,Switch PhC SPC) ]
40092 / CircuitBreaker / The datapoint sets are incompatible-> [ (Switch phA DPS,Switch phB
DPS,Switch phC DPS) , (Switch phA SPS,Switch phB SPS,Switch PhC SPS) ]
40089 / CircuitBreaker / The datapoint is missing-> [Ph not together]
41378 / CircuitBreaker / The AR Bay and the CB Bay can't be managed by 2 differents computers
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. This check is not
done for Switch PhA SPC, this datapoint is allowed for a "Triple phase CircuitBreaker".
40094 / CircuitBreaker / The datapoint is not allowed-> [Switch phA DPC]
If the circuit-breaker contains a Select SPC, this datapoint must be wired.

40099 / CircuitBreaker / The datapoint is not wired
2.3.4.2 Synchrocheck of Circuit Breaker
Substation
(R) is synchrocheck of
Ext manual CS
Feeder
Circuit breaker
Sync CB close SPC

Ext auto CS
Ext manual CS
Int synchrocheck
The Circuit Breaker must be linked only once to a Synchrocheck function (relation "is synchrocheck
of").
42098 / Synchrocheck / Multiple links to synchrochecks
Example :
42098 / Synchrocheck / Multiple links to synchrochecks-> [has for synchrocheck : Ext auto CS]

Energy Automation
If the Circuit Breaker is linked to a internal manual Synchrocheck function (relation "is
synchrocheck of"), then its "Sync CB close" SPC Datapoint is not allowed
42094 / Synchrocheck / The datapoint is not allowed-> [Site | Substation | Voltage level |
BAY_CBO | circuit breaker | Sync CB close]
If the Circuit Breaker is linked to a internal automatic Synchrocheck function (relation "is
synchrocheck of"), then its "Sync CB close" SPC Datapoint must not have a feedback xPS.
42049 / Synchrocheck / The relation is not valid-> [Site | Substation | Voltage level | BAY_CBO |
circuit breaker | Sync CB close | has for feedback : Switchgear pos.]
If the Circuit Breaker is linked to extrenal Synchrocheck or internal auto synchrocheck function
(relation "is synchrocheck of"), then its "Sync CB close" SPC Datapoint must be present.
In case of Internal Manual Synchrocheck this datapoint is optional.
42089 / Synchrocheck / The datapoint is missing-> [Sync CB close]
if a circuit-breaker has got a xPC "Sync CB Close" managed by a "CtrlPopup", then a datapoint
Switch Ctrl xPC must exist under the breaker and be managed by this "CtrlPopup".
42156 / Synchrocheck / The datapoint is missing (popup usage) -> [Switch Ctrl xPC]
47157 / Symbol / The ctrl popup must act on the following datapoint -> [Switch Ctrl xPC]
2.3.5 Automation
2.3.5.1 FBD automation
2.3.5.1.1 FBD consistency
A FBD id must be unique :
38359 / Automation / The FBD id is not unique-> [FBDx,FBDy]
In some degraded cases, an FBD may be inconsistent. Theres 3 possible result:

- the XML file doesnt exists
- the XML file is not correct
- the inputs/outputs or settings defined in XML file are not present in SCE database
38273 / Automation / The FBD's XML file doesn't exists -> [XML file]
38274 / Automation / The FBD's XML file is corrupt -> [XML file]
38275 / Automation / The FBD has inconsistent input, output or setting -> [XML file]
When such problem raise, the FBD is corrupted, and must be deleted.
For instance objects or template clones, the check is done on template source.

Energy Automation
38394 / Automation / By computer, the number of Binaries Inputs (SPS + DPS) used in FBD cant
be greater than 200
38395 / Automation / By computer, the number of MEASURES used in FBD cant be greater than
200
38396 / Automation / By computer, the number of MPS used in FBD cant be greater than 200
38397 / Automation / By computer, the number of SR LATCH used in FBD cant be greater than
200
38427 / Automation / Fbd diagram, Constant boolean input is not allowed in fbd diagram.Use fbd
bolean settings
42352 / Synchrocheck /
The command datapoint "Control Uniqueness" attribute value for the circuit breaker must be
equal to "Yes".
For the CB, "Control Uniqueness" attribute value for the father bay must be equal to "See
substation definition".
When the CB are managed by same Bay, the substation "Control uniqueness" attribute value
must be equal to "Bay level".
When the CB are managed by several Bay, the substation "Control uniqueness" attribute value
must be equal to "Substation level".
A TPI measure can not enter in a PSL.
57400 / MV / TPI can't be used by a FBD -> [SPI]
2.3.5.1.2 FBD status
(A) FBD status

FBD automation - Modified
- Correct
- Failure
The value of the attribute "FBD status" must be "Correct".
38101 / Automation / The attribute value is not valid
Example :
38101 / Automation / The attribute value is not valid-> [FBD status, Modified]

Energy Automation
The developed equation cant contain more than 256 datapoints.
38160 / Automation / The developed equation is to big (count, max)
A computer mustnt manage more than 256 FBD/interlocks
38288 / Automation / Too much FBD/Interlock for a computer (count, max)
FBD must not contain TON/TOFF standard block timer with a timer value lower than t#50ms or
t#20ms if the SCE parameter Dsce.FbdTimerMinForcedTo20msis used.
38252 / Automation / FBD contains at least one timer value lower than 20|50 milliseconds (value)
A computer must not manage more than 12 Accurate timers of FBD

38307 / Automation / Too much accurate timer of FBD for a computer (count, max)
FBD must not contain TON_A/TOFF_A accurate block timer with a timer value greater than t#50ms
38315 / Automation / FBD contains at least one accurate timer value greater than 50 milliseconds
(value)
2.3.5.1.3 Input/Output plugs
(R) uses DPS DPS

FBD automation (R) uses SPS SPS
(R) uses MPS MPS
FBD inputs (R) uses MV MV
FBD input (R) uses DPC DPC
(R) uses SPC SPC
FBD outputs (R) controls DPC DPC

FBD output (R) controls SPC SPC
(R) produces SPS SPS
For one "FBD input" plug, only one relation is allowed.
39088 / AutomationIOPlug / Multiple links to datapoints
Example :
39088 / AutomationIOPlug / Multiple links to datapoints-> [uses DPS : Bay DPS]
For one "FBD output" plug :

- the count of relations towards DPC or SPC Datapoints must be 4
- the count of relations towards SPS Datapoints must be 4
- a SPC/DPC datapoint can not be linked more than once to the same FBD output
39088 / AutomationIOPlug / Multiple links to datapoints
Example :
CHECKS SPECIFICATION Page:

100/182
Energy Automation
39088 / AutomationIOPlug / Multiple links to datapoints-> [controls DPC : Bay DPC]
FBD bloc MASK accepts only LSP datapoint on entry nMPS. (Error 39219)
FBD bloc MASK doesnt accept LSP datapoint on bit entry (0 to 15) (Error 39220)
Only LSP datapoint
No LSP datapoints
39219 / AutomationIOPlug / Fbd Mask nMPS entry must be direct-link with LSP (Uses data point)
Example:
39219 / AutomationIOPlug / Fbd Mask nMPS entry must be direct-link with LSP (Uses data point)->
[Site | Substation | Voltage level | Generic bay | Generic module | Module MPS]
39220 / AutomationIOPlug / Fbd Mask bit entry must not be link with LSP (Uses data point)
(Uses data point)
Example:
39220 / AutomationIOPlug / Fbd Mask bit entry must not be link with LSP (Uses data point)-> [Site |
Substation | Voltage level | Generic bay | Generic module | LSP]
Any Fbd Input/Output must be link with at least one data point
39226 / AutomationIOPlug / Fbd input/output must be link with one data point

101/182
Energy Automation
For FBD, two types of timer exists non accurate timer and accurate timer, this block allow one
setting timer as input (PT input). The Timer block non accurate allow only Setting timer as
input, and the accurate timer allow only Setting timer accurate as input.
Accurate Timer
block, only accurate
timer input
Non accurate Timer

block, only non
accurate timer input
39308 / AutomationIOPlug / Invalid setting timer used for timer block (setting path, allowed timer
setting, used timer setting)
Any input or output of FBD automatism that is not served by the computer managing the FBD,
must have goose usage attribute set to true at data object level of the associated datapoint.
22149 / DatapointClient / The client-server relation must be goosed for Automation/Mapping usage
at client level (server, client)
22150 / DatapointClient / The IEC/UCA2 relevant address must be goosed for
Automation/Mapping usage
Any Fbd Input/Output must be used in the diagram
39271 / AutomationIOPlug / The IOPlug must be used in FBD diagram
Datapoint use by interlock FBD must have an IEC address.
39410 / AutomationIOPlug / Datapoint use by interlock must have an IEC address.
2.3.5.1.4 Datapoint used by FBD at computer level
At computer level, a datapoint can not be used more than 255 times in the set of its PSLs.
38222 / Automation / The datapoint is used more tha 255 times in the PSLs of computer
[computer, nb tims >255]

102/182
Energy Automation
2.3.5.1.5 Settings Micom S1 used by FBD at computer level
By computer, the number of Boolean settings MicomS1 used in FBD cant be greater than 100.
38253 / Automation / The number of FBD boolean settings MicomS1 for this computer is too great
[computer, nb > 100]
By computer, the number of Timer settings MicomS1 used in FBD cant be greater than 100.
38254 / Automation / The number of FBD timer settings MicomS1 for this computer is too great
By computer, the number of settable FBD cant be greater than 50.
38269 / Automation / The number of settable FBD for this computer is too great [computer, nb >
50]
For each FBD operator the maximum number of boolean setting per operator basis (AND, OR )
is 1.
38293 / Automation / There are more than one boolean setting for the operator
For each timer and accurate timer, the default value must be between the minimum value and
maximum value.
38312 / Automation / The default value is not between minimum and maximum value
For each FBD function block (TON, TOFF, TON_A, TOFF_A and RS) it is not allowed to have a
boolean setting.
38314 / Automation / The function block can not have a boolean setting as input
For each FBD output slot it is not allowed to have a boolean setting.
38342 / Automation / The output slot can not have a boolean setting as input
2.3.5.2 Slow automation
2.3.5.2.1 Modified flag
(A) modified
Slow automation - Yes
- No
The value of the attribute "modified" must be "No".
38101 / Automation / The attribute value is not valid
Example :
38101 / Automation / The attribute value is not valid-> [modified, Yes]

103/182
Energy Automation
2.3.5.2.2 Input/Output
Any input or output of slow automation that is not served by the computer managing the
automation, must have goose usage attribute set to true at data object level of the
associated datapoint.
2.3.5.2.3 Settings Micom S1 used by UserFunctions (Slow Automation) at computer level
By computer, the number of settings MicomS1 (Boolean, Integer, Float) used in Isagraf cant be
greater than 100.
38341 / Automation / The number of Isagraf settings MicomS1 for this computer is too great
By computer, the number of settable Isagraf function cant be greater than 50.
38268 / Automation / The number of settable Isagraf function for this computer is too great
[computer, nb > 50]
2.3.5.2.4 Dictionnary coherency
For each input/output of isagraf an attributes IO reference and IO prefix is definded.
- For each I/O the concatenation of these two attributes must exist and must be unique in isagraf
dictionnary
38327 / Automation / Missing I/O definition in dictionary (I/O reference, I/O prefix)
38328 / Automation / Double I/O definition in dictionary (I/O reference, I/O prefix)
- For each I/O the the attribute /IO reference must exist and must be unique in isagraf dictionary.
38329 / Automation / Missing I/O reference in dictionary (I/O reference)

38330 / Automation / Double I/O reference in dictionary (I/O reference)
2.3.5.2.5 Isagraf files existence
For each Isagraf object check verifies that the database files of the Isagraf exists.
38331 / Automation / Missing Isagraf file in configuration database.
2.3.5.2.6 Isagraf version

104/182
Energy Automation
For each Isagraf object check verifies that the project is in the good version.
38343 / Automation / The Isagraf project needs to be upgraded (current version, target version).
2.3.5.2.7 Real Time UserFunctions
A RTUsrFct must belong to a bay managed by a Gateway device.
38339 / Automation / The bay containing a RTUsrFct must be managed by a Gateway device ->
[Bay, Device].
For all RTUsrFcts of a same resource number, one and only one must be Master Resource.
38340 / Automation / One and only one RTUsrFct Master Resource by resource number ->
[Resource Number, Number of Master Resource].
A redunded gateway can not manage more than 2 Isagraf resources
38440 / Automation / A redunded gateway can not manage more than 2 isagraf resources.
Isagraf resources number must be consecutives and start at 1.
38439 / Automation / Isagraf resources numbers must be consecutives and start at 1.
2.3.6 Tap Changer
2.3.6.1 Position indicator
Transformer 0
transformer (A) Value features / minimum value
Tap changer (A) Value features / maxmum value
Tap pos ind 0
The following constraint between the two attributes must be respected :

("maximum value" "minimum value" 1) [2..64]
37087 / TapChanger / The result of Value features/maximum value - Value features/minimum

value + 1 is not in [2..64]
The values min and max of the transformer (attributes MinUsablePosition and
MaxUsablePosition) must be included between the MV tap position indicator values.
37363 / TapChanger / Site | Substation | Voltage level | Transformer 1 | transformer | Tap changer |
Tap pos ind / Min and max value of transformer don't belong to the interval minimum value -
maximum value of the TPI (MinUsablePosition < MinScaledValue and/or MaxUsablePosition >
MaxScaledValue)

105/182
Energy Automation
37388 / TapChanger / / Site | Substation | Voltage level | Transformer 1 | transformer | Tap changer
| Tap pos ind / A threshold can not be configured for a Tap Position Indicator
37400 /TapChanger / Site | Substation | Voltage level | Transformer 1 | transformer | Raise/Lower

DPC / The has for feed back relation from Raise/Lower DPC must be removed.
Moreover for analog TPI the following constraints must be respected:
current valid range (% maximum value) > (2 / (maximum acq. value - minimum acq. value))
37212 / TapChanger / The constraint is not valid:[current valid range (% maximum value) > (2 /
(maximum acq. value - minimum acq. value))]
current valid range (% maximum value) < (100 / (maximum value - minimum value))
37212 / TapChanger / The constraint is not valid:[current valid range (% maximum value) < (100 /
(maximum value - minimum value))]
2.3.6.2 RaiseLower / GotoMinMax coherence
Transformer
transformer
Tap changer (R) has for profile (A) SBOMode
Raise/lower DPC ?
DPC profile
Goto min/max DPC
On Tap changer, if the Raise/lower DPC is SBO Many, forbid the Goto min/max DPC
37178 / TapChanger / When Raise/lower DPC is SBO Many, Goto min/max DPC is not allowed
2.3.6.3 RaiseLower / TAP Selection coherence
On Tap changer, if the Raise/lower DPC is Direct Execute, forbid the TAP Selection DPC.
37332 / TapChanger / When raise lower DPC is configured with Direct Execute, it's not allowed to
have a TAP Selection.
2.3.7 AutoRecloser function

106/182
Energy Automation
- Not used
- 1P
- 1P-3P
- 1P-3P-3P
(A) functioning mode (1 ph trip) - 1P-3P-3P-3P
Feeder (A) functioning mode (3 ph trip)
Autorecloser - Not used
- 3P
- 3P-3P
- 3P-3P-3P
- 3P-3P-3P-3P
(A) 1st period monophased 500

(A) 1st period triphased 500
(A) 2nd period triphased 5000
(A) 3rd period triphased 5000
(A) 4th period triphased 5000
The two attributes "functioning mode (1 ph trip)" and "functioning mode (3 ph trip)" must not be both
set to "Not used" value.
41096 / Autorecloser / The attribute values are not compatible-> [functioning mode (1 ph trip) =
Not used, functioning mode (3 ph trip) = Not used]
If "functioning mode (1 ph trip)" value is set to "1P-3P-3P-3P", then the following rules must be
respected :
- "1st period monophased" < "2nd period triphased"
- "1st period monophased" < "3rd period triphased"
- "1st period monophased " < "4th period triphased"
If "functioning mode (1 ph trip)" value is set to "1P-3P-3P", then the following rules must be
respected :
- "1st period monophased" < "3rd period triphased"
If "functioning mode (1 ph trip)" value is set to "1P-3P", then the following rule must be respected :
41103 / Autorecloser / 1st period monophased (ms) is not lower than 2nd period triphased (ms)
41103 / Autorecloser / 1st period monophased (ms) is not lower than 3rd period triphased (ms)
41103 / Autorecloser / 1st period monophased (ms) is not lower than 4th period triphased (ms)
If "functioning mode (3 ph trip)" value is set to "3P-3P-3P-3P", then the following rules must be
respected :
- "1st period triphased" < "2nd period triphased"
- "1st period triphased" < "3rd period triphased"
- "1st period triphased" < "4th period triphased"
If "functioning mode (3 ph trip)" value is set to "3P-3P-3P", then the following rules must be
respected :
- "1st period triphased" < "3rd period triphased"
If "functioning mode (3 ph trip)" value is set to "3P-3P", then the following rule must be respected :

107/182
Energy Automation
41103 / Autorecloser / 1st period triphased (ms) is not lower than 2nd period triphased (ms)
41103 / Autorecloser / 1st period triphased (ms) is not lower than 3rd period triphased (ms)
41103 / Autorecloser / 1st period triphased (ms) is not lower than 4th period triphased (ms)
- Not used
- 1P
- 1P-3P
- 1P-3P-3P
Feeder (A) functioning mode (3 ph trip)
Trip PhA - 3P
Trip PhB - 3P-3P
Trip PhC (A) unlocking way
- 3P-3P-3P
- 3P-3P-3P-3P
on/off ctrl DPC
on/off ctrl DPS
lock/reinit SPC - Not used

lock/reinit SPS - Reinitialization
- Manual close
- Both ways
If "functioning mode (1 ph trip)" value is different from "Not used", then at least one of the three
SPS datapoints { "Trip PhA", "Trip PhB", "Trip PhC" } is mandatory.
41090 / Autorecloser / One of the datapoints is missing-> [Trip PhA, Trip PhB, Trip PhC]
If "functioning mode (1 ph trip)" value is set to "Not used", then none of the three SPS datapoints
{ "Trip PhA", "Trip PhB", "Trip PhC" } is allowed.
41097 / Autorecloser / The attribute value is incompatible with the datapoints-> [functioning mode
(1 ph trip) = Not used, Trip PhA, Trip PhB, Trip PhC]
The two datapoints { "on/off ctrl DPC", "on/off ctrl DPS" } are mutually exclusive and, at least one of
them is mandatory.
41066 / Autorecloser / The datapoints are not compatible-> [on/off ctrl DPC, on/off ctrl DPS]
41090 / Autorecloser / One of the datapoints is missing-> [on/off ctrl DPC, on/off ctrl DPS]
The two datapoints { "lock/reinit SPC", "lock/reinit SPS" } are mutually exclusive. If the "unlocking
way" attribute value is set to "Reinitialization" or "Both ways" then, at least one of the two datapoins
is mandatory.
41066 / Autorecloser / The datapoints are not compatible-> [lock/reinit SPC, lock/reinit SPS]
41090 / Autorecloser / One of the datapoints is missing-> [lock/reinit SPC, lock/reinit SPS]

108/182
Energy Automation
- Not used
- 1P
- 1P-3P
- 1P-3P-3P
Feeder
(R) is autorecloser of (A) functioning mode (3 ph trip)
- 3P
Circuit breaker - 3P-3P
- 3P-3P-3P
(A) circuit-breaker type - 3P-3P-3P-3P
- Single phase CircuitBreaker

- Triple phase CircuitBreaker
- Other CircuitBreaker
If "functioning mode (1 ph trip)" value is different from "Not used", then the "circuit-breaker type"
must be set to "Single phase CircuitBreaker".
41096 / Autorecloser / The attribute values are not compatible-> [functioning mode (1 ph trip) = 1P,
Site | Substation | Voltage level | Feeder | circuit breaker | circuit-breaker type = Triple phase
CircuitBreaker]
If "functioning mode (3 ph trip)" value is set to "Not used", then the "circuit-breaker type" must be
set to "Single phase CircuitBreaker".
41096 / Autorecloser / The attribute values are not compatible-> [functioning mode (3 ph trip) =
Not used, Site | Substation | Voltage level | Feeder | circuit breaker | circuit-breaker type = Triple
phase CircuitBreaker]
2.3.8 Synchrocheck function

109/182
Energy Automation
Substation
Ext manual CS
on/off ctrl DPC
mutually exclusive + wired
on/off ctrl SPC
on/off DPS
on/off SPS mutually exclusive
Feeder
Ext auto CS
on/off ctrl DPC
on/off ctrl SPC mutually exclusive
on/off DPS
Ext manual CS
on/off ctrl DPC mutually exclusive + wired
on/off ctrl SPC
on/off DPS
Int auto CS
on/off ctrl DPC forbidden
on/off ctrl SPC
on/off SPS
Int manual CS
on/off ctrl DPC mutually exclusive
on/off ctrl SPC
on/off SPS
As shown in the picture, under a Synchrocheck function, some Datapoints are mutually exclusive
and some must be wired.
Note :
Here, the term "wired" means that the datapoint must be linked to a digital/analog channel of a
computer, or linked to an IED address.
42066 / Synchrocheck / The datapoints are not compatible-> [on/off ctrl DPC, on/off ctrl SPC]
42066 / Synchrocheck / The datapoints are not compatible-> [on/off SPS, on/off DPS]
42099 / Synchrocheck / The datapoint is not wired
For a "Int manual synchrocheck" function, the "on/off ctrl DPC" or "on/off ctrl SPC" Datapoint must
be present.
42090 / Synchrocheck / One of the datapoints is missing-> [on/off ctrl DPC, on/off ctrl SPC]
For a "Int automatic synchrocheck" function, the "on/off ctrl DPC" or "on/off ctrl SPC" Datapoint are
not allowed.
42094 / Synchrocheck / The datapoint is not allowed-> [on/off ctrl xPC]
Only one internal synchrocheck can be configured on a per computer basis.
42151 / Synchrocheck / More than one internal synchrocheck on the same computer

110/182
Energy Automation
For an internal synchrocheck, all associated circuit-breakers must be managed by the same
computer than the synchrocheck.
42152 / Synchrocheck / The internal synchrocheck and the breaker have not the same manager
For an internal synchrocheck, if set as type 1, the computer managing the synchrocheck must
have a TMU200 or TMU220 Board.
42159 / Synchrocheck / The manager of the internal synchrocheck have not a TMU200 TMU220
Board
For an internal synchrocheck, if set as type 1 and the datapoint CS_BusBarVChoice_SPS exists
under the synchrocheck, the associated TMU board must be a TMU220
42204 / Synchrocheck / The TMU220 board is missing for datapoint usage in reference
For an internal synchrocheck, if set as type 2, the associated TMU board must be a TMU210
42264 / Synchrocheck / The TMU210 board is missing for synchrocheck of type 2
For an internal synchrocheck, if set as type 2, the datapoint CS_BusBarVChoice_SPS mustnt

exists
42265 / Synchrocheck / The BusBar V Choice datapoint is not allowed for synchrocheck of type 2
For an internal synchrocheck, if set as type 2, all this datapoints must exists :
o Bypass
o Scheme Coupling
o Scheme Locking
o Scheme LD/BD
o Scheme LD/BL
o Scheme LL/BD
42276 / Synchrocheck / The datapoint is missing-> [Bypass]
For an internal synchrocheck, if set as type 1, all this datapoints must not exists :
o Bypass
o Scheme Coupling
o Scheme Locking
o Scheme LD/BD
o Scheme LD/BL
o Scheme LL/BD
42277 / Synchrocheck / The datapoint is not allowed-> [Bypass]
If the datapoint SynchroVChoice is configured under internal synchrocheck, than the datapoint
busbarVChoice must also be configured, and the computer managing parent bay must have a
TMU220.

111/182
Energy Automation
73441 / Datapoint / The Synchro V Choice datapoint can be configured only if the datapoint
busbar V choice is present and a TMU220 is configured on C264
When the datapoint SynchroVChoice is configured, then the attribute reference phase side of C264
TMU220 managing parent bay must be set to line side.
73442 / Datapoint / The phase ref side attribute on TMU220 must be set to line side when
datapoint Synchro V choice is configured under synchro check
2.3.9 ATCC function
Substation
ATCC
(A) ATCC existence - Yes
Voltage level (1) - No
Transformer
transformer
ATCC fct needs
Tap changer (R) has its primary on

Raise/lower DPC or
(R) has its secondary on
MCB position DPS
MCB position SPS
BusBar
ATCC fct needs
Voltage level (2)
If there is no ATCC under the Substation, then :

- a "Voltage level" must not have its "ATCC existence" attribute set to "Yes".
- the "ATCC fct needs" is allowed neither under a "transformer" nor under a "BusBar".
26101 / ATCC / The attribute value is not valid-> [ATCC existence, Yes]
26109 / ATCC / The component is not allowed-> [ATCC fct needs]
If there is an "ATCC fct needs" under a "transformer", then :

- the "Tap changer" with its "Raise/lower DPC" Datapoint are mandatory.
- one of the two Datapoints { "MCB position DPS", "MCB position SPS" } is mandatory. They
are mutually exclusive.
- the "transformer" must be linked to a Voltage level through one and only one of the relations
{ "has its primary on", "has its secondary on" }. The Voltage level must be different from the
one under which the transformer is located.
26110 / ATCC / The component is missing-> [Tap changer]

26089 / ATCC / The datapoint is missing-> [Raise/lower DPC]
26090 / ATCC / One of the datapoints is missing-> [MCB position DPS, MCB position SPS]
26066 / ATCC / The datapoints are not compatible-> [MCB position DPS, MCB position SPS]

112/182
Energy Automation
26111 / ATCC / The link to primary or secondary voltage level is missing

26044 / ATCC / The relation types are not compatible-> [has its primary on, has its secondary on]
26050 / ATCC / The relation link is not valid-> [has its primary on : Voltage level]
If an ATCC is defined, then all Switchgears and Circuit Breakers must have a Switchgear Position
datapoint.
26090 / ATCC / One of the datapoints is missing -> [Switchgear position]

If an ATCC is defined, then the voltage MV of transformer or BusBar ATCC functions cant be wired
both :
- If voltage MV of transformers are wired (in board or on IED), voltage MV of BusBars must be
computed.
- If voltage MV of BusBars are wired (in board or on IED), voltage MV of transformers must be
computed.
26176 / ATCC / The voltage MV wiring of an ATCC function is not compliant full ATCC description
2.3.10 Protection module
The following checks concerns protection functions embedded in computer. They required the
presence of the TMU210 board for the computer.
As soon as one or several bays managed by a computer, have got a integrated protection
function, this computer must contain a TMU210 board.
<09153>/ Calculator boards / The TMU210 board is missing for protection function usage
For the set of bays managed by a computer, each kind of protection function can be present only
once.
<55154> / Module protection / Kind of protection module is defined more than once
.
For the set of bays managed by a computer:
as soon as one of them uses a protection function, the relay automatism function must be
present.
if a 81U exists, a 81O must also exist
if a 81O exists, a 81U must also exist
if a 81R exists, both 81U and 81R must exist
the 81U and 81O must have the same values for the attributes trip contact #i (i=1,2,3) usage
<55155> / Module protection / relay automatism function is missing.

<55156> / Module protection / 81O function is missing.
<55157> / Module protection / 81U function is missing.
<55158> / Module protection / 81Oor 81U function is missing
<55329> / Module protection / 81Oand 81U function must have same trip usage values

113/182
Energy Automation
2.3.10.1 EPATR function
When a TMU210 is configured with attribute EPATR tore type set to a value different from not
used, the EPATR function is active for this board. Subsequently, the following checks are
implemented:
For the set of bays managed by the relevant computer, the protection function 67N is required.
<71215> / EPATR / the protection function 67N is missing for EPATR usage
The following datapoints are required under the 67N protection function:
15A_over_current, 1_2_s_over_current, EPATR_RSE_Mode, EPATR_DSP_RSE_Mode
<71216> / EPATR / the datapoint is missing for EPATR usage: <required datapoint short name>
2.3.11 Electre function ARS
The following checks concerns Electre function ARS embedded in computer. The following constraints
must be respected:
t_ars_tb1 < t_ars_tb2 < t_ars_trecup

<65208>/ Electre function ARS / constraint not valid: Tempo blocage B1 disj. (s) < Tempo
blocage B2 disj. (s) < Tempo. rcup. disj. (s)
t_ars_trtl1 + t_ars_ticrt < t_ars_tdrt

Tempo cycle triphas lent 1 (s) + Tempo
<65208>/ Electre function ARS / constraint not valid:
inversion des consignes (s) < Tempo dsarm cycle triphas lent (s)
d_ars_lentrl < t_ars_trtl1

<65208>/ Electre function ARS / constraint not valid: Dure valide renvoi ligne pour cycle
triphas lent (s) < Tempo cycle triphas lent 1 (s)
d_ars_lentrl < t_ars_ticrt

Dure valide renvoi ligne pour cycle
<65208>/ Electre function ARS / constraint not valid:
triphas lent (s) < Tempo inversion des consignes (s)
d_ars_lentrb < t_ars_trtl1

<65208>/ Electre function ARS / constraint not valid: Dure valide renvoi barre pour cycle
triphas lent (s) < Tempo cycle triphas lent 1 (s)
d_ars_lentrb < t_ars_ticrt

<65208>/ Electre function ARS / constraint not valid: Dure valide renvoi barre pour cycle
triphas lent (s) < Tempo inversion des consignes (s)

114/182
Energy Automation
2.3.12 Electre function PSL
The following checks concerns Electre function PSL embedded in computer.

Under a PSL function, one and only one of the two following sets of datapoint must exist (these sets
are exclusive each other):
Intersaison configuration: Signalisations which must be present
- ElecPSL_saison2bis, ElecPSL_tcsaison2Bis
OR
- ElecPSL_saison2, ElecPSL_tcsaison2, ElecPSL_saison3, ElecPSL_tcsaison3
Hiver configuration: Signalisations which must be present
- ElecPSL_saison4bis, ElecPSL_tcsaison4Bis
OR
- ElecPSL_saison4, ElecPSL_tcsaison4, ElecPSL_saison5, ElecPSL_tcsaison5
<66210>/ Electre PSL Fct / Bad configuration for intersaison signalisations

<66211>/ Electre PSL Fct / Bad configuration for hiver signalisations
2.3.13 Electre function PDA
The following checks concerns Electre function PDA embedded in computer.

Under a PDA function, one and only one of the two following sets of datapoint must exist (these sets
are exclusive each other):
Intersaison configuration: Signalisations which must be present
- ElecPDA_saison2bis, ElecPDA_tcsaison2Bis
OR
- ElecPDA_saison2, ElecPDA_tcsaison2, ElecPDA_saison3, ElecPDA_tcsaison3
Hiver configuration: Signalisations which must be present
- ElecPDA_saison4bis, ElecPDA_tcsaison4Bis
OR
- ElecPDA_saison4, ElecPDA_tcsaison4, ElecPDA_saison5, ElecPDA_tcsaison5
<67210>/ Electre PDA Fct / Bad configuration for intersaison signalisations

<67211>/ Electre PDA Fct / Bad configuration for hiver signalisations
2.3.14 Topology
The following checks concerns the electrical topology, i.e. nodes values existing at electrical module
level. They are run when an ATCC function or a Fast Load Shedding function is configured. In the
folloqing, used node means node whose value is different from 65535
The used nodes of a module can not have the same value.

115/182
Energy Automation
<74239> / Topology / the nodes of a module can not have the same value
Two modules can not have the same set of used nodes.
<74240> / Topology / two modules can not have the same node values
For a transformer, its adjacent non-generic modules located in the same Transformer bay should
have at least 2 used nodes.
<74241> / Topology / node values are missing for modules (at least 2 values are required)
For a transformer defining topology nodes, a relation HasPrimaryOn or HasSecondaryOn must be

defined.
<74432> / Topology / Relation "has its primary on" or "has its secondary on" must be set on
transformer with node references
2.3.15 Fast load shedding
If LSP datapoints exist in configuration data base the relation has for main FLS server is mandatory
at site level
<75244> / Fast load shedding / Site / Relation 'Has for main FLS server' mandatory to
manage LSP datapoints
2.3.16 Load shedding/ Load Curtailement
A computer can manage only one load shedding function and/or only one load curtailment function.
Load function are configured at bay level.
79278 / Load function / RTU | Computer | C264_LS / Invalid number of load curtailment
managed by the computer, only one load curtailment function must be configured per
computer (load curtailment functions)->
[Site | Substation | Electrical Bay | Generic bay | Load function 1,
Site | Substation | Electrical Bay | Generic bay 1 | Load function,
Site | Substation | Electrical Bay | Generic bay 1 | Load function 1]
Load Function : A load function needs at least one group
79279 / Load function / Site | Substation | Voltage level | Generic bay | Load function / The Load
Function needs at least one group
2.3.17 It function
When It function is configured, the 67 relay function must exist.
81280 / It function / Site | Substation | Voltage level | Generic bay | It function / The protection
module '67' is missing for the computer, mandatory for It function.
TMU210 board must exist at computer level if It function is configured.
09153 / ComputerBoards / Scs | Ethernet network | C264 / The TMU210 board is missing for
protection module usage at computer level.

116/182
Energy Automation
TMU210 board must compute the MV bellows if It function is configured.
IT_phase_A
IT_phase_B
IT_phase_C
IT_total
I2T_phase_A
I2T_phase_B
I2T_phase_C
I2T_total
81281 / It function / Site | Substation | Voltage level | Generic bay | It function / Missing
mandatory computed MV for It function (Computed MV)-> [IT: IT_phase_A]
Only one It function can be configure per computer.
55154 / Protection module / Site | Substation | Voltage level | Generic bay 1 | It function
The protection module still exists for the computer-> [Scs | Ethernet network | C264].
2.3.18 AVR Function
The two Days chosen for week end days on AVR Period Type 2 and Type 3 must be
consecutive days.
AVR Fct
AVR Period type 2 Saturday
AVR Period type 3 Monday X Check error must be Sunday
84295 / AVR / Site | Substation | Voltage level | AVR | AVR / Week end days configured on
AVR period type 2 and type 3 must be two consecutive days (fisrt day, second day).
Computer can manages one and only one AVR function

117/182
Energy Automation
Bay 1
Manages
AVR
Manages
Bay 2 C264
AVR
84298 / AVR / Scs | Ethernet Network | C264 / Invalid count of AVR managed by the same
computer (count,max,managed AVR functions)
In same configuration database AVR must be configured with same mode : Stand Alone XOR
Master Follower in parallel XOR MCC
84299 / AVR / Substation / AVR functions with different working mode is not compatible
Maximum of four AVR function configured in Master Follower in parallel or MCC
84300 / AVR / Substation / Invalid count of AVR function for Master follower in parallel mode or
MCC mode (count, max)
For AVR function configured in Master Follower in parallel or MCC mode, one and only AVR
with role Master must be configured an a maximum of 3 Follower can be configured.
84301 / AVR / Substation / Invalid count of AVR master (count of master, min of master, max of
master)
84302 / AVR / Substation / Invalid count of AVR slave (count of slave, min of slave, max of slave)

118/182
Energy Automation
Bay 1
AVR Role = Master Only one Master AVR
Bay 2
AVR Role = Follower
Bay 3
AVR Role = Follower Maximum of 3 AVR followers
Bay 4
AVR Role = Follower
84096 / AVR / Site | Substation | Voltage level | AVR | AVR / Tranfo in // / Transformer in parallel
When the AVR RPF used attribute is true then AVR Transformer in parallel attribute
must be false
84096 / AVR / Site | Substation | Voltage level | AVR | AVR / Voltage / Double wound
When the AVR RPF used attribute is true then AVR Double wound attribute must be
false
For AVR function configured in Master Follower in parallel mode, maximum one AVR with role
Follower Master backup can be configured.
84362 / AVR / Site | Substation / Invalid count of AVR backup (count of backup, min of backup,
max of backup)
For AVR function configured in Master Follower in parallel or MCC mode, the values of the
AVR (attributes Highest Tap Value and Lowest Tap Value) must belong to the transformers
values (attributes minimal usable position and maximal usable position)
84364 / AVR / Site | Substation | Voltage level | Transformer | AVR / Values of the AVR don't
belong to the transformer's values (LowestTapValue < MinUsablePosition and/or HighestTapValue >
MaxUsablePosition)
For AVR function configured in Master Follower in parallel mode, all the AVR functions must
have the same min and max values for the attributes Highest Tap Value and Lowest Tap Value
for the TAP.

119/182
Energy Automation
84365 / AVR / Site | Substation / All the AVR functions must have the same min and max values
for the TAP
When there is an existing datapoint Tr.Not.Parallel under an AVR :
The attribute tranformer_in_parallel of AVR must be equal to 1 (Yes)

84404 / AVR / Site | Substation / The attribute 'transformer_in_parallel' of AVR must be equal to 1
(Yes)
The attribute 'parallel_method' of AVR must be equal to 0 (Master / Follower)

84405 / AVR / Site | Substation / The attribute 'parallel_method' of AVR must be equal to 0
(Master / Follower)
The attribute 'master_follower_role' of AVR must be equal to 1 or 2 (Follower of Follower Master

backup)
84406 / AVR / Site | Substation / The attribute 'master_follower_role' of AVR must be equal to 1 or
2 (Follower of Follower Master backup)
Only one Follower can be configured with its master

84407 / AVR / Site | Substation / Only one Follower can be configured with its master
The attribute master_failure_management of AVR must be equal to 1 (Stand alone regulation)

84408 / AVR / Site | Substation / The attribute master_failure_management of AVR must be
equal to 1 (Stand alone regulation)

120/182
Energy Automation
Graphical check
MVs under an AVR function can be displayed specifically.

Two MVs cannot have the same display configuration (ie Display Type + Display Page + Display
Order)
84453 / AVR / Display attributes [DisplayType-Page-Order] must be unique for each MV into an
AVR.
Furthermore, the maximum order for Fixed MVs into page 1 is 2 (instead of 7)
84452 / AVR / The maximum display order for fixed MV into page 1 is 2.
2.3.19 OI Workspace
Scs
Ethernet network (R) has for workspace Graphic
OI bay OI workspace #1
OI Server OI workspace #2
OI Client (R) has for workspace
2.3.19.1 Display resolution
An OI Workspace which has for display resolution 800x600 must be used only by an OI Bay
78267 / OI Workspace / The displayed resolution 800x600 must be used only by an OI Bay
2.3.19.2 Limitations
An OI workspace shouldnt contain more than 150000 graphic objects (i.e. graphical symbols).
78313 / OI Workspace / The number of graphical objects by OI Workspace exceed the acceptable
limit (count of objects, max value)
2.3.19.3 OI Bay limitations
A workspace used by an OI Bay must respect some constraints.
Alarm, Title and Command banners are not allowed in 800x600 resolution.
78268 / OI Workspace / The Alarm, Title and Command banners are not allowed in a 800x600
workspace -> [forbidden component]
Up to five mimics are allowed by workspace.
78269 / OI Workspace / Up to five mimics are allowed in an OI Bay workspace -> [mimic count]
The count of Active X must respect the following rules:

Only one alarm viewer and one trend viewer can be configured

121/182
Energy Automation
FSS viewer is not allowed
78270 / OI Workspace / The count of an activeX type is not good in an OI Bay workspace ->
[ActiveX type, allowed, count]
The workspace of an OI Bay in 800x600 resolution must have at least actions Login and Exit
(actions are specific launch actions):
78277 / OI Workspace / The mandatory action type is not defined for the 800x600 workspace ->
[action type]
The workspace of an OI Bay in 800x600 resolution must not have a memo icon :
76357/ OI Bay / Graphic | Memo / A Memo can't be memo of OI Bay which 800*600 resolution
workspace -> [Graphic | Memo]
An OI Bay can't be linked with a 800*600 resolution workspace which have a Memo Icon :
76358 OI Bay / Graphic | OI workspace | Window | Mimic | Memo icon 1 / An OI Bay can't be
linked with a 800*600 resolution workspace which have a Memo Icon -> [Graphic | OI workspace |
Window | Mimic | Memo icon 1]
An OI Window can not have both a Mimic and an Banner :
43372 / Window / A Window can not have both a Mimic and a Banner
An OI Window can not have two Banners :
43376 / Window / A Window can not have two Banners.
2.3.20 OI Window
Graphic Scs
OI workspace (R) is workspace of Ethernet network
Window OI client
Mimic
Std Alarm Banner
Std Comm. Banner
Std Title Banner
An OI "Window" which has its "OI workspace" linked to at least 1 "OI client", must not be empty.
It must contain at least one of the following components :
- Mimic(s)
- one Standard alarm banner
- one Standard command banner
- one Standard title banner

122/182
Energy Automation
43117 / Window / The Window is empty
2.3.21 OI Mimic
2.3.21.1 Symbols
Coordinates of Symbols :
Graphic
OI workspace
window (A) width / (A) height
Mimic 1000 / 700
(A) x / (A) y
AlarmViewer 0, 0
(A) x / (A) y
AlarmMultiState 0, 70
Circle (A) x / (A) y
0, 140
Group (A) x / (A) y
10, 150
Circle (A) x / (A) y
Text (A) x / (A) y 10, 150
10, 150
The coordinates (x, y) of a symbol must not be located outside the mimic area.
47122 / Symbol / The symbol is outside the mimic area
Example :
47122 / Symbol / The symbol is outside the mimic area (1000, 700)-> [x = 1085, y = 55]
Limits of the count of Symbols :
Graphic
OI workspace
window
Mimic
Group
Shape
Multistate
MultiState Max = 1500 / mimic
Shape

The number of symbols (shapes or multistates) cant exceed 1500 inside a mimic. This count is done
recursively. The groups are not count, but their sons yes.
02003 / CapacityLimits / The count of Symbol components is not valid (count, maximum)
2.3.22 Bay Mimic symbols
2.3.22.1 Symbols
Hidden Symbols :

123/182
Energy Automation
Graphic
Comp. workspace
width = 128 / height = 128 (fixed values)
Bay mimic
LHMI Transformer (A) x / (A) y 0, 65
LHMI Gen module (A) x / (A) y 0, 85
LHMI bitmap (A) x / (A) y 0, 45
LHMI line (A) x / (A) y
(A) x / (A) y 40, 10
LHMI text
0, 40
The coordinates (x, y) of a symbol must not be located outside the mimic area.
47122 / Symbol / The symbol is outside the mimic area
Example :
47122 / Symbol / The symbol is outside the mimic area (128, 128)-> [x = 145, y = 6]
Limits of the count of Symbols :
Graphic
Comp. workspace
Bay mimic max = 24 / Comp. workspace
LHMI Transformer max = 9 / Bay mimic
LHMI Gen module
LHMI bitmap max = 5 / Bay mimic
LHMI line max = 30 / Comp. workspace max = 18 / Bay mimic
LHMI text max = 5 / Bay mimic (1 is reserved for the Bay name) + 1 reserved
for the Bay name
Some limit exceedings are prevented by the Structural Database rules. The others leads to the
following errors :
02003 / CapacityLimits / The count of components is not valid (count, maximum)
Examples :
02003 / CapacityLimits / The count of LHMI Gen module, LHMI Transformer components is not
valid (count, maximum)-> [10, 9]
02003 / CapacityLimits / The count of LHMI bitmap, LHMI line, LHMI text components is not valid
(count, maximum)-> [21, 18]
02003 / CapacityLimits / The count of LHMI line components is not valid (count, maximum)-> [35,
30]
Empty texts :

124/182
Energy Automation
Graphic
Comp. workspace
Bay mimic
LHMI Transformer
(A) short name
Name
LHMI Gen module
(A) short name
Name
(A) fixed text value
LHMI text
(A) short name
EQL BP (A) short name
L/R
(A) short name
S/C BP
SBMC (A) short name
LHMI labels (A) all labels
The text of a symbol or labels must not be empty. The check is done for languages use by computer
generator.
47187 / Symbol / The text symbol of a Local HMI mustn't be empty (Language)
47188 / Symbol / The local HMI label mustn't be empty (Label name, Language)
2.3.22.2 Visualized MV datapoints
Graphic Feeder
Comp. workspace (R) represents - Cyclic long period

(A) transmission on event - Cyclic short period
Bay mimic MV - According to a % of full scale value
(R) visualizes
- According to a % of current value
An MV Datapoint visualized in a "Bay mimic" (relation "visualizes") must be produced by a TMU

board.
33168 / BayMimic / The MV datapoint must be produced by TMU board for bay visualization
An MV Datapoint visualized in a "Bay mimic" (relation "visualizes") must belong to the bay
represented by the "Bay mimic" (relation "represents").
33125 / BayMimic / The datapoint does not belong to the bay (datapoint, bay)-> [visualizes :
VoltageLevel MV, represents : Feeder]
For each visualized MV Datapoint, the "transmission on event" attribute must be set neither to
"Cyclic short period" value nor to "Cyclic long period" value to avoid overflow of the Bay mimic
input buffer.
33123 / BayMimic / The attribute value is not compatible with the relation-> [transmission on event
= Cyclic short period, is visualized by : Bay mimic]
2.3.23 Standard Command Banner

125/182
Energy Automation
2.3.23.1 OI Bay
The Klaxon usage value on a Standard Command Banner of an OI Bay must be set to No,
because OI bay doesnt manage Klaxon option.
76255 / OI Bay/ Klaxon usage value on Standard Command Banner of an OI Bay must be set to
No (OI Bay)
,
2.3.24 OI symbols
2.3.24.1 Multi-States
Graphic
OI workspace
window Bay
Mimic (R) is managed by Board
Alarm MultiState IED
Audi. MultiState Module
Discrepancy MS
For each Multi-State : 1, and only 1, relation "is managed by" must be linked.
49130 / MultiState / At least one relation must be linked-> [is managed by]
49113 / MultiState / Multiple links-> [is managed by : ]
Example :
49113 / MultiState / Multiple links-> [is managed by : Feeder]
Multistate cant have another MultiState as parent (at any level)
49218 / MultiState / A multistate must not be a sub-object of another mulitstate (Parent Object)
Exemple :
SPS multistate is under an
another Multistate Object (MPS
Multistate) = Error 49218


A multistate can only use symbol defined inside itself
49231 / MultiState / A multistate must reference only symbol defined inside it (Symbol)

126/182
Energy Automation
2.3.24.2 Var Texts
Graphic
OI workspace
Bay
window
(R) refers to Board
Mimic
Var. text IED
Module

For each "Var.Text" : 1, and only 1 relation "refers to" must be linked.
For each "Launch Action" : 1, and only 1 relation "acts on" must be linked.
47130 / Symbol / At least one relation must be linked-> [refers to]

47113 / Symbol / Multiple links-> [refers to : ]
Example :
47113 / Symbol / Multiple links-> [refers to : Feeder]
2.3.24.3 Trend viewer
Graphic
OI workspace
window
Mimic (A) trend type - real time
Trend viewer
- archive
Series (1)
Series (2)
If a "Trend viewer" has its "trend type" attribute set to "real time", then it can have only 1 "Series".
45003 / TrendViewer / The count of Series components is not valid (count, maximum)
Example :
45003 / TrendViewer / The count of Series components is not valid (count, maximum)-> [2, 1]
In case of usage by an OI Bay in 800x600 resolution, theres some limitations.
Scs
Graphic (R) is workspace of Ethernet network
OI workspace OI Bay
window
Mimic
Trend viewer
The trend viewer type must be set to real time

127/182
Energy Automation
45275 / TrendViewer / The trend type must be set to real time in a 800x600 workspace
2.3.24.4 Alarm/State viewer
Graphic
OI workspace
window
Mimic (R) is pre-filtered on
Bay
Alarm viewer Voltage level

For an "Alarm/state viewer", only 1 relation "is pre-filtered on" can be linked.
46112 / AlarmViewer / Multiple links to filters-> [is pre-filtered on : ]
Example :
46112 / AlarmViewer / Multiple links to filters-> [is pre-filtered on : Feeder]
For an alarm/state viewer, at least, one list must be defined.

46194 / AlarmViewer / Missing a defined list for alarm/state viewer
Graphic
OI workspace (A) display count of active alarms
window
Yes
Mimic (A) display count of present alarms
Alarm viewer Yes
For an alarm/state viewer which has a browser counting alarms, the alarm list must be defined.
46245 / AlarmViewer / The alarm list must be defined for alarm/state viewer browser which count
alarms
In case of usage by an OI Bay in 800x600 resolution, theres some limitations.
Scs
Graphic (R) is workspace of Ethernet network
OI workspace OI Bay
window
Mimic
Alarm viewer
The alarm viewer must be pre filtered
46271 / AlarmViewer / A relation is pre-filtered on must be defined in a 800x600 workspace
The alarm viewer mustnt contain event list or archive list
46272 / AlarmViewer / The list of the alarm viewer is not allowed in a 800x600workspace -> [list]
The alarm viewer mustnt have a contextual menu defined (contextual menu attribute must be set
to No)

128/182
Energy Automation
46273 / AlarmViewer / The contextual menu attribute must be set to No in a 800x600workspace
The alarm viewer toolbar must contain only Acknowledge and Clear buttons or separators (toolbar
attributes for other buttons must be set to 0)
46274 / AlarmViewer / A button of the toolbar mustnt be used (the rank must be set to 0) in an OI
Bay workspace -> [button attribute]
2.3.24.5 ActiveX columns
(A) timestamp column rank

Graphic (A) origin column rank [0..6]
OI workspace (A) object name column rank [0..6]
window (A) object message column rank [0..6] ( 0 means "not used" )
Mimic (A) alarm state column rank [0..6]
(A) alarm gravity column rank [0..6]
Alarm viewer [0..6]

(A) origin column rank [0..4]
(A) object name column rank [0..4]
[0..4] ( 0 means "not used" )
(A) object message column
FSS viewer [0..4]
rank
(A) origin column rank [0..6]
(A) object name column rank [0..6]
(A) object message column rank [0..6] ( 0 means "not used" )
(A) alarm state column rank [0..6]
(A) alarm gravity column rank [0..6]
Std Alarm Banner [0..6]
For each ActiveX :

- there must be at least one column definition with a value different from 0.
- each column value (if different from 0) must be unique
44118 / ActiveX / No column is selected

44119 / ActiveX / Multiple use of the same column rank
Example :
44119 / ActiveX / Multiple use of the same column rank-> [object name column rank, origin column
rank, object message column rank, timestamp column rank, 1]
2.3.24.6 Graphic and Launch Actions
Graphic
OI workspace
window
Mimic (1)
Rectangle
Change view
(R) has for new view
Mimic (2)
Each "has for new view" relation of a Symbol "Change view" action must be linked to another Mimic
than the one under which the symbol is located.

129/182
Energy Automation
47120 / Symbol / The initial and target mimics are identical
Example :
47120 / Symbol / The initial and target mimics are identical-> [has for new view : Mimic (1)]
Graphic
OI workspace
window
Mimic
Circle
(R) acts on (R) has for profile
Open ctrl popup DPC DPC profile
(R) acts on
(R) has for profile
SPC SPC profile
For an "Open ctrl popup", all the Datapoints linked to the "acts on" relation, must fulfil the following
conditions :
- all of them, or none, are linked to the same Datapoint through the relation "has for feedback"
- all of them, or none, are linked to the same Datapoint through the relation "has for AutoManu
dependency"
- all of them have their attributes "Substation mode dependency" set to the same value (if the
attribute is available, up to four attributes may be configured)
- all of them have their attribute "bay mode dependency" set to the same value (if the attribute is
available)
- all of them have their attribute "SBMC mode dependency" set to the same value (if the attribute is
available)
- all of them have the attribute "SBO mode" of their Profile set to the same value
- if the OpenPopupControl authorizes the Lock function, and if one or several of them have at the
same level the following datapoints : LockModule (SPS) and LockModule_SPC, then all of them
must belong to the same module.
Particular check for Circuit breaker with internal synchrocheck:

- when internal synchrocheck is automatic, OpenControlPopup can acts on the Switch Ctrl xPC and
Sync CB Close at same time
- when internal synchrocheck is manual, OpenControlPopup can not acts on the Switch Ctrl xPC and
Sync CB Close at same time
47121 / Symbol / The linked datapoints have incompatible definitions (relations)-> [acts on]
For an "Open ctrl popup" authorizing the Locking function, the datapoints of locking "LockModule" and
"LockModule_SPC" for the controlled datapoint should be present.
47191 / Symbol / The locking datapoints should be present (relations)-> [acts on]
Graphic
OI workspace
window
Mimic
Circle SPS (R) has for profile SPS profile
(R) acts on
Send FSS Order or or
DPS DPS profile

130/182
Energy Automation
For an UserAction "Send FSS Order", the datapoint (SPS or DPS) linked to the "acts on" relation must
have a profile with the attribute "EnableFSS" set to true.
47171 / Symbol / The linked datapoint profile isn't FSS enable (relations)-> [acts on]
One and only one Launch Action can be configured under a Graphical symbol object
Graphic
OI Workspace
Window
Mimic
Symbol
Launch Action [0..1]
47289 / Symbol / Graphic | OI workspace | Window | Mimic | Circle / Only one launch action
allowed under graphical symbol object
2.3.24.7 Text
Graphic
OI workspace
window
Mimic
Text
(A) Type
(A) Box color
A text which is defined as non standard type must be transparent.
47276 / Symbol / The text color is not allowed for this type -> [type, bad color, allowed color]
Try to avoid putting a SendOrder under a Text.
47304 / Symbol / Its better to avoid putting a Send Order under a Text symbol.
When a text has current time, current date or logged user as type, it is not allowed to put it under
a group. The text need to be moved outside the group.
47334 / Symbol / A text with type "current time", "current date" or "logged user" can not be used in
a group, move the text out of the group.

131/182
Energy Automation
2.3.24.8 Image
On image object the attribute file name must be defined.
47296 / Symbol/ Graphic | OI workspace | Window | Mimic | Image 2 / The attribute "file name" of
an Image object must be defined
2.3.25 Bitmaps
All the Bitmaps of a configuration are defined in the "Bitmap table" of the configuration.
2.3.25.1 Bitmap index
Graphic
Graph. Tables
Bitmap table (A) reference index
Bitmap (1) 0
(A) reference index
Bitmap (2) 1
Bitmap (3) (A) reference index
2
The "reference index" attribute value of each "Bitmap" of the "Bitmap table" must be unique.
48115 / Bitmap / The attribute value is not unique in the Bitmap Table
Example :
48115 / Bitmap / The attribute value is not unique in the Bitmap Table-> [reference index, 0]
2.3.25.2 Bitmap size
Graphic
Graph. Tables
Bitmap table - Simple
(A) type - 5-uple
Bitmap
(A) file name by default
(A) file name for 'open' state file1.png
(A) file name for 'closed' state file2.png
file3.png
(A) file name for 'withdrawn open' state
file4.png
(A) file name for 'withdrawncclosed' state file5.png
Depending on the "type" attribute value, 1 or 5 PNG file(s) can be linked to a Bitmap.
For each one, the bitmap size must be 512 bytes.
48124 / Bitmap / The bitmap size in bytes is not valid (file, size, max)
Example :
48124 / Bitmap / The bitmap size in bytes is not valid (file, size, max)-> [file name by default =
file1.png, 519, 512]
2.3.25.3 Reference from BayMimic elements to Bitmap

132/182
Energy Automation
Graphic
Comp. workspace
Bay mimic (A) bitmap reference
LHMI bitmap 0
LHMI Gen module

(A) multi-bitmap reference
LHMI xPS MultiSt 1
LHMI Transformer
(A) bitmap reference
LHMI TPI MultiSt 2
Graph. Tables
Bitmap table
(A) reference index
Bitmap (1) 0
Bitmap (2) (A) reference index 1
Bitmap (3) (A) reference index 2
The link from an element to its bitmap is defined with the attribute : "bitmap reference". The value of
this attribute must refer to an existing bitmap in the "Bitmap table".
33116 / BayMimic / The reference does not exist in the Bitmap Table
Example :
33116 / BayMimic / The reference does not exist in the Bitmap Table-> [multi-bitmap reference, 10]
Graphic
Comp. workspace Feeder
Bay mimic Circuit breaker
LHMI Gen module Withdrawn SPS
(R) is managed by
LHMI xPS MultiSt xPS
(A) multi-bitmap reference
Graph. Tables
Bitmap table
(A) reference index
Bitmap 0
(A) type 5-uple
(A) file name by default
(A) file name for 'open' state file1.png
(A) file name for 'closed' state file2.png
file3.png
(A) file name for 'withdrawn open' state
file4.png
(A) file name for 'withdrawn closed' state file5.png
The "Bitmap" linked to a "LHMI xPS MultiSt" MultiState must be defined as follow :
- 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.
33126 / BayMimic / The attribute value of the referenced bitmap is not valid
33127 / BayMimic / The attribute value of the referenced bitmap is missing
33128 / BayMimic / Multiple use of the same attribute value in the referenced bitmap

133/182
Energy Automation
Example :
33126 / BayMimic / The attribute value of the referenced bitmap is not valid-> [Graphic | Graph.
Tables | Bitmap table | Bitmap | type, Single]
33127 / BayMimic / The attribute value of the referenced bitmap is missing-> [Graphic | Graph.
Tables | Bitmap table | Bitmap | file name by default]
33128 / BayMimic / Multiple use of the same attribute value in the referenced bitmap-> [Graphic |
Graph. Tables | Bitmap table | Bitmap | file name by default, file1.png]
33127 / BayMimic / The attribute value of the referenced bitmap is missing-> [Graphic | Graph.
Tables | Bitmap table | Bitmap | file name for 'withdrawn open' state]
33128 / BayMimic / Multiple use of the same attribute value in the referenced bitmap-> [Graphic |
Graph. Tables | Bitmap table | Bitmap | file name for 'withdrawn open' state, file4.png]
2.3.25.4 Memo bitmaps
The memo are a specific type of bitmaps. They are used by Memo Icons.
Graphic
OI workspace
Window
Mimic (R) has for memo Graphic
Memo icon Memo
(A) bitmap reference
Graph. Tables
Bitmap table
(A) reference index
Bitmap 0
(A) type Memo for OI client
(A) file name for unavailable state
(A) file name for 'no note' state file1.png
(A) file name for 'active' state file2.png
file3.png
(A) file name for 'inactive' state
file4.png
Only a Memo icon can reference a memo bitmap, and only this type.
64126 / Memo icon / The attribute value of the referenced bitmap is not valid
33126 / BayMimic / The attribute value of the referenced bitmap is not valid
Example :
64126 / Memo icon / The attribute value of the referenced bitmap is not valid-> [Graphic | Graph.
Tables | Bitmap table | Bitmap | type, Single]
33126 / BayMimic / The attribute value of the referenced bitmap is not valid-> [Graphic | Graph. Tables
| Bitmap table | Bitmap | type, Memo for OI client]
In a Memo Bitmap, all referenced bitmaps must be filled

48127 / Bitmap / The attribute value of the referenced bitmap is missing

134/182
Energy Automation
Example :
48127 / Bitmap / The attribute value of the referenced bitmap is missing-> [file name for 'no note'
state]
In a Memo Bitmap, all referenced bitmaps must have same size

48205 / Bitmap / The bitmap sizes are not equal (file 1, file 2)
Example :
48205 / Bitmap / The bitmap sizes are not equal (file 1, file 2) -> [file name for 'no note' state =
file1.png (16x16), file name for 'active' state = file2.png (8x16)]
2.3.25.5 Particular format for VarText symbol and VarText
For VarText symbol and VarText, the attribute 'particular format' (used at OI client level) should have
the same value for the database languages.
06325 / Attributevalue / The format should have the same value for all the database languages
2.3.26 Memo
Graphic
Memo
Bay
(R) is memo of Module
(non)IEC physical device
For each "Memo" : 1, and only 1 relation "is memo of" must be linked.
72130 / Memo / At least one relation must be linked-> [is memo of]
72113 / Memo / Multiple links-> [is memo of : ]
2.3.27 Alarm Groups
Graphic
(R) uses
Alarm group Datapoint
For an "Alarm Group", at least 1 relation "uses" must be linked.
50130 / AlarmGroup / At least one relation must be linked-> [uses]
Graphic
(R) uses
For an "Alarm Group", data point used must be alarmed

135/182
Energy Automation
73265 / AlarmGroup / Data point used by alarm group is not alarmed-> [Graphic |
ALR.GRP.NOT.OI]
2.3.28 User Profile
A User Profile cant be called Administrator
60181 / UserProfile / User Profile name is not allowed (name) -> [name]
2.3.29 Buffered reports
The buffered status of reports between a server and a client is defined on the relation
Has_for_IEC61850_server by the attribute prefered report type.
An IED cant have more than 4 IEC61850 clients using buffered reports.
92393 / Buffered Reports / Number of buffered clients for this server is invalid (count, maximum)->
[count, max]
Only computers (C264) and gateways can have IEC61850 clients using buffered reports.
92394 / Buffered Reports / Only computers, gateways and non PACiS IED can be server of
buffered reports
Computers (C264) cant be IEC61850 client using buffered reports.
92395 / Buffered Reports / Computers can't be client of buffered reports
If an OI server is IEC61850 client of many servers, all its relations has for IEC61850 server must use
the same prefered report type (buffered report or unbuffered report).
92396 / Buffered Reports / All the relations client/server of an OI must use the same prefered
report type (buffered or unbuffered)
2.4 Datapoints checks
2.4.1 Datapoint Profiles
2.4.1.1 Events logging

136/182
Energy Automation
If a Datapoint profile is linked to an OI printer through its attributes printer usage (1<=i<=4) set on
Events, then its "treatment on event" attribute must be set to Logging for OI and/or computer.
In the case of profiles having several attributes "treatment on ", at least one of them must respect
the rule.
23082 / DatapointProfile / The logging definition is not compatible with the attribute printer usage

If a datapoint profile is linked to a OI printer through its attributes printer usage (1<=i<=4) set on
Alarms , then:
- its must respect previous rule.
- its alarms "defined" attribute must be set to "Yes".
23082 / DatapointProfile / The logging definition is not compatible with the attribute printer usage

23083 / DatapointProfile / The alarm definition is not compatible with the attribute printer usage 
2.4.1.2 SBO mode
Profile per Datapoint type :

137/182
Energy Automation
Substation Scs
Loc/rem ctrl DPC (R) has for profile (A) SBO mode Direct Execute
DPC profile
(R) has for profile (A): SBO mode
Feeder SPC profile Direct Execute
Loc/rem ctrl DPC
(R) has for profile (A) SBO mode
Setpoint profile Direct Execute
Circuit breaker
Selection SPC (R) has for profile
Setpoint
ATCC (R) has for profile (A) SBO mode Direct Execute
SPC SPC profile
DPC DPC profile Direct Execute
BusBar
ATCC fct needs (R) has for profile (A) SBO mode Direct Execute
SPC SPC profile
DPC DPC profile Direct Execute
Transformer
transformer
ATCC fct needs (R) has for profile (A) SBO mode Direct Execute
SPC SPC profile
DPC (R) has for profile DPC profile (A) SBO mode
Direct Execute
Tap changer (R) has for profile (A) SBO mode
Raise/lower DPC DPC profile SBO Operate Many
Scs
Ethernet network
C264 (R) has for profile (A) SBO mode
Loc/rem ctrl DPC DPC profile Direct Execute
Substation (R) has for synchrocheck Scs

Ext manual CS
Feeder 1
Circuit breaker (R) has for profile (A) SBO mode
Sync CB close (SPC) SPC profile Direct Execute
Feeder 2 (R) has for synchrocheck

Ext manual CS

Ext auto CS
Sync CB close (SPC) SPC profile SBO Operate Once

Int manual synchrocheck (R) has for profile
on/off ctrl DPC DPC profile (A) SBO mode
(R) has for profile Direct Execute
on/off ctrl SPC SPC profile
Circuit breaker

Int auto synchrocheck
(R) has for profile
on/off ctrl DPC DPC profile (A) SBO mode
on/off ctrl SPC (R) has for profile Direct Execute
SPC profile
Circuit breaker
Sync CB close (SPC) (R) has for profile (A) SBO mode
SPC profile SBO Operate Once
The possible values of the "SBO mode" attribute of the profile of a Datapoint are :
SBO Operate Many

138/182
Energy Automation
SBO Operate Once

Direct Execute
Direct Execute with SBO popup
The following table shows the constraints on the value of the "SBO mode" attribute of the profile of a
list of Datapoints :
Datapoints "SBO mode" attribute value

"Raise/lower DPC" Datapoint "SBO Operate Many" :
is allowed only for this Datapoint.
It's forbidden for any other Datapoint.
"Loc/rem ctrl DPC" Datapoint of Substation, Bays, Allowed values are :
Computers "Direct Execute"
"Selection SPC" Datapoint of Circuit-breaker Allowed values are :
"Direct Execute"
SPC and DPC Datapoints of the "ATCC" function Allowed values are :
"Direct Execute"
SPC and DPC Datapoints of "ATCC fct needs" of Allowed values are :
BusBars and Transformers "Direct Execute"
Setpoint Datapoints which are wired on DO Allowed values are :
channels of Computer "Direct Execute"
"Sync CB close" Datapoint of a "Circuit breaker" Allowed values are :
linked to a "Ext manual CS" or "Int manual "Direct Execute"
synchrocheck" synchrocheck built-in funtion Direct Execute with SBO popup
"Sync CB close" Datapoint of a "Circuit breaker" Allowed value is :
linked to a "Ext auto CS" or "Int auto "SBO Operate Once"
synchrocheck" synchrocheck built-in funtion
"on/off ctrl DPC" or "on/off ctrl SPC" Datapoint of Allowed values are :
an "Int synchrocheck" synchrocheck built-in "Direct Execute"
funtion Direct Execute with SBO popup
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)
Example :
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)-> [Scs |
DPC profile | SBO mode, SBO Operate Many]
SPC profile | SBO mode, SBO Operate Once]
Deselection address :
Note : This check is processed only for UCA2 Ethernet Network protocol.

139/182
Energy Automation
(R) has for profile Scs

(A) SBO mode SBO Operate Once
SPC SPC profile
DPC DPC profile SBO Operate Once
Setpoint Setpoint profile SBO Operate Once
C264
C26x UCA2 Map.
LD
n
GenBRIC
(R) has for UCA2 address CO (A) UCA2 name
GenBO BO
(R) has for UCA2 address (A) UCA2 common class
GenDCO
(R) has for UCA2 address SP
GenAO
R: has for UCA2 deselect address
(A) UCA2 name

GenSBOCF nSBO
For each SPC, DPC or Setpoint datapoint having a profile with "SBO mode" attribute set to "SBO
Operate Once" or "SBO Operate Many" value :
if the datapoint is linked to an UCA2 address through the relation "has for UCA2 address", then this
address must be linked to a deselection UCA2 address through the relation "has for UCA2 deselect
address".
Furthermore, for an SPC or DPC datapoint, the UCA2 name of the deselection address must be
made of the UCA2 name of the address followed by the "SBO" string.
23084 / DatapointProfile / The link to deselection address is missing

23085 / DatapointProfile / The name is not valid (valid name = GenBOSBO)-> [GenSBOCF]
Order type of IED address :
(R) has for profile Scs

(A) SBO mode
SPC SPC profile SBO Operate Once
DPC DPC profile SBO Operate Once
Setpoint Setpoint profile SBO Operate Once
C264
DNP3 master
DNP3_IED
(R) has for IED address IED SPC Mapping (A) order type
SPC addr. on IED - SBO
- Direct Execute
For each SPC, DPC or Setpoint datapoint linked to an IED address through the "has for IED address"
relation : the "order type" attribute value of the IED address must match the "SBO mode" attribute
value of the datapoint profile.

140/182
Energy Automation
23086 / DatapointProfile / The attribute value does not match the datapoint profile (attribute, profile
attribute)-> [order type = Direct execute, SBO mode = SBO Operate Once]
2.4.1.3 Forcing/Substition/Suppression enabling
(R) has for profile Scs (A) enable Force/Subst/Sup

SPS SPS profile - No
DPS DPS profile - Yes
MPS MPS profile
MV MV profile
Counter Counter profile
The profile of a Datapoint of the System topology must have its "enable Force/Subst/Sup" set the "No"
value.
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)
Example :
SPS profile | enable Force/Subst/Sup, Yes]
2.4.1.4 Alarming/Archiving/Logging/MeanValue Computation for non addressed

datapoints
A datapoint which is not addressed cant be alarmed/archived/logged or computed by OI. Warn user if
profile says other.
The datapoint non addressing possible causes are following :

- IEC61850 address is not available for this kind of datapoint
- datapoint is out of scope of IEC61850 auto-addressing
- datapoint must be IEC61850 addressed
2.4.1.4.1 Alarmed Datapoints :
(R) has for profile Scs (A) Alarms / defined

Dpt Dpt profile Yes
23172 / DatapointProfile / The Datapoint is alarmed in OI but has no IEC61850 address
Remark: If the datapoint is in a OI Server no warning is displayed
2.4.1.4.2 Logged Datapoints :

Scs
Ethernet network
(R) has for profile Scs (R) has events logged on OI server
Dpt Dpt profile OI printer
(R) has alarm events logged
on

141/182
Energy Automation
23173 / DatapointProfile / The Datapoint is logged in OI but has no IEC61850 address
2.4.1.4.3 Mean value computation Datapoint :
(R) has for profile Scs (A) Mean value / computation

MV MVProfile Yes
(R) has for profile (A) Mean value / computation
Counter CounterProfile Yes
23174 / DatapointProfile / The Datapoint has mean value computed by OI but has no IEC61850
address
2.4.1.4.4 Archived Datapoint :
(R) has for profile Scs (A) State treatment / treatment on event
Dpt Dpt profile - Archive and logging
- Archive only
23175 / DatapointProfile / The Datapoint is archived in OI but has no IEC61850 address
Remark: If the datapoint is in a OI Server no warning is displayed
If multiple profiles with the same name exist, then a check should be raised
23409 / DatapointProfile / Multiple profile with the same name
All command datapoints that have an address on a Modbus gateway can not be set at Select before
Operate.
18413 / DatapointProfile / SBO are forbidden for Modbus, all commands must be DE (Direct
Execute).
2.4.1.5 C264 state treatments values
All C264 state treatments must have the same value.

Treatment on event has available values:
C264 : no archive, no logging
C264 : no archive, logging
C264 : archive, logging
C264 : archive, no logging
Profile C26x treatment on

Short Long SelfCheckFaul Substitute Forcin Substitutio
Reset Set Toggling Unknown Suppressed Forced Suppressio
name name t d g n
SPS archive, archive, archive, archive, archive, archive, archive, archive, archive, archive,
SPS archive, logging
profile logging logging logging logging logging logging logging logging logging logging

142/182
Energy Automation
23428 / DatapointProfile / All C264 state treatments should have the same value for a profile given
Example:
23248 / DatapointProfile / All C264 state treatments should have the same value for the profile SPS
PROFILE of type DPS.
2.4.2 Acquisition / Control Source definition
For a Datapoint, the Acquisition/Control source is defined through relations.
Prior to the checks definitions, the figures hereafter introduce those relations, per Datapoint type, as
they are defined by the SCE Data Design.
Note :
If the Acquisition source is defined with the "is managed by" relation, then the Datapoint is considered
as a "System" Datapoint.
C264
DIU200
Counter (R) 'primary input' wired DI # 0
on 'secondary input' wired on
(R) DI # 1
(R) is computed by
TIU200
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
IED_@
UCA2/IEC gen IED

UCA2/IEC IED Map.
(R) has for UCA2/IEC address
UCA2/IEC_@
(R) is managed by
Slow automation
C264
DIU200
SPS (R) wired on
DI # 0
DI # 1
DNP3 master
DNP3_IED
IED_@
UCA2/IEC gen IED

(R) has for UCA2/IEC address UCA2/IEC IED Map.
UCA2/IEC_@
(R) is managed by
Slow automation
(R) is produced by Fast automation

Output
FBD automation
(R) is produced by FBD output

143/182
Energy Automation
C264
DIU200
DPS (R) 'closed' wired on
DI # 0
(R) 'open' wired on DI # 1
DNP3 master
DNP3_IED
IED_@ (1)
(R) has for IED address IED_@ (2)
UCA2/IEC gen IED

UCA2/IEC_@
(R) is managed by
Slow automation
(R) has 'closed' state given by SPS (1)
(R) has 'open' state given by SPS (2)
C264
DIU200
MPS (R) 'state' wired on
DI # 0
(R) 'read inhibit' wired on DI # 1
DNP3 master
DNP3_IED
IED_@
UCA2/IEC gen IED

UCA2/IEC_@
(R) is managed by
Slow automation
C264
(R) 'bit ' wired on DIU200
MV DI # 0
(R) 'read inhibit' wired on DI # 1
(R) 'sign bit' wired on DI # 2
AIU200
(R) wired on AI # 0
(R) is computed by
TIU200
DNP3 master
DNP3_IED
IED_@
UCA2/IEC gen IED

UCA2/IEC IED Map.
UCA2/IEC_@
(R) is managed by
Slow automation

144/182
Energy Automation
C264
(R) wired on DOU200
SPC DO # 0
DNP3 master
DNP3_IED
IED_@
UCA2/IEC gen IED

UCA2/IEC IED Map.
UCA2/IEC_@
(R) is managed by
Slow automation
FBD Automation
(R) is controlled by
FBD output
C264
(R) 'closed' wired on (*) DOU200
DPC DO # 0
(R) 'open' wired on (*) DO # 1
DNP3 master
DNP3_IED
IED_@ (1)
UCA2/IEC gen IED

UCA2/IEC IED Map.
UCA2/IEC_@
(R) is managed by
Slow automation
FBD Automation
(R) is controlled by FBD output
(*) up to 2 closed wired on and 2 open wired on relations can be set (i.e. up to 4 DO channels for the
same DPC).
C264
(R) 'bit ' wired on DOU200
Setpoint DO # 0
(R) 'read inhibit' wired on DO # 1
(R) 'sign bit' wired on DO # 2
(R) 'refresh' wired on DO # 3
(R) wired on AOU200

AO # 0
(R) wired on
AO # 1
(R) wired on AO # 2
(R) wired on AO # 3
DNP3 master
DNP3_IED
IED_@
UCA2/IEC gen IED

UCA2/IEC IED Map.
(R) has for UCA2/IEC address UCA2/IEC_@
(R) is managed by
Slow automation

145/182
Energy Automation
LSP Site
Has for FLS server : C264-1
System
C264
C264-1
C26x IEC Map
IEC@
The choice between the two relations "has for UCA2 address" and "has for IEC address" must be
compatible with the "Ethernet network" protocol (UCA2 or IEC61850).
21114 / DatapointServer / The relation is not compatible with the Ethernet network protocol
Example, for an UCA2 Ethernet Network protocol :

21114 / DatapointServer / The relation is not compatible with the Ethernet network protocol-> [has
for IEC address : ACDxST]
Only 1 Acquisition/Control source can be defined per Datapoint.
21043 / DatapointServer / Multiple control sources (server, relation)

21041 / DatapointServer / Multiple acquisition sources (server, relation)
Example :
21043 / DatapointServer / Multiple control sources (server, relation)-> [Scs | Ethernet network |
C264, has for IED address : DPC addr. on IED]
A datapoint must be addressed on the computer which manages it.
i.e.: the automatic addressing generate addresses of a bay datapoint on the computer which manage
the bay, but if the datapoint is produced by an automation which is managed by another computer,
theres a problem to determine which computer is server.
21045 / DatapointServer / The relation link is not compatible with the datapoint server
Example :
21043 / DatapointServer / The relation link is not compatible with the datapoint server -> [has for
IED address : DPC addr. on IED]
Counter Datapoint :
Only 1 relation "has for UCA2 address" or "has for IEC address" is allowed. It must be compatible with
the "Ethernet network" protocol (UCA2 or IEC61850).
If the relation "secondary input wired on" is linked, then the relation "primary input wired on" must be
linked too.

146/182
Energy Automation
21062 / DatapointServer / 'primary input' is not wired
MV Datapoint :
If the Acquisition Source is defined on DI channels then the Acquisition Source type is Digital, else it's
Analog. The value (Analog or Digital) of the "type" attribute of the MV Datapoint must be compatible
with the Acquisition Source type.
21070 / DatapointServer / The acquisition source is incompatible with the datapoint type
Example :
21070 / DatapointServer / The acquisition source is incompatible with the datapoint type-> [type,
Analogue]
Several Bit relations are available : "bit wired on", with i [00..63].
Among these relations, values must be contiguous and start from 00.
If some of these relations are defined, then the relation "wired on" is forbidden, and vice versa (these
two types of relations are incompatible acquisition sources).
21051 / DatapointServer / Wired bits are not contiguous
21041 / DatapointServer / Multiple acquisition sources (server, relation)
DPC Datapoint :
If the relation "open wired on" is linked, then the relation "closed wired on" must be linked too, and vice
versa.
21055 / DatapointServer / 'open' is not wired on channel
21054 / DatapointServer / 'closed' is not wired on channel
A "DPC" Datapoint can have up to 2 reIations "has for IED address". In the case of 2 relations, they
are considered as only 1 Control Source definition.
When a DPC is wired on DO channels, all concerned channels must belong to the same board.
<21158> / DatapointServer / 'open' and 'closed' are not wired on the same board
If the relation "open wired on" is double-linked, then the relation "closed wired on" must be double-
linked too, and vice versa.
<21137> / DatapointServer / 'open' is not double-wired on DO channels
<21138> / DatapointServer / 'closed' is not double-wired on DO channels
SPS Datapoint :

147/182
Energy Automation
DPS Datapoint :
If the relation "open wired on" is linked, then the relation "closed wired on" must be linked too, and vice
versa.
21055 / DatapointServer / 'open' is not wired on channel
21054 / DatapointServer / 'closed' is not wired on channel
If the relation "has open state given by" is linked, then the relation "has closed state given by" must be
linked too, and vice versa. The two links must be different.
21057 / DatapointServer / 'open' state is missing
21056 / DatapointServer / 'closed' state is missing
21058 / DatapointServer / 'open' and 'closed' states are linked to the same datapoint
A "DPS" Datapoint can have up to 2 reIations "has for IED address". In the case of 2 relations, they
are considered as only 1 Acquisition Source definition.
MPS Datapoint :
Several State relations are available : "state wired on", with i [00..15].
21052 / DatapointServer / Wired states are not contiguous
Setpoint Datapoint :
Several Bit relations are available : "bit wired on", with i [00..47].
21051 / DatapointServer / Wired bits are not contiguous
If the Acquisition Source is defined on DI channels then the Acquisition Source type is Digital, else it's
Analog. The value (Analog or Digital) of the "type" attribute of the Setpoint Datapoint must be
compatible with the Acquisition Source type.

148/182
Energy Automation
21070 / DatapointServer / The acquisition source is incompatible with the datapoint type
Example :
21070 / DatapointServer / The acquisition source is incompatible with the datapoint type-> [type,
Analogue]
LSP Datapoint :
For LSP datapoint, the server datapoint must be the same than the FLS server defined at site level by
relation Has for FLS server.
21045 / DatapointServer / The relation link is not compatible with the datapoint server
2.4.3 Client / Server definition
For a Datapoint, the Server and Clients identification is based on general rules (see 2.4.3.1 General
definitions) which can be overwritten by specific rules depending of the Datapoint type (see 2.4.3.2
Detailed definitions).
These definitions are based on the SCE Data Design.
2.4.3.1 General definitions
For a Datapoint, 1, and only 1, Server device must be defined.
21047 / DatapointServer / The server is missing

21040 / DatapointServer / The server is not unique (server, relation)
Example :
21040 / DatapointServer / The server is not unique (server, relation)-> [Scs | Ethernet network |
C264, has for IED address : DPC addr. on IED]
Special case :
Substation (R) is managed by C264

Voltage level C26x UCA2/IEC Map.

Feeder UCA2/IEC@
Dpt (1)
Dpt (2) (R) has for UCA2/IEC address
For a Datapoint having no Server explicitly defined, then :

- if the Datapoint is located under a Bay, the device managing the Bay is automatically considered as
the Server ("is managed by" relation link).
- if the Datapoint is located above a Bay, the device managing the associated voltage level,
substation or site (via has for default server relation set at the corresponding level) is automatically
considered as the Server except if it has an UCA2/IEC address on a specific server.
A device is Client of a Datapoint, if, and only if, it's not Server of this Datapoint.

149/182
Energy Automation

Datapoint
Client Server

Device A Device B
A Datapoint must be linked to an address, in the mapping of its Server device, with the "has for
UCA2 address" or "has for IEC address" relation.
This, if :
- the Datapoint has at least 1 Client device
- the relation is available for the Datapoint type (ie, it's defined by the Structural Database rules).
A device, Client of a Datapoint, must be linked to the Server of the Datapoint through the "has for
UCA2/IEC server" relation.
21046 / DatapointServer / The datapoint is not linked to an address of the server (server)
22048 / DatapointClient / The client-server relation is missing (server, client)
Example :
21046 / DatapointServer / The datapoint is not linked to an address of the server (server)-> [Scs |
Ethernet network | C264]
22048 / DatapointClient / The client-server relation is missing (server, client)-> [Scs | Ethernet
network | C264, Scs | Ethernet network | OI server]
2.4.3.2 Detailed definitions
2.4.3.2.1 Computer
2.4.3.2.1.1 System Datapoints :
C264
System infos
SystDpt
Board
System infos
SystDpt
SCADA Networks
C26X SCADA prot
System infos
SystDpt
Legacy Networks
Leg_Network
IED
System infos
SystDpt

150/182
Energy Automation
The Computer "C264" is Server of each System Datapoint "SystDpt".
2.4.3.2.1.2 Acquisition/Control Sources :

C264
DIU200
(R) wired on
Dpt (1) DI # 0
(R) is computed by TIU200
Dpt (2)
DNP3 master
DNP3_IED
Dpt (3)
IED_@
The Computer "C264" is Server of each Datapoint "Dpt(1)", "Dpt(2)", "Dpt(3)".
2.4.3.2.1.3 SCADA address :

C264
C26X SCADA prot
Gtw SCADA Map.
Dpt GtwSCADA@
The Computer "C264" is Client of the Datapoint "Dpt".
Moreover, a C264 which supports gateway function must receive information through reports : it
cannot have a relation "goose only" with other C264 which provides it these information.
22193 / DatapointClient / The report usage for client-server relation is missing for gateway or
grouping at client level (server, client)
2.4.3.2.1.4 FBD automation :
C264
(R) runs on
FBD automation PLC
Input (R) uses

DPS | SPS | MPS | MV | DPC | SPC (1)
Output (1) (R) controls
DPC | SPC (2)
Output (2) (R) produces
SPS (3)
The Computer "C264" is Client of the used Datapoints (1).

The Computer "C264" is Server of the controlled Datapoints (2).
The Computer "C264" is Server of the produced Datapoint (3)".
2.4.3.2.1.5 Slow automation :

151/182
Energy Automation
C264
(R) runs on PLC
Slow automation
(R) is client of
UserFunction Dpt (3)
DPC | DPS | SPC | SPS | MPS | MV | Setpoint | Counter (1)
(R) manages
DPC | DPS | SPC | SPS | MPS | MV | Setpoint | Counter (2)
The Computer "C264" is Server of the "Slow automation" Datapoints (3) and of the managed
Datapoints (2).
The Computer "C264" is Client of the used Datapoints (1).
2.4.3.2.1.6 Bay Built-in functions :
(R) is managed by C264

Feeder
Autorecloser
(R) is autorecloser of
AR_Dpts
Ext auto CS
Accept forcing
Ext manual CS
Accept forcing
Int synchrocheck
IS_Dpts
Circuit breaker (1)

Circuit breaker (2)
Circuit breaker (3)
Circuit breaker (4)
The Computer "C264" is the manager of the Bay containing the Circuit-breakers, therefore it's the
Server of the Datapoints belonging to each Built-in function : "Autorecloser", "Ext auto CS", "Ext
manual CS" and "Int synchrocheck".
If, for a Built-in function Datapoint, another Server is explicitly defined, then the Computer "C264" is
Client of this Datapoint.
2.4.3.2.1.7 Substation Built-in function :
Substation (R) is synchrocheck of

Ext manual CS
Accept forcing
(R) is managed by
(R) is synchrocheck of C264 (1)
Voltage level
(R) is managed by
Feeder C264 (2)
Circuit breaker (1)
Circuit breaker (2)

152/182
Energy Automation
The Computer "C264(1)" is the manager of the Built-in function "Ext manual CS", therefore it's the
Server of the Datapoints belonging to this Built-in function.
The Computer "C264(2)" is the manager of the Bay containing the Circuit-breakers, therefore it's the
Client of the Datapoints belonging to the Built-in function "Ext manual CS".
2.4.3.2.1.8 DPS-SPS association :
(R) has 'closed' state given by Server

DPS SPS (1) C264
(R) has 'open' state given by Server
SPS (2)
The Computer "C264" is the Server of "SPS(1)" and "SPS(2)" Datapoints, therefore it's also the
Server of the "DPS" Datapoint.
For this, both "SPS(1)" and "SPS(2)" Datapoints must have the same Server device.
21040 / DatapointServer / The server is not unique (server, relation)
Examples (from the DPS point of vue) :

21040 / DatapointServer / The server is not unique (server, relation)-> [Scs | Ethernet network | C264,
has 'closed' state given by : SPS(1)]
21040 / DatapointServer / The server is not unique (server, relation)-> [Scs | Ethernet network |
C264(2), has 'open' state given by : VoltageLevel SPS(2)]
2.4.3.2.1.9 Group SPS :
(R) is managed by
Feeder C264
Group SPS (R) contains the SPS
(R) contains the DPS SPS
DPS
The Computer "C264" is the Server of the "Group SPS" Datapoint,

and it's Client of the two Datapoints "SPS" and "DPS".
Moreover, a C264 which supports grouping function with inputs from other computers must receive
these inputs through reports : it cannot have a relation "goose only" with other C264 which provides it
these information.
22193 / DatapointClient / The report usage for client-server relation is missing for gateway or
grouping at client level (server, client)
2.4.3.2.1.10 State Change :
(R) controls on state change Server

SPS SPC C264
(R) controls on state change
DPS DPC

153/182
Energy Automation
A "SPS" (or "DPS") Datapoint can be linked to a "SPC" (or "DPC") Datapoints through relations
"controls on state change".
The Server of the "SPC" (or "DPC") Datapoint is Client of the "SPS" (or "DPS") Datapoint.
An xPC must be controlled only one time by same xPS

15248 / RelationControlsOnStateChange / The xPC is controlled by an xPS more than one time
(mutliple link with same xPS) (linked xPS)
A controlled xPC by an xPS can not be mapped on legacy IED

15044 / RelationControlsOnStateChange / Therelation types are not compatible [is control on
state change of, has for IED address]
A controlled xPC by an xPS must be wired

15305 / RelationControlsOnStateChange / The use of a relation 'controls on state change' for xPC
not wired is not authorized.
A controlled xPC by an xPS must have its profile to 'Direct Execute' when the control sequence is
activated
15335 / DirectExecuteInControlMode / The xPC profile must be to 'Direct Execute' if this one is
controlled by an xPS state change with the control sequence activated (xPC)
A controlled xPC by an xPS must have the same server than the xPS when the control sequence is
activated
15336 / SameServerInControlMode / The xPC and the xPS must have the same server if the xPC
is controlled by an xPS state change with the control sequence activated (xPS server, xPC server)
2.4.3.2.1.11Auto/Manu dependency :
C264
Server
(R) has for AutoManu dependency SPS

SPC
(R) has for AutoManu dependency
DPC DPS
A "SPC" (or "DPC") Datapoint can be linked to a "SPS" (or "DPS") Datapoint through relation the "has
for AutoManu dependency".
The Server of the "SPC" Datapoint is Client of the "SPS" and "DPS" Datapoints.
2.4.3.2.1.12 Order running :

154/182
Energy Automation
(A) default uniqueness

Substation Substation level
Voltage level (R) is managed by
Feeder C264
Order running SPS
The Computer "C264" is the Server of the "Order running" SPS Datapoint.
If the attribute "default uniqueness" of the "Substation" is set to the "Substation level" value, then all
the computers are Clients of the "Order running" SPS Datapoint.
2.4.3.2.1.13 ATCC function :
Note :
hereafter, the term "wired" for a Datapoint means that the Datapoint has one of the following relations :
"wired on", "has for IED address", or "has for UCA2/IEC address" to an UCA2/IEC generic IED.
Main ATCC :
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
The Computer "C264(1)", managing the main "ATCC", is the Server of all the Datapoints of this latter
("ATCC_Dpts").
BusBar ATCC function :
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
(R) is managed by C264 (2)
BusBar (Bay)
ATCC fct needs
ATCC inhibited
ATCC inv module
ATCC inv voltage
ATCC max transfo
ATCC on/off
ATCC on/off ctrl
ATCC targ 1 ctrl
ATCC targ 2 ctrl
ATCC targ 3 ctrl
ATCC targ 4 ctrl
ATCC targ 5 ctrl
ATCC target 1
ATCC target 2
ATCC target 3
ATCC target 4
ATCC target 5
ATCC to target
BusBar voltage
In the case of all the Datapoints of the "ATCC fct needs", except the "BusBar voltage" Datapoint :

155/182
Energy Automation
they cannot be wired. As a result, the computer "C264(1)", managing the main "ATCC", is their
Server.
In the case of the "BusBar voltage" Datapoint :

if it's not wired then, the computer "C264(1)", managing the main "ATCC", is its Server.
if it's wired then, the computer "C264(2)", managing the BusBar bay, is its Server and the
computer "C264(1)", managing the main "ATCC", is its Client.
Transformer ATCC function :
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
Voltage level (R) is managed by C264 (2)

Transformer
transformer
ATCC fct needs
ATCC disc eqpt
ATCC homing
ATCC hunting
ATCC inv voltage
ATCC local bay
ATCC low-voltage
ATCC on/off
ATCC overcurrent
ATCC overvoltage
MCB trip
Run away
Second. active P
Second. current
Second. react. Q
Second. voltage
TAP bad TCIP
TAP invalid
TAP long TCIP
In the case of all the Datapoints of the "ATCC fct needs", except the "Run away", "Second. active P",
"Second. current", "Second. react. Q", "Second. voltage" Datapoints :
they cannot be wired. As a result, the computer "C264(1)", managing the main "ATCC", is their
Server.
In the case of the "Run away" Datapoint :

it cannot be wired. But, the computer "C264(2)", managing the Transformer bay, is its Server and
the computer "C264(1)", managing the main "ATCC", is its Client.
In the case of the "Second. active P", "Second. current", "Second. react. Q", "Second. voltage"
Datapoints :
they can be wired or not. If wired, the computer "C264(2)", managing the Transformer bay, is their
Server and the computer "C264(1)", managing the main "ATCC", is their Client. If not wired, the
computer "C264(1)" managing the main "ATCC", is their Server.

156/182
Energy Automation
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
Voltage level (R) is managed by C264 (2)

Transformer
transformer
ATCC fct needs
ATCC on/off
Tap changer (R) has for AutoManu dependency

Raise/lower DPC
MCB position DPS

MCB position SPS
Case of the "Raise/lower DPC" Datapoint :

if it's present then, the "ATCC on/off" Datapoint must be linked to it through the relation "has for
AutoManu dependency".
26031 / ATCC / The link to AutoMany dependency is missing
Case of "MCB position DPS" and "MCB position SPS" Datapoints :

they are mutually exclusive.
they must be wired.
The computer "C264(2)", managing the Transformer bay, is their Server and the computer
"C264(1)", managing the main "ATCC", is their Client.
26066 / ATCC / The datapoints are not compatible-> [MCB position DPS, MCB position SPS]
21042 / DatapointServer / The acquisition source is missing
UCA2/IEC servers :
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
(R) is managed by C264 (2) (R) has for UCA2/IEC server
BusBar (Bay)
ATCC fct needs
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
Voltage level (R) is managed by C264 (2) (R) has for UCA2/IEC server
Transformer
transformer
ATCC fct needs
The computer "C264(2)", managing the BusBar or Transformer bay, must be linked to the computer
"C264(1)", managing the main "ATCC", through the relation "has for UCA2/IEC server". Moreover, the
link must at least use report mode.

157/182
Energy Automation
22048 / DatapointClient / The client-server relation is missing (server, client)-> [Scs | Ethernet
network | C264(1), Scs | Ethernet network | C264(2)]
22192 / DatapointClient / The report usage for client-server relation is missing for ATCC at client
level (server, client)
2.4.3.2.1.14 LHMI :
Graphic (R) has for workspace C264

Comp. workspace GHU200
(R) represents (R) is managed by
Bay mimic Feeder
LHMI Gen module

LHMI xPS MultiSt (R) visualizes
MV
LHMI Transformer
LHMI TPI MultiSt (R) is managed by
SPS
DPS
(R) is managed by
transformer
Tap changer
Tap pos ind
The Computer "C264" is the Server of the Datapoints : "MV", "SPS or DPS", "Tap pos ind".
2.4.3.2.1.15 Local/Remote :
Substation
Server
Local/remote DPS C264
Loc/rem ctrl DPC
If the two Datapoints "Local/remote DPS" and "Loc/rem ctrl DPC" are present, they must have the
same Server device.
24063 / Datapoint_LocalRemote / The Local/Remote datapoints have not the same server
(servers)
If a Module SPC or DPC depends on a bay managed by a computer, the existence of Local/remote
DPS under this bay is mandatory
24390 / Datapoint_LocalRemote / This composant needs Local/remote DPS
If a Module SPC or DPC depends on a bay managed by a gateway, it cant use the bay mode
dependency
24414 / Datapoint_LocalRemote / This composant can't use the bay mode dependency because it
is under a bay managed by a gateway

158/182
Energy Automation
2.4.3.2.1.16 Taking-Control function :
Substation
Server
Local/remote DPS C264 (1)
Loc/rem ctrl DPC
(R) is taken control of C264 (2)

Taking Status (SPS) C26X SCADA prot
Taking Control (SPC)
C264 (3)
(R) is taken control of C26X SCADA prot
Taking Status (SPS)
Taking Control (SPC)
If a Taking-Control function is defined then, the "Loc/rem ctrl DPC" must be present.
52089 / TakingControl / The datapoint is missing-> [Loc/rem ctrl DPC]
The Server of the Local/Remote Datapoints ("C264(1)") is the Server of each Datapoints couple
"Taking Status" / "Taking Control".
All the devices ("C264(2), C264(3)") having a SCADA network linked to a Taking-Control function are :
- Clients of each Datapoints couple "Taking Status" / "Taking Control".
- Clients of the Datapoints couple "Local/remote DPS" / "Loc/rem ctrl DPC".
2.4.3.2.2 OI server
OI server
System infos
SystDpt
OI printer
System infos
SystDpt
The "OI server" is Server of each System Datapoint "SystDpt".
2.4.3.2.2.2 Alarmed Datapoints :
(R) has for profile Scs (A) Alarms / defined

Dpt Dpt profile Yes
All the "OI server" devices (except backups and datapoints which are not auto-addressed) are Clients
of each Alarmed Datapoint.

159/182
Energy Automation
2.4.3.2.2.3 Logged Datapoints :

Scs
Ethernet network
(R) has for profile Scs (R) has events logged on OI server
Dpt Dpt profile OI printer
(R) has alarm events logged
on
The "OI server" is Client of the Datapoint "Dpt", except datapoints which are not auto-addressed.
2.4.3.2.2.4 Mean value computation Datapoint :
(R) has for profile Scs (A) Mean value / computation

MV MVProfile Yes
(R) has for profile (A) Mean value / computation
Counter CounterProfile Yes
of each Datapoint having a Mean Value computation.
2.4.3.2.2.5 Archived Datapoint :
(R) has for profile Scs (A) State treatment / treatment on event
Dpt Dpt profile - Archive and logging
- Archive only
of each archived Datapoint.
2.4.3.2.2.6 Datapoint used by a graphic animation :
(R) is workspace of (R) has for HMI server

OI workspace OI client OI server
Window
Mimic
Var. text (R) is graphically used by
Dpt
(R) manages
DPS MultiState DPS (1)
(R) manages
Discrepancy MS DPS (2)
Circle (shape) (R) is controlled by

Open Ctrl popup DPC
(R) is controlled by
Send order SPC
Open cnt popup (R) is controlled by
Counter
Send value (R) is controlled by SetPoint
The "OI server" is Client of all the Datapoints used by a graphical animation.

160/182
Energy Automation
2.4.3.2.2.7 Datapoint used by Alarm Group :
Graphic
(R) is used by
Alarm group Dpt
All the "OI server" devices (except backups) are Clients of each Datapoint used by an "Alarm group".
2.4.3.2.3 OI client
(R) has for HMI server

OI client OI server
System infos
OI client link
The "OI server" is Server of the System Datapoint "OI client link" of the "OI client".
2.4.3.2.4 OI Bay
An OI bay cant be clients of more than 500 datapoints.
02256 / OI Bay / An OI bay cant be clients of more than 500 datapoints (current number of
datapoints)
2.4.3.2.5 UCA2/IEC generic IED
UCA2/IEC gen IED
System infos
SystDpt
The "UCA2/IEC gen IED" is Server of each System Datapoint "SystDpt".
2.4.3.2.5.2 UCA2/IEC addressed Datapoint :

161/182
Energy Automation
UCA2/IEC gen IED

UCA2/IEC IED Map.
UCA2/IEC@ Dpt
The "UCA2/IEC gen IED" is Server of each Datapoint linked to an UCA2/IEC address of its mapping.
2.4.3.2.6 UCA2/IEC Gateway
UCA2/IEC gateway
System infos
SystDpt
Usual protocol
System infos
SystDpt
The "UCA2/IEC gateway" is Server of each System Datapoint "SystDpt".
2.4.3.2.6.2 SCADA addressed Datapoint :
UCA2/IEC gateway
Usual protocol
Gtw SCADA Map.

SCADA@ Dpt
The "UCA2/IEC gateway" is Client of each Datapoint linked to a SCADA address of its mapping.
2.4.3.2.6.3 IEC61850 addressed Datapoint :
UCA2/IEC gateway
(R) is transmitted on IEC 61850
61850 protocol Dpt
The "UCA2/IEC gateway" is Client of each Datapoint transmitted to a 61850 protocol.
2.4.3.2.7 OI Bay
The maximum number of data points displayed on OI panel must be lower or equals to 500.

162/182
Energy Automation
02256 / OI Bay / Number of data points displayed on OI panel is greater than maximum value
(maximum value, current value)
The Klaxon usage value on a Standard Command Banner of an OI Bay must be set to No,
because OI bay doesnt manage Klaxon option.
76255 / OI Bay Klaxon usage value on Standard Command Banner of an OI Bay must be set to
No (OI bay),
The alarm group used in a Mimic of an OI bay must have at least one datapoint client of this OI
Panel.
(R) has for workspace

OI bay OI Workspace
Mimic
Clients of (example alarmed)

MultiState
(R) Manages
Graphic
(R) uses
76264/ OI Bay / Alarm group used by the OI bay must have at least one datapoint client of OI bay-
> [Graphic | ALR.GRP.NOT.OI],
2.4.4 Datapoints constraints
2.4.4.1 MV Datapoints sent on 'set' or 'close' state
(R) is sent on set state of

MV SPS
(R) is sent on closed state of
DPS
The two relations "is sent on set state of" and "is sent on closed state of" are mutually exclusive.
28069 / RelationSentOnSetOrClosedState / The relations, sent on 'set' and 'closed' states, are
exclusive

163/182
Energy Automation
2.4.4.2 MV Datapoints digital acquisition
(A) type Digital

MV
(A) Digital acquisition / validation delay
50
(A) Digital acquisition / stabilization delay 10
If the attribute "type" of the "MV" Datapoint is set to a "Digital" value, then the following constraint
beetween the two attributes must be respected :
"validation delay" 5 "stabilization delay"
51081 / MV_Acquisition / validation delay (x 10 ms) is not greater than 5 * stabilization delay (x 10
ms)
Moreover, avoid to use a cyclic transmission for digital measurement:

57256 / MVDatapoint / Avoid cyclic transmission for digital measurement
2.4.4.3 MV Datapoints value features and scaling checks
A MV datapoint must be configured for its value features and scaling.
The maximum value must be strictly greater than the minimum value (value features tab):
57235 / MVDatapoint /The max value of a MV must be strictly greater than the min value (min
value, max value)
Examples :
57235 / MVDatapoint /The max value of a MV must be strictly greater than the min value (min value,
max value) -> [0.0, 0.0]
The maximum acquisition value must be strictly greater than the minimum acquisition value
(scaling tab):
57236 / MVDatapoint / The max acquisition value of a MV must be strictly greater than the min
acquisition value (min value, max value)
Examples :
57236 / MVDatapoint / The max acquisition value of a MV must be strictly greater than the min
acquisition value (min value, max value) -> [120.0, 50.0]
The threshold configuration must follow some rules (value features tab):
Considering computed value diff with following formula

Diff = ( ( maximum value - minimum value ) * hysteresis ) / 100
and considering low threshold as L, LL and LLL and high threshold as H, HH, HHH

164/182
Energy Automation
1) For configured threshold, each threshold must be greater than previous one
(HHH>HH>H>L>LL>LLL)
2) all configured H thresholds must be greater than previous configured one by at least diff
(HHH>HH+diff and HH>H+diff)
3) all configured L thresholds must be greater than previous configured one by at least diff
(L>LL+diff and LL>LLL+diff)
4) first configured H threshold must be greater than last configured L threshold by at least diff * 2
(H>L+diff*2 or HH>L+diff*2 etc.)
57237 / MVDatapoint / Threshold must be greater than previous configured one with at least given
difference (threshold, current value, previous value, difference)
Examples :
57237 / MVDatapoint / Threshold must be greater than previous configured one with at least given
difference (threshold, current value, previous value, difference)-> [low-low threshold, 50.0, 30.0, 25.0]
Dead Band value Constraints
For a MV the dead band value can be equals to zero only for MV issued from T103 IED with ASDU
value equals to 4. (MV of tap position and MV Main Internal Status are excluded from this check).
57266 / MVDatapoint / Only MV issue from IEC 103 IED with ASDU number equals to 4 can
have a deadband value equals to 0.
A MV datapoint is not logged and archived, then the archive trend viewer of the OI will not display
anything.
57360 / MVDatapoint / A MV datapoint linked to a Trend Viewer is not archived
When an operating MV is sent on a SCADA (has a link has for scada address), there is a loss of
accuracy due to the data format conversion.
57388 / MVDatapoint / Operating MV values sent by the IED should be converted into float. Values
bigger than 0x00FFFFFF will have a loss of accuracy
57327 / MVDatapoint / MV mapped on INC/INS cant be transmit on SCADA network
2.4.4.4 Integer MV for FLS
MV datapoint mapped on INS IEC address must be managed only by non PACiS IED.

165/182
Energy Automation
57351 / MVDatapoint / Only non PACiS IED can managed FLS integer MV ( server path )
Only OI server, SUI server and Gateway can be client of MV datapoint mapped on INS IEC address.
57352 / MVDatapoint / Only OI server, SUI server and Gateway can be client of FLS integer MV
(list of clients)
MV datapoint mapped on INS IEC address must not be used into Trendviewer
57353 / MVDatapoint / FLS integer MV can't be used into TrendViewver
MV datapoint mapped on INS IEC address must not be alarmed, archive or logged
57354 / MVDatapoint / FLS integer MV can't be archived or logged

57355 / MVDatapoint / FLS integer MV can't be alarmed
2.4.4.5 SetPoint datapoint mapped on INC_DIR
2.4.4.5.1 Integer SetPoint for FLS
SetPoint datapoint mapped on INC_DIR IEC address must be managed only by non PACiS
IED or Gateway.
94375 / SetPointDatapoint / Only non PACiS IED and Gateway can managed FLS integer SetPoint
(server path)
Only OI server and SUI server can be client of SetPoint datapoint mapped on INC_DIR IEC
address.
94376 / SetPointDatapoint / Only OI server and SUI server can be client of FLS integer SetPoint
(list of clients)
SetPoint datapoint mapped on INC_DIR IEC address must not be alarmed, archive or logged
94377 / SetPointDatapoint / FLS integer SetPoint can't be archived or logged

94378 / SetPointDatapoint / FLS integer SetPoint can't be alarmed
2.4.4.6 Restrictions Value
A Setpoint must not have this minimum feature value greater than this maximum feature value
94401 / SetPointDatapoint / Setpoint minimum feature value must be stricly lower than the
setpoint maximum feature value

166/182
Energy Automation
A Gateway scada address with format set to Adjusted or Normalised, which is linked to a Setpoint,
must not have this minimum feature value greater than this maximum feature value
94402 / SetPointDatapoint / Minimum value must be stricly lower than the setpoint maximum value
2.4.4.7 DPC and DPS Datapoints linked to IED addresses
2.4.4.8 DPC and DPS Datapoints linked to IED addresses
C264
DNP3 master
DNP3_IED
IED Mapping
(R) has for IED address (A) contact type
DPC IED_@ (1) - Unused
(R) has for IED address IED_@ (2) - open
- close
(R) has for IED address
DPS IED_@ (3)
A "DPC" or "DPS" Datapoint can have 1 or 2 relation(s) "has for IED address".
In the case of 1 IED address :

the attribute "contact type" of the IED address must be set to the "Unused" value.
In the case of 2 IED addresses :

the attribute "contact type" of one of the IED addresses must be set to the "open" value, and the
attribute "contact type" of the other IED address must be set to the "close" value.
18134 / xxxAddressOnIED / The attribute value of the referenced IED address is not valid
Examples :
18134 / xxxAddressOnIED / The attribute value of the referenced IED address is not valid-> [Scs |
Ethernet network | C264 | DNP3 master | DNP3_IED | IED Mapping | IED DPC Mapping | DPC
addr. on IED | contact type, Unused]
2.4.4.9 DPC/SPC Datapoints linked to Output plugs of Fast/FBD automations
Fast/FBD automation
(R) controls DPC
Output (1) DPC
(R) controls SPC SPC
Output (2)
A "DPC" or "SPC" Datapoint can be linked to an Output plug of a Fast (or FBD) Automation through
the relation "controls DPC" or "controls SPC".
These relations are not compatible with the following ones :
- relations defining the Control Source, except the "wired on" relation(s)

167/182
Energy Automation
- 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".
39044 / DatapointServer / The relation types are not compatible
Examples :
39044 / DatapointServer / The relation types are not compatible-> [is controlled by : Output, has for
UCA2 address : GenDCO]
SCADA address : Gtw DPC addr.]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by : FBD output, is
controlled on state change of : Substation DPS]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by : FBD output,
has for AutoManu dependency : Substation DPS]
has for feedback : Substation DPS]
has for local/remote dependency : Local/remote DPS]
2.4.4.10 DPC/SPC Datapoints linked to Input plugs of FBD automations
FBD automation
(R) uses DPC
Input (1) DPC
(R) uses SPC SPC
Input (2)
A "DPC" or "SPC" Datapoint can be linked to an Input plug of a FBD Automation through the relation
"uses DPC" or "uses SPC".
These relations are not compatible with the following ones :
- relations defining the Control Source : "wired on"
- relation defining the Control Source : "has for IED address"
39044 / DatapointServer / The relation types are not compatible
Examples :
39044 / DatapointServer / The relation types are not compatible-> [is used by : FBD input, 'open'
wired on : DO # 1 (NO)]

168/182
Energy Automation
39044 / DatapointServer / The relation types are not compatible-> [is used by : FBD input, 'closed'
wired on : DO # 0 (NO)]
39044 / DatapointServer / The relation types are not compatible-> [is used by : FBD input, has for
2.4.4.11 Relation "has for feedback"
DPC DPS
SPS
SPC DPS
SPS
SetPoint MV
(R) has for feedback MPS
For each "DPC", "SPC" or "Setpoint" Datapoint, 2 relations "has for feedback" are available, but they
are mutually exclusive.
14023 / RelationHasForFeedback / Multiple links to feedbacks
An xPC can not have a transient feedback

14278 / RelationHasForFeedback / the xPC can not have a transient feedback
A MV datapoint that is a feedback of a SetPoint can not have a profile with FSSEnable set to true.
14294 /RelationHasForFeedback / The MV feedback of a SetPoint can not have a FSS profile
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 should be "Wired" too.
- 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.
This rule does not concerned the Computed Switch Pos datapoint of a circuit breaker when it is
feedback of a wired SPC/DPC control of a breaker.
Note :
Here, the term "Wired" means that the datapoint is linked to a digital or analog channel of a computer,
or linked to an IED address, else it's "System".
14224 / RelationHasForFeedback / The xPS is feedback of several xPC

This rule does not concerned the Computed Switch Pos datapoint of a circuit breaker.
14026 / RelationHasForFeedback / The datapoint and its feedback have not the same server
(servers)
14028 / RelationHasForFeedback / The datapoint and its feedback are not both wired
14027 / RelationHasForFeedback / The datapoint and its feedback are not both system
14029 / RelationHasForFeedback / The datapoint and its feedback are not both linked to an
address of a Generic IED

169/182
Energy Automation
Case of the Circuit-breaker "Lock control SPC" Datapoint :
Feeder
Circuit breaker
Lock control SPC DPS
(R) has for feedback SPS
1 relation "has for feedback" is mandatory.

Case of the Synchrocheck On/Off Command Datapoints :
Substation
Ext manual CS (R) has for feedback
(R) has for feedback on/off ctrl DPC
on/off ctrl SPC
on/off DPS
on/off SPS
Feeder
Ext manual CS (R) has for feedback
on/off ctrl SPC
on/off DPS
on/off SPS
Ext auto CS (R) has for feedback

on/off ctrl SPC
on/off DPS
on/off SPS
Int synchrocheck (R) has for feedback

on/off ctrl SPC
on/off SPS
If the "on/off ctrl DPC" or "on/off ctrl SPC" Datapoint of a Synchrocheck function is linked to a feedback
through the relation "has for feedback", then the feedback must be the "on/off DPS" or "on/off SPS"
Datapoint of the same Synchrocheck function.
14050 / RelationHasForFeedback / The relation link is not valid
Feedback execution timeout :
(A) activation mode

DPC Transient
(A) close duration
500
(A) open duration 500

DPS
SPS
(A) execution timeout 200

170/182
Energy Automation
For a "DPC" Datapoint, if its attribute "activation mode" is set to the "Transient" value, then the
following rule must be respected :
"execution timeout" > max [ "open duration" , "close duration" ]
14024 / RelationHasForFeedback / The feedback execution timeout (x ms) is lower than the max[
open duration (ms), close duration (ms) ]-> [200, 500, 500]
(A) activation mode

SPC Transient
(A) order on duration
500
DPS
SPS
(A) execution timeout 200
For a "SPC" Datapoint, if its attribute "activation mode" is set to the "Transient" value, then the
following rule must be respected :
"execution timeout" > "order on duration"
14025 / RelationHasForFeedback / The feedback execution timeout (ms) is lower than the order
on duration (ms)-> [200, 500]
14166 / RelationHasForFeedback / A computed MV can't be the feedback of a SetPoint.
2.4.4.12 Relation "has for AutoManu dependency"
DPC DPS
SPS
SPC DPS
SPS
SetPoint DPS
(R) has for AutoManu dependency SPS
For each "DPC", "SPC" or "Setpoint" Datapoint, 2 relations "has for AutoManu dependency" are
available, but they are mutually exclusive.
16032 / RelationHasForAutoManuDependency / Multiple links to AutoMany dependencies
Case of the "Raise/lower DPC" Datapoint :
refer to 2.4.3.2.1 Computer - ATCC function.
2.4.4.13 Local/Remote Datapoints
Substation Mode Datapoints:


171/182
Energy Automation
Substation
Local/remote DPS
Loc/rem ctrl DPC
Operating Mode MPS
Note :
Hereafter, the term "wired" means that the datapoint must be linked to a digital channel of a 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.
24089 / Datapoint_LocalRemote / The datapoint is missing-> [Local/remote DPS]

Except on a Bay managed by an IED Gateway.
24089 / Datapoint_LocalRemote / The datapoint is missing-> [Loc/rem ctrl DPC]

24099 / Datapoint_LocalRemote / The datapoint is not wired
A local/remote managed by a gateway can not be wired on a C264 board (acquisition only on
legacy IED or Isagraf)
24410 / Datapoint_LocalRemote / Relation is forbidden on gateway local/remote
A local/remote managed by a C264 can not have following relations:

HasOpenWiredOn
HasClosedWiredOn
ControlsOnStateChange
IsAutoManuDependentFrom
IsMappedOn
HasForStatusLed
24411 / Datapoint_LocalRemote / Gateway C264 local/remote can not be linked on a legacy IED
Local/Remote with IED address must be managed by the same gateway which manages the IED
24405 / Datapoint_LocalRemote / Gateway local/remote with IED address must be managed by

the same gateway which manages the IED
Local/Remote managed by gateway must be acquired on this gateway

172/182
Energy Automation
24412 / Datapoint_LocalRemote / Local/Remote managed by gateway must be either managed by

an RT automation or linked to an IED address
A built-in function of local/remote and a RT automation must be managed by the same gateway
24406 / Datapoint_LocalRemote / The Built-in function and the RT Automation must be managed
by the same gateway
The two datapoints for operating mode of the substation are exclusives (Local/Remote Substation
DPS and Operating mode MPS)
62196 / Operating mode / Datapoints for operating mode are exclusives (Local/Remote Substation
DPS and Operating mode MPS)
Moreover, for any SCADA protocol attached to a substation via a computer or a gateway, the
substation operating mode is mandatory ("Local/remote DPS" or Operating Mode MPS).
62165 / Operating mode / The datapoint is required for SCADA link -> [Local/remote DPS or
Operating mode MPS]
Bay Local/Remote Datapoints :
Feeder
Local/remote DPS
Loc/rem ctrl DPC
Note :
Hereafter, the term "wired" means that the datapoint must be linked to a digital channel of a 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.

24100 / Datapoint_LocalRemote / The datapoint is wired

24099 / Datapoint_LocalRemote / The datapoint is not wired
A database cant contain a local remote managed by a gateway under a built-in function and a local
remote managed by a C264 at same time.
24404 / Datapoint_LocalRemote / A local/remote must be managed by either a gateway or a C264

173/182
Energy Automation
Bay Local/Remote DPS and LHMI :
(R) is managed by
Feeder (1) C264 (A) HMI type
Local/remote DPS GHU200 Simple
(R) is managed by
Feeder (2)
Local/remote DPS
If the "GHU200" board of a 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".
24064 / Datapoint_LocalRemote / The acquisition sources of the Local/remote DPS datapoints are
mismatched for the simple LHMI
Local/Remote dependency :
Substation
Local/remote DPS
Operating mode MPS
Voltage level
Feeder
Local/remote DPS (A) Substation mode dependency
Yes
DPC (A) bay mode dependency Yes
(A) Substation mode dependency

Yes
SPC Yes
(A) bay mode dependency
If, under a Substation, a "DPC" or "SPC" Datapoint has one attribute "Substation mode dependency"
set to "Yes", then the Substation "Local/remote DPS" or operating mode MPS Datapoint must be
present.
There are four substation mode dependency attributes:
- Local substation dependency
- Remote substation dependency
- Mode 2 substation dependency
- Mode 3 substation dependency
These attributes define the command authorizations for SCADA or OI. When a command is refused,
this command is dependent of the substation mode.
62089 / Operating mode / The datapoint is missing-> [Local/remote DPS or Operating mode MPS]
If, under a Bay, a "DPC" or "SPC" Datapoint has its attribute "bay mode dependency" set to "Yes",
then the Bay "Local/remote DPS" Datapoint must be present.

2.4.4.14 SBMC Datapoints

174/182
Energy Automation
Feeder
SBMC SPS
SBMC control SPC
if "SBMC SPS" is present and not wired, then "SBMC control SPC" must be present
if "SBMC control SPC" is present, then "SBMC SPS" must be present
25089 / Datapoint_SBMC / The datapoint is missing-> [SBMC control SPC]

25089 / Datapoint_SBMC / The datapoint is missing-> [SBMC SPS]

SBMC dependency :
Feeder
SBMC SPS
(A) SBMC mode dependency Yes
DPC
(A) SBMC mode dependency
SPC Yes
(R) has for profile (A) SBMC dependant Yes

DPS DPS Profile
(R) has for profile (A) SBMC dependant
SPS SPS Profile Yes
If a "DPC" or "SPC" Datapoint has its attribute "SBMC mode dependency" set to "Yes", then the
"SBMC SPS" Datapoint must be present.
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.
25089 / Datapoint_SBMC / The datapoint is missing-> [SBMC SPS]

2.4.4.15 Datapoints of OI Server Klaxons
OI Server (R) warns audibly

Klaxon VoltageLevel
(R) warns audibly UCA2/IECPhysicalDevice
A "Klaxon" refers to a set of Datapoints. This set contains all the Datapoints which are in the sub-tree
of each "VoltageLevel" and "UCA2/IEC PhysicalDevice" linked to the klaxon through the relation
"warns audibly".
In the set of Datapoints, at least 1 Datapoint must fulfil the following conditions :
- it must be linked to a Datapoint Profile which has its attributes "Alarms / defined" and "Alarms /
audible" set to the "Yes" value.
- the "OI Server" must be its Server or its Client
- it must not be the "Main status MV" System Datapoint of a computer.

175/182
Energy Automation
The sets of Datapoints of each "Klaxon" of an "OI Server" must not share the same Datapoints.
53135 / OIKlaxon / The Klaxon is not associated to audible Datapoints

53136 / OIKlaxon / The Klaxons share the same Datapoints
A given Voltage level or UCA2/IEC PhysicalDevice can not be linked more than once to the same
klaxon.
<53147> / OIKlaxon / The same voltage level is associated more than once to the same klaxon
<53148> / OIKlaxon / The same UCA2/IEC PhysicalDevice is associated more than once to the
same klaxon
2.4.4.16 SPC managing a Klaxon
OI Server (R) is controlled by

Klaxon SPC
(R) has its klaxon controlled by
Computer SPC
The klaxons can be managed by any SPC. These SPC has to be permanent.
<69214> / SPCDatapoint / When an SPC datapoint manages a klaxon, it must be permanent
2.4.4.17 SPC and DPC Datapoints
Any SPC/DPC datapoint defined as permanent until feedback must be linked to an SPS/DPS via a
feedback relation.
<14146> / RelationHasForFeedback / The feedback must be defined for xPC is permanent until
feedback
2.4.4.18 Counter Datapoints

Computer can manage a maximum of 128 counters. For C264-R the maximum number of counter is
128 on main rack and all extensions rack.
02279 / CapacityLimits / Scs | Ethernet network | C264 / Invalid count of counter datapoint for this
computer (max, count)-> [128, 143]
Main rack or standalone can manage up to 8 wired counter, and extension racks up to 16
02291 / CapacityLimits / Invalid count of wired counter datapoint for this computer or rack
(count, maximum)-> [32, 16]
02415 / CapacityLimits / The maximum of serial legacy and serial scada protocol on gateway
count exceeds 20
02412 / CapacityLimits / The maximum of serial scada protocol on gateway count exceeds 4

176/182
Energy Automation
2.4.4.19 Energy Counter Datapoints
Any counter datapoint defined as energy counter (attribute Type is set to Import or Export Energy)
must be linked to an MV via an integration relation and then, a counter which integrates an MV must
be an energy counter.
<56161> / CounterDatapoint / The Energy Counter must integrate an MV

<56162> / CounterDatapoint / An Energy Counter which integrate an MV must be Import or Export
When an MV datapoint is integrated by two energy counters, these two counters must not be of same
type (import or export).
<57163> / MVDatapoint / An integrated MV can't be integrated by two energy counter with same
type (Import or Export)
2.4.4.20 Datapoints linked to SCADA addresses
A datapoint must have only one SCADA address on a same SCADA network.
Exception : the DPS and DPC can have 2 addresses for DNP3 network.
19177 / xxxAddressOnSCADANetwork / The datapoint has two addresses in same SCADA

network [SCADA Network, max address]
A datapoint in substation or voltage level with a SCADA address must have an IEC address
19182 / xxxAddressOnSCADANetwork / A datapoint in substation or voltage level with a SCADA

address must have an IEC address. This case is treated for a user profile type not equals to C264-
STANDALONE.
2.4.4.21 Xps grouping
Any Generic Bay cant contain more than 512 group SPS.
<02179> / CapacityLimits / The maximum number of datapoints in an xPS group is reached

(group, count, maximum)
Any group SPS can't contain more than 8 cascading levels of group SPS.
<02287> / CapacityLimits / Too many cascading levels of group SPS (>8)
Any group SPS can't contain loop with cascading grouping SPS.
<02286> / CapacityLimits / Loop with cascading grouping SPS detected
2.4.4.22 Datapoint profile Order Usage

177/182
Energy Automation
For transient SPC with control popup, the Order off usage must be set to No
This check is not done for specific case of on/off ctrl SPC of an internal manual synchrocheck.
<23183> / DptProfile / A profile of a transient SPC with control popup, must have Order off usage
set to No (SPC)
For SPC datapoint with control popup, both of the order off usage and the order on usage must not
be to No.
<23339> / DptProfile / Datapoint profile link with Open Ctrl Popup cant set both of OrderUsageOn
and OrderUsageOff to No.
2.4.4.23 TM computed by TMU board
On a TMU board, it cant be two TM computed by with same measure type
<57184> / DptMV / Only one measure type is allowed by TMU board (fixed by relation) (measure
type, TMU board)
On a TMU board, in case of Delta topology, the following TM computed by measure type are not
allowed:
- active power phase A, B or C
- reactive power phase A, B or C
- apparent power phase A, B or C
- power factor phase A, B or C
- phase angle phase A, B or C
<57190> / DptMV / The measure type is not allowed for delta topology (measure type, TMU
board)
On a TMU board TMU210 MV data point of type mod Vo (ADC), mod I1 (ADC), mod I2 (ADC), mod
V1 (ADC), mod V2 (ADC), thermal status must not have relation is transmitted on IEC61850 SCADA
network.
<57221> / DptMV / This MV data point type can't be transmitted on IEC 61850 SCADA Network
(MV data point type)
On a TMU210 board if the type of connection equals 3Vpp+Vb, the following TM computed by
measure type are not allowed:
- VAN, RMS value of the voltage phase A
- VBN, RMS value of the voltage phase B
- VCN, RMS value of the voltage phase C
<57230> / DptMV / The measure type is not allowed for the 3Vpp+Vb connection type (measure
type, TMU210 board)
2.4.4.24 Command Panel Assignment
For Raise/Lower DPC, if it is SBO Many, the Command Panel Assignment must be set to No

178/182
Energy Automation
<61185> / DptRaiseLower / A Raise/Lower DPC SBO Many, must have Command Panel
Assignment set to No
2.4.4.25 Datapoint Mapping function
Origin Dpt Target Dpt

(R) is mapped on
SPS MappingSPS
MappingDPS
(R) is mapped on
DPS MappingSPS
MappingDPS
(R) is mapped on
MPS MappingSPS
(R) is mapped on
MV MappingSPS
Any configuration database can't contain more than 100 Mapping Datapoints per computer.
63198 / MaxTargetDpt / The maximum number of Target Datapoints per computer is reached
(count, maximum)
Any Origin Datapoint can't be mapped on more than 10 Target Datapoints.
63199 / MaxTargetDpt / The maximum number of Target Datapoints per Origin datapoint is
reached (count, maximum)
Any Target Datapoint must map one and only one Origin Datapoint.
63200 / UnicityOriginDpt / A MappingxPS datapoint (target) must map one and only one Origin
Datapoint.(count, maximum)
Site
Server
Origin datapoint C264-1
(SPS | DPS | MPS | MV)
Has for Client
(R) IsMappedOn
Mapping datapoint Server C264-2

(SPS | DPS)
If the Server of the Origin Dpt (Example C264-1) is different of the Server of Mapping Dpt (Example
C264-2) then C264-1 has for client C264-2.

179/182
Energy Automation
2.4.4.26 Data point Short Name and Long Name constraints
Datapoint must not has a comma character (,) in Short name or Long name attribute in any
languages.
73229 / Datapoint / Invalid character find in datapoint attribute (Attribute, Invalid character, OI
language)-> [long name, ',', US English]
A check appears if duplicated long and short names in hierarchy when a SUI is present
06392 / AttributeValue / Short names must be unique
06391 / AttributeValue / Long names must be unique
2.4.4.27 Device link datapoint constraint
The device link datapoint of an OI server cant be use in a mimic.
OI Server Mimic
Device link Symbol
Is controled by
Send FSS order
manages
SPS Multistate
manages
Discrepancy MS
Is graphically used by
Var. Text
73238 / Datapoint / Device link datapoint of OI server cant be used in a mimic (graphical element)
73346 / Datapoint | Redundancy mode / The gateway system datapoints or datapoints coming
from SBUS cannot be goosed
2.4.4.28 Switchgear pos. (SPS/DPS) datapoints constraint

180/182
Energy Automation
For datapoint Switchgear pos.(SPS : SwitchPos_SPS, DPS : SwitchPos) must not has relation is
transmitted on IEC61850 SCADA network if they are created under a Circuit breaker (XCBR)
module.
Check Error 73253.

Impossible to have this
relation under this
datapoints under a circuit
breaker module.
Check Error 73253.

relation under this
breaker module.
Check Error 73253.

relation under this
breaker module.
73253 / Datapoint / Relation 'is Transmitted on IEC 61850 SCADA network' is invalid for this
datapoint under circuit breaker module
2.4.4.29 Datapoints transmitted on gateway IEC/IEC
Datapoints can not be transmitted into a report on an upper gateway IEC/IEC. So all relations is
transmitted on scada network linked to an IEC protocol under an upper gateway (represented by a
generic IED) must have modelling/goose usage attribute set to Goose only.
This is done automatically when importing gateway model (ConfigAP file) correctly filled with goose
needs on main gateway (which permits coherency control between configurations), or it can be done
manually.

181/182
Energy Automation
77403 / Gateway / It is not possible to transmit a datapoint into a report to an upper gateway
IEC/IEC, only goose is allowed. Delete/update relation or update gateway model.
It is not possible for a datapoint to be transmitted into a goose to a gateway which has not its Goose
activation flag set to yes.
To see if the flag is activated:
- On the gateway:
- Gateway version must be V5 (no goose in gateway V4)
- Goose activation attribute must be set to Activated
- On generic IED representing gateway into upper conf:
The attribute GSEControl creation (IEC61850 Capabilities tab) must be set to Yes.
NB: the GSEControl creation is not editable by user. It is updated when setting model to generic model
in accordance to main configuration gateway flag.
To correct this error on main gateway, user can:

- delete the relation
- update manually the attribute modelling/goose usage to data model only
- delete the gooses on upper gateway, and then reimport model.
To correct it on upper gateway, delete the lreation as it is no longer possible to transmit datapoint from
upper to main configuration
77402 / Gateway /The datapoint is transmitted into a goose to a gateway IEC/IEC which has not
goose activated.
A datapoint transmitted on an IEC 61850 protocol of a lower gateway IEC/IEC cant be sent in Goose
Only. All datapoints transmitted in goose must be also sent in report.
73420 / Datapoint / A datapoint transmitted on an IEC 61850 network of a lower gateway can't be
sent in goose only.

182/182

Sce 5.14.10#build1 Checks

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sce 5.14.10#build1 Checks

Uploaded by

Copyright:

Available Formats

CONFIDENTIAL. All rights reserved. SCHNEIDER ELECTRIC.

Confidentiality Category Error:

Reference source not

ISSUE DATE AUTHOR REF. COMMENTS

2 24/05/2004 Marinella KHALDY Updates after first Reader/Author cycle.

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 3/182

3 14/06/2004 Marinella KHALDY Updates after second Reader/Author

New checks : Synchrocheck function

Updated checks : FBD automation

Check messages identification with

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 4/182

4 01/09/2004 Christophe THIEBAUT Adding bookmarks in this document.

A 18/08/2005 F VERWEE Deletion of FastAutomation checks

03/10/2005 C BLOCH 42159 / Synchrocheck / The manager

17/11/2005 Luc GRANDGIRARD <13020> / LD name is prefixed by

12/01/2006 F. VERWEE 17167 / LegacyIED / The MPS

CHECKS SPECIFICATION Page: 5/182

17/02/2006 C.BLOCH 58170 / GooseUnicity / Goose ID

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 6/182

12/06/2006 C. BLOCH 23183 / DptProfile / A profile of a

21/08/06 F. VERWEE CRA_319 19189 /

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 7/182

16/11/06 L. GRANDGIRARD FR_4650 27113 / Multiple links : 2.2.2.3.1, only

CHECKS SPECIFICATION Page: 8/182

06/03/2007 F. VERWEE PTR2007 42204 / Synchrocheck / The TMU220

12/04/2007 C. BLOCH FR_5501 Add checks for count of SCADA

24/04/2007 F. VERWEE FR_4862 Add checks for Electre function ARS

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 9/182

27/04/2007 F. VERWEE FR_5335 09197 / ComputerBoards / when

This check is de-acitvated for Poste_d

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 10/182

11/07/2007 G. ESTIMBRE PTR0714 Uses of nMPS in FBD. The nMPS must

MV type name MV type id

mod Vo (ADC) 307

mod I1 (ADC) 308

mod I2 (ADC) 309

mod V1 (ADC) 310

mod V2 (ADC) 311

thermal status 312

<57221> / DptMV / This MV data point

>36223> / WaveRecording / The

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 11/182

31/08/2007 C. BLOCH FR_6258 Add check for template coherency

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 12/182

22/01/2008 C. BLOCH FR 6899 Add check on MV Min/Max value

CHECKS SPECIFICATION Page: 13/182

05/02/2008 C. BLOCH FR6452 Add checks for SNTP server addresses

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 14/182

19/03/2008 G. ESTIMBRE FR7579 Add a check on maximum count of

Add a check on Unicty of IED address

Checks.doc Identification Number: 2070290

CHECKS SPECIFICATION Page: 15/182

16/06/2008 C. THIEBAUT DE 8438 Dont treat checks 08140 and 08141

CHECKS SPECIFICATION Page: 16/182