POL00165493 - Email chain from IT Solution Atos Incident Management to Joe Milton, Liz Tuddeham, Veronqiue Durand and others RE: GY: I5804252 Notice #2 P1 SERVICE/SYSTEMS PERFROMANCE DEGRADED- Reference data integrity not proven error in Horizon

Evidence on official site

POL00165493
POL00165493

IT-Solutions Atos Incident Managemen
Sent: Thur 10/07/2014 7:58:27 AM (UTC)

Ce: i
Bec:

J; Barry R Evang”
nia Ulgiati;
Mario Michael...

Joy Lennonf.

Subject: GY:15804252 - Notice #2 - P1 - SERVICE/SYSTEMS PERFORMANCE DEGRADED -
Reference Data Integrity Not proven error in Horizon

UPDATE

Incident title: I Reference Data Integrity Not proven error in Horizon

Ticket: I GY:15804252

Incident level: I P1

Critical impact start: I 10-07-2014 07:44 UTC+01 (DST)

Service restoration: I Running

Business impacted: I Post Office Limited - ALL P1/P2 In

cidents, Post Office Limited - POL SAP Incidents

Sites impacted: I Multiple

Current business impact: I Fujitsu have confirmed that currently 658 PO Branches are affected. This number is currently increasing.

Initial business impact: I Business impact being gathered

UPDATE 10-07-2014 08:47 UTC+01 (DST)
Atos Incident Management have agreed to raise this incident to a P1.

Case summary: I cusitsu believe this to be a BT WAN Failure and are currently trying to correlate information in relation to

the PO Branch locations to identify the geographical nature of the incident.

POL00165493
POL00165493

Fujitsu have logged the incident with BT.
Next Update to be sent at 10:00.

INITIAL 10-07-2014 07:42 UTC+01 (DST)
Fujitsu have been engaged to investigate

Action plan:

UPDATE 10-07-2014 08:47 UTC+01 (DST)
Atos Incident Management have agreed to raise this incident to a P1.

Fujitsu believe this to be a BT WAN Failure and are currently trying to correlate information in relation to
the PO Branch locations to identify the geographical nature of the incident.

Fujitsu have logged the incident with BT.
Next Update to be sent at 10:00.

INITIAL 10-07-2014 07:42 UTC+01 (DST)
To be confirmed

System(s) affected:

Horizon

Application(s) / environments
affected:

Horizon

Start of incident:

10-07-2014 07:38 UTC+01 (DST)

Comet v3.1.40221.1116, 21-02-2014 10:35 UTC,