Admin → All modules
Identity & licensing
SSO, roles, sites, and offline licenses flow into DMS, LMS, QMS, BRM, AuditLens, Reporting, and Nova AI.
Suite integrations
Native interlocks. Not brittle middleware.
Novaqis products share identity, licensing, and audit from day one. Manufacturing, documents, training, and quality events connect through native interlocks—not fragile custom interfaces that break at every upgrade.
How modules connect
Integration map
Each link below is a first-class product capability—not a custom project left to your SI after go-live.
DMS → BRM
Controlled-copy issuance
Issuance token verification and batch evidence archive keep EBR tied to governed content.
LMS → BRM
Qualification gate
Step execution checks training qualification before the operator can proceed.
DMS → LMS
Effective-event retraining
SOP release triggers curricula and training gates on the same identity model.
QMS → DMS / LMS
Evidence & impact
Deviations and CAPA link to documents and competency without shadow spreadsheets.
Deep dive
Integration pillars
Batch execution
BCH-2026-0142 · Tablet Blend A
LMS: QualifiedDMS copy: CC-88421
Platform fabric
Every module plugs into the same control plane so you validate one governance story.
- Novaqis Admin: organizations, sites, users, roles, SSO, and product licensing
- ES256 offline license verification—no mandatory phone-home for day-to-day operation
- ALCOA+ entity audit trails with a consistent vocabulary across modules
- Deploy on-premises or in your cloud behind your reverse proxy
BRM ↔ DMS
Electronic batch records stay bound to controlled documents—not a parallel paper pack.
- Verify DMS issuance tokens and controlled-copy numbers before a batch can run
- Mark issuance tokens used when execution starts—prevent reuse
- Archive batch execution evidence back to DMS for the controlled-document story
- Operators and QA see one chain from approved MFR/SOP through floor execution
BRM ↔ LMS
Manufacturing steps enforce competency—not informal floor checklists.
- Qualification verify before operators execute manufacturing steps
- Training evidence from LMS on the same identity as the batch record
- Fewer reconciliation gaps between “who was trained” and “who signed the step”
- Policy-aligned gates that auditors can follow without swivel-chair exports
DMS ↔ LMS
When controlled documents become effective, competency follows automatically.
- Document-effective events drive retraining assignments
- Training gates can block secure view, print, or issuance until qualification is verified
- Investigators see training status beside document versions
- Attention monitoring and assessments remain on the same SSO and audit fabric
QMS ↔ DMS / LMS
Quality events close with evidence—not orphan tickets in a separate tracker.
- Suite-native links from deviations and CAPA to governed documents
- Training impact and competency status visible beside quality records
- Configuration Studio workflows on shared roles and sites from Admin
- One inspection narrative across quality, documents, and training
Nova AI across the suite
Assistance that respects your access rules—never a back door around permissions.
- Embedded in Admin, DMS, LMS, QMS, and BRM where enabled
- Document assist, learner checkpoints, recipe/MFR assist themes, and operational summaries
- Permission-scoped and tenancy-aware with dedicated AI audit logging
- Deployable inside your perimeter alongside the rest of the stack
Why it matters
One stack vs. point-to-point tax
Brittle point-to-point integrations
- Separate identity stores per product
- Custom interfaces that break on upgrade
- Manual reconciliation at inspection
- Repeated validation for every connector
Native suite interlocks
- One Admin control plane
- Interlocks ship with the products
- Shared ALCOA+ audit vocabulary
- One platform validation narrative