Every active trip carries a state in the OCC: scheduled, dispatched, airborne, arrival window, on-block, post-flight. Position, fuel state, slot status and crew duty buffer update against that state in near real time. The duty officer sees a deviation before it becomes a notification to the operator.

Map view defaults to a global picture; drill-down per trip shows the OFP overlay, the alternate, the destination weather radar and the handling agent's status. The duty officer can talk to dispatch, the handling agent and the crew without switching windows or asking the operator to relay.

We tune alerts so that an OCC operator can trust them. A two-minute slot drift at LHR is not an alert; a fifteen-minute drift that puts the trip past the curfew is. Weather deteriorations at destination are flagged when they cross approach-minima, not on every TAF update. Crew duty is flagged when the buffer drops below the operator's policy floor, not at every push of the schedule.

Operators with their own OCC get the same feed via API or a read-only console so the two control centres see the same picture. We do not gate visibility.

Weather diversion: alternate is already coordinated. Slot loss: we have a backup slot or an alternate field staged. ATC closure: the rerouting is pre-built for the major Gulf and European disruptions. Permit revocation: alternate routing held warm for state-of-registry-sensitive corridors. Each playbook is a checklist, not a memory test.

When a real-world event lands outside the playbooks — a runway shutdown at OBBI, an ash advisory across the eastern Mediterranean — the duty officer escalates inside the OCC and starts the recovery while the supervisor brings in the operator and the captain. Speed beats elegance in those windows.

The OCC speaks to the captain via SATCOM, ACARS and the handler's company frequency on arrival. The operator gets a structured status update at defined trigger points: dispatch, pushback, top of climb, top of descent, on-block, and any deviation greater than a threshold. We do not flood the operator with chatter; we make every message worth opening.

Post-flight, every deviation is logged against the trip reference and reviewed in the weekly OCC stand-up. Trends — a slot policy tightening at a hub, a handler missing pushback windows, a corridor running consistently long — feed back into the dispatch defaults.

Shift hand-off is structured: every active trip is walked through, every open deviation has an owner, every pending escalation has a deadline. Trips do not fall through the seam between shifts because the seam is documented and audited.

For operators in time zones that do not overlap with our primary OCC, a named relationship lead sits in the operator's window so the strategic conversation happens inside business hours even while the OCC runs around the clock.