Aviation, inside the rules.
OpenAir is the aviation platform on Mission Systems. Crew, compliance and disruption as aviation-specific modules, on the same operational model as everything else the operation runs.
Built for a flight operation, module by module.
The general platform models people, shifts and sites. OpenAir adds what a flight operation runs on and nothing else models properly.
Crew rostering
Pairings and rosters solved against demand, qualifications, cost and fairness together, and kept solving after publication.
Flight and duty limits
Duty periods, minimum rest and cumulative ceilings bind the solver. Under CASA, fatigue risk management enters the same way, as a constraint rather than a sign-off.
Currency and qualifications
Type ratings, recency, line checks and medical expiry on one crew record with their dates. A pairing that would assign an out-of-currency crew member is infeasible.
Disruption
A delay, a sick call or an aircraft swap re-enters the solve while the day is still running. The roster re-solves around it and holds every limit it held before.
What it writes to the model, and what Launchpad does with it.
A crew member is one record whether the roster, the training department or payroll is looking at it. Currency is checked at the moment of assignment, from that record.
- Reads & writes
- crews, aircraft, pairings, duty periods, qualifications, currency
- Launchpad
- Solves the crew roster inside flight and duty limits. Blocks an out-of-currency assignment. Re-solves around a delay or an aircraft swap. Records which constraint bound each assignment.
- Autonomy
- Set per capability, from off to unattended, and movable back
- Works with
- Workforce, Procurement, Analytics
- Regime
- CASA implemented as the worked case; other regulators modelled against their published rules as configuration
Crew, rostered inside the rules.
A compliant roster and a roster you audited afterwards are different objects. OpenAir produces the first kind: a breach is an infeasible answer at solve time, so the exception queue that follows a published roster stops existing.
How it runs in a flight operationFAQ
They share the solver and the operational model. Workforce is the team application for rostering, HR and payroll in any sector; OpenAir adds the aviation-specific modules on top: flight and duty limits, fatigue risk management, currency, pairings and disruption. A flight operation runs OpenAir; its ground and office teams can run Workforce beside it on the same records.
CASA is the regime implemented as the worked case: flight and duty time limits and fatigue risk management as hard constraints. Another regulator’s limits are configuration rather than code, modelled against its published rules with your compliance team in the room before anything goes live.
Every assignment carries the constraints that applied, which of them were binding and why the crew member was chosen. A regulator’s question is answered from the record rather than reconstructed afterwards.
You set that per capability. It can propose and wait, publish inside limits you set and tell you afterwards, or run unattended. Most operations start with approval on every publish and raise the dial as the record builds.