What Is a MES? Manufacturing Execution Systems in Plain Language
A manufacturing execution system (MES) is the software that runs production on the factory floor: it takes a work order, puts it in front of the operator, records what the machines actually did, and reports the result back to the systems that count money. That is the whole job. Everything else in this article is detail hanging off that sentence.
Vendors wrap that job in acronyms and suite names, and enterprise MES projects have earned their reputation for cost and delay. But the underlying idea is simple, and for a mid-market factory it is worth understanding plainly before anyone quotes you a project. We build Voltrus MES, so read this as the explanation we would give you across the table.
What a MES Does Day to Day
Strip the marketing and a MES cycles through four responsibilities, every shift:
- Work orders: the schedule becomes a task at the line. The operator starts and stops against a real order, and the counts, scrap, and machine states post back from the equipment instead of from memory at the end of the day.
- Traceability: every unit gets tied to the machine that made it, the operator who ran it, the material lot that went in, and the process parameters at the time. When a customer complaint or an auditor arrives, the answer is a query, not a warehouse walk.
- Quality checks: checklists and measurements happen at the station, triggered by quantity or event, with an out-of-spec path that does not depend on initials on paper.
- Performance: availability, performance, and quality (the three OEE factors) roll up per work order and per shift, so you can see which orders ran well and which ones quietly ate the margin.
Where It Sits in the Stack
A MES does not talk to machines itself, and it does not keep your books. It sits in the middle of a chain you probably already have pieces of:
- Machines and PLCs hold the raw signals: counts, states, alarms.
- A gateway or protocol layer (for us, Voltrus Gateway: seven protocols behind one API) turns those signals into data a computer can use.
- SCADA and OEE (we sell Voltrus SCADA and Voltrus OEE) watch the machines: dashboards, alarms, downtime, availability per machine.
- The MES turns that stream into execution: orders, traceability, quality, and performance per order.
- The ERP or accounting system receives production confirmations and keeps the financial truth.
The practical consequence: if you already run SCADA or OEE, a MES does not need a new data-collection project. It reads the same path. That is the single biggest cost difference between a MES built on your existing stack and one sold as a green-field platform.
Signs Your Factory Has Outgrown Spreadsheets
Most factories we meet run scheduling on a spreadsheet and line status on a WhatsApp group. That works, until one of these happens:
- Someone asks which batch ran on which machine with which material lot, and the answer takes a day of searching.
- Two people edit the schedule file and one version silently loses.
- Scrap counts get typed in days later, from memory, and nobody trusts the yield number.
- The one person who understands the spreadsheet is on leave.
- You cannot say which orders made money, because downtime lives in one place and output lives in another.
One of these is an annoyance. Two or more mean the factory has outgrown the tool, whatever the tool costs.
Why MES Projects Earn Their Bad Reputation
Enterprise MES is real software with real value, sold with enterprise economics: licensing that assumes plant-wide rollout, implementation led by a systems integrator, and go-live measured in quarters. The patterns feed each other: wide scope forces long projects, long projects force change management, and the factory keeps running on spreadsheets the whole time.
The fix is not a cheaper enterprise MES. It is a smaller first step: one line, the modules that line needs, data from the systems already in place, and a vendor who treats go-live in weeks as the product. That is the gap Voltrus MES is built for, and why we run it as a pilot cohort instead of a download: the first handful of sites set the build order with us.
Frequently Asked Questions
Is a MES the same as SCADA?
No. SCADA watches machines: live values, dashboards, alarms, history. A MES runs production: work orders, traceability, quality, OEE attributed to orders. SCADA data is an input a MES consumes. We break this down further in MES vs ERP, since the two questions usually come together.
Does a small factory need a MES?
Need is strong wording. If the spreadsheet version of your schedule is accurate, current, and understood by three people, you may not. The honest test: when something goes wrong on an order, can you reconstruct what happened in minutes? If not, execution is being run on memory, and memory does not scale.
How long does a MES implementation take?
Enterprise answer: six to eighteen months. Our answer: the pilot starts at one line, with onboarding assisted by us on a call or on site around East Java. The heavy parts of traditional projects (plant-wide scope, new data collection, custom integrations designed in a conference room) are exactly the parts we cut.
What does it cost?
Voltrus MES is free during the pilot. Production pricing is set with the pilot cohort and locked for pilot sites. The layers below it (SCADA from $49 one-time, OEE from $30 per machine per month) are priced publicly today.
See the MES Layer for Yourself
Voltrus MES is in early access: a pilot cohort of factories is setting the scope now. Read the honest version of what ships and what does not, or request a pilot slot for your line.
See Voltrus MES