FUJ00232857
FUJ00232857
oO POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
Document Title: POST OFFICE ACCOUNT DEFECT MANAGEMENT
REPORTING
Document Reference: SVM/SDM/PRO/4695
CP/CWO Reference: None
Abstract: Description of the procedures used on the Post Office Account to
produce Defect Management Reports.
Document Status: INITIAL DRAFT
Author & Dept: Matthew Hatch
External Distribution: None
Information See section 0.9
Classification:
Approval Authori
Name Role
See Dimensions for record
See Dimensions for record
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
ONLY:
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS Page No: 1 of 7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
0 Document Control
0.1 Table of Contents
0 DOCUMENT CONTROL.
0.1 Table of Contents...
0.2 Document History.
0.3 Review Details.
0.4 Associated Documents (Internal & External,
0.5 Abbreviations.
0.6 Glossary..
0.7 Changes Exp
0.8 Accuracy...
0.9 Information Classification
INTRODUCTION......
Overview of the Live Defect Management Reporting approach.
The Goal.
Backgrount
asa a
wea
2 LIVE DEFECT MANAGEMENT REPORTING.
2.1 Weekly HDR Report Creation Work Instructions.
2.2 Weekly CBIF Submission Extract Work Instructions...
Appendix A — No Fault Found Response Category values.
2.3 Providing updates to POL Questions in the meeting and additional question:
2.4 Sending POL the Weekly HDR Report.
2.5 Saving the reports, minutes and emails to Sharepoin
2.6 LIVE Defect Management Monthly Report Creation..
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS Page No: 2 0f7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Re)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
0.2 Document History
Only integer versions are authorised for development.
Version No. Date Summary of Changes and Reason for Issue Associated Change
CWO, CP, CCN or
PEAK Reference
03/10/2022 Initial draft versions not released for review
NIA
NIA
0.3 Review Details
See POA Reviewers/Approvers Matrix (PGM/DCM/ON/0001) for guidance on completing the lists below. You may
include additional reviewers if necessary, but you should generally not exclude any of the mandatory reviewers
shown in the matrix for the document type you are authoring.
Review Comments by: (date by which comments should be returned)
Review Comments t (author's email) + POA Document Management
If preferred you can delete the following Mandatory and Optional reviewer tables and paste in the appropriate list
copied from POA Reviewers/Approvers Matrix (PGM/DCM/ION/0001)
Mandatory Review
Role Name
Optional Review
Role Name
‘eviewers that returned comments
Issued for Information lease restrict this
Position/Role Name
0.4 Associated Documents (Internal & External)
References should normally refer to the latest approved version in Dimensions; only refer to a
specific version if necessary.
Reference Version Date Title Source
PGM/DCM/TEM/0001 I See note I See note above POA Generic Document Template Dimensions
(DO NOT REMOVE) I above
PGM/DCM/ION/0001 POA Document Reviewers/Approvers I Dimensions
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE Ref. SVM/SDM/PRO/4695
Version: 0.4
UNCONTROLLED WHEN PRINTED OR Date: 03-OCT-2022
STORED OUTSIDE DIMENSIONS Page No: 30f7
FUJ00232857
FUJ00232857
ce) POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
(DO NOT REMOVE) Role Matrix
Alphabetical order
please
SVM/SDM/PRO/4317 I Latest I See Dimensions POL Horizon Defects Review Terms I Dimensions
of Reference
SVM/SDM/PRO/0875 I Latest I See Dimensions Application support Strategy Dimensions
CS/MAN/O11
Abbre'
ion
Alphabetical order please
0.5 Abbreviations
Det
HDR Horizon Defect Review
HDR-FIN Horizon Defect Review - Financial Impact
HDR-EXP Horizon Defect Review - SPM Experience
SPM Sub Post Master
PBS Payment and Banking Service
PROD OUT Production Out Date
SME's System Matter Experts
HTML Hyper Text Markup Language
PNG Portable Network Graphics
JPEG Joint Photographic Experts Group
CBIF Customer Business Impact Forum
POL Post Office LTD
MGT Management
TISNow TRIOLE for ServiceNow
PEAK Peak Incident Management System
0.6 Glossary
Term Definition
Alphabetical order please
0.7 Changes
Expected
ee
0.8 Accuracy
Fujitsu Services endeavours to ensure that the information contained in this document is correct but, while every
effort is made to ensure the accuracy of such information, it accepts no liability for any loss (however caused)
sustained as a result of any error or omission in the same.
© Copyright Fujitsu 2022
FUJITSU CONFIDENTIAL (INTERNAL USE,
ONLY)
UNCONTROLLED WHEN PRINTED OR
STORED OUTSIDE DIMENSIONS
SVM/SDM/PRO/4695
0.1
03-OCT-2022
4o0f7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
0.9 Information Classification
The author has assessed the information in this document for risk of disclosure and has assigned an information
classification of FUJITSU CONFIDENTIAL (INTERNAL USE ONLY).
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
ONLY:
7 Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 5 0f7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
1 Introduction
This document describes the way in which the various internal and external Defect Management reports
are produced for LIVE Defects including branch impacting. It can be used as a procedural document that
can be referred to and updated in line with changes and/or improvements that are made to the Defect
Management reports as they evolve and change owing customer or internal requirements.
1.1 Overview of the Live Defect Management Reporting
approach
1.2 The Goal
e If the Live Incident or Live Defect affects, or could affect, branch operations, we share it with
POL in a weekly HDR Report and at the Horizon Defect Review (HDR) weekly meeting
1.3 Background
« The Defect Management reports are produced for internal and external distribution in order to
demonstrate Fujitsu’s management and communication of the LIVE affecting defects including
those that have a branch impact.
e The LIVE affecting defects reported to POL will have one or more of the following collections
added in order to qualify as a candidate for reporting:
o ##LiveAffectingDefect
o HDR-FIN — Horizon Defect Review — Financial Impact
o HDR-EXP - Horizon Defect Review - SPM Experience
e These Defects could be in various stages whilst reporting on them to POL:
o INVESTIGATING - A Live Defect will start out as a Potential Live Defect until sufficient
investigation has taken place
= [Fujitsu internal unless linked to a bonded Incident]
o SOLUTIONING - If a fault is confirmed then this will progress to be a Confirmed Live
Defect (if it is not a fault then the Potential Live Defect will be closed)
« [Fujitsu internal as a solution still needs to be identified and agreed]
o PROPOSED FOR - Once a solution is identified for a Confirmed Live Defect it will need
to go through the POA processes before the fix is assigned to a sensible Release
= [Fujitsu internal involving developer / feature conflict check. Counter defects are
discussed with POL]
o TARGETED AT - Releases are then managed through to deployment to Live
= [Visible to all parties as the Release work starts]
2 Live Defect Management Reporting
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS Page No: 6 of 7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
2.1 Weekly HDR Report Creation Work Instructions
To create the weekly HDR Report which is shared with POL, follow these steps:
o The criteria to be used to determine HDR reporting candidates to share with POL will be
determined by creating a list using the following logic. The resulting list allows for the HDR
candidates to be identified.
o Prepare the report to send to POL
e A spreadsheet format has been used to date so the previous week’s POL “HDR Defects
update report — dd.mm.ccyy v1.0.xlsx” submission should be used as the basis for the
new report — removing all previous week highlighting and deleting rows scored out as
POL have been told these are being removed.
= Save the file as v0.1 initially and use v1.0 for the version that is shared with
POL. As a visual reminder add WIP into cell B2
= It may be easier to create several draft versions i.e. v0.1, v0.2, v0.3 etc during
the creation of the report, so that it is in a state suitable to create v1.0 to share
with POL.
= Amend the date in F3 making sure to leave it as a text field or the title of the
section below it will not render correctly
o Create the Peak extract to build the report from
e Then, open any version of the “Peak_Defect_Management extract dd.mm.ccyy
hh.mm.xisx” spreadsheet and Enable Content and go to the Data tab
“##LiveAffectingDefect" and click Refresh All. The password to run the embedded
queries needs entering 3 times and is! Save the resulting file with the
timestamp to match when the extract was created — so it can be referred back to. Turn
off AutoSave
© Quick filtering method:
* Go to the “HDR Report Pivot” tab
e Right mouse click on any part of the filter values at the top and choose “Refresh”
PROD OUT Planned Date (MUIcaiibn
Response Category (Mur
vn +N AB %D
Status Mi
[HDR classification Myltininttnmel lent tnt an exp
Deferred yall [2 Copy
Eesrule (All Format Cells.
am
Count of Summary [B Refresh
59 More 5
Remove "HDR Classification’
Field Settings
PivotTable Options
GD) Hie Fei ist
eCheck that all the filters are accurate and match the description shown:
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE per. SVM/SDM/PRO/4695
ONLY)
7 Version: 0.1
UNCONTROLLED WHEN PRINTED OR Date’ 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 7 of7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
REFRESH auLiveAtfectingDefect TAB THEN REFRESH THIS PIVOT AND CHECK THE FILTERS AS SHOWN,
PROD OUT Planned Date (Multiple items) I Check PROD OUT Planned Date only ticks the blanks and future dates
Response Category (Multiple Items) -T Check the NFF Response Categories are all unticked
status
HOR Classification
Deferred
BS Project
(Multiple tems) untick ¢
(ay ~ Set to Yes or blank
(al) ~ Set to Yes or blank
(Multiple Items) 2 Set to impact and Experience (Error needs looking at, blank is excluded)
‘Double click the number shown to expose the result set for reporting & rename the tab to Deferred/PBS/Other
‘Count of Summary
38
e Ensure that you have set Deferred and PBS Project to (All)
e Pay special attention to the “PROD OUT Planned Date” which may have had new future
dates added that need to be ticked
call Type Defect Identified I7/s
PROD OUT Planned Date (Multiple Items) -Is
Respor Sesrch pu
Status’ _()19/01/2021 ak
HDRCh 03/04/2022 J
Target (03/02/2022 E
BIF Play) 12/02/2022 E
PTFPIg -©423/02/2022 s
BiF_Tic ~ 16/03/2022 E
Action’ “(111/02/2022 5
(4 31/03/2022 c
01/05/2022 <
‘Count «
© Select Multiple tems C
o List - Deferred,
Project and HDR Live Defect Peaks
PROD OUT Planned Date (Multiple Items) -T
Response Category (Multiple Items) -T
Status (Multiple Items) -¥
HDR Classification (Multiple Items) -¥
Deferred (All) *:
PBS Project (All) bd
e If there are any Deferred, Project and HDR Peaks to consider, a number will appear
under the Count of Summary
(Count of Summary
30
Double click on the number to open a new sheet with the relevant Peak(s) listed
and rename it “HDR Report”
It is more likely that the result set largely matches the previous results showing
in the HDR Report. Alternatively, you can create v0.1 using the previous report.
Compare the previous HDR report to the new list and amend accordingly so the
new HDR report list matches what the system now shows
o To do this it is worth hiding the following columns as it makes to easier
to compare the data against the previous HDR Report:
«= B-Summary
= C-Date Opened
= D- Product
= _E-—Product Group
= G-—Priority
= H-Assignment Team
= __I~Status
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
Onty) Version: 0.1
UNCONTROLLED WHEN PRINTED OR _Date: 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 8 of 7
Fe)
FUJITSU
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
FUJ00232857
FUJ00232857
«= J-— Response Category
= K-—Root Cause
= M-—References
= N-TFSNow Reference
= O-POL SNOW Reference
= P—Contact Name
= R-Business Impact
e It is good idea to mark for each Defect PEAK the “Call Reference”, “Description”, “
Release Type” and “Target Release” red on the HDR Report tab of the
“Peak_Defect_Management extract dd.mm.ccyy hh.mm.xisx” once checked against the
report.
‘Target
Fall Referencelhd summary Bd Call typed Collections Workaround Business impact
c0302313
c0302681
pco301437
0301364
0301299
Pco301174
0300404
Pc0300338
c0300066
0299783
0289322
0298894
0298823
PC0298591
0298324
0298067
60297965
0237964
co297963
0297962
0297878
Pco295854
0294925
Pc0293665
0293598
0292825
0232708
0290005
0289922
Pc0289127
DEV - PIN Pa Defect Ident ##LiveAffectin No
SV&i:72.30:€ Defect Ident HDR-Fin, ##Liv Yes
Transaction IDefect Iden’ HOR-Fin, ##Liv Yes
BTS reports «Defect Ident HDR-Fin, ##LivYes
BAL fix - INC Defect Ident .SSC3rd, ##LiveYes
Customer nc Defect Ident HDR-Fin, ##Liv Yes
DEV - Transa Defect Iden’ ##LiveAffectir No
Counter Fix - Defect ident .SSC3rd, ##LiveYes
PBS: INC102: Defect Iden! HDR-Fin, #aLiv Yes
PBS Banking Defect Ident HDR-Fin, ##LivYes
Branch 2508! Defect Ident HDR-Fin, #Liv Yes
PBS Comple: Defect Ident ##LiveAffectin No
PBS: Regres: Defect Ident HDR-Fin, ##Liv Yes
PBS transact Defect Ident HDR-Fin, .SSCFYes
PBS Counter Defect Iden’ SSCRandR, ## No
LST:R71.10- Defect Ident ##LiveAffectin No
ISTR71,10- Defect Iden’ #Liveaffectin No
(ST:R71-10- Defect Iden‘ #Livedffectin No
LST:R71.10 -1Defect Iden’ ##Liveaffectir Yes
(ST:R7L.10- Defect Ident #Liveaffectin No
PBS LST:R71. Defect Ident BIFApproved, No
LST: R70.40 C Defect Ident BIFApproved, No
Obsolete He Defect Iden’ Sattars, SSCCENO
CBB-5606 - L: Defect Iden’ ##Liveaffectin
70.40: ATO Defect Iden’ BIF Approved, No
1NC7179929 : Defect Iden! SSC - 4th Line, No
CBB-5259 - H Defect Ident BIFApproved,
LST:REL_IND Defect Iden‘ BIFApproved, No
LST: R70.20 C Defect Iden’ BIFApproved, Yes
£70,20-SV&l Defect Iden! BIFApproved,
The PIN Pad status Proposed For
During Existing Rev Reported In
Ifa counter perforr Targeted At
After a failed stock Targeted At
Ifa clerk uses the T Targeted At
During this basket \ Proposed For
If Transaction Log s Targeted At
Ifa clerk uses the T Proposed For
Declined transactio Reported In
This issue is the res Targeted At
AP Transaction (AutTargeted At
Ifa PBS Balance En¢ Proposed For
Inrare cases, preve Targeted At
Ifthe user presses Targeted At
On PBS counters wi Targeted At
Business impact: W Proposed For
Business impact: If Proposed For
During Existing Rev Proposed For
There have been niProposed For
Existing Reversals ¢ Proposed For
When a PBS bankin Targeted At
PBSIL does not imp Proposed For
When help pages h Targeted At
In particularly rare ‘Proposed For
For AP-ADC transac Targeted At
See Title. this is be Proposed For
The history text ge! Proposed For
When the Clerk att Proposed For
During a Rem In fo Proposed For
For some back offic Targeted At
HNG-X 73.10
HNG-X Rel. Ind.
HNG-X 72.30
HING-X 72.30
HNG-x 38.08
HING-X 73.10
HNG-x 72.30
HNG-X 73.10
HNG-X Rel. ind.
HNG-X 72.30
HING-X 37.01
HNG-X 73.10
HNG-X 72.20
HING-X 72.20
HING-X 72.20
HING-X 73.10
HNG-X 73.10
HNG-X 73.10
HNG-X 73.10
HNG-X 73.10
HING-X 72.20
HNG-X 73.10
HNG-X 72.20
HNG-X 73.10
HNG-X 72.20
HING-X 73.10
HNG-X 73.10
HING-X 73.10
HNG-x 73.10
HNG-X 72.20
e Any that have been closed should be moved to the HDR Closed Defects section of the
HDR Report and highlight in yellow:
© Copyright Fujitsu 2022
FUJITSU CONFIDENTIAL (INTERNAL USE,
UNCONTROLLED WHEN PRINTED OR
STORED OUTSIDE DIMENSIONS
Ref. SVM/SDM/PRO/4695
Version: 0.1
Date: 03-OCT-2022
Page No:
9of7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING ~
FUJI I SU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
(ote asin lout nt 2H ee cor
a 1 I
Reteresxe POL Tite ‘ategory Heferece: Fj Tie I cosets
}PBSN8L02 Section S67 x State 4 excertions, Banking foe
cman in sos este ramon ep ier
Int entrench I tet I ED swe
te ci re staan es
somalia
Imus primeycctonacrbcontomen I wat I rama [MEINE I wae, I pram tsceamest
pnather transaction is processed [Hn sine IPOL Tale ond reference oded and sbove statement edded to
‘escrito
emi
lec eamettettemocnanacininnn I I Yucstntinmenmecitonesr I seyaqy feta oy
iomanearien fever fe cerennetr nek
Release Date = Screenshots
nya
=
HDR Export PCO302305.htrn! SOS Swe sae
NA
Ce
HOR export PeOs02278.ntmt henebetenic 1 teenie
12/09/2022
e Any that are new should be added to the list and highlighted in red on the HDR Report
tab whilst they are checked and completed
o These then need scrutiny to ensure they look correctly tagged as HDR.
This will require the Peak to be read and checked
co If they are HDR, then the Impact tab needs checking to ensure it is
complete and reads well. Any amendments should be referred to the
SMEs for updates to be added to Peak
o When the report is ready to submit, the highlighting on the new rows
should be changed to yellow
o Extract the list showing:
o POL Reference (from column Bl)
o POL Title (from column BN or set to N/A for a new entry)
o Category (from column BF)
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
IL
> Version: 0.1
UNCONTROLLED WHEN PRINTED OR Date: 03-OCT-2022
STORED OUTSIDE DIMENSIONS Page No: 10 of 7
FUJ00232857
FUJ00232857
oe POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
Fujitsu Reference (the Peak Call Reference from column A)
o Summary (the Peak Summary field from column B)
o Confirmed Defect (set to “Yes” if Call Type in column F is “Defect
Identified” or “No” otherwise)
Workaround (from column Q)
Update (manually updated to pick out any changes made week to week
on the Peak in question — if nothing has changed (as is typical once a
Peak is Targeted At) then the “No change since dd/mm/ccyy” will
probably be ok to leave as is. If any updates are identified, set this cell
to YELLOW FILL
o Target Release Type (from column S)
o Target Release (from column T)
HDR Extract
= Create the file to embed:
= This is created within Peak from the Impact tab
= Open the Peak and go to the Impact tab
= Click on the Export icon on the top right
= A view of the Impact screen is presented in a new window
= Right mouse click and choose “Save as”
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE er. SVM/SDM/PRO/4695
ONLY:
7 Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 11 of 7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
°
Refresh
Print
] Cast media to device
Read aloud
2 Translate to English
Save the file
Embed the file
Click on the cell into which the saved HTML file is to be
added
Click on the Insert menu option at the top
ome Insert Page Lay
Click on Object in the Text section
8 4] Wordan ~
Sr ie [Bf Signature Line ~
Bor & Footer 1] Object
Text
Click on the “Create from File” option on the screen that
appears
I Object 7 x
I create new Create trom File
File name:
Browse.
Ciuink to tite
I C1 Dispiay as icon
I Resutt
I Inserts the contents of the file into your
I document so that you can edit it later
I using the program which created the
source file.
Click on Browse and then navigate to and click on the
relevant file and select “Insert”
Then click OK
© Copyright Fujitsu 2022
FUJITSU CONFIDENTIAL (INTERNAL USE par. SVM/SDM/PRO/4695
ONLY)
7 Version: 0.1
UNCONTROLLED WHEN PRINTED OR Date’ 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 12 of 7
FUJ00232857
FUJ00232857
(ee) POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
= The file will be inserted into the cell in the HDR report
o Screenshots
= If any screenshots have been requested or are needed, first
save the screenshot to a file (PNG or JPEG)
o Embed the file
= Click on the cell into which the saved HTML file is to be
added
= Click on the Insert menu option at the top
ome Insert Page Layc
= Click on Object in the Text section
8 4] Wordart~
[Bi Signature Line ~
Text Header
Box & Footer ©] Object
Text
= Click on the “Create from File” option on the screen that
appears
Object ? x
I create New Create trom Fite
I File name:
I Browse.
i Ditink to tite
C1 Display as icon
Resutt
Inserts the contents of the file into your
I document so that you can ed later
I ting the program which created the
source file.
cance
= Click on Browse and then navigate to and click on the
relevant file and select “Insert”
= Then click OK
= The file will be inserted into the cell in the HDR report
= If itis a PDF document you will need to click on Display as
icon checkbox
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 13 of 7
FUJ00232857
FUJ00232857
oe POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING.
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
Object 2 x
ae te fle moyordeumert
i a
PC0301364.pdf
‘change icon.
ee] areas
Click OK and then resize the PDF document in the cell
Once all details are added please ensure that all the row illustrating the
new Defect is highlighted in yellow.
FYI ONLY — MANUAL FILTERING
o If the HDR Report Pivot is absent or corrupted, then the manual filtering is as follows
o Go to the ##LiveAffectingDefect tab and filter as follows:
e Set the filter on Response Category [column J] to exclude the No Fault Found values
(see Appendix A)
e Seta filter on HDR Classification [column BF] to exclude blanks
¢ Seta filter on Planned Out Live [column AH] so the dates are in the future or blank (it
has not been deployed)
e Exclude closed Peaks where Status [column I] is “C” —- as these may have been fixed
outside of a release by Ingenico themselves
o Then the 1 List needs to be created that can be used to compare against the previous week's
report:
o Deferred Live Defect Peaks
e Set the filter on Deferred [column BH] to “Yes”
e These are unlikely to be discussed at HDR as they are previously approved and
understood but are provided to show the level of Fujitsu control
o Project Live Defects
e Set the filter on PBS Project [column BG] to “Yes”
e These are unlikely to be discussed at HDR as they are part of the ongoing Project
Manager regular review calls
o Non-Project Live Defects (likely originating from an Incident during normal service delivery)
e Change the filter on PBS Project [column BG] to exclude “Yes”
e These require more comprehensive information as these will be discussed at the
HDR meeting
e Extract the list as described above
o These previously were listed as individually in their own sections but is now reported all together.
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 14 of 7
Fe)
FUJITSU
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
2.2 Weekly CBIF Submission Extract Work Instructions
To identify if there are any CBIF submissions necessary to POL, follow these steps:
o Create the Peak extract to build the report from
Open any recent version of the “Peak_Defect_Management extract dd.mm.ccyy
hh.mm.xisx” spreadsheet and Enable Content and go to the Data tab and click Refresh
All on each tab. The password to run the embedded queries needs entering 3 times and
is! ave the resulting file with the timestamp to match when the extract was
created — so it can be referred back to. Turn off AutoSave
o Quick way
Go to the “CBIF Peaks Pivot” tab
Right mouse click on any part of the filter values at the top and choose “Refresh”
Call Type Defect Identified -T/set toD
PROD OUT Planned Date (Multiple items) I set to ft
Response Categor cain «111 A A EY % ¢
Status *
BI ~A-~B-~ Oa
HDR Classification aad °
frarget Release Tyr~ eet waht
Bir Planned Date [1 Copy 4
PTFPlanned Date [5] Format Cele. i
BiF_Ticked_Quest t
‘ActionedTeam [2 Refresh ij
Move >
Count of Summary
Remove "Target Release Type’
BB Fila settings
Pivot Table Options
BD He Fig tt
Check that all the filters are accurate and match the description shown:
REFRESH tiLiveAfectingDefect TAB THEN REFRESH THIS PIVOT AND CHECK THE FILTERS AS SHOWN,
Call Type Defect identified I set to Defect identified
PROD OUT Planned Date (Multiple tems) _ Set to future date or blanks
Response Category _ (Multiple items) T Untick the No Fault Found categories
status (multiple tems) Exclude c
HDRClassification (blank) Set to blanks
‘Target Release Type (Multiple Items) _-¥ Exclude Targeted At
BiF Planned Date (Multiple tems) 57 Exclude blanks
PTF Planned Date (blank) set to blanks
BIF Ticked Questions (Multiple tems) -¥ Exclude blanks
Actioned Team (blank) <¥ set to blanks
Double click the number shown to expose the result set (usually nothing)
‘Count of Summary r 1
Pay special attention to the “PROD OUT Planned Date” which may have had new future
dates added that need to be ticked
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
ONLY:
7 Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 15 of 7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
Call Type Defect Identified -¥/s
PROD OUT Planned Date (Multiple items) 7's
Respor Sear pu
Status 1) 19/01/2021 ale
HOR Chi 44.03/04/2022 s
Target (03/02/2022 ia
BIF Plat (J 12/02/2022 E
PTF Pla ~423/02/2022 s
pir tic 4 16/03/2022 4
‘Actiont -C111702/2022 5
(4 31/03/2022 c
(0105/2022 .
Count «
Select Multiple tems C
e If there are any CBIF Peaks to consider, a number will appear under the Count of
Summary
Count of Summary
1
o Double click on the number to open a new sheet with the relevant Peak(s) listed
o Go to “Collating the results” below
o Manually filtering way
« Go to the ##LiveAffectingDefect tab
« Call Type [column F] is "# - Defect Identified" (a fix is needed)
e Set the filter on Response Category [column J] to exclude the No Fault Found values
(see Appendix A)
e Seta filter on HDR Classification [column BF] to blanks
e _ BIF Planned Date [column U] must not be blank (it has to have been to a BIF meeting)
e Target Release Type [column S] is not Targeted At (as this means it has gone through
PTF already)
e PTF Planed Date [column AA] must be blank (it has not been to PTF)
e Planned Out Live [column AH] date is in the future or blank (it has not been deployed)
e The Actioned Team [column AJ] must be blank (i.e. not BIF (not ready for CBIF) or PTF
(gone past the CBIF step))
¢ BIF_Ticked_Questions [column AM] is not blank (BIF selected it for CBIF)
¢ Go to “Collating the results” below
o Collating the results:
e Check that each Peak(s) in the result set is/are correctly marked by reviewing the Peak
Details and looking at the Release Management (Release MGT) tab for notes that
clarify. Any Peaks that are confirmed as CBIF candidates then need a CBIF Proposal
creating as this is what will be submitted to POL.
e CBIF is part of the HDR meeting and any proposals should be submitted along with the
weekly HDR report for discussion at the weekly HDR meeting with POL.
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 16 of 7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
Appendix A — No Fault Found Response Category values
Peaks with the following Response Categories are deemed to be No Fault Found as no action was
required to remedy the issue raised. In some cases this is because the fault is within an area of the
system that is managed using TfSNow and hence Peak is not the source of the Live Defect information.
Response Category — 68 -- Final -- Administrative Response
Response Category — 95 -- Final -- Advice after Investigation
I Response Category — 94 -- Final -- Advice and guidance given
Response Category — 70 -- Final -- Avoidance Action Supplied
Response Category — 200 -- Final —- Call withdrawn by user
Response Category — 120 -- Final — Cloned to create Defect Peak
I Response Category - 72 -- Final -- Duplicate Call
Response Category — 58 -- Final -- Documentation Fix Available to Call Logger
Response Category — 66 -- Final ~ Enhancement Request
Response Category — 96 -- Final -- Insufficient evidence
“Response Category — 62 -- Final — No fault in product
I Response Category — 63 -- Final -—- Programme Approved — No Fix Required
Response Category — 64 — Final — Published Known Error
“Response Category - 100 — Final — Route call to TTS :
Response Category — 97 -- Final -- Unspecified insufficient evidence
Response Category — 98 -- Final -- User error
2.3 Updating the PIVOT Tab of the Weekly Defect Update
Report
The Pivot tab of the Weekly Defect Update report provides a table and graph that illustrates 1)
The Proposed For 2) Targeted At 3) TBC for the Defects displayed in the HDR Report - Open
Defects by Target Release and HDR collection i.e. Impact and Experience.
If no new defects are added to the report, then the table and graph can be refreshed to pick up
any changes by following the below steps:
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 17 of 7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
Fe)
FUJITSU
«On the Pivot tab, select a cell within the table and then right click, to bring up the menu
fle Hone et Pagano Fomt Oata Rew ew ey Potie eae Dag
ome
om ns <eete ( BR Blew 0 .
a Pee ee a
+ Defects Targeted At releases with BLANK release dates means that there is no agreed Go Live date so the fixes have no confirmed date for resolution
2
4 Gootsthinn yy =
5 Rowtabee
GaSe T we = sonnei
Gage
e If new defects have been added to the HDR Report — Open Defects then select the
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE er. SVM/SDM/PRO/4695
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 18 of 7
FUJ00232857
FUJ00232857
o POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING “
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
PivotTable Analysis menu bar
Defects Targeted At releases with BLANK release dates means that there is no agreed Go Live date so the fixes have no confirmed date for resolution
oom rm
= 2 ws
2 enndtod ae
rs
Defects Targeted At releases with BLANK release dates means that there is no agreed Go Live date so the fixes have no confirmed date for resolution
-_ ae
7ST nO a Re BOE AS
= i
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE er. SVM/SDM/PRO/4695
ONLY:
7 Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 19 of 7
FUJ00232857
FUJ00232857
oe POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
«The Change PivotTable Data Source menu will be displayed
OR Report open Detects HOR aD
Change the Table/Range to cover all the active rows and then click ok
e This will then return you to the Pivot Tab
A See ie ea ee ee a
+ Defects Targeted At releases with BLANK release dates means that there is no agreed Go Live date so the fixes have no confirmed date for resolution
s Ct
=i) 22 tema eon a St = ia
2 emda er)
Fa
»
7 eeet_HD pat TDaR ORG NCoER ONSET CLT
ic
e Again it is worth refreshing the table.
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE er. SVM/SDM/PRO/4695
ONLY:
7 Version: 0.1
UNCONTROLLED WHEN PRINTED OR _Date: 03-OCT-2022
STORED OUTSIDE DIMENSIONS Page No: 20 of 7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
2.4 Providing updates to POL Questions in the meeting and
additional questions
As a result of the weekly HDR meeting there maybe questions raised by POL that you will need
to read the Defect PEAK or engage the required technical resource to gain the required updates
to add to the Impact Tab so a revised HDR Extract can be provided in the next HDR Report.
Additionally, POL may send questions on HDR Defect PEAKS in order to gain clarification, that
will again need to be added to the Impact Tab so a revised HDR Extract can be added to the
HDR Report.
These actions can be performed outside of the producing of the weekly HDR Update Report in
order to be ready to add the report against the appropriate HDR Defect PEAK in the report.
2.5 Sending POL the Weekly HDR Report
e Once all the required changes have been added to the HDR Report, you are know in a position
to create v1.0 to send to POL by approximately 10:00 on a Friday morning, in preparation for the
HDR meeting with POL on a Monday morning (Usually 11:45). If you send it a little late owing to
awaiting an update from a technical resource, that is not a big issue as long as it is sent to POL
by close of play on the Friday.
o Open the latest draft version of the report i.e. HDR Defects Update Report v0.2
o Ensure that all the required updates, HDR Extracts and Screenshots have been added to
the report. This includes checking against the actions from the minutes of the previous
meeting sent by POL in order to ensure that the required information to answer POL
questions is included in the HDR Extracts for the appropriate HDR Defect PEAKS. This
will assist in confirming the status of the Fujitsu actions from the previous meeting.
co If so, remove the word “WIP” into cell B2 and save the report as “HDR Defects update
report — dd.mm.ccyy v1.0.xIsx”
o Next prepare the email to be sent to POL that the report needs to be attached to. Please
see example of the weekly email for the HDR Update Report below:
From: Hatch, Matthew
Sent: Friday, September 30, 2022 10:12 AM
To: Paul I Smith 7
Nn:
Subject: HDR Defects Update Report - 30.09.2022 - v1.0
Good Morning Paul and Lisa,
There are NO CBIF candidates to put forward this week and NO NEW DEFECTS to
raise.
There is also FOUR updates to the existing entries, that have been highlighted in yellow
in the update column.
Changes to report and updates:
e The pivot has been updated
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE per.
Version:
UNCONTROLLED WHEN PRINTED OR _ Date
STORED OUTSIDE DIMENSIONS Page No:
SVM/SDM/PRO/4695
0.1
03-OCT-2022
21 of 7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
e The four updates are:
co 1 has had the Target Release updated.
o 1 has Status Update amended to reflect POL questions
o 1has RCA updated etc amended to reflect POL questions
= Already provided revised HDR to POL on Monday 26" of
September.
oc 1has the latest problem update.
e The one closed defect from last week:
o PC0302653 - Invalid session receipts printed before session settlement
& user confused as to how to settle it
= The HDR extract has been updated to reflect POL accepting
that this is not a defect and is working as per design, as result of
meeting held on Wednesday 28" of September.
There are NO OPEN ACTIONS for Fujitsu — as I have engaged technical resources and
updated the HDR Extracts for the below:
* PC0302313 DEV - PIN Pad Record Not Updated To Show When
Responsive/Non-responsive during logon or unlock
« PC0302653 Invalid session receipts printed before session settlement &
user confused as to how to settle it - (closed)
co Meeting held on Wednesday 28" of September as highlighted above.
I approve the minutes from the HDR Meeting on Monday 26/09 from a Fujitsu
perspective.
o Then add the report version 1.0 “HDR Defects update report — dd.mm.ccyy v1.0.xIsx” to the
email and send to
2.6 Saving the reports, minutes and emails to Sharepoint
In order to have an audit record of the HDR Defect Update reports, emails sent to POL and emails and
minutes of the meetings sent by POL to Fujitsu, there is a sharepoint location whereby all of these
emails and documents are held. Following the sending of the weekly report to POL, or responding to
POL emails with questions or the receiving of meeting minutes from POL please save them to the below
sharepoint location:
Service Management - Horizon Defects Review (HDR) - started June 2021 - All Documents
‘sharepoint.com.
2.7 LIVE Defect Management Monthly Report Creation
To create the monthly Live Defect Management for POA stack owners and leadership, follow these
steps:
o Create the Peak extract to build the report from
e Then, open any version of the “Peak_Defect_Management extract dd.mm.ccyy
hh.mm.xisx” spreadsheet and Enable Content and go to the Data tab and click Refresh
fab. The password to run the embedded queries needs entering 3 times and
ave the resulting file with the timestamp to match when the extract was
created — so it can be referred back to. Turn off AutoSave
o Prepare the report
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
ONLY:
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS Page No: 22 of 7
FUJ00232857
FUJ00232857
POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
Fe)
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
e« Aspreadsheet format has been used to date so the previous month's
“POA_Live_Defect_Management Monthly Report dd.mm.ccyy hh.mm.xisx” should be
used as the basis for the new report. To show history, copy the white box on the top left
of the Summary tab and paste it to the right as an image (you may need to delete a
previous image)
«Save the file with the same date and time values as the Peak extract created earlier so
you know which extract the report relates to
o Go to the ##LiveAffectingDefect tab and filter as follows
Then the 5 tabs are derived as follows:
Check the range of values in the Call Type column. If there are any that are neither “Live Incident”
nor “Defect Identified” then these need to be looked at to decide whether to treat them as one of
these 2 categories. There shouldn't be any, but if there are, it is most likely to be Vulnerability which
can be treated as Defect Identified. If so, amend the filtering below where ** is shown.
o Still Investigating
¢ Clear ail filters
e Filter the Planned Out Live date so it is in the future or blank (it has not been deployed)
e Filter out the No Fault Found Response Category values (see Appendix F)
e Filter Call Type to “Live Incident” ONLY **
= Consider filter on Status to exclude “C’losed — but beware the closures may be
wrong
e Extract the columns shown on the tab from the filtered list and paste the values into the
report
e Expand/contract the Stack owner column by copying/pasting the formula so all rows are
attributed to a name
o DI-Solutioning
¢ Clear all filters
e Filter the Planned Out Live date so it is in the future or blank (it has not been deployed)
e Filter out the No Fault Found Response Category values (see Appendix F)
e Filter Call Type to “Defect Identified” ONLY **
e Filter “Target Release Type” to exclude “Targeted At” and “Proposed For”
= Consider filter on Status to exclude “Closed — but beware the closures may be
wrong
= Manually add back in any that are “Targeted At’ or “Proposed For’ and Target
Release is “Re-target” if there are any
e Extract the columns shown on the tab from the filtered list and paste the values into the
report
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 23 of 7
FUJ00232857
FUJ00232857
oe POST OFFICE ACCOUNT DEFECT MANAGEMENT REPORTING
FUJITSU FUJITSU CONFIDENTIAL (INTERNAL USE ONLY)
© Copyright Fujitsu 2022 FUJITSU CONFIDENTIAL (INTERNAL USE por. SVM/SDM/PRO/4695
Onty) Version: 0.1
UNCONTROLLED WHEN PRINTED OR _ Date 03-OCT-2022
STORED OUTSIDE DIMENSIONS PageNo: 24 of 7