The brain
of the airport.
The AOCC's operating intelligence layer. Sense, fuse, decide, act, remember — every airfield event on one clock, AI advisories, audit-ready record by construction.
The AOCC today
is a wall of dashboards.
A hub AOCC is a room of screens — A-CDM, ramp, runway, weather, FOD — each from a different vendor. The CEO walks in and sees a wall, not a picture. ATOMS is the picture.
- A-CDM shows TOBT — not the apron exception that slipped it.
- Tower sees throughput — not the FOD about to close the runway.
- Airline ops sees the delay code — not the cause.
- Reconciliation — three different stories next morning.
- Every event — apron, taxi, runway, FOD, video — on one clock.
- AI advisories — pushback nudges, config flips, sequencing gains.
- Every role sees its view of the same record.
- Reconciled by construction.
Five functions.
One brain.
A brain doesn't display data — it converts signals into action and keeps the record.
Sense.
Five NorthSky products feed in; AeroVision is the video spine. A-CDM, ATC, AODB, DCS, BHS, ADS-B fill the rest.
Fuse.
Time-aligned on the platform clock; attributed to tail / stand / runway; classified into one shared taxonomy. This is what makes the record reconciled by construction.
Decide.
Predictive models emit advisories — pushback nudges, config flips, sequencing gains — with confidence bands. Advisory, not command. Acceptance climbs as models learn the aerodrome.
Act.
Advisories reach the actor — tower, watch manager, handler crew, airline ops. Every action and override logged back.
Remember.
Every event, advisory, action, override — timestamped, hashed, immutable. DGCA audit log produced from the same record the operation runs on.
The turn cycle,
from origin to wheels-up.
A turnaround doesn't start at chocks. It starts when the inbound leaves its origin and ends wheels-up on the outbound. ATOMS captures the whole arc.
Phases 1–4 use third-party feeds (ADS-B, AODB, DCS, ATC). Phases 5–7 are captured by NorthSky hardware packs — opt-in below. Phase 8 closes the record and opens the next cycle.
Three roles.
One record, three views.
Airport CEO.
One screen, not seven. Delivered vs declared, fuel + CO₂ saved, OTP trend, audit readiness.
AOCC duty manager.
Acts on advisories — dispatches before the schedule breaks. Exception queue, config recs, hot-spots, TOBT variances.
Safety + regulator.
Continuous safety record — FOD, incursions, ramp violations. Audit-ready DGCA / ICAO Annex 14 / A-CDM.
What changes when
the record is shared.
How ATOMS sees
the airport.
Existing infrastructure first. Apron CCTV, taxiway optics, runway-end cameras. NorthSky fills coverage gaps; no rip-and-replace.
Edge boxes at the stand, taxiway, or runway end. Sub-second latency, low bandwidth. Tower outage doesn't blind the apron.
Events stream to the NorthSky platform. Airport ops, airline ops, and the ground handler each see their own view of the same record. Audit trail by design. In-region inference. Read AI governance →
Plugs into the
systems you already run.
Inbound feeds
- ADS-B for position + timing.
- AODB for the flight schedule.
- DCS for departure control.
- BHS for baggage milestones.
- Tower / ATC for runway events.
Outbound flows
- AOCC dashboard — full network view.
- Airline ops — per-flight timeline with delay attribution.
- Handler dispatch — per-team performance, exception queue.
- A-CDM network manager feeds where applicable.
- Open REST + webhooks for everything else.
Common questions.
What does basic ATOMS — without add-ons — give us?
The turn-cycle record fed by your existing A-CDM, AODB, ADS-B, DCS, ATC, BHS. Per-flight timeline, exception queue, three-way transparency, audit log. Light up AeroGround → sees the apron. Add AeroTaxi → sees the network.
Does the AI take decisions away from the tower?
No. Every output is an advisory. Controllers retain authority. Acceptance climbs to 85–90% once they see the predictions land.
How is ATOMS different from our A-CDM platform?
A-CDM is a milestone-sharing protocol; ATOMS is the brain that reads A-CDM, fuses it with everything else, runs AI, and writes the operating record. ATOMS feeds A-CDM; doesn't replace it.
Do I have to take all the feeds?
No. Each is independently licensed. Most start with Core + AeroGround; AeroTaxi in month three; AeroRunway by month six.
Ready to deploy.
Production-tested. Pilots scoped in days, live in weeks. Pair with AeroTaxi and AeroRunway to extend the operating record across taxi and runway.
Bring the brain
to your AOCC.
A 30-minute walkthrough on your real stands, taxiways, and runway throughput. We'll show what each step on the ladder unlocks — and propose a deployment scoped to your priorities.