Digital Engineering and BIM Requirements in Civil Tenders

A drainage contractor opens a council tender for a road upgrade and finds a returnable headed “Digital Engineering Requirements”. It asks for their BIM capability, their proposed BIM execution plan, their common data environment arrangements and their compliance with ISO 19650. Increasingly the same returnable also asks about information security, covered in our guide to cyber and information security in civil tenders.

They do not own modelling software. Nobody in the business has heard of ISO 19650. The instinct is either to bluff — promise everything, work it out later — or to leave the returnable blank and hope it is not scored.

Both are wrong, and both are avoidable. Digital engineering and BIM requirements ask far less of a construct-only civil subcontractor than the vocabulary suggests. This guide separates what the words mean from what you are actually obliged to do.

The requirement that arrived without warning

Digital engineering entered Australian civil construction through the major road and rail authorities, which mandated it on large projects to get consistent asset data out of construction and into asset management. It has since flowed downward by two routes.

• Flow-down from head contracts. A Tier 1 with digital engineering obligations passes the relevant parts to its subcontractors — the back-to-back mechanism described in subcontracting to Tier 1 civil contractors.
• Template drift into council tenders. Councils adopt agency specification templates, and the digital engineering clauses come with them — sometimes deliberately, sometimes because nobody removed them.

That second route explains why the requirement often looks disproportionate. A four-hundred-metre kerb renewal does not need a federated 3D model. But the clause is in the contract, it is in the returnable schedule, and it is scored — so it has to be answered. The site-delivery end of the same shift — building from the model rather than describing it — is covered in our guide to machine control and GNSS.

The vocabulary, decoded

Term	What it actually means	Does it apply to a civil subcontractor?
BIM — building information modelling	Producing and managing structured information about an asset, usually but not only a 3D model	Partly. The information obligation applies; the modelling obligation usually does not
Digital engineering (DE)	The broader Australian term agencies prefer — BIM plus data, systems and process	Yes, as an information and handover obligation
ISO 19650	The international standard for managing information across an asset’s life using BIM	Yes, but principally as roles and process, not modelling
EIR — exchange information requirements	The client’s statement of what information it wants, in what format, when	Yes. This is the document that binds you
BEP — BIM execution plan	The team’s response to the EIR: how information will be produced and delivered	Yes — you either contribute to one or are covered by the head contractor’s
CDE — common data environment	The single agreed platform where project information is stored and exchanged	Yes. You will be given access and expected to use it
LOD — level of detail / development	How complete and reliable a piece of model information is at a given stage	Rarely, unless you carry design
Federated model	Separate discipline models combined for coordination and clash detection	No — that is the designer’s and head contractor’s job
Asset information model	The information handed to the asset owner at completion	Yes. Your as-constructed data feeds it

The pattern in that table is the whole point of this article. The requirements that genuinely reach a construct-only civil contractor are about capturing and handing over accurate information in a specified format. The requirements about producing and coordinating models generally sit with the designer and the head contractor.

ISO 19650 and what it asks of you

ISO 19650 is a series of standards for organising and digitising information about buildings and civil engineering works. Australian tenders reference it because it gives everyone a common vocabulary for who produces what information, when, and to what standard.

Its most useful contribution for a subcontractor is a set of defined roles:

• Appointing party — the client. Issues the exchange information requirements.
• Lead appointed party — usually the head contractor. Coordinates the information deliverables and runs the BIM execution plan.
• Appointed party — the subcontractors and suppliers. This is you. You deliver your part of the information to the agreed standard, into the agreed environment, at the agreed time.

Reading yourself as the appointed party clarifies almost everything. You are not required to run the information management system. You are required to deliver defined information into someone else’s, correctly and on time — which is a records discipline, and one you already exercise under quality management plans and ITPs.

The EIR — the document that sets your obligations

If you read one digital engineering document in a tender pack, read the exchange information requirements. Everything binding flows from it.

What to look for, in order:

1. What information is required from the contractor, as distinct from the designer. Frequently the honest answer for a construct-only package is: survey, as-constructed data, test results, product and material data, and photographs. Our guide to drone survey and reality capture covers how most of that is now collected.
2. In what format. A specified file format, naming convention and data structure. This is the single most common source of rejected deliverables.
3. To what accuracy or tolerance, particularly for survey and as-constructed data.
4. At what point. Progressively during the works, or at completion, or both.
5. Into which environment, and who provides access.
6. Who reviews and accepts it, and what happens when it is rejected.

Where the EIR is absent, thin or clearly inherited from a template that does not fit the job, that is a legitimate clarification question during the tender period — and a valuable one, because the answer usually reduces your obligation. The mechanics of asking are in tender clarifications and the RFI window.

The BIM execution plan, pre and post contract

The BEP is the delivery team’s response to the EIR. It exists in two versions and the distinction matters at tender time.

	Pre-contract BEP	Post-contract BEP
When	Submitted with the tender	Developed after award, before work starts
Purpose	Demonstrates you understand and can meet the requirements	The operational document the team actually works to
Length	Short. A statement of approach, capability and resourcing	Detailed, and usually the head contractor’s to produce
Your role as a subcontractor	Describe your contribution and your systems	Comply with it — you are usually a contributor, not the author

When a tender asks for “your BIM execution plan”, it almost always means the pre-contract version, and it is asking a capability question rather than requesting a technical document. Two or three pages that state what information you will produce, in what format, using what systems, checked by whom, is a complete and correct answer.

The common data environment

The CDE is the single agreed place where project information lives. On most civil projects it is provided by the client or head contractor, and your obligation is to use it properly rather than to supply one.

What using it properly means in practice:

• Files go in the CDE, not in email. An as-constructed drawing emailed to the superintendent has not been delivered, and on a strict project it does not count.
• Naming conventions are mandatory. The convention will be specified. Files that do not comply are rejected, and rejection is a delivery failure with a date attached.
• Status codes matter. Information moves through states — work in progress, shared, published, archived. Uploading something as published when it is a draft creates real problems.
• It is an audit trail. Everything is dated and attributed. That cuts both ways: it evidences your delivery, and it evidences your lateness.

That last point is worth internalising. A CDE is contemporaneous, timestamped and independent — which makes it useful evidence when a delay or variation is later disputed. The record discipline in contract administration for civil SMEs applies with more force, not less, on a digitally managed project.

Level of detail, and why it matters commercially

Level of detail — sometimes level of development, and the two are not the same thing in every framework — describes how complete and reliable a piece of information is at a given point.

For a construct-only contractor the commercial relevance is narrow but sharp: a model issued at a low level of detail is not a construction document. If you are given a design model and asked to build from it, establish what its stated level of detail is and whether it is issued for construction. Building from a coordination-stage model and discovering the levels were indicative is a variation argument you would rather not have — and the entitlement analysis is the one in variations in civil construction contracts.

Where a model and a drawing conflict, the contract will usually say which prevails. Find that clause before you price. On many civil contracts the drawings still prevail, and the model is provided for information only.

As-constructed data is the real obligation

For most civil subcontractors, this is what digital engineering actually amounts to — and it is where the cost and the risk sit.

Traditional as-constructed delivery was a marked-up drawing at the end of the job. Digital delivery typically requires:

• Survey-grade spatial data in a nominated coordinate system, to a stated accuracy.
• Data captured progressively, particularly for anything that gets covered — pipes, conduits, subgrade, service crossings. Once it is buried, an accurate record is expensive or impossible to recover.
• Attribute data as well as geometry — not just where the pipe is, but its material, diameter, class, manufacturer and installation date.
• A defined structure and format, so the asset owner can load it into their asset management system without rework.

The critical operational point: this is a during-construction obligation, not a completion one. A contractor who plans to assemble as-constructed data at the end of a pipeline job has already lost the information. Survey before backfill, or pay to expose it later — and note that final payment and practical completion are frequently conditional on the data being accepted, which is covered in practical completion, defects liability and the final claim.

What is actually required at SME scale

If the project is…	Realistically expected of a civil SME
A council road or drainage job with template DE clauses	Digital as-constructed data in a nominated format. Often nothing more. Clarify if the clause looks inherited
A council or utility job with a real DE requirement	As-constructed to specified accuracy and structure, delivered through the client’s CDE, with a short statement of approach at tender
A subcontract under a Tier 1 on a major project	Compliance with the head contractor’s BEP and CDE, defined data deliverables, and possibly a nominated person responsible
A design-and-construct package	Genuine modelling obligations, because you carry design — see AS 4902, GC21 and Minor Works

Three of those four rows require no modelling software at all. That is the single most useful thing a civil SME can know about this subject.

How to answer the returnable honestly

The instinct is to overstate. Do not — capability claims here are unusually easy to test, and a contractor who claims a modelling capability they lack will be found out during delivery, when it is expensive.

A strong SME answer has five parts and runs to about two pages.

1. State what you are. “As a construct-only civil contractor our digital engineering role is as an appointed party under ISO 19650: we produce and deliver defined project information, we do not undertake design modelling.” Correct, confident, and it demonstrates you have read the standard.
2. Name your deliverables. Survey and as-constructed data, ITP and test records, material and product data, photographic records, and the format for each.
3. Describe your capture method. Who surveys, with what equipment, to what accuracy, and at what point in the sequence — specifically that data is captured before cover.
4. Describe your data handling. Naming convention compliance, who uploads to the CDE, who checks before upload, and how versions are controlled.
5. Name a responsible person. Not a BIM manager — the person in your business who is accountable for the information deliverables. On a five-person contractor that may be the project manager, and saying so plainly is better than inventing a role.

Where you genuinely cannot meet a requirement, say so and state how you will cover it — a surveyor engaged for data capture, or a stated reliance on the head contractor’s environment. An honest, resourced gap scores better than a claim that collapses, and the reasoning is the same as in how to address selection criteria.

Pricing digital engineering

Usually under-priced, because it looks administrative and is actually surveying.

• Survey time during construction, not just at completion. Progressive capture is the largest single cost.
• Survey equipment or subcontracted survey, at the accuracy specified.
• Data processing and formatting into the required structure — real hours, frequently by someone whose time is not otherwise on the job.
• CDE administration — uploads, naming, resubmissions after rejection.
• Rework allowance. First submissions are commonly rejected on format. Budget for a second pass.
• Software or training, only where genuinely required.

These belong in preliminaries as identified items rather than absorbed — the discipline in preparing civil works cost estimates. Where the requirement is disproportionate to the contract value, that is worth raising in clarifications, and occasionally worth reflecting in the go/no-go decision.

Building the capability without buying software

A staged approach that costs very little and answers most requirements.

Stage	What to do	Cost
1. Survey discipline	Establish progressive as-constructed capture as standard practice on every job, whether or not it is required	Process change
2. Naming and structure	Adopt a consistent file naming and folder convention across the business	Nil
3. A named owner	One person accountable for project information delivery	Nil
4. Survey capability	Either in-house equipment and training, or a standing relationship with a surveyor	Moderate
5. A reusable statement	A two-page digital engineering capability statement, maintained and adapted per tender	One day, once
6. Modelling	Only if you take on design-and-construct work. Otherwise unnecessary	Significant — defer it

Stages one to five cost almost nothing and answer the requirement on the overwhelming majority of civil tenders. Stage six is where contractors waste money attempting to buy a capability the market has not actually asked them for. Keep the statement in your library, per building a tender content library.

Seven ways contractors lose marks here

1. Leaving the returnable blank because the terms are unfamiliar. A scored returnable left blank scores zero.
2. Claiming full BIM capability that does not exist. Easy to test, expensive when found.
3. Answering with software names. Listing packages you own is not a description of how information gets delivered.
4. Confusing design modelling with information delivery — and so answering a question that was not asked.
5. Treating as-constructed as an end-of-job task. The data is gone once it is covered.
6. Ignoring the naming convention. Correct information in the wrong format is a rejected deliverable.
7. Not pricing it. Survey time, processing and resubmission are real hours.

Checklist

• Have you found and read the exchange information requirements, not just the returnable?
• Do you know which deliverables are yours as opposed to the designer’s or head contractor’s?
• Do you know the required format, naming convention and accuracy?
• Do you know whether data is required progressively or only at completion?
• Do you know who provides the CDE and who gets access?
• If a model is provided, do you know its status and whether drawings prevail over it?
• Does your answer state your role correctly as an appointed party?
• Have you named a responsible person rather than invented a role?
• Is progressive survey capture built into your construction sequence?
• Have you priced survey, processing, upload and a resubmission allowance?
• If the requirement looks disproportionate to the contract, have you raised it in clarifications?

The short version

• Digital engineering asks far less of a construct-only civil contractor than the vocabulary suggests. You are an appointed party: you deliver defined information into someone else’s system.
• The exchange information requirements is the document that binds you. Read it before the returnable.
• As-constructed data is the real obligation, and it is a during-construction task. Survey before cover or lose the information.
• Three of the four common project types require no modelling software at all.
• Answer honestly and specifically — role, deliverables, capture method, data handling, named person. About two pages.
• Format failures cause more rejected deliverables than accuracy failures. The naming convention is mandatory.
• Price survey time, processing and a resubmission allowance. It is surveying work, not administration.

Sources and further reading

This guide is general information for Australian civil construction businesses and is not technical or legal advice. Digital engineering and information management requirements are set by the individual client, the exchange information requirements and the contract, and differ substantially between agencies, between projects and between contract values. Terminology is not applied consistently across frameworks — level of detail and level of development in particular carry different meanings in different systems. Always work from the exchange information requirements and the executed contract for the specific project rather than from general descriptions of the standards.

• ISO 19650, Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Information management using building information modelling, adopted in Australia as the AS ISO 19650 series. The role structure referenced in §04 — appointing party, lead appointed party and appointed party — and the concepts of exchange information requirements, the BIM execution plan and the common data environment are drawn from that series. The standard describes an information management process; it does not itself mandate modelling software or a particular platform, which is the distinction this guide turns on.
• Australian state road authority digital engineering frameworks and specifications, which are the principal route by which these requirements entered Australian civil construction and subsequently flowed into council and utility tender templates. Requirements, maturity expectations and deliverable formats differ by authority and by project, and are set in the project’s own exchange information requirements rather than by a national standard.
• Related TenderBuilt guides carrying the primary-source detail referenced above: quality management plans and ITPs (conformance records, test results and as-constructed reporting), contract administration for civil SMEs (the contemporaneous record discipline a CDE formalises), AS 4902, GC21 and Minor Works (where design responsibility, and therefore genuine modelling obligation, transfers to the contractor), and subcontracting to Tier 1 civil contractors (how head contract obligations flow down to subcontract packages).