Accendo Reliability

Your Reliability Engineering Professional Development Site

  • Home
  • About
    • Contributors
  • Reliability.fm
    • Speaking Of Reliability
    • Rooted in Reliability: The Plant Performance Podcast
    • Quality during Design
    • Critical Talks
    • Dare to Know
    • Maintenance Disrupted
    • Metal Conversations
    • The Leadership Connection
    • Practical Reliability Podcast
    • Reliability Matters
    • Reliability it Matters
    • Maintenance Mavericks Podcast
    • Women in Maintenance
    • Accendo Reliability Webinar Series
    • Asset Reliability @ Work
  • Articles
    • CRE Preparation Notes
    • on Leadership & Career
      • Advanced Engineering Culture
      • Engineering Leadership
      • Managing in the 2000s
      • Product Development and Process Improvement
    • on Maintenance Reliability
      • Aasan Asset 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
      • ReliabilityXperience
      • RCM Blitz®
      • Rob’s Reliability Project
      • The Intelligent Transformer Blog
    • on Product Reliability
      • Accelerated Reliability
      • Achieving the Benefits of Reliability
      • Apex Ridge
      • Metals Engineering and Product Reliability
      • Musings on Reliability and Maintenance Topics
      • Product Validation
      • Reliability Engineering Insights
      • Reliability in Emerging Technology
    • 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
      • Integral Concepts
      • Learning from Failures
      • Progress in Field Reliability?
      • Reliability Engineering Using Python
      • Reliability Reflections
      • Testing 1 2 3
      • The Manufacturing Academy
  • eBooks
    • Reliability Engineering Management DRAFT
  • Resources
    • Accendo Authors
    • FMEA Resources
    • Feed Forward Publications
    • Openings
    • Books
    • Webinars
    • Journals
    • Higher Education
    • Podcasts
  • Courses
    • 14 Ways to Acquire Reliability Engineering Knowledge
    • Reliability Analysis Methods online course
    • Measurement System Assessment
    • SPC-Process Capability Course
    • Design of Experiments
    • Foundations of RCM online course
    • Quality during Design Journey
    • Reliability Engineering Statistics
    • An Introduction to Reliability Engineering
    • An Introduction to Quality Engineering
    • Process Capability Analysis course
    • Root Cause Analysis and the 8D Corrective Action Process course
    • Return on Investment online course
    • CRE Preparation Online Course
    • Quondam Courses
  • Webinars
    • Upcoming Live Events
  • Calendar
    • Call for Papers Listing
    • Upcoming Webinars
    • Webinar Calendar
  • Login
    • Member Home

by Carl Carlson Leave a Comment

Determining the Scope of the FMEA

Determining the Scope of the FMEA

The first step in FMEA preparation

Every journey begins with a statement of the goal or objective. Why would it be any different for FMEA? Yet, some FMEA teams do not clearly identifying the focus of the analysis. This sounds simple, and it is; but, it is very important. This article explains why.

“Begin with the end in mind” – Stephen Covey

Definition of “scope”

The Oxford English dictionary defines “scope” as “the extent of the area or subject matter that something deals with or to which it is relevant.”

Why is it important to determine the scope of an FMEA project?

Determining the scope of the analysis is an extremely important step because clearly defined boundaries establish the issues that are to be considered and the approach that the team will take during the analysis.

The scope needs to define the major elements of the FMEA project, such as the subsystems or components that will be analyzed, interfaces between lower level subsystems or components, interfaces with environment and/or humans, and other elements.

The other reason the scope needs to be well defined is to avoid “scope creep.”

What is “scope creep”?

Many FMEA projects suffer the effects of “scope creep,” in which the project begins without agreed upon boundaries and then expands as the meetings go on. If this happens, the team must go back and redo the early work to take into account the larger scope and the project becomes “endless.”

The FMEA scope typically includes . . .

For System FMEAs, the scope typically includes system-related deficiencies, system safety, system integration, interfaces or interactions between subsystems or with other systems, interactions with the surrounding environment, human interaction, service, and other issues that could cause the overall system not to work as intended.

For Design FMEAs, the scope typically includes design-related deficiencies, with emphasis on improving the design and ensuring product operation is safe and reliable during the useful life of the item. For subsystem Design FMEAs, the scope includes the subsystem itself, as well as the interfaces between adjacent components.

For Process FMEAs, the scope typically includes manufacturing- or assembly-related deficiencies, as identified in manufacturing and assembly operations, shipping, incoming parts, transporting of materials, storage, conveyors, tool maintenance, and labeling.

For each type of FMEA, the exact scope will need to be determined by the FMEA team.

Application Tip 1:

In defining the scope of any FMEA project, it is essential to include the interfaces between adjacent subsystems or components. This is important because empirical data show that at least fifty percent of problems occur at the interfaces between subsystems or components.

Application Tip 2:

One of the most effective techniques to define the scope of an FMEA project is to “make it visible.” Design FMEAs use FMEA block diagrams. Process FMEAs use process flow diagrams. Making the scope visible will be the theme of next month’s FMEA Corner.

Problem:

You are part of a team of engineers that are redesigning an all-terrain bicycle. You’ve been asked to lead the System FMEA. Describe some of the ingredients that you might include within the scope of your System FMEA.

Answer:

The following are possible ingredients of a System FMEA for an all-terrain bicycle. These can be converted into primary functions, and each one should be properly described, including standard of performance. The final scope of the System FMEA needs to be determined by the System FMEA team.

* Overall system-related functions for the bicycle (what the bicycle is intended to do)
* System safety functions (the overall safety of the bicycle and rider)
* Integration of subsystems (how the various subsystems should perform together)
* Interfaces between subsystems (physical connections, material exchange, energy transfer, data exchange)
* Interfaces or interactions with other systems (example might be a GPS system)
* Interactions with the surrounding environment (such as pavement, weather)
* Human interaction (such as rider, mechanic)
* Service (maintenance throughout life of bicycle)
* Single-point failures (where failure of a single component results in complete failure of the entire system)
* Other issues that could cause the overall system not to work as intended

Next Month

Next month’s article will be “Making the Scope Visible.”

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

« DOE Training Danger Signs
Belt Conveyor Tuning »

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

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.

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

  • Terrorism Risk Insurance Act Exclusions: Gray Coverage Areas
  • Why Total Productive Maintenance Is The Answer To Reliability-Centered Culture
  • 17 Powerful Insights on Effective Communication Using FINESSE
  • Surprising Insights from Simple Run Charts
  • Risk is Round

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

This site uses cookies to give you a better experience, analyze site traffic, and gain insight to products or offers that may interest you. By continuing, you consent to the use of cookies. Learn how we use cookies, how they work, and how to set your browser preferences by reading our Cookies Policy.