Replacing an RTLS Tag Without Losing the Asset's History

A cart receives a replacement tag and immediately starts reporting. The map looks healthy, except the marker carries another cart's name. Successful radio reception does not establish that the device is associated with the correct asset.

A tag change has a physical step and an information-management step. This operating approach keeps the asset understandable across both. Effective-date associations and history preservation must be verified in the chosen systems.

1. Keep the asset number separate from the device ID

The asset number identifies the physical cart. The tag ID identifies the reporting device. Reusing a tag on another cart changes the relationship, even though the device ID stays the same. Renaming a marker alone may not preserve that distinction.

Consider a register containing the asset number, active tag ID, effective time, attachment position and verifier. Reconcile the physical label with the existing register. Agree on formatting so leading zeros or spaces do not create apparent duplicates.

2. Verify the existing relationship before removal

Check the physical cart, its current association and its last observed timestamp. Record why the device is being replaced. An update gap can come from attachment or reception conditions as well as power problems.

At a US manufacturing site where maintenance changes tags and operations uses the carts, identify who signs off on the replacement. Confirm the selected model's procedure: devices differ in whether they permit battery replacement, require charging or need complete replacement. Do not generalize one model's instructions to another.

3. End one association and start the next

Two active tags linked to the same cart can produce conflicting observations. Distinguish an agreed test configuration from an accidental duplicate. For a normal replacement, preserve the end of the earlier relationship and the start of the new one.

Do not globally replace historical tag IDs with the new ID. Earlier observations should retain their original source. If effective periods cannot be represented in the system, keep a change register and explain the limitation to operators. Automatic reconciliation is an implementation requirement to verify.

4. Test the attached device on a real route

Attachment position and surrounding metal can affect reception. Follow the model's mounting instructions, avoid obstructing the cart's use and record the position. Reassess an unsuitable earlier mounting point rather than reproducing it automatically.

Move the cart along a safe agreed route. Check its displayed identity while stopped, moving and crossing zone boundaries. Confirm that an operator can locate the correct physical cart using the resulting record. Seeing the replacement tag online is only one part of acceptance.

5. Control removed and reusable tags

A removed tag still transmitting on a workbench can make the cart appear to be there if the relationship remains active. End the operational association and distinguish returned, under-inspection and ready-for-reuse devices. Handle power according to the product instructions.

When reused, give the new relationship an effective time. Check that earlier observations have not been attributed to the newly assigned asset. Include issue and return records where several people share spare devices.

6. Check the next shift's view

Query the same asset before and after replacement. Identify any gap and check that subsequent signals from the removed tag do not appear as the cart's movement. Where continuity is limited, provide the change register.

Alongside ORBRO RTLS Manager device management, decide where asset associations will be maintained. Bring device models, responsible roles and history requirements to ORBRO.