BS1192:2007. Collaborative production of architectural, engineering and construction information Code of practice. Barrie Sharp

Transcription

1

2 BS1192:2007 Collaborative production of architectural, engineering and construction information Code of practice Barrie Sharp

3 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

4 How old is it? First edition BS :1990 Second edition BS :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.

5 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.

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

7 Common Data Environment

8 Common Data Environment 1.1 WIP file created for its first version

9 Common Data Environment First version is issued WIP goes to next version

10 Common Data Environment Second version is issued WIP goes to next version First version is archived 1

11 Common Data Environment WIP is backed up and goes to next minor version in response to large changes

12 Common Data Environment Third version is issued WIP goes to next version Second version is archived

13 CDE as a Folder Structure WIP is local to author

14 CDE as a Folder Structure WIP is local to author Other folders will be available to others using cloud

15 CDE as a Folder Structure File goes on a journey

16 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.

17 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

18 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

19 Project Originator The unique identifier should identify the organization responsible for creating the data. For Crofton, let s use: -CFN BS1192

20 Project Originator The unique identifier should identify the organization responsible for creating the data. For Crofton, let s use: BS1192-CFN

21 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

22 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

23 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

24 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

25 Code File Type Code File Type File Type BQ CO CP Bill of quantities Correspondence Cost plan AF CM CR Animation file (of a model) Combined model (combined multidiscipline model) Specific for the clash process DB Database DR 2D drawing The code should be exactly two characters as follows: FN HS IE MI MS File note Health and safety Information Exchange file Minutes / action notes Method statement M2 M3 MR VS 2D model file 3D model file Model rendition file for other renditions, e.g thermal analysis etc. Visualization file (of a model) 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

26 File Type Let s use the Presentation code: -PP BS1192-CFN-00-XX

27 File Type Let s use the Presentation code: BS1192-CFN-00-XX-PP

28 Model Discipline Each organization should be allocated to one or more roles within the project. Let s use General: -Z BS1192-CFN-00-XX-PP A B C D E F G H I K L M P Q S T W X Y Z Architect Building Surveyor Civil Engineer Drainage, Highways Engineer Electrical Engineer Facilities Manager Geographical and Land Surveyor Heating and Ventilation Designer Interior Designer Client Landscape Architect Mechanical Engineer (Also combined models containing MEP) Public Health Engineer (All Pipework) Quantity Surveyor Structural Engineer Town and Country Planner Contractor Subcontractor Specialist Designer General (non-disciplinary)

29 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

30 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

31 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

32 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

33 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

34 Status Revision identifies the version of the file. Let s use Preliminary 01: -P01 BS1192-CFN-00-XX-PP-Z-0001-S2

35 Status Revision identifies the version of the file. Let s use Preliminary 01: BS1192-CFN-00-XX-PP-Z-0001-S2-P01

36 Hang on What about Published? Published is only used for official document sets. The Suitability codes are a strong clue

37 Hang on What about Published? Published is only used for official document sets. The Suitability codes are a strong clue

38 Hang on What about Published? Published is only used for official document sets. The Suitability codes are a strong clue

39 Hang on What about Published? Published is only used for official document sets. The Suitability codes are a strong clue

40 Hang on What about Published? Published is only used for official document sets. The Suitability codes are a strong clue

41 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

42 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

43 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.

44 Wakey wakey Feel free to ask questions