The airline planning cycle, end to end

A flight doesn’t appear fully formed. It travels a long road — from a strategic bet about a market, through months of refinement, to an aircraft pushing back from a gate. Understanding that road, and where schedule data flows along it, makes it obvious why the humble SSIM file sits at the centre of so much.

The cycle, stage by stage

The path from strategy to operation runs roughly like this:

1. Network planning. The long-range question: which markets do we serve, and with how much capacity? Route economics, demand forecasts, competition. Output: a route network and broad capacity plan.
2. Schedule development. Turning the network into an actual timetable — frequencies, departure times, aircraft rotations, and the bank structure that makes connections work. This is where minimum connect times and hub waves get engineered.
3. Fleet assignment. Matching aircraft types to flights by demand and range — deciding which tail flies which leg, subject to maintenance and crew.
4. Slot coordination. Securing the slots the schedule needs at coordinated airports, and reconciling the plan with what’s actually held.
5. Publication. Releasing the schedule to the world as an SSIM file — to airports, GDSs, distributors, and internal systems.
6. Maintenance. Keeping it current through the season with SSM and ASM messages as things change.
7. Day of operations. Operations control flies the plan — and every disruption feeds back into how the next schedule is built.

It’s genuinely a cycle: what happens on the day, and how the last season performed, informs the next round of network planning.

Who touches it, and what moves

Notice the connective tissue running down the right-hand column: nearly every stage produces, consumes, or modifies schedule data. The network plan becomes a timetable becomes a published file becomes a stream of changes becomes the operated day — and each hand-off is a place the data has to stay faithful.

Where it breaks down

Because the cycle spans so many teams and systems, the failures tend to happen at the seams:

• A schedule that no longer matches the slots held.
• A published file that drifts from the internal plan after a season of messages.
• A comparison between “what we planned” and “what we published” that takes days because the two live in different tools.
• Conflicts — an aircraft double-assigned, an impossible turnaround — that slip through until day of operations.

Every one of these is a schedule-data problem: reading a feed correctly, comparing two versions, checking one dataset against another.

The planning cycle is a relay race, and schedule data is the baton. Drop it at a hand-off and the whole leg has to be re-run.

Doing it well

The teams that run this cycle smoothly share a trait: they can read, compare, and check schedule data quickly at every seam — not just at publication. Open the feed fast, diff two versions, validate against the standard, reconcile against slots. That’s the foundation SSIM Toolkit is built to provide: one fast, local, deterministic place to work with the schedule at every stage of its life, so the baton never gets dropped.

Next, the failure mode that hides at the seams: deconfliction.