How it fits together.
V5 Ultimate is the system of record on the floor: MES, QMS, WMS, LIMS, eDHR/eBR and document control in one platform — the lab is native, not a bolt-on. Your ERP stays the system of record for finance, BI keeps the numbers, lab instruments and shop-floor devices land signed evidence straight into the batch record. This page shows the boundary, the direction of every sync, and the three scenarios buyers ask about most.
- One platform: MES · QMS · WMS · LIMS · eDHR · Docs
- Signed webhooks + audit-grade event log
- Every action e-signed at the source
- Devices land straight into the batch record
Data in motion — MES, QMS, WMS ↔ ERP, LIMS, BI, devices
The V5 Ultimate core sits between the enterprise stack (ERP, LIMS, BI) and the physical floor (scales, scanners, printers, kiosks, PLCs). Every packet on the diagram is a real payload that flows over signed webhooks or the event log.
Motion pauses automatically for viewers with reduced-motion preferences.
The boundary between ERP and V5, made explicit
The single biggest question in a two-system stack is which system is right when they disagree? V5 is authoritative for anything that happens on the floor or in the QMS. ERP is authoritative for anything that hits the general ledger. Everything else is a sync in a known direction.
| Object | In ERP | In V5 Ultimate | Direction of sync |
|---|---|---|---|
| Item / SKU master | System of record | Read + local batch attrs | ERP → V5 |
| Bill of materials (BOM) | Commercial BOM | Manufacturing formula (MBR) | ERP → V5 · V5 owns process detail |
| Suppliers & customers | System of record | Read + certifications / CoA | ERP → V5 |
| Purchase order | System of record | Receives against PO | ERP → V5 |
| Goods receipt / lot | Financial receipt | Quality-gated receipt | V5 → ERP |
| Work / production order | Demand & cost | Execution + electronic record | ERP → V5 · V5 → ERP on close |
| Inventory movements | Ledger | Physical movements + kiosk | V5 → ERP |
| Finished-goods release | Available to promise | QA release + genealogy | V5 → ERP |
| SOPs, specs, change control | — | System of record (Docs) | V5 owns |
| Deviations, CAPA, audits | — | System of record (QMS) | V5 owns |
| Training records | — | System of record | V5 owns |
| Lab results (HPLC, GC, KF…) | — | Native LIMS captures result | Instrument → V5 |
| Device signals (scan, weight, sensor) | — | Signed on capture | Device → V5 |
| BMR / DHR (report) | — | Generated from signed events | V5 output · PDF/A + signed XML |
| CoA (report) | — | Generated from LIMS results | V5 output |
| Audit-trail export | — | Part 11 / Annex 11 export | V5 output |
| GL / invoicing | System of record | — | ERP owns |
How the diagram plays out in real life
Receive raw material
- 1ERP sends the PO to V5.
- 2Receiver scans the pallet at the dock — V5 creates a lot with license-plate.
- 3V5 blocks the lot from production until identity test + QA release.
- 4On release, V5 posts the financial receipt back to ERP.
Run a batch
- 1V5 snapshots the approved MBR at work-order release (immutable).
- 2Operators clock onto steps at the kiosk; scales, scanners and printers stream signed evidence.
- 3In-process checks route deviations straight to QMS with the lot / step / operator attached.
- 4The batch record assembles in real time — no paper, no rekey.
Release finished goods
- 1QA reviews the eBR / eDHR by exception in Auditor Mode.
- 2On release, V5 posts the finished-goods receipt and consumption to ERP.
- 3V5 pushes lot + serial genealogy to the BI warehouse (signed event log).
- 4Recall scope is one query — API → bulk → bottle, in seconds.
How the floor plugs in
Scales & balances
Serial / USB / Ethernet capture straight into dispense steps, with tolerance bands and two-person sign-off.
Scanners & wearables
1D/2D symbologies including GS1 · UDI · SSCC. Ring scanners, tablets and Zebra / Honeywell handhelds.
Label & doc printers
Zebra / SATO / Datamax templates driven from V5 label templates — GS1-128, UDI, DPM, thermal & laser.
PLC / OPC-UA
Read machine state, cycle counts, temperature and setpoints. Alarms feed the deviation register automatically.
Sensors & IoT
Cold-chain probes, environmental monitoring, particle counters — signed telemetry into the batch record.
Kiosk / MDM
Locked-down Android and Windows kiosks. Offline-tolerant with queued signed transactions on reconnect.
What each adjacent system contributes
LIMS is native to V5 Ultimate — sampling plans, test methods, specifications, stability, CoA generation and release gating all live inside the platform against the batch record. External lab instruments feed that native LIMS.
Lab instruments
HPLC, GC, dissolution, Karl Fischer, titrators and balances stream results into V5's native LIMS against the sampled lot — no rekey, no shadow spreadsheets. Empower and Chromeleon integrate at the data-system level.
Empower · Chromeleon · OpenLab · Mettler · Sartorius
BI / data warehouse
Every state change writes to a signed event log. Feed Snowflake, BigQuery or a lake, then visualise OEE, yield, right-first-time and CAPA cycle time in Power BI or Tableau.
Power BI · Tableau · Snowflake · BigQuery
ERP
ERP owns items, POs and the ledger; V5 owns the batch and the floor. Reconciliation is real-time, not nightly, and every posting carries the V5 event ID it came from.
NetSuite · SAP Business One · Dynamics · QuickBooks · Xero
Three deployment shapes, one architecture
SaaS (multi-tenant)
Fastest to start. Same integration surface, same event log. Not offered to customers under formal computer-system-validation obligations.
See Live in 7 daysPrivate cloud (single-tenant)
Default for validated customers. Dedicated tenant, IQ/OQ/PQ per version, customer-instigated updates.
Validation & assessmentOn-premises
Supported where customer infrastructure meets or exceeds the published minimum specification. Same platform, same connectors, same event log.
On-prem specificationWant this drawn against your stack?
Share the systems you already run — ERP, LIMS, BI, device fleet — and we'll return a one-page architecture with the boundary, sync directions and integration effort marked up for your plant.