Tuesday, October 31, 2006
Monday, October 30, 2006
Thanks to the new RevitCity 2.0 for also posting a link to my blog!
Thursday, October 26, 2006
- Version Number
In the case of creating a new family in the firm, version number would typically start at 1.0, Source would be the firm's name, and Author would be the author's name. For families that are produced by contracted consultants, Source would be the consultant's name, and author the employee of the consulting firm that creates the family. For downloaded content, source would be the website and author would be whatever the username is of the contributing "original" author, or as best can be determined. As part of integrating these three parameters with the process of creating new families we are planning/hoping to add them to all family templates so that the end user merely needs to be concerned with filling the parameters out. When creating new families in our firm we also require end users to provide a description, an assembly code (when it makes sense) and a keynote (also when it makes sense).
Why go to all this trouble? The tracking parameters help us to know where a family came from if it is in circulation. If we have the author and a version number we can to a certain extent more easily track down problems. If the author still works for us, we can just go back to them, version number helps, because there might be a more recently updated family that addresses the problem the user is having with the family. By requiring the descriptive data we are "future proofing" ourselves as we use E-Specs more, or if we work with contractors or other consultants where this type of data can be important, or if we figure out new and innovative ways to make use of the data.
We also include a version number in our Project Template file, which exsists as a project parameter under Project Info, no end user is ever going to bother touching it, and most people probably won't ever notice it. However, once again, if there is a problem with the template we can know what version the template is, furthermore everytime the template is updated we have an excel file where we track the version numbers and changes, thus, we can know what might be missing from an older template and or what needs to be updated to resolve an inherent problem with the template.
There is one downside to the "versioning" of our families, when reloading, even when "overwrite parameters of existing types" is selected the version number does not always update, which is rather unfortunate, as it makes it harder to track what version of a family is loaded into a particular project. Hopefully in the future Autodesk will provide some resolution to this issue.
Thanks for reading,
Wednesday, October 25, 2006
If you're a fellow Revit or BIM blogger (and I know who some of you are) and are interested in collaborting on building the search, and including it on your own blog, drop me a comment, or if I've already been in touch with you via other digital communiques contact me that way.
Monday, October 23, 2006
To fix this problem you need to create a detail component and nest into your 3D family. Detail components (2D geometry only) allow the use of filled regions (which thankfully can block patterns!). If you create a parametric detail component with a filled region, you can then nest it, and attach its parameters to the parameters of the 3D family. Once this is taken care of you can succesfully load the family into a project and get the results of the table on the left.
I highly reccomend creating a rectangular detail component with a filled region, with the lines set to "invisible", you can then use this component in a variety of situations. If you do not want the filled region to have a pattern or color, make sure to set the type properties of the filled region to "no pattern" and not a solid fill color. If however you want a material pattern you can choose whatever you like. You may also want some filled region detail components for other common shapes like circle, L, etc...
Setting the parameters to instance based will give you shape handles when the component is loaded that can be quickly grabbed & locked. These filled region detail components can be handy for detailing in project views too, rather than having to always create filled regions every time you need one. Instance parameters will make it so that you don't need multiple types.
Wednesday, October 18, 2006
Here's to Revit!
Tuesday, October 17, 2006
Wednesday, October 11, 2006
Construction Administration (CA) of a Revit project seems to be becoming a hot topic. There have been a couple of threads, some new, some ressurected, showing up on AUGI. Currently because of our average project sizes we are reccomending that projects should expect to export a full set of DWG documents when the Construction Documentation (CD) phase has ended. Generally we've found that while plans export very well, and sections generally do, we find that we need to do clean-up on elevations, and some general housekeeping on the other views. While on a very large project, it might take week to do this, we think its worth it. So far, from what we've seen when you have a large revit project, on a tight site, with a tight schedule, and unforseen conditions (that never happens right ;) ), Revit just doesn't lend itself to quickly producing RFI sketches and addendum. We want to keep the Revit model involved, but at the same time we need to face the realistic needs of our project teams.
Furthermore, the other kink in Revit is not being able to have a view on more than one sheet, this makes it very hard to issue an addendum sketch, and have the same drawing on the original sheet. There are some lenghty dicussions on AUGI about this topic, but suffice is to say, work arounds are just sometimes a pain. CA is fraught with enough difficulties, we don't need to make it harder for our own staff.
Hopefully Autodesk will find time to address this portion of Revit's use, and of course we will continue to encourage them to do so. :)
Thursday, October 05, 2006
After the powerpoint, which was interspersed with live Revit demos to illustrate various points, we moved on to creating a family. Here's a pic of what I told them they would have by the end of the day.
2 pick family with arrayed nested cabinet family that can be user modified, doors are also nested and interchangeable. As a bonus they're challenged to write the formula that will limit the number of cabinet instances so that they don't extend past the overall length (yes I did write the formula as proof of concept).
All of them did it (I had about 8 people in the class, course my CIO was reading his e-mail, didn't see Revit open on the laptop ;) ). It was a fantastic training session and we covered just about everything related to families. Workplanes, subcategories, parameters, formulas, shared & nested families, visibility settings, shared parameters, keynotes, and of course general best practices on building complex families. Everyone felt that the course was a great success, and I was very happy with the results. I was very fortunate in that one of my co-workers in the course is a note taking nazi and she has provided excellent written documentation of what we did, making it much easier to make it repeatable and tweakable.
At the start of the day I provided them with a CD that included the power point, a PDF synopis of key points to remember (printed too), the required family templates, keynote file, shared parameter file, excel file of the firm's additional subcategories, and examples of the finished families, and the doors (I pre-made them for them). My favorite part though was that I was also able to include progressive copies of the families. By setting the number of back-up copies to 250 I was able to create a sequence of files by saving after every major action as I created the families. In the end I have 14 sequential files of the base cabinet, they proved very useful as I had a latecomer to the class, and I was able to catch him up ASAP by simply opening one of the 14 files and he was ready to go.
All in all this was a great experience and I was very satisfied with the results, and everyone who participated thought that it was great (though a long day). Now though, I know where I can break up the course to do it in shorter smaller parts. In addition to teaching the course internally, I hope to take it public at some point (with some modifications ;) ). I look forward to doing it again and perfecting it. :)