Choosing MES and PLM Platforms for Medical Device Manufacturing

The Regulated-vs-General Trap

Most medical device manufacturers start with a general-purpose ERP — SAP, Oracle, Microsoft Dynamics, Odoo — because the company existed before it became regulated, or because the founders came from non-regulated industries. The ERP handles inventory, procurement, and finance well. It does not handle the traceability, electronic records, and design-control linkage that ISO 13485, FDA 21 CFR Part 820, and KGMP require.

The gap is typically filled with three patches: manual records, spreadsheets, and document control systems bolted on the side. The patches work for a while. They fail predictably at three inflection points:

First MDSAP or KGMP audit — the auditor traces a serial number from finished goods to lot disposition to component supplier and finds discrepancies between systems.
First design change post-launch — the change cascades through Bill of Materials, work instructions, training records, and validation files, and the spreadsheet-based change control loses fidelity.
First scale event — production volume doubles and the manual records cannot keep pace with traceability requirements.

At each inflection, the cost of fixing the patchwork architecture exceeds the cost of having selected proper MES and PLM platforms upfront.

What MES Solves That ERP Does Not

A Manufacturing Execution System (MES) runs the production floor — sequencing work orders, capturing operator actions, recording machine data, enforcing process parameters, and producing electronic device history records (DHRs). The MES integrates with ERP (for materials and orders) and PLM (for the latest-approved design), but its specific job is the regulated electronic record of "what happened on the floor for this lot."

For ISO 13485 and KGMP, MES specifically provides:

Electronic Device History Record (eDHR) — every manufacturing step, recorded as the operator performs it, with sign-offs and timestamps.
In-process inspection records — pass/fail data captured at each inspection point, with operator identification.
Non-conformance routing — when a step fails, automatic routing to the disposition workflow (rework, scrap, accept-as-is, return to vendor).
Effective version control — the work instructions in front of the operator are always the latest approved version from PLM.
Genealogy — every component lot, every operator, every machine, every parameter tied to the finished serial.

A general ERP captures the what was ordered and what was shipped. The MES captures the what was actually built.

What PLM Solves That Document Control Does Not

A Product Lifecycle Management (PLM) system manages the device design across its full lifecycle — design inputs, design outputs, change history, BOM versions, supplier-controlled parts, and the linkage to clinical and risk documentation.

Document control systems (Veeva, MasterControl, Greenlight Guru) handle documents. PLM handles engineering objects. A BOM is not a document; it is a structured object with version history, item relationships, supplier links, and impact analysis. Forcing a BOM into a document control system flattens it into a PDF or spreadsheet, losing the structure that makes change impact analysis possible.

For medical device manufacturers, PLM specifically provides:

Version-controlled BOM with explosion across configurations and effectivity dates.
Design history traceability — from user need to design input to verification evidence to validation result, linked at the object level.
Change impact analysis — when a component changes, the system identifies every affected SKU, document, and validation report.
Supplier component management — controlled parts library tied to approved supplier lists and quality records.
Regulatory file generation — the PLM can produce the structured technical file content for FDA, EU MDR, and MFDS submissions from the same authoritative source.

How They Fit Together

A working medical device platform stack looks like:

PLM (design source of truth)
   │
   │ approved BOM, work instructions, specifications
   ▼
MES (execution and electronic record)
   │
   │ eDHR, in-process data, non-conformances
   ▼
eQMS (quality system, CAPAs, audits, document control)
   ▲
   │ corrections, design changes
   │
ERP (orders, inventory, finance, supplier ledger)

The eQMS sits at the center of quality records — pulling from MES, feeding back to PLM for design changes, integrated with ERP for supplier ledger.

Selection Criteria for Medical Device Sites

A short selection checklist when evaluating MES or PLM platforms:

Must-haves:

Validated for FDA 21 CFR Part 11 electronic records and signatures
Audit trail at the field level (not just record level)
Role-based access with documented qualification records
Native integration with at least one of: Veeva, MasterControl, ETQ for eQMS bridge
Support for both serial-level and lot-level traceability
Multi-site configuration (most MedTech manufacturers eventually have two or more sites)

Strong nice-to-haves:

Pre-built KGMP-compliant configuration (some MES vendors offer Korea-specific deployment templates)
Native multi-language support (for Korean, Japanese, Chinese deployments)
Open API for integration with custom validation systems
Migration tooling from common starting points (Solidworks PDM, Arena, etc.)

Red flags:

Vendor advertises "we work for medical devices" but has no Class II/III customers
No documented validation evidence (IQ/OQ/PQ packages)
Closed proprietary file format with limited export
No support for multi-site or multi-language

The Korean Manufacturing Implication

For manufacturers building or moving manufacturing to Korea (or extending Korean operations), MES and PLM choices have specific KGMP implications:

MES eDHR must support Korean-language operator interfaces if the production floor is Korean-staffed.
PLM-generated technical files must be capable of producing the Korean STED-format documentation, not just FDA/EU formats.
Validation evidence for the MES and PLM platforms themselves must be available for the KGMP audit. Vendors with strong FDA validation packages typically can produce KGMP-compatible evidence; vendors strong only in EU compliance often cannot.

Manufacturers that deploy validated MES and PLM platforms specifically with KGMP scope in mind report meaningfully shorter KGMP audit cycles and fewer findings.

Practical Migration Path

Manufacturers rarely deploy MES, PLM, and eQMS all at once. A workable sequence:

Phase 1: PLM first. The design system underpins everything. A clean PLM with accurate BOM and design history makes everything downstream cleaner.

Phase 2: eQMS in parallel. Quality records (CAPAs, complaints, audits) are independent of production volume. eQMS deployment can be done before MES rollout.

Phase 3: MES on production lines. Roll out MES line-by-line, not all at once. Start with the highest-volume or highest-risk production line. Use early lessons to refine the rollout for subsequent lines.

Phase 4: ERP integration. Once MES and PLM are stable, the ERP integration (for materials, costing, shipping) is the cleanup phase.

Total program is typically 18–36 months for a mid-size medical device manufacturer.

Where Leanabl Plugs In

The Platform PLM, Platform MES, and Platform eQMS services run platform selection, configuration, and validation for medical device manufacturers. For deployments specifically scoped to support Korean KGMP and MFDS operations, the platform work integrates with Korea QMS Foundation and KGMP Certification.