ABSTRACT

This chapter describes the structure of an “ideal” hazard log, which is one of the most important rail safety assurance documents and, in a way, that also fulfils key EN 50126 standard requirements. The number of hazard logs that a project should have depends on many factors—participating organizations, subsystems, etc. A list of entry fields with example values that make a well-structured hazard log is recommended. Also important is how multiple hazard logs can be linked together across disciplines and across hierarchy levels. A crucial issue that every project faces is the transfer of hazards and risks. How this can be done using a structured approach is also explained. Equally vital is the management of interface hazards—whether internal within a discipline, an organization, or a project or externally with stakeholders. Examples of how hazards statistics can be presented at any given project life cycle stage are shown.