CalqenfrarptSign in

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.

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

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

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.

Related

Try it in CalqThe full guide is in Calq, for signed-in accounts.