At substantial completion, an operations team can receive information it can use or another set of records it has to rebuild. Ian McGaw called that moment day zero. In one 2019 healthcare example, documents, asset records, and federated models were loaded into the owner's management systems so facilities, real estate, and clinical engineering teams could begin using them.
Day-zero readiness does not begin at turnover. It begins when the owner chooses the operational outcome the project information must support.
Let the operating outcome set the requirement
Ian McGaw began owner conversations by asking whether the priority was space, asset, or energy management. A general interest in all three was not enough to define the data requirement.
Different facilities also needed different information. An office and a hospital did not manage the same assets, spaces, or reporting needs. Ian used COBie as a starting point when an owner had no standard, then adapted the requirement to the facility and owner.
Join the plans across the lifecycle
Ian McGaw described strong design and construction execution plans that were not connected to one another or to the operations phase. His lifecycle execution plan covered design, construction, turnover, and the use of information after the building began operating.
The document itself became shorter as his team learned. The purpose was not to create more instructions. It was to make the handoffs and requirements manageable enough for the people carrying them through each phase.
Use a limited data set to learn what the owner needs
The healthcare work included several pilots and multiple owner divisions using different management systems. Ian McGaw described a limited-data approach that focused on a minimum set of attributes while the owner clarified which assets and information it wanted to track.
The pilots let stakeholders see what was easy, medium, or hard to deliver and gave the team a place to adjust the process. Those pilots belonged to one organization in 2019, so the lessons could guide its adjustments without becoming a universal implementation result.
Protect continuity before adding another tool
Ian McGaw identified interoperability problems when models and data moved between design and construction systems. He also warned against introducing a shiny technology late, especially when an owner had a poor experience with BIM in the past.
His priority was the information. Ian said, “I think that the data is really what we're driving at.” Models, visualization, and new interfaces could support that data, but they could not replace the continuity required to produce and hand it over.
Define the day-zero outcome before listing the data. From that receiving need, trace back to the design and construction decisions required for the information to arrive complete, understandable, and ready for the operations team.
Day zero works when operations receives a usable record, not another reconstruction project.
