Transcript Document

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
Jim.Luth@Invensys.com
7/16/2015
John Gillerman
Grid Cloud Systems, Inc.
OPC UA w.g. Member
OPC TAC Member
john@gridcloudsys.com
1
Problem Statement: Users/Apps Can’t
Easily Access Integration Bus Data
Energy Management
Systems
Outage Management
Systems
Supervisory Control
and Data Acquisition
Grid
Cloud
System
s
Asset Management
System
61968-100 Integration Bus
Distribution
Management
Systems
2
Customer
Information
System
Meter Data
Management
System
© Copyright 2012 Grid Cloud Systems, Inc.
Grid
Cloud
System
s
Not Possible For An Individual or Application To Receive And Process All
Integration Bus Messages. Users need a way to find and filter data
Huge Data
Bus
3
© Copyright 2012 Grid Cloud Systems, Inc.
Example: Meter Readings via IEC
61968 Part 9 Messaging
4
Grid
Cloud
System
s

A meter reading head end may send out a million
meter events a day. Each meter is typically identified
by a numeric ID.

IEC 61968 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?
© Copyright 2012 Grid Cloud Systems, Inc.
Grid
Cloud
System
s
IEC 61968-100 Smart Proxies


5
IEC 61968-100 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.
WS Client
JMS Client
JMS Event Listener
JMS Interface
Request
Reply
Event
Request
WS Interface
Prioxy
Topic
Router
Topic
Topic
Request
JMS Interface
Reply
Service
Event
Reply
© Copyright 2012 Grid Cloud Systems, Inc.
Typical Approach: Warehouse Based Portal
Grid
Cloud
System
s

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
IEC 61968 - 100
Integration Bus
6
PreConfigured
Web Portal
© Copyright 2012 Grid Cloud Systems, Inc.
Grid
Cloud
System
s
CIGRE D2.24 Utility Information Architecture
Specifies QCRUD Access to Current/Historical and
Model/Measurements: Query, Create, Update Delete
Event History Consumer
Event Notification Consumer
business
code
business
code
Output Data
Input Data
business
code
Output Data
Output Data
Input Data
Output Data
Output Data
Data
Access
event history
View Consumer
Data
Access
event notification
view update
Input Data
Output Data
DS ‘A’
DS ‘B’
Data
Access
view creation
Context ‘X’, DS ‘A’
System Data Set Management
7
j-1
vj-1
on
r si
en
th
vj
ve
isto
j
s
ry
s
vk-1
on
vk
r si
k
ev
k-1
Context ‘X’, DS ‘B’
vk+1
ve
ev
en
th
isto
ry
k+1
© Copyright 2012 Grid Cloud Systems, Inc.
Using Web Services Gateway
to Access Operational Data
IEC 61968 - 100
Integration Bus
Grid
Cloud
System
s
Gateway
supports unified
QCRUD access
to Integration
Bus and 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.
8
© Copyright 2012 Grid Cloud Systems, Inc.
OPC UA Can Be Used To Provide
QCRUD Access To Integration Bus Data
Grid
Cloud
System
s
User only receives
messages of interest
base on topic and
content
IEC 61968 Part 9 message
payload in OPC UA WS Event
OPC UA Adapter can
send and receive IEC
61968 Part 9 messages
Integration Bus
IEC 61968 Part 9 Messages
in IEC 61968-100 WS Event
IEC 61968 compliant applications exchange IEC 61968 Part 9 messages
according to IEC 61968-100 architecture over integration bus
9
© Copyright 2012 Grid Cloud Systems, Inc.
Grid
Cloud
System
s
Solution Architecture
Access to
Integration Bus
within the context
of the CIM
IEC 61968 - 100
Integration Bus
10
IEC 61968
Smart Proxy
OPC UA
QCRUD Adapter
© Copyright 2012 Grid Cloud Systems, Inc.
Solution Architecture
Grid
Cloud
System
s
Generic OPC UA Client receives specific OPC
UA events by browsing the IEC 61968 CDPSM
CIM instance data and selecting CIM objects
IEC 61968 - 100
Integration Bus
IEC 61970 CPSM
Schema Data File
IEC 61968
Smart Proxy
OPC UA
QCRUD Adapter
Prototype developed by the OPC
Foundation during for the 2011 IEC
61968-9 IOP
IEC 61970 CPSM
Instance Data File
11
© Copyright 2012 Grid Cloud Systems, Inc.
OPC Demo Topics
• Review of the IEC 62541/OPC UA Meta Model
• Demo
7/16/2015
12
IEC 62541 Architecture
7/16/2015
13
Summary Node Classes
Everything in the UA
Address Space is a
Node
UA defines a nonextensible list of 8
Node Classes
BaseNode
+NodeId : NodeId
+NodeClass : NodeClass
+BrowseName : QualifiedName
+DisplayName : LocalizedText
+Description : LocalizedText
Each Node Class has a
defined set of Attributes
Nodes are connected by
References
The identifier for a node
is the NodeId
Object
Variable
Method
+EventNotifier : Byte
+Value
+DataType : NodeId
+ArraySize : Int32
+AccessLevel : Byte
+UserAccessLevel : Byte
+MinimumSampleInterval : Int32
+Executable : Boolean
+UserExecutable : Boolean
View
+ContainsNoLoops : Boolean
+EventNotifier : Byte
ObjectType
ReferenceType
VariableType
+IsAbstract : Boolean
+IsAbstract : Boolean
+Symmetric : Boolean
+InverseName : LocalizedText
+Value
+DataType : NodeId
+ArraySize : Int32
+IsAbstract : Boolean
7/16/2015
DataType
14
IEC 62541 Meta Model
Top Layer
Relationship
Base Types
Top
Complex Data
Schema
Type
Layer
Instantiation
(between layers)
Subclassing
(Inheritance)
Data Type
Reference
Standard and
System -defined
Data Type
Definitions
Other relationship such as
“contained”,
“operated by”,
“controls”, etc.
Instance Layer
7/16/2015
15
Object Type Node Class
Root
Organizes
HasTypeDefinition
reference
Objects
Organizes
Boiler
Pipe1
Instances
FlowTransmitter
Types
Organizes
Types
Valve
Organizes
•
•
•
•
ObjectTypes
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
7/16/2015
Organizes
BaseObjectType
FolderType
BaseEventType
ValveType
BoilerType
HasSubType
reference
16
Object Type Node Class
Root
Organizes
HasTypeDefinition
reference
Objects
Organizes
Boiler
Pipe1
Instances
FlowTransmitter
Types
Organizes
Types
Valve
Organizes
•
•
•
•
ObjectTypes
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
7/16/2015
Organizes
BaseObjectType
FolderType
BaseEventType
ValveType
BoilerType
HasSubType
reference
17
Overview of Meta Model Mapping
7/16/2015
18
OPC UA/CIM DEMO
7/16/2015
19
Setting Up The Demo
OPC UA Client
(Has no knowledge of the CIM)
OPC UA
Web Services
OPC UA Wrapper
(OPC DA Client and an OPC UA Server
Customized to import CIM Data)
OPC DA
COM API
SISCO AX-S4 61850
OPC DA COM Server
GE
Relay
7/16/2015
Step 1: Import
NodeSet XML Enterprise Architect
with CIMBat Plugin
Step 2: Import
CIM XML
ABB 40
Bus Model
Step 3: Import
Map OPC DA COM
Map XML
Measurements to
CIM Measurements
Siemens
Relay
20
Running The Demo
OPC UA Client
(Has no knowledge of the CIM)
Step 1: Add
Measurement
Step 2: Map
Measurement
Step 3: Delete
Measurement
Step 4: Import
Meter Reading
OPC UA
Web Services
CIM Incremental
File
OPC UA Wrapper
(OPC DA Client and an OPC UA Server
Customized to import CIM Data)
OPC DA
COM API
IEC 61968 Part 9
Meter Reading
Message XML
SISCO AX-S4 61850
OPC DA COM Server
GE
Relay
7/16/2015
CIM Incremental
File
Siemens
Relay
21
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
•
•
•
•
•
•
7/16/2015
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
22