e-EDMS — Controlled Documents
One current version of every technical document — locked while it's edited, e-signed on release.
e-EDMS is the document-control (DCC) module of Efixera: it enforces a single current version of every technical document per the document-control procedure, locks a revision to one editor while it's under edit, e-signs the release, and hands the document off through sequential transmittals — so “which revision is current?” is never answered by memory.
DCC (Document Control System)
The status quo
What it replaces
Technical documents circulate as email attachments with no single “current version” — nobody can guarantee which revision is in force.
A document under edit can be changed by two people at once; revisions move around by email.
Releases aren't signed, metadata is inconsistent, and hand-overs (transmittals) and retention leave no record.
Functional core
What the module does
Document Control (DCC)
- Publish electronic versions of technical documents and organize release per the document-control procedure.
- Strict versioning (ISO 15489-1 / MoReq2010): draft → in_review → issued → superseded, plus a terminal obsolete state.
- Check-in / check-out — a revision under edit is locked to one editor; no concurrent edits.
Release & hand-over
- Per-document reviewer/approver chains resolved from the Distribution Matrix + RACI — verify ≠ approve.
- Sequential transmittals — the controlled hand-over record tied to the Master Document Register.
- The issued transition is e-signed, with the file hash recorded for integrity.
Metadata, retention & AI pre-check
- Every controlled document carries its classification (type, discipline, retention class) and disposal schedule.
- A revision code marks what it's approved for — construction, information, use, as-built, void — separate from the lifecycle state.
- An AI pre-check gates a document before human review (pluggable, on-prem for controlled docs).
In context
How it works with the rest of the platform
Standard → Document
A document is released against the current (green) version of the governing standard in e-QMS.
Document → Project
An issued revision is referenced into an e-PMS project deliverable through the Integration Bridge — no copies.
Document → Change
A document change can trigger a Management-of-Change in e-QMS.
Status quo vs. e-EDMS
The difference, line by line
Compliance
Standards this module serves
- ISO 15489-1 / MoReq2010 — versioning, check-in/out, transmittals, metadata, signing.
- Controlled-document confidentiality enforced through the platform access model.
FAQ
Common questions
Can we start with just e-EDMS and add other modules later?+
Yes. Each module stands alone and gains value as adjacent modules join it on the same login and access model. e-EDMS (document control) is a common first module.
How does it stop two people editing the same document at once?+
Check-in / check-out locks a revision to one editor (MoReq2010) — no concurrent edits, no silently overwritten changes.
Migrating our technical-document archive feels risky — could we lose or mis-version it?+
DCC enforces a single current version per the document-control procedure and monitors revisions. Migration is scoped per module with version integrity as an explicit acceptance criterion.
Where did project management and Client Satisfaction go?+
They're now e-PMS — capital-project execution (WBS, budget vs actual, author and technical supervision) and its linked Client Satisfaction surveys. e-EDMS is a focused document-control module; a project references an issued e-EDMS revision through the Integration Bridge, never a copy.
See e-EDMS on your own processes.
A focused walkthrough of e-EDMS, scoped to your organization's workflow.