From leak rejects to a root cause, in eleven steps
A pump housing drifted out of flat and leak rejects rose. MIYOQA worked the problem from the records, and left every decision to the engineer.
In brief
- The Engineering Board drew a fishbone from the part's records. Every cause cites the record behind it.
- MIYOQA Intelligence drafted the whys, a root cause and a countermeasure: one task, 11 steps, 13 cents.
- An engineer read every cited record and accepted four proposals. The assistant approved nothing.
The problem
On the electric coolant pump, external leak rejects rose in lot 2216. At the same time, the face flatness of the machined housing was drifting at OP20. The question for the team was the usual one: why, and what do we change so it does not return?
Every category, checked against the record
The Engineering Board started with a fishbone. Its engines read the whole part, not a summary of it, and placed a card in each category only where a record supports one.
An empty category is a finding in its own right. It tells the team where the records do not point, before anyone spends a shift looking there.
From cause to countermeasure
The team then asked MIYOQA Intelligence to develop the problem as a 5-Why. It ran as one task of 11 steps, on Claude Sonnet 5.5, for 13 cents.
Each step rests on a recorded corrective action or the NCR. The assistant marked the causes as partly supported, because no readings are yet split by fixture cleaning, and proposed an action to make that split.
What the engineer decided
The engineer read every cited record before accepting anything, accepted the four proposals they support, and declined a repeated why. The verification action stays open for the engineer's decision. Nothing on the board was approved by the assistant.
Why it matters
Problem solving holds up in an audit when every step points to evidence and every decision has a name against it. Here the evidence came first, the drafting was fast and inexpensive, and the decisions stayed with the people accountable for them.
Demonstration case. The records come from Project M, a synthetic programme that ships with MIYOQA for training and evaluation. No customer data is shown.
More case studies
When a Ppk of 2.03 is not good enough
The index was well above the requirement, and MIYOQA still blocked the release. A capability number is only as good as the process behind it.
Read the case
Ask the plant a question, and check every line of the answer
One question became a plan of three engine steps and a brief in which every sentence points to its source.
Read the case