Comparison
Crew roster optimisers: the five categories of tool, compared
Crew scheduling tools fall into five categories: the scheduling module of an operations suite, the compliance checker, the generic optimisation platform you model yourself, the large-carrier network optimiser, and the vertical optimisation add-on connected by API. They do not solve the same problem, which is why comparing them feature by feature produces a meaningless table.
This comparison is published by a vendor that belongs to the fifth category, which is worth stating in the first paragraph. It names no competitor: brand comparisons age badly and help nobody decide. Comparing tool models does something more durable. It lets you place any solution on the market, including ones that do not exist yet.
What are the five categories?
1. The operations suite's scheduling module. One brick among many in a system that covers flights, quoting, maintenance and documents. Its strength is native data integration; its optimisation depth varies enormously between vendors, and it is rarely the module the suite was built around.
2. The compliance checker. A tool that verifies a roster a human has built: it computes counters, flags FDP breaches, warns on expiring qualifications. It generates nothing. A surprising number of products marketed as "optimisers" belong here.
3. The generic optimisation platform. A constraint solver, often an excellent one, that knows nothing about aviation until somebody models the rules into it. It is a technology component, not a domain product: the FTL model, the qualification logic and the duty patterns all have to be written, then maintained.
4. The large-carrier network optimiser. Built for the full scheduled-carrier chain: crew pairing construction, seniority-based or preferential bidding assignment, integration with the network and its connecting banks. Maximum capability, long implementation, usually deployed alongside a dedicated operations research team. The field's active research gives a sense of scale: on monthly crew pairing instances of up to 50,000 flights, guiding the solver with machine learning cuts solution cost by 6.8 to 8.5% and global constraint cost by 70 to 78% (Yaakoubi, Soumis & Lacoste-Julien, 2020); on neighbouring vehicle and crew scheduling problems, machine-learned column selection saves up to 30% of compute time (Morabit, Desaulniers & Lodi, 2021). Only this category mobilises that level of engineering, and a mid-size operator has no need to carry it itself.
5. The vertical optimisation add-on. A tool specialised in generating rosters and optimising them, shipped with the domain rules already modelled, connecting by API to the operations system in place. It replaces nothing: it adds a computation layer on top of existing data.
How do they compare?
| Criterion | Suite module | Checker | Generic platform | Network optimiser | Vertical add-on |
|---|---|---|---|---|---|
| Generates a roster? | Varies | No | Yes, once modelled | Yes | Yes |
| Domain rules included | Partly | Yes (checking) | No, you write them | Yes | Yes, configurable |
| Prerequisite | The suite itself | An existing roster | A team able to model | A structured flight schedule | An operations system in place |
| Time to value | Zero if already equipped | Short | Long (development) | Long (project) | A few weeks (API integration) |
| Fit to in-house rules | Vendor-dependent | Good | Total | Good, via project | Configured per operator |
| Recompute after disruption | Varies | Not applicable | To be developed | Yes | Yes |
| Cost of ownership | Included or extra module | Low | Development plus maintenance | High | Subscription |
No column is "best". Each answers a different starting position, and it is the starting position, not the table, that should decide.
When is each category the right answer?
- The suite module wins when you have no structured operations system yet, or when the priority is consolidating scattered tools rather than optimising the roster (see our comparison of an optimisation add-on and an all-in-one suite). It is also the right answer when your scheduling problem is genuinely simple: few crew, few qualifications, few disruptions.
- The checker wins when building the roster by hand is not your problem but legal exposure is. It is cheap, it deploys fast, and it removes the most expensive class of error. It will never give you back construction time.
- The generic platform wins when your problem really is unusual and you have a team able to model it and maintain the model for years. It is a deliberate "build" decision, with real advantages: full control of the model, independence from any vendor's roadmap.
- The network optimiser wins for a large scheduled carrier: a repeating flight schedule, crew pairing to construct, seniority or bidding systems in place, and scale gains that justify a multi-year programme.
- The vertical add-on wins when you are satisfied with your operations system, your problem is optimisation depth and recomputation speed, and you want neither an IT programme nor an operations research team.
How do you place a vendor in a category?
Five questions do the job, and they belong before the demo rather than after it:
- "Does your tool generate a roster, or check the one I build?" This separates category 2 from the rest, and it is rarely asked that directly.
- "Are the regulatory rules shipped, or do we model them?" Separates category 3 from domain products. The follow-up matters as much: who maintains them when the regulation changes?
- "What happens to my current operations system?" Separates replacement from add-on, and determines the size of the project on its own.
- "How long does a re-generation take after a disruption, on a month already published?" Separates tools designed for ex ante construction from tools designed for daily operation. This is the number your team lives with.
- "Can I encode my own rules without going through you?" Separates a configurable product from a bespoke project, and determines how autonomous you are three years from now.
Where does SkAI Tech sit, and where does it not?
SkAI Tech belongs to the fifth category: a cloud add-on connected by API to the operations system already in place, in production with FL3XX, Cyberjet and Leon Software. It generates ON/OFF patterns against the applicable rules, optimises flight-to-crew assignment and tracks key crew indicators in a customisable dashboard. The regulatory base covers ORO.FTL, Part 91 and Part 135, extended by regional and in-house rules configured per operator. Data is hosted in Paris, under a GDPR-compliant framework.
What that delivers at equipped operators: an average roster generation time of 12 minutes and 20% fewer roster deviations. These results are observed across SkAI Tech deployments in 2025-2026, over a scope of more than 70 aircraft and 900 crew members, and vary with fleet size and operating model.
What the model does not do, better said before a demo than after one:
- it does not replace your operations management system, and it presupposes one: with no structured upstream data source, there is nothing to optimise;
- it is not a development platform: if your need is to model a novel optimisation problem yourself, a generic platform fits better;
- it does not cover the full chain of a very large scheduled carrier: network crew pairing, seniority systems and preferential bidding belong to the fourth category;
- it is neither an FRMS nor a certified fatigue model: it enforces the fatigue rules you define, it does not validate them on your behalf.
Choosing a tool for your operations department? See what SkAI Tech brings to operations leaders.
FAQ
Are "optimisers" that only check compliance common?
Common enough, and usually through vocabulary drift rather than bad faith. The distinction is sharp, though: checking answers "is this roster legal?", optimisation answers "which is the best legal roster against my objectives?". Both functions have value; you simply need to know which one you are buying.
Can categories be combined?
That is the usual real-world setup: an operations suite as the data foundation, an optimisation add-on on top, sometimes an independent checker for audit. The point to settle is the source of truth. There must be exactly one, or reconciliation costs more than optimisation returns.
How do you compare tools with different pricing models?
Reduce everything to a three-year total cost: licence or subscription, integration, configuration, rule maintenance, and above all internal cost in your own team's days. A generic platform that is cheap to buy can be the most expensive option once development and maintenance are counted.
Do you need a technical team to run an optimiser?
It depends on the category. A generic platform requires one; a network optimiser usually comes with an operations research team attached; a vertical add-on is designed to be run by the crew schedulers themselves. That is a selection criterion at least as decisive as algorithm quality.
Sources
- FAQ and Integrations page of this site: add-on positioning, production connections (FL3XX, Cyberjet, Leon Software), regulatory base, data hosting.
- SkAI Tech indicators (first-party data): average generation time and reduction in roster deviations observed across 2025-2026 deployments, over more than 70 aircraft and 900 crew members, varying with fleet size and operating model.
- Yaakoubi, Y., Soumis, F. & Lacoste-Julien, S. (2020), Machine learning in airline crew pairing to construct initial clusters for dynamic constraint aggregation, EURO Journal on Transportation and Logistics 9(4), DOI 10.1016/j.ejtl.2020.100020: 6.8 to 8.5% lower solution cost and 70 to 78% lower global constraint cost, on instances of up to 50,000 flights.
- Morabit, M., Desaulniers, G. & Lodi, A. (2021), Machine-Learning-Based Column Selection for Column Generation, Transportation Science 55(4), 815-831, DOI 10.1287/trsc.2021.1045: up to 30% less compute time.