Here's a number that should terrify every construction executive: according to FMI Corporation, bad data costs the global construction industry $1.85 trillion per year. That's not a typo. That's more than the GDP of Australia, wasted annually because project teams can't find, trust, or use the information they've already generated.

And yet, when we talk about "digital transformation" in construction, the conversation inevitably gravitates toward drones, BIM models, and IoT sensors. Exciting, certainly. But these tools are data producers. Almost nobody is talking about the far harder problem: what happens to that data after it's created.

The Information Entropy Problem

Every construction project generates an enormous volume of documentation. Specifications, drawings, inspection reports, commissioning records, O&M manuals, as-built surveys, defect logs — the list is nearly infinite. On a major infrastructure project, you're looking at tens of thousands of documents and millions of individual data points.

The problem isn't volume. The problem is entropy.

Left to their own devices, project teams store information wherever is most convenient at the moment of creation. A commissioning record lands in one engineer's email. A valve specification lives in a shared drive folder that three people know about. The asset register — the supposed single source of truth — is an Excel file on someone's desktop with 47 tabs and a macro that stopped working in 2019.

The construction industry doesn't have a data creation problem. It has a data entropy problem — information drifts toward maximum disorder from the moment it's produced.

By the time a project reaches handover, the information landscape resembles an archaeological dig site more than a structured database. And the owner — the entity that will operate this asset for the next 30 to 50 years — inherits all of it.

Why Spreadsheets Were Never the Answer

The spreadsheet became construction's default data tool not because it was good at managing project information, but because it was available. Everyone had Excel. Everyone could (sort of) use it. And for a single, isolated task — tracking a punch list, logging daily quantities — it works tolerably well.

But construction data isn't isolated. A pump doesn't exist in a vacuum. It connects to a pipe that feeds a tank that serves a process that supports a facility. The pump has specifications, maintenance schedules, commissioning results, warranty information, spare parts, and photos. All of those relationships are invisible in a spreadsheet.

Worse, spreadsheets actively resist collaboration. Version control is nonexistent. Concurrent editing creates conflicts. Validation rules are brittle. And when someone emails a copy of the "master" spreadsheet, you've just forked reality.

The Handover Cliff

The consequences of data entropy become most visible — and most expensive — at project handover. This is the moment when the construction team passes responsibility to the operations team. In theory, the owner receives a complete, structured digital record of the asset they've just paid hundreds of millions (or billions) to build.

In practice, they receive a hard drive.

Sometimes literally. We've spoken with asset owners who received physical hard drives containing tens of thousands of unindexed PDFs. No metadata. No relationships. No way to answer a basic question like "show me all the commissioning certificates for Level 3."

The operations team then spends the first two to three years of the asset's life re-creating the information that already existed during construction — retyping nameplate data, re-scanning documents, re-establishing the relationships between equipment and its documentation. The cost is staggering. The inefficiency is breathtaking.

The Oestler Asset Hub: Structured Data, Not Flat Tables

Oestler's Asset Hub is built around three core registries that work together to enforce data quality at the source — before the data has a chance to drift:

The Asset Register

Every asset in Oestler has a record with a tag number, description, location, parent asset (for hierarchy), and a DPK (Data Package Key) that groups related attributes into bundles. The register is fully searchable and filterable by any attribute — not just the fixed columns a spreadsheet forces you to accept. Column visibility, order, and width are all configurable and saveable as named views that can be shared across the project team.

Attribute Definitions

Every asset type has a defined attribute schema — the specific fields required for that asset to be considered complete. Attribute definitions carry an ID, a display title, an example value, and a link to a validation rule. This is what separates Oestler from a glorified spreadsheet: attributes aren't just columns, they're typed, validated fields with known expectations.

Validation Rules

Validation rules constrain what can be entered in every attribute field. Six types cover the full spectrum of construction data:

  • BOOL — yes/no binary fields
  • INT / FLOAT — numeric values with implicit type enforcement
  • STRING — free text with optional length constraints
  • REGEX — pattern-matched strings for tag numbers, reference IDs, and codes
  • LINK — validated URL or cross-asset references

A validation failure isn't a report that someone reads three months later. It's a flag on the record, visible the moment the data is entered. This is continuous data quality — the opposite of the retrospective "data cleanse" that every handover team dreads.

Search That Understands Context

Oestler's Knowledge Search goes beyond text matching. It traverses the relationships between assets — tag numbers, attribute values, location codes, document associations — to return contextually relevant results. Search for a room number and get all the assets physically located there. Search for a valve specification and find every asset that shares it.

Alongside search, the QR Scanner lets field teams go from physical equipment to full digital record in a single scan. The asset's complete attribute set, photos, commissioning records, and open tasks are immediately accessible — without knowing the tag number, navigating a menu, or opening a laptop.

The Opportunity Is Enormous

Construction is a $13 trillion global industry — the largest in the world by output. It has also been, by virtually every metric, the slowest to digitise. McKinsey ranks it second-to-last among all industries in digital adoption, just above mining.

That gap between the volume of value created and the sophistication of the tools used to manage it represents one of the largest untapped opportunities in technology. The industry doesn't need another point solution. It needs a platform that treats data as a first-class citizen — from the first day of design through decades of operations.

The construction industry's data problem is bigger than most people think. But so is the upside of solving it.