1 / 11

UK Link Technology Refresh

UK Link Technology Refresh. Annie Griffith & Chris Fears September 2007. Progress since last update. Key progress made since last update: Development and Unit testing completed

nhector
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 & Chris Fears September 2007

  2. Progress since last update Key progress made since last update: • Development and Unit testing completed • Installation and configuration of all servers and networks at Peterborough Data Centre and Wellingborough completed • Network Operations Centre (NOC) set up in Bangalore and operational • System testing started • Operational Acceptance testing Started

  3. Overall Testing Progress • Full code migration and upgrade completed • OAT – 2 phases Jun-Oct ’07 & Oct-Jan ‘08 • OAT1 – machine build confirmation – Ahead of schedule • OAT2 – performance testing, operational schedules, support processes, fall back and recovery etc. • System testing : Started mid Aug and ahead of schedule • Users involved in testing of critical business components to gain greater levels of assurance ahead of UAT • UAT : Nov – end Jan • To include Shipper Trials : late Nov - early Dec • Detailed UAT planning underway • Full scale trial migration completed – • Minimum of 2 further full scale trial migrations planned to allow for tuning

  4. Shipper Trials • Initial suggestion was that only file routing tests to be executed, limited to sample files only • As a result of UKLC July 07 request, revised approach is to test: • Nomination file (NOM) – inbound and Nomination response (NMR) outbound • Commodity Invoices (COS) – outbound, with inbound delivery receipt • Datalogger Read files (MDR) – outbound • Involvement is optional • Code of Conduct: The test environment is not to be used for any other activities ie: enquiries other than the scenarios and data agreed by each Shipper

  5. Shipper Trials • Trial environment will be a copy of production data as of 1st October 2007 • Shippers to save selected copies of production NOM files between 1/10 – 12/10and rename • Between 3 and 5 NOM files are to be saved for future processing • Use standard test file naming convention: xxx01.TN123456.NOM • Earlier files will result in fewer queries due to better alignment with data-cut • Submission of files to take place before 12 noon • Response files will be processed and sent back the following day by 10.00am (The test file turn-a-round time will not be representative of Production) • Test files to be submitted in date order • No xoserve validation of rejections at MPRN level will take place

  6. Shipper Trials

  7. Shipper Trials Assurance & Sign-off • Individual Daily Test Reports will be produced by the Test Coordinator and issued at end of day • On conclusion of the Shipper Trial phase xoserve will confirm final test position (by e-mail) with each participating Shipper • Teleconference meeting to take place at the end of testing • Capture lessons learnt • Confirm any outstanding issues • Discuss remedial action plans (if necessary)

  8. 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 • Timescales being challenged, seeking alternative approaches and tuning to reduce outage • Minimum of 2 further full scale trial migrations planned over summer • MOD proposal being drafted to include: • 2 non-effective days for SPA processing (25th & 26th Feb) • 4 days relief from data logger liabilities (24th-27th Feb)

  9. Cutover Approach • Data cutover • Likely to 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

  10. 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 Transfer Run – Weds 27th Feb on NEW UK Link

  11. Next Steps • Completion of OAT Phase 1 • Complete trial migration 2 • Invitations issued for Shipper Trials • Continue with more in depth Implementation Planning • Firm up on outage timings • Understand catch-up and return to normal operation • Dates when other systems will be brought back on-line/in-step • Report back at October UKLC

More Related