Skip directly to search Skip directly to A to Z list Skip directly to navigation Skip directly to page options Skip directly to site content

Mining Product: Programmable Electronic Mining Systems: Best Practice Recommendations (In Nine Parts): Part 2: 2.1 System Safety

Original creation date: April 2001

Image of publication Programmable Electronic Mining Systems: Best Practice Recommendations (In Nine Parts): Part 2: 2.1 System Safety

This report (System Safety 2.1) is the second in a nine-part series of recommendations addressing the functional safety of processor-controlled mining equipment. It is part of a risk based system safety process encompassing hardware, software, humans, and the operating environment for the equipment's life cycle. The reports in this series address the various life cycle stages of inception, design, approval and certification, commissioning, operation, maintenance, and decommissioning. These recommendations were developed as a joint project between the National Institute for Occupational Safety and Health and the Mine Safety and Health Administration. They are intended for use by mining companies, original equipment manufacturers, and aftermarket suppliers to these mining companies. Users of these reports are expected to consider the set in total during  the design cycle.

  • 1.0 Safety Introduction. - This is an introductory report for the general mining industry. It provides basic system/software safety concepts, discusses the need for mining to address the functional safety of programmable electronics, and includes the benefits of implementing a system/software safety program.
  • 2.1 System Safety and 2.2 Software Safety. - These reports draw heavily from International Electrotechnical Commission (IEC) standard 61508 [IEC 1998a,b,c,d,e,f,g] and other recognized standards. The scope is "surface and underground safety mining systems employing embedded, networked, and non-networked programmable electronics." System safety seeks to design safety into all phases of the entire system. Software is a subsystem; thus, software safety is a part of the system's safety.
  • 3.0 Safety File. - This report contains the documentation that demonstrates the level of safety built into the system and identifies limitations for the system's use and operation. In essence, it is a "proof of safety" that the system and its operation meet the appropriate level of safety for the intended application. It starts from the beginning of the design, is maintained during the full life cycle of the system, and provides administrative support for the safety program of the full system.
  • 4.0 Safety Assessment. - The independent assessment of the Safety File is addressed. It establishes consistent methods to determine the completeness and suitability of safety evidence and justifications. This assessment could be done by an independent third party.
  • 5.0 Safety Framework Guidance. - It is intended to supplement the safety framework reports with guidance that provides users with additional information. The purpose is to help users in applying the concepts presented. In other words, the safety framework is what needs to be done and the guidance is how it can be done. The guidance information reinforces the concepts, describes various methodologies that can be used, and gives examples and references. It also gives information on the benefits and drawbacks of various methodologies. The guidance reports are not intended to promote a single methodology or to be an exhaustive treaty of the subject material. They provide information and references so that the user can more intelligently choose and implement the appropriate methodologies given the user's application and capabilities.

Authors: JJ Sammarco, TJ Fisher

Information Circular - April 2001

NIOSHTIC2 Number: 20001003

U.S. Department of Health and Human Services, Public Health Service, Centers for Disease Control and Prevention, National Institute for Occupational Safety and Health, DHHS (NIOSH) Publication No. 2001-137, Information Circular 9458, 2001 Apr; :1-47