1 / 14

Andrew Howard UNFCCC secretariat www.unfccc.int ahoward@unfccc.int

Progress in implementing the international transaction log Consultations on registry systems prior to SBSTA 22 Bonn 13-14 May 2005. Andrew Howard UNFCCC secretariat www.unfccc.int ahoward@unfccc.int. Overview. Technical design work Applicability of the CITL for ITL development

delores
Download Presentation

Andrew Howard UNFCCC secretariat www.unfccc.int ahoward@unfccc.int

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. Progress in implementing the international transaction log Consultations on registry systems prior to SBSTA 22 Bonn 13-14 May 2005 Andrew Howard UNFCCC secretariat www.unfccc.int ahoward@unfccc.int

  2. Overview Technical design work Applicability of the CITL for ITL development Development schedule Initialization of registries

  3. Data exchange standards Basis for the ITL established in the standards • Transaction types • Checks to ensure conformity with rules • Reconciliation to eliminate inconsistencies • Electronic communications with registries • Data records to be kept • Administrative processes Version 1.0 of the technical specifications for the standards

  4. ITL technical design Version 1.0 (draft #7) of the ITL technical design specifications • Database design and structure • Logical flows for transaction and reconciliation processes • Detailed specifications of coding components • Detailed methods for ITL checks • Links to other databases for reference information - Compilation and accounting database - CDM information system - JI information system (track 2) • Detailed specifications for ITL notifications

  5. ITL development tasks • Review ITL technical design • Create database • Develop programme code and an administrator interface • Establish hardware environment • Testing (individual components and overall functionality) • ITL deployment in a production environment • Initialization of secure communications with registries • Documentation (plans, guides, training) • Public website

  6. A head start through the CITL EU ‘Community Independent Transaction Log’ • Performs checks on transactions under the EU trading scheme • Modelled on Kyoto’s ITL • Development based on ITL technical design CITL programme code provides a robust basis for the ITL • Strong architecture for transactions, data integrity and checks • Around half of required ITL functionality contained in CITL code • Challenge is to safely and seamlessly adapt, remove and add code

  7. Current EU communications EU checks Nationalregistry Nationalregistry Nationalregistry EU Member State registries EU transaction log (CITL) EU communications hub

  8. Future Kyoto Protocol communications EU transaction log (CITL) Other supplementarytransaction logs EUchecks Otherchecks UNchecks Nationalregistry Nationalregistry Nationalregistry CDMregistry Nationalregistry Nationalregistry EU Member State registries Other Kyoto registries Kyoto international transaction log Kyoto communications hub

  9. Adaptation of CITL code • Create new database or modify CITL database • Add web service communications (tCERs and lCERs, notifications, STL communications) • Add functions to interact with STLs (routing and processing communications, reconciliation, data sharing) • Add transaction types (replacement, expiry date change) • Add ITL notification functions and running totals • Modify existing checks and add ITL-specific checks (tCER and lCER checks, transaction-specific checks, reconciliation checks) • Remove unneeded CITL code (account management, EU-specific checks, EU supplementary unit and transaction types)

  10. Testing the ITL • Unit testing on individual code and database components • Integration testing of compiled ITL code (with registries and STLs) - Cover all transaction, reconciliation and notification cases - Cover all ITL check cases • Regression testing (after fixes made through earlier testing) • Performance testing (for efficiency improvements) - In actual hardware/software environment - Under realistic load scenarios

  11. Indicative ITL development schedule

  12. Initializing registries • Administrator training • Receipt and review of initialization documentation • Establishment of VPN connection • Transaction and reconciliation tests (web services tests) • Tests for other data submission to ITL • Full registry tests • Activation of production environment connection Concentrate initially on registries not associated with an STL

  13. The special EU case CITL initialization • Similar process as for registries • Establishment of secure ITL-CITL connection • Data migration schedule (coordinated with EU registry migration), including standardized data migration procedures and scripts Migration of registry connections from the CITL to the ITL • One migration round or several? • Coordination through the administrators cooperative forum

  14. Communications with administrators Communications and planning through the cooperative forum • ITL requirements • Planning and schedules for development, testing, deployment, initialization (including data and registry migration in the EU case) Support for initialization • Provision of ITL prototype • VPN purchase/configuration support for registries • Further guidance on documentation • Initialization support being incorporated in contractor selection

More Related