Académique Documents
Professionnel Documents
Culture Documents
K02 03 20060309
Page: 1
OMICRON
K02 03 20060309
OMICRON
K02 03 20060309
Page: 2
Objectives
DATA CONSITENCY:
between domains (communication, HMI, graphical,
automation, etc.)
between devices (HMI, gateway, bay computer,
protections, etc)
EASE OF USE
Implicit processing (data, logic)
No need to be an IEC 61850 expert
LIFE CYCLE APPROACH
Manage evolutions during the system life
Handle legacy devices
OMICRON
K02 03 20060309
Page: 3
4 Domains in 1 Tool
Electrical Part
Key features
Create/Delete Relations
(bindings) between domains
System Part
Graphical Part
Automation Part
OMICRON
K02 03 20060309
Page: 4
Evolution
TEMPLATES
Instances
A template can be made of
Graphical, Electrical, System and
Automation domains.
It might be imported (typ. An IED)
Automatic
CB1
CB2
CB3
CB1
CB2
CB3
QUERIES
Database on
Multiple criteria
OMICRON
K02 03 20060309
Page: 5
OMICRON
K02 03 20060309
Page: 6
OMICRON
K02 03 20060309
Page: 7
OMICRON
K02 03 20060309
Page: 8
UML
The heart of object-oriented problem
solving is the construction of a model.
The model abstracts the essential
details of the underlying problem from
its usually complicated real world.
Several modeling tools are wrapped
under the heading of the UML, which
stands for Unified Modeling
Language.
OMICRON
K02 03 20060309
Page: 9
UML
The Unified Modeling Language (UML)
is a standard language for specifying,
visualizing, constructing, and
documenting the artifacts of different
simple or complex systems.
UML uses mostly graphical notations
to express the design of software
projects. Using the UML helps project
teams communicate, explore potential
designs, and validate the architectural
design of the system.
OMICRON
K02 03 20060309
Page: 10
UML
The UML is applicable to objectoriented problem solving.
A model is an abstraction of the
underlying problem.
The domain is the actual world from
which the problem comes.
Models consist of objects that interact
by sending each other messages.
Objects have things they know
(attributes) and things they can do
(services).
OMICRON
K02 03 20060309
Page: 11
OMICRON
K02 03 20060309
Page: 12
K02 03 20060309
Page: 13
OMICRON
K02 03 20060309
Page: 14
K02 03 20060309
Page: 15
OMICRON
K02 03 20060309
Page: 16
Meaning
0..1
0..* or *
1..*
OMICRON
K02 03 20060309
Page: 17
SERVER
ObjectName
ObjectReference
Generalization
Association
1..*
LOGICAL-DEVICE
Aggregation
1..*
LOGICAL-NODE
Multiplicity
1..*
DATA
1
1..*
DataAttribute
OMICRON
K02 03 20060309
Page: 18
InstanceName1:Class Name
InstanceName2:Class Name
InstanceNameN:Class Name
OMICRON
K02 03 20060309
Page: 19
Control Object
Oper_req(off)
Oper_rsp+
Report_req(off)
Activation bar
Message
OMICRON
K02 03 20060309
Page: 20
K02 03 20060309
Page: 21
Sel_req[Test ok]^client.Sel_rsp+
Ready
cancel_req^client.cancel_rsp+
Timeout
TimOper_req[Test not ok]^client.TimOper_rspOper_req[Test not ok]^client.Oper_rspOper_req[Test ok, sboClass=OPERATE_ONCE]^client.Oper_rsp+
Oper_req[Test ok, sboClass=OPERATE_MANY]^client.Oper_rsp+
TimOper_req[Test ok]^client.TimOper_rsp+
OMICRON
K02 03 20060309
Page: 22
Why XML?
Offers a method for putting structured data
into a text file
Looks a bit like HTML
Is machine readable, but human intelligible
Comprises of a family of technologies
Is verbose
Is relatively new, but has honorable roots
Is license free, platform-independent and
well supported
OMICRON
K02 03 20060309
Page: 23
Why XML?
Extensible means that it can be advanced
to meet specific needs by creating
descriptive tags to fit the requirements of
the problem domain
Files can be edited using off-the-shelf text
editors
Availability of specialized tools
OMICRON
K02 03 20060309
Page: 24
OMICRON
K02 03 20060309
Page: 25
Markup description
Markup declaration open
Element name
Element termination
Element content
OMICRON
K02 03 20060309
Page: 26
XML schemas
Need for a mechanism to enforce
constraints
Defines document content rules
Describes the structure that determines:
order of elements
presence of elements and attributes
indication of number of expected occurrences
OMICRON
K02 03 20060309
Page: 27
OMICRON
K02 03 20060309
Page: 28
Displaying XML
Since XML defines the data structure, it will
not display a page by itself.
We must use a formatting technology, such
as CSS or XSL to display XML-tagged
documents in a Web browser.
Cascading Style Sheets (CSS), are the current
way to display XML documents in a Web
browser.
CSS is a means of assigning display values
to page elements.
OMICRON
K02 03 20060309
Page: 29
OMICRON
K02 03 20060309
Page: 30
OMICRON
K02 03 20060309
Page: 31
XML Applications
Part 6 of the IEC 61850 standard specifies
a description language for configurations
of electrical substation IEDs Substation
Configuration Language (SCL) based on
XML Version 1.0
It is used to describe IED configurations
and communication systems according to
parts 5 and 7 of this standard.
Description of the relations between the
substation automation system and the
substation (switchyard) itself
OMICRON
K02 03 20060309
Page: 32
XML Applications
For easier engineering of application
functions.
SCL allows the description of an IED
configuration to be passed to a
communication and application system
engineering tool
Its main purpose is to allow the
interoperable exchange of communication
system configuration data between an IED
configuration tool and a system
configuration tool of different
manufacturers.
OMICRON
K02 03 20060309
Page: 33
XML Applications
Example from IEC 61850, Part 6 - Substation
Configuration Language(SCL):
OMICRON
K02 03 20060309
Page: 34
Substation Configuration
Language SCL
Must be capable of describing:
A system specification in terms of the
single line diagram, and allocation of
logical nodes (LN) to parts and equipment
of the single line to indicate the needed
functionality.
Pre-configured IEDs with a fixed number of
logical nodes (LNs), but with no binding to
a specific process . may only be related to
a very general process function part.
Pre-configured IEDs with a pre-configured
semantic for a process part of a certain
structure, for example a double busbar GIS
line feeder.
OMICRON
K02 03 20060309
Page: 35
Substation Configuration
Language SCL
Must be capable of describing:
Complete process configuration with all
IEDs bound to individual process functions
and primary equipment, enhanced by the
access point connections and possible
access paths in subnetworks for all
possible clients.
As above, but additionally with all
predefined associations and client server
connections between logical nodes on data
level. This is needed if an IED is not
capable of dynamically building
associations or reporting connections
(either on the client or on the server side).
OMICRON
K02 03 20060309
Page: 36
Substation Configuration
Language SCL
Substation section: describes the
substation single line diagram, and its
binding to logical nodes as well as the
placement of logical nodes onto IEDs.
Thus also the binding of IEDs to
substation parts and substation devices
is defined.
Communication section: describes the
communication connections between
IEDs in terms of connecting
communication links.
OMICRON
K02 03 20060309
Page: 37
Substation Configuration
Language SCL
IED section: describes the capabilities
(configuration) of one or more IEDs, and
the binding to logical nodes on other
IEDs.
LNType section: defines which data
objects are actually contained within the
logical node instances defined for the
IEDs.
OMICRON
K02 03 20060309
Page: 38
Objectives
Substation
1
1
Voltage
level
1
Bay
1
Device
1 1
0..5
CBR
Terminal
1
ConNode
0..*
0,1
1
IED
1
Subdevice
Phase
DIS
PTR
LNode
1
1..*
Data
associations
1
1..*
1
AccessPoint
Server
LDevice
1..2
1..*
1..*
1..*
0,1
1
Functional / substation structure
Subnetwork
Product / IED structure
Router
Communication structure
OMICRON
K02 03 20060309
Page: 39
OMICRON
K02 03 20060309
Page: 40
SCL Examples
OMICRON
K02 03 20060309
Page: 41
OMICRON
K02 03 20060309
Page: 42
SCL Files
Data exchange from a system
specification tool to the system
configuration tool. This file describes
the single line diagram of the substation
and the required logical nodes. The file
extension shall be .SSD for System
Specification Description.
Data exchange from the IED
configuration tool to the system
configuration tool. This file describes
the capabilities of an IED. The file
extension shall be .ICD for IED
Capability Description.
OMICRON
K02 03 20060309
Page: 43
SCL Files
Data exchange from the system
configuration tool to IED configuration
tools.
This file contains all IEDs,
communication configuration and
substation description sections.
The file extension shall be .SCD for
Substation Configuration Description.
OMICRON
K02 03 20060309
Page: 44
SCL Files
Data exchange from the IED
configuration tool to the IED. It
describes an instantiated IED within a
project.
The communication section contains
the current address of the IED. The
substation section related to this IED
may be present and then shall have
name values assigned according to the
project specific names.
It is an SCD file, possibly stripped
down to what the concerned IED shall
know.
The file extension shall be .CID for
Configured IED Description.
OMICRON
K02 03 20060309
Page: 45
K02 03 20060309
Page: 46
Redundancy requirements
Communications architecture
Substation level functions
Other as necessary
All of the above should be produced by
a system specification tool that
provides as an output an SSD file.
OMICRON
K02 03 20060309
Page: 47
OMICRON
K02 03 20060309
Page: 48
The Revolution
Need for some further development,
including:
Completion of the settings parts of the
logical nodes class models
Inclusion of the settings in the ICD and
CID files
Harmonization between the CIM model
and the IEC 61850 model
Extensions in the system model to cover
the needs of coordination and analysis
tools
Addition of IED setting configuration
functions in the System Configuration
tools
OMICRON
K02 03 20060309
Page: 49
The Revolution
As a result it will be possible to extend
the use of the SCD files for the following
substation automation systems
engineering tasks:
Automatic creation of the graphical user
interface from the SCD file, including the
different screen layouts
Automatic mapping of the different
measurements and status information
from the IEDs to the substation HMI
Automatic configuration of the IED or
substation protection and control system
testing process
Automatic substation event analysis
OMICRON
K02 03 20060309
Page: 50
The Benefits
Quite significant
Reduce the costs for system design
Improve factory and site acceptance
testing
Improve the maintenance process
Improve the overall quality of the
substation automation system
OMICRON
K02 03 20060309
Page: 51
ICD
File
IEC 61850
Standard System
Configuration Tool
SCD
File
Network
System
Simulator
Scheme
Testing Tool
IEC 61850
Standard Test
Configuration
Tool
Other Test
Modules
IED
IED
IED
Simulator
Simulator
Simulator
MU
MU
Simulator
MU
Simulator
Simulator
Test Device
OMICRON
K02 03 20060309
Page: 52