
A Manufacturing Execution System (MES) records and guides what actually happens on the shop floor: which order is on which machine, who ran it, how many parts were produced and rejected, what material went in, and why the machine stopped. If you are new to the idea, start with our guide What is an MES?
This article is for manufacturers who have decided they need MES capability and are weighing custom MES software development — building a system designed around their own factory — against buying a packaged product. It covers when building makes sense, what to build first, how operator apps and machine data fit in, how the project runs and what drives cost.
Why factories build their own MES
Packaged MES products are designed for the processes their vendors expect. For a plant that fits them, they work well. Custom development is chosen when:
- The process is specific. Job shops with changing routings, batch processes with recipes, mixed assembly and machining, job work with outside vendors, or testing steps unique to the product.
- The shop floor needs simple screens. Operators need two or three large buttons in their own language, not a screen designed for every possible industry.
- Integration matters. Orders come from an existing ERP or Tally, quality records must follow customer formats, and results must flow back to planning and accounts.
- Machines are mixed. New CNCs with data interfaces sit next to 20-year-old presses. A custom system can collect data in whatever way each machine allows.
- Licences scale badly. Per-station or per-user pricing grows quickly when every machine gets a tablet.
Our article on how to choose MES software helps decide between the two routes.
The core MES modules
Production orders and routings
Orders arrive from the plan or ERP with their operations, machines or work centres, standard times and drawings. The MES releases them to the shop floor in the planned sequence.
Production booking (the operator app)
At each machine or station, an operator logs in, scans the job card or selects the order, starts and stops the operation, and records good quantity, rejections with reasons, and downtime. This replaces paper job cards. A good operator app is fast, works on inexpensive Android tablets, supports local languages and needs very little typing.
Work-in-progress tracking
Because every operation is booked, the system knows where each order is, how much is complete, what is waiting between operations and what is at outside job work. Planners and sales can answer "where is my order?" without walking the floor.
Downtime and OEE
Every stoppage is recorded with a reason — breakdown, setup, no material, no operator, quality hold — using well-designed downtime reason codes. From availability, performance and quality, the system calculates OEE by machine, shift and product.
Quality checks
First-piece, in-process and final inspections are recorded against the job, with limits and photos, as described in in-process quality checks in MES. Out-of-limit results can hold the job automatically.
Material and traceability
Material lots, heat numbers or batches are scanned when issued to the job, building the lot genealogy needed for customer complaints and recalls.
Digital work instructions
Each operation can show its drawing, setup sheet, photos and steps on the operator's tablet, always the current revision. See digital work instructions for manufacturing.
Shift handover and dashboards
Shift reports generate themselves from bookings. Supervisors hand over open issues in the app instead of a notebook. Managers see live boards by line and plant.
Machine data: when and how
Machine connectivity is valuable but not where every MES must start. Common options are:
- Operator entry only — fastest to start and works on any machine.
- Simple signals — a cycle or running signal from the machine or an add-on sensor gives accurate counts and run time. See retrofitting old machines for IIoT.
- Controller and PLC data — modern CNCs and PLCs can provide status, counts, alarms and parameters through their data interfaces, where the machine supports them.
Many plants combine all three: automatic counts where available, with operators adding reasons and quality data.
Integration with ERP and other systems
The MES sits between planning and the shop floor. Typical links are sales orders and production orders from the ERP, material issues and receipts with stores, finished goods back to the ERP, and quality records to the QMS. Our guide to MES versus ERP explains where each system's responsibility ends, and one work order through ERP and MES follows a real order across both.
How a custom MES project runs
- Discovery on the shop floor. Developers walk the process with supervisors and operators, collect job cards, inspection sheets and reports, and agree what the first phase must deliver.
- Scope and estimate. A written scope listing modules, screens, roles, devices, integrations and phases.
- Screen design with operators. Operator screens are tested with real operators before coding — this is the single biggest factor in adoption.
- Phase one build. Typically booking, WIP and downtime for one line, with a supervisor dashboard.
- Pilot and adjust. A few weeks of real use, then fixes and improvements.
- Rollout and later phases. More lines, quality, traceability, machine data and integrations.
Our MES implementation roadmap for SME manufacturers goes deeper into sequencing, and MES ROI shows how to build the business case.
What drives MES development cost
- Number of modules and lines in the first phase.
- Variety of processes — one discrete process is simpler than machining, assembly and batch processes together.
- Device requirements — tablets, barcode scanners, label printers, offline operation.
- Machine connectivity — number and variety of machines and what their controllers support.
- Integrations with ERP, Tally, QMS or customer portals.
- Reporting — standard dashboards versus many customer-specific formats.
- Hosting, support and the pace of later phases.
See manufacturing software development cost for how to estimate a factory software project.
Common mistakes to avoid
- Starting with everything. A big-bang MES across all lines and modules delays value and overwhelms users.
- Designing for managers instead of operators. If booking takes too long, operators stop doing it and the data is worthless.
- Ignoring master data. Routings, standard times and reason codes need cleaning before go-live.
- No owner in the plant. Every successful MES has a production manager who champions it daily.
Architecture choices for a custom MES
A development company should explain its technical approach in plain terms. The main choices are:
- Cloud, on-premise or hybrid. Cloud hosting simplifies access across plants and reduces IT burden. Plants with unreliable internet can use a local server or local caching on devices, synchronised with the cloud.
- Web app, tablet app or desktop app. Supervisors and managers use web screens; operators often use Android tablets; high-volume data entry teams may prefer a keyboard-driven desktop app. One central database can serve all three.
- Machine data layer. Signals from sensors, PLCs or CNC controllers are collected by a small gateway at the plant and sent to the MES, so a network interruption does not lose data.
- Integration layer. Clearly defined interfaces for orders in and results out, so the ERP or accounting system can change in future without rebuilding the MES.
- Configurability. Reason codes, inspection characteristics, routings and shift patterns should be maintained by the plant team in master screens, not by developers.
Designing the operator app
The operator app is where most MES projects succeed or fail. Principles that work on Indian and international shop floors alike:
- One job, one screen. The operator sees the current job, its quantity, target and the next action. Everything else is a tap away.
- Scan instead of select. Job cards, materials and operator IDs are scanned with the tablet camera or a scanner.
- Reasons from a short list. Six to ten downtime and rejection reasons per machine type, with icons where helpful.
- Prompt at the right moment. Ask for a downtime reason when the machine has stopped, and a quality check when one is due — not at the end of the shift.
- Show the operator their own performance. Count against target and good parts so far motivate more than any report.
Master data you will need
An MES depends on master data that many factories hold only partly or in people's heads. Prepare it early:
- Machines and work centres, with capacity and shift patterns.
- Items, drawings and revisions.
- Routings — operations, machines, standard cycle and setup times.
- Bills of materials for assembled products.
- Downtime, rejection and rework reason codes.
- Inspection characteristics and limits for in-process checks.
- Operators, skills and shift rosters.
Standard times do not need to be perfect at the start. Once the MES records actual times, you can correct them from real data — one of the first benefits factories see.
Measuring success
Agree before the project starts how you will judge it. Typical measures are the time taken to answer "where is my order?", hours spent compiling shift and daily reports, visibility of downtime by cause, rejection rate by machine and product, on-time delivery, and the accuracy of WIP and finished goods stock. Record where you are today so the improvement can be seen.
Where Corposol fits
Corposol builds custom MES and shop-floor management software for manufacturers, from operator tablet apps to plant dashboards, integrated with existing ERP and accounting systems where they allow it. For a hydraulics manufacturer in Bengaluru's Peenya Industrial Area, we replaced an old in-house VB application with cloud software and a keyboard-driven desktop app now used across all 11 of its factories — read the use cases. We build in phases and transfer all custom code on final payment.
Frequently asked questions
What is the difference between buying an MES and developing one?
A packaged MES comes with fixed screens and workflows that the factory configures and adapts to. A custom MES is designed around the factory's own routings, records, roles and machines, and is owned by the factory. Packaged products suit plants whose processes match the product; custom development suits plants with specific processes, mixed machine types or tight links to existing systems.
Can an MES be built in small phases?
Yes, and it usually should be. A first phase such as production booking on tablets, work-in-progress tracking and downtime reasons for one line can go live in weeks, proving value before the wider rollout.
Do our machines need to be connected for an MES?
No. Many MES projects start with operator entry and barcode scanning. Machine signals can be added later where machines or add-on sensors support it.
Can a custom MES work with Tally or our ERP?
Usually yes, where the ERP or accounting system offers an API, import facility or data export. Orders can come from the ERP and production results can go back to it. We confirm feasibility during scoping.
