# FMEA Failure Mode Brainstorm Worksheet > Source: https://netray.co/tools/fmea-failure-mode-brainstorm-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Capture process steps, functions, failure modes, effects and causes in one structured table before you score severity, occurrence and detection. ## Category quality ## Industry Manufacturing ## Audience - Quality engineer - Process engineer - Reliability engineer ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Process step or item **Key:** step **Type:** text #### Function or requirement **Key:** function **Type:** text #### Failure mode **Key:** mode **Type:** text #### Effect of failure **Key:** effect **Type:** text #### Effect level **Key:** level **Type:** select **Options:** - Next operation - Plant - Customer - End user #### Potential cause **Key:** cause **Type:** text #### Source of idea **Key:** source **Type:** select **Options:** - Team - Scrap data - Customer complaint - Past FMEA - Operator #### Discuss first (1 = yes) **Key:** priority **Type:** number **Rows:** #### OP20 Bore **Function:** Bore diameter 25.00 +0.02 **Mode:** Bore oversize **Effect:** Seal leaks at assembly **Level:** Customer **Cause:** Tool wear not offset **Source:** Scrap data **Priority:** 1 #### OP20 Bore **Function:** Bore diameter 25.00 +0.02 **Mode:** Bore undersize **Effect:** Part scrapped at gauge **Level:** Plant **Cause:** Wrong offset after tool change **Source:** Operator **Priority:** 0 #### OP30 Deburr **Function:** No burrs on cross hole **Mode:** Burr left in cross hole **Effect:** Debris in hydraulic circuit **Level:** End user **Cause:** Brush worn out **Source:** Customer complaint **Priority:** 1 #### OP40 Wash **Function:** Cleanliness per spec **Mode:** Chips not removed **Effect:** Rework at final inspection **Level:** Plant **Cause:** Nozzle blocked **Source:** Team **Priority:** 0 #### OP50 Pack **Function:** Parts protected in transit **Mode:** Parts touch in tray **Effect:** Cosmetic damage **Level:** Customer **Cause:** Wrong tray insert **Source:** Past FMEA **Priority:** 0 **Totals:** #### Items to discuss first **Key:** priority **Agg:** sum **Format:** integer **Summary:** #### Failure modes captured **Key:** n_modes **Expr:** count **Format:** integer **Notes:** Do not score here. Use this table to get the failure chain right, then move each line into your PFMEA or DFMEA sheet for rating. ## Content **Intro:** Good scoring depends on a clean failure chain: function, failure mode, effect and cause. This worksheet lets the team brainstorm that chain quickly and edit it freely, before the pressure of rating begins. **Sections:** #### How to use the worksheet **Body:** Work step by step through the process flow. For each step, write the function it must deliver, then ask how it could fail to deliver. For every failure mode, record the effect on the next operation, the plant, the customer or the end user, then list causes. Mark items for early discussion with 1. Export to Excel to paste into your FMEA form. **Bullets:** - One failure mode per row - Write effects as what someone would notice - List causes you can act on, not just operator error - Note the source so the team can trace evidence #### The failure chain **Body:** In the AIAG-VDA structure, a failure mode belongs to a function, has effects that propagate up to the customer, and has causes that sit lower in the process. Keeping that chain consistent matters more than the number of rows. A failure mode that is really a cause, such as worn tool, produces a confused sheet later. #### Where ideas come from **Body:** Use real data before opinion: scrap reports, customer complaints, rework logs and the previous FMEA of a similar part. Ask operators what they fix daily. The source column keeps a record so the team can later check whether ratings match evidence. Pulling this data from your ERP, such as NCR or scrap transactions by operation, makes the first session more productive. #### Common mistakes **Body:** Brainstorming only failures you have already seen leaves the new risks invisible. Writing vague modes such as bad quality cannot be scored. Mixing process and design failures in one table makes ownership unclear. Keep one worksheet per FMEA scope and review it with the process owner before scoring. **Cta:** If scrap and NCR history are locked in your ERP, Netray can extract them by operation to seed this list. Ask for a quick review. **Faq:** #### Is this a replacement for the FMEA form? **Answer:** No. It is a pre-work table for the failure chain. After agreeing the chain, enter each line into your FMEA form and add ratings, controls and actions. #### How many failure modes per step? **Answer:** As many as are credible, but most steps have two to six. If a step has dozens, split it into smaller steps or check whether you are listing causes as modes. #### What is a good effect statement? **Answer:** One that states what is noticed at the level affected, for example seal leaks at customer assembly. Avoid just writing defect or scrap, which hides the real consequence. #### Can I use it for DFMEA? **Answer:** Yes. Use the item column for the component or interface, the function column for the design requirement and keep the same chain of mode, effect and cause. ## Search terms fmea brainstorm worksheet, failure mode brainstorming template, fmea failure mode list excel, fmea structure analysis worksheet, failure mode effect cause table, pfmea pre-work template, fmea function failure analysis --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json