NOV-DEC 2018

Issue link:

Contents of this Issue


Page 28 of 56

INTECH NOVEMBER/DECEMBER 2018 29 SYSTEM INTEGRATION This frees engineering resources to do the more im- portant work of running the business. Today, there are more than 4,200 suppliers who have created more than 35,000 different OPC products used in more than 17 million applications. The estimate of the savings in engineering resources alone is in the billions of dollars. The OPC Foundation strategy is: l rules for OPC UA Companion Specifications developed together with partners l predefined process for joint OPC UA companion specifications l templates to ensure standardized format and potential certifications l compliance l intellectual property l working processes The OPC Foundation is focused on evange- lizing the OPC UA information framework and collaborating with standards orga- nizations and consortia to incorporate data models that reflect the knowledge of their subject-matter experts. Information models OPC UA, beyond being a secure, interoperable standard for moving data and information from the embedded world to the cloud, is an open ar chitecture for a wide range of application in- formation models that add meaning and context to data. Information modeling allows organiza- tions to plug their complex information models into OPC UA. This brings information integration and interoperability across disparate devices and applications. Using the common OPC UA frame- work was a way for all standards organizations to seamlessly connect their data between the IT and OT worlds. This greatly simplifies the end user's task of digitalization. Service-oriented collaborative architecture The OPC Foundation collaboration across many organizations is a very important part of the OPC UA service-oriented architecture that lets other or ganizations model their data and have it seam- lessly and securely connected. The concept is simple. An organization develops its data model, mapping it to an OPC UA information model. Ven- dors can build a server that publishes information, providing the appropriate context, syntax, and se- mantics. Client applications or subscribers can dis- cover and understand the syntax and semantics of the data model from the respective organizations. An OPC UA server is a data engine that gathers in- formation and presents it in ways that are useful to various types of OPC UA client devices. Devices could be located on the factory floor, like a human- machine interface, proprietary control program, historian database, dashboard, or sophisticated analytics program that might be in an enterprise server or in the cloud. The initial collaboration that the OPC Founda- tion engaged with was called OpenO&M, which was a cooperation between OPC Foundation, MI- MOSA, ISA95, and OAGIS. This first collaboration resulted in several OPC UA companion specifica- tions that were focused at the IT world and inte- gration with the factory floor. The graphic shows the logos of the numerous standards organiza- tions that the OPC Foundation has partnered with. These specifications allow generic applications to connect to different devices and applications to discover and consume the data and information. Fast forward to late 2018, and the OPC Founda- tion has now partnered with more than 40 different FAST FORWARD l Information integration requires standards organizations to work closely together for interoperability to address digitalization and convergence. l The OPC Foundation is working with consortia and standard development organizations to achieve superior production with digitalization. l OPC UA provides a secure, interoperable standard for moving data and information from the embedded world to the cloud using application- oriented data models from other organizations. OPC UA Model diagram AMQP MQTT Built-in information models Base, DA, AC, HA, programs Information model layer Communication model Protocol bindings Client/server Built-in security Publish/subscribe DI model UA for devices OPC UA metamodel Basic rules for exposing information with OPC UA Services Browse, read/write, method calls, subscriptions UA Binary UA Secure Conversation UA TCP Relay JSON WebSocket/HTTPS Message model PubSub, configuration, data sets, message readers and writers OPC Foundation responsibility OPC UA = IEC 62541 UA Binary JSON UADP UDP UADP/JSON TSN

Articles in this issue

Archives of this issue

view archives of InTech - NOV-DEC 2018