Processing FMEA with PathMaker
Quality management knows about preventive actions. These are proactive actions which anticipate and eliminate the possible causes of a potential problem in order to prevent the occurrence of a nonconformity. A method for anticipating potential problems is the FMEA An FMEA is used to eliminate the sources of failures. The benefits of applying FMEA are significant:
- Improved product/process quality
- Reduced failure costs
- Reduced time consumption for re-work
- Less inspection needs
- Increased customer satisfaction and competitiveness
PathMaker is a software tool to plan, run, and control any kind of management projects. This includes the FMEA (Failure Mode and Effects Analysis). PathMaker contains lots of tools that assist in completing an FMEA:
- Flowcharts are used to display the process being investigated.
- Brainstorm/Affinity can be applied to search for failure modes.
- Analysis of failure causes is displayed by a Cause & Effect Diagram.
- Assess severity, occurrence and detectability by voting in Consensus Builder.
- Meetings with Agenda and Minutes allow to create and discuss FMEAs within a team.
- To assist your FMEA project you can further create links to slide shows (html files) that include your organisationīs guide on creating FMEAs. A general slide show on FMEA is included in the software.
FMEA Failure Mode and Effects Analysis - a Sample Form
In order to present this form here more easily, the headings are replaced by numbers. The content of the columns 1 - 18:
- Items: What is the process step, or product characteristic?
- Failure Modes: How can the process or product fail?
- Occurrence: Likelihood of occurrence of a failure scaled 1 to 10
- Failure Effects: What happens when such a failure occurs?
- Severity: Severity of a failure scaled 1 to 10
- Failure Causes: What could cause a failure?
- Current Controls: How do we prevent failure now?
- Detectability: Likelihood of detection of a failure scaled 1 to 10
- RPN: Risk Priority Number
- Recommended Actions: Outline improvements for items with high RPN
- Responsibility: Who is responsible for actions?
- Actions taken: List those actions taken
- Schedule Date: Planned finish date for actions taken
- Completion Date: Actual finish date for actions take
- Planned Occurrence: Likelihood of occurrence of a failure scaled 1 to 10 after actions taken
- Planned Severity: Severity of a failure scaled 1 to 10 after actions taken
- Planned Detectability: Likelihood of detection of a failure scaled 1 to 10 after actions taken
- Planned RPN: Risk Priority Number after actions taken
Running a FMEA project with PathMaker is just one out of lots of management projects you can do with PathMaker. Further examples include:
PathMaker is available in two versions:
which is a desktop-based software solution. Click on PathMaker to learn more about this solution.
is a web-based solution. Click on ipathmaker to learn more about this solution.
PathMaker is developed by