The Harmonized OneWindow Reporting of Energy Use, Production and Greenhouse Gas Emissions Informatio

1
The Harmonized One-Window Reporting of Energy
Use, Production and Greenhouse Gas Emissions
Information in Canada

• Bob Pagnutti
• Assistant Director,
• Manufacturing, Construction and Energy Division
• Statistics Canada
• Presentation to the Oslo City Group Meeting on
  Energy Statistics
• February 8, 2006

2
What are some of the common things all users want
from energy statistics?

• Information has to be
• Timely
• Of high quality
• Comprehensive
• Coherent with other information
• Consistent
• Reliable
• Cost effective and minimize response burden

3
What additional qualities were regulatory
authorities looking for from the System?

• No surprise, the regulators wanted the same thing
  as most users as seen on the previous slide PLUS
• They also wanted a partner that was trusted and
  respected by all stakeholders to build and house
  the system
• In Canada the environment is the responsibility
  of both Federal and Provincial levels of
  government
• It would be a multi-phase program starting with
  the collection of Greenhouse Gas Emissions
  information and expanding into energy and
  production
• The vehicle had to be flexible to collect
  supplementary information for some jurisdictions
• And the system had to have separation of
  statistical vs. regulatory care and control for
  the regulators audit, verification and
  enforcement purposes

4
What were some contributions from industry?

• Industry only wants to report once to all levels
  of government entitled to see their information
• The System should minimize their reporting and
  compliance costs
• KISS
• Of utmost importance -- Protect their
  Confidential Business Information
• In transit
• In storage

5
What is being achieved

• Harmonized One-Window reporting of Greenhouse Gas
  Emissions, Production and Energy Use for LFEs
• Timeliness filing opens March 15 and closes June
  1
• Of high quality CV 0 information subject to
  intense scrutiny
• Comprehensive content developed and tested
  extensively with industry closed some
  statistical gaps
• Coherent bringing together at the plant level
  energy, production, emissions
• Consistent harmonized concepts and improved
  industrial classification of units
• Reliable Reported information is subject to
  audit and verification.

6
What is being achieved (cont)

• Operator had to be trusted by all stakeholders
• Statistics Canada -- not a provincial regulator,
  not a federal regulator, but the National
  Statistics Agency for Canada
• Extensive data gathering experience working with
  industry
• Extensive experience developing leading edge user
  friendly applications
• Had to meet their audit, verification and
  enforcement needs
• the Statistics Act Section 12
• Report once to all levels of government
• the Statistics Act Section 12
• Keep the cost of reporting down
• Possible alternative to costly 3rd party
  verification
• Ability to Protect and Secure Information
  Guaranteed by the Statistics Act
• Use of SSA and STC PKI
• Use of STC to house island where information is
  stored

7
How it is working out

• 2004
• STC built an information website for reporters, a
  reporting vehicle and a secure multi-jurisdictiona
  l GHG data warehouse in a little under 9 months
  at a cost of 1.1M Cdn working with industry,
  ENGOs and policy departments of Federal,
  Provincial and Territorial governments
• Extensive testing was done with industry
• 2005
• Collected 2004 GHG emissions information from
  LFEs
• 2006
• Collecting 2005 GHG emissions information from
  LFEs
• Starting work with industry to establish an XML
  standard to report emissions, energy use and
  production data

8
The Legal Framework

• Data jointly collected by
• Statistics Canada
• Statistics Act (Data sharing provision)
• Environment Canada
• Canadian Environment Protection Act
• The Government of Alberta
• Climate Change and Emission Management Act

9
How it looks on paper
10
ApplicationFeatures

• On-line registration
• Need to dynamically assign unique facility
  identifiers to allow registration and reporting
  in a single session
• Security feature to prevent automated
  registration
• Registration information transferred to reporting
  application
• Save and resume functionality at any time while
  in the application
• Information from partially completed
  questionnaires encrypted and transmitted
• Encrypted information stored in a database in XML
  format
• Reporter resumes the session using the password
  they created
• Information is decrypted on the clients browser
• Questionnaire is repopulated

11
ApplicationFeatures (cont)

• Use of embedded calculations and data transfers
  within the application to minimize transcription
  errors and ensure consistency
• Use of imbedded edits to detect reporting
  anomalies, transcription errors and other
  inconsistencies
• Mechanism for the reporter to certify the
  information is correct for each jurisdiction
  under penalty of law
• Reporting in subsequent years the reporter can
  permit their tombstone information from the
  previous year to be pre-populated into the next
  years e-form

12
ApplicationFeatures - Auto. Calculations of
Totals

• Client side calculation of CO2 equiv. using
  JavaScript

13
ApplicationFeatures - Data Verification

• Reporters can review their report for missing
  fields

14
ApplicationFeatures Data Certification

• PKI can support digital signatures
• Business processes to confirm identity of
  reporters not in place
• Signed paper Statement of Certification used for
  non-repudiation in Phase One
• Collected information transferred from
  application into a printable HTML page

15
(No Transcript)
16
Lessons Learned

• Statistics Canada is a valued partner to all
  stakeholders
• Previous investment in EDR could be leveraged
  significantly
• Important to build strategically, functionality
  can be applied in other areas
• Lead with examples prototyping can speed
  development
• Conduct multiple rounds of usability testing
• Keep your ear to the ground for potential
  technical problems and be ready to react quickly
  and effectively
• Help line, Stakeholder involvement, Options for
  EDR
• Anticipate and plan for future reporting
  requirements well in advance

17
Questions/Discussion
?
?
?
?