A DFMEA that keeps up with the design.
Most DFMEAs are accurate on the day they're approved and drift from there. Every engineering change, whether a new material, a revised tolerance or a different supplier, can move a risk that the document still scores the old way.
The DFMEA is a snapshot. The design isn't.
Updating the DFMEA after a change depends on someone remembering to do it, and knowing which rows the change touches. On a busy program that's hard enough. After launch it's harder still: a VA/VE change two years post-launch, when the original team has moved on, rarely makes it back to the DFMEA at all. That's where the DFMEA quietly goes stale, and the DVP&R goes stale with it.
Every change checked against the risk it can move.
It watches for engineering changes
From your change process or your PLM system.
It works out which rows a change can actually affect
And sets aside the ones it can't, so your engineer isn't asked to re-review the whole document for a change that touches three rows.
It proposes specific updates to the DFMEA and DVP&R
New rows, revised scores with the reasoning for each, and rows that no longer apply. It can do this before the change is approved, so the risk becomes part of the change decision instead of an afterthought.
Your engineer decides every proposed update
Nothing changes without them. Every decision is recorded and traced back to the change that prompted it.
Your engineer still owns the DFMEA.
It never certifies a product as safe or a risk as acceptable. It proposes; your engineer reviews, amends and approves, just as they do today.
Patent pending. In development.
Change Signal Monitoring is planned for a later release and is not part of the current pilot. If it matters to your team, tell us on the pilot application.
Start with a DFMEA built on your product.
We're enrolling a small number of pilot partners.