What you get
Work orders that know their own state
Every job carries its status, its service level, who it is on, and what it is still short of.
An asset register with history
Hierarchy, meters, cover, failures, costs and downtime, all on the machine they belong to.
Maintenance that raises itself
Plans triggered by the calendar, a meter reading, an event or a measured condition.
Dispatch with the checks shown
Drag a job onto a technician and see travel, skills, parts, tools and clashes before you commit.
Reliability you can argue with
Bad actors ranked against the fleet, with recommendations you can accept or dismiss.
A handset that works with no signal
Technicians execute jobs offline; the queue syncs when signal returns.
Condition monitoring that raises work
Sensors bound to a meter turn a live reading into maintenance that comes due on its own.
Investigations that get followed up
Root cause, corrective actions, and a review months later asking whether they worked.
Reports that answer as you
Build a report once; every reader sees only the rows they could already open.
Who uses it
Technicians
Technicians
Technicians pick up jobs on the field app, work through the checklist at the
machine, record hours, parts, meter readings and photographs, and close the job — with or
without a network. Everything queues locally and syncs later.
Planners
Planners
Planners triage requests, build maintenance plans,
watch the capacity plan for the day that will not fit, and use the
dispatch board to put the right person on the right job.
Supervisors
Supervisors
Supervisors run the shop floor: assigning and reassigning work, moving preventive rounds,
recording failures, and clearing what is blocked.
Storekeepers
Storekeepers
Storekeepers manage parts across stores, issue against jobs, and work the
reorder list before a shortage stops a repair.
Managers and executives
Managers and executives
Managers watch backlog, SLA and cost. Executives read the board view:
availability, MTBF, MTTR, PM compliance, downtime and what needs attention.
Administrators
Administrators
Administrators configure the plant — sites and locations,
people and access, the statuses and
fields the rest of the product is built on, and the
rules that decide what happens without anybody asking.
How the pieces fit
An asset is the machine. A work request is somebody reporting that something is wrong. A work order is the job itself. A maintenance plan raises work orders on a schedule. A requirement is what a job needs before it can start — a part, a tool, a skill, a vendor. An entitlement decides whether a contract or warranty pays for it.Almost everything in the lists below — statuses, priorities, types, categories — is configurable
per organisation. What this documentation shows are the defaults a new organisation starts with.
Your plant may have renamed them. See statuses and transitions.
Start here
Sign in, find your way around, and follow a job from request to close.