Managing data in our Pollution Inventory Alex Hole Assessment & Reporting Advisor

Overview  Diffuse pollution  Guidance materials  Process for collection and verification of data  Software used for data collection and verification  Confidentiality issues  Pulling together the report for EPRTR

Diffuse Pollution  NAEI – National Atmospheric Emissions Inventory  Air emissions only  Information for the whole of the UK   Run by a consultant on behalf of our ministry of Environment (Defra)  Use data on fuel use, data from environment agencies to map emissions  No diffuse water data as yet

Guidance and tools for operators [1]  For waste operators:  GasSimLite for modelling landfill gas releases  Landfill leachate estimator tool  Landfill reporting guidance  PI guidance for waste treatment and transfer facilities  Oil estimator tool for waste treatment stations  For STWs:  PIEDC guidance for WIA operations  STW estimator tool

Guidance and tools for operators [2]  Combustion  Petroleum  Iron & Steel  Cement & Lime  Incineration  Paper & pulp  Chemicals  Intensive Agriculture  Hazardous waste transfer stations  Mines & quarries  Waste treatment operations  Used oil treatment  Food & drink  Not statutory/mandatory - designed to help quantify releases where site-specific data is not available  For other industries:

Guidance and tools for operators [3]  Sector guidance notes developed in collaboration with industry  Sector guidance should have lists of relevant substances and methodologies for calculating emissions where no monitoring data is available  Some sectors we include basic instructions on how to complete the form (e.g. Agriculture)

Guidance and tools for operators [4]  General:  PI reporting guidance  PI reporting codes  Guidance on using PIEDC (electronic reporting system)  PI reporting forms (MS Word & Acrobat)  All general and sector specific guidance is available from the PI website at:

PI process - a summary  Issue of PI Notices  Issue of reminder letters by 20th December  PI returns obtained from industry operators by 28th February  Paper forms entered on to PIEDC by 15th March  Data is verified by site officers by the 5th April  Overview audit carried out between 5-20th April  Identified problems resolved by 30th April  Final Data ready by 15th May

How is data checked & verified ? During data entry:  PIEDC system triggers ‘check flags’ highlighting potential data errors Following data entry:  Returns verified for accuracy by regulatory site officer/team using knowledge of site  Overview audit of PI dataset by regional data teams and feedback to PI contact points  National overview of PI dataset by national team and any further feedback to PI contact points

Why do Check flags occur ? Reasons why they are generated:  Emissions high compared with previous year [>50% of the value]  Emissions are low compared with previous year [<50% of the value]  Emission high compared with threshold [factor of 5 times or more]  Incorrect units selected - factor of 1000 different  ‘brt’ entered compared to an emission the previous year  Emission value entered below reporting threshold

Dealing with Check flags  Check flags must be investigated before removal  Electronically submitted forms should include explanation by operator in ‘qualification notes’ box  Chance to clear at data entry stage  Outstanding check flags should be cleared during verification  Status of PI return cannot be changed to ‘Verified’ with check flags remaining

Verification of data The verifier should:  Clear outstanding check flags  Check all expected substances have been reported  Follow up ‘qualification notes’ made by operator  Use local site knowledge to determine whether changes in releases are valid  Provide commentary on significant changes or other changes in ‘Inspectors’ comments’ box  Use ‘Verification Checklist for Inspectors’  Complete verification by 5th April

Generic issues for all returns Incorrect units entered:  Check whether kg, tonnes etc.  Check PI reporting requirements are followed  Waste transfers must always be entered in tonnes Common problems include:  Non-methane volatile organic compounds [NMVOCs] must be reported as ‘total mass’ not ‘total carbon-equivalent mass’  CFCs, PFCs, HFCs, HCFCs & halon must be reported as total mass

Reporting of all expected substances Indicative list of substances by sector:  Lists substances you would expect to see released by sector to air/water  Indicative list - for guidance only to identify that site has reported appropriately LCPD data:  reported in addition to PI NOx/SOx is appropriate

‘Inspectors’ comments’ box  Use for explanation of significant changes in emissions For example as a result of :  Change in operating conditions  Improved abatement technology  Changes in raw materials  Provide as much explanation as possible during verification stage  No explanations could lead to further enquiries at later stages

Verifying returns from waste sites  More detailed handouts provided on verifying PI returns from:  Landfill sites - including information on leachate, landfill gas [GasSimLite] etc.  Waste transfer facilities - including expected release sources, likely releases, estimating releases etc.  Chemical treatment facilities - including likely releases, quantifying releases etc.  Oil recovery operations - likely releases etc

Auditing estimated data  Compare with values from previous years for sanity check  Compare releases with other similar sites/works  Check with appropriate sector experts in area/region

Auditing monitored data  Is monitoring data from a reliable source and technique ?  Have enough concentration values/flow rates been used to generate meaningful annual load ?  How do values compare with previous years ?  Would use of an estimator tool be preferable ?

Commercial confidentiality  Operator can make a claim for confidentiality  Written justification must be provided  28 days from date of receipt to determine  Case by case judgement  For Intensive agriculture, permitting teams were issued guidance and this is being used for PI

What is the PIEDC?  Pollution Inventory Electronic Data Capture  Web based application  ‘Front end’ of the Pollution Inventory database  Data is stored in an Oracle database  Internal and external version of system  Operators enter emissions data onto PIEDC  Paper forms entered by staff onto PIEDC  Approximately 50-60% returns are submitted electronically via the web  Data extracted from the database using an Access database

Details of Installations [1] PPC activities  Name, address, grid reference, EA ‘area’, site inspector details come from PPC permitting system Link between permitting system and PI Manual changes can be made

Details of Installations [2] Non-PPC activities (new EPRTR)  Written to using a list from a third party  Asked to complete information on Name, address, grid reference  For all sites RBD will be calculated using GIS

Demonstration of the PIEDC

‘What’s in your Backyard ?’

The rest of the UK Scotland  PRTR is called the SPRI (Scottish Pollutant Release Inventory)   Bob Boyce in SEPA is the contact Northern Ireland  do not have an electronic PRTR – paper based system  All data will come together for the UKPRTR

Compiling data for EPRTR  Data will be extracted by each country in UK  Only extract data from the database where it meets EPRTR requirements (data collected from PPC activities which goes beyond EPRTR is not included)  Format of data required for the EPRTR is described in the guidance document  EEA will provide a validation tool for EPRTR  Data is entered into validation tool  Any errors in data format will be double checked  Once data passes validation it will be uploaded to website

Alex Hole Assessment & Reporting Advisor