Faridabad's auto-component and engineering suppliers answer quality complaints from their OEM customers in structured formats, typically an 8D problem-solving report: the problem, containment, root cause, corrective action and so on. Writing them is slow, so suppliers and their software vendors are trying language models that draft the report from inspection data, complaint emails and past reports.
A plausible-looking draft is the danger. Tests should check:
- Root cause invention: the draft must not state a cause that is not in the investigation notes. Fluent "likely due to tool wear" sentences are the classic hallucination here.
- Data fidelity: part numbers, batch numbers, quantities rejected and dates must match the source records exactly.
Read moreRead less
- Copy-over from old reports: when past reports are used as examples, check that their actions do not leak into the new one.
- Completeness: every required section present, with "to be confirmed" where data is missing.
For practice, invent a small complaint case with inspection results and two earlier reports, generate drafts and score them field by field. Quality engineers who move into software testing have a real advantage here, because they can tell at a glance when a corrective action is nonsense.