CodeBook at the Conferences
- 1. CBUG-AU_05_2013 CodeBook at the Conferences 27/08/2013
- 2. We are users!!! CBUG.AU is a multi-disciplinary volunteer group of “Codebookers”. Advocating and working towards identifying best practice workflows for Codebook. Early Days Professional Community Collective Technical Resource Knowledge Base - Support Resource User / Developer Liaison We would love your feedback on what you think the group can offer the codebook professional!!! _Committee Members LinkedIn Group : “Codebook User Group”
- 3. Some recent updates: Latest Build: 30th July 2013 – Final Build compatible with AutoCAD2012 Some upcoming release information: _This build implements Revit 2014. (Revit 2012 and 2013 can continue to be used) _When using new project wizard, if the library folder exists and contains a library mdb, the original file will be renamed with a version suffix rather than replaced _Equipment legends will now output 3d thumbnails when they exist _Delete Homeless rooms, will now remove all floors and departments that contain no rooms _Have added an option to the Load ribbon bar to organise rooms and floors according to the Revit levels _The Revit elements that bound a room are now collected during a sync and displayed in the Room Editor _When updating designed equip list, the current Revit design option will be displayed in dialog for information _The C Sheet equipment schedule now writes entire schedule to a single shared param, that can be included as a label of the view sheet title family _File paths of pictures in flex reports were not being defined correctly with , broken a few builds back when changing how network paths were manipulated _Equipment usage reports now include alternative cad names. _This will be the final build that provides Acad 2012 support Where do you find this information? In the CIS-Note-003 on BOX (Along with all the other Codebook Information Sheets) Other Interesting information: CBUG committee to test CodeBook on STRATUS! _Revit + CodeBook in the cloud _Access from any PC, any where at any time! http://stratus.net.nz/ _Codebook News
- 4. 2 x Presentations (approx. 30mins each) Revit C-sheets – a BIM Unicorn The A, B, C & D of Space Planning Technologies Questions (approx. 10mins) Things to note: - Limited time. - We ask that questions are ideally relevant to the topic and content of the presentation. We ask that broader scope questions or specific technical issues are addressed to your local host, who will ensure they reach the rest of the group and can be appropriately actioned. Alternatively questions that arise out meeting maybe submitted to: cbug.au@gmail.com _Tonight’s Format
- 5. CodeBook CSheets with Revit No Longer a BIM Unicorn Danielle Currie and Andrew Harp Silver Thomas Hanley, Perth
- 7. Launched - 1993 v8.2 CAD v9 and v10 CAD
- 8. Sept 2012 CSheets Implemented v9 RVT Revit - 2009 (?) 2011 (?)
- 9. Jan 2013 CSheets to create views v10 RVT
- 10. Feb – Jun 2013 CSheets v10 RVT Mar 2013 EQ List as parameters
- 11. GO LIVE . . . CSheets v11 RVT
- 12. GONE LIVE . . . Questions?
- 13. CodeBook CSheets with Revit No Longer a BIM Unicorn Danielle Currie and Andrew Harp Silver Thomas Hanley, Perth
- 14. Quick live demo! CodeBook C-sheets with Revit, no longer a BIM Unicorn
- 15. That BIM definition… again… Building information modelling (BIM) is the process of generating and managing building data during the life cycle of the built structure. It uses three-dimensional, real-time, dynamic building modelling software to increase productivity in building design, construction and occupation. The process produces the building information model (also abbreviated BIM), which encompasses building geometry, spatial relationships, geographic information, quantities and properties of building components and spaces. Many forms of analysis can then be performed on this digital prototype before it is actually physically built in its environment at great cost.
- 16. Alternative BIM definition • Building Information Management is an alternative description of BIM, focussed on the management of information and process. • Once the design principles and project aspirations are identified, they should drive how the BIM is developed, it’s content and final use - the project team need to be aware of this! • Information should develop integrally within the design and the whole team understand the needs and deliverables at each project milestone. • What information do our clients require and when?• Generic arrangements • Specialist areas • Schedules for Tender / BofQ • Internal QA checks • Brief vs. Design • Client management • Identification • Design criteria • Fabric & finishes • Schedule of Areas • Functional brief • Equipment schedule Briefing Rooms FF&EValidation
- 17. Space Planning Technology ...is a general term used to describe software packages that: o enable the briefing of facilities o integrate briefing data with BIM’s o generate reports o analysis of brief vs. design o some functionality beyond design o or the ability to export data downstream
- 18. Typical inputs + outputs
- 19. SPT in BIM Revit does many things... Modelling... Documentation... Basis for visualisation...
- 20. Object oriented
- 21. No object = no information Alan Johnston Drawing a Shadow Alan Johnston used white walls as a blank sheet of paper on which to base his drawing. He divided Galleries 1, 2 and 3 up into unequal frames, drawing directly with a pencil onto the walls in strips covering an area of about 2 square cm. Navigating the corners, recesses and architraves; the space which is left is equally as important as the space that he fills in; constantly measuring the shape in space, he makes sculpture out of architecture.
- 23. Areas of Focus DATA CAPTURE _Spaces _Location _Functional _Finishes _Furniture _Equipment _Services _Door
- 24. Object oriented DATA CAPTURE _Economy strength _BIM Capability _BIM Management Plans _Standards (BIM) _SPT Capability
- 25. Revit + BIM Link + RDB Link …
- 26. Revit + BIM Link + RDB Link … Both are great tools, but have limitations o enable the briefing of facilities o integrate briefing data with BIM’s o generate reports o analysis of brief vs. design o some functionality beyond design o or the ability to export data downstream
- 27. SPT main players A – Affinity (Trelligence) B – BuildingOne C – CodeBook D – dRofus
- 28. Noteworthy… _Project Size _International Use _Years of Operation _BIM Interoperability _Organizational Size
- 29. Common ground _Each do many similar things _Approx 75% overlap _Each has a unique point of difference _Each has a bi-directional link to BIM _Focus on rooms and their content _Drive brief information into BIM _Analyse the design against the brief
- 30. Overview Process (dRofus) Programming Design and construction - Check differences between program and BIM (IFC) - Cost control different solutions - Design step 2 As-built Program As-built model / building ”Best practice” Evaluation Continous update of requirements and BIM. - Function programming Step 3 - Equipment programming Step 2 - Function programming Step 2 - Equipment programming Step 1 - Function programming Step 1 - Construction - FM - Design step 3 - Design step 1 © Nosyko AS Process with owner stakeholders and consultants Org.developement - Additional programming - Equipment purchase The iterative process of client requirement management Standardized Requirements model Exchange and present requirements in design tool Exchange and compare design to requirements Deviations trigger one of the following actions: > Update design > Update requirements > Present delta At handover Requirement=Design=As Built All data exchange using open buildingSMART standards
- 31. Detailed Workflow - SD
- 32. Detailed Workflow - DD
- 33. Detailed Workflow - CD
- 34. Typical / traditional deliverables
- 35. buildingSMART
- 36. Standard Pack of Deliverables > 1:200 Generic Room Keyplan > 1:50 Generic Room Layout Sheets (relevant to dept) > Generic Room Data Sheets (relevant to dept) > 1:100 GA setout plans > 1:50 FF&E plans (key rooms for user review) > 1:50 RLS drawings (key room for user review) > Schedule of Accommodation (department) > Room Data Sheets (key rooms for review in meeting) > RDS excel extract (update in meeting, rather than markup) > FF&E Schedule
- 37. Revit considerations Data Author – BIM or SPT? Map it out and make sure the team know
- 38. Shared or System System parameters – built in, for specific uses Shared parameters – user defined, do anything!
- 39. Categories You may also choose to use categories such as Communication Devices, Data Devices, Fire Alarm... available within the Building Design Suite
- 52. Unique selling point Affinity – planning module BuildingOne – FM solution CodeBook – works with multiple design tools dRofus – accessibility
- 53. Roles
- 55. Issuing Process INTEGRAL PART OF DESIGN PROCESS _UPDATING / SYNCHRONISATION _QA CHECKING _PRODUCTION OF INFORMATION _PDF’ing _UPLOADING
- 57. _BRIEF CAPTURE _CONCEPTUAL PLANNING _EASE OF USE _AREA ANALYSIS _BIM INTEGRATION _INFORMATION MANAGEMENT _EQUIPMENT VALIDATION _ADDITIONAL SERVICES / FEES _EXPORT TO COBie / FM _ACCESS FROM MOBILE DEVICES
- 58. Advice? _Get training, or embed a specialist in your team _Shoot the content re-designers, re-namer, that over model, over complicate.... _Know your project delivery requirements, define the deliverables, their format etc... _define roles and define the Data Author _Design what is important _Technology doesn’t stop bad work
- 59. Questions?
- 60. Meeting Wrap up Next session 24th September 2013 LinkedIn - CodeBook User Group Email – cbug.au@gmail.com