Sophisticated rule authoring. Structured storage. Full lifecycle management. Seven jurisdictions. Export to any engine.
Crew360 Hub gives every rule a structured form — not a paragraph in a Word doc. Rules are authored with typed parameters, bound to a shared ontology of 53 crew operations terms: FDP, Layover Rest, Augmented Crew, Day Off, Rest Facility, and more. Inline rule parsing detects ambiguous interpretations and flags them for human review — before they reach operations. Where similar published rules exist, Hub suggests defaults.
Every rule is a database record, not a file. Parameters are bound to ontology terms — not hardcoded strings. Provenance is tracked on every change: who touched it, when, and what changed. The rules engine receives clean, typed inputs. Not parsed prose.
Every rule moves through a structured lifecycle before it reaches operations. Reviewer tasks are assigned with checklists and resolution tracking. Version history is kept per rule — with diff visualisation between versions so reviewers know exactly what changed and why.
Test cases attach directly to rules — input data plus expected outcome. Run all tests on demand. See pass/fail per rule, per jurisdiction. When a regulator changes a requirement, Hub tells you exactly which test cases now fail, before a single pairing is re-evaluated.
NZCAA, FAA, EASA, CASA, DGCA-India, TCCA, CAAC — pre-loaded and structured. Layered override model: regulator baseline → operator scheme → airline-specific variant. Jurisdiction-scoped rule visibility means airline-private overrides never leak to other tenants.
Rules export on demand to DRL (for Drools), DMN (vendor-neutral), or custom JSON for your own evaluator. Your rules are your rules — portable, versioned, and never locked to our runtime.
Not a webinar. Not a recorded walkthrough. A conversation with the people who built it.