Workflows / The federated model: every discipline, one coordinated whole
The federated model: every discipline, one coordinated whole
How to federate an LOD 400 project in Calq: one model per discipline linked into the others, their storeys mapped, each model changing only what is its own, Calq AI working from the linked models, and the whole written to IFC.
- Available
One model or several
A small project can live in one Calq model, every discipline drawing in it at once. A large one is usually split: architecture, structure, services, site, each in its own model with its own team and its own issues, federated into one coordinated whole. ISO 19650 calls each an information container; together they are the federated model.
In Calq a link is live: a linked model is drawn in every view of yours, read by the checks and by Calq AI, and it follows the other team's saves.
Federate, step by step
- Link each model: the Project menu, Any time, Linked models, or Calq AI "link the structure model and the services model of this project" (link_model). An IFC from a tool outside Calq links the same way.
- Map the storeys: each storey of a linked model is drawn on one storey of yours, by the map you give or by height; the storeys you lack are made in one step on your word (take_link_storeys).
- Decide how each link looks: normal, halftone or as an underlay; each view may draw a link as in its own model or its own way (set_view_graphics).
- Work from the links: Calq AI reads your model with its links, so it can lay the services under a linked architecture's ceilings or a structure on its grid, writing only into your model.
- Coordinate across them: check_links and coordinate_links, as on the clash detection page; each model changes only its own elements.
Who owns what
The owner of a wall makes its holes; the model that owns a run only asks. A hole carries the same key in both models, so both agree with nothing passed between them, and its state is asked, made, moved or refused. That keeps each discipline's responsibility in its own container, as ISO 19650 asks.
Hand the federation over
- One IFC of the whole federation, or one file per model (export_ifc)
- The coordination requests as IFC provisions for voids and BCF (export_link_requests)
- Each model's people and roles kept per model
Questions
Can I link models from different Calq projects?
A link reads a model the person can open. Each link's storeys are mapped to yours and its look is chosen per view.
Does Calq AI see the linked models?
Yes. It reads your model with its links, says what each link brought, and writes only into your model.