Why unique? Because it was...
- an event organised by three (Graham Stewart @ Ramboll, Ray Purvis @ Atkins and Rob Clark @ Excitech) of #UKBIMCrew for #UKBIMCrew
- a free event without any hidden 'marketing' agenda
- an event focusing on the reality of BIM rather than all the fluff around it
My takeaways of the day:
- Employer's Information Requirements (EIR) is a must have document on any BIM project
- Information Manager role should be carried out by a Design Lead until a Main Contractor is appointed. The Main Contractor should undertake Information Manager role upon appointment or appoint a member of that project team to carry out the Information Management task.
- Design team should work with 'clash avoidance' in mind as part of their day to day 'BIM' work; removing the need for a third party to perform 'clash detection' for the team. This is not to say that we don't need overall/project wide Information Management.
- IFC, there are still some reservations in the industry mainly due to software vendors' implementation of it. Most of attendees expressed their concerns about loosing information (graphical and/or non-graphical) when exporting IFC from different sources.
- COBie, still a concept. May not be practical on complex / large jobs. Personally, I yet have to see a useful case study where COBie and data drops are used throughout the project life cycle as COBie is intended to be used.
- Asset Information, It is still not clear where, how, who adds these information. Is it useful to *manually* add this information in BIM model and then extract it into a COBie or is it better to *manually* add this information straight into COBie or Asset Management database and link 3D BIM geometry to it? Personally, I *think* the later is more useful and efficient.
- LOD, a detailed breakdown of BIM model elements such as AIA is preferable specially for responsibility matrix; i.e. who own concrete stair, slab etc. and what point the ownership is transferred
- BEP, BIM Execution Plan is the most important document and should be an evolving document starting it's life as a Pre-Contract document (mainly design team, client and QS involvement led by the Design Lead) and then becoming Post-Contract document once a Main Contractor is appointed (involving design team, key sub-contractors, client, QS MC etc, led by the Main Contractor)
- BEP, QS's input is useful to define modelling requirements for quantity take-offs
- Main Contractors input/involvement in overall BIM process is paramount. Design team should start sharing their models with Main Contractors like they do with design team members, with caveats if required, to encourage contractors' involvement.
Thanks @StewartGH1970, @Clarkrob and @RayPurvis for organising this event. Look forward to see more of this.