Although this has been discussed a great lengths by others, I have to explicitly call out those who are continuing to perpetuate the false idea that creating pipe types for the purpose of graphical filtering or naming is the correct thing to do. This is a myth.
This issue originally stemmed from the lack of available OTB system types within Revit. Those who have done lab work know that the piping systems can go easily into the double digits. Currently the pipe connector systems available by default within Revit are as follows
- domestic hot water
- domestic cold water
- fire protection wet
- fire protection dry
- fire protection pre-action
- fire protection other
- hydronic return
- hydronic supply
- Other (the universal donor)
At some point in time someone thought it would be a good idea to duplicate pipe types and rename the family types to correspond with the system it was “supposed” to be on (ie. chilled water supply). Notice the use of quotations. This is the first issue with this type of categorization. You will always to be able to create the filter, visibility, and naming settings you want even if the pipe is on the WRONG system. this allows you to override the actual system with the wrong one. Why would you ever want to do that? And worse yet, you may never catch it.
Here are some of the issues with creating pipe families and types by system
- doesn’t allow you to catch incorrect system connections
- creates duplicates of already defined real pipe types (steel, PVC, etc.)
- reinforces bad habit of not creating or completing piping systems
As outlined a while back by Martin Schmid @ Inside the System, the correct way to create an unlimited amount of piping systems is through the use of the system name.
The original purpose of Pipe Types was to be able to define pipes by their material, pressure class, dimensions and joint/connection types. There is no reason to duplicate steel or copper piping for the purpose of visibility and graphical settings.
Stay tuned next time for Part II of Mythbusters where I will talk about Worksets.