FUJ00119617
FUJ00119617
ceptance iteri Hi Ref.: CR/ACS/o20
(cL A on ta Wh Version: 1.0
Pathway Schedule CS Date: 24/12/98
Acceptance Specification
Document Title — Acceptance Criteria Within Schedule C3 Acceptance Test.
Document Type —_ Acceptance Specification
Abstract This document describes the Acceptance Test for Acceptance
Criteria Within Schedule C3
Status Issued
Author J CC Dicks
Approval By 8/1/99
Distribution Pathway Management Team
Test & Integration Manager
Pathway Library
POCL/DSS Tain Kerr
Jeff Austin
PDA tba
Recommended ICL Pathway Test Manager _Authority(ies) Test Manager
for Approval
Signature
Name
Date
Approved For and behalf of ICL For and behalf of Authority(ies)
Pathway
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 1 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
cceptonce ‘ tH Ref.: CR/ACS/o20
(cL A Criteria Wi Version: 1.0
Pathway Schedule C3 Date: 24/12/98
Acceptance Specification
Signature
Name
Date
o.. DOCUMENT CONTROL
O.1 DOCUMENT HISTORY
Version Date Reason
Ou 1/4/98 Issued for review
0.2 23/7/98 Issued for approval
03 20/11/98 Updated for comments, issued for approval
0.4 10/12/98 Updated for comments, issued for approval
0.5 18/12/98 Includes reference to caveats document, issued for
approval
1.0 24/12/98 Version for approvals
0.2 ASSOCIATED DOCUMENTS
Reference Version Date Title Source
(1)
(2) Acceptance Ou 13/09/96 Standard for Raising and — Pathway
Standard Progressing Acceptance
Incidents.
(3) I Acceptance 1.2 13/7/98 Standard for documenting Pathway
Standard Acceptance Specifications
(4) Authorities’ 7.2 22/5/97 Acceptance Procedures DSS/POCL
Agreement Schedule (A)Ao7
(5) POCL 7.2 22/5/97 I Acceptance Procedures POCL
Agreement Schedule (P)An
(6) DSS 7.2 22/5/97 Acceptance Procedures DSS
Agreement Schedule (D)Au
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
CONTRACT CONTROLLED
Printed on: [ DATE \*
Page 2 of 33
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119617
FUJ00119617
. . Hr Ref.: CR/ACS/o20
ICL Acceptance Criteria Within Version: 1.0
Pathway Schedule C3 Date: 24/12/98
Acceptance Specification
Reference Version Date Title Source
(7) Authorities’ 8.1 8/3/98 Requirements Schedule DSS/POCL
Agreement (A)Bo4
(8) Authorities’ 8.1 8/3/98 Solutions Schedule Pathway
Agreement (A)Bos
(9) DSS 8.1 8/3/98 Requirements Schedule DSS
Agreement (D)A15
(io) DSS 8.1 8/3/98 Solutions Schedule Pathway
Agreement (D)A16
(u) POCL 8.0 13/u/97__—_ Requirements Schedule POCL
Agreement (P) As
(iz) POCL 8.1 8/3/98 Solutions Schedule Pathway
Agreement (P)A16
(33) CR/FSP/o04 = 4.0 30/9/97 Service Architecture Pathway
Design Document
(144) PA/STR/oog 2.0 24/2/98 Release Contents Pathway
Definition for Pathway
New Release 2
(15) CR/ACS/o21 03 13/u/98 Policies & Standards Pathway
Acceptance Test
Specification
(a6) DSS of 27/1/96 Schedule Bo DSS
Agreement
(17) POCL of 27/u/96 Schedule Boi POCL
Agreement
48) DSS 5.2 29/n/96 Schedule Boz DSS
Agreement
(9) POCL 5.2 29/1/96 Schedule Bo2 POCL
Agreement
(20) DSS of 29/n/96 Schedule Bo3 DSS
Agreement
(21) POCL of 29/1/96 Schedule Bo3 POCL
Agreement
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 3 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
cceptonce . . ithi Ref.: CR/ACS/o20
(cL A Criteria Wi Version: 1.0
Pathway Schedule C3 Date: 24/12/98
Acceptance Specification
Reference Version Date Title Source
(22) DSS 73 24/6/97 Schedule Bo6 DSS
Agreement
(23) POCL 8.0 13/u/97_ Schedule Go6 POCL
Agreement
(24) As_cavoi.doc oo. 4/12/98 Acceptance Specification I DSS / POCL
draft Consolidated Caveats
(25)
(26)
(27)
0.3 ABBREVIATIONS
BT Business Thread
DSS Department of Social Security
HLTP High Level Test Plan
PDA Programme Delivery Authority
POCL Post Office Counters Ltd
0.4 CHANGES IN THIS VERSION
Version for approvals
0.5 GENERAL CAVEAT
Approval of this Acceptance Specification is subject to the relevant caveats in the
extant version of Acceptance Specification Consolidated Caveats.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 4 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FU.
ceeptance Criteri ni Ref.: CR/ACS/o20
IL A Criteria W Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specificatiow
0.5 TABLE OF CONTENT
0. DOCUMENT CONTROL ......ccsessessesessessesseneseeseenseseenessesseseneeensseesrenesaeenens 2
ou DocumENT History
0.2 ASSOCIATED DOCUMENTS
03 ABBREVIATIONS........04
0.4 CHANGES IN THIS VERSION.
0.5 GENERAL CAVEAT...
O5 TABLE OF CONTENT.
1. PURPOSE & SCOPE ....cssscssesesssssseseseseseeeenenenseceseseseseenesensneensseseseesenensenenenses 6
2. ACCEPTANCE INCIDENT:
3. ACCEPTANCE PERIOD......ccccssssssesesesssesesseseneseesssenssescesescsesseseseneneeseseneeeseene 7
4. DELIVERABLES & SERVICES
5. ACCEPTANCE CRITERIA ....cccsssseseseseesesesenesesesessseesesesensesessseseeeeseneneenenenees 8
5a ACCEPTANCE CRITERIA AND TEST CONDITIONS........:0000008
5.11 Description Of Tests Conducted By Acceptance Trial.
5.1.2 Description of tests conducted by Acceptance Review
5.2 CRITERIA FOR LATER ACCEPTANCE
5.3. CRITERIA SUMMARY..
6. ACCEPTANCE INCIDENT SEVERITY .
61 HIGH SEVERITY INCIDENTS.
6.2 MEDIUM SEVERITY INCIDENTS
63 Low SEVERITY INCIDENTS ..
7. TEST DATA uu... csescescsseseeseneesesseseesesseeceasenessensesesseseesensesecsesaseseaseneesenaensees 29
8. AUTHORITY RESPONSIBILITIES........sssssesessessrsserecesrsesesssssseseeeeeeseneeeee 30
8.1 APPOINT TEST MANAGER
8.2 ACCEPTANCE INCIDENT REPORTS
83 ACCEPTANCE INCIDENT ANALYSIS REPORTS.
8.4 ATTENDANCE AT TRIALS AND REVIEWS
85 MANAGEMENT AND CO-ORDINATION .
8.6 PROGRESS REVIEWS
9. CONTRACTOR RESPONSIBILITIES .
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 5 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
00119617
ICL Acceptance Criteria Withiw
Pathwoy Schedule CS
Acceptance Specification
FUJ00119617
FUJ00119617
Ref.: CR/ACS/o20
Version: 1.0
Date: 24/12/98
10. ACCEPTANCE TRIAL TEST CONDITIONS. .........0008
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT I
CONTRACT CONTROLLED
Printed on: [ DATE \*
Page 6 of 33
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri A Ref.: CR/ACS/o20
ICL A Criteria Wi Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
1 PURPOSE & SCOPE
This document describes the Acceptance Test for Acceptance Criteria Within
Schedule C3 in accordance with the Acceptance Procedures that are set out in the
Schedules referred to in section 0.2 and also in the Pathway document “Standard
for Documenting Acceptance Specifications”. This Test will determine that
Acceptance Criteria Within Schedule C3 meets all the Acceptance Criteria that are
agreed in the Acceptance Specification and that are within the scope of the
“Pathway Release Contents Specification” document for New Release 2, if
applicable.
Schedule C3
Policies & Standards
Education Levels
POCL DSS POCLIDSS POCLDSS
Implementation Implementation Implementation
Training Service Rollout
Fs} ‘DSS Interface ‘TIP Interface MIS Interface
= PAS CMS:
=II2
a g 4 g
Help Desks 2 é
Reference 2
Data 3
PocL -
Infrastructure
BES ‘ones ee EPOSS
Figurei-1; This Acceptance Test in relation to others
2. ACCEPTANCE INCIDENTS
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 7 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
The standard and method for originating, progressing and resolving Acceptance
Incidents shall be as described in the associated Document “Standard for Raising
and Progressing Acceptance Incidents”.
3. ACCEPTANCE PERIOD
The Acceptance Period for the Acceptance Tests, which comprise the Operational
Trial, is as determined by schedule Bo7 of the AUTHORITIES’ Agreement.
The Pathway programme plan details the schedule for the Acceptance Criteria
Within Schedule C3 Acceptance Test.
4. DELIVERABLES & SERVICES
This section details the Deliverables and Services that are the subject of this
Acceptance Test and as defined by the related Agreements.
Deliverable or Contract Method
Service. Reference
Requirements D)A5, (P)A15 Acceptance Review
D)A16, (P)Ai6
Deliverables and ))Ao2, (D) Boi, (D)Bo2, (D)Bo3,
(
Solutions (
(D
Services (D)Bo6, (D)Bos, (D)Do2, (D)Eo2;
(
(
P)Aoz2, (P)Bou, (P)Bo2, (P)Bo3,
P)Go6, (P)Bo5, (P)Do2, (P)Eo2,
(P)Fo2, (P)Go4, (P)Ho2,;
Table of Deliverables and Services.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 8 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
5. ACCEPTANCE CRITERIA
This section lists the identifier of each Acceptance Criterion that will be
demonstrated by the Acceptance Test. It also lists the Acceptance Test Conditions
that are used to determine whether (or not) the Acceptance Criterion has been met
together with the applicable test Phase, Technical Test, or Live Trial.
Acceptance Criteria are split into three sets of tables according to the nature of the
acceptance method, one set for those tested by Acceptance Trial, a second for those
tested by Acceptance Review and a third which lists those criteria which are for
Acceptance at a later release. The Release on which Acceptance is to be conducted
is defined by reference to the Release Contents Description included in the
Associated Documents section of the Acceptance Specification. Exceptionally, it
may be necessary for one particular Acceptance Criterion to be tested by a
combination of trial and review in which case there are entries for Trial and Review.
The Acceptance Criteria in this specification refer to those in other Acceptance
Specifications. For these the recommended method is to treat the results of
Acceptance Tests as Review items and to evaluate and resolve any non-
conformances.
The Acceptance Criteria for this and other Acceptance Specifications are defined in
the Pathway Acceptance Criteria Database.
5.1. ACCEPTANCE CRITERIA AND TEST CONDITIONS
Conformance of the Acceptance Criteria Within Schedule C3 Acceptance Criteria
will be demonstrated through Acceptance Trials and/or Acceptance Reviews.
Tests conducted by Acceptance Trials comprise practical tests using prepared test
scripts. If applicable the Test Condition(s) appropriate to a criterion are specified
in section 5.1.1 together with a description of the test. Detailed composition of the
test in terms of sequences of Test Conditions is contained in Section 10. In the
tables in section 5.1.1 the rows labelled Function Run Entry will be populated
immediately prior to the running of the Acceptance Trials in a working version of
the Acceptance Specification. These will provide invigilators with references to the
checklists used to monitor the progress of the testing. The order of running of Test
Conditions will not necessarily correspond to the order presented in HLTPs
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 9 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
because of the “physicalisation” of the testing. The Function Run Entry will allow
the invigilator to read across from the criterion to the checklist.
Tests conducted by Acceptance Review comprise typically document reviews, site
visits or presentations. If applicable the Test Condition(s) are described in section
5.1.2.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 10 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
5.1.1 Description Of Tests Conducted By Acceptance Trial
No Acceptance Criteria will be met by Acceptance Trial.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 11 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri A Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
5.1.2 Description of tests conducted by Acceptance Review
The table below shows which Acceptance criteria are to be met by Acceptance
Review. Acceptance Tests will use the versions of any relevant documents (as
referenced from section 0.2) contained in the approved version of the Acceptance
Specification.
&
1
Schedule
The Services shall meet the following acceptance Criteria,
namely that:
(a) the Requirements specified in Schedule A15 of the
DSS Agreement and Schedule A15 of the POCL
Agreement (or Schedule Bi of the AUTHORITIES’
Agreement prior to its transposition to the DSS and
POCL Agreements) shall be satisfied fully:
i. in accordance with the Policies and Standards
specified in Schedule Aoz of the DSS Agreement
and schedule Ao2 of the POCL Agreement
The Criteria specified in Acceptance Test Specification
Policies & Standards are satisfactorily tested.
Review of the results of the Policies &Standards
Acceptance Test
(5)
Operational Trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 12 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri A Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
&
2
Schedule
The Services shall meet the following acceptance Criteria,
namely that:
(a) the Requirements specified in Schedule A15 of the
DSS Agreement and Schedule Ai5 of the POCL
Agreement (or Schedule Bi of the AUTHORITIES’
Agreement prior to its transposition to the DSS and
POCL Agreements) shall be satisfied fully:
ii. by means of the Solutions specified in Schedule
AiG of the DSS Agreement and Schedule A16 of the
POCL Agreement (or Schedule B2 of the
AUTHORITIES’ agreement prior to its
transposition to the DSS and POCL Agreements)
The Requirements are met by the Solutions
Document inspection of the results of Acceptance as
evidenced through all other Acceptance Specifications
All other Acceptance Specifications
Operational Trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 13 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri A Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
&
3
Schedule
The Services shall meet the following acceptance Criteria,
namely that:
(a) the Requirements specified in Schedule A15 of the
DSS Agreement and Schedule Ai5 of the POCL
Agreement (or Schedule Bi of the AUTHORITIES’
Agreement prior to its transposition to the DSS and
POCL Agreements) shall be satisfied fully:
iii. utilising the Software specified in schedule Bi of
the DSS Agreement and Schedule Bi of the
POCL Agreement
[DN: Interpreted as Schedules Bo1.]
The Requirements are met using the specified software
Inspection of the functional software:
DSS
¢ Auditor Access to CMS & PAS
« Auditor Access to TMS
POCL
* Windows NT Workstation
« Riposte
EIT
PCDF
PPF
ESNS+
PEF
Auditor Access to TMS
(16), (17)
Operational Trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 14 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ICL Acceptance Criteria Within Venn crs ‘ACS/o20
Pathwoy Schedule CS Date: 24/12/98
A Specificati
&
4
Schedule
The Services shall meet the following acceptance Criteria,
namely that:
The Services shall meet the following acceptance Criteria,
namely that:
(a) the Requirements specified in Schedule A15 of the
DSS Agreement and Schedule A15 of the POCL
Agreement (or Schedule Bi of the AUTHORITIES’
Agreement prior to its transposition to the DSS and
POCL Agreements) shall be satisfied fully:
iv. utilising the Hardware specified in Schedule Bz
of the DSS Agreement and Schedule Bz of the
POCL Agreement
[DN: Interpreted as Schedules Bo2.]
The requirements are met using the specified hardware
No test is required. No Hardware is specified in (18), (19).
All hardware supplied is Pathway’s. No hardware is to be
supplied as an Optional Product.
(a8), Go)
Operational Trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 15 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri A Ref.: CR/ACS/o20
ICL A Criteria Wi Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
A Specificati
&
5
Schedule
The Services shall meet the following acceptance Criteria,
namely that:
(a) the Requirements specified in Schedule A15 of the
DSS Agreement and Schedule Ai5 of the POCL
Agreement (or Schedule Bi of the AUTHORITIES’
Agreement prior to its transposition to the DSS and
POCL Agreements) shall be satisfied fully:
v. delivering the Documentation specified in
Schedule B3 of the DSS Agreement and Schedule
B3 of the [POCL] Agreement
[DN: Interpreted as Schedules Bo3.]
The Requirements are met delivering the specified
documents
DSS I POCL
BA/POCL Reports and Receipts [BA/POCL I“ v
Reports and Receipts - Pathway Horizon
Office Platform Service: Release 2]
OPS Style Guide v
[Pathway Horizon Office Platform Service
Style Guide Manual]
Security Functional Specification v v
Service Architecture Design Document
TMS Technical Documentation [TMS v
Architecture]
Fraud Risk Management Service Design v v
Specification
PUN Information Note [PUN information v v
notes, PCi, 11, 13]
Service Interface Definition Document v
[obsolete]
CAPS Access Service High Level Design v
[CAPS Access Service High Level Design
and CAPS Access Service (On-Line) High
N
SN
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 16 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
Acceptance Criteria Withiw
Acceptance Specification
Ref.:
Version:
Schedule CS Date:
CR/ACS/o20
1.0
24/12/98
FUJ00119617
FUJ00119617
Level Design]
BPS MIS Requirements Catalogue [Benefit
Payment Service MIS Requirements
Catalogue]
Pathways Training of User Awareness
Baseline Document [Training and User
Awareness Baseline Document]
Counter Hardware Design Specification
Post Office Site Failure Contingency
Procedures
Release 1 Contents Description [Release
Contents Definition for Pathway New
Release 2]
Release Policy
AP Client Design Specification [AP Client
Specification <AP Client name>]
Business Continuity Plan [Contingency
Map]
Pathway Security Policy
Pathway Security Standards [Security
Management Procedure]
OBCS Interface High Level Design [OBCS
Interface Definition]
Counter Transaction Performance
Measurement and Benchmarking [POCL
Counter Transaction Performance
Measurement]
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT I
CONTRACT CONTROLLED
POCL.
Printed on: [ DATE \*
Page 17 of 33
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
CR/ACS/o20
1.0
FUJ00119617
FUJ00119617
Acceptance Criteria Within Venn
Schedule CS Date:
A Specificati
24/12/98
PPD Counters & Helpdesk
[Horizon System Help Desk Call Enquiry
Matrix
NR2 - PCHL Call Enquiry Matrix
Pathway Customer Service PPD Structure
and Review Method
NRz2 Electronic Point of Sale Service PPD
NR2 Order Book Control Service PPD
NR2 Benefit Encashment Service PPD
NR2 Operating Environment PPD
NR2 Access Control and User
Administration PPD
NR2 Automated Payment Service PPD
NRz Pathway Card Distribution Facility
PPD
NR2 Payment Card Helpline PPD
NRz2 Horizon System Helpdesk PPD]
Document inspection of the delivered documents.
Note that some of the documents have different titles from
those listed and/or are organised into different document
structures. The titles within brackets describe how the
specified documents are realised where different.
(20) (21)
Operational Trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT I
CONTRACT CONTROLLED
POCL.
Printed on: [ DATE \*
Page 18 of 33
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
FUJ00119617
FUJ00119617
ICL Acceptance Criteria Within Venn crs ‘ACS/o20
Pathwoy Schedule CS Date: 24/12/98
A Specificati
iS)
6
Schedule
The Services shall meet the following acceptance Criteria,
namely that:
b) such Requirements are capable of being implemented
as specified in Schedule B6 of the DSS Agreement and
Schedule G6 of the POCL Agreement
[DN: Interpreted as Schedules xo6.]
The specified Requirements referenced by the Acceptance
Criteria within the applicable Acceptance Test
Specifications are capable of implementation.
DSS
926
IM/ACS/o05 (Implementation - Roll-out )
929
RS/ACS/oo1 (End-to-End) & IM/ACS/005
(Implementation - Roll-out )
930
IM/ACS/o05 (Implementation - Roll-out
931
IM/ACS/o05 (Implementation - Roll-out
941
IM/ACS/o05 (Implementation - Roll-out
972
)
)
)
IM/ACS/oo05 (Implementation - Roll-out )
974 CR/ACS/o017 (DSS Interface)
POCL
487 IM/ACS/oo05 (Implementation - Roll-out )
488 IM/ACS/o05 (Implementation - Roll-out )
489 IM/ACS/o05 (Implementation - Roll-out )
490 IM/ACS/oo5 (Implementation - Roll-out )
491 IM/ACS/oo05 (Implementation - Roll-out )
492 IM/ACS/oo5 (Implementation - Roll-out )
493
IM/ACS/003 (Implementation - Services
494
IM/ACS/003 (Implementation - Services
495.
IM/ACS/oo05 (Implementation - Roll-out
496
IM/ACS/o05 (Implementation - Roll-out
497
IM/ACS/o05 (Implementation - Roll-out
498
)
)
)
IM/ACS/oo5 (Implementation - Roll-out )
499
CR/ACS/o18 (Help Desks)
500
IM/ACS/oo05 (Implementation - Roll-out )
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
Printed on: [ DATE \*
CONTRACT CONTROLLED Page 19 of 33
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
ceeptance Criteri A Ref.: CR/ACS/o20
ICL A Criteria Wi Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
A Specificati
FUJ00119617
FUJ00119617
501
IM/ACS/oo5 (Implementation - Roll-out
502
IM/ACS/oo5 (Implementation - Roll-out
503
IM/ACS/o05 (Implementation - Roll-out
504
IM/ACS/o05 (Implementation - Roll-out
5°7.
IM/ACS/o05 (Implementation - Roll-out
508
IM/ACS/o05 (Implementation - Roll-out
509
IM/ACS/o005 (Implementation - Roll-out
510
IM/ACS/o05 (Implementation - Roll-out
5u
512
IM/ACS/o05 (Implementation - Roll-out
5133
IM/ACS/o05 (Implementation - Roll-out
514
IM/ACS/oo5 (Implementation - Roll-out
515
IM/ACS/o05 (Implementation - Roll-out
516
IM/ACS/o05 (Implementation - Roll-out
517
IM/ACS/oo5 (Implementation - Roll-out
518
IM/ACS/o05 (Implementation - Roll-out
519
( )
( )
( )
( )
( )
( )
( )
( )
IM/ACS/oo05 (Implementation - Roll-out )
( )
( )
( )
( )
( )
( )
( )
)
IM/ACS/o05 (Implementation - Roll-out
525
CR/ACS/o18 (Help Desks) & CR/ACS/o006
(APS)
834
CR/ACSo08 (EPOSS)
906
IM/ACS/o05 (Implementation - Roll-out )
929
RS/ACS/oo1 (End-to-End) & IM/ACS/005
(Implementation - Roll-out )
941
IM/ACS/o05 (Implementation - Roll-out )
945
IM/ACS/oo05 (Implementation - Roll-out )
971
CR/ACS/006 (APS)
97
IM/ACS/o05 (Implementation - Roll-out )
Document inspection of the results of the Acceptance
Tests listed above for the Acceptance Criteria derived from
the Requirements listed above.
(22), (23)
Operational Trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
CONTRACT CONTROLLED
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
Printed on: [ DATE \*
Page 20 of 33
FUJ00119617
FUJ00119617
“tori. Hr Ref.: CR/ACS/o20
ICL Acceptance Criteria Within Version: 1.0
Pothwey Schedule C3 Date: 24/12/08
A Specificati
&
7
Schedule
The Services shall meet the following acceptance Criteria,
namely that:
c) the Acceptance Criteria in Schedules B5, D2, and E2 of
the DSS Agreement and B5, D2, E2, F2, G4 and H2 of
the POCL Agreement are met
[DN: Interpreted as Schedule xon.]
The Services meet the Acceptance Criteria in the specified
Schedules
DSS Schedule subject I Acceptance Specifications
Schedule I and considerations
within Schedule
Bo5 DSS Service
Infrastructure
Security, interface I RS/ACS/oo2 (Security)
validation CR/ACS/017 (DSS Int)
Fraud RS/ACS/o02 (Security)
CR/ACS/on (Audit)
Contingency RS/ACS/oo2 (Security)
Doz PAS
Security RS/ACS/o02 (Security)
CR/ACS/o15 (PAS)
Fraud RS/ACS/o02 (Security)
CR/ACS/on (Audit)
CR/ACS/015 (PAS)
Contingency RS/ACS/o02 (Security)
CR/ACS/o15 (PAS)
Service Levels CS/ACS/o08 (MIS)
Eo2 CMS
Security RS/ACS/o02 (Security)
CR/ACS/o16 (CMS)
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
CONTRACT CONTROLLED
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
Printed on: [ DATE \*
Page 21 of 33
FUJ00119617
FUJ00119617
ICL Acceptance Criteria Within I Ret! CR/ACS/o20
Pathway Schedule C3 Date: 24/12/98
Acceptance Specification
Fraud RS/ACS/o02 (Security)
CR/ACS/on (Audit)
CR/ACS/o16 (CMS)
Contingency RS/ACS/oo02 (Security)
CR/ACS/o16 (CMS)
Service Levels CS/ACS/o08 (MIS)
POCL Schedule subject I Acceptance Specifications
Schedule I and considerations
within Schedule
Bos POCL Service
Infrastructure
Security, interface I RS/ACS/oo2 (Security)
validation CR/ACS/o01 (BES)
CR/ACS/006 (APS)
CR/ACS/008 (EPOSS)
CR/ACS/007 (POCL Inf)
CR/ACS/o05 (OBCS)
Fraud RS/ACS/o02 (Security)
CR/ACS/on (Audit)
CR/ACS/o12 (Reconcil’n)
CR/ACS/007 (POCL Inf)
Do2 BES
Security RS/ACS/oo02 (Security)
CR/ACS/o01 (BES)
CR/ACS/007 (POCL Inf)
Fraud RS/ACS/o02 (Security)
CR/ACS/ou (Audit)
CR/ACS/o12 (Reconcil’n)
CR/ACS/o01 (BES)
Contingency RS/ACS/o02 (Security)
CR/ACS/oo1 (BES)
Service Levels CS/ACS/o008 (MIS)
Eo2 APS
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 22 of 33
Nothing contained herein shall be deemedl or construcd ay affecting existing contractual
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ICL Acceptance Criteria Within I Ret! CR/ACS/o20
Pathway Schedule C3 Date: 24/12/98
Acceptance Specification
Security RS/ACS/o02 (Security)
CR/ACS/o06 (APS)
CR/ACS/007 (POCL Inf)
Fraud RS/ACS/o02 (Security)
CR/ACS/ou (Audit)
CR/ACS/o12 (Reconcil’n)
Contingency RS/ACS/o02 (Security)
Service Levels CS/ACS/008 (MIS)
Fo2 EPOSS
Security RS/ACS/o02 (Security)
CR/ACS/008 (EPOSS)
CR/ACS/007 (POCL Inf)
Fraud RS/ACS/o02 (Security)
CR/ACS/on (Audit)
CR/ACS/o12 (Reconcil’n)
Contingency RS/ACS/oo2 (Security)
Service Levels CS/ACS/008 (MIS)
Go4 POCL
Infrastructure
Services
Security, interface I RS/ACS/oo2 (Security)
validation CR/ACS/007 (POCL Inf)
CR/ACS/o01 (BES)
CR/ACS/o06 (APS)
CR/ACS/o008 (EPOSS)
CR/ACS/o05 (OBCS)
Fraud RS/ACS/o02 (Security)
CR/ACS/on (Audit)
CR/ACS/o12 (Reconcil’n)
CR/ACS/007 (POCL Inf)
Contingency RS/ACS/o02 (Security)
CR/ACS/007 (POCL Inf)
Service Levels CS/ACS/008 (MIS)
Ho2 OBCS
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE
MERGEFORMAT ]
CONTRACT CONTROLLED
Printed on: [ DATE \*
Page 23 of 33
obligations or creating new contractual obligations between ICL Pathway and the DSS and/or
POCL.
FUJ00119617
FUJ00119617
coeptance Criteria Withi Ref: CR/ACS/o20
(cL A Criteria Wi Version: 1.0
Pothwey Schedule C3 Date: 24/12/08
A Specificati
Security RS/ACS/o02 (Security)
CR/ACS/007 (POCL Inf)
CR/ACS/oo5 (OBCS)
Fraud RS/ACS/o02 (Security)
CR/ACS/ou (Audit)
CR/ACS/o12 (Reconcil’n)
Contingency RS/ACS/o02 (Security)
CR/ACS/o05 (OBCS)
Service Levels CS/ACS/008 (MIS)
Document inspection of the results of the Acceptance
Tests in the Acceptance Specifications listed for the
considerations defined.
These are shown in the Test Condition above
Operational trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 24 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri A Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
iS}
8
Schedule
Acceptance during the Operational Trial Period shall also
be dependent on the CONTRACTOR demonstrating the
capability of the “Release 2” (as defined in Schedule Ao7) to
support the payment of multiple benefits and on-line
functionality, both of which will be introduced into live
operation later, in conjunction with CAPS version 3
No separate demonstration is required as this capability is
available as part of New Release 2.
[DN: Now expected to be introduced into live operation by
DSS at CAPS Version 4.0.]
Document inspection
BPS Systems Test and BIT Reports
Operational Trial
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 25 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
5.2 CRITERIA FOR LATER ACCEPTANCE
This level of Acceptance Specification relates to Tests performed at New Release 2.
Certain functionalities are not implemented at New Release 2 and therefore will not
be Accepted at this time.
The three principal deliverables currently planned for New Release 2 +, “Soft” EVP,
Enquiries On-Line and AP Smart are items for which agreements on definition are
not yet available or (in the case of AP Smart) was achieved too late for inclusion in
New Release 2.
A later level of this specification will define the process for Acceptance of associated
Criteria.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 26 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri A Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
5.3. CRITERIASUMMARY
(e} 1
(ee) 2. v
C3 3. v
(e} 4. No test
[S} 5. v
GB 6. v
(e} 7. v
(e} 8. v
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 27 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
6. ACCEPTANCE INCIDENT SEVERITY
This section identifies the guidelines to be applied during the analysis of
Acceptance Incidents, in order to establish the severity of such Acceptance
Incidents.
61 HIGH SEVERITY INCIDENTS
Failure to meet an Acceptance Criterion which would have a substantive impact on
the service received by the Customer, e.g. failure to pay benefits to the right person,
at the right place, at the right time.
Failure to meet an Acceptance Criterion which would have a major impact on the
ability of the AUTHORITY or AUTHORITIES to perform their business, or where
there was a major impact on the resources of the AUTHORITY or AUTHORITIES
necessary to overcome that impact on their business, e.g. failure to support
accurate POCL accounting.
Failure to meet an Acceptance Criterion which would impact the security of the
service where there is no acceptable procedural workaround.
Consistent failure to meet Minimum Acceptable Thresholds for Service Levels, e.g.
where particular transactions do not meet the minimum Acceptable Threshold
under normal loading.
6.2, MEDIUM SEVERITY INCIDENTS
Failure to meet an Acceptance Criterion which is visible to the Customer and is
likely to give rise to an adverse public perception of the service, but does not
substantively impact the service received by the Customer, e.g. incorrect spelling
ona receipt.
Failure to meet an Acceptance Criterion which would have a medium impact on
the ability of the AUTHORITY or AUTHORITIES to perform their business, or
where there was a medium impact on the resources of the AUTHORITY or
AUTHORITIES necessary to overcome that impact on their business, e.g. non-
production of a weekly report, resulting in its manual transcription, which causes
additional resource or effort at every outlet of the average duration of one hour per
week per outlet.
Occasional failure to meet Minimum Acceptable Thresholds for Service Levels, e.g.
at peak loading, some transactions fail to meet Minimum Acceptable Thresholds,
but on average all transactions within the service do achieve Minimum Acceptable
Thresholds.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 28 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
6.3 LOW SEVERITY INCIDENTS
Failure to meet an Acceptance Criterion that is neither visible to nor has
substantive impact on the service received by the Customer e.g. presentational,
style and other cosmetic faults that are only visible to the user.
Failure to meet an Acceptance Criterion which would have a minor impact on the
ability of the AUTHORITY or AUTHORITIES to perform their business, or where
there was a minor impact on the resources of the AUTHORITY or AUTHORITIES
necessary to overcome that impact on their business, e.g. non-production of a
weekly report, resulting in its manual transcription, which causes additional
resource or effort at ten or fewer outlets of the average duration of one hour per
week per outlet.
Failure to meet an Acceptance Criterion which would impact the security of the
service but where the workaround is as secure as the original solution (i.e. the only
impact on risk is in ensuring that the workaround is performed, but where
procedures have been agreed and are in place).
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 29 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A Criteria Wi Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
7 TEST DATA
Test data including any operator entered scripts that are required to run the
Acceptance Test are defined below.
Business Test Thread: —_Not applicable
High Level Test Plan(s): Not applicable
Organisation: Not applicable
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 30 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
8. AUTHORITY RESPONSIBILITIES
This section describes the AUTHORITY’s or AUTHORITIES’ Responsibilities in
relation to this Acceptance Test. Particular Acceptance Tests may also require
additional participation and responsibility by the AUTHORITY or AUTHORITIES.
8.1 APPOINT TEST MANAGER
The AUTHORITY or AUTHORITIES shall nominate a Test Manager and other
representatives to review the tests prior to commencement of the test.
8.2 ACCEPTANCE INCIDENT REPORTS
The nominated representatives and Test Manager shall be diligent in raising
complete, accurate and timely Acceptance Incident Reports as set out within this
Acceptance Specification.
8.3. ACCEPTANCE INCIDENT ANALYSIS REPORTS
The Test Manager shall be diligent in returning signed Acceptance Incident
Analysis Reports with their decision (e.g. Accept, Reject, Discuss) normally within
five working days, or when urgency is requested by Pathway, within two working
days of receipt from Pathway. A copy of all correspondence will be faxed to reduce
delay.
8.4 ATTENDANCE AT TRIALS AND REVIEWS
The nominated representatives shall at their discretion attend Acceptance Test
Trials and Reviews including repeat Tests at reasonable times and reasonable
locations and with reasonable advance notice by Pathway.
8.5 I MANAGEMENT AND CO-ORDINATION
The Test Manager shall be the single point of communication and co-ordination
with Pathway’s nominated Test Manager for all matters concerning this Acceptance
Test from its initial planning through to Acceptance.
8.6 PROGRESS REVIEWS
Unless otherwise waived by both parties, Pathway’s Test Manager and the
AUTHORITY’s or AUTHORITIES’ Test Manager shall meet each week to review the
progress and actions of both parties until Acceptance of the Acceptance Test is
achieved, The time and location of review meetings will be scheduled with at least
two week’s advance notice by Pathway.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 31 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
ceeptance Criteri tna. Ref.: CR/ACS/o20
ICL A on ta Wh Version: 1.0
Pathwoy Schedule CS Date: 24/12/98
Acceptance Specification
9. CONTRACTOR RESPONSIBILITIES
The Contractor shall nominate a Test Manager for each Test who shall be the single
point of communication and co-ordination with the AUTHORITY’s or
AUTHORITIES’ Test Manager for all matters concerning this Acceptance Test from
its initial planning through to Acceptance.
Upon receipt of a signed Acceptance Incident Analysis Report from the
AUTHORITY or AUTHORITIES, where correction is required to be re-tested within
the same phase of Acceptance Test, the Contractor will return the amended
component(s), on average, within 4 days. This will include re-testing necessary as
per the agreed test strategies.
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORNAT ]
CONTRACT CONTROLLED Page 32 of 33
obligations or creating new contractual obligations between ICL Pathway andl the DSS and/or
POCL.
FUJ00119617
FUJ00119617
we sae Ref.: CR/ACS/o20
ICL Acceptance Criteria Within Schedule C3 Version: 1.0
Pathway Acceptance Specification Date: 24/12/98
1o. ACCEPTANCE TRIAL TEST CONDITIONS
© 1998 ICL Pathway Ltd COMMERCIAL IN CONFIDENCE Printed on: [ DATE \*
MERGEFORMAT ]
Page 33 of 33
Nothing contained herein shall be deemed or construed ay affecting existing contractual obligations or creating new contractual obligations between ICL
Pathway and the DSS and/or POCL.