Associating (the digital twin of) a device to a specific location in the location tree of a customer is called registering a device. Together with such an association an optional mount point can be stored, the mount point is a textual description of the devices precise mounting position within the location. The registration of a device at a customer's location also designates the customer as the device's owner.
Registering a device makes the digital twin of the device visible in the Client Service and therefore visible for users. Registering a device is the precondition for working with devices in HsM in the context of a customer. The Client Service however also provides limited support for working with devices that are not registered, for more details see: working with non-registered devices.
Only devices known to the Digital Twin Service can be registered, with exceptions for device systems. To register a specific device in a specific location of a customer, the user attempting the device registration must have the EDIT_DEVICES_<COMPETENCECLASS> permission (for the competence class associated with the device'S device-type) on this customer and must identify the device. Devices can only be only registered at location types that allow to register devices.
Devices of a device-type that has the registration option Member Only set in the Catalog Service cannot be registered directly. Those devices can only be registered via a device system configuration.
A device can be registered at multiple locations and customers over time, but it can only be registered at one location at any given moment. The Client Service keeps a historical record of the registrations of a device.
Devices that are currently registered cannot be registered at another location. In that case the device has to either be unregistered and then registered again or the device can be moved.
Devices that are currently registered at a location of a customer that is marked as deleted can be registered at a location of another customer. The Client Service will in the background unregister the device at the location of the deleted customer and then register the device at the new location/customer. In this case the user performing the registration does not need any permission on the deleted customer.
Once a device is registered to a customer the permissions set up for that customer apply to that device. Unregistered devices can be registered at any customer, i.e. as long as a device is not registered at a customer anyone can identify that device and register it at a customer where he has the permission <%PC EDIT_DEVICES_COMPETENCECLASS%> for the competence class associated with the device's device-type. That also means that if a user can identify an unregistered device he can take digital ownership of that device.
Registration dates
Table 32 shows the dates stored by Client Service in connection with device registrations.
Attribute |
Description |
|---|---|
Date and time when this device was first registered in HsM, independent of customer. |
|
Date and time when this device was first registered at some location of the customer it is currently registered to. |
|
Date and time when this device was registered at the current location. |
Table 32: Registration dates provided by the Client Service
Compound devices
When the identified device that shall be registered is member of a compound device then the registration is actually performed for the compound device. I.e. the link between the compound member and the compound device is not modified. Both the compound device and compound member are then associated with the same location and have the same mount point.
Device systems
Device systems cannot be registered directly as they cannot be identified (device systems are not real physical devices) and are not known to the Digital Twin Service. The Client Service can however create device systems.
