Last week I wrote about the £79m ($100m, €95m) daily cost of commissioning delay. Several of you replied with the same question: why does it take so long?
This week: the answer. It starts with a wiring diagram.
The scenario everyone recognises
The unit of computing is no longer a chip. It is an entire AI factory. A 100 MW campus engineered at rack-scale precision, where power density and cooling push the physical limits of what has ever been built. Thousands of racks. Hundreds of megawatts. Billions of pounds in capital.
But when that factory reaches mechanical completion, the operations team arrives to commission the electrical systems. They need the single-line diagram for Switchboard 3A.
It exists. It was produced by the electrical subcontractor eight months ago. It is somewhere in the 30,000 documents generated during construction.
The problem is that nobody can find it.
The subcontractor saved it as ELEC-SLD-3A-R04-FINAL-APPROVED.pdf. The general contractor renamed it DC-NORTH-E-003-REV4.pdf when uploading to their document management system. The client's system logged it as 247-EL-DWG-0312.pdf under a different classification entirely.
Three names. Three systems. Same file. The operations engineer searching for "switchboard 3A single-line" finds nothing.
So they walk the site with a clipboard.
Rack-scale design. PDF-scale handover.
The instinct is to blame poor document control. But the problem is structural, not procedural.
A single data centre project involves 15 to 40 subcontractors. Each uses different software. Revit. AutoCAD. MicroStation. Tekla. Each saves files in proprietary formats. Each follows a different naming convention inherited from their own company standards.
The general contractor consolidates into a project document management system. But consolidation is not harmonisation. The files are in one place. The naming, classification, and metadata are not.
FMI and Autodesk found that construction professionals spend 5.5 hours per week searching for project information. That is 35% of productive time lost to non-productive activity. Across a 200-person commissioning team, that is 1,100 hours per week wasted on finding files that already exist.
The format problem beneath the naming problem
Even when someone finds the right file, they often cannot use it.
The electrical subcontractor produced the wiring diagram in Revit. The mechanical team needs the cable routing in AutoCAD. The fire safety engineer needs the same information in PDF with specific annotation layers. The operations team needs it in a format their Computerised Maintenance Management System (CMMS) can ingest.
One document. Four consumers. Four format requirements. No automated translation between them.
We simulate these facilities in digital twins before breaking ground. We build perfect 3D models. But the day construction completes, the digital thread snaps. Four formats. No automated translation. The twin goes dark with the facility.
The US National Institute of Standards and Technology (NIST) estimated that inadequate interoperability costs the US capital facilities industry £12.4bn ($15.8bn, €15bn) annually. That was in 2004. The number has not improved.
buildingSMART developed the Industry Foundation Classes (IFC) standard to solve this. ISO adopted it as ISO 16739. But adoption remains inconsistent. Most subcontractors still deliver in proprietary formats because their contracts do not require otherwise.
What 95% unused looks like in practice
Here is a number that should alarm every infrastructure investor.
Not lost. Not deleted. Unused. It exists on a server somewhere. It was paid for. It was produced by qualified engineers. And the operations team cannot access it because the naming conventions, file formats, and classification schemas do not match what their systems expect.
Over 50% of operations teams wait more than six months to receive closeout documents. Six months of operating a facility without the documentation that describes how it works.
The real cost is not the search. It is the re-creation.
When an operations team cannot find a document, they do not wait. They re-create it. A field engineer walks the site, photographs the installation, and manually drafts a new version of the drawing that already exists.
For a single data centre, this re-creation effort costs £4m to £12m ($5m to $15m, €5m to €14m). For the global hyperscaler build rate, £12.4bn ($15.8bn, €15bn) in annual interoperability waste.
The documents were produced. The engineering was done. The money was spent. And then the operations team does the work again because the file was named wrong.
This happens in every sector
Healthcare renovations generate 50,000+ documents per project. Semiconductor fabs exceed that. Nuclear plants produce documentation that must remain traceable for 60 to 150 years.
In nuclear, a mislabelled cable schedule is not an efficiency problem. It is a regulatory finding. In healthcare, a missing ventilation diagram delays patient occupancy. In semiconductor, an inaccessible clean room specification means requalification.
The sector changes. The pattern does not.
What comes next
Edition 3: One switch fails. £7m ($9m, €8.5m) gone. Every hour.
Edition 4: 18 months of handover. One team did it in four weeks.
Edition 5: 25 standards walk into a facility. None of them agree.
If you build, operate, invest in, or regulate infrastructure anywhere in the world, this is written for you. Subscribe to Still Dark on LinkedIn.
This newsletter lives in the gap between digital delivery complete and permit to operate. That gap is where value dies, and where it can be recovered.
I also co-author The Vistergy Brief at vistergy.com/archive. Satellite and geospatial monitoring, facility lifecycle intelligence, and standards architecture across LNG, nuclear, data centres, utilities and construction. Subscribe to both for the full picture.