A Systems View of the Building Process

The Integrated Building Process Model (IBPM), developed over 20 years ago, provides a very valuable framework for the processes performed to deliver a facility project. This model defines, in generic terms, a series of processes performed when planning, designing, constructing and operating a facility. The facility could be a building, road or industrial facility. The overall goal of this model was to outline a framework for supporting the implementation of technology into the process.

It is now time to revisit this model to determine how we can use, and modify as needed, this foundational model of the facility delivery process. By integrating this model, along with more recent modeling efforts performed for specific Information Delivery Manuals and the BIM Project Execution Planning Guide, we can organize the development processes and information exchanges throughout the lifecycle of a facility. This will require a new, systems view of the process which was not originally embedded into the IBPM, which dives into a level of detail that allows for specific, system level detail. For example, one of the most detailed Information Delivery Manuals is the Precast Concrete IDM led by Chuck Eastman's group at Georgia Tech. This highly detailed IDM discusses the specific processes for designing, fabricating and constructing precast concrete elements for a project. Currently, these detailed processes only tangentially map into the IBPM processes, but a more detailed structural system process element breakdown could be developed to explicitly map these processes into the larger process for a project.

There will be some clear challenges in developing the process which will require some innovative solutions. Some challenges that are envisioned include:
1) The need to allow for variations in the process based on project characteristics including delivery approach, facility design, team member standard procedures, and other characteristics.
2) The common definition of systems that is all inclusive. The Omniclass classifications will assist in this area.
3) The organization of a process map that is easy to understand and modify by the project team while remaining adequately detailed to drive the process automation.