12.4. VNAB-SIVI AFS mapping

Based on the article ‘Opstellen eerste VNAB-berichten mogelijk binnen SIVI AFS’ (in SIVI AFS Magazine December 2022).

The iDOSpl@tform of the VNAB (Dutch Insurance Exchange Association) facilitates a user-friendly and structured exchange of data such as object information, mutations and (BIPAR) premium consequences between parties. VNAB wants an easy and standardized exchange of data between the iDOSpl@tform and system houses. VNAB and SIVI set up a mapping between VNAB and SIVI AFS to facilitate this data exchange. AFD 2.0 offers the flexibility to properly model the complexity of the iDOSpl@tform.

First three functions

The iDOSpl@tform does not have a single web service that retrieves all the data at one time/mode, but partial and micro-services that retrieve parts of retrieve data based on criteria in the request. Therefore, after an analysis, it was decided to start the mapping to SIVI AFS with the following three partial functions to begin with:

1. getDossierDetailsByCriteria, part of the larger web service ‘Dossier’ (‘File’). A dossier contains data on one relationship with respect to relating to one or more premium periods (comparable to insurance years), which in turn consist of premium periods (e.g., quarters).
2. getBookableAmountsByPremiumPeriodId, part of ‘PremiumPeriod’. About the premium terms and periods from the partial service at (1), booking data can be can be retrieved with this function.
3. getTotalAmountsByCriteria, part of ‘ObjectList’. About a so-called object list (state of affairs per year/premium period) with one or more objects, the coverage and premium data are recorded. This function retrieves totals per object list, down to the level of details per coverage-currency combination: these include total premium and sum insured, among others.

Expansion of AFD 2.0 to include insurance exchange policies

A consequence of setting up the VNAB mapping is that we have extended AFD 2.0 with elements from the aforementioned iDOS functions, which were not previously in AFD 2.0. These include entityTypes for objectList, premiumTerm and userOrganization, and attributes such as objectListDescription, vnabNumber and amountBasedOnSingleLossLimit. Meanwhile, we have also added the policyStructure-VNAB baseline to AOS, making it possible to create AFD definitions for a VNAB file or exchange policy. The three mapped functions (getDossierDetailsByCriteria, getBookableAmountsByPremiumPeriodId and getTotalAmountsByCriteria) will also become available as AFD definitions.

Next steps

With the implementation of the VNAB – AFD 2.0 mapping for the three aforementioned services and the inclusion of the baseline and AFD definitions in SIVI AOS, SIVI has taken a big step in mapping VNAB messages to SIVI AFS. This aligns with SIVI’s agenda – in developing AFD 2.0 within SIVI AFS – at the data level to support the capture of the complete customer record. In the coming period, SIVI will also provide mappings for other VNAB services.