CONFIDENTIAL
Version History
FUJ00234917
FUJ00234917
SCHEDULE B3.2
BUSINESS CAPABILITIES AND SUPPORT FACILITIES
Version No. Date Comments
1.0 31/08/06 Agreed version as at date of signature of CCN 1200
2.0 25/01/07 Baseline of 1.2
3.0 09/07/07 Baseline copy of 2.1
3.4 03/01/08 Applying CCN's1214,1217,1227c
4.0 14/04/08 Baseline copy of 3.1
41 12/06/09 Applying changes as per CCN1252a
6.0 06/07/09 Moving all schedules to V6.0 as agreed with Fujitsu
6.1 01/04/10 Applying changes as per CCN1270
7.0 10/05/10 Moving all schedules to V7.0 as agreed with Fujitsu.
8.0 21/02/12 Applying changes as per CCN1304b, CCN1310b,
CCN1286a and CCN1294d
9.0 13/01/14 Applying changes as per CCN1349, CCN1307a,
CCN1316a, CCN1320a, CCN1329a and CCN1342a
10.0 10/09/15 Applying changes as per CCN1338, CCN1409a,
CCN1410, CCN1411 and as subsequently amended in
this CCN1506, CCD reference updates and moving all
Schedules to V10.0 in accordance with CCN1506
11.0 31/03/16 Applying changes as per CCN 1427 and moving all
Schedules to Version 11.0 in accordance with CCN1604
12.0 03/07/17 Applying changes as per CCN 1605 and moving all
Schedules to Version 12.0
13.0 Applying changes as per CCN 1613a, CCN1640 and
moving all Schedules to V13.0
14.0 20/12/2021 Updating as per CCN1641c, CCN1658c, CCN1659a,
CCN1666b, CCN1623b, CCN1648b, CCN1668a,
CCN1669a, CCN1672a, CCN16778, CCN1677a and
moving all Schedules to V14.0
15.0 22/12/2022 Updating as per CCN1703a, CCN1715b, CCN1725a,
CCN1727, CCN1724a, CCN1738, CCN1739, CCN1741,
Schedule B3.2 Version 15.0
Page 1 of 36
CONFIDENTIAL
2a1
SCHEDULE B3.2
BUSINESS CAPABILITIES AND SUPPORT FACILITIES
INTRODUCTION
This Schedule records and specifies the Business Capabilities and Support Facilities
which are provided to Post Office.
Fujitsu Services shall operate and maintain:
1.2.1. each Business Capability and Support Facility listed in paragraphs 2 and 3 in
accordance with the terms of the Agreement;
1.2.2 all relevant CCDs as referred to in paragraph 7; and
1.2.3 all Service Levels as set out in Schedule C1.
The functionality and interfaces for the Business Capabilities and Support Facilities are
defined in the CCDs shown in Table A of paragraph 7 below and in the CCDs indicated to
relate to these Business Capabilities and Support Facilities in the CCD entitled “Post
Office Contract Controlled and Contract Referenced Document List”
(COM/CUS/SPE/0001).
The EUC Tower Contractor shall be responsible for keeping the HNG-A Application
software on the Replaced Branch Infrastructure up to date, using the HNG-A Application
Release version of the Software provided to the EUC Tower Contractor for distribution.
Fujitsu Services shall be responsible for issuing Releases as required for HNG-A
Application software, to the EUC Tower Contractor for distribution on the Replaced
Branch Infrastructure in Branches and Admin Positions and New CTO Configurations.
Any Business Capability or Support Facility that is to be accessed via the Counter Position
PC shall be provided in accordance with the CCD entitled “HNG-A UI Style Guide”
(DES/APP/STD/3433) which shall set out, among other things, general guidelines for the
Human Computer Interface.
HIGH LEVEL DESCRIPTION OF THE BUSINESS CAPABILITIES
Introduction
2.1.1 The functionality available at each Counter Position for serving Customers shall
comprise one or more Business Capabilities as specified below. The provision of
each Business Capability is dependant on one or more of the Support Facilities
described in paragraph 3.
2.1.2 The Business Capabilities shall be enabled by Fujitsu Services on all Counter
Positions in all Branches and Other Authorised Locations and shall require an
operational data communications link in order to process Transactions.
Schedule B3.2 Version 15.0
Page 2 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.1.3
Each Business Capability shall support a range of data selection, capture and
validation facilities which are controlled and constrained by Post Office Reference
Data. These facilities provide support for:
2.1.3.1 product selection mechanisms;
2.1.3.2 a range of data capture and validation routines;
2.1.3.3 the use of print templates in support of customised receipt and slip print
layouts.
The production of Post Office Reference Data to make use of the data capture
shall be in accordance with and subject to the provisions of the CCD entitled “AP-
ADC Reference Manual” (DES/GEN/MAN/0002). Post Office shall have
responsibility for:
2.1.4.1 the design and development of Transactions that utilise the facilities
described in the CCD entitled “AP-ADC Reference
Manual”(DES/GEN/MAN/0002);
2.1.4.2 ensuring that Post Office Reference Data, intended to introduce those
Transactions, functions correctly within the HNG-X System (in
accordance with any applicable Reference Data rules) and has the
desired business effect (save to the extent that Fujitsu Services is
required to facilitate testing of Post Office Reference Data in accordance
with the CCD entitled “Fujitsu Services / Post Office Ltd Interface
Agreement for Operational Business Change - Reference Data”
(CS/PRD/058)); and
2.1.4.3 defining receipts (for all Transactions that use the facilities described in
the CCD entitled “AP-ADC Reference Manual’(DES/GEN/MAN/0002).
This will not include the definition of any receipts used in conjunction with
Transaction or session recovery whose content and usage shall be jointly
agreed by the Parties.
2.2 Point of Sale Business Capability
2.2.1
The Point of Sale Business Capability provides a general "till" function which
enables Post Office to carry out sales operations within Branches for the range
of Post Office products defined within Post Office Reference Data.
These Post Office Products may be general retail products or be traded via one
of the following Business Capabilities (described below):
2.2.2.1 In/Out Payment Business Capability;
2.2.2.2 APOP Business Capability;
Schedule B3.2 Version 15.0
Page 3 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.2.3
2.2.2.3 Banking Business Capability;
2.2.2.4 Removed by CCN1724a;
2.2.2.5 Electronic Top-Up Business Capability; or
2.2.2.6 Bureau Service Business Capability.
The Point of Sale Business Capability implements (a) the business and pricing
rules for each product (including the production of the Transaction receipt(s)) and
manages the aggregation and recording of all Transaction data into a Customer
Session and (b) the Trade Restrictions unless the Training Controls have been
disabled using the Training Controls Disablement and Re-Enablement Service.
Transactions undertaken using the Point of Sale Business Capability shall be
recorded as part of a Customer Session and shall be committed as part of the
settlement process using the Payment Management Business Capability.
The Point of Sale Business Capability shall enable a Transaction to be cancelled
from a Customer Session subject to Post Office Reference Data, prior to
settlement by the Payment Management Business Capability.
28) In/Out Payment Business Capability
2.3.1
2.3.3
The In/Out Payment Business Capability enables Post Office to provide a range
of payment services to Customers comprising in-payment (e.g. bill payment) and
out-payment (e.g. postal order redemption).
The In/Out Payment Business Capability may be invoked through the use of
Tokens or other mechanisms and may involve the use of a range of data capture,
including CRM Tokens derived via CRM Tokenisation, data validation and
Transaction validation facilities.
The In/Out Payment Business Capability supports the following range of Tokens:
2.3.3.1 magnetic stripe cards; and
2.3.3.2 barcoded documents.
The Clients and Tokens supported by the In/Out Payment Business Capability
are set out in the CCD entitled “Automated Payments System Client List”
(BP/DOC/008).
Specific payment services and the Transactions which support them conform to
the relevant Application Interface Specification, the CCD entitled “POCL
Automated Payments Generic Rules” (BP/DOC/014) and appropriate Token
Technology Specification(s).
Schedule B3.2 Version 15.0
Page 4 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.3.5
2.3.6
2.3.10
The In/Out Payment Business Capability supports the use of HNG-X User
Interface components which may be specified via Post Office Reference Data as
being equivalent to a manually entered barcode token.
The In/Out Payment Business Capability may utilise data, typically comprising
tariff data, received from Clients.
The In/Out Payment Business Capability may access the PAF Support Facility,
APOP Business Capability and such other specific external applications as the
Parties may agree under the Change Control Procedure.
Transactions undertaken using the In/Out Payment Business Capability shall be
recorded as part of a Customer Session and shall be committed as part of the
settlement process using the Payment Management Business Capability.
Data captured as a result of an In/Out Payment Transaction shall be transferred
to Client systems and Post Office systems in accordance with the relevant
Application Interface Specification and shall be carried out using the File
Management Support Facility. Data captured as a result of an In/Out Payment
Transaction transacted for AP Client Account: 9999 shall not be transferred to
Client systems but shall continue to be transferred to Post Office systems.
Transactions undertaken using the In/Out Payment Business Capability and
taking place within the same POL Core Day as the original Transaction and
committed using the Payment Management Business Capability may
subsequently be Reversed in a new Customer Session, subject to such action
being allowed within Reference Data. This shall have the effect of Reversing the
accounting effect of the Transaction. Where a Transaction has been Reversed
then no data relating to the original Transaction or the Reversing Transaction shall
be sent to the relevant Client subject to the relevant Application Interface
Specification. It will not be possible to start a Reversal Transaction during the
period of three minutes before the end of the POL Core Day.
24 APOP Business Capability
2.4.1
The AP Out-Payments (APOP) Business Capability is a set of components that
support the creation of APOP Services. Each business application that makes
use of the APOP Business Capability will be segmented into its own APOP.
Service.
The components of the APOP Business Capability are as follows:
2.4.2.1 an APOP database which stores details of Transaction Vouchers and the
actions that have been performed on a Transaction Voucher by each
APOP Transaction;
Schedule B3.2 Version 15.0
Page 5 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.4.2.2 an APOP authorisation service which processes APOP Transactions by
applying the rules defined in the CCD entitled "APOP Definition"
(BP/SPE/046);
2.4.2.3 an APOP branch service that processes APOP on-line Transactions
initiated from an AP-ADC Transaction using the APOP authorisation
service referred to in paragraph 2.4.2.2;
2.4.2.4 an APOP batch service which will send/receive batch files to/from Post
Office Data Gateway and process APOP batch Transactions using the
APOP authorisation service referred to in paragraph 2.4.2.2;
2.4.2.5 an APOP administration service that will process APOP on-line
Transactions initiated from an APOP Administration Workstation using
the APOP authorisation service referred to in paragraph 2.4.2.2.
Transactions will be routed to the APOP authorisation service by a web
server;
2.4.2.6 an APOP reporting service that will process APOP Transactions to extract
records from the APOP database using the APOP authorisation service
referred to in paragraph 2.4.2.2;
2.4.2.7 an APOP housekeeping service that will process time-driven event APOP.
Transactions using the APOP authorisation service referred to in
paragraph 2.4.2.2;
2.4.2.8 an APOP archiving service that archives data from the APOP database;
2.4.2.9 a web service to route APOP on-line Transactions to the APOP database
for the APOP Service;
2.4.2.10 templates for the Customer receipt and the Branch receipt; and
2.4.2.11 templates for the office counter weekly and office weekly reports.
An APOP Service comprises at least the elements set out in paragraphs 2.4.2.3,
2.4.2.9, 2.4.2.10 and 2.4.2.11.
The production of Reference Data by Post Office to make use of the APOP
Business Capability shall be in accordance with and subject to the provisions of
the CCD entitled "APOP Authorisation Service Reference Manual"
(AP/MAN/004).
The CCD entitled "APOP Definition" (BP/SPE/046) sets out the rules that shall
apply in determining whether Post Office is required to request a Work Package
in respect of introducing additional APOP Services/AP Transactions using the
APOP Business Capability and/or modifying an existing APOP Service. Where
so required by the provisions of that CCD, Post Office shall request a Work
Schedule B3.2 Version 15.0
Page 6 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
Package for the introduction and/or modification (as applicable) of such
services/transactions.
Post Office shall be responsible for:
2.4.6.1 the design and development of new AP Transactions that use the APOP.
Business Capability;
2.4.6.2 (save to the extent that Fujitsu Services is required to facilitate testing of
Post Office Reference Data in accordance with the CCD entitled "Fujitsu
Services / Post Office Ltd Interface Agreement for Operational Business
Change - Reference Data" (CS/PRD/058)) ensuring that Post Office
Reference Data, intended to introduce those new AP Transactions,
functions correctly within the HNG-X System (in accordance with any
applicable Reference Data rules) and has the desired business effect;
2.4.6.3 defining receipts (for all AP Transactions that use the APOP Business
Capability). This will not include the definition of any receipts used in
conjunction with Transaction or session recovery whose content and
usage shall be jointly agreed by the Parties.
2.4.6.4 transforming incoming data files into standard APOP format according to
the APOP Interface Specifications for live purposes; and
2.4.6.5 generating required reports from extract files generated by APOP,
according to the APOP Interface Specifications for live purposes.
Transactions undertaken using the APOP Business Capability shall be recorded
as part of a Customer Session and shall be committed as part of the settlement
process using the Payment Management Business Capability.
25 Banking Business Capability
2.5.1
The Banking Business Capability enables Post Office to support the transaction
of banking business in Branches.
The Banking Business Capability is invoked by either:
2.5.2.1 a card swipe (or input of card details) where EMV functionality is not
supported in respect of that card; or
2.5.2.2 a Customer inserting their card into the chip card reader in a PIN Pad
where such card supports EMV functionality.
The following Transaction types are supported:
Schedule B3.2 Version 15.0
Page 7 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.5.6
2.5.3.1 cash deposit;
2.5.3.2 cash withdrawal;
2.5.3.3 balance enquiry; and
2.5.3.4 change of PIN at PIN Pad.
Each Transaction type comprises:
2.5.4.1 a series of screen dialogues;
2.5.4.2 the input or selection of data by the User;
2.5.4.3 the input of PIN numbers by Customers where applicable;
2.5.4.4 the interactive exchange of information via the Payment and Banking
Service with the Bank systems; and
2.5.4.5 the printing of receipts
Transactions undertaken using the Banking Business Capability shall be centrally
recorded as part of a Customer Session and shall be committed as part of the
settlement process using the Payment Management Business Capability.
Removed by CCN1725a
2.6 Removed by CCN1724a
27 Electronic Top-Up Business Capability
27.1
The Electronic Top-Up Business Capability enables Post Office to support the
Customer purchase or refund of mobile phone related credits and associated
content products (e.g. ring tones).
Electronic Top-Up ('ETU’) credit products (known as ‘Top-Up’ products or 'PIN'
products) are invoked by swiping a Customer's card (or by the manual input by
the Counter Clerk of the Customer's card details). ETU content products (known
as PIN/e-voucher products) are invoked by Counter Clerk selection. The following
Transaction types are supported:
2.7.2.1 the purchase of a card based Top-Up product;
2.7.2.2 the purchase of card based PIN product;
2.7.2.3 the purchase of a PIN/e-voucher product;
Schedule B3.2 Version 15.0
Page 8 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.7.2.4 the refund of a card based Transaction; and
2.7.2.5 the refund of a PIN/e-voucher Transaction.
Each Transaction type comprises:
2.7.3.1 the selection of ETU products from menus;
2.7.3.2 a series of screen dialogues;
2.7.3.3 the input or selection of data by the User;
2.7.3.4 the interactive exchange of information with e-pay; and
2.7.3.5 the printing of receipts.
Transactions undertaken using the Electronic Top-Up Business Capability shall
be centrally recorded as part of a Customer Session and shall be committed as
part of the settlement process using the Payment Management Business
Capability.
The Electronic Top-Up Business Capability shall automatically generate a
Reversal Transaction and transmit this to e-pay when the authorisation response
to certain Transaction types is not received within a pre-configured timeout
period.
2.8 Bureau Service Business Capability
2.8.1 The Bureau Service Business Capability enables Post Office to trade foreign
currencies and travellers’ cheques on-demand at Counter Positions (the on-
demand Bureau Service facility).
2.8.2 The Bureau Service Business Capability enables Post Office to pre-order
foreign currencies and travellers’ cheques at Counter Positions (the pre-order
Bureau Service facility).
2.8.3 The Bureau Service Business Capability enables Post Office to sell and top-
up travel money cards at Counter Positions (the travel money card Bureau
Service facility). The CRM Tokenisation element of the Payment and Banking
Service is used to allocate/substitute the PAN of the travel money card with a
CRM Token for use in records of Bureau Service Business Capability
Transactions.
2.8.4 The Bureau Service Business Capability enables Post Office to capture,
validate and report on the barcode or serial number on travellers’ cheques
traded.
2.8.5 The Bureau Service Business Capability enables Post Office to control the
Bureau Service facilities available at a Counter Position by Post Office
Reference Data
Schedule B3.2 Version 15.0
Page 9 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.8.6 The Bureau Service Business Capability enables Post Office to control the
currency types that can be traded by each Bureau Service facility at a Counter
Position by Post Office Reference Data
2.8.7 The counter dialogue for the Bureau Service facilities is controlled by Post
Office Reference Data in accordance with and subject to the provisions of the
CCD entitled “AP-ADC Reference Manual” (DES/GEN/MAN/0002).
2.8.8 The Bureau Service Business Capability enables Post Office to calculate up
to four quotes for each on-demand, pre-order or travel money card Bureau
Service Transaction and to present the quotes to the User
2.8.9 The Bureau Service Business Capability supports the ability to receive Spot
Rates Files and Margins & Commissions Files from Post Office in accordance
with CCD entitled “Post Office to Fujitsu Services Bureau de Change Rates
Interface Specification” (RD/IFS/033), and to use the data in these files to:-
2.8.9.1 control the rates at which currencies, travellers' cheques and travel
money cards are traded;
2.8.9.2 control the rates at which currencies and travellers’ cheques are
remitted, transferred and re-valued
2.8.10 The Bureau Service Business Capability supports the ability to receive Branch
Profile Files from Post Office and to use the data in a Branch Profile File to:
2.8.10.1 control the set of Margin Rates used when calculating quotes;
2.8.10.2 control the set of up-sell, value rounding and rate overriding
values specified in the Pricing Profile File which will be used when
calculating quotes;
2.8.11 The Bureau Service Business Capability supports the ability for Fujitsu to
receive Pricing Profile Files from Post Office and to use the data in these files
to control the up-selling, value rounding and rate overriding available in a
Branch.
2.8.12The Bureau Service Business Capability supports the ability for Fujitsu to send
Bureau Transaction and Control Totals Files to Post Office in accordance with
AIS ‘Bureau de Change Transactions Feed for FRTS' (NB/IFS/012).
2.8.13Transactions undertaken using the Bureau Service Business Capability shall
be recorded as part of a Customer Session and shall be committed as part of
the settlement process using the Payment Management Business Capability.
29 Postal Services Business Capability
2.9.1 The Postal Services Business Capability supports a range of Mails Acceptance
and Mails Administration business processes taking place within designated
Branches together with support for the establishment and management of Postal
Services Reference Data. These will comprise: -
2.9.1.1 services provided to Customers that support the pricing and sale of mails
products;
2.9.1.2 the management of mail items received into and despatched from a
Branch;
Schedule B3.2 Version 15.0
Page 10 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.9.2
2.9.3
2.9.1.3 the provision of data to Post Office and Postal Services Clients
concerning these operations;
2.9.1.4 tools to enable Post Office to establish and manage the Postal Services
Reference Data.
Mails Acceptance supports the over the counter processes for accepting mail
items from customers and comprises: -
2.9.2.1 the presentation and selection of valid primary, additional and value-add
mail services;
2.9.2.2 incremental price calculation based on service and option selection;
the capture and validation of data (including track and trace barcode
data, destination, PAF addresses, weight, size, service choice etc) at
defined points throughout the Transaction;
2.9.2.4 the application of business rules against captured data or Customer
selections which may constrain or enforce subsequent product / service
choices or data collection;
2.9.2.5 support for bulk mail acceptance, optionally varying the business
process steps and rules including additional data capture and price
validation;
2.9.2.6 the production of mails labels and Certificate of Postings upon
completion of the Mails Acceptance transaction as determined by
business rules and associated Reference Data;
the provision of on-screen help information, including Mails Carriers’
conditions of acceptance, as determined by Post Office in support of the
above facilities; and
2.9.2.8 the ability to conduct multiple Mails Acceptance Transactions without
requiring individual re-selection of the Postal Services function.
Mails Administration supports the in-Branch processes for receiving and
dispatching mails items and comprises:
2.9.3.1 the recording of the receipt of track and trace mails items into a Branch
for later collection by Customers;
2.9.3.2 the provision of an enquiry and priced mails collection service for
Customers;
2.9.3.3 the management of uncollected items;
Schedule B3.2 Version 15.0
Page 11 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.9.4
2.9.5
2.9.6
2.9.3.4 the management, reconciliation and reporting of mails items accepted
into a Branch via the Mails Acceptance facility. Certain mails items can
be excluded from this process as determined by business rules and
associated Reference Data;
support for a mails despatch and exception handling process for mails
items collected by Mails Carriers;
2.9.3.6 support for the receipt and reporting of undelivered priority mails items;
and
2.9.3.7 the provision of on-screen ‘Help’, including conditions of acceptance,
information as determined by Post Office in support of the above
facilities.
The Postal Services Business Capability supports the transfer to the BIG of track
and trace and related data captured by the Mails Acceptance and Mails
Administration facilities for selected Mails Carriers and the transfer of completed
Postal Services transaction data to various Post Office systems. This comprises:
2.9.4.1 transfer of data in accordance with the document entitled “AWS NRT and
Agent Lambda Solutions” (DES/APP/HLD/4410); and
2.9.4.2 transfer of completed Postal Services Transaction data to the POLSAP
Software, DIW & HR SAP as part of transfer of all other Branch
Transaction data.
The Postal Services Business Capability enables Post Office to specify and
manage the Carrier Services Reference Data which controls the options, choices
and pricing for all Carrier Services. This comprises a range of data preparation
and maintenance tools to allow Post Office to manage the Carrier Services
Reference Data in readiness for introduction into live operation. These tools will
define the allowable Carrier Services, the associated business data (e.g. pricing
tables and calculations) and associated business rules (e.g. data validation,
service constraints and options) to be specified and maintained.
Transactions undertaken using the Postal Services Business Capability shall be
recorded as part of a Customer Session and shall be committed as part of the
settlement process using the Payment Management Business Capability.
2.10 Payment Management Business Capability
2.10.1
The Payment Management Business Capability enables the settlement of a
Customer Session using cash, cheque, vouchers, Debit Cards or Credit Cards as
methods of payment.
Schedule B3.2 Version 15.0
Page 12 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.10.2
2.10.3
2.10.4
2.10.5
2.10.6
2.10.7
The Payment Management Business Capability manages the aggregation of the
required tender value for a Customer Session and provides change calculation
facilities.
The Payment Management Business Capability manages the production of any
AP Customer receipt and any required or requested Customer Session receipt
as part of the settlement of a Customer Session. The required layout of a AP
Customer receipt and a Customer Session receipt shall be defined in the CRD
entitled “HNG-X AP and ADC Receipts” (DES/GEN/SPE/0011).
The following Debit Card Transaction types (defined in CCD entitled " ( “Mapping
Schedule B3.2 to the HNG-X Solution” (REQ/GEN/REP/1091)) are supported by
the Payment Management Business Capability:
2.10.4.1 Debit Card purchase;
2.10.4.2 Debit Card Refund;
2.10.4.3 explicit Reversals;
2.10.4.4 Contactless Transactions; and
2.10.4.5 Contactless refunds.
The following Credit Card Transaction types are supported:
2.10.5.1 Credit Card purchase;
2.10.5.2 Credit Card Refund; and
2.10.5.3 explicit Reversals;
2.10.5.4 Contactless Transactions; and
2.10.4.5 Contactless refunds.
The Payment Management Business Capability implements the business rules
associated with the use of the Debit Card or Credit Card Method of Payment
which shall include the use of inclusion lists and exclusion lists which will specify
which products can be settled with which card types. Business rules will include
a transaction limit, set at a fixed amount which may be changed from time to time
via reference date by prior agreement with Post Office.
The Payment Management Business Capability implements the use of separate
authorisation dialogues using separate merchant identity/terminal identity values
for Bureau and non-Bureau products and the validation of the allowable products
and allowable settlement values according to the type of Debit Card or Credit
Card.
Schedule B3.2 Version 15.0
Page 13 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.10.8 The Payment Management Business Capability supports the Debit Card and
Credit Card Method of Payment via
the Payment and Banking Service.”
2.11 Cash and Stock Management Business Capability
2.11.1 The Cash and Stock Management Business Capability provides facilities to
enable all Branches to capture data (including cash declarations, inward /
outward remittances, pouch collection and receipt) for onward submission to the
POLSAP Software.
2.11.2 The Cash and Stock Management Business Capability supports the receipt from
the POLSAP Software of planned orders and replenishment delivery details.
2.11.3. The Cash and Stock Management Business Capability provides the following
facilities within Branches:
2.11.3.1
2.11.3.2
2.11.3.3
2.11.3.4
2.11.3.5
2.11.3.6
the display of screen dialogues that support cash and stock
transfers, cash and stock declarations, adjustments to cash
holdings;
scanning bar coded labels to monitor the movement of cash and
stock bags and pouches into the Branch;
the automatic inward remittance of the value of cash pouches
and bureau de change pouches using the associated
replenishment delivery details;
support for recording that selected cash and stock pouches and
bags are part of a REM Collection, or have been removed from
a REM Collection;
scanning bar coded labels to monitor the movement of cash and
stock bags and pouches that form a REM Collection out of the
Branch; and
a facility for viewing planned order details originated by the
POLSAP Software and transmitted to the Branch.
2.11.4. The Cash and Stock Management Business Capability supports the recording of
cash movements by Branches that are designated as Operator Cash Branches.
2.12. Branch Management Business Capability
2.12.1 The Branch Management Business Capability provides facilities to enable
authorised Users within any Branch to perform various administrative functions
including:
Schedule B3.2 Version 15.0
Page 14 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
2.12.11
2.12.1.2
2.12.13
2.12.1.4
212.15
2.12.1.6
Stock Unit balancing;
Branch accounting;
printing of Client summaries;
printing of Branch reports (including those on-demand reports
provided by POL SAP to Operator Cash Branches);
support for Reversals and Refunds; and
support for the application of Transaction Correction Records
supplied from the POLSAP Software.
2.13 Additional Branch Reporting Business Capability
2.13.1 The Additional Branch Reporting Business Capability supports the ability for Users to
access Branch reports using mechanisms other than Counter Positions or Admin Positions, such
mechanisms accessing the reports in accordance with the AIS ‘BRSS Data Access Server
(BDAS) to Branch Hub Als (DES/APP/AIS/3718).
3. HIGH LEVEL DESCRIPTION OF THE SUPPORT FACILITIES
3.1 Introduction
Fujitsu Services shall provide the following Support Facilities that support or enable the
provision of the Business Capabilities described in paragraph 2. The functionality of the
Support Facilities is provided via the HNG-X System.
3.2 Branch Administration Support Facility
3.2.1. The Branch Administration Support Facility, available in all Branches and
requiring an operational data communications link, comprises a range of
functions including:
3.2.1.1 User log on / off, which shall:
(a)
(b)
Schedule B3.2 Version 15.0
Page 15 of 36
authenticate all Users logging on to a Branch terminal using full
access control and password management facilities, which shall
require each User to be identified by a unique User ID and
individual password;
ensure that Users shall only access those Business Capabilities
for which they have been given permission by the Branch and in
FUJ00234917
FUJ00234917
CONFIDENTIAL
(c)
accordance with the Logon Restrictions of Training Controls,
unless they have been disabled using the Training Controls
Disablement and Re-Enablement Service; and
enable Users to log-on to a Branch terminal in their Branch in
accordance with their defined role. Any access to data or
services outside of that Branch is controlled exclusively by the
relevant Business Capability.
3.2.1.2 User / password management, which shall:
(a)
(b)
provide facilities to enable the Branch Manager to establish new
Users and set an initial password for all Users in a Branch.
Should a User forget their password the Branch Manager shall
be able to reset the password. The same procedure shall apply
at single Counter Position Branches and multiple Counter
Position Branches; and
for situations where the sole User (e.g. Branch Manager in a
single Counter Position Branch) has forgotten their password,
provide the facility to reset the User password. This shall be
triggered via the Service Desk and enabled via the Service
Management Service. The User shall then be able to reset their
User password.
3.2.1.3 Stock Unit creation / allocation, which shall allow authorised Users to:
(a)
(b)
(c)
(d)
introduce a new Stock Unit;
associate a user with a Stock Unit;
delete a Stock Unit; and
view details about a Stock Unit.
3.2.1.4 the provision of secure inactivity time-out facilities if a Branch terminal is
inactive for a period defined in Reference Data. Should the User be
unable to re-activate the time-out facility, the following actions may be
taken:
(a)
(b)
Schedule B3.2 Version 15.0
Page 16 of 36
after a period of time during which there is no active session, the
session shall be automatically logged-out;
the Branch Manager may assume responsibility for any
uncompleted session, the Stock Unit or share thereof, by
entering his own User name / password;
FUJ00234917
FUJ00234917
CONFIDENTIAL
3.2.1.5
3.2.1.6
3.2.1.7
(c) once the Branch terminal has logged-out, any authorised User
may then use that Branch terminal; and
(d) the above events shall be recorded as audit events.
The time-out facility shall allow the User to resume work with the
minimum delay consistent with achieving security in accordance with the
provisions of this Agreement.
Call logging, which shall enable a User via a Branch terminal to record
details of an Incident and for these details to be provided as a Service
Desk call to the Service Desk provided by Fujitsu up until the 2" July
2014. The system shall provide a unique call reference to the Incident.
For the avoidance of doubt this shall not be provided to the Service Desk
provided by the Next Supplier.
the provision of facilities to enable the User to:
(a) save a session by settling the session to a holding account;
(b) start a new session;
(c) display a list of saved sessions;
(d) select a saved session and recall the balance of the saved
session;
(e) undertake further transactions after recalling a session; and
(f) settle the recalled session.
the provision of facilities to enable Post Office Ltd to:
(a) Record postal services Reference Data in Selectica data format
using a set of spreadsheets designed by Fujitsu;
(b) Dispatch updates to postal services Reference Data by sending
populated versions of the above set of spreadsheets to Fujitsu;
(c) Require Fujitsu to upload populated sets of spreadsheets
provided by Post Office Ltd into the HNG-X Reference Data
preparation system (HRDP) ;
(d) I Enter postal services reference data that is not included within
the Selectica data format directly into the HRDP subsystem of
HNG-X
3.3 Branch Support Facility
Schedule B3.2 Version 15.0
Page 17 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
3.3.1
The Branch Support Facility, available in all Branches and requiring an
operational data communications link, comprises a range of support facilities to
facilitate the delivery of a Business Capability at a Counter Position including:
3.3.1.1 the provision of a generic and updateable User help system comprising
linked context sensitive pages;
3.3.1.2 the display of sales prompts;
3.3.1.3 the ability to support the bulk input of Transactions; and
3.3.1.4 facilities to support testing and resetting of various peripheral devices
(e.g. test printing on slip printer, clearing print queue for Back Office
printer).
3.4 Transaction Management Support Facility
The Transaction Management Support Facility provides support for Transaction
aggregation and Transaction storage.
The Transaction Management Support Facility also provides facilities to allow authorised
Post Office personnel to have enquiry access to Banking Transaction data using the
Payment and Banking Service Web Portal.
3.5 File Management Support Facility
3.5.1
3.5.2
The File Management Support Facility provides support for the automatic receipt
and dispatch of batch files between the HNG-X System and Clients, other third
parties, Post Office systems external to the HNG-X System and the POLSAP
Software.
Outbound batch files contain data originating from Business Capabilities that are
produced in accordance with the relevant AIS.
Inbound batch files are received directly from Clients or other third parties and
contain data for use by a Business Capability.
All data transfers shall be in accordance with the relevant Application Interface
Specification and Technical Interface Specification as specified in the CCDs
indicated to relate to these Business Capabilities and Support Facilities in the
CCD entitled “Post Office Contract Controlled and Contract Referenced
Document List” (COM/CUS/SPE/0001).
3.6 Reference Data Support Facility
Schedule B3.2 Version 15.0
Page 18 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
3.6.1
3.6.7
The Reference Data Support Facility supports the receipt of Post Office
Reference Data for use by either business or system operations. Business
related Reference Data comprises information that relates to particular
Transactions. System related Reference Data comprises information that relates
to the state of the Branch and its associated software base (e.g. Event
management details, software version numbers).
Reference Data provided by Post Office comprises the definition of the properties
and relationships of the data to be processed and the processing methods that
are to be used. Reference Data use date/time and version controls, and are also
be used to control product availability within Branches. Additional Reference
Data may be created by Fujitsu Services.
Reference Data received from the Post Office Reference Data System shall be
in accordance with the CCD entitled “Application Interface Specification
Reference Data to Fujitsu Services Limited” (BP/IFS/010). The Reference Data
Support Facility also supports the manual input of data by Fujitsu Services’
personnel and incorporation of system generated data from other parts of the
HNG-X System.
The Reference Data Support Facility supports the receipt of Reference Data from
the Post Office Reference Data System delivered in separately identifiable
change instructions in accordance with the CCD entitled “Reference Data
Management Service: Service Description” (SVM/SDM/SD/0013). These change
instructions are then made available to a daily extract process when correct
authorisation for each request is received from Post Office. Details regarding the
delivery and authorisation of Reference Data are given in the following CCDs:
3.6.4.1 for products, “Fujitsu Services / Post Office Ltd Interface Agreement for
Operational Business Change - Reference Data” (CS/PRD/058); and
3.6.4.2 for Branches, “Post Office Limited Operational Business Change —
Branch, Interface Agreement” (SVM/SDM/STD/0001).
The Reference Data Support Facility:
3.6.5.1 provides support for version control of Reference Data including start and
end dates for its validity; and
3.6.5.2 manages the distribution of Reference Data to Branches via the HNG-X
System.
The Reference Data Support Facility provides data used by all the Business
Capabilities and has the potential to extend this to additional Business
Capabilities running on the HNG-X System.
The Reference Data Support Facility checks Reference Data consistency and
reports any exceptions.
Schedule B3.2 Version 15.0
Page 19 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
3.7 PAF Support Facility
3.7.1
The PAF Support Facility is a generic facility used by certain Business
Capabilities to:
3.7.1.1 allow Users to validate an address against the PAF Database by entering
the details of premises and postcode or premises, street and town of the
address to be validated;
3.7.1.2 present Users with a validated postal address;
3.7.1.3 permit Users to enter a postal address manually; and
3.7.1.4 make available the manually entered postal address for use by the
Branch Transaction that invoked the PAF Support Facility.
The PAF Support Facility is available at all Counter Positions in all Branches (but
access to the PAF Support Facility is only available at locations with an
operational data communications link)
3.8 Message Handling Support Facility
3.8.1
The Message Handling Support Facility supports the creation by Post Office of
plain text based messages which are distributed to all or selected Branches.
Within a Branch, Users may select messages for display and subsequent printing.
The Message Handling Support Facility is available at all Counter Positions in all
Branches (but messages can only be received at locations with an operational
data communications link.)
3.9 Audit Support Facility
3.9.1
The Audit Support Facility enables the recording of an operational audit trail and
a commercial audit trail as defined in the CCD entitled "Audit Trail Functional
Specification" (CR/FSP/006). These comprise the audit trail associated with:
3.9.1.1 the set of audit events as set out in the CCD entitled "Audit Trail
Functional Specification" (CR/FSP/006)
3.9.1.2 the operation of:
(a) the Horizon Applications in each Branch prior to the HNG-X Date
in respect of that Branch; and
(b) Business Capabilities and Support Facilities in each Branch after
Branch migration has occurred in respect of that Branch; and
Schedule B3.2 Version 15.0
Page 20 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
3.10
3.9.1.3 the audit trail of that part of Fujitsu Services’ internal commercial records
to which Post Office's internal auditors or agents, as specified in
Schedule D5, have access.
The audit trails shall conform to the CCD entitled "Audit Trail Functional
Specification" (CR/FSP/006).
3.9.2 Data within the operational audit trail shall be retained for eighteen (18) months,
although; the set of records associated with a transaction voucher transacted by an APOP.
Service shall be retained for seven (7) years; and Transaction data relating to
Transactions originated from the Banking Business Capability and data relating to
Transactions that are settled using the Debit Card or Credit Card Method of Payment,
processed under the Payment and Banking Service, shall be retained for fifteen (15)
months.
3.9.3 Data within the commercial audit trail shall be retained for seven years, although
some data will be retained for the term of this Agreement which may be longer.
3.9.4Access to audit trail data is provided to authorised Post Office personnel either by
interactive access or through a set of standard reports.
3.9.5Security of data and audit trail
All data captured at the Data Centre either as part of a Transaction performed at
a Counter Position or as an administration function shall form part of a unique
Transaction which shall have a unique reference number. The format of this
Transaction shall vary according to the Transaction type but will typically contain:
(a) Branch Code;
(b) Counter Position ID;
(c) unique Transaction ID;
(d) date;
(e) time;
(f) User ID; and
(g) Transaction details.
Reconciliation Support Facility
3.10.1 The Reconciliation Support Facility and associated reports support Post Office in
establishing a common financial position between Post Office and those Clients
and other third parties whose own processes may cause them not to accept a
Transaction performed in a Branch.
Schedule B3.2 Version 15.0
Page 21 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
3.10.2
Reports will be produced and provided to Post Office and the Reconciliation
Support Facility will be supported by the processes specified in the CCD entitled
“End to End Reconciliation Reporting" (SVM/SDM/SD/0020).
3.11 Training Support Facility
3.14.1
3.11.2
3.11.3
3.11.4
3.11.5
3.11.6
3.14.7
3.11.8
The Training Support Facility supports training from CTOs enabling each CTO
Counter within a CTO to operate an independent training environment.
The Training Support Facility utilises those aspects of the Business Capabilities
and Support Facilities that provide Branch based capability together with
separate functionality to simulate online interfaces which will return pre-defined
simulation responses. For transactions that would be performed using Payment
and Banking Service in Branches, an emulator is provided to emulate interactions
with the Payment and Banking System. The emulator implements a fixed set of
responses as described in the document entitled “CTO C3 Emulator User Guide”,
(DES/GEN/MAN/4318).
Users of the Training Support Facility will generate Training Transactions and
Training Data that will be separated and separately identifiable from HNG-X
Transactions and data. Training Data will not be passed to external clients or the
audit stream.
Reports generated using the Training Support Facility will reflect the Training
Transactions performed during the Training Session and stock levels reported will
be adjusted accordingly.
Post Office will establish and manage each CTO Branch as a Branch within the
live estate and each will be allocated their own Branch Code which will indicate
that they are a CTO Branch.
The Training Support Facility will utilise Replaced Branch Infrastructure and will
require the use of an operational data communications link in order to process
Training Transactions. Each CTO Counter within a CTO will be connected by
LAN through the shared single branch router, and there will be a shared back
office printer.
The Training Support Facility will enable the Training Data of a CTO Counter to
be reset back to a pre-defined default state.
The Training Support Facility will require the use of an operational data
communications link in order that updates of software change and reference data
can occur. This may take place automatically in the same manner as for Branches
or at points in time that are agreed between Fujitsu Services and Post Office.
Schedule B3.2 Version 15.0
Page 22 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
4. ADDING NEW BUSINESS CAPABILITIES OR SUPPORT FACILITIES
41 Introduction
4.141
When a new Business Capability or Support Facility is to be added under the
Change Control Procedure, the following actions shall be completed:
4.1.1.1 a high-level description of the Business Capability or Support Facility
shall be incorporated into paragraphs 5 or 6 including a statement of any
interdependency with any existing (or new) Business Capability or
Support Facility as appropriate;
4.1.1.2 the relevant Schedules to this Agreement shall be updated to record the
new Business Capability or Support Facility, including:
(a) Schedule 1 (Interpretation);
(b) Schedule C1 (Service Level Principles and Remedies);
(c) Schedule A5 (Post Office Responsibilities);
(d) this Schedule B3.2 (Business Capabilities and Support
Facilities); and
(e) other Schedules to this Agreement, as relevant; and
Relevant CCDs shall be created or updated and referenced from the table
contained in paragraph 7.
5. ADDITIONAL BUSINESS CAPABILITIES
This paragraph will include brief descriptions of each new Business Capability.
5.1.1
Paragraph removed by CCN1725aRemoved by CCN1725a.
5.2 Channel Integration Capability
5.2.1
The Channel Integration capability enables non-HNG-X devices to access a
subset of HNG-X services through the use of a collection of technical services
that handle the inbound and outbound messages to the non-HNG-X device and
integrates with the HNG-X services.
5.3 Paragraph removed by CCN1640a
5.3.1
Not Used
5.4 Smart Metering Capability
Schedule B3.2 Version 15.0
Page 23 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
5.4.1
The Smart Metering capability means the web service provided by Fujitsu that
allows customers of British Gas to access and top up their Smart Card for usage
on British Gas Meters.
6. ADDITIONAL SUPPORT FACILITIES
This paragraph will include brief descriptions of each new Support Facility.
6.1 Generic Web Services (GWS) Support Facility
6.1.1
Fujitsu Services will provide a set of services as defined in Annex C of the CCD
‘Data Centre Operations Service: Service Description’ (SVM/SDM/SD/0003) to
enable GWS Clients to be developed, tested and deployed in the Fujitsu Data
Centre.
The Generic Web Services Support Facility provides a generic set of facilities in
the Fujitsu Data Centre which enables Post Office to:
6.1.2.1 define new GWS Clients;
6.1.2.2 amend or update existing GWS Clients defined using the Generic Web
Services Support Facility;
The Generic Web Services Support Facility enables messages to be received
from, and responses to be sent to, an In/Out Payment Counter Transaction as
defined in the CCD entitled “AP-ADC Reference Manual” (DES/GEN/MAN/002)
and the ‘APOP Authorisation Service - On-line Application Interface
Specification” (AP/IFS/064);
The Generic Web Services Support Facility enables messages to be sent to, and
responses to be received from, the GWS Client over the internet;
The Generic Web Services Support Facility enables messages sent to, and
responses received from, the GWS Client to be encrypted as defined in the ‘Web
Service Client Connection Process’ (REQ/GEN/PRO/1386);
Using the ‘Web Service Client Connection Process’ (REQ/GEN/PRO/1386) the
Generic Web Services Support Facility enables Post Office to define for a Generic
Web Service Client:
6.1.6.1 the routing of on-line messages between an In/Out Payment Counter
Transaction and a GWS Client;
6.1.6.2 the transaction mapping between the In/Out Payment message format
and the GWS Client message format:
Schedule B3.2 Version 15.0
Page 24 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
e field mapping;
© field validation;
«data transformation;
6.1.6.3 the response code mapping between the response received from the
GWS Client and the response returned in the In/Out Payment Counter
Transaction;
6.1.6.4 the message data which must not be written to the Generic Web Service
log file;
6.1.6.5 the network connection type.
6.2 Client File Delivery Support Facility
6.2.1 The Client File Delivery Support Facility enables:
6.2.1.1 transactions in PayStation and Post & Go-transaction files to be
posted into the branch accounts;
6.2.1.2 transactions in the PayStation and Post & Go transaction files to be
collated with HNG-X counter transactions;
6.2.1.3 delivery of collated AP transaction data to Post Office Clients;
6.2.1.4 delivery of collated transaction data to POL MI Services;
6.2.1.5 Not Used;
6.2.1.6 collated AP transaction data to be summarised and delivered client
transaction summaries;
6.2.2 The Client File Delivery Support Facility enables Data Files to be transferred
to/from the Post Office Data Gateway Support Facility
6.3 Post Office Data Gateway Support Facility
6.3.1 The Post Office Data Gateway Support Facility enables Data Files to be
transferred between:-
6.3.1.1 the HNG-X Data Centre and Post Office Clients;
6.3.1.2 the Post Office Data Centre and the HNG-X Data Centre;
6.3.1.3 Post Office Clients and the Post Office Data Centre;
6.3.2 The Post Office Data Gateway Support Facility enables:-
6.3.2.1 Data File transfers to the Post Office Data Gateway Support Facility
to be initiated by the Post Office Data Gateway or by Post Office or its
Clients;
6.3.2.2 Data File transfers from the Post Office Data Gateway Support Facility
to be initiated by the Post Office Data Gateway or by Post Office or its
Clients;
Schedule B3.2 Version 15.0
Page 25 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
6.3.3
6.3.4
The Post Office Data Gateway Support Facility enables a Data File received
by the Post Office Data Gateway Support Facility in one format to be
transformed into another format that is supported by either Post Office or its
Clients;
The Post Office Data Gateway Support Facility enables Data Files received
by the Post Office Data Gateway Support Facility to be merged into a single
Data File;
The Post Office Data Gateway Support Facility enables Data Files output by
the Post Office Data Gateway Support Facility to be transferred to one or more
recipients;
The Post Office Data Gateway Support Facility enables Data Files to be
transferred using one of the Post Office Data Gateway Support Facility
protocols specified in the ‘Post Office Data Gateway to Post Office Clients
Technical Interface Specification’ (DES/NET/TIS/1499);
The Post Office Data Gateway Support Facility enables Data Files to be
transferred from an external (to the HNG-X Data Centre) sending service, or
transferred to an external (to the HNG-X Data Centre) receiving service, using
the internet.
6.4 Common Digital Platform Adaptor
6.4.1
The Common Digital Platform Adaptor relays messages received from the
HNG counters using AP-ADC scripts to the external platform known as
Common Digital Platform and relays the responses from Common Digital
Platform back to the HNG counters.
6.5 Counter Web Browser Support Facility
6.5.1
The Counter Web Browser Support Facility provides mechanisms for a web
browser session to be initiated from the HNG-A Application at a Counter
Position.
When initiated from the HNG-A Application the Counter Web Browser
Support Facility will initiate the “WebView2” web browser software, provided
as part of the Replaced Branch Infrastructure, and have it browse to the
specified URL. For the avoidance of doubt, Fujitsu Services resources shall
have no visibility, access or liability to User's use of the Counter Web
Browser Support Facility. Fujitsu Services’ support shall be limited to the
initiation of the Counter Web Browser and browsing to the initial URL, as
specified in Reference Data, all usage beyond this by Users is outside of the
scope of Fujitsu Services’ support of the Counter Web Browser Support
Facility.
The button(s) within the HNG-A Application to initiate the browser and the
URL to be browsed to on initiation will be defined by Post Office, in
Reference Data.
Schedule B3.2 Version 15.0
Page 26 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
6.5.4
6.5.7
The HNG-A Application and the “WebView2” web browser software will be
run as separate processes. No data will flow from the “WebView2” browser
software into the HNG-A Application and, apart from the initial URL to be
browsed to, no data will flow from the HNG-AApplication to “WebView2”.
The Counter Web Browser Support Facility will not support browsing to
URLs which require external applications to be launched nor will it allow
downloads, uploads, “Save” or “Save As” options, pop-up windows or new
tabs.
On exit from any web browser session, when ‘Close’ is selected by the user,
the Counter Web Browser Support Facility shall delete all user-related
browser cached data, including browsing history, locally cached files, data
entered into fields and stored cookies.
The Post Office Responsibilities documented in paragraph 11 of Annex B of
Schedule A5 represent those responsibilities on which Fujitsu Services
depend on, in order to provide the Counter Web Browser Support Facility.
Whilst Fujitsu Services will be able to deliver the Counter Web Browser
Support Facility without the following responsibilities being met, they will not
be provided by Fujitsu Services and Fujitsu Services will accept no
responsibility or liability for any consequences as a result of these
responsibilities not being delivered by Post Office except for instances where
Post Office fails to meet its obligations as a direct result of Fujitsu Services’
acts or omissions or subsequently met by a User. Post Office shall be
responsible for;
6.5.7.1 Maintenance, patching and support of the “WebView2” and “.Net
Framework v4.8” softwares provided as part of the Replaced Branch
Infrastructure.
6.5.7.2 Provision of Reference Data defining permitted use of the Counter
Web Browser Support Facility in Branches and at Counter Positions
and initial URL(s) to be browsed to.
6.5.7.3 Security of the Replaced Branch Infrastructure, including any provision
of antivirus/malware scanning and protection, user authentication and
access permissions and security certification that Post Office choose
to implement.
6.5.7.4 Disablement of copy/paste and keyboard shortcut functionality to
inhibit movement of data between the “WebView2” browser software
and the HNG-A Application. Also, disablement of application switching
functionality (from Counter Web Browser to HNG-A) such that the
“WebView2” browser software must be closed before the user is
returned to the HNG-A Application.
Schedule B3.2 Version 15.0
Page 27 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
6.5.7.5 Configuration of Replaced Branch Infrastructure to allow/disallow
browsing to specified sites.
6.5.7.6 All browsing activities performed by Users accessing the Counter Web
Browser Support Facility.
Te LIST OF RELATED DOCUMENTS.
71 Business Capability and Support Facilities definitions
7.1.1 Prior to start of Trigger Point T5 (Data Centre Ready for HNG-X), the provisions
of Schedule B4.2 (Horizon software) applied and was linked to a number of
definition documents. Following the implementation of Project HNG-X these
documents were withdrawn.
7.1.2 This Schedule B3.2 provides a summarised description of the HNG-X Business
Capabilities which defines the functionality available at each Post Office Counter
for serving Customers and the Support Facilities which define the administration
and background functionality used by Branches.
7.1.3 In addition, the CCD entitled ‘Mapping Schedule B3.2 to the HNG-X Solution’
7.2
(REG/GEN/REP/1091) provides a list of the existing Solution Baseline
Documentation Sets and Contract Controlled Documents that apply to each
Business Capability and Support Facility described in this Schedule B3.2.
The CCDs and CRDs listed in Table B below supplement the document described in
paragraph 7.1.3 and relate to more than one Business Capability / Support Facility.
Table B
FUJ00234917
FUJ00234917
Document Title
Fujitsu Services Reference
HNG-X Technical Security Architecture
CCD ARC/SEC/ARC/0003
Horizon OPS Reports and Receipts - Post
Office Account Horizon Office Platform
Services
CCD SD/DES/005 (Replaced by (CCD)
(DES/GEN/SPE/0008) September 2011,
(CCD) (DES/GEN/SPE/0009) December
2013, (CRD) (DES/GEN/SPE/0010) May
2015, (CRD) (DES/GEN/SPE/0011)
November 2013
HNG-A UI Style Guide
(CCD) DES/APP/STD/3433
Schedule B3.2 Version 15.0
Page 28 of 36
CONFIDENTIAL
8. POL Service Types
8.1 The POL Service Types applicable to the period after Acceptance Point Z3 are set out in
8.2
8.3
9.1
Annex 1 to this Schedule.
If Post Office notifies Fujitsu Services in writing that it no longer requires use of a POL
Service Type and requests that Fujitsu Services disable that POL Service Type in
accordance with Clause 10.5, then where Post Office ceasing to use that POL Service
Type may affect the use of any other POL Service Type(s), Fujitsu Services shall advise
Post Office accordingly. Where Fujitsu Services so advises Post Office, the Parties will
discuss and agree (acting reasonably) the appropriate steps to be taken to address the
effect of disabling the POL Service Type on any other POL Service Type(s).
In relation to the Generic Web Services (GWS) Support Facility, the GWS Client list that
shall be maintained by Fujitsu Services is set out in Annex 2 to this Schedule B3. Should
Post Office Limited no longer require use of a GWS Client it shall give Fujitsu Services
no less than 30 days written notice.
ASSOCIATED DOCUMENTS
The following CCDs are associated with this Schedule B3.2:
Document Reference Document Title
1 ARC/SEC/ARC/00003 HNG-X Technical Security
Architecture
2 SD/DES/005 Horizon OPS Reports and Receipts
- Post Office Account Horizon
Office Platform Service
3 DES/APP/STD/3433 HN UI Style Guide
4 COM/CUS/SPE/0001 Post Office Contract Controlled and
Contract Referenced Document
List
5 DES/GEN/MAN/0002 AP-ADC Reference Manual
6 CS/PRD/058 Fujitsu Services / Post Office Ltd
Interface Agreement for
Operational Business Change -
Reference Data
7 BP/DOC/008 Automated Payments System
Client List
8 BP/DOC/014 POCL Automated Payments
Generic Rules
9 EF/SER/001 Debit Card MoP _ Functional
Description
Schedule B3.2 Version 15.0
Page 29 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
10 AP/MAN/004 APOP Authorisation — Service
Reference Manual
11 BP/SPE/046 APOP Definition
12 SVM/SDM/SD/0020 End To End _ Reconciliation
Reporting
13 CR/FSP/006 Audit Trail Functional Specification
14 SVM/SDM/SD/0013 Reference Data Management
Service: Service Description
15 SVM/SDM/STD/0001 Post Office Ltd Operational
Business Change - _ Branch,
Interface Agreement
16 Not Used Not Used
17 BP/IFS/010 Application Interface Specification
Reference Data to Fujitsu Services
Limited
18 AS/IFS/001 (withdrawn) Horizon to Post Office Feed Feed
for Track and Trace Application
Interface Specification (withdrawn)
19 DES/APP/AIS/0009 Horizon Online — Streamline
Application Interface Specification
20 ARC/SOL/ARC/0001 HNG-X = Solution — Architecture
Outline
21 ARC/SEC/ARC/0002 Horizon Security in the absence of
HNG-X
22 REQ/GEN/REP/1091 Mapping Schedule B3.2 to the
HNG-X Solution
23 DES/GEN/SPE/0008 HNG-X Branch and Counter
Reports
24 DES/GEN/SPE/0009 HNG-X Receipts, Slips and Labels
9.2 The following CRDs are associated with this Schedule B3.2.
(DES/GEN/SPE/0011)
HNG-X AP and ADC
Receipts
Schedule B3.2 Version 15.0
Page 30 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
FUJ00234917
FUJ00234917
DES/GEN/SPE/0010
HNG-X Banking, Debit
Card and ETopUp
Receipts and Texts
Schedule B3.2 Version 15.0
Page 31 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
ANNEX 1
POL SERVICE TYPES
HNG-X
1 I Point of Sale
2 I In/Out Payment (basic services)
3 I In/ Out Payment (Advanced Data Capture)
4 I In/Out Payment (APOP)
5 I Removed by CCN1672a and CCN7125a
6 I Removed by CCN1672a and CCN1725a
Removed by CCN1672a and CCN1725a
8 I Removed by CCN1724a
9 I Electronic Top-Up
10 I Bureau Service
11 I Postal Services
12 I Payment Management (Basic MOPs)
13 I Payment Management (Debit Card)
14 I Payment Management (Credit Card)
15 I Cash and Stock Management
16 I Branch Management
17 I Branch Administration
18 I Branch Support
19 I Transaction Management (Transaction
storage and management)
Schedule B3.2 Annex 1 Version 14.0
Page 32 of 36
CONFIDENTIAL
20 I Removed by CCN1739
21 I File Management
22 I Reference Data
23 I PAF
24 I Message Handling
25 I Audit
26 I Reconciliation (Banking style)
27 I Reconciliation (AP style)
28 I CTO Training
29 I Removed by CCN1725a
30 I Generic Web Services Support Facility
31 I Client File Delivery Support Facility
32 I Post Office Data Gateway Support Facility
33 I Collect and Returns Support Service
34 I Removed by CCN1640a
35 I Smart Metering Capability
36 I Channel Integration Capability
37 I Common Digital Platform Adaptor (CDPA)
Capability
38 I Additional Branch Reporting Business
39 I Banking (Ingenico/Vocalink)
40 I Counter Web Browser
Schedule B3.2 Annex 1 Version 15.0
Page 33 of 36
FUJ00234917
FUJ00234917
FUJ00234917
FUJ00234917
CONFIDENTIAL
Schedule B3.2 Annex 1 Version 15.0
Page 34 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
ANNEX 2
GENERIC WEB SERVICES (GWS)
GWS Client Name I Date Effective I CTorCwo I Date of CWS I CT or CWO
from: introducing the Client removing the
7 Ceased Service
Service into
Live
1 SFA (Skills 43th CT1009 318' May CT1943
Funding Agency) November 2016
2012
2 POLO 10! December CT1218 31% Dec 2019 I CWO148a
2012
3 UK Online 23 May 2013 cT1201a 31% Dec 2019 I CWO148a
4 DVLA Vehicle 16" June 2013 CT1091 11" Oct 2022 I CWO0594
Excise Duty (VED)
and Change of Tax
Class (CTC)
Note: Duplicate
Licence
(DL) element
removed under
CT1585
5 Homephone & 25' July 2013 T1214 31% May 2021 I CWO0365a
Broadband
6 National Express 415% CT1213
Ticketing service September
Web Service 2013
7 The Health Lottery 16 CT1256
September
2013
Schedule B3.2 Annex 2 Version 14.0
Page 35 of 36
FUJ00234917
FUJ00234917
CONFIDENTIAL
8 UKBA (UK Border oath CT1261a 31% Oct 2017 I C2272
Agency) Support November
Payments Web 2013
Service
9 DVLA Direct Debit I 1% October CT1584 11" Oct 2022 I CWO0594
2014
10 Click & Collect I 12% May 2015 CT1398,
CT1346b
"1 FMCV Travel 28" April 2015 cT1429,
Money Card CT1513, CT1943
Schedule B3.2 Annex 2 Version 15.0
Page 36 of 36