OMICRON

Page: 1 K02 03 20060309

K02 03 20060309
Substation Configuration
Substation Configuration
Language Based Engineering
Language Based Engineering
Dr. Alexander Apostolov
OMICRON Page: 2 K02 03 20060309
SAS Engineering Tools
SAS Engineering Tools
The IEC 61850 series defines requirements
on engineering-tools, especially for
system configuration and
parameterization.
To be able to exchange the device
descriptions and system parameters
between tools of different manufacturers
in a compatible way, IEC 61850-6 defines a
substation configuration language (SCL).
SCL allows to describe the capabilities of
an IED in terms of the models of IEC
61850-5 and IEC 61850-7-x for import to the
system engineering tool.
OMICRON Page: 3 K02 03 20060309
Objectives
Objectives
DATA CONSITENCY:
between domains (communication, HMI, graphical,
automation, etc.)
between devices (HMI, gateway, bay computer,
protections, etc)
LIFE CYCLE APPROACH
Manage evolutions during the system life
Handle legacy devices
LARGE DATA FLOWS:
More data than with legacy communication protocols
More flows (client/servers, peer-to-peer), not only
master slave
EASE OF USE
Implicit processing (data, logic)
No need to be an IEC 61850 expert
OMICRON Page: 4 K02 03 20060309
Data consistency: Concepts
Data consistency: Concepts
4 Domains in 1 Tool
Electrical Part
System Part
Graphical Part
Automation Part
EDITORS
Object oriented with hierarchical domain approach in line with IEC 61850 hierarchy
Key features
Create/Delete Relations
(bindings) between domains
Template management (per
domain and composite)
Check per editor and global
(completion, consistency)
OMICRON Page: 5 K02 03 20060309
Large volume of data handling:
Large volume of data handling:
Concepts
Concepts
Graphical template example
Instances
CB1
CB2
CB3
Automatic
CB1
CB2
CB3
Evolution
TEMPLATES
A template can be made of
Graphical, Electrical, System and
Automation domains.
It might be imported (typ. An IED)
QUERIES
Database on
Multiple criteria
OMICRON Page: 6 K02 03 20060309
SAS Engineering Tools
SAS Engineering Tools
Successful implementation of Substation
Automation Systems (SAS) requires the
availability of appropriate engineering
tools
Used to determine and to document the
application specific functionality and the
integration of devices into the SAS.
Project design tools
Configuration tools
Documentation tools
OMICRON Page: 7 K02 03 20060309
SAS Engineering Tools
SAS Engineering Tools
SCL is used also to describe all data
needed to define system parameters for a
single IED.
This includes especially the binding of the
IED and its functions to:
the substation itself, in terms of its single
line diagram
to the communication system.
The Substation Configuration Language is
based on XML
OMICRON Page: 8 K02 03 20060309
TLAs
TLAs
and
and
FLAs
FLAs
SGML - Structured Generalized Markup
Language - 1988
HTML HyperText Markup Language (current
version 4.01 is meant to be final)
XML - eXtensible Markup Language - 1998
XSL - eXtensible Stylesheet Language
CSS - Cascading Style Sheets
XHTML - HTML reformulated as an
application of XML
OMICRON Page: 9 K02 03 20060309
UML
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 Page: 10 K02 03 20060309
UML
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 Page: 11 K02 03 20060309
UML
UML
The UML is applicable to object-
oriented 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 Page: 12 K02 03 20060309
UML Modeling Diagrams
UML Modeling Diagrams
Use case diagrams
Class diagrams
Object diagrams
Sequence diagrams
Collaboration diagrams
Statechart diagrams
Activity diagrams
Component diagrams
Deployment diagrams
OMICRON Page: 13 K02 03 20060309
UML: Use Case Diagrams
UML: Use Case Diagrams
Use case diagrams describe what a
system does from the standpoint of an
external observer. The emphasis is on
what a system does rather than how.
A scenario is an example of what
happens when someone interacts with
the system.
An actor is who or what initiates the
events involved in that task. Actors are
simply roles that people or objects
play.
The connection between actor and use
case is a communication association.
OMICRON Page: 14 K02 03 20060309
UML: Class Diagrams
UML: Class Diagrams
Class diagram gives an overview of a
system by showing its classes and the
relationships among them. Class
diagrams are static -- they display what
interacts but not what happens when
they do interact.
UML class notation is a rectangle
divided into three parts: class name,
attributes, and operations.
Class Name
Attribute 1
Attribute 2
:
Attribute n
Service 1
Service 2
:
Service n
OMICRON Page: 15 K02 03 20060309
UML: Class Diagrams
UML: Class Diagrams
Association -- a relationship between
instances of the two classes. There is an
association between two classes if an
instance of one class must know about the
other in order to perform its work. In a
diagram, an association is a link
connecting two classes.
Aggregation -- an association in which one
class belongs to a collection. An
aggregation has a diamond end pointing to
the part containing the whole.
Generalization -- an inheritance link
indicating one class is a superclass of the
other. A generalization has a triangle
pointing to the super-class.
OMICRON Page: 16 K02 03 20060309
UML: Class Diagrams
UML: Class Diagrams
Multiplicity of an association end is the
number of possible instances of the
class associated with a single instance
of the other end.
Multiplicities are single numbers or
ranges of numbers.
OMICRON Page: 17 K02 03 20060309
UML: Class Diagrams
UML: Class Diagrams
Multiplicities Meaning
0..1 0 or 1 instance. The notation
n . . m indicates n to m instances.
0..* or * No limit on the number of instances
(including none).
1 exactly one instance
1..* at least one instance
OMICRON Page: 18 K02 03 20060309
UML: Class Diagrams
UML: Class Diagrams
DATA
DataAttribute
1..*
1
1..*
1
LOGI CAL-NODE
1..*
1
1..*
1
LOGICAL-DEVICE
1..*
1
1..*
1
Name
ObjectName
ObjectReference
SERVER
1..*
1
1..*
1
Association
Aggregation
Generalization
Multiplicity
OMICRON Page: 19 K02 03 20060309
UML: Object Diagrams
UML: Object Diagrams
Object diagrams show instances
instead of classes.
They instantiate class diagrams
InstanceName1:Class Name
InstanceName2:Class Name InstanceNameN:Class Name
OMICRON Page: 20 K02 03 20060309
UML: Sequence Diagrams
UML: Sequence Diagrams
Class and object diagrams are static
model views.
Interaction diagrams are dynamic. They
describe how objects collaborate.
A sequence diagram is an interaction
diagram that details how operations
are carried out -- what messages are
sent and when.
Sequence diagrams are organized
according to time.
Client
Control Object
Oper_req(off)
Oper_rsp+
Report_req(off)
Activation bar
Message
OMICRON Page: 21 K02 03 20060309
UML:
UML:
Statechart
Statechart
Diagrams
Diagrams
Objects have behaviors and state. The
state of an object depends on its
current activity or condition.
A statechart diagram shows the
possible states of the object and the
transitions that cause a change in
state.
States are rounded rectangles.
Transitions are arrows from one state
to another.
Events or conditions that trigger
transitions are written beside the
arrows.
OMICRON Page: 22 K02 03 20060309
UML:
UML:
Statechart
Statechart
Diagrams
Diagrams
-
-
SBO
SBO
Ready
Oper_req[Test not ok]^client.Oper_rsp-
WaitForActivationTime
entry / start timer
TimOper_req[Test not ok]^client.TimOper_rsp-
Oper_req[Test ok, sboClass=OPERATE_MANY]^client.Oper_rsp+
TimOper_req[Test ok]^client.TimOper_rsp+
timer expired[Test ok, sboClass=OPERATE_MANY] ^client.TimOper_rsp+
Unselected
Timeout
cancel_req^client.cancel_rsp+
timer expired[Test not ok] ^client.TimOper_rsp-
Sel_req[Test not ok]^client.Sel_rsp-
Sel_req[Test ok]^client.Sel_rsp+
timer expired[Test ok, sboClass=OPERATE_ONCE] ^client.TimOper_rsp+
Oper_req[Test ok, sboClass=OPERATE_ONCE]^client.Oper_rsp+
OMICRON Page: 23 K02 03 20060309
Why XML?
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 Page: 24 K02 03 20060309
Why XML?
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 Page: 25 K02 03 20060309
File name extensions
File name extensions
.xml - generic XML file extension
.xsl - Extensible Markup Language File
.xsd - Extensible Schema Definition
.xdr - XML Data Reduced Schema
.dtd - Data Type Definition
OMICRON Page: 26 K02 03 20060309
Markup description
Markup description
<pickup>1.5</ pickup >
Element name
Element content
Markup declaration open Markup declaration close
Element termination
OMICRON Page: 27 K02 03 20060309
XML schemas
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
The above rules are incorporated into a
Schema that defines the structure of an
XML instance
OMICRON Page: 28 K02 03 20060309
XML Documents Validation
XML Documents Validation
XML documents are validated by XML
parsers or other development tools
A " Well Formed" XML document is a
document that conforms to the XML
syntax rules
A " Valid" XML document is a " Well
Formed" XML document which conforms
to the rules of a Document Type Definition
(DTD) or other schema.
OMICRON Page: 29 K02 03 20060309
Displaying XML
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 Page: 30 K02 03 20060309
SAS Engineering Process
SAS Engineering Process
OMICRON Page: 31 K02 03 20060309
Example MMXU
Example MMXU
-
-
Notepad view
Notepad view
OMICRON Page: 32 K02 03 20060309
XML Applications
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 Page: 33 K02 03 20060309
XML Applications
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 Page: 34 K02 03 20060309
XML Applications
XML Applications
Example from IEC 61850, Part 6 - Substation
Configuration Language(SCL):
OMICRON Page: 35 K02 03 20060309
Substation Configuration
Substation Configuration
Language SCL
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 Page: 36 K02 03 20060309
Substation Configuration
Substation Configuration
Language SCL
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 Page: 37 K02 03 20060309
Substation Configuration
Substation Configuration
Language SCL
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 Page: 38 K02 03 20060309
Substation Configuration
Substation Configuration
Language SCL
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 Page: 39 K02 03 20060309
Objectives
Objectives
Voltage
level
Bay Device
CBR
ConNode
DIS
PTR
IED AccessPoint Server LDevice
LNode
Subnetwork
1..*
1..2
1..*
1..*
1
1 1
1
1
1
1
1
Data
1
1
1
1..*
1..*
associations
0,1
0,1
Functional / substation structure
Product / IED structure
Communication structure
0..*
Substation
1
1
Terminal
1
1
0..5
Subdevice
Phase
1
Router
OMICRON Page: 40 K02 03 20060309
SCL UML Diagram Example
SCL UML Diagram Example
OMICRON Page: 41 K02 03 20060309
SCL Examples
SCL Examples
OMICRON Page: 42 K02 03 20060309
SCL UML Diagram Example: IED
SCL UML Diagram Example: IED
OMICRON Page: 43 K02 03 20060309
SCL Files
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 Page: 44 K02 03 20060309
SCL Files
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 Page: 45 K02 03 20060309
SCL Files
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 Page: 46 K02 03 20060309
SAS Engineering Process
SAS Engineering Process
Define the functional specification
according to the approved protection,
automation and control concepts and
users standards. This is done using
the substation one line diagram and
defining:
Protection functions required for each
primary substation or system
component
Measurements and status information
needed
Controls to be used
Reporting requirements
Monitoring and recording requirements
OMICRON Page: 47 K02 03 20060309
SAS Engineering Process
SAS Engineering Process
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 Page: 48 K02 03 20060309
SAS Engineering Process
SAS Engineering Process
OMICRON Page: 49 K02 03 20060309
The Revolution
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 Page: 50 K02 03 20060309
The Revolution
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 Page: 51 K02 03 20060309
The Benefits
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 Page: 52 K02 03 20060309
The IEC 61850 Test Configuration
The IEC 61850 Test Configuration
Scheme
Testing Tool
IED
Simulator
Test Device
IEC 61850
Standard System
Configuration
Tool
SCD
File
IEC 61850
Standard Test
Configuration
Tool
Network
System
Simulator
Other Test
Modules
MU
Simulator
MU
Simulator
MU
Simulator
IED
Simulator
IED
Simulator
ICD
File
ICD
File