RESEARCH ROADMAP · PHYSICAL STANDARDS

Modular Interface Standardization


Connectivity standards whitepaper cover
CfOC Whitepaper
Open Source Connectivity Standards for the U.S. Offsite Construction Industry
Live · revised Feb 2026

This whitepaper makes the case for open-source connectivity standards across the U.S. offsite construction industry. It sets the framing that became the CfOC-ICC-1220 interface standard.

Read the whitepaper →
Research roadmap · physical standards
Modular interface standard (CfOC-ICC-1220)
Live · drafting v0.2 → v1.0
Seeking $86.5K to complete the v0.2 → v1.0 drafting and committee convenings.
Foundational. Unlocks .CTO and the marketplace · pairs with the UCC legal mateline
CfOC lead: Jason Van Nest (Committee Chair) Partners ICC MBI In talks DPR Uponor
For manufacturers →

Vision

The goal is simple to state and hard to build: a Tier 2 offsite product — a kitchen pod, a bathroom pod, a mechanical rack — arrives at a Tier 1 assembly factory, or even a job site, and just plugs in.

  • A pod kitchen plugs into a modular apartment block on the factory line.
  • A pod bathroom plugs into a traditionally-framed single-family house on site.
  • If an assembler receives a defective pod, they source a better one from a competing manufacturer that fits the same interface — no redesign.

Most industries crossed this bridge long ago. Standard interfaces are what make system-wide interoperability possible, and they are the same technology that makes e-commerce and catalog-based sales work. Construction hasn’t built them yet. This standard does.

Problem

The U.S. offsite industry has never organized open, widely adopted interfaces between its products. Without them, components from different manufacturers are routinely incompatible, forcing custom adaptation that slows delivery and inflates cost: the Engineer-to-Order (ETO) trap of higher prices, more waste, and limited scale.

The threshold to real productization is combining several trades’ connections into one interface: a pod earns its value by ganging plumbing, mechanical, and electrical work into a single, repeatable handoff. Those multi-trade interface agreements have never been worked out across the stakeholders who must honor them: labor, manufacturing, lending, and insurance. The missing capability is interoperability: the ability of a system to work with or use the parts or equipment of another system.1

A National Institute of Standards and Technology study estimated that inadequate interoperability imposed $15.8 billion in annual costs on the U.S. capital facilities industry, spread across designers, contractors, specialty fabricators, suppliers, and owners.2 CfOC-ICC-1220 addresses a physical version of the same problem: offsite products cannot become true catalog products until their connection points become predictable, shared, and repeatable.

The Current Awkward Hybrid

The few modular interfaces that exist today are proprietary, and proprietary interfaces have never driven mass adoption. They survive inside vertically integrated firms and die with them — a common thread among failed modular companies (Katerra among them) is that each tried to own its own interface standard, locking itself into narrow supplier networks and brittle coordination. Some volumetric builders don’t even recognize their internal interfaces as interfaces, treating them as Standard Operating Procedures or guarding them as intellectual property. The result is an industry that re-solves the same connection on every project.

The CTO Marketplace

Market evolution requires replacing clients with customers, and efficiency requires replacing services with products. Industry-wide interface standards are what allow that shift. With them, modular components from different manufacturers integrate seamlessly; standardized couplings let pods, panels, and volumetric structures interoperate; and a durable Tier 2 marketplace can form — firms offering product lines of large building components under Configure-to-Order (CTO) and Select-Variant (STO) delivery, and builders organizing around those products rather than around bespoke scopes.

The Federation Effect in the Market

CfOC-ICC-1220 gives firms a way to make physical interfaces mutually reliable. A manufacturer that adopts the standard becomes easier for builders, inspectors, designers, and other manufacturers to trust because the connection point is no longer a private assumption buried inside one project team’s drawings. It becomes a public rule.

The CTO marketplace depends on many firms building different pieces of the same building system. No single manufacturer needs to control the whole chain. Each firm gains strength by making its products easier for the rest of the market to accept, connect, inspect, and reuse.

Where We Are: Drafting v0.2

The CfOC is an ANSI-Accredited Standards Developer, working in partnership with the International Code Council (ICC) as co-publisher. A seated Consensus Committee — chaired by CfOC Executive Director Jason Van Nest — is actively drafting the standard under ANSI’s consensus procedures.

As of the v0.2 internal committee draft (May 2026), the framework is taking concrete shape. The draft establishes a 3-inch Modular Dimensional Unit as the coordinating grid; a two-sided interface coupling-assembly model, in which a single manufactured assembly presents a host-building side and an off-site-product side rather than two halves joined in the field; and prescribed rules for interface location, clearance, and access. That framework is applied to three building systems in this edition — plumbing, mechanical exhaust, and electrical service — and is closed out by a sequence-neutral testing, inspection, and acceptance chapter that works whether the building side or the product side is finished first. Fire and life safety interfaces are reserved for a future edition, so the first standard can ship with the systems that matter most to repeatable pod connection.

The path to publication runs in phases. Phase 0 launched the effort with a 2024 whitepaper and ANSI membership. Phase 1 secured ANSI Accredited Standards Developer status and the ICC co-author agreement. Phase 2 seated and scoped the Consensus Committee. Phase 3 — where we are now — is active drafting and committee convening, producing v0.2 on the way to a balloted v1.0. Phases 4 through 6 carry the standard through public feedback, pilot deployment, and a final ballot to national rollout.

PhaseMilestoneStatus
0Launch whitepaper & framing✓ Done
1ANSI ASD approval · ICC co-author · PINS✓ Done
2Consensus Committee seated & scoped✓ Done
3Drafting the standard — v0.2 (May 2026)● In progress← we are here
4Public feedback & revisionsUpcoming
5Pilot deploymentUpcoming
6Final ballot & rolloutUpcoming

How It Connects

1220 is the physical foundation of the roadmap. The Configurator File Type (.CTO) and the configurator marketplace are built directly on the interfaces it defines — without a standard handoff, there is nothing for a configurator to configure. It pairs with the Common-Law-to-UCC “legal mateline,” which governs the same handoff in contract and ownership, so the physical and legal seams line up. And the standard isn’t being written in a vacuum: its interface definitions are already being exercised against an early commercial configurator — a real-world check that the rules translate into products a buyer can actually order.

Funding

The CfOC is pursuing a blend of industry sponsorship and grant funding to carry 1220 from draft to published standard. Funding conversations are currently underway with industry sponsors — including DPR and Uponor — whose participation aligns the standard with the manufacturers and builders who will adopt it. Grant applications are also in review. The full effort is costed by phase below.

PhaseEstimated cost
1 · Framing & recruitment$45,400
2 · Kickoff & charge authorship$61,200
3 · Drafting & convenings$86,500
4 · Public feedback & revisions$115,500
5 · Pilot deployment$172,300
6 · Final ballot & rollout$91,100
Total$572,000

Key Outcomes

A widely adopted, nationally recognized Modular Interface Standard makes it dramatically easier for developers and contractors to specify and procure offsite components — and clears the way for an e-commerce (and agent-compatible) pod marketplace that delivers faster, more affordable multifamily housing at scale. Specific outcomes the standard is built to unlock:

  • HUD adoption of the standard and pod-based workflow in its granting programs — first in pilots, eventually by default.
  • Nationally recognized private developers adopting the standard as a procurement specification.
  • Industry presentations featuring the standard as a primary driver of lower cost, less on-site labor, and faster delivery.
  • Lending and insurance products that reward use of the standard for removing technical and legal uncertainty.

Key Partners

  • International Code Council (ICC) — co-publisher and standards-development partner.
  • Modular Building Institute (MBI) — mobilizing manufacturer and builder participation.
  • CTO Housing Alliance — advocates for Configure-to-Order delivery in multifamily housing.
  • Industry sponsors (in conversation) — including DPR and Uponor.
  • Pod manufacturers, MEP engineers & architects, general contractors, and public-sector advisors — contributing technical input and adoption pathways.
  • ANSI — accreditation body for the consensus process.

Key Idea

Every CTO tool lowers the cost of trusting another firm. This standard binds the factory and the job site.

  1. Interoperability.” Merriam-Webster.com Dictionary, Merriam-Webster, https://www.merriam-webster.com/dictionary/interoperability. Accessed 21 Jun. 2026. ↩︎
  2. Chapman, R. (2005), Inadequate Interoperability: A Closer Look at the Costs, ISARC 2005| 22nd, Ferrara, IT (Accessed June 21, 2026) ↩︎