Role-based Scenarios

1. Why role matters

The same platform is used differently by different people.

Prodia becomes more useful when the question, analytical path, and output are matched to the role that is reading the answer.

2. Typical role views

Role	Typical concern	Typical Prodia output
Plant or production management	yesterday's performance, major loss, priority follow-up	KPI summary, anomaly highlights, focus list
Production supervisor	line fluctuation, bottleneck, shift comparison	line and process comparison, bottleneck clues
Quality engineer	bad rate, defect structure, quality loss source	defect ranking, affected process, likely cause path
Process engineer	takt, parameter window, process relationship	bottleneck signals, parameter focus, optimization direction
Maintenance or equipment engineer	downtime, fault distribution, equipment risk	fault Pareto, MTBF / MTTR, investigation order
OEM or service team	repeated anomaly handling, cross-site experience reuse	case recall, suggested diagnosis path, knowledge assistance

3. Scenario examples by role

Management

• What were yesterday's output, OEE, and yield?
• Which anomaly should be reviewed first this morning?

Production

• Which process slowed the line down the most?
• What changed between day shift and night shift?

Quality

• Which defect type contributed most to the yield drop?
• Which process should be reviewed first?

Process

• Which station has the largest takt fluctuation?
• Which parameter is most worth checking?

Maintenance

• Which fault caused the longest downtime this week?
• Which equipment deserves first inspection?

OEM / service

• Have we seen a similar field issue before?
• What should be checked next for this anomaly pattern?

4. Practical takeaway

Prodia should not be positioned as a single generic question-answer screen.

Its value increases when it becomes a shared industrial intelligence layer for different roles, while keeping each role's question style and decision needs intact.