1. What device lifecycle covers
A device moves through production, activation, operation, maintenance, and scrapping, and each stage has its own state and its own actions. Device lifecycle management (device lifecycle) lets you define lifecycle states such as Inactive, Online, Offline, In Maintenance, and Decommissioned. A state change can start a workflow, send a notice, or change a permission, so the whole life of the device is managed as data. The platform supports a custom state machine, state-transition rules, and an automation policy. Manufacturing, energy, and asset-leasing customers already run on it.
2. Lifecycle states
Inactive / Online / Offline
After the first connection, a device that was never activated moves from Inactive to Online. A long offline stretch is marked abnormal automatically, as Offline. Counts by state make an asset check straightforward.
In Maintenance / Decommissioned
A device under maintenance can be set out of service, as In Maintenance. Once it is scrapped it is archived and its resources are released, as Decommissioned. A rental fleet can add its own states, such as On rent, Returned, and Awaiting repair.
Automation Policy
A policy can disable a device after N days offline, or unbind the user when a device is scrapped. Lifecycle events can be pushed to a business system and start a workflow or a permission change.
3. A typical life
4. Systems it connects to
| Integration | What it does |
|---|---|
| Asset management | Lifecycle state stays in sync with the asset system. Scrapping a device starts depreciation and updates the ledger. |
| ERP | Lifecycle events are pushed to ERP and can move with orders, purchasing, and other business systems. |
| Work order | A state change can open a work order, and the In Maintenance state stays linked to the work-order system. |
| Lifecycle API | A lifecycle API and state-machine configuration notes, so an external system can query state and trigger a transition. |
5. Where teams use it
Manufacturing, energy, and asset-leasing customers use device lifecycle to manage a device as data from activation through scrapping. Counts by stage feed an asset report. SimtoLink can help design the state machine, configure the automation policy, and integrate ERP and the asset system. Contact us if you want that work shaped to your estate.
Appendix: operating the lifecycle after go-live
Lifecycle states only stay trustworthy at fleet scale when three habits are already running. Stress-test and chaos-drill a pre-production or pilot batch that matches production — connection storms, a full disk, certificate rotation, a failure across regions — and keep the outcome as an acceptance checklist you can reuse. Write metrics, alert thresholds, the on-call escalation path, and audit retention into change management, so a parameter change is traceable and reversible and does not depend on one person’s memory. Each quarter, engineering, operations, security, and data should check that the metrics still explain business risk, and attach every improvement to a ticket and a release. SimtoLink treats the console, the open APIs, and exports as an asset you keep operating — observable, orchestrable, and auditable — rather than a launch you walk away from. If the design has to fit your ITSM, IAM, data lake, or edge clusters, the SimtoLink solutions team can review it with you and come back with implementation notes and a risk list.