FMEA software: keep the analysis connected to the control revision

Choose the analysis before choosing the worksheet

The ASQ FMEA overview distinguishes design analysis from process analysis and places scope, functions, potential failures and consequences before prioritisation. Define the product or process, its boundaries, assumptions and responsible team before asking a vendor to demonstrate a scoring screen.

For design FMEA, demonstrate the item or interface, intended function, potential failure and effects in the relevant operating context. For process FMEA, demonstrate the manufacturing or service step, its function, potential failure, effects, causes and existing controls. Shared references can connect the analyses, but copying a design row into a process worksheet does not establish the process analysis.

Four records that should remain distinguishable

Documented FMEA scopes to investigate

Ordered by how closely our sources document this process, not by quality. Sponsored placements are labelled. How lists are ordered

Same rule for every product: tagged “Quality Management”, “Risk Assessment”, “Risk Management”, “CAPA Management” or “Manufacturing Quality”, with a sourced FMEA capability in its record, or one the vendor stated to us, labelled as vendor-stated. 3 qualify.

• AssurX

  Risk links around an FMEA: the researched Risk Management scope connects FMEA with quality events, decisions and tasks. That connection alone does not establish a native DFMEA or PFMEA authoring application. Verify in the demo: create the required analysis in the quoted package, identify which records are authored there and which are linked from elsewhere, and follow a changed control back to the approved analysis version. Source: assurx.com

• Cority

  FMEA among operational assessment methods: the researched scope names FMEA alongside JSA, HAZOP and What-If, with actions, approvals and control verification. A list of supported methods does not establish the particular automotive method or rating implementation you need. Verify in the demo: identify the FMEA template and method version, demonstrate its rating logic, and show who reviews the analysis when control-effectiveness evidence changes. Source: cority.com

• Sphera

  Quality-risk studies with FMEA templates: Advanced Risk Assessment documents FMEA, mitigation actions and effectiveness monitoring. This scope does not establish a complete QMS with controlled documents, supplier quality and product release. Verify in the demo: retain the approved study, record a failed effectiveness check and trace its effect on reassessment. Identify the applications or interfaces needed for control plans and related quality records before treating them as included. Source: sphera.com Source: sphera.com

Record the method, rating basis and version explicitly

AIAG's 2019 handbook introduction describes revised rating tables and an Action Priority methodology replacing RPN within the AIAG & VDA approach. That does not mean every FMEA method has changed in the same way. A numerical RPN and an AP assessment are different outputs; renaming a column or assigning AP from a generic RPN cut-off does not implement that methodology.

The current AIAG catalogue identifies FMEAAV-1 as first edition, second printing. AIAG also maintains a manual errata page. Record the method, edition, applicable corrections and any agreed customer requirements in the buying brief. Ask which version the supplied template implements and who maintains it.

Have the responsible team explain each rating and its evidence under the selected method. Keep original and reassessed ratings tied to the controls and assumptions assessed at that time. A new detection control should not silently change an effect's severity; action completion alone supplies no reassessment rationale. This guide reproduces no proprietary rating table and prescribes no score or acceptance threshold.

Demo case: a completed action with an unresolved control check

Use fictional PFMEA-017 for a carton-labelling process, PROC-017 revision 1. STEP-017 should apply the correct product identifier. FM-017 is a wrong variant label; the stated effect is incorrect product identification at receipt. CAUSE-017 is a potential selection of the previous job's artwork, recorded as an analysis assumption rather than a confirmed incident finding.

The baseline records an approved artwork-selection procedure as a prevention control and an operator label comparison as a detection control. Link their evidence to CONTROL-017 revision 1 and the approved control plan CP-017 revision 1. Save the team review, scope and method reference. No numerical ratings or AP category are supplied by this exercise; the responsible team must establish those under its selected method.

CHANGE-017 proposes a scanner check against the job record. Create PROC-017 revision 2 and CONTROL-017 revision 2 as drafts, with CP-017 revision 2 awaiting review. ACT-017 later records implementation evidence, but VFY-017, the planned effectiveness check, has no result. Show implemented action, unreviewed document revisions and unverified control effectiveness as separate states. Preserve PFMEA-017 revision 1 and its original references.

Introduce a fictional VFY-017 result showing that the wrong variant was accepted during the proposed control check. Record the result as not meeting the exercise's stated criterion, retain the evidence and assign further review. Do not automatically lower occurrence or detection ratings, approve the revised control plan or close the issue because the scanner was installed. Demonstrate the configured release decision and responsible owner separately; this is not an instruction to operate a changed process.

Prepare PFMEA-017 revision 2 as a draft that links the failed verification, pending action and affected process/control-plan versions. Retain any proposed reassessment with its rationale and status; it must remain distinguishable from the earlier approved analysis. Export both versions and show how a later acceptable verification would be reviewed without erasing the failed check.

Trace the failure mode through each revision

Test links when the connected record changes

Ask the vendor to change a process step, control or shared library item after one FMEA has been approved. Show which analyses are affected, who reviews the change and whether the earlier version can still be reproduced. Copying a library entry should preserve its source and assumptions; a later library edit must not silently rewrite every approved project.

Trace a nonconformance or complaint to the relevant failure mode and review. The event may challenge an assumption or reveal a missing failure mode. It does not determine new ratings without analysis. Where CAPA is used for the action, keep its implementation and effectiveness evidence visible from the FMEA.

For a proposed SPC connection, request the exact characteristic, process revision, data source and review responsibility. A hyperlink to a chart or a control-plan export is not proof of automatic synchronisation. Demonstrate both the configured update and the treatment of an unavailable or conflicting connection.

Six demonstrations before choosing FMEA software

Put method support and change control in the quote