3 Terms, definitions, and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in OPC 10000-1, OPC 10000-7, OPC 10000-12, OPC 10000-14, OPC 10000-15, OPC 10000-81, and OPC 10000-100 as well as the following, apply.
All used terms are italicised in this document as described in OPC 10000-1.
3.1.1 Asset
Physical or logical elements of an AutomationComponent
3.1.2 AutomationComponent
entity that performs one or more automation functions and is modelled by an AutomationComponentType
3.1.3 Compute
software application collecting data, running on a variety of hardware platforms
3.1.4 Controller
industrial digital computer used in the control of manufacturing or process automation processes
3.1.5 ConnectionManager
entity that interacts with AutomationComponents to establish Connections between FunctionalEntities
3.1.6 Controller-to-Compute
interaction model involving Controllers exchanging data with Computes
3.1.7 Controller-to-Controller
interaction model involving Controllers exchanging data with one another
3.1.8 Controller-to-Device
interaction model involving Controllers exchanging data with devices
3.1.9 Connection
logical communication relationship between FunctionalEntities for exchanging information and coordinating joint operations
3.1.10 Descriptor
multi-document file (zip package) containing information for using and configuring one or more AutomationComponents
3.1.11 Device-to-Compute
interaction model involving devices exchanging data with Computes
3.1.12 Device-to-Device
interaction model involving devices exchanging data with one another
3.1.13 FunctionalEntity
element of an AutomationComponent containing the data and methods needed to configure, control and manage functional behaviour
3.1.14 OfflineEngineering
design phase activity, where, based on data from the vendors of the AutomationComponents, the configuration for AutomationComponents is planned (typically without the hardware available), which gets deployed to the physical Controller, device, or Compute during the commissioning phase at a plant
3.2 Abbreviated terms
| 5G | Fifth Generation broadband cellular network |
| AC | AutomationComponent |
| APL | Advanced Physical Layer |
| C2C | Controller-to-Controller |
| C2D | Controller-to-Device |
| DCS | Distributed Control System |
| DHCP | Dynamic Host Configuration Protocol |
| CM | ConnectionManager |
| DNS | Domain Name Service |
| FE | FunctionalEntity |
| FX | Field eXchange |
| HMI | Human Machine Interface |
| IEC | International Electrotechnical Commission |
| IEEE | Institute of Electrical and Electronics Engineers |
| IIoT | Industrial Internet of Things |
| IPC | Industrial Personal Computer |
| MES | Manufacturing Execution System |
| PAS | Process Automation System |
| PLC | Programmable Logic Controller |
| QoS | Quality of Service |
| SCADA | Supervisory Control And Data Acquisition |
| SPE | Single Pair Ethernet |
| TSN | Time-Sensitive Networking |
| UAFX | OPC UA Field eXchange |
| VLAN | Virtual Local Area Network |
| WLAN | Wireless Local Area Network |
3.3 Conventions used in this document
In this specification, the name of a type without the inclusion of “Type” indicates an instance of the type. For example, the following phrase, “an instance of ConnectionConfigurationSetType,” can be replaced with “a ConnectionConfigurationSet”. The phrase “instances of ConnectionEndpointType” can be replaced with “ConnectionEndpoints”.