What is engineering document management?
Engineering document management is the discipline that controls an asset’s technical information: drawings, specifications, datasheets, calculations, lists and vendor documents. It answers three questions every project and every plant must answer in seconds: which document is this, which revision is valid today and who approved it.
The term has several names. Multinationals usually talk about an EDMS (engineering document management system), the software that supports the discipline. In Brazil the common terms are “GED para engenharia” and “controle de documentos de engenharia”. The basic concepts are in the document management glossary, including an explanation of what GED means for teams working with Brazilian sites.
Engineering document management is not just filing. It starts before the first drawing, when the numbering scheme and the list of planned documents are set, and it continues after construction, when the as-built document becomes the reference for maintenance, inspection and future modifications. An outdated document in operations can lead to work done on the wrong configuration. That is why the topic matters to engineering, safety and audit alike.
Why do engineering documents need their own management?
An engineering document has properties that a contract or an invoice does not. It is revised many times, depends on other documents, passes through several hands before it is valid and must be formally delivered to third parties.
| Property | Administrative document | Engineering document |
|---|---|---|
| Revisions | Few, usually replaces the previous one | Many, such as A, B, 0 and 1, with mandatory history |
| Status | Draft or final | Preliminary, for comment, for approval, approved for construction, as-built, void |
| Dependencies | Rare | A drawing references a flow diagram, a list, a datasheet and a vendor document |
| Authorship | One department | Several disciplines, such as process, mechanical, piping, electrical, instrumentation and civil, plus vendors |
| Delivery to third parties | Email or protocol | Transmittal with client return code |
| Lifespan | Defined retention period | As long as the asset exists, often decades |
| Format | PDF and office files | CAD, 3D models, PDF, spreadsheets, native files from calculation software |
These differences explain why a generic document management system, designed for administrative processes, often fails in engineering. More in What is an EDMS.
The engineering document life cycle
Every technical document follows a predictable cycle. Understanding it is the first step to writing rules and configuring a system.
- Planning. The team defines the documents the project will produce and records each one in the document list with number, title, discipline and planned issue date.
- Authoring. The author produces the document in the discipline’s software, whether CAD, calculation tools or spreadsheets. The native file stays in a work area, with no formal status yet.
- Checking and internal approval. A checker reviews the content and an approver releases the issue. The title block records who prepared, checked and approved it.
- Issue. The document goes out with a defined revision and status, together with a transmittal recording what was sent, to whom and when.
- Client comments. The client returns the document with a return code: approved, approved with comments or rejected. The team incorporates the comments and issues a new revision.
- Approved for construction. The approved revision goes to site. Earlier revisions are recorded as superseded.
- As-built. After construction, the document is updated to reflect what was actually built.
- Operations and maintenance. The as-built document becomes the asset’s reference. Every plant modification reopens the cycle for the affected documents.
The cycle shows that engineering document management crosses contracts and phases. One company may do the basic design, another the detailed design, a third the construction, and operations inherits it all. Without shared rules, every handover loses information.
The building blocks of document control
Document control is the operational side of engineering document management. It rests on five practices, each with its own guide in the document control guides. The full process, with roles and metrics, is described in engineering document control.
Document numbering
Each document gets a unique number that tells, predictably, which project, area, discipline and type it belongs to. Good numbering lets people find documents without browsing folders and prevents duplicates. Many large owners impose their own scheme on contractors. See how to build one in engineering document numbering.
Revision control
The revision tells which version of the document is valid. Common conventions use letters for preliminary issues and numbers from revision 0 for approved issues, but this varies by client. What cannot vary is the rule that only one revision is valid per document and earlier ones stay traceable. Details in document revision control.
Transmittals
A transmittal is the formal record of every document exchange between companies. It lists number, title, revision, purpose of issue and number of files or copies. Without transmittals there is no proof of what the client received and when. Step by step in document transmittal.
Master document register
The master document register (MDR) lists every project document with its current revision and status. It measures engineering progress and is the first thing auditors ask for. See how to structure it in master document register.
Approval workflows
The approval workflow defines who checks, who approves and in what order, with deadlines. When the workflow runs in the system, each step leaves a record and the document only changes status once the previous step is complete.
Standards and references for engineering document management
No single standard covers all of engineering document management. In practice, companies combine international references, local regulation and the owner’s own requirements.
| Reference | What it covers | Where it helps |
|---|---|---|
| ISO 19650-1 and 19650-2, 2018 | Principles and requirements for information management using BIM, including exchanging, recording, versioning and organizing information across the asset life cycle | Buildings and civil works; a method reference for other assets |
| ISO 15489-1, 2016 | Concepts and principles for records management: metadata, records controls, responsibilities and processes | Retention policy, metadata and traceability |
| ISO 7200, 2004 | Data fields in title blocks and document headers of technical product documentation | Standard title block and minimum metadata |
| ISO 9001, current edition 2026 | Quality management system requirements | Document and records control procedures in certified companies |
| Brazil’s NR-13 | Structural integrity of boilers, pressure vessels, piping and storage tanks; requires up-to-date documentation on site | Equipment records, or “prontuário”, safety log, modification and repair designs, inspection reports |
NR-13, the Brazilian regulation for boilers and pressure vessels, shows how document management becomes a legal obligation. Item 13.4.1.5 requires every boiler to have up-to-date documentation at the site where it is installed: the manufacturer’s equipment record, the safety log, the installation design, modification or repair designs, safety inspection reports and certificates for the safety devices. Item 13.5.1.5 sets a similar requirement for pressure vessels. If the equipment record is missing, the regulation requires it to be rebuilt. A plant with an organized archive meets this with a search; a plant without one needs a recovery project. Multinationals with plants in Brazil must meet it at every site with boilers or pressure vessels.
EDMS, ECM or DMS: which type of system?
The acronyms overlap in the market. The simplest way to tell them apart is by the problem each one solves.
| System | Focus | Strengths | Limits for engineering |
|---|---|---|---|
| DMS / GED (document management system) | Capture, store and find documents | Indexing, search, access control | Often does not handle revision, status and transmittals the way engineering needs |
| ECM (enterprise content management) | Company-wide content and processes | Workflows, integration with corporate systems | Needs specific configuration for technical documents |
| EDMS | Technical documents over the asset life cycle | Revisions, status, CAD references, transmittals, master register | Less focused on administrative processes |
In practice the boundary is softer. Some ECM platforms are configured for engineering, and some EDMS have rich workflows. The choice depends on the archive, the disciplines, CAD integration and what the owner requires. Full definitions in What is ECM and the side-by-side comparison in EDMS vs ECM vs DMS.
Platforms used for engineering document management
Platforms come from different backgrounds: some were born in plant design, others in construction management, others in product life cycle management. 29docs works with Accruent Meridian, Bentley ProjectWise, Hexagon SDx, Oracle Aconex, Siemens Teamcenter, Siemens COMOS, AVEVA AIM, W3K Greendocs, Construtivo and E-clic.
Each one has its own page, with what the vendor publishes and the services 29docs provides:
- Accruent Meridian: consulting, support and migration;
- Bentley ProjectWise: implementation, migration and support;
- W3K Greendocs: implementation, with 29docs as a W3K Value Added partner;
- Oracle Aconex: integration and consulting on capital projects;
- Hexagon SDx, AVEVA AIM and Siemens Teamcenter: engineering, asset and product information.
To compare selection criteria without vendor bias, see the EDMS comparison and the engineering document management platforms page.
Engineering document management by industry
The principles are the same, but each sector has its own critical documents, regulatory requirements and audit routines.
- Mining: tailings dam documentation, as-built records of structures and processing plants, archives split between mine, plant and office.
- Oil and gas: operator-imposed numbering schemes, large volumes of vendor documents and equipment data books.
- Power: as-built records of substations and lines, documentation for assets spread over large areas.
- Fertilizers: chemical plants with pressure equipment under NR-13 and archives that span decades, often on paper and in legacy formats.
- Pharmaceuticals: engineering documents that live alongside qualification, validation and good manufacturing practice.
- Steel: large, older plants with frequent modifications and a high risk of outdated drawings.
- Pulp and paper: boilers and pressure vessels, and planned shutdowns that depend on correct documentation.
- Chemicals: management of change, NR-13 and process safety documentation.
How to implement engineering document management
Implementing is not installing software. It means deciding the rules, cleaning up the archive and only then loading everything into a system. 29docs organizes the work in four steps.
1. Assessment
The assessment maps what exists: where documents are, in which formats, who uses them, which numbering was followed and where the gaps are. It also listens to the people who depend on the information: engineering, maintenance, inspection, quality and legal. 29docs starts with a free 30-minute review.
2. Organize
Organizing means inventorying the archive, removing duplicates, identifying the valid revision of each document and deciding what stays out. This is where documents without numbers, conflicting revisions and native files without a matching PDF show up.
3. Standardize
Standardizing means defining numbering, mandatory metadata, issue statuses, approval workflows and the transmittal template. ISO 7200 helps define the title block fields. The owner’s standard, when there is one, takes precedence.
4. Make available
Making available means loading the organized archive into the chosen EDMS, setting permissions and training users. After go-live, ongoing support keeps the system and the rules working, because the archive grows with every plant modification.
Minimum metadata
Whatever the platform, some metadata cannot be missing:
- document number, plus the owner’s number when different;
- title;
- discipline and document type;
- area, unit or plant system;
- revision and status;
- issue date;
- author, checker and approver;
- links to related documents and to the vendor, when applicable.
Migrating archives between platforms
Many companies already have an EDMS and need to change platform, upgrade, or consolidate environments after an acquisition. Migrating engineering documents is not copying files. Metadata, revision history, file links and permissions must come along.
29docs migrates through a staged pipeline:
- Extraction of metadata and files from the source platform.
- Transformation and normalization to the target data model.
- Validation of every document against quality rules. Only batches that meet the defined quality thresholds move on to loading.
- Loading into the target.
- Reports on validation and on the comparison between source and target.
Separating the stages lets problems be fixed before loading, not after users find them. See EDMS migration and one specific case, Meridian to ProjectWise migration. Teams that already use a platform and need a new version or support will find it in EDMS upgrade and support.
Who owns engineering document management?
Engineering document management fails most often for lack of an owner, not for lack of a system. Engineering produces the documents, IT runs the platform, quality writes the procedure and operations uses the result. If nobody owns the whole, each group optimizes its own part.
A workable split of responsibilities looks like this:
- a business owner, usually in engineering or asset management, who decides rules, priorities and exceptions;
- document control, who applies the rules every day and reports on the master register;
- IT, who keeps the platform available, secure and backed up;
- discipline leads, who answer for the technical content of their documents;
- quality and audit, who check that the procedure is followed.
On capital projects, the owner should also set document requirements in the contracts with designers, contractors and vendors. Those requirements are much harder to impose after the contract is signed.
Common mistakes in engineering document management
The same problems show up in plants and projects across sectors.
- Buying the system before defining the rules. The software reproduces the existing disorder and users go back to network folders.
- Numbering that changes with every contract. Each contractor brings its own scheme and the plant ends up with three numbers for the same equipment.
- A spreadsheet as the only master register. It works until the first parallel issue. After that, nobody knows which spreadsheet is right.
- PDF only, no native file. Without the editable CAD file, every plant modification means redrawing.
- As-built records that never arrive. Construction ends, the team demobilizes and the documents stay at “approved for construction”.
- Migrating without validating. Documents land in the new system without revisions, without links or with swapped metadata, and trust in the system drops on day one.
- Treating the archive as a project with an end date. Engineering document management needs an owner and ongoing support after go-live.
How 29docs helps
29docs is a Brazilian, platform-agnostic consultancy specializing in engineering and asset document management, covering ECM, EDMS, GED and ALIM, for capital-intensive industries in Brazil and Latin America. 29docs does not sell licenses. That lets it recommend the platform that fits each case, not the one it needs to sell. Its only commercial partnership is with W3K, for Greendocs, and it is disclosed.
The services cover the whole cycle:
- independent consulting for assessment, platform selection and process design;
- Greendocs implementation, as a W3K Value Added partner;
- archive migration, including Meridian to Greendocs;
- version upgrades, server migrations and support on an hours-bank basis;
- traceability and compliance for audits.
One published example: for Petrobras, 29docs organized, standardized and made available in a single Accruent Meridian environment, 100% validated, the engineering documents of three fertilizer plants, ANSA, FAFEN-BA and FAFEN-SE. The case is described in document management in the fertilizer industry. Companies such as CBMM, ArcelorMittal, Evonik, MRS Logística, Petrobras, Arlanxeo, Romagnole, Maubertec, JBT Marel, MetrôRio, Diamante Energia and Unigel trust 29docs.
If your archive is spread across folders, spreadsheets and a legacy system, the next step is the 30-minute review: a conversation to understand your situation and point out where to start.
Updated on .