Hello Michael, The profile you provided is for scenario "Dynamisch Überflutung r-15-30". When I open the model you provided this scenario doesn't have outfall O-1 set to use a tidal boundary condition type. Perhaps you didn't save the model before uploading it or you uploaded an older revision of the model? From the image of the Cyclic Time-Elevation Curve you provided for outfall O-1, it appears that you are using the values from your spreadsheet's "Wasserstand Zustand 5 Faktor 2,5" column. The image of the curve data you provided starts with time=1min, however the elevations start with values that correspond with time=0min (in the spreadsheet). I recommend starting with time=0min and use the elevation values that correspond to these times in the spreadsheet. Note that there is a difference between entering this data starting at 0min and 1 min. The following profile shows how this change will impact the results. I am not seeing a total overflow volume of about 10 cu-m reported in the Hydraulic Reviewer for catchments or manholes in either of these configurations/scenarios. Try correcting the values in the "Cyclic Time-Elevation Curve" to match the values in the spreadsheet. If that doesn't help, then please provide the updated model files and images of matching results that you believe are incorrect. Why do you believe the results you are seeing are not plausible? The results that I'm seeing appear to be reasonable for what is being modeled. Were you expecting the total overflow volume to be less or more than 10cu-m? What software are you using? Is this an existing system that you want to find out how much will overflow, or are you designing a system to avoid overflow? Here are some related articles that might be helpful. How to find volume (such as overflow volume) through specific elements Troubleshooting unstable SewerGEMS and CivilStorm results using the implicit solver

Hola Scott, y gracias por atender mi solicitud Mi pregunta es: Como represento al pozo? Cual sería la elevación del pozo? Como mando el caudal desde el pozo al tanque que se encuentra a mayor altura? Como es la representación gráfica en watercad? Saludos cordiales

Hola Luis, ¿Cómo represento el pozo? El pozo está representado por el elemento reservorio. ¿Cuál sería la elevación del pozo? La elevación del depósito es la elevación de la superficie del agua en el pozo. ¿Cómo controlo el flujo del pozo al tanque que es más alto? Puedes usar un elemento de bomba para esto. ¿Cómo es la representación gráfica en Watercad? Depende si está utilizando una bomba de velocidad fija o una bomba de velocidad variable. Incluí una traducción de Google de este artículo a continuación, que explica cómo hacer esto en detalle. Contabilizando la reducción de pozos Problema ¿Cómo puedo considerar los efectos de extracción de una bomba de pozo, ya sea para una bomba de velocidad fija o de velocidad variable? Solución - Bombas de velocidad fija Para una bomba de velocidad constante, la extracción del pozo normalmente se toma en cuenta al compensar la curva de la bomba por la diferencia entre las elevaciones del agua subterránea estática y bombeada. La cantidad de extracción se restará del cabezal de la bomba y los nuevos valores utilizados para los datos del cabezal de curva de la bomba. Solución - Bombas de velocidad variable Con una bomba de velocidad variable, el enfoque anterior tampoco funciona, debido a la forma en que la velocidad escala la curva de la bomba. En este caso, se necesita una curva de pérdida de carga GPV, al lado de la bomba. A continuación hay una explicación. En el archivo de la hoja de cálculo a continuación hay dos hojas. communities.bentley.com/.../Well_2D00_VSP_2D00_Drawdown.xlsx El primero muestra la forma en que puede explicar la reducción modificando la curva de la bomba. Esto generalmente funciona bien para una bomba de velocidad constante. Sin embargo, se vuelve bastante difícil para un VSP porque la velocidad no se conoce antes del cálculo. Lo que realmente sucede es que la reducción puede aproximarse reduciendo el cabezal de succión en función del flujo. Esta solución se parece al gráfico a continuación y está en la segunda hoja del archivo. La curva de la cabeza del sistema azul no es drawdown mientras que las cuentas de naranja para drawdown. Tenga en cuenta que los resultados de flujo son los mismos para ambas hojas. Por ejemplo, en N (velocidad) = 0,8, Q = 70. Sin embargo, las cabezas de la bomba están apagadas para el enfoque de ajuste de la curva de la bomba porque se ajustó la curva de la cabeza de la bomba. Esto implica que es mejor ajustar la curva de la cabeza del sistema que la curva de la cabeza de la bomba. Pero el programa no puede hacer eso directamente sin iterar. Entonces, necesitamos insertar algo para causar la pérdida de carga como una función del flujo. Esto se puede hacer con una Válvula de Propósito General (GPV) que da la misma pérdida de carga que la tasa de extracción de la bomba (0.2 pies / gpm). Considere el siguiente modelo WaterCAD / WaterGEMS que contiene un VSP y GPV. communities.bentley.com/.../VSP-Drawdown-Example.zip NOTA: este modelo se guarda en la Edición CONNECT (10.00.00.49) y no se puede abrir en versiones anteriores. Las tuberías en este modelo fueron calibradas para proporcionar la misma pérdida de carga vs. curva de flujo. El modelo se calculó para tres velocidades con drawdown y una vez sin drawdown (4 escenarios). Como puede ver, los resultados del modelo coinciden con la hoja de cálculo. Tenga en cuenta que el GPV en este modelo se colocó en el lado de descarga, pero usar el lado de succión puede ser más preciso y le permitiría mirar NPSH, aunque los puntos de operación de la bomba son los mismos. En conclusión, la mejor manera de modelar la extracción en un pozo (incluso para bombeo de velocidad variable) es aproximar la velocidad de extracción (por ejemplo, 0.2 pies / gpm) con un GPV que tiene una curva con los puntos que corresponden a la reducción (ej. 0,0) y (100,200)).

Hello, Sushma and Scott! Thanks you! Surge tank and hydropneumatictank protection is existing devices Follow Scenarios and Alternatives; that shows E-ST1 and HT-2 are effects against negative pressure and two towers at location ending pipeline did not have much effect. I have been checked data inputs of the hydropneumatictank, that true. Yes, have negative pressure at pump (at suction pipe) due to check valve slam Wait for your commen.

Hello Ankit, We have created a service request for this issue and attached enhancement to it. So whenever this enhancement is considered in the future release of the product you will be notified about same via mail.

Hello Phanindra, The geometry collection field counts the geometry of a particular link/pipe element. This includes the start X,Y; stop X,Y; and the bend X,Y's. Hence the collection number will be always start + end + number of bends. Hence, if the number of bends are say 5; then the geometry collection would be 7. I am sharing screenshots of an example; Hope this helps.

Hello Huthyfa, Based on the discussion on this forum, here is the relevant wiki article; Catchment geometry lost when importing model prepared in InfoSWMM

Ok. . .thank you for the action. . .!

Hello Yashodhan, Thank you for your reply. I understand how geometry collection works. However what I mean to say is that while laying down Cast Iron or Ductile Iron underground piping, we can deflect the pipe upto a 5 degree angle without requiring 'bend' fittings. Consider the diagram provided below. The junction J-2 and J3 has 22°30' bends. However the point J4 doesnt have a 'bend fitting' but is being deflected by a 5° angle without using any bends. The diagram below is created in AutoCAD. While creating L-section drawings from surveys, a CAD drawing is intially prepared and then is extracted using modelbuilder into Watergems. Now I would like to import this entire span from J1 to J5 as a single pipe into WaterGems. Now in this span there should be two 'bends'. However when we import the model in Watergems, and look into the geometry collection, the point (J4 as per the AutoCAD drawing) is also being counted in since there is a defelection in the pipe angle at this point. However in the actual piping model there is no 'bend fitting' at this point. In short what I mean to say is that all the points that is being counted as a bend in WaterGems may not have an 'actual bend' in the piping model. In a complex model consisting of several pipes and long spans, at several locations the pipes are going to be 'deflected without using bend fittings'. However if we rely on the ' geometry collection' as a means for counting the number of bend fittings in the pipes, then it may not provide accurate results with respect to the actual piping model. Hence will counting bends by using 'geometry collection' provide a practical solution?

Hello Phanindra, Thanks for elaborating your query. The geometry as it appears in AutoCAD while laying out your network will be imported as it is in WaterGEMS. Hence when laying a network in AutoCAD if you introduce a deflection of 5 degrees in the AutoCAD polyline it will be recognized as a bend in WaterGEMS. When importing a DXF, the software will treat the network layout as geometry and import line breaks (WaterGEMS will create nodes on both sides of a line) and bends in a polyline as "bends". When you create a network in AutoCAD only the graphical properties are accounted for. The 5 degree bend can be represented graphically as a deflection but it is not possible for the software to ignore this as a bend. Also, it should be known that the model prepared in WaterGEMS is a hydraulic model and is representative of your actual system. The geometrical intricacies are generally accounted for hydraulically. In your case you can define the minor loss due to the 5 degree bend by specifying the coefficient or you can add the 5 degree bend loss in the library to use it for multiple pipes. One more alternative for this is identifying pipes with the 5 degree deflection in AutoCAD by adding a property field (maybe as a special name like PIPE_5 degrees). Then you can filter out those pipes while importing the DXF and create your network. After network is created you can model these pipes manually. Here are some articles which can help you; Importing an AutoCAD or MicroStation CAD file using ModelBuilder Using ModelBuilder to Import External Data Hope this helps.

Hello Yashodhan, Thanks for your reply. I totally agree to what you said regarding geometrical intricacies being accounted for hydraulically. Hence I think rather than accounting for the number of bends 'geometrically' it is more practical to account them 'hydraulically' as far as WaterGems/Hammer is concerned. In case of a complex model consisting of several pipes, I generally prefer doing so by considering a marginally higher pipe roughness or by considering a 10% increase in headloss (as often stated by Tom Walski and Tanay Kulkarni elsewhere in this forum) so as to simplify the process. However estimating the number of bends used in the actual piping model using 'gemoetrical collection' in WaterGems may not always render an accurate estimate. However sometimes Clients do want to know the number of bends and related diameters utilised in the model. In future updates if a separate field can be introduced where the user can manually enter the number of bends and friction factor explicitely (as per actual piping model) associated with each pipe and the same is reflected in the flextables and hydraulic inventory report (alongwith the respective diameter), then may be it can prove to be an additional helpful feature. Alternatively, an enhancement can be made in future updates such that the number of fittings and their types can be specified by the user in the 'minor loss collection items' field for relevant pipes. Then this data can be reflected in the hydraulic inventory report based on the associated pipe diameter. For example, the user can associate tees, bends etc for relevant pipes. They can later access the hydraulic inventory report to get a list of the total number of fittings used based on the relevant pipe diameters those fittings have been associated with.

While building a Storm Drain Network 3D Model using ModelBuilder Tool of Subsurface Utility Design and Analysis (MXRoad SS4), irrespective of shape and dimensions given, Manhole assumes a typical shape and size as shown below: - Is there any way by which, we can model Manhole in 3D with given shape and dimensions?

Hello Ankit, You would have to define a custom cell which would have the manhole dimensions and shape as per your requirements. Then you can select the custom cell for your manholes. Here is an article which describes assigning custom cells for MicroStation integrated mode. The same approach can be followed in SUDA. Using custom cells for element symbols in MicroStation Integrated mode Here is another article which can guide you; Understanding Haestad Hydraulics and Hydrology Functionality in Subsurface Utilities / OpenRoads Hope this helps.

Hello Phanindra, The feature to identify minor losses is already available in WaterGEMS. You can specify multiple types such as 45 degree, 90 degree bends, contractions, expansions etc. with their numbers and coefficients by directly importing from the library or specifying as per your requirements. Just keep the "Specify Local Minor Loss" field as "False" and specify each type of minor loss in the " " in the "Minor Losses" property for a pipe. Calculating the number of bends as N-2 (-2 is for deducting start and end nodes) can be used for pipes. However, for DI pipes you have a 5 degree bend which is not actually a bend. Wen you draw a pipe connecting two points in AutoCAD, with the 5 degree bend AutoCAD will recognize it as a bend too. The 5 degree bend not being a bend is a property for the DI pipe but for AutoCAD or WaterGEMS its a graphical entity. Hence, it will always be imported as a bend. Using fittings and other appurtenances is a part of detail engineering. For large projects it would be a cumbersome job to detail each pipe with these components. The hydraulics of these can be accommodated by either increasing the pipe length by 10% or by specifying minor losses in detail. Hope this helps.

Hello Yashodhan, Thanks for your patient reply. I am presently working on a transmission pipeline of around 6.8 km for a Sri Lankan Project. The L-Section model and the BOM of the entire pipeline has already been prepared for the entire system. The Client wants us to account for the losses of all the fittings individually in the WaterGems/Hammer model. It is their standard practise to incorporate as much details in the hydraulic model as possible. Hence I already have to manually take care of all the fittings in the system by specifying the friction factors and fittings quantity in the 'minor loss collection items' field for relevant pipes. It is as you said a 'cumbersome job' but it has to be done in this case because the Client requires it and technically is not ready to accept otherwise. Moreover, they would also want us to specify the number of fittings being associated with the pipes of different diameters in the WaterGems model and then would compare that data with the data available from the BOM of the actual piping system. So basically we have to create a 'Fittings table' alongwith the model manually and hand it over to them. I have faced this issue with another Client previously as well. This is the reason why I was mentioning if this situation can be solved by providing any enhancement in any future update.

Thanks for the response. . .but I am unable to edit the .cel file as it is showing write protected and opens in read-only mode only. . .can you help with this?

Product(s): WaterCAD, WaterGEMS, PondPack, StormCAD, SewerCAD, FlowMaster, CulvertMaster, Hammer, SewerGEMS, CivilStorm Version(s): Various Area: General Author: Bentley Technical Support Background This article documents compatible platforms (AutoCAD, MicroStation and ArcMap) and Operating Systems for a range of Haestad product versions. A Note on Hardware / System Requirements For hardware requirements (RAM, CPU, Video card), refer to the Readme.PDF file included in the installation folder of your Bentley Haestad product. In general, hardware requirements are highly dependent on the size and complexity of the model. The more elements and more complexity in the model and the longer the simulation duration, the more memory it will take up and the more a faster CPU will impact overall performance. Since modeling is done in 2D, Haestad products are not graphics intensive. For more information, see How to increase model performance / reduce run time. To download the latest versions of the products, please see the following link: Downloading Haestad / Hydraulics and Hydrology Software . WaterCAD & WaterGEMS Version 10.01.01.04 (CONNECT Ed. Update 1) 10.01.00.72 (CONNECT Ed. Update 1) 10.00.00.55 (CONNECT Ed.) 10.00.00.49 & 10.00.00.50(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 2018-May-9 2017-Dec-22 2017-June-16 2016-Oct-12 / 2016-Nov-28 2015-Aug-27 / 2016-Feb-10 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 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP1 (32 & 64-bit for all) Windows 10, Windows 8, Windows 8.1, Windows 7 SP1 (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 SP1 (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) See alternatives here . 2017, 2018, 2019 (32/64-bit) 2018, (32/64-bit), 2017(32/64-bit), 2018 (32/64-bit), 2017(32/64-bit), 2016 (32/64-bit) 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) See alternatives here . V8i SS4 V8i SS4 8.11.7.x and 8.11.9.x 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 Highest supported ArcMap ver. in WaterGEMS (earlier versions supported though not fully tested) 10.6 10.5.X 10.5.X 10.4.1 10.3.x 10.3.X (via patch) 10.2 10.1 SP1 10.0 10.0 9.3 SP1 Version of .NET needed 4.6.1 4.6.1 4.6.1 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 HAMMER Version 10.01.01.04 (CONNECT Ed. Update 1) 10.01.00.72 (CONNECT Ed. Update 1) 10.00.00.55 (CONNECT Ed.) 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 2018-May-9 2017-Dec-22 2017-June-16 2016-Oct-12 2015-Aug-27 2014-Aug-4 2013-Jul-1 / 2013-Nov-5 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 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all) 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 SP1 (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) See alternatives here . 2017, 2018, 2019 (32/64-bit) 2018, (32/64-bit), 2017(32/64-bit), 2018 (32/64-bit), 2017 (32/64-bit), 2016 (32/64-bit) 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* Highest supported ArcMap ver. (earlier versions supported though not fully tested) 10.6 10.5 10.5 10.4.1 10.3.X 10.2.1 (10.3.X in patch) 10.2 (build .58 only)10.1 10.1 10.0 10.0 9.3.1 Certified MicroStation versions (older versions also supported) See alternatives here . V8i SS4 V8i SS4 8.11.7.x and 8.11.9.x 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.6.1 4.6.1 4.6.1 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 StormCAD Version 10.01.01.04 (CONNECT Ed. Update 1) 10.01.00.70 (CONNECT Ed. Update 1) 10.00.00.45 (CONNECT Ed.) 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 2018-May-9 2017-Nov-17 2017-June-16 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 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10*, Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Server 2008/R2 Server 2012 Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Server 2008/R2 Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Server 2008/R2 Windows 8 (32/64 bit)* Windows 7 SP1 (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 SP1 (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) See alternatives here . 2017, 2018, 2019 (32/64-bit) 2018, (32/64-bit), 2017(32/64-bit), 2018, (32/64-bit), 2017(32/64-bit), 2016 (32/64-bit) 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) See alternatives here . V8i SS4 V8i SS4 V8i SS4 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.6.1 4.6.1 4.6.1 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.01.01.04 10.01.00.70 (CONNECT Ed. Update 1) 10.00.00.45 (CONNECT Ed.) 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 2018-May-9 2017-Nov-17 2017-June-16 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 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP 1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP 1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP 1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10*, Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Server 2008/R2 Server 2012 Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Server 2008/R2 Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Windows Vista SP2 (32/64 bit)* Server 2008/R2 Windows 8 (32/64 bit)* Windows 7 SP1 (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 SP 1(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) See alternatives here . 2017, 2018, 2019 (32/64-bit) 2018, (32/64-bit), 2017(32/64-bit), 2018 (32/64-bit), 2017 (32/64-bit), 2016 (32/64-bit) 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) See alternatives here . V8i SS4 V8i SS4 V8i SS4 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.6.1 4.6.1 4.6.1 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 SewerGEMS Version 10.01.01.04 (CONNECT Ed. Update 1) 10.01.00.70 (CONNECT Ed. Update 1) 10.00.00.45 (CONNECT Ed.) 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 2018-May-9 2017-Nov-17 2017-June-16 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 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP 1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP 1(32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10*, Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Server 2008/R2 Server 2012 Windows 8, 8.1 (32/64 bit)*Windows 7 SP1 (32/64 bit)*Windows Vista SP2 (32/64 bit)* Server 2008/R2 Windows 8, 8.1 (32/64 bit)*Windows 7, 7 SP1 (32/64 bit)*Windows Vista SP2 (32/64 bit)* Server 2008/R2 Windows 8 (32/64 bit)*Windows 7 SP1 (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 SP1 (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) See alternatives here . 2017, 2018, 2019 (32/64-bit) 2018, (32/64-bit), 2017(32/64-bit), 2018 (32/64-bit), 2017 (32/64-bit, 2016 (32/64-bit) 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 Highest supported ArcMap ver. (earlier versions supported though not fully tested) 10.6 10.5 10.5 10.4.1 10.3 10.3 10.2 SP1 10.2 10.1 10.0 9.3.x Certified MicroStation versions (older versions also supported) See alternatives here . V8i SS4 V8i SS4 V8i SS4 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.6.1 4.6.1 4.6.1 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.01.01.04 (CONNECT Ed. Update 1) 10.01.00.70 (CONNECT Ed. Update 1) 10.00.00.45 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 2018-May-9 2017-Nov-17 2017-June-16 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 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10, Windows 8, Windows 8.1, Windows 7 SP1 (32 & 64-bit for all), Server 2008/R2, Server 2012 Windows 10*, Windows 8, 8.1 (32/64 bit)* Windows 7 SP1 (32/64 bit)* Server 2008/R2 Server 2012 Windows 8, 8.1 (32/64 bit)*Windows 7 SP1 (32/64 bit)*Windows Vista SP2(32/64 bit)* Server 2008/R2 Windows 8, 8.1 (32/64 bit)*Windows 7 SP1 (32/64 bit)*Windows Vista SP2 (32/64 bit) Server 2008/R2 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 SP 1 (32/64 bit)*Windows 8 (32/64 bit)*Windows 2008 Server R2 (64 bit only)* Windows XP SP3 (32 bit)* Windows 7 SP 1 (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) See alternatives here . 2017, 2018, 2019 (32/64-bit) 2018, (32/64-bit), 2017(32/64-bit), 2018 (32/64-bit), 2017 (32/64-bit), 2016 (32/64-bit) 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) See alternatives here . V8i SS4 V8i SS4 V8i SS4 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.6.1 4.6.1 4.6.1 4.5.1 4.5.1 3.5 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 PondPack Version 10.00.00.02 08.11.01.56 08.11.01.54 08.11.01.51 10.01.04.00 Date Released 2018-Aug-8 2012-Mar-8 2010-Dec-16 2009-Oct-26 2008-Nov-7 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 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) See alternatives here . 2012 (32 bit) 2011 (32 bit)* 2012 (32 bit) 2011 (32 bit)* 2011 2010 2010 2009* N/A Certified MicroStation versions (older versions also supported) See alternatives here . 8.11.7.x and 8.11.9.x 8.11.7.x and 8.11.9.x 8.5.xx.xx /8.11.7.xx 8.11.5.x N/A Version of .NET needed 3.5 SP1 3.5 SP1 3.5 SP1 3.5 SP1 1.1 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 2003 Windows Server 2003(64bit) Windows XP (64 bit) Windows Vista (64 bit) 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 Haestad / 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's Haestad products only integrate with full versions of AutoCAD and will not integrate with AutoCAD LT (Lite). MicroStation CONNECT Edition As of May, 2018, the latest available versions of the Haestad products do not yet integrate with MicroStation CONNECT Edition. ProjectWise CONNECT Edition Integration See: ProjectWise CONNECT Edition Compatibility ArcGIS Pro As of April, 2018, ArcGIS / ArcMap Pro is currently not supported yet. Most users prefer the Standalone environment, so development has not yet focused on ArcGIS Pro.

Applies To Product(s): WaterGEMS, WaterCAD, HAMMER, SewerGEMS, SewerCAD, CivilStorm Version(s): V8i, CONNECT Edition Area: Modeling Original Author: Scott Kampa, Bentley Technical Support Group Problem When trying to use LoadBuilder, the following error message occurs: "Calculations returned the following error message: A very high number of Usage types were found. Please check whether the selected Usage type field is correct." Solution This is caused by an issue with the Type Field selected in LoadBuilder. For example "Load Type" for the Nearest Node method or "population density type" for the Load Estimation by Population method. This error message indicates that there are a large number of distinct types in the selected "type" field. The type field should be a field in the shapefile that contains the label of the “type” of load or demand for the corresponding load polygon/point. For example residential, commercial, industrial. This enables you to enter a different pattern (for methods like nearest node) or projection (flow per capita per time, for methods like load estimation by population) for each of the different types. For example you might want to assign a specific pattern only to residential loads vs. industrial, or a provide a different projection of demand/load for each type. So, there should be a relatively small number of distinct types in the field that you select, so that the list that you must populate isn’t too long (list of patterns at the end of the LoadBuilder process, or list of different projections to enter, for the projection methods). If you are seeing this message, that is usually an indication that you may not have selected the right field, or there is a problem with the field. If you do not have a need to set a different pattern/projection for each type of use (only one pattern for all loads/demands for methods like nearest node, or only one projection to apply to all loads, for methods like Projection), then you would select the “ ” option in the dropdown, which should automatically appear there. This will tell LoadBuilder that you don’t have a type field in your shapefile and that you will only have one pattern or projection for all loads. If you do want to set different projections for different types of population, then you will need to either pick the correct field in the shapefile that has those labels, or you need to check the field you are trying to pick, for issues. If the field has similar but slightly different labels for the desired type for example, you may need to add a new column to your shapefile (via ArcGIS for example) to show only the unique types. For example if the label for a residential type looks like “Residential12345”, then the custom field could truncate it to just “Residential”. Or, if you have number codes to represent different types of loads, then you'll need to simplify it so there’s one unique number for each distinct type that you want to appear as a row in the table at the bottom of the LoadBuilder wizard. See Also Related forum thread. How do each of the Loadbuilder methods work? Troubleshooting and Understanding LoadBuilder

Product(s): StormCAD, SewerCAD, WaterCAD, CivilStorm, WaterGEMS, Hammer, PondPack, CulvertMaster, FlowMaster Version(s): 08.11.XX.XX, 10.XX.XX.XX Area: Licensing Below you will find a list of wiki articles related to activating (Licensing) Bentley Hydraulics and Hydrology products. You can either scan this page for your error or use the CTRL + F function to open the "Find" tool in your browser to search the page based on a keyword. How to (General Information) The following articles contain detailed information on how Bentley's Hydraulics and Hydrology product licensing and activation works and how to configure it. Activate (license) Hydraulics and Hydrology Products Set the correct feature level in the Municipal License Administrator Manually check in a license Automate product activation Setting the Default Feature Configuration as an Administrator, for other Windows Accounts Using Custom Activation Groups to prevent unintended usage Set ELS feature configurations Locate the CAiHE Licensing and Activation Key Find registration / license information and version / build number for Hydraulics and Hydrology products Perform a clean uninstall and reinstall of the Hydraulic and Hydrology products Batch file to remove invalid activation status entries Troubleshooting The following articles can assist in troubleshooting licensing related errors or warnings. What do the different license statuses mean? General Licensing and Activation Troubleshooting for Haestad Products "Site has not been activated with server name and activation key on this machine, and a checked-out license is not available. Please run the License Tool" "Default license feature configuration not found. Product features may be limited. Please run the License Administrator." User Notification: "The number of active in this model exceeds the number of allowed for your license" The default license configuration is not retaining changes to a setting Product does not show up in the Municipal License Administrator "An error has occurred while attempting to verify the server and activation key" Default license feature configuration not found Unable to activate license with Deployed server: Bentley.lictransmit for Windows has stopped working Setting the Default Feature Configuration as an Administrator, for other Windows Accounts Products are listed multiple times in the Activation Status tab of the License Management Tool Usage Logging / Reporting What is usage and how is it calculated? Understanding, Monitoring and Managing Usage License usage logging for multiple instances of the same product on a machine License usage with AutoCAD integration At what point does license usage start when integrated with MicroStation? Do inactive elements count against the license count? Application And Usage Reporting [FAQ] How does a checked out license work for SELECT or ELS customers with product usage logging? See Also Product TechNotes and FAQs SELECTsupport TechNotes And FAQs Original Author: Craig Calvin

[quote userid="431557" url="~/products/hydraulics___hydrology/f/haestad-hydraulics-and-hydrology-forum/161705/profile-creation-in-sewergems/477647"]I want to see the Service Road Profile and Main Carriageway Profile.[/quote] Can you clarify what you mean by this? The Enhancement that Scott mentioned would enable you to include multiple, existing profiles in a custom report. These would be profiles of specific paths through the pipe network. If you're actually looking for a way to superimpose multiple lines on a single profile to show different ground surfaces, you could export the profile to DXF, then add the lines manually in another application like MicroStation or AutoCAD. See: Exporting profiles to .DXF files Also, if you have terrain models of the two different surfaces, you could use the Terrain Model feature to turn on one surface as "active", then look at the profile (which will display the surface from the active terrain model) Lastly, you could look into the enhanced profile cutting capabilities in OpenRoads Designer , which can utilize the same underlying hydraulics found in SewerGEMS.