A robot builds what is in the plan and nothing else, so the plan has to hold every part. The Tonian dashboard takes a scan of a site to that plan in five steps. The screenshots show the same steps on another job: a scaffold planned along the facade of a scanned farmhouse.
Upload a photogrammetry scan. The dashboard turns it into a measured model: the terrain on a 10 cm grid, the buildings already there, and build, no-go and staging zones drawn in plan.
Shown: Elevation map of the site in plan view with contour lines and a build zone
Draw the walls on the site, drag doors and windows onto them, add storeys and a roof. The house is a timber frame on a slab, the way a framer would build it.
Shown: A scaffold planned along the facade of a scanned farmhouse, in 3D
The dashboard frames every wall with a framer’s rules: studs on the grid, plates, kings, jacks and headers at the openings, sheathing laid the way a crew lays it. Then it places every screw, with its head, its tip and the member it holds.
Shown: The scaffold editor: bays, decks and heights, with 11 collisions with the scan flagged
Each member is placed after everything it rests on. Scrub through the build and the problems show up on screen instead of on site.
Shown: The scaffold in build order, lift by lift, part 264 of 488
The plan becomes a task graph: one task per member, with what it requires, who carries it, and the screws it closes. A whole house or one wall can be exported for the robots.
Shown: Dispatch: 376 tasks scheduled across four robots, with the critical path
The export is a set of open, versioned JSON formats plus the terrain grid. Each file is hashed, so the plan on site can be checked against the plan that was approved.
Planning, orchestration and verification do not know which robot or which part library they drive. Parts and skills plug in, so a new trade is another library on the same spine. Scaffolding and earthworks already run on it.
