Horizon Programme
POL00028100
POL00028100
Post Office Counters Ltd.
3rd Floor, Terminal House
52 Grosvenor Gardens
London
SW1W O0AB
Brief and Documents for CAPS Board meeting to be held on 18 September
Dave,
You asked for a brief, plus copies of documents referred to in the CAPS action
point status report, for your visit to the CAPS Board on Friday 18th. You
already have the Progress Report - but I have attached a copy for
completeness (attachment A).
The following provides:
(1)
(2)
(3) Status of MOR
1) Action status update.
You may wish to use the following table when reviewing the status of actions
from the last CAPS Board meeting. Additional information, not included in
the response to CAPS, is shown in column 3 (where available).
An update against actions
Information re Pathway plan V5.0
(1) (2) (3)
Action point. *2I:': Update:Reported:to, «I: Additional-Brief*
AP 5.4 (H) Cleared -Meeting held
Peter Crahan / Dave I 0n3/9/98.
Miller to arrange for a
final PDA transition
board to take place.
AP 6.1 (A) Ongoing - Update tobe I Now Cleared.
Mike Coombs to provided to Vince Steve Muchow,
provide an update to I Gaskell, copied to Dave I Pathway, faxed the
Vince Gaskell of the I Miller, by 16 September. I information to Vince
code changes being Gaskell - copied (by fax)
put in place to resolve to you - on Tuesday 15
the issue of September.
incomplete
transactions.
S:\\MONTHREP\98\ AUG98\DOC2.D0C
POL00028100
POL00028100
staff are on site and
present during Testing)
S:\MONTHREP\98\ AUG98\DOC2.DOC
AP 6.2(H) Cleared - Hard copy of I Copy of the extract
Dave Miller to extract from Support supplied to George
provide George Notice for NR2 (Model I McCorkell attached
McCorkell with a Office and End toEnd) I at B.
written description of I v1.0 detailing call _
the PinICL process. raising procedures .
(including PinICL hlpOdec —¥
process) provided to
George McCorkell. Tepe 7°
Complete document
held by P Noon (CAPS)
AP 6.3 (H) Dave Cleared - Short brief was I The situation, as
Miller to provide provided at the meeting I reported at the CAPS
Vince Gaskell witha I on 21 August. Board on 21 August, has
report on what has not changed:-
been done as result of ‘As discussed at the
the Correspondence Horizon Service Review
Server failure Forum on June 17th
(13/7/98) (CAPs represented by Paul
Hanson), there was a
failure on the main host
file system (sequent), on
the 11th June. Situation
handled smoothly. Seven
payments files were
delayed but this did not
impact on customers
receiving money.
Solution to prevent this is
to upgrade to the next
sequent release on NR2.
A Post Incident Review
(PIR) was not thought
necessary and not
undertaken on this
occasion’.
AP 6.4 (H) Dave Ongoing - Horizon Now Cleared.
Miller to provide Testing Manager to Simon Rilot had a
greater visibility of contact Parry Jenkins to I meeting with Parry
what is happening in I confirm requirements Jenkins on 15 September
Horizon testing to and progress as to agree action.
Parry Jenkins necessary. (Note - CAPS .
S:\MONTHREP\98\ AUG98\ DOC2.DOC
AP 6.5 (H) Dave Cleared - Copy of Copy of replan
Miller to issue a Horizon Programme document attached at C
formal note to all Replan document dated
concerned, giving key I 2 September has been
Horizon release dates. I supplied to the CAPS
PMO who have been
asked to issue it to
relevant parties.
AP 6.6 (H) Dave Ongoing - Dates List of forecast sign off
Miller to provide currently being dates attached at D
Peter Crahan with finalised. Expect to be
revised sign-off dates I available for Board
for all acceptance meeting on 18
specifications. September.
AP 6.7 (H) Dave Cleared - Details of Oral update provided at
Miller to arrange for I implementation activity I the Horizon
Bruce McNiven to (including the issue of _ I Implementation Board
provide Peter Crahan I RGM letters) are by Barrie Davies (not
with a detailed regularly provided (by I minuted).
breakdown of the ICL Pathway) to the
RGM letters Horizon Breakdown as at 14
Implementation Board I September:
which Val Curran Po Planned actual 7
attends. NE 450 519
NWNW_ 697 687
M 488 486
SWSW 686 679
NTEA 1324 1185
SE - oe
TOTAL 4402 4303
AP 6.8(H) Ongoing - Dave Miller I MSmail message sent to
Dave Miller to liaising with POCL Roger Tabor on 10
determine the current } Finance Director September asking him
state of debate regarding any assistance I to confirm that the BES
between BES/PAS required for resolution I / PAS boundary issue is
and see if dialogue in hand, and whether
between you and he need to
Horizon/CAPS discuss further.
directors could be (Ll understand that you
used to break the are meeting Ruth °
apparent deadlock. Holeran and Kevin
Corrigan prior to
meeting Mena Rego)
POL00028100
POL00028100
AP 6.9 (H) Dave Cleared -DIT2 closure I Copy of closure report
Miller to provide the I report supplied to Les attached at E
signed off DIT2 Hodson (CAPS Testing I All sign-off signatures
closure report Strand Manager) w/c7 I obtained.
September. (copy of closure report
faxed to Vince Gaskell
16 September)
2) ICL Pathway Plan v5.0
Version 5.0 of Pathway’s high level plan and Release Notes received 14
September - copy attached at F. This has not been issued to CAPS.
Horizon Release / Stage Manager and Planning have reviewed the plan with
Pathway PMO and variances against our Programme Level 1 plan have been
identified and action is under way to resolve the differences.
Note:
¢ The Pathway plan reflects a Child Benefit only Model Office, Live Trial and
National Roll-out.
¢ No information on the Multi-Benefits activities have been included.
¢ The duration of Live Trial shows only 11 weeks and does not reflect the 17
week replan proposal. This impacts the NRO start date.
¢ Activities up to the end of Migration are (mostly) in line with our replan
but there are major variances post start of the Live Trial.
3) Model Office
Model Office Rehearsal cycle 2 commenced on 14 September as planned. No
problems experienced. Forecast to complete 16 October.
Bob Burkin
Horizon Plannin;
Tel{
‘S:\ MONTHREP\98\ AUG98\DOC2.D0C
16 September 1998
POL00028100
POL00028100
huated\
(nnsider
ois nday
ok Ad]
Or2-
POL00028100
POL00028100
Input into CAPS Programme Board Report H
for Meeting on 18 September 1998 :
1 Introduction , Joe a?
This report summarises the state of the Horizon Programme as at August "oot
month end. i
I
2 Programme Overview ’
The major focus of the Programme at the current time continues to be: {
+ supporting the existing live systems fi
+ supporting the testing phase
+ progressing the ‘Programme Management’ content of the Replan with
respect to the Live Trial, multiple Benefits and the NR2+ Release.
+ clarifying the contractual implications and acceptance process arising
from the replan.
+ developing the Live Trial plans in detail.
+ developing the 1c to NR2 migration plans in more detail.
3 Live Operations
The current Release continues to provide a Benefit Payment Service and
Order Book Control System for Child Benefit Payments in 204 outlets
(119 in the South West & South Wales Region and 85 in the North East
Region).
From an operational point of view, there are no major threats to business
continuity.
Concern over the level of incomplete transactions (ITs) continues. These
have risen to 5.6 per 10,000 during July (from 4.0 in the previous month).
The main reason for this increase is due to a single category, BES/OBCS
Corruption (which represent 47% of all Incomplete Transactions)
Kee Operational workshops continue to be held to address this issue and the
resultant fixes for various categories of ITs have been placed in testing.
Evaluation and analysis of these fixes are imminent. If solutions prove
successful it is foreseen that categories of ITs and consequently volumes
will reduce dramatically - particularly those in the category mentioned
above. Forecast implementation of these solutions is 22 September (on
the assumption that testing is successful and passes acceptance by sponsor
organisations).
During July there were approximately 68,000 encashments (including
foreign encashments) with a total value in excess of £2m.
The Horizon Service Management Team continues to produce a monthly
Service Report which includes service performance reports and
: operational issues / threats. The latest report was-issued on 28 August
@ (BA/CAPS are included on distribution list).
SAMONTHREP\S\SEPT98\CB1809.DOC page 2 of 7
POL00028100
POL00028100
4 Progress against the Master Plan and Integrated Programme Plan
The Programme Master Plan (MP version 4) and Integrated Plan (IPP
version 1) will be updated following the formal agreement to the Release
2 replan. Progress is being monitored against Pathway High Level Plan
version 4.0 (15 June) and the current status of key milestones planned for
July/August is shown below:
iles : hieved
Direct Interface Testing 8 July Completed as planned. I ,
Start of Horizon Model 3 August Achieved -. Horizon
Office Rehearsal (for MO commenced 3
Release 2) August 1998.
Commence End to End 3 August Commenced on
@ testing (main pass) _ schedule
Commence Office Surveys, 3 August Work commenced in
Re-surveys and all areas
Modifications.
Complete System Test Main 30 August All these elements of
Pass for EPOSS, TPS, MIS, System Testing are
RDMC and Training (mode) forecast to complete
by 21 September.
Overall testing
timescales are
. consistent with replan
dates.
Complete Walkthrough of 31 August Extra work is required
E2E procedures (target date) in order to define all
processes to a lower
level of detail than
expected. This
milestone has been re-
forecast to complete in
November for
subsequent inclusion
_ in MOT.
Complete MOR I 11 September Successfully
completed 26 August
(earlier than
scheduled)
For this report, the list of the strategic and high level Programme
milestones (contained in the Master Plan (version 4) and Integrated
Programme Plan (version 1) showing their current status) has not been
included. The list will be reinstated when the current replan exercise has
been formally agreed and the milestones reviewed to ensure that they are
i) still relevant to the revised approach.
~SAMONTHREP\9S8\SEPT98\CB1809.DOC page 3 of 7
POL00028100
POL00028100
5 ICL Pathway Release 2
5.1 q Statu:
Planning
Dialogue continues in order to resolve issues affecting.the Replan
particularly with regard to the Live Trial, the multiple Benefits
introduction and the release of NR2+. Agreement has been reached on the
structure and dates for MOR, MOT and F2E activities for release 2
(POCL and Child Benefit functionality). In addition, agreement has been
reached on the Ic to NR2 migration plans. including the Data Centres, and
the installation of the extra 100 offices. Work is now necessary to develop
the detailed aspects of this plan and Pathway have been invited to
commence work in this area. Meetings with BA arranged for 9
September.
Testing
JSA MOT third cycle is progressing well and is due to complete on
schedule mid September in time to feed into (Horizon) MOR2 .
MORI completed satisfactorily on 26 August 1998. Overall impressions
of the counter service from the users (trained counter staff) and the
Horizon Test Team have been that the counter is working well: that it is
useable and resilient, that it performs with speed and that the error and :
exception handling messages/functions are present. The majority of
current problems are considered to be of minor importance and are
expected to be fixed for MOR2 which is planned to start on 14 September.
The MORI phase has been successful. Pathway have been able to prove
their live architecture. in particular the data centre and its migration, the
network and communications, and the connectivity between the counter
and the data.
E2E progress is slow but steady. The E2E cycle is being run in a more
deliberate manner than MO, allowing serious errors to be fixed before
progressing. The expectation is that most of the first cycle will be
completed by the target date. At this stage it is too early to predict whether
there will be an impact on the final end date of 18 December. The latest
position on testing will be presented by the Horizon Programme Director
to the CAPS Board at the meeting on 18 September.
Acceptance
During the period, management of the acceptance team was further
strengthened with the recruitment of an Incident Manager and a Process
Manager. Further recruitment continues to bring the team up to full
strength. A review of the support tools has completed and additional
hardware has been ordered. *
The acceptance framework, which provides a business top-down view has
now been developed and is being used to provide a review of the
adequacy of the acceptance approacli. A gap analysis continues and will
be completed by the first week in September. This will be followed by
SAMONTHREP\98\SEPT98\CB1809.DOC page 4 of 7
POL00028100
POL00028100
)
BSc aca
#
q
further analysis to determine whether the identified gaps can be filled by
other parts of the contract or whether they are true omissions.
The Acceptance Preparation Stage is continuing with the review and ‘
agreement of the acceptance specifications. ICL Pathway’s target for all
specs to be completed and signed-off by mid-August was not met and the
implications are being assessed. All 23 acceptance specifications have
now been received from ICL Pathway and reviews continue. There are
still a number of problems in this area and additional efforts are now being
brought to bear to improve the overall situation:
Formal management forums are in the process of being established for
acceptance. Draft Terms of Reference for the Acceptance Managers’
Forum have been completed and invitations to members will be issued
toward the end of August.
Implementation
General
The Implementation Risk Register has undergone a complete review with
the second iteration, including updates on mitigating action, issued 1
August.
The Horizon Implementation Board met on 11 August and will continue
to meet on a monthly basis to co-ordinate progress and address issues.
Installation
An updated Installation Strategy is expected from ICL Pathway for POCL
sign off by 21 August. A signed off copy of the Survey Requirements has
been received from ICL Pathway (excluding Flat Screens). A revised
Survey Document retlecting the Flat Screen option has been received and
is under review.
Training
Model Office training and training of Survey Support Managers has been
completed.
Migration
A draft plan and draft interim procedures for implementation of NR2 in
Release Ic outlets have been produced. ‘The Outlet Migration Strategy is
being redrafted by ICL Pathway taking into account recent developments
in the ECCO migration process. Discussions are underway with ICL
Pathway to obtain their sign-off of the migration tool functional
specification. Interim tools were used in MORI, and some difficulties
were experienced. Revised migration software tools will be ready for use
in MOR2.
Live Trial
Work continues to draw together the details based on the Horizon replan
which proposes a 17 week Live Trial. The justification for the 17 week
period has been presented to Pathway though this has not yet been
formally accepted by them given the wider contractual issues.
SAMONTHREP\9S\SEPT98\CB1809.DOC page 5 of 7 .
POL00028100
POL00028100
or
5.2
National Rollout
A meeting between Pathway and POCL increased the joint understanding
regarding the trigger points for starting rollout and the currently agreed
ramp up volumes. Further work is necessary to develop this and to link
with the Live Trial plans.
issues / Risks
The following areas of concern have been identified as possible obstacles
to the delivery of Release 2. These issues are being actively managed
within the Programme.
Issue
Action
End to End/Model Office Testing
While the first cycle of Model
Office completed ahead of
schedule, some problems have been
encountered in End to End testing
which may pose a risk to achieving
the 18 December completion date.
A number of actions are being
evaluated to improve the likelihood
of completion to schedule. Some
contingency time is also available
in January should it prove
neccesary.
BES/PAS Boundary
Agreement on this boundary is
necessary for establishing liabilities
in the live environment.
Action is with POCL Finance
Director who is reviewing the
position. Horizon Programme
Director continues to liaise with
Finance Director to provide input as
required.
BES Fallback
Additional mechanisms are
required to ensure the final
reconciliation of BES and EPOSS
transactions when a communication
line failure occurs.
Pathway are implementing an
agreed solution.
Acceptance Specifications
Some specifications are incomplete
due to unavailability of some cited
evidence and inadequate coverage.
This also impacts the clarity of the
plans for acceptance execution.
Continuing work with Pathway to
support the process of completing
the specifications and improving
their quality. DSS comments
outstanding on the DSS interface
specification.
Future Releases
Release 2+
The issue resolution process is continuing. For soft EVP the action is with
POCL to follow up the proposal from Pathway. There are no outstanding
technical issues concerning on-line enquiries though the issue around the
required delivery date is being progressed.
Pathways Release Contents Definition was received on 27 August and
distributed for comment.
SAMONTHREP\98\SEPT9S\CB1809.DOC page 6 of 7
POL00028100
POL00028100
A development plan for NR2+ should be available by the end of
September.
7 This report has been produced in accordance with the guidelines agreed ‘
between Peter Crahan and the Horizon Programme Director on 15 April. ,
The area not covered is ‘Routine Commercial / Contractual Activity’
where no request had been made by the CAPS PMO for specific detail,
and no input received from the Horizon Joint Contracts Team.
?
SAMONTHREP\8\SEPT98\CB1809.DOC page 7 of 7
POL00028100
POL00028100
499 ‘98 FRI 10:18 PAX {~ BA/POCL TEST SITE ++ TERMINAL *HOUSE - -@)002° & hi
ICL Pathway Support Notice - New Release 2 Version: 1.0
e Model Office & End to End Date: W858 :
Document Title: Support Notice - New Release 2 - Model Office & End to End ? ,
Abstract: This document describes the Support Routes for the Model
Office phases and End to End testing for New Release 2. It also. -
covers the release process for the Model Office and End to End
Status: Draft
me
Distribution:
ICL Pathway J.Bennett, M.Coombs, T.Austin, C.Humphries, J.Dicks,
D.Conniss, M.Fisk, K.Morley, M.Peach, L.Higman,
@. P.Gardner, G.French, B.Longley, G.Rogers, N.O’Sullivan,
P.Mead, P.Curley, J.Lindegard-Stewart, J.Wright, R.Aurora,
J.Bowes, S.Lee, A.Hanson, I.Morrison, P.Jobson
ICL Pathway Model Office _S.Palladino, G. Jackson, M. Molloy, J. Burgoine
ICL Pathway Development Product Managers
ICL Pathway Customer Service Management Team
Girobank . D. Wilson
DLR R. Ellis
System service B. McCully
Oracle K. Linfoot
HSHD/SMC S. Breen, R.Vigar, L.Cotterell, J.Opera
Outsourcing V.Cochrane, G.Boyce, S.Gardiner, C.Johnson, R.Bustard,
L.McGrath, P.G.Roberts
Horizon Test Team C. Young, J. Brett, K. Hall
a TIP P. Jones, D.Salt
@ cars P. Noon
POCL Service Management _N. Embling
POCL Migration Team T. Hacker
POCL RDP T. Baldwin
OSG / HAPS I. Blood
OBCS S. Bollom
PACS A. Smith
C. Oudot
Author: Pat Lywood
Comments to: Pat Lywood
o
COMMERCIAL IN CONFIDENCE Page 1 of 34 i
© 1997 ICL Pathway Ltd
11 SEP °98 19:23 AIM WS ERI ones AF
POL00028100
POL00028100
"“«@&
o
11 SEP °98 19:24
31/99 '98 FRI 10:19 FAX!
71h
ICL Pathway Support Notice - New Release 2 Version: 1.0 I
BA/POCL TEST SITE +++ TERMINAL HOUSE — - 003 t
Model Office & End to End Date: 1/8/98
41
4.2
4.3
Normal Working Hours Support
During Normal Working Hours, the support route will operate as the Live Operational
Service. All application, operational and infrastructure calls will be raised on the:
HSHD and Payment/Card/Pun related calls will be raised on the Payment Card
Helpline. (NOTE - Girobank are not providing the Payment Card Helpline facility for
E2E testing. )
The 2", 3rd and 4" Jine support routes will operate in a similar way to the Live ‘
Operational Service. The only amendment is that 3" line will pass calls to PIAT rather
than direct to development. If PIAT decide a fix is required they will pass the call to
Release Management to authorise the fix. Once the fix is authorised Release
Management will forward the call to development. See Appendix 4.
The expertise and knowledge of the Pathway T&I team may be used to aid in the :
support process during the MO period.
When a call reaches 3 line the call type will be amended to:
N- for MORI and MOR2
M- for MOT
E- for E2E
For full details of phone numbers and operational hours see Appendix 2.
Out Of Hours Support Routes
During Out Of Hours minimal HTT testing is planned. Any problem occurring out of
hours should be in the area of file transfer of data to and from the MO Data Centre,
transfer of data to or from the MO Counter Environment or problems to do with the
operation of the system.
The Support Route during these times is direct from Outsourcing Operations to 3rd
line support and the E2E or MO Manager. 3% line will call in whomever they deem
appropriate. The E2E or MO Manager is called in case there may be a delay to the
plan or authorisation is required to perform any data changes.
Call Logging
All issues requiring ICL Pathways attention must be logged via the HSHD.
For calls from HTT the FAD code of the relevant post office should be sufficient.
For calls raised by other areas involved in testing the following codes should be used:
PAT900 for MO
PAT901 for E2E
The HSHD call logger must ensure the text of the call includes a statement detailing
whether it is a MO or an E2E call.
COMMERCIAL IN CONFIDENCE Page’8 of 34
174 G0 Ean? mane ns
POL00028100
POL00028100
41/09 ‘98 FRI 10:20 FAX
oem,
BA/POCL TEST SITE +++ TERHINAL HOUSE Boos ~ i
aha
pre
: : fe
ICL Pathway Support Notice - New Release 2 Version: 1.0 “We
Model Office & End to End Date: 1/8/98
4.4 Call Logging for CAPS, TIP, ESNS, HAPS, PACS, RDS
Before a call is logged with the HSHD HIT should be contacted. HTT will discuss
the fault with the MO Site Manager or E2E Manager. The calling supplier will be
advised if a call should be placed with the HSHD or whether the fault is due to an
existing known condition. This process only applies to the following suppliers :
CAPS, TIP, ESNS, HAPS, PACS, RDS. ~
4.5 APT migration calls
All calls on APT migration should be directed to the APS helpdesk.
4.6 Data Warehouse calls
Calls telated to the Data Warehouse should be routed to PinICL stack CFM Support
2
4.7 Oracle support calls
During MORI, and the cycle 1 main pass of E2E testing, support for the Oracle
applications will be provided by Oracle Development with the support of ICL
Outsourcing. In subsequent testing phases support will be provided by ICL
Outsourcing with Oracle Development in a supporting role.
Calls for Oracle application support should be routed to PinICL stack Oracle 2
4.8 Reference data calls
Calls related to reference data should be routed to PinICL stack RefDataQual. The
‘Product group’ should be set, by 3" line support, to ‘Ref Data’. The ‘Product’ should
be set, by 3 line support, to ‘Ref Data Problems’.
COMMERCIAL IN CONFIDENCE : Page 9 of 34 ;
11 SEP 'S8 18:25 : @171 357 6523 PAGE.@4
POL00028100
POL00028100
41/99 ‘98 FRI 10:20 F/
- ae
BA/POCL TEST SITE +++ TERHINAL HOUSE @oos BAe
sors
ICL Pathway Support Notice - New Release 2 Version: 1.0
Model Office & End to End Date: 1/8/98
Sw
5.11 Summary and Timings
Tea ee ROUGE: Ta Raye iRIee Wiese Epstagey re =]:
1030 Reports Received From ICL Pathway suppliers and support route
1200 Report Received From TIP / CAPS / HAPS/ ESNS / RDS / PACS
1200 Report Received From HTT Via MO Site Manager or E2E Manager
1330 Consolidated Report Sent
6 PinlCL Management
@ The overall responsibility for the management of the PinICLs raised during the MO
and E2E period lies with the MO Manager and E2E manager respectively.
‘The Product or Service Managers, of both Pathway and it's suppliers, are responsible
for the management and timely resolution of PinICLs within their own stack.
7 Test control
Confirmation that MO and E2E testing is to be suspended or restarted rests with the
following people. They are responsible for ensuring that all interested parties are
informed of the suspension and expected restart dates.
MORI] & MOR2 MO Manager
MOT HTT MO /E2E Manager
Cyclel main pass E2E E2E Manager
. Cycle2 main pass E2E E2E Manager
o Final pass E2E E2E Manager
demevat met
COMMERCIAL IN CONFIDENCE Page 17 of 34
11 SEP 'S8 10:25 @171 357 6523 PARF.AS :
POL00028100
POL00028100
at
oy vengse
é “°
‘ithout Prejudice and Subject to Contract
HORIZON PROGRAMME REPLAN
. SUMMARY OF LEVEL 0 PLANS
aS.
Horizon Release Management
and Programme Office
2"! September 1998 ip
Summary of Plans Page 1 of 5 2™ September 1998
POL00028100
POL00028100
@ ; ® x @ "
Without Prejudice and Subject to Contract
1. Management Summary
4.4 Introduction
This document summarises and extracts the key planning information from the formally presented Horizon Replan Summary. The Replan has
been agréed by both Sponsors (POCL and Benefits Agency). ICL Pathway have agreed to work to the. plan while commercial negotiations are in
process. This summary is produced to support clear and consistent communication of the Replan within POCL and the Horizon Team, but copies
will also be provided to the Benefits Agency and Pathway. .
The Replan covers:
the new POCL infrastructure and services (including BES, EPOSS, and APS) together with card payment facilities on behalf of the Benefits
Agency (PAS and CMS) - these are referred to collectively as the ‘NR2’ release
supplementary facilities which are necessary to complete the contracted requirements and enable a _network-wide rollout (the ‘NR2+’
- release).
It also addresses the required interfaces with the Benefits Agency systems through an agreed plan with their CAPS Programme.
The focus of the Replan has been on the programme approach and timetable for the delivery and implementation of the new services. The Replan
will require the support of the Treasury Review and agreed changes to the contract and to the acceptance process. For the,time being all parties
are Working to the approach. Regular updates to this document will be issued to reflect developments.
41.2 Benefits of Proposed Approach ws 8
The Horizon Programme has proposed a fresh approach in this Replan which to a significant extent ‘decouples’ the Horizon and CAPS activities.
In principle it provides a two stage approach whereby the rollout of POCL infrastructure and services will commence initially with Child Benefit
card payments only, followed in the second stage by the rollout of the card payment service for multiple benefits. By separating the two aspects
of rollout (ie the ‘rollout of post offices’ from the ‘rollout of benefit card payments’), this approach will give. the management within the
Sponsoring organisations more flexibility to manage their individual responsibilities while minimising constraints upon each other.
Summary of Plans Page 2 of S 2™ September 1998
POL00028100
POL00028100
© e ; eu.
Without Prejudice and “Subject to Contract 2
In summary therefore the decouple approach will: *
« reduce the complexity of the joint management and integration of activities
« provide the earliest achievable date for Pathway to rollout services to the POCL offices, with an estimated date of 5" July 1999.
support the CAPS work programme for integration of the Feeder Benefit Systems
* build on the proven experience of Child Benefit card payments, and follow this by the rapid rollout of the ‘multi-benefit’ service as soon as it
is proven
« enable a staged acceptance of the Pathway service, with full contractual acceptance, to include the delivery of NR2+, in February 2000.
1.3 Plan Summary
A high level presentation of the plan is shown in Appendix 1. This is taken from the agreed Replan Proposal. There are two main stages:
¢ POCL Services/Child Benefit .
¢, Multi-benefit Stage (to include JSA, IS and Pensions)
The dates provided are based on the Sponsor’s current best view but will be subject to the agreement of detailed plans.
4.3.1 Stage 1 -POCL Services/Child Benefit
This, stage results in the commencement of rollout of the POCL infrastructure and services in July 1999 together with the support of Child
Benefit payments in every office as it goes live on Horizon. The main steps in this stage are as follows:
Pathway delivery of NR2 into Model Office 3" August 1998
Model Office testing 3™ August to 18" December 1998
Start joint Model Office testing with CAPS From 14" September 1998
End-to-End testing 3" August to 18" December 1998
Start Migration of the 204 ‘1c’ offices to NR2 * 4th January 1999
Start POCL Live Trial (child benefit) 8th February 1999
Complete POCL Live Trial (child benefit) 4" June 1999
Contingency period for testing and Trial (4 weeks) Up to 2" July 1999
Start POCL/Child Benefit rollout . By 5" July 1999 =
Summary of Plans Page 3 of 5 2™ September 1998
POL00028100
POL00028100
Without Prejudice and Subject to Contract i
Given the scale and scope of the processes which need to be proven in Model Office and End-to-End testing the plan seeks to provide a
‘contingency window’ at the end of these stages. If they complete satisfactorily by 18" December, with Release Authorisation by Christmas, then
the Migration step can proceed on 4" January. However a contingency provision is made for testing to continue until 11" January if necessary,
with Release Authorisation by 15th January. This would result in Migration starting on 18" January. The POCL Live Trial, which follows 5
weeks after the start of migration, is scheduled to start therefore on 8" February, or 22" February if the contingency is required . A decision on
whether this contingency window is needed will be made by the end of October 1998 when the rate of progress on testing will be clear.
The Live Trial is scheduled for 17 weeks finishing on 4" June 1999. The earliest date to start the post office rollout would therefore be 7* June
1999. However the testing contingency of 2 weeks discussed above may be necessary and a further 2 week contingency period is provided at the
end of the Live Trial. This gives a rollout start date of 5" July 1999. If neither the testing contingency nor the POCL Live Trial contingency are
required then rollout can commence at the earlier date of 7" June 1999. A decision on this earlier start for POCL office rollout will need to be
taken at the latest by 1* April 1999. This date will allow sufficient evidence to be assessed from the Live Trial while giving at least 8 weeks to
manage the lead in to the post office rollout. The Benefits Agency card rollout could be brought forward to the 7" June 1999 only if notice is
given by the end of October 1998. Otherwise the planned date for card rollout will remain as the 5* July 1999. On the other hand unforeseen
problems, whether of a business or technical nature, could be found in the Trial (which is the reason for undertaking it). Through careful
monitoring and timely action the Programme will however strive to ensure the rollout does commence by Sth July 1999.
1.3.2 Stage 2 - Multi-Benefit Stage
The Multi-benefit service will run on the same NR2 software platform as the Child Benefit release but will utilise-the more complex processing
associated with, for example, urgent stops and payments. It will also require integration with the three additional Feeder Benefit Systems for
JSA, IS and Pensions,
The Multi-benefit stage therefore begins with a ‘pre-proving? testing activity prior to entry to the full Model Office environment in order to give
initial confidence that these transaction types can be correctly processed. This work will commence from 1* December 1998.
The main steps in Stage 2 are as follows:
Pre-proving tests December 1998 to March 1999
Summary of Plans : Page 4 of 5 2™ September 1998
POL00028100
POL00028100
Without Prejudice and Subject to Contract
Joint Model Office 12" April to 1" October 1999
Multi-benefit Trial starts 13" September 1999
All benefits into Trial By end November 1999 ”
Full acceptance of NR2 February 2000
Multi-benefit card rollout starts From 28" February 2000
By February 2000 several thousand offices will already have been rolled out from Stage 1 and there will be an existing base to which cards can
be deployed. Card deployment for JSA, IS and Pensions can therefore take place as quickly as practical to their offices, subject to maintenance of
an acceptable level of service. It will then follow the continuous office rollout .
The Related Agreements with Pathway also includes delivery of the NR2+ software release. This will provide additional functionality to support
a network wide deployment (notably On-Line Enquiries and Soft EVP - Extended Verification Procedures) as well as additional POCL services
such as AP Smart. The final design of NR2+ functionality is currently being completed which will be followed by a formal development plan to
be agreed by all parties. Based on discussions to date with Pathway, the Sponsors believe that it is reasonable to expect that NR2+ could be
delivered into joint sponsor acceptance testing from 1" October 1999. This would be advantageous in that the acceptance processes for Multi-
benefit and NR2+ could be run concurrently to complete in February 2000. Confirmed NR2+ development and testing and deployment dates do
however need to be established by more detailed planning and with the agreement of all parties.
1.4 Summary Plans
Appendix 1 shows the representation of the high level Replan which was included in the Replan Proposal. eh
Appendix 2 shows the formal Level 0 Plan for the Programme showing the key dates established in the Replan process. Changes to the Level 0
Plan are the responsibility of the Horizon Release Management Team who will agree them with the other parties.
The Level 0 Plan will be supported by more detailed Level 1 and 2 plans, covering the various areas within Horizon, Pathway and the Benefits
Agency. These plans will be co-ordinated and consolidated by the Horizon Programme Office.
Summary of Plans Page 5 of 5 2™ September 1998
POL00028100
POL00028100
Horizon Programme Replan Appendix 1
1999
SE ier ay ee ee dykes
fei tt ett shoe leat bee ee ed pete
‘ ; : NR2:Model Office : ; p ; ; : : ; : ;
: [ChB / CAPS3.0}
: 2 . ‘ r : Reledse :
Sak : :NR2 End-to-End : authorisation : : i
See eg CHB. CAESS-O1 5S Start office rollout
CAPSJSA_ : amas eetie cia tee ak sees. ar eg Hie eee
Model Office :
Multiple Benefit:
Joint online : :
payments/stops etc’ a
pre-proving : Multi-Benefit Model Office : :
NR2/ CAPS3.0 /JSA /IS / PSCS
A
CAPS 3.5:
: Multi-benefit
: Card: rollout:
All benefits
into trial :
A
Multi-benéfit Trial
Release into H : : : : : :
Model Office: : c i : : : : ACCEPTANCE
26 August 1998
POL00028100
POL00028100
log co] VY UY o
BA/POCL PROGRAMME arene
NILE RELEASE 2 INTEGRATED PLAN - LEVEL 0 Date :2 September 1996
298 T 1999 T 2000.
I T sas pew sot] roson [STH TATSTOINTD STF INTATHT ST TATSTOTHIOISTFIMIATNTS TS TATSTO
I aad aad —
I = NH
I Pathway S188 I 076 ey PH POIc Stameer I
I yess 161296)
I ~ey Patway 9808) 1106I Ld py H/po
re} PatwayI 14986 16/1006) mp P/HIPOIC
BBE Petway YBI008) ane ems P/N/POLC ECS
7 iModel Otic Test Cycle 4) Horizon’ zane 181288 cP/H/POC Proposal Summary paper dated 2
aE 2 as {ay 1998 arc addencum no of
9] Endo End (ChBICAPS 3.0) 3ess 181298 19 August 1998,
[io] Pass Patwey 3086, 16088) CL pu ypore
fav] Pass2 Pathway § 21898 31186 cP /HiPOLe
[72] Final Pass Patway 41198) 181298 cP /H/POVE
73] Acceptance 1s1098 17/198
[fa] ~~ Aecsane Tl oun ot Patway 188 Ta mist ae
[75] Release Authorisation / yenase) ten2ee
I eq Release Authorisation Board Hodaon'CAPS I 1ei2eeI 181288 NIC (\I Rseeee Aatertoston
[a7] anes z7n99
Te] anne) “13180 iy P/H/PO
14188 27780 ‘er iniPO
30799) wine
4 2
mo P/H/PO
=P /PO I
eauic
HIC /\ Acceptance (1)
o
PUWIPOG (aera re
ceo PHO
12499 11088
12498 28/580
xa P/H/POVe
ea PHI POVe
xa P/M/POVe
= P/M/PoVe
wveseI 788
12788!” boa
2am) 108
139199) 27/200
vase! 51188
81188 I 261188)
wanes 277000
zaniee” 2enie9
2720 27200
22200 61000
287200 “6x00 ic
‘0798 I ~ €10000I
“Bae
2in0e®I 14200
270 I 272806
200) 6/0100
‘wees 17/7090
sian 111099
sane’ 5498
Pook! 11088! sinoe Aro
aeee 11080)
CAPs; weve! 11486
] «I @I 2] @] 8] 2] s[ a] 8] 8] e] eo] e) ey a] 2
cP /H/PO/C
ma P/HIPOIC
eo PH IPO
A, AI Bonotits into Tris!
Accoptanes (2) /\ H/C
£) 8) 8] 5)
I aie
(res P
ces P/H/POVC
Acceptance (3) & Release Authorisation /\ H/C
£] 2I s] =] 3] e[ [4
carsI ieee) a0
CAPs) iinome) ivhase
A, CAPS35 Release ino Model Otice Eaty Apel 90
L\ CAPS 35 Release Go Live In May / June 99
CAPS 4.9 Release Go Live (Provisional) /\,
Ss PG NT Mlosione A
ASLEVEL_08.MPP Paget
Version 0.1 (Draft - Issue For Review / Comment)
CONAMAWON=
0
Acceptance Test Specifications RAG Status Report - Summary -
Acceptance Specification
APS/HAPS
Audit
BES
DSS (CAPS) Interface
CMS
End to End Acceptance
EPOSS
Help Desk
Implementation - A User Training & Documentation
Implementation - B Customer Education
Implementation - C Services
Implementation - D Rollout
MIS
OBCS
Operational Trial (Schedule C3)
PAS
POCL Infrastructure
Policies & Standards
Reconciliation
Reference Data
Security
Service Levels
TIP Interface
IRAG Status
IGREEN = before 19th October
AMBER = 19th - 25th October
RED = After 26th October
Sign Off
Imminent
29-Sep
30-Sep
48-Sep
30-Sep
16-Oct
16-Oct
04-Nov
Imminent
09-Oct
Imminent
09-Oct
Imminent
Imminent
16-Oct
30-Sep
30-Sep
30-Sep
OctNov
16-Oct
30-Sep
16-Oct
16-Oct
Notes
Spec ready for approval - subject to contractual completeness check
Review meeting scheduled for 22/9
PAS-BES boundary issue yet to be resolved (No. 67 in issues database)
No known issues
No known issues
To be confirmed
16 Oct is aim date for approval. Feasibility to be confirmed
Pathway due to release spec for approval on 28th October
Spec ready for approval - subject to contractual completeness check
Change request and CCN paperwork to be raised
Spec ready for approval - subject to contractual completeness check
To be confirmed when outcome of 11 Sept meeting is known
Spec ready for approval - subject to contractual completeness check
Spec ready for approval - subject to contractual completeness check
No known issues
PAS-BES boundary issue yet to be resolved (No. 67 in issues database)
To be confirmed
To be confirmed
Pathway not due to release next issue until end Sept. (Testing by doc review)
To be confirmed
To be confirmed
To be confirmed
Outstanding issue regarding comprehensiveness of spec to be resolved
NB
1. We are still waiting for a detailed schedule from Pathway giving test dates
2. Itis assumed that Acceptance Testing is due to start on 19th October
POL00028100
POL00028100
®. .
16/09/98
RAG Status
GREEN
GREEN
GREEN ~
GREEN
GREEN
GREEN
AMBER
RED
GREEN
GREEN
GREEN
GREEN
GREEN
GREEN
GREEN
GREEN
GREEN
GREEN
RED
GREEN
GREEN
GREEN
GREEN
3. All RAG status indicators are relative to the 19th October start date, NOT the sign-off date
Page 1 of 1
~Y
4
POL00028100
POL00028100
i
Author:
Bruce Talmage
Signature:
Date: 28/08/98
Authorised: Simon Rilot
Signature: __GRO a :
Date: 28/08/98
Document Reference:
New Release 2
Approved:
Simon Palladino
Peter Jones
Les Hodson
Andrew Fretter
Linda Vel
John Lees
Organisation
ICL Pathway
TR
CAPS
HAPS
ESNS
PCL/TST/CLR/001/V2_0
ee
Signature: Date:
Document Version: 2.0
Document Status: FINAL
28/08/98 Page 1 of 16 Version 2.0
Status —- FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
Horizon Programme - -
0. CONTENTS
0.1. DOCUMENT CONTROL..
0.2. REFERENCES.
0.3. GLOSSARY...
1, MANAGEMENT SUMMARY
Ld SUMMARY.
1.2. CONCLUSIO}
2. INTRODUCTION.
21 DOCUMENT PURPOSE.
2.2. DIT TESTING OBJECTIVES.
3. TESTING APPROACH
OVERVIEW.
DIT 1.
DIT 2.. .
. 1. Extended Interface Testing (EIT).
3.2. PARTICIPANTS...
3.2.1. ICL Pathway.
3.2.2, Horizon Testin;
3.3. Test SCRIPTS..
3.3.1, Timins
4, TESTING COVERAGE.. 9
4.1, EXCLUSIONS/SHORTFALLS. 9
4.2. END2 END I" PASS WEAKNESSES 9
4. Reference Data Proving. 9
4. Migration... 9
4.3. DESIGN STABILITY... 9
5. INCIDENTS... pa
5.1. INCIDENTS RAISED DURING DIT 2cessessrsnesnerernnenne . if
6. OBSERVATIONS & PROBLEMS... 12
6.1. TEST PREPARATION...
Reference Data Configuration
1.2. BES Cards...
6.2. HAPS CLIENT CARO!
6.2.1. Errors in Payment Author
6.3. TESTING EXECUTION ERRORS.
7. LESSONS LEARNT.
7.1, READINESS TO START.
7.2. DATE AND DATA ALIGNMENT.
7.3. DIT 2/END2END 1 PAss.
7.4. PRE-REQUISITE OF AN INTEGRATED ENVIRONMENT,
7.5. REFERENCE DATA INTEGRITY ....
APPENDIX A- INTERFACE SPECIFICATION VERSIONS....
APPENDIX B— OUTSTANDING PinICLs. z 15
PINICLS PLANNED TO BE RE-TESTED PRIOR TO END2END/MOT ..
OTHERS...
PINICLS AWAITING ACTION BY POCL..
28/08/98 Page 2 of 16 Version 2.0
Status —- FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
a
POL00028100
Bs ~' > +: DIT Closure Report for New Release’2--.--
0.1 20/07/98 Initial Draft for comment .
1.0 30/07/98 Final version
i 10/08/98 Changes due to comments from Nikki O'Sullivan (Pathway) and Peter
Jones (Pathway). Signatures received against version 1.0 from Les
Hodson (CAPS), Andrew Fretter (POCL RDP) and Graham
Shervington (HAPS). t+
2.0 27/08/98 Final amendment to paragraph 42. 1 to satisfy wording requirement
from ICL Pathway.
0.2. References
A. Revisions to the tess = integration “Approach VU/STROO6 V2.0 24/1 10/98
for Pathway Release 2.0
0.3. Glossary
BA - Benefit Agency
BES - Benefit Encashment Service
BIT - Business Integration Testing
CAPS - Customer Accounting and Payments Strategy
DIT - Direct Interface Testing
ESNS - Electronic Stop Notices System
MOR - Model Office Rehearsal
MOT - Model Office Testing.
OBCS - Order Book Control Service ~
PinICL - ICL owned incident reporting application
POCL - Post Office Counters Limited
28/08/98 Page 3 of 16 Version2.0 I
Status — FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
7 Horizon Programme be DIT Closure Report for New Release 2
see
L MANAGEMENT SUMMARY
The execution of the DIT 2 script was completed on the 8* July 1998 with all output files being
accepted by each of the parties involved. Therefore, although some faults have been found and have
yet to be cleared, all parties agreed that DIT had completed on that date.
All the DIT testing objectives have been met although for various reasons, not all as a direct result‘of
DIT, the End2End 1* pass objectives have not been entirely satisfied. In particular the End2End 1*
Pass objective that was not met is with regard to the proving of the Pathway End2End environment.
The reasons for this are given in Section 4.2. os
This means that there are some minor risks carried over to the End2End 2 Pass that would have been
expected to be resolved in a full 1* Pass. . ‘
LL Summary
In summary, the findings of the DIT phase are as follows:
= The Horizon Application was, by the commencement of the second attempt at DIT 2, stable and
capable of supporting the parallel DIT activity. There are a number of system faults that have been
discovered and Pathway are attempting to clear these prior to the commencement of End2End and
MOT. These are detailed in this document in Appendix B — Outstanding PINICLS.
- The Design. Although the interfaces operated to the agreed specifications, a number of issues have
either been raised concerning the design itself or were known to be issues with the agreed
specification at the time of commencing DIT testing. Some of these are currently the subject of
proposed design changes or discussions that may result in same. These are being progressed in
other areas of the programme and are discussed elsewhere in this document (See Section 4.3).
However they are only of concem to DIT 2 in that they may undermine the testing that has taken
place by altering the underlying design baseline.
= Test Preparation was complicated by the need to ensure the compatibility of the individual
interface tests and the parallel activity to take place in DIT 2. This meant a “date/data alignment”
exercise to validate the dates and data (as supported by the common reference data), which
inevitably led to a number of complications in both the derivation and the agreement of the test
scripts - particularly the joint script that was required for DIT 2.
There were also a number of problems with the setting up of the DIT 2 environment prior to the
second attempt at running it, which are highlighted in Section 6.1.
1.2, Conclusion
While a number of problems were experienced with the system during DIT, the majority of these have
now been fixed and re-tested, or are in the process of being fixed prior to commencing MOT and
End2End, Therefore, this report concludes that it is safe to commence the End2End and MOR
activities, although the de-stabilising effect of any design changes should be closely guarded against.
. "These have now been accepted by the MOT and End2End managers and are being managed as part of
(-} those test phases,
28/08/98 Page 4 of 16 Version 2.0
Status - FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
—
Horizon Programme DIT Closure Report for New Release 2
2. INTRODUCTION
2.1. Document Purpose
This document summarises the objectives of DIT and describes the approach taken during DIT. It also
provides a presentation of results following completion of the DIT test phase and provides a method
for agreeing between all participants the closing status.
22. DIT Testing Objectives
The objective of Direct Interface Testing can be described as follows:
To ensure that each of the interfaces, between the key primary systems/organisations and
Pathway, are operating to specification and in a stable and predictable fashion.
It is not intended as a system test of the internal/business functionality of any of the involved systems.
That is an activity that should be run independently of the interface test by each of the systems
involved.
Clearly the focus is on the ability to correctly transfer data in the formats and structures expected by
the systems receiving the data. The data is passed through the external facing validation components of
those systems to validate this and testing is conducted using links that are as close to live
configurations as possible.
However, in line with the approach agreed in Reference A to fulfil the objectives of End2End 1* Pass
during DIT2, the DIT environment is to be adopted for use by End2End testing and the following
additional objective was added to DIT2:
To commission the environments, including the links between them, to ensure their readiness
for End2End.
The following diagram shows the interfaces in question. Note that there is a secondary interface
between TIP and Reference Data, which was also tested within DIT, as this provides evidence of the
ability to keep the Reference Data of both TIP and Pathway in step with each other.
Reference TIP
Data “>I
Na th Hi
Pathway APS
OBCS CAPS
During the preparation for DIT2 the decision was taken to ensure that a reasonable degree of integrity
exists in cash accounting — this being one of the central focuses of attention of the End2End phase.
This required a level of functional stability that would otherwise not be required during DIT.
28/08/98 Page 5 of 16 Version 2.0
Status — FINAL Ref: PCL/TST/CLR/001/V2_0
Horizon Programme DIT Closure Report for New Release 2
3. TESTING APPROACH
3.0 Overview
The DIT testing phase, as described in Reference A is split into two distinct test phases as shown in the
following diagram:
ITI
pITL
DIT2/E2E Ist Pass
DiTl
pit!
1 Stream Per Interface Parallel Running
3.1.1. DITI
The DIT I activity was completed without the benefit of a fully integrated Pathway product. It was run
‘on two Pathway test rigs, each operating with a subset of the interfaces and the underlying
functionality. This was carried out in parallel with the Pathway BIT testing before deployment ofan
integrated product onto a single rig for DIT 2. The following diagram shows the split between the two
DIT rigs:
Reference I_ TIP
Data
The DIT I test phase also provided the opportunity for extensive negative testing to take place for each
of the interfaces. This was testing of failure conditions, some of which needed to be simulated to
represent the appropriate circumstances of the failure. These were, in the main, not carried through to
the DIT 2 test as this would have caused too much disruption to the overall execution of that parallel
run,
One of the consequences of this split in both functionality and physical rig was that it was not possible,
within DIT 1, for the TIP interface to be proven with the transactions that were generated from the
HAPS, CAPS and OBCS supporting functionality.
This would have meant that the interface was only partially tested prior to DIT 2. In order to
circumvent this problem, Pathway furnished TIP with evidence of BIT test activity.
28/08/98 Page 6 of 16 Version 2.0 I
Status — FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
POL00028100
POL00028100
ja
Horizon Programme DIT Closure Report for New Release 2
eoxtehce
Paes
3.1.2. DIT2
Prior to DIT 2 commencing, a script was produced from the underlying DIT I scripts that represented a
period of execution that would be triggered by, and triggers, data across each of the interfaces.
Although this was an opportunity for each of the systems to test their individual interfaces again, it
became apparent that the test phase was very much for the benefit of TIP and Pathway for the
following reasons:
© Each of the other systems were generally satisfied with the level of testing already carried
out. This was particularly true of CAPS who, despite having a couple of minor negative
tests to complete at some stage, felt that the interface hiad been appropriately exercised by
the end of DIT I.
* Pathway would be given the opportunity to exercise the integrated product to ensure that
the interfaces still worked correctly when run in combination.
© TIP had largely only had simulations of data for the areas of the system not shared on
their DIT rig. The DIT 2 script enabled them to receive data combinations of differing
types and sources that had not been possible during DIT 1.
For the TIP interface to be proven to the satisfaction of TIP (taking into account their detailed scripting
of expected results), and in accordance with objectives to operate DIT 2 asa 1" Pass for End2End, the
Cash Accounting functionality had to show a “reasonable” degree of integrity. Although this ventured
into the areas of functional proving it was decided that this was a valid pre-requisite and in a meeting -
held on 30 April it was formally agreed that the cash accounting must demonstrate this integrity prior
to commencement of (and for the duration of) DIT 2.
3.1.3, Extended Interface Testing (EIT)
During the course of DIT there were requests from cach of the participants for tests that were not
strictly within the scope of DIT, or could wait until End2End, but that made sense to be
accommodated, if possible. Rather than expand the scope of DIT and detract from the primary
objectives. These tests were provided at quicter moments in the testing schedule, These were also
sometimes referred to as “supplementary tests”.
3.2. Participants
The testing teams responsible for each of the systems involved liaised with the Pathway test team/s to
ensure that their test requirements within the scope of DIT were included within the test phase. They
also provided test data where appropriate in support of their own tests and those that were required to
generate the necessary outputs for other systems ¢.g. TIP.
‘The testing teams of each system were responsible for checking the data received by them for
completeness and accuracy and notifying Pathway where discrepancies rose. These were then
investigated and an agreed explanation or resolution put in place.
Each testing team also provided representation and verbal or written progress reports through the
weekly DIT Co-ordination meeting and any such other ad-hoc mecting that was deemed necessary
during the test phase.
2.1. ICL Pathway
ICL Pathway, through the authority of the DIT Manager, was responsible for the final say on any
decisions regarding scope and timing of each of the DIT test phases. Where possible this was done
with the understanding and full agreement of all parties.
3.2.2. Horizon Testing
‘There was no direct Horizon testing involvement apart from the DIT Co-ordinator's role. The DIT Co-
ordinator ran a weekly co-ordination meeting where progress and issues were recorded. These were
formally minuted, circulated to all attendees and agreed. These are available for inspection in either
electronic or paper from the DIT Co-ordinator. .
28/08/98 Page 7 of 16 Version 2.0
Status — FINAL Ref: PCLITST/CLR/001/V2_0
POL00028100
POL00028100
.
* Horizon Programme DIT Closure Report for New Release 2...
33. Test Scripts
Individual scripts were agreed for DIT 1 between ICL Pathway and each of the parties.
Reference data produced one script for each of the drops of data that they provided. As the reference
data drops were incremental these were issued and agreed with the release of each drop of data.
AtDIT 2a joint script (version 11) was agreed between all parties. This version was shorter than
previous versions, having been reduced from 38 days to 17. This reduction centred on the removal of
differing lengths of accounting periods. The DIT Manager took this decision on the basis that the
length of the accounting periods has no specific effect on the Horizon solution and therefore is not
pertinent to DIT. ue
3.3.1. Timing
ity proceeded approximately to plan - the underlying plan being the subject ofa
is over the period.
An initial attempt at DIT 2, starting on 20" April, was unsuccessful and it was agreed after one week
that the Pathway integrated product was not at the standard required to continue. There was then a
pause, allowing some EIT work to'take place and for the Pathway System Test and BIT test phases to
make more progress. During this time Pathway provided evidence of the progress being made,
particularly in the area of cash accounting. A fresh start commenced on 16% June.
28/08/98 Page 8 of 16 Version 2.0. I
Status — FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
i
Horizon Programme
4, TESTING COVERAGE
4. Exclusions/Shortfalls
The following areas were either not covered to the satisfaction of all parties during DIT, or were
specifically excluded from the DIT scope. They are therefore risks carried over into later test phases:
© The testing of extended accounting periods was excluded from the test script for DIT 2.
This specific functionality will therefore first be covered by End2End and is considered
by Pathway to be low risk -
«No BES Card based (swiped) transactions were carried out. All card activations and -
encashments were manually processed. Pathway gave assurances that this specific
functionality has been tested elsewhere and therefore, in their opinion, the risk of this
omission in minimal.
«Migration.
* Any acknowledged gaps in the interface design/s, as noted in the agreed interface
specifications were specifically excluded from DIT. In particular the handling of BES
exceptions in the TIP reconciliation process.
4.2, End 2 End 1" Pass weaknesses
4.2.1. Reference Data Proving
On top of the problems with the configuration management of the reference data mentioned in Section
6.1.1 the approach to the provision of the End2End reference data changed during the period of the
DIT 2 execution.
‘The original intention was that the DIT reference data would be used for End2End. It has now been
decided that the End2End data is to be constructed from live reference data, in the same way as the
MOT data, ageing it appropriately to match the run dates agreed for End2End.
It was not an objective of DIT to test the capability of TIP & Pathway to take incremental reference
data drops & keep in step with each other. This will be tested elsewhere.
Consequently the reference data has not been pre-proven for End2End by DIT.
4.2.2. Migration
As migration is currently planned as the opening activity in the End2End High Level Test plan the
Pathway test environment will be partially, if not fully, re-configured for the purposes of the migration
test. There is a risk associated with this break in continuity that the environment proving will be
undermined.
4.3. Design Stability
A number of changes are currently under consideration, which may affect the interfaces in the future.
‘These are as follows:
© Changes are being discussed to further automate the Reference Data interface,
particularly the transmission of Class B data e.g. cash-account mappings and Methods of
Payment. This is being monitored through the Reference Data Checkpoint meeting,
chaired by Product Assurance and attended by Horizon, Pathway and POCL Reference
Data. The current understanding is that this will not be in New Release 2 and is therefore
not currently a risk to the stability of the design during this release.
* Enhanced error handling across the HAPS interface to improve the handling of file
rejections. The current understanding is that this will also not be in New Release 2 and is
therefore not currently a risk to the stability of the design during this release,
28/08/98 Page 9 of 16 Version 2.0 I
Status — FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
.
3
“Horizon Programme ” DIT Closure Report for New Release 2
PinICL 8881 (see Appendix B) has been raised regarding an apparent discrepancy
between Reference Data and Pathway in the way they identify clients and how Pathway
relate this in respect of the HAP interface. This is being monitored by Product Assurance
as noted in the minutes of the I* Reference Data Checkpoint Meeting held on 30* June.
BES Exception processing. This is a known deficiency in the design to mect the agreed
TIP interface specification. This is currently being discussed between the TIP project and
ICL Pathway to establish and agree a solution.
‘The design solution to support discrepancies between cash accounting periods is still
evolving.
‘The design of the directory structure on the Reference Data gateway PC has still not been
resolved. This means that the transfer of data between the Reference Data Project and
Pathway may not have been conducted during DIT2 in exactly the same environment as
that intended for live.
28/08/98
Page 10 of 16 Version 2.0
Status - FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
Horizon Programme : . * ‘DIT Closure Report for New Releas:
5. INCIDENTS
‘The position at the end of DIT2 and prior to entry to MOT and End2End is as follows:
5.1. Incidents raised during DIT 2.
During the course of DIT2 a total of 63 incidents were raised by TIP? and passed to Pathway for
investigation.
These consisted of:
* 14 due to execution or data preparation errors
© 20 diagnosed as “no fault” ’
© — Qattributable to existing/known PinICLs
© 10 duplicates of previously raised incidents
© 2 faults due to problems with the reference data held by TIP
© 8new PinICLs
A break down of the various PinICLs still outstanding at the end of DIT 2 is provided in Appendix B.
‘The outstanding faults, which are not planned to be corrected prior to End2End/MOT, are not an
impediment to starting these test phases*.
2 A handful of incidents were raised by HAPS with no significant error being identified. I
? This recommendation has been reviewed and agreed by the Horizon End2End manager.
28/08/98 Page 11 of 16 Version 2.0 I
: Status — FINAL Ref: PCL/TST/CLR/001/V2_0 - ©
POL00028100
POL00028100
Horizon Programme DIT Closure Report for ‘New Reléase 2 i
6. OBSERVATIONS & PROBLEMS
6.1. Test Preparation
6.1.1, Reference Data Configuration
During the setting up of the DIT 2 test rig at Pathway the reference data baseline (DROP 1), agreed by
all parties, was loaded over the top of the development reference data set. This situation was identified
by Pathway and resolved, causing only a minor delay to the execution of DIT2.
However, the Pathway DIT reference data set was shared with other test and development users and~
changes requested by them were percolated into the DIT 2 testing environment.
This resulted in some testing discrepancies where the Pathway and TIP reference datasets becameout +
of step.
6.1.2. BES Cards
No cards were available to match the test data being used for DIT 2. Consequently all card transactions
were carried out manually and no “swipe” of the cards was completed. Ultimately this resulted in
discrepancies between the actual and expected results, from a TIP perspective, and highlighted a
difference in the interpretation of the script.
6.2. HAPS Client Cards
Early on in the DIT phase, cards were not readily available for all the clients agreed to be used in the
script. This situation was resolved by Pathway for the final run of DIT2.
6.2.1. Errors in Payment Authorizations
During DIT 1, where specific payments were scripted but multiple authorisations existed on the system
for the clients, the unwanted authorisations were stopped so that the encashments could proceed as
planned. This was an awkward practice.
Prior to DIT 2.a decision was taken to construct the payment authorisations within the Pathway test
team. This was accepted at the time as a potentially risky decision. Unfortunately the construction
process was not error free and a number of problems were encountered regarding payment amounts. I
It should be noted that risk associated with the adopted approach was understood and agreed by all
parties prior to the commencement of the final run of DIT2.
6.3. Testing Execution Errors : a
Some testing execution errors were encountered during DIT2. These were partly caused by some of the
test preparation problems described above.
Due to its closely scripted nature, the amount of work that execution errors could generate in End2End
could be unacceptable and should be avoided.
28/08/98 Page 12 of 16 Version 2.0
# Status - FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
aaa
Horizon Programme “DIT Closure Report for New Release 2. hohe
8
¢
=I
7. LESSONS LEARNT
7A. Readiness to start
Due to the pressures on the programme to meet planned dates, the first attempt at DIT 2 proceeded
when the state of the system was not at the appropriate standard. Although the pressures are understood
the time spent on this early attempt was generally accepted to be an inefficient use of available
resources. This situation should be avoided in future.
Every attempt was made, through the close monitoring of the entry criteria, to ensure that the second
attempt did not start prematurely. This approach proved to be successful.
7.2. Date and Data alignment
The effects and the implications of aligning the data and dates between the different interfaces were not
clearly understood from the outsct of DIT and the effects were not always clear.
‘This was due to the split between the bilateral testing in DIT1 and the multilateral testing in DIT2 and
the difference between the narrow and broader views that this required. It was also due to the late
realisation of the emphasis on TIP requirements for DIT2.
Having been through this exercise this should be a cleaner and easier exercise in future. It is also not
thought to be a problem that will be encountered during End2End, as the emphasis during the
preparation for End2End has consistently been on the wider testing requirements of all participating
parties.
73. DIT 2/End2End 1" Pass
Having attempted to use the DIT test as a method of proving/commissioning the End2End test
environment, it appears that this has had two effects. These are:
© Ithas blurred the edges between the technical and functional objectives of the DIT 2
phase. This had an effect on the scope and certainly caused differences of opinion in the
agreement of that scope. One consequence was the introduction of the cash account
integrity as a pre-requisite for DIT2, which in its own right would arguably have been
excluded from DIT but for inclusion of the End2End 1* pass objectives.
© It confused the dependencies between these two tasks. The DIT activity had to be
completed prior to End2End even though the DIT preparation and planning was reliant on
key assumptions for End2End, such as run dates and core test data. In the end some of
these dependencies disappeared c.g. the approach to the provision of reference data
changed during course of DIT, effectively removing some of the dependency on
reference data being synchronised between these two test phases.
‘The benefits of attempting to combine two test phases with separate objectives must be clearly
balanced against the costs and risks associated with doing so. Where possible the savings from any
overlapping activity/objectives should be recognised by perhaps shortening the two test phases - whilst
retaining their independence, rather than combing them.
7A, Pre-requisite of an integrated environment
It was not obvious to all concerned until well into the testing that it would not be possible to transfer all
types of data across the TIP interface until the fully integrated version of the system was available.
Because of the nature and size of future release this is unlikely to occur in the future but should be bom
in mind when assessing the dependencies of the interface testing with other test phases.
15. Reference Data Integrity
When the integrity of reference data between TIP, Pathway and Reference Data is required, it is
essential that the reference data is secure in each of the,three areas from other test phases. This was not
the case for DIT 2 and TIP and Pathway became out of step.
28/08/98 Page 13 of 16 Version 2.0
Status — FINAL Ref: PCLTST/CLR/001/V2_0
POL00028100
POL00028100
Horizon Programme DIT Closure Report for New Release 2 >
pS
APPENDIX A— INTERFACE SPECIFICATION VERSIONS.
Ref. Title; Reference Data System Application Interface Spec Reference Data to Pathway
Data‘ Ref: RDP/AIS/001
Version: 3.2
CAPS Title: CAPS to PAS/CMS Data Interface and Validation Rules (R3)
Ref: hifd ifd 0006.04
Version: 6.04
HAPS Title: Pathway to HAPS Interface Specification
Ref: AP/IFS/001
Version: 2.0
OBCS Title: OBCS Client Interface Specification
Ref: OBCSINT.001
Version: 1.0
TIPS Title: Pathway to TIP application interface spec
Ref: PCSTIPIS.doc
Version: 5.1a
+ This was enhanced and version 3.3 was intercepted at the start of DIT 2
* This was moved to version 5.2 by the agreement of both TIP and Pathway during DIT. Version 5.3 is
in existence but is yet to be agreed.
28/08/98 Page 14 of 16 Version 2.0
Status - FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
. 14 Horizon Programme : . DIT Closure Report for New Release 2:
ae
APPENDIX B— OUTSTANDING PinICLs
PinICLs planned to be re-tested prior to End2End/MOT
es pS Bi
There are no additional al details for events: Suis 916 and 919
8879 Cash Account week number is missing from events: 915, 916, 919
9933 The refund flag should be null for all events.
12012 Number of Organisational units for BAT record dated 27/03 within BARSF
dated 17/03. Value received 30, value expected 4.
12408 Failure to populate all encashment tables
12443 APS recovery transaction showing method of payment as 1 (Cash) rather than 2
(Cheque) D
12455 Tender for linked reversal different from that of initial transaction
12459 — Incorrect details in non-automated PO help desk BES encashment.
12488 — BES Help Desk transaction included in BES Transaction Total on the TIP BA 1
Reconciliation file. It should also have been included in field ‘Total Value of
POCL Exceptions’, but was not.
8898 — Wrong additional data for reversal
10473 “Agency Code" for all received BES encashments = null I.e. spaces. This is a
mandatory field when "BES Status" is 1 (Complete)
11429 Discrepancy values as stock items
12032 The STX records in the electronic cash account include duplicate entries and
entries for non-stock items
12484 Additional details for existing reversal incorrect.
12485 Wrong Item Id for OBCS milk tokens on OTX record
12791 Cash Account line for BES milk tokens not populated
12891 — Adjust stock on incorrectly re-valued item
Notes
1. Possible hangout.
[—] 28/08/98 Page 15 of 16 Version 2.0
Status — FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
i
ve Horizon Programme
Others
ICL LDH PUORNS RRS AEES os
“QR Entry method on OBCS files inaccurate for ‘eneashments i in fcian office with
ISDN link down.
8881 Account Id and Client Code. Different references used by HAPS and TIP. 2,4
9961 — Unexpected OTX records received with item id; 932 (log on failed password) 1
and 938 (Change address (BES)
12717 Query conceming the definition of the line ‘Number of Benefit it Encashments', 1
line 4081, in the Cash Account
13035 Invalid or unreadable OBCS encashments creating a spurious OBCS event. 1
12690 - EOD Markers including transaction date not trading date 2
12817 “Catch-up” cash account transactions being sent for 2-3 week cash-accounts 2
9901 — Stock Unit Balance completion event (911) includes period dates which should 3
be null for events.
9919 Spurious extra transactions with cash zero value 3
Notes
No testing date currently known and therefore a possible “hang-out” for End2End/MOT
2. Compliant with AIS but possible design problem.
3. Considered low priority and no re-test date announced.
4, This is a design issue surrounding the differences between the various data used by TIP and HAPS
to identify clients. The interfaces met the agreed designs but it looks likely that the design will
encounter problems during End2End. This PinICL is against the HAPS interface specification.
PinICLs awaiting action by POCL
10100. APS ee transaction mode 14.
11488 — Method of data capture 5
12644 — Housekeeping transaction mode 15 2
Notes
I. Non DIT. Thought to be cleared but awaiting evidence,
2. Confirmation required that TIP accept agreed reference data values.
28/08/98 Page 16 of 16 Version 2.0
Status - FINAL Ref: PCL/TST/CLR/001/V2_0
No
POL00028100
POL00028100
New Release 2
Author: Bruce Talmage Approved: Organisation ; Signature: Date:
Signature: i G RO : Simon Palladino ICL Pathway _GROI ale s¥
Date: 28/08/98 a
Peter Jones TR one
Authorised: I Simon Rilot
~ Les Hodson CAPS —
Signature:
Andrew Fretter RDP
Date: 28/08/98
Linda Vel HAPS
John Lees ESNS
Document Reference: PCL/TST/CLR/OOI/V2_0
Document Version: 2.0
Document Status: FINAL
2808/98 ee Page 1 of 16 ote, Version 2.0
i . Status - FINAL Ref PCL/TST/CLR/OOL/V2_0
* Horizon Programme
seean tha arn eg ee a> te). ar?
eTeaszeTe* *-Q191 357 652938 2° URL
DIT Closure Report for Now Release 2 AR
(om x Fp OK Aenweld te
TITLE: DIT CLOSURE REPORT
POL00028100
POL00028100
TITLE: DIT CLOSURE’
Approved: Organisation Signature: Date:
tamnon eainding . ICL Pathway
‘e]3/ "2
Veter Jones: ‘rir
Les Efodson CAPS on
andrew Fretter RDP oe
Saude Vet HAPS, ceaseenntsssecenseense — eeeertanene
sulin Lees FESNS —essssaseseasessnsnnins 0 sesnetnnane
“Podiiment Reference: *CLIPST/CLR/OOL/V2_0
_ Décument Version: .
nient Status:
POL00028100
POL00028100
Horizon Programme
TITLE: DIT CLOSURE REPORT
New Release 2
Author: Bruce Talmage Approved: Organisation Signature: Date:
Signature: Simon Palladino ICL Pathway aoe : 0
Date: ‘28/08/98
Peter Jones TR
Authorised: Simon Rilot
ro Les Hodson CAPS
Signature: I
Andrew Fretter RDP ee
Date: - 28/08/98
Linda Vel . HAPS eccameacevunnscnonere ——_avesenennnn
John Lees ESNS
Document Reference: PCL/TST/CLR/001/V2_0
Document Version: 2.0
Document Statits: FINAL
1
Hi
1
28/08/98 Page 1 of 16 Version 2.0
Stans - FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
New Release 2
Author: Bruce Talmage Approved: Organisation Signature: Date:
Signature: Simon Palladino ICL Pathway
Date:
Peter Jones TIP ssenssnnseecncennns — seeeennnaes
Authorised:
Les Hodson CAPS
Signature:
Andrew Fretter RDP
Date: 28/08/98
Linda Vel HAPS
John Lees ESNS ——sesssccessnnssecenne sasssenenee
Document Reference: PCL/TST/CLR/001/V2_0
Document Version: 2.0
Document Status: FINAL
eS 28/08/98 * Page I of 16 Version 2.0
Status — FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028100
POL00028100
eport for New Release 2
TITLE: DIT CLOSURE REPORT
New Release 2
Author: Bruce Talmage Approved:
Signature: G RO Simon Palladino
Date: ‘280898
Peter Jones
Authorised: — Simon Rilot
Les Hodson
Signature:
Andrew Fretter
Date: 28/08/98
Linda Vel
John Lees
Organisation Signature:
ICL Pathway
TR
CAPS
RDP
HAPS
ESNS
Document Reference: PCL/TST/CLR/001/V2_0
Document Version: 2.0
Document Status: FINAL
28/08/98 Page 1 of 16 Version 2.0
Status — FINAL
“Ref: PCLITST/CLR/O01/V2_0
Date:
POL00028100
POL00028100
Po SNotean”
DIT Closure Report for New Release 2
TITLE: DIT CLOSURE REPORT
New Release 2
Author: Bruce Talmage Approved: Organisation Signature: “”, Date:
Signature: I G RO Simon Palladino TCL Pathway cssssssssesssssccsssne seseennnnne
Date: 28/08/98
Peter Jones TIP asaeesecccsennnnnnens tnzsnnnanee
Authorised: Simon Rilot
cc , Les Hodson CAPS oe
Signature: G RO
Licemnnnnemnnencneenned Andrew Fretter RDP —_______cavssnsnsssnnnesersns — sttsneenvee
Date: 28/08/98
Linda Vel HAPS
I
I
I John Lees ESNS
Document Reference: PCL/TST/CLR/001/V2_0
I Document Version: 2.0
Document Status: FINAL
28/08/98 Page 1 of 16 Version 2.0
Status — FINAL Ref: PCL/TST/CLR/001/V2_0
POL00028
POL00028100
100
NEW RELEASE 2 —- HIGH LEVEL PLAN
(oc Ref: PM/PLA/031)
VERSION 5.0
BASELINE DATE: 11°" SEPTEMBER 1998
RELEASE NOTES: for General Distribution.
All the dates contained within this plan (ref: PM/PLA/031) are based on a Child Benefit only
Model Office, Live Trial and start of National Roll Out. No information on the Multi-
Benefit activities have been included, as this information is currently held by the Horizon
team.
The start date and duration of the Live Trial has yet to be agreed, as such version 5.0 of the
Release 2 plan maintains the 11 wk duration of version 4.0 but starting on the 1 February
1999, rather than. 2st January 1999.
No reference has been made to New Release2+.
This version of the New Release2 High Level Plan takes into consideration the following
changes:
¢ Approved modifications to the Model Office Waterfall, to include Model Office
Rehearsal #3 and better use of the in-built contingency.
¢ _ Re-alignment of the remaining System Test Main Passes to take account of the final
functional drop of BPS Reconciliation and PinICL, fixes.
¢ Re-alignment of System Test Final Passes to meet test rig availability.
Re work of other areas of the testing plan to come into line with System Test and Model
Office. .
Replan work on Technical / Performance and Security testing.
Inclusion of activities to represent the EPOSS Usability Study
Additional activities for Acceptance.(System Test Final Passes)
Dates for Live Trial, post 1° February 1999, still awaiting agreement.
Inclusion of Milestones for the Release Authorisation Process from a presentation given
at last weeks Check Point Meeting. The approach is still to be ratified with Steve
Muchow and amendments will be made as appropriate.
© The Customer Education plan is still “No Forecast” awaiting the resolution of the Live
Trial Plan.
© Additional activities for Customer Service and Reference Data.
Andy Morley
(ICL Pathway Programme Plan Co - Ordinator)
10" September 1998
AANR2_HLP.DOC ’
COMMERCIAL IN CONFIDENCE
POL00028100
POL00028100
“
Release 2 High Level Plan - el1 Page: 10 4 2
Version 5.0 Print Date: 14SEP98
‘pti ime io
Act ID Description v5.0 Start II v5.0 Comp laa ey eR SCT hay pene
2 Develpmert ‘0108097
Prick Fes oroece7
Mair. rp 0106097
a synem Tesing OWAYo8
428001 POSS - System Tost Mal Ps 12498
asx {8PS - Syston Tos Man Pa souayon
sor TPS. Syatom Tost Man Pass awayos
«25000 1 - System Test Man Pass owayos
Ue Retorence Data drop rom POCL sun
425000 OMG. System Tost Man Pass vena
«20003 Traning - System Test Man Pass zoayon
420000 ‘Aust Test Main Pass 100cT98
25009 ‘System Tost Fra Pase voooT9s NOW rf Test Fn Fh
a2s0s1 ‘APS. Syatom Tost Final Pass vwooTos 2s0cT98
425088 POSS - System Tost Fina Pans 90croe eaniovee
428085 OMG - System Test Foal Pass cenoves s9novee
2087 {BPS - System Test Final Pass reoTve zenovee
«20089 (0008 Syston Tost Fina Pass sooo 1s0cT98
25081 ‘PS - System Tot Fal Pass oanoven 21Novo8
425003 Mis - Syston Test Fal Pass 100799 nove
425008 Trang - System Tet Fea Pass 900r0e canoves
420087 ‘Aust Tost Fra Pass onoves z2Nove8
cssae APS Pre Producten Testing osocrse 12sAN00 10 Prosfoucton Testing
0 BIT Testing ‘ouAvoe 180808
«amo SLT Main Pass oman 2nocT98
ens [LT Fina Pass (net Migration) cenovo8 z2Novee
«2088 System Testing Regression counyon zanovee
a2res7 BLT Migration Testing 22AUG96 O1NOVE8- }
427080 Rei 2/ BIT / YK 17AUG96- 180EC98 \ 7
‘ezro70 End 0 End Toring voavaoe 9098 Endo End Toh
sams nd to End Testing Man voauaoa canovee
427076 End to End Testing Final O9NOVES 180EC98 ¥
2000 Technical & Seay Testing Peromance 7200 R08 Nove rca 8 Secure Texing -Pertorhance
a pean ind Rieti) meee noes mas ee
“25701 Technical 8 Securty Testing - Securty nove? Nove Tofnca & Secure] Testing - Secu
0% Securty - Planning & Sorting 2anover I 22098 I
480000 Securty- 18 Phase Test zauanse I aus
452800 Seouty- 2nd Phase Test oxavaos PsP E I
rae fant hee I I
Baseline Date: 11Sep98 Author : Andy Morley File Names :
Doc. Ref.; I PM\PLA\031 GsPians\REPORTS\Generah2 High level Plan v5 adsize.at
(:Phans\Overal Plaa\Rol 2. 50ND
Version : 5.0
the
=
Release 2 Hich Level Plan -
Version 5.0
Page: 2
14SEP98
Print Date:
POL00028100
POL00028100
Description
v5.0 Start
1908
EPTEMBER
I_avousr
Tacha SacryTortng Tech iregy Newark
Validation rt
Tech iniagny & Networking - Test
Tech Integy & Networking - Adstionl Test
‘C2APROB
2nP ROB
I oecemocn
brnicl& Secu] Testing - Tech fwgry / Netwok Vatdaton
wanuany I FEBRUARY I _MAROH
APA
Baseline Date: 11Sep98
Doc. Ref.
Version
Andy Morley
PM\PLA\O31
5.0
491900 ‘Tech inaprty & Netwonting - Regression 1900798 zNovee
«20009 Technica &Secuty Testing Syste Management coAPR98 nove Peal & Secur] Tesing: Systefa Manager
«5750 Systems Management: Test 8 Re-Tost caAP R08 SEP 8
«20450 Syms Management Regression 238700 zenovee I
2 Fewase 2PPO Prodvcion o1APR08 V7OECOR BF Peieabe 2 PPO Procuchen
s2400 Retease 2 PPO vO Resouton of aves O1APRO® eocre . I
sauna Release 2 PPOs v0.5 Rework/ Review and ase 900T98 1106008 4 3 I
suas fadease 2 PPO ned atv 1.0 swocooe AY a 4
By Feteate 2 Counter Procedure evelpment eatery 20NOVIS II Retase 2 Courter Procdur development i
Rotese 2 Counter Procedures v 80 Rework & Ravina 2aavoos 2sEPo8
our Procedure anmentarais or MOT fo WO tied ae r
pe Boag 2 Cour: Procntres v6.0 Tot 8 Rework oui ‘econ y
rat Horton User Guides to HO Putas swocTs
Es Trang Oevetaoment er) a = Trang Dwodprant oe I
s2ease Tearing Comterts Sin Os zaunoe osnoves
J I seer Release 2 Workbook & ORG (POCL) Signott s1Aua98 SONOvES 4
s24289 8A Trang / Voting 14a ones 4
OSS Usabity Study a9 ones epossfosabay Sy
POSS Usabity Suc) -mplemertaion s1Ui08 cwocTos
POSS Usabny Study - Sudy osocTes s000T98
POSS Uasoity Study -Evauaton osocT9s oanoves
rag mee ee oma
‘covarateAccoprarce Test Sowct core 008 s0seP a8
POCk Sign-On at Test Spector Tats aoscree I
POC Si9n-0H remainder of Test Spece I s00cTe8
100011 et 2 Acceptance - Technical & Secity I 2s96h8 1806008
om fel 2Accopanc Tn Syoem Test FsiPanss I roots zenowss
et 2Accaptance Tals - BIT Fra Pass I cenoves znoves I
100018 Fel 2 Accapance Ravers zoos seAPROD
so I _rat2henpne ge Th I toro I seer
30 Mosel Otice
Fa coe Otce Preparation ] oasuNo8 180038
czas Soate Data Genre Preparation i ssn r0cT9e
pareee I axa corse are
«20010 NUMA.G vain to Operatons 1 1o00TVe
e23701 peratona Procmduie Reraaral l s98 voavase
File Names :
{0-PiansiREPORTS\Gonerah2 High level Pan v5 asize wt
Pans Overall Plana\Rel 21 50 arp
a)
POL00028100
___POL00028100
Release 2 High Level Plan - el Page: 3
Version 5.0 Print Date: 14SEP98
Act ID Description v5.0 Start I v5.0 Comp hie! 1
JUNE ay waoust I beerempen I ocrosen I novewscn I pecewecn I sanuany I resauany I Mani PAR May.
COperatenal Recovery Procasurws Phase 1 raAuaee
Operatonal Recovery Procasuces Phe 2 I 180EC98 ¥
Provide MORE 2 Training Systems
Provide MORE Traning Syston
Provide MOT Training Systems
exon MOT Reeds Review reocree
ezome Cprasone!Resdeas Revi moves e
penity oe te fg rene ponte POL vraase g I
Nas Fw Mosel Once Tesirg Sched proviso Rebs. lp
Support or JSA.CAPS Model tice casune sianse II Gamma i
ayANoO Model Once
esting
Model Otte Testing
Mode! Oca Rehearsal - Wit oxmvass o7avase
Model ice Rehearsal #1 roauaes 2rAuG%8
(CAPS join Mode! tice 14SeP98
azr08 Model Oce Rebearsl 2 - Wii ASE 98 1eSEP 98
42700 Model rice Rehearsal #2 2186P98 180oT98
aar08 Mode! Oton Rebeara #9 Wii vwocr9s 23ccT08
sare Mode! once Reta #3 zeoctes 2onovee
sar Model te Testis aavoves zmovee
aero Mode! ote Tost sovoves vwoecoo
azres Coningeney 2106098 casano
* Dre Tae! 7 arn
824303 Ye. NR2 upgrades UA Events Prep. 17SEP98 OeNOveS \
s2007 Le Tha User Avorn Evan Prep ascct98 senove
200 ang Coir Mgtento10 Hr oo awe —
cy ‘Data Centre Clear Down and Migration S0JAN90 JANDD a te
624860 Link Established to TIP O1FERO9 4
200 oot Ado! 100 ve Tal Pot Cees ovrcooo ‘9000
ev plone ata Cate ‘Feo vare000
EJ Uve Trial O1FEB99 16APROO i
Fae Astoreaton Prone raocres oem Fear hfroreaton Pre
cxsme Release Aaoreton Board (RAB) review a0Kco8
czars Pre-Release Aatoraton Board (RAB) review uocooe
A Progress Meeting #1 s20cTes
A Progress Mewting #2 omioves 2
A. Pr Meaing eroeces cxoecme
A Mating 21oco% cece II Gn
9! Roll Out Preparat a _.19APR00 I DTA 2 SNR SATE ET a ed
a = aun er ol
- el
Baseline Date: 11Sep98 Author: Andy Morley File Names :
Doc. Ref.; PM\PLA\031 G:ans\REPORTS.GereratR2 High oa Plan v5 waza
Version: _5.0 G:vnsiOvra PanaiRot 2.1 v0.9
Release 2 Hiah Level Plan -
el 1
Page:
POL00028100
POL00028100
Version 5.0 Print Date: 44SEP98
ActID) Description vgi0 Stalt]IVB.0 Comp seas 21 egte Tara I emia Ucar ct cael ua eel (eter peg a
per, Ti esac on Gri aa roo rar
peas el Proyanme pas 8G 8 Masa and aa ore ce) See ae -
sas Seer an Meiteral Apron ot Prise ¥
poanes Asvecting Maria Paring Stars 9
poco ton Rl Ou haveing Sane I g
a ‘eleertavon eres I om ee ae
82020 ‘Commence Issue of RGM Letters g
s2.0465 Commence MIB Everts z
s200 commence Ste Suveys
s2007 Commence Sie Re Suveys
sous National Rot Ou UA Evans Pp sre sa}
22000 Commence Ste Preparations
s20%0 Commence User Awareness e I
Deesion on Model Otew Coningeney y I
‘Commence build of National Rot Out Counters I
52051 Commence Trlnng g
52055 ‘Stat National RotOut 19APROO e
“ ‘System Management oun I vn0coo8 I yn Management
czas Buainess Contnuty Maps & Gutes sewunoa 1906008 ‘ .
eae Pees iter Meregenon Povene/ jnaase iced I
Fen Over tangent rc ene tes I i » I
outs? purrccupanyprtuce Bnew Cnty Av008 oscPo8 I y F
6 Cperatona Suppo MAYO or) ‘Operbional Suppo
ease 1st, 2nd, 364th Line Suppor prapartin for Retase 2 ormayos 110098 i
ezao upper Conc in place 1908008
° Retornce Osta Orman corey Retwrance
sere ve Reternce Oat op rom POCL za.0N00
sev987 Review Une Reeronce Date dap rom POCL. zaNe8
eau Aeterence Oat Live Piet. ormayoa 190098
ounce Live Re, Data Joint Processes & Procedures ava o7seP08 a19eP90
e2u0es Lve Rel, Data - Post nplementaton Review me0cTes 1aNove
Proparton of Live Ret, Data Envonment seunee I syAuaoe
Business User Vertcation oxseres I senoves
Busnes User Vertaton + Change Cont swnovee ceuaNso
Ey Rewase Waragement 1806098 17DECSS TPR eieafe Managemen
ewe esease Maragersentsutegy proved 1098 e I
2 Sennce Management 1806698 1706098 oT nde Management
eas Seren Manure Process aad wn POCLBN ica ¥
—
II Baseline Date: 11Sep98 Author : Andy Morley File Names :
Doc. Ref.: PM\PLA\031 GPlans\REPORTS General R2 High level Plan v5 adsize.avt
anion ete 6.0 G:Plans\Overal Planet 21 vS0ap
POL00028100
POL00028100
17 SEP °98 14:03 FROM
TO $7763955, P.@2/11
Memorandum
To: John Meagher - Horizon Acceptance From: Mary Reade
Manager
Date: 16/8/98
Subject: [ Briefing Notes for Dave Miller }
Acceptance Specifications
Below is a copy of the summary progress report issued to Bob Burkin for Dave
Miller.
Acceptance Specification Sign Off Notes RAG
Status
1 APSIHAPS Imminent Spec ready for approval - subject to contractual GREEN
completeness check
2 Avdit 29-Sep Review meeting scheduled for 22/9 GREEN
3 BES 30-Sep PAS-BES boundary issue yet to be resolved GREEN
(No. 67 in issues database)
4 DSS (CAPS) interface 48-Sep No known issues GREEN
5 CMS 30-Sep No known issues GREEN
6 End to End Acceptance 16-Oct Tobe confirmed GREEN
7 ~~ +EPOSS 16-Oct 16 Octis aim date for approval. Feasibility tobe = AMBER
confirmed
8 Help Desk 04-Nov Pathway due to release spec for approval on RED
28th October
9 implementation-A User Training & Imminent Spec ready for approval - subject to contractual © GREEN
Decumentation completeness check
10 implementation - 8 Customer 09-Oct Change request and CCN peperwork to be GREEN
Education raised
11 Implementation - C Services Imminent Spec ready for approval - subject to contractual © GREEN
completeness check
12 Implementation - D Rollout 09-Oct To be confirmed when outcome of 11 Sept GREEN
meeting is known
1300 MIS Imminent Spec ready for approval - subject to contrectual © GREEN
completeness check
14“ OBCS Imminent Spec ready for approval - subject to contractual © GREEN
completeness check
15 Operational Trial (Schedule C3) 16-Oct No known issues GREEN
16 PAS 30-Sep _PAS-BES boundary issue yet to be resolved GREEN
(No. 67 in issues database)
17 POCL Infrastructure 30-Sep To be confirmed GREEN
48 Policies & Standards 30-Sep To be confirmed GREEN
19 Reconciliation Oct/Nov Pathway not due to release next issue until end RED
‘Sept. (Testing by doc review)
20 Reference Data 146-Oct To be confirmed GREEN
21 Securty 30-Sep Tobe confirmed GREEN
22 ~— Service Levels 16-Oct Tobe confirmed GREEN
23° TIP interface 16-Oct Outstanding issue regarding comprehensiveness GREEN
of spec to be rescived
80916TIM.DOC Pagel
1B post: Third Floor, Terminal House, $2 Grosvenor Gardens.
‘phone I B fax:I
17/09 ‘98 14:40 TX/RX NO. 1302 P02
PRAT? aoe
Dre Levers
NeaStarnte
Bh. I Re,
POL00028100
POL00028100
a \OUTINUS To TAKE Comme op
VPECK
= ie
Oy ruts via Re Rizen fe
i Ee mans
ve oes
NOKTINEE Te MAP ANTiTiers
Stem os TP
\
\ ‘ oe -
4' AeD Ren dw” Teh Sue SMD
Gr! CAN SAAN ee tom eo uae
Cos > Sg ones, ‘ LAD oe
POL00028100
— POL00028100
Conte AcTyac ares
PREPARATION STAGE
EF ecutied STAGE
Deeision
Manaceneat
Drpesret PAPER 1 S0ED
Tusa - Wicd LEVER AVAILAELO — DETALED AOBITED
Wesevac €, TEAM STRENGTHENED I
RELENNE MOAAGERS FUSuM RElnc NET OP
POL00028100
POL00028100
1? SEP °98 18:23 FROM BA-POCL PDA FELTHAM
Paul Wootton
Room 5023
—___.
banking &
accountancy branch
—_——
Corporate Banking and Methods of Payment Group
P.@2718
To: John Meagher From: Paul Wootton
Horizon COBAP
Date: 14 September 1998
cc: BA Acceptance WG
Ken Davenport
Issue: Acceptance Issues
Action: To confirm agreement and update on progress
Timing: By cop Wednesday 16 September 1998 to enable briefing to Peter Crahan
prior to CAPS and Card Programme Board
2: When we met on 4 September, we alluded to the Acceptance issues BA identified to you in early August
1998, and discussed the Acceptance implications of the replan.
2. This minute seeks to:
2.1 Clarify BA’s approach to replan Stage 1 (Acceptance v Release Authorisation)
2.2 Wdentify additional issues arising from the replan and seek acknowledgement that you accept
these as issues to be resolved.
23 Review the identified issues, suggest methods of approaching some of the outstanding Issues,
and to seek an Horizon progress report
24 Raise additional issues which need to be addressed., seek confirmation that they are accepted,
and obtain information on how Horizon is dealing (will deal) with them.
Replan - Acceptance v Release Authorisation
2. In discussing the replan, I explained to you on 4 September the then BA perspective that Stage 1 appeared
to be @ Release Authorisation rather than @ contractual Acceptance. I have since obtained a copy of the
feplan documents and discussed within BA and with Pat Kelsey. I now concur with your position that
Stage 1 constitutes part of the Acceptance process, as I explained in the phone message I left with Rod
Stocker on Monday last.
Replan Acceptance Issues
3. Having had the opportunity to look at the replan proposals in more detail, several issues emerge, which
have been aired at the BA Acceptance Working Group:
17/09 '98 10:14 TX/RX NO. 1297
P02
POL00028100
POL00028100 _
17 SEP °98 10:23 FROM BA-POCL PDA FELTHAM P.@3/18
34 We need an overall integrated plan for the whole of the Acceptance process. This was alluded to
at our meeting, and we discussed in more detail with Ian Kerr later. (1 have also written to Rod
Stocker to suggest that his recent paper on Release Authorisation should specifically refer 10 the
Contractual Acceptance process, and that Release plans should specifically acknowledge
Acceptance work steps - Rod tells me he has no problem with this)
52 The present Acceptance Specifications are NR2 specific but do not distinguish between NR2
Stage 1 and NR2 Stage 2.
3.3. We are not aware of a definition of a Proof of Concept for Mobile Configuration, (required for
Stage 1 Acceptance). If it does not exist, it will need to be developed and, in any event, brokered
between the parties. It is not clear where the responsibility lies for defming it, nor how it will be
factored in.
34 Criteria for success in nuulti-benefit testing (Required for Stage 1 Acceptance) needs to be
defined and brokered between the parties. It is not clear where the responsibility lies for defining
them, nor how they will be factored into the Acceptance process.
35 Criteria for adequate progress in NR2+ development (Required for Stage 1 Acceptance) nced to
be defined and brokered between the parties. It is not clear where the responsibility lies for
defining it, nor how they will be factored into the Acceptance process,, [Note that to move this
along, I propose that the Criteria will be that the Authorities have seen and agreed:
1. NR2+ SADD
2.NR2+ RCD
3. NR2+ Acceptance Specification,
and
4, Logical design is complete
S. Code is 100 % complete but may not be tested.
Tam seeking BA approval to this line)
(Note: See also para 9 et seq below]
36 Calera for NR2+ Proof of Concept (Required for Stage 2 Acceptance if NR2+ and NR2 Stage 2
do not coincide) needs to be defined and brokered between the parties. It is not clear where the
responsibility lies for defining them, nor how they will be factored into the Acceptance process.
ic have suggested, (subject to internal BA agreement, which should be forthcoming by Monday
next) that our opening position should be that we must have seen and agreed:
1.NR2+SADD
2. NR2+ RCD
3. NR2+ Acceptance Specification,
and,
4. Pathway can demonstrate a version with no major Technical Test acceptance
incidents for which they cannot produce a credible plan to fix].
37 The Implementation Acceptance Specs need to be reviewed in the light of the replan.
(Note: a quick look shows that:
Implementation A
17/09 "98 10:14 TX/RX NO. 1297 P03
POL00028100
POL00028100 _
17 SEP *98 10:24 FROM BA-POCL PDA FELTHAM
4, Please confirm that you acknowledge these as issucs which need to be addressed., and that their resolution
is being built into your plans.
Review of Acceptance Issues
3. Referring to the list of issues I provided to you in early August 1998, the previously identified issues are:
5.1
P.84718
No date or release plan specific Requirements or Test conditions except Requirement
913, criterion 16 Test conditions look to be Release plan specific and may need
changing
Implementation B
No date or release plan specific requirements or Test Conditions except!Requirement
916 criterion 1 Points to a specific document (Marketing and Education Plan) which
may need updating
Implementation C
No date or release plan specific requirements or Test Conditions
Implementation D
No date or release plan specific requirements or Test Conditions except that many of
1 would be grateful if you would confirm that the above reflects your understanding, and that
work is in hand to update the subordinate documents to reflect the replan working assumptions
Revised drafts would be appreciated in due course.
No overall plan for handling acceptance
We alluded to this issue when we met on 4 September 1998, and you advised me that a draft
narrative document and programme bar chart were imminent. I have subsequently received from
Tain Kerr (end was able to access on Friday) an early draft of a document “Horizon Acceptance
Plan” draft 0.2) on which I have sent early comments separately. Thanks, I have issued the
document to the BA Acceptance Working Group members to obtain a wider view, and hope to
let Inin have final comments by 21 September 1998,
‘There are some issues which need to addressed urgently, which are:
1. The plan needs to fully match the replan working assumptions.
2 ‘The plan needs to fully cover the processes and activities necessary to recover from the
lateness of the Acceptance Specs.
= 5 The plans need expanding to fully take into account that LT DO's, various areas of
CAPS, BA Audit, BA PAAG, BA Security, in addition to LT PO Outlets will need to
be fully aware of when, how and where to report an incident. They will need to be
identified, educated, trained and the appropriate processes put in place.
4. ‘The incident management processes need to be developed to fully cover:
7 An urgent business assessment of each incident, leading to rapid decisions on
the scale of any problem and urgent decisions on workarounds where
appropriate - the imperative is kecp the business going.
17/09 ‘98 10:14 TX/RX NO. 1297 PO4
POL00028100
POL00028100
—
17 SEP °98 18:25 FROM BA-POCL PDA FELTHAM P.a5718
5 feeding incident reports to other systems where appropriate
ag identifying inadequacies in the contracted obligations and decisions on
remedies.
5. ‘The processes to provide assurance that the Acceptance Specifications fully meet
Contracted obligations, arc fully reflected in HLTPs and Scripts need beefing. The
description of HLTPs within the paper is a litle rosier than I have previously been led
to believe, and possibly misleadingly so.
6. There are other big holes which are identified in Drafting Notes which need to be filled
quickly.
7. We still (desperately) await a programme timetable for acceptance and a comprehensive
list of products, product descriptions and relationships.
Please confirm that you have these issues in hand, and advise dates.
52 Relations with Pathway need to be clarified and visible
We generally agreed when we met that this needed to be addressed, and you suggested that this
may be satisfied in part by my inclusion in a tri-partite Acceptance Manager’s forum. You were
going to let me have proposed ToR.
I note from the Horizon Acceptance Plan para $ that three forums are being proposed, the
Incident Review Panel, the Acceptance Management Forum and the Joint Acceptance Board. 1
Presume that it is the formightly Acceptance Management Forum which you referred to at our
meeting. I would be grateful if you would set that up immediately and let me have dates. It is
possible that Peter Crahan will also wish to attend from time to time. Are you able to offer draft
ToR yet ?
In addition, as I mentioned to you when we met in August, I need to see minutes of all mectings
with Pathway relating to acceptance, but I do not appear to be getting them yet. Could you
arrange for me to be notified of all meetings with Pathway which address Acceptance issues and
for me to be copied into agendas and the minutes.
Please confirm agreement and dates
53 Pathway Acceptance Test proposals and plans
Thave not yet seen Pathway’s detailed plans, Please update me.
54 No agreed meaningful or doable timetable for clearing Acceptance Specifications
T know that Iain was working on a MS Project Timetable. He promised to let me have a copy
when it was sufficiently advanced. But I have not yet seen it. I would be grateful if you would let
me have a copy urgently.
In the meantime, I shall be putting together our thoughts over the next day or so, and will copy
you in to the initial draft.
55 _ Pathway’s apparent reluctance to Accept any Acceptance Testing within the Model Office
Stage
Picase update on progress in clearing with ICL Pathway.
3.6 Operational Trial Entry and Exit Criteria (for phases)
17/09 ‘98 10:14 TX/RX NO. 1297 POS
POL00028100
POL00028100
P.@5/18
1? SEP °98 18:27 FROM BA-POCL PDA FELTHAM
* feeding incident reports to other systems where appropriate
. identifying inadequacies in the contracted obligations and decisions on
remedies.
5. ‘The processes to provide assurance that the Acceptance Specifications fully meet
contracted obligations, are fully reflected in HLTPs and Scripts need beefing. The
description of HLTPs within the paper is a little rosier than I have previously been led
to believe, and possibly misleadingly so.
6 ‘There are other big holes which are identified in Drafting Notes which need to be filled
quickly.
x We still (desperately) await a programme timetable for acceptance and a comprehensive
list of products, product descriptions and relationships.
Please confirm that you have these issues in hand, and advise dates.
52 Relations with Pathway need to be clarified and visible
We generally agreed when we met that this needed tn he addressed, and yon enggested that this
may be satisfied in part by my inclusion in a tri-partite Acceptance Manager's forum, You were
going to let me have proposed ToR.
I note from the Horizon Acceptance Plan para S that thrcc forums are being proposed, the
Incident Review Panel, the Acceptance Management Forum and the Joint Acceptance Board. i
Presume that it is the formightly Acceptance Management Forum which you referred to at our
meeting. I would be grateful if you would set that up immediately and let me have dates. It is
possible that Peter Crahan will also wish to attend from time to time. Are you able to offer draft
ToR yet?
In addition, as I mentioned to you when we met in August, I need to see minutes of all mectings
with Pathway relating to acceptance, but I do not appear to be getting them yet. Could you
arrange for me to be notified of all meetings with Pathway which address Acceptance issues and
for me to be copied into agendas and the mimutes.
Please confirm agreement and dates
53 Pathway Acceptance Test proposals and plans
Thave not yet seen Pathway’s detailed plans, Please update me.
54 No agreed meaningful or doable timetable for clearing Acceptance Specifications
T know that Iain was working on a MS Project Timetable. He promised to let me have a copy
when it was sufficiently advanced, But I have not yet seen it. I would be grateful if you would let
me have @ copy urgently.
In the meantime, I shall be putting together our thoughts over the next day or so, and will copy
you in to the initial draft.
55 Pathway’s apparent reluctance to Accept any Acceptance Testing within the Mode! Office
Stage
Please update on progress in clearing with ICL Pathway.
5.6 Operational Trial Entry and Exit Criteria (for phases)
17/09 ‘98 10:19 TX/RX NO. 1298 POL
POL00028100
POL00028100
17 SEP °98 18:28 FROM BA-POCL PDA FELTHAM P.@6/18
Please update on progress. (Note that to help you move this along, we shall be considering
Separately what BA would like to see in place, and I will copy you in).
5.7 _ Pathway Configuration management
Please update on progress, In particular, we need to be assured that there is central version
Control, that testing will confirm that when one element changes, all linked elements continue to
work, and to see the processes which will enable this to be managed.
We also need to know what action Horizon propose to take to ensure that it is properly managed.
5.8 NR2+ PoC undefined
Please sce para 3.6 above, where, to move this issuc forward, I have set out BA’s opening
Proposals. Confirmation that you can proceed with Pathway on that basis would be appreciated.
59 Uncertainty of Acceptance Criteria Sourcing & of currency of document set
‘Thank you for assuring me when we last met that HLTPs and Test Scripts have been QA'd by
Horizon to ensure that they are NR2 compliant. An update on other issues would be appreciated ,
addressing , in particular:
* Action being taken to ensure that the full set of Contracted Obligations required by AA
Schedule C3 are reflected in the Operational Trial Criteria (see my comment on para
3.7.2 of the Horizon Acceptance plan)
J Action being taken to ensure that the subordinate documentation pointed to by
Acceptance Criteria is clearly identified (by Version), that the versions are populated
and signed off and reflect current agreement
bd Action being taken to ensure that all contract changes have rippled through to the
relevant document set, and that the Change Control processes cover these documents.
ba That the database you are developing includes the design objective that it will allow
tracking from acceptance criterion to actual test, and back up again, and that the design
complies with this.
310 Start of Acceptance Testing - Relationship to sign off of Acceptance Specifications
I note from our earlier meeting, and from the Horizon Acceptance Plan that start of testing of the
OT system starts 25 August, and that you have put in place an agreement with Pathway (which I
support) that any changes to testing arising from changes to Acceptance Specs will be
introduced and tested during post MO regression testing. (Thank you).
Thave E-mailed you separately about the need to liaise with Parry Jenkins over the detail of how
this will be handled, and I assume you have now contacted him.
5.11 Number of Acceptance Specifications
T note that you have now incorporated within the Horizon Acceptance Plan the concept that the
23 Acceptance Specifications constitute a single logical Operational Trial Acceptance
Specification. Thank you.
5.12 PAS Single Key Issues in BES
‘There are two issues.
17/09 '98 10:19 TX/RX NO. 1298 P02
POL00028100
POL00028100
P.87718
1? SEP *98 1@:29 FROM BA-POCL PDA FELTHAM
pt The was an agreement of principle in drop down that requirements which referred to
PAS, which, because of this suppliers umique distributed system, were delivered in
2. There are some cases where both PAS and BES have to work in concert, to achieve the
required end result, and others where the functionality has been entirely shifted to BES.
within PAS, and that within BES both need to be tested for Acceptance. Where,
however, all the functionality was transferred to BES, then only BES would need to be
tested to enable a tick to be placed in both the BES and PAS boxes. AA Clause 203.1
allowed the latter scenario, Pathway, however are seeking to invoke the Clause to avoid
testing complementary functions in PAS arising under the former scenario. They
intend to rely on a test solely within BES. This is unacceptable.
As you will be aware, I discussed these issues with Karen Rogers last week, and agreed with her
that the simplest way forward was:
t To issue change requests to correct the drop-down omissions, and
2: To take a firm line with Pathway over issue 2 above.
1 am aware that discussions are already taking placc between BA and POCL on the first issue,
with a different perspective in view. I have beca asked not to proceed with the change control
Rote at this stage, rather to run the proposal in more detail past CAPS Commercial. I shall be
doing this within the next couple of days, and no doubt Horizon will hear from them if there is a
BA decision to proceed.
5.13. BA Acceptance Strategy to be produced and brokered
This clearly has to be on the back of the Horizon plan, but I probably have enough now to start
the ball rolling again.
5.14 Uncertainty as to Replan
Subject to your agreement to the comments I have made in respect of the Horizon Acceptance
Plan, I think we now share working assumptions, which will need to be monitored, and factored
into both our plans.
5.16 Replan needs some brokering of Acceptance Terms
Tshared with you a set of BA objectives for Acceptance Terms for the replan, and note that some
have been incorporated into the Horizon Acceptance Plan. Others have not. I would be grateful
if you would update me on your perspective re these objectives.
New Acceptance Issue
6. At the BA Acceptance Working Group on 10 September 1998, 1 was asked to introduce a new
Acceptance Issue, which is that the practical mechanics of execution of the Acceptance process are
unknown,
7. This issue has now been partly addressed within the Horizon Acceptance Plan, and I have indicated
within the comments I have provided where I have concems.
17/09 "98 10:19 TX/RX NO. 1298 PO3
POL00028100
POL00028100
1? SEP °98 18:29 FROM BA-POCL PDA FELTHAM P.@8718
8. seach net few days, 1 shall be seeking to amplify those concems, and set out skeleton thoughts for
Geveloping the BA side, and submitting them for approval by the BA Acceptance Working Group, T wil
Share these thoughts with you at the same time.
New Release 2+ Acceptance Specification - risk of late delivery
9. Concern was raised at the BA Acceptance Working Group meeting that unless we buttoned down the
NRO* Acceptance Specification at an early stage, then we may be vulnerable to Pathway seeking to alter
the terms at a later stage.
10. One way forward tw reduce this risk is to ensure that agreement of the NR2+ RCD and the NR2+
Acceptance Criteria are components of evidence of sufficient progress in the development of the NR2
Stage 1 sign off., and I have proposed this at para 3.6 above.
Status of Audit, Reconcitiation and Security Panels in relation to Acceptance
ay In considering how we organise our Acceptance Processes, one of the issues we must consider is the status
of the Audit, Reconciliation and Security Panels in approving Acceptance Specifications, These panels do
an excellent job bottoming issues.
13. T shall be giving some thought as to how this best might be achieved for BA, and perhaps it is something
‘We shall be able to discuss when next we meet.
14, T would be grateful if you would inform me how Horizon is now structured to deal with Security issues
and who the personnel are. Who is looking after security Acceptance issues and what processes are in
place ?
Next Meeting
15. After we last met, Iain tried to book a farther meeting, but was unable to do so, I would like to meet w/e
21 September if possible, and presently have available Monday, Tuesday, Wednesday or Friday, Please
confirm that one of these days is suitable.
Conclusion
16. Jam sory that this minute has tumed out to be so long.
17. Nevertheless, I would be grateful if you would update on progress and issues by cop Wednesday 16
September to enable me to brief Peter Crahan before the next CAPS and Card Programme Board on 18
September.
Paul Wootton
17/09 ‘98 10:19 TX/RX NO. 1298 P04
POL00028100
POL00028100
17 SEP "98 10:30 FROM BA-POCL PDA FELTHAM P.g3/18
Memorandum
To: Paul Wootton From: Colin Oudot
Address: Product Management Team
Post Office Counters Lid
Date: 16 September 1998
ce: John Meagher
SUBJECT: Acceptance Issues
Rha As we discussed earlier today, John Meagher is currently on 3
days annual leave and in the light of your requirement for a
response to your minute by CoP today I agreed to provide an
interim response.
Your Para. Interim Response ]
2 Noted, thank you
= Pa I agree, Ian Kerr is in the process of producing an
I integrated Plan. The major contribution to this is
the Pathway Acceptance Plan and I understand that
this has now been sent to us.
S22 I agree that this needs to be done.
av There will need to be an agreed definition of ProofF
lof Concept for Mobile Configurations. The
xvesponsibility for this will lie with the Horizon
Acceptance Manager.
3.4 You kindly agreed to produce a straw man for this.
3.5 Thank you for your proposal. This will obviously
have to be agreed with Pathway. I would point out
that I personally would consider no. S to be both
ees impractical and unachievable.
3.6 As above except that 1 Personally do not have any
issues with it.
Sue Clearly there will be implications on
Implementation and these will need to be I
considered.
er Ii agree that the Horizon Acceptance Plan requires
Product Management page 1 of 3 Colin Oudot
1709/98
17/09 "98 10:19 TX/RX NO. 1298 POS
POL00028100
POL00028100
17 SEP °98 18:31 FROM BA-POCL PDA FELTHAM P.18/18
further levels of detail in some areas without
necessarily agreeing to all of the Points you have
raised. As we discussed I am not convinced that all
of the processes you describe are part of an
acceptance process but there obviously needs to be
a discussion between Horizon/BA/Pathway regarding
the interaction between live incidents and
acceptance incidents.
Se I am unaware of John’s progress on the TOR and
dates but will ensure that he forwards to you as
soon as they are available.
Sis As mentioned above I believe that Pathway’s plans
have now been sent to us. Provided they are
confirmed as fit for purpose they will then be
issued for comment.
5.4 Work on this area is continuing. Your thoughts will
ef course be welcome.
5-5 i do not believe that this basis conflict will be
resolved by exchanges of correspondence and propose
that it forms part of the agenda for the ist
Acceptance Managers Forum so that you can argue the
contractual status directly with Pathway.
-6 Tam unable to comment
7 Horizon have sought to ensure Pathway’s
configuration management through logical revue and
I’m sure that John will be happy te discuss with
you how Horizon may in turn assure BA. i
5.8 Dealt with earlier
eee i can confirm the design objective of the database
is as you state. I will not be detailing actions be
taken in this interim minute.
5.10 I am unable to confirm if Parry has as yet been
contacted but I will ensure that if not John will
do so on his return.
S a2 i await the outcome of BA’s deliberations.
eas I_ appreciate your positive approach to this.
10 As discussed earlier 1 think your proposal is a
valid one.
cas Again I feel that your comments are valid and
worthy of discussion at our next meeting.
1¢ The product Assurance team within Horizon is
currently the subject of a re-organisation but John
; should be in a position to inform you of relevant
security related responsibilities and deliverables
some time next week. As a current planning
assumption it is probably safe to assume that
Product Management page 2 of 3 Colin Oudot
170998
aek TOTAL PAGE.1@ +k
17/09 ‘98 10:19 TX/RX NO. 1298 P06
POL00028100
POL00028100
Lilley, June
From: Burkin, Bob
To: Miller, Dave (Horizon)
Ce: Lilley, June
Subject: CAPS ACTIONS
Date: Friday, September 11, 1998 12:10
Attached is the status report for the actions arising from the CAPS Board meeting held on 21 August.
note: Regarding action point 6.2, I will send the extract (3 pages) to
George McCorkell after your agreement to this status report .
Are you content for the Status Report to be issued?
<<File Attachment: CAPUPDTE.DOC>>
Page 1
POL00028100
POL00028100
Post Office Counters Ltd
Retod Development Centre Director
Post Office Counters Ltd
King Edward Building
Pos Once Coser at Repeared to and
Nec 21500 Repuered Oe Hong Ewer
Rig Coen Sewee ndon CIA TAA
POL00028100
POL00028100
‘ 11 SEP ’98 16:41 FROM BA-POCL TERMINAL HSE To PAGE .881
co
FAX HEADER
Post Office Counters Ltd.
3rd Floor, Terminal House
Horizon Programme 52 Grosvenor Gardens
London
SW1W 0AB
To: George McCorkell
Fax No:
Tel No:
n > Copy: Dave Miller
Date: 11/9
Time: 16:15
Number of I5
pages incl.
this one:
From: Bob Burkin
Subject: Action (AP6.2) from CAPS Board Meeting
Comments
Attached is an extract (including a copy of the first page for
reference) from the Support Notice for NR2 (Model Office
and End to End) detailing call raising procedures
(including PinICL process). A copy of the complete
document is held by P Noon (CAPS).
This clears the action (AP6.2) picked-up by Dave Miller at
the CAPS Board meeting held on 21 August.
Lhope this proves useful.
Bob Burkin Tel:
Horizon Planning Team Fax: I
bubfix.doc
11/08 '98 16:38 TX/RX NO. 1267 POL
POL00028100
POL00028100
Post Office Counters Ltd
Retail Development Centre Director
Post Office Counters Led
King Edward Building’ '{ I
King Edward Street’;
London I
ECIA IAA
POL00028100
POL00028100
11 SEP ’98 16:41 FROM BA-POCL TERMINAL HSE TO! PAGE .a02
y AAU HS FRE Lure FAX BA/POCL TEST S}TE TERMINAL HOPSE Booz
{CL Pathway Support Notice - New Release 2 Version: 1.0
Model Office & End to End Dates Males
Document Title: Support Notice - New Release 2 - Model Office & End to Eng
Abstract: This document describes the Sypport Routes for the Model
‘ Office phases and End to End testing for New Release 2. It also
govers the release process for the Model Office and End to Eqd
Tigs- :
§fatus: Draft
Distribution:
ICL Pathway J.Bennett, M.Coombs, T.Austin, C.Humphries, J.Dicks,
z D.Conniss, M.Fisk, K.Morley, M.Peach, L.Higman,
VA P.Gardner, G.French, B.Longley, G.Rogers, N.O'Sullivan,
P.Mead, P.Curley, J.Lindegard-Stewart, J. Wright, R.Aurora,
I.Bowes, S.Lee, A-Hanson, I.Morrison, P.Jobson
ICL Pathway Model Office _S.Palladino, G. Jackson, M. Molloy, J. Burgoine
ICL Pathway Development Product Managers
ICL Pathway Customer Service Management Team
Girobank D. Wilson
DLR R. Ellis
System service B. McCully
Oracle K. Linfoot
HSHD/SMC S. Breen, R.Vigar, L.Cotterell, J.Opera
Outsourcing V.Cochrane, G.Boyce, S.Gardiner, C.Johnson, R.Bustard,
L.McGrath, P.G.Roberts
Horizon Test Team C. Young,’J. Brett, K, Hall
TIP P. Jones, D.Salt
Vv CAPS P. Noon
POCL Service Management N. Embling
POCL Migration Team T. Hacker
POCL RDP T. Baldwin
OSG / HAPS I. Blood
OBCS S. Bollom
PACS A. Smith
C. Oudot
Author: Pat Lywood
Comments to: Pat Lywood
a
COMMERCIAL IN CONFIDENCE Page 1 of 34
© 1997 ICL Pathway Lid
12 SEP 'S8 19:23 Ot94 37 Exoe meer nn
11/09 '98 16:38 TX/RX NO. 1267 P02
POL00028100
POL00028100
Post Office Counters Ltd
Retad Development Centre Dizector
Post Office Counters Ltd
King Edward Building
King Edward Street
London
ECIA IAA
FocsimileI _.
Corer tara id
Pom
Nec I50 Repewrd Ot Ky Coon Bing
Hang Léword Seve Lonon ECIA TAN,
POL00028100
POL00028100
AGE .883
11, SEP 798 16:42 FROM BA-POCL TERMINAL HSE TO! iz
e us7uy ver x) + TERMINAL HOUSE @oo3s
Re 2UILY PAA BA/PUCL 'TEST SI’
4.
ICL Pathway Support Notice - New Release 2 Version: 1.0
Model Office & End to End Dater 1/8/98
4.1. Normal Working Hours Support
During Normal Working Hours, the support route will operate as the Live Operational
Service, All application, operational and infrastructure calls will be raised on the
HSHD and Payment/Card/Pun related calls will be raised on the Payment Card
Helpline. (NOTE - Girobank are not providing the Payment Card Helpline facility for
E2E testing. )
‘The 24, 3rd and 4® line Support routes will operate in a similar way to the Live
Operational Service. The only amendment is that 3“ line will pass calls to PIAT rather
than direct to development. If PLAT decide a fix is required they will pass the call to
Release Management to authorise the fix. Once the fix is authorised Release
Management will farward the call to development. See Appendix 4.
The expertise and knowledge of the Pathway T&L team may be used to aid in the
Support process during the MO period.
‘When a call reaches 3" line the call type will be amended to:
N - for MORI and MOR2
M - for MOT
E-forE2E
For full details of phone numbers and operational hours see Appendix 2.
4.2 Out Of Hours Support Routes
During Out Of Hours minimal HTT testing is planned. Any problem occurring out of
hours should be in the area of file transfer of data to and from the MO Data Centre,
transfer of data to or from the MO Counter Environment or problems to do with the
operation of the system.
The Support Route during these times is direct from Outsourcing Operations to 3rd
line support and the E2E or MO Manager. 3 line will call in whomever they deem
Ne appropriate. The E2E or MO Manager is called in case there may be a delay to the
plan or authorisation is required to perform any data changes.
43 Call Logging
All issues requiring ICL Pathways attention must be logged via the HSHD.
For calls from HTT the FAD code of the relevant post office should be sufficient.
For calls raised by other areas involved in testing the following codes should be used:
PAT900 for MO
PAT901 for E2E
The HSHD call logger must ensure the text of the call includes a statement detailing
whether it is a MO or an E2E call.
Ne
COMMERCIAL IN CONFIDENCE: Page 8of34
11 SEP 'S8 10:24 PAGF AR
11/08 '98 16:38 TX/RX NO. 1267 P03
POL00028100
POL00028100
Post Office Counters Ltd
Retad Development Centre Director
Post Office Counters Led
King Edward Building
King Edward Street
London 4
ECIA TAA. bad
POL00028100
POL00028100
11 SEP ’98 16:42 FROM BA-P
cilanal
aseU9 90 PRL 2U:ZU
PAGE.804
TERMINAL HSE To!
OGL. SRT NN OGL TEST Site
ICL Pathway Support Notice - New Release 2 Version: 1.0
Model Office & End to End Date: 1/8/98
4.4
45
4.6
AT
4.8
Call Logging for CAPS, TIP, ESNS, HAPS, PACS, RDS
Before a call is logged with the HSHD HTT should be contacted. HTT will discuss
the fault with the MO Site Manager or E2E Manager. The calling supplier will be
advised if a call should be placed with the HSHD or whether the fault is due to an
existing known condition. This process only applies to the following suppliers :
CAPS, TIP, ESNS, HAPS, PACS, RDS.
APT migration calls
All calls on APT migration should be directed to the APS helpdesk.
Data Warehouse calls
Calls related to the Data Warehouse should be routed to PinICL stack CFM Support
2
Oracle support calls
During MORI, and the cycle 1 main pass of E2E testing, support for the Oracle
applications will be provided by Oracle Development with the support of ICL
Outsourcing. In subsequent testing phases Support will be provided by ICL
Outsourcing with Oracle Development in a supposting role.
Calls for Oracle application support should be routed to PinICL stack Oracle 2
Reference data calls
Calls related to reference data should be routed to PinICL stack RefDataQual. The
‘Product group’ should be set, by 3 line support, to ‘Ref Data’. The ‘Product’ should
be set, by 3" line support, to ‘Ref Data Problems’.
41 SEP °S8 1@:25 r
COMMERCIAL IN CONFIDENCE Page 9 of 34
PAGE.@4
11/09 '98 16:38 TX/RX NO. 1267 P04
TERMINAL HOUSE @ao4
POL00028100
POL00028100
Post Office Counters Ltd
Reted Development Centre Director
Post Office Counters Led
King Edward Building
King Edward Street
London
ECIA IAA
POL00028100
POL00028100
. z —-POCL TERMINAL HSE To i PAGE.@a5
Rela jee Re Estes BA/POCL TEST SI +> TERMINAL HOUSE @ous
ICL Pathway Support Notice - New Release 2 Version: 1.0
ae I
Model Office & End to End Dare: 1898
5.11 Summary and Timings
1030 i Suppliers and support route
1200 Report Received From TIP / CAPS / HAPS/ ESNS/ RDS / PACS
I 1200 Report Received From HTT Via MO Site Manager or E2E Manager
1330 Consglidated Report Sent
6 = PinICL Management
a The overall responsibility for the management of the PinICLs raised during the MO
and E2E period lies with the MO Manager and E2E manager respectively.
The Product or Service Managers, of both Pathway and it’s suppliers, are responsible
for the management and timely resolution of PinICLs within their own stack.
7 Test control
Confirmation that MO and E2E testing is to be suspended or restarted rests with the
following people. They are responsible for ensuring that all interested parties are
informed of the suspension and expected restart dates.
MORi & MOR2 MO Manager
MOT HTT MO / B2E Manager
Cyclel main pass EZE E2E Manager
ee Cycle2 main pass E2E EAR Manager
Fn pen Fe sn
COMMERCIAL IN CONFIDENCE Page 17 of 34
11 SEP 'S8 10:25
*e TOTAL PAGE.aa5 xx
11/09 "98 16:38 TX/RX NO. 1267 POS
POL00028100
POL00028100
Post Office Counters Ltd
Retail Development Centre Director
Post Office Counters Ltd
King Edward Building
King Edward Street
London
ECIA IAA
Ne: 2154500 Regtred Oe King Ewer ing
King Eduard Set London CIA TAA
POL00028100
POL00028100
FMPMMVIrie
I; APD 2S)
Miller, Dave (Horizon) 41 SEP 1993
From: Twidale, Mike l} Buu Ta
To: Miller, Dave (Horizon) 9 tornenaoenneeennennnnn
Ce: Lilley, June
Subject: CAPS Board Report
Date: 11 September 1998 10:07
I attach copy of the Horizon input to the CAPS Board report for your clearance for issue today.
We have taken on board amendments arising from your meeting with Bob Burkin.
We are also pursuing the action point updates as agreed and will provide these when we have them.
Re Section 5.2 of the report (ie the BES/PAS boundary issue) and the associated action - Roger Tabor
is not in the office until Monday. I have asked if he can confirm that the BES/PAS boundary issue is in
hand, and whether you and he need to discuss this further.
Please advise whether you are content for the report to be issued'to CAPS.
ate Attachment: CB1809.D0C> >
Chroned
Oa Wa,
Page 1
POL00028100
POL00028100
Post Office Counters Ltd
Reta Development Centre Director
Post Office Counters Ltd
King Edward Building
t King Edward Street
London‘
ECIA IAA
Osea Kg Coen
Ceword Seve Lona CIA TAR,
POL00028100
POL00028100
SS
Benefits Agency and
Post Office Counters Ltd.
3rd Floor, Terminal House
Horizon Programme 52 Grosvenor Gardens
London
SW1W OAB
Tel:
Fax:
To: Tim Cutts Copy: Dave Miller
CAPS Programme Office Jan Topham
Sue Daniel
Val Whitbread
From: _ Bob Burkin Date: 11 Sept. 1998
Subject: Input into CAPS Board Report
As requested, the attached report is provided as input into the CAPS Programme
Board Report for the meeting to be held on 18 September.
It is expected that Dave Miller, Horizon Programme Director, will be attending the
meeting. Will you therefore please arrange for the Agenda, including timings, to be
supplied in advance of the meeting
A status report (on‘actions - if any - arising from meeting on 21 August -) will be
provided separately.
Thope this proves useful. As always, happy to discuss.
Bob Burkin
Planning & Reporting Team
Horizon Programme
CAWINDOWS\TEMP\CB1809.DOC page 1 of 7
POL00028100
POL00028100
Yai 193 wpe mag pane Bat
Rane Rk BO Pansy CNET N
90 may
Supung premp3 Suny
p27 ss91Un0D 92yj0 as0q
2oDRAg ane) waurdopiag OY
PI] suaqUNOD D2130 350g
POL00028100
POL00028100
Input into CAPS Programme Board Report
for Meeting on 18 September 1998
1 Introduction
This report summarises the state of the Horizon Programme as at August
month end.
2 Programme Overview
The major focus of the Programme at the current time continues to be:
+ supporting the existing live systems
+ supporting the testing phase
+ progressing the ‘Programme Management’ content of the Replan with
respect to the Live Trial, multiple Benefits and the NR2+ Release.
+ clarifying the contractual implications and acceptance process arising
from the replan.
+ developing the Live Trial plans in detail.
+ developing the 1c to NR2 migration plans in more detail.
3 * Live Operations
The current Release continues to provide a Benefit Payment Service and
Order Book Control System for Child Benefit Payments in 204 outlets
(119 in the South West & South Wales Region and 85 in the North East
Region).
From an operational point of view, there are no major threats to business
continuity.
Concern over the level of incomplete transactions (ITs) continues. These
have risen to 5.6 per 10,000 during July (from 4.0 in the previous month).
The main reason for this increase is due to a single category, BES/OBCS
Corruption (which represent 47% of all Incomplete Transactions)
Operational workshops continue to be held to address this issue and the
resultant fixes for various categories of ITs have been placed in testing.
Evaluation and analysis of these fixes are imminent. If solutions prove
successful it is foreseen that categories of ITs and consequently volumes
will reduce dramatically - particularly those in the category mentioned
above. Forecast implementation of these solutions is 22 September (on
the assumption that testing is successful and passes acceptance by sponsor
organisations). -
During July there were approximately 68,000 encashments (including
foreign encashments) with a total value in excess of £2m.
The Horizon Service Management Team continues to produce a monthly
Service Report which includes service performance reports and
operational issues / threats. The latest report was issued on 28 August
(BA/CAPS are included on distribution list).
C:AWINDOWS\TEMP\CB1809.DOC page 2 of 7
POL00028100
POL00028100
Deora peng
aaa
2] sunUNED 921 280g
sopang anua maudeping poy
P27 suqUN0D 240 asoq
POL00028100
POL00028100
Progress against the Master Plan and Integrated Programme Plan
The Programme Master Plan (MP version 4) and Integrated Plan (IPP
version 1) will be updated following the formal agreement to the Release
2 replan. Progress is being monitored against Pathway High Level Plan
version 4.0 (15 June) and the current status of key milestones planned for
July/August is shown below:
milestone planned date achieved /
re-forecast
Direct Interface Testing 8 July Completed as planned.
Start of Horizon Model 3 August Achieved -. Horizon
Office Rehearsal (for MO commenced 3
Release 2) August 1998.
Commence End to End 3 August Commenced on
testing (main pass) schedule
Commence Office Surveys, 3 August Work commenced in
Re-surveys and all areas
Modifications,
Complete System Test Main 30 August All these elements of
Pass for EPOSS, TPS, MIS, System Testing are
RDMC and Training (mode) forecast to complete
by 21 September.
Overall testing
timescales are
consistent with replan
dates.
Complete Walkthrough of 31 August Extra work is required
E2E procedures (target date) in order to define all
processes to a lower
level of detail than
expected. This
milestone has been re-
forecast to complete in
. November for
subsequent inclusion
in MOT.
Complete MOR 1 11 September Successfully
completed 26 August
(earlier than
scheduled)
For this report, the list of the strategic and high level Programme
milestones (contained in the Master Plan (version 4) and Integrated
Programme Plan (version 1) showing their current status) has not been
included. The list will be reinstated when the current replan exercise has
been formally agreed and the milestones reviewed to ensure that they are
still relevant to the revised approach.
C:AWINDOWS\TEMP\CB1809.DOC page 3 of 7
POL00028100
POL00028100
pans puemp3 Suny
upyng psemp3 Bupy
Pr] s191Un03 92yjO 3804
sepang amie weudeaiog poy
P37 su2UNOD B2WJO aS0g
POL00028100
POL00028100
7 :
1
5 ICL Pathway Release 2
5.1 Current Status
Planning
Dialogue continues in order to resolve issues affecting the Replan
particularly with regard to the Live Trial, the multiple Benefits
introduction and the release of NR2+. Agreement has been reached on thé
structure and dates for MOR, MOT and E2E activities for release 2
(POCL and Child Benefit functionality). In addition, agreement has been
reached on the 1c to NR2 migration plans, including the Data Centres, and
the installation of the extra 100 offices. Work is now necessary to develop
the detailed aspects of this plan and Pathway have been invited to
commence work in this area. Meetings with BA arranged for 9
September.
Testing :
JSA MOT third cycle is progressing well and is due to complete on
schedule mid September in time to feed into (Horizon) MOR2 .
MORI completed satisfactorily on 26 August 1998. Overall impressions
of the counter service from the users (trained counter staff) and the
Horizon Test Team have been that the counter is working well: that it is
useable and resilient, that it performs with speed and that the error and
exception handling messages/functions are present. The majority of
current problems are considered to be of minor importance and are
expected to be fixed for MOR2 which is planned to start on 14 September.
The MORI phase has been successful. Pathway have been able to prove
their live architecture, in particular the data centre and its migration, the
network and communications, and the connectivity between the counter
and the data.
E2E progress is slow but steady. The E2E cycle is being run in a more
deliberate manner than MO, allowing serious errors to be fixed before
progressing. The expectation is that most of the first cycle will be
completed by the target date. At this stage it is too early to predict whether
there will be an impact on the final end date of 18 December. The latest
position on testing will be presented by the Horizon Programme Director
to the CAPS Board at the meeting on 18 September.
Acceptance
During the period, management of the acceptance team was further
strengthened with the recruitment of an Incident Manager and a Process
Manager. Further recruitment continues to bring the team up to full
strength. A review of the support tools has completed and additional
hardware has been ordered.
The acceptance framework, which provides a business top-down view has
now been developed and is being used to provide a review of the
adequacy of the acceptance approach. A gap analysis continues and will
be completed by the first week in September. This will be followed by
C:AWINDOWS\TEMP\CB1809.DOC page 4 of 7
POL00028100
POL00028100
WE VID sop 5 peng Bat
Deore pang] Rea 90 Peed OYSIEIN,
ream peng pry tne) BD may
Wi vida
wopuoy
pang puempy Zupy
Surpyng paempy Zupy
I sua1uN0D S21} 3504
sepaag anuay waudopicg poy
P37] SudIUNOD 92140 350g
POL00028100
POL00028100
further analysis to determine whether the identified gaps can be filled by
other parts of the contract or whether they are true omissions.
, The Acceptance Preparation Stage is continuing with the review and
agreement of the acceptance specifications. ICL Pathway’s target for all
specs to be completed and signed-off by mid-August was not met and the
implications are being assessed. All 23 acceptance specifications have
now been received from ICL Pathway and reviews continue. There are
still a number of problems in this area and additional efforts are now being
brought to bear to improve the overall situation.
Formal management forums are in the process of being established for
acceptance. Draft Terms of Reference for the Acceptance Managers’
Forum have been completed and invitations to members will be issued
toward the end of August.
Implementation
General
The Implementation Risk Register has undergone a complete review with
the second iteration, including updates on mitigating action, issued 1
August.
The Horizon Implementation Board met on 11 August and will continue
to meet on a monthly basis to co-ordinate progress and address issues.
Installation
An updated Installation Strategy is expected from ICL Pathway for POCL
sign off by 21 August. A signed off copy of the Survey Requirements has
been received from ICL Pathway (excluding Flat Screens). A revised
Survey Document reflecting the Flat Screen option has been received and
is under review.
Training
Model Office training and training of Survey Support Managers has been
completed.
Migration
A draft plan and draft interim procedures for implementation of NR2 in
Release 1c outlets have been produced. The Outlet Migration Strategy is
being redrafted by ICL Pathway taking into account recent developments
in the ECCO migration process. Discussions are underway with ICL
Pathway to obtain their sign-off of the migration tool functional
specification. Interim tools were used in MORI, and some difficulties
were experienced. Revised migration software tools will be ready for use
in MOR2.
Live Trial
Work continues to draw together the details based on the Horizon replan
which proposes a 17 week Live Trial. The justification for the 17 week
period has been presented to Pathway though this has not yet been
formally accepted by them given the wider contractual issues.
C:AWINDOWS\TEMP\CB1809.DOC page 5.of7
POL00028100
POL00028100
et en I
Yi vi31 vor 05 png) Rey
Danae nag Bn 990 Pam COSTE AN
peda pmadny yr tare OO me
uopuey
pang putmpy Zupy
Supung premp3 Suny
xy sus1UNOD 92140 2504
sepang anus woudepiog poy
PY] su93UNOD B2YJO r50g
POL00028100
POL00028100
National Rollout
A meeting between Pathway and POCL increased the joint understanding
regarding the trigger points for starting rollout and the currently agreed
ramp up volumes. Further work is necessary to develop this and to link
with the Live Trial plans.
5.2 Issues / Risks
The following areas of concern have been identified as possible obstacles
to the delivery of Release 2. These issues are being actively managed
within the Programme.
Issue Action
End to End/Model Office Testing
While the first cycle of Model A number of actions are being
Office completed ahead of evaluated to improve the likelihood
schedule, some problems have been I of completion to schedule. Some
encountered in End to End testing I contingency time is also available
which may pose a risk to achieving I in January should it prove
the 18 December completion date. I necessary.
BES/PAS Boundary
Agreement on this boundary is Action is with POCL Finance
necessary for establishing liabilities I Director who is reviewing the
in the live environment. position. Horizon Programme
Director continues to liaise with
Finance Director to provide input as
required.
BES Fallback
Additional mechanisms are Pathway are implementing an
required to ensure the final agreed solution.
reconciliation of BES and EPOSS
transactions when a communication
line failure occurs,
Acceptance Specifications
Some specifications are incomplete I Continuing work with Pathway to
due to unavailability of some cited I support the process of completing
evidence and inadequate coverage. I the specifications and improving
' This also impacts the clarity of the I their quality. DSS comments
plans for acceptance execution. outstanding on the DSS interface
specification.
6 Future Releases
Release 2+ :
The issue resolution process is continuing. For soft EVP the action is with
POCL to follow up the proposal from Pathway. There are no outstanding
technical issues concerning on-line enquiries though the issue around the
required delivery date is being progressed.
Pathways Release Contents Definition was received on 27 August and
distributed for comment.
C:AWINDOWS\TEMP\CB1809.DOC page 6 of 7
POL00028100
POL00028100
39 Yop ng Rang Dg .
a0 Peleg Cosy 18M
Im
wiv
Dora nae
peo
=) bd
WI VID3
uopucy
Wang puemp3 Bury
Bupung prempy Zupy i
7 s1a1un0D 9230 2504 4
song anvan wourdoping pony
27 S193UNOD 92140 350g
POL00028100
POL00028100
A development plan for NR2+ should be available by the end of
September.
7 This report has been produced in accordance with the guidelines agreed
between Peter Crahan and the Horizon Programme Director on 15 April.
The area not covered is ‘Routine Commercial / Contractual Activity’
where no request had been made by the CAPS PMO for specific detail,
and no input received from the Horizon Joint Contracts Team.
C:AWINDOWS\TEMP\CB1809.DOC page 7 of 7
POL00028100
POL00028100
Wr 191 wpe sag pang Bet - .
Deere pany Ani 90 punns CoS VIE AN
pada rt
uopuoy I }
wang puempg Bury
Burpung premp3 Suny
pr] ssa1uno5 9240 3804
Py] S19IUNOD D450 350g
POL00028100
POL00028100
ICL Pathway Release 2 Model Office Rehearsal 1 Ref: YURERIONG
‘ersion: .
Closure Report, Date: 16/09/98
Document Title: Release 2 Model Office Closure Report
Document Type: Test Report
Abstract: . This document summarises the findings and conclusions of the
Pathway Test & Integration Unit on the conduct of the Model
Office Rehearsal 1 test phase.
Status:
Distribution: . Horizon Pathway
J. Meagher T. Austin
S. Rilot G. Chatten
M. Coombs
P. Jeram
C. Wannell
J. Wooler
Author: S. Palladino
Comments to: S. Palladino
Comments by:
COMMERCIAL IN CONFIDENCE Page 1 of 8
© 1998 ICL Pathway Ltd
POL00028100
POL00028100
ICL Pathway Release 2 Model Office Rehearsal 1 f AIREPIONG
Closure Report 16109198
0’ Document control
0.1 Document history
Version IDate Reason
0.1 11/9/98 I First Draft
0.2 Approval authorities
Name Position - Signature Date
None
0.3. Associated documents
Reference Vers I Date Title . _I Source
0.4 Abbreviations
APS I Automated Payment Service
BPS I Benefit Payment Service
CAPS I Customer Accounting and Payments Strategy
EPOSS I Electronic Point Of Sale Service
ESNS I Electronic Stop Notice System
HAPS I Host Automated Payments System
MORI I Model Office Rehearsal 1
OBCS I Order Book Control System
R2 I Release2 (Horizon system)
TIP I Transaction Information Processing
0.5 Changes in this version
None. This is the first issue.
COMMERCIAL IN CONFIDENCE Page 2 of 8
POL00028100
POL00028100
ICL Pathway Release 2 Model Office Rehearsal 1 Miia
Glosure Report Date: 16/09/98
~ 0.6 Table of content
1 Introduction... woe 4
2 Scope and Objectives, 4
3 System under tes! 4
3.1 Environment 4
3.2 Software
4 Test Conduct
4.1 Test Phases...
4.2 Tests Performe
4.3 Testing Incidents.
5 Conclusion
5.1 Summary.
5.2 Achievements
5.3 Issues...
6 Appendix A - Model Office Test Environment
COMMERCIAL IN CONFIDENCE Page 3 of 8
POL00028100
POL00028100
ICL Pathway Release 2 Model Office Rehearsal 1 Doc Ref: VI/REP/016 I
Version: 0.1
Closure Report Date: 16/09/98
1 Introduction
This is a summary report addressed to Pathway and Horizon management to comment on the
conduct of the Model Office Rehearsal 1 phase of Pathway’s Release 2 testing. It focuses on
the testing environment, the testing activities performed, the results of these, and the
conclusions drawn.
The appendices contain additional supporting information to the text.
2 Scope and Objectives
MOR! is the first of three planned Model Office Rehearsals. It’s major objectives are to
prove:
Pathway’s solution architecture, network and connectivity
Pathway’s supporting infrastructure
migration from Release 1c to R2
supporting and reporting processes and routes are in place
It is not a purpose of MORI to perform R2 functionality proving although note is taken, and
incidents raised, in response to errors found. Due to the nature of this test it was expected that
there would only be time for a small subset of the available counter tests to run successfully.
The format of the testing was for the Horizon test team to run a series of scripts and test cases
jointly devised by themselves, the Benefit Agency and TIP, at a Model Office site based in
Borough High Street and supported by Pathway operations at the R2 target live operational
environment in the Bootle data centre.
3 System under test
3.1. Environment
The test environment within the Pathway domain comprised two data centres, one at release
1c and the other the target R2 go live solution, with links to all external systems. Full details
of these are given in Appendix A.
offices were migrated from release 1c to R2; four new offices were introduced into the R2
system, two from ECCO and two that were previously manual. The counters were the current
Pentium baseline rather than the proposed future Pentium 2.
i
I
The test environment within the Horizon domain comprised seven Post Offices; three of these I
I
Gateway PC’s, for the transmission of data to remote sites, were located at Famborough,
Huthwaite and De La Rue, Tewkesbury.
COMMERCIAL IN CONFIDENCE. Page 4 of 8
POL00028100
POL00028100
ICL Pathway Release 2 Model Office Rehearsal 1 Doc Ref: VI/REP/016
Version: 0.1
Closure Report - Date: 16/09/98
3.2 Software
The following applications formed part of the testing baseline:
m BPS :
m@ EPOSS
m APS
™ OBCS
The software release was 8F increment 4, with some additional changes made to this baseline
during the test cycle. These changes were notified to the relevant testing partners, and are
identified in Appendix B of this document.
4 Test Conduct
4.1 Test Phases
The testing was performed by Horizon test staff and Post Office counter staff over the period ©
3" August to 27" August inclusive, the stages being:
m 3"_ 11" phase 1 of migration, moving three outlet operations from
telease 1c to R2, with the data centre at release 1c
m 12". 13", data centre migration to R2
m 14.27, full R2 operation and the introduction of new R2 outlets
CAPS were not available to participate in this phase of testing, their input being simulated by
Pathway. As a result, the BA PACS reconciliation group could not participate.
4.2 Tests.Performed
The following are the test statistics:
™ numberof planned scripts 5089
@ number of scripts run 4072
™ number ofscripts passed 3734
™ percentage ofscriptsrin’ 80%
™ percentage of scripts passed 91%
a
As a result of some initial connectivity problems the scheduling of script running was re-
planned, after which the revised timescale was achieved.
COMMERCIAL IN CONFIDENCE Page 5 of 8
POL00028100
POL00028100
ICL Pathway Release 2 Model Office Rehearsal 4 Doc Ref: VI/REP/016
. Version: 0.1 ~
Closure Report Date: 16/09/98
4.3 Testing Incidents ,
Throughout the test cycle a number of incidents were raised. These are summarised as
follows:
Total Incidents raised 341
Incidents Closed
no fix required 120
fix applied during MORI or due 80
; in MO2 ,
duplicate of existing PinICL 55
Incidents still open 86 *
* denotes: 7 fixes are included in the MOR2 baseline for open incidents.
Remaining open incidents will be carried forward for MOR2 reporting
5 Conclusion
5.1. Summary
MORI successfully proved the test phase objectives, namely that Pathway’s architecture,
networks, connectivity and supporting infrastructure are all fit for purpose. Some issues were
identified, none of which are considered to be major, and these can be addressed in the later
_ Phases of MOR.
Although of a lower testing priority, the degree of application functionality executed was
higher than expected.
5.2. Achievements
The following have been successfully demonstrated:
™ Bootle R2 data centre build
networking and communications
data centre security
installation of outlet equipment
auto-configuration of R2 counters
‘migration of outlets from Release 1c to R2
use of MiMan migration tool and HFSO procedures
COMMERCIAL IN CONFIDENCE Page 6 of 8
POL00028100
POL00028100
ICL Pathway Release 2 Model Office Rehearsal 1 Doc Ref: VI/REP/016'
Version: 0.1
Closure Report Date: 16/09/98
data centre migration from Release lc to R2
link to and from ESNS
links to Famborough (HAPS) and Huthwaite (TIP)
link to De La Rue
_ PAS/CMS Help Desk operation
Horizon Help Desk operation
Pathway support procedures .
operation of the four main application areas
operation of the Data Warehouse
user training
5.3 Issues
The following issues were identified, some of which have already been addressed:
™ the MiECCO migration tool was not available for use, so ECCO
outlets were migrated using the manual migration tool instead
™ the data prepared for input.to the manual migration process did not
lead to speedy use of the software tool ©
the cash account did not balance
although used, the FTMS gateways were not sufficiently robust
there were no non-core reference data products available
some problems were experienced using the back office printer
COMMERCIAL IN CONFIDENCE Page 7 of 8
POL00028100
POL00028100
ICL Pathway Release 2 Model Office Rehearsal 1 pias Ref: Me sa
ersion: 0.
giosine Repory Date: 16/09/98
6 Appendix A- Model Office Test Environment
‘Washington! vie CAPS Hutheaise (TemDMerar
COMMERCIAL IN CONFIDENCE
Page 8 of 8
POL00028100
POL00028100
17/09 '98 THU 18:02 FAX 0181 730 4161 ICL PATHWAY PROG. DIR. Boo
FAXMiessage
To: PD anc DN) \Non
Phone:
Fax Phone:
CC.
Date: ee: Bet
Restricted Commercial - This fax transmission and aay accompanying documents may contain
information belonging to the sender which is confidential and legally privileged. This information is
imtended only for the usc of the individual or entity to whom this facsimile is addressed. If you are
not the intended recipient, any disclosure, copying, distribution or action taken in reliance on the
sckicsusdion beaealaad metain bo aicaly peoutece, If you have received this transmission in error,
please call the sender to arrange for the return of the documcats.
Message:
Docs
(iscias Res OAXachs» ~ Ads, dabadat
Orrred proves «Simon LIA aye chy ca hente’
Lyd yer plame Ley Sime, that Dir Barer
As ees we 3 ena Oren, ee
2 vagina Te As sy be ka Agnes off
poem CP Rela for mony
Ve ere Vee La ke oa Give 4 eclsde ds LAL.
Pim _ovarleiis. a.d these, Pinte bal gy hvaBinohad ,
ce
If transmission is ICL Pathway Ltd
Interrupted or Forest Koad
incomplete, Feltham
Please notify Middx
‘sender as soon as TW13-7Ej
possible
17/09 ‘98 18:03 TX/RX NO. 1305 POL
POL00028100
POL00028100
ICL PATHWAY PROG. DIR. Booz
17/09 '98 THU 18:02 FAX
MrD Miller
Horizon Programme
Benefits Agency & Post Office Counters Ltd ”
King Edward Building
King Edward Street
London EC1A 1AA
17th September 1998
Dear Dave,
ICL
As promised, please find below a current update on testing progress,
End2End
It is now planned to complete the first cycle of testing on 22/9, including CAPS Recovery
testing.
Inthe early stages of E2E it was discovered that the Reference Data supplied by POCL did
not contain valid Non Core products. It was agreed that this was required for E2E and the
quickest way forward was for Pathway to edit the file delaying testing for 5 days, rather than
wait for an RDP update.
‘There were a number of environment issues between Pathway and CAPS before Temporary
Tokens would operate. These were resolved after a 3 day delay.
Following these initial delays, E2E generally progressed at a day for a day without having to
restart. ° - .
The data centre was successfully migrated and MiMan and MiEcco successfully used to
migrate counters.
Transfers were made between HAPS, CAPS, OBCS and TIP. Some issues were experienced
and were addressed at the time. ,
Communication issues between CAPS and Pathway were resolved and On-Line CAPS
processing of Temporary Tokens, Urgent Payments and Urgent Stops were successfully
made.
. CAPS have had some difficulties matching their data and expected results. Issucs such as
‘payments not being loaded due to missing cardholder/beneficiary data need to be resolved by
CAPS before the next cycle.
Following the first day of CAPS Recovery testing tomorrow, testing will be suspended over
the weekend to allow CAPS time to address their anticipated Recovery issues.
PinICLs have been raised during the testing and will be addressed for later Cycles.
17/09 "98 18:03 TX/RX NO. 1305 P02
POL00028100
POL00028100
4 17/08 '98 THU 18:03 FAX
ICL. PATHWAY PROG. DIR. 003
A meeting was held with Horizon, POCL and BA to discuss E2E progress and the movement
into the next Cycle, It has been agreed that the migration days run for cycle 1 will not be
repeated. This therefore reduces the cycle lengths of E2E and allows for the further cycles to
be aligned with Model Office cycles. It is expected that this will be agreed on 18/9 and
planned in detail at a workshop next week.
MOR2
Progress has continued through the week on MOR2.
' , y,
On Monday, the 1¢ Counters were delivered to Borough and the CAPS files were received q
and processed,
_ On Tuesday, the Ic counters were configured on to the System, further CAPS files were
received and processed and the National Stops file was loaded.
On Wednesday, tests were first performed on the Ic counters and then these counters were
replaced by R2 counters. During the following MiMan migration processing a potential issue
was detected, this was dealt with at Borough by zero filling the remaining Stock Units. There
is confusion as to whether these Stock Units should have contained data or zeros, but if this
is found to be an issue, the details can be added by Remitting In the Stock Unit information.
On Thursday, further testing has been performed on the final 1¢ Post Office and this is
currently now being migrated. The Post Offices previously migrated to R2 counters are now
being used for further tests.
At present we are on schedule for migrating the data centre from Ic to R2 this weekend, -
General
Pathway is currently working towards creating the Software build that MOR3 will be based
on. This build will contain resolutions to the remaining issucs identified in the MOR2
Release Notice and will deliver BES Fallback.
Pathway has now issued Version 5.0 of the ICL Pathway Release 2 High Level Plan and is on
; .
schedule to deliver the milestones within it. i
i
:
"If you would like to discuss any detail further, please contact me at Feltham.
ICL Pathway Ltd
Forest Road -
Peter Jeram Feltham
ICL Pathway Middx TW13 EJ
patra tas
Reimeed h Ere and ro nonce,
Registered Otrce
20 FORT
tbrean IAS
17/09 '98 18:03 TX/RX NO. 1305° P03
POL00028100
POL00028100
ey
CAPS and Card Programme Board Actions - Issue 6
Horizon Action Points / updates from Board meeting on 21st Aug
1998
Action point Update
AP 5.4 (H) Cleared -Meeting held on 3/9/98.
Peter Crahan / Dave Miller
to arrange for a final PDA
transition board to take
place.
AP 6.1 (H) Ongoing - Update to be provided to Vince
Mike Coombes to provide _I Gaskell, copied to Dave Miller, by 16
an update to Vince Gaskell I September.
of the code changes being
put in place to resolve the
issue of incomplete
transactions.
AP 6.2(H) Cleared - Hard copy of extract from Support
Dave Miller to provide Notice for NR2 (Model Office and End to
George McCorkell with a End) v1.0 detailing call raising procedures
written description of the (including PinICL process) provided to
PinICL process. George McCorkell. Complete document held
by P Noon (CAPS)
AP 6.3 (H) Dave Miller to Cleared - Short brief was provided at the
provide Vince Gaskell with I meeting on 21 August.
a report on what has been
done as result of the
Correspondence Server
failure (13/7/98)
AP 6.4 (H) Dave Miller to
provide greater visibility of
what is happening in
Horizon testing to Parry
Jenkins
Ongoing - Horizon Testing Manager to
contact Parry Jenkins to confirm
requirements and progress as necessary.
(Note - CAPS staff are on site and present
during Testing)
C:\WINDOWS\TEMP\CAPUPDTE.DOC
POL00028100
POL00028100
———— a I
~
Yar ign tener eas pang Bet J
Mere nent het 200 pamadrd OF STEN .
reoae et)
2 rurooy
“pooudn
Wi ving
wopuoy
ans premp3 Sup
‘Surpyng purmp3 fury
pry sumunon vaio as0g
seDaAg anuay woudopnag poz
P27 $193UNOD OYJ 350g,
POL00028100
POL00028100
y
AP 6.5 (H) Dave Miller to Cleared - Copy of Horizon Programme
issue a formal note to all Replan document dated 2 September has
concerned, giving key been supplied to the CAPS PMO who have
Horizon release dates. been asked to issue it to relevant parties.
AP 6.6 (H) Dave Miller to Ongoing - Dates currently being finalised.
provide Peter Crahan with I Expect to be available for Board meeting on
revised sign-off dates for all I 18 September.
acceptance specifications.
AP 6.7 (H) Dave Miller to Cleared - Details of implementation activity
arrange for Bruce McNiven I (including the issue of RGM letters) are
to provide Peter Crahan regularly provided (by ICL Pathway) to the
with a detailed breakdown I Horizon Implementation Board which Val
of the RGM letters Curran attends.
AP 6.8(H) Ongoing - Dave Miller liasing with POCL
Dave Miller to determine Finance Director regarding any assistance
the current state of debate _I required for resolution
between BES/PAS and see
if dialogue between
Horizon/CAPS directors
could be used to break the
apparent deadlock.
AP 6.9 (H) Dave Miller to Cleared - DIT2 closure report supplied to Les
provide the signed off DIT2 I Hodson (CAPS Testing Strand Manager) w/c
closure report 7 September.
C:\WINDOWS\TEMP\ CAPUPDTE.DOC
POL00028100
POL00028100
yet vign nen mans pa en J
m0
WI VID3
vopuey
spans puemp3 Suny
Suyping prempa Bury
pry su01Un0> 92410 3804
sopaag ame waudoping poy
px] suaquNED D21YO 380g
POL00028100
POL00028100
15 SEP °98 14:17 FROM BA-POCL PDA FELTHAM P.01/88
,
FACSIMILE
ba [dave MicLeR
—— nn
Soueé Guer
Fax Number: ' “GRO
Telephone Number:
From: I Seton kicor
Date: 15/09/98
Time:
Number of Pages: ig
(ncluding This One)
RESTRICTED COMMERCIAL
This fax transmission and any accompanying documents may contain information belonging to the sender which
is confidential and legally privileged. This information is intended only for the use of the individual or entity to
who this facsimile is addressed. If you are not the intended recipient, any disclosurc, copying, distribution or
action taken in reliance on the informstion contained herein is strictly prohibited. If you have received this
transmission in crror, please call the sender to arrange for the return of the documents.
he daewesed
15/09 '98 14:08 TX/RX NO. 1277 POL
POL00028100
POL00028100
—— -—-- —
15 SEP "98 14:17 FROM BA-POCL PDA FELTHAM T
12709 '98 FRI 15:44 FAX I. ICL PATHWAY PROG.
. IcL Now Release 2 Ref: are pes 3
Pathway elease Notice Version: 1.
more Dare: 9/9/98
Document Title: New Release 2 MOR2 Release Notice
Document Type: Definition Document
Abstract This document defines the software baseline for New
Release 2 MOR2.
Status: Issued
Distribution: John Meagher, Horizon, Simon Rilot, Horizon
Author/Editor: Simon Palladino, ICL Pathway Model Office Test
Manager
File Reference: PM/REN/002
Printed: 11/09/98 COMMERCIAL-IN-CONFIDENCE
Page 1
© 1998 ICL Pathway Led
15/09 ‘98 14:08 TX/RX NO. 1277 P02
POL00028100
POL00028100
————
1S SEP °98 14:18 FROM.BA-PNC..PDA FELTHAM TO
21/09 '98 FRI 15:44 Fax ICL PATHWAY PROG.
P.@3/08
icL New Release 2 ee Ref pe tie
Notice fersion: 1.
Pathway MORZ Release nasa
Introduction
This Release Notice defines the software baseline used for New Release 2 MOR2 and
identifies the set of known functional limitations associated with this baseline. The
limitations are grouped by Service below. No limitations have been added since the
MORI release notice and it is the intention to clear all limitations by MOR3.
The Baseline
The software baseline for MOR2 is referenced in the ICL Pathway change control
system as 9f incr 1.
Known Limitations
APS
* In the event of a printer problem, after printing the first APS receipt, the second
receipt (the office copy) cannot be reproduced for this transaction.
BPS
« Atreceipt printing time the system always prompts for an Authorisation To Pay
(ATP) receipt (even when it should request a normal encashment receipt).
* ifthe customer is a main beneficiary and an alternate payee, the system allows
collection as the alternate payee, but does not allow collection as the main
beneficiary.
* The EVP questions relating to the unique address question for No Fixed Abode are
not generated.
« The BES weekly encashment summary cannot be produced.
EPOSS
« If while attempting to print a Stock Unit (SU) balance report, you transfer the
session to another counter, then transfer it back and roll over the stock unit, alll the
stock in the stock unit will be lost.
© Stack entry help facility does not function correctly and an invalid tablet is
displayed.
¢ Bilingual receipt not produced at Welsh Post Office. Information has now been
provide by Horizon; this will be available at MOR3.
« Some keyboard function keys are not working correctly. They are however correct
on the touch screen.
TPS
« When reconciliation discussions between Pathway and Horizon conclude, we
expect a re-designed reconciliation to be delivered. Until that time issues in the
current design solution will remain unresolved. Discussions have now concluded
this issue will be resolved at MOR3
Printed: 11/09/98 COMMERCIAL-IN-CONFIDENCE
Page2
© 1998 ICL Pathway Led
11 SEP °96 15:@8 Pans
15/09 "98 14:08 TX/RX NO. 1277
om
@oos
POL00028100
POL00028100
——
15 SEP °98 14:18 FROM BAa-POCL PDA FELTHAM TOL. P.84/88
A1/U9 ‘98 PRI 15:44 Pat! H ACL PATHWAY PROG. DIR. oad
1cL New Release 2 Ref PM/REN/002
Version: 1.0
Pathway MOR2 Release Notice Sts
TRAINING MODE
« There are currently performance issues when ing between the desktop and
training mode. It is recommended that limited use is made of this feature in MOR2.
REFERENCE DATA
* The Model Office reference data still has issues outstanding. We are still validating
this data and expect to uncover further issues that will need resolution.
Reduced Limitations
¢ IfEVP fails during a carded casual agent transaction then the system only prompts
the clerk to retain one card. The prompt is still the same but the system now
impounds both cards making the second one,
© After using BES preview report the counter
le.
occasionally left with the task bar
showing on the screen. = an 7
Printed: 11/09/98. COMMERCIAL-IN-CONFIDENCE,
Page 3
© 1998 ICL Pathway Lud
11 SEP '98 15:06 PAGE.@4
15/09 ‘98 14:08 TX/RX NO. 1277 P04
POL00028100
POL00028100
15 SEP °98 14:19
11/03 '98 FRI 15:44 F,
11 «SEP ’96 1S:@8
PDA FELTHAM To
ICL PATAWAY PROG.
P.@5/88
Boos
IcL New Release 2
Pathway MOR2 Release Notice
Cleared Limitations
APS
* Session Mobility can cause duplicate APS receipt numbers.
¢ TIP cannot accept bulk input of AP transactions because of a reference data fault
which prevents this mode of operation.
BPS
+ An encashment transaction conducted by the Payment Card Help Line (CHL)
cannot be subsequently conducted in the Post Office. The Post Office is not
currently being updated by the PCHL system and, therefore, will not balance.
¢ Card activation by swiping does not function correctly. Card activation can be
achieved via the keyboard. Once activated via the keyboard all subsequent
transactions can be performed by using the card swipe.
* Benefit Payment Contingency functionality (i.e. payments to beneficiaries when
CAPS is down) does not function.
* The counter allows more than two foreign encashments within the 26 week limit.
¢ The EVP questions relating to 2™ line of address no longer relevant to Release 2.
* The counter does not recognise card batches as “activated” when they have been
actioned at the PCHL.
EPOSS
* Transferring stock between individuals within an outlet does not function.
» Suspense account tables are not being carried. forward across Cash Account
Periods.
* Ifa user is deleted whilst attached to an individual SU, SU rollover is prevented
and the Cash Account is not produced. It is advised not to delete users under these
circumstances.
¢ There remain a number of scenarios that lead to an imbalanced Cash Account
(CA). Refer to letter from Terry Austin to David Miller 10/09/98
Printed: 11/09/98 COMMERCIAL-IN-CONFIDENCE
Page 4
© 1998 ICL Pathway Lid
15/09 ‘98 14:08 TX/RX NO. 1277
POS
POL00028100
POL00028100
15 SEP *98 14:19 FROM. RA-POCL_PDA FELTHAM P.@6/08
44/43 39 FRA 19.49 FAA! AGL FALEWAY FRUG. DIK. goose
ee cL New Release 2 Ref
Pathway MOR2 Release Notice _— 1.0
MORI calls cleared in MOR2
PAS CMS
OBCS
MOR Maestro
[MORI
[MORI .RDDS
(ORI TPS
[MORI PAS CMS
PAS CMS.
IMORI APS.
IMORI APS _
IMORI PAS CMS migration
MOR! .RDMC
IMORI RODS
[MORI PAS CMS Migration
MORI PAS CMS
PAS CMS
{ORI RDMC
IMOR1_PAS CMS.
[MORI PAS CMS Mi
IMOR1 PAS CMS Migration
IMOR1 PAS CMS Migration
TPS
[MORI Check digit method for 29 and 38 have embedded space - Ref data
27. MOR] Missing post autoconfig batch files
28 [MORI POCL reference data does not coutein post codes -
SPPPPrEPRE
EISI@ 18/5 I>ISlaIaIe[s[s
RE
ye
IMORI Warehouse rds Siler unreadable
[MORI Build issues
Sposte user to adminiowaiors group on counters
[ORI The MIMAN tool available.
MORI Thcy are missing some local products from the reference data through the MIMAN migration tool.
is from leto
[MORI day 2 af testing, missing cash account lines, When catering data irom the manual cash account onto
ines on the correct tables on the Horizon System,
[MORI test day 2 eoript number 789-no core icons available but do not function, While reauting in from otha
PO's which was the supplies division or when in Serve Customer mode noa core items
[MORI test day 2 script number 789, Remittance af £3 phonccard hes uo effect, £699 of £3 phonecards were
permed in from another PO. Rem in lip produced. £0 pounce ceptayed on \adjust sock seen, stock wnit
{balance snapsbot
Printed: 11/09/98 COMMERCIAL-IN-CONFIDENCE
© 1998 ICL Pathway Lad
ii SEP ‘98 18:89
15/09 '98 14:08 TX/RX NO. 1277 P06
POL00028100
POL00028100
—- —
15 SEP °98 14:20 FI To P.07/88
11/09 '98 FRI 15:45 PAX AVL FALHWAY PRUG. DIK. wuurt
- icL New Release 2 Refi PM/REN/2
Pathway MORZ Release Notice Veasion: 1.0
—Date:_9/9/98_____
payment (ransactions not accepting account number. On entering BT bil] transaction there is no facility
enter the q
(E-9806110042 [MORI software Script number 00455, date 10/11/97 Unable to enter post cheque account number. On the
ECCO isa code which needs to be entered that is cithor one or two lemers
I47. 130045 [MORI Sys date .13/11/97 script 0693 Test Day 6, Saving certificare purchase invalid amount excepted, from
Ithe desktop selecting transaction (f1) then serve customer (f1) and then other products (13) and then giro
Puan (£3) and
48. IE-9808130064 [MORI , Sys date:13/11/97(has no time or Day no, or no scrip no)Counters: 1. Incorrect screen message
49. IE-980815000S [MORI Counter daily report - BT bill not displayed correctly. BT bill amount of £20,777.18 entered into
haMAN. £777.80. 14/31/97,
$0. _IB-9808150013 [MORI Redeemed electric stamps icon does not work. From Serve Customet/ Functions/ Settlement/ Electric
\scamp redeem (F14) When F14 pressed, screen flashes for half a scoond the retums 10 selemant screen I
Si. 150017 MORI The scale tariff incorrect. Prices are incorrect on Burope/Zone 1/Zone 2. NOTE: Have evidence at
Test Site for use. 14/11/97, Teme: 13. 15, Counters:2.
Isz._JE-5808170024 [MORI Sun Alliance icon’s description. The sun alliance screen displays 11 different icons that need further
Idescriotions. It is not cles: whaz icon represents what service. Some icons stez to be duplicated.
153. }5-9808170031 {MORI Description missing on ll offices a2MORI and R2 the description for le payments was missing from
(R2 counters. Sys date: 16/11/97.
FE-9808170032 IMORi V10/V62 icon not active. When icon is touched nothing happens. Date:13/11/97, Scritp:0753, Day:9,
{Counter:1.
55._[B-980817004] IMOR} Datapost icons not working. Following meng to non-accounting data. 3 icons marked datapost and
11, F12, 13 do not respond to touch. System Timer] 1.15, Date:13/11/97, Day:9, Seript:1080, Counters:1. I
[56.__IB-9808170044 IMORI Exrar message appears when printing weekly summaries. When producing the reports the printer starts
it print then 30 seconds Jeter as message appears on the screen advising printer error not responding ny again,
cancel,
[57._ IB-9808170052 {MORI . Wrong price for scales transection overseas surface. Serving custamer Input 312G international
surface letter price £6.21, the correct price is £2.27, the system reference data states £6.21. Date, 14/11/97,
[Day:10,
I58._IE-9608170055 [MORI Lewers pre-paid icon does not work, When touching lerters pre-paid icon nothing happens.
IDate:14/11/97, Day:19, Seript:0754. Counter:!.
1S9._IE-9808170057 IMOR1 Moncygram sead does not work. Touching the moneygram icon does not work. Date:14/11/97,
Day:10,Scripc0754, Counter: 1
[S0._IB-9808170062_{MORI - Sys date: 13/11/97 - day No: 9 - Script Number 0491. BT Phone card not active.
}E-9808170064 IMORI REM out cash/foreign currency stetling. Rem out cash to other post offices works ak, but there i¢no I
: con to rem out foreign currency sterling. Also after print out of a rem report system should go back to desktop,
st ‘nor remain on
(62. _]B-9808170092 IMORI Barcoder reader and APS reader failure on slave terminals. Able to swipe and scan cards and bercoded
: bilts om the Geceway but not on the slave txminals. Card NumsAPMOT060,....062...067...057,...285.
IMORI Unable to locate Southem Plectric Stamps. Atternpted to locate Southern Elee stamps under Local
Schemes menu & Savings Stamps menu, cannot use PLU number to locate either. 11/11/97, Day 7, Script
0430.
I64._IE-9808170106 IMORI - - Date: 17/11/97 - Day. 13 - Number of Counters: 3 - Seript Number: 0653 - National Saving
[Certificate Purchase (NSC) - NSC System allows Purchase of NSC for £80.00 mininnure should be £100.00.
JE-98081 70107 {MORI - - Date: 17/11/97 - Day: 13 - Number of Counters: 3 - Script Number: 0654 - Parcel services NO
ICONs Working.
\66._ IB-9808170123 Bie Oe Day no. 13, ie. ee ie oe eS
MORNE Des 1ST Dae Script 0735, ee
}gone into NS crossed warrants their is a prompt for account no. This not necessary NS products on current
S systems.
I68._ [E-9808180004 IMORI Unable to perfarm a lottery prize transaction. Tuken the Path desktop to transactions to serve custome:
he [to other products to !cigure the national lottery cheque prize ioon does not work. Sys date
(69. _IB-9808180006 eR ace ees eee BS Aes ese PSR oc nvm Oe
38 office the
“CAN x
© 1998 ICL Pathnway Lad
11 SEP *98 1S:a9
15/09 ‘98 14:08 TX/RX NO. 1277 P07
POL00028100
POL00028100
15 SEP °98 14:21 FROM BaA-PNC... PDA FELTHAM TO: P.@8/88
44708 98 FRI 19:46 FAL! ! ACL PALHWAY PROG. DIR. (doos
~ IcL New Release 2 - Ret PMRENMOO2 f
Pathway MOR2 Release Notice ‘Verlag 5.
Date: _ 9/9/98
[MORI Date 18/11/97 Day 14 soript no. 0524, Little prize icon not working, From leisure menu little woods I
[prize icon dacs not work
IMOR1 Date 18/11/97, Day 14, Script 0523, moneygrem receive icon does not work, Moneygram icon not
{MOR} Nor eccounting data icons malfunction. Data post icons not acted when pressed. Sys date:13/11/97,
{Time:10.54, Dey-9, Scrite-1080. Countes-2.
[MORI Cameiot vouchers icon not working. Camalot Fa voucber not working. Sys date-13/11/97, Time-
0: 1080,
1 MVL stamp redeemned. After completion of VIO/V62 transaction on settlement screen entered 10 for
quantity then touched F12 MVI. stamp redemption icon. nothing happened. Sys datc-17/1 1/97, Time-15.00,
JMOR1 OBCS book encashment. From the desktop to transactions to serve customer to scan boak. The book
Idetails are ( aud the last two digits on the books are now different,
177. {E-9808190035 RI TIP gateway
178. _{E-9808190039.
79. _{E-9808190041_IMORI CASHS sub file received
180. {E-9808200043 IMORI Unable to manually enter smaxt card on horizon. Serve customer local products, miscellaneous, system
[flashes but, i AS unable to enter smart card details APT and Horizon will not balance.
IE-980820005 i IR1 BARSS files received
12-9808200052 {MORI TIP files
E-9808200053_IMORI TIP files
I5-9808200056_IMORI TIP files
IE-9808200060_IMORJ FAD code mismatch
E-9808210038 {MORI file W_322012 rejected by tip because otran subfile for ORG unit 23576 contains records thet are not
jim “end time of transaction “ order, ie records out of sequence. Caller could give no system
JB-9808250001_IMOR] Many invalid
$3 I & [es 53]
Printed: 11/09/98 COMMERCIAL-IN-CONFIDENCE
Page?
© 1998 ICL. Pathway Led
44 coo 00 tesa a NS a
4k TOTAL PAGE.@8 4
15/09 ‘98 14:08 TX/RX NO. 1277 POs
POLO00028100
POL00028100
Lilley, June
I Lilley, June
To: Twidale, Mike
I Subject: RE; CAPS Board Report
Date: Friday, September 11, 1998 11:02
Priority: High
OK, this can be sent out
Thanks
E
for June Lilley
From: Twidale, Mike
To: Miller, Dave (Horizon)
Cc: Lilley, June
Subject: CAPS Board Report
Date: Friday, September 11, 1998 10:07
lattach copy of the Horizon input to the CAPS Board report for your clearance for issue today.
We have taken on board amendments arising from your meeting with Bob Burkin.
We are also pursuing the action point updates as agreed and will provide these when we have them.
Re Section 5.2 of the report (ie the BES/PAS boundary Issue) and the associated action - Roger Tabor is not
in the office until Monday. I have asked if he can confirm that the BES/PAS boundary issue is in hand, and
whether you and he need to discuss this further.
Please advise whether you are content for the report to be issued to CAPS.
<<File Attachment: CB1809.D0C>>
SAt Of
Page 1
POL00028100
POL00028100
Yan vina per maa pane Bet
‘ora nner] Re t>a0 PRAIA CoSVSIE
Ped parry 3 OBO mA
WI VIDa
wopuoy
ans purmpy Suny
2urpng premp3 Suny
pry suaiun05 92yjO 2504
sopang anuay waudepieg FoI
PY] susqUN0D D24J0 380d
7
POL00028100
POL00028100
fy ordi eo
Briefing Note Onts badd
ae
Host File System Failure
Background °.
The Host system is the main processing facility at the centre of the Pathway Horizon
system, i.e. the sequent server. ;
The Host runs CMS and PMS applications and takes data feeds from the CAPS
system.
The Host failure in question effectively stopped the data feed from CAPS, this did not
affect counter payments (Payment authorities had been sent down the day before and
distributed as normal).
This did however, prevent the Stops being sent through (these come through as they
happen and are sent at any time). _
In these circumstances the contingency procedure is for ICL Pathway to notify the
DSS of the incident and to implement a fall back process. This entails DSS faxing
stop details through the PCHL The PCHL then apply the stops onto the system
manually and these are then distributed to the outlet.
Events
¢ A failure occurred on the main host file systern (sequent) at 08.22 on the 11th June.
© The situation was retumed to normal by 22.15 on the 11th June.
¢ All the subsequent overnight processing was successful.
© Following similar instances at 12.15 on Saturday 13th June and the moming of the
24th (where again impact on the service was very limited) two sequent boards were
replaced. :
Impacts
“ e During the day CAPS files could not be processed.
¢ No impact upon customers at the Post Office counter because payment authorities
are transmitted 72 hours in advance.
¢ All payment stops were implemented via the Payment Card Helpline and no over
payment arose.
POCL Service Management 1 24/08/98
POL00028100
POL00028100
Further Action
* ¢ No further service breaks have occurred and close monitoring of the host file
system is in place.
" Incident discussed at the Horizon Review Forum, and logged i in the Pathway
Release 1C Operations Report
POCL Service Management 2 24/08/98
addressed’.
The three outstanding issues with TA have been agreed and the
documentation is expected today or tomorrow. It is expected to be
incorporated into MOR3 but CW would specifically confirm this.
POL00028100
POL00028100
JM
15 Sept
DD
‘14% Sept
Checkpoint Meeting No 26
0930-1130 Tuesday September 8” 1998
- : ICL Board Room
Feltham
Attendees
Mike Coombs ICL Pathway MC
Peter Jeram ICL Pathway Py
Graham Chatten ICL Pathway Gc
Chris Wannell ICL Pathway cw
Dave Miller POCL Chair DM
Andrew Simpkins POCL AS
Rod Stocker POCL Secretary RS
John Meagher POCL JM
Don Docherty POCL DD
Bruce McNiven POCL BMcN
Naresh Mohindra POCL NM
Apologies .
Terry Austin ICL Pathway TA
Janet Topham - POCL yt
Simon Rilot POCL SR
» Andy Radka POCL AR
Notes
1 Review/Acceptance Previous Minutes
1.1 JMnoted that there was an action missing from the previous minutes (recorded below as action
2511).
2 Actions from Previous Meeting
2.1 Allactions cleared as stated in briefing paper except for the following:
Action ‘To ensure that John Dicks, Pathway responds on the Acceptance Scoping
2312 Report with comments, actions and recommendations’. JM will speak to
John Dicks to help progress this action.
JM said that John Dicks has replied to the framework but not to the
scoping study. JM said that he was following up with John Dicks. Action
ongoing.
Action ‘To define for PJ what information needed to be included in the MOR
2404 reports’,
SR is still following up with PJ. Since SR is on holiday until next Monday
(14/9) it was agreed that DD would follow up to resolve before start of
MOR2. It was noted that the basis already exists.
Action ‘To ensure that the agreed principles for “reconciliation in BES fallback” is
2415 fully documented and signed up to and that all the outstanding issues are
10% Sept
Ref Chkpnt26 Commercial in Confidence Page 1 of 9
Action
2503
Action
2506
Action
2507
Action
2508
Action
2510
Action -
2511
Action
2601
3
3a I
3.2
Action
2602
Ref Chkpnt26 Commercial in Confidence Page 2 of 9
JM to arrange a joint (Horizon, Ref Data and TIP with Pathway present)
meeting / forum to ensure all are focused on resolving issues arising from
testing.
Action ongoing. An update will be provided at the next Checkpoint
meeting.
John Dicks to provide John Meagher with details as to wherein the testing
life cycle the various tests to be witnessed would take place.
JM has reached an agreement in principle with John Dicks and this has
been documented and sent to John copy to MC. It will in fact be available
for MOR3. MC has not yet received the email but will follow up with
John Dicks to ensure a response is sent.
TA to confirm when all the User Guides will be available.
Action Closed. CW confirmed that the User Guides would be available for
MOR2 (those not available at the start have an agreed availability date).
See further action 2601.
The possibility of an automatic confirmation of delivery of the Checkpoint
pack would be investigated.
Action Closed. Tests had been conducted successfully but problems are
still experienced with “blockages” within mail servers. An oral check will
be made first thing each Monday morning in future to confirm receipt by
Pathway.
JM to arrange for latest TIP plans to be provided to Pathway.
The ‘Ready for Testing’ date for Operational TIP is forecast for 5/4/99 with
a Go-live date of 11/10/99. Lower level dates are required by Pathway so
the action is carried forward.
‘To explore the potential for protecting data transferred from Reference
Data during live running with a view to de-risk the possibility of data
corruption.
JM is producing Terms of Reference to give to TA today. Action ongoing to
report progress at the next Checkpoint meeting,
Actions arising from review
To provide a list of all User Guides and the dates when they will be
available for MOR2.
Pathway Progress Report
GC reported that the new v5 Pathway plan is nearing completion and will
now be available to issue on 14" Sept. The delay has been due to re-jigging
the systems Test to accommodate MOR3. MC said that he would like to agree
the dates for Acceptance (see action 2312) to include in the plan.
GC confirmed that MOR1 had completed on schedule and that a closure
report is due this week. GC said that Build 9F for MOR2 was completed at the
end of last week. System.test activities are continuing and the MOR3 build
will be available to start formal acceptance testing on 1* Oct (though the
EPOSS main pass cycle 3 is targeted to restart to intercept the MOR3 build a
week earlier on 23" Sept).
AS said that Horizon needs a better understanding of the builds, incremental
changes and configuration management during the period of October and
November so that there is a common understanding of how to de-risk ©
MOR3/MOT from incomplete systems testing particularly with EPOSS.
To set up a presentation next week (week beginning 14 Sept) to provide
an overview of the build control, incremental updates and their
relationship with the various testing phases.
POL00028100
POL00028100
JM
22n4 Sept
MC
15" Sept
TA
8th Sept
AS
84 Sept
JM
11" Sept
JM
22n4 Sept
cw
10% Sept
cw
10 Sept
POL00028100
POL00028100
33
34
3.5
Action
2603
Action
2604
42
Action
2605
Action
2606
43
Action
2607
44
GC said that problems had been experienced with E2E testing with HAPS
and TIP and that these were being addressed. DD noted that there isa
review tomorrow with CAPS, POCL, Pathway and Horizon to review E2E in
particular to look at MOR2 readiness, need to include migration, alignment to
baseline, proactive rescheduling to realign and terminating E2E cycle 1 earlier
than previously planned. He added that there had been problems up until
last Friday but that good progress has been made since.
MC noted that the Implementation figures quoted in Pathway’ 's report were
~ now out of date and the position as at this morning is:
3424 RGM letters issued
71 MIB events run
2937 MIB attendees
1441 surveys scheduled
825 surveys completed
. © 270 re-surveys scheduled
The reason for the difference is down to time lags though the process is in
place. DM stated that it was important to have an up to date picture for these
meetings.
Following a question from DD, GC promised to check on the position with
regard to 3" Party testing.
To talk to John Wooler and ascertain the position with regard to the HLTP Gc
for 3" Party testing in order to brief DD. 114 Sept
Horizon Progress Report
MC expressed concern that CAPS are not prepared to formally state what is
in their Release 3.5, 4.0 and 4.1. Prior to yesterday he had not been aware of
release 4.1. He said that Parry Jenkins had stated at the meeting last week that
on-line enquires would not be available in 3.5 yet AS believes that it is
included. He added that this presented a risk to the viability of Pathway’s
plans.
To obtain a formal definitive statement from CAPS as to what AS
functionality is to be included in Release 3.5, 4.0 and 4.1. 16% Sept
AS handed out copies of the Horizon Level0 plan which has been sent to
Horizon Management and CAPS, Pathway now need time to assess this
against the Pathway Level 1 v5 plan before meeting next week to co-ordinate
the two plans,
To co-ordinate the replies from Pathway on the Horizon Level0 plan and Py
forward to AS. 14% Sept
To arrange to meet week beginning 14'' Sept to co-ordinate the Pathway AS/GC
Level1 v5 plan and Horizon Level plan and to incorporate all factors 11" Sept
discussed to date into the Master plan.
BMcN confirmed that he had seen a demo of MiMan which was fine. They
were now looking at how the mapping could be improved to ease the
process. CW said that it was possible to accept a new mapping table but that
the code was now frozen so changes, other than to the mapping table, were
not possible,
To investigate the sort of changes that need to be made to the mapping in BMcN
order therefore to improve and ease the migration process. ‘15 Sept
RS noted that although a response to the 9 MiEcco issues had been received
by Horizon, four of them appeared not to have been answered. RS promised
to provide details. :
Ref Chkpnt26 Commercial in Confidence Page 3 of 9
POL00028100
POL00028100
Action To provide CW with details about the four outstanding issues‘on the RS
2608 MiEcco clarification points. 8th Sept
[After the meeting RS confirmed that his statement was incorrect; there
were in fact only 2 issues. One of these had already been answered, the text
having been buried in the middle of another answer, and the second was a
contractual issue regarding timing which is being addressed separately.
Action Closed].
45 AS noted that he is proposing to organise a workshop on Live Trial in the
week beginning 21* Sept. MC said that he would like to attend and was
available on 21* and 22"4 Sept.
4.6 BMeN said that there are concerns as to whether the necessary changes to
Training could be incorporated in time. A meeting had been organised for
this Friday 11'* Sept to address the concerns.
Action To provide an update at the next Checkpoint on the concerns about the BMcN
2609 preparedness of Training. 22"4 Sept
47 MC said that there.is an internal Pathway meeting this afternoon to discuss -
the NR2+ plans and it was hoped to have a plan in place by end Sept.
However it was necessary to understand the CAPS and TIP plans (see actions
2604 and 2510). It was agreed that there is a need for Horizon and Pathway to
meet during week beginning 21* Sept to discuss.
Action To organise to meet during week beginning 21* Sept to discuss the plans AS/MC
2610 for NR2+. 15% Sept
5° Review Testing Progress
51 DD confirmed that MOR] had been successfully completed including
migration and running an NR2 outlet through a 1c Data Centre. PJ confirmed
that MOR1 and MOR2 are run on Pentium I whereas MOR3 will be run on
Pentium II. The Release notice for MOR2 would be available at the end of this
week. °
Action To send the Release Notice for MOR2 to JM on 11" Sept for JM to Py
2611 distribute to Horizon staff. 11 Sept
5.2 PJ confirmed that CAPS have stated that they will not be utilising Temporary
Tokens or Emergency payments in NR2 but that they will be supporting
Urgent Stops. .
5.3 JM said that it would be helpful to have reports about security, resilience and
performance included in Pathway’s future Checkpoint reports. He also added
that it would help to have a status report on ‘Acceptance Specifications and
acceptance testing. A status report was handed out at the meeting.
Action To include progress reports on security, resilience and performance, Gc
2612 Acceptance Specifications and Acceptance testing in future Checkpoint 2284 Sept
reports. ; ongoing
5.4 MC said that it was too early to form any view or prognosis on the likelihood”
of completing MOT and E2E on 18% December. Nevertheless, DM said that it
was important that realistic reports were provided to CAPS and that he
needed an update by next Thursday before he attends the CAPS Board on the
Friday.
Action To provide an update on testing progress in particular covering the Py
2613 preparedness of MOR3 and the shape of E2E to DM by 1800 hours 17 174 Sept
Sept. '
54 It was agreed that there is a need to review the status of testing and prognosis
on completion at the next Checkpoint. ;
Action To review at the next Checkpoint the status of testing and prognosis on AS
2614 likelihood to complete MOT and E2E by 18 December. 224 Sept
Ref Chkpnt26 Commercial in Confidence Page 4 of 9
POL00028100
POL00028100
5.5 JM said that he was expecting detailed plans today from John Dicks
concerning the proposals for Acceptance Testing. MC asked that this be
monitored today. :
Action To check today that the level of planning promised by John Dicks to JM JM/GC
2615 for next Monday is as expected byJM. 8th Sept
6 Review of Milestones
61 No further discussions.
Review of Issues
71 BMcN confirmed that he had met with MC and Barrie Davies to discuss
migration and that he had been promised information this Thursday before a
further meeting arranged for Friday 11'* Sept.
7.2 NM noted that the owner for Acceptance in the Key Decisions was now JM.
73 BMcN confirmed that he has submitted a paper to Pathway on the trigger
points and ramp up of the National Rollout. MC said that they were
reviewing the paper.
74 DM asked to be updated on the issue regarding BES/PAS boundary before
the CAPS Board.
Action To.update DM on the status of the issue regarding BES/PAS boundary JM
2616 before the next CAPS Board on 18! Sept 17 Sept
8 Release Authorisation proposal
81 NM presented an overview and handed out copies of his slides.
8.2 It was noted that there is a need to identify risks, regression points and
“points of no return” in the release process.
8.3 It was acknowledged that the Release Authorisation was owned by Horizon
(DM in particular) although it was recognised that there would be separate
reviews within Pathway, CAPS, POCL and probably Horizon.
84 It was noted that the criteria setting should also include Implementation,
security and performance and BA Seals of Approval (SoA).
Action - To formally register, at the CAPS Board next week, the need for SoA for DM
2617 NR2 recognising that this is a non CAPS release. The SoA needs to cover 18tk Sept
the number of offices and Cards proposed to be rolled out for Live Trial.
85 It was recognised that there is a need to identify the lower level detail in the
release process. As part of this it was felt that a regular review separate from
the Checkpoint meetings would be beneficial.
Action . To consider regular Release Management meetings between Pathway and NM
2618 Horizon to monitor the progress on Release Authorisation. 2204 Sept
8.6 The discussion on release authorisation prompted two further actions.
Action To determine whether the Procedural “walkthrough” proposed is a NM
2619 tri-partite arrangement or not. 22n4 Sept
Action To ask Keith Baines to ensure that the BA plans to trigger the cessation of AS.
2620 ChB Order Books and the issue of Cards is known bearing in mind the BA; 11'* Sept
lead time on this process and it’s impact on the Card Volumes. These ‘
discussions to recognise the need to increase the number of offices to 300
in early February 1999 with a corresponding increase in the number of
Cards that would be expected at that time.
Ref Chkpnt26 Commercial in Confidence Page 5 of 9 -.
POL00028100
POL00028100
9 Any Other Business
91 None
10 _Date of Next Meeting
Tuesday 224 September 0930-1130 at ICL Feltham
Ref Chkpnt26 Commercial in Confidence Page 6 of 9
POL00028100
POL00028100
Summary of Actions
Action
2312
Action
* 2404
Action
2415
Action
Action
2506
Action
2507
Action
2508
Action
2510
Ref Chkpnt26 Commercial in Confidence Page 7 of 9
‘To ensure that John Dicks, Pathway responds on the Acceptance
Scoping Report with comments, actions and recommendations’. JM will
speak to John Dicks to help progress this action.
JM said that John Dicks has replied to the framework but not to the
scoping study. JM said that he was following up with John Dicks.
Action ongoing.
‘To define for PJ what information needed to be included in the MOR
reports’,
SR is still following up with PJ. Since SR is on holiday until next
Monday (14/9) it was agreed that DD would follow up to resolve before
start of MOR2. It was noted that the basis already exists.
‘To ensure that the agreed principles for “reconciliation in BES
fallback” is fully documented and signed up to and that all the
outstanding issues are addressed’.
The three outstanding issues with TA have been agreed and the
documentation is expected today or tomorrow. It is expected to be
incorporated into MOR3 but CW would specifically confirm this.
JM to arrange a joint (Horizon, Ref Data and TIP with Pathway present) _
meeting / forum to ensure all are focused on resolving issués arising
from testing. -
Action ongoing. An update will be provided at the next Checkpoint
meeting.
John Dicks to provide John Meagher with details as to where in the
testing life cycle the various tests to be witnessed would take place.
JM has reached an agreement in principle with John Dicks and this has
been documented and sent to John copy to MC. It will in fact be
available for MOR3. MC has not yet received the email but will follow
up with John Dicks to ensure a response is sent.
TA to confirm when all the User Guides will be available.
Action Closed. CW confirmed that the User Guides would be available
for MOR2 (those not available at the start have an agreed availability
date). See further action 2601.
The possibility of an automatic confirmation of delivery of the
Checkpoint pack would be investigated.
Action Closed. Tests had been conducted successfully but problems are
still experienced with “blockages” within mail servers. An oral check
~ will be made first thing each Monday morning in future to confirm
receipt by Pathway.
JM to arrange for latest TIP plans to be provided to Pathway.
The ‘Ready for Testing’ date for Operational TIP is forecast for 5/4/99
with a Go-live date of 11/10/99. Lower level dates are required by
Pathway so the action is carried forward.
JM
‘15th Sept
_ DD
14th Sept
cw
10th Sept
JM
22nd Sept
MC
15th Sept
TA
8th Sept
AS
8th Sept
JM
‘ith Sept
POL00028100
POL00028100
Action To explore the potential for protecting data transferred from Reference JM
2511 Data during live running with a view to de-risk the possibility of data 22nd Sept
corruption.
JM is producing Terms of Reference to give to TA today. Action
ongoing to report progress at the next Checkpoint meeting.
Action To provide a list of all User Guides and the dates when they will be cw
2601 available for MOR2. 10th Sept
Action Tosetupa presentation next week (week beginning 14th Sept) to cw
2602 provide an overview of the build control, incremental pdates and their 10th Sept
relationship with the various testing phases. z
Action To talk to John Wooler and ascertain the position with regard to the Gc
2603 HLTP for 3rd Party testing in order to brief DD. T1th Sept
Action To obtain a formal definitive statement from CAPS as to what AS
2604 functionality is to be included in Release 3.5, 4.0 and 4.1. 16th Sept
Action To co-ordinate the replies from Pathway on the Horizon Level0 plan Py
2605 and forward to AS. 14th Sept
Action To arrange to meet week beginning 14th Sept to co-ordinate the — AS/GC
2606 Pathway Level v5 plan and Horizon Level0 plan and to incorporate all ‘11th Sept
factors discussed to date into the Master plan.
Action To investigate the sort of changes that need to be made to the mapping BMcN
2607 in order therefore to improve and ease the migration process. 15th Sept
Action To provide CW with details about the four outstanding issues on the RS
2608 MiEcco clarification points. + 8th Sept
[After the meeting RS confirmed that his statement was incorrect; there
were in fact only 2 issues. One of these had already been answered, the
text having been buried in the middle of another answer, and the
second was a contractual issue regarding timing which is being
addressed separately. Action Closed].
Action To provide an update at the next Checkpoint on the concerns about the BMcN
2609 preparedness of Training. 22nd Sept
Action To organise to meet during week beginning 21st Sept to discuss the AS/MC
2610 plans for NR2+. 15th Sept
Action To send the Release Notice for MOR2 to mM on 1th Sept for JM to r
2611 distribute to Horizon staff. 11th Sept
Action To include progress reports on security, resilience and performance, Gc
2612 Acceptance Specifications and Acceptance testing in future Checkpoint 22nd Sept
Feports. ongoing
Action To provide an update on testing progress in particular covering the ry
2613 preparedness of MOR3 and the shape of E2E to DM by 1800 hours 17th 17th Sept
Sept.
Ref Chkpnt26 Commercial in Confidence Page 8 of 9
POL00028100
POL00028100
Action To review at the next Checkpoint the status of testing and prognosis on AS
2614 likelihood to complete MOT and E2E by 18th December. 22nd Sept
Action _ To check today that the level of planning promised by John Dicks to JM/GC
2615 JM for next Monday is as expected by JM. 8th Sept
Action To update DM on the status of the issue regarding BES/PAS boundary JM
2616 before the next CAPS Board on 18th Sept 17th Sept
Action To formally register, at the CAPS Board next week, the need for SoA for DM
2617 NR2 recognising that this is a non CAPS release. The SoA needs to 18th Sept
cover the number of offices and Cards proposed to be rolled out for
Live Trial.
Action To consider regular Release Management meetings between Pathway NM
2618 and Horizon to monitor the progress on Release Authorisation. 22nd Sept
Action To determine whether the Procedural “walkthrough” proposed is a NM
2619 tri-partite arrangement or not. 22nd Sept
Action To ask Keith Baines to ensure that the BA plans to trigger the cessation AS
2620 of ChB Order Books and the issue of Cards is known bearing in mind Ith Sept
Ref Chkpnt26 ql Commercial in Confidence Page 9 of 9
the BA lead time on this process and it’s impact on the Card Volumes.
These discussions to recognise the need to increase the number of
offices to 300 in early February 1999 with a corresponding increase in
the number of Cards that would be expected at that time.
POL00028100
POL00028100
¥, Oech porate
(P@(rNVie
. : APD 267,
Miller, Dave (Horizon) 14_SEP_1998
From: . Stocker, Rod [
To: "Miller, Bave (Horizon) beau
Subject: Checkpoint notes
Date: 11 September 1998 09:37
Please note that Peter Crahan di not receive the Notes from the Cehckpoint meeting due to technical
problems at their end. Andrew wanted to amend them slightly so a revised version is attached. Please
replace your earlier version.
ROD
< <File Attachment: CHKBA26.DOC> >
en bug I
—_
Rare
POL00028100
POL00028100
aoans purp3 2p)
Buping puempg Zupy :
~ pr sioiunoD v2yI6 280g."
sepang amie woudepaiag poy
P27 S49IUNOD 921J0 350d
POL00028100
POL00028100
Checkpoint Meeting No 26
0930-1130 Tuesday September 8" 1998
ICL Board Room
Feltham
Notes
1. Horizon have reached an agreement in principle with Pathway regarding the witnessing of
the Acceptance tests which will coincide with MOR3. Supporting documentation on the
agreement is awaited,
2. Pathway confirmed that the User Guides would be available for MOR2.
3. Ithas been agreed that Horizon and Pathway will explore the potential for protecting data
transferred from POCL Reference Data during live running with a view to de-risk the
Possibility of data corruption.
4, Pathway reported that the new v5 Pathway plan is nearing completion and will now be
available to issue on 14” September. The delay has been due to re-jigging the systems
Test to accommodate MOR3.
5. Pathway confirmed that MOR1 had completed ahead of schedule, including migration and
running an NR2 outlet through a 1c Data Centre, and that a closure report is due this
week. They confirmed that Build 9F for MOR2 was completed at the end of last week.
6. Horizon and Pathway reported that problems had been experienced with E2E testing but
that these have been addressed and good progress has been made since last Friday. E2E
is now bedding down into day to day running and the necessary script proving is taking
place. There is a review tomorrow with CAPS, POCL, Pathway and Horizon to review
testing progress. This will look at MOR2 readiness and the outlook for completing the first
cycle of E2E. A number of options will be considered to improve the efficiency of the E2E
testing including how some of the migration tests could be better executed (e.g. by moving
into MOR).
7. Pathway said that it was too early to form a definite view on completing MOT and E2E on
18" December though progress was good to date and early indications are encouraging,
despite the problems in E2E.
8. Pathway confirmed the position with regard to the Implementation figures:
© 3424 RGM letters issued
71 MIB events run
2937 MIB attendees
1441 surveys scheduled
825 surveys completed
270 re-surveys scheduled
eeeee
9, Pathway confirmed that there is an internal meeting this afternoon to discuss the NR2+
plans and it was hoped to have a plan in place by end September. Pathway expressed
concern that CAPS are not yet prepared to formally state what is in their Release 3.5, 4.0
and 4.1. Prior to yesterday they had not been aware of release 4.1. There is still
uncertainty as to whether on-line enquires will be available in 3.5. These uncertainties
presented a risk to the viability of Pathway’s plans to support the multi-benefit phase and
NR2+.
10.Horizon handed out copies of their Level0 plan which has been sent to Horizon
Management and CAPS, Pathway will review this against the Pathway Level 1 v5 plan
before meeting next week to co-ordinate plans.
11.Horizon confirmed that they had seen a demo of the MiMan tool which was satisfactory.
Horizon are now looking at how the mapping could be improved to ease the migration
process.
12.Horizon said that there are concerns as to how the necessary changes to Training could
be incorporated and that there is a meeting with Pathway this Friday 11"Sept to address
the concerns.
Ref Chkba26.doc Commercial in Confidence Page 1 of 2
POL00028100
POL00028100
EE I
Ye v191 wpe ws papa Be
‘Bere pane Re 790 PeaEdNE STIL, U
nada pamadng yr a) OO A
apang putmp3 3uyy
Burpung premp3 Buy
x7 su01un0D 92410 3804
sepIAg aD wouxdopisg pry
P37] S493UN0D 92440 350g
POL00028100
POL00028100
13.It was confirmed that CAPS have stated that they will not be utilising Temporary Tokens or
Emergency payments in NR2 Child Benefit but that they will be supporting Urgent Stops.
14.Meetings between Horizon and Pathway to discuss the in-office migration had taken place
and a further meeting was arranged for Friday 11" Sept.
. 15.Horizon have submitted a paper to Pathway on the trigger points and ramp up of the
National Rollout which Pathway are now reviewing.
16.Horizon presented an overview of the Release Authorisation process.
17.Itwas acknowledged that the Release Authorisation was owned by Dave Miller in Horizon
although it was recognised that there would be separate reviews within Pathway,
BA/CAPS, POCL and probably Horizon.
18.It was noted that the criteria setting should also include Implementation, security and
performance and BA Seals of Approval (SoA). It was noted that the SoA needs to cover
the number of offices and Cards proposed to be rolled out for Live Trial.
19.Horizon accepted an action to ensure that the BA plans to trigger the cessation of Child
Benefit Order Books and the issue of Cards is agreed, bearing in mind the BA lead time on
this process and it’s impact on the Card Volumes. This needs to recognise the need to
increase the number of offices to 300 in early February 1999 with a corresponding
increase in the number of Cards that would be expected at that time.
Ref Chkba26.doc Commercial in Confidence Page 2 of 2
POL00028100
POL00028100
Yin vin pan maa pang Ro
Sowa nano Bawa pean
‘Supang paempy Zupy
Pr] sua1UNED 99410 2804
seman awa waudopieg FoITy
P37 S103UN0D 921j0 350g
POL00028100
POL00028100
90 EHE ~- RELEASE i
The Baseline
The software baseline for MOR] is referenced in the ICL Pathway change control system as 9f incr 1 MOR iner 1.
K Limitati
Ref - Limitation (from Pathway MORI Release Notice PM/REN/002 1.0) : 2 Status Target Release Impact
APS
1 e Inthe event of a printer problem, after printing the first APS Awaiting fix from _MOR3 Medium -
receipt, the second receipt (the office copy) cannot be reproduced for Escher relatively fow tests
this transaction. are impacted but it
would be release
threatening if not
fixed.
BPS
2 e The BES weekly encashment summary cannot be produced. Fix available MOR3 Medium -
daily summaries
can be used for
MOR2 but as this
is more time
consuming we do
not wish to,
encourage this in
live environment.
POL00028100
POL00028100
Ref. Limitation (front Pathway MORI Release Notice PM/REN/O02 1.0). :. ~~ Status.” “Target Release. Tinpact
3 e Atreceipt printing time the system always prompts for an Fix available MOR3 Low -
Authorisation To Pay (ATP) receipt (even when it should request a
; stem prints th
normal encashment receipt). Sy: prints the
correct information
in the right place.
ATP is only I
available if ‘
presented by
customer.
4 e Ifthe customer is a main beneficiary and an alternate payee, the Fix available MOR3 Medium - 4
system allows collection as the alternate payee, but does not allow ‘
collection as the main beneficiary. During single ; \ i
benefit operational
trial there will be
few , ifany,
customers who are
both a beneficiary
and an alternative
Payee for CHB.
5 e The EVP questions relating to the unique address question forNo Fix available MOR3 Low - It is not
_ Fixed Abode are not generated. expected that there
will be many, if
any, NFA’s during \
single benefit
operational trial ‘
and other \
questions are
available.
=
POL00028100
POL00028100
sf - Limitation (from Pathivay MORI Release Notice PM/REN/002 1.0):° ° = Status Target Release . “Impact -°".*
EPOSS
e If, while attempting.to print a Stock Unit (SU) balance report, you Fix available MOR3 Low -
_ transfer the session to another counter, then transfer it back and roll This is a rare
over the SU, all the stock in the SU will be lost. exception
condition.
¢ Stack entry help facility does not function correctly and an invalid Fix available MOR3 Low -
tablet is displayed. : Help is available
clerically from
User Guides.
¢ Bilingual receipt not produced at Welsh Post Office. Translations have now MOR3 Low
been provided by
Horizon and will be
coded for MOR3
e Somekeyboard function keys are not working correctly. They are Fix available MOR3 Medium -
however correct on the touch screen. Cannot start
assessing MMI
aspects if keyboard
functions are not
working.
POL00028100
POL00028100
Ref ™ Limitation (from Pathway MORI:Releas¢ Notice PM/REN/002 1.0) Status: .- 2-0 "Parget Release Impact: :”
10 © When reconciliation discussions between Pathway and Horizon Under development, MOR3 Medium -
conclude, we expect a re-designed reconciliation to be delivered. following agreement of This has minimal
Until that time issues in the current design solution will remain BES fallback
nde effect on BA as
unresolved. reconciliation CAPS stream is
functionality. Expect tentibeted, Indow
to pass through ST and torarenmene bnawe
etry fore entering relatively high
impact on TIP who
are unable to test a
major part of their
reconciliation
“process.
TRAINING MODE
11. e +There are currently performance issues when transferring between Fix available . MOR3 Low
the desktop and training mode. It is recommended that limited use is
made of this feature in MOR2.
EFERENCE
12 © The Model Office reference data still has issues outstanding. We Reference Data issues. _MOR3 Medium/High
are still validating this data and expect to uncover further issues that
will need resolution. :
POL00028100
POL00028100
I Horizon Test Team Daily Report End to End - Pass 1
Daily Report for E2E1 - Day 26 & 27 - 15"" September 1998
Management Summary
¢ Testing consisted of rolling the systems forward two days, as no counter activity was planned. This
activity was essential to claw back some of the time lost earlier in the cycle.
© OBCS reported an incident via the Helpdesk, but were advised to report the problem direct to
Pathway for analysis prior to a PinICL being raised.
© There is now an opportunity to complete the counter activity for the cycle by Sunday 20/9, this
however will include performing BES Contingency Recovery over the weekend. The future of this
cycle will be discussed at a mecting today (16/9) which will be attended by representatives of
participating system areas,
¢ The outstanding PinICLs for E2E have been collated by Pathway, and including relevant duplicates
~ of MORI PinICLs there are a total of 45 (B=20, C=23 D=2).
Main Report
Planned Activity For Day
No counter activity for the day. Pathway were active in advancing the system from Day 25 to the start
of Day 28, in order to gain 1 physical day.
Actual Activity for Day
As planned.
Script Metrics
The table below reports results on the complete E2E1 cycle;
Description 7 Current Day Summary of All Days
Planned Scripts Nil 3187
Scripts Passed Nil 1738
Scripts Failed * Nil 594
Scripts Not Run ** Nil 855
Totals Nil 3187
* Scripts failed includes transactions which are unavailable at present, hence the large number.
** Scripts not run includes scripts which, due to catching up test days on offices which had problems
some of the scripts were cither not necessary or pulled out to enable the day to be complete.
Incidents Raised Yesterday
The following table details the incidents raised yesterday
PinICLNo. Description Priority
c:\windows\ temp\e2150998.doc 17/09/98 Page 1 of 2
POL00028100
POL00028100
Horizon Test Team Daily Report ~ End to End - Pass 1
Incidents Closed Yesterday
The following PinICLs were closed yesterday;
PinICL No. .IDescription Priority \Latest
Summary Of Open Incidents
The following table summarises all incidents raised during E2E 1;
Priority-A. Priority B «Priority C_ a Total
Incidents raised - Loe - -
yesterday
Incidents closed - - - 7
yesterday...
Total Open ‘- 20 23 2
Incidents ~ :
Total Closed : - - -
Incident
This table will be fully populated in future reports. Today’s report is a result of changing report
formats, .
c:\windows\ temp\e2150998.doc 17/09/98 é Page 2 of 2
POL00028100
POL00028100
Horizon Test Team Daily Log Model Office Rehearsal-2
Daily Progress Report for MOR2 - Day -2 - 15" September
1998
Management Summary
« After the resolution of several minor problems, the-Release 1c counter environments were
successfully set-up .
© CAPS received transmissions from Feeder: Benefit Systems and continued on-line and batch
processing
Planned Activity For Day
CAPS continue on-line and batch processing.
Pathway. to continue restoration and realignment of networks/servers/comms. This includes both
Release 2.0 and Release 1c environments
POCL Reference Data to provide first drop of planned data changes to Pathway
OBCS pass initial stoplist file to Pathway
Counter training begins
Actual Activity for Day
As planned, with the following additions;
© The 3 Release Ic test configurations were successfully set-up.
* HAPS completed APT polling initiating
The following planned activity was not completed;
« Although keyed by POCL RDP, the planned Reference Data change drop was not passed to ©
Pathway
Several minor software/hardware problems within the counter environment were encountered and
rectified, This included the reseating of CPU Hard disks, resetting of ISDN CHAP passwords, local
amendment of system date, and the restoration of an incomplete message store,
One incident was raised when a network card was found to be faulty.
Script Metrics -
None planned
_Incidents Raised Yesterday
The following call was raised at the Horizon test site
Call Ref Description Priority
1E9809150060 ISpecial X Network Card not functioning B
Incidents Closed Yesterday
-None
c:\windows\ temp\mo980915.doc 17/09/98 Page 1 of 2
POL00028100
POL00028100
Bee a
Horizon Test Team Daily Log Model Office Rehearsal 2
Summary Of Open Incidents
The following table summarises all incidents raised at the Horizon Test Site during MOR 2
Priority A Priority B -Priority C Total
Incident raised ) 1 0 1
yesterday
Incidents - 0 0 0 0
closed -
yesterday
TotalOpen - [') 1 0 41
Incidents
Total Closed 0 0 0 0
Incident _
]
I
I
I
I c:\windows\ temp\mo980915.doc 17/09/98 Page 2 of 2
POL00028100
POL00028100
BIRD & BIRD.
Stica Bet ae
_Caes Cheuienicueca’ op
Owe fein ag es “tad “Gadi dake eta
Wadasite : od inmates IS
CHE apecad whe Loot Gk
; Malet tei.
@) (ok oabsbintices piadiy — 90 fk A
A spare .
20% Hee {Ite swabs, pcan d ones. ;
100% Hace alice panna Bee sengh :
(0) Im:
)
POL00028100
POL00028100
BIRD & BIRD
Nee Premsce Zo hesflar's brews
Tig ea aaa & Aakenredh col NE =
rd Shed,
Assmg te ihn CER pin
Prana foe [rcs ene
Z.- fREPALATionN SRGE.
Vet ta he atnnd of “orerne’d ,
————
‘ lee Gomh a S wrtence « Str TA BIT ELE:
tedivnrcall [cecwts, bth Mats/ mo
od
eee
—# hes ea fos
“hy Irdeadanet OCI.
POL00028100
POL00028100
: BIRD & BIRD.
raenese Soge o
1a Westnet
(ead a pare date Dok Ge ae
lt ofpad te calor Disk
= bumbee Ons
Ogewdult xd toa Jr~ Alfa
POL00028100
POL00028100
POL00028100
POL00028100
__ 15709 "98 TUE 16:03 FAX” . ‘Len Pathway Boor
FAXMessage
’ Customer Service
To: Vinee Gaskece
From: SrEtHEN Mucstos
CARL Reoctanme Hiwsanc
Low, Rertor
Location:
(Cc PATHRAT
Fax Phone:
Dae: /<° fEtrénkel 199&
“No. of pages:
Message:
Vince [dat
A Hecrer GH
(including cover sheet)
on; i ntom& ke dyes ont
; both.
Qopix in He poh &
bape: fo
If transmission Is
Interrupted or
Incomploto,
plaase notify
sonder as soon as.
possible
15/09 '98 17:02 TX/RX NO. 1278
ICL Pathway Ltd
Forest Road
Feltham
Midd=
TW13 7EJ
POL
POL00028100
POL00028100
* Neweastle-upon-Tyne
“15 September 1998
1 CL Pathway
‘Mr. Vince Gaskell
CAPS Programme Manager
CAPS
Long Benton
‘NE98 1YX
Dear Vince.
Incomplete Transactions at Release 1C
Tunderstand that, on behalf of the CAPS Board, you expressed an interest in knowing the current state and
progress that has been made by ICL Pathway in identifying and eliminating the root causes of incomplete BES
transactions that have been experienced during Release 1C. .
‘There have been identified eleven (11) causes of incomplete transactions during the life of Release 1c.
Please find attached a table that identifies each of these, its underlying cause, and the actions taken to
eliminate or mitigate the problem and the effect of these actions. Also attached is a graph that shows the
progress over time of the total incidents of incomplete transactions and their ratio with respect to the overall
number of BES transactions.
‘You may note that as overall transaction rates increased, the problem diminished. In August, the success
rate was 99.98% - with less than 3 transactions per 10,000 being incomplcte, Our target is to continue to
reduce the number of incomplete transactions towards zero and we arc confident that where the cause is a
systematic error or where a systematic preventative measure can be devised then this will be achieved.
‘There will always remain a residual ‘human element’ for which there is no ready answer except that with
increasing experience of the behaviour of our end-user community we will be able to reinforce the
application of correct operational procedures through focused fecdback and transaction re-engineering,
Iwill be delighted to provide further explanation or clarification if required.
Yours sincerely
Stephen Muchow
Customer Service Director
ICL Pathway ICL Pathway Ltd
Forest Road
Cc:D Miller (Horizon), JH Bennett, MJB Coombs
Encl (2)
15/09 '98 17:02 TX/RX NO. 1278 P02
32ZT 86, 60/ST
20
°ON XU/XL
get
20d
Incomplete Transaction Analysis
POL00028100
POL00028100
transaction: Postmaster failed to follow procedures
and assign new Counter Clerk to a user group.
Ah GutepOny sal paeanca eee Bienen Sine Resulbtene et: fi ee
So
Heiiinalscectes oa ire nseeN Cet Sereda 5 PATERSON Cn Mr nceaeeo RV & Ae Nae #
fee ee eee as
1, Counter Counter terminals ‘Time Out’ after 15 minutes of Code Fix to actionon I Short term fix -Time-out period 2101/9: Prior to 9/2/98 there were 53
Terminal inactivity, Unfinished transactions are notcommitted I time-out with pending I extended to thr. instances,
Timeout once the terminal has timed out. Counter Clerk failed incomplete transaction, All transactions that are now
to follow procedures and complete the transaction, Permanent fix - ‘Forced 09/02/98 forcibly committed are
committal’ fix - ensuring that an logged and investigated by
incomplete transaction is Pathway. No transactions
7 committed after 74 minutes. have been committed
incorrectly since this was
: implemented.
2. Suspended I Counter clerk begins a ‘BES session, the session is Code Fix as per 1 ‘Forced commitlal’ fix ensuring. I 17/05/98" Prior to 17/5/98 there were
BES Session I then suspended but not committed. A second BES . above for parallel that any suspended session 26 instances of this problem.
session is started and committed in the normal way. sessions, holding an incomplete Since the fix was applied, no
‘The transaction from the first session is left transaction is committed upon further instances have been
incomplete. Counter Clerk failed to follow procedures terminal timeout after 74 mins. discovered.
and complete the transaction.
3. User Set-up I Ancw counter clerk is introduced to the system by the I Code Fix to default the I Fix currently being tested, Tobe ‘There have been 13
Postmaster but is not allocated to any User Group. ‘The I user group assignment : advised instances to date, This
new Counter Clerk is still able to swipe a card and and reinforce correct problem has been isolated
printa receipt but the system will not allow the operational procedures and is associated with relief
Counter Clerk to ‘Finish’, resulting in an incomplete I with Postmasters. staff appointments during
‘I holiday periods.
e
»
a
g
3
s
é
3
a
~
7
3
a
2
i
Anayand 12 7
“2008
60/ST
3LT 86,
rau)
*ON XU/XL
82eT
0d
POL00028100
POL00028100
, &
3
3
. 3
- 2
Brees envany 1) Eco Nolesnacterts S
ae Ce ee ee .
oo
Seeoueven
a epee
completion of the transaction once the manual receipt
has been completed, Some Counter Clerks are
accessing the ‘R. Preview’ button via “Exceptions”.
‘The scrcen appears identical to the screen displayed
when the ‘Manual Receipt’ button is pressed, however
the transaction cannot be completed when the Counter
-Clerk exits out of the receipt screen.
is sey : s
‘Counter clerk has removed the receipt prematurely Code Fix to enforce Fix currently ‘There have been 30
Receipt from printer, o the printer has failed. An error correct procedure. : advised instances to date.
message appears requesting the clerk to retry the print: 14/09/98 - BSU have tested the
If this option is sclected the transaction progresses fix anda CP and CCN arc in
through to completion but if the clerk sclects ‘Cancel’ train.
the transaction cannot be completed without voiding
and recommencing from card swipe. ts
5. Power Clerk proceeds through normal BES transaction, PSU authorises PCIL I Rare incident that can only be Never ‘There have been 3 instances
Failure printing a receipt and paying the Customer, encashment. Machine I resolved manually. to date, °
‘Theré are two scenarios where the transaction cannot re-started by .
be completed when power is lost: " postmaster.
1 Ifthe power is lost following printing of the
receipt and the customer has been paid but before
the Counter Clerk has touched ‘Finish’
2, Ifthe power fails after the Counter Clerk has
touched ‘Finish’ but in the ‘split second’ priorto
the transaction being written to the PC’s hard disk. '
6. Receipt During fallback following ‘counter printer failure when I Code Fix Fix released. “Receipt preview” I 02/07/98 Prior to the fix being applicd
Preview the Counter Clerk prepares a manual receipt, the button is now inactivated when there were 32 instances. No
Counter Clerk should access the ‘Manual Receipt” the reccipt printer has failed. further instances have been
option via ‘Exceptions’. This will allow the Clerk is forced to use ‘Manual discovered.
Receipt’ option.
é
5
=
ia
wd TOT
poo
60/ST
Z0:LT 86,
“ON XU/XL
set
sod
POL00028100
POL00028100
Peg rz
es
: oe
eet
ee
oo
aye
Ses
fess poe iy ilk
7, Incomplete I An OBCS transaction has been started but not finished I Code Fix to enforce Tobe
Receipt BES I anda BES transaction is then started, correct procedure, advised instances to date.
/OBCS Areceipt has been removed prematurely from printer 14/09/98 - BSU have tested the
Corruption I during the BES transaction; or the printer has failed fix and a CP and CCN are in
during the transaction. An error message appears train,
giving the Counter Clerk the option of reprinting the
receipt. If this option is sclected the transaction
progresses through to completion. However, if the
Counter Clerk selects ‘Cancel’ the transaction cannot ‘
be completed without retuming to Desktop’ and
recommencing from card swipe. In this circumstance
however, when the Counter Clerk retums to the
"Desktop’, the OBCS transaction is available for
finishing. This may give the Counter Clerk a false
sense of security that by finishing the OBCS
transaction, the BES transaction is also completed. ‘
. Clerk Error I Any failure to commit a transaction resulting from ‘Allerrors perceived to I Can only be Tesolved manually I N/A “here have been 19
genuine cletk error where the system behaved as be ‘Clerk errors’ will t instances to date,
required. be fully documented
. and reviewed by the
Accounting and
Reconciliation
Operations forum for
‘agreement,
9T SNL 86, 60/ST
Xva 60
~
a
et
bd
e
&
-y
&
. $008)
O:LT 86, 60/ST
“ON XU/XL
8LeT
90d
POL00028100
— POL00028100
¢
S
S
8
a
SREP PETE ETT Sn =n
ee ee Ae :
mete enya ge eats Sse siartnarcet I enh ease ksigs a
SS a
as aaiibae Geee tibet ST ooze ie ei e
9, User Logout unter Clerk procceds through normal BES Code Fix Fix currently being tested. Tobe ‘There have becn 9 instances z
transaction and attempts to print a receipt, but because advised to date. fs
of printer problems the Counter Clerk decides to log 14/09/98 - BSU have tested the
out of the system. Normally you cannot logout ofthe fix and a CP and CCN arc in
system, Escape button and Jogout icon bring up train
message “This button may only be pressed when the
‘No Entry Sign is not displayed”. .
10, New Card ‘Counter Clerk procecds through normal BES Code Fix Fix currently being tested.” ‘Tobe ‘There has becn only 1
Activation transaction, printing a receipt but docs not properly ‘ advised instance tu date.
‘ complete the transaction: ‘The clerk then activates a
new card — the outstanding transaction is left “
incomplete. °
er
=
11.1SHD Counter Clerk aleris HSHD of system problem. TISHD instructed in ‘There have been 3 instances Zz
Instruction I HSHD instructed Counter Clerk to log out during correct procedure that to date, &
transaction but provided no follow up advice —the is to determine where
transaction was therefore incomplete. the Counter Clerk was
. within the transaction.
when the system failed
and take appropriate
action.
S00}
POL00028100
POL00028100
15/09 ‘98 TUE 16:12 FAX!
Fd
8
°
I C L Pathway
15/09 '98
17:02
TX/RX NO.
1278
PO7
POL00028100
POL00028100
17.SEP.1998 8:58 CAPS PROGRAM CONTROL OFFICE NO.635 P14
CAPS and Card Programme Board Agenda
Issue 7
18 September 1998 at 10.30 to 14.10 Room B2506(F), DSS Longbenton
cae se = am
Attending: George McCorkell, Vince Gaskell, Peter Crahan, Dave Miller, Alexis
Cleveland, John Delamore, Lis Astall, Ken Davenport, Val Whitbread, Tim Cutts
(secretariat)
Apologies: John MacGregor, John Codling
1 Minutes of the CAPS and Card
Programme Board - Issue 6 Val Whitbread 10.30 - 10.40
2 Action Point Update Val Whitbread 10.40 - 11.20
3 CAPS and Card Programme
Managers’ Report - Paper 36 Vince Gaskeli/Peter Crahan 11.20 - 12.00
4 Horizon Wirector's Keport - Paper 38 Dave Miller 12.00 - 12.40
Lunch 12.40 -~ 13.10
5 JSA Go-Live readiness ~ presentation Claire Iall-Moore 13.10 - 13.35
6 Acceptance update - Presentation Paul Wooton 13.35 - 14.00
7 Any Other Business/Forward Look Peter Crahan 14.00 - 14.10
Below the line papers,
For information only:
Payments to customers in Residential Care Homes - Paper 35
Card Volumes - Paper 34 (CCPB AP 2.3 refers)
Finance report July 1998 - Paper 37
T6 September 1998 Status: Final
17/09 ‘98 08:55 TX/RX NO. 1294 POL
HORIZON PROGRAMME PROGRESS AGAINST KEY MILESTONES
Status @ 16" September 1998
Key Milestone
1. Current Testing
Pathway delivery into Model Office
Model Office Test Cycle 1 ends
Model Office Cycle 2 starts with
CAPS
End to End Cycle I completes
2. Planning
Issue Migration Stage PID
Complete Level 1 Plans
Issue Live Trial PID
3. Final Tests & Authorise
Conduct Model Office Test
Conduct Final End to End Pass
Release Authorisation for Live Trial
4, Migration to Rollout
Start Migration of Ic to NR2 offices
Commence Live Trial
Complete Live Trial
Start National Rollout
Planned Date
3 August 98
11 September 98
14 September 98
18 September 98
25 September 98
30 September 98
9 October 98
20 November - 18 December 98
4 November - 18 December 98
21 December 98
4 January 99 - 14 February 99
8 February 99
4 June 1999
5 July 1999
Current Progress
Achieved on plan
Achieved ahead of plan on 27 August
Commenced on schedule
Some initial problems but objectives will be
achieved for this cycle
First draft issued 16 September
Stage plans now drafted
On schedule
Appears on track but confirmation not possible
until late October
Some concerns on achieving all accounting
reconciliation tests by 18/12 but 2-3 week
contingency available in January
Draft approach and plan prepared
Detailed work in progress
Pathway deliverables on schedule, some
concerns on POCL service management
Assumes 17 weeks is adequate to prove service
for NRO
1 month contingency in plan after Trial
Status
Green
Green
Green
Green
Green
Green
Green
Green/
Amber
Amber
Green
Green
Amber
Amber
Amber
POL00028100
POL00028100
Comtstr Planck
Manda 21° *
Tn Cdvocks
Town) Cope
Rdod ne
S hued Swrcahuo~
aur Ak,
Daur Mathes
thane ego.
POL00028100
POL00028100
Mr. Vince Gaskell
CAPS Programme Manager
CAPS
Long Benton
Newcastle-upon-Tyne
NE98 1YX
CL
EEA
15 September 1998
Dear Vict ,
Incomplete Transactions at Release 1C
Tunderstand that, on behalf of the CAPS Board, you expressed an interest in knowing the current state and
progress that has been made by ICL Pathway in identifying and eliminating the root causes of incomplete BES
transactions that have been experienced during Release 1C.
There have been identified eleven (11) causes of incomplete transactions during the life of Release 1C.
Please find attached a table that identifies each of these, its underlying cause, and the actions taken to
eliminate or mitigate the problem and the effect of these actions. Also attached is a graph that shows the
progress over time of the total incidents of incomplete transactions and their ratio with respect to the overall
number of BES transactions.
‘You may note that as overall transaction rates increased, the problem diminished. In August, the success
rate was 99.98% - with less than 3 transactions per 10,000 being incomplete. Our target is to continue to
reduce the number of incomplete transactions towards zero and we are confident that where the cause is a
systematic error or where a systematic preventative measure can be devised then this will be achieved.
‘There will always remain a residual ‘human element’ for which there is no ready answer except that with
increasing experience of the behaviour of our end-user community we will be able to reinforce the
application of correct operational procedures through focused feedback and transaction re-engineering.
I will be delighted to provide further explanation or clarification if required.
Stephen Muchow
ti Service Direct
Cust ee jirector ICL Pathway Ltd
Forest Road
Feltham
CevD Miller (Horizony, JH Bennett, MJB Coombs Midds TW13 7EL.
Encl (2)
SCL Psrway ted
Restoran Engnd no 3022863
2 Fesbay Sousre
Usacon EC2A 10S
Incomplete Transaction Analysis
POL00028100
POL00028100
Purses
1. Counter
Terminal
Timcout
Counter terminals ‘Time Out’ after 15 minutes of
inactivity. Unfinished transactions are not committed
once the terminal has timed out, Counter Clerk failed
to follow procedures and complete the transaction,
Code Fix to action on
time-out with pending
incomplete transaction,
Short term fix =Time-out period
extended to Ihr.
Permanent fix - ‘Forced
committal’ fix - ensuring that an
incomplete transaction is
committed after 74 minutes.
21/01/98
09/02/98
ts
Prior to 9/2/98 there were 53
instances, :
All transactions that are now
forcibly committed are
logged and investigated by I
Pathway. No transactions
have been committed *
incorrectly since this was
implemented.
2. Suspended
BES Session
Counter clerk begins a BES session, the session is
then suspended but not committed, A second BES
session is started and committed in the normal way.
‘The transaction from the first session is left
incomplete. Counter Clerk failed.to follow procedures
and complete the transaction.
Code Fix as per I
above for parallel
sessions.
‘Forced committal’ fix ensuring,
that any suspended session
holding an incomplete *
transaction is committed upon
terminal timeout after 74 mins.
17/05/98
Prior to 17/5/98 there were
26 instances of this problem.
Since the fix was applied, no
further instances have been .
discovered.
3. User Set-up
A new counter clerk is introduced to the system by the
Postmaster but is not allocated to any User Group. The
new Counter Clerk is still able to swipe a card and
print a receipt but the system will not allow the
Counter Clerk to ‘Finish’, resulting in an incomplete
transaction, Postmaster failed to follow procedures
and assign new Counter Clerk to a user group.
Code Fix to default the
user group assignment
and reinforce correct
operational procedures
with Postmasters.
Fix currently being tested.
To be
advised
There have been 13
instances to date. This
problem has been isolated
and is associated with relief-
staff appointments during
holiday periods. .
POL00028100
POL00028100
4, Incomplete
Receipt
from printer, or the printer has failed, An error
message appears requesting the clerk to retry the print.
If this option is selected the transaction progresses
through to completion but if the clerk selects ‘Cancel’
the transaction cannot be completed without voiding
and recommencing from card swipe.
Code Fix to enforce
correct procedure,
ix currently being tested,
14/09/98 - BSU have tested the
fix and a CP and CCN are in
train, *
To be
advised
There have been 30
instances to date. _
5. Power
Failure
Clerk proceeds through normal BES transaction,
printing a reccipt and paying the Customer.
‘There are two scenarios where the transaction cannot
be completed when power is lost:
1 Ifthe power is lost following printing of the
reccipt and the customer has been paid but before
the Counter Clerk has touched ‘Finish’
2. Ifthe power fails after the Counter Clerk has
touched ‘Finish’ but in the ‘split second’ prior to
the transaction being written to the PC’s hard disk,
BSU authorises PCHL
encashment. Machine
re-started by
postmaster.
Rare incident that can only be
resolved manually.
Never
There have been 3 instances
to date, t
6. Receipt
Preview
During fallback following counter printer failure when
the Counter Clerk prepares a manual receipt, the
Counter Clerk should access the ‘Manual Receipt’
option via ‘Exceptions’. This will allow the
completion of the transaction once the manual reccipt
has been completed. Some Counter Clerks are
accessing the ‘R. Preview’ button via ‘Exceptions’.
The screen appears identical to the screen displayed
when the ‘Manual Reccipt’ button is pressed, however
the transaction cannot be completed when the Counter
Clerk exits out of the receipt screen.
Code Fix
Fix released. “Receipt preview”
button is now inactivated when
the receipt printer has failed,
Clerk is forced to use ‘Manual
Reccipt’ option.
02/07/98
Prior to the fix being applied
there were 32 instances. No
further instances have been
discovered.
POL00028100
POL00028100
Receipt BES
/OBCS
Cormuption
7. Incomplete -
“
An OBCS transaction has been started but not finished
and a BES transaction is then started.
A receipt has been removed prematurely from printer
during the BES transaction, or the printer has failed
during the transaction, An crror message appears
giving the Counter Clerk the option of reprinting the
receipt, If this option is selected the transaction
progresses through to completion, However, if the
Counter Clerk selects ‘Cancel’ the transaction cannot
be completed without returning to ‘Desktop’ and
recommencing from card swipe. In this circumstance
however, when the Counter Clerk retums to the
‘Desktop’, the OBCS transaction is available for
finishing. This may give the Counter Clerk a false
sense of security that by finishing the OBCS
transaction, the BES transaction is also completed.
Code Fix to enforce
correct procedure,
PRES.
Fix currently being tested.
14/09/98 - BSU have tested the
fix and a CP and CCN are in
train,
advised
instances to date.
8. Clerk Error
Any failure to commit a transaction resulting from
genuine clerk error where the system behaved as
required.
All errors perceived to
be ‘Clerk errors’ will
be fully documented
and reviewed by the
Accounting and
Reconciliation
Operations forum for
agreement,
Can only be resolved manually
NIA
There have been 19
instances to date,
POL00028100
POL00028100
complete the transaction. ‘The clerk then activates a
new card — the outstanding transaction is left
incomplete.
9. User Logout I Counter Clerk proceeds through normal BES Code Fix Fix currently being tested. Tobe There have been 9 instances
transaction and attempts to print a receipt, but because advised to date.
of printer problems the Counter Clerk decides to log 14/09/98 - BSU have tested the
out of the system, Normally you cannot logout of the fix and a CP and CCN are in
system, Escape button and logout icon bring up train *
message “This button may only be pressed when the
No Entry Sign is not displayed”
10. New Card Counter Clerk proceeds through normal BES Code Fix Fix currently being tested. Tobe There has been only 1
Activation transaction, printing a receipt but docs not properly advised instance to date.
11.HSHD
Instruction
Counter Clerk alerts HSHD of system problem.
HSHD instructed Counter Clerk to log out during,
transaction but provided no follow up advice ~ the
transaction was therefore incomplete.
‘
HSHD instructed in
correct procedure that
is to determine where
the Counter Clerk was
within the transaction
when the system failed
and take appropriate
action,
There have been 3 instances
to date,
16a a
Report 3.7: Incomplete Transactions Ric to Date
POL00028100
POL00028100
70.60 %
-@ Percent received / encashed payments
il
6+
\3
iF
1
97/11 Nov
97/12 Dec
98/01 Jan
0.50 %
—}-0.40 %
0.30%
0.20 %
o
a
0.10 %
0.00 %
98/08 Aug
POL00028100
POL00028100
as 8.SEP.1998 11:38 CAPS PROGRAM CONTROL OFFICE NO.S46, P.2
Restricted - Management and Commercial fi (qo Ir l \\ fl ir
CAPS and Card Programme Board Action Notes
21 August 1998, Longbenton, Newcastle-upon-Tyne
Issue 6 (Horizon only)
Attending: George McCorkell (Chair), Dave Miller, Mike Coombes, Vince Gaskell, Peter
Crahan, John Delamore, Lis Astell, John MacGregor, Parry Jenkins, Lilian Hunt and Ian
Roden (Minutes)
Apologies: Ken Davenport, Alexis Cleveland and John Codling
1. Horizon Only Action Points
11 AP 5.1(H) Dave Miller/Peter Crahan to discuss the establishment of a working
group to conduct an end to end review of service management. George McCorkell
said that the Terms of Rcferenec in regard to the boundaries/interfaces between
POCL, Pathway and CAPS needed to be clearly established. Dave Miller agreed
to take the action with a target completion date of the end of October. Peter
Crahan suggested that someone from CIS could be used to help with the Terms Of
Reference.
1.2 AP S.2(H) Dave Millor to advise Vinoo Gaskell if a post incident review of the
Sequent Box failure had been undertaken, Dave Miller reported that a short report
on the incident has been provided to Vince Gaskell. This will be discussed at the
next Service Review Forum.
1.3 AP 5.3(H) Peter Crahan/Dave Miller to meet to discuss long standing CRs. The
meeting has not taken place. George McCorkell sought assurance that there would
be no delays and that the long standing CRs were being dealt with. Mike
Coombes said that there were no ‘blockers’ as far as he could tell; there was a lot
of activity on Agreements To Agree (A2A), there was significant movement on the
‘Orange List! and nothing on the ‘Red List’. The joint contract team will monitor a,
and review at CNT meetings. Action cleared.
1.4 AP 5.4(H) Peter Crahan/Dave Miller to arrange for a final PDA Transition Board
to take place. The final PDA Transition Boa:d is scheduled for 3/9/98.
4 September 1998 CAPS & Card Programme Board Action Notes (Horizon only), Page 1
Status: Draft
08/09 '98 11:35 TX/RX NO. 1242 P02
POL00028100
POL00028100
8.SEP.1998 11:39 CAPS PROGRAM CONTROL OFFICE NO.546 P.3
Restricted - Management and Commercial
The Horizon Directors Report
2. Live Operations
2.1 Mike Coombes said that Jost transactions were now given the more accurate
description of ‘incomplete transactions’. He further reported that the deadline for
solving this problem was set at the end of October with the target set at zero. It
was agreed that Vince Gaskell be sent an update of the code changes, being put in
place to resolve the issue of incomplete transactions.
AP 6.1)
Mike Coombes to provide an update to Vince Gaskell of the code changes heing put
in place to resolve the issue of incomplete transactions.
3. Testing Plan
3.1 George McCorkell asked how faults identified in the various parallel testing
streams (eg. End-To-End Testing/Model Office Testing etc.) were factored into the
various testing phases. Mike Coombes gave a verbal update on the PinICL Process
but Dave Miller agreed to provide George McCorkell with a written description.
AP 6.2(H)
Dave Miller to provide George McCorkell with a written description of the PiuICL
process.
4. Live Running
44 On 30/7/98 the Correspondence Server tatled causing a total of 17 duplicate
payments to be made by Child Benefit. Vince Gaskell asked if Dave Miller could
provide him with a detailed account of how Horizon were progressing the issue.
Specifically;
a) Has the problem been understood ?
b) What has been done to put it right ?
c) Is there a PIR ?
d) How does it impact on current plans ?
AP 6.38)
Dave Miller to provide Vince Gaskell with a report on what has been done as a
result of the Correspondence Server failure (13/7/98).
5. Planning
5.1 Dave Miller said that work with the replan was well under way, but that there were
4 September 1996 CAPS & Card Frogramme soara Achon Notes (Horizon only), Page 2
Status: Draft
08/09 ‘98 11:35 TX/RX NO. 1242 PO3
POL00028100
POL00028100
8.SEP.1998
11:48 CAPS PROGRAM CONTROL OFFICE NO.546 P.4
Restricted - Management and Commercial
some eommoreial isoucs which, in the current eireumstances, would have to be
‘parked’ and included in any subsequent renegotiation. Mike Coombes confirmed
for George McCorkell that ‘Horizon is working to the principles contained in the
Pathway document and the dates contained within it. ie. All parties are working on
the assumption contained within the replan documents.
6. Testing
61 Dave Miller reported that at present Horizon/POCL were relatively content with the
present status of testing. Model Office Testing Rehearsal 1 was up to date and a
higher percentage of seipts Led becu iuu thaw capecusl. Eud-Tu-End Testing had
started slowly and at the time of the meeting had only reached Logical Day 5 when
it was planned to have been on Logical Day 11. George McCorkell asked Dave
Miller if he could provide the Board with greater visibility of Horizon testing
including STIRS/PinICLs. Dave Miller agreed to raise a report from Simon Rilot
to pass on to Parry Jenkins to agree a lavel of confidence. Parry Jenkine and
Simon Rilet are to meet to disouss the flexibility of the Testing plan. Dave Miller
agreed to report back to the board.
AP 6.4(H)
Dave Miller to provide greater visibility of what is happening in Horizon testing to
Parry Jenkins.
7: Release Management
71 Peter Crahan asked if the dates for Stage 1 (Release 2 with Child Benefit) and
Stage 2 (Release 2 with Multi-Benefits) in the Horizon Director's Report were
confirmed. Dave Miller agreed to issue a formal note of unambiguous dates to the
Board,
AP 6.5(8)
Dave Miller to issue a forma) note to all concerned giving key Horizon release dates.
8. Acceptance
8.1 Mike Coombes agreed that ICL/Pathway's mid-August target date for all
acceptance specifications to be completed and signed off would not be met. Dave
Miller agiced ty provide Peter Cruhan with the revised sign-off dates.
AP 6.6(H)
Dave Miller to provide Peter Crahan revised sign-off dates for all acceptance
specifications.
4 September 1998 CAPS & Card Programme Roord Action Notes (Horizon only), Pago 2
Status: Draft
08/09 '98 11:35 TX/RX NO. 1242
Po4
POL00028100
POL00028100
8.SEP.1998 11:40 CAPS PROGRAM CONTROL OFFICE NO.S46 P.S
Restricted - Management and Commercial
9. Implementation
94 PC asked for clarification of the overall ‘estate position’ following issue of the
recent RGM letters. DM confirmed that Bruce McNiven had possession of this info
and would make this available.
Change AP 6.7(H)
Dave Miller to arrange for Bruce McNiven to provide Peter Crahan with a detailed
breakdown of the RGM letters,
10. — Issues/Risks
10.1 Dave Miller confirmed the DA view that the Louuday Leiwecn BES/PAS was siill
an area of disagreement between respective finance directors, centring on the
liability position in the event of major system failure. He would determine the
current state of debate and see if dialogue between Horizon/CAPS directors could
be used as a means to break the apparent deadlock.
AP 6.8(H)
Dave Miller to determine the cusscut state uf debaic between BES/PAS and see if
dialogue between Horizon/CAPS directors could be used to break the apparent
deadlock.
10.2 Dave Miller advised that a CAPS Release 4.0 meeting was scheduled to take place
on 7/8/98 as plans for release 2+ were being drawn together.
AP 6.8
Vinee Gaskell to establish if the CAPS Release 4.0 meeting took place and report the
findings back to George McCorkell w/c 31/8/98.
11. Other Issues
11.1 In regards w Testing, George McCorkell sought clarification over D112 and
requested a closure report.
AP 6.9(H)
Dave Miller to provide the signed off DIT2 closure report to George McCorkell.
11.2 With regards to Issues. Gearge McCarkell asked if Finetianal Hangante far Model
Office testing were a serious issue ‘particularly for EPOSS'. Mike Coombes said
that the problem was not as big as it seemed and would not become a serious issue
until after 24/9/98, which was the date Horizon had set to have the problem
resolved by. An update will be provided for the next board.
4 September 1998 CAPS & Card Programme Roard Actinn Notes (Harizan only), Page 4
Status: Draft
08/09 '98 11:35 TX/RX NO. 1242 POS
8.SEP.1998 11:41
CAPS PROGRAM CONTROL OFFICE
RESTRICTED - MANAGEMENT AND COMMERCIAL
POL00028100
POL00028100
NO.546 P.6
CAPS and Card Programme Board Actions - Issue 6
Tssue: Horizon Action Points and updates from Board meeting on 21st August 1998 -
Version 1
Action: The Board is asked to note the new actions and provide updates.
Timing: By 11th September 1998
Action point Update Status Due date
AP 3.4 (H) 12 June 1998. Meeting held with Bruce Ongoing I 71/8/98
Peter Crahan (in McNiven and Andrew Simpkins. Work to
conjunction with I be progressed by Bruce, and Dave Miller
Bruce McNiven) I will provide an update on progress.
to arrange for an I PB 12 June 1998. Peter Crahan and Dave
informal 'post Miller to meet to progress this work
implementation urgently and report to the next Programme
review’ of the Board.
organisational PB 10 July 1998 A meeting has been held
changes post between Peter Crahan and Daye Miller
April 1998 where it was agreed that the forums, should
together with be implemented and meet within 1 month.
Preparation of an I PB 2/ August 1998. This is now the only
action plan forum outstanding, the position will be
reviewed on 3/9/98.
AP 3.5 @) PB 10 July 1998. Ken Davenport has made I Cleared
Ken Davenport to I necessary approaches. AP cleared.
commence
negotiations with
POCL on the
potential
requirement to
extend the use of
ESNS beyond
April 2000
AP 3.6 (H) 12 June 1998. John Meagher, the Horizon Cleared
Bruce McNiven to } Product Assurance Manager, is in the
provide a clear Process of writing to Peter Crahan advising
Statement of the him of the position regarding Pathway
contribution each I ‘light’.
requirement PB 12 June 1998. Dave Miller (John
makes to the Meagher) will provide a formal statement to
Pathway solution I the board of what makes ‘light’ solutions
‘heavy’.
9 July 1998. Paper produced by John
Meagher and issued to Peter Crahan.
08/09 '98 11:35 TX/RX NO. 1242 POG
POL00028100
POL00028100
8.SEP.1998 11:41 CAPS PROGRAM CONTROL OFFICE . *- NO.S46 P.7
RESTRICTED - MANAGEMENT AND COMMERCIAL
Action point "I Update *.*. _ wae — “I Status Due date
AP 5.1.0) 17 August 1998, Andy Radka has been Cleared I 21/8/98
Dave Miller / appointed in POCL to lead-up the Service mo y
Peter Crahan to Management Development Project. Vince
discuss the Gaskell has given Dave Miller a nomination °
establishment of a I to work on the CAPS end of a service
Working group to management review, Te1uus of reference to
conduct an end to I be provided asap.
end review of: PB 21 August 1998, Dave Miller to draft
service Tenms of Reference. -.
Management, ;
AP 5.2 @) 17 August 1998. As discussed at the Cleared I 21/8/98
Dave Miller to Horizon Service Review Forum on 17/6/98
advice Viaeo’ “ I (CAPE represcuted Ly Paul Hanson) there
Gaskell if a post I was a failure on the main host file system
incident review of I (sequent) on 11/6/98. Situation handled
the Sequent Box .I smoothly. Seven payment files were
failure had been delayed but this did not impact on
undertaken. ‘customers rereiving money. Solution to
Prevent this is to upgrade to the next
sequent release on NR2, A post Incident
Review (PIR) was not thought necessary
and not undertaken on this occasion.
PB 21 August 1998. Dave Miller provided a
shott report to Vince Gaskell and Peter
Crahan, to be considered and discussed at
next CCPB. E
AP 5.3 () 17 August 1998. Ongoing: Ongoing I 21/8/98
Peter Crahan / PB 21 August 1998. Mike Coombes
Dave Miller to reported that there was good progress being
meet to discuss . { made‘and 'no blockers’ to dealing with this
long standing CRs I- issue. Qoared
AP 5.4 ®) 17 August 1998, _Meeting fixed for 3/9/98. I] Ongoing I 21/8/98
Peter Crahan /
Dave Miller to .
arrange for a final
PDA transition
board to take : . .
place. 5 : Cleoted
08/09 "98 11:35 TX/RX NO. 1242 P07
POL00028100
POL00028100
8.SEP.1998 11:42
RESTRICTED - MANAGEMENT AND COMMERCIAL
CAPS PROGRAM CONTROL OFFICE NO.546 P.8
AP 6.1 ()
Mike Coomhes to
provide an update
to Vince Gaskell
of the code
changes being put
in place to resolve
the issue of
incomplete
transactions.
New
AP 6.2)
Dave Miller to
provide George
McCorkell with a
written description
of the PinICL
process,
=
AP 6.3.(H) Dave
Miller to provide
Vince Gaskell
with a report on
what has been
done as result of
the
Correspondence
Server failure
(13/7/98)
New
roar bri} yao qrendidl at tha Dt Agia uald..
AP 6.4 (H) Dave
Miller to provide
greater visibility
of what is
happening, in
Horizon testing to
Parry Jenkins
New
AP 6.5 (H) Dave
Miller to issue a
formal note to all
concemed, giving
key Horizon
Telease dates.
New
AP 6.6 (H) Dave
Miller to provide
Peter Crahan with
tevised sign-off
dates for all
acceptance
Specifications,
New
08/09 '98 11:35 TX/RX NO. 1242 POs
POL00028100
POL00028100
8.SEP. 1998 11:43 : CAPS -PROGRAM CONTROL OFFICE
RESTRICTED - MANAGEMENT AND COMMERCIAL
NO. S46.
P.S
AP 6.7(H) Dave I - . . .
Miller to arrange *
for Bruce . Bruce fhe N Won ,
MeNiven'to Z ‘
provide Peter - ‘
Crahan with a ‘ - -
breakdown of the
RGM leners.
New
AP 6.8(H)
Daye Miller to
determine the 7
Ss
current state of
debate between
BES/PAS and see
if dialogue —_——
between
Horizon/CAPS
dircotors could ve.
used to break the
apparent deadlock.
New
AP 6.9 (H) Dave
Miller to provide SS
the signed off Soe Inman,
DIT2 closure - am
report
New
From;
Tim Cutts
CAPS PMO
Room.B2306.DSS.LBIN
Tels_
08/09 '98. 11:35
TX/RX NO.
1242
Pog
POL00028100
POL00028100
URGENT FACSIMILE
TO: Mike Coombs
FAX NO: i GRO
NO OF PAGES (inc cover sheet) 1) a .
FROM PS to Dave Miller
TELEPHONE I GRO I
. HORIZON AUTOMATION PROGRAMME
MESSAGE:
] oso9y98
POL00028100
POL00028100
rE viz wpe wg papa Bat
dor ane bei 90 .
rman
ans paemp3 Bupy
2urpyng premp3 Zury
2] s92UN0D 22140 280g
sopang anuap meudopneg pony
P27 suazun0> 22140 350g
POL00028100
POL00028100
Q.SEP.1998 11:38 CAPS PROGRAM CONTROL OFFICE Nows46 Pt
IN ANd», -
oow® . Pay,
Programme Management Office
Rm B2506, DSS Longbenton, Benton Park Road,
Newcastle-Upon-Tyne, NE98 1Y¥X.
. FAX COVER SHEET
Date: 08/09/98 . :
To: i Dave Miller . Of: . Horizon
Tel: BI: Fax:
From: Tan Roden’
Secretariat, Internal. Cammun/Briefing
Tel: ; GRO: Fax:
Ro: Programme Board Minutes and Action Points
Number of pages (including this cover sheet): 9
Message:
FAO Of Dave Miller,
A copy of the Minutes and Action Points arising from the CAPS and Card Programme
Board (21/8/98)
1
08/08 '98 11:35 TX/RX NO. 1242 POL