Follow up for my other idea BCI-I-494 (link https://bentleyopencivil.ideas.aha.io/ideas/BCI-I-494).
The feature was implemented, but it still missing some core functions.
What it does now, is add the drop on a design scenario. If the setting is turned on in a analysis run, the 3D geometry/inverts won't respect the wall drop, but it will consider them for the calculos. That results in some pretty strange hydraulic profiles, kind of a bunch of stair steps at each node.
The best workflow for this settings would be for it to be considerated during the placement/construction of the networks, NOT when running the calculate tool.
If it only affects after a calculate run, if it is a design, it will add the wall drops, if it is a analysis, it will not edit the inverts, but consider the wall for hydraulics, resulting in most of the conduit having negative slopes.
| Civil Product Used | OpenSite Designer, OpenRoads Designer, OpenRail Designer |
Please submit this as a service case.
Could you log a Service Case please, including your data and ideally a video, so that our Support analysts can look at your issue. The sump depth setting for a node should be honoured when a conduit is placed, as you note. Thanks.
Hi James,
The way it is now, the conduit wall thickness is only applied to the drop of the node invert in a design scenario and not when placing the element.
So, if we are working on an analysis scenario, the settings for considering the wall thickness for nodes invert becomes obsolete and really just gets in the way, because they are not applied to the model (geometry), but is used in the hydraulic run.
The drop should not come from the calculus, it should affect the geometry construction during placement/modeling and then the updated geometry affects the hydraulic run.
Just like when connecting a conduit with "set invert to stop" as false, the conduit changes the node invert. AT THIS MOMENT, the wall thickness should be applied. Not after running a design scenario.
Could you elaborate on what problem this suggestion is trying to solve?