Maintenance · Maintenance Bay
Turn due work into accountable maintenance.
A maintenance calendar does not show the parts, downtime and repair history behind machine availability.
This is a capability inside Lightning Pharos, not a separate product.
Release a preventive or breakdown work order.
01 · What ships
The complete working surface.
Planned upkeep that competes for the same hours as production.
- 01
Preventive schedules by calendar or by meter reading
- 02
Six-state maintenance work orders
- 03
Meter readings, downtime events, and derived availability
- 04
Parts issued from Inventory against the work order
- 05
Breakdown, repair, and closure history against the machine
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Release a preventive or breakdown work order.
- 02 / 03
Governed event
State, meter, downtime, parts and closure are recorded against the asset.
- 03 / 03
Connected result
The asset keeps the repair history. Recorded parts consume available stock; a shortage keeps a stock note instead of inventing a movement.
03 · What it needs
Connected by design.
Pharos requires these modules first because the workflow depends on their records. The dependency is enforced in the product.
04 · Where it stops
The boundary is part of the product.
There is no OEE, MTBF or MTTR calculation, labour-hours ledger, full repair cost, asset hierarchy, failure-code library, or warranty workflow.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system