Objective

Estimation data from the bill of quantities (BoQ) is exported from iTWO – or alternatively from Nevaris or BRZ – and transferred to specter. Two options are available:

Option 1

Model-Based Estimation (BoQ + Quantity Split): The BoQ and quantity split are exported and transferred via a GUID-position number link. This keeps quantities, costs, and hours directly linked to the 3D model components.

Option 2

BoQ without Quantity Split: Only a BoQ (as *.csv) is exported, without a quantity split and without model linkage. When creating tasks in specter, costs, effort value, and the short description name can be imported from it; the model or specter link is then established manually. This option works whenever a BoQ is available as a CSV (also from Nevaris, BRZ, …) and no model linkage yet exists.

Option 1: Model-Based Estimation (BoQ + Quantity Split)

Background & How It Works

This requires both the information from the bill of quantities (model-based) and the corresponding quantity split.

Options

It is possible to store only BoQ position names with quantities, without hours and costs. However, including all 3 data points provides the best added value. A decision must be made individually as to which “Costs” & “Hours” are to be used and analyzed (e.g., with or without surcharges, in hours or man-hours, etc.). The planned quantity (VA) can of course also be the work preparation quantity (AV); as a rule, the VA quantity is the most practical. In the BoQ *.csv, total costs and total hours are divided by the position quantity. For the quantity split, the VA quantity is distributed across each linked building component.

Required Fields for Export

A - Quantities Only (Without Costs & Hours)

Pos. No.	Short Description	Planned Quantity	Unit
1. 1. 10.	Cast-in-place Concrete Wall	2,01	m³

Required fields: Pos. No. · Short Description · Planned Quantity · Unit

B - Quantities + Hours

Pos. No.	Short Description	Planned Quantity	Unit	Hours
1. 1. 10.	Cast-in-place Concrete Wall	2,01	m³	52,26

Required fields: Pos. No. · Short Description · Planned Quantity · Unit · Hours

C - Quantities + Hours + Costs

Pos. No.	Short Description	Planned Quantity	Unit	Hours	Costs	Currency
1. 1. 10.	Cast-in-place Concrete Wall	2,01	m³	52,26	17.195,64	EUR

Required fields: Pos. No. · Short Description · Planned Quantity · Unit · Hours · Costs · Currency

Quantity Split via GUID (Model Linkeage)

Pos. No.	Planned Quantity	GUID
1. 1. 10.	2,01	D46e3baea-f64d-4007-9e86-ee5231a8e7a3D@ c0b4aa5f-8a5d-41da-8d68-943b0d493488@ Oc80dc50-97d8-4472-904b-a3674976d132

Required fields: Pos. No. · Planned Quantity · GUID

Steps in iTWO

STEP 1 - Export the Tender BoQ (Model-Oriented)

Open project → Open (Tender) BoQ (model-oriented)
Customize columns via right-click "Customize": show the desired values
Save the view for future reuse (saves column configuration) as:
1. specter_lv_export_uebergabe_in_specter
Right-click the table (BoQ) and select "Save As → Excel CSV File" (If this option is not available in your version of iTWO, the easiest workaround is to copy and paste into Excel and save as *.csv)

STEP 2 – Open Tender BoQ (model-oriented) & Open Quantity Split

Select the „Processing (Model Oriented)“ tab. The quantity split panel appears at the bottom right.

📷 Screenshot 1 "Processing (Model-Oriented)" tab + Quantity Split panel at the bottom right

⚠ Important: The quantity split only ever shows the components of the currently selected BoQ position. For ALL components to appear, the entire BoQ must be selected - not just a single position!

STEP 3 - Enable the GUID Column in the Quantity Split

Right-click in the quantity split panel -> "Customize..."

📷 Screenshot 2 – Right-click context menu: select "Customize..."

The "Column Display Properties – Standard_ItemQuantities.cft" dialog opens:

Column "Guid" → check the box for "Visible"
Enable/disable additional columns as needed:
Pos. No. · Guid
Confirm with OK

📷 Screenshot 3 – Column Display Properties (checking the Guid box)

⚠ Note: If "Guid" is not in the list → Step 3b: Add column manually

STEP 3b – Add Guid Column Manually (only if not in the list)

Click the three dots "..." at the end of a row
The "Column Definition" dialog opens:
Type: Object attribute | Content: Value
Search the attribute list for the following entries:
ifcGuid · ifcID · ID (depending on model configuration & iTWO version)

📷 Screenshot 4 – Column Definition: Type "Object attribute" → select ifcGuid / ifcID

STEP 4 – Export Quantity Split as CSV

Select the entire quantity split with the left mouse button (all rows). It is important that the complete BoQ is selected as the reference (or the 3D-based BoQ section if, for example, only structural/shell positions are to be exported).
Right-click → "Save As..." → "Excel CSV File..."
Save the iTWO view here as well for future exports as: specter_mengensplit_export_uebergabe_in_specter

📷 Screenshot 5 – Right-click: "Save As..." → "Excel CSV File..."

STEP 5 – Upload BoQ to specter

In the specter project data, navigate to the second tab "Estimation" and first upload the BoQ

📷 Screenshot 6 –Upload BoQ

STEP 6 - Upload Quantity Split to specter

In the specter project data, select the IFC model and then click "Next Step".
Then select the quantity split and click "Next Step" again.
You can now optionally upload an object catalog for an individual building structure. This step can be skipped by clicking "Next Step" if no object catalog is available.
Start the specter pipeline

📷 Screenshot 7 – Select *.ifc and choose the iTWO pipeline

Pros & Cons

Pros

Includes planned costs & hours
Calculated quantities directly from iTWO
Position names from the BoQ
Actual values can be added retroactively

Cons

Unedited short descriptions may be difficult for the construction team to read
Very detailed positions per building component
Subsequent assignment to tasks & trades required (one-time for the master BoQ)

⚠After import into specter: A one-time manual assignment to trades directly in the specter platform is required.

Option 2 - BoQ without Quantity Split

Background & How It Works

In this option, only a bill of quantities (BoQ) is exported as a CSV and uploaded to specter – without a quantity split and therefore without model linkage. The source can be iTWO, Nevaris, BRZ, or any other estimation tool from which the BoQ can be exported as *.csv. When creating tasks in specter, costs, effort value, and the short description/name are imported from the BoQ. The link to model components or within specter is then established manually. This option is suitable whenever a BoQ is available as *.csv and no model linkage yet exists.

Required Fields for Export

Pos. No.	Short Description	Unit	Hours	Costs	Currency
1. 1. 10.	Cast-in-place Concrete Wall	m³	52,26	17.195,64	EUR

Required fields: Pos. No. · Short Description · Unit · Hours · Costs · Currency

Recommended for full added value: additionally include costs and effort value. Technically, only position number and short description/name are mandatory.

⚠ Important to know: In this option, specter does NOT adopt the position numbers (Pos. No.) from the BoQ, but instead builds its own structure. The assignment to model components or the specter link must then be established manually.

Steps (BoQ Export & specter Import)

STEP 1 – Export BoQ

Open project → Open (Tender) BoQ.
Customize columns (show Pos. No., Short Description/Name, Costs, Effort Value).
Save as CSV – from iTWO, Nevaris, or BRZ.
Regarding iTWO, see above

STEP 2 – Import BoQ as CSV into specter

Import the BoQ when creating tasks in specter.

📷 Screenshot 8 – Importing the BoQ CSV when creating tasks in specter

STEP 3 – Adopt values

Costs, effort value, and short description/name are assigned to the tasks.

⚠ Important: specter does not adopt the position numbers (Pos. No.) from the BoQ, but builds its own structure.

📷 Screenshot 9 – Selecting the position in specter Work Preparation

STEP 4 – Establish Link Manually

The model link is then established manually, as no GUID-based model link is available. See the AV video in the Help Center for guidance.

Pros & Cons

Pros	Cons
Fast import directly when creating tasks in the Inspector Works with any BoQ as CSV (iTWO, Nevaris, BRZ) Costs & effort value can be adopted No quantity split / no model linkage required	No quantities from the model – no GUID linkage specter does not adopt BoQ position numbers, but builds its own structure Model/Inspector link must be established manually Less automation than Option 1