Strategy · published
A repeatable evidence workflow from the student projects — which metrics to calculate, with which tool or method, and the decision it led to.
| Summary | A simulation of truck arrivals tests how many docks keep the same throughput, and swept paths of real trucks fix the size of the bays. |
| Tool or method | Discrete-event simulation (custom; software not named) and AutoTURN swept-path analysis |
| Status | published |
The question it answers
How few docks and how little paved yard can handle the same number of trucks?
How it works
- Simulate truck arrivals and dock handling many times for each docking layout and number of docks.
- Compare the distribution of trucks handled, to find the smallest number of docks that keeps throughput.
- Generate swept paths of standard trucks to check and size the bays and turning areas.
- Turn the paved area that is no longer needed into greenery or water retention.
In the student projects
- Hynek Hrabík — discrete-event simulation (custom; software not named) and AutoTURN. Number of docks: classic layout 60 docks vs flow-through 40 docks at equal throughput; Truck throughput: flow-through 40 docks centred near 250 trucks handled, overlapping the 60-dock case (250 trucks/hour arrival rate, 2,000 runs per configuration). Decision: “The simulation showed flow-through docking keeps full throughput with a third fewer docks, and the swept-path analysis fixed the bay size. Together they justified replacing conventional apron docking at the PPL hub with flow-through corridors: 20 fewer docks and about 30% less paved surface (18,000 to 13,000 m²), with the freed area turned into greenery and ponds.”
Values and decisions as reported by the student; see each case study for the page in the portfolio.
Where it falls short
- Only one project uses this workflow, and the simulation software is not named.
- Dock turnaround time is shown only as a bar chart, without a value.
Where are the ambitions, metrics and tools?
They appear automatically below under Connections, and in Obsidian under the
auto_properties.
Connections
- Case studies: Hynek Hrabík
- Metrics it calculates: Number of docks, Truck throughput, Yard area per dock
- Tools: AutoTURN
- Ambitions (through its projects): Compact footprint, Efficient truck flow and compact yards, Habitat and ecological connectivity, Rainwater kept on site
Something wrong or missing? Suggest a correction