90-day advisory evaluation
An operational system.
Ready to pilot now.
Advisory-mode decision support in your OCC, measured against your own disruption baseline — not a concept study. Select pilot partners are being accepted from regional airlines, cargo and charter operators, airport authorities, and military aviation units.
Pilot timeline
From first conversation to a production-gated go-live, measured in weeks not years. Advisory mode throughout the pilot; production is gated on validation sign-off.
| Phase | Timeline | What happens |
|---|---|---|
| Discovery | 2 weeks | Stakeholder interviews, data inventory, integration feasibility, operational KPIs agreed. |
| Integration | 4 weeks | External feeds (flight data, weather/ATC) connected; 1–2 high-value internal systems (aircraft rotations, crew, or gate/turn) mapped to the normalized operational model with least-privilege access. |
| Validation | 4 weeks | Risk and recovery accuracy checked against historical disruption events; acceptance thresholds agreed with OCC leadership. |
| Pilot | 90 days | Advisory mode live in the OCC. Measure delay minutes avoided, misconnections prevented, recommendation acceptance rate, time-to-awareness, and modeled cost avoided. |
| Production cutover | 30 days | Enterprise hardening sign-off, staff training, go-live. Transition to enterprise SaaS or on-prem appliance contract. |
Pilot scope & integrations
Advisory mode first, 2–3 core workflows, external feeds plus one or two high-value internal integrations — enough to demonstrate measurable value without a lengthy enterprise program.
Data integrations
- External flight data — schedule, status, positions, gate/terminal, delay (FlightAware AeroAPI, Cirium FlightStats, or similar).
- Weather / ATC — METAR, TAF, GDP/ground stop, ATC flow constraints.
- Aircraft rotations (1–2 internal) — tail-specific turn chains; the binding dependency for disruption prediction.
- Crew management (optional) — duty time, pairings, reserve availability; gated on data-access agreement.
- Maintenance status (optional) — MEL/CDL, release ETA, AOG state.
Success metrics
Delay minutes avoidedPrimary KPI
Misconnections preventedPassenger impact
Recommendation acceptance rateTrust indicator
Time-to-awarenessDetection speed
Modeled cost avoidedExecutive ROI
Security & governance posture
In the engine today
- Role-based access control — station, fleet, and department scoping.
- Multi-factor authentication — TOTP-based MFA, scrypt password hashing.
- Hash-chained decision record — recommendations, approvals and actions appended to an HMAC-SHA256 chain that the platform can re-verify.
- Human-approval gates — required on all recovery actions, customer messages, crew and gate changes.
- On-prem capable — self-host or private VPC; no vendor cloud lock-in required.
Phase B hardening
- SSO / SAML / OIDC — enterprise identity federation.
- Data-retention policies — by customer and data class.
- Air-gapped appliance — offline read-only mode for sovereign / restricted-data environments.
- Model governance — approved prompt templates, output validation, red-team testing schedule.
Voiced ops briefing
The shift briefing the platform writes can also be the briefing your stations hear. Every spoken phrase is rule-built from a named record field — no generative model authors safety-relevant text. Demo audio is pre-baked; live audio is rendered by the AeroVox engine.
Voice module: AeroVox
Voiced shift briefing — Meridian ORD OCC
Meridian Air operations briefing, Day shift, ORD OCC. Time one five zero two local. ATC constraint. ORD Ground Delay Program. EDCTs in effect, average 38 minutes, convective flow from the west. Weather constraint. Convective line west of ORD. Building cells 14:30 to 18:00, affects west departures and DEN DFW arrivals. Weather constraint. Low ceilings BOS. MVFR easing after 18:00, minor arrival impact. Ground delay program rate seven two, average delay three four minutes. High risk. MERIDIAN 1842, ORD to LGA, risk eight six. Inbound tail N812MR, MER2051, running plus 38; projected 28 minute turn beats the 35 minute minimum, into an ORD ground delay program. High risk. MERIDIAN 419, ORD to ATL, risk seven niner. Open MEL on N905MR, hydraulic qty sensor. Release ETA slipped 15:30 to 16:10; spare N907MR frees at 15:50. All recovery actions are advisory and require human approval. End of briefing.
Phrase-to-field trace (9 phrases, deterministic — no generative author)
| Meridian Air operations briefing, Day shift, ORD OCC. | carrier.name, shift_label |
| Time one five zero two local. | as_of |
| ATC constraint. ORD Ground Delay Program. EDCTs in effect, average 38 minutes, convective flow from the west. | constraints[ATC] |
| Weather constraint. Convective line west of ORD. Building cells 14:30 to 18:00, affects west departures and DEN DFW arrivals. | constraints[Weather] |
| Weather constraint. Low ceilings BOS. MVFR easing after 18:00, minor arrival impact. | constraints[Weather] |
| Ground delay program rate seven two, average delay three four minutes. | tmi.program_rate, tmi.avg_delay_min |
| High risk. MERIDIAN 1842, ORD to LGA, risk eight six. Inbound tail N812MR, MER2051, running plus 38; projected 28 minute turn beats the 35 minute minimum, into an ORD ground delay program. | flights[MER1842] |
| High risk. MERIDIAN 419, ORD to ATL, risk seven niner. Open MEL on N905MR, hydraulic qty sensor. Release ETA slipped 15:30 to 16:10; spare N907MR frees at 15:50. | flights[MER0419] |
| All recovery actions are advisory and require human approval. End of briefing. | (fixed footer — advisory rule) |
AeroVox renders live FAA weather observations into multilingual broadcast phraseology today — this applies the same deterministic engine to TMI advisories and ops briefings.
Pricing & target segment
$50K – $150K
Paid pilot — depending on integrations, carrier size, and duration
Transitions to enterprise SaaS (annual platform + volume + support) or on-prem appliance license after a successful pilot.
Positioning. Decision support, not autonomous dispatch. Human-in-the-loop on every operational action. Advisory mode throughout the pilot period.
Target pilot segment
- Regional airlines — ready for demonstrations and pilot conversations now.
- Cargo operators — strong fit for network visibility and maintenance integration.
- Charter operators — rapid deployment, lower integration overhead.
- Airport authorities — gate/turn and ground operations workflows.
- Military aviation units — on-prem / sovereign deployment option; HMAC audit chain.
Major carriers come after the pilot phase — they need SSO, deeper integrations, security governance, and at least one pilot reference.