Book a demo
Login
On a large offshore development or refinery expansion, it is not unusual to have 200,000 engineering documents in circulation at peak construction — drawings, datasheets, vendor manuals, inspection records, commissioning certificates. Dozens of contractors are producing, reviewing, and revising documents simultaneously. The owner-operator needs a complete, verified, as-built set at handover.
This is the fundamental problem that engineering document management exists to solve. Not document storage — document control. And the distinction matters enormously on capital projects in oil and gas, energy, chemicals, and utilities.
Generic document management — SharePoint, Google Drive, file servers — is designed for business documents: contracts, HR files, procurement records. The documents are mostly static, version changes are infrequent, and the audience is internal staff working within a single organisation.
Engineering document management on a capital project is categorically different. Documents are produced by dozens of external contractors, each with their own numbering conventions. Every drawing and datasheet goes through multiple formal revision cycles — from issued-for-review to issued-for-construction to as-built — and each revision must be controlled, distributed, and acknowledged. Documents must be traceable not just to a project, but to the specific physical equipment or tag they describe. And at the end of a project, every required document must be collected, verified, and handed over to the operator in a structured, usable form.
An engineering document management system (EDMS) is the active control layer over engineering documents throughout a project and asset lifecycle. For more detail on the definition, see our Engineering Document Management System (EDMS) glossary entry. This guide focuses on how it works in practice — and why it matters.
The MDRL is the foundation of engineering document control. It defines every document that must be produced, who is responsible for producing it, and what its required status is at each project milestone. Every contractor's deliverable is tracked against the MDRL, giving the project team a live picture of document progress across the full scope. Without an MDRL — enforced through an EDMS — document completeness becomes a matter of estimation rather than fact.
Transmittals are the controlled mechanism for sending documents between parties. Every transmittal has a unique number, a list of documents included, a reason for issue code, and a required response. When a contractor submits a drawing for review, the EDMS logs the transmittal, routes it to the reviewers, tracks comments, and records the return transmittal. This creates an unbroken audit trail of who sent what, when, and what the response was. On projects with multiple EPCs and subcontractors, this audit trail is a contractual and regulatory requirement.
Tag and equipment linking distinguishes a purpose-built EDMS from basic document storage. In an engineering environment, every document belongs to one or more physical assets — a pump datasheet belongs to a specific tag, a piping isometric belongs to a specific line number, a vendor manual belongs to a specific equipment item. When documents are linked to tags at the point of ingestion, the project team can always answer the question: for this piece of equipment, do we have all required documents, at the right revision, with approved status? This is the only way to measure handover completeness at the asset level.
Engineering revision coding follows formal conventions — alphabetic for design phases (A, B, C), numeric for construction (0, 1, 2) — that signal where a document is in its lifecycle. An EDMS enforces this structure, prevents out-of-sequence revisions, and maintains the full revision history for every document. This is essential for audit purposes, for demonstrating regulatory compliance, and for ensuring that construction teams are always working from the correct, current issue.
EPCs and owner-operators use an EDMS differently, and a capable system must support both perspectives on the same project.
An EPC is producing and submitting documents. Their primary requirements are contractor portal access, transmittal submission and tracking, comment management, and the ability to produce periodic status reports against the MDRL. The EPC needs to demonstrate progress to the owner-operator, manage review responses efficiently, and ultimately produce a complete, approved handover package. An EDMS reduces the administrative overhead of document control — which on a major project can represent a significant proportion of total project cost — and gives the EPC a defensible record of every deliverable submitted.
An owner-operator is receiving and approving documents from multiple sources simultaneously. They need a controlled inbox — a structured way to receive transmittals from EPCs, contractors, and suppliers, route documents for technical review, track approval status, and accumulate the asset record. The owner-operator also needs to be able to challenge completeness at any point: which documents are missing, which are at the wrong revision, and which have not yet been approved. At handover, they need a verified, structured set of documents linked to tags and ready for ingestion into their CMMS or EAM system.
Supplier documentation — vendor manuals, equipment datasheets, test records, certificates — is consistently one of the most difficult parts of any handover package to manage. Suppliers submit documents late, in non-standard formats, and without proper linking to equipment tags. An EDMS with a controlled supplier portal enforces review, approval, and linking before documents are accepted into the asset record. This removes the manual effort of chasing, formatting, and filing supplier documents — a task that on large projects can consume weeks of document controller time. Sharecat supports ISO 15926 and CFIHOS-aligned data structures, ensuring the information delivered at handover is structured and ready for integration with operational systems such as CMMS and ERP.
Document handover is where years of poor document control surface all at once. The EPC submits a handover package; the owner-operator's team begins checking it against the MDRL and finds gaps: missing as-builts, documents at the wrong revision, equipment tags that do not match the asset register, vendor manuals that were never formally submitted through the transmittal process.
Good handover documentation does not just mean the files exist — it means every document is at the correct revision, linked to the correct tag, verified as approved, and formatted to the owner's specification. An EDMS that tracks completeness at the tag level — not just document count — enables the EPC to report and close gaps in real time, rather than discovering them at mechanical completion. The difference between a smooth handover and a delayed one is often entirely a function of how well document control was managed throughout the project.
On a large capital project, a delayed handover is not a minor inconvenience. It delays operations start-up, increases carrying costs, and — in sectors such as offshore oil and gas — can have significant contractual and regulatory consequences. Document management is not a back-office function on these projects; it sits on the critical path.
An EDMS does not operate in isolation. On a capital project, it sits alongside project controls, procurement systems, and inspection management platforms. At handover, the asset record it has accumulated needs to flow into the operator's operational systems — primarily the Computerised Maintenance Management System (CMMS) or Enterprise Asset Management (EAM) system, and in many cases the ERP.
The quality of this transition depends almost entirely on how documents were structured during the project. If documents are linked to tags using a consistent, standards-aligned tagging convention — such as ISO 15926 or CFIHOS — the handover package can be ingested directly into the CMMS with the document-to-asset relationships already in place. If documents were stored in a generic file system without tag linking, the operator faces months of manual data migration work before the operational systems are usable.
Sharecat is designed with this transition in mind. The platform structures all document and data relationships against the physical asset from day one of the project, so that at handover the asset record is already in a form that operational systems can consume.
When evaluating an EDMS for a capital project in oil and gas or energy, the following capabilities should be assessed as non-negotiable requirements:
Can the system define, track, and report against a full Master Document Requirements List, at the tag level, across multiple contractors and disciplines?
Does the system support formal transmittal issue, receipt, routing, comment tracking, and return — with a complete, exportable audit trail?
Can every document be linked to one or more equipment tags, and can completeness be reported at the tag level rather than only at the document level?
Does the system include a controlled supplier submission portal with approval workflows, rather than relying on email and shared drives for vendor documentation?
Does the system support ISO 15926, CFIHOS, or the specific data structures required by the owner-operator's CMMS for handover ingestion?
Can the system generate a verified, structured handover package — with completeness reporting at the tag level — at any point during the project, not just at mechanical completion?
Sharecat is built specifically for owner-operators, EPCs, and suppliers in oil and gas, energy, chemicals, and utilities. Where traditional EDMS tools treat documents as the primary object, Sharecat treats the physical asset — the tag — as the primary object, and attaches both documents and structured data to it.
This means that every P&ID, datasheet, inspection certificate, and vendor manual is not just stored — it is linked to the specific tag or equipment item it describes. Completeness can therefore be measured at the tag level: for each piece of equipment in scope, does the system have all required documents, at the right revision, with approved status? This is what makes handover a measurable process rather than a final scramble.
Suppliers and contractors submit documentation through a controlled supplier portal, with workflows that enforce review, approval, and linking before documents are accepted into the asset record. This removes the manual effort of chasing, formatting, and filing supplier documents — a task that on large projects can consume weeks of document controller time. Sharecat supports ISO 15926 and CFIHOS-aligned data structures, ensuring the information delivered at handover is structured and ready for integration with operational systems such as CMMS and ERP.
A document management system (DMS) manages files — storing, versioning, and retrieving documents. An EDMS adds engineering-specific capabilities: revision coding aligned to engineering standards (A, B, 0, 1, 2), transmittal management, the Master Document Requirements List (MDRL), and the ability to link every document to the physical asset or equipment tag it describes. An EDMS is purpose-built for capital project environments where document control is a contractual and handover requirement.
In oil and gas, an EDMS manages engineering deliverables across the full project lifecycle — from FEED through detailed design, construction, and handover. It controls the flow of drawings, datasheets, P&IDs, inspection certificates, and vendor documents between EPCs, subcontractors, and the owner-operator. It tracks which documents have been reviewed, approved, and issued for construction, and at handover it produces the verified document package the asset owner needs for operations and maintenance.
An EDMS supports handover by ensuring that every document is linked to a specific tag or equipment item, tracked against the MDRL, and verified as approved before inclusion in the handover package. The EPC can report tag-level completeness at any point during the project. The owner-operator receives a structured, verified set of documents ready for ingestion into their CMMS or EAM system, with no gaps or unapproved items.
A complete EDMS handover package typically contains: as-built drawings and P&IDs, equipment datasheets, inspection certificates and test records, vendor documentation and manuals, and instrument calibration records. Each document must have a confirmed revision status and an audit trail showing who reviewed and approved it.
No. SharePoint and Google Drive are general-purpose file storage tools. They lack the core capabilities that define an EDMS: there is no transmittal workflow, no MDRL, no engineering revision coding, and no mechanism for linking documents to equipment tags. On a capital project, this leads to version confusion, uncontrolled document sharing, and an inability to produce a verified handover package without months of manual remediation work.
ISO
27001
Certified
