Session 1 - Project Kick-Off

Next Page | Previous Page

Some of the points presented here are in context to the Employers Information Requirement document presented for the fictional Shrewsbury Hardware Store project at the event. This document can be downloaded from here

Consensus
Process
  • BS1192:2007 Workflows - In excess of half of the room (show of hands) are actively or currently are adopting BS1192:2007 workflows.
  • The Employers Information Requirements and the BIM Execution Plan
  • Worthwhile - The Employers Information Requirements document is worthwhile and good starting point to a project briefing.
  • Plain English - The Employers Information Requirements must be written in plain English and contain questions to qualify ability against the requirement.
  • Accessible - The accepted format of Employers Information Requirements documents should be easy to follow, understandable and scalable for clients of projects of any complexity or size.
  • FM Teams Involvement - The Facilities Management team should be involved in the initial project set up.
  • BIM Execution Plan - The Employers Information Requirements document should naturally inform the contents of the BIM Execution Plan
  • Single BIM Execution Plan - The team’s response to the Employers Information Requirements Document should be a single BIM Execution Plan.
  • Roles and Responsibilities
  • BIM Manager - This role is defined as an office management role with tasks including giving advice on best practice, provision of content, assessing capability and training and reviewing progress in relation to the project goals.
  • Model Ownership
  • Liability Through Project Indemnity - The liability of the project should be managed through project indemnity. Mervyn Richards went on to explain later that insurance companies are happy with the CIC advice.
Suggestions
Ownership
  • Model Ownership
    Please note the Ownership section is presented as understood by the attendees of the conference only. It does not form any form of contractual or legal advice.
    At the event, it was suggested a number of times that the “client owns the model”. Although there was some objection to this statement, including, “the client does not own the model, they are licenced to use it for the intended purpose, and the ownership resides with the author. If you buy a book, you do not own the rights to that book, you only own it to read and that is the licence you enter into. To state that the client owns the model is to imply that they can use it for whatever purpose they like, which they cannot.” It was pointed out the new CIC BIM Protocol does cover this in Clause 6, however it was felt by some that the current wording would need to be revisited. Ultimately, there seemed to be consensus that the client would be able to unhindered utilise the model for operational purposes for the project asset. However there is concern how this particular point is conveyed. Typically this concern lies in implying that the model could be utilised on other similar construction projects the client undertakes.
  • Process
  • Employers Information Requirements / BIM Execution Plan / Master Information Delivery Plan - “This should be consolidated into a single document” Although it was also questioned how this would work in practice, “the Employers Information Requirements are written by the client, BIM Execution Plan by the 'Team'. The Master Information Delivery Plan is sometimes a joint effort between the client and the team”
  • The Employers Information Requirements and the BIM Execution Plan
  • Timeframe - The Employer Information Requirements “should contain time frames for delivery”
  • More Information - The Employers Information Requirements “should contain more information regarding a client’s deliverables” and “why” they need certain information.
  • Product Register - Product preferences should be included.
  • Sustainability Information - The Employers Information Requirements should contain sustainability aspirations of the client.
  • Information Delivery Plan - The Employers Information Requirements should contain a plan of “who will supply what”
  • Standard Clauses - “In a normal project, this happens then, that happens then” which gives you a clear opportunity to change these to show how this differs from a normal project.
  • Digital Plan of Work - The Employers Information Requirements should make clear what asset data is required at what stage. For example “I want these 10 fields of COBie data at data drop 1, and these 5 at Data Drop 2”
  • Asset Information
  • Make COBie friendly - COBie data needs a “client friendly interface”
  • Roles and Responsibilities
  • Information Manager - Some defined this as a client representative that will check models, equivalent to Project Quantity Surveyor (PSQ). It was noted that in 3.1 of the CPIx Post Contract Execution Plan this role is to “enforce the Project BIM Standard” and ensure delivery of the Information requested in the Employers Information Requirements”. It was suggested by some that the key words are “ensure delivery”.
  • “Roles Are Not People” - It was suggested one of the main confusion areas in roles and responsibilities is that the roles are not defined by who does them, but the tasks themselves. Therefore in some instances the same person can wear many hats, whereas in other instances more than one person may be required to fill a role on a project.
    Main Challenge Areas
    Roles and Responsibilities
  • Roles - There is still a significant amount of confusion about what these roles are and how they are defined. Who does what? The industry seems to be seeking clarification here, particularly for the Information Manager and Task Team Manager. It was suggested by some that these roles are however clearly explained, for example the Information Manager is listed in the CIC BIM Protocol
  • Task Team Manager Push Back - This is a role in PAS1192:2013 process. Many believing the new title is not required and that it is a BIM Coordinators or Model Managers role. Some suggested that this was one of Data Validation, and that this person(s) would be responsible for ensuring models are shared effectively.
  • Federated Model Responsibility - Lack of clarity on who is responsible for production of federated models. It was suggested the main contractor should be by some. This was discussed in greater detail in Session 3, Construction and Operation.
  • CDE Responsibility - “CDE should be provided by the main contractor”, “CDE should be hosted by the team”, “We took it that we would host the CDE”. General confusion on who is responsible and what it needs to look like. Although, equally it was suggested this is no different to existing process and that there is no “one fits all” solution.
  • Standards and Protocols
  • Industry Foundation Class - “Its equivalent to print portals, you don’t know what is going to be spat out”. It was stated that IFCs are improving “monthly” and that the authoring and importing software is more likely to blame than anything, however there continues to be a trust issue. However equally others have suggested there is nothing wrong with the IFC format and that we should be utilising it as an interoperability standard. It was also suggested the onus was on everybody to push software vendors for improvements.
  • Uniclass 2.0 “Aspirational” - “They are releasing all of the tables except the ones you use”. You need to understand its limits. “The BIM Execution Plan should not be afraid to challenge the use of Uniclass”.
  • Frequency of Information Exchange - There was significant debate on when information should be transferred and in what manner. It was felt that daily had its advantages in collaborative workflow, especially when working in the same company. Some even live sync models. However some felt once of week reduced the risk of abortive work.

Next Page | Previous Page