Throughout this document and the referenced other Parts of the series, certain document conventions are used.
Italics are used to denote a defined term or definition that appears in the “Terms and definition” clause in one of the Parts of the series.
Italics are also used to denote the name of a service input or output parameter or the name of a structure or element of a structure that are usually defined in tables.
The italicized terms and names are also often written in camel-case (the practice of writing compound words or phrases in which the elements are joined without spaces, with each element's initial letter capitalized within the compound). For example the defined term is AddressSpace instead of Address Space. This makes it easier to understand that there is a single definition for AddressSpace, not separate definitions for Address and Space.
For the purposes of this document, the following terms apply.
a function that calculates derived values from Raw data
type of Event associated with a state condition that typically requires acknowledgement
Note 1 to entry: See Part 9 for a description of Alarms.
primitive characteristic of a Node
Note 1 to entry: Brokers are building blocks of Message Oriented Middleware.
generic term that is an extension to an Event
Note 1 to entry: A Condition represents the conditions of a system or one of its components and always exists in some state.
layered set of software modules between the application and the hardware that provides various functions to encode, encrypt and format a Message for sending, and to decode, decrypt and unpack a Message that was received
data that is composed of elements of more than one primitive data type, such as a structure
list of named data values
Note 1 to entry: The DataSetMessage is an immutable payload of the NetworkMessage handed off to the Message Oriented Middleware (transport layer) for delivery by the Publisher. The Subscriber receives the DataSetMessage as the payload of a NetworkMessage from the Publisher with additional headers that may be supplied by the Message Oriented Middleware along the way.
generic term used to describe an occurrence of some significance within a system or system component
organizational framework that defines, characterizes and relates information resources of a given system or set of systems.
Note 1 to entry: The core address space model supports the representation of Information Models in the AddressSpace. See Part 5 for a description of the base OPC UA Information Model.
infrastructure supporting sending and receiving NetworkMessages between distributed systems
Note 1 to entry: An OPC UA Application may support different types of Message Oriented Middleware infrastructures and protocols like AMQP or UADP with IP multicast. Other types like DDS, MQTT or XMPP can also be integrated into the OPC UA PubSub model.
callable software function that is a component of an Object
DataSetMessages and header to facilitate delivery, routing, security and filtering
Note 2 to entry:The term message is used with various connotations in the messaging world. The Publisher might like to think of the message as an immutable payload handed off to the Message Oriented Middleware for delivery. The Subscriber often thinks of the message as not only that immutable payload from the sender, but also various annotations supplied by the Message Oriented Middleware along the way. To avoid confusion the term DataSetMessage is used to mean the message as supplied by the Publisher for a DataSet and the term NetworkMessage is used to mean the DataSetMessage plus sections for annotation at the head and tail of the DataSetMessage.
fundamental component of an AddressSpace
class of a Node in an AddressSpace
generic term for data that announces the detection of an Event or of a changed Attribute value; Notifications are sent in NotificationMessages.
Message published from a Subscription that contains one or more Notifications
Node that represents a physical or abstract element of a system
synonym for Object
Node that represents the type definition for an Object
Note 1 to entry: A Publisher can be a native OPC UA Application or an application that only has knowledge about the Message Oriented Middleware and the rules for encoding the NetworkMessages and DataSetMessages.
OPC UA variant of the publish subscribe messaging pattern
specific set of capabilities to which a Server may claim conformance.
Note 1 to entry: Each Server may claim conformance to more than one Profile
Note 2 to entry: The set of capabilities are defined in Part 7
executable Object that, when invoked, immediately returns a response to indicate that execution has started, and then returns intermediate and final results through Subscriptions identified by the Client during invocation
explicit relationship (a named pointer) from one Node to another
Note 1 to entry: The Node that contains the Reference is the source Node, and the referenced Node is the target Node. All References are defined by ReferenceTypes.
Node that represents the type definition of a Reference
Note 1 to entry: The ReferenceType specifies the semantics of a Reference. The name of a ReferenceType identifies how source Nodes are related to target Nodes and generally reflects an operation between the two, such as “A Contains B”.
software application that implements and exposes the Services specified in this set of specifications
group of related Services
Note 1 to entry: A Subscriber can be a native OPC UA Application or an application that has just knowledge about the Message Oriented Middleware and the rules for decoding the NetworkMessages and DataSetMessages. A Subscription in the OPC UA Client Server model has a different meaning than the Subscriber in the PubSub model.
Note 1 to entry: ”Subscription” is a generic term that describes a set of Nodes selected by the Client (1) that the Server periodically monitors for the existence of some condition, and (2) for which the Server sends Notifications to the Client when the condition is detected.
Hardware or software platforms that exist as an independent entity. UA Applications are dependent on an entity’s existence in order to perform UA services. However, the entity is not dependent on UA Applications.
Note 1 to entry: Hardware and software platforms include physical hardware, firmware, operating system, networking, non-UA applications, as well as other UA Applications. A Distributed Control System, PLC/Device, and UA Server are examples of an Underlying System.
Node that contains a value
specific subset of the AddressSpace that is of interest to the Client.
A&EAlarms and Events
AMQPAdvanced Message Queuing Protocol
APIApplication Programming Interface
COMComponent Object Model
DCSDistributed Control System
DDSData Distribution Service
HDAHistorical Data Access
LDAPLightweight Directory Access Protocol
MESManufacturing Execution System
MQTTMessage Queue Telemetry Transport
OPCOPC Foundation (a non-profit industry association) formerly an acronym for “OLE for Process Control”. Acronym no longer used.
PLC Programmable Logic Controller
SCADASupervisory Control And Data Acquisition
SOAPSimple Object Access Protocol
UA Unified Architecture
UADPUA Datagram Protocol
UDDIUniversal Description, Discovery and Integration
UML Unified Modelling Language
WSDLWeb Services Definition Language
XMLExtensible Markup Language
XMPPExtensible Messaging and Presence Protocol