SkywardOpsDocs

Maintenance

Keep units airworthy, with a second pair of eyes.

Keep units airworthy, with a second pair of eyes.

/app/maintenance · ready · accent #C27C0E

Work orders, calibrations, firmware and repairs per unit, flight-hour service intervals, predicted component wear and a four-eyes release to service.

Pages

Each module has at most four pages under /app/maintenance.

PagePathKindWhat it shows
Overview/app/maintenanceDashboardUnits by state (grounded, in the hangar, service due, cleared), parts and labour spend by work type, the service runway and the sign-off queue.
Work orders/app/maintenance/work-ordersListEach work order with unit, priority, status, technician, due date and who signed it off.
Forecast/app/maintenance/forecastAIPredicted service date, likely component and confidence per unit.
Checklists/app/maintenance/checklistsLibraryInspection and calibration steps per unit type.
Integrations/app/maintenance/integrationsintegrationsThe connectors this module takes data from, with status, last sync and what each one feeds in.

Opening

The dashboard opens with its own layout, Hangar board, built for this module's data:

  • Every unit in one state: grounded, in the hangar, service due or cleared to fly
  • Parts and labour spend by work type (treemap), against the 30 days before
  • Service runway: units closest to their next service
  • Sign-off queue and work orders per week

Features

  • Work orders per unit
  • Service intervals by flight hours
  • Firmware tracking
  • Four-eyes release to service
  • Grounding that blocks launches

Who can do what

Everyone with view on Maintenance can read its pages. Changes need edit; the actions below that need publish are the ones with real-world effect. Agents are capped at edit, so they can never run a publish action.

ActionWhat it doesNeeds
workorder.createOpen a work orderedit
workorder.statusMove a work order through its statusesedit
workorder.signoffRelease a unit to service (four-eyes sign-off)publish

Any action not listed needs publish (the app fails closed).

Integrations

Every module has an Integrations page (/app/maintenance/integrations) next to its data pages. It lists the connectors below with their status and last sync. Owners and admins connect, test or disconnect them through the shared Connections flow (the same dialog as Settings → Connections); everyone else sees the page read-only. No external calls are made in this build: in the demo the statuses are generated, and in local database mode a saved connector stays pending.

ConnectionUsed forStatusVerify before launch
PX4 / MAVLinkFlight hours and firmware versions from dronesmockAutopilot versions, mission protocol, signing
ROS 2 bridgeRun hours and firmware versions from trucks and robotsmockMessage types, QoS profiles, transport auth (rosbridge or Zenoh)
AI modelsThe Forecast pagemockProvider API keys, catalog prices (none verified yet), credit metering, prompt review

See Connections for the full list.

On this page