Ten Ways to Tell a Good Hazard Report From a Poor Bookend

摘要

The 10 ways offered by the authors are based on over 35 years of experience in writing and reviewing hazard analyses. While the individual data elements of a particular hazard report may be driven by program requirements, there are characteristics that are common to all powerful and useful reports. This paper addresses the key components of such reports including identification of proper hazard causes, hazard controls, and verifications. Guidance is also given on the proper type of supporting information and the best use of references. The evolving nature of the analysis and its proper relationship to program phases (design, development, test, and operation) is addressed. The importance of having accurate and timely information is stressed. A basic theme and underlying message of the paper is to express the advantages of having a product that is based on team effort (safety, engineering, manufacturing, and operations). In closing the paper also provides guidance for the use of the information from the reports to be used in engineering and program management risk decision processes.