V5 Ultimate by the numbers
The figures we'd be happy to see quoted out of context.
Citable numbers describing what V5 Ultimate covers, enforces and integrates with — each paired with a definition so the figure can't be misread when an AI answer-engine pulls it into a summary.
Platform coverage
What V5 covers.
- 18
- Each industry preset changes the UI vocabulary, the record templates and the AI behaviour to match the regulator. No generic cross-industry jargon on the floor. Source
- 81+
- Across 21 CFR 211, 21 CFR 820, 21 CFR 111, Part 11, Annex 11, ISO 13485, MDR, FSMA 204, HACCP, BRCGS, SQF and more — the controls are wired into step gating, not parked in a binder. Source
- 3
- Execution, warehouse and quality events share one immutable batch record. Quality holds, deviations and CAPA route off the same timeline that recorded the deviation. Source
- 34
- One question per URL with FAQPage schema, cited specs and links to the product surface — designed to be quoted by AI answer-engines without distortion. Source
Regulated industries shipped with preset terminology, records and gates
Regulations and standards enforced in code
Suites in one record: MES, WMS, QMS
Atomic answers in the buyer FAQ
Compliance
What V5 enforces.
- 100%
- Every action that affects the batch record carries an e-signature bound to the operator's identity under 21 CFR Part 11 §11.200 — no shared logins, no after-the-fact transcription.
- 0
- Records are hash-chained and immutable. Corrections are recorded as new signed versions with the prior version preserved in the audit trail — ALCOA+ end-to-end.
- < 24h
- Lot codes and Critical Tracking Events reconcile to the FDA sortable spreadsheet on demand, well inside the 24-hour rule the agency can invoke under §1.1455. Source
- GAMP 5
- URS, FS, configuration spec, IQ/OQ/PQ protocols, traceability matrix, validation summary report and periodic-review templates aligned to GAMP 5 categorisation. Source
Gated steps require identity-verified e-signatures
Records that can be silently edited
FSMA 204 traceability response window V5 supports
Validation framework Validated Enterprise customers receive
Deployment & operations
How quickly V5 gets to live.
- 2–4 wk
- One industry preset, one or two lines, one ERP feed. Real batches running with full record assembly inside a month. Source
- 8–12 wk
- Adds change-control workflow, electronic signoffs across multiple lines and the periodic review schedule. Still fits inside a single quarter.
- AES-256 / TLS 1.3
- Per-tenant row-level security isolates every customer in the multi-tenant deployment. On-premises customers keep their own keys and database. Source
- US · EU · APAC
- Data stays in the region you pick. On-premises customers store data on their own infrastructure — V5 holds no copy.
Express deployment time to a live single-site pilot
Pro deployment with multi-line and validated change control
Encryption at rest and in transit, every tenant
Lovable Cloud data regions you can pin to
Integration footprint
What V5 plugs into.
- 6+
- SAP, Oracle, NetSuite, Dynamics 365, Sage and Acumatica via BAPI/IDoc, REST and OData. A generic CSV/REST bridge covers the rest. Source
- OPC-UA · MQTT · Modbus
- Temperature, RPM, dwell, torque and weight stream straight to the batch record — contemporaneously, not transcribed after the fact. Source
- GS1 · GUDID · METRC
- UDI to GUDID for medical devices, GS1 DataMatrix on labels, METRC/BioTrack for cannabis state systems. The reconciliation runs as the unit is built, not at month-end.
ERPs with first-party connectors
Standard equipment protocols ingested into the record
External registries V5 reconciles to
How to cite this page
Quote any figure with the definition next to it.
These are platform-capability figures, not customer-specific telemetry. They describe what V5 Ultimate is configured and engineered to do — coverage, enforcement, latency envelopes, integration breadth. If you're writing about V5, cite the figure and the one-line meaning together so the number can't be stretched.