A plain definition.
A manufacturing execution system is software that manages and records work as it happens on the shop floor. Where planning software decides what should be made, an MES helps coordinate and document what is actually being made: which order is running, which instructions apply, what was produced, what went wrong, and who did the work.
In the ISA-95 model of manufacturing systems, this activity sits between business planning systems and the equipment and controls on the floor. Real products differ a great deal. Some focus on production tracking, some on quality, some on maintenance or documents, and many combine several of these in modules.
What an MES typically covers.
No two vendors draw the boundary in the same place, but most MES offerings include some mix of the following areas.
- Production execution: work orders, routing, status, and output.
- Work instructions and document control at the point of use.
- Quality data: inspections, nonconformances, corrective actions.
- Material tracking and traceability from lot to finished product.
- Equipment status, downtime and maintenance.
- Workforce records such as training and qualifications.
- Reporting on performance, for example output, scrap and downtime.
Signs a plant is ready to look at one.
You rarely need an MES because a vendor says so. You usually need one when the cost of not knowing becomes visible. Common signs include operators using different versions of the same instruction, a customer or auditor asking for records that take days to assemble, scrap discovered at the end of a shift instead of during it, and key knowledge that lives in a few people’s heads or spreadsheets.
A useful test is to pick one recurring problem and ask what information would have prevented it, and when that information needed to be available.
Why a modular start can make sense.
Large MES projects have a reputation for taking a long time and asking a plant to change everything at once. A smaller manufacturer often does better by choosing the one workflow that causes the most pain and getting that under control first. Document control and training records are practical first steps because they are needed in every plant, they do not depend on connecting machines, and they produce records an auditor can ask for on day one.
The risk of a modular approach is picking tools that do not fit together later. When you evaluate any modular system, ask how the modules share users, locations, permissions and master data.
A realistic first ninety days.
A practical first phase is smaller than most people expect. In the first month, pick one workflow, name an owner, and agree on what a good result looks like, for example finding any current work instruction in under a minute. In the second month, run a pilot with a single line or department and collect feedback from the people who actually use it. In the third month, review what worked, fix the rough edges, and decide whether to extend to another area or another module.
The plants that succeed with this approach tend to measure something simple before and after: the time to find a record, the number of out-of-date copies found on a walk, or the number of overdue training items. A modest improvement you can show is a better foundation than a large plan nobody can verify.
Where STRATUM MES is today.
STRATUM MES is designed as a modular system for small and mid-size manufacturers. Today the modules presented on this site are Document Control and Training. Paid subscriptions are not open yet, and ERP, MRP, Production and broader quality tools remain under development. If you are looking for production tracking, material tracking or equipment monitoring today, STRATUM is not yet that product.
What’s live and what’s comingDocument control softwareTraining software
Questions to ask any MES vendor.
Whichever product you evaluate, a few questions help separate what exists from what is planned.
- Which modules are in production use today, and which are on a roadmap?
- Can I try the actual product with my own users, not a recorded demo?
- How are users, plants and permissions shared across modules?
- What does a pilot with one workflow look like, and how long does it take?
- How do I get my data out if I leave?
- What do I need to supply, such as imports or integrations, and who does that work?