Hello AHQ, Do you have gutter elements in your network along with the conduits? Could you please share screenshot of the network path along which you are not able to create profile, with right click > create profile? I tested it for manholes-conduits-catch basins-gutters-outfall, it will not create profile for gutters.
↧
Forum Post: RE: Error creating profile due to a "gutter being part of the path" problem - SewerCAD CONNECT
↧
Forum Post: RE: Error creating profile due to a "gutter being part of the path" problem - SewerCAD CONNECT
Hi, No I don't have gutters. It is a wastewater collection network and it has only conduits, manholes and outfalls (tie ins to other networks modelled as such). Even gutters are gray in the elements symbology table of contents. Please see below. Regards
↧
↧
Forum Post: RE: WaterGEMS and SewerGEMS
Augustine, please send your email address to me at tom.walski@bentley.com and I will send you some material.
↧
Forum Post: RE: Deadpoint
Mal than: 1. The source can not be increased pressure, it is from an existing network and not from a treatment plant .... 2. it was thought to locate a booster but it does not help much and it gets worse upstream ... 3. the diameter increase is considered but it does not help much .... Regards, Leonidas
↧
Forum Post: RE: Deadpoint
What exactly is the hydraulic grade at the source and what is the hydraulic grade at the low pressure area? What are the velocities between the two points?
↧
↧
Forum Post: RE: Deadpoint
there are 2 flow inputs in the northern part 55m of HG and in the south 27m of HG .... reaching the 8m point of HG (Hydraulic Grade) ... no high points are all between the 2 or 3 m.a.s.l. the velocities on one side are at 0.3 and the other 0.5 as the figure shows ..
↧
Forum Post: RE: Deadpoint
For the HG to drop fro 55 m to 8 m, it takes a very high head loss or a very long distance. I'm thinking that ther is a bottleneck in your system that is wasting a lot of energy. Use the profile tool to find that location. Also, feeding a zone with two sources with such different HG value (55 and 27 m) can mean that water is rushing fromteh north source to the south source. check that.
↧
Blog Post: CONNECT Edition Update 1 release of SewerGEMS, CivilStorm, SewerCAD, and StormCAD
We are pleased to announce the availability of CONNECT Edition Update 1 of SewerGEMS, CivilStorm, SewerCAD, and StormCAD: SewerGEMS CONNECT Edition Update 1 (10.01.00.70) CivilStorm CONNECT Edition Update 1 (10.01.00.70) SewerCAD CONNECT Edition Update 1 (10.01.00.70) StormCAD CONNECT Edition Update 1 (10.01.00.70) This Update 1 release is available at no cost for SELECT and ELS subscribers and includes many enhancements and new features to help you be more successful with your storm and sewer hydraulic modeling projects. Below are just a few of the highlights. A more comprehensive list of "What's new" will be available soon. ModelBuilder Snapshots Improves model maintenance and synchronization with a GIS by tracking changes to the GIS/source files during ModelBuilder updates. Other ModelBuilder Enhancements GIS-ID Control Center: provides an easier way to manage model element GIS-IDs. Selection sets for Sync-in and Sync-out: provides a way to update only certain elements. Command line operation: enables batch-importing for more efficient model building workflows. Bing Maps background layer Provides a quick and easy way to add and align aerial imagery and street maps. Engineering Standards Enables you to set up standards on physical properties and quickly check for compliance. Critical Storm Analysis (SewerGEMS, SewerCAD, CivilStorm) Enables you to quickly view and analyze which storm events were the worst-case (the "critical" storm) for each manhole and catch basin. Tracking of storm data source Makes it easier for you to understand the source of your storm events (which engineering library entry.) Events in Long-term Simulations (SewerGEMS, CivilStorm) Improves performance of long-term simulation models by skipping dry states between storm events. Branch Labeling (SewerGEMS, StormCAD, CivilStorm) Enables you to easily adhere to standards that label pipes and nodes based on network branches. Display TIN triangles in Terrain Models Enables you to better visualize terrain models, to help with catchment delineation and other tasks. Tree view for choosing active scenario Makes it more clear and easy to select the appropriate scenario from the dropdown. Save to Package Makes it easier to zip and send all related files for a model to someone else. More ! Subscribe to our Blog for an update when a “What’s new?” article is posted. This release also integrates with MicroStation V8i SELECTseries 4 and AutoCAD 2017 and 2018 (32 bit/64 bit). For SewerGEMS, ArcGIS integration supports up to version 10.5. For more information on downloading this release, please see the following article: Downloading Haestad / Hydraulics and Hydrology Software To discuss any questions or feedback you have on this release, please post on our forum: Haestad | Hydraulics and Hydrology Forum
↧
Forum Post: CONNECT Edition Update 1 release of SewerGEMS, CivilStorm, SewerCAD, and StormCAD
We are pleased to announce the availability of CONNECT Edition Update 1 of SewerGEMS, CivilStorm, SewerCAD, and StormCAD: SewerGEMS CONNECT Edition Update 1 (10.01.00.70) CivilStorm CONNECT Edition Update 1 (10.01.00.70) SewerCAD CONNECT Edition Update 1 (10.01.00.70) StormCAD CONNECT Edition Update 1 (10.01.00.70) This Update 1 release is available at no cost for SELECT and ELS subscribers and includes many enhancements and new features to help you be more successful with your storm and sewer hydraulic modeling projects. Below are just a few of the highlights. A more comprehensive list of "What's new" will be available soon. ModelBuilder Snapshots Improves model maintenance and synchronization with a GIS by tracking changes to the GIS/source files during ModelBuilder updates. Other ModelBuilder Enhancements GIS-ID Control Center: provides an easier way to manage model element GIS-IDs. Selection sets for Sync-in and Sync-out: provides a way to update only certain elements. Command line operation: enables batch-importing for more efficient model building workflows. Bing Maps background layer Provides a quick and easy way to add and align aerial imagery and street maps. Engineering Standards Enables you to set up standards on physical properties and quickly check for compliance. Critical Storm Analysis (SewerGEMS, SewerCAD, CivilStorm) Enables you to quickly view and analyze which storm events were the worst-case (the "critical" storm) for each manhole and catch basin. Tracking of storm data source Makes it easier for you to understand the source of your storm events (which engineering library entry.) Events in Long-term Simulations (SewerGEMS, CivilStorm) Improves performance of long-term simulation models by skipping dry states between storm events. Branch Labeling (SewerGEMS, StormCAD, CivilStorm) Enables you to easily adhere to standards that label pipes and nodes based on network branches. Display TIN triangles in Terrain Models Enables you to better visualize terrain models, to help with catchment delineation and other tasks. Tree view for choosing active scenario Makes it more clear and easy to select the appropriate scenario from the dropdown. Save to Package Makes it easier to zip and send all related files for a model to someone else. More ! Subscribe to our Blog for an update when a “What’s new?” article is posted. This release also integrates with MicroStation V8i SELECTseries 4 and AutoCAD 2017 and 2018 (32 bit/64 bit). For SewerGEMS, ArcGIS integration supports up to version 10.5. For more information on downloading this release, please see the following article: Downloading Haestad / Hydraulics and Hydrology Software Please use this forum to discuss any questions or feedback you have about this release. Happy modeling! Regards, Bentley Technical Support
↧
↧
Forum Post: RE: Creating Thiessen polygons for inlets in StmCAD or CS model
Yes, Catchment Delineation was added in the CONNECT Edition release. You can read all the details in the wiki article that Scott linked to in his previous reply, including two YouTube video demonstrations (see links at bottom of article).
↧
Forum Post: RE: Automatic creation of branch lines to orphaned nodes
Dear Jesse, Thank you for the explaination about the possiblility using Customer Elements instead of Junctions. I have rebuild part of my overall model for test purpose by deleting all small pipes connected to the previous "consumer" junctions and replaced these Junctions with Customer Elements. Afterward I ran the LoadBuilder "Customer Meter Load Data" to assign the Customer Elements to nearest Pipes. This all worked out fine. Now, as described above, my demand data is provided in a GIS shapefile, consisting of sector demands (polygones with associated demand in yearly increasing 2017-2036) overlapping my network. I didn't find an option in the LoadBuilder to allocate the demands to the "Customer Elements" as I previously did with Junctions using "Propotional Distribution by Area".
↧
Forum Post: RE: Automatic creation of branch lines to orphaned nodes
Hello Florian, The distribution of demands using your polygon would be done separately. In my first proposed workaround steps, I assumed that the demand allocation (to junctions) was already completed (based on a LoadBuilder run with your polygon shapefile), and those demands would be retained in step d of the process (copy/paste from the demand control center to a spreadsheet). Step g involved importing those demands back in, to the customer elements.
↧
Wiki Page: What is the purpose of the left and right overbank in the conduit properties?
Product(s): CivilStorm, SewerGEMS, StormCAD Version(s): 08.09.26.17 and later Area: Layout and Data Input Problem What is the purpose of the left and right overbank in the conduit properties, when using the "Bank Channel" roughness type of an irregular channel? What is the purpose of "left bank station"/"left overbank Manning's n", "right bank Station"/"right overbank Manning's n" and "channel manning's n"? Solution When selecting "Bank channel" as the roughness type of an irregular channel, the user must define the roughness coefficient for the left bank of the channel, right bank of the channel and central part of the channel. The "Left bank station" is the station point that marks the end of the left bank. The left bank is measured from the first station-depth point in the irregular channel section table to the selected point. The "left overbank Manning's n" is the roughness coefficient for the left river bank (the part of the channel to the left of the "left bank station".) The "right bank station" is the station point that marks the beginning of the right bank. The right bank is measured from the selected point to the last station-depth point in the irregular channel section table. The "right overbank Manning's n" is the roughness coefficient for the right river bank (the part of the channel to the right of the "right bank station".) The "channel Manning's n" is the roughness coefficient for the middle part of the channel, between the left and right bank stations. Basically if the water surface is below the banks, the "channel Manning's n" applies but if the flow rises to a point where some of it goes over the banks on the sides of the river, part of the flow is subjected to a different roughness, based on the coefficients entered. You would also choose the Channel Weighting Method (default is Pavlovski) which is used to determine the overall Mannings n as water flows beyond the banks. See Also Original Author: Jesse Dringoli
↧
↧
Forum Post: RE: Automatic creation of branch lines to orphaned nodes
Hi Jesse, Thanks for the immediate supply. Demand allocation is completed, in my case for 5 time steps between 2017 and 2036. However, in case the demand forecast is changed in GIS (which happens by the client), with my approach by using junction I only have to re-do the demand allocation and then batch run all scenarios. Also if I want to include an additional time step inbetween, I am quite fast. To do your workaround to allocate the demands to the Customer Elements for each time step / scenario I guess is more time consuming. Also by importing demands back in to the customer elements using Excel, I always get the Error message " Microsoft Acess Database Engine 2010 (64 bit) is required". I had the same problems during modelbuilding before and Access Database Engine is installed on my computer. To open the file in 32-bit gives me another alert. All in all, is it worth all the effort or should I stick with demand junctions for my application?
↧
Wiki Page: Defining conduit or channel roughness varying with depth or flow
Applies To Product(s): CivilStorm, SewerGEMS, SewerCAD, StormCAD Version(s): 08.11.xx.xx, 10.xx.xx.xx Area: Modeling Original Author: Dan Iannicelli, Bentley Technical Support Group Problem How do you model an open channel where the Manning's n coefficient varies based on the depth or flow? Solution CivilStorm, SewerGEMS, StormCAD and SewerCAD will allow the Manning's n coefficient to vary based on depth or flow for an open channel. The Roughness Type in a Conduit can be set to "Roughness Depth" or "Roughness Flow", where you can vary the Manning's n coefficient based on depth or flow, respectively: If you change the Roughness Type to "Roughness Depth" or "Roughness Flow", you can enter a Depth or Flow versus Mannings's n value curve and the program will adjust the roughness value accordingly based on the rating table. Meaning, as the depth or flow in the channel or conduit changes, the overall roughness coefficient will change accordingly, to reflect the change in material/roughness as the water level changes. The "Roughness-Flow" Roughness Type is useful when describing a conduit or channel whose roughness changes with flow. This could occur for example in a natural channel, in which higher flows reach sections of the channel that have a different roughness (grassy vs. sandy/rocky, etc) and thus the overall effective roughness coefficient changes. If you instead know how the overall Mannings n changes with flow depth, use the "Roughness Depth" Roughness Type instead. When modeling an Irregular Channel, you also have the option to define changes in roughness using the Bank Channel Roughness Type . With this selected, the Irregular Channel section editor allows you to enter the separate Mannings n beyond the bank stations. You would also choose the Channel Weighting Method (default is Pavlovski) which is used to determine the overall Mannings n as water flows beyond the banks. Note: with StormCAD and SewerCAD (or the GVF-Rational or GVF-Convex solvers in SewerGEMS and CivilStorm), currently the Roughness Type field is only available for irregular channels and only the Bank Channel method is available.
↧
Forum Post: RE: Roughness Type
I assume you're referring to SewerGEMS or CivilStorm. The "Roughness-Flow" Roughness Type is useful when describing a conduit or channel whose roughness changes with flow. This could occur for example in a natural channel, in which higher flows reach sections of the channel that have a different roughness (grassy vs. sandy/rocky, etc) and thus the overall effective roughness coefficient changes. If you instead know how the overall Mannings n changes with flow depth, use the "Roughness Depth" Roughness Type instead. When modeling an Irregular Channel, you also have the option to define changes in roughness using the Bank Channel Roughness Type . With this selected, the Irregular Channel section editor allows you to enter the separate Mannings n beyond the bank stations. You would also choose the Channel Weighting Method (default is Pavlovski) which is used to determine the overall Mannings n as water flows beyond the banks. I have updated the following wiki article with these details: Defining conduit or channel roughness varying with depth or flow
↧
Forum Post: RE: Automatic creation of branch lines to orphaned nodes
Hello Florian, Regarding the Access Database Engine error, please see the following article which has multiple solution: ModelBuilder/SCADAConnect error: Microsoft Access Database Engine 2010 64-bit is required to access this data source If you have a need to update the demand allocation using Proportional Distribution by Area, consider my second proposed workaround of changing the customer elements back to junctions. With this, you will have the lateral pipes as you want them (as pipe elements) and the demands will be on junctions, so their demand allocation can be updated using the Proportional Distribution by Area method. The downside to this is that you will have extra pipes in the model, compared to the customer meter approach which uses the special lateral element and tap node to associate with one pipe. If you have a large (or Unlimited) pipe limit in your license, that may not be a problem. There would also be a small performance impact since hydraulics would be calculated through the lateral pipe, but that may be negligible. I will check to see if we have plans to add the other LoadBuilder methods to the "Customer Meter load data" LoadBuilder type.
↧
↧
Forum Post: RE: Deadpoint
si estás en lo correcto !! ... hay mucha distancia hasta este punto y mucha demanda en puntos intermedios ... ¿Qué quieres decir con "puede significar que el agua se precipita desde la fuente norte a la fuente sur" How can I see the profile for this, is it in the juctions or the pipe?...
↧
Forum Post: RE: Deadpoint
If this is a new design, you need to find the pipes with high velocityheadloss and upsize them to reduce head loss. If this is an existing system, then you may need to parallel the pipes with excessive head loss. If the two sources are tanks, then water from the north tank may be flowing to the south tank instead of to customers. Check the direction of flow. If they are pumps, the south pump may be forced to a bad operating point by the north pump. Check the flow contribution form each.
↧
Forum Post: RE: Automatic creation of branch lines to orphaned nodes
Hi Jesse, I have around 90.000 consumer in my network, so regardless of the laterals being no extra pipes I need to use unlimited pipes licence. Telling me that the performance impact is only marginal I will stick with my approach. This brings the advantage to update demand variations with only 2 clicks which is very comfortable. Also the Loadbuilder methods (Area Proportial or Equal) are available. Thank you for the link regardin the Access Database Engine error, I try that. BR Florian
↧