I'm quite lucky really... I work in a highly creative environment, with thought leaders, technical innovators and have a boss who really understands BIM, whilst allowing me the freedom to look at how we can do it better.
BIM implementation is largely a cultural thing in my opinion - back in the "good ol CAD drafting days" people focused exclusively on the plan, detail or section they were producing that day. BIM karma forces us to consider how we build it and what the guy sat nextdoor is working on tomorrow?
In the "flatland" 2D CAD days, we documented things in a prosaic, manually intensive way, trying desperately to coordinate drawings, packages - invariably with little recognition from clients of the effort required to make this happen.
In 2012, we have the tools available to automate these historic pipe dreams and get technology to work for us... for a change. Some of these tools have been around for a while, but generally by exception rather than as a rule.
CodeBook is a highly detailed program and when combined with Revit it can provide miraculous results - BUT - there are some basics that are often overlooked in the new world of BIM complexity.
Understanding what information you already have available to you, not re-inventing the wheel and making the most of that data is regularly forgotten when creating deliverables and "getting drawings out."
I'm an ardent believer in NOT duplicating information, but knowing how to extract and how to make the best use of the data available, in the right medium, is a skill that often comes with a high premium.
Going back to grass roots, reminding you of what you may already know and the information already available to you is the purpose of this "serendipity-esq" post.
Room information and room data stored within your CodeBook database is ready and waiting for you to utilisse within the CodeBook Reports. Most people know what is contained within a Room Data Sheet, but may not realise that this information can be pushed into your BIM model, or extracted through a report.
A room data sheet typically consists of:
_design data - the function of the room, the occupancy, hours of operation etc...
_finishes - floor, wall, ceiling, doors, internal glazing etc...
_environmental conditions - temperature, HVAC, hepa filtration, lighting lux levels, UPS, etc...
_equipment - furniture, equipment and services
...and whilst we report these conclusively in a Room Data Sheet, they can be extracted individually for architectural reasons and to aid in coordination with other disciplines.
The CodeBook reporting function has a number of pre-defined reports, but also several that can be configured or customised to provide whatever you may need through the report settings.
For example, if you wanted to extract the acoustic data, floor finishes, or lighting lux levels to send to a consultant for coordination - you can create a Room Data (xls) report specific to that data.
The way you do this is to select a Room Data (xls) report and in the report settings pick (through tick boxes) the information you require. These are categorised in sections - Room Information, Design, Finishes, Equipment and M+E - first you choose which section you require and then select the fields within these Categories that you wish to report.
For example = choose the Design section and tick the box for Occupancy - CodeBook will produce a report restricted to that information, which can then be emailed to the Services Engineer for checking.
An alternative to excel is to map this data in CodeBook to a corresponding Revit Room Parameter and provide the Services Engineer with a colour scheme drawing that shows each rooms Occupancy values by colour.
In practice you may wish to choose more data than this to send to your services consultant, but individual parameters may be useful, especially when represented in the context of the building through a colour themed view.
The "BIM karma" mentality involves recording information correctly once and then utilising it many scenarios.
Make it happen.
Thursday, 23 February 2012
Wednesday, 15 February 2012
Spread the love - system and shared parameters
It's been a couple of months since I last posted... Christmas, New Years, getting engaged, having a baby and Tet (Chinese/Vietnamese new year) are some of my own highlights, I hope y'all had an enjoyable break!
I'm going to start by making a prediction for 2012 - it's going to be a big year for the "I" in BIM, which stands for Information or Interoperability depending on your perspective.
CodeBook 'System' Parameters are those essential for CodeBook to function with Revit, CodeBook 'Shared' Parameters are those which are user defined optional parameters relating to either room or equipment data that you want to include within your Revit model.
Many large practices use a Shared Parameters File (SPF) to predefine the key parameters important to the modelling and documentation of each project. The idea being that you define them once correctly in your SPF and then utilize them on each project - think title block info, common building element, family and view properties.
Let's start with the CodeBook System Parameters, which I've defined in the image below
...these need to be explicitly defined in your Shared Parameters File as above - or you can allow CodeBook to add these to your project by choosing NOT to tick 'Do not create missing shared parameters' see image below. Apologies for the double negatives, but make sure you get it right or you'll have issues when you synchronise rooms, or update designed equipment.
We have chosen to control all parameters and define them through our SPF, hence why this BOX IS TICKED in the image.
The CodeBook Shared Parameters are optional and you can choose to include as many, or as few as you like. The image below shows an example of the CodeBook room information and room data fields we have chosen to 'share' in one of our projects.
The columns on the left hand side indicate the CodeBook fields, the Parameter Group and Parameter Name fields relate to (in this case) the Revit Room Parameters that we wish to 'Share' between CodeBook and Revit. Once you have mapped these, you need to determine which direction the data will be exchanged.
Generally speaking it is advisable to push or publish these parameters from CodeBook into Revit by selecting Copy data TO BIM. Typically you will define room data in CodeBook long before your Revit model is developed sufficiently to include in your model - i.e. your room data sheet info such as room name, required area, floor finish etc... are created in CodeBook during the briefing phase and it is only during the schematic design or design development phase that you would look to link this information with the Revit model.
Once your parameters are mapped, you've chosen the direction in which the data will be exchanged and selected which to 'Include' you are ready to Synchronise BIM to database links. Every time you Synchronise, CodeBook will record the geometric and coordinate data of each room from Revit into CodeBook - PLUS - dependant on what you've defined in your parameter mapping CodeBook will publish room data into the Revit Room Parameters. Note: the direction is critical, if you select Copy Data TO BIM, information will flow from CodeBook into Revit. If you select to Copy Data FROM BIM, the values within your Revit Room Parameters will be copied into the CodeBook fields.
Hopefully this all makes logical sense, but to fully get the point across, let's take the example of room names. If you have room names populated within CodeBook, but not in your Revit model, you would select to Copy Data TO BIM. When you synchronise BIM to database links CodeBook will record area, perimeter etc... from Revit into CodeBook and populate the Room Name Parameter field in Revit with the values defined in your CodeBook project. If you selected to Copy Data FROM BIM (and the Revit Room Name Parameter was empty) you would end up with a CodeBook project full of empty room names.
So to recap, the CodeBook 'System' Parameters are essential for CodeBook and Revit to work together, generally you should allow CodeBook to manage this by leaving 'Do not create missing shared parameters' UNTICKED. If you have defined these in your SPF then you can tick this box - but make sure you get it correct!
The CodeBook 'Shared' Parameters are optional and you define them in the parameter mapping. Specify the data you want to exchange between CodeBook and Revit and the direction - CodeBook to Revit, or Revit to CodeBook. When you Synchronise BIM to database links, the geometry and locational coordinate data will be recorded from Revit into CodeBook AND the parameters you've 'Included' within your parameter mapping will also be synchronised.
Also within Project Parameters > Define Parameter mapping, you'll notice you that you can define parameters for equipment and doors. The same principle applies in that you specify the CodeBook data and map this to a corresponding Revit Parameter. Door parameters can be exchanged in either direction, but equipment parameters can only be synchronised from CodeBook to Revit.
The reason for having a single directional data flow for equipment families, is due to the 'data relationship type' being one to many. Each equipment family should have the same code, description, group etc... but it is possible to have different instance values for these in your Revit model, if the values were entered manually. There is a single record in the CodeBook library for each item of equipments code, description, group etc... therefore you can only publish these parameters from CodeBook to Revit.
Again to fully explain this at length, let's take the example of equipment codes. If you had a family within Revit with multiple different parameter values for the equipment code and CodeBook allowed you to exchange data from Revit to CodeBook, how would CodeBook know which was correct? WE DEFINITELY WANT these to be consistent for each family type, hence why the data flow for equipment is one directional.
Hopefully this has explained CodeBook System and Shared parameters fully, but if in doubt, contact CodeBook support who will be sure to point you in the right direction.
Happy CodeBooking!
I'm going to start by making a prediction for 2012 - it's going to be a big year for the "I" in BIM, which stands for Information or Interoperability depending on your perspective.
CodeBook 'System' Parameters are those essential for CodeBook to function with Revit, CodeBook 'Shared' Parameters are those which are user defined optional parameters relating to either room or equipment data that you want to include within your Revit model.
Many large practices use a Shared Parameters File (SPF) to predefine the key parameters important to the modelling and documentation of each project. The idea being that you define them once correctly in your SPF and then utilize them on each project - think title block info, common building element, family and view properties.
Let's start with the CodeBook System Parameters, which I've defined in the image below
...these need to be explicitly defined in your Shared Parameters File as above - or you can allow CodeBook to add these to your project by choosing NOT to tick 'Do not create missing shared parameters' see image below. Apologies for the double negatives, but make sure you get it right or you'll have issues when you synchronise rooms, or update designed equipment.
We have chosen to control all parameters and define them through our SPF, hence why this BOX IS TICKED in the image.
The CodeBook Shared Parameters are optional and you can choose to include as many, or as few as you like. The image below shows an example of the CodeBook room information and room data fields we have chosen to 'share' in one of our projects.
The columns on the left hand side indicate the CodeBook fields, the Parameter Group and Parameter Name fields relate to (in this case) the Revit Room Parameters that we wish to 'Share' between CodeBook and Revit. Once you have mapped these, you need to determine which direction the data will be exchanged.
Generally speaking it is advisable to push or publish these parameters from CodeBook into Revit by selecting Copy data TO BIM. Typically you will define room data in CodeBook long before your Revit model is developed sufficiently to include in your model - i.e. your room data sheet info such as room name, required area, floor finish etc... are created in CodeBook during the briefing phase and it is only during the schematic design or design development phase that you would look to link this information with the Revit model.
Once your parameters are mapped, you've chosen the direction in which the data will be exchanged and selected which to 'Include' you are ready to Synchronise BIM to database links. Every time you Synchronise, CodeBook will record the geometric and coordinate data of each room from Revit into CodeBook - PLUS - dependant on what you've defined in your parameter mapping CodeBook will publish room data into the Revit Room Parameters. Note: the direction is critical, if you select Copy Data TO BIM, information will flow from CodeBook into Revit. If you select to Copy Data FROM BIM, the values within your Revit Room Parameters will be copied into the CodeBook fields.
Hopefully this all makes logical sense, but to fully get the point across, let's take the example of room names. If you have room names populated within CodeBook, but not in your Revit model, you would select to Copy Data TO BIM. When you synchronise BIM to database links CodeBook will record area, perimeter etc... from Revit into CodeBook and populate the Room Name Parameter field in Revit with the values defined in your CodeBook project. If you selected to Copy Data FROM BIM (and the Revit Room Name Parameter was empty) you would end up with a CodeBook project full of empty room names.
So to recap, the CodeBook 'System' Parameters are essential for CodeBook and Revit to work together, generally you should allow CodeBook to manage this by leaving 'Do not create missing shared parameters' UNTICKED. If you have defined these in your SPF then you can tick this box - but make sure you get it correct!
The CodeBook 'Shared' Parameters are optional and you define them in the parameter mapping. Specify the data you want to exchange between CodeBook and Revit and the direction - CodeBook to Revit, or Revit to CodeBook. When you Synchronise BIM to database links, the geometry and locational coordinate data will be recorded from Revit into CodeBook AND the parameters you've 'Included' within your parameter mapping will also be synchronised.
Also within Project Parameters > Define Parameter mapping, you'll notice you that you can define parameters for equipment and doors. The same principle applies in that you specify the CodeBook data and map this to a corresponding Revit Parameter. Door parameters can be exchanged in either direction, but equipment parameters can only be synchronised from CodeBook to Revit.
The reason for having a single directional data flow for equipment families, is due to the 'data relationship type' being one to many. Each equipment family should have the same code, description, group etc... but it is possible to have different instance values for these in your Revit model, if the values were entered manually. There is a single record in the CodeBook library for each item of equipments code, description, group etc... therefore you can only publish these parameters from CodeBook to Revit.
Again to fully explain this at length, let's take the example of equipment codes. If you had a family within Revit with multiple different parameter values for the equipment code and CodeBook allowed you to exchange data from Revit to CodeBook, how would CodeBook know which was correct? WE DEFINITELY WANT these to be consistent for each family type, hence why the data flow for equipment is one directional.
Hopefully this has explained CodeBook System and Shared parameters fully, but if in doubt, contact CodeBook support who will be sure to point you in the right direction.
Happy CodeBooking!
Monday, 28 November 2011
Content is King!
Downloading free Revit families vs. buying stock families vs. modelling your own is under constant debate within most practices. Personally I think there is room for each, but before using any family within a project - you should take time to understand what it contains and what LOD it has been modelled to.
The 'grey hairs' are often misled into thinking there is a sea of free families out there, perfectly modelled that will insert themselves directly into a project. As Steve points out in his post (below), it's still the wild west out there...
http://revitoped.blogspot.com/2011/11/content-critique.html
The 'grey hairs' are often misled into thinking there is a sea of free families out there, perfectly modelled that will insert themselves directly into a project. As Steve points out in his post (below), it's still the wild west out there...
http://revitoped.blogspot.com/2011/11/content-critique.html
Sunday, 20 November 2011
CodeBook v10 - sneak peak!
The Revit Application Programming Interface (API) has been somewhat restrictive in recent years and whilst it is still not as "open" as many developers would like, it is significantly better now than it was 5 years ago when the first incarnation of CodeBook for Revit was unveiled.
CodeBook International's (CBI) development focus during the past 12 months has been to refine and optimize core functionality for Revit, enhance reporting and improve interoperability with 4, 5 and 6D systems. CodeBook also has a SQL server version and as one of the users involved in the beta testing for v10, I'm very excited about the official release!
CodeBook International have been increasing their global presence during the last few years and alongside releasing v10, CBI have a fresh new website, re-juvenated brand and clearer definition about what CodeBook is and how it's used by designers, construction companies and building owners
So you may have already seen some of the new functions and utilized them in your projects through a beta, however, there have been over 100 enhancements, tweeks, or new functions added in 2011 alone. For a full list review CIS-003 when you upgrade - but in the meantime below is a summary of the major updates:
CodeBook Interface:
_Equipment ID range extended
(10,000-79,000)
_Import equipment from another Library
_Add 6 Assemblies to Room Types
_Omit, remove & replace multiple equipment
Interoperability:
_Maximo integration enhanced
_HFBS import enhanced
_ESRI export
_Export to COBie
Reporting:
_FF&E reports added
_Flex custom report system introduced
_Word reports also export a pdf
Revit interface:
_Assign family to a room
_Edit / delete parameters
_Nested family parameters updated
_Link Doors in separate model to rooms
_CB shared params always added
...and last but by no means least CodeBook shuttle is back which deserves a separate post.
There are a few functions that I think will be very useful, so here's a bit more info on them:
Troubleshooting Room links is accessed through the Revit Add-ins menu>Build>Troubleshoot and this allows you to put a marker into the rooms identifying which are linked, duplicates and unlinked rooms. You can also unlink all duplicates, which is sometimes easier than working out which is correct and you can also remove "phantom" rooms (not placed rooms).
Updating the value for a parameter en-masse is now possible and you can also delete a parameter from your project. Whilst this can be a very useful tool, take some time to double check what you are doing so that you don't overwrite or delete data that is in use.
When updating from the BIM model, CodeBook will also now place a red marker and generate a text file to list out the families that are not being reported (i.e. inside a room). This is a hugely valuable tool and knowing unequivically which items are not being reported immediately after updating will save lots of time.
In the case of items falling outside a room, that should be reported, for example a window blind there is now the function to assign these to a room. I know this has been high on people's wish list for some time.
So that gives you a taster of what to expect from CodeBook version 10 when it is officially released, which I believe will be in the next fortnight, to coincide with this years Autodesk University.
CodeBook International's (CBI) development focus during the past 12 months has been to refine and optimize core functionality for Revit, enhance reporting and improve interoperability with 4, 5 and 6D systems. CodeBook also has a SQL server version and as one of the users involved in the beta testing for v10, I'm very excited about the official release!
CodeBook International have been increasing their global presence during the last few years and alongside releasing v10, CBI have a fresh new website, re-juvenated brand and clearer definition about what CodeBook is and how it's used by designers, construction companies and building owners
So you may have already seen some of the new functions and utilized them in your projects through a beta, however, there have been over 100 enhancements, tweeks, or new functions added in 2011 alone. For a full list review CIS-003 when you upgrade - but in the meantime below is a summary of the major updates:
CodeBook Interface:
_Equipment ID range extended
(10,000-79,000)
_Import equipment from another Library
_Add 6 Assemblies to Room Types
_Omit, remove & replace multiple equipment
Interoperability:
_Maximo integration enhanced
_HFBS import enhanced
_ESRI export
_Export to COBie
Reporting:
_FF&E reports added
_Flex custom report system introduced
_Word reports also export a pdf
Revit interface:
_Assign family to a room
_Edit / delete parameters
_Nested family parameters updated
_Link Doors in separate model to rooms
_CB shared params always added
...and last but by no means least CodeBook shuttle is back which deserves a separate post.
There are a few functions that I think will be very useful, so here's a bit more info on them:
Troubleshooting Room links is accessed through the Revit Add-ins menu>Build>Troubleshoot and this allows you to put a marker into the rooms identifying which are linked, duplicates and unlinked rooms. You can also unlink all duplicates, which is sometimes easier than working out which is correct and you can also remove "phantom" rooms (not placed rooms).
Updating the value for a parameter en-masse is now possible and you can also delete a parameter from your project. Whilst this can be a very useful tool, take some time to double check what you are doing so that you don't overwrite or delete data that is in use.
When updating from the BIM model, CodeBook will also now place a red marker and generate a text file to list out the families that are not being reported (i.e. inside a room). This is a hugely valuable tool and knowing unequivically which items are not being reported immediately after updating will save lots of time.
In the case of items falling outside a room, that should be reported, for example a window blind there is now the function to assign these to a room. I know this has been high on people's wish list for some time.
So that gives you a taster of what to expect from CodeBook version 10 when it is officially released, which I believe will be in the next fortnight, to coincide with this years Autodesk University.
Tuesday, 8 November 2011
CodeBook appoint reseller in South East Asia!
Having lived and worked in S.E.Asia for several years, I can say from first hand experience, that CodeBook has a captive market and real growth opportunities there.
National and local government's in the region are switching onto BIM and coupled with their desire for brief conformity, whilst developing large numbers of similar schemes - CodeBook is a great fit.
CodeBook has a translation editor so you can re-create CodeBook in any language (providing you also know english!)
Also with tools like Google Translate, which is able to convert a webpage from one language to another I predict news will spread like wildfire!
Here is the announcement in Chinese:
http://translate.google.com.au/translate?hl=en&sl=en&tl=zh-TW&u=http%3A%2F%2Fwww.codebookinternational.com%2Fmedia%2Fnews-releases%2Fisbim-reseller
Vietnamese:
http://translate.google.com.au/translate?hl=en&sl=en&tl=vi&u=http%3A%2F%2Fwww.codebookinternational.com%2Fmedia%2Fnews-releases%2Fisbim-reseller
Korean:
http://translate.google.com.au/translate?hl=en&sl=en&tl=ko&u=http%3A%2F%2Fwww.codebookinternational.com%2Fmedia%2Fnews-releases%2Fisbim-reseller
Plus the english version:
http://www.codebookinternational.com/media/news-releases/isbim-reseller
National and local government's in the region are switching onto BIM and coupled with their desire for brief conformity, whilst developing large numbers of similar schemes - CodeBook is a great fit.
CodeBook has a translation editor so you can re-create CodeBook in any language (providing you also know english!)
Also with tools like Google Translate, which is able to convert a webpage from one language to another I predict news will spread like wildfire!
Here is the announcement in Chinese:
http://translate.google.com.au/translate?hl=en&sl=en&tl=zh-TW&u=http%3A%2F%2Fwww.codebookinternational.com%2Fmedia%2Fnews-releases%2Fisbim-reseller
Vietnamese:
http://translate.google.com.au/translate?hl=en&sl=en&tl=vi&u=http%3A%2F%2Fwww.codebookinternational.com%2Fmedia%2Fnews-releases%2Fisbim-reseller
Korean:
http://translate.google.com.au/translate?hl=en&sl=en&tl=ko&u=http%3A%2F%2Fwww.codebookinternational.com%2Fmedia%2Fnews-releases%2Fisbim-reseller
Plus the english version:
http://www.codebookinternational.com/media/news-releases/isbim-reseller
CodeBook Health Secrets revealed!
OK, so I needed to use a catchier title than "Database maintenance" in order to get anyone to read this post... well you're here now so you may as well carry on reading!
In this post I've outlined some of the common "health problems" that CodeBook projects can suffer from and how to resolve them. After reading this post, your very next step should be to implement a database maintenance policy on your projects as soon as possible.
Most AutoCAD files need to be purged once in a while, sometimes even "super purged", Revit models too can get clogged up with redundant data and need to be purged, compacted and central files periodically rebuilt - well CodeBook files also require the odd bit of maintenance.
The technical reason for this is that when you add information to a database, space is allocated for that information and when you delete something the space allotted for the information continues to be held in reserve by the database and it is not released for re-use. Likewise, extra space, created by modifying and shortening records, is not released for reuse.
So there are several ways to tidy up or compact your database, you can simply open the database in Microsoft Access and from the Office button select Manage > Compact and Repair Database. If you don't have Microsoft Access installed, or opening up a database in Access scares you - you can do this in CodeBook through File > Compact Project.
From within CodeBook you can also set the database to Auto-compact once it gets to a certain filesize. From the Project Properties window > Database Settings, there is a box labelled "Auto-compact database at size" in which you can enter a number.
Note: choose a number to small and you're database will perpetually auto-compact, choose a number too large and you won't get any real value out of this.
As mentioned in a previous post, you can have a single database which stores all of the buildings, departments and rooms - but you may also choose to split this up into several more manageable databases when working within a team environment with multiple Revit FF&E models and users accessing and contributing to the data. This has it's pros and cons of course, typically I try to keep project database size to under 15mb wherever possible.
In addition there may be redundant data lurking in your database, which should, but has not yet been deleted. What I mean by this are things like, unlinked rooms no longer in use, duplicate rooms, lookups created by mistake, room data templates copied in error and equipment that someone else must have created??
I'm stepping into slightly dangerous turf here... but I'm a firm believer in not carrying around unnecessary baggage within files and blasting away data that is not actively in use. BUT, before doing so take some time to double check the data is definitely not being used, think it through, take a backup of your files and talk to others.
The odd unlinked (red) rooms will be common in the early stages of a project, but once the planning has settled down, the 1:200 departmental layouts have been signed off and you enter the Design Development phase you should ideally have a database full of linked (blue) rooms and a Revit model full or rooms with parameter Linked_Status = 'Valid Link'
Unlinked rooms in CodeBook may originate from the schedule of accommodation (space programme), a room may have become accidentally unlinked or even deleted from the model and so a "due dilligence" check needs to be carried out before it is deleted. In order to check this, I would first run a full synchronise for the project so all linked rooms are coloured blue in CodeBook and each linked Revit Room has a Linked_Status parameter value of 'Valid Link'.
There are lots of wonderfully technical ways to review these, but I find a visual "common sense" check is normally the quickest and best method. A quick eyeball check of each department will identify unlinked rooms in CodeBook and through a Revit schedule you can identify any unplaced or unlinked rooms in Revit. Using a combination of the CodeBook display rooms function, find room using BIM hit and the Revit function Show (from within a schedule) will zoom you to any rooms that you need to check.
New and experienced users will generate extra lookup values and room data template duplicates, whilst developing the project. Often this happens by a lookup value simply becoming obsolete, for example, a type of floor finish might be specified early on and subsequently be deleted from the scheme. Also templates may be duplicated in error and then not removed.
You may ask yourself why would someone do this - i.e. create unecessary data? Using any software is difficult before it becomes easy, and it's always easy when you know how.
Before getting rid of these items, you should first check if and where they are being used - i.e. assigned to a room and form part of that rooms data. To do this we generate lookup and room data template usage reports, which list out the rooms that are using the value or template.
From within the Lookups Editor or Room Data Templates window, you can generate these usage reports quite easily. (note, you'll need to do this for each project database)
Equipment can also become redundant and again, like lookups and templates, we first need to assess whether these are in use within the project before removing them. If you suspect an item is no longer in use, then if you browse to the item in the Equipment Library window, you can generate a usage report by selecting File > Usage Report.
You can 'Hide' individual items of FF&E, but if you are confident using Access, or even Excel based formula's you will be able to work out which items exist within your project as required or designed equipment, and compare this against the overall equipment in your library. Once you have identified the equipment that you want to hide, there is a nifty and fairly recent function that will let you do this en masse.
From Librarian > Update Data > Batch Hide Equipment, this will open a window with 2 buttons, select "Create xls file of current library" and CodeBook will generate an excel list of the equipment within your library.
The excel file has a column 'Show or Hide' which you can edit accordingly. Once you've finished editing your excel file, select the Update button, browse to your freshly updated xls file and CodeBook will do the rest.
So many times I've heard people say "Well I didn't create it, so I'm not going to delete it." But these are normally the same people who complain about having too many lookups, or templates they know should be removed.
Everyone should be responsible for keeping the project dataset lean and mean, and whilst it may not be everyones role to remove redundant data you should encourage your team not to suffer in silence. Hope this gives you a few ideas...
In this post I've outlined some of the common "health problems" that CodeBook projects can suffer from and how to resolve them. After reading this post, your very next step should be to implement a database maintenance policy on your projects as soon as possible.
Most AutoCAD files need to be purged once in a while, sometimes even "super purged", Revit models too can get clogged up with redundant data and need to be purged, compacted and central files periodically rebuilt - well CodeBook files also require the odd bit of maintenance.
The technical reason for this is that when you add information to a database, space is allocated for that information and when you delete something the space allotted for the information continues to be held in reserve by the database and it is not released for re-use. Likewise, extra space, created by modifying and shortening records, is not released for reuse.
So there are several ways to tidy up or compact your database, you can simply open the database in Microsoft Access and from the Office button select Manage > Compact and Repair Database. If you don't have Microsoft Access installed, or opening up a database in Access scares you - you can do this in CodeBook through File > Compact Project.
From within CodeBook you can also set the database to Auto-compact once it gets to a certain filesize. From the Project Properties window > Database Settings, there is a box labelled "Auto-compact database at size" in which you can enter a number.
Note: choose a number to small and you're database will perpetually auto-compact, choose a number too large and you won't get any real value out of this.
As mentioned in a previous post, you can have a single database which stores all of the buildings, departments and rooms - but you may also choose to split this up into several more manageable databases when working within a team environment with multiple Revit FF&E models and users accessing and contributing to the data. This has it's pros and cons of course, typically I try to keep project database size to under 15mb wherever possible.
In addition there may be redundant data lurking in your database, which should, but has not yet been deleted. What I mean by this are things like, unlinked rooms no longer in use, duplicate rooms, lookups created by mistake, room data templates copied in error and equipment that someone else must have created??
I'm stepping into slightly dangerous turf here... but I'm a firm believer in not carrying around unnecessary baggage within files and blasting away data that is not actively in use. BUT, before doing so take some time to double check the data is definitely not being used, think it through, take a backup of your files and talk to others.
The odd unlinked (red) rooms will be common in the early stages of a project, but once the planning has settled down, the 1:200 departmental layouts have been signed off and you enter the Design Development phase you should ideally have a database full of linked (blue) rooms and a Revit model full or rooms with parameter Linked_Status = 'Valid Link'
Unlinked rooms in CodeBook may originate from the schedule of accommodation (space programme), a room may have become accidentally unlinked or even deleted from the model and so a "due dilligence" check needs to be carried out before it is deleted. In order to check this, I would first run a full synchronise for the project so all linked rooms are coloured blue in CodeBook and each linked Revit Room has a Linked_Status parameter value of 'Valid Link'.
There are lots of wonderfully technical ways to review these, but I find a visual "common sense" check is normally the quickest and best method. A quick eyeball check of each department will identify unlinked rooms in CodeBook and through a Revit schedule you can identify any unplaced or unlinked rooms in Revit. Using a combination of the CodeBook display rooms function, find room using BIM hit and the Revit function Show (from within a schedule) will zoom you to any rooms that you need to check.
New and experienced users will generate extra lookup values and room data template duplicates, whilst developing the project. Often this happens by a lookup value simply becoming obsolete, for example, a type of floor finish might be specified early on and subsequently be deleted from the scheme. Also templates may be duplicated in error and then not removed.
You may ask yourself why would someone do this - i.e. create unecessary data? Using any software is difficult before it becomes easy, and it's always easy when you know how.
Before getting rid of these items, you should first check if and where they are being used - i.e. assigned to a room and form part of that rooms data. To do this we generate lookup and room data template usage reports, which list out the rooms that are using the value or template.
From within the Lookups Editor or Room Data Templates window, you can generate these usage reports quite easily. (note, you'll need to do this for each project database)
Equipment can also become redundant and again, like lookups and templates, we first need to assess whether these are in use within the project before removing them. If you suspect an item is no longer in use, then if you browse to the item in the Equipment Library window, you can generate a usage report by selecting File > Usage Report.
You can 'Hide' individual items of FF&E, but if you are confident using Access, or even Excel based formula's you will be able to work out which items exist within your project as required or designed equipment, and compare this against the overall equipment in your library. Once you have identified the equipment that you want to hide, there is a nifty and fairly recent function that will let you do this en masse.
From Librarian > Update Data > Batch Hide Equipment, this will open a window with 2 buttons, select "Create xls file of current library" and CodeBook will generate an excel list of the equipment within your library.
The excel file has a column 'Show or Hide' which you can edit accordingly. Once you've finished editing your excel file, select the Update button, browse to your freshly updated xls file and CodeBook will do the rest.
So many times I've heard people say "Well I didn't create it, so I'm not going to delete it." But these are normally the same people who complain about having too many lookups, or templates they know should be removed.
Everyone should be responsible for keeping the project dataset lean and mean, and whilst it may not be everyones role to remove redundant data you should encourage your team not to suffer in silence. Hope this gives you a few ideas...
Wednesday, 12 October 2011
Backups, archiving and milestone images
One of the most useful CodeBook functions, is the ability to create a Revision database and compare milestone images against one another. You might be asking yourself "what does all of that mean?" Well don't worry, you're probably not the only person and in this post I'll cover basic backup procedures, images and revision databases.
Backups
In order to make a full backup of your data, you'll need to take a copy of the CodeBook project database(s) and also the library files (equipment + room data). As a general rule of thumb it's a good idea to take a backup of your files on a weekly basis and at each project milestone, but it's worth speaking to your IT department to find out how often they run a full studio backup. Typically this is carried out monthly and a backup tape stored locally as well as off site. Larger practices may do this on a weekly basis, but whatever the frequency this will inform the amount of backup files you should keep on your server at any time. If your practice take monthly backups and you are also taking weekly backups, you should only ever need to keep 1 months worth of live backups on your server at any time. The rest can be retrieved from the backup tapes your IT department have taken.
Over the years, I've rarely reverted to a backup file older than one month, as typically the design has moved on substantially during that time meaning you'd lose more than you'd gain. If you take weekly backups and don't delete any of these till the project is over, you could end up with a large amount of unnecessary data stored on your server. That data will also be backed up monthly in the studio backup and so the issue manifests exponentially. The CodeBook data alone won't cause problems, but having a sensible approach towards backups is critical when working in a team environment - if everyone is taking more backups than they really need and never purging these from the server, it is inevitable that you will run into problems at some point.
For large projects you may have a series of staggered milestones and there may be a timeframe of longer than one month between them. This is where milestone image database should be utilized.
Images of the past...
An image database is a single consolidated database which merges the project, equipment and room data files to provide a snapshot of the data at a specific moment in time. If you create image databases at each project milestone, you're able to generate a revision database, which compares milestone image 1 with milestone image 2. The reports that you can generate from a Revision database highlight the differences between the two milestone images.
This can be a very powerful tool if used correctly and can aid with your in-house QA checking. Often clients want validation that their comments (from a previous meeting) have been taken on board, so providing that all of the clients comments have indeed been made, you're able to create a report which demonstrates this.
Generating an image database is quite a simple process, from the Control Centre select Output>Create Image Database... and you'll then be asked to confirm the location where the file will be saved. (In Project Properties you can specify the default location for this) A window will pop up asking you to add a note, which will act as a future reminder. It's obvious right now why you are creating the image database, but may not be 100% clear in the future, especially if you are working on a large project. Speaking from personal experience, clear notes are valuable and will help ensure you can locate the right image database in future and reduce the chances for error.
One very important thing to consider is precisely when you create the image database. If you create the image before producing reports and schedules, there is the chance that "last minute changes" could be made (having reviewed the reports) and your image does not fully reflect the issued set of documents. Similarly if you leave it till a few days after the issue has been made, again there may be differences between the issued set of information and the image you have generated.
The right time to create the image is straight after your reports have been generated and in conjunction with this, you should also be mindful of what other users may be working on. If another user is editing the project, equipment or room data library this may affect your image database. The key thing is communication and it should be possible to organize the production of reports and image databases to happen when the rest of the team are not editing the CodeBook data - or perhaps vice versa, the team are aware when this is happening and that they should not be editing CodeBook data.
The default CodeBook filename used for images includes the current date and time, it's advisable to keep this but to also include the project, sector and/or department the image relates to. This will be useful later on when you want to create a revision database and need to find the right image file to use.
Revision databases
An image database cannot be opened directly in CodeBook per se, it's purpose is to provide a point of comparison - so the way that you access the image information is to create a revision database. The process for creatng a revisions database is straightforward, from the Output menu simply select Create Revision Database and a pop up window will prompt you to specify the latest image and comparison image database. The latest image database should automatically be filled in with details of the last one you created, the comparison image should be the project/sector/department image database you created at the previous project milestone.
So give it a go, explore the Revision database reports that are available and start getting real value out of your data.
Backups
In order to make a full backup of your data, you'll need to take a copy of the CodeBook project database(s) and also the library files (equipment + room data). As a general rule of thumb it's a good idea to take a backup of your files on a weekly basis and at each project milestone, but it's worth speaking to your IT department to find out how often they run a full studio backup. Typically this is carried out monthly and a backup tape stored locally as well as off site. Larger practices may do this on a weekly basis, but whatever the frequency this will inform the amount of backup files you should keep on your server at any time. If your practice take monthly backups and you are also taking weekly backups, you should only ever need to keep 1 months worth of live backups on your server at any time. The rest can be retrieved from the backup tapes your IT department have taken.
Over the years, I've rarely reverted to a backup file older than one month, as typically the design has moved on substantially during that time meaning you'd lose more than you'd gain. If you take weekly backups and don't delete any of these till the project is over, you could end up with a large amount of unnecessary data stored on your server. That data will also be backed up monthly in the studio backup and so the issue manifests exponentially. The CodeBook data alone won't cause problems, but having a sensible approach towards backups is critical when working in a team environment - if everyone is taking more backups than they really need and never purging these from the server, it is inevitable that you will run into problems at some point.
For large projects you may have a series of staggered milestones and there may be a timeframe of longer than one month between them. This is where milestone image database should be utilized.
Images of the past...
An image database is a single consolidated database which merges the project, equipment and room data files to provide a snapshot of the data at a specific moment in time. If you create image databases at each project milestone, you're able to generate a revision database, which compares milestone image 1 with milestone image 2. The reports that you can generate from a Revision database highlight the differences between the two milestone images.
This can be a very powerful tool if used correctly and can aid with your in-house QA checking. Often clients want validation that their comments (from a previous meeting) have been taken on board, so providing that all of the clients comments have indeed been made, you're able to create a report which demonstrates this.
Generating an image database is quite a simple process, from the Control Centre select Output>Create Image Database... and you'll then be asked to confirm the location where the file will be saved. (In Project Properties you can specify the default location for this) A window will pop up asking you to add a note, which will act as a future reminder. It's obvious right now why you are creating the image database, but may not be 100% clear in the future, especially if you are working on a large project. Speaking from personal experience, clear notes are valuable and will help ensure you can locate the right image database in future and reduce the chances for error.
One very important thing to consider is precisely when you create the image database. If you create the image before producing reports and schedules, there is the chance that "last minute changes" could be made (having reviewed the reports) and your image does not fully reflect the issued set of documents. Similarly if you leave it till a few days after the issue has been made, again there may be differences between the issued set of information and the image you have generated.
The right time to create the image is straight after your reports have been generated and in conjunction with this, you should also be mindful of what other users may be working on. If another user is editing the project, equipment or room data library this may affect your image database. The key thing is communication and it should be possible to organize the production of reports and image databases to happen when the rest of the team are not editing the CodeBook data - or perhaps vice versa, the team are aware when this is happening and that they should not be editing CodeBook data.
The default CodeBook filename used for images includes the current date and time, it's advisable to keep this but to also include the project, sector and/or department the image relates to. This will be useful later on when you want to create a revision database and need to find the right image file to use.
Revision databases
An image database cannot be opened directly in CodeBook per se, it's purpose is to provide a point of comparison - so the way that you access the image information is to create a revision database. The process for creatng a revisions database is straightforward, from the Output menu simply select Create Revision Database and a pop up window will prompt you to specify the latest image and comparison image database. The latest image database should automatically be filled in with details of the last one you created, the comparison image should be the project/sector/department image database you created at the previous project milestone.
So give it a go, explore the Revision database reports that are available and start getting real value out of your data.
Subscribe to:
Posts (Atom)