here is the version details that I use as well

Hello Jatin, Once you have created a profile, right click on the profile label>Edit>Change the stations in the column - "User defined column", change the starting manhole's station to your desired value>open the profile check it>close the profile. Right click on the profile label>View Engineering profile>Options>Axis>Automatic Scaling>change the desire increment here so that software will calculate downstream chainages accordingly. I hope this helps you.

You can add multiple entries say for pressure for an element using the Time Series Field data in the model.

Applies To Product(s): Bentley WaterGEMS, Bentley HAMMER, Bentley WaterCAD Version(s): 08.11.XX.XX Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem How do I model parallel fixed head (target head) variable speed pumps that are controlled by flow in a downstream pipe? OR How do I resolve the user notification, "Variable speed pumps not in parallel cannot be controlled by the same control node"? Background Parallel variable speed pumps have special rules that apply and unless you make some specific changes to your model to workaround these rules your pumps will not work as you'd like them to. In the screen shot below the following model was originally set up where all the pumps had a single downstream junction, the black one immediately downstream of the colored junctions, which functioned as the single node the VSPs were controlled based on. The controls used for the model below are as follows: IF P-131 Flow = 25.000 L/s And P-131 Flow 50.000 L/s THEN P102C Pump Status = On Solution 1) Add 5 junctions between your pumps and the downstream control node. The software then interprets each of these VSPs separately, which is why we have step two. If we didn't have step two then the software would generate a red user notification that would prevent you from running the model. The user notification reads, "Not parallel variable speed pumps cannot be controlled by the same control node". 2) The fifth junction (green, blue, and pink all each line) that you place will be the new control node for the upstream pump, so make sure to set it appropriately in the pump properties for the control node.

Monika, The wiki link below describes a workaround that is used for how to model fixed head VSPs in parallel. The workaround involves adding 5 junctions between your pump and the control nodes. communities.bentley.com/.../20319.how-do-i-model-parallel-fixed-head-target-head-variable-speed-pumps-that-are-controlled-by-flow-in-a-downstream-pipe Mark

You can download the software with the steps in the following article. Downloading Haestad / Hydraulics and Hydrology Software When you type into the search bar use "Bentley OpenUtililities Designer". Note that there is no space in OpenUtilities. For questions on how to use that product, please post to the OpenUtilities Forum.

Hello Stephen, Regarding "Does the sewergems implicit engine "initialize" the network at the start of a run?" - By default the solver assumes a dry condition to start the simulation, but gives two options for the "start type" - warm up or transition. See the help topic "Calculation Option Attributes", section "start type". Can you clarify if you need further assistance? I was a bit unclear on your previous response if SewerGEMS is showing you results that you will need to take action on, or if you're having a problem with the model.

Hello Tushar, The Periodic Head-Flow element represents a boundary condition which allows you to specify a constant head, constant flow, or any time-dependent variation, including periodic changes that repeat indefinitely until the end of the simulation. You would set the Transient Parameter to be either Head or Flow. You would then fill in the head or flow pattern in relation to time. This gives you control over how the head or the flow is coming into the system. For the case of a positive displacement pump, you would use the steps in the link that Jesse provided earlier ( communities.bentley.com/.../11042.modeling-positive-displacement-pumps-in-hammer ). You would place the elements similar to the diagram that you see in the link. There will be two periodic head-flow elements near each other but not connected. These would be set to use the Transient Parameter "Flow" and you would need to fill in a Flow Pattern based on what you are trying to accomplish. If the positive displacement pump is shutting down, you would start with some representative flow value and after a certain amount of time, the flow would go to zero. If you are modeling the pump starting up, the flow in the pattern would start at zero and after a given time, you would enter some representative flow value. As mentioned in the link, the patterns for these periodic head-flow elements would be identical except for the values for flow. On the suction side, the flow values will be positive. On the discharge side, they will be negative, to represent inflow. As an example, if you wanted to assume a representive flow of 100 gpm for the pump, the periodic head-flow element representing the suction side of the pump would have a value of 100 gpm and the period head-flow element on the discharge side of the pump would have a flow value of -100 gpm. For your three scenarios, the setup would generally be as follows: 1) The flow pattern in the period head-flow elements would start begin with some representative flow, such as 100 gpm on the suction side and -100 gpm on the discharge side. After a time of your choosing, the flow would go to zero. Remember that the patterns will be identical except for the positive or negative sign of the flow value. 2) For a pump startup, the flow would start at zero. After a time of your choosing, the flow would be some representive value. 3) For a valve closure, the flow may be able to be set to whatever value you need to represent the flow. If the valve is supposed to be on the pump itself, you could model this similar to the pump shutdown case in number 1 above. If this doesn't help, more information on how you are setting up your periodic head-flow elements will be needed. What sorts of issues are you running into? How are the periodic head-flow elements being set up? Are you using the positive and negative values as mentioned above and in the link that was provided earlier? Any details on the issue will be useful to finding a solution. Regards, Scott

Applies To Product(s): WaterGEMS, WaterCAD, HAMMER, SewerCAD, StormCAD, SewerGEMS, CivilStorm, Pondpack Version(s): V8i or V8 XM Area: Modeling 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: Is it possible to compare scenarios and alternative between models? See Also Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs Hydraulics and Hydrology Forum External Links Bentley SELECTservices 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 Pondpack Version(s): V8i Area: Modeling 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. See more here: Inserting user defined flow or hydrograph into the model 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. See this link for additional information: How do you attach a pond outlet to an outfall in PondPack V8i? 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? 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 LEARN Server

Hi Jesse, I have tried checking the decimal places as well, with no luck. I have attached my model. I am using PondPack V8i. Thanks (Please visit the site to view this file)

Applies To Product(s): Bentley PondPack Version(s): 08.11.01.56 Area: Modeling Original Author: Akshaya Niraula, Bentley Technical Support Group Problem When attempting to validate or compute a model or when computing a composite outlet with a user defined rating table, one of the following red user notifications appear: "The maximum elevation (xft + yft) for the rating table is not the same as the headwater maximum xft. The rating table maximum elevation must equal the maximum headwater elevation." "The minimum elevation (xft + yft) for the rating table is not the same as the headwater minimum xft. The rating table minimum elevation must equal the minimum headwater elevation." Solution Most likely the elevations entered in the rating table are absolute value rather than a relative. The values on the table are added to the "elevation" value that you enter in the main properties of the user defined rating table. 1) Double click the message in the User Notifications window or go to Components > Composite Outlet Structure, then select the rating table in question. 2) In User Defined Rating Curve field, click on the three dots button (ellipsis button) and update the elevation fields. Instead of being the actual elevation value, enter a relative elevation so it may look like 0, 0.25, 0.50 etc. If this does not help, try setting the main "elevation" to zero, change the rating table elevations to be actual elevations (global edit the elevation column and add the min headwater elevation if needed), then re-type in each min and max value. meaning, click in the cell and re-enter the number, for the first and last elevation in the table, and the headwater min, max and increment value in the root properties of the composite outlet structure (if using user defined headwater elevations) Lastly, if the above does not work, try adding spot elevations (root properties of the composite outlet structure) for the min and max headwater.

Hi Mark, Thanks for sending the files. I'm uncertain exactly why this is needed, but if you change the datum to zero and re-type in the values, it works. Here's the "fixed" model: Basically I changed the user defined outlet's "elevation" to zero, global edited the elevation column in the rating table itself and added 90.6. I then re-typed in the first and last elevation in the rating table and in the min/max headwater range in the composite outlet structure. I have also combined the two aforementioned articles that Sushma sent into one, and added this workaround: Notifications about minimum or maximum elevations on the rating table not matching the headwater range

Thanks Jesse, that worked!

Applies To Product(s): Bentley WaterGEMS, Bentley SewerGEMS, Bentley CivilStorm, Bentley StormCAD, Bentley PondPack, Bentley StormCAD, Bentley HAMMER, Bentley WaterCAD Version(s): 08.11.XX.XX Area: Output and Reporting Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem Description How do I convert my model elements into shapefiles? Or: is there a way I can generate polygon shapefiles if I do not have a Map application such as ArcGIS? For example if I need a population or boundary layer for use in Loadbuilder. Background All of our software products allow you to convert your modeling elements to shapefiles that can be used in our modelbuilder tool, as background layers, or in any software that can open or work with shapefiles, such as ArcGIS or AutoCAD. Steps Use the icon on the top of the element flextables 1. Open up any flextable that has elements that are located in your model (View > Flextables> Double click on the flextable you want to open) If you do not already have these elements in the drawing, lay them out first. For example if you want to generate polygon shapefiles, lay out catchments (SewerGEMS, SewerCAD, CivilStorm, StormCAD, PondPack) or pump stations (WaterCAD, WaterGEMS, HAMMER). 2. Edit your flextable so it has all the fields that you want displayed in your shapefile. If you don't want to modify the predefined flextables, consider creating a new flextable (under View > Flextables > Project for example) with only the fields you want to export. 3. In the upper left hand corner of the flextables click the first icon. See screen shot below. Also note that when exporting flextables to shapefiles the shapefile will only contain the fields displayed in the flextable. 4. Name the shapefile and then click save. 5. Adjust the shapefile field names if necessary. The field names need to follow the shapefile field name rules, which include a limited number of characters (~9-10). 6. Click the ok button and your shapefile will be created. See Also Building a model using ModelBuilder

Applies To Product(s): Bentley WaterGEMS, Bentley SewerGEMS, Bentley CivilStorm, Bentley StormCAD, Bentley PondPack, Bentley SewerCAD, Bentley HAMMER, Bentley WaterCAD Version(s): 08.11.XX.XX Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem Using the ModelBuilder connection file. or Can a ModelBuilder file be shared? Solution After a ModelBuilder run has been created (see images below) a user can choose to export the properties of the run by clicking the 'Export Connection button'. ModelBuilder will create a .mbc file that can be shared with colleagues by using the "Import Connection" feature. See Also Building a model using ModelBuilder

Applies To Product(s): Civil products (as listed) Version(s): 08.11.XX.XX Area: Modeling Original Author: Sushma Choure, Bentley Technical Support Group Overview The purpose of this TechNote is to help you understand the Haestad Hydraulics and Hydrology (H&H) functionality in Subsurface Utilities, within Bentley's latest Civil product releases. It explains which programs it is available in, and the availability of Hydraulics & Hydrology tools within them. Background Hydraulics and Hydrology functionality was introduced in the SELECTseries 4 (SS4) version (08.11.09.845) of Bentley Civil products. Prior to that Subsurface Utility Engineering (SUE) tools were introduced in SELECTseries 3 Civil products (version 08.11.09.674+). At the time of writing, the SELECTseries 4 version of Subsurface Utilities includes the SELECTSeries 5 versions of the Haestad storm-sewer hydraulic functionality. Note that Subsurface Utilities has also been known as "SUDA" or "Subsurface Utilities Design and Analysis". Hydraulics and Hydrology functionality is included with Bentley's Civil products. These products include OpenRoads technology, which Subsurface Utilities leverages to update utilities when reference information changes. The SELECTseries 4 version introduces hydraulic design of storm and sanitary systems, in addition to the 3D modeling capabilities already available in the Select Series 3 version. Here is the list of Civil products, for which this functionality are available. GEOPAK Suite Power GEOPAK InRoads Suite Power InRoads Power RailTrack PowerCivil MXRoad MXRoad Suite Note : this does not apply to the AutoCAD environment of Civil products like Bentley InRoads, Bentley GEOPAK. Hydraulics and Hydrology functionality will help users design and analyze all underground utilities, in a single product. It contains the following features: Subsurface Utility Engineering License StormCAD license (the ability to use the H&H StormCAD solver for analysis and design of up to 100 inlets is included) If you own a license for another storm/sewer product, the functionality for that product will be available. In other words, if you own a SewerGEMS license, you will be able to use SewerGEMS functionality in the Civil product. Conflict Management / Clash Detection SUE Attributes 3D Modeling of all Underground Utilities Integrated with OpenRoads Storm/Sanitary Hydraulic Analysis and Design Hydrology Hydraulics and Hydrology Functionality With the availability of the Subsurface Utilities tools within your civil products, you can perform the following things: Design / Analysis of new or existing storm-sewer models within the civil product What if analysis, scenario and alternatives management as is possible in Hydraulics & Hydrology products Directly import existing storm-sewer models into Civil products The file saved in the .DGN format, can be directly opened back in Bentley's storm and sewer products (SewerGEMS, CivilStorm, StormCAD and SewerCAD). Clash detection of the utilities like water, gas, waste water, thermal, electrical, storm water, petroleum etc. Reference the Bentley Haestad Storm and Sewer models in the form of DGN files, to perform the clash detection or to compare the position of e.g. storm water lines with the water lines. Storm and Sanitary design tools integrated with OpenRoads road and site design tools. Meaning while laying out the network you can extract the elevation from the existing terrain model, so you don't need to enter the elevations manually. Elevations can be ruled to road/site design surfaces Position can be ruled to road/site geometry Most of the tools of Haestad storm-sewer products are available within Subsurface Utilities tools. 3D modeling of the elements within the Civil products. Licenses available A 100-inlet StormCAD license is included and used if your licence includes Civil storm and sanitary functionality. This allows for hydraulic analysis of up to 100 inlets in a given hydraulic model. If you own Haestad (H&H) product licenses, then you will have additional licenses available. In other words, if you have a 1000 pipe license for SewerGEMS, then you can use that license in the Civil products as well by making it active. If you are in the OpenAccess program, you will have access to all storm/sewer products. If the license for this is active and set as the default license configuration, you would be able to use other H&H products besides StormCAD as well. To change the active license, go to Tools > Product Add-ins > Subsurface Utility Analysis and Design > Current Hydraulics Analysis product > Change the active license. If you own this license It will include these Storm-Sewer functions: SUE functionality Any Civil product which does not include GEOPAK Drainage, InRoads S&S or MX Drainage None None Any Civil product which includes GEOPAK Drainage, InRoads Storm and Sanitary, or MX Drainage Storm water peak flow design and analysis Max 100 Inlets in any single drainage model Storm/Sanitary attributes Utilities can be modeled in 3D No SUE attributes No Utility Conflict Tools Any of the above plus either: StormCAD Unlimited SewerCAD CivilStorm SewerGEMS Unlocks additional hydraulics calculation capabilities, according to which license is activated. Utilities can be modeled in 3D No SUE attributes No Utility Conflict Tools Any of above plus a SUE license Same hydraulic capabilities as above according to which hydraulics license is active. Unlocks SUE attributes Unlocks Utility Conflict Tools NOTE : If you have SELECT Open Access licensing, you will have all the features above available for use. See Also Subsurface Utilities (SUE and StormCAD) Video Clips, TechNotes & FAQs Performing clash detection of storm/sewer/water models using Bentley Products Video: Clash Detection OpenRoads Special Interest Group (SIG) FAQs

Product(s): WaterGEMS, WaterCAD Version(s): 08.11.04.xx and later, 10.xx.xx.xx Area: Modeling Overview This article explains how to use the Scenario Energy Cost and Energy Management tools. The images in this article were taken from WaterGEMS, however the same general workflow applies to WaterCAD as well. See this article for information on using the Scenario Energy Cost tool in SewerGEMS, SewerCAD and CivilStorm. Table of Contents Background Scenario Energy Cost Analysis Energy Pricing (Tariff Types) Time of Day Block Rate Block Rate Based on Billing Demand Constant Viewing Results Water Power, Wire Power, and Wire to Water Efficiency Multiple Peak Charges in Energy Management Turbine Energy Recovery Modeling Energy Management Power Meters Carbon Emission Analysis Background There are two levels at which energy costs can be analyzed in the software. The tool called "Scenario Energy Cost" calculates energy use and cost for a single scenario. This tool is available in WaterGEMS, WaterCAD, SewerGEMS, SewerCAD and CivilStorm. "Energy Management" uses the results of multiple Energy Cost scenarios to determine energy costs at a higher level of aggregation to determine the energy cost for pump stations (not just pump-by-pump) for multiple scenarios that can occur over a billing period and determine economic costs such as net present worth of pumping energy. This tool is available in only WaterGEMS and WaterCAD. The Scenario Energy Cost analysis determines the energy cost by pump for all pumps selected by the user. Pricing for energy cost is set up in the Pricing button in energy costing. Price functions are assigned to individual pumps in energy costing. For users interested in a more complete energy analysis, running a single scenario may not be sufficient as block rate charges must be determined based on energy use over a complete billing cycle which may contain low, average and high water use periods which should be modeled as separate scenarios. In addition, the scenario corresponding to the setting of a peak demand charge is usually not an average day but some kind of peak condition that should be modeled in a separate scenario. In order to deal with the complexities of block rates, multiple scenarios, aggregation of pumps within a station, and performing present worth calculation, the user needs to use the Energy Management analysis. Such calculations are usually required because of complex tariffs for electric power. Because there may be other energy uses at the pump station besides pumping, the user can specify non-pumping energy costs to account four uses such as lighting, HVAC, control systems, chemical feed equipment, etc. These costs are added in on a Power Meter basis. There may also be charges on the power bill that are not associated with individual pumping operations such as taxes, discounts, lump sum surcharges, etc. These can be added in to the overall cost and are referred to as "other costs". The usual work flow for using the energy cost and energy management analyses may be followed as shown below: Develop EPS scenarios to be used in energy cost. Run scenarios. Start scenario energy cost analysis. Create price functions and optional carbon emission factors. Assign price functions to pumps. Run energy cost for each scenario of interest. In WaterGEMS/WaterCAD, the user can also conduct a more thorough analysis using the following steps: Close scenario energy cost analysis and start energy management. Create new energy management study. Identify which pump stations/pumps are associated with each power meter. Specify the mix of scenarios to be analyzed. Identify interest rate and number of periods if present worth calculations needed. Compute study. Review results and rerun or create new studies. In the next section we will go through a detailed step by step guide of how to use the Energy Management and Scenario Energy Cost tools. Scenario Energy Cost Analysis To open the Scenario Energy Cost tool in WaterGEMS/WaterCAD Connect Edition, go to Analysis > Energy Cost > Scenario Energy Cost. In WaterGEMS/WaterCAD V8i, the Scenario Energy Cost tool can be opened by going to Analysis > Scenario Energy Cost, or by selecting the Scenario Energy Cost icon in the toolbar. This will open the Scenario Energy Cost manager as shown below. On the left side of the manager, it will display the current scenario. If you wish to analyze a different scenario, you can choose it from the Scenario pulldown. Note: The Scenario must be an EPS run. The right side of the manager is where you will set up the energy cost analysis. On the left side of the manager you will see some result fields and specific element options. You can specify which elements will be included in the analysis in the table located on the bottom left of the manager. After selecting the scenario you will be analyzing, you will need to set up the energy pricing. To do this, click in a cell in the Energy Pricing column and click the ellipsis ("...") button. This will open the Energy Pricing manager. There are four types of Energy Pricing. Time of Day Block Rate Block Rate based on Billing Demand Constant Each of these types of Energy Pricing will act differently when you run an Energy Analysis. The Time of Day Energy Pricing will calculate energy cost comparing hours vs. $/kwh. Note: You can change the units for the energy pricing by right-clicking on the current units and choose "Units and Formatting." This allows you to change the units and the precision that the data is displayed. Time of Day The Time of Day Energy Pricing will calculate energy cost comparing hours vs. $/kwh. Energy Supply Rate structure based on a Time of Day Pattern. To create a new Time of Day Energy Pricing definition, click the New icon in the upper left. On the right side of the manager is where the data is entered. The energy pricing data itself is entered in the lower right of the dialog. First, change the Tariff Type to Time of Day. Then enter the “Starting Energy Price.” If the pricing changes over the course of the EPS run, you can enter that data in the table below "Starting Energy Price." If the pricing will include Peak Demand Charge, you must place a checkmark in the box beside “Include Peak Demand Charges?” When this is done, the two fields used with this will become available. Enter the value for Peak Demand Charge and Billing Period. The Billing Period is used to convert the peak demand charge, which may be calculated for the month, year, or another period of time, into a daily cost which can be added to the energy cost to obtain the Daily Cost. Block Rate Block Rate Energy Pricing will calculate energy cost based on a Block Rate Cost Structure. A Block Rate is a certain price charged for the first definite number of units used and a successively lower or higher price for each additional block used. Block rate charges must be determined based on energy use over a complete billing cycle which may contain low, average and high water use periods which should be modeled as separate scenarios. Note: Block Rate cannot work during Energy Scenario Cost Analysis because it must be determined based on Energy use for a complete billing cycle. Block Rate Energy Prices can only be calculated using the Energy Management tool. Block Rate Energy Pricing will compare Energy Use (kWh) vs. Energy Price ($/kWh) Block Rate based on Billing Demand Block Rate Energy Pricing will calculate energy cost based on a Block Rate Cost Structure. A Block Rate is a certain price charged for the first definite number of units used and a successively lower or higher price for each additional block used. Block Rate Energy Pricing will compare Energy Use per Billing Demand (kWh) vs. Energy Price ($/kWh) Note: Block Rate Energy Prices can only be calculated using the Energy Management tool. Constant Constant Energy Pricing will use a constant Energy Price ($/kWh) for the entire model simulation. If the pricing will include Peak Demand Charge, you must place a checkmark in the box beside “Include Peak Demand Charges?” When this is done, the two fields used with this will become available. Enter the value for Peak Demand Charge and Billing Period. The Billing Period is used to convert the peak demand charge, which may be calculated for the month, year, or another period of time, into a daily cost which can be added to the energy cost to obtain the Daily Cost. Click "Close" to return to the Scenario Energy Costs manager. When you click a cell in the Energy Price column, the energy price definition that was created will be available for selection. Viewing Results Once the energy pricing and the elements to be used in the analysis are selected, the analysis can be run. Note : You must compute the scenario before you can calculate the energy cost. Click the Compute icon in the upper left of the Energy Cost manager. Once completed, the pumps for which the calculation was run will appear in the window on the left side of the dialog. To view the results for an individual pump, select one of them from the window on the left. A Results table will appear on the right side of the manager. You can also view the available results fields as a graph by selecting the Graph tab. To select which result field to view, click the pulldown and select the field. Depending on the item you highlight different results are available. For instance, if you click on the top-most item in the tree, you will see a summary of results that include information on the energy used, the cost, the volume of flow, and the run duration. The Pump/Turbine Usage (or Pump Usage for SELECTSeries 6) folder includes this same information, but broken down by the pumps, VSPBs, or turbines that are in the model. The Pump Time Details folder shows the combined results such as volume, flow, wire power, energy cost and energy usage for all pumps over time. There is also a graph tab that allows you to view these results in a graphical format. You will also be able to view these results, plus results for water power, motor efficiency, wire to water efficiency, and cost per unit volume. As with the Pump Time Details, this shows the results per time steps. The results can also be graphed. Tank costs are accounted for in the Storage item. Peak Energy Demands shows when the peak occurs and any costs that are associated with that. Water Power, Wire Power, and Wire to Water Efficiency Many of the results that the Scenario Energy Cost manager generates are relatively straight forward. As an example, Volume Pumped (Incremental) is the volume pumped during that time step. For a few results, such as water power, wire power, and wire to water efficiency, some additional information may be needed. Water power is the amount of energy transferred to the water by the pump. This is related to the flow rate and the head added by the pump, in addition to the specific weight of the liquid (typically water). The equation used is: Wire power is the amount of energy delivered to the pump motor. Information below will show how this is derived in the program Wire to water efficiency is the ratio of water power to wire power. This can found by taking the dividing the water power by the wire power. It can also be determined by multiplying the pump efficiency and the motor efficiency. In addition to the items above, two other properties are important in the calculation of the energy used by the pump. This is the pump efficiency and the motor efficiency . Pump efficiency is derived based on the efficiency data you enter in the pump definition. You can choose to energy a Best Efficiency Point, Constant Efficiency, or Multiple Efficiency Points. Best Efficiency Power generates a curve based on the BEP Efficiency and the flow that the best efficiency occurs. Multiple Efficiency Points allows the user to enter the efficiency for different flow values. Constant Efficiency is a single efficiency value for all flows. Best Efficiency Point or Multiple Efficiency Points would likely yield the best results. Motor efficiency is also added in the pump definition under the Motor tab. It is a value set by the user. Putting it all together The energy results are determined using the wire power. In WaterGEMS and WaterCAD, the wire power is calculated by first finding the water power using the equation above. Once the water power is determined, this value is used to find the brake power using the equation: where WP is the water power and ep is the pump efficiency at the given flow that the pump is pumping at. Once the brake power is calculated, this is used to find the wire power using the following equation: where IP is the wire power and em is the motor efficiency. With the wire power, the energy used by the pump can be calculated by multiplying the wire power and the time for the energy cost simulation. Multiple Peak Charges in Energy Management The software can also be used to manage tariffs with multiple peak charges. After placing a checkmark in the box, the user can now edit the multiple peak changes. The Peak Charge Type can either be based on Clock Time or Simulation Time. The user will include the start and end times for the peak charge and enter the value for the peak demand change. With this data entered, multiple peak charges can now be taken into account when running the Scenario Energy Cost simulation. For information and assumptions on multiple peak charges, see the below Support Solution: Using Multiple Peak Demand Charges Turbine Energy Recovery Modeling Starting with the CONNECT Edition release of WaterGEMS and WaterCAD, it is now possible to model turbines for energy and revenue generation using the Scenario Energy Cost module. Turbines are more often used in HAMMER's transient analysis because of potential transient impact of startup and shutdown, however they can also be modeled in WaterGEMS and WaterCAD as well. The general setup for turbines will be the same as for pumps. In the Scenario Energy Cost manager in WaterGEMS/WaterCAD CONNECT Edition, you will now see a Turbine tab. As with pumps and pump stations, you will select Energy Pricing and, if applicable, Unit Carbon Emissions. The pricing data you use may be the same as the pump pricing data, depending on the setup of your system. One key takeaway is that turbines are typically used for energy generation . For this reason, the energy data in the turbine energy results is the energy generated, and the cost information is the revenue from the turbine. If you consider a case like the screenshot below, there is a pump and turbine in parallel. The setup of the model is such that the pump will be filling a downstream tank until the tank is full. The tank will then drain, passing through the turbine back to the reservoir upstream of the pump. The purpose of passing through the turbine is so that energy is generated as water flows into the reservoir. In running the scenario energy cost analysis for this system, you can see that some of the cost for running the pump is recouped by having the turbine in place. The energy cost data in the summary table above is a negative value because energy is being generated by the turbine. This allows you to see the net cost that includes the cost of running the pump and the revenue generated by the turbine. Note that turbines are not included in the Energy Management tool, which is discussed below, at this time. Energy Management The Scenario Energy Cost Manager is ideal for comparing different scenarios based on energy cost. However, if you would like to do more thorough analysis of Block Rates, Multiple Scenarios, or would like to consider all Energy Use you should open Energy Management tool. The Energy Management tool will allow you to use Block Rates and compare Multiple Scenarios using a single tool. You will also be able to add other Energy Costs that are not associated with WaterGEMS/WaterCAD elements such as Lighting, HVAC, Taxes, etc. Below is a list of the main differences between running the Scenario Energy Cost vs. Energy Management: Scenario Energy Costs Energy Management Detailed Energy Use Results Summary of Energy Costs Single Scenario One or More Scenarios Cost by Individual Elements and System Wide Cost by Individual Elements, Power Meter, Scenario and Systemwide Pumps and VSPB’s and Tanks Pump Stations, Pumps, and VSPB’s Cost based on Unit Energy cost or Time of Day and Peak Demand charge Cost based on all types of Energy Tariffs including Block Rates and all those from Scenario Energy Cost Considers Pump Energy and Demand Considers All Energy Use Considers only Energy Costs Considers Pump, Non-Pump and Extraneous costs To open an Energy Management Study in WaterGEMS/WaterCAD CONNECT Edition, go to Analysis > Energy Cost > Energy Management In WaterGEMS/WaterCAD V8i, click on the Energy Management icon or go to Analysis > Energy Management. Once you open the Energy Management dialog you will see the following window appear. Click the New button in the top Left Corner to create a New Energy Management study. Once you create a New Energy Management Study you will see multiple Tabs to enter data. The first Data Tab is the Options tab. Here you are able to set the Billing Period, Calculate Net Present Value, and Scenario Data. The most useful part of using the Energy Management tool is the ability to compare scenarios in the same study. As shown below you can add and compare Scenarios based on Percentage of Billing Period. The model uses the Billing Period value entered to calculate the Total cost of the study. Billing Period - Enter the total Billing Period for the Energy Study. EX. (730 days - 2 years) Calculate Net Present Value - Check to calculate the Net Present Value using the Interest Rate and Number of Years variables. Scenarios Table - Add all of the scenarios you would like to compare in a single Energy Management Study. In this example, Average Day and Peak Day scenarios are included. Include in Cost Calculation - Check Box to include or exclude the Scenario from the Management Study. Percent of Billing Period - Percentage of Billing Period entered above to use the specified scenario for the Energy Management Calculation. Compute Scenario and Energy - Dropdown menu where you can select whether to recompute the Hydraulic model Data as well as recompute the Scenario Energy Cost. (Note: Leaving this as "None" will save Calculation Time.) Use for Peak - Check Box to use the specified Scenario for Peak Demand Charge. Power Meters An important concept in energy management analysis is that of a "Power meter". A Power Meter is the basic unit that is billed by an electric utility. A Power Meter usually corresponds to a pump station. However, in WaterGEMS/WaterCAD, a pump station is a collection of pumps serving a single pressure zone. Therefore, if a pump station building has a single electric service but has a set of Low, Medium and High service pumps, for WaterGEMS and WaterCAD hydraulic calculations, it is three Pump Station elements but for energy management, it corresponds to a single Power Meter. The figure below shows how a single power meter can include multiple pumps and pump stations in a single building. Power meters are used during Energy Management. To enter data for a Power meter click on the Power meter Icon on the main toolbar inside the Energy Management dialog box. The Power Meter Dialog box looks like the following. There are Tabs to enter Pump Data, Non-Pumping Energy, and Notes. To create a New Power Meter click on the New button in the top left corner of the Power Meter window. Pumps Tab - Enter the Pumps corresponding to the specified Power Meter. Non-Pumping Energy - Enter other cost data associated with the Power Meter such as HVAC, Lighting, Control Panels, Security Systems, Temperature Control Systems, or any other Extraneous data. Notes - Enter any Notes or Instructions associated with this specified Power Meter. Once all the Power Meter data is complete you can exit the Power Meter Dialog. In the Power Meter tab, enter the applicable Energy Pricing for the Various Power Meters. Once all of the data for the Energy Management tabs has been entered you are ready to calculate the Energy Management. Click on the Calculate button on the Taskbar. Once the Calculation process is complete you will get numerous detailed results. The Results Summary section will give you detailed results about the Energy Management study. In the Results Summary you can compare results based on the entire billing period. An example is shown below: Carbon Emission Analysis Carbon Emissions can also be considered when running a Energy Cost analysis. You can choose the pumps to be included in the analysis at the same time as you select which pumps to include with the energy cost analysis. In order for the carbon emission analysis, you need to enter a Carbon Dioxide Emission Factor to complete the analysis. To do this, click in a cell under the column header Unit Carbon Emission. This will open the Unit Carbon Emission dialog. Create a new definition by select the New icon, then enter your value for the carbon dioxide emission factor. Click “Close” to return to the Energy Cost dialog and choose the new unit carbon emission definition from the pulldown menu. When you select the Compute icon in the upper right, it will now calculate the carbon emissions from the pump. To view the results, select “Pump Usage” directly under the scenario name in the window on the left. In the table, scroll all the way to the left. The Carbon Emission results field will be the last column. See Also Using the Scenario Energy Cost tool in SewerGEMS, SewerCAD and CivilStorm Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs External Links Hydraulics and Hydrology Forum Bentley SELECTservices 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!

This article provides a list of in-depth TechNotes and FAQs for Bentley SewerCAD. To search within this page, press [Ctrl]+F. Frequently Asked Questions SewerCAD General FAQs Modeling Creating User-Defined Profile Settings LoadBuilder - Flow Monitoring Distribution Modeling Force Mains with Air Valves in SewerCAD (GVF Convex Solver) Pump Station and Pump Combination Curves SewerCAD (GVF Convex Solver) vs. SewerGEMS/CivilStorm (Implicit and Explicit Dynamic solvers) vs. StormCAD (GVF Rational Solver)? Using the Scenario Energy Cost tool in SewerGEMS, SewerCAD and CivilStorm Troubleshooting Troubleshooting Automated Design Results Troubleshooting and Understanding LoadBuilder Troubleshooting negative pressures at pumps, junctions, & other node elements What’s New What's new in SewerCAD V8i SELECTseries 2 What's new in SewerCAD V8i SELECTseries 3 What's new in SewerCAD V8i SELECTseries 4 What's new in SewerCAD V8i SELECTseries 5 What’s new in StormCAD, SewerCAD, SewerGEMS and CivilStorm V8i SELECTseries 5 with CONNECT Integration What's new in SewerCAD CONNECT Edition See Also SewerCAD Product Information Haestad Product TechNotes And FAQs Haestad Methods Water Solutions on Bentley Website

This article provides a list of in-depth TechNotes and FAQs for Bentley SewerGEMS. To search within this page, press [Ctrl]+F. Frequently Asked Questions SewerGEMS General FAQs SewerGEMS For ArcGIS FAQs Modeling Creating User-Defined Profile Settings Headwalls LoadBuilder - Flow Monitoring Distribution Modeling Force Mains with Air Valves in SewerCAD (GVF Convex Solver) Pump Station and Pump Combination Curves Running a Long Term Continuous Simulation SewerCAD (GVF Convex Solver) vs. SewerGEMS/CivilStorm (Implicit and Explicit Dynamic solvers) vs. StormCAD (GVF Rational Solver)? Transferring Custom Inlets Catalogs, Storm Data, Conduit Catalogs, or Flow-Headloss Curves from One Computer to Another Understanding the Modified Rational Method Understanding LoadBuilder Using Catchment Delineation Using the Scenario Energy Cost tool in SewerGEMS, SewerCAD and CivilStorm Why does the profile for the system appear to be at odds with the results for the capacity? (For example, the profile does not show a conduit as being full, but the capacity results indicate that it is.) Troubleshooting Troubleshooting negative pressures at pumps, junctions, & other node elements Troubleshooting unstable model results using the Explicit SWMM Solver Troubleshooting unstable model results using the implicit solver What's New What's new in SewerGEMS V8i SELECTseries 2 What's new in SewerGEMS V8i SELECTseries 3 What's new in SewerGEMS V8i SELECTseries 4 What's new in SewerGEMS V8i SELECTseries 5 What’s new in StormCAD, SewerCAD, SewerGEMS and CivilStorm V8i SELECTseries 5 with CONNECT Integration What's new in SewerGEMS CONNECT Edition See Also SewerGEMS Product Information Haestad Product TechNotes And FAQs Haestad Methods Water Solutions on Bentley Website