ICL
Pathway
ICL Pathway New Release 2
Contents Description
FUJ00119599
FUJ00119599
Ref: PA/STR/009
Version: 2.0
Date: 24/02/98
Document Title:
Document Type:
Abstract:
Status:
Distribution:
Author/Editor:
Comments to:
Comments by:
File Reference:
Pathway New Release 2 Contents Description
Definition Document
‘This document defines the functional content of New Release 2
Steady State Services.
Issued
PDA - Colin Oudot (For onward controlled distribution)
Pathway Approval Authorities (Listed in this document)
Plus:
Pathway - Dominic Barton
Pathway - John Bennett
Pathway - Alan D’Alvarez
Pathway - Barrie Davies
Pathway - John Dicks
Pathway - Janet Dore
Pathway - Liam Foley
Pathway - Jan Holmes
Pathway - Graham King
Pathway - Peter Lindsey
Pathway - Ian Morrison
Pathway - Tony Oppenheim
Pathway - Barry Procter
Pathway - Martin Riddell
Pathway - Roy Smethurst
Pathway - Chtis Wannell
Pathway - Library
Martyn Hughes
Dick Long
RCD-v2.0.doc
© 1997 ICL Pathway Ltd
COMMERCIAL IN CONFIDENCE
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Version: 2.0
Pathway Contents Description Date: 24/02/98
0 DOCUMENT CONTROL
0.1 DOCUMENT HISTORY
Version Date Reason
0.1 23/07/97 First Draft for Pathway internal use
0.2 31/07/97 Revisions following internal Pathway reviews
0.3 03/08/97 Addition of Release 1e Inclusions
0.4 07/08/97 Revisions following internal Pathway reviews
1.0 26/09/97 Baseline & place under Change Control following feedback &
revisions from wider Pathway audience & initial PDA responses
11 30/10/97 Revisions and restructuring following Pathway re-plan & associated
gap analysis
1.2 16/11/97 Revisions and restructuring following major reviews
2.0 13/02/98 Major review during NR2 re-plan
0.2 APPROVAL AUTHORITIES
Name Position Signature Date
Mike Coombs Director Programmes
Terry Austin Director Systems
Martyn Bennett Director Quality & Risk
Stephen Muchow Director Customer Services.
Richard Long System Design Manager
Chris Humphries — Software Development Manager
Steve Warwick Product Manager - Counter Systems
Bill Hillyard Product Manager - Central Systems
Peter Sewell Product Manager - System Infrastructure
Chris Wannell ‘Technical Integration Manager
John Wooler Testing & Integration Manager
Martyn Hughes Release 2 Manager
wy
COMMERCIAL IN CONFIDENCE
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Version: 2.0
Pathway Contents Description Date: 24/02/98
0.3 ASSOCIATED DOCUMENTS
Reference Vers Date Title
[1] CR/FSP/0004 4.0: 30/09/97 Service Architecture Design Documentation
[2] RS/FSP/0001 3.0. -——:03/12/97 Security Functional Specification
BB] DSs- 72 Schedule AO1 - Interpretations
BP/CON/036
POCL -
BP/CON/054
0.4 ABBREVIATIONS
The terms and abbreviations used in this document are those defined in the AUTHORITIES
Agreement [3] and in the SADD [1].
0.5 CHANGES IN THIS VERSION
Changes as documented in Document History, once basclined any changes will be maintained
using side bars.
COMMERCIAL IN CONFIDENCE 3
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Version: 2.0
Pathway Contents Description Date: 24/02/98
FUJ00119599
FUJ00119599
0.6 TABLE OF CONTENT
1.0 INTRODUCTION
1.1 SCOPE
1.2 OVERVIEW
1.3 DOCUMENT STRUCTURE
1.4 SUMMARY OF CONTENT BY MAJOR COMPONENT
2.0 SADD V4.0 COMPLIANCY MATRIX
3.0 EXPLANATORY NOTES ASSOCIATED WITH THE COMPLIANCY MATRIX
3.1 PFISERVICE ARCHITECTURE
CARD MANAGEMENT SERVICE,
3.3 PAYMENT AUTHORISATION SERVICE
3.4 COMMON PAS AND CMS SERVICE
3.5 DSS SERVICE INFRASTRUCTURE
3.6 DSS SERVICE ENVIRONMENT
3.7 BES AND PCDF
3.8 APS
3.9 EPOSS SERVICE - EPOSS ADMINISTRATION
3.10 ORDER BOOK CONTROL SERVICE
3.11 POCL INFRASTRUCTURE SERVICES,
3.12 POCL CONTINGENCY SERVICES
3.13 APPENDIX B
4.0 SFS
Dun
a
12
COMMERCIAL IN CONFIDENCE
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Pathway a Version: 2.0
Contents Description Date: 24/02/98
1.0 INTRODUCTION
1.1 SCOPE
The Related Agreements define a Release to be a documented collection of software and/or data
provided by the CONTRACTOR to deliver a Service.
This document describes the planned contents for New Release 2 (NR2).
1.2 OVERVIEW
‘The Releases identified as Pathway Release 1e and Pathway Release 2 no longer exist and have
effectively been withdrawn. NR2 has been created by Pathway in their place, in order to establish
a Release based on what was previously Release Le and re-prioritised elements of what was
Release 2.
The major new business components of this Release are:
the encashment processes
Help Desk support for the introduction of ‘Temporary Tokens
a CAS on-line interface.
Functionality will be delivered to provide:
BPS end to end service
EPO!
APS (covering magnetic stripe card and bar coded bills)
the technical and security infrastructure to support these services
To provide a method by which Pathway’s central systems will link directly to CAPS 3.0,
HAPS, ‘TIP and POCL RDS.
Migration will be from Release 1c (interfacing with CAPS 3.0) to NR2 (interfacing with CAPS 3.0
- Nile 2); to enable the Live Trial and contractual acceptance process.
COMMERCIAL IN CONFIDENCE 5
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Version: 2.0
Pathway Contents Description Date: 24/02/98
1.3 DOCUMENT STRUCTURE
Section 1 - provides an overview of the contents of NR2. It provides a high level view of the end
user functionality that will be delivered as a part of this Release. This is provided by major
component and is not exhaustive.
Section 2 - provides a detailed statement of compliance against SADD v4.0 [1].
Section 3 - provides explanatory notes by reference to SADD v4.0 [1] paragraph numbers.
Section 4 - provides a statement of conformance of the SFS [2].
COMMERCIAL IN CONFIDENCE 6
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Version: 2.0
Pathway Contents Description Date: 24/02/98
1.4 SUMMARY OF CONTENT BY MAJOR COMPONENT
‘The new and changed functionality for New Release 2, for each major component is:
‘Component Changes
CMS 1. Provide management of the production, automatic renewal, issue and
distribution of Temporary Tokens
2. Implement new name validation
Support for CAPS On-line interface
4, Software Support for cards:
© Multiple Agency (SSA, WPA)
© Bilingual cards
© New card issued on Change of Nominated Post Office while
card in production o delivery or collection
Support for all other Payee Roles that can map to the agreed
encashment rules identified under the following roles:
© Beneficiary
© Permanent Agent
© Carded Casual Agent
© Alternative Payee
© Appointee
6. Support for enquiries on archived information
Additional card management:
© stop cards for customers no longer of interest
© control card ordering via cardholder
© changed wording on PUNs
© inhibit PUN for undeliverable address
.
.
2
gn
automatic generation of replacement card
‘Temporary Token event types and codes
© Temporary Token Books event types and codes
8. Business objects for:
* second reminder PUNs
* n0n-collection of cards
9. De La Rue functionality:
© card batch tra
CMS Help Desk 10. Support for functionali
© Support of customer requiring on-going supply of Temporary
Tokens maintaining replenishment thresholds and quantities
© Support via Reference Data changes to delivery addresses for
TTs
© Maintain TT order status and TT status
© Use of BA Codes File
Emergency TT Orders in English and English/Welsh leading
to production, distribution and assigament
Support Emergency TT Batch Orders
Allow bulk stops of batch of TTs
Allow cancellation of TT Orders
Reporting of lost, stolen and damaged Temporary Tokens
Issue of TT Stops
Allow TT encashments at Specified Office by beneficiary or
agent
© Associate pre-authorised temporary agent with Temporary
‘oken to encash existing payments
* Toassign TT to existing cardholders whose personal details
and trace via Royal Mail
COMMERCIAL IN CONFIDENCE 7
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Pathway a Version: 2.0
Contents Description Date: 24/02/98
remain unchanged
© Accept CAPS assignment of a TT to a customer with a
Specified Office
© Accept with TT assignment instructions to reissue replacement
card
© Ensure any existing payments, pending payments or urgent
payments for which the customer is a payee are associated with
a TT when TT assignment received from CAPS
© Transfer any uncollected payments to pending file on expiry of
TT if not collectable by another customer
© To stop expired TT's
Ensure that an active card or TT invalidated when new TT.
issued to customer
© Support separate Urgent Payment and Temporary Token
assignment notifications from CAPS,
Support EVP on TT encashments
Help Desk Emergency Store
Allow searching using surname, initial and first line of address
Provide call logging
Distribute TT's via Royal Mail using Track and Trace and
invalidate those not received within three working days
© Support notification of emergency orders
eevee
© Support TT ordered and received reconciliation enquiries
11. Maintenance:
«Restrictions on creating users
PAS 72, Support payments:
© Collected by IT by enriching them with TT details
© Allowing association of any existing payments to a TT when
card lost, stolen or damaged beyond use
For Temporary Agent with a card at a Nominated Post Office
For Temporary Agent with a'TT at a Specified Post Office
Optional single payment associated with TT assignment
Where RPOT is introduced via the CAPS On-line interface
Immediate processing of payment stops introduced via CAPS
On-line interface
© To report unmatched CAPS On-line payments stops
13. Support customers of temporary interest:
© Introduced urgently
© Discontinue temporary agency on expiry of TT and archiving/
purging records after 90 days or payments expired
© Allow new card details to be introduced during TT assignment
© Transfer any uncollected payments to pending file on expiry of
TT if not collectable by another customer
14, Support checks that:
© non-urgent payments refer to known customer who is
currently of interest
eo eeee
© at least one payee has valid card or TT
© TAis not already a payee for beneficiary or appointee payment
15, Support Change of Nominated Post Office:
© Inform customer immediately if request is accepted
© Change immediat:
© Forward change to CAPS overnight
© Not allow change using TT
* Notallow change by Carded Casual Agent
16. Contingency payment support:
COMMERCIAL IN CONFIDENCE 8
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Pathway wo Version: 2.0
Contents Description Date: 24/02/98
© Based on last authorised payment details
17. Reporting Supported:
© Attempted RPOT infringements on foreign encashments
© Attempted RPOT infringements on Change of Nominated
Post Office
PAS Help Desk 18. Support for functionali
* Provide call logging
Support EVP on TT encashments
Common CMS & PAS 19. Support for functionality:
© Warnings exception reporting
© Audit trail for cards and collateral
© Audit trail for cardholders, beneficiaries and payments
© Re-assignment of outstanding payments on change of
nominated post office (this actioned overnight, including
changes notified via CAPS on-line)
© Check on Restricted Post Office Indicator on change of
nominated post office
© Notify CAPS of change of nominated post office
© Exception reporting to DSS via FRMS of rejected change of
nominated post office due to Restricted Post Office Indicator
© Maintenance of benefit payment references
© Deletion of cardholders no longer of interest after 90 days
20. DSS Management Information changes:
© Change to delivery mechanism for electronic reports
© Card issued report to include analysis by reason for issue and
reporting by DSS issuing office
Calls received report to include by BA Region
Length of call report to include by BA Region
Encashment reports on Appointees
Foreign encashment reports to include Appointees
‘Temporary Tokens issued report to include issued, impounded
and expired by issuing office
© Cards activated report to include issuing office
21. Accounting changes:
* Corrections to brought forward figures for late polling
changes:
© Support CAPS on-line interface
23. PAS Reconciliation changes:
* Reconciliation on the value of tokens
eeeee
22. CA
* Reconciliation of stops received via CAPS on-line interface
© Reconciliation of exception report including duplicate
payments
* Corrections to the calculation of unencashed balances
24, CMS Reconciliation:
* Reporting on offices where TT ava
ability is zero
© Reports on cards required but not available and cards no
longer required (end of interest)
upport of functionality:
BES/PCDF
© Audit report showing cumulative card position in office
© Routine card collection without PUN including EVP
© Support automatic system impounding of Ts including
production of a receipt
© Support clerk activated impounding of TTs
* Reporting on impounded TTs on daily, weekly and ad-hoc
basis by reasons of counterfeit suspected, fraud suspected and
COMMERCIAL IN CONFIDENCE 9
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Pathway a Version: 2.0
Contents Description Date: 24/02/98
other reasons
BES 26. Support of functionality:
© Support customer using TT for encashments at a specified
office only reading the bar-code or by manual entry
Support for previously authorised casual agent with TT
Receipt printing in English and English/Welsh as appropriate
Display of TT Id where used
Receipt printing to include beneficiary’s name and NINO as
well as Appointee’s name and NINO in Appointee case
* Correction to thousand pound threshold calculation to sort
first by recurring payments before non-recurring payments
© Support for enforcing geographical restrictions on
encashments informing the clerk of the attempted
eoee
infringement
© Prevention of foreign encashments by card carrying casual
agents
© Foreign encashment counting to take into account emergency
closures
© Help Desk support for foreign encashments during roll-out
© Encashment involving non-recurring benefits to be excluded
from foreign encashment counting
© Support for informing clerk that a foreign encashment has
been attempted when RPOT is set
© RPOT to be applied to a cardholder
© Support for informing the clerk when the foreign encashment
limit has been reached and for the case where a foreign
encashment will bring the customer up to the limit
© Provision of the date of next allowable foreign payment on the
last foreign payment allowed
© Support for carded casual agent encashments including EVP
‘on agent
© Support for carded temporary agents
© Support for change of nominated post office including
informing the clerk if the change is denied due to RPOI and
asking EVP
POCL Contingency Services I 27. Support of functionality:
© Support for Manual input of TT Ids
© Support for Appointee details on receipts
© Support for manual impound receipts
© Provide reconciliation of Help Desk encashments and counter
amounts
© Provide EVP on Help Desk change of nominated post office
«Provide temporary transfer of payments to another office
Fraud Risk Management 28. Support of functionality:
© Reporting on fraudulent transactions by Alternative Payees,
Casual agents
© Reporting on customers who have attempted to infringe
Change of Nominated Post Office RPOT rule
© Reporting on TTs impounded and returned to FRMS, that is
defaced, counterfeit suspected, details mismatch
APS 29. Support of functionality:
© AP magnetic card and barcode tokens
© AP counter transaction (normal, recovery, fallback and
manual)
© _AP transaction files sent to HAPS daily
COMMERCIAL IN CONFIDENCE 10
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref.: PA/STR/009
Version: 2.0
Pathway Contents Description Date: 24/02/98
OBCS 30. Support of functionality:
*_OBCS Help Desk
EPOSS 31. Support of functionality
¢ Product/Service distribution and availability
© Customer session and desktop transactions control (including
reports and receipts)
© Counter transaction definition
¢ Administration functions
© Stock transfers, remittances and stock unit balancing
© User and Stock Unit Maintenance
© Cash Account
© Control and maintenance of local ref. Data centrally
.
Training Mode
COMMERCIAL IN CONFIDENCE 1
FUJ00119599
FUJ00119599
ICL ICL Pathway New Release 2 Ref: PA/STR/009
Pathway a Version: 2.0
Contents Description Date: 24/02/98
2.0 SADD V4.0 COMPLIANCY MATRIX
2.1 This section categorises each paragraph in the SADD v4.0 that describes the
functionality of the system. The following categories have been used:
- Paragraph has no content.
I The functionality described in the paragraph is included in NR2.
Where a paragraph in the SADD contains a statement that a
facility will not be available, an I indicates that the non-
availability continues at NR2.
P This indicates partial satisfaction of the paragraph. For each
paragraph in this category there will be a corresponding entry in
the Explanatory Notes section for this paragraph number. This
provides clarification of what is not to be provided.
Cc This indicates that a Clarification note appears in the
Explanatory Notes section associated with this paragraph
number.
E This indicates the functionality is excluded from NR2.
COMMERCIAL IN CONFIDENCE 12