Here's come the problem. If I need a door to be rated, I have to make a new type for this door (say a hollow metal door) as a rated door that is different from a non-rated door. As a result, you could end up with many more duplicates for the same type of doors.
For many users, they would create their own "Fire Rating" parameter as an instance base shared parameter (if needed for tagging) or just a project parameter and use it for schedule. I often find this annoying since the available fields from the door schedule will now have 2 parameters both call "Fire Rating". I have seen people somehow get confused and not knowing which one to use.
My office was undergoing a process of re-building all the door families for our office library. I was discussing this same issue with some of my peers about what's the best way to handle this. As it turns out, there is a much easy and elegant way to get around this without using user-created parameters for fire rating.
|Hard-coded "Fire Rating" parameter that is locked/greyed out|
Next is to go to Family Category --> change your door from doors category to other category. In my case, I just chose the Generic Models category.
Since Generic Models do not have built-in parameter for "Fire Rating", Revit will now treat this parameter as a user-defined parameter; therefore, you can now go in and modify it!
Just go to modify and switch from "Type" to "Instance". Voila! You now have this as an instance parameter!!!
However, don't forget to go back to Family Category and switch it back from generic models to doors.
Put this modified door back into the project and now you can assign "Fire Rating" as an instance parameter under properties.
This trick should also work on other hard-coded parameters in other families. The key to understand this is to switch the original family to something that does not have its specific parameter built-in. Hope this will be a helpful tip and I think the factory should somehow re-think how the users want to utilize family parameter in projects.