NP-SP-02 · Fleet Assignment & Tail Routing

📊

Process Flow Diagram (BPMN)

📋

L4 Process Steps

Step	Step Name	Role / Swim Lane	System	Input	Output	KPI	Dec?	Exc?
Phase 1 1.1	Ingest Approved Season Schedule	Fleet Planning Analyst	Amadeus SkyMAX	Final SSIM file from NP-SP-01	Schedule loaded into SkyMAX optimisation engine	100% of flights ingested without parse error	N	Y
1.2	Load Fleet Availability & Maintenance Windows	Fleet Planning Analyst	SkyMAX + Custom MRO System	Fleet register, maintenance plan, AOG reserve list	Available aircraft pool per date range	Fleet availability forecast accuracy ≥95%	Y	Y
Phase 2 2.1	Run Fleet Assignment Optimisation	Fleet Planning Analyst	Amadeus SkyMAX	Schedule, fleet pool, turn constraints, crew ratios	Initial fleet assignment: aircraft type per flight leg	Fleet utilisation ≥13 block hours/day; deadhead cost minimised	N	N
2.2	Validate Turn Time Feasibility	Network Operations Analyst	SkyMAX + Avtec Scout	Fleet assignment, ground time per station, gate data	Turn time feasibility report; flagged short-turns	0 turns below minimum turn time (25 min domestic / 35 min focus city)	Y	N
2.3	Generate Tail Routing Plan	Fleet Planning Analyst	Amadeus SkyMAX	Validated fleet assignment	Day-of-week rotation plan: tail number per flight sequence	Tail routing feasibility 100% (no orphaned tails)	Y	N
Phase 3 3.1	Cross-Check Crew-Aircraft Co-location	Crew Planning Analyst	Crew Management System (AWS) + SkyMAX	Tail routing plan, crew pairing plan	Co-location validation report	0 crew-aircraft positional mismatches at day-start	Y	Y
3.2	Maintenance Routing Alignment	MRO Planning Analyst	Custom MRO System	Tail routing plan, scheduled maintenance events	Maintenance-aligned routing; tails routed through maintenance bases on correct nights	100% of A-checks aligned to correct overnight station	Y	N
Phase 4 4.1	Stress-Test with IRROP Scenarios	Network Operations Manager	Avtec Scout NOC Console + SkySYM	Tail routing plan, historical weather/ATC disruption data	IRROP resilience score; recovery playbooks per disruption type	Recovery plan covers top-10 disruption scenarios; recovery time <3 hours	Y	N
4.2	Operations Control Final Approval	VP Network Operations Control	Avtec Scout	Stress-tested routing plan, all validation reports	Ops-approved tail routing plan	0 open conflicts at approval gate	Y	N
Phase 5 5.1	Publish Routing to Crew & MRO Systems	Fleet Planning Analyst	SkyMAX → Crew Management System (AWS), Custom MRO System	Approved tail routing plan	Routing published to downstream systems	Downstream sync confirmed within 2 hours	N	Y
5.2	Archive Plan & Update Capacity Model	Network Analyst	AWS S3 Data Lake	Final routing plan, utilisation actuals from prior season	Archived rotation file; updated capacity baseline model	Archive latency <24 hours post-season freeze	N	N

📋

Process Attributes

Identification

Process IDNP-SP-02

L1 DomainNetwork Planning & Scheduling

L2 ProcessSchedule Planning

L3 NameFleet Assignment & Tail Routing

L4 Steps11 across 5 phases

Decision Gates7 (all with iteration loops)

Exceptions4 documented

Swim Lanes (Roles)

Fleet Planning Analyst

Network Operations Analyst

Crew Planning Analyst

MRO Planning Analyst

Network Operations Manager

VP Network Operations Control

Network Analyst

Systems & Tools

Amadeus SkyMAXSkyMAX + Custom MRO SystemSkyMAX + Avtec ScoutCrew Management System (AWS) + SkyMAXCustom MRO SystemAvtec Scout NOC Console + SkySYMAvtec ScoutSkyMAX → Crew Management System (AWS), Custom MRO SystemAWS S3 Data Lake

Key Performance Indicators

Ingest Approved Season Schedule100% of flights ingested without parse error

Load Fleet Availability & Maintenance WindowsFleet availability forecast accuracy ≥95%

Run Fleet Assignment OptimisationFleet utilisation ≥13 block hours/day; deadhead cost minimised

Validate Turn Time Feasibility0 turns below minimum turn time (25 min domestic / 35 min focus city)

Generate Tail Routing PlanTail routing feasibility 100% (no orphaned tails)

Cross-Check Crew-Aircraft Co-location0 crew-aircraft positional mismatches at day-start

Maintenance Routing Alignment100% of A-checks aligned to correct overnight station

Stress-Test with IRROP ScenariosRecovery plan covers top-10 disruption scenarios; recovery time <3 hours

Airline-Specific Risks & Pain Points

SSIM format version mismatches between SkyWORKS export and SkyMAX import cause periodic re-loads

MRO system API to SkyMAX is custom-built and brittle; maintenance window changes often require manual SkyMAX refresh

Single fleet type removes payload/seat differentiation lever; optimisation is purely rotation-cost and utilisation-based

Post-Dec 2022: minimum turn time floor is now hard-coded constraint. Pre-2022, planners could override — this is now blocked

737-700 vs 737-800 capacity difference (143 vs 175) must align with demand forecast by leg — manual override common for thin markets

AWS ↔ SkyMAX API integration is the highest-risk interface in the planning stack; mismatch was root cause of Dec 2022 cascade

Inputs / Outputs

Primary InputFinal SSIM file from NP-SP-01

Primary OutputArchived rotation file; updated capacity baseline model