10.07.2015 Views

MAP-01-011 HFI Technical Guide - Human Factors Integration ...

MAP-01-011 HFI Technical Guide - Human Factors Integration ...

MAP-01-011 HFI Technical Guide - Human Factors Integration ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 17 – Safetyequipment. Exposure to electrical shock, moving equipment, collision withequipment casings and fittings, effects of fire or weapons damage are instanceswhich may need to be anticipated when designing equipment. The second classarises from inadvertent operation or erroneous use of the equipment that maythen threaten personnel on the vessel or elsewhere. Experience with existingequipments indicates that safety risks often arise because of the interaction ofdifferent factors. Poor access for maintenance purposes can lead to accidentsdue to lack of visibility or awkward manipulation of tools or equipment. Lack ofattention to user seating design or the co-location of users with potentiallydangerous equipment can lead to safety risks in the event of platform collisionsor compartment damage. Lack of training can lead to safety risks for usersoperating or maintaining sensors and weapons systems. Poor display designand workstation layout can lead to safety risks to own ship or other platforms.<strong>HFI</strong> <strong>Technical</strong> Issues17.1.13 Safety Regime – Safety CaseThe <strong>HFI</strong> Focus is responsible for ensuring that <strong>HFI</strong> contributes to the overarchinghealth and safety requirements described in JSP 430 [Ref 5] and in BR 2000(20)‘Ship Engineering Practice, Safety Considerations and Precautions’ [Ref 31]. ASafety Regime compliant with JSP 430 and the ‘Project Oriented SafetyManagement System’ (POSMS) [Ref 36], or equivalent ‘Safety ManagementSystem’, is required to be in place for a vessel from its inception to its disposal.JSP 430 further requires that a ‘Safety Case’ is in place through life for allplatforms and associated equipments.The Safety Case documents the evidence demonstrating the safety of the vesselor equipment. A ‘Safety Case Report’ is produced in each Phase of theprocurement and life cycle of a vessel. This is a management tool thatdocuments specific safety risks and hazards and details ownership of actions andmitigation required to reduce the risks of these arising. The Safety Case willinclude a description of the vessel and its equipment, a formal safetyassessment, description of the ‘Safety Management System’ (SMS) andemergency and contingency arrangements. <strong>HFI</strong> is of particular use whengenerating the Formal Safety Assessment and identifying or assessing theEmergency and Contingency Arrangements. This section describes specifictechnical issues and the <strong>HFI</strong> activities that are applicable when generating theSafety Case.Formal Safety Assessment comprises Hazard Analysis, Risk Assessment andRisk Reduction. <strong>HFI</strong> contributes to each of these as follows:1. Hazard Analysis – Hazard Analysis (HAZAN) identifies and quantifies thelikelihood and impact of risks to health and safety. <strong>HFI</strong> contributes a rangeof techniques to this process. Task Analysis, Operability Evaluation,Workload Analysis, Link Analysis, Synthetic User Modelling, Health &Safety Analysis and <strong>Human</strong> Reliability Analysis can all be used for thispurpose.2. Risk Assessment – Risk Assessment assesses the tolerability ofsustaining health and safety incidents on the basis of their likelihood andseverity. <strong>HFI</strong> contributes data and standards on human tolerance to arange of potentially hazardous factors and techniques for qualifying andquantifying the likelihood of error.3. Risk Reduction – Risk Reduction concentrates on measures to remove ormitigate risks to health and safety. <strong>HFI</strong> contributes techniques and data forNov 2006 Page 17-11 Issue 4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!