Typical Workflows

1. Prodia’s closed-loop flow

Prodia is not a collection of isolated features. It is designed as a continuous path from question to action.

2. Three common workflows

Daily review workflow

Step	User action	System output
1	Query yesterday’s core indicators	Output, OEE, yield, anomaly summary
2	Ask which part moved the most	Line / process / equipment-level differences
3	Ask for the likely cause of the anomaly	Cause candidates, affected scope
4	Ask what to focus on today	Priority items and follow-up suggestions

Exception handling workflow

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 asking	What to check first, who to involve, which period to inspect
4	Receive guidance	Investigation path, recommended actions, review direction

Process optimization workflow

Step	User action	System output
1	Identify a bottleneck or quality fluctuation	Bottleneck station or process
2	Analyze trend and distribution	Pattern of variation, high-impact objects
3	Relate process and parameters	Optimization direction and key variables
4	Form improvement actions	Follow-up validation items and watch metrics

3. Why this matters

• Faster: reduce the time from issue discovery to workable judgment
• More stable: reduce variation through standardized analytical paths
• More repeatable: let the workflow be reused instead of relying on individual memory