Quality and product safety

Lessons learned that the next product generation actually finds

Quality methods produce a lot of documentation: 8D reports, FMEAs, test results. The reasoning behind them stays in the individual document. rygg links complaint, root cause, measure, FMEA update and proof of effectiveness, so the next project and the next plant can find them.

Find your starting point Demo graph: Quality and product safety

Situation

The same root cause appears again in another plant or product generation.

FMEAs are updated, but the link to the complaint and to the user context is missing.

In a liability case, the organization has to show what was known and decided, and when.

Questions rygg answers

Has this root cause appeared before, and what was done?
Which measure proved effective, and how was that shown?
Which special characteristics have no valid measurement system analysis?
Which use errors from the field are not yet in the FMEA?
What did we know at the time of this decision?

Applications in this use case

Quality and product safety: 4 applications

context engineering with rygg

Repeat root causes

Whether a root cause has occurred before, in another plant or product generation, and what helped.

Agent context

Agent task: Searches similar complaints and root causes
Reads: 8D reports, root causes, measures, effectiveness
Suggests: Similar cases with references
Approved by: Quality engineer

Metric: Repeat root causes across plants

From 8D to FMEA

Root causes and measures transferred into the FMEA, with proof of effectiveness.

Agent context

Agent task: Proposes FMEA updates from closed 8D cases
Reads: 8D, FMEA, characteristics
Suggests: FMEA update draft
Approved by: FMEA moderator

Metric: Measures with proof of effectiveness

Use errors from the field

Use errors observed in the field linked to failure modes, so they reach development and the FMEA.

Agent context

Agent task: Maps field observations to failure modes
Reads: Field findings, contexts of use, failure modes
Suggests: Link suggestions
Approved by: Product safety

Metric: Field use errors transferred into the FMEA

What was known when

The state of knowledge at the time of a decision, reconstructed from the timeline of the graph.

Agent context

Agent task: Reconstructs the state of the graph at a given date
Reads: Nodes with creation and change dates
Suggests: Snapshot report with node references
Approved by: Product safety and legal

Metric: Time to answer a liability question

What rygg provides

8D trail: complaint, root cause, measure, FMEA update, effectiveness
Characteristic chain with test status and validity
Use context from the field linked to failure modes
Decision records with the information available at the time

Who works with it

Head of quality, plant management
Product safety
Development and test

Metrics we agree on

Repeat root causes across plants and generations
Measures with proof of effectiveness
Field use errors transferred into the FMEA
Time to answer a liability question

What rygg is not here

Not a CAQ or FMEA tool. rygg reads from them and keeps the reasoning across documents.

How it starts

One product family: complaints, 8D reports and FMEA of the last years brought into the graph, with a report on repeat causes and missing links.

Find your starting point

Usually starts withEvidence Project

Research and design to HCRD standards. Results are documented so they can become part of a graph.

Demo graphQuality and product safety

Complaints, root causes, FMEA updates, proof of effectiveness and the information available at the time of a decision.