Model Groups
For models with options, Innobrix uses a modular concept based on Revit Model Groups. These are reusable, swappable groups of elements or parts of a model. Innobrix builds on this by tagging these groups with a set of Innobrix parameters. Those parameters are then used in Innobrix to generate a gridfield where groups can be swapped based on a buyer�s option list. This lets you offer a home or concept in a modern way to buyers and stakeholders. Elements not in Model Groups are never exported to Innobrix.
To understand the Model Group structure, check the Configurator Revit Model in our Downloads.
When a home is sold and options chosen, you can use the same modular approach by swapping Model Groups in your Revit document for the chosen options. It is a bidirectional pipeline: from Revit to Innobrix and back. That last step is the Revit import.
Origins
When setting up Model Groups, it is essential to place the Model Group origin (zero point) consistently. The origin acts as an anchor; all geometry in a model group is positioned relative to it.
... Why is this important?
When exporting to Innobrix, all Model Groups in the IBX file are moved to the origin. If geometry is positioned incorrectly relative to the origin (or vice versa), parts of the model will be misaligned when expanded in the Configurable Editor.
The animation shows collapsing/expanding the gridfield. From the physical position of a group in the gridfield (set by parameters in Revit), the group is moved back to the absolute origin (0,0,0). Options then swap one or more groups.
Simply put: front and rear facade model groups have their origins at the same spot.
Innobrix: Type(s)
Model Groups are inherently modular and reusable. Innobrix leverages this. If you reuse a Model Group across multiple homes or types, you only need to set parameters on one of them, saving time and reducing errors.
Check if a Model Group is reused by performing an instance check in Revit. Select a Model Group, open the context menu (RMB) -> Select all instances -> Visible in view. All instances are now selected.
Projects often have staggered (front) facades, as below. Everything except the staggered facade elements is the same between lot 1 and lot 2 (layouts, options, etc.). In that case, implement the lot-specific facades as a Functional option.
Similarly, end facades that differ between mid-terrace and corner homes fall under the same home type if bay width matches.
"Type" is broad, but in Innobrix a home type is usually differentiated at the bay width level. Otherwise, you double the number of Model Groups in the gridfield for the same options. While possible, we do not recommend it due to maintainability, scale, and complexity.
Modeling considerations
- Do not model building-spanning elements (e.g., one roof spanning the entire block).
- It is not required, but splitting elements per floor is preferred.
- Minimize element-dependent constraints (e.g., Attach to top); the Revit import swapping Model Groups may break these constraints.
- Ensure model group origins are placed correctly.
- Material names longer than 63 are truncated to 63 characters (some special unicode chars may consume more than one ASCII character).
Tracking Model Groups
As you develop models/home concepts, your gridfield in Innobrix will likely grow because of more model groups for options. It is practical to set up a Revit Schedule to track how many groups you created and parameterized.