Two-way synchronisation with LV-BRO

In cooperation with Home Affairs, the project to set up a two-way synchronisation between Dawaco and the Landelijke Voorziening Basis Registratie Ondergrond (LV-BRO) has been launched. This project is needed because source holders supply groundwater monitoring wells to LV-BRO outside Dawaco, leading to inconsistent and outdated data. The aim of the project is to investigate what steps are needed to achieve two-way synchronisation, including solutions to problems and cost estimates. The starting point is to work out the GMW registration object first, and other registration objects later. Cooperation with the BRO organisation is necessary to programme the synchronisation and to avoid overloading the LV-BRO. The project provides functionality for data comparison and allows users to modify data.
 
The following are some key problems (issues) that need to be resolved for proper synchronisation between LV-BRO and Dawaco. The first issue is that the data supplier of the wells cannot be modified by agents of the source holder. Currently, corrections and additions can only be made by the data supplier who delivered the well to LV-BRO. This can be solved by enabling the data supplier of the wells to be modified by an authorised user via the source holder portal (BHP). A request for this has already been submitted, but it is not expected to be realised until the end of the year. In the meantime, the BRO Service Desk can modify the data supplier at the source holder's request.

The second issue is that the ObjectID of the source holder is not unlocked. To correctly link the wells in Dawaco and LV-BRO, it is desirable to use the ObjectID of the source holder. This is a field that can be used by the source holder to identify the wells and can prevent duplicates in the measurement points in LV-BRO. Currently, the source holder's ObjectID is not publicly accessible and can only be retrieved by the source holder itself via a secure environment. A solution to release the source holder's ObjectID via the BHP is being worked on, but this is not a high priority and is not expected to be realised until the end of 2023. An interim solution is to use the SOAP interface with PBKI certificate, which allows a data supplier to query the non-public data. However, this solution involves high additional costs.
 
The third issue is that non-public data cannot be retrieved, so correction messages cannot be built. This problem can be solved by bringing back an old functionality where a source holder can request the original data via the BRO service desk to build correction notices. A solution to bring back this functionality is currently being worked on.