UnitedOps · Network Irregular Operations Optimizer

A cockpit for United's IROPS team to see the whole network at once

This prototype treats the hub as the unit of work: flights, disruptions, and mitigation options for ORD and IAH in a single view, instead of scattered across tools and spreadsheets.

Airline operations & schedulingIROPS & network controlDecision-support, not full automation

About this prototype

This page focuses on the product surface United controllers would live in during a disruption. A separate case study can go deeper on problem framing, user journeys, and impact.

If you add a /case-study route later, you can link to it from here. Until then, this page stands alone as the primary demo.

IROPS Cockpit (Demo)

Recompute the network plan in one screen, not ten spreadsheets

Switch hubs and scenarios to see how UnitedOps represents flights, disruptions, and mitigation options the way a network controller actually thinks — by bank and risk, not just by flight number.

How to explore this demo

1. Choose a hub (ORD vs. IAH).
2. Toggle Base, Weather, and Crew Misconnect scenarios.
3. Watch flights, disruptions, and recommendations update together.

Planned schedule with no major weather or crew disruptions.

Flights in View

Hub & scenario specific snapshot.

Delayed / Cancelled

0 delayed, 0 cancelled.

Reassigned Tails

Aircraft swaps in this scenario.

Disruptions & Options

0 / 0

Issues vs. suggested mitigations.

Flights View (Demo Data)

Flight	Route	Schedule	New Times	Tail / Crew	Pax Risk	Status
UA 1123	DEN → ORD	08:10 / 11:35	Unchanged	N782UACrew D1234	Low	On Time
UA 882	ORD → LHR	18:05 / 07:30+1	Unchanged	N27958Crew I2345	Low	On Time
UA 2015	EWR → ORD	13:10 / 15:05	Unchanged	N452UACrew D2211	Low	On Time

Disruptions & Mitigations

What's breaking the plan, and what levers UnitedOps suggests you pull: cancel, swap, re-time, or protect key banks.

No major issues flagged.

For this demo scenario, UnitedOps doesn't see impactful disruptions or recommended changes at the hub level.

What UnitedOps is designed to do in a real environment

The demo is intentionally thin, but it mirrors the ideas I'd push for in production: represent the network as a system, make disruptions visible, and make recomputation cheap instead of tribal.

Hub-first mental model

Controllers think in terms of hubs, banks, and flows. UnitedOps aggregates flights and disruptions by hub so the plan is legible at a glance.

Disruptions with levers attached

Weather, crew, and maintenance issues are tied directly to suggested actions — cancel, swap, re-time — so the next decision is obvious.

Scenario-friendly by default

Base day, weather events, and crew misconnects live as adjacent scenarios, not separate spreadsheets, so you can compare options quickly.