BS 1192:2007

Collaborative production of architectural, engineering and construction information – Code of practice

Provides the outline methodologies for setting up the BIM project. (Makes extensive reference to CPIC's Code of Procedure for the Construction Industry)

BS 1192-4 defines expectations for the exchange of information throughout the lifecycle of an asset, and includes requirements for reviewing and checking for compliance, continuity and completeness. COBie is the UK Government’s chosen information exchange schema for federated BIM Level 2, alongside graphical BIM models and PDF documents.

To make the most of the collaborative working process, a common methodology for managing the data produced by and between all parties must be used. This should include the naming of data as well as a process for exchanging data.

BS 1192:2007 supersedes BS 1192-5:1998 - an extract from Section 1 Scope…

‘…establishes the methodology for managing the production, distribution and quality of construction information, including that generated by CAD systems, using a disciplined process for collaboration and a specified naming policy.
It is applicable to all parties involved in the presentation and use of information throughout the design, construction, operation and deconstruction throughout the project life cycle and the supply chain.
The principles for information sharing and common modelling are equally applicable to building and civil projects.
This standard is also a guide for developers of software applications to enable them to support its implementation through the provision of configuration files or application add-ons.’

This is a Code of Practice and as such takes the form of guidance and recommendations, and this should be made clear wherever it is quoted. The document addresses two key issues – the process for managing the exchange of the data and the convention for naming data.

Collaborative management process

BS1192:2007 advocates that a common set of generic processes and procedures should be followed, and fine-tuned for particular projects where required. These procedures should include:

  • Co-ordination of model files as they develop
  • Production of drawings
  • Production of drawings using CAD software

The flow of data is managed via the Common Data Environment (CDE), and has four phases:

  1. Work-in-progress – each member of the project team carry out their own work here prior to issuing to other team members.
  2. Shared – the data from each team member is placed here when it is ready to be shared with the other team members. The process describes various status codes to be used when issuing data to the ‘shared’ environment to indicate its status.
  3. Published documentation – at agreed milestones, published documentation will be produced from data in the ‘shared’ area. All of this data will have been checked, reviewed an4. d approved.
  4. Archive – all superseded data is placed in the ‘archive’ area so as to remain available should it be required in future.

Data naming

The process for naming data outlined in BS 1192:2007 is widely used and appears most commonly in drawing numbering applications. It produces a distinctive 6- or 8-group string of pairs of characters (see example below), and includes fields such as project, originator, zone, level, type, role, classification and number.


This string shows that the document or data relates to a project with the code ‘SM’, and was issued by a company with the code ‘CO’. It relates to the ground floor in zone 02, and is a 3D model. It was issued by the mechanical engineer and the general topic is chilled water (using CAWS classification).

Full standard freely downloadable at the Bim-Level2 website