POL00363893
POL00363893
From: Jonathan Gribben'
Sent: Tue 29/01/2019 4:39:24 PM (UTC)
To: Lucy Bremner!
ParkerSP¢_
Ce: Matthew.Lenton
Subject: RE: SP Second Witness Statement: Possible examples to use - effective software fixes
[WBDUK-AC.FID27032497]
Attachment: _DOC_153983890(1)_Second Witness Statement of Stephen Paul Parker 29 Jan 19 v2.DOCX
Steve,
While we are waiting for Gareth to confirm that point, please would you review the attached version of your
statement. If you are happy with it, please would you complete the statement of truth on the final page and return it to
me.
Kind regards
Jonny
Jonathan Gribben
Managing Associate
Womble Bond Dickinson (UK) LLP
y)) WOMBLE womblebonddickinson.com
BOND
d DICKINSON v ©
Fro ucy Bremner
Sent: 29 January 2019 16:32
To: ParkerSP;
Cc: Jonathan Gribben; Matthew.L
Andrew Parsons; Gareth Jenkins; _
Subject: Re: SP Second Witness
AC.FID27032497]
ing
i.
oftware fixes [WBDUK-
Steve,
Thank you.
Gareth - can you confirm that this is correct as soon as possible or provide a different explanation if necessary?
King regards
Jonny
Lucy Bremner
Associate
POL00363893
POL00363893
Womble Bond Dickinson (UK) LLP
\\ womblebonddickinson.com
) WOMBLE
‘ BOND
DICKINSON y ©
Sent from my iPhone
On 29 Jan 2019, at 16:25, "ParkerSP!
wrote:
Jonny
lam free but you'll need someone like Gareth to give you a definitive answer, it was his idea after all.
I think the answer is that Giro bank is ALSO an AP transaction (like bill payments). It is the only type of
bank account that is. All other banking deposits go through a totally different path.
Steve
From: Jonathan Gribben!
Sent: Tuesday, January 29, 2019 4:13 PM
To: Parker, Steve!
Cc: Lenton, Matthew:
Subject: RE: SP Second Witness Statement: Possible examples to use - effective software fixes [WBDUK-
AC.FID27032497]
Steve,
Thank you for this. Updated version attached. We are down to one point to bottom out, which is the
GIRO bank theory in para. 35. The bit we are struggling with is that it if it is possible to deposit money in
a Giro bank account, how is it not possible to deposit money in a normal account. Why is a paper slip
necessary for this type of account?
It might be worth having a quick call on this. Are you free?
Kind regards
Jonny
Jonathan Gribben
Managing Associate
Womble Bond Dickinson (UK) LLP
POL00363893
POL00363893
Stay informed: sign up to our e-alerts
womblebonddickinson.com
<image001.png>
<image002.png> <image003.png
From: ParkerSP. GRO. ]
Sent: 29 January 2019 14:47
To: Jonathan Gribben
Cc: Matthew.Lentort”
John.Simpkinsf
Subject: RE: SI
AC.FID27032497]
Dave. Ibbett. Lucy Bremner;
cond Witness Statement: Possible examples to use - effective software fixes [WBDUK-
Latest comments / change marked
Steve
From: Jonathan Gribbeni
Sent: Tuesday, January 2:
To: Parker, Steve!”
Cc: Lenton, Matthew
Subject: RE: SP Second Witness Statement: Possible examples to use - effective software fixes [WBDUK-
AC.FID27032497]
Importance: High
Steve,
Please see attached the updated version of your statement and a comparison showing the changes
made.
Can we discuss the comments at 2:00pm please?
Kind regards
Jonny
Jonathan Gribben
Managing Associate
Womble Bond Dickinson (UK) LLP
Stay informed: sign up to our e-alerts
POL00363893
POL00363893
<image001.png> womblebonddickinson.com
<image002.png> <image003.png
J
Sent: 29 January 2019 10:52
To: Jonathan Gribben
Subject: RE: SP Second Witness Statement: Possible examples to use - effective software fixes [WBDUK-
AC.FID27032497]
Yes, will do
From: Jonathan Gribben‘
bb
“} Simpkins, John
SP Second Witness Statement: Possible examples to use - effective software fixes [WBDUK-
AC.FID27032497]
Steve,
Thank you for this.
I'm working on the statement now — next (and hopefully final version) will be with you within 30 minutes.
We need to get it out today, so please can you review on receipt? I'll send you a comparison so you can
easily see the changes made.
Kind regards
Jonny
Jonathan Gribben
Managing Associate
Womble Bond Dickinson (UK) LLP.
Stay informed: sign up to our e-alerts
womblebonddickinson.com
<image001.png>
<image002.png> <image003.png>
From: ParkerSP:
Sent: 29 January 2019 09:10
To: Jonathan Gribben
Cc: Matthew.Lentonj
John.Simpki Gareth Jenkins
Subject: SP Second Witness Statement: Possibl
GRO
POL00363893
POL00363893
IMPORTANT - This email or attached documents contains legal advice (or relates to litigation or anticipated litigation) and is being
provided in circumstances for which Legal Privilege may be claimed. Do not copy or forward this document without permission.
Jonny, we’ve been looking at some potential examples to use within the witness statement. Suggest
WBD have a look and decide if it is useful to add them as examples?
Effective Software Fixes
Pc0089918: PSteed2847N - reverse a rem, but when this has been reversed it is doubling
up ona balance
+ve: Already mentioned in statement but still shows a quick software error turn round
28/04/03: SSC (Paul Steed) identified error
28/04/03: Paul Steed updated and sent to MSU to handle discrepancy with FAD & POL
30/04/03: Development identify error
01/05/03: Work Package generated: PWY_WP_16353 B3S30R
07/05/03: Tested on LST. Fix released.
09/05/03: I have spoken to the PM to say that the software fix was sent down and became active on 07-
May-2003 and so there should be no recurrences of the original problem.
PC0123699: 28/07/05 ...payments and receipts are mismatched...PM states he was
balancing on node 2 but there was discrepancies..
-ve: Initial SSC response was erroneous, to send back to Helpdesk.
+ve: Fast fix to live for financial issue
+ve: Demonstrates passing to MSU to tie up financial impact with POL
+ve: Example of looking at more than one site, diligence identifying other sites with issue
+ve: Shows how an initial R&P error is seen by PM and support are subsequently able to identify other
events that tie it in to other sites
28/07/05: Incorrectly sent back by SSC ...Balancing problems should be dealt with initially by NBSC...
28/07/05: ...Have spoken with the PM and advised...All that remains now is for us to try and identify the
root cause of the discrepancy which may take a while. As per usual we will forward our findings on to
the MSU who will advise POL accordingly...
29/07/05 With development. Work Package PWY_WP_22602 generated
01/08/05: BI3S80R_WP22602 is now ready for test
02/08/05: Release PinICL PC0123865
08/08/05: This has passed testing in LST and is being returned to RM for live pilot.
09/08/05: sent out to the Pilot 100 successfully
05/09/05: Applied to all live outlets and now in the live Generic Prodlists roll-outs using both S70 and
S80 spares
When the PM went to produce a trail balance a discrepancy was shown but at the bottom the receipts
and payment totals did not match.
The £170 discrepancy was down to an APS txn message that had no product number and no primary or
secondary mappings. There was a critical event raised on 21st Jul on counter 9 which helped to identify
this (Event Id:4 with the text "Error Message: Failed to generate EPOSSCore transaction grammar").
As the txn message was incomplete it was omitted from the rollover 'calculations' and thus caused the
discrepancy reported.
When I checked the tivoli event archives yesterday I found that 216 of these events had been logged in
the past 7 days at different offices/counters
Looks like whenever the event is raised it is either down to a cancelled quantum txn
POL00363893
POL00363893
Have checked out a sample of 40 to 50 sites and they're all at S80 so its probably safe to assume its an
S80 problem.
Unless otherwise stated, this email has been sent from Fujitsu Services Limited (registered in
England No 96056); Fujitsu EMEA PLC (registered in England No 2216100) both with
registered offices at: 22 Baker Street, London W1U 3BW; PFU (EMEA) Limited, (registered in
England No 1578652) and Fujitsu Laboratories of Europe Limited (registered in England No.
4153469) both with registered offices at: Hayes Park Central, Hayes End Road, Hayes,
Middlesex, UB4 8FE.
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
intercepted and amended or that it is virus-free.
Please consider the environment! Do you need to print this email?
y is
5 possible
se notify jonathan af
this communication or a
d and may be
ction software before transmiss
nd you should carry out your o
Any files attached to thi
no liability for any loss or
Womble Bond Dickinson (UK) LLP accepts
+hecks before opening any attachment
n nor endorsed by it.
r number OC317661
© term partner to refer
ed in England and Wales
sis open to inspection. We
ration number is GB
fe Bond Dickinson entity is a separa
son entity. Womble Bond Dicl
details.
ional) Limited
Womble Bond Dickinson (UK) LLP is authorised and regulated by the Solicitors Regulation Authority
Unless otherwise stated, this email has been sent from Fujitsu Services Limited (registered in
England No 96056); Fujitsu EMEA PLC (registered in England No 2216100) both with
registered offices at: 22 Baker Street, London W1U 3BW; PFU (EMEA) Limited, (registered in
England No 1578652) and Fujitsu Laboratories of Europe Limited (registered in England No.
4153469) both with registered offices at: Hayes Park Central, Hayes End Road, Hayes,
Middlesex, UB4 8FE.
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
intercepted and amended or that it is virus-free.
Unless otherwise stated, this email has been sent from Fujitsu Services Limited (registered in
England No 96056); Fujitsu EMEA PLC (registered in England No 2216100) both with
registered offices at: 22 Baker Street, London W1U 3BW; PFU (EMEA) Limited, (registered in
England No 1578652) and Fujitsu Laboratories of Europe Limited (registered in England No.
4153469) both with registered offices at: Hayes Park Central, Hayes End Road, Hayes,
Middlesex, UB4 8FE.
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
intercepted and amended or that it is virus-free.
Unless otherwise stated, this email has been sent from Fujitsu Services Limited (registered in
England No 96056); Fujitsu EMEA PLC (registered in England No 2216100) both with
registered offices at: 22 Baker Street, London W1U 3BW; PFU (EMEA) Limited, (registered in
England No 1578652) and Fujitsu Laboratories of Europe Limited (registered in England No.
4153469) both with registered offices at: Hayes Park Central, Hayes End Road, Hayes,
POL00363893
POL00363893
Middlesex, UB4 8FE.
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
intercepted and amended or that it is virus-free.