Revision control As-built and handover Installations and construction projects

Custom engineering document management

Appfront builds custom software for managing drawings, schematics, specifications and calculations for capital-intensive installations and construction projects. The question is rarely where a document is, but which revision is currently valid, who approved it, and whether the superseded version can demonstrably be shown to be out of circulation.

Document management for an installation is different from the office

Engineering document management, often called document control or EDMS in tenders, covers the technical documentation of a physical asset: P&IDs, isometrics, electrical diagrams, structural drawings, strength calculations and supplier documentation. It plays a role in process industry, energy, infrastructure, shipbuilding and commercial construction.

The difference from office document management lies in the nature of the document. A contract has a version, and that version is the contract. A drawing has a revision, and that revision is a claim about an object that itself changes. If the installation and the drawing drift apart, the archive is not merely inaccurate but misleading.

Two adjacent questions belong elsewhere. If you are dealing with master data that must be consistent across several systems, such as asset and tag numbers, you need master data management software. If it is about procedures, work instructions, deviations and audits, that belongs in a custom quality management system.

One valid revision

Exactly one revision is the valid one. That status follows from a release with a name and a date, not from a file name.

Superseding is an action

The system knows to whom a revision has been issued and sets a withdrawal against it, which only closes after confirmation.

Documentation follows reality

A change on site opens an obligation on the associated document, with an owner and a status.

Three drawings of the same pipe, and nobody knows which one applies

In the cabinet at the installation hangs a laminated drawing, printed during the last major shutdown. The project manager's mailbox holds revision D. Next week's contractor works from the tender set, revision B. All three were once valid, and none of them reports that something newer exists.

As long as it concerns a dimension, the cost is rework. In an installation where safety depends on having the right drawing, the nature of the problem changes. An isolation plan drawn up on an outdated P&ID can point to a valve that was moved during the previous modification. The work permit is then formally in order and materially wrong, and invisible until it matters. That is not an archive problem but a risk in the installation.

As-built and as-designed drift apart

Small changes during construction, an emergency repair at the weekend, a pump replaced by a different type, a pipe rerouted to make room. Each intervention is defensible and disappears from view as soon as nobody has to report it back. The pattern is familiar: the as-built is promised at the end, by which time the project team has been disbanded, and the last ten per cent never arrives. A system that breaks this pattern ties the report-back to change management, so that an approved change opens an obligation that counts towards close-out.

Third-party documents belong behind a gate

Contractors and suppliers deliver a substantial part of the documentation: as-builts, inspection reports, material certificates and maintenance manuals, in their own numbering and formats. If you let that land directly in the archive, within a year you have an archive nobody dares to build on. An acceptance process belongs in between: checks for completeness and format, renumbering to your structure, review by the responsible discipline, and only then admission. The return path for rejection belongs in the contract.

Revision status is the core, not a field on a form

A document status is only worth something if it follows from an action performed by a named person, and if the system attaches consequences to it. In most installation environments this comes down to four states.

1
Concept

In progress with the author. Others may look but must not use it as a basis for work; anyone who prints it gets that marking printed on it.

2
In review

Submitted to the reviewers of the disciplines involved. Comments are attached to the revision, so it stays traceable which comment led to which change.

3
Approved

Released for use, with name, role and date. From this point the revision is immutable: a correction results in a new revision. Distribution starts here.

4
Discontinued

The successor has been approved. The system generates the withdrawal instruction from the distribution history. The document remains available for reference, but is clearly marked.

In project environments, further states come into play: a separate release for construction alongside a release for information, or a hold when a revision has been withdrawn without a successor. Which status model you need is a question to settle before the build: changing it afterwards means reinterpreting the history of every existing document.

What such a system needs to do

How much each of these matters varies: an asset management organisation with a stable archive has different needs from a project organisation handling hundreds of documents a week.

Numbering scheme that follows the asset

A number that encodes the installation, system part and document type is still readable years later. The numbering scheme is built into the system as a rule.

Searching on metadata

Discipline, system, tag number, project phase, revision status and supplier as searchable fields, instead of doing the rounds of your colleagues.

Acceptance of submissions

A submission portal that checks for completeness, format and naming, plus a review round per discipline.

Distribution and withdrawal

Recording who received which revision, so withdrawal can be targeted. Printing on request with a watermark and print date.

As-built feedback

A change on site opens an obligation on the documents concerned, with an owner and a deadline.

Handover file as a requirements list

The contents of the handover file are fixed at the start for each system part, so it is clear well in advance what is missing.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Coding and standards: what exists, and what do they do for you?

International standards exist for structuring and numbering installation documentation, and it pays to align your numbering scheme with them. IEC 81346-1:2022 defines the structuring principles and reference designations you use to identify objects across disciplines. For the document type, IEC 61355-1:2008 was long the framework, with its document kind classification code. That standard was replaced in early 2025 by EN IEC 81355-1:2025, which shifts the focus to information containers and replaces the DCC with an information kind classification code (ICC).

In construction and infrastructure, the NEN-EN-ISO 19650 series is the framework: part 1 covers concepts and principles, part 2 the design and construction phase, part 3 the operational phase. The series is deliberately general in its wording, which is why DigiGO is working on practical guidelines. For drawings in civil engineering, NLCS defines the coding system, layer structure and metadata.

In the process industry and the oil and gas sector, CFIHOS is the designated framework for information handover at completion. It is hosted by IOGP as JIP36 and describes which data and documents a contractor delivers, and in what form. That is easier to enforce contractually than a list of your own.

At Brzo sites, documentation is not an administrative side issue. The Major Accidents (Risks) Decree 2015 transposes the Seveso III Directive (2012/18/EU) into Dutch law and requires a safety management system in accordance with Annex III of that directive; Article 12 requires upper-tier establishments to keep an up-to-date list of the hazardous substances present. In an inspection, the question is rarely whether you have documentation, but whether you can demonstrate that it is up to date.

IEC 81346-1:2022 EN IEC 81355-1:2025 NEN-EN-ISO 19650 NLCS CFIHOS / IOGP JIP36 Brzo 2015 PDF/A archiving CAD and PDF viewers Maintenance management system integration

When you are better off not building this

Mature EDMS and PDM packages exist for exactly this problem, and for a good share of readers here, such a package is the right choice. If you work with a common revision system, your numbering scheme follows a standard and your processes fit within what the package offers, you buy years of development work and a proven approval model. Swapping that for a custom build is rarely wise, and the same goes if your document volume is limited or nobody wants to take on the maintenance.

Custom development is justified in a narrower set of situations: when your numbering or approval structure differs fundamentally from what a package supports, when the system has to integrate with environments the vendor doesn't know, or when a feature you needed stayed on a vendor's roadmap for years.

You should know in advance what custom brings with it. Maintenance, user support and further development become your organisation's responsibility. In regulated environments, there is also the obligation to substantiate and document how the system itself works, and to keep that up to date with every change. With a package, you partly rely on the vendor for this; with a custom build, it rests with the client.

Consider custom development when

  • your numbering or approval structure doesn't fit a package
  • you need to integrate with systems the package vendor doesn't support
  • multiple sites with their own regimes need to sit under one archive
  • external parties supply documents according to your contract terms
  • you want to own the code, data and migration path

Related services

Where related issues belong, so you don't build one system for three problems.

Master data management

The master data behind your documents: asset and tag numbers, equipment types and suppliers. If these differ slightly everywhere, no document management system will help. See building master data management software.

Quality management

Procedures, work instructions, deviations and audits follow their own rhythm and belong alongside the engineering archive. See building a custom quality management system.

Software for manufacturing

If you manufacture yourself, with bills of materials and engineering-to-order, that is a different issue. See building manufacturing software.

Frequently asked questions about engineering document management

The questions clients ask just before making a choice.

A folder structure tells you where a document is stored, not whether it is the current revision; anyone can copy a file or open an old version without anyone noticing. In a document management system, the status follows from an approval with name and date, an approved revision cannot be changed, and superseding a document triggers a withdrawal task for each recipient.

For many organisations that is the better choice. If you work with a standard revision scheme and your processes fit within the package, you are buying years of development work and a proven approval model. Custom development is only justified when you have an unusual approval structure or need integrations the vendor doesn't support.

Superseding is an action with consequences, not a silent status change. The system records who a revision was issued to and in what form, and when the successor is approved it generates a withdrawal task for each recipient that only closes once confirmed. Prints carry a watermark with the revision number and print date.

Through an acceptance process, not through the mailbox. External parties submit documents via a portal that checks for completeness, format and naming, followed by renumbering to your structure and review by the responsible discipline. Write the submission requirements into the contract, otherwise the portal will be bypassed.

The client owns the source code and the data. We hand over the repository, the build and deployment scripts, the database schema and the technical documentation, so that another party can take over. Document formats remain open, so the archive stays readable even without our application.

In that case, what counts is not the presence of documentation but being able to prove it. The system records for each revision who drafted, reviewed and approved it, who it was distributed to and when the previous one was withdrawn. That chain can be exported, which matters for Brzo sites with their mandatory safety management system.

By tying your numbering scheme and metadata to a standard rather than to the application. If you designate objects according to IEC 81346 and classify document types according to the successor of IEC 61355-1, you keep an archive that remains meaningful outside the system. Store everything in open, archive-suitable formats.

What's going on in your archive?

Tell us which installation it concerns, how your revisions and approvals currently work and where your documentation is out of step. We will also honestly assess whether an off-the-shelf package would serve you better.

Edit content