Incidents incident report

The initial incident report is very important. This document captures the initiator s firsthand knowledge of what occurred in the moments after the specific event. Example 5-2, Sample Toller Initial Incident Report, is an example of the data that should be documented as soon as possible. Note that it should be modified using the company s management system procedure and incident investigation procedure, which should describe the type of data needed, and level of detail desired. 

The final incident investigation report written by the assigned incident investigation team (which may include members from the client) can be written in a less structured way depending on the extent of the incident. A detailed discussion of how and why to conduct incident investigations can be found in the AIChE publication. Guidelines for Investigating Process Safety Incidents, Second Edition. 

Example 5-2. Sample toller initial incident report... 

If yes, for each incident, attach the incident report or give the following information Description of the incident, chronology of verifiable events, other pertinent facts, root causes and contributing factors, and proposals for corrective action. 

The PM is probably ultimately responsible to make sure that all project activities are completed in accordance with requirements as outlined in the HASP. In some cases the PM may be required to perform at least one on-site safety review during the project. The PM is also responsible for making sure that all incidents are reported promptly and... 

IPRDS prepares nuclear plant data under the auspices of the ANSI/Failure and Incidents Reports Review (FIRR) Data Subcommittee. Data collection teams visit plants to e) n... 

The HAZOP team consisted of a HAZOP leader, scribe, process engineer, senior operator, and afety engineer. Previously, the HAZOP leader collected information on the process design (e.g P lDs, operating procedures, emergency procedures and incident reports) for distribution to each team men The leader sectioned the process and identified process deviations prior to the HAZOP. 

According to the incident report, there was no clear division of responsibilities between the Gas Board and the contractor who was carrying out the repairs. Where, as in this case, a special risk is likely to arise due to the nature of the work performed (and the owner of the premises has special knowledge of it), the owner must retain sufficient control of the operation to ensure that contractors e.mployees are properly protected against the risk [4],... 

Pressure can develop inside drums, and then when the lid is released, it may be forcibly expelled and injure the person releasing it. Most of the incidents reported have occurred in waste drums where chemicals have reacted together. For example, nitric acid has reacted with organic com-... 

The incident report stated that the cause of the accident was human error. Although maintenance procedures were available, they had not been used. The... 

In addition to incident reporting systems, root cause analysis techniques can be used to evaluate the causes of serious incidents where resources are usually available for in-depth investigations. A practical example of root cause investigation methods is provided in Chapter 7. 

Incident reporting systems, designed to identify underlying and direct causes for larger numbers of incidents with relatively minor causes... 

The types of data required for incident reporting and root cause analysis systems are specified. Data Collection practices in the CPI are described, and a detailed specification of the types of information needed for causal analyses is provided. 

The main function of an incident reporting system (IRS) is to identify recurring trends from large numbers of incidents with relatively minor outcomes, or from near misses. One of the important characteristics of an IRS is that the time and resources required to evaluate an incident and incorporate it into the database must be minimized. This means that the designers of an IRS have to carefully evaluate the benefits and costs of requiring more comprehensive information from each incident that is to be reported. A requirement for too much information will bring the system into disrepute, and too little information will mean that the results are too general to be of any real value. 

---