Description

Devices typically come with a set of properties that identify them for discovery, management, and maintenance purposes. This set of properties is commonly summarized using the term “nameplate“. The information available includes (but it is not limited to) device name, identifiers, serial number, manufacturer, hardware and software versions, and product URI. A nameplate for a device is required to be recognized correctly in the server.

Furthermore, a Device is composed of different Components. Each of these Components can have a nameplate itself. The definition of Components is up to the implementer of the Device.

It should be possible to represent an individual Device as an OPC UA Server or aggregate multiple Devices into the same OPC UA Server. Therefore, an OPC UA Server can represent an arbitrary number of Devices. The following scenarios are envisioned to be covered by this specification:

• Single Devices incorporating an OPC UA Server,
• Gateway Devices representing a set of Devices, including OPC UA capable Devices as well as non-OPC UA capable Devices  (e.g., a simple analogue Sensor or legacy device using a different communication protocol),
• Devices serving both of the above roles.

Addressed in Section: 7.1