1. IEC 61970 Part 502-8 Discussion (IEC 62541/OPC UA for CIM) Jim Luth
Invensys Operations Management
OPC UA w.g. Chairman
OPC TAC Member
John Gillerman
Grid Cloud Systems, Inc.
OPC UA w.g. Member
OPC TAC Member

2. Problem Statement: Users/Apps Can’t Easily Access Integration Bus Data
Energy Management Systems
Outage Management Systems
Supervisory Control and Data Acquisition
Asset Management
System
EMS
OMS
SCADA
AMS
Integration Bus
DMS
CIS
MDMS
Distribution Management Systems
Customer Information System
Meter Data Management System

3. Huge Data
Not Possible For An Individual or Application To Receive And Process All Integration Bus Messages. Users need a way to find and filter data
Inte
gra
tion
Bus
sag es
Mes

4. Example: Meter Readings via IEC 61968 Part 9 Messaging
A meter reading head end may send out a million meter events a day. Each meter is typically identified by a numeric ID.
IEC Part 9 messaging supports getting a list of every meter ID and to poll for specific meter events once you have the meter ID.
How does a user who is only interested in VIP metering events select the data of interest? Is it possible for any human to go through a million numeric IDs to find the ones of interest?

5. IEC Smart Proxies
IEC states that “smart proxies” can be used to implement topic based subscriptions but does not specify how this is done.
OPC UA can be used to create a “smart proxy” with additional features for intermittently connected clients.

6. Typical Approach: Warehouse Based Portal
Putting all messages into a data warehouse disables real-time eventing. The portal typically has no means to notify applications/users that new data of interest is available.
Using a data warehouse/portal in this way supports query, but defeats the purpose of an event driven architecture which is one of the main goals of an integration bus
HTTP Server
Pre-
Configured
Web Portal
IEC
Integration Bus
Data
Warehouse

7. CIGRE D2.24 Utility Information Architecture
Specifies QCRUD Access to Current/Historical and Model/Measurements: Query, Create, Update Delete

8. Using Web Services Gateway to Access Operational Data
Gateway supports unified QCRUD access to Integration
Bus and Data Warehouse
IEC
Integration Bus
Data
Warehouse
Gateway supports QCRUD: Client Query and Topic based Message Subscription all configured via a model driven GUI.
Need services that are not tied to the database layout of the database, instead data is access via CIM objects.

9. User only receives messages of interest base on topic and content
OPC UA Can Be Used To Provide QCRUD Access To Integration Bus Data
User only receives messages of interest base on topic and content
OPC UA Client
OPC UA
Gateway with IEC Message Adapter
OPC UA Adapter can send and receive IEC Part 9 messages
IEC Part 9 message payload in OPC UA WS Event
Integration Bus
IEC 61968
Application
IEC Part 9 Messages
in IEC WS Event
IEC 61968
Application
IEC compliant applications exchange IEC Part 9 messages according to IEC architecture over integration bus

10. Access to Integration Bus within the context of the CIM
Solution Architecture
IEC WS Publisher
Application
IEC WS Subscriber
Application
Access to Integration Bus within the context of the CIM
IEC 61968
Smart Proxy
OPC UA
QCRUD Adapter
IEC
Integration Bus
IEC WS Publisher/Subscriber and
OPC UA Client/Server

11. IEC 61968 Part 9 WS Subscriber and OPC UA Server/COM Wrapper
Solution Architecture
Generic OPC UA Client receives specific OPC UA events by browsing the IEC CDPSM CIM instance data and selecting CIM objects
IEC Part 9 WS Publisher
Application
IEC 61968
Smart Proxy
OPC UA
QCRUD Adapter
IEC
Integration Bus
Prototype developed by the OPC Foundation during for the 2011 IEC IOP
IEC CPSM
Schema Data File
IEC Part 9 WS Subscriber and OPC UA Server/COM Wrapper
OPC COM DA SCADA Data
Server
IEC CPSM
Instance Data File

12. OPC Demo Topics
Review of the IEC 62541/OPC UA Meta Model
Demo

13. IEC Architecture

14. Summary Node Classes Everything in the UA Address Space is a Node
UA defines a non- extensible list of 8 Node Classes
Each Node Class has a defined set of Attributes
Nodes are connected by References
The identifier for a node is the NodeId

15. IEC Meta Model
Other relation- ship such as “contained”, “operated by”, “controls”, etc.
Subclassing
(Inherit
ance)
Data Type
Reference
Instantiation
(between layers)
Standard and
System -
defined
Definitions
Top Layer
Type
Layer
Relationship
Base Types
Instance Layer
Top
Complex Data
Schema

16. Object Type Node Class
Types folder provides main entry point for the types
ObjectTypes folder provides main entry point for the object types
FolderType and BaseEventType are sub types of the BaseObjectType and are defined by OPC
ValveType and BoilerType are referenced with HasTypeDefinition by the instances of the object types

17. Object Type Node Class
Types folder provides main entry point for the types
ObjectTypes folder provides main entry point for the object types
FolderType and BaseEventType are sub types of the BaseObjectType and are defined by OPC
ValveType and BoilerType are referenced with HasTypeDefinition by the instances of the object types

18. Overview of Meta Model Mapping

19. OPC UA/CIM Demo

20. Setting Up The Demo OPC UA Client (Has no knowledge of the CIM) OPC UA
Web Services
Step 1: Import NodeSet XML
OPC UA Wrapper
(OPC DA Client and an OPC UA Server
Customized to import CIM Data)
Enterprise Architect with CIMBat Plugin
Step 2: Import CIM XML
ABB 40
Bus Model
Step 3: Import Map XML
Map OPC DA COM Measurements to CIM Measurements
OPC DA COM API
SISCO AX-S
OPC DA COM Server GE
Relay
Siemens
Relay

21. Running The Demo Step 1: Add Measurement Step 3: Delete Measurement
OPC UA Client
(Has no knowledge of the CIM)
Step 2: Map
Measurement
Step 4: Import
Meter Reading
OPC UA
Web Services
OPC UA Wrapper
(OPC DA Client and an OPC UA Server
Customized to import CIM Data)
CIM Incremental
File
CIM Incremental File
IEC Part 9
Meter Reading
Message XML
OPC DA COM API
SISCO AX-S
OPC DA COM Server GE
Relay
Siemens
Relay

22. Why Use OPC UA
OPC UA is becoming the defacto standard for model based Web Services in the process control industries
Support growing fast by tool and application vendors
Unique capabilities include:
Address Space Model
Full Mesh
Supports versioning of type information and instance data
Eventing to support WG 14 messages
Security
Performance
Availability and Reliability
Established testing procedures, tools and organization
Backward compatible with OPC DA COM means that migration and interoperability issues are greatly diminished