Professional Documents
Culture Documents
Sce en T D10
Sce en T D10
SCE/EN T/D10
Technical Guide
Technical Guide SCE/EN T/D10
Contents
PACiS System Configuration Editor Page 1/2
PACiS SCE
CONTENTS
BLANK PAGE
Safety & Handling SCE/EN SA/D10
CONTENT
1. INTRODUCTION 3
2. SAFETY 4
2.1 Health and Safety 4
2.2 Explanation of symbols and labels 4
2.3 Installing, Commissioning and Servicing 4
2.4 Decommissioning and Disposal 4
3. GUARANTEES 5
BLANK PAGE
Safety & Handling SCE/EN SA/D10
1. INTRODUCTION
This document is a chapter of PACiS System Configuration Editor PACiS SCE
documentation. It describes the safety, handling, packing and unpacking procedures
applicable to PACiS SCE software tools.
SCE/EN SA/D10 Safety & Handling
2. SAFETY
WARNING: THIS SAFETY SECTION SHOULD BE READ BEFORE COMMENCING
ANY WORK ON THE EQUIPMENT.
2.1 Health and Safety
The information in the Safety Section of the product documentation is intended to ensure
that products are properly installed and handled in order to maintain them in a safe condition.
It is assumed that everyone who will be associated with the equipment will be familiar with
the contents of the Safety Section and all Safety documents related to the PC and
Communication networks.
2.2 Explanation of symbols and labels
The meaning of symbols and labels may be used on the equipment or in the product
documentation, is given below.
2.3 Installing, Commissioning and Servicing
3. GUARANTEES
The media on which you received Schneider Electric software are warranted not to fail
executing programming instructions, due to defects in materials and workmanship, for a
period of 90 days from date of shipment, as evidenced by receipts or other documentation.
Schneider Electric will, at its option, repair or replace software media that do net execute
programming instructions if Schneider Electric receive notice of such defects during the
guaranty period. Schneider Electric does not guaranty that the operation of the software shall
be uninterrupted or error free.
A Return Material Authorisation (RMA) number must be obtained from the factory and clearly
marked on the package before any equipment acceptance for guaranty work.
Schneider Electric will pay the shipping costs of returning to the owner parts, which are
covered by warranty.
Schneider Electric believe that the information in this document is accurate. The document
has been carefully reviewed for technical accuracy. In the event that technical or
typographical errors exist, Schneider Electric reserves the right to make changes to
subsequent editions of this document without prior notice to holders of this edition. The
reader should consult Schneider Electric if errors are suspected. In no event shall
Schneider Electric be liable for any damages arising out of or related to this document or the
information contained in it.
Expect as specified herein, Schneider Electric makes no guaranties, express or implied and
specifically disclaims and guaranties of merchantability or fitness for a particular purpose.
Customer's rights to recover damages caused by fault or negligence on the part
Schneider Electric shall be limited to the amount therefore paid by the customer.
Schneider Electric will not be liable for damages resulting from loss of data, profits, use of
products or incidental or consequential damages even if advised of the possibility thereof.
This limitation of the liability of Schneider Electric will apply regardless of the form of action,
whether in contract or tort, including negligence. Any action against Schneider Electric must
be brought within one year after the cause of action accrues. Schneider Electric shall not be
liable for any delay in performance due to causes beyond its reasonable control.
The warranty provided herein dues net cover damages, defects, malfunctions, or service
failures caused by owner's failure to follow the Schneider Electric installation, operation, or
maintenance instructions; owner's modification of the product; owner's abuse, misuse, or
negligent acts; and power failure or surges, fire, flood, accident, actions of third parties, or
other events outside reasonable control.
SCE/EN SA/D10 Safety & Handling
BLANK PAGE
Introduction SCE/EN IT/D10
INTRODUCTION
Introduction SCE/EN IT/D10
CONTENT
1. INTRODUCTION TO PACiS 3
BLANK PAGE
Introduction SCE/EN IT/D10
1. INTRODUCTION TO PACiS
The PACiS range will continue to be expanded. The general features of PACiS will also be
enhanced, as we are able to adopt new technology solutions.
For up-to-date information on any PACiS product, visit our website:
www.schneider-electric.com
SCE/EN IT/D10 Introduction
• Operation Guide: includes information on the application of the PACiS SCE and a
technical description of its features. It is mainly intended for protection & control
engineers concerned with the selection and application of the PACiS SCE for the
Configuration of PACiS solution or of any of the PACiS equipment.
TECHNICAL DATA
Technical Data SCE/EN TD/D10
CONTENT
2. REQUIREMENTS 4
3. CAPABILITIES 5
SCE/EN TD/D10 Technical Data
BLANK PAGE
Technical Data SCE/EN TD/D10
2. REQUIREMENTS
For the minimum hardware requirements to operate the PACiS SCE application, please refer
to the table that follows:
You can install the SCE on the same PC than has the Operator Interface (OI) and the
System Management Tool (SMT).
Technical Data SCE/EN TD/D10
3. CAPABILITIES
The capabilities of the PACiS SCE application allow you to define the maximum
configuration of a PACiS project. You can find a description of the capacity limits of the
different devices of a PACiS project in the chapter PACiS SCE/EN MF. Please refer to the
topic, Capacity limits.
SCE/EN TD/D10 Technical Data
BLANK PAGE
Functional Description SCE/EN FT/D10
FUNCTIONAL DESCRIPTION
Functional Description SCE/EN FT/D10
CONTENTS
BLANK PAGE
Functional Description SCE/EN FT/D10
• Level 3 users have the capability to modify and create new templates derived from the
existing template libraries. They can generate PACiS application databags but also
template libraries. User of level 3 will be all T&D-EAI PACiS specialists.
• Level 4 users are PACiS SCE experts. They can modify and create the templates
directly from the structural database elements. Their PACIS SCE user level allows
also the management of all template databases and the administration of the
structural database. The level 4 users are the PACiS SCE administrators.
Such categories is only an outline of PACIS SCE users since several of its tools thanks to
specific editors, or report managers, can provided the records needed by other tasks:
commissioning cubicle, mapping extraction, etc.
2.2.2 PACIS SCE Template & Object
A database is basically a collection of persistent data. In the PACIS SCE framework, a
database is a collection of objects. Any object has its specific attributes, organised in
categories and subcategories. The objects are organised in the database by following pre-
defined association rules.
The structural database defines object types and association types. Association types
are hierarchical link types and relation link types between object types. Hierarchical links
are defined for father/child associations. Relation links are defined for other associations,
and may hold attributes. Cardinalities are defined for all associations.
A library database contains templates. A template is a collection of objects/associations
instantiated from the structural database or from others templates.
A configuration database contains objects/associations instantiated from types of the
structural database or from templates. It also contains its own templates, created specifically
for the configuration, or imported from a library database. A configuration database defines
all data needed by system devices to feel up customer application.
All the database elements support internationalisation (multiple languages).
SCE/EN FT/D10 Functional Description
• Import a template from an external library into current database (in its template area)
• Feel up predefined attribute known as degree of freedom (for example the name)
• Attribute input
• Relation creation
• Generation
Configuration database
Instance 1
Instance n
S0126ENa
Interface
PACiS files
Data Model
External
XML files Tools
MiCOM
CAT
C264
SCL files
ISaGRAF
There is no software interfaces between PACiS SCE and other external tools or PACiS
devices.
External interfaces are implemented through files:
• XML files: the user can export / import objects to / from other database.
• SCL files: the user can export or import a whole configuration or only a subset. A
PACiS SCE exchange SCL format is defined for describing files which are:
• Reports: the user selects a whole configuration or only a subset and asks a report. A
predefined report pdf format is delivered with PACiS SCE.
LIMITATION: The PACiS SCE importing of graphical object whose level is lower or
equal to mimic is not supported.
SCE/EN FT/D10 Functional Description
For displaying information it is needed to load a database. After such database load, the
PACIS SCE application looks as below.
• Title Bar
• Menu Bar
• Tool Bar
• Docking Window or common work area composed of several on line optional and
customisable areas.
• State Bar
SCE/EN FT/D10 Functional Description
• Mimic Editor
When selecting object (click, enter) all views are “refreshed” with corresponding data:
• Template Entry List (of existing template of that can be added under selected object
from DB template list)
• Object Entry List (of objects that can be added under selected object from conceptual
modeling)
2.4.3 Management under Windows XP
2.4.3.1 Windowing
The PACIS SCE Application follows windowing behaviour. As presented before it has all
option for iconify, maximise/minimise, or close/exit.
When window is minimised it can be resized by its border or corner, and displaced by
dragging of title bar. This behaviour is also down with sub windows.
2.4.3.2 ToolTip
When mouse pointer remains on tool bar icon or menu, a tool tip appears with a short
message explaining the function.
Installation SCE/EN IN/D10
INSTALLATION
Installation SCE/EN IN/D10
CONTENTS
2. REQUIREMENTS 4
2.1 Hardware 4
2.2 PACiS SCE License 4
2.2.1 Scope of Use 5
2.2.2 The Licensee agrees NOT TO: 5
2.2.3 Duration 5
2.2.4 Confidentiality 5
2.2.5 The Licensee SHALL NOT 5
2.2.6 The Licensee SHALL 6
2.2.7 Warranty 6
2.2.8 Limitations of Liability 7
2.2.9 Multi-User 7
2.2.10 General 7
2.3 PACiS SCE delivery package 8
2. REQUIREMENTS
PACiS SCE can be installed onto desktop or laptop PC depending of the use of it:
⇒ checking data
⇒ parameter modification
⇒ prototyping substation
⇒ template/model development
− The case of an Event of Default falling within 5.3 above the purchase price of the
Licensed Programme.
− The case of any other Event of Default the licence fee paid in respect of the
Licensed Programme.
6. Subject to clause 5.2 above the Supplier shall not be liable to the Licensee in respect
of any Event of Default for loss of profits, goodwill or any type of special indirect or
consequential loss (including loss or damage suffered by the Licensee as a result of
an action brought by a third party) even if such loss was reasonably foreseeable or the
Supplier had been advised of the possibility of the Licensee incurring the same.
2.2.9 Multi-User
The Supplier in consideration of an enhanced licence fee paid on its own or as part of a
purchase price may authorise the Licensee to use the Licensed Programme simultaneously
on:
1. Any single computer system that contains up to 5 central processing units (CPUs).
2. Any single computer system that contains up to 10 central processing units (CPUs).
2.2.10 General
This Licence Agreement overrides all prior written and oral communications regarding the
Licensed Programme with the Licensee, and sets out the entire agreement between the
Supplier and the Licensee. In the event of a dispute between the Supplier and the Licensee
relating to this Licence Agreement, the Licensee agrees to submit to the jurisdiction of the
French Courts or to the Courts of other legal systems that may from time to time be elected
at the sole discretion of the Supplier. If any provision in this Licence Agreement is ruled
invalid under any law, such provision shall be deemed modified or omitted only to the extent
necessary to render it valid and the remainder of this Licence Agreement shall continue in
full force and effect.
SCE/EN IN/D10 Installation
Step Action
1
Administrator rights
The Installation on Windows Seven must be done with Administrator rights.
2
Disabling Windows Update
The Windows Update from the Control Panel has to be inactive.
• Access "Control Panel > System and Security > Windows Update"
• Click "Turn Windows Update on or off"
• Choose option "Never check for updates”
SCE/EN IN/D10 Installation
Step Action
3
Disabling Windows Firewall
The Windows Firewall from the Control Panel has to be inactive.
• Access "Control Panel > System and Security > Windows Firewall"
• Click "Turn Windows Firewal on or off"
• Choose options "Turn off Windows Firewall"
The InstallAnywhere asks then for the appropriate installation language. A scrolling list
shown in Fig 2 helps in selecting it.
Next screen proposes to accept the terms of the Licence Agreement. Next button is enabled
only if the choice “I accept…” has been done.
Selecting the Next button leads to define what can be installed. It is proposed a Software,
documentation or Software and Documentation installation.
At this stage, all parameters are entered. It remains possible to stop the installation via the
cancel button. The Install button will then start to uncompress in the defined folder.
Step Action
1 • Select PACIS SCE Shortcut
• Click Right
• Choose Properties
2 • The "Properties" dialog box:
• Choose Compatibility
• Validate option Run this program in compatibility mode for:
• Choose Windows Vista (Service Pack2)
• Validate option Run this program as an administrator
• Click Apply
SCE/EN IN/D10 Installation
CARE PRIOR STARTING to read and parameter correctly the equipment as described in
chapter PACiS SCE SETTING.
3.1.4 PACiS SCE Tool Install: vcredist_X86.exe
Always execute/Install the vcredist_X86.exe file located in ("C:\Program
files\PACiS\sce\<SCEVersion>\data\cal\setting\vcredist_x86\vcredist_x86.exe") .If it is not
correctly installed, the setbuilder program to produce the setting files of MiCOM C264 may
not work.
Installation SCE/EN IN/D10
⇒ D:\S2K_HMI\XSL
FIGURE 17 - RESTART
Restart your computer for a correct running of XML Parser.
Installation SCE/EN IN/D10
3.4 PACiS SCE Tool Install: Configurable Automation ISaGRAF data access
To compile ISaGRAF project from PACiS SCE and if Microsoft Access 97 is not installed,
you need MS Office 97 ValuPack.
Install the ODBC driver (dataacc.exe) provided in the MS Office 97 Value Pack. You can
download the MS Office 97 Value Pack from:
− http://www.microsoft.com/ and search for these key words “Office 97 ValuPack”. Make
sure that you spell ValuPack the Microsoft way: it is a registered trademark name.
− http://www.microsoft.com/downloads/en/details.aspx?familyid=BEFD7842-602E-
42B0-89D2-6BE39F1167C1&displaylang=en
Office 97 SR-2b is a free update to Office 97, consisting of a series of recent fixes and
designed to make it even easier for customers to deploy Office 97. SR-2b includes currently
available downloads such as the Microsoft Excel 97 for Windows Auto-Recalculation Patch.
3.5 ISaGRAF upgrade
If you have a dongle for ISaGRAF 5.13, you can upgrade it to 5.21.
To do this, install license manager. Then, insert the dongle for 5.13 and launch license
manager. Do this procedure for each dongle, one at a time.
− Download and install the dongle management software Sentinel Protection on the
ISaGRAF USB dongle. This dongle software is available at:
http://c3.safenet-inc.com/downloads/0/F/0FE57DCB-3A4A-4197-9728-
EDF352C04562/Sentinel%20Protection%20Installer%207.2.2.exe
− The License Manager window shows that the dongle is for ISaGRAF 5.1X:
Installation SCE/EN IN/D10
− To claim your upgrade from ISaGRAF Version 5.13 to ISaGRAF Version 5.21, click
Send... The License Manager sends the User codes 1 and 2 to ISaGRAF support:
supporteurope@isagraf.com
− Type the Registry keys 1 and 2 in the License Manager. Click Proceed.
− ISAGRAF PRO
− …
In the case of PACiS SCE, the Uninstall can be done directly with “Start-up/Application
menu” on item uninstall.
Installation SCE/EN IN/D10
⇒ Menu File/ Prepare Upgrade & Save (save DB with additional data)
⇒ Open the DB
FIGURE 22 - JAVA CONSOLE IN THE WINDOWS CONFIGURATION PANEL, ACTIVATED USER JAVA
APPLICATION RUNTIME VERSION (S)
Installation SCE/EN IN/D10
3. In the Windows Configuration Panel using the JAVA console configure JAVA Updates
to never check for updates automatically
7. TEST
The test strategy consists in creating various scripts dedicated to the various silent mode
commands. Targeted data bases will be standard ones (no import), PCCN ones (XML files
import) and PACIS “d” ones (FCS files import) when available.
Run the script using the command line.
Settings SCE/EN ST/D10
SETTINGS
Settings SCE/EN ST/D10
CONTENT
3. REGITRY KEYS 8
SCE/EN ST/D10 Settings
BLANK PAGE
Settings SCE/EN ST/D10
• Acrobat Reader Application path: the binary file path of Acrobat Reader.
SCE/EN ST/D10 Settings
• Graphic part settings: the graphical editors (mimic editor, bay mimic editor,…) options.
3. REGITRY KEYS
The PACiS SCE application records a registration key:
HKEY_LOCAL_MACHINE\SOFTWARE\...\PACIS\System Configuration Editor\4.7
NOTE: For the complete path access of registry key, please consult the
Schneider Electric technical support if needed.
which has the following strings value:
This key is issued by the installation procedure of a patch to erase files of an already
installed version.
Record Sheet SCE/EN RS/D10
RECORD SHEET
Record Sheet SCE/EN RS/D10
CONTENT
2. WORKSTATION CHARACTERISTICS 4
2.1 PC Characteristics 4
2.2 OS Characteristics 4
3. INSTALLATION 5
3.1 Software Delivery 5
3.2 PACiS SCE Installation 5
3.2.1 General Installation 5
3.2.2 Optional Installations 5
3.3 Installation checking 6
3.3.1 General Checking 6
3.3.2 Settings Checking 6
SCE/EN RS/D10 Record Sheet
BLANK PAGE
Record Sheet SCE/EN RS/D10
2. WORKSTATION CHARACTERISTICS
2.1 PC Characteristics
PC Name
Clock Frequency (GHz)
RAM Size (MB)
DD Size (MB)
2.2 OS Characteristics
3. INSTALLATION
3.1 Software Delivery
lax.nl.java.option.java.heap.size.max
JDK’s version
PACiS SCE’s version
Maintenance SCE/EN MF/D10
MAINTENANCE
Maintenance SCE/EN MF/D10
CONTENT
2. CHECKS 4
2.1 Check user interface 4
2.2 Graphic symbols used in this document 5
2.3 General checks 6
2.3.1 Internal error 6
2.3.2 Objects in Temporary area 6
2.3.3 Capacity limits 6
2.3.4 Variant attributes value 7
2.3.5 Relations 7
2.3.6 Templates 9
2.4 System checks 9
2.4.1 TCP/IP definition on Ethernet Network 9
2.4.2 SNTP servers 10
2.4.3 IEC61850 Physical Devices 10
2.4.4 Wave Records of MiCOM C264s 25
2.4.5 Channels 27
2.4.6 Legacy Networks 28
2.4.7 SCADA Networks 35
2.4.8 Taking Control function 41
2.4.9 Non PACiS IED on IEC61850 43
2.5 Electrical checks 43
2.5.1 Bay and Bay Mimic 43
2.5.2 Switchgear 44
2.5.3 Circuit Breaker 44
2.5.4 Automation Input/Output Plugs 46
2.5.5 Tap Changer 51
2.5.6 AutoRecloser function 52
2.5.7 Synchrocheck function 54
2.5.8 ATCC function 56
2.5.9 Protection module 57
2.5.10 Topology 58
2.5.11 Fast Load Shedding 58
2.5.12 Load shedding/ Load Curtailement 58
2.5.13 I²t function 58
2.5.14 AVR Function 59
SCE/EN MF/D10 Maintenance
2. CHECKS
This section presents the list and the corresponding explanation of the error/warning
messages you can get into the checks tab of the log window.
Theses errors or warning are raised during the complete consistency check of the current
configuration. The check function is available via menu item file/check (shortcut F6).
Checks are performed according to the following steps:
− General checks
− System checks
− Electrical checks
− Graphical checks
− Datapoints checks
Spare objects are not processed.
Objects in Temporary area are not processed.
Referenced document is SCE Check Specification-DSL2-Issue B1.
2.1 Check user interface
The system displays check traces in the following table of the Traces panel ("Checks" tab):
− Each row corresponds to one check operation whose result is an error or a warning or
information.
Table columns:
− First column:
The user can check On/Off this column to remember which error/warning he tried to
correct.
− Level:
Icon of error, warning or info.
− Code:
Identifier of the error, warning or info message. Each code and its level are defined
below.
− Type:
Identifier of the check operation.
Example: "CircuitBreaker" is a check consisting in verifying the configuration of a
Circuit breaker (missing datapoints, … ).
Maintenance SCE/EN MF/D10
− Reference:
For each check operation, an Object implicated in the check operation, is considered
as the main Object. The column displays the external Id of this Object. If the user
activates the "Reach" action on the row, this Object is retrieved in the SCE browsers
and selected.
− Message:
It displays a message explaining the error/warning/info for the check operation.
The panel of the Table contains also the following buttons:
The configuration of Relations and Attributes is described in the User Manual of PACiS SCE.
SCE/EN MF/D10 Maintenance
Additional checks:
The check of the count of Symbols per "Comp. workspace" and per "Bay mimic" is described
in section 2.6.4.1Symbols.
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.16 bits
- Address on 16 bits.8 bits
- Address on 8 bits.8 bits.8 bits
- Address on 24 bits (3 bytes)
S0220ENa
At the User Interface, the modification of the "protocol" value may lead to an incompatible
"address structure" value.
• 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
S0221ENa
If the relation is linked to a spare object, then the following message is displayed:
− C26x SCADA protocols have the relation with a “main comm. port” which hasn’t to be
filled in case of T104 protocol,
− GHU200 Boards have a relation with a workspace which hasn’t 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
S0222ENa
− If a filter is defined for a relation, the link must be compatible with the filter definition.
Object
(R)
Relation link
Filter link ∉ Filter
S0223ENa
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]
Maintenance SCE/EN MF/D10
2.3.6 Templates
The goal of these checks is to warn user about template coherency. For templates, check if
all components are present in all instances or clones.
This check indicates the template and instance concerned, and the component which are
missing. If the component is a template clone, indicate only the main template.
The way to correct this error is to delete the missing component in the template and to
recreate it.
68213 / Templates / One instance of the template is not coherent with the template
definition (Template, Instance, missing component)
Example:
68213 / Templates / One instance of the template is not coherent with the template definition
(Template, Instance, missing component) -> [Site-Feeder-Feeder1 | Feeder1, Site |
Substation | Voltage level | Feeder 1, Circuit breaker]
68215 / Templates / One instance of the template is not coherent with the template
definition, a root component is missing (Template, Instance, missing component)
A template can only use 1 sub-level of template, i.e. a maximum level of inner template is 2.
Each device connected to an Ethernet Network has 2 attributes "TCP/IP address" and
"network name".
⇒ The "TCP/IP address" value of a device, must be unique among all the devices per
Ethernet Network.
⇒ The "network name" value of a device, must be unique among all the devices per
Ethernet Network.
⇒ The network name (alias TCP/IP) must not be reserved by operating system.
Exception:
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.
07249 / TCPIPattribute / The PACiS SNTP server must be a computer (IP address,
device)
If auxiliary IP address is configured primary address must be configured too.
07251 / TCPIPattribute / The two SNTP addresses must be different (IP address)
If the SNTP server (main or auxiliary) is a computer, the datapoint “External clock status” is
mandatory for it:
• For a device, the relations "has for backup" and "is backup of" are mutually exclusive.
30044 / Redundancy / The relation types are not compatible-> [has for backup, is backup
of]
A main and its backup must be devices of the same type.
30073 / Redundancy / The main and the backup are not of the same type
Examples:
30073 / Redundancy / The main & the backup are not of the same type-> [OI server, C264]
Maintenance SCE/EN MF/D10
• A Client must not be linked to the same Server through multiple relations "has for IEC
server".
08107 / RelationClientServer / The relation attribute value is not valid. It must be: Data
model only
Examples:
08107 / RelationClientServer / The relation attribute value is not valid. It must be: Data model
only-> [has for IEC server: OI server, modelling/goose usage = Goose only]
• for a relation client-server with data model usage = data model with or without GOOSE,
a MICOM C264 cannot have more than 10 clients and/or 16 servers. The client-server
relations with GOOSE only are out of the scope of this rule.
SCE/EN MF/D10 Maintenance
<08141> / RelationClientServer / More than 10 clients for the same computer server
<08140> / RelationClientServer / More than 16 servers for the same computer client
(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
S0472ENa
− this Mapping must be compatible with the value ("IEC61850") set to the "protocol"
attribute of the "Ethernet network".
• For each Legacy Device on a Legacy Network and, for each SCADA Network:
− this extended Mapping must be compatible with the value ("IEC61850") set to the
"protocol" attribute of the "Ethernet network".
− 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 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".
− MX
− ST
the maximum count of DataObjects is 50.
SCE/EN MF/D10 Maintenance
OI server
HMI IEC Map.
LD0 for OI
HMIDIAG
ST for HMIDIAG
SOE1St0
SOE1St1
SOE2St0
SOE2St1
SLB1St0
SLB1St1
SLB2St0
SLB2St1
(A) printer
OI printer Sequence of Events
System infos (R) has for IEC address
Printer status SOE∗St∗
(R) has for IEC address
BackupPrint stat SOE∗St∗
(A) printer
OI printer Log Book
System infos (R) has for IEC address
Printer status SLB∗St∗
(R) has for IEC address
BackupPrint stat SLB∗St∗
• If the "OI printer" has its attribute "printer type" set to the "Sequence of Events" value,
then its system Datapoints "Printer status" and "BackupPrint stat." must be linked to an
IEC address named "SOE∗St∗". Only 1 relation is allowed.
• If the "OI printer" has its attribute "printer type" set to the "Log Book" value, then its
system Datapoints "Printer status" and "BackupPrint stat." must be linked to an IEC
address named "SLB∗St∗". Only 1 relation is allowed.
OI server
HMI IEC Map.
LD0 for OI
HMIDIAG
ST for HMIDIAG
HMISt0
HMISt1
HMISt2
HMISt3
HMISt4
HMISt5
HMISt6
HMISt7
(R) has for HMI server
OI client
System infos (R) has for IEC address
OI client link HMISt∗
• The system Datapoint "OI client link" of an "OI client" must be linked to an IEC address
named "HMISt∗". Only 1 relation is allowed.
C264
C26x IEC Map.
LD0 for C26x
C26xDIAG
ST for C26xDIAG
DIUSt0
DIUSt1
DIUSt2
DIUSt3
…
(A) physical board number 0
DIU200
System infos (R) has for IEC address
DIU status DIUSt0
S0232ENb
• The status Datapoint of a Computer board must be linked to an IEC address with a
name matching the board type and ending with the value of the attribute "physical
board number". Only 1 relation is allowed.
27067 / EthernetAddressing / The address in not compatible with the board number
Example:
27067 / EthernetAddressing / The address in not compatible with the board number-> [has
for IEC address: DIUSt1, DIU200.physical board number = 0]
2.4.3.4 C264 Boards
A B 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
BIU CPU
− DOU200
− DIU2xx
− CCU20x
− AOU200
Slot 15 may contain 1 TMU200/TMU210/TMU220 board or 1 board of the above types.
A B 1 2 3 4 5 6
BIU CPU
Maintenance SCE/EN MF/D10
− DOU200
− DIU2xx
− CCU20x
− AOU200
Slots 5, 6 may contain 1 TMU200/TMU210/TMU220 board or 2 boards of the above types.
09144 / ComputerBoards / The count of TMU boards is not valid (count, maximum)
09145 / ComputerBoards / The count of AIU boards is not valid (count, maximum)
S0233ENb
For boards AOU200, 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)
SCE/EN MF/D10 Maintenance
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]
S0592ENa
For boards managing the slot number, the "slot number" attribute values must be unique.
09282 / ComputerBoards / The attribute value is not unique for boards of rack
Example:
09282 / ComputerBoards / The attribute value is not unique for boards of rack -> [slot
number, C]
• GHU200 board.
The GHU200 board has an attribute "HMI type" and a relation "has for workspace".
C264 - Simple
(A) HMI type
GHU200 - Complete
Led # 4 - Old
(R) has for workspace
SPS
DPS
S0234ENa
− 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 / Computer Boards / 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 / Computer Boards / 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]
Maintenance SCE/EN MF/D10
− 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 can’t 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 computer bearing the led:
35227 / BoardLeds / Board led can be use only by data point managed by the led server
− Only led #14 to led #17 can be used by a data point if the led allocation is set to
predefined at the GHU board level:
35281 / BoardLeds / The use of this LED is incompatible with the predefined led
allocation
<09139> / ComputerBoards / TMU200, TMU210 and TMU220 can not belong to the
same computer.
• TMU210 board
When used, its DO channel can only be wired to the open or close states of the Switch
Control DPC of a breaker.
The DO#1 can be wired on open state and DO#5 on closed state.
09180 / ComputerBoards / DO channels of TMU210 can only be used for open (DO_1)
or close (DO_5) states of the Switch Control DPC of a breaker
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 SCE
• CPU260/CPU270 board
When ports 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 C264 is configured as redundanct, AOU200 board is not allowed.
S0233ENa
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
For each attribute category (BI filtering / Measurements / Counter), if the attribute
"debouncing delay" is set to value 0, then the attribute "filtering delay" must be set to value 0.
S0236ENa
The "SPC" link of the relation "has its klaxon controlled by" must be wired on a DO channel
of the Computer.
10034 / ComputerSettings / The relation link is not a datapoint wired on the Computer
Maintenance SCE/EN MF/D10
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.4.3.8 Computer Printers
C264
(A) buffer size
Serial printer 1000
(A) nb of events to suppress when saturated 300
S0237ENa
The following constraint between the two attributes values must be respected:
"buffer size" > "nb of events to suppress when saturated"
29105 / Printers / buffer size (events) is not greater than nb of events to suppress when
saturated
Examples:
29105 / Printers / buffer size (events) is not greater than nb of events to suppress when
saturated-> [200, 300]
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
S0238ENa
OI server
(A) printer type Sequence Of Events
OI printer 1
(A) printer type
OI printer 2 Sequence Of Events
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]
OI server
(A) buffer length
OI printer 60
(A) recovery length 45
S0240ENa
The following constraint between the two attributes values must be respected:
"buffer length" > "recovery length"
29105 / Printers / buffer length (s) is not greater than recovery length (s)
Examples:
29105 / Printers / buffer length (s) is not greater than recovery length (s)-> [60, 61]
OI server
(A) Chronology column rank
OI printer 1
(A) Time Stamp column rank
2
(A) Origin column rank
3
(A) Object Name column rank
(A) Object Message column rank
4
(A) Origin Cat. column rank
5
0
(A) Origin Ident. column rank
0
The value of each "… column rank" attribute different than 0 must be unique.
The maximum number of characters by printing line is 154
Example:
29072 / Printers / The column rank is not unique-> [Chronology column rank, Object
Message column rank, Object Name column rank, Origin column rank, Time Stamp column
rank, 1]
29203 / Printers / The size in character of the printing line is too long
Example:
29203 / Printers / The size in character of the printing line is too long -> [205, 154]
2.4.3.10 OI server Symbols
NOTE : These checks are only processed for non-backup OI servers.
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.
Doesn’t treat a workspace twice if set as workspace of two clients.
02003 / CapacityLimits / The count of Send Order components is not valid (count,
maximum)
2.4.3.11 IEC Gen IED data model reference
34101 / DataModelReference / The attribute value is not valid-> [model file name]
2.4.3.12 Cyclic SPS
NOTE: This check is only processed for non-backup computers.
Up to eight cyclic SPS can be managed per computer basis
76263 / C264 AM Acquisition / Delta between 'long AI scanning cycle' and 'short AI
scanning cycle' must be greater or equals to 500 ms.
SCE/EN MF/D10 Maintenance
2.4.3.14 OI Server
• In Hot Redundancy mode the OI Server must have the Redundancy Status datapoint
“Red Status”. The “Red Status” indicates the OI status (refer to OI/EN AP chapter for
status details).
Red.Status must be
configured in Hot
Redundancy mode.
• In Hot Redundancy mode, if exist more than one OI Clients exists, each OI Server is
HMI server for at least one OI client
77260 / OI / In Hot Redundancy mode if exist more than one OI Client, each OI Server is
HMI server for at least one OI client.
Maintenance SCE/EN MF/D10
• 36195 / WaveRecording / multiple links to the same datapoint -> [external id of the
relation]
A Wave Record can only registrer data point wired physically on the same server tha the
MiCOM C264which mange the Wave Record.
A Wave Record can only registrer data point managed by the same server than the C264
which mange the Wave Record, and not acquire on IED.
C264
Wave fast record (A) pre-trigger cycle 0
(A) total cycles
480 | 240 | 120 | 60
(A) number of files
1|2|4|8
S0243ENa
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]
2.4.4.3 Wave Slow Record
C264
Wave slow record (A) pre-trigger cycle 0
(A) total records
480 | 240 | 120 | 60
(A) number of files
1|2|4|8
S0244ENa
DPS
SPS
S0245ENa
− If the "integration time" value is > 5, then no DPC, SPC, DPS, SPS recording is
allowed.
− If the "integration time" value is > 6, then no DPC, SPC, DPS, SPS recording is
allowed.
36223 / WaveRecording / The trigger datapoint has not the same server as its
associated wave record (servers)
Maintenance SCE/EN MF/D10
2.4.5 Channels
Example of relations connecting Legacy Network / SCADA Network / Serial Printer /
Datapoint to a Channel:
C264 C264
BIU200
DNP3 master (Legacy Network) (R) has for main comm. port
RS232/485 port 1 (Comm. Channel)
(R) has for aux. comm. port RS232/485 port 2 (Comm. Channel)
C264
(R) 'bit 00' wired on DIU200
MV DI#0 (Channel)
(R) 'bit 01' wired on
DI#1 (Channel)
S0248ENa
Under a Gateway, each channel used by a non-GI74 protocol, must have a unique value for
its "plug com. number" attribute.
31019 / GatewayCommPorts / The attribute value is not unique for the gateway
Example:
31019 / GatewayCommPorts / The attribute value is not unique for the gateway-> [plug com.
number, 1]
Attribute "baud rate" of Gateway channel:
Under a Gateway, channel baud rates 100, 200, 38400 are available only for T101 protocol.
17277 / LegacyIED / Even parity is required for T103 usage on the port
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
T101 master
(A) network address
T101_IED 0
S0250ENa
Maintenance SCE/EN MF/D10
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
S0251ENa
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]
SCE/EN MF/D10 Maintenance
DNP3_IED
IED Mapping
IED MV Mapping
MV addr. on IED (A) address 5
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-> [address, 0]
Maintenance SCE/EN MF/D10
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 MPS Mapping (A) mapping address , (A) function , A: bit number
MPS addr. on IED 0,1,1
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-> [mapping address/function/bit number, 0/0/0]
18037 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the
Mapping-> [mapping address/function, 0/0]
• In the IED Mapping, the address ‘bit number’ attribute must be lower than 16 ( 0..15)
for SPS/DPS/MPS/SPC/DPC MODBUS IED Address.
• 18232 / xxxAddressOnIED / 'Bit number' on IED MODBUS address must be lower than
16
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.
For each "xxx addr. on IED", the address identification is made of the following combinations
of its attribute values :
MODB_IED_1_ABB
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 MPS Mapping (A) mapping address , (A) function , A: bit number
MPS addr. on IED 0,1,1
MODB_IED_2_ABB
IED Mapping
IED DPC Mapping (A) mapping address , (A) function , A: bit number
DPC addr. on IED 1,0,0
IED DPS Mapping (A) mapping address , (A) function , A: bit number
DPS addr. on IED 1,0,0
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
IED MPS Mapping (A) mapping address , (A) function , A: bit number
MPS addr. on IED 1,1,1
18262 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the
legacy MODBUS for all ABB IED-> [mapping address/fonction/bit number, 57/1/1, Scs |
Ethernet network | C264 | Modbus Mod. (LB)]
Under a Legacy MODBUS a maximum of 15 ABB IED can be use. ABB flexgate manage 15
IED maximum.
02003 / CapacityLimits / The count of ABB IED components is not valid (count,
maximum)-> [16, 15]
Maintenance SCE/EN MF/D10
T103_IED
IED Mapping
IED DPC Mapping (A) ASDU number , (A) function type, (A) information number
DPC addr. on IED 0,0,0
(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
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-> [ASDU number/function type/information number, 0/0/0]
18037 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the
Mapping-> [ASDU number/function type/information number/common address of ASDU,
0/0/0/1]
18037 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the
Mapping-> [ASDU number/function type/information number/common address of
ASDU/index in the ASDU, 0/1/1/0/0]
SCE/EN MF/D10 Maintenance
T101_IED
IED Mapping
IED DPC Mapping (A) information object address, (A) common address of ASDU
DPC addr. on IED 0,0
IED Counter Mapping (A) information object address, (A) common address of ASDU
Counter addr. on IED
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-> [information object address, 0]
18037 / xxxAddressOnIED / The address of the 'xxx address on IED' is not unique in the
Mapping-> [information object address/common address of ASDU, 0/0]
2.4.6.3 IED on Legacy T103 Network
For each T103 IED, if the MPS datapoint POC exists, the MPS PSE must also exist.
• 17186 / LegacyIED / The IED must have the relation Is Relay Of, because PSE and/or
POC is SBMC dependent
Maintenance SCE/EN MF/D10
• 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.
17274 / LegacyIED / The IED requires a SEPAM synchronisation (IED network, IED)
17275 / LegacyIED / The IED requires a FLEXGATE synchronisation (IED network, IED)
2.4.7 SCADA Networks
NOTE: These checks are not processed for SCADA Networks of backup
devices.
2.4.7.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.4.7.1.1 Address value, in SCADA Mapping of C264s and Gateways
SCE/EN MF/D10 Maintenance
S0257ENb
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 MiCOMC264:
Two addresses are used. Their values are given by:
Examples:
19038 / xxxAddressOnSCADANetwork / The address of the 'Gtw xxx address' is not unique
in the Mapping-> [object address, 255]
19038 / xxxAddressOnSCADANetwork / The address of the 'Gtw xxx address' is not unique
in the Mapping-> [SOE file address, 255]
Particular cases of T101, T104 and DNP3 protocols (for MiCOM C264 and Gateways):
− The unicity constraint is applicable only for addresses of the same type.
Addresses of different types can have identical addresses and therefore this does
not lead to an error but to a warning.
− Address for Disturbance uploading and Buffer Overflow (only for T101 and T104)
to SCADA are also taken into account in the unicity check.
− The type for T101 and T104 is same as defined in SCE (SPS, DPS, SPC…) and
for DNP3, is grouping simple and double (TS, TC, TM, Counter and SetPoint)
18169 / LegacyIED / The SCADA address format for PSE/POC must be bitstring
For CDCII SCADA addressing, SQN value attribute must respect following constraints:
C264 - T101
(A) protocol - DNP3 depending of
C26x SCADA prot
- T104
Gtw SCADA Map. (A) address structure
- 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
- Address on 8 bits.16 bits
- Address on 16 bits.8 bits
- Address on 8 bits.8 bits.8 bits
255.255.255
S0258ENa
An "object address" value is formatted according to the "address structure" value selected in
the protocol definition.
The set of possible "address structure" values depends on the protocol type.
SCE/EN MF/D10 Maintenance
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".
C264
(A) protocol DNP3
C26x SCADA prot
Gtw MV Map
Gtw MV addr. (A) Format
Natural
Transformer (Bay)
transformer
(R) has for SCADA address
Tap Changer
Tap pos ind (MV)
S0259ENa
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]
Maintenance SCE/EN MF/D10
"W" ≤ "K"
20103 / SCADA_Networks / T2: acknowledgement time-out (s) is not lower than T1:
APDU time-out (s)
20103 / SCADA_Networks / T1: APDU time-out (s) is not lower than T3: test frame time-
out (s)
IEC gateway
GI74 protocol
S0262ENb
Example:
14023 / RelationHasForFeedback / Multiple links to feedbacks-> [has for feedback: GI74
DPS addr., has for feedback: GI74 SPS addr.]
2.4.7.1.7 Addressing of MPS on T101/T104 of MiCOM C264
MPS addressing in refused on T101/T104 SCADA network of MiCOM C264.
20206 / SCADA_Networks / The maximum number of SCADA protocols for a C264 has
been reached (max number, count of protocols)
20209 / SCADA_Networks / The coherency between this protocol type (protocol type)
and this gateway port (gateway port) is failed.
Maintenance SCE/EN MF/D10
C264
Extension
rack
BIU2
41
Port 1
Port 2
Has For aux. comm. port
SCADA
Network Has For Main comm. port
S0596ENa
S0265ENa
• If, at least, one SCADA network is linked to a Taking Control function, all the SCADA
Networks of the system must be linked to a Taking Control function.
52131 / TakingControl / The relation link is missing-> [has for taken control]
SCE/EN MF/D10 Maintenance
• A "Taking Control" datapoint must be linked to a "Taking Status" datapoint through the
relation "has for feedback".
Substation
(A) activation mode - Permanent
Taking Control - Permanent until feedback
Taking Status (A) detection mode
- Permanent
S0266ENa
• Both "Taking Control" and "Taking Status" datapoints must be linked to a SCADA
address in the mapping of their SCADA network.
Substation
Ethernet network
(R) has for feedback
Taking Control C264
(R) is taken control of
Taking Status
C26X SCADA prot
GtwSCADAMap
(R) has for SCADA address
Gtw SPC Mapping
Gtw SPC addr.
(R) has for SCADA address
Gtw SPS Mapping
Gtw SPS addr.
S0267ENa
• 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
S0268ENa
82283 / IED virtual input / The virtual input and the associated used datapoint can not
have the same server
2.4.9.2 Report by client limit
For each non PACiS IED, check if there’s enough report for all clients needs.
83284 / Indiced reports Not enough reports for all clients (Server path, Client path, List of
DataObject missing)
2.4.9.3 Dataset creation limit
For each non PACiS 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.5 Electrical checks
2.5.1 Bay and 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)
• 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]
33106 / BayMimic / The relation attribute value is not unique (relation, attribute)
SCE/EN MF/D10 Maintenance
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 view):
33005 / BayMimic / The count of graphically displayed Bays is not valid (count, maximum)->
[13, 12]
2.5.2 Switchgear
Switchgear
Switch Ctrl SPC mutually exclusive
Switch Ctrl DPC
S0508ENa
The same type of datapoints which can be single or double (like "Switch Ctrl DPC" and "Switch
Ctrl SPC") are mutually exclusive
70066 / Switchgear / The datapoints are not compatible -> [Switch Ctrl SPC, Switch Ctrl
DPC]
2.5.3 Circuit Breaker
2.5.3.1 Phases of Circuit Breaker
• The same type of datapoints which can be single or double (like "Switch Ctrl DPC" and
"Switch Ctrl SPC") are mutually exclusive. None is mandatory.
40066 / CircuitBreaker / The datapoints are not compatible-> [Switch Ctrl DPC, Switch
Ctrl SPC]
Maintenance SCE/EN MF/D10
• 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.
− 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) ]
• If the "circuit-breaker type" is set to the "Triple phase CircuitBreaker" value, then:
Substation
(R) is synchrocheck of
Ext manual CS
Feeder
Circuit breaker
• The Circuit Breaker must be linked only once to a Synchrocheck function (relation "is
synchrocheck of").
42094 / Synchrocheck / The datapoint is not allowed-> [Site | Substation | Voltage level |
BAY_CBO | circuit breaker | Sync CB close]
42049 / Synchrocheck / The relation is not valid-> [Site | Substation | Voltage level |
BAY_CBO | circuit breaker | Sync CB close | has for feedback : Switchgear pos.]
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.5.4 Automation Input/Output Plugs
2.5.4.1 FBD automation
2.5.4.1.1 FBD status
38160 / Automation / The developed equation is to big (do not exceed 256 datapoints)
• FBD must not contain TON/TOFF block with a timer value lower than t#50ms.
38252 / Automation / FBD contains at least one timer value lower than 50 milliseconds
(lower value)
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)
Maintenance SCE/EN MF/D10
− a SPC/DPC datapoint can not be linked more than once to the same FBD output
• 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.
• Bloc MASK accepts only LSP datapoint on entry “nMPS”. (Error 39219)
• FBD bloc MASK doesn’t accept LSP datapoint on “bit” entry (0 to 15) (Error 39220)
No LSP datapoints
S0597ENa
SCE/EN MF/D10 Maintenance
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 linked with at least one data point.
39226 / AutomationIOPlug / Fbd input/output must be linked with one data point.
• 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.
• Any FBD automatism input or output, which is not served by the computer, must have
a ‘goose usage’ attribute set to ‘true’ from data object level of datapoint associated
39308 / AutomationIOPlug / Invalid setting timer used for timer block (setting path,
allowed timer setting, used timer setting)
− the inputs/outputs or settings defined in XML file are not present in SCE database
38273 / Automation / The FBD's XML file doesn't exists -> [XML file]
38274 / Automation / The FBD's XML file is corrupt -> [XML file]
38275 / Automation / The FBD has inconsistent input, output or setting -> [XML file]
When such problem raise, the FBD is corrupted, and must be deleted.
For instance objects or template clones, the check is done on template source
2.5.4.1.4 Datapoint used by FBD at MiCOM C264 level
• At MICOM C264 level, a datapoint can not be used more than 255 times in the set of
its PSLs.
38222 / Automation / The datapoint is used more than 255 times in the PSLs of
MICOM C264 [C264, nb tims >255]
2.5.4.1.5 Settings Micom S1 used by FBD at MiCOM C264 level
• By MICOM C264, the number of Boolean settings MicomS1 used in FBD can’t be
greater than 100.
38253 / Automation / The number of FBD boolean settings MicomS1 for this C264 is too
great [C264, nb > 100]
• By MICOM C264, the number of Timer settings MicomS1 used in FBD can’t be greater
than 100.
38254 / Automation / The number of FBD timer settings MicomS1 for this C264is too
great [C264r, nb > 100]
• By MICOM C264, the number of settable FBD can’t be greater than 50.
38269 / Automation / The number of settable FBD for this C264 is too great [C264, nb >
50]
• For each FBD operator the maximum number of boolean setting per operator basis
(AND, OR …) is 1.
38293 / Automation / There are more than one boolean setting for the operator
• For each timer and accurate timer, the default value must be between the minimum
value and maximum value.
38312 / Automation / The default value is not between minimum and maximum value
• For each timer and accurate timer, the default value must be a multiple of step value.
o Example: a step of 15 allows a default value of 15, 30, 45, 60, etc…
38320 / Automation / Default value for FBD timer must be a multiple of step value
• 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
SCE/EN MF/D10 Maintenance
(A) modified
Slow automation - Yes
- No
S0275ENa
38252 / Automation / The number of Isagraf settings MicomS1 for this C264r is too great
[C264, nb > 100]
• By MICOM C264, the number of settable Isagraf function can’t be greater than 50.
38268 / Automation / The number of settable Isagraf function for this C264 is too great
[C264 nb > 50]
Maintenance SCE/EN MF/D10
Transformer 0
transformer (A) Value features / minimum value
Tap changer (A) Value features / maxmum value
Tap pos ind 0
S0276ENa
• current valid range (% maximum value) > (2 / (maximum acq. value - minimum acq.
value))
37212 / TapChanger / The constraint is not valid:[current valid range (% maximum value)
> (2 / (maximum acq. value - minimum acq. value))]
• current valid range (% maximum value) < (100 / (maximum value - minimum value))
37212 / TapChanger / The constraint is not valid:[current valid range (% maximum value)
< (100 / (maximum value - minimum value))]
37363 Min and max value of transformer don't belong to the interval minimum value -
maximum value of the TPI (MinUsablePosition < MinScaledValue and/or MaxUsablePosition
> MaxScaledValue)
2.5.5.2 RaiseLower / GoToMinMax coherence
Transformer
transformer
Tap changer (R) has for profile (A) SBOMode ?
Raise/lower DPC DPC profile
Goto min/max DPC
S0483ENa
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
SCE/EN MF/D10 Maintenance
- 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
• 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:
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:
If "functioning mode (3 ph trip)" value is set to "3P-3P-3P", then the following rules must be
respected:
41103 / Autorecloser / 1st period triphased (ms) is not lower than 2nd period triphased
(ms)
41103 / Autorecloser / 1st period triphased (ms) is not lower than 3rd period triphased
(ms)
41103 / Autorecloser / 1st period triphased (ms) is not lower than 4th period triphased
(ms)
- 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
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
• 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.
• 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]
- Not used
- 1P
- 1P-3P
- 1P-3P-3P
(A) functioning mode (1 ph trip) - 1P-3P-3P-3P
Feeder
(R) is autorecloser of (A) functioning mode (3 ph trip)
Autorecloser - Not used
- 3P
Circuit breaker - 3P-3P
- 3P-3P-3P
(A) circuit-breaker type - 3P-3P-3P-3P
• 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.5.7 Synchrocheck function
Substation
Ext manual CS
on/off ctrl DPC
on/off ctrl SPC mutually exclusive + wired
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
on/off SPS mutually exclusive
Ext manual CS
on/off ctrl DPC mutually exclusive + wired
on/off ctrl SPC
on/off DPS
on/off SPS mutually exclusive
Int auto CS
on/off ctrl DPC forbidden
on/off ctrl SPC
on/off SPS
Int manual CS
on/off ctrl DPC mutually exclusive
on/off ctrl SPC
on/off SPS
• As shown in the picture, under a Synchrocheck function, some Datapoints are mutually
exclusive and some must be wired.
NOTE: Here, the term "wired" means that the datapoint must be linked to a
digital/analogue channel of a computer, or linked to an IED address.
42066 / Synchrocheck / The datapoints are not compatible-> [on/off ctrl DPC, on/off ctrl
SPC]
Maintenance SCE/EN MF/D10
42066 / Synchrocheck / The datapoints are not compatible-> [on/off SPS, on/off DPS]
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.
42151 / Synchrocheck / More than one internal synchrocheck on the same computer
• 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, the computer managing the synchrocheck must have a
TMU200 or a TMU220 board.
42159 / Synchrocheck / The manager of the internal synchrocheck have not a TMU200
Board
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
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:
− Bypass
− Scheme Coupling
− Scheme Locking
− Scheme LD/BD
− Scheme LD/BL
− Scheme LL/BD
• For an internal synchrocheck, if set as type 1, all this datapoints must not exists :
− Bypass
SCE/EN MF/D10 Maintenance
− Scheme Coupling
− Scheme Locking
− Scheme LD/BD
− Scheme LD/BL
− Scheme LL/BD
• For an internal synchrocheck, if coupling function is set, the value of Ta can not be null.
42326 / Synchrocheck / The value of Ta can not be null for the coupling function usage
2.5.8 ATCC function
Substation
ATCC
(A) ATCC existence - Yes
Voltage level (1) - No
Transformer
transformer
ATCC fct needs
BusBar
ATCC fct needs
− 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]
− 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.
26090 / ATCC / One of the datapoints is missing-> [MCB position DPS, MCB position
SPS]
Maintenance SCE/EN MF/D10
26066 / ATCC / The datapoints are not compatible-> [MCB position DPS, MCB position
SPS]
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.
26176 / ATCC / The voltage MV wiring of an ATCC function is not compliant full ATCC
description
2.5.9 Protection module
The following checks concerns protection functions embedded in MICOM C264P . They
required the presence of the TMU210 board for the MICOM C264P .
• As soon as one or several bays managed by a MICOM C264P , have got a integrated
protection function, this MICOM C264P 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 MICOM C264P , 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 MiCOM C264P:
• as soon as one of them uses a protection function, the “relay automatism” function
must be present.
<55329> / Module protection / “81O”or “81U” functions muusy have the same trip usage
values.
SCE/EN MF/D10 Maintenance
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.5.10 Topology
The following checks concern the electrical topology, i.e. nodes values existing at electrical
module level. They are run when an ATCC function or a Fast Load Shedding function is
configured. In the folloqing, used node means node whose value is different from 65535
• The used nodes of a module can not have the same value.
<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)
2.5.11 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
81280 / I²t function / Site | Substation | Voltage level | Generic bay | I²t function / The
protection module '67' is missing for the computer, mandatory for I²t function.
− IT_phase_A
− IT_phase_B
− IT_phase_C
− IT_total
− I2T_phase_A
− I2T_phase_B
− I2T_phase_C
− I2T_total
81281 / I²t function / Site | Substation | Voltage level | Generic bay | I²t function /
Missing mandatory computed MV for I²t function (Computed MV)-> [I²T: IT_phase_A]
55154 / Protection module / Site | Substation | Voltage level | Generic bay 1 | I²t
function. The protection module still exists for the computer-> [Scs | Ethernet network |
C264].
2.5.14 AVR Function
• The two Days chosen for week end days on AVR Period Type 2 and Type 3 must be
consecutive days.
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 (first day, second
day).
SCE/EN MF/D10 Maintenance
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
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)
Maintenance SCE/EN MF/D10
Bay 1
Bay 2
Bay 3
Bay 4
S0600ENa
Scs
Ethernet network (R) has for workspace Graphic
OI bay OI workspace #1
OI Server OI workspace #2
OI Client (R) has for workspace
2.6.1.2 Limitations
An OI workspace shouldn’t contain more than 150000 graphic objects (i.e. graphical
symbols).
78268 / OI Workspace / The Alarm, Title and Command banners are not allowed in a
800x600 workspace -> [forbidden component]
SCE/EN MF/D10 Maintenance
78269 / OI Workspace / Up to five mimics are allowed in an OI Bay workspace -> [mimic
count]
− Only one alarm viewer and one trend viewer can be configured
• 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]
2.6.2 OI Window
Graphic Scs
OI workspace (R) is workspace of Ethernet network
Window OI client
Mimic
Std Alarm Banner
Std Comm. Banner
Std Title Banner
S0282ENa
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)
2.6.3 OI Mimic
2.6.3.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
S0283ENa
The coordinates (x, y) of a symbol must not be located outside the mimic area.
Graphic
OI workspace
window
Mimic
Group
Shape
Multistate
MultiState Max = 1500 / mimic
Shape
…
The number of symbols (shapes or multistates) can’t exceed 1700 inside a mimic. This count
is done recursively. The groups are not count, but their sons yes.
02003 / CapacityLimits / The count of Symbol components is not valid (count, maximum)
2.6.4 Bay Mimic symbols
2.6.4.1 Symbols
• Hidden Symbols:
Graphic
Comp. workspace
width = 128 / height = 128 (fixed values)
Bay mimic
LHMI Transformer (A) x / (A) y 0, 65
LHMI Gen module (A) x / (A) y 0, 85
LHMI bitmap (A) x / (A) y 0, 45
LHMI line (A) x / (A) y
(A) x / (A) y 40, 10
LHMI text
… 0, 40
S0284ENa
The coordinates (x, y) of a symbol must not be located outside the mimic area.
Graphic
Comp. workspace
Bay mimic max = 24 / Comp. workspace
LHMI Transformer max = 9 / Bay mimic
LHMI Gen module
LHMI bitmap max = 5 / Bay mimic
LHMI line max = 30 / Comp. workspace max = 18 / Bay mimic
LHMI text max = 5 / Bay mimic (1 is reserved for the Bay name) + 1 reserved
… for the Bay name
S0285ENa
Some limit exceeding are prevented by the Structural Database rules. The others leads to
the following errors:
• Empty texts:
Graphic
Comp. workspace
Bay mimic
LHMI Transformer
(A) short name
Name
LHMI Gen module
(A) short name
Name
(A) fixed text value
LHMI text
(A) short name
EQL BP (A) short name
L/R
(A) short name
S/C BP
SBMC (A) short name
LHMI labels (A) all labels
S0484ENa
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.6.4.2 Visualized MV datapoints
Graphic Feeder
33168 / BayMimic / The MV datapoint must be produced by TMU board for bay
visualization
Maintenance SCE/EN MF/D10
33125 / BayMimic / The datapoint does not belong to the bay (datapoint, bay)->
[visualizes: Voltage Level MV, represents: Feeder]
• For each visualized MV Datapoint, the "transmission on event" attribute must be set
neither to "Cyclic short period" value nor to "Cyclic long period" value to avoid overflow
of the Bay mimic input buffer.
33123 / BayMimic / The attribute value is not compatible with the relation-> [transmission
on event = Cyclic short period, is visualized by: Bay mimic]
2.6.5 Standard Command Banner
2.6.5.1 OI Bay
• The Klaxon usage value on a Standard Command Banner of an OI Bay must be set to
No, because OI bay doesn’t manage Klaxon option.
76255 / OI Bay/ Klaxon usage value on Standard Command Banner of an OI Bay must
be set to No (OI Bay)
2.6.6 OI symbols
2.6.6.1 Multi-States
Graphic
OI workspace
window Bay
Mimic (R) is managed by Board
Alarm MultiState IED
Audi. MultiState Module
Discrepancy MS …
S0287ENa
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]
49231 / MultiState / A multistate must reference only symbol defined inside it (Symbol)
SCE/EN MF/D10 Maintenance
Graphic
OI workspace
Bay
window
(R) refers to Board
Mimic
IED
Var. text
Module
…
S0289ENa
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.
Graphic
OI workspace
window
Mimic (A) trend type - real time
Trend viewer
- archive
Series (1)
Series (2)
S0290ENa
If a "Trend viewer" has its "trend type" attribute set to "real time", then it can have only 1
"Series".
45003 / TrendViewer / The count of Series components is not valid (count, maximum)
Example:
45003 / TrendViewer / The count of Series components is not valid (count, maximum)-> [2,
1]
In case of usage by an OI Bay in 800x600 resolution, there’s some limitations.
Scs
Graphic (R) is workspace of Ethernet network
OI workspace OI Bay
window
Mimic
Trend viewer
45275 / TrendViewer / The trend type must be set to ‘real time’ in a 800x600 workspace
Maintenance SCE/EN MF/D10
Graphic
OI workspace
window
Mimic (R) is pre-filtered on
Bay
Alarm viewer Voltage level
…
S0291ENa
For an "Alarm/state viewer", only 1 relation "is pre-filtered on" can be linked.
Graphic
OI workspace (A) display count of active alarms
window
Yes
Mimic (A) display count of present alarms
Alarm viewer Yes
For an “alarm/state viewer” which has a browser counting alarms, the alarm list must be defined.
46245 / AlarmViewer / The alarm list must be defined for alarm/state viewer browser
which count alarms
In case of usage by an OI Bay in 800x600 resolution, there’s some limitations.
Scs
Graphic (R) is workspace of Ethernet network
OI workspace OI Bay
window
Mimic
Alarm viewer
46272 / AlarmViewer / The list of the alarm viewer is not allowed in a 800x600workspace
-> [list]
• The alarm viewer mustn’t have a contextual menu defined (contextual menu attribute
must be set to ‘No’)
• The alarm viewer toolbar must contain only Acknowledge and Clear buttons or
separators (toolbar attributes for other buttons must be set to ‘0’)
46274 / AlarmViewer / A button of the toolbar mustn’t be used (the rank must be set to
‘0’) in an OI Bay workspace -> [button attribute]
SCE/EN MF/D10 Maintenance
− there must be at least one column definition with a value different from 0.
Graphic
OI workspace
window
Mimic (1)
Rectangle
Change view
(R) has for new view
Mimic (2)
S0294ENa
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.
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
S0295ENa
Maintenance SCE/EN MF/D10
For an "Open ctrl popup", all the Datapoints linked to the "acts on" relation, must fulfil the
following conditions:
− all of them, or none, are linked to the same Datapoint through the relation "has for
feedback"
− all of them, or none, are linked to the same Datapoint through the relation "has for
AutoManu dependency"
− all of them have their attribute "Substation mode dependency" set to the same
value (if the attribute is available , up to four attributes may be configured))
− all of them have their attribute "bay mode dependency" set to the same value (if
the attribute is available)
− all of them have their attribute "SBMC mode dependency" set to the same value (if
the attribute is available)
− all of them have the attribute "SBO mode" of their Profile set to the same value
− if the Open Control Popup authorizes the Lock function, and if one or several of
them have at the same level the following datapoints: LockModule (SPS) and
LockModule_SPC, then all of them must belong to the same module.
Particular check for Circuit breaker with internal synchrocheck:
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
S0473ENa
For a UserAction "Send FSS Order", the datapoint (SPS or DPS) linked to the "acts on"
relation must have a profile with the attribute "EnableFSS" set to true.
47171 / Symbol / The linked datapoint profile isn't FSS enable (relations)-> [acts on]
One and only one “Launch Action” can be configured under a Graphical symbol object
SCE/EN MF/D10 Maintenance
Graphic
OI workspace
window
Mimic
Text
(A) Type
(A) Box color
S0606ENa
47276 / Symbol / The text color is not allowed for this type -> [type, bad color, allowed
color]
Try to avoid putting a SendOrder under a Text.
47304 / Symbol / It’s better to avoid putting a Send Order under a Text symbol.
2.6.6.8 Image
On image object the attribute “file name” must be defined.
47296 / Symbol/ Graphic | OI workspace | Window | Mimic | Image 2 / The attribute "file
name" of an Image object must be defined
2.6.7 Bitmaps
All the Bitmaps of a configuration are defined in the "Bitmap table" of the configuration.
2.6.7.1 Bitmap index
Graphic
Graph. Tables
Bitmap table (A) reference index
Bitmap (1) 0
(A) reference index
Bitmap (2) 1
Bitmap (3) (A) reference index
2
S0296ENa
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]
Maintenance SCE/EN MF/D10
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
S0297ENa
Depending on the "type" attribute value, 1 or 5 PNG file(s) can be linked to a Bitmap.
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.6.7.3 Reference from BayMimic elements to Bitmap
Graphic
Comp. workspace
Bay mimic (A) bitmap reference
LHMI bitmap 0
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
S0298ENa
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
S0299ENa
SCE/EN MF/D10 Maintenance
The "Bitmap" linked to a "LHMI xPS MultiSt" MultiState must be defined as follows:
− its three first file names { "file name by default", "file name for 'open' state", "file
name for 'closed' state" } are mandatory and each one must be unique.
Furthermore, if the MultiState is linked to a SPS or DPS Datapoint of a module containing a
"Withdrawn" SPS Datapoint, through the "is managed by" relation, then the following
constraints are added to the "Bitmap" definition:
− its two file names { "file name for 'withdrawn open' state", "file name for 'withdrawn
closed' state" } are both mandatory and each one must be unique.
33126 / BayMimic / The attribute value of the referenced bitmap is not valid
33128 / BayMimic / Multiple use of the same attribute value in the referenced bitmap
Example:
33126 / BayMimic / The attribute value of the referenced bitmap is not valid-> [Graphic |
Graph. Tables | Bitmap table | Bitmap | type, Single]
33127 / BayMimic / The attribute value of the referenced bitmap is missing-> [Graphic |
Graph. Tables | Bitmap table | Bitmap | file name by default]
33128 / BayMimic / Multiple use of the same attribute value in the referenced bitmap->
[Graphic | Graph. Tables | Bitmap table | Bitmap | file name by default, file1.png]
33127 / BayMimic / The attribute value of the referenced bitmap is missing-> [Graphic |
Graph. Tables | Bitmap table | Bitmap | file name for 'withdrawn open' state]
33128 / BayMimic / Multiple use of the same attribute value in the referenced bitmap->
[Graphic | Graph. Tables | Bitmap table | Bitmap | file name for 'withdrawn open' state,
file4.png]
2.6.7.4 Memo bitmaps
A memo is a specific type of bitmap. They are used by Memo Icons.
Graphic
OI workspace
Window
Mimic (R) has for memo Graphic
Memo icon Memo
(A) bitmap reference
Graph. Tables
Bitmap table
(A) reference index
Bitmap 0
(A) type Memo for OI client
(A) file name for ‘unavailable’ state
(A) file name for 'no note' state file1.png
(A) file name for 'active' state file2.png
file3.png
(A) file name for 'inactive' state
file4.png
• Only a Memo icon can reference a memo bitmap, and only this type.
64126 / Memo icon / The attribute value of the referenced bitmap is not valid
33126 / BayMimic / The attribute value of the referenced bitmap is not valid
Maintenance SCE/EN MF/D10
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]
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)]
06325 / Attributevalue / The format should have the same value for all the database
languages
2.6.8 Alarm Groups
Graphic
(R) uses
Alarm group Datapoint
S0300ENa
73265 / AlarmGroup / Data point used by alarm group is not alarmed-> [Graphic |
ALR.GRP.NOT.OI]
2.6.9 User Profile
A User Profile can’t be called “Administrator”
• 60181 / UserProfile / User Profile name is not allowed (name) -> [name]3
SCE/EN MF/D10 Maintenance
2.6.10 Memo
Graphic
Memo
Bay
(R) is memo of Module
(non)IEC physical device
S0566ENa
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]
Scs
Ethernet network
Scs OI server
Dpt (R) has for profile (R) has events logged on
Dpt profile OI printer
- No archive, no logging
- Archive and logging
- Archive only
S0301ENa
If a Datapoint profile is linked to an OI or computer printer through the "has events logged
on" relation, then its "treatment on event" attribute must be set to the " Logging for OI and/or
computer" value.
In the case of profiles having several attributes "treatment on …", at least one of them must
respect the rule.
23082 / DatapointProfile / The logging definition is not compatible with the relation-> [has
events logged on: OI printer]
Scs
Ethernet network
(R) has for profile Scs (R) has alarm events logged on OI server
Dpt Dpt profile OI printer
- No archive, no logging
- Archive and logging
(A) Alarms / defined - Archive only
- Yes
- No
S0302ENa
If a datapoint profile is linked to an "OI printer" through the "has alarm events logged on"
relation, then:
23082 / DatapointProfile / The logging definition is not compatible with the relation-> [has
alarm events logged on: OI printer]
23083 / DatapointProfile / The alarm definition is not compatible with the relation-> [has
alarm events logged on: OI printer]
SCE/EN MF/D10 Maintenance
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
(R) has for profile (A) SBO mode
DPC DPC profile Direct Execute
BusBar
ATCC fct needs (R) has for profile (A) SBO mode Direct Execute
SPC SPC profile
(R) has for profile (A) SBO mode
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
S0303ENa
Feeder 1
Circuit breaker (R) has for profile (A) SBO mode
Sync CB close (SPC) SPC profile Direct Execute
The possible values of the "SBO mode" attribute of the profile of a Datapoint are:
⇒ Direct Execute
The following table shows the constraints on the value of the "SBO mode" attribute of the
profile of a list of Datapoints:
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)
Example:
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)->
[Scs | DPC profile | SBO mode, SBO Operate Many]
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)->
[Scs | SPC profile | SBO mode, SBO Operate Once]
SCE/EN MF/D10 Maintenance
C264
DNP3 master
DNP3_IED
(R) has for IED address IED SPC Mapping (A) order type
SPC addr. on IED - SBO
- Direct Execute
S0306ENa
For each SPC, DPC or Setpoint datapoint linked to an IED address through the "has for IED
address" relation: the "order type" attribute value of the IED address must match the "SBO
mode" attribute value of the datapoint profile.
23086 / DatapointProfile / The attribute value does not match the datapoint profile
(attribute, profile attribute)-> [order type = Direct execute, SBO mode = SBO Operate Once]
2.7.1.3 Forcing/Substition/Suppression enabling
S0307ENa
The profile of a Datapoint of the System topology must have its "enable Force/Subst/Sup"
set the "No" value.
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)
Example:
23065 / DatapointProfile / The attribute value of the profile is not valid (profile attribute)->
[Scs | SPS profile | enable Force/Subst/Sup, Yes]
2.7.1.4 Alarming/Archiving/Logging/MeanValue Computation for non addressed datapoints
A datapoint which is not addressed can’t be alarmed/archived/logged or computed by OI.
Warn user if profile says other.
The datapoint non addressing possible causes are following:
S0474ENa
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
S0475ENa
S0476ENa
23174 / DatapointProfile / The Datapoint has mean value computed by OI but has no
IEC61850 address
2.7.1.4.4 Archived Datapoint
(R) has for profile Scs (A) State treatment / treatment on event
Dpt Dpt profile - Archive and logging
- Archive only
S0477ENa
06325 / Attributevalue / The format should have the same value for all the database
languages
2.7.2 Acquisition / Control Source definition
For a Datapoint, the Acquisition/Control source is defined through relations.
Prior to the checks definitions, the figures hereafter introduce those relations, per Datapoint
type, as they are defined by the SCE Data Design.
NOTE: If the Acquisition source is defined with the "is managed by" relation,
then the Datapoint is considered as a "System" Datapoint.
SCE/EN MF/D10 Maintenance
C264
DIU200
Counter (R) 'primary input' wired on DI # 0
(R) 'secondary input' wired on DI # 1
(R) is computed by
TIU200
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
IED_@
S0308ENb
C264
DIU200
SPS (R) wired on
DI # 0
DI # 1
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
IED_@
C264
DIU200
DPS (R) 'closed' wired on
DI # 0
(R) 'open' wired on DI # 1
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
IED_@ (1)
(R) has for IED address IED_@ (2)
C264
DIU200
MPS (R) 'state<i>' wired on
DI # 0
(R) 'read inhibit' wired on DI # 1
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
IED_@
C264
(R) 'bit <i>' 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
(R) has for IED address IED Mapping
IED_@
C264
(R) wired on DOU200
SPC DO # 0
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
IED_@
C264
(R) 'closed' wired on DOU200
DPC DO # 0
(R) 'open' wired on DO # 1
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
IED_@ (1)
(R) has for IED address IED_@ (2)
FBD Automation
(R) is controlled by
FBD output
S0314ENb
(*) 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 <i>' 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 # 2
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
IED_@
(R) is managed by
Slow automation
S0315ENb
LSP Site
'Has for FLS server: C264-1'
System
C264
C264-1
(R) has for IEC address C26x IEC Map
IEC_@
S0567ENa
The relation "has for IEC address" must be compatible with the "Ethernet network" protocol
(IEC61850).
21114 / DatapointServer / The relation is not compatible with the Ethernet network
protocol
Example, for an IEC Ethernet Network protocol:
21114 / DatapointServer / The relation is not compatible with the Ethernet network protocol->
[has for IEC address : ACDxST]
Maintenance SCE/EN MF/D10
21045 / DatapointServer / The relation link is not compatible with the datapoint server
Example:
21043 / DatapointServer / The relation link is not compatible with the datapoint server -> [has
for IED address : DPC addr. on IED]
• Counter Datapoint:
Only 1 relation "has for IEC address" is allowed. It must be compatible with the "Ethernet
network" protocol (IEC61850).
• MV Datapoint:
Only 1 relation "has for IEC address" is allowed. It must be compatible with the "Ethernet
network" protocol (IEC61850).
21070 / DatapointServer / The acquisition source is incompatible with the datapoint type
Example:
21070 / DatapointServer / The acquisition source is incompatible with the datapoint type->
[type, Analogue]
Several Bit relations are available : "bit<i> wired on", with i ∈ [00..63].
Among these relations, <i> values must be contiguous and start from 00.
If some of these relations are defined, then the relation "wired on" is forbidden, and vice
versa (these two types of relations are incompatible acquisition sources).
• DPC Datapoint:
Only 1 relation or "has for IEC address" is allowed. It must be compatible with the "Ethernet
network" protocol (IEC61850).
<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.
• SPS Datapoint:
Only 1 relation "has for IEC address" is allowed. It must be compatible with the "Ethernet
network" protocol (IEC61850).
• DPS Datapoint:
Only 1 relation "has for IEC address" is allowed. It must be compatible with the "Ethernet
network" protocol (IEC61850).
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.
Maintenance SCE/EN MF/D10
• MPS Datapoint:
Only 1 relation "has for IEC address" is allowed. It must be compatible with the "Ethernet
network" protocol (IEC61850).
Several State relations are available : "state<i> wired on", with i ∈ [00..15].
Among these relations, <i> values must be contiguous and start from 00.
• Setpoint Datapoint:
Only 1 relation "has for IEC address" is allowed. It must be compatible with the "Ethernet
network" protocol (IEC61850).
Several Bit relations are available : "bit<i> wired on", with i ∈ [00..47].
Among these relations, <i> values must be contiguous and start from 00.
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.7.3 Client / Server definition
For a Datapoint, the Server and Clients identification is based on general rules (see § 2.7.3.1
General definitions ) which can be overwritten by specific rules depending of the Datapoint
type (see § 2.7.3.2 Detailed definitions).
These definitions are based on the SCE Data Design.
2.7.3.1 General definitions
For a Datapoint, 1, and only 1, Server device must be defined.
Special case:
− if the Datapoint is located under a Bay, the device managing the Bay is
automatically considered as the Server ("is managed by" relation link).
− if the Datapoint is located above a Bay, the device managing the associated
voltage level, substation or site (via has for default server relation set at the
corresponding level) is automatically considered as the Server except if it has an
IEC address on a specific server.
A device is Client of a Datapoint, if, and only if, it's not Server of this Datapoint.
Client Server
• A Datapoint must be linked to an address, in the mapping of its Server device, with the
"has for IEC address" relation.
This, if:
− the relation is available for the Datapoint type (i.e., 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 IEC server" relation.
21046 / DatapointServer / The datapoint is not linked to an address of the server (server)
C264
System infos
SystDpt
Board
System infos
SystDpt
SCADA Networks
C26X SCADA prot
System infos
SystDpt
Legacy Networks
Leg_Network
IED
System infos
SystDpt
S0318ENa
C264
DIU200
(R) …wired on
Dpt (1) DI # 0
(R) is computed by TIU200
Dpt (2)
DNP3 master
DNP3_IED
(R) has for IED address IED Mapping
Dpt (3)
IED_@
S0319ENa
C264
C26X SCADA prot
Gtw SCADA Map.
(R) has for SCADA address
Dpt GtwSCADA@
S0320ENa
22193 / DatapointClient / The report usage for client-server relation is missing for
gateway or grouping at client level (server, client)
SCE/EN MF/D10 Maintenance
C264
(R) runs on
FBD automation PLC
C264
(R) runs on PLC
Slow automation
(R) is client of
User Function Dpt (∗3)
DPC | DPS | SPC | SPS | MPS | MV | Setpoint | Counter (∗1)
(R) manages
DPC | DPS | SPC | SPS | MPS | MV | Setpoint | Counter (∗2)
S0323ENa
The Computer "C264" is Server of the "Slow automation" Datapoints (∗3) and of the
managed Datapoints (∗2).
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.
Maintenance SCE/EN MF/D10
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.7.3.2.1.8 DPS-SPS association
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.
(R) is managed by
Feeder C264
Group SPS (R) contains the SPS
(R) contains the DPS SPS
DPS
S0327ENa
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)
SCE/EN MF/D10 Maintenance
A "SPS" (or "DPS") Datapoint can be linked to a "SPC" (or "DPC") Datapoints through
relations "controls on state change".
The Server of the "SPC" (or "DPC") Datapoint is Client of the "SPS" (or "DPS") Datapoint.
NOTE: An "SPC" (or "DPC") Datapoint can be the link of 1, and only 1
"controls on state change" relation.
C264
Server
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.
Maintenance SCE/EN MF/D10
S0330ENa
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.7.3.2.1.13 ATCC function
NOTE: hereafter, the term "wired" for a Datapoint means that the Datapoint
has one of the following relations: "…wired on", "has for IED address",
or "has for IEC address" to an IEC generic IED.
Main ATCC:
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
S0331ENa
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
S0332ENa
In the case of all the Datapoints of the "ATCC fct needs", except the "BusBar voltage"
Datapoint:
⇒ they cannot be wired. As a result, the 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.
SCE/EN MF/D10 Maintenance
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
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.
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
⇒ if it's present then, the "ATCC on/off" Datapoint must be linked to it through the
relation "has for AutoManu dependency".
⇒ 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]
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
(R) is managed by C264 (2) (R) has for IEC server
BusBar (Bay)
ATCC fct needs
Substation
(R) is managed by
ATCC C264 (1)
ATCC_Dpts
Voltage level (R) is managed by C264 (2) (R) has for IEC server
Transformer
transformer
ATCC fct needs
The 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 IEC server".
Moreover the link must at least use report mode.
22192 / DatapointClient / The report usage for client-server relation is missing for ATCC
at client level (server, client)
2.7.3.2.1.14 LHMI
The Computer "C264" is the Server of the Datapoints: "MV", "SPS or DPS", "Tap pos ind".
SCE/EN MF/D10 Maintenance
2.7.3.2.1.15 Local/Remote
Substation
Server
Local/remote DPS C264
Loc/rem ctrl DPC
S0338ENa
If the two Datapoints "Local/remote DPS" and "Loc/rem ctrl DPC" are present, they must
have the same Server device.
Substation
Server
Local/remote DPS C264 (1)
Loc/rem ctrl DPC
If a Taking-Control function is defined then, the "Loc/rem ctrl DPC" must be present.
GTW
The GTW is server of the "Slow automation" Datapoints (3) and of the managed Datapoints
(2).
The GTW is client of the used Datapoints (1).
Maintenance SCE/EN MF/D10
2.7.3.2.2 OI server
2.7.3.2.2.1 System Datapoints
OI server
System infos
SystDpt
OI printer
System infos
SystDpt
S0340ENa
S0341ENa
All the "OI server" devices (except backups and datapoints which are not auto-addressed)
are Clients of each Alarmed Datapoint.
2.7.3.2.2.3 Logged Datapoints
Scs
Ethernet network
(R) has for profile Scs (R) has events logged on OI server
Dpt Dpt profile OI printer
(R) has alarm events logged on
S0342ENa
The "OI server" is Client of the Datapoint "Dpt", except datapoints which are not auto-
addressed.
2.7.3.2.2.4 Mean value computation Datapoint
All the "OI server" devices (except backups and datapoints which are not auto-addressed)
are Clients of each Datapoint having a Mean Value computation.
2.7.3.2.2.5 Archived Datapoint
(R) has for profile Scs (A) State treatment / treatment on event
Dpt Dpt profile - Archive and logging
- Archive only
S0344ENa
All the "OI server" devices (except backups and datapoints which are not auto-addressed)
are Clients of each archived Datapoint.
SCE/EN MF/D10 Maintenance
S0345ENa
The "OI server" is Client of all the Datapoints used by a graphical animation.
2.7.3.2.2.7 Datapoint used by Alarm Group
Graphic
(R) is used by
Alarm group Dpt
S0346ENa
All the "OI server" devices (except backups) are Clients of each Datapoint used by an
"Alarm group".
2.7.3.2.3 OI client
2.7.3.2.3.1 System Datapoints
System infos
OI client link
S0347ENa
The "OI server" is Server of the System Datapoint "OI client link" of the "OI client".
2.7.3.2.4 IEC generic IED
2.7.3.2.4.1 System Datapoints
System infos
SystDpt
S0348ENb
The "IEC gen IED" is Server of each Datapoint linked to an IEC address of its mapping.
Maintenance SCE/EN MF/D10
IEC gateway
System infos
SystDpt
Usual protocol
System infos
SystDpt
IEC gateway
Usual protocol
Gtw SCADA Map.
…
(R) has for SCADA address
SCADA@ Dpt
The "IEC gateway" is Client of each Datapoint linked to a SCADA address of its mapping.
IEC gateway
(R) is transmitted on IEC 61850
61850 protocol Dpt
02256 / OI Bay / An OI bay can’t be clients of more than 500 datapoints (current number
of datapoints)
• The Klaxon usage value on a Standard Command Banner of an OI Bay must be set to
No, because OI bay doesn’t manage Klaxon option.
76255 / OI Bay Klaxon usage value on Standard Command Banner of an OI Bay must
be set to No (OI bay),
• The alarm group used in a Mimic of an OI bay must have at least one datapoint client
of this OI Panel.
SCE/EN MF/D10 Maintenance
76264/ OI Bay / Alarm group used by the OI bay must have at least one datapoint client
of OI bay-> [Graphic | ALR.GRP.NOT.OI],
2.7.4 Datapoints constraints
2.7.4.1 MV Datapoints sent on 'set' or 'close' state
The two relations "is sent on set state of" and "is sent on closed state of" are mutually
exclusive.
S0353ENa
If the attribute "type" of the "MV" Datapoint is set to a "Digital…" value, then the following
constraint between the two attributes must be respected:
C264
DNP3 master
DNP3_IED
IED Mapping
(R) has for IED address (A) contact type
DPC IED_@ (1) - Unused
(R) has for IED address IED_@ (2) - open
- close
(R) has for IED address
DPS IED_@ (3)
(R) has for IED address IED_@ (4)
S0354ENa
A "DPC" or "DPS" Datapoint can have 1 or 2 relation(s) "has for IED address".
• In the case of 1 IED address the attribute "contact type" of the IED address must be set
to the "Unused" value.
• In the case of 2 IED addresses the attribute "contact type" of one of the IED addresses
must be set to the "open" value, and the attribute "contact type" of the other IED
address must be set to the "close" value.
18134 / xxxAddressOnIED / The attribute value of the referenced IED address is not
valid
Examples:
18134 / xxxAddressOnIED / The attribute value of the referenced IED address is not valid->
[Scs | Ethernet network | C264 | DNP3 master | DNP3_IED | IED Mapping | IED DPC
Mapping | DPC addr. on IED | contact type, Unused]
2.7.4.4 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)
S0355ENa
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)
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: Output,
has for IED address: DPC addr. on IED]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: FBD
output, is controlled on state change of: Substation DPS]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: FBD
output, has for AutoManu dependency: Substation DPS]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: FBD
output, has for feedback: Substation DPS]
39044 / DatapointServer / The relation types are not compatible-> [is controlled by: FBD
output, has for local/remote dependency: Local/remote DPS]
FBD automation
(R) uses DPC
Input (1) DPC
(R) uses SPC SPC
Input (2)
S0356ENa
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:
DPC DPS
(R) has for feedback
SPS
SPC DPS
(R) has for feedback
SPS
SetPoint MV
(R) has for feedback MPS
S0357ENa
For each "DPC", "SPC" or "Setpoint" Datapoint, 2 relations "has for feedback" are available,
but they are mutually exclusive.
− if one of them is a "Wired" Datapoint, the other one must be "Wired" too.
Maintenance SCE/EN MF/D10
− if one of them is a "System" Datapoint, the other one must be "System" too.
− if one of them is linked to an "IEC gen IED" through the relation "has for IEC
address", this relation must also be defined for the other one.
This rule does not concern the CB Computed Pos datapoint when it is feedback of a wired
SPC/DPC control of a breaker.
NOTE: Here, the term "Wired" means that the datapoint is linked to a digital or
analogue channel of a computer, or linked to an IED address, else it's
"System".
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
Case of the Circuit-breaker "Lock control SPC" Datapoint:
Feeder
Circuit breaker
Lock control SPC DPS
(R) has for feedback SPS
S0358ENa
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
(R) has for feedback on/off ctrl DPC
on/off ctrl SPC
on/off DPS
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.
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" ]
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"
DPC DPS
(R) has for AutoManu dependency
SPS
SPC DPS
(R) has for AutoManu dependency
SPS
SetPoint DPS
(R) has for AutoManu dependency SPS
S0362ENa
For each "DPC", "SPC" or "Setpoint" Datapoint, 2 relations "has for AutoManu dependency"
are available, but they are mutually exclusive.
Substation
Local/remote DPS
Loc/rem ctrl DPC
Operating Mode MPS
S0363ENb
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 wired, then "Loc/rem ctrl DPC" is not mandatory but, if it's
present, it must be wired.
• The two datapoints for operating mode of the substation are exclusive (Local/Remote
Substation DPS and Operating mode MPS)
62196 / Operating mode / Datapoints for operating mode are exclusives (Local/Remote
Substation DPS and Operating mode MPS)
Feeder
Local/remote DPS
Loc/rem ctrl DPC
S0364ENa
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.
(R) is managed by
Feeder (1) C264 (A) HMI type
Local/remote DPS GHU200 Simple
(R) is managed by
Feeder (2)
Local/remote DPS
S0366ENa
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".
Substation
Local/remote DPS
Voltage level
Feeder
Local/remote DPS
(A) Substation mode dependency
DPC Yes
(A) bay mode dependency Yes
If, under a Substation, a "DPC" or "SPC" Datapoint has one attribute "Substation mode
dependency" set to "Yes", then the Substation "Local/remote DPS" or “operating mode MPS”
Datapoint datapoint must be present.
There are four substation mode dependency attributes:
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.
Feeder
SBMC SPS
SBMC control SPC
S0368ENa
• if "SBMC SPS" is present and not wired, then "SBMC control SPC" must be present
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
S0369ENa
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.
S0370ENa
A "Klaxon" refers to a set of Datapoints. This set contains all the Datapoints which are in the
sub-tree of each "VoltageLevel" and "IEC PhysicalDevice" linked to the klaxon through the
relation "warns audibly".
In the set of Datapoints, at least 1 Datapoint must fulfil the following conditions:
− it must be linked to a Datapoint Profile which has its attributes "Alarms / defined"
and "Alarms / audible" set to the "Yes" value.
A given Voltage level or 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 IEC PhysicalDevice is associated more than once to the
same klaxon
2.7.4.11 SPC managing a Klaxon
S0511ENa
The klaxons can be managed by any SPC. These SPC has to be permanent.
02291 / CapacityLimits / Invalid count of wired counter datapoint for this computer or
rack (count, maximum)-> [32, 16]
2.7.4.14 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
integrate an MV must be an energy counter.
<23183> / DptProfile / A profile of a transient SPC with control popup, must have “Order
off usage” set to No (SPC)
2.7.4.18 TM computed by TMU board.
On a TMU board, it can’t 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” measurement
type are not allowed:
<57190> / DptMV / The measure type is not allowed for delta topology (measure type,
TMU board)
<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:
<57230> / DptMV / The measure type is not allowed for the 3Vpp+Vb connection type
(measure type, TMU210 board)
On TMU200 / TMU220, additional measurement values are available :
<61185> / DptRaiseLower / A Raise/Lower DPC SBO Many, must have Command Panel
Assignment set to No
2.7.4.20 Datapoint Mapping function
Any configuration database can't contain more than 100 Origin datapoints.
63199 / MaxTargetDpt / The maximum number of Target Datapoints per Origin datapoint
is reached (count, maximum)
Any Target datapoint must map only one Origin datapoint.
63200 / UnicityOriginDpt / A MappingxPS datapoint (target) must map only one Origin
Datapoint.(count, maximum)
Maintenance SCE/EN MF/D10
Site
Server
Origin datapoint C264-1
(SPS | DPS | MPS | MV)
Has for Client
(R) IsMappedOn
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.
• 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
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)
SCE/EN MF/D10 Maintenance
Examples:
57237 / MVDatapoint / Threshold must be greater than previous configured one with at least
given difference (threshold, current value, previous value, difference)-> [low-low threshold,
50.0, 30.0, 25.0]
2.7.4.22 MV datapoints Deadband value
A MV datapoints with ‘deadband’ value equals to 0 and transmission on event configured on
‘According to a ‰ of full scale’ or ‘According to a ‰ of current value’ value must be issued
from IEC 103 IED and must have ‘ASDU number‘ equals to 4 on its IED address.
57266 / MV Datapoint / Only MV issue from IEC 103 IED with ASDU number equals to 4
can have a deadband value equals to 0
2.7.4.22 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.
NAME CONSTRAINTS
OI Server Mimic
Device link Symbol
Is controled by
Send FSS order
manages
SPS Multistate
manages
Discrepancy MS
Is graphically used by
Var. Text
S0568ENa
73238 / Datapoint / Device link datapoint of OI server can’t be used in a mimic (graphical
element)
Maintenance SCE/EN MF/D10
SWITCHGEAR POS
73253 / Datapoint / Relation 'is Transmitted on IEC 61850 SCADA network' is invalid for
this datapoint under circuit breaker module
SCE/EN MF/D10 Maintenance
BLANK PAGE
Problem Analysis SCE/EN PR/D10
PROBLEM ANALYSIS
Problem Analysis SCE/EN PR/D10
CONTENT
4. WINDOW MANAGING 6
SCE/EN PR/D10 Problem Analysis
BLANK PAGE
Problem Analysis SCE/EN PR/D10
4. WINDOW MANAGING
Managing dockable windows: after many user manipulations, the position and the
displaying of dockable windows could be inconsistent.
Workaround: click on the button that is located in the main toolbar or choose the menu
item window/reset perspective. The default perspective is displayed again.
Glossary PACiS/EN LX/D10
GLOSSARY
Glossary PACiS/EN LX/D10
Page 1/14
CONTENTS
Page 2/14
BLANK PAGE
Glossary PACiS/EN LX/D10
Page 3/14
Page 4/14
2. GLOSSARY
AC Alternating Current
AccI Accumulator Input
ACSI Abstract Communication Service Interface
Mapping from the standard IEC 61850 abstract specification of
communication service to a concrete communication infrastructure based
on CORBA.
A/D Analog/Digital
ADC Analog to Digital Converter
AE qualifier Application Entity qualifier
Used internally by IEC 61850 to identify a server application
AI Analog Input (Measurement Value including state attribute)
Commonly Voltage or current DC signals delivered by transducers, and
representing an external value (refer to CT/VT for AC).
AIS Air Insulated Substation
AIU Analog Input Unit ( C264 Bay Computer board name for DC Analog Input)
Alarm An alarm is any event tagged as an alarm during the configuration phase
AO Analog Output
Value corresponding to a desired output current applied to a DAC.
AOU Analog Output Unit ( C264 Bay Computer board name for Analog Output)
API Application Programming Interfaces
AR Auto-Reclose
ARS Auto-Recloser
ASCII American Standard Code for Information Interchange
ASDU Application Specific Data Unit
Name given in the OSI protocol for applicable data (T103, T101..)
ASE Applied System Engineering
ATCC Automatic Tap Change Control
Automation in charge of secondary voltage regulation, more specific than
AVR
AVR Automatic Voltage Regulator
Automatic system used to regulate the secondary voltage by automatic
tap changer control (see ATCC). Set of features can be added, see
chapter C264 FT.
Bay Set of LV, MV or HV equipment (switchgears and transformers) and
devices (Protective, Measurement…) usually encompassing a Circuit
Breaker and ancillary devices, and controlled by a bay computer.
BCD Binary Coded Decimal
One C264 supported coding on a set of Digital Inputs, that determine a
Digital Measurement, then a Measurement value (with specific invalid
code when coding is not valid). Each decimal digit is coded by 4 binary
digits.
BCP Bay Control Point
Name given to the device or part used to control a bay. It can be Mosaic
Panel, C264 LCD, usually associated with Remote/Local control.
BCU Bay Control Unit
Name given to the C264 controlling a bay. Usually in contrast to
Standalone.
Glossary PACiS/EN LX/D10
Page 5/14
Page 6/14
Page 7/14
Page 8/14
Page 9/14
Page 10/14
Page 11/14
Page 12/14
Page 13/14
TM Analog Measurement
TMU Transducer-Less Measurement Unit
Topological Interlocking algorithm, based on evaluation of topological information of
interlocking the switchgear arrangement in the HV network, the switchgear type and
position, and defined rules for controlling this kind of switch (e.g. continuity
of power supply)
TPI Tap Position Indication (for transformers).
Frequently acquired via a Digital Measurement
TS Logic position
Page 14/14
Voltage level Set of bays, whose plants & devices deal with the same voltage (for
example, 275 kV)
VT Voltage Transformer
Electric device connected to process and extract a voltage measurement.
By extension, part of a device (C264) that receives this AC value and
converts it to a numerical measurement value. VTs are wired in parallel.
Schneider Electric
35 rue Joseph Monier
92506 Rueil-Malmaison
FRANCE
Phone: +33 (0) 1 41 29 70 00
Fax: +33 (0) 1 41 29 71 00
www.schneider-electric.com Publishing: Schneider Electric
Publication: SCE/EN T/D10 02/2013