End-of-Life and Decommissioning¶

This flow covers the steps required to permanently retire a device from the ToloMEO platform at the end of its operational life.

Involves: PMS, Fleet Manager, Cybersecurity, ToloMEO CLI

Step 1 - Record the disposal event in PMS¶

Before removing any platform records, register a DISPOSAL public event on the device. This creates a permanent entry in the device's audit trail marking the date and reason for decommissioning, which is useful for compliance, warranty tracking, and customer reporting:

tlm-cli pms events create public --serial <serial-number> --customer <customer-code>

Select DISPOSAL as the event type and add a description that captures the reason (end of contract, hardware failure, return, etc.).

Step 2 - Unprovision the device¶

Remove the device's platform identity and all associated records from PMS and the IoT layer:

tlm-cli pms provisioning unprovision <serial-number>

Warning

Unprovisioning is permanent. The device record and its platform identity are deleted and cannot be restored. Ensure the disposal event from Step 1 has been recorded before proceeding.

Step 3 - Remove unused firmware versions¶

If the decommissioned device was the last in the fleet running a particular firmware version, that version is no longer deployed anywhere and can be removed from the model in PMS. Retaining firmware releases that are no longer in use adds noise to OTA management and keeps obsolete software in the system unnecessarily.

Check whether any other devices in the fleet are still running the same firmware version before deleting a release. If no devices remain on that version, remove it from the relevant model in PMS Models.

Step 4 - Stop CVE tracking in Cybersecurity¶

If a firmware version was being tracked in the Cybersecurity module and is no longer deployed on any device, stop tracking it. Retaining it continues to generate alarm notifications and appears in dashboards and reports, creating work for vulnerabilities that have no impact on any live device.

From the Cybersecurity module, remove the tracked version for the relevant model. Any alarms configured specifically for that version can also be cleaned up at this point. For a reminder of how alarms are set up, see SBOM Tracking - Set up alarms.