Skip to main content

What is the Revit import?

The Revit import or import is the final step in the Innobrix process. When your properties have been sold and you want to use your buyer's choices to put together the final model then using the Revit import may be your best and fastest way to do this. The import step works on the basis of a loaded configuration (.JSON) file and can only be used successfully within the documents from which the models were also exported.

What is a configuration (JSON) file?​

The configuration file you can generate from Innobrix studio could be compared to a shopping list. It does not contain geometry but simply a list of groups that make up the selected Property. The file also contains the Configurable name from which the Dwelling was created (which is equivalent to the Innobrix: Type(s) parameter). The configuration file can be downloaded in Innobrix in 2 different places:

  1. Within the Plan Editor: select one or more Houses, then click on the icon.
  2. On the Configurations page in the Studio: click on the ... next to an available Configuration and then click on the R icon.

It is important that there is a relationship between the situation in Innobrix and the situation in Revit. That is, the houses that exist in Innobrix exist basically also correspond to the situation that exists in Revit.

When you start loading a configuration file, the Innobrix add-in will ask you for its own parameter. This parameter should be:

  • Instance based
  • Be present on all Model Groups.

This parameter establishes the link between the Home in Innobrix on the one hand, and the collection of Model Groups that make up a home in Revit on the other.

Matching

So it is very important that the content filling of this parameter in Innobrix and Revit EXACT match!

Construction-numbers

What happens during the import process?​

Once a configuration .JSON file is loaded and the import process is started, the Innobrix add-in will engage in the following actions:

  • Based on the configuration .JSON file exchange of Model Groups when a group exists in the base situation but is not chosen in the configuration file.
  • Based on the configuration .JSON file, instantiate of Model Groups that do not exist in the current base situation but have been chosen in Innobrix.
  • Based on the configuration .JSON file, don't do anything with Model Groups that both exist in the current base situation, and that are also present in the configuration file.
  • After the groups are exchanged, any material substitutions are applied to the elements within the groups affected. The group is made unique.
Material parameter

It is important for any generic elements that the Material parameter is an editable field. For material switches applied specifically to Wall family elements, it is important to have target materials available as Family types since Walls do not contain a material parameter but are provided with materials based on their structure.

How does the add-in know which groups to exchange?​

The configuration file inside searches based on Innobrix: Type(s) in combination with the list of groups that have the correct Floor (deprecated, and only applicable for old models of still) , Column and Row parameters. However, it is likely that you have used one Model Group for several construction numbers (or even types).

Imagine that the Model Group facade of Building Number 1 is also used for Building Number 2. Only one of the 2 groups is provided with Innobrix parameters.

Both groups are instances of each other.

The add-in knows how to distinguish based on the own defined parameter.

2 instances: 2 different 'Innobrix: Types'

The add-in cannot properly detect when 2 Model Groups (which are instances of each other) are exported to Innobrix as 2 separate groups. Should the add-in detect this problem, the group will be skipped during the import process and the add-in will continue the process. The add-in's log file will also mention the problem should it be detected.

Uncertain import This issue can be resolved in 2 ways:

  • By making both groups unique so that they are no longer instances of each other, or
  • By using the ;-seperator so that you need one group for exporting and importing.