Role playbook · FLEET_MANAGER
Fleet Manager
Fleet operations leads, dispatchers and planners who coordinate aircraft availability against the daily schedule.
Audience: Fleet ops / dispatch / planningTime to first value: first full week with the live monitor
Why CyViation matters in your role
Fleet ops already balances maintenance, crew, weather and ATC slots. CyViation surfaces two more variables that used to be invisible:
- Route-level GNSS / cyber threat zones along today's planned tracks.
- Tail-level cyber-maintenance status — whether a tail has unapplied CMBs that should block dispatch.
The outcome isn't "more reds on the board" — it's better-informed small adjustments made earlier, before the day spirals.
Daily playbook
- Compare today's schedule against active threat zones; flag sectors needing an alternate routing decision.
[Overwatch → GNSS Threat Map] - Coordinate with the dispatcher on route adjustments — the live monitor shows what dispatcher and SOC see at the same time.
[SkyRay → Dispatcher Live Monitor] - Confirm cyber-maintenance status per tail — no aircraft launches with an unapplied flight-blocking advisory.
[SkyRay → Aircraft Asset View] - Check the fleet-wide availability indicator before the morning brief.
[SkyRay → Fleet Operations View]
Weekly playbook
- Review aircraft-availability impact from cyber events — was the impact proportional to the risk?
- Plan maintenance windows with MRO to minimise schedule disruption.
- Sync with MRO on the upcoming patch cycle — which tails, which nights, which fleets.
- Review aggregated pilot feedback — flying crew see things planners don't.
- Trial the alert-before-zone (predictive) view on at least one route per week; feed results back to product.
First 30 days
- Full fleet roster mapped into SkyRay with tail / type / base
- Availability-impact thresholds configured (what counts as "fleet degraded")
- Ran one full week of dispatcher coordination using the live monitor
- Approved or declined one route-change recommendation, with rationale logged
- Pilot-tested the alert-before-zone view on a high-risk route; filed product feedback
- Established the daily ops brief slot where SkyRay status is a standard agenda item
- Met your SOC liaison and your MRO duty manager
Key screens
| Use case | Screen |
|---|---|
| Daily fleet picture | [SkyRay → Fleet Operations View] |
| Coordinate live with dispatcher / SOC | Dispatcher OCC · [SkyRay → Dispatcher Live Monitor] |
| Route-level GNSS threat picture | [Overwatch → GNSS Threat Map] |
| Maintenance window planning | [SkyRay → Maintenance Calendar] |
| Tail-level cyber status | [SkyRay → Aircraft Asset View] |
When to escalate
| Situation | Who | How |
|---|---|---|
| Threat zone makes today's primary routing untenable | Dispatcher + Ops Control | Standard ops decision, SkyRay note attached |
| Patch backlog risks grounding a tail tomorrow | MRO duty manager + CISO | Plan, don't react |
| Recurring high-severity zones on the same corridor | SOC + CyViation TAM | Strategic, not tactical |
| Pilot feedback says alerts are noisy | SOC liaison | Weekly digest reply is fine |
Glossary
Full list on the Glossary page. Key terms here: alert-before-zone, tail, CMB, RNP corridor, risk acceptance.