Overview. Implementation of the international transaction log. Overall ITL role and approach. Support from ITL developer/operator

Transcription

1 Implementation of the international transaction log Andrew Howard David Sturt Climate Change Secretariat 1 st meeting Registry System Administrators Forum Bonn, Germany April Overview Overall ITL role and approach Support from ITL developer/operator Working with other systems Plans and schedules Key interaction points with other systems 2 1

2 Overall approach 3 ITL twin purposes Provides certainty of delivery under carbon market trading Occupies central location in network of national registries Supports the secure communications between systems that coordinate transaction and reconciliation processing Ensures that only Kyoto-valid transactions may be undertaken Safeguards integrity of Kyoto compliance accounting Checks that transactions conform to Kyoto Protocol rules Tracks international movement of emission allowances Keeps account of allowance holdings for each Annex B Party Supports comparison of allowance holdings and actual emissions 4 2

3 ITL tasks Communications hub connects all registries Checks transactions against - technical standards for data exchange (46 checks defined) - policy-related rules (95 checks defined) Builds up records of holdings and transactions which mirror registries Regularly reconciles ITL records with records Notifies registries of required transactions (eg cancellation) Feeds EU transactions to the CITL for supplementary checking 5 Current EU systems EU transaction log (CITL) Communications hub EU checks EU Member State registries 6 3

4 Future Kyoto Protocol communications EU transaction log (CITL) EU checks Other supplementary transaction logs Other checks Kyoto international transaction log (ITL) Communications hub UN checks CDM EU Member State registries Other Kyoto registries 7 Tight implementation schedule ITL is required to connect EU trading scheme into Kyoto trading Allows CDM project credits to be used by EU companies Eases the meeting of EU company-level emission targets EU governments have promised this link to industry for phase 1 Market and political pressure is building Awareness is growing Registries to be connected and operational by April

5 ITL characteristics Full compatibility with data exchange standards Transaction validation is real-time Fully resilient architecture - secondary fail-over facilities - availability set at 99.9% (9 hours downtime per year) Sized to cope with peak loads Scalable to meet evolving market needs Service desk to run the ITL and support registries and the CITL 9 Working with the service partner External service provider being selected - developer services - operator services Partnering approach with the provider Shift from development to operational focus over time Contract period of 10 years Flexibility provisions integrated in the contract - robust governance mechanisms - biennial contract reviews 10 5

6 Developer services Requirements review Software design and development Testing (with final acceptance by secretariat) System documentation Support ITL operator - hardware and software configuration - software deployment and operation - training (especially service desk staff) - 2 nd line support to the service desk - initialization support Ongoing maintenance and support (after warranty period) 11 Operator services Primary data centre infrastructure Secondary (fail-over) data centre infrastructure Internal and external networks Support registries and CITL - initialization of connections - technical administration of connections - 1 st line service desk support Strategic technology support to secretariat - sub-contracts and procurement - monitoring and change processes - evolution of data exchange standards - RSA Forum activities 12 6

7 Contract governance Robust governance mechanisms integrated in contract Involves secretariat, developer and operator representatives ITL steering group (meets monthly) - oversees scope, budget, expenditure, issues and risks - mandates and coordinates actions - monitors progress and ensures requirements are met ITL change forum (meets as needed) - reports to steering group - coordinates change requests 13 Working with registries Collaboration tools during development (issue tracking) Operator service desk Focus for day-to-day ITL-RSA communications Coordination of tasks (scheduling, testing, reconciliation, etc) Problem management (reporting, escalation and resolution) Support in time zones from Canada to New Zealand Skeleton services for pilot testing, full services for initialization RSA Forum Cooperation on procedures and longer term development Common procedures, recommended practices, information sharing 14 7

8 Schedules and interaction 15 Schedule overview First live at end M8 CITL and EU registries live by end of March 2007 Project starts 16 8

9 Project initiation Key task to elaborate detailed resource plans for project management Other parallel first steps include Development items - specification verification by vendor - agreed specification by mid-m2 Service and support items - service Level Agreement developed - SLA forms basis of service and support ITL platform items - agree hardware and software configuration - provide network connectivity requirements to registries (end M1) 17 Development Using typical approach to construction for a well specified system - software build and test - development of test scripts from requirements specifications Deliverables include - pilot version of ITL software with limited functionality - version 1 of ITL software for initialization and live operation - documentation - training and assistance to operators and service desk Acceptance testing by operator and secretariat 18 9

10 Testing Testing from many perspectives to ensure successful operation Development (unit, integration and acceptance testing) User interface (usability testing) Performance (load, soak, stress and volume testing) Security and access control (penetration testing) Fail-over and recovery testing Installation and configuration testing Operability testing CITL migration testing 19 ITL platform Establishes an infrastructure ready to receive ITL application Takes place in parallel to software development work Scalable high availability design across two data centres Activities include procuring, installing, configuring and testing - computing security and network hardware - network connectivity - operating systems and middleware Platform will integrate with operations management infrastructure Includes the build and test of live environment 20 10

11 ITL platform components registries Private lines Primary network Admin app. LIVE PRODUCTION environment DB Server Secondary network registries Public internet ITL comms hub ITL comms hub Load balancing ITL app server ITL app server clustering European Commission To CITL Admin app. replication BACKUP environment DB Server Secretariat To UNFCCC ITL comms hub ITL comms hub ITL app server ITL app server Load balancing clustering Resilient VPN over Internet or private lines NW switches, firewalls, load balancing, External-facing systems in DMZ Back-end systems on secure internal network 21 Interfaces to the secretariat ITL interfaces to secretariat systems to provide or extract data Not on critical path, though timely implementation important The CDM is initialized as with other registries 22 11

12 Service and support Developed based on the Service Level Agreement (SLA) Well integrated with ITL platform Activities to build the support function include - develop call handling and escalation procedures - prepare and train the service desk - develop problem and change management procedures - develop communication procedures - develop knowledge base Pilot testing and initialization add to knowledge base 23 ITL pilot testing To test the ITL with registries and give feedback to ITL development ITL pilot testing participants and schedule to be confirmed early Use early version of ITL (limited subset of functionality) Test ITL against representative variety of software Service desk involvement with registries starts (with knowledge base) 24 12

13 Initialization overview Three tier initialization process - review of registries operation by document review - basic connectivity testing - functional tests Staggering of tests to spread work load and reduce complexity Coordinated and support by service desk CDM to be initialized first CITL and EU registries initialized in a second stage - initialized in same period but not necessarily simultaneously - Activation in one group (creates heavier process and work) Non-EU registries expected to be initialized later 25 Preparing for initialization RSA activities Assign initialization contact people Submit documentation to ITL Administrator Provide government account information (cancellation, etc) Enable secure access to and from the ITL Service desk activities Schedule initialization process tiers with each RSA RSA Forum activities Elaborate documentation requirement procedures Enable secure access to and from each system Set up government account information for each 26 13

14 Tier 1 Document review Documentation focuses on non-functional DES requirements Database and application backup Disaster recovery plan (business continuity) Security plan Application logging documentation Time validation plan Version change management Test plan and test report Operational plan 27 Tier 2 Connectivity testing Detailed in Annex H of the DES Communication initialization Access to ITL website - public ITL website - access to ITL extranet Basic connectivity problems resolved before functional tests 28 14

15 Tier 3 Functional testing Detailed in Annex H of the DES Provide government account information Requests for other data Data identifier initialization Web services testing - all individual transactions and queries - reconciliation Full system testing (end-to-end business transactions) 29 Supporting initialization Initialization is supported by the Service Desk Developer, operator and secretariat have roles in support infrastructure Key learning process the service desk Initialization experience to be incorporated in desk s knowledge base 30 15

16 Activation Short coordinated tasks will be needed to activate connection Activation schedule to be confirmed after initialization approval Stage 1 (low risk): CDM Stage 2: CITL and connected EU registries - activated together before the end of March significant coordination effort required - involves data migration from CITL to ITL Stage 3: Expected to be non-eu registries 31 Live operation Live environment commences on activation of first Service desk to be fully in place Live environment to be fully operational with high resilience Full support structure to be in place 32 16

17 Key points of interaction Key information prepared by ITL administrator Network connectivity requirements (M1) Confirmation of pilot test schedule (M4) Initialization test schedule (M4) Key points of involvement Pilot test scheduling (M3) Pilot testing with selected registries (M5) Initialization scheduling (M3/M4) Initialization (starts in M5) Activation (from M9) Live operation (ongoing from activation) 33 17