OPC Today and in the Future

1
OPC Today and in the Future

• Tom Burke - President and Executive Director, OPC
  Foundation
• Jim Luth, Technical Director, OPC Foundation

2
OPC Past, Present, Future

• Thomas Burke, OPC Foundation President

3
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.

4
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
Archive Replay Module
min
Control Stations
Area Servers
Plant Network Modules
Additional CN Modules
Application Module
History Module
secs
Fiber Optics
CONTROL NETWORK
Network Gateway
Network Gateway
PLC Gateway
Subnetwork Gateway
Network Interface Module
1 sec
Control Network Extenders
Other Data Hiway Boxes
PLC
Other Subsystems
Multifunction Controller
msec
Logic Manager
Process Manager
Extended Controller
Subnetwork
CONTROL NETWORK
Advanced Process Manager
Basic Controller
Advanced Multifunction Controller
LocalProcessors

• sec

Smartine Transmitters
Transmitters

• Complex Information Flows
• Multi-vendor
• Proprietary

• Asynchronous Processing
• Multiple Interfaces
• Mission Critical
• How To Manage Changes?

5
The Inter-Enterprise Nightmare

• Best-of-breed solutions
• Many different vendors
• Custom made solutions
• Proprietary technologies
• Point-to-point Integration
• Limited real-time information
• Risking future success
• Complex business environment
• Maintenance nightmare
• Multiple dependencies
• Multiple standards

Manufacturer
Plants
Suppliers
Customer value is lost
6
InterOperability
InterOperability

• A standard object model and set of interfaces for
  applications and servers

Performance
Before OPC
With OPC
Custom interfaces
Client and Server write to a standard

• reduce cost
• protect investment
• more choices
• increase productivity

• costly
• inefficient
• risky

Connectivity
Display Application
Trend Application
OPC
OPC
PLC
DCS
Controller
7
OPC Data Access Architecture
Software App provides a linkage between OPC
Client(s) and devices
OPC Server
PLC
PLC
Proprietary Messaging OPC Data Access
8
OPC Market Acceptance

• Dramatic Market Acceptance Growth
• Clear business benefits risk mitigation
• Many vertical industry applications

OPC
OPC UA
9
OPC Functional Areas
10
Todays Integration Challenges

• Numerous incompatible protocols
• Complex configuration and maintenance
• Islands of automation
• Rigid infrastructure
• Vulnerability to system and network failures
• Security

11
Numerous Incompatible Protocols
DDE
RS-232
HART
Lonworks
UNICODE
802.3
V.35
ProfiBus
Interbus
Bluetooth
CC-Link
DNS
IPsec
RS-485
DeviceNet
TCP
OAGIS
CAN
Kerberos
ControlNet
CORBA
DHCP
RS-422
BAPI
netDDE
EBCDIC
SNMP
HTTP
802.11
SOAP
DeviceLogix
ANSI
FieldBus
FIPIO
COM
IPX
USB
CANopen
IndustrialEthernet
RS-423
AS-I
.NET Remoting
DCOM
OPC-HDA
OPC-AE
XML
ARP
Firewire
OLE
Modbus
WMI
IPv6
802.1x
IPv4
UDP
OPC-DA
FDI
RARP
ICMP
J1939

Ethernet
FTP
12
Numerous Incompatible Tiers
13
OPC Unified Architecture Motivation
.NET new Communication architecture
DCOM retires
Internet
OPC-UA
Better Integration (DA, HDA, AE)
More Areas of Application (MES, ERP)
Service Oriented
14
OPC Unified Architecture

• Web Services / XML
• Easy Configuration and Maintenance
• Increased Visibility
• Broader Scope
• Reliability
• Security
• Performance
• Platform Neutrality
• Legacy Products Plug Right In

15
OPC Unified Architecture Base

• Architecture
• Integration of DA, AE, 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..

16
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

17
Unified Architecture Evolution
Asset Management
Purchasing
Inventory Management
ProductionControl
SCADA
HMI Visualization
The Enterprise paradigm
The Automation paradigm
ProductionManagement Systems
18
OPC Unified Architecture
Open Standards to Deliver Interoperability Device
to Device and Device to the Enterprise
MIS
Device Data
Enterprise Integration (ERP, Asset
Management, Advanced Diagnostics, etc.)
APPLICATION PACKAGES
Configuration
Subsystem Integration
Device Integration (FF, Profibus, HART, etc)
19
OPC Provides Industry-Standard interOperability,
Productivity Collaboration
ERP, SAP Corporate Enterprise
OPC Unified Architecture
Manufacturing, Production and Maintenance
OPC Unified Architecture
Batch
Adv. Control
HMI
SCADA
MES
OPC
OPC
OPC
PC-Based Control
OPC
Industrial Networks
PLC DCS
Data Acquisition
??.......??
20
OPC Unified Architecture

• Jim Luth, OPC Technical Director

21
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

22
OPC Interface Unification

• SOA (Service Oriented Architecture)
• Single set of Services
• Query, Read, Write, Subscribe
• Named/Typed relationships between nodes.

AlarmsEvents
DataAccess
Historical DataAccess
Commands
ComplexData
UA Server
The UA Server embodies the functionality of
existing OPC Servers using a single set of
services
23
Unified Object Model
24
OPC-UA Address Space

• Full Mesh Network Model
• Unlimited Named/Typed Relationships
• Views are used to present hierarchies

25
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

26
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.

27
Communication Layering
.NET (WCF) Version Portable C/C Version Java
Version
Tool orLanguageDependent(e.g. .NET)
Scalable Platform Independent Messaging Model
Business Model, Adaptable to Platform
Independent Messaging Models (e.g. WSDL)
28
Specification Layering

• Clients written to just the base can still
  discover and access all data from the derived
  layers!

29
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

30
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

31
UA Server Chaining
EnterpriseSemantics
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.
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.
Enterprise Network
Operations Network
ProcessSemantics
Plant Floor Network
DeviceSemantics
32
OPC Address Space Today

• Pure Hierarchy
• Parent/Child Relationships Only

33
Data Items and Alarms Today
34
UA Coherent Address Space
35
UA Coherent Address Space
Integrated data and alarms
36
Object Classes and Instances

Top Layer

Relationship
Complex Data
Top

Base Types

Schema

Type
Layer

Instantiation
(between layers)

Subclassing

(Inherit
ance)

Data Type
Reference

Standard and
System
-
defined
Other relation- ship such as contained,
operated by, controls, etc.
Data Type

Definitions

Instance Layer

37
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)

38
Methods vs.
Programs

• 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.

• Methods part of UA Base
• Synchronous invocation similar to blocking
  function calls.
• AckAlarm()

39
Programs can have State
State Machine

• UA defines the basic state machine.
• State transitions may cause notifications.

• Sub-states can be defined in particular for the
  executing state.

40
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

41
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

42
UA Services

• Common services support DA, AE, and HDA
  operations
• Protocol independence
• Timeless durability
• Integrated with the UA Data Model
• Partitioned into Service Sets

43
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

44
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

45
Putting it all together
Abstract Services
Type Descriptions
Data Model
SOA Model
Object Model
OPC UA
Protocol Independent
DA, HDA, and AE
Comms Model
Platform Independent
Plant floor and Internet Access
46
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

Proxy
Client
Stub
Server
SOAP
47
Interoperability with UAPI
Client Application
UA Programmers Interface
WSE 2.0
Indigo
Java
UA TCP
XML UA Binary
XML UA Binary
UA Binary
Indigo Binary
WSE 2.0
Indigo
Java
UA TCP
UA Programmers Interface
Server Application
48
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
49
UA Enable all OPC COM Servers

• UA clients can instantly connect to hundreds of
  existing OPC COM Servers

UAClient
UAServer Wrapper
COMDA Server
SOAP over
UA
HTTP or TCP
50
UA Enable all OPC COM Clients

• Use the UA Client Proxy to connect existing COM
  clients to new UA Servers

UAClient Proxy
COMDA Client
UAServer
SOAP over
UA
HTTP or TCP
51
Disable Remote DCOM

• Use the UA proxy and wrapper to replace DCOM as
  remote communication protocol

UAClient Proxy
COMDA Client
UAServer Wrapper
COMDA Server
SOAP over
UA
HTTP or TCP
52
Disable Remote DCOM

• Use the UA proxy and wrapper to replace DCOM as
  remote communication protocol

UA Proxy
COM Client
UA Wrapper
COM Server
UA
53
OPC Unified Architecture Roadmap
OPC Unified Architecture Milestones
54
OPC Unified Architecture Demo

• The UA Proxy and Wrapper
• Enhancing the past,Connecting the future

55
Cross Industry Interoperability Strategy

• OPC used in process discrete manufacturing
• OPC adopted in the following
• Semiconductor
• Plant Maintenance and Production Management
• Industrial Ethernet ..
• Security
• Building Controls
• RFID
• Retail/ Financial
• .
• Collaboration with MIMOSA
• Collaboration with ISA (S88, S95, S99)
• Collaboration with OAGi
• Collaboration with IEC
• Collaboration with MS MUG NAMUR
• Collaboration with (stay tuned)

Markets
Collaboration
56
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,

57
More Information

• Visit the UA home page
• http//www.opcfoundation.org/UA

58
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!