IEC 61850 Seminar-SISCOpdf

Transforming the world of energy using open standards
IEC 61850 Seminar
For SCADATECH
© Copyright 2018 SISCO. All Rights Reserved

Agenda
• Abstract Communications Service Interface (ACSI) Overview
• The business case for IEC 61850
– Abstract Services
• IEC 61850 Standard structure – Mapping to MMS via IEC 61850-8-1
• IEC 61850 Object Models • Profiles for Ethernet, IP, Multicast
– Common Data Classes • Introduction to AX-S4 61850
– Installation and Basic Configuration
– Logical Nodes (LN)
• LN overview
– AX-S4 61850 Client
• SCL configuration
• LN Structure
• Discovery Configuration
– Input References and Linking LNs
• ACSI Reporting Model
– Statistical Calculations
– Unbuffered and Buffered Reporting
– Using Namespaces to define new objects
– AX-S4 61850 Client Reporting
– Simulation and Testing
• ACSI Control Model
• IEC 61850-6 Substation Configuration Language (SCL) Overview
– SBO
– SCL File Types – Enhanced Security
– SCL Engineering Process – AX-S4 61850 Client control functions
– SCL Tools – Using AX-S4 61850 Explorer
– Example SCL Tooling – Using the OPC Interface
– Applications for SCL
2 © Copyright 2018 SISCO. All Rights Reserved

Agenda
• Settings Groups • IEC 61850 Security
– Authentication
– Settings versus setpoints
– Encryption
• GOOSE – GOOSE and SV extensions
– Ethernet Multicast – Role Based Access Control
– Reliable Multicast • Configuring Security for AX-S4 61850
– Control Block and signal subscriptions • Migration Issues
– Routable GOOSE (R-GOOSE) – DNP/IEC 60870-5 to IEC 61850
• Using AX-S4 GOOSE – Ed.1 – Ed.2 – Ed2.1 of IEC 61850
• GOOSE Monitoring • IEC 61850 Testing
• Process Bus – Sampled Values – Functional Testing Issues
• Simulation mode
• Using the AX-S4 61850 Server
– Interoperability
– SCL configuration
– Conformance
– Mapping functions • CIM – IEC 61850 Harmonization
– Reporting • Detailed Overview of Logical Nodes and Common
– Applications Data Classes requested by attendees
• Conclusion

Ground Rules
Have a question? Ask a question!

The Business Case for IEC 61850

The Energy and Utilities industry is Changing Dramatically
Electric vehicles will become more
Smart appliances are
pervasive and will become both
becoming ubiquitous
load and storage
Consumers will be able to Home energy management

sell surplus energy to the systems will become more
grid or contract with a third prevalent
party
Regulatory environment allows Consumer-owned
new business opportunities for generation will be affordable
energy providers for the average household
Battery technology will become Microgrids will emerge

increasingly available where existing
infrastructure is
insufficient
ADR Automated Demand Response will There is an app for that! consumers
be used to control peak demand will want to connect to their utility
via their smart phone

The Nature of the Electric Utility Will Transform
Consumer
Power Flow
Periodic Information Flow
Continuous Information Flow
Coal/Natural Gas Solar Energy Storage
UTILITY
Hydroelectric Nuclear
UTILITY
Wind
Coal/Natural Gas Energy Storage

Solar Wind
Solar Energy Storage
Plug-in Vehicle
Wind
TRADITIONAL TRANSFORMED
• Unidirectional power flow • Multi-directional power flow
• Large centralized energy resources • Numerous Distributed Energy Resources (DER)
• Tag based Operational applications • Model based Operational applications

Expanding Number of Data Sources and Data Quality
Affects the Scope of Utility Applications
+106 +10x
Customer Social Media
Usage Points Clicks
+104 +107
Waveform Utility Potential
Samples points
The growth of data requires a new approach for OT applications:
Model based integration using CIM and IEC 61850

IEC TC 57 Standards Are Addressing These Trends
• With increasing system complexity the traditional business processes and technologies cannot
meet the need
• Systems need to be:

– Discoverable
– Self-Configuring
– Incrementally Integrated
– Flexible
– ….. MODEL – DRIVEN!
• Semantic information must be captured during the design process and used for implementation

A Standards-Based Model-Driven Architecture Maximizes Interoperability,
Flexibility and Scalability
IEC Reference Architecture
IEC 61850: A New Approach to Power System Communications
– Standardized Device, Object and Service/Behavior

Modeling
– Standardized Communications Protocols and Profiles for
Specific Use Cases:
– Station Level Monitoring and Control (TCP/IP)
– Protection and Control – Multicast GOOSE
– Process Bus – Multicast Sampled Values
– Read, Write, buffered reporting, controls, logging, files,

etc.
– Formalized engineering process to configure power
system functions and create interoperable configuration
files for IEDs using Substation Configuration Language.
– UCA International User Group (UCAIug) supports
conformance/interoperability testing and user feedback.

Traditional Protocol Standards
• Specified how you arrange bytes on the wire in order to transfer bytes of
data between a device and an application
• Good News: It worked! Device communications costs were lowered.
• Bad News: No standard for data representation or how devices should look
and behave to network applications.
– Some Interoperability but not Integration

Typical Legacy Protocol Data Model
It is in:
Object #6,
Variation #2,
Index #27
That’s intuitive?
I need the Phase A voltage for

the 345KV primary feeder
Device NO POWER SYSTEM CONTEXT FOR

DATA ACCESS
Legacy Object Mapping
• Legacy data objects must be mapped to power system for each different
device, application, and vendor.
Legacy Device
Power System Functions R400040
R400041
R400042
Phase A Voltage
R400043
Measurements Phase B Voltage
R400044
Phase C Voltage
R400045
Local/Remote Status
R400046
Controls Breaker Position
R400047
Blocked Open
R400048
Activate Phase A R400049
Protection Activate Phase B R40004A
Activate Phase C R40004B
All Cost…No Value

Behavior Modeling
• Assume Index #25 is always used to store breaker status.

• Does 1 mean open or closed?
• Can I write this object to operate the breaker?
• Where is the select?
• Is it selected?
• Even if every device used Index #25 to hold breaker status

this still isn’t enough to provide integration.

A New Approach Needed
• For protocols to provide interoperability at the system level they
need to:
– Specify the bytes/format of the data on the wire
– Specify the meaning of data
– Specify the behavior of the data

IEC61850 is Different
• IEC61850 is an object oriented substation automation standard that
defines:
– Standardized names
– Standardized meaning of data
– Standardized abstract services
– Standardized device behavior models
– Standardized protocols for:
• Control
• SCADA
• Protection
• Transducers
– Self-describing devices
– Common configuration language
– Standardized Engineering Process
IEC61850 View of Devices
Brand X Brand Y
IOC Relay Diff Relay
Measurements Measurements
PIOC MMXU1 PDIF MMXU1
ST DC DC MX ST DC DC MX
Mod Mod PhV PhV Mod Mod PhV PhV
MMXU1.MX.PhV
IEC61850 Name for Phase-to-Ground Voltage Measurements

IEC 61850 Object Mapping
• NO MANUAL MAPPING NEEDED: IEC61850 objects already
portray the power system context.
IEC61850 Device
LD
MX.A.PhsA.cVal.mag.f
MMXU1 MX.A.PhsB.cVal.mag.f
MX.A.PhsC.cVal.mag.f
ST.Loc.stVal
XCBR1 ST.Pos.stVal
ST.BlkOpn.stVal
ST.Op.phsA
PIOC1 ST.Op.phsB
ST.Op.phsC

IEC 61850-4 Engineering
Process
• A standardized process to
capture power system
engineering information as it is
created and leverage it to
dramatically reduce engineering
effort for substation automation
implementation
• The Substation Configuration

Language (SCL) of IEC 61850-6 is
the key enabling factor

Perceived Impediments
Impediment Truth
Lack of Knowledge and Complexity IEC 61850 requires additional education. Complexity
depends on your point of view.
RS-232 connections exempt from NERC No longer true with NERC CIP 5 which is risk based.
CIP
Not possible to secure IEC 61850 and Not true but there is confusion.
meet NERC CIP
IEC 61850 is a substation only protocol Not true. IEC 61850-90-2 specifies how to use 61850
between substations and control centers and other
standards are in place to use it for DER and Hydro.
No SCADA systems support IEC 61850 Solutions are coming. There are at least two SCADA
vendors participating at the next Interoperability
test.

Complexity
• A common complaint is that IEC 61850 is big, complex and requires a long
learning curve. DNP3 or Modbus are simple. Simple is better.
• The complexity of a system is not based on how the bytes sent on the wire
are organized
• Product implementation complexity does not result in application complexity
• Even though user configuration is understandable (simple) overall system

complexity is increased

Renewable Integration - Solar
• Sun Spec Alliance has developed a Modbus based
communication protocol for grid connected inverters
• At a 2010 industry event a Sun Spec representative told me:

– IEC 61850 was too complex for grid connected inverters
– Modbus was simple and easy to implement
• Let’s look at how “simple” grid connected inverters are using

Modbus
Sun Spec Protocol Implementation Conformance Statement
© Copyright 2018 SISCO. All Rights Reserved There are 75 tabs on this spreadsheet
Renewable Integration - Solar
• In California:
– In 2014 there were 2,164 different models of inverters from 151 different
manufacturers that are approved for grid connection of solar panels.
• Sun Spec Alliance:
– 37 manufacturers with 127 models of Sun Spec certified Modbus interfaces.
• According to public sources:
– There are > 626,000 solar homes in California
• Will it be “simple” to integrate 600K homes with utility scale applications to build an
intelligent grid leveraging solar resources using Modbus?
• Good news: New standards like IEC 61850-7-420 are being considered

Why Does This Happen?
• Assuming product implementation complexity results in
application complexity
• Assuming that technology constraints today will be valid over the

life of the system
• Assumption that user configuration is reasonable because it is

understandable
• User effort costs less than development

Where should the complexity be handled?
626,000 mappings
developed by
USERS
Modbus Applications
Power System Functions R400040
R400041
Phase A Voltage R400042
Measurements Phase B Voltage R400043
Phase C Voltage R400044
R400045
Local/Remote Status
R400046
Controls Breaker Position
R400047
Blocked Open
R400048
Activate Phase A R400049
Protection Activate Phase B R40004A
Activate Phase C R40004B
Devices
151 mappings
developed by VENDORS

The Most Important Aspect of IEC 61850 is:
Semantics
• Semantics to implement an engineering process based on
standardized configuration language (Substation Config.
Language – SCL)
• Semantics to eliminate mappings and automate
configuration
• Semantics to manage the complexity of very large systems
that are changing constantly
• How data is sent/received on the wire is not what makes a
system complex
IEC 61850 Engineering Process
As the substation design

proceeds from planning
through operation
semantic information is
captured and used for
configuration of IEDs and
integration with other
systems (SCADA, EMS,
DMS, etc.)
The Impact of IEC 61850
Consumer
Power Flow
Periodic Information Flow
Continuous Information Flow
Coal/Natural Gas Solar Energy Storage
UTILITY
UTILITY
Wind
Coal/Natural Gas Energy Storage

Solar Wind
Solar Energy Storage
Plug-in Vehicle
Wind
TRADITIONAL TRANSFORMED
• Unidirectional power flow • Multi-directional power flow
• Large centralized energy resources • Numerous Distributed Energy Resources (DER)
• Tag based Operational applications • Model based Operational applications

Evolution of Interoperability
• By 2008 IEC 61850 became the dominant protocol used for
substation automation in Europe without a user mandate
• Implementation of the IEC 61850 engineering process across
multiple vendors was challenging because of the tools
• A Spanish group of utilities and then ENTSO-E began to address
this with multi-vendor mandates ~2011
– “We know IEC 61850 devices can communicate with each
other no problem. We need the engineering process to
interoperate the same way”
• In 2011 the UCA International Users Group (UCAIug) began
establishing rigorous and formal interoperability testing and this
continues based on user requirement (2013, 2015, 2017, 2019…)
Global Adoption of IEC 61850
32
A Test Question
• Substations suppliers bid and won projects in Europe using IEC 61850 without a
customer requirement because of which reason?
a) IEC 61850 Costs More to Use
b) IEC 61850 Costs Less to Use

Newton-Evans Reflects North American Reality
45%
40%
35%
30%
25%
20%
15% Current Usage
10% Future Usage
5%
0%

Why So Little Penetration of IEC 61850 in NA?
• NA Utilities are vertically integrated
– Power system engineering
– Substation design
– Substation engineering
– Substation testing
– Substation commissioning
• European (and other) utilities bid substations turnkey

– Utility specs requirements for voltage levels in/out, loads, space, etc.
– Lowest cost credible supplier designs, builds, tests and commissions substations.

35
Vertical Integration and Regulation
• NA utilities are already highly automated and successful using legacy approaches.
• NA Utilities are focused on the costs to transition, not the benefit of using
– Training
– New learning
– Existing approaches
• Many PUCs do not reward utilities to lower these costs. Regulations cause perverse incentives.
• This instructor is sure that that benefits are overwhelming and IEC 61850 will prevail in NA as it is
everywhere else.

Current Status of IEC 61850 in North America
• There are substantial IEC 61850 applications in NA although
not well publicized (AEP, SCE, Entergy, CFE, several Coops)
• More NA utilities are engaging with IEC 61850 all the time
• New approaches to apply IEC 61850 engineering to existing

legacy technologies like DNP3 (e.g. DTE)

Using IEC 61850 with DNP3
SISCO
IEC 61850 Software
Utility Model Files
Requirements
Substation
Device
Template
ICD IEC 61850
Design Tool
ICD File
Spreadsheet Creator (Device Template) (SCT)
IEEE 1815.1
(or IEC 61850-80-1 for -104) IEC 61850 SCD File
XML Mapping File SCL to CIM
Generic Tag PI DNP3 CIM XML For Topology
Configuration Interface Information
Generation Configurator EMS/DMS CIM Adapter
System for PI
Other
DNP3/101/104
Interfaces
OSIsoft PI System

The Justification Dilemma
COSTS
BENEFITS
Engineer’s View of Justification

The Justification Dilemma
BENEFITS
COSTS
Accountant’s View of Justification

The Tragedy of Integration and Automation
There are no benefits

without some cost

About Benefits & Justification
• Identify all the benefits (obvious).
• ALSO Identify ALL the costs:

– Equipment
– Installation
– Engineering
– Commissioning
– Utilization Costs
– Impact on External Systems
– Costs to Change/Migrate in Future
– Intangibles (new capability)
• Requires a complete view of cost and the use case driving the need.
• Requires a longer time frame.

Model-Driven Cost Justification
Traditional
Cost Approaches
Model
Driven
Approaches
Payback
Time
Purchase

IEC 61850 Standards
Structure of the International Electrotechnical Commission

(IEC) and the IEC 61850 Standards

IEC TC 57 (Power Systems Management and Associated Information Exchange)
Working Groups
• WG 3 – Telecontrol Protocols
– IEC 60870-5-7 – Security for IEC 60870-5 protocols.
• WG 9 – Distribution automation using distribution line carrier systems – IEC 61334
• WG 10 - Power system IED communication and associated data models
– IEC 61850 – Communications for power system automation
• WG 13 - Energy management system application program interface (EMS - API)
– IEC 61970 – Common Information Model (CIM) and Generic Interface Definition (GID)
• WG 14 - System interfaces for distribution management (SIDM)
– IEC 61968 – CIM for distribution and model driven messaging
• WG 15 - Data and communication security
– IEC 62351 – Communications Security
• WG 16 - Deregulated energy market communications
– IEC 62325 – CIM for energy markets
• WG 17 - Communications for Distribution Automation and Distributed Energy Resources (DER)
– IEC 61850-7-420 – IEC 61850 for DER applications
– IEC 61850-8-2 – IEC 61850 using XML encoding over XMPP
• WG 18 - Hydroelectric power plants - Communication for monitoring and control
– IEC 61850-7-410 – IEC 61850 for Hydropower applications
• WG 19 - Interoperability within TC 57 in the long term
– IEC 62445 – Use of IEC 61850 between control centers and substations
– IEC 61850-CIM harmonization, ICCP-TASE.2 update, naming/design rules for CIM, quality codes.
• WG 20 – Planning of power line carrier systems – IEC 60495, 60663
• WG 21 - Interfaces and protocol profiles relevant to systems connected to the electrical grid
– IEC 62746 – Interfaces and protocol for Smart Grid to Consumer systems
• JWG 16 – Mapping between CIM and DLMS/COSEM – metering protocols (TC 13)
• JWG 25 – Communications for windpower systems (TC 88) IEC 61400-25
• TC 38 WG 37 Instrument Transformers interfaces IEC 61869-9
• TC 65 SC65C – Precision Time Protocol – IEC 61588 (IEEE 1588)
TC 57 Architecture

Strategic Vision for Integration and Interoperability
• Abstract Modeling
• Object and Information Models
• Abstract Service and Interface Models
• Self Description and Discovery
• Technology Independent Design
• Security
• Applying mainstream standards to TC57 standards
• Power system specific applications and recommendations

IEC 61850
Communications and networks for

power systems automation

IEC 61850 Standards
Standard Description Standard Description
IEC TR 61850-1:2013 Introduction and overview
IEC TR 61850-90-1:2010 Use of IEC 61850 for the communication between substations
IEC TS 61850-2:2003 Glossary
Using IEC 61850 for communication between substations and control
IEC 61850-3:2013 General requirements IEC TR 61850-90-2:2016 centres
IEC 61850-4:2011 System and project management IEC TR 61850-90-3:2016 Using IEC 61850 for condition monitoring diagnosis and analysis
IEC 61850-5:2013 Communication requirements for functions and device models IEC TR 61850-90-4:2013 Network engineering guidelines
IEC 61850-6:2009+AMD1:2018 Configuration description language for communication in power utility automation systems related to Use of IEC 61850 to transmit synchrophasor information according to
CSV IEDs IEC TR 61850-90-5:2012 IEEE C37.118
Object models for power converters in distributed energy resources
IEC 61850-6:2009 Configuration description language for communication in electrical substations related to IEDs
IEC TR 61850-90-7:2013 (DER) systems
Configuration description language for communication in power utility automation systems related to
IEC 61850-6:2009/AMD1:2018 IEC TR 61850-90-8:2016 Object models for E-mobility
IEDs
IEC TR 61850-90-10:2017 Models for scheduling
IEC 61850-7-1:2011 Basic communication structure - Principles and models
IEC TR 61850-90-12:2015 Wide area network engineering guidelines
IEC 61850-7-2:2010 Basic information and communication structure - Abstract communication service interface (ACSI) IEC TR 61850-90-17:2017 Using IEC 61850 to transmit power quality data
Communication network and system security - Introduction to security
IEC 61850-7-3:2010 Basic communication structure - Common data classes
IEC TS 62351-1:2007 issues
IEC 61850-7-4:2010 Basic communication structure - Compatible logical node classes and data object classes
IEC TS 62351-2:2008 Glossary of terms
IEC TS 61850-7-7:2018 Machine-processable format of IEC 61850-related data models for tools
IEC 62351-3:2014+AMD1:2018 CSV Communication network and system security - Profiles including TCP/IP
IEC 61850-7- Basic communication structure - Hydroelectric power plants - Communication for monitoring and
IEC 62351-3:2014 Communication network and system security - Profiles including TCP/IP
410:2012+AMD1:2015 CSV control
IEC 62351-3:2014/AMD1:2018 Communication network and system security - Profiles including TCP/IP
Basic communication structure - Hydroelectric power plants - Communication for monitoring and
IEC 61850-7-410:2012 control IEC TS 62351-4:2007 Profiles including MMS
IEC 61850-7- Basic communication structure - Hydroelectric power plants - Communication for monitoring and IEC TS 62351-6:2007 Security for IEC 61850
410:2012/AMD1:2015 control IEC 62351-7:2017 Network and System Management (NSM) data object models
IEC 61850-7-420:2009 Basic communication structure - Distributed energy resources logical nodes IEC TS 62351-8:2011 Role-based access control
Basic information and communication structure - Use of logical nodes for modeling application IEC 62351-9:2017 Cyber security key management for power system equipment
IEC TR 61850-7-500:2017 functions and related concepts and guidelines for substations IEC TR 62351-10:2012 Security architecture guidelines
IEC TR 61850-7-510:2012 Basic communication structure - Hydroelectric power plants - Modelling concepts and guidelines IEC 62351-11:2016 Security for XML documents
Resilience and security recommendations for power systems with
Specific communication service mapping (SCSM) - Mappings to MMS (ISO 9506-1 and ISO 9506-2) IEC TR 62351-12:2016 distributed energy resources (DER) cyber-physical systems
IEC 61850-8-1:2011 and to ISO/IEC 8802-3 Guidelines on security topics to be covered in standards and
Specific communication service mapping (SCSM) - Mapping to Extensible Messaging Presence IEC TR 62351-13:2016 specifications
IEC 61850-8-2:2018 PRV Protocol (XMPP) IEC TR 62351-90-1:2018 Guidelines for handling role-based access control in power systems
IEC 61850-9-2:2011 Specific communication service mapping (SCSM) - Sampled values over ISO/IEC 8802-3 IEC TR 62357-1:2016 Reference architecture
IEC/IEEE 61850-9-3:2016 Precision time protocol profile for power utility automation Guidelines for migration from Internet Protocol version 4 (IPv4) to
IEC TR 62357-200:2015 Internet Protocol version 6 (IPv6)
IEC 61850-10:2012 Conformance testing
Guideline to exchanging information from a CDC-based data model using IEC 60870-5-101 or IEC
IEC TS 62361-102:2018 CIM - IEC 61850 harmonization
IEC TS 61850-80-1:2016 60870-5-104 IEC TR 62361-103:2018 Standard profiling
IEC TR 61850-80-3:2015 Mapping to web protocols - Requirements and technical choices IEC 61869-9:2016 Digital interface for instrument transformers
IEC TS 61850-80-4:2016 Translation from the COSEM object model (IEC 62056) to the IEC 61850 data model

Standards Numbering
• IEC 61850-7-4:2010
• International Standard (IS) published in 2010
• Ed.2 of the Logical Node (LN) standard for IEC 61850
• IEC 61850-6:2009/AMD1:2018
• Amendment 1 of the IS version (2009) that was published in 2018
• Ed2.1 of the Substation Configuration Language (SCL) standard
• IEC TS 61850-80-1:2016
• Technical Specification (TS) published in 2016 (1st version of potential future IS)
• Mapping of IEC 61850 object models to IEC 60870-104/101 for protocol gateway
• IEC TR 61850-90-8:2016
• Technical Report (TR) published in 2016 (a future addition to the IEC 61850 base standard)
• Object models for e-mobility (electric vehicles)

IEC TR 61850-90-XX: Future IEC 61850 Standards
• Currently Published:
• IEC TR 61850-90-1:2010 Use of IEC 61850 for the communication between substations
• IEC TR 61850-90-2:2016 Using IEC 61850 for communication between substations and control centres
• IEC TR 61850-90-3:2016 Using IEC 61850 for condition monitoring diagnosis and analysis
• IEC TR 61850-90-4:2013 Network engineering guidelines
• IEC TR 61850-90-5:2012 Use of IEC 61850 to transmit synchrophasor information according to IEEE C37.118
• IEC TR 61850-90-7:2013 Object models for power converters in distributed energy resources (DER) systems
• IEC TR 61850-90-8:2016 Object model for E-mobility
• IEC TR 61850-90-10:2017 Models for scheduling
• IEC TR 61850-90-12:2015 Wide area network engineering guidelines
• IEC TR 61850-90-17:2017 Using IEC 61850 to transmit power quality data
• These documents include:

• Detailed use cases for all the data models illustrating how it is used in real systems
• Complete Logical Node and attribute definitions to support those use cases
• These documents will be incorporated into future IS versions, or Amendments, of the IEC 61850
standards.
• This could impact multiple documents but mostly IEC 61850-7-4 (Logical Nodes)

Current Work on IEC 61850 (Partial List)
Standard Description WG Standard Description WG
61850-10-3 Functional testing of IEC 61850 based systems 10 61850-7-6 Guideline for Basic Application Profiles 10
Guideline for technical committees and working groups for 61850-7-7 Specification of schema for namespace definition files 10
61850-1-2 10
extending IEC 61850
61850-80-5 Mapping between Modbus and IEC 61850 10
61850-2 Glossary 10
Mappings to MMS (ISO/IEC 9506-1 and ISO/IEC 9506-2) and to
61850-8-1 10
61850-4 System and project management 10 ISO/IEC 8802-3
61850-5 Communication requirements for functions and device models 10 61850-8-2 Mapping to Webservices 17
Configuration description language for communication in Methodologies for modelling of logics for IEC 61850 based
61850-6 10 61850-90-11 10
electrical substations related to IEDs applications
Guideline for function modeling in SCL for substation 61850-90-12 Wide area network engineering guidelines 10
61850-6-100 10
automation
61850-90-13 Deterministic network topologies 10
Configuration description language extensions for human
61850-6-2 10
machine interfaces 61850-90-14 Using IEC 61850 for FACTS and power conversion data modelling 10
61850-7-1 Basic communication structure – Principles and models 10 61850-90-15 IEC 61850 based DER Grid Integration 17
61850-7-2 Abstract communication service interface (ACSI) 10 61850-90-16 Requirements for System Management 17
61850-7-3 Common data classes 10 61850-90-18 Modeling Alarm handling for IEC 61850 10
61850-7-4 Compatible logical node classes and data classes 10 61850-90-19 Applying role based access control to IEC 61850 10
Hydroelectric power plants - Communication for monitoring 61850-90-20 Guideline for redundant IEDs with IEC 61850 10
61850-7-410 18
and control
Communications systems for distributed energy resources 61850-90-21 Use of IEC 61850 for traveling wave fault location system 10
61850-7-420 17
(DER) - Logical nodes 61850-90-4 Network engineering guidelines for substations 10
61850-7-5 IEC 61850 modelling concepts 10
61850-90-6 Using IEC 61850 for Distribution Automation 17
61850-7-510 Hydroelectric plants – Modelling concepts and guidelines 18
61850-90-8 Object models for electrical vehicles 17
61850-7-520 DER - Modelling concepts and guidelines 17
61850-90-9 Object models for electrical energy storage 17
61850-90-6 Distribution Automation 17
52 61850-9-2 Sampled values over ISO/IEC 8802-3 10
The Primary Standard Parts
• IEC 61850-3 General Requirements (Environmental Specifications)
• IEC 61850-5 Communication requirements for functions and device models (Defines
power system functions used for Logical Nodes)
• IEC 61850-6 Substation Configuration Language (SCL)
• IEC 61850-7-X Communication and Information Models
• 7-1 Principles and Models (includes naming rules and how to extend)
• 7-2 Abstract Communications Service Interface (ACSI)
• 7-3 Common Data Classes (CDC)
• 7-4 Compatible Logical Node (LN) Classes and Data Classes
• IEC 61850-8-1 Specific Communication Service Mapping (SCSM) to MMS (ISO 9506)
TCP/IP – Ethernet
• IEC 61850-9-2 SCSM for Sampled Values over Ethernet
– IEC 61869-9 Using IEC 61850-9-2 for instrument transformers (TC 38)

Other IEC 61850 Standards of Common Interest
• IEC 61850-7-410 Modeling for hydro power plants
• IEC 61850-7-420 Modeling for Distributed Energy Resources (DER)
• IEC TR 61850-90-1 Using IEC 61850 for control center to station
• IEC TR 61850-90-5 Using GOOSE and SV over Wide Area Networks
• IEC 62351 Security standards
• IEC 61400-25-4 IEC 61850 models for wind turbines

Guide For the Reader

IEC 61850 Standard Status
• Edition 1 (Ed.1) was released in 2003
• Widespread adaption throughout Europe, Asia and Latin America
• Identified numerous interoperability issues
• ENTSO-E project to gain interoperability of tools
• Edition 2 (Ed.2) was released in 2009-2010
• Many more Logical Node definitions
• More precise state machine definitions for reporting, controls, etc.
• Numerous corrections and clarifications to address interoperability
• Some changes were not backward compatible although most client applications can talk both Ed.1 and Ed.2 without
difficulty
• Amendment 1 to Edition 2 (Ed2.1) is being released 2017-2019
• Incorporating 90-X technical reports into base standards (more Logical Nodes)
• Further improvements and clarifications that are BACKWARD COMPATIBLE ONLY
• Future:
– Edition 3 will probably start 2020
– Additional Basic Application Profiles (BAP)
• A BAP defines how to use IEC 61850 for a given application
• Makes many optional parameters mandatory

IEC 61850 Object Models

The Virtual Device Model
Common Data Classes and Base Types
Logical Nodes

Use of Abstract Models
• IEC 61850 standards are mostly abstract models that do not define how
devices work
• Exceptions are the SCSM (e.g. IEC 61850-8-1 mapping to MMS TCP/IP Ethernet) which
specify a concrete mapping to a specific set of protocols
• The abstract models specify the behavior and data model of an abstract
device
• Network visible data and functions
• Developers of devices need to map this abstract model to how their actual
products and devices

IEC 61850 Server Abstraction
IEC 61850 Objects

Mapping
IEC61850
To Real
Server
Device
(Developer)
Client
Developers are
free to
implement as
Only externally
desired
visible behavior is
standardized

IEC61850 Server Object
• Represents the external network visible behavior of the physical
device
• Supports one or more Service Access Points (SCSM e.g. 8-1 or 9-2)
• Contains one or more logical devices which, in turn, contains all

other objects and services like Logical Nodes (LNs)

IEC61850 Class Model in UML
Name SERVER
Contains LDs and files
ObjectName
ObjectReference
1
“Containment Hierarchy”
Inheritance 1..*
or
LOGICAL-DEVICE
(LD) “Aggregation”
1
3..*
LOGICAL-NODE
(LN)
Contains all other data objects
1
1..*
DATA
1
1..*
DataAttribute UML – Unified Modeling Language

Logical Device
• Container for Logical Nodes and all other data.
• Used as a proxy to represent data from other devices such as

gateways and data concentrators.
• 8-1 maps the abstract “logical device” to MMS Domains.

Logical Device Structure IEC61850 Clients
IEC61850 Server Physical Device

Client
Functions
Logical Logical
Device 1 to N Logical Devices
Device
Logical
Node
... Logical
Node
Logical
Node
... Logical
Node
… … … …
Data Data Data Data Data Data Data Data
Communications Driver
Process Bus
Field Signals Legacy Device

Logical Node
A named grouping of data and associated services that is

logically related to some power system function.

Examples of Logical Nodes
Current
Transformer
Voltage
Breaker Transformer
Breaker
Switch
Breaker Controller

Logical Nodes Contain Data
Name SERVER
ObjectName
ObjectReference
1
1..*
LOGICAL-DEVICE
(LD)
1
3..*
LOGICAL-NODE
(LN)
1
1..*
DATA
We are going to start from the
1
bottom up and build up the logical
1..*
node definitions starting with Base
DataAttribute Types and Common Data Classes
(CDC) and their attributes.

Common Data Classes (CDC)
• Defines structure for common types that are used to describe data
objects.
• CDC are complex objects built on predefined simple base types

organized into Functional Constraints (FC)
• Examples:
• Single point status (SPS) – on/off
• Double point status (DPS) – on/off/transient

IEC61850 Base Types from IEC 61850-7-2
Name Value Range
BOOLEAN True/False
INT8 -128 to 127
INT16 -32,768 to 32,767
INT24 -8,388,608 to 8,388,607
INT32 -2,147,483,648 to 2,147,483,647
INT128 INT64 -2**127 to (2**127)-1 -2**63 to (2**63)-1
INT8U 0 to 256 – unsigned integer
INT16U 0 to 65,535 – unsigned integer
INT24U 0 to 16,777,215 – unsigned integer (fractions of second)
INT32U 0 to 2,294,967,295 – unsigned integer
INT64U For Accumulators (V2)
FLOAT32 IEEE 754 single precision floating point
FLOAT64 IEEE 754 double precision floating point
ENUMERATED Ordered set of values, defined where used
CODED ENUM Ordered set of values, defined where used
OCTET STRING Sequence of bytes (octets) max length defined where used
VISIBLE STRING Visible string (ASCII)
UNICODE STRING Unicode string (for non-latin languages)
Packed List Combination of several elements packed into a single element

IEC 61850 TimeStamp
• Universal Time Coordinated (UTC)
• All time stamps are specified in Greenwich Mean Time (GMT)
• Conversion to local time is a local matter for the clients
• Time stamps provide up to 60ns accuracy potential
• Includes a time stamp quality byte

IEC 61850 TimeStamp Format (Packed List)
• 4 Bytes = Second Of Century (SOC) Starting January 1, 1970
• Based on the Network Time Protocol (NTP) standard
• There are 31,536,000 seconds/year (non-leap)
• 4 bytes = 4, 294,967,296 counts do not wrap for 136 years or 2106
• 3 Bytes = Fraction of Second

• 16,777,216 counts
• about 60nsec potential resolution
• 1 Byte = Time Quality (Packed List)

• 1 bit : Leap Seconds known
• 1 bit : ClockFailure
• 1 bit : ClockNotSynchronized
• 5 bits: TimeAccuracy - Number of significant bits in Fraction of Second (N)

IEC 61850 Time Accuracy
Class Accuracy Time Accuracy (N bits)

T0  10 ms N=7
T1  1 ms N=10
T2  0.1 ms N=14
T3  25 sec N=16
T4  4 sec N=18
T5  1 sec N=20
`**unspecified** N=31

IEC 61850 Quality (packed list)

IEC 61850 Quality
MSB 13 bit Bit-String, typically stored in a 16-bit integer LSB
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
OperatorBlocked
Test
00 Good Source = 0 Process
01 Invalid = 1 Substituted
10 Reserved Inaccurate
11 Questionable Inconsistent
OldData
Failure
Oscillatory
BadReference
OutofRange
Overflow

Common Data Classes (CDC)
• CDCs are complex structured objects that represent the Data

Objects (DO) defined in a Logical Node (LN)
• Measurement, Status, Controls, Settings, etc.
• The Data Attributes (DA) of CDCs are defined by base types
• CDCs are fixed. New LNs may not change existing CDCs.

Common Data Classes - Status
Name Description
SPS Single Point Status
DPS Double Point Status
INS Integer Status
ENS Enumerated Status (Ed.2)
ACT Protection Activation
ACD Directional Protection Activation Info.
SEC Security Violation Counting
BCR Binary Counter Reading
HST Histogram (Ed.2)
VSS Visible String Status (Ed.2)
ORS Object Reference Status (Ed2.1)
TCS Time Value Status (Ed2.1)

Common Data Classes - Measurands
Name Description
MV Measured Value
CMV Complex Measured Value
SAV Sampled Value
WYE Phase to ground measured values for 3-phase system
DEL Phase to phase measured values for 3-phase system
SEQ Sequence
HMV Harmonic value
HWYE Harmonic value for WYE
HDEL Harmonic value for DEL

Common Data Classes - Controls
Name Description
SPC Controllable Single Point
DPC Controllable Double Point
INC Controllable Integer Status
ENC Controllable Enumerated Status (Ed.2)
BSC Binary Controlled Step Position Info.
ISC Integer Controlled Step Position Info.
APC Controllable Analogue Process Value
BAC Binary Controlled Analog Process Value (Ed.2)

Common Data Classes – Settings and Descriptions
Name Description
SPG Single Point Setting
ING Integer Status Setting
ENG Enumerated Status Setting
ORG Object Reference Setting
TSG Time Setting Group
CUG Currency Setting Group
VSG Visible String Setting
ASG Analogue Setting
CURVE Setting Curve
CSG Curve Shape Setting
DPL Device Name Plate
LPL Logical Node Name Plate
CSD Curve Shape Description

Common Data Classes – Control Block Service Tracking
Name Description
CTS Common Service Tracking (Ed.2)
BTS Buffered Report Tracking Service (Ed.2)
UTS Unbuffered Report Tracking Service (Ed.2)
LTS Log Control Block Tracking Service (Ed.2)
GTS GOOSE Control Block Tracking Service (Ed.2)
MTS Multicast Sampled Value (9-2) Control Block Tracking

Service (Ed.2)
NTS Unicast Sample Value (9-1) Control Block Tracking Service

(Ed.2)
SGCB Setting Group Control Block Tracking Service (Ed.2)

Functional Constraints (FC)
• There are many data attributes in an object like a breaker that have
related usage
– Control, configuration, measurement, reporting, etc.
• Functional Constraints (FC) is a property of a Data Attribute (DA)

that characterizes the use of that attribute.
• Useful to functionally organize data attributes to provide structure

and context.

FC Name Description
Functional Constraints ST Status Information
MX Measurands (analog values)
CO Control
SP Set point (settings without using setting groups)
SV Substituted Values
CF Configuration
DC Description
SG Setting Group Active
SE Setting Group Editable
SR Service Response
OR Operate Received
BL Blocking
EX Extended Definition (naming – read only)
BR Buffered Report
RP Unbuffered Report
Replaced with Control LG Logging
Block Service Tracking GO GOOSE Control
CDCs in Ed. 2 of 7-2 GS GSSE Control
But Ed.2 of 8-1 reinserted MS Multicast Sampled Value (9-2)
for mapping to MMS US Unicast Sampled Value (9-1)
XX Used as wild card in ACSI

Single Point Status (SPS)
SPS class
Data Type FC TrgOp Value/Value range M/O/C
Attribute
name
DataName Inherited from GenDataObject Class or from GenSubDataObject Class (see
IEC 61850-7-2)
DataAttribute
status
stVal BOOLEAN ST dchg TRUE | FALSE M
q Quality ST qchg M
t TimeStamp ST M
substitution and blocked
subEna BOOLEAN SV PICS_SUBST
subVal BOOLEAN SV TRUE | FALSE PICS_SUBST
subQ Quality SV PICS_SUBST
subID VISIBLE STRING64 SV PICS_SUBST
Edition 2 blkEna BOOLEAN BL O
configuration, description and extension
d VISIBLE STRING255 DC Text O
dU UNICODE STRING255 DC O
cdcNs VISIBLE STRING255 EX AC_DLNDA_M
cdcName VISIBLE STRING255 EX AC_DLNDA_M
dataNs VISIBLE STRING255 EX AC_DLN_M
Services
As defined in Table 13
Attribute Mandatory/
Name Type Trigger Range of Optional
Functional
Constraint Options Values

Trigger Option (TrgOp)
Specifies the conditions under which reporting on the data attribute can be triggered.
TriggerConditions type
Attribute name Attribute type Value / Value Range M/O/C
PACKED LIST M
data-change BOOLEAN See Clause
See Clause Error! M
Reference source not
found.
quality-change BOOLEAN See Clause
See Clause Error! M
found.
data-update BOOLEAN See Clause
See Clause Error! M
found.
integrity BOOLEAN See
See Clause
Clause Error! M
found.
general-interrogation BOOLEAN See Clause
See Clause Error! M
found.

TrgOp – BitString Value per IEC 61850-8-1
MSB LSB
0 1 2 3 4 5 6 7
Unused
Bit 5 general-interrogation
Bit 4 integrity
Bit 3 data-update
Bit 2 quality-change
Bit 1 data-change
Bit 0 reserved

Mandatory/Optional Parameters
• Specifies whether a data attribute (DA) is mandatory (M) or

optional (O) and under what conditions the are mandatory or
optional:
– PICS_XXXX: Specifies an ACSI service model that if
supported then the DA is mandatory
– PICS_SUBST means if Substitution is supported ths DA is
mandatory
PICS = Protocol Implementation Conformance Statement

SPS class
Substitution Data
Attribute
Type FC TrgOp Value/Value range M/O/C
name
IEC 61850-7-2)
DataAttribute
status
stVal BOOLEAN ST dchg TRUE | FALSE M
q Quality ST qchg M
t TimeStamp ST M
subVal BOOLEAN SV TRUE | FALSE PICS_SUBST
blkEna BOOLEAN BL O
Services
• Substitution enables value and quality to be overridden by a
local process or by an operator identified by subID.
• Status or measured values only. Not applicable to sampled
values.
• Substition is reflected in the quality (q) of the original value.

Logical Node Name Plate - LPL
LPL class
attribute
name
IEC 61850-7-2)
DataAttribute
vendor VISIBLE STRING255 DC M
swRev VISIBLE STRING255 DC M
d VISIBLE STRING255 DC O
configRev VISIBLE STRING255 DC AC_LN0_M
paramRev INT32 ST dchg O
Edition 2
valRev INT32 ST dchg O
ldNs VISIBLE STRING255 EX shall be included in LLN0 only; AC_LN0_EX
for example "IEC 61850-7-4:2003"
lnNs VISIBLE STRING255 EX AC_DLD_M
CDC namespaces
Ed2.1 cdcNs VISIBLE STRING255 EX AC_DLNDA_M cannot be changed
cdcName VISIBLE STRING255 EX AC_DLNDA_M outside of IEC 61850-
Services
7-3
AC_LN0_M = Mandatory for LLN0
AC_LN0_M = Used exclusively for LLN0 only
Configuration Revision Parameters
MSB
• configRev – Changed whenever at least one semantic aspect of the data has changed within the Logical Device
(LD) within which this LLN0 is contained. Left to the “user” (vendor) for other LNs.
– New LNs
– New attributes
– New data sets, etc.
• paramRev – Changed when the value of any editable setting (SE) or setpoint (SP) parameter is changed.
– If changed via communications or local HMI the value is increased by 1.
– If changed via SCL import the value is increased by 10,000.
• valRev – changed when the value of any configuration (CF) parameter is changed.
– If changed via communications or local HMI the value is increased by 1.
– If changed via SCL import the value is increased by 10,000.

Device Name Plate - DPL
DPL class
attribute
name
IEC 61850-7-2)
DataAttribute
hwRev VISIBLE STRING255 DC O
swRev VISIBLE STRING255 DC O
serNum VISIBLE STRING255 DC O
model VISIBLE STRING255 DC O
location VISIBLE STRING255 DC O
name VISIBLE STRING64 DC O
owner VISIBLE STRING255 DC O
ePSName VISIBLE STRING255 DC O
primeOper VISIBLE STRING255 DC O
secondOper VISIBLE STRING255 DC O
latitude FLOAT32 DC O
longitude FLOAT32 DC O
Edition 2
altitude FLOAT32 DC O
mrID VISIBLE STRING255 DC O
cdcNs VISIBLE STRING255 EX AC_DLNDA_M Ed2.1
Services
As defined in Table 45 Lat/Long in WGS84 coordinates
Double Point Status (DPS)
DPS class
Attribute
name
IEC 61850-7-2)
DataAttribute
status
stVal CODED ENUM ST dchg intermediate-state | off | on | bad-state M
q Quality ST qchg M
t TimeStamp ST M
subVal CODED ENUM SV intermediate-state | off | on | bad-state PICS_SUBST
Services
2-bit pair in DPS versus boolean in SPS
Integer Status - INS
INS class
Attribute
name
IEC 61850-7-2)
DataAttribute
status
stVal INT32 ST dchg, M
dupd
q Quality ST qchg M
t TimeStamp ST M
subVal INT32 SV PICS_SUBST
blkEna BOOLEAN BL O
units Unit CF O
Services
Enumerated Status – ENS (Edition 2)
ENS class
Attribute
name
IEC 61850-7-2)
DataAttribute
status
stVal ENUMERATED ST dchg, M
dupd
q Quality ST qchg M
t TimeStamp ST M
subVal ENUMERATED SV PICS_SUBST
blkEna BOOLEAN BL O
Services
Visible String Status – VSS (Edition 2)
VSS class
Attribute
name
IEC 61850-7-2)
DataAttribute
status
stVal VISIBLE STRING 255 ST dchg Text M
q Quality ST qchg M
t TimeStamp ST M
Services

Controllable Double Point – DPC (Edition 1)
Mandatory if
control is
supported
Optional if
control is
supported
Ed2.1

Control Model (ctlModel)
• 0: Status only. No control allowed.
• 1: Direct control with normal security
• 2: SBO control with normal security
• 3: Direct control with enhanced security
• 4: SBO control with enhanced security

SBO Class (sboClass)
• operate-once (0) Deselected after operate
• operate-many (1) Remains selected after operate

PulseConfig
1 2 numPls (# of pulses)
offDur – Off Duration in mSec

onDur – On Duration in mSec
persistent = device has some local means of disabling the output

Controllable Double Point DPC (Edition 2)
DPC class
attribute
name
IEC 61850-7-2)
DataAttribute
status and control mirror
origin Originator ST AC_CO_O
ctlNum INT8U ST 0..255 AC_CO_O
stVal CODED ENUM ST dchg intermediate-state | off | on | bad- M
state
q Quality ST qchg M
t TimeStamp ST M
stSeld BOOLEAN ST dchg O
opRcvd BOOLEAN OR dchg O
Edition 2 opOk BOOLEAN OR dchg O
tOpOk TimeStamp OR O
subVal CODED ENUM SV intermediate-state | off | on | bad- PICS_SUBST
state
pulseConfig PulseConfig CF dchg AC_CO_O
ctlModel CtlModels CF dchg M
sboTimeout INT32U CF dchg AC_CO_O
sboClass SboClasses CF dchg AC_CO_O
Edition 2 operTimeout INT32U CF dchg AC_CO_O
Services
98 As defined in Table 31
parameters for control services
Service parameter name Service parameter type Value/Value range
ctlVal BOOLEAN off (FALSE) | on (TRUE)
Control Service Tracking Added
• opRcvd – an Operate command has been received
• opOk – an Operate command has been accepted
• tOpOk – the time at which the output was activated
• operTimeout – Operate Timeout (CF) in milliseconds

name
IEC 61850-7-2)
Controllable DataAttribute
origin Originator ST
AC_CO_O
Double Point ctlNum

stVal
q
INT8U
CODED ENUM
Quality
ST
ST
ST
dchg
qchg
0..255
intermediate-state | off | on | bad-
state
AC_CO_O
M
DPC t
stSeld
opRcvd
opOk
TimeStamp
BOOLEAN
BOOLEAN
BOOLEAN
ST
ST
OR
OR
dchg
dchg
dchg
M
O
O
O
ctlVal (Edition 2) tOpOk
subEna
TimeStamp
BOOLEAN
OR
SV
O
PICS_SUBST
subVal CODED ENUM SV intermediate-state | off | on | bad- PICS_SUBST
state
blkEna BOOLEAN BL O
pulseConfig PulseConfig CF dchg AC_CO_O
operTimeout INT32U CF dchg AC_CO_O
Services
ctlVal BOOLEAN off (FALSE) | on (TRUE)

Controllable Integer Status - INC Edition 2 Edition 1
INC class
attribute
name
IEC 61850-7-2)
DataAttribute
stVal INT32 ST dchg M
q Quality ST qchg M
t TimeStamp ST M
opOk BOOLEAN OR dchg O
blkEna BOOLEAN BL O
minVal INT32 CF dchg O
maxVal INT32 CF dchg O
stepSize INT32U CF dchg 1 … (maxVal – minVal) O
units Unit CF dchg O
Ed2.1 cdcNs VISIBLE STRING255 EX AC_DLNDA_M
Services
101 © Copyright 2018 SISCO. All Rights Reserved parameters for control services
ctlVal INT32
INC class
attribute
name
Controllable Integer Status – INC – ctlVal DataName Inherited from GenDataObject Class or from GenSubDataObject Class (see
IEC 61850-7-2)
DataAttribute
stVal INT32 ST dchg M
q Quality ST qchg M
t TimeStamp ST M
blkEna BOOLEAN BL O
units Unit CF dchg O
Services
ctlVal INT32

Analog Set Point Control (APC)
Edition 1
Edition 2
Ed2.1

Integer Controlled Step Position (ISC) Edition 1
ISC class
attribute
name
DataName Inherited from GenDataObject Class or from GenSubDataObject Class (see IEC 61850-7-2)
DataAttribute
valWTr ValWithTrans ST dchg AC_ST
q Quality ST qchg AC_ST
t TimeStamp ST AC_ST
subVal ValWithTrans SV PICS_SUBST
blkEna BOOLEAN BL O
Ed2.1 cdcNs VISIBLE STRING255 EX AC_DLNDA_M
Services
104 © Copyright 2018 SISCO. All
As defined Rights31Reserved
in Table
ctlVal INT8 –64 … 63
Transitional Values (valWTr)
From IEC61850-7-3
transInd = 1 equipment in a transitional state (value is changing)

attribute
BSC class
name
Binary Controlled Step Position (BSC)

DataName
attribute
name
DataAttribute
Inherited from GenDataObject Class or from GenSubDataObject Class (see IEC 61850-7-2)
Edition 1
DataAttributeOriginator
origin ST AC_CO_O
ctlNum INT8U ST status and control
0..255mirror AC_CO_O
origin
valWTr Originator
ValWithTrans ST dchg AC_CO_O
AC_ST
ctlNum
q INT8U
Quality ST qchg 0..255 AC_CO_O
AC_ST
valWTr
t ValWithTrans
TimeStamp ST dchg AC_ST
q
stSeld Quality
BOOLEAN ST qchg
dchg AC_ST
O
topRcvd TimeStamp
BOOLEAN ST
OR dchg AC_ST
O
stSeld
opOk BOOLEAN ST
OR dchg O
opRcvd
tOpOk BOOLEAN
TimeStamp OR dchg O
opOk BOOLEAN OR substitution
dchg and blocked O
tOpOk
subEna TimeStamp
BOOLEAN OR
SV O
PICS_SUBST
subVal ValWithTrans SV substitution and blocked PICS_SUBST
subEna
subQ BOOLEAN
Quality SV PICS_SUBST
subVal
subID ValWithTrans
VISIBLE STRING64 SV PICS_SUBST
subQ
blkEna Quality
BOOLEAN SV
BL PICS_SUBST
O
subID VISIBLE STRING64 SV
configuration, description and extension PICS_SUBST
blkEna
persistent BOOLEAN BL
CF dchg O
M
Edition 2 ctlModel CtlModels configuration,
CF description and extension
dchg M
persistent
sboTimeout BOOLEAN
INT32U CF dchg M
AC_CO_O
ctlModel
sboClass CtlModels
SboClasses CF dchg M
AC_CO_O
sboTimeout
minVal INT32U
INT8 CF dchg AC_CO_O
O
sboClass
maxVal SboClasses
INT8 CF dchg AC_CO_O
O
minVal
operTimeout INT8
INT32U CF dchg O
AC_CO_O
maxVal
d INT8
VISIBLE STRING255 CF
DC dchg Text O
operTimeout UNICODE
dU INT32U STRING255 CF
DC dchg AC_CO_O
O
d
cdcNs VISIBLE STRING255 DC
EX Text O
AC_DLNDA_M
dU
cdcName UNICODESTRING255
VISIBLE STRING255 DC
EX O
AC_DLNDA_M
Ed2.1 cdcNs
dataNs VISIBLE STRING255 EX AC_DLNDA_M
AC_DLN_M
cdcName
Services VISIBLE STRING255 EX AC_DLNDA_M
dataNs
As VISIBLE
defined in Table 31 STRING255 EX AC_DLN_M
Services parameters for control services
AsService
definedparameter
in Table 31name Service parameter type Value/Value range
ctlVal CODED ENUM stop | lower | higher | reserved
ctlVal CODED ENUM stop | lower | higher | reserved
Measured Value - MV
MV class
attribute
name
DataAttribute
measured attributes
instMag AnalogueValue MX O
mag AnalogueValue MX dchg, M
dupd
range ENUMERATED MX dchg normal|high|low|high-high|low-low O
q Quality MX qchg M
t TimeStamp MX M
subMag AnalogueValue SV PICS_SUBST
blkEna BOOLEAN BL O
units Unit CF dchg see Annex A O
db INT32U CF dchg 0 … 100 000 O
zeroDb INT32U CF dchg 0 … 100 000 O
sVC ScaledValueConfig CF dchg AC_SCAV
rangeC RangeConfig CF dchg GC_CON_range
smpRate INT32U CF dchg O
Services
107 As defined
© Copyright 2018 SISCO. All Rights in Table 21
Reserved
instMag v.s. mag
• Use mag in datasets to trigger a report when data changes

• Use instMag in datasets for reporting data without triggering a report

Measured Value - MV
MV class
attribute
name
DataAttribute
measured attributes
instMag AnalogueValue MX O
mag AnalogueValue MX dchg, M
dupd
q Quality MX qchg M
t TimeStamp MX M
subMag AnalogueValue SV PICS_SUBST
blkEna BOOLEAN BL O
Services
109 As defined
© Copyright 2018 SISCO. All Rights in Table 21
Reserved
AnalogueValue
GC_1 = At least one attribute must be present.

Range Configuration (RangeConfig)
RangeConfig type definition
Attribute name Attribute type Value/Value range M/O/C

hhLim AnalogueValue M
hLim AnalogueValue M
lLim AnalogueValue M
llLim AnalogueValue M
min AnalogueValue M
max AnalogueValue M
Edition 2 limDb INT32U 0 … 100 000 O
min < llLim < lLim < hLim < hhLim < max
limDb – Limit deadband in units of .1% (.001) of full

scale for hysteresis of range alarms
Scaling of Integer Values
multiplier
floating point value (f) x 10 = (integer value (i) x scaleFactor) + offset
12

Multipliers

Base Units

Derived Units

Extended and Industry Specific Units

Sampled Values (SAV)
SAV class
attribute
name
DataAttribute
measured attributes
instMag AnalogueValue MX M
q Quality MX qchg M
t TimeStamp MX O
min AnalogueValue CF dchg O
max AnalogueValue CF dchg O
Services
CMV class
attribute
Complex Measured Value (CMV) name
DataAttribute
measured attributes
instCVal Vector MX O
cVal Vector MX dchg, M
dupd
Edition 2 rangeAng ENUMERATED MX dchg normal|high|low|high-high|low-low O
q Quality MX qchg M
t TimeStamp MX M
subCVal Vector SV PICS_SUBST
Edition 2 subID VISIBLE STRING64 SV PICS_SUBST
blkEna BOOLEAN BL O
dbAng INT32U CF dchg 0 … 100 000 O
Edition 2 rangeAngC RangeConfig CF dchg GC_CON_rangeAng
magSVC ScaledValueConfig CF dchg AC_SCAV
Edition 2 angSVC ScaledValueConfig CF dchg AC_SCAV
angRef ENUMERATED CF dchg V | A | other ¦ Synchrophasor O
Services
Vector and AnalogueValue
GC_1 = At least one attribute must be present.

WYE Connected Measurements (WYE)
WYE class
attribute
name
SubDataObject
phsA CMV GC_1
phsB CMV GC_1
phsC CMV GC_1
neut CMV GC_1
net CMV GC_1
res CMV GC_1
DataAttribute
angRef ENUMERATED CF dchg Va | Vb | Vc | Aa | Ab | Ac | Vab | Vbc | O
Vca | Vother | Aother | Synchrophasor
Edition 2 phsToNeut BOOLEAN CF dchg DEFAULT = FALSE O
Services

Delta Connected Measurements (DEL)
DEL class
data Type FC TrgOp Value/Value range M/O/C
attribute
name
SubDataObject
phsAB CMV GC_1
phsBC CMV GC_1
phsCA CMV GC_1
DataAttribute
Vca | Vother | Aother | Synchrophasor
Services

Sequence Measurements (SEQ)
Ed2.1

Harmonic Values (HMV)
HMV class
attribute Type FC TrgOp Value/Value range M/O/C
name
Edition 1 DataAttributes
q Quality MX qchg M
t TimeStamp MX M
SubDataObject
har ARRAY 0..numHar OF CMV (was Vector in Edition 1) M
DataAttribute
numHar INT16U CF dchg >0 M
numCyc INT16U CF dchg >0 M
evalTm INT16U CF dchg M
frequency FLOAT32 CF dchg nominal frequency M
hvRef ENUMERATED CF dchg fundamental | rms | absolute O
rmsCyc INT16U CF dchg AC_RMS_M

Harmonic Values for WYE (HWYE)
HWYE class
name
q Quality MX qchg M
t TimeStamp MX M
SubDataObject
phsAHar ARRAY 0..numHar OF CMV (was Vector in Edition 1) M
phsBHar ARRAY 0..numHar OF CMV (was Vector in Edition 1) O
phsCHar ARRAY 0..numHar OF CMV (was Vector in Edition 1) O
neutHar ARRAY 0..numHar OF CMV (was Vector in Edition 1) O
netHar ARRAY 0..numHar OF CMV (was Vector in Edition 1) O
resHar ARRAY 0..numHar OF CMV (was Vector in Edition 1) O
DataAttribute
Units Unit CF see Annex A O
Vca | Vother | Aother
frequency FLOAT32 CF dchg fundamental frequency M

Harmonic Values for Delta (HDEL)
HDEL class
attribute
name
q Quality MX qchg M
t TimeStamp MX M
SubDataObject
phsABHar ARRAY 0..numHar OF CMV M
phsBCHar ARRAY 0..numHar OF CMV O
phsCAHar ARRAY 0..numHar OF CMV O
DataAttribute
units Unit CF O
Vca | Vother | Aother
frequency FLOAT32 CF dchg nominal frequency M

Protection Activation - ACT
ACT class
Attribute Type FC TrgOp Value/Value range M/O/C
name
DataAttribute
status
general BOOLEAN ST dchg M
phsA BOOLEAN ST dchg O
phsB BOOLEAN ST dchg O
phsC BOOLEAN ST dchg O
neut BOOLEAN ST dchg O
q Quality ST qchg M
t TimeStamp ST M
originSrc Originator ST O
Edition 2
operTmPhsA TimeStamp ST O
operTmPhsB TimeStamp ST O
operTmPhsC TimeStamp ST O
operTm Timestamp CF

Directional Protection Activation (ACD)
Ed2.1
127 © Copyright 2018 SISCO. All Rights Reserved GC_2 (x) = All or none of the attributes in group x should be present
Security Violation Counter (SEC)
From IEC61850-7-3
Ed2.1

Binary Counter for Reading (BCR)
BCR class
name
DataAttribute
status
actVal INT64 (INT128 in Ed.1) ST dchg M
frVal INT64 (INT128 in Ed.1) ST dupd GC_2_1
frTm TimeStamp ST GC_2_1
q Quality ST qchg M
t TimeStamp ST M
pulsQty FLOAT32 CF dchg M
frEna BOOLEAN CF dchg GC_2_1
strTm TimeStamp CF dchg GC_2_1
frPd INT32 CF dchg GC_2_1
frRs BOOLEAN CF dchg GC_2_1
129 © Copyright 2018 SISCO. All Rights Reserved frVal = Frozen value
Histogram – HST
HST class
name
DataAttribute
status
hstVal ARRAY 0..maxPts-1 ST dchg, M
OF INT32 dupd
q Quality ST qchg M
t TimeStamp ST M
numPts INT16U CF 0 < numPts ≤ maxPts M
hstRangeC ARRAY 0..maxPts-1 CF dchg M
OF Cells
xUnits Unit CF M
yUnits Unit CF O
units Unit CF O
maxPts INT16U CF M
xD VISIBLE STRING255 DC M
xDU UNICODE STRING255 DC O
yD VISIBLE STRING255 DC O
yDU UNICODE STRING255 DC O
A histogram represents a series of values based on an evaluation of that value in a certain range.

Histogram Application
10
4;10 8;10 12;10
5 3
4;8 8;8
12;8
4;4
Y-Axis
10;4 12;4
10 9
0;0 4;0 10;0
X-Axis
10
For that example, the values would be as follows:
index 0 1 2 3 4 5
hstVal 0 10 9 1 5 3
hstRangeC 0;0 / 4;10 4;0 / 10,4 10;0 / 12;4 4;4 / 12;8 4;8 / 8;10 8;8 / 12;10

Single Point Setting (SPG)
From IEC61850-7-3
Ed2.1
• AC_NSG_M Mandatory if Setting Groups are NOT supported
• AC_SG_M Mandatory if Setting Groups are supported

Analog Setting (ASG)
ASG class
name
DataAttribute
setting
setMag AnalogueValue SP dchg AC_NSG_M
setMag AnalogueValue SG, SE AC_SG_M
minVal AnalogueValue CF dchg O
maxVal AnalogueValue CF dchg O
stepSize AnalogueValue CF dchg 0 … (maxVal – minVal) O
 AC_NSG_M Mandatory if Setting Groups are NOT supported
 AC_SG_M Mandatory if Setting Groups are supported

Integer Setting (ING)
ING class
name
DataAttribute
setting
setVal INT32 SP dchg AC_NSG_M
setVal INT32 SG, SE AC_SG_M
Edition 2 units Unit CF dchg O

Setting Curve (CURVE)
CURVE class
name
DataAttribute
Setting
setCharact ENUMERATED SP dchg AC_NSG_M
setParA FLOAT32 SP dchg AC_NSG_O
setParB FLOAT32 SP dchg AC_NSG_O
setParC FLOAT32 SP dchg AC_NSG_O
setParD FLOAT32 SP dchg AC_NSG_O
setParE FLOAT32 SP dchg AC_NSG_O
setParF FLOAT32 SP dchg AC_NSG_O
setCharact ENUMERATED SG, SE AC_SG_M
setParA FLOAT32 SG, SE AC_SG_O
setParB FLOAT32 SG, SE AC_SG_O
setParC FLOAT32 SG, SE AC_SG_O
setParD FLOAT32 SG, SE AC_SG_O
setParE FLOAT32 SG, SE AC_SG_O
setParF FLOAT32 SG, SE AC_SG_O

Curve Characteristics (setCharact)
See Curve Setting

Description (CSD) for
shape of the curve

Curve Shape Setting – CSG
CSG class
name
IEC 61850-7-2)
DataAttribute
setting
pointZ FLOAT32 SP AC_NSG_O
numPts INT16U SP 1 < numPts ≤ maxPts AC_NSG_M
crvPts ARRAY 0..maxPts-1 SP AC_NSG_M
OF Point
pointZ FLOAT32 SG, SE AC_SG_O
numPts INT16U SG, SE 1 < numPts ≤ maxPts AC_SG_M
crvPts ARRAY 0..maxPts-1 SG, SE AC_SG_M
OF Point
xUnit Unit CF M
yUnit Unit CF M
zUnit Unit CF O
maxPts INT16U CF M
xDU UNICODE STRING255 DC O
yD VISIBLE STRING255 DC M
zD VISIBLE STRING255 DC O
zDU UNICODE STRING255 DC O

Curve Shape Description (CSD)
CSD class
Attribute Attribute type FC TrgOp Value/Value range M/O/C
name
DataAttribute
xUnits Unit DC M
Edition 2 xDU UNICODE STRING255 DC O
yUnits Unit DC M
yD VISIBLE STRING255 DC M
zUnits Unit DC O
Edition 2
zD VISIBLE STRING255 DC O
zDU UNICODE STRING255 DC O
numPts INT16U DC >1 M
crvPts ARRAY 0..numPts-1 DC M
OF Point

Object Reference Setting – ORG
ORG class
attribute Type FC TrgOp Value/Value Range M/O/C
Name
DataAttribute
Setting
setSrcRef ObjectReference SP dchg Object Reference M
setTstRef ObjectReference SP dchg Object Reference GC_2_1
setSrcCB ObjectReference SP dchg Object Reference O
setTstCB ObjectReference SP dchg Object Reference GC_CON_setT
stRef
intAddr VISIBLE STRING255 SP dchg O
tstEna BOOLEAN SP dchg GC_2_1
purpose VISIBLE STRING255 DC O

Object Reference Syntax
The ObjectReference syntax shall be:
LDName/LNName[.Name[. ...]]
– The “/” shall separate the instance name of a logical device (LDName) from the
name of an instance of a logical node (LNName).
– The “.” shall separate the further names in the hierarchy.
– The “[. ]” indicates an option.
– The “[. ...]” indicates further names of recursively nested definitions.
– The “(…)” shall indicate an array element
– The type is VISIBLESTRING129 (up to 129 characters)

Time Setting – TSG
TSG class
name
DataAttribute
Setting
setTm TimeStamp SP dchg AC_NSG_C1
setCal CalendarTime SP dchg AC_NSG_C1
setTm TimeStamp SG, SE AC_SG_C1
setCal CalendarTime SG, SE AC_SG_C1

CalendarTime
CalendarTime type definition
Attribute name Attribute type Value/Value range M/O/C
occ INT16U M
occType ENUMERATED Time, WeekDay, WeekOfYear, DayOfMonth, M

DayOfYear
occPer ENUMERATED Hour, Day, Week, Month, Year M
weekDay ENUMERATED reserved, Monday, Tuesday, … Sunday M
month ENUMERATED reserved, January, February, … December M
day INT8U 1..31 M
hr INT8U 0..24 M
mn INT8U 0..59 M
occ: Occurrence of a calendar element. The value 0 is used to indicate the

last. For the identification of week numbers, week number 01 shall
always be the first week in January (according to definition of UN /
CEFACT).
occType: the kind of calendar element that is used for the occurrence.
occPer: the repetition period of a calendar based time setting.

Currency Setting - CUG
CUG class
name
DataAttribute
Setting
cur Currency SP dchg ISO 4217 3-character currency code AC_NSG_M
cur Currency SG, SE ISO 4217 3-character currency code AC_SG_M

Service Tracking CDCs
• Used in ACSI (IEC 61850-7-2) to provide the means to control
and track control blocks and commands.
– Replaces the object type descriptions of control blocks in Edition 1.
– Mapping in IEC 61850-8-1 results in substantially similar objects and
interactions.
• Based on a general Common Service Tracking (CST) CDC

Common Data Classes – Control Block Service Tracking
Name Description
CTS Common Service Tracking
BTS Buffered Report Tracking Service
UTS Unbuffered Report Tracking Service
LTS Log Control Block Tracking Service
GTS GOOSE Control Block Tracking Service
MTS Multicast Sampled Value (9-2) Control Block Tracking Service
NTS Unicast Sample Value (9-1) Control Block Tracking Service
SGCB Setting Group Control Block Tracking Service

Common Service Tracking – CST
CST Class
Attribute name Attribute type FC TrgOp r/w Value/Value range M/O/C
DataName Inherited from Data Class
Specific to the CST
objRef ObjectReference SR dupd r Reference of the object that M
is used in the tracking:
either a control block that is
being accessed or a control
object that is being
controlled.
serviceType ServiceType SR r Type of the tracked service M
errorCode ServiceError SR r See error associated to the M
service that is specified by
serviceType; value None for
successful service
originatorID OCTET STRING64 SR r Originator of the service O
t TimeStamp SR r TimeStamp of the M
completion of the service or
entryTime for report buffer
entries
d VISIBLE STRING255 DC r O
dU UNICODE STRING255 DC r O
cdcNs VISIBLE STRING255 EX r AC_DLNDA_M Ed2.1
cdcName VISIBLE STRING255 EX r AC_DLNDA_M
dataNs VISIBLE STRING255 EX r AC_DLN_M
For Control Blocks: ObjectReference = LDName/LNName.CBName

GetEditSGValue 20
GetSGCBValues 21
ServiceType
Report 22
GetBRCBValues 23
SetBRCBValues 24
GetURCBValues 25
SetURCBValues 26
ACSI value MMS value
GetLCBValues 27
Unknown 0 SetLCBValues 28
Associate 1 QueryLogByTime 29
Abort 2 QueryLogAfter 30
GetLogStatusValues 31
Release 3
SendGOOSEMessage 32
GetServerDirectory 4
GetGoCBValues 33
GetLogicalDeviceDirectory 5 SetGoCBValues 34
GetAllDataVaues 6 GetGoReference 35
GetDataValues 7 GetGOOSEElementNumber 36
SendMSVMessage 37
SetDataValues 8
GetMSVCBValues 38
GetDataDirectory 9
SetMSVCBValues 39
GetDataDefinition 10 SendUSVMessage 40
GetDataSetValues 11 GetUSVCBValues 41
SetUSVCBValues 42
SetDataSetValues 12
Select 43
CreateDataSet 13
SelectWithValue 44
DeleteDataSet 14 Cancel 45
GetDataSetDirectory 15 Operate 46
SelectActiveSG 16 CommandTermination 47
TimeActivatedOperate 48
SelectEditSG 17
GetFile 49
SetEditSGValue 18
SetFile 50
ConfirmEditSGValues 19
DeleteFile 51
GetEditSGValue 20 GetFileAttributeValues 52
GetSGCBValues 21 TimeSynchronization 53
Report 22 InternalChangeUnknown 54
GetBRCBValues 23
147 SetBRCBValues
© Copyright 2018 SISCO. All Rights Reserved 24
GetURCBValues 25
SetURCBValues 26
GetLCBValues 27
ServiceError
no-error 0
instance-not-available 1
instance-in-use 2
access-violation 3
access-not-allowed-in-current-state 4
parameter-value-inappropriate 5
parameter-value-inconsistent 6
class-not-supported 7
instance-locked-by-other-client 8
control-must-be-selected 9
type-conflict 10
failed-due-to-communications-constraint 11
failed-due-to-server-constraint 12

Buffered Report Tracking Service – BST
BTS Class
Attribute name Attribute type FC TrgOp r/w Value/value range M/O/C
Shall inherit all the data attributes of the CST CDC
Specific to the BTS
rptID VISIBLE STRING129 SR r Service parameter ReportIdentifier is M
mapped to rptID
rptEna BOOLEAN SR r Service parameter ReportEnable is M

mapped to rptEna
datSet ObjectReference SR r Service parameter DatSetReference is M

mapped to datSet
confRev INT32U SR r Service parameter ConfigurationR evision M

is mapped to confRev
optFlds PACKED_LIST SR r Service parameter OptionalFields is M

mapped to optFlds
bufTm INT32U SR r Service parameter BufferTime is mapped M

to bufTm
sqNum INT32U SR r Attribute SqNum of BRCB is mapped to M

sqNum
trgOps TriggerConditions SR r Service parameter M

TriggerOptionsEnabled is mapped to
trgOps
intgPd INT32U SR r Service parameter IntegrityPeriod is M

mapped to intgPd
gi BOOLEAN SR r Service parameter GeneralInterrogation M

is mapped to go
purgeBuf BOOLEAN SR r Service parameter PurgeBuf is mapped M

to purgeBuf
entryID EntryID SR r Service parameter EntryIdentifier is M

mapped to entryID
timeOfEntry EntryTime SR r Service parameter TimeOfEntry is M

mapped to timeOfEntry
resvTms INT16 SR r Service parameter ReserveTimeSecond O

is mapped to resvTms

Unbuffered Report Tracking Service – UTS
UTS Class
Specific to the UTS
rptID VISIBLE STRING129 SR r Service parameter ReportIdentifier M
is mapped to rptID
rptEna BOOLEAN SR r Service parameter ReportEnable M

is mapped to rptEna
resv BOOLEAN SR r Service parameter Reserve M

datSet ObjectReference SR r Service parameter M
DatSetReference is mapped to
datSet
confRev INT32U SR r Service parameter M

ConfigurationRevision is mapped
to confRev
optFlds PACKED_LIST SR r Service parameter OptionalFields M

is mapped to optFlds
bufTm INT32U SR r Service parameter BufferTime is M

mapped to bufTm
sqNum INT32U SR r Attribute SqNum of BRCB is M

mapped to sqNum

TriggerOptionsEnabled is mapped
to trgOps
intgPd INT32U SR r Service parameter IntegrityPeriod M

is mapped to intgPd
gi BOOLEAN SR r Service parameter M

GeneralInterrogation is mapped to
go

Log Control Block Tracking Service – LTS
LTS Class
Specific to the LTS
logEna BOOLEAN SR r Service parameter LogEnable M
is mapped to logEna
DataSetReference is mapped
to datSet
optFlds PACKED LIST SR r Service parameter M
OptionalFields is mapped to
optFlds
bufTm INT32U SR r Service parameter BufferTime M
is mapped to bufTm
TriggerOptions is mapped to
trgOps
intgPd INT32U SR r Service parameter M
IntegrityPerdiod is mapped to
intgPd
logRef ObjectReference SR r Service parameter M
LogReference is mapped to
logRef

Log Tracking Service – LTS
OTS Class
Specific to the LTS
oldEntrTm TimeStamp SR r Service parameter OldestEntryTime is M
mapped to oldEntrTm
newEntrTm TimeStamp SR r Service parameter NewestEntryTime is M

mapped to newEntrTm
oldEntr INT32U SR r Service parameter OldestEntry is M

mapped to oldEntr
newEntr INT32U SR r Service parameter NewestEntry is M

mapped to newEntr
rangeStrTm TimeStamp SR r Service parameter RangeStartTime is M

mapped to rangeStrTm
rangeStpTm TimeStamp SR r Service parameter RangeStopTime is M

mapped to rangeStpTm
entry EntryID SR r Service parameter Entry is mapped to M

entry

GOOSE Control Block Tracking Service – GTS
GTS Class
Specific to the GTS
goEna BOOLEAN SR r The service parameter GoEnable M
is mapped to goEna
goID VISIBLE STRING 129 SR r The service parameter GOOSEID M

is mapped to goID
datSet ObjectReference SR r The service parameter M

DataSetReference is mapped to
datSet
confRev INT32U SR r The service parameter M

to confRev
ndsCom BOOLEAN SR r The service parameter M

NeedsCommissioning is mapped
to ndsCom
dstAddress PHYCOMADDR SR r The service parameter M

DestinationAddress is mapped to
dstAddress

Multicast Sampled Value Control Block Tracking Service – MTS
MTS Class
Specific to the MTS
svEna BOOLEAN SR r The service parameter SvEnable is M
mapped to svEna
msvID VISIBLE STRING 129 SR r The service parameter M

MulticastSampleValueID is mapped
to msvID
datSet ObjectReference SR r The service parameter M

DataSetReference is mapped to
datSet
confRev INT32U SR r The service parameter M

ConfigurationRevision is mapped to
conRev
smpMod ENUMERATED SR r The service parameter M

SampleMode is mapped to smpMod
smpRate INT16U SR r The service parameter SampleRate M

is mapped to smpRate
optFlds PACKED LIST SR r The service parameter M

OptionalFields is mapped to
optFlds
dstAddress PHYCOMADDR SR r The service parameter M

DestinationAddress is mapped to
dstAddress

Setting Group Control Block Tracking Service – STS
STS Class
Specific to the STS
numOfSG INT8U SR r The service parameter M
NumberOfSettingGroup is mapped
to numOfSG
actSG INT8U SR r The service parameter M

ActiveSettingGroup is mapped to
actSG
editSG INT8U SR r The service parameters M

SettingGroupNumber resp.
EditSettingGroup are mapped to
editSG
cnfEdit BOOLEAN SR r M
lActTm TimeStamp SR r The service parameter M
LastActivateTime is mapped to
lActTm
resvTms INT16U SR r O

Questions - Discussion

Logical Nodes

Logical Device Structure IEC61850 Clients

Client
Functions
Logical Logical
Device 1 to N Logical Devices Device
Logical
Node
... Logical
Node
Logical
Node
... Logical
Node
Data … Data Data … Data Data … Data Data … Data
Process Bus

Logical Node
A named grouping of data and associated
services that is logically related to some power
system function.

Examples of Logical Nodes
Current
Transformer
Voltage
Breaker Transformer
Breaker
Switch
Breaker Controller
Name Description
Axxx Automatic Control
IEC61850 Logical Node Naming Cxxx Supervisory Control
and Groups Dxxx Distribution and Distributed Energy Resources
Fxxx Functional Blocks
Gxxx Generic Functions
Ixxx Interfacing/Archiving
Kxxx Mechanical and Non-Electrical Equipment
Lxxx System Logical Nodes
Mxxx Metering & Measurement
Pxxx Protection
Qxxx Power Quality Events
Rxxx Protection Related
Sxxx Supervision, Sensors and Monitoring
Txxx Instrument Transformer
Xxxx Switchgear
Yxxx Power Transformer
Zxxx Other Equipment
Wxxx Wind
Oxxx Solar
Hxxx Hydropower
Nxxx Power Plant
Bxxx Battery
Fxxx Fuel Cells

Logical Node Listing
• Listing of IEC61850 logical nodes follows.
• We will look at several in detail
• Make a note of others you are interested in for a closer review

System Logical Nodes
Name Description
LPHD Physical Device
LLNO Common Logical Node MANDATORY
LCCH Physical Communications Channel Supervision
LGOS GOOSE Subscription
LTIM Time Management
LTMS Time Master Supervision
LTRK Service Tracking

Automatic Control Logical Nodes
Name Description
ANCR Neutral Current Regulator
ARCO Reactive Power Control
ARIS Resistor Control
ATCC Automatic Tap Changer controller
AVCO Voltage Control

Supervisory Control Logical Nodes
Name Description
CALH Alarm Handling
CCGR Cooling Group Control
CILO Interlocking
CPOW Point-on-wave switching
CSWI Switch Controller
CSYN Synchronizer Controller

Functional Block Logical Nodes
Name Description
FCNT Counter
FCSD Curve Shape Description
FFIL Generic Filter
FLIM Control Function Output Limitation
FPID PID Regulator
FRMP Ramp Function
FSPT Set-Point Control Function
FXOT Action at Over Threshold
FXUT Action at Under Threshold

Generic Function Logical Nodes
Name Description
GAPC Generic Automatic Process Control
GGIO Generic Process I/O
GLOG Generic Log
GSAL Generic Security Application

Interfacing and Archiving Logical Nodes
Name Description
IARC Archiving
IHMI Human Machine Interface
ITCI Telecontrol Interface
ITMI Telemonitoring Interface
ISAF Safety Alarm Function
ITPC Teleprotection Communications Interface

Mechanical and Non-Electrical Logical Nodes “K”
Name Description
KFAN Fan
KFIL Filter
KPMP Pump
KTNK Tank
KVLV Valve Control

Metering and Measurement Logical Nodes
Name Description
MDIF Differential measurements
MHAI Harmonics or interharmonics
MHAN Non phase related harmonics or interharmonics
MMTR Metering
MMXN Non phase related measurements
MMXU Measurements
MSQI Sequence and Imbalance
MSTA Metering Statistics
MENV Environmental Information
MFLK Flicker Measurement
MHYD Hydrological Information
MMDS DC Measurement
MMET Metrological Information

Protection Logical Nodes
Name Description
PDIF Differential
PDIR Direction
PDIS Distance
PDOP Directional overpower
PDUP Directional underpower
PFRC Rate of change of frequency
PHAR Harmonic restraint
PHIZ Ground detector
PIOC Instantaneous overcurrent
PMRI Motor restart inhibition
PMSS Motor starting time supervision
POPF Over power factor
PPAM Phase angle measuring

Protection Logical Nodes (cont’d)
Name Description
PSCH Protection scheme
PSDE Sensitive directional earth fault
PTEF Transient earth fault
PTOC Time over current
PTOF Over frequency
PTOV Over voltage
PTRC Protection trip conditioning
PTTR Thermal overload
PTUC Under current
PTUV Under voltage
PVOC Voltage controlled time over current
PVPH Volts per Hz
PZSU Zero speed or under speed

Protection Logical Nodes (cont’d)
Name Description
PRTR Rotor Protection
PTHF Thyristor Protection
PUPF Underpower Factor Protection
PSOF Switch on to Fault
PTDV Voltage Differential

Power Quality Events Logical Nodes
Name Description
QFVR Frequency Variation
QITR Current Transient
QIUB Current Unbalance Variation
QVTR Voltage Transient
QVUB Voltage Unbalance Variation
QVVR Voltage Variation

Protection Related Logical Nodes
Name Description
RDRE Disturbance recorder function
RADR Disturbance recorder channel analogue
RBDR Disturbance recorder channel binary
RDRS Disturbance record handling
RBRF Breaker failure
RDIR Directional element
RFLO Fault locator
RPSB Power swing detection/blocking
RREC Auto reclosing
RSYN Synchronism-check or synchronising
RMXU Differential Measurements

Supervision, Sensors and Monitoring Logical Nodes
Name Description
SARC Monitoring and diagnostics for arcs
SIMG Insulation medium supervision
SIML Insulation medium supervision (liquid)
SPDC Monitoring and diag. for partial discharges
SCBR Circuit Breaker Supervision
SLTC Tap Changer Supervision
SOPM Supervision of Operating Mechanism
SPTR Power Transformer Supervision
SPRS Pressure Supervision
SSWI Circuit Switch Supervision
STMP Temperature Supervision
SVBR Vibration Supervision

Instrument Transformer Logical Nodes
Name Description
TCTR Current transformer
TVTR Voltage transformer
TANG Angle
TAXD Axial Displacement
TDST Distance
TFLW Liquid Flow
TFRQ Frequency
TGSN Generic Sensor
THUM Humidity
TLVL Media Level

Instrument Transformer Logical Nodes (cont’d)
Name Description
TMGF Magnetic Field
TMVM Movement Sensor
TPOS Position Indicator
TPRS Pressure Sensor
TRTN Rotation Transmitter
TSND Sound Pressure Sensor
TTMP Temperature Sensor
TTNS Mechanical Tension/stress
TVBR Vibration Sensor
TWPH Water Acidity

Switchgear Logical Nodes
Name Description
XCBR Circuit Breaker
Ed2.1 XFUS Circuit Fuse
XSWI Circuit Switch

Power Transformer Logical Nodes
Name Description
YEFN Earth fault neutralizer
YLTC Tap changer
YPSH Power shunt
YPTR Power transformer

Other Power System Equipment Logical Nodes
Name Description
ZAXN Auxiliary network
ZBAT Battery
ZBSH Bushing
ZCAB Power cable
ZCAP Capacitor Bank
ZCON Converter
ZGEN Generator
ZGIL Gas insulated line
ZLIN Power overhead line
ZMOT Motor
ZREA Reactor
ZRRC Rotating reactive component
ZSAR Surge arrestor
ZTCF Thyristor controlled frequency converter
ZTCR Thyristor controlled reactive component
ZRES Resistor
ZSCR Semiconductor Controlled Rectifier
ZSMC Synchronous Machine

Logical Node Names
• Example for Circuit Breaker:

ddd XCBR01
Logical Node Instance #
Logical Node Name per

IEC 61850-7-4 (circuit breaker)
Optional Application Specific Prefix
prefix digits + instance digits ≤ 7 (Ed. 1)

prefix digits + instance digits ≤ 12 (Ed. 2)
Logical Node Classes
LN
LPHD Common LN Inherited

Relationships
LLN0 Domain Specific An IEC 61850 device

LNs (i.e. XCBR) must contain LPHD, LLN0,
and 1 or more domain
specific logical nodes.

Note on Ed2.1 Logical Node Descriptions
• Ed2.1 (Amendment 1 to Edition 2) was rebuilt completely using Unified
Modeling Language (UML)
• The actual text of the IEC 61850 standards is auto generated from UML
• Logical Node (LN) descriptions have many more inherited relationships

than shown here
• The Ed2.1 standards can be more difficult to read but the presentation
here is still reasonably accurate

Physical Device - LPHD
LPHD class
Data object Common Explanation T M/O/
name data class C
Data objects
Status information
PhyNam DPL Physical device name plate M
PhyHealth ENS Physical device health M
OutOv SPS Output communications buffer overflow O
Proxy SPS Indicates if this LN is a proxy M
InOv SPS Input communications buffer overflow O Only LN that does
NumPwrUp INS Number of Power ups O not inherit
WrmStr INS Number of Warm Starts O Common LN
WacTrg INS Number of watchdog device resets detected O properties.
PwrUp SPS Power Up detected O Inherits a name
PwrDn SPS Power Down detected O
only.
PwrSupAlm SPS External power supply alarm O
Controls
RsStat SPC Reset device statistics TO
Edition 2 Sim SPC Receive simulated GOOSE or simulated SV O

Settings
Ed2.1 DataMaxDl ING
Sets (see IEC 61850-7-2)
Maximum processing delay of samples if IEC 61869 is applied to this device
Inherited and specialised from Logical Node class (see IEC 61850-7-2)
BuffferedReportControlBlock (see IEC 61850-7-2)
UnbuffferedReportControlBlock (see IEC 61850-7-2)
Transient Data
• Designated by “T” in the Logical Node Definition Table.
• Transient means that the transition from TRUE to FALSE is automatic and does not
cause a DATA-CHANGE.
• For a controllable transient object (e.g. RsStat) the client need only change the state to
TRUE and the object will automatically resume the FALSE state when appropriate.
• BOOLEAN objects only.

Device Name Plate - DPL
DPL class
attribute
name
IEC 61850-7-2)
DataAttribute
hwRev VISIBLE STRING255 DC O
swRev VISIBLE STRING255 DC O
serNum VISIBLE STRING255 DC O
model VISIBLE STRING255 DC O
location VISIBLE STRING255 DC O
name VISIBLE STRING64 DC O
owner VISIBLE STRING255 DC O
ePSName VISIBLE STRING255 DC O
primeOper VISIBLE STRING255 DC O
secondOper VISIBLE STRING255 DC O
latitude FLOAT32 DC O
longitude FLOAT32 DC O
altitude FLOAT32 DC O
mrID VISIBLE STRING255 DC O
Services
Common Logical Node Class – Edition 1
From IEC61850-7-4
ALL other logical nodes contain these attributes even though they are not
listed in the other logical node description tables.

Common Logical Node Class – Edition 2 Changes

Common Logical Node Class – Edition 2
Common LN class
name data class C
Data objects
Mandatory and conditional Logical Node Information (shall be inherited by ALL LN but LPHD)
Mod ENC Mode C1
Beh ENS Behavior M
Health ENS Health C1
NamPlt LPL Name plate C1
Optional Logical Node Information
InRef1 ORG General input O
BlkRef1 ORG Blocking reference shows the receiving of dynamically blocking signal O
Blk SPS Dynamically blocking of function described by the LN O
CmdBlk SPC Blocking of control sequences and action triggers of controllable data C2
objects
GrRef ORG Reference to a higher level Logical Device O
Optional Logical Node Information (statistical calculation specific – refer to annex G)
ClcExp SPS Calculation period expired T C3
ClcStr SPC Enables the calculation start at time operTm from the control model (if O
set) or immediately
ClcMth ENG Calculation Method of statistical data objects. Allowed values C3
PRES_OR_UNKNOWN(default) | TRUE_RMS | PEAK_FUND AMENTAL |
RMS_FUNDAMENTAL | MIN | MAX | AVG | SDV |PREDICTION| RATE
Common Logical Node Class – Edition 2 (cont’d)

CmdBlk SPC Blocking of control sequences and action triggers of controllable data
objects
C2

set) or immediately
ClcMod ENG Calculation mode. Allowed values: C4
TOTAL | PERIOD | SLIDING
ClcIntvTyp ENG Calculation interval typ. Allowed values: C4
MS | PER_CYCLE | CYCLE | DAY | WEEK | MONTH | YEAR |
EXTERNAL
ClcIntvPer ING In case ClcIntvTyp equals to MS, PER-CYCLE, CYCLE, DAY, WEEK, C4
MONTH, YEAR, number of units to consider to calculate the calculation
interval duration
NumSubIntv ING The number of sub-intervals a calculation period interval duration O

contains
ClcRfTyp ENG Refreshment interval typ. Allowed values: MS, PER-CYCLE, CYCLE, O
DAY, WEEK, MONTH, YEAR, EXTERNAL
ClcRfPer ING In case ClcIntvTyp equals to MS, PER-CYCLE, CYCLE, DAY, WEEK, O
MONTH, YEAR, number of units to consider to calculate the refreshment
interval duration
ClcSrc ORG Object Reference to Source logical node C5
ClcNxTmms ING Remaining time up to the end of the current calculation interval – O
expressed in millisecond
InSyn ORG Object reference to the source of the external synchronization signal for
the calculation interval
Data Sets (see IEC 61850-7-2)
BuffferedReportControlBlock (see IEC 61850-7-2)
UnbuffferedReportControlBlock (see IEC 61850-7-2)
Logical Node Name Plate - LPL
LPL class
attribute
name
IEC 61850-7-2)
DataAttribute
ldNs VISIBLE STRING255 EX shall be included in LLN0 only; AC_LN0_EX
for example "IEC 61850-7-4:2003"
Services

Mode and Behavior Mode of LLN0 within that
same logical device
Behavior of
Mode of the the individual
individual logical logical node is
node calculated
Edition 1:
On-Blocked = Blocked

Health
Health Value
OK (Green) 1
Warning (Yellow) minor problems

2
but safe operation
Alarm (Red) severe problem no

3
operation possible

Common Logical Node – LLN0
(Logical Node Zero)
LLNO class
name data class C
Data objects
Status information
LocKey SPS Local operation for complete logical device O
Edition 2
LocSta SPC Switching authority at station level O
Loc SPS Local Control Behavior O
OpTmh INS Operation time O
Controls
Diag SPC Run Diagnostics O
LEDRs SPC LED reset TO
Settings
MltLev SPG Select mode of authority for local control (True – control from multiple O
Edition 2 levels above the selected one is allowed, False – no other control level
above allowed)
SettingGroupControlBlock [0..1] (see IEC 61850-7-2)
The Mode (Mod) and Local/Remote status of this logical node affects all LNs in that Logical Device
Log [0..n](see IEC 61850-7-2)
GOOSEControlBlock [0..n] (see IEC 61850-7-2)
195 © Copyright 2018 SISCO. All RightsInherited
Reserved and specialised from Logical Node class (see IEC 61850-7-2)
MulticastSampledValueControlBlock [0..n] (see IEC 61850-7-2)
UnicastSampledValueControlBlock [0..n] (see IEC 61850-7-2)
LN Containment in Edition 1
Containment
Relationship
Inherited
Relationship

contains 0..1 File contains 0..n File contains 0..n
7 GenServer File
system directory
LN Containment
is associated with 0..1
Service
Access
contains 1..n
23
Point
Hierarchy
is associated with 0..n
contains 0..n
TPAppAssociation Control Blocks
contains 0..n contains 0..n
MCAppAssociation Log 17
Edition 2 is associated with 0..n
9
contains 1..n
LogicalDevice
17
contains 0..n Log Control
refers to one
Block
17
contains 1..n Buffered Report
Control Block
10 LogicalNode contains 0..n
17
Unbuffered Report
contains 0..n Control Block
18
GOOSE
contains 0..n Control Block
19
contains 0..n Multicast Sampl.
Value Control Block
19
Unicast Sampl.
contains 0..n Value Control Block
16 Setting Group
Control Block
contains 0..1
may refer to one
contains 1..n contains 0..n
DataObject DATA-SET
refers to 0..n
influences
influences 11 12 13
Instance of
Tracking
Control influences
14 15 20
20 21
xx reference to clause in this part Time

Physical Communication Channel Supervision – LCCH
LCCH class
Data Object Common Explanation T M/O/
Name Data Class C
Data Objects
ChLiv SPS Physical channel status; true, if channel receives telegrams within a M
specified time interval.
RedChLiv SPS Physical channel status of redundant channel C
OutOv SPS Output communications buffer overflow O
InOv SPS Input communications buffer overflow O
FerCh INS Frame error rate on this channel; count of erroneous (or missed, in case O
of redundancy) messages for each 1000 messages forwarded to the
application.
RedFerCh INS Frame error rate on redundant channel; count of missed messages on O
this channel for each 1000 messages forwarded to the application.
RxCnt BCR Number of received messages O
RedRxCnt BCR Number of received messages on redundant channel O
TxCnt BCR Number of sent messages O
Settings
ApNam VSG Access point name to which this channel belongs; only needed, if more O
than one access point and more than one physical channel exists.
ChLivTms ING Timeout time for channel live supervision; default 5s O
Note: if channel redundancy with duplicate remove is used, the number of lost messages can be calculated as
‘messages forwarded to application as result of both channels – messages received on this channel’. In this case
the FER is calculated by counting thre received messages per channel, until 1000 messages are forw arded to the
198 application,
© Copyright 2018 SISCO. All Rights Reserved and then using above formula per channel.
Observe that in PRP any message received for a wrong channel is also forwarded to the application. Thus a
wrong connection of cables to ports can be detected, if Fer and RedFer have a valu e around 500 (1000 messages
with wrong channel identification forwarded to application, 500 messages with wrong channel identification
GOOSE Subscription – LGOS Ed2
LGOS class
Data Common Explanation T M/O/
object name data class C
LNName The name shall be composed of the class name, the LN -Prefix and LN-
Instance-ID according to IEC 61850-7-2, Clause 22
Data objects
Status information
SbsNdsCom SPS Subscription needs commissioning O
SbsSt SPS Status of the subscription (True = active, False=not active) O
SbsSim SPS Subscription wih simulation O
LastStNum INS Last state number received O
ConfRevNum INS Expected Configuration revision number O
Settings
GoCBRef ORG Reference to the subscribed GOOSE control block O
LGOS reflects the state of a subscribing device’s subscription to

another device’s GOOSE Control Block (Publisher)
GOOSE Subscription (LGOS) Ed2.1
LGOS
Data object Common data class T Explanation PresCond nds/ds
name
Descriptions
NamPlt LPL inherited from: DomainLN MONamPlt / na
Status information
LastStNum INS Last state number of the received GOOSE message. O / na
NdsCom SPS inherited from: SubscriptionSupervisionLN O / na
St SPS inherited from: SubscriptionSupervisionLN M / na
SimSt SPS inherited from: SubscriptionSupervisionLN O / na
ConfRevNum INS inherited from: SubscriptionSupervisionLN O / na
RxConfRevNum INS inherited from: SubscriptionSupervisionLN O / na
Beh ENS (BehaviourModeKind) inherited from: DomainLN M / na
Health ENS (HealthKind) inherited from: DomainLN O / na
Mir SPS inherited from: DomainLN MOcond(1) / na
Controls
Mod ENC (BehaviourModeKind) inherited from: DomainLN O / na
Settings
GoCBRef ORG Object reference of subscribed GOOSE control block. M / na
InRef ORG inherited from: DomainLN Omulti / na

SubscriptionSupervisionLN
SubscriptionSupervisionLN
Data object Common data class T Explanation PresCond nds/ds
name
Descriptions
Status information
NdsCom SPS If true, the subscription needs commissioning, i.e., the received O / na
message does not conform the current subscription configuration
(either the 'dataSetRef' is wrong, the data set members, the
configuration revision number, … or no subscription is configured at
all).
St SPS If true, the subscription is active and valid message forwarded to M / na

application, otherwise it is inactive or messages are not forwarded to
application. ConfRevNum and RxConfRevNum can deliver further
diagnostic information.
SimSt SPS If true, subscribed messages with the simulation bit set are being O / na
received and accepted.
ConfRevNum INS Expected configuration revision number of the message. If no O / na
subscription is configured, the attribute 'q.validity' is set to 'invalid'.
RxConfRevNum INS Configuration revision number of the received messages. If no O / na
telegram is received, the attribute 'q.validity' is set to 'invalid'.
Health ENS (HealthKind) inherited from: DomainLN O / na
Mir SPS inherited from: DomainLN MOcond(1) / na
Controls
Settings

Time Management – LTIM
LTIM class
Data objects
Status information
TmDT SPS Indicating if for this location daylight saving time is in effect now M
Settings
TmOfsTmm ING Offset of local time from UTC in minutes M
TmUseDT SPG Flag indicating if this location is using daylight saving time M
TmChgDayTm TSG Local time of next change to daylight saving time O
TmChgStdTm TSG Local time of next change to standard time O
StrWeekDay ENG Day of the start of the local week for statistical calculation (MONDAY O
(default) | TUESDAY | WEDNESDAY | THURSDAY | FRIDAY |
SATURDAY | SUNDAY )

Time Master Supervision – LTMS
LTMS class
Data objects
Status information
TmAcc ENS Time accuracy class acc. IEC 61850-7-2 O
TmSrc VSS Current time source M
TmSyn ENS Time synchronized acc. IEC 61850-9-2 O
TmChSt1 SPS Time channel status (up/down) O
Settings
TmSrcSet1 VSG Time source setting (“1588” in case the time source is a IEEE1588 O
source or dotted IP-address)

Service Tracking – LTRK
LTRK class
name data class C
Instance-ID according to IEC 61850-7-2, Clause 22.
Data objects
SpcTrk CTS Control Service Tracking for Controllable Single Point O
DpcTrk CTS Control Service Tracking for Controllable Double Point O
IncTrk CTS Control Service Tracking for Controllable Integer O

EncTrk CTS Control Service Tracking for Enumerated Controllable O
ApcTrk CTS Control Service Tracking for Controllable Analog Set Point O
BscTrk CTS Control Service Tracking for Binary controlled step position information O
IscTrk CTS Control Service Tracking for Integer controlled step position information O
BacTrk CTS Control Service Tracking for Binary controlled analog process value O
UrcbTrk UTS Access Service Tracking for Unbuffered Report Control Block O
BrcbTrk BTS Access Service Tracking for Buffered Report Control Block O
LocbTrk LTS Access Service Tracking for Log Control Block O
GocbTrk GTS Access Service Tracking for Goose Control Block O
MsvcbTrk MTS Access Service Tracking for Multicast Sampled Values Control Block O
UsvcbTrk NTS Access Service Tracking for Unicast Sampled Values Control Block O
SgcbTrk STS Access Service Tracking for Settig Group Control Block O

Logical Node Description – XCBR – Edition 2
XCBR class
name data class C
Data objects
LocKey SPS Local or remote key (local means without substation automation O
communication, hardwired direct control)
Edition 2
Loc
Loc SPS
SPS Local Control Behavior M
EEHealth ENS External equipment health O
EEName DPL External equipment name plate O
OpCnt INS Operation counter M
Controls
Pos DPC Switch position M
BlkOpn SPC Block opening M
BlkCls SPC Block closing M
ChaMotEna SPC Charger motor enabled O
Metered values
SumSwARs BCR Sum of Switched Amperes, resetable O
Status information
CBOpCap INS Circuit breaker operating capability O
POWCap INS Point On Wave switching capability O
MaxOpCap INS Circuit breaker operating capability when fully charged O
Dsc SPS Discrepancy O
Edition 2 Settings
CBTmms ING Closing Time of breaker O
Common Data Class

Data Object Names Description Mandatory/Optional/Conditional

Single Point Status (SPS) CDC
(e.g. Loc)
stVal
Data Attribute Names

Data Type of Attribute

Object Name for Local/Remote Attribute of XCBR1
XCBR1.ST.Loc.stVal
Attribute
Data
Functional Constraint
Logical Node
Same in Edition 1 or Edition 2

Mapping of Names via 8-1
• Section 8-1 maps the IEC61850 LN and Data Object
Names to MMS (ISO9506)
• MMS allows only numbers, letters, “$”, and “_” in

object names.
• Resulting MMS Object Name:

XCBR1$ST$Loc$stVal
7-1 Formatted Object Name
XCBR1.Loc.stVal[ST]
Functional
Constraint
Attribute
Data
Logical Node

Object Name Format Used in This Presentation
XCBR1.ST.Loc.stVal
or
XCBR1$ST$Loc$stVal

Breaker Position
Pos DPC
From IEC61850-7-4

Breaker Position
XCBR class
name data class C
Data objects
LocKey SPS Local or remote key (local means without substation automation O
communication, hardwired direct control)
Loc SPS Local Control Behavior M
OpCnt INS Operation counter M
Controls
Pos
Pos DPC
DPC Switch position M
BlkOpn SPC Block opening M
BlkCls SPC Block closing M
ChaMotEna SPC Charger motor enabled O
Metered values
SumSwARs BCR Sum of Switched Amperes, resetable O
Status information
CBOpCap INS Circuit breaker operating capability O
POWCap INS Point On Wave switching capability O
MaxOpCap INS Circuit breaker operating capability when fully charged O
Dsc SPS Discrepancy O
Settings
CBTmms ING Closing Time of breaker O

DPC class
Breaker Position Dat a

at t r ib u t e
n am e
T yp e FC T r g Op V alu e /V alu e r an g e M /O/C
Da t a Name Inhe rited from Ge nDataObject C lass or f rom Ge nSubData Object C lass (see
IEC 61850-7-2)
Da t aAttribute
st a t us a nd cont rol mirror
origin O riginat or ST A C _C O _O
ct lNum INT8U ST 0. . 255 A C _C O _O
st Va l C O DED ENUM ST dchg int e rme diate -stat e | off | on | ba d - M
stVal st a t e
q Q ua lit y ST qchg M
t Time St a mp ST M
st Se ld BO O LEAN ST dchg O
opR cvd BO O LEAN OR dchg O
opO k BO O LEAN OR dchg O
t O pO k Time St a mp OR O
subst it ut ion a nd blocke d
subEna BO O LEAN SV PIC S_SUBST
subVa l C O DED ENUM SV int e rme diate -stat e | off | on | ba d - PIC S_SUBST
st a t e
subQ Q ua lit y SV PIC S_SUBST
subID VISIBLE STR ING64 SV PIC S_SUBST
blkEna BO O LEAN BL O
conf igura t ion, de script ion a nd e x t e nsion
puls e Config Pulse Config CF dchg A C _C O _O
ct lModel C t lModels CF dchg M
sboTime out INT32U CF dchg A C _C O _O
sboC lass SboC lasses CF dchg A C _C O _O
ope rTime out INT32U CF dchg A C _C O _O
d VISIBLE STR ING255 DC Te x t O
dU UNIC O DE STRING255 DC O
cdcNs VISIBLE STR ING255 EX A C _DLNDA _M
cdcNa me VISIBLE STR ING255 EX A C _DLNDA _M
da t a Ns VISIBLE STR ING255 EX A C _DLN_M
Se r vices
A s de f ined in Ta ble 31
213 pa ra me t e rs f or cont rol se rv ice s
Se r vice param e t e r n am e Se r vice param eter t yp e V alu e /V alu e r an g e
ct lVa l BO O LEAN of f (F A LSE) | on (TR UE)
Object Name for Breaker Position Attribute of XCBR1
XCBR1.ST.Pos.stVal
Attribute
Data
Functional Constraint
Logical Node

Switch Controller
Position = CSWI1$ST$Pos$stVal

Switch Controller
CSWI clas s
Dat a o b je ct Co m m o n Exp lan at io n T M /O/
n am e d at a class C
LNName The name s hall be composed of the c lass name, the LN- Pr efix and LN-
Ins tance-ID according to IEC 61850-7-2, Clause 22.
Dat a o b jects
Loc Key SPS Loc al or r emote key O
Edition 2
Loc Sta SPC Sw itching authority at s tation level O
Loc SPS Loc al Control Behavior O
OpCntRs INC Res etable operation counter O
Co n trols
Pos DPC Sw itch, general M
Pos A DPC Sw itch L1 O
Pos B DPC Sw itch L2 O
Pos C DPC Sw itch L3 O
St a tus i nformation
OpOpn A CT Oper ation “Open Sw itch” TO
Edition 2 SelOpn A CT Selec tion “Open Switch” O

OpCls A CT Oper ation “Close Sw itch” TO
Edition 2 SelCls A CT Selec tion “Close Sw itch” O
Position = CSWI1$ST$Pos$stVal
Voltage Transformer (TVTR)
TVTR class
name data class C
LNName The name shall be composed of the class name, the LN-Prefix and LN-
Data objects
Measured values
VolSv SAV Voltage (sampled value) C1
Status information
FuFail SPS TVTR fuse failure O
Settings
VRtg ASG Rated Voltage O
HzRtg ASG Rated frequency O
Rat ASG Winding ratio of external voltage transformer (transducer) if applicable O
Cor ASG Voltage phasor magnitude correction of external voltage transformer O
AngCor ASG Voltage phasor angle correction of external voltage transformer C2
CorCrv CSG Curve phasor magnitude and angle correction C2
Condition C1: The data object is mandatory if the data object is transmitted over a communication link and
therefore it is visible.
Condition C2: If there are two or more correction pairs necessary, CorCrv should be used.

Current Transformer (TCTR)
TCTR class
name data class C
Data objects
Measured values
AmpSv SAV Current (Sampled value) C1
Settings
ARtg ASG Rated Current O
HzRtg ASG Rated Frequency O
Rat ASG Winding ratio of an external current transformer (transducer) if applicable O
Cor ASG Current phasor magnitude correction of an external current transformer C2
AngCor ASG Current phasor angle correction of an external current transformer C2

Measurement Unit (MMXU)
M M XU clas s
Dat a o b jects
EEHealth INS Ex ter nal Equipment Health ( external sensor) O
M easu red values
TotW MV Total A ctive Pow er (Total P) O
TotV Ar MV Total Reac tive Pow er ( Total Q) O
TotV A MV Total A pparent Pow er (Total S) O
TotPF MV A v erage Pow er factor ( Total PF) O
Hz MV Fr equency O
PPV DEL Phas e to phase voltages (VL1VL2, …) O
Edition 2 PNV WY E Phas e to neutral v oltage O

PhV WY E Phas e to ground v oltages (VL1ER, …) O
A WY E Phas e c urrents ( IL1, IL2, IL3) O
W WY E Phas e ac tive power (P) O
VAr WY E Phas e r eactive power ( Q) O
VA WY E Phas e apparent power ( S) O
PF WY E Phas e pow er factor O
Z WY E Phas e Impedance O
A v APhs MV A r ithmetic average of the magnitude of curr ent of the 3 phases. O
A v erage( Ia,Ib,Ic)
A v PPV Phs MV A r ithmetic average of the magnitude of phase to phase voltage of the 3 O
phas es.
A v erage( PPV a, PPV b, PPV c)
PF WY E Phas e pow er factor O
Z WY E Phas e Impedance O
A v APhs MV A r ithmetic average of the magnitude of curr ent of the 3 phases. O
MMXU (cont’d) A v PPV Phs MV
A v erage( Ia,Ib,Ic)
A r ithmetic average of the magnitude of phase to phase voltage of the 3 O
Edition 2 phas es.
A v erage( PPV a, PPV b, PPV c)
A v PhVPhs MV A r ithmetic average of the magnitude of phase to r eference voltage of the O
3 phas es.
A v erage( PhVa, PhV b, PhVc)
A v WPhs MV A r ithmetic average of the magnitude of active power of the 3 phases. O
A v erage( Wa, Wb, Wc)
A v VAPhs MV A r ithmetic average of the magnitude of apparent power of the 3 phases. O
A v erage(VAa, VAb, VAc)
A v VArPhs MV A r ithmetic average of the magnitude of reactive power of the 3 phases. O
A v erage(VAra, VArb, VArc)
A v PFPhs MV A r ithmetic average of the magnitude of power factor of the 3 phases. O
A v erage( PFa, PFb, PFc )
A v Z Phs MV A r ithmetic average of the magnitude of impedance of the 3 phases. O
A v erage( Za, Zb, Z c
MV Max imum magnitude of cur rent of the 3 phases. O
Max A Phs
Max ( Ia,Ib,Ic)
MV Max imum magnitude of phase to phase voltage of the 3 phases. O
Max PPV Phs
Max ( PPV a, PPV b, PPV c )
MV Max imum magnitude of phase to r eference voltage of the 3 phases. O
Max PhV Phs
Max ( PhV a, PhVb, PhVc)
MV Max imum magnitude of active power of the 3 phases. O
Max WPhs
Max ( Wa, Wb, Wc)
MV Max imum magnitude of apparent power of the 3 phases. O
Max V APhs
Max ( VAa, VAb, VAc)
MV Max imum magnitude of reactive power of the 3 phases. O
Max V ArPhs
Max ( VAra, VArb, VArc)
MV Max imum magnitude of power factor of the 3 phases. O
Max PFPhs
Max ( PFa, PFb, PFc )

Dat a o b jects
MMXU (cont’d) EEHealth

M easu red values
INS Ex ter nal Equipment Health ( external sensor) O
Edition 2 Max Z Phs

MV Max imum magnitude of impedance of the 3 phases.
Max ( Z a, Zb, Z c)
O
MV Minimum magnitude of cur rent of the 3 phases. O

MinA Phs
Min( Ia,Ib,Ic )
MV Minimum magnitude of phase to phase voltage of the 3 phases. O
MinPPV Phs
Min( PPV a, PPV b, PPV c )
MV Minimum magnitude of phase to r eference voltage of the 3 phases. O
MinPhV Phs
Min( PhV a, PhVb, PhVc)
MV Minimum magnitude of active power of the 3 phases. O
MinWPhs
Min( Wa, Wb, Wc)
MV Minimum magnitude of apparent power of the 3 phases. O
MinV A Phs
Min( V Ara, VArb, VArc)
MV Minimum magnitude of reactive power of the 3 phases. O
MinV A rPhs
Min( V Ara, VArb, VArc)
MV Minimum magnitude of power factor of the 3 phases. O
MinPFPhs
Min( PFa, PFb, PFc )
MV Minimum magnitude of impedance of the 3 phases. O
MinZ Phs
Min( Z a, Zb, Z c)
Set t ings
Clc TotVA ENG Calc ulation method used for total apparent power (TotVA) ( VECTOR | O
A RITHMETIC )
PFSign ENG Sign c onvention for VAr and Pow er Factor (PF) (ActivePower | O
LEA D/LA G)

WYE Measurements
WYE c la s s
Dat a T yp e FC T r g Op V alu e /V alu e r an g e M /O/C
at t r ib u t e
n am e
Da t a NameInhe rited from Ge nDataObject C lass or f rom Ge nSubData Object C lass (see
IEC 61850-7-2)
SubDataObject
phsA C MV GC _1
phsB C MV GC _1
phsC C MV GC _1
ne ut C MV GC _1
ne t C MV GC _1
re s C MV GC _1
Da t aAttribute
a ngR ef ENUMER ATED CF dchg Va | Vb | Vc | A a | A b | A c | Va b | Vbc | O
Vca | Vot he r | A othe r | Sy nchrophasor
phs ToNeut BO O LEAN CF dchg DEF A ULT = F A LSE O
Se r vices
CM V c la ss
Complex at t r ib u t e
n am e
IEC 61850-7-2)
Measured Value Da t aAttribute
me a sure d a t t ribut e s
inst C Val Ve ct or MX O
cVa l Ve ct or MX dchg, M
dupd
ra nge ENUMER ATED MX dchg norma l|high|low|high-high|low-low O
ra nge Ang ENUMER ATED MX dchg norma l|high|low|high-high|low-low O
q Q ua lit y MX qchg M
t Time St a mp MX M
subst it ut ion a nd blocke d
subEna BO O LEAN SV PIC S_SUBST
subC Val Ve ct or SV PIC S_SUBST
subQ Q ua lit y SV PIC S_SUBST
subID VISIBLE STR ING64 SV PIC S_SUBST
blkEna BO O LEAN BL O
unit s Unit CF dchg se e A nnex A O
db INT32U CF dchg 0… 100 000 O
dbA ng INT32U CF dchg 0… 100 000 O
ze roDb INT32U CF dchg 0… 100 000 O
ra nge C R a ngeConfig CF dchg GC _C ON_ra nge
ra nge AngC R a ngeConfig CF dchg GC _C ON_ra nge
A ng
ma gSVC Sca le dValueConfig CF dchg A C _SC A V
a ngSVC Sca le dValueConfig CF dchg A C _SC A V
a ngR ef ENUMER ATED CF dchg V | A | ot he r ¦ Sy nchrophasor O
smpR a t e INT32U CF dchg O
Se r vices
223 © Copyright 2018 SISCO. All Rights Reserved A s de f ined in Ta ble 21
Vector
Ve c t o r t y pe de finit io n
A t t r ibut e na m e A t t r ibut e t y pe Va lue /Va lue r a nge M /O/C
ma g A na logueValue M
a ng A na logueValue –180 < n ≤ +180 A C _CLC_O
A na lo gue Va lue t y pe de finit io n
A t t r ibut e na m e A t t r ibut e t y pe Va lue /Va lue r a nge M /O/C

i INT32 int e ger va lue GC _1
f F LO A T32 f loa ting point value GC _1

Object Name for Phase A to Ground Voltage
MMXU1.MX.PhV.PhsA.cVal.mag.f
Data
Functional Constraint (measurements)
Logical Node
Same in Ed. 1 and Ed. 2

Metering (MMTR)

Binary Counter for Reading (BCR)
BCR c la ss
at t r ib u t e
n am e
IEC 61850-7-2)
Da t aAttribute
st a t us
a ct Va l INT64 ST dchg M
f rVa l INT64 ST dupd GC _2_1
(was INT128)
f rTm Time St a mp ST GC _2_1
(was INT128)
t Time St a mp ST M
unit s Unit CF dchg se e A nnex A O
pulsQ ty F LO A T32 CF dchg M
f rEna BO O LEAN CF dchg GC _2_1
st rTm Time St a mp CF dchg GC _2_1
f rPd INT32 CF dchg GC _2_1
f rR s BO O LEAN CF dchg GC _2_1
d VISIBLE STR ING255 DC O
Se r vices
Object Name for WH pulse count
MMTR1.ST.TotWh.actVal
Data
Functional Constraint (Status)
Logical Node
Metering Statistics (MSTA Ed.1 Only) replaced with statistics in MMXU in Ed. 2

Instantaneous Over Current (PIOC)
PIOC clas s
Dat a o b jects
Edition 2 Str A CD Star t O
Switched
Order Op A CT Oper ate TM
Co n t r o l s
Set t ings
Str V al A SG Star t Value O

Analog Setting (ASG)
ASG class
name
DataAttribute
setting
setMag AnalogueValue SP dchg AC_NSG_M
setMag AnalogueValue SG, SE AC_SG_M
minVal AnalogueValue CF dchg O
maxVal AnalogueValue CF dchg O
stepSize AnalogueValue CF dchg 0 … (maxVal – minVal) O
 AC_NSG_M Mandatory if Setting Groups are NOT supported
 AC_SG_M Mandatory if Setting Groups are supported

Settings or Setpoints for PIOC
• If Settings Groups are NOT supported:
• PIOC1.SP.StrVal.setMag.f
• If Settings Groups are supported:
– Active Setting:
• PIOC1.SG.StrVal.setMag.f
– Editable Setting:
• PIOC1.SE.StrVal.setMag.f

Protection Activation – ACT and ACD
A CT c lass
At t r ib u t e
n am e
IEC 61850-7-2)
Da t aAttribute
st a t us
ge ne ral BO O LEAN ST dchg M
phsA BO O LEAN ST dchg O
phsB BO O LEAN ST dchg O
A CD c la ss
phsC BO O LEAN ST dchg Dat a T yp e FCO T r g Op V alu e /V alu e r an g e M /O/C
ne ut BO O LEAN ST dchg At t r ib u t e O
q Q ua lit y ST qchg n am e M
t Time St a mp ST Da t a Name Inhe rited from Ge nDataObject
M C lass or f rom Ge nSubData Object C lass (see
originSrc O riginat or ST IEC 61850-7-2) O
Da t aAttribute
ope rTmPhsA Time St a mp ST O
st a t us
ope rTmPhsB Time St a mp ST O
ge ne ral BO O LEAN ST dchg M
ope rTmPhsC Time St a mp ST O
dirGe neral ENUMER ATED ST dchg unknown | f orward | ba ckward | both M
conf igura t ion, de s cript ion a nd e x t e nsion
phsA BO O LEAN ST dchg GC _2_1
dirPhsA ENUMER ATED ST dchg unknown | f orward | ba ckward GC _2_1
phsB BO O LEAN ST dchg GC _2_2
dirPhsB ENUMER ATED ST dchg unknown | f orward | ba ckward GC _2_2
phsC BO O LEAN ST dchg GC _2_3
dirPhsC ENUMER ATED ST dchg unknown | f orward | ba ckward GC _2_3
Se r vices
ne ut BO O LEAN ST dchg GC _2_4
dirNe ut ENUMER ATED ST dchg unknown | f orward | ba ckward GC _2_4
t Time St a mp ST M
233 © Copyright 2018 SISCO. All Rights Reserved da t a Ns VISIBLE STR ING255 EX A C _DLN_M
Se r vices
Object Name PIOC Trip Status
PIOC1.ST.Op.general
Data
Functional Constraint (Status)
Logical Node

COMTRADE Disturbance Recorder (RDRE)
RDRE clas s
Dat a o b jects
Co n trols
Edition 2 Rc dTr g SPC Tr igger recorder O
Switched MemRs SPC Res et r ecorder memory ( set the pointer of memory s tart to the beginning) T O
Order MemClr SPC Clear Memor y ( er ase all c ontent of the memory) TO
Rc dMade SPS Rec or ding made M
FltNum INS Fault Number M The
Gr iFltNum INS Gr id Fault Number O
Rc dStr SPS Rec or ding s tarted O
recorder
MemUs ed INS Memor y us ed in % O function is
Set t ings
Tr gMod ENG Tr igger mode (internal trigger, external or both) O
composed
Lev Mod ENG Lev el Tr igger Mode O of one or
Pr eTmms ING Pr e- tr igger time O
Ps tTmms ING Pos t- trigger time O
more analog
MemFull ING Memor y f ull level O or binary
Max NumRc d ING Max imum number of r ecords O
ReTr gMod ENG Retr igger Mode O
channel LNs
Per Tr gTms ING Per iodic trigger time in s O
Ex c lTmms ING Ex c lus ion time O
Rc dMod ENG Rec or der operation mode ( Saturation, Ov erwrite) O
StoRte ING Stor age r ate, i.e. sampling r ate of the disturbance r ecorder O
NOTE 1 The tr igger modes ( TrgMod) of RDRE, RA DR and RBDR ar e not independent. If the tr igger mode of
235 RDRE is ex ter nal, the trigger modes of RADR and RBDR may be external ( no extension of trigger possibilities) or
inter nal ( extension of the external tr igger mode). If the tr igger mode of RDRE is inter nal, the tr igger modes of
RA DR and RBDR s hould als o be inter nal bec aus e other w is e, no tr igger pos s ibility is pr ov ided.
NOTE 2 The s our ce of the external trigger is a local issue. It may be a contact or a signal f r om an other logic al
node.
Disturbance Recorder Analog Channel (RADR)
Edition 2
One RADR per Analog Channel

Disturbance Recorder Binary Channel – RBDR
Edition 2

Breaker Failure – RBRF
RBRF class
name data class C
Data objects
Status information
Str ACD Start, timer running O
OpEx ACT Breaker failure trip (“external trip”) TC
OpIn ACT Operate, retrip (“internal trip”) TC
Controls
OpCntRs INC Resetable operation counter O
Settings
FailMod ENG Breaker Failure Detection Mode (current, breaker status, both, other) O
FailTmms ING Breaker Failure Time Delay for bus bar trip O
SPlTrTmms ING Single Pole Retrip Time Delay O
TPTrTmms ING Three Pole Retrip Time Delay O
DetValA ASG Current Detector Value O
ReTrMod ENG Retrip Mode O
Condition C: At least one of either data objects shall be used depending on the applied tripping schema.

Alarm Handling – CALH
CALH class
name data class C
Data objects
Status information
GrAlm SPS Group alarm C
GrWrn SPS Group warning C
Edition 2 GrInd SPS Group Indication C
AlmLstOv SPS Alarm list overflow O
Condition C: At least one data object shall be modelled.
Other specific alarms are located in specific LNs.
Associating these generic group alarms to actual I/O

or status is a local matter left to the discretion of the
device developer.

CCGR class
Cooling Group – CCGR Data object
LNName
name
Common
data class
Explanation
The name shall be composed of the class name, the LN -Prefix and LN-
T M/O/
C
Data objects
EEHealth INS External Equipment Health O
EEName DPL External Equipment Name Plate O
Measured values
EnvTmp MV Temperature of environment O
OilTmpIn MV Oil temperature cooler in O
OilTmpOut MV Oil temperature cooler out O
OilMotA MV Oil circulation motor drive current O
FanFlw MV Air flow in fan O
CETmpIn MV Temperature of secundary cooling medium in O
CETmpOut MV Temperature of secundary cooling medium out O
CEPres MV Pressure of secundary cooling medium O
CEFlw MV Flow of secundary cooling medium O
FanA MV Motor drive current fan O
Controls
CEBlk SPC Control of automatic / manual operation (blocking) O
CECtl SPC Control of complete cooling group (pumps and fans) O
PmpCtlGen ENC Control of all pumps O
PmpCtl ENC Control of a single pump O
FanCtlGen ENC Control of all fans O
FanCtl ENC Control of a single fan O
Auto SPC Automatic or manual O
Status information
FanOvCur SPS Fan overcurrent trip O
PmpOvCur SPS Pump overcurrent trip O
PmpAlm SPS Loss of pump O
Settings
OilTmpSet ASG Set point for oil temperature O

Interlock Control (CILO)
Relationship between CILO and other switch functions and the

interlocking algorithm is a local matter left to the discretion of the
device developer.

Generic I/O – GGIO (Edition 1)
A place holder for generic I/O
Can be extended to contain any data from an SCL file (IEC 6185-6)
Typically used by relays for inter-relay GOOSE datasets (UNFORTUNATELY)

Generic I/O – GGIO (Edition 2)
GGIO class
Data objects
LocKey SPS Local or remote key O
Loc SPS Local Control Behavior O
OpCntRs INC Resetable operation counter O
Measured Values
AnIn1 MV Analogue input O
Attributes ending in “1” AnOut1 APC Controllable analogue output O

Controls
can be instantiated in SPCSO1 SPC Single point controllable status output O
DPCSO1 DPC Double point controllable status output O
multiples (Ind1, ISCSO1 INC Integer status controllable status output O
Metered Values
Ind2….IndX) CntRs1 BCR Counter, resettable O
Status information
IntIn1 INS Integer status input O
Alm1 SPS General single alarm O
Wrn1 SPS General single warning O
Ind1 SPS General indication (binary input) O

Tap Changer (YLTC)
YLTC class
name data class C
Data objects
OpCnt INS Operation counter O
Measured values
Torq MV Drive Torque O
MotDrvA MV Motor Drive Current O
Controls
TapPos ISC Change Tap Position to dedicated position C
TapChg BSC Change Tap Position (stop, higher, lower) C
Status information
EndPosR SPS End position raise reached M
EndPosL SPS End position lower reached M
OilFil SPS Oil Filtration O
OoStep SPS Out of step alarm: supervision of selector switch synchronism O
LTCCycAlm SPS LTC switching cycle incomplete: tap change operation without diverter O
Edition 2 switch operation
BlkLoVisc SPS Blocked by low oil viscosity O

Batteries – ZBAT

Bushings – ZBSH
ZBSH class
name data class C
Data objects
Measured values
React MV Relative capacitance of bushing related to the data object RefReact M
Edition 2 AbsReact MV Online capacitance, absolute value O
LosFact MV Loss Factor (tan delta) O
Vol MV Voltage of bushing measuring tap O
DisplA MV Displacement current: apparent current at measuring tap O
Edition 2
LeakA MV Leakage current: active current at measuring tap O
Settings
RefReact ASG Reference capacitance for bushing at commissioning O
RefPF ASG Reference power factor for bushing at commissioning O
RefV ASG Reference voltage for bushing at commissioning O

Current Transformer – TCTR
TCTR class
name data class C
Data objects
Measured values
AmpSv SAV Current (Sampled value) C1
Settings
ARtg ASG Rated Current O
HzRtg ASG Rated Frequency O
Rat ASG Winding ratio of an external current transformer (transducer) if applicable O
Cor ASG Current phasor magnitude correction of an external current transformer C2
AngCor ASG Current phasor angle correction of an external current transformer C2

Distance Sensor – TDST
TDST class
Data object Common T M/
Explanation
name data class O/C
The name shall be composed of the class name, the LN -Prefix and LN-
LNName
Data objects
Measured values
DisSv SAV Distance [m] C
Settings
SmpRte ING Sampling rate setting O
Condition C: The data object is mandatory if the data object is transmitted over a communication link and

Fan – KFAN
KFAN class
Data objects
EEName DPL External equipment nameplate O
Loc SPS Local control behavior O
LocKey SPS Local or remote key O
Measured Values
Spd MV Rotational speed of the fan O
Controls
OpCtl SPC Operate fan C
SpdSpt APC Speed set-point (in case of speed regulated motor) C
Settings
MinOpTmm ING Minimum operation time in minutes O
MaxOpTmm ING Maximum operation time in minutes O

Counter – FCNT
FCNT class
Instance-ID according to IEC 61850-7-2, Clause 22Clause 22
Data objects
Metered Values
CntRs BCR Counter M
Status information
Up SPS Last count direction upward O
Dn SPS Last count direction downward O

PID Control – FPID FPID class
Instance-ID according to IEC 61850-7-2, Clause 22Clause 22
Data objects
Measured Values
Out MV PID output M
PAct MV Proportional action C
IAct MV Integral action C
DAct MV Derivative action C
ErrTerm MV Control loop termination error value O
Settings
PIDAlg ENG P|I|D|PI|PD|ID|PID| M
KP ASG Proportional gain C
KI ASG Integral Gain C
ITmms ING Integral time (ms) C
KD ASG Derivative gain C
DTmms ING Derivative time (ms) C
DFilTmms ING Derivative time filter (ms) C
Bias ASG Bias added to process variable O
ILim ASG Anti-windup integral limit O
Droop ASG Percent change in effective setpoint at maximum action O

Other Logical Node Standards
• IEC 61850-7-410 contains LN descriptions for hydro power (water)
• IEC 61850-7-420 contains LN descriptions for distributed energy resource (DER) applications (a.k.a.
distributed generation)
• IEC 61400-25 contains LN descriptions for wind power applications.
• Many Others too.
• Some IEC 61850 devices have some proprietary LN definitions.


Input References
Interactions between Logical Nodes

Logical Node Interactions
• Many logical nodes are intended to interact with each other:
– Protection Tracking (PTRC) uses other protection fault LNs as
inputs
– Instrument transformers (TCTR & TVTR) are inputs to
measurements (MMXU)
– Measurements (MMXU) are inputs to Statistical LNs
• IEC 61850 provides the means to “connect” LNs together

MMXU and TCTR/TVTR Linking
TCTR1
Current
MMXU1
Measurements
TVTR1
Voltage

Protection Nodes Linking
TCTR1 PTOC1 PTRC1 RBRF1

Protection Breaker
Current Measurements
Tracking Failure Open/Close
TVTR1 MMXU1 XCBR1 CSWI1

Circuit Switch
Voltage Measurements
Breaker Controller

Input References in the Common Logical Node Class
Common LN class
name data class C
Data objects
Mandatory and conditional Logical Node Information (shall be inherited by ALL LN but LPHD)
Mod ENC Mode C1
Beh ENS Behavior M
Health ENS Health C1
NamPlt LPL Name plate C1
Optional Logical Node Information
CmdBlk SPC Blocking of control sequences and action triggers of controllable data C2
objects
set) or immediately
258 © Copyright 2018 SISCO.ClcMth
All Rights Reserved ENG Calculation Method of statistical data objects. Allowed values C3
Object Reference Syntax
The ObjectReference syntax shall be:
LDName/LNName[.Name[. ...]]
– The “/” shall separate the instance name of a logical device (LDName) from the
name of an instance of a logical node (LNName).
– The “.” shall separate the further names in the hierarchy.
– The “[. ]” indicates an option.
– The “[. ...]” indicates further names of recursively nested definitions.
– The “(…)” shall indicate an array element
– The type is VISIBLESTRING129 (up to 129 characters)

Multiple References
• “Specialization of data by use of number extensions” per IEC
61850-7-1:
– If an attribute name ends with “1” then it can be extended
with multiple instances
– There must be at least “1” if any attributes are present
– They don’t need to be sequential (1, 2, 4, 6, etc.)
• In Ed2.1 it was changed to use the “Omulti” conditional but

the result is exactly the same.

Ed2.1 Common Logical Node class
DomainLN
Data object name Common data class T Explanation PresCond nds/ds
Descriptions
MONamPlt /
NamPlt LPL Name plate of the logical node.
MONamPlt
Status information
Read-only value, describing the behaviour of a domain logical node. It

depends on the current operating mode of the logical node
('DomainLN.Mod'), and the current operating mode of the logical device
Beh ENS (BehaviourModeKind) M / M
that contains it ('LLN0.Mod'). Processing of the quality status ('q') of the
received data is the prerequisite for correct interpretation of
'DomainLN.Beh'.
Reflects the state of the logical node related hardware and software. More
Health ENS (HealthKind) detailed information related to the source of the problem may be provided O / O
by specific attribute of the logical node.
If true, the LN is a mirror and represents a LN from another LD that does

MOcond(1) /
Mir SPS not reflect this physical device. If false, it is recommended to omit the
MOcond(1)
data object Mir.
Controls
(controllable) Operating mode of the domain logical node that may be

Mod ENC (BehaviourModeKind) changed by operator. Processing of the quality status ('q') of the received O / O
data is the prerequisite for correct interpretation of the operating mode.
Settings
InRef ORG Object reference of data object bound to the input n. Omulti / Omulti

MMXU and TCTR/TVTR Linking
Logical Device LDevice2/MMXU1.InRef1.setSrcRef = “LDevice1/TCTR1.AmpSv”
“LDevice1” LDevice2/MMXU1.InRef2.setSrcRef = “LDevice1/TVTR1.VolSv”
AmpSv Logical Device

TCTR1 “LDevice2”
Current
InRef1
MMXU1
Measurements
A, V, PF, W
InRef2
VolSv
TVTR1
Voltage

Statistical LN Model

Statistical LN Model
• A Statitical LN is a mirror of another LN’s data but it contains statistically
calculated data
• The ClcSrc data object points to the original LN

•
• Statistical calculation may be chained. For example, the first LN can
produce RMS value, then a second statistical LN can calculate an average
of the considered RMS value on a certain period, then another statistical
LN can calculate the maximum of the calculated averages since the last
reset of this maximum value.

Common LN class
StatisticsLN
Data object Common data Explanation T M/O/C
name class

set) or immediately
PRES_OR_UNKNOW N(default) | TRUE_RMS | PEAK_FUNDAMENTAL |

ClcMod ENG Calculation mode. Allowed values: C4
TOTAL | PERIOD | SLIDING

ClcIntvTyp ENG Calculation interval typ. Allowed values: C4
MS | PER_CYCLE | CYCLE | DAY | W EEK | MONTH | YEAR |

EXTERNAL
ClcIntvPer ING In case ClcIntvTyp equals to MS, PER-CYCLE, CYCLE, DAY, W EEK, C4
MONTH, YEAR, number of units to consider to calculate the calculation
interval duration
NumSubIntv ING The number of sub-intervals a calculation period interval duration O

contains
ClcRfTyp ENG Refreshment interval typ. Allowed values: MS, PER -CYCLE, CYCLE, O
DAY, W EEK, MONTH, YEAR, EXTERNAL
ClcRfPer ING In case ClcIntvTyp equals to MS, PER-CYCLE, CYCLE, DAY, W EEK, O
MONTH, YEAR, number of units to consider to calculate the
refreshment interval duration
ClcSrc ORG Object Reference to Source logical node C5
ClcNxTmms ING Remaining time up to the end of the current calculation interval – O
expressed in millisecond
InSyn ORG Object reference to the source of the external synchronization signal for
the calculation interval

Statistical Calculation Linking
Logical Device Logical Device
MMXU2
“LDevice1” “LDevice2” Measurements
A, V, PF, W
ClcSrc = MMXU1
ClcMth = [AVG]
AmpSv InRef1 ClcMod = [PERIOD]
TCTR1 ClcIntvTyp = [MS]
Current ClcIntvPer = [600000]
MMXU1
Measurements
A, V, PF, W
ClcMth = [TRUE_RMS] MMXU3
Measurements
InRef2 A, V, PF, W
VolSv ClcSrc = MMXU2
TVTR1 ClcMth = [MAX]
Voltage
LDevice2/MMXU2.ClcSrc.setSrcRef = “LDevice2/MMXU1”
LDevice2/MMXU3.ClcSrc.setSrcRef = “LDevice1/MMXU2”

Extending Logical Nodes and Namespaces
Identifying Non-Standard IEC 6 1850 Objects

What is a Namespace?
• Naming and modeling convention
• The “owner” of the Namespace controls it
• For instance, the owner of the naming and object conventions specified in Ed.2 of IEC 61850-7-4
is “IEC 61850-7-4:2010”
• The owner of the Common Data Class (CDC) Namespace is “IEC 61850-7-3:2010”
• When an LN is extended with new attributes a Namespace for those extensions must be
specified
• This is done via the Logical Node Nameplate (LPL) and CDC attributes that occurs in all LNs and
CDCs
• The value of the Namespace tells you where to find the meaning of the attributes

Logical Node Nameplate (LPL)
LPL class
attribute
name
IEC 61850-7-2)
DataAttribute
ldNs VISIBLE STRING255 EX Shall be included in LLN0 only; for AC_LN0_EX
example "IEC 61850-7-4:2010"; details of the
name space concept are defined in IEC 61850 -7-1.

Namespace attributes
Attribute M/O/C Description Location
Logical Device Namespace exclusively found in

LLN0. Contains a reference to the prime
ldNs AC_LN0_EX LDName/LLN0.NamPlt.ldNs
technical specification used for the whole logical
device.
The name space of this LN is different than that

specified by the Logical Device Name Space
lnNs AC_DLD_M LDName/LNName.NamPlt.lnNs
specified in LLN0 (LLN0.ldNs). Used for a custom
or modified LN.
CDC namespaces cannot be changed and this

cdcNs AC_DLNDA_M If present, likely an Ed.1 device
attribute has been removed in Ed2.1
If present it means the CDC for a given Data

cdcName AC_DLNDA_M LDName/LNName.DataName.cdcName
Object (DO) within this LN is non-standard
The attribute shall be present, if the data name

space of this data object (DO) deviates from the
data name space referenced by either lnNs of
dataNs AC_DLN_M the logical node in which the data is contained or LDName/LNName.DataName[.DataName[. ...]].dataNs
the ldNs of the logical device in which the data is
contained. Used if a DO has been added to an
otherwise standards compliant LN.

Namespace format
• Format: “NamespaceID:VersionRevision”
• Ed.1 = “IEC 61850-7-4:2003”
• Ed.2 = “IEC 61850-7-4:2010”
• Ed2.1 = “IEC 61850-7-4:2010B”
• Transitional Technical Report (TR) = “(Tr)IEC 61850-90-12:2018”
• A new CDC would have this in all DOs for that new CDC
• dataNs = “(Tr)IEC 61850-90-XX:2016”
cdcName = “NEW”

Simulation and Testing

Simulation vs. Testing
• Simulation mode refers to the ability for a device to be switched from
processing “normal” signals to processing “simulated” signals that mimic real
data
• Simulated data has the same semantics
• Simulated data does not have a different quality but the messages carry a simulation flag
• Simulation mode applies to the entire logical device (LD)
• Test mode refers to the ability to put either the entire logical device or an
individual LN into a test mode
• Test mode affects the quality of the data being produced
• Individual LNs can be put into test mode that switches the input to an LN to a completely
different input

Simulation Mode
• Simulated and non-simulated
messages (GOOSE and SV) can be
presented to the device
• When the LD is put into

simulation mode it will continue
to accept non-sim data until
simulated data is detected
• Once detected it will continue to

process only simulated data for
that signal until simulation mode
is exited and non-sim data is
detected

Test Mode
• Place the entire Logical Device (LD) into test mode
• Place a single Logical Node (LN) into test mode
• The Behavior (Beh) of an individual LN depends on the Mode (Mod)

of LLN0 and the Mode (Mod) of that LN
• Test mode can use simulated or non-simulated data

Mode and Behavior
• on – normal operation
• on-blocked
• No wired output will be issued to the process
• test
• Data transmitted q.test=true
• Only control commands with Test=true are accepted
• test/blocked
• No wired output will be issued to the process
• Data transmitted q.test=true
• Onl control commands with Test=true are accepted
• off
• Application functions do not work
• Communications working
• No process output will be done
• Data transmitted with q.validity=invalid
• All control commands rejected except the Mod accepts
control commands with Test=false
• Settings and configuration can be changed
Mod, Beh and Health always sent with q.test=false

Test Mode Operation
LN XXYZ1 where Beh.stVal = test
Incoming
signal: Invalid
GOOSE or Invalid
Report with
q=test Incoming
on data
treated as
valid but
no output
to the
Incoming off process
signal:
Control Not
service with
processed
Test=true


The IEC 61850 Engineering Process
Substation Configuration Language (SCL)

The IEC 61850-4 SAS Engineering Process
It starts with a power system design

The automation and protection functions are defined

IEDs are selected and configuration and programming is defined

The IEDs are tied together via the network to integrate the power system automation and protection functions

Monitoring and visualization enables control of the power system

The IEC 61850 process addresses all aspects of the SAS that need to be successfully planned, designed, and deployed.

SCL – Substation Configuration Language
IEC61850-6
• Description language for describing the power system topology,

communication and configuration for electrical substations.
• XML based language that allows a formal description of

• Substation automation system and the switchyard and the relation between the
power system and the various IEDs
• IED configuration and settings
• Support for private extensions

SCL Tools
• System Configuration Tool (SCT)
• Used to design systems and substations
• Schematic designer (Single Line Diagrams – SLD)
• Assigns devices to specific power system functions
• Configures interactions between devices
• Configuration and settings for devices
• IED Configuration Tool (ICT)

• Finishes the configuration of a device based on vendor requirements (e.g. logic
programming and proprietary functions)

SCL File Types
• SSD: System Specification Description.
– XML description of a system. A specification for what is needed without specific IEDs assigned to power system functions.
• SCD: Substation Configuration Description.

– XML description of a single substation. A description of the substation and configured IEDs in it that is generated by a Substation Configuration
Tool (SCT).
• IID: Instantiated IED Description

– XML description of a device that is used in the substation design of an SCD but may not be completely configured.
• CID: Configured IED Description.

– XML configuration for a specific IED that has been completely configured. An IED Configuration Tool (ICT) uses an IID or SCD as input and
generates the CID.
• SED: System Exchange Description

– Subset of a SCD file that specifies responsibilities between entities implementing different parts of a project
• ICD: IED Capability Description.

– XML description of what is supported by an IED. A template for a given type of product that is provided by the IED supplier. Used by a SCT to
select devices for the design of the substation.

Substation Engineering
SCL Workflow ICD for ICD for
ICD for
IED Type 2 … IED Type N-1
ICD for
IED Type 1 IED Type N
Requirements for
the system
Templates for
the various IEDs
SCT SSD SCT used in the
system
Specification/Planning
IID Design of the
Changes made by SCD substation
including IED
ICT are sent back
configuration
to SCT via IID files
CID ICT ICTs can use either IID or

can extract the IID
information from the SCD
Includes additional IED configuration needed
for the device that is not part of SCD
IED Engineering
SSD File
• SSD file specifies the SSD File – Entire System
requirements for a system SCD File #1 SCD File #n
design Single Substation Single Substation
Substation #1 Substation #n
• Consists of 1 or more
substations …
• Includes the topology,
protection and automation
functions unassigned to a
specific device

SCD Files
Substation Configuration Description
• SCD file is extracted from an SSD

SCD File
• Assigns power system functions to specific IEDs
• Assign a particular relay to provide the specific breaker control
(CSWI and XCBR) and protection LNs needed to implement system
IID File
• Assigns names to IEDs, bays, etc.
For IED #1
• Imports the ICD files
…
• Configures the interaction between devices
• Defines data sets
• Defines report and GOOSE control blocks
• Defines Report & GOOSE subscriptions
• “Wires up” the various LNs to each other
IID File
• Define network configuration For IED #n
• Describes settings and other configuration options
• When complete exports the IID files needed for IED

engineering

ICD versus IID Files
ICD File = What an IED is
• IID File = Subset of ICD File Actually capable of
Used + Substation Specific
Configuration Information IID =
Configuration Substation
for a specific specific
• Subset: IED configuration
information
– Not all logical nodes, control blocks, I/O, added by
etc. supported by the device are used in a SCT
given system
• Substation Configuration Info:

– Report control block presets
– Static values for location, settings and ICD – IED Capability Description
other descriptions IID – Instantiated IED Description

IID versus CID Files ICD File = What an IED is
capable of
• CID File = IID + Additional configuration
information added by ICT (IED CID = Configuration used by a specific IED
Configuration Tool)
IID =
• IED Configuration Info is generally Configuration Substation Device
manufacturer specific and not needed for
for a specific specific specific
the substation design unrelated to that configuration configuration
specific IED for which it is generated IED
information information
added by added by
SCT ICT
• The CID is what gets loaded into the
device
• The ICT must also generate an IID for

providing changes back to the SCT when ICD – IED Capability Description
needed IID – Instantiated IED Description
CID – Configured IED Description

Parts of IEC 61850 Names
Defined in IEC Defined in IEC
61850-7-3 61850-7-4
configurable
LDName LNName DataName DataAttributeName
LN Prefix LN class LN Instance no
Part 1 Part 2 Part 3 Part 4

Product Based Naming
LDName LNName
Predefined by IED
IED Section:
Attribute Inst of element LN
IED Section: IED Section:

Attribute Name of element Attribute Inst of element
IED LDevice
Header:
NameStructure=“IEDName”

Prefix Naming
LDName LNName
IED Section:
Attribute Inst of element LN
Substation section: Substation section:

Attribute Name of element substation and Attribute Name of element
of element VoltageLevel and Equipment
of element Bay and of element SubEquipment

SCL Driven Naming
Voltage level E1 In the substation structure
this CBR is identified as
=E1Q1QA1
Bay Q1
QA1
In the substation structure
this LN is identified as
IED SB1
=E1Q1QA1CSWI2
LN1 LN2 LN1 LN2 In the IED (product)
structure
LD1 LD2 this LN is identified as
Access point S1 -E1Q1SB1LD2CSWI2
Station bus
W1
In the communication structure

this connection is identified as In theIED structurethis LD
is identified as
W1E1Q1SB1S1
-E1Q1SB1LD2

Example SCL Based One-Line Diagram
Logical Node Designators

About SCL Files
• SCL files contain all object model information explicitly declared except
for: control blocks
• Allows new or updated LN definitions to be incorporated using existing tools
• SCL files can contain device configuration of:
• Network addressing
• Initial values and configuration
• Settings and setpoints
• XML schema validation is not sufficient:
• The XML may conform to the standard schema while not conforming to the IEC 61850
standards
– Including a report subscription for a client that does not exist

IED Capability Description (ICD) File
• A template file that specifies what a device is capable
• IED Name = TEMPLATE

SCD File
• The design of a substation

SCL Manager Demonstration
• SCL Manager is an SCT from ASE-Kalkitech


Abstract Communications
Service Interface
ACSI

ACSI
Abstract Communications Service Interface
• Defines a base set of data types for describing objects

• Definitions for general enumerations, functional constraints, conditional
elements, etc.
• Defines a set of objects (Server, Logical Device, Logical Nodes, Data
Objects, etc.)
• Defines a set of Abstract Services to manipulate and access those objects

ACSI Object and Services
• We will present the basic ACSI Objects and the MMS Services to which
they are mapped in IEC 61850-8-1 (Specific Communication Service
Mapping (SCSM) for MMS over TCP/IP-Ethernet)
• This conflates the virtual ACSI model with the concrete SCSM of MMS but
facilitates understanding of what you will see in real devices
• We will start with an overview of stack profiles, then MMS and then ACSI

How Stack Profiles are Built

Some Terms
• Network Access Methods:
– Master Slave – a master controls slave access to the network (e.g.
DNP3 or IEC 60870-5-10X)
– Peer-to-peer – any entity may send data to any other peer entity on
the network without having to coordinate with a master (TCP/IP-
Ethernet).
• Client-Server – defines roles between 2 peers on a network.

7-layer OSI Network Architecture
Application Services to Applications
Presentation Format and Context Negotiation/Translation
Session Dialog Management
Transport Reliable delivery of messages
Network Connectivity/routing between networks
Data Link Control and access to media
Physical Wires, connectors, signals, etc.
A model for the functions needed for networked communications

“Peer-to-Peer” 7-layer OSI Network Architecture
Application Application Protocol Data Unit Application
Presentation PPDU APDU Presentation
Session SPDU PPDU Session
Transport TPDU SPDU Transport
Network NPDU TPDU Network
Data Link DPDU NPDU Data Link
Physical Physical
Physical Connection
• Each Layer embeds the protocol data unit (PDU) from the n+1 layer as “user data”
• Each layer processes its own PDU information and passes the n+1 data up the stack
• Result is that each layer communicates only with its remote peer layer

IEC 61850 and the “9-layer” OSI Architecture
Environmental Layer Electrical Power System Automation
User Layer IEC 61850-7-2, 7-3, 7-4, 8-1 object and service models
Application Manufacturing Message Specification (MMS) per ISO 9506 and
Association Control Service Elements (ACSE) per ISO 8560
Presentation Presentation per ISO 8823
Session Session per ISO 8327

Network ISO Transport Class 0 over TCP Port 102 per RFC 1006
Transport
Profile
Network Internet Protocol (IP) per IETF recommendations
Data Link Ethernet per IEEE 802 specifications
Physical Ethernet per IEEE 802 specifications

Interoperability of Power Systems
Power Power
Systems Systems
IEC 61850 Layer IEC 61850 Layer

Application Application
Presentation Presentation
Session Session
Transport Transport
Network Network
Data Link Data Link
Physical Physical
Interoperability at the environmental layer (Power Systems) is

only possible with user layer standardization.
Client/Server Architecture
Service Primitives
Server: Client Network Server
• A device or application that maintains data

objects and performs operations on behalf 1 2
Client Server
of clients. Sends Request Indication Receives
Request Indication
• Service primitives: Indication and
Response. 3
Server
Client: Takes Action
• A networked application or device that asks 5 4

Client Server
for data or an action from the server. Receives Confirm Response Sends
Confirmation Response
• Service primitives: Request and (+) or (-) (+) or (-)
Confirmation.
Request – Indication are identical

Response – Confirmation are identical Differ only in direction

Questions – Discussion

Brief Overview of MMS
ISO 9506 – Manufacturing Message Specification

MMS
• Manufacturing Message Specification
– ISO 9506
– Developed in 1988 by ISO TC184
– Originally developed for industrial automation
– V2002 of MMS is used for IEC 61850
• Larger Object Names
• Eliminated restrictions on Journals (logs)
• UTC time format
• Supervisory control and real-time data access

MMS Standards
• ISO 9506-1 (part 1) Service Specification:
• Defines a set of objects that can exist within a device
• Defines a set of communication services to access and manipulate those
objects
• Defines the behavior of the device to those communication services
• ISO 9506-2 (part 2) Protocol Specification

• Specifying the MMS messages using Abstract Syntax Notation Number 1
(ASN.1) per ISO 8824/8825
• How to encode the messages into bits and bytes on the wire using ASN.1
Basic Encoding Rules (BER) for IEC 61850-8-1
• Other encoding rules like XML Encoding Rules (XER) are also supported for
IEC 61850-8-2

Why MMS for IEC61850-8-1
• Real-time control needs more robust and higher
performance communications than offered by
http and XML.
• MMS was ahead of its time in 1988. MMS remains

one of the few standardized protocol
specifications capable of supporting the IEC 61850
requirements for service, complex named data,
and performance.
MMS Objects
• Virtual Manufacturing Device (VMD) – A server
that contains objects
• Variable – Named complex variables that are self
describing.
• Named Variable List (NVL) – A collection of
variables
• Domain – A resource that may contain other
objects.
• Journal – A time based record of variables.

Basic MMS Services
• Initiate/Conclude/Abort
– Make/break connections between client and server
• Read/Write
– Variables and NamedVariableLists (DataSet)
• InformationReport
– Send an unsolicited Read response to a client
• ReadJournal
– Query a historical log of variable data
• GetNameList/GetObjectAttributes
– Get the definition of an object

MMS Abstract Virtual Manufacturing Device (VMD) Model
• Objects + Services + Behavior =

Virtual Manufacturing Device Model (VMD)
• A model of how devices look and behave

to network applications.
• Device vendors map their real devices to

the VMD Model and then to IEC 61850 model

MMS Objects
• Domains • Program Invocations

• Variables • Types (Variables)
• Semaphores • Operator Interface
• Event Action • Event Condition
• Event Enrollment
• Journals
• NamedVariableLists
• Files

In General MMS Services
• Create Objects
• Delete Objects
• Get Object Values
• Change Object Values
• Determine Object Attributes

Domain Objects
• Represent a resource within the VMD
• Examples of domains
– Program memory
– Data memory
– IEC 61850 Logical Devices
– Domains may be permanent, pre-existing, and pre-named.

Example VMD: Batch Processor
Ingredient A Ingredient B Ingredient C
Container Station Container Station

#1 #2

• Each Station Requires:
– Different I/O Addresses
– Different Recipes – Different Data
– The same control algorithms

VMD
Program Invocation #1 Program Invocation #2
Recipe #1 Recipe #2
Domain Domain
Control Program Domain

(Sharable)
I/O #1 I/O #2
Domain Domain

Modeling Issues
• The choice on how to represent a real object in the VMD model is
critical.
• The wrong choice makes communication difficult:

– Variables – access to individual typed data
– Domains – blocks of non-typed data (no individual access).
• This is also true for IEC 61850 – Choosing the right model is
important

Object Scope
Variables specific to
VMD FEED_A_USED
FEED_B_USED
FEED_C_USED
Variables Specific to
a domain
FEED_A_USED FEED_A_USED
FEED_B_USED FEED_B_USED
FEED_C_USED FEED_C_USED
Recipe #1 Domain Recipe #2 Domain

Scope =
• VMD Specific
• Domain Specific
• Application-Association (defined over the network)

MMS Variables
• A Variable is an element of typed data for which access is “atomic” (access
to all data is either successful or fails – no partial success/failure).
• A Variable can be:
• Simple (e.g. Integer, Boolean, Float, etc…)
• Complex (e.g. structure)
• Array (multi-dimensional)
• A combination of the above
• A variable is described by its:
• Type and Address (MMS Only…not in IEC 61850)
• OR by Name

Type Description
• MMS Types are very flexible and can describe any data format
that can be represented in most computer languages.
• The nesting level describes how complex the types can be.

Simple Type Definitions
• A Simple Type definition consists of Class and Size (Precision) and has a “Nesting Level” of Zero.
• Type Classes:
BOOLEAN VISIBLESTRING
BITSTRING OCTETSTRING
INTEGER GENERALTIME (ISO)
UNSIGNED(INT) BINARYTIME(MMS)
FLOAT (IEEE) BCD
REAL(ISO)

Type Description
Although MMS Data has the form information
built-in (integer, string, Boolean, etc.) only Type
Definition has the precision (size) information needed
To convert to local format.
Var1: 16-bit Integer
Read Var1 Value =100
Response returns 1 byte of type

Integer with a value of 100.
Only the type description gives you the max value

Type Examples
‘c’ Definition Visual Precision Nest

INTEGER
Int var1 8,16,32,64 0
STRING
char var3[size] 0

Type Examples
'C' Definition Visual Precision Nest
INTEGER
int var4[3] 8,16,32,64 1
struct { 1
int var5; Integer
Character
char var6;
Integer
int var7;
}var8;
Type Examples – Array of Structures
'C' Definition Visual Precision Nest
struct { 2
int var5; Integer
char var6; Character
int var7; Integer
}var8[3];

Named Variable List = IEC 61850 Data Set
• A Named Variable List (NVL) is a named MMS object that

consists of a list of named or un-named variables.
• Once defined, a single Read/Write can access all the defined
variables.
• Note: NVL Access is not “atomic”. Access can be partially
successful because each variable exists independently.

Variable Services - General
• Read
• Write
• InformationReport
• Send a Read response without a Read request
• IEC 61850 Reports
• GetVariableAccessAttributes
• DefineNamedVariable
• DeleteNamedVariable
Variable Services - Lists
• DefineNamedVariableList
• GetNamedVariableListAttributes
• DeleteNamedVariableList

Reading a List of Variables
• Allows multiple individual variables to be read or written using a

single Read or Write service request. Non-Atomic Access. Each
variable is independent of the other variables in the list.
Read (var1, var2,var3)
ReadResponse with Data

(var1, var2, var3)

Alternate Access
• Allows partial access of arrays and structures

• Allows re-arranging of structure elements
Integer
Character Ability to access last
Integer integer or any subset of a
structure or an array.

Journal Definition
• A Journal is a Named MMS object that contains a time based record
of:
– Events
– Variables
• A Journal is accessed by:
– Time of Entry
– RecordNumber
• IEC 61850 Logs

Journal Services
• ReadJournal • ReportJournalstatus
• WriteJournal • CreateJournal
• InitializeJournal • DeleteJournal

File Services
• MMS provides simple file transfer (not access) by read access

only.
• ObtainFile service is used to tell remote node to read a file in

order to perform a file write.

File Services
• Obtainfile • FileRead
• FileOpen • FileRename
• FileClose • FileDelete
• FileDirectory

VMD Support Services
• Status – Obtain logical and physical status from a device
• UnsolicitedStatus – Send status (non-confirmed)
• GetNameList – Obtain a list of named MMS objects

VMD Services…
• Identify – Get vendor, model, and version information
• Rename – Rename named MMS objects
• GetCapabilityList – Get a list of the capabilities of the VMD

Context Management Services
• Initiate – Negotiate an association with another application.
• Conclude – Terminate an association gracefully.
• Abort- Terminate immediately, regardless of state.

Context Management Services
• Cancel – Cancel an outstanding MMS service request
• Reject – Reject an invalid message

• An abort of the association follows after a reject

Association Negotiation
• The process by which an application establishes an
association with another application.
• Definitions
• Calling: The node that requests an association
• Called: The node that responds to an associate request.
• CBB: Conformance Building Block. These
represent the functional characteristics and
services supported by a given application.

Negotiated Parameters
• Max Outstanding Services (Calling) – The number of MMS requests
that a client can issue without having to wait for a response.
• Max Outstanding Services (Called) – The number of MMS requests

that a server can queue before resources are overflowed.
The parameters are conveyed in the Initiate request and responses

for both the calling and called application.

Negotiated Parameters
• Max Data Structure Nesting Level
• MMS version number- 2=2002, 1=IS, 0=DIS
• Parameter CBBs Supported – conveys capabilities supported as

server only
• MMS Services Supported – conveys MMS services supported in a

server role (responder)

Parameter CBBs
• STR1 – Data complexity of arrays supported
• STR2 – Data complexity including structures supported
• Nest=X Overall data nesting complexity allowed
• VNAM – Named variables supported
• VADR – Address variable Support
• VALT – Alternate access support
• VLIS – Named variable list support
• TPY – Third party operations support
• CEI – Event condition evaluation interval can be changed
• REAL – ISO 8824 (ASN.1) floating point support


IEC 61850 Communications

Profiles
Protocols and Networks

IEC 61850-5 Interfaces
• Each numbered circle represents
a different kind of interface that
IEC 61850 standards address
• Each is based on a different use

case with unique requirements Station
for: Bus
– Performance
– Kind of messaging Process
– Kind of data exchanged Bus
– Types of functions
performed
– Communications profile

IEC61850 – Layered Standard
Device Object Models - IEC61850-7-3, 7-4, etc.
Abstract
Device Model Data Objects Data Types Naming Conventions
Abstract Service Model - IEC61850-7-2
Associate Reporting Self-Description Control Data Set Logs
M A P P I N G
Mapping to MMS Protocol - IEC61850-8-1
Real
Initiate InfoReport. GetNameList Write NamedVariableList Journals
Communication Stack Profiles
TCP / IP protocol stack

Benefits of Abstraction and Layering
• Abstract models are independent of the protocol and can be used outside of
protocol applications (SCADA tag naming convention)
• Enables definition beyond just the bytes on the wire to incorporate naming and
behavior
• Each layer can be optimized independently
• Enables protocols to be separated from application functions to enable use of

existing standards (Ethernet, TCP/IP, etc.)
• Enables use of the abstract concepts to other protocols/systems in the future as

technology changes.

Mapping IEC 61850 to XML
IEC 61850-8-2 MMS Mapping to XMPP IEC 61850-8-1 Mapping to MMS-TCP/IP
Electrical Power Systems
Electrical Power Systems Environmental Layer
IEC 61850-7-2, 7-3, 7-4, 8-1 object and service models User Layer IEC 61850-7-2, 7-3, 7-4, 8-1 object and service models
MMS per ISO 9506 and ACSE per ISO 8560 Application
Application MMS per ISO 9506 and ACSE per ISO 8560
using ASN.1 XML Encoding Rules (XER) ASN.1 Basic Encoding Rules (BER)
Presentation Presentation per ISO 8823
Extensible Messaging and Presence Protocol
(XMPP) per RFC
Session Session per ISO 8327
Transmission Control Protocol (TCP) Transport ISO Transport Class 0 over TCP Port 102 per RFC 1006
Internet Protocol (IP) per IETF recommendations Network Internet Protocol (IP) per IETF recommendations
Ethernet per IEEE 802 specifications Data Link Ethernet per IEEE 802 specifications
Ethernet per IEEE 802 specifications Physical Ethernet per IEEE 802 specifications

Using IEC 61850 for DNP3 Systems
IEC 61850
Utility Model Files
Requirements
Substation
Device
Template
ICD IEC 61850
Design Tool
ICD File
Spreadsheet Creator (Device Template) (SCT)
IEEE 1815.1
(or IEC 61850-80-1) IEC 61850 SCD File
XML Mapping File SCL to CIM
Generic Tag PI DNP3 CIM XML For Topology
Configuration Interface Information
Generation Configurator EMS/DMS CIM Adapter
System for PI
Other
DNP3/101/104
Interfaces
OSIsoft PI System

Basic IEC 61850 Profiles
Multicast Client/Server GDOI = Group Domain of
Core Interpretation RFC 6407 (to
Process I/O Symmetric ACSI Time access encryption keys)
State/Status
Messaging Messaging Key Access Services Synch
IGMP = Internet Group
Sampled GDOI Management Protocol RFC 4604
MMS IEEE (for routers to learn routing paths
Values GOOSE (for R-GOOSE
Protocol 1588 for multicast streams)
(SV) and R-SV)
DSCP = Differentiated Services

RFC 1006 Code Point RFC 2474/1475
UDP/IP Transport Layer Security (TLS) (quality of service for multicast
IGMP/DSCP streams)
(for R-GOOSE TCP/IP
and R-SV)
ISO/IEC 8802-3 Ethertype - Ethernet

The Profiles to Implement ACSI Services
• Process Bus
• Sampled Values (SV) over Multicast Ethernet (IEC 61850-9-2 and IEC 61869-9)
• Station Bus – IEC 61850-8-1

• Generic Object Oriented Substation Event (GOOSE) messaging over Multicast
Ethernet
• Client Server Messaging using MMS over TCP/IP
• Remote Communications – IEC 61850-8-1
• Routable Sampled Values (R-SV) over IP Multicast
• Routable GOOSE (R-GOOSE) over IP Multicast

Multi-Cast Application Association
Subscribing
Application
A B D
Network
A B B C C D 2 MCAAs
1 Service
Publishing Publishing Publishing Access
SERVER SERVER SERVER Point
ACSI Service: Send Data (unconfirmed)

Two Party Application Association (TPAA)
Client Client Client
Maximum
# of TPAA
Supported
SERVER

Association Negotiation
• The process by which an application establishes an association (a virtual connection) with
another application.
• Definitions
• Calling: The node that Initiates an association
• Called: The node that responds to an associate request.
– Independent of client/server roles:

• Once the association is established a given node can assume the role of client or server or both
over that association independent of calling/called.
• Typically: clients are the calling nodes.

Some Negotiated Parameters
• Max Outstanding Services (Calling) – The number of MMS requests that a client can issue
without having to wait for a response
• Max Outstanding Services (Called) – The number of MMS requests that a server can
queue before resources are overflowed
• Maximum Message size
• The parameters are conveyed in the Initiate request and responses for both the calling
and called application
• Other parameters are exchanged (e.g. services supported) where each side must accept
what the other side proposes
• These parameters are not typically visible or of primary concern to users.

ASCI Services for TPAA Management
• Associate – A request to establish an application association from a calling node to a
called node (MMS Initiate).
• Release – Gracefully terminate an existing application association (MMS Conclude)

• The server may deny a Release request
• Abort – Terminate an existing application association

• Cannot be denied. Association is terminated when sent.
• Reject – a malformed message was received. Immediately followed by an Abort. Not a

formal ACSI service but used by MMS.

Association Example
Attempt to establish the connection. Telephones

are a good example.
Phone Number?
Analogous to an IP Address

Association Example
After the connection is established, the language
of discussion needs to be established.
English
I speak English I speak English &

Spanish
Association Example
Language support equates to protocol version supported.
MMS 2002
Support MMS 2002 Supports 2002, IS

Association Example
After the context is established, the rules of
communication need to be established.
Rules
No Politics No Religion

The MMS Initiate parameters are analogous
Association Example to an agreement between parties on the
rules of communications.
InitateRequest
InitiateResponse
MaxOutCalling=5 MaxOutCalling=5
MaxOutCalled=5 MaxOutCalled=2
MaxMsgSize=128K MaxMsgSize=64K
The MMS Initiate parameters are analogous to an agreement

between the parties on the rules of communications


IEC 61850 and Ethernet
Brief Overview of Ethernet for IEC 61850

Ethernet and the 7 (9) Layer Model
9. Environment (Power Systems)
8. User (IEC 61850)

7. Application (MMS)
6. Presentation
5. Session
4. Transport
3. Network Logical Link Control (LLC)
EtherType
2. Data Link
Media Access Control (MAC)
IEEE 802.3 Carrier Sense Multiple Access with
1. Physical
Collision Detection (CSMA/CD)
Network Media
EtherType Packet Structure used by GOOSE and SV
8 Bytes 6 Bytes 6 Bytes 4 Bytes 2 Bytes 46-1500 Bytes 4 Bytes
Preamble DA SA 802.1Q Type/Length Data and Pad Frame Check
2 Bytes 2 Bytes
TAG User Priority CFI VLAN ID

Protocol 3 Bits 1 Bit 12 Bits
Identifier TAG CONTROL INFORMATION
▪ 4 bytes added to the Ethernet frame

▪ Tag Protocol Identifier (TPID) set to 8100 hex …identifies an 802.1Q message type
▪ 12 bits used for VLAN Identifier
▪ 3 bits used for Priority – 8 levels
▪ Canonical Format Indicator (CFI) = 0 for Ethernet
Virtual LAN (VLAN)
 VLANs: Are logical groupings of nodes that reside in a common broadcast domain
▪ Virtual because the VLAN is artificially created and the nodes need not be physically located on the
same switch or even reside in the same building, but
❑ Nodes that are members behave like they are connected together by one layer 2 bridge or switch
❑ A router is required to communicate between the two VLANs
VLAN 2
VLAN 1
Switch 3
Switch 1 Segment 3
Switch 2
E
F
Segment 1 G
Segment 2
A
B C

Ethernet Priority
▪ Ethernet 802.1q provides a priority setting
▪ “High” priority messages are moved to the priority queue
▪ Specified in IEC GOOSE and Implemented in GE Multilink Switch
Ethernet Switch Port 5 Port 6

New
Msg 1(high)
(low)
Msg 12 (low)
Msg
Msg 32 (med)
(low)
Msg 34 (med)
Msg (low)
Latency Msg 4 (low)
Port 1 Port 2 Port 3 Port 4
New (high) New “high priority” message for Port 6

Redundant Port Implementations
Redundant Port: 2 independent Ethernet ports with 2 different addresses
MAC – 1 Ethernet1 Ethernet2 MAC – 2

IP Addr - 1 IP Addr - 2
Redundant Media: 1 Ethernet port with switched media
MAC – 1
Ethernet
IP Addr - 1
Switches on loss of Ethernet link

pulses
Primary Back-Up
Redundant Media is Common
Current Redundant Network Configuration
Ethernet Switch Ethernet Switch Ethernet Switch
The time to rebuild

MAC tables after
Ethernet Card failure is critical
feature of the
switches
WAN WAN
Rapid Spanning Tree Protocol (RSTP) enables network rebuild after MAC failure/change
RSTP Networks
Single Ring Network Recovers Quickly

VLAN Configuration Difficult for Large # of Devices

Multiple Rings = Localized VLAN Configurations More
Devices & Longer Recovery

Alternatives –Ring with embedded switches
IEC 62439-3: High Availability Seamless Redundancy Protocol (HSR)
Discarded
1b
1a 1b 1b 1b
1b 1b
E-Net1 E-Net2 E-Net1 E-Net2 E-Net1 E-Net2
Switch Switch Switch
IED IED IED
Recovery to a single link failure is immediate

Works for small number of devices

Alternative– Redundant Parallel Networks
IEC 62439-3: Parallel Redundancy Protocol (PRP)
LAN2
1a
Destination
E-Net1 E-Net1 E-Net1
nodes
PRP
discard
IED PRP IED PRP IED
E-Net2 E-Net2 E-Net2
packets they
1b
already
received
LAN1
Recovery to a single link failure is immediate

Emerging Approaches – Redundant
Parallel Networks
IEC 62439-3: Parallel Redundancy Protocol (PRP) PDU
PRP Header
LAN A
LAN B
PRP Cache
First PRP frame
received
is delivered PDU
HSR and PRP Can Be Used Together

IEC61850 Virtual Model
From IEC61850-7-1
ACSI using MMS

Two Party Application Association
Maximum
# of TPAA
Supported
SERVER

Subscribing
Application
A B D
Network
A B B C C D 2 MCAAs
1 Service
Publishing Publishing Publishing
Access
SERVER SERVER SERVER
Point
Service: send Data (unconfirmed)

• We will present the basic ACSI Objects and the MMS Services
to which they are mapped in IEC 61850-8-1 (Specific
Communication Service Mapping (SCSM) for MMS over
TCP/IP-Ethernet)
• This conflates the virtual ACSI model with the concrete SCSM
of MMS but facilitates understanding of what you will see in
real devices

ACSI Objects and MMS Mapping
ACSI Object Class MMS Object
SERVER class Virtual Manufacturing Device (VMD)
LOGICAL DEVICE class Domain
LOGICAL NODE class Named Variable
DATA class Named Variable
DATA-SET class Named Variable List
SETTING-GROUP-CONTROL-BLOCK class Named Variable
REPORT-CONTROL-BLOCK class Named Variable
LOG class Journal
LOG-CONTROL-BLOCK class Named Variable
GOOSE-CONTROL-BLOCK class Named Variable
GSSE-CONTROL-BLOCK class Named Variable
CONTROL class Named Variable
Files Files

• We will present the basic ACSI Objects and the MMS Services
to which they are mapped in IEC 61850-8-1 (Specific
Communication Service Mapping (SCSM) for MMS over
TCP/IP-Ethernet)
• This conflates the virtual ACSI model with the concrete SCSM
of MMS but facilitates understanding of what you will see in
real devices

Two Party Application Association (TPAA)
Maximum
# of TPAA
Supported
ACSI Service
SERVER forServers MMS Service Description
Associate Initiate Establish a TPAA
Abort Abort Abort a TPAA
Release Conclude Release a TPAA Gracefully

Subscribing
Application
A B D
Network
A B B C C D 2 MCAAs
1 Service
Publishing Publishing Publishing Access
SERVER SERVER SERVER Point
ACSI Service MMS
for Servers Service Description
Send N/A Send data over an MCAA
Receive N/A Receive data from an MCAA

ACSI Services
ACSI Services MMS Services
LogicalDeviceDirectory GetNameList
GetAllDataValues Read
GetDataValues Read
SetDataValues Write
GetDataDirectory GetVariableAccessAttributes
GetDataDefinition GetVariableAccessAttributes
Enable GetDataSetValues Read
Self SetDataSetValues Write
Describing CreateDataSet CreateNamedVariableList
DeleteDataSet DeleteNamedVariableList
Devices GetDataSetDirectory GetVariableAccessAttributes
Report (Buffered and Unbuffered) InformationReport
GetBRCBValues/GetURCBValues Read
SetBRCBValues/SetURCBValues Write
GetLCBValues Read
SetLCBValues Write
QueryLogByTime ReadJournal
QueryLogAfter ReadJournal
GetLogStatusValues GetJournalStatus
Select Read/Write
SelectWithValue Read/Write
Cancel Write
Operate Write
Command-Termination Write

SERVER Object and Services
• Obtain a list of:

• Logical Devices
– MMS GetNameList service, Object Class = domain
• Files
– MMS FileDirectory service
LOGICAL DEVICE Object and Services
• Obtain a list of Logical Nodes in a Logical

Device:
• MMS GetNameList where Object Class =
Variable and Domain = Logical Device name

LOGICAL NODE Class Attribute name
GenLogicalNodeClass
Attribute type Explanation
LNName ObjectName Instance name unambiguously
identifying the logical node within
the scope of a logical device.
LNRef ObjectReference Unique path-name of the logical
node: LDName/LNName.
DataObject [1..n] GenDataObjectClas All data objects contained in the
s logical node.
NOTE IEC 61850-7-4 defines
standardized data object classes.
DataSet [0..n] DATA-SET All DataSets contained in the logical
node.
BufferedReportControlBlock [0..n] BRCB All buffered report control blocks
contained in the logical node.
UnbufferedReportControlBlock [0..n] URCB All unbuffered report control blocks
LogControlBlock [0..n] LCB All log control blocks contained in
the logical node.
IF compatible LN class equals LLN0 of name space IEC 61850 -7-4
SettingGroupControlBlock [0..1] SGCB Setting group control block
Log [0..n] LOG All logs contained in the logical
node.
GOOSEControlBlock [0..n] GoCB All GOOSE control blocks contained
in the logical node.
MulticastSampledValueControlBlock MSVCB All multicast sampled value control
[0..n] blocks contained in the logical node.
UnicastSampledValueControlBlock USVCB All unicast sampled value control
[0..n] blocks contained in the logical node.
Routable GOOSE Control Block [0..n] RgCB All R-GOOSE control blocks
contained in the logical node. Added in IEC 61850-8-1 Ed2.1
Routable Sampled Value Control RsCB All R-SV control blocks contained in
Block [0..n] the logical node.
Services
GetLogicalNodeDirectory
GetAllDataValues

LOGICAL NODE Services
• GetLogicalNodeDirectory
• MMS GetNameList where
– ObjectClass = Variable Name, NamedVariableList, and Journal
– ObjectScope = Logical Device Name
– (Can be simplified)
• GetAllDataValues
• MMS Read where Variable Name = Logical Node Name
– Not always practical due to MMS message size restrictions

ACSI Services for DATA
• GetDataValues
• MMS Read where Variable Name = name of DATA Object
• SetDataValues
• MMS Write where Variable Name = name of DATA Object
• GetDataDirectory and GetDataDefinition

• MMS GetVariableAccessAttributes

DATA-SET
• Named object consisting of a set of DATA
• Maps to an MMS Named Variable List in IEC61850-8-1
• Used for Reporting, GOOSE and Sample Values

DATA-SET Object and Services
• GetDataSetValues = Read
• SetDataSetValues = Write
• CreateDataSet = DefineNamedVariableList
• DeleteDataSet = DeleteNamedVariableList
• GetDataSetDirectory = GetNamedVariableListAttributes

Using ACSI for Data Discovery
And the fast way to do it with MMS

ACSI Service Mapping using MMS
• GetLogicalNodeDirectory:
• GetNameList of variables in Logical Device domain (variables
defined under MMXU1)
• GetAllDataValues
• Read MMXU1

ACSI Service Mapping using MMS
• GetDataDirectory maps to
– GetVariableAccessAttributes of:
– MMXU1$MX$ PhV
– MMXU1$CF$ PhV
– MMXU1$DC$ PhV
– MMXU1$EX$ PhV
– MMXU1$SV$ PhV
• To obtain list of data defined within PhV (cVal or instCVal, range, q, t, subEna, etc.)
• GetDataDefinition maps to
– GetVariableAccessAttributes
– MMXU1$MX$ PhV$PhsA – PhsB – PhsC
of:
– MMXU1$CF$ PhV$PhsA – PhsB – PhsC
– MMXU1$DC$ PhV$ PhsA – PhsB – PhsC
– MMXU1$EX$ PhV$ PhsA – PhsB – PhsC
– MMXU1$SV$ PhV$ PhsA – PhsB – PhsC
• To obtain list and type of data contained within PhV (cVal$mag$f, cVal$ang$f, etc.)
• Now repeat for all attributes, data objects, logical nodes and logical
devices

IEC61850 Client Simplification
• Rather than executing multiple GetVariableAccessAttribute

requests for each and every element of MMXU:
• A smart IEC 61850 client will perform a GetVariableAccessAttributes on

the MMXU1 object and derive all the LOGICAL NODE, DATA, and attribute
information from a single response.
• Instead of many minutes to retrieve the definitions, it takes

only a few seconds

AX-S4 61850 Overview
Complete IEC 61850 Interface for OPC Applications

Description
• Complete “Access For IEC 61850” interface for Windows applications

– IEC 61850 Client to access data in IEC 61850 devices
– IEC 61850 Server for gateways, concentrators, and proxies.
– IEC 61850 GOOSE publisher and subscriber
• Standardized interface to applications:

– OPC Data Access (DA) V3.0 (see http://www.opcfoundation.org)
– Backward Compatible to OPC DA V2.05
• Supports Windows 7, Windows 10, Server 2012 and Server 2016
© Copyright 2016 SISCO, Inc.

Complete Architecture

Basic Application
Substation Ethernet LAN

Client Features
• IEC 61850 Ed.1 and Ed.2 Client functions supported (OPC Server):
• Object discovery and automatic configuration of data using ACSI services
• SCL (IEC 61850-6-1) import to configure client with remote device data objects
– Can import individual devices via ICD, IID and CID Files
– Can import an entire substations in a single operation via SCD files
• Transparent and Automatic Handling of Buffered and Unbuffered Reporting
• Read/Write of any IEC 61850 Object
• Automated Controls (with Normal or Enhanced Security)
• Logs
• File Transfer client
• OPC DA V3.0 Server
• IEC 62351 secure communications supported:
– TLS 1.2 for server level authentication and encryption
– X.509 Digital certificates for strong application level authentication.
• Includes interactive object explorer for device object visualization, debug, testing,
configuration, and control.

Explorer – Interactive Access

“Out-of-the-Box” and Ready to Run System
After installation there is a pre-configured IEC 61850 server (based on the AX-S4 61850
Server) supporting ACSI and GOOSE with simulated data that can be accessed via the AX-S4
61850 client or other networked ACSI clients and GOOSE devices.
Useful for application testing or illustrating configuration and setup concepts.
Let’s Install
• Unzip to any folder • Other Devices:
• Run Setup – Bitronics Meter
– Installs prerequisites • 50.227.243.169
– Installs AX-S4 61850 – Siemens relay

• 50.227.243.170
• Set Ethernet Adapter in AX-S4
GOOSE Configuration Utility – SEL relay
• 50.227.243.171
• Run AX-S4 61850 Server
• Run AX-S4 61850 Explorer

Run AX-S4 61850 Explorer

Debugging – SISCO Log System
• AX-S4 61850 Client, Server, GOOSE can be run as a regular process or as a
service. Explorer can only be run as a process
• When run in process logging information can be displayed in window at the
bottom of the screen
• When run as a service there is no GUI and you would use the SISCO Log
Viewer to look at the activity of the service
• A Log Configuration Editor can be used to change what gets logged
• Generally: use the default to avoid excessive logging
• Change the log levels only if directed by SISCO support or if you need to investigate an issue
• Log files, documentation and configuration files are located here:
C:\ProgramData\SISCO\AX-S4 61850\<component name>

Report Model

Reporting
• Unbuffered Reporting allows clients to receive data from the
server without polling.
• If network connection (TPAA) between client and server is lost, data is lost.
• Buffered reporting enables the server to retain data if

associations are lost enabling the client to retrieve ALL data.
• Reports are sent using MMS InformationReport

Report-Log Model

Attribute Name Description
RptID Name assigned to this URCB
Report RptEna
Resv
= 1 Reports enabled, = 0 Reports disabled
= 1 In-use by client, =0 Available (unbuffered only)
DatSet Name of the DATA-SET reference
Control ConfRev
OptFlds
Configuration Revision Number (can track Data Set changes)
Optional Fields to Include in the Report
Block sequence-number
report-time-stamp
Include the sequence number
Include a report time stamp (even if DATA is time stamped)
reason-for-inclusion The reason the report was sent (dchg, qchg, etc.)
Attributes data-set-name
data-reference
Include the DATA-SET name in the report
Include the names of the DATA elements in the report
buffer-overflow Include buffer status in report (buffered only)
entry-ID Include the entry ID in the report (buffered only)
conf-revision Include the current value of the ConfRev in the report
BufTim Buffer Time (the fastest that reports will be sent)
SqNum Sequence Number
TrgOp Trigger Conditions
data-change Send report on data change exceeding deadband
data-update Send report if data is updated even if it didn’t change
Send report on change in quality
integrity Send report on integrity period expiration
general-interrogation Send report when requested
IntPd Integrity Period
GI General Interrogation
PurgeBuf Purge the report buffer (buffered only)
EntryID Start reporting from a specific entry in the buffer (buffered only)
TimeOfEntry Start reporting from a specific entry time (buffered only)
ResvTms Reservation Timer (buffered only) - OPTIONAL EDITION 2
Owner Client ID of RCB owner - OPTIONAL EDITION 2

OptFlds – What data should be sent in a report
MSB LSB
0 1 2 3 4 5 6 7 8 9 10 11 12 13 15 16
Unused
Bit 9 segmentation
Bit 8 conf-revision
Bit 7 entryID
Bit 6 buffer-overflow
Bit 5 data-reference
Bit 4 data-set-name
Bit 3 reason-for-inclusion
Bit 2 report-time-stamp
Bit 1 sequence-number
Bit 0 reserved

TrgOp – What changes should trigger a report
MSB LSB
0 1 2 3 4 5 6 7
Unused
Bit 5 general-interrogation
Bit 4 integrity
Bit 3 data-update (data updated but did not change)
Bit 2 quality-change
Bit 1 data-change
Bit 0 reserved

Unbuffered Report Control Block – URCB
URCB class
Attribute name Attribute type r/w Value/value range/explanation
URCBName ObjectName Instance name of an instance of BRCB
URCBRef ObjectReference Path-name of an instance of BRCB
Specific to report handler
RptID VISIBLE STRING129 r/w c1
RptEna BOOLEAN r/w
Resv BOOLEAN r/w
DatSet ObjectReference r/w c1
ConfRev INT32U r
OptFlds PACKED LIST r/w c1
BufTm INT32U r/w c1
SqNum INT8U r
TrgOps TriggerConditions r/w c1
IntgPd INT32U r/w 0.. MAX; 0 implies no integrity report.
GI BOOLEAN r/w
Owner OCTET STRING64 r c2

Buffered Report Control Block – BRCB
BRCB class
BRCBName ObjectName Instance name of an instance of BRCB
BRCBRef ObjectReference Path-name of an instance of BRCB
Specific to report handler
RptID VISIBLE STRING129 r/w c1, c2
RptEna BOOLEAN r/w
DatSet ObjectReference r/w c1, c2
ConfRev INT32U r
OptFlds PACKED LIST r/w c2
BufTm INT32U r/w c1, c2
SqNum INT16U r
TrgOps TriggerConditions r/w c1, c2
IntgPd INT32U r/w c1, 0.. MAX; 0 implies no integrity report
GI BOOLEAN r/w
PurgeBuf BOOLEAN r/w
EntryID EntryID r/w c2
TimeOfEntry EntryTime r
ResvTms INT16 r/w c3
Owner OCTET STRING64 r c4

ResvTms – Reservation Time
• Used to control access to the BRCB (and other CBs) by clients as follows:
= -1 BRCB is assigned per configuration to specific clients
=0 Not reserved for any client
>0 Number of seconds that the BRCB will remain reserved for a client after a disconnect.
Buffering will happen during that time. Upon expiration buffering is stopped and BRCB
is unreserved.

Report Services
• Report = MMS Information Report
• GetBRCBValues or GetURCBValues
• MMS Read
• SetBRCBValues or SetURBCValues
• MMS Write

Report Format

Report Format (cont’d)

IEC 61850 Report
• A “Report” is when a server sends data without a client request.
• In IEC 61850-8-1 reports are mapped to the MMS

InformationReport service
• InformationReport is essentially a way to send the data from a Read

response without the client having to ask for it

IEC 61850-8-1 Report Format
parameter name Condition
RptID Shall always be present
Reported OptFlds Shall always be present
SeqNum Shall be present if OptFlds.sequence-number is TRUE
TimeOfEntry Shall be present if OptFlds.report-time-stamp is TRUE

DatSet Shall be present if OptFlds.data-set-name is TRUE
BufOvfl Shall be present if OptFlds.buffer-overflow is TRUE
EntryID Shall be present if OptFlds.entryID is TRUE
ConfRev Shall be present if OptFlds.conf-rev is TRUE
SubSeqNum Shall be present if OptFlds.segmentation is TRUE
MoreSegmentsFollow Shall be present if OptFlds.segmentation is TRUE
Inclusion-bitstring Shall be present
data-reference(s) Shall be present if OptFlds.data-reference is TRUE
value(s) See AccessResult for value(s)
ReasonCode(s) Shall be present if OptFlds.reason-for-inclusion is TRUE
Inclusion-bitstring tells the client what data from the dataset is in the report
RCB Reservation Rules
• RCBs can be reserved via SCL which has supremacy over Resv and ResvTms
• If SCL reserved:
– URCB.Resv = True
– BRCB.ResvTms = -1
• If Resv or ResvTms = 0 then it is available for a client to take control of the RCB:
• Write BRCB.ResvTms = > 0
• Write URCB.Resv = True
• The client must reserve the RCB before attempting to write any other
elements of the RCB (e.g. enabling the RCB)
• The client must know about SCL reservations by processing the SCL file
• The client cannot override an SCL reservation even if the RCB is reserved for
that client by SCL

Example Reporting Sequence for URCB
1. Write OptFlds for BufTim, TrgOp, IntgPd (DataSet, etc.) to desired values:
1. MMXU1$RP$urcbMX$OptFlds = 011110001000000 (include: Sequence #, report time
stamp, reason for inclusion, data set name, and configuration revision)
2. MMXU1$RP$urcbMX$BufTim = 500 (500 milliseconds)
3. MMXU1$RP$urcbMX$TrgOp = 01100000 (data and quality change only)
4. MMXU1$RP$urcbMX$IntgPd = 60000 (1 minute)
2. Enable Report
1. MMXU1$RP$urcbMX$RptEna = 1
3. Receive Reports
Is this correct?
Example Reporting Sequence - CORRECTED
1. Find URCB where Resv = 0 and Write Resv = 1
2. Write OptFlds, BufTim, TrgOp, IntgPd (DataSet, etc.) to desired values:
1. MMXU1$RP$urcbMX$OptFlds = 011110001000000 (include: Sequence #, report time stamp,
reason for inclusion, data set name, and configuration revision)
2. MMXU1$RP$urcbMX$BufTim = 500 (500 milliseconds)
3. MMXU1$RP$urcbMX$TrgOp = 01101000 (data, quality, and integrity only)
4. MMXU1$RP$urcbMX$IntgPd = 60000 (1 minute)
3. Enable Report Integrity Enabled

1. MMXU1$RP$urcbMX$RptEna = 1
4. Receive Reports

Buffered Reporting with GI Example
Client enables BRCB
report SqNum = 01, data change, <data>

report SqNum = 03, integrity, <data>
IEC 61850 Communications Terminated
Client
time
Communications Reestablished – Client Re-Enables the BRCB
Client request General-Interrogation

report SqNum = 10, general-interrogation, <data>
SqNum = 10 flags when the GI was issued by the client to identify data that was reported while disconnected.

Buffered Reporting with EntryID Example
Client enables BRCB
report EntryID = 0102, data change, <data>

report EntryID = 0204, data change, <data>
report EntryID = 6402, integrity, <data>
Communications Terminated
EntryID = 5987, data change, <data> BUFFERED

EntryID = 2615, data change, <data> BUFFERED
time
IEC 61850 EntryID = 4550, integrity, <data> BUFFERED
Communications Reestablished
Client
Client sets EntryID = 6402, Then enables BRCB


Using Modeling to Control Reports
• Requirements:
– Desire to receive any change of any current measurements on
all 3 phases of a feeder should be reported immediately
– Any under or over voltage or current conditions should be
reported immediately
– The voltage on Phase A should be reported every 10 minutes
• Use MMXU for actual measurements and range alarms

Measurement Unit (MMXU)
From IEC61850-7-4

WYE Measurements
From IEC61850-7-3

Complex Measured Value (CMV)
From IEC61850-7-3

Solution
• Define a Dataset containing:
– MMXU1.MX.A
A change in ANY of these values will cause an immediate report to be
– MMXU1.MX.PhV.phsA.range sent AFTER the BuffTim expires as long as the RCB is enabled and
– MMXU1.MX.PhV.phsB.range TrgOp = dchg is set.
– MMXU1.MX.PhV.phsC.range
– MMXU1.MX.PhV.phsA.instCVal.mag.f None of these values have TrgOp = dchg so they will not trigger
– MMXU1.MX.PhV.phsA.q reports when their value changes. Their values will only be sent in
– MMXU1.MX.PhV.phsA.t Integrity reports
• Assign this dataset to a report control block with:

– Integrity = 10 minutes
– TrgOp = data-change and integrity
• Enable the report

Service Data object Common data class T
LTRK
Explanation PresCond
Tracking
name nds/ds
Descriptions
Status information
LTRK Health
Mir
ENS (HealthKind)
SPS
inherited from: DomainLN
inherited from: DomainLN
Controls
O / na
MOcond(1) / na

Settings
Control and access service tracking
SpcTrk CTS (BOOLEAN) Control service tracking for controllable single point status data. O / na
DpcTrk CTS (BOOLEAN) Control service tracking for controllable double point status data. O / na
IncTrk CTS (INT32) Control service tracking for controllable integer status data. O / na
EncTrk CTS (EnumDA) Control service tracking for enumerated n controllable status Omulti / na
data.
ApcFTrk CTS (AnalogueValueCtlF) Control service tracking for controllable analogue setpoint data O / na
with float command.
ApcIntTrk CTS (AnalogueValueCtlInt) Control service tracking for controllable analogue setpoint data O / na
with integer command.
BscTrk CTS (StepControlKind) Control service tracking for binary controlled step position data. O / na
IscTrk CTS (INT8) Control service tracking for integer controlled step position data. O / na
BacTrk CTS (StepControlKind) Control service tracking for binary controlled analogue data. O / na
GenTrk CST Common service tracking for all services for which no specific O / na
tracking data exists.
UrcbTrk UTS Access service tracking for unbuffered report control blocks. O / na
BrcbTrk BTS Access service tracking for buffered report control blocks. O / na
LocbTrk LTS Access service tracking for log control blocks. O / na
GocbTrk GTS Access service tracking for GOOSE control blocks. O / na
MsvcbTrk MTS Access service tracking for multicast sampled values control O / na
blocks.
UsvcbTrk NTS Access service tracking for unicast sampled values control blocks. O / na
SgcbTrk STS Access service tracking for setting group control blocks. O / na

Common Service Tracking – CST
CST Class
Attribute name Attribute type FC TrgOp r/w Value/Value range M/O/C
DataName Inherited from Data Class
Specific to the CST
objRef ObjectReference SR dupd r Reference of the object that M
is used in the tracking:
either a control block that is
being accessed or a control
object that is being
controlled.
serviceType ServiceType SR r Type of the tracked service M
errorCode ServiceError SR r See error associated to the M
service that is specified by
serviceType; value None for
successful service
originatorID OCTET STRING64 SR r Originator of the service O
t TimeStamp SR r TimeStamp of the M
completion of the service or
entryTime for report buffer
entries
d VISIBLE STRING255 DC r O
dU UNICODE STRING255 DC r O
cdcNs VISIBLE STRING255 EX r AC_DLNDA_M
cdcName VISIBLE STRING255 EX r AC_DLNDA_M
dataNs VISIBLE STRING255 EX r AC_DLN_M
For Control Blocks: ObjectReference = LDName/LNName.CBName

Unbuffered Report Tracking Service – UTS
UTS Class
Specific to the UTS
rptID VISIBLE STRING129 SR r Service parameter ReportIdentifier M
is mapped to rptID
rptEna BOOLEAN SR r Service parameter ReportEnable M

is mapped to rptEna
resv BOOLEAN SR r Service parameter Reserve M

DatSetReference is mapped to
datSet
confRev INT32U SR r Service parameter M

to confRev
optFlds PACKED_LIST SR r Service parameter OptionalFields M

is mapped to optFlds
bufTm INT32U SR r Service parameter BufferTime is M

mapped to bufTm
sqNum INT32U SR r Attribute SqNum of BRCB is M

mapped to sqNum

TriggerOptionsEnabled is mapped
to trgOps
intgPd INT32U SR r Service parameter IntegrityPeriod M

is mapped to intgPd
gi BOOLEAN SR r Service parameter M

GeneralInterrogation is mapped to
go

Buffered Report Tracking Service – BST
BTS Class
Specific to the BTS
rptID VISIBLE STRING129 SR r Service parameter ReportIdentifier is M
mapped to rptID
rptEna BOOLEAN SR r Service parameter ReportEnable is M

mapped to rptEna
datSet ObjectReference SR r Service parameter DatSetReference is M

mapped to datSet
confRev INT32U SR r Service parameter ConfigurationR evision M

is mapped to confRev
optFlds PACKED_LIST SR r Service parameter OptionalFields is M

mapped to optFlds
bufTm INT32U SR r Service parameter BufferTime is mapped M

to bufTm
sqNum INT32U SR r Attribute SqNum of BRCB is mapped to M

sqNum

TriggerOptionsEnabled is mapped to
trgOps
intgPd INT32U SR r Service parameter IntegrityPeriod is M

mapped to intgPd
gi BOOLEAN SR r Service parameter GeneralInterrogation M

is mapped to go
purgeBuf BOOLEAN SR r Service parameter PurgeBuf is mapped M

to purgeBuf
entryID EntryID SR r Service parameter EntryIdentifier is M

mapped to entryID
timeOfEntry EntryTime SR r Service parameter TimeOfEntry is M

mapped to timeOfEntry
resvTms INT16 SR r Service parameter ReserveTimeSecond O

is mapped to resvTms

Using Reports with AX-S4 61850 Client

AX-S4 61850 Client Reporting
• Flexible support for reporting:
• Completely manual via OPC client interactions
• Completely automatic via manual configuration of Auto Reports
– With support for auto creation of dynamic Data Sets
• Completely automatic via SCL import
• Once Auto Reports are configured AX-S4 61850 will automatically

handle all report functions
• OPC clients only need to access the data via normal OPC DA 3.00 clients

Auto Report
Configuration

OPC Client Access to Reports

Reporting Tips
• Create Data Sets that use reported data separately from data that is polled
• Define large Data Sets (given Maximum Message Size constraints) rather than
more smaller Data Sets
• Put high speed data in different Data Sets from infrequently changing data
• Don’t use a smaller buffer time than you really need for the application
• Use the OPC Reports branch to find data that is Reported
• Put ONLY reported data into OPC Groups and set Group Update Rate = 0
• Check Minimum Group Update Rate setting for polled data


Controls

Control Model Objects
• Enables control of ACSI Objects:
– Controllable Single Point (SPC)
– Controllable Double Point (DPC)
– Controllable Integer Status (INC)
– Binary Controlled Step Position (BSC)
– Integer Controlled Step Position (ISC)
– Controllable Analog Set Point (APC)
– Controllable Enumerated Set Point (ENC) Ed.2

Control Services
• Services available for controlling objects:
• Select (Sel)
• SelectWithValue (SelVal)
• Cancel
• Operate (Oper)
• TimeActivatedOperate (TimOper)
• Command Termination

Control Model (ctlModel)
• Describes the modes of control allowed for a given controllable object
0: Status only. No control allowed.

1: Direct control with normal security (direct-operate)
2: SBO control with normal security (operate-once or operate-many)
3: Direct control with enhanced security (direct-operate)
4: SBO control with enhanced security (operate-once or operate-many)

General Control Model

Direct Control with Normal Security

SBO Control with Enhanced Security
Report_req(int)

Mapping Controls to MMS
• IEC61850-8-1 adds attributes to control objects :
• SBO – for Select operations (Read)
• SBOw – for SelectWithValue operations (Write)
• Oper – for Operate commands (Write)
• Cancel – for cancel commands (Write)
• A client either Reads from or Writes to these objects to invoke the

command
• Replaces CDC objects with CO functional constraint (ctlVal in Ed.2)
• Needed because of the way 7-2 maps the controllable CDCs to ACSI
• ACSI doesn’t define the detailed control operations for MMS
SBO Structure for DPC
Contains object name

For Select: SBO e.g. CSWI1$CO$Pos$Oper

SBOw Structure per 8-1
IEC 61850-7-2 IEC 61850-8-1 component name FC MMS TypeDefinition m/o
parameter
ctlVal <CO_CtrlObjectRef>$SBOw$ctlVal depending of the CDC of the m

control object – see IEC
61850-7-3
operTm <CO_CtrlObjectRef>$SBOw$operTm Timestamp c
origin <CO_CtrlObjectRef>$SBOw$origin Originator (Structure) m
ctlNum <CO_CtrlObjectRef>$SBOw$ctlNum INT8U m
T <CO_CtrlObjectRef>$SBOw$T Timestamp m
Test <CO_CtrlObjectRef>$SBOw$Test BOOLEAN m
Check <CO_CtrlObjectRef>$SBOw$Check CheckConditions m
NOTE 1 ctlVal type is dependant of the CDC of the object (e.g. ctlVal or ctlVal$f).
NOTE 2 The service parameter operTm shall only be present if the control object support TimeActivatedOperate.
CtrlObjectRef = CSWI1$CO$Pos
A client writes all these elements as a structure to perform a SelectWithValue

Oper Structure per 8-1
parameter
ctlVal <CO_CtrlObjectRef>$Oper$ctlVal depending of the CDC of the m

61850-7-3
operTm <CO_CtrlObjectRef>$Oper$operTm Timestamp c
origin <CO_CtrlObjectRef>$Oper$origin Originator (Structure) m
ctlNum <CO_CtrlObjectRef>$Oper$ctlNum INT8U m
T <CO_CtrlObjectRef>$Oper$T Timestamp m
Test <CO_CtrlObjectRef>$Oper$Test BOOLEAN m
Check <CO_CtrlObjectRef>$Oper$Check CheckConditions m
A client writes all these elements as a structure to perform an Operate

Cancel Structure
parameter
ctlVal <CO_CtrlObjectRef>$Cancel$ctlVal depending of the CDC of the m

61850-7-3
operTm <CO_CtrlObjectRef>$Cancel$operTm Timestamp c
origin <CO_CtrlObjectRef>$Cancel$origin Originator (Structure) m
ctlNum <CO_CtrlObjectRef>$Cancel$ctlNum INT8U m
T <CO_CtrlObjectRef>$Cancel$T Timestamp m
Test <CO_CtrlObjectRef>$Cancel$Test BOOLEAN m
A client writes all these elements as a structure to Cancel a previous Select, SelectWithValue or Operate

Originator Structure
orCat – Category of Control Action

0 – not supported
1 – Bay Control
2 – Station Control
3 – Remote Control
4 – Automatic Bay
5 – Automatic Station
6 – Automatic Remote
7 – Maintenance
8 – Process
orIdent – Originator Identity (binary ID) Typically IP Address of client

Check Conditions
CheckConditions (PackedList)
Attribute name Attribute type (Value/Value range) Description PresCond
synchrocheck BOOLEAN If true, perform synchrocheck (Bit0 (MSB)) M
interlockCheck BOOLEAN If true, check for interlocking condition (Bit1 (LSB)) M

ACSI Select Mapping to MMS
ACSI Select
MMS Read of
CSWI1$CO$Pos$SBO
Positive Read response contains the

name of the object being controlled:
CSWI1$CO$Pos$SBO or
CSWI1$CO$Pos$Oper or
CSWI1$CO$Pos
Negative Read response means the

Select did not succeed
ACSI SelectWithValue Mapping
MMS Write Response is either:

(+) Select was successful
(-) Select was Not Successful

ACSI Operate Mapping

(+) Operate command will be processed
(-) Operate will not be processed
468

ACSI Cancel Mapping

(+) Operate, Select or SelectWithValue was cancelled
(-) Operate, Select or SelectWithValue was not cancelled

ACSI CmdTerm(+) Mapping
MMS InformationReport containing Oper structure means the

Operate was successfully completed

ACSI CmdTerm(-) Mapping
MMS InformationReport containing 2 structures:

1.LastApplError (with reference to the control object)
2.Oper structure used in the Operate command
AddCause
Error codes and Unknown

Not-supported
Blocked-by-switching-hierarchy
0
1
2
Additional Causes Select-failed

Invalid-position
Position-reached
3
4
5
(AddCause)
Parameter-change-in-execution 6
Step-limit 7
Blocked-by-Mode 8
Blocked-by-process 9
Blocked-by-interlocking 10
Blocked-by-synchrocheck 11
Command-already-in-execution 12
Blocked-by-health 13
Error = 1-of-n-control 14
Abortion-by-cancel 15
0: No Error (default see AddCause) Time-limit-over 16
Abortion-by-trip 17
1: Unknown Object-not-selected
Object-already-selected
18
19
2: Timeout test not OK No-access-authority

Ended-with-overshoot
20
21
3: Operator test not OK Abortion-due-to-deviation

Abortion-by-communication-loss
22
23
Blocked-by-command 24
None 25
Inconsistent-parameters 26
Locked-by-other-client 27

Examples
Changing Switch Positions Using

Various Control Modes (CSWI1)
Direct Operate Normal Security
• Verify (optional)
• Read CSWI1$ST$Pos$stVal (current position)
• Read CSWI1$CF$Pos$ctlModel (control model = 1)
• Operate:
• Write CSWI1$CO$Pos$Oper
» ctlVal, operTm, origin, ctlNum, T, Test, Check

Select Before Operate Normal Security
• Read CSWI1$ST$Pos$stSeld (= false if not already selected)
• Select:
• Read CSWI1$CO$Pos$SBO (return value = CSWI1$CO$Pos$Oper)
• Optional: Read CSWI1$ST$Pos$stSeld (= true if selected)
• Operate:

Direct Operate with Enhanced Security
• Read CSWI1$ST$Pos$stSeld (= false if not already selected)
• SelectWithValue:
• Write CSWI1$CO$SBOw
• Optional Read CSWI1$ST$Pos$stSeld (= true if selected)
• Operate:
• CmdTerm (Command Termination)

• (+) InformationReport containing CSWI1$CO$Pos$Oper
• (-) InformationReport containing LastApplError and CSWI1$CO$Pos$Oper

SBO with Enhanced Security
• Read CSWI1$ST$Pos$stSeld (= false is not already selected)
• SelectWithValue:
• Write CSWI1$CO$SBOw
• Optional Read CSWI1$ST$Pos$stSeld (= true if selected)
• Operate:
• CmdTerm (Command Termination)

• (+) InformationReport containing CSWI1$CO$Pos$Oper
• (-) InformationReport containing LastApplError and CSWI1$CO$Pos$Oper
Client Applications
• Typical bay controllers expose simple control commands such
as Select-Operate or Operate.
• HMI screen developers can use ActiveX controls or scripts to

embed the control state machine and functions within a
simple interface
• Some IEC 61850 clients provide simplified operations that

enable write of the ctlVal only.

Using AX-S4 61850 for Controls

Multiple Choices for Processing Controls
• Manual manipulation via OPC
• Write each individual element of the SBOw, Oper or Cancel structure
• Then write the BlockWrite bit to TRUE
• AX-S4 61850 Client will write the entire structure in single atomic action
• Automatic Control
• Enable AutomatedControl (enabled by default)
• Set the default orCat (default = 3: remote control)
• Upcoming Release of AX-S4 61850 (V7.1000) will include a graphic control

operator for interactive control operations that will capture and display
CmdTerm message data

Auto Control Settings


Setting Groups

Setting Groups
• Settings group is a logical element that is associated to all the
settings in all the logical nodes within a logical device.
• A setting group is referred to by a number 1….n where n is the

number of setting groups supported.
• IEC 61850 clients use setting group control blocks (SGCB) to access
and manipulate the settings.

Setting Group Control Blocks
• A SINGLE SGCB can be contained in LLN0 and used to:
– Select the Active Setting Group to Use

– Select a Setting Group to Edit
– Edit a Setting Group
• The access to the settings for all Logical Nodes with any SG or SE
functionally constrained data (primarily Pxxx and Rxxx LNs) in them
are controlled by this SGCB

SGCB Definition
SGCB class
Attribute name Attribute type r/w Value/value range/explanation M/O/C
SGCBName ObjectName -- Instance name of an instance of SGCB M
SGCBRef ObjectReference -- Path-name of an instance of SGCB M
NumOfSG INT8U r n = NumOfSG M
ActSG INT8U r Allowable range: 1 ... n M
EditSG INT8U r/w Allowable range: 0 ... n M
CnfEdit BOOLEAN w Confirm the edit M
LActTm TimeStamp r Time of last SelectActiveSG request M
ResvTms INT16U r # of seconds to reserve SBCB for a client O
since the last SelectEditSG
Services
SelectActiveSG
SelectEditSG
SetEditSGValue
ConfirmEditSGValues
GetEditSGValue
GetSGCBValues

Setting Group Control State Diagram
Initial values
SG exists
SelectActiveSG and has
values SelectEditSG
of another SG
(copy SG to edit buffer)
ConfirmEdit
SGValues
SG can be
SG is active SelectActiveSG
(copy SG to edited
active buffer)
GetSGValues (Read SG objects)

SetSGValues (Write SE objects)
GetSGValues (Read SE objects)
Setting Group Architecture

Setting Group Examples
• SelectActiveSG #2:
– Write LLN0.SP.sgcbName.ActSG = 2
• Change the setting for the starting value (StrVal) in PIOC and the
reset delay time (RsDlTmms) in PDIF for setting group #2
– Select different active setting group (SelectActiveSG)
• Write LLN0.SP.sgcbName.ActSG = 1
– Select setting group #2 for editing (SelectEditSG)
• Write LLN0.SP.sgcbName.EditSG = 2
– Change the settings (EditSGValues)
• Write PIOC.SE.StrVal.setMag.f = 1,255.44 (amps)
• Write PDIF.SE.RsDlTmms.setVal = 1000 (milliseconds)
– Confirm the editing (save the settings – via ConfirmEditSGValues)
• Write LLN0.SP.sgcbName.CnfEdit = 1
– Wait for settings to be saved (GetSGCBValues)
• Read LLN0.SP.sgcbName.CnfEdit (wait for =0)
– Select the new settings (SelectActiveSG)
• Write LLN0.SP.sgcbName.ActSG = 2


IED to IED Data Exchange
Multi-cast GOOSE Messaging

Directed Messaging (Client/Server)

Application Application Application
B C D
Server
Application
A

Multi-cast Messaging
Subscribing
Application
A B D
Network
B C
A B C D
Publishing Publishing Publishing

Device Device Device
Applications “subscribe” by listening for data sent TO a given multi-cast destination address

Multi-cast MAC Address
6-byte DESTINATION MAC Address
0 1 2 3 4 5
0 1 2 3 4 5 6 7
Example: 01-0C-CD-01-F1-04 = 1 - Multicast

Legacy Hardwired Architecture
Breaker
Relay 2
1 2
5
Breaker Relay 1 Relay 3 Breaker
6
4 3
Relay 4
Hardwired signals for
relay to relay links
Breaker

IEC61850 Network Architecture
Network Hub
GOOSE
Relay 1 Relay 2 Relay 3 Relay 4
Breaker Breaker Breaker Breaker
GOOSE - Generic Object Oriented Substation Event (data sets)

IEC 61850 GOOSE Network Performance Requirements
For Trip messages in transmission bays: < 3ms

< 3 ms
For Trip messages in distribution bays: < 10ms
Signal
Relay
Relay
Time
Sends
Data to Receives
Network Interface latency, Data from
I/F network access and Network I/F
transmission

Why 3ms?
• In the early 1970s ASEA introduced a high-speed auxiliary tripping relay (RXMS) with an
operating time of 4ms.
• Widely used to reduce trip times in substations since then.
• When GOOSE was vetted by protection engineers in the 1990s this criteria could be
accepted because it could justify the elimination of the need for these auxiliary tripping
relays.
• Therefore, the 3ms requirement was derived from the operating time of a circa 1970
relay.
• Hat Tip: John Tengdin, Opus Publishing

GOOSE - Generic Object Oriented Substation Event per 7-2
GOOSE message
Parameter name Parameter type Value/value range/explanation
DatSet ObjectReference Value from the instance of GoCB
GoID VISIBLE STRING129 Value from the instance of GoCB
GoCBRef ObjectReference Value from the instance of GoCB
T TimeStamp
StNum INT32U
SqNum INT32U
Edition 2 Simulation BOOLEAN (TRUE) simulation | (FALSE) real values

ConfRev INT32U Value from the instance of GoCB
NdsCom BOOLEAN Value from the instance of GoCB
GOOSEData [1..n]
Value (*) (*) type depends on the appropriate common data
classes (CDC).

Actual GOOSE Message per 8-1
Name Type
gocbRef GOOSE Control Block Reference
timeAllowedtoLive How long to wait for next message (ms)
datSet The name of the data set being sent
goID APPID of the sending GOOSE application (default: gocbRef)
T Time of state change
stNum State Number
sqNum Sequence Number
Simulation Simulated Data (true/false)
confRev Configuration Revision of the GOOSE Control Block (dataset config)
ndsCom Needs Commissioning (true/false)
numDatSetEntries Number of data set entries in the message
Data The data values of the data set in sequence.

GOOSE is Reliable Multicast
NON-EXISTENT
New State: 1.Sequence Number = 0

2.State Number++
3. Reset HoldTimer
RETRANSMIT-
PENDING
1. Hold Time Preset ++
2. Start Hold Timer HoldTime expired
3. Sequence Number ++
SEND
Message
TimeAllowedToLive (TAL) > Hold Timer

GOOSE Traffic
Each line below represents a GOOSE message
State = 1, Seq = 0 State = 2, Seq = 0

State = 1, Seq = 6
t
Event at t=0 Hold time increases from until
steady state of ~1/min is reached
State change occurs

Why Ethertype?
• Supports Virtual LAN (VLAN) processing by switches.
• VLAN enables intelligent 3-layer Ethernet switches to

prioritize packets via VLAN Priority.
• Enables high priority GOOSE packets to be forwarded sooner

than lower priority directed messages (SCADA).

GOOSE Control Block per 8-1
Component MMS r/w m/o Condition Comments
Name TypeDescription
GoEna Boolean rw m
GoID Visible-string r m
DatSet Visible-string r m The value of this component shall
be of the format of
ObjectReference and shall be
limited to VMD or domain scoped
NamedVariableLists
ConfRev Unsigned r m
NdsCom Boolean r m
DstAddress PHYCOMADDR r m
MinTime Unsigned r o As specified in the SCD file for the
GoCB
MaxTime Unsigned r o As specified in the SCD file for the
GoCB
FixedOffs Boolean r o As specified in the SCD file for the
GoCB
Component Name Data Type m/o Comments

Addr OCTET-STRING m Length is 6 Octets and contains the value of
the destination Media Access Control (MAC)
address to which the GOOSE message is to
be sent. The address shall be an Ethernet
address that has the multicast bit set TRUE.
PRIORITY Unsigned8 m Range of values shall be limited from 0 to 7.
VID Unsigned16 m Range of values shall be limited from 0 to
4 095.
APPID Unsigned16 m As defined in Annex C

GOOSE Subscription Supervision (LGOS)
LGOS class
Data objects
Status information
SbsNdsCom SPS Subscription needs commissioning O
SbsSt SPS Status of the subscription (True = active, False=not active) O
SbsSim SPS Subscription wih simulation O
LastStNum INS Last state number received O
ConfRevNum INS Expected Configuration revision number O
Settings
GoCBRef ORG Reference to the subscribed GOOSE control block O
Allows a client to determine if a server is

subscribed to a GoCB and if it is receiving data
Using AX-S4 GOOSE

GOOSE Features
• IEC 61850 Publisher and Subscriber (OPC Server DA V3.0 interface):
• Configuration of GOOSE control blocks via SCL (IEC 61850-6-1)
– Can represent single or several IEDs and GoCBs from SCL file
• Enable and disable GOOSE control blocks via OPC interactions
• Configurable retransmission curves
• Automated timestamp, quality, state, sequence number and time allowed to live
processing
• Writing changed data to AX-S4 GOOSE triggers outgoing GOOSE and increments state
number
• OPC items updated as GOOSE messages arrived
• High performance architecture provides reliable processing
• OPC DA V3.0 Server
• Support for R-GOOSE coming in V7.2000

5
508
GOOSE Application
GOOSE
GoCBs SCL File

Configure AX-S4 GOOSE

SISCO GOOSE Monitor

The Challenge of GOOSE
• IEC 61850 GOOSE Messaging uses multicast technology for station level
time-critical protection and automation messaging
• Each device is typically publishing multiple GOOSE control blocks and
subscribing to multiple GOOSE control blocks from other devices in the
substation
• In large substations there are many hundreds of publish-subscribe
relationships between devices
• With messages being transmitted as fast as 5-10 ms per message it can
be very difficult for the substation engineer to debug these systems using
traditional network monitoring or by monitoring a single device

511 © Copyright 2018 SISCO, Inc.
The GOOSE Monitor Solution
• The GOOSE Monitor is designed to provide an intuitive

visualization of the real-time GOOSE messaging
occurring on station bus that enables the engineer to
quickly identify what is working and what is not working
• Allows the engineer to cut through the complexity and

focus their attention on where the problems are

GOOSE Monitor Provides Answers
• Are GOOSE messages being published as expected?

• Are GOOSE messages being received by the IEDs as expected?
• Are their unexpected GOOSE messages on the network?
• What data is being published in each GOOSE message?
• Is the flow of GOOSE messages as expected?
• Are their simulated GOOSE messages on the network?

GOOSE Monitor Features
• Provides an intuitive and simplified view of network relationships and
GOOSE traffic status to help the engineer focus on what is important
• GOOSE configuration is automatically generated from SCD file:

– Graph diagram
• Nodes represent state of GOOSE subscriptions via LGOS
• Connections between nodes represent GOOSE messaging
– Addressing
– LGOS monitoring
• Beep Mode allows the engineer to follow the publisher and subscriber
relationships through the system to track down root causes of problems

GOOSE Screen Capture

Sampled Values
Process Bus
IEC61850-9-2

Sampled Values
• A method for transmitting sampled measurements from
transducers such as CTs, VTs, and digital I/O.
• Streaming of continuous measurements compared to event

messaging of GOOSE
• Enables sharing of I/O signals among IEDs
• Uses Multicast services (MSVC) over Ethernet (9-2)

IEC61850 Approach
Bay Protection Fault RTU,
Controller Relay Recorder etc.
Ethernet Ethernet Ethernet Ethernet
9-2 Process Bus
Ethernet
Merging Unit
A/D A/D Input
Voltages
Breaker
and
currents Status

Application of Process Bus
Breaker
Protection-1
Process Bus Switch

Merging Breaker
Unit Protection-2
Line
Merging Protection
Unit
Transformer
Protection
Test Set
Merging
Unit

IEC61850-9-2 Process Bus
• Transducer and I/O signals are shared via a network.
• Only one transducer or I/O point per signal.
• VERY LARGE Reduction in wiring costs

– 4 fibers per bus (2 per redundant pair) versus hundreds of copper wires per phase
• Minimization of calibration and maintenance.
• Incremental cost for additional signals is linear

– Pay to add a measurement once to a single Merging Unit
• CT/VT signals can be sent across long distances
• IEC 61869-9 is a new profile for applying IEC 61850-9-2 to instrument transformers
• Edition 1 profile was called 9-2LE (Limited Edition) published by the UCAIug (www.ucaiug.org)

SV Control Block (MSVCB) and Services Edition 1

SV Control Block (MSVCB)
MSVCB class
MsvCBName ObjectName - Instance name of an instance of MSVCB
MsvCBRef ObjectReference - Path-name of an instance of MSVCB
SvEna BOOLEAN r/w Enabled (TRUE) | disabled (FALSE), DEFAULT FALSE
MsvID VISIBLE STRING129 r/w
DatSet ObjectReference r/w
ConfRev INT32U r
SmpMod ENUMERATED r/w samples per nominal period (DEFAULT) | samples per
second | seconds per sample
SmpRate INT16U r/w (0..MAX)
OptFlds PACKED LIST r/w
refresh-time BOOLEAN
reserved BOOLEAN
sample-rate BOOLEAN
Edition 1 data-set-name BOOLEAN

DstAddress PHYCOMADDR r
Edition 2

What is a bus?
Bay Protection Fault RTU,
Controller Relay Recorder etc.
Ethernet Ethernet Ethernet Ethernet
9-2 Process Bus
Ethernet
Merging Unit
A/D A/D Input
Voltages
Breaker
and
currents Status

What is a Bus?
Ethernet
Merging Unit
A/D A/D Input
Voltages
and Breaker
currents Status

What is a Bus?
Process Bus
Ethernet
Merging Unit
A/D A/D Input
Voltages
and
Breaker
currents Status

New Development in Process Bus – point-to-point!?
Fiber Patch Panel

Fiber Optic Connector
Merging Unit or “brick”

A/D A/D Input
Voltages
and
Breaker
currents Status

Point-to-Point Process Bus – Controversy
• Some say 9-2 does not specify point-to-point links:
– Therefore this is NOT process bus!
• Existing implementations of this technology have some non-

interoperable “enhancements”
– Requires interaction with special GOOSE messages to trigger
MU
• Interesting idea even if it is not strictly 9-2 process bus.


Using the AX-S4 61850 Server

Server Features
• IEC 61850 Server functions:
• Configuration of IEC 61850 server via SCL (IEC 61850-6)
• Mapping of IEC 61850 objects to external OPC server for dynamic data.
• Fixed value initialization via SCL or mapping file for static data.
• Read/Write of any IEC 61850 Object
• Buffered and Unbuffered Reporting
• Controls (Direct and SBO via Normal Security)
• Full support for object discovery using ACSI services
• IEC 61850 file server functions
• OPC DA V3.0 Client
• IEC 62351 secure communications supported:
– TLS 1.2 for server level authentication and encryption
– X.509 Digital certificates for strong application level authentication.

Server

Example Mapping File: IEC 61850 gateway to Modbus Device
CTRL AlmGGIO1$ST$Beh$stVal KEPware.KEPServerEx.V4 Simulated.User.beh_stVal ReadOnlyDyn

CTRL AlmGGIO1$ST$Health$stVal KEPware.KEPServerEx.V4 Simulated.User.Health_stVal ReadOnlyDyn
CTRL AlmGGIO1$ST$SPCSO1$stVal SISCO.AXS4GOOSE.1 Local.SISCO_IED1CTRL/SPSCO1$stVal ReadWriteDyn
CTRL AlmGGIO1$CF$Mod$ctlModel KEPware.KEPServerEx.V4 Simulated.User.ctlModel ReadOnlyStatic
CTRL AlmGGIO1$CF$SPCSO1$ctlModel KEPware.KEPServerEx.V4 Simulated.User.ctlModel ReadOnlyStatic
CTRL AlmGGIO1$DC$NamPlt$vendor KEPware.KEPServerEx.V4 Simulated.User.vendorSISCO ReadOnlyStatic
CTRL AlmGGIO1$DC$NamPlt$swRev KEPware.KEPServerEx.V4 Simulated.User.swRev ReadOnlyStatic
CTRL AlmGGIO1$DC$NamPlt$d KEPware.KEPServerEx.V4 Simulated.User.namPltSISCO ReadOnlyStatic
CTRL AlmGGIO1$DC$NamPlt$configRev KEPware.KEPServerEx.V4 Simulated.User.configRev ReadOnlyStatic
CTRL AlmGGIO1$EX$NamPlt$lnNs dummy_opcserver dummy_opcitem ReadOnlyStatic IEC 61850-7-4:2003
CTRL MMXU1$MX$Hz$mag$f KEPware.KEPServerEx.V4 MODBUS.GEUR.HzMagf ReadOnlyDyn
CTRL MMXU1$MX$PhV$phsA$cVal$mag$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsA_V_Mag ReadOnlyDyn
CTRL MMXU1$MX$PhV$phsA$cVal$ang$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsA_V_Ang ReadOnlyDyn
CTRL MMXU1$MX$PhV$phsB$cVal$mag$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsB_V_Mag ReadOnlyDyn
CTRL MMXU1$MX$PhV$phsB$cVal$ang$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsB_V_Ang ReadOnlyDyn
CTRL MMXU1$MX$PhV$phsC$cVal$mag$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsC_V_Mag ReadOnlyDyn
CTRL MMXU1$MX$PhV$phsC$cVal$ang$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsC_V_Ang ReadOnlyDyn
CTRL MMXU1$MX$A$phsA$cVal$mag$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsA_A_Mag ReadOnlyDyn
CTRL MMXU1$MX$A$phsA$cVal$ang$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsA_A_Ang ReadOnlyDyn
CTRL MMXU1$MX$A$phsB$cVal$mag$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsB_A_Mag ReadOnlyDyn
CTRL MMXU1$MX$A$phsB$cVal$ang$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsB_A_Ang ReadOnlyDyn
CTRL MMXU1$MX$A$phsC$cVal$mag$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsC_A_Mag ReadOnlyDyn
CTRL MMXU1$MX$A$phsC$cVal$ang$f KEPware.KEPServerEx.V4 MODBUS.GEUR.PhsC_A_Ang ReadOnlyDyn
CTRL MMXU1$ST$Mod$stVal KEPware.KEPServerEx.V4 Simulated.User.mod_stVal ReadOnlyDyn
CTRL MMXU1$ST$Beh$stVal KEPware.KEPServerEx.V4 Simulated.User.beh_stVal ReadOnlyDyn

as an IEC 61850 Proxy
“Proxy Server”
IEC 61850 clients access the AX-S4 61850 proxy server

instead of individual devices. Enables multiple clients to
share a single application association to the device.
...
...

SCADA Protocol Gateway
SCADA Master
(protocol master)
May be needed to transform

incompatible data types (e.g.
double point status to/from
boolean, float to/from integer,
scaling, etc.) or control
processing
GOOSE
Client (if needed)

Data Concentrator
SCADA Master
(IEC 61850 Client)
Each device is
represented as a
separate Logical SCL Server
File
Device in the SCL
file
May be needed to transform

incompatible data types (e.g.
double point status to/from
boolean, float to/from integer,
scaling, etc.) or control
processing

to Expose OPC server data to IEC 61850 clients

IEC 61850 Device Simulator with GOOSE
GOOSE

Configuration Files
• Located here: C:\ProgramData\SISCO\AX-S4 61850\Server\Config
• Config Files (except for the SCL files) can be either comma delimited
(CSV) or tab delimited.
• Ralph’s advice for mapping files:
• Open the files using Excel and save a copy as an *.xlsx file, edit the xlsx file and
then save as tab delimited and rename to use in the actual server application
• Each time the AX-S4 61850 Server is run it generates a file named
opcmapout.cfg which contains a list of all the points that can be
mapped
• Once you can start the server without SCL errors, open the
opcmapout file using Excel and then save it using the file name you
are going to use for the mapping file. Then edit this file.
startup.cfg File
Entry in startup.cfg Default Value Description
SCLFileName AX-S4_61850_Server.iid IID, CID or SCD File containing the SCL description of the server
OPCMapFileName OPCMAP.CFG OPC Mapping File Used by Server
Defines the names of the OPC groups used in the mapping file and their update
IOClassFileName IOCLASS.CFG
rates and read/write setting
IEDName AXS4_61850 The name of the IED in the SCL file
MaxMmsPduLength 131072 Proposed Maximum MMS Message Size
MaxCallingConnections 0 Maximum calling connections
MaxCalledConnections 20 Maximum Called Connections
MaxCallingRequests 5 Maximum outstanding requested for calling TPAA
Maximum outstanding requested for called TPAA
MaxCalledRequests 5
AccessPointName Server The name of the Access Point in the SCL File
ReportScanRate 1 Internal scan rate for report generation
“Example IEC 61850 Server for
Capability 0 or more capability strings to be included in any GetCapabilityList request
AX-S4 61850”
“Can be used for data
Capability
concentrators and gateways”

Configuration Files
# This is the mapping file for the example IEC 61850 Server for the AX-S4 61850 Server
# Any line starting with the hash symbol is considered to be a comment line.
#Logical-Device IEC-61850-Attribute OPC-Server OPC-Item OPC-Group Initial-Value SISCO-Type SCL-Value #
AXS4_61850Device1 AlmGGIO1$ST$Mod$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 1 # Open this file using MS-Excel to view the data column aligned. Save it as tab delimited file using the name defined in the STARTUP.CFG file. OPCMAP.CFG by default.
AXS4_61850Device1 AlmGGIO1$ST$Health$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 1 # The GOOSE Control Block is mapped to AX-S4 GOOSE process. Import the IID file for the IEC 61850 server into AX-S4 GOOSE before running the AX-S4 61850 Server
AXS4_61850Device1 AlmGGIO1$ST$SPCSO1$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Bool 0 # An IEC 61850 Client will need to write the Enable bit of the GoCB to True to enable GOOSE outputs. Or an OPC client can access AX-S4 GOOSE directly to enable the GoCB.
AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$ctlVal dummy_opcserver dummy_opcitem dummy_ioclass type=Bool 0 #
AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$origin$orCat dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 0 # Logical-Device IEC-61850-Attribute OPC-Server OPC-Item OPC-Group Initial-Value SISCO-Type
AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$origin$orIdent dummy_opcserver dummy_opcitem dummy_ioclass type=OVstring64 AXS4_61850Device1 AlmGGIO1$ST$Mod$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 AlmGGIO1$ST$Health$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$ctlNum dummy_opcserver dummy_opcitem dummy_ioclass type=Ubyte 0
AXS4_61850Device1 AlmGGIO1$ST$SPCSO1$stVal SISCO.AXS4GOOSE.1 Local.AXS4_61850Device1/AlmGGIO1$ST$SPCSO1.stVal ReadOnlyDynamic type=Bool
AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$T dummy_opcserver dummy_opcitem dummy_ioclass type=Utctime
AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$ctlVal SISCO.AXS4GOOSE.1 Local.AXS4_61850Device1/AlmGGIO1$ST$SPCSO1.stVal ReadWriteStatic type=Bool
AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$Test dummy_opcserver dummy_opcitem dummy_ioclass type=Bool 0 AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$origin$orCat dummy_opcserver dummy_opcitem ReadWriteStatic type=Byte
AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$Check dummy_opcserver dummy_opcitem dummy_ioclass type=BVstring2 AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$origin$orIdent dummy_opcserver dummy_opcitem ReadWriteStatic type=OVstring64
AXS4_61850Device1 AlmGGIO1$CF$Mod$ctlModel dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 0 AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$ctlNum dummy_opcserver dummy_opcitem ReadWriteStatic type=Ubyte
AXS4_61850Device1 AlmGGIO1$CF$SPCSO1$ctlModel dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 1 AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$T dummy_opcserver dummy_opcitem ReadWriteStatic type=Utctime
AXS4_61850Device1 AlmGGIO1$DC$NamPlt$vendor dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 SISCO, Inc. AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$Test dummy_opcserver dummy_opcitem ReadWriteStatic type=Bool
AXS4_61850Device1 AlmGGIO1$DC$NamPlt$swRev dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 V7.0000 AXS4_61850Device1 AlmGGIO1$CO$SPCSO1$Oper$Check dummy_opcserver dummy_opcitem ReadWriteStatic type=BVstring2
AXS4_61850Device1 AlmGGIO1$DC$NamPlt$d dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 Demo GGIO to Trigger GOOSE Message AXS4_61850Device1 AlmGGIO1$CF$Mod$ctlModel dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 AlmGGIO1$CF$SPCSO1$ctlModel dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 AlmGGIO1$DC$SPCSO1$d dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 Control To Trigger GOOSE for SISCO Example Server
AXS4_61850Device1 AlmGGIO1$DC$NamPlt$vendor dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255
AXS4_61850Device1 LLN0$ST$Mod$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 1
AXS4_61850Device1 AlmGGIO1$DC$NamPlt$swRev dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255
AXS4_61850Device1 LLN0$ST$Health$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 1 AXS4_61850Device1 AlmGGIO1$DC$NamPlt$d dummy_opcserver dummy_opcitem ReadWriteStatic type=Vstring255
AXS4_61850Device1 LLN0$CF$Mod$ctlModel dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 0 AXS4_61850Device1 AlmGGIO1$DC$SPCSO1$d dummy_opcserver dummy_opcitem ReadWriteStatic type=Vstring255
AXS4_61850Device1 LLN0$DC$NamPlt$vendor dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 SISCO, Inc. AXS4_61850Device1 LLN0$ST$Mod$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 LLN0$DC$NamPlt$swRev dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 V7.0000 AXS4_61850Device1 LLN0$ST$Health$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 LLN0$DC$NamPlt$d dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 Example IEC 61850 Server to Illustrate Configuration of AX-S4 61850 Server AXS4_61850Device1 LLN0$CF$Mod$ctlModel dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 LLN0$DC$NamPlt$configRev dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 V7.0000 AXS4_61850Device1 LLN0$DC$NamPlt$vendor dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255
AXS4_61850Device1 LLN0$GO$goCB$GoEna dummy_opcserver dummy_opcitem dummy_ioclass type=Bool 0 AXS4_61850Device1 LLN0$DC$NamPlt$swRev dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255
AXS4_61850Device1 LLN0$GO$goCB$GoID dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring129 AXS4GOOSE AXS4_61850Device1 LLN0$DC$NamPlt$d dummy_opcserver dummy_opcitem ReadWriteStatic type=Vstring255
AXS4_61850Device1 LLN0$DC$NamPlt$configRev dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255
AXS4_61850Device1 LLN0$GO$goCB$DatSet dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring129 AXS4_61850Device1/LLN0$GOOSE_Dataset
AXS4_61850Device1 LLN0$GO$goCB$GoEna SISCO.AXS4GOOSE.1 Outgoing.AXS4_61850Device1/LLN0$GO$goCB.Enable ReadWriteDynamic type=Bool
AXS4_61850Device1 LLN0$GO$goCB$ConfRev dummy_opcserver dummy_opcitem dummy_ioclass type=Ulong 1
AXS4_61850Device1 LLN0$GO$goCB$GoID SISCO.AXS4GOOSE.1 Outgoing.AXS4_61850Device1/LLN0$GO$goCB.AppId ReadOnlyStatic type=Vstring129
AXS4_61850Device1 LLN0$GO$goCB$NdsCom dummy_opcserver dummy_opcitem dummy_ioclass type=Bool 0 AXS4_61850Device1 LLN0$GO$goCB$DatSet SISCO.AXS4GOOSE.1 Outgoing.AXS4_61850Device1/LLN0$GO$goCB.DatSet ReadOnlyStatic type=Vstring129
AXS4_61850Device1 LLN0$GO$goCB$DstAddress$Addr dummy_opcserver dummy_opcitem dummy_ioclass type=Ostring6 01 0c cd 11 22 33 AXS4_61850Device1 LLN0$GO$goCB$ConfRev SISCO.AXS4GOOSE.1 Outgoing.AXS4_61850Device1/LLN0$GO$goCB.ConfRev ReadOnlyStatic type=Ulong
AXS4_61850Device1 LLN0$GO$goCB$DstAddress$PRIORITY dummy_opcserver dummy_opcitem dummy_ioclass type=Ubyte 4 AXS4_61850Device1 LLN0$GO$goCB$NdsCom SISCO.AXS4GOOSE.1 Outgoing.AXS4_61850Device1/LLN0$GO$goCB.NdsCom ReadOnlyStatic type=Bool
AXS4_61850Device1 LLN0$GO$goCB$DstAddress$VID dummy_opcserver dummy_opcitem dummy_ioclass type=Ushort 1 AXS4_61850Device1 LLN0$GO$goCB$DstAddress$Addr SISCO.AXS4GOOSE.1 Outgoing.AXS4_61850Device1/LLN0$GO$goCB.DstAddressReadOnlyStatic type=Ostring6
AXS4_61850Device1 LLN0$GO$goCB$DstAddress$APPID dummy_opcserver dummy_opcitem dummy_ioclass type=Ushort 4097 AXS4_61850Device1 LLN0$GO$goCB$DstAddress$PRIORITY dummy_opcserver dummy_opcitem dummy_ioclass type=Ubyte
AXS4_61850Device1 LLN0$GO$goCB$MinTime dummy_opcserver dummy_opcitem dummy_ioclass type=Ushort 1 AXS4_61850Device1 LLN0$GO$goCB$DstAddress$VID dummy_opcserver dummy_opcitem dummy_ioclass type=Ushort
AXS4_61850Device1 LLN0$GO$goCB$MaxTime dummy_opcserver dummy_opcitem dummy_ioclass type=Ushort 1000 AXS4_61850Device1 LLN0$GO$goCB$DstAddress$APPID dummy_opcserver dummy_opcitem dummy_ioclass type=Ushort
AXS4_61850Device1 LLN0$GO$goCB$FixedOffs dummy_opcserver dummy_opcitem dummy_ioclass type=Bool 0 AXS4_61850Device1 LLN0$GO$goCB$MinTime dummy_opcserver dummy_opcitem dummy_ioclass type=Ushort
AXS4_61850Device1 LLN0$GO$goCB$MaxTime dummy_opcserver dummy_opcitem dummy_ioclass type=Ushort
AXS4_61850Device1 LLN0$EX$NamPlt$ldNs dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 IEC 61850-7-4:2010
AXS4_61850Device1 LLN0$GO$goCB$FixedOffs dummy_opcserver dummy_opcitem dummy_ioclass type=Bool
AXS4_61850Device1 LPHD1$ST$PhyHealth$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Long 1
AXS4_61850Device1 LLN0$EX$NamPlt$ldNs dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255
AXS4_61850Device1 LPHD1$ST$Proxy$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Bool 0 AXS4_61850Device1 LPHD1$ST$PhyHealth$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Long
AXS4_61850Device1 LPHD1$DC$PhyNam$vendor dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 AXS4_61850Device1 LPHD1$ST$Proxy$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Bool
AXS4_61850Device1 LPHD1$DC$PhyNam$model dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 AXS4_61850Device1 LPHD1$DC$PhyNam$vendor dummy_opcserver dummy_opcitem dummy_ioclass SISCO, Inc. type=Vstring255
AXS4_61850Device1 LPHD1$DC$PhyNam$location dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 AXS4_61850Device1 LPHD1$DC$PhyNam$model dummy_opcserver dummy_opcitem dummy_ioclass AXS4-61850-142-095-XXXtype=Vstring255
AXS4_61850Device1 MMXU1$MX$Hz$mag$f dummy_opcserver dummy_opcitem dummy_ioclass type=Float 0 AXS4_61850Device1 LPHD1$DC$PhyNam$location dummy_opcserver dummy_opcitem ReadWriteStatic Customer Computer type=Vstring255
AXS4_61850Device1 MMXU1$MX$PhV$phsA$cVal$mag$f dummy_opcserver dummy_opcitem dummy_ioclass type=Float 0 AXS4_61850Device1 MMXU1$MX$Hz$mag$f OPCSample.OpcDa20Server.1 Dynamic/Analog Types/Hz ReadOnlyDynamic type=Float
AXS4_61850Device1 MMXU1$MX$PhV$phsB$cVal$mag$f dummy_opcserver dummy_opcitem dummy_ioclass type=Float 0 AXS4_61850Device1 MMXU1$MX$PhV$phsA$cVal$mag$f OPCSample.OpcDa20Server.1 Dynamic/Analog Types/PhsA ReadOnlyDynamic type=Float
AXS4_61850Device1 MMXU1$MX$PhV$phsC$cVal$mag$f dummy_opcserver dummy_opcitem dummy_ioclass type=Float 0 AXS4_61850Device1 MMXU1$MX$PhV$phsB$cVal$mag$f OPCSample.OpcDa20Server.1 Dynamic/Analog Types/PhsB ReadOnlyDynamic type=Float
AXS4_61850Device1 MMXU1$MX$PhV$phsC$cVal$mag$f OPCSample.OpcDa20Server.1 Dynamic/Analog Types/PhsB ReadOnlyDynamic type=Float
AXS4_61850Device1 MMXU1$ST$Mod$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 1
AXS4_61850Device1 MMXU1$ST$Mod$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 MMXU1$ST$Health$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 1
AXS4_61850Device1 MMXU1$ST$Health$stVal dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 MMXU1$CF$Mod$ctlModel dummy_opcserver dummy_opcitem dummy_ioclass type=Byte 0 AXS4_61850Device1 MMXU1$CF$Mod$ctlModel dummy_opcserver dummy_opcitem dummy_ioclass type=Byte
AXS4_61850Device1 MMXU1$DC$NamPlt$vendor dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 SISCO, Inc. AXS4_61850Device1 MMXU1$DC$NamPlt$vendor dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255
AXS4_61850Device1 MMXU1$DC$NamPlt$swRev dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 V7.0000 AXS4_61850Device1 MMXU1$DC$NamPlt$swRev dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255
AXS4_61850Device1 MMXU1$DC$NamPlt$d dummy_opcserver dummy_opcitem dummy_ioclass type=Vstring255 SISCO Example IED using AX-S4 61850 Server AXS4_61850Device1 MMXU1$DC$NamPlt$d dummy_opcserver dummy_opcitem ReadWriteStatic type=Vstring255


IEC 61850 Security

General Security Concerns
• Appropriate access to information
• Restriction of control and configuration ability.
• Communication Access Control
• Confidentiality
• Others?

The IEC 62351 Specifications
• IEC 62351-1 Introduction and Overview
• IEC 62351-2 Glossary
• IEC 62351-3 TCP/IP Profile
– How to use TLS
• IEC 62351-4 Security for MMS based profiles
– Includes ICCP-TASE.2 annex)
– References 62351-3
• IEC 62351-5 Security for IEC 60870-5 and derivatives (DNP3)
• IEC 62351-6 Security for 61850
– References 62351-4
• IEC 62351-7 Mgmt Info. Base (MIB) for end-to-end net. Mgmt.
• IEC 62351-8 Role Based Access Control
• IEC 62351-9 Key Management

IEC 62351 – Data and Communications Security
• IEC 62351 specifies only how to use technology to implement
security for TC57 protocols.
• It does not (yet) specify when to use authentication to implement

role-based access control
• This and other issues should be addressed in other standards (e.g.

ISA S99, government regulations, etc.)

Profiles of concern
ACSE SMV GOOSE
Application MMS (ISO/IEC 9506)
ISO Presentation (ISO 9576)
Presentation ASN.1 (ISO/IEC 8824/8825)
Session ISO Session (ISO 8327)
ISO Transport (ISO/IEC 8073)

Transport Class 0
Transport
RFC 1006
TCP (RFC 793)

IP (RFC 791)
Network ARP (RFC 826)
Logical Link Control (ISO 8802), 802-3 Ethertype
Data Link Media Access Control (ISO 8803)

Security Tools
• Encryption
– Encrypting data so that only the 2 communicating entities are able to
understand the data.
• Authentication
– Using digital signatures to ensure that the entity at the other end is
known and trusted.

Security Technologies Used
• Public/Private Key Encryption

– Transport Layer Security (TLS)
– Needed for Confidentiality
• Digital Signatures
– Needed to verify authenticity of identification
• X.509 Digital Certificate Technology

– Public / Private Key

Profile Capabilities impact security choices
SMV GOOSE MMS
X.509 Certs
(Identity) – –
Encryption
(confidentiality) – –
Tamper
Detection

Public Key Encryption
NODE A NODE B
Data Data
Node B Encrypt Decrypt Node B

Public Key Private Key
Encrypted Encrypted
Data Data

Digital Signatures
NODE A NODE B
Data Don’t Use
Data
Create N
Digest Signature Y OK to
OK? Use Data
Node A Encrypt
Node A
Private Key Digest
Public Key
Data + Data +
Signature Signature

Typical Solutions
Can be confused
Identity
Establishment
Authentication
Encryption Access
(Confidentiality) Control

What is a Digital Certificate?
• A digital certificate is a standardized file format that can be exchanged

with communications partners that identifies an entity and contains:
– A public key for encrypting data that can only be decrypted by

the private key
– A unique serial number assigned by the certificate authority
– Certificate Authority Signature of the Certificate and algorithm
used
– The name of the certificate authority
– Version of the certificate
– Validity dates
– Certificate thumbprint/digest and algorithm used
– usage, etc.
– A private key is included for your own certificate that you install
on your own machine. You do not distribute certificates with
private keys to others
What is a Certificate Authority?
• A certificate authority is an entity that issues certificates.
• There is a digital certificate for the CA that includes all the usual certificate information
including the CA’s public key
• TRUST is a critical element of the CA:

– Accepting a CA certificate means that you trust them to verify that the information
in certificates issued by them is valid
– A trusted CA is the start of a “chain of trust” (other CA certificates can be
authenticated based on another trusted
• Don’t install certificates from CAs into your system you don’t trust

Use of Certificate Authority
• Calculate Digest/thumbprint/fingerprint of the digital certificate
• Compare this to the signature generated by the certificate authority
• If they MATCH AND you trust the CA: the certificate was issued to the
entity identified in the certificate by that CA and the public key can be
trusted
• If they DON’T MATCH: then something is wrong and you can’t trust the
certificate or any information in it including the public key.

Certificate Authorities
• Verisign
• Thawte
• Certisign
• Deutche Telecom
• EquiFax
• ANYONE can be a CA
• Important to Utilities
– Power Pools
– ISOs
– RTOs
– Your own company

Secure Profile for IEC 61850 (and ICCP-TASE.2)
ACSE (ISO/IEC 8650) + ACSEACSE Authentication
Authentication Definitions
Application MMS (ISO/IEC 9506) IEC 62351-4
ISO Presentation (ISO 9576)

Presentation ASN.1 (ISO/IEC 8824/8825)
Session ISO Session (ISO 8327)
ISO Transport (ISO/IEC 8073)

Transport Class 0
Transport RFC 1006

SSL/TLS IEC 62351-3
TCP (RFC 793)

IP (RFC 791)
Network
ARP (RFC 826)
Logical Link Control (ISO 8802)
Data Link Media Access Control (ISO 8803)

Specification Theory
• TLS is used to supply encryption and node authentication.

– Authenticates the identity of the computer running the transport stack, not the applications
accessing that stack.
• ACSE is used for Application Authentication.

– Authenticates individual applications residing on a given computer.

Different Modes Need to be supported
Application
TLS Encryption Use
Authentication
Backward Compatible with

None None
current implementations
For use over VPN

None Yes connections or internal to
control centers
Provides encryption and
Yes None node level authentication
only.
Yes Yes Full security

TLS Encryption
• Asymmetrical Public Key exchange based on 1024 or 2048 bit keys are used to
negotiate a secure encrypted connection at the transport level
• After TLS session establishment a symmetrical key (both sides use the same
encryption key) of a smaller size (256 bits) is then exchanged for continuing
communications in order to minimize processing overhead

Symmetrical Key Renegotiation
• Maximum of every 5,000 packets (configurable).

• 10 minute time limit (configurable)
• Entity that was connected to (called) responsible for
key negotiation.
• Avoids protocol deadlocking.
• Eliminates possibility of long-term eavesdropping to

break the weaker symmetrical keys.

TLS Cipher Suite
• OpenSSL from http://www.openssl.org
• Many suites are available in OpenSSL
• Picked a single suite as mandatory to enable interoperability:

– TLS_DH_DSS_WITH_AES_256_SHA (Ed.1)
– TLS_DH_DSS_WITH_AES_256_SHA256 (Ed.2)
• Several don’t encrypt and are deprecated
• TLS 1.2 is used. Previous TLS versions are deprecated in the latest specs.

CPU Performance Impact of Encryption (2008)
TLS 1.0 Suite System A System B
None 0.425 0.537
AES 256 0.577 (+35%) 0.758 (+41%)
3DES 0.708 (+66%) 0.931 (+73%)
DES 0.597 (+40%) 0.884 (+65%)
Not a significant impact on network bandwidth requirements

Impact of Application Authentication
• Application Authentication only takes place during association establishment.
• IEC 61850 consists of long-lived associations

– Infrequent application association initiation
• No significant impact on application perfromance or bandwidth for application

authentication.
• Minimal impact on application association initiation processing.

GOOSE and SV are special
• Security may/may not be needed in small local networks
• Encryption overhead may require hardware solution to meet

performance requirements
• Implementations of secure and non-secure (authenticated) PDUs need

to be interoperable
• Becomes a subscriber’s configuration issue if to expect/require security

Layer 2 GOOSE and SV security specified in IEC 62351-6
R-GOOSE
Layer 2
GOOSE
If non-encrypted can be processed by non-secure nodes

Why new end-to-end?
• Strong authentication mechanism counts on TLS to provide per packet message
authentication. New authentication scheme could be used without TLS (e.g. over a
LAN-to-LAN VPN, etc.)
• Concern over TLS tunnels being broken at gateways and other relay mechanisms.
– IEC 61850-8-2 uses XMPP to distribute messages.
– TLS tunnel effective only between the XMPP client and XMPP server.
– XMPP server represents a potential for confidentiality protection to be broken
(acts as Man-in-the-Middle).
• Some smart grid standards are beginning to mandate it (lack of trust of TLS
intermediaries) .

End-to-End for Client/Server
Application Layer
Application Layer Payload
Payload
IP TCP Clear- Authen

Header ACSE
Header MMS Message
token ticator
▪ Enhancement of existing A-Profile

▪ “A+” -Profile targeting end-to-end authentication and message integrity as Authentication and Integrity
well as session binding to initial authentication

Confidentiality
▪ “AE+” Profile targeting the A+ Profile in combination with encryption
Authentication and Integrity
(session binding to initial authentication)
▪ Cleartoken in general contains necessary information to establish and maintain the security session. In conjunction with
the authenticator, it is used to achieve message integrity
▪ Profile or originator token neglected due to limited security (would provide a self contained end-to-end token but the
binding to the actual message containing the token cannot be ensured)
▪ Session key renegotiation periodicity being determined.

Configuring Security for AX-S4 61850

AX-S4 61850 Security Extensions
• Incorporates Support for IEC 62351-4 to provide
• Application level authentication using digital certificates
• Transport Layer Security (TLS) for encryption
• 1024/2048 bit asymmetrical keys for authentication and connection establishment and 256-bit
symmetrical keys for encryption
• Encryption is periodically rekeyed to eliminate brute force breaking of encryption
• Connect requests are time stamped and signed to avoid playback and spoofing
• Supports simultaneous use with or without security functions on a link by link basis
• Security extensions are included with AX-S4 61850 at no additional cost
• Supports both AX-S4 61850 Client and AX-S4 61850 Server
• AX-S4 61850 Security Extensions are subject to governmental export restrictions

AX-S4 61850 Security Extensions

Enable AX-S4 61850 for Secure Operation
Security is off by default
1. Run AX-S4 61850 Explorer
2. Select “Tools|Start Security Configuration Utility”
3. Enable security functions under SNAP and Common Application Security Settings
4. Exit Security Configuration Utility
5. Run Microsoft Management Console: mmc.exe using the Run dialog
6. Select “File|Add/Remove Snap In”
7. Select “Certificates” for the Computer Account on the local computer
8. Import any Root CA certs into your Trusted Root CA store
9. Import any remote device certifications into the SISCO Certificate store
10. Exit the Certificate Console

Configure AX-S4 61850 Security Functions
1. Start the Security Configuration Utility
2. Select the Root CAs that will be used for IEC 61850
3. To not use individual certificates and authenticate on TLS only using any
cert signed by a trusted Root CA:
– Uncheck Remote Certificates Required under SSL Settings
4. Configure certificates for remotes that will use MMS Authentication
Certificate Extensions (MACE – application authentication)
5. Once security is enabled you must configure some form of AE Title
matching for the AX-S4 61850 Server. It will no longer accept un-
identified requests to establish a TPAA.

Security Configuration Utility

Role Based Access Control
IEC 62351-8

Pre-Defined Roles and Permissions for IEC 61850
SETTINGGROUP
Permission

LISTOBJECTS
READVALUES
REPORTING
FILEWRITE
FILEMNGT
SECURITY
FILEREAD
CONTROL
DATASET
Value
CONFIG
Role
<0> VIEW ER X C X C
<1> OPERATOR X X X X
<2> ENGINEER X X X X X X X
<3> INSTALLER X X X X X
<4> SECADM X X X X X X X X X
<5> SECAUD X X X X
<6> RBACMNT X X X X X
<7…32767> Reserved For future use of IEC defined roles.
<-32768 .. -1> Private Defined by external agreement. Not guaranteed to be interoperable.
c= Conditional read access, clarification of specific data objects may be necessary (e.g., VIEW ER may
not access security settings, but process values)

Roles, Rights, and Operations

PUSH Model for RBAC Authentication

PULL Model for RBAC Authentication


Wide Area Use of GOOSE and Sampled Values
IEC TR 61850-90-5

Use cases documented in 90-5
• WAMS - Wide Area Measurement Systems
• Situational Awareness using Synchrophasors
• State Estimation and on-line security assessment
• Archival of information
• WAMPAC - Wide Area Protection and Control

• Special protection schemes (SPS) between substations and large areas
• Predictive Dynamic Stability
• Phenomenon assumption WAMPAC

Use cases documented in 90-5
• “regional”/local related
– Out-of-step (OOS) protection
– Adaptive relaying
– Synchro-check
– Under-voltage shedding
• NASPINET
• PDC use case to be added.

NASPInet - Requirements
IP multicast to address large scale of NASPInet.

To meet the use cases:
• Services explicitly specified in IEC TR 61850-90-5
– GOOSE for PAC use cases (protection and control)
– SV for measurement use cases (Synchrophasors)
• Profile supports IP Multicast

Comparison of C37.118.2, 61850, and 61850-90-5

IEC TR 61850-90-5 has several different profiles
Security Key Multicast Data Transfer

Management Route
Key Distribution Determination
Center (KDC)

Group Domain of Interpretation (GDOI): Phase 1
• Utilizes client certificate exchange to establish identity
• Asymetric keys are used to establish a secure path betweeen 2

nodes for exchange of symmetric key information.
• Symmetric keys used to encrypt TCP/IP packets.
• Similar to how TLS is used for ICCP-TASE.2

GDOI Phase 2
• Once access to the KDC is authenticated, subscriber requests

a policy for a security association (SA) to an IED:
– Type of communications (GOOSE or SV)
– Data Set being transmitted

GDOI Phase 3
• Assuming the client is authorized to access, the KDC responds with GDOI
Security Association Payload (SA):
– The Current Key Encrypting Key (KEK) in use by the PMU/PDC
• KEK is a symmetric key used to authenticate data received by the client that is in current use by
the PMU/PDC
– Next KEK that is to be used
– Time remaining on current KEK
• Client receives the IEC 61850-90-5 payloads separately using IP Multicast and
authenticates using the KEK.
– Must occassionaly reinstate GDOI phases to keep keys up to date.

IEC TR 61850-90-5
Session Protocol

IEC TR 61850-90-5
Session Protocol
Functional:
Encapsulation of
GOOSE (Events)
Sampled Values (Streaming)
Tunneling of Ethernet Frames

IEC 61850-90-5
Session Protocol
Security
Security: Secure HMAC

Hash Based Message Authentication Code
Tamper Detection
Authentication and Identity Establishment

IEC TR 61850-90-5
Session Protocol
Security: Encryption
Confidentiality

IEC TR 61850-90-5
Session Protocol
Security: Key Management

“Perfect” Forward Security
Provides current and next keys to be

used for decryption
Obtained from the KDC

IEC TR 61850-90-5
Session Protocol
Security:
Replay Protection
Out of Domain (OOD) Detection

Why UDP Multicast? Engineering for UDP
• Allows large number of

subscribers to receive data from
a single IED with minimal packet
duplication.
• Minimizes the need for PDCs in

a deployment architecture.
• A couple of issues:
– Engineering for UDP
– How to prevent multicast
from going everywhere.

Free range IP multicast: IGMPv3
IGMPv2
DEST 1 Filters on destination only
WAN
DEST 2
IGMPv3
DEST 1 Filters on destination &
WAN source address
Makes sure routers can

determine a consistent
and optimum path
DEST 2

IEC TR 61850-90-5 Status
• IEC Documents published in 2012
• NERC formally acknowledged the importance of the use of 90-5 to goals for WAMS and
congratulated the IEC on the speed of the effort
• Open source available via the UCAIug web site:

– http://iec61850.ucaiug.org/90-5/default.aspx
• Commercial products coming
• IEC TR 61850-90-5 will be merged into Ed 2.1 standards

– Session Protocol will go into IEC 61850-8-1
– SCL extensions into IEC 61850-6
– Security into IEC 62351-6

To Summarize: IEC TR 61850-90-5
• Allows for eventing (control) and streaming of data (synchrophasor and other) and delivery of “late” data.
• Security is baked in
– Authentication
– Confidentiality
– Key management
• Multicast with UDP

– IGMPv3 solves “free ranging” multicast issue
– Differentiated Services Code Point (DSCP) provides coarse-grained, class-based mechanism for implement
quality of service (QOS) traffic management
• Provides SCL based configuration capability
• Uses existing mainstream IP technology mostly already widely in use

Application of R-GOOSE for Wide Area Protection
Centralized Remedial Action System (C-RAS) at SCE

Why C-RAS?
• Long lines separating load and
generation need protection.
• Increasing reserve margins to
protect lines reduces available
energy.
– More transmission capacity in the
same corridor is subject to the same
contingencies and results in
increasing reserve margins.
• Maintaining system stability during
anomalous conditions challenges
operators to respond quickly to
prevent cascade failure

Individual Remedial Action Schemes and Special Protection Systems (RAS/SPS)
• Protects lines from

damage during anomalous
conditions.
• Individual RAS are

available using traditional
approaches involving
hardwired devices within
local areas.

Multiple Individual RAS
• Deploying multiple
individual RAS practical
because little interaction
between RAS.
• Difficult to maintain and

update as number of RAS
increases.

Integration of Multiple Individual RAS into a Distributed RAS
• Addressing system stability

requires integration of multiple
RAS over a wide area.
• Information sharing and

interactions between individual
RAS using traditional techniques
increases complexity and cost
beyond what is practical.

Centralized Remedial Action Systems (C-RAS)
• Centralized control reduces complexity of information sharing making implementation feasible.
• Centralization of control requires a network architecture to support very reliable high speed
communications of events and controls
Control Center
Backup Control Center

Unified Analytic Platform (UAP)
The UAP was specifically

designed to meet the
requirements of implementing
Special Protection Systems for
wide area protection
applications based on a
Centralized Remedial Action
Systems (C-RAS) architecture

C-RAS Controller Requirements
• High Performance and Low Latency: • Testability
– Analytic and control processing – Simulation of data and monitoring of
– Communications in and out test actions
– External system interfaces – Playback of previously encountered
• Traceability for all communications and scenarios
control actions • Repeatability
• Controllability – Control actions must be consistent and
– Enabling/disabling analytics based on
predictable under minor variations
contingencies determined by EMS • Redundancy and Resiliency for all
– Modifying control actions based on system components
conditions (e.g. load shed levels) – Three Dual-Redundant controllers for
• GOOSE Input conditioning application in redundant control centers
– Eliminating bad data from analytic – Simple voting mechanism in mitigation
processing substations
– Virtualizing IED signal processing

UAP Components Analytic
Application
Analytic
Application EMS
1 N
Arm/Disarm Status &
• GOOSE/R-GOOSE Interface with Analytics Events
Input Conditioner
Data EMS Interface
• EMS System Interface (ESI) Data Exchange,
Exchange Mappings,
• Commands (arm/disarm) and data from EMS Monitor And Control Historian
• Sends C-RAS data for operator displays
Event
• Historian Interface Event Simulation Playback
• Scenario Player High-Speed Scenario

IEC GOOSE
• Plays back previously recorded data Interface
Player
• GOOSE Blaster
• Enables complex GOOSE sequences to be
simulated
Secure Corporate WAN
• Monitor System Simulation
• Monitors data exchange between
components
• Analytics Substations Substations
609
UAP Data Modeling
• Management of system configuration and interaction between systems requires a common data model for
data exchange
– Without common data model each system’s understanding of the power system relationships of data could be
different.
– Performing critical control operations on the power system requires absolute certainty of the operations…ambiguity is
not allowed
• CIM is used for high-level power system models

– Existing EMS mapping with CIM already established
– CIM power system model (IEC 61970-301 and -452 (CPSM))
• IEC 61850 is used for IED modeling

– Measurement and status naming
– Configured IED Description (CID) files for GOOSE subscriptions
• Extensions to integrate these models into a “Master Model” used by the C-RAS central controllers

CIM Extensions
UAP Use of CIM
• IEC 61970-452 profile used for
power system modeling
• Extensions for modeling of:

– Contingencies
– Mitigations
– RAS Analytics
– IEDs

Configuration Flow UAP Development
61850 Devices Controller Master Model Schema
(RDFS)
EMS
Services allowed file
(gi, alert, subst, control)
CIM XML
(instances) CIM RAS Analytics
IEC 61850 Gen Contingencies (from
SCL File
Extended CIM planning)
XML used for
EMS messaging
Input
and operator Processor
displays Configuration

IED are Virtualized and Composited
Must be operated as one Used for
Process Real
Composite Virtual Physical
CIM IEC
C A1 61850
o Virtual
m
p B1
o
s
i
t
A2
e
Virtual
B2
A3
Virtual
B3

RAS and Contingencies
Commands and
data from EMS
via Web Service
Interface
Contingency1 – (n-1)
Process data Logic &
Outputs
from Input Monitoring
Conditioner
From Planning Systems

Unified Analytic Platform (UAP)
• Off-the-shelf components delivered

as part of a complete solution
• Built and maintained on-site using
customer configuration mgmt.
• Some components are available
separately as stand-alone products:
– GOOSE Blaster
– R-GOOSE Gateway

GOOSE Blaster
• Simulates GOOSE and R-GOOSE
messaging
• Capable of supporting large scale
simulations of many devices
including
– Critical state changes
– Out of sequence and missing
message scenarios
– Good/bad quality/timestamps
– Many realistic and anomalous
conditions can be simulated

GOOSE Blaster Scenario Editor

R-GOOSE Gateway
• Translates Ethernet Multicast
GOOSE messaging to/from IP
Multicast GOOSE (R-GOOSE)
with minimal latency
• Configures with SCL and

autogenerates the necessary
GoCB and RgCBs needed on
either end of the gateway
SCE Architecture EMS Web Service Interface Using CIM
Backup
Control Center Control Center
IEC 61850 GOOSE

SISCO UAP

SCE Architecture EMS Web Service Interface Using CIM
50 ms
Round Trip
Fault to Backup
Control Center Control Center
Mitigation
4 ms RAS
processing
IEC 61850 GOOSE Time
SISCO UAP

Redundancy
• 3 dual-redundant C-RAS controllers in primary and backup

control centers
• Dual redundant monitoring and mitigation relays in
substations
• Mitigation relays implement a voting mechanism
– 2 of 3 UAPs from either primary or backup must agree on
control action for mitigation to take place

Project Implementation
• Project started early 2012
• Planning and design with SISCO, GE and CISCO
• Integration pre-test phase
• Verifying EMS System Interface (ESI), network design, C-RAS controller (UAP)
implementation
• FAT at GE
• SAT1, SAT2 and SAT3 at SCE
• Unstructured testing between SAT2 and SAT3 including a fully
simulated transmission system test using RTDS
• Final acceptance late 2014

Project Scope
• Up to 120 Substations
• 932 IEDs (466 on A and B each)
• 2 GOOSE Control Blocks per IED (high and low priority)
• 1,864 GOOSE DataSets processed per UAP
• 43 different items/IED sent (80,152 per UAP)
• Each UAP processes both A and B system GOOSE messages
• Each UAP produces approximately 150K GOOSE messages

GOOSE Performance

EMS System Interface (ESI)
• 150K-200K values per UAP pair

• C-RAS presents visualization challenges for operators
– Configuration and displays are automatically generated
based upon harmonized CIM instance file.

Project Completion
• Final acceptance in 2014
• Auto-configuration generation for RAS implemented by SISCO
after acceptance
• VLAN configuration was challenging
– Concerns about maintaining as # of RAS proliferate
– Emerging routable GOOSE (R-GOOSE) technology based on
IEC 61850-90-5

GOOSE to R-GOOSE
• GOOSE is a 3 layer protocol with GOOSE message sent directly in an
Ethernet IEEE 802.1Q packet with VLAN and priority tagging to a
multicast Ethernet address
• R-GOOSE is a 4 layer protocol with GOOSE messages sent over
UDP/IP to a multicast IP Address using:
• Differentiated Services Code Point (DSCP) to provide prioritization of message
forwarding
• Internet Group Management Protocol V3 (IGMPv3) to provide source and
destination IP filtering
• More scalable than VLAN: Routers determine an optimized and
consistent routing path using IGMPv3

C-RAS Migration to R-GOOSE
• Migrate existing system and RAS to R-GOOSE in preparation

for large-scale deployment
• Project begun in 2017
• In process. SAT3 to start this summer

IEC61850 Migration

Why is Migration Important?
• IEC 61850 delivers significant benefits:
• Drastically reduced setup/configuration
• Standardized naming and configuration
• More standardized functions (less custom)
• Higher performance
• Without migration, benefits are only available for new

systems.
• Missed opportunity for cost and performance improvements

Replace Existing Equipment
• New construction
• System replacements
• What about system expansions or upgrades?

• Some new equipment but still need to leverage existing equipment while
preserving benefits of IEC61850

Migration Strategy
• Data Concentrators/Gateways
– Preserve existing equipment
– “Wrap” the legacy protocol with IEC61850 to hide the
primitive protocols.
– Isolates the limitations of the legacy systems to enable the
benefits of IEC61850
• IEC 61850 is designed specifically to support these concepts.

Logical Device Structure
WAN to
IEC61850 Clients Control
Center

Client
Functions
Logical Logical
Device 1 to N Logical Devices Device
Logical
Node
... Logical
Node
Logical
Node
... Logical
Node
Data … Data Data … Data Data … Data Data … Data
Process Bus

Example Project – Current
Phone
Network
Control Center
Existing automation for
existing feeders
RTU
IED
IED
Modem
I/O

Example Project – New
WAN
Control Center
New
Router/
automation Firewall
for
expansion Station Bus
Process Bus

Example Project – Migrated
WAN
Control Center
New
automation Router/
for Firewall existing feeders
expansion
RTU
Station Bus
LD IED
Process Bus
LD IED
LD
I/O
Data Concentrator

Example Project – Integrated
WAN
Control Center
New Existing automation for
Router/
automation Firewall existing feeders
for
expansion Station Bus
IED
Logical Device
Process Bus
Logical Device IED
Logical Device I/O
Eliminates maintenance and

Data Concentrator configuration of separate RTUs

Example Project – Equip. Replacement
WAN
Control Center
New
automation Router/
for Firewall existing feeders
expansion
Station Bus
Process Bus
Logical Device IED
Logical Device
I/O
Equipment Replacement Has Minimal

Impact on Existing Systems

Benefits of Migration
• Eliminates legacy IED and protocol dependencies from applications
reducing configuration and maintenance cost.
• Common network infrastructure for both
• Legacy equipment can be replaced with minimal application impact.
• Manual configuration (mapping) of points only needed for legacy systems.

Testing
Interoperability and Conformance

The Ultimate Goal of Testing:
Everything works as expected when systems are deployed

in the field
PROJECT SUCCESS

Interoperability
• Testing that multiple devices or multiple applications of different design can exchange
information
• Interoperability and Integration is the fundamental user expectation when they

purchase a system
– All components can exchange data and cooperate in the implementation of the
system requirements
• A system acceptance test is essentially an interoperability and integration test.
• Interoperability testing is always the first step in proving a standard.

Limitations of Interoperability Testing
• Only the functions of the current applications are tested
– Adding new functions may not be as testable due to current operations.
• New systems not tested with existing applications may not interoperate
– All possible combinations of interoperability tests between a set of
available applications may not be performed.
• All tested systems may be non-conformant in the same way

– 2 apps have the same non-conformance problem may interoperate with
each other but not with other systems that are conformant.

Conformance Testing
• A formalized test that verifies conformance to the standard
• Typically a reference test system is created and devices/apps must interoperate with
the tester.
• Conformance testers are written with the standard in mind

– Interoperability tests are typically written with the application in mind
• Conformance testers will also test negative/error test cases.
• Conformance testing will increase the likelihood that applications will interoperate

Limits of Conformance Testing
• It is possible that 2 conformant applications may not interoperate for a variety of reasons
– Features sets that don’t overlap.
– Applications can be configured differently to behave in a different manner that is independent of conformance.
• The configuration of devices may not be compatible “out of the box” requiring engineering to achieve
interoperability.
– 2 Protection Relays:
• IED 1: uses an XML file generated by the user to configure the IEC 61850 information that is sent to other relays.
• IED 2: has a fixed configuration of specific data that can be sent.
• Both are conformant
• Unless IED 1 config. is modified to support IED 2 they will not interoperate.
• Highlights the importance of the quality assurance process to improve testing over time.
• Interoperability testing is still needed to test what it takes to make devices interoperate and integrate with
each other.
• IEC 61850 was not designed for interchangeability...only interoperability.

Certification
• A statement that tests have been run:
• Who ran the tests
• What tests have been run
• How the results were determined
• An independent third party should certify that the tester is valid and that
the process used by a test lab is valid.
• Certifying body must provide a quality assurance process to improve the

testing, fix the standards, and increase field interoperability

IEC61850-10 Conformance Testing
• Introduction
• Conformance Testing Definitions
• Quality Assurance Process
• Conformance Testing
• Procedures
• Test Cases for Servers
• Performance Testing
• Methodology
• Criteria

IEC 61850-10 Is a Subset of Tests Needed
• As systems are implemented technical issues (Tissues) are
discovered that need to be addressed
• An organization is needed to ensure this information is
captured, resolutions are developed and that testing proceeds
using these resolutions
• Result is testing that goes beyond the initial IEC conformance
testing standard

UCA IUG Quality Assurance Process
Vendor
System
Integrator
IEC TC57 Projects

Working (Users)
Groups
Test Test
System Laboratories
Developers
Realistic Coordination
Technical Issue (TISSUE) Process
A TISSUE resolution process is in place

to feed back user experience to
improve the standard.
TISSUE Membership
UCA Iug
Technical Each part of the standard
Committee has a responsible GoE
member identified
Group
Of
Experts
IEC TC57
WG10

TISSUE Process Initiator emails
TISSUES Selected and distributed to the

responsible member of GoE
Accepted
Could be a short
Resp. GoE member will
term fix 1st Proposal create 1st proposal and
distribute to all of GoE .
Final Proposal After discussion a final
proposal is distributed
to TISSUES group for vote.
Ready for the
100% approval
standard. UCAIug Needs work by
might make “green” TISSUES “yellow” TISSUES standards committee
mandatory if it
affects before resolution
interoperability.
IEC TC57 WG10

TISSUE Clarification Schedule
Voted
1st Final
Selecting Voting
Proposal Proposal
Veto
Veto
2 days 2 weeks 2 weeks 4 weeks
http://tissues.iec61850.com
Information Needed for Testing
• PICS: Protocol Implementation Conformance Statement
• Specifies what parts of the standard are implemented
– (e.g. ACSI services, etc.)
• MICS: Model Implementation Conformance Statement

• Specifies what portion of the model that are implemented
– (e.g. LNs, Data, attributes, etc.)
• PIXIT: Protocol Implementation eXtra Information for Testing

• Specifies information needed for testing that is outside the scope of IEC61850
– (e.g. addresses, supported values, etc.)
• TICS: Tissue Implementation Conformance Statement

– Specifies which Tissues have been implemented

IEC61850-10 Test Process Start Static Conformance
Requirements
PICS Static Conformance

Review
MICS Dynamic Conformance
Requirements
Test Selection Conformance Test

PIXIT Suite/Cases
and Setup
Dynamic Tests
_________________________
Communication Testing
Anomaly & Capability Testing
Behavior Testing
Review of Results Information

Testing
PICS – Protocol Implementation Conformance Statement Final Conformance Review
Conclusion (Customer Sign-Off)
Interaction
MICS – Model Implementation Conformance Statement Test Report Production
PIXIT – Protocol Implementation eXtra Information for Testing Control Flow
Data Flow
End

Test Architecture
Communications Simulator
Ethernet Hub
Device
Under Analyzer Time Master
Test
Equipment Simulator

Sample Test Cases

Sample Test Cases

Acceptance Criteria
• Pass
• DUT behaves as specified by IEC61850 and PIXIT
• Fail
• DUT does not behave per IEC61850 and PIXIT
• Inconclusive
• Action need to resolve
• DUT must remain operational throughout tests

Inconclusive?
• Ambiguities in the DUT responses to test cases
• Ambiguities in the standard?
• Input to the Tissue Process!!


CIM – IEC 61850 Harmonization

Common Information Model (CIM) is an object-oriented information
model of the power system
Central Generating Step-Up

Station Transformer
Distribution Receiving Distribution

Substation Gas Station Substation
Turbine Recip
Engine
Micro- Distribution
turbine Substation
Commercial
Recip Fuel
Engine cell
Photo
voltaics
Cogeneration
Batteries Flywheel
Industrial Commercial
Residential
UML – Unified Modeling Language

CIM Files and How They Are Used
• Schema File
– Describes all the object classes, their class
relationships/associations, and attributes
– Essentially it is the UML file transformed into an XML file.
– How it is used:
• Used by message development and processing tools
• Used by Enterprise Service Bus (ESB) for message transformations
• Used to configure applications with understanding of models to interpret the
content of the “instance files”

The Common Information Model Defines Objects and Relationships – Schema (UML, XSD, etc.)
Power System Resource

(logical)
SuperClass of
Equipment Container Conducting

Associated
Equipment with
Has Measurement
SuperClass of SuperClass of
XFMRWinding
Substation
Transformer
Has
Has
VoltageLevels

CIM As “Populated Instance Model” (IEC 61970-552)
Power System Resource
(logical)
SuperClass of
Equipment Container Conducting Equipment

Associated
with
Has Measurement
SuperClass of SuperClass of
XFMRWinding
Substation
RealizedBy
RealizedBy RealizedBy
Transformer
Has
Airport
Substation Has RealizedBy Tag 567
VoltageLevels Winding ABC

Has
Has
RealizedBy
XFR 123
Has
13KV
Object Instances

CIM Files and How They Are Used
• Instance File – CIM:XML format (IEC 61970-552) based on a profile (e.g.
CPSM ala IEC 61970-452)
– Full model file is a list of all the CIM objects within a given application
• All objects are related to the classes in the schema file
• All objects are indentified by a unique “master resource identifier” (MRID) or globally
unique identifier (GUID).
– Partial model file would contains only a part of the model (e.g. a single
substation)
– Incremental model file contains changes to the model such as
additions and deletions.

CIM Use Case: Power System Model Exchange
NERC CPSM Profile – IEC 61970-452
Interconnection Point(s)
• Schema is typically Power System 2

Power System 1
implied by mutual
agreement between
the parties.
• Typically only EMS EMS EMS

EMS
instance files are #1 #1
Exchange
#2 #2
Exchange
Model
exchanged. Model
Import Export Export Import
• Dynamics, planning,
and solutions are
being exchanged Instance File
today.
Instance File

Simplified Planning Process
New Subdivision &
Shopping Mall
Studies on
• Well defined
Existing processes and tools
Systems
for designing new
Design New
power system
Systems extensions,
simulating their
Studies on impact, defining new
New Systems
contingencies, etc.
Finalize New Design
Submit Prints, specs

Moving Design to Operations
• Since the advent of the CIM the ability to move models from
planning to operations (and vice-a-versa) in a multi-vendor
environment has improved.
– To be expected through use of standards.
– Eventually enable wide exchange of planning models like
ENTSO-E and WECC.
• EMS and planning use a set of tools that have been harmonized to
enable the flow of information between them.

Moving the Design to Substations
• Power system engineers use a completely different set of

tools supporting a completely different set of standards
to define the substation automation and protection
systems.

It’s About Productivity
• The effort and knowledge put into the planning and operations models
that isn’t embodied in the one-line diagrams is lost and has to be
transferred manually into the substation design through the engineering
process duplicating previous effort.
• If the tools used a common set of standards the flow of information can
be automated enabling topology, SCADA, protection, communications,
settings, etc. to be preserved and leveraged through the engineering
process.

CIM versus IEC 61850: What they define
CIM IEC 61850
• Detailed Power System Topology • Power System Topology Model
• Asset Model • Device Configuration Description
• Consumer and load models • Device Models
• Financial • Service Models
• Scheduling and transactions – Reporting
– Controls
• Market operations – Protection
• Work management • Performance/Requirements
• SCADA and Measurements • Object and Data Naming Conventions
• GIS – Location
• Protocols
• Business Messaging (WG14)
• Interface Services (GID)

CIM Based Modeling Tool

IEC 61850 Based Modeling Tool (SCL)
Logical Node Designators

Two Different Purposes – Two Solutions are OK, BUT
• Detailed system wide description • Substation design and modeling

• Model exchange for high-level systems • Device configuration management
• Power flow, state estimation, etc. • Protection and device control
• Market operations • SCADA, protection, & control data exchange
• Planning and system design

CIM and IEC 61850 Difference in Topology
Are these the

same objects?
IEC 61970-301 EMS Diagram IEC 61850-6 SCL Diagram

Harmonization of CIM – IEC 61850
• IEC TC57 WG19: “Interoperability Within TC 57”
• Integration of non-overlapping models into a single unified model
• Rules and procedures for transforming overlapping models when needed.

– Convert from one model form to another to suit the application
– Transformations are not bi-directional
• IEC 61850 SCL cannot be transformed into a complete CIM model
– Complete integration may require some mapping in special circumstances
– Most applications can use transformation.
• Substation engineering and operations use different tools.
• EPRI project developed a proposed approach to harmonization adapted by WG 19

IEC62361-102 CIM-61850 Harmonization
sd ScadaUseCase Sequence
Priority 1:
«business actor»
Planning Department SCADA/EMS/DMS CIM /EMS
«business actor» «business actor»
CIM Modeling Engineer 61850 System Engineer SCT (tool) IED Tool IED
«business actor»
IED Vendor(s)
Mapping transfer
from 61850 SCL to
(Substation Engineering) (from Modeling and (from (from (from
Tools
Actors) Actors) Actors) Actors)
(from
Actors)
CIM
01_Requirements & Design Specification()
02_Data
Entry()
SSD(v1)
03_SSD(v1)
Mapping(SSD)
04_05_Review()
Comments()
06_Comments()
07_Updates()
08_SSD(v2)
09_ICD()
10_Review proposed devices()
10A_Select devices()
11_ICD[n]()
SCD(v1) 12_Communications Design()

13_SCD(V1)
Mapping (SSD)
14_15_Review()
Comments()
16_Comments()
17_Revision()
SSD
18_SCD(v2)
19_Configure IEDs()
20_Pre-acceptance tests and updates()
CIM Update usecase Mapping (SSD)
22_Add CIM infomation()

21_SCD(v2)
SCD(v2)
SCD
24_CIM
Update(test)
CIM Activation usecase

The prefix numbers for each transfer correspond to the
step numbers in Section 4.
25_CIM Update(online)
(from Actors) (from Actors) (from Actors) (from Actors)

SCL – CIM Converter SCT
• Converts IEC 61850 SCD file into IEC 61970 IEC 61850
Common Information Model (CIM) files for SCD
import into EMS, DMS, PI, etc.

• Enables the substation semantic information
created during the substation design process SCL to CIM
to be used for configuration of other systems Converter
including:
– Substation power system topology and CIM-XML
connectivity
– Attribute/tag naming
– Settings EMS/
– Subscriptions for SCADA clients PI

IEC 61850 UML
NSD(s) “IEC 61850 UML Artifact”
“Code Components” Tooling
IEC 61850-7-2
IEC 61850-7-3
IEC 61850-7-4
IEC 61850-7-420

SCL Toolkit
• A set of utilities to assist users in implementing the IEC 61850 “Top-Down” engineering process
– Specification Comparison Tool – IED selection utility
– Workflow Comparison Tool – Evaluates changes in SCL files
– LN Definition Browser – Provides access to IEC 61850 object definitions
– SCD to CID Extractor – Extracts CID/IID information from an SCD
– SCL to CIM Converter – Converts IEC 61850 SCL to IEC 61970 CIM
– DNP3 ICD Creator and Mapping – Enables use of DNP3 devices with the IEC 61850 engineering
process
– IEC 61850 UML – UML for Enterprise Architect for use in Enterprise Semantic Modeling (ESM)
and Application Integration activities

• Any detailed Logical Node

Reviews?
• Look at existing and
emerging standards?
• Open Discussion?
• Any good fishing stories?

Thank You

IEC 61850 Seminar-SISCOpdf

Uploaded by

Copyright:

Available Formats

IEC 61850 Seminar-SISCOpdf

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IEC 61850 Seminar-SISCOpdf

Uploaded by

Copyright:

Available Formats

Transforming the world of energy using open standards

IEC 61850 Seminar

© Copyright 2018 SISCO. All Rights Reserved

2 © Copyright 2018 SISCO. All Rights Reserved

3 © Copyright 2018 SISCO. All Rights Reserved

Have a question? Ask a question!

4 © Copyright 2018 SISCO. All Rights Reserved

The Business Case for IEC 61850

© Copyright 2018 SISCO. All Rights Reserved

Consumers will be able to Home energy management

Battery technology will become Microgrids will emerge

6 © Copyright 2018 SISCO. All Rights Reserved

Coal/Natural Gas Energy Storage

7 © Copyright 2018 SISCO. All Rights Reserved

The growth of data requires a new approach for OT applications:

Model based integration using CIM and IEC 61850

• Systems need to be:

9 © Copyright 2018 SISCO. All Rights Reserved

– Standardized Device, Object and Service/Behavior

– Read, Write, buffered reporting, controls, logging, files,

11 © Copyright 2018 SISCO. All Rights Reserved

• Good News: It worked! Device communications costs were lowered.

© Copyright 2018 SISCO. All Rights Reserved

I need the Phase A voltage for

Device NO POWER SYSTEM CONTEXT FOR

All Cost…No Value

• Assume Index #25 is always used to store breaker status.

• Even if every device used Index #25 to hold breaker status

© Copyright 2018 SISCO. All Rights Reserved

– Specify the bytes/format of the data on the wire

– Specify the meaning of data

– Specify the behavior of the data

© Copyright 2018 SISCO. All Rights Reserved

Mod Mod PhV PhV Mod Mod PhV PhV

© Copyright 2018 SISCO. All Rights Reserved

19 © Copyright 2018 SISCO. All Rights Reserved

• The Substation Configuration

20 © Copyright 2018 SISCO. All Rights Reserved

21 © Copyright 2018 SISCO. All Rights Reserved

• Product implementation complexity does not result in application complexity

• Even though user configuration is understandable (simple) overall system

22 © Copyright 2018 SISCO. All Rights Reserved

• At a 2010 industry event a Sun Spec representative told me:

• Let’s look at how “simple” grid connected inverters are using

© Copyright 2018 SISCO. All Rights Reserved

• Assuming that technology constraints today will be valid over the

• Assumption that user configuration is reasonable because it is

• User effort costs less than development

© Copyright 2018 SISCO. All Rights Reserved

© Copyright 2018 SISCO. All Rights Reserved

As the substation design

Coal/Natural Gas Energy Storage

30 © Copyright 2018 SISCO. All Rights Reserved

a) IEC 61850 Costs More to Use

b) IEC 61850 Costs Less to Use

33 © Copyright 2018 SISCO. All Rights Reserved

34 © Copyright 2018 SISCO. All Rights Reserved

• European (and other) utilities bid substations turnkey

35 © Copyright 2018 SISCO. All Rights Reserved

36 © Copyright 2018 SISCO. All Rights Reserved