Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Inside Story: How OPC UA and DDS Can Work Together in Industrial Systems

Originally presented on June 15, 2016.

Watch On-Demand:

  • Login to see the comments

The Inside Story: How OPC UA and DDS Can Work Together in Industrial Systems

  1. 1. The Inside Story: How OPC UA and DDS Can Work Together in Industrial Systems Stan Schneider, PhD. RTI CEO, IIC Steering Committee Thomas Burke, President, The OPC Foundation
  2. 2. Agenda  Technology, benefits, & applications – OPC UA – DDS  Working together – Industrie 4.0 and IIC architecture integration – OPC UA and DDS integration  Bottom line – Compare in a nutshell – Analyze your problem & mindset – Start without fear of misstep
  3. 3. Thomas J. Burke President & Executive Director
  4. 4. • The OPC Foundation is the world’s leading community for interoperability solutions based on OPC specifications that deliver universal connectivity. Community: • The mission of this community is to advance the development, adoption and certification of OPC based products through global collaborations. Collaboration: • The Foundation is the official source for the OPC Certification Program, ensuring that OPC products plug-and-play in real-world application. Compliance:
  5. 5. OPC Foundation Scottsdale, Arizona OPC Europe Verl, Germany OPC Japan Musashino-shi, Tokyo  Vision secure, reliable, multi-vendor, multi-platform, multi domain interoperability from sensor to enterprise  International ◦ Companies from Automation & IT ◦ International standard IEC62541 OPC Asia China
  6. 6. Thomas J. Burke OPC Foundation President & Executive Director
  7. 7. Proprietary OPC UA (Embedded)OPC UA (PC) S S S S UA UA UA UA UA Client UA Client
  8. 8. Open Data Connectivity Connectivity Standards Protocols
  9. 9. Data Context Preservation OPC UA
  10. 10. • Ground-Up Secure Design • Based on latest security standards • Accepted by IT and OT groups • Recognized for its security by key organizations: • NIST • Industrie 4.0 • MDIS • … Data Security
  11. 11. OPC UA Meta Model Built-in Information Models Companion Information Models Vendor Specific Extensions OPC UA Publish/Subscriber Communication Model  Generic Pub-Sub Information Model under development  Evaluation of existing protocols ongoing Client/Server Services Protocols Pub-Sub Model PubSubConfiguration Connections MessageWriters Protocols UA Secure Multicast AMQP More to evaluate
  12. 12. OPC UA Server Address Space Subscriber NSubscriber 1OPC UA Client A Client A Session Publish Message Oriented Middleware Subsciption MessageWriter DataSet Publisher OPC UA Application
  13. 13. OPC UA Server Address Space OPC UA Client C OPC UA Client B OPC UA Client A Client A Session Client B Session Client C Session Subsciption Publish Publish Publish Subsciption Subsciption
  14. 14. UDP Multicast Group OPC UA Subscriber OPC UA Subscriber OPC UA Subscriber OPC UA application Publisher Connection MessageWriter Message 276 OPC UA application Subscriber Connection MessageReader Message 276 Message 276 Message 276 Message 276
  15. 15. OPC UA Server Product specific address space and data integration Publisher UA UDP Multicast OPC UA Server Product specific address space and data integration Subscriber Send Receive OPC UA Client Configure Configure UA TCP / UA Binary  Existing OPC UA Server can be extended  Configuration through OPC UA Clients
  16. 16.  Requirements and Use Case ◦ Collected in 2014  Specification Work started ◦ Main work item of OPC UA WG ◦ Draft specification available  Information Model is getting stable  Protocol and security details next work item ◦ Main open issues  Meta data exchange  Reliable messaging for events
  17. 17. OPC UA: New Generation OPC  Definition 2003 – 2006  Verification and Implementation 2006 – 2008  Final OPC Foundation Release 2009  IEC 62541 Release 2010 – 2011  OPC UA = established OPC features + Platform independence + Standard internet and IP based protocols + Built in security features + Generic object model + Extensible type system + Scalability through profiles + Migration path from Classic OPC
  18. 18.  Communication infrastructure  OPC UA Provides multivendor multiplatform secure reliable interoperability for moving data/information from the embedded world to the enterprise!  High Perfomance & High Scalabilty  Rich Service Oriented Architecture  Industrial automation with integration into many other domains!  Information modelling  Rich, object oriented extensible type model  Support simple and complex models  Collaboration partners plug-n-play their information seamlessly into OPC UA Corporate Network Operations Network Plant Floor Network Firewall Controllers Controllers DCS HMI MES ERP Firewall Motor Starter 01 Configuration Control Function Local Operation Multifunction Input DI0 ParameterSet Motor Parameters Motor Current Low Motor Current High Service Info Number of Starts Motor Starter 01 Parameter Set Control Function Local Operation Configuration Multifunction Input DIO Motor Current Low Motor Current High Number of Starts Motor Current Low Motor Current High Service Info
  19. 19. Data Distribution Service (DDS)
  20. 20. The IIoT Disruption The real value is a common architecture that connects sensor to cloud, interoperates between vendors, and spans industries Common technology that spans industries brings bold new approaches and enables fast change
  21. 21. RTI’s Experience • ~1000 Projects – Healthcare – Transportation – Communications – Energy – Industrial – Defense • 15+ Standards & Consortia Efforts – Interoperability – Multi-vendor ecosystems
  22. 22. DDS Introduction Technology, benefits, & applications
  23. 23. The DDS Standard for the IIoT • The Data Distribution Service (DDS) is the Proven Data Connectivity Standard for the IoT • OMG: world’s largest systems software standards org – UML, DDS, Industrial Internet Consortium • DDS: open & cross-vendor – Open Standard & Open Source – 12+ implementations Interoperability between source written for different vendors Interoperability between applications running on different implementations DDS-RTPS Protocol Real-Time Publish-Subscribe Distribution Fabric DDS API
  24. 24. Data-Centric QoS-Aware Application Integration CRUD operations Persistence Service Recording Service Virtual Global Data Space DDS DataBus
  25. 25. Data Centricity Definition a) The interface is the data. b) The infrastructure understands that data. c) The system manages the data and imposes rules on how applications exchange data.
  26. 26. Data Centric is the Opposite of OO Object Oriented • Encapsulate data • Expose methods Data Centric • Encapsulate methods • Expose data Explicit Shared Data Model
  27. 27. Data Centricity Reliability, Scale, Speed, Control • Global Data Space – Automatic discovery – Read & write data in any OS, language, transport – Type Aware – Direct peer-to-peer – Redundant sources/sinks/nets • No Servers! • QoS control – Timing, Reliability, Redundancy, Ordering, Filtering, Security Shared Global Data Space DDS DataBus Signalized Intersection Vehicle Status Actuation Perception Obstacle Status Planning&Nav Cloud Offer: Write obstacle situation update 100x/sec Reliable for 10 secs Request: Read obstacle 10x/sec If distance < 200 m && velocity > 10
  28. 28. It’s Not About Patterns! • Publish-Subscribe • Request-Reply • Queuing 2004 2015 (Vendor products) 2013
  29. 29. DDS Benefits
  30. 30. Ensure Reliable Availability • What: Continuous operation >> 99.999% • How: Easy redundancy, no servers
  31. 31. Guarantee Real-Time Response • What: response < 100us, even with load, complex data types, many flows • How: peer-to-peer, multicast, data path optimization
  32. 32. Manage Complex Data Flow and State • What: Find and deliver the right information to the right place at the right time • How: Data centric selective source filtering
  33. 33. Ease System Integration • What: Manage interfaces between teams and modules • How: Explicit interface design, evolution, and enforcement
  34. 34. Example DDS Applications
  35. 35. Common Platforms Revolution® "GE Healthcare chose the DDS standard because it can handle many classes of intelligent machines. DDS satisfies the demanding requirements of our devices and supports standardization on a single communications platform across product lines." -- J Gustavo Perez, General Manager for MI&CT Engineering
  36. 36. GE Healthcare's IIoT Architecture "GE Healthcare is leveraging the GE Digital Predix architecture to connect medical devices, cloud-based analytics, and mobile and wearable instruments. The future communication fabric of its monitoring technology is based on RTI's data-centric Connext DDS platform.” -- Matt Grubis, Chief Engineer, GE Healthcare's Life Care Solutions
  37. 37. Large-Scale Control • The NASA KSC launch control is the world’s largest single-system SCADA • It combines 300k points, at 400k msgs/sec • RTI Connext DDS powers launch control, in-flight monitoring, UAV reentry- tracking ground station, and the recovery ship
  38. 38. Selective Data Availability • Wind turbine farms can include 500 turbines • Gust control across the array requires fast communications with dynamic, selective filtering • DDS enables large, distributed intelligent machines
  39. 39. Critical Distributed Reliability • DDS controls the 6.8 GW GC Dam – Largest power plant in North America – Fastest-responding major power source on the Western Grid – Requires 24x7 operation • Connext DDS met the challenges – Extreme availability – Wide area communications – Multi-level routing – High security – 300k data values • RTI system live since Jan 2014
  40. 40. Fast, Multi-Vendor System Integration • Audi hardware-in-the-loop simulation feeds realistic data to components for testing • The system offers plug-n-play between simulation vendor solutions • RTI middleware enables a modular test environment that scales to work with hundreds of devices
  41. 41. Modular Application Development A product group within ABB’s Grid Automation business unit chose RTI Connext DDS to: – Enable modular substation automation applications – Significantly reduce the cost of development – Leverage a standards- based commercial product
  42. 42. ©2015 Real-Time Innovations, Inc. Autonomous Vehicles Status Feb 2016
  43. 43. Cloud Services Intelligent Autonomy Sensing Planning Radar, LIDAR Vehicle Platform Navigation Error Management Visualization Situation Analysis Situation Awareness Vision Fusion Cameras, LIDAR, Radar … Data Fusion LoggingVehicle Control Localization DDS Bus Traffic Maps DDS Bus
  44. 44. Drilling Automation • Improves well quality and production • Captures domain knowledge from the 60% of field experts retiring over next 6 years • Increases safety • Protects the environment • Decreases drilling time and costs • Decreases downtime and equipment failure
  45. 45. Working Together Industrie 4.0 & IIC OPC UA & DDS
  46. 46. Platform Industrie 4.0 and Industrial Internet Consortium 2nd International Workshop on Collaboration in the Industrial Internet – Chicago, May 19th 2016
  47. 47. Industrie 4.0
  48. 48. 200+ companies strong Goal: build and prove a common architecture that spans sensor to cloud, interoperates between vendors, and works across industries
  49. 49. 200+ Companies, 25+ Countries Contributing Members IIC Founding Members The IIC Created the Industrial Internet of Things Market
  50. 50. Platform Industrie 4.0 and Industrial Internet Consortium 2nd International Workshop on Collaboration in the Industrial Internet – Chicago, May 19th 2016 1 ENERGY HEALTHCARE MANUFACTURING PUBLIC DOMAIN TRANSPORTATION IIC Cross-domain & Interoperability in IIoT Detailed model for next-gen Manufacturing value chainI4.0 51 DOMAIN FOCUS AREAS ARE COMPLIMENTARY
  51. 51. Platform Industrie 4.0 and Industrial Internet Consortium 2nd International Workshop on Collaboration in the Industrial Internet – Chicago, May 19th 2016 2 RAMI4.0 IIRA Interoperability 52 A CLEAR MAPPING BETWEEN BOTH ARCHITECTURES WILL ENABLE CROSS-DOMAIN INTEROPERABILITY
  52. 52. Platform Industrie 4.0 and Industrial Internet Consortium 2nd International Workshop on Collaboration in the Industrial Internet – Chicago, May 19th 2016 3 TEST 53 COLLABORATION ON TESTBEDS / TEST FACILITIES AND INFRASTRUCTURE WILL ENSURE INTEROPERABILITY ON THE TECHNICAL LEVEL
  53. 53. IIRA “Core Connectivity Standard” Approach “Core connectivity standards” that link with “gateways” • Delivers performance with flexibility • Scales linearly (only have to map each “other” to one “core”) • Supports natural security Choose the core standard that matches system needs
  54. 54. Multiple core protocols Core Protocol #1 Core Protocol #3 Core Protocol #2 2 3 1
  55. 55. OMG: Focus on DDS to OPC UA bi-directional Bridge • Existing: OPC UA Server on controller • Existing: OPC UA Client applications • Existing: DDS App • New: OPC UA-DDS Gateway– Maps “operations” on OPC UA to DDS NOTE: OPC foundation also working on a “Pub-Sub” mechanism for OPC UA. Plan is to make “DDS” one of the 3 supported “communication” models for pub-sub. DDS App DDS App OPC UA Server OPC UA-DDS Gateway OPC UA Client RTPS DDSBus
  56. 56. OPC Foundation Focus: Use DDS to implement OPC UA PUB/SUB • OPC UA PUB-SUB emerging • OPC UA UDP Profile designed for simplicity • OPC UA Pub-Sub DDS Profile for databus functionality OPC UA Client OPC UA Client OPC UA Server PUB-SUB Request/Reply OPC UA-TCP RTPS DDS App DDS App DDSBus
  57. 57. OPC UA - DDS Communications Model
  58. 58. Comparison in a Nutshell • DDS is a data-centric approach to software systems integration – Implements a global data space abstraction – Decouples applications in time, space, & flow – Software teams use DDS to write software modules that interact through a data model • OPC UA is a device-centric technology for device interoperability – Implements a node-graph address space of devices abstraction – Decouples applications from device details – Workcell integrators use OPC UA to write programs through a device model
  59. 59. Should I Start With DDS or OPC UA? • Use DDS if… – You are developing many distributed software modules concurrently • You will define a system architecture, and then build pieces • You can impose a shared information model – You need DDS key features • No servers for dynamic configuration & easy redundancy • Peer-peer, QoS-controlled flow with location transparency • Data centricity to manage a large or varying data space – You want the simplicity of applications talking to the data space, not to other apps • Use OPC UA if… – You are developing devices to be integrated later • You have need for future device interoperability • You will program generic devices, building an information model at runtime – You need key OPC UA features • Separate device design from system design • Library of device models • Client/server deployment design – You want the simplicity of device-centric programming You see your problem as distributed software You see your problem as programming devices
  60. 60. Bottom Line DDS is for systems facing a primary software integration challenge, While OPC UA is for simpler software systems facing device interchangeability issues
  61. 61. ©2015 Real-Time Innovations, Inc. What If I Choose The Wrong Path?
  62. 62. Summary • OPC UA and DDS are key, established protocols in the IIoT • They are quite different designs – OPC UA: object oriented, client-server – DDS: data centric, peer-peer • They target different users & applications – DDS is for systems facing a primary software integration challenge, – While OPC UA is for simpler software systems facing device interchangeability issues • The communities are working together – Your investment will be preserved
  63. 63. Questions? • OPC UA – OPC Foundation: – Email: • DDS – DDS portal: – RTI: – Email: – Examples, forum, papers: • IIC & Industrie 4.0 – IIC website: – Industrie 4.0: • Connect on LinkedIn!