UK Link Technology Refresh
Annie Griffith
January 2008
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
 3rd 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 (25th &
26th Feb)
 4 days relief from data logger liabilities (24th-27th Feb)
Cutover Weekend Back-out Points
Go-No/Go Point
G5
Sat 23rd Feb
11:00
Data loggers
Complete
G6
Sun 24th Feb
11:00
Migrations
Completed
Back-out Action Needed
Re-start production services.
Restart Batch schedule
Recovery Time
to BAU
1-2 hours
13:00 Sat 23rd
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 25th Feb
G7
Mon 25th 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 27th Feb
G8
Mon 25th 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 28th Feb
G9
Mon 26th 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 29th Feb
Implementation Communications
 Specific updates around the implementation will be emailed
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
Scenario
Likely Action (will always be dependant on nature
of fault/failure)
Unable to produce Invoices
Can delay Capacity Invoice to 13th 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, emailing 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
Date
Milestone
14/01/08
Interface Routing Implemented
21/01/08
UAT Completed
21/01/08
OAT Completed
27/01/08
Dress Rehearsal Completed
Feb
Mod Approved
01/02/08
Bulk Data Migration Started
21/02/08
Readiness Verified
23/02/08
Start Outage
25/02/08
Start Catch Up
28/02/08
Complete Catch Up
30/05/08
End of Post Implementation Support
Go/No-Go Decision Points
ID
Date
Input
Output
G1
11th Jan
Interface Plans Agreed
Move to early interface implementation
G2
22nd Jan
UAT and OAT Completed
Initiate Bulk Data Migration
G3
01ST Feb
Dress Rehearsal completed, All
plans in place
Start pre-cutover activities
G4
21st Feb
All approvals in place
Approval to start
G5
23rd Feb
Data loggers Complete
Start Outage
G6
24th Feb 11:00
Migrations Completed
Desk top rollout and reconciliation checks
G7
25th Feb 11:00
Data Rec. Completed
Release to internal users for screen
verification
G8
25th Feb 17:00
On Line Verification complete
Start batch catch up
G9
26th Feb 09:00
Transfer Routes and data
validated
Release to internal other systems
G10
26th Feb 10:00
Files generated and verified
Release to Shippers
G11
26th Feb 12:00
Batch catch-up progress OK
Enable peripheral applications
System Impacts
System
Saturday
23rd Feb
Sunday
24th Feb
Monday
25th Feb
Tuesday
26th Feb
Wed’s
27th Feb
Conquest
Outage
Outage
Returns PM
and will
reflect UK
Link
As UK Link
As UK Link
IAD
Will have
data as 22nd
Will have
data as 23rd
Will have
data as 23rd
Will have
data as 23rd
Will have
data as
24th , 25th
SP Transfer
No Run
No Run
No Run
Run 24th
and 25th
Run 26th
and 27th
Data Loggers
23rd Run
No Run
No Run
Run 24th
and 25th
Run 26th
and 27th
DN Link
Outage
Outage
As UK Link
As UK Link
As UK Link