Platform
It does not just read your model. It changes it, with your permission.
An agent that drives Revit and Navisworks directly. Ask it anything about the live model, and every write it makes is previewed element by element before it runs.
It can't invent an action that isn't there.
Every question and every edit resolves to a real Revit or Navisworks operation, with its parameters checked against a strict schema before anything runs. The agent only picks from operations the model actually supports, and only fills fields it will accept.
Reads never fall back to running code. So when it tells you eight doors on Level 3 sit below the standard head height, it read them from the live model. It did not approximate.
How many doors on Level 3 sit below the standard head height?
Ask the live model the way you'd ask a colleague.
One question, in plain language, against the model open on your desk. The agent counts, filters and cross-checks, then answers in millimetres with a clean result, not a wall of raw properties.
Which doors on Level 3 sit below a 2100 mm head height?
Reading the door head heights on Level 3.
8 of 42 doors on Level 3 sit below 2100 mm.
- Which grids aren't pinned?
- In-place families in the model
- Walls taller than 6 m
- What are my worst warnings?
- Rooms that are unplaced or unbounded
- Views that aren't on a sheet
- Concrete volume by wall type
- Total duct length
- Floor area by department
- What differs from the structural link?
- Why is my link in the wrong place?
Nothing changes until you approve that exact change.
Ask for an edit and the agent previews it first. It shows you what it matched and the before and after for each element, and writes nothing. You approve that specific change, and only then does it commit.
Type parameters
If a change would hit every element of a type, not just your selection, it says so before it runs.
Bulk deletes
Removing more than 500 elements needs an explicit override, and it lists what Revit would take with them.
Derived values
Area, volume and wall thickness are calculated. It explains why they can't be set directly instead of failing quietly.
Set Head Height to 2100 mm on Level 3 doors
and 6 more
Nothing has changed yet.
One conversation over the whole project.
The same agent reads and writes your Revit model and your Navisworks federation, and reads across every coordination engine, your documents and your decision log. Whatever figure it gives you, it names where the figure came from.
Revit
The authoring model, read and written through the Bridge.
Navisworks
The federated model and its clash tests.
Coordination engines
Clash, spec, document and readiness results.
Documents
Specs, consultant reports and minutes, by hybrid search.
Decisions and RFIs
Past calls and the questions still open.
Compound work runs as one job.
Ask for something that takes several steps, like setting up the drawing set for a level. The agent previews the whole plan at once. Approve it once and it commits as a single undo.
Set up the drawing set for Level 3
- 1Create floor plan, Level 3
- 2Create sheet A103
- 3Place the plan on A103
- 4Apply view template "A1 Plan"
- 5Tag the doors on the view
One preview, one approval, one undo. If any step fails, the whole job rolls back.
Your next coordination cycle starts soon
Connect your model, drop in your specs, and see what Bimiq finds in the first hour.
14-day free trial. No credit card required.