What is BS EN IEC 62541-14‒ OPC UA PubSub about?
BS EN IEC 62541-14 is the 14th part of an international multi-series standard that covers attributes of OPC Unified Architecture.
BS EN IEC 62541-14 defines the OPC Unified Architecture (OPC UA) PubSub communication model. It defines an OPC UA publish-subscribe pattern which complements the client-server pattern defined by the Services in IEC 62541-4. IEC TR 62541-1 gives an overview of the two models and their distinct uses.
BS EN IEC 62541-14 consists of a general introduction of the PubSub concepts, a definition of the PubSub configuration parameters, a PubSub configuration model as well as mapping of PubSub concepts and configuration parameters to messages and transport protocols.
Who is BS EN IEC 62541-14‒ OPC UA PubSub for?
BS EN IEC 62541-14 on OPC UA PubSub is useful for:
- IT companies
- Programmers
- Software developers
- Data analysts
- Data analysis companies
- MS office user companies
Why should you use BS EN IEC 62541-14‒ OPC UA PubSub?
OPC Unified Architecture (OPC UA) can be defined as a machine-to-machine communication protocol used for industrial automation. It was developed by the OPC Foundation. The OPC UA platform is a platform-independent service-oriented architecture that combines discrete OPC Classic specifications into an expandable framework.
BS EN IEC 62541-14 provides you with the OPC Unified Architecture (OPC UA) PubSub communication model that enables the distribution of data and events from an OPC UA information source to interested observers inside a device network as well as in IT and analytics cloud systems.
BS EN IEC 62541-14 sets an approach for PubSub (Publish-Subscribe), that gives you a substitute mechanism for data and event notification. PubSub has been optimized for many-to-many configurations, as in Client-Server communication each notification is for a single client with guaranteed delivery. It helps users to understand the features of Publish-Subscribe (PubSub), which enables OPC UA applications to not directly exchange requests and responses. Instead, Publishers send messages to a Message Oriented Middleware, ensuring the security of the subscribers.
