Tutorials BimCraft help Coming from other software
Working between two BIM programs
Send a model from one BIM program to another through IFC with BimCraft in the middle, keep its GlobalIds, property sets and classifications, set both programs up for the same properties, and see what came back.
Written for BimCraft 0.6.1. The same help is inside the app: press F1.
What you'll do
Move a model between two BIM programs, for example from Revit to Archicad and back, through IFC, with BimCraft in the middle to check it, add to it and report what survived. Neither program's own file format is read: everything travels as IFC.
What BimCraft keeps
When you change a model in BimCraft and click Save as IFC, every line you did not change is written back exactly as it was. So:
- GlobalIds stay the same, and the other program can match each element to the one it sent.
- Property sets and their values stay, apart from the values you changed.
- Classifications stay attached to their elements.
Set both programs up for the same properties
- Open the model in BimCraft (and the project bundle, if you have one: its property groups are added).
- In the left panel, open Between two BIM programs.
- Under Property mapping, download what each program needs:
- Shared parameters: a shared parameter file. In Revit, load it with Manage › Shared Parameters and add the parameters to the categories that need them.
- IFC export property sets: a user-defined property set file. In Revit's IFC export settings, choose it under user-defined property sets, so the exported IFC carries the same set and property names.
- Mapping table (CSV): every property with its IFC set and name, its type, and the matching names in each program. Archicad's mapping files are not a published format, so set up its IFC translator and property manager from this table by hand.
- Mapping file: the whole mapping as one file, to keep with the project.
Standard sets (Pset_ and Qto_) are left out of the shared parameter file: both programs write those from their own data.
Send the model and bring it back
- Export IFC from the first program with GlobalIds kept (Revit: "Store the IFC GUID in an element parameter after export" on).
- Open it in BimCraft, check it (Model checks, Clash check), add issues (Issues, BCF), change values if you need to, and Save as IFC.
- Open the saved IFC in the second program, work on it, and export IFC from there with GlobalIds kept (Archicad's translator: "Global Unique Identifiers: Keep existing").
- Back in BimCraft, open the model that went out, then add the one that came back (Add a model under Models).
- In Between two BIM programs, choose Went out and Came back, and click Make the report.
Read the report
- Elements: how many came back with the same GlobalId, how many are missing, and how many are new. Elements with a new GlobalId show as one missing and one new: the other program did not keep it.
- IFC class changed: elements that came back as another kind of element.
- Property values kept: the share of values that came back unchanged. The list below shows the properties with the most changed or missing values.
- Classifications: kept, changed (same system, another code) or missing.
Download the report (CSV) gives every property with its counts. To see which elements moved or changed shape, use Compare versions on the same two models.
Issues travel as BCF
Issues you raise in BimCraft export as BCF (Issues), which both programs can read with their BCF tools, so a question about an element reaches the person working in the other program with its viewpoint.
See also Open a project bundle, From a project file to BimCraft through IFC and Compare two versions of a model.