Tracking equipment across customer sites is more complicated than maintaining a list of serial numbers. The difficult part is keeping identity, location, responsibility and operational history connected as the estate changes.
A useful approach starts with a hierarchy that mirrors the real world.
1. Separate customer, site and asset
Do not store the customer location as free text on every machine if you can avoid it. Use a clear hierarchy:
Customer → Site → Asset
This makes it possible to change a site address or contact information without editing every asset individually, and it supports estate-level reporting later.
2. Give every asset a durable identifier
Manufacturer serial numbers matter, but an internal asset identifier is often still useful. It can remain consistent even when labels, customer references or other systems change.
A QR label can then resolve that durable identifier into the live asset record.
3. Record responsibility, not just location
Two machines at the same site may have different commercial arrangements. One may be owned by the supplier; another may have been sold to the customer.
Useful fields can include:
- legal or commercial owner;
- operating customer;
- service provider;
- warranty or support context;
- installation / commissioning date;
- current site and location within the site.
This prevents location from being mistaken for ownership.
4. Put recurring actions against the asset
A central calendar of generic tasks becomes hard to interpret as the estate grows. Where practical, attach care and inspection requirements to the equipment or equipment type.
Then an estate view can answer both:
- What is due across all sites?
- What is due for this exact asset?
5. Keep service history with the equipment
Job-management software often stores excellent information about a service visit, but the customer or owner may still struggle to see the complete machine history over several years.
The asset record should retain the relevant outcome even when the commercial job has closed.
See What should an equipment service history contain?.
6. Make moves explicit
Equipment moves are normal. An asset may be swapped between customer sites, taken into workshop, held in storage and later redeployed.
Rather than overwriting the current site with no trace, keep a location history where that matters to the lifecycle.
7. Add telemetry selectively
Telemetry can help confirm usage, machine status or maintenance information, but connected data should map to the same asset identifier used by the rest of the system.
The goal is not another disconnected machine portal. It is a richer version of the existing asset record.
The minimum useful estate view
At estate level, most owners need to answer:
- how many assets are deployed;
- where they are;
- which require action;
- which have overdue care or service;
- which have open issues;
- what has changed recently.
That is more actionable than a spreadsheet containing only make, model and serial number.