Audit-ready traceability for factories that outgrew spreadsheets.
Work orders at the line, unit-level traceability, and a batch record that exports as a file, on the machine data the Voltrus stack already collects.
Self-diagnosis
Signs you need MES.
Nobody buys MES because a brochure said so. You buy it when the paper layer starts costing real days. If two or more of these describe last week, the constraint is no longer the machines.
Two versions of the schedule exist
The spreadsheet the planner maintains and the sequence the floor actually runs have quietly diverged, and nobody can say which one is true.
Production numbers don't match inventory
Output re-typed into the ERP never quite agrees with what the line produced, so every month-end starts with a reconciliation hunt.
Downtime reason comes from memory
Reasons are reconstructed days later by whoever remembers, which makes the Pareto chart a story, not a measurement.
Customer traceability requests take hours
Answering which lot, machine, and operator made a part means pulling travelers and walking the warehouse while the customer waits.
Quality records are still paper
Inspection checklists live on clipboards and NCRs in a filing cabinet, so the audit pack is a three-day assembly project.
Shift handover depends on WhatsApp
The state of the line travels through chat threads: unsearchable, unauditable, and gone the day the phone does.
The same signs, by industry
“The BPOM audit took three days of pulling paper.”
Food and beverage plants under BPOM regulation keep batch records on paper and hunt for them when inspectors arrive. We implement the electronic batch record: production recorded once at the line, every batch traceable to machine, operator, and material lot, so the evidence is an export, not a search.
“We can’t tell which roll caused the defects.”
Roll-based packaging plants cannot trace a defect back to the input roll, so every recall is wider and slower than it should be. Roll and lot are captured at machine-level ingest and traced through the work orders: the affected width is a query, not a guess.
“A customer genealogy request cost us a week.”
Automotive customers ask which order, station, operator, and lot produced a part, and answering by hand eats the week. Here it is the default record: every unit is captured as it runs, and the genealogy pack exports as CSV with documented columns.
What it covers
Execution modules on the data path you already have.
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, and every block below names what ships, not what might.
Machine Connectivity & Ingest
Counts, states, and scrap captured at the machine through the Voltrus stack: Gateway protocols feeding SCADA and OEE ingest. No operator tallying, no clipboard at the end of the shift.
Work Orders & Schedule
The week's schedule becomes work orders dispatched to the terminal at the line. Operators start and stop against real orders; actuals post back from machine data.
Lot Genealogy & Audit Pack
Every unit tied to machine, operator, and material lot. The electronic batch record (the audit pack) is assembled from the production record and exported as a file, not retyped.
Inspections & NCR
Checklists and measurement checks at the station, triggered by event or quantity. Out-of-spec becomes an NCR recorded against the lot, not initials on a paper form.
OEE Rollups & Downtime
Availability, performance, and quality rolled up per work order and shift, with downtime reason codes and alerts: station down, OEE below target, order running late.
Reports & Month-End Packs
Production and NCR reports as CSV with documented columns; a month-end zip for the auditor or the ERP. The MES executes; your existing systems keep doing their jobs.
AI Native, MCP First
The whole MES is one MCP endpoint: 25 tools covering sales orders, work orders, the line terminal chain, OEE, and lot trace. Claude, Codex, or any MCP client runs the plant in natural language, behind the same role gates as the UI.
What it looks like
Screens from a running instance, not mockups.
These are live captures from a running instance, on the seeded demo line. Every module below ships today. Full per-module documentation with screenshots lives in the docs.
The stack
One pyramid, every layer shipped.
One ISA-95 pyramid, every layer shipped. Voltrus fills L1 to L3 on native industrial protocols through the Voltrus Gateway; your ERP keeps L4, integrated via API.
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.
Pricing
One price per machine. Checkout to shop floor in a day.
Software only: pay by card, pick a password, create your machines. You connect the hardware with the included Voltrus Gateway, no implementation project, no SI on your payroll.
Voltrus MES · all modules · software
Billed annually · 5-machine site minimum · every module included · updates included
- Work orders, schedules, and shift handover at the line
- Lot genealogy with an exportable audit pack (batch record)
- Quality inspections and NCR at the station
- OEE per work order and shift, downtime reason codes
- Andon board, alerts, maintenance tickets and PM schedules
- CSV packs for your ERP and month-end
- Support in Bahasa Indonesia or English
Checkout by card through Polar. Payment lands on an activation page: pick a password and your site is live. Bank transfer or Rupiah invoice: [email protected]
Multi-site, SSO, white-label for SIs, or hands-on onboarding around East Java: talk to us.
FAQ
Common questions
For SI partners
You already sell, install, and support the PLC and SCADA layer. Traceability is the question your factory customers ask next.
Partners deliver Voltrus MES under their own brand, with us on the build side: co-delivery on your customer, your relationship, your margin. The factory trusts you already, and that trust is the channel.
The next audit finds the answer in a file.
Lot genealogy, the electronic batch record, inspections and NCR, OEE per order: recorded as production runs, exported when asked, on the stack that already runs your machines. One line to start.
Stay updated
Product updates and the MES build log. A few emails per quarter.
Also from Voltrus