An unambiguous code for every building element From BIM model to maintenance In line with the BIM basic ILS

Custom NL-SfB integration development

NL-SfB is the most widely used classification for building elements in the Netherlands. Every building element gets a four-digit functional code, so that an external wall, a heated ceiling or a lift is identified in the same way in every model, every cost estimate and every maintenance system. Appfront builds the integration that uses NL-SfB codes in your own software: coding objects, checking them and making the codes align with budgeting, maintenance and management.

What is an NL-SfB integration?

An NL-SfB integration ensures that the objects in your software have an NL-SfB code and that the code means the same thing everywhere. According to digiGO, NL-SfB is the most widely used classification for building elements; construction and installation companies use it to code layers and objects in BIM and CAD systems and to sort and filter supplier information. Its foundation is the Swedish SfB structure from 1947, which groups building elements by their function in the building. It was introduced in the Netherlands as NL-SfB in the 1980s. The standard was renewed in 2019, adding building services and fixed facilities such as lifts and sun shading, and NL-SfB 2021 followed in 2021. All versions work with four-digit functional codes.

Since 1 April 2026, Ketenstandaard Bouw en Techniek has owned and managed this open standard; before that it was managed by digiGO, which absorbed the BIM Loket. Ketenstandaard is working with Buildwise and digiGO on a single SfB for the Netherlands and Belgium, with NL-SfB 2026 as a transitional release. The codes align with NEN 2767 for condition assessment and NEN 2699 for cost estimates. The BIM basis ILS, the basic agreements for exchanging BIM models, sets out how to use NL-SfB: table 1, only the four-digit notation without brackets, written as NL-SfB with a hyphen. Examples are 21.11 for non-structural solid external walls and 56.83 for heating and cooling ceilings. The code belongs in the IFC file, together with its description.

We build custom because the code is only worth something if every system uses it. In a model, codes are missing or don't match the object: a wall with the external wall code that has been modelled as an internal wall. A cost calculation follows its own breakdown, and a housing association's asset management system uses yet another. The integration reads objects from models and systems, checks whether the NL-SfB code fits the type and properties such as IsExternal and LoadBearing, translates your own breakdowns into NL-SfB and produces overviews per code, for example for a budget or a maintenance plan. An object without a suitable code ends up in a list instead of in the overview.

One language

The same code in every system.

Checked

Code matches the object.

Usable

Overviews per building element.

How we build your NL-SfB integration

We start with your software and your data: which models, cost calculations and asset management systems currently hold building elements, which breakdown each system uses and what you want to do with the codes, such as budgeting, planning maintenance or checking models. Then we place your breakdowns alongside NL-SfB and show where they match and where choices are needed. We first build the coding and checking for one model or one system and have your specialists review the result. Other systems and the overviews per code follow once that works well. After that, we maintain the integration whenever the standard gets a new version.

1
Mapping your data

Models, systems, breakdowns.

2
Comparing

Your breakdown alongside NL-SfB.

3
First model

Coded and checked.

4
Go-live and maintenance

Go-live, monitoring, and maintenance per version.

What an NL-SfB integration actually does

The components below appear in almost every NL-SfB integration. Which ones you need depends on your software and on what you want to do with the codes.

Coding

An NL-SfB code for objects.

Validation

Code matches type and property.

Translating

Your own breakdown to NL-SfB.

IFC

Code and description in the model.

Statements

Quantities per building element.

Versions

Transition made visible.

Who we build an NL-SfB integration for

The integration is intended for organisations that record building elements in multiple systems and currently work with separate translation tables or manual coding. The more models, projects and objects you have, the more it delivers.

Contractors

Cost calculation and model aligned.

Installers

Installation components coded.

Housing associations

Management per building element.

Software builders

NL-SfB in your software.

Technology and integrations

This page is about the NL-SfB classification of building elements. If you want to import specifications following the STABU system, take a look at our STABU integration; for exchanging building models themselves there is the IFC integration, and for the classification of technical products the ETIM integration. If you inspect buildings according to NEN 2767, also take a look at the inspection app for condition assessment. You can read about our approach at building software.

NL-SfB table 1 BIM basis ILS IFC IsExternal and LoadBearing NEN 2767 NEN 2699 SfB viewer Cost calculation and budgeting Maintenance and asset management software Log

Why Appfront for your NL-SfB integration?

A model where half the objects have no code, an estimate that follows a different structure from the model, or a maintenance plan that names building elements differently for each complex costs time on every project and produces figures that nobody can compare. That is what we build on: NL-SfB as a fixed structure, checks that show where a code does not fit, and a log in which you can see what has changed.

Unambiguous

Every building element, the same code.

Comparable

On projects and complexes.

Kept up to date

Keeps pace with new versions.

Security and privacy for an NL-SfB integration

The classification itself is public, but your models, estimates and asset management data usually are not: they concern projects, prices and buildings belonging to your clients. The integration uses NL-SfB as a reference, keeps your data in your own environment and records every change with the time and the user. Personal data is rarely needed for this; where it does occur, such as with residents or project members, the GDPR applies.

The integration runs in a European data centre, with encrypted connections and storage. Access to model servers, CDEs and asset management systems goes through protected accounts that are not visible to staff. We agree with you in advance who may change codes and who may approve a mapping to your own classification.

Frequently asked questions about an NL-SfB integration

Questions that contractors, installers and property managers ask before getting started.

A classification for building elements, based on the Swedish SfB structure from 1947. Each building element gets a four-digit functional code, such as 21.11 for non-structural solid external walls. According to digiGO, it is the most widely used classification for building elements in the Netherlands.

Since 1 April 2026, Ketenstandaard Bouw en Techniek has been the owner and manager of NL-SfB. Before that, it was managed by digiGO, into which the BIM Loket was merged. Ketenstandaard is working with Buildwise and digiGO on a joint SfB for the Netherlands and Belgium.

According to the BIM basis ILS, you use table 1, only the four-digit notation without brackets, and you write NL-SfB with a hyphen. The code goes into the IFC file; exactly where depends on your software. Also export the description of the code.

STABU describes the work in a specification, in chapters and sections. NL-SfB divides a building into building elements. They complement each other: an integration can link a specification item or estimate line to an NL-SfB code if your systems use that structure.

IFC is the open format in which building models are exchanged. NL-SfB is the classification that is attached to objects in such a model. An IFC integration handles reading and writing models; an NL-SfB integration makes sure the codes in them are correct and usable.

The BIM basis ILS asks for the most recently published version. Ketenstandaard's SfB viewer includes NL-SfB 2019 and 2021, among others, and NL-SfB 2026 is the transitional release towards a joint SfB for the Netherlands and Belgium. The integration shows what a transition means for your objects.

For organisations that record building elements in several systems, such as models, estimates and asset management systems, and for software vendors who want to support NL-SfB in their package. If you only occasionally code a model in your BIM package, the function in that package is often enough.

Every building element, the same code, in every system?

Tell us which models and systems your building elements are in and what you want to do with the codes. We will show you how an integration codes and checks them according to NL-SfB.

Edit content