2. Background

Context

In the past, many parties used AFD XML templates to share service specifications or record data. Business rules regarding correct use were supplied separately through, for example, an Excel or Word document. This old way of working, however, reduced the uniform interpretation of product definitions and led to errors, delays in processing operations and extra costs.

The AFD-definition Standard focuses on standardizing (unifying) several aspects of the definition of services and/or products. The goal is to ensure that data storage and the exchange of messages between partners in the insurance industry take place unambiguously. This standard can also be used to define a fixed structure for business rules (calculation or product rules). It is suitable for use by all parties within the insurance industry. More information about structures in various situations is available in manual SIVI All Finance Standard.

To support the AFD-definition Standard, SIVI also developed a standard tooling ‘AFD Online Compilation’ (‘AFD Online Samenstellen’ or AOS) for creating AFD-definitions. More information is available in the section Tooling for creating AFD-definitions in this manual and on the AOS landing page on the SIVI website.

The AFD-definition Standard focuses on two areas where product definitions play a major role: registration and services. Registration defines the way data (e.g. contract data) is stored in the database. Services define the use of functions: both the call of a function in a request and the result of a function in a response.

Examples of specifications that you can draw up with the AFD-definition Standard:

• Storing contract data for a motor vehicle
• Storing acceptance rules for a product
• A service calling a function: e.g. newContract_request
• A service as a result of a function: e.g. newContract_response
  

Effects

The use of the AFD-definition Standard for messages improves the data quality of these messages. The lower failure rate of these messages due to less incorrect or incomplete data will lead to more efficient processes in the distribution chain.

Effects of implementation of the AFD-definition Standard:

• Simplification of implementations
  Developers can (partly) automate the design of products by the use of standards in combination with a wide availability of software tools. This can save costs and prevent errors.
• Improvement of data quality in messages and databases
  The machine-processable specifications make it possible to check data during storage and/or the handling of services.
• More user-friendly dialogs
  Improved handling of screen dialogs through expanded options for specifying controls. This will ensure better user interaction and, consequently, better data input quality.
• More efficient implementation of processes
  AFD definitions enable flexible and efficient configuration of specifications in the software, resulting in a reduced time-to-market for implementations and changes.