Back to Course

CoM SSA Sustainable Energy Access and Climate Action Plan (SEACAP) course

0% Complete
0/0 Steps
  1. MODULE 1: Setting the scene
  2. Lesson 1.1: Introduction to the CoM SSA initiative
    2 Topics
  3. Lesson 1.2: Introduction to the SEACAP
    3 Topics
  4. Lesson 1.3: Climate change and cities in Africa
    2 Topics
  5. MODULE 2: SEACAP mitigation pillar
  6. Lesson 2.1: Key concepts in climate change mitigation
    1 Topic
  7. Lesson 2.2: Introduction to the mitigation pillar
    2 Topics
  8. Lesson 2.3: The SEACAP development process for the mitigation pillar
    1 Topic
  9. Lesson 2.4: Emissions inventories: GHG emissions
    4 Topics
  10. Lesson 2.5: Developing a Baseline Emissions Inventory (BEI)
    3 Topics
  11. Lesson 2.6: Tools for BEI development
    2 Topics
  12. MODULE 3: SEACAP access to energy pillar
  13. Lesson 3.1: Key concepts in access to energy
  14. Lesson 3.2: Introduction to the access to energy pillar
    2 Topics
  15. Lesson 3.3: The SEACAP development process for the access to energy pillar
  16. Lesson 3.4: Data collection
    3 Topics
  17. Lesson 3.5: Developing an Access to Energy Assessment (AEA)
    2 Topics
  18. Lesson 3.6: Setting an energy vision and targets
    3 Topics
  19. Module 3.7: Planning energy actions
    3 Topics
  20. MODULE 4: SEACAP adaptation pillar
  21. Lesson 4.1: Key Concepts in climate change adaptation
    1 Quiz
  22. Lesson 4.2: Introduction to the adaptation pillar
    2 Topics
    |
    1 Quiz
  23. Lesson 4.3: The SEACAP development process for the adaptation pillar
    1 Topic
    |
    1 Quiz
  24. Lesson 4.4: Developing a Risk and Vulnerability Assessment (RVA)
    1 Quiz
  25. Lesson 4.5: Setting an adaptation vision and sectoral targets
    2 Topics
    |
    1 Quiz
  26. Lesson 4.6: Planning adaptation actions
    2 Topics
    |
    1 Quiz
  27. MODULE 5: Steps to take before you implement your SEACAP
  28. Lesson 5.1: Next steps for prioritised actions
  29. Lesson 5.2: Categorising actions to access external finance
    2 Topics
    |
    1 Quiz
  30. MODULE 6: Communicating your SEACAP
  31. Lesson 6.1: Designing your SEACAP
    3 Topics
    |
    1 Quiz
  32. Lesson 6.2: Communicating your SEACAP to key stakeholders
    1 Topic
    |
    1 Quiz
  33. MODULE 7: Reporting your SEACAP
  34. Lesson 7.1: Introduction to reporting your SEACAP
    3 Topics
    |
    1 Quiz
  35. Lesson 7.2: Introduction to reporting the mitigation pillar
    4 Topics
    |
    1 Quiz
  36. MODULE 8: Integrating your SEACAP into existing planning processes
  37. Lesson 8.1: Integrating your SEACAP actions into local level plans
    1 Topic
  38. Lesson 2.7: Setting mitigation targets
    2 Topics
  39. Lesson 2.8: Planning mitigation actions
    1 Topic
  40. Lesson 7.4: Introduction to reporting the access to energy pillar
    3 Topics
  41. Lesson 7.3: Introduction to reporting the adaptation pillar
    3 Topics
Lesson Progress
0% Complete
What is the Proxy Data Tool?
  • The Proxy Data Tool (PDT) has been developed to assist local governments in sub-Saharan Africa to compile an inventory following the Global Protocol for Community-scale Greenhouse Gas Inventories (GPC) and the GCoM Common Reporting Framework.
  • The tool was developed under the CoM SSA initiative in 2020 to enable the development of GHG inventories in cities with limited local data and resources
  • The PDT follows the BASIC reporting standard outlined in the GPC. As such it focuses on Stationary energy (scope 1 and 2), Transportation (scope 1 and 2) and Waste (scope 1 and 3) sectors, and does not include agriculture, forestry and other land use (AFOLU), and industrial processes and product use (IPPU).
  • It does this using available national and international data that are downscaled as required – this downscaling utilises population and GDP data if both are provided by the user, otherwise it utilises population data.
  • It is assumed that all solid waste and wastewater generated within the region is treated within the region (e.g. solid waste generated by households is landfilled within the region) and therefore no Scope 3 waste emissions occur.
  • Emission factors and global warming potentials are IPCC defaults.
Why use the Proxy Data Tool?
  • The Proxy Data Tool was developed as an add-on to the City Inventory Reporting and Information System (CIRIS) Tool – it integrates with the CIRIS spreadsheet and helps users to auto-complete the spreadsheet. 
  • The inputted data automatically carries forward into the CIRIS Tool. 
  • All the sections of the tool are automatically pre-populated, including the method and data quality sections.
  • The developed tool is designed to ensure it is as easy for users as possible. This means that only basic census data is required as a very minimum to calculate an inventory.

However, to improve the accuracy in regions where data are available, it also allows users to review the data and enter their own data where these are available.

 

What is inside the Proxy Data Tool?
  • The PDT includes two additional data input sheets beyond the standard CIRIS Tool spreadsheets. 
  • The first additional sheet requires users to input basic regional and census data (country, year of inventory, regional land area, regional population and ideally, local GDP). Based on this data, the PDT uses built-in data to determine default values for the city or region’s GHG inventory. 
  • The second additional sheet presents these calculated default national and regional values, which can be overridden with updated or more specific local data when available. This data, along with its reference sources, populates the CIRIS Tool spreadsheets to compile the region’s GHG inventory. 
  • The PDT conforms to BASIC-level GPC reporting, though users can add additional emission sources (e.g., IPPU and AFOLU sectors) directly into the CIRIS tool sheets.  
  • There are more sheets in the PDT that are placed after the standard CIRIS Tool sheets. These record all the data with which the PDT is built/ modelled. It can be interesting to look at these sheets to take a deep dive into the tool’s data and where it all comes from.