MES for factories that outgrew spreadsheets.
Work orders dispatched to the line, every unit traceable to machine and material, quality checks at the station, OEE rolled up per order. It runs on the machine data the Voltrus stack already collects. No enterprise-MES budget, no 12-month implementation.
01 · The problem
Mid-market factories run execution on Excel and WhatsApp.
The schedule lives in a spreadsheet. Line status travels by WhatsApp. Travelers are paper, quality checks are initials on a form, and traceability means walking the warehouse. When an auditor or a customer asks which batch ran on which machine with which material lot, that is a day of searching.
Enterprise MES answers this, on enterprise terms: SAP-class licensing, a systems-integrator project, 6-18 months before go-live. Most mid-market factories reasonably conclude the cure costs more than the disease.
02 · What it covers
Execution, not another dashboard.
Six modules, one data path: the same machine data SCADA and OEE already collect. No parallel data-collection project, no new wiring at the machine.
Dispatch & Scheduling
Work orders from the schedule to the terminal at the line. Operators start and stop against real orders; counts and scrap post back automatically from machine data.
Traceability & Genealogy
Every unit tied to machine, operator, material lot, and process parameters. Batch → machine → operator in one query, exportable as a report when the auditor asks.
Quality at the Station
Checklists and measurement checks triggered by event or quantity, with out-of-spec handling instead of initials on a paper form.
OEE Rolled Up per Order
Availability, performance, and quality from the same machine data OEE uses, attributed to work order and shift, not just per machine.
Shift & Andon Reporting
End-of-shift production report by line and order. Andon state per line, visible on the floor display and in the dashboard.
ERP Handoff
Production confirmations out as CSV or API to Odoo, SAP Business One, Accurate, or whatever the plant already runs. MES executes; the ERP keeps its books.
The stack
The layers below MES already ship.
Gateway, SCADA, OEE, PLC, and eight native protocol explorers are bought and running in production today. The machine-data layer is product, not a promise. MES reads the same data path, and its scope is set by the pilot cohort, not by a generic spec.
03 · Integration without a project
Describe the input. Describe the output. Review it like a PR.
On the roadmap for MES: an MCP server and an AI-assisted flow builder. Local IT describes what data comes in and what should go out where; the AI compiles that into a reviewable integration flow; the engine runs it deterministically. The AI authors, humans approve, the runtime never calls a model.
Describe it
"Odoo creates a purchase-order work order; MES should create the same work order at line 2." You bring the input source, the expected output, and one sample payload from each side.
AI compiles the flow
A declarative YAML flow (trigger, transform, output) generated from your description and validated against the schema before you ever see it. Invalid flows are rejected at authoring time.
You review the diff
Every flow is a file in git. Dry-run it against a real payload, read the diff, activate when it's right. Rollback is git checkout. No black box wiring your plant.
Engine runs it forever
A deterministic executor with webhooks, cron triggers, retries, and a dead-letter queue. Zero LLM calls in the hot path: the AI is the compiler, not the runtime.
04 · Compare
How it compares to what you're using now
Every factory running on spreadsheets has the same three options. Here's how they stack up.
05 · The pilot
Free during the pilot. Priced per line after.
The pilot cohort, a small number of sites, sets the build order. We would rather build the second-most-important screen second than guess.
| Phase | What you get | Price |
|---|---|---|
| Pilot site | Work orders + traceability + OEE rollup on one line, onboarding assisted on a call or on site (East Java), direct line to the build queue. | Free during pilot |
| Production | All modules, per-line pricing, updates included. | Set with the pilot cohort, locked for pilot sites |
| Multi-site / OEM | Multi-site, SSO, white-label. | Talk to us |
Where it stands
Shipping today: Voltrus SCADA, Voltrus OEE, Voltrus Gateway, Voltrus PLC, and the protocol tools. You can buy and run all of it now.
Voltrus MES is early access. There is no download on this page, and this is the only honest MES landing page you'll read this year. The pilot cohort sets the scope; if the cohort doesn't fill, MES doesn't get built and this page will say so. The layers below keep shipping either way.
06 · FAQ
Common questions
For SI partners
You already sell, install, and support the PLC and SCADA layer. MES is the question your factory customers ask next.
Pilot partners deliver Voltrus MES under their own brand, with us on the build side: co-delivery on your customer, your relationship, your margin.
Talk about white-label →Run the line, not the spreadsheet.
Work orders, traceability, quality checks, OEE per order, built with a pilot cohort of Indonesian factories, on the stack that already runs their machines.
Stay Updated
Get notified about the pilot cohort & build updates
Pilot-cohort openings and the MES build log. A few emails per quarter, no spam.
Also from Voltrus