Work orders and release to service
Log the work, ground the unit, and have a second person sign it back into service.
Maintenance keeps units airworthy. The core object is the work order: one piece of work on one unit, such as an inspection, a calibration, a firmware update or a repair.
Work orders
Open work orders from Maintenance → Work orders. Each one has a code, a unit, a type, a priority, a technician and a status.
| Status | Meaning |
|---|---|
open | Logged, not started |
in_progress | A technician is working on it |
awaiting_signoff | The work is done and needs a release to service |
closed | Signed off; the unit is back in service |
Creating and moving work orders needs edit on Maintenance. Technicians and the Maintenance Planner agent can do this.
The Overview shows due and overdue work, grounded units and flight hours against each unit type's service interval. Forecast predicts component due dates from flight hours and health trends.
Grounding
A work order can ground its unit. A grounded unit:
- is hidden from the unit picker in the mission planner,
- fails the "Unit assigned and airworthy" preflight check,
- cannot be launched: the database refuses it (see invariant 5).
The unit stays grounded until the work order is released to service.
Four-eyes release to service
Closing a grounding work order puts the unit back in the air, so it needs two people:
- The technician does the work and moves the order to awaiting sign-off.
- A second person with
publishon Maintenance, who is not that technician, signs it off.
On sign-off the order closes and the unit is ungrounded. If the technician tries to sign off their own work, the database refuses the write, even if they have publish.
In the demo workspace, Taylor Kim and Alex Morgan are technicians (edit) and Jamie Patel, the maintenance lead, signs off (publish). Agents never sign off.
Service intervals and limits are defaults for the demo. Use your manufacturer's maintenance programme for real units.