Improving the reporting process WG DIS 23./24.10.2014 B. Werner, F. Nery (EEA)

Current reporting process Long and cumbersome process including a lot of manual work. It takes months from the time the MS uploads the information until it can be used. COM/EEA regularly comes back to MS with comments and requests for corrections weeks or even months after the submission.

Objectives Reduce the manual processing of information Reduce errors, improve the quality of MS submissions Reduce time from reporting to effective use of information Provide swift automated feedback to data reporters on quality of their data  using strict agreed quality rules and criteria Further improvement of the user-friendliness of the system for all users

Process up to the confirmation letter Strict and clear rules for QA/QC routines applied before final release – some critical information missing can block the release (see QA document) MS during submission should apply these routines and get derived products as immediate feedback to correct (iterative) before final release. HTML sheets and summaries presenting information in a readable and printable format Tables and charts with basic statistics If possible, interactive maps where the information submitted is displayed, possibly alongside information already available in the system (other RBDs and/or MS).

Process up to the confirmation letter The different QA routines and the way and timing (hours or couple of days) they are fed back still needs to be established in terms of process from immediate feedback and the elements included into the confirmation letter. An access data base to support the data provision will still be provided as an option if MS wish so. Quality control routines are the same as in Reportnet GIS information needs to be subject to automated QA/QC. Therefore spatial data need to be delivered in GML. Further specifications are needed on possibly conversions

Production and use of EU data base After release, the import of information (tabular & spatial) into the EU data base should be automated and ASAP available to develop the end products timely Resubmissions needs to be handled strictly to ensure that the automated processes can process them smoothly (i.e. replace the old information with the new one). A user-friendly front-end will be developed for the EU database with some standard queries built-in and allow the user to filter and select relevant data.

Thank you for your attention