1. 2. Presentation of the reporting tools
12. December 2012,
Workshop on Drinking Water Directive reporting under WISE
atkins_ppt_new-3

2. What to report Electronic XML based reporting 4 schemas:
- 1 covering quality of water for human consumption (article 13)
- 3 schemas covering 1., 2. and derogation (article 9)
All files are to be uploaded in EEA's Reportnet
Next deadline (article 13): 29th of February 2012 (every 36 months) – covering data from 2008, 2009 and 2010

3. Intro to new submission workflow

4. Similar reporting set-up applies to
Water Framework Directive
Floods Directive
Marine Strategy Framework Directive

5. Tools and documents for the reporting
Schema
Spreadsheet (Excel)
Tools (Conversion of data to xml and Desktop validation)
Stylesheet ("Read friendly" output of reported data)
User Manual, v1.0
Reporting Guidances (document 2 and 3)
Ressource page:

6. Ressource page

7. Spreadsheet
The table structures in Guidance Document translated into spreadsheet – in some cases necessary to set a different structure in order to accommodate both one-to-many relations and to simplify the structure.
Structure of the spreadsheet must be kept in order to run the conversion tool successfully
Enumeration lists (drop-down lists) available where appropriate
1 spreadsheet per year
Note:

8. Spreadsheet
14 worksheets covering 8 tables in Guidance document

9. 3 worksheets covering table 6

10. 3 worksheets covering table 6
= ws 1: NonComplianceInformation
= ws 2: NCI_Cause
= ws 3: NCI_Remedial

11. 3 worksheets covering table 6
ws 1: NonComplianceInformation
ws 2: NCI_Cause
ws 3: NCI_Remedial

12. Simplified structure in spreadsheet
(2)Please use codes ‘W’ for waterworks, ‘N’ for network, ‘L’ for legal point of delivery and ‘T’ for tap in domestic installations. It is possible to enter more than one code if different sample locations are used

13. Schema
Schema is defining the required XML structure to be uploaded in Reportnet
Makes it possible to run validation check on data

14. Schema (2)
Annotation text: Explains what is required and/or the data definition of the element – eg. ReportingYear should be reported as yyyy
Dashed line means optional information

15. Conversion tool
Conversion tool: Tool which links to Spredsheet and generates a XML file on the basis of the DrinkingWaterDirective schema

16. Desktop validation tool
Desktop Validation tool: Validation carried out in desktop tool before uploading files in Reportnet
Validates the XML files
Retrieves schema from ReportNet
Accesses QA/QC validation on ReportNet
Same checks and output as ReportNet

17. Desktop validation tool (2)

18. Validation rules
Technical schema validation ensures that numbers are entered as numbers, no characters; required elements are reported, that the XML file is well-formed and so on => all technical rules can be found in schema design
Complex rule validation handles the more complex relations in the XML, e.g. conditional elements that are required on the basis of reported data in other elements => all technical rules can be found in User Manual, Annex A

19. Validation rules (2)
Example of complex validation rule: Conditional element (table 7 Quality Information)
Validation rules are meant to ensure data meet the requirements of the reporting sheet

20. Understanding validation output
=>Technical schema validation
=>Complex rule validation

21. Understanding validation output (2)
Technical schema validation output
The error in line 16 (using Notepad++ will provide line number) says that the number reported as the TotalVolumeSuppliedWater is not an integer (whole number)

22. Understanding validation output (3)
Complex validation

23. View XML output in HTML
In validation tool it is possible to view XML output

24. Submission in Reportnet
Upload XML file into the envelope and name it
CountryCode_DWD[YYYY]_YYYYMMDD
(eg. DK_DWD2009_ )
Run QA
Correct errors and resubmit
Release envelope and cover letter will automatically be generated

25. Questions?

26. Thank you!
atkins_ppt_new-3