Awaiting review
Sheet layout
Four sheets renamed, one added
from Archicad · not yet applied
Nothing has changed in Mudo. That is the design, not a delay.
A sync you have to agree to
In pilot — available to selected practices
Not shown here
The Archicad side of the connection
Showing it means capturing it from a real pilot practice. An illustrated Archicad window would be a claim about software Mudo does not publish, so this page argues from what crosses the boundary rather than from a picture of either side of it.
In short
In pilotRunning with a small number of invited practices. Access by request.- What it is
- A bridge between Archicad and Mudo. Project information, model data, drawing registers, schedules and budgets are kept in step between the model and the practice system.
- Who it is for
- Practices working in Archicad whose drawing register, schedules and fee position are maintained separately from the model and drift apart between issues.
- What is different
- Very little practice management software reaches into the BIM model at all. This is the capability that keeps the design record and the commercial record describing the same job.
- Availability
- In pilot. Running with a small number of invited practices, behind an access gate. Not generally available, and not included on any plan by default.
- How it connects
- Connect feeds the drawing register that drawing review works on, the project information in the Pod, and the budget figures the commercial position uses.
Part of Create.
Verified against the Mudo application on .
The drift between the set and the fee
On a long project the drawing register and the commercial record slowly stop describing the same job. Sheets are added in the model that the register never hears about. A package is issued that the fee schedule does not reflect.
Nobody notices until an issue is prepared or an invoice is questioned, and by then the reconciliation is archaeology.
What the bridge actually does
Connect keeps specific things in step: project information, model data, the drawing register, visual schedules and budget figures. It is a synchronisation, not a takeover. The model stays in Archicad and the practice record stays in Mudo.
Why this is in pilot, and stays labelled
Connect is significant enough to be a reason to choose Mudo, which is exactly why its status must be stated everywhere it is mentioned rather than implied.
It runs today with a small number of invited practices. It is not on general release, it is not included in a plan by default, and this page will change when that changes.
Common questions
What does Mudo Connect do?
It links an Archicad model to the Mudo project. Project information, model data, drawing registers, visual schedules and budget figures are synchronised, so the register the practice manages and the set the model produces describe the same thing.
Is Mudo Connect available?
Not generally. It is in pilot with a small number of invited practices and sits behind an access gate in the application. Access is by request, and it is not part of standard plan entitlement.
Which BIM tools are supported?
Archicad. Nothing else is claimed, because nothing else is implemented.
What this page is based on
Every capability described here was checked against the running application before publication. These are the parts of it you can open for yourself.
- /connect/archicad, /connect/drawing-register-sync, /connect/budget-syncThe Connect modules that are implemented and reachable in the application.
Keep the drawing set and the fee from drifting apart.
This capability is running with a small number of invited practices. Access is by request rather than by signing up.