track what it runs on
Equipment history that is audit-ready.
Keep equipment history, certifications and safety records without the spreadsheets.
what it does
What Asset Management does
An asset accumulates a history: what was serviced, when, by whom, what was replaced, what was flagged and not acted on.
Held against the asset itself rather than scattered across visits, that history is what makes the next visit faster and predictive maintenance possible at all.
It is also what someone asks for when they want to know why a machine failed.
- Full service history per asset
- Certifications and safety records held alongside
- Service intervals and what is due next
- The history a technician sees before arriving
how it works
Four steps, and none of them are magic.
-
register
Every serviceable thing gets a record
Equipment at customer sites, its make and model, serial, location, warranty position and who is responsible for it.
-
accumulate
History attaches to the asset, not the visit
Every job, part, reading and form completed against it. When the technician who knows this line is on leave, the machine still remembers.
-
monitor
Condition and usage drive the schedule
Meter readings and inspection outcomes feed preventive maintenance, so servicing follows actual use rather than a date in a spreadsheet.
-
decide
Repair-or-replace becomes an argument with evidence
Cumulative cost, failure frequency and downtime per asset, which is the conversation customers ask for at renewal.
data and integration
What it reads, what it writes, what it sits beside.
Nothing here is a separate database. Asset Management works off the same work order, customer and asset records as everything else, which is the whole reason the modules are worth running together.
reads
Work orders, forms, parts consumption, meter readings, contract coverage.
writes
Preventive maintenance jobs into the schedule; asset context onto every new work order.
alongside
Knowledge AI for documentation, Contract Management for what is covered.
questions we actually get
Before you ask us on the call.
Yes: site, system, sub-assembly. A chiller can hang under a plant room under a site, and history rolls up.
Normal, and the common case. Ownership is a field; the record is yours to service against and can be shared with the customer.
No. Most operators register assets as jobs touch them and are substantially covered within a maintenance cycle. A big-bang data load is rarely worth the delay.
Yes: hours run, cycles, distance. Readings captured on site advance the schedule.
elsewhere in the platform
Other capabilities
further reading