Maintenance & asset management
The full asset lifecycle — registry, inspections, defects, service intervals, parts & fluids, and work orders — kept as one continuous record per asset. When equipment moves between plants, the record moves with it.
An asset and sub-asset hierarchy — the wash line, its conveyor, the conveyor's motor — tracked individually and inspected as one. Every meter reading knows where it came from, and a due-items rollup sits on every asset.
One inspection composes a section-group per child asset and computes a worst-case result — Pass, Operating with defects, or Out of service. An odometer field writes the reading back to the asset meter on submit, and an out-of-service result locks the asset until a passed return-to-service inspection clears it. Template library, per-asset profiles, 15 field types, and it keeps working offline in the field.
A defect carries a status machine, photos, a change log, downtime hours, a due date, and a meter snapshot auto-captured at creation. Work orders turn defects into scheduled, assignable jobs whose parts and labor costs roll up to the asset's history, with priority derived from severity.
Four service-interval types, with cadences by time — Once, Daily, Weekly, Monthly, Quarterly — or by meter: every N units, or meter-and-time, whichever comes first. A daily meter estimate projects meter-based due points onto real dates, always shown as an estimate with a ~.
Parts and fluids with a critical flag and minimum quantities — items below min wash red and pin to the top. A usage log per part, a replenishment log with quantity, vendor, ticket, and date, and monitored bulk tanks with live level bars carrying the reading source and freshness.
Reliability
The record doesn't just log failures — it gets ahead of them.
Why not a bolt-on CMMS
Downtime, workplace exams, and defects live on the same asset as production — maintenance is never a silo the plant reports into.
When equipment moves between plants, the whole history moves with it. No export, no import, no stale copy.
Meters, gates, and due items are properties of the record itself — not a spreadsheet beside the system of record.