Beyond ATC · Airport ground operations

A flight schedule instead of an airspace, but the same shape of problem

SkyRoster has never rostered a ramp agent. Everything on this page is a mapping exercise against the product's own architecture, checked here in the open, not a description of a deployment. Airport ground operations is, of the four sectors on this site, the closest to ATC's own shape: safety-critical permits with expiry dates, multi-role coverage against a demand curve that moves within the hour, and a workforce that already trades shifts informally whether or not the software behind it checks the trade.

The scheduling problem

What ramp scheduling actually has to hold

Coverage shape

A turnaround is a fixed sequence of tasks against a fixed block of time once an aircraft is on stand. Miss the window and the delay is immediate and visible, not absorbed quietly the way a quiet control room can absorb a late relief.

Qualifications

An airside driving permit, a dangerous-goods certificate, a de-icing qualification, a marshalling sign-off. Each has its own validity period, and several require a periodic practical reassessment rather than a one-time exam.

Statutory rest

Ground staff answer to general working-time law rather than a flight-crew-specific fatigue rule. It is still a duty-length and rest constraint an engine would have to enforce, whatever instrument states it for a given country.

Demand pattern

Demand tracks the flight schedule, not the clock. A bank of departures at the top of the hour needs far more ramp staff than that hour's average would suggest.

What maps directly

Mechanisms already built for a different name

Every item below is an illustrative mapping against SkyRoster's existing data model.modelled None of it has been configured for a ground handler, and none of it has been proven at an airport's scale.

Working positions and stacked qualifications

A ramp role, marshaller, baggage handler, de-icing operator, pushback driver, becomes a working position. The airside permit, the dangerous-goods certificate, the de-icing sign-off become qualifications and requirements with their own validity windows, exactly the mechanism that already gates an ATC position on a current medical certificate. See /platform/competency.

Quarter-hour demand resolution

Sector planning already rejects an hourly demand model, because an hour can hide two very different fifteen-minute pictures. A departure bank is the same argument in a different vocabulary: average it across the hour and the peak disappears from the plan, not from the apron. See /platform/sector-planning.

Manpower requirements per stand or turnaround

How many people, with which qualification, covering which stand, at what time, is the same table shape sector planning already builds for airspace and working positions. See /platform/configuration.

Tactical threshold tolerance

A threshold table already lets a unit state the shortfall it will tolerate during a genuine shortage rather than demand a hundred per cent it cannot reach. An irregular-operations day at an airport is the same situation under a different name. See /platform/tactical-rostering.

Swap check re-verification

A ramp crew trading a shift would need the same re-check a controller's swap already gets: qualification current, rest intact, before either side can confirm it, not after. See /platform/shift-swaps.

A departure bank, read the way sector planning already reads a traffic peak

modelled

The shape: Six aircraft on stand inside the same clock hour, staffed against a fixed headcount set for that hour's average.
What it shows: The average hides the peak. For perhaps twenty minutes inside that hour every stand needs a full turnaround crew, and for the rest, most of them are idle. A fifteen-minute demand grid, the same one built for ATC sector openings, would show that peak as an actual staffing number instead of averaging it into invisibility.
What it does not show: Nobody has run this against a real airport's stand allocation. It is the same reasoning applied to a different demand curve, not a validated forecast, and not a saving anyone has measured.

What would need new rules or new work

Where the honest answer is development, not a settings screen

Multi-employer coordination

SkyRoster's unit model assumes one organisation's own units. A shared apron staffed by several competing ground handlers, each serving different airlines under different contracts, is a different data shape. This is the one place on this page where the honest answer is new product work, not a configuration change.

A flight-schedule demand feed

Sector planning's demand comes from a sector configuration an administrator defines ahead of time. Ground-ops demand that tracks a live flight schedule and its changes would need a feed from an airport or airline system, an integration that does not exist today.

Irregular-operations re-planning

A diversion or a ground stop needs fast, cascading re-crewing tied to the schedule change as it happens, not a periodic re-solve. That is a different workflow shape from a planned swap or a leave request.

The engine

Bring your turnaround times, not just your headcount.

A working session with your own turnaround profile and permit list shows exactly which of this page's mappings hold, and which of the open questions above would actually need building first.

Book a working session Send a question instead