9
OP Mach C UA hine-to-M In – A F Machine n Subsea First L e Connec a Applica Look ctivity ations Copyright 2011 Matrikon Inc.

Opc Ua Sean Leonard

Embed Size (px)

Citation preview

Page 1: Opc Ua Sean Leonard

OP

Mach

C UA

hine-to-MIn

– A F

Machinen Subsea

First L

e Conneca Applica

Look

ctivity ations

Copyright 2011 Matrikon Inc.

Page 2: Opc Ua Sean Leonard

•• • •

Connectivity Vision

HMI

ToDevice

HMI

ToPLC

HMI

ToLogs

DB

ToDevice

DB

ToPLC

DB

ToLogs

Analysis

ToDevice

Analysis

ToPLC

Analysis

ToLogs

Network of Proprietary Interfaces

The Problem Classic OPC Solved

1 Copyright 2011 Matrikon Inc.

Page 3: Opc Ua Sean Leonard

The OPC Concept: Open Connectivity OPC – A Set of Separate Standards• Classic OPC Specifications

– OPC DA – real time– OPC HDA – history

– OPC A&E – events– OPC CMD – programs

– OPC Security– Complex Data

Historical

Data

Access

Alarms

&

Events

Complex

Data

Commands

Data

Access

Why OPC Classic Succeeded• Published industrial standards for system interconnectivity• Domain Agnostic Application Interfaces

– Data model agnostic– Stable application interfaces

Domain Agnostic

ServerServer

Domain Agnostic

ServerServer

Domain Agnostic

ServerServer

2 Copyright 2011 Matrikon Inc.

Page 4: Opc Ua Sean Leonard

Domain Agnostic

ServerServerBatchBatch

Manufacturing, Production and MaintenanceManufacturing, Production and Maintenance

OP

CO

PC

Adv.Adv.ControlControl

OP

CO

PC

HMIHMI SCADASCADA

PCPC--Based ControlBased Control

MESMES

OPC OPC

OPCOPC

Industrial Networks

Data

AcquisitionPLC, RTU

DCSOther Protocols

Corporate EnterpriseCorporate Enterprise

OPCOPC

Where Classic OPC is used today

Taking Stock of OPC Classic

Challenges to Enterprise Integration

Industrial Landscape Shifts…

•Access to Control Data at Control level.

•Limited corporate access or applications.

•Limited users

Industrial Landscape Shifts…

• Embedded OPC for non

Windows devices

• Growing corporate/operational demand for control data

• Improved security necessary• New Industry segments adopting

OPC

3 Copyright 2011 Matrikon Inc.

Page 5: Opc Ua Sean Leonard

The Challenge

• Next Gen OPC requires:– Operating system agnostic

– Industry Domain agnostic– Scalable: embedded to enterprise

– Single interface/unified address space– Communicate data and context

• Secure, Reliable, Interoperable OPC UNIFIED ARCHITECTURE (UA)Next generation Open Connectivity

OPC UA - High Level View• Not “another” super protocol

• Complements existing protocols

• facilitates data connectivity regardless of underlying protocol

OPC UA Specification Layering

OPC UA Base Services All Necessary Services

Vendor Information Model

DA A&E HDA CMDsOPC

Information Model Specifications IEC, ISA, MIMOSA …

•Comprehensive Data Modeling Handles All Data Needs•OPC UA Clients choose appropriate data detail

OPC UA Solves Even More..

OPC Unified Architecture BaseArchitecture • Integration of DA, A&E, HDA, Commands, Complex Data, and

Object Types

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 domain specifics

4 Copyright 2011 Matrikon Inc.

Page 6: Opc Ua Sean Leonard

OPC Unified Architecture BaseSecurity• Secure-by-default, Encryption, Certificate Handling

Robustness and Reliability• Communication failure recovery• Redundancy

Companion Standards• Industry collaboration (EDDL, FDT, MIMOSA, ADI)

UA Specifications & OPC Classic Mapping

Tool or Language Dependent: • • Portable C/C++ Version•

Scalable Platform Independent Messaging Model

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

API

Proxy /Stubs

WSDL / SOAPor TCP / Binary

Services Binding

Abstract UA ModelSpecification

OPC UA Communication Layering Moving OPC Forward

• Component Model:– Expose interfaces– Remote method invocation– Platform dependent– Windows security

OPC Server

COMI/F

OPC Client

COMI/F

Component Model

OPC Server

Service

OPC Client

Proxy

WWW

Service Model

• Service Model:

– Expose services

– Message exchange

– True platform independence

– WS security

MainframeMainframe

OPC UA Scalability

PortablesPortables

DesktopDesktopPCPC

ServerServer

Unix Unix ServersServers

EmbeddedEmbeddedSystemsSystems

ControllersControllers

Standard internet

protocols allow cross-

platform communication

Enterprise Wide Scalability

5 Copyright 2011 Matrikon Inc.

Page 7: Opc Ua Sean Leonard

UA Connectivity Options

• Multiple connection types supported:

Transport Layer

TCP/IP

Web Services (XML over HTTP)

Security

Security Disabled

Signed

Signed & Encrypted

Data Format

Binary

XML

UA Connectivity Options

UA BinaryUA XML

WS Secure Conversation UA Secure Conversation

SOAP 1.2 UA TCP

TCP/IPHTTP/HTTPS

OPC Client Connection: Endpoints

UA Server

UA Server

UA Server

UA Server

UA Server

UA Server

UA Client

UA Connectivity: Endpoints

• Multiple connection types supported:

Transport Layer

TCP/IP

Web Services (XML over HTTP)

Security

Security Disabled

Signed

Signed & Encrypted

Data Format

Binary

XML

UA Server

Scalability Through Profiles• Facet: an atomic client/server capability

• Profile:• A defined level of minimum set of facets for interoperability• A set of facets and profiles

• Scalability Profiles• Nano Embedded Device Server – Security is NONE only and only basic

binary DA type calls.• Micro Embedded Device Server – Nano with subscription capabilities.• Embedded UA Server – Micro with more subscription options and some

security.• Standard UA Server – A full UA Server with full DA and subscriptions and

all security

UA AddressSpace

• UA Server models information using:• AddressSpace

– Nodes• Variable: DATAITEMTYPE (Classic Item mapping)• References (Relationships between nodes)• Properties (High/Low Ranges)• …

– Views• UA Servers can organize information into defined

groupings for different UA Clients

6 Copyright 2011 Matrikon Inc.

Page 8: Opc Ua Sean Leonard

UA Modeling• Robust data models can be built using nodes

& the relationships between them.

UA Nodes• Single AddressSpace facilitates all UA Specifications

Change in DataItem State or Value (Deadband)

Access to DataItem’s archived values

Notifications about events of interest occurring

Notifications about events where DataItem state or value exceeds predefined limits

DataAccess

HistoryAccess

Event

Alarms & Conditions

Available Now:Name Description

Specifications The specs are complete and released

MatrikonOPC Universal Connectivity Server

native OPC UA and OPC Classic access to countless device drivers

MatrikonOPC Universal Connectivity Server for SCADA

native OPC UA and OPC Classic access to telemetry based devices

MatrikonOPC Universal Connectivity Server for Non-Windows

native OPC UA access on non-Windows platforms to countless device drivers

MatrikonOPC Security Gateway Add the power of OPC UA and per-user-per-item level security to any OPC server

UA Strengths• Scalable• Domain agnostic• Platform and protocol independent

– Not another super protocol– Protocol mapping across domains

• Data models• Security is baked in• Service Oriented Architecture

UA Challenges• OPC Classic

– Great technology– Often poorly implemented/Executed– DCOM OPC UA still has the word OPC

• Education– No one knows what is behind the curtain– Perceived complexity

• End users are not demanding faster adoption

MatrikonOPC can Help• Training (become an expert):

• OPC UA• OPC Implementations

• Services• Architectural assessments• Technology consulting

• Technology• MatrikonOPC Universal Connectivity Server• Adapters• Server Development

7 Copyright 2011 Matrikon Inc.

Page 9: Opc Ua Sean Leonard

Summary • OPC Classic’s success is undeniable• OPC UA provides

– Secure, Robust, Efficient, Scalable – Platform and protocol independent – Rich clients and servers– Evolutionary, not revolutionary

• OPC UA is ready todayNew capabilities for customersNew opportunities for vendors

THANK YOU

8 Copyright 2011 Matrikon Inc.