Input Argument Options

The methods defined for Asset Management, Joining Process Management and Joint Management has ProductInstanceUri as an input argument.

The usage of ProductInstanceUri could vary based on the type of system. The following options are possible from a Server.

• Use Case 1: ProductInstanceUri is empty.
• The Server should consider the ProductInstanceUri of the asset where it is deployed. If it does not apply for the specific method, then the Server should return the respective error code.
• Examples: SendJoiningProcess, GetJoiningProcess, GetJoiningProcessList, etc.
• Use Case 2: ProductInstanceUri is non-empty.
• A Joining System with virtual stations.
• In a joining system with one controller, multiple tools connected to the controller, multiple accessories, and multiple virtual stations:
• OPC UA Server is deployed at controller.
• Client should pass the ProductInstanceUri of the corresponding Virtual Station mapped in system or it is also allowed to pass the ProductInstanceUri of the physical asset.
• Examples: SetCalibration, EnableAsset, RebootAsset, etc.
• A Joining System without virtual stations.
• In a joining system with one controller, multiple tools connected to the controller, multiple accessories:
• OPC UA Server deployed at controller.
• Client should pass the ProductInstanceUri of the corresponding physical asset connected to the Controller.
• Examples: SetCalibration, EnableAsset, RebootAsset, etc.

Multiple Client Method Execution

The mutual exclusion mechanism to handle the execution of the same method from multiple clients should be handled by the Server application layer and is not defined in this specification.