Asset lifecycle: preventive maintenance, recalls, sites and full history

Every unit installed at a customer (an asset in the installed base) now has a full lifecycle inside the service module. Open it from Installed base, then Lifecycle, maintenance and recalls, or from the Asset tab of the lifecycle page (also reachable from the notification bell when a warranty or cont

Every unit installed at a customer (an asset in the installed base) now has a full lifecycle inside the service module. Open it from Installed base, then Lifecycle, maintenance and recalls, or from the Asset tab of the lifecycle page (also reachable from the notification bell when a warranty or contract is ending).

Preventive maintenance in data Create a maintenance plan for a product (model) or for a single asset. A plan can be by time (every N days), by usage counter (every N hours, cycles, km), or both: whichever comes first opens a ticket. The ticket is a real ticket, linked to the asset, with the queue, priority and instructions of the plan, and it is opened automatically every minute by the system with the lead time you set. Only one occurrence stays open per plan and asset, so the system never opens the same maintenance twice. Marking the occurrence done writes the service event on the asset and starts the next cycle from that day; if you enter the counter value at completion, the next usage cycle counts from it.

An asset without an installation date, a service record or a counter reading has no baseline: the plan says so and opens nothing, instead of guessing a date.

Usage counters Record hour meter, cycles or any counter the equipment has, with the date it was read. Readings are entered by people; the system computes the rate from the last 90 days and projects when the next usage maintenance is due. A reading with the same date and counter is recorded once. Readings cannot be edited; to correct, record another.

Recalls and service campaigns A campaign selects a population by product, serial range and installation window. Preview shows exactly which units will be called. Launching opens one ticket per unit, linked to it, in batches; launching again never duplicates and only opens what is still missing. Coverage (done, open, pending, excluded) follows the live status of each ticket. Units you decide not to call can be excluded with a note.

Structure and downtime propagation An asset can be a component of another (system and modules). The tree, the where-used by model and the cycle guard are built in. Per system, you can choose that a downtime on the system also marks its components as down; ending it ends theirs. Modules that keep working when the system stops should leave this off.

Sites and locations A tree per customer: site, building, floor, room. Assign the asset to a leaf; the asset's location text receives the full path and the move is recorded in its history. Deleting a location requires it to be empty; deactivate instead.

Coverage The asset view shows warranty, the linked service contract and the support entitlements that reach the unit, either through the asset's contract or through the customer account and covered products. There is no second contract: this reads the same entitlement the ticket SLA uses. When a warranty or contract is about to end, the account owner receives a notification pointing to the asset.

Full history One timeline with installation, service events, tickets, downtime, field jobs and visits, service orders, parts used, counter readings, maintenance occurrences and campaigns. Filter by kind and open the ticket from the line.

End of life Decommissioning writes the asset off with a date and a method (disposed, returned, sold, lost), ends any open downtime and skips open maintenance. It is final: a written-off asset never returns to active; a new unit gets a new record with the replacement link. A system with active components must be decommissioned together with them or after moving them.

Analytics Breakdowns by product, status, age, warranty, criticality, customer and location, with the count of units down and out of warranty in each, plus open and overdue maintenance, active campaigns and unplanned downtime hours in the last 90 days. Export the installed base as CSV.

What this does not do There is no telemetry or IoT: counters and downtime are recorded by people or by tickets. Cost and revenue per asset are not computed. Documents still attach to the product record, not to the unit.

Open this article inside the system →