Estate weekday morning
Play a weekday morning on a four-block estate and see where people wait for the lifts.
No sign-in needed: open it in Studio, inspect the saved results and edit in 2D and 3D. Sign in to connect your own AI; project files remain free. Check Account for execution access. Opening asks before replacing your current space.
How do delivery boxes change the couriers’ time and lift use at the morning peak, and how long do residents wait for a lift?
- Who uses it
- Housing managers, estate developers and management associations
- How it can create value
- Compare delivery boxes with delivering to every door, and see the morning lift waits floor by floor, before deciding on delivery boxes, a second lift or delivery rules. Shorter waits and rounds alone do not establish resident satisfaction or savings; weigh them against installation costs and real parcel volumes.
- Bring your site data
- Departures by floor and time of day, the lift’s speed, door times and control, parcel volumes by block and hour, the share that goes into boxes and how often nobody is home. The lift’s real control and door times need checking before trusting the waits.
A model you can inspect.
A weekday morning from 7:30 to 8:30 on a four-block estate. Residents leave their flats (poisson with a time-of-day profile: 6 per floor per hour from 7:30 to 8:15, twice that from 7:40 to 8:00), keeping off the lawns unless the way round is more than three times as long: from levels 1 and 2 on foot (down the stairs from level 2), from level 3 up by their block’s lift, one car for 9 people (1 m/s; each stop 5 s of doors and 3 s open). They call the car at their floor and wait in its hall; the car takes the call it can reach soonest in its direction, picks up those waiting to go down on the way while it has room, and waits where it stopped when idle. A quarter put a bag in the nearest refuse cage; then 60 % walk to the east gate for the station, 25 % cycle from their block’s shelter and 15 % drive off from the car park. At 8:00 two couriers start from their vans (north: blocks A and B, south: C and D) with 4 parcels a block, each into the lobby’s delivery boxes or, by weight, by lift to a random door and back down, sharing the cars with the residents. The car rules are fixed and simple (no optimised group control); a trolley counts as one person; nobody is absent; no crowding, redelivery, satisfaction or costs.
Change one thing
With the same residents, put every parcel in the delivery boxes (boxes 100, doors 0) or take every parcel to the door (0 and 100); raise the residents leaving per floor from 6 to 12; or give each block two lift cars.
Read the consequence
Lines at each floor’s lift hall, where each car is and how many are in it, the waits for a car floor by floor, the couriers’ round times and their lift rides. The cars follow simple fixed rules (no optimised group control); absence, redelivery, satisfaction and costs are not modelled.
View the starting inputs
- Residents leaving per floor per hour (doubled 7:40–8:00)
- 6
- Parcels into delivery boxes (%; the rest to the door)
- 50
- Parcels per block
- 4
- Lift cars per block
- 1
- People per lift car
- 9
Agent counts, routes and resource definitions are also saved in the project JSON.
A reproducible starting result.
One run, seed 15. Observation window 60 minutes.
| Scenario | Completed | Mean wait | Mean cycle | Blocked |
|---|---|---|---|---|
| Original scenario | 174 | 10s | 2m 22s | 0 |
Waiting averages cover arrived jobs, including unfinished waits; cycle averages cover completed jobs only. These are synthetic calculations, not measured site performance, revenue or a safety assessment.
Engine, status and output notes
process-des-2.7.0. Status: Original scenario: completed. “Completed” is the engine run status, not success for every job. Check blocked jobs and warnings.
- No engine warnings.
Engine inputs and saved comparisons stay with the saved project. Any limited trace affects playback details, not aggregate metrics.
Articles on this example
Housing managers and management associations, residential developers and designers, and anyone considering delivery boxesIs one lift enough for the morning at an apartment estate?At a four-block estate on a weekday morning, your AI simulates a resident's time from the door to the ground-floor hall with one lift car per block, and what a second car or delivery boxes change.Read the walkthrough 
Condominium boards and management companies, owners of rental apartment buildings, installers proposing security camerasHow many security cameras does an apartment entrance need?Your AI counts on the plan how many security cameras an apartment entrance needs for the vestibule, the auto-lock door, the delivery boxes and the lift hall to be seen.Read the walkthrough 
Board members of apartment owners’ associations and their managing agents, managers of public rental housing, installers proposing security camerasHow many security cameras does an apartment estate need?How many security cameras does an apartment estate need? On the site plan, eight on the street lights see 41.1%; with the blocks' walls too, sixteen see 73.5%, and 23 see 84.8%.Read the walkthrough
Plan in 2D. Inspect in 3D. Keep the whole project.
- Open and adjust. Switch between 2D and 3D; edit a part, a floor or an input. Both views describe the same model.
- Connect your agent for free. Sign in, choose Connect AI and connect ChatGPT, Claude, Codex or Claude Code. Ask it to inspect the example, edit the layout and check a route.
- Save a checkpoint. Project → Project file, or ask the agent to export the complete project. Import it later to restore floors, scenarios, saved comparisons and the selected view.
- Compare options. Run new operational comparisons under the same demand. Check Account for execution access, built-in AI and manual cloud-saving limits.