Hi Terry Even when I try snapping to a polyline I must turn on the snap tool each time. I am able to draw the conduit and then snap it onto the polyline by moving the node but that's time consuming. It may be something to do with profile settings? Colm.

For a situation like this with a single pipe, I would set up the model with an estimate of the pipe size, run it, check the results, then adjust as needed. You can graph HGL (or percent full) in the tank to see how long it takes to fill.

If you are comfortable with estimating the shape of the gutter as conventional, then what you mentioned sounds like a reasonable approach. From the picture, I assume the road is sloped (cross slope) toward the vertical concrete barrier, which would form a typical conventional gutter cross section. If you define the gutter at the inlet location in the catchbasin properties as Conventional and select "Same as Start Node Gutter" in the downstream gutter link element, that gutter link will use the same conventional gutter cross section that you had selected for the inlet. In your case it does look like a uniform cross section at both the inlet location and to the sides, so this seems reasonable.

Applies To Product(s): WaterGEMS, WaterCAD, HAMMER, SewerCAD, StormCAD, SewerGEMS, CivilStorm, Pondpack Version(s): V8i or V8 XM Environment: N/A Area: N/A Original Author: Scott Kampa, Bentley Technical Support Group Overview The purpose of this technote is to briefly discuss the scenario management in the Bentley Hydraulics and Hydrology products. There are also Quick Start Lessons related to Scenario Management. These can be found by opening the product and going to Help > Quick Start Lessons. Background Scenario Management is one of many project tools available in Bentley Hydraulics and Hydrology products. Scenarios allow the user to calculate multiple "What If?" situations in a single project file. The user can try several designs and compare the results, or analyze an existing system using several different input alternatives and compare the results. A Scenario is a set of Alternatives and Calculation Options. Alternatives contain the actual model data. Calculation Options allows the user to run different types of analyses. The available items and properties listed for Alternatives and Calculation Options will vary from product to product. Scenarios and alternatives are based on a parent/child relationship, where a child scenario or alternative inherits data from the parent scenario or alternative. This can be useful in situations where a new scenario will use most of the model data from an existing scenario, with only minimal changes to an alternative. As noted above, different products will have different available Alternatives. For simplicity, the screenshots below will show the alternatives list for WaterGEMS. The general steps involved will be the same across all products. Scenarios: A Scenario contains all the input data (in the form of Alternatives), calculation options, results, and notes associated with a set of calculations. Scenarios let you set up an unlimited number of "What If?" situations for your model and allow you to modify, compute, and review your system under different conditions. This section will describe how to create new Scenarios, how to switch between existing scenarios, how to calculate a batch run, and how to compare results from different scenarios. Scenario Manager The Scenario Manager allows you to create, edit, and manage an unlimited number of scenarios. When opening a new project, there will be one default scenario, called “Base”. If you want to model different conditions in a system, whether it is modeling peak demands versus average demands or the current system layout versus a proposed future system layout, you can create additional scenarios that reference the alternatives needed to perform and recall the results of each of your calculations. The Scenario Manager can be opened by going to Analysis > Scenarios. You can also click the Scenario icon listed above the drawing pane. Creating New Scenarios There are two methods to create a new scenario. First, you can select the New icon in the upper right and choose either Base or Child Scenario. As stated above, child scenarios will inherit data from the parent scenario. Second, you can right-click on any scenario listed in the Scenario Manager, select New, and choose either Base or Child Scenario. There are two types of scenarios: Base Scenarios and Child Scenarios. Base Scenarios contain all of your working data. When you start a new project, you begin with a default base scenario. As you enter data and calculate your model, you are working with this default base scenario and the alternatives it references. Child Scenarios inherit data from a base scenario or other child scenarios. Child scenarios allow you to freely change data for one or more elements in your system. Child scenarios can reflect some or all of the values contained in their parent. This is a very powerful tool, giving you the ability to make changes in a parent scenario that will trickle down through child scenarios, while also giving you the ability to override values for some or all of the elements in child scenarios. Changing the Current Scenario Once you have multiple scenarios, you will want to switch between them to view the properties and results in a given scenario. There are a few different ways of doing this. First, you can select the Make Current icon in the Scenario Manager. This will make the highlighted Scenario the active scenario. Second, you can right-click on any scenario and select Make Current. Third, there is a way of changing the current scenario outside of the Scenario Manager. In the main page, there is a pulldown menu listing the name of the current scenario. By clicking in this box, you will see a list of the available scenarios. Choosing a scenario from the list will set that scenario as current. Note: If the pulldown is not available, it can be added. Right-click on the space around the other icons and select the Scenarios item. This will add the pulldown, as well as icon to open the Scenario Manager, Alternatives Manager, and Calculation Options Manager. Batch Run You can compute your scenarios one at a time by making a scenario current and then computing the model. You can also compute more than one scenario consecutively by doing a Batch Run. As with many functions in Scenario Management, there are multiple ways of doing this. First, you can select the small triangle beside the Compute icon, then select Batch Run. Second, you can right-click on any scenario, then select Compute, then Batch Run. Either method will result in a new dialogue listing all available scenarios. Click the box beside the scenarios you wish to compute and then select Batch. Each selected scenario will then compute. Note: Once multiple scenarios are computed, either manually or with a batch run, it is possible to compare results either by switch between scenarios (see “Changing the Current Scenario” above) or by graphing given elements in the model. Scenario Properties As stated above, scenarios are a compilation of alternatives and calculation options. Viewing, changing, and managing the different alternatives associated with a scenario is done through the Properties dialog. In order to view the scenario properties, double-click on the scenario. Alternatively, you can right-click on the scenario and choose Properties. Displayed in the Properties dialog will be a list of the alternatives associated with the scenario. If you have created a new scenario, you will likely wish to change to an alternative that reflects the properties of the scenario. If you have created a new Base Scenario, all of the alternatives will default to the Base Alternatives. If you created a child scenario, the scenario will initially inherit all of the alternatives from the parent scenario. When you create a child scenario, by default it inherits the selection/configuration of alternatives of the parent scenario. In which case, you will see the "I" next to the name of the alternative. If you pick an alternative without the "I," then the child scenario will no longer inherit the changes in alternatives made in the parent scenario. To change any alternative for a scenario, click the pulldown beside the scenario name and select the alternative. If you have not yet created an alternative for the scenario, you can create a new alternative here as well. Select the item “New”. You will be prompted to enter the name for the new alternative. After entering the name, the new alternative will be selected for the scenario. Note : The new alternative will now be listed in the Alternatives Manager. Alternatives: Alternatives Manager The Alternative Manager allows you to create, view, and edit the alternatives that make up the project scenarios. The dialog box consists of a pane that displays folders for each of the alternative types which can be expanded to display all of the alternatives for that type and a toolbar. The Alternative Manager can be opened by going to Analysis > Alternatives. You can also click the Alternatives icon listed above the drawing pane. As with scenarios, there are two kinds of alternatives: Base alternatives and Child alternatives. Base alternatives contain local data for all elements in your system. Child alternatives inherit data from base alternatives or even other child alternatives. The data within a child alternative consists of data inherited from its parent and the data altered specifically by you (local data). Remember that all data inherited from the base alternative is changed when the base alternative changes. Only local data specific to a child alternative remain unchanged. Steps to create new alternatives are the same as the steps to create new scenarios. See the section “Creating New Scenarios” above. Editing Alternatives To edit an alternative, expand the tree so that all of the alternatives for a given category are listed. There are a number of ways to open an alternative. You can double-click on the alternative. You can also highlight the alternative and select the Open icon. Finally, you can right-click the alternative and select Open. This will open a new dialog window. Each alternative will have different properties. Any column that is shown as white is an editable field. Columns in yellow are not editable from the alternative, but in some cases may be editable from other places in the model, such as the Flextables or Properties. The first column in any alternative editor contains a series of check boxes, which indicate the records that have been changed in this alternative. If the box is checked, the record on that line has been modified and the data is local, or specific, to this alternative. If the box is not checked, it means that the record on that line is inherited from its higher-level parent alternative. Inherited records are dynamic. If the record is changed in the parent, the change is reflected in the child. The records on these rows reflect the corresponding values in the alternative's parent. Information on the individual alternatives available in the different hydraulics and hydrology software can be found by searching the Help menu for the product. Note: Changes made in the drawing pane, Properties, and Flextables will automatically make changes to the values in the active alternative. Calculation Options The Calculation Options Manager allows you to create, view, and edit the calculation options available for your scenarios. The dialog box consists of a pane that displays calculation options created. Note: The parent/child function is not used in for calculation options. New calculation options can be created by select the New icon. In order to edit the calculation options in the manager, double-click on the one you want to edit. This will display the properties of the calculation options in the Properties dialog. Properties contained in the calculation options will differ between different hydraulics and hydrology software. Information on what properties are available can be found by searching the Help menu for the product. Scenario Comparison Please see the following link for details: http://communities.bentley.com/products/hydraulics___hydrology/w/hydraulics_and_hydrology__wiki/19839.is-it-possible-to-compare-scenarios-and-between-models-solution-500000067646 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 Comments or Corrections? Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Applies To Product(s): Bentley HAMMER Version(s): V8i Environment: N/A Area: Modeling Original Author: Jesse Dringoli, Bentley Technical Support Group Overview This technote explains how the Discharge to Atmosphere element works and its typical application in HAMMER V8i. It also provides an example model file for demonstration purposes. How it Works The "discharge to Atmosphere" element encompasses a valve to atmosphere, orifice to atmosphere and head vs. flow rating table. It is used to model an opening / orifice that allows flow to leave the pipe network and discharge to the atmosphere. You can model it as a fixed orifice that is always open, or a valve that is either initially open or closed, then opens or closes during the transient simulation. It can be placed in series with the main water line or at a "T" Note: it is important to understand that this element discharges to atmosphere, not between the adjacent pipes. So in the above case of an in-line orientation, flow still passes through the pipeline beneath the valve, regardless of if the valve is opened or closed. In the calculation engine, it is essentially modeled as a demand point located a hydraulically short distance from its node coordinates (based on the wave speeds of the pipes connected to it). The initial pressure and flow (entered by the user) are used to automatically calculate a flow emitter (orifice) coefficient, which will be used during the simulation to calculate transient outflows. This applies to both the initial conditions (steady state) solver as well as the transient solver (they both use the same resulting pressure/flow relationship) Basically HAMMER uses that coefficient to calculate other flows and their corresponding pressure drop: Q = C A (2 g P)^0.5 Q - Discharge (cfs, cms) C - A 'discharge coefficient' (distinct from CV used elsewhere in HAMMER) which will be computed based on the typical flow/pressure A - The cross-sectional area of the opening (ft, m) g - gravitational acceleration P - Pressure head (ft, m) As you can see, once the "C" is calculated from the initial head/flow, HAMMER can solve for other flows, as the pressure head changes during the simulation. Note: if pressure in the system becomes subatmospheric (below zero) during the simulation, the discharge to atmosphere element allows air into the system. When to Use it Common applications of the D2A acting as a valve Opening or closing of a hydrant, blowoff, sprinkler or other discharge - Select "Valve" as the Discharge Element type and specify the initial status. If the valve is initially closed at the start of the transient simulation, it will open and vice versa. Set the time to start operating and the time to be fully open; the valve opening increases linearly. Set the emitter value for the element by specifying the pressure drop at some flow rate. Modeling a main break - The discharge element type is also "valve" in this case, but the "time to Fully Open or Close" would be zero. This is because it is conservative (for a design scenario) to model the rupture occuring quickly and producing a large opening. Essentially the initial conditions describe the normal pipe and appropriately conservative flow conditions just before the break, then the transient simulation instantly opens the 'valve', to initiate transition to a ruptured condition. To represent the opening's size, it is recommended that the user set the "Pressure drop (typical)" to the steady-state pressure (observed prior to the break), and only vary the "flow (typical)" according to the equation further above. A sensitivity analysis wherein the cross sectional area, A is varied would illustrate the consequences of a range of breaks, with an upper limit to A being the diameter of the incoming pipe(s). The analysis should also consider different locations of the break(s). Depending on the pipe network's topology, a sudden break can lead to the formation of vapor pockets with ensuing collapses and pressure spikes. Common applications of the D2A acting as an Orifice Demand/consumption points that can let air in. In HAMMER V8i, any demand at a node (junction or hydrant) is called a consumption node and is treated as an orifice discharging to atmosphere that cannot allow air back into the system during periods of subatmospheric pressure. This is because the majority of water demands entered into hydraulic models are really the sum of several houses or demand points, each located at a significant distance from the point where their aggregate demand is being modeled. HAMMER assumes that any air allowed into the system at the individual demand points cannot reach the aggregate demand location. If this is not the case, you must model the demand using the Discharge To Atmosphere element, set as an orifice. This is because upon subatmospheric pressure, the discharge to atmosphere element allows air into the system. Any free discharge point. For example, the end of a sewer force main that discharges to an unsubmerged manhole, or a free discharge into the top of an un-modeled tank. You would need to decide how to compute the headloss through the pipe outlet, but a decent estimate might be headloss = k*v 2 /2g, where k is set to 1, v is the flow velocity and g is gravity. Alternatively, if the outlet orifice is smaller than the pipe diameter (unlikely) you might want to use the orifice equation, V = C*(2g*headloss) 0.5 . Of course these equations are very similar to each other. Basically you would select an approximate flow (and therefore velocity) and use one of the above approaches to solve for the "Pressure drop (typical)". Transients initiated by an 'inrush' event. When a pump turns back on in a sewer force main, it may expell some air from the downstream end. The headloss through the discharge opening causes a resistance that can result in a severe upsurge once the water column reaches the opening. For example, with a small orifice size, an upsurge occurs when the flow reaches it, because the water basically can't get out of the pipe fast enough. Modeling this situation can be done by using the Discharge to Atmosphere element, operating as an orifice. The initial conditions must describe the low head condition (zero pressure at the discharge to atmosphere element) and you must enter a volume of air in the "Gas Volume (initial)" field. You would then have the head increase during the transient simulation (pump turning on or periodic head element with head value increasing, for example.) The "Flow (typical)" and "Pressure drop (typical)" would be estimated similar to item 2. Basically the higher the "Pressure Drop (typical)", the smaller the orifice size, and the more resistance to flow, resulting in a higher upsurge after the air pocket is expelled. Note: The "Gas Volume (Initial)" will impact the timing of the release of the air. The value you enter will be up to your engineering judgment, but a good starting point may be the volume of the "empty" pipe. A larger volume of air for the same size orifice will take longer to be expelled from the D2A. This, in turn, will impact the head increase at the source. The most important impact on the system will occur with the air is fully expelled, which is when the transient would occur. So while a large air volume will take longer to expel, the setup and size of the D2A may prove to the be most important part of the transient event. Impulse turbine. The turbine element in HAMMER is not used to represent impulse turbines. Transients caused by impulse turbines can be approximated in HAMMER by using a Throttle Control Valve (TCV) or Discharge to Atmosphere element to represent the turbine nozzle. Note: the "rating curve" discharge element type is used when the discharge out of your orifice does not follow a typical orifice-equation relationship. It allows you to explicitly define the flow released out of the system for certain pressures at the discharge location. Attributes The following attributes are available when the "discharge element type" is set to "Valve": "Valve Initial Status" - This specifies whether the valve is initially open or initially closed. "Time to Start Operating" - The valve starts to operate after this time. (either starts to open or starts to closed, based on the initial status selection) It is measured from the start of the simulation. So a value of 5s means that the valve remains in a fixed position for the first 5 seconds, and then starts to operate. "Time to Fully Open or Close" - This is the time it takes for the valve to either fully open (if the initial status is closed) or fully close (if the initial status is open. It is measured from the "time to start operating". Meaning, if the "time to start operating" is set to 5s and the "time to fully open or close" is set to 10 seconds, then the valve closes linearly between time t=5 and t=15. (the valve is fully closed 10 seconds after it starts operating). "Flow (Typical)" - This is the typical discharge out of the valve when it is open. "Pressure Drop (Typical)" - This is the pressure corresponding to the typical flow through the valve. It is referred to as the "drop" because the pressure beyond the orifice is zero. The pressure and flow computed in the initial conditions will not necessarily be equal to these values, so you only need to enter any known pair. For example, if modeling a hydrant closure, you might enter the typical pressure and flow as the flow and pressure observed in a field test when the hydrant was opened. You are basically defining an orifice size by way of the "typical" flow and pressure drop fields. By supplying one pair of pressure and flow, HAMMER can figure out the relationship based on the orifice equation that gives the pressure drop for any flow value. So, if unsure, you can use the orifice equation along with the size of your opening and an estimate of the "head" (pressure head drop) to solve for the typical flow. Selecting a pressure head drop close to a typical value you might see under normal operating conditions will yield the most accurate pressure/flow relationship during both the initial conditions and transient simulation. See further above under "How it works". Note: a standard 2.5 in. (100 mm) hydrant outlet would have a pressure drop of roughly 10 psi at 500 gpm. When the Discharge Element type is set to "orifice", only the typical pressure drop and typical flow are available. When set to Rating Curve, only a rating curve table is available, where you would enter the table of head versus flow for your discharge. Initial conditions and transient head/flow is computed based on the values in this rating table. Example Model Click to Download Note: the above model is for example purposes only. It can be opened in version 08.11.00.30 and above and you can find additional information under File > Project Properties. See Also Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs Protective Equipment FAQ General HAMMER V8i FAQ External Links Water and Wastewater Forum Bentley Technical Support KnowledgeBase Bentley LEARN Server

Applies To Product(s): WaterCAD, WaterGEMS, SewerGEMS, SewerCAD, StormCAD, PondPack, CivilStorm Version(s): V8i Environment: N/A Area: Modeling Original Author: Akshaya Niraula, Bentley Technical Support Group Overview One of the greatest features of Bentley's Municipal product line is the ModelBuilder tool. Using ModelBuilder, a hydraulic model can be created as well as updated. In the V8i product generation, ModelBuilder is also capable of updating the source GIS file. The steps provided here will help you to first to create the model, then update it, and finally update the source file. Similar steps can be followed in several software packages from the Haestad Methods product line, such as WaterGEMS, WaterCAD, SewerGEMS. The procedure below uses a Geodatabase as the source of modeling information and WaterGEMS as the modeling software. Please note that the geodatabase option as data source type will only be available in WaterGEMS for ArcMap. In the standalone version if you want to work with importing a shapefile you can select ESRI Shapefile as your data source type. **Note: Helping to achieve proper network connectivity using modelbuilder starts when a shapefile or feature class is created in ArcMap. When creating the file you should make sure to turn on all your snapping options so the elements are actually connected in ArcMap and there aren't gaps between the elements. Another thing that you want to do is make sure that you are laying out the elements in the correct order according to WaterGEMS rules. This means that every pipe needs to have some type of node element attached at either end. Node elements include junctions, tanks, valves, reservoirs, and pumps. If possible it's also advised to create a new pipe between each two nodes elements. This means that instead of laying out all your pipes first when creating your shapefile (feature class) you would create things in the following manner: i) Create a node element ii) Create the line element representing the pipe iii) Create the end node element for the line iv) Repeat steps 1-3 until finished. Preview of Source File As mentioned, for this example the source file of modeling information is GeoDataBase (GDB). This GDB contains four modeling elements (or hydraulic features). 1) Well 2) Tanks 3) Pump 4) Pipe The modeling attributes for each of the features are shown in picture below. Build Model Using ModelBuilder The first step, in general, is to build the model. Here, ModelBuilder is used to build the model. The source file used is GeoDataBase. The procedure assumes that you have created a blank model in ArcMAP, and that most of the WaterGEMS menus are active. Open ModelBuilder To open ModelBuilder, choose Tools > ModelBuilder (Tools menu of Hydraulic Modeling Product) ModelBuilder as shown below will show up. Click on the New button (highlighted). Specify your Data Source The "Specify your Data Source" dialog will show up. First, select the Data Source type, and then ‘Browse' for the source file, as shown. You can select more than one shapefile at a time by holding down the CTRL button. In this step: Source data can be selected. Tables/ layers can be selected/ deselected SQL query can be applied to filter the table if required Source table can be previewed When the "Show Preview" box is checked, only the highlighted Table will be displayed. The "WHERE" statement applies only for selected layer (in this case, "PIPE []"), and different "WHERE" statements can be specified for different layers. Below is an example: Notice the other two pipe attributes are not shown in the preview. In this example, the "WHERE" statement will not be used. (If it were used, only two pipes would be created.) Click Next. Specify Spatial and Connectivity Options Depending on the source file, your screen may look different from the example screen capture below. Provide the unit of your Source Data under "Specify the Coordinate Unit of your data source. If you are not sure of your units, try "ft." Checking the box next to "Create nodes if none found at pipe endpoint" will create a pressure junction at any pipe endpoint that (a) doesn't have a connected node, and (b) is not within the specified tolerance of an existing node. This field is only active when the "Establish connectivity using spatial data" box is checked. (This option is not available if the connection is bringing in only point type geometric data, for example, Well or Wet-Well.) Check the box for "Establish connectivity using spatial data" and provide a value for 'Tolerance'. Pipes will be connected to the closest node within the specified tolerance. The unit associated with the tolerance is dictated by the Specify the Coordinate Unit of your data source field. Click Next. Specify Element Create/Remove/Update Options Depending on your requirements the selection of options may vary. For this example, the options are selected as shown. After you select the appropriate options, Click Next. Specify Additional Options This step is particularly important if the GIS source file has a Unique ID. In this workflow, there is a unique ID, so GIS-ID has been selected. If there is no unique ID, you can select Label, and it will work similarly. For more information on these options please search for them in the programs help menu. If you plan to use the Sync Out feature (update the source file based on model updates), then maintaining a Unique ID is highly preferred. The Help file explains each option in detail. When you have finished selecting additional options, click Next. Specify Field mappings for each Table/Feature Class In this step, data source tables are mapped to the desired modeling element types, and data source fields are mapped to the desired model input properties. The screen below shows steps for mapping Pipe element types and Diameter fields. In this case, the "LABEL" is the field that holds the Unique ID. So, the "Key Field" is LABEL. If there is no unique ID, then select from the drop down. Select the Table. Select the Table Type. Select the Key Fields. Select the source field. From the Property (of hydraulic model), select the corrosponding field (6). If needed, select the unit--"in" in this case (not shown). To map the material, see 7-9 below. Do NOT map the Unique ID field or field. Finally, the screen should look like: Similarly, the remaining tables can be mapped. The following screen shows the Pump mapping structure. The screen below represents Tanks mapping structure. In the same way, Wells can be mapped. After mapping all the elements and fields, click Next. Create Model Now? Select "Yes" and click on "Finish". ModelBuilder Summary Close the Summary after reviewing. Click "Yes" in the next screen (below). Finally, the screen should look like below. Notice the existing features are turned off, and new layers of the WaterGEMS are checked. This concludes the model building process using ModelBuilder. Note: After running ModelBuilder, ModelBuilder creates an xml file which holds all the configuration information. This link will be used to update the model again; otherwise, all the fields need to be mapped again. The link that was used to build the model can be seen in the image below. See Also Updating A Model Using Model Builder Updating Source File Using Model Builder Setting Boolean (True/False) Fields using Model Builder Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs WaterGEMS V8 Modeling FAQ External Links Bentley Technical Support KnowledgeBase Bentley LEARN Server Water and Wastewater Forum

Applies To Product(s): Bentley WaterGEMS, Bentley WaterCAD Version(s): 08.11.XX.XX Environment: N/A Area: Calculations Original Author: Terry Foster, Bentley Technical Support Group Error or Warning Message Why do a I get a message that states "Pump X" cannot deliver flow or head? Where 'X' is the pump label. Explanation This message can occur if the pump was trying to operate at the shutoff point (zero flow), but it will also show if the pump is operating beyond the defined pump curve. WaterCAD/GEMS will extrapolate out the pump characteristic curve past the maximum operating point if the curve does not go out to zero head, but it is not desirable for a pump to operate past the defined pump curve. Information to Check 1) Check the pump curve to make sure it is defined correctly and as accurately as possible. A 3 point design curve or multiple point curve is preferable to have over a 1 point design curve because they are usually more accurate to what you have in the field. 2) Check your junctions or demand control center to make sure you demands are correctly entered. Having too large a demand might cause your pump to operate off its defined curve. 3) Check your pipe for large reported headloss values. These could be an indication something is wrong with the pipe such as too small a diameter, too long/short a pipe, too large a minor loss, too large a roughness coefficient. 4) Assuming that the flow and head data in the pump curve is correct, check the downstream elevations and hydraulic grade, as well as the elevation of the pump. If the difference in elevation between the pump and a downstream tank or reservoir is larger than the shutoff head of the pump, you may see that the pump will not operate and the user notification is generated.

Applies To Product(s): Bentley WaterGEMS, Bentley WaterCAD Version(s): 08.11.xx.xx Environment: N/A Area: Modeling Original Author: Scott Kampa, Jesse Dringoli, Tom Walski How To: Model a Connection to an Existing System Background A connection to an existing system is typically required when modeling a proposed expansion (such as a new subdivision, industrial park, school, shopping mall, etc.). Frequently, the engineer will not have complete information on the system to which they are connecting, and must decide on an appropriate approach for modeling this connection. The most reliable method for representing the existing system is to include a least a skeletonized representation of the significant system components that affect the project area. Typically, this representation would include tanks, pumps, control valves, and significant demands in the same pressure zone. This necessary information can usually be obtained through water utility mapping and modeling personnel. Another method for modeling a connection to an existing system is to represent the connection point as a constant head elevation using a reservoir element. This is a very simplified approach, and usually a very unreliable one, since it doesn’t account for any fluctuation in head due to changing system conditions (e.g., pump status, tank level) or demands. The reliability of the method described in this article lies somewhere between the two just described. It consists of representing the connection to the existing system as a reservoir and a fictitious pump with a 3-point characteristic curve based on static and residual pressure obtained during a two-hydrant flow test near the connection point. The fictitious pump will simulate the pressure drops and the available flow from the existing water system. Unlike the first approach described, this third method does not allow the engineer to capture the changes at the connection point due to, for instance, fluctuating tank levels and pump status changes in the supply system. However, it does allow for consideration of change in head due to variation in the demand at the connection point. When combined with a good general understanding of how the larger system performs under a range of conditions and knowledge of system conditions (e.g., tank and pump status) at the time flow tests were performed, it can be an acceptable approach in many instances. It is usually most appropriate for “fill in” development where most of the customers and infrastructure are already in place as opposed to large expanses of undeveloped land at the fringe of an existing system. If model results obtained using this method are near the borderline of being unacceptable, the engineer should revert to the more rigorous first approach. NOTE: This method is only an approximation, so the results will not be as accurate as if you modeled the system back the actual source. It is also important to note that you cannot model multiple connections to an existing system. The results in such a case could be skewed and will not be viable. In order to simulate the range of pressures at the connection point for a range of flows, you must first obtain two-hydrant flow test data. To represent zero flow, you'll need the static pressure. To represent the highest flow possible through the connection, you'll need the residual pressure and flow. To convert the pressures to hydraulic grade, you will need to know the exact elevation of the residual pressure gage. This data is obtained from field tests. For more information on how to perform a field hydrant test, you may refer to section 5.2 of Advanced Water Distribution Modeling and Management . NOTE: The flows you obtain from the hydrant test must be in actual flow units such as gallons per minute, not pitot gage pressures. Equation 5.1 in Advanced Water Distribution Modeling and Management provides a conversion. Steps to Accomplish The reservoir simulates the supply of water from the system. The Elevation of the reservoir should be equal to the elevation at the connection point. The pump and the pump curve will simulate the pressure drops and the available flow from the existing water system. The points for the pump curve are generated using a mathematical formula (given below), and data from a fire flow test. The pipe should be smooth, short and wide. For example, a Roughness of 140, length of 1 foot, and diameter of 48 inches are appropriate numbers. Please note that it is ALWAYS best to model the entire system back to the source. This method is only an approximation, and may not represent the water system under all flow conditions. Qr = Qf * [(Hr/Hf)^.54] where: Qr = Flow available at the desired fire flow residual pressure Qf = Flow during test Hr = Pressure drop to desired residual pressure (Static Pressure minus Chosen Design Pressure) Hf = Pressure drop during fire flow test (Static Pressure minus Residual Pressure) D etermining the Three-Point Pump Curve Below is an example of how the three-point pump curve is developed. This will use the flow test results from your system, but the steps below will be same once you have that data. 1. The first point is generated by measuring the static pressure at the hydrant when the flow (Q) is equal to zero. Q = 0 gpm H = 90psi or 207.9 feet of head (90 * 2.31) (2.31 is the conversion factor used to convert psi to feet of head). 2. The engineer chooses a pressure for the second point, and the flow is calculated using the Formula below. The value for Q should lie somewhere between the data collected from the test. Q = ? H = 55 psi or 127.05 feet (55 * 2.31) (chosen value) Formula: Qr = Qf * (Hr/Hf)^.54 Qr = 800 * [((90 - 55) / (90 - 22))^.54] Qr = 800 * [(35 / 68)^.54] Qr = 800 * [.514^.54] Qr = 800 * .69 Qr = 558 Therefore, Q = 558 gpm 3. The third point is generated by measuring the flow (Q) and the residual pressure of the hydrant. Q = 800 gpm H = 22 psi or 50.82 ft. of head (22 * 2.31) Pump curve values for this example: Head (ft.) Discharge (gpm) 207.9 0 127.05 558 50.82 800 Setting up the Model To set up the model, you will enter the pump curve just developed, lay out the model elements, and enter their attributes within your project area. 1. Open your model in WaterCAD/WaterGEMS (or open the existing model if you have already laid out the elements for the new system) and go to Components > Pump Definitions. 2. In the Pump Definitions Manager, click the "New" button and name your pump definition appropriately (such as "Connection"). 3. Keep the default Pump Definition Type of "Standard (3 point)" and enter your data in the table: 4. Click the "Close" button to accept the curve, which we will use further below. 5. Now lay out the elements in the model (if this is not already done). You will need a reservoir and pump, which represents the connection to an existing system. 6. To adjust the attributes of these elements, first double-click the reservoir node to open the properties grid. For the "Elevation" attribute, enter the elevation of the pressure gauge used at the hydrant. Note that the pipe connecting the reservoir to the pump which be such that the hydraulic impact is negligible. For example, a Roughness of 140, length of 1 foot, and diameter of 48 inches are appropriate values. 7. Click the junction immediately downstream of the pump. This point represents where the proposed system begins, so enter the elevation of the connection point. 8. Click the pump element and enter the pressure gauge elevation as the "Elevation" attribute, which should be slightly higher than the reservoir. Select the pump definition you created in the previous section from the "Pump Definition" dropdown. 9. Make sure the rest of the system is set of correctly and compute the model. The pump should react according to the proposed system demands to provide an approximation of head at the connection point. Assumptions and Limitations This approach is an approximation, the accuracy of which depends on a number of factors . It is better to model all the way back to the source, at least by obtaining skeletonized data on the existing system. The skeletal model must begin at the real water source(s), such as the pump or tank, which will serve as the primary water source(s) for the new extension pipes. It should be calibrated using the results of fire hydrant flow tests, especially the tests conducted near the location where the new extension will tie in. You may need to call the municipality to obtain basic information on the existing system. Using the pump approximation method can present problems because this approximation of the existing system only accounts for the exact boundary conditions and demands that existed at the time that the test was run (for example, the afternoon on an average day with one pump on at the source). Basically, the simulated connection is only valid for the conditions present during the hydrant tests. Therefore, determining the effect of changing any of the demands or boundary conditions is difficult. An extended period simulation (EPS) that is performed using the pump approximation method will be less accurate and may not provide reliable data regarding projected changes in consumption. The pump approximation approach only works well if the existing system is fairly built-out near the connection point and the demand and operation conditions are expected to remain essentially the same in the long run. The hydrant flow test is useful for predicting changes in pressure when downstream demands change, but not for evaluating other types of system changes such as the addition of new pipes, or operational alternatives such as fire pumps starting up. Modeling more than one connection between the proposed expansion and the existing system may not be a valid approach. Some reasons for this are, first, the hydrant tests were most likely done at different times, yet the model will allow water to be taken from both sources at the same time. This is not accurate because in reality, both sources will not be able to provide the full observed residual pressure when open at the same time. In other words, if hydrants or connections were really opened at both connection points simultaneously, the combined flow would result in a much reduced residual pressure at both locations versus what was observed during the independent tests. Secondly, in some cases, depending on the hydraulic grades, it may be possible for flow to enter at one connection point and exit at another. However, the pump element only allows water in the forward direction, so the pump approximation method would not work in this case (and may provide a message about one of the pumps not being able to deliver head). The situation is too complex to model using a method other that a skeletonized representation of the larger system. However, if you are modeling a system where the upstream system will not experience a significant change in pressure as a result of multiple connections flowing at the same time, or if there are separate, disconnected systems upstream of each connection point, modeling multiple connection point may be fine. As the size of the modeled system increases and the number of connection points increases, it may not be reasonable to separate the development site from the rest of the system and achieve accurate results. The interactions may be too complex. One suggestion in this case is to get together with the City water distribution engineers and discuss how to model this. Ideally you would get a copy of the City model (at least the pressure zone of interest) and build your model on top of it. Or you can get their distribution maps and build very simple skeletal model of the system. You need to model back to some real boundary condition. One, somewhat far fetched, test might be to run (assuming you have 6 connection points) 6 simultaneous flow tests. You couldn't run all the hydrants wide open (unless you have a very strong system) without lowering the pressure too much. So, if your demand is 1800 gpm for example, you could run 300 gpm at each flowed hydrant. This isn't as good as running a model of the full pressure zone but at least it gives you an idea of what a 1800 gpm demand will do to the City system. Attempting to compute the 'static' (no demand) conditions of the new model with the pump approximation in place will most likely result in an unbalanced simulation . In this case, you may need to model the connection simply as a reservoir with an elevation equal to the pressure gauge elevation and static pressure head (i.e., the static HGL), or simply manually compute the static pressure at each node by taking the difference between the static HGL and the node physical elevation.

Applies To Product(s): Bentley Pondpack Version(s): V8i Environment: N/A Area: N/A Original Author: Jesse Dringoli, Bentley Technical Support Group What happened to the subarea and hydrograph queue node elements? In previous versions of PondPack, the user could use the "Hydrograph Queue" element to inject a user defined hydrograph. The "Subarea" element was used to represent drainage areas. The functionality of these elements are now included in the Catchment element in PondPack V8i. A catchment is a polygon representation of your drainage area, using a certain runoff method (such as Unit hydrograph). To model a hydrograph queue node (user defined hydrograph), you would select "user defined hydrograph" as the Runoff Method, then enter your hydrograph using a table of time vs. flow. Your user defined hydrograph would then be injected into the system, at the point identified in the catchment "outflow node" property. Where is the "add link" element? (black line) In previous versions, the "Add link" element was used to direct outflow from one node to another. The Add Link is no longer an element in V8i. To connect a catchment to the rest of the model, you would simply select the appropriate element for the "outflow node" property of the catchment. You'll then observe a dashed line connecting the center of the catchment to the discharge point. Aside from catchments, the equivalent of the add link tool in V8i would be to use the "conduit" element, selecting "virtual" as the conduit type in the conduit properties. This would instantly carry the upstream hydrograph to the downstream node without attenuation (which is what the add link tool did in older versions). For example, Catchment > Junction > conduit (set to Virtual) > Outfall > Pond. What happened to the pond route? What do I have to do now to model my pond outlet structure? In previous versions, the pond outlet structure was designated by the red "pond route" link tool, which directly connected to the pond node. However, in V8i, ponds are polygons. So, the Pond Outlet Entrance node is used to identify and place an icon at the point within the pond where the outlet structure is located. A link element called a Pond Outlet is then connected to the Pond Outlet Entrance. The Pond Outlet link will then connect to the element that the pond outlet structure discharges to. For example, Pond > Pond Outlet Entrance > Pond Outlet link > Outfall. The outlet structure is created under Components > Composite Outlet Structures. Your composite outlet structure is then assigned to the pond outlet link, not the pond outlet entrance. In the properties of the pond outlet, select "Yes" for "Has Control Structure?" then select your composite outlet structure from the drop-down next to the "Composite Outlet Structure" field. What happened to the reach route? How do I model a channel in V8i? In previous versions, the "Reach" element was used to attenuate a hydrograph, typically over a length of channel or some other cross sectional geometry. The reach link is now called a "conduit". The conduit link element can be configured as many different shapes, such as irregular channel or circular pipe, and will attenuate flow. It is important to understand that the water surface elevation in the channel does not affect upstream elements. For example, if your pond empties into a channel that could back up and eventually cause reverse flow into the pond, you'll need to use another modeling approach. What happened to the Catalog Explorer? In previous versions, the Catalog Explorer was used to define and store reusable information, particularly storm events. Global library information previously seen in the "catalog explorer" is now found in the Engineering Libraries. Go to Components > Engineering Libraries to view the engineering library manager. A variety of information can be exported to and imported from the various engineering libraries available. For example, the purple book icon under Components > Storm Data is used to export and import storm information to/from the Storm Event Groups engineering library. Storm events would not be created directly in the engineering library manager. You storm event is created under Components > Storm Data. When done, you can export the storm data to the engineering libraries. When you need to use it in other models, simply import from that library, in the Storm Data dialog. Did the model layout representation change from schematic to scaled? Yes - the elements of your detention pond model can now be drawn to scale. In previous versions of Pondpack, the network layout was a schematic, with nodes and links defining connectivity only. For example, catchments and ponds are now drawn as polygons and Pondpack V8i computes the area of the polygon based on its shape and size. The length of a conduit is based on the distance between its end nodes. Note however that you can override these scaled areas and lengths with user defined lengths if you'd like, irrespective of the length/size seen in the drawing pane. You can also place a background such as a DXF or shapefile, using View > background layers. This can be helpful so that you lay your elements out in the correct scale by tracing over the background. Is the scaled area of my pond polygon automatically used in the volume calculation? No - although the scaled area is used for catchments, the ponds represent three-dimensional space, to occupy volume. So, you must still define the pond using one of the volume methods such as elevation-area or elevation-volume tables. The scaled area of the pond can be useful as a reference, for the top pond elevation value. Is there an easier way to lay out a schematic representation of my pond or catchment? Yes - hold down your CTRL key on your keyboard, left click in the drawing pane, move your mouse slightly, then left click again. This will lay out a pentagon shaped polygon for your pond or catchment. If you are using this method to represent a schematic of your catchment (the area not correlated with the area of the polygon), make sure you choose "false" for "Use Scaled Area" in the catchment properties, then enter the area in the "Area (User Defined)" field. Has there been a change to the hydraulic calculation engine between V10 and V8i? Should I expect to get comparable results between the two versions? Although the user interface and features in Pondpack V8i are quite different from previous versions, the basic hydraulic calculation engine is essentially the same. The equations and calculations used and how they are applied have not changed. Why is it called "V8i"? Hasn't there already been a Pondpack V8? Although there has indeed already been a Pondpack 8.0 (circa ~2003), Pondpack V8i integrates with Bentley's V8i product line (Microstation V8i, Projectwise V8i), so the versioning was kept consistent. Can I open models saved in older versions? Yes. Pondpack V8i can directly open models saved in version 6.1, 7.0, 7.5, 8.0, 9.0, 10.0 and 10.1, using File > Open. The scenario, alternatives, storm events, etc necessary for you to compute multiple return events will be imported automatically. Can I open V8i models in previous versions? No - Pondpack V10 is not forwards compatible. Once your model is saved in V8i, you cannot open it in previous versions. There is no method to "save down" to the older version. Does a user-defined hydrograph count toward my pond limit? In previous versions of Pondpack, the hydrograph queue node element represented a user-defined hydrograph and would count as a pond (when checking the pond limit in your license). In Pondpack V8i, the user defined hydrograph option for a catchment does not count toward the pond limit. The system requirements state that AutoCAD 2009 is supported, but a shortcut is not being created for me. Why not? The Pondpack for AutoCAD 2009 shortcut is located in the installation folder. Typically this is C:\Program Files\Bentley\Pondpack8\. You can move this shortcut file to your desktop or start menu folder for easier access. Why do I get a message that there is no valid Pondpack for AutoCAD license, when opening the Pondpack for AutoCAD shortcut? The use of Pondpack inside of AutoCAD requires the AutoCAD module in your license. You are always able to use Pondpack in Standalone and inside of Microstation, but AutoCAD integration is an extra cost. Please contact Bentley's sales department for more information on adding AutoCAD to your license. If you do have AutoCAD in your license or if you're not sure, go to Start > All Programs > Bentley > Pondpack > Municipal License Administrator. Look in the features column next to Bentley Pondpack to see if AutoCAD is included with your license. To ensure that license is configured, click the Bentley Pondpack row and click "make default". Why isn't Windows 2000 a supported Operating System? This is due to the fact that PondPack V8i requires a Windows component called Microsoft .NET Framework. The version of .NET framework required by this version of PondPack is 3.5, which Windows 2000 does not support. Therefore, PondPack V8i cannot run in Windows 2000. What is the purpose of these "Scenarios" and "alternatives"? A scenario is a collection or configuration of alternatives, which describe various characteristics of your model. For example, the physical property information (such as channel invert) is stored in the Physical alternative but the outfall tailwater information (free outfall, time-elevation curve, etc) is stored in the Boundary Condition alternative. Each scenario can use a different configuration of alternatives, which allows you to compute multiple "what if" situations in the same model file. For example, you could analyze the differences between having a 10" conduit versus a 16" conduit for the same return event, by using different physical alternatives in the two scenarios. When you make a change to your model, it changes the data in the appropriate alternative assigned to the scenario you are currently viewing. The other common use of scenarios and alternatives is to examine multiple return events. The Rainfall Runoff alternative stores the storm event selection, so if you'd like to examine multiple return events (for example, 10, 50, 100 year), you would set up a scenario for each one. Each scenario would use its own rainfall runoff alternatives, each configured with the appropriate storm event. Note: a special scenario creation tool is included in PondPack V8i, to make it easier to create scenarios for predeveloped/postdeveloped conditions and for multiple return events. This tool will appear when you first create a project and is also available within the Scenario manager. How can I use the Active Topology feature/alternative? The active topology alternative stores information on which elements are active and which are inactive. Inactive elements are not considered when you compute the model, as if you had deleted them. Inactive elements are colored gray by default but you can configure them to disappear from view. One example of a case where you might want to use active topology would be predevelopment versus postdevelopment. Meaning, you may need to compute an area in it's pre-developed conditions and then compute it after development occurs. Your postdevelopment scenario might have an active pond and several "developed" catchments, whereas the predeveloped scenario would likely not have a pond and the catchment would describe undeveloped conditions. In previous versions, the user would either need to create two separate models, or two separate networks in the same model to describe these conditions. In V8i, you would use a single model with multiple scenarios to describe this. The postdeveloped scenario's active topology alternative would describe the pond and developed subareas being active, whereas the predeveloped scenario's active topology alternative would have those elements inactive, with only the elements present in the predeveloped conditions active. Note that if you're using the modified rational method, there is no need to create separate pre/post scenarios. This is because both the pre and post conditions are handles in the modified rational catchment. You'll still need to create separate scenarios for each return event though. When I make an element inactive, it still shows up in gray. Can I have inactive elements disappear instead? Yes. This is controlled under Tools > Options > Global. If you'd like inactive elements to disappear from view, uncheck "Display Inactive Topology?". Unchecking this option is recommended and will results in a more intuitive model display in most cases. Keeping this option checked will remind you of the elements that are no longer active though. Why am I being asked if I'd like to create pre/post scenarios, when starting a new model? The pre/post scenario creation wizard allows you to quickly generate the scenarios and alternatives necessary to analyze pre and postdeveloped conditions for multiple return events in the same model. If you choose not to use this, you'll need to manually set up your scenarios and alternatives. What is the workflow for setting up pre and postdeveloped conditions for multiple return events? 1) Choose "yes" when asked if you'd like to create pre/post scenarios upon creating the model, or select this tool from the "new" button in the scenario manager. 2) Enter labels for pre/post scenarios and list the return events to be analyzed. 3) After the scenarios and alternatives are generated, go to Components > Storm Data and either create or import your storm events. 4) Go to Components > Global Storm Data and select the storm events corresponding to each return event. 5) Select one of your predeveloped scenarios as the active/current scenario and lay out or import the predeveloped conditions (for example, a catchment going to an outfall.) 6) Select one of your postdeveloped scenarios as active/current and lay out the postdeveloped conditions. The elements you lay out while in the postdeveloped scenario will be inactive in the predoeveloped scenarios. 7) If the elements from the predeveloped scenarios are different in the postdeveloped scenario, make the necessary changes. For example, if the Tc is different, make the change while in your postdeveloped scenario - the predeveloped Tc will remain intact for the predeveloped scenarios. If an element from the predeveloped conditions should be gone in the postdeveloped conditions, make the element inactive using the "is active?" property or the Active Topology Selection tool under the Tools menu. For example, if you have a catchment called "pre conditions" in the predeveloped scenario, but that catchment has a different shape in the postdeveloped conditions and should be named "post conditions", then make the "pre conditions" catchment inactive in the postdeveloped scenario, then lay out and configure the "post conditions" catchment. Since the default active topology setting is Inactive and since the predeveloped scenarios use a different active topology alternative, the "post conditions" catchment will be inactive in the predeveloped scenario and thus not considered in the calculations. What do I have to do to compute multiple return events at once? In previous versions, you could select multiple return events in the Compute dialog and Pondpack would run multiple simulations at once. In V8i, the concept of Scenarios and Alternatives is used, and you must use the Rainfall alternative to handle this. Each return event is described in a rainfall alternative, and each scenario only has one rainfall alternative assigned to it. So, to compute multiple return events, you must create multiple Scenarios, each with the appropriate rainfall alternative assigned (and the other alternatives all the same). You can then compute all scenarios at once, using the Batch run feature. This is found in the compute dropdown button in the Scenario manager (Analysis > Scenarios). An easier way to set up your model to analyze multiple return events would be to use the Scenario Creation wizard. This will create the scenarios and alternatives for you automatically. Either choose "yes" to the prompt that normally appears when first creating a model, or go to Analysis > Scenarios, click the "new" button and choose "New pre/post development scenarios". If you're not doing a pre/post analysis and simply want to create the scenarios and alternatives necessary to analyze multiple return events, then select "Post development only" as the scenario creation type and enter a label for your scenarios. In the table at the bottom, enter a label for each return event you'd like to analyze. When you click create, Pondpack will create a scenario for each return event, each with its own rainfall runoff alternative. To tell Pondpack which storm is used for which scenario, first create or import your storms under Components > Storm Data. Once done, go to Components > Global Storm Data. In here, you will see an alternative corresponding to each return event (based on the labels you had chosen). Select the corresponding storm event next to each one. Note: If you have opened a model saved in a previous version (such as 10.0), you do not need to set up the scenarios and alternatives for multiple return events. These will all be imported for you - simply run a batch in the scenario manager to compute multiple return events. What if I use the pre/post scenario creation tool but want to go back and add another return event? If you had used the Pre/Post Scenario Creation tool at some point in the past, but later want to add another return event, you'll need to add a new rainfall runoff alternative and two new scenarios. First, go to Analysis > Alternatives and expand the Rainfall Runoff Alternative. Right click on the base rainfall runoff alternative, choose New > Child Alternative and give it a name corresponding to your new return event. For example, you may already have a '10 year' base alternative with '25 year' and '100 year' child scenarios. If you were adding the 50 year scenario as a child to the 10 year, it would show up on the same 'level' as the 25 and 100. Next, click Analysis > Scenarios, right click the base predeveloped scenario, choose New > Child scenario and name it appropriately. Double click the new scenario and assign the newly created rainfall runoff alternative. For example, if you had just added a 50-year rainfall runoff alternative, select it as the "rainfall runoff" alternative for your new predeveloped 50 year scenario. Next, right click the base postdeveloped scenario, choose New > Child scenario and name it appropriately. Just like with the new predeveloped scenario, double click the new postdeveloped scenario and assign the newly created rainfall runoff alternative. Next, if you have not done so already, import or create your new return event's storm data, under Components > Storm Data. Lastly, Go to Components > Global Storm Data and select the new storm event for the newly created rainfall runoff alternative. How can I import storm information from the catalog explorer of old versions? In previous versions, storm information such as rainfall curves, IDF curves, design storms, etc could be stored in the catalog explorer. This allowed the user to reuse these storms in any project. When you open a V9/10 model in V8i, any storm information saved in it will be imported. You can then export that information to V8i's engineering library for future use. To import storm information stored in V10's catalog explorer but not stored in any V10 model file, go to File > Import > Pondpack 9/10 Engineering library data. You will now need to browse to the .xml file, which stores the catalog explorer data that you wish to convert to V8i. This is the file cabinet icon seen in V9/10. If you are not sure where your xml file is located, open Pondpack V9/10, right click on the file cabinet representing the library item in question (in the catalog explorer) and choose "properties". The path to the .xml file will be displayed. After selecting the v9/10 XML file, you will then be prompted for a location to save the V8i format engineering library file. Choose a safe location and click OK. The library will be automatically registered in V8i's Engineering Library manager, so you can now begin using it with your projects.If you encounter a second prompt stating that a reference library cannot be found, then you are likely importing a design storm catalog, which references one or more rainfall curve catalogs. In this case, you'll need to click "Yes" and browse to the folder where the rainfall curve catalog XML file is located. How can I reuse storm information in subsequent projects, like with the catalog explorer of previous versions? To do this, first create the storm information for your locale, under Components > Storm Data. For example, create a new Time-Depth storm event group, with a 2, 10, 50 and 100 year storm events within it. Then, click the name of the storm event group on the left side, click the purple book icon and choose to export to library. If you'd like to be able to share your storm collections, it is recommended that you create a new library to store them. To do this, right click on "Storm Event Groups" in the engineering libraries window, choose "create library", then save the .xml file in a safe location. Click the name of that library and click the "select" button to export your storms to your engineering library. This is equivalent to the Design Storm section of the Catalog Explorer in previous versions. Now, if you need to use these storms again in another model, first go to Components > Storm data. Then, click the purple book icon and choose "import from library". Lastly, expand the name of your engineering library XML file, select your storm and click "select". Your storms will appear in the Storm Data window and can now be used in your model. If you'd like to share your standard storm event groups, simply copy the .XML file that you had saved, to a safe folder on the other computer. Then, inside Pondpack on that computer, go to Components > Engineering libraries. Click "new" > "Add Existing" and browse to the XML file. The storms will now be available for import in the Storm Data dialog. Note that if you use Bentley Projectwise, you can elect to store engineering library data there, for access on multiple computers. To do this, first copy the XML file to Projectwise. Then in Pondpack on each computer, click Components > Engineering Libraries. Click New > Projectwise Add Existing Library, then connect to Projectwise and browse to the XML file. How can I apply a rainfall depth to a dimensionless curve to create a storm event? First go to Components > Storm Data. Click the new button and select "Time-Depth" or "Time-Intensity" and provide a name for your storm event group (equivalent to the "Design Storm" in previous versions). On the right side, click the new button and select "Add return event from dimensionless curve". In the window that appears, expand the library of choice and select your dimensionless rainfall curve. If you need to create a custom one first, you can do so under Components > Engineering libraries. In the "generate storm event" window that appears next, provide a label, return frequency, total depth, etc and click OK. Your time-depth or time-intensity event will be constructed based on the entered depth and dimensionless distribution. I placed an outfall on top of a pond but the flow doesn't seem to be entering the pond, or I get a message that the pond is not connected to an upstream element. Why? By default, the outfall element will be configured as free outfall. This means that upstream flow reaching the outfall will leave the system. If you need to have the upstream flow empty into a pond, ensure that you select "boundary element" as the outfall's boundary condition type, then pick your pond as the "boundary element". How do I view my results? There are many ways to view results: 1) In the calculation summary after computing the model, core result information such as the hydrograph volume , peak flow and max water surface elevation are shown. You can get back to this under Analysis > Calculation Summary. 2) The Report Builder tool seen in previous versions is still available, either by clicking the "report" button in the calculation summary or by going to Report > Report builder. This contains copious amounts of text results and calculation related information. 3) Graphs can be generated for many results, under View > Graph or by selecting your element(s) and choosing "graph" under the right click menu. For example click a pond, hold down the CTRL key, click another pond, right click the pond and choose graph. 4) The Properties window shows results for a particular timestep, for any element. For example, go to Analysis > EPS Results browser and select a timestep. Double click an outfall in your drawing to open the properties window. Under the "Results" section of the properties, you'll see the elevation and flow for that timestep, as well as other information. 5) Flextables are a convenient way to show information for many elements at the same time, in tabular form. For example go to View > Flextables and double click the Catchment Table. Click the yellow edit button at the top of the Catchment table and configure which fields you'd like to see. When done, you'll have a table of your catchments, showing the results you'd like to see. How do I display a time series of an attribute such as time vs. elevation for multiple return events in the same graph? First, compute all scenarios desired. Then create a graph of the element(s) in question. For example, right click a pond, choose "Graph" and select the attributes you'd like to graph. In the graph series options window, you will also see a Scenarios section on left side. Select all the scenarios you'd like to graph that attribute for by clicking the check boxes. When you click OK, you will see a graph of those attributes, for all the scenarios specified. When you're viewing the graph, you can get back to the series options by clicking the button at the top or using right click > graph series options. Can I customize the properties window to only show fields I'm interested in? Yes. By default, Pondpack will show many attributes in the properties window of your elements and you may want to reduce clutter and show just the fields you're concerned with. Pondpack V8i includes some default customizations for common modeling situations, which can help this. For example, select "Basic Results (Predefined)" from the dropdown menu at the top of the properties window to see only basic results fields. You can also create your own customizations to show the fields you want. To do this, go to View > Customizations. Create a new customization and select which attributes you'd like to show in the properties for each element type. Then, select your customization from the dropdown at the top of the properties window to apply the filter. How can I show multiple scenarios / return events in the Master Network Summary? First, either compute the desired scenarios one by one, or perform a batch run in the scenario manager. Then, go to Report > Report builder. In the Scenario Selection window that appears, place a check in the box next to the scenarios you'd like included in the report, then click OK. Now when you view the Master Network Summary, it will include results for all the scenarios you selected. Is it possible to view old-style text reports? https://communities.bentley.com/products/hydraulics___hydrology/w/hydraulics_and_hydrology__wiki/12667.is-it-possible-to-create-old-pondpack-style-text-reports.aspx How can I print just the rating curve plot for my outlet structure? In the composite outlet structure manager, the report button provides a full report of both the rating tables and curves. To print only a particular rating curve graph, right click on the X axis of that graph, choose "graph properties" and click the print tab. Report Builder has so many reports. Can I customize which ones show? Yes. In the Report Builder window, click the Report Filter button (funnel icon). Click the new button to create a new filter, name it, then double click to configure it. In this window, use the check boxes to select which reports you'd like to see. You can create multiple filters depending on the types of results you're interested in. Back in the main Report Builder window, select your report filter from the dropdown to filter the available reports. Once I set up my report filter the way I like it, how can I share it with my colleagues so they have the same filter? In the Report Builder window, click the report filter button, then click the export button. Choose a location and name, then save the .xml file. Send this file to your colleague's computer. In their Pondpack, click the "import" button in the report filter window and select the .xml file to import the filters. How can I view the cross section and rating curve of a channel/conduit? First, lay out the conduit and configure its properties. Either enter a user defined shape or select from the conduit catalog. Make sure to enter the conduit's elevation data. Right click on the conduit from the drawing pane, choose "Channel rating curve" and the rating curve and cross section will be computed and displayed. The window that opens has a dropdown selection to view the cross section drawing, rating curve (elev vs. flow) and other various useful graphs. Which end of the conduit do the "Flow" and "Elevation" result fields refer to? The "Elevation" result field shows the elevation at the upstream end of the conduit. The "Flow" result field shows the Flow at the downstream end of the conduit. What is the difference between a "composite outlet structure" and an "outlet structure"? The composite outlet structure refers to a collection of individual structures acting as the pond outlet. For example, composite outlet X may consist of an orifice and a weir. The composite outlet structure is what you assign to the pond outlet link, which tells Pondpack to use that 'composite' collection of structures as the pond outlet discharging to the element downstream of the outlet link. Do I still have the option of having Pondpack use stored EQT tables for ICPM outlets? Yes. In previous versions, a check box was available in the pond route properties, to "Use EQT table?". This option allowed the user to compute the EQTW table for the individual outlet structure first and then have Pondpack re-use that table during the full network calculations, instead of re-computing it. This feature saves on calculation time and is still possible in V8i, using these steps: 1) Go to Components > Composite Outlet Structures and create your composite outlet structure. A tailwater type of "Interconnected ponds" must be selected to use EQTW curves. 2) Click the name of your composite outlet structure and choose "Yes" for the "Store Elevation-Flow-Tailwater table?" property. 3) Select "Create new EQTW series" for the "Elevation-Flow-Tailwater" field. 4) Compute the EQTW rating curve by clicking the green compute arrow at the top. After calculation, the EQTW table will be stored in the Elevation-Flow-Tailwater manager. 5) Close the Composite Outlet Structure manager and look at the properties of your pond outlet link. 6) Select "No" for the "Has control structure?" field, "Yes" for "Use Elevation-Flow-Tailwater Table?" and select the EQTW table entry from the "Elevation-Flow-Tailwater Table" field. Now when you compute your model, it will use the stored EQTW table instead of recalculating it. Why do I not see progress details when computing an outlet rating curve or ICPM model? For large and/or complex composite outlet structures, it may take a while to compute the rating curve. For large models with ICPM pond routes, it may take a while to compute the ICPM routing. By default, no detailed progress indicator is shown. To enable the display of these details, select "true" for the "Show status" field in the calculation options for your active scenario (Analysis > Calculation options). Then, when you compute the outlet rating curve, you'll see calculation progress (current tailwater elevation, headwater elevation, convergence, etc.) Note: enabling the display of calculation status will typically cause an increase in runtime. How does the new Vortex Valve outlet structure element work? Vortex valves are a type of outlet structure used in some ponds. They have a unique rating curve, which may help reduce the require storage volume, when compared to other outlet structure types. In Pondpack V8i, they are essentially handled as user-defined rating curve outlet structure types, but can be stored in an engineering library. Meaning, they are a defined relationship between the pond water surface and the corresponding outlet structure discharge. First, you must either construct the vortex valve rating curve under Components > Vortex Valves (you can copy/paste the data from manufacturer documentation), or import from a library (some default HydroInternational vortex valves are included). Then, in the Composite Outlet Structure manager, right click your composite outlet structure, choose new > vortex valve. In the properties of the vortex valve entry, select your vortex valve from the "Vortex Valve" dropdown and enter an "Elevation". The "head" values in your vortex valve rating curve are depths above the "Elevation" that you enter. For example, say that the flow at a "head" of 1.0ft on your vortex valve rating curve is 2cfs and you enter 995ft as the "elevation". This means that when the water surface of the pond is 996ft, the flow out of this outlet structure will be 2cfs. Note: Be careful when using vortex valves in an interconnected pond scenario; the rating curves assume a free outfall. In step 1 of Pondmaker, what does the "design scenario" and "target scenario" represent? The Design scenario represents the scenario which you are designing the pond for. It is typically the Post-development conditions, where catchment runoff is higher than the predevelopment conditions. The Target scenario (when using scenario as the target flow/volume source type) should be the scenario describing the conditions that your pond will be designed to reduce flows down to. So, it is typically the "predevelopment" scenario for the same return event. You will design the pond and outlet to attenuate the peak flow from the Design scenario down to the target value from the Target scenario. When using the modified rational method, what is the difference between using "Scenario" versus "Modified Rational Catchment" as the "Target Flow/Volume Source" in step 1 of Pondmaker? Under normal circumstances you should use the "Modified Rational Catchment" as the "Target Flow/Volume Source", when using the Modified Rational method. When doing this and selecting your modified rational catchment as the target element, Pondmaker uses the predeveloped peak from that catchment as the target peak flow to design against. This is based on the Predevelopment Tc, Predeveloped C and Predevelopment area (if the outflow criteria is set to Pre-Development) or the "Target" flow (if the outflow criteria is set to User Defined) entered in the catchment properties. If you choose "Scenario" as the "Target Flow/Volume Source", the target peak flow that your design will be based on will come from the computed peak of the hydrograph at the select target element, in the selected scenario. In this case, you would not want to select the same scenario as your design scenario, with the modified rational catchment as the target element. This is because the hydrograph in that scenario, at that element would be the design/peak flow, not the target/allowable flow. One possible reason for using "scenario" as the target flow/volume source would be if you had a scenario using the custom critical Td option to mimic existing/predevelopment conditions for the modified rational runoff hydrograph. What do all those lines represent, in the graph seen in steps 4 and 5 of Pondmaker? The bold blue line represents the rating curve of the outlet structure you computed. The horizontal dashed lines represent the estimated water surface elevations for each of your return events. Each of these has an orange dot, corresponding to the target peak outflow that you're designing for. The orange line connects these dots, so it is the target rating curve. Basically this is a good way to visualize how close your trial outlet structure is at achieving your design goal for each return event. The goal is to get the blue outlet rating curve as close as possible to the orange target rating curve. When you tweak your outlet structure and click the green compute button, the outlet rating curve will update, to give you a good visual idea of how well the adjustment was. What is the purpose of the "Computed Outflow Volume vs. Target" field in Pondmaker? This field will show you if your designed pond and outlet are able to reduce the total pond outflow volume to be within the tolerances of the total outflow volume in the target (typically pre-development) condition. If you do not use infiltration with your pond, the computed outflow volume is going to be the same as the total inflow volume before implementing the pond. This is because the pond only attenuates the flow - the same mass of water still flows out of it. So, you may not need to be concerned with this field, unless you are required to reduce the outflow volume by way of infiltration. In the routing step of Pondmaker, if you'd like to implement infiltration to reduce the outflow volume, first go back to step 3 (pond dimensions) and select your infiltration method. Then, click back to the routing step and compute it. Note: the pond dimensions and outlet design steps of Pondmaker will not account for infiltration. I don't like the way the report looks in Pondmaker. What options do I have? You can easily export the worksheet data for the Design and Routing tabs to another program, such as Microsoft Excel. To do this, click the Design or Routing tab, then click the blank gray cell at the upper left corner to select the entire table. Press CTRL+C on your keyboard to copy the data into clipboard. Then, open your external application and paste the data in. You can format the table the way you'd like it, then print. For the various graphs available in the Pondmaker process, you can right click the X axis, choose "graph properties", click the "print" tab and print from there. Can I still choose to store computed hydrographs? Yes. In previous versions of Pondpack, the user would click a check box in the Compute dialog, to tell Pondpack that the hydrographs computed during the simulation should also be stored in the hydrograph manager. To do this in Pondpack V8i, go to Analysis > Calculation Options and double click the calculation option set associated with the scenario in question (designated by the red check mark). In the properties window, select "True" for "Store Hydrographs (as input)". Then, when you compute your model, the hydrographs will be stored under Components > Hydrographs > Hydrographs. If you'd like to use these stored hydrographs as input, first lay out a catchment and specify the outflow node that the hydrograph will discharge to. In the properties of the catchment, select "user defined hydrograph" as the "Runoff method". Then, click the dropdown next to the "Hydrograph" field and select the hydrograph from the hydrograph manager that you'd like to inject into the system. Where do I find Pond Volume Results? https://communities.bentley.com/products/hydraulics___hydrology/w/hydraulics_and_hydrology__wiki/12905.where-do-i-find-pond-results-like-elevation-vs-volume.aspx See Also Product TechNotes and FAQs Licensing TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs External Links Bentley Technical Support KnowledgeBase Bentley LEARN Server

Applies To Product(s): Bentley SewerGEMS, CivilStorm Version(s): 08.11.XX.XX Environment: N/A Area: Modeling Subarea: Original Author: Jesse Dringoli, Bentley Technical Support Group Problem When using the Implicit dynamic solver, I can use a conduit between a wetwell and a pump. With the GVF Convex solver, I'm forced to use a pressure pipe in this case. Why? Solution This is mainly a technical limitation due to the numerical solvers running behind the scenes. The GVF Convex (SewerCAD) solver calculates pressure networks separately using the EPANET engine where all pipes are assumed to be full, so a pressure pipe is expected. With the implicit dynamic solver, all parts of the network (both pressure and open flow/gravity) are solved at the same time, by the same solver. The Preissmann slot method is used to simulate pressurized flow in both pressure pipes and conduits. For compatibility between solvers, it may be best to use pressure pipes. Both conduits and pressure pipes can be designated as "virtual" as well (no hydraulic significance - flow in=flow out) for cases such as submersible pumps.

Applies To Product(s): Bentley WaterCAD, Bentley WaterGEMS, Bentley SewerGEMS, Bentley SewerCAD, Bentley CivilStorm, Bentley StormCAD, Bentley HAMMER Version(s): 08.11.xx.xx Environment: AutoCAD Area: Modeling Subarea: Original Author: Scott Kampa, Bentley Technical Support Group Problem Description The Properties menu or other manager windows are not opening in the AutoCAD platform for a Haestad Methods product. Steps to Resolve In the Standalone version of the products, using the Reset Workspace command will often resolves issues like this. Reset Workspace is not available in the AutoCAD platform. If the menu or manager window is not display, it may be pushed away from the drawing pane. It is possible to retrieve it though. In the AutoCAD platform, move your cursor to left of the drawing window until you see the cursor change to the one shown below: Click and drag your mouse back to the right. The manager should now appear. The appearance of the managers should remain like this unless you need to reinstall or reintegrate the products. For some missing managers, you may need to click on the right side of the drawing pane and move it to the left. For the case of user notifications, you would need to click the bottom of the drawing pane and drag it up. See Also Reset Workspace

Applies To Product(s): Bentley WaterGEMS Version(s): V8 XM and V8i Environment: N/A Area: Modeling Subarea: N/A Original Author: Scott Kampa, Bentley Technical Support Group Overview The purpose of this technote is to discuss common steps to calibrate a model using Darwin Calibrator in Bentley WaterGEMS. Additional information can be found in the WaterGEMS Help menu. Background In order to accurately model a water system, the user will often need to calibrate the model. Darwin Calibrator allows the user to calibrate a model either manually or, with efficient genetic algorithms, in a more automated fashion. It allows for multiple calibration candidates to be presented so the best possible solution to a given system can be found. Solutions can also be exported into a new scenario for use in an existing water system. Darwin Calibrator is included with a license for Bentley WaterGEMS V8i. Older licenses for WaterCAD allowed for the purchase of Darwin Calibrator as an add-on. This has been grandfathered in for these licenses. New purchases of WaterCAD will not see Darwin Calibrator available as an add-on; you would need to get WaterGEMS to use Darwin Calibrator. Note: Non-Select users will need to check out both WaterGEMS and Darwin Calibrator in order to use this tool. You can check out the license from the License Management Tool. Setting Up a Calibration Study In order to calibrate a model, Darwin Calibrator makes adjustments to the pipe roughness, demand, and/or element status. For this reason, the first step for any calibration study is to have a completed model with all demand and roughness data entered. With a completed model ready, you are set to start using Darwin Calibrator. You can open Calibrator by going to Analysis > Darwin Calibrator or by select the Darwin Calibrator icon. The Darwin Calibrator window will then open. To start a new calibrator study, select the New icon in the upper left and select New Calibrator Study. You will then see tabs and available features appear on the right part of the window. The next step is to create your adjustment groups. While you can also set up the field data snapshots, it is recommended that the adjustment groups are created first, rather than let available data determine how many adjustment groups to have. For clarity, the focus will be on creating roughness groups, though the general steps will be the same for demand groups and status groups. Go to the Roughness Groups tab. Click the New icon to create a new item. It is up to the engineer how many groups to create. The recommended workflow is to group elements that have similar characteristics such as age or material, since it can be assumed that two pipes of the same age or material will see similar changes to the actual roughness. To add elements to the roughness group, click the cell in the Element IDs column and select the ellipsis button. A new window will open. Choose the “Select from Drawing” icon. The Select toolbar will appear, allowing the modeler to choose elements from the drawing using a few different ways, including manual selection and query, among others. Once you have the elements selected, click the green check mark to complete the selection. You will now see the elements in the table. Click Okay to return to Darwin Calibrator. The selection of Demand and Status groups follow similar steps. Click the in the Demand Group or Status Element tab to select the elements. Note: Status Elements are used when a particular part of the system is believed to contain a closed valve or pipe. It is recommended that Status groups contain one or very few pipes. With the adjustment groups selected, now it is time to enter the field data snapshots. Return to the Field Data Snapshots tab. Make sure the representative scenario is set to the one to be used in the calibration study. Darwin Calibrator will pull results from a given scenario to compare to the adjusted values from the calibration study. Next, select the New icon below the Field Data Snapshot tab. You will see a new field data snapshot appear. Adjust the date/time information and identify a demand multiplier, if necessary. For example, if you have knowledge that your demand is higher or lower by a specific percentage, you can set that value here. The default value is 1. Next, the observed data for the field data snapshot will need to be entered. This is entered in the lower right of the window, below the Observed Data tab. With the field data snapshot highlighted, click the New button under the Observed Target tab. A new line will appear with the Element cell blank. Click inside the cell, and then click the ellipsis button. Select the element that you have the data for from the drawing, or use the Find option. Once you have selected the node, it will be available in the pulldown. With the node selected, the Attribute and Valve columns will be editable. Choose either Hydraulic Grade or Pressure for the attribute and then enter the appropriate value. Enter as many elements as you have field data for. If you have a field data snapshot for another time during the model run, you can create a new one with a different time. You can then enter observed data for this time as well. Next to the Observed Data tab is the Boundary Override tab. This is also important in a calibration study since it is possible that a tank level or pump/valve status is different from how it is depicted in the model. To get the most accurate results, applicable boundary overrides should be applied. Click the Boundary Override tab and select the New icon below the tab. A new item will appear. Select the element as before, keeping in mind that this should be a tank, valve, or pump. Depending on the element chosen, the Attribute field will offer different selections. For a tank, the Attribute can be either Hydraulic Grade or Tank Level. For pumps and valves, setting and status are the options. Again, enter the appropriate value for the attribute selected. Demand Adjustment is the last tab. This is used to adjust demand for individual elements, such as flow from a hydrant. Enter data here as necessary. Manual Calibration Run With the field data and boundary overrides entered, and the adjustments groups created, you are ready to run a calibration study. This section will discuss the manual calibration run. As before, the steps below will show a calibration study using roughness adjustment groups. Similar steps can be taken with demand groups. The manual calibration study allows the user to enter multipliers or set values to change the existing roughness coefficient, demand, or status to a new value. After computing the study, you can compare the simulated results to the field data entered that given time. To start a new manual run, click the New icon in the upper left and choose “New Manual Run”. A new item will appear below the calibration study label. On the right side of the window will be a series of tabs. In the roughness tab, you will see the roughness groups created earlier. To make a certain roughness group active, make sure the check box under “Is Active?” is checked. For the Operation column, choose either Multiply or Set, depending on which you wish to use. For Value, enter the appropriate value. Then click the Compute button. Note: Multiple manual runs can be created so that a number of values can be entered for the roughness. When completed a solution will appear that will include the results from the calibration study. Click “Solutions” directly under the manual run. This will display a fitness value for the solution or solutions. Fitness is a correlation between the observed data from the field data snapshot and the calculated value from the calibration study. The smaller the value, the better the fit. Returning to the left side of the window, click “Solution 1” to view the results. Under the Solution tab will be the adjusted roughness values for the pipes included in the calibration study. Under the Simulated Results tab will be the elements included in the field data snapshots. Columns for the observed data and the simulated data with the new roughness coefficients are presented, along with a column showing the difference between the observed and calculated values. Optimized Calibration Run The optimized calibration study uses a genetic algorithm to find the best possible solution available within certain parameters. The optimized calibration study has no true optimality and only knows the best solution relative to other solution already found during computation. However, the optimized calibration study runs through a large number of possible solutions and can often find a very good solution to fit the model. The process is similar to the manual run. Click the New icon in the upper left and choose New Optimized Run. Under the Roughness tab, you will see the roughness groups created earlier. To make a certain roughness group active, make sure the check box under “Is Active?” is checked. For the Operation column, choose either Multiply or Set, depending on which you wish to use. Instead of entering a new value manually for the roughness, you will enter minimum and maximum values, as well as an increment. Then click the Compute button. Darwin Calibrator will then try different values for roughness that fall within the values entered in the Roughness tab and compare the resulting values to the observed data from the field data snapshots. Darwin Calibrator will continue this until it finds the best solution available. The results are viewed just as the manual run, however there is an option to view as many as ten solutions. See the Tips section below for more information about this. Updating the Model If you are satisfied with the results, you can export the new roughness coefficients, demands, or status to a new physical alternative. To do this, highlight the solution you wish to export. The “Export to Scenario” icon will become active. Choose this icon and a new window will appear. To export to a new scenario, check the “Export to Scenario?” box. Do the same for the alternatives. With the check boxes selected the new results will be exported to new physical or demand alternatives (depending on the type of calibration study done). If you export to a scenario and do not export to an alternative (by unchecking the associated box or boxes), the data for that alternative type will be exported to the Base alternative. Note: The data in your original model will not change unless you use this export feature. Tips After computing a calibration study, you will sometimes see results that do not have a good fitness or do not make sense. Below are a few general tips to look at. More information on Darwin Calibrator can be found in the WaterGEMS Help documentation. Try running a manual calibration study with no adjustments to the roughness or demand. In other words, keep the multipliers for the adjustments groups at 1. Then look at the fitness. If you have a very high fitness number, this is an indication that something is wrong with the model setup. Review your model and make sure the results look reasonable and that no unusual user notifications are generated. Verify that the boundary overrides and demand adjustments are properly entered. This is very important since otherwise Darwin Calibrator will use values in the model at the times of the field data snapshots instead. Since the results in the model results might not be the same as what is actually occurring in the field, it is important to make these changes. Accurate data model-wide is important as well. Good, accurate data will mean the calibration study will work optimally. If you are computing an optimized run, you can change some of settings in the Options tab. Highlight the optimized run on the left side of the window, then choose the Options tab on the right. Detailed information for the options can be found in WaterGEMS Help. Changing the Maximum Trials and the Non-Improvement Generations items to higher values will allow Darwin Calibrator to try more adjustments and possibly find better solutions. You can also change the Fitness Tolerance and the Solutions to Keep. It is recommended that the Advanced Options remain set to the default values. Since Darwin Calibrator’s genetic algorithms can only compare a result to results that came before, making changes to the options can create new sets of solutions. It is recommended that you run several optimized runs even if the initial calibration study is good. A better solution might be generated after changing the parameters. WaterGEMS and WaterCAD also come with several sample models that have completed manual and/or optimized calibration studies. These are a good resources to see the general setup of a calibration study, and can allow you to calculated models and see how the results differ not only with between manual and optimized runs, but also in changing the options. The sample files can be found at the following file path. C:\Program Files (x86)\Bentley\WaterGEMS\Samples Example5.wtg is an example of calibration based on three hydrant flow tests done at different times of the day. The hydrant flow, pressure, and corresponding pump and tank status are shown in the Demand Adjustments, Observed Target, and Boundary Overrides tabs within the calibration study, respectively. Example4.wtg shows a system separated into DMAs, demonstrating the use of the Pump Station element. A Darwin Calibrator study is included, giving examples of calibration based on both static and residual hydrant flow tests. Optimized runs where both demand and roughness can be adjusted are included, along with examples of Manual runs where roughness and/or demands are adjusted manually. Example8.wtg is an example of a leakage detection study using Darwin Calibrator. Observed hydraulic grades at several different locations in the system have been entered, for several different times of the day. The "Detect leakage node" option is used in each of the optimized runs, to detect leakage node candidates by using emitters. Importing Field Data from SCADA A new option in WaterGEMS V8i SELECTseries 5 and later allows the user to import field data directly from your SCADA data right in Darwin Calibrator. You click the "Import Field Data from SCADA" button to do this. You can then select data to import into Darwin Calibrator. Note that there is no bulk import tool, but you can easily import representative data to use in model calibration. How do I match the results I am getting from Darwin Calibrator in my model? In order to match the results that you are getting from Simulated Results tab in Calibrator (see image below) you will need to do the following: 1. Make sure the scenario you are look at in your model is the representative scenario listed in the Field Data Snapshots tab 2. Make sure the calculation options (Analysis > Calculation Options) for your scenario are set to represent the field data snapshot you are looking at results for. Calibrator only calculates results for a steady state scenario at a particular time period that you specify in your field data snapshot so it only makes sense to set your model up to reflect this. In this example we are looking at the field data snapshot labeled “Flow Test 1” In your model you will need to set your calculation options as follows: Simulation Start Date = The same date listed in the field data snapshot Time Analysis Type = Steady State Is EPS Snapshot? = True Equivalent Hydraulic Time Step (hours) = 1.00 Start Time = The same time list in the field data snapshop Setting the calculation option for “Is EPS Snapshot? = True ensures that your model is going to use the pattern multiplier that Calibrator used when doing its calculations. 3. Make sure ALL the boundary overrides, for the particular field data snapshot you are looking at, are reflected that way in your model. For example, if you have pump PMP-1 set to a status of ON in your boundary overrides tab make sure your model has this pump set to a status of ON too. 4. Make sure that if you have any demand adjustments set that you also add those into your model. Demand adjustments are in addition to current demands already in your model when you run Calibrator, they are not in lieu of them. For example, if you have a demand adjustment of 41.01 L/s on junction J-170 then you would need to make sure to add that to J-170’s demand collection in addition to what is already there for that junction when Calibrator was run. 5. After you run Calibrator and are happy with the solution make sure you export that solution. In order to achieve the same results in your scenario you will need the adjusted values that Calibrator arrived at for your roughness adjustment groups, demand adjustment groups, and status elements. After you make all these changes to the scenario in your model just compute and look at the properties of the observed target in your model to make sure it matches the simulated results in Calibrator. See Also Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs [[General WaterGEMS V8 FAQ|General WaterGEMS V8 FAQ]] http://communities.bentley.com/products/hydraulics___hydrology/w/hydraulics_and_hydrology__wiki/18867.how-do-i-match-the-results-i-am-getting-from-darwin-calibrator-in-my-model External Links Bentley Technical Support KnowledgeBase Bentley LEARN Server

Applies To Product(s): SewerGEMS, CivilStorm Version(s): 08.11.04.54 Environment: N/A Area: Calculations Original Author: Jesse Dringoli, Bentley Technical Support Group Problem How does the Implicit dynamic solver calculate HEC-22 2nd edition structure losses and what assumptions are involved? Why is the headloss through my catchbasin or manhole smaller than expected or zero, when using the HEC-22 2nd edition energy loss method? Solution In general, when using the Implicit dynamic solver in SewerGEMS or CivilStorm, HEC-22 headlosses are calculated the same way as the StormCAD and SewerCAD solvers; based on equation 7-10 through 7-16 in the HEC-22 manual. However, there are a few assumptions that need to be considered when using the Implicit numerical solver with SewerGEMS or CivilStorm: 1) HEC-22 2nd edition is intended to be used for junction loss between inflow and outflow pipes through a structure. Therefore headloss is currently (as of version 08.11.04.55) not calculated in cases where there is no upstream pipe and the headloss will be reported as zero. This applies to the other headloss methods as well (with the Implicit numerical solver in SewerGEMS and CivilStorm). Future versions may reconsider this and allow headloss calculations in upstream-most nodes. 2) To avoid stability issues, if the velocity of the downstream pipe is greater than 5 ft/s, a special "filter" is applied, by modifying the velocity as follows: Vm = 5.0 + 0.1 *(V-5.0) Where V = calculated pipe velocity Vm = modified velocity used by structure loss calculations So, in cases where the velocity is high, the calculated headloss can be smaller than expected. 3) In SELECTseries 4 (08.11.04.54) and below, the Implicit numerical solver in SewerGEMS and CivilStorm does not have awareness of the angle of the incoming pipe, so an assumption is made in calculating the "Initial headloss coefficient" (K0) component of the HEC-22 2nd edition structure losses. So for a pipe with a relatively large bend angle, this can sometimes lead to a smaller headloss than expected. An enhancement was made in the SELECTseries 5 release to account for the bend angle. This fix is also available in the latest cumulative patch set for SELECTseries 4. Note: as of version 08.11.04.54, structure headlosses are not supported with the EPA-SWMM solver. See Also

For anyone following this thread - an enhancement was made to the Implicit solver to account for the bend angle in the HEC-22 2nd edition structure loss method. When the cumulative patch set is updated next month (May 2015), it will be included. This will also be available in the upcoming SELECTseries 5 release of SewerGEMS and CivilStorm. The Support Solution linked to this thread has been updated accordingly.

Applies To Product(s): Bentley SewerGEMS, Bentley SewerCAD, Bentley StormCAD, Bentley CivilStorm, Bentley WaterGEMS, Bentley WaterCAD, Bentley HAMMER Version(s): 08.11.xx.xx Environment: N/A Area: Modeling Subarea: Original Author: Scott Kampa, Bentley Technical Support Group Error or Warning Message When trying to publish an i-model in WaterCAD/WaterGEMS/HAMMER, the following error occurs: --------------------------- Publish to i-model --------------------------- Could not load file or assembly 'Bentley.ECAttachAddIn.ECPluginFileIO, Version=1.0.0.0, Culture=neutral, PublicKeyToken=4bf6c96a266e58d4' or one of its dependencies. The system cannot find the file specified. --------------------------- OK --------------------------- How to Avoid This issue is due to using the Hydraulics and Hydrology i-model publishing engine with a shapefile background. If the shapefile background is not necessary, remove it from the background layers manager before publishing to i-model. If you need to keep the shapefile as part of the i-model and also have MicroStation or another MicroStation-based product installed, uninstall the "i-model publishing engine for Hydraulics and Hydrology" from Control Panel > Add/Remove programs. The program will then use MicroStation for i-model publishing, which should not be a problem with shapefile backgrounds.

Applies To Product(s): Bentley WaterGEMS, Bentley WaterCAD Version(s): 08.11.04.57 Environment: N/A Area: Layout and Data Input Subarea: Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem Description Does SCADAConnect support a connection to ClearSCADA? Answer SCADAConnect allows the interaction with any SCADA system that supports database like Microsoft Access, Microsoft Excel. SCADAConnect also supports database connectivity (ODBC) interface, OLE DB interface or Structured Query Language (SQL) connection interface. Citect's native application program interface (API) is used to allow access to data sampled by the Citect server. SCADAConnect can also import data from a real time or historical OPC server. To use SCADAConnect, the user must identify the properties of the data source being used. If the data source is a data base, as opposed to an OPC server, then the user must first define the connection, which essentially identifies the type of data format (e.g. Excel, Access, ODBC) and the path to that data. If the data source is an OPC server, there is no need to set up a connection as the user need only name the computer on which the OPC server is located and the name of the OPC server. A database source refers to the data being stored in a file. For more information about this please consult our help documentation as there is more information given about SCADA connect that might help answer your question.

Colm, I don't believe we've seen this issue before so it is indeed possible that it could be related to a specific setting. It would also be helpful to know details such as the exact versions of AutoCAD and StormCAD and if this happens only with a specific drawing/xref or with any drawing (for example try one of the sample models with a separate, test xref. If you feel it is more efficient, it may be best to connect with technical support offline. A remote desktop sharing session may be necessary. We can then circle back to this forum post to share the solution.

I want to design a sanitry network and a storm network for one area in the same project.. How do I work it ?

where to find out "how long it takes to fill" ?

I am using GIS network to build model, GIS department didn't cut pipe at Orange Junction and that junction is automatically created when drawing blue pipe. When I build hydraulic model by Modelbuilder, Pipe did not split at orange junction. How can I split all pipe candidates in WaterGEMS?