Annie Griffith January 2008 UK Link Technology Refresh

Progress Since Last Update  OAT  Final few tests in OAT Phase 2 now underway – 96% complete  No outstanding defects  UAT  97% complete  Final few tests in progress  3 rd Full scale trial migration completed  Independent review by IBM has verified quality, appropriateness and completeness of testing and data migration validation  Dress Rehearsal commenced

Cut-over and Implementation  Outage still planned at 4 days  All Go/No-go points defined  Back-out points and processes defined  Error scenarios worked through and recovery actions understood  MOD proposal 184 drafted to include:  2 partial non-business days for SPA processing and queries (25 th & 26 th Feb)  4 days relief from data logger liabilities (24 th -27 th Feb)

Cutover Weekend Back-out Points Go-No/Go PointBack-out Action NeededRecovery Time to BAU G5 Sat 23 rd Feb 11:00 Data loggers Complete Re-start production services. Restart Batch schedule 1-2 hours 13:00 Sat 23rd G6 Sun 24 th Feb 11:00 Migrations Completed Reverse file transfer configuration changes Reverse file system re-routing changes and application re-pointing Restart production service and commence batch catch-up 12 hours +1 days catch-up 23:00 25 th Feb G7 Mon 25 th Feb 11:00 Data Rec. Completed Reverse file transfer configuration changes Reverse file system re-routing changes and application re-pointing Restart production service and commence batch catch-up 12 hours + 2 days catch-up 23:00 27 th Feb G8 Mon 25 th Feb 17:00 On Line Verification complete Reverse file transfer configuration changes Reverse file system re-routing changes and application re-pointing Restart production service and commence batch catch-up 12 hours +2.5 days catch-up 20:00 28 th Feb G9 Mon 26 th Feb 09:00 Transfer Routes and data validated Reverse file transfer configuration changes Reverse file system re-routing changes and application re-pointing Restart production service and commence batch catch-up 12 hours + 3 days catch-up 10:00 29 th Feb

Implementation Communications  Specific updates around the implementation will be ed to the standard distribution lists  UKLC  Operational Shipper Contacts  Will use the existing xoserve Customer teams for communications  Will be using the xoserve web site for general updates

Example Failure Scenarios ScenarioLikely Action (will always be dependant on nature of fault/failure) Unable to produce Invoices  Can delay Capacity Invoice to 13 th March  If delay over 7 days UNC allows for issue of estimated invoice xoserve is unable to send out files to Shippers  If fault is at new UK Link Data Centres would FTP files to IX at existing data centres  No changes are being made to IX so believe failure is unlikely, however, if necessary options exist for issue of paper invoices, ing files or transfer to alternative media and courier xoserve is unable to receive files from shippers  If fault is between IX and new UK Link Data Centres would FTP files  No changes are being made to IX so all Shipper files should still be received in IX as now. A shipper receives the incorrect file  Will alert other party upon notification, suspend Shipper file issue until exact nature of fault verified.  Will back-out. Would expect Shipper system validation to reject and not process.  If experienced, likely to be du to a configuration error which can be easily rectified. The data within a file is found to be incorrect or corrupt  Action dependent on nature of error  May require Network Code Contingency to be invoked to prevent any further data corruption or propagation of corrupt data  Will attempt to fix and then catch-up

Next Steps  Completion of OAT Phase 2  Progress UAT to completion  Conclude Dress Rehearsal  Prepare & issue pre-implementation Shipper comms  Early Interface Implementation  Finalise Implementation Planning

Addendum Supplementary Information presented previously

Major Milestones DateMilestone 14/01/08Interface Routing Implemented 21/01/08UAT Completed 21/01/08OAT Completed 27/01/08Dress Rehearsal Completed FebMod Approved 01/02/08Bulk Data Migration Started 21/02/08Readiness Verified 23/02/08Start Outage 25/02/08Start Catch Up 28/02/08Complete Catch Up 30/05/08End of Post Implementation Support

Go/No-Go Decision Points IDDateInputOutput G111 th JanInterface Plans AgreedMove to early interface implementation G222 nd JanUAT and OAT CompletedInitiate Bulk Data Migration G301 ST FebDress Rehearsal completed, All plans in place Start pre-cutover activities G421 st FebAll approvals in placeApproval to start G523 rd FebData loggers CompleteStart Outage G624 th Feb 11:00Migrations CompletedDesk top rollout and reconciliation checks G725 th Feb 11:00Data Rec. CompletedRelease to internal users for screen verification G825 th Feb 17:00On Line Verification completeStart batch catch up G926 th Feb 09:00Transfer Routes and data validated Release to internal other systems G1026 th Feb 10:00Files generated and verifiedRelease to Shippers G1126 th Feb 12:00Batch catch-up progress OKEnable peripheral applications

System Impacts SystemSaturday 23 rd Feb Sunday 24 th Feb Monday 25 th Feb Tuesday 26 th Feb Wed’s 27 th Feb ConquestOutage Returns PM and will reflect UK Link As UK Link IADWill have data as 22 nd Will have data as 23 rd Will have data as 24 th, 25 th SP TransferNo Run Run 24 th and 25 th Run 26 th and 27th Data Loggers23 rd RunNo Run Run 24 th and 25 th Run 26 th and 27 th DN LinkOutage As UK Link