The control room for your pallet high-bay: where every location belongs, and what it saves.
Enter rack geometry, I/O points and crane data. ASRS classifies every storage location into A/B/C, shows the zones in 3D and simulates the saving against your current putaway. No article data needed.
What you enter
- Aisles
- 14
- Columns × levels
- 100 × 18
- Column / level pitch
- 1.3 / 1.8 m
- SILO setup
- bidirectional
- Horizontal speed
- 3.5 m/s
- Vertical speed
- 1.0 m/s
- Acceleration x / y
- 0.5 / 0.8 m/s²
- Fork cycle
- 9 s
Assumed demand
- Locations A/B/C
- 20 / 30 / 50 %
- Movements A/B/C
- 60 / 30 / 10 %
- Fill level
- 75 %
- Storages per day
- 1,950
No movement history, no article master: drawings, crane datasheet and an estimate of your demand are enough.
Loading the demo warehouse…
- A pallet
- B pallet
- C pallet
- empty
Simulated stock at 75 % fill in a demo SILO with 14 aisles. Drag to turn.
Readings example calculation
10.8 % ± 0.2
less crane time per pallet
+12.1 % ± 0.3
crane capacity (theoretical)
12.8 % ± 0.6
less motion energy
± is the 95 % confidence interval of the simulation.
Today (first free location) → class-based; chaotic putaway for comparison. The rule shown in 3D in bold.
- Time per job
- 73.4 → 65.5 s
- Travel per job
- 127 → 100 m
- Energy per job
- 0.259 → 0.226 kWh
- Chaotic, per job
- 75.7 s
- Crane hours saved per year
- 2,572 h
- Cost saved per year
- ≈ 13,694 €
Per year from the mean saving per job; same relative interval.
Example calculation with the assumptions on the left. Your figures depend on your data.
How it works
Three inputs you already have, one simulation, and every figure with the assumptions it rests on. Point at a value to see where it sits in the sketch; the values are the demo warehouse's.
Describe one aisle
Rack geometry and the I/O points come from your layout drawing. All aisles are assumed identical, so one aisle is enough; reserved levels, e.g. for fire-sensitive goods, stay out of the classes.
Side view of one aisle
Top view (double-deep example)
Speed over time for one move (horizontal and vertical axis alike)
Give the crane its physics
Both axes move at the same time and the slower one decides. Short moves never reach full speed. Fork, positioning and handshake times make up the rest of a job. Defaults come from public datasheets; your own values replace them.
Simulate today against class-based
Tens of thousands of crane jobs per aisle, once with your current putaway (first free location: lowest level, then northernmost) and once with A/B/C zones. Trucks arrive in bursts, the crane starts each job where the last one ended, and repeated runs give a 95 % confidence interval.
Job stream of one crane (burst of 3 pallets)
What the figures do not claim
- Saved crane time becomes throughput only where the crane is the bottleneck; otherwise it shows up as idle time.
- Demand is an assumption, not your article data. Compare several assumptions before quoting a figure.
- In flow-through SILOs the time saving is usually small; the benefit there is mainly energy.
- Maintenance savings are estimates and secondary: inspections and fork cycles do not change.
Example report
Demo SILO: 14 aisles, 100 columns × 18 levels, 75 % fill, 1,950 storages per day, assumed demand 20/30/50 % of locations → 60/30/10 % of movements. All times per crane job, including empty travel and fixed times; ± is the 95 % confidence interval.
- Time per job
- 10.8 % ± 0.2
- 73.4 s → 65.5 s
- Crane capacity
- +12.1 % ± 0.3
- 49.0 → 55.0 jobs/h
- Motion energy
- 12.8 % ± 0.6
- 0.259 → 0.226 kWh/job
- Horizontal travel
- 127 → 100 m
- per job, ± 0.6 / 0.2 m
Per year, all 14 cranes
| Crane hours saved | 2,572 h |
| Working time per crane and day | 5.7 h → 5.1 h |
| Energy cost saved (0.172 €/kWh) | 6,651 € |
| Maintenance saved (estimate: 3 % of 350,000 € per crane, 60 % fixed) | 7,043 € |
| Total saved per year (energy + maintenance) | 13,694 € |
Yearly figures use the mean saving per job; they carry its relative interval (± 0.2 points on 10.8 %).
If today's putaway were chaotic (any free location, at random), the same warehouse would need 75.7 s per job, 3.1 % more than with first free location, because the crane uses the whole height of the rack. Class-based putaway would then save 13.5 % ± 0.2.
Calculated by the same engine as the app (model 0.5.0). Every report lists all inputs it used.
What you get
- The 3D view
- Every location in its class, the simulated stock with today's rule, the other rule for comparison and class-based, colour profiles that stay readable for colour-blind colleagues.
- The savings report
- Crane time, capacity, energy and maintenance per year, by fill level, with confidence intervals and the full list of assumptions. Prints as a PDF for the people who decide.
- The WMS export
- One row per location with your own location IDs and zone names, as CSV or one file per aisle, checked for unique IDs before download.
Location ID;WMS zone;Score [s] 01-001-02-11;HB-FAST;34.51 01-001-03-11;HB-FAST;34.12 01-001-04-11;HB-FAST;34.57 01-001-05-11;HB-FAST;35.02 01-001-06-11;HB-FAST;35.85 01-001-07-11;HB-FAST;37.20 …
Request a pilot analysis
One of your warehouses, analysed with its real geometry and crane data, and walked through together.
- 1You send what you have. Layout drawing or rack dimensions, the crane datasheet, a rough idea of storages per day.
- 2We set up the warehouse. Every assumption we make is marked as one, for you to check.
- 3We walk through the results. 3D view, report and export, and what they mean for your site.