I have a few questions regarding input data for a calibration study. Consider this model: (see attached image) Available Data: Pump Definitions Pump Station Delivery Pressure – P10 (kPa) – historical SCADA data source (Delivery Pressure) Pump Station Discharge – J2 (L/s) – historical SCADA data source (PS Discharge) Demands J3, J4, J5 and J8 (reduced from monthly meter readings (kl/m to L/s) Demand - J9 (L/s) – historical SCADA data source (SE-1) Tank Levels T-1 and T-2 (m) – historical SCADA data sources (SE-2 and SE-3) The network does not really have a pattern it is quite sporadic thus no demand pattern is defined, will this be an issue? Assuming I choose four snapshots for calibration and enter data (Steady State scenario set, with EPS snap shot set to true) Questions For my demands (J3,J4,J5 and J8) i. Should I enter these demands into the model and then use these as “demand adjustments” in the calibrator as well? ii. Should I enter the demand data for these nodes in the model via the nodes or meter element? For my demands (J9) i. I have entered the snapshot values from SCADA historical result as “Demand adjustments”? is this correct? ii. The node does not have any demand assigned to it in the model at this stage except the SCADA Element Other data i. Pump discharge is entered for each pump in the “observed target” tab, is this the correct place? ii. Pump Station discharge is entered in the “observed target” tab, is this correct? This is not a demand but flow at a pipe immediately out of the pump station. iii. Pump Station Delivery pressure is entered in the “observed target” tab, is this correct? As pressure not HGL. iv. Tank levels are entered as “Boundary overrides”, is this correct? v. Pump Statuses are entered as “Boundary overrides”, is this correct? vi. In one of the Snap Shots I have one pump off, if I switch off the pump (change status to off in the “boundary overrides” for this snapshot) do I need to set the pump discharge to zero? This seems to influence on the calibration result even when the pump is set to off in that time step. I have tank controls in place already in the model. Calibration ( Assuming now that I have calibrated and I am happy with the results) i. I export the result of my calibration (Scenario, Roughness, Demands), do I need all of them? ii. For demands export do I choose even distribution or base flow? Does it matter? remember I still don’t have any demand patterns defined for this model. Now Back at the model i. I create an EPS child scenario under my calibrated imported scenario since I need to simulate in an EPS environment? Is this the correct way to inherit the alternatives, demands etc. from the steady state calibrated scenario? ii. From the results of the calibration do I need to enter any data directly into my model (esp. for demands) or does the result export take care of it? If I do (need to enter data myself), what value do I use for the node where I am referencing historical SCADA – J9? If there was already demand data there or at any node would I have to add the total of the previous and the calibrated result? I know its handful of questions but these are the places where I found I had the most uncertainty, the exercises and examples given do not go into much detail. I look forward to your response.

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. 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 WaterCAD & WaterGEMS Version 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 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 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) 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) 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 Supported ArcMap versions in WaterGEMS (earlier versions should work, not tested) 10.3 - 10.4.1 10.3 - 10.4.1 10.2.1 10.2 10.2.1 10.3.X 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 HAMMER Version 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.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 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) 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* ArcGIS versions in HAMMER 10.3 - 10.4.1 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 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 StormCAD Version 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 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, 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) 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) 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.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.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 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, 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) 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) 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.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.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 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, 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) 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 Certified ArcMap versions (older versions also supported) 10.2 - 10.4.1 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 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.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 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, 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) 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) 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.5.1 4.5.1 3.5 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 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). ProjectWise Integration Bentley's Haestad products released after September 2015 are compatible with ProjectWise CONNECT Edition version 10.00.02.96.

Product(s): SewerGEMS, CivilStorm Version(s): 08.11.XX.XX Area: Calculations Problem Which version of the EPA SWMM numerical solver is used by SewerGEMS and CivilStorm, when the active solver is set to "Explicit" in the calculation options? Solution The SWMM solver version number used can be found by computing a model while using the Explicit SWMM solver. In V8i SELECTseries 5 and earlier, a text file will appear with the SWMM version number listed at the top. Starting with the CONNECT Edition of SewerGEMS and CivilStorm, the solver version can be seen in the SWMM output file, saved when saving the model. You can also refer to the below chart. Note : future versions of the program may offer the ability to turn on or off the "Bentley Enhanced" improvements that are included on top of the respective base SWMM solver version. as well as the possibility of selecting specific legacy SWMM solver versions. Enhancement # 136686 Bentley Hydraulic and Hydrology Product EPA SWMM Version SewerGEMS/CivilStorm CONNECT Edition (10.00.00.45) 5.1.012 SewerGEMS/CivilStorm CONNECT Edition (10.00.00.40) 5.1.010 SewerGEMS/CivilStorm V8i SELECTseries 5 (08.11.05.113) 5.1.007 SewerGEMS/CivilStorm V8i SELECTseries 5 (08.11.05.58) 5.1.007 SewerGEMS/CivilStorm V8i SELECTseries 4 (08.11.04.54) 5.0.022 SewerGEMS/CivilStorm V8i SELECTseries 3 (08.11.03.84) 5.0.022 SewerGEMS V8i SELECTseries 2 (08.11.02.46 and 08.11.02.49) 5.0.018 CivilStorm V8i SELECTseries 2 (08.11.02.62 and 08.11.02.65) 5.0.018 SewerGEMS (08.09.26.14 and 08.09.26.17) 5.0.011 CivilStorm (08.09.26.14 and 08.09.26.17) 5.0.011 What is meant by "Bentley Enhanced"? The EPA-SWMM solver included with SewerGEMS and CivilStorm is a "Bentley Enhanced" version, which means Bentley has added functionality so that it more seamlessly integrates with the SewerGEMS/CivilStorm data model and with other Storm-Sewer Products. It is important to note that as of the initial CONNECT Edition release of SewerGEMS and CivilStorm, the core SWMM hydraulic solver has not been modified by Bentley - it has simply been "enhanced" to provide more results. Details below: 1. HEC-22 Inlet Calculations 2. Ability to compute complex pond outlet structures 3. Headloss Calculations at structures including HEC-22 and Standard Headloss methods 4. Additional detailed results 5. Integrated LID results 6. Tractive Stress Calculations 7. Hydrogen Sulfide Modelling See Also Troubleshooting unstable SewerGEMS and CivilStorm model results using the Explicit SWMM Solver

We have created a video which explains how to Annotate Slopes in permille. communities.bentley.com/.../35218.video-changing-pipe-slope-annotation-units We will also log an enhancement to have permille be able to be selected from the pulldown of Slopes Annotation. Simon Pegg Bentley Civil Support

This replaces % with permille symbol. But we also need to multiply it by 1/10 to get the right value.

Applies To Product(s): WaterGEMS, HAMMER, WaterCAD Version(s): 08.11.XX.XX, 10.XX.XX.XX Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem My pumps are operating at a much higher rate than the design point. How do I fix this? OR What does the user notification "Pump exceeds the maximum operating point specified for the pump curve" mean? Solution The first step to solving this problem starts with understanding how pumps function in the hydraulics and hydrology products. You can find that explanation in this wiki . The second step is to check the pump curves for the pumps that are adding too much flow or head and make sure the curves are correct. If the curves are correct check the head and flow being output by the pump is on the pump curve. Next, check the demands in your model for the junctions, hydrants, tanks, and the HGL on your reservoirs that are downstream of the pump. The best way to check your demands on downstream elements is to make a selection set of all those nodes and then open your flextable based on that selection set. There are directions in the wiki found here that explain how to do this. With the flextable open add the column called "Demand" if it's not already. This wiki article will explain how to do that. Once that column is added you can right click on the column header and choose statistics to see the total sum of the demand and other important information. At this point you can also sort that column by right clicking on it and choosing Sort > Descending because you are likely looking for values in the column that are to high. After doing this you should scan all the demands to make sure they are correct. Note that for the reservoir there is no "demand" column. You should be checking the hydraulic grade in reservoirs to make sure that it is set correctly. Finally, if you are checking the demands for an EPS simulation you should use the time browser to choose the time step where the pumps are operating higher than the design point and then use the steps above to check the appropriate tables for the demands. What does the user notification "Pump exceeds the maximum operating point specified for the pump curve" mean? Pumps in water and storm water product line operate by adding enough head to system to balance the hydraulic grade in the system, namely by overcoming the losses and elevation differences between your upstream and downstream boundary conditions. The head and flow rate is defined on your pump definition curve. In the water products, like WaterGEMS and WaterCAD, the pumps need to also add enough flow to be able to fulfill the demand. This warning message usually indicates that the pump is operating beyond the user-entered pump characteristic curve (pump definition). This will happen when the pump definition is not defined all the way out to zero head. WaterCAD and WaterGEMS will use extrapolation on the pump curve, so that it extends all the way to zero head. The pump can operate past the user entered range if the system conditions warrant it. The pump curve that you see in the system head curve viewer is an extrapolated pump curve. The warning message may indicate that the real pump may not be able to operate correctly in this condition. Basically, the system conditions are such that the head the pump needs to add is less than the lowest head value in your pump curve. You can always check the operating point and extrapolated pump curve by right clicking the pump and selecting "Pump Curve". You should compare the operating point to the actual pump curve that you have defined under Components > Pump Definitions, and not to the system head curve window. Sometimes you may also get this message if you are using a multiple point pump curve with large gaps between flow values. If this is the situation you're facing, the issue can usually be resolved by adding one or two flow values with its corresponding head value to make the gaps between consecutive values smaller. See Also Pump cannot deliver flow or head user notification

Product(s): WaterGEMS Version(s): SELECTseries 2 and Later Area: Modeling Overview The purpose of this technote is to discuss the Pipe Renewal Planner feature available in Bentley WaterGEMS V8i Select Series 2 and higher. Additional information can be found in the WaterGEMS Help menu. For a free webinar demonstration Pipe Renewal Planner, use the link in the "See Also" section at the bottom of this article. Note : Pipe Renewal Planner is only available in WaterGEMS. If you have WaterCAD, you will need to upgrade to WaterGEMS to get this additional functionality. (similar to Darwin Calibrator, Darwin Designer, Darwin Scheduler, Skelebrator and SCADAConnect). More on WaterCAD vs. WaterGEMS here . Background It is often advantageous to know about vulnerable parts of a system so that potential problems can be fixed before they cause system disruptions. Pipe Renewal Planner provides the user with a method to calculate a weighted score for each pipe based on user-defined aspects of the model. Pipe Renewal Planner can give the user guidance to determine which pipes in the model may be most vulnerable and allow them to remedy issues that have caused the pipe to have a high score. Before using Pipe Renewal Planner Pipe Renewal Planner provides the user with a method to calculate a weighted score for each pipe based on user-defined aspects of the model. Pipe Renewal Planner can include any aspect that can be entered for a pipe or calculated for the pipe. These include capacity, projected pipe breaks, material, and depth of cover, among others. Scores determined by Pipe Renewal Planner are highly dependent on the specific system and on the availability of data. Before using Pipe Renewal Planner, the user needs to identify which aspects will be used in scoring pipes and which properties are going to be used as a basis for calculating the aspect scores. It may be necessary to define new properties in User Data Extensions and import values for properties from external data sources using ModelBuilder or copy/paste features. In order to import values, it is essential that there exist a common key field shared by the WaterCAD V8i model and the external data source. Calculation of raw scores for aspects such as capacity (fire flow) and criticality (deamnd shortfall) can be time consuming such that it may be advisable to have already computed these analyses before computing Pipe Renewal Planner. However, if any properties are changed that may affect scores, it is possible to recompute the scenario from within Pipe Renewal Planner. Also, keep in mind that doing the default Pipe Renewal Planner analysis will use fire flow (capacity), criticality, and segmentation, and pipe break results. It is recommended that this information is reviewed beforehand, as this technote will only touch on these in general terms. Please review the available technotes or Help items on these features for more information. Using Pipe Renewal Planner You can access Pipe Renewal Planner by selecting Analysis > Pipe Renewal Planner or picking the Pipe Renewal Planner icon from the toolbar. This opens the welcome dialog if no analyses have already been run. To start a new analysis, click the New icon in the upper left. A new pipe renewal planner label will appear in the list on the left, while the section to the right will be populated with default aspects: pipe break, criticality, and capacity (fire flow). Each aspect has a select number of properties associated with them. The Selection Set column allows you to choose either the entire network or a predefined selection set of elements for the aspect analysis. The Weight column is a way for you to decide how much emphasis will be placed on a certain aspect in Pipe Renewal Planner. The Scenario column defines which scenario the data for the individual aspect comes from. These different scenarios can be computed ahead of time, which will save some computational time for the Pipe Renewal Planner analysis itself. Computing the scenario ahead of time will also allow you to verify that the results for the aspects are reasonable. However, if you have not computed the scenario, you can put a checkmark in the Compute Scenario column and Pipe Renewal Planner will compute the scenario during the analysis. In addition to the default aspects, you can also add new aspects for the pipe renewal planner to account for. To do this, either click the New icon below the General tab or simply click in the empty cell beneath the default aspects. Then click in the cell and select the ellipsis button. This will open the Aspects manager. Select the New icon to create a selection. Then select which property you would like to be considered in the analysis. Whether you use the default aspects or create new ones, you will need to select the Representative Scenario for the analysis. This does not need to be the current scenario. The representative scenario will be used as the source of element properties and the location to save results except where another scenario is explicitly called out. Note: Two Pipe Renewal Planner configurations cannot share the same representative scenario. If a scenario is selected, it is not available as the representative scenario from the pulldown menu for other Pipe Renewal Planner configurations. Computing and Viewing Results The individual aspects will need to be set up before computing the Pipe Renewal Planner analysis. For information on how to run a fire flow , criticality , segmentation , and pipe break analyses , please review posted information in Help or in the technotes found in the Hydraulics and Hydrology Technotes page. Note: The raw score for capacity (fire flow) for a given pipe is equal to the difference between the "target" velocity (the "Pipe velocity greater than" field in the fire flow alternative) and the maximum velocity in that pipe (over all the fire flow events). In order for a pipe to be considered during this part of the calculation, it must either be adjacent to a fire flow node or be included in the "auxiliary output selection set" in the fire flow alternative. Once you have your aspects selected and applied, you will be ready to compute Pipe Renewal Planner. Click the green Compute icon in the Pipe Renewal Planner manager. Note: If you have not computed the scenarios associated with the aspects, you will be prompted to do so. You can either compute the scenarios individually or put a checkmark in the Compute Scenario column for the different aspects. If you click the Results tab, you will see the results of the analysis. The overall score for the pipe is found in the Pipe Score column. It is the weighted sum of the individual aspect scores. A higher value indicates a pipe with potential problems in need of repair, rehabilitation, replacement or some other remedial action. Scores are presented on a 0 to 100 scale unless the user has set up some different scaling. Other data included in the results tab include the scores and results for the individual aspects. The data can be sorted by right-clicking on a column header and choosing the Sort function. By choosing “Sort Descending,” the highest score will be at the top. You can also view the data graphically in the drawing pane by setting up color coding in the Element Symbology manager. Open this by clicking View > Element Symbology. Right-click on Pipe and select New > Color Coding. This will open a new manager. Choose “Pipe Score” from the Properties pulldown and select the range. You can initialize the color coding on the right side of the manager. More information on color coding can be found under Help. (Please visit the site to view this video) See Also Free Webinar demonstration Pipe Renewal Planner Understanding Automated Fire Flow Results Running a Criticality Analysis Original Author: Scot Kampa, Bentley Technical Support

Hello Linda, 1. i. You should include any normal demands in the model. The demand adjustment is used when the demand does not match up with what the model is using at that time step. ii. It doesn't matter if the demand data is at the junction or the customer meter. The program will calculate the demands at the junction either way. 2. i. Typically, the field data snapshot comes from a hydrant flow test. You measure the pressure results at some point while a nearby hydrant is flowing. The Demand Adjustment you see there will be this hydrant flow during the test, since it is an additional flow not already in the model. ii. If there is no demand at J9, that is fine. If that is the hydrant that is flowing during the flow test, you will still want to include this as an additional demand in the field data snapshot. 3. i-iii. What you include in the Observed Target will demand on the data you have available. For instance, if you have pressure values at a hydrant, you can include that. If you have pump flow, you can include that. Darwin Calibrator will make adjustments to the roughness values in your pipes to try to make it so that that model results match as closely as possible to the field data. What I often see are pressure results at points in the model while the hydrant flow test is being done, but pump flow is allowable as well. I would say that if you have the pump flow already, including pipe flow downstream of the pump may be redundant, since the flow from the pumps will already be included. iv-v. Tank levels and status of the pumps are included in the boundary overrides, if they are different from what you see from the model results. If the model reports that a given pump is off at the time of the flow test and the pump is off in the field, there is no reason to include it. vi. If you set the pump status in the boundary override and the status is Off, there is no need to set the pump flow to zero as well. 4. i. When exporting results, you would export the solution. This will include any changes to the roughness within roughness groups used for the solution. You can export as many solutions as you like, but you do not need to export all of them. ii. Demand export is only used if you are using Demand Groups (which is used less often than Roughness Groups). If you are not using Demand Groups, don't worry about exporting demands at all. 5. i. Importing as a child would be a good workflow, though it will be somewhat dependent on the model and what is being exported. ii. Typically, model calibration uses flow tests, and the hydrant will not typically flowing in a typical modeling case (like average day demands). You can try putting in the extra demand to see how the calibrated scenario looks but it is not necessary. The calibrated model would be calibrated for more than just the situation with the hydrant flowing. The results that are directly exported are the adjusted roughnesses from the Roughness Groups and, if you are using them, demands from the Demand Groups. Boundary overrides and demand adjustments used in the field data snapshot are not exported and should not really be needed. For your use, and use of other users on the forum, you can find more information on Darwin Calibrator in the WaterGEMS Help documentation of the following link: Using Darwin Calibrator . Regards, Scott

I have updated the video to show how to select slope units of mm/m, which gives the correct ratio, before changing the suffix to permille.

I can't find where anyone has posted this (of course I am new to this). I have created georeferenced TIFF files out of ArcGIS. However, when I open these TIFF files in WaterCAD they are totally black... no image. I am not using WaterGEMS in ArcGIS because I want to run in standalone WaterCAD. Please help so images actually show up in WaterCAD. Thanks

Product(s): WaterGEMS, WaterCAD, HAMMER, SewerGEMS, SewerCAD, StormCAD, CivilStorm Version(s): 08.11.XX.XX Area: Other Problem My GIS-ID naming system in my GIS has changed (for example to GlobalID) How can I update existing GIS-IDs in my model to these new IDs while maintaining the one-to-many and many-to-one relationships? Solution Here are the steps to update GIS-IDs in an existing model. Note : Please make sure you retain a backup copy of your original SQLite database before they make any edits. 1) First, prepare a file with the mapping between the old GIS-ID and the new GlobalID. The below steps assume a spreadsheet with a worksheet that has two columns: “Old_GIS-ID” and “GlobalID”. Also, be sure to close WaterGEMS and back up your model. 2) Download and install a SQLITE database access tool. These steps assume the use of DB Browser for SQLite. 3) Open the model database with the tool. This is the file with the extension of .SQLITE. 4) In the Database Structure, scroll down to the table “HMIModelingElementGISIDs” and open it 5) In the table, you will see a column for ElementID and GISID. Select both columns and press CTRL+C to copy to clipboard 6) Create a new worksheet in the spreadsheet from step 1 and paste in the data. Make sure you have column headers for ElementID and GISID. 7) Create a third column in this worksheet, called NewGIS-ID and set up a Vlookup function to find the corresponding GlobalID from the other worksheet. In the example below, the worksheet with the GIS-ID to GlobalID mapping is called “Mapping”. The range of A2:B7 is the range of this example case, select the entire range of the “mapping” worksheet. =VLOOKUP(B2,Mapping!$A$2:$B$7,2,FALSE) 8) Click the cell handle in the lower right corner and drag all the way to the bottom of the table to copy the function. 9) Highlight all the values in the “NEWGIS-ID” column (excluding the header) and press CTRL+C to copy. 10) Back in the SQLITE DB browser, click the first cell in the GIS-ID column and press CTRL+V to paste. Ensure that the data was correctly pasted and not offset. 11) Save changes (in “DB Browser for SQLite”, click the “Write Changes” button) and reopen the model in WaterGEMS. All the previous GIS-IDs should be updated to your new GlobalIDs. Spot checking is recommended, especially in cases where an element references multiple GIS-IDs or a GIS-ID is referenced in multiple elements. The example model and spreadsheet used in the above steps can be downloaded here: (Please visit the site to view this file)

I figured out why this was occurring. The version of TIF being created by ArcGIS simply didn't work for some reason. My guess is because it was a georeferenced image. Not sure. I created non-georeferenced images and they worked just fine. Thanks

Hello Irobinson, I'm glad to hear that you were able to resolve the issue. If you have a moment, I would be interested to know if you're using the latest version (CONNECT Edition, 10.00.00.50), and if the TIFF had a World file (is this what you mean by the file being georeferenced?). World files store geospatial information about an image file and can be utilized automatically starting with the CONNECT Edition, to display the background in the proper location (instead of having to manually enter the coordinates of the corners). See "World file support for background images" in the below article: What file types are supported for background layers in the standalone platform? A background appearing black is also a possible indication of video hardware driver problems, though I'm uncertain if that is the issue.. See related articles on that: Background image quality poor on some computers Updating video drivers and troubleshooting video hardware issues If the above does not help or does not apply, I'd be happy to take a look at the georeferenced version of the image file for testing in case there is a solution or some improvement to be made in the software: Sharing Hydraulic Model Files on the Haestad Forum

Hello Craig, I have tried all these solutions but failed, If you see the pic which i have attached with the very first comment. It will show that not only the Active topology but also User Extension, Physical Alternative, Demand Alternative etc has been changed due to set up of incoming scenario. You people are stressing about labels and structure, but my labels are different between elements of sub-model and Target. Its same for alternatives and scenario. I think there is something which we are missing to solve this issue..

Dears, It sounds the above is a feature in Civil stom but not in StormCAD. It is the case or is there a way to do it? thanks

Please provide a copy of the base model and submodel so we can provide a specific answer for your situation: Sharing Hydraulic Model Files on the Haestad Forum

Hello AHQ, Currently the local storm event option is not available in StormCAD (GVF-Rational solver). The primary reason is because StormCAD uses the Rational method which is typically used for relatively small areas, where you would not experience a notable different in rainfall across the site. See related: Different rainfall values in different areas in SewerGems? One workaround is to replace the catchment+catchbasin with the catchbasin only, with the runoff directly entered in the catchbasin properties (as a pair of "external Tc" and "External CA", or "Flow (additional carryover)" for example). If you're working on a relatively large site and need to have local storm events, consider if a unit hydrograph method might be more appropriate, which can be used with the Implicit and Explicit dynamic solvers in CivilStorm and SewerGEMS.

Hello Manfredi, Yes, since the PSV node element currently does not support automatic modulation during a transient event ( PRVs can ), the manual approach you mentioned would be best. Run a steady state with the pump off to determine the relative closure corresponding to the reaction to the change of the pump turning off. Decide how long it would take for the PSV to react, and built your operating rule accordingly (to shift from the starting relative closure to the new relative closure over a certain amount of time). See more here: Modeling existing valves as Throttle Control Valves in HAMMER However, one concern I have is the high point and what will happen when the pump if off. Without flow, there can be no headloss through the PSV, and hence it may either be fully closed or fully open, and part of the pipeline may drain. If the pipe drains in this case, this situation goes beyond the normal assumptions of HAMMER in that pipes are assumed to be pressurized and air only occupies a specific point in space. If you have an air valve at the high point, you will see an air pocket form upon pump shutdown. You will likely want to simulate what happens when the pump turns back on, to see the impact of expelling the large amount of air from the drained pipeline. This can be done with the variable speed/torque transient pump type. See more on that here: Modeling a pump startup and shutdown transient event in the same simulation See also other related articles: Modeling a case where an empty pipe is filling using Bentley HAMMER Assumptions and limitations of tracking air or vapor pockets in HAMMER

Applies To Product(s): WaterCAD, WaterGEMS, HAMMER, StormCAD, SewerCAD, SewerGEMS, CivilStorm, PondPack Version(s): V8 XM, V8i, CONNECT Edition Area: Modeling Original Author: Jesse Dringoli, Bentley Technical Support Group What is Waterobjects.NET and what can I do with it? Waterobjects.NET is the Application Programming Interface (API) used with Bentley's Hydraulics and Hydrology products, such as WaterCAD and WaterGEMS. It allows users with programming knowledge to extend the functionality of the product to suit their needs. Being .NET Framework based allows support for a number of different programming languages, such as VB, C#, C++, etc (more information on that can be found here and here .) Waterobjects.NET essentially provides a way to code routines/tools that take the data in a hydraulic model file, manipulate it in some way and either present output in a certain way and/or modify the model data. It is not intended as a way to modify the existing numerical engines or the user interface. Source code for those components are not provided. A basic training/overview course is also available on the LEARN.Bentley.com: How can I access it? To use Waterobjects.NET, you need: Programming knowledge The software installed (Bentley WaterGEMS, Bentley SewerGEMS, etc) A place to write your code: Visual Studio VSTO (for Microsoft Office) Visual Basic/C#/C++ Express Edition Note : you will also need to learn the structure/schema of the Haestad products/code which will require a time investment. The SDK will help with this. If you have the product already installed (SewerGEMS, WaterGEMS, etc) then you already have access to program with Waterobjects.NET. There is no separate installation file necessary. However, if you are a member of the Bentley Developer Network (BDN), then you can download the Software Development Kit (SDK) from our website. The Waterobjects.NET SDK includes Programming and Sample guide documents as well as several samples (mostly written in C#). This will help guide you through how to use Waterobjects, though in most cases a high level of programming experience will be necessary as a prerequisite. WaterObjects.NET SDK version Compatibility The below table outlines general compatibility between the Haestad product version and the sample projects included in the WaterObjects.NET SDK. In general, the first six digits of the version number of the latest available release corresponds with the current WaterGEMS release. For example 10.00.00 .01 corresponds with WaterGEMS 10.00.00 .50. If in doubt on compatibility, ask technical support via the forum. WaterObjects.NET version Compatibility 10.00.00.01 CONNECT Edition 08.11.06.01 SQLITE-based versions such as V8i SS6 08.11.05.01 and below MDB-based versions More information on the Bentley Developer Network (BDN): https://www.bentley.com/en/software-developers Some benefits of BDN : Access to the BDN Blog, which includes more examples of Waterobjects.NET projects (the below link will not work unless you are a member and are signed in): http://communities.bentley.com/communities/other_communities/bentley_developer_network/b/bentley_developer_network-blog Access to download the SDK via the Fulfillment Center : More Information and Frequently Asked Questions For a more in-depth FAQ on WaterObjects.NET, see the below FAQ PDF from 2012. Note that you must be signed in first or the link will not work. Do I really need Waterobjects.NET for the Tool I Have in Mind? Successful use of Waterobjects.NET often requires advanced programming experience and the willingness to take the time to learn the API. If used properly, it can be a powerful tool in extending the product functionality. However, due to the time investment that would typically be required, when considering if Waterobjects.NET is right for you, it's important to ensure that the functionality you desire isn't already available in the product itself. Bentley's Hydraulics and Hydrology products are robust, feature rich and flexible, out of the box. Below are some examples of using product functionality to do things that you might be considering Waterobjects.NET for: Customizing a report of model input and/or output: Flextables have the ability to export to .CSV format, which can be manipulated easily in external software such as Excel. So for example, you could create a new Flextable with the desired fields, export to CSV, then import the CSV file in Excel, along with custom formatting and functions that can manipulate the values. Flextables also have the ability to export to XML format, which allows you to apply a custom style sheet. In later releases such as the CONNECT Edition, you can export all elements to Excel at once via File > Export > Export to Excel In later releases you can also create custom reports including element information, results, graphs, with customizable header, footer, etc You can use Modelbuilder to "Sync out" (export) model input and output fields to a number of different formats. For example you could export to a database, which could be used in a external application to present results in a certain way. You could also configure a spreadsheet in Excel for example, with the formatting and functions you need, then export model results to that spreadsheet. Performing a calculation based on model data/results If you need to make a calculation that is a function of one or more input or result fields in the model, you can take advantage of the Formula-derived User Data Extension (UDX) feature. This allows you to create a custom field whose value is based on a formula. This feature is quite flexible and the resulting data can be used like any other model input/output field, in that you can color code on it, annotate, etc. Note that formula UDX operates on information at a given timestep, so it currently cannot be used to aggregate data for multiple timesteps (such as finding the sum, min, max for a particular field across all timesteps). More information on Formula UDX can be found here: Creating Formula Based User Data Extensions Advanced model querying and manipulation Let's say for example you want to locate all junctions that are at a dead-end, then convert them all to hydrants. This can be done in the program already, by first using the "dead end junctions" predefined query (accessible from View > Queries or View > Network Navigator) to select the dead end nodes, then select Tools > Batch Morph, click the "selection" option, choose Hydrant as the new node type, then click OK. There are many other useful queries available in Network Navigator . Specifics on using WaterObjects.NET for SewerCAD See article: Using Waterobjects.NET for SewerCAD What if I need help with Waterobjects.NET? In general, support for Waterobjects.NET is provided by way of the community forum (including Bentley developers and other users). For general information on Waterobjects.NET and the Bentley Developer Network, post your question to the BDN forum (available to BDN members - must be signed in and a member of the community or the link will not work) For other, technical questions such as how to program something or problems with your tool, use the Haestad | Hydraulics and Hydrology Community First, use the Search bar to search for existing discussions or articles on the topic. If you cannot find the answer, start a new Thread on the Haestad | Hydraulics and Hydrology Forum For consulting services on developing a Waterobjects.NET tool, contact your Bentley Account Manager (sales representative). See Also Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs

Hello Ivana, I have moved your post to the correct forum: Haestad | Hydraulics and Hydrology Forum. Regarding the negative pressures - if they occur for a tank, check the physical elevation compared to the initial elevation. If this is occurring at specific times during an EPS, graph the elevation (HGL) of the tank. See related article in our wiki: Troubleshooting negative pressures at pumps, junctions, & other node elements Regarding the system disconnection message - if this is occurring due to a pipe connected to a tank, it is an indication that the tank's built-in altitude valve is closing that pipe. Graph the "percent full" attribute for the tank and see if it becomes full or empty at any point during the EPS. Controls should be put in place to prevent this from happening. If there are element disconnected from a water source (tank or reservoir) due to this, it will result in the notification in question and the results will not be reliable as an HGL cannot be accurately calculated without a connected boundary condition. See related articles in our wiki: System Disconnected or Junction Disconnected user notification messages What happens when a tank becomes empty or full? If this does not help, please provide a copy of the model files (.WTG and .WTG.SQLITE, zipped): Sharing Hydraulic Model Files on the Haestad Forum