LCB ONE · Capacity & congestion simulation

Where does smoothing stop working?

Push the sliders. Scheduling fixes clustering — it cannot invent lanes that don't exist. This shows exactly where that line is.

Inputsillustrative defaults — tune to your real numbers
1.0× = today's volume, 3.0× = triple
trucks the approach road can hold before it visibly blocks traffic
—

Daily capacity check

This is the same number in all three scenarios below — no schedule changes it.

What the queue looks like, all day

Today — flat hourly

everyone books for :00, so demand spikes each hour
Demand vs. capacity
Queue over 24h
Peak queue—
Est. peak wait—
Drains by midnight?—

LCB ONE — dynamic 15-min slots

same trucks, spread evenly within each hour
Demand vs. capacity
Queue over 24h
Peak queue—
Est. peak wait—
Drains by midnight?—

LCB ONE + buffer yard

overflow beyond the road shoulder holds off-road instead
Demand vs. capacity
Queue over 24h — road (solid) + buffer (light)
Peak road queue—
Peak buffer use—
Buffer overflowed?—
Methodology & limits

A deterministic fluid-queue model at 15-minute resolution: trucks/day follow a modeled daily traffic shape (low overnight, two daytime peaks); within each hour they either cluster at :00 ("Today") or spread evenly ("LCB ONE"). Capacity = lanes × throughput/lane, held constant through the day. This is an illustrative planning model, built to make the concept and the breaking point adjustable in front of stakeholders — it is not a calibrated traffic study. Before committing budget to lane-widening or gate counts, validate against a real microsimulation (e.g. SUMO or VISSIM) using PAT's actual road geometry, measured gate service times, and observed arrival data.