Read how configuration actually works and how the engine decides before the four pages below. Every claim on them rests on those two mechanisms, not on anything specific to a new industry.
Beyond ATC
Deployed for air traffic control. Built as a rule engine underneath that.
Air traffic control is the only sector SkyRoster runs in today: the only one it is sold into, deployed in and proven in. Nothing on the four pages linked from this one changes that. What they argue is a narrower, checkable claim about how the product is built. The engine that solves an ATC roster takes its positions, its qualifications and its rules as configuration an administrator sets, not as code written for one customer. Point the same engine at a different rulebook and it can plan a different 24/7 operation. That is a statement about architecture, not a claim about a market SkyRoster has entered.
The mechanism, once
Five things the engine treats as data, not as air traffic control
Five mechanisms carry almost all of an ATC roster's logic. None of them mention aviation by name in how they are built. What they hold is the aviation content.verified
| Mechanism | What it holds today | What it is built to hold |
|---|---|---|
| Working position | An ATC console or task, with its own qualification requirement and timing limits. | Any single location-and-task combination that needs a specifically qualified person. |
| Qualification and requirement | A rating, a licence, a medical certificate, each valid only while its own preconditions are. | Any credential that expires on its own timetable and gates who can be assigned where. |
| Manpower requirement | Controllers needed per sector, per working position, down to the quarter-hour. | Any headcount-by-time-by-place demand table, at whatever resolution the work needs. |
| Approval chain | Leave, duty and swap sign-off, configured per unit as an ordered list of eligible approvers. | Any ordered sign-off sequence, including one that auto-approves because nobody configured it. |
| Hard rule vs soft rule | Minimum rest and licence currency as non-negotiable stops, fairness as a weighed preference. | Any constraint an organisation needs enforced absolutely, next to one it only wants weighed. |
What does not travel automatically: a rule shape the catalogue has never needed, a demand signal that has to come from a system SkyRoster has never connected to, or a workflow that is genuinely different in kind rather than in vocabulary. Each of the four pages below names those plainly for its own sector, rather than describing a capability as though it already existed.
Four sectors, read as rule sets
Airport ground operations
Turnaround-driven demand, multi-role ramp staff, safety-critical airside permits. The closest of the four to ATC's own shape.
modelled
Healthcare
Skill-mix coverage, acuity that moves within a shift, credentials that expire on their own schedule.
modelled
Fire and rescue
Apparatus-based crewing, 24-hour watches, specialist certifications stacked on top of the base role.
modelled
Railway
Route and traction knowledge scoped like a licence, duties built from a timetable instead of a fixed shift.
modelled
Bring your rulebook, not your industry.
If your operation runs a 24/7 roster against qualifications, a shift pattern and an approval chain nobody wants to keep in a spreadsheet, bring it to a working session. We will tell you plainly which part is a settings screen and which part is new development, before either of us spends a procurement cycle finding out.