Chapter 8

Setting Up a Collaborative BIM Workflow

In This Chapter

arrow Explaining the importance of collaboration

arrow Creating the employer’s information requirements

arrow Considering the BIM execution plan

arrow 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.

Getting the Lowdown on Collaboration

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

  • Culture and behavior
  • Process
  • Digital tools
  • Form of contract

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.

image

Illustration by The BIM Task Group

Figure 8-1: The BIM Onion Diagram.

Modeling in the Parametric Domain

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.

Project information model (PIM)

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.

tip Include details of the arrangement and timings for the transfer of ownership of the PIM from the design team to the contractor in the conditions of engagement or contracts between the employer and supplier.

Asset information model (AIM)

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:

  • Existing information and data transferred from existing organizational systems
  • Recognizing or relabeling an existing data and information store
  • New or updated information and data from surveys of the physical asset
  • Information and data from the PIM

tip The information manager should authorize, validate, and accept information before the asset management team can rely on it as part of an AIM. The authorization and validation processes should follow any principles set out in an information management process.

Include the following in your AIM:

  • Information concerning the original brief, specification, design intent, and analysis relating to the original installation of the asset and any subsequent changes
  • 3D object-based models of the environment and location of the asset
  • Information, or links to information, concerning the ownership of the asset and any rights or covenants associated with the asset
  • Information, or links to information, concerning data obtained from the maintenance, survey, or other work carried out on the asset during its lifetime
  • Information, or links to information, concerning data obtained from monitoring the operation and condition of the asset

warning Just like a vintage classic car, information about its past owner history and service records may be incomplete or even missing. The information manager is responsible for receiving and inputting information into the model in compliance with agreed processes and procedures. Through BIM, information can be provided to a standard data structure, which increasingly allows project teams to digitally verify that the information that is being requested has been delivered. The information manager should validate compliance with the information requirements and advise on any areas of noncompliance. An employer defines what she wants to receive as structured data, and the delivery team develops a proposal and submits a BIM in industry open standards such as IFC or COBie.

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.

Bringing it all together

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.

Eyeing the common data environment (CDE)

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.

remember The benefits and advantages of a CDE are as follows:

  • Shared information reduces time and cost. Sharing information means that another consultant or project team member doesn’t have to model essential base information again.
  • Ownership of information remains with the originator. Imagine that the structural engineer is reviewing the architectural model and she discovers that when the structural model is combined or overlaid with the architectural model, a structural column runs straight through the middle of a window. This now involves some good, old-fashioned dialogue between the architect and structural engineer as to what course of action the project team should take. Although the team shares and reuses information, only the originator of the information can change it. For example, if the structural engineer decides that the window configuration is going to change to accommodate the structural column, then only the architect can change her model.
  • The project team can generate multiple documents from different combinations of files. Unlike traditional CAD, a section or elevation is simply a selected view from the model. Think of your digital music library that you may have on your MP3 player, phone, or computer. The information about each song is tagged with information such as artist, year, and genre, and so you can choose to listen to all country music, or perhaps Elvis is more your type of thing.
  • Version control and easy distribution provides everyone with up-to-date information. Coordinated information means the project team is working on a single source of truth. It also means that the team isn’t only working from the same information, but is also working on the latest version of that information, reducing the risk of working on an out-of-date floor plan or superseded elevation.
  • Others can use information for downstream activities. These activities include planning, estimation, cost planning, and facilities management.
  • Information is safe and secure. Data is stored securely, usually on a remote cloud server with monitored and controlled access.
  • Information can be archived. The CDE can store previous revisions away in a digital vault, rather than the traditional physical filing and drawing cabinets. Digital information contains metadata, and so clients, end users, and facility managers can locate information quickly with a simple search function.
  • The postal service is relied on less, which reduces cost and saves time. The great thing about digital uploads/downloads and electronic correspondence is that they’re almost instantaneous. You can upload or download information easily at the push of a button, essentially making the postman and those expensive stamps a thing of the past.
  • Dispersed teams can work together regardless of where they’re based. The age of the Internet opened up a global economy, and now purchasing something from the other side of the world using your laptop and your flexible friend (credit card) is easy. The sharing of information and communication via one central place means that project teams no longer have to work in close proximity to one another. Different time zones can, of course, cause a bit of a headache, but whether you’re located in London, Lyon, or Louisville no longer matters: everyone can collaborate.

Combining all the model data

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.

Making Life Easier with Digital Information Management

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).

technicalstuff When the industry went from the drawing board to CAD, BS 1192 (first published in 1998) provided a guide for the structuring and exchange of CAD data. Revised in 2007 and given a new title of “Collaborative Production of Architectural Engineering and Construction Information,” the standard put more emphasis on collaboration so that project team can effectively reuse data. It promoted the avoidance of wasteful activities such as waiting and searching for information, overproduction of information with no defined use, overprocessing of information simply because technology allowed it, and defects caused by poor coordination across the graphical and nongraphical data set that require rework.

Describing the digital information requirements

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:

  • Technical: Details of software platforms and definitions of levels of detail
  • Management: Details of management processes to be adopted in connection with BIM on a project
  • Commercial: Details of BIM model deliverables, timing of data drops, and definitions of information purposes

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:

  • Levels of development — for example, requirements for information submissions at defined project stages.
  • Training requirements.
  • Planning of work and data segregation including modeling management, naming conventions, and so forth.
  • Coordination and clash detection, which is the process of identifying conflicts and issues through 3D collaboration and coordination — also known as interference checking. See Chapter 17 for more information on clash detection.
  • Collaboration process.
  • Any specific information that should be either excluded or included from information models.
  • Any constraints such as model file or attachment sizes.
  • Compliance plan.
  • A definition of any coordinate origin/system (three dimensions) that the employer requires the design team to use to place graphical models; for example, ordnance survey locators, geospatial, and location with respect to an agreed origin.
  • Schedule of any software formats, including version numbers that the supply chain will use to deliver the project.
  • Exchange of information — alignment of information exchanges, work stages, purpose, and required formats.
  • Client’s strategic purposes — details of the expected purposes for information provided in models.
  • A schedule of any software formats, including version numbers that the supply chain will use to deliver the project.
  • An initial responsibility matrix setting out any discipline responsibilities for model or information production in line with the defined project stages. The responsibility matrix sets out the relationships between disciplines and the production of information or models. It outlines who is responsible for what.
  • A schedule of the standards and guidance documents used to define the BIM processes and protocols that the design team will use on the project.
  • A schedule of any changes to the standard roles, responsibilities, authorities, and competences set out in the contract.
  • Competence assessment.

remember The contents of the EIR may also include project-specific items such as pre-construction surveys or a requirement for the employer to receive information models describing newly generated products and assemblies.

tip Public sector employers may not want to (or be able to) specify software packages that their suppliers should use, but may instead specify the formats of any outputs. Private sector employers may choose to specify software packages and/or output formats.

remember An initial responsibility matrix forms part of the EIR, setting out any discipline responsibilities for models or information production in line with the defined project stages. The free-to-use RIBA Plan of Work Toolbox (www.ribaplanofwork.com/Toolbox.aspx) provides a downloadable spreadsheet (in Microsoft Excel format) containing customizable tables, allowing easy creation of the project roles, design responsibility matrix, and multidisciplinary schedules of services. The toolbox also contains helpful guidance and examples.

Demonstrating capability: BIM execution plans

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.”

tip To gain maximum value, make the BEP accessible to the whole project team. Put procedures in place so that any new team members are aware of the core project procedures.

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.

    remember 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:

    • Information required by the EIR: The BEP should respond to the parts of the EIR that specifically require a response. This is likely to include information regarding planning of work and data segregation, coordination and clash detection, health and safety management, and collaboration procedures such as details of meeting schedules and agendas, model management, including filing storage, and structure and modeling requirements.
    • Project information: Such as project name, description, location and critical dates, key project members, project roles, company organization chart, and a contractual tree.
    • Project implementation plan (PIP): Each organization that’s bidding for a project submits this document as part of the initial BEP. Include company organization charts and details of project roles. Refer to the next section for more information about the PIP.
    • Project goals, objectives, and major milestones consistent with the project program: Include project goals for collaboration and information management and how the supplier’s proposals will meet these.
    • Project information model (PIM) delivery strategy: Consider the delivery strategy, taking into account the deliverables, accuracy, and completeness of the design at each stage of the project from brief to in-use.
  • Post-contract: Submitted after the client awards the contract to explain the supplier’s methodology for delivering the project using BIM. The document should provide conformation and reassurance to the client and build upon the details and information provided in the pre-contract BEP. The post-contract BEP contains all the preceding information, plus the following:
    • Management: Details of roles, responsibilities, and authorities, existing legacy data or survey information (if available), and details of how the supplier intends to approve information.
    • Revised PIP information exchange: Now that the client has awarded the contract, the PIP should contain further details of the supply chain’s capability to deliver the project.
    • Responsibility matrix: It should outline the agreed responsibilities across the whole supply chain, task information delivery plan (TIDP), and master information delivery plan (MIDP). Check out the later section “Delivering the promises” for more about TIDP and MIDP.
    • Model QA procedures: Include details of modeling standards, naming conventions, model origin points, and agreed tolerances for all disciplines and change-control procedures.
    • Delivery strategy and procurement: Describe in detail the methods for contract management and the specifics of the procurement strategy and documentation that would need to be referenced for the actual delivery of the project.
    • Communication strategy: Incorporate what types of meetings the project team will have and when.
    • IT solutions and technology: Include agreed software versions, exchange formats, and details of process and data management systems.

Assessing competence: Project implementation plans

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.

warning In this context the PIP relates to information capabilities. Don’t confuse it with a generic project management plan.

remember The PIP should describe and give a summary of the lead party such as the main contractor as well as the supply chain’s capability to deliver the project. A summary of the supply chain’s capability enables the employer to make a quick assessment and comparison. The assessments should cover the following:

  • Supplier BIM assessment form: Completed by all appropriate organizations within the supply chain. It gives an opportunity for the supply chain to highlight any previous BIM experience and what benefits they realized, as well as the opportunity to demonstrate that the supply chain understands the analysis and methods that are proposed for the project.
  • Supplier information technology assessment form: Completed by all appropriate organizations within the supply chain, usually with the assistance of the organizations’ IT departments. It demonstrates the capability and IT resource of the supplier for information exchange in a collaborative environment.
  • Supplier resource assessment form: The supplier uses this to assess the organization’s current resource capability and capacity to demonstrate its capability to deliver the project.

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.

remember A simple BIM capability questionnaire is a good way to help the project team identify any training, coaching, or support requirements that the supply chain may require. The CPIC provides a BIM assessment form as a free download (www.cpic.org.uk/cpix/cpix-bim-assessment-file) that includes a BIM Capability Questionnaire template with 29 questions. The questions were created as part of working documentation provided by the Skanska UK BIM team.

Delivering the promises

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.

Master information delivery plan (MIDP)

The main contractor uses the MIDP to manage the delivery of information during a project. It lists the following information deliverables for the project:

  • Models
  • Drawings
  • Specifications
  • Equipment schedules
  • Room data sheets

Task information delivery plan (TIDP)

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

  • Demonstrate what team member is responsible for each task or deliverable.
  • Indicate that milestones within each TIDP are aligned to design and construction programs to produce the MIDP.
  • Show that each task team manager is responsible for compiling her own TIDP with its milestone.

Singing Off the Same Hymn Sheet: Information Exchange

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.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.219.249.210