29
October 2006 Introduction to Unified Architecture The Next Generation of System Interoperability Thomas J. Burke OPC Foundation President & Executive Director

Introduction to Unified Architecture - Home - CIMugcimug.ucaiug.org/KB/Knowledge Base/Introduction_To_… ·  · 2008-06-10Introduction to Unified Architecture ... ERP EAM Content

  • Upload
    vodien

  • View
    220

  • Download
    0

Embed Size (px)

Citation preview

October 2006

Introduction to Unified ArchitectureThe Next Generation of System Interoperability

Thomas J. Burke

OPC Foundation President & Executive Director

Thomas J. Burke 2

OPC Foundation’s New OpportunityImprove the Existing … and … Find Its Place in …

Next Gen Systems: Enterprise InteroperabilityMany complex information structures

Many groups working on semantics: schemas+

Complex exchanges between platformsBusiness & Integration processes (scenarios)

Consolidation of standards – less overlap

Reduce complexity, easier decisions, …Faster progress

New architecture with bigger scope:Service-based (SOA, SBA, …)

Scope includes other platforms:Microsoft, Oracle, SAP, IBM, …

Thomas J. Burke 3

The Enterprise IOp Challenge …OPC Foundation Taking on a Larger Role

User Environment

Views & Concepts

User Defined

Standard Msgs

Custom & Vendor Specific

Vendor ApplicationExperts

RemovableMedia

Local & Hidden1

IsolatedLevel

(Manual)

A

Manual Coordination

Basic Sharing PossibleB

Proprietary or simplistic

Exchanged Occasionally

C2

ConnectedLevel

(Open)

A

Scenarios

B

Messaging, File Transfers, Remote

Procedure Calls

SynchronizedSelective Visibility & Collaboration

C3

IntegratedLevel

(Selective)

A

Standardized & Extensible

Processes and Scenarios

Collaborative

B

Built Into Architecture & Service-based

Common Sharing Models

C4

UnifiedLevel

( Standardized)

A

User Tunable Standard

ProcessesB

Transparent & Invisible

Flexible Analytics on

Common Models

User Tunable Role-Based

Collaborative Environments

C5

DynamicLevel

(Flexible)

CommunicationsInformation & Knowledge

Process & Workflow

People

Interoperability AttributesMaturity LevelEnvironment

Increasing Maturity

2006

Next

Thomas J. Burke 4

Suppliers Platforms Are Required for UnificationNot Enough Industry Standards – Will Be Evolutionary

Communications

ContextViews &Concepts

Unified Information& Events

Unified Processes &Workflow

Production ManagementManufacturing Operations

Business ManagementBusiness Operations

Product Definitions & Production Capabilities

WIP & Inventory Status

ProductionOrders

OrderCompletion& ResourceConsumption

NAEMEA Asia

SuppliersPLM Logistics

Customers

Thomas J. Burke 5

Custom Integration

Technology Platform

Technology PlatformTechnology Platform

OPC Unified ArchitectureA Basis for Unifying “Aspects of” Supplier Platforms?

PAMLIMS

CPM/AutomationData

TMSWM

S

Equipment

Operations Apps Platform

PDM

P&IDsModels

EquipmentSpecs

Drawings

Design & Eng. Apps Platform

Enterprise Apps Platform

CRMSCM

FINERP EAMContent

StandardsStandards

Standards

StandardsStandards

Partners Customers

Thomas J. Burke 6

Platform Concepts DefinedOPC UA: Unify Component Frameworks?

Application Products & Suites

Integration Server, Messaging, Directory Services, …

Industry Specific Extensions

Role-based Portal EnvironmentWorkflow ManagementData Management, …

Application Configurations

Operating System - Networking

Monito

r &

Manage

Security

Technology

Platform

ApplicationPlatform

Application Component Frameworks

Thomas J. Burke 7

Enterprise Interoperability Fundamentals

Existing OPC Interfaces within new capabilities …Component-based information modeling

Operations Application must have Flexible Asset and Resource Modeling

Accommodate many semantic standardsISA/B2MML, OAGi, RosettaNet, CIDX, …

Support standard messaging (above)Support reliable enterprise-wide orchestration

Within Enterprise and Operations Platform ToolsStrong security integrated with infrastructure

Better management of security information

Thomas J. Burke 8

Where Does OPC UA Help?(Definitely a work in progress)

(Does not specify user data management, …)Encryption, Digital Signatures, PKIWeb Service Security StandardsTraceability & Audit Records required

Security

(Does not address orchestration)… Exposes common services (for Orchestration)… Exposes Standardized Programming I/F’s… Provides common state model for managing services

Unified Orchestration

(Does define or address messaging)Complements Industry Standards Create and expose Object Commands (Methods and Programs)

Unified Messaging

(Does define semantics or address mapping to Apps)Complements Industry StandardsCreate and Expose Object Structures

Unified Semantics

(Does not define data models)Provides Common Object Management MethodsSupports more complex and flexible models

Unified Data Models

Existing OPC I/F’s …Subscription Model

Support Legacy Systems

OPC UAE-IOp

Thomas J. Burke 9

How is OPC UA Going to Work?Use UA-Based Software Supplier Platforms and Tools

Communications

ContextViews &Concepts

Unified Information& Events

Unified Processes &Workflow

Provide Tools to “Import” Industry Standards into UA and Create Shared UA Objects and Commands

Provide Tools to Create andExpose Application Object Info and Commands

as UA Services and Programming I/Fs

Use Platform Tools (Portal, UI, …) to Create Role-Based Common Views by

Browsing and AccessingShared UA Objects and Commands

Use Platform Tools (BPM, EAI, …) toCreate Processes and Mappings by

Browsing and AccessingShared UA Objects and Commands

OPC UA Server Suppliers

OPC UA Client Suppliers

“Conform to UA Security Guidelines”

Thomas J. Burke 10

Questions:Once we Understand …

Explore the Implementation of UAHow will Commands get created?

How will industry standards (semantics, messages, …) be used on OPC UA?How do we expect Enterprise Apps to use OPC UA?

What do we expect suppliers to implement?

Will OPC Foundation manage any shared code?

Who is working on UA and what are their deliverables?How can we become more aware of its status and monitor its progress?

(If we run out of important things to talk about)OPC UA talks about Objects - How does OPC UA compare to CORBA?

Thomas J. Burke 11

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…

Thomas J. Burke 12

Numerous Incompatible Protocols

CCCC--LinkLinkTCPTCP

EthernetEthernet

HARTHART

OAGISOAGIS

DDEDDE

COMCOM

BAPIBAPIDeviceNetDeviceNet

ProfiBusProfiBus

FieldBusFieldBus

OPCOPC--DADA

HTTPHTTP

WMIWMI

SOAPSOAP

OPCOPC--A&EA&EDCOMDCOM

802.1x802.1x

802.11802.11

IPv4IPv4UDPUDP

CANCAN

RSRS--232232

IPv6IPv6

IPXIPX

OLEOLE

FTPFTP

OPCOPC--HDAHDA

KerberosKerberos

J1939J1939

ModbusModbusFDIFDI

CANopenCANopenASAS--II

InterbusInterbus

IndustrialIndustrialEthernetEthernet

ControlNetControlNet

DeviceLogixDeviceLogixDHCPDHCP

DNSDNS

XMLXML

BluetoothBluetoothLonworksLonworks

FIPIOFIPIO

FirewireFirewire

USBUSBRSRS--423423

RSRS--485485RSRS--422422

IPsecIPsec

netDDEnetDDE

802.3802.3 V.35V.35

RARPRARP

ARPARP

ICMPICMP

EBCDICEBCDICANSIANSI

CORBACORBA

.NET .NET RemotingRemoting

SNMPSNMP

UNICODEUNICODE

Thomas J. Burke 13

The Inter-Enterprise Nightmare

Manufacturer

SuppliersPlants

Application X ...

DCS ControllerPLC

Application Y

The ProblemMany different vendorsCustom made solutionsProprietary technologiesPoint-to-point IntegrationLimited “real-time” informationMaintenance nightmareMultiple dependencies

Solution

OPC Unified Architecture

P

L

P

L

P

L

P

L

APPLICATIONPACKAGES

MIS

Dev

ice

Dat

a Configuration

Thomas J. Burke 14

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

Thomas J. Burke 15

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 or related functions and procedures that perform some specific service that the COM object will provide.

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

COM Interfaces

Thomas J. Burke 16

OPC Unified Architecture Motivation

OPC-UA

DCOMretires

.NETnew

Communicationarchitecture

Better

Integration(DA, HDA, AE)

More Areas of

Application(MES, ERP)

Internet

ServiceOriented

Thomas J. Burke 17

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.

Thomas J. Burke 18

OPC Unified Architecture

Web Services / XMLEasy Configuration and MaintenanceIncreased VisibilityBroader ScopeReliability Reliability ReliabilitySecurity Security SecurityPerformance Platform NeutralityLegacy Products Plug Right In…

Thomas J. Burke 19

SOA (Service Oriented Architecture)

Single set of ServicesQuery, Read, Write, Subscribe…

OPC Interface Unification

Historical Data

Access

Alarms&

Events

ComplexData

Commands

DataAccess

The UA Server embodies the functionality of existin g OPC Serversusing a single set of services

UA ServerUA Server

Thomas J. Burke 20

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!

Thomas J. Burke 21

OPC Unified Architecture Base

ArchitectureIntegration of DA, A&E, Commands, Complex Data, and Object Types

Designed for Federationabstract data/ information from the plant floor, through information models, and up to enterprise systems

Information Modelingdevelopment and deployment of standard information models to address industry domains specifics

Complex DataOPC Standard & Domain & vendor specific…..

Thomas J. Burke 22

OPC Unified Architecture Base

SecurityCollaboration, Development & Reference

Enterprise IntegrationOPC UA standard messaging system

Robustness / Reliability Designed & Built in….NO FailuresSequence numbers, keep-alives, resyncing, and support for redundancy

Commands

Companion Standardsindustry groups define what OPC Unified Architecture “transports”

Thomas J. Burke 23

Putting it all together

DataModel

SOA Model

OPC OPC UAUA

CommsModel

ProtocolIndependent

PlatformIndependent

Plant floorand Internet

Access

DA, HDA, and A&E

ObjectModel

TypeDescriptions

Abstract Services

Thomas J. Burke 24

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

PCPC--Based ControlBased Control

MESMES

OPC OPC

OPCOPC

Industrial NetworksIndustrial Networks DataAcquisition

DataAcquisition

PLCDCS

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

ERP, SAP ERP, SAP …… Corporate EnterpriseCorporate Enterprise

OPC Unified Architecture OPC Unified Architecture

Thomas J. Burke 25

OPC - Going Forward (Technology)

Thomas J. Burke 26

OPC (First Generation)• Connectivity • Real-time data,

Alarms, Historical Data

• OPC DA• OPC A&E• OPC HDA• OPC XML• OPC…

OPC Roadmap

OPC (UA Generation)

• Robustness & Reliability

• Interoperability• Connectivity

• Compliance & Certification

• MES & ERP Connectivity

• Profile support• OPC UA Core

• OPC DA• OPC UA - A&E• OPC UA - HDA

• Next Significant Step

• Diagnostics• System Administration• Configuration Change

Notification• Consistency Check

between layers

Thomas J. Burke 27

Vision

Transition from Device Connectivity to Data connect ivity

Thomas J. Burke 28

OPC is Dedicated to Interoperability

SecurityReliabilityInteroperability PerformanceAdopted StandardOpen PlatformAutomation to Enterprise IntegrationOpenness, Productivity & Collaboration

Thomas J. Burke 29

Questions?

Thomas J. BurkeOPC Foundation President

& Executive [email protected]