Several AI surfaces connected to different parts of VECHR MES, rather than one chatbot for everything. All of them follow the same principle: the AI proposes, a person confirms, and nothing in production data changes without approval.
Ask questions about your plant in plain language. The AI drafts routings, flows and master data, and a person confirms every change.
Today Answers wait for someone to build a report.
With VECHR MES Ask in plain language. Get the answer from live data.
Today Configuration means navigating many forms.
With VECHR MES The AI drafts it. You review and confirm.
Today AI cost is a black box.
With VECHR MES Token use is tracked per user, per model, per turn.
Each is designed for different work, but all of them hold the same line: AI helps you make the decision, it does not take the decision over.
| Surface | What it does |
|---|---|
| AI Insight | Answers everyday-language questions about KPIs, OEE (Overall Equipment Effectiveness), downtime, and the status of a particular batch or lot. |
| MES Advisor | Helps answer configuration and usage questions from the product documentation, rather than generating an answer from general knowledge. |
| MES Expert Engineer | Drafts master data changes for a person to review. It never executes those changes itself. |
| Orchestrator Assistant | Turns a plain-language description of an automation into a draft flow that can be reviewed before deployment. |
| Routing Designer Assistant | Turns a plain-language description of a production process into a draft routing to review before use. |
This boundary is part of the system design: a proposed change has to pass human confirmation before it is applied or saved as a change.
AI Insight opens from the top bar (⌘⇧A or Ctrl+Shift+A). Behind it are three specialised read-only agents for performance, production and quality, so each conversation loads only the tools it needs.
What executives and IT usually ask before enabling AI.
Not directly. The surfaces that produce changes only create drafts, and a user has to review and confirm before anything is applied. That boundary is part of the system design, not a permission that can be loosened.
Questions about the operation are answered from the MES data and records available. MES Advisor uses the product documentation as its context for configuration and system usage questions.
Token usage is tracked per user, model, and turn, and can be filtered by time range. Administrators can see usage patterns and AI consumption clearly.