FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Ret PASTRIOI2
ersion:
Contents Description Date:25/06/99
Document Title: ICL Pathway Core System Release Contents Description
Document Type: Definition Document
Abstract: This document defines the functional content of the Core
System Release Services.
Status: Approved
Distribution: Horizon/POCL Library
ICL Pathway Library
Terry Austin
Stephen Muchow
John Dicks
Author: Joan Patterson
COMMERCIAL IN CONFIDENCE Page 1 of 1
© 1999 ICL Pathway Ltd
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Ret PASTRIOI2
‘ersion:
Contents Description Date:25/06/99
0 DOCUMENT CONTROL
0.1 DOCUMENT HISTORY
Version Date Reason
0.1 08/06/99 First Draft for ICL Pathway internal use.
0.2 15/06/99 Second draft reflecting initial comments received.
0.3 16/06/99 Third draft reflecting comments received from Informal review.
0.4 22/06/99 Fourth draft incorporating Formal review comments.
Ready for Pathway Approval.
1.0 25/06/99 Pathway Approved
0.2 APPROVAL AUTHORITIES
Name Position Signature Date
Terry Austin Director Development
Stephen Muchow Director Customer Service
John Dicks Director Customer Requirements.
COMMERCIAL IN CONFIDENCE Page 2 of 1
ICL Pathway
FUJ00078801
FUJ00078801
ICL Pathway Core System Release Ref.:PA/STR/012
wae Version:1.0
Contents Description Date:25/06/99
0.3 ASSOCIATED DOCUMENTS
(1)
[2]
[3]
(4]
Reference
CR/FSP/0004
RS/FSP/0001
DSS -
BP/CON/036
POCL -
BP/CON/054
PA/STR/009
Vers
4.0
3.0
7.2
2.0
Date Title
30/09/97 Service Architecture Design
Documentation
03/12/97 Security Functional Specification
Schedule A01 - Interpretations
24/02/98 ICL Pathway New Release 2 Contents
Description
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 baselined any changes will be
maintained using side bars.
COMMERCIAL IN CONFIDENCE Page 3 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release Ref.:PA/STR/012
Version:1.0
Contents Description Date:25/06/99
0.6 TABLE OF CONTENT
1.0 INTRODUCTION 5
1.1. SCOPE 5
1.2 OVERVIEW 5
1.3. DOCUMENT STRUCTURE 6
1.4 SUMMARY oF CONTENT BY MAJOR COMPONENT 7
2.0 SADD V4.0 COMPLIANCY MATRIX 8
3.0 EXPLANATORY NOTES ASSOCIATED WITH THE COMPLIANCY MATRIX 30
3.1 PFI SERVICE ARCHITECTURE 30
3.2 DSS SERVICE ARCHITECTURE 31
3.3. POCL SERVICE ARCHITECTURE 31
3.3.1. BENEFIT ENCASHMENT SERVICE 31
3.3.2 APS 31
3.3.3. EPOSS SERVICE 32
3.3.4 ORDER BOOK CONTROL SERVICE 34
3.3.5 I POCL INFRASTRUCTURE SERVICES 35
3.3.6 POCL CONTINGENCY SERVICES 37
3.4 APPENDIX B 40
4.0 SFS 42
ADDENDUM A: DSS AND BENEFIT PAYMENT CARD EXCLUSIONS 44
ADDENDUM B: CCNS COMPREHENDED 58
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD 84
COMMERCIAL IN CONFIDENCE Page 4 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release Ref.:PA/STR/012
Version:1.0
Contents Description Date:25/06/99
1.0 INTRODUCTION
1.1 SCOPE
The Agreement defines 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 the Core System Release (CSR).
1.2 OVERVIEW
The Releases identified as Pathway Release 1e and Pathway Release 2 no longer
exist and have effectively been withdrawn. New Release 2 [4] was created by ICL
Pathway in their place, in order to establish a Release based on what was previously
Release 1e and re-prioritised elements of what was Release 2. The changes brought
about by the outcome of the Treasury Review, which requires exclusion of DSS
related functionality and services, has given rise to this release which is known as
the Core Systems Release (CSR).
Any reference to the previous contract (PFI) will need to be interpreted in line with
the revised contract which is a Public Private Partnership (PPP)contract.
Functionality will be delivered to provide:
EPOSS
OBCS
APS (covering magnetic stripe card and bar coded bills)
the technical and security infrastructure to support the above services
a method by which ICL Pathway’s central systems will link directly to Host APS
(HAPS), TIP and POCL Reference Data System (RDS).
COMMERCIAL IN CONFIDENCE Page 5 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release Ref.:PA/STR/012
Version:1.0
Contents Description Date:25/06/99
1.3. DOCUMENT STRUCTURE
Section 1 - provides an overview of the contents of CSR. 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 v3.0 [2].
Addendum A — provides a list of SADD v4.0 [1] paragraphs which are no longer
required due to termination of the DSS contract and removal of the Benefit Payment
Card.
Addendum B - provides a list of Change Control Notes comprehended and identifies
the status of each.
Addendum C — provides the list of future changes required to the SADD v 4.0 [1]
which was provided by Horizon as a caveat to the approval of this document. The
status of each change is documented.
COMMERCIAL IN CONFIDENCE Page 6 of 1
ICL Pathway
FUJ00078801
FUJ00078801
ICL Pathway Core System Release Ref.:PA/STR/012
wg Version: 1.0
Contents Description Date:25/06/99
1.4 SUMMARY OF CONTENT BY MAJOR COMPONENT
The functionality provided by the Core System Release, for each major component is:
[Component
(Changes
APS
1. Support
.
.
.
of functionality:
AP magnetic card and barcode tokens
AP counter transaction (normal, recovery, fallback and
manual)
AP transaction files sent to HAPS daily
(OBCS
2. Support
of functionality:
OBCS Help Desk
Receipt/dispatch of data to/from ESNS.
Enrichment of stop records
Dispatch of stop records to outlets
Management/updating of central/local stop lists
Creation/management of central/local CRNF
Recording checking in of Order Books
Recording handing over of Order Books to Customers
Payment using Order Books
IEPOSS
3. 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
COMMERCIAI
LIN CONFIDENCE Page 7 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release Ref.:PA/STR/012
Version:1.0
Contents Description Date:25/06/99
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
CSR. 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 CSR.
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 CSR.
D DSS functionality excluded
COMMERCIAL IN CONFIDENCE Page 8 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ret PUSTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
2. PFl SERVICE ARCHITECTURE :
2.1 PFI SERVICE INFORMATION FLOWS c/D
[2.2 PATHWAY SERVICE COMPONENT RELATIONSHIPS c/D
2.3 BPS END-TO-END SERVICE DEFINITION E/D
2.4 BUSINESS CONTINUITY :
2.4.1 CONTINGENCY VD
12.4.2 PATHWAY BUSINESS CONTINUITY l
2.5 SECURITY INFRASTRUCTURE -
2.5.1 INTRODUCTION c/D
[2.5.2 FRAUD RISK MANAGEMENT SERVICE E/D
2.6 DATA PROTECTION ACT, 1984 Cc/D
2.7 OPERATIONAL AUDIT Cc/D
3. DSS SERVICE ARCHITECTURE E/D
COMMERCIAL IN CONFIDENCE
Page 9 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ret PUSTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4. POCL SERVICE ARCHITECTURE =
4.1 POCL STEADY STATE SERVICES :
4.1.1 BENEFIT ENCASHMENT SERVICE/PATHWAY CARD DISTRIBUTION FACILITY E/D
4.1.2 AUTOMATED PAYMENT SERVICE
4.1.2.1 INTRODUCTION
4.1.2.2 STEADY STATE SERVICE
4.1.2.2.1 APS architecture overview
4.1.2.2.2 Tokens Supported
4.1.2.2.3 APS Scope
4.1.2.3 APS FUNCTIONAL SUMMARY
4.1.2.3.1 APS Host Function Summary
4.1.2.3.2 APS Counter Function Summary
4.1.2.4 APS HOST FUNCTIONS
4.1.2.4.1 Receive Reference Data
4.1.2.4.2 Receive Client Data
4.1.2.4.3 Despatch Client Transaction Data
4.1.2.5 APS COUNTER FUNCTIONS
4.1.2.5.1 Counter Process Summary
4.1.2.5.2 Process 1 and 2 - Read And Validate Token
—Iv]o]a]mI—Io}—]—I—]-0}-0/—I-J-I
COMMERCIAL IN CONFIDENCE
Page 10 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.2.5.3 Process 3 / 4 - Process And Record APS Transaction
4.1.2.5.4 Using A Magnetic Card
4.1.2.5.5 Using A Smart Card Or Smart Key
4.1.2.5.6 Using A Bar-Coded Document
4.1.2.5.7 Sale Of Meter Tokens
4.1.2.5.8 Transaction Selection
4.1.2.5.9 Transaction Committal
4.1.2.6 AP TOKEN ISSUE
4.1.2.7 APS OUTPUTS
4.1.2.7.1 APS Receipts
4.1.2.8 TRANSACTION RECOVERY
4.1.2.9 TRANSACTION REVERSALS
4.1.2.10 APS MIGRATION
4.1.2.10.1 Migration to TIP
4.1.2.10.2 Migration for existing AP Clients
4.1.2.11 EXTENSIONS TO APS
Q/0}—I—I—I—Io}-0Im}-0]—I—]—}mI—I-0
COMMERCIAL IN CONFIDENCE
Page 11 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.3 EPOS SERVICE
4.1.3.1 EROSS COUNTER TRANSACTIONS,
4.1.3.1.1 Product / Service Distribution and Availability
4.1.3.1.2 Stock Items
4.1.3.1.2.1 STOCK UNIT
4.1.3.1.2.2 STOCK UNIT STATUS
4.1.3.1.2.3 READY STATE
4.1.3.1.2.4 CUSTOMER PERCEPTION
4.1.3.1.2.5 POST SHOP FUNCTIONALITY
4.1.3.1.3 The Customer Session
4.1.3.1.4 Customer Session Log
4.1.3.1.5 Methods Of Payment (MoP)
4.1.3.1.6 Reports & Summaries
4.1.3.1.7 Desktop Transactions
4.1.3.1.8 Other Transactions
4.1.3.1.9 Modify A Transaction
4.1.3.1.10 Void A Transaction
4.1.3.1.11 Reverse A Transaction
4.1.3.1.12 Settle And Commit A Transaction c/D
4.1.3.1.13 Abandon A Customer Session
oI—I—I-0]—I-Jo}-IvJo]—I:
COMMERCIAL IN CONFIDENCE
Page 12 of 1
ICL Pathway ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
SADD V4.0 REFERENCE
CSR STATUS
4.1.3.1.14 Session Settlement
4.1.3.1.15 End Customer Session
4.1.3.1.16 Commit Transactions
4.1.3.1.17 Start A New Customer Session
4.1.3.1.18 Suspend And Resume Customer Session
4.1.3.1.19 Print A Session Receipt
4.1.3.1.20 Print A Duplicate Receipt
4.1.3.2 EPOSS COUNTER TRANSACTION DEFINITIONS
4.1.3.2.1 Content Driven Functionality
4.1.3.2.1.1 THE SCOPE FOR NEW TRANSACTION INTRODUCTION
4.1.3.2.1.2 INITIAL LEVELS OF FUNCTIONALITY
4.1.3.2.2 Multi-group Architecture
4.1.3.2.2.1 THE BUSINESS GROUP.
4.1.3.2.2.2 THE PRESENTATION GROUP
4.1.3.2.2.3 THE ACCOUNTING GROUP
4.1.3.2.3 Entities Within Groups
4.1.3.2.3.1 BUSINESS GROUP OBJECTS
4.1.3.2.3.2 BUSINESS GROUP OBJECTS ATTRIBUTE GRAMMAR
4.1.3.2.3.3 PRESENTATION GROUP OBJECTS
4.1.3.2.3.4 PRESENTATION GROUP OBJECTS ATTRIBUTE GRAMMAR
P
l
P/D
i
ej
c/D
i
l
l
l
ej
I
l
i
l
i
I
I
P
l
COMMERCIAL IN CONFIDENCE
Page 13 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.3.2.3.5 ACCOUNTING GROUP OBJECTS
4.1.3.2.4 Transaction Products And Their Objects
4.1.3.2.5 Automated Products
4.1.3.2.5.1 ILLUSTRATIVE EXAMPLES
4.1.3.3 EPOSS ADMINISTRATION
4.1.3.3.1 Access Control
4.1.3.3.1.1 PASSWORD USAGE
4.1.3.3.1.2 FUNCTION SELECTION
4.1.3.3.2 Counter Administration
4.1.3.3.2.1 THREE METHODS OF WORKING
4.1.3.3.2.1.1 Support for Individual Clerk Accountability
4.1.3.3.2.1.2 Support for Team Working
4.1.3.3.2.1.3 Support for Sub Post Office Accounting
4.1.3.3.2.2 SHARING A STOCK UNIT
4.1.3.3.2.3 ATTACH A STOCK UNIT
4.1.3.3.2.4 START A NEW STOCK UNIT BALANCE PERIOD
4.1.3.3.2.5 DETACH A STOCK UNIT
4.1.3.3.2.6 STOCK TRANSFERS
4.1.3.3.2.6.1 Transfer Request
4.1.3.3.2.6.2 Transfer Out
-I-I-I-I-I-}2I5]-I-I-]2Jo}-
-I-I-lol-I5
COMMERCIAL IN CONFIDENCE
Page 14 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.3.3.2.6.3 Transfer In
4.1.3.3.2.6.4 Transfer Completion
4.1.3.3.2.7 REMITTANCES
4.1.3.3.2.7.1 Remittances In
4.1.3.3.2.7.2 Remittances Out
4.1.3.3.2.7.3 Remittance Completion
4.1.3.3.2.8 STOCK UNIT BALANCING
4.1.3.3.2.8.1 Declare Stock in Hand
4.1.3.3.2.8.2 Print Stock in Hand Report
4.1.3.3.2.8.3 Declare Cash in Hand
4.1.3.3.2.8.4 Daily Cash Locked Up
4.1.3.3.2.8.5 Produce Balances
4.1.3.3.2.8.6 Declare Losses and Gains
4.1.3.3.2.8.7 Clear Losses and Gains
4.1.3.3.2.8.8 Dormant and Resting Stock Units
4.1.3.3.2.8.9 Adjustments
4.1.3.3.2.9 DISPLAY AND PRINT REPORTS AND CLIENT SUMMARIES
4.1.3.3.2.10 AP CLIENT TRANSACTION CUT-OFFS
4.1.3.3.2.11 END OF DAY
4.1.3.3.2.12 ROLL-OVER
o}—ImI—I-I—I-I—I—]-}-I-I-I-]-}-}-I-I-]-
COMMERCIAL IN CONFIDENCE
Page 15 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ret PUSTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.3.3.3 Office Administration
4.1.3.3.3.1 USER MAINTENANCE
4.1.3.3.3.1.1 Add User
4.1.3.3.3.1.2 Remove User
4.1.3.3.3.1.3 Modify User Details
4.1.3.3.3.2 STOCK UNIT MAINTENANCE
4.1.3.3.3.2.1 Add Stock Unit
4.1.3.3.3.2.2 Remove Stock Unit
4.1.3.3.3.2.3 Modify Stock Unit
4.1.3.3.3.3 ATTACH/DETACH A STOCK UNIT
4.1.3.3.4 The Cash Account
4.1.3.3.4.1 OFFICE BALANCE (WEEKLY CASH BOOK)
4.1.3.3.4.2 NON-ACCOUNTING DATA
4.1.3.3.4.3 END OF ACCOUNT
4.1.3.3.4.4 ACCOUNTING ADJUSTMENTS
4.1.3.3.4.5 TRANSACTION REVERSALS
4.1.3.3.4.6 STOCK RECORD ADJUSTMENTS
4.1.3.3.4.7 OFFICE REPORTS
4.1.3.3.4.8 REVALUATIONS
4.1.3.3.5 Reference Data Local Maintenance
—}—}—I—}—I—I—I—]—IJ-—J-J-J—}) J-J—J—}e J-
COMMERCIAL IN CONFIDENCE
Page 16 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.3.3.5.1 MAINTAIN OFFICE DATA
4.1.3.3.5.1.1 Office Details
4.1.3.3.5.1.2 Cash Totals
4.1.3.3.5.1.3 Balance / Daily Cash Book Printing Options
4.1.3.3.5.1.4 Cash Account Dates
4.1.3.3.5.1.5 Preferences
4.1.3.3.6 Training Mode
4.1.3.3.6.1 TRAINING STOCK UNIT
4.1.3.3.6.2 WORKING IN TRAINING MODE
4.1.3.3.6.3 EXITING TRAINING MODE
4.1.3.3.6.4 CREATING TRAINING STOCK UNITS
4.1.3.3.6.5 INDICATING TRAINING MODE IS ACTIVE
4.1.3.3.6.6 TRAINING MODE COUNTER OPERATION
4.1.3.3.6.7 EXCLUDING TRAINING FROM ACCOUNTING
4.1.3.3.6.8 USING TRAINING DATA
4.1.3.3.6.9 HOW TMS HANDLES TRAINING TRANSACTION DATA
4.1.3.3.7 Broadcasts & Documents
4.1.3.3.7.1 BROADCASTS,
4.1.3.3.7.2 DOCUMENTS.
QOJNJNJONJOIOJ\O}—I—I—-I-I-I—
Q
fe)
[o)
mjmyj +
COMMERCIAL IN CONFIDENCE
Page 17 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ret PUSTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.4 ORDER BOOK CONTROL SERVICE
4.1.4.1 OBCS OVERVIEW
4.1.4.2 OBCS FUNCTIONS
4.1.4.2.1 OBCS Host Functions
4.1.4.2.2 Stop List processing
4.1.4.2.2.1 CENTRAL STOP LIST
4.1.4.2.2.2 LOCAL STOP LIST
4.1.4.2.2.3 LOCAL CRN FILE
4.1.4.2.2.4 CENTRAL CRN FILE
4.1.4.2.2.5 INITIAL IMPLEMENTATION
4.1.4.2.3 OBCS Counter Functions
4.1.4.2.3.1 RECEIPT OF BAR-CODED ORDER BOOK IN POST OFFICE (OBCS)
4.1.4.2.3.1.1 Steady State Service Provision
4.1.4.2.3.1.2 Outputs
4.1.4.2.3.2 HANDOVER OF ORDER BOOK TO CUSTOMER (OBCS)
4.1.4.2.3.2.1 Steady State Service Provision
4.1.4.2.3.2.2 Outputs
4.1.4.2.3.3 BENEFIT ENCASHMENT USING FOIL (OBCS)
4.1.4.2.3.3.1 Steady State Service Provision
4.1.4.2.3.3.2 Outputs
lo}: I—lo}—I-lo]—I—I-I-I-]-I-} + I2]—I2Jo
COMMERCIAL IN CONFIDENCE
Page 18 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ret PUSTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.5 POCL INFRASTRUCTURE SERVICES -
4.1.5.1 OFFICE PLATFORM SERVICE P/D
4.1.5.1.1 Standard Configuration i
4.1.5.1.1.1 USABILITY i
4.1.5.1.1.2 AVAILABILITY I
4.1.5.1.1.3 SECURITY I
4.1.5.1.1.4 POTENTIAL FOR CHANGE I
4.1.5.1.2 Standard Configuration Details P/D
4.1.5.1.3 Back Office Configuration c/D
i
I
I
I
i
/I
I
4.1.5.1.4 Equipment Substitution
4.1.5.1.5 Optional POCL Requirements
4.1.5.1.6 Space Constraints
4.1.5.1.7 Mobile Configuration E,
4.1.5.1.8 Final OPS Configuration
4.1.5.2 TRANSACTION MANAGEMENT SERVICE
4.1.5.2.1 Introduction c/D
4.1.5.2.2 Commercial Attributes
4.1.5.2.2.1 DISCRETENESS Cc/D
4.1.5.2.2.2 SCALEABILITY I
4.1.5.2.2.3 EXCLUSIVITY c/D
COMMERCIAL IN CONFIDENCE
Page 19 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ret PUSTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.5.2.3 Functions To Be Supported -
4.1.5.2.3.1 CONNECTION c/D
4.1.5.2.3.2 COMMUNICATIONS ACCESS SUPPORT l
4.1.5.2.3.3 INTERFACE SUPPORT P/D
4.1.5.2.3.4 DATA TRANSFER ATTRIBUTES I
4.1.5.2.3.4.1 Ruggedness Of Distributed Database c/D
4.1.5.2.3.4.2 Data Integrity I
4.1.5.2.3.4.3 Data Privacy I
4.1.5.2.3.4.4 Data Currency c/D
4.1.5.2.3.5 DATA TRANSFER OPERATIONS I
4.1.5.2.3.5.1 Files And Records I
4.1.5.2.3.5.2 File Operations I
4.1.5.2.3.5.3 File Processing I
4.1.5.2.3.5.4 Data Transfer Initiation I
/I
4.1.5.2.3.5.5 Data Transfer Retry c/D
4.1.5.2.3.6 AUDIT FACILITIES
4.1.5.3 SYSTEMS MANAGEMENT SERVICE
4.1.5.3.1 Hardware
4.1.5.3.1.1 FUNCTIONALITY SUPPORTED
4.1.5.2.3.5.6 Broadcast And Messaging Operations E
I
I
I
l
COMMERCIAL IN CONFIDENCE
Page 20 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.5.3.2 Software
4.1.5.3.2.1 SYSTEMS MANAGEMENT
4.1.5.3.2.1.1 Remote Operations
4.1.5.3.2.1.2 Statistics
4.1.5.3.2.1.3 Asset Management
4.1.5.3.2.1.4 Software Distribution
4.1.5.3.2.1.5 Configuration Management for Outlets
4.1.5.3.2.1.6 Reference Data Management
4.1.5.3.2.1.7 Event Management And Alerts
4.1.5.3.2.2 NETWORK MANAGEMENT
4.1.5.3.2.3 SECURITY SERVICES
4.1.5.3.3 Other Computer & Telecomms Equipment
4.1.5.3.3.1 HORIZON SYSTEM HELP DESK IT SYSTEMS
4.1.5.3.3.2 PATHWAY MIS
4.1.5.3.3.3 WAN INFRASTRUCTURE
4.1.5.3.3.3.1 POCL / Pathway Links
4.1.5.3.3.3.2 Pathway Inter-Site Links
4.1.5.3.3.3.3 ISDN Links Between Post Offices And Pathway
4.1.5.3.3.3.4 Third Party Links
4.1.5.3.3.4 TELEPHONE CALLS TO HELP DESKS
}—I—I—I—/-I:
RY
SG
Q\I_
S
Q
—ImI-I-JoI-I5)-I-I-
COMMERCIAL IN CONFIDENCE
Page 21 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ret PUSTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.5.4 POCL BUSINESS SERVICES
4.1.5.4.1 Transaction Information Processing
4.1.5.4.2 Inventory Management
4.1.5.5 LINKS TO POCL CLIENTS
mmals
4.1.6 POCL CONTINGENCY SERVICES -
4.1.6.1 INTRODUCTION P/D
4.1.6.2 MAGNETIC CARD READER
4.1.6.2.1 BES
4.1.6.2.2 OBCS
4.1.6.2.3 EPOSS
4.1.6.2.3.1 CONTINGENCY ARRANGEMENTS
4.1.6.2.4 APS
4.1.6.2.4.1 CONTINGENCY ARRANGEMENTS
4.1.6.2.4.1.1 Automated Payment Using Magnetic Card
4.1.6.2.4.1.2 Automated Payment Using Smart Card / Key
4.1.6.3 BAR-CODE / OCR READER
4.1.6.3.1 BES
m m
Bl P/mI—)-I2I-I-I-I5]}
COMMERCIAL IN CONFIDENCE
Page 22 of 1
ICL Pathway ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
SADD V4.0 REFERENCE
CSR STATUS
4.1.6.3.2 OBCS
4.1.6.3.2.1 CONTINGENCY ARRANGEMENTS
4.1.6.3.2.1.1 Receipt Of Order Books Into The Post Office
4.1.6.3.2.1.2 Collection Of Order Book By Customer / Benefit Encashment Using Foil
4.1.6.3.3 EPOSS
4.1.6.3.4 APS
4.1.6.3.4.1 CONTINGENCY ARRANGEMENTS
eIv)—I—I—]} + I—
4.1.6.4 SMART CARD / KEY READER / ENCODER
4.1.6.4.1 BES, OBCS, EPOSS
qa
oIS
4.1.6.4.2 APS
4.1.6.4.2.1 CONTINGENCY ARRANGEMENTS
mim
4.1.6.6 COUNTER PRINTER
4.1.6.5.1 BES
4.1.6.5.2 OBCS
4.1.6.5.3 EPOSS / APS
4.1.6.5.3.1 CONTINGENCY ARRANGEMENTS
4.1.6.6 ELECTRONIC WEIGH SCALE
4.1.6.6.1 BES, OBCS, APS
4.1.6.6.2 EPOSS
4.1.6.6.2.1 CONTINGENCY ARRANGEMENTS
COMMERCIAL IN CONFIDENCE
Page 23 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.6.7 BACK OFFICE PRINTER
4.1.6.7.1.1 CONTINGENCY ARRANGEMENTS
4.1.6.8 KEYBOARD
4.1.6.8.1 BES, OBCS, EPOSS, APS c/D
4.1.6.8.1.1 CONTINGENCY ARRANGEMENTS
4.1.6.9 TOUCH SCREEN
4.1.6.10 PC - SINGLE COUNTER OFFICE
4.1.6.10.1 BES
4.1.6.10.2 OBCS.
4.1.6.10.2.1 CONTINGENCY ARRANGEMENTS
4.1.6.10.2.1.1 Receipt Of Order Books In Post Office
4.1.6.10.2.1.2 Collection Of Order Book By Customer
4.1.6.10.2.1.3 Benefit Encashment Using Foil
4.1.6.10.3 EPOSS
4.1.6.10.3.1 CONTINGENCY ARRANGEMENTS
4.1.6.10.4 APS
4.1.6.10.4.1 CONTINGENCY ARRANGEMENTS
4.1.6.10.4.1.1 Magnetic Card Transactions
4.1.6.10.4.1.2 Smart Card / Key Transactions
Q_I_Ij_
+ fol—l—fa J—
mi—}# IUO
COMMERCIAL IN CONFIDENCE
Page 24 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
4.1.6.10.4.1.3 Bar-code / OCR Transactions P
4.1.6.11 PC - MULTI-COUNTER OFFICE -
4.1.6.11.1 BES (gateway PC) E/D
4.1.6.11.2 BES (non-gateway PC) E/D
4.1.6.11.3 OBCS -
4.1.6.11.3.1 CONTINGENCY ARRANGEMENTS I
4.1.6.11.4 EPOSS / APS :
4.1.6.11.4.1 CONTINGENCY ARRANGEMENTS I
4.1.6.11.5 PC In Mid Customer Session P/D
4.1.6.12 NETWORK - ISDN CONNECTION :
4.1.6.12.1 BES / OBCS c/D
4.1.6.12.1.1 CONTINGENCY ARRANGEMENTS I
4.1.6.12.2 EROSS / APS -
4.1.6.12.2.1 CONTINGENCY ARRANGEMENTS P
4.1.6.13 SITE RELATED I
4.1.6.13.1 BES / OBCS c/D
4.1.6.13.1.1 CONTINGENCY ARRANGEMENTS c/D
4.1.6.13.2 EROSS / APS -
4.1.6.13.2.1 CONTINGENCY ARRANGEMENTS. l
4.1.6.14 SITE RELATED FAILURE PROCEDURES l
COMMERCIAL IN CONFIDENCE
Page 25 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE
CSR STATUS
(4.1.7 OPTIONAL POCL SERVICES I I ]
4.2 POCL SERVICE ENVIRONMENT re
4.2.1 POCL COMPUTERS ]
4.2.2 TELECOMMUNICATIONS.
l
4.2.3 BUSINESS OPERATING SYSTEMS & SERVICES
COMMERCIAL IN CONFIDENCE
Page 26 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ret PUSTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
Appendix A
References to DSS components within Appendix A are to be disregarded.
When redrawn, they will show sources of Reference Data more clearly and TIP will be added where appropriate.
COMMERCIAL IN CONFIDENCE
Page 27 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ret PUSTRIOI2
‘ersion: 1.
Contents Description Date:25/06/99
SADD V4.0 REFERENCE CSR STATUS
IB.1 GENERAL PRINCIPLES
B.1.1 INTERFACE TYPES WITHIN THE SOLUTION ARCHITECTURE
IB.1.1.1 CENTRAL SERVICES LAYER
B.1.1.2 TMS LAYER
B.1.1.2.1 TMS interface with Central Services
IB.1.1.2.2 TMS interface with OPS and Counter applications
IB.1.1.3 COUNTER AND BACK-OFFICE LAYER
IB.1.1.4 END-TO END APPLICATIONS SERVICES
B.1.1.5 SOLUTION COMPONENTS & AND THE SERVICES
B.1.2 SERVICE BOUNDARIES
IB.1.2.1 PFl BOUNDARY (PATHWAY - EXTERNAL HOSTS)
IB.1.2.2 TMS UPPER BOUNDARY (HOSTS - TMS)
IB.1.2.2.1 Bulk outbound data transfer agents
IB.1.2.2.2 Bulk inbound data transfer agents
IB.1.2.2.3 Outbound interactive agents
IB.1.2.2.4 Inbound interactive agents
IB.1.2.3 TMS LOWER BOUNDARY (TMS - OPS AND COUNTER APPLICATIONS)
IB.1.2.3.1 Outbound messages arriving at OPS
B.1.2.3.2 Inbound messages created at OPS
IB.2 INTERFACES WITHIN THE END-TO-END BENEFITS PAYMENTS SERVICE
IB.3 INTERFACES WITHIN THE END-TO-END POCL SERVICES
oImI—I—lo]—I—I—I—]—}2JoJololoI—I—-]-lo}:
COMMERCIAL IN CONFIDENCE
Page 28 of 1
ICL Pathway ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
SADD V4.0 REFERENCE
CSR STATUS
B.3.1 INTERFACES WITHIN EPOSS
IB.3.1.1 POCL (RD/TIP) TO/FROM PATHWAY (RDMC/TPS)
IB.3.1.2 RDMC AND TPS TO/FROM EPOSS (VIA TMS)
IB.3.1.2.1 Downloading of reference data
IB.3.1.2.2 Uploading and Harvesting of Transaction data
IB.3.1.3 RD COLLECTIONS - EPOSS
IB.3.2 AUTOMATED PAYMENTS SERVICE INTERFACES
B.3.2.1 OVERVIEW.
IB.3.2.1.1 Initial operation via HAPS
IB.3.2.1.2 Direct Operation to POCL clients
IB.3.2.2 APS - HAPS
IB.3.2.3 APS HOST TO/FROM APS COUNTER APPLICATION
IB.3.3 ORDER BOOK CONTROL SERVICE INTERFACES
B.3.3.1 ESNS HOST TO/FROM OBCS HOST
IB.3.3.2 OBCS HOST TO/FROM OBCS COUNTER APPLICATION (VIA TMS)
-I=-I-]o}-0ImI—I—I—I-]o}-I-I-I-
COMMERCIAL IN CONFIDENCE
Page 29 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Reh PASTRION2
‘ersit
Contents Description Date:25/06/99
3.0 EXPLANATORY NOTES ASSOCIATED WITH THE
COMPLIANCY MATRIX
The following section provides details of the clarifications and
exceptions to the information held in SADD v4.0. The notes are in
SADD paragraph number sequence.
3.1 PFISERVICE ARCHITECTURE
SADD Explanatory Notes
Paragraph
2.1 IThe reference in the diagram to “IM” needs to change to
‘SAPADS”.
Figure 2-1 requires to be reworked to reflect removal of DSS and
Benefit Payment Card services and the explicit inclusion of all
(CSR services.
2.2 Figure 2-2 needs to be re-worked to show host for APS.
It needs the removal of IM.
All references in Figure 2-2 to CAPS, PAS, CMS and BES are to
be removed together with the first text bullet point and any other
references to DSS.
2.3 BPS service removed.
2.4.1 IThe references to Section 3.1.2.5.5 Contingency Payments are to
be removed.
2.5.1 IThe reference to DSS to be removed.
2.5.2 IDSS — no longer a requirement.
2.6 IThe SADD requires redraft in accordance with requirement 698.
2.7 References to DSS, the National Audit Office and BPS MIS to be
removed.
COMMERCIAL IN CONFIDENCE Page 30 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Reh PASTRION2
‘ersit
Contents Description Date:25/06/99
3.2 DSS SERVICE ARCHITECTURE
DSS Services are no longer required.
3.3. POCL SERVICE ARCHITECTURE
3.3.1. BENEFIT ENCASHMENT SERVICE
SADD Explanatory Notes
Paragraph
4.1.1 Benefit Encashment Service no longer required.
3.3.2 APS
SADD Explanatory Notes
Paragraph
4.1.2.2.2 [Tokens not supported at CSR are Landis & Gyr PISCES smart
card, GEC Meters Watercard smart card, British Gas Quantum
smart card and Schlumberger key.
4.1.2.2.3 IAPS transactions described in the “Authorities Agreement,
‘Schedule A06” and involving smart card or smart key counter
functions are excluded at CSR.
4.1.2.4 IThe diagram, Figure 4.3, needs to be re-worked to show the APS
[Host boundary clear of the main Reference Data flows and to
cover cases where client reference data goes directly to TMS. ThisI
ill be completed in the next version of the SADD.
4.1.2.4.2 [Receive Client Data - Process 2 is excluded from CSR.
IThe note on Quantum no longer applies.
4.1.2.4.3 Dispatch Client Transaction Data (direct client interfaces). Process
3 - This will be driven by the client cut over within the client
migration programme.
4.1.2.5 \Token sales are communicated to the client for the customer
account to be updated.
IThe statement in the last paragraph should not include “and
EPOSS’.
COMMERCIAL IN CONFIDENCE Page 31 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Reh PASTRION2
‘ersion: 1 .I
Contents Description Date:25/06/99
Paragraph 1 should include ‘unreadable barcode’.
4.1.2.5.1 IThe bubble ‘Update token if smart’ is excluded in CSR.
4.1.2.5.3 Figure 4-6 will be changed to reflect the structure in Figure 4-4.
However, in both cases, the “Update token if smart” bubble is
excluded in CSR.
4.1.2.5.5 Using a smart card or smart key is excluded from CSR.
4.1.2.5.9 [Smart cards are excluded at CSR.
4.1.2.6 AP Smart Token - functionality is excluded from CSR.
4.1.2.7 IThe three bullets, “Endorsed MoPs (i.e. cheques)”, “Stock
management of tokens” and “Encoding smart card or smart key”,
should be deleted as this functionality will not be present at CSR.
4.1.2.7.1 IThe functionality described in the DN is excluded from CSR.
4.1.2.10.2 Migration for Existing AP Clients — for details of the infrastructure
necessary to enable AP Client Migration refer to the AP client
migration Strategy document for implementation details.
4.1.2.11 Will require to change since Schedule A06 no longer applies.
3.3.3 EPOSS SERVICE
SADD Explanatory Notes
Paragraph
4.1.3.1.1 Paragraph 1 should read ‘DVLA licences are restricted by DVLA’.
4.1.3.1.2 Session level discounts are not currently required.
4.1.3.1.2.2 ILast sentence should read ‘The stock unit balance can be
displayed on demand’.
4.1.3.1.2.5 IThe five bullets in Post Shop functionality: Discounting, Coupon
Management, Multibuys, Promotions and Marketing are excluded
from CSR. The CSR solution does provide the facility to use and
laccount for coupons as a method of payment. However, this must
lbe set up and driven through reference data received from POCL
via the POCL RDS interface.
4.1.3.1.5 Methods of Payment (MoP). EFTPOS is excluded from CSR.
COMMERCIAL IN CONFIDENCE Page 32 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Reh PASTRION2
‘ersion: 1 .I
Contents Description Date:25/06/99
(The possibility of MoPs linked to products has been removed.
4.1.3.1.12 The example, Benefit Encashment, selected to demonstrate this
point is to be replaced.
4.1.3.1.14 IThe possibility of MoPs linked to products has been removed.
4.1.3.1.16 References to BES and PAS to be removed.
ISmart’ technology will not be available in CSR.
4.1.3.1.18 I IOnly one customer session may be suspended and resumed, not
‘one OR MORE”.
4.1.3.1.19 [Reference to BES to be removed.
4.1.3.2.1.2 Will require to change since Schedule A06 no longer applies.
4.1.3.2.3.3 [Presentation group objects - exclusions are SmartCard Impulse
land OCR Impulse.
4.1.3.2.4 [Schedule A06 no longer applies.
4.1.3.2.5 (Automated products - AP smart key/cards are excluded from
ICSR.
4.1.3.3.1.1. IThe specific password lifetime should be removed. In fact it has
lbeen set to 6 months.
4.1.3.3.1.2 IThe Pathway approach to handling the possible loss of
transaction data is set out in separate letters (Hughes to Oudot,
dated 21% January 1998 and 30" January 1998).
4.1.3.3.2.3 here the user is not attached to any functional stock unit he
lutilises a ‘default stock unit’.
4.1.3.3.2.5 IReplace the existing words with “Detaching from a Stock Unit is
lachieved by attaching to a different Stock Unit”. These
requirements refer to a “Detach” facility for Stock Units. The
earlier joint working had implemented such a feature but this
lprocess has been made more efficient in the re-engineering by
implicitly detaching when attaching to a new stock unit.
4.1.3.3.2.10 IThe functionality of individual AP Client Cut Off will not be
implemented in CSR. At CSR all APS transactions are “cut-off” at
Ithe same time of day using the “End of Day” process invoked
lautomatically by the system at a time relative to the outlet closing
time. This design has been put in to guarantee the “clean break”
COMMERCIAL IN CONFIDENCE Page 33 of 1
© 1999 ICL PATHWAY LTD
ICL Pathway
ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
requirement expressed in the contract to ensure that the data seni
to POCL (TIP) and the data sent to clients (via POCL HAPS)
lexactly matches.
4.1.3.3.2.12
In the third paragraph it should state that ‘All but the last sharer of
la shared stock unit must detach from it or be logged out in order
that it can be balanced and rolled-over’
(The document, Day-in-the-Life-of Analysis of Clerk Cycles,
referred to in the last paragraph of this section does not exist. The!
IPPDs describe the implemented solution.
4.1.3.3.4 [The Cash Account - the CRU will not be implemented at CSR.
4.1.3.3.6 (Training Mode will be available in CSR. Training Mode may differ
in its detailed implementation from that described in the SADD [1],
lhowever, the general principles will be met. This comment applies,
jto paragraph 4.1.3.3.6.1 to 4.1.3.3.6.9 inclusive.
4.1.3.3.6.8 IThe example using BES and PAS is no longer appropriate.
4.1.3.3.7.1 [Broadcasts — a solution is still being sought to satisfy this
requirement. At present no solution has been identified and is
lexcluded from CSR.
4.1.3.3.7.2 [Documents — requirements and solutions for publishing electronic
\documents to outlets is to be clarified. This is excluded from CSR.
3.3.4 ORDER BOOK CONTROL SERVICE
SADD Explanatory Notes
Paragraph
4.1.4 (Change all references to ESNS to ESNCS
4.1.4.1 (There is no functionality to check the status of order book on re-
direction. This is documented in the OBCS Business Processing
Rules and will not be implemented in CSR.
4.1.4.2.1 Steady state provision. OBCS Host Functions. The ability to
compare a complete DSS control notice list against Pathway
\database and list discrepancies will not be available in CSR
4.1.4.2.3.1.1 IThe audible alarm indicates SUCCESS not failure of a bar-code
read.
COMMERCIAL IN CONFIDENCE Page 34 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release Ref.:PA/STR/012
Contents Description
4.1.4.1.3.2.1 IThe audible alarm indicates SUCCESS not failure of a bar-code
read.
4.1.4.1.3.3.1
[The audible alarm indicates SUCCESS not failure of a bar-code
read.
3.3.5 POCL INFRASTRUCTURE SERVICES
SADD Explanatory Notes
Paragraph
4.1.5.1 The bullet for Mobile Configuration and the associated sub-bulletsI
are excluded from CSR.
Remove reference to BES and DSS.
4.1.5.1.2 \Standard configuration details. The standard OPS counter
configuration will not include a smart key reader in CSR.
Remove reference to BES, benefit encashment and Pick Up
Notices.
4.1.5.1.3 Remove reference to DSS.
4.1.5.1.6 (The two approaches identified are the use of a flat screen and the
luse of a trolley
4.1.5.1.7 [The mobile configuration will not be available in CSR.
Remove reference to DSS.
4.1.5.2.1 Remove reference to PAS/CMS.
4.1.5.2.2.1 IRemove reference to DSS.
4.1.5.2.2.3 [Remove reference to DSS.
4.1.5.2.3.1 [Remove reference to DSS.
4.1.5.2.3.3 [The only POCL interfaces supported at CSR are:
ith TIP from outlets;
ith POCL Host (Farnborough Data Polling Centre);
ith POCL RDS.
Remove reference to DSS interfaces for PAS/CMS and ‘foreign
office’ .processing.
COMMERCIAL IN CONFIDENCE Page 35 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Reh PASTRION2
‘ersion:1.{
Contents Description Date:25/06/99
4.1.5.2.3.4.1 [Remove reference to PAS.
4.1.5.2.3.4.4 [Remove references to DSS, card or payment stop message.
4.1.5.2.3.5.5 [Remove reference to DSS.
4.1.5.3.2.1.5 ISee comment in Section 4.0 of this RCD relating to paragraph 8.6
lof SFS.
4.1.5.3.2.1.6 I‘and POCL Clients” should be deleted from the second
paragraph.
Remove reference to DSS.
4.1.5.3.2.2 [Remove reference to DSS.
4.1.5.3.3.2 IPathway MIS does not include Asset/Configuration Management.
Asset/ Configuration management functionality is provided by
[Sorbus under Dispatch 1 at Stevenage. Pathway MIS only
supports Audit of its own changeable data. Other hosts and the
laudit work station provide the general Audit Requirement referred
jto under 894.
Remove reference to Fraud risk management analysis and
reporting.
4.1.5.3.3.3.1 IISDN2 circuits” are not used in our solution — kilostream is used.
4.1.5.3.3.3.4 IThere are no Third Party links supported at CSR.
4.1.5.4.1 (The reference to the paragraph in which Reference Data is
defined should be 4.1.5.3.2.1.6.
Remove reference to BA transaction reconciliation reports.
4.1.5.4.2 Inventory Management - will not be available at CSR.
4.1.5.5 Links to POCL clients are excluded from CSR.
3.3.6 POCL CONTINGENCY SERVICES
SADD Explanatory Notes
Paragraph
4.1.6.1 OCRs and Smart cards and their reader/encoders are not
available at CSR.
COMMERCIAL IN CONFIDENCE Page 36 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Reh PASTRION2
‘ersion: 1 .I
Contents Description Date:25/06/99
Remove reference to BES, PUN, mandate and NINO details.
4.1.6.2.1 DSS — requirement to be removed.
4.1.6.2.4 ‘Smart cards/keys not available at CSR.
4.1.6.2.4.1.2 [This section relating to smart card/key is excluded at CSR.
4.1.6.3 (OCR reader is not available at CSR
4.1.6.3.1 DSS — requirement to be removed.
4.1.6.3.4 OCR reader is not available at CSR.
4.1.6.3.4.1 OCR reader is not available at CSR.
4.1.6.4 [This section relating to smart card/key reader/encoder is
excluded at CSR.
All reference to BES to be removed.
4.1.6.5.1 DSS — requirement to be removed.
4.1.6.6.1 Remove reference to BES.
4.1.6.8.1 Remove references to BES.
4.1.6.10.1 DSS — requirement to be removed.
4.1.6.10.2.1.3 [Foreign OBCS transactions in fallback will be authorised via the
OBCS Help Desk at the discretion of the clerk
[The reference to specific menus and screens in the second
paragraph is not correct. There are no such screens.
All menu statements should refer to “The Horizon OPS Menu
Hierarchy Release 2” document, SD/SPE/016 which has been
agreed with Horizon.
[The DN at the end of the section is not achievable. Pathway
lhave written to Horizon indicating the problem and a response
is awaited. The issue relates to the lack of an order book
inumber at the point in the time that the problem is discovered.
4.1.6.10.3.1 Screen titles not correct.
4.1.6.10.4 OCRs and Smart cards/key transactions are not available at
CSR.
COMMERCIAL IN CONFIDENCE Page 37 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Reh PASTRION2
‘ersion: 1 .I
Contents Description Date:25/06/99
4.1.6.10.4.1.2 [Smart cards are not available at CSR.
4.1.6.10.4.1.3 JOCR transactions are not available at CSR
4.1.6.11.1 DSS — requirement to be removed.
4.1.6.11.2 DSS — requirement to be removed.
4.1.6.11.5 [This paragraph refers to paragraph 4.1.3.3.1.2. Refer to the
comment associated with this reference earlier in this section.
Remove reference to BES.
4.1.6.12.1 Remove reference to BES.
4.1.6.12.2.1 I ITemporary Mobile Post Offices are excluded at CSR.
Printouts that identify transactions not yet delivered to TMS are
produced at the outlets.
4.1.6.13.1 Remove reference to BES.
4.1.6.13.1.1 [Remove references to BES transactions and service.
(OBCS transactions should be based on the Control Notice for
Inominated office transactions and the OBCS Help Desk for
foreign transactions.
4.2 IThe reference to ‘Reference’ in the first paragraph should read
(Reference Data’.
COMMERCIAL IN CONFIDENCE Page 38 of 1
© 1999 ICL PATHWAY LTD
ICL Pathway
ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
:PA/STR/012
3.4 APPENDIX B
SADD Explanatory Notes
Paragraph
B.1.1.1 Remove references to CMS/DSS/PAS.
B.1.1.3 Remove references to BES/CMS/PCDF.
B.1.1.4 [The last sentence of the last-but-one paragraph should be
deleted.
Remove references to DSS — Fig B-1. Remove references to
IBA/DSS infrastructure CMS/PAS/BES.
B.1.1.5 [The diagram indicates under client interfaces that the APS Host
Application provides “client forwarding” - this is not available at
CSR.
From Figure B-2, remove CAS Interface, CMS Host Application,
PAS Host Application, CMS Loaders and Harvesters, PAS
Loaders and Harvesters, CMS/PCDF, BES, DSS Application
Services and also CMS and PAS.
B.1.2 Remove reference to PAS/CMS/DSS Service Infrastructure.
B.1.2.1 IThe second bullet contains a reference to a data
communications service between a Pathway APS gateway and
la POCL client APS host. This will not be available at CSR.
Remove reference to DSS, CAPS, PAS/CMS, CAS.
B.1.2.3 Remove reference to BES.
B.2. DSS — Requirement to be removed.
B.3 Remove reference to BES transactions.
Figure B-5 needs to change to remove BES, BES EPOSS
[Transactions and to reflect the fact that APS and OBCS are not
dependent upon EPOSS - these applications independently
construct their EPOSS transactions.
B.3.1.2.2 Remove references to benefit encashments, BES, BES
[Transaction message, BES Encashment message, BPS Card
Event message, BES Foreign Enquiry time message, BPS
COMMERCIAL IN CONFIDENCE Page 39 of 1
© 1999 ICL PATHWAY LTD
ICL Pathway
FUJ00078801
FUJ00078801
ICL Pathway Core System Release Ref.:PA/STR/012
Version: 1.0
Contents Description Date:25/06/99
EPOSS Transaction line message and BES encashment
infringement records.
B.3.2.1.2
[The direct operation to POCL clients will not be available in
CSR.
B.3.2.2
IThe reporting of tariff lists and action codes; APS transaction
(data from non-Horizon outlets to be managed by Pathway APS
host will not be available in CSR.
B.3.2.3
‘Support for an interactive APS agent for interactive
authorisation will not be available in CSR. The transfer of APS
client data via the downloading mechanisms will not be
available in CSR
COMMERCIAL IN CONFIDENCE Page 40 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Reh PASTRION2
‘ersion:
Contents Description Date:25/06/99
4.0 SFS
SFS Version 3.0 contains details of the security qualities being applied to the
system. This section documents a number of exclusions from the ICL
Pathway Core System Release which will be included in later releases. All
non-excluded functionality described in the SFS is planned to be delivered.
The references below are to the paragraph numbers in the SFS.
SFS Comment
Paragraph
27 The POCL TIP link will be protected as detailed in Paragraph 8.3 of
the SFS
5.1.2.5 [Standard operating system error messages will be used
5.1.4 In certain circumstances, e.g. 4" line support, a card may be ‘assigned’
to an individual for a limited period. In such cases, a full audit trail of
such cards will be retained.
5.4 [The technical solution outlined in paragraph 5.4.1.4 of the SFS v3.0 will
not be implemented at CSR.
6.1.2.1 Least privilege is implemented to the extent that the security
lenvironment and functions allow. Any major residual threats will be
laddressed by means agreed with POCL Horizon..
7.3.1.1 System close down is not captured within the NT event log and thus
Isuch events will not be logged at CSR.
Failed log on attempts will not be captured by ORACLE within
lapplication level auditing.
8.3.2 Management of cryptographic keys at CSR have been documented and
forwarded to POCL Horizon for information.
8.6.3
8.7.2
8.5 IAP Signing will be introduced at the next major Release.
COMMERCIAL IN CONFIDENCE Page 41 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Reh PASTRION2
‘ersion:
Contents Description Date:25/06/99
18.6 The Key management Application cannot be implemented at CSR
without significant impact upon the current timescales. Key
management for CSR has been documented and forwarded to the
IPOCL HORIZON for information.
9.1 Unless otherwise stated in the relevant sections within the SFS,
message protection will be performed using DSA with a 768 bit modulus.
9.2.2 Public Key Certificates will be introduced at the next major Release.
COMMERCIAL IN CONFIDENCE Page 42 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release \ RetPASTRIOI2
‘ersit
Contents Description Date:25/06/99
ADDENDUM A: DSS AND BENEFIT PAYMENT CARD
EXCLUSIONS
The following section provides a list of SADD v4.0 [1] paragraphs that are no
longer required following the termination of the DSS contract and removal of
the Benefit Payment Card.
COMMERCIAL IN CONFIDENCE Page 43 of 1
© 1999 ICL PATHWAY LTD
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
2.3 BPS END-TO-END SERVICE DEFINITION
2.3.1 PFl RELATIONSHIPS
2.3.2 A WALK-THROUGH OF BPS
2.3.2.1 SUMMARY OF BPS IN THE DSS SERVICE ARCHITECTURE
2.3.2.2 SUMMARY OF BPS IN THE POCL SERVICE ARCHITECTURE
2.5 SECURITY INFRASTRUCTURE
2.5.2 FRAUD RISK MANAGEMENT SERVICE
2.5.2.1 MANAGEMENT INFORMATION SYSTEM
2.5.2.2 IRREGULAR ENCASHMENT PATTERNS
3. DSS SERVICE ARCHITECTURE
3.1 DSS STEADY STATE SERVICE
3.1.1 CARD MANAGEMENT SERVICE
3.1.1.1 INTRODUCTION
3.1.1.2 OVERVIEW DIAGRAM OF THE CARD MANAGEMENT SERVICE
3.1.1.3 CARDHOLDER PROCESSES
3.1.1.3.1 Introduce New Card Holder/Temporary Token Holder
3.1.1.3.1.1 ROUTINE INTRODUCTION
3.1.1.3.1.2 URGENT INTRODUCTION
[3.1.1.3.2 Maintain Cardholder/Temporary Token Holder Details
3.1.1.3.2.1 CARDHOLDER DETAILS
3.1.1.3.2.2 TEMPORARY TOKEN HOLDER DETAILS
3.1.1.3.3 Maintain Card Status
3.1.1.3.4 Record Card Holder ‘End of Interest’
3.1.1.4 THE CARD
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 44 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
3.1
-1.4.1 Circumstances When A Card Order Will Be Generated
3.1
-1.4.2 Catering For Special Needs Groups
3.1
-1.4.3 Card Production
3.1
.1.4.4 Card Personalisation And Delivery To Nominated Post Office
3.1
1.4.4.1 CARD LIVERIES / LOGOS.
3.1
-1.4.4.2 POCL VIEWPOINT
3.1
-1.5 THE PUN
3.1
.1.5.1 Delivery Of PUN To Cardholder's Nominated Address
3.1
1.5.1.1 DSS VIEWPOINT
3.1
-1.5.1.2 CUSTOMER'S VIEWPOINT
-1.6 COLLECT AND ACTIVATE CARD.
-1.6.1 Customer Unable To Collect Card
-1.6.2 Replacement Of Existing Card On Card Expiry
-1.6.3 Automatic Replacement of Damaged Card
-1.6.4 Replacement Of Damaged Card By Customer Report
-1.6.5 Replace Lost Or Stolen Card
1.7 REPORT NON-ARRIVAL OF BATCH OF CARDS AT POST OFFICE
.1.7.1 Inhibit Card On Failure To Collect
-1.8 CARD MANAGEMENT SERVICE HELP DESK
-1.8.1 Introduction
-1.8.2 Overview Diagram Of The CMS Help Desk
.1.8.3 DSS Customer's Viewpoint
Ba
-1.8.3.1 CALLER VERIFICATION
3.1
-1.8.3.2 REPORT LOST / STOLEN OR FOUND CARD / TEMPORARY TOKEN
[3.1
-1.8.3.3 REPORT DAMAGED CARD / TEMPORARY TOKEN
3.1
-1.8.3.4 REPORT NON RECEIPT OF PUN
3.1
-1.8.3.5 REPORT CARD NOT AVAILABLE AT NOMINATED POST OFFICE
3.1
-1.8.3.6 REPORT CARD / PUN FOUND PREVIOUSLY REPORTED LOST
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 45 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOIZ
‘ersion:1.
Contents Description Date:25/06/99
3.1.1.8.3.7 ENQUIRE UPON CARD / PUN STATUS/EVENTS
3.1.1.8.3.8 EXCEPTIONS TO THE ABOVE PROCEDURES
3.1.1.8.4 DSS Staff Viewpoint
3.1.1.8.4.1 CALLER VERIFICATION
3.1.1.8.4.2 SUSPEND A CARD
3.1.1.8.4.3 UNSUSPEND A CARD
3.1.1.8.4.4 TERMINATE A CARD.
3.1.1.8.4.5 ENQUIRE UPON CARD / PUN STATUS (FALLBACK)
3.1.1.8.4.6 CALLS ON BEHALF OF DSS CUSTOMERS
3.1.1.8.4.7 EMERGENCY ORDER BATCH OF TEMPORARY TOKENS
3.1.1.8.4.8 TERMINATE TEMPORARY TOKEN(S)
3.1.1.8.4.9 EXCEPTIONS
3.1.1.8.5 POCL Counter Clerk’s Viewpoint
3.1.1.8.5.1 CALLER VERIFICATION
3.1.1.8.5.2 NON ARRIVAL OF BATCH OF CARDS
3.1.1.8.5.3 EXCEPTIONS
3.1.1.8.6 Miscellaneous Calls
3.1.1.8.7 Audit And Controls
3.1.1.9 TEMPORARY TOKEN PRODUCTION AND ISSUE
3.1.1.9.1 Introduction
3.1.1.9.2 Order A Batch Of Temporary Tokens
3.1.1.9.3 Maintain Reference Data
3.1.1.9.4 Produce And Despatch Temporary Tokens
3.1.1.9.4.1 DSS VIEWPOINT
3.1.1.9.5 Token Assignment
3.1.1.9.5.1 DSS VIEWPOINT
3.1.1.9.5.2 CUSTOMER VIEWPOINT
3.1.1.9.6 Payment Processing
COMMERCIAL IN CONFIDENCE Page 46 of 1
© 1999 ICL PATHWAY LTD
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
3.1.1.9.7 Issue Temporary Token Payment
3.1.1.9.8 Invalidate Token On Expiry
[3.1.1.9.9 Cancel A Token / Batch Of Tokens
3.1.1.9.9.1 DSS VIEWPOINT
3.1.1.9.10 Temporary Tokens during CAPS failures
3.1.1.9.10.1 GENERAL CAPS UNAVAILABILITY
3.1.1.9.10.2 CAPS UNAVAILABLE AT INDIVIDUAL DSS OFFICES
3.1.2 PAYMENT AUTHORISATION SERVICE
3.1.2.1 INTRODUCTION
3.1.2.2 OVERVIEW OF THE PAYMENT AUTHORISATION SERVICE
3.1.2.3 CUSTOMER PROCESSES.
3.1.2.3.1 New Customer
3.1.2.3.2 Amendment To Customer Details
3.1.2.3.3 Customer No Longer Of Interest To PAS And CMS
3.1.2.4 AMENDMENT TO CARD/TEMPORARY TOKEN HOLDER DETAILS
3.1.2.4.1 Card Details
3.1.2.4.2 Temporary Token Details
3.1.2.5 ISSUE NON-URGENT AUTHORISED PAYMENT
3.1.2.5.1 Pending Payment Stops
3.1.2.5.2 Payable Authorised Payments
3.1.2.5.3 Next Day Payments
3.1.2.5.4 Urgent Payments
3.1.2.5.4.1 URGENT PAYMENT-ENABLING, EXISTING CUSTOMER WITH
[TEMPORARY TOKEN
3.1.2.5.4.2 URGENT PAYMENT ENABLING EXISTING CUSTOMER WITH TEMPORARY
[TOKEN
3.1.2.5.4.3 URGENT PAYMENT - ENABLING, CREATION OF A PAYMENT
3.1.2.5.5 Contingency Payment
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 47 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
3.1.2.6 ENCASHED PAYMENT
3.1.2.6.1 Encashments Infringements
3.1.2.6.2 Encashed Payment Reporting
3.1.2.7 EXPIRED PAYMENT
3.1.2.8 STOPPED PAYMENT
3.1.2.9 ENQUIRY ON PAYMENT DETAILS
3.1.2.10 CUSTOMER NOTIFICATION OF CHANGE OF DETAILS
3.1.2.10.1 Notification Of Change Of Nominated Post Office
3.1.2.10.2 Infringements
3.1.2.10.3 Valid Changes
3.1.2.10.4 Notification Of Change Of Address
3.1.2.11 PAYMENT AUTHORISATION SERVICE (PAS) HELP DESK
3.1.2.11.1 Introduction
3.1.2.11.2 DSS Customer’s Viewpoint
3.1.2.11.3 DSS Staff Viewpoint
3.1.2.11.3.1 CALLER VERIFICATION
3.1.2.11.3.2 CAPS / CAPS ACCESS FACILITY NOT AVAILABLE
3.1.2.11.3.3 PAYMENT STOP (FALLBACK)
3.1.2.11.3.4 ENQUIRE UPON PAYMENT STATUS (FALLBACK)
3.1.2.11.3.5 CALLS ON BEHALF OF DSS CUSTOMERS.
3.1.2.11.3.6 EXCEPTIONS
3.1.2.11.4 POCL Counter Clerk’s Viewpoint
3.1.2.11.4.1 CALLER VERIFICATION
3.1.2.11.4.2 ENCASH PAYMENT VIA THE HELP DESK
3.1.2.11.4.3 ENCASH FOREIGN PAYMENT VIA THE HELP DESK
3.1.2.11.4.4 CHANGE NOMINATED POST OFFICE VIA THE HELP DESK
3.1.2.11.4.5 EXCEPTIONS
3.1.2.11.5 Miscellaneous Calls
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 48 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
3.1.8 COMMON CMS & PAS SERVICE ELEMENTS
3.1.3.1 OPERATIONAL STATUS
3.1.3.2 TECHNICAL SUPPORT
3.1.3.3 VALIDATION OF CAPS DETAIL RECORDS WITHIN CMS / PAS
3.1.3.4 AUDIT AND CONTROL
3.1.3.5 MAINTAIN POST OFFICE REFERENCES
3.1.3.6 MAINTAIN BENEFIT PAYMENT REFERENCES
3.1.3.7 DATA HOUSEKEEPING
3.1.3.7.1 Beneficiaries
3.1.3.7.2 Cardholders / Cards
3.1.3.7.2.3 Payments / Encashments
3.1.3.8 DSS MANAGEMENT INFORMATION
3.1.3.8.1 Contract Management
3.1.3.8.1.1 REQUIREMENT 1: CARDS ISSUED
3.1.3.8.1.2 REQUIREMENT 2: TYPES OF CALLS TO THE HELP DESKS
3.1.3.8.1.3 REQUIREMENT 3: ANALYSIS OF TYPES OF CALLS TO THE HELP DESKS
3.1.3.8.1.4 REQUIREMENT 4: CALLS LOST OR ABANDONED
3.1.3.8.1.5 REQUIREMENT 5: LENGTH OF CALLS
I3.1.3.8.1.6 REQUIREMENT 6: QUALITY OF SERVICE OFFERED TO CALLERS
3.1.3.8.1.7 REQUIREMENT 7: ENCASHMENTS AUTHORISED
3.1.3.8.1.8 REQUIREMENT 8: FOREIGN ENCASHMENTS.
3.1.3.8.1.9 REQUIREMENT 9: PAYMENTS MADE UNDER FALLBACK PROCEDURES
3.1.3.8.1.10 REQUIREMENT 10: CONTINGENCY PAYMENTS
I3.1.3.8.1.11 REQUIREMENT 11: TEMPORARY TOKENS ISSUED
3.1.3.8.1.12 REQUIREMENT 12: CARDS ACTIVATED
3.1.3.8.1.13 REQUIREMENT 13: CERTAIN ACTIVE CARD STATUS CHANGES
3.1.3.8.2 Audit
3.1.3.8.2.1 REQUIREMENT 14: RANDOM SELECTION OF ENCASHMENT RECORDS
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 49 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
3.1.3.8.2.2 REQUIREMENT 15: BESPOKE ANALYSES
3.1.3.8.3 Accounting
3.1.3.8.3.1 REQUIREMENT 16: DAILY AND WEEKLY SUMMARY
3.1.3.8.3.2 REQUIREMENT 17: MISMATCHES
3.1.3.8.3.3 REQUIREMENT 18: UNCASHED TRANSACTIONS
3.1.3.8.4 Security
3.1.3.8.4.1 REQUIREMENT 19: INTERNAL FRAUD INCIDENTS.
3.1.3.8.4.2 IRREGULAR ENCASHMENT PATTERN REPORTS
3.1.3.8.5 Other Management Information
3.1.3.9 CAPS ACCESS SERVICE ( CAS )
I3.1.3.9.1 Introduction
3.1.3.9.2 Data Delivery
3.1.3.9.2.1 DATA TRANSFER OPERATIONS
3.1.3.9.2.1.1 Batch Interface In/Out tray operation
3.1.3.9.2.1.2 On-Line Interface OSI/TP Operation
3.1.3.9.2.2 MIS REPORTING
3.1.3.9.3 Data Exchange
3.1.3.9.4 Data Validation
3.1.3.9.5 System Interface
3.1.3.9.6 CMS & PAS Interfaces
3.1.3.10 PAS RECONCILIATION REQUIREMENTS.
3.1.3.10.1 PAS-related Reconciliation
3.1.3.10.1.1 TIMING, LEGISLATIVE AND REPORTING CONSTRAINTS
3.1.3.10.1.2 ENCASHMENT AND EXPIRY REPORTING
3.1.3.10.1.3 EXCEPTIONAL LATE REPORTING
I3.1.3.10.1.4 PAYMENT STOPS
3.1.3.10.1.5 SCOPE OF RECONCILIATION
3.1.3.10.1.6 TREATMENT OF PATHWAY ADJUSTMENTS
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 50 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
3.1.3.10.2 The Common Basis Of Settlement
3.1.3.10.2.1 REQUIRED OUTPUTS.
3.1.3.10.2.2 MATCHED AUTHORISATIONS.
3.1.3.10.2.3 RECONCILIATION EXCEPTIONS
I3.1.3.10.2.4 UNENCASHED BALANCES
3.1.3.11 CMS RECONCILIATION
3.1.3.11.1 CMS-Related Reconciliation
3.1.3.11.1.1 CARD-RELATED RECONCILIATIONS
3.1.3.11.1.2 TEMPORARY TOKEN-RELATED RECONCILIATIONS
3.1.3.12 DSS ENQUIRY HELP DESK FACILITY
8.1.4 RELEVANT OPTIONAL DSS SERVICES
3.2 DSS SERVICE INFRASTRUCTURE
3.2.1 HARDWARE
3.2.2 SOFTWARE
3.2.3 OTHER COMPUTER & TELECOMMS EQUIPMENT
3.2.3.1 ACCS TO PATHWAY CAMPUSES
3.2.3.2 BETWEEN PATHWAY CAMPUSES
3.2.3.3 PATHWAY CAMPUSES TO DE LA RUE
3.2.3.4 PATHWAY CAMPUSES TO ROYAL MAIL
3.3 DSS SERVICE ENVIRONMENT
3.3.1 DSS COMPUTERS
[3.3.2 BUSINESS SYSTEMS AND DATA
3.3.2.1 BUSINESS INTERFACES, PROCESSES AND PRODUCTS
3.3.2.1.1 Processes Within CAPS Computer
3.3.2.1.2 File Transfer Product3.3.2.1.3 Processes Within PAS / CMS
3.3.2.1.3 Processes Within PAS/CMS
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 51 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
3.3.2.2 BUSINESS DATA
3.3.2.2.1 Files Received From CAPS - CAPS Outbound Process
3.3.2.2.1.1 BATCH FUNCTIONS
3.3.2.2.1.2 ON-LINE FUNCTIONS.
3.3.2.2.2 File Transfer Over WAN
3.3.2.2.2.1 BATCH FUNCTIONS
3.3.2.2.2.2 ON-LINE FUNCTIONS
3.3.2.2.3 Files Received From CAPS - PAS / CMS Inbound Process
3.3.2.2.3.1 BATCH FUNCTIONS
3.3.2.2.3.2 ON-LINE FUNCTIONS
I3.3.2.2.4 Files Sent To CAPS - PAS / CMS Outbound Process
\3.3.2.2.5 Files Sent To CAPS - CAPS Inbound Process
3.3.2.3 HOUSEKEEPING
3.3.2.3.1 Log File
3.3.2.3.2 VME Disk Files
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 52 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
4.1.
41 BENEFIT ENCASHMENT SERVICE/PATHWAY CARD DISTRIBUTION FACILITY
4.1.
1.1 INTRODUCTION
4.1.
1.2 RECEIPT OF BATCH OF CARDS IN POST OFFICE (PCDF)
4.1.
1.2.1 Transaction Selection
4.1.
1.2.2 Steady State Service Provision
4.1.
1.3 RECONCILIATION OF CARDS AGAINST BATCH DETAILS (PCDF)
4.1.
1.3.1 Transaction Selection
4.1.
1.3.2 Steady State Service Provision
4.1.
1.4 COLLECTION OF NEW CARD BY CUSTOMER (PCDF)
4.1.
1.4.1 Transaction Selection
4.1.
1.4.1.1 COLLECTION WITH PUN
4.1.
1.4.1.2 ROUTINE CARD COLLECTION (NO PUN)
4.1.
1.4.2 Steady State Service Provision
4.1.
1.4.3 Customer’s Viewpoint
4.1.
1.4.4 PUN Holder Unable to Collect Card
4.1.
1.5 EXTENDED VERIFICATION PROCEDURE (EVP) (BES)
4.1.
1.5.1 Transaction Selection
4.1.
1.5.2 Steady State Service Provision
4.1.
1.5.3 Customer’s Viewpoint
a4
-1.6 IMPOUNDMENT OF CARD / TEMPORARY TOKEN / PUN (PCDF)
-1.6.1 Transaction Selection
-1.6.2 Steady State Service Provision
-1.6.3 Customer's Viewpoint
4.1
1.7 FORWARDING/DISPOSAL OF IMPOUNDED PUNS, CARDS AND TEMPORARY
ITOKENS (PCDF)
4.1.
1.7.1 Transaction Selection
4.1.
1.7.2 Steady State Service Provision
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 53 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
4.1.1.8 BENEFIT ENCASHMENT - STANDARD ENCASHMENT (BES)
4.1.1.8.1 Transaction Selection
4.1.1.8.2 Steady State Service Provision
4.1.1.8.3 Customer’s Viewpoint
4.1.1.8.4 Encashments Greater Than DSS Limit
4.1.1.9 BENEFIT ENCASHMENT - FOREIGN ENCASHMENT (BES)
4.1.1.9.1 Transaction Selection
4.1.1.9.2 Steady State Service Provision
4.1.1.9.3 Customer’s Viewpoint
4.1.1.10 BENEFIT ENCASHMENT - CASUAL AGENT (BES)
4.1.1.10.1 Transaction Selection
4.1.1.10.2 Transaction Selection
4.1.1.10.3 Customer's Viewpoint
4.1.1.11 BENEFIT ENCASHMENT - BY PLANNED PROXY (BES)
4.1.1.11.1 Transaction Selection
4.1.1.11.2 Steady State Service Provision
4.1.1.11.3 Customer's Viewpoint
4.1.1.12 FORWARDING OF BENEFIT ENCASHMENT RECEIPTS (BES)
4.1.1.12.1 Transaction Selection
4.1.1.12.2 Steady State Service Provision
4.1.1.14 CHANGE OF NOMINATED POST OFFICE (BES)
4.1.1.14.1 Transaction Selection
4.1.1.14.2 Steady State Service Provision
4.1.1.14.3 Customer's Viewpoint
4.1.6.2.1 BES
4.1.6.2.1.1 CONTINGENCY ARRANGEMENTS
4.1.6.2.1.1.1 Receipt Of Batches Of Cards Into The Post Office
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 54 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
4.1.6.2.1.1.2 Collection And Activation Of Card By Customer
4.1.6.2.1.1.3 Benefit Encashment Using Card
4.1.6.2.1.1.4 Change Of Nominated Post Office
4.1.6.3.1 BES
4.1.6.3.1.1 CONTINGENCY ARRANGEMENTS.
4.1.6.3.1.1.1 Batch Details Of Cards Received Into The Post Office
4.1.6.3.1.1.2 PUN Details
4.1.6.5.1 BES
4.1.6.5.1.1 CONTINGENCY ARRANGEMENTS.
4.1.6.10.1 BES
4.1.6.10.1.1 CONTINGENCY ARRANGEMENTS.
4.1.6.10.1.1.1 Receipt Of Batch Of Cards In Post Office
4.1.6.10.1.1.2 Collection And Activation Of Card
4.1.6.10.1.1.3 Benefit Encashment Using Card
4.1.6.10.1.1.4 Duplicate Receipt Request
4.1.6.10.1.1.5 Change Of Nominated Post Office
4.1.6.11.1 BES (gateway PC)
4.1.6.11.1.1 CONTINGENCY ARRANGEMENTS.
4.1.6.11.2 BES (non-gateway PC)
4.1.6.11.2.1 CONTINGENCY ARRANGEMENTS.
B.2 INTERFACES WITHIN THE END-TO-END BENEFITS PAYMENTS SERVICE
B.2.1 CAPS TO PAS/CMS
B.2.2 CMS-PAS (INCLUDING PCDF-BES)
B.2.3 CMS TO/FROM PCDF (VIA TMS)
B.2.5 BES AGENT TO BES (VIA TMS)
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 55 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
ADDENDUM B: CCNS COMPREHENDED
The following section provides a list of Change Control Notes comprehended
in either CSR or CSR+ and identifies the status of each.
For complete visibility, the table lists all CCNs raised up to and including
CCN485, indicating their status as at 18" June 1999.
The Reason column, where used, indicates why a particular CCN is not
included in the release contents for either CSR or CSR+. The Reasons used
are as follows:
REASON MEANING SHADING
KEY
ithdrawn ICCN withdrawn by Pathway
ICR withdrawn ICR withdrawn by Horizon
Rejected ICCN rejected by Horizon
Superseded Replaced by a subsequent CCN
Earlier Release
Specific to an earlier release e.g. IGL or
Ric, and not carried forward into CSR
IDSS/BPC INo longer applicable as relates to DSS or
IBenefit Payment Card or as a result of the
Letter and Heads of Agreement
ICSR+ Planned to be implemented at CSR+ hen NOT
japproved, Status
Box is shaded
Administration
Affects administrative issues, not
functionality
hen NOT
japproved, Status
Box is shaded
Documentation [Affects documentation, not functionality hen NOT
approved, Status
Box is shaded
(Commercial Affects terms of business, not functionality hen NOT
japproved, Status
Box is shaded
Implementation
Affects implementation issues e.g. roll out,
Inot functionality
hen NOT
japproved, Status
Box is shaded
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 56 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release Ref.:PA/STR/012
Version:1.0
Contents Description Date:25/06/99
[Schedule Affects the timetable, not functionality hen NOT
japproved, Status
Box is shaded
Note the Reason may not be in logical accord with the Status column.
Where a CCN is shown as part of the release contents, the CCN is being
implemented as it was presented for the release. It is agreed that approval
of this document does not indicate approval of any otherwise unapproved
CCNs. CCNs numbered beyond 485 that are applicable to a release may or
may not be included in that release by specific agreement.
Status Reason Release
CCN __I Description
e OF Li
0002 Live Trial Volumes Approved Schedule N/A
0003 CAPS IGL Configuration Approved DSS/BPC
Not to be
applied
(0004b Automatic Replenishment Of Approved IDSS/BPC
[Temporary Tokens INot to be applied
0005d Proxy Collection Of Cards/ Approved DSS/BPC
Housebound PUN Holder Not to be
applied
Encashment ID Format (IGL I Approved DSS/BPC
Only) Not to be
applied
(0008b Roll-Out And Implementation [Approved Schedule IN/A
Agreement (Note CCNO008a
Listed In Ccns 0067, 00069,
(CCNO008b In CCNO068)
0009 Addition Of Management Approved Administration N/A
Team CVs
(0010b IR895 - Irregular Encashment + IApproved IDSS/BPC
Patterns INot to be applied
All reports for
IR895 currently
lapply solely to
IDSS/BPC
0011 EPOSS Transaction Input Approved Administration N/A
(0012 Bilingual BES Receipt ATP. (Approved IDSS/BPC.
INot to be applied
(0013a (OBCS Stop Record Archiving [Approved CSR
0014 Change From BT To Energis_I Approved Commercial N/A
(0015a (Clarification Of PAS/BES Approved IDSS/BPC
Service Boundary INot to be applied
0016 Introduce POCL MIS Reports I Approved Administration N/A
As A Controlled Document
COMMERCIAL IN CONFIDENCE Page 57 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release vi eo
fersion:1.
Contents Description Date:25/06/99
0017 Use PAS Help Desk To Approved DSS/BPC
Compensate For Removal Of I Not to be
Monitor Usage Flag/Card applied
Alert File From CAPS V6
Remove PUN Receipt Approved DSS/BPC
Not to be
applied
lEPOSS/Audit Retention Of Approved
Records
0022a Internal Service Levels TMS _I Approved CSR
(0023b internal Service Levels CMS —_ Approved IDSS/BPC
INot to be applied
(0024b Internal Service Levels PAS — Approved IDSS/BPC
[Not to be applied
0025b Order Book Call And Approved CSR
Redirection Transactions
(0026b ~—- Card Wording And R962 (Approved, IDSS/BPC
jsuperseded by
ICCN 78
INot to be applied
0027b Changes To Control Card Approved DSS/BPC
Population Awaiting CAPS
support
Not to be
applied
0028 POCL A Pathway Approved Commercial N/A
Subcontractor
0029a I Royal Mail A Pathway Approved DSS/BPC
Subcontractor Not to be
applied
0030a Amendments To Schedules Approved Administration
lignment Of R914 Approved (Administration
escriptions In Schedules BO1
nd BO2 With G10
OBCS Handling Counterfeit Approved
Book
COMMERCIAL IN CONFIDENCE Page 58 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release vi eo
fersion: 1.
Contents Description Date:25/06/99
0037a Extended Verification Approved DSS/BPC
Change To SADD V2.0 Not to be
applied
Solutions Update (Schedules I Approved Administration
B5(A), A15(D&P) In
Preparation
(0043, R708 (Approved IDSS/BPC
INot to be applied
[0044a R898. IApproved (Administration IN/A
[0045a R890, Approved (Administration IN/A
(0046 R914 (Approved (Administration IN/A.
0047a_I OBCS Availabili x nee Administration N/A
0049a I Remove Replacement Approved DSS/BPC”
Receipts Not to be
=
0054 Further Extension Of Drop- Approved Administration
Down Period
[0059 Acceptance Procedures (Approved Commercial
[0060 Reference Data System Approved ICSR
(0061 Amend POCL Agreement Prior IApproved (Administration IN/A
{To Completion Of ExtrapolationI (Commercial
And Transposition
j0062 (Complete POCL Agreement Approved Administration IN/A
lExtrapolation And (Commercial
[Transposition
0063 Complete Authorities’ Approved Administration N/A
Agreement Extrapolation And Commercial
Transposition
(0064 (Complete DSS Agreement \Approved IDSS/BPC.
Extrapolation And INot to be applied
[Transposition
[0065 [Delete R933 Approved Schedule IN/A
[0066 Extend POCL Signing AuthorityIApproved (Administration IN/A
[0067 (Omnibus CCN - POCLI Approved (Administration IN/A.
Agreement
COMMERCIAL IN CONFIDENCE Page 59 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release vi eo
fersion:1.
Contents Description Date:25/06/99
0068 Omnibus CCN - Authorities’ Approved Administration N/A
Agreement
(0069 (Omnibus CCN - DSS IApproved IDSS/BPC.
Agreement INot to be applied
(0070 Amend Authorities’ Agreement Approved (Administration IN/A
Prior To Completion Of
lExtrapolation And
[Transposition
0071 Schedule A06 - Charging Approved Commercial N/A
Mechanisms
(0072 Amend DSS Agreement Prior [Approved IDSS/BPC.
[To Completion Of ExtrapolationINot to be applied
And Transposition
0073 OBCS Acceptance And Approved Commercial N/A
Effect On Guarantees
(0074 Application Of EVP And Limits [Approved IDSS/BPC
[Thereon INot to be applied
0075 Omnibus CCN - Grp 4 POCL I Approved Administration N/A
Agreement
(0076 (Omnibus CCN — DSS Approved IDSS/BPC
Agreement INot to be applied
0077 Omnibus CCN - Authorities’ Approved Administration N/A
Agreement
(0078 (Card Wording And R962 Approved IDSS/BPC
INot to be applied
0079 Further Extension Of Drop- Approved Administration N/A
Down Period
0081d I Electronic Cash Account I Approved Post CSR+
0082b I Rationalising Service Targets I Approved DSS/BPC
For Acknowledging CAPS Not to be
Files applied
0087 Removal Of Existing Approved
Equipment
Adjusted Next Payment Due I Approved DSS/BPC
Date Not to be
applied
COMMERCIAL IN CONFIDENCE Page 60 of 1
© 1999 ICL PATHWAY LTD
ICL Pathway
Contents Description
ICL Pathway Core System Release
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
0093b I Removal Of Type 2 Stop Approved
Confirmations Not to be
applied
0096a I Correction Of
Communication Contact
Point In PDA
a co
—
Of Services
Agreement
(Omnibus CCN (Approvals) Dss
Call Reason Value For Data I Approved DSS/BPC
Item ‘Action On Time’ Not to be
applied
0101 Contractual Obligation Approved DSS/BPC
Processing - Minor Not to be
Amendment applied
10102 (Omnibus CCN (Approvals) Approved (Commercial IN/A
Authorities Agreement
0103 Omnibus CCN (Approvals) Approved Commercial N/A
Pocl Agreement
(0104 (CAPS/Pathway Interface - On- [Approved IDSS/BPC.
Line Functionality INot to be applied
Replan And Phased Delivery I Approved Schedule N/A
IDSS/BPC
(Omnibus CCN (Withdrawals)
Authorities Agreement
Approved
(Commercial
New Caps Baseline
Documentation
applied
0110 Omnibus CCN (Withdrawals) I Approved Commercial N/A
POCL Agreement
0111 Omnibus CCN (Withdrawals) I Approved DSS/BPC
DSS Agreement Not to be
DSS/BPC
© 1999 ICL PATHWAY LTD
COMMERCIAL IN CONFIDENCE
Page 61 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release vi eo
fersion:1.
Contents Description Date:25/06/99
(0115b (CAPS Amendment To \Approved IDSS/BPC
(CORHLD [Not to be applied
0116 Correction To Outlet Approved Documentation N/A
Downtime Remedy
Calculation
(0117 Reusable Temporary Tokens [Approved IDSS/BPC.
And Related Modifications INot to be applied
0118b CAPS Change Migration Approved DSS/BPC
COR Notification Identifiers I Not to be
See also CCN133; applied
Remove Numbers Of Post (Approved
(Offices Within BA Districts INot to be applied
From Number Allocation To BA
Districts.
0121a Schedule AO03 Audit Approved Commercial N/A
0122a Common CAPS Batch And Approved DSS/BPC
On Line Interfaces (No functional
consequence)
Not to be
applied
Remote Stock Units Approved Administration
(paid study)
(0126a _ Duplicate Stop Requests File IApproved IDSS/BPC.
[Type INot to be applied
(0127 (COR HLD Lost File (Approved IDSS/BPC.
Notifications And VME INot to be applied
Filename
0128 Order Of Processing COR Approved DSS/BPC
Notifications Received Not to be
applied
Change Additional Value For I Approved DSS/BPC
Invalid COR Notification Not to be
applied
Increase CAPS Services 5 : DSS/BPC
From One To Six
‘See also CCN118b)
Single Format Cash Account_I Approved
COMMERCIAL IN CONFIDENCE Page 62 of 1
© 1999 ICL PATHWAY LTD
ICL Pathway
FUJ00078801
FUJ00078801
ICL Pathway Core System Release Ref.:PA/STR/012
co Version:1.0
Contents Description Date:25/06/99
Fraud Risk Management
Reports
Schedule DD01 - PAS Service
Definition Amendment
Approved
DSS/BPC
IDSS/BPC
(Change BA Districts Details
proved
lot to be applied
_ IDSS/BPC
Post Office Closure Date File
(On PO Codes Table
proved
lot to be applied
IDSS/BPC
Identify Horizon-Originated
APS Transactions In APACHI
rafting Changes To
\cceptance Procedures
chedules
Approved
Revised Rollout Plan
Removal Of Duplicate Receipts,
‘See also CCN49a)
(Approved
INot to be applied
IDSS/BPC
(0150
Reference Data To Pathway
Application Interface
ISpecification Tidy Up
(Approved
CSR
(0151
Reference Data To Pathway
Application Interface
ISpecification Tidy Up
(Approved
CSR
0152
Black Ink Ribbon
Consumable For Counter
Printer
Revised Rollout And
Implementation Agreement
Approved
Approved
Implementation N/A
Implementation
COMMERCIAL IN CONFIDENCE Page 63 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v eo
ersion:1.
Contents Description Date:25/06/99
0156 Introduce New Definitions Approved DSS/BPC
For Authority To Pay And Not to be
Payment Receipt applied
10157 Documentary Change To (Approved IDSS/BPC
IPAS/CMS Error Codes INot to be applied
(0158 (Clarify Reference To PIVOT In [Approved (Commercial IN/A
Schedule PFO8
Post Office Within Live Trial I Approved
Evaluation
Implementation
Pathway Change Of Approved Commercial
Company Name.
(CAPS Contingency, SeptemberIApproved IDSS/BPC.
11997 Through To CAPS INot to be applied
Release 3.
0163 CAPS Contingency For Approved DSS/BPC
Release 3 Onwards Not to be
Omnibus CCN Authorities Approved Commercial
Agreement For 116, 131a,
135, 138, 145, 152, 158, 159
(0168 (Omnibus CCN DSS AgreementiApproved IDSS/BPC
For 116, 131a, 135, 138, 145, INot to be applied
152, 158, 159
0169 Omnibus CCN POCL Approved Commercial N/A
Agreement For 116, 131a,
135, 138, 145, 152, 158, 159
(0170b New Values For PO Code File Approved IDSS/BPC.
[Equipment INot to be applied
(0171a Add Caps File Type 23 (Approved IDSS/BPC
INot to be applied
(0172 (Change To The Details (Approved IDSS/BPC
Relating To BA Districts INot to be applied
0173 Omnibus CCN For 91b, 93b, I Approved Commercial N/A
100b, 101, 114b, 115b, 118b, I (Note 91b and
120, 122a, 125, 126a, 127, 93b are now
128, 133, 136, 139, 140, 141, I recorded as
146, 150 151, 154, 157, 162, I approved)
163
(0174e (Customer Education Branding, IAApproved IDSS/BPC
Need For All Communications INot to be applied
[To Reflect Card And Special
Needs
0175b I PCHL Phone Number Approved DSS/BPC.
Changes Not to be
applied
COMMERCIAL IN CONFIDENCE Page 64 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v eo
ersion: 1.
Contents Description Date:25/06/99
Removal Of Record Approved
Separators From HAPS
Interface
CAPS Change Amendment To [Approved
Service Identifier Definition On INot to be applied
Files From Pathway
IDSS/BPC
(0180a__ [BPS Reference Data - Routing IApproved IDSS/BPC.
[Data For Pathway INot to be applied
0181 Amend CAPS To PAS/CMS__I Approved DSS/BPC
Codes Files Definition Not to be
Document applied
(Cosmetic Damage Approved implementation
Minor Changes To Reference I Approved
Data To Pathway Application
Interface Specification
Revised Id List ‘Approved DSS/BPC
Not to be
applied
(0189 Revised Rollout Plan (Approved Implementation IN/A.
0190 Revised Rollout Plan - Approved Implementation NIA
Stream A2
(0191 Alteration Of FRM Reporting Approved IDSS/BPC
Requirements. Not to be applied
(0192 (Correcting An Incorrect Cross IApproved (Commercial IN/A
Reference In Schedule BOS Of
[The POCL Agreement
0193 Withdrawal Of Requirement I Approved Customer Education I N/A
917 (Customer Education
Concerning POCL
Automation)
(0194. [Payment Card Textual Approved IDSS/BPC
(Changes (PDA CR P47) lot to be applied
(0195 Reversion Of Encashment Id Approved IDSS/BPC
[To IGL Format [Not to be applied
(0196 TELNET Access Requirements IApproved IDSS/BPC
[To 1¢ Routers INot be applied
0197 Use Of TACACS+ For Approved DSS/BPC
Release 1c Not to be
applied
COMMERCIAL IN CONFIDENCE Page 65 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release vi eo
fersion: 1.
Contents Description Date:25/06/99
0198b Contract Controlled & Approved Administration N/A
Referenced Document List
0199 OBCS Transaction Value Approved CSR
Capture
0201 Minor Changes To Reference I Approved CSR
Data To Pathway Application
Interface Specification
0202 Electronic Weighing Scales Documentation N/A
0203 PAS/CMS DIDVR -Change Approved DSS/BPC
Validation Of “U” And “T” Not to be
Type Broadcasts applied
0204a_ I Generate Card Stop Approved DSS/BPC
Following CMS End Of Not to be
Interest applied
0205a Visual Check Of Card Details I Approved DSS/BPC
During Card Collection Not to be
applied
Pathway Release 2 Caps \Approved IDSS/BPC
interface Document List INot to be applied
0208d I Pathway Release 1c CAPS Approved DSS/BPC
Interface Document List Not to be
applied
0209a I Wording Changes To PUN, Approved DSS/BPC
Authority To Pay, Nil Not to be
Receipts, Impound Receipts _I applied
0210 Introduction Of Empty But Approved Commercial N/A
Referenced Schedules ...
(0211 ATP Amendment (Approved IDSS/BPC
[Not to be applied
(0212 (Customer First Forename (Approved IDSS/BPC
‘alidation Documentary Not to be applied
(Change
(0213 IMulti-Agency Common Basis [Approved IDSS/BPC
(Of Settlement (CBOS) Reports INot to be applied
(0214 Adding Year Of Birth To The [Approved IDSS/BPC
IEVP Data Set [Not to be applied
0215b Approval Of SADD Version 4 I Approved Documentation N/A
0216 Additional Granulation Of Approved DSS/BPC
FRM Reports. Not to be
applied
COMMERCIAL IN CONFIDENCE Page 66 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRION
ersion: 1.
Contents Description Date:25/06/99
0218 Report Of Attempted RPO! Approved DSS/BPC
Encashment Infringement Not to be
applied
0220 RPO! Operation I Approved DSS/BPC
Not to be
applied
0221 Control On-Line Interface Approved DSS/BPC
Between CAPS And Pathway I Not to be
applied
0222 Introduction Of New Versions I Approved Commercial & N/A
Of Consumables Schedules Implementation
Into DSS And POCL
Agreements
(includes CCN 152)
0223a I Reduce Number Of Retries I Approved DSS/BPC
: In EVP Not to be
: applied
0224 Lost Transactions And Approved DSS/BPC
: Duplicate Payments Not to be : oo
applied
0228b I Reference Data To Pathway I Approved CSR
Application Interface
Specification Version 3.3
New Version Of “CAPS To Approved DSS/BPC
PAS/CMS Data Interface Not to be
Definition & Validation applied
Rules”.
COMMERCIAL IN CONFIDENCE Page 67 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v eo
‘ersion: 1.!
Contents Description Date:25/06/99
IPAS/CMS Help Desk Enquiries [Approved
By BA Staff Pending CAPS On-I
Line Enquiries lot to be applied
10236 Restoration Of POCL Approved (Commercial IN/A
(Consumables (Ithaca Counter
Printer Ribbon)
(0237 Additional Signatories Approved (Administration IN/A
[0238 Schedule A02 Policies & (Approved (Administration IN/A
(Standards
0239a Clarification Of Requirement I Approved Commercial N/A
493
0240 Amendment To BES PPD Approved DSS/BPC
(R1c only) Not to be
applied
PUN Amendment To Aid Approved DSS/BPC
“NFA Delivery” Not to be
applied
Establishment Of New IDSS/BPC
(Contract Controlled Document INot to be applied
‘Major Post Offices”
Definition Of “Working Pending Administration
Documents” Approval
On hold
10246 Alignment Of BA MIS (Approved IDSS/BPC
Reporting Periods To Contract INot to be applied
(Charging Periods
(0247 lew Version Of CAPS To (Approved IDSS/BPC
IPAS/CMS Codes Files [Not to be applied
[Definitions (R2.2)
(0248 [Documentary Change To (Approved IDSS/BPC
(Clarify Validation Applicable ToINot to be applied
IPAS Customer Detail Records
0249a Introduction Of Logistics Approved CSR+
Feeder Service
(BRD V15)
(0250 (Checks Undertaken Within (Approved IDSS/BPC
(Card Collection Procedure INot to be applied
0251a Release Contents Approved Administration N/A
Description - New Release 2 I To be
superseded
(0252 Documentary Changes To (Approved IDSS/BPC
CPCS To PAS/CMS Error INot to be applied
(Codes (R3)
COMMERCIAL IN CONFIDENCE Page 68 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v eo
ersion:1.
Contents Description Date:25/06/99
(0253 Removal Of Restricted Post Approved IDSS/BPC
(Office Infringement Files From INot to be applied
[The PAS/CMS Interface
(0254 (CAPS/Pathway On-Line Fatal IApproved IDSS/BPC.
[Error Handling lot to be applied
Establishment Of A New Approved DSS/BPC
Contract Controlled Not to be
Document “Definitive List Of I applied
BA Districts”
Fraud Risk Management Approved DSS/BPC
Service Design - Change To I Not to be
Functionality Within The applied
FCMS Reports
NR2 Service Levels
(See CCN284)
PUN Modification Approved DSS/BPC
Not to be
applied
0261a Agreement Of AP Client Approved Documentation N/A
Take On Process - A2As
R545-1a & 1b &3
0262 General - Security Approved Documentation N/A
Contingency Plans - A2ZA R Implementation
830-2
0263a Detailed Format Of All Approved Documentation N/A
Interfaces - A2A R831 Commercial
0264 Interface Integrity Controls - I Approved Documentation N/A
A2A R891-1
(0266 [To Update Contract Controlled IApproved ‘IDSS/BPC
Document List With Release 1cINot to be applied
IPPDs
0267a I Introduction Of CAPS Approved DSS/BPC
Interface Version Control Not to be
Document (V31.02) Into applied
Baseline
0268a Introduction Of Virtual Approved CSR+
Private Networks (SG VPN)
0269 Customer Calls To PCHL To I Approved DSS/BPC
Report Under/Over Payment I Not to be
applied
COMMERCIAL IN CONFIDENCE Page 69 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref. PSTRION2
‘ersion:
Contents Description Date:25/06/99
0270 POCL Applications — Approved Documentation N/A
EPOSS: Transaction Times Implementation
(A2A R870-1)
0271 POCL Applications - EPOSS: I Approved Documentation N/A
Transaction Times (A2A Implementation
R870-2)
0272 Benefit Payment Service - Approved DSS/BPC
Service Levels: PAS Help Not to be
Desk (A2A R888-1) applied
10273 Benefit Payment Service - Approved IDSS/BPC
Service Levels: PAS Help DeskINot to be applied
(A2A R888-3)
10274 Benefit Payment Service - Approved IDSS/BPC
Service Levels: CMS Help INot to be applied
Desk (A2A R889-3)
(0275 (Card Management \Approved IDSS/BPC
Reconciliation (A2A R891-10) _INot to be applied
0276 DSS Implementation - Approved DSS/BPC
Customer Education: BPS. Not to be
Marketing & Education (A2A I applied
R916)
0277b Pathway To TIP AIS Update I Approved Documentation N/A
To V5.3
0278 Encashment Trailer Format Approved DSS/BPC
(DIDVR 6.04) Not to be
applied
0279 Benefit Payment Service - Approved DSS/BPC
Service Levels : CMS Help Not to be
Desk, (A2A Ref:R889-1) applied
0280 Implementation - Service Approved Documentation N/A
Level Agreement: Implementation
Operational Systems Help
Desk (A2A R914-3)
0281 Implementation - Service Approved Documentation N/A
Level Agreement: Implementation
Operational Systems Help
Desk (A2A R914-5)
0282 Benefit Payment Service- Approved DSS/BPC
Intfs: Service Boundary BPS I Not to be
MIS Repts To DSS (A2A applied
R939-2)
0283 Change Of Registered Office_I Approved Commercial N/A
0284 Measurement Of Printer Expired (CSR)
Times Linked to 2:
0285a Change To PO Logo On Approved DSS/BPC
Payment Cards Not to be
applied
0286d Introduction Of Training Approved Implementation N/A
Courses
0287 Lost Stolen Card Report Approved DSS/BPC
Parameter Changes Not to be
applied
0288 Modify Password Expiry Approved DSS/BPC
Parameter In OPS Not to be
applied (Ric)
COMMERCIAL IN CONFIDENCE Page 70 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release vi eo
fersion:1.
Contents Description Date:25/06/99
0289 APS Data Capture — A2A Approved Documentation N/A
Ref. Id: R547
0290a POCL Interfaces — (A2A Approved Documentation N/A
$831-8)
0291 Benefit Payment Service — Approved DSS/BPC
Interfaces: Service Boundary I Not to be
DSS Customer To CMS applied
(DSS Customer Enquiries) —
(A2A R936-1)
0292 Benefit Payment Service — Approved Documentation N/A
OPS Interface: ESNCS To
OBCS - (A2A R956-3)
(0293 larketing And Education Approved IDSS/BPC
Pater — Mccann-Erickson INot to be applied
(A2A $918-1)
(0294 (Marketing And Education (Approved IDSS/BPC.
[Partnership Empowerment — _INot to be applied
(A2A S918-2)
[0295 IMarketing And Education Approved IDSS/BPC
Partnership Responsibilities — INot to be applied
(A2A S918-3)
0296b “Functional Specification For I Approved DSS/BPC
CAPS Contingency Not to be
Payments” To Be Included In I applied
PWY Release 2 Baseline
Document Set
0297 War Pension Order Books (CSR)
Being Barcoded
0298 Establishment Of A New Approved DSS/BPC
CCD “Major Post Offices” Not to be
applied
APS Watercard Smart Approved
Product
302 APS Quantum Smart Product I Approved CSR+
0303a I Implement “CAPS To Approved DSS/BPC
PAS/CMS Codes Files Not to be
Definitions (Release 3)” applied
Version 12.02
0304a Flat Panel Display Monitors Approved CSR
FPDs)
COMMERCIAL IN CONFIDENCE Page 71 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v eo
ersion: 1.
Contents Description Date:25/06/99
PUN Information Notes Approved : DSS/BPC
(A2A R968) Not to be
applied
Introduction Of Document To Approved ~ Documenta ion
Define APS Client Baseline
10311b (Counter Hardware Design Submitted (CSR)
Specification
(0312a introduce References To POCLIApproved (Commercial IN/A
IHAPS Into Related AgreementsI
0313a HAPS Disaster Recovery Approved Documentation N/A
Proposal
0314 Operational Responsibility Approved DSS/BPC
For CAS VME Not to be
applied
(0315a _— Restore Duplicate Encashment Approved IDSS/BPC.
Reporting To CAPS In SADD___INot to be applied
0316 To Remove Five Post Approved DSS/BPC
Offices From The ‘Major List’ I Not to be
And Replace With Five New I applied
Post Offices
Amendment To Definitive List [Approved IDSS/BPC.
(Of BA District Offices INot to be applied
0319 Introduce DIDVR 6.07 As Approved DSS/BPC
New CCD Not to be
applied
0320a Update DIDVR To 6.06 As Approved DSS/BPC
New CCD Not to be
applied
0322c Changes To Control Card Approved
DSS/BPC
Population (Removal Of Not to be
Pathway Initiated End Of applied
Interest On PAS Stream)
0323a I Introduction Of Revised Administration N/A
Contract Controlled And
Referenced Document List
0324a User_Id- Consistent Length I Approved DSS/BPC
Not to be
applied
(0325 Amend COR Processing To = Approved IDSS/BPC
Allow Warning Reports To Be Not to be applied
Notified On The Error Report
File Associated With A Partial
Acceptance Receipt
COMMERCIAL IN CONFIDENCE Page 72 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release vi eo
ersion:1.
Contents Description Date:25/06/99
0326 Update Of The CCD List To Approved DSS/BPC
Include “PAS/CMS And Not to be
CAS(VME) Error Codes For I applied
CAPS’ Version 4.0
0327 APS Token Verification (CSR)
Service
0328 Update Of The CCD List To I Approved DSS/BPC.
Include “CAPS — PAS/CMS __I Not to be
Error Codes” Document applied
Version 005.02
Incomplete Transactions: Approvet
Fixes For Incomplete Not to be
Receipt, BES/OBCS applied
Corruption, New Card
Activation And User Logout
Categories
0331a Incomplete Transactions: Fix I Approved DSS/BPC
For User Setup Category Not to be
applied
0332 PAS Service Definition Approved Commercial
Wording Clarification Not to be
applied
0333a I Amend APS Client Baseline Documentation N/A
0334a Encashed Payment Approved DSS/BPC
Validation & Adjustment Not to be
From NR2 applied
(0335 Add PC12 To List of CCDs Approved IDSS/BPC
lot to be applied
0336 Introduce Version 8.1 of the Approved DSS/BPC
DSS Consumables Schedule I Not to be
(DSS B04) to the Related applied
Agreements Contract
Baseline
0337 2 OR 3 Week Cash Account__I Approved CSR
0338 To Introduce the APS Approved Documentation N/A
Acceptance Specification as
0340 To Introduce the Approved Documentation N/A
Implementation A (User
Training) Acceptance
Specification as a CCD
COMMERCIAL IN CONFIDENCE Page 73 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRION
ersion: 1.
Contents Description Date:25/06/99
0347 I To Introduce the Approved DSS/BPC
Implementation B (Customer I Not to be — gj <
Education) Acceptance applied
Specification as a CCD : as
0342 To Introduce the Approved Documentation N/A
Implementation C (Services)
Acceptance Specification as
aCcD
(0343 [To Introduce the MIS (Approved [Documentation IN/A
Acceptance Specification as a
(CCD.
(0344. [To Introduce the OBCS (Approved [Documentation IN/A
Acceptance Specification as a
(CCD.
(0345 [To Introduce the Security [Approved [Documentation IN/A
Acceptance Specification as a
(CCD.
0346 To Introduce the Service
Levels Acceptance
Specification as a CCD
Approved Documentation N/A
Siting Of Infrastructure Approved Implementation
Elements In An Outlet
(A2A R509)
AP Client Specifications Approved Documentation
(A2A R545-2)
0353 Timing Of Site Survey (A2A_ I Approved Implementation N/A
R945-48&5)
COMMERCIAL IN CONFIDENCE Page 74 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v eo
ersion: 1.
Contents Description Date:25/06/99
To Introduce the Audit Approved Documentation
Acceptance Specification as
aCcD
0362 To Introduce Updated Approved Documentation N/A
Version of OBCS Acceptance
Specification as a CCD.
Introduce Frame Relay Approved
Communications
[To Introduce the CMS (Approved
Acceptance Specification as a INot to be applied
ICCD
[0366 [To Introduce the PAS (Approved IDSS/BPC
Acceptance Specification as a INot to be applied
CCD.
To Introduce the DSS Approved DSS/BPC
Interface Acceptance Not to be
Specification as a CCD applied
Correction to COR Error Approved DSS/BPC
Report Trailer Not to be
applied
To Introduce the TIP Approved Documentation
Acceptance Specification as
aCcD
Introduce CAPS to PAS/CMS I Approved DSS/BPC.
DIDVR (CAPS Rel. 3.5) as Not to be
ccD. applied
0373 Issue New Version of the Approved DSS/BPC
Major Office List Not to be
applied
Introduce PSTN
Communications
British Gas Trading Simple Approved Documentation
Payment Module Smart But linked to
Product 411
COMMERCIAL IN CONFIDENCE Page 75 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release vl Reh PSTRIONZ
‘ersion: 1.!
Contents Description Date:25/06/99
0377 Introduce Application Approved CSR
Interface Specification (11/2/99)
Reference Data to Pathway Likely to be
Non-Automated Type B Data I further
superseded.
Pathway
attempting to
implement in
NR2
0378 To Introduce the EPOSS Approved Documentation N/A
Acceptance Specification as
aCCD
[0379 ITo Introduce the Help Desk (Approved [Documentation IN/A
Acceptance Specification as a
(CCD
(0380 [To Introduce the Reconciliation IApproved [Documentation IN/A
Acceptance Specification as a
(CCD
0381 To Introduce the Rollout Approved Documentation N/A
Acceptance Specification as
aCcD
0382 To Introduce the End-To-End I Approved Documentation N/A
Service Acceptance
Specification as a CCD
0383 To Introduce the Schedule Approved Documentation N/A
C3 Acceptance Specification
as a CCD
0384a Introduce Installation Approved Implementation N/A
Strategy, IM/STR/026 as a
Contract Controlled
Document
(A2As R489, R501, S489-1)
0385 BES Data in Encashment Approved DSS/BPC
Details from BES to PAS Not to be
(A2A R859) applied
0386 Number of Counter Positions I Approved Implementation N/A
(A2A R945-1)
0387 ESNCS - Restate Full Stops I Approved Documentation N/A
and Recalls List (A2A R956- Administration
1)
0388 To Introduce the Policies & Approved Documentation N/A
Standards Acceptance Commercial
Specification as a CCD
0389a Amendment to “CAPS to Approved DSS/BPC
PAS/CMS Data Interface Not to be
Definitions and Validation applied
Rules (R3, R3.5, and post
le 2)”
COMMERCIAL IN CONFIDENCE Page 76 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v eo
ersion: 1.
Contents Description Date:25/06/99
0391b I Introduction of Version 5.0 of
Horizon OPS Reports &
Receipts
(CSR)
0392 Revised Version of CAPS to
PAS/CMS Codes files
Definitions (Release 3)
DSS/BPC
Introduce Other Payee Role I Rejected (for DSS/BPC
Type ‘Split Payment Payee’ NR2+)
To be withdrawn
APS Receipt — Client and Approved
Scheme Name
The Removal of References DSS/BPC_
to Costing Recommendations
for Customer Education In
Requirements 916, 918, 919
To Introduce the POCL Documentation
Reference Data Interface
Acceptance Specification as
aCCD
Amendment to S708 to correct Approved IDSS/BPC.
typographical error lot to be applied
0404 Operational Responsibility for I Approved DSS/BPC
CAS VME Additional Not to be
Requirement Affected applied
0405a Amendment to S507 to Approved Implementation N/A
Reference CCD for Definition
of Christmas Period
0406 Delete Misplaced Text in Commercial N/A
POCL Schedule H08 (A2A
PH08-3)
0407 OPS Technology Refresh Approved Commercial N/A
(A2A R560)
COMMERCIAL IN CONFIDENCE Page 77 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRION
ersion: 1.
Contents Description Date:25/06/99
Clarify Wording re. Mobile Documentation
Configurations in Schedule
PGO1
Specify Temporary Token Approved — DSS/BPC
Encashment Period (A2A Not to be
$707-1) ‘ applied : <
0411a British Gas Trading Simple Approved CSR+
Payment Module Smart
Product
0412a Authorities Agreement Approved Commercial N/A
Schedule A06 Price
Adjustments for 1999
Invoice Design Documentation
(A2A PA10)
Introduction of 1999/2000 Approved
Cash Account
Activity within DSS premises I Approved DSS/BPC
(A2As R930, S930-1) Not to be
hae lied é :
APS Key Management Documentation
(A2A S952-2)
Appearance of the OPS Approved Documentation
Equipment
(A2A R465, 465-1)
OPS Interface ESNCS to Approved Documentation
OBCS
(A2A R956-2)
0423 Audit Trail Documentation N/A
(A2As R699, R942, S699-1,
S699-2, S699-3)
COMMERCIAL IN CONFIDENCE Page 78 of 1
© 1999 ICL PATHWAY LTD
ICL Pathway
ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
0426
Revision to Office Weekly
Suspense Account Report
Approved
CSR
0427
Client Report Upgrade to
1999/2000 Specification
Approved
0428b
CSR
Update CCD list to Introduce
New Versions of and
Additional Interface
Specifications
0429
N/A
Introduce Document
Scheduling Strategy as a
ccD
(A2A R517)
Approved Documentation
N/A
0430
EPOSS General Service
Levels
(A2A R871)
Approved Documentation
N/A
0434
Acceptance Specifications
Consolidated Caveats as a
ccD
Approved Documentation
N/A
Acceptance Incidents raised
by the Contractor
Approved Commercial
1999/2000 Cash Account
format — to allow ICL
Pathway to update the
Horizon Cash Account
Report to comply with
Revised Layout and
presentation 1824/1854
N/A
Update Contract Controlled Documentation
List to Introduce APS
Reports Document
0436 Security Statements Approved Documentation N/A
Document for Siemens
Metering Limited
0437 Extension of Training Approved Implementation N/A
Window in Live Trial for
Offices that Undertake an
Individual Stock Unit Balance
using ECCO+
Introduction of Network
Business Support Centre -
Live Trial
Reconciliation
(A2As)
Documentation
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 79 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRION
ersion: 1.
Contents Description Date:25/06/99
0444 Horizon OPS Reports and Documentation N/A
Receipts
(A2As)
Changes to the Pathway to Documentation
TIP AIS to support
Operational TIP at Release
2+
Introduce New Version of Documentation
DSS Client Interface
Specification/OBCS (V3a)
0453 Supply of Consumables Documentation NIA
(A2A S466-1
To Introduce the POCL Approved Documentation
Infrastructure Acceptance
Specification as a CCD
Resolution of Various A2As [Documentation
[Disaster Recovery Provision fot
[Huthwaite
Introduce the SFS Version Documentation
4.0 as a CCD
COMMERCIAL IN CONFIDENCE Page 80 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release vi eo
ersion:1.
Contents Description Date:25/06/99
[0464 [Introduction of the AP Client [Documentation IN/A
igration Strategy as a CCD
(A2As R971, S971-1)
[0465 Introduce the Security Policy [Documentation IN/A
ersion 4.0 as a CCD
0466 CCD AIS Reference Data to Documentation N/A
Pathway
SADD A2As
0467
To Link a POCL Financial
Year With a Set of Reports
and Mappings to Include the
Cash Account, Redeemed
Savings Stamps Summary
and Counters Revenue
Schedule
(0471 Restricted Functionality at
(Outlets
(A2A S473-1)
(0472 (Change to Requirement 818/3
0473a Facilitate the POCL
Management of Products
using Item Transaction Mode
0474 Introduce Document
“Removal of Existing
Customers from the Card
Scheme’ as a CCD
0475 Live Trial Enhancement 1 —
Validate the Office Brought
Forward Figure at Migration
0476 Live Trial Enhancement 2 —
Stock Declaration Process
for Shared Stock Units to
become Optional
(0477 Live Trial Enhancement 3 —
Allow Users to Select and Edit
Existing Stock, Stamp and
(Cash Declarations
(0478 Live Trial Enhancement 4 —
Reduction of Forced Cash,
Stock, Stamp Declarations
[0479 Live Trial Enhancement 8 —
[Remove the Cash Account
Snapshot Function
[0480 Live Trial Enhancement 7 —
[Declaration and Stock
Adjustment of Linked Products
Documentation
N/A
(CSRICSR+)
[Documentation
IN/A
Administration
IN/A
(CSR¥)
Approved Documentation
N/A
(CSR)
(CSR)
(CSR)
(CSR)
(CSR)
(CSR)
COMMERCIAL IN CONFIDENCE
© 1999 ICL PATHWAY LTD
Page 81 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v eo
fersion: 1.
Contents Description Date:25/06/99
(0481 Live Trial Enhancement 9 — (CSR)
Stamp Declaration by Volume
[Rather than Value
10482 Live Trial Enhancement 10 — (CSR)
Remove the Office Balance
Process
0483 Introduction of the NR2 PPDs Documentation N/A
as CCDs
10484 introduction of Additional Copy IR (CSR)
lof TMS Layer Following Loss ofI
Single Data Centre
(0485 Resolution of Group 20 A2As [Documentation IN/A
COMMERCIAL IN CONFIDENCE Page 82 of 1
© 1999 ICL PATHWAY LTD
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release V Ref: PNSTRIONZ
ersion:1.!
Contents Description Date:25/06/99
ADDENDUM C: CCN 215B FUTURE CHANGES
REQUIRED TO SADD
The following section provides the changes associated with the approval of
SADD v4.0 [1] and identifies the status of each given the termination of the
DSS contract and the removal of the Benefit Payment Card.
The following Key has been used in the ‘Status’ column to clarify the position:
E - indicates EXCLUDED
C — indicates a COMMENT has been made in the RCD
and the next SADD version will reflect
I - indicates INCLUDED in a release and the release
identity is given
OMMERCIAL IN CONFIDENCE Page 83 of 1
© 1999 ICL Pathway Ltd
ICL Pathway
ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
© 1999 ICL Pathway Ltd
IParaNo. IStep No. IReviewers Comments Explanation PMT Comment Status
land
Exception
No.
1. IGeneral In the scenarios where customers are referred to “the DSS”, [Agreed as future E
[this should be changed to “the local BA office” change
2. (The procedure for when there are no payments due on an [Agreed as future E
existing card and when a replacement card is available for jchange
collection appears to be missing.
3. 2.5.2 5" para 2"¢ bullet — add at end “, and in NI, SSA.” Agreed as future E
ichange
4. 2.5.2.2 ‘arious —_‘ [The description of the specific irregular encashment ‘Agreed as future E
patterns at 2.5.2.2 should be amended to include “by POCL Ichange
Region, BA Region or SSA” as appropriate
5. 3.1.1.3.1.2 IThis paragraph implies that DSS will have to manage 2 ‘Agreed as future E
different types of instructions: Urgent or Non-Urgent. The change
current Service Definition does not cover this, the matter of
‘Urgency" being more closely related to the issue of the
\Card (which itself is governed by the date the payment is
due), rather than the urgency of the introduction. Note that
ithe Service Level relates to the delivery of the Card rather
[than the speed at which the “introduction” is processed by
COMMERCIAL IN CONFIDENCE Page 84 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
© 1999 ICL Pathway Ltd
ICL Pathway. The necessity for DSS to further distinguish
between temporary and permanent “Urgent” introduction is aI
Inew Contracting Authorities Responsibility. Need to
lestablish Service Levels for “Urgent - Temporary
instructions” as the is no card issue — There is a Service
Level for on-line updating of personal details, which is 3
seconds if this is to be applied then it need to be clear.
6. 3.1.1.3.2.2 (0 — state here that easy access to archived records will be IAgreed as future E
provided. change to 3.1.3.7
7. 3.1.1.3.3 [1 para The meaning of “first order” and “second order” is unclear. IAgreed as future E
change
8. 3.1.1.3.3 The amendment to the fact that lifecycle is up to three cards IAgreed as future E
land therefore the paragraph should read current and change
previous card(s) has not been shown.
9. 3.1.1.3.4 & IE-CAPS advise that they currently do not propose to notify [Agreed as future E
3.1.1.6.2 lend of interest on emigration change
10. 3.1.1.4 41% para line 3, after “liveries” insert “(presently BA, SSA, WPA)” (Agreed as future E
change
11. 3.1.1.4.3 IUrgent Final bullet — as previous comment ‘Agreed as future E
jorders change
12. 3.1.1.5 para 4 ll note your response to AS’s comment on this para. ‘Agreed as future E
However, the para still implies that a card will be issued in change
IDLO cases. It needs re-wording to remove that impression.
COMMERCIAL IN CONFIDENCE Page 85 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOIZ
‘ersion:1.
Contents Description Date:25/06/99
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
See also comment on 3.1.1.5.1.1
13. 3.1.1.5.1.1 I2" para [See PW comment above on 3.1.1.5 4" para (Agreed as future E
change
14. 3.1.1.6.2 IDN Check Version of DIDVR.V6.3 is current version. Agreed as a future [E
change. Will refer to
DIDVR for CAPS
Release 4.
15. 3.1.1.6.4 (The instance when a card is too damaged to involve manual IAgreed as future E
keying needs to be recognised. change
16. 3.1.1.7.1 The extension of collection period to 3 months, under Agreed as future
exceptional circumstances, needs to be added change
17. 3.1.1.8.2 I Last para I In the case of no forwarding address, are DSS to be told Assumption E
that the card has not been issued, and, if so, how. correct, agreed as
future change
In the case of the speech or psychological impairment, E
Ipresumably only the case where the cardholder cannot be
identified will result in the reorder cycle being inappropriate
+ in which case the loss (or finding) would not be recorded
jon the database — please clarify
18. 3.1.1.8.4.5 [Final para [This needs to be cross-referred to CCN 124. The contracted [Agreed as future E
long term position is the provision of on-line enquiry access Ichange
ia CAPS. The interim solution is the provision of a multi-
jterminal enquiry helpdesk within DSS with access to the
COMMERCIAL IN CONFIDENCE Page 86 of 1
© 1999 ICL Pathway Ltd
ICL Pathway
ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
© 1999 ICL Pathway Ltd
CMS (and PAS) database.
19. 3.1.1.9.5.1 \This has not been included contrary to the claim. ‘Agreed as future E
change
Note that this comment was that 3.1.1.9.5.1 should point to
ithe proposed 3.1.1.9.6 reference that clerk should always
lask the customer whether he has a PUN.
20. 3.1.1.9.7 Meaning still unclear. What is “This process”? I think the (Agreed as future E
English needs tidying rather than anything substantial done. Ichange
21. 3.1.2.1 (Although notes say fixed, it has not been [Agreed as future E
change
22. 3.1.2.4.2 (The table of all comments wrongly shows that this comment [Agreed as future E
related to Para 3.1.2.3 change
3.1.2.4.2 is still deficient
23. 3.1.2.6.1 4 para [This doesn’t make sense, and may be redundant. (Agreed as future E
change
24. 3.1.2.6.2 ILast para [See comment on para 3.1.3.10.1.6 below. We need ‘Agreed as future E
information on duplicates top be passed to CAPS change. See
separate
correspondence.
25. 3.1.2.8/9/1 Please include refs to SLA. SLA refs are included against [Agreed as future E
COMMERCIAL IN CONFIDENCE Page 87 of 1
FUJ00078801
FUJ00078801
ICL Pathway ICL Pathway Core System Release v Ref: PASTRIOIZ
‘ersion:1.
Contents Description Date:25/06/99
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
(0 lother areas and so should be included here to be change
consistent.
26. 3.1.2.9 [This para doesn’t make sense. Payment enquiries originate [Agreed as future E
lin DSS domain. The contracted solution is for enquiries to change
lbe made from District Offices to PAS via CAPS. This should
lbe made clear.
27. 3.1.2.9 [The existing requirement was for on-line enquiry facility. Agreed as future E
Enquiries via the Help Desk are only envisaged before this \change. Interim
is available or once it is available, when the normal on-line [CAPS Helpdesk
service is non-operational. Has a CCN been approved ‘solution no longer to
Ichanging this? There may be significant cost implications _Ibe utilised.
due to premium charged for enquiries to help desk over
(7500 per year.
28. 3.1.3.7 See comment above (re para 3.1.1.3.2) on stating in SADD IAgreed as future E
jthat archived data will be easy to access. Consider includingichange
lstatement on principle here.
29. 3.1.3.8 to \various IThese paras need to make clear that SSA, BA and WPA ‘Agreed as future E
3.1.3.8.1.1 MIS will be shown separately, and that references to DSS _ change
2 staff, DSS Issuing Office and DSS Region, mean SSA staff,
ISSA Issuing Office or SSA where appropriate.
30. 4.1.1.1 (Change “benefit cards” to “Benefit Payment Cards”. (Agreed as future E
change
31. 4.1.1.10 IUncarded IThis para needs to reflect the agreement that whilst ‘Agreed as future E
casual Uncarded Casual Agents will be excluded from NR2 the change
COMMERCIAL IN CONFIDENCE Page 88 of 1
© 1999 ICL Pathway Ltd
ICL Pathway
ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
agent functionality to support them will be available at a later
provision _ Irelease if required.
32. 4.1.1.10.2 Mandate (ATP) will need amending — Is it the intention that Agreed as future E
[the list of ID will be required on the ATP? Where has this change
come from?
33. 4.1.1.10.2 Delete DN. As per comment on 4.1.1.10 (Agreed as future E
change
[The agreed items which form the basis of the Evidence of racperthes “ Kentty
Identity List are described within Contract A section 3, Ist will no longer be
Schedule 7. appropriate.
34. 4.1.1.12 IThe current method of reporting for BES receipts does not \Agreed as future E
provide the full functionality required for POCL to enable an Ichange DN to be
loutlet to complete their requirements for clients and inserted that this
laccounting. For 1C the principles as described have been __ report may be
laccepted and a work-around has been put in place. Further superseded by
development work is taking place for release 2. Please add [EPOSS reports.
IDN or caveat for the document which elucidates this point.
35. 4.1.1.2.2 [The clerk will contact the Payment Card Helpline, not the IAgreed as future E
ICMS Help Desk (note: this appears throughout the change
\document).
36. 4.1.1.2.2 (Change “Process and Procedures Document” to Processes \Agreed as future E
land Procedures Document (note: this appears throughout change
[the document).
© 1999 ICL Pathway Ltd
COMMERCIAL IN CONFIDENCE
Page 89 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
37. 4.1.1.3 IAdd “e.g.” before “suspected”. (Agreed as future E
change
38. 4.1.1.4.2 ID.N. We have agreed for release 1c to identify the 4new ‘Agreed as future E
\documents in a free text field in an abbreviated form i.e. B.C Ichange subject to
F- Birth Certificate agreement of
(CCN188
39. 4.1.1.4.2 It has now been agreed that a signature check is not [Agreed as future E
required (letter from Graham King to Karen Rogers 1/10/97 \change
refers).
40. 4.1.1.4.2 [The old card will not be provided if the customer has a PUN. IAgreed as future E
E If this relates to routine card replacement, the customer will Ichange
xcp 5 . ~
not provide proof of identity.
41. 4.1.1.5 (The statement that “This function is part of BES and is used Agreed as future E
ithin the Card Issue part of PCDF” appears to be change
misleading, as EVP can also be applied during encashment.
(Could “also” be added after “is used” to make this clearer.
42. 4.1.2.4.2 (Quantum cards are not a new service — they have always _IAgreed as future I CSR+
lbeen in the requirement change
43. 4.1.2.5 Para 1 should include “faulty/unreadable bar code” ‘Agreed as future IC
ichange
44. 4.1.3.1.1 It is wrong to say that ‘DVLA licences are restricted ‘Agreed as future IC
generally to Branch Offices’ and this should be removed. change
\There are currently about 4000 outlets doing MVL
© 1999 ICL Pathway Ltd
COMMERCIAL IN CONFIDENCE
Page 90 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
FUJ00078801
FUJ00078801
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
© 1999 ICL Pathway Ltd
transactions; less than 20% of which are Branch Offices.
45. 4.1.2.1.2.2 Last line “...balance can displayed...” ‘Agreed as future IC
change
46. 4.1.3.3.4 Para 4 — The printed cash account is still to include a 2D barAgreed as future IC
code eventually. This has only been accepted as an change
exclusion for release 2.
A7. 4.1.3.3.4 IThe removal or inclusion of 2D bar codes is not yet resolved IAgreed as future IC
(subject of CCN81d) ichange
48. 4.1.3.3.4 hat is the basis for the removal of the requirement to ‘Agreed as future IC
Iproduce a 2D bar code? ichange
My understanding is that this requirement was in place as IC
lan option for processing. If this option is no longer required
then it is appropriate that the requirement is removed.
However as this document does not articulate this and I
lhave no information as to how this decision was made, I
ould like some clarification.
49. 4.1.4.1 (5) (And throughout the document: the contractual reference and/Agreed as future IC
defined term for the DSS computer system is ESNCS, not [change
ESNS.
50. 4.1.5.3.3.2. ISFS 2.1 was never delivered to the PDA. Baselined version IAgreed as future Believe
1 is 2.0, version 2.4 is currently under review. As faras the [change should refer,
Para 2 Farnborough link, the expected solution is the one in the Ito
Interface Spec (signed off by PDA), and this is what's being 4.1.5.3.3.3.
COMMERCIAL IN CONFIDENCE Page 91 of 1
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
carried into subsequent 1.
IC
51. 4.1.6.10.2. I1% para 19 IWhilst it may turn out to cause difficulties to phone the help IAgreed as future IC
1.3 desk on all foreign encashments, the contracted position is Ichange
that it will be done. Note that DSS and POCL are currently
discussing the arrangements, and the sponsors’ decision
ill be dependent on Pathway’s proposed solution for help
desk functionality.
52. 4.1.6.10.2. The removal of OBCS help desk contingency has not been [Agreed as future IC
1.3 lagreed (repeated through this section) change
53. 4.1.6.13.1. IOBCS transactions should be based on the Control Notice [Agreed as future IC
i ffor nominated office transactions, and the OBCS Helpdesk change
ffor foreign transactions.
54. 4.1.6.13.1. \This contradicts information in the PO Not Available for ‘Agreed as future IC
iM Benefit Encashment document, as cards will be cancelled change
land new cards issued to the new nominated office in all
scenarios.
55. 4.1.6.2.1 (The reference to Duplicate Receipts should be removed. [Agreed as future IC
change
56. 4.2 (2) \‘....and Reference Data are....” ‘Agreed as future IC
change
57 Appendix Ai Figures AQ, A10, A11 and A14 should all contain Reference [Agreed as future IC
© 1999 ICL Pathway Ltd
COMMERCIAL IN CONFIDENCE
Page 92 of 1
FUJ00078801
FUJ00078801
ICL Pathway
ICL Pathway Core System Release
Contents Description
Ref.:PA/STR/012
Version:1.0
Date:25/06/99
FUJ00078801
FUJ00078801
ADDENDUM C: CCN 215B FUTURE CHANGES REQUIRED TO SADD
Data links within the map.
change
© 1999 ICL Pathway Ltd
COMMERCIAL IN CONFIDENCE
Page 93 of 1