Scope
A typical aviation pilot covers one terminal or hub and two to three flows from {crew coverage, gate flow, MRO dispatch, disruption recovery}. We connect to your AODB, MRO platform, and HRIS via existing APIs and avoid touching your safety-critical systems of record beyond read-write fields agreed in the SOW.
Success criteria
Concrete, measured against your own baseline. Signal-to-decision under 200ms on in-scope flows in the sandbox. First production writeback to your AODB or MRO system by week three. A measurable reduction in same-day dispatch error rate, with the baseline you bring on day one.
Timeline
Week 1, connectors and tenancy. Weeks 2–3, sandbox decisions and first writeback to a non-production tenant. Weeks 4–8, expansion to two more flows. Weeks 9–12, production graduation review with your safety and IT leads.
First decision in production
Target, the first MAIA-authored decision lands in your AODB or MRO system within 21 days of kickoff. We track this against the SOW and surface the milestone to both teams in real time.
MAIA is in pilot with a small number of design partners, by design. We do not publish anonymised partner outcomes here, the way many vendors do, and we will not invent ones. When we have an outcome we can name on a logo and attest to in audit, we will publish it. Until then, what you see above is how we structure the engagement, end to end.
