Study · synthetic paired comparison
How warehouse backlog forms — and how aisle congestion affects picking
One paired comparison from the existing CoupledSimulation model: identical synthetic work, identical pickers, one difference. In the second run the front of sorter row 39 is blocked for the whole configured hour. We stop both runs at 1800 seconds and read the counters.
Scope. Synthetic, deterministic, one paired run. Not Monte Carlo, not client data, not a return-on-investment claim. The half-hour observation window is not a whole shift or a day.
The setup
60 original jobs were released, containing 4,025 location lines, worked by 30 pickers on a one-hour configured shift. The scenario is clustered-strict, with zero interrupts. The only change between runs is blockedSeconds: 0 in the open run, 3600 in the blocked run, applied to the front of sorter row 39.
A location line is one source/SKU confirmation: a picker confirms quantity at one location for one SKU. It is not a job and not a piece.
Key inputs
| Parameter | Value |
|---|---|
| jobs | 60 |
| interruptCount | 0 |
| wmsHours | 1 |
| blockedZone | sorter |
| blockedRow | 39 |
| blockedSection | front |
Model defaults
The comparison changes only aisle blockage. Every other resolved default is shared, including requested vehicle speed, safety clearance, STOP dwell, pick timing, mixed packaging and finite handover resources.
Inspect the complete resolved baseline configuration
| Parameter | Value |
|---|---|
| wmsHours | 1 |
| jobs | 60 |
| controlStudy | false |
| controllerMode | legacy |
| twinCongestionSeconds | 90 |
| twinFairnessSeconds | 900 |
| twinSlaSeconds | 7,200 |
| allocationStudy | false |
| allocationPolicy | restricted |
| allocationScope | warehouse |
| priorityPickerIds | ["PK01","PK02","PK03","PK04","PK05","PK06","PK07","PK21","PK22","PK23"] |
| allocationWaveCount | 8 |
| allocationJobsPerWave | 90 |
| allocationGoodPerWave | 30 |
| allocationCardsPerWave | 30 |
| allocationWaveGapSeconds | 3,600 |
| binCaseProfile | standard |
| binCaseConsolidate | false |
| binCaseCartons | 25 |
| binOpenSeconds | 3 |
| binCutSeconds | 12 |
| interruptCount | 0 |
| policy | manual |
| voiceVerify | 3 |
| scannerVerify | 3 |
| voiceRetryRate | 0 |
| scannerRetryRate | 0 |
| retryDelay | 5 |
| quantityConfirm | 2 |
| pickDwell | 8 |
| pickPerUnit | 1 |
| outerPackSize | 12 |
| catalogMode | mixed |
| swapChannels | false |
| clearance | 3.5 |
| stopDwell | 1.5 |
| requestedSpeed | 6 |
| burstSorter | 12 |
| burstClassic | 8 |
| reachSorter | 6 |
| reachClassic | 4 |
| reachJobs | 3 |
| liftSeconds | 40 |
| jobChangeSeconds | 30 |
| recoveryDelaySeconds | 120 |
| recoveryHandoverSeconds | 60 |
| blockedZone | sorter |
| blockedRow | 39 |
| blockedSection | front |
| blockedSeconds | 0 |
| deliveryRows | [1,2,3,4,5,6,7,8] |
| deliveryRowsProvisional | true |
| laneCapacity | 4 |
| sorterPlaceSeconds | 30 |
| sorterClearSeconds | 300 |
| sorterCarriersPerTask | 1 |
| binDeliveryToSorter | true |
| binHandoverCapacity | 4 |
| outerMaxLocations | 25 |
| binMaxLocations | 100 |
| classicMaxLocations | 100 |
| classicMaxPieces | 200 |
| wrapperBufferCapacity | 4 |
| wrapperMachines | 1 |
| wrapperHandoverSeconds | 30 |
| wrapperFeedSeconds | 15 |
| wrapSeconds | 90 |
| wrapperTransferSeconds | 20 |
| loadingBufferCapacity | 4 |
| loadingBays | 1 |
| truckLoadingSeconds | 45 |
| truckAvailableAt | 0 |
| truckCapacityCarriers | 20 |
| truckChangeSeconds | 300 |
What we observed at 1800 seconds
| Metric | Open aisle | Blocked aisle |
|---|---|---|
| blockedSeconds | 0 | 3,600 |
| releasedJobs | 60 | 60 |
| releasedLines | 4,025 | 4,025 |
| confirmedLines | 794 | 654 |
| backlogLines | 3,231 | 3,371 |
| confirmedBaseUnits | 9,890 | 8,977 |
| pickerWaitingSeconds | 32,840.36 | 35,412.8 |
| completedOriginalJobs | 7 | 7 |
| loadedBaseUnits | 0 | 0 |
| teamBaseUnitUPH | 19,780 | 17,954 |
In the open run, 794 lines were confirmed and 3,231 remained in backlog, with 9,890 confirmed base units and 32,840.36 summed picker waiting seconds. With the aisle blocked: 654 confirmed, 3,371 backlog, 8,977 base units and 35,412.8 waiting seconds.
Both runs completed 7 original jobs and loaded 0 base units. Those are deliberately reported: half an hour in, almost nothing is finished or shipped in either case, so the confirmed-unit difference must not be read as shipped output.
Definitions and formulas
- Backlog lines = released lines − confirmed lines. Open: 4,025 − 794 = 3,231. Blocked: 4,025 − 654 = 3,371.
- Base-unit UPH per team = confirmed base units ÷ 0.5 h. Open: 9,890 ÷ 0.5 = 19,780. Blocked: 8,977 ÷ 0.5 = 17,954. This is a whole-team rate over the elapsed half-hour. It is not per picker, not jobs per hour and not a daily projection.
- Summed waiting is person-seconds added across all 30 pickers, not wall-clock seconds.
- Base units versus packages. The existing catalog uses a mixed pack mapping, so package counts are not interchangeable with pieces. Source quantities are preserved as recorded.
A separate, high-level day model
The Warehouse Digital Twin also contains a coarse demand-and-capacity queue for a day. Its identity is: opening backlog 14,200 + demand 450,000 − throughput 300,000 = ending backlog 164,200, a growth of 150,000. Capacity coverage is 66.7% while utilization is 100%: the team is fully busy and still cannot keep up.
That model counts a different thing on a different time scale. Do not equate its backlog with the line backlog in the detailed study above.
How the model works
The workload is generated deterministically from synthetic inputs; there are no independent stochastic repetitions. The discrete-event solver decides when each picker moves, waits and confirms. The 3D view in the 3D Picking Lab visualizes solver state. It does not determine throughput.
Reproduce it
- Open the detailed lab at 3D Picking Lab.
- Download the evidence JSON. Each
resolvedentry contains the completeconfiguration;scenarioDefinitionidentifies the dispatch and rules. This evidence file is not an importable lab preset. - Using the supplied v21 model module, construct
new CoupledSimulation(configuration, scenarioDefinition), runadvanceTo(1800), and readsummary(). Repeat with the second resolved configuration. The repository verification command isnode artifacts/kasynets-ai-solutions/scripts/verify-picking-study.mjs.
Limitations
- Synthetic inputs only; no live WMS connection.
- No client results, no ROI estimate and no certification.
- Any operational decision requires pilot validation on real data.
- Observed over an elapsed half-hour, not a whole shift or day.
Related: the warehouse simulation film and the warehouse automation overview.