Admares + ABB: When the Housing Factory Becomes the Building Site
Admares and ABB Robotics are building AI-enabled modular housing factories. What it means for an architecture practice's IFC round-trip and model ownership.
Signal. Admares, the Finnish industrialised-housing developer, has signed a global partnership with ABB Robotics to wire robots and an “Industrial AI Operating System” into its modular factories — starting with a planned Smart Factory in Australia built alongside Porsche Consulting, MHP, Siemens, EDAG and Nvidia. AEC Magazine reports the plant is meant to run on robotics, AI-driven production planning, predictive maintenance and a real-time digital twin. Founder Mikael Hedberg called it “a fully integrated, next-generation manufacturing environment for industrialised housing.” We read that sentence from the side of the desk where the work actually has to be won, modelled, coordinated and billed.
System. The frontier here isn’t the robot arm — ABB has shipped those for decades, and was just named a 2026 Ford Supplier of the Year. The interesting research line is touch. ABB’s own collaboration with PSYONIC, covered this spring by Fox News, feeds real-world tactile data from bionic prosthetic hands into industrial robots so they can handle delicate, irregular parts. That matters because a house is not a car: it is thousands of slightly-different, tolerance-hungry assemblies. A factory that can only place identical parts builds caravans; a factory that can adapt grip and force per panel builds buildings. The leap from rigid pick-and-place to sensed manipulation is what turns a production line into something an architect could actually design into.
←TODAY: In 2026 a modular plant still wants frozen geometry — change a panel late and the line stalls. →3012: The factory reads your IFC, plans its own tooling, and quotes you back a buildable variant overnight. Fulcrum: The model only earns that round-trip if the office owns it cleanly enough to hand a robot a part it has never seen.
Street. Here is the unglamorous reality the press release skips, and the week it cost us. We once won a small housing Studienauftrag, then nearly lost the margin in Ausführungsplanung because our Archicad model and the fabricator’s machine model disagreed on what a “wall” was. Our LOD-300 competition geometry was beautiful and completely unmanufacturable. An AI-enabled plant doesn’t fix that — it punishes it faster. The day a factory parses your model directly, every loose layer, every untyped object, every Hotlink you never reconciled becomes a production fault, not a coordination note. The BIM-to-BoT research line (Bock et al., Automation in Construction, 2025) is blunt about this: the bottleneck isn’t the robot, it’s whether the BIM carries enough structured intent to drive the toolpath.
Atelier: Treat the factory as a downstream consumer of your model with a strict contract, the same way you treat a Generalplaner’s clash gate. Write into the BEP exactly which objects must be machine-readable, who owns them, and at what LOIN — before the competition model is allowed to become an execution model. The seam where we stopped paying for plugins and started documenting the round-trip is exactly the seam Admares is now automating at industrial scale.
Hack: This Hack teaches you to audit, in seconds, whether your IFC export is even legible to a robot before you promise a fabricator anything. The medium is runnable code; the domain is IFC. Walk every wall and flag the ones missing a material — those are the parts a sensed line can’t tool.
import ifcopenshell
m = ifcopenshell.open("competition.ifc")
for w in m.by_type("IfcWall"):
mats = ifcopenshell.util.element.get_materials(w)
if not mats:
print("UNTOOLABLE:", w.GlobalId, w.Name)
Run it on the model you think is finished. The list it prints is your real handover backlog.
The trade-off, stated plainly: an AI factory collapses the gap between a sloppy model and a wrong building, which rewards offices with model discipline and quietly bankrupts the ones who treat BIM as drawing-with-extra-steps. From a later vantage, the practices that got hurt weren’t the ones that automated late — they were the ones that bought a new tool every project and never wrote down how the round-trip worked, so the discipline walked out with each Praktikant. Repeatability, not talent, is the bottleneck.
PAZ Takeaway: The thing this story actually exposes is a model-handover contract — and that is buildable today, no Smart Factory required. PAZ’s Grasshopper↔Archicad Library exists to harden exactly that seam: personalising the software-to-software workflow and filling the gaps in the native connection so a competition model survives into something a machine, or a fabricator, can read without re-modelling it. An office doesn’t need ABB’s hardware to start; it needs the round-trip documented first.
Move. Before you chase a fabrication partner, run the snippet above on your last won project and fix the untoolable list — own your model cleanly enough that a robot could read it, and the factory partnership becomes a procurement decision instead of a rescue.
SOURCE · ↗
PAZ Kaffi · multidisciplinary editorial, led by PAZ Academy