Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
What exactly are you proposing? I agree that conduit runs are not treated well (as are most other things on the electrical side of Revit), but they're not going to get better unless we provide more specific suggestions to Autodesk. The programmers aren't electrical designers, so they don't know what we do and don't want.
Agree with Aaron-- we need to provide more specific suggestions. I have some suggestions below....
Scheduled conduit run lengths are doubled when using the parallel conduit feature as well as the offset feature. Currently the parallel conduits feature is being treated like a parallel feeder and not an independent conduit run.
Provide a Boolean toggle in the electrical settings to treat each run as a separate length.
Project parameters assigned to conduit/conduit runs/conduit fittings currently do not carry over values.
Allow conduit system families to carry over project parameter values. This will allow scheduling to be much more manageable for the end user.
Project parameters assigned to conduit runs cannot be scheduled.
I am sure most everyone uses the comments parameter because this is the only parameter that will carry over values from a conduit run and is the only parameter that will read correctly on a conduit run schedule. Currently project parameters cannot be used in a conduit run schedule without the assistance of Dynamo. My suggestion is to allow project parameters to be treated identically from a programmatic standpoint as the comments parameter.
I have more ideas/bug fixes but in my experience these seem to be the biggest pain point for everyone drawing conduit in Revit. Any other ideas on this topic?
@kadmonkee - pipe doesn't have a concept of a 'run'... a conduit run is a contiguous series of straight segments and bends, intended to resemble a bent (albeit, potentially quite long) piece of conduit. A run stops at junction boxes and the like. What sorts of information are you looking to carry over along a length of conduit?
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.
@aaron.jonesSAP83 - is your goal to get a schedule of all conduit segments per system (life safety, critical, etc..).. and to visually see each system colored differently in your views?
I think I understand that your other goal is to ensure that you have no more than 270 or 360 degrees of bends between pull points... and you're thinking if you scheduled each run, you could easily identify runs that are above that value.
@Martin__Schmid - that is exactly what I'm looking for. However, I'm an engineer, and when we do conduit modelling, it's very high-level. There might be a lot more information a contractor working in a Revit model might look for. These are just the things I'd like to see.
Is this still in the works? Revit 2025 is out and I haven't seen anything new pertaining to these issues. From what I've gathered the only solution is to use Dynamo or something similar to get around this. Seems like it would be easier to have these capabilities natively in Revit for the end user.