Integrated pollution and prevention control IPPC

1
Integrated register of reported pollution
(IPPC) Integrating polluter-to-government
reporting flows (IRZ)
Jirí 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
Political and technical background

• 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

2
JHr
3
IT oriented approach database integration

• Integration of the current topic information
  systems
• Clear standpoint of the majority of IT staff
• Easiest to understand for decision makers (lets
  buy some hardware!)
• A great lure for IT companies

IRZ
Water
Discharges
Waste
?
IRZ
EAI, WS,
JHr
3
4
Integration of reporting processes

• Integration of the current topic reporting
  processes
• The decision makers unfamiliar with process
  management and reengineering
• Requires thorough process analysis
• Anticipates process optimization

Reporter a factory, facility operator, etc
Desk officer Receives the report
Portal Apply forms, registration, security
IRZ Validation, verification, registration
Topic Information Systems Data available for
further processing
JHr
4
5
Contents of the IRZ

• 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

• Validation of the subject
• Owners identity must be verifi(able)ed
• E.g. facility changed owner during year

• Contents verification
• Any information reported must be verifi(able)ed
• E.g. reported emissions has been checked by
  environmental inspectorates

• 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

JHr
5
6
Just a snippet of IT

• 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

• Several tools available
• Catalog of data and information sources aka
  metainformation system (JavaPHP)
• 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

JHr
6
7
Benefits

• This system has several clear benefits
• eGovernment means process optimization (and
  savings)
• Future reporting obligations can be set up in
  virtually no time and for a fraction of initial
  and running costs
• Data mining, manager information system, support
  for case hearings, etc.

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
JHr
7
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!
JHr
8