CREW360 OPS

Where the day gets flown.

Pairings Builder with live legality preview. Augmented Gantt. ADS-B correlation. Works with Crew360 Engine — or yours.

PAIRINGS BUILDER

Live legality. Before you publish.

Drag-drop flight canvas with auto-chronology. Every edit triggers immediate rule evaluation — FDP, sector limits, rest requirements, hours-in-period. Results render as 3-D puck encoding: Severity (fill): legal green / warning amber / illegal red Trajectory (ring): stable solid / improving inward pulse / degrading outward pulse Recoverability (edge): healthy solid / constrained dashed / unrecoverable dotted Server-side legality re-check fires at publish to prevent evaluation races. Controllers see what's legal before they commit — not after.

LEGAL · STABLE

WARN · IMPROVING

ILLEGAL · CONSTR.

Real-time evaluation3-D puck encodingServer-side publish checkFDP · Sector · Rest · Hours

HOW OPS READS STATE

Your controllers don't have time to read rule traces. They shouldn't have to.

Every puck on the canvas encodes three dimensions at a glance. Fill is severity. Ring is trajectory. Border is recoverability. Together they tell a controller what to do without parsing a single line of regulatory text.

SEVERITY · FILL

Where the pairing is right now.

Green for legal. Amber for warning band. Red for illegal. The same three colours the rule engine returns from the evaluator — no interpretation layer between the engine and the canvas.

LegalWarningIllegal

TRAJECTORY · RING

Where it's heading on the next edit.

A solid ring means stable — nothing's changing. An inward pulse means improving — the edit is pulling it back to legal. An outward pulse means degrading — every change makes it worse.

StableInward pulseOutward pulse

Stable

Inward

Outward

RECOVERABILITY · EDGE

How much room you have to fix it.

Solid border means healthy options — swap candidates everywhere. Dashed means constrained — fewer crew available. Dotted means no recovery — escalate or cancel.

SolidDashedDotted

Healthy

Constrained

Unrecoverable

Three states a controller scans in two seconds.

SCENARIO 1

Sector count near cap, controller easing the duty.

Amber fill · inward pulse · solid edge. Warning band, but the edit is pulling it back to legal. Recovery options are healthy. Keep going.

SCENARIO 2

Pairing violates rest after a late MVT arrival.

Red fill · solid ring · dashed edge. Illegal now, not getting worse, but recovery requires a deadhead or reserve. Find the candidate before the deadline.

SCENARIO 3

Illegal FDP, no eligible crew, no deadhead option.

Red fill · outward pulse · dotted edge. Cancel-or-delay territory. Escalate. The system isn't going to find an answer.

ENCODING EXAMPLES

Fill · Ring · Edge — read at a glance.

Every puck encodes three independent dimensions. Fill is severity, the ring animation is trajectory, the border is recoverability. Together they tell a controller what to do without reading a rule trace.

Scenario

Fill

Ring

Edge

What it tells you

Standard pairing within all limits

Green

Solid

Legal · Stable · Healthy — publish freely.

FDP within limits, rest buffer shrinking each rotation

Green

Outward pulse

Solid

Legal now, trending toward warning. Watch the next edit.

Legal pairing built on a single eligible reserve

Green

Solid

Dashed

Legal but fragile — one drop and recovery is non-trivial.

FDP at 95% of max with extension applied

Amber

Solid

In warning band, holding. Reviewable, not blocking.

Sector count near cap, controller easing the duty

Amber

Inward pulse

Solid

Warning, but the edit is pulling it back to legal.

Hours-in-28-days creeping up across the bid period

Amber

Outward pulse

Dashed

Warning, worsening, and few swap candidates left.

Pairing violates rest after late MVT arrival

Red

Solid

Dashed

Illegal. Recovery requires a deadhead or reserve.

Illegal, but controller is mid-fix and trending back

Red

Inward pulse

Solid

Illegal now, fix in progress, recovery path open.

Illegal FDP, no eligible crew, no deadhead option

Red

Outward pulse

Dotted

Cancel-or-delay territory. Escalate.

AUGMENTED GANTT

The duty grid, with rule outcomes overlaid.

Crew duty grid with legality outcomes rendered inline. Live ADS-B map shows actual aircraft positions — not just where they're rostered. MVT correlation auto-updates flight states as aircraft movement messages arrive.

Rule outcomes overlaidLive ADS-BMVT correlation

OPEN TIME

Unassigned pairings. Available crew. Side by side.

Crew availability is driven by rule outcomes from the engine — not a static availability flag. Match candidates show 'would this assignment be legal' before commit. Deadhead options surface automatically.

Engine-driven availabilityPre-commit legality checkDeadhead surfacing

DISRUPTION

IROPS. Before ops staff have to find it.

SSIM, SSM, ASM and MVT messages feed the disruption engine. Affected crew and flights surface automatically. Re-pairing candidates are ranked by cost: deadhead, overnight, overtime, disruption risk. Dispatcher feedback ranks suggestions — the model improves for your airline over time.

SSIM · SSM · ASM · MVT ingestCost-ranked candidatesDispatcher feedback loop

ENGINE FLEXIBILITY

Works with our Engine. Or yours.

Crew360 Ops evaluates via our Engine by default. For airlines with existing Drools or IBM ODM investment: point Ops at your cluster. We provide the round-trip validation framework so you can prove exported rules behave identically across engines. Journey 2 starts here.

Drools compatibleIBM ODM compatibleDMN round-trip validation

Request a Demo

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