Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
    • About Us
    • Colophon
    • Survey
  • Reliability.fm
  • Articles
    • CRE Preparation Notes
    • NoMTBF
    • on Leadership & Career
      • Advanced Engineering Culture
      • ASQR&R
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset Management
      • AI & Predictive Maintenance
      • Asset Management in the Mining Industry
      • CMMS and Maintenance Management
      • CMMS and Reliability
      • Conscious Asset
      • EAM & CMMS
      • Everyday RCM
      • History of Maintenance Management
      • Life Cycle Asset Management
      • Maintenance and Reliability
      • Maintenance Management
      • Plant Maintenance
      • Process Plant Reliability Engineering
      • RCM Blitz®
      • ReliabilityXperience
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
      • The People Side of Maintenance
      • The Reliability Mindset
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Field Reliability Data Analysis
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability by Design
      • Reliability Competence
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
      • Reliability Knowledge
    • on Risk & Safety
      • CERM® Risk Insights
      • Equipment Risk and Reliability in Downhole Applications
      • Operational Risk Process Safety
    • on Systems Thinking
      • Communicating with FINESSE
      • The RCA
    • on Tools & Techniques
      • Big Data & Analytics
      • Experimental Design for NPD
      • Innovative Thinking in Reliability and Durability
      • Inside and Beyond HALT
      • Inside FMEA
      • Institute of Quality & Reliability
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • R for Engineering
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Statistical Methods for Failure-Time Data
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Glossary
    • Feed Forward Publications
    • Openings
    • Books
    • Webinar Sources
    • Podcasts
  • Courses
    • Your Courses
    • Live Courses
      • Introduction to Reliability Engineering & Accelerated Testings Course Landing Page
      • Advanced Accelerated Testing Course Landing Page
    • Integral Concepts Courses
      • Reliability Analysis Methods Course Landing Page
      • Applied Reliability Analysis Course Landing Page
      • Statistics, Hypothesis Testing, & Regression Modeling Course Landing Page
      • Measurement System Assessment Course Landing Page
      • SPC & Process Capability Course Landing Page
      • Design of Experiments Course Landing Page
    • The Manufacturing Academy Courses
      • An Introduction to Reliability Engineering
      • Reliability Engineering Statistics
      • An Introduction to Quality Engineering
      • Quality Engineering Statistics
      • FMEA in Practice
      • Process Capability Analysis course
      • Root Cause Analysis and the 8D Corrective Action Process course
      • Return on Investment online course
    • Industrial Metallurgist Courses
    • FMEA courses Powered by The Luminous Group
    • Foundations of RCM online course
    • Reliability Engineering for Heavy Industry
    • How to be an Online Student
    • Quondam Courses
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home
  • Barringer Process Reliability Introduction Course Landing Page
  • Upcoming Live Events
You are here: Home / Articles / Understanding Functions – Part 2

by Carl S. Carlson Leave a Comment

Understanding Functions – Part 2

Understanding Functions – Part 2

Problems and Solutions

Do you consider yourself an FMEA beginner or are you more experienced? Challenge yourself with these problems about FMEA functions, and see how you do. One of the best ways to learn is by pondering application problems and seeing of you can solve them.

If you haven’t yet read last week’s article Understanding FMEA Functions – Part 1, it would be a good idea to read it now, as the questions are based on that article.

Beginner’s Problem

In an FMEA, which of the following is true about a “function”? (Select all that apply)
1. A “function” is what the item is intended to do, and can be listed with or without respect to a standard of performance.
2. A “function” is what the item is intended to do, usually to a given standard of performance.
3. There is always one function for each item in an FMEA.
4. The function description in an FMEA must include the consequence or impact on the end user.

Beginner’s Solution

In an FMEA, which of the following is true about a “function”? (Select all that apply)
1. A “function” is what the item is intended to do, and can be listed with or without respect to any standard of performance. (False. A function description needs to include the standard of performance. It is the function statement including the standard of performance that allows the FMEA team to determine the failure modes.)
2. A “function” is what the item is intended to do, usually to a given standard of performance. (True)
3. There is always one function for each item in an FMEA. (False. There can be many functions for an item.)
4. The function description in an FMEA must include the consequence or impact on the end user. (False. An effect must include the consequence or impact on the end user, not a function.)

Intermediate/Advanced Problem

Scenario: You are preparing to lead a System FMEA on the all-terrain bicycle. The “All-Terrain Bicycle Functional/Technical Specifications” includes the following verbiage:

Front suspension: Should be able to absorb forces up to 1000 N without reaching the end of the travel distance. Should use a 75 mm-travel coil-sprung fork with hydraulic damping for greater adjustability and control. Should withstand g-force acceleration to 3g, above which it is considered abusive usage. The fork shock absorber should have adjustable spring rates and damping. The damper should be oil-filled (not air-compressed).
Color offerings: Grey-black or silver-red with scratch resistant coating.
Frame strength: Should be able to withstand 2x the 95th percentile rider (in terms of weight) on the top part, plus 2000 N of force on points of contact with rear and front wheel, 1500 N on point of contact with handlebars.
Frame weight: Should be less than 25 pounds (maximum).
Frame material: B1457 premium aluminum. No visible corrosion on frame for 8 years.
Frame diameter: Maximum diameter of frame is 2 inches at down tube, top tube 1 inch, seat tube 0.75 inch, rest of tubes up to 0.5 inches.
Frame welding: Tungsten Inert Gas (TIG) welding.
Gears: ABC 9-speed Ease of pedaling: Should be able to move bicycle with 5Nm torque on first gear.
Rims: Double-walled 26-inch alloy rims should be able to withstand 2x the rider’s weight, plus 3g-force deceleration impact on solid surfaces such as rocks. Each rim should weigh no more than 10% of bicycle’s total weight.
Tubes: Should be designed for nominal pressure of 40 psi (2.8 bars), but should be able to withstand temporary increase of 50% in pressure.

Answer the following three questions:

Problem 1: The Front suspension has a requirement: “Should withstand g-force acceleration to 3g, above which it is considered abusive.” Should this requirement be part of the all-terrain System FMEA, and if so, how would it be used?

Problem 2: The Gears have a requirement: “Ease of pedaling—should be able to move bicycle with 5 Nm torque on first gear.” Should this requirement be part of the all-terrain System FMEA, and if so, how would it be used?

Problem 3: What type of requirement seems to be missing from the All-Terrain Bicycle Functional/Technical Specifications”?

Intermediate/Advanced Solution

Scenario: You are preparing to lead a System FMEA on the all-terrain bicycle. The “All-Terrain Bicycle Functional/Technical Specifications” includes the following verbiage:

Front suspension: Should be able to absorb forces up to 1000N without reaching the end of the travel distance. Should use a 75mm-travel coil-sprung fork with hydraulic damping for greater adjustability and control. Should withstand g-force acceleration to 3g, above which it is considered abusive usage. The fork shock absorber should have adjustable spring rates and damping. The damper should be oil-filled (not air-compressed).
Color offerings: Grey-black or silver-red with scratch-resistant coating.
Frame strength: Should be able to withstand 2x the 95th percentile rider (in terms of weight) on the top part, plus 2000 N of force on points of contact with rear and front wheel, 1500 N on point of contact with handlebars.
Frame weight: Should be less than 25 pounds (maximum).
Frame material: B1457 premium aluminum. No visible corrosion on frame for 8 years.
Frame diameter: Maximum diameter of frame is 2 inches at down tube, top tube 1 inch, seat tube 0.75 inch, rest of tubes up to 0.5 inches.
Frame welding: Tungsten Inert Gas (TIG) welding.
Gears: ABC 9-speed Ease of pedaling: Should be able to move bicycle with 5Nm torque on first gear.
Rims: Double-walled 26-inch alloy rims should be able to withstand 2x the rider’s weight, plus 3g-force deceleration impact on solid surfaces such as rocks. Each rim should weigh no more than 10% of bicycle’s total weight.
Tubes: Should be designed for nominal pressure of 40 psi (2.8 bars), but should be able to withstand temporary increase of 50% in pressure.

Answer the following three questions:

Problem 1: The Front suspension has a requirement: “Should withstand g-force acceleration to 3g, above which it is considered abusive.” Should this requirement be part of the all-terrain System FMEA, and if so, how would it be used?

Answer 1: During the ground rules and assumptions portion of FMEA preparation, the team will need to consider whether abuse of the all-terrain bicycle will be within the scope of the analysis. The specification clearly says that g-forces above 3g are considered abusive. The team may wish to ignore any g-forces above 3g. In this case the 3g limit would carry over to the function column of the System FMEA as one of the primary functions, such as “the bicycle must be able to safely and reliably with-stand g-forces up to 3g while riding on all surfaces, environments, and maneuvers, according to the customer usage document ABC.” However, if the FMEA team decides to address g-forces above the 3g limit (abusive) for safety or any other reason, they will need to document this decision (with approvals as needed) and generate the appropriate function verbiage.

Problem 2: The Gears have a requirement: “Ease of pedaling—should be able to move bicycle with 5 Nm torque on first gear.” Should this requirement be part of the all- terrain System FMEA, and if so, how would it be used?

Answer 2: The ease of pedaling requirement should be used in the function column of the System FMEA as one of the primary functions. For example, one of the all- terrain bicycle functions might be “The rider should be able to easily pedal the bicycle forward in first gear applying 5 Nm of torque.”

Problem 3: What type of requirement seems to be missing from the All- Terrain Bicycle Functional/Technical Specifications”?

Answer 3: The requirements in the document cover subsystem usage, subsystem-to-user interface, and subsystem-to-environment interface. Missing are requirements related to subsystem-to-subsystem interfaces. Example might be steering while braking maneuvers to avoid loss of control of bicycle by rider.

Next Article

The next article is an FMEA Q and A. The question from the reader asks how to define system-level functions, and how they are different from subsystem and component functions. Just for fun, see if you can answer the readers question before reading the next article.

[display_form id=415]

Filed Under: Articles, Inside FMEA, on Tools & Techniques

About Carl S. Carlson

Carl S. Carlson is a consultant and instructor in the areas of FMEA, reliability program planning and other reliability engineering disciplines, supporting over one hundred clients from a wide cross-section of industries. He has 35 years of experience in reliability testing, engineering, and management positions, including senior consultant with ReliaSoft Corporation, and senior manager for the Advanced Reliability Group at General Motors.

« Get Your Parts Right: The Storeroom Manager
ANOVA Calculation Example »

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Articles by Carl Carlson
in the Inside FMEA series

[popup type="" link_text="Logo Info" ]

Information about FMEA Icon

Inside FMEA can be visually represented by a large tree, with roots, a solid trunk, branches, and leaves.

- The roots of the tree represent the philosophy and guiding principles for effective FMEAs.
- The solid trunk of the tree represents the fundamentals for all FMEAs.
- The branches represent the various FMEA applications.
- The leaves represent the valuable outcomes of FMEAs.
- This is intended to convey that each of the various FMEA applications have the same fundamentals and philosophical roots.

 

For example, the roots of the tree can represent following philosophy and guiding principles for effective FMEAs, such as:

1. Correct procedure         2. Lessons learned
3. Trained team                 4. Focus on prevention
5. Integrated with DFR    6. Skilled facilitation
7. Management support

The tree trunk represents the fundamentals of FMEA. All types of FMEA share common fundamentals, and these are essential to successful FMEA applications.

The tree branches can include the different types of FMEAs, including:

1. System FMEA         2. Design FMEA
3. Process FMEA        4. DRBFM
5. Hazard Analysis     6. RCM or Maintenance FMEA
7. Software FMEA      8. Other types of FMEA

The leaves of the tree branches represent individual FMEA projects, with a wide variety of FMEA scopes and results. [/popup]

Join Accendo

Receive information and updates about articles and many other resources offered by Accendo Reliability by becoming a member.

It’s free and only takes a minute.

Join Today

Recent Posts

  • Gremlins today
  • The Power of Vision in Leadership and Organizational Success
  • 3 Types of MTBF Stories
  • ALT: An in Depth Description
  • Project Email Economics

© 2025 FMS Reliability · Privacy Policy · Terms of Service · Cookies Policy