Add drawings & detail

The map has the where. This step adds the how big — the height, diameters and wall thickness no satellite image can show. Drop a GA, elevation or section sheet and the assistant reads the figures off it against the structures you have already placed; each one arrives on the next screen as a suggestion beside its field, naming the sheet it came from, for you to accept or reject. Nothing you placed gets moved or replaced.

Nothing placed yet? You can describe the job here instead and the assistant will place structures from your words — but it has to guess where they are, so setting the site on the map first is the accurate route.

Not sure where to start? These pre-fill the assistant with a typical job — change the location and sizes to match yours.

🗣️ Describe your job — the AI sets it up

New here? Just tell the assistant what you're demolishing, roughly where, and how — it asks what it needs, then pre-fills the plan for you to confirm. No forms to get started. It helps you plan and simulate; the blast / charge design stays with your licensed engineer.

⚡ The AI assistant isn't switched on for this deployment yet. To chat and drop drawings / photos here, add these to your server (on Render → your service → Environment), then redeploy:

DEMSIM_LLM_BASE_URL = https://api.ppq.ai
DEMSIM_LLM_API_KEY = your ppq.ai key
DEMSIM_LLM_MODEL = claude-sonnet-5 (or any vision-capable model)

The name must be exactly DEMSIM_LLM_API_KEY — not DEMSIM_API_KEYS (that's the login password). Until then you can set up your site by hand just below — it runs exactly the same simulation.

Your site: boundary & structures

1 Find your site

Paste a Google Maps link or coordinates and the satellite jumps there. This is the fastest way in — everything else on this screen builds on the view you land on.

2 Put the structures on the map

Add what is coming down and the neighbours that matter — the surroundings are what turn a collapse into a clearance answer. Every value lands as an assumption you confirm next.

What are you demolishing here? Optional, but it is the difference between the AI finding your structures and finding whatever it noticed. Say which ones matter and what to call them. It reads position and footprint only — heights always come from you or a drawing.

Click the BASE of a structure, never its top. (why?)

Satellite imagery is corrected for the ground, not for tall objects: a chimney is photographed at an angle, so its top leans away from the centre of the image and can appear tens of metres from where it actually stands. Pin the base — the point where it meets the ground — and the model will sit on the real one instead of beside it. If the lean is severe, the Basemap list offers other captures of the same ground; one of them will be closer to straight down.

Import instead — coordinates, GeoJSON, an IFC model or drone footage

From drone footage (beta)

Pick 3+ overlapping drone photos of the site and the platform sends them to your own open-source photogrammetry node (OpenDroneMap) to build a textured 3D site mesh — stored with the study and downloadable. The capture becomes scenery in the photoreal render, and it can propose structures with measured heights for your plan — every proposal is an assumption you confirm, and anything that is really vegetation or parked plant can be deleted. Greyed out until a NodeODM endpoint is configured on the server.

3 What is on your site

Nothing placed yet.

Confirm every assumption

📄 Drawings & documents

Checking what is held…

A satellite image cannot see height, so unless you state it, it is a default. Drop a GA, elevation or section and the assistant reads the height, diameters and wall thickness off it — each figure arrives beside its own field for you to accept or reject. Nothing you placed is moved or replaced, and every file stays with the study, so a client asking "where did that height come from?" gets the sheet.

Reading figures off a sheet needs the AI reader, which is not switched on for this deployment — drop the files anyway and they are kept with the study, but you will need to type the height and diameters in below. (Running locally? demsim serve asks for the gateway settings on first start.)

Member schedule (optional) — beam & column sizes, tier L2

This is a different thing from the drawings button above. Above reads the overall dimensions of a structure off a GA or elevation — height, diameters, wall. This reads a member schedule table — the mark/size/grade/rebar list for a framed building's columns and beams — and is what raises the study from L0 (typology defaults) to L2 (documented members). A chimney or cooling tower has no member schedule, so this does nothing for a stack.

Paste the schedule table text, or upload a photo / screenshot of the drawing sheet — with an AI reader configured on the server (ppq.ai or Anthropic key) the image is transcribed automatically. Every extracted field keeps its verbatim text with a confidence score — doubtful cells are highlighted; click any cell to correct it. Corrected fields re-parse at full confidence; uncorrected doubtful fields are skipped at run time, never silently trusted. (PDF: export the schedule page(s) as PNG/JPG first.)

Proximity to surroundings

Reference rings (inner yellow, outer green) around the selected structure (click one on the plan) — or tick Ring all chimneys to ring the whole row at once — and the measured closest-approach distance to every other structure and receptor — the figures that drive the exclusion-zone radii and the fall direction (plan the fall away from the nearest receptors). Trace neighbouring footprints on the site map, and add receptors (nearby buildings / sensitive sites you only need the distance to). Distances are straight-line, in metres, in the shared map frame.

Reference rings [m] Receptor name Ring all chimneys

Demolition plan

Which structure is coming down?

Check every structure you want demolished in THIS run. One checked runs it alone, with the full plan below. Two or more checked run them TOGETHER on one shared clock — each keeps its own technique preset and its own delay from the clock below.

Plan type Preset: directional felling (topple away) Preset: implosion (vertical collapse) Preset: high-reach machine (nibble top-down within boom reach)

When the first cut fires [s]

Firing / work sequence

One row per delay group: what happens, to which members, when. In the solver a charge is a timed member elimination — which members act, and when. The hole layout and charges behind each group are recorded in the Drill & charge plan module. Leave storey/gridline blank to mean "all".

t [s]	action	members	storey	grid	machine load	note

Pre-weakening (site prep cuts, existing damage)

Mark the notch member by member: click columns on each floor plan to record what your crews cut before firing — torch cuts, partial saw cuts, stripped cover, known deterioration. Members shade red by how deep the cut is. This is your recorded site prep; the platform simulates its effect on the collapse — it never designs the cut.

Or type the cuts in a table

A drawn plan above supersedes this table. Use it when you would rather type gridline names than click.

members	storey	grid	remaining capacity	note

How long to simulate [s] Finish quality

Same physics either way — Presentation divides the structure finer and runs the joints at nearer full stiffness, so the motion and the debris pile are what you would show a client. The run-time estimate below follows whichever you pick.

Physics engine

Reference is the engine every capacity test and golden run locks — deliverables run on it. The Bullet preview trades fidelity for speed (joint capacities collapse to one scalar): a quick look-see, never a client figure. Greyed out when this server does not have the preview engine installed.

Uncertainty band

A collapse is chaotic, so one run is one sample of it. Running the same plan several times over the capacity model's own stated scatter shows how far the debris figure actually moves — a range to plan against instead of a single number. Each run is a full simulation, so 5 runs takes about five times as long. The band covers the capacity model only: not an untested batch of concrete, not the weather, not a charge that fails to fire.

Where this runs

Before you run — reality check

What is confirmed, what came from map/file data, and what is still a typology assumption for this target — so you know exactly what fidelity you are presenting.

Replay

View the collapse in 3D on the map solver output on the real site — render adds light, never motion

Records the replay above exactly as you see it — solver output on the satellite view — straight to a file on your machine. Nothing is uploaded and it costs nothing. Set the camera angle you want first; the recording follows the view. For a lit, shaded cinematic version, use the photoreal render below.

Premium — photoreal video Provider

A lit, shaded MP4 of this collapse, rendered on a GPU — a visualisation of the simulation (render adds light, never motion). A premium GPU step; the in-browser 3D replay above is free.

Result

Want to try something different?

Fell Direction Wind Speed

Safety plan — debris vs exclusion zone

Predicted debris reach (solver output) against your cleared exclusion perimeter. This is not a recommended safety distance — the exclusion figure is the contractor's, and every deliverable requires review by a licensed professional.

Your exclusion perimeter [m] Ground slope [°, − is uphill] Slope falls toward [bearing °]

Provenance

Is this replay physically plausible?

Your verdict is logged against the knowledge pack (improvement Loop 2). It never edits physics directly.

After the real demolition — record the outcome (improves calibration)

The only data that can ever change physics parameters — and only through the calibration gate. Enter what was actually observed; leave unknowns blank and state the measurement quality honestly.

Upload collapse sequence photos

📹 Measure the real fall from your footage — the strongest evidence you can give us. End figures (where the rubble landed) are weak: many different collapses end in the same pile. The fall itself pins the dynamics down.

Save a few frames from your video. For each one: set its time (seconds after the first cut), load it, then click the structure's base and then its tip — or let the AI suggest them and just check. Three or more readings is enough.

Frame time [s]

time	tilt	frame

Honest limit: this measures the angle in the picture, so it is the true tilt only when the camera looked roughly square-on to the way the structure fell — which is how a felling is normally filmed. Don't use a steeply angled view.

Each frame you measure is kept with this record, along with where you clicked, so the measurement can be checked later — by you, by a reviewer, or by a better method. Frames are stored reduced in size (not the original video), so keep your own copy of the footage.

📐 Measure it from an after-flight drone capture

Fly the site after the demolition and run the capture (site screen). The remnant height inside each target's footprint is measured from the AFTER flight; measuring debris reach needs a BEFORE flight too — without one, new rubble cannot be told from ground clutter, so no debris figure is claimed.

After flight Before flight

Project Structure Measurement quality Tallest standing remnant [m] Farthest debris beyond footprint [m] structure came down completely

The predicted fall drawn over the fall you measured, with the difference at every reading — the review artifact, and the honest version of the “real vs simulation” picture competitors publish as marketing.

Basemap

Always click the BASE where it meets the ground, never the top or the roof — tall structures lean in satellite imagery, and this platform does not correct for lean. To check a placement, switch between the two satellite captures above: a structure on its base stays put, one placed on its lean jumps.

Any XYZ raster template with {z}/{x}/{y} works — paste your orthophoto or licensed-imagery service to trace over it. Tiles are viewing context only; the traced polygons are the engineering input and carry traced provenance.

Checking your sign-in…

Your branding — client deliverables

Add drawings & detail

🗣️ Describe your job — the AI sets it up

Your site: boundary & structures

1 Find your site

2 Put the structures on the map

📷 Street View

From coordinates (OpenStreetMap)

From a GeoJSON file

From drone footage (beta)

From a BIM / IFC file

3 What is on your site

Parametric Structures — manual dimensions

Confirm every assumption

📄 Drawings & documents

Member schedule (optional) — beam & column sizes, tier L2

Proximity to surroundings

Demolition plan

Per-structure firing plan

Detail level & compute

Cut-arc study — at what % does it come down?

Firing sequence (chimney)

Firing / work sequence

Blast sequence planner

Drill & charge plan

Dust & air quality

Water monitors on this job

Misting curtains

Noise

Ground vibration (PPV)

Weather & wind

Timing optimiser

Before you run — reality check

Building your simulation…

My studies

Project plan — method statement & programme

Replay