BIM Busters: Why the Prototype Dogma Blocks Construction (And How We Decode Building DNA)

“We build prototypes, so construction cannot be compared to the auto industry, cannot be automated, and certainly cannot be standardized.” It is the ultimate straw man of the AEC industry—the dogma of our time meant to kill every efficiency discussion before it starts.

But is it even true? Just because almost everyone believes the earth is flat does not make it flatter. Dig deeper and you quickly notice: the statement “every building is a prototype” is only half the truth.

To bust the dogma, we must understand that there are three completely different kinds of standards:

• The standard of form: Every building looks exactly the same. That leads to the architectural monotony of old panel housing—aesthetic catastrophe nobody wants. Here the prototype argument holds: every building should be individual!
• The standard of process: The steps to the goal are always similar. Whoever builds a concrete wall sets formwork, places rebar, and pours concrete.
• The standard of pattern: A human face always looks different. Yet it follows the same pattern: two eyes, one nose, one mouth.

And that is exactly where the key to digital construction without bullshit lies.

The Hidden Pattern in the Stairwell

Take three arbitrary multi-family buildings from three different architects. Facades look different, floor plans vary. But look at the stairwells. The underlying pattern—the algorithm behind them—is eerily identical:

• Surrounding walls are concrete (usually with a predefined fire rating like EI90).
• Stair flights are also concrete.
• There is a railing (visually different, but functionally identical).

Although different people planned and built these buildings, the pattern repeats again and again. Every building consists of the same elements: interior walls, exterior walls, slabs, columns, roofs. How they look differs—but how they relate to each other is almost always the same.

The 4 Building Blocks of Building DNA

This universal underlying pattern is building DNA. Just as human DNA creates infinite diversity from only four organic bases (adenine, thymine, cytosine, and guanine), every complex building rests on only four fundamental blocks:

• Spaces (IfcSpace): They make the building usable in the first place.
• Separations: Walls and slabs that bound rooms.
• Connections: Windows and doors that link rooms.
• Rules: The mathematical relationships of how these elements connect.

          [ The 4 Building Blocks of Building DNA ]
          /                |               \                \
          [Spaces]     [Separations]    [Connections]       [Rules]
          (Rooms)      (Walls/Slabs)    (Doors/Windows)   (Relationships)

From Code to Ecosystem: The Pragmatic BIM Data Contract

Until now, software could not automatically use these patterns because every architect models walls and components in IFC chaotically and differently—the so-called geometry anarchy.

That is where abstract.build technology comes in. We do not force architects into a rigid corset—we read the mathematical structure of the model.

The foundation that makes this DNA tangible in practice is a radically simplified, open data model: the Pragmatic BIM Data Contract.

This open-source data contract is the technological core of everything we do. It forms the shared nervous system for two fundamental pillars of modern planning:

• iterthink: Our engine for algorithmic generation and iterative exploration of variants. It uses the clean data structures of the data contract to simulate planning decisions in real time.
• yourcompanyos: The digital operating system for forward-looking planning firms. It automates internal workflows, data management, and quality assurance based on exactly this standardized minimum data model.

Instead of manually querying hundreds of redundant attributes, the data contract reduces requirements to the functional minimum. Our Normalizer algorithm needs only two core inputs to prepare the model:

1. Every space must know its function (e.g. office, kitchen, stairwell).
2. The system mathematically computes in automatically generated abstractBIM exactly which wall stands precisely between which two rooms.

Once this topological relationship stands in the data contract, the “prototype problem” is solved for software. The algorithm recognizes the pattern behind individual architecture. Suddenly quantity takeoffs, cost calculations, or thermal building simulation run fully automatically—orchestrated via yourcompanyos and optimized through iterthink.

So let us stop hiding behind the prototype dogma. The patterns are there. We just need to read them out.

View the Pragmatic BIM Data Contract on GitHub and learn how iterthink and yourcompanyos take your planning data to the next level.