Task 1: Read and translate the text in written form

Essential elements that should be part of an incident report 
The person experiencing the problem or the team supporting related operations 
usually creates an incident report with input from others involved in resolving it. 
Incident reports are a vital part of any infrastructure’s health and safety routine, 
and depending on the nature of the incident, an incident report might be concise or 
thorough. 
A brief report is appropriate if the occurrence is minor and has little impact. 
However, if the incident is serious, all information must be recorded while 
preparing a complete major incident report. 
The person experiencing the problem or the team supporting related operations 
usually creates an incident report with input from others involved in resolving it. 
Here are a few key elements to include in your incident report: 
• 
Incident raised: The name of the individual who made the incident 
report/ticket 
• 
Time of acknowledgment: It is critical to capture the correct date and time 
since it aids in measuring the effects of SLA (service level agreement). 
• 
Services are being hampered: Identifying which services are unavailable will 
allow the appropriate team to participate in the troubleshooting process. 
• 
Whether or not the SLA was breached: Breaching the SLA would result in a 
penalty and escalation. 
• 
Description of the incident: Rather than writing excessive information, the
description should be concise and relevant, covering the actual occurrence 
details. 
• 
Business impact: Severe incident causes outages or major breakdown 
leading to business impact. Senior management and stakeholders are 
involved in such incident calls. 
• 
Action taken: After the situation has been resolved and services have 
returned to normal, action taken actions are written, including all stages and 
troubleshooting methods in the KEDB (Known Error Database) database for 
future reference.