MES vs ERP: The Honest Decision Framework for Indian Plant Heads
The MES vs ERP debate is usually framed as a turf war. It is not. It is a question of horizons.
ERP optimises hours, days, months. MES optimises seconds, minutes, hours. Anyone arguing that one replaces the other has either never seen both in production or is selling you one of them.
The Seven-Question Framework
- How long does it take to close production for a shift today? If > 4 hours, you have an MES gap, not an ERP gap.
- Can you compute OEE without Excel? No → MES gap.
- Are your downtime reasons categorised in a system that survives audits? No → MES gap.
- Are your dispatch errors > 2%? Yes → traceability / WMS / RFID gap, often solved as an MES module.
- Is your month-end variance analysis longer than 2 days? Yes → the gap is at the ERP / MES handshake, not in either system alone.
- Do your operators still write on paper? Yes → MES gap (paperless work instructions).
- Do your top 5 customers ask for batch-level traceability? Yes → you need MES even if your ERP is healthy.
When ERP Expansion Is Actually Right
Sometimes the answer really is "no MES needed". The signals:
- Low-velocity production (one or two SKUs per line per week).
- Highly manual processes where machine connectivity is not the bottleneck.
- Existing ERP is healthy, well-customised and integrates cleanly with quality / inventory.
- Volumes do not justify the per-plant MES capex.
The Middleware Path
For plants with a healthy ERP that simply lacks real-time shop-floor visibility, a thin integration middleware layer plus operator tablets often delivers 70% of MES value at 30% of the cost. We have shipped this pattern at multiple Tier-1 component manufacturers — ERP stays untouched, a lightweight execution layer is added, operators get tablets, and the data starts flowing.
Practitioner note
Decision rule: expand ERP for transactional gaps, build MES for execution gaps, add middleware when both systems are largely fine but do not talk to each other in real time.
Frequently asked
Can SAP do everything an MES does?
SAP DMC (Digital Manufacturing Cloud) is a real MES, but its licensing economics and 9 – 18 month implementation make it a poor fit for plants under ~1,000 crore in revenue. For smaller plants the answer is purpose-built MES integrated to SAP ECC / S/4HANA.
What about Tally?
Tally is an accounting and inventory system, not an ERP in the manufacturing sense. Use it for books, integrate it via API to a real MES for any shop-floor visibility.
Continue reading
14 min read
Manufacturing Execution Systems (MES) in India: The 2026 Practitioner’s Guide
A field guide to choosing, implementing and operating a Manufacturing Execution System in Indian plants — written from 50+ deployments across process and discrete industries.
9 min read
The 12-Week MES Implementation Playbook (Plant-by-Plant)
The exact week-by-week plan we run for MES rollouts in Indian plants. Built from 30+ deployments. No vendor-speak.
Amey Kadle
Founder & CEO, Ajinkya Technologies. 20+ years of building MES, ERP and AI systems for India’s most demanding manufacturing plants.