MES vs. ERP for Regulated MedTech Manufacturing

Why the Question Matters

Medical device manufacturers routinely deploy a single enterprise system — typically an ERP — and attempt to use it for both business operations (orders, inventory, finance) and production floor management (work orders, batch records, in-process inspection). The ERP can be configured to handle some production data, but the configuration consistently breaks down at three audit-relevant points:

1. Electronic Device History Record (eDHR) granularity. ERPs typically capture order-level and shipment-level data. eDHRs need step-level data with operator identification per step.

2. Real-time process parameter capture. Manufacturing process validation requires capturing actual process parameters (temperature, pressure, time) per unit, often at multiple points per unit. ERPs capture aggregate batch data, not per-unit telemetry.

3. In-process non-conformance routing. When a unit fails an in-process inspection on the floor, the non-conformance must route to disposition in real time. ERPs typically batch non-conformances for QA review hours or days later.

These gaps are not theoretical. They are routine findings in MDSAP, KGMP, and FDA inspections.

What an ERP Does Well

For clarity, the value of ERP in a medical device manufacturing business is real and substantial. ERPs handle:

• Sales order management and customer relationships
• Procurement and supplier ledger
• Inventory accounting (financial and physical)
• Production planning at the work-order level
• Materials requirements planning (MRP)
• Financial accounting and reporting
• Shipping and logistics coordination
• Multi-site consolidated reporting

For these activities, ERP is the right system and a well-deployed ERP carries significant operational benefit.

The question is not "ERP or MES" — it is "what specifically does each system do, and how do they integrate?"

What an MES Does That ERP Cannot

An MES is purpose-built for the production floor. Its core capabilities:

Electronic Device History Record (eDHR)

The MES captures, for every produced unit:

• Operator identity per step (linked to training records)
• Timestamp per step (UTC and local)
• Equipment ID per step (linked to calibration records)
• Component lot numbers consumed per step (with consumed quantity)
• Process parameter values measured per step
• In-process inspection results per step (pass/fail with measurements)
• Deviations recorded per step (with operator description and supervisor approval)
• Final disposition (release, hold, scrap, rework)

The eDHR is the per-unit manufacturing record. For ISO 13485, FDA 21 CFR 820, and KGMP, this record must be retrievable for the device's full retention period (typically 10+ years post-EOL).

Real-Time Work Instruction Display

The MES displays the latest-approved work instructions to the operator at the moment they perform the work. Critical properties:

• The instructions displayed are current — not last week's version, not the version the operator printed two weeks ago.
• Sign-off is required to advance — the operator cannot skip steps.
• Work instructions integrate with the eDHR — the act of confirming completion creates the eDHR record.

ERPs cannot do this. They can hold work order metadata, but they cannot deliver step-level work instructions with real-time approval status.

In-Process Inspection and Control

MES enforces inspection at the points and frequencies defined by the manufacturing process validation:

• Mandatory inspection steps cannot be bypassed.
• Inspection results integrate with the eDHR.
• Out-of-specification results trigger non-conformance routing in real time.
• Statistical process control (SPC) is calculated continuously as data is captured.

Genealogy and Traceability

For every shipped serial number, MES can produce the full traceability trace within minutes:

• Every component lot consumed
• Every operator who touched the unit
• Every machine the unit passed through
• Every inspection result captured
• Every process parameter value recorded

ERPs can produce batch-level genealogy but not unit-level genealogy in the depth required for KGMP/FDA inspection.

How They Integrate

A correctly architected MES + ERP stack has clear data flows:

ERP  ──────►  MES
   (work orders, materials availability, customer order priority)

MES  ──────►  ERP
   (production completion, materials consumption, scrap, finished goods receipt)

PLM  ──────►  MES
   (approved BOM, current work instructions, specifications)

MES  ──────►  eQMS
   (non-conformances, in-process trend data, eDHR for review)

eQMS ──────► MES
   (CAPA-driven work instruction updates via PLM)

The systems are distinct but tightly integrated. None of them is a "system of record" for everything; each is the system of record for what it does well.

Cost Comparison

A common objection to MES deployment: cost. The comparison is not as one-sided as it appears.

ERP-only with manual eDHR (typical starting state):

• ERP license: ongoing
• Manual eDHR labor: per-unit operator time + QA review time
• Audit finding remediation: periodic, can be 6-figure remediation projects
• Manual record search during recall or investigation: 4–40 hours per investigation
• Estimated all-in: high variable cost, escalating with volume

ERP + MES:

• ERP license: same
• MES license: typically $50K–$500K depending on platform and scope
• MES implementation: 6–18 months
• Reduced per-unit operator time, reduced QA review time, fewer audit findings
• Estimated all-in: high one-time + lower variable cost, leveling with volume

The crossover point — where ERP+MES becomes cheaper than ERP-only — depends on production volume, audit frequency, and product complexity. For mid-size medical device manufacturers producing more than 10,000 units/year of Class II products, the crossover is typically in year 2–3 post-MES deployment.

When MES Deployment Is Premature

MES deployment is not the right answer in every situation. It is premature when:

• Production volume is below 1,000 units/year (manual records are cheaper at this scale)
• Product is in pre-launch with unstable processes (validate the process first, then automate)
• The QMS itself is immature (deploying MES on top of broken procedures amplifies the procedure problems)
• The PLM is not yet authoritative (MES depends on PLM as the source of work instructions; if PLM is unreliable, MES inherits the unreliability)

The right sequence is generally: QMS → PLM → MES. Skipping ahead causes integration pain.

When MES Deployment Is Overdue

Conversely, three signals suggest MES is overdue:

1. Most recent audit had a finding related to eDHR completeness. This is the most common direct signal.
2. Production volume is doubling year-over-year and manual record-keeping is straining. The cost of keeping up manually escalates before the visible failures.
3. Multi-site manufacturing is being established and per-site procedures are diverging. MES provides a unified production floor system across sites; without it, sites drift apart.

Korean Manufacturing Specifics

For manufacturers building or extending Korean manufacturing operations, MES selection has specific KGMP considerations:

• The MES must support Korean-language operator interfaces if the production floor is Korean-staffed.
• KGMP auditors specifically check eDHR completeness; MES-generated eDHRs reliably pass this check, manual records often do not.
• KGMP-compatible validation packages for MES platforms exist; vendors with Korean medical device customers can produce these. Vendors without Korean customer base often cannot.
• The MES must integrate with the KLH's import-record system for end-to-end traceability from Korean import through Korean distribution.

What This Has to Do with PLM

A note: MES depends on PLM for current work instructions and BOM. A weak PLM upstream means MES inherits stale or inconsistent work instructions. Many MES deployments stall not because of MES issues but because the upstream PLM cannot deliver authoritative content. Manufacturers planning MES deployment should evaluate PLM readiness first.

Where Leanabl Plugs In

The Platform MES service runs MES platform selection and deployment for medical device manufacturers. The upstream Platform PLM work establishes the design source-of-truth that feeds MES. For the full eQMS infrastructure that integrates MES, PLM, and quality records, Platform eQMS and the eQMS service together cover the stack. For Korean manufacturing specifically, the platform work integrates with Korea QMS Foundation.