| Positioning — legacy cloud vs agentic | AI agents + sub-second loop over FDM / QAR / radar | Azure-hosted ACMS batch, Airbus scheduled analytics | GE private cloud + AWS, industrial streaming (energy / manufacturing) | IBM on-prem / hybrid, post-incident triggering | Honeywell Connected Plant, locked OEM hosting |
|---|
| Surveillance type (24/7 continuous vs scheduled) | 24/7 AI agents, sub-second loop over FDM / QAR / radar | Daily ACMS batch — no live agent-level loop | Scheduled industrial streaming, no sub-second aviation loop | Post-incident work-orders, business-hours | Honeywell programme alerts, business-hours |
|---|
| Legacy dependency / long onboardings | No legacy — AI agents + FDM / QAR / MRO connectors, read-only | Azure-hosted ACMS batch + Airbus OEM enterprise contract | GE private cloud + industrial stack, long framework contract | IBM on-prem + 3-12 months per-fleet customisation | Honeywell Connected Plant + long framework contracts |
|---|
| FAA / EASA compliance | Part 5 SMS / Part-CAMO / ED-153 — end-to-end audit trail | EASA-conformant inside Airbus, partial outside | Industrial scope, no civil-aviation alignment | MRO post-incident reporting, not continuous | DO-178C on Honeywell parts, separate certification |
|---|
| Data sovereignty (on-prem outposts) | Montréal + sovereign on-prem outposts, FAA / EASA timezone | Azure Airbus-hosted — no sovereign on-prem outpost | AWS + GE private cloud — no on-prem outpost | IBM on-prem — sovereignty possible, offshore support | Honeywell Connected Plant, locked hosting |
|---|
| Customer target (MRO · defense · airline) | Airline + business jets + defense + MRO (all segments) | Airline (Airbus-first), partial MRO | Industry / energy — outside civil aviation | MRO asset-centric (pure-play) | Airline + defense, Honeywell-OEM first |
|---|