Transcript Model Driven Web Services

OPC Today and in the Future
Tom Burke - President and Executive Director, OPC
Foundation
Jim Luth, Technical Director, OPC Foundation
OPC : Past, Present, & Future
Thomas Burke, OPC Foundation
President
OPC Foundation
• International Industry Standard Organization
– 400+ Member Companies / 40+ end-users Members
– 2500+ Total Companies Build OPC Products = 15000+ Products
• The vision of OPC is to be the Foundation for interOperability
– for moving information vertically from the factory floor through the
enterprise of multi-vendor systems (with stops in between…)
– For moving information horizontally between devices on different
industrial networks from different vendors;
– Not just data but information…….
• Reliable, Secure Integration is not an Option
• Collaboration is key to pulling multiple “open” standards into
unified open platform architecture….
The Plant : a Complex Environment with many opportunities for
standards for interoperability
Other
Computing
Devices
Plant
Servers
hours
PLANT INFORMATION NETWORK - Ethernet
Personal Computer
Network Manager
min
secs
Area Servers
Plant
Network
Modules
Application
Module
Additional
CN Modules
History
Module
Fiber Optics
Network
Gateway
CONTROL NETWORK
Network
Gateway
1 sec
msec
Subnetwork Gateway
Other Data
Hiway Boxes
Multifunction
Controller
LocalProcessors
PLC
Gateway
Control Network
Extenders
PLC
Other
Subsystems
Process
Manager
Advanced
Process
Manager
Advanced
Multifunction
Controller
Transmitters
•
•
•
•
Network
Interface
Module
Logic Manager
Extended
Controller
Basic
Controller
 sec
Archive
Replay Module
Control Stations
Asynchronous Processing
Multiple Interfaces
Mission Critical
How To Manage Changes?
Smartine
Transmitters
• Complex Information Flows
• Multi-vendor
• Proprietary
InterOperability
InterOperability
A standard object model and set of interfaces for applications and servers
Performance
Before OPC:
With OPC:
Client and Server write to a standard
Custom interfaces
• costly
• inefficient
• reduce cost
• protect investment
• risky
• more choices
• increase productivity
Connectivity
...
Application X
PLC
Application Y
DCS
Controller
Display
Application
Trend
Application
OPC
OPC
PLC
DCS
Controller
OPC Data Access Architecture
MES and/or HMI Applications
(OPC Client)
OPC Server
Software App
provides
a linkage between
OPC Client(s)
and devices
PLC
PLC
Proprietary Messaging
OPC Data Access
OPC Market Acceptance
•
•
•
Dramatic Market Acceptance & Growth
Clear business benefits & risk mitigation
Many vertical industry applications
Technology Life Cycle Curve
OPC
$
OPC UA
Chasm
Time
Innovators
Early Adopters
Early Majority
Late Majority
Laggards
Technology
Enthusiasts
Visionaries
Pragmatists
Conservatives
Skeptics
Source: Inside the Tornado by Geoffrey A. Moore, HarperBusiness, 1995 pages 14 & 19
OPC – Functional Areas
Today’s Integration Challenges
•
•
•
•
•
•
Numerous incompatible protocols
Complex configuration and maintenance
Islands of automation
Rigid infrastructure
Vulnerability to system and network failures
Security
Numerous Incompatible Protocols
DDE
RS-232
HART
Lonworks
UNICODE
V.35
ProfiBus802.3
Interbus
DNSCC-Link BluetoothIPsecDeviceNet
RS-485
TCP
OAGIS
CAN
Kerberos
ControlNet
CORBA
DHCP
RS-422
netDDE
BAPI EBCDIC
SNMP
HTTP
802.11
SOAP
DeviceLogix
FieldBus
COM IPX FIPIO ANSI
USB
CANopen
RS-423
AS-I Industrial
.NET
Remoting
DCOM
OPC-HDA
OPC-A&E
ARP
XML
Ethernet
Firewire Modbus
OLEIPv6
WMI
UDP OPC-DA 802.1x FDI IPv4
RARP
ICMP
J1939
Ethernet
FTP
Numerous Incompatible Tiers
OPC Unified Architecture Motivation
Internet
DCOM
.NET
new
Communication
architecture
retires
OPC-UA
More Areas of
Better
Integration
(DA, HDA, AE)
Service
Oriented
Application
(MES, ERP)
OPC Unified Architecture
•
•
•
•
•
•
•
•
•
Web Services / XML
Easy Configuration and Maintenance
Increased Visibility
Broader Scope
Reliability
Security
Performance
Platform Neutrality
Legacy Products Plug Right In…
OPC Unified Architecture Base
•
Architecture
– Integration of DA, A&E, Commands, Complex Data, and Object Types
•
Designed for Federation
– abstract data/ information from the plant floor, through information models, and up to
enterprise systems
•
Information Modeling
– development and deployment of standard information models to address industry
domains specifics
•
Complex Data
– OPC Standard & Domain & vendor specific…..
OPC Unified Architecture Base
•
Security
– Collaboration, Development & Reference
•
Enterprise Integration
– OPC UA standard messaging system
•
Robustness / Reliability Designed & Built in….
– NO Failures
– Sequence numbers, keep-alives, resyncing, and support for redundancy
•
•
Commands
Companion Standards
– industry groups define what OPC Unified Architecture “transports”
Unified Architecture Evolution
Asset
Management
Production
Control
HMI
Visualization
Inventory
Management
Purchasing
SCADA
The
Automation
paradigm
Production
Management
Systems
The
Enterprise
paradigm
OPC Unified Architecture
Open Standards to Deliver
Interoperability
Device to Device and Device to the
Enterprise
Enterprise Integration
(ERP, Asset Management,
Advanced Diagnostics, etc.)
MIS
APPLICATION
PACKAGES
Subsystem Integration
Device Integration
(FF, Profibus, HART, etc)
P
P
L
P
L
P
L
L
OPC Provides Industry-Standard interOperability, Productivity &
Collaboration
ERP, SAP … Corporate Enterprise
OPC Unified Architecture
Manufacturing, Production and Maintenance
OPC Unified Architecture
HMI
SCADA
OPC
OPC
Adv.
Control
MES
OPC
Batch
PC-Based Control
OPC
PLC
DCS
Industrial Networks
Data
Acquisition
??.......??
OPC Unified Architecture
Jim Luth, OPC Technical
Director
OPC-UA Fundamentals
• Based on standards for the Web
– XML, WSDL, SOAP, WS-*
• WS-Policy negotiates protocol and encoding
• WS-SecureConversation provides secured sessions
• Optimized for the Intranet
– OPC Binary encoding over TCP
OPC Interface Unification
Alarms
&
Events
•
SOA (Service Oriented Architecture)
•
Single set of Services
– Query, Read, Write, Subscribe…
Data
Access
•
Named/Typed relationships between
nodes.
Historical
Data
Access
Commands
Complex
Data
UA Server
The UA Server embodies the functionality of existing OPC Servers using
a single set of services
Unified Object Model
OPC DA and HDA
OPC Commands
OPC UA Object
Variable Services
Method Services
Variables
___
___
___
Methods
___()
___()
___()
OPC A&E
Events
Event
Services
OPC Subscriptions
OPC-UA Address Space
Root
Fieldbus
Pressure
Xmitter
Sensor Bus
Valve
• Full Mesh – Network Model
• Unlimited Named/Typed Relationships
• “Views” are used to present hierarchies
Areas
Area 1
Robustness
• Subscription Update Features
– Keep-alive (heartbeat) messages
• Allows clients to detect a failed server or channel
– Sequence Numbers in each update message
• Allows client re-sync to obtain missed messages
– Decouples callback channel from notification mechanism,
allowing callback channel to be reset without loss of data
• Redundancy Features
– Designed for easy (optional) redundancy of both Clients
and Servers
• e.g. re-sync request can be sent to a backup server
Security
• UA Clients present credentials to UA
Servers (x509 certs on both sides).
• UA Servers require authentication and
authorization.
– Access control can be fine-grained down
to the property level.
• Optional message signing and
encryption.
Communication Layering
Tool or
Language
Dependent
(e.g. .NET)
.NET (WCF) Version
Portable C/C++ Version
Java Version
Scalable Platform Independent
Messaging Model
Business Model, Adaptable to
Platform Independent
Messaging Models (e.g. WSDL)
Specification Layering
Vendor Information Models
Information Model Specifications
DA
A&E
HDA
OPC UA Base Services
CMDs
IEC, ISA, MIMOSA …
OPC Information Model
All Necessary Services
Clients written to just the base can still discover and access all data from the derived
layers!
Scalability
• OPC UA “Server Profiles” defined to allow servers with different capability
levels
• Client can discover server profile
• Profiles and wrappers defined for migrating existing servers to UA
• More capable profiles also defined
Server Diagnostics
• Standard “Server” node defined in address space
• Standard diagnostic data items defined for the server, such as
“SubscriptionCount”
• Server specific diagnostics can be added, with semantics defined by object
type definitions
UA Server Chaining
UA
Client
UA
Client
Enterprise Network
Operations Network
UA
Client
UA
Server
UA
Server
UA
Client
UA
Client
Plant Floor
Network
UA
Server
UA
Server
UA
Client
UA
Server
Enterprise
Semantics
Process
Semantics
Device
Semantics
“Aggregating” UA Servers
extract and process data
from lower level “Device”
UA Servers.
Data is recast using
different information
models appropriate for the
clients at the higher level.
OPC Address Space Today
Root
Fieldbus
Pressure
Xmitter
Sensor Bus
Valve
• Pure Hierarchy
• Parent/Child Relationships Only
Areas
Area 1
Data Items and Alarms Today
Data Access Address Space
Alarms & Events Address Space
Root
Root
Field
Bus
Pressure
Xmitter
Valve
Current
Value
Sensor
Bus
Temp
Xmitter
Hi
Limit
Lo
Limit
Area 1
Clients must correlate the
two temperature
transmitter nodes based
on external knowledge
Area 2
Temp
Xmitter
Hi Alarm
Lo Alarm
Area 3
Pressure
Xmitter
Valve
UA Coherent Address Space
Root
Field
Bus
Pressure
Xmitter
Sensor
Bus
“Located In”
reference
Temp
Xmitter
Valve
Areas
Area 1
Area 2
Current Value
Hi Limit
Lo Alarm
Lo Limit
Lo Alarm
Area 3
UA Coherent Address Space
Root
Field
Bus
Pressure
Xmitter
Sensor
Bus
“Located In”
reference
Temp
Xmitter
Valve
Areas
Area 1
Area 2
Current Value
Hi Limit
Lo Alarm
Lo Limit
Lo Alarm
Integrated data and alarms
Area 3
Object Classes and Instances
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
Complex Data Features
• Tells clients how to parse structured data
• Allows use of XML Schemas for describing XML data
• Defines OPC Binary data description language that uses XML to describe
binary data structures
• Allows client to access device specific data descriptions (e.g. Fieldbus
Foundation OD)
Methods
Method Services
Object
Variables
___
___
___
Methods
___()
___()
___()
vs.
•
•
Methods part of UA Base
Synchronous invocation similar to
blocking function calls.
–
AckAlarm()
Programs built on top of Methods
Programs represent executable components of objects ,
e.g.,
–
–
DownloadProgram(Name, InitState)
MonitorNetwork (From, Till, Interval)
•
•
Execution time may vary from milliseconds to indefinitely.
Asynchronous invocation is non-blocking. Results are
returned using notifications.
•
The client can control the execution.
Events
•
•
Programs
Programs can have State
State
Machine
Idle
5
1
7
4
Halted
(optional)
8
UA defines the basic state machine.
State transitions may cause notifications.
9
Executing
6
•
•
3
Abnormal
Failure
2
Completed
Opening
•
Sub-states can be defined in particular
for the executing state.
Executing
Sending
2
Closing
3
Scalability
• OPC UA “Server Profiles” defined to allow servers with different capability
levels
• Client can discover server profile
• Profiles and wrappers defined for migrating existing servers to UA
• More capable profiles also defined
Server Diagnostics
• Standard “Server” node defined in address space
• Standard diagnostic data items defined for the server, such as
“SubscriptionCount”
• Server specific diagnostics can be added, with semantics defined by object
type definitions
UA Services
•
•
•
•
•
Common services support DA, A&E, and HDA operations
Protocol independence
Timeless durability
Integrated with the UA Data Model
Partitioned into Service Sets
UA Service Sets
• Secure Channel Service Set
– Open & Close Channel, GetPolicies
• Session Service Set
– Create, Close, Activate, ImpersonateUser
• Node Management Service Set
– Add & Delete Objects and References
• View Service Set
– Browse, BrowseNext
UA Service Sets (2)
• Query Service Set
– QueryFirst, QueryNext
• Attribute Service Set
– Read, Write, ReadHistory, UpdateHistory
• Method Service Set
– Call
• Monitored Item Service Set
– Create / Modify / Delete
• Subscription Service Set
– Create / Modify / Delete, Publish, Republish
Putting it all together
Object
Model
Abstract
Services
Type
Descriptions
Data
Model
DA, HDA,
and A&E
Platform
Independent
SOA
Model
OPC
UA
Comms
Model
Protocol
Independent
Plant floor
and Internet
Access
UA Programmers’ Interface
• Designed to provide an abstraction layer between the application
developer and the SOAP stack/wire encoding
• Defined by UA to match the abstract specification instead of the WSDL
Client
Proxy
SOAP
Stub
Server
Interoperability with UAPI
Client Application
UA Programmers’ Interface
WSE 2.0
Indigo
Java
XML
Indigo
UA Binary Binary
WSE 2.0
Indigo
UA TCP
UA Binary
Java
UA Programmers’ Interface
Server Application
UA TCP
The UA SDK (II)
WSE 2.0
Indigo
Java
UA TCP
UA Programmers’ Interface
UA Reference Server
UA Reference Server Extensibility Interface
COM
Wrapper
XML-DA
Wrapper
Native
Vendor
Specific
UA –Enable all OPC COM Servers
• UA clients can instantly connect to hundreds of existing OPC COM Servers
UA
Client
SOAP over
UA
HTTP or TCP
UA
Server
Wrapper
COM
DA
Server
UA –Enable all OPC COM Clients
• Use the UA Client Proxy to connect existing COM clients to new UA Servers
COM
DA
Client
UA
Client
Proxy
SOAP over
UA
HTTP or TCP
UA
Server
Disable Remote DCOM
• Use the UA proxy and wrapper to replace DCOM as remote communication
protocol
COM
DA
Client
UA
Client
Proxy
SOAP over
UA
HTTP or TCP
UA
Server
Wrapper
COM
DA
Server
Disable Remote DCOM
• Use the UA proxy and wrapper to replace DCOM as remote communication
protocol
COM
Client
UA
Proxy
UA
UA
Wrapper
COM
Server
OPC Unified Architecture Roadmap
Architecture Vision
Q4 / 03
Implementation SubCommittee Formed
Q1 / 05
Phase One
Ref. Implementation
Q4 / 06
OPC Unified Architecture Milestones
UA Committee
Formed
Q1/ 04
Phase One Spec.
Release
Q2 / 06
Promote Phase One
Worldwide
Q4 / 06
OPC Unified Architecture Demo
The UA Proxy and Wrapper:
Enhancing the past,
Connecting the future
Cross Industry Interoperability Strategy
•
•
OPC used in process & discrete manufacturing
OPC adopted in the following:
•
•
•
•
•
•
Collaboration
Collaboration
Collaboration
Collaboration
Collaboration
Collaboration
–
–
–
–
–
–
–
–
Semiconductor
Plant Maintenance and Production Management
Industrial Ethernet …..
Security
Building Controls
RFID
Retail/ Financial
….
with
with
with
with
with
with
MIMOSA
ISA (S88, S95, S99)
OAGi
IEC
MS MUG & NAMUR
…… (stay tuned)
OPC Vision
•
OPC Domains
–
–
–
–
–
–
•
•
Automation (factory & process)
Building Controls
Security
Semi – Conductor
Financial / Retail
…..
OPC is the “HOW” for moving “WHAT”
OPC Collaboration
– Industrial Ethernet, WS - *, IEC, ISA SP95, ISA SP88, ISA SP99, EDDL, OMAC, MS MUG, …
More Information …
Visit the UA ‘home’ page
http://www.opcfoundation.org/UA
®
F O U N D A T I O N
OPC Success
• Success is measured by level of adoption
• OPC members’ participation
– Design, Build, and Deliver Products
– Compliance / Interoperability Testing
• End-users demand certification
• Industry Endorsement
• OPC is everywhere!