POL00028382
POL00028382
3@ SEP "98 15:52 FROM . TO S776395S si daestend
To: -
Fax Number:
Telephone Number:
From: Pore S Weng
BA/POCL Programme Delivery Authority,
3rd Floor,
Terminal House,
52 Grosvenor Gardens,
London SW1W OAB.
® Phone: 0171200
©) Fax: I GRO!
‘DSS Courier: London BA/POCL
Date: Ro\ Soav\ ae
Time: . Sj AU Dosen
Number of Pages: ; a *
Gaucluding This One)
RESTRICTED COMMERCIAL
‘This fix transmission and any accompanying documents may contain information belonging to the sender which
{s confidential and legally privileged, This information is intended only for the usc of the individual or entity to
who this fhesimile is addressed. If you are not the intended reciplent, any disclosure, copying, distribution or
action taken in reliance on the information contained herein is stricdly prohibited. Ifyou have received this
transmission in error, please call the sender to arrange for the retum of the documents.
Comments :
Bhs Qo TO Qe
—
A ssues Lay
loex — Tihs Is The fevsen
“SHOE Kin WoT To Ge ic
1 THesses Coreang, We _
Yikes Wey lone On
-
Conti) Rusts looms
© What
etre Wey S> We .
t eT I}
_
Yousas
30/09 98 16:29 ‘TX/RX NO. 1379 POL
62:9T 86, 60/0€
“ON XU/XL
6LeT
e0d
POL00028382
POL00028382
Horizon Implementation Plan ~ Points of Issue
w
Go
Statement of the Issue -BA View Horizon View Pathway. View Way Forward 3
1. Is there a consistent and A significant number of design. Tn the live environment EPOSS design has been The techuteal design of these - »
complete tcchinical design for key issues arc believed to be Reference Data will require exposed to, and documented systems ts complete but their 7
products (EPOSS and Reference —_ outstanding in these areas which disciplined processes to control _with, Horizon. There are no operabllity needs to be a
Data)? are a risk to the plan. and validate change and these outstanding design change confirmed in testing unit
BA have noted that Pathway aro being actively developed. requirements, Usabilityand Live Trial - this is a known . Fy
and [Horizon believe these issues ‘The impact of Reference Data on functionality are being tested _ tsk which Is being managed .
are under active management cash account production is being int current phase of work. in plamed areas of work e.g
but would like sight of progress.
BA would also wish to review
any functional ‘hangouts’ due in
MOR3.
On non-ISDN outlets and
mobile configs BA would like
evidence of progress.
flushed out in Model Office and
E2E testing,
‘There haye been a large
number of testing faults but
these are steadily being
cleared,
Live Reference Data
Proving, EPOSS Usability
Trlal. If this risk ls not
managed ther contingetrey
would be necded. RA further -
require:
2) Visibility of progress
(A Simpkins to provide by
IQ) -
2Thelr own assessment of
functlonal hangouts
(Pathway to provide details
by O10) ;
Unilerstaniling of progress
on non-ESDN and mobiles
{Pathway to provide by
HID).
Horizon Release Management - Version 2 30/998
Page 1
2
6Z:9T 86, 60/0¢
“ON XU/XL
6LeT
t0d
POL00028382
Horizon Implementation Plan - Points of Issue
w
So
Statement of the Issue BA View Horizon View Pathway View Way Forward * 3
2a. Are the required service No firm evidence yet available Preparation for and exccution of _ Activities and plans are Prepare TOR for eni-to-ent a
management products available to confirm adequacy. POCL Live Trial will provide visible in the Service ~ stuly and discuss with PA a
and scaleahte in Pathway ? next level of confidence and Management Forum, No {D Miller by 6/10) Fi
provide greater exposure of Known outstanding problems . Conduct the E2E service mgt
Pathway capability, identified by Pathway or review (D Miller by O/1) g
Sponsors at this stage.
2b, Will the POCL service Only embryonic function in Overall approach documented, . Will work with POCL to See 2a
management function be ready for place anda major challenge for and approved by CEC. Detailed ensure effective end-to-end
rollout ? POCL to develop planning and recruitment ore service as the provider of
. moving forvard.Outsourcing, Suppost for the infrastructure
‘arrangentent in process of tender and applications,
3. Can there be confidence inthe Doubts about Pathway ‘The Treasury Review Panel was — Many papers already BA to prepare alist of
scalcability of the ICL Pathway capability to support full rollout reassured on this issue, produced on which specific questions (P
design 2 General concer must remain as discussions have taken place, Crahan by W/1Q)
rollout proceeds but no further A further paper will be issued Horlzon/Pathway to respoud
Actions proposed at this stage - in October to support ata workshop before 16/10
Acceptance - any detail canbe under PA’s facilitation
addressed as required .
4 Will the speed of the accepfance Horizon have not yet produced Approach has been agreed. No Concern that all acceptance "Review already arranged at
process threaten key dates 7 aclear plan of tests and Teason why tests cannot be. spec sign-offs have not been — Acceptance Bourd on 1/10,
resources required and therefore complcted within the available’ completed ina timely Report to PA following
itis not possible to be confident timescale given co-operation manner, Acceptance Bonrd(D Miller)
in compiction by the key dates. Confirm detalt of plaus
cg, slart of acceptance tests at (D Miller by 16/10)
end of October,
2
Horizon Release Management - Version 2 30/9/98 Page 2 :
POL00028382
62:9T 86, 60/0¢
“ON XU/XL
6lZeT
0d
POL00028382
POL00028382
Horizon Implementation Plan - Points of Issue
8
Statement of Issue BA View Horizon View Pathway View Way Forward 7
5 Can the HPO drive the ° HPO is still not Wider HUO is now geared up; Pathway recognise PA fo review progress atid status 8
Programme forward and provide demonstrating effective 1. £im+.p.a. being spent on improvements haye been of HPO (by 9/10) a
robust moniforing of plans ? control of the programme. additional external resouree ‘made and that the general g
See specific items in 2. Detailed planning approach approach is now much more
G.McCorkell's letter to now in place focused on achieving delivery. a
Harry Bush 3. New processes developed in
Programme Office
6. What is the status of the plans No detailed plan has been . Pathway plan awaited, but Plan for NR2+ being dled CAPS amit NR2+ plans and dates
for NR2+? presented by Horizon for BA/CAPS also need to clarify but needs confirmation from fo be agreed und any impact on
. the delivery.of NR2+ and their requirement and CAPS BA/CAPS on CAPS releases. the key dates and approach tu the
this puts in doubt the date. ~ delivery dates, It will then be contents and dates, E.g. Replun to be assessed.
of February 2000. Later clear which Pathway or CAPS I IFCAPS 4.0 isnotavailable 4. Horizon to review pathway
delivery of NR2+ would activitics impact on the critical fora G month testing window plan (A Simpkins by 1/10)
impact multi-benefit cord path for NR2+. *- until Oct 99, then this may 2, Agree lutegeation with CAPS
rollout in terms ofnumber — NR2+- plans are not however delay NR2+ go-live until April (A Shupkins/P Jenkins by
of cards and outlets. expected to impact the NR2 2000 S110)
rollouttoPOCL offices. ~° 2) AlsoifCAPS4.0go-liveis 3. Provide NR2+ plan to PA (A
scheduled for Easter 2000 then Stinphlas by 7/10)
NR2+ may be delayed to this
date as well.
2
3
Horizon Release Management - Version 2 30/9/98 Page 3
ST 86, 60/0€
6e
“ON XU/XE
6LeT
sod
aer™
wk SB°S90d WLOL Kk
POL00028382
Horizon Implementation Plan - Points of Issue
8
Statement of Issue BA View Horizon View Pathway View Way Forward :
7a, Are there scrious problems in A number of BES faulis have . E2E accounting is not yct proven $ BES faults identified -2 with Problems to be resolved and 8
the areas of functionality critical been identified. A number of in the current test phasc-too carly CAPS,2 with Pathway, 1 escalated as part of the a
(OBA? functional hangouts also to judge if this will bean issue or —_ under investigation. normal test correction and g
exist, and there isancedto. —_ may prolong testing, roportiig process bit Horlzon
perform a business to respout to tprovements in F
assessment of the pinicl the reporting process
position. suggested by V-ince Guskell
: (A Simphins by 6/10)
7b What is the likelihood of the = Concernsat stippages and. Testing execution has been’ Agree that testing has had Joint test review with ull
current (est plinse achieving the limited coverage achieved to running in line with Horizon problems but not outside parties and PA to be
target date of 18/32/98 2 date - date not considered plans and expectations but number expectations, December date is rescheduled t0 13/10 (2)
8. To what extent ins the Replan
Improved the position on delivery
dates suggested by Treasury
Panel?
Is there a baseliued master plan
ageeed by the parlics 2
feasible,
BA also need to be
convinced about the
availability of contingency.
of faults is a concern. Still too
early to reassess likely completion
date, At least 2 weeks contingency
ayailable in January without
changing July rollout
Replan has not advanced,
and in fact put back by one
month, the full rollout of
NR2,
1, Replan hos de-risked overall
delivery by separating the
POCL and the card rollout
2. AllPOCL functionality (and
ChB) has been moved forward
from Jan 2000 to July 1999
3. Move of Full NR2 to February
2000 was at BA’s request,
being continually reviewed and
reported fo the fortnightly
Checkpoint meetings with
Horizon.
Agree with Horizon view.
Would like clarification as to
the BA’s planning assumptions
and dependencics on the
schedule for multi-benefit
Shupkins to arrange by 6/10)
PA (0 take ylew on the test
plan, the need for
contingency, and the
consequences for the later test
stages (PA by 14/10 but need
to combine with 8. below)
All partles (o support Horlzon
Programme Office tn
protucing full baselined
anaster plan by 9/10
Review plan wlth all parties ia
Aight of the wider actions
within this review (A Simpkins
by 13/10)
PA fo perforin risk assessment
and to share with parties on
44/10.
Horizon Release Management - Version 2 30/9/98 *
Page 4
POL00028382