Information Governance & Digital Delivery

The problem

The National Institute of Standards and Technology estimated the annual cost of inadequate interoperability in the U.S. capital facilities industry at approximately $15.8 billion in 2002 dollars, roughly two-thirds of it borne by owners and operators, predominantly during operations and maintenance. The cost of information failure is paid mostly by whoever inherits the building.

This failure persists on projects that did everything the technology literature recommends. Pishdad-Bozorgi, Gao, Eastman and Self documented a $113 million, 200,000 square foot university research facility that had a formal BIM Execution Plan, required COBie, and operated under a collaborative delivery philosophy, and whose automated import into the maintenance management system still failed at handover (Automation in Construction, 87, 22–38). The cause was not a missing standard. It was the absence of early lifecycle data governance and a schema that did not align with the receiving system.

What governs this area

• ISO 19650-1/-2:2018Information management across the asset lifecycle; the delivery phase.
• ISO 31000:2018Risk management principles applied to information exposure.
• COBie / NBIMS-USStructured handover data for operations.
• BIMForum LOD SpecLevel of information need, by element and by stage.
• AIA E201/E202/G203-2022Current digital practice suite, superseding the 2013 documents.
• GSA P100 · USACE ECB 2018-7 · DoD UFCBinding federal digital delivery requirements.

The decisions it comes down to

1. What asset information will operations require, as data rather than as documents?
2. Which party is accountable for each information container?
3. What level of information need applies to each element, at each stage?
4. What states exist in the common data environment, and who authorizes each transition?
5. Who may read, edit and issue within each state?
6. What check must a container pass before issue, and who performs it?
7. What happens to superseded information?

The requirement landscape

Digital Delivery Is Already a Federal Requirement

GSA · USACE · NBIMS-US · every citation below verified against official published documents, August 2026

Digital delivery on U.S. public work is not an emerging trend to be watched. It is a procurement requirement with more than twenty years of history, thresholds in square feet and dollars, and deliverables written into contracts. And the firms it now reaches are precisely the ones least equipped to interpret it.

1. The civilian mandate: GSA

The General Services Administration, the federal government’s civilian landlord, established the National 3D-4D-BIM Program in 2003 through its Public Buildings Service. The first hard requirement followed for fiscal year 2007: “a spatial program BIM will be the minimum requirement for all major (new and modernization) projects” submitted for final concept approval. The current facilities standard, P100 (2024), states the present tense plainly: “GSA has required the use of BIM in design and construction in various ways since the 2009 P100,” and today “all new-construction, major repair and alteration projects are required to submit BIM deliverables throughout the project period, at multiple milestone points …”, with an Industry Foundation Classes-based submission required alongside each native-format submission. A numbered guide series, seven of them published, accompanies the program; Guide 08 (2011) extends the requirement past construction into facility management data.

2. The military mandate: USACE

On the defense side the requirement is broader and newer. The U.S. Army Corps of Engineers’ ECB 2018-7 (current revision September 2025) is categorical: “The use of advanced modeling processes and related technologies for design and construction are required as described herein.” The thresholds are concrete: military projects over 5,000 gross square feet and $3 million, and civil works projects over $3 million, must comply. Compliance is contractual, not aspirational: the Corps’ contract language, its Project Execution Plan template and its Minimum Modeling Matrix “must be incorporated into all projects that meet the minimum thresholds …” and for architect-engineer designed work the modeling execution plan “is a required submittal.” Deliverables run from native design models through “record drawings (PDF) and BIM and/or CIM record models through construction completion.” In May 2026 the Corps consolidated the practice in a dedicated engineer manual, EM 1110-1-4017, Advanced Modeling for Digital Project Delivery: the execution plan “must be included in the Design Analysis” for all projects, and record models “must reflect all approved changes during construction including red-lines, requests for information, and contract modifications …”

3. The standard underneath: NBIMS-US and COBie

Beneath both agencies sits a consensus national standard. The National BIM Standard-United States, published by the National Institute of Building Sciences, reached Version 4 in 2023 with four modules: project BIM requirements, BIM execution planning, BIM use definitions, and COBie Version 3, the construction-to-operations information exchange. COBie’s stated purpose is the exact failure this practice area exists to prevent: capturing and delivering asset data “with the goal of reducing or even eliminating the delay between handover (after design and construction) and when the facilities management system can begin the operations and maintenance of those maintainable assets.”

4. Why the mandates alone do not close the gap

Every document above specifies deliverables. None of them, by itself, produces the governance that makes deliverables trustworthy: the peer-reviewed record includes a $113 million facility with a formal BIM execution plan, COBie required, and a collaborative delivery philosophy, whose automated handover into the maintenance system failed anyway (Pishdad-Bozorgi, Gao, Eastman & Self, Automation in Construction, 2018). The lesson generalises: a requirement without an owner, a verification step and an access regime is a format, not a governance system. Read as governance, the federal stack maps exactly onto the decision chain this area sets out: information requirements belong in the appointment; the execution plan is the delivery team’s binding response; the common data environment needs defined states and authorities; and handover data is derived from what operations will need, not from what was convenient to model. That translation, from mandate to decisions a project team can actually make, is the work of this practice area, and it matters most for the small and mid-sized firms that now meet these requirements on federal work without a BIM department to interpret them.

5. The lawyer’s reading of the standard

The gap between mandate and governance has a legal literature of its own, and it says what this chapter says, from the profession that litigates the failures. A published legal analysis of the ISO 19650 series (Winfield, 2020, in the Institution of Civil Engineers’ Management, Procurement and Law) credits the standard as “a game changer in standardising the process of digital information management,” and then draws the line that matters: the series was “written primarily by technical, rather than legal, authors.” Her working example is the status codes of the standard’s UK National Annex, under which a “shared” information container is labelled non-contractual and a “published” one contractual, even though “the term ‘non-contractual’ is not used in the normal legal context”: unless the contract itself states which containers amount to deliverables, the labels cannot be relied on, and the analysis sees “confusion, potential delays and additional costs” where that allocation is missing, precisely what this chapter’s decision chain exists to prevent. Her verdict is the sober one: the standard “should not be considered the panacea,” because it “does introduce some potential legal uncertainties of its own” that must be resolved through binding contractual terms. A technical standard and a contract are written in different languages. Information governance is the discipline of making them say the same thing.

Basis

Writing in this area