On many shop floors, the true picture of production appears only at the end of a shift, in a spreadsheet. The production director learns where an order got stuck and why a machine stood idle when it is already too late to react. A manufacturing execution system flips that order around: it shows order statuses, throughput and downtime as they happen on the machine, not a day later.
In our experience, the hard part is not the concept of MES but assembling a team that understands the shop floor, the integrations and the software at the same time. We do not have a finished MES case study in our portfolio, let’s say that plainly. What we do have is real experience in industrial and Industry 4.0 projects and people who build the backend, tap into machines and design operator interfaces, so we supply the skills that deliver such an implementation instead of promising a story we have not lived.
What is a manufacturing execution system and what does it actually give production?
MES, the Manufacturing Execution System, is the software layer between planning and the machine. It translates an order from the ERP into concrete operations on the floor and gathers back the data on how they were done. In practice that gives you:
- visibility into the status of every order in progress, not just at the input and output,
- measurement of throughput and downtime (e.g. in OEE logic) based on facts, not estimates,
- batch and genealogy tracking of the product for quality and complaints,
- less paper and re-keying of data between systems and shifts.
In short, MES turns the floor from a black box into a source of data you can base decisions on.
What does order and status tracking on the floor look like?
Order tracking is the heart of a daily MES. The point is to always know where an order is, at which workstation and in what state:
- operation status (waiting, in progress, on hold, done) updated in real time,
- reports from workstations on produced pieces, scrap and downtime reasons,
- queuing and priorities, so the operator knows what to do next,
- a link to the batch, machine and operator for full traceability.
Production order tracking only makes sense when data flows straight off the floor, which is why we design it together with the integration layer, not as a separate screen for manual clicking.
How do you integrate an MES with ERP and machines?
An MES does not live on its own. On one side it must talk to the ERP (orders, routings, inventory, production settlement); on the other, to controllers and machines on the floor:
- ERP integration (e.g. SAP, Dynamics) via APIs, message queues or file exchange,
- machine data acquisition through OPC UA, Modbus, MQTT or PLC drivers,
- a middleware layer that normalises different protocols into one data model,
- support for older machines, often via added sensors or IoT gateways.
This is exactly where implementations most often stumble, so we treat integrations as a separate, full-fledged skill, not an add-on to the backend.
Why does production need real-time data?
Data collected once a day is for a report; real-time data is for acting during the shift. The difference is concrete:
- reacting to downtime in minutes, before it grows into a delay for the whole order,
- a live view of OEE and plan progress on a shop-floor board the team can see,
- an early quality signal, before a whole defective batch is produced,
- better planning decisions, because the next order is planned on facts from the floor.
For this to work, you need an event stream and a performant backend underneath, not a database polled once a day.
Which skills do we provide for an MES implementation?
We shape the team around the specific scope, not “just in case”. An MES project most often needs:
- backend developers (Java, .NET, Python) building the order logic, APIs and event processing,
- integrators who know industrial protocols and ERP systems,
- frontend / operator UI builders who design screens for work on the floor,
- DevOps and data specialists for deployments, event streams and reporting.
This setup lets the team take real ownership of a specific MES module, not just add hands to an existing plan.
How do we design operator interfaces for the floor?
An operator interface is not an admin panel. The operator works in gloves, in a hurry and often with a single screen per workstation, so the UI must be simple, large and error-resistant:
- large tiles and legible statuses instead of dense tables,
- a minimum of clicks to report a piece, scrap or downtime,
- operation on terminals and tablets in shop-floor conditions,
- a clear split between what the operator sees and what a supervisor or planner sees.
A good operator interface decides whether the data in the MES is true, because if reporting is a chore, the floor will find a way to skip it.
What are the most common MES implementation pitfalls?
MES implementations rarely fall over on technology; more often on organisation and integration. The pitfalls we see most often:
- starting with everything at once instead of one line or one area,
- underestimated integration with the ERP and the machine park,
- an interface designed from a desk, not at the workstation with an operator,
- no data owner on the production side who guards the quality of reports.
That is why we start from a narrow, working scope and extend it only once the data from the first area is reliable.
How fast can a team join an MES project?
Speed matters, because production will not stop for the implementation. Our recruitment usually closes in about three weeks, stretching to two months only for non-standard requirements, such as a rare combination of industrial and software skills. As a nearshore partner from Poland we work in a close time zone, so the team joins your rhythm of meetings, code reviews and shop-floor visits without a long ramp-up.
Custom MES or an off-the-shelf system: what pays off?
It depends on how non-standard your production is. An off-the-shelf MES starts faster where processes are standard, but it can chafe with unusual routings and integrations. A custom-built solution costs more up front, but fits your process and machine park exactly. In practice the middle option is common: an off-the-shelf core plus custom work at the edges with machines, ERP and reporting, and those edges are exactly where we most often add skills. We covered the differences between engagement models in our article on IT engagement models.
How do we do it at RITS?
We do it as a nearshore partner from Poland, with experience in industrial and Industry 4.0 projects:
- we supply the skills, even without a finished MES case study, as team augmentation or a dedicated team,
- we join backend, integrations and operator interfaces into one maintainable team,
- we verify skills before the start and shape the team around the implementation,
- we strengthen the data and analytics layer with AI/Data skills from the RITS Group where they add real value.
Most often we do this as custom software built by our team and, where people need topping up fast, as team augmentation.
Where to start with an MES implementation?
Start from one line or one area and from the question of what data you must collect from the floor to manage orders. That defines the integration scope, the shape of the operator interface and the roles you need. The first working slice of an MES will show more than months of analysis on slides.
Want to support production with an MES and order tracking? Let’s talk - we’ll match a team and a scope to your floor.