Upload
others
View
16
Download
0
Embed Size (px)
Citation preview
• Ameen Hamdon
• President, SUBNET Solutions Inc.
• Former President, DNP3 User Group
• Canada
We have many different IEDs and BI Systems deployed to meet different department needs
The Situation Today
Deploy many more IEDs and integrate them intelligently to new BI Systems and realize many new Smart Grid Benefits
The “Smarter” Grid Tomorrow – The Reward?
Without good standards, this has created a complexity that has become unmanageable.
The “Smarter” Grid Tomorrow – The Reward?
Substation Integration complexity today is more than just Protocol Translation
• SCADA and Non-SCADA data substation communications
• Fault File Management
• Remote Engineering Access (CIP-005, CIP-007)
• Password Change Management (CIP-005, CIP-007)
• Configuration Management (CIP-010)
IEC-61850 Marketed Promise
• IEC-61850 had been marketed for approximately 15 years as the Electric Utility answer for….
– Multi-vendor Interoperability
– Reducing IED Integration complexity
• Self Description, etc
– Enabling engineering efficiencies
• Configuration
• Testing
Presentation Overview
• This presentation outlines recent history of the state of IEC-61850 Interoperability
– Review Results from Recent IEC-61850 IOPs
– Review Issues and Solutions for a Major Multi-Vendor IEC-61850 Utility Project
– Discusses vendor business cases “for” and “against” effective Multi-Vendor IEC-61850 Interoperability
Using IEC 61850 was supposed to assist with this complexity
Single Vendor IEC 61580 Interoperability = OK
Relay Relay
Gateway
Relay
61850
HMI
Relay Relay Relay
61850
Gateway HMI
What about Multi-Vendor IEC-61580 Interoperability
? Relay Relay Relay IEC-61850 Gateway HMI
Recent IEC 61850 Interoperability Panels
• UCA held an IEC 61850 IOP in April 2011
• UCA held another IEC 61850 IOP in October 2013
• Cigre 2014 IEC 61850 IOP
• Another IEC 61850 IOP is being held later in 2015
IEC 61850 Interoperability 2011
• Points taken from the following report IEC 61850 IOP, Paris, France UCAIug-63-111Rv1.pdf
• Issues found between vendor files – Incorrect initialized values. – Issues found between vendor implementations
• Support of Integer 128 issues – Inability to “to map/support such a value in the implementations
memory/application”
– “Vendor A attempted to import an SCD file exported by Vendor B. A problem occurred. The problem was diagnosed to be an unsupported XML Namespace issue”
IEC 61850 Interoperability 2013
• UCA held a IEC 61850 IOP in October 2013
• Points taken from the following report http://www.ucaiug.org/Meetings/CIGRE_2014/USB%20Promo%20Content/UCAIug/UCA%20Users%20Group%2061850%20IOP%20Report%2028012014f.pdf
– “Engineering efforts required to implement the standard in a substation are huge”
– “Grid operators are forced to use specific vendor tools that are not optimal in a multi-vendor environment and train staff to use a wide range of tools to configure the system”
– “A clear move by the market to a top-down approach using standardized third-party tools is needed”
http://www.ucaiug.org/Meetings/CIGRE_2014/USB Promo Content/UCAIug/UCA Users Group 61850 IOP Report 28012014f.pdfhttp://www.ucaiug.org/Meetings/CIGRE_2014/USB Promo Content/UCAIug/UCA Users Group 61850 IOP Report 28012014f.pdfhttp://www.ucaiug.org/Meetings/CIGRE_2014/USB Promo Content/UCAIug/UCA Users Group 61850 IOP Report 28012014f.pdfhttp://www.ucaiug.org/Meetings/CIGRE_2014/USB Promo Content/UCAIug/UCA Users Group 61850 IOP Report 28012014f.pdf
IEC 61850 IOP 2013
IEC 61850 IOP 2013
• 61850 Standard Issues from the report:
– SCL
• “ED.1/ED.2 co-existence in a single SCD file”
• “Client reporting subscription”
• “GOOSE subscription”
• “SV subscription”
– Networking
• “VLAN Tag 0 support in switches”
Incorrect SCD/CID File Formats
• CIGRE 2014:
– Issues with Major Relay Vendor CID files
• Problem: Vendor tools create incorrect CID file formats – Issue: Found several instances of missing DOType, DAType,
ENUM, and ConnectedAP definitions
– Issue: Point IDs created to be too long and incompatible with certain 61850 server driver implementations
Incorrect SCD/CID File Formats
• Problem: Vendor tools used to integrate CIDs into an SCD file don’t properly handle object types with the same name in each CID. This causes conflicts and redefining definitions. – Example: Each CID defines its own DOType called A. What DOType definition is used in
the SCD?
SCD File
CID DOType = A DAType 1 DAType 2
CID DOType = A DAType 1 DAType 2
DAType 3
CID DOType = A DAType 1
CID CID CID
DOType = A?
Incorrect SCD/CID File Formats
• Solution: Vendor enhancement requests
SCD File
CID_1 DOType = A DAType 1 DAType 2
CID_2 DOType = A DAType 1 DAType 2
DAType 3
CID_3 DOType = A DAType 1
CID_1 CID_2 CID_3
DOType = A_1 DOType = A_2 DOType = A_3
CID CID CID
Vendor Specific Config Settings
Vendor Specific IED Config
Settings mnot part of the CID
Relay Relay Relay
Gateway HMI
Vendor CID files only partially defines the IED Configuration
Vendor Specific IED Config
Settings mnot part of the CID
Vendor Specific IED Config
Settings mnot part of the CID
SCD File
Multi-vendor modifications needed for SCD to provide full IED Configuration Management
Unified SUBNET CID c/w Private
Data
Unified SUBNET CID c/w Private
Data
Unified SUBNET CID c/w Private
Data
CID CID CID
Vendor Specific Config Settings
Vendor Specific IED Config
Settings mnot part of the CID
Relay Relay Relay
Gateway HMI
Vendor Specific IED Config
Settings mnot part of the CID
Vendor Specific IED Config
Settings mnot part of the CID
However, IEC 61850 Vendor Specific Interoperability Issues continue to inhibit this
goal Vendor Specific
Vendor Specific PRP/HSR
RCB
Vendor Specific
File naming, file collection
Vendor Specific
File naming, file collection
Conclusion: Multi-Vendor IEC-61580 Interoperability continues to have major issues
? Relay Relay Relay 61850 Gateway HMI
Result of IEC-61850 Issues
• Many Utilities concerned about doing their own integration
• Many seek turnkey integration solutions for device Vendor
• Device Vendors get to supply Single Vendor solutions vs Multi-Vendor
• Bottom Line: Ongoing Vendor Specific issues hurt Utilities, help Device Vendors
IED Vendors Smart Grid Business Case for Profit Maximization
IED Vendors Integration Goals
• Buy more of their IEDs
• Buy newer, more expensive IEDs
• Upgrade, Replace IEDs more Frequently
IED Vendor Specific Integration Solutions
• Buy more of their IEDs vs others
• Add new basic IT functionality into edge IEDs vs upper tier devices
• Accelerate product discontinuance, obsolescence
Multi-Vendor IEC 61850 is still possible however…
Southern California Edison Irvine Smart Grid Demonstration
“The project will demonstrate the next generation of automation and control design based on the open standard IEC-61850.
This is expected to provide measurable engineering, operations, and maintenance benefits through improved safety, security, and reliability.
Demonstration of a new auto-configuration application is intended to significantly reduce manual effort, errors, and omissions.”
The Configuration Management, Password Management, and Remote Engineering Access Management need to be integrated.
Using IEC 61850 for Enterprise Management
You can’t keep passwords a secret if every time someone uses your remote engineering access
system, they need the password.
Integrated Solution
Password Management and Remote Engineering Access need to be integrated.
Integrated Solution
The same is true with configuration management. If the system is to provide automation of these functions, it needs to be able to logon to the device at an authorized privilege level. This requires both remote
engineering access and the device passwords.
Integrated Solution
The Configuration Management, Password Management, and Remote Engineering Access Management need to be
integrated.
Integrated Solution
The solution needs to be vendor-agnostic.
Integrated Solution
What functions are we looking for?
• Version-control
• Permission policies
• Approval processes and workflow
• Change Notifications
Configuration Management (CIP-010)
IEC-61850 Defines a Standards-Based Approach to Configurations with SCL.
SED System Exchange Description
SSD System Specification Description
SCD Substation Configuration Description
ICD IED Capability Description
CID Configured IED Description
IID Instantiated IED Description
Based on Standards
A vast array of tooling and technology can be leveraged for working with the information.
SCL Files are XML
The CID schema can be extended for defining legacy devices (Modbus, DNP3, etc.) within the context of IEC-61850. The CID schema can be extended to support equipment such as routers and switches.
SCL Files are Extensible
IEC-61850 SCL helps us with… • considering all device
configurations as one holistic substation configuration.
• differencing two different configuration files.
• Ensuring compatibility with legacy devices.
• considering the IT devices (routers, switches, and radios) the same at the OT devices.
• Leveraging open standards.
Solving part of the problem
Our corporate and substation-level architecture can help with the rest.
• Synchronization between the corporate environment and the substation.
• actively monitoring the devices in the substation.
• Automatically extracting changed configurations from devices.
Solving the other part of the problem
The system starts with the building of a Substation Configuration Description file (.SCD) by a “Substation
Engineering Modelling Tool”.
The SCD describes the entire substation configuration, including every IED, HMI, network switch, and router.
Substation Engineering
Modelling Tool outputs
.SCD
1. SCD File Configuration
Because the SCD File is XML, the Corporate Device Manager has an
opportunity to configure itself based on the SCD file.
.SCD
Corporate Device
Manager
Input to
2. The SCD File is Loaded into the Corporate Device Manager
Solution can: • Automatically create a substation instance • Place the SCD file under document control • Automatically create all substation devices • Automatically create substation and device meta-data
tags • Extract per-device CID configuration files • Place all CID files under document control • Synchronize with other systems such as
certificate/key managers, historians, etc.
2. The SCD File is Loaded into the Corporate Device Manager
Corporate Device
Manager
Substation Gateway
.SCD
Electronic transfer ensures: • SCD updates are always accessible at the substation • The right configuration file is at the substation
3. Transfer of SCD File to Substation Gateway
Corporate Device
Manager
Substation Gateway
.SCD
Electronic transfer ensures: • SCD updates are always accessible at the substation • The right configuration file is at the substation • The substation gateway can auto-configure itself. • The substation gateway can auto-configure the rest of the
equipment in the substation.
3. Transfer of SCD File to Substation Gateway
Configuring the substation gateway:
• Automatically create all substation devices.
• Automatically build point references.
• Establish which end devices have configurations ready to be deployed.
3. Transfer of SCD File to Substation Gateway
Configuring the substation gateway:
• Automatically create all substation devices.
• Automatically build point references.
• Establish which end devices have configurations ready to be deployed.
• Automatically deploy those end device configurations.
3. Transfer of SCD File to Substation Gateway
The Substation Gateway can actively poll and monitor the devices in the substation for out-of-band configuration changes.
1. Front faceplate changes
2. Users accessing devices with vendor configuration software
Substation Gateway
Substation IED
5. Active Configuration Monitoring
If a change is detected, the Substation Gateway can extract the configuration from the device.
Substation Gateway
.CID
Substation IED
5. Active Configuration Monitoring
The Substation Gateway can automatically transfer the file to the Corporate Device Manager for archival.
Corporate Device
Manager
.CID
Substation Gateway
5. Active Configuration Monitoring
The Corporate Device Manager can notify users that an out-of-band change was detected.
Corporate Device
Manager
5. Active Configuration Monitoring
In summary…
• Integration solutions from device vendors benefit from Multi-vendor Interoperability issues as they maximize revenue when he sells a their Single Vendor solution
• However effective IEC 61850 Multi-Vendor Integration is possible
• IEC-61850 Interoperability issues can be resolved by companies focused on providing true Multi-vendor solutions
Ameen H. Hamdon
SUBNET Solutions Inc.
+1 403 270-8885