Alpha Importing Bouwnummers from Optio
Fill a project's blocks and bouwnummers from an Optio projectoverzichtlijst instead of typing them in by hand
Importing Bouwnummers from Optio
If your development department hands you a project as an Optio projectoverzichtlijst, you can load it straight into a project instead of retyping every bouwnummer. The import fills in the blocks, the bouwnummers, their woningtype, whether they are mirrored, and the plan options that come with the house.
The import always runs in two steps: it first shows you what it would do, and only writes once you confirm.
Where to find it
- Open the project in Construction → Projects → [project].
- Switch the editor to Design → Viewer.
- In the right toolbar open the tools menu and choose Import from Optio.
What the file must contain
An .xlsx with these sheets:
| Sheet | Used for |
|---|---|
Projecten | The project number and description, shown as a header in the preview |
Bouwnummer | One row per bouwnummer: this is the sheet that actually creates houses |
OPTIOelementen | Optional. Per-bouwnummer element parameters |
From the Bouwnummer sheet the import reads:
| Column | Becomes |
|---|---|
blok | The block the bouwnummer lands in |
bouwnummer | The bouwnummer (bnr) itself |
optio_type | The woningtype, matched on the Alpha type's name |
beukmaat | The Beukmaat option |
stramiendiepte | The Stramiendiepte option |
woningsoort | The Type Woning option (hoek, tussen, tweekapper, vrijstaand) |
gespiegeld | Mirrored, when the cell contains an x |
From OPTIOelementen, a parameter like ELE-19 selects the option that offers that code, and a suffixed one like ELE-19_breedte with value 2835 sets its companion option. This is resolved per woningtype, because the same element code can mean different things on different types.
Nothing is hard-coded. The import looks the codes up in the woningtype itself, so a code you add to a type later is picked up without a code change.
The preview
After you drop the file in and press Controleren, you get a row per bouwnummer:
| Label | Meaning |
|---|---|
| Nieuw | The bouwnummer does not exist yet and will be created |
| Bijwerken | It already exists; its woningtype, spiegeling and plan options will be updated |
| Niet mogelijk | It cannot be imported: the reason is shown next to it |
A bouwnummer is skipped when:
- there is no woningtype with that name. This is the common one: an Optio export usually names types that have not been built in Alpha yet. Create the type first, then import again.
- the bouwnummer is not numeric (e.g.
12A). Alpha generates new bouwnummers by counting, and a non-numeric one breaks that. - the same bouwnummer appears twice in the sheet.
Anything else is only a remark and does not stop the row: an element code the woningtype does not model, or a value that is not one of the option's codes. Those show in the Opmerkingen column and that single option is left unset; the rest of the bouwnummer still imports.
Importing again on the same project
Re-importing is safe. An existing bouwnummer keeps its buyer, sale status, buyer choices, base configuration and price; the import only touches the woningtype, the spiegeling and the plan options. So you can re-run it after development sends an updated list without losing anything a buyer configured.
New bouwnummers count towards your woningen quota, the same as adding them by hand.