Sunday, December 02, 2012

OmniClass as Criteria

I heard mention of Omniclass during Autodesk University a few times last week. Each component (loadable) family in Revit has a pair of parameters built for OmniClass. What is that you say?

Lifted directly from their web site:
    The OmniClass Construction Classification System (known as OmniClass™ or OCCS) is a classification system for the construction industry. OmniClass is useful for many applications, from organizing library materials, product literature, and project information, to providing a classification structure for electronic databases. It incorporates other extant systems currently in use as the basis of many of its Tables – MasterFormat™ for work results, UniFormat for elements, and EPIC (Electronic Product Information Cooperation) for structuring products.
Revit supplies the OmniClass Number and the related OmniClass Title for each family category.

It hasn't quite reached full citizenship in Revit because system families do not yet offer an option for assigning them OmniClass values, neither do rooms or spaces. You can certainly add your own shared parameters to do it but there won't be any linkage to the same table of values as provided in the image above, that's only for component families.

Revit has also always offered the UniFormat Assembly Code and Description, not for rooms or spaces either though. These two systems both provide a way to classify the essence of an element in the model, like the Dewey Decimal system helps to organize books in a library to some degree. If we are careful to assign appropriate values to the content we create we'll find we can harness them to enhance our experience with using schedules and filters. That's completely apart from the downstream possibilities of using it to help define specifications with tools like e-SPECS or BSD LinkMan.

Try hard to remember to assign a value for OmniClass and the Assembly Code so you and others can take advantage of them later.

1 comment:

Aaron Maller said...

Yeah, we had to do the Shared parameter thing, for an FM project we talked about in my class.

Unfortunately, we needed the data in System families, and in Systems themselves (for MEP), and we also had different Omniclass data for different Types (but not for different families), since some content was made with generic placeholders.

That gets really ugly, since the Omniclass data is under Family Parameters, and not Instances or Types. :(