Prodia is designed as a continuous path from issue discovery to result improvement.
This loop continues into “what should be done first, who confirms it, and whether the result improved.”
| Step | User action | System output |
|---|
| 1 | Review core fluctuation from yesterday or this week | output, OEE, yield, downtime, anomaly summary |
| 2 | Ask which part had the largest movement | line / process / equipment-level differences |
| 3 | Ask for the likely main cause | cause candidates, affected scope |
| 4 | Ask what should be addressed first | priority issues and suggested actions |
| Step | User action | System output |
|---|
| 1 | Notice a quality, fault, or takt anomaly | affected object and time range |
| 2 | Trigger diagnosis | ranked factors and comparison results |
| 3 | Continue probing | what to check first, who to involve, which period to inspect |
| 4 | Receive guidance | investigation path, suggested action, review direction |
| Step | User action | System output |
|---|
| 1 | Identify a bottleneck or quality fluctuation | station or process bottleneck point |
| 2 | Analyze trend and distribution | variation pattern and high-impact objects |
| 3 | Relate process and parameters | optimization direction and key variables |
| 4 | Form improvement actions | follow-up validation items and watch indicators |
- more proactive: it helps identify the most important issue faster
- less people-dependent: it reduces repeated reliance on experts and repetitive manual preparation
- more results-oriented: it makes it easier for analysis to connect to quality, efficiency, and cost improvement