How it works
Four steps. Then you are running it.
If a vendor cannot walk this loop on a whiteboard, they are selling logging, not maintenance.
-
1. Tree
Build the plant as a tree: site, area, line, asset. Names the floor already uses. This is the map everyone shares — planner, tech, and later, the person who signs.
-
2. Work on the asset
When something fails, the work order hangs on that node. Not on a person, not in email. The backlog is a list of jobs on machines.
-
3. PM fires
The PM engine is watching the same tree. When a service is due, it becomes work on that asset — same object, same closeout — not a ghost on a wall calendar.
-
4. Tech closes on the floor
The technician PWA shows one job, a checklist, scan and photo. Done means the planner’s board moved. If it cannot close in the aisle, it will not close.
That is the demo. Not a tour of settings.