ChevronLift · Internal Scheduling Cockpit

Automated crude & product scheduling that schedulers can live in

This is the live ChevronLift prototype: a single place for crude and refined product schedulers to see tomorrow's movements, understand conflicts, and explore options without rebuilding spreadsheets.

Crude & product logisticsScheduling & demurrage riskAI-assisted planning (not full autopilot)

Want the full product story?

This page focuses on the app experience. If you want the full breakdown of problem framing, user personas, flows, and impact, there's a separate case study.

Read the ChevronLift case study

Scheduling Cockpit (Demo)

See tomorrow's barrel flows, not someone's spreadsheet

Flip between systems and scenarios to see how ChevronLift represents crude & product movements, flags conflicts, and surfaces suggested actions schedulers can actually use.

How to play with this demo

  • 1. Pick a system (Gulf crude vs. Midcon products).
  • 2. Switch between Base, Late Vessel, and Tank Stress.
  • 3. Watch the plan and conflicts update together.

Feasible next-day schedule with no major disruptions applied.

Movements in View

3

Pipelines, tank transfers, and vessels.

Total Volume

680,000 bbl

Across the filtered schedule.

Conflicts Flagged

0

Issues requiring scheduler judgment.

Movement Plan (Demo Data)
IDAssetProductVolumeWindowLocationStatus
GC-01Enbridge MainlinePipelineWCS50,000 bbl2025-03-02 06:00→ 2025-03-02 18:00Cushing → Gulf CoastPlanned
GC-02Chevron Tank 401 → 407Tank TransferMaya30,000 bbl2025-03-02 08:00→ 2025-03-02 11:00Gulf Coast Terminal APlanned
GC-03MT Gulf VoyagerVesselMixed Crude Blend600,000 bbl2025-03-02 13:00→ 2025-03-03 01:00Berth 3Planned

Conflicts & Risk (Demo)

Operational issues surfaced for this system and scenario — things schedulers care about before traders feel it in P&L.

No conflicts detected.

For this demo scenario, ChevronLift doesn't see any projected tank, dock, or compatibility issues.

What ChevronLift is designed to handle in a real environment

The prototype only scratches the surface of what an internal Chevron deployment would do, but it's built around the same core ideas: unify movements, surface risk early, and make recomputation cheap instead of painful.

Unified movement layer

Pipelines, tanks, docks, and vessels represented in one interface so schedulers aren’t the human integration bus between systems.

Conflicts with explanations

Tank overfills, berth conflicts, and batch incompatibility surfaced alongside why they matter and what knobs schedulers can turn.

Scenario-friendly by design

Late vessels, stressed tanks, and trader changes don’t require rebuilding the schedule — just rerunning constraints against the same graph.