1. October 2006 Future of Real-time Architecture OPC Unified Architecture Thomas J. Burke OPC Foundation President & Executive Director

2. Thomas J.Burke2 The Plant : a Complex Environment with many opportunities for standards for interoperability Complex Information Flows Multi-vendor Proprietary Plant Servers Other Computing Devices PLANT INFORMATION NETWORK - Ethernet Area Servers Plant Network Modules Network Gateway Network Gateway CONTROL NETWORK Subnetwork Gateway Application Module History Module Personal Computer Network Manager Control Stations Archive Replay Module Additional CN Modules Fiber Optics Network Interface Module Other Data Hiway Boxes Multifunction Controller Extended Controller Basic Controller Advanced Multifunction Controller LocalProcessors Subnetwork CONTROL NETWORK Smartine Transmitters PLC Gateway Other Subsystems PLC Logic Manager Process Manager Advanced Process Manager Transmitters Control Network Extenders Asynchronous Processing Multiple Interfaces Mission Critical How To Manage Changes?  sec msec 1 sec secs min hours

3. Thomas J.Burke3 Numerous Incompatible Protocols CC-Link TCP Ethernet HART OAGIS DDE COM BAPI DeviceNet ProfiBus FieldBus OPC-DA HTTP WMI SOAP OPC-A&E DCOM 802.1x 802.11 IPv4 UDP CAN RS-232 IPv6 IPX OLE FTP OPC-HDA Kerberos J1939 Modbus FDI CANopen AS-I Interbus Industrial Ethernet ControlNet DeviceLogix DHCP DNS XML Bluetooth Lonworks FIPIO Firewire USB RS-423 RS-485 RS-422 IPsec netDDE 802.3 V.35 RARP ARP ICMP EBCDIC ANSI CORBA.NET Remoting SNMP UNICODE

4. Thomas J.Burke4 Numerous Incompatible Tiers Equipment sensors transmitters valves fieldnetworks NCmachines robots Station continuous controllers batch controllers NC controllers discrete controllers processmonitoring Cell cell controllers HMI DCS operator interfaces Section/Area materialdispatch performancemeasurement SCADA qualitysystems productionplanning process history areacontrollers Facility/Plant timeandattendance maintenancemanagement resourcemanagement productgenealogy WIPtracking PDM productionplanning Enterprise ERP CRM SCP SCE PLM R&D

5. Thomas J.Burke5 The Inter-Enterprise Nightmare Manufacturer Suppliers Plants Application X... DCS Controller PLC 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 APPLICATION PACKAGES MIS Device Data Configuration

6. Thomas J.Burke6 New Communications Underpinnings 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. Thomas J.Burke7 OPC Unified Architecture Motivation OPC-UA DCOM retires.NET new Communication architecture Better Integration (DA, HDA, AE) More Areas of Application (MES, ERP) Internet Service Oriented

8. Thomas J.Burke8 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 Complex Data Commands Data Access The UA Server embodies the functionality of existing OPC Servers using a single set of services UA Server

9. Thomas J.Burke9 New Security Model 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.

10. Thomas J.Burke10 New 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)

11. Thomas J.Burke11 OPC UA Base Services All Necessary Services Designed to expose models Vendor Information Model DAA&EHDACMDs 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!

12. Thomas J.Burke12 Unified Object Model

13. Thomas J.Burke13 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

14. Thomas J.Burke14 Mainframe UA Scalability Portables Desktop PC Server Server Cluste r EmbeddedSystems devices portables desktops servers clusters mainframes Controllers Standard internet protocols allow cross-platform communication Multiple UA APIs C/C++ JAVA Microsoft.NET

15. Thomas J.Burke15 Existing OPC Features Retained Address Space visibility through browsing & query Efficient report-by-exception communication Similar base information models for easy adapters DAA&EHDACMDs OPC Information Model

16. Thomas J.Burke16 Solutions Example Problems Solved with OPC UA Solutions…

17. Thomas J.Burke17 Remote Access PROBLEM: I need fast, secure remote access to data via the internet to my supply chain partner. SOLUTION: OPC-UA using HTTP and UA Binary encoding

18. Thomas J.Burke18 ISA S95 Modeled Plant PROBLEM: I modeled my plant using ISA S95 and I want the metadata in the model available as well as the real-time data. SOLUTION: OPC-UA is designed to expose model metadata and there will be a UA companion spec. for S95

19. Thomas J.Burke19 OPC in device PROBLEM: I want to supply an OPC interface to my device without the use of an external Windows PC SOLUTION: OPC-UA is cross-platform and embeddable HMI OPC UA Server OPC COM Server

20. Thomas J.Burke20 Java based ERP PROBLEM: My Java based ERP system needs data from MES and the factory floor SOLUTION: OPC volunteers are creating a UA communication stack and API in Java

21. Thomas J.Burke21 Redundancy PROBLEM: EDF needs redundancy in nuclear applications SOLUTION: UA defines how redundancy is done for consistency between all UA applications

22. Thomas J.Burke22 OPC is Dedicated to Interoperability Security Reliability Interoperability Performance Adopted Standard Open Platform Automation to Enterprise Integration Openness, Productivity & Collaboration

23. Thomas J.Burke23 Questions? Thomas J. Burke OPC Foundation President & Executive Director Thomas.Burke@opcfoundation.org

24. Thomas J.Burke24 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

25. Thomas J.Burke25 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…

26. Thomas J.Burke26 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…..

27. Thomas J.Burke27 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 Programs Companion Standards industry groups define what OPC Unified Architecture “transports”