POL00134346
POL00134346
From:
Sent:
To:
Ce:
Subject:
Attachment:
Attachment:
Attachment:
Attachment:
Thx Simon
Lesley J Sewel
Thur 16/05/2013 7:35:02 PM (UTC)
Simon Baker!”
Alwen Lyons"
Re: Balancing Issues in 2010
Picture (Device Independent Bitmap) 1.jpg
Picture (Device Independent Bitmap) 2.jpg
Picture (Device Independent Bitmap) 3.jpg
Picture (Device Independent Bitmap) 4.jpg
Gareth references a story board attached. Do you have it as its not attached.
L
Sent from my iPad
On 16 May 2013, at 19:47, "Simon Baker"
Lesley, Alwen
Brief overview of the problem encountered in 2010 below.
The reassuring point, for those looking for comfort, is that in this case Horizon’s monitoring systems
automatically picked up the anomaly.
Simon
From: Jenkins Gareth G
Sent: 16 May 2013 15:52
To: Simon Baker
Cc: Davidson James
Subject: Balancing Issues in 2010
Simon,
Here is a quick briefing on the Balancing issue we had in 2010 in preparation for tomorrow’s meeting with Lesley.
When a clerk balances a stock unit the rollover screen is eventually displayed, and the clerk then presses the
Preview or Print button to produce the Trial Balance Report. The counter then returns to the rollover screen.
Having checked the report, the clerk then presses the Rollover button, and in normal circumstances is given the
choice of rolling to a new Balance Period (BP) or a new Trading Period (TP).
If the clerk chooses to roll to a new TP, and net discrepancies are present, then the system asks whether the clerk
wishes to transfer the net discrepancy to local suspense, or else cancel the rollover (MSG31316).
If the clerk presses Cancel on MSG31316, and on the rollover screen then presses Rollover again, then the Final
POL00134346
POL00134346
Balance report will have a Receipt/Payments mismatch (Total Receipts not equal to Total Payments) which will
ultimately lead to a Non-zero Trading Position on the Branch Trading Statement.
If the clerk does not check the Final Balance report, he/she may not be aware that the report has a
Receipts/Payments mismatch. For a Trial Balance report the counter does warn the clerk if a Receipt/Payments
mismatch occurs, for a Final Balance report it does not. This is as stated in use case BAC-11 Balance Stock Unit.
The counter however does always raise error 0902 in the log file and NT event log.
The key message is the last statement, namely that “The counter however does always raise error 0902 in the log
file and NT event log”. What this means is that an unexpected alert is raised that should be picked up by our
Alert monitoring systems that will ensure that the problem is investigated by our support teams. In other words,
the system is designed to spot a problem like this as it is something that should never happen (other than as a
result of bugs) and if it does happen, then an alert is raised so it can be investigated.
One of the actions that we are taking as a result of the Local Suspense problem we found this year is to put in
some further checks for “situations that should never happen” that related to that problem and to raise an alert
if they do.
I attach a document I produced for Post Office Ltd in May 2011 where I put together a storyboard showing the
exact sequence of events for one of the affected branches.
The problem affected around 60 Branches. I understand that FSC communicated with all the affected branches
and compensated them where appropriate.
Regards
Gareth
Gareth Jenkins
Distinguished Engineer
Business Applications Architect
Post Office Account
JITSU
Gareth_Jenkins{
hito:/uk.fulitsu‘com
<Pictur s<Pictur <Pictur <Pictur
le (Device Ie(Device Ie (Device Ie (Device
Independent [Independent IIndependent IIndependent
Bitmap) Bitmap) Bitmap) Bitmap)
1 jpg> 2.jpa> 3.jpe> 4 .jpg>
Fujitsu is proud to partner with Shelter, the housing and homeless charity
Reshaping ICT, Reshaping Business in partnership with FT.com
FS Please consider the environment - do you really need to print this email?
Unless otherwise stated, this email has been sent from Fujitsu Services Limited, from Fujitsu
(FTS) Limited, or from Fujitsu Telecommunications Europe Limited, together "Fujitsu".
This email is only for the use of its intended recipient. Its contents are subject to a duty of
confidence and may be privileged. Fujitsu does not guarantee that this email has not been
POL00134346
POL00134346
intercepted and amended or that it is virus-free.
Fujitsu Services Limited, registered in England No 96056, registered office 22 Baker Street,
London W1U 3BW.
Fujitsu (FTS) Limited, registered in England No 03808613, registered office 22 Baker Street,
London W1U 3BW.
PFU Imaging Solutions Europe Limited, registered in England No 1578652, registered office
Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE.
Fujitsu Telecommunications Europe Limited, registered in England No 2548187, registered office
Solihull Parkway, Birmingham Business Park, Birmingham, B37 7YU.