CalqenfrarptSign in

Workflows / COBie, BCF and IDS from the BIM model

COBie, BCF and IDS from the BIM model

Calq writes the COBie 2.4 handover workbook, exchanges issues as BCF 2.1 and 3.0, reads and writes IDS 1.0 and checks the model against it, and names every file by ISO 19650-2, from a free account in the browser.

What it is

Information delivery is what a project must hand over beside its geometry: the asset data, the open issues, proof that the model holds what was asked, and files named so anyone can find them. Calq does each through the open standard made for it, read from the same model the IFC is written from.

Because the workbook, the issues and the checks read the same elements and the same GlobalIds as the IFC file, what one says agrees with the others.

COBie 2.4: the handover workbook

Calq writes COBie 2.4 as the workbook a facilities team loads: every sheet of the standard in its order, with its own column headings.

BCF: issues that travel

An issue raised in Calq is a BCF topic: its title, status, priority, comments and viewpoints, with the camera and the elements selected. It leaves as BCF 2.1 or 3.0 and selects the same elements in any BCF tool, because they are named by the GlobalId of the IFC export.

A BCF file from another tool comes in as issues on the model. Rows of a schedule become issues in one step, so a list of doors that fail a rule is a list of topics.

IDS: what the model must hold

An IDS 1.0 file says which objects must carry which classes, attributes, properties, classifications and materials. Calq reads the file and checks it on the IFC4 the model exports, exactly as another tool will read it, and lists each specification as met or not, with the elements that fall short.

A project can also set its milestone by the level of information need of ISO 7817-1: Calq checks the model at that milestone, and writes the same requirements out as an IDS file for every other party.

Names, statuses and revisions

Good to know

COBie, BCF, IDS and IFC export are written in the browser and are on the free account. Bringing an IFC in is Beta: check what comes in.

A handover is as complete as the model: an asset with no type or no room says n/a in its cell, and an IDS facet Calq has no check for is kept as a note on its specification, never passed in silence.

Questions

Can I export COBie from Calq?

Yes. Calq writes a COBie 2.4 workbook from the model in the browser, with every sheet of the standard, on the free account.

Does Calq support BCF?

Yes. Calq exports issues as BCF 2.1 or 3.0 with their viewpoints, and imports BCF files from other tools as issues on the model.

Can Calq check a model against an IDS file?

Yes. Calq reads an IDS 1.0 file and checks it on the IFC4 the model exports, listing each specification as met or not and the elements that fall short.

Does Calq name files by ISO 19650?

Yes. Every export's file name, status and revision follow ISO 19650-2 from one table, and a sheet's title block reads the same record.

Is COBie export free?

Yes. COBie, BCF, IDS, gbXML and IFC export are all on the free account, with no card.

Do BCF issues from Calq open in other BIM tools?

Yes. A viewpoint names its elements by the GlobalId of Calq's IFC export, so a tool that has that IFC open selects the same elements.

Related

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