COLLABORATIVE_VALIDATION
Validation Steps
Validation is carried out at least once every 12 months.
Evidence
Operational Level Agreement with NATS.
OpMet API service does not own the quality of the underlying observation data, it only owns how it has been filtered and packaged and exposed via an API.
NATS as the London ROC owns the quality assurance of the data it ingests, post processes and transmits to the OpMet service
OpMet API service does not own the quality of the underlying observation data, it only owns how it has been filtered and packaged and exposed via an API.
NATS as the London ROC owns the quality assurance of the data it ingests, post processes and transmits to the OpMet service
Validation
Self validation is complemented by COLLABORATIVE_VALIDATION with operational service consumers. The whole process is subject to EASA oversight.
Validation
Self validation is complemented by COLLABORATIVE_VALIDATION with operational service consumers. The whole process is subject to EASA oversight.
Validation
Self validation is complemented by COLLABORATIVE_VALIDATION with operational service consumers. The whole process is subject to EASA oversight.
Validation
Self validation is complemented by COLLABORATIVE_VALIDATION with operational service consumers. The whole process is subject to EASA oversight.
Validation
A collaborative validation with independent actors is planned in 2022 to compare forecast with real tile observation (satellite imagery).
Validation
WeatherProfile service is running operationally since 2018.
MetSafe has developed an independent validation process used for each service upgrade.
Before operational use, a collaborative validation has been performed with Weatherprofile current users.