TrainER III Compiling a National Emission Inventory using CollectER III

Transcription

1 Compiling a National Emission Inventory using CollectER III ETC/ACC Deliverable 2009, Task CollectER III update and support November 2009 Tinus Pulles The European Topic Centre on Air and Climate Change (ETC/ACC) is a consortium of European institutes under contract of the European Environmental Agency PBL UBA-D UBA-V NILU AEAT AUTh CHMI MET.NO ÖKO TNO REC

2 Authors Purpose of this document Compiling a National Emission Inventory using CollectER III Tinus Pulles This document provides a self training course in emission inventory compilation, using version III of the CollectER software tool, developed by ETC-ACC under the work programme of the European Environment Agency. The software and this document can be downloaded free of charge from ETC- ACC s web site at Version III.01 This version of TrainER is a renewed write-up of an earlier version of the document. It now has been linked to the third generation of the CollectER / ReportER system: CollectER III. 1 Contents... 2 Compiling a National Emission Inventory using CollectER III... 2 Your TrainER for the CollectER III software tool Introduction Background and Objective Legal framework A bit of history The CollectER tool Inventory structure A general approach Dimensions of the Inventory Relational database Data tables Auxiliary tables Building a national inventory using CollectER III An example inventory for Middle Earth Starting a new inventory Data Entry Starting a new inventory cycle Reporting Reporting the Inventory to International Obligations Reporting to UNFCCC and EU MM Reporting to LRTAP and NEC Directive Tools within CollectER III Introduction Preparing the Inventory: QA/QC tools Other reports and overveiws Import of data Using MS Office applications Accessing the CollectER III database directly Road transport Public Power plants This document uses the version of CollectER III as available on November 5 th, 2009 Page 2 of 80

3 7 References Appendix A New inventory using existing CollectER II inventory or inventories Examples for Sources and Source Categories Source 1 Residential heating on Coal Source 2 Residential heating on Oil Source 3 Residential heating on Natural gas Source 4 Residential heating on Wood Source 5 Manure management Source 6 NorthEast Power Plant Source 7 Mordor Steel: Integrated Iron and Steel works Source 8 Road transport Source 9 Public Power plants Page 3 of 80

4 Your TrainER for the CollectER III software tool. This report is part of the documentation distributed to users of the new version of the CollectER software system for air emission inventories and accompanies the distribution of version III of this tool. This report 1) describes the basics of the system as far as necessary and useful for the National Expert as the intended user of the software. 2) provides an overall description of the inventorying process that the software can support. 3) provides step by step guidance for the inventory compilation and reporting, using the CollectER III tool for a virtual country called Middle Earth. This country is derived from the novel The Lord of the Rings by the Oxford storyteller JRR Tolkien. This document replaces an earlier version, published by EEA as Technical Report 33 (November 1999). The document also exploits the new structure and outline of the EMEP/EEA Guidebook, using the new Technologies approach in CollectER. A technology is, where possible, linked to a specific table in the revised Guidebook. With this the CollectER III tool is fully consistent with the approaches and structure of the revised Guidebook. The report assumes that the users has CollectER III, version 2 (dd ##/##/2009) installed. Furthermore the version 3.3 of the CRF Reporter is used to explain the GHG inventopry reporting using CollectER III. We hope that use of this software will greatly facilitate the development of more consistent, transparent and comparable emission inventories in all countries participating in the EEA work programme. On behalf of CollectER III developers team Tinus Pulles Page 4 of 80

5 1 Introduction 1.1 Background and Objective The CollectER tool is designed to help national experts on air emissions to collect the relevant air emission data for delivery to the European Commission and to international conventions. The tool has been developed over the last 20 years, originally as a dbase oriented system CORINAIR94, and later as an integrated set of MS Windows tools. All tools are available free of charge from the ETC-ACC web site at ( 1.2 Legal framework The legal framework for reporting of air emissions consists for all European Union (EU) Member States and other Parties of the following international conventions: o UNECE Convention on Long Range Transboundary Air Pollution (CLRTAP) : SO2, NOx, CO2, CH4, NMVOC, CO, NH3, heavy metals (HMs), POPs and particulkatye matter. o UN Framework Convention on Climate Change : CO2, CH4, N2O, HFCs, PFCs and SF6; Apart from the individual Member States the EU is also a Party to UNECE/CLRTAP and UNFCCC, requiring the EU to report total EU member states emissions. The EU Decisions and/or Directives requiring reporting of emission data to the European Commission are fully consistent with the requirements of both Conventions. Over time sometimes minor but also major (LRTAP) changes were introduced in the formats used for reporting to both UNFCCC and LRTAP. The major ones are: o For UNFCCC this regards the obligatory use of the CRF Reporter tool, requiring a specific XML formatted file for data import from national systems o For LRTAP the original reporting in SNAP categories has been replaced by (successively two versions of) the NFR source definitions This has resulted in a well harmonised system of source category definitions that is used in both conventions. Both conventions require reporting of annual emission inventories (and sinks). In addition CRLTAP requires every five years reporting of geographically disaggregated emissions (in grids of 50x50 km) mainly for use in the EMEP atmospheric chemical transport models. 1.3 A bit of history CORINAIR The CORINAIR system has been developed since the mid 1980s to support participating countries in preparing emission inventories complying with international obligations. The activities of the CORINAIR programme have been closely related and supported by the EMEP Task Force on emission Inventories and Projections (TFEIP). Page 5 of 80

6 The CORINAIR programme consisted of two parts: 1) The development of a standardized methodology, allowing strong harmonization between countries and between the different international obligations. This has resulted in the publication of the CORINAIR / EMEP Guidebook on Emission inventories. A fully revised and restructured version of the Guidebook is underway. The definitions and methods as described in this guidebook are consistent with the methods and definitions as given in the IPCC Guidelines for greenhouse gas inventories. 2) The development of a set of software tools and database definitions that can be used by countries to compile their national emissions inventory and to report to the various conventions from this database. The SYSTEM has originally been developed as a dbase application. Since 1996 this dbase application has been replaced by a set of mutually related MS Windows software tools, using an MS Access database structure. The CollectER III software tool is the third generation in these series of tools. 1.4 The CollectER tool The CollectER / ReportER emission inventory software tools are developed by European Environment Agency (EEA) and its European Topic Centre on Air and Climate Change (ETC-ACC) since the year The objectives of the software are to facilitate preparation of transparent, consistent, complete, comparable and accurate data for emissions reporting procedures in accordance with the requirements of international conventions, protocols and EU legislation. The reporting requirements for two conventions NFR of UNECE/CLRTAP and UNFCCC CRF are supported by the reporting part of the software tools. These reporting requirements are fully consistent with the reporting requirements of the European Union, as these are based on the requirements of the Conventions. The present version CollectER III solves a number of shortcomings related to time series, source categories and geographical resolution usage: 1) Time series The system has originally been set up as an annual system. Meanwhile the reporting formats for UNFCCC/EU Monitoring Mechanism and LRTAP/ NECD have developed to require explicit annual reporting of the full time series. CollectER III now is a multiannual database system 2) Changing reporting formats Over time sometimes minor but also major (LRTAP) changes were introduced in the formats used for reporting to both UNFCCC and LRTAP. The major ones are: For UNFCCC this regards the obligatory use of the CRF Reporter tool, requiring a specific XML formatted file for data import from national systems For LRTAP the original reporting in SNAP categories has been replaced by (successively two versions of) the NFR source definitions Page 6 of 80

7 CollectER III now fully supports these new formats 3) Geographical resolution The CollectER system has originally being designed to follow the CORINAIR praxis, linking to the official European NUTS territorial definitions. The line of thinking behind this was twofold: Activity data on the level of NUTS territorial units might be available to calculate geographically distributed emissions directly The size of NUTS-3 territorial units in Europe is of the same order of magnitude as the geographical resolution of the EMEP grid (50 x 50 km). In practice now only a few countries use the NUTS functionality of the system. CollectER III no longer requires the use of NUTS, although it still is possible to do so. 4) Source sector definitions A few years ago, the LRTAP has decided to replace the original SNAP based source definitions by the so-called Nomenclature For Reporting (NFR) to harmonize reporting with the source category definitions of the UNFCCC reporting (CRF). A second related issue here is that at the 2006 TFEIP meeting in Thessaloniki, the decision was made to also restructure the EMEP/CORINAIR Guidebook to mimic the NFR source definitions, while maintaining the link to the SNAP technology definitions. CollectER III now is based on the NFR/CRF source classification, while the link top the original SNAP is still available. Page 7 of 80

8 2 Inventory structure A general approach The traditional inventory model Most emission inventories estimate emissions for each pollutant using the equation Equation 1 ( AR EF ) Emission pollutant = activity pollutant, activities activity This equation assumes a linear relation between the intensity of an activity AR activity (Activity Rate) and the emission (E pollutant ) for each activity. The emission factor is the proportionality constant EF activity,pollutant. In this classical approach, compilation of a global emission inventory is typically the collection of (time series of) country level activity data and country specific emission factors. Time dependency is implicit in this approach An improved emission inventory model This classical approach of emission inventories as represented by the above formula does not represent explicitly some important aspects of the historical developments of emissions. The same is recognized in the guidance provided by the latest version of the EMEP/EEA Guidebook [1] to produce emission projections. Both in retrospective and prospective (projections) time series of emissions it is crucial to take the technological developments into account. Figure 2-1, based on the algorithm proposed by the Guidebook, schematically indicates how economic, technological and behavioural aspects can be included in the basic approach of an emission estimate:. o The changes in structure and production in the economy is taken care of by the Activity. Activity data include apart from the economic sectors also activities like households and transport. Time series of activity data then model economic growth o Technology is taken care of by the Emission Factor. Each emission factor describes the relation between the intensity of the activity and the emissions for a given technology, used to perform the activity. The replacement of one technology by another is reflected in a changing emission factor. These changing emission factors therefore model technological development of innovation. o The selection of certain technologies for specific activities is modelled by Penetration. Its value indicates the percentage of the activity that uses a specific technology with associated emission factors. The changes in penetration reflect the effects of investments in new or improved technologies. 2 This chapter is based on a TNO report: The Art of Emission Inventorying, soon available via TNO s website Page 8 of 80

9 Economy Technology Behaviour Emission = Activity Emission Factor Penetratio Technologi es n Economic growth Innovation Investments Figure 2-1 The three aspects of estimating emissions: economy, technology and behaviour In our approach we explicitly model the introduction of alternative technologies into the emission inventory by applying the following equation: Equation 2 E pollutant ( t) =, activities technologies ( ARactivity ( t) Pactivity, technology ( t) EFtechnology pollutant ) with activities, t : P, ( t) = 100% activity technology technologies Similar to other studies on time series of emissions, the activity rate is changing over time. In most inventories these data are organised in database tables, providing an activity rate for each relevant activity for each time step (in most cases each year). The temporal resolution of the activity data determines also the temporal resolution of the inventory. In principle the activity data will also be location dependent and the spatial resolution of the activity data will also define the spatial resolution of the inventory. The penetration P activity,technology is modelled as the percentage of the activity that is performed by applying the relevant technology for a specific activity. Penetration obviously is dependent upon the activity and the technology and will change over time when one technology s gradually introduced to replace another. The condition ensures that at all times all of the activity is associated to a technology. Obviously, the spatial resolution of the penetration should follow the spatial resolution of the activity data. By introducing the penetration of technologies into the model, the emission factors become independent of time and location. In this approach, the emission factors for the different substances are a property of the technology and not of the activity. Emission factors also are independent of time and location. The apparent or implied emission factors that are used in the classical approach are related to our emission factors as being the averaged value of all technologies applied for a certain activity. As a result of this these apparent or implied emission factors could be dependent on time and location. To avoid any confusion, we will use the expression emission rate, whenever we refer to these apparent or implied emission factors. Page 9 of 80

10 Every technology could in principle be applied for different activities. Examples of these are combustion technologies that can be essentially the same in public power generation, oil refineries and many industrial manufacturing industries. Compiling an emission inventory now exists of collecting activity data for the full time period under study similarly to the classical approach and building a database of technologies with associated emission factors. The Emission Inventory Model now is completed by the selection of one or more technologies for each relevant activity for every time step in the time series The model consists of three main components: 1) The economic aspect, represented by a table of the activity rates (AR activity ) as in the classical inventory approach; these activity rates will be given for all relevant source activities, for each geographical unit and for every year in the inventory 2) The technological aspect represented by a table of all relevant technologies that can be used to perform the activity in any geographical unit of any year; each technology is accompanied by emission factors (EF technology, pollutant ) for each relevant pollutant 3) The behavioural aspect, linking one or more technologies to each activity in every country and every year. This technology selection (P activity,technology ) could either be a table, listing the penetration of each technology for every activity. It can easily be replaced by a selection algorithm in for instance what-if studies How CollectER III is organised CollectER III is, similarly to earlier versions of the tool, an executable programme, running under the Windows operating system, which manages and compiles an MS Access type of relational database. CollectER III integrates inventory compilation and inventory reporting into one software tool, rather than keeping both separated as was the case in earlier versions. CollectER III directly works into a working database, stored in a subfolder of the CollectER III program folder, usually C:\Program Files\CollectER III\Data. The structure of the database is described below (section 2.3). The working database contains at all moments all latest changes and updates, made with the tool. It is good practice to copy this working database every now and then into a back up file, representing the user s inventory at the time of the back up. This is done by an explicit action of the user ( Back up ) leading to a full copy of the working database into the user s inventory. This inventory is also an MS Access database. Page 10 of 80

11 Backup User s Inventory Restore Working database CollectER III executable Figure 2-2 The relation between the CollectER III working database and the user s inventory. An already available inventory (provided it is in the correct, most recent format) can be Restored. In this case the inventory is copied into the CollectER III working database. A new inventory can be started by Restoring the blank database that is part of the installation package. 2.2 Dimensions of the Inventory An emission inventory should be regarded as a collection of numbers, each having four independent attributes or dimensions: o the (chemical and/or physical) identity of the pollutant or gas that is emitted; o the (economic and/or societal) activity or sector and fuel that causes the emission; o the time dependence of the emission. o the (geographic) location of the emission. These dimensions define the What, Why, When and Where of the environmental pressure resulting from the emissions. This chapter will deal with these four dimensions of an emission inventory separately. 2.3 Relational database As is indicated above (section 2.1) a general approach of an emission inventory activity can be described as in Equation 2. This formula is to be applied for any location that is included in the inventory. Since the summations in these formulas might include a long list of activities, the most suited tool for emission inventorying is a database tool. In agreement with Equation 2 and the scheme as presented in Figure 2-1 three main data tables should be included in this database: 1) A table of activity rates providing information on the intensity of each activity or sector at every relevant location and at every relevant time period; 2) A table of emission factors, linked to a table of all available technologies; 3) A table selecting one or more technologies for each activity in the database. Page 11 of 80

12 Figure 2-3 presents a schematic overview of the relations between these four core tables in the CollectER III database structure. Figure 2-3 Core of the relational database structure in CollectER III The main advantage of using the relational database structure is that it o implements safeguarding against entry of non-existing source categories or fuels o allows for editing names and codes at one single record in the relevant definition tables, rather than in each record in the activities table. Below we will describe some additional issues for each of the main data tables and we will provide some additional thoughts on implementing the dimensions of the inventory. Why: Sources, sectors and fuels As is indicated in the general database structure of Figure 2-3, each activity needs to be given for a source (Source_ID field). As described above, a source is defined by a number of attributes, including a source category and, in combustion sources, a fuel. In a relational database structure this can be implemented by including a table defining all sources in the inventory. Each of these sources links to (see Figure 2-4) o a specific source category, as defined in an additional source categories definition table o a specific fuel, as defined in the fuels table The fuel is obviously not relevant for non-combustion sources; this can be implemented in the database by either defining a dummy fuel, called no fuel or by allowing a null value in the fuels field of the sources table. In Figure 2-4 it is proposed to define the unit in which to express the activity rate in the sources definitions table, rather than in the activity rates table. This would force the inventory compiler to use the same unit for the activity rates for a specific source in all locations and all years in the inventory. Page 12 of 80

13 Figure 2-4 Definition of sources and linking to source categories, fuels and locations; the green Details table is optional In many inventories the compiler might need to stratify certain source categories and fuel combinations into more specific sources (see also section ). In CollectER III this is used to link to the SNAP nomenclature. The easiest and safest way to implement this into the database structure is to add an additional table, defining all deeper details (in this case the SNAP) and an additional field in the sources table, linking to these details. Where: Locations Each source might occur on one or more locations in the database. Similarly as for the sources, the implementation in a relational database includes a link to a separate locations definitions table. This table could define both geographical areas (countries, provinces, municipalities) and point sources. What: Pollutants All emission factors in an emission inventory will be valid for one specific pollutant. Similarly to the other dimensions, this can be implemented by linking each emission factor to a pollutants definitions table (Figure 2-5). This figure proposes to include a pollutant unit in the pollutants definitions table. This unit is the one in which the calculated emissions will be reported. Section 2.5 describes a mechanism that can ensure that units are properly converted when calculating emissions in the inventory. Page 13 of 80

14 Figure 2-5 When: Time periods Emission factors and pollutant definitions It might be wise to also add a table of all valid years (or other time periods) in the inventory and link the time field of the activities table to this table of valid time periods. This would prevent data entry for time periods outside the intended range. 2.4 Data tables Activity rate data For each source the intensity of the activity needs to be estimated for each year in the inventory. Technology and emission factors In this approach the concept of technologies is basically used to organize emission factors in a comprehensive and logical way, ensuring that emission factors for different pollutants are consistent. Emission factors are crucial for any emission inventory and the selection of appropriate emission factors for each technology applied in all activities in the inventory is a major task for the inventory compiler. Some important places to find emission factors are: o Greenhouse gases IPCC Guidelines [2, 3, 4, 5] IPCC Emission Factor Database [6] o Air Pollutants EMEP/EEA Guidebook [1] US EPA, Clearinghouse for Inventories & Emissions Factors [7] These resources provide in most cases sufficient information for the inventory compiler to decide on which emission factors might be most appropriate for application of the inventory under construction. Page 14 of 80

15 In some cases, mainly for large facilities, emission data are directly available from measurements at specific individual sources. Obviously the compiler will wish to use these data in the inventory. To be able to do so, additional background information on the determinants of the emission (activity data, process types, abatement installed etc.) is crucial to smoothly integrate such data into a full inventory. Selecting Technologies The final data table in the proposed database structure provides the link between the activities and the emission factors by selecting one or more technologies that are applied for a specific source in a specific location in a specific year (see Figure 2-3). This table implements the time dependency of aggregated emission factors by allowing the stratification over different technologies to change over time. In the case of a tier 1 estimate for a certain source, no stratification is applied and the full activity is to be linked to one single typical or averaged technology with the associated tier 1 emission factors: the fraction in the Select_Technologies table is set to 100 %. In a higher tier approach one or more specific technologies with the associated tier 2 or tier 3 emission factors are selected. 2.5 Auxiliary tables Apart from tables, defining the dimensions of the inventory and the data tables in the inventory, auxiliary tables in the relational structure can help to screen data during input or import. Units As in all scientific data sets, units for all parameters and values are crucial. Several systems of units are in use throughout the world. The 11 th General Conference on Weights and Measures [8] recommended a practical system of units of measurement for universal use. This system is known as Système International d'unités or International System of Units (international abbreviation SI). We strongly advise any inventory compiler to convert all units in both activity data and emission factors into the SI unit system. Units are used in two important places in the inventory: o to indicate the unit of measure for the activity data o to indicate the derived unit 3 of measure for the emission factors; this derived unit consists of a mass unit, to express the emission, divided by an activity rate unit; the most clear way of including this in the database is to add two unit fields to each emission factor record, defining these two parts of the derived unit. Unit Conversion Units will in many cases be used with different multipliers (the prefixes milli-, kilo-, mega-, giga-, etc. [8]). Conversions will frequently be needed when aggregating emissions over many sources. Furthermore the emission factors might be expressed with other prefixes than 3 Derived units are products of powers of base units [8]. Page 15 of 80

16 the one in which the user wants to express the total emissions. To support such conversions a separate table lists the conversion factors between different units in the units definitions table. Page 16 of 80

17 3 Building a national inventory using CollectER III 3.1 An example inventory for Middle Earth This chapter presents an example inventorying activity in a (non-existent) country called Middle Earth (see Figure 3-1). We take the geography of this country from the story by J.J.R. Tolkien, the Lord of the Rings. A limited number of activities is introduced in this inventory and in the course of this chapter updating these data and adding new sources will be demonstrated. Emission factors are taken from the revised EMEP/EEA Guidebook [1]. Figure 3-1 Map of Middle Earth from Starting a new inventory Open a blank database To start a new inventory, open the CollectER III application. The application will open in a database that was open in an earlier session of CollectER III. In case of a new installation, this is a testing database, used while developing the tool. To start a new inventory, we must start from a new blank database. To do this: o Click File Restore DB Page 17 of 80

18 Comment [TP1]: Update all screen shots with the latest version In the open dialog find the Blank_CollectER_III.mdb database, which is stored ion the Data subdirectory of the program folder (by default installation this is C:\Program Files\CollectER_III\Data). Since this will delete all data in the current database, warnings will be shown. Accept these warnings and a new blank CollectER III database will be available. Select your country from the list of ISO 2 codes, shown in the popup window. Since Middle Earth is not an existing country, there will be no matching entry in this list; you can select any country code in this case. The CollectER III window will look like: Page 18 of 80

19 Looking at the Source filter tabs, you will notice that you now have available all NFR/CRF source categories (Categories tab), all existing SNAPS (Details tab) and fuels (Fuels tab). Locations are not yet defined. To be able to start entering data a location should first be defined. Define years To be able to use the database, at least one inventory year must be defined. This can easily be done by clicking the Edit Add a Year menu item and define the year(s) of the inventory in the dialog that opens. In this example we define the years 2000, 2001, 2002, 2003, 2004 and 2005 by typing each year in the New Year box and clicking OK. When ready: click the Cancel button. The years will now be visible in the Activity rates section of the window. Define locations To define locations, ensure that the Locations tab in the Source filter area of the window is selected. o Right click the Locations entry in the Locations tree and select Add. A small dialog window will open: o Enter MI as the location id and Middle Earth as the location name. o Click Save; the Locations tree will now show the entry for the country Middle Earth Page 19 of 80

20 o Select the new entry, right click it and add a location for all area sources a location for all point sources as shown in the following screen dump. LOCATIONS 3.3 Data Entry In earlier versions of the CollectER system, the user had to apply the EU NUTS geographical codes. In this version this is not obligatory anymore. The user can define any geographical distribution he or she wants. There however must be at least one entry in the Locations tree. In this example we will make a clear split between area sources and point sources. For the area sources we will use the national total only. We define a separate geographical entry to contain all national level emission estimates and one to contain all individual point sources. The CollectER III tool now also allows for more than one country in the database. An additional country can easily be added by defining a new entry at the highest level of the tree (Locations). The database now is ready for data entry Area Sources We will enter a time series of emissions data for residential heating in the country. Data entry for area sources includes: o Defining the source Page 20 of 80

21 o Adding activity data o Defining or selecting the technologies and emission factors Define a new source SOURCE 1 RESIDENTIAL HEATING ON COAL To define a new source, do the following: o Right click in the Source list area of the window and select Add source. The source definition dialog will open. o In the Locations tab of this dialog, select the Middle Earth Area sources location, as shown below. Expand and/or collapse the branches in the tree if needed by clicking the small + or buttons in the tree. o In the Categories tab select 1.A.4.b (residential), to link this source to this reporting category o In the Details tab select Residential other equipment o In the Fuels tab select 103 Sub-bituminous coal. o You can add any comments to the field at the bottom of the window. The new source definition window now should look like: Page 21 of 80

22 o Click Save SOURCE 2 RESIDENTIAL HEATING ON OIL SOURCE 3 RESIDENTIAL HEATING ON NATURAL GAS SOURCE 4 RESIDENTIAL HEATING ON WOOD To add a source in the same category with another fuel, you can use the Add source from menu item. This will copy the selected source and enables you to change at least one of the characteristics. You could add: o Residential heating on Gas oil, Natural Gas and Wood and Wood waste The new sources are now defined in the database and ready for data input. First we will enter activity data (section ) and subsequently the technologies and emission factors (section ). Finally we will calculate the emissions from this source (section ) Entering activity data Entering activity data is rather straight forward. Simply select the source or sources where activity data are to be entered in the Source list of the window. The Source list can be filtered by using the Source filter functionality. In the screen dump below all sources in source category 1.A.4.b are selected and shown in the Activity rates list. Values in this activity rates list can be entered by simply clicking the relevant cells in the grid and enter the data. Double clicking a grid cell provides a bit more functionality. It allows adding specific comments with each data entry. In the screen dump below this is used to indicate that the value for gas fired residential heating in 2002 is an expert estimate, using a coarse interpolation. This dialog also allows for entering a so-called notation key. Page 22 of 80

23 You could enter the values as indicated below. Once activity data are entered, visual inspection is available, using a simple graph function by cl;icking the Graph button. The graph will include all sources selected from the Source list Technologies and emission factors Residential heating, using coal For the technologies applied in Middle Earth for residential heating stoves, fired with solid fuels, we use the technology as defined in the revised Guidebook and reproduced in Table Page 23 of 80

24 3-1 and the associated emission factors. To include this technology in the database do the following: o Click the Root data Technologies menu item and the technologies dialog will open. o Right click in the Technologies list of this dialog to open the Technologies input dialog and complete it as indicated in the screen dump below o Click Save to store the newly defined technology. o Select the newly defined technology and right click the Emission Factors area of the dialog. Page 24 of 80

25 Table 3-1 Tier 2 emission factors for source category 1.A.4.bi, boilers burning solid fuel (except biomass) (Table 3-15 of the chapter 1.A.4 Small Combustion of the Guidebook) Tier 2 emission factors Code Name NFR Source Category 1.A.4.b.i Residential plants Fuel Solid Fuel (not biomass) SNAP (if applicable) Residential - Other equipments (stoves, fireplaces, cooking,...) Technologies/Practices Region or regional conditions Abatement technologies Not estimated Stoves NA NA NH 3 Not applicable Aldrin, Chlordane, Chlordecone, Dieldrin, Endrin, Heptachlor, Heptabromo-biphenyl, Mirex, Toxaphene, HCH, DDT, PCP, SCCP Pollutant Value Unit 95% confidence interval Reference Lower Upper NO x 100 g/gj EMEP/CORINAIR B216 CO g/gj EMEP/CORINAIR B216 NMVOC 600 g/gj EMEP/CORINAIR B216 SO x 900 g/gj EMEP/CORINAIR B216 TSP 500 g/gj EMEP/CORINAIR B216 PM g/gj EMEP/CORINAIR B216 PM g/gj EMEP/CORINAIR B216 Pb 100 mg/gj EMEP/CORINAIR B216 Cd 1 mg/gj EMEP/CORINAIR B216 Hg 5 mg/gj EMEP/CORINAIR B216 As 1.5 mg/gj EMEP/CORINAIR B216 Cr 10 mg/gj 6 18 EMEP/CORINAIR B216 Cu 20 mg/gj EMEP/CORINAIR B216 Ni 10 mg/gj 6 24 EMEP/CORINAIR B216 Se 2 mg/gj EMEP/CORINAIR B216 Zn 200 mg/gj EMEP/CORINAIR B216 PCB 170 µg/gj Kakareka et. al (2004) PCDD/F 1000 ng I-TEQ/GJ EMEP/CORINAIR B216 Benzo(a)pyrene 250 mg/gj EMEP/CORINAIR B216 Benzo(b)fluoranthene 400 mg/gj EMEP/CORINAIR B216 Benzo(k)fluoranthene 150 mg/gj EMEP/CORINAIR B216 Indeno(1,2,3-cd)pyrene 120 mg/gj EMEP/CORINAIR B216 HCB 0.62 µg/gj EMEP/CORINAIR B216 o An emission factor definition dialog will open. Enter the data as indicated in the screen dump below to enter the first emission factor from Table 3-1. o Click Save to store the new emission factor. o Repeat for all emission factors in Table 3-1 Page 25 of 80

26 UNITS To enter the emission factor for dioxins and furans, you will need the unit µg I-TEQ, which is not available in a newly installed version of CollectER III. This unit can easily be added to the system as follows: In the main program window select the Root data Units menu item to open the Units dialog. Right click in the grid and select Add Complete the New Unit dialog and click Save The Unit id must be a unique number. The screen dump below shows the resulting new unit with id 50. Ensure that the checkbox Emission unit is checked t indicate that this unit will be used for emissions. To be able to use this unit, a conversion factor must be defined to convert this new unit to the one used for reporting: Click Root data Coversions and enter a new conversion factor as indicated below. The unit used for reporting can be checked in the Root Pollutants menu item, when opening the Edit Pollutant dialog (right click the dioxin entry and select Edit from the popup menu). This concludes the input of the first technology and emission factors. The result is provided in the screen dump below. Page 26 of 80

27 GREENHOUSE GASES Emission factors for greenhouse gases can easily be added from the IPCC guidelines. You could use the following (from the IPCC 2006 Guidelines): CO kg/gj CH 4 1 g/gj N 2 O 1.5 g/gj We assume that in Middle Earth over time a second type of coal stoves is introduced. Emission factors for such advanced stoves can be found in table 3-23 of the Guidebook s small combustion chapter (NFR 1.A.4). To include this technology in the database: o Select the technology CoalStoves, right click in the Technologies list and select Add technology from from the popup menu. Page 27 of 80

28 o Complete the New Technology dialog as indicated below and click Save. This will create a copy of the selected technology with a different name and code. o Select the NewCoalStoves technology and update the emission factors to those of table 3-23 of the Small Combustion chapter in the Emission factors grid. This table has different emission factors for the main pollutants only (NO x, SO 2, CO, NMVOC, TSP, PM 10 and PM 2.5 ) Estimate emissions The final step before emissions can be calculated is to choose one or more technologies for all activity data. In this section we will select technologies for the coal fired heating stoves in Middle Earth. The assumption is that during the period 2000 to 2005, the traditional coal stoves (the CoalStoves technology) in the country start to be replaced by advanced wood stoves (the NewCoalStoves technology). In 2000 all stoves are still conventional and from 2001 onwards every year 10 % of these traditional stoves are replaced by advanced ones. To introduce this into the inventory do the following: o Select the first source (residential heating on bituminous coal) in the Source list of the main CollectER III window. The time series of activities for this source should be visible in the Activity rates field o Right click in the Selected Technologies field to open the New Technology dialog. o Clicking the ^-button will open the Technologies dialog with a list of all available technologies. o Select the CoalStoves technology and click Close o Select the year 2000 from the Year dropdown box o Enter the value 1 in the fraction field Page 28 of 80

29 o Add a comment in the comment box. The New Technology dialog will now look as shown in the screen dump below. o Click Save. The main CollectER III window now should show this selected technology in the Selected Technologies list. o Right click this selection in the Selected technologies list and select Add technology from in the popup menu. in the New technology dialog, select 2001, set the fraction to 0.9 and add a comment (if needed). o Click Save. The selection will show a red warning icon, indicating that for this activity rate not the full 100 % of activity is covered. o Do the same for 2002, 2003, 2004 and 2005 with fractions of 0.8, 0.7, 0.6 and 0.5 respectively. All selections will be marked with the red icon. o Right click again in the Selected technologies area and select Add technology from the popup menu. o Now select the NewCoalStoves technology, select 2001 and set the fraction to 0.1. Click Save. The red icon for the 2001 selections now should be gone. o Select this new technology also for 2002, 2003, 2004 and 2005, setting the fractions to the correct value. If you make an error in this, the red icon will remain, as shown in the screen dump below. Correct any errors by selecting the erroneous entry right click it and use the edit function to enter the correct data. Page 29 of 80

30 DIFFERENT TECHNOLLGIES VERSUS DIFFERENT SOURCES In mathematical terms there is no difference between defining a separate source for both types of stoves instead of using the select technologies mechanism to bring the changing population of coal fired residential stoves into the database. An alternative to the above approach could therefore be to define indeed two sources for the coal stoves and link these each for the full 100 % to one technology. In this alternative approach, the inventory compiler has to split the fuel statistics, used as activity data into the two sources, rather than CollectER III doing the split on the basis of penetrations. To define a second coal stoves source, the user will also have to define an additional Detail entry since each source must have a unique combination of Source category, Fuel, Detail and Location. Together this would make this alternative approach more work to implement. It is up to the user s taste to select one or the other approach when bringing in more detail into the database. A decisive issue to make such a decision could be whether or not the compiler wants to model the time dependency of the penetration of alternative or new technologies into the activity. This finalizes the data entry for this source and the emissions can be calculated and shown by clicking the Emissions button above the Source list. An Emissions window will popup, providing the calculated emissions for all selected sources in the Source list. The emissions of selected pollutants can also be presented as a time series graph by clicking the Graph button. Page 30 of 80

31 OTHER SOURCES Above we proposed to also include stoves on wood, oil and gas in the inventory. The emission factors for these sources could be obtained from the Guidebook s Small Combustion chapter as follows: Wood combustion for residential heating: assume half of this activity is in Fireplaces (table 3-14 in the Guidebook chapter) and the other half in wood stoves (table 3-17) Oil stoves could be used with a technology that is based on table 3-21 of the Guidebook Gas stoves could be based on table This could lead to the technologies as listed in the screen dump below. Obviously, many more area sources can be brought into the database. SOURCE 5 MANURE MANAGEMENT Below an overview activity data and technologies applied in Middle Earth for fattening pigs and laying hens is given. Emission factors can be found in table 3-1 of the 4.B Animal Husbandry and Manure Management chapter of the revised Guidebook and in the relevant chapters in the IPCC Guidelines. For fattening pigs a slurry based manure system is gradually replaced by a solid system. Animals Year Activity Rate Unit Fattening pigs, Fattening pigs, Laying hens slurry solid Fattening pigs caput 25% 75% caput 35% 65% caput 50% 50% caput 60% 40% caput 80% 20% caput 85% 15% Laying hens caput 100% caput 100% caput 100% caput 100% caput 100% caput 100% Page 31 of 80

32 The screen dump below shows the resulting emissions for these sources. NH 3 CH 4 BULK IMPORT Chapter 6 shows how in principle a large amount of data (road transport) can be entered into the database by using MS Access directly Point Sources In this section we will include a power plant, located in the Angmar region in Middle Earth. This power plant is owned by NorthEast Power and includes four units: o a 600 MW e hard coal fired unit o two 350 MW e hard coal fired unit o a 275 MW e natural gas fired unit. SOURCE 6 NORTHEAST POWER PLANT Define a new source In CollectER III point sources are indentified by their location. As proposed above we have introduced already two geographical definitions: one to store all national total area emissions and one to organise the point sources. Since in many countries many point sources could be included in the inventory, it might be wise to group these in different areas. We decide to group all point sources in the Eriador region, where Angmar is located (see map in Figure 3-1) in one Location by defining the Eriador region under the point sources location: o Select the point source location in the Locations Source filter tab and right click it o Select Add from the popup menu and define the Eriador region as indicated in the New Location dialog below. Page 32 of 80

33 o Define the power plant in the Eriador region by selecting the region and right clicking the field. o Define the four units within the NorthEast Power plant in Angmar as indicated in the screen dump below. o Define for each of these locations s source, similarly as described above for area sources, as indicated in the screen shot below. HOW TO DEFINE INDIVIDUAL INSTALLATIONS (UNITS) WITHIN A PLANT? Each source in the database must have a unique combination of location, source category, detail and fuel. It is therefore possible to have more than one source within each point source unit only if such a second unit has at least a different source category, a different detail or a different fuel. Page 33 of 80

34 The inventory compiler can apply some flexibility here in deciding whether or not to use different units or to define different sources within a plant or unit to store information of more complex facilities with more processes and units. In cases where different units are identical in all four parameters an alternative might be to add the activities of such units and define one source only. Entering activity data Now the sources have been defined, the activity rates can be easily entered in the Activity rates grid. The screen dump below shows these data. Due to maintenance, unit 3 has not been operational in 2003, so the activity rate is set to 0. The 350 MW e Coal Unit 1 has been closed down in November Therefore no activity Page 34 of 80

35 rate is given for this unit for This type of information can be included in the comment field for the relevant activity rate as indicated below. Technologies and emission factors Including technologies and selecting these for the point sources is fully analogous to what has been described for area sources. The technologies can be derived from the relevant Guidebook chapter. The coal fired boilers are of the Wet Bottom boilers type as given in table 3-16 of the Energy Industries chapter from the revised Guidebook (reproduced below). The coal technology could be defined as follows: With the emission factors from the table below and those from the IPCC 2006 Guidelines for the greenhouse gases, all information on the technology for the wet bottom boilers in the NorthEast power plant in Angmar are available. By selecting the newly defined technology and setting the fraction to 1 for the three coal fired units for all years the emissions now can be calculated. For the gas fired plant the technology and emission factors from table 3-15 of the chapter 1.A.1 Energy Industries can be used. Page 35 of 80

36 NFR Source Category Fuel SNAP (if applicable) Technologies/Practices Region or regional conditions Abatement technologies Not estimated Not applicable Tier 2 emission factors Code Name 1.A.1.a Public electricity and heat production Coking Coal, Steam Coal & Sub-Bituminous Coal Wet Bottom Boilers All Aldrin, Chlordane, Chlordecone, Dieldrin, Endrin, Heptachlor, Heptabromo-biphenyl, Mirex, Toxaphene, HCH, DDT, HCB, PCP, SCCP NH3 Pollutant Value Unit 95% confidence interval Reference Lower Upper NOx 190 g/gj Guidebook (2006) CO 12.1 g/gj Eur.Comm. (2006) NMVOC 30 g/gj Guidebook (2006) SOx 100 g/gj Eur. Comm. (2006) TSP 40 g/gj CEPMEIP (2004) PM10 30 g/gj CEPMEIP (2004) PM g/gj CEPMEIP (2004) Pb g/gj Guidebook (2006) Cd g/gj Guidebook (2006) Hg g/gj Guidebook (2006) As g/gj Guidebook (2006) Cr g/gj Guidebook (2006) Cu g/gj Guidebook (2006) Ni g/gj Guidebook (2006) Se g/gj Guidebook (2006) Zn g/gj Guidebook (2006) PCB 0.13 mg/gj Guidebook (2006) PCDD/F g/gj 1.65E US EPA (1998) Benzo(a)pyrene mg/gj TNO (1995) Benzo(b)fluoranthene mg/gj TNO (1995) Benzo(k)fluoranthene mg/gj TNO (1995) Indeno(1,2,3-cd)pyrene mg/gj TNO (1995) Total 4 PAHs 7.26E-06 g/gj 7.26E US EPA (1998) Page 36 of 80

37 DIRECT EMISSIONS In many cases emissions from individual plants might be measured at the stack. In principle, CollectER III allows for input of such emissions directly. However this is not recommended for two reasons: In most cases only a few pollutants are measured and the measurements need to be completed by estimated emissions on the basis of activity data and emission factors for those pollutants that are not measured. Since the emission reporting requirements for the UNFCCC request also the reporting of activity data, such activity data must be available for all sources in the database. So activity data must be available and would allow the inventory compiler to calculate implied emission factors for all sources where only direct emissions are available. If the implied emission factors deviate from the ones found in Guidelines or Guidebook, a specific technology for the plant could be defined with the implied emission factors for the measured pollutants and emission factors from literature for the others. The origin of the emission factor could be documented in the comment field. SOURCE 7 MORDOR STEEL: INTEGRATED IRON AND STEEL WORKS A second example is Mordor Steel, an integrated iron and steel works located in the Mordor area in Middle Earth (Figure 3-1). This large industrial facility consists of a coke plant, a sinter plant, a blast furnace and a basic oxygen furnace steel plant. Figure 3-2 shows the mass flow through this plant to produce 1000 tons of steel. The plant has a total capacity of 2500 tonnes of steel per year, but normally produces between 1500 and 2250 tonnes of steel every year. All blast furnace gas is used as an energy source within the facility. So the inputs into the facility are coal for the coke production and iron ore as the main feed stocks. The only product of this facility is steel. Coal Coke production 500 ton coke Blast Furnace Steel making (BOF) Steel Sinter production 940 ton pig iron 1000 ton steel Iron ore 1090 ton sinter scrap and additives Figure 3-2 Mordor Steel Works overview; the mass flows are those needed to produce 1000 tonnes of steel. Define the sources To define the sources we first need to define new locations. Following our earlier approach to have the facilities organised by regions, we first define the Mordor region within Middle Page 37 of 80

38 Earth. The Mordor Steel works is the first facility within Mordor. In this example we do not define separate units within the plant, but define these as different sources within the plant. Since these four processes do all have a unique source category (and Detail), there is no need to create a separate location for these units. The sources are indicated in the screen dump below. COAL USED AS FEED STOCK The coal used in the steel works is mainly used as the reducing chemical, rather than as energy source. The waste gases of the coke production (coke oven gas) and the blast furnace (blast furnace gas) are used as energy source for the processes. Enter activity data The activity rates for the different processes within the Mordor Steel integrated iron and steel works could be as follows: Process Product Unit Coke oven Coke ton of product Sinter plant Sinter ton of product Blast furnace Pig iron ton of product Steel making Steel ton of product Technologies and Emission Factors Define the required technologies and get the emission factors for o the coke oven from table 3-1 of the 1.B.1.b Solid Fuel Transformation chapter of the new Guidebook, o the sinter plant from table 3-2 of the 2.C.1 Iron and Steel Production chapter of the new Guidebook, o the blast furnace from table 3-9 of the 2.C.1 Iron and Steel Production chapter of the new Guidebook and Page 38 of 80

39 o the steel making furnace from table 3-15 of the 2.C.1 Iron and Steel Production chapter of the new Guidebook The unit µg I-TEQ needs to be defined to be able to enter the dioxins emission factors. Ensure that all necessary unit conversions are also included. Emission factors for greenhouse gases can be obtained from the IPPU Volume of the IPCC 2006 Guidelines. The technologies might now look like the screen dump below. The table provides an overview of emission factors. Pollutant Unit Blast Furnace Coke Oven Sinter Plant Steel Making CO 2 Mg/Mg product CH 4 g/mg product 0.1 kg/mg product 0.07 NO X g/mg product 10 NH 3 g/mg product 5 NMVOC g/mg product CO kg/mg product 3.5 TSP g/mg product PM 10 g/mg product Page 39 of 80

40 Pollutant Unit Blast Furnace Coke Oven Sinter Plant Steel Making PM 25 g/mg product As g/mg product Cd g/mg product Cr g/mg product Cu g/mg product Hg g/mg product Ni g/mg product Pb g/mg product Se g/mg product Zn g/mg product Benzo(a) g/mg product 0.75 Benzo(b) g/mg product 0.25 Benzo(k) g/mg product 0.25 DIOX µg I-TEQ/Mg product HCB µg/mg product 32 Indeno g/mg product 0.3 PAH g/mg product mg/mg product 0.1 PCBs g/mg product mg/mg product The resulting emissions are shown below. Page 40 of 80

41 3.4 Starting a new inventory cycle Emission inventories are typically compiled ion an annual cycle. Every year a new year needs to be added to the inventory. This can be done by selecting the Edit Add a Year menu item. The Create New Year dialog will open. The new year must be entered in the New Year text box. The user then has two options: o Copy an existing year into the new year by selecting the From Selected radio button and one of the already available years in the inventory. Depending on the status of the two check boxes the activity data and/or the technology selections and technologies/emission factors will be copied from this year into the new year o Open an empty inventory for the new year by selecting the Empty radio button; in this case no activity data or technology selections are copied. In this case all existing technologies and emission factors obviously will be available for use in the new year. In the first case all activity rates and /or the technology selections must be updated. The user can start at the largest source categories first and work towards the smaller source categories. Wherever needed new technologies can be defined and used for any source category where needed. Also new sources can be added. Generally, sources that have been closed down in the new year cannot be deleted, since data will still be in the database for earlier years. The user might consider setting the notation key for the activity rate for such a source to NO (not occurring). Page 41 of 80

42 4 Reporting 4.1 Reporting the Inventory to International Obligations The main objective of compiling inventories with the CollectER III tool is to prepare national submissions to the international obligations. This chapter will explain how an inventory can be reported to the UNFCCC and the LRTAP Conventions, once the inventory has been completed. The next chapters will provide some additional functionality and explanations that can help the user to further improve and quality control the inventory. 4.2 Reporting to UNFCCC and EU MM The CRF Reporter tool CRF Reporter version and installation Reporting of a national greenhouse gas emission inventory to UNFCCC for Annex I countries must use the CRF Reporter tool as developed by the UNFCCC Secretariat. This software tool can be downloaded from UNFCCC s website at URL The version used in this report is shown in the about box below. Since the CRF Reporter ask the user to select the party (= country) upon installation from the list of Annex I parties, Middle Earth obviously cannot be chosen. In these examples therefore the Netherlands has been chosen. The system seems to work properly, despite the unavailability of Middle Earth in CRF Reporter s list of countries. CRF Reporter also can be installed for two types of users: o The National inventory compiler (NIC) a person responsible for the overall preparation, compilation and official reporting of national GHG inventories Page 42 of 80

43 o A Sectoral expert (SE) a person responsible only for a certain part, sector or subsector, of a national inventory. The SE communicates data on the specific sector to NIC. The main difference between both types of users is that a SE cannot submit the inventory to the UNFCCC. The installation used in this document is the SE installation. This type of installation does not need a special registration, as does the NIC installation. However it provides all functionality needed to import the CollectER III into the CRF Reporter. AVAILABILITY OF CRF REPORTER At this moment CRF Reporter is in principle applicable to all Annex I countries that report to the UNFCCC. The submission functionality includes secured and specific communication between the National Inventory Compiler (NIC) and the UNFCCC secretariat. For non-annex I countries this functionality is not implemented. However, CRF Reporter can for these countries also generate a set of CRF MS Excel files that could be submitted as part of for instance a national communication, to UNFCCC. In this case the expert probably has to change filenames and table headings in each sheet manually to indicate the country Data import into CRF Reporter Import into CRF Reporter uses a specific XML file format. The interpretation of this file by the CRF Reporter tool is partly governed by the settings that might be specific for the country, a so-called country profile. CollectER III uses the country profile to allocate specific data in the CollectER database to those in the CRF Reporter database. The CollectER III tool comes with a predefined country profile, but it might be wise to generate a new country profile as follows: o Open the CRF Reporter and select the Submission Generate party profile menu item Page 43 of 80

44 o The Profile generation wizard will open and guide you through the successive steps of this function. You must generate your country profile from the CRF Reporter if this tool already includes data from other sources than the CollectER III tool. Importing data into CRF Reporter will overwrite any data that might already exist in the CRF Reporter database for the same source categories, fuels and years as stored in the import file. WARNING Before using the import function of CRF Reporter, please ensure that you have read the appropriate sections of the CRF Reporter documentation. Importing data into CRF Reporter cannot be undone, so ensure an appropriate backup of your CRF Reporter database before you start importing new data. This will enable you to revert to the situation of the data before the import was performed Generating the XML file for import into CRF Reporter In the present version of CollectER III producing an XML import file for CRF Reporter must be done for every year in the inventory separately. This section will describe how this should be done. o Select the Reporting UNFCCC menu item to open the CRF reporting dialog (see screen shot below). o Ensure that the appropriate country profile is loaded. If you produced a country profile from the CRF Reporter tool, load it by clicking the Country profile load button and select this file in the file open dialog. CRF Reporter generates two country profile files. The one to be loaded is the *_profile_variables_*.txt file (see below in the case of the Netherlands as the reporting country). Page 44 of 80

45 o Save the XML file for each year in the database by clicking the Save to File button. In the case of the inventory as produced in this report, you will save six separate XML files as indicated in the screen dump below. With this the files for import into the CRF Reporter are ready and available for import in CRF Reporter and you can close the CollectER III application Import the XML files into CRF Reporter o Open the CRF Reporter tool and select the File Import data menu item or click the import data button in the tool bar. o Follow the steps in the Import Wizard to import each of the six XML files exported from CollectER III Page 45 of 80

46 o Repeat this import for all the years where export files have been generated. After the import of the files as described, the CRF Reporter main window might look like the screen shot below. For further use of the CRF Reporter, please see the CRF Reporter documentation and help files. Page 46 of 80

47 4.2.4 Generating the CRF tables The CRF Reporter tool provides functionality to directly generate the CRF tables from the CRF Reporter database. The CRF Reporter uses the party selection to both labelling each sheet in the CRF files and generating filenames for these files. 4.3 Reporting to LRTAP and NEC Directive The NFR Report option of CollectER III directly generates the flat file format as defined in the Revised UNECE/EMEP Reporting Guidelines ECE/EB.AIR/2008/4 (templates Tables4A-C). Partial reports for selected pollutant or a subset of pollutants or for a selected category or subset of categories may by produced by this report option. The selected data can be stored into the simple flat file format as defined by the UNECE/EMEP reporting Guidelines. o Select the Reporting UNECE_LRTAP menu item to open the NFR Report dialog. o Click the Safe to file button and define the folder and filename for the export file. This will export all relevant data into an NFR flat file format. The select buttons on the NFR report dialog window allow the user to select specific pollutants and/or source categories. By default all pollutants and source categories are selected. Page 47 of 80

48 5 Tools within CollectER III 5.1 Introduction The present ReportER III application has limited possibilities to visually inspect the data in the database. Simple graphs can be produced for both activity data and calculated emissions by clicking a Graph button on a number of windows. This will lead to a simple time series for the selected items in the window. Under the Tools Quality control menu item several additional tools are available. These tools relate to the official quality criteria of both sets of reporting guidelines. These tools include: o Completeness report o Key category analysis Air pollutants, following the key category analysis of the Methodological Choice chapter of the revised Guidebook 4 Greenhouse gases, following the key category analysis of the IPCC 2000 Good Practice Guidance and the 2006 IPCC Guidelines. This functionality is not implemented yet o Time series consistency; not implemented yet. The Tools Check data menu item provides a few additional checks, essentially identifying any missing information to use the imported data for generating the formal reports. In addition a number of exports are available, allowing the user to export (a selection of) CollectER III data into a file format that can easily be studied, presented and scrutinized in commercial spreadsheet tools like MS Excel. 5.2 Preparing the Inventory: QA/QC tools Completeness Completeness check One of the main quality criteria is the completeness of the database. CollectER III includes a series of checks that looks for source categories that are not included in the database and identifies the use of notation keys at several tables in the database. COMPLETENESS REPORTING TO UNFCCC The CRF tables include information on the use of notation keys in the inventory. The present version of CollectER III is not able yet to complete these tables from the database directly. This function is planned for implementation in A completeness check of the inventory can be activated by selecting the Tools Quality Control Completeness menu item. This will run a completeness check on the database. 4 Page 48 of 80

49 When ready a message box will appear and a text file will be opened in Notepad. The user can safe this text file, using the SaveAs function of Notepad. An example of the completeness check output is reproduced in the screen dump below Resolving completeness issues Source categories not estimated The first block of issues in the completeness check file lists the source categories that do not have a source defined (missing source categories). This might be because the country does not have any source in such a source category or the source might intentionally not have been estimated. In the latter case the source should receive an NE (not estimated) notation key. If the source category does not occur in the country it should have a NO (not occurring) notation key. Page 49 of 80

50 Attaching a NO notation key to a source category can be done as follows: o Define a new source within the source category as indicated in the screen dump below. This is the second source category in the list of not estimated sources in the completeness check above. o Set the activity data for this source in at least one year to NO. If you now rerun the completeness check, this source category is no longer included in the list of missing source categories. This error messages should be seen as a warning. Any source category listed here must appear as a not estimated source category in the submission to both LRTAP and UNFCCC. Missing activity data The second block of messages lists those sources that are defined but where no activity data have been entered. Solving this issue is obvious: either add activity data (including if relevant a notation key) or delete the source. This also is a warning. Missing technologies The next block lists those sources that have been given activity rates, but no technologies associated to them. The solution must be to select technologies for these activities. This is an error. Apparently activity data are included for the source, but emissions cannot be calculated because no technology and associated emission factors is selected for this source. Page 50 of 80

51 Emission Factor NE s and NA s The final check in the completeness report lists the emission factors for specific technologies that have an NE or NA notation key. The first one should be listed as NE in the completeness table of the CRF. The latter one should correspond with the grey cells in the reporting tables of both UNFCCC and LRTAP. This again are warnings Key Categories The concept of Key Categories is introduced in the IPCC Good Practice Guidance [3]. Its purpose and definition are reproduced from the IPCC Good Practice Guidance in Figure 5-1. Although the revised EMEP/EEA Guidebook has taken over this concept and approach, the algorithms to identify key categories within an inventory differ between the reporting requirements on air pollutants and on greenhouse gases. This is a consequence of the fact that aggregation over the pollutants in the LRTAP convention is not possible, whereas aggregation over gases in the UNFCCC reporting is possible by using the GWP of individual gases. Figure 5-1 Copy of the introduction to and definition of a Key Category from [3] The key sources are identified, once the inventory is completed, by either one of two approaches: o In Approach 1, key categories are identified using a pre-determined cumulative emissions threshold. Key categories are those that, when summed together in Page 51 of 80

52 descending order of magnitude, add up to at least this threshold level; in the IPCC Guidelines this approach is called a Tier 1 Key Category Analysis (KCA) o Approach 2 key categories can be derived by inventory compilers, if category uncertainties or parameter uncertainties are available. Source categories with high uncertainties have a higher chance of being identified as key category as compared to Approach 1; in the IPCC Guidelines this approach is called a Tier 2 KCA. Since at this moment uncertainty information is not included in the CollectER III databases Approach 2 cannot be implemented Greenhouse gases The key source analysis for greenhouse gases determines key sources for all gases together by aggregating the emissions for all greenhouse gases using the Global Warming Potential. The cumulative emissions threshold for greenhouse gases is set to 95 %. The details of the greenhouse gas KCA are described in the IPCC Good Practice Guidance, chapter 7 [3]. This function is not implemented yet. It will need an addition to the CollectER III database structure allowing for the calculation of emissions in GWPs. Implementation of this function is planned for Air Pollutants The wide range of air pollutants, included in the LRTAP convention and its protocols does not allow for an aggregation over all pollutants to identify key categories. This means that KCA s have to be performed by pollutant. Against this understanding, the threshold value for the cumulative emissions is set to 80 % for each pollutant [1, Genral Guidacne chapter 2, Key Category Analysis and Methodological Choice]. To generate a KCA for air pollutants, select the Tools Quality Control Key Category Air Pollutants menu item. Page 52 of 80

53 Selecting this menu item will open a Key Category dialog, where the key categories are identified by pink rows and a key icon. The user can select the pollutant and the inventory year in the respective list boxes. The user can save the KCA results by clicking the Safe to File button in two formats, by selecting the appropriate file type in the Save As dialog: o A semicolon separated text file o An MS Excel workbook Time Series Consistency Time series consistency is one of the quality criteria for national inventory submissions. This menu item is basically a place holder for a tool that is to be developed in the future. A time series consistency check could include the detection of gaps, time jumps and other Page 53 of 80

54 outliers. Algorithms for this can be developed and included in the CollectER III tool when users are interested in this. At this moment the user can check the graphical representations of activity data and emissions by clicking a button at the appropriate screens. 5.3 Data checking The data checking tool has been developed for data screening after bulk import, either by importing an earlier CollectER version database or by directly importing using MS Access as described in chapter 6, Import of data Using MS Office applications. The tool also includes at this moment one data integrity check. In future such checks could be extended. The data check can be run by the menu item Tools Data Check. This will open the checking dialog: The Start Checking Import button will run a data check on the data imported from earlier CollectER versions databases and will identify undefined fuels, details and other issues that need to be repaired before a full successful import can be performed. The start checking other data runs a number of consistency checks. THIS CHECKING FUNCTIONALITY NEEDS FURTHER DEVELOPMENT. 5.4 Other reports and overviews The CollectER III software tool provides a series of export functions that allow the user to review and assess the data in other software tools. These exports can both be as semicolon separated text files or directly as MS Excel files. The choice between the two formats is made by selecting the appropriate file type in the SaveAs dialog window. These exports can be produced by selecting on of the submenu items in the File Export menu (see screenshot below). Page 54 of 80

55 Page 55 of 80

56 6 Import of data Using MS Office applications BULK IMPORT This chapter provides examples of bulk data import into the CollectER III database. Bulk import is performed in a copy of the CollectER III database. This import procedure uses standard functionality of MS Access and MS Excel. The procedure below assumes good and in dept knowledge of both MS Excel and MS Access. The procedure uses some advanced features of both MS Office applications: the pivot tables to generate overviews and to prepare the input table. It also could use linked Excel tables in the Access database to perform the actual import Import should follow a specific order of actions: Define the new sources; this might need definition of new SourceDetails and/or Fuels and/or Units Import ActivityRates Define new Technologies Import the penetrations into the TechnologySelections table Import EmissionFactors WARNING Be sure to always make a back up of your CollectER III database before you start working directly in MS Access. Always check your import carefully in the CollectER III tool after you have made changes as described below and assure yourself that the changes are correctly interpreted by the tool and that the result indeed is as intended. 6.1 Accessing the CollectER III database directly The data in CollectER III are stored in a database collecter_iii.mdb, stored in the data subdirectory of the CollectER III program directory, normally (default installation) C:\Program Files\CollectER_III\Data. Although it is possible to work directly in this database, it is recommended to use the backup and restore functionality of CollectER III to create a copy of this file. The direct data entry then can be performed on the back up copy and imported into the CollectER III tool by the restore function: o Open the CollectER III application. o Click the File Backup menu item and define a filename for the exported backup copy of the database o Click OK. o Open the backup database in MS Access: Page 56 of 80

57 6.2 Road transport SOURCE 8 ROAD TRANSPORT This section follows the necessary steps to import data for road transport, where vehicle types, vehicle classes and vehicle technologies are defined. The technologies and emission factors are derived from the revised Guidebook Activity data The table below presents the available activity data for road transport in Middle Earth for the years 2000 until In this table we have activity data for each of the three fuels (diesel, gasoline and LPG) different vehicle types and (size) classes in the country. We will define a source for each vehicle type, class and fuel separately. Once the sources have been defined and appended to the Sources table the activity data can be appended to the Activities table in the database. The first step is to define the sources in the Sources table of the database. This means that we have to link the vehicle types and vehicle classes to the Source Categories and Source Details and the fuels to the Fuels in the database. Page 57 of 80

58 Max of AR Year CRF/NFRCode SourceGroup Description FuelName A.3.b.i Passenger Cars Passenger Cars; 2-Stroke Motor Gasoline Passenger Cars; Diesel <2,0 l Gas/Diesel Oil Passenger Cars; Diesel >2,0 l Gas/Diesel Oil Passenger Cars; Gasoline <1,4 l Motor Gasoline Passenger Cars; Gasoline >2,0 l Motor Gasoline Passenger Cars; Gasoline 1,4-2,0 l Motor Gasoline Passenger Cars; LPG Liquefied Petroleum Gases A.3.b.ii Light Duty Vehicles Light Duty Vehicles; Diesel <3,5 t Gas/Diesel Oil Light Duty Vehicles; Gasoline <3,5t Motor Gasoline A.3.b.iii Buses Buses; Coaches Articulated >18 t Gas/Diesel Oil Buses; Coaches Standard <=18 t Gas/Diesel Oil Buses; Urban Buses Articulated >18 t Gas/Diesel Oil Buses; Urban Buses Midi <=15 t Gas/Diesel Oil Buses; Urban Buses Standard t Gas/Diesel Oil Heavy Duty Trucks Heavy Duty Trucks; Articulated t Gas/Diesel Oil Heavy Duty Trucks; Articulated t Gas/Diesel Oil Heavy Duty Trucks; Articulated t Gas/Diesel Oil Heavy Duty Trucks; Rigid <=7,5 t Gas/Diesel Oil Heavy Duty Trucks; Rigid >32 t Gas/Diesel Oil Heavy Duty Trucks; Rigid t Gas/Diesel Oil Heavy Duty Trucks; Rigid t Gas/Diesel Oil Heavy Duty Trucks; Rigid t Gas/Diesel Oil Heavy Duty Trucks; Rigid t Gas/Diesel Oil Heavy Duty Trucks; Rigid t Gas/Diesel Oil Heavy Duty Trucks; Rigid 7,5-12 t Gas/Diesel Oil A.3.b.iv Mopeds Mopeds; <50 cm³ Motor Gasoline Motorcycles Motorcycles; 2-stroke >50 cm³ Motor Gasoline Motorcycles; 4-stroke <250 cm³ Motor Gasoline Motorcycles; 4-stroke >750 cm³ Motor Gasoline Motorcycles; 4-stroke cm³ Motor Gasoline Fuels I n our activity data set we have three fuels used. We recommend the following link to the CollectER III fuels; o Gas/Diesel oil fuel_id 205 o Motor Gasoline 208 o Liquified Petroleum Gases 303 Source categories We propose the following link: o Mopeds Source category 1.A.3.b.4 o Motorcycles 1.A.3.b.4 o Passenger cars 1.A.3.b.1 o Light duty vehicles 1.A.3.b.2 o Heavy duty vehicles 1.A.3.b.3 o Buses 1.A.3.b.3 Page 58 of 80

59 SOURCE CATEGORIES The relevant source categories can be found in the SourceCategories table in the database. This table should not be changed. The entries in this table determine in what source category the emissions will be reported. These source categories are defined by the reporting guidelines. Any change in this table might lead to erroneous reporting of emissions. Source details The SourceDetails table does not contain the details as required from the available activity data. This table therefore should be modified by the user to enable import the activity data above. To keep the hierarchical structure of the table, we recommend appending to this table the list of unique vehicle classes. The value of the level field ensures that these new details are directly under the 4 digit SNAP codes 070#. Detail_ID Detail_Name Combustion Level 0701a Passenger Cars; 2-Stroke TRUE b Passenger Cars; Diesel <2,0 l TRUE c Passenger Cars; Diesel >2,0 l TRUE d Passenger Cars; Gasoline <1,4 l TRUE e Passenger Cars; Gasoline >2,0 l TRUE f Passenger Cars; Gasoline 1,4-2,0 l TRUE g Passenger Cars; LPG TRUE a Light Duty Vehicles; Diesel <3,5 t TRUE b Light Duty Vehicles; Gasoline <3,5t TRUE a Buses; Coaches Articulated >18 t TRUE b Buses; Coaches Standard <=18 t TRUE c Buses; Urban Buses Articulated >18 t TRUE d Buses; Urban Buses Midi <=15 t TRUE e Buses; Urban Buses Standard t TRUE f Heavy Duty Trucks; Articulated t TRUE g Heavy Duty Trucks; Articulated t TRUE h Heavy Duty Trucks; Articulated t TRUE i Heavy Duty Trucks; Rigid <=7,5 t TRUE j Heavy Duty Trucks; Rigid >32 t TRUE k Heavy Duty Trucks; Rigid t TRUE l Heavy Duty Trucks; Rigid t TRUE m Heavy Duty Trucks; Rigid t TRUE n Heavy Duty Trucks; Rigid t TRUE o Heavy Duty Trucks; Rigid t TRUE p Heavy Duty Trucks; Rigid 7,5-12 t TRUE a Mopeds; <50 cm³ TRUE b Motorcycles; 2-stroke >50 cm³ TRUE c Motorcycles; 4-stroke <250 cm³ TRUE d Motorcycles; 4-stroke >750 cm³ TRUE e Motorcycles; 4-stroke cm³ TRUE 2 With this information a table can be constructed in a spreadsheet, providing all the data needed for the bulk import of the activity. The upper part of such a table is reproduced below. The full table contains 180 rows of data (30 sources, 6 years). Page 59 of 80

60 Location_ID SourceCategory SourceDetail SourceName Fuel Year Value MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l MI_area 1.A.3.b.i 0701c Passenger Cars; Diesel >2,0 l MI_area 1.A.3.b.i 0701c Passenger Cars; Diesel >2,0 l MI_area 1.A.3.b.i 0701c Passenger Cars; Diesel >2,0 l MI_area 1.A.3.b.i 0701c Passenger Cars; Diesel >2,0 l MI_area 1.A.3.b.i 0701c Passenger Cars; Diesel >2,0 l MI_area 1.A.3.b.i 0701c Passenger Cars; Diesel >2,0 l MI_area 1.A.3.b.i 0701d Passenger Cars; Gasoline <1,4 l MI_area 1.A.3.b.i 0701d Passenger Cars; Gasoline <1,4 l MI_area 1.A.3.b.i 0701d Passenger Cars; Gasoline <1,4 l MI_area 1.A.3.b.i 0701d Passenger Cars; Gasoline <1,4 l MI_area 1.A.3.b.i 0701d Passenger Cars; Gasoline <1,4 l MI_area 1.A.3.b.i 0701d Passenger Cars; Gasoline <1,4 l MI_area 1.A.3.b.i 0701e Passenger Cars; Gasoline >2,0 l MI_area 1.A.3.b.i 0701e Passenger Cars; Gasoline >2,0 l MI_area 1.A.3.b.i 0701e Passenger Cars; Gasoline >2,0 l MI_area 1.A.3.b.i 0701e Passenger Cars; Gasoline >2,0 l MI_area 1.A.3.b.i 0701e Passenger Cars; Gasoline >2,0 l MI_area 1.A.3.b.i 0701e Passenger Cars; Gasoline >2,0 l MI_area 1.A.3.b.i 0701f Passenger Cars; Gasoline 1,4-2,0 l MI_area 1.A.3.b.i 0701f Passenger Cars; Gasoline 1,4-2,0 l MI_area 1.A.3.b.i 0701f Passenger Cars; Gasoline 1,4-2,0 l MI_area 1.A.3.b.i 0701f Passenger Cars; Gasoline 1,4-2,0 l MI_area 1.A.3.b.i 0701f Passenger Cars; Gasoline 1,4-2,0 l MI_area 1.A.3.b.i 0701f Passenger Cars; Gasoline 1,4-2,0 l MI_area 1.A.3.b.i 0701g Passenger Cars; LPG MI_area 1.A.3.b.i 0701g Passenger Cars; LPG MI_area 1.A.3.b.i 0701g Passenger Cars; LPG To make import from this table possible in MS Access we recommend defining a name for the range in Excel, containing this data. In our example we use the range name RoadActivityData in the spreadsheet. Append SourceDetails To import both the new SourceDetails and the activity data do the following: o Open the exported database in MS Access and select the Tables tab in the main database window o Right click in the tables list and select Link tables. Page 60 of 80

61 o Locate the MS Excel file that contains the named range with data in the file open (Link) dialog and click Link to open the Link Spreadsheet Wizard. o Select the named range RoadSourceDetails and click Next. o Ensure that in the next window First Row Contains Column Headings is checked and click Finish. The data table now is available in the MS Access database. o Create an Append query as indicated above and run it to append the new source details to the SourceDetails table. Note that the columns 3, 5 and 7 in the Excel table do not have headings, MS Access uses F3, F5 and F7 as these headings respectively. Since we will not use the different driving patterns in the SNAP 6 digit level, these can be deleted from the SourceDetails table. Page 61 of 80

62 Append Sources UNITS Activity data for road transport are given in TJ. This unit is not available in the database yet and should be added: Add an entry in the.units table as indicated below The Unit id must be a unique number. The screen dump above shows the resulting new unit with id 51. Ensure that the checkbox Emission unit is not checked to indicate that this unit will not be used for emissions. To be able to use this unit, conversion factors must be defined to convert this new unit to the one used for reporting. Add three new conversion factors to the UnitConversions table: one for GJ (unit_id = 28) to TJ (unit_id =51), factor = 0,001 and one for TJ to GJ (factor = 1000) one for TJ to TJ (factor = 1). To append the sources to the Sources table work similarly. Just build and run the query as indicated below, based on the RoadActivityRates named range in the spreadsheet. Note: the Page 62 of 80

63 fuel code in the Excel table is seen by MS Access as a number, whereas the Sources table expects it to be a string. Therefore the MS Access function Str must be used. Since the Str function in MS Access adds a space before the number, the function Trim should be used on top of this. The Unit_id should be read from the Units table. The final two columns of the query ensure that this is indeed the case. To see what has happened in the inventory, the new Source details and sources can be viewed in CollectER III by using the restore (menu item File Restore) of the application. After restoring to the updated database, the Details tree should look like the screen dump below. The sources shown in the Source list will depend on the selection in the Details tree.. Page 63 of 80

64 Append Activity Data Since the Sources now have been defined, the activity data can be appended in the database. Close CollectER III and re-open the database in MS Access. Build the query as reproduced below that will append the road transport activity data to the ActivityRates table. Note that the relation between the fuel code in the spreadsheet data range (ActivityData table) is a numerical value, whereas the Sources table has this code as a text. Therefore a relation cannot be made by the usual dragging and dropping in the query design interface, but must be made explicitly as indicated in the fifth column of the query. This completes the input of the activity data for road transport. After restoring the database into the CollectER III application, the data can now be viewed in the CollectER III main window. Page 64 of 80

65 6.2.2 Technologies and Technology Selections The procedure to introduce technologies and technology selections into the database is similar to the procedure outlined above for source definitions and activity data. The first step is to prepare a named range in MS Excel, containing all the technologies and the fractionsd of each technology used in each source for all years in the inventory. The top part of this table might look like the one below. Technology_Code TechnologyName LPG_PC_Euro_3_1 Passenger Cars; LPG; LPG; PC Euro 3-98/69/EC Stage2000 LPG_PC_Euro_2_1 Passenger Cars; LPG; LPG; PC Euro 2-94/12/EEC LPG_PC_Euro_1_1 Passenger Cars; LPG; LPG; PC Euro 1-91/441/EEC LPG_Conventional_1 Passenger Cars; LPG; LPG; Conventional Gasoline_PC_Euro_3_1 Passenger Cars; Gasoline; Gasoline 1,4-2,0 l; PC Euro 3-98/69/EC Stage2000 Gasoline_PC_Euro_2_1 Passenger Cars; Gasoline; Gasoline 1,4-2,0 l; PC Euro 2-94/12/EEC Gasoline_PC_Euro_1_1 Passenger Cars; Gasoline; Gasoline 1,4-2,0 l; PC Euro 1-91/441/EEC Gasoline_Open_Loop_1 Passenger Cars; Gasoline; Gasoline 1,4-2,0 l; Open Loop Gasoline_PC_Euro_3_2 Passenger Cars; Gasoline; Gasoline >2,0 l; PC Euro 3-98/69/EC Stage2000 Gasoline_PC_Euro_2_2 Passenger Cars; Gasoline; Gasoline >2,0 l; PC Euro 2-94/12/EEC Gasoline_PC_Euro_1_2 Passenger Cars; Gasoline; Gasoline >2,0 l; PC Euro 1-91/441/EEC Gasoline_ECE_15/04_1 Passenger Cars; Gasoline; Gasoline >2,0 l; ECE 15/04 Gasoline_PC_Euro_3_3 Passenger Cars; Gasoline; Gasoline <1,4 l; PC Euro 3-98/69/EC Stage2000 Gasoline_PC_Euro_2_3 Passenger Cars; Gasoline; Gasoline <1,4 l; PC Euro 2-94/12/EEC Gasoline_PC_Euro_1_3 Passenger Cars; Gasoline; Gasoline <1,4 l; PC Euro 1-91/441/EEC Gasoline_Open_Loop_2 Passenger Cars; Gasoline; Gasoline <1,4 l; Open Loop Gasoline_Conventional_1 Passenger Cars; Gasoline; 2-Stroke; Conventional Diesel_PC_Euro_3_1 Passenger Cars; Diesel; Diesel >2,0 l; PC Euro 3-98/69/EC Stage2000 Diesel_PC_Euro_2_1 Passenger Cars; Diesel; Diesel >2,0 l; PC Euro 2-94/12/EEC Diesel_PC_Euro_1_1 Passenger Cars; Diesel; Diesel >2,0 l; PC Euro 1-91/441/EEC Diesel_Conventional_1 Passenger Cars; Diesel; Diesel >2,0 l; Conventional Note that the TechnologyCode must be unique for each technology in the database. The MS Excel named range is in our example linked to the database with the name RoadTechnologies. The technology name is a combination of the Source, Fuel and Technology. The import of the penetrations into the SelectTechnologies table can be performed with the query below, using the spreadsheet range RoadPenetrations as provided below also. Page 65 of 80

66 Location_ID SourceCategory SourceDetail SourceName Fuel Year Terchnology_Name Value MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke Passenger Cars; Gasoline; 2-Stroke; Conventional 1.00 MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke Passenger Cars; Gasoline; 2-Stroke; Conventional 1.00 MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke Passenger Cars; Gasoline; 2-Stroke; Conventional 1.00 MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke Passenger Cars; Gasoline; 2-Stroke; Conventional 1.00 MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke Passenger Cars; Gasoline; 2-Stroke; Conventional 1.00 MI_area 1.A.3.b.i 0701a Passenger Cars; 2-Stroke Passenger Cars; Gasoline; 2-Stroke; Conventional 1.00 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; Conventional 0.86 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; PC Euro 1-91/441/EEC 0.08 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; PC Euro 2-94/12/EEC 0.06 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; Conventional 0.80 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; PC Euro 1-91/441/EEC 0.09 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; PC Euro 2-94/12/EEC 0.12 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; Conventional 0.72 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; PC Euro 1-91/441/EEC 0.10 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; PC Euro 2-94/12/EEC 0.18 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; Conventional 0.61 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; PC Euro 1-91/441/EEC 0.12 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; PC Euro 2-94/12/EEC 0.19 MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; PC Euro 3-98/69/EC Stage MI_area 1.A.3.b.i 0701b Passenger Cars; Diesel <2,0 l Passenger Cars; Diesel; Diesel <2,0 l; Conventional 0.50 With this all newly defined sources in road transport now have been associated with technologies. It is wise to now check this import by restoring the database into CollectER III. The screen shot below shows how the selected technologies now would appear in the main window of the application. Note that the width and order of the columns are changed by simply dragging or clicking the column headers. The newly added technologies can be browsed and edited via the Root Data Technologies menu item. Page 66 of 80

67 6.2.3 Emission Factors The final step is the import of emission factors for each technology. To this end, prepare a table of emission factors as shown below. The Technology_Codes should refer to the technologies definitions as described above. The table could be given a range name RoadEmissionFactors and linked to the MS Access database. The query as shown below should perform the import Page 67 of 80

68 Technology_Code Pollutant Pollutant_Code Value Bus_Diesel_Conventional_5 TSP 07_ Bus_Diesel_Conventional_5 PM2.5 07_ Bus_Diesel_Conventional_5 PM10 07_ Bus_Diesel_Conventional_5 NOX 06_ Bus_Diesel_Conventional_5 NMVOC 07_ Bus_Diesel_Conventional_5 NH3 06_ Bus_Diesel_Conventional_5 N2O 05_ Bus_Diesel_Conventional_5 ID(1,2,3,cd)P 03_P Bus_Diesel_Conventional_5 CO 07_ Bus_Diesel_Conventional_5 B(k)F 03_P Bus_Diesel_Conventional_5 B(b)F 03_P Bus_Diesel_Conventional_5 B(a)P 03_P Bus_Diesel_HD_Euro_I_5 TSP 07_ Bus_Diesel_HD_Euro_I_5 PM2.5 07_ Bus_Diesel_HD_Euro_I_5 PM10 07_ Bus_Diesel_HD_Euro_I_5 NOX 06_ Bus_Diesel_HD_Euro_I_5 NMVOC 07_ Bus_Diesel_HD_Euro_I_5 NH3 06_ Bus_Diesel_HD_Euro_I_5 N2O 05_ Bus_Diesel_HD_Euro_I_5 ID(1,2,3,cd)P 03_P Bus_Diesel_HD_Euro_I_5 CO 07_ Bus_Diesel_HD_Euro_I_5 B(k)F 03_P Bus_Diesel_HD_Euro_I_5 B(b)F 03_P Bus_Diesel_HD_Euro_I_5 B(a)P 03_P Bus_Diesel_HD_Euro_II_5 TSP 07_ Bus_Diesel_HD_Euro_II_5 PM2.5 07_ Bus_Diesel_HD_Euro_II_5 PM10 07_ Bus_Diesel_HD_Euro_II_5 NOX 06_ Bus_Diesel_HD_Euro_II_5 NMVOC 07_ Bus_Diesel_HD_Euro_II_5 NH3 06_ Bus_Diesel_HD_Euro_II_5 N2O 05_ Bus_Diesel_HD_Euro_II_5 ID(1,2,3,cd)P 03_P Bus_Diesel_HD_Euro_II_5 CO 07_ Bus_Diesel_HD_Euro_II_5 B(k)F 03_P Bus_Diesel_HD_Euro_II_5 B(b)F 03_P Bus_Diesel_HD_Euro_II_5 B(a)P 03_P Bus_Diesel_HD_Euro_III_5 TSP 07_ Bus_Diesel_HD_Euro_III_5 PM2.5 07_ Bus_Diesel_HD_Euro_III_5 PM10 07_ Bus_Diesel_HD_Euro_III_5 NOX 06_ Bus_Diesel_HD_Euro_III_5 NMVOC 07_ Bus_Diesel_HD_Euro_III_5 NH3 06_ Bus_Diesel_HD_Euro_III_5 N2O 05_ Bus_Diesel_HD_Euro_III_5 ID(1,2,3,cd)P 03_P Bus_Diesel_HD_Euro_III_5 CO 07_ Bus_Diesel_HD_Euro_III_5 B(k)F 03_P Calculate emissions Emissions now can be calculated as indicated in the main text of this document (section ). Page 68 of 80

69 6.3 Public Power plants SOURCE 9 PUBLIC POWER PLANTS This section provides as an example the inventory for the power plants in Middle Earth. For this source category the following information is assumed to be available: the total fuel used for power plants by fuel type the fuel combusted quantities for four power plants in Middle Earth emission reports (E-PRTR type) for three of these power plants for at least one year in the time series. Again we will use direct input into the database in some instances. WARNING Be sure to always make a back up of your CollectER III database before you start working directly in MS Access. Always check your import carefully in the CollectER III tool after you have made changes as described below and assure yourself that the changes are correctly interpreted by the tool and that the result indeed is as intended Available information The table below presents an overview of the activity data for the source category as available for Middle Earth. Plant Region Unit Natural Gas NorthEast Power Angmar plant Eriador 275 MW Gas unit Other plants and units National Total Hard Coal NorthEast Power Angmar plant Eriador 600 MW coal unit MW Coal unit MW Coal unit Mordor Power Mordor 600 MW coal unit MW coal unit MW coal unit Other plants and units National Total Brown coal Saruman Power Plant Nurm 150 MW Brown Coal unit MW Brown Coal unit MW Brown coal unit Harlindon Power Eriador 600 MW Brown Coal Other plants and units National Total The NorthEast Power plant in Angmar has already be included into the database (see section above). We have individual data available for three more power plants (Mordor, Saruman and Harlindon). Comparison with the national energy statistics shows that all brown coal is included in these facility data but some of the natural gas and hard coal is not. In Middle Earth facvilities with units over 50 MW are obliged to report. This means that all units and facilities, not included in the facility level data, will be units below this threshold capacity. We will therefore include these not-included activities as area source. Locations o Export the CollectER III database using the back up menu item and open the exported database in MS Access. Page 69 of 80

70 o Add the three power plants to the Locations table as indicated in the screen dump below. The following must be taken into account: The Location_ID must be unique for each Location The Location_ID of a higher level should start with the id string of the parent You must indicate the correct Location_level for each new record to ensure that the locations tree is correctly built. In the screen dump below a new region Nurm is defined to enable definition of the Saruman Power plant and its three units. Harlindon Power is defined as the second point source in Eriador and Mordor Power as the second facility in Mordor. Sources The sources now can be defined as indicated in the table below. Location Category Detail Fuel SourceName UnitID Comment Plant Region Unit MI_point_E_P1_4 1.A.1.a TJ Natural Gas NorthEast Power Angmar plant Eriador 275 MW Gas unit MI_area 1.A.1.a TJ Other plants and units MI_point_E_P1_1 1.A.1.a TJ Hard Coal NorthEast Power Angmar plant Eriador 600 MW coal unit MI_point_E_P1_2 1.A.1.a TJ 350 MW Coal unit 1 MI_point_E_P1_3 1.A.1.a TJ 350 MW Coal unit 2 MI_point_M_2_1 1.A.1.a TJ Mordor Power Mordor 600 MW coal unit 1 MI_point_M_2_2 1.A.1.a TJ 600 MW coal unit 2 MI_point_M_2_3 1.A.1.a TJ 600 MW coal unit 3 MI_area 1.A.1.a TJ Other plants and units MI_point_N_1_1 1.A.1.a TJ Brown coal Saruman Power Plant Nurm 150 MW Brown Coal unit 1 MI_point_N_1_2 1.A.1.a TJ 150 MW Brown Coal unit 2 MI_point_N_1_3 1.A.1.a TJ 200 MW Brown coal unit MI_point_E_2 1.A.1.a TJ Harlindon Power Eriador 600 MW Brown Coal MI_area 1.A.1.a TJ Other plants and units To find the correct categories or details, you can browse the relevant tables in the database. However be careful not to change any of the data in these tables while doing so. The sources can now be added to the Sources table by either typing them one by one or by copying and pasting from the table above. Please note that the database will not allow a Page 70 of 80

71 second Source with the same Location, Category, Detail and Fuel. If you try to copy in the NorthEast Power plant, an error message will appear. In case a long table of sources is to be imported it might be advisable to use a specific append qury in the database, reading directly from an Excel data table via a link in the database. See the documentation and help function of MS Access to perform the import along these lines. After the import final records in the Sources table will look like the screen dump below. Please note that the Source_ID are generated automatically by the MS Access application. The values of these IDs depends on the history of the database file and might differ from what is seen below. It might be wise to import (menu item File Restore) the database into CollectER III now to see whether the sources are correctly defined. The best view for this is now to use the Category filter and select 1.A.1.a Public Power. The screen dump below shows that the sources indeed have been imported correctly. Page 71 of 80

72 Activity data To import the activity data we will use an MS Excel data range, linked to the CollectER III MS Access database. We assume that the data as given above are available in an MS Excel worksheet as given below. This data in a cross table by year needs to be converted into a sequential data table as shown below. Page 72 of 80

73 MS Excel includes a number of functions that could relatively easily perform this task. The table below shows the formulae to be included in the second row of the worksheet to read the data from the table in the Sources worksheet. Row Column Location Category Detail Fuel Year Value =INDIRECT(ADDRESS($A2+1,$B2+11,,,"Sources")) =INDEX(Sources!$L$1:$AH$1,$B2) =INDIRECT(ADDRESS($A2+1,COLUMN(F1)- COLUMN($B$1),,,"Sources")) =INDIRECT(ADDRESS($A2+1,COLUMN(E1)- COLUMN($B$1),,,"Sources")) =INDIRECT(ADDRESS($A2+1,COLUMN(D1)- COLUMN($B$1),,,"Sources")) =INDIRECT(ADDRESS($A2+1,COLUMN(C1)- COLUMN($B$1),,,"Sources")) =INT((ROW()-ROW($G$1)- 1)/COUNTA(Sources!$B$2:$B$189))+1 =MOD((ROW()-ROW($G$1)- 1),COUNTA(Sources!$B$2:$B$189))+1 The first and second columns calculate the rows and columns where the activity data are to be read. The results of these are used to identify the data records, the year and the activity rate for each year ad each point source location. Page 73 of 80

74 Be sure to copy this row far enough downwards to ensure that all data are de-crossed. Note that the year column will contain zeros after all data columns have been de-crossed. Then link the worksheet ActivityData to the CollectER III database (see the MS Access documentation on how to do this). As shown in the screen dump below, the MS Excel data are now available in the CollectER III database: The query below finds each Source_ID in the Sources table with each of the new activity rates. To prevent double entries, a second query checks for each activity record whether the source already has an activity rate included for each year. If not, it appends the record to the ActivityRates table. This is done by the following query: Page 74 of 80

75 It is a good idea to check the data import at this stage by restoring the new version of the database into the CollectER III tool. The following screen dump shows how the data now should look like in CollectER III. Note that the activity data for the sources imported via this procedure are expressed as TJ and those of the power plants already in the database in GJ. The emissions calculation algorithms in CollectER III take care of this. Technologies and emission factors Import of technologies and emission factors for the power generating activities in the country into the database is described above. It includes the following steps: Page 75 of 80

76 o Identify the technologies applied. A Technology is essentially a unique set of emission factors, connected to a defined practice or activity or even installation. Emission factors can be obtained from Available facility emissions data; it is necessary to convert any measured emissions to facility specific emission factors, using the activity data. When not all pollutants and gases are measured, activity data are needed to estimate those emissions not measured, using emission factors from literature Activity data are also needed in most cases for the reporting to the Climate Convention and the EU Monitoring mechanism. Technology specific emission factors ( Tier 2 ) from the EMEP/EEA Guidebook or other scientific publications Default ( Tier 1 ) emission factors if no further technical information is available. o Import the technologies and emission factors into the database; please note that some technologies might already be defined and used in other sources. It is the responsibility of the user to keep track of those to avoid redundancy in the database. TIME SERIES OF EMISSION MEASUREMENTS In a number of cases, annual emission measurements will be available. Since measurements will unavoidably contain some errors and uncertainties, the calculated facility level emission factors will vary from year to year. As long as there are no modifications to the processes in the facility, one would generally expect the emission factor to not change over time. There are two ways of dealing with this: From the scientific point of view the best approach here would probably be to use an averaged emission factor for all years, derived from the annual measurements. In practical terms, the users of the inventory might wish exactly recognize the measured data for each facility. In this case a separate technology for each year in the inventory should be defined. It is a matter of taste and choice how to solve this in the inventory. Technology selection The final step again is to select one or more technologies for each source in each year. This procedure has been described above. Page 76 of 80

77 7 References 1 TFEIP (2009), EMEP/EEA Emission Inventory Guidebook 2009, the 2009 Revised Guidebook, in preparation, available at or via the TFEIP home page 2 IPCC (1996), Revised 1996 IPCC Guidelines for National Greenhouse Gas Inventories, 3 IPCC (2000), Good Practice Guidance and Uncertainty Management in National Greenhouse Gas Inventories, 4 IPCC (2003), Good Practice Guidance for Land Use,Land-Use Change and Forestry, 5 IPCC (2006), 2006 IPCC Guidelines for National Greenhouse Gas Inventories, 6 IPCC National Greenhouse Gas Inventories Program, Emission Factor Database, 7 US Environmental Protection Agency, Clearinghouse for Inventories & Emissions Factors, 8 General Conference on Weights and Measures, (1960), Resolution 12 of the 11th meeting of the CGPM,, Page 77 of 80

78 Appendix A New inventory using existing CollectER II inventory or inventories 1. Introduction A country might already have compiled a series of inventories in the earlier CollectER II version. Such inventories are annual only and need to be combined into one database structure as used in CollectER III. In addition the structure needs to be built in the NFR source categories, rather than in the SNAP nomenclature. This annex provides an outline on how to do this. Importing the CollectER II data into CollectER III will in a number of cases lead to problems: Consistent codes Since all the CollectER II annual databases are in principle independent complete relational database structures, users can select and in some cases have selected different solutions for the same problem in different years. This has occurred for fuels, locations and even SNAP classifications in several countries. Obviously, when importing such data into one multi-annual database one of such solutions should be selected for all the years in the database. In quite a number of cases, users of CollectER II have defined their own extensions to the SNAP and fuel codes. CollectER III is more strict on this to increase inter-country comparability and to provide unambiguous links to the reporting formats. Obviously, this has to be repaired by the inventory compiler. The import procedure provided in this annex supports the user in identifying such issues but leaves the solution to the compiler. Consistent Emission Factors National experts had to enter emission factors for every pollutant independently for all years in the time series. Due to typos, but also due to different rounding, emission factors for the same source could be slightly different in different years. In several cases this is not the intention of the expert, but induced by the process. Furthermore, the sets of emisison factors might not include all pollutants for all years. An automatic import process therefore might generate sets of emission factors, grouped into the technologies of the new database structure of CollectER III, that are actually not meant as different technologies. The CollectER III tool therefore provides a Join Technologies function that allows the user to replace such a series of unintentionally different technologies by one only. This will increase time series consistency. Consistent Units The choice and even the definition of units between different annual CollectER II databases is not always the same in all years. CollectER III requires the user to harmonize these. Page 78 of 80

79 Furthermore, CollectER III makes a distinction between mass units for emissions and activity units to express activity rates. In some cases we have found issues with the choice of units in the earlier versions, leading to errors in the imported database. The CollectER II import tool therefore also checks the units used in all years. Since import of earlier versions of CollectER databases into CollectER III is a once only activity and will be different in details for all countries, support will be needed and will be available from the CollectER III help desk. 2. Procedure If CollectER II database files of the mdb type are available, it is possible to import content of such files into the new CollectER III version using Import CollectER II function of the Tools Import CollectER II function. This will import both the structure and the data. During import procedure a series of checks is performed on categories, units, pollutants and fuels. As a first step the locations are imported. After successful import of locations the procedure proceeds with the import of facilities (point sources) that are defined standard way, i.e. with category identifier, location identifier, activity rate and related emission factors. The next step is import of facilities with some or all emission measured so called direct emission. Processing of such emissions depends on the fact if there are only measured emissions available or if there is mix of measured and calculated emissions available for the source. 3. Join Technologies Same or similar technologies may be joined into single technology using Join Technology Mechanism. In such case all technologies from the set of joined technologies will be replaced with single technology identifier according to decision of the national expert or other responsible person. Page 79 of 80