ERPEnterprise Resource Planning

An Enterprise Resource Planning system is the corporate backbone — the single source of truth for financial transactions, purchasing, sales, costing, planning and high-level inventory. Modern ERPs add CRM, HR, project, and analytics modules around that core. The defining trait is enterprise scope: one system holding the financial and commercial position of the whole business, integrated to a single ledger.

ERP excels at the things that happen daily, weekly or monthly at a transactional level — purchase orders, invoices, journals, sales orders, stock balances, MRP runs, period close. It is not built for the events that happen every minute on the shop floor — every dispense, every weight, every CCP check, every in-process result, every operator signature, every label print, every quarantine flag.

ERPs are GAMP 5 Category 4 systems (configured products). Their validation envelope covers transactional accuracy, financial controls, and the configuration applied at implementation. They are not validated for sub-minute operator workflows, scale-integrated dispense, or regulated-record capture at the granularity Part 11 and Part 211 require.

The ISA-95 (IEC 62264) standard describes the boundary cleanly:

ERP owns level 4. The shop-floor work — operator execution, dispense, in-process capture, batch records, traceability — lives at level 3. Pushing operator-level execution into level 4 doesn't end well: the response time isn't there, the audit-trail granularity isn't there, the regulated record structures aren't there, and the system was never validated for it.

ERPs do have shop-floor modules — production scheduling, work order management, basic shop-floor data collection. They are not designed for regulated manufacturing execution and do not satisfy 21 CFR 211/212/820, EU GMP Annex 11, or Part 11 expectations at the operator-event level. The specific gaps are:

• Sub-minute response times required by operators at a kiosk on a noisy line.
• Scale, label printer, scanner and device-bridge integration with hardware-level error handling.
• Per-weighment audit trail with photo evidence, tolerance enforcement, container ID capture, lot drill-through.
• Two-person e-signature flows for high-consequence events with Part 11 meaning strings.
• Real-time deviation routing into the QMS at the moment of an OOS event.
• Master Batch Record management with two-person approval, immutability and v+1 revision discipline (211.186).
• BMR/DHR snapshot at work-order release so the executed record is an "accurate reproduction" of the MMR (211.188).
• Sample plan execution and LIMS hand-off at the moment a sample is taken on the floor.
• Equipment status tracking — cleaned, qualified, in-use, fault — at the granularity required for cleaning-validation defence.
• Training enforcement at the kiosk that hard-blocks an under-trained operator from starting a regulated task.

V5 doesn't replace your ERP. It extends it down to operator-level execution and feeds verified production data back. The boundary is intentional, stable, and survives ERP upgrades:

The single most common ERP-related concern from regulated manufacturers: "we just spent two years and millions implementing this ERP — we cannot replace it." Right answer. You shouldn't. V5 sits next to it and closes the compliance loop on the shop floor that ERP was never built to close.

The ERP keeps its strengths (finance, planning, high-level inventory, commercial flow, executive reporting). V5 adds operator execution, regulated records, real-time traceability, electronic batch records, audit-grade controls. The customer sees one continuous workflow; the systems share the truths each owns. Crucially, the ERP validation envelope does not need to be re-opened — V5 takes responsibility for the GxP execution layer and ships its own Validation Pack.

Customers who try the alternative — pushing execution into the ERP via custom modules or third-party add-ons — typically end up in one of two failure modes: either the ERP modifications break on the next vendor upgrade, or the GxP record granularity is insufficient and the first serious audit produces 483 observations.

The patterns below are the same across every major ERP. The transport varies (REST, SOAP, file drop, message queue) but the data flow is consistent:

Quality hold flag is the underrated one. When V5 opens a deviation on a lot, that flag must propagate to ERP within seconds, not on the overnight sync, or the ERP will happily allocate held material against a sales order shipping the next morning.

Sites that try to run regulated manufacturing on ERP alone (no MES/WMS/QMS layer) typically encounter the same observations on inspection:

• No per-weighment record — the ERP captures the work-order total, not the operator-by-operator dispense events the BMR requires.
• Audit trail too coarse — ERP audit logs capture transactional events (PO posted, SO shipped) not the operator screen-by-screen actions Part 11 expects on a regulated record.
• No two-person e-signature flow on MMR approval, on conditional release, on label content changes.
• Master Batch Record held as a static document; no v+1 immutability, no two-person approval, no snapshot to the executed record.
• Quality holds applied manually in the ERP item master, with no audit trail of who held, why, and when.
• Training enforcement at the SOP-acknowledgement level, not at the kiosk-task level — under-trained operators can still start regulated tasks.
• Sample/LIMS hand-off via spreadsheet, with results re-entered manually into the ERP item master.
• Equipment status tracked verbally or on a whiteboard, with no defensible cleaned/qualified/in-use trail.

Each of those is a single observation on a 483. A site with three or four of them on its first FDA inspection is a Warning Letter candidate.

• Trying to run shop-floor execution from ERP work-order screens — slow, wrong granularity, no e-signature, no audit trail.
• Sync running daily — by the time ERP "knows" about a receipt, the line has already started the wrong material.
• Material master maintained in both systems independently — drift becomes a chronic source of errors and the team spends 20% of its time reconciling.
• No reverse flow — verified production data never feeds standard-cost variance analysis, so finance has no view of yield erosion or labour drift.
• Two separate inventory truths — book-and-bin reconciliation becomes a part-time job and the gap between ERP and the floor grows monthly.
• Quality hold not synchronised in real time — held material gets allocated and shipped, then recalled.
• ERP modifications to fit GxP — every upgrade breaks the customisation; vendor support drops to best-effort.
• Integration via overnight file drop — fine for finance, fatal for shop-floor decisions that need to happen in the next 15 minutes.

1. Treat the ERP as the financial and planning source of truth. Do not duplicate ERP master data in V5 beyond the fields V5 needs to operate.
2. Treat V5 as the operational source of truth for everything below level 4. Do not duplicate operator events back into the ERP beyond roll-ups.
3. Real-time sync for quality holds, lot status, and PO/SO state changes. Batched sync for inventory roll-ups and cost feedback.
4. Field-level ownership documented per attribute (which system writes, which reads). Reviewed annually.
5. Vendor-supplied adapters preferred over custom integration code; custom only where the adapter doesn't fit a field-level mapping.
6. Change control on both sides — an ERP item change triggers V5 re-validation only where the field affects a GxP-relevant attribute.
7. Single inventory truth at any given timestamp — agree the reconciliation cadence and own the gap as a known.

Master data is the silent killer of every ERP / shop-floor integration. Items, units of measure, suppliers, customers, locations, BOMs, employees — every one of them exists in both systems and every one of them drifts the moment the field-level ownership rules are unclear. Sites that do not write the governance rules down end up with two truths inside six months, and the reconciliation work becomes a full-time job.

The rule that works: each field has exactly one system of record, named explicitly, and one or more systems of consumption that receive a synchronised copy. The system of record can write the field; the systems of consumption can read it but not edit it. Changes propagate one direction only. When operators need to add metadata that the ERP doesn't carry (regulated attributes — sample plan, allergen group, in-process specs, equipment routing), V5 becomes the system of record for those fields, and the ERP does not see them at all.

Once the table above is signed off by ERP owners, V5 owners and QA, the integration build is straightforward — every field maps to a row, and any future field change references the table for direction and cadence. The annual review takes 90 minutes. Sites that skip the table spend several thousand hours over the system's life arguing about who broke what.

When an existing ERP is in place and V5 extends down to the floor, the validation envelope splits cleanly along the ISA-95 boundary. The ERP retains its existing validation scope (GAMP 5 Category 4 — configured product covering finance, planning, transactional accuracy). V5 takes its own validation scope (GAMP 5 Category 4 covering operator execution, regulated records, electronic signatures, audit trail). The interface between them gets its own validation artefact: an Integration Test Plan covering every field-level mapping and every direction of flow.

• ERP validation — unchanged. The ERP IQ/OQ/PQ remains in force; V5 does not re-open it.
• V5 validation — shipped with the V5 Validation Pack (URS, FS, IQ, OQ, PQ, traceability matrix, validation summary report) tailored to the customer's scope.
• Integration validation — discrete test plan covering ERP → V5 inbound flows, V5 → ERP outbound flows, error handling, retry, replay, and the quality-hold latency requirement.
• Change control — independent on each side. An ERP item-master schema change triggers V5 integration re-test only for the affected fields. A V5 regulated-metadata change does not touch the ERP at all.
• Periodic review — joint, annually. Both validation owners review the field-mapping table, the integration test results, and any drift observed in production.

The split keeps both validation owners in their lane — ERP IT does not need to learn GMP record granularity, and Quality does not need to learn financial controls. The Integration Test Plan is the only document both teams co-own, and it is short (typically 30–50 pages) because the field-mapping table already does most of the work.

The single most common integration mistake is treating every flow as real-time (which over-engineers the integration and creates fragility) or treating every flow as batched (which produces the held-material-shipped scenario). The answer depends on the consequence of latency:

Quality hold is the line that must hold (every pun intended). Everything else can degrade gracefully — a 30-minute delay on inventory roll-up is fine, a 30-minute delay on a quality hold can ship a contaminated lot.