Scenario Routing and Intent Parsing
1. Why routing is necessary
Different industrial questions require different analytical paths.
Prodia therefore needs to decide:
- what the user is asking
- which object and period are involved
- whether the task is descriptive, diagnostic, predictive, or prescriptive
- which governed capability should be called next
2. Typical parsing dimensions
| Dimension | Example |
|---|---|
| Object | line, process, station, equipment, product, batch |
| Metric | output, yield, OEE, takt, fault, parameter |
| Time | yesterday, this week, last shift, a batch window |
| Intent | query, compare, diagnose, recommend |
| Priority | urgent anomaly, routine review, optimization topic |
3. Why parsing quality matters
If intent parsing is weak:
- the wrong capability may be selected
- comparison scope may be wrong
- follow-up questions may lose continuity
- results may be hard to trust or act on
4. Routing principle
Prodia should route a question to the smallest sufficient industrial path:
- simple queries should stay lightweight
- diagnostic questions should continue into ranked factors or cause clues
- high-risk flows should prefer playbooks or governed analytical paths