Information Rejection

[edit] Background

BIM protocols for an organisation or project may state that Appointed Parties must deliver the project information files in accordance those agreed BIM protocols. The industry sometimes finds that Appointed Parties agree to implement BIM processes as the source of their design, and that their deliverables will be derived, exported or 'cut' from their project BIM volume(s), but they fail to do so and instead implement exo-BIM processes. Due in some cases to lack of skills and competency with the designated design team.

What is sometimes reported by Information Managers and BIM Coordinators are attempts by some consultants to develop their exo-BIM design based on 2D CAD files exported (by a third party in some cases) from the other consultants federated 3D model volumes. The resulting exo-BIM 2D design developed outside of the collaborative process will not adequately take in to account design issues including clashes with other consultants's design intent.

A disparity and time shift between the live 3D federated models typically exchanged fortnightly on the CDE and the exo-BIM derived design occurs, this results in inacuracy, failure to collaborate effectively, delays on site and reduced overall value to the client.

[edit] Concept

"Information Rejection". IR is the scenario whereby an Appointed Party or supplier attempts to exchange files on a CDE that are:

• Not derived from the project team's 3D BIM volume(s)
• CAD files reverse BIM'd in to 3D volumes by a third party
• Exo-BIM data not exported from the BIM volumes e.g. manually added to spreadsheets
• Non-compliant with project BIM protocols
• 2D Drawings not derived from the 3D BIM volume(s)

The potential consequences for having exchange information rejected are:

• Responsibility for causing delays
• Charges imposed for delays
• Percentage of fees withheld
• Termination of appointment

[edit] Detection

To detect the occurence of attempts to exchange drawings and data not derived from the required 'live' 3D BIM volume, the BIM protocols must state that any file exchanged on the CDE must have an associated 3D BIM Volume to verify as the source of that information.

Where a clear disparity between the two occurs, or there is an absence of a 3D BIM Volume to verify the drawing or data against. That will be deemed a breach of the agreed rules and information Rejection will be the resulting action.

[edit] Action

In the BEP cite a reference to the UK BIM Framework's "Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery".

According to Table 12 in the aforementioned UK BIM Framework document, when exchanged information is audited and verified at Status S6, if rejected the status will be reduced to S0 "Work in Progress and not yet suitable to be Shared outside the task team.".

Read the references to information acceptance and rejection defined within the aforementioned reference and have the Information Manager and Document Controller implement it via the protocols. See Prevention.

[edit] Prevention

Create a BIM Services Agreement or similar, to be signed by each Appointed Party or Supplier in a Task Team prior to appointment to a project.

Amongst the descriptions of how and why Appointed Party's must read and understand the BIM protocols, it will be necessary to define the resulting actions that will be applied to the responsible party when their exchanged information on the CDE is discovered to be derived from exo-BIM sources and methods.

In the BIM Execution Plan under standards applied, cite the UK BIM Framework's "Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery".

[edit] Exemplar

Below is a typical example of how to define the circumstances and outcomes to the Appointed Party(s) if they fail to apply BIM processes in their design and exchanged files:

Information Rejection:

Starting from the first file exchange uploaded to the CDE, all drawings, details, schedules and other data files exchanged will be verified against your 3D .RVT/.IFC model exchanged at the same cycle. Be aware that if the files are found not to be derived from this 3D file, all exchanged files will be rejected and notice given to you for deviating from this agreement. Rejection of your files will have negative consequences with regards to your fees and potential charges imposed for causing delays. Your appointment to this project may also be terminated for breaching this agreement. Refer to the contracts director for further details.

[edit] Related articles on Designing Buildings

• Asset information requirements AIR.
• BIM articles.
• BIM dimensions.
• BIM execution plan.
• BIM glossary of terms.
• BIM maturity levels.
• BIM resources.
• Construction Operations Building Information Exchange (COBie).
• Common data environment.
• Data drops..
• Digital information.
• Digital model.
• Federated building information model.
• Government Soft Landings.
• Industry Foundation Classes.
• Information management.
• Revit.
• Uniclass.

[edit] External references

See Sections 1.3/1.4 and Table 12 in the UK BIM Framework: Information management according to BS EN ISO 19650 Guidance Part 2: Processes for Project Delivery below:

ISO-19650-Guidance-Part-2-Single-Page-Print.pdf (ukbimframework.org)