The hub floor

Pitlane — the hub floor

The Control Tower watches the lane. Pitlane watches the floor. One screen per hub showing what is arriving, what is standing, what is leaving and what is free.

Request a Demo →All modules

A vehicle at a dock is the same event as a car in a pit box, or an aircraft on a stand. Work happens while it is stationary, and the only number that matters is how long before it leaves. The difference at a transport hub is that nobody is counting.

A pit crew is not faster because it tries harder. It is faster because it is standing there before the car arrives. That is a data problem, not a labour problem and not an infrastructure problem, and it is the problem Pitlane solves.

Pitlane

Four boards on one screen

Arriving

Every vehicle inbound to the hub, with its route, expected arrival, distance still to run, and how late it already is.

In the box

What is at the hub now, when it arrived, how long it has been standing, and the countdown to the departure it is booked on.

Rolling out

What is loading and leaving, and the lane each vehicle is running, so a threatened connection is visible before it breaks.

Idle

Vehicles standing free around the hub, each with an idle clock, and the ones you are yet to call. Assign a trip from the same screen.

What makes it usable on a hub floor

A radar, not a list

Inbound vehicles plotted in concentric circles by distance from the hub, coloured by delay. The question a hub actually asks is what is coming and when, and this answers it at a glance.

Every arrival carries its onward departure

A late arrival is never the problem on its own. The departure it holds up is. Pitlane links the two so the floor manages connections rather than vehicles.

A countdown, not a status field

Not "unloading, in progress". Instead: arrived 07:47, dwell 4h 3m, departs 13:47, depart in 1h 56m. A countdown is an instruction; a status is an excuse.

Dwell attention and delay buckets

Vehicles sorted by how much of their window they have already spent, and delays grouped into bands, so a supervisor looks at the four that need intervention rather than at all forty.

Built for a wall, not a login

A large display for the hub floor that refreshes itself, plus a desk view for the ops coordinator. The board does not depend on anyone remembering to open it.

One board per hub, all hubs in one Control Tower

Each hub gets its own screen, and the network view sits above them, so a head of operations can work hub by hub rather than guessing which one is the problem.

Pitlane board showing arrivals, vehicles at hub, departures and idle vehicles on one screen

The four boards on one screen. Each opens on its own tab, so the unloading team and the loading team keep their own display without competing for it.

Where we draw the line

The dwell clock and the countdown are what Pitlane keeps today. Timing each activity inside the stop — unload, load, clean, driver change — is on the roadmap and not in the product, and this page will not pretend otherwise.