1 / 17

Data Exchange Standards for the interaction with the ITL 08 November 2004 Bonn, Germany

Data Exchange Standards for the interaction with the ITL 08 November 2004 Bonn, Germany. Peggy Quarles Perrin Quarles Associates, Inc. peggyquarles@pqa.com. Reconciliation. The process by which data from different registry systems are compared and inconsistencies resolved.

tavia
Download Presentation

Data Exchange Standards for the interaction with the ITL 08 November 2004 Bonn, Germany

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Exchange Standards for the interaction with the ITL 08 November 2004 Bonn, Germany Peggy Quarles Perrin Quarles Associates, Inc. peggyquarles@pqa.com

  2. Reconciliation The process by which data from different registry systems are compared and inconsistencies resolved.

  3. Why do you need Reconciliation? • Credibility • Data accuracy • Process to identify and correct problems

  4. Reconciliation Registry and ITL agree on timing HOWEVER, if discrepancies exist… …an alternate process takes place.

  5. Reconciliation (continued) If Data discrepancies exist… …the ITL works to isolate and identify units in question to facilitate the final step in the reconciliation process… ITL

  6. Key Elements of Reconciliation • Good communication • Flexibility in timing, starting point and phases • Technical feasibility

  7. Notifications A Notification is a communication to a registry from the ITL about a required or recommended action involving unit transactions.

  8. Types of Notifications • Net source cancellation • Non-compliance cancellation • Impending tCER or lCER expiry • Reversal of storage for CDM Project • Non-submission of Certification Report for CDM Project • Excess issuance for CDM Project • CPR level problem • Unit carry-over

  9. Elements of a Notification • Notification ID • Number of Units • Unit Blocks • Update or status report for earlier notification

  10. Typical Notification Process ITL sends notification of transaction requirements including Notification ID. ITL Administrator initiates notification. Registry responds with transactions including the Notification ID. ITL monitors compliance with transaction requirements. Registry ITL reports to CDM Executive Board and other entities ITL ITL send updates to Registry indicating progress or completion of requirements

  11. Other Requirements in the DES • Data Records • Change Management • Registry Testing and Initialization

  12. What do Registry Systems Record? • All transactions, including detail about unit blocks and response codes • All reconciliation messages • All notifications • All internal activity (who changed what and when) • A message archive (storage of XML files)

  13. Change Management Change management is the process by which the Data Exchange Specifications can be modified.

  14. Change Management • Changes or enhancements are unavoidable • Changes will be minimized to provide stability and reduce costs • Registries and ITL will cooperate to implement changes methodically • ITL Administrator will have key role in coordinating and communicating regarding changes

  15. Registry Initialization • Initialization is the process of bringing a registry system on-line, allowing it to fully participate with the ITL in a trading scheme. • This is a technical process, not related to eligibility.

  16. What does a Registry Need to Do? • Establish and test communications • Coordinate and perform testing with ITL, per Annex H • Develop and submit documentation • Provide government account information

  17. Required Registry Documents • Backup and Recovery Plan • Disaster Recovery Plan • Security Plan • Time Validation and Data Logging Plans • Version and Change Management Plan • Test Plans and Reports • Operational Plan

More Related