Line being picked——
Orders queued: —Queue expected empty: —
Next drawer—
Industrial example
A vertical lift module, line by line.
Two towers, one operator, orders from the ERP: while you pick at one bay, the other tower prepares the next drawer. Lines per hour, waits, stock and reorders, energy and the forecast for the day. Simulated data; one second is 10 seconds. Try sending an urgent order.
With AI predictive analytics estimates the day's workload, forecasts reorders and suggests where to place the most requested items.
Loading the digital twin…
Tower A—
Tower B—
Bay A—
Bay B—
Cart—
Warehouse 1 · — · simulated data · —
Lines per hour—
Today —Lines per drawer —
Orders done——
Operator waiting——
Drawer cycles——
Energy per line——
Multi-order cart · four orders at once, one light per bin
Queued from the ERP
Tower A
——
Drawers queued
- Cycles today
- —
- Busy
- —
Tower B
——
Drawers queued
- Cycles today
- —
- Busy
- —
Stock · the items closest to minimum
When an item drops below minimum stock, Studio sends a reorder proposal to the ERP; the put-away comes back to the bay like any other line.
Most visited drawers · today
The most requested items sit in drawers close to the bay: the lift travels less.
Operator · the day
—
Energy
Now—
Today—
Recovered—
On the way down the lifts feed energy back to the grid: “Recovered” is what a brake would waste as heat.
Events
Devices in Link
- Tower controls (2) · OPC UA
- Light curtains and bays · via the tower control
- Energy meters (2) · Modbus TCP
- Cart displays · Modbus TCP
The ERP talks to the Studio REST API: orders in, confirmed lines and reorders out.
From the ERP
- Orders received today
- —
- Lines confirmed
- —
- Reorders proposed
- —
The tower control runs the picking; the Suite joins states, drawers and lines with the ERP orders, stores them and works out lines per hour, waits and stock.
Anomalies · Datathesys Cloud
Tower B: extracting drawer B07 has gone from 6 to 9 seconds over the last week, with the same load. The drawer weighs 241 kg out of 250 allowed: worth moving some items or checking the guides.
Studio sends the data to Datathesys Cloud, which compares drawers and days and flags unusual behaviour.
Expected plan
Orders already in the ERP and expected for the rest of the day, shifts and breaks, reorders and put-aways.
Forecast
What the Industrial vertical does in the warehouse
Automated warehouses connected: vertical lift modules, carousels and stacker cranes over OPC UA or Modbus TCP, alongside the production machines.
Orders and lines: from the ERP through the Studio REST API, confirmations and reports going back.
Lines per hour and waits: how much the operator works, how long the drawer waits, how long the order waits.
Stock and reorders: minimum stock per item, reorder proposal to the ERP, tracked put-aways.
Condition-based maintenance: cycles per tower, extraction times per drawer, loads close to the limit.
Energy: kWh per tower and per line, with the energy recovered on the way down.
Got a warehouse to connect? Let's talk.