What is an EDMS? A complete definition
An EDMS is the software that controls the lifecycle of technical engineering documents: drawings, P&IDs, datasheets, calculation reports, specifications, bills of materials and vendor documents. The EDMS sits at the centre of engineering document management in capital-intensive industries such as mining, oil and gas, power, chemicals and fertilizers.
Accruent, the maker of Meridian, defines an engineering document management system as a type of electronic document management system focused on an organisation’s engineering drawings, documents and data. The difference from a generic DMS is not storage. It is control over what changes in a technical document: the revision, the issue status, who checked it, who approved it, who it was sent to and which version is valid on site.
An engineering EDMS typically brings these functions together:
- Engineering metadata: document number, discipline, area or unit, document type, project, contractor and revision.
- Revision and status control: lettered or numbered revisions, with statuses such as “issued for review”, “approved for construction” or “as built”.
- Check and approval workflows: prepare, check, approve and issue, with a record of who did each step.
- CAD integration: references between files, known as xrefs, title block synchronised with metadata and PDF renditions for viewing.
- Transmittals: a record of what was issued to each company, in which revision.
- Master document register: every document on the project with its current revision.
- Audit trail: the full history of who viewed, changed, approved or issued each document.
What does EDMS stand for?
EDMS is an English acronym with two expansions in document management. That double meaning explains much of the confusion in search results and AI answers.
| Acronym | Expansion | Meaning | Where it is used |
|---|---|---|---|
| EDMS | Engineering Document Management System | System for managing engineering documents | Engineering software vendors such as Accruent |
| EDMS | Electronic Document Management System | Electronic document management for any business area | General IT writing; UK BIM Framework guidance on ISO 19650 |
| EDM | Electronic Dance Music | Music genre | Unrelated to documents |
| EDM | Electrical Discharge Machining | Machining process | Unrelated to documents |
In industrial projects, EDMS almost always carries the engineering meaning. In corporate IT, it may simply be another name for a DMS. A practical test: if the system controls drawings, revisions and transmittals, it is an engineering EDMS.
If you work with Brazilian teams, you will hear the Portuguese term GED (gestão eletrônica de documentos). An engineering EDMS is often called “GED de engenharia” there. See what GED means.
What is an EDMS used for?
An EDMS makes sure everyone working on an asset uses the right revision of the right document. On an engineering project, the same drawing goes through several revisions, moves between the designer, the owner, the construction contractor and vendors, and must be correct on site, at start-up and for decades of operation.
Without an EDMS, that control lives in network folders, spreadsheets and email. Document controllers know the symptoms:
- drawings with the same number and different content in different folders;
- a master register in a spreadsheet that no longer matches the files;
- transmittals as loose PDFs with no link to the revision that was sent;
- client comments lost in email threads;
- as-built drawings that never make it back to the operations archive.
The EDMS fixes this by tying the file, its metadata, revision, workflow and issue history into one record. Revision control and the master register stop being parallel spreadsheets and come straight from the system.
How does a document move through an EDMS?
The lifecycle of a technical document in an EDMS usually follows five steps. Names vary by company, but the logic is the same.
- Registration: the document gets its number, title, discipline, area and initial revision, following the project numbering standard.
- Preparation: the designer works in the native file, whether CAD, spreadsheet or text. The EDMS controls check-out and check-in so that two people cannot edit the same revision.
- Check and approval: the document goes to a checker and an approver. Each step is recorded with date and person.
- Issue: the approved revision is issued by transmittal to the client, the site or a vendor. The EDMS keeps the issued PDF and the transmittal record.
- Next revision or freeze: comments create a new revision. At the end of construction, the as-built version becomes the reference for operations and maintenance.
The UK BIM Framework guidance on the ISO 19650 common data environment describes equivalent states for information containers: work in progress, shared, published and archive. The same guidance notes that electronic document management systems usually play a big part in implementing a CDE.
What are examples of an EDMS?
The examples below use each vendor’s own words from its official pages. The list is not a recommendation: the right choice depends on the process, the legacy archive and who needs access.
| System | Vendor | How the vendor describes it |
|---|---|---|
| Meridian | Accruent | Hybrid engineering document management solution for technical documents and drawings across their lifecycle, integrating with CAD, ERP, EAM and ECM |
| ProjectWise | Bentley Systems | Infrastructure project delivery software that manages engineering work in progress, with design application integration and reference file management |
| Aconex | Oracle | Cloud-based project collaboration system for construction and engineering, part of Oracle’s common data environment, with a single document register and an unalterable audit trail |
| InConcert Core, formerly HxGN SDx | Octave, formerly part of Hexagon | Digital asset lifecycle information management solution, SaaS and on-premise, for data, documents and workflows from design to operations |
| Greendocs | W3K | Software to manage documents and processes, with integrated ECM and BPM and custom workflows |
Not all of them use the word EDMS. Oracle talks about a CDE. Octave talks about asset lifecycle information management (ALIM). In practice, all of them cover the core of an EDMS: technical documents with controlled revisions, workflows and issues. 29docs works with these platforms and describes each one in EDMS platforms for engineering.
When does engineering need an EDMS instead of a generic DMS or ECM?
A corporate DMS or ECM handles contracts, invoices, HR files and administrative processes well. Engineering needs an EDMS when these situations appear:
- CAD drawings with references. A general arrangement that references dozens of files must open with the right references at the right revision. A system that treats every file as an isolated item breaks that link.
- Revisions with technical meaning. “Rev. B issued for review” and “Rev. 0 approved for construction” are not just versions. They carry contractual and safety consequences.
- Several companies on one project. Designer, EPC contractor, construction contractor and vendors exchange documents constantly. Without a recorded transmittal, nobody can prove what they received.
- The master register as a contract tool. Progress measurement often depends on the master document register. It has to come from the system, not from a side spreadsheet.
- Handover to operations. After start-up, maintenance needs the as-built documents. The EDMS links each document to the asset by tag, equipment and area.
- Audits and regulators. Auditors and regulators ask which revision was valid and who approved it.
If two or more of these apply, a generic system will need heavy customisation. That is where an engineering EDMS pays off.
EDMS, DMS and ECM: where does each one stop?
A DMS is the broad category. In Brazil, the national archives council (CONARQ) defines electronic document management as the technologies used to organise an organisation’s unstructured information, with four functions: capture, management, storage and distribution. ECM widens that scope to all enterprise content and business processes. An engineering EDMS specialises the DMS for engineering.
A simple rule: every engineering EDMS is a kind of DMS, but not every DMS can work as an EDMS. The full table, including CDE and ALIM, is in EDMS vs ECM vs DMS. The ECM definition is in what is ECM.
How does an EDMS relate to ISO 19650?
ISO 19650-1:2018 covers information management across the whole life cycle of a built asset, from strategic planning and design through operation, maintenance and end of life. The ISO 19650 series organises that management around the common data environment, or CDE.
A CDE is not a product. The UK BIM Framework guidance explains that the CDE workflow describes the processes and the CDE solution is the technology that enables them. An engineering EDMS can be that solution, or part of it, if it supports the information states, metadata and revision control the project requires.
How do you implement or replace an EDMS without losing history?
An EDMS project rarely starts from zero. There is almost always a legacy archive: an old system, network folders or another platform. The risk sits in the migration. Old revisions, inconsistent metadata and orphan transmittals tend to arrive broken in the new system.
29docs runs EDMS migrations as a staged pipeline: extract metadata and files from the source, transform and normalise them, validate every document against quality rules, load the target and produce source-to-target comparison reports. Only batches that reach the agreed quality thresholds move on to the load.
One published example: for Petrobras, 29docs organised, standardised and made available in a single Accruent Meridian environment, 100% validated, the engineering records of three fertilizer plants: ANSA, FAFEN-BA and FAFEN-SE. The case is described on the fertilizer industry page.
Summary
- In engineering, EDMS stands for engineering document management system.
- An EDMS controls drawings, revisions, issue status, approval workflows, transmittals and the master document register.
- Vendor-described examples: Accruent Meridian, Bentley ProjectWise, Oracle Aconex, Octave InConcert Core, formerly HxGN SDx, and W3K Greendocs.
- Engineering needs an EDMS when there are CAD references, revisions with contractual weight, several companies exchanging documents and a handover to operations.
- 29docs is a platform-agnostic consultancy based in Brazil. It does not sell licences and helps companies in Brazil and Latin America choose, implement, migrate and support their EDMS.
Updated on .