would you please elaborate more about "Integration with Bentley's OpenRoads, which provides hydraulic analysis and simultaneous 3D modeling of storm and sewer features" Thank you,
↧
Forum Post: RE: V8i SELECTseries 5 release of SewerGEMS, CivilStorm, SewerCAD, and StormCAD
↧
Forum Post: RE: V8i SELECTseries 5 release of SewerGEMS, CivilStorm, SewerCAD, and StormCAD
Subsurface Utility Design and Analysis (SUDA) adds hydraulic capabilities to the functionality provided in SUE technology. SUDA leverages the power of hydraulic design/analysis capability in SewerCAD, CivilStorm, SewerCAD and SewerGEMS wrapped up in a single package and runs in the OpenRoads environment. While the capabilities of all 4 storm water products is included in the same package, the functions available to any specific user depends on which licenses you have active. Here are the features of SUE, which are same for SUDA as well which is releasing soon. You will be able to check for conflicts between any modeled underground utilities, drainage and sanitary networks and even 3D road and bridge design artifacts to help guide your design. Thus in more manual process you would design and model your road/site, existing utilities, proposed utilities and proposed drainage, then check for conflicts on all the above to guide your decision making process for the remainder of the design.
↧
↧
Forum Post: RE: Cyanotoxin Analysis
Thank you for your reply. I will run various models of the system throughout this process. I can keep the progress posted if there is interest. Attacking the source of the bloom is an on-going, high profile issue for Lake Erie and as the season progresses, it will become more critical. Multiple studies are in process and many scientists, regulatory agencies and engineers are working together in an attempt to address the causes and effects of the algae issues. The EPA’s mandate for public water systems to have a contingency operations plan specific for cyanotoxin may speedup the process. paula
↧
Forum Post: RE: Cyanotoxin Analysis
Thanks, Paula. We'd be interested in hearing how you addressed this issue. The best way to attack the problem is through the source or treatment. Once these chemicals get into the distribution system, there is not much you can do. It's easy for regulators to require a contingency plan but hard to come up with one. If the algae bloom is short lived, then you may be able to do some flushing to remove the plume if you can identify roughly where it is.
↧
Forum Post: RE: CivilStorm SS4 error: One or more EPA-SWMM catchment failed to compute.
hi Mark, I will reply on behalf of the user who is having communities login problem... Dear Mark, My name is Pawel and in fact the problem originates from my project and was only submitted by Rafał. I still have the problem with activation of my account at the Bentley support. Anyway, many thanks for your comments. The only problem is that they do not solve my issue. I have a problem not only with this trivial system. I have much bigger system with about 500 conduits and 500 catchments. First of all the it is not dependent on the size of catchment. Please feel free to increase the size of catchment 100 times. Error message would remain the same. My idea was to show you that a good model – built in CivilStorm Select Series 2 works also in Select Series 4 but only until some additional catchment is added. My observation is that the problem is present when CN-Curve loss method is used. The problem is also very clear when someone stars to develop completely new system form the early beginning at Select Series 4 (it is exactly very sad but it is my current situation – I have defined all manholes, conduits and catchments but I am not able to run simulations). I also tried with different precipitation scenarios – different hyetographs. It does not solve the problem. Please help! Best regards Pawel
↧
↧
Forum Post: RE: Cyanotoxin Analysis
I agree with your comments; however, developing a contingency plan is the easy part – making it effective and actually being able to implement it is the true issue. And much of it will depend on the operations and maintenance of the individual public water systems. When an operator of a water treatment plant catches a sample to test it in the laboratory there is a time period for the testing. The question EPA wants answered is -- how far and how fast does the water reach consumers between the time of a sample draw and detection of limit exceedence is discovered and how can the system be isolated to stop it. One of the key components of the contingency plan is isolation of areas within the distribution system. Now more than ever, valves need to be operational. We have modeled many systems to show operators where valves are closed. This product is a GREAT tool for proving where closed/broken/inoperarable valves are located – our modeling results have always been correct. Lake Erie. The far left edge of the picture is Toledo, the lower area to the right is Cleveland (to give you scale as to how vast the issue is). There are multiple causes of the algae growth and there are multiple opinions about why it is growing – everything from wastewater treatment plant effluent, industry, storm water runoff, lack of controlled discharge/buffer strips from farms, etc. There’s a lot of finger pointing. And there are a lot of regulatory changes being implemented and in process including treatment and testing. These are pictures from last season and what is starting now.
↧
Wiki Page: How can a user fix the WaterGEMS/WaterCAD error message "Network Unbalanced"?
Applies To Product(s): Bentley WaterGEMS, Bentley WaterCAD Version(s): 08.11.xx.xx Environment: N/A Area: Modeling Subarea: Original Author: Scott Kampa, Bentley Technical Support Group Error or Warning Message How can a user fix the WaterGEMS/WaterCAD error message "Network Unbalanced"? Explanation The "Network Unbalanced" user notification means that for a particular time step the program could not converge on a balanced solution within the maximum number of trials. Between calculation iterations, the program checks the relative change in flow, which has a default value is 0.001. If the relative flow change is below the "Accuracy" value designated in the calculation options, the time step is balanced or is said to have converged. If the relative flow change is greater than the Accuracy value, the program will try another iteration. If the program reaches the maximum number of trials without finding a solution, the "Network Unbalanced" user notification is generated. How to Avoid There are some things that a user can try to resolve the issue. First, you can try increasing the number of trials. To do this, go to Analysis > Calculation Options. Under the "Steady State/EPS Solver" section, double-click on the active calculation option to view the properties. Find the property field "Trials" and set this to a higher value, such as 400. In many instances, this is enough to allow the program to find a viable solution. Note that the program will not necessarily run all 400 trials, but will only use the number of trials it takes to come up with a viable solution. If that doesn't work, you can also try to increase the Accuracy field (also in Calculation Options properties) to a higher value, such as 0.01. This will mean that the relative flow change between iterations can be higher, which may allow the program to find a solution. You do not want the accuracy value to be too high though, or it may compromise the results. You can also try changing the Engine Compatibility field. The latest solver is "WaterGEMS 2.00.12". If you are using an older solver, using the latest may help as well. If the issue still occurs, here are some steps to consider when looking for the possible cause of the error message. Check to make sure that your data for all elements is input correctly. Pay close attention to logical controls, valve settings and valve status, empty or full tanks, and near zero flows as these are common causes of the issue. If you have a check valve on the pipe directly downstream of a pump, consider removing the check valve. In WaterGEMS and WaterCAD, a pump will not allow reverse flow. A check valve on the downstream pipe is redundant and can sometimes impact the model calculations. For EPS simulations you might find more clues to solving your problem by opening the .RPC file. This file contains a log of the trials that the program runs through when it is trying to converge on a solution. In order to open this file browse to the folder where your model is saved; that is where the .RPC file will be. You can open this file in a text editor, such as Notepad. With this file open you should look down the trial list until you start to see the trials where there are elements that are constantly changing status (for valves a status change may be going from "active" to "closed" or vice versa and for pumps it could be going from "On" to "Off") over consecutive trials. The elements that have a constantly toggling status could be a clue to where your problem lies. If this happens often for certain elements then your model may be to tightly constrained or controlled and you should attempt to simplify the model where possible. See Also "Network Unbalanced" problems with zero flow/ static conditions (Solution 500000060448)
↧
Forum Post: RE: Cyanotoxin Analysis
Paula, What is the standard fro cyanotoxins? Last I recall, they were just on EPA's Candidate Contaminant List. That picture of the green water looks delicious. ;o) Tom
↧
Forum Post: RE: Cyanotoxin Analysis
The Ohio EPA just released today notification of Early Stakeholder Outreach asking for public comment on the pending rule. The limits listed are actually 0.3 ug/l warning level for preschool age children or under and 1.6 ug/l is a do not drink order… but there is also a repeat in the sampling and a time limit. The rule seems to be somewhat inconsistent with the goal. paula
↧
↧
Wiki Page: Submodel Import/Export
Applies To Product(s): Bentley WaterGEMS, WaterCAD, HAMMER, StormCAD, SewerCAD, SewerGEMS, CIvilStorm, PondPack Version(s): V8 XM and V8 i Environment: N/A Area: N/A Subarea: N/A Original Author: Mark Pachlhofer, Bentley Technical Support Group Overview This technote will show you how to import one model file ("submodel") into another model file ("target"). It is meant to provide clarification and explanation beyond what is given in the Help documentation. Note that this Technote was written for WaterCAD and WaterGEMS but the same concepts apply to HAMMER, StormCAD, SewerCAD, SewerGEMS, CIvilStorm and PondPack (V8i and V8 XM.) Definitions Target Model - The model that is accepting the submodel file. Submodel - The model that is being imported. Network Elements - The elements in your drawing pane that make up your model. These are junctions, pipes, valves, tanks, reservoirs, pumps , hydrants, etc. Rules for Importing Submodels 1. Existing elements in the target model will be matched with incoming elements from the submodel using their labels. 2. Incoming submodel input data will override target model data for any element matched by its label. 3. If a submodel element of the same label does not already exist in the target model, it will be created during the submodel import. Element Types Governed by Submodel Rules The rules for importing submodels govern the following element types: Analysis Menu Scenarios Alternatives Calculation Options Components Menu Controls Pump Definitions Unit Demands Zones Patterns Minor Loss Coefficients Pressure Dependent Demand Funtions GPV Headloss Curves ConstituentsValve Characteristics Time Series Field Data Tools Menu User Data Extensions Hyperlinks Example 1 In this example, the Submodel and Target Model have no elements in common (i.e., scenarios, alternatives, calculation options, and network elements do not match). Town 'A' (The Target Model) In the model illustration below, take notice of the labels for the elements outlined in red: Alternatives e.g., "Year 2000 Active Topology" "Plus Two 18in Pipes," "Diameter times 2") Scenarios (e.g., "Year 2000 Conditions," "Plus Two 18in Pipes") Calculation Options (e.g., "Year 2000 Conditions") Network Elements (e.g., Pipes P-90 and P-60, Junctions J-50 and J-40, Pumps, Reservoirs, Tanks, etc.) Town 'B' (The Submodel) In the model illustration below, take notice of the labels for the items outlined in red: Alternatives (e.g., "Model_B_Active Topology") Scenarios (e.g., "Model_B_Average_Day") Calculation Options (e.g., "Model_B") Network Elements (e.g., Pipes B_Pipe-9 and B_Pipe-11, Junctions B_Junc-7 and B_Junc-6, Pumps, Reservoirs, Tanks, etc.) Result of Importing Submodel into Target Model In the illustration below, the target model network elements are visible on the left, and the imported submodel network elements are outlined in red on the right. Since the target model elements have no label names in common with the submodel elements, all of the submodel elements will be created the target model, according to rule 3 above. None of the data in the target model will be overwritten in this case, since there were no matching labels. Observe how the scenarios, alternatives, calculation options, and element labels for all the submodel items have been brought into the target model (see red outlined areas). For example, for the Active Topology alternatives, all of the submodel's (Town 'B') network elements have come in as inactive for the original "Year 2000 Active Topology." The reason is because the newly imported elements did not previously exist in that alternative, so the default attributes are used. In the case of active topology, the default is inactive. So, the newly imported elements are inactive in the "Year 2000 Active Topology" alternative. In the case of the physical alternative, if the submodel's physical alternatives don't match the target model's, the default physical attributes will be used for the newly imported elements, for the physical alternatives that already existed in the target model. So in this example, since the physical alternative in the submodel ("Model_B_Physical") doesn't exist in the target model, it was brought in as a new alternative. So, the pipes from the submodel in the scenarios that use the "Year 2000 Physical" will have 6" diameters and junctions will have zero elevations and so forth. In order to see the original attributes of the submodel elements, the scenario would need to use the "Model_B_Physical" physical alternative. Example 2 In this example, the submodel and target model have some elements in common (i.e., scenarios, calculation options, and network elements J-100, J-210, and P-250). Town 'A' (The Target Model) In the model illustration below, take notice of the labels for the items outlined in red: Alternatives (e.g., "Year 2000 Active Topology" "Plus Two 18in Pipes," "Diameter times 2") Scenarios (e.g., "Year 2000 Conditions," "Plus Two 18in Pipes") Calculation Options (e.g., "Year 2000 Conditions") Network Elements (eg., Pipe "P-250" and Junctions "J-100" , "J-210") Town 'B' (The Submodel) In the model illustration below, take notice of the labels for the items outlined in red: Alternatives (e.g., "Model_B_Active_Topology") Scenarios (e.g., "Year 2000 Conditions") Calculation Options (e.g., "Year 2000 Conditions") Network Elements (eg., Pipe "P-250" and Junctions "J-100" , "J-210") Result of Importing Submodel into Target Model In this model below we have connected the submodel (right) network to the target model network (left) at junctions J-100, J-210, and pipe P-250 (center). This connection occurs because both models shared some of the same junction and pipe labels as import rule 2 states. The submodel data is therefore going to overwrite the existing target model data in any items governed by the rules that are common to both models (illustrated below). You can see that for both the submodel and target model there is also a common scenario name. If any of the properties for this scenario were different the submodel properties for this scenario would overwrite the properties for the target model. Above we see the target model network has all become inactive except for the junctions and the pipe that are shared by both models. This happens because the submodel data is overwriting the scenario data for the 'Year 2000 Conditions' scenario (import rule 2). In the illustration below, Town 'A' Demands and Pipe Diameter before the import are outlined in red Junction Demands Pipe P-250 Diameter J-100 = 19.60 gpm 6 inches J-210 = 72.60 gpm In the illustration below, Town 'B' demands and pipe diameter before the import are outlined in red Junction Demands Pipe P-250 Diameter J-100 = 72.0 gpm 8 inches J-210 = 40.0 gpm In the illustration below, pipe size and junction demands after the import are outlined in red Junction Demands Pipe P-250 Diameter J-100 = 72.0 gpm 8 inches J-210 = 40.0 gpm Example 3 In this example, the submodel and target model share all of the same network elements but, none of the same scenarios, calculation options, or alternatives. Town 'A' (The Target Model) In the model illustration below, take notice of the labels for the items outlined in red: Scenarios Calculations Options Alternatives Average Day Demand Average Day Conditions Average Day Fire Flow Fire Flow Fire Flow Constituent Analysis Constituent Constituent Alternative - 1 Town 'A'_2 (Submodel) In the model illustration below, take notice of the labels for the items outlined in red: Scenarios Calculation Options Alternatives Peak Conditions Peak Condtiions Peak Peak Times 2 Peak Times 2 Result of Importing Submodel into Target Model In the model below we can see the import of the submodel results in all the network elements remaining the same because all these elements had the same labels. Hypothetically, if any of the properties of the network elements were different in the submodel from the target model the properties of the result would contain the values that were contained in the submodel (import rule 2). The significant change that happens in this model, much like in the first example, is that the scenarios, alternatives, and calculation options from the submodel all get added to the target model without overwriting anything. In the model illustration below, take notice of the labels for the items outlined in red: Scenarios Calculation Options Alternatives Average Day Demand Average Day Conditions Average Day Fire Flow Fire Flow Fire Flow Constituent Analysis Constituent Constituent Alternaitve - 1 Peak Conditions Peak Conditions Peak Peak Times 2 Peak Times 2 Steps for completing a Submodel Export/Import 1) Open the model that you want to export the submodel part from. 2) Select the part (or entire) model that you want to export. This can be done in many ways. Three common ways are by using your mouse to draw a box around certain areas, using your mouse to left click and select one element or multiple elements while holding down the shift key, or by holding down the CTRL key + A , which will select all the elements on screen. The default color for selected elements is red. 3) With the elements selected in the display panel go to File > Export > Submodel. Name and save your model to a location that you will remember. 4) Now open your target model and after it load go to File > Import > Submodel. Note: if you would like to import the entire model and not a subsection of the model, only step 4 is required. Meaning, in the target model, simply go to File > Import > Submodel, then select the .wtg.mdb file associated with the submodel you would like to import. Troubleshooting If you know you imported the model but don't see anything or are missing part of the model on in your display area. Answer: Go to Tools > Options and see if the option on the Global tab for "Display Inactive Topology" is checked. Also notice the color the inactive topology is set to. If all or part of the model you imported is gray Answer: Your model has likely imported correctly but, all or part of it is currently inactive. If you want it to appear as an "active" status element the active scenario you have to use the active topology tool (Tools > Active Topology Selection) or go into the active topology alternative and change the status of the inactive elements. The reason this happens is because the active topology alternative in the submodel did not match the target model. So, the default status of inactive is used. If you do not want to manually change this in the resultant model, you will need to first go back to the target model and change the labels and structure of the active topology alternatives, so that they match between the models. The attributes/data from the submodel were lost Answer: If the properties of the submodel elements appear to use the default values (such as 6" for all diameters, zero elevation, etc), most likely the physical alternative(s) in your submodel did not match the physical alternatives in the target model. You will either need to correct this manually, or go back to the target model and change the labels and structure of the alternatives so they match exactly to the target's What if models have same labels? Answer: If models have same labels such as P-1 in Project A and P-1 in Project B as well, then the tool from the link below can be used to prefix the Labels before importing. Once the import process is done, the prefixed label can be removed too. http://communities.bentley.com/other/old_site_member_blogs/peer_blogs/b/akshayas_blog/archive/2013/07/11/update-labels-of-a-hydraulic-model-using-waterobjects-net.aspx See Also Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs External Links Water and Wastewater Forum Bentley Technical Support KnowledgeBase Bentley LEARN Server
↧
Wiki Page: Setting Up Pressure Dependent Demand [TN]
Applies To Product(s): Bentley WaterCAD, Bentley WaterGEMS, Bentley HAMMER Version(s): V8 XM and V8i Environment: N/A Area: Layout and Data Input Subarea: N/A Original Author: Nancy Mahmoud, Bentley Technical Support Group Overview Pressure Dependent Demands (PDD) allows you to perform a hydraulic simulation in which the nodal demand is treated as a variable of nodal pressure. This TechNote describes how to set up a PDD simulation in WaterCAD, WaterGEMS, and HAMMER, and also provides suggestions for PDD input data. Background Some types of water demands are volume-based, in that the demand is independent of available pressure. Examples of volume-based demand sources are washing machines, dishwashers, and toilets. Other demands are pressure-dependent, meaning water usage decreases with a decrease in pressure. Pressure-based demand examples include showers, sprinklers, and leaks. Typically, water modeling programs assume that all demands are volume-based, and maintain the user-input demand regardless of the calculated available pressure. Although this assumption works well under the normal range of pressure conditions, it loses accuracy if an episode such as a fire or pump outage causes a significant decrease in system pressure. One option for modeling demands that vary based on pressure is to set up model nodes as simple flow emitters. Because the flow emitter approach places no upper limit on the amount of water demanded with increasing pressure, it is most useful for determining water consumption by a free-discharge element such as a sprinkler or broken pipe. However, other pressure-based demand types result in no additional consumption once the pressure is above a certain threshold value, such that use of flow emitters in the model could skew water consumption to be unrealistically high in higher-pressure areas. Another limitation of flow emitters is that they will result in calculation of a negative demand, or inflow, when the pressure is negative. WaterCAD and WaterGEMS V8 XM and V8i have a Pressure Dependent Demands (PDD) feature that allows for more control over demand calculation. In many instances where pressure affects water use, the PDD feature will provide a more realistic result than simply placing flow emitters on nodes. Using PDD, you can: Analyze pressure-dependent demands at a single node, subset of nodes, or all nodes Define the reference pressure at which 100 percent of the specified reference demand can be met Define the threshold pressure beyond which an increase in pressure results in no additional demand increase Combine PDD and volume-based demands at individual nodes Determine the actual supplied demand at a PDD node, as well as the demand shortfall Obtain a result of zero for pressure-dependent demands when the pressure is less than or equal to zero Present the calculated PDD and the associated results in a table and graph Setting Up the PDD Function Go to Components > Pressure Dependent Demand Click the New button to create a new PDD function The Function Type can either be Power Function or Piecewise Linear The Power Function option is used to define the exponential relationship between the nodal pressure and demand. The ratio of actual supplied demand to the reference demand (i.e., percentage of defined nodal demand designated as pressure-dependent) is defined as a power function of the ratio of actual pressure to reference pressure. (Defining of reference pressure and pressure-dependent demand percentage is done in the Alternative, as described in the next section.) Using a power equation for your Pressure Dependent Demands is like you are assuming that each 'demand' in your system acts like an orifice. The orifice equation can be written like this: Q = K*P 0.5 Where Q is flow through the orifice, P is pressure upstream of the orifice, and K is some coefficient (which is a function of orifice area, coefficient of discharge, et c.) You can specify a desired Power Function Exponent. The default value provided is 0.5, which is the exponent used in the orifice equation. By checking the box for "Has Threshold Pressure?" you can define a pressure value that maximizes the computed pressure-dependent demand (i.e., demand remains constant when the pressure exceeds the threshold value). If you do not define a threshold pressure, demand will increase with pressure regardless of how high it is. Since many PDD simulations are focused on the effects of lower pressure conditions, it is often not necessary to define a threshold pressure. See the screenshot below for Power Function: Example: If pressure on J-10 is 40% of the Pressure (Reference) set in the Pressure Dependant Demand Alternative (explained below), then going by the graph above (or by computing 0.40 0.5 ), the demand on that given junction will be 63.2% of what was set initially. In other words, if J-10 had a demand of 100gpm, and the Pressure (Reference) is set to 150psi, then if pressure on J-10 drops to 60psi (which is 40% of the 150psi), the demand will not be 100gpm any more--it will be 63.2 gpm.The Piecewise Function allows you to manually specify the relationship between reference pressure and demand, as shown in the screenshot below: Example: If pressure on J-10 is 65% of the Pressure (Reference) set in the Pressure Dependant Demand Alternative (explained below), then going by the table above, the demand on that given junction will be 80% of what was set initially. In other words, if J-10 had a demand of 200 gpm, and the Pressure (Reference) is set to 150psi, then if pressure on J-10 drops to 130psi (which is 65% of the 200psi), the demand will not be 100 gpm anymore, it will be 80 gpm. If you are using a piecewise linear function make sure the changes aren't too abrupt on the curve, otherwise the solver may have a more difficult time arriving at a solution. If you have too abrupt a change you may get a "network unbalanced" user notification. To resolve this you could try to gradually decrease the demand. Create a Scenario that Assigns a PDD Function to an Alternative This section describes how to create and configure a new Scenario and Alternative to run your PDD analysis. Go to Analysis > Scenarios. Create a new Scenario. Double-click on the scenario you just created. Click on the drop-down menu right next to Pressure Dependant Demand. Click on New. Assign a name to the new alternative or keep the default as Pressure Dependent Demand Alternative - 1 Go to Analysis > Alternatives. Expand the Pressure Dependant Demand alternative and double-click on the one you just created. Select the Global Function you created earlier. See screenshot below: Set the Pressure (Reference), or check the Reference Pressure Equals Threshold? box if you want it to apply. Often, the Reference Pressure will be defined as the typical pressure at a node under typical demand conditions. However, if you are analyzing pressure-dependent demands for multiple nodes with significantly different typical pressures, you will need to override this system Reference Pressure on a node-by-node basis, as described in the next section. You can set a percentage of the demand that can be pressure dependent. For example, in that case that J-10 has a demand of 200 gpm, you can set 20% (40 gpm) that will not be affected regardless of pressure changes on that node, and the rest of the 80% (120 gpm) will comply to the Pressure Dependent Demand function. If that doesn't apply, keep Percent of Demand that is Pressure Dependent to 100% Click on Close. Assigning PDD on Specific Nodes To override the PDD settings locally on specific junctions, go to the Junction/Hydrant Tab on the Pressure Dependent Demand Alternative window. Check the box under "Use Local Pressure Dependent Demand Data?" Then, select the Local Function from the drop-down menu (you can also create a different PDD function that can be used on selected junctions). Check the Reference Pressure Equals Threshold? or set the Pressure (Reference), if it applies. You may want to set the Reference Pressures for your nodes equal to their "typical" pressures, as computed in a separate representative Scenario. One way to do this is to: Go to your "typical" scenario, open a junction table, sort it by ID, click the first cell in the Pressure column, hold the Shift key, and click the last cell in the column. Then, CTRL+C to copy the data to your Windows clipboard. Return to your PDD alternative, go to the Junction tab, and right-click and Global Edit the "Use Local Pressure Dependent Demand Data?" column to set all values to TRUE. Sort the junctions by ID. Click the Pressure (Reference) column heading to select the cells in that column, then CTRL+V to paste pressure values from your clipboard. Spot check the pressures to be sure they pasted correctly. Set up Calculation Options You'll also need to set up the Calculation Option for the new scenario you created. Go to Analysis > Calculation Options. Click on New button. Double click on the newly created calculation option. Set Use Pressure Dependent Demand? to True. For Pressure Dependent Demand Selection you can either choose or a Selection Set (with nodes where the PDD alternative will apply to, with all the rest always using their regular demands) you created from that list. Now, assign this Calculation Option to the PDD scenario, by double-clicking on the scenario, then choose the PDD calculation option under the Calculation Option drop down menu. Now you can run the scenario. Additional Resources: eSeminar by Dr. Tom Walski See Also Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs [[General WaterGEMS V8 FAQ|General WaterGEMS V8 FAQ]] How do pressure dependent demands (PDD) handle a situation where the pressure drops all the way to zero? External Links Bentley Technical Support KnowledgeBase Bentley LEARN Server
↧
Forum Post: Water path
Hi, I am working on a large network (more than 20,000 nodes) with 4 reservoirs. I need to calculate the exact path that the water travels (from one or more reservoirs) to arrive at a specific node. I have calculated the percentage of water coming from different reservoirs to each node (using Trace option) but I also need the exact path. Any solution is appreciated. Thanks Fatemeh
↧
Wiki Page: How do I select all elements upstream or downstream of a certain point?
Applies To Product(s): Bentley StormCAD, SewerCAD, SewerGEMS, CivilStorm, WaterGEMS, WaterCAD, HAMMER Version(s): 08.11.XX.XX Environment: N/A Area: Modeling Subarea: Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem Description How do I select all elements upstream or downstream of a certain point? Steps to Resolve Go to View > Network Navigator Click on the > button Select Network Trace and then choose either downstream of upstream Select the element from which to trace from and click OK Use the Select in Drawing or Highlight buttons at the top of Network Navigator to view the path in the drawing. Note: for WaterCAD, WaterGEMS and HAMMER, if multiple sources (reservoirs or tanks) supply flow to the selected element, the path to both will be selected.
↧
↧
Forum Post: RE: Water path
Hi Fatemeh, Try doing a search for "trace upstream" in the Hydraulics and Hydrology wiki and you should come across this article, which explains how to use the Trace Upstream query in Network Navigator to do this. communities.bentley.com/.../12772.how-do-i-select-all-elements-upstream-or-downstream-of-a-certain-point
↧
Forum Post: RE: V8i SELECTseries 5 release of SewerGEMS, CivilStorm, SewerCAD, and StormCAD
The videos can not be displayed. for example I press on "Video: Clash Detection" I can not see the video or any link.
↧
Forum Post: Darwin Designer considering fire flow?
Hello, I am working on darwin designer for WaterGems V8i (select series 5). i am having a problem how to design the system under fire flow condition? it is required in our project to consider all junction as fire nodes . and when i try to use demand adjustment it gives me over estimated pipe sizes and fails in feasibility check. question 1 : how to consider fire flow for all nodes in darwin designer? question 2 : i have classified the pipes in 3 design groups (Trunk, main collector and branches) would that give me an appropriate design results? should i imply more design groups? question 3 : i have used customer meters demand in some projects as update for select series 5, now i have a problem using darwin designer for those files as it does not consider customer meter as demand in the mode. how to handle this? note: i don't have the access to the latest select series patch update. thanks
↧
Forum Post: RE: V8i SELECTseries 5 release of SewerGEMS, CivilStorm, SewerCAD, and StormCAD
It seems to work for me. Were you logged in when you attempted to view the video? Have you tried an alternate web browser? If this doesn't help, you may want to post on the Road and Site Design Forum: communities.bentley.com/.../f Regarding the Openroads integration bullet point you asked about - to add what what Sushma said, this is being mentioned as part of the storm and sewer product release announcement because SELECTseries 5 is essentially the version of the H&H product technology that will be available as part of the upcoming SELECTseries 4 release of OpenRoads products. This is sometimes referred to as the "SUDA" technology, which is further enhanced by the SUE product that Sushma mentioned. More information will be available after the OpenRoads SELECTseries 4 release.
↧
↧
Forum Post: ArcGIS 10.3 support for Bentley WaterGEMS, HAMMER and SewerGEMS
As seen in a recent announcement , Bentley SewerGEMS V8i SELECTseries 5 (08.11.05.58) has been released, which adds support for Esri ArcGIS 10.3. An update is also now available for Bentley WaterGEMS and HAMMER V8i SELECTseries 5 (08.11.05.61), to add support for ArcGIS 10.3. Please see the below article for some important details: Integrating WaterGEMS, SewerGEMS and HAMMER with ArcGIS 10.3
↧
Wiki Page: Integrating WaterGEMS, SewerGEMS and HAMMER with ArcGIS 10.3
Applies To Product(s): Bentley WaterGEMS, Bentley SewerGEMS, Bentley HAMMER Version(s): 08.11.05.61+ (WaterGEMS & HAMMER) and 08.11.05.58+ (SewerGEMS) Environment: N\A Area: Other Subarea: N\A Original Author: Terry Foster, Bentley Technical Support Group How can I integrate WaterGEMS, SewerGEMS or HAMMER with ArcGIS 10.3? The Process for Integrating ArcGIS 10.3 with SewerGEMS and WaterGEMS WaterGEMS and HAMMER ArcGIS 10.3 support has been added to WaterGEMS and HAMMER version 08.11.05.61 in May of 2015, by way of a patch. This addition is included in the latest cumulative patch set for this version, which can be downloaded from our website. See the below articles for assistance with downloading. If the latest patch is not yet available on the download site, please contact technical support. See additional steps further below for how to integrate after applying the patch. How do I download the water and storm sewer products? Cumulative patch set frequently asked questions SewerGEMS Officially tested and certified ArcGIS 10.3 support has been added as of SELECTseries 5, build 08.11.05.58. See below article for how SELECT subscribers can download the latest version. See additional steps further below for how to integrate after applying the patch. How do I download the water and storm sewer products? Additional Steps Required to Integrate As of May, 2015, a patch to ArcMap 10.3 and 10.3.1 is required from Esri in order for WaterGEMS, SewerGEMS and HAMMER integration to work properly. This patch addresses an issue on the ArcGIS side. It is possible that future versions or updates to ArcGIS 10.3 will include this fix. In the meantime, please use the below steps. Follow these instructions once you have installed SewerGEMS 08.11.05.58 (or greater) or WaterGEMS 08.11.05.61 (with the latest cumulative patch installed) or HAMMER 08.11.05.61 (with the latest cumulative patch installed). 1. Visit the following link: http://support.esri.com/en/knowledgebase/techarticles/detail/43712 Under "Solution or Workaround" (You have to scroll down a little to see this.) download the ESRIRegAsm.exe.config.zip file. Unzip and copy it to C:\Program Files (x86)\Common Files\ArcGIS\bin on a 64-bit Windows OS Copy to C:\Program Files\Common\Files\ArcGIS\bin on a 32-bit Windows OS. 2. Run Haestad.Integrator from Start > All Programs > Bentley > WaterGEMS, Start > All Programs > Bentley > SewerGEMS or Start > All Programs > Bentley > HAMMER. Please contact Esri for assistance with the ArcGIS patch or for information on when this fix will be included in a product update.
↧
Forum Post: RE: SewerCAD User Data Extensions
Hello MO, I have file an enhancement to see if it will be possible to add something like this to a future version of the program. The reference number for this is 220396. If this is implemented, it will be in a future release of the product. For now, one of the other methods above are available. You could also export or copy data to Excel and import or paste the data back into a User Data Extension. Regards, Scott
↧