ATOMS is the
brain of the
airport.
The operating intelligence layer of the AOCC. Senses every airfield event, fuses them onto one clock, runs the AI that turns events into decisions, dispatches advisories, writes the audit-ready record. Start with the core; every NorthSky product gives the brain more to sense.
The AOCC today
is a wall of dashboards.
An AOCC at a hub is a room of screens — A-CDM, ramp ops, runway, weather, FOD, TOBT — each built by a different vendor. The CEO walks in and sees a wall, not a picture. ATOMS is the picture.
- A-CDM shows TOBT but not the apron exception that made it slip.
- Tower sees runway throughput but not the FOD about to close it.
- Airline ops sees the delay code but not the evidence of cause.
- Reconciliation = a meeting next morning with three different stories.
- Every event — apron, taxi, runway, FOD, video — on one clock.
- The AI turns event streams into advisories — pushback nudges, config flips, sequencing gains.
- Every role sees its own view of the same record.
- Reconciliation by construction. One record, not three.
Five functions.
One brain.
A brain doesn't display data — it converts signals into action and keeps a record. ATOMS does exactly that for the airport.
Sense.
AeroGround (apron), AeroTaxi (surface), AeroRunway (runway), AeroFOD (debris), AeroFeedback (passenger). AeroVision is the video spine. A-CDM, ATC, AODB, DCS, BHS, ADS-B fill in the rest.
Fuse.
Every event time-aligned on the platform clock; attributed to tail / stand / runway; classified into a shared taxonomy. Same time-source, same grammar, same audit trail. The fusion is what makes the record reconciled by construction.
Decide.
Models read the live stream and emit advisories — pushback nudges, config flips, sequencing gains, RET recs. Each carries a confidence band. Controller/watch manager/handler accept or override. Acceptance climbs as models learn.
Act.
Advisories reach the actor — tower, watch manager, handler crew, airline ops, CEO. Every action and override captured back into the record.
Remember.
Every event, advisory, action, override — timestamped, hashed, immutable. DGCA audit log produced from the same record the operation runs on. The models also learn from it.
The turn cycle,
from origin to wheels-up.
A turnaround doesn't start when the chocks go on. It starts when the inbound leaves its origin and ends when it's wheels-up on the outbound. ATOMS captures the whole arc — every phase, every event, every actor — on one operational record.
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.
Delivered vs declared capacity, fuel + CO₂ saved, FOD-closures-avoided, OTP trend, audit readiness. One screen, not seven.
AOCC duty manager.
Live exception queue, config recs, congestion hot-spots, FOD events, TOBT variances. Acts on advisories, dispatches the right team before the schedule breaks.
Safety + regulator.
Continuous safety record — FOD, incursion advisories, ramp violations, closures. Audit-ready in regulator format — 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. Same record, more decisions.
Does the AI take decisions away from the tower?
No. Every output is an advisory. Duty controller and watch manager retain authority. Acceptance climbs to 85–90% once controllers 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 back 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 customers start with Core + AeroGround; AeroTaxi in month three; AeroRunway by month six. Ladder is additive.
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, your real taxiways, your real runway throughput. We'll show you what each step on the capability ladder unlocks and propose a deployment scoped to your priorities.