The transaction log

Decision 16 CP.10 renamed the independent transaction log as the international transaction log .

A live production environment for the ITL will be made available when the connection of the first registry or the CITL has been approved.

international transaction log (2005)

Schedule An indicative schedule and key dates, as specified in the RFP, for the development and operation of the ITL is set out below

Report of the administrator of the international transaction log under the Kyoto Protocol

The COP MOP may wish to refer the consideration of the information contained in this report to the Subsidiary Body for Scientific and Technological Advice (SBSTA) and provide guidance, as necessary, to the secretariat concerning the fulfilment of its functions as ITL administrator.

CMP.1 Issues relating to the implementation of Article 8 of the Kyoto Protocol 1 (FCCC KP CMP 2005 3 Add.2)

The African Group would be expected to nominate a replacement.

Scope of the note This first annual report of the administrator of the ITL provides information to the COP MOP on progress made towards implementing the ITL.

The SBSTA further noted that the ITL administrator will, in accordance with decision 16 CP.10, prepare common operational procedures, including those relating to the testing and initialization of communications by registry systems with the ITL.

After the successful completion of all initialization testing for a registry or STL, the operator will recommend approval of the connection to the ITL administrator.

Staff of the RDA programme will manage this external work, including through monitoring and review of activities and the provision of guidance and approval, as appropriate, at key stages of the work.

The first meeting will provide updated information on progress with the implementation of the ITL.

Report of the administrator of the international transaction log under the Kyoto Protocol (Agenda item 6)

Once the connection of the first registry or the CITL has been approved, the live production environment for the ITL will be made available to which registries and the CITL will maintain their connections on an ongoing basis.

This process has been designed to progress from simple to complex activities and will ensure the capability and suitability of registry systems and their hosting environments through

This peer review is to focus on the software code of the ITL in order to assist the ITL administrator in ensuring that the ITL meets required specifications.

Technical activities Development activities The secretariat has issued a request for proposal (RFP) on the ITL.

The developer and operator will need to work closely to ensure that the ITL software and the data centre and network infrastructure are complementary.

A steering group, consisting of representatives of the ITL administrator, the operator and the developer, is to provide for the coordination, cooperation and consistency between these parties.

The precise schedule of the ITL implementation is subject to elaboration with the vendor in the course of the initial planning and preparation of contractual arrangements with the secretariat.

Documentation relating to the ITL testing, including test results and the acceptance criteria used, are to be shared through the RSA Forum and will be made public through the UNFCCC web site, as appropriate.

The resource requirements for the development of the ITL are being provided through contributions to the UNFCCC Trust Fund for Supplementary Activities.

All references to the independent transaction log in this decision will therefore be amended in the report of the COP MOP.

The sufficiency of these contributions may need to be re assessed in early 2006 in the light of the procurement process to select contractors for the development and operation of the ITL.

The only STL currently foreseen is the Community Independent Transaction Log (CITL) implemented under the European Union emissions trading scheme.

Introduction Mandate The Conference of the Parties (COP), by its decision 19 CP.7, requested the secretariat to establish and maintain the international transaction log (ITL) to verify the validity of transactions undertaken by registries established under decisions 17 CP.7 and 19 CP.7.

Resource requirements for the operation of the ITL and the facilitation of the RSA Forum are provided for in the programme budget for the biennium 2006 2007.

The secretariat wishes to draw technical support for its facilitation of the RSA Forum from the operator of the ITL.

It recognized that this indicative schedule may be revised in the context of more detailed planning once a technical developer has been selected for the ITL.

The scheduling of the initialization testing and the liaison with registry administrator will be undertaken by the service desk of the operator, under the management of the ITL administrator.

Indicative scale of contributions from Parties to the Kyoto Protocol for the biennium 2006 2007

(d) Simplification of the administration of transaction and lower transaction costs.

The RFP contains detailed specifications for the development of the ITL, including the technical specification of the data exchange standards and a specification of the core and periphery software for the ITL, and for the tasks required in order to complete the work.

After the ITL has been established, the developer will commence a long term phase of its contract to provide maintenance and support to the ITL, including for minor changes and upgrades, on an ongoing basis until 2015.

The scheduling of the pilot testing and the liaison with participating administrators will be undertaken by the service desk of the operator, under the management of the ITL administrator.

Commercial transactions

It is envisaged that the Forum will need to meet twice a year, although meetings may need to be more frequent during the initial establishment of the ITL and registries, and that specialized working groups would meet more frequently.

The ITL administrator is to develop, in cooperation with the other administrators, procedures and practices that complement the data exchange standards and may be implemented by administrators of all registry systems.

Each correspond with exactly one other Update Log Record (although the corresponding update log record is not typically stored in the Compensation Log Record).

Transaction costs and efficiency

Financial transactions

The transaction log shall verify that there is no discrepancy with regard to the requirements of paragraphs 41 to 53 above as part of its automated checks set out in CMP.1 (Modalities for the accounting of assigned amounts).

Changelog