CREW360 ENGINE

Stateless. Deterministic. Yours — or not. Your choice.

The evaluation oracle under Crew360 Ops. Available as a standalone service, or replaceable with your own Drools, IBM ODM, or DMN-compatible runtime.

Request a Demo

WHAT THE ENGINE DOES

Inputs in. Outcome plus reasoning trace out.

Input: a rule + a context (flight, crew, history). Output: an outcome + a reasoning trace — which rule fired, with what input values, producing what result. Every evaluation is fully traceable. Stateless: same inputs always produce same outputs. No customer-state leak between requests.

Stateless evaluationReasoning traceNo state leak

WHAT THE ENGINE RETURNS

Every evaluation returns a verdict, a trajectory hint, and a recovery class.

Crew360 Engine doesn't just say "this pairing fails rule FDP-7." It returns three structured fields that any UI — Crew360 Ops, your own controller front-end, or a downstream system — can render as the canonical puck. Same encoding, anywhere it runs.

SAMPLE ENGINE RESPONSE

{
  "pairing_id": "AKL-WLG-AKL-2026-06-12",
  "verdict": {
    "severity":       "warning",
    "trajectory":     "improving",
    "recoverability": "constrained"
  },
  "rule_trace": [
    { "rule_id": "FDP-7", "status": "warn", "metric": "13h 40m / 14h limit" },
    { "rule_id": "REST-2", "status": "pass", "metric": "10h 12m" }
  ],
  "explanation": "FDP within 95% of cap; controller edit is reducing block; swap candidates limited to 2 reserves"
}

The three fields under verdict map directly to the puck encoding rendered in Crew360 Ops. severity is the fill colour, trajectory drives the ring animation, recoverability drives the border style. Build your own UI on top, or use ours.

Why structured verdicts matter.

PORTABILITY

Same shape, any front-end.

The verdict envelope is a contract. Your existing controller UI can consume it without parsing rule text. Build new front-ends without re-implementing semantics.

TESTABILITY

Verdicts are unit-testable.

You assert on three enum fields, not on rendered strings. The same input always produces the same verdict. Stateless. Deterministic.

REPLACEABILITY

Swap the engine if you need to.

Crew360 Ops + Portal consume the verdict envelope. If you'd rather run your own Drools or IBM ODM behind it, you can — as long as your engine returns the same three fields.

DIMENSION-AWARE EVALUATION

Not all violations are equal.

Rules carry five dimensions: · Severity — info / warning / violation · Behavior — overrideable / inviolate / advisory · Context — rolling window / calendar period · Override level — crew / dispatcher / director · Document ref — the regulation being evaluated Dimensions inform outcomes. Not all violations are equal. The engine knows the difference between 'warn the dispatcher' and 'block the publish.'

5 rule dimensionsSeverity-awareOverride levels

SCALE

Built for large airline rule sets.

Postgres-backed evaluation path for fast, consistent results. Horizontally scalable. Tested against large airline rule sets.

BRING YOUR OWN ENGINE

Hub exports. Your runtime evaluates.

For airlines with existing Drools or IBM ODM investment: Hub exports to your format, your engine evaluates, Ops + Portal render the outcome. We provide round-trip validation so you can prove the exported rule behaves identically across engines.

DRL exportDMN exportRound-trip validation

Request a Demo

Not a webinar. Not a recorded walkthrough. A conversation with the people who built it.