Exception Diagnosis Loop

1. What this workflow solves

When an abnormality appears, the problem is rarely the lack of data alone.

The harder part is deciding:

• what changed first
• which scope is affected
• where to investigate first
• how to coordinate the next action

2. Workflow structure

3. Typical exception-handling sequence

Step	User action	System response
1	Raise the abnormal signal	identify line, process, station, equipment, and time range
2	Ask why it happened	return comparison and ranked cause clues
3	Ask what to check first	suggest first inspection path
4	Ask who should be involved	point to likely operational roles
5	Close the review	retain case and response path for future reuse

4. Why it matters

• reduces diagnosis latency
• improves consistency in exception response
• lowers dependence on individual expert memory
• makes similar future anomalies easier to handle