1 / 12

UK Link Technology Refresh

UK Link Technology Refresh. Chris Fears December 2007. Progress Since Last Update. OAT – 2 phases Jun-Oct ’07 & Oct-Jan ‘08 OAT1 – machine build confirmation – Completed OAT2 – performance testing, operational schedules, support processes, fall back and recovery etc. – Started

Download Presentation

UK Link Technology Refresh

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. UK Link Technology Refresh Chris Fears December 2007

  2. Progress Since Last Update • OAT – 2 phases Jun-Oct ’07 & Oct-Jan ‘08 • OAT1 – machine build confirmation – Completed • OAT2 – performance testing, operational schedules, support processes, fall back and recovery etc. – Started • Internal penetration testing conducted, 3rd party penetration testing planned • UAT : Nov – end Jan : Started • Shipper trials : Completed • 3rd Full scale trial migration added • Detailed implementation planning under way

  3. Shipper Trial Update • Tests have successfully concluded • File transfer connectivity between the Shipper locations and new UK Link Data Centres has been proven • NOM files were successfully received, loaded & processed • NMR, COS and MDR files were issued to participants who confirmed the file formats and content was as expected • Participants confirmed successful loading and processing of all files issued • 1 file was sent to a wrong directory due to a configuration error in IX • Lesson - Check file location configurations prior to implementation • Lesson - Tightened up the file exchange approval mechanism • Delivery receipts successfully received for all files issued from the new system

  4. Testing Updates • OAT is 80% complete • Completed back up and fail over tests • Scheduler testing planned for 19/12 • UAT is 88 % complete • Performance testing ongoing – looking good

  5. Cut-over and Implementation • Outage still planned at 4 days • Detailed implementation planning activities ongoing • Looking at cut-over activities and catch-up processing • Back-out plans also being drawn up • MOD proposal 184 drafted to include: • 2 partial non-business days for SPA processing and queries (25th & 26th Feb) • 4 days relief from data logger liabilities (24th-27th Feb)

  6. Cutover Approach • Data cutover • Will start 3 weeks in advance of main cutover, then will require “delta” data updates • This will have no effect upon the operational service • Final cutover starts 22nd/23rd February 2008 • REC invoice to be issued early on Friday 22nd – due dates will be unchanged • Other production runs on 22nd will be unchanged • Outage start time • Start after Datalogger issue on Saturday 23rd confirmed as optimal approach

  7. Major Milestones

  8. Go/No-Go Decision Points

  9. System Impacts

  10. Implementation Concerns & Mitigations (1) • Data Corruption • IBM conducting a health check on the migration and validation processes • Replaced manual checks with scripted , repeatable checks • System performance • No adverse performance observed during testing • All testing done on production sized environments • Back Outs • As part of the Dress Rehearsal we will practise the back out steps • Once we have propagated the data to the systems of others we will be in a “fix forwards” situation

  11. Implementation Concerns & Mitigations (2) • Checkpoints • The implementation will have a series of go/no-go points identified • Expanded the number of health checkpoints during implementation • Both time and event driven • Will hold files and validate before release • Communications • Will be using the xoserve web site for general updates • Specific updates around the implementation will go to the standard distribution lists (UKLC and Operations) • Will use the existing xoserve teams for communications

  12. Next Steps • IBM to complete assurance of testing and data migration approach • Completion of OAT Phase 2 • Includes completion of 3rd party penetration testing • Progress UAT to completion • Finalise Implementation Planning • Plan detailed activities for Dress Rehearsal • Define and refine back out processes • Enhance the go/no go and escalation criteria • Finalise catch-up and return to normal operation plan

More Related