GEN2 / INBOUND
INTERACTIVE DEMO · ENTER YOUR OWN VALUES
Truck arrival → receiving → putaway

Will inbound finish before cut-off?

Enter lines, throughput, staffing, and planned and actual arrival times for each truck. Compare queues, finish times, and the risk of missing your cut-off.

Best of the staffing options tested
Calculating…
Chance of finishing on time—
Median finish—
Later finish, P95—
Expected total cost—

Where does the queue build?

One illustrative shift with the selected staffing. The chart shows lines waiting at receiving and putaway. The probabilities above use 1 200 simulated shifts.

Total lines—
Average peak receiving queue—
Average peak putaway queue—
Receiving queuePutaway queueCut-off time

Compare staffing options

We compare your staffing with one extra person in either step, one extra in both steps, or one fewer in both. Each option faces the same simulated disruptions. Expected cost = paid hours × hourly cost + late probability × late-day impact.

Receiving / putawayLate riskMedian / P95LabourExpected totalRisk limit

What the model assumes

Your arrival times and line counts are used directly. Productivity varies between shifts, absence is assumed at 2.5% per person, and lines move from receiving to putaway at the next 15-minute step.

This is a simplified browser model. It does not cover dock capacity, item mix, WMS outages, coordinated breaks, or your actual outcomes. Use it as an illustration, not an operational staffing instruction.

What a Gen2 pilot adds

We would adapt the neutral Python engine to one customer workflow, test it against historical shifts, and document each run so the result can be reviewed.

Discuss a pilot →

Calculations and evidence

Your values run locally in this browser demo, not in the Gen2 Python engine. The separate reference report below was produced with Gen2 v using synthetic presets. It does not validate results for your own entries.

Show reference run identity