Applies To Product(s): Bentley WaterCAD, Bentley WaterGEMS Version(s): V8 XM, V8i Environment: N/A Area: Output and Reporting Subarea: N/A Original Author: Jesse Dringoli, Bentley Technical Support Group Overview This Technote explains how to interpret and troubleshoot calculated results for an automated fire flow analysis in WaterCAD or WaterGEMS V8 XM or V8i. Before reading this Technote, it is recommended that the user complete the Fire flow Quick start lesson. This is located in the WaterCAD/WaterGEMS help, under Contents > Quick Start Lessons > Automated Fire Flow Analysis. Background Fire Flow analysis is a common tool used in WaterCAD and WaterGEMS to ensure enough protection is provided during fire emergencies. The user is able to enter constraints in order to determine how much fire flow is available at hydrants while adequate system pressure is maintained. Several tools available to aid in understanding fire flow results. How Does Automated Fire Flow Work? Fire flows are computed at each node by iteratively assigning demands and computing system pressures. When you execute a fire flow analysis, WaterCAD\GEMS will: Calculate a steady-state simulation for all nodes designated as fire-flow nodes. At each node, it begins by running a Steady-State simulation using only non-fire demands, to ensure that the fire flow constraints (e.g., minimum residual pressure, minimum zone pressure) that have been set can be met without withdrawing any Fire Flow from any of the nodes. Evaluate the Fire Flow Upper Limit and Available Fire Flow at each of the fire-flow nodes. Assuming the fire flow constraints were met in the initial run, the program performs a series of steady-state runs in which flow is applied to each specified fire-flow node and results are evaluated against fire-flow constraints. Note that the fire flow for each individual node is evaluated using a separate analysis (i.e., needed fire flow is not applied simultaneously to all fire-flow nodes). The program performs a series of steady-state analyses in which the Fire Flow Upper Limit discharge is applied to each node in turn. If the fire flow constraints are met for the Fire Flow Upper Limit discharge, the node satisfies the fire flow constraints and no further analysis is required for that node. The program then performs a series of steady-state analyses in which it iteratively assigns lesser demands to nodes that do not meet Fire Flow Upper Limit constraint to determine the Avalable Fire Flow. The Available Fire Flow is the maximum fire flow that each node can supply without violating fire flow constraints. If the Available Fire Flow is greater than or equal to Needed Fire Flow, the node satisfies the fire flow contraints. If Available Fire Flow is less than Needed, it does not. Run a final Steady-State calculation that does not apply Fire Flow demands to any of the junctions. This provides a baseline of calculated results that can then be compared to the Fire Flow conditions, which can be determined by viewing the results presented on the Fire Flow tab of the individual junction editors, or in the Fire Flow Tabular Report. Interpreting the Fire Flow Alternative Configuration for an automated fire flow analysis is done under the Fire Flow alternative. This is found under Analysis > Alternatives > Fire flow. When computing a scenario, the fire flow alternative assigned to that scenario is used. At a minimum, you should specify values for the needed Fire Flow, Fire Flow Upper Limit, Apply Fire Flow By, Residual Pressure Lower Limit, Zone Pressure Lower Limit and Fire flow nodes selection set. Below is an explanation of each of the main fields found in this alternative (when double clicking on it): Note: If the above options need to be configured differently for each junction/hydrant, you can specify "local" fireflow constraints by clicking the "specify local fireflow constraints?" check box next to the junctions/hydrants in the list at the bottom of the fireflow alternative. If this box is not checked, that particular fireflow node will utilize the global constraints entered at the top of the fire flow alternative. Note: it is important to understand that for the minimum zone pressure constraint, the program checks pressures for all other nodes in the model that are assigned to the same zone as the fireflow node in question. The zone is an attribute of the node. Say for example there are two nodes in the fireflow selection set: J-1 and J-2. J-1 is assigned to Zone A and J-2 is assigned to Zone B. Fireflow nodes are checked independently during the analysis, so when J-1 is being computed, the program will check pressures at all other nodes that are also assigned to Zone A and compare against the minimum zone pressure constraint. Then, when the analysis moves on to J-2, it will be checking pressure at all nodes assigned to Zone B. So, the program isn't running a fireflow analysis on a particular zone - it considers pressures at nodes assigned to certain zones, based on the fireflow node it is currently analyzing. Configuring your model to run a fire flow analysis After you've configured your fire flow alternative, the next step is to assign that alternative to the scenario you would like to compute. First, go to Analysis > Calculation Options. If you have an existing calculation option set that you're using in other scenarios, click on it and click the "duplicate" button. If you'd like, you could also click the "new" button to create a new calculation option set. Provide a meaningful name for your new calculation option set and double click it to open the properties. In the properties, set the Calculation Type to Fire Flow. Next, go to Analysis > Scenarios. Create a new scenario by choosing New > base scenario, or right click an existing scenario and choose "child". Provide a name for the new scenario, such as "Automated Fire Flow Analysis". Double-click your fire flow scenario to open the properties. Select your fire flow alternative from the dropdown next to "Fire Flow" and select your fire flow calculation option from the dropdown next to "Steady state/EPS solver Calculation options". Make your fireflow scenario current by right clicking it's name in the scenario manager and choosing "make current" or by selecting it from the Scenario dropdown menu bar at the top of your WaterCAD/WaterGEMS window. At this point, the automated fireflow analysis can be computed by going to Analysis > Compute. To understand the process that WaterCAD/GEMS uses, please see the section further above, entitled "How does the automated fire flow routine work?". Fire Flow in SELECTSeries 6 of WaterGEMS With the release of WaterGEMS SS6, the SCADAConnect Simulator has new option of Fire response of adding the fire flow demand to an element for certain period of time. Fire Response enables you to place a fire demand (or other emergency flows) at a junction for a period of time to determine its impact on pressure and flows and possibly test alternative ways of responding to the fire. The fire response can be found at Home tab or the Emergency Response tab in SCADAConnect Simulator. This is to be used for simulating the operational consequences for a fire. For system wide fire flow capacity analysis, you should use Fire Flow Analysis as specified above. When you are picking the Fire Response, a dialog appears. You then need to pick the node where the fire flow is placed and complete the fire flow demand, start date/time and duration of fire demand. In some cases, fire fighters will use a large flow to control a fire for a few hours and then a lower flow to finally extinguish the fire. This would correspond to two entries in the Active fire flow dialog. An example of that setup is shown below. Make sure that you are making the Fire response active in the window below. You can directly compute the scenario from the SCADAConnect Simulator tool or in a usual way. You can see the difference in the results with the active fire flow demand in the SCADAConnect Simulator after computing the scenario. The image below shows the symbol for a fire placed on a hydrant element. Interpreting Automated Fire Flow Results There are several ways you can view the results of your automated fire flow analysis. Below describes the most common. Using the Fire Flow Report Make sure that your Fire Flow Analysis scenario is the current scenario and that you've succesfully computed it. Click Report > Element Tables > Fire Flow Report. The Fire Flow report is essentially a custom flextable including only the relevant fire flow results for both junctions and hydrants. The fields seen here can be added to the junction and hydrant flextables, but it is generally more convenient to use and keep this separate fireflow flextable when reviewing results of an automated fire flow analysis. Note: if you look at the general results in other flextables, such as "pressure" in the junction table, you will be viewing the baseline steady state results for your model, without any fire flow demands present. It is recommended that you only look at the fireflow table, so as not to be confused. The first thing you will notice is a column titled "Satisfies Fire Flow Constraints?" This will be checked only if the particular fire flow node (designated by the "label" for each row in this report) can provide at least the needed fire flow, while satisfying the fire flow constraints - the pressure constraints and sometimes the velocity constraints, if applicable. Here is a description of some of the other fields (columns) available in the fire flow report: Note: if your table does not display one or more of the below fields, you can add it using the yellow "edit" button at the top of the flextable. Is Fire Flow Run Balanced? "If set to true then the fire flow analysis was able to solve". Specifies whether the fireflow run was balanced or not for the given node. Using the Fire Flow Results Browser The Fire Flow Results Browser will allow you to check results for others elements in your model, during individual fire flow runs. Normally, the only results available after a fire flow analysis are the residual pressures at each fireflow node and minimum zone/system pressures. If you'd like to see other results, such as pipe velocities, hydraulic grades, valve status, etc, during a specific fire flow test, you can use this tool. First, you'll need to make sure that you have set up your Fire Flow Alternative for this function before running the fire flow analysis: After you have set up your Auxiliary Output Settings and run the Fire Flow analysis, go to Analysis > Fire Flow Results Browser. Select a fire flow node from the list to see the results for its adjacent pipes, and for the elements included in the output selection set (defined in the fire flow alternative). With a fire flow node selected, you can then establish color coding, annotations or simply check auxiliary results using the elemenet properties or flextables. For example, if you wanted to see the status of Valve X when Hydrant Y was flowed, click Hydrant Y in the list and then open the properties of Valve X. Color Coding Fire Flow Results Another good way to review an automated fire flow analysis is to use color coding. For example, you can color code junctions and hydrant based on the values for total available fire flow, to see areas where the available fire flow is lacking. Another useful color coding could be one based on the "satisfies fire flow constraints?" attribute. For example, you could color code such that junctions with "false" for this attribute show up as red, with a larger size. This would be done by using the "color and size" option, in the color coding dialog. You can also use color coding with the fire flow results browser. For example, you could color code pipe velocities so that when you click fire flow nodes from the fire flow results browser list, the colors will update to show the velocity distribution when that particular node was flowed. Troubleshooting Fire flow results not available In some cases, you may notice that the results in your fire flow report show "N/A" after computing the model. Make sure your scenario is set up correctly. Ensure that the correct fire flow alternative is assigned to the scenario that you are computing and ensure that its calculation options have the calculation type set to "fire flow". If this is set to "hydraulics only", fire flow results will not be computed. Make sure the scenario computed succesfully. If any messages show up under your user notification (Analysis > User notifications) with a red circle next to them, it means that the calculation failed. You'll need to address these fatal errors first, before results will be available. "N/A" entries can also be caused by omission from the fireflow selection set. In your fire flow alternative, make sure that all the nodes you'd like to study are included in the selection set selected for "Fire flow nodes". The fireflow routine will only analyze and provide results for nodes in this selection set. If desired, a filter can be used in the fire flow report so that nodes not included in the fire flow nodes selection set are not displayed. Make sure that you are not trying to use the fire flow results browser, if you haven't set up your fire flow alternative to save auxiliary results. Doing so can cause results in the fire flow flextable to show "N/A". This can be fixed by clicking the "reset to standard steady state results" button at the top of the fire flow results browser. Understanding why a node cannot provide the desired fire flow In the fire flow report (flextable), you may notice that one or more fire flow nodes does not satisfy the fire flow constraints. Meaning, the total available fire flow is less than the needed fire flow or below what you expected. There are several reasons why this could occur. First, check the calculated residual pressure field. This is the pressure at the fire flow node, at the total available fire flow. So, if this is equal to the residual pressure constraint, it means that the residual pressure constraint would be violated if any more flow was passed, so the fire flow routine stopped. If the calculated residual pressure is less than the residual pressure constraint, it probably means that the residual pressure was below the constraint even with the base demands (with no additional fire flow added). In this case, you should check the pressures in the model with baseline demands - they should all be above the constraints entered in the fire flow alternative. Next, check the calculated minimum zone pressure field. This is the lowest pressure out of all nodes in the same zone as the fire flow node in question, at the total available fire flow. So, if this is equal than the minimum zone pressure constraint that you entered, it means that the fire flow constrainted would be violated if any more flow was passed. So, the fire flow calculation stopped and reported the total available fire flow such that this would not be violated. If the calculated minimum zone pressure shows as less than the constraint, it probably means that the pressure somewhere else in that zone was less than the constraint, even with only the base demands (with no additional fire flow added). You should check the pressures in the model with baseline demands - they should all be above the constraints entered in the fire flow alternative. To check which specific node had the lowest pressure in the zone, check the "Junction with minimum pressure (zone)" field. In many cases, this may be a node at the suction side of the pump or at some other location that you may not be concerned with. In this case, it is recommended that you assign a different zone to these nodes. For example, create a zone called "low" and use that. This way, it won't be in the same zone as any fire flow nodes and thus won't be considered (unless you're using the minimum system pressure constraint). If you elected to use the minimum system pressure constraint in your fire flow alternative, you'll also need to check the calculated minimum system pressure. This is identical to the zone pressure constraint (see above), except it checks pressure at ALL nodes in the model. You can also check the "Junction with minimum pressure (system)" field to see which node caused the fire flow routine to stop. If you elected to use the Velocity constraint in your fire flow alternative, you'll also need to check the "Velocity of maximum pipe" and "Pipe w/ Maximum Velocity" fields. If the velocity in any pipe inside the chosen "pipe set" selection set exceeds the constraint you entered, the fire flow routine will stop. So, similar to the pressure constraints, you may notice the "Velocity of maximum pipe" is equal to or less than the constraint, indicating the reason why no additional fire flow could be extracted. Lastly, in rare cases, the fire flow routine may stop at a certain Total Available fire flow due to an unbalanced model. Meaning, at certain flow rates, the steady state simulation may not be able to converge on a balanced hydraulic solution within the maximum number of trials. This can occur in large, complex models, with low or near-zero flows, and/or when other data input in the model is not correct. It causes the results to be invalid and the fire flow run to stop. If your available fire flow is less than the upper limit, yet all the constraints described above are not violated, chances are that this was caused by the network becoming unbalanced. To check, try running a manual fire flow analysis on that junction. For the manual run, just make sure the calculation type in your calculation options is set to “Hydraulics only” and that you have entered the value for the total needed fire flow as an additional, fixed demand on that junction. Run the analysis and check your user notifications for an unbalanced error. One solution to this is to increase the max trials value in the calculation options, but you should also consider investigating other causes, such as data entry errors. Note: be aware of the presence of local fire flow constraints. At the bottom of your fire flow alternative, you can set node-specific constraints, which override the global constraints set at the top. This could potentially cause confusion when viewing fire flow results. For example, the total available fire flow for a certain node may be less than what you believe the needed fire flow value is, but still showing as satisfying the fire flow constraints. If you had a local "needed fire flow" set to a lower value, this could be valid. So, make sure you include and check the "Fire flow (needed)", "Fire flow (upper limit)" "Pressure (residual lower limit)" and "Pressure (Zone lower limit)" fields in your fire flow report/flextable. Consider the following Fire Flow Flextable, with no minimum system pressure or maximum velocity constraints used: J-10 - This node passed the fire flow test, as indicated by the "Satisfies fire flow constraints?" check box. It reports a Total available fire flow of 2012.68gpm, which is above the total needed fire flow of 462.68. Although the needed fire flow is actually 450.00gpm, we have chosen to add fire flows to base demands, and there is a base demand of 12.68gpm on this node. The total available amount of 2012.68gpm accounts for this base demand as well. Meaning, the total demand on this particular node can be up to 2012.68gpm without violating any fire flow constraints. The reason is because at the upper limit (2012.68gpm), both the residual pressure and minimum zone pressure are 59.2psi, which is above the constraints. The fire flow analysis stopped at the upper limit value to prevent unrealistically high flows from being computed. J-169 - This node passed the fire flow test with a reported total available fire flow of 557.82gpm. This is above the needed fire flow but below the upper limit. The reason why the fire flow test stopped at this flow is because a higher flow rate would violate the zone pressure constraint. As you can see, the calculated minimum zone pressure (lower limit) is equal to the user-entered minimum zone pressure constraint of 20psi and the "junction w/ minimum pressure (zone)" shows J-170. This means that although the residual pressure at J-169 (24.3psi) is above the constraints, J-170 is in the same zone as J-169 and had the lowest pressure, 20psi. J-171 - This node passed the fire flow test with a reported total available fire flow of 489.28gpm. This is above the needed fire flow but below the upper limit. The reason why the fire flow test stopped at this flow is because a higher flow rate would violate the residual pressure constraint. Although the minimum zone pressure of 23.5psi is above the 20psi constraint, the residual pressure (calculated pressure at J-171) is equal to the residual pressure constraint of 15psi. At a higher flow rate than 489.28gpm, the residual pressure would drop below 15psi, which would violate the pressure constraint. So, the fire flow analysis reports the maximum flow available without violating the constraint. J-159 - This node failed the fire flow test, as indicated by the unchecked "Satisfies fire flow constraints?". This is because the total available fire flow is 327.06gpm, which is less than the total needed flow of 453.17gpm. The reason why this node can only supply 327.06gpm is because of the residual pressure constraint. As you can see, even though the minimum zone pressure (60.4psi) is well above the zone pressure constraint, the calculated residual pressure is equal to the residual pressure constraint. This means that the pressure constaint would be violated at a flow any higher than 327.06gpm. J-154 - This node failed the fire flow test, because the available fire flow of 289.24gpm is less than the needed fireflow of 455.39. The reason it can only supply this much flow is because of the minimum zone pressure constraint. As you can see, although the residual pressure (28.5psi) is above the constraint, the minimum zone pressure is equal to the constraint, with J-158 as the "junction w/ minimum pressure (zone)". This means that J-158, which is in the same zone as J-154, is preventing any additional flow from being extracted, without violating the minimum zone pressure constraint. J-1 - This node failed the fire flow test with a total available flow of zero. This means that even without any demand at all on J-1, the baseline pressures in the model fall below the constraints. This is indicated by the calculated residual pressure of -1.4psi. This means that with zero demand on this node, the pressure at J-1 is -1.4psi. Since this is well below the constraint of 20psi, the fireflow test fails and the available fire flow is reported as zero. This particular junction is located on the suction side of a pump station, so it probably should be excluded from the fire flow nodes selection set. Meaning, it is probably unnecessary to compute fire flow for this node. J-2 - This node also failed the fire flow test with a total available flow of zero. In this case, it is because the minimum zone pressure constraint was violated. This means that without any demand at all on this node, the pressure at J-1 is -1.4psi. J-1 is in the same zone as J-2 and as seen above, it is at the suction side of the pump. So, assigning a new zone to J-1 should resolve this problem, since it would no longer be considered during the check of zone pressure. J-3 - This node, along with other junctions below it, show "N/A" for all calculated fields. This is because these nodes are not included in the fire flow nodes selection set , set in the fire flow alternative. Fire flow results browser not working If you attempt to use the fire flow results browser tool, you may run into problems if it is not configured correctly. Symtoms could be: Nothing showed up in the list. Some results show "N/A" in the properties/flextables after clicking a fire flow node from the list. This is caused by improper configuration in the fire flow alternative. Open the fire flow alternative and check the "Auxiliary output Settings" section. If you'd like to be able to check auxiliary results for any fire flow node, regardless of whether it passed or failed the "needed fire flow", select "All nodes" for the "Fire flow auxiliary results type". Doing this will ensure that all nodes show up in the list. At this point, at a minimum, you will be able to see auxiliary results for pipes adjacent to the fire flow node that you select in the results brower. If you'd like to see results for more elements, you'll need to choose a selection set for the "Auxiliary output selection set". If you want to be able to see auxiliary results for all nodes, you can create a selection set of all nodes. To do this, close the fire flow alternative, go to Edit > Select All. Right click anywhere in the drawing pane, choose "create selection set" and give it a name, such as "ALL ELEMENTS". Then, select this in your fire flow alternative for the output selection set. Now, when you compute the fire flow simulation, you'll be able to check results for all elements in the model, for your fire flow nodes. Note: the more fire flow nodes available in the list and the more elements included in the output selection set, the longer the calculation will take to perform and the more disk space it's saved results will take up. See Also WaterGEMS V8 Automated Fire Flow FAQ Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs WaterGEMS V8 Automated Fire Flow FAQ [[General WaterGEMS V8 FAQ|General WaterGEMS V8 FAQ]] WaterGEMS V8 Modeling FAQ Hydraulics and Hydrology Forum Whats new in WaterGMES SS6 SCADAConnect Simulator for WaterGEMS SS6

I tested the example project file and had no issue getting the merge nodes tool to work from the right click menu. I then opened my project file and IT WORKED!!! Problem solved. I'm wondering if my pc just needed a hard re-boot and re-opening my .mxd. Thanks for your help Jesse and Kristen!

Before you start using Darwin Designer, you need to develop a good, sound system as a starting point. To do this, you need to manually design the system and run many, many steady and EPS simulations so that you understand the issues in the system. It may be that you are trying to serve a node that is at too high of an elevation or you have a pump curve that doesn't match the system or you have placed the demands with the wrong units. As a general rule, before you try to optimize anything, you need to simulate it to the point where you have a deep understanding of how the system performs and what the key issues are in the design.

Hmm, strange. Glad to hear its working now though!

Product(s): Bentley SewerGEMS Version(s): 08.11.03.77 Environment: N\A Area: Modeling Subarea: N\A Problem Can SewerGEMS be used to model backflow through a catch basin and into a gutter? In other words, can the flow from a catchbasin vault back up and overflow into the gutter, pass downstream and approach the next inlet? Problem ID#: 89471 Solution This can be modeled in SewerGEMS and CivilStorm V8i SELECTseries 3 (or higher) using the EPA-SWMM solver.This method is internally referred to as the Two Node Solution. This case is used in the following inlet types: HEC-22 Catalog Inlet in Sag using any routing method. A user defined, catalog depth-capture flow curve in sag using any routing method. HEC-22 Catalog Inlet On Grade using Uniform, Kinematic Routing Methods. A user defined, catalog depth-capture flow curve on grade using Uniform, Kinematic Routing Methods. Max Capacity, using Kinematic or Uniform flow Routing. Percent Capture, using Kinematic or Uniform flow Routing. Inflow Captured flow curve – using Kinematic or Uniform flow routing. If you look at the below screenshot, this shows a typical setup for an On Grade inlet. The catch basins are connected by a conduit and a gutter. When the SWMM solver is used, it is assumed to be like in the image at the bottom, where the solver will split the catch basin into two nodes, with subsurface and surface flow. Such a setup could allow for backflow in the catch basin to be picked up by the gutter and propagated downstream. See Also

Applies To Product(s): Bentley SewerGEMS, Bentley SewerCAD, Bentley StormCAD, Bentley CivilStorm, Bentley WaterGEMS, Bentley WaterCAD, Bentley HAMMER Version(s): 08.11.xx.xx Environment: Area: Installation Subarea: Original Author: Scott Kampa, Bentley Technical Support Group Problem Description When installing or uninstalling, "Error 1603" or "Error 1605" appears. How to Avoid This is a Windows Installer error which may occur if the particular component is in use or cannot be changed. First, try rebooting the computer, closing all open applications (including Windows Updates if present), then try again. If the installation still fails, try manually installing the errant component. For example if it fails on installing Microsoft .NET Framework 3.5 SP1, close the installation, download .NET 3.5 SP1 from Microsoft's website, and try installing that first. Other prequisites like the Visual C++ Redistributable are also available from Microsoft. For other components, and if you're not sure where to find them, try extracting them manually from the installation file. To do this, open the installation executable file with a compression utility such as Winrar. Inside, you will see the Setup.msi file along with all the other prerequisites. Extract all the files and run the separately, one by one. If you're using Windows 7 or Vista, you may need to right-click on the installation file and choose "Run as Administrator". If this does not help, try uninstalling the old version from Control Panel > Programs and Features. If the same error occurs, try booting the computer in Safe Mode, to ensure that any potentially interfering processes are not running. If all else fails, a third-party installation cleanup utility might need to be used, in case the installation or Registry entries have become corrupt and unable to be removed by the normal uninstallation routine. See the below Microsoft tool: https://support.microsoft.com/en-us/mats/program_install_and_uninstall Also the below article may be relevant: Cannot uninstall software

Product(s): SewerCAD, SewerGEMS Version(s): 08.11.XX.XX Environment: N\A Area: Calculations Problem When using an equation-based Extreme Flow method such as the Babbitt Equation, along with Count Based unit load, the resulting calculated flow does not seem to be following the equation and considering the Extreme flow factor. Solution There are a few key things to check when using count based unit loads with extreme flow factors. 1) Proper model setup - First, ensure that the model is properly configured to use the Extreme flow Method you have configured a) Go to Components > Extreme Flow Setups and select the appropriate extreme flow method for each unit load type b) Go to Analysis > Calculation Options, open the calculation option set for the scenario of interest and select the entry from the "Extreme flow setup" dropdown. c) Select Steady State as the Time Analysis Type 2) Unit count vs population - Keep in mind that the base load is equal to the Loading Unit Count (entered in the manhole properties) times the Unit Load flow rate (entered in the Unit Sanitary Loads dialog). The population is tracked separately to determine the extreme flow factor that will be applied to the total 3) Tracking of population and base load - Keep in mind that at any given point in the network, the total upstream population is tracked; see result field "Population (System Sanitary)". The total *base* sanitary load is also tracked, for each type of contributing upstream unit load type. The total population is then used along with the total base load and the respective extreme flow method for each unit load type to determine the adjusted total "extreme flow" at that point in the network. This is reported as the "Flow (System Sanitary)" result field that you see. 4) Population Units - Be mindful of the unit used in the extreme flow equation's "Population Unit in Equation". Some Extreme Flow equations such as the Babbitt equation use "Capita X 10^3" for the unit, which essentially means that you need to divide the population "P" in the equation by 1000. Example Loading Unit count - 400 Associated Unit load flow - 150 L/d Population Equivalent - 5 capita Extreme flow Method : Babbitt Equation Population Unit in Equation : Capita X 10^3 Proof: EFF = (5+(0*P^1)/((1*(P /1000 ))^0.2) EFF = (5+(0*2000^1)/((2000/1000^0.2) EFF = (5+0)/(2^0.2) EFF = (5+0)/(1.1487) EFF = 4.353 Q = 4.353 X (400 X 150) = 261,165 L/d Note that the division by 1000 in bold above is due to the Population Unit in Equation of Capita X 10^3 See Also Using Extreme Flow Factors

Applies To Product(s): Bentley SewerCAD, Bentley SewerGEMS Version(s): 08.11.xx.xx Environment: N/A Area: Modeling Subarea: Original Author: Scott Kampa, Bentley Technical Support Group Background Extreme flow factors are generally used for computing peak discharges, and therefore are typically referred to as peaking factors or peaking equations. However, since they can also be used to compute minimum discharges, the term extreme flow factor is more accurate and will be used throughout the program and documentation. This article applies to Bentley SewerCAD as well as Bentley SewerGEMS, when the numerical solver is set to "GVF Convex" (the SewerCAD solver). Steps to Accomplish Loading in SewerCAD is done through the Sanitary Load Control Center. Patterns can be applied are generally used for Extended Period Simulations (EPS). With Steady State runs using Unit Loading, a user will want to look at the peak flow to get a conservative analysis of system. That is where Extreme Flow Factors come in. To begin, you need to set up the Extreme Flow. To do this, go to Components > Extreme Flow Setups. To create a new Extreme Flow Setup, click the New button in the upper left. When you do this, a row will be added for each Unit Load associated with the model. You have the option to use a given load by placing a check box in the Use column. The other columns include the Extreme Flow Method and a couple of multipler options. There are a couple of options available to the extreme flow method. If you leave the Extreme Flow Method column set to "None" you can enter a constant. This is the multipler that will be used on the loading derive from the Unit Load in the Sanitary Loading Control Center. However, you also have the ability to use one of several Extreme Flow Methods. To create these, go to Components > Extreme Flows, or click the ellipsis button in the Extreme Flow Method cell in the Extreme Flow Setups dialog. Click the New button and choose from one of the four methods available. If you choose the Table methods, you will have to manually enter the base load value or the population and the extreme flow factor associated with it. Note that the keyboard shortcuts work with this table, so if you have the table values in a format like Excel, you can copy and paste the data into the table. If you choose the Equation methods, you will need to enter the coefficients for the equation. For convenience, the equation used to calculate the Extreme Flow Factor can be found at the bottom of the Extreme Flows dialog. NOTE: When choosing the method, be sure that it matches with your unit loads. For instance, if your unit loading is based on population, you should use a population-based extreme flow factor method. Once you have created the Extreme Flows, you must apply it to the Unit Load. Return to the Extreme Flow Setups dialog. In the Extreme Flow Method, select the table- or equation-based method you wish to use. If there is an extra adjustment you need to apply, you can enter a value for the Adjustment Multiplier. If you do not need to apply any extra adjustment, simply set the values in this column on 1.0. Now that the Extreme Flow Setups are completed, you need to apply them to the Calculation Option of the model. Go to Analysis > Calculation Options and double-click the active calculation option to view the properties. Find the properties field Extreme Flow Setup and set this to the Extreme Flow Setup you wish to use. Now when you compute the model, the extreme flow setup will be applied to the loading of an element. Please note : Extreme flow setups are only used for steady state simulations. They are not used for EPS runs. This is because a peak flow analysis is only valid in a steady state (snapshot of time). See Also Troubleshooting Extreme Flow Results with Count based Unit loads

Applies To Bentley WaterGEMS, Bentley HAMMER, Bentley WaterCAD Product(s): Version(s): 08.11.XX.XX Environment: N/A Area: Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem When trying to import an .INP file into WaterGEMS or WaterCAD, I get an error message, similar to the following message: "The specified EPANET file could not be loaded. Error message: The specified EPANET file contains values with no section. Format does not follow EPANET standards." Solution This may occur in some cases where the EPANET file is in an older format or if it was created from a third-party software. Typically, software developers verify the "correctness" of their exported format by importing a model into EPANET 2 and checking hydraulic results. The issue with this approach is that EPANET 2 itself supports older INP formats and upon opening an INP in EPANET 2, if it detects such older file formats it does silent updates to convert the data into EPANET 2 format. So it is possible that if a model is exported from a third-party software but in an older format, that the .INP file may not fully work in WaterCAD/GEMS, which is designed to support the official EPANET 2 format. The following steps should help with most cases of this issue: 1) Open the file in EPANET and do a "File > Save As" to rename it just to be sure the filename isn't an issue. This saves the file in .NET format. 2) Then in EPANET do a "File > Export > Network", which saves the file back to a .INP format. This new INP file opened in WaterGEMS through the File > Import > EPANET process. See Also Importing or exporting to WaterCAD, WaterGEMS, or HAMMER from other software What are the differences between WaterGEMS/CAD and EPANET?

Applies To Product(s): Bentley FlowMaster, Bentley WaterCAD Version(s): 08.11.01.03, 08.11.XX.XX Environment: N/A Area: Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem Error message: Unrecognized database format "C:\Users\ \AppData\Local\Temp\Bentley\ .fm8.mdb.$$$" when trying to open a project. OR When attempting to open an old model consisting of a .wcd and .mdb file in V8i, the following error occurs: "Unrecognized database format" Solution Open Microsoft Access and use the compact and repair tool in order to repair the database. If that doesn't work please try to restore your backup files using the wiki found here . If you are still having trouble after that please contact technical support by submitting a service request.

Applies To Product(s): Bentley WaterGEMS, WaterCAD Version(s): 08.11.05.61 Environment: N/A Area: Modeling Original Author: , Bentley Technical Support Group Problem My pumps (or other element such as a valve) do not appear to be following their controls. A pump should stay off but it stays on. Solution There are a few things that should be checked to ensure that the controls are set up properly: 1) Check to make sure that the controls in question are enabled in the Operational Alternative. First, with the scenario in question active, navigate to Analysis > Alternatives, then open the Operational alternative assigned to that scenario. Note the control set, click the ellipsis button, then make sure that the controls are present in that control set. If they are not, add them. 2) If you are computing a steady state simulation, check the calculation option set assigned to your scenario and check if the "use simple controls in steady state?" is set to "true". If it is, ensure that the controls in question are marked as Simple control (as opposed to logical). There are also some types of controls that are not supported in steady state (you'll see User Notification for these) in which case you can simply manually set the initial status of the action element based on the condition in that steady state. 3) Make sure you're accounting for all controls currently set on the element in question. For example if the problem is with a pump, open the pump's properties and click the ellipsis button next to the "Controls" "Collection". This will display all the controls currently being used on that element. You may find that there are multiple controls and/or conditions that control the element in question. 4) Use graphs to view the conditions and actions. For example if the control is based on tank hydraulic grade and pump status, select both the tank and the pump, right click > graph, then select hydraulic grade for the tank and flow for the pump. From here you can get a good visual of the condition and the action, to double check if the action is occurring when the condition warrants. 5) Make sure the model is balanced during the timesteps when the control should be operating. In the Calculation Summary, you will see a red icon next to a trial if it is not balanced, plus a message in the tabs at the bottom and in the User Notification window. An unbalanced network indicates instability in the calculation which needs to be resolved before the results can be trusted. See item 6 below. 6) If the status of the action element still doesn't appear to be correct based on the controls, try checking the Intra-Trial Status Messages tab in the Calculation Summary (available in SELECTseries 5 and higher, build 08.11.05.61). This will display status changes that occur during a trial. If you see certain elements switching status in a given timestep, it's an indication that there is some instability causing the status to oscillate. For example if you have a pump turn on and off based on pressure at a junction, it's possible that the act of turning on the pump may instantly trigger the pump to turn back off based on the pressure set points. In this case, the time step may balance on a condition that may appear to be at odds with the control. In this case, you will notice the pump changing status in the Intra-Trial Status Messages tab, when clicking on the time step in question. Another common example would be dynamic valves like PRVs and PSVs. For example a PRV becoming active may cause another PRV to become active, which then causes the first one to become open, and so on. If this occurs, you'll see the PRVs show up multiple times in the intra-trial status messages tab. See Also What is the difference between a Simple Control and a Logical Control?

Applies To Product(s): Bentley HAMMER Version(s): 08.11.xx.xx Environment: N/A Area: Modeling Subarea: Original Author: Scott Kampa, Bentley Technical Support Group Problem Description A pump in a HAMMER model is initially off, in anticipation of performing a pump startup transient run. However, after calculating the initial conditions, the pump is turning on. Steps to Resolve The first thing to check is to see if there is a control associated with the pump. The easiest way to do this is to select the pump and open the Properties display. Find the Operational section and click the ellipsis button in the Controls cell. This will open the controls dialog filtered for just the pump. If there is a control there, it may be turning the pump on based on condition. The two best options you would have would be to either delete the controls associated with the pump or to create a new Control Set that does not include the pump control. More information on creating controls and control sets can be found at this link . If there is a simple control that you want to remain in the model, you can also make an adjustment to the Steady State/EPS solver, which governs the initial conditions calculation. In the Steady State/EPS solver calculation options, there is a property called "Use simple controls during steady state?" If you set this to False, the control will be ignore for a steady state initial conditions calculation. If there are no controls associated with the pump, check the user notifications for any red items, such as Network Unbalanced messages. If a red user notification occurs, the results should not be trusted and the issues mentioned should be fixed before running the transient simulation. This link has details on the Network Unbalanced message and some things you can do to resolve it. The Modeling a Pump Start-Up Transient Event in HAMMER V8i TechNote has information on modeling a pump startup simulation in HAMMER. See Also Pumps not following controls

Applies To Product(s): Bentley WaterGEMS, Bentley SewerGEMS, Bentley CivilStorm, Bentley StormCAD, Bentley PondPack, Bentley SewerCAD, Bentley HAMMER, Bentley WaterCAD Version(s): 08.11.XX.XX Environment: N/A Area: Other Subarea: Original Author: Dan Iannicelli, Bentley Technical Support Group Error or Warning Message 'Unexpected numeric presentation' error occurs when attempting to open an existing model created by another user . Explanation *This explanation uses WaterCAD or WaterGEMS as a an example, but will work for any of the software products. If you open file with file extension .wtg in Notepad or any other text editing software, on line 4 you will see where it says, "ProductVersionLastModified" . The number in quotes next to that is version number of the software the project was last modified in. More detailed instructions for how to check the version number can be found here . It is probably the case where the file was created with a newer version of the software than what is currently being used on the computer. To check the version number on the computer you can go to Help > About inside your program and locate the number in the lower left corner next to the date. It should start like this, 08.11.XX.XX, where X are some numbers. If that is the case you'll have to upgrade the version in order to open this model. Steps for upgrading software can be found here . How to Avoid Make sure the file you are opening is built in an earlier or equal version of WaterCAD/GEMS Newer models will not open in Older versions of WaterCAD/GEMS. You can check the version of the model file by using the steps found here.

Applies To Product(s): Bentley FlowMaster Version(s): 08.11.01.03 Environment: N\A Area: Installation Subarea: N\A Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem When you try to create an .msi file using the command line with the -a command the windows installer package that is created throws a file error when trying to repackage or run it. Solution *This solution uses FlowMaster as an example, but can be used for any of the water or storm sewer hydraulics and hydrology products. To resolve this problem and extract the executable's contents follow these steps: 1) Open a Windows Explorer window and in the top type in "%Temp%" without the quotation marks. This should bring you to "C:\Documents and settings\{user name}\Local Settings\Temp" folder on a Windows XP Operating System or on a Windows Vista operating system or newer "C:\Users\{user name}\AppData\Local\Temp". 2) From a separate window launch your "Flowmaster.exe" file by double clicking on it. Let it proceed to the point where the progress bar is up and moving. At that point look in the other windows explorer window you have open from step 1 and locate the folder that just popped up. The folder should pop up on top of the list. If it doesn't I'd recommend deleting all the files in the temp files folder that you can to make it easier to locate. It will probably have random GUID as a name (e.g. 7ZipSfx.000) and there you'll find the .MSI file. 3) Copy the file and then abort or cancel the setup process

Applies To Product(s): WaterGEMS, WaterCAD, HAMMER, StormCAD, SewerCAD, SewerGEMS, CivilStorm, Flowmaster, CulvertMaster, PondPack Version(s): Various Environment: N/A Area: Installation Subarea: Original Author: Jesse Dringoli, Bentley Technical Support Group Background As a systems administrator, it is sometimes necessary to install one or more of Bentley's Water, Storm and Sewer products silently, so that no prompts appear on the client side. A script may be needed to push this out from a server. Silent Installation Methods The process for silently installing a Haestad product varies depending on the version. Use the table below to determine which method to use with the version you are deploying. Further details on each method are displayed in the sections that follow (below "General"). Product Version Installer Technology Silent install syntax .NET required WaterCAD/WaterGEMS/HAMMER 08.11.06.58 7Zip/Wix /gm2 /ai 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.05.61 7Zip/Wix /gm2 /ai 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.04.58 IEpress/Wix /q:a 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.04.57 IEpress/Wix /q:a 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.04.50 IEpress/Wix /q:a 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.03.19 IEpress/Wix /q:a 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.03.17 IEpress/Wix /q:a 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.03.16 IEpress/Wix /q:a 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.02.31 IEpress/Wix /q:a 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.01.32 IEpress/Wix (older) N/A 3.5 SP1 WaterCAD/WaterGEMS/HAMMER 08.11.00.30 Installshield /s /v/qn 3.5 WaterCAD/WaterGEMS/HAMMER 08.09.400.34 Installshield /s /v/qn 2.0 WaterCAD/WaterGEMS 08.09.165.12 Installshield /s /v/qn 2.0 WaterCAD/WaterGEMS 08.09.165.09 Installshield /s /v/qn 2.0 WaterCAD/WaterGEMS 08.09.165.00 Installshield /s /v/qn 1.1 WaterCAD/WaterGEMS 08.09.155.00 Installshield /s /v/qn 1.1 WaterCAD/WaterGEMS 07.00.061.00 Installshield /s /v/qn 1.1 WaterCAD/WaterGEMS 07.00.027.00 Installshield /s /v/qn WaterCAD/WaterGEMS 6.5120n Wise /s HAMMER 07.01.013.00 Installshield /s /v/qn 1.1 HAMMER 07.00.060.00 Wise /s StormCAD 08.11.05.58 7Zip/Wix /gm2 /ai 3.5 SP1 StormCAD 08.11.04.54 7Zip/Wix /gm2 /ai 3.5 SP1 StormCAD 08.11.03.84 IEpress/Wix /q:a 3.5 SP1 StormCAD 08.11.03.83 IEpress/Wix /q:a 3.5 SP1 StormCAD 08.11.03.77 IEpress/Wix /q:a 3.5 SP1 StormCAD 08.11.02.75 IEpress/Wix /q:a 3.5 SP1 StormCAD 08.11.02.38 IEpress/Wix /q:a 3.5 SP1 StormCAD 08.11.02.35 IEpress/Wix /q:a 3.5 SP1 StormCAD 08.11.00.44 Installshield /s /v/qn 3.5 StormCAD 08.11.00.40 Installshield /s /v/qn 3.5 StormCAD 08.11.00.34 Installshield /s /v/qn 3.5 StormCAD 08.11.00.24 Installshield /s /v/qn 3.5 StormCAD 08.09.081.00 Installshield /s /v/qn 2.0 StormCAD 05.06.014.00 Installshield /s /v/qn 1.1 StormCAD 05.06.012.00 Installshield /s /v/qn 1.1 StormCAD 05.06.007.00 Wise /s SewerCAD 08.11.05.58 7Zip/Wix /gm2 /ai 3.5 SP1 SewerCAD 08.11.04.54 7Zip/Wix /gm2 /ai 3.5 SP1 SewerCAD 08.11.03.84 IEpress/Wix /q:a 3.5 SP1 SewerCAD 08.11.03.83 IEpress/Wix /q:a 3.5 SP1 SewerCAD 08.11.03.77 IEpress/Wix /q:a 3.5 SP1 SewerCAD 08.11.02.75 IEpress/Wix /q:a 3.5 SP1 SewerCAD 08.11.02.49 IEpress/Wix /q:a 3.5 SP1 SewerCAD 08.11.02.46 IEpress/Wix /q:a 3.5 SP1 SewerCAD 08.11.00.52 Installshield /s /v/qn 3.5 SewerCAD 08.11.00.48 Installshield /s /v/qn 3.5 SewerCAD 05.06.014.00 Installshield /s /v/qn 2.0 SewerCAD 05.06.011.00 Installshield /s /v/qn 1.1 SewerCAD 05.06.008.00 Wise /s SewerGEMS 08.11.05.58 7Zip/Wix /gm2 /ai 3.5 SP1 SewerGEMS 08.11.04.54 7Zip/Wix /gm2 /ai 3.5 SP1 SewerGEMS 08.11.03.84 IEpress/Wix /q:a 3.5 SP1 SewerGEMS 08.11.03.83 IEpress/Wix /q:a 3.5 SP1 SewerGEMS 08.11.03.77 IEpress/Wix /q:a 3.5 SP1 SewerGEMS 08.11.02.75 IEpress/Wix /q:a 3.5 SP1 SewerGEMS 08.11.02.49 IEpress/Wix /q:a 3.5 SP1 SewerGEMS 08.11.02.46 IEpress/Wix /q:a 3.5 SP1 SewerGEMS 08.11.01.21 Installshield /s /v/qn 3.5 SewerGEMS 08.11.00.08 Installshield /s /v/qn 3.5 SewerGEMS 08.09.26.17 Installshield /s /v/qn 2.0 SewerGEMS 08.09.025.00 Installshield /s /v/qn 1.1 CivilStorm 08.11.05.58 7Zip/Wix /gm2 /ai 3.5 SP1 CivilStorm 08.11.04.54 7Zip/Wix /gm2 /ai 3.5 SP1 CivilStorm 08.11.03.84 IEpress/Wix /q:a 3.5 SP1 CivilStorm 08.11.03.83 IEpress/Wix /q:a 3.5 SP1 CivilStorm 08.11.03.77 IEpress/Wix /q:a 3.5 SP1 CivilStorm 08.11.02.75 IEpress/Wix /q:a 3.5 SP1 CivilStorm 08.11.02.65 IEpress/Wix /q:a 3.5 SP1 CivilStorm 08.11.02.62 IEpress/Wix /q:a 3.5 SP1 CivilStorm 08.11.01.36 Installshield /s /v/qn 3.5 SP1 CivilStorm 08.11.00.08 Installshield /s /v/qn 3.5 CivilStorm 08.09.26.17 Installshield /s /v/qn 2.0 CivilStorm 08.09.023.25 Installshield /s /v/qn CivilStorm 08.09.20.09 Installshield /s /v/qn PondPack 08.11.01.56 IEpress/Wix /q:a 3.5 SP1 PondPack 08.11.01.54 IEpress/Wix /q:a 3.5 SP1 PondPack 08.11.01.51 IEpress/Wix (older) N/A 3.5 SP1 PondPack 10.01.04.00 Installshield /s /v/qn 1.1 FlowMaster 08.11.01.03 Installshield /s /v/qn 2.0 FlowMaster 08.11.00.03 Installshield /s /v/qn 2.0 FlowMaster 08.01.071.00 Installshield /s /v/qn 1.1 FlowMaster 08.01.068.00 Installshield /s /v/qn 1.1 FlowMaster 08.01.067.00 Installshield /s /v/qn 1.1 CulvertMaster 03.03.00.04 Installshield /s /v/qn 2.0 CulvertMaster 03.02.00.01 Installshield /s /v/qn 2.0 CulvertMaster 03.01.010.00 Installshield /s /v/qn 2.0 CulvertMaster 03.01.009.00 Installshield /s /v/qn 1.1 CulvertMaster 03.01.003.00 Wise /s General What if I want to silently deploy a newer version of a product that is already installed? With newer generation installation packages based on IEpress/Wix, a silent installation of a newer version should automatically uninstall the older version first. There should be no prompt appearing on the user side. For Installshield generation versions and below, you may need to uninstall the existing older version first (see further below on silent uninstallation). Patch sets DO NOT have a silent install switch, but can be repackaged Patch sets do not have silent install switches because they are really just self extracting zip files. If you want to do a silent install you can definitely extract the necessary information from them and repackage it. You can use a program like 7 zip or WinRAR to extract the contents of the patch. You'll notice here are a few files once you extract everything. Delete all the files except the ZIP file. Now you can take this zip file then open it to extract the contents of the patch set for each program. Note on .NET Framework Microsoft .NET Framework is a prerequisite to all Haestad products. Before silently deploying the product, if the required version of .NET (see chart above) is not already installed, it it best to silently deploy that first. Troubleshooting / Alternatives If you're having trouble performing a silent installation, try extracting all the contents and silently deploying them separately. See "Older IEpress/Wix Installers" section below for more information. Silent Uninstallation To perform a silent un installation, run msiexec with the following syntax: msiexec /x { guid } /qn On a 64-bit operating system, the guid for our products (which use a 32-bit installer), can be found in the registry under: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ On a 32-bit operating system, the guid can be found under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ For instance for WaterGEMS 08.11.04.50, the guid is {BE30126E-C93C-4C98-97EA-3EEBB4F2561F}, so you would run it like this: msiexec /x {BE30126E-C93C-4C98-97EA-3EEBB4F2561F} /qn Here are the guids for the current versions of some of our other products: HAMMER 08.11.04.50: {138400E8-3D74-470F-83FE-F12BCD7F824D} SewerGEMS 08.11.03.77: {85DA45AD-89CB-49C9-9602-8A49C1397D54} SewerCAD 08.11.03.77: {78A1B73D-5951-440D-9B91-8CFE4E0F5289} CivilStorm 08.11.03.77: {640ACA2B-8959-47A9-A293-96D325E3EE03} StormCAD 08.11.03.77: {59531A5F-531C-4AAE-8810-FD64100607F8} Silent installation for Versions using IExpress and Wix Technology (~2010-present) Recent versions of Haestad products (as of ~2010-2013) utilize IEpress to extract the installation files and Wix to package the .msi. Versions using this technology can be silently installed by running the install file with the either the /gm2 /ai or the /q:a switch, depending on the version. See the table above for the syntax needed. Note: . Starting with WaterGEMS/WaterCAD/HAMMER V8i SELECTseries 5 and SewerGEMS/SewerCAD/StormCAD/CivilStorm V8i SELECTseries 4, the switch is /gm2 /ai . A server script would need to execute this on the client computer, with the install file in a shared/network location. Two exceptions are version 08.11.02.31 of WaterCAD, WaterGEMS and HAMMER, and version 08.11.01.51 of PondPack (see "older IEpress/Wix" section below for these). When run, the program will attempt to install without any user interaction. Older versions of IExpress/Wix Technology (2009 PondPack and WaterCAD/WaterGEMS/HAMMER) When the IEpress and Wix technology was first used in our installers, we did not support passing of the silent mode switch (/q:a). This applies to version 08.11.02.31 of WaterCAD, WaterGEMS and HAMMER, and version 08.11.01.51 of PondPack. For these versions, you must first extract the prerequisites and setup msi file and deploy them silently. A server script would need to execute this on the client computer, with the install file in a shared/network location. 1) Extract the contents of the installation executable to a folder, using a tool such as 7zip or WinRAR. You can also use the steps located here for extracting those files . 2) Silently deploy all the prerequisites with standard silent mode arguments. To check the order of installation, look in the Settings.ini file. For example to install the Microsoft .NET Framework prerequisite silently: dotnetfx35setup.exe /q /norestart To install Microsoft Visual C++ Redistributable x86: vc9redist_x86.EXE /q:a /c:"msiexec /i vcredist.msi /qn" 3) Silently deploy the main application, contained within the Setup.msi file. Example: MsiExec.exe /I Setup.msi /L* %TEMP%\SetupLog.txt /qn Note: The prerequisite installer also does a test on the prerequisite to see if it is already installed, through a registry check. You can see the registry path in the Settings.ini file. For instance for Microsoft Visual C++ 2008 Redistributable x86 checks if the following registry path is present when the prerequisite is installed so there is no point in installing it: 32-bit OS: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{86CE85E6-DBAC-3FFD-B977-E4B79F83C909} 64-bit OS: SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{86CE85E6-DBAC-3FFD-B977-E4B79F83C909} Silent installation for versions using InstallShield (~2005-~2009) Versions of the Haestad products that use InstallShield technology can be silently installed by running the install file with the /s /v/qn switch. A server script would need to execute this on the client computer, with the install file in a shared/network location. When run, the program will attempt to install without any user interaction. Silent Installation for Versions Using Wise (~2004 and earlier) Old versions of Haestad products that utilized Wise installer technology can be silently installed simply by running the install file with the switch /s . A server script would need to execute this on the client computer, with the install file in a shared/network location. When run, the program will attempt to install without any user interaction. Note: it is highly recommended to upgrade to a newer version, especially for Operating System compatibility reasons. Licensing It is sometimes necessary to also silently configure licensing after silently installing a product. To do this, your server script can run command line arguments on the Licensetool.exe and Haestad.LicenseAdministrator.Console.exe , both found in the product's installation folder. To set the server name , use this syntax: LicenseTool.exe /nowin configure -setting:SelectServer -value:SERVER_NAME To set the activation key , use this syntax: LicenseTool.exe /nowin configure -setting:ActivationKey -value:ACT_KEY To set a default license feature configuration, (typically done manually in the Municipal License Administrator (MLA), to choose your pipe, inlet or pond limit) use this syntax: Haestad.LicenseAdministrator.Console.exe /configure Where is the ID corresponding to the Bentley application and is the default feature string you want to set. A typical feature string looks something like this: acad=yes|agis=yes|mstn=yes|pipe=250. Of course, you will need to be licensed for the feature string you set, else the product will not activate (and may run in Disconnected Mode for a limited period of time). Option 2 If the above does not work or you'd like an additional option to use the steps below will explain how to create a copy of the registry entry for you license file. After doing that you can write a script file the enters the information automatically into the registry from the license text file that you'll be creating. Note that you'll have to perform these steps on a computer that already has one of the Bentley Water Products already installed. 1) Browse to "HKEY_LOCAL_MACHINE\SOFTWARE\BENTLEY\LICENSING\1.1" on a 32 bit computer OR "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BENTLEY\LICENSING\1.1" on a 64 bit computer. 2) With the 1.1 folder highlighted right click and choose > Export. 3) After you save the file you can write a script that reads the information from this file and populates the Select Server and Activation key in the registry at the locations listed above. Here is the list of Product IDs: WaterCAD: 1248 WaterGEMS: 1249 HAMMER: 1225 SewerGEMS: 1244 CivilStorm: 1207 StormCAD: 1246 SewerCAD: 1243 If running this command from the client's computer, use the Run command with the full path to the executable file. The Haestad.LicenseAdministrator.Console.exe file will be located in the product's installation folder. The path depends on where you originally directed the program to install to and whether the operating system is 32 ot 64-bit. For example, the Run window for StormCAD running on a 64-bit version of Windows 7 would be like this: C:\Program Files (x86)\Bentley\StormCAD8\Haestad.LicenseAdministrator.Console.exe /configure 1246 mstn=yes|inlt=25 See Also How can I disable the ArcGIS, Microstation, and AutoCAD integration Option? Extracting an .msi file from hydraulics and hydrology (Haestad) programs

Buenos días señores de Bentley. Soy el Ingeniero Oscar López y estoy trabajando para la empresa CDM SMITH. Estamos desarrollando el Proyecto Centro Ampliado en la ciudad de Bogotá, el cual consiste en la calibración de las redes de acueducto de la ciudad. Inicialmente se está tratando de calibrar un sector de todo el proyecto a través del software WaterGems V8i. En este sector se tienen datos de Macro medición, Facturación y 4 puntos de presión al interior del distrito. Con los datos de Macro medición y Facturación se calculó el patrón de consumo y el Índice de Agua No Contabilizada. La Facturación se añadió al modelo a través de la herramienta Customer Data. Inicialmente se corrió el modelo para un escenario dinámico (24 horas) arrojando diferencias de presión máximas de 7 mca con respecto a los datos de campo. Después se utilizó el Darwin Calibrator, buscando un factor multiplicador para diferentes grupos de demanda creados. En la tabla de los resultados simulados se muestra las diferencias de presión existentes utilizando el Darwin Calibrator. Sin embargo, cuando exportó y simulo este escenario, no me arroja los mismos valores que me mostraba en la tabla “Simulated Results” del Darwin Calibrator. Por lo tanto, me surge la duda si la herramienta Customer Data no es compatible con la del Darwin Calibrator, ya que se realizó otro escenario sin utilizar el Customer Data y este problema desapareció. Les agradezco la respuesta a la anterior inquietud.

Oscar, Un saludo.El desarrollo original de Darwin Calibrator y la implementación del algoritmo genético (GA) para calibración hidráulica de modelos se basó en el ajuste de rugosidades (propiedad de tuberías), demandas en nodos y estados (abierto/cerrado) de tuberías. Dentro de los grupos de ajustes de demanda del calibrador solamente es posible crear grupos conformados por nodos en los cuales los datos de demanda o potenciales fugas son inciertos. No hace mucho sentido que se pudiera seleccionar elementos de medidores de clientes (customer meters) puesto que se trata de un valor obtenido por micro-medición en el que existe una mayor certeza (esto no impide que dentro del dato de demanda del medidor no se pueda incluir previamente el % de error de micromedicón - casi siempre subcontaje). Ahora bien, en calibraciones de modelos con "Customer Meters" el D.Calibrator va a estimar la demanda total en los nodos incluida la demanda proveniente de micro-medidores asociados y va a determinar un factor mutiplicador de demandas para obtener una funcíón de ajuste (fitness) menor y conseguir una mejor correlación estadística. Sin embargo, al momento de exportar un escenario o solución calibrada ese factor multiplicador solo afectaría las demandas base asignadas directamente a los nodos y no las demandas de los "customer meters". Si quisieras afectar el elemento medidor de cliente se tendría que hacer de forma manual. Reitero que el elemento medidor de cliente es útil cuando se tienen los datos de consumo de cada cliente basados en facturación, no cuando se tiene un dato inferido o se reparte el caudal total de un sector hidráulico en todos los elementos de medidor de cliente. En ese ultimo caso no se trataría de un consumo realmente medido. Si un modelo hidráulico tiene la totalidad de elementos "customer meters" con datos de consumo extraidos en su totalidad de facturación, entonces la operación que aplicaría en D. Calibrator es la de detección de nodos con fugas (Leakage Node Detection) y no la de multiplicar demandas originales. Una más detallada explicación de esta pregunta que planteas la puedes encontrar en este post: Using Customer Meter Demands with Darwin Calibrator Att, Juan Carlos

I have a couple of questions, the first is in the tanks you have the option to feed in the top but only one pipe is selected as the input, but if you have several arrivals to a tank that I can do, since the apparently other pipes entering the bottom, is that correct? this leads me sometimes negative pressures. The second is something related to the above as the pipe coming into the tank takes my tank top as the top of which comes the hydraulic grade, I have to do so in the course of the line in the there are high points which I take them as intermediate point to win the pump. I placed a Air Valve at the highest point and corrected something if this is not the right thing.

Hi, I have long, flat sewers that i must model and will have to implement lifting pumps stations. I particular, the type where you have a small submersible pump inside a manhole (at say 5m deep) to discharge into the gravity line connected to the same manhole at say 1m deep i.e. the "rising main" is inside the manhole. How can I model this and still have a realistic long sections which consists of manholes and pipes only as I need to put this on a profile drawing? Regards

For the top filling tank, you can have only one pipe at top, filling the tank. But you can have multiple pipes flowing into a tank. Here are the things to check for negative pressure. http://communities.bentley.com/products/hydraulics___hydrology/w/hydraulics_and_hydrology__wiki/10830.negative-pressures If this doesn’t help then please upload a copy of your model for our review. There are two options for sharing your model files on Communities. If you would like the files to be visible to other members, compress the files into a zip file and upload them as an attachment using the ‘Advanced Reply editor’ before posting. If your data is confidential, you can follow the instructions in the link below to send it to us via Bentley Sharefile. Files uploaded to Sharefile can only be viewed by Bentley. communities.bentley.com/.../7079.be-communities-secure-file-upload If you send the model, please post here so we know it is available.