How is the quality of data documented at various service lifecycle stages?
How do I document quality of data in a service definition?
The items used to describe quality of data vary between information domains. They may include, for example, accuracy, resolution and precision.
A service definition sets out community agreed requirements on the service to be implemented. The community can be strict or less strict with the requirements. Therefore, the quality of data requirements can:
- be left or
- give a minimum to be ensured by all service providers either by including requirements or making reference to them.
If the requirements are left at the abstract level, implementers have freedom to define their own concrete quality of data.
Requirements may be found in:
- ICAO documents. For example, "The data shall meet the data quality requirements outlined in the PANS-AIM Data Catalogue".
- EU regulations. For example, "The aeronautical data offered by the service shall satisfy the applicable sections of Commission Implementing Regulation (EU) 2017/373 of 1 March 2017".
- community agreed requirements such as AIXM coding guidelines
How do I document quality of data in a service description?
There is no requirement to document the quality of data in a service description. However, it can be added if needed and help inform the negotiations of the "formal arrangement" in a similar way to the quality of service parameters as explained at Formal Arrangements - Service Level Agreements.
SWIM-SERV-190 Source of information is used to record modifications that have happened to the information.