Asset data according to IMBOR Exchanging data with contractors and software packages Checked before it is used

Custom IMBOR integration development

Appfront builds integrations with IMBOR, the CROW information model for managing public space. If you record asset data according to IMBOR, you can exchange it with contractors, consultancies and other asset management packages without converting it. We connect your own systems to the model, so data on trees, paving, lighting and water keeps the same names and properties.

What is an IMBOR integration?

IMBOR is the Information Model for Managing Public Space (Informatiemodel Beheer Openbare Ruimte) from CROW. It is an open standard that defines what objects in public space are called and which data belongs with them, from trees and paving to lighting and watercourses. IMBOR 2025 was released on 14 July 2025, as a database and as linked data, with a SPARQL endpoint for technical users.

In the new version, IMBOR is better aligned with other standards, such as NEN 2660-2 and NEN 3610, and with the link to BGT-IMGeo. For urban water there is a sub-model that connects to the GWSW of Stichting RIONED. Even so, many asset managers still work with their own names and properties. Data that a contractor delivers after a project then has to be converted first, and that is often done by hand.

We build custom solutions because asset managers differ: which disciplines, which software packages, which custom properties and who supplies the data. We look at how your data relates to IMBOR in the first step, together with you.

One language for asset management

Your data translated into the IMBOR object types.

Exchange without converting

With contractors, consultancies and other packages.

Checked

Against the model, before data is used.

How we build your IMBOR integration

We start with your assets: which disciplines, which systems, which custom names and properties, and who supplies data. Then we record how your data relates to IMBOR. We often start with one discipline, such as green space or paving. Others follow once the first is running well. That way you quickly see what the integration delivers. Where your own data doesn't fit IMBOR, we show what is missing and what you can add.

1
Assets mapped out

Disciplines, systems and custom properties.

2
Translation to IMBOR

Your data alongside the object types of the model.

3
Building the integration

Exchange and checks against the model.

4
Go-live and maintenance

Go-live, and maintenance for new versions of IMBOR.

What an IMBOR integration actually does

The components below appear in almost every IMBOR integration. Which ones you need depends on your asset base.

Object types

Your objects mapped to IMBOR.

Properties

Attributes and values.

Validation

Checked against the model.

Exchange

With contractors and software packages.

Map

Together with BGT-IMGeo.

Log

Every delivery recorded.

Who we build an IMBOR integration for

The integration is intended for managers of public space and the parties who work for them. The more deliveries and software packages involved, the more an integration delivers.

Municipalities

Many disciplines and packages. One shared language matters most.

Water authorities and provinces

Large asset bases. Exchange is the core.

Contractors and consultancies

Data after a project. Handing over properly matters.

Software suppliers

A management package. Connecting to IMBOR is the core.

Technology and integrations

This page is about integrations with IMBOR. For the map layer, see our page on the BGT integration, for sewerage our page on the GWSW integration, and for reports our page on public space reports. You can read about our approach on custom software development.

IMBOR 2025 Linked data (RDF) SPARQL Object types and attributes BGT-IMGeo GWSW NEN 2660-2 NEN 3610 Management packages Log

Why Appfront for your IMBOR integration?

Data that has to be converted again with every delivery costs time and gets lost along the way. That is what we build on: one language for your asset management, exchange without conversion, and a check against the model before data is used.

One language

The same names in every system.

Properly delivered

Deliveries checked.

According to CROW

The model stays leading.

Security and privacy in an IMBOR integration

The integration processes data about objects in public space, and sometimes about reports and contracts. Access credentials are stored encrypted and used only by the integration, and every delivery is logged.

The integration runs in a European data centre, with encrypted storage and daily backups. We record the processing in a data processing agreement, and you decide who has access to the log.

Frequently asked questions about an IMBOR integration

Questions that managers and their partners ask before getting started.

IMBOR is the Information Model for Public Space Management (Informatiemodel Beheer Openbare Ruimte) from CROW. It defines what objects in public space are called and which data belongs to them, so that managers, contractors and software packages speak the same language. A tree or a lamp post then has the same name and the same properties everywhere, regardless of who recorded the data.

IMBOR 2025 was released on 14 July 2025. It is better aligned with NEN 2660-2, NEN 3610 and BGT-IMGeo, has a sub-model for urban water that aligns with the GWSW, and is also available as linked data.

The BGT is the map: which area is where. IMBOR describes the managed objects and their properties. They belong together, and IMBOR 2025 has updated its link with BGT-IMGeo. In the integration we use them together, so that an object on the map and in your management data is the same thing.

Not necessarily. Often your own system stays as it is, and the integration translates your data to IMBOR on exchange. Where that is not possible, we show you what needs to change. This can be done per discipline, so you don't have to tackle everything at once.

Yes. A delivery is checked against the model before it enters your system, with a list of what is missing or incorrect. The contractor gets that list back, so they can complete it before the project is closed. This brings your asset base back in order after every project.

We adapt the translation to the new version and show you which objects and properties change. You decide when to switch, and until then the integration keeps working on the current version.

For municipalities, provinces and water authorities with multiple packages or many deliveries, and for contractors, consultancies and software vendors who want to connect to IMBOR.

Is your asset management data structured according to IMBOR?

Tell us which systems and disciplines you work with and where data is currently converted by hand. We'll show you what the integration would look like.

Edit content