Chapter 8
In This Chapter
Explaining the importance of collaboration
Creating the employer’s information requirements
Considering the BIM execution plan
Setting up the common data environment
Effective collaborative working methods rely on many things such as soft skills inherent in individuals working in the project team, communication, and a desire by all to succeed. Pursuing a culture of integration and encouraging the right behaviors is vital; after all, BIM is just as much about a behavioral change program as anything else.
Effective processes and protocols are essential if the project is to be a success. Today’s built assets involve a wide range of digital technologies during the whole project timeline and in producing project information. Throw the many ways and methods in which people communicate into the mix, and you can clearly see that users require clarity from an early stage if BIM is to be effective.
This chapter looks at the different elements that are required to make an efficient and effective collaborative working environment, which is right at the heart of BIM.
Collaboration is all about working together as a team to undertake tasks that achieve a shared goal. To produce better outcomes, the construction industry needs to develop better and more efficient ways of working and communicating in order to deliver better built assets. Technology and processes have evolved over time, and the construction industry has a fantastic opportunity to harness these developments in BIM. When you set up a collaborative workflow, you need to consider
Figure 8-1 shows these key aspects of developing a collaborative working environment. Referred to as the Onion Diagram, it shows that you can’t consider one aspect in isolation; rather, each part must have a regard to each other, with each part having an effect on the other. For example, if you consider information exchange, you use digital tools such as BIM software to produce digital data. This digital information is exchanged using defined processes that comprise managed and agreed data drops and exchanges during the project’s lifecycle. To make BIM effective, all project team members need to operate in a culture and ethos of collaboration and sharing.
When you think about a digital model, you may initially think of its 3D geometry and what it looks like. This assumption is fair given the fact that physical architectural and construction models have been around for centuries.
However, in a BIM context the model is actually an information model made up of documentation, graphical information, and nongraphical information. Some of this information may live deep within the property of a BIM object or live in an associated document completely outside the BIM platform environment, such as a report or a survey. The following models go through a series of iterations depending on their intent.
During the design and construction phase, the project information model (PIM) starts out life as a design intent model, showing the designers’ intentions. The project team then progressively develops the PIM across the project stages into a virtual construction model, after which the project team transfers the ownership to the construction suppliers until handover. The information manager delivers information to the employer via information exchanges. Usually, the information manager defines these information exchanges and sets them out within a scope of services document, and they correspond to important decision-making points that the client needs to action.
The asset information model (AIM) is a single source of validated and approved information that relates to the built asset, and clients, end users, and facility managers use it for the operation and in-use phases. It may relate to a single asset, a system of assets, or the entire asset portfolio of an organization. The AIM provides a fully populated asset data set that can feed into computer-aided facility management (CAFM) systems.
The asset management team can derive information in the AIM from a number of sources, such as:
Include the following in your AIM:
The BIM toolkit provides the tools to review the teams’ submission and identifies where the client’s information requirements have or have not been met. If there are errors or omissions, the BIM toolkit will identify them and allow the user to return to their BIM tool and correct them. This saves wasted time by avoiding the client receiving incorrect submissions. To allow the BIM toolkit review process to be carried out in all types of organization, both a cloud version and a standalone, in-house version are available. After a submission is ready, it’s passed on to the validation tool, which produces a simple spreadsheet report indicating the contents of a file and its compliance.
You may think of the model as a single entity, but it’s actually an assembly of distinct, interlinked domain models each produced by individual contributors. These models then come together to create a complete picture of the asset. In the future you’ll be working on a complete integrated model; however, for the time being we’re talking about a federated model. Think of a federated model as a number of consultants’ drawings, with the information subsequently transferred to a single master set.
In the following sections we discuss the central place in which the models and information are brought together, known as the common data environment (CDE) and the benefits that it brings.
The information manager carries out the process of managing these assemblies of models back and forth between the project team within one shared environment known as a common data environment (CDE). A CDE is simply a place in which the project team shares information about a project, which therefore allows all information to be based upon a single source of truth. Although this information is shared and can be reused, its ownership still remains with its originator, the only person who can alter, change, or update it. This approach relies on a much more rigorous process of structuring data because others are reliant upon it. Issues such as file naming conventions and origin points become very important, but the benefits are that the project team can better use information in both construction planning and activities later in the project.
In most cases, work in progress (WIP) is within the supply chain systems. Not until information is shared or published does it go into the client’s system.
After information goes through an approval stage, including a number of checks — the nature of which depends on the type of information and the point at which the project team adds it (referred to as an approval gate) — the information manager then makes this information available in a shared location, usually a published section of the CDE, where other members of the team can access it. The information manager may archive information that has been superseded for future reference.
A CDE could be a project extranet or a project server, and may contain useful features such as version control, search functionality, markup functionality, and the ability to control access rights through administration settings. Some CDEs can further promote the ethos of sharing and collaboration by including co-authoring functionality, survey tools, blogs, and web pages.
Model viewing software, also known as model integrators, allows you to combine a number of models so that they can be viewed as a whole. Even though some software tools for collaboration and construction management have this function built in, standalone model viewers are available, many of which are free. In Chapter 11, we discuss more about open data standards and IFC, but in the meantime it’s important to remember that these open standards such as IFC are important because many viewing tools use IFC information. Chapter 21 examines model viewers and checkers.
Protocols, standards, and processes are the essential foundations when setting up a collaborative BIM workflow. Other considerations to think about include the physical environment and how teams will integrate with each other; for example, co-locating teams, a cave automatic virtual environment (often just referred to as the acronym CAVE), and big rooms where the entire project team can come together to share best practice, knowledge, and ideas.
The world is built on standards that help drive innovation and increase productivity. On a more rudimentary level, these protocols make life easier. For example, interoperability standards such as food labeling let you clearly understand the nutritional value of the food you buy.
In the context of the digital world, standards allow you to create, use, and maintain information in an efficient way. They not only encourage best practice, but they also offer a means to achieve real improvements. Sharing construction information, drawings, specifications, and schedules in an agreed and consistent manner can bring about savings in cost and reduce waste.
In order to convey a clear message as to what digital information should be delivered, the information requirements (IR) should be documented. Then the whole project team knows what to supply and the client knows what she is getting. In the next sections, we look closer at employer’s information requirements (EIR) and how the supply chain responds to this request for information via the BIM execution plan (BEP).
Information requirements need to be defined as part of the EIR, a pre-tender document forming part of the appointment and tender documents on a BIM project. The EIR sets out the information that the supplier will deliver and the standards and processes the supplier will adopt, as part of the project delivery process. The client (or the client’s adviser) develops the EIR, and it’s crucial to the BIM process in that client uses it to describe precisely which models she requires on a project and what the purpose of those models will be. The EIR defines which models need to be produced at each project stage — together with the required level of detail and definition. These models are key deliverables in the data drops, which are packets of information shared at strategic milestones along the project timeline, contributing to effective decision-making at key stages of the project and ensuring the whole project team has access to the latest information. The content of the EIR covers three areas:
The EIR is informed by the organizational information requirements (OIR) and asset information requirements (AIR) plus data needs to support interim decision-making.
Ideally, the EIR should advocate the use of open standards and specify the use of ISO 16739 for the exchange of model data. Doing so allows the client to select competing project teams based on her competency rather than the BIM platform being used. The compelling argument for using IFC is that newer versions always open older versions, so they’re ideally placed for achieving open file formats. IFC is going to be fundamental to achieving BIM Level 3 and an environment where everyone can work from a single integrated model. This may not happen for some time, but you can start to prepare for these data transactions now.
Include the following in your plan:
The BEP is an important and useful document, even on a small project. Because BIM is enabling a faster design process, the need to consider software and hardware requirements, information exchanges, and how you plan to communicate with others has become even more important.
Essentially, the BEP is the supplier response to the questions and requirements set out in the EIR. Its purpose is to outline the vision and provide information and guidance to the project team to aid understanding and communication and so achieve a more collaborative process. A good plan indicates how the project team will produce and manage information and explains how the supplier will carry out and deliver the BIM project.
A number of templates and guidance documents can get you on the way to completing your BEP. The Construction Project Information Committee (CPIC) provides BEP templates for both pre- and post-contract as a free download at www.cpic.org.uk/cpix/cpix-bim-execution-plan
.
The Pennsylvania State University Computer Integrated Construction (CIC) research program’s BIM Planning website (http://bim.psu.edu
) has developed the BIM Project Execution Planning Guide, which is available as a free download. The guide was a product of the buildingSMART alliance (bSa) Project “BIM Project Execution Planning.”
The supplier prepares a BEP with the following:
Pre-contract: Submitted at tender stage, pre-contract, to address issues in the EIR. It demonstrates the supplier’s proposed approach, capability, capacity, and competency to meet the EIR. It provides a way for the client to assess the supplier’s BIM credentials, resources, IT, and any other BIM project experience.
Information the supplier provides in the pre-contract BEP should be sufficient to enable the employer or client to review the supplier’s BIM credentials so that she can make a selection or appointment. Include the following in your plan:
The employer uses the PIP to assess capability, competence, and experience of potential suppliers bidding for a project, along with quality documentation. It’s essentially a statement that relates to the supplier’s IT and human resource capability to deliver the EIR.
The principal supplier is responsible for obtaining enough information about the supply chain to assure that it has the appropriate capability to meet the requirements set out in the contract and the EIR. Resolve any potential problems or issues around interoperability and information exchange as early as possible, ideally before the design commences. If the IT assessment highlights an incapability, in that files can’t open, read, or analyze models from the different teams, then drawing production will be difficult to achieve.
After the client awards a contract, the project lead usually calls an initial meeting to collaborate and develop the MIDP made up from the team members’ TIDP. The following sections take a closer look at these two forms.
The main contractor uses the MIDP to manage the delivery of information during a project. It lists the following information deliverables for the project:
The TIDP is a federated list of information deliverables that are broken down by each task, including format, date, and responsibilities, and it forms part of the BEP. The main contractor should use the information within the TIDP when working out the required sequence of model preparation for any work packages used in the project.
The contractor uses the TIDP to
Having a protocol in place sets the foundations for everyone to work collaboratively and exchange information. Protocols can also put in place robust quality assurance (QA) procedures.
In response to the UK government’s BIM strategy, the Construction Industry Council has published the CIC BIM Protocol (together with other supporting documentation). This free-to-download guide (http://cic.org.uk/publications
) is concise at only eight clauses long, but highlights the minimum legal and commercial requirements that apply when using BIM on a project, clarifying rights, responsibilities, and liabilities of each party involved. It also features a prototype production and delivery table to clarify which models the client requires at different stages of a project, who’s responsible for the information at each data drop or work stage, and the required level of detail.
18.219.249.210