Assembly Codes: Changing for 2006?

[Scott D Davis]

In January 2006, those of us using the CSI divisions in any of our work will need to reconfigure everything from the 16 division format, to the 50 division format. (yikes!)

Revit currently uses the 16 division format for assembly codes for objects, which other programs, such as E-specs, use to pull information from the model.

Question for the Factory is: Will there be an update to Revit, and all of the OOTB and Web Library content to the new system for assembly codes so that we can 'go live' in Jan 2006 with the new format?

[GuyR]

Scott,

If the factory don't do it for you just edit the file in the program directory.

Guy

[Scott D Davis]

GuyR,

Which file is that?

[gravelin]

UniformatClassifications.txt

[Scott D Davis]

Thanks!

I had never noticed that file before....

so if I change a classification of an object in my project, it updates this TXT file? Is this another file that needs to be on a network location so that everyone in the office has the same codes?

[gravelin]

it works in the other way....
You will get in Revit what you put in this .TXT file.

I don't know if it's a way to configure the path in revit to move this file.

[GuyR]

so if I change a classification of an object in my project, it updates this TXT file?

No, you need to change the text file first. The format is relatively straightforward you just need to be careful editing it. Otherwise you won't see anything in the assembly code tree when you restart Revit. I'd suggest backing up the existing file and then have a play.


Is this another file that needs to be on a network location so that everyone in the office has the same codes?

Yes if they all get revit.exe from the same machine. Copy it to each machine if not.

HTH,

Guy

[mlgatzke]

I would assume that this new format list will be available from the factory with the next release. I'm hoping that there will be a predefined method for the conversion of existing projects. I would think someone would have already worked out this list.

[Marek Brandstatter]

In January 2006, those of us using the CSI divisions in any of our work will need to reconfigure everything from the 16 division format, to the 50 division format. (yikes!)
From what I can tell, Revit's assembly codes (uniformatclassification.txt) are based on UNIFORMAT II http://www.uniformat.com (http://www.uniformat.com/) This is not the same as CSI Masterformat. Therefore the assembly codes should stay more or less the same.

http://www.mc2-ice.com/popular_conversion/popular_conversion_files/construct_code/levels.html

[Scott D Davis]

From the Uniformat website:


The ASTM "Standard Classification for Building Elements and Related Sitework -UNIFORMAT II" (E 1557-96 ) provides a common structure linking the building program, specifications, and estimates. Its integration in the design process results in improved communications and coordination among all project participants, an accelerated design, and significantly increased productivity. The classification provides the Project Manager with an essential tool to control project scope, cost, time and quality.

UNIFORMAT is recommended by the Construction Specifications Institute/ Construction Specifications Canada (CSI/CSC) to structure schematic phase specifications, and by the Design-Build Institute of America for performance specifications.
The CSI Masterformat is based upon the standards set by Uniformat.

[Marek Brandstatter]

to structure schematic phase specifications The key word is schematic.


MasterFormat, a classification that is based on products and materials, is a logical format choice when preparing detailed cost estimates. But a cost estimate prepared using a format based on a listing of products and materials is time consuming, costly, and inappropriate at the early design stages. Yet, it is in the early stages of design that economic analysis is most important in establishing the economically efficient choices among building alternatives. Only estimates based on an elemental classification such as UNIFORMAT II provide the necessary cost information for the analyst to evaluate building alternatives in a cost-effective manner. From a Uniformat document by Robert P. Charette & Harold E. Marshall

The two systems serve different purposes. The newly revised 48 division Masterformat 04 classification shouldn't impact on Uniformat or on Revit's assembly codes.

[jamesd10181097]

Would we want to wait to see if the new CSI division system actually takes hold.

As you pointed out in the other thread, Scott, the need to update everything to a new format is cumbursum. Though that might seem like alot of work to us on the drafting end think about the work for all the specifiers, directories like Sweets and ARCAT, all manufacturers liturature let alone all the contractors out there that are used to looking up particular sections for their work. Introduction of this new system would turn the whole industry on end. Everyone I know are so engrained in the current system that they have no intention of switching over for many different reasons.

CSI has tried to make drastic changes in the past and they never took hold, like the one where they proposed that all notation on drawings strictly being the section number, That did not last for a month.

I have reviewed the 2004 edition of the CSI masterformat, and though it makes alot of sense like giving different divisions to things like fire protection and security systems. The fact that everyone would have to change everything, I simply do not see it being widely embraced.

[mlgatzke]

I think that some of you are a little confused by the difference between UniFormat and MasterFormat. MasterFormat is an organizing schema that uses a 5 digit number based on material and assembly of an item (e.g. Metals, Masonry, Wood & Plastics, etc). UniFormat is an organizing schema that uses alphanumerics to organize items based on their use within the structure (e.g. substructure, shell, interior, etc). UniFormat was originally designed as an "outline" format that the user would then convert their information to MasterFormat when the project moved on to a more mature status. However, some smaller contractors (very small commercial and some residential) use UniFormat throughout the project construction cycle.

The two formats are actually very different, both in intent AND how things are organized. You would not be able to modify the UniformatClassifications.txt file. These two formats are too extensively different.

Sorry for the seeming rant, but I teach a class on CSI's CDT certification - of which this topic is covered extensively.

[Marek Brandstatter]

http://peoplelogicsoftware.com/products/estimating_guide.htm

The above link offers a useful overview of the different types of estimating.

[gillesl]

I would be careful with modifying the uniformatclassification.txt file for a few reasons.

1. Programs like e-specs and others are using these classifications to tie their systems into the revit model. If one modifies these classifications they are in essence braking any links that these third party applications are making.

2. Making modifications to this file is done on a local file and not a distributed file. Even on networked licenses there is a chance that changes will overwrite required classifications placed into the file by others. This makes for additional management requirements. In small firms this may be manageable but in large firms this could become a nightmare without version control.

3. There are coded items within the file which are needed by Revit for sorting and ordering processes within the program. Incorrect changes to this file could create unexpected results in the application or create aborted features.

If it were me I would ensure that there was a strict protocol established and that a strong disciplined approach would be taken before any application specific file were modified.