1. Integrated register of reported pollution (IPPC+) Integrating polluter-to-government reporting flows (IRZ) Jiří Hradec Ministry of the Environment of the Czech Republic NATO SCIENCE PROGRAMME in conjunction with the Carnegie Bosch Institute ADVANCED RESEARCH WORKSHOP Life Cycle Analysis for Assessing Energy and Environmental Implications of Information Technology

2. Currently polluters have to report on their emissions, wastes, discharges etc. - 7 laws, 7 processes, 7 places to report to, 5 different dates Czech Act No. 76/2000 on Integration pollution and prevention control (IPPC) and Integrated pollution register (IRZ) fixes reporting obligations. THE GOAL: - to facilitate unified approach for all the economic subjects liable to reporting. - to save money and effort on both sides, increase availability and transparency - to ensure comprehensiveness of information about pollution and sources - to provide credible information to decision makers, the public and international reporting Political and technical background 2 JHr

3. 3 Integration of the current topic information systems: 1.Clear standpoint of the majority of IT staff 2.Easiest to understand for decision makers (let‘s buy some hardware!) 3.A great lure for IT companies EAI, WS, … IRZ Water Waste Discharges ? IT oriented approach – database integration

4. Integration of the current topic reporting processes: 1.The decision makers unfamiliar with process management and reengineering 2.Requires thorough process analysis 3.Anticipates process optimization JHr 4 Integration of reporting processes Reporter a factory, facility operator, etc Topic Information Systems Data available for further processing Desk officer Receives the report Portal Apply forms, registration, security IRZ Validation, verification, registration

5. The process of IRZ has been characterised by: -Transparency -Availability -Use of quality measurement -Traceability -Year-to-year and subjects in neighborhood comparison -Support of knowledge management and processing + technology database JHr 5 Contents of the IRZ Registration - A comprehensive list of reporters, reports and values reported - Nowadays it takes weeks to find all the information we have on a specific subject Contents verification - Any information reported must be verifi(able)ed - E.g. reported emissions has been checked by environmental inspectorates Validation of the subject - Owner‘s identity must be verifi(able)ed - E.g. facility changed owner during year

6. The technology is evolving quickly. XML / SOAP / WSDL / UDDI seems to have best value to cost ratio. Web services within IRZ: -Broker handles XML requests and routes the data to services -WSDL described services in UDDI catalog -All relevant information systems SOAP enabled JHr 6 Just a snippet of IT Several tools available -Catalog of data and information sources aka metainformation system (Java+PHP) -Data processing catalog (Java) -XML/SOAP information broker (Java/Perl) -Linguistic analyzer (Lotus Notes) -Map server (ESRI ArcIMS 4.0.1) -XML forms in a freeware XML editor (tbd) -Portal toolkit + PKI (Java) -mapmaker.env.cz, indikatory.env.cz

7. This system has several clear benefits 1. eGovernment means process optimization (and savings) 2.Future reporting obligations can be set up in virtually no time and for a fraction of initial and running costs 3.Data mining, manager information system, support for case hearings, etc. JHr 7 Benefits Timetable:  Feb02 IRZ issue emerged  May03 IRZ process synthesis started  Sep03 IRZ process synthesis completed  Nov03 Commence the programming!  Jun04 First test reports  Jan05 Day-to-day operation, fully staffed

8. JHr 8 Conclusions Why we actually do it? We want to receive exact and credible data (perhaps for the first time) and make our figures valid… Thus we have to: 1. offer reporters the most convenient way of reporting (e.g. both paper and e- version) 2. make everything easy to understand and unambiguous 3. stay as close to the reporter as possible (reuse desk officers at local and regional authorities, use portals) 4. try to verify a majority of the data reported 5. keep the doors open to PKI and other emerging technologies when they become widely accepted 6. rope-in decision makers and reporters 7. not to get excited about IT possibilities!