Applies To Product(s): BENTLEY STORMCAD Version(s): 05.06.00.00 Environment: N\A Area: Installation Subarea: N\A Original Author: Scott Kampa, Bentley Technical Support Group Problem Will StormCAD version 5.6 or SewerCAD version 5.6 install on a Windows 7 machine? Problem ID#: 90075, Solution Version 5.6 of both StormCAD and SewerCAD are not supported on Windows 7. These programs would need to be installed on a Windows XP machine.The latest version of StormCAD and SewerCAD are compatible with Windows 7.You can install the virtual machine for windows XP operating machine. See Also

Applies To Product(s): Bentley StormCAD Version(s): 08.11.00.44 Environment: N\A Area: Layout and Data Input Subarea: N\A Original Author: Jesse Dringoli, Bentley Technical Support Group Problem When importing an Inroads storm and sanitary file (.sdb) into StormCAD, the following error occurs: "Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index" Problem ID#: 43493, Solution This may occur if the Inroads network has one or more instances of a pipe with two upstream pipes coming into it, but with the upstream node not set to "Y_JUNC". Correct this and the file should import. See Also

Hello Sawsan, Typically the shape of the hydropneumatic tank (horizontal vs. vertical for example) would not have a large impact on transient results. The reason is because the change in the gas-liquid interface (water level) would typically be very small relative to the magnitude of the pressure from the pressurized gas. For example the water level might change only one meter while the hydraulic grade might change by 50 meters. However if the change in water level is important, you can model the shape of the hydropneumatic tank by selecting "variable elevation" as the "elevation type". You may want to try running the transient simulation with both shapes (vertical and horizontal) and check the sensitivity of the results. More on this can be found in the following articles on our Wiki: Is there a way to view the water level within a hydropneumatic tank? Modeling Reference - Hydropneumatic Tanks (see section "variable elevation".)

Hi Andrew, Thanks for asking this question. As one of the developers who has worked on the WaterGEMS computational engine for many years I will try to provide you with an answer. In order to do this, I would like to cover a little bit of history of the engine development, which should shed some light on the motivation behind such settings as damping limit. Firstly, I should point out that the hydraulic engine upon which the WaterGEMS numerical engine is based, is the US EPA's EPANET, in fact EPANET v2. EPANET v2 was originally developed in the late 90's (first released to the public in 2000) and was actively developed by the US EPA until 2008. During those years, changes were made to the computational engine by the US EPA in response to feedback from users. In the history of the engine development there were and continue to be two main stable release points as follows. EPANET 2.00.10, released 6/24/2002. EPANET 2.00.12, released 2/25/2008. That is, EPANET 2.00.10 was the result of 2 years of public feedback that stood un-modified for 5 years until 2007, and EPANET 2.00.12 has been the standard since 2008. EPANET 2.00.12 was the release that included a parameter for controlling the damping limit. You will note corresponding to the above stable releases, that in WaterGEMS, we support an engine compatibility setting, that has four possible options as follows: 1. EPANET 2.00.10 2. EPANET 2.00.12 3. WaterGEMS 2.00.10 4. WaterGEMS 2.00.12 The meaning of these four settings, in the same order as listed above, is: 1. An engine closely based upon EPANET 2.00.10. This engine attempts to match the result obtained by EPANET 2.00.10. 2. An engine closely based upon EPANET 2.00.12. This engine attempts to match the result obtained by EPANET 2.00.12. 3. An engine based upon EPANET 2.00.10, but with corrections and enhanced features. 4. An engine based upon EPANET 2.00.12, but with corrections and enhanced features. In reality, it is always the same computational engine behind the scenes, but the compatibility setting changes the way the engine behaves in accordance with the above descriptions. The words "attempts to" (for cases 1 and 2) means that the engine version will faithfully reproduce any known computational errors that exist in the corresponding EPANET version in order to match the EPANET results of the same version. For that reason, you would only want to use an EPANET compatibility mode in the case you are exporting to EPANET and wish to match hydraulic results with that version of EPANET. The words "based upon" (for cases 3 and 4) could also, for most intents and purposes, be interpreted as "using the convergence strategy of" and this point provides the segway we need into the discussion of convergence and the questions you are asking. One of the more significant changes made between EPANET 2.00.10 and 2.00.12 was to alter the convergence strategy used for control valves. This was presumably in response to cases (models) where the previous strategy was unable to solve correctly. Cases that could not solve would typically manifest in unbalanced calculations where pairs of control valves would oscillate. The convergence strategy was modified in a number of ways. One modification was to initialize control valves to ACTIVE (versus explicitly starting only PRVs and PSVs as OPEN), so to answer your specific question about "does it change algorithm starting point?" the answer is that the EPANET 2.00.12 based mode does this in comparison to the EPANET 2.00.10 based mode, but otherwise there is no effect on starting point (other than the continued fact that the solution for one time-step in an EPS run forms the starting point for the next time's simulation). Or in other words, the EPANET 2.00.10 based engines use a different starting point to the EPANET 2.00.12 based engines, but changing engine options does not affect starting point. Another modification to the convergence strategy is that the concept of damping (2.00.11) and a damping factor (2.00.12) was introduced, in order to assist with the convergence of problematic models. By the sounds Andrew, you have discovered this option and utilized it to your benefit. The change was simply to no longer check the status of control valve every iteration (which could result in oscillations in some cases) and to relax that check only occur when the relative flow change is getting close to the target accuracy (e.g., 0.01, versus 0.001). In EPANET 2.00.11 the damp limit was fixed at 10x the hydraulic accuracy, however, in EPANET 2.00.12 it was exposed to allow the user to change it (and it defaults to OFF (0) in that case, which reverts to the same case as EPANET 2.00.10, unless a user wishes to enable it). In terms of "what is affected by damping options", let me first start with a brief description of why the damping is in place, and not some other kind of modification. The computational engine essentially solves one linear continuity equation for each node and one non-linear energy equation for each loop. Since the equations are non-linear, an iterative method must be used. Once the equations are set up, the solution converges very efficiently, however, once a control valve changes status, the equations themselves change. Thus, the computational engine is shooting at a moving target. In order to help the equations to stay stable for a while, the damping comes into play. Too much damping, however, can slow down the process. So damping affects the convergence checks that are made on valves and then the subsequent flow changes applied to all hydraulic links, by reducing the magnitude of the flow changes. The damping option aims to allow the solution to converge to within a reasonable level before checking control valve status, and then when it has converged to within a certain value, to smooth out the effect of oscillating valve status changes and improve the final convergence in such situations. As an analog, think of the damping as something similar to tweaking the feedback amplifier in a feedback control system. The damping tries to avoid overshoot. In so far as computed results go, the main factor here is the specified hydraulic accuracy. Valve statuses are checked for the converged solution so using damping should not affect the result in that way; it's merely a means to improving the ability of the algorithm to find a valid solution. Converged results achieved with different calculations in play are not guaranteed to be exactly the same since the results in part may depend on the path taken to convergence, however, the default hydraulic accuracy value normally means that for most practical purposes and systems that results do not significantly vary (by any appreciable value in an engineering sense). You may wish to perform a sensitivity analysis on your model with varying hydraulic accuracy to see whether the model you have built solves well with the default hydraulic accuracy, or whether a tighter value is required (at the potential trade-off of more hydraulic trials). Finally, you mention VFD (Variable speed pumps) in your question. There should not be any discernible difference between the application of the VSP algorithm in either the EPANET 2.00.10 and EPANET 2.00.12 based engines (noting that EPANET itself does not support automatically variable speed parameter estimation) or with any calculation options changes. At the end of the day you should adopt the set of calculation options that results in consistent and stable convergence, and if that is not readily obtainable, as Jesse mentioned in his response, then you should seek to eliminate the causes of such stability issues from the model itself. I hope that this reply helps, at least in part, to answer some of your questions. Regards, Wayne.

Product(s): SewerGEMS Version(s): 10.00.00.40 Environment: N\A Area: N/A Overview The CONNECT Edition release of SewerGEMS introduces numerous improvements and features to help you be more successful. Let's explore each of these in detail. List of Topics Compatibility Supported Operating Systems Compatible Platforms Interface Ribbon Interface File and Help Menus Layout & Data Input Background Images View and edit the path for background images Improved background layer performance World file support for background images New Element Property Connection Automated Catchment Delineation Calculations Pump Energy Costs SWMM Enhancements New SWMM Climatology Monthly Adjustments Table New SWMM Calculation Executive Summary New SWMM Calculation Options SWMM Culvert Support New Roadway Weir LID (Low Impact Development) Enhancements Outfall to a catchment Improved Performance HEC-22 3rd Edition Tractive Stress Results Graphs QuickGraph More meaningful steady state graph "Select in drawing" in graphs and graph manager Profiles Engineering Profile Annotation Table Profiles no longer save automatically Customizable Reports Record AVI video from time results Usability Enhancements Duplicate Prototypes Open on selection from within FlexTable Double-click on dropdown list to toggle through values Option to auto-close the Calculation Summary dialog after computing a model New alternative features (recently added to FlexTables) Excel export option available in all platforms Inroads IDF Importer Ability to use Wetwell %full as a condition with SewerCAD controls Maximum depth/rise property added to conduits to identify flooding/surcharging CONNECT Integration View Changes Toggle tap node dashed line display Added support for DGN files in ModelBuilder New Queries Display contour lines in plan view Compatibility [ Top of Page ] Supported Operating Systems Windows 10 (32-bit or 64-bit) Windows 8 (32-bit or 64-bit) Windows 7 (32-bit or 64-bit) Compatible Platforms SewerGEMS CONNECT Edition standalone version does not require any CAD or GIS software to work. However, it can be integrated with the following platforms: MicroStation V8i SELECTseries 4 (Note: MicroStation CONNECT Edition integration is not yet supported with this release) AutoCAD 2016, or 2017 ArcGIS 10.3.1, or 10.4 See: Wiki Platform Compatibility Wiki SewerGEMS CONNECT Edition (10.00.00.40) Readme Interface [ Top of Page ] Ribbon Interface A new ribbon user interface has been added to the stand-alone products. A button has been added to the welcome dialog to provide quick access to the ribbon interface help documentation. The application menus match the platform the program is integrated with. MicroStation V8i and ArcGIS do not use a ribbon user interface. Therefore this release of the Storm and Sewer products will not use the ribbon interface when integrated with MicroStation or ArcGIS. The following article provides an in-depth look at the new ribbon menu. Ribbon Interface for Storm and Sewer CONNECT Edition products File and Help Menus When the File tab is selected, the entire program dialog switches to display the File menu (ie. "backstage"). The Help menu and Database Utilities have been moved to the File menu. Layout & Data Input [ Top of Page ] Background Images View and edit the path for background images The Image Properties dialog now displays the image's filename and includes a Browse button to edit the field. Improved background layer performance Background layers are now loaded more efficiently so that less memory is consumed. This improvement is especially helpful when using multiple large files for background images. World file support for background images The following background image formats are now supported. Bentley Drawing Files (*.idgndb, *.imodel, *.dgn) World Files Some image formats support associated world files. When attaching a background image file that has an associated world file present, the image will be spatially located automatically (ie. georeferenced). The following file formats support an associated world file. bmp jpg jpeg jpe jfif tif tiff png Gif The World file extension is based on the image's extension. One convention is to use the first and last letter of the image's extension and add a "w" (eg. .jpg>.jgw). Another convention is to append the image's extension with a "w" (eg. .jpg>.jpgw). When opening the file, the Image Properties dialog will automatically enter the coordinates from the World file in the editable (Drawing) fields. New Elements This release includes a new element type; property connection. Property Connection Property connection elements are used to load sewer models based on data at the level of individual properties. This is useful when you have loading data provided for customers/properties based on metering, number of occupants/fixture units, or simply flow per property. Including all property connections in your hydraulic model is useful when there is a need to have a closer (one-to-one) match with your GIS. Being able to see all property connections in the hydraulic model allows you to get a more detailed view of where the individual loading occurs, rather than lumping many loads into one manhole. Property connections are used for sanitary loading in the Implicit, Explicit and GVF Convex solvers, but not the GVF Rational solver. Property connections support hydrograph, pattern, and unit loads. They can also directly accept runoff as the outlet of a catchment. For the GVF Rational Solver, flow through a Property Connection must come from a Catchment. (Property Connection designated as the Outflow Element.) Inflow/loading from a property connection element would typically enter your network via a Lateral link that connects to a conduit via a tap node. See: Wiki Property Connections Help "Property Connections" LoadBuilder can be used to assign isolated Property Connection elements to the nearest element by creating a tap and lateral connection. Isolated Property Connections are those elements that are not connected to any lateral element. Laterals are automatically placed between the source element and the hydraulic network when using LoadBuilder and selecting Property Connection Load Data as the Available LoadBuilder Method. When this data source is used, it is assumed that that load data is already available in the Property Connection. See: Wiki Using LoadBuilder to assign Property Connections to the nearest element and create taps and laterals Help "LoadBuilder Wizard" The query "Property Connections not connected to Nearest Link" is now included in the Network Review Predefined Queries. Automated Catchment Delineation The new Catchment Delineation tool is a terrain model analysis system designed to find the catchment area with runoff flow path ending at a low point or passing through an inlet surface area. It automatically finds catchment boundary points for inlets, calculates catchment properties, and derives gutter network and gutter properties. Note: Bentley terrain model and its functions are used in running catchment delineation. When the Run Catchment Delineation is selected from the Terrain Modeling Manager, the button for Catchment Delineation will be placed in the depressed position. At this time, whenever a catch basin is added or moved within the Digital Terrain Model (DTM) the catchment is identified or updated. Selecting Catchment Delineation Settings from the Terrain manager opens the following dialog where the user can adjust parameters that control the catchment delineation tool behavior. See: Help "Catchment Delineation" Help "Catchment Delineation Settings" Calculations [ Top of Page ] Pump Energy Costs This release introduces a new Energy Cost tool which optimizes pump operations. With this tool you can now analyze the cost of operating pumps (by the energy used) during a single extended period simulation scenario. 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 the energy costing manager. Price functions are assigned to individual pumps in energy costing. This tool works with all solvers that support pumps: Explicit (SWMM Solvers) Implicit (SewerGEMS Dynamic Wave) This solver always assumes the Relative Speed Factor = 1 if the pump is on. GVF-Convex (SewerCAD) Results can be viewed in tabular format or graphed. Depending on the selection, results can show data for a single pump or a pump station. SWMM Enhancements New SWMM Climatology Monthly Adjustments Table The SWMM extension Climatology now includes the "Adjustments" tab. Checking the Apply Climate Adjustments box enables the Monthly Adjustments table, where you can define Temperature Constant, Evaporation Constant, Rainfall Multiplier, and Soil Conductivity Multiplier adjustments by month. New SWMM Calculation Executive Summary In previous versions, after successfully computing a model with the SWMM solver a large text file would be created and opened with an external text editor, such as Notepad. Starting with this release, an internal dialog provides the SWMM Calculation Executive Summary. This makes it much easier to browse or find results. This dialog displays values using the hydraulic model's units. In prior versions, the results were displayed in US Customary units regardless of the hydraulic model's defined units. New SWMM Calculation Options The Explicit default Routing Time Step was reduced from 30 seconds to 5 seconds for better stability. The default value for Use Variable Time Step is now True. The following two calculation options for the Explicit solver were introduced in this release. The Minimum Variable Time Step is the smallest time step allowed when variable time steps are used. The default is 0.5 seconds. Smaller steps may be warranted, but they can lead to longer simulation runs without much improvement in solution quality. The Number of Threads is the number of parallel computing threads to use on machines equipped with multi-core processors. The default is 1. The SWMM Default Infiltration Method has the new option "Green and Ampt (Modified)". This modified version of the original Green and Ampt method no longer redistributes upper zone moisture deficit during low rainfall events. The original authors of SWMM's Green-Ampt model have endorsed this modified version. It will produce more infiltration for storm events that begin with low rainfall intensities, such as the SCS design storm distributions. SWMM Culvert Support Culverts can now be modeled by the Explicit (SWMM) solver. When exporting a model to SWMM the culverts in the engineering libraries will now be converted with their associated SWMM culvert codes. This allows the culvert to be recognized when the model is opened in SWMM. The Section "SWMM Solver" has been added to the Culvert Catalog dialog. You can either enter the "SWMM culvert code" or you can click the ">" button to select the culvert from a menu. New Roadway Weir A new type of weir, a ROADWAY weir, has been added. It models roadway overtopping using the FHWA HDS-5 method and would typically be used in parallel with a culvert conduit to route bypass to the downstream node. The fields Road Width and Surface Type are specific to the Roadway weir type. LID (Low Impact Development) Enhancements New LID Underdrain Target option The LID (Low Impact Development) element has the new field "Underdrain Outflow Element" which lets you specify an element that will accept underdrain flow from the LID. New LID Control Type Low Impact Development Control type now includes the option Roof Top Disconnection. New Soil fields for Porous Pavement type LID control A Soil section has been added to the LID control type Porous Pavement as shown below. This allows you to model a sand filter or bedding layer beneath the pavement. Outfall to a catchment The field "Route to Catchment" is now available for the outfall element when using the Explicit solver. This field allows you to specify the catchment to which flow will be routed from the outlet. The following outfall Boundary Condition Types are supported. Free Outfall Normal Tidal Time-Elevation Curve User Defined Tailwater Improved Performance Other general improvements have been implemented to reduce the computation time when using the SWMM Solver. HEC-22 3rd Edition Prior to this release, the HEC-22 3rd Edition junction loss method was only available with the GVF-Rational and GVF-Convex solvers. (The Implicit solver only supports the HEC-22 2nd Edition procedure). Various improvements have been made to the HEC-22 3rd edition structure loss calculations to bring better compliance with the HEC-22 Standard. Bentley has added functionality to the EPA's version of SWMM so that it more seamlessly integrates with our data model and our other Storm-Sewer Products. HEC-22 Inlet Calculations Ability to compute complex pond outlet structures Headloss Calculations at structures including HEC-22 and Standard Headloss methods. Additional detailed results Integrated LID results Tractive Stress Calculations Hydrogen Sulfide Modelling Tractive Stress When conduits and channels have sufficient tractive stress they are essentially self-cleaning in that particles will either not settle or they will be re-suspended if they do. Conduit tractive shear stress is now calculated when using the following solvers. GVF-Convex Explicit Implicit (Dynamic Wave) Note: Previously, tractive stress was only supported by the GVF-Convex solver. Starting in this release, tractive stress is included in constraint based design. See: Help "Tractive Force Design" Wiki Tractive Stress (aka Tractive Force, Shear Stress) Calculations and Design Results [ Top of Page ] Graphs QuickGraph The new Quick Graph feature provides a fast way to view a graph of a single element in the drawing. The Quick Graph automatically updates to display data for the selected element. More meaningful steady state graph If the current scenario is steady-state (or the base condition for fire flow), the default graph is a bar chart for the selected elements. Elements from different scenarios can also be added in the Series Options dialog. The Series Options dialog can be used to customize the information displayed in the graph (scenarios, elements, and fields). "Select in drawing" in graphs and graph manager In the graphs manager you now have an additional option "Select in Drawing" which is to the right of "Add to Graph". When a saved graph is selected and you click this button it will select the elements that are part of the saved graph. Any existing selection will first be cleared. Only elements that are checked in the graph options will be selected in the drawing. Profiles Engineering Profile Annotation Table Engineering profiles now have the option to include an annotation table which is drawn similar to the analysis profile. However, the displayed fields and field order can be edited in the engineering profile which makes it more customizable. To toggle the annotation table display, click on the down arrow next to the Chart Settings icon and select "Show Profile Annotation Table" from the dropdown menu. The annotation table options can be edited by selecting "Profile Annotation Table Options…" from this dropdown menu. Profiles no longer save automatically Profiles created with the context menu (right-click>Create Profile) are now temporary. When you close the profile viewer for a temporary profile, you are asked if you want to save it. When you select Yes to this prompt you will have the chance to enter a label for the profile. Customizable Reports A new Custom Report tool has been added to the Report tab. This tool allows you to quickly assemble a customized report which can contain user input, results, graphs, etc. You can now define the template interactively instead of modifying an XML file manually (which can still be done). The reports can be exported to the following formats PDF HTML MHT RTF Excel CSV Text Image The Report Options dialog can be accessed by clicking the icon below the Custom Report icon. This dialog allows you to control how reports are displayed (eg. font, header, footer, margins). See: Help "Custom Reports" Help "Report Options" Record AVI video from time results The AVI Screen capture enhancement allows you to record videos of scenario animations. You can select which portion of the screen will be recorded. The screen capture utility will capture and record all the frames of the animation within the bounds you specify and produce an AVI video file which is sharable outside of the storm and sewer products. An internal video player allows you to watch the video after it is done recording. See: Help "Recording Scenario Animations" Usability Enhancements [ Top of Page ] Duplicate Prototypes The Prototypes Manager now includes the option to duplicate prototypes. Open on selection from within FlexTable When you have a FlexTable open, i.e. Junction FlexTable, you can now select the rows in the table based on the current selection. To use the feature: Select some elements. Open a FlexTable for one of the selected elements and click the drop-down arrow for the “Select in Drawing” button. Click the last item, “Select from Drawing”. If there are any elements for the type of table you currently have open, it will select the rows for the elements selected. You can then filter down the contents of the table by right-clicking the row header and clicking on “Open on Selection”. Double-click on dropdown list to toggle through values When editing data in the property grid you can double-click the label to change the value. This applies to Boolean fields (those that show true/false values); reference fields (i.e. zone); and enumerated fields (i.e. Status (Initial)). When you double-click any of these field types it will cycle through the available values in the drop-down list. Commands like “Edit” for reference fields are excluded during the cycling. Option to auto-close the Calculation Summary dialog after computing a model The Calculation Executive Summary dialog box opens after you compute a model. You now have the option to not automatically open the dialog after a compute by unchecking “Show this dialog after Compute”. This option applies to all available solvers for the product. This is a global option and once unchecked applies to all projects opened in the product. The post-calculation summary dialog now allows you to choose if it displays after computing a model as seen in the image below. This dialog can also be accessed by clicking on the Home tab and selecting the Calculation Summary icon. New alternative features (recently added to FlexTables) Some features that were recently added to FlexTables are now available for alternatives. You can now quickly zoom to an element within an Alternative dialog by either right-clicking on the row header and selecting "Zoom To", or by double-clicking on the row header. When a row is highlighted, pressing enter will select the next row. Excel export option available in all platforms FlexTables can be exported to an Excel file in multiple products (SewerGEMS, SewerCAD, StormCAD, and CivilStorm) and for all integrated platforms (MicroStation, AutoCAD, ArcMap, and stand alone). See: Can I easily export my results to an Excel spreadsheet? Inroads IDF Importer InRoads IDF files can now be imported into an engineering library storm event group which can then be used by SewerGEMS, StormCAD, CivilStorm, or PondPack. This can be done as a batch process with an external tool or individually using the Storm Data dialog. Ability to use Wetwell %full as a condition with SewerCAD controls Wet well control conditions now include the storage attribute "Percent Full". Note: Controls only apply to the "GVF-Convex (SewerCAD)" numerical solver. If using the "Explicit (SWMM Solvers)" or "Implicit (SewerGEMS Dynamic Wave)" numerical solver, pump controls must be defined in the properties of the pump. Controls do not apply to the "GVF-RationaI (StormCAD)" numerical solver. Maximum depth/rise property added to conduits to identify flooding/surcharging Conduits now have the property "Depth (Maximum) / Rise (%)" which displays the ratio of maximum calculated average depth (average between start and stop) to the rise of the conduit. CONNECT Integration This release requires the latest version of CONNECTION client. If it isn't already on the computer, it will be downloaded and installed during the product's installation. After the product installation completes, a CONNECTION client slideshow will display. This provides an introduction to the CONNECTION client, allows you to enter your login information, or create a new account if you don't already have one. There is a new CONNECTED Project association dialog which allows the default behavior to be set. If you don't want the dialog to appear in the future, then select "Do not notify me again". View Changes The view can be quickly set to Zoom Extents by double-clicking the middle button on your mouse. For some, this may be done with the scroll-wheel button. Toggle tap node dashed line display When a tap is placed, a dashed line appears to show which link the tap is associated with. The tap element symbology properties now include a "Show Associated Link Decorations" field to control if this dashed line is displayed. Added support for DGN files in ModelBuilder ModelBuilder now supports Bentley Drawing File formats (*.idgndb, *.imodel, *.dgn). New Queries The following Queries have been added. Network Review Property Connections not connected to Nearest Link Inlets In Sag With Bypass Gutters Inlets On Grade Without Bypass Gutters Catch Basins Without a Catchment Network Trace Find Adjacent Nodes Find Adjacent Links Find Adjacent Start Nodes Find Adjacent Stop Nodes Display contour lines in plan view Terrain Models can now display contour lines. The terrain model edit dialog allows you to define the minor interval and the amount of lines per major interval. The major interval will be calculated based off of those inputs. You can also customize the colors of the major and minor interval contour lines. See Also [ Top of Page ] SewerGEMS CONNECT Edition (10.00.00.40) Readme Product TechNotes and FAQs Haestad Methods Product TechNotes And FAQs SewerGEMS and CivilStorm TechNotes and FAQs Downloading Haestad / Hydraulics and Hydrology Software Software installation order Cumulative patch set information Set up notifications for new versions and patch set releases Original Author: Craig Calvin

Product(s): CivilStorm Version(s): 10.00.00.40 Environment: N\A Area: N/A Overview The CONNECT Edition release of CivilStorm introduces numerous improvements and features to help you be more successful. Let's explore each of these in detail. List of Topics Compatibility Supported Operating Systems Compatible Platforms Interface Ribbon Interface File and Help Menus Layout & Data Input Background Images View and edit the path for background images Improved background layer performance World file support for background images New Element Property Connection Automated Catchment Delineation Calculations Pump Energy Costs SWMM Enhancements New SWMM Climatology Monthly Adjustments Table New SWMM Calculation Executive Summary New SWMM Calculation Options SWMM Culvert Support New Roadway Weir LID (Low Impact Development) Enhancements Outfall to a catchment Improved Performance HEC-22 3rd Edition Tractive Stress Results Graphs QuickGraph More meaningful steady state graph "Select in drawing" in graphs and graph manager Profiles Engineering Profile Annotation Table Profiles no longer save automatically Customizable Reports Record AVI video from time results Usability Enhancements Duplicate Prototypes Open on selection from within FlexTable Double-click on dropdown list to toggle through values Option to auto-close the Calculation Summary dialog after computing a model New alternative features (recently added to FlexTables) Excel export option available in all platforms Inroads IDF Importer Ability to use Wetwell %full as a condition with SewerCAD controls Maximum depth/rise property added to conduits to identify flooding/surcharging CONNECT Integration View Changes Toggle tap node dashed line display Added support for DGN files in ModelBuilder New Queries Display contour lines in plan view Compatibility [ Top of Page ] Supported Operating Systems Windows 10 (32-bit or 64-bit) Windows 8 (32-bit or 64-bit) Windows 7 (32-bit or 64-bit) Compatible Platforms CivilStorm CONNECT Edition standalone version does not require any CAD or GIS software to work. However, it can be integrated with the following platforms: MicroStation V8i SELECTseries 4 (Note: MicroStation CONNECT Edition integration is not yet supported with this release) AutoCAD 2016, or 2017 See: Wiki Platform Compatibility Interface [ Top of Page ] Ribbon Interface A new ribbon user interface has been added to the stand-alone products. A button has been added to the welcome dialog to provide quick access to the ribbon interface help documentation. The application menus match the platform the program is integrated with. MicroStation V8i does not use a ribbon user interface. Therefore this release of the Storm and Sewer products will not use the ribbon interface when integrated with MicroStation. The following article provides an in-depth look at the new ribbon menu. Ribbon Interface for Storm and Sewer CONNECT Edition products File and Help Menus When the File tab is selected, the entire program dialog switches to display the File menu (ie. "backstage"). The Help menu and Database Utilities have been moved to the File menu. Layout & Data Input [ Top of Page ] Background Images View and edit the path for background images The Image Properties dialog now displays the image's filename and includes a Browse button to edit the field. Improved background layer performance Background layers are now loaded more efficiently so that less memory is consumed. This improvement is especially helpful when using multiple large files for background images. World file support for background images The following background image formats are now supported. Bentley Drawing Files (*.idgndb, *.imodel, *.dgn) World Files Some image formats support associated world files. When attaching a background image file that has an associated world file present, the image will be spatially located automatically (ie. georeferenced). The following file formats support an associated world file. bmp jpg jpeg jpe jfif tif tiff png Gif The World file extension is based on the image's extension. One convention is to use the first and last letter of the image's extension and add a "w" (eg. .jpg>.jgw). Another convention is to append the image's extension with a "w" (eg. .jpg>.jpgw). When opening the file, the Image Properties dialog will automatically enter the coordinates from the World file in the editable (Drawing) fields. New Element This release includes a new element type; property connection. Property Connection Property connection elements are used to load sewer models based on data at the level of individual properties. This is primarily used with sewer models, but is still available in CivilStorm. This is useful when you have loading data provided for customers/properties based on metering, number of occupants/fixture units, or simply flow per property. Including all property connections in your hydraulic model is useful when there is a need to have a closer (one-to-one) match with your GIS. Being able to see all property connections in the hydraulic model allows you to get a more detailed view of where the individual loading occurs, rather than lumping many loads into one manhole. Property connections are used for sanitary loading in the Implicit, Explicit and GVF Convex solvers, but not the GVF Rational solver. Property connections support hydrograph, pattern, and unit loads. They can also directly accept runoff as the outlet of a catchment. For the GVF Rational Solver, flow through a Property Connection must come from a Catchment. (Property Connection designated as the Outflow Element.) Inflow/loading from a property connection element would typically enter your network via a Lateral link that connects to a conduit via a tap node. See: Wiki Property Connections Help "Property Connections" The query "Property Connections not connected to Nearest Link" is now included in the Network Review Predefined Queries. Automated Catchment Delineation The new Catchment Delineation tool is a terrain model analysis system designed to find the catchment area with runoff flow path ending at a low point or passing through an inlet surface area. It automatically finds catchment boundary points for inlets, calculates catchment properties, and derives gutter network and gutter properties. Note: Bentley terrain model and its functions are used in running catchment delineation. When the Run Catchment Delineation is selected from the Terrain Modeling Manager, the button for Catchment Delineation will be placed in the depressed position. At this time, whenever a catch basin is added or moved within the Digital Terrain Model (DTM) the catchment is identified or updated. Selecting Catchment Delineation Settings from the Terrain manager opens the following dialog where the user can adjust parameters that control the catchment delineation tool behavior. See: Help "Catchment Delineation" Help "Catchment Delineation Settings" Calculations [ Top of Page ] Pump Energy Costs This release introduces a new Energy Cost tool which optimizes pump operations. With this tool you can now analyze the cost of operating pumps (by the energy used) during a single extended period simulation scenario. 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 the energy costing manager. Price functions are assigned to individual pumps in energy costing. This tool works with all solvers that support pumps: Explicit (SWMM Solvers) Implicit (SewerGEMS Dynamic Wave) This solver always assumes the Relative Speed Factor = 1 if the pump is on. GVF-Convex (SewerCAD) Results can be viewed in tabular format or graphed. Depending on the selection, results can show data for a single pump or a pump station. SWMM Enhancements New SWMM Climatology Monthly Adjustments Table The SWMM extension Climatology now includes the "Adjustments" tab. Checking the Apply Climate Adjustments box enables the Monthly Adjustments table, where you can define Temperature Constant, Evaporation Constant, Rainfall Multiplier, and Soil Conductivity Multiplier adjustments by month. New SWMM Calculation Executive Summary In previous versions, after successfully computing a model with the SWMM solver a large text file would be created and opened with an external text editor, such as Notepad. Starting with this release, an internal dialog provides the SWMM Calculation Executive Summary. This makes it much easier to browse or find results. This dialog displays values using the hydraulic model's units. In prior versions, the results were displayed in US Customary units regardless of the hydraulic model's defined units. New SWMM Calculation Options The Explicit default Routing Time Step was reduced from 30 seconds to 5 seconds for better stability. The default value for Use Variable Time Step is now True. The following two calculation options for the Explicit solver were introduced in this release. The Minimum Variable Time Step is the smallest time step allowed when variable time steps are used. The default is 0.5 seconds. Smaller steps may be warranted, but they can lead to longer simulation runs without much improvement in solution quality. The Number of Threads is the number of parallel computing threads to use on machines equipped with multi-core processors. The default is 1. The SWMM Default Infiltration Method has the new option "Green and Ampt (Modified)". This modified version of the original Green and Ampt method no longer redistributes upper zone moisture deficit during low rainfall events. The original authors of SWMM's Green-Ampt model have endorsed this modified version. It will produce more infiltration for storm events that begin with low rainfall intensities, such as the SCS design storm distributions. SWMM Culvert Support Culverts can now be modeled by the Explicit (SWMM) solver. When exporting a model to SWMM the culverts in the engineering libraries will now be converted with their associated SWMM culvert codes. This allows the culvert to be recognized when the model is opened in SWMM. The Section "SWMM Solver" has been added to the Culvert Catalog dialog. You can either enter the "SWMM culvert code" or you can click the ">" button to select the culvert from a menu. New Roadway Weir A new type of weir, a ROADWAY weir, has been added. It models roadway overtopping using the FHWA HDS-5 method and would typically be used in parallel with a culvert conduit to route bypass to the downstream node. The fields Road Width and Surface Type are specific to the Roadway weir type. LID (Low Impact Development) Enhancements New LID Underdrain Target option The LID (Low Impact Development) element has the new field "Underdrain Outflow Element" which lets you specify an element that will accept underdrain flow from the LID. New LID Control Type Low Impact Development Control type now includes the option Roof Top Disconnection. New Soil fields for Porous Pavement type LID control A Soil section has been added to the LID control type Porous Pavement as shown below. This allows you to model a sand filter or bedding layer beneath the pavement. Outfall to a catchment The field "Route to Catchment" is now available for the outfall element when using the Explicit solver. This field allows you to specify the catchment to which flow will be routed from the outlet. The following outfall Boundary Condition Types are supported. Free Outfall Normal Tidal Time-Elevation Curve User Defined Tailwater Improved Performance Other general improvements have been implemented to reduce the computation time when using the SWMM Solver. HEC-22 3rd Edition Prior to this release, the HEC-22 3rd Edition junction loss method was only available with the GVF-Rational and GVF-Convex solvers. (The Implicit solver only supports the HEC-22 2nd Edition procedure). Various improvements have been made to the HEC-22 3rd edition structure loss calculations to bring better compliance with the HEC-22 Standard. Bentley has added functionality to the EPA's version of SWMM so that it more seamlessly integrates with our data model and our other Storm-Sewer Products. HEC-22 Inlet Calculations Ability to compute complex pond outlet structures Headloss Calculations at structures including HEC-22 and Standard Headloss methods. Additional detailed results Integrated LID results Tractive Stress Calculations Hydrogen Sulfide Modelling Tractive Stress When conduits and channels have sufficient tractive stress they are essentially self-cleaning in that particles will either not settle or they will be re-suspended if they do. Conduit tractive shear stress is now calculated when using the following solvers. GVF-Convex Explicit Implicit (Dynamic Wave) Note: Previously, tractive stress was only supported by the GVF-Convex solver. Starting in this release, tractive stress is included in constraint based design. See: Help "Tractive Force Design" Wiki Tractive Stress (aka Tractive Force, Shear Stress) Calculations and Design Results [ Top of Page ] Graphs QuickGraph The new Quick Graph feature provides a fast way to view a graph of a single element in the drawing. The Quick Graph automatically updates to display data for the selected element. More meaningful steady state graph If the current scenario is steady-state (or the base condition for fire flow), the default graph is a bar chart for the selected elements. Elements from different scenarios can also be added in the Series Options dialog. The Series Options dialog can be used to customize the information displayed in the graph (scenarios, elements, and fields). "Select in drawing" in graphs and graph manager In the graphs manager you now have an additional option "Select in Drawing" which is to the right of "Add to Graph". When a saved graph is selected and you click this button it will select the elements that are part of the saved graph. Any existing selection will first be cleared. Only elements that are checked in the graph options will be selected in the drawing. Profiles Engineering Profile Annotation Table Engineering profiles now have the option to include an annotation table which is drawn similar to the analysis profile. However, the displayed fields and field order can be edited in the engineering profile which makes it more customizable. To toggle the annotation table display, click on the down arrow next to the Chart Settings icon and select "Show Profile Annotation Table" from the dropdown menu. The annotation table options can be edited by selecting "Profile Annotation Table Options…" from this dropdown menu. Profiles no longer save automatically Profiles created with the context menu (right-click>Create Profile) are now temporary. When you close the profile viewer for a temporary profile, you are asked if you want to save it. When you select Yes to this prompt you will have the chance to enter a label for the profile. Customizable Reports A new Custom Report tool has been added to the Report tab. This tool allows you to quickly assemble a customized report which can contain user input, results, graphs, etc. You can now define the template interactively instead of modifying an XML file manually (which can still be done). The reports can be exported to the following formats PDF HTML MHT RTF Excel CSV Text Image The Report Options dialog can be accessed by clicking the icon below the Custom Report icon. This dialog allows you to control how reports are displayed (eg. font, header, footer, margins). See: Help "Custom Reports" Help "Report Options" Record AVI video from time results The AVI Screen capture enhancement allows you to record videos of scenario animations. You can select which portion of the screen will be recorded. The screen capture utility will capture and record all the frames of the animation within the bounds you specify and produce an AVI video file which is sharable outside of the storm and sewer products. An internal video player allows you to watch the video after it is done recording. See: Help "Recording Scenario Animations" Usability Enhancements [ Top of Page ] Duplicate Prototypes The Prototypes Manager now includes the option to duplicate prototypes. Open on selection from within FlexTable When you have a FlexTable open, i.e. Junction FlexTable, you can now select the rows in the table based on the current selection. To use the feature: Select some elements. Open a FlexTable for one of the selected elements and click the drop-down arrow for the “Select in Drawing” button. Click the last item, “Select from Drawing”. If there are any elements for the type of table you currently have open, it will select the rows for the elements selected. You can then filter down the contents of the table by right-clicking the row header and clicking on “Open on Selection”. Double-click on dropdown list to toggle through values When editing data in the property grid you can double-click the label to change the value. This applies to Boolean fields (those that show true/false values); reference fields (i.e. zone); and enumerated fields (i.e. Status (Initial)). When you double-click any of these field types it will cycle through the available values in the drop-down list. Commands like “Edit” for reference fields are excluded during the cycling. Option to auto-close the Calculation Summary dialog after computing a model The Calculation Executive Summary dialog box opens after you compute a model. You now have the option to not automatically open the dialog after a compute by unchecking “Show this dialog after Compute”. This option applies to all available solvers for the product. This is a global option and once unchecked applies to all projects opened in the product. The post-calculation summary dialog now allows you to choose if it displays after computing a model as seen in the image below. This dialog can also be accessed by clicking on the Home tab and selecting the Calculation Summary icon. New alternative features (recently added to FlexTables) Some features that were recently added to FlexTables are now available for alternatives. You can now quickly zoom to an element within an Alternative dialog by either right-clicking on the row header and selecting "Zoom To", or by double-clicking on the row header. When a row is highlighted, pressing enter will select the next row. Excel export option available in all platforms FlexTables can be exported to an Excel file in multiple products (SewerGEMS, SewerCAD, StormCAD, and CivilStorm) and for all integrated platforms (MicroStation, AutoCAD, ArcMap, and stand alone). See: Can I easily export my results to an Excel spreadsheet? Inroads IDF Importer InRoads IDF files can now be imported into an engineering library storm event group which can then be used by SewerGEMS, StormCAD, CivilStorm, or PondPack. This can be done as a batch process with an external tool or individually using the Storm Data dialog. Ability to use Wetwell %full as a condition with SewerCAD controls Wet well control conditions now include the storage attribute "Percent Full". Note: Controls only apply to the "GVF-Convex (SewerCAD)" numerical solver. If using the "Explicit (SWMM Solvers)" or "Implicit (SewerGEMS Dynamic Wave)" numerical solver, pump controls must be defined in the properties of the pump. Controls do not apply to the "GVF-RationaI (StormCAD)" numerical solver. Maximum depth/rise property added to conduits to identify flooding/surcharging Conduits now have the property "Depth (Maximum) / Rise (%)" which displays the ratio of maximum calculated average depth (average between start and stop) to the rise of the conduit. CONNECT Integration This release requires the latest version of CONNECTION client. If it isn't already on the computer, it will be downloaded and installed during the product's installation. After the product installation completes, a CONNECTION client slideshow will display. This provides an introduction to the CONNECTION client, allows you to enter your login information, or create a new account if you don't already have one. There is a new CONNECTED Project association dialog which allows the default behavior to be set. If you don't want the dialog to appear in the future, then select "Do not notify me again". View Changes The view can be quickly set to Zoom Extents by double-clicking the middle button on your mouse. For some, this may be done with the scroll-wheel button. Toggle tap node dashed line display When a tap is placed, a dashed line appears to show which link the tap is associated with. The tap element symbology properties now include a "Show Associated Link Decorations" field to control if this dashed line is displayed. Added support for DGN files in ModelBuilder ModelBuilder now supports Bentley Drawing File formats (*.idgndb, *.imodel, *.dgn). New Queries The following Queries have been added. Network Review Property Connections not connected to Nearest Link Inlets In Sag With Bypass Gutters Inlets On Grade Without Bypass Gutters Catch Basins Without a Catchment Network Trace Find Adjacent Nodes Find Adjacent Links Find Adjacent Start Nodes Find Adjacent Stop Nodes Display contour lines in plan view Terrain Models can now display contour lines. The terrain model edit dialog allows you to define the minor interval and the amount of lines per major interval. The major interval will be calculated based off of those inputs. You can also customize the colors of the major and minor interval contour lines. See Also [ Top of Page ] Product TechNotes and FAQs Haestad Methods Product TechNotes And FAQs SewerGEMS and CivilStorm TechNotes and FAQs Downloading Haestad / Hydraulics and Hydrology Software Software installation order Cumulative patch set information Set up notifications for new versions and patch set releases Original Author: Craig Calvin

Product(s): StormCAD Version(s): 10.00.00.40 Environment: N\A Area: N/A Overview The CONNECT Edition release of StormCAD introduces fixes to various user-reported problems and other general improvements. Let's explore each of these in detail. List of Topics Compatibility Supported Operating Systems Compatible Platforms Interface Ribbon Interface File and Help Menus Layout & Data Input Background Images View and edit the path for background images Improved background layer performance World file support for background images New Element Property Connection Automated Catchment Delineation Calculations HEC-22 3rd Edition Results Profiles Engineering Profile Annotation Table Profiles no longer save automatically Customizable Reports Usability Enhancements Duplicate Prototypes Open on selection from within FlexTable Double-click on dropdown list to toggle through values Option to auto-close the Calculation Summary dialog after computing a model New alternative features (recently added to FlexTables) Excel export option available in all platforms Inroads IDF Importer CONNECT Integration View Changes Toggle tap node dashed line display Added support for DGN files in ModelBuilder New Queries Display contour lines in plan view Compatibility [ Top of Page ] Supported Operating Systems Windows 10 (32-bit or 64-bit) Windows 8 (32-bit or 64-bit) Windows 7 (32-bit or 64-bit) Compatible Platforms StormCAD CONNECT Edition standalone version does not require any CAD or GIS software to work. However, it can be integrated with the following platforms: MicroStation V8i SELECTseries 4 (Note: MicroStation CONNECT Edition integration is not yet supported with this release) AutoCAD 2016, or 2017 See: Wiki Platform Compatibility Interface [ Top of Page ] Ribbon Interface A new ribbon user interface has been added to the stand-alone products. A button has been added to the welcome dialog to provide quick access to the ribbon interface help documentation. The application menus match the platform the program is integrated with. MicroStation V8i does not use a ribbon user interface. Therefore this release of the Storm and Sewer products will not use the ribbon interface when integrated with MicroStation. The following article provides an in-depth look at the new ribbon menu. Ribbon Interface for Storm and Sewer CONNECT Edition products File and Help Menus When the File tab is selected, the entire program dialog switches to display the File menu (ie. "backstage"). The Help menu and Database Utilities have been moved to the File menu. Layout & Data Input [ Top of Page ] Background Images View and edit the path for background images The Image Properties dialog now displays the image's filename and includes a Browse button to edit the field. Improved background layer performance Background layers are now loaded more efficiently so that less memory is consumed. This improvement is especially helpful when using multiple large files for background images. World file support for background images The following background image formats are now supported. Bentley Drawing Files (*.idgndb, *.imodel, *.dgn) World Files Some image formats support associated world files. When attaching a background image file that has an associated world file present, the image will be spatially located automatically (ie. georeferenced). The following file formats support an associated world file. bmp jpg jpeg jpe jfif tif tiff png Gif The World file extension is based on the image's extension. One convention is to use the first and last letter of the image's extension and add a "w" (eg. .jpg>.jgw). Another convention is to append the image's extension with a "w" (eg. .jpg>.jpgw). When opening the file, the Image Properties dialog will automatically enter the coordinates from the World file in the editable (Drawing) fields. New Element This release includes a new element type; property connection. Property Connection Property connection elements are used to load sewer models based on data at the level of individual properties. This is primarily used with sewer models, but is still available in StormCAD. This is useful when you have loading data provided for customers/properties based on metering, number of occupants/fixture units, or simply flow per property. Including all property connections in your hydraulic model is useful when there is a need to have a closer (one-to-one) match with your GIS. Being able to see all property connections in the hydraulic model allows you to get a more detailed view of where the individual loading occurs, rather than lumping many loads into one manhole. Property connections are used for sanitary loading in the Implicit, Explicit and GVF Convex solvers, but not the GVF Rational solver. Property connections support hydrograph, pattern, and unit loads. They can also directly accept runoff as the outlet of a catchment. For the GVF Rational Solver, flow through a Property Connection must come from a Catchment. (Property Connection designated as the Outflow Element.) Inflow/loading from a property connection element would typically enter your network via a Lateral link that connects to a conduit via a tap node. See: Wiki Property Connections Help "Property Connections" Automated Catchment Delineation The new Catchment Delineation tool is a terrain model analysis system designed to find the catchment area with runoff flow path ending at a low point or passing through an inlet surface area. It automatically finds catchment boundary points for inlets, calculates catchment properties, and derives gutter network and gutter properties. Note: Bentley terrain model and its functions are used in running catchment delineation. When the Run Catchment Delineation is selected from the Terrain Modeling Manager, the button for Catchment Delineation will be placed in the depressed position. At this time, whenever a catch basin is added or moved within the Digital Terrain Model (DTM) the catchment is identified or updated. Selecting Catchment Delineation Settings from the Terrain manager opens the following dialog where the user can adjust parameters that control the catchment delineation tool behavior. See: Help "Catchment Delineation" Help "Catchment Delineation Settings" Calculations [ Top of Page ] HEC-22 3rd Edition Various improvements have been made to the HEC-22 3rd edition structure loss calculations to bring better compliance with the HEC-22 Standard. Results [ Top of Page ] Profiles Engineering Profile Annotation Table Engineering profiles now have the option to include an annotation table which is drawn similar to the analysis profile. However, the displayed fields and field order can be edited in the engineering profile which makes it more customizable. To toggle the annotation table display, click on the down arrow next to the Chart Settings icon and select "Show Profile Annotation Table" from the dropdown menu. The annotation table options can be edited by selecting "Profile Annotation Table Options…" from this dropdown menu. Profiles no longer save automatically Profiles created with the context menu (right-click>Create Profile) are now temporary. When you close the profile viewer for a temporary profile, you are asked if you want to save it. When you select Yes to this prompt you will have the chance to enter a label for the profile. Customizable Reports A new Custom Report tool has been added to the Report tab. This tool allows you to quickly assemble a customized report which can contain user input, results, graphs, etc. You can now define the template interactively instead of modifying an XML file manually (which can still be done). The reports can be exported to the following formats PDF HTML MHT RTF Excel CSV Text Image The Report Options dialog can be accessed by clicking the icon below the Custom Report icon. This dialog allows you to control how reports are displayed (eg. font, header, footer, margins). See: Help "Custom Reports" Help "Report Options" Usability Enhancements [ Top of Page ] Duplicate Prototypes The Prototypes Manager now includes the option to duplicate prototypes. Open on selection from within FlexTable When you have a FlexTable open, i.e. Junction FlexTable, you can now select the rows in the table based on the current selection. To use the feature: Select some elements. Open a FlexTable for one of the selected elements and click the drop-down arrow for the “Select in Drawing” button. Click the last item, “Select from Drawing”. If there are any elements for the type of table you currently have open, it will select the rows for the elements selected. You can then filter down the contents of the table by right-clicking the row header and clicking on “Open on Selection”. Double-click on dropdown list to toggle through values When editing data in the property grid you can double-click the label to change the value. This applies to Boolean fields (those that show true/false values); reference fields (i.e. zone); and enumerated fields (i.e. Status (Initial)). When you double-click any of these field types it will cycle through the available values in the drop-down list. Commands like “Edit” for reference fields are excluded during the cycling. Option to auto-close the Calculation Summary dialog after computing a model The Calculation Executive Summary dialog box opens after you compute a model. You now have the option to not automatically open the dialog after a compute by unchecking “Show this dialog after Compute”. This option applies to all available solvers for the product. This is a global option and once unchecked applies to all projects opened in the product. The post-calculation summary dialog now allows you to choose if it displays after computing a model as seen in the image below. This dialog can also be accessed by clicking on the Home tab and selecting the Calculation Summary icon. New alternative features (recently added to FlexTables) Some features that were recently added to FlexTables are now available for alternatives. You can now quickly zoom to an element within an Alternative dialog by either right-clicking on the row header and selecting "Zoom To", or by double-clicking on the row header. When a row is highlighted, pressing enter will select the next row. Excel export option available in all platforms FlexTables can be exported to an Excel file in multiple products (SewerGEMS, SewerCAD, StormCAD, and CivilStorm) and for all integrated platforms (MicroStation, AutoCAD, ArcMap, and stand alone). See: Can I easily export my results to an Excel spreadsheet? Inroads IDF Importer InRoads IDF files can now be imported into an engineering library storm event group which can then be used by SewerGEMS, StormCAD, CivilStorm, or PondPack. This can be done as a batch process with an external tool or individually using the Storm Data dialog. CONNECT Integration This release requires the latest version of CONNECTION client. If it isn't already on the computer, it will be downloaded and installed during the product's installation. After the product installation completes, a CONNECTION client slideshow will display. This provides an introduction to the CONNECTION client, allows you to enter your login information, or create a new account if you don't already have one. There is a new CONNECTED Project association dialog which allows the default behavior to be set. If you don't want the dialog to appear in the future, then select "Do not notify me again". View Changes The view can be quickly set to Zoom Extents by double-clicking the middle button on your mouse. For some, this may be done with the scroll-wheel button. Toggle tap node dashed line display When a tap is placed, a dashed line appears to show which link the tap is associated with. The tap element symbology properties now include a "Show Associated Link Decorations" field to control if this dashed line is displayed. Added support for DGN files in ModelBuilder ModelBuilder now supports Bentley Drawing File formats (*.idgndb, *.imodel, *.dgn). New Queries The following Queries have been added. Network Review Inlets In Sag With Bypass Gutters Inlets On Grade Without Bypass Gutters Catch Basins Without a Catchment Network Trace Find Adjacent Nodes Find Adjacent Links Find Adjacent Start Nodes Find Adjacent Stop Nodes Display contour lines in plan view Terrain Models can now display contour lines. The terrain model edit dialog allows you to define the minor interval and the amount of lines per major interval. The major interval will be calculated based off of those inputs. You can also customize the colors of the major and minor interval contour lines. See Also [ Top of Page ] StormCAD TechNotes and FAQs Product TechNotes and FAQs Haestad Methods Product TechNotes And FAQs SewerGEMS and CivilStorm TechNotes and FAQs Downloading Haestad / Hydraulics and Hydrology Software Software installation order Cumulative patch set information Set up notifications for new versions and patch set releases Original Author: Craig Calvin

Thank you, Wayne, for this very helpful reply. Between your explanation and model analysis, it looks like damping was designed for this type of model situation. For this particular model, the damping feature dramatically improves solver runtime and avoids calculation errors. As you suggested, a sensitivity analysis on the most sensitive pumps shows very little change when varying calculation options (no change for the majority of time steps; at most 2% difference in flow/pressure). Thanks for addressing these questions and improving confidence in this software. Looking forward to more runs… Andrew

I am not sure the best approach to this, I have complicated water system model where I would like to add in a 3" pipe and see what the available flow rate is at the outlet of the pipe. I thought I could achieve this by adding a discharge to atmosphere node at the end of the pipe, but I dont know what to put in for the typical pressure drop and flow. Is there an easier way to just see how much water is available at the end of the 3" pipe? What I am trying to do is add in metered bulk water stations throughout the system where contractor can come fill up a water truck, I want to see what is avaiable in the system and how it affects the pressure in the rest of the system. Any help is appreciated.

Hello Fariba, You have posted on the file gallery, which is not monitored. Please ask your question on the Hydraulics and Hydrology forum. Regards, Jesse

Product(s): WaterCAD, WaterGEMS Version(s): 08.11.xx.xx Environment: N\A Area: Modeling Problem How does WaterGEMS/WaterCAD treat the discharge to atmosphere element during EPS/steady state? Solution This element is primarily for use with HAMMER, but also has a hydraulic effect in WaterGEMS and WaterCAD. The reason why this element (and other transient related elements) are present in WaterCAD/WaterGEMS is because these programs share a file format with HAMMER. Meaning, you can lay out your transient analysis protective equipment when developing your steady state/EPS hydraulic model, so that you can later directly open it in HAMMER and have it ready for transient modeling. The typical flow and pressure drop are used to calculate a discharge (orifice) coefficient. The program uses that value to calculate the other flows through the element during the simulation and their corresponding pressure drop. The flow and pressure drop are based on the HGL in the system during the steady state (initial condition) run where the solver finds the flow needed to drop that HGL to the discharge to atmosphere element's elevation (where it meets the atmosphere) given the calculated discharge coefficient. The following methods can be used to either assume a flow and solve for head, or assume a head and solve for flow. Method 1: If there is no restriction/contraction at the pipe outlet, then consider using the minor loss equation H = K * (V^2) / 2g K: Minor loss coefficient. 1.0 is a typical value for a pipe exit (to atmosphere, not submerged). V : Velocity at the pipe exit (ft/s, m/s) g : Gravitational acceleration (32.2 ft/(s^2), 9.81 m/(s^2)) V = Q/A V : Velocity (ft/s, m/s) Q : Flow (cfs, cms) A : Cross-sectional Area (ft^2, m^2) Method 2: If the outlet orifice is smaller than the pipe diameter, then consider using the orifice equation. Q = C A (2 g H)^0.5 Known C : Orifice coefficient. This value is assumed by the engineer. A typical value for a typical orifice is 0.6. For in-depth information on orifice coefficients for different situations, see Brater and King’s Handbook of Hydraulics (1996). A : Orifice Area (ft, m) g : Gravitational acceleration (32.2 ft/(s^2), 9.81 m/(s^2)) Unknown Q : Discharge (cfs, cms) H : Head (ft, m) The program will not produce valid results if the "Flow (Typical)" and a corresponding "Pressure Drop (Typical)" are set to zero. If you are using this element, you will need to enter valid values for these two fields. See Also Options for modeling an outflow that varies with pressures How do WaterGEMS/WaterCAD treat the discharge to atmosphere element? Modeling Reference - Discharge To Atmosphere [TN] Stormwater Conveyance Modeling and Design - Page 204 Advanced Water Distribution Modeling and Management - Page 40 Original Author: Jesse Dringoli

Applies To Product(s): Bentley WaterGEMS, Bentley WaterCAD Version(s): 08.11.XX.XX Environment: Area: Modeling Subarea: Original Author: Jesse Dringoli, Bentley Technical Support Group Problem How can you calculate the actual flow available when opening a hydrant nozzle, accounting for losses based on the orifice diameter, etc? Solution You can simply enter an emitter coefficient at the junction or hydrant element corresponding to the actual hydrant size. The correct emitter for your hydrant size will account for losses through the nozzle and the outflow will be dependent on the pressure available in the system. There is a discussion of this in Advanced Water Distribution Modeling and Management , pages 451-453. Typical values for a 2.5 in outlet are on the order of 165 to 185 gpm/sqrt(psi). You can also take a look at Conventional Flushing in the Flushing tool , which allows you to essentially see results in batch for multiple, separate hydrants. If the hydrant has been placed in-line with the distribution main pipes (lateral pipes not explicitly modeled), you can account for any losses through the lateral pipes using the fields available in the properties of the hydrant node.

Matt, For modeling this scenario you'll need to be familiar with how to use the active topology alternative to create a new scenario with a 3" pipe that has a discharge to atmosphere (d2a) element on the end of the pipe. This wiki explains how WaterCAD and WaterGEMS treat a D2A element and what values to enter for the typical flow and pressure drop. This can also be modeled with a hydrant using an emitter coefficient using the procedure discussed in this wiki Regards, Mark.

Thanks Mark. For an example, say you just had one pipe connected to a reservoir on one end and a discharge to atmosphere on the other. Is there a way to see how much flow you can get through the pipe? Is there is another way to do this, w/o entering in a value for the typical flow and pressure drop? I just want to know what you can get out of the pipe.

Applies To Product(s): Bentley WaterGEMS/WaterCAD Version(s): V8i SELECTseries 4 (08.11.04.50) Environment: N/A Area: Other Subarea: N/A Original Author: Terry Foster, Bentley Technical Support Group This technote applies for Flushing in SELECTseries 4 and SELECTseries 5 versions of WaterGEMS and WaterCAD. There is a separate technote on Flushing in WaterGEMS/CAD Select Series 6 +, below is the link to that. http://communities.bentley.com/products/hydraulics___hydrology/w/hydraulics_and_hydrology__wiki/25654.flushing-in-watergemscad-select-series-6 Overview The Flushing tool has greatly been improved. The new flushing module is easy to setup, easy to run (you can run a selected event or all events), and easy to generate printer ready reports. Both conventional and unidirectional flushing can be arranged under certain area or study. In earlier builds of WaterGEMS/CAD, flushing was controlled in the flushing alternative. Flushing is now under the Analysis menu (Analysis > Flushing Manager). If a user opens a project created in an earlier build, the data in the flushing alternative will be transferred to the flushing manager. There has been a new criteria added "Target Shear Stress" along with the Target Velocity. This field can be used as a requirement to test the flushing event run. Reasons to Flush Operating hydrant to assure that the hydrant will operate properly when called on in an emergency Removing stale water Increasing disinfectant residual Removing dissolved material Removing settled solids Removing attached solids Removing bio-films Removing contaminants after a contamination event Categories Movement of dissolved matter (includes disinfectant and taste and odor) - Velocity and shear stress are inconsequential. Removal of settled and loosely attached material (includes color and turbidity) - Very small increases in shear stress are all that is required. Removal of attached material (includes bio-films and attached solids) - More substantial threshold shear stress must be met. Work Flow for Modeling Flushing Start with a calibrated model Start Flushing Manager Create Study Create Area/Set up Options Create Events Compute Study Area or Event Create Area/Set up Options To perform an analysis of a set of flushing events (i.e. a flushing area), the user must create flushing events. Upon opening the flushing manager initially, there will be a default study, "Flushing Study" which will have one area called "Base Flushing" in the left pane. The user creates new studies or areas by right-clicking on the study node in the left pane. By right-clicking on the area a new event can be created. Identifying the Buttons Left to Right New : creates new study, area or event depending on which node is highlighted Delete : deletes the highlighted study, area or event Rename : to edit the name of the highlighted study, area or event Compute : starts analysis of highlighted study or area Flushing Browser : opens the flushing results browser Report : opens up a preview of the operator report Move Up : moves selected area or event up the list Move Down : moves selected area or event down the list Zoom : zooms to extent of selected study, area or event Highlight : highlights elements in selected study, area or event Expand/Collapse : expands or collapses selected node Options : enables user to set default colors and extent of view in conventional flushing Help : opens flushing help Within a flushing area, the user defines the representative scenario, target velocity and shear stress, pipe set, method to determine flow (emitter or flow) and auxiliary output if desired. It is a good idea to create a selection set corresponding to the pipe set before entering the flushing manager. Representative Scenario : This establishes the boundary conditions (tank levels, pump status, demands) for the area. Output Scenario: This is created automatically the first time the area is computed. Target Velocity: The velocity that should be exceeded for the flushing to be considered successful for that pipe. Target Shear Stress: The user may specify a Target Shear Stress or a Tar Velocity, or in addition to a Target Velocity. Both defaults are zero. Pipe Set: By clicking on the ellipsis button the user can select the pipes or a selection set. Nodes of Interest: Auxiliary results are saved to these. They are usful for monitoring low pressure during flushing. This is an optional field. Flushing Flows: The user can specify either emitter coefficient for the hydrant or junction being flowed or the actual flow rate. Because the flow rate depends on pressure and the user usually does not know the flow rate ahead of time, it is usually more accurate to specify an emitter coefficient. Do not specify both an emitter coefficient and a flow. Typical values are 250 gpm/psi^0.5 (20 L/s/m^0.5). Auxiliary Output: The user can save values for all elements from each event. However, in most cases the user is not interested in values far from flushing. Therefore, the user must specify conditions for element data to be saved and available for display for individual events. If the box, "Includes nodes with Pressure less than?" is checked, properties for elements with pressure less than the specified value are saved for display. If the box, "Include pipes with velocity greater than?" is checked, properties of pipes with high velocity are saved. This makes it possible to use color coding to display results of flushing without saving a great deal of unneeded values. The user then creates events within an area. It is assumed that the flushing events are conducted in the order in which they are listed. The key to order is usually to flush from clean water into un-cleaned areas. Conventional events are made up of the hydrant (or junction) to be flowed. These events have an advantage of being very easy to set up a large number of conventional events in essentially one step. The user will see the Selection dialog where individual junctions or hydrants are selected. Junctions or hydrants can be selected by polygon or they can be selected based on a selection set that has been previously defined. If not all the nodes in a polygon are to be flowed, it can be helpful to have a selection set done already. For UDF events, they must be created one at a time because the user must select flowed elements, controlled elements, and optionally the pipe run to be flushed. In this case a special form of the select dialog is opened. The events tab enables the user to get a quick view of the events that are contained in the area, and if desired, make events active or inactive for the next run. The notes tab enables the uwer to enter a text description of the area. In creating a UDF event, use the second button to select the operational elements (hydrant, junction, valve). If a hydrant or junction is selected, it is considered to be flowed. If an isolation valve or control valve is selected these are considered to be closed. If a pipe element is selected the default is that the pipe is closed. If the user selects the third button to select the pipes will be a part of the pipe run. In creating a UDF event, use the third button to add the pipe run elements. Once an event is created, if the event is expanded in the left pane, there is one row for each element that is flowed, closed, or part of a pipe run. The element label and type are properties of the element selected and the status is an editable field (unless it is a flushing element such as a hydrant) indicating if the element is open/closed, flowed, or part of a pipe run. The flow emitter or flows specified in an area tab can be overwritten by checking the Specify Local Flows check box for that element and inserting a different flow or emitter. Note fields are very important if the results of the flushing analysis are to be given to operators to locate elements to operate. The notes may included an address for a hydrant or at a location of a valve that needs to be closed. Flushing Results Browser The flushing results browser contains the results of a flushing run listed by event. The content of the browser corresponds to the current scenario. If it is not a flushing output scenario, no events would be displayed. The scenario can be switched to the flushing browser in the main drawing or by picking the button next to the output scenario selection in the right panel of the flushing manager. Before opening the browser it is helpful to set up color coding and annotations that will highlight the flushing events. Usually color coding pipes by velocity or shear stress, and junctions or hydrants by demand, will be the most useful. Conventional Results UDF Results Toolbar Buttons on Flushing Results Browser Zoom : zooms to extent of flushing event Highlight : highlights elements in flushing event. In highlighting, the pipe run color will override element symbology color coding. Reset : cancels out the selected event and displays results for representative scenario Report : opens preview of flushing browser report Help : opens flushing help Flushing Area Report (Flex Table) While the Flushing Results Browser displays flushing results on an event basis, the flushing area results flex table presents the results on a pipe basis listing whether the pipe met the flushing target and which event was the most effective in flushing that pipe. With the current scenario set to a flushing output scenario, open the flushing flex table. By default, the table will open with all pipes. If the model is large it is helpful to make a selection of elements and pick "Open on Selection" when opening the flex table. Flushing Notifications Message Text Message Category Response Pipe set not specified. Error Specify pipe set At least one flushing event element is not active during the flushing run. Warning Elements must be active to affect flushing results. Have you deleted any pipes since pipe set was created? At least one run pipe is not included in flush pipe set Information Ideally, pipes in a run should be included in pipe set. At least one run pipe is closed during the flushing run Warning Pipes in run should not be closed. At least one event contains a pipe run that is not continuous Warning Check for gaps in the pipe run. Reports The user can identify the extent of the drawing that will appear in the optional reports. Default Report Options User Defined Report Options Before opening the operator's report button, the modeler should: 1. Set up the desired background layer 2. Decide the extent of the view to display and if additional views are desired, set up those views. 3. Include detailed notes to help the operators locate the elements (e.g. an operator may not know where H-21 is located but will know "Hydrant in front of 31 Elm St.". Operator Report The operator report consists of three types of pages for each event: 1. Text description of the event indicating which elements to operate 2. Drawing of the event 3. Form which flushing operator can complete to describe results of flushing for feedback (optional). In addition to the default drawing of the event, the user can create "Secondary Views" which may for example, zoom into details of a complex intersection. To do this, right-click on Report Views in the left pane and select Add Secondary View. Draw a box around the extents of the secondary view and click Select New Report View. The view that appears when the report is open is called a Preview. With this preview, it is possible to: Change page set Print Export to a variety of file formats including .pdf and text file Transmit via email The report can be saved and it is possible to zoom and pan within the document. Example of a Conventional Report Example of a UDF Operator Report External Links Product TechNotes and FAQs Hydraulics and Hydrology Forum Bentley SELECTservices Bentley Learn Server

Matt, You need to have some type of element on the other end of the pipe that has a demand. The D2A element with the typical flow and pressure drop acts as a demand, so you'd at least need to enter that information for the sample model you're describing to run. Based on your description you'll want to use method 1 described in the wiki and estimate typical flow and pressure using the minor loss equation. Once that is entered you'll be able to estimate the flow through your pipe. Regards, Mark

Matt, A pipe can carry an infinite flow rate, at an infinite headloss. So, the flow that will actually leave the system at the end of your pipe depends on either the size of the opening (if discharging to the atmosphere) or an assumed consumption/outflow. If the pipe does discharge to the atmosphere, the program needs to know something about the size of the opening in order to calculate the outflow based on the pressure at the pipe end. You may want to look into emitters for this; you can enter an emitter coefficient to represent the opening size and the program will be able to vary the outflow based on the pressure. You may be able to find an appropriate coefficient from a reference manual. For the discharge-to-atmosphere approach, as Mark says, you could use the orifice equation to calculate the "typical" flow and pressure drop, based on the size of the opening that will discharge to the atmosphere. You can also place a junction at the end of the pipe (where flow would leave the system), right click on that junction and choose "hydrant flow curve". This will plot a curve of outflow (demand) vs pressure. So, you can see the resulting residual pressure for a range of outflow rates. This only gives the residual pressure though; you may want to know about pressure drop elsewhere in the system. Looking at your original post, you say that this is for a metered bulk water station. I'm not familiar with these, but the problem reminds me of a fire flow analysis, where the modeler may want to know the pressures resulting from a fire engine connecting to a fire hydrant. In your situation, how would the connection work? Would a pump be involved? Can you make a conservative assumption on the outflow that will occur when a truck uses the station? (in which case you can simply add this as a demand and use a separate demand alternative to keep it separate from your other scenarios)

Applies To Product(s): Bentley WaterGEMS, Bentley WaterCAD Version(s): 08.11.xx.xx Environment: N/A Area: Modeling Subarea: Original Author: Scott Kampa, Bentley Technical Support Group Error or Warning Message How can a user fix the WaterGEMS or WaterCAD error message "Network Unbalanced" or "Cannot solve network hydraulic equations". A "Reverse flow detected" may be encountered as well. Explanation The "Network Unbalanced" and "Cannot solve network hydraulic equations" user notification means that the program could not converge on a balanced solution within the maximum number of trials. The difference between these is that the "Network unbalanced" message can occur for individual time steps, while the "Cannot solve network hydraulic equations" does not specify a time step where the issue occurs. Between calculation iterations, the program checks the relative change in flow, which has a default value is 0.001. If the relative flow change is below the "Accuracy" value designated in the calculation options, the time step is balanced or is said to have converged. If the relative flow change is greater than the Accuracy value, the program will try another iteration. If the program reaches the maximum number of trials without finding a solution, the "Network Unbalanced" user notification is generated. How to Avoid The first thing to do is to check to make sure your entire network is connected properly. Perform a validation (Analysis > Validate) on the model to see if there is information on possible issues in the model. If there are messages that are related to specific elements, double-click on it or right-click and choose "Zoom To", which will select the element in the drawing pane. Check the properties and setup of the element to see if there are issues related to data entry or orientation. If the element is a node, you can click and drag the element to make sure it is connected to all the pipes it is supposed to be connected to. Nodes that are not connected to pipes can occur if you used ModelBuilder to create the model. If your junctions are not connected properly you can use the Batch Pipe Split tool , which will allow you to connect the junctions to the pipes they are supposed to be connected to by splitting them. The Network Navigator tool can help you locate topological issues. (check the "See also" for two links on this) If there are not validation issues, make sure the setup of elements are accurate. Pay close attention to logical controls, valve settings, and valve status, empty or full tanks, and near zero flows as these are common causes of the issue. If you have a check valve on the pipe directly downstream of a pump, consider removing the check valve. In WaterGEMS and WaterCAD, a pump will not allow reverse flow. A check valve on the downstream pipe is redundant and can sometimes impact the model calculations. If you have a significant portion of your model with zero flow (such as the case when modeling "static" conditions), the numerical solver will have a hard time converging on a balanced solution. The reason is because the relative flow change between trials will typically be large in this case, since the numbers that it is dealing with are very close to zero. Check the link in the "See Also" section below for more on this. If you have multiple fixed or variable speed pumps (VSP) discharging into the same pressure zone, this can also cause numerical instability. If the real system includes some manual operation of the pumps in this case, consider matching that in the model by using time based controls or a pattern (is variable speed pump = true, type = pattern). If you have GPV's check the "Flow Demanded" from the calculation summary (Analysis > Calculation Summary) at the time step of the red user notification. If the flow going to that GPV is not enough to provide the flow demanded examine the GPV headloss curve to make sure the maximum value of the curve is large enough to cover that flow. For example, if the flow demanded is 850 gpm check the largest value on the curve is at least 851 gpm. Confirm that tanks have the proper elevation data, including any top-fill tanks that may be in the model. If the model setup is accurate, you can find additional steps to help with this issue below. Intra-Trial Status Messages For EPS simulations you might find more clues to solving your problem by either: 1) (if you have V8i SELECTseries 5 or greater) - Click the timestep in question in the Calculation Summary, then click the Intra-Trial details tab. This identifies elements that are changing status between trials 2) (if you have V8i SELECTseries 4 or earlier) - open the .RPC file. This file contains a log of the trials that the program runs through when it is trying to converge on a solution. In order to open this file browse to the folder where your model is saved; that is where the .RPC file will be. You can open this file in a text editor, such as Notepad. Look down the trial list until you start to see the trials where there are elements that are constantly changing status (for valves a status change may be going from "active" to "closed" or vice versa and for pumps it could be going from "On" to "Off") over consecutive trials. The elements that have a constantly toggling status could be a clue to where your problem lies. If this happens often for certain elements then your model may be to tightly constrained or controlled and you should attempt to simplify the model where possible. If you are seeing many valves oscillating status in a particularly challenging timestep, this is an indication that their configuration should be checked, to ensure that they are correct and not accidentally "fighting against each other" due to the assumed settings. You might be able to adjust the configuration of those valves (in some cases with a conservative assumption) to make the model more simple and stable. In other words, try to address the root of the problem instead of tweaking the options to get it to work. This should be better in the long run if you can identify (with help from the intra-trial status messages) some changes that stabilize the model. For example this article talks about challenges like this that can occur with PRVs in parallel. Of course in some cases you may need to adjust the calculation options, in which case it does make sense to be extra cautious. Calculation Options Several advanced calculation options are available to help with convergence in challenging situations where the model data input and topology has been checked. First, you can try increasing the number of trials. To do this, go to Analysis > Calculation Options. Under the "Steady State/EPS Solver" section, double-click on the active calculation option to view the properties. Find the property field "Trials" and set this to a higher value, such as 400. In many instances, this is enough to allow the program to find a viable solution. Note that the program will not necessarily run all 400 trials, but will only use the number of trials it takes to come up with a viable solution. If that doesn't work, you can also try to increase the Accuracy field (also in Calculation Options properties) to a higher value, such as 0.01. This will mean that the relative flow change between iterations can be higher, which may allow the program to find a solution. You do not want the accuracy value to be too high though, or it may compromise the results. You can also try changing the Engine Compatibility field. The latest solver is "WaterGEMS 2.00.12". If you are using an older solver, using the latest may help as well. If you have PRVs or PSVs in the model, you can also try adjusting the calculation option Damping Limit. Change the value so that it is 10 times the accuracy. So if you have an accuracy of 0.001, set Damping Limit to 0.01. If you have check valves or FCVs, as well as PSVs or PRVs, you can adjust the calculation options "Convergence Check Frequency" and "Convergence Check Cut Off" to higher values. Note that these options are only available for the solver "WaterGEMS 2.00.12". Much more information on these can be found at the following support solution: Engine Compability modes and Calculation Options . See Also "Network Unbalanced" problems with zero flow/ static conditions Engine Compability modes and Calculation Options Using The Network Navigator Using Network Navigator's Powerful Queries

Applies To Product(s): Bentley WaterGEMS Version(s): V8i SELECTSeries 2 Environment: N/A Area: Calculations Subarea: N/A Original Author: Kathy Wiggins, Technical Support, Wayne Hartell, Advisory Software Engineer, Tom Walski, Bentley Fellow Overview The purpose of this article is to explain the engine compatibility modes and related advanced calculation options. These have been added to Bentley WaterCAD/WaterGEMS/Hammer V8i SelectSeries 2 (SS2). Additional information may be found in the Help menu of each program. Summary Background Starting with V8i SELECTseries 2, the ability to switch between two different versions of the EPANET and Bentley-Enhanced numerical solvers was introduced. This allows the user to provide results directly compatible with a certain version, for example when exporting back to EPANET. Newly created models will default to the Bentley-Enhanced 2.00.12 version of the EPANET solver. Previous models will retain the solver version used by the version they were last saved in . Four additional calculation options are available when using the 2.00.12 numerical solver version, as seen under the ‘Hydraulics’ section of the Calculation Options dialog. Each option will be covered in detail below. See further below for a more detailed background. Engine Compatibility Modes The ‘Engine Compatibility’ Calculation option in V8i SS2 replaces the ‘Use EPANET Compatible Results?’ option, as seen in V8i SELECTSeries 1 and earlier. When set to true, you were using EPANET 2.00.10. The software now includes compatibility modes, to choose between EPANET 2.00.10, as well as the revised engine changes in EPANET 2.00.12. The four engine compatibility modes available: WaterGEMS 2.00.12 – this engine is based on the EPANET 2.00.12 engine, including Bentley modifications. Choose this option to get all the latest engine improvements and fixes made by Bentley and an engine mode that is based upon EPANET 2.00.12.This is the default for new models. Meaning any new model created in WaterGEMS V8i SS2 will default to the ‘WaterGEMS 2.00.12’ engine compatibility option. WaterGEMS 2.00.10 – this engine is based on the EPANET 2.00.10 engine, including Bentley modifications. Choose this option to maintain compatibility with previous versions of WaterGEMS (meaning V8i SS1 and earlier) where the computational engine is based upon EPANET 2.00.10. This is the default for upgraded (existing) models. Note: the ‘Use Linear Interpolation for Multi Point Pumps?’ option is FALSE by default in existing models as well. These default options are designed to make the transition smoother for users. IF an existing model has ‘Enable EPANET Calculation Results?’ set to TRUE, then the ‘Use Linear Interpolation for Multi Point Pumps?’ option is hidden (as it will not apply). EPANET 2.00.12 – models run using this engine have results that are compatible with EPANET 2.00.12. If choosing a version of the EPANET engine, any enhancements, calculation corrections, bug fixes, etc. made by Bentley will be disabled to match the specific EPANET version results. Imported EPANET models will default to the appropriate EPANET version. EPANET 2.00.10 – models run using this engine have results that are compatible with EPANET 2.00.10. Note : The following engine compatibility matrix is included in the Help file (Modeling Capabilities>Calculation Options>Engine Compatibility Calculation Option). Additional Calculation Options If the user has selected either the WaterGEMS 2.00.12 or EPANET 2.00.12 versions, there are three additional calculation options now available. These options are the same for both the EPANET and WaterGEMS 2.00.12 engines. Convergence Check Frequency – The Convergence Check Frequency option sets the number of solution trials that pass during the hydraulic balancing before the status of pumps, check valves, flow control valves (FCV) and pipes connected to tanks are once again updated. The default value is 2 (meaning that status checks are made every other trial). A value equal to the maximum number of trials would mean that status checks are made only after a system has converged. The frequency of status checks on pressure reducing (PRV) and pressure sustaining valves (PSV) is determined by the Damping Factor option. Convergence Check Cutoff – The Convergence Check Cutoff option is the number of solution trials after which periodic status checks on pumps, check valves, flow control valves (FCV) and pipes connected to tanks are discontinued. Instead, a status check is made only after convergence is achieved. The default value is 10 (after 10 trials, instead of checking status every “convergence Check Frequency” trials, the status is only checked after convergence is achieved). Damping Limit – The Damping Limit is the accuracy value at which solution damping and status checks on PRVs and PSVs should begin. Damping limits all flow changes to 60% of what they would otherwise be as future trials unfold. So, instead of checking the status of control valves at every iteration (which could result in oscillations in some cases) damping relaxes that check to only occur when the relative flow change is getting close to the target accuracy (e.g., 0.01, versus 0.001). The default value is 0 (zero), which indicates that no damping should be used and that status checks on control valves are made at every iteration. Damping might be needed on networks that have trouble converging. A limit of 0.01 is suggested (relative to the default calculation hydraulic accuracy of 0.001). See further below for a more detailed explanation. Additional Post Calculation Warnings Post Calculation warnings have been added to advise a user if they are using any features that are NOT supported by EPANET when they are running with one of the two EPANET compatibility settings. These are POST calculation and will not be displayed when validating a model (i.e. these calculation warnings are only displayed when computing a model. Detailed Background The hydraulic engine upon which the WaterGEMS and WaterCAD numerical engine is based, is the US EPA's EPANET v2. EPANET v2 was originally developed in the late 90's (first released to the public in 2000) and was actively developed by the US EPA until 2008. During those years, changes were made to the computational engine by the US EPA in response to feedback from users. In the history of the engine development there were and continue to be (as of this writing in August, 2016) two main stable release points as follows. EPANET 2.00.10, released 6/24/2002. EPANET 2.00.12, released 2/25/2008. That is, EPANET 2.00.10 was the result of 2 years of public feedback that stood un-modified for 5 years until 2007, and EPANET 2.00.12 has been the standard since 2008. EPANET 2.00.12 was the release that included a parameter for controlling the damping limit, Convergence Check Frequency and Convergence Check Cutoff. You will note corresponding to the above stable releases, that in WaterGEMS, we support an engine compatibility setting, that has four possible options as follows: 1. EPANET 2.00.10 2. EPANET 2.00.12 3. WaterGEMS 2.00.10 4. WaterGEMS 2.00.12 The meaning of these four settings, in the same order as listed above, is: 1. An engine closely based upon EPANET 2.00.10. This engine attempts to match the result obtained by EPANET 2.00.10. 2. An engine closely based upon EPANET 2.00.12. This engine attempts to match the result obtained by EPANET 2.00.12. 3. An engine based upon EPANET 2.00.10, but with corrections and enhanced features. 4. An engine based upon EPANET 2.00.12, but with corrections and enhanced features. In reality, it is always the same computational engine behind the scenes, but the compatibility setting changes the way the engine behaves in accordance with the above descriptions. The words "attempts to" (for cases 1 and 2) means that the engine version will faithfully reproduce any known computational errors that exist in the corresponding EPANET version in order to match the EPANET results of the same version. For that reason, you would only want to use an EPANET compatibility mode in the case you are exporting to EPANET and wish to match hydraulic results with that version of EPANET. The words "based upon" (for cases 3 and 4) could also, for most intents and purposes, be interpreted as "using the convergence strategy of". One of the more significant changes made between EPANET 2.00.10 and 2.00.12 was to alter the convergence strategy used for control valves. This was presumably in response to cases (models) where the previous strategy was unable to solve correctly. Cases that could not solve would typically manifest in unbalanced calculations where pairs of control valves would oscillate. The convergence strategy was modified in a number of ways. One modification was to initialize control valves to ACTIVE (versus explicitly starting only PRVs and PSVs as OPEN). The EPANET 2.00.12 based mode does this in comparison to the EPANET 2.00.10 based mode, but otherwise there is no effect on starting point (other than the continued fact that the solution for one time-step in an EPS run forms the starting point for the next time's simulation). Or in other words, the EPANET 2.00.10 based engines use a different starting point to the EPANET 2.00.12 based engines, but changing engine options does not affect starting point. Another modification to the convergence strategy is that the concept of damping (2.00.11) and a damping factor (2.00.12) was introduced, in order to assist with the convergence of problematic models. The change was simply to no longer check the status of control valve every iteration (which could result in oscillations in some cases) and to relax that check to only occur when the relative flow change is getting close to the target accuracy (e.g., 0.01, versus 0.001). In EPANET 2.00.11 the damp limit was fixed at ten times the hydraulic accuracy, however, in EPANET 2.00.12 it was exposed to allow the user to change it (and it defaults to OFF (0) in that case, which reverts to the same case as EPANET 2.00.10, unless a user wishes to enable it). Regarding the Damping Limit, one must first understand why the damping is in place, and not some other kind of modification. The computational engine essentially solves one linear continuity equation for each node and one non-linear energy equation for each loop. Since the equations are non-linear, an iterative method must be used. Once the equations are set up, the solution converges very efficiently, however, once a control valve changes status, the equations themselves change. Thus, the computational engine is "shooting at a moving target", so to speak. In order to help the equations to stay stable for a while, the damping comes into play. Too much damping, however, can slow down the process. So damping affects the convergence checks that are made on valves and then the subsequent flow changes applied to all hydraulic links, by reducing the magnitude of the flow changes. The damping option aims to allow the solution to converge to within a reasonable level before checking control valve status, and then when it has converged to within a certain value, to smooth out the effect of oscillating valve status changes and improve the final convergence in such situations. As an analogy, think of the damping as something similar to tweaking the feedback amplifier in a feedback control system. The damping tries to avoid overshoot. In so far as computed results go, the main factor here is the specified hydraulic accuracy. Valve statuses are checked for the converged solution so using damping should not affect the result in that way; it's merely a means to improving the ability of the algorithm to find a valid solution. Converged results achieved with different calculations in play are not guaranteed to be exactly the same since the results in part may depend on the path taken to convergence, however, the default hydraulic accuracy value normally means that for most practical purposes and systems that results do not significantly vary (by any appreciable value in an engineering sense). You may wish to perform a sensitivity analysis on your model with varying hydraulic accuracy to see whether the model you have built solves well with the default hydraulic accuracy, or whether a tighter value is required (at the potential trade-off of more hydraulic trials). With that said, you should adopt the set of calculation options that results in consistent and stable convergence, and if that is not readily obtainable, then you should seek to eliminate the causes of such stability issues from the model itself. See Also Drawbacks of Using Damping Limit? Troubleshooting "Network Unbalanced" or "Cannot solve network hydraulic equations" user notification

Note that I have updated the following wiki articles based on the information in this discussion: Engine Compability Modes and Calculation options Troubleshooting "Network Unbalanced" or "Cannot solve network hydraulic equations" user notification