Creating an AFD-definition requires the following steps:
- Define specifications of a product or service
- Create/manage an AFD-definition using the tooling ‘‘AFD Online Samenstellen’ (AOS, AFD Online Composing)
- Certification and publication of the AFD-definition
- Implementation of the AFD-definition in applications
These steps are described in the remainder of this paragraph.
Define specifications of a product or service
The initial step involves defining the specifications for the product or service. Each function serves as the foundation of an AFD-definition. SIVI has created an Excel template specifically for AFD-definitions, facilitating the description of these specifications. While the use of this template is optional, it is strongly recommended. Its advantages include:
- Serving as a design document
- Ease of coordination with third parties
- Automatic import into AOS
The template is available on the page AFD-definition Standard.
The templates for ‘Volmacht Distributie’ (underwriting agents) are available on the page AOS and for ‘Provinciale Distributie’ (classic distribution) on the page AFD-definitie registratie polis voor de Provinciale Distributie.
The explanation in the text below is based on the use of this template.
Create/manage an AFD-definition using tooling AOS
After the creation of the AFD-definition in Excel, the process of composing the AFD-definition in AOS commences.
AOS generates schemas and validation rules for the AFD-definition. based on the specified inputs, This can be accomplished either manually or partially automatically through the upload of an Excel file (XLSX).With the Excel template, it is feasible to create an AFD-definition comprising multiple subsets of AFD-definitions per function simultaneously.
The creation of an AFD-definition in AOS relies on the following components:
- Entities and the maximum iteration limits
- Attributes
- Attribute properties
- Validation rules, which can be expressed in pseudo-code (simplified English, using only XPath) or through a query expression in XPath (AFD 1.0) or JMESPath (AFD 2.0)
- In pseudo-code (simplified English, only XPath) or a query expression in JMESPath or XPath
Certification and publication of AFD-definitions
Upon completion of the AFD-definition creation process, it’s crucial to conduct thorough checks to ensure accuracy. Errors within an AFD-definition can lead to unnecessary costs throughout the chain. Once finalized, the AFD-definition undergoes certification to verify its compliance with the key principles of AFD. Upon certification within AOS, the AFD-definition becomes accessible in the AOS-register for AFD-definitions. Within the register, there are three visibility options:
- Invisible to third parties
- Visible to third parties but not downloadable
- Visible and downloadable
For more information about this topic, see paragraph Certify/publish.
Implementation of the AFD-definition in applications
Software developers have the option to register for a notification service within SIVI’s AOS environment, enabling automatic receipt of notifications for new or updated AFD-definitions of a specified type, provided the supplier has made the AFD-definition downloadable. Subsequently, software developers can manually retrieve the AFD-definitions or opt for fully automated retrieval using the AOS API provided by SIVI. Leveraging these AFD-definitions, a software developer can, depending on their software capabilities, automatically extract product specifications within the software and consequently, partially or fully automate the configuration or adjustment process.
For more information about the AOS API see the AOS page on the SIVI website.
Post your comment on this topic.