Blog

Measurement BIM and coding

📐 Article5 min read

What you will learn What a digital model really changes for measurement, why attaching quantities to items remains manual, where coding is decided, and what does not automate.

A digital model produces quantities. It does not produce a bill of quantities.

The difference lies in attachment: moving from a modelled object to an item of a bill presupposes a decision, and that decision has no general automatic solution in Belgium. No software takes that decision in the drafter's place.

What the model really changes

Three contributions are real and measurable. They concern quantity extraction, consistency and traceability.

The reliability of geometric quantities. Areas, volumes and lengths extracted from a coherent model are more reliable than a manual take-off, and they recalculate instantly after a change.

Traceability. Each quantity attaches to an identifiable object, so its origin is known.

Detection of geometric inconsistencies, revealing early the problems that would otherwise surface on site.

What the model does not change: the definition of an item's scope. A modelled object does not state which incidentals, finishes or tolerances attach to it. That remains in the description.

Why attachment remains laborious

The cause is structural and lies in the nature of classification systems, explained in the article on the federal framework and coding. Classifying an object and describing it remain two distinct operations.

Belgian specification frameworks are enumerative. Each element occupies a single position in a single hierarchy.

Classification systems used in digital environments are predominantly faceted. An object receives several codes along several independent axes.

Moving from the latter to the former amounts to reducing a multidimensional description to a single position. That is design work, not conversion, and it depends on the project, the level of detail adopted and the conventions agreed.

Where coding is decided

This is the most important practical point, and it plays out at the start of the project. It concerns the choice of coding.

The coding used in a digital project follows from an explicit choice: it may be standardised, proprietary or defined specifically for the project, and that choice is settled in the documents framing digital collaboration. That choice is recorded in the project protocol.

Belgium has a national reference protocol for buildings, which structures that collaboration and provides for these conventions to be defined rather than endured.

Three questions must find answers there.

Which classification system is used, and at what level of detail.

How attachment to the items of the specification framework applicable to the contract is made.

Who produces the bill from the model, and under whose responsibility.

A project that does not settle those three questions at the outset will settle them under pressure, when the tender documents are produced.

Operation Automatable Human decision
Quantity extraction Yes, from the model Choice of level of detail
Breakdown into items No Structure of the bill
Choice of unit No Measurement convention adopted
Object to item attachment Partly Attachment rule and judgement calls

What does not automate

Four operations remain human decisions, whatever the tooling. They concern the breakdown, the unit, the convention and the attachment.

The choice of division. Deciding that a work forms one item or several belongs to the economics of the project, not to geometry.

Measurement rules. Deducting openings or not, measuring to the centreline or to the face, are conventions attaching to the framework, not to the model.

Unmodelled works. Site set-up, protection, coordination, testing and waste management do not exist as geometric objects.

The classification of quantities. Deciding that a quantity is provisional or lump-sum is a contractual decision.

A significant part of a bill therefore derives from no model, and that part is precisely the one producing most disputes.

What this means for a professional

Four rules.

Do not confuse quantity extraction with a bill. The first feeds the second; it does not replace it.

Fix the coding at the outset, in the digital collaboration documents, not when producing the bill.

Treat unmodelled works separately, listing them explicitly rather than hoping they will appear.

Check the measurement rules applied on extraction. A tool applies the conventions it has been given, and those of the framework are not its defaults.

This article reflects professional practice at the date of checking and serves as orientation. It does not constitute legal advice and does not replace assessment of the individual case.

Frequently asked questions

It produces quantities, not a bill. Moving from a modelled object to an item presupposes an attachment decision no software takes alone.

Because classification systems order information without prescribing the works. No automatic bridge exists between classification and bill.

At the start of the project, in the protocol. The choice is documented explicitly, whether standardised, proprietary or project-specific.

The breakdown into items, the choice of unit, the measurement convention and the attachment rule. Those are human decisions.

Measurement and specification in Belgium