Anuncios
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
Comentario

The biggest piece of information I would like to see is degrees of bend.  Code requires that we have no more than 360 degrees of bend in the conduit between pull points (j-boxes, conduit bodies, outlet locations, etc.), so this is a piece of information that is very important to the design of routing.  If we get over 360 degrees (or if we're following our company's standard spec, 270), we would likely add a junction box or condulet as a pull point.

 

In healthcare, we quite often have several conduit systems ("Life Safety", "Critical", "Equipment", "Optional Standby", etc.) similarly to how mechanical/plumbing might have "Supply", "Return", "Domestic Hot", "Chilled Water Return", etc.  In one project, we have a project parameter associated with conduits that we are applying a view filter to in order to get color into our model.  However, we are still using a filter, which could vary between views (and different view templates) inadvertently as the project grows.  It would be wonderful if we could create a "Conduit System" and apply graphic overrides to it by type (like how mechanical can globally make all of their ducts on the "Supply air" system blue).

 

Additionally, the Comments parameter is the only one that carries over from the conduit objects into the schedule.  I was attempting to select a conduit run, edit our project parameter to the correct system, and view it in the conduit run schedule (and create a separate conduit run schedule for our Life Safety, Critical, etc.).  The colors changed properly per the view's filter settings, but the conduit run schedule showed our project parameter blank, even though every object in the run had the same value.  This meant that I couldn't automatically schedule based on my parameter.  I could type the value into our project parameter from the schedule, but that requires me to type the information in twice, and it's possible to inadvertently change the system a conduit run is on by typing in the wrong row.  With only one parameter (other than family, type, size, length, and a few other properties of the run that aren't text-based) that the schedule pulls from the model, I have to very carefully craft what I type into it to make sure I don't inadvertently change my project parameter's value on the wrong row, changing the conduit's color without realizing it.  If conduit runs were treated more like conduit systems, I'd be able to schedule based on a project parameter.