From data collection to reporting - experiences and boundary conditions for an aggregating reporting system Michael Nagy Umweltbundesamt Wien Experience with “WasserBLIcK” and interesting aspects in the context of WISE Brussels, 15 February 2005

Purposes for reporting Common vision Information Users Policy Effectiveness Public M S EEA Intern. Conv. Useful Information COM SoE Trends An. Data treatment / aggregation Compliance checking Member States Data Purposes for reporting Drivers for data collection © DG ENV

Drivers for data collection – Austrian view Correct implementation of EU Directives? etc. WasserBLIcK etc. Heterogeneous Homogeneous Aggreg. Federal Ministry + related institutions Overview for political measures, etc. Data for every day use Data for reporting purposes Regional Aut. Regional Aut. Emission values according to national law? Regional Aut. DA DA DA DA DA DA DA DA DA Process optimisation Operators of UWWTPs and IWWTPs

Structural frame Heterogeneity on every level Contact points (persons) for each level needed Quality assurance on each level required Problems with data aggregation Changes lead to financial and legal consequences Drivers for data collection: local / regional / national water management  not reporting!

Example WFD 2000/60/EC Identification of pressures (Annex II 1.4); Data which should be collected and maintained by the Member State Significant point sources Significant diffuse sources Significant water abstraction Significant water flow regulation Significant morphological alterations Other significant anthropogenic impacts Land use patterns

Terms which are not defined in WFD Example WFD 2000/60/EC Terms which are not defined in WFD POINT SOURCE DIFFUSE SOURCE SIGNIFICANCE CRITERIA Point sources Diffuse sources

Austrian Example – Established Data Flow Data input by different regional bodies Data transfer via email or floppy disc Data collection and validation by regional authority Internet access Data transfer via email or floppy disc Data storage and evaluation by the BMLFUW / Umweltbundesamt

Austrian Example – Legal basis Austrian Water Act (2003) WISA – general electronic reporting system EMREG / UWWTP-database – point sources / diffuse sources Ordinances: Detailed (legally binding) description of „why“ „what“ „how“ „who“ „when“

Austrian Example - Conclusion Answering of the question: What do we need to know? Legal basis Data policy – binding rules Administration of data flow Quality assurance Appropriate technical solution for electronic data exchange

General conclusion – Emissions (Env.) data is usually a by-prduct Economic needs (e.g. accounting of treated waste water volumes or pollutants) Operation of treatment plants (measurements for finetuning of processes) Enforcement data: Permitted water discharges Surveillance monitoring (water inspectors, self-monitoring) ... Involvement of many national institutions required: Authorities NSI Universities Operators Environment Agencies ...

The role of the database and the applications in the reporting system A reporting system needs clear rules for responsibilities, reporting deadlines and a common understanding of the relevant terminology. A database and the related applications are important tools, but can only work properly, once the following questions are clarified: Why? What? How? Who? When?

Thank you very much for your attention! Michael Nagy