Applies To Product(s): WaterGEMS, WaterCAD, HAMMER, StormCAD, SewerCAD, SewerGEMS, CIvilStorm, PondPack Version(s): CONNECT Edition, V8 XM and V8 i Area: Modeling Original Author: Mark Pachlhofer, Bentley Technical Support Group Overview This TechNote will show you how to import one model file ("submodel") into another model file ("target"). It is meant to provide clarification and explanation beyond what is given in the Help documentation. Note that this Technote was written for WaterCAD and WaterGEMS but the same concepts apply to HAMMER, StormCAD, SewerCAD, SewerGEMS, CIvilStorm and PondPack (V8i and V8 XM.) Definitions Target Model - The model that is accepting the submodel file. Submodel - The model that is being imported. Network Elements - The elements in your drawing pane that make up your model. These are junctions, pipes, valves, tanks, reservoirs, pumps , hydrants, etc. Rules for Importing Submodels 1. Existing elements in the target model will be matched with incoming elements from the submodel using their labels. 2. Incoming submodel input data will override target model data for any element matched by its label. 3. If a submodel element of the same label does not already exist in the target model, it will be created during the submodel import. Element Types Governed by Submodel Rules The rules for importing submodels govern the following element types: Analysis Menu Scenarios Alternatives Calculation Options Components Menu Controls Pump Definitions Unit Demands Zones Patterns Minor Loss Coefficients Pressure Dependent Demand Funtions GPV Headloss Curves ConstituentsValve Characteristics Time Series Field Data Tools Menu User Data Extensions Hyperlinks Example 1 In this example, the Submodel and Target Model have no elements in common (i.e., scenarios, alternatives, calculation options, and network elements do not match). Town 'A' (The Target Model) In the model illustration below, take notice of the labels for the elements outlined in red: Alternatives e.g., "Year 2000 Active Topology" "Plus Two 18in Pipes," "Diameter times 2") Scenarios (e.g., "Year 2000 Conditions," "Plus Two 18in Pipes") Calculation Options (e.g., "Year 2000 Conditions") Network Elements (e.g., Pipes P-90 and P-60, Junctions J-50 and J-40, Pumps, Reservoirs, Tanks, etc.) Town 'B' (The Submodel) In the model illustration below, take notice of the labels for the items outlined in red: Alternatives (e.g., "Model_B_Active Topology") Scenarios (e.g., "Model_B_Average_Day") Calculation Options (e.g., "Model_B") Network Elements (e.g., Pipes B_Pipe-9 and B_Pipe-11, Junctions B_Junc-7 and B_Junc-6, Pumps, Reservoirs, Tanks, etc.) Result of Importing Submodel into Target Model In the illustration below, the target model network elements are visible on the left, and the imported submodel network elements are outlined in red on the right. Since the target model elements have no label names in common with the submodel elements, all of the submodel elements will be created the target model, according to rule 3 above. None of the data in the target model will be overwritten in this case, since there were no matching labels. Observe how the scenarios, alternatives, calculation options, and element labels for all the submodel items have been brought into the target model (see red outlined areas). For example, for the Active Topology alternatives, all of the submodel's (Town 'B') network elements have come in as inactive for the original "Year 2000 Active Topology." The reason is because the newly imported elements did not previously exist in that alternative, so the default attributes are used. In the case of active topology, the default is inactive. So, the newly imported elements are inactive in the "Year 2000 Active Topology" alternative. In the case of the physical alternative, if the submodel's physical alternatives don't match the target model's, the default physical attributes will be used for the newly imported elements, for the physical alternatives that already existed in the target model. So in this example, since the physical alternative in the submodel ("Model_B_Physical") doesn't exist in the target model, it was brought in as a new alternative. So, the pipes from the submodel in the scenarios that use the "Year 2000 Physical" will have 6" diameters and junctions will have zero elevations and so forth. In order to see the original attributes of the submodel elements, the scenario would need to use the "Model_B_Physical" physical alternative. Example 2 In this example, the submodel and target model have some elements in common (i.e., scenarios, calculation options, and network elements J-100, J-210, and P-250). Town 'A' (The Target Model) In the model illustration below, take notice of the labels for the items outlined in red: Alternatives (e.g., "Year 2000 Active Topology" "Plus Two 18in Pipes," "Diameter times 2") Scenarios (e.g., "Year 2000 Conditions," "Plus Two 18in Pipes") Calculation Options (e.g., "Year 2000 Conditions") Network Elements (eg., Pipe "P-250" and Junctions "J-100" , "J-210") Town 'B' (The Submodel) In the model illustration below, take notice of the labels for the items outlined in red: Alternatives (e.g., "Model_B_Active_Topology") Scenarios (e.g., "Year 2000 Conditions") Calculation Options (e.g., "Year 2000 Conditions") Network Elements (eg., Pipe "P-250" and Junctions "J-100" , "J-210") Result of Importing Submodel into Target Model In this model below we have connected the submodel (right) network to the target model network (left) at junctions J-100, J-210, and pipe P-250 (center). This connection occurs because both models shared some of the same junction and pipe labels as import rule 2 states. The submodel data is therefore going to overwrite the existing target model data in any items governed by the rules that are common to both models (illustrated below). You can see that for both the submodel and target model there is also a common scenario name. If any of the properties for this scenario were different the submodel properties for this scenario would overwrite the properties for the target model. Above we see the target model network has all become inactive except for the junctions and the pipe that are shared by both models. This happens because the submodel data is overwriting the scenario data for the 'Year 2000 Conditions' scenario (import rule 2). In the illustration below, Town 'A' Demands and Pipe Diameter before the import are outlined in red Junction Demands Pipe P-250 Diameter J-100 = 19.60 gpm 6 inches J-210 = 72.60 gpm In the illustration below, Town 'B' demands and pipe diameter before the import are outlined in red Junction Demands Pipe P-250 Diameter J-100 = 72.0 gpm 8 inches J-210 = 40.0 gpm In the illustration below, pipe size and junction demands after the import are outlined in red Junction Demands Pipe P-250 Diameter J-100 = 72.0 gpm 8 inches J-210 = 40.0 gpm **If there is a case where the target model and the submodel share elements in common, as in the example above, but the X and Y coordinates differ they will be updated with the X and Y coordinates from the submodel. Example 3 In this example, the submodel and target model share all of the same network elements but, none of the same scenarios, calculation options, or alternatives. Town 'A' (The Target Model) In the model illustration below, take notice of the labels for the items outlined in red: Scenarios Calculations Options Alternatives Average Day Demand Average Day Conditions Average Day Fire Flow Fire Flow Fire Flow Constituent Analysis Constituent Constituent Alternative - 1 Town 'A'_2 (Submodel) In the model illustration below, take notice of the labels for the items outlined in red: Scenarios Calculation Options Alternatives Peak Conditions Peak Condtiions Peak Peak Times 2 Peak Times 2 Result of Importing Submodel into Target Model In the model below we can see the import of the submodel results in all the network elements remaining the same because all these elements had the same labels. Hypothetically, if any of the properties of the network elements were different in the submodel from the target model the properties of the result would contain the values that were contained in the submodel (import rule 2). The significant change that happens in this model, much like in the first example, is that the scenarios, alternatives, and calculation options from the submodel all get added to the target model without overwriting anything. In the model illustration below, take notice of the labels for the items outlined in red: Scenarios Calculation Options Alternatives Average Day Demand Average Day Conditions Average Day Fire Flow Fire Flow Fire Flow Constituent Analysis Constituent Constituent Alternaitve - 1 Peak Conditions Peak Conditions Peak Peak Times 2 Peak Times 2 Steps for completing a Submodel Export/Import 1) Open the model that you want to export the submodel part from. 2) Select the part (or entire) model that you want to export. This can be done in many ways. Three common ways are by using your mouse to draw a box around certain areas, using your mouse to left click and select one element or multiple elements while holding down the shift key, or by holding down the CTRL key + A , which will select all the elements on screen. The default color for selected elements is red. 3) With the elements selected in the display panel go to File > Export > Submodel. Name and save your model to a location that you will remember. 4) Now open your target model and after it load go to File > Import > Submodel. Note: if you would like to import the entire model and not a subsection of the model, only step 4 is required. Meaning, in the target model, simply go to File > Import > Submodel, then select the .wtg.mdb file associated with the submodel you would like to import. Troubleshooting If you know you imported the model but don't see anything or are missing part of the model on in your display area. Answer: Go to Tools > Options and see if the option on the Global tab for "Display Inactive Topology" is checked. Also notice the color the inactive topology is set to. If all or part of the model you imported is gray Answer: Your model has likely imported correctly but, all or part of it is currently inactive. If you want it to appear as an "active" status element the active scenario you have to use the active topology tool (Tools > Active Topology Selection) or go into the active topology alternative and change the status of the inactive elements. The reason this happens is because the active topology alternative in the submodel did not match the target model. So, the default status of inactive is used. If you do not want to manually change this in the resultant model, you will need to first go back to the target model and change the labels and structure of the active topology alternatives, so that they match between the models. The attributes/data from the submodel were lost Answer: If the properties of the submodel elements appear to use the default values (such as 6" for all diameters, zero elevation, etc), most likely the physical alternative(s) in your submodel did not match the physical alternatives in the target model. For example if a scenario and physical alternative exist in the base model but not in the submodel, any new elements imported from the submodel will use default values for physical properties in that scenario in the base model. You will either need to correct this manually, or go back to the target model and change the labels and structure of the alternatives so they match exactly to the target's What if models have same labels? Answer: If models have same labels such as P-1 in Project A and P-1 in Project B as well, then the tool from the link below can be used to prefix the Labels before importing. Once the import process is done, the prefixed label can be removed too. http://communities.bentley.com/other/old_site_member_blogs/peer_blogs/b/akshayas_blog/archive/2013/07/11/update-labels-of-a-hydraulic-model-using-waterobjects-net.aspx OR You can use the relabel function in the flextables to relabel some elements. The wiki for how to do that can be found here: See Also Pipes connecting to the wrong element after submodel import Elements turning inactive and reverting to default properties after submodel import
↧
Wiki Page: Submodel Import/Export
↧
Wiki Page: Modeling elliptical, arch, and box channels in PondPack
Product(s): PondPack Version(s): 08.11.01.56 Area: Calculations Problem User is trying to model elliptical, arch, and box channel, but that is not one of the standards for PondPack. Problem ID#: 43645 Solution A workaround for this if you can't approximate the shape with one of the available types, is to choose "elevation-flow-area curve" for the conduit type in the conduit properties. Then define the table of elevation-flow based on the ellipse section by computing the rating curve externally and entering it. If you have FlowMaster you can use that, since it has an elliptical pipe worksheet and can generate rating tables. An irregular channel with a user defined station vs. elevation curve can also be entered to model these and other non-default channel shapes. Original Author: Terry Foster
↧
↧
Wiki Page: What file types are supported for background layers in the standalone platform?
Product(s): WaterGEMS, WaterCAD, StormCAD, SewerCAD, SewerGEMS, CivilStorm, PondPack, HAMMER Version(s): 10.00.xx.xx, 08.11.xx.xx Area: Layout and Data Input Problem What file types are supported for background layers for the standalone platform for the water or storm-sewer products? Problem ID#: 74835 Solution Prior to the release of the Connect Edition products, the supported file types included: .dxf, .shp, .bmp, .jpg, .jpeg, .jpe, .jfif, .tif, .tiff, .png, .gif, .sid Note : MrSid files are currently only supported in the 32-bit version of the Haestad product. How do you run a hydraulics and hydrology product in 32 bit mode? The following file types are also supported starting with the release of CONNECT Edition (10.XX.XX.XX) The file types dgn, dgndb, and .imodel can now be added as background layers. World file support for background images Some image formats support associated world files. When attaching a background image file that has an associated world file present, the image will now 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. (Please visit the site to view this video) See Also MrSid files are not available as a background layer type Can a DWG file be attached as a background?
↧
Wiki Page: Element label editing and automatic numbering
Applies To Product(s): WaterGEMS, WaterCAD, HAMMER, SewerGEMS, SewerCAD, StormCAD, CivilStorm, PondPack Version(s): 08.11.XX.XX Area: Layout and Data Input Original Author: Craig Calvin, Bentley Technical Support Group How to specify automatic numbering format for new elements as they are added to the network. Go to, Tools > Options > Labeling tab From here, you can set how new elements will be labeled for each element type. Buttons Save As : Saves your element labeling settings to an element label project file, which is an. xml file. Load : Opens an existing element label project file. Reset : Resets the values in the 'Next' column to the values that are located in the 'Increment' column. The default value of the increment column is 1. Labeling Table Columns Element : Shows the type of element to which the label applies. On : Turns automatic element labeling on and off for the associated element type. Next : Type the integer you want to use as the starting value for the ID number portion of the label. Bentley WaterGEMS V8i generates labels beginning with this number and chooses the first available unique label. Increment : Type the integer that is added to the ID number after each element is created to yield the number for the next element. Prefix : Type the letters or numbers that appear in front of the ID number for the elements in your network. Digits : Type the minimum number of digits that the ID number has. For instance, 1, 10, and 100 with a digit setting of two would be 01, 10, and 100. Suffix : Type the letters or numbers that appear after the ID number for the elements in your network. Preview : Displays what the label looks like based on the information you have entered in the previous fields. How to edit existing element labels. Elements that have already been placed can be edited in the "Label" field of the Properties grid for individual elements. FlexTables can also be used to edit existing element labels and make it easier to edit multiple elements at a time. All elements in the FlexTable can be edited at the same time by right-clicking on the "Label" column heading, then clicking "Relabel…". The following three types of relabeling operations can be performed: Replace : This operation allows you to replace all instances of a character or series of characters in the selected element labels with another piece of text. Example: P could be replaced with the word Pipe by entering P in the Find field, Pipe in the Replace With field, and clicking OK. P-1 would be replaced with Pipe-1 and so on. Append : This operation allows you to append a prefix, suffix, or both to the selected element labels. Example: Suppose that you have selected the labels 5, 10, 15, and 20, and you wish to signify that these elements are actually pipes in Zone 1 of your system. You can use the append operation to add an appropriate prefix and suffix, such as P and -Z1, by specifying these values in the Prefix and Suffix fields and clicking the Apply button. Performing this operation yields the labels P5-Z1, P10-Z1, P15-Z1 and P20-Z1. Renumber : This operation allows you to generate a new label, including suffix, prefix, and ID number for each selected element. Example: If you had the labels P-1, P-4, P-10, and Pipe-12, you could use this feature to renumber the elements in increments of five, starting at five, with a minimum number of two digits for the ID number field. You could specify a prefix P and a suffix -Z1 in the Prefix and Suffix fields, respectively. The prefix and suffix are appended to the front and back of the automatically generated ID number. The value of the new ID for the first element to be relabeled, 5, is entered in the Next field. The value by which the numeric base of each consecutive element is in increments, 5, is entered in the Increment field. The minimum number of digits in the ID number, 2, is entered in the Digits field. If the number of digits in the ID number is less than this value, zeros are placed in front of it. Click the Apply button to produce the following labels: P05-Z1, P10-Z1, P15-Z1, and P20-Z1. Note: The entry fields displayed depend on what operation is selected. The Preview field displays an example of the new label using the currently defined settings. (Please visit the site to view this video) See Also How do I append a prefix to element labels based on a selection set of elements?
↧
Wiki Page: How are the coefficients derived for the HEC-22 structure loss method?
Product(s): StormCAD, CivilStorm, SewerGEMS Version(s): V8i, CONNECT Edition Area: Modeling Problem How are the coefficients derived in StormCAD when using the HEC-22 structure loss method? Problem ID#: 58019 Solution The `HEC-22' structure loss method used in StormCAD (and the GVF-Rational solver in CivilStorm and SewerGEMS) is based on the FHWA's Urban Drainage Design Manual, Hydraulic Engineering Circular No. 22 (HEC-22) energy-loss methodology. This method computes an adjusted headloss coefficient by multiplying the initial headloss coefficient by correction factors for diameter, flow depth, relative flow, plunging flow and benching (Structure Headloss). This adjusted headloss coefficient is then multiplied by the velocity head in the outlet pipe to determine the total junction headloss. This is the method outlined in the current edition of the HEC-22 document (HEC-22, Second Edition, August 2001). Note that is more recent versions, the Third Edition HEC-22 structure loss method is also available. See Also HEC-22 2nd edition energy loss calculations with the Implicit solver What are the differences between HEC-22 3rd edition and HEC-22 2nd edition? HEC-22 "junction loss" (equation 7-10 of HEC-22) Junction minor headloss coefficients for standard method
↧
↧
Forum Post: Questions regarding System Head Curve and Pump status for a closed system
(Please visit the site to view this file)(Please visit the site to view this file)(Please visit the site to view this file)Dear All, I have a question to clarify some confusions regarding system head curve and pump selection. First, a bit of background. The system is in a developing country, serving low-income communities (standpipe at household level). Currently, the set-up is, storage of water from supply in underground reservoir, then lifting of water to overhead tank and from there, distribution. The pump operation is done by manual operator. I am attaching the existing model for your reference as well. The local NGO operating the system received two more access points for water supply from municipality water works and they want to expand their service network. They also have water scarcity and capacity deficiencies in the existing network. So, they want to connect the new network with existing one. Topography is quite flat and they don’t have funds for any pressure controlled valve for boundary set-up between the two phases. Due to capital cost limitations, the NGO is opting for pumping directly to new network (though opinions about life cycle cost, inefficient operating cost was communicated). Given land-rights issues, they are reluctant to make high capital investments. Objective is to meet demand at 1 bar pressure minimum. The pumps considered are low cost household level centrifugal pumps (usually used for lifting water to high-storied buildings). For the new supply sources, water stored at sump/equalization tank and then, pumping is considered. From local consumption survey in existing network, the consumption pattern shows significant peaking during day time. To address that, at each source, two pumps in parallel are considered. The second pump will kick in only during the peak hour operations. Initially, only the reservoir was used for pipe sizing and identifying flow variation at each new source. Then, pumps were introduced. The pumps are identical in size. Since one pump will operate alone at each source for about 13.5 hours (parallel pumping for 5.5 hours), pump selection was done such that best efficiency point lies between low and peak demand region during solo operation. My understanding is, it is going to act like a closed system. Though the existing tank at discharge side should make it an open system, when I tried to generate the system head curve, the curves had the same characteristic errors of closed system head curve (generated in the usual way). Any explanation why it behaved like that? I devised a pressure dependent demand scenario and run the model to devise system head curves. The system head curves are generated for the peak and least demands during parallel pumping and solo pumping. They are also attached. My primary concern is, during peak hour combined operation (13:00 hour); the flow leaving the pump station (i.e. discharge side pipe flow) is higher relative to the pump curve-system head curve intersection point’s corresponding flow. Also, the pressure at downstream node in the model is even lower. I am suspecting my selected pump capacity is low (for peak hours). I deliberately did that keeping in mind flow is available from existing overhead tank as well. I’ll appreciate it if anybody can explain the phenomenon, any remediation needed. Despite the inherent inefficiency of the system choice, I am prioritizing pump operation efficiency, water supply at 1 bar minimum pressure. With kind Regards, Imtiaz
↧
Wiki Page: How are surge tanks and hydropneumatic tanks used in WaterGEMs and WaterCAD models?
Applies To Product(s): WaterGEMS, WaterCAD Version(s): 10.00.xx.xx, 08.11.xx.xx Area: Layout and Data Input Original Author: Jesse Dringoli and Mark Pachlhofer, Bentley Technical Support Group Problem How are surge tanks and hydropneumatic tanks (hydro tank) used in WaterGEMs and WaterCAD models? Tips and What you Need to Know A hydropneumatic tank uses compressed air or gas to provide a relatively small amount of water storage volume while keeping the hydraulic grade much higher than the physical top of the tank. Hydro tanks can be set to either follow the traditional Gas Law equation or use the Constant Area Approximation method to calculate a change in pressure/HGL and volume. The constant area approximation uses a linear relationship; the user must specify minimum/maximum HGL and the corresponding volume between. The Gas Law method is non-linear and follows the Gas Law--as gas is compressed, it becomes harder to compress it more. Unless you have a specific need to use the constant area method, it is recommended that you use the Gas Law. The Constant Area Approximation method is primarily left in place for legacy purposes, to provide a way for users to achieve equivalent results compared to the method that was used before this element type was available in the product. Meaning, before the hydropneumatic tank element, it was common to model a hydropneumatic tank using a normal tank node element configured to be very tall with the appropriate constant diameter. With the hydropneumatic tank node element, an older model (or one from another product such as EPANET) could have a hydropneumatic tank inserted instead of the regular tank and configured with the Constant Area Approximation method to achieve comparable results. The two models are described in more detail below: Constant Area Approximation : This method approximates a hydropneumatic tank by using a tall, thin tank whose water surface elevation approximates the HGL in a hydropneumatic tank. The "HGL on" and "HGL off" fields represent the maximum and minimum hydraulic grade lines within the hydropneumatic tank (i.e., when an associated booster pump would turn on or off). An approximate diameter is computed based on the effective volume of the hydropneumatic tank so that the tank cross sectional area multiplied by the distance between HGL on and HGL off gives the same volume as the hydropneumatic tank. Gas Law : This method uses the ideal gas law, PV=nRT, to compute new hydraulic grades as liquid volume changes in the EPS simulation (nRT is assumed to be constant). The initial liquid volume is subtracted from the total tank volume to find the gas volume. The physical "elevation" is subtracted from the initial HGL to find the gauge pressure. The atmospheric pressure is added to the gauge pressure to get absolute pressure, which is used in the ideal gas law equation. *Both methods typically yield similar results within the "effective" control range, but the gas law is technically more accurate. If the hydropneumatic tank is just being used for transient protection and it "floats" on the system (meaning that it stays at the system HGL and neither fills nor drains until a transient event), then you can model this by setting the property of the hydro tank for "Treat as Junction?" equal to True. In some small scale systems you may want to model the tank filling or draining. If this is the case, then you will need to make sure that you have the hydraulic time step, which is found in the calculation options, set small enough to capture all the quick changes these type of tanks can exhibit. You will want to make sure the time is small enough, so that if intermediate time steps are necessary to include for the controls they don't skip over the controls. Intermediate time steps are calculation time steps that are inserted between regular interval time steps to account for control changes to element statuses. These time steps are inserted at 1/10th of the normal hydraulic time step. You will know if you need a smaller hydraulic time step because the HGL in the tank will shoot past the control elevation in 1/10 of a calculation hydraulic time step.This helps to ensure that the controls do not end up overshooting the fast level changes that can occur. Surge Tanks Surge tanks are handled just as regular tanks are in WaterCAD and WaterGEMS. They are located in the software because our water line of hydraulics and hydrology products share a common graphic user interface and file extensions, so a file created in one product can be opened in another. Example Model Click the below link to download a small example model with a Reservoir > Pump > Hydropneumatic tank > Demand. The Gas Law is used with pump controls based on the tank hydraulic grade, with a suitably small time step. (Please visit the site to view this file) Surge tanks and Hydropneumatic tanks have a field called "Treat as Junction?" In many cases a hydropneumatic tank or surge tank may be implemented only for transient protection. During a steady state condition, the tank may simply operate under the corresponding normal / steady state head ("line pressure"). To simplify this during a model simulation there is field called "Treat as junction" that can be set to "True". Doing this allows the WaterGEMS/WaterCAD solver to compute a hydraulic grade at the tank location and the user simply assumes that the tank has already responded to the hydraulic grade and the air volume has expanded or contracted accordingly. When using this option the user only needs to enter the initial volume of gas under the "Transient" section of the tank properties that corresponds to the hydraulic grade (unless using a bladder instead of gas law setting). See Also Why are there so many extra elements listed for WaterGEMS and WaterCAD such as surge tanks, rupture disks, or periodic head-flow elements? How does the gas law model work for a hydropneumatic tank in WaterGEMS or WaterCAD? Hydropneumatic tanks modeling reference for HAMMER
↧
Wiki Page: Using LoadBuilder to assign Customer Meters to the nearest pipe using taps and laterals
Product(s): Bentley WaterGEMS, Bentley WaterCAD Version(s): 10.xx.xx.xx Area: Modeling Introduction In earlier versions of WaterGEMS and WaterCAD, LoadBuilder could be used to assign Customer Meter elements to the nearest junction. With the introduction of taps and laterals in the CONNECT Edition release of WaterGEMS and WaterCAD, new tap and lateral elements, can be used to assign Customer Meters directly to the pipe. The previous workflow assigning the Customer Meters to nodes is still valid. However, LoadBuilder will not create laterals when assigning the Customer Meter to the nearest node, though the lateral can be added manually or through ModelBuilder if that is desired. The steps to assign a Customer Meter to a node is discussed in the link above. Below are the steps to assign to the Nearest Pipe using Taps and Laterals. Note: as of version 10.00.00.50, lateral link elements do not count toward your pipe limit. Steps to Accomplish These steps assume the Customer Meters are already present in the model. If you have not added them yet, you can do so manually or using ModelBuilder . This layout shows three Customer Meters that are currently unassigned to a hydraulic element. First, we will consider a case where the Customer Meter is assigned to the nearest node. Assign Customer Meter to nearest pipe Open LoadBuilder by going to the Tools tab. Click the New button in the upper left of the dialog to create a new connection. Select the Customer Meter Load Data option on the left side of the dialog. Since we are assigning the customer meter to the nearest pipe, select that option from the selections on the right, then click Next. In the next screen, you will select the Pipe Layer, Node Layer, and Customer Meter Layer. This is basically telling the program which elements the Customer Meter may be associated with. Next to the Pipe Layer option, click the ellipsis ("...") button, which will open the "Select a Layer" dialog shown above. For this case, we will choose "Pipe\All Elements," which means that all active pipes will be considered. Note: If a node is inactive, the Customer Meter cannot be assigned to that node. Only elements active through Active Topology will be considered for associated elements. In addition to selecting the Pipe Layer, you will also need to select the Load Assignment. The default setting is Closest Node, but you can also choose to weight the demand between the end nodes of the pipe, distribute the demand equally between the end nodes, or apply the demand to the farthest node. Next, click the ellipsis (...) button next to Node Layer. All node types that can have a demand applied to them are available. In this case we will choose "Junctions\All Elements". Finally, do the same thing for the Customer Meter elements. You also have the option to exclude customer meters that already have an associated element, but may not have a lateral or tap. To do this, click the "Exclude unconnected Customer Meters that already have an Associated Element." Lastly, you will want to select the option "Create taps and laterals for Customer Meters that are not connected." This will assure that the necessary elements are created to correctly associate the Customer Meters to the pipes via a tap and lateral. Click Next and see the results that LoadBuilder has calculated. Notice in the screenshot below that two of the Customer Meters are assigned to one pipe. It is possible to have more than one customer meter assigned to an individual element. Lastly, you will need to create a label for the LoadBuilder connection. You will also need to either update an existing Demand Alternative or opt to create a new alternative. Click Finish and the LoadBuilder will assign the Customer Meter to the nearest pipe, as well as create the taps and laterals to complete the connection. Reassigning taps to new pipe During the process of analyzing a model, you may need to associate an existing Customer Meter to a different pipe. If that case arises, you can use the following workflow. First, you will need to drag and drop the Tap element to the pipe that the Customer Meter should be associated with. In the screenshot below, the tap has been moved from pipe P-20 to pipe P-260. Notice the dashed line that is connected to the tap element and P-20. This means that the tap is still associate with P-20. In order to associate the tap with the correct pipe you can right-click on the tap element and choose Attach. If there are multiple taps that need to be reassigned after moving them, you there a batch tool that will do this as well. Go to the Tools tab. In the Tools section, select More > Assign Taps to Links. This tool is used to batch assign taps to pipes when there is no current association. For instance, if you manually added the customer meters, taps, and laterals, there may be no true association between the elements. The Assign Taps to Links tool will assign this. However, it can also be used to reassociate taps that are currently associated to a different pipe. To apply this, select the option "Also process taps that already have an associated link" from the Options section of the Assign Taps to Links tool. When you click OK, the tap will be reassigned to the new pipe. The tap is now associated with a new pipe. However, the customer meter is still assigned to the old pipe. You can change the association manually in the Customer Meter properties. You can also use LoadBuilder to update the association. Using LoadBuilder, you can run the existing connection. When you are on the screen where you assign the pipe, node, and customer meter layers, uncheck the box for "Exclude unconnected Customer Meters that already have a valid Associated Element." Click Next and complete the LoadBuilder process. Once you are completed, you should see the associated pipe for the Customer Meter is the same one that the tap is connected to. See Also Customer Meter elements and the External Customer Meter Data Manager Troubleshooting and Understand LoadBuilder
↧
Wiki Page: How can I reduce the number of pipes in my model?
Product(s): WaterGEMS, WaterCAD Version(s): 08.11.XX.XX Problem How can I reduce the number of pipes in my model? Problem ID#: 74797 Solution To reduce the number of pipes in a model try to combine pipes that have equivalent diameters and roughnesses. If you have access to Skelebrator (Tools > Skelebrator) in WaterCAD/GEMS if you have that feature available to you. See more on Skelebrator in the articles linked to further below. You can also use of Laterals and Customer elements to assign demands along the length of a pipe instead of creating extra nodes (which split the pipe). As of version 10.00.00.50, lateral link elements do not count toward your pipe limit. Furthermore, you can also use isolation valves instead of valve node elements (like GPVs or TCVs) to model valves, as the isolation valves do not split the pipe. See Also Series Pipe Merging in Skelebrator not working for pipes with zero diameter Pipes not merging when using Skelebrator with series pipe merging Customer Meter Elements and the External Customer Meter Data Manager
↧
↧
Wiki Page: How do Taps and Laterals work in the storm and sewer products?
Product(s): StormCAD, SewerCAD, SewerGEMS, CivilStorm Version(s): 08.11.05.xx and higher Area: Modeling Problem How do Taps and Laterals work in the storm and sewer products? Solution A Tap is a type of node that connects the lateral to the conduit or channel. It enables the user to add inflows along a conduit or channel without the need to break the link element into multiple elements. There could be a number of lateral connections to a single trunk conduit or channel. The flow comes from the upstream catch basin, down the lateral, and to the tap. The flow from the tap is then contributed to the conduit or channel it's connected to. Although it can be used with manholes in a sewer model, the primary use of the Tap and Lateral element are road and site design engineers and OpenRoads users (see above) because this level of detail is more significant when working with a physical model. For example, an OpenRoads user (starting with the SS4 release as mentioned above) might need to use the Subsurface Utilities Engineering (SUE) clash detection tool, in which case the exact location of the lateral and tap is important. Since this is the primary intent of the tap and lateral feature, it is not recommended to use this in very large models, where Modelbuilder would be required to import a large number of taps and laterals. Starting with the CONNECT Edition, a new Property Connection element was introduced, where a single node representing a property can be associated directly with a node on the trunk main. Note: Taps and laterals are not supported in the Implicit dynamic solver. With the Explicit (SWMM) solver, laterals are treated as "dummy" conduits. The SewerCAD (GVF-Convex) solver does not do any hydraulic calculations in the lateral pipe. Note: as of version 10.00.00.40, lateral link elements count toward your pipe limit. (Please visit the site to view this video) See Also Using LoadBuilder to assign Property Connections to the nearest element while creating taps and/or laterals How to toggle tap node dashed line display Property Connections
↧
Wiki Page: Customer Meter Elements and the External Customer Meter Data Manager
Applies To Product(s): WaterGEMS, WaterCAD Version(s): 10.xx.xx.xx, 08.11.xx.xx Area: Modeling Original Author: Scott Kampa, Bentley Technical Support Group Customer Meter Element Customer meter elements provide a way for users to maintain customer water demand data within WaterGEMS and WaterCAD. It provides the user access to features such as element symbology and the ability to visualize customer location and assignment of demand to node elements. The new customer meter element is represented by a house icon as pictured below and the association of the element with a node or pipe is shown as a dashed line. The main steps for using the customer meter elements are entering demands for the element and assigning the customer metering element to a hydraulic model element, such as a junction. This is done by clicking on the drop down button in the “Associated Element” field from the properties grid or the FlexTable then choosing “Select Associated Element…” Note: the "Zone" field will display the Zone of the customer meter's associated element. The customer meter element can also be imported or updated from eternal data sources using ModelBuilder. More information can be found on ModelBuilder by this link: Building and updating a model using ModelBuilder The external data source should contain a label, the x-y coordinate and demand data for the new element. If the data source is a shapefile, the spatial data is included already, so x-y coordinates are not needed. Demands can be entered manually by entering values in the property grid, the customer meter FlexTable, and the Demand Alternative under the Customer Meter tab. Demands from a customer meter element must be assigned to the associated hydraulic modeling element in order to be used in the calculations. The demand control center is not used for the customer meter element because there can only be a single demand and unit demand for a customer meter. Importing Customer Meters with Loadbuilder LoadBuilder can be used to assign the customer meter element to the hydraulic modeling element using one of the allocation methods located within the “Customer Meter load data” in the first step of the LoadBuilder process. The different methods that can be chosen are, "Nearest node", "Nearest pipe", or “Customer Meter Aggregation”. The "Model Node Layer" will usually be set to ‘Junction\All Elements’, but it can also be any selection set of node elements that have “Demand (Base)” as a property. The "Customer Data" is usually set to Customer\All Elements although it can also be any selection set of customer meter elements. If the customers are being assigned based on nearest pipe method, in addition to specifying the Model Node Layer and Customer Data, the user must also specify the Model Pipe Data which identifies the pipes to be considered. This enables the user to use a selection set which can ignore large transmission mains with no customers. Note : - For more information on connecting customer meters to pipes with taps and laterals, see this article . - When using Loadbuilder to assign customer meters to junctions, the user should update the existing Demand alternative rather than create a new one. If a new Demand alternative is created, the demand data imported through ModelBuilder will be lost. Typically, customer meter elements are not directly used in hydraulic calculations so there are no hydraulic results for them. The user should find results in the node to which the customer element is associated. However, starting with the CONNECT Edition release of WaterGEMS and WaterCAD, results fields for hydraulic grade and pressure have been included for the customer meter element. If you want to include these results in the customer meter, open the Calculation Options and change the property "Calculate Customer Results?" to True. When you compute the model, you will see results for hydraulic grade at the current time step, as well as maximum and minimum results across the model run. If you are using WaterGEMS/WaterCAD V8i SELECTseries 6 or earlier, hydraulic results will not be directly available. External Customer Meter Data Manager A new External Customer Meter Data manager have been added so that external source data can be added to the Customer Meter element. This allows the user to see detailed information about the location that the Customer Meter element represents. Similar to ModelBuilder, the user can select from a number of source file types, such as database files and Excel files, and import the data into the External Customer Meter Data manager. This can be important in keeping track of demand information that will be applied to the Customer Meters. For a free Webinar on using the Customer Element, click this link . If this link does not work, navigate to the main H&H Webinar directory and scroll down to the entry from Sep 2014 entitled "Improved hydraulic modeling of customers and their water demands" (Please visit the site to view this video) See Also Can I change the associated element for a customer meter in a child scenario? Using Customer Meter demands with Darwin Calibrator Pressure and other results at Customer Meter elements
↧
Forum Post: RE: StormCad running Error during validation
Thanks Jesse the patch seems to have resolved that issue. Kim
↧
Forum Post: RE: StormCad running Error during validation
Great, thanks for confirming.
↧
↧
Wiki Page: Ratio of losses field in hydropneumatic tank
Applies To Product(s): HAMMER Version(s): 08.11.XX.XX Area: Settings/Attributes Original Author: Jesse Dringoli, Bentley Technical Support Group Problem What is the purpose of the "Ratio of losses" attribute of a hydropneumatic tank or surge tank in HAMMER V8i? How are headlosses determined through these tanks? Problem Number: 34650 Solution The headloss through the orifice connecting these tanks to the pipeline is determined by the "minor loss coefficient (outflow)" attribute (or "headloss coefficient for a surge tank). When the tank is draining (outflow), just this coefficient alone is used to determine the losses, based on the velocity through the orifice, using the standard headloss equation H = KV^2/(2g). When the tank is filling, the minor loss coefficient is multiplied by the value entered in the "ratio of losses" field to determine the inflow headloss. Note that in HAMMER V8 XM (08.09.400.34) and greater, the minor loss coefficient was incorrectly labeled "minor loss coefficient (inflow)" for the hydropneumatic tank. In V8i and greater, it is correctly labeled "Minor loss coefficient (outflow)". One reason for using a ratio of losses greater than 1.0 is to model a "differential orifice" such as in the diagram below. See linked article below for more. Should the minor loss coefficient for a hydropneumatic tank also include the K for head loss through the differential orifice or just the K value for the minor losses (i.e. fittings and contraction)? This is a decision for the engineer to make, as there isn't one single way of modeling it. Since the K that you enter corresponds to the velocity through the "diameter" that you enter, it would normally represent the losses through that opening only. If you need to model minor losses through fittings, bends, etc., you would probably want to enter those in the adjacent pipe if that pipe diameter is different from the diameter of the tank orifice, so that the correct velocity is used. Anothe option is you could account for them with an Orifice Between Pipes element, or even by lengthening the pipe to have an equivalent friction loss. It depends on what you feel is most appropriate for the situation. If you wanted to lump all of your minor losses into that single K factor, you would need to come up with a K that gives the appropriate headloss for the velocity that would occur through the "diameter" field that you entered. In the case of a differential orifice, you could set the diameter and K to represent the losses through the larger size pipe with the check valve, account for losses through the check valve, pipe, bends, fittings and tank inlet. Then, you would need to figure out how much head loss you would get for the reverse flow, when flow travels through the bypass. From that, you would calculate what the ratio of losses is. That way when tank outflow occurs, the head loss through the tank assembly accounts for all losses from the tank to the main line. Then when tank inflow occurs, the head loss from the main line to the tank would account for all those same losses, plus the additional loss from going through the bypass. If you didn't have a differential orifice or any significant bends/fittings, you would set the diameter equal to the tank inlet orifice diameter and set the K to represent the losses through that opening. You could then explicitely model the pipe going from the main line to the tank and enter a friction factor to account for those losses, or place the tank inline with the main line and increase the K factor a bit to account for those losses. Note that the inclusion of the lateral pipe may be significant on the transient results, as the pressure in the tank would need to accelerate that volume of water during a transient event. See Also Modeling Reference - Hydropneumatic Tanks
↧
Wiki Page: Modeling a weir within a catch basin or manhole
Product(s): SewerGEMS, CivilStorm, SewerCAD, StormCAD Version(s): 08.11.xx.xx or higher Area: Modeling Problem Is it possible to model a weir within a catch basin or manhole in the the storm-sewer Haestad products? Basically a control structure (weir plate, orifice plate, etc) inside the structure vault. Solution It is not possible model a weir directly inside a node, but there are a few workarounds that can be tried, which in most cases should be acceptable. Option 1: conduit control structure First, you can apply a start control structure on the conduit directly downstream of the catch basin or manhole. This would simulate a weir that is right where the catch basin or manhole connects to the downstream conduit. One of the control structure types that can be modeled in this way is a weir. Note: conduit control structures currently are not supported with the GVF-Rational (StormCAD) solver. Enter the weir data with elevations expected for the weir within the catch basin or manhole. When the water elevation exceeds the weir elevation, flow will pass into the conduit. This method works best when the invert of the downstream conduit and the invert of the catch basin or manhole is the same. (in other words, "set invert to start?" is set to true, on the downstream conduit). If the outgoing conduit start invert is above the bottom of the node invert, you would need to adjust the weir elevation for the start control structure to account for the drop depth. It is also possible to model this as a stop control structure. The workflow is the same except that the flow through the conduit would not enter the catch basin or manhole until the elevation in the conduit is above the weir. A start control structure may yield more stable results. If you have more than one outgoing conduit (going away from the single control structure), you will need to use one of the other methods below, or add a short "fake" conduit connected between the manhole or catchbasin that contains the weir, and a "fake" node, from which the multiple outgoing pipes connect to. Then, the start control structure can be set on that "fake" conduit. Or if using the Implicit or explicit solvers, multiple conduits can leave the node and could each of their own start control structure if needed. Note that if you're using the Implicit solver (set in the calculation options) with SewerGEMS or CivilStorm to model a conduit control structure, you may need to change to the Explicit (SWMM) solver with a small Routing Step, for more stable results. Option 2: pond Another option is to model the catch basin or manhole as a small pond with a pond outlet structure using a weir. In this case, the manhole would be replaced with a pond with the same dimensions as the original manhole. The conduit that drains into the manhole would need to end with an outfall that uses the new pond as the boundary element. A pond outlet structure will need to be added as well. This will be set as the weir. The end result for this will be similar to Option 1 above. If the manhole or catch basin is relatively small in depth and/or diameter, you may need to decrease the time step and the output increment to increase the stability of the results. In addition, if the weir is inside a catchbasin, this workflow would work best when there is no gutter attached. Option 3: structure loss The third option would be model the weir as a structure loss. If you are using the GVF-Rational solver (available in SewerGEMS, CivilStorm or StormCAD) or the GVF-Convex solver (available in SewerGEMS and SewerCAD), you could convert a rating table for the weir into a flow-headloss curve, which is one of the structure loss methods available in this solver. If you are using the Implicit solver, you could use the Standard headloss method. With the right headloss coefficient, you may be able to reasonally match the rating curve for the weir (the rating curve would need to converted to use a head drop instead of an elevation to better see the difference). This will take some trial and error and would in all likelihood end up being an approximation. You may need to superimpose the rating curve of the weir (which can be obtained from the composite outlet structure dialog) with several rating curves based on different headloss coefficients. You could also use the Absolute headloss method based on the head drop seen in the weir rating table for a typical flow. This would allow you to make a conservative estimate for the headloss. In addition, if you are using the Explicit solver for Option 3, you would need to use the Absolute headloss method since the Standard headloss method is not available with this solver. See Also Modeling a flow split (diversion) in SewerGEMS or CivilStorm Modeling a flow split (diversion) with the SewerCAD or StormCAD numerical solver
↧
Wiki Page: Conduit start/stop control structures
Product(s): SewerGEMS, SewerCAD, CivilStorm Version(s): As of 10.00.00.40 Area: Layout and Data Input Which storm/sewer Haestad product numerical solvers can model a start or stop control structure in a conduit? The Implicit (Dynamic Wave) solver can model conduits with start and/or stop control structure. The Explicit (SWMM) solver can model conduits with a start control structure. The GVF-Convex solver can model conduits with a start and/or stop control structure. The GVF-Rational solver can not model conduits with a start or stop control structure. See Also Differences between solvers: GVF-Convex vs. GVF-Rational vs. Implicit vs. Explicit (SWMM) Modeling a weir within a catch basin or manhole
↧
Wiki Page: Multiple Demand Adjustments
Product(s): WaterGEMS, WaterCAD, HAMMER Version(s): 08.11.XX.XX and 10.00.00.XX Area: Calculations Can multiple adjustments (via the Demand Adjustment calculation option) be applied to the demand at a junction? Yes. All adjustments related to the demand at a junction will be applied to it. An example of this is shown below. What order are the adjustments applied in? The demand adjustments in the calculation options are applied first, in the order they are displayed. The order can be edited with the arrow icons. After the demand adjustments from calculation options have been applied, then the demand pattern multiplier is applied. For example, take a look at the following demand and adjustments. Junction J-1 is included in all demand adjustment scopes listed above. Row 1: 100*1.5=150 Row 2: 150*0.8=120 Row 3: 120+10=130 "Demand Pattern A" multiplier at current time step = 2 Adjusted Demand: 130*2=260 Does it matter what order the adjustments are listed in the Calculation Options dialog? When all adjustments have the multiply operation then the order is arbitrary because of the associative property . However, as shown below, changing the adjustment order can change the resulting demand if there are operations used such as add. Row 1: 100+10=110 Row 2: 110*1.5=165 Row 3: 165*0.8=132 "Demand Pattern A" multiplier at current time step = 2 Adjusted Demand: 132*2 = 264 What if a junction has two pattern multipliers applied? Each base demand will have the demand adjustments in the calculation options dialog applied (in order). Each of those adjusted base demands will have their respective pattern multiplier applied. Those adjusted demands are summed. The example below assumes that the calculation options adjustment order matches the first example above (add operation last). Row 1: 100*1.5=150 Row 2: 150*0.8=120 Row 3: 120+10=130 "Demand Pattern A" multiplier adjustment at current time step: 130*2=260 Row 1: 80*1.5=120 Row 2: 120*0.8=96 Row 3: 96+10=106 "Demand Pattern B" multiplier adjustment at current time step: 106*0.5=53 Adjusted demand at junction J-1 at current time step: 260 + 53 = 313 See Also Forum: How does Watergems CONNECT Edition handle multiple demand adjustments (via Calculator Options) applied to the same element? Wiki: Calculated demand does not match entered demand Wiki: How to edit demands, unit demands, or a subset of demands globally Wiki: Importing Demands From A Spreadsheet
↧
↧
Wiki Page: Can a model be detached from a DWG when integrated with AutoCAD?
Product(s): WaterGEMS, WaterCAD, HAMMER, SewerGEMS, SewerCAD, StormCAD, CivilStorm, PondPack Version(s): V8i and CONNECT Edition, as of 10.00.00.50 Area: Modeling Problem Can a hydraulic model be detached from a DWG when integrated with AutoCAD? Solution Currently there isn't a direct option to detach a Bentley Hydraulic Model from a DWG, but you do have a couple of options. Option 1: Export to DWG. The exported DWG can then have a different hydraulic model imported. You could delete the hydraulic model elements/linework first before performing the export. Option 2: Create a new DWG and reference in any original linework. After referencing the original DWG, then you can "Bind" it to the new DWG if needed. See Also What files are necessary to work with a WaterCAD for AutoCAD drawing? Saving a hydraulic model when using the AutoCAD platform (ie. integrated)
↧
Wiki Page: "Unable to Initialize DAO / Jet db engine" when exporting to Inroads
Product(s): StormCAD, Civilstorm, SewerGEMS Version(s): 10.00.00.40 Area: Data Import /Export Problem After exporting a model to InRoads format (.SDB) upon opening the file the in InRoads the error message "Unable to Initialize DAO / Jet db engine" is generated. Solution In the label names of your elements in StormCAD look for quotation marks ( " ) and remove them. After locating all the quotation marks export the file to InRoads and open it. Defect #695942 has been filed for a change in an upcoming release of the software. See Also InRoads crashes when viewing and editing a model imported from a storm-sewer product
↧
Forum Post: RE: Pump and Darwin Designer
Two problems: 1- You say 'you will know that the pump station will maintain a hydraulic grade'. But I do not know the HGL. Knowing HGL needs head losses and I have not pipe diameters (since it is going to be designed after) to know head losses. 2- Besides, The pump is a Booster Pump and can not be replaced with a Reservoir.
↧