hmi-50 open standards with opc interoperability

46
ICONICS Worldwide Customer Summit – September 2006 HMI-50 Open Standards with OPC Interoperability

Upload: oren

Post on 06-Jan-2016

35 views

Category:

Documents


2 download

DESCRIPTION

HMI-50 Open Standards with OPC Interoperability. Welcome and Introductions. Session Participants: Jim Luth – OPC UA Presentation Mark Hensley – OPC Interoperability and Compliance Rudolf Griessl – ICONICS OPC ToolWorX - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: HMI-50 Open Standards with OPC Interoperability

ICONICS Worldwide Customer Summit – September 2006

HMI-50 Open Standards with OPC InteroperabilityHMI-50 Open Standards with OPC Interoperability

Page 2: HMI-50 Open Standards with OPC Interoperability

2

Welcome and IntroductionsWelcome and Introductions

Session Participants:

• Jim Luth – OPC UA Presentation• Mark Hensley – OPC Interoperability and

Compliance• Rudolf Griessl – ICONICS OPC ToolWorX• Contributors: Michael Hiefner, Pavel

Tucek, Milan Prochazka, and Josh Obal

• Session Coordinator: Jon Brown

Page 3: HMI-50 Open Standards with OPC Interoperability

ICONICS Worldwide Customer Summit – September 2006

OPC Unified Architecture OPC Unified Architecture

HMI-50 ICONICS Summit 2006

Page 4: HMI-50 Open Standards with OPC Interoperability

4

OPC Unified Architecture MotivationOPC Unified Architecture Motivation

OPC-UA

DCOMretires

.NETnew

Communicationarchitecture

Better

Integration(DA, HDA, AE)

More Areas of

Application(MES, ERP)

Internet

ServiceOriented

Page 5: HMI-50 Open Standards with OPC Interoperability

5

OPC Provides Industry-Standard OPC Provides Industry-Standard interinterOOperability, perability,

PProductivity & roductivity & CCollaborationollaboration

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

OPC OPC

OPCOPC

Industrial NetworksIndustrial Networks DataAcquisition

DataAcquisition

PLCDCS

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

Corporate EnterpriseCorporate Enterprise

OPC Unified Architecture OPC Unified Architecture

Page 6: HMI-50 Open Standards with OPC Interoperability

6

OPC-UA FundamentalsOPC-UA Fundamentals

Based on standards for the Web•XML, WSDL, SOAP, WS-*WS-Policy negotiates protocol and encodingWS-SecureConversation provides secured sessionsOptimized for the Intranet• OPC Binary encoding over TCP

Page 7: HMI-50 Open Standards with OPC Interoperability

7

SOA (Service Oriented Architecture)

Single set of Services• Query, Read, Write,

Subscribe…

Named/Typed relationships between nodes.

OPC Interface UnificationOPC 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

Page 8: HMI-50 Open Standards with OPC Interoperability

8

Unified Object ModelUnified 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

Page 9: HMI-50 Open Standards with OPC Interoperability

9

OPC-UA Address SpaceOPC-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

Page 10: HMI-50 Open Standards with OPC Interoperability

10

RobustnessRobustness

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

Page 11: HMI-50 Open Standards with OPC Interoperability

11

SecuritySecurity

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.

Page 12: HMI-50 Open Standards with OPC Interoperability

12

Abstract UA ModelSpecification

WSDL / SOAPor TCP / Binary

Services Binding

Proxy /Stubs

API

Communication LayeringCommunication Layering

Tool orLanguageDependent(e.g. .NET)

Scalable Platform Independent Messaging Model

.NET (WCF) VersionPortable C/C++ VersionJava Version

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

Page 13: HMI-50 Open Standards with OPC Interoperability

13

Methods vs. Methods vs. ProgramsPrograms

Programs built on top of MethodsPrograms 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 BaseSynchronous invocation similar to blocking function calls.• AckAlarm()

Page 14: HMI-50 Open Standards with OPC Interoperability

14

Complex Data FeaturesComplex Data Features

Tells clients how to parse structured dataAllows use of XML Schemas for describing XML dataDefines 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)

Page 15: HMI-50 Open Standards with OPC Interoperability

15

MainframeMainframe

UA ScalabilityUA Scalability

PortablesPortables

DesktopDesktopPCPC

ServerServer

ServerServerClusterCluster

EmbeddedEmbeddedSystemsSystems

devices porta

bles desktops servers clusters m

ainframes

devices porta

bles desktops servers clusters m

ainframes

ControllersControllers

Standard internet protocols allow cross-platform communication

Multiple UA APIs•C/C++•JAVA•Microsoft .NET

Page 16: HMI-50 Open Standards with OPC Interoperability

16

OPC UA Base Services All Necessary Services

Specification LayeringSpecification Layering

Vendor Information Model

DA A&E HDA CMDs OPC Information Model

Information Model Specifications IEC, ISA, MIMOSA …

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

Page 17: HMI-50 Open Standards with OPC Interoperability

17

OPC CollaborationOPC Collaboration

MIMOSA

B2MMLISA-95

ISA

OMAC

BatchML

WBFOPC

OpenO&M Relationship

Relationship

OpenO&M

MFG JWG

ISA-99

OpenO&M – Joint work by MIMOSA, OPC & ISA-95 to integrate operations and maintenance information

ISA StandardsISA-95 – Enterprise/Control System Interface

Standard, Parts 3 & 4 define MES Functions

ISA-99 – Control System Cyber-Security Standard

OMAC – Open Modular Architecture Controls group standardizing packaging machinery interfaces

WBFBatchML – XML Schemas based on ISA-88

B2MML – XML Schemas based on ISA-95

OPC – DCOM and XML interfaces. New Web Services Unified Architecture (UA) under development

MIMOSA – Asset Mgt and Maintenance Mgt Schema, Meta Data and Interfaces

Page 18: HMI-50 Open Standards with OPC Interoperability

18

UA Committee UA Committee FormedFormedQ1/ 04Q1/ 04

Phase One Spec. Phase One Spec. Release Release Q2 / 06Q2 / 06

OPC Unified Architecture RoadmapOPC Unified Architecture Roadmap

OPC Unified Architecture MilestonesOPC Unified Architecture Milestones

Architecture VisionArchitecture VisionQ4 / 03Q4 / 03

Implementation Sub-Implementation Sub-Committee FormedCommittee Formed

Q1 / 05Q1 / 05

Phase One Phase One Ref. ImplementationRef. Implementation

Q4 / 06Q4 / 06

Promote Phase One Promote Phase One WorldwideWorldwide

Q4 / 06Q4 / 06

Page 19: HMI-50 Open Standards with OPC Interoperability

19

More Information …More Information …

Visit the UA ‘home’ page

http://www.opcfoundation.org/UA

F O U N D A T I O N

®

Page 20: HMI-50 Open Standards with OPC Interoperability

20

GraphWorX Interoperability GraphWorX Interoperability with the KepWare OPC Serverwith the KepWare OPC Server

Let’s take a look at OPC in Action!- (demo)

Page 21: HMI-50 Open Standards with OPC Interoperability

ICONICS Worldwide Customer Summit – September 2006

OPC Compliance, Interoperability, and CertificationOPC Compliance, Interoperability, and Certification

OPC, It’s just that easy

By Mark Hensley

Page 22: HMI-50 Open Standards with OPC Interoperability

22

Making OPC Reliable and Making OPC Reliable and EasyEasy

What we will Cover• Issues that effect OPC reliability• How the OPC Foundation has addressed

these issues• Continued Improvement, OPC Third Party

Certification• How to know the Compliance and

Certification status of a product• What you can do

Page 23: HMI-50 Open Standards with OPC Interoperability

23

Problems and their Causes Problems and their Causes

The Problems:• OPC technology is complex to design• Vendor interpretations of OPC specifications

can vary• Interactions between OPC products can result

in unique issues• Quality control can vary from vendor to vendor• No guarantee of cooperation between vendorsWe want “Plug and Play” not “Plug and Pray”How do we get there?

Page 24: HMI-50 Open Standards with OPC Interoperability

24

OPC Compliance Test Tool (CTT)OPC Compliance Test Tool (CTT)

The OPC Foundation provides a Compliance test for OPC Server vendorsActions Performed by the Compliance test• Test the OPC Servers adherence to the specifications• Stresses basic server operation (speed, memory

management)• Generates an encrypted results file sent to the OPC

FoundationThe Server vendors can choose to submit their results to the OPC FoundationMany vendors use the OPC Compliance tool as a part of their normal testingUnfortunately at this time there is no compliance test for OPC Client products• Client applications can perform operations that negatively

impact even a compliant OPC server

Page 25: HMI-50 Open Standards with OPC Interoperability

25

OPC Interoperability (IOP)OPC Interoperability (IOP)

Page 26: HMI-50 Open Standards with OPC Interoperability

26

OPC Interoperability (IOP)OPC Interoperability (IOP)

The OPC Foundation host Interoperability Meetings each year• Multiple worldwide locations

- US, Germany, Japan

OPC Vendors test their products against each otherTesting takes a full week (12 hour days)Vendors are encouraged to bring source code and make fixes on the spotThe goal is to reduce and eliminate OPC issues before customers encounter themUnfortunately not every vendor takes advantage of this opportunity

Page 27: HMI-50 Open Standards with OPC Interoperability

27

Continual Continual ImprovementImprovement OPC Certification OPC Certification (Future) (Future)

True Third Party CertificationTesting Labs to be establish worldwideTest Labs will be sanctioned by the OPC FoundationTest both OPC Servers and OPC ClientsTest procedures will be standardized across all labsSpecifications for OPC Certification and Test Lab operation are well underway

Page 28: HMI-50 Open Standards with OPC Interoperability

28

Where to Learn MoreWhere to Learn More

www.opcfoundation.org

Page 29: HMI-50 Open Standards with OPC Interoperability

29

What to look forWhat to look for

How to know if a product is Compliant and Certified

New Self Tested

Compliance Logo

New Certified

Compliance Logo

CurrentSelf

Tested Complianc

e Logo

Page 30: HMI-50 Open Standards with OPC Interoperability

30

What You Can DoWhat You Can Do

Buy OPC products only from OPC MembersAsk your vendor when they last attended an Interoperability workshopBuy OPC products that have passed CompliancePush your vendors to do all of the above

Page 31: HMI-50 Open Standards with OPC Interoperability

31

QuestionsQuestions

Thank You

Page 32: HMI-50 Open Standards with OPC Interoperability

ICONICS Worldwide Customer Summit – September 2006

OPC ToolWorX 3.2 OPC ToolWorX 3.2

HMI-50 ICONICS Summit 2006

Page 33: HMI-50 Open Standards with OPC Interoperability

33

OPC ToolWorXOPC ToolWorX

OPC ToolWorX; Rapid Development Tool for creating OPC Standards Compliant OPC Servers - FASTCompatible with Visual Studio 2005 and earlier versions.OPC ToolWorX OPC Servers are compliant with:• Data Access v2.05a• Data Access v3.0 – including “queuing” interface• Complex Data v1.0• Alarms & Events v1.1 including the optional

enable/disable conditions interfaces

Page 34: HMI-50 Open Standards with OPC Interoperability

34

OPC ToolWorXOPC ToolWorX

OPC ToolWorX Supports XML! • OPC XML Data Access• .NET Web Service Wrapper

- Web Enables any OPC DA 2.0 or 3.0 Server- Redistributable with ToolWorX Servers- Requires IIS- Can run on a different machine from the COM

Server.

OPC ToolWorX OPC Servers Support Simple and Tracking Events

Page 35: HMI-50 Open Standards with OPC Interoperability

35

OPC ToolWorX is easy for OPC ToolWorX is easy for Developers to UseDevelopers to Use

These features are built into OPC ToolWorX OPC Servers:• Online configuration

- Configuration changes made in the Configurator are reflected in the running server without a restart.

• XML import / export- Allows external XML applications access to the configuration

data- New non-database format for CE and embedded servers to

read configuration• Statistics and Counters

- Via OPC interface - Via Stats Utility Application

Page 36: HMI-50 Open Standards with OPC Interoperability

36

Built-In Features of OPC Built-In Features of OPC ToolWorX ServersToolWorX Servers

Error Logging• To XML files via TraceWorX• To NT Event LogRecursive address space• Eliminates the need to have multiple DB tables

to store the same object on different levels in the hierarchy

Unsolicited Device Communication• Data Access• Alarms & Events

Page 37: HMI-50 Open Standards with OPC Interoperability

37

Developer Ease of UseDeveloper Ease of Use

Memory and CPU optimizations• Minimize footprint of servers with a large

address space• Add lightweight classes eliminating properties

that are rarely used

Wizards to create more server types:• Simple Server – minimize overrides• Complex Server – show all features

Page 38: HMI-50 Open Standards with OPC Interoperability

38

Developer Ease of UseDeveloper Ease of Use

Ethernet TCP/IP helper classes• Modeled after the existing serial port helper

classes

New documentation and examples:• Background Polling• Active Scan• Channels• Dormant Points• Registry Settings

Page 39: HMI-50 Open Standards with OPC Interoperability

39

OPC ToolWorX 3.2 OPC ToolWorX 3.2 Released!Released!

Wizard-Driven Support for Creation of Runtime and Configuration Executables in Visual Studio 2005!Many small fixes and enhancements• Simulation of all elements in Arrays• Improvements to Background Polling Mechanisms• OPC DA 3.0 support for EUType and EUInfo

properties• Updated OPC Core Components to v. 2.30• Added notification of OPC Configuration Changes

Page 40: HMI-50 Open Standards with OPC Interoperability

40

OPC ToolWorX 3.2 Anomalies OPC ToolWorX 3.2 Anomalies AddressedAddressed

Item Data Type Conversion issueSeveral CE compile issuesIssues with Background Polling – New Centralized Background PollingEnhanced algorithm to provide LowEU, HighEU, LowIR, and HighIR propertiesExpanded all Text fields to 255 Characters (OPC Tag Name is still 50 Characters)Issues with OPC Updates on Inactive Tags

Page 41: HMI-50 Open Standards with OPC Interoperability

41

OPC ToolWorX v4 - OPC ToolWorX v4 - OverviewOverview

Based on OPC Unified Architecture model and Web based standardsImplement all OPC specifications (DA, AE, HDA, Commands, Complex Data …) in one serverUse latest Microsoft technologies (.NET 2.0, Windows Communication Foundation, VS2005, Windows Presentation Foundation, …)Fully rewritten in managed code (C#, C++)

Page 42: HMI-50 Open Standards with OPC Interoperability

42

OPC ToolWorX v4 - OPC ToolWorX v4 - ObjectivesObjectives

OPC ToolWorX 3.1 Migration PathContinue to improve overall performance Use XML as a transport protocolNetwork protocol independent Strong built-in security model • (OPC clients present credentials to the server)

Designed for easy redundancy• Clients• Servers

Page 43: HMI-50 Open Standards with OPC Interoperability

43

Architecture visionArchitecture visionQ1/ 05Q1/ 05

OPC UA Phase One OPC UA Phase One Spec. & Ref. Spec. & Ref.

ImplementationImplementationQ4 / 05Q4 / 05

OPC ToolWorX V4 MilestonesOPC ToolWorX V4 Milestones

OPC Foundation OPC Foundation Promote OPC UA Promote OPC UA

Worldwide Worldwide 20062006

OPC ToolWorX v4OPC ToolWorX v4Q4 / 07Q4 / 07

OPC ToolWorX v4 - OPC ToolWorX v4 - RoadmapRoadmap

Page 44: HMI-50 Open Standards with OPC Interoperability

44

OPC ToolWorX 3.2OPC ToolWorX 3.2

Upgrades are available for earlier versions of OPC ToolWorX• Upgrade Wizards provided to update your OPC

Server Code to 3.2

Available in three versions:• OPC ToolWorX 3.2 Lite

- DLL Only. Major OPC Functions provided as Dynamic Link Libraries

• OPC ToolWorX 3.2 Standard- Full Source Code provided for all functions

• OPC ToolWorX 3.2 Demo Mode- Produces Runtime Executable with a 2-hour Runtime Limit

Page 45: HMI-50 Open Standards with OPC Interoperability

45

OPC ToolWorX 3.2 OPC ToolWorX 3.2 DemonstrationDemonstration

We will build a Modbus OPC Server using Wizards• Runtime Executable Creation• Configuration Executable Creation• Sample Configuration Database

Page 46: HMI-50 Open Standards with OPC Interoperability

ICONICS Worldwide Customer Summit – September 2006

Questions?

Ready for the Quiz? Let’s Go!

Questions?

Ready for the Quiz? Let’s Go!

HMI-50 ICONICS Summit 2006