The asset register is the spine of your operation. We built ours around the fact that it's never really one building — it's a hierarchy, a history, a stack of manuals and warranties, and a running tally of what each thing has cost you.
Most registers are a spreadsheet with extra steps. Ours is a living record — hierarchy, lifecycle, parts, docs, QR codes, and a repair-vs-replace engine that actually tells you what to do.
Company → site → building → area → line → asset → sub-asset. 8 levels deep. Drag & drop to reorganise — WO history follows the asset, not the path.
Every asset has a commissioning date, warranty window, run hours, and a predicted end-of-life. We flag the tipping point from "maintain" to "replace" before your CFO asks.
Every asset carries its BOM. When a WO consumes a part, stock drops automatically. Reorder thresholds trigger POs; techs never open a job to find the shelf empty.
Print QR tags from the app or order weather-rated stickers. Scan on any phone — no login wall for guest reporters. Operators open tickets in 11 seconds flat.
Cost-to-date vs cost-to-replace, risk-adjusted for asset criticality. Line up the number, hit "open capex request" — Oracle or SAP PO ready to ship.
Manuals, SOPs, photos, warranty certs — pinned to the asset. Techs see relevant docs inside the WO on their phone; no hunting in SharePoint for the torque spec.
Most registers treat every asset as a standalone row — so the user manual for your HVAC gets uploaded fourteen times, the PM checklist gets copy-pasted, and the spec sheet goes stale on six of them. Asset Definitions fix that.
A definition is a template for an asset type — say, "HVAC Unit · Model RTU-7500". It carries the shared fields, PM checklists, parts list, and attached files. Every individual unit is an instance that inherits all of it.
When a tech opens a WO on their phone, every relevant doc is there — inherited from the definition or attached to that specific asset. No hunting in SharePoint for the torque spec.
We've imported from Excel, Fiix, Limble, UpKeep, Maximo, and seven flavours of bespoke SQL. Upload what you have — we'll map it for you.
Drop your asset list — CSV, XLSX, or direct CMMS export. We read up to 500,000 rows in one go.
Auto-detects common schemas. Reviewable before commit — nothing lands in your workspace until you approve.
Build the tree by choosing parent fields (site, area, line). Drag to reorganise after, nothing breaks.
We pull serial numbers, manual links, and BOM suggestions from public manufacturer data when available.
Upload your current asset list. In under 10 minutes we'll show you what it looks like with the hierarchy, lifecycle view, and replace-vs-repair calc applied. No call required — just you and a trial workspace.
We use cookies to analyze site traffic and improve your experience. Learn more