The LADSDeviceType provides a base class for Laboratory and Analytical Devices. It is formally defined in Table 15.

Table 15 – LADSDeviceType Definition

Attribute	Value
BrowseName	LADSDeviceType
IsAbstract	False
References	Node Class	BrowseName	DataType	TypeDefinition	Other
Subtype of the DeviceType defined in OPC 10000-100
0:HasAddIn	Object	4:Components		LADSComponentsType	O
0:HasComponent	Object	FunctionalUnitSet		FunctionalUnitSetType	M
0:HasProperty	Variable	3:HierarchicalLocation	0:String	0:PropertyType	O
0:HasAddIn	Object	2:Identification		4:MachineIdentificationType	M
0:HasProperty	Variable	3:OperationalLocation	0:String	0:PropertyType	O
0:HasComponent	Object	DeviceState		LADSDeviceStateMachineType	M
0:HasComponent	Object	Maintenance		MaintenanceSetType	O
0:Organizes	Object	4:MachineryBuildingBlocks		0:FolderType	O
0:HasAddIn	Object	4:MachineryItemState		4:MachineryItemState_StateMachineType	O
0:HasAddIn	Object	4:MachineryOperationMode		LADSOperationModeStateMachineType	O
0:HasAddIn	Object	2:OperationCounters		4:MachineryOperationCounterType	O
0:HasAddIn	Object	4:LifetimeCounters		4:MachineryLifetimeCounterType	O
Conformance Units
LADS LADSDeviceType

Components is a generic set of identifiable sub-components of the Device as mandated by OPC 40001-1.

Note: The BrowseName of Components does not follow the naming conventions of this spec (should be “ ComponentSet”). This is for harmonization with the Machinery Specification.

FunctionalUnitSet contains the Functional Units of this Device.

HierarchicalLocation pro vides the hierarchical location of the LADS Device. The structure within the string may expose several levels. How this is exposed, which delimiters are used, etc. is vendor specific. Examples of such strings are “FactoryA/BuildingC/Floor1” or “Area1-ProcessCell17-Unit4” (see OPC UA OPC 10000-110 for more details).

OperationalLocation pro vides the operational location of the LADS Device. The structure within the string may expose several levels. How this is exposed, which delimiters are used, etc. is vendor specific. Examples of such strings are “Warehouse1/Sheet3” or “StainlessSteelTote3” (see OPC UA OPC 10000-110 for more details).

Recommendations for both hierarchical and operational locations have been proposed:

• For instances where the location definition encompasses multiple levels, these levels should be separated by the delimiter character "/". An instance of a location definition with multiple levels separated by the delimiting character "/" is "US-NY-NYC-Building101/Floor35/Room10.1".
• For additional use cases not covered by the aforementioned properties, it is recommended to employ the additional location formats NmeaCoordinateString, LocalCoordinate, and WGS84Coordinate as delineated in the OPC UA for AutoId Devices Release 1.01.1 (2021-07-13) specification.

Identification provides properties to identify a Device.

Recommendations for the Identification:

• If the device consists solely of software with no hardware, the SoftwareRevision should be provided, and the HardwareRevision should be omitted.
• If the device consists solely of hardware with no software, the HardwareRevision should be provided, and the SoftwareRevision should be omitted.
• If the device consists of both hardware and software, the HardwareRevision should be provided. The SoftwareRevision should be provided if there are no device components providing a SoftwareRevision. Otherwise, the SoftwareRevision may be provided to represent the overall revision of all software components.
• If a ProductInstanceUri can be created, this property should be part of the Identification.

OperationCounters for monitoring the operation of a LADSDeviceType, including parameters of the OperationCounters interface and lifetime variables (see OPC UA for Devices for more information).

DeviceState StateMachine that controls and represents the Device’s current state.

Maintenance is a set containing all maintenance tasks of a Device.

The MachineryBuildingBlocks folder contains all machinery building blocks, especially the MachineryItemState, MachineryOperationMode, OperationCounter and Lifetime Counter.

Refer to Annex B for proposed mappings between the DeviceStateMachine, the FunctionalUnit state machines, the MachineryItemState and the DeviceHealth.

MachineryItemState indicates the current state of the device and is comparable with the LADS Device state machine.

MachineryOperationMode indicates the type of Tasks being performed by the Device.

OperationCounter provides information on how long a MachineryItem has been turned on and how long it performed an activity. It uses the 2:IOperationCounterType interface and the predefined functional group 2:OperationCounters defined in OPC 10000-100.

Lifetime Counter provides information about the past and estimated remaining lifetime of a MachineryItem, or other aspects of a MachineryItem such as a software license. It is based on the 2:LifetimeVariableType defined in OPC 10000-100.

Children of the LADSDeviceType have additional References, which are defined in Table 16.

Table 16 – LADSDeviceType additional References

SourceBrowsePath	Reference Type	Is Forward	TargetBrowsePath
4:MachineryBuildingBlocks	0:HasAddIn	True	LADSDeviceType 4:MachineryItemState
4:MachineryBuildingBlocks	0:HasAddIn	True	LADSDeviceType 4:MachineryOperationMode
4:MachineryBuildingBlocks	0:HasAddIn	True	LADSDeviceType 2:OperationCounters
4:MachineryBuildingBlocks	0:HasAddIn	True	LADSDeviceType 4:LifetimeCounters
4:MachineryBuildingBlocks	0:HasAddIn	True	LADSDeviceType 4:Components
4:MachineryBuildingBlocks	0:HasAddIn	True	LADSDeviceType 2:Identification