Custom Aquo integration development
Aquo is the Dutch standard for exchanging data in water management. It is maintained by the Informatiehuis Water (Water Information House), and for government bodies it is on the Forum Standaardisatie 'comply or explain' list. Aquo defines which concepts, objects and values you use, so that measurements and management data mean the same thing across water boards, provinces, Rijkswaterstaat, laboratories and consultancies. Appfront builds the integration that lets your own systems exchange data according to Aquo.
What is an Aquo integration?
An Aquo integration ensures that the water data in your own systems has the same meaning as in the rest of the water sector. According to the Informatiehuis Water, Aquo is the Dutch standard for efficient, automated exchange of water data. It consists of three parts: information models that describe the structure of the exchange with objects, domains and their relationships; domain tables with the values you may use and the agreed spelling; and a concept framework with the definitions of the terms. The Aquo website includes the Information Model Water (IMWA), IM Metingen (the measurements information model) and domain tables such as the observation types.
Forum Standaardisatie added Aquo to the 'comply or explain' list on 17 May 2016. The scope is the exchange of data on the management of surface water and groundwater and on wastewater treatment, and the obligation applies to central government, provinces, municipalities, water boards and the (semi-)public sector. The list includes version Aquo 2026-06, and because the Forum rates its management as excellent, new versions are added to the list without a separate assessment. The exchange models are based on NEN 3610, and alignment with SIKB0101 has been requested for measurements. The Informatiehuis Water is a joint programme of Rijkswaterstaat, the water boards and the provinces.
We build custom solutions because measurement and management systems use their own codes, units and object names. A parameter, a measurement location or a structure has a different name in your system than in the Aquo domain tables. The integration records that translation once, retrieves new versions of the domain tables and flags values that are no longer valid. When Aquo is updated, as with the 2026-06 release, you can see which codes in your data are affected. We will determine with you in the first step which information models and exchanges apply to you.
One meaning
Your codes mapped to the domain tables.
Up to date
New versions spotted automatically.
Checked
Invalid values flagged.
How we build your Aquo integration
We start with your data: which systems hold measurements, objects and management data, who you exchange them with and where conversion is currently done by hand. We then create a mapping of your codes and fields to the Aquo information models and domain tables, which your information managers can review. We first build the exchange that takes the most conversion work, for example measurements from a laboratory or data for a national report, and test it with real data. Other flows follow once that works well. After that, we keep the integration up to date when Aquo releases a new version or your systems change.
Systems, partners, conversion work.
Codes mapped to the domain tables.
Tested with real measurements.
Go-live, monitoring, and maintenance when new versions arrive.
What an Aquo integration actually does
The components below appear in almost every Aquo integration. Which ones you need depends on your role in water management and on the data you exchange.
Mapping
Fields mapped to the information models.
Domain tables
Codes translated and up to date.
Validation
Invalid values flagged.
Exchange
Water data in Aquo format.
Locations
Measurement points and objects unambiguous.
Log
Every exchange traceable.
Who we build an Aquo integration for
The integration is intended for organisations that hold water data in their own systems and regularly need to exchange it with other parties in water management. The more sources and recipients you have, the more it delivers.
Water boards
Management and measurement data.
Provinces and municipalities
Groundwater and sewerage.
Laboratories
Analyses in Aquo format.
Software builders
Your software package on Aquo.
Technology and integrations
This page is about exchanging water data according to Aquo. If you are looking for software for a water authority in general, see custom water authority software; for recording measurements at bathing sites, there is the bathing water measurement log. If your data concerns the subsurface, such as groundwater monitoring, read about the BRO integration, and for geodata about the PDOK integration. You can read about our approach on building software.
Why choose Appfront for your Aquo integration?
Measurements that are converted again for each recipient, a parameter code with a different name in two systems, or an exchange that fails because a value comes from an outdated domain table all cost time and make data less reliable. That is what we build around: a mapping you can review, domain tables that stay up to date and validation before every exchange.
Reviewable
Mapping recorded per code.
Up to date
Every Aquo version followed.
Visible
Deviations in the log.
Security and privacy in an Aquo integration
Water data is usually not personal data, but it can still be sensitive, for example data on structures, discharges or companies. The integration uses only the data needed for the exchange, with a dedicated account that has exactly the permissions required for it, and records every exchange with its time and result. If the data includes information about individuals, such as a contact person or a parcel owner, the GDPR applies.
The integration runs in a European data centre, with encrypted connections and storage. Keys and certificates are kept secure and are not visible to staff. We agree with you in advance which data is shared with which partner.
Frequently asked questions about an Aquo integration
Questions that information managers, laboratories and software suppliers in water management ask before getting started.
Aquo is the Dutch standard for exchanging data in water management. It consists of information models, domain tables with permitted values and a conceptual framework. The Informatiehuis Water (Water Information Centre) develops and maintains the standard.
For government bodies and the (semi-)public sector, yes: since 17 May 2016, Aquo has been on the Forum Standaardisatie 'comply or explain' list for exchanging data on surface water, groundwater and wastewater treatment. For laboratories and consultancies it is not a legal requirement, but their clients often ask for it.
Lists of the values you may use in an exchange, with the agreed spelling, such as the observation types. They are updated in update rounds. An integration keeps them up to date and flags codes in your data that are no longer valid.
The Forum Standaardisatie list includes Aquo version 2026-06. Because its management has been rated excellent, new versions are added to the list without a separate assessment. We establish which version your recipients expect in the first step.
The Informatiehuis Water, a collaborative programme of Rijkswaterstaat, the water authorities and the provinces. Users can submit change proposals; these are assessed by the Aquo team, with advice from the Aquo Expert Community and technical working groups.
The integration checks every exchange against the domain tables and puts a record with an unknown or outdated value on an error list, together with the reason. You see which measurement and which code is affected, and can have it reprocessed after correction.
For organisations with their own systems that regularly exchange water data with several parties, or whose software does not support Aquo at all or only in part. If you only exchange the occasional file, a manual conversion is usually enough.
Want to exchange your water data in line with Aquo?
Tell us which systems you use and who you exchange data with. We will show you how an integration takes over the conversion to Aquo.