Name, type, location, serial, model, manufacturer, purchase cost, warranty end date, photo, manuals, and parent-child links are all on one record with a stable ID.
Every field change records who changed what, when, and from what value to what value. The field-level audit is on the asset, not in a separate log.
Parent assets cannot be deleted while children are still linked. Children cannot be orphaned. The graph holds through reorganisation.
01 · Master record
One record. Every field the binder used to hold.
When a piece of equipment is registered, the system captures name, description, asset type, location, serial number, model name, manufacturer, year of manufacture, purchase cost, purchase date, warranty end date, photo, and attached manuals or files. One record. One stable ID. Pull it up and the install certificate is right there, not on an ex-staff member's laptop.
Purchase cost and warranty end date are first-class fields on the record, not afterthoughts in a separate tab. A list view answers which warranties end in the next 60 days by reading the record directly.
Manuals, install photos, inspection certificates, and supplier documents attach to the asset directly. A technician pulling up a chiller sees the right documents against that specific unit.
Master record
Reviewer view
AST-2026-0047 · Chiller 4 · HVAC Rooftop Chiller
Identification
Asset IDAST-2026-0047
NameChiller 4
TypeHVAC Rooftop Chiller
SerialNT-2024-44821
ModelNT-RX820
ManufacturerNorthline Thermal Systems
Purchase + warranty
Purchase date12 Mar 2024
Purchase cost$142,500
SupplierProTrade Services
Warranty end12 Mar 2029
Warranty chipActive warranty · 3y 10m remaining
2 manuals3 photos1 install certificate
Priya S. updated warranty end date · previous 12 Mar 2028 → new 12 Mar 2029
Mike J. attached install photo · 02 Apr 2024
Sara T. created record · 14 Feb 2024
02 · Hierarchy
A chiller has compressors. The tree is real.
A chiller rig with six subcomponents. A switchboard with its protected circuits. A lift with its controller and car. These are linked on the master record, so the tree survives reorganisation. Parents cannot be deleted while their children are linked.
Location is also a hierarchy, not a string. Buildings contain floors, floors contain rooms, rooms contain equipment. The breadcrumb on every asset reads the location graph back to you.
Equipment tree · Location hierarchy
Building 3 › Level 2 › Rooftop
AST-2026-0047 · Chiller 4 · HVAC Rooftop Chiller
AST-2026-0048 · Compressor 1 · Scroll compressor
AST-2026-0049 · Compressor 2 · Scroll compressor
AST-2026-0050 · Evaporator · Plate heat exchanger
AST-2026-0051 · Condenser · Air-cooled condenser
AST-2026-0052 · Control panel · PLC controller
AST-2026-0053 · Pressure regulator · Safety valve
Children cannot be orphaned. Parents cannot be deleted while children are linked.
03 · Per-type schema
One record shape. Different fields per type.
Each organisation defines its own asset types. Chillers, fire panels, lifts, switchboards, air handlers, pumps, generators, boilers. Each type carries its own schema of properties and its own set of actions.
Admin writes the type once. Every new chiller inherits the schema. Every fire panel inherits its own. No engineering ticket to add a new column for a new asset class.
HVAC Chillerv3 · Active
Centralised cooling plant for multi-floor facilities.
Properties
Compressor typetext
Refrigeranttext
Capacity (tons)number
COP ratingnumber
Actions
Quarterly serviceAnnual inspection
Fire Panelv2 · Active
Fire alarm control panel with zone monitoring.
Properties
Zone countnumber
Battery typetext
Backup durationnumber
Loop topologytext
Actions
Monthly testAnnual recertification
04 · Warranty visibility + audit
You see what is expiring. And every change to the date has a name on it.
Warranty end date is a field on every asset, with a countdown chip on the record (3 years 10 months remaining). A list view filters to assets whose warranty ends in the next 60 days, so renewal, claim, and replacement decisions sit in a queue you can work, not a calendar reminder you can miss.
When that date moves, the record captures who moved it. Previous value, new value, actor, timestamp, optional reason note. Same for serial number, location, manufacturer, manuals. The trail survives reorganisation, ownership changes, and staff turnover.
You see what is expiring on a list view. You see who edited the date on the record. Same record, no second tool.
05 · Maintenance history
Every work order against this asset is on its record.
The asset record shows a count of past work orders and a compact list of the most recent ones: work order number, date, work type, primary actor, a single-line summary. It is a cross-reference, not the job story.
When a breakdown repeats, you see it on the asset. When you want to know what happened on that last service, you click through to the work order.
Past jobs · On this asset
12 work orders in last 12 months. 5 most recent shown.
A replaced chiller still has a trail for compliance review.
When equipment is replaced and the old record is taken out of service, the system writes a final audit snapshot: the full previous state of the record, the actor who took it out, the timestamp, and an optional reason.
This is not a disposal queue. It is not an approval workflow. It is not a depreciation engine. It is a record event with actor, timestamp, and previous state.
The final audit snapshot is on the record. Not a queue, not a workflow, a record event.
07 · Adjacent pages
This record connects the rest of the platform. It does not pretend to be them.
The asset record is the operational ground-truth. IoT detail for connected equipment lives on the IoT page. The work-order state machine, assignment, and evidence live on work-orders. Recurring preventive jobs attached to this asset are authored on preventive maintenance. The asset page shows the counts and the connections. It does not retell the other stories.
One page, one job. The asset page is the record. The other pages are the activity, the schedule, the signal, and the form.
Asset registry · Filtered list
Type: HVAC ChillerLocation: Building 3IoT-connected: Any