Operations Strategy

MES vs ERP for Indian Manufacturers: Where Each Belongs

Written by Anand Krishnan (Implementation Lead, Manufacturing Operations). Reviewed by Jainam Shah (Founder, ERPDrive). Published 19 May 2026. We update this article when GST rules, compliance thresholds or IATF standards change.

Published 19 May 2026 11 min read Anand Krishnan

Quick definitions

MES (Manufacturing Execution System) is a software layer that runs on the shop floor between the high-level planning system (ERP) and the physical equipment (machines, sensors, PLCs). It typically captures real-time machine signals, dispatches work orders to specific operators or machines, enforces process routings step-by-step, and feeds back actuals to the ERP. The ISA-95 standard defines this as 'Level 3' between the business planning (Level 4 = ERP) and process control (Levels 1-2 = PLC/SCADA).

ERP (Enterprise Resource Planning) is the business-management layer above MES. It handles orders, inventory, accounting, procurement, and high-level production planning. For Indian manufacturers it must also handle GST, e-invoicing, ITC-04 job work, and payroll. Modern manufacturing ERPs include production-tracking that overlaps with what MES does - which is the source of most of the confusion.

Where ERP ends and MES begins (in theory)

The classical division of labour from ISA-95:

  • ERP: sales orders, purchase orders, production plan, BOMs, inventory, costing, finance, payroll. Time horizon: weeks to months.
  • MES: work-order dispatch to specific machine/operator, real-time machine data capture, operator clock-in/out, statistical process control (SPC), full electronic traceability, work-in-progress tracking. Time horizon: minutes to hours.
  • PLC/SCADA: direct machine control, cycle time, motor speed, temperature, pressure. Time horizon: milliseconds.

Where the line actually sits in 2026 (Indian SME reality)

In practice the line has moved. Modern manufacturing ERPs include features that 5 years ago would have required a separate MES:

  • Operator clock-in/clock-out tied to a work order.
  • Machine signals via OPC-UA or MQTT for OEE computation.
  • Reason-code logging for stops.
  • First-piece QC blocking the next step until cleared.
  • Batch and serial-number traceability through multi-step routings.
  • Live shop-floor dashboards.

When you need both ERP and a separate MES

From our experience implementing across 60+ Indian shop floors, you need a separate MES when ALL of these are true:

  • Turnover above INR 200 crore.
  • More than 200 operators per shift.
  • Customer requires traceability down to component batch (e.g., automotive Tier-1, defence, aerospace, medical devices).
  • Cycle times under 30 seconds where the operator cannot reasonably clock each piece manually.
  • Existing investment in PLCs and sensors that can feed sub-minute data.

Cost comparison (Indian market, 2026)

Indicative ranges from quotes we have seen:

  • Indian cloud manufacturing ERP (e.g., ERPDrive): INR 15,000-50,000/month subscription, 2-6 week implementation. Includes shop-floor tracking.
  • Mid-market global ERP (SAP Business One, Dynamics 365): INR 6-15 lakh/year licence, 4-9 month implementation.
  • Standalone MES (cloud-deployed): INR 8-20 lakh setup + INR 1.5-3 lakh/month subscription. 3-6 month implementation.
  • Standalone MES (on-prem enterprise): INR 50 lakh-INR 5 crore upfront + 18-25% annual maintenance. 6-15 month implementation.
  • Bundled ERP+MES from a single vendor: INR 25-100 lakh.

Integration: the hidden cost of MES

An MES is only useful if it integrates with the ERP - otherwise you have two systems of record and reconciliation hell. The integration is rarely included in MES pricing.

Typical integration scope:

  • Work-order push from ERP to MES (every time a production order is created).
  • Production actuals pull from MES to ERP (every work-order step completion).
  • Item master sync (BOM revisions, alternate parts).
  • Operator master sync.
  • Inventory consumption reverse-feed to ERP (every operator pick).

A pragmatic decision framework

Use this if you are evaluating MES vs ERP-with-shop-floor:

  • Step 1: List your top three operational pain points. Are they about planning, accounting, GST, or about real-time machine data and SPC?
  • Step 2: If pain is planning/accounting/GST/inventory, a good manufacturing ERP solves it. Stop.
  • Step 3: If pain is real-time machine data, SPC, batch genealogy, and your scale justifies (criteria above), evaluate ERP+MES.
  • Step 4: Before buying a separate MES, ask your shortlisted ERP vendor to demo their shop-floor module on your machines and routings. You may find ERP-only is enough.
  • Step 5: If you do buy MES, budget integration cost separately and explicitly.

Frequently Asked Questions

What is the main difference between MES and ERP?

ERP (Enterprise Resource Planning) is the business-management layer - orders, inventory, accounting, GST, high-level production planning. MES (Manufacturing Execution System) is the shop-floor execution layer - real-time machine data, operator clock-in/out, statistical process control, work-order dispatch to specific machines. ERP works in weeks-to-months horizon; MES works in minutes-to-hours.

Do Indian SMEs need a separate MES?

For most Indian SMEs under INR 200 crore turnover, no. A modern manufacturing ERP like ERPDrive includes shop-floor modules (OEE, operator clock-in, work-order tracking, traceability) that cover 80% of MES functionality at 20% of the cost. A standalone MES is justified only when you need sub-second machine data, component-batch genealogy, or have 200+ operators per shift.

How much does an MES cost in India?

Indicative 2026 prices: cloud MES INR 8-20 lakh setup + INR 1.5-3 lakh/month subscription. On-premise enterprise MES INR 50 lakh-5 crore upfront + 18-25% annual maintenance. Integration with ERP adds another INR 5-15 lakh one-time + INR 50K-1 lakh/year. A bundled ERP+MES from a single vendor costs INR 25 lakh-1 crore total.

Can ERP do what MES does on the shop floor?

Modern manufacturing ERPs include shop-floor execution features that overlap heavily with MES: operator clock-in/out tied to work orders, machine signals via OPC-UA/MQTT, OEE calculation, reason-code logging, first-piece QC blocking, multi-step traceability. ERPDrive includes all of these natively. The gap with a true MES is real-time SPC, sub-second machine data, and component-level batch genealogy.

When should I implement ERP and MES together?

If you tick all five: turnover above INR 200 crore, 200+ operators per shift, customer requires component-batch traceability (automotive Tier-1, medical, aerospace), cycle times under 30 seconds, and existing PLC/sensor investment. Otherwise a strong manufacturing ERP with shop-floor modules is sufficient and avoids integration complexity.

What is the ISA-95 standard for MES?

ISA-95 (also published as IEC 62264) is the international standard that defines the hierarchy and data interfaces between business systems (Level 4 = ERP), manufacturing operations (Level 3 = MES), supervisory control (Level 2 = SCADA), basic control (Level 1 = PLC), and the physical process (Level 0). It standardizes vocabulary, data models, and information exchange between layers to make integration consistent across vendors.

Sources & References

This article cites the following primary sources. Click through for the official source documents: