• Products
    • Our Products
    • Relyence FMEA
    • Relyence FRACAS
    • Relyence Fault Tree
    • Relyence Reliability Prediction
    • Relyence RBD
    • Relyence RCM
    • Relyence Maintainability Prediction
    • Relyence Weibull
    • Relyence ALT
    • Relyence Studio
  • Industries
    • Industries Overview
    • Aerospace
    • Automotive
    • Commercial
    • Consumer Products
    • Defense
    • Healthcare
    • Manufacturing
    • Medical
    • Oil & Gas
    • Telecom
  • Services
    • Our Services
    • Training
    • Implementation
    • Technical Support
    • Resources
  • Blog
  • About Us
    • Our Team
    • Join Us
    • Why Relyence
    • Contact Us
  • Support

Call us today! 724.832.1900

wecare@relyence.com
My Account
RelyenceRelyence
  • Products
    • Our Products
    • Relyence FMEA
    • Relyence FRACAS
    • Relyence Fault Tree
    • Relyence Reliability Prediction
    • Relyence RBD
    • Relyence RCM
    • Relyence Maintainability Prediction
    • Relyence Weibull
    • Relyence ALT
    • Relyence Studio
  • Industries
    • Industries Overview
    • Aerospace
    • Automotive
    • Commercial
    • Consumer Products
    • Defense
    • Healthcare
    • Manufacturing
    • Medical
    • Oil & Gas
    • Telecom
  • Services
    • Our Services
    • Training
    • Implementation
    • Technical Support
    • Resources
  • Blog
  • About Us
    • Our Team
    • Join Us
    • Why Relyence
    • Contact Us
  • Support

A Guide to Using Foundation FMEAs in Relyence FMEA

Home » A Guide to Using Foundation FMEAs in Relyence FMEA
A Guide to Using Foundation FMEAs in Relyence FMEA Graphic

A Guide to Using Foundation FMEAs in Relyence FMEA

March 21, 2022 FMEA, How-to, Reliability

Failure Mode and Effects Analysis, or FMEA, is a well-organized, step-by-step approach to identifying potential failures of a product or process and developing a plan to effectively address those potential failures that represent the highest risk. Since initially being developed by the U.S. Department of Defense in the 1940s, FMEA has been adopted across a broad range of industries as a valuable tool toward establishing and improving an organization’s quality objectives. Now, FMEA is widely-known as one of the most commonly used techniques in reliability engineering.

FMEA is a flexible risk analysis technique and can be tailored in its usage and specifications to a wide range of industries. In some, such as medical and aerospace, FMEAs are often a required part of the design and manufacturing process. In other sectors, while not required, FMEAs are widely accepted and considered essential. In particular, the automotive industry has proven to be a leading driver in the development of FMEA protocols and procedures.

New to FMEA?

In this article we will focus on recent advancements to the FMEA technique that have been largely driven by the automotive industry. In particular, we discuss how FMEA data can be captured and leveraged for future designs by a method known as Foundation FMEA. If you are new to FMEA, see our New to FMEA introductory overview article. In addition, you can watch a video or read our blog post to see an example of the step-by-step FMEA process.

What are Foundation FMEAs?

In recent years, the power that FMEA can provide as a base of knowledge in product design and manufacturing has been recognized. When performed effectively, the data available from the FMEA Worksheet can be invaluable during all product stages – from creating a next-generation design through to in-field implementation. This has led to an increased emphasis on what are called Foundation FMEAs, also known as shell, core, template, or master FMEAs.

Foundation FMEAs are a database to store FMEA information from past analyses. This ensures that lessons learned are retained and carried through to all your ongoing projects. If performed properly, they provide access to your historical data in an easily accessible place so it can be efficiently referenced and retrieved. Depending on the organization’s usage, Foundation FMEAs can be employed as a place to store universal FMEA data that applies to all products – these FMEAs can also be known as baseline, generic, or best-practices FMEAs. Or, they can be tailored to more specialized data – for example, Foundation FMEAs could be created that apply to certain product lines, processes, manufacturing locations, etc. When this more specialized approach is chosen, the resulting failure information database can also be referred to as a family FMEA.

What are the Advantages of Foundation FMEAs?

Foundation FMEAs provide several important benefits towards ensuring your FMEA process is as efficient and effective as possible.

Capture Lessons Learned

A key benefit to the usage of Foundation FMEAs is that they provide a place to store historical data from past designs. The ability to leverage data from previous analyses ensures that lessons learned are captured and carried through to next generation products. This approach sets up your organization for success in the pursuit of continual improvement.

Reuse Stored Knowledge

When new products and processes are being developed, they often begin with pieces from previous designs. This could mean entire subassemblies being reused – for example, the electronic starter assembly in an automobile could be shared between previous and new designs.  Or it could mean that certain risk-related data or process step information is shared – an example of this case could be a shared potential failure mode and associated risk data of the steering assembly when an EV prototype is created based on a gasoline-powered model.

Whether the new design includes identical components to previous products or pieces of shared FMEA information, the data from previous projects is often helpful baseline data also applicable in the new designs. In both of these situations, you can see how a Foundation FMEA can be helpful as a master FMEA database that allows for easy data reuse.

Enhance Worksheet Consistency

By providing a shared database of information related to your products and processes, Foundation FMEAs allow the ability to reference stored data across your analyses. This ensures consistency and accuracy in your analyses as information can be dispersed to all appropriate FMEAs from one common source. As an example, let’s assume that a certain potential Failure Mode exists in multiple products within your organization. By first utilizing a Foundation FMEA to store this particular Failure Mode and all associated risk data, you can then include this information in all appropriate analyses and be sure it is accurate and complete. Plus, if something about the Failure Mode and its associated risk data changes, you can change it once in the Foundation FMEA and update all FMEAs accordingly.

Reduce Analysis Costs

Once built, Foundation FMEAs can significantly cut down on the time it takes to complete your failure mode and effects analyses. They offer a launching point for new analyses and allow elements of your FMEA to be brought in from a database of stored information. From this starting point, differences between the new and existing analyses can be distinguished and you can then focus your analysis on the elements that are new. By decreasing the amount of time that is required to build a base for your FMEA Worksheet, Foundation FMEAs can reduce the time and money required to support your FMEA efforts.

Advantages of Foundation FMEAs Infographic

Why Should I Use Foundation FMEAs?

Similar to FMEA methodology in general, the usage of Foundation FMEAs may be mandated depending on your industry. However, any FMEA practitioner can benefit from building Foundation FMEAs. By providing a place to store historical data for easy reuse, Foundation FMEAs provide a solid base from which to begin during new product or process design. They ensure that all appropriate FMEA risk data is captured and that your FMEAs are not only effective, but also easy to build and maintain, given the efficiency allotted by the use of Foundation FMEAs.

Foundation FMEAs can be useful across a broad range of industries. By ensuring analysis accuracy and efficiency, Foundation FMEAs build on the success of the proven and broadly adopted FMEA technique as an invaluable tool for risk assessment and mitigation. The data that is captured in a Foundation FMEA can be leveraged forward in future designs to ensure that the next generation of products is always improving.

One common example of an industry where Foundation FMEAs are important is in the automotive sector. The goal of automotive manufacturers is to continually improve each new model in a variety of ways – from safety, to fuel efficiency, to the addition of new features. By relying on the database of lessons learned from a Foundation FMEA, these companies are able to build on past success and continually improve year after year.

While Foundation FMEAs quickly gained popularity in the automotive sector, they can be useful across a broad spectrum of organizations. From consumer electronics, to medical devices, to software packages, building on past success to create higher quality products and processes is something common to many industries. That is to say – wherever there is a need to continually improve, Foundation FMEAs can be leveraged as a useful technique towards this goal.

How Do I Get Started Using Foundation FMEAs?

There are various approaches that can be used to begin the process of creating Foundation FMEAs.

  • They can be started as a general base of knowledge before the formal FMEA on a particular product or process.
  • Or, they can be built up piece-by-piece alongside the FMEA for the system or process currently under analysis.
  • Or, they can be created from a finalized FMEA from a completed design or process FMEA.

Once an initial knowledge base has been created, Foundation FMEAs are at their most effective if they are treated as a living document rather than a static database of FMEA information. As design and manufacturing processes are further refined and as additional failure data is uncovered, the Foundation FMEA should be updated with the new information. Adopting this approach ensures both that the analysis process increases in its efficiency and that new products and processes improve in quality with each iteration.

Leverage Foundation FMEAs Graphic

How to Use Foundation FMEAs in Relyence FMEA

In Relyence FMEA, Foundation FMEAs are supported by utilizing our innovative Knowledge BanksTM. In essence, Relyence Knowledge Banks are a compilation of Foundation FMEAs.

In this section, we will step through an example use-case of the creation and reuse capabilities that Knowledge Banks offer. For this example, case, let’s assume we have a completed FMEA for a quadcopter drone product. Now, we are developing our next generation product – an octocopter drone – and want to utilize the Foundation FMEA technique to build on the success of our past design.

Step 1: Create a Foundation FMEA with the Relyence Knowledge Bank

Since this is our first time using a Foundation FMEA, we begin by adding the appropriate FMEA information from our completed quadcopter drone FMEA to the Knowledge Bank. In this case, that means adding two pieces of FMEA data.

  1. In our octocopter drone, we are planning to reuse the GPS from our quadcopter drone. So, from our quadcopter drone FMEA, we begin by adding the GPS subsystem to the Knowledge Bank. To accomplish this, from the Properties pane of the GPS, click Bank > Add to Knowledge Bank from the top toolbar in Relyence FMEA.

Optionally, you can then click Bank > Go to Knowledge Bank to view the GPS subsystem and associated FMEA data in your Knowledge Bank. (Note: You can also access the Knowledge Bank by clicking Knowledge Bank in the sidebar of Relyence FMEA.) This will serve as the master copy of your GPS subsystem with all associated FMEA data included.

  1. Additionally, on the FMEA Worksheet for the top-level Quadcopter Drone item, we have a Function “Provides convenient flying, aerial surveillance and video recording functionality and experience”. This Function and its associated Failure Mode, Effect, Cause, and Recommended Action information will also apply to our new octocopter drone design. So, we add that Function to our Knowledge Bank as well. To accomplish this, select the appropriate Function in the FMEA Worksheet, and click Bank > Add to Knowledge Bank from the toolbar.

Similar to the GPS subsystem, you can then optionally navigate to the Knowledge Bank to see the newly added Function and its associated FMEA data.

https://relyence.com/wp-content/uploads/2022/03/Create-a-Foundation-FMEA-with-the-Relyence-Knowledge-Bank.mp4

For the purposes of this example introduction to Foundation FMEAs, we will assume these two pieces of FMEA data constitute our Foundation FMEA. However, in a real-world use-case, additional FMEA data can and should be added to the Knowledge Bank in a similar way.

Step 2: Use the Foundation FMEA Data for a New Design

Now that we have our Foundation FMEA created and populated with the appropriate FMEA information we need for our new design, we can begin the FMEA for our octocopter drone, taking advantage of Foundation FMEA data.

  1. From our empty Octocopter Drone FMEA, we will begin by adding the GPS subsystem to our new Analysis from the Knowledge Bank. In the Octocopter Drone Analysis, click Edit > Edit Tree above the Analysis Tree hierarchy. Then, click the Search button in the toolbar, type “GPS” into the Search field and click Search. (Note: You can pick either to insert as a Sibling or Child subsystem depending on where the GPS subsystem fits). Select the checkbox next to the GPS subsystem and click Insert.
  2. Next, we will add the “Provides convenient flying, aerial surveillance and video recording functionality and experience” Function to the top-level Octocopter Drone subsystem. To do so, simply click in the Function column of the FMEA Worksheet, then click the Search button in the toolbar. We then use the Search Functions dialog to find the appropriate Function within our Knowledge Bank. We check the checkbox next to our matching Function, then click the Insert button to add the appropriate Function and its associated FMEA data to our Worksheet.
https://relyence.com/wp-content/uploads/2022/03/Use-the-Foundation-FMEA-Data-for-a-New-Design.mp4

With the help of Knowledge Banks, which store our Foundation FMEA data, we have now efficiently initiated our FMEA for the octocopter drone. We can be confident that we have begun with accurate information since it is based on a past known design. Now, we can continue to add additional FMEA details specific to the octocopter in the Analysis as needed. In this way, we have leveraged the power of Foundation FMEAs through the use of Knowledge Banks towards the goal of an efficient and accurate design process.

Bonus! Data Synchronization with Knowledge Banks

One of the most notable advantages of Foundation FMEAs is reusability. When using Relyence FMEA’s Knowledge Banks to support Foundation FMEAs, you get the added bonus of data synchronization.

As new failure information is uncovered or the design or manufacturing processes are changed, the Foundation FMEAs should be updated to reflect this most recent data. Also, all FMEAs using the all FMEAs using baseline data from the Foundation FMEA should be updated with this information as well.

Relyence FMEA Knowledge Banks offer a data Push feature to allow you keep your FMEAs in sync. When you use Relyence FMEA Knowledge Banks as your repository for your Foundation FMEAs, this important capability is available to you for the most efficient management of your FMEA data.

Octocopter Drone Data Synchronization Example

Consider the octocopter drone once again – in particular the GPS subsystem. Recall that the GPS subsystem and it’s FMEA data was found in and remains linked to the Knowledge Bank. In this case, let’s assume that during the prototyping stage, we uncover a new Failure Mode of “Inaccurate position reported” with associated Cause “Multi-path error”. Now we have to make the decision whether or not to include the new Failure Mode in the master copy of the GPS subsystem within the Knowledge Bank or only within the octocopter drone FMEA. In this case, we decide the new failure information applies to all projects containing the GPS subsystem, so we add the new Failure Mode to master copy of the GPS subsystem in the Knowledge Bank.

Now we can use the Relyence Knowledge Bank Push capability to synchronize the new failure information with all appropriate FMEAs where the GPS subsystem is used. For example, recall that the GPS subsystem and its FMEA data was originally added to the Knowledge Bank from the quadcopter drone Analysis. Clicking Push in the toolbar of the Knowledge Bank brings up a list of all the Relyence Analyses that may be impacted by the newly identified failure information. In this case, this will include both the quadcopter drone and octocopter drone projects. From there, you can choose to update all affected Analyses with the new data or you can pick and choose from the list – for example, there may be some completed FMEAs that you do not wish to modify.

https://relyence.com/wp-content/uploads/2022/03/Relyence-Knowledge-Banks-and-Data-Synchronization.mp4

Updating the Knowledge Bank and your Analyses as you proceed through the FMEA process allows your ongoing projects to be kept in sync with the latest information. You can also be sure that future designs use the most accurate data. When used in this way, Knowledge Banks allow you to continually build on your past successes, thus ensuring that you take full advantage of the data captured in your Foundation FMEAs.

Conclusion

Relyence FMEA was designed to ensure the FMEA process is as easy and effective as possible. The unique and innovative Relyence Knowledge Bank is a key part of achieving that objective. Importantly, the Relyence FMEA Knowledge Bank features enables you to support the use of Foundation FMEAs. If Foundation FMEAs are required for your organization, using Relyence FMEA and Knowledge Banks can meet your compliance requirements. Or, if you are like many organizations and recognize the vast benefits of incorporating Foundation FMEAs as part of your FMEA process, Relyence FMEA easily supports your efforts. As we have seen, using Knowledge Banks as your source for Foundation FMEAs ensures that lessons learned from past analyses are captured and preserved for ongoing and future analyses.

Relyence FMEA is a powerful platform that fully supports your failure mode and effects analysis tasks. It includes a broad array of features and functions that make it the best-in-class FMEA solution. To explore more, check out our FMEA product information as well as our informative FMEA articles.

Contact Us Graphic

Check us out today to see why Relyence FMEA has become the go-to platform for Failure Mode and Effects Analyses! If you are interested in learning more about Relyence FMEA sign up today for your own no-hassle free trial. Or, feel free to contact us to discuss your needs or schedule a personal demo.

Tags: Control PlanCPDFMEAfmeaFMECAFoundation FMEAKnowledge BankMIL-STD-1629PFMEAsyncsynchronize
Share

You also might be interested in

Relyence Reliability Prediction Dashboard

Welcome to Relyence 2018 Release 2!

Apr 16, 2018

We are proud to introduce our most recent Relyence release[...]

FMEA word in Red with Gears in background

Using FMEA Software as a Guided Approach to Performing Failure Analysis

Jan 18, 2021

Introduction FMEA, or Failure Mode and Effects Analysis, is a[...]

New to RCM featured Image

New to RCM?

Jul 1, 2016

Reliability Centered Maintenance, or RCM, is an organized maintenance planning[...]

Recent Posts

  • Welcome to Relyence 2025 Release 1!
  • Q&A with Our Team: How to Use and Organize Relyence Knowledge Banks
  • The Essentials of Relyence Knowledge Banks
  • An In-Depth Review of Fault Tree Analysis Calculation Methods
  • Welcome to Relyence 2024 Release 2!

Archives

  • March 2025
  • February 2025
  • January 2025
  • November 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • May 2022
  • March 2022
  • February 2022
  • January 2022
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • February 2021
  • January 2021
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • December 2019
  • November 2019
  • October 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • January 2019
  • November 2018
  • October 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • April 2017
  • March 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016

Categories

  • 217Plus
  • ALT
  • ANSI/VITA 51.1
  • CAPA
  • China's GJB/z 299
  • Dashboard
  • Fault Tree
  • FMEA
  • FRACAS
  • Fundamentals
  • General
  • How-to
  • IEC 61709
  • Knowledge Bank
  • Life Data Analysis
  • Maintainability Prediction
  • MIL-HDBK-217
  • MTBF
  • News
  • NPRD/EPRD
  • NSWC Mechanical
  • Quality
  • RBD
  • RCM
  • Reliability
  • Reliability Block Diagram
  • Reliability Centered Maintenance
  • Reliability Growth
  • Reliability Prediction
  • Reliability Studio
  • RGA
  • Telcordia
  • Weibull

Tag Cloud

8D AIAG AIAG & VDA always-in-sync AP Availability China's GJB/z 299 Control Plan COPQ CP dashboard DFMEA EPRD failure mode fault tree fmea FMECA Foundation FMEA fracas FTA GJB/z 299 Intelligent Part Mapping ISO-9001 Knowledge Bank MIL-HDBK-217 MIL-STD-1629 MTBF MTTF MTTR NPRD PFMEA process flow Process Flow Diagram QMS RBD Redundancy Reliability Reliability Block Diagram reliability prediction RPN standby Telcordia Weibull What-If? Workflow

Find us on

Start your free trial today! Try for Free!
Relyence Corporation logo

At Relyence, we have a passion for always improving. We believe in always creating, always innovating, and always being the best. We believe that in the software world, and in the technology space, we must always be moving ahead. We need to keep pace with all the new technological innovations, as well as new methodologies in industries. We continually work on product development, new capabilities, feature enhancement, and ever improving our tools.

AIAG Member Logo

FIND US HERE

  • Relyence Corporation
  • 540 Pellis Road, Greensburg, PA 15601
  • 724.832.1900
  • wecare@relyence.com
  • https://relyence.com

Privacy Policy

Terms of Service

Sitemap

FRESH FROM OUR BLOG

  • Welcome to Relyence 2025 Release 1!
  • Q&A with Our Team: How to Use and Organize Relyence Knowledge Banks
  • The Essentials of Relyence Knowledge Banks

© 2025 Relyence Corporation All Rights Reserved. Relyence® is a registered trademark of Relyence Corporation.

  • Try for Free!
Prev Next
Relyence
Manage Consent

To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent may adversely affect certain features and functions.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}
Relyence
Manage Consent

To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent may adversely affect certain features and functions.

Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}