Product(s): WaterGEMS, WaterCAD, HAMMER, SewerGEMS,CivilStorm,SewerCAD, StormCAD, PondPack Version(s): 08.11.XX.XX and later (features vary) Environment: N\A Area: Layout and Data Input How To How to filter a FlexTable by Query, Selection Set, or by selecting from drawing pane for reporting, global edits, etc. Background There are cases when a user may want to globally edit only certain elements in a FlexTable. In such a case, you need to use a filter to remove some of the elements from the FlexTable. Below are steps to do this. Option 1: Filter by attribute Option 2: Filter by selection set Option 3: Filter by selecting elements from the drawing pane Option 4: Select from Drawing (Available in CONNECT Edition, version 10.00.00.40 and later) Note: You can only edit a selection set of one element type at a time. For example, you can't adjust the elevation for valves and pumps at the same time. Steps to Accomplish Option 1 - By attribute To filter a FlexTable, open the element FlexTable and right-click on any column header. Next, choose Filter > Custom. This will open the Query Builder dialog. Next, you will need to create the query you want to filter the FlexTable with. For instance, you may want to only view the pipes with a diameter of 250 mm. If such a case, you would search the Fields table on the left for "Diameter". Double-click this and it will appear in the section at the bottom of the Query Builder dialog. Next, select the operator, such as "=". Next, click the Unique Values button in the upper right and then double-click the value you want to filter by. When you are done, the Query Builder dialog will look similar to the screenshot below NOTE: If you want to filter by more than one item, you can select the "AND" operator from the middle of the dialog and then go through the process above once more. Once you click Okay, the filter will be applied. The FlexTable will now look similar to the screenshot below. Note that it says "FILTERED" in the lower right of the FlexTable. In the lower left, if says that only some of the elements are displayed (in the screenshot above, "4 of 17 elements displayed"). These are indicators that a filter is applied. Now when you globally edit the FlexTable, only the elements that are displayed will be changed. All other elements will be left with their original values. To do this, right-click on the column header you want to change and choose "Global Edit". A new dialog will open. Choose the operator. For numerical fields, like diameter, you have an option to "Set" and use mathematical operators, like Add and Multiply. For text fields, only the Set option is available. Choose the operator and enter a value and the value in the FlexTable will change. To remove the filter, right-click on any column header once more and choose Filter > Reset. This will reset the filter and display all elements. Option 2 - by Selection Set Another way that you can filter and edit only some elements is via the steps below: 1) Create a selection set of the elements that you want to filter based on 2) Make sure the selection set of elements is selected in the drawing pane. Do this by going to 'View > Selection Sets' and double clicking on the selection set name. The elements in that selection set will highlight in red in your drawing pane by default unless you have changed the default selection set color. 3) With the elements selected go to 'View > FlexTables' to open the FlexTable manager. Locate the element table you want to create a report for and right click on it then choose "Open On Selection". This will open the FlexTable based on your selection in the drawing. 4) If necessary use the edit icon at the top of the FlexTable to edit your columns so that you have all the information you need to report on. Option 3 Similar to the Selection Set option, you can simply manually highlight elements in the drawing. Hold down the control button on your keyboard to select more than one item or use the selection tools located under the 'Edit' menu. You can then right click in the drawing pane and select Edit Group. The rest of the steps are the same as Option 2 above. This method can be less precise then using the other methods, but can be useful if you know which elements you want to change. Option 4 - Select from Drawing (Available in CONNECT Edition, version 10.00.00.40 and later) When you have a FlexTable open, i.e. Junction FlexTable, you can now select the rows in the table based on the current selection. To use the feature: Select some elements. Open a FlexTable for one of the selected elements and click the drop-down arrow for the “Select in Drawing” button. Click the last item, “Select from Drawing”. If there are any elements for the type of table you currently have open, it will select the rows for the elements selected. You can then filter down the contents of the table by right-clicking the row header and clicking on “Open on Selection”. See Also How can I edit my FlexTables? How can I create a selection set? Original Author: Scott Kampa

Product(s): SewerGEMS, StormCAD, CivilStorm, SewerCAD Version(s): 10.00.00.40 Area: Layout and Data Input When a tap is placed, a dashed line appears to show which link the tap is associated with. The tap element symbology properties now include a "Show Associated Link Decorations" field to control if this dashed line is displayed. By setting this to False the dashed line will not display. See Also Using LoadBuilder to assign Property Connections to the nearest element while creating taps and/or laterals How do Taps and Laterals work in the storm and sewer products? Property Connections

I can not find any thing Mr Jesse Dringoli

Product(s): SewerGEMS,CivilStorm,SewerCAD,StormCAD Version(s): 10.00.00.40 and later Environment: N\A Area: Layout and Data Input Introduction Property connection elements are used to load sewer models based on data at the level of individual properties. This is useful when you have loading data provided for all customers/properties based on metering, number of occupants/fixture units, or simply flow per property, and you would like to see it in your hydraulic model (rather than lumping all loads into manholes). Layout and Connections A Property Connection can be placed manually in a model by selecting Layout, then either Property Connection or Lateral. Property connections can be connected to a downstream gravity network using lateral links. Laterals connect to tap elements and most gravity nodes such as manholes, transitions, and catch basins. Taps can connect to channels and manholes. Property connections cannot be connected to pressure elements. Laterals can only make a single connection to a tap or other hydraulic element. There cannot be any hydraulic elements on the upstream side of a Property Connection. However, a Property Connection can be the Outflow Element for a catchment. Create Property Connection elements and assign loads Option 1: A Property Connection can be placed manually in a model by selecting Layout, then either Property Connection or Lateral. The load data for each Property Connection can then be entered in the properties grid or FlexTable. Option 2: Create Property Connection elements via ModelBuilder, with the loading data attached to the data source. Then use LoadBuilder to assign the property connection flows to the nearest element. Assigning Property Connections to the Nearest Link LoadBuilder can be used to assign isolated Property Connection elements to the nearest element by creating a tap and lateral connection. Isolated Property Connections are those elements that are not connected to any lateral element. Laterals are automatically placed between the source element and the hydraulic network when using LoadBuilder and selecting Property Connection Load Data as the Available LoadBuilder Method. When this data source is used, it is assumed that that load data is already available in the Property Connection. For steps detailing this process, see the following article: Using LoadBuilder to assign Property Connections to the nearest element while creating taps and/or laterals Calculations Elevation of the ground and the lateral invert can be placed in the attributes of the Property Connection element but are not used in the hydraulic calculations. It is not possible to construct a profile through a lateral link and up to a Property Connection. Property connections are used for sanitary loading in the Implicit, Explicit and GVF Convex solvers, but not the GVF Rational solver. Property connections support hydrograph, pattern, and unit loads. They can also directly accept runoff as the outlet of a catchment. For the GVF Rational Solver, flow through a Property Connection must come from a Catchment. (Property Connection designated as the Outflow Element.) Query The query "Property Connections not connected to Nearest Link" is included in the Network Review Predefined Queries (version 10.00.00.40 and later). See Also Using LoadBuilder to assign Property Connections to the nearest element and create taps and laterals Introducing individual Property Connections to your model [VID] How to toggle tap node dashed line display Help Article "Property Connections" Original Author: Craig Calvin

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. 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. 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 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. Future versions of SewerGEMS may introduce a sewer Customer element type where the added detail of the tap+lateral+manhole would not be necessary. Note: Taps and laterals are not supported in the Dynamic Wave solver. With the SWMM solver, Laterals are treated as "dummy" conduits. The SewerCAD (GVF-Convex) solver does not do any hydraulic calculations in the lateral pipe. 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

Product(s): SewerGEMS Version(s): 10.00.00.40 and later Area: Modeling Introduction LoadBuilder can be used to assign isolated Property Connection elements to the nearest element by creating a tap and lateral connection. Isolated Property Connections are those that are not connected to any lateral element. Laterals are automatically placed between the source element and the hydraulic network when using LoadBuilder and selecting Property Connection Load Data as the Available LoadBuilder Method. When this method is used, it is assumed that that load data is already available in the Property Connection. Steps 1. Run the LoadBuilder tool from the Tools tab. 2. Click the New icon 3. Select Property Connection Load Data as the Available LoadBuilder Method and click Next. 4. Optional: Create a selection set containing the links elements (ie. Channel or conduit) that can have taps associated with them. 5. Optional: Create a selection set containing the Property Connection elements that are to be assigned with Loadbuilder. 6. Enter all fields on the Property Connection Nearest Link page and then click Next. Link Layer In standalone, when the […] button for Link Layer is clicked, the following dialog displays to select all elements of a particular type or a selection set containing conduits and/or channels. In ArcMap, when the […] button for Link Layer is selected, the following dialog displays and allows you to select the available Feature Class layer. Link ID Field Specify the source database field that contains the identifying label data. In standalone, MicroStation and AutoCAD platforms, this field is always “ElementID”. In ArcMap, multiple choice are given based on the columns available in the selected FeatureClass Layer. Property Connection Layer In standalone, when the […] button for Property Connection Layer is clicked, the following dialog displays to select all Property Connection Elements or available selection sets of Property Connection type. In ArcMap, when the […] button for Property Connection Layer is selected, the following dialog displays and allows you to select the available Feature Class layer. Property Connection ID Field Specify the source database field that contains the identifying label data. In standalone, MicroStation and AutoCAD platforms, this field is always “ElementID”. In ArcMap, multiple choice are given based on the columns available in the selected FeatureClass Layer. If Next is pressed without entering one of these fields, then one of the following errors will display. Link layer not provided Link ID Field not provided Property Connection Layer not provided Property Connection ID Field not provided If the selected Property Connection Layer doesn't contain any isolated Property Connection elements, then the following message will display. "There are no results available for the given input parameters. Please verify your data and try again." 7. The Results Preview page contains a list of the nearest elements for each Property Connection. A lateral will be created to connect elements listed in the Property Connection column with the corresponding assigned elements in the Nearest Element column. Based on the geometric location of a Property Connection, the Nearest Element that it is assigned to could be a link (conduit/channel) or node (catch basin, manhole, transition, cross section or headwall) element type. 8. On the last page of the LoadBuilder wizard, enter a name for the LoadBuilder run and click Finish. 9. Review and close the summary dialog. Close the Loadbuilder Manager. 10. Model Synchronization After a successful Property Connection nearest link run, one or more lateral and/or tap elements will be created. Therefore, a drawing needs to be synchronized to display them. Once the Summary Report and Load Manager are closed, the following dialog will display asking if you want to synchronize the drawing: If you click Yes, a drawing will be synchronized and new elements will be display. Otherwise, the drawing will remain out-of-sync. Active Topology An element's active topology state is considered when using LoadBuilder with Property Connection load data. LoadBuilder will not assign a property connection to an inactive element. A Property Connection will only be assigned to a link if both of its nodes are active. Properties of newly created Lateral and Tap elements Newly created Lateral and tap elements will have a default values from the active lateral and tap prototypes respectively. If a tap element is created, it will have a reference link (dashed line) connecting it to the nearest pipe. The dashed line can be turned off by setting the tap property "Show Associated Link Decorations" to False in Element Symbology. Property Connection Assignment The nearest element the Property Connection is assigned to will vary for different use cases. When is a tap node created on the nearest link element? If the Property Connection element is perpendicular to the nearest link, and the perpendicular intersection is not within 10ft of a valid node. If the Property Connection makes a perpendicular intersection with the nearest link within 10 feet of, or beyond the node, but the nearest node is invalid (eg. outfall). When is the nearest node used? If the Property Connection element is not perpendicular to the nearest link and the nearest node is valid (eg. manhole). If the Property Connection element is perpendicular to the nearest link, and the perpendicular intersection is not within 10ft of a valid node. A Property Connection element will be assigned to the nearest node if one of the following are true: The Property Connection element is close to (within 10ft) the valid node element (ie. manhole, catch basin, transition, cross section, headwall). This 10ft is a fixed distance and can’t be modified. If the Property Connection element is closer to an applicable node (ie. Manhole, catch basin, transition) then the lateral will be created from the property connection element to the node. See Also Wiki: Property Connections Wiki: How to toggle tap node dashed line display WIki: How do Taps and Laterals work in the storm and sewer products? Blog [VID]: Introducing individual Property Connections to your model

It looks like the version you're using does not have that topic there. I've copied the section below, from the CONNECT Edition help. May I ask why you need to know this information? Are you a student, needing to cite this for a thesis perhaps? A bit more context may help us better assist you. Pressure Benefits The benefit of the hydraulic performance is measured by using junction pressure (P) improvements. Two types of pressure benefit are provided in Darwin Designer, namely dimensionless benefit and unitized benefit. Dimensionless Pressure Benefit The pressure improvement for dimensionless benefit is proposed as a ratio of pressure difference between the actual pressure and a user-defined reference pressure. The benefit is normalized by the junction demand (JQ). The factors are also introduced to enable a modeler to convert and customize the hydraulic benefit function. Unitized Pressure Benefit Pressure benefit resulting from a design and rehabilitation can also be quantified by using the unitized average pressure improvement across the entire system. The benefit functions can be given as follows: The advantage of using the unitized pressure benefit function is that a modeler is able to evaluate the average pressure enhancement for the investment. It is worth being aware of the value of the dollars spent.

I have a series of six text files that contain time-depth information for six different return events (two columns - time and cumulative depth). How can I import these into PondPack? I see where to create the different events, but I would like to import the depths rather than type them all in. My import button is greyed out. Thanks, Josh Mauritz

Applies To Product(s): Bentley SewerGEMS, Bentley Civilstorm Version(s): 08.11.XX.XX Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem Can ModelBuilder be used to import time-depth curve storm data? Solution Yes, it can be used to import certain minimal parts of the time-depth curve field data, but cannot import the time vs. depth table values. The reason is because the data table values are a collection field that are nested with in a the storm data that is another collection field. This makes it complicated to access. The workaround is to create your time-depth curves using the manual method, but copy and paste in the data table information if you have it in a spreadsheet. After the information is input you will export the time-depth curve to the engineering libraries , so it can be imported the next time you need the information.

Hello Josh, The import button is only available for the "User Defined IDF Table". Option 1: If you have another model with the Time-Depth storm events already entered: Open the model containing the Time-Depth storm and export it to an engineering library. Then you could open the new model and import the storm events from the engineering library. Option 2: If the storm events have not been entered in any model. You can create a time-depth storm and create 6 return events. Then open the text files with Excel and copy/paste the data from Excel into PondPack. As mentioned in the first option, this storm event could be exported to an engineering library and reused by another model. I don't recommend using ModelBuilder to import the time-depth data because it does not include the table values. See Also: Can ModelBuilder be used to import time-depth curve storm data?

See my comments within your post below: You can create a time-depth storm and create 6 return events. I HAVE DONE THIS. Then open the text files with Excel and copy/paste the data from Excel into PondPack. THIS IS THE PART I CAN'T FIGURE OUT. HOW DO I SPECIFICALLY PASTE THE CUMULATIVE RAINFALL DEPTHS INTO THESE STORMS? WHAT DO I CLICK IN PONDPACK TO ALLOW ME TO PASTE THESE VALUES? I HAVE A FEELING I AM MISSING SOMETHING REALLY OBVIOUS, BUT I CAN'T GET BY IT. Thank you, Josh

Dr.Jesse Dringoli. Greetings I'm a PhD student I brought a doctoral of using artificial intelligence algorithms in the field of water distribution system So I need the fitness function and relations and equations A private company that Bentley is the oldest sources of these programs and equation Unfortunately, I bought a copy of water GWMS Connect Edition, but unfortunately did not work on my lapفخح and also bought a copy waterCAD Connction edition also did not work I need touse Darwin Designer and other genetic algorithms that you have programs Thank you for your company

Here is a video showing the steps. Make sure you copy the depths without including the first one (associated with 0 hours). I pressed [Ctrl]+V to paste. (Please visit the site to view this video)

Ibrahim, The installation issue is a separate topic, so I will split that off into a separate thread. I will reply shortly regarding fitness.

Hi Ibrahim, I have sent you a private message regarding this. I would like to ask a few questions offline first, to help troubleshoot. Thanks,

Applies To Product(s): Bentley HAMMER Version(s): 08.11.03.XX+ Area: Output and Reporting Original Author: Scott Kampa, Bentley Technical Support Group How To: View HAMMER results for multiple scenarios in the Transient Results Viewer. Steps to Accomplish If you have multiple scenarios where you have different protection setup, such as different devices or different setups for a single protection device, it is possible to view Time History and Extended Node Data results for more than one scenario on a single graph. This applies to HAMMER V8i SELECTseries 3 (08.11.03.XX) and higher. To do this, make sure you have computed all scenarios that you want to graph and then open the Transient Results Viewer. Choose the Time History tab (this works for Extended Node Data as well). You will see an item called Additional Scenarios. Click the ellipsis button next to this and the dialog below will open: This shows all additional scenarios that have been computed. The active scenario you are already will not be listed. Check the scenario or scenarios you want to view in addition to the active scenario and click OK. Now when you plot a graph, you will see results for both the active scenario and the other scenarios you selected. Note that this option would only work in the report point you are graphing exists in all scenarios you are graphing. See Also A Tip on Comparing Results from Multiple Scenarios in HAMMER General HAMMER FAQ

Product(s): WaterCAD, WaterGEMS, PondPack, StormCAD, SewerCAD, FlowMaster, CulvertMaster, Hammer, SewerGEMS, CivilStorm Version(s): Various Area: General Original Author: Shahzaib Bukhari, Bentley Technical Support Group Background This article documents compatible platforms (AutoCAD, MicroStation and ArcMap) and Operating Systems for a range of Haestad product versions. WaterCAD & WaterGEMS Version 10.00.00.49 (CONNECT Ed.) 08.11.06.58 (SS6) & 08.11.06.113 (SS6 with CONNECT Integration) 08.11.05.61 (SS5) 08.11.04.57 08.11.04.58 (SS4) 08.11.04.50 (SS4) 08.11.03.16 08.11.03.17 08.11.03.19 (SS3) 08.11.02.31 (SS2) 08.11.01.32 (SS1) Date Released 2016-Oct-12 2015-Aug-27 2014-Aug-4 2013-Jul-1 2013-May-6 2011-Jul-8 2010-Nov-24 2009-Oct-26 O/S compatibility * = certified Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all) Windows 7, SP1(32 bit/64 bit) Windows Vista SP2 (32 bit/64 bit) Windows 8, 8.1(32/64 bit) Windows 10 Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Note: Windows XP is no longer supported. Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows XP SP3 (32-bit)* Windows 2008 Server R2 (64 bit only)* Windows 2008 Server (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows 7* Windows XP SP2 or later Windows XP SP2 or later (64-bit) Windows Server 2003 SP2 or later Windows Vista Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows Vista SP2* Windows XP SP1/SP2 Windows XP (64 bit) Windows Vista SP0 Windows 2008 Server Windows 7 Supported AutoCAD Versions (*= basic testing only) 2017(32/64-bit), 2016 (32/64-bit) 2016 (32/64-bit)2015 (32/64-bit) 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2012 (32/64 bit) 2011 (32 bit) 2011 (64 bit)* 2011 2010* 2010 2009* Certified MicroStation versions (older versions also supported) 8.11.7.x and 8.11.9.x 8.11.7.X & 8.11.9.X 08.11.09.459(SS4) 08.11.09.357 (SS3) 08.11.07.443 (SS2) 08.11.09.xx (SS3) 08.11.07.xx (SS2) 8.11.7.443 (SS2) 08.11.09.xx (SS3) 8.11.7.443 (SS2) 8.11.7.x Supported ArcMap versions in WaterGEMS (earlier versions should work, not tested) 10.3 - 10.4.1 10.2.1, 10.3.X 10.2 10.2.1 10.2 10.1 SP1 10.0 SP5 10 SP5 10.1 SP1 9.3.1 SP2 10 (Certified in 10 only) 9.3 10 9.3 9.3 SP1 Version of .NET needed 4.5.1 3.5 SP1 (08.11.06.58), 4.5.1 (08.11.06.113) 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 + SP1 PondPack Version 08.11.01.56 08.11.01.54 08.11.01.51 10.01.04.00 Date Released 3/8/2012 12/16/2010 10/26/2009 11/7/2008 O/S compatibility * = certified Windows Vista SP2* Windows XP SP3 (32/64 bit)* Windows XP SP2 or later Windows XP SP2 or later (64 bit) Windows Server 2003 SP2 or later Windows 7 Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows 8, 8.1 Windows 10 Windows XP SP3 (32/64 bit)* Windows 7 Windows XP SP2 or later Windows XP SP2 or later (64 bit) Windows Server 2003 SP2 or later Windows Vista SP2* Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3 (32/64 bit)*Windows Vista SP2*Windows XP SP2 or laterWindows XP SP2 or later (64 bit)Windows Server 2003 SP2 or laterWindows 2008 ServerWindows 7Windows 2008 Server R2 Windows XP SP1-SP3 (32/64 bit)*Windows Vista SP1 (32 bit)*Windows Vista (64 bit) Windows Server 2003 (32/64 bit) Supported AutoCAD Versions ( * = basic testing only) 2012 (32 bit)* 2011 (32 bit)* 2011 2010 2010 2009* N/A Certified MicroStation versions (older versions also supported) 8.11.7.x and 8.11.9.x 8.5.xx.xx /8.11.7.xx 8.11.5.x N/A ArcGIS versions in Pondpack N/A N/A N/A N/A Version of .NET needed 3.5 SP1 3.5 SP1 3.5 SP1 1.1 StormCAD Version 10.00.00.40 (CONNECT Edition) 08.11.05.113 (SS5 with CONNECTION Client) 08.11.05.58(SS5) 08.11.04.54 (SS4) 08.11.03.83/84(SS3) 08.11.03.77(SS3) 08.11.02.75(SS2) 08.11.02.38(SS2) Date Released 8/18/2016 2/10/2016 5/8/2015 6/3/2014 7/15/2013 1/7/2013 11/7/2011 12/16/2010 O/S compatibility * = certified Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all) Windows 10*, Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit) Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows XP* Windows Server 2003* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Wndows Server 2003 x64* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows 8 (32/64 bit)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows Vista SP2* Windows XP SP3*Windows 7(32/64 bit)*Windows XP SP2 or later (32/64 bit)Windows Server 2003 SP2 or laterWindows VistaWindows 2008 Server (32/64 bit)Windows 2008Server R2 (64 bit only) Supported AutoCAD Versions ( * = basic testing only) 2017(32/64-bit), 2016 (32/64-bit) 2016 (32/64-bit) 2015 (32/64-bit) 2016 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2012 (32/64 bit)2011 (32/64 bit) * 201120102009* Certified MicroStation versions (older versions also supported) V8i SS4 V8i SS3 V8i SS3 08.11.09.357 (SS3) 08.11.7.443 (SS2) 08.11.09.357 (SS3) 08.11.7.443 (SS2)8.11.09.357 (SS3) 8.11.7.443 (SS2)8.11.9.209 (beta) 8.11.5, 8.11.7 Version of .NET needed 4.5.1 4.5.1 3.5 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 SewerCAD Version 10.00.00.40 (CONNECT Edition) 08.11.05.113 (SS5 with CONNECTION Client) 08.11.05.58(SS5) 08.11.04.54 (SS4) 08.11.03.84 08.11.03.83 (SS3) 08.11.03.77 (SS3) 08.11.02.75 (SS2) 08.11.02.49 (SS2) 08.11.02.46 (SS2) Date Released 8/18/2016 2/10/2016 05/08/2015 07/15/2013 07/15/2013 01/17/2013 11/07/2011 12/16/2010 07/01/2010 O/S compatibility * = Certified Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all) Windows 10*, Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit) Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows XP SP3 (32 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows Server 2003 (32/64 bit)* Windows 8 (32/64 bit)* Windows 7 (32/64 bit)* Windows XP SP3 (32 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows Server 2003 (32/64 bit)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows Vista SP2 (32/64 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 (32/64 bit) Windows Vista SP0/SP1 (32/64 bit) Windows 2008 Server SP1/SP2 (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3*Windows Vista SP2 (32/64 bit)*Windows 7 (32/64 bit)* Windows Server 2003 SP2 (32/64 bit) WindowsVista SP0/SP1 (32/64 bit) Windows 2008 Server SP1/SP2 (32/64 bit) Windows 2008 Server R2 (64 bit only) Supported AutoCAD Versions ( * = basic testing only) 2017 (32/64-bit), 2016 (32/64-bit) 2016 (32/64-bit) 2015 (32/64-bit) 2016 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2012 (32/64 bit)2011 (32/64 bit) 20112010 20112010 Certified MicroStation versions (older versions also supported) V8i SS4 V8i SS3 V8i SS3 08.11.09.357(V8i SS3) 08.11.09.357 (SS3)08.11.07.443 (V8i SS2) 08.11.09.357(SS2)08.11.07.443 (V8i SS3) 08.11.07.443 (SS2) 08.11.09.357 (V8i SS3) 8.11.7.x 8.11.7.x Version of .NET needed 4.5.1 4.5.1 3.5 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 FlowMaster Version 08.11.01.03 08.11.00.03 08.01.071.00 08.01.068 Date Released 11/14/2009 8/27/2008 3/6/2007 11/10/2006 O/S compatibility * = Certified Windows XP SP3 (32/64 bit)* Windows Vista SP2* Windows XP SP2 or later (32/64 bit) Windows 7 (32/64 bit) Windows Server 2003 SP2 or later (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows 8, 8.1 Windows 10 Windows XP*Windows Vista* Windows Server 2003Windows Server 2003(64bit) Windows XP (64 bit) Windows Vista (64 bit)Windows 7 Windows 2000*Windows 2003*Windows XP (32/64 bit)*Windows Vista (32/64 bit)* Windows 2000*Windows XP (32/64 bit)* Version of .NET needed 2.0 2.0 1.1 1.1 CulvertMaster Version 03.03.00.04 03.02.00.01 03.01.010.00 03.01.009.00 Date Released 11/5/2009 8/11/2008 2/14/2007 12/6/2005 O/S compatibility * = certified Windows Vista SP2* Windows XP SP3 (32/64 bit)*Windows XP SP2 or later (32/64 bit)Windows Server 2003 SP2 or laterWindows 2008 ServerWindows 7Windows 2008 Server R2 Windows 8, 8.1 Windows 10 Windows Server 2003 SP1 or laterWindows Server 2003 (64 bit)Windows XP SP2 or later*Windows XP (64 bit)Windows Vista*Windows Vista (64 bit) Windows 2000*Windows Server 2003*Windows XP (32/64 bit)*Windows Vista (32 bit/64 bit)* Windows 2000*Windows XP (32/64 bit)* Version of .NET needed 2.0 2.0 2.0 1.1 HAMMER Version 10.00.00.49 (CONNECT Ed.) 08.11.06.58 (SS6) & 08.11.06.113 (SS6 with CONNECT Integration) 08.11.05.61 (SS5) 08.11.04.58 08.11.04.58 (SS4) 08.11.04.50 (SS4) 08.11.03.16 08.11.03.17 08.11.03.19 (SS3) 08.11.02.31 (SS2) 08.11.01.32 (SS1) Date Released 2016-Oct-12 2015-Aug-27 2014-Aug-4 2013-Jul-1 2013-May-6 2011-Jul-8 2010-Dec-7 2009-Oct-26 O/S compatibility * = certified Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all) Windows 7, SP1(32 bit/64 bit) Windows Vista SP2 (32 bit/64 bit) Windows 8, 8.1(32/64 bit) Windows 10 Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Note: Windows XP is no longer supported Windows 8 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows XP SP3 (32 bit)* Windows 2008 Server R2 (64 bit only)* Windows 2008 Server (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3* Windows 7* Windows XP SP2 or laterWindows XP SP2 or later (64 bit)Windows Server 2003 SP2 or later Windows Vista Windows 2008 Server (32/64 bit)Windows 2008 Server R2 (64 bit only) Windows XP SP3*Windows Vista SP2*Windows XP SP1/2Windows XP (64 bit)Windows Vista SP0Windows 2008 Windows 7 Supported AutoCAD Versions ( * = basic testing only) 2017 (32/64-bit), 2016 (32/64-bit) 2016 (32/64-bit) 2015 (32/64-bit) 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2012 (32/64 bit)2011 (32/64 bit) 20112010* 20102009* ArcGIS versions in HAMMER 10.3 - 10.4.1 10.2.1, 10.3.X 10.2, 10.2.1 10.2 (build .58 only)10.1 SP110.0 SP5 10.0 SP5 10.1 9.3.1 SP210.0 (Certified in 10.0 only) 9.3.1 SP110.0 9.39.3.1 Certified MicroStation versions (older versions also supported) 8.11.7.x and 8.11.9.x 8.11.7.X & 8.11.9.X 08.11.09.459 (SS4) 08.11.09.357 (SS3) 08.11.07.443 (SS2) 08.11.09.357 (SS3) 08.11.07.443(SS2) 08.11.07.443 08.11.07.443 8.11.7.x Version of .NET needed 4.5.1 3.5 SP1 (08.11.06.58), 4.5.1 (08.11.06.113) 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 SewerGEMS Version 10.00.00.40 (CONNECT Edition) 08.11.05.113 (SS5 with CONNECTION Client) 08.11.05.58 (SS5) 08.11.04.54(SS4) 08.11.03.83/84 (SS3) 08.11.03.77 (SS3) 08.11.02.75 (SS2) 08.11.02.49(SS2) Date Released 8/18/2016 2/10/2016 05/08/2015 06/03/2014 07/15/2013 12/19/2012 11/07/2011 12/16/2010 O/S compatibility * = certified Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all) Windows 10*, Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit) Windows 8, 8.1 (32/64 bit)*Windows 7 SP1 (32/64 bit)*Windows Vista SP2 (32/64 bit)* Windows 8, 8.1 (32/64 bit)*Windows 7, 7 SP1 (32/64 bit)*Windows Vista SP2 (32/64 bit)* Windows 8 (32/64 bit)*Windows 7 (32/64 bit)*Windows XP SP3 (32 bit)*Windows Server 2003 (32/64 bit)*Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)*Windows 2008 Server R2 (64 bit only)* Windows 8 (32/64 bit)* Windows 7 (32/64 bit)*Windows XP SP3 (32 bit)*Windows Server 2003 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)Windows 8 (32/64 bit)* Windows XP SP3 (32 bit)*Windows 7 (32/64 bit)*Windows Server 2003 SP2 or later (32/64 bit)Windows Vista SP2(32/64 bit)Windows 2008 Server (32/64 bit)Windows 2008 Server R2 (64 bit only) Win XP SP3* Win 7 (32/64 bit)*Windows Server 2003 SP2 or later (32/64 bit)Windows Vista SP0/SP1 (32/64 bit)Windows 2008 Server SP1/SP2 (32/64 bit)Windows 2008 Server R2 (64 bit only) Supported AutoCAD Versions (* = basic testing only) 2017 (32/64-bit, 2016 (32/64-bit) 2016 (32/64-bit) 2015 (32/64-bit) 2016 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2011 (32 bit)* 2013 (32/64 bit)2012 (32/64 bit)2011 (32 bit) * 2012 (32/64 bit)2011 (32 bit)2011 (64 bit)* 20112010 Certified ArcMap versions (older versions also supported) 10.2 - 10.4.1 10.3, 10.2.2, 10.2.1, 10.2 10.3, 10.2.2, 10.2.1, 10.2 10.2 SP110.2 10.2, 10.1 SP1, 10.1, 10.0 10.1 10.0 9.3.1 SP2 + 10.0 9.3.x Certified MicroStation versions (older versions also supported) V8i SS4 V8i SS3 V8i SS3 08.11.09.357 (SS3) 08.11.09.357 (SS3) 08.11.09.357 (SS3)8.11.7.443 (SS2) 08.11.7.x08.11.09.209 (beta) 08.11.7.x Version of .NET needed 4.5.1 4.5.1 3.5 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 CivilStorm Version 10.00.00.40 (CONNECT Edition) 08.11.05.113 (SS5 with CONNECTION Client) 08.11.05.58 (SS5) 08.11.04.54 (SS4) 08.11.03.83/84 (SS3) 08.11.03.77 (SS3) 08.11.02.75 (SS2) 08.11.02.65 (SS2) Date Released 8/18/2016 2/10/2016 05/08/2015 6/03/2014 7/15/2013 1/17/2013 11/07/2011 12/16/2010 O/S compatibility * = certified Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all) Windows 10*, Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit) Windows 8, 8.1 (32/64 bit)*Windows 7 SP1 (32/64 bit)*Windows Vista SP2(32/64 bit)* Windows 8, 8.1 (32/64 bit)*Windows 7, 7 SP1 (32/64 bit)*Windows Vista SP2 (32/64 bit) Windows XP SP3 (32 bit)*Windows Server 2003 (32/64 bit)*Windows Vista SP2 (32/64 bit)Windows 2008 Server (32/64 bit)*Windows 7 (32/64 bit)*Windows 8 (32/64 bit)*Windows 2008 Server R2 (64 bit only)* Windows XP SP3 (32 bit)* Windows 7 (32/64 bit)* Windows Server 2003 SP2 or later (32/64 bit)* Windows Vista SP2 (32/64 bit)* Windows 2008 Server (32/64 bit)* Windows 2008 Server R2 (64 bit only)* Windows 8 (32/64 bit) Windows XP SP3 (32 bit)* Windows 7 (32 bit/64 bit)* Windows Server 2003 SP2 or later (32/64 bit) Windows Vista SP2 (32/64 bit) Windows 2008 Server (32/64 bit) Windows 2008 Server R2 (64 bit only) Windows XP SP3*Windows 7 (32/64 bit)*WinXP (SP2 or later)WinXP 64-bit (SP2 or later) Windows Server 2003 SP2 (32/64 bit)*Windows Vista SP0/SP1 (32/64 bit)*Windows 2008 Server SP1/SP2 (32/64 bit)*Windows 2008 Server R2 (64 bit only)* Supported AutoCAD Versions (* = basic testing only) 2017 (32/64-bit), 2016 (32/64-bit) 2016 (32/64-bit) 2015 (32/64-bit) 2016 (32/64 bit 2015 (32/64 bit) 2014 (32/64 bit) 2015 (32/64 bit) 2014 (32/64 bit) 2014 (32/64 bit) 2013 (32/64 bit) 2012 (32/64 bit) 2011 (32 bit) 2013 (32/64 bit)2012 (32/64 bit)2011 (32 bit) 2012 (32/64 bit) 2011 (32/64 bit) 2011 2010 Certified MicroStation versions (older versions also supported) V8i SS4 V8i SS3 V8i SS3 08.11.09.357 (SS3) 08.11.09.357 (SS3)08.11.07.443 (SS2) 08.11.09.357(SS3)08.11.07.443 (SS2) 8.11.7.X 8.11.9.209 (beta) 8.11.7.X Version of .NET needed 4.5.1 4.5.1 3.5 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 Hydraulics and Hydrology Functionality in Subsurface Utilities If you own this license It will include these Storm-Sewer functions: SUE functionality Any Civil product which does not include GEOPAK Drainage, InRoads S&S or MX Drainage None None Any Civil product which includes GEOPAK Drainage, InRoads Storm and Sanitary, or MX Drainage Storm water peak flow design and analysis Max 100 Inlets in any single drainage model Storm/Sanitary attributes Utilities can be modeled in 3D No SUE attributes No Utility Conflict Tools Any of the above plus either: StormCAD Unlimited SewerCAD CivilStorm SewerGEMS Unlocks additional hydraulics calculation capabilities, according to which license is activated. Utilities can be modeled in 3D No SUE attributes No Utility Conflict Tools Any of above plus a SUE license Same hydraulic capabilities as above according to which hydraulics license is active. Unlocks SUE attributes Unlocks Utility Conflict Tools NOTE : If you have SELECT OpenAccess licensing, you will have all the features above available for use. AutoCAD LT (Lite) Bentley Hydraulic and Hydrology products only integrate with full versions of AutoCAD and will not integrate with AutoCAD LT (Lite).

Applies To Product(s): StormCAD, SewerCAD, CivilStorm Version(s): 08.11.XX.XX Area: Other Original Author: Jesse Dringoli, Bentley Technical Support Group Problem How do you set up the parts library in Civil3D and the conduit catalog in StormCAD and SewerCAD so that they are linked to draw the same conduit, type, size, etc, when using LandXML import/export? Solution After you export a StormCAD or SewerCAD model to the LandXML format and import the .XML file in AutoCAD Civil3D, the structures must be matched to items in a Civil3D parts library, otherwise, Civil 3D will try to use the closest sizes and elements will not come in correctly. Be sure to click the "Edit" button in the import options to designate the correct parts list, containing the same structures as the StormCAD/SewerCAD model. In this same window, you can link StormCAD structures to Civil3D "parts". The parts list used here is just a standard Civil3D parts library. Here are a couple of points worth noting: 1. Pipe networks in Civil3D are made up of 'parts' from a part catalog. However, in older versions of Civil3D, the default parts catalog only contained two 'Structures' under the 'Inlet-Outlets' category and they were both headwalls. That means that if you try to import a LandXML file created in StormCAD/SewerCAD into Civil 3D, and are using the default Parts Catalog, all of the StormCAD/SewerCAD catch basin elements will come into Civil3D as 'Headwall' structures. This may be confusing and may lead you to believe that there is a problem with the StormCAD/SewerCAD produced LandXML file - but that is not the case. The problem is that more 'Inlet-Outlets' structures need to be added in your Civil3D Parts Catalog. 2. You need to make sure you have the same pipe sizes in the Civil3D parts library as you have in StormCAD/SewerCAD because Civil3D matches based on pipe sizes. For example, if there is a 6 inch pipe in the LandXML data, Civil3D will match that with the pipe in its parts library that is closest to 6 inches. For structures (manholes, catch basins) the structure size needs to match. Note also that the LandXML import/export process isn't always guaranteed to give perfect results. For example Civil 3D 2010 makes you pick a part catalog to match different elements to. For example, if the Circular pipes in the LandXML file are matched up with the "Concrete Pipe" part catalog. If your circular pipes are a mixture of concrete and, say, PVC, then you need a Civil 3D part catalog that contains both Concrete and PVC, and all of the diameters needs to be unique. Also, Civil 3D doesn't support open channels, or grate/curb/combination inlets so that info won't come across. For more on configuration of Civil3D parts libraries, please contact Autodesk. *Pressure pipes export is not currently supported by Civil 3D's export process for Land XML files. See Also Catchbasins imported as manholes from LandXML Catchbasin structure data not being exported to LandXML file

During modeling Stormwater by SewerGEMS with SCS method I got few notification; would somebody; 1-Explain why I am getting those? 2- what does that mean? 3- how to solve that? The notification are: 22012 720 min_FEH Conduit 729 CO-312 33 A supercritical to subcritical transition is occuring for this element. Hydraulic Results 22013 720 min_FEH (N/A) -1 (N/A) 0 A supercritical to subcritical transition is occuring during this time-step. Hydraulic Results 22015 720 min_FEH Conduit 496 CO-79 39 Froude number is greater than 1 for sections in this element. Hydraulic Results 22018 720 min_FEH Conduit 580 CO-163 399 Conduit is operating under pressure. Hydraulic Results Regards......Mohamad