This specification provides building blocks for various use cases. Other specifications or vendor-specific information models can pick the building blocks for specific use cases they want to support.
The user would like to uniquely identify machines, potentially across various OPC UA Servers or aggregating OPC UA Servers. The user wants to get standardized information about the machine, like manufacturer or serial number, and set user-specific information in order to simplify the usage of the machine.
That leads to the requirements:
- A machine shall be globally uniquely identified (see section 8, ProductInstanceUri).
- Information about the machine, like manufacturer or serial number, can be accessed (see section 8, IMachineVendorNameplateType).
- Application-specific information about a machine can be set by an OPC UA Client (see section 8, IMachineTagNameplateType).
The user would like to easily find all machines managed by an OPC UA server.
That leads to the requirement:
- All machines shall be easy to find in an OPC UA Server (see section 9, Machines Object).
The user would like to identify components of a machine. The user wants to get standardized information about the component, like manufacturer or serial number, and set user-specific information in order to simplify the usage of the component.
That leads to the requirements:
- Information about the component, like manufacturer or serial number, can be accessed (see section 10.2, MachineryComponentIdentificationType).
- Application-specific information about a component can be set by an OPC UA Client (see section 10.2, MachineryComponentIdentificationType).
The user would like to easily find all components related to a specific machine.
That leads to the requirement:
- All components of a machine shall be easy to find in an OPC UA Server (see section 11.2, MachineComponentsType).