So I came up with this today, and thought I'd share.
At my firm, we use a Drawing Specification for 95% of our projects. It's a CAD drawing with the specification composed in Mtext that we then Link in to our model. Our Piping spec lists piping material, joint methods, fitting types, and valve types for various systems (Domestic Water, Chilled Water, Natural Gas, etc.) I was editing the Piping Specification today, removing systems that weren't included, adding systems that were, when I thought "there has to be a better way to deal with this crap."
I started tinkering in our Project Template, and pretty quickly came up with a Piping System Schedule that lists all of our Piping Systems, along with a series of plain Text Project Parameters for Pipe Material, Pipe Joint Method, Pipe Fitting Type, and Pipe Valve Type. They're Type Parameters that apply to the System Type. I used the stock "Description" parameter to group them in the same way that our standard spec does (For instance, Compressed Air, Nitrogen, and Vacuum piping use the same spec.) And, of course, I had "Itemize Every Instance" unchecked.
That's about all there is to it. If any of these modeled systems are deleted, they drop off the schedule, BUT because the Text parameters apply to the System Types and not the Systems themselves, the data isn't lost. If I add a piping system back into the model, the data comes right back. I've seen architects use things like this for their various tables, and now I see why!

Here are the parameters my schedule uses. Like I said, nothing fancy!

Now, to see if my bosses (who don't understand Revit) will go for it!
I feel like I've had a serious "Ah ha" moment here. I'm wondering what other "spec items" I can automate away!
At my firm, we use a Drawing Specification for 95% of our projects. It's a CAD drawing with the specification composed in Mtext that we then Link in to our model. Our Piping spec lists piping material, joint methods, fitting types, and valve types for various systems (Domestic Water, Chilled Water, Natural Gas, etc.) I was editing the Piping Specification today, removing systems that weren't included, adding systems that were, when I thought "there has to be a better way to deal with this crap."
I started tinkering in our Project Template, and pretty quickly came up with a Piping System Schedule that lists all of our Piping Systems, along with a series of plain Text Project Parameters for Pipe Material, Pipe Joint Method, Pipe Fitting Type, and Pipe Valve Type. They're Type Parameters that apply to the System Type. I used the stock "Description" parameter to group them in the same way that our standard spec does (For instance, Compressed Air, Nitrogen, and Vacuum piping use the same spec.) And, of course, I had "Itemize Every Instance" unchecked.
That's about all there is to it. If any of these modeled systems are deleted, they drop off the schedule, BUT because the Text parameters apply to the System Types and not the Systems themselves, the data isn't lost. If I add a piping system back into the model, the data comes right back. I've seen architects use things like this for their various tables, and now I see why!
Here are the parameters my schedule uses. Like I said, nothing fancy!
Now, to see if my bosses (who don't understand Revit) will go for it!
I feel like I've had a serious "Ah ha" moment here. I'm wondering what other "spec items" I can automate away!
Comment