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 2.1 1 First version is issued WIP goes to next version
Common Data Environment 3.1 2 1 Second version is issued WIP goes to next version First version is archived
Common Data Environment 3.2 2 1 3.1 WIP is backed up and goes to next minor version in response to large changes.
Common Data Environment 4.1 3 1 3.1 Third version is issued 2 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: -CFN BS1192
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: -00 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 -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: -XX BS1192 -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 -CFN-00 -XX
Code File Type Code File Type AF Animation file (of a model) File Type BQ Bill of quantities CM Combined model (combined CO Correspondence multidiscipline model) CP Cost plan CR Specific for the clash process DR 2D drawing DB Database M2 2D model file FN File note M3 3D model file The code should be exactly HS Health and safety MR Model rendition file for other renditions, e.g thermal analysis IE Information Exchange file two characters as follows: etc. MI Minutes / action notes VS Visualization file (of a model) 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 BS1192-CFN -00-XX
File Type Let’s use the Presentation code: -PP BS1192 -CFN-00-XX
File Type Let’s use the Presentation code: BS1192 -CFN-00-XX -PP
Model Discipline A Architect Each organization should be B Building Surveyor C Civil Engineer allocated to one or more roles D Drainage, Highways Engineer E Electrical Engineer within the project. F Facilities Manager G Geographical and Land Surveyor Let’s use General: H Heating and Ventilation Designer I Interior Designer -Z 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 BS1192 -CFN -00-XX-PP Y Specialist Designer Z General (non-disciplinary)
Model Discipline Each organization should be allocated to one or more roles within the project. Let’s use General: BS1192 -CFN-00-XX-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: -0001 BS1192 -CFN -00 -XX -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 -CFN -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: -S2 BS1192-CFN -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 -00-XX-PP-Z-0001 -S2
Status Revision identifies the version of the file. Let’s use Preliminary 01: -P01 BS1192-CFN -00-XX-PP-Z-0001-S2
Status Revision identifies the version of the file. Let’s use Preliminary 01: BS1192-CFN -00-XX-PP-Z-0001-S2 -P01
Hang on… What about Published? Published is only used for official document sets. The Suitability codes are a strong clue
Hang on… What about Published? Published is only used for official document sets. The Suitability codes are a strong clue
Hang on… What about Published? Published is only used for official document sets. The Suitability codes are a strong clue
Hang on… What about Published? Published is only used for official document sets. The Suitability codes are a strong clue
Hang on… What about Published? Published is only used for official document sets. The Suitability codes are a strong clue
Simple Analogy (CDE) Journal Publication Multiple contributors have W ork I n P rogress 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) Published A4- It’s sent to Printers for Publication
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
Recommend
More recommend
