Alpha Models & Variants
Review concept and variant model coverage per type, sync coverage, and export all needed models to Excel
Models & Variants
The Models tab in the project editor shows, per type used in the project, which 3D/Revit models are needed and whether they already exist and are complete.
Pick a type on the left to see its models. The panel is split into tabs:
| Tab | What it shows |
|---|---|
| Concept | The models needed for the concept (base) configuration |
| One tab per variant | The models needed for each variant, derived from the plan options of the houses assigned to it |
| Plan filters | Which plan-option codes are actually used by houses in this project |
| Jobs | Coverage-calculation jobs queued for this type in this project |
Each row shows the model's tree, name, whether it exists in the database, and whether the RVT and GLB files are present (with file sizes).
Syncing coverage
The action buttons in the top-right recalculate which models are needed:
- Synchroniseren (Sync) — recalculates coverage for the currently open tab (concept or the selected variant), based on the plan options of the assigned houses.
- Sync all variants — queues a coverage recalculation for every variant of the selected type in one click.
Run a sync after changing house assignments or plan options so the needed-model list stays accurate.
Exporting models to Excel
The Export button (spreadsheet icon) downloads all needed models for the selected type in a single Excel file — the concept plus every variant — without having to open each tab.
The workbook contains one worksheet per source:
- A Concept sheet, and
- One sheet per variant (named after the variant).
Each sheet lists the same columns you see on screen: tree, name, whether the model exists in the database, completeness, and RVT/GLB presence and file size. The file is named for the project and type, e.g. Modellen - De Waarden IV - Type A - 2026-06-16 14.30.xlsx.
This gives buyers' advisors and modelling teams a single, shareable overview of everything that still needs to be modelled for a type.