Realize the Power of OPC-UA

Tom Burke - President and Executive Director, OPC

Foundation

OPC Foundation

• International Industry Standard Organization – 400+ Member Companies / 100+ 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….

OPC HistoryApplication X ...

DCS ControllerPLC

Application Y

DisplayApplication

TrendApplication

OPC OPC

DCSController

PLC

• The Problem– Many different vendors

– Custom made solutions

– Proprietary technologies

– Point-to-point Integration

– Limited “real-time” information

– Maintenance nightmare

– Multiple dependencies

• Solution– OPC

OPC Data Access Architecture

PLC

PLC

MES and/or HMI Applications(OPC Client) OPC Server

Software App provides

a linkage betweenOPC Client(s)and devices

Proprietary Messaging

OPC Data Access

OPC – Functional Areas

• Data Access• Alarms & Events• Historical Data Access• Complex Data• Batch

• Data eXchange• XML Data Access• Commands• Security

Today’s Integration Challenges

• Numerous incompatible protocols

• Complex configuration and maintenance

• Islands of automation

• Rigid infrastructure

• Vulnerability to system and network failures

• Security or lack there of…

Numerous Incompatible Protocols

CC-LinkCC-LinkTCPTCP

EthernetEthernet

HARTHART

OAGISOAGIS

DDEDDE

COMCOM

BAPIBAPI

DeviceNetDeviceNetProfiBusProfiBus

FieldBusFieldBus

OPC-DAOPC-DA

HTTPHTTP

WMIWMI

SOAPSOAP

OPC-A&EOPC-A&EDCOMDCOM

802.1x802.1x

802.11802.11

IPv4IPv4UDPUDP

CANCAN

RS-232RS-232

IPv6IPv6

IPXIPX

OLEOLE

FTPFTP

OPC-HDAOPC-HDA

KerberosKerberos

J1939J1939

ModbusModbusFDIFDI

CANopenCANopenAS-IAS-I

InterbusInterbus

IndustrialIndustrialEthernetEthernet

ControlNetControlNet

DeviceLogixDeviceLogixDHCPDHCP

DNSDNS

XMLXML

BluetoothBluetoothLonworksLonworks

FIPIOFIPIO

FirewireFirewire

USBUSBRS-423RS-423

RS-485RS-485RS-422RS-422

IPsecIPsec

netDDEnetDDE

802.3802.3 V.35V.35

RARPRARP

ARPARP

ICMPICMP

EBCDICEBCDIC

ANSIANSI

CORBACORBA

.NET Remoting.NET Remoting

SNMPSNMP

UNICODEUNICODE

The Inter-Enterprise NightmareManufacturer

SuppliersPlants

Application X ...

DCS ControllerPLC

Application Y

• The Problem– Many different vendors– Custom made solutions– Proprietary technologies– Point-to-point Integration– Limited “real-time”

information– Maintenance nightmare– Multiple dependencies

• Solution– OPC Unified

Architecture

P

L

P

L

P

L

P

L

APPLICATIONPACKAGES

MIS

Dev

ice

Dat

a Configuration

Unified Architecture Evolution

SCADASCADAHMI Visualization

HMI Visualization

AssetManagement

AssetManagement PurchasingPurchasing

ProductionManagement

Systems

ProductionManagement

Systems

InventoryManagement

InventoryManagement

ProductionControl

ProductionControl

The Automationparadigm

The Automationparadigm

The Enterpriseparadigm

The Enterpriseparadigm

COM object

Interfaces

ServerClient

Pointers tointerfaces

A client accesses a COM object's services through pointers to its interfaces.

Function1( )Function2( )Function3( )

Each interface provides one or morefunctions

•An interface is a collection of methods An interface is a collection of methods or related functions and procedures or related functions and procedures that perform some specific service that that perform some specific service that the COM object will provide.the COM object will provide.

•COM does not specify the COM does not specify the implementation of interfaces, only their implementation of interfaces, only their behavior in interacting with clients.behavior in interacting with clients.

COM Interfaces

OPC Unified Architecture Motivation

OPC-UA

DCOMretires

.NETnew

Communicationarchitecture

Better

Integration(DA, HDA, AE)

More Areas of

Application(MES, ERP)

Internet

ServiceOriented

OPC Unified Architecture

• OPC-UA (OPC Unified Architecture) extends the highly successful OPC communication protocol, enabling data acquisition and information modeling/communication between the plant floor and the enterprise.

OPC Unified Architecture

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

OPC-UA Fundamentals

• Based on standards for the Web– XML, WSDL, SOAP, WS-*

• Optimized for the Intranet– OPC Binary encoding over TCP

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

• SOA (Service Oriented Architecture)

• Single set of Services– Query, Read, Write,

Subscribe…

• Named/Typed relationships between nodes.

OPC Interface Unification

Historical Data

Access

Alarms&

Events

ComplexData

Commands

DataAccess

The UA Server embodies the functionality of existing OPC Servers using a single set of services

UA ServerUA Server

Unified Object Model

OPC UA Object

Variables ___ ___ ___

Methods ___() ___() ___()

Events

Method Services Variable Services

Event Services

OPC DA and HDA OPC Commands

OPC A&E

OPC Subscriptions

OPC-UA Address Space

Root

Fieldbus Sensor Bus Areas

PressureXmitter

Valve Area 1

• Full Mesh – Network Model

• Unlimited Named/Typed Relationships

• “Views” are used to present hierarchies

Abstract UA ModelSpecification

WSDL / SOAPor TCP / Binary

Services Binding

Proxy /Stubs

API

Communication Layering

Tool orLanguageDependent(e.g. .NET)

Scalable Platform Independent Messaging Model

.NET (WCF) Version

Portable C/C++ Version

Java Version

Business Model, Adaptable to Platform Independent Messaging Models (e.g. WSDL)

OPC UA Base Services All Necessary Services

Specification Layering

Vendor Information Model

DA A&E HDA CMDs OPC Information Model

Information Model Specifications IEC, ISA, OAGi, EDDL…

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

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”

Putting it all together

Data Model

SOA Model

OPC OPC UAUA

Comms Model

Protocol Independent

Platform Independent

Plant floor and Internet

Access

DA, HDA, and A&E

Object Model

TypeDescriptions

Abstract Services

OPC Provides Industry-Standard interOperability, Productivity & Collaboration

BatchBatch

OPC Unified Architecture OPC Unified Architecture

Manufacturing, Production and MaintenanceManufacturing, Production and Maintenance

OP

C

OP

C

Adv.Adv.ControlControl

OP

C

OP

C

HMIHMI SCADASCADA

PC-Based ControlPC-Based Control

MESMES

OPCOPC

OPCOPC

Industrial NetworksIndustrial Networks DataAcquisition

DataAcquisition

PLCDCS

PLCDCS ??.......????.......??

ERP, SAP … Corporate EnterpriseERP, SAP … Corporate Enterprise

OPC Unified Architecture OPC Unified Architecture

OPC Compliance

Cross Industry /Collaboration 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 EDDL • Collaboration with MS MUG & NAMUR• Collaboration with …… (stay tuned)

The Vision of OPC

• Success Is Measured By Level Of Adoption

• Collaboration

• 24/7 Reliability

• OPC Is Plug-and-play

• OPC Is Everywhere

• Get Connected