Your OCC, your crew app, your rule authoring — from one architecture, designed for now and what's next.
Crew360 is three products that work independently or together. Start wherever you are.
Your crew rules live in Word docs, SharePoint and someone's head. Crew360 Hub gives them a proper home — structured, versioned, tested, governed. Your existing systems consume the output.
Your Drools or IBM ODM setup works. Your controller UI and crew app don't. Crew360 Ops + Portal sit over your existing engine. Keep what works. Replace what doesn't.
One vendor. One architecture. One contract. Hub for authoring, Engine for evaluation, Ops for daily flying, Portal for crew, Integration Hub for SSIM/SSM/ASM/MVT data flow.
Hub exports to DRL, DMN, or custom JSON. Ops evaluates via our Engine — or yours.
NZCAA, FAA, EASA, CASA, DGCA, TCCA, CAAC — plus airline-specific overrides. Seven jurisdictions pre-loaded. Layered override model: regulator → operator scheme → airline-specific.
Rules are typed records, not paragraphs. Parameters bound to an ontology of 53 crew operations terms — FDP, Layover Rest, Augmented Crew, Day Off and more. No free text. No ambiguity by accident.
Author in Hub. Export to DRL for Drools, DMN for IBM ODM, or custom JSON for your own evaluator. Your rules are yours — portable, on demand.
React, Postgres, Cloudflare. No installation, no on-prem footprint, no 18-month implementation. CI/CD from day one.
Not a webinar. Not a recorded walkthrough. A conversation with the people who built it.