Machine Safety: What are fault exclusions?

Where did the term “fault exclusions” derive? Can you simply choose any fault to exclude? Who would ever exclude a fault while trying to provide employees with appropriate safe machine guarding?

03/08/2013


Has anyone heard about “fault exclusions”? Where did this term emerge from? Can you simply choose any fault to exclude? Who in their right mind would exclude a fault while trying to provide employees with appropriate safe machine guarding?

 

Okay, now that I have your attention, let’s try to provide some background and understanding for this term.

 

Does a definition exist? I’ve examined several ANSI, NFPA, IEC and ISO standards. I found several uses of the term “fault exclusion” in IEC 62061, ISO 13849-1 and ISO 13849-2, however, I could not find the term in the definitions section of these standards. Additionally, I could not find the term used in NFPA 79, RIA 15.06, ANSI/PMMI B155.1 or any of the current ANSI B11 standards except one – ANSI B11.TR6 – 2010, Safety Control Systems for Machine Tools. Here’s the definition:

3.22 fault exclusion: The elimination from consideration of a specific identified failure within the Safety-Related Parts of the Control System because its probability is low relative to the systems‘ required performance, through design, selection of components, or implementation of additional measures.

 

Furthermore, in Clause 4 of the General Design Considerations section you’ll find the following additional clarifications for use:

4.6.2 Fault Exclusion

During the analysis, certain faults may be uncovered that cannot be detected during operation without undue economic costs. Further, the probability that these faults might occur may be extremely small, by using mitigating design, construction and installation. Under these conditions, the faults may be excluded from further consideration. This includes recommended maintenance procedures.

Fault exclusion can be based on but not limited to:

·  the low probability of occurrence of some faults;

·  tried and true (good) engineering safety practices;

·  application specific technical requirements for the specific hazard.

Detail justification shall be given in the technical documentation for any excluded faults.

 

ANSI B11.TR6 is a technical report and not a standard with normative requirements that “shall” be followed. ANSI standards are frequently referenced by OSHA via the General Duty Clause and therefore become law via enforcement by OSHA. As a technical report TR6 provides “guidance in understanding and implementing.”

 

Why doesn’t this term appear in any of our domestic normative standards? Since it’s used in several international standards why hasn’t it been defined and clarified? Can anyone help the rest of us with the background for “fault exclusion”? Will there be a trend for this term rolled into everyday life for safety professionals, end users and manufacturers?

 

J.B. Titus, CFSE

Have you encountered any of these issues? Add your comments or thoughts to the discussion by submitting your ideas, experiences, and challenges in the comments section below.

 

Related articles:

Inside Machines: Does adopting ISO 13849-1:2006 change the U.S. model for compliance and enforcement?

Machine Safety – does OSHA reference consensus standards for compliance?

Machine Safety: Is OSHA okay with my 'acceptable' risk mitigation?

Contact: http://www.jbtitus.com for “Solutions for Machine Safety”.



No comments
The Engineers' Choice Awards highlight some of the best new control, instrumentation and automation products as chosen by...
Each year, a panel of Control Engineering editors and industry expert judges select the System Integrator of the Year Award winners.
Control Engineering Leaders Under 40 identifies and gives recognition to young engineers who...
Learn more about methods used to ensure that the integration between the safety system and the process control...
Adding industrial toughness and reliability to Ethernet eGuide
Technological advances like multiple-in-multiple-out (MIMO) transmitting and receiving
Virtualization advice: 4 ways splitting servers can help manufacturing; Efficient motion controls; Fill the brain drain; Learn from the HART Plant of the Year
Two sides to process safety: Combining human and technical factors in your program; Preparing HMI graphics for migrations; Mechatronics and safety; Engineers' Choice Awards
Detecting security breaches: Forensic invenstigations depend on knowing your networks inside and out; Wireless workers; Opening robotic control; Product exclusive: Robust encoders
The Ask Control Engineering blog covers all aspects of automation, including motors, drives, sensors, motion control, machine control, and embedded systems.
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
News and comments from Control Engineering process industries editor, Peter Welander.
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.
This is a blog from the trenches – written by engineers who are implementing and upgrading control systems every day across every industry.
Anthony Baker is a fictitious aggregation of experts from Callisto Integration, providing manufacturing consulting and systems integration.
Integrator Guide

Integrator Guide

Search the online Automation Integrator Guide
 

Create New Listing

Visit the System Integrators page to view past winners of Control Engineering's System Integrator of the Year Award and learn how to enter the competition. You will also find more information on system integrators and Control System Integrators Association.

Case Study Database

Case Study Database

Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.

These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.

Click here to visit the Case Study Database and upload your case study.