Aerospace, automotive, semiconductors, logistics and animated film integrated their chains end to end. This essay gathers what the literature says about how they managed it, why construction fell behind — and a simple test: we searched the scientific literature and the public repositories for a building with the documented process and an accessible as-built model. It does not exist (verification of 2026-09-06).
In one sentence: the sectors that got there had three things construction does not have — an open and stable data standard, someone with contractual power to impose it on the whole chain and a product that repeats — and the result shows in the simplest number of all: while the Boeing 777 has been designed entirely in digital since 1994, there is not a single building in the world whose complete process is published and whose as-built model can be downloaded today.
Between 1990 and 1994, Boeing designed the 777 entirely in CAD — the first commercial aircraft without a final physical mock-up, with digital pre-assembly and the Pratt & Whitney, Rolls-Royce and General Electric engines coordinated in model. What was learned there was not about software.
Software was the least of it. What made the difference was the chain: Boeing agreed with the three engine makers to use the STEP standard “as the production data exchange process” [C, NIST Planning Report 02-5]; the US Navy began writing into contracts the delivery of data in the ISO 10303-239 profile, and the Department of Defense requires 3D models from its suppliers [C, NIST TN 1753]. The standard was born of a measured pain: the lack of interoperability cost the North American automotive industry on the order of a billion dollars a year (RTI 1999, via NIST 02-5). And the doctrine that came out of it is explicit:
“a digital three-dimensional (3D) model … serves as the authoritative information source for all activities in the product's lifecycle.” Model-Based Enterprise, NIST Technical Note 1753 · the model as the single source of truth, not the exchange of documents
Two more pieces construction envies. First: STEP has been in use since 1994, and the AP242 (2014) merged the aerospace and automotive variants into a single profile — a mature standard before most BIM programmes were born. Second: the product that repeats — Ford's platforms cut 15–20% of development cost per model [C, NIST 02-5]; each aircraft, each car amortises the digital investment over thousands of units. A building does not repeat itself, and it is here that the analogy starts to break — we return to that in §5.
| Sector | How it integrated the chain | The mechanism |
|---|---|---|
| Aerospace | Boeing 777, 100% digital; the OEM imposes STEP and tools on suppliers | standard + integrator with contractual power |
| Automotive | product platforms (Ford −15–20%); interoperability costing $1bn a year led to STEP | repeated product + open standard |
| Semiconductors | IEEE 1800/1076 as the contract between stages; common roadmap ITRS→IRDS; a consortium pays for the standard | standard + roadmap + someone to fund it |
| Maritime logistics | ISO 668 container — the interface was standardised, not the product; the gain came from handling, not freight | interface + data (EDI) |
| Process industry | ISO 15926 for the design→operation handover — but with no consensus on criteria and no conformance testing: partial adoption | negative lesson |
| Cinema/VFX | USD (Pixar, open-sourced in 2016) — AOUSD alliance under the Linux Foundation; Core Specification 1.0 ratified in Dec 2025, with a path to ISO | consortium keeps the format open |
Two notes of honesty, because portraits of these sectors almost always lack the shadow. First: even in the leading sectors, benefits are not always measured — in a systematic review of MBSE, two thirds of the claimed benefits had only “perceived” evidence, not measured [C, DOI 10.1002/sys.21566]; in North American industrial practice, 85% of firms use 3D models but only 41% as the primary source of information [C, NIST survey]. Second: the process industry is the experimental control — ISO 15926 was created by asset owners for the handover of engineering data to operations, and even so NIST concluded there is “no consensus as to the criteria for achieving interoperability” and “modest” conformance verification effort: half a standard does not stick [C, NIST IR 7917, read in full]. The parallel with IFC and buildingSMART is uncomfortable and direct.
If the other sectors have the complete digital thread, buildings like this should exist. We set the bar on three legs: documented process end to end, as-built model (reflecting what was built, not what was designed), public access today.
We put the question to the scientific literature (OpenAlex, ~1,700 works in four corpora [measured]) and to the public repositories (Zenodo, GitHub, state programme archives). The result: zero (verification of 2026-09-06). No real building meets the three legs — and the pattern of the failures is more informative than the count:
The two closest cases are complementary half-proofs. The Schependomlaan, a real Dutch house, has the entire collaborative process documented — weekly IFCs, clash reports in BCF, event logs — and the whole set is downloadable today (CC BY 4.0; we downloaded and opened the IFC, 49 MB) [C, buildingSMART mirror]; but the as-built is only a point cloud — there is no as-built IFC. The NZERTF, the NIST laboratory house, has the opposite: design, construction, two years of operation with 379 instrumentation channels and the data open with DOI for a decade [C, NIST] — without any BIM. And the epitaph of the genre: the IFCs of Norwegian public buildings were once listed on an FTP of the HIBO programme, which died without a copy in the web archive [C, verification made on 2026-09-06].
It is the right question — and the answer starts by undoing a confusion: equipment brands and warranties are the innocent part. They already travel in the O&M manuals the owner receives and in COBie; of all the information in the model, they are what benefits the building's owner most. What blocks sharing is something else, in order of weight:
The sum of this is not secrecy — it is a collective action problem: the benefit of sharing is diffuse (the industry learns), the cost and the risk are private. That is why the only almost-open cases came from academia, where it is research funding that pays the bill for sharing.
What manufacturing imposes through ordering power, construction can only impose through contract: EIR/BEP/CDE, IFC/IDS and classification required of the whole chain as an obligation to deliver data, not drawings. The “product that repeats” exists — at the scale of the organisation: parametric libraries, versioned product models and data reused across projects. The STEP-substitute is what we already have (IFC 4.3, IDS, bSDD) with the known brake of being younger and less comprehensive than its manufacturing cousin [C, Pratt 2005; Kenley 2016]. And off-site goes where the structure allows: the prefabricated sectors always grow more in productivity [C, Eastman & Sacks 2008], but the DfMA literature itself speaks of “a combination of offsite prefabrication and onsite assembly” [C, Gao et al. 2019] — and the most transferable lesson from logistics is not even the factory, it is the interface.
What cannot be mirrored was said by the founders of the transfer itself. Lauri Koskela wrote in 1992 that the peculiarities of construction — “one-of-a-kind projects, site production, temporary organization” — prevent flows as efficient as manufacturing's [C, CIFE TR 72]. Six years later, Ballard and Howell closed the argument:
“construction is a fundamentally different kind of production… Adopting a single-minded strategy of transforming construction into manufacturing would be precisely the wrong thing to do… Manufacturing is becoming more like construction.” Ballard & Howell (1998), IGLC-6 · the convergence runs both ways
And copying without adaptation is documented as failure: DfMA guides imported from manufacturing “without adequately considering important differences between the two sectors” — six axes of difference, from site to process [C, Tan et al. 2020, read in full]. The right mirror is not “being a factory”: it is importing the mechanisms — imposed standard, platform that amortises, closed data loop — and letting them live in the form construction has.
Still missing is the number that frames everything: in the US, construction is the second least digitalised sector, ahead of only agriculture — and in Europe it is in last place, behind it: “In the United States, construction comes in second to last, ahead of only agriculture. In Europe, construction is in last position.” [C, MGI 2017] — with productivity falling about 1% a year between 1970 and 2020 — in 2020, below the 1950 level [C, Goolsbee & Syverson, NBER 30845]; in Europe, 94% of firms have fewer than 10 workers and “no firm is large enough to pioneer and lead major innovations” [C, MGI 2017]. The first building with the three legs — published process, verifiable as-built, open licence — is one contractual clause away. The 777 of construction is going to be a small building.
Three structural reasons: one-off projects that do not amortise the digital investment, a fragmented chain (94% of European firms with fewer than 10 workers) and contracts that reward the lowest price. R&D below 1% of revenues, against 3.5–4.5% in automotive and aerospace [C, MGI 2017].
It is hybrid: the prefabricated sectors always grow more in productivity, but the most transferable lesson is the standardised interface (from the container to the data), which works with or without a factory.
No. Whoever documented everything closed the model (Crossrail, Sydney Opera House, The Edge); whoever publishes does not document the process (academic datasets); the rest is synthetic. The closest: Schependomlaan, NZERTF and LivingBIM — each with two of the three legs.
The product data standard of manufacturing (ISO 10303), in use since 1994 — the equivalent of IFC, but older and more comprehensive over the life cycle. It was born of a measured pain: interoperability costing the automotive industry ~$1bn a year.
It is not the brands or the warranties — it is the legal value of the record, physical security (there is a standard just for that, ISO 19650-5), the privacy of occupancy data, commercial lock-in, ambiguous ownership and the duty to maintain. It is not secrecy: nobody is paid to share.
The verifiable as-built is the step almost every model is missing: this collective delivers scan-to-BIM with declared accuracy (contractual LOA) and verifiable IFC. And if your next building could be the first with the three legs — published process, open as-built, licence in the contract — write to us: [email protected].
See scan-to-BIM