codebook at the conferences
TRANSCRIPT
CBUG-AU_05_2013
CodeBook at the Conferences
27/08/2013
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”
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
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: [email protected]
_Tonight’s Format
CodeBook CSheets with RevitNo Longer a BIM Unicorn
Danielle Currie and Andrew HarpSilver Thomas Hanley, Perth
CSHEETS
COORDINATED
VALIDATED
Launched - 1993
v8.2 CAD
v9 and
v10 CAD
Sept 2012
CSheets
Implemented
v9 RVT
Revit - 2009 (?)
2011 (?)
Jan 2013
CSheets to create views
v10 RVT
Feb – Jun 2013
CSheets
v10 RVT
Mar 2013
EQ List as parameters
GO LIVE . . .
CSheets
v11 RVT
GONE LIVE . . .
Questions?
CodeBook CSheets with RevitNo Longer a BIM Unicorn
Danielle Currie and Andrew HarpSilver Thomas Hanley, Perth
Quick live demo!
CodeBook C-sheets with Revit, no longer a BIM Unicorn
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, quantitiesand 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.
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
Space Planning Technology
...is a general term used to describe software packages that:
o enable the briefing of facilitieso integrate briefing data with BIM’so generate reportso analysis of brief vs. designo some functionality beyond designo or the ability to export data downstream
Typical inputs + outputs
SPT in BIM
Revit does many things...Modelling...Documentation...Basis for visualisation...
Object oriented
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.
Brief development
Brief
Design
ReviewClient input
Design
Review
Areas of Focus
DATA CAPTURE_Spaces_Location_Functional_Finishes_Furniture_Equipment_Services_Door
Object oriented
DATA CAPTURE_Economy strength_BIM Capability_BIM Management Plans_Standards (BIM)_SPT Capability
Revit + BIM Link + RDB Link …
Revit + BIM Link + RDB Link …
Both are great tools, but have limitations
o enable the briefing of facilitieso integrate briefing data with BIM’so generate reportso analysis of brief vs. designo some functionality beyond designo or the ability to export data downstream
SPT main players
A – Affinity (Trelligence)B – BuildingOneC – CodeBookD – dRofus
Noteworthy…
_Project Size_International Use_Years of Operation_BIM Interoperability_Organizational Size
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
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 toolExchange and compare design to requirementsDeviations 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
Detailed Workflow - SD
Detailed Workflow - DD
Detailed Workflow - CD
Typical / traditional deliverables
buildingSMART
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
Revit considerations
Data Author –
BIM or SPT?
Map it out and
make sure the
team know
Shared or System
System parameters – built in, for specific uses
Shared parameters – user defined, do anything!
Categories
You may also choose
to use categories such
as Communication
Devices, Data Devices,
Fire Alarm... available
within the Building
Design Suite
Unique selling point
Affinity – planning module
BuildingOne – FM solution
CodeBook – works with multiple
design tools
dRofus – accessibility
Roles
Deliverables & Programme
Issuing Process
INTEGRAL PART OF DESIGN PROCESS
_UPDATING / SYNCHRONISATION
_QA CHECKING
_PRODUCTION OF INFORMATION
_PDF’ing
_UPLOADING
Implementation challenges
_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
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
Questions?
Meeting Wrap up
Next session 24th September 2013
LinkedIn - CodeBook User Group
Email – [email protected]