BS1192:2007 Collaborative production of architectural, engineering - - PowerPoint PPT Presentation

BS1192:2007

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

Barrie Sharp

Why?

• It’s a standard
• not MY Standard
• Everyone can get on board; It’s not company or project

specific; familiar

• Processes can be automated to engage on multiple

projects

• ALL Government BIM projects WILL use it
• It’s better than the chaos that project directories can

tend towards

How old is it?

• First edition BS 1192-5:1990
• Second edition BS 1192-5:1998
• Third edition BS 1192:2007
• Revisions in 2015 and ongoing

Nothing new but there is now a drive to get everyone engaged with using it.

Is it the best standard ever?

Probably not. I’m sure we can all find fault with it and the document is still being revised to plug any ambiguities. What makes it work is industry wide adoption. The best standard is not half as good as an adopted standard.

Common Data Environment

The CDE is a workflow. A file goes through four states: 1) Work in progress 2) Shared 3) Published 4) Archived

Common Data Environment

Common Data Environment

1.1

• WIP file created for its first version

Common Data Environment

1 2.1

• First version is issued
• WIP goes to next version

Common Data Environment

2 3.1 1

• Second version is issued
• WIP goes to next version
• First version is archived

Common Data Environment

2 3.2 1 3.1

• WIP is backed up and goes to next

minor version in response to large changes.

Common Data Environment

4.1 1 3.1 2 3

• Third version is issued
• WIP goes to next version
• Second version is archived

CDE as a Folder Structure

• WIP is local to author

CDE as a Folder Structure

• WIP is local to author
• Other folders will be available

to others using cloud

CDE as a Folder Structure

• File goes on a journey

File Naming

• Naming should apply to all collaborative documents in

the common data environment project structure.

• This includes all CAD drawings, schedules and reports.
• Anything stored outside the CDE will not need to follow

this structure but a logical naming convention should be used to aid colleagues.

Project Number

• The code for the project and any sub-projects should

be from two to six characters.

• For this project, let’s use:

BS1192

Project Number

• The code for the project and any sub-projects should

be from two to six characters.

• For this project, let’s use:

BS1192

Project Originator

• The unique identifier should identify the organization

responsible for creating the data.

• For Crofton, let’s use:

BS1192

• CFN

Project Originator

• The unique identifier should identify the organization

responsible for creating the data.

• For Crofton, let’s use:

BS1192-CFN

Project Volume

• The “Volume/System” code should be one or two
• characters. Strategies will be determined for each

project.

• Invariably, smaller projects just use 00:

BS1192

• 00
• CFN

Project Volume

• The “Volume/System” code should be one or two
• characters. Strategies will be determined for each

project.

• Invariably, smaller projects just use 00:

BS1192

• 00
• CFN

Project Level or Location

• The “level” code should be two characters as listed in

BS1192.

• As no level is applicable, let’s use:

BS1192

• XX
• CFN-00

Project Level or Location

• The “level” code should be two characters as listed in

BS1192.

• As no level is applicable, let’s use:

BS1192

• XX
• CFN-00

File Type

• The code should be exactly

two characters as follows:

BS1192-CFN

Code File Type AF Animation file (of a model) CM Combined model (combined multidiscipline model) CR Specific for the clash process DR 2D drawing M2 2D model file M3 3D model file MR Model rendition file for other renditions, e.g thermal analysis etc. VS Visualization file (of a model) Code File Type BQ Bill of quantities CO Correspondence CP Cost plan DB Database FN File note HS Health and safety IE Information Exchange file MI Minutes / action notes MS Method statement PP Presentation PR Programme RD Room data sheet RI Request for Information RP Report SA Schedule of accommodation CA Calculations SH Schedule SN Snagging list SP Specification SU Survey

• 00-XX

File Type

• Let’s use the Presentation code:

BS1192

• PP
• CFN-00-XX

File Type

• Let’s use the Presentation code:

BS1192

• PP
• CFN-00-XX

Model Discipline

• Each organization should be

allocated to one or more roles within the project.

• Let’s use General:

BS1192

• Z
• CFN

A Architect B Building Surveyor C Civil Engineer D Drainage, Highways Engineer E Electrical Engineer F Facilities Manager G Geographical and Land Surveyor H Heating and Ventilation Designer I Interior Designer K Client L Landscape Architect M Mechanical Engineer (Also combined models containing MEP) P Public Health Engineer (All Pipework) Q Quantity Surveyor S Structural Engineer T Town and Country Planner W Contractor X Subcontractor Y Specialist Designer Z General (non-disciplinary)

• 00-XX-PP

Model Discipline

• Each organization should be

allocated to one or more roles within the project.

• Let’s use General:

BS1192

• Z
• CFN-00-XX-PP

Number

• The numbering for standard coding should be exactly

four integer numeric digits, used sequentially. Leading zeros should be used.

• Let’s use:

BS1192

• 0001
• CFN
• XX
• 00
• PP-Z

Number

• The numbering for standard coding should be exactly

four integer numeric digits, used sequentially. Leading zeros should be used.

• Let’s use:

BS1192

• 0001
• CFN
• XX
• 00
• PP-Z

Status

• Status is made up of Suitability and Revision (Version).
• Suitability lets you state how ‘finished’ a file is and for what

purpose it might be used.

• Let’s use Suitable for Information:

BS1192-CFN

• S2
• 00-XX-PP-Z-0001

Status

• Status is made up of Suitability and Revision (Version).
• Suitability lets you state how ‘finished’ a file is and for what

purpose it might be used.

• Let’s use Suitable for Information:

BS1192-CFN

• S2
• 00-XX-PP-Z-0001

Status

• Revision identifies the version of the file.
• Let’s use Preliminary 01:

BS1192-CFN

• P01
• 00-XX-PP-Z-0001-S2

Status

• Revision identifies the version of the file.
• Let’s use Preliminary 01:

BS1192-CFN

• P01
• 00-XX-PP-Z-0001-S2

Hang on…

• Published is only used for official

document sets.

• The Suitability codes are a strong clue

What about Published?

Hang on…

• Published is only used for official

document sets.

• The Suitability codes are a strong clue

What about Published?

Hang on…

• Published is only used for official

document sets.

• The Suitability codes are a strong clue

What about Published?

Hang on…

• Published is only used for official

document sets.

• The Suitability codes are a strong clue

What about Published?

Hang on…

• Published is only used for official

document sets.

• The Suitability codes are a strong clue

What about Published?

Simple Analogy (CDE)

• Journal Publication
• Multiple contributors have Work In Progress

Illustrators Writers Editors

• They Share progress for editors to

coordinate and form finished piece

• They issue a Draft (D2 Tender)
• They send a proof (B4 Partial Sign-off)
• A4-It’s sent to Printers for Publication

Published

Source Files vs Outputs

• There are many examples where a file is used to

produce other files

• For example, a model produces drawings
• Both the model and drawings are issued and should be

named independently

• The drawings never have a WIP version

Shared Files

• Files shared by others should be linked directly into

designs for reference

• Files should not need to be modified but a collaborative

workflow may need to be established and files reissued

• Shared files should be combined to create the full

project

• Nothing should be duplicated or replicated from others

to avoid risk of conflicting or out of date data.

Wakey wakey…

Feel free to ask questions