PDA

View Full Version : Uniformat Class / Assembly Codes / SmartBIM QTO



cliff collins
2010-02-11, 05:24 PM
When assigning Assembly Codes for families such as millwork/trim on Interior Design
projects, which is the best category in the Uniformat system? I can't find anything for wood trim/millwork in the list. I suppose this list can be edited, similar to the Keynote text file, to include new categories? But what "standard" should be followed when adding new categories? Is there a published Uniformat document somewhere?

Also, a good deal of "custom content" on our projects has been modelled as Generic Models, and even when assigning an Assembly Code for those items ( such as lathe-turned wood spindles, wood knee brackets, countertops, etc. ) the SmartBIM QTO program cannot assign a cost to these families?

We are trying to get all users to model new content in the correct family template,
and to avoid using generic models when possible.

This is very important when using Revit with downstream applications for 4D and 5D
scheduling and cost estimation.

cheers.........


edit: I have found this: http://www.omniclass.org/
and will see if this answers some of these questions........

arqt49
2010-02-11, 06:17 PM
You can get the uniformat II here: http://www.bfrl.nist.gov/oae/publications/nistirs/6389.pdf

You can get more information here: http://www.csinet.org/s_csi/sec.asp?CID=1379&DID=11342

Keep in mind that Uniformat is a classification for elements, and it's not very extensive (4 levels).

I attached a sample of the Uniformat draft from April 2007.

phyllisr
2010-02-12, 06:58 AM
For fun and games when you are really bored, you can open the Uniformat and OmniClass .txt files that ship with Revit and find all the mistakes. You can even make categories of mistakes!

One category could be simple typos that spellcheck does not find - you can blame Autodesk for that. Extra spaces and punctuation problems could go here. Another might be fabricated words that do not mean anything and for which there are perfectly good words that actually mean something. Not sure who to blame for this one. Then there is the category of parts of speech used incorrectly like verbs used as nouns. Another really fun thing to do is count all the inconsistencies with hyphens and compound words. Have not decided if problems with upper and lower case should be a separate category or whether they belong with typos and punctuation. Or maybe punctuation could share a separate category .

And if you still have nothing to do and you finish this, you can start on MasterFormat! At least we cannot blame Autodesk for any of that.

OK, I am finished venting now... :-)