Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
60 views2 pages

Root Cause Analysis Template 1.0

This document is a template for a root cause analysis report detailing an incident, including sections for incident summary, details, contributory causes, root cause, downtime, resolution, and preventative measures. It outlines the necessary information to be filled in regarding the incident, such as date, location, severity, and affected systems. The report aims to identify the root cause of the incident and propose measures to prevent future occurrences.

Uploaded by

malikmdnurani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
60 views2 pages

Root Cause Analysis Template 1.0

This document is a template for a root cause analysis report detailing an incident, including sections for incident summary, details, contributory causes, root cause, downtime, resolution, and preventative measures. It outlines the necessary information to be filled in regarding the incident, such as date, location, severity, and affected systems. The report aims to identify the root cause of the incident and propose measures to prevent future occurrences.

Uploaded by

malikmdnurani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

mark stevens

2/8/22

Root cause analysis report

INCIDENT TITLE: {Give the incident/fault a meaningful title}

INCIDENT SUMMARY
DATE AND TIME OF THE INCIDENT: {e.g., 08th Feb 2022 at 1930 HRS}
REPORT AUTHOR: {e.g., Mark Stevens}
LOCATION: {e.g., site location or device location}
{e.g., IP Network, System Applications, Transmission,
SCOPE:
Servers}
REFERENCE NUMBER/INCIDENT ID: {e.g., Trouble Ticket Number or Incident Id}
{e.g., Customer, Automated Alarm Monitoring Tools, NOC,
WHO PICKED IT UP?
Field Team, Backoffice Team or Remote Support Team}
SEVERITY OF THE INCIDENT/PROBLEM: {e.g., Critical/Emergency, Major, Minor}
RE-OCCURRENCE OF INCIDENT/PROBLEM: {e.g., Is it the repetition of a previous failure? YES/NO}
INCIDENT DETAILS
{e.g., Which system(s) were affected because of the failure
SYSTEM(S)/SERVICE(S) AFFECTED:
(Applications, Services, Infrastructure etc.}

{e.g., Briefly describe the incident, what happened? You can


include the Alarm messages/logs/screenshots/tests
performed, etc.}

DESCRIPTION OF THE INCIDENT/PROBLEM:

{e.g., Temporary Fix, Work Around, Partially Resolved, or


CURRENT STATUS OF THE INCIDENT/PROBLEM:
Fully Resolved?}
EXPECTED FINAL RESOLUTION DATE: {e.g., If not yet fully resolved}
{e.g., Logfiles, Trace files, Test Results etc.}
ANY ASSOCIATED SUPPORT INFORMATION:

{e.g., What were the contributory causes for the failure


CONTRIBUTORY CAUSES:
(People, Processes or Procedures? }
{e.g., What was the root cause of the failure? Server disk
failure, Cable failure, Device failure, hardware failure,
software failure, power failure. Include evidence like logs,
ROOT CAUSE OF INCIDENT/PROBLEM:
messages, screenshots, pictures, alarms}

TOTAL DOWNTIME: {e.g., How long was the customer(s) impacted?}


{e.g., What action(s) were taken to resolve the problem?}
RESOLUTION:

PREVENTATIVE MEASURES
{e.g., What can/has be/been done to prevent future failures?}
PRO-ACTIVENESS:

Root cause analysis report mark stevens


mark stevens
2/8/22

Root cause analysis report

Root cause analysis report mark stevens

You might also like