FUJ00095766
FUJ00095766
Re)
FUJITSU
Joint Programme Board
18 May 10
FUJ00095766
FUJ00095766
RMGA Level 1 — Programme Summary
Fe)
FUJITSU
Activity
HNGX R1
Development complete
Integration Complete
Test complete
Deployment complete
Decommissioning Complete
POLSAP
POL-FS Stable for POLSAP
Implementation rehearsal
Implem. Dress rehearsal
Data Migration complete
POLSAP Cutover complete
HNGX R2
Development complete
Integration Complete
Testing complete
Deployment complete
Model Office
AEI Interim Solution
Design complete
Build complete
Test Complete
Deployment complete
Go Live (first installation)
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov
01/6/10
01/6/10
6/7/10
09/8/10
I
18/11/10
= 25/3/10
SS 18/6/10
i es 13/8/10
—— 23/8/10
i m 30/8/10
—————— es ssii0
06/8/10
ee 28/9/10
912/8/10
mum (06/4/10
11/4/10
11/4/10
30/5/10
m 13/4/10
FUJ00095766
FUJ00095766
Fe)
FUJITSU
HNGX Progress Report
Geoff Butts
FUJ00095766
FUJ00095766
HNGX R1 Agreed Baselines FUJITSU
@ Schedule
mw V120.A00 draft
* (The plan that will be reported against from now onwards)
mw V80.A00 check-pointed with the client
m Requirements
m version 1.42
™ Testing Baselines
mw LST — MR 01.22.00 + hot fixes
m VOL — MR 01.20.00 + hot fixes
FUJ00095766
FUJ00095766
Red Major issue impacting timescales, cost or risk Fe)
H N G xX R1 S umm arye Major issue but with actions agreed to resolve FUJITSU
Lo donde ‘ls. 2Green _Noissues —— ee
RAG Last Current Description G2G plan G2G Target
Status Status Date
Delays to completion of Pilot and Rollout will I Full cost impact to be determined once
Approved Budget impact overall Project Costs. Rollout schedule is confirmed. 31 May 10
Review of HSD completed, Problem I -
Resourcing Manager recruited for Oracle issues. Release Manager required. Recruitment 23 May 10
Y « underway.
Security Architect recruited.
High Volume started 25/03/10, but Implementation of 1 patch and 2 setting
suspended 26/03/10. Stabilisation of live changes recommended by Oracle to fix
Schedule service continuing. Tracked via Red Alert IBranch database hanging. Further remedial I 28 May 10
and daily management updates. Criteria to I fixes planned for 16/05. Stability of service
re-start Pilot under review. under review.
Requirements
Architecture
Daily prioritisation of new issues from Red Alert remediation plan in place. Waiting
Apps Development live/test. High volume of Hot fixes. Focus ot contin on testing required for new 28 May 10
on addressing Oracle LCK issues. racle Patch. Daily tracking of progress
against plan.
Vol test cycle 2 completed 26/03/10. Cycle 3 .
Test start delayed due to live issues requiring Vol Revised plan for start of Cycle 3 to be 23 May 10
rig to test. :
Red for HNG-X Migrations due to High Revised schedule for High Volume Pilot &
Migration Volume Pilot being suspended. Branch Rollout to be confirmed. Fixes targeted into I29 May 10
Router installations in tail management. live throughout May 2010.
Baektip ivan switehing-selition
in Model Office 11/05. Testing completed 7
Infrastructure 14/05, pilot to start 17/08. Satelite Branch I erching solution. Complete Satelite Branch] 28 May 10
Router solution — target exit from LST 9 a PI y
slipped 1 week to 28/05 due to BT issue on Router LST testing.
rig.
Ongoing monitoring in place for live issue.
Service Transition Recommendations from internal review Continue to review live service stability. 23 May 10
implemented.
Contract
CRs
FUJ00095766
FUJ00095766
HNGX R1 Exec Summary
foe)
FUJITSU
@ High Volume Pilot Started 25/03/10 (212 additional branches migrated)
™ 622 Branches (1,754 counters) on HNG-X, including 8 Model offices
@ High Volume Pilot migrations suspended 26/03/10 until live service issues
resolved
@ Minimum number of migrations (up to 10) recommended before planned
fixes implemented during May 2010. Stability of service under continual
review.
& Resolution of Oracle issues escalated to Exec level in Oracle
@ 11,178 Branch Router installations completed, in tail management (less
than 3%, 273 branches remaining, including 50 VSAT branches, 55 PHUs).
m Milestones — 33 completed on schedule, 10 completed ahead of schedule,
64 completed behind schedule
FUJ00095766
FUJ00095766
HNGxX Live Issues Impacting Multiple Branches Fujitsu
™ Further Branch Database hanging incidents affecting many/all branches on
6, 9", 16" 28" April and 7", 12" & 13" May. Multiple minor occurrences.
@ In addition - 5 out of 20 BAL OSRs went into a loop on 28" April, resulting in
longer outage than previous incidents. Cause - change contained in release
1.21 that was applied to live 25th April. Fix tested & implemented into live
4" May.
5" May — 40 minute HNG-X outage caused by human error
Diagnostic tracing and Oracle Streams switched on in live by agreement
with POL from 11" May to enable new occurrences of LCK error to be
captured with full diagnostic data. Cannot be replicated on Vol rig.
= Full diagnostics captured 12 May 17:40 & 13" May 09:00 and sent to
Oracle.
@ Escalations to Oracle Exec level. 3 recommendations from Oracle:-
m Hidden parameter change — tested in Vol 11" May, implemented into live
14'" May outside trading hours
= New patch and 1 additional parameter change to be implemented 19"
May subject to completion of testing.
@ Plan with additional remedial steps agreed with POL 10" May. Fixes
scheduled for implementation throughout May 2010. Daily tracking of
progress against plan
FUJ00095766
FUJ00095766
HNGX R1 Key Risks & Issues FUJITSU
@ Key Risks @ Key Issues
= Cost overrun from programme = A revised schedule for branch
delays. migrations cannot be given until
m Further issues in pilot may result
in the rollout being delayed
again.
m Loss of support from National
Federation of Sub-postmasters.
= Beat rate during full rollout
cannot be sustained, leading to
delay.
u Datacentre components may
fail, resulting in delays to rollout.
confidence is re-established that
the HNG-X system is stable.
High Volume of Hot fixes in
addition to maintenance fixes
leading to testing bottleneck &
delays in implementation.
Revised Maintenance Plan issued
and reviewed with POL Team 17"
May.
Exit from Wigan and Bottle
Datacentres by 31/07/10 is not
achievable due to delays in the
rollout schedule.
FUJ00095766
FUJ00095766
HNGX R11 Milestones
Fe)
FUJITSU
Milestone
Team
PlannedIForecast
Comment
Counter Roll Out Commence
Mig
09/11/09/TBC
Subject to satisfactory completion of High Volume Pilot and Volume
Testing. Delayed due to live issues with Oracle database performance
Branch Router Roll Out Complete
Mig
15/11/09
06/06/10I}>97% of estate has had a Branch Router installed. Now in tail
management. 50 remote branches requirring satellite comms (VSAT)
enabled router will not receive Branch Router until May 2010 due to
delays in test due to contention with maintenance releases. Sign-off of
VSAT in test moved back to end May.
Counter Rall Out Complete
Mig
30/04/10
TBC
Excludes 4% tail. Delayed due to Oracle issues during High Volume
Pilot. Completion date to be confirmed
FUJ00095766
FUJ00095766
HNGX R1 Progress Against Plan FUJITSU
@ Original Plan (Baselined June 2009) Key Milestones
m= Branch Router Rollout complete 13/04/10
m HNG-X Branch Migration Rollout complete 22/04/10
™ Delays caused by:-
= Datacentre Migration Slip - 3 weeks
= Branch Router solution delays — 1 week
m Delay to start of Medium Volume Pilot — 1 week
m Delay to start of High Volume Pilot —- 2 weeks
m Delay to start of HNG-X Rollout — 7 weeks (estimated)
FUJ00095766
FUJ00095766
HNGX R11 High Level Schedule FUJITSU
Activity Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct
Development
14.16.03 Delivery 24/9/09 ozjoaio
Maintenance Release 1.03 Ct} =2=A2i Seana i 17/09/10
Live Support Ss
Test
V&l Complete 22/9/09
SVI PEAK Clearance _ 20/02/10
RV Mg Cycle 4 A 11/12/09
LST DC Prep Re h aftclos
LST Test Weekend B/C Install m 4 9
LST Test Weekend B/C proving mum 28/10/09
LST Counter proving EERIE 11/01/10
Deployment :
Migration Weekend BC m_ ‘1/09 14/5/10
Bench Router Depleyacne AN Til
Model Office Pilot (Counter) AA = — 02/03/10 }
Pilot (Counter) ae TBC 24/05/10
Branch Rollout (Counter) : TBC 09/08/10
FUJ00095766
FUJ00095766
HNGX R1 Slip Chart
Fe)
FUJITSU
Jun ul Wg Sep I __oct Nov Deo Jan Feb I__ Mar Apr Jun ul
Date i522 20 06 13 20 27 [03 10 17 24 31 [O74 21 Sy pee ee BOTA BHNDH DBO 0 TB
@ 4 P
lacceptance Gateways 6B Gateway 2De Gateway 1B Rover Gatenay 3 om
Migration 01/1008 100 02/%¢ Gateway 6 fila acceptance
one pit 21009 15020 Sate
[Application Development ‘at Tater LUVE 0108, car
“Applatons& Networks cA avo7e8 110808 agoriio +
(from integration) 1 ve MW Wa ated LVE OS LVEDIOT WeTatas I LVEOI0B0C [ay
4 0107/09 24/07/09 o5/0B09 19108109 OT10G09 240808 — 05/1009 2ar10109 07/1208 20110
Peak Fives GA Fies ABC
1008
TEST
Disaster Recovery AD a a a
wnt
Vilntegrity DR LWINTFs 300609 wings VIINT
WINTH Onde onal
aor08
ViVolume (horizon) or [we wer
TE 10808
sval oR SM___svcr Vi peak dewance
o TSOTT
RV ACC(editation) OR ‘ ce Sgn off
mi a
BV Mg C28 BN c2o RV a
Ry Malate) oR aa re rr
ST on lst, STDC Prep ist pg ist pc ISTO st counter ST PHULST BR upg LsLvoL.
UST (uve Systm tet oR ra TR se TOT TTT aa
fe ee ee ———
Votprep_ValPt voiP3
VOL (Volume HNGX) oR ai Daron a
bus Ass POL) Lie set p/LRDP)
Reference data GA a
Migration
Securty fc)
11800 8nch
Branch Router CB Pilot Start Plot ends Rollout starts 2800 Brnchs 8790 Bch 28003110
TT oT TT ey THOTT
vow
Model Ofice Pit start I
stosttog rtt08 .,
Dorp WKBC KD a ce Rotel competes
Migration OC Implementaton I GB STEEN TOT aos ore ny mete
I I Fin 1671109
i I
Week Nq 25 26 27 28 29 30 31 32 33 34 35 36 97 38] 30] 40 41 42 43 44 45 46 47 48 49) 50 S152 53 1 2 3 4 5 6 7 8 9 10 14 12:13 14 15 1617 180 14 12 13 14 15 16:17 14 15 16 17
FUJ00095766
FUJ00095766
Fe)
FUJITSU
POLSAP Progress Report
Alan D’Alvarez
FUJ00095766
FUJ00095766
Red Major issue impacting timescales, cost or risk oO
Amber Major issue but with actions agreed to resolve
POLSAP Summary «ows FUJITSU
RA Current Description G2G Plan G2G Target
G Status I Date
Currently forecasting a FAC circa £65k over
Approved Budget the agreed baseline as a result of re-visiting IReview of resourcing to be undertaken 21 May 2010
the forecasted infrastructure resources.
. The request and the situation regarding CAT
‘ POL have asked for Fujitsu to support CAT I. - -
Resourcing : is due to be discussed this week to agree 19 May 2010
beyond the agreed end date for this work mitigation plan
Under pressure to complete data quality
Schedule checking which is required to complete prior IPOL to review resourcing 17 May 2010
to starting testing the batch schedules
Requirements
. Migration Plans Need to Be agreed and Agree Migration Plans
Architecture pean 26 May 2010
performance monitoring to be completed Complete performance monitoring y
Apps Development
Test Collaborative Acceptance Testing is behind
schedule.
FUJ00095766
FUJ00095766
POLSAP Summary (Continued) FUJITSU
RAG Last Current Description G2G plan G2G Target
Status I Status Date
Completion of data quality checking
- required to be completed 21/5 and is under IPOL to present plan for data quality
Implementation pressure. This is required to complete prior Ichecking 21 May 2010
to starting testing of the batch runs
Infrastructure
Service Transition
Progress is being made on addressing the
outstanding change request responses. -
Release of response for POLSAP Training Continue to progress the responses ASAP.I31 May 2010
Environment is imminent.
Contract / CR’s
FUJ00095766
FUJ00095766
foe)
POLSAP Apps Exec Summary FUJITSU
= Implementation:
m Issues with the file format extracts provided by CSC are causing issues
for Test Cycle 3 data loads. The new set of extracts has now been
provided and there are no further issues. Data quality checking needs to
complete by 21/5 and POL looking at mitigating impact of delays
m A further low-level planning session has been arranged for cutover
= Awaiting scope of functional testing from POL
m CAT/CMS:
m POL are no longer confident of meeting the planned date for completion
of CAT. There are a number of outstanding test scripts to run, and a
number of defects to close. A plan is in place to address the outstanding
defects as a priority
m The pricing change relating to CMS will not require a change control.
However, POL acceptance of the fix is still outstanding
@ Training:
mu The CR for the POLSAP Training Environment has been approved by
CCB and will be issued to POL
FUJ00095766
FUJ00095766
POLSAP Infrastructure Exec Summary fujitsu
@ Network Infrastructure
= Circuit tails were completed by NTL in Huthwaite over the weekend 8'/9"" May,
further activities are needed to complete the upgrade of the links and we are
progressing the swap-out of the 5 routers in the next couple of weeks.
u FCIL design progressing, RMGA design to be progressed following this and all
on plan.
@ Performance Assurance:
u Topology workshop held and was generally successful with only a couple of
extra pieces of information being requested
a System Inspector reports are available on POL-FS and the SAPADS installation
looks possible and is progressing. Purchase Order for the analysis progressing
through the system
m Response provided regarding the suitability of Fujitsu’s approach to performance
assurance
@ Other Infrastructure:
u Pre-Live Proving scope produced, joint meeting on Thursday to define the
definitive scope.
= Batch Processing progressing
a Archiving design out for review, workshop held for the “final 3 month” run and all
teams working together on finding solutions to enable successful cutover
FUJ00095766
FUJ00095766
POLSAP High Level Plan
Fe)
FUJITSU
Activity
Development complete
Build
Network Infrastructure
Testing
Collaborative Testing
Implementation
Rehearsal
Dress Rehearsal
Service Preparation
Technical Interfaces
Batch Processing
CSC Activities/Infrastructure
Service Transition
Data Migration
POL-FS Stable for POLSAP
POLSAP Cutover complete
Dec Jan Feb-= Mar Apr May Jun Jul Aug Sep _ Oct
Nov
Sd r7I3it0
EE a
—E 13/510
ee 12/5/10
es 13/8/10
es 20/8/10
Ad 25/3/10
@ 30/8/10
FUJ00095766
FUJ00095766
POLSAP Slip Chart iT
POLSAP Slip Chart Author Leo Sapiets Date 9/5/10
Jan Fob oo. Mar Apr May I Jun il Jul aT Aug Sep ]
03 10 17 24 31 [07 14 21 28 04 11 18 25 [03 10 17 24 31 [07 14 21 26 05 12 19 26 02 09 16 23 30 07 14 21 28 04 11 18 25
Build ] ] ]
Network Infrastructure on Routing Updated Upgrace implement “ase
2arnino 418110 716/10 38/10
Testing
5 CAT Test complete
. tart ‘ompletes
Collaborative Testing 0402/10 toa0 4915/10
Implementation
Start Load Data __ Validate I __ Completes
Rehearsal 23/02/10 718110 1915/10 18/6/10
Start Load Data _ Validate Completes
Dress Rehearsal 2se0 i270 I “217/10 I =" 43/8/10
Service Preparation
Impact Approve CSC Unit Test
Start Assessments Design Changes f_CSC Changes mms Completes:
Technical Interfaces 813/10 2615/10 2316/10 1a7In0 10/8/10
Potsignott Completes
Batch Processing ao peas 6108/10
cviti KTs Completes
CSC Activities ain I prs si9i10
start Knowledge
- ie It OLA fue THLE es Transfer = completes
Service Transition Ss0s008 2116/10 47110 2418/10 25/8/10
. . Start ‘1st version 2nd versi Completes
Data Migration Schedule 16/4/10 2316/10 mero 20/8/10
Migration / Cutover
IPOLFS Stable for POLSAP. C) 2513/10
POLSAP Cutover Complete ¢ 30/8/10
1
FUJ00095766
FUJ00095766
POLSAP Key Milestones FUJITSU
I Plan Baseline Operational
UID Task Name Finish Owner Forecast I Baseline
1437 ITest Cycle 2 Complete 08/03/10 POL Project Team 14/04/10 I 14/04/10 pierre
507 IHuthwaite Network Upgrade Ready for Cutover 01/06/10 POL Project Team 27/05/10 } 27/05/10
Initiate Implementation Rehearsal 14/04/10 14/04/10 I 14/04/10 Petey] Ft Cy
Scope for Implementation Rehearsal defined 14/04/10 I FS Apps & POL Project team I 05/05/10 } 05/05/10
Implementation Rehearsal Complete 15/06/10 POL Project Team 18/06/10 I 18/06/10
Initiate Implementation Dress Rehearsal 18/06/10 23/06/10 I 23/06/10
Scope for Implementation Dress Rehearsal defined I 18/06/10 POL Project Team 23/06/10 } 23/06/10
Implementation Dress Rehearsal Complete 10/08/10 I FS Apps & POL Project team I 13/08/10 } 13/08/10
FUJ00095766
FUJ00095766
POLSAP Key Dependencies FUJITSU
Plan Task Name Operational Owner Forecast RAG
UID I i Baseline
2327IGET: Definition of Scope of Functional Testing 05/05/10 POL 05/05/10
2062IGET: POL Sign-Off Converted Data 07/05/10 POL 07/05/10 Complete
2313/GET: Initial Scoping/Draft Schedule Creation 07/05/10 FJS 07/05/10
674IGET: Produce a List of New Roles for Dress Rehearsal 10/05/10 Fujitsu 10/05/10 Complete
338]GET: Raise change request(s) for CSC Equivalent to support POLSAP interface 12/05/10 POL 12/05/10
implementation
339]GET: Raise change request(s) for Logica (POLMI) Equivalent to support POLSAP 12/05/10 POL 12/05/10 Complete
interface implementation
1168IGET: CAT Testing Signed Off 13/05/10 POL 13/05/10
1578IGET: POL review Data Migration Specs 19/05/10 POL 19/05/10
2117IGET: Implementation Rehearsal POL Sign-Off of All Data Validations 19/05/10 POL 19/05/10
2041IGET: POL Sign-Off Printing Test Results 20/05/10 POL 20/05/10
2502/GET: Training User Setup 21/05/10 21/05/10
2317IGET: Agree pre-live proving plan/detailed schedule (POL/Fujitsu/CSC) 21/05/10 FJS 21/05/10
2319IGET: CSC Confirm Business Connector Ready for Pre-Live Proving 24/05/10 CSC 24/05/10
1490IGET: POL Sign-Off Batch Processing Requirements 24/05/10 POL 24/05/10
933]GET: POL SAP Licenses in place for SAP Practice 31/05/10 POL 31/05/10
353]GET: Design POLMI_ Changes 01/06/10 Logica 01/06/10
432IGET: Define Functional Batch Testing Plan 01/06/10 POL 01/06/10
FUJ00095766
FUJ00095766
Client Ref
POLSAPROO14 Maxted
Christopher
POLSAPROOS2 Maxted
Christopher
POLSAPRO05S3 Maxted
Christopher
POLSAPRO058 Mesarosova
Livia
POLSAPROO66 Paddon Dave
POLSAP Key Risks
Description:
End-Users are not trained properly in
time for Go-Live.
Description:
There is a risk that data may not
meet the required quality standards.
Description:
There is a risk of CAT delay, leading
to a negative impact on the Go-Live
date.
Description:
There is a risk that users are given
the opportunity to commit fraud,
leading to issues for POL and
Fujitsu.
Description:
Huthwaite link not upgraded in time
to support live service running for
POLSAP
‘ontainment Strateg
Containment:
Training is currently being considered prior to integration into the over plan. There is
also an open change request that is being considered in order to understand the impact
of setting up a training environment.
Update & Action 23APR10:
POL have issued a Change Control to request Fujitsu to produce a training client. The
impact assessment for this change request is underway and will be sent to POL shortly
for approval.
Containment:
Escalate to POL as owners for this activity are required in order to ensure data is up to
the required standard.
Update & Action 23APR10:
This is a POL-owned activity, and needs a staus update from POL.
Containment:
1) CAT performance to be tracked against the plan, and change control to be excercised
where necessary to incorporate delays.
2) POL to ensure sufficent, skilled resources are available to support CAT.
Update 23APR10:
POL are managing the CAT testing elements of the plan and are confident of hitting the
contractual milestone date for this activity.
Containment:
This is a risk that POL need to consider a containment strategy for.
Update & Action 19MAR10:
To be discussed during next JSB.
Containment:
Regular reviews with 3rd party supplier.
Update & Action 19MAR10:
1) POL to provide commercial cover and then hand-off routers to be procured ASAP.
2) POL to ensure dependencies are met.
16/04 - New date for the huthwaite tail is 1st May; conference call the week before
arranged to ensure the process is understood
30/4 - Confirmed date over the weekend of 8th May
Probability
Fe)
FUJITSU
Impact
10% 0.12
50% 4 0.36
25% 4 0.2
10% 4 0.12
70% 4 0.36
FUJ00095766
FUJ00095766
POLSAP Key Risks (cont’d) FUJITSU
Containment Strateg’ Probability Impact
POLSAPROO69 Rhodes Seth Descriptio. Containment: 25% 4 0.2
POL do not sign off the offshore 1) Fujitsu are currently undertaking a review of ISO 27001 against POLSAP with POL.
support model proposed for 2) RMGA Security and POL Security are actively working together on POLSAP Security
POLSAP. requirements. Risk assessment report already provided to POL.
Update & Action 18MAR10:
1) Containment action 1 is scheduled to be progressed on 12th April.
2) Overview of RMGA security requirements being obtained from Bill Memberry.
3) Consideration to be given to the use of POL-configured laptops as a fallback tactic.
POLSAPROO74 Mesarosova Description: Containment: 40% 4 0.36
Livia There is a risk that the POLSAP. Fujitsu and POL to discuss and agree an approach quickly, and then an impact
system may not have all the required assessment can be carried out.
elements prior to the baseline Go-
Live date.
POLSAPROO75 Mesarosova Description: Containment: 15% 4 0.12
Livia The project may experience All parties to ensure they have sufficient resources to keep to project milestones.
unexpected delays & key milestone
slippages.
POLSAPROO76 Mesarosova Description: Containment: 15% 8 0.24
Livia Project timeline and costs are Careful review of the migration design document, and the impact to the plan. Need to
extended. keep scope in mind, and ensure any changes to scope are covered via a formal change
control process.
POLSAPROO77 Mesarosova Description: Containment: 50% 4 0.36
Livia CAT testing identifies a lot of faults, CAT testing issues and progress to be regularly reviewed by all POLSAP parties, and
leading to time and cost extentions. consideration given to any adverse impacts to the plan and what action to take to keep
the project on track.
POLSAPROO80 Paddon Dave Description: Containment: 15% 8 0.24
There is a risk that the planned Fujitsu to arrange a workshop to understand the CSC concerns and walk through the
migration weekend of 28-30th August proposed design to assist with clarification of the requirements by 11th May.
2010 could be delayed.
FUJ00095766
FUJ00095766
foe)
FUJITSU
HNGX R2 Progress Report
David Court
FUJ00095766
FUJ00095766
Red Major issue impacting timescales, cost or risk Fe)
R2 RAG Summ ary Amber Major issue but with actions agreed to resolve FUJITSU
Green No issues
RAG
Last
Status
Current
Status
Description
G2G plan
"G26 Target
Date
Approved Budget
Resourcing
Schedule
Requirements
Architecture
Apps Development
Test
Migration
n/a
Infrastructure
Service
Introduction
Service Introduction not yet planned with CS.
Plan being discussed
31 May 2010
Contract
CRs
Deployment
At risk due to managing R2 Deployment while R1
rollout still ongoing.
Deployment Plan under review
FUJ00095766
FUJ00095766
CT Status
Fe)
FUJITSU
CT755a
ADSL Checker & New URL
Card Payment Referrals
Approved
Approved
Implemented Successfully.
In SV&I testing
Camelot Chequebook Reconciliation (Amended
410
Log Off (PING)
CT759a 438 I requirement) Approved 4 I POL testing in SV&I
CT762a 397 I Date Calculation Function in AP-ADC (Version 2) Approved 1 In SV&I testing
Change to handling Transaction Acknowledgments at
CT772a Approved
In SV&I testing
CT775c 369 I HNG-X Release 2 Wrapper Approved N/A CT approved on 29" March 2010.
Outline costing for prototype and full solution
CT776 365 I PCI Two Factor Authentication Design on TESQA Approved N/A I being reviewed.
CT778 388 I PAF Lite for Horizon Online Approved 1 In SV&I testing
ct779 391 I Policing Methods of Payment Approved 3 I In SV&I testing
FUJ00095766
FUJ00095766
CT Status continued FUJITSU
R2 Baseline CTs
cn cp I ; } ‘Description I CT Status RAG I Drop SHIT AEM Netes
CT781 385 I Streamline Observation Rectifications Approved 12 In SV&I testing
Development forecast now for Drop 5 including
CT797 396 I Improved control of Stock Adjustment Functionality Approved 5 changes on.
AP-ADC Changes to support Offline Banking
CT798 395 I Improvements Approved 1 In SV&l testing
CT802 406 I MoneyGram Web Service Changes for Release 2 Approved 4 On target for SV&I for 3 May
CT805 394 I Policing Plastic Refunds Approved 4 On target for SV&I for 3 May
Being delivered with Agent workaround to make
CT815 409 I Changes for LISS 2008 Approved 4 implementation counter independent
FUJ00095766
FUJ00095766
CT Status continued
Fe)
FUJITSU
R2 Additions to Baseline
CT cP Description Status RAG Drop Notes —
Response provided to POL query
CT800 437 Additional APOP Host Postal Order Reports Submitted 6 Require POL approval to progress
CT810 426 Travel Insurance on CTO Emulator for HNGx Approved 5 CT approved.
Changes to the Delivery of the Bureau de Early delivery in 1.29 scheduled 27/06.
CT819 442 Change Margins File - Quick Win Approved 0 (Note release number changed)
Testing and Introduction of the APOP Travel Early delivery in 1.29 scheduled 27/06.
CT823 443 I Insurance Refund Services Approved 0 (Note release number changed)
Support POL Access from Chesterfield to the CT approved.
CT8&32 439 SV&l APOP service Approved N/A To be scheduled
CT820 433 Changes to PING AIS Approved 2 CT approved.
Work Carried out Under Commercial Cover on
CT835 TBA I HNG-X Release 2 Approved N/A CT approved.
CT837 458 Streamline Accreditation (extra to CT781) Pending N/A Awaiting sign off by Fujitsu Commercial.
PCI Compliance Issues & Link Accreditation
CT838 461 (extra to CT815) Pending 4 Awaiting sign off by Fujitsu Commercial.
FUJ00095766
FUJ00095766
CT Status continued
Fe)
FUJITSU
Changes for Moneygram Web Service Changes
CT846 I 463 I for R2 (CT802) Submitted 4 Submitted for CCB 10" May 2010
Re-Allocation of Spread Charges on HNG-X
CT845 I 459 I Release 2 Approved N/A I CT approved.
HNG-X - Improved control of Stock Adjustment
CT852 450 I Functionality - Revised Requirements Approved 5 CT approved.
HNG-X - Policing Plastic Refunds - Further
CT853 454 I Changes Approved 4 CT approved.
Change to the MoneyGram AIS baseline for
CT855 469 I CP0406 Pending 4 Awaiting sign off by Fujitsu Commercial.
FUJ00095766
FUJ00095766
R2 Exec Summary FUJITSU
@ Key Challenges:
m Use Cases / Baseline of requirements in Doors
mu Managing Deployment on R2 while R1 rollout still ongoing.
m™ Key Progress:
ma SV&I Cycle 4 started
= Connectivity to Streamline complete
= Connectivity to Link planned for completion by 14" May 2010.
= Actions agreed to decouple from R1 and detailed planning in progress.
FUJ00095766
FUJ00095766
R2 Risk Register
Fe)
FUJITSU
CONTAINMENT RISK
REF NO. DESCRIPTION STRATEGY STATUS OWNER PROB% IMPACT PI
RMGARisk0306 I Additional test effort Review requirement In Progress Maving 20% 2 0.1
required due to the Following Chris
implementation of soft Implementation
launch options to CP’s planning workshop
included in R2 POL to test
RMGARisk0312 I POL Gateways may Review requirements In Progress Hinde David 50% 2 0.18
require un-estimated with POL
activities
RMGARisk0313 I Late deliveries may result Monitor progress In Progress Maving 80% 2 0.18
in insufficient time for Chris
regression testing (e.g
Stock Adjustments in
drop 5)
RMGARisk0265 I Unforseen issues may Proactively manage In Progress Hinde David 20% 4 0.2
result in a budget overrun the budget
RMGARisk0326 I R1 fixes planned for R2 Monitor progress and In Progress Hammond 30% 4 0.28
may be late manage POL Christopher
expectations
RMGARisk0325 I Risk that R1 stability Define R1 stability In Progress Hinde David 75% 8 0.72
issues may impact R2 criteria
because of high volume
of R1 issues requiring
fixes and delayed
availability of LST
FUJ00095766
FUJ00095766
R2 High Level Schedule
Fe)
FUJITSU
Activity
Development
Drop 1—Drop 4
Drop 5- Drop 7 Peaks
Integration
Drop 1— Drop 4
Drop 5- Drop 7 Peaks
Test - SVI
Drop 1-Drop 4
Drop 5 - Drop 7 Peaks
Test -— LST
Cycle 1
Cycle 2
Deployment
Deployment data centre
Deployment Counter:
Model Office
Pilot
Full Rollout
Jan Feb Mar Apr May Jun Jul Aug’ Sep. Oct
Nov
Dec
I
15/06/10
24/5/10
(09/7/10
my 30/7/10
= 06/8/10
HB 02/8/10
wp 2/8/10
a 26/8/10
= 28/9/10
FUJ00095766
FUJ00095766
R2 Slip Chart j
far Apr May Jun I __Aug__I __sep_I Oct ! lov Dec
Dae [SO TMA MAS UT SOD TMA MB OR OOOO OT MUU BSUS HOO OH OT OW 7
IApplication Development 1
sats gonplte t
emletes
Drop 4 OH Panne Po teai0 '
copies, I
Drop 2 On Fetter Sa
s
Drop 5-7 Peak Fixes DH ' Some
i
1
Integration H
stats Completes i
Drop 1 PO ' road i
Starts Completes
Drop 2 Po ogiaa'10 “12/0310
stats Completes
Drop 3 PO za0310 0608/10
stats Complete
Drop Po jsato —— zryoan0
Drop 5-7 Peak Fixes PO
Ly
TEST
ISVI (System Validation & Integrity)
Drop 1 om
jetes
Drop 2 om See
stats __Complete
Drop 3 om yen fBOO4NO
1
3
Drop 4 om fens
3 Completes
Drop 5-7 peak fixes cM Bh cory STON
LST (Live System test)
stats Completes
Cycle 1 sB 12071 10
Completes
cyte 2 sB er
[Miaration
06 Star_bo completes
Deployment Data Centre cD 2707192108110
Deployment Counter: cp woo NO Comptes
Model Otfice co 9/080. “Tooert0
Pilot start__ ot Completes
Pilot co 12087 —er08/10
rolout Stat __Rotout Completes
Ful rollout cp 1400/10 —TEMB/i0
1 1
jeckNf 1 2 3 4 5 6 7 bo 112 wf 6 16 17 1810 20 21 es A ODT LHe a OM AT] a0 50 51
FUJ00095766
FUJ00095766
R2 Key Milestones
Fe)
FUJITSU
Drop 5 to CIT
03-May
DEV 03- May Started
SV&I Cycle 1 start (Drop1) TEST 03-Mar 03-Mar parted 3 days late but expected to complete on
ime.
SV&I Cycle 2 start (Drop 2) TEST 22-Mar 22-Mar Completed.
SV&I Cycle 3 start (Drop 3) TEST 12-Apr 12-Apr Completed.
SV&I Cycle 4 start (Drop 4) TEST 03-May 07-May Delayed to 7th May 2010 identifying opportunities
to catch up
SV&I Cycle 5 start (Drop 5) TEST 24-May 24-May
SV&I Cycle 6 start (Drop 6) TEST 14-June 14-June
SV&I Cycle 7 start (Drop 7) TEST 28-June 28-June
LST Start TEST 12-Jul 12-Jul
Start Model Office TEST 09-Aug 09-Aug
FUJ00095766
FUJ00095766
R2 Key Dependencies FUJITSU
Plan UID Task Name Baseline Owner Forecast RAG
f Finish I __ :
Testing
1530IGET: Drop 4 - MoneyGram Loyalty Card NA POL 04/05/2010
1555IGET: Formal accreditation VOCALINK testing NA Vocalink 24/06/2010
1564IGET: Formal Streamline - certification tests NA Streamline_I 01/07/2010
1574IGET: Formal Moneygram accreditation testing NA Moneygram I 01/07/2010
1706IGIVE: Drop 2 - Generate QandA NA Fujitsu 03/05/2010
1703IGET: Drop 2 - Final DOORS archive NA POL 10/05/2010 I
1709IGIVE: Drop 3 - Generate QandA NA Fujitsu 24/05/2010
1710IGET: Drop 3 - Final DOORS archive NA POL 31/05/2010
1712IGET: Drop 4 - Initial DOORS archive NA POL 07/06/2010
Development
834/GET: Stock Adjustments - Stable Use cases available from POL 11/05/2010 POL 11/05/2010 I
02.03.00.00
604/GIVE: MOP Support - AP-ADC Manual DES/GEN/MAN/0002 08/06/2010 Fujitsu 08/06/2010
Release and Implementation Plan
190I}GET: Drop 5 - Test ref data for drop 5 functionality 06/05/2010 POL 06/05/2010
189]GET: Drop 6 - LIVE ref data specifications (ADC receipt templates for Moneygram and 13/05/2010 POL 13/05/2010 I ~
Camelot Cheques)
188IGET: Drop 6 - LIVE ref data 27/05/2010 POL 27/05/2010
191]GET: LIVE Counter Rollout - Confirmation of phased functionality enablement 14/05/2010 POL 14/05/2010
requirements for Release 2 Counter rollout
FUJ00095766
FUJ00095766
foe)
FUJITSU
Beyond HNGX R2 Progress Report
David Court
FUJ00095766
FUJ00095766
HNG-X Target Releases , FUJITSU
la et) Dee I en Feb I ar
i En I
2st
Design & Build LST Post Office Ltd commited date
FUJ00095766
FUJ00095766
R3 Exec Summary FUJITSU
@ Key Challenges:
m AEI, POCa & Savings Gateway — primarily all Agent work.
= AEI — Baseline Req’s Catalogue & AIS; Design Proposal start next week;
Commercial cover via R2 approved CT; re-impacting for R3.
= POCa - Commercial cover via R2 approved CT ; re-impacting for R3.
m= Savings Gateway - Requirements and AIS to be completed this month;
Design Proposal baselined this month; impact for R3; CT to cover initial
design work.
=m POLVAT — complete CT by 3 week May; POL immediate approval
m Use Cases / Baseline of requirements in Doors
= Approving wrapper CT
m™@ Key Progress:
= Target plan walked through with POL
FUJ00095766
FUJ00095766
R4 Exec Summary FUJITSU
m Key Challenges:
= PO Essentials — issue CT now; POL approval; Note also related
POLSAP CR
mu TPOS - Requirements and AIS to be completed this month; Design
Proposal baselined next month; impact for R4; CT to cover initial design
work.
m Use Cases / Baseline of requirements in Doors
= Approving wrapper CT
™ Key Progress:
= Target plan walked through with POL
FUJ00095766
FUJ00095766
Fe)
FUJITSU
AEI Progress Report
David Court
FUJ00095766
FUJ00095766
AEI RAG Summa
Red Major issue impacting timescales, cost or risk Re)
Amber — Major issue but with actions agreed to resolve FUJITSU
_“” Green Noissues
RAG
Last
Status
Approved Budget
Resourcing
Schedule
Requirements
Architecture
Apps Development
Test
Migration
Infrastructure
Service Transition
Contract
CRs
Current
Status
Description G2G plan G2G Target
Date
{CT not approved CT Released for Customer Approval
Awaiting CT Approval ERICs being raised 14/05/2010
{Branch Priority (i.e. Tranche 3) not being
{released to Fujitsu with enough time to action
all activities
POL to use branches that have
progressed furthest
_INeeds bringing under HNG-X
CT Released for Customer Approval
FUJ00095766
FUJ00095766
AEI Exec Summary FUJITSU
m Key Challenges:
= Meeting POL Rollout Timescales / Scheduling has no tolerance
MOD Engineer Team Management
Access to POL Branches is frequently being denied / Uncooperative
BT Management and Issue Management
Failure Management
PO Branch Management
POL not releasing Tranche Information (Actual Priority of Branches for a certain
Milestone Date)
™ Key Progress:
u 142 Branches Completed (plus 17 Cogent)
= 320 Pre Installations Completed
u 437 PSTNs Ordered, 260 ADSLs Ordered
a
a
I
Pre Installation Visits proving affective
End to End Connectivity is Stable
Joined Up View Established with Customer
FUJ00095766
FUJ00095766
AEI Key Risks & Issues FUJITSU
m Risks:
mu Milestone dates at risk if information is not released by POL within the
agreed 36 working days for 150 Branches
mw Scheduling — Geographic Complexity is a risk to delivery
m Large number of Open Issues is a risk to achieving Milestones
m Changes to schedule (removal of Branches, not specifying Branch
Priority) is a risk to achieving Milestones
@ Issues:
Engineering Team not following Work Packages
FS Team stretched to working limit
PO Branches resisting BT and FS Hardware installs
PO Branches do not appear to have working knowledge of solution —
and appear to be re-directing BT Installations
FUJ00095766
FUJ00095766
AEI High Level Schedule FUJITSU
]
Activity Jan Feb Mar Apr Halt Jun Jul Aug Sep Oct Nov Dec
Design
Design complete & 06/04/10
Build
Router Build 06/4/10
Network Build gummy 09/04/10
Operations Centre ummm 09/04/10
Test
Model Office Test @_ og/og/io
Network test Gy 13/04/10
Service Delivery ‘
Service readiness 19/05/10
Deployment ‘
Go Live (first branch) B 13/04/10
nelout 31/5/10
FUJ00095766
FUJ00095766
AE! Key Milestones
Fe)
FUJITSU
Model Office Interim Router
06/04/2010
06/04/2010
All
Testing
Fujitsu Core Infrastructure FCN, DSL, 12/04/2010 12/04/2010
Setup NOC
End Datacentre Integration I FCN, DSL, 12/04/2010 12/04/2010
NOC
VLAN, Firewall, Sub Firewall, 12/04/2010 12/04/2010
Interface Networks
DSL to FCN Link DSL, FCN 10/04/2010 15/04/2010
Deployment of 10 Routers I Engineering, 12/04/2010 12/04/2010
per day to Post Office FCN, NOC
Branches
Tranche 1 30/04/2010 07/05 Tranche 1 completed except for
Issue Sites (still WIP)
Tranche 2 21/05/2010 28/05/2010 I Full Tranche 2 (150 Branches)
completion at risk due to high
volume of Issues
Tranche 3 25/06/2010 02/07/2010 I Full Tranche 3 (150 Branches)
completion at risk due to final
Tranche 3 Branch List not being
available within 36 day period
FUJ00095766
FUJ00095766
Cross-Programme Dependencies
Fe)
FUJITSU
Hip
Gib
it Ui DEPRES Us ERLE
iB
HNGX / POLSAP / R2
hedules need to be updated to reflect the Release 2 and POLSAP
Needed for wie Aug 2th, but expected to be
TWS sc
schedules. performed by IS UNIX under OCP.
2 IHNG-X/ POLSAP FTMS (File Transfer Management System) needs to be updated to reflect file Needed for w/e Aug 27th.
movement changes caused by POLSAP introduction.
3. IHNG-X / POLSAP Sysman3 changes needed to monitor POLSAP schedules (both TWS and SAP —_INeeded for w/e Aug 27th
intemal).
4 IHNG-X / POLSAP DAT update needed to reflect the changes in the interface to POLSAP. Needed for w/e Aug 27th
5 IHNG-X/ POLSAP Capacity Management team need to provide input to the performance assurance + IOngoing, now.
work,
6 —IHNG-X/ POLSAP Release Management to assist Service Transition team in defining ongoing release
process
7 IHNG-X/ POLSAP Decommissioning is dependent on POLFS Dev/QA move to IRE.
8 IHNG-X/R2 Stability criteria for R1 (tba) need to be met before R2 can be promoted to LST.
9 IHNG-X/ R2 Release 2 package can only be operational in branches that are running HNG-X
counters.
10 JPOLSAP / POL POL CR01962 required before POL can go-live on PING This is a dependency for POL, not between R2 and
POLSAP)