Reviews

Levels of Information

 

Documents

Document downloads are only available to registered members. Click here to sign in.

If you have not created an account yet, then please sign up first.

August 17, 2015

When you think of a model, perhaps the first thing that comes to mind is geometry. This is not surprising as models have been used for centuries to set out a designer’s intentions – conveying shape, space and dimensions. The ‘Great Model’ of Sir Christopher Wren’s St Paul’s Cathedral did this in the 1670s and can still be seen today.

However, while the geometrical or graphical data can tell us the width of a brickwork leaf and the height of the walls, at a certain point during construction it is the written word that is needed to take us to a deeper level of information. It is within this textual environment that we describe the characteristics of the brickwork itself such as density, strength and source, and it is words that are used to describe the kind and type of mortar joint and wall ties.

In the context of BIM, we are actually looking at a rich information model which, aside from graphical data − such as geometry and shape − also includes non-graphical information such as performance requirements and associated documentation, presented in a specification or manual format. The written specification is not new and has been around for centuries. However, it is only now by combining these aspects of graphical and non-graphical information that we get the ‘overall picture’.

Advertisement

Today, clients are not only procuring a physical asset: they are also procuring information, typically in a digital format. The amount and level of information increases as we progress through the project lifecycle. For example, at an early strategic briefing stage, when the client is assessing needs, there may just be a requirement for spaces and activities. At concept stage this will be developed into the design intent of elements/systems to meet the Employer’s Information Requirements (EIR). This is then further developed at design stage when considering the characteristics of each deliverable in terms of performance requirements; this could relate to security requirements of a plant room space, an external wall element or a doorset system. At technical design stage, or at least prior to construction, product selection can be determined by the specifier or delegated as ‘contractor’s choice’ based upon generic product performance requirements.

The Government’s ‘Soft Landings’ guidance recommends that a building’s ’in operation’ phase should be considered throughout the whole project lifecycle. By establishing required performance outcomes and operational budget at an early stage, these can then be compared to the actual performance outcomes. From a concept stage, the performance criteria − such as the structural performance of a partition system − can be considered. As the information develops, specific references to relevant standards and classes are stated, along with any testing methods that may be required. Certifications by accredited third party certification bodies are also considered as the information progresses, to ensure that the client’s outcomes are met at the end of the project. At project handover, information specific to the installed object’s operation and maintenance is incorporated into standard COBie properties, as well as documentation such as links to PDF manuals.

Thanks for reading!

Please enjoy a limited number of articles over the next 30 days.

For total access log in to your The BIM Hub account. Or register now, it's free.

Register Sign in

Published
Source: www.thenbs.com/topics/BIM/articles/levels-of-information.asp