Print

Building Information Modelling or "BIM" is a "new term" for what is being hyped as best practice in construction for the next several years.

However, Best Practice has been around for a long time ... so what does BIM have that we haven't had before ?


15th May 2014 - Quote from New Civil Engineer magazine [in Association with - whose buzz word in the article heading is "Sustaining Infrastructure"]

Quote

About 80% of what BIM is about is passing on information and data associated with models in a structured way.

End Quote

One cannot but help ask the question "But what about all the other relevant and critical information ?" In particular when an item of information [which may be part of a model] is Approved for Construction, and then vitally when it is Issued for Construction. AND this must be done in a manner which is legally admissable - viz when all goes wrong just who is a Judge going to believe ? THAT is the key question.


First an examination of what Best Practice in Construction Engineering Management Document Control [CEMDC] has meant to date - that includes the whole gamut of bringing a project from inception to completion of construction, and operation, and in some cases to its removal - such as for an oil platform. It will include the manuals for operation as well as suggestions for removal. 

Heery International, a project management firm involved with major complex projects was a partnership between Balfour Beatty and Heery Inc. The second phase of the development of TDOC was done to meet their specifications, and to meet the best practice as outlined in their sales brochure. 

The TDOC copy of these documents are as follows: 

There are a number of operational questions covering document control - by which is meant the management of information on a construction project - or CEMDC:


So where did BIM come from ?
 
The first thing is to correct the name: it is not BIM, but Construction Operations Building Information Exchange (COBIE)
 
The answer from where the idea came is simple: the worlds largest procurement agency - namely the US Department of Defence.
 
It is worth re-iterating the main objective, and its consequences: 
  • The purpose of COBIE is to improve how information is captured during design and construction, and then provided for operations, maintenance, and asset management purposes.
  • COBIE eliminates the need to create and transfer boxes full of paper construction documents to facility operators following completion of the project.
  • COBIE also eliminates the need for post ad hoc as-built data capture, and it helps to reduce operational costs.
Probably the best white paper to read on the need for COBIE is its Requirements Definition and Pilot Implementation Standard - published by the US Army Corps of Engineers. 
 
Another white paper that should be consulted defines the National BIM Standard for the United States - INFORMATION EXCHANGE STANDARD - Version 3. In particular this states "COBie is implemented in commercial software to allow the users of that software to transfer the information from one phase of a project to another without having to repeatedly recapture that same information, as is the case in the capital facilities industry today.
 
The last white paper which covers the rest of the subject matter is the overview provided in a document entitled: Construction Operations Building Information Exchange (COBie)by E. William East, PE, PhD, Engineer Research and Development Center, U.S. Army, Corps of Engineers. This was last updated in April 2014.
 
It includes in its overview this statement: "COBie simplifies the work required to capture and record project handover data. The COBie approach is to enter the data as it is created during design, construction, and commissioning, see Figure 1. Designers provide floor, space, and equipment layouts. Contractors provide make, model, and serial numbers of installed equipment"
 
The simplest methodology is for the main contractor to collate the information during the construction phase, and then to pass the software, the database, and the documents to the project owner. As long as the main contractor is involved in the detailed design process, the whole project life will be covered.
 
It is to be noted that some relevant information is NOT included: particularly the issue and approval of information during the construction process. Further more there is a relational problem with documentation that relates to more than one asset [space, system, plant item, structural item, etc]. This includes such things as Electrical Loads for example and P&ID's [Process and Information Diagrams].
 
What COBIE IS about is to create a model of the project - its design, construction and operation. It is NOT about a "3-D computer model of the structure" which is the impression that is often given. It is about being able to retrieve the required relevant information in a fast and efficient manner, and being sure that all of the information is there and retrievable.
 
Within TDOC entities such as floor, space, and equipment layouts may be set up by the user as "Groups". A Group may also be created as a contract or sub contract. Against this type of group, a start date and an end date may be set, as well as the budget for the work within that "work package": activities include the certification of monies due, and paid etc. 
 
One of the most important methodologies for ensuring that a project proceeds smoothly is managing the Submittal & Approval process. The best definition is that provided by the SDRS [Supplier Documentation Requirement Specification], sometimes referred to as VDRL.
 

Next: The BIG question: which is to examine what it is that the UK promoters of BIM - Building Information Modelling - think that it actually encompass's AND which has not been done before. The following links are worth examining (Comments in red refer to information for the construction management process):

 


About some British Standards: Research conducted in June 2012 has shown that the following standards have emerged as a consequence of BIM (Comments in red refer to information for the construction management process; please note that British Standards are now publicly viewable via public libraries and thus do not need to be purchased in order to be read):

  • BS ISO 29481-1:2010 - Building Information Modelling - Information Delivery Manual - Part 1: Methodology & Format 
    • This defines the construct of the 3-D model
    • Provides the concept of an Information Delivery Manual or IDM
    • The construction engineering management document control process is wholly ignored
  • ISO/DIS 29481-2:Draft - Building Information Modelling - Information Delivery Manual - Part 2: Interaction Framework
    • Defines interaction of process ... Design -> Specification -> 3-D Model -> Cost [see table 1 page 6] 
    • This seems to be an improbable order - nowhere are the contractual and risk arrangements mentioned
    • The Appendices describing the various elements demonstrate that the proposed system complexity is probably unworkable.
  • BS ISO 12006-2:2001 - Building Construction - Organization of information about construction works - Part 3: Framework for classification of information.
    • This standard dates from the era of the EDIFACT [United Nations alternative to XML], EDICON [Appears to be dead], and EDIBUILD [Alive but mostly relating to Quantity Surveyors and Bills of Quantities].
    • EDI in conjunction with html forms although commonly used in many environments have been mostly ignored by the construction industry.
  • BS ISO 12006-3:2007 - Building Construction - Organization of information about construction works - Part 3: Framework for object-orientated information.
    • Introduces the EXPRESS-G specification and notation in the xtd entities.
    • Although the example include "A Document" its connection properties are undefined let alone its status or even the history of its development and as for its life history in terns of issue and comment - well that is missing.
  • BS EN ISO 9001:2008 - Quality management systems. Requirements
    • Sets forth the requirements of best management practice in a contract environment.
    • Contains considerable requirements regarding document [or information] control and dissemination.
    • For construction specific quality requirements, a good look at the Canadian Standard Z299 is worthwhile.
    • Possibly the best standard in the world to use for procurement of a construction project. Its requirements exceed those of ISO 9001

Some Comments on the use of 3D Computer Models [or a BIM]:
  • First of course is to provide an overview of the project. This can be used to demonstrate a number of things:
    • Blending in to the environment - how it looks within the context of the local scenery. This used to be done by an artist painting a picture, or series of pictures. These have often become historic pictures.
    • Complexity of construction ... for example interaction of a new underground railway station with existing infrastructure. Previously this would be done by isometric drawings and cross sections - which were hugely time consuming to create.
    • Walk through of buildings and structures - for example for making sales of space within a shopping centre.
    • Fire and evacuation management.
  • Clash detection. To be effective, this requires that the model be updated in minute detail - as many inter service clashes arise from misaligned construction and or service installations ranging from causes such as piles driven to miss underground high voltage cables to ....
  • Generation of 2D documents
    • Most construction projects require the use of a drawing or schedule on site - for which a 2D drawing is required
    • Often a 3D perspective is required.
What 3D Computer  Models do NOT / CANNOT do:
  • Record the issue of information [in whatever form] for approval or construction for example.
  • Conduct buildability [or method of construction] checks in the same manner that can be accomplished with a physical model as is often used in Power Station construction for example.
  • Present, for example, cable or drumming schedules which are required to minimise cable wastage, ditto Reinforcement schedules 
  • Handle Technical Queries or Request for Information, Contract Notices etc
  • Record the results of comparisons between models, in a similar manner to comparing drawings or specifications.
In summary, one should be aware of the fundamental differences between a project model, and a model of a structure within a project.
 

Some SERIOUS Comments:
  • The number of views indicates that in reality no-one in the Construction Industry can be bothered with BIM ... 
  • Most of the above videos are simply sales stuff ... trying to get away from the fact that certain well known Software Companies have escalated their sales methodology to sell to Government requiring their use be mandated on all public projects.
  • Almost all of what they promote has been standard practice for many many years. One suspects that the Ancient Egyptians, the Greek, the Romans, and many many other cultures from thousands of years ago faced up to and solved the same problems.
  • One is tempted to ask how Microsoft, AutoDesk and Bentley store the necessary CEMDC data. The answer of course is that they don't.
  • There are some vague comments about operating in conjunction with Accounting Systems and the like to fill in the holes.
  • 3-D models have some great facilities:
    • 3-D clash detection has been available for many years - with probably the first applications in recent times in ship building and oil facility construction. Certainly the author of this paper was doing these things in the 1980's on IBM main frames, and Compaq 386's.
    • Walk through of the proposed buildings.
  • 3-D models also have some serious defects:
    • The model isn't fixed ... so changes to stuff that has already been built can be made,
    • The effort in keeping a model up to date on a daily basis let alone an hourly basis on a large project is hugely expensive in resources.
    • The model has no knowledge of what information has been issued for construction or manufacture,
    • For a large structure such as a hospital the model will become huge ... and that means loading it up to obtain some trivial information becomes wholly un-feasible - viz why would an electrical contractor want to be able to view weld details when all he wants to know is the position of a wireless smoke detector ?
    • Models cannot cope with Process & Information Diagrams ....
    • Models do not carry out buildability checks which are the source of many problems - Google will tell you more. 

Conclusion
 
The similarities with the failed CITE initiative are strikingly similar - indeed many of the same people are involved. 
 
There is no simple publicly freely available list of what BIM entails. A lot of waffle - YES, but nothing that one can turn into a check list. Sure there are Several British Standards: BUT they deal with related matters not the CORE of what it is all about.
 
So although modelling of buildings is a good thing, it is NOT the be all and end all as is being made out. Indeed in the old days there was always a model of a ship or a power station, which could be taken to pieces to demonstrate buildability, its features etc etc.
 
When a concept gets "out of control", when the senior members of the various professions cease commenting on it, and when the magazines representing these professions start taking excessive volumes of related advertising [even if it is just to stay alive], then one is tempted to question the integrity of these magazines. They are NOT trade magazines where one expects "advertorial", and editors must, even unwittingly, avoid being placed in the situation where it appears thus. 

Return to Meaning of Terms 

 

And for those with a sense of humour, a parody of a very old poem ....