Filter Filtering Gotcha

When you create or edit a view Filter we can apply a Filter to the list of categories based on discipline.

Filtering the list of categories has a direct impact on the Filter Rules > Filter by: list too. If you tell Revit to only show you Architecture categories then you'll find the available parameters listed in the Filter by: criteria drop down will not include parameters that are related to other disciplines. For example, if you were hoping to use the filter to alter the way MEP elements look when they are linked into your model then you might be confused until you realize that earlier you told Revit to only show you Architectural stuff.

Remember the Filter's Filter. Same thing can happen in the View Templates, Visibility/Graphics dialog and Object Styles dialogs.

Level Matching in Schedules

If you've used the Level parameter in a door or room schedule to sort and group them you may have also been surprised when you attempt to do the same thing including a linked file's elements. The Level parameter becomes unavailable in the filter tab of Schedule properties when it includes linked elements.

Behind the scenes Revit doesn't look at a Level the same way we do. We see a name like ground or second floor but Revit sees a unique ID instead. That means a linked project might have the same levels, the names we read, but they aren't the same ID. To a computer they couldn't be more different.

Revit reconciles this same situation with phases by providing a phase mapping tool in the properties of each linked model. When we use that dialog we are telling Revit that "this" is the same as "that". It seems pretty reasonable to me to do the same thing for levels. Provide a level mapping button right next to phase mapping, or combine them into a project mapping dialog. Maybe it doesn't have to be a mapping dialog. We could just interact with them in a view to map them to each other. We do this when we use Copy/Monitor.

The current workaround is to filter a schedule based on some other data that is uniquely level related or worse, actually entering "level" information into each element so they can be filtered by it. Add to the un-Revityness is that we now have to encourage people to add the same info to their model so we can use it in our schedule. Especially frustrating when the "same" info is already in the model.

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.