FUJ00161724
FUJ00161724
From: Parker, Steve[/O=FUJITSU EXCHANGE ORGANIZATION/OU=EXCHANGE ADMINISTRATIVE
GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=C05AB06345 1 849CE89F838011C3]
Sent: Tue 29/01/2019 4:25:38 PM (UTC)
To: Jonathan GribbenIj
Ce: Lenton, Matthew(L.
Lucy Bremner
Subject: RE: SP Second Witness Statement: Possible examples to use - effective software fixes
[WBDUK-AC.FID27032497]
Jonny
1am 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 Gribbe:
Sent: Tuesday, January 29, 2019 4:13 PM
To: Parker, Steve
Cc: Lenton, Matthew
>; Ibbett, Dave
; Lucy Bremner
Simpkins, John <_ Andrew Parsons
i. Pp
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.
Stay informed: sign up to our e-alerts
womblebonddickinson.com
FUJ00161724
FUJ00161724
WOMBLE v in)
BON
DICKINSON
From: ParkerS!
Sent: 29 January 2019 14:47
To: Jonathan Gribben
Cc: Matthew.Lenton{ GRO", Dave. Ibbett! GRO
Andrew Parsons
Subject: RE: SP Second Witness Statement: Possible examples to use - effective software fixes [WBDUK-
AC.FID27032497]
Latest comments / change marked
Steve
From: Jonathan Gribben <_
Sent: Tuesday, Janu:
; Lucy Bremner
ndrew Parsons
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.
womblebonddickinson.com
WOMBLE
BON
DICKINSON y ©
FUJ00161724
FUJ00161724
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 <___ GRO >
Sent: Tuesday, January 29, 2019 10:40 AM
To: Parker, Steve <_
Cc: Lenton, Matth
Ibbett, Dave
ucy Bremner
Gareth Jenkins
< }
Subject: RE: 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
DICKINSON y ©
From: ParkerSP! GRO }
Sent: 29 January 2019 09:10
To: Jonathan Gribbe
Cc: Matthew.Lento
Gareth Jenkins <{ i
Subject: SP Second Witness Statement: Possible examples to use - effective software fixes
Dave. Ibbett! Lucy Bremner; John.Simpkins! GRO :
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?
FUJ00161724
FUJ00161724
Effective Software Fixes
PC0089918: PSteed2847N - reverse a rem, but when this has been reversed it is doubling up on a
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 PCO123865
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 $80 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
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
FUJ00161724
FUJ00161724
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?
The information in this
mail and any attachn
di
Privacy Policy on our website
mail and any attachments
If you are not parkerspf
ion, publication or copying of this commun
‘as possibi
notify jonathan, -
or attachments is prohibit
mination, distri be unlawful, Informat
attached to this e-mail will have be
‘age which may be caused by softs
Any fi
y jecked by us with virus detection software before transmission, Womble Bond Dickinson (UK) LLP accepts no liability for any
loss or d
n
{ruses and you should carry out your own virus checks before opening any attachm
Content of this email which does not relate to the official business of Womble Bond Dickinson (UK) LLP, is neither given nor endorsed by it.
This email is sent by Womble Bond Dickinson (UK) LLP which is a limited liabilit
is 4 More London Riverside, London, SE1 2AU, whe
or consultant who is of equivalent standing. Our VAT
sartnership registered in England and Wales under number 0C317661. Our registered office
ion. We use the term partner to refer to a member of the LLP, or an employee
a list of members! names
ration number is GB1
Womble Bond Dickinson (Internat
the world. Each Womble Bond Di
mn entity. Womble Bond Dickin
onomous law firms providing
of independent an
's not responsible for the acts or omissions of, nor
can bind law, Please see
www
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.