1 / 46

HMI-50 Open Standards with OPC Interoperability

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

oren
Télécharger la présentation

HMI-50 Open Standards with OPC Interoperability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HMI-50 Open Standards with OPC Interoperability

  2. Welcome 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

  3. HMI-50 ICONICS Summit 2006 OPC Unified Architecture

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

  5. OPC Provides Industry-Standard interOperability, Productivity & Collaboration Corporate Enterprise OPC Unified Architecture Manufacturing, Production and Maintenance OPC Unified Architecture Adv. Control HMI MES SCADA Batch OPC OPC OPC PC-Based Control OPC PLC DCS Industrial Networks Data Acquisition ??.......??

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

  7. OPC Interface Unification Alarms&Events • SOA (Service Oriented Architecture) • Single set of Services • Query, Read, Write, Subscribe… • Named/Typed relationships between nodes. DataAccess Historical DataAccess Commands ComplexData UA Server The UA Server embodies the functionality of existing OPC Servers using a single set of services

  8. Unified Object Model

  9. OPC-UA Address Space • Full Mesh – Network Model • Unlimited Named/Typed Relationships • “Views” are used to present hierarchies

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

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

  12. 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)

  13. 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()

  14. 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)

  15. ServerCluster Mainframe devices portables desktops servers clusters mainframes Server DesktopPC Portables Controllers Embedded Systems UA Scalability Standard internet protocols allow cross-platform communication • Multiple UA APIs • C/C++ • JAVA • Microsoft .NET

  16. Vendor Information Model Information Model Specifications OPC UA Base Services DA A&E HDA CMDs All Necessary Services OPC Information Model IEC, ISA, MIMOSA … Specification Layering Clients written to just the base can still discover and access all data from the derived layers!

  17. OpenO&M Relationship Relationship OPC Collaboration MIMOSA • OpenO&M – Joint work by MIMOSA, OPC & ISA-95 to integrate operations and maintenance information • ISA Standards • ISA-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 • WBF • BatchML – 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 OPC WBF OMAC BatchML ISA ISA-99 ISA-95 B2MML OpenO&M MFG JWG

  18. Architecture Vision Q4 / 03 Implementation Sub-Committee Formed Q1 / 05 Phase One Ref. ImplementationQ4 / 06 UA Committee Formed Q1/ 04 Phase One Spec. Release Q2 / 06 Promote Phase One Worldwide Q4 / 06 OPC Unified Architecture Roadmap OPC Unified Architecture Milestones

  19. More Information … Visit the UA ‘home’ page http://www.opcfoundation.org/UA

  20. GraphWorX Interoperability with the KepWare OPC Server • Let’s take a look at OPC in Action! • (demo)

  21. OPC, It’s just that easy OPC Compliance, Interoperability, and Certification By Mark Hensley

  22. Making OPC Reliable and Easy • 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

  23. 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 vendors • We want “Plug and Play” not “Plug and Pray” • How do we get there?

  24. OPC Compliance Test Tool (CTT) • The OPC Foundation provides a Compliance test for OPC Server vendors • Actions 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 Foundation • The Server vendors can choose to submit their results to the OPC Foundation • Many vendors use the OPC Compliance tool as a part of their normal testing • Unfortunately 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

  25. OPC Interoperability (IOP)

  26. OPC Interoperability (IOP) • The OPC Foundation host Interoperability Meetings each year • Multiple worldwide locations • US, Germany, Japan • OPC Vendors test their products against each other • Testing takes a full week (12 hour days) • Vendors are encouraged to bring source code and make fixes on the spot • The goal is to reduce and eliminate OPC issues before customers encounter them • Unfortunately not every vendor takes advantage of this opportunity

  27. Continual Improvement OPC Certification (Future) • True Third Party Certification • Testing Labs to be establish worldwide • Test Labs will be sanctioned by the OPC Foundation • Test both OPC Servers and OPC Clients • Test procedures will be standardized across all labs • Specifications for OPC Certification and Test Lab operation are well underway

  28. Where to Learn More www.opcfoundation.org

  29. What to look for • How to know if a product is Compliant and Certified CurrentSelf Tested Compliance Logo New Self Tested Compliance Logo New Certified Compliance Logo

  30. What You Can Do • Buy OPC products only from OPC Members • Ask your vendor when they last attended an Interoperability workshop • Buy OPC products that have passed Compliance • Push your vendors to do all of the above

  31. Questions Thank You

  32. HMI-50 ICONICS Summit 2006 OPC ToolWorX 3.2

  33. OPC ToolWorX • OPC ToolWorX; Rapid Development Tool for creating OPC Standards Compliant OPC Servers - FAST • Compatible 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

  34. OPC 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

  35. OPC ToolWorX is easy for Developers 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

  36. Built-In Features of OPC ToolWorX Servers • Error Logging • To XML files via TraceWorX • To NT Event Log • Recursive 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

  37. Developer 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

  38. Developer 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

  39. OPC ToolWorX 3.2 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

  40. OPC ToolWorX 3.2 Anomalies Addressed • Item Data Type Conversion issue • Several CE compile issues • Issues with Background Polling – New Centralized Background Polling • Enhanced algorithm to provide LowEU, HighEU, LowIR, and HighIR properties • Expanded all Text fields to 255 Characters (OPC Tag Name is still 50 Characters) • Issues with OPC Updates on Inactive Tags

  41. OPC ToolWorX v4 - Overview • Based on OPC Unified Architecture model and Web based standards • Implement all OPC specifications (DA, AE, HDA, Commands, Complex Data …) in one server • Use latest Microsoft technologies (.NET 2.0, Windows Communication Foundation, VS2005, Windows Presentation Foundation, …) • Fully rewritten in managed code (C#, C++)

  42. OPC ToolWorX v4 - Objectives • OPC ToolWorX 3.1 Migration Path • Continue to improve overall performance • Use XML as a transport protocol • Network protocol independent • Strong built-in security model • (OPC clients present credentials to the server) • Designed for easy redundancy • Clients • Servers

  43. OPC Foundation Promote OPC UA Worldwide 2006 Architecture visionQ1/ 05 OPC UA Phase One Spec. & Ref. ImplementationQ4 / 05 OPC ToolWorX v4 Q4 / 07 OPC ToolWorX v4 - Roadmap OPC ToolWorX V4 Milestones

  44. OPC 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

  45. OPC ToolWorX 3.2 Demonstration • We will build a Modbus OPC Server using Wizards • Runtime Executable Creation • Configuration Executable Creation • Sample Configuration Database

  46. HMI-50 ICONICS Summit 2006 Questions?Ready for the Quiz? Let’s Go!

More Related