Thursday, 2 May 2013

Using the FMEA PLM 360 App


So as discussed in my last post, I'm gonna do a deep dive into the Apps in the PLM 360 App Store over the coming months to give you an overview of what they are all about.

First up is the FMEA App, the FMEA App or the Failure Mode Effect Analysis is used to record the results for each type for Functional, Design or Process analysis for components, assemblies, and subsystems.

The Wiki View of FMEA
Failure mode and effect analysis (FMEA) was one of the first systematic techniques for failure analysis. It was developed by reliability engineers in the 1950s to study problems that might arise from malfunctions of military systems. An FMEA is often the first step of a system reliability study. It involves reviewing as many components, assemblies, and subsystems as possible to identify failure modes, and their causes and effects. For each component, the failure modes and their resulting effects on the rest of the system are recorded in the App. An FMEA is mainly a qualitative analysis.[1] A few different types of FMEA analysis exist, like Functional, Design and Process FMEA.

Dilbert's view of FMEA!




BUT having used FMEA processes in many of my companies that I've worked for in the past, I can say that it IS effective! and with this PLM 360 App it makes the process a lot easier without you having to 'LIANCE' !

Let's cut to the chase and get on with the good stuff..

Install the App from the PLM 360 App Store, if your stuck have a look at my previous post. And don't forget to assign the right group to the Role brought over with the FMEA App.

Step 1.

Add you date, project, process type, image, customer etc to the FMEA details tab




Step 2.

Next step is to start to add the analysis for each item in your process or BOM, click in the 'FMEA Analysis Results' tab and complete a row for each process or product




Some help guides are below:

SEV - Severity
What is the Severity of the effect? 
– No harm = 1, Lethal = 10

OCC - Occurrence
What is the probability of Occurrence?
– not likely = 1, certainty = 10

DET - Detection
What is the likelihood that the failure will escape Detection before it causes effect?
– Always detected = 1, undetectable = 10


RPN  - Risk Priority Number - (Calculated Automatically)
RPN = Severity x Occurrence x Detection 
 - Ranges from 1 to 1000
 - Higher numbers have greater priority
 - Multiple failure modes exist in a system, which one is the most critical to address?
 - Risk management should consider regulatory issues

Risk Management and results
The main aim is to Reduce the RPN
- Re-design the product or Improve Processes in order to:
- Remove the failure mode, or
- Increase the detectability of the failure mode, or
- Reduce the severity by changing the effect


Step 3 

Manage the FMEA using the workflow and track using the Project Management App.




Design FMEA Benefits

 - Aids in the objective evaluation of design requirements and alternatives.

 - Increases the probability that potential failure modes and their effects on the system / product have been considered.

 - Aids in the planing of design test and development programs.

 - Aids in analyzing field concerns, design changes and in developing advanced designs.

 - Ranks potential failure modes according to their effect on the customer, thus prioritizing improvements and development testing.

 - Provides an open issue format for recommending and tracking risk reducing actions.

 - Can reduce product development timing, production startup problems, reduce costs and enhance product quality, reliability and safe

I hope you get some value from the FMEA PLM 360 App, subscribe to the blog for more in depth analysis of the Autodesk PLM 360 Apps.



Post a Comment