Industrialised housing doesn't succeed because someone bought a factory. It succeeds when the product range lives as a governed digital system the factory — and its robots — can actually consume. Here is how I'd architect that chain, and, just as important, where it honestly stops.

The design spine — Autodesk, up to a point

Revit holds the product range as a CORE plus a kit of parts: what repeats lives once, what varies is a governed, swappable part. With Autodesk Informed Design, each part is authored as a manufacturable product in Inventor and placed in Revit as a traceable, known-manufacturable component — so bills of quantities and shop drawings generate from the placed instances rather than being redrawn.

Forma Building Design fits that product range to each site at feasibility stage; Revit 2027, currently a tech preview, is Autodesk's first Forma connected client, syncing granular data with no file conversion. Autodesk Construction Cloud is the common data environment — and where a schedule-and-workplan automation ties factory output to the site assembly sequence.

The honest boundary — where Autodesk stops

No design platform carries data all the way to the machine. Precast and panel lines run on the equipment vendor's own software — Weinmann's wupWorks for timber, a precast master computer from the likes of Vollert or Progress — and they ingest neutral exchange formats: BTL for timber, UNITECHNIK/UXML, PXML and BVBS for precast and reinforcement. In precast, the detailing tool is more often Tekla than Revit.

So the Autodesk stack is the design-and-coordination spine; it hands off to the vendor ecosystem through those formats. Pretending it is Autodesk all the way to the robot is how these integrations fail.

Where the real engineering is — the connective tissue no platform ships

The valuable work isn't configuring the platform — it is building the parts the platforms don't provide: the handoff into the vendor's exchange formats, the model-to-line integration, and the feedback loop that returns as-built and QA data to the model so the chain stays honest.

That is the work I have done. A production schedule-and-workplan automation, built on platform capability the vendor does not officially document, and engineered with monitoring and fail-soft so it runs reliably in daily use. A 258-tool automation suite. A standardised master framework across 120-plus designs, migrated across API generations in one governed pass. The tools that make factory housing work are mostly the ones that don't come off the shelf.

Built within a national volume home builder in a global industrialised-housing group — the discipline that model demands, delivered digital-first.