1 / 9

UK Link Technology Refresh

UK Link Technology Refresh. Annie Griffith November 2007. Progress Since Last Update. Full code migration and upgrade completed OAT – 2 phases Jun-Oct ’07 & Oct-Jan ‘08 OAT1 – machine build confirmation – Completed

dustin
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 Annie Griffith November 2007

  2. Progress Since Last Update • Full code migration and upgrade completed • 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 • System testing : Completed Successfully • Users involved in testing of critical business components to gain greater levels of assurance ahead of UAT • Invoices produced matching to the penny • UAT : Nov – end Jan : Started • To include Shipper Trials : late Nov - early Dec • 2nd Full scale trial migration completed • Data validations activities for migration practised • Timings confirm previous expectations • Further full scale trial migration planned as part of Dress Rehearsal

  3. Shipper Trials

  4. Cut-over and Implementation • Outage of 3 - 4 days as previously indicated • Detailed implementation planning activities ongoing • Looking at cut-over activities and catch-up processing • Back-out plans also being drawn up • MOD proposal 179 drafted to include: • 2 non-effective days for SPA processing (25th & 26th Feb) • 4 days relief from data logger liabilities (24th-27th Feb)

  5. 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

  6. High Level Timetable (Draft) • Invoices • Friday 22nd - REC Invoice issued early, due dates unchanged • Non-effective Days • Mon 25th Feb - Tuesday 26th Feb • Relief from DM Read liabilities Sun 24th –Weds 27th • Datalogger files • Issued from OLD UK Link Sat 23rd • Suspend daily issue of data logger files Sun 24th – Weds 27th • Issued from NEW UK Link Thursday 28th • Transfers • Last files processed 11pm Friday 22nd Feb on OLD UK Link • Next scheduled Transfer Run – Weds 27th Feb on NEW UK Link, may have interim run as part of catch-up processing

  7. Implementation Concerns & Mitigations (1) • Data Corruption • Using pre-validated scripts to test data quality • Testing has been carried out by matching to production values • Will hold files for validation prior to issuing them externally or to other systems • System performance • Test strategy includes completion of load and performance testing • Primarily batch facing so lower online loads generally • 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

  8. Implementation Concerns & Mitigations (2) • Checkpoints • The implementation will have a series of checkpoints for go/no-go • These will be both event and time driven • Communications • Will be using the xoserve web site for general updates • Specific updates around the implementation will go to the standard distribution lists • Will use the existing teams for communications

  9. Next Steps • Completion of OAT Phase 2 • Includes completion of load and performance testing • Progress UAT & Shipper Trial • Continue with more in depth Implementation Planning • Finalise scope of Dress Rehearsal • Define and practise back out processes • Enhance the go/no go and review criteria • Understand catch-up and return to normal operation • Dates when other internal systems will be brought back on-line/in-step

More Related