P07 project - BIM Guides Workshop

Transcription

1 P07 project - BIM Guides Workshop , Toronto

2 Welcome & Introductions This is a workshop. Expect some discussions.

3 Agenda AM Session: MACRO LEVEL Project Overview current state How does this project relate to other efforts? PM Session: MICRO LEVEL Project Specifics discussion of topics Work By Phase identify/update Next Steps

4 Project Overview Macro Level

5

6

7 Definition A database for BIM guides* that can be searched by topic for help in developing a BIM standard/guide based on existing work. Build a custom guide from optional parts Map different classifications for different roles and terms used across guidelines Gain awareness of all docs out there

8 Guides * For the purposes of this project, "Guides" refer to any documentation that has been published to support the end-user in applying standardized BIM processes, procedures or technical requirements in the built environment.

9 Business Case Will save A LOT of time for those needing to develop a BIM Guide* Will help industry adopt BIM Will help industry standardize / develop standards Will help industry build upon existing work Will ease BIM guides usage thanks to their harmonized structure

10 Added Value This work will lead to metrics on what concepts, topics, terminology and content industry is using. Could help to identify gaps and incomplete coverage in existing guidelines and BIM implementation as a whole. Harmonized requirements lead to harmonized education and (people) certification

11 Project history Implementing 04/2014 Stockholm 10/2014 Toronto Experimenting 10/2013 Munich Exploring

12 AM Session

13 How does this work link to other efforts? Project Overview current state Norway Common Table of Contents RLOM Real Life Object Mapping Korea buildingsmart initiatives Korea Status on Research development in Korea The BIM Protocol Generator initiative UK NBS BIM Object Standard USA NBIMS guides and the bsdd Steen Sunesen Prof. Ghang Lee Dr. Chan-won Jo Susan Keenliside Stefan Mordue Birgitta Foster

14 List of additional guides to add 1. RIBA - BIM Overlay to the RIBA Outline Plan of Work 2. Owner's Guide to Maximizing Success in Integrated Projects (UofColorado+PennSt w/ grant from Charles Pankow) 3. Finland Infra Guide (FI: available, EN: about to be published) 4. IFMA new technical committee > new standards/docs to be uploaded? (ref: Deke) 5. Netherland BIM Handbook 6. Norway BIM Guidelines/Standard (?) > National BIM Guide (or Manual) being established as a database to create a product > ref: RLOM > configure project; get reports (reporting function) > ref: Data Dictionary 7. PAS :2013 (reference from Nick Nisbet) Ref:

15 List of additional guides to add (cont ) 8. Norway - NS 8360 BIM Objects (EN) (publication: pending) 9. Korea - KBIMS (KR)

16 Concerns 1. Too niche of a market? 2. Too academic to be useful? 3. Not academic enough to be useful? Ref: Work done by Li Wang, UTexas 4. Seed funding to come from where? 5. Business Model options for sustainable (i.e., reliable and scalable) service/product delivery

17 To Wiki or not to Wiki? The tool is not the project (John Messner, Penn State) Public interface vs. Search engine Public perception of a wiki (typically negative) Tagging of document content How?

18 PM Session

19 Project Specifics Micro Level

20 New bsi Website Review new bsi website and capture suggested edits to what is posted (name of project, description, call for participation, etc.)

21 Assumptions No PDF hosting Linking to specific document/paragraphs on external sites

22 We need a rule as to how things are listed to show their relationships Deke: We need to be able to show that a document is part of another document, or was derived from another document the four cases that I know of that we need to account for are: 1. Stand alone. The document was created from scratch and is not included in any other compendiums and has not gone through a consensus process. (Example: none come to mind immediately, but I am sure there are some) 2. Derivative work The document discussed is based on another document or is an update and we provide the name of that document. If the original document has gone through consensus and this one has not then that must be so noted. (Example: BIM Guide in Australia is a derivative of the VA BIM Guide) 3. Included document We identify the work that this document has been included within. It may or may not have gone through consensus. (Example: BIM Execution Guide is part of a consensus document NBIMS-US) 4. Consensus Document This document type may or may not have other documents included, or be a single document, but it has gone through consensus (Example: ISO or NBIMS- US)

23 ToC during Review Capture? Should review process change to Steen's chapter dispersal? i.e. mapping done when entering review vs. concept listing?

24 XML format of guides XML format of guides (ref: ModelSpace), as common format for guidelines > template structure + import feature + test platform for guideline structure > Export from wiki to either tool? Configure BIM guides from wiki. Excel file w/ same CSV structure

25 Open vs. Proprietary Birgitta s suggestion: "vet guidelines but not exclude the whole guide just because they are not open but say are Revit based. There are sections that still have value without being proprietary." Steen: need open format as main requirement to be contained within the database > bldgsmt = open standards, approving authority, quality stamp (*certifying organization) > What are the criteria for being bsi certified? Guidelines = not just file formats, but processes, and workflow, and collaboration (actors) 'Not trying to be proprietary, they need to be.' Jason Reece (PDS member) John Messner: need the proprietary files to re-enter the design cycle

26 Work By Phase Phase One: By Template Review Metadata Phase Two: Common Table of Contents Phase Three: Keyword Search (Full Text) Phase Four: Machine-Readable Constraints/Requirements

27 Work By Phase Phase One: By Template Review Metadata 1. Put pic of front cover of guide up on review page 2. Contact document authors to engage in process, garner support, raise funds and profile of project + to keep link to doc up to date + know when a newer version comes out 3. Contact each buildingsmart chapter lead to garner support, connect dots, include them in the effort 4. Identify and add in guides not currently in the database 5. Map out an example of how the database would be used (such as "BIM Guide for Government of Canada"); methodology + inclusion list 6. Make case for NBIMS/Alliance example of why the exercise is beneficial

28 Work By Phase Phase One: By Template Review Metadata 7. User interface needs curb appeal 8. (See list from Sylvain's 'diary') 9. buildingsmart logo beside 'openbim-supporting' guides 10. geo-ref globe view on Home Page (ref: Mark) 11. Identify and submit to grant opportunities 12. Identify student work options/opportunities 13. Externally-referenced content: author org keeps the doc/link up to date 14. Show/Insert Mark's graphs that depict focus areas of guides (=analysis)

29 Work By Phase Phase Two: Table of Contents 1. Add/reproduce table of contents for each document 2. How does content get tagged/referenced to related keywords?

30 Work By Phase Phase Three: Keyword Search (Full Text) 1. Need list of keywords and associations (terminology)

31 Work By Phase Phase Four: Machine-Readable Constraints/Requirements ex: Solibri does this already mvdxml concept already in existence

32 Resolutions (to be added in the agenda)

33 Thank you