Thanks a lot Yashodhan, It was a great help.

It has been a while (more than 5 months), so are there any updates on what Bentley is planning to do with MOHID Studio. When are we to see Civil Storm Integration. I hope you can sense how much this is awaited by the modeling community.

Dear Bentley Experts I studied your former discussions about a question I have too (as you listed them here: https://communities.bentley.com/products/hydraulics___hydrology/f/haestad-hydraulics-and-hydrology-forum/102437/using-load-builder-proportional-distribution-by-area/305454#305454 ), but the problem was not solved yet and I need your help: The whole informtion I have is: A City Polygons as citypolygons.shp, I have the boundary of the city as BoundaryPolygon.shp. I have another shapefile which is called DensityPolygons.shp in which three density polygons are defined with a Factor for each polygon (factor 0.1 for low density polygon, 1.0 for medium density polygon and 10.0 for high density polygon). meanwhile the total population of the city and total Demand are specified. Which method of loadbuilder's methods is better for this case? Just mention it and I will do it myself.

Product(s): WaterGEMS, WaterCAD, HAMMER Version(s): 10.01.01.04 Area: Other Problem When using the "Update database cache" tool, the following error occurs: Exception : System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. Inner Exception : Haestad.SQLite.SQLiteException: 11: database disk image is malformed Or The following error is generated after compacting database and opening the model: “11: database disk image is malformed” Background This error or exception can occur when the database is corrupted in some way. When updating or compacting a database, the step "Purging elements marked as deleted…" is skipped. This step is skipped when compacting the database while the model is opened and when compacting with the model closed and selecting "Purge records to save space". The deleted elements do not get purged from the database which can sometimes result in this problem. Solution To resolve this notification the following options can be adopted; Option 1: Restoring the model from backup The first step would be to try to restore the model from the backup file. For example, if this crash or error occurred while working on WaterGEMS, then try to locate the .WTG.SQLITE. BAK and .WTG. BAK files to restore the model from. The steps to recover models from backup files can be found here . If the model is successfully restored, check if you get the error or crash by going to File > Database Utilities > Update Database Cache. If the error or crash persists, then please contact Technical Support for resolution. Option 2: Export sub-model and import it into new workspace With this option you can simply export the entire model as a sub-model and importing it in a new workspace. 1. Select all elements in the model (Home > Drawing > Select > Select All) or manually select all elements. 2. Go to File > Export > Submodels 3. Save the .sqlite file in a separate location. Close the model. 4. Go to File > Import > Database. Browse to the location of the newly saved database file (.sqlite) and open it. 5. The exception will no longer occur. Note: With this option there might be some minor loss of data though (things not exported to the submodel). It is better to save a backup of the model for future reference. If the above options do not work, please contact Technical Support to repair your database. Repairing the database involves checking the integrity of the database (.SQLITE file) and re-indexing which should fix this problem. If you are comfortable with doing so, you can try repairing the database yourself. Be sure to make a backup of the model’s .SQLITE file first. This is the model’s database file and is in the same folder where the model is stored, with the same base file name. Using an application that can open SQLITE files, try re-indexing all tables in the SQLITE file. As an example, the application called SQLITE Expert has an option to check the integrity of the database and an option to re-index. See Also Can I restore a backup file of my model project or software component?

Product(s): SewerGEMS, SewerCAD, StormCAD, CivilStorm Version(s): 10.XX.XX.XX, 08.11.XX.XX Area: Modeling Problem When validating a model where a property connection element is connected to a diversion link the following user notification occurs; “ Tap node cannot reference a diversion link ” Background This “red” user notification is generated when a property connection is connected to a conduit which is set as a diversion link via a tap node. The message would look like this; A diversion link is used to define a flow split. The flow through the diversion link is based on the rating table of upstream flow vs. diverted flow. When a property connection is applied to a diversion link (via tap and lateral) there is conflict which occurs due to the multiple flow conditions applied on the diversion link. A property connection would have sanitary loads to generate the flow to be assigned to a conduit which will determine the flow within the conduit. However, when this conduit is defined as diversion link, the flow within it is governed by the diversion rating curve. As both these flow conditions are assigned to a same conduit (modeled as a diversion link) the user notification is generated to warn the user that calculation cannot be performed for this link. Also, since the conduit is defined as a diversion link the diversion rating curve will govern the flow. Solution To resolve this notification the following options can be adopted; Option 1: Assign the Property Connection to the upstream node This can be done by manually deleting the tap and lateral for the property connection and assigning the property connection to the upstream node. You can also right click on the end of the lateral link, choose "reconnect", and attach it to the manhole. Option 2: Assign a transition With this option you can simply divide the conduit by a transition element. After doing this, check the new downstream conduit and ensure that “False” is selected for the “Is Diversion Link?” property. See Also Modeling storm/sewer Property Connections Modeling a flow split (diversion) with the SewerCAD or StormCAD numerical solver

Product(s): WaterGEMS, WaterCAD, HAMMER Version(s): CONNECT Edition, V8i Area: Modeling Problem How can I model variable speed pumps (VSP’s) in parallel? How do parallel VSPs work? Background VSP’s in parallel work on the principle of “lead” and “lag”. For a certain number of VSP’s in parallel, there will be one pump which functions as the “lead” VSP which first turns on to attempt to meet the target pressure or flow. If the lead VSP cannot satisfy the target head or flow, despite running on the user entered maximum relative speed (which defaults to 1.0 meaning full speed), then the next VSP will be triggered to assist the “lead” VSP. This second pump is known as a “lag” VSP. The VSP calculation determines the common speed for both VSP’s. When both the VSP’s cannot deliver the target head within the maximum relative speed factor, the third VSP (if present) is triggered to turn on. This will continue for all the VSP’s in parallel until the target is satisfied. It is not necessary that all the VSP’s will be triggered. If the target head is satisfied then only the required number of VSP’s will run. In case all the VSP’s are running at maximum speed and still not able to deliver the target head, then they are considered as fixed speed pumps. This is referred to as “fixed speed override”. The above logic occurs automatically when multiple VSPs are detected as being in parallel, with the same pump definition and target. Solution The following demonstrates how to model variable speed pumps (VSP’s) in parallel. VSP’s can be modeled in parallel like ordinary pumps. In the pump properties there is a field “Is Variable Speed Pump?”. By setting this field to “True” the pump would be treated as a variable speed type. Once the status is changed to “True” some additional properties appear. Here, the type of VSP should be specified in the “VSP Type” field. There are three types of VSP’s Target Head – The most commonly used VSP type. Specify the target pressure/hydraulic grade to be maintained at a junction downstream of the parallel VSP’s. If a tank is specified, it will attempt to maintain a constant hydraulic grade in the tank. Fixed Flow – Specify the desired fixed flow from the pump Pattern Based – Specify a specific pattern of speed over time. Enter relative speed factors/multipliers over time (typically not greater than 1 since the speed of the motor typically cannot exceed maximum speed.) This would be the typical setup of parallel VSP’s; Notice that the start and the end node are the same for all VSP’s. This is important as the software recognizes this configuration as parallel VSP’s. Note: Sometimes there are multiple junctions between the individual VSP’s and the common node for all VSP’s. A user notification is generated when such parallel VSP’s are run; “Variable speed pumps not in parallel”. I n such a case a common node must be defined so that all VSP’s are identified in parallel. The following article explains how to resolve such an error. How do I model parallel fixed head (target head) variable speed pumps that are controlled by flow in a downstream pipe? Once the pumps are setup in parallel, each pump needs to be defined as a variable speed type pump with a target head. It should be noted that, the pump definition (pump curve), maximum relative speed factor, target head/flow and target node for all the VSP’s in parallel should be the same, otherwise they would not function as parallel VSP’s. Criteria for parallel VSP’s Parallel VSP’s must be controlled by the same target node Parallel VSP’s must be controlled by the same target head Parallel VSP’s must have the same maximum relative speed factors Parallel VSP’s must be identical, namely the same pump curve Parallel VSP’s must share common upstream and downstream junctions within 3 nodes (inclusive) of the pumps for them to be recognized as parallel VSP’s. All upstream pipes should have the same diameter, roughness, length and minor loss coefficient, the same for all downstream pipes within the parallel VSP group. As opposed to the first five criteria a difference in these attribute values will not stop the calculation run. Only a warning user notification is generated for each attribute with at least one deviation. Note that the results within the suction and the discharge junction of the parallel VSP group will not be completely correct in this case. When configuring the VSP’s in parallel you have the option to assign them to a Pump Station like any other pump setup. However, you can use the variable speed pump battery element (VSPB) to model VSP’s in parallel. The benefits of using this are outlined here . Fixed Flow VSP's A fixed flow VSP can be defined in the VSP type field of pump properties. The Relative Speed Factor is typically kept as 1 because the pump typically cannot operate beyond its maximum speed. However, it can be changed as per operating conditions. The “Flow (Target)” field takes the input of the fixed flow at which the VSP is desired to operate. The relative speed is then adjusted to meet the fixed flow specified. However, the lead and lag principle of operation of parallel VSP’s will not function with Fixed Flow VSP’s or Variable Speed Pump Battery (VSPB) because each VSP will try to maintain its own “Fixed Flow”. More information about this can be found here . See Also Help Section of WaterGEMS. Modeling Variable Speed Pumps > Parallel VSP’s Modeling variable speed pumps in parallel with different pump curves Modeling fixed head parallel VSPs that have different head values Modeling multiple VSPs where only one turns on at a time How do I model parallel fixed head (target head) variable speed pumps that are controlled by flow in a downstream pipe? The headloss in a pipe downstream of a parallel VSP is higher than expected Why is the “lag pump count” field not available when selecting Fixed Flow as the “VSPB Type”?

Product(s): PondPack Version(s): 08.11.xx.xx Area: Other Problem When trying to open PondPack, the following error is generated: "The application was not able to start correctly." Solution The issue may be related to anti-virus or anti-malware software. Try temporarily disabling the software, then opening PondPack. If this helps, adding PondPack as an exception to the anti-virus software should help prevent future problems. If that doesn't help, try opening PondPack from the following location: C:\Program Files (x86)\Bentley\PondPack8\Haestad.PondPack.Starter.exe. This bypasses the splash screen and may help opening the program. Again, using Run as Administrator may help. If this works, create a new shortcut from this file. If this doesn't help, try a "clean reinstallation" of PondPack using a new installation file. A clean reinstallation will help to remove any files that might be left over after uninstalling the program. The following link has the steps on how to do this: How to perform a clean reinstallation of a Hydraulics and Hydrology product . This link includes licensing related steps, but you shouldn't need to do these.

Hello Jesse, Thanks for your response, but I think I coudnt explain correctly my problem, so Im going to explain it again but in spanish. Quiero realizar una modelación transiente de una línea de impulsión cuando tengo una caída de voltaje de la bomba (Shut down After Time Delay). Esta línea tiene su punto inicial a una elevación de 4.100 m, mientras que su punto final se tiene una elevación de 2.600 m, por lo que puede funcionar de manera gravitacional, pero se utilizan estas bombas para evitar presiones bajas en un punto alto a lo largo de la línea. Estas bombas están ubicadas al comienzo de la línea y son alimentadas por un estanque que posee una capacidad de almacenamiento aproximada de 200 m³. Sin embargo, cuando intento agregar las características del estanque me aparece el siguiente error: (Message ID 41510). Por otro lado, si modelo el sistema incorporando un reservorio en vez de un estanque, resulta que si bien la bomba deja de impulsar el flujo, sigue habiendo transporte del fluido por el hecho que el reservorio es una fuente "infinita" de agua y como está ubicada a una mayor cota, su conducción ocurrirá por la diferencia geométrica del sistema. Tras esto tengo las siguientes dudas: 1.- Hay alguna manera de modelar el sistema transiente considerando un reservorio, pero que una vez se corte la bomba deje de escurrir el flujo? 2.- Tengo problemas al dimensionar el Estanque. Busqué en el manual de ayuda del programa sobre cómo definir las dimensiones, pero aún así me arroja el mensaje de error que mostré. Gracias por tu colaboración. Saludos

Applies To Product(s): WaterGEMS, WaterCAD, SewerCAD Version(s): CONNECT Edition, V8i Area: Modeling Original Author: Scott Kampa, Bentley Technical Support Group, Tom Walski, Senior Product Manager Overview The amount of head the pump must add to overcome elevation differences is dependent on system characteristics and topology (and independent of the pump discharge rate), and is referred to as static head or static lift. Friction and minor losses, however, are highly dependent on the rate of discharge through the pump. When these losses are added to the static head for a series of discharge rates, the resulting plot is called a system head curve. In a simple situation, where you have two sources (tanks or reservoirs) and a single pipe, the system head curve can easily be generated with hand calculations. In a more complicated situation, where there are multiple sources, multiple pumps, demands, looping pipes, branching networks, etc., doing a manual calculation for the system head curve can be difficult, and provide only a rough estimate of the system head curve. A program like WaterGEMS or WaterCAD makes solving these much easier. A system head curve depends on tank water levels, the operation of other pump stations in the system, the physical characteristics of the pipes (roughness, minor losses, etc.), and system demands. Because of this, the system head curve will reflect the system conditions at the time of the run. As the demands and tanks levels change or as other pump statuses change, the system head curve will change too. For that reason, there is a band of multiple system head curves over the course of a model run time. What is the Definition of a System Head Curve? Defining "System Head Curve" in such a way that it applies to all situations including complex networks can be challenging. Here is one possible definition: "A system head curves is defined as a curve (function) relating the head that must be provided at the pump to the flow rate at that pump location. The points on the system head curve are a property of the system and are independent of the specific pump used." Here is another one that describes what the products do: "Actual head required at a pump is determined by the difference in head between the suction and discharge sides of the pump in the model with the pump represented by an outflow from the suction side and an inflow into the discharge side. The relationship between the head difference and the pump discharge is called the system head curve." System Head Curves When generating the system head curve, WaterGEMS, WaterCAD, SewerCAD basically replaces the pump with two nodes: a suction node and a discharge node. Note that there must be a source, either a tank or a reservoir, on either side of the pump. It is from the elevations in these sources that the head before and after the pump is determined. The suction node acts like a demand while the discharge node acts like an inflow, or negative demand. The system head curve uses a range of flows. These flows are the demand and inflow values. For a given flow, the difference in head is determined on either side of the pump. As the flows change, the head will change as well. The range of flow should be reasonable for the conditions expected in the system. Once the system head curve is available, an appropriate pump can be found that will deliver the needed head at the desired flows. In the CONNECT Edition releases of the products, Analysis > Analyis Tools > More > System Head Curves, or by right-clicking on a pump in the model and choose System Head Curve. In the V8i releases, you can open the system head curve dialog by going to the Analysis pulldown menu and choose System Head Curve, or by right-clicking on a pump in the model and choosing System Head Curve. In the upper left, you would select the pump for the system head curve, as well as a maximum flow and number of intervals. The maximum flow will be automatically filled in based on the pump definition that you have assigned to the pump, but you can change this to another value if you want. The number of intervals is how the flow range will be split. The system head curve is generated by finding the difference in head for different flows. If you have a maximum flow of 3000 gpm and an interval of 10, the program will start with a zero flow case and find the head across the pump. It will then set the flow at 300 gpm and find the head across the pump. Then it will find the head across the pump for a flow of 600 gpm, and so on. The end result will be similar to the screenshot below. The blue line is the system head curve; the red line represents the pump definition. If you click on the Data tab, you will see the numerical results. The columns in the screenshot above called “0.000 hours Flow” and “0.000 hours Head” are the data from which the system head curve is generated. When the flow is 0.00 gpm, the difference in head between the suction side and the discharge system of the pump is 16.4 feet. When the flow is 1500 gpm, the difference in head is 147.4 feet. (Note: The model this system head curve is based on in Example1.wtg, which can be found at C:\Program Files (x86)\Bentley\WaterGEMS\Samples\Example1.wtg.) As mentioned above, the system head curve is based on the elevation of the sources on either side of the pump, as well as the physical characteristics of the system, demands, and the status of other pumps in the model. Because of this, the system demands and the headlosses in the pipes are important for determining the head on either side of the pump. Since the system head curve can depend on the conditions at a given time, demand patterns and a change in level in a tank will be important to the system head curve. Because of that, it is often a good idea to look at other time steps as well. The screenshot below shows the system head curves for the system at 0 hours and at 20 hours. Between the start of the simulation and hour 20, the tank on the discharge side has been filling and thus has a higher elevation than at the start of the model run. Because of this, the head on the discharge side is higher, resulting in a higher system head curve. The point where the system head curve and the pump definition intersect is the operating point of the pump. As conditions in the system change, the pump operation is expected to change as well. The green line in the screenshot above is the pump definition. The blue line is the system head curve at hour 0 and the red line is the system head curve at hour 20. As you can see, the pump will need to generate more head at hour 20 since the elevation in the tank is higher at that time. Based on the pump definition, this means the flow will be slightly less than what you would see at hour 0, when the elevation in the tank is smaller. System Head Curves in Closed Systems Normally a system head curve is determined based on a system where there is a source of flow on either side of the pump. However, there may be cases where you want to find a system head curve for a closed system or a system with no downstream source. If you tried to compute a system head curve with no downstream source, you may end up with a curve that looks similar to the one below: The system head curve option is invalid for this condition. The scale exaggeration throws off the graph--really what we are seeing plotted is a near-vertical line for the system head curve. This is displayed as a large change in head for a small change in flow. Only the single point at which the pump is operating (the point where the system head curve and the pump curve intersect) is valid since the flow from the pump can only be the demanded flow on the discharge side. However, it is possible to find a valid system head curve in a closed system if you use pressure dependent demands . With pressure dependent demands, the demands can change based on the pressure at a node. This provides WaterGEMS and WaterCAD with the information necessary to create an accurate system head curve. Note: when using PDD with system head curves and no downstream storage, it is important that the PDD function be configured to have no threshold limit. This way, with increasing pressure the PDD demand can be increased above the base demand of the corresponding scenario to calculate the system head curve for flows larger than the total demand of all demand nodes in the closed network. For more details on this situation, see the link "System head curves with no downstream storage" under the "See Also" section at the bottom of this article. Note : If the tank on the upstream or downstream end of the pump is empty, you will see results like this as well. If a tank is empty, the results will not be valid. Impact of other pumps and multiple downstream tanks The system head curve will be dependent on the status of other pumps in the system. If you look at the graph, the y-intercept is only equal to 'static head' in the simple case where there is one pump in the system. However, if you have more than one pump the results are slightly different. Take an example where you have two pumps in parallel, PMP-1 and PMP-2. When looking at the system head curve for PMP-1, the value where Q=0 is the minimum head that a pump must provide before it can deliver any water into the pipeline. This is dependent on what the second pump in your system is doing. When PMP-1 and PMP-2 are both off (and assuming there are no demands in the system), the hydraulic grade (HG) elevation at the common downstream node is the level of water in the downstream reservoir. The minimum head that pump PMP-1 must provide before it can deliver any water is the difference between the HG on the discharge side of the pump and the suction side of the pump. That is what we know as “static head.” Now, if PMP-2 is turned on and PMP-1 is still off, the HG elevation at the common downstream node, would be something higher than when both pumps are off, since PMP-2 is now adding head. The minimum head that PMP-1 must provide before it can deliver any water is the difference between the HG on the discharge side and the HG on the suction side. This explains the head value on the system head curve when flow is zero. You could say that pump PMP-1 must overcome the static head plus the dynamic head of PMP-2 before it can deliver any water. If you are designing PMP-1, you must pick a pump that works well when PMP-2 is either on or off, so you need to look as system head curves for both cases. Note that if you have the latest version of WaterCAD or WaterGEMS, you can use the Combination Pump Curve tool, which always shows the system head curve with all others pumps turned off. If you have a case where there are multiple tanks downstream of the pump, this can be difficult to calculate by hand as well, since the hydraulic grade at the tanks may be different values. However the system head curve in WaterGEMS and WaterCAD will be looking at the cumulative impact of the tanks when looking at the head across the pump and the hydraulic grade on the discharge side. Non-parabolic system head curves As you can see from the screenshots above, system head curves are often parabolic, with the flow increasing with an increase in the head across the pump. However, there can be cases where the curve is not parabolic. The most common reason for a system head curve that is not parabolic is water consumption between the pump and the downstream tank. When this consumption occurs, it lowers the system head at low flow. In fact, if the consumption between the pump and tank is greater than the pump output (such that flow goes from the tank toward the pump), then there is an inflection point in the pump curve. If you want to check this out manually, put a single large demand between the pump and tank. WaterGEMS and WaterCAD will handle this automatically. Manually generating a system head curve With a simple system, it is possible to manually generate a system head curve. Detailed steps on doing this can be found in the Advanced Water Distribution Modeling and Management book available from Bentley’s website. The easiest way to arrive at the system head curve is to remove the proposed pump from the model, leaving the suction and discharge nodes in place. For the curve to be computed properly, a tank or reservoir must be present on each side of the pump. The water that leaves the suction-side pressure zone is identified as a demand on the suction node, while the water that enters the discharge-side pressure zone is identified as an inflow (or negative demand) on the discharge node. The difference in head between the suction and discharge nodes as determined by the model is the head that must be added to move that flow rate through the pump (that is, between the two pressure zones). The flow rate at both the suction and discharge nodes is then changed and the model re-run to generate additional points on the curve, continuing until a full curve has been developed. Please see the following link for additional details and reasons that the system head curve calculated by hand may differ from the system head curve calculated by WaterGEMS, WaterCAD, or SewerCAD: System head curve generated in WaterGEMS, WaterCAD, or SewerCAD looks different from hand calculations . System Head Curves with intermediate high point The system head curve is based on the head values at sources on the upstream and downstream side of the pump. The pumps (and the system head curve) does not take into account intermediate highs points, which in model cases can result in negative pressures at the highs points. An air valve can be used to mitigate these negative pressures. When an air valve is present in the model, the system head curve may use the air valve as part of the calculation. When you start up a pump, the downward sloping part of the pipe at the air valve will generally be empty or part-full. In such a case, you would calculate the system head curve from the suction reservoir to the air valve at the high point. Once the pipe is full, you would calculate the system head curve for the entire pipeline. There are some exceptions to this. In some cases, the downward sloping pipe is so large and steep that it never runs full and the system head curve is always to the high point. In addition, if you don't have an air valve and the hydraulic grade at the high point drops below the vapor pressure of the fluid, the fluid will turn into vapor. This shows the importance of having an air valve at high points that are susceptible to negative pressure. Ideally, you would make the downward pipe so small that it easily flows full or so large that it always flows partly full. This will make the calculation of the system head curve easier over the course of the simulation. Setting Vertical Axis Starting the the CONNECT Edition releases of WaterGEMS, WaterCAD, and SewerCAD, you now have the ability to adjust the vertical axis on the system head curve. This can be useful when the head range is large and make the system head curve more legible or include the most important information. To do use this feature, select the checkbox for "Specify vertical axis limits" and enter minimum and maximum head values. This will adjust the vertical axis to include only a select range of head values. The screenshot below shows a system head curve without limiting the vertical axis: If you wanted to limit the vertical axis to a maximum value of 600 feet of head, select the "Specify vertical axis limits" check box and enter a minimum head 0 feet and a maximum head of 600 feet. Display Legend Starting with WaterGEMS and WaterCAD CONNECT Edition Update 1, you can now more easily display a legend to better understand the curves in the system head curve. Click the small black triangle next to the Chart Options button to choose the option to show the legend. This will allow you to quickly identify the curves in the System Head Curve graph. In older versions, you would need to go into Chart Options to generate the legend. System Head Curves for Variable Speed Pumps Starting with WaterGEMS and WaterCAD CONNECT Edition Update 1, you can now view pump characteristic curves for different pump speeds in the system head curve tool. This provides a more accurate and complete illustration of the operating point as a VSP changes speed during the simulation. If your model includes a variable speed pump, you will see a check box that says “Show Variable Speed Pump Curves?” If you leave this unchecked, pump curves will show the pump characteristic curve at full speed. By checking this box, you will be able to view the system head curves at times that you select, as well as the pump curve at the relative speed factor calculated at that time step. The screenshot above shows system head curves at hours 0, 10, and 24 (which are curving up) and the pump definition (which are curving down) at the calculated relative speed factor at hours 0, 10, and 24. The color coding used for both the pump curve and the system head curve is the same for each time step being displayed. The color coding is set up this way to clarify which system head curve relates to which pump definition. For instance, for the curves at hour 0 (denoted in blue), the pump is operating at a relative speed factor of 0.824, as shown in the legend. The operating point is where the pump curve and the system head curve at hour 0 intersect, which is a flow of 1500 gpm and a head of 155 feet. It is important to note that where the system head curve for hour 0 intersects the pump curve at hours 10 and 24 are essentially meaningless, since the pump doesn’t operate at the same relative speed factor at these times. The gray pump curve that is displayed is the pump curve at full speed, or a relative speed factor of 1.0. If one of the pumps happened to operate at full speed at some point during the calculation, the gray curve would be replaced by the actual pump curve. Where the system head curve intersects with the pump curve at full speed would give the user an idea of the operating point if such a condition were used at that time step. You can add a legend to the system head curve by clicking the Options button and selecting Show Legend. See the section “Show Legend option added to System Head Curve dialog” below for details. See Also There are a number of support solutions that already exist for some of the items described above. You can find those solutions below: System Head Curves with no downstream storage Pump Selection for a Closed System System Head Curve changing depending on the statue of other pumps Pump Stations and Combination Pump Curves How to manually generate a system head curve Estimating a pump curve for WaterGEMS and WaterCAD (pump design) The following papers have information on system head curves as well: Paper: Ormsbee, L. and Walski, T. "Developing System Head Curves for Water Distribution Systems," Journal AWWA, Vol. 81, No. 7, July 1989. Paper: Walski, Hartell and Wu, 2010, "Developing system head curves for closed systems" JAWWA, 102:9:84, September.

Applies To Product(s): WaterGEMS, WaterCAD Version(s): CONNECT Edition, V8i Area: Calculations Original Author: Jesse Dringoli, Bentley Technical Support Group Problem In a model with no downstream boundary condition (reservoir or tank) why do I see strange numbers when attempting to graph the system head curve of my pump? Problem Number 29108 Solution The system head curve option is invalid for this condition. The scale exaggeration throws off the graph--really what we're seeing plotted is a near-vertical line for the system head curve. As graphed, there is a huge change in head for a small change in flow. Only the single point at which the pump is operating (the point where the system head curve and the pump curve intersect) is valid. Although we can accurately show the actual pump operating point, we are unable to generate a valid system head curve for the condition represented in the model. This isn't a problem with the software, but rather a limitation dictated by the condition being represented. This is what the graph with the exaggerated scale looks like: Notice the large negative values on the Y-Axis. Here is some background on the WaterGEMS modeling algorithm. WaterCAD and WaterGEMS are demand-based calculations, unless flow emitters or pressure-dependent demands (V8 only) are being used. This means the modeler has to explicitly define the demands and the program runs the calculation to see the resulting flows and pressures that result when these demands are met. However, because of the way the pressure-based calculation works there needs to be some interpretation on the part of the modeler regarding the validity of the results. For instance, maybe the modeler runs a scenario for a very high demand, like a fire flow demand. The resulting calculation may show very negative pressures at some of the nodes for this condition, because the negative values are required to satisfy the energy equation for the specified demands. However, on reviewing the calculations, the modeler sees these negative pressures and realizes that, in reality, these pressures couldn't occur. Instead, the flow actually available at the fire flow junction will be less than what the modeler specified as the fire flow demand. Concerning system head curves: generation of this curve requires that the program have the flexibility to look at how the system reacts to a "range" of flows through the pump. In a system with storage downstream of the pump, the model is able to look at this range of flows because the downstream system has a way to deal with different flow rates being forced into it. To model flows on the system head curve (i.e., flows through the pump) in excess of the total node demand, any excess water can be used to fill the tank or reservoir. To model flows on the system head curve less than the total node demand, the difference in flow can be made up by the tank or reservoir. To sum up, when a system has storage (reservoir or tank) downstream of the pump, it is possible to create a system head curve because it is possible for the pump to push a "range" of flows into the system. In a situation in which the demands are fixed and there is no downstream storage/reservoir, this means that there is only one possible flow through the pump, which is equal to the sum of all the demands in the system. The only thing the model can compute is the single operating point of the pump--it is impossible to generate a "curve". Note : If the tank on the upstream or downstream end of the pump is empty, you will see results like this as well. If a tank is empty, the results will not be valid. In order to resolve this problem what you need to do is create and assign a pressure dependent demand (PDD) function to all of the junctions with demands in your model that are downstream of the pump you're creating to get the system head curve for. This wiki TechNote will describe how to create pressure dependent demands and add them to your model: Setting Up Pressure Dependent Demands Note : the pressure dependent demand function should be configured to have no threshold limit. This way, with increasing pressure the PDD demand can be increased above the base demand of the corresponding scenario to calculate the system head curve for flows larger than the total demand of all demand nodes in the closed network. Therefore using a piecewise linear PDD function is not recommended because this function is limited to the largest demand percentage in the PDD curve. Once this is done you should get an accurate representation of your system head curve graph: Set Vertical Axis Starting with the CONNECT Edition release of WaterGEMS and WaterCAD, you can now adjust the vertical axis for the system head curve. This can be especially useful for cases there there is no downstream storage. While the system head curve is not valid for cases with no downstream storage if you are not using pressure dependent demands, by assigning minimum and maximum head values, the graph will be less extreme and more legible, as seen below. To use this feature, select the checkbox for "Specify vertical axis limits" and enter minimum and maximum head values. See Also A forum discussion about this issue System Head Curves in WaterGEMS and WaterCAD Pump Selection for a Closed System Paper: Walski, Hartell and Wu, 2010, "Developing system head curves for closed systems" JAWWA, 102:9:84, September.

Applies To Product(s): HAMMER Version(s): V8i, CONNECT Edition Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem How do I model a pump shut down (pump power failure) transient event? Solution Shut down after time delay The traditional method of simulating a pump shutdown transient event is to use the Shut After Time Delay transient pump type. This assumes that the applied electrical torque drops to zero at the time that you specify for the shutdown. For more on the assumptions, check the article in the "See Also" section at the bottom of this page. Here are the steps to configure a pump shutdown event in HAMMER: 1) Set the pump Status(Initial) to 'On' 2) In the Transient (Operational) section of the pump properties set the pump type (transient) to 'Shut Down After Time Delay'. 3) Set the Time (Delay until Shut Down) property. The time you enter is the time at which the power to the pump motor is shut off. It should also be noted that a linear closure is assumed for this case. 4) Set the Pump Valve Type to check valve or control valve depending if the pump has one of these type of valves. If your pump has a control valve you'll need to enter the time it takes for the valve to close. This is the time taken for the pump discharge control valve to close after the transient simulation begins. The check valve assumes instant closure on the first detection of reverse flow. If you want neither a control valve nor a check valve, choose control valve and enter a large number such as 99999 seconds. If you want to control the closure time of the check valve use the steps from the last sentence then insert a check valve node element from your layout toolbar just downstream of the pump. See screen shot below: Note : unless you model this built-in valve, HAMMER does not assume that the pump is "closed" when the pump shuts down. Meaning, the "shut after time delay" simulates a power failure to the pump impeller, which eventually may drop to zero rpm. However, flow can still pass through the zero-speed pump, unless you model a valve closure. Variable Speed/Torque pump shut down Another option to model a pump shutdown transient event is to use the variable speed/torque option. This could be used as part of a shutdown followed by startup . Or, it could be used to model a controlled shutdown, where the speed is ramped down. Here are the steps: 1) Set the pump Status(Initial) to 'On' 2) Set the Pump Type to "Variable Speed/Torque". 3) In the Time (Valve to Operate) property you enter the time to close the check valve or to open it if initial flow is zero. If the check valve allows flow only in one direction enter 0 (i.e. the pump has a built in check valve). To simulate a pump with no check valve or control valve enter a very large number like 9999 seconds so it never closes. If you enter a very small number like 0.1 seconds, the valve would close immediately after the start of the simulation, which would cause a transient response similar to a valve closure. 4) For the control variable properties you can choose either speed or torque. For more information on the difference between the variable speed and torque setting please refer to this wiki article . Here the default value is to control the speed of the impeller by using the pattern. If you want to control the pump using the torque control variable (so the momentum of the impeller is accounted for like with the shut down after time delay type) you have the option to do that too. For that approach, you will need to enter the nominal torque of the pump before it shuts down. The nominal torque is then multiplied by the operating rule pattern multiplier that will result in the torque values the numerical solver uses. To simulate the same behavior as the "shut after time delay", you would have the multiplier in the pattern drop from 1.0 (full applied torque) to zero in one timestep, at the time that you want the shutdown to occur. For a controlled shutdown, you would control either the speed or the torque to gradually ramp down the pump, per the operating rule. 5) Define the operating rule the pump will shut down based on. Click the dropdown button in the entry box and choose to create a pattern. 6) Under the Operational (Transient, Pump) section, right click to create a new pattern and set the starting multiplier equal to 1.000. In the section of the window under that enter the "Time from Start" , which is the time the speed or torque starts to drop. In the multiplier column enter 0 for when the speed or torque is zero. If you have the pump shut down between time steps 5 and 10 seconds for example it will gradually shut down over that period. Modeling a pump startup followed by shutdown, or shutdown followed by startup The variable speed transient pump type would be used to model both a shutdown and startup in the same simulation. See more here: Modeling a pump startup and shutdown transient event in the same simulation See Also Modeling a pump start up transient event in Bentley HAMMER How does pump inertia effect the pump calculations during a transient simulation? Modeling a pump startup and shutdown transient event in the same simulation

Product(s): HAMMER Version(s): CONNECT Edition, V8i Area: Modeling Overview This tech-note discusses how to configure the Surge Tank element for transient analysis in HAMMER. Background A Surge Tank (also known as a “Stand Pipe”) is a surge mitigation device which can be modeled in HAMMER as a “Surge Tank” element. The surge tank supplies stored fluid (water) when pressures drop in the pipeline and takes fluid, when pressures increase (in case of two-way type). The Surge Tank is a non-pressurized type of tank i.e. the free water surface of the tank is open to atmosphere. The normal water level is typically equal to the hydraulic grade line at steady state. A surge tank can also overflow and the user can specify the weir coefficient for overflow. Types Surge Tanks can be of two types; simple or differential Simple Surge Tank A simple surge tank can operate in three modes under a transient analysis; normal when the tank water level is between the top and the connecting pipe(s) at the bottom; weir overflow when the tank water level is at the top in overflow condition; and drainage when the tank water level is at the elevation of the connecting branch(es). A simple surge tank can be a one-way or a two-way surge tank. One-way Surge Tanks A one-way surge tank is a relatively small conventional surge tank, with a check valve in the connecting pipe, or riser, that only allows flow out of the tank. The tank water level is maintained by an altitude valve bypassing the check valve. The tank is located at the high point to supply water and prevent water-column separation. However, one-way tanks provide no upsurge protection to the system because no flow is allowed back into the tank. Two-way Surge Tanks A two-way surge tank allows stored water to flow out in the event of low pressure developing in the pipeline but also allows water to flow into it in times of high transient pressures. two-way surge tank controls transients by converting stored potential energy in the elevated water body inside the tank into kinetic energy, which supplements flow in the piping system at critical times (or vice versa, for pipe flow into the tank) during periods of rapid flow variation. The tank is normally located at the pumping station or at a high point in the system. In HAMMER, you can setup a “Simple” surge tank and govern the type i.e. one-way or two-way by setting the “Has Check Valve?” field to either “True” or “False”. (True = One-way, False = Two-way) Differential Surge Tank A Differential surge tank is a specialized surge tank within a larger tank which provides a fast response. This type of a surge tank contains a differential orifice installed at the inlet riser which serves two functions, it doesn’t allow the surge tank to fill up quickly during a high pressure event by causing a large enough headloss to dissipate the transient energy but at the same time, flow can leave the surge tank quickly (with little headloss) in case of a low pressure event. There are different modes of operation for a differential surge tank. For "normal" operation, the tank water level is between the orifice and the top of the riser. Other modes are distinguished by the riser level relative to the orifice elevation and the tank level versus the top of the riser. During a powerful upsurge, the upper riser will overflow into the tank to complement the orifice flow. Surge Tank Properties The following is a description of the properties of the surge tank element. Operating Range Operating Range Type - choose "level" to enter the minimum, initial and maximum as levels above the base elevation, or "elevation" to enter the actual elevations. Elevation (Base) - this represents the datum elevation that levels are entered in reference to, when the Operating Range Type is set to Level. Often this is set equal to the Elevation (Minimum). Elevation/Level (Minimum) - this represents the physical bottom of the tank, below which an air pocket would form. See more here: What happens when a tank becomes empty or full? Elevation/Level (Initial) - this represents the starting water surface elevation in the tank. Not used when "treat as junction" is set to True (see calculated "Hydraulic Grade" in the "Results" section, instead) Elevation/Level (Maximum) - this represents the physical top of the tank, above which overflow will occur. See more here: What happens when a tank becomes empty or full? Use High/Low Alarm - Not used during the transient simulation (see note further below) Physical Elevation - this represents the datum elevation that pressure is based on. In most cases it would be set equal to the tank bottom elevation. Section - used to select the cross sectional shape of the tank Treat as junction? - this specifies whether the initial hydraulic grade of the tank is based on the Elevation (initial) (set to "False"), or if the HGL is computed for you. See more further below. Transient Surge Tank Type - Choose either Simple or Differential. A Differential surge tank is a specialized surge tank within a larger tank which provides a fast response. If set to differential, there are several more input values. (see section above). "Simple" is used to model a "normal" surge tank with an inlet opening and open top. Has Check Valve - If set to "true", the tank becomes a one way surge tank and liquid cannot enter the tank from the system. In this case, the tank is treated as a junction when running steady state (computing initial conditions.) See more below under "surge tank operation" Weir Coefficient - Coefficient 'k' in the formula for weir overflow, when the water surface elevation exceeds the top of the tank (the "Elevation (Maximum)" field). It is computed as follows: Q = k H^1.5 (H >= 0) where Q is the rate of overflow and H is the height above the top of the tank. The coefficient must be positive. By default, it is a large positive number. For a broad-crested weir, in SI units k = 1.84 L, where L is the width of the weir (refer to Streeter and Wylie, pg 358.) Weir Length - The length associated with the overflow weir as described above. Normally it is the perimeter of the top of the tank. Diameter (Orifice) - diameter of tank inlet orifice. (or the equivalent circular diameter, if the opening shape is not circular) Ratio of Losses - This is the ratio of inflow to outflow headloss and is used to model a differential orifice (see more below). For flows into the tank (inflows), the "minor loss coefficient" is multiplied by this value and the losses are computed using that. For flows out of the tank, HAMMER only uses the "Minor Loss coefficient". So, if you enter a minor loss coefficient of 1.5 and a ratio of losses of 2.5, the headloss coefficient used when the tank is filling would be 1.5 X 2.5 = 3.75. Headloss Coefficient - this is used to compute headloss through the surge tank inlet orifice, based on the standard headloss equation (K = V^2/2g). The headloss coefficient applies directly for tank outflows. For tank inflows, it is multiplied by the "ratio of losses" and the resulting coefficient is used. The effect of a differential orifice can be large for some systems. Note: you may consider adjusting the minor loss coefficient to represent multiple losses through the tank assembly. For example you may have minor losses from bends, fittings, the tank inlet itself and the differential orifice assembly. In this case, you can set the "minor loss coefficient" value to represent all those losses, but remember that the velocity used to calculate them is based on the area of the "diameter (orifice)". Also, you'll need to set up the ratio of losses such that the losses through the entire tank assembly appropriately accounts for the additional loss through the bypass of the differential orifice Transient (Reporting) Report Period Differential Orifice (not to be confused with the differential surge tank type described further above) The piping connection between the surge tank and the system should be sized to provide adequate hydraulic capacity when the tank is discharging, as well as to cause a head loss sufficient to dissipate transient energy and prevent the tank from filling too quickly. Both of these requirements are met through the use of a piping bypass. In HAMMER, the headlosses associated with this can be modeled by using the "Minor Loss Coefficient", "Ratio Of Losses" and "Diameter (Tank Inlet Orifice)" attributes of the surge tank. This is referred to as the differential orifice, because the ratio of losses allows you to have the inflow headlosses different from the outflow headlosses. In the above illustration, you can see that the check valve causes inflows to undergo larger headlosses as water passes through the bypass. So, the ratio of losses attribute is usually larger than 1.0 and applies to inflows. Surge Tank Operation The surge tank operation depends on how the surge tank is setup in the model. If it is a simple one-way type surge tank, the hydraulic grade observed would initially be above the tank water level as a one-way surge tank's check valve would close to only allow fluid / water to flow out during a low-pressure event to avoid water column separation. If the hydraulic grade during the transient simulation falls below the initial water surface elevation, the check valve opens and water exits the surge tank and enters the pipeline (to keep the water column moving during a "downsurge" transient). In the case of a two-way surge tank, the hydraulic grade in the pipeline would be more or less the same as the tank hydraulic grade as water is allowed to flow out as well as flow in. When initial conditions are run, the surge tank would behave as a normal tank with level fluctuations as one would observe in an Extended Period Simulation. If your system hydraulic grade is very high at the surge tank location, a two-way tank may not be feasible since it would have to be taller than the hydraulic grade. A note on "Treat as junction?" If your surge tank "floats" on the system (hydraulic grade = system HGL, with zero inflow and outflow during normal operations), set the "Treat as Junction?" property to "true". This tells the initial conditions solver to treat the tank as a junction, and therefore calculate the HGL as if there is no tank present. The resulting HGL is then used as the starting water surface elevation of the tank, instead of the "Elevation (initial)". This provides an easier way to model a tank whose HGL floats on the system; otherwise you would need to adjust the "Elevation (initial)" until the tank had zero inflow and outflow, and may need to do so repeatedly for different scenarios and other changes to the model. With this option set to True, ensure that the resulting HGL does not fall below the "Elevation (minimum)" or above the "Elevation (maximum)". Note: Sometimes the surge tank may fill up or empty too quickly to observe the mitigation of the transients produced. In such times, it is better to set up a higher “report time” and a smaller time-step to observe the tank filling and emptying. Refer this link for more details. Reporting As of version 10.01.01.04, surge tank-specific output results are found in the Transient Analysis Detailed Report. To prepare for viewing this information, first check your transient calculation options. "Show standard output log" and "Enable Text Reports" should be set to "true". Next, enter a number for the "report period" field of your surge tank. This represents how often extended text results will be reported. For example, if your time step is 0.01 seconds and you enter '10' for the report period, it means you'll see extended text results every 10 time steps or every 0.1 seconds. To see a table of extended surge tank results, open the Transient Analysis Detailed Report , under Report > Transient Analysis Reports. Scroll down near the bottom, to the section starting with " ** Surge tank at node" and you will find a table of Level, Head, Inflow and Spill rate. Level : represents the water surface elevation inside the surge tank. Head : represents the hydraulic grade line in the pipeline just outside of the surge tank inlet. Inflow : rate of flow into the surge tank. A negative value indicates outflow. Spll-rate : the rate of flow that spills over the top of the tank, per the weir equation. Note: if high and low alarms are setup to trigger when violated the same would be reported when the initial conditions are run. However, these would not be reported when Transient Analysis is performed. Refer this article for more details. Troubleshooting "Invalid tank Operating Range" If you encounter a red user notification indicating that the tank operating range is invalid, check to make sure that the "initial" is between the "minimum" and the "maximum" field in the "Operating Range" section of the properties. If the "operating range type" is set to "level", note that the minimum, initial and maximum values represent distances above the "base" elevation. See Also Hydraulic grade above top of one way surge tank How can I see the amount of inflow or outflow occuring for a particular surge tank during the transient simulation in HAMMER? What happens when a tank becomes empty or full? How can I model a Vent Pipe or Stand Pipe in HAMMER? Using the Ratio of Losses field for hydropneumatic tanks and surge tanks Determining the Headloss Coefficient for a hydropneumatic tank or surge tank

Hola Marco, I used Google Translate to see your question in English. Below are responses in English, as well as Google translation back to Spanish: English: 1) As you mentioned, the "shut after time delay" stops the pump impeller, but flow can still pass through it if the hydraulic conditions dictate. If you do not want water to pass through the pump that is turned off, you will need to consider how the pump in the real system will prevent this. If it does not have a built-in valve, then water may indeed continue flowing through it. If there is a built-in valve that also closes along with the pump shutting down, you can model that in HAMMER by using the "Time (For Valve to Operate)" field in the pump properties. You can read more about that here: Modeling a pump shut down transient event 2) If you want to assume that the pond water surface elevation will stay the same (not move) during the transient simulation, you should use the Reservoir element. If you want to see the water surface elevation change, the tank or surge tank element can be used. The error you mentioned indicates that the surge tank's initial elevation is not between the minimum and maximum elevation. Can you provide a screenshot of the surge tank properties, including the "operating range" and "results" sections? If the "Operating Range Type" is set to "level", the values you enter for the "minimum", "initial" and "maximum" are distances above the "base" elevation. Make sure that the "initial" is between the minimum and the maximum. You can read more about surge tank modeling here: Modeling Reference - Surge Tanks En español: 1) Como mencionó, el "shut after time delay" detiene el impulsor de la bomba, pero el flujo puede pasar a través de él si las condiciones hidráulicas lo requieren. Si no quiere que pase agua a través de la bomba que está apagada, tendrá que considerar cómo la bomba en el sistema real evitará esto. Si no tiene una válvula incorporada, entonces el agua puede continuar fluyendo a través de ella. Si hay una válvula incorporada que también se cierra junto con el apagado de la bomba, puede modelar eso en HAMMER utilizando el campo "Time (For Valve to Operate)" en las propiedades de la bomba. Puede leer más sobre esto aquí: Modeling a pump shut down transient event 2) Si desea suponer que la elevación de la superficie del agua del estanque se mantendrá igual (no se moverá) durante la simulación transitoria, debe usar el elemento del depósito. Si desea ver que cambie la elevación de la superficie del agua, se puede usar el tanque o el elemento del tanque de compensación. El error que mencionaste indica que la elevación inicial del tanque de compensación no está entre la elevación mínima y máxima. ¿Puede proporcionar una captura de pantalla de las propiedades del tanque de compensación, incluidas las secciones de "operating range" y "Results"? Si el "Operating Range Type" está configurado en "level", los valores que ingrese para "minimum", "initial" y "maximum" son distancias sobre la elevación "base". Asegúrese de que la "inicial" esté entre el mínimo y el máximo. Puede leer más sobre el modelado de tanque de compensación aquí: Modeling Reference - Surge Tanks

Thanks for your continued interest. We are hard at work on a solution so that you can perform a 2D simulation with your CivilStorm model, with help from our recently acquired technology. We expect to have an announcement about this in the next few weeks. If you have not done so already, please subscribe to our Blog to get an email alert for release announcements.

Product(s): SewerGEMS, CivilStorm Version(s): CONNECT Edition Area: Modeling Problem When computing a model, using the Explicit solver, the following error is generated: ERROR 173: Time Series (element label)_Inflow_Ts has its data out of sequence. Solution First, make sure you are using the latest version of the software. The link has details on downloading the latest version: Downloading Haestad / Hydraulics and Hydrology software . If that doesn't help, review any patterns you are using, including for sanitary and wet weather inflows. For instance, if a pattern begins with hour zero, similar to the screenshot below, this error message will be valid. Note that since you have included a starting multiplier for the pattern, have an hour zero may be inaccurate. In addition, make sure the last item in the pattern matches the starting multiplier. See Also Troubleshooting unstable SewerGEMS and CivilStorm model results using the Explicit SWMM Solver

Applies To Product(s): PondPack Version(s): 08.11.01.XX, 10.00.00.XX Area: Modeling Original Author: Scott Kampa, Bentley Technical Support Group Problem What does the following user notification mean? "Non-increasing value for 2/t + O...Elevation= A ft. Discharge= B ft³/s. Volume= C ac-ft. St2O= D ft³/s." Engine Fatal Error Solution PondPack uses the storage indication method when doing pond flow routing calculations. There is some good detail on this in the Help (see Hydraulics Theory > Routing Methods > Ponds). These calculations rely on the value of this equation to be increasing as depth increases (see the Help for background on this equation): 2 x Storage Volume / calculation time step + Outflow But in certain situations this doesn't happen, so you get the error in question. The solution may be different in each situation, but a good start would be to check the storage volume for your pond. If it's very small, you may need a smaller calculation time step (set in the calculation options). For further help, contact technical support. Conduit If the notification points to a conduit and there are no problems with the configuration (ie. They have reasonable lengths, slopes etc.) then set the conduits' property Conduit Type to User Defined Conduit. Then verify the conduit shape, diameter, material and roughness are correct. Note: If the user defined conduit properties have not been defined for a pipe, then the values will be retained from the catalog conduit after switching the conduit type. No Volume Pond If you are using a "No Volume" pond, ensure that the adjacent outlet structures are configured correctly. A user defined headwater range should be used in the downstream outlet and a user defined tailwater range (via interconnected ponds as the type) should be used for the upstream outlet. Void Space If you have the "use void space" set to "true", try setting it to "false", then adjust the pond elevation-area or elevation-volume curve to compensate for the void space (instead of using the void space option). For pond types like Pipe or trapezoidal, this can be done by first viewing the elevation area table via right click > pond volume results table , then noting the area (or volume) results. Next, switch the pond volume type to elevation-area or elevation-volume and enter the adjusted values to define the pond volume available for storage.

Hasta hoy veo tu respuesta. Yo te recomendaría que sigas o mi método o el de Douglas, known flows son una forma de forzar el caudal que uno quiere en una tubería pero como te habrás dado cuenta no son aditivos, simplemente cuando el caudal que "va" en una tubería se encuentra un nuevo "known flow" en otra intersección, se resetea y cambia a ese nuevo valor. Mejor dicho no hay continuidad de nada, y para reportar eso en flextables se vuelve un enredo!! Es mejor que manejes solo caudales de un tipo, en tu caso, caudal sanitario "sanitary loads".

Hi, Does anyone got training video and dataset to learn on CulvertMaster? Client bought the CulvertMaster and would like to learn from Bentley LEARN but no training info available for CulvertMaster. I already logged service ticket (ST 7000819409) but no reply, Thank you in advance.

Hello Harati, You have to use the "Load Estimation by Population" method in LoadBuilder. Please refer the below article which provides details on all the methods used for load estimation; How do each of the LoadBuilder methods work? Hope this helps.

Hello, That's true there is no any training course available about Culvertmaster on Learnserver, please allow us some time to see if we have any training material available on our internal sharepoint, which we can share with the user. Till then you can ask the client to go through the tutorials in Help. Go to Culvertmaster>Help>Tutorial.