Multi-trigger schedules
Calendar (every 7 days) or meter (every 250 engine hours). The meter schedule fires on the device, from the reading the technician just took.
Engine-hour PM fires offline, at the moment of the reading. No scripts.
Preventive maintenance
Calendar, meter, and condition-based schedules. Pause a schedule. Reschedule without breaking audit. Generate the compliance report in one click.
Calendar (every 7 days) or meter (every 250 engine hours). The meter schedule fires on the device, from the reading the technician just took.
Engine-hour PM fires offline, at the moment of the reading. No scripts.
Pause a schedule while a machine is out. Per-asset intervals. A PM is never raised twice for the same day.
A paused schedule generates nothing and keeps its history.
On-time %, overdue count and skipped %, by team or asset. Export for internal audit.
One shared definition — the report and the app compute compliance the same way.
Keep exploring
Assets
Tree-and-table view, status pills, criticality glyphs. The hierarchy is a Postgres ltree, so depth costs you nothing.
Explore →Work orders
Raise, assign, execute, close. Raise it at the machine with no signal, assign it to a technician or a team, and they accept or decline in one tap.
Explore →Mobile
Technicians work where the work is. Photos, signatures, meter readings, parts pulled — all queue locally and sync the moment connectivity returns.
Explore →Thirty minutes on your assets, your shift pattern, your data.