Design an Airline Aircraft Assignment Planner
Reassign airport aircraft after delays and publish a feasible, versioned flight plan with revised departure and arrival times.
Problem statement
For this exercise, assume one airline plans outbound flights at one airport over a rolling 24-hour horizon. Each flight has an ID, scheduled departure, fixed duration and required aircraft class.
An availability source reports airport ground visits with stable visit and aircraft IDs, class, earliest readyAt, expected/present/unavailable state and source revision. readyAt already includes preparation time.
A visit may supply only one outbound flight; another use of the same aircraft requires a distinct later airport visit from the source. Propose compatible assignments, including replacement aircraft when an inbound delay changes readyAt.
For an assignment, departure is the latest of scheduled departure, readyAt and the planning time; arrival is departure plus the fixed duration. Show changed times, delay impact and explicit unassigned reasons. An operator compares proposals and approves a complete plan revision.
Each flight and visit has at most one active assignment. Approval must reject changed plan or availability versions without partial changes; identical retries recover the same outcome. A later source update marks affected plans outdated and leads to a new proposal.
This is a software planning tool: approval does not establish physical arrival or authorize departure. Crew, maintenance decisions, gates, air-traffic control and global network optimization are outside scope.
What to build
- Ingest versioned flight and airport-visit availability facts and expose affected stale plans.
- Compare feasible aircraft assignments after a delay and show revised departure, arrival, delay impact and unassigned reasons.
- Approve the complete assignment change set atomically, recover repeated approval requests and retain plan history.
At scale
- For this exercise, assume up to 500 airport visits and 2,000 outbound flights in the 24-hour planning view, with availability bursts of 10 updates per second.
- For this exercise, aim to return a bounded proposal within two seconds at that load; a stale proposal must be recomputed or rejected rather than approved from old evidence.
- For this exercise, retain approved plan revisions, their input references and approval outcomes for 30 days; the dashboard shows its plan version and stale-input state.