Showing posts with label InfoSWMM. Show all posts
Showing posts with label InfoSWMM. Show all posts

Saturday, January 13, 2024

InfoSWMM, adding RDII (Rainfall-Derived Infiltration and Inflow) to nodes - workflow

 Using  InfoSWMM, adding RDII (Rainfall-Derived Infiltration and Inflow) to nodes is a straightforward process, enhanced with graphical tools for user-friendliness. 🌧️🛠️

  1. Select a Junction: Click on the junction node where you want to assign RDII.
  2. Access Inflow Settings: Use the 'hammer' tool in the InfoSWMM browser, symbolizing adjustments or modifications.
  3. Navigate to RDII: Select the 'Inflow' option and then click the RDII tab.
  4. Specify Parameters: Define the Unit Hydrograph (UH) group, which dictates the response pattern to rainfall, and set the sewershed area contributing to this specific inflow.

This approach blends intuitive UI elements with the robust hydraulic modeling capabilities of SWMM5 and InfoSWMM, making it easier to simulate the impacts of rainfall on sewer systems. 💻🌦️

To handle Rainfall-Derived Infiltration and Inflow (RDII) assignments in bulk within SWMM5 and InfoSWMM, you can utilize the Node RDII table:

  1. Open Node RDII Table: Access the dedicated table for RDII assignments in the software.
  2. Enter New Rows: In the table, add rows for each node you wish to assign RDII.
  3. Specify Details: For each row, enter the node ID, select the appropriate Unit Hydrograph (UH) Group, and input the sewershed area.

This method is highly efficient for managing multiple nodes simultaneously, streamlining the process of RDII setup in your hydraulic model. 📈💧🖥️

Wednesday, November 8, 2023

Full Product Plan (FPP) for Integrating models from XPSWMM SWMM5, InfoSWMM, and InfoSewer into ICM InfoWorks and ICM SWMM

Integrating models from XPSWMM SWMM5, InfoSWMM, and InfoSewer into ICM InfoWorks, especially considering ICM's Ruby scripting capabilities, involves a blend of technical acumen and attention to detail. Here’s a consolidated guide with added emojis for a touch of clarity and fun:

1. Data Compatibility and Conversion 🔄:

  • Data Structures 🔩: Ensure compatibility of network topology and hydraulic elements.
  • Units of Measurement 📏: Verify consistent unit conversions throughout the models.

2. Hydraulic and Hydrologic Model Features 🌊:

  • Hydraulic Modeling Features 💧: Translate features like pumps and weirs accurately.
  • Hydrologic Processes 🌧️: Ensure hydrologic processes are represented correctly.

3. Model Parameters and Settings ⚙️:

  • Parameter Equivalents 🔄: Find equivalents for all parameters in the ICM environment.
  • Operational Settings ⏲️: Migrate control rules and settings meticulously.

4. Calibration and Validation 🎯:

  • Calibration Data 🔍: Re-calibrate and validate the imported model to match original results.
  • Validation Criteria ✅: Set clear criteria for performance comparison.

5. Software-Specific Features 🧩:

  • Custom Functions 🛠️: Convert and test any custom functions or scripts.
  • Extensions and Plugins 📲: Check for compatibility or alternatives in ICM.

6. Results and Reporting 📊:

  • Output Resolution 📈: Match time steps and durations for accurate comparisons.
  • Graphical and Tabular Outputs 📉: Ensure outputs are consistent and informative.

7. User Interface and Experience 👥:

  • Workflow Adjustments 🔄: Adapt workflows to fit ICM's interface.
  • Training 🏫: Train users to proficiently navigate the new system.

8. Quality Assurance 🛡️:

  • Automated Testing 🤖: Use tools to compare results from both systems.
  • Peer Review 👀: Have experts review the conversion process.

9. Documentation 📝:

  • Record Keeping 🗂️: Document every step and decision in the conversion process.
  • Model History 📚: Maintain a comprehensive history of the original model's development and calibration.

10. Technical Support 🆘:

  • Vendor Communication ☎️: Keep in touch with software vendors for assistance.
  • Community Forums 💬: Utilize forums for additional insights and support.

Integration with Ruby Scripting 💎:

  • Script Conversion 🔄: Translate existing scripts into Ruby for ICM.
  • Ruby Scripting Capabilities 🤹: Exploit Ruby to enhance model functions and automation.
  • Script Testing 🔬: Ensure all Ruby scripts operate flawlessly within ICM.

Custom Feature Development with Ruby 🏗️:

  • Feature Extension 📐: Develop new scripts to match original software capabilities.
  • Custom Analyses 🧬: Craft Ruby scripts for analyses that require adaptation to ICM's modeling paradigm.

Combining these technical considerations with the powerful scripting language Ruby 🚀, your imported models into ICM InfoWorks can not only match the original software's capabilities but also potentially exceed them, paving the way for more efficient and insightful water management in Boulder. 🏔️🏙️

Thursday, March 16, 2023

InfoSWMM to InfoSewer - Caveats with Emojis

🚧 The primary challenge in transitioning from 🌧️ InfoSWMM to 🚰 InfoSewer lies in the differences between the two software's requirements and restrictions. InfoSewer, unlike InfoSWMM, has a more ⛓️ rigid set of rules and constraints, which can make the conversion process 🔄 complex and ⏳ time-consuming. Some of these rules and constraints are as follows:

🌲 Dendritic network: InfoSewer requires a dendritic network structure, meaning that the network must be a tree-like structure without loops or closed circuits. This constraint ensures a simpler flow path and a more stable 🌊 hydraulic simulation.

💪 Strict force main and pump rules: InfoSewer enforces specific rules for force mains and pumps, such as the requirement to connect force mains directly to pump stations and the need for wet wells. These rules help maintain the accuracy and consistency of simulations in pressurized systems.

⛰️ Adverse slope issues: InfoSewer is sensitive to pipe slopes and may flag adverse slopes that could lead to hydraulic issues or incorrect flow directions. Careful attention must be paid to the elevation data to avoid these problems.

🔄 Loop issues: As mentioned earlier, InfoSewer requires a dendritic network without loops. Loops in the network must be removed or modified to adhere to this constraint, which can be a challenging and manual process.

🔗 Disconnected node issues: InfoSewer does not allow orphan or disconnected nodes, which means all nodes must be connected to the main network. These disconnected elements must be identified and either connected or removed from the model.

🌊 Flow splits: InfoSewer requires proper flow splits to ensure accurate flow distribution among downstream pipes. This may necessitate the manual adjustment of flow splits, making the conversion process more time-consuming.

While automating the entire conversion process from 🌧️ InfoSWMM to 🚰 InfoSewer is difficult due to these rules and constraints, the use of 📑 CSV and 🌍 shapefile import and export tools can streamline certain aspects of the process. These tools help in transferring data between different formats and can make the conversion process more manageable. However, a thorough review and adjustment of the model's elements are still required to ensure that the resulting InfoSewer model adheres to its specific rules and produces accurate simulations. 🎯


The primary challenge in transitioning from InfoSWMM to InfoSewer lies in the differences between the two software's requirements and restrictions. InfoSewer, unlike InfoSWMM, has a more rigid set of rules and constraints, which can make the conversion process complex and time-consuming. Some of these rules and constraints are as follows:

  1. Dendritic network: InfoSewer requires a dendritic network structure, meaning that the network must be a tree-like structure without loops or closed circuits. This constraint ensures a simpler flow path and a more stable hydraulic simulation.

  2. Strict force main and pump rules: InfoSewer enforces specific rules for force mains and pumps, such as the requirement to connect force mains directly to pump stations and the need for wet wells. These rules help maintain the accuracy and consistency of simulations in pressurized systems.

  3. Adverse slope issues: InfoSewer is sensitive to pipe slopes and may flag adverse slopes that could lead to hydraulic issues or incorrect flow directions. Careful attention must be paid to the elevation data to avoid these problems.

  4. Loop issues: As mentioned earlier, InfoSewer requires a dendritic network without loops. Loops in the network must be removed or modified to adhere to this constraint, which can be a challenging and manual process.

  5. Disconnected node issues: InfoSewer does not allow orphan or disconnected nodes, which means all nodes must be connected to the main network. These disconnected elements must be identified and either connected or removed from the model.

  6. Flow splits: InfoSewer requires proper flow splits to ensure accurate flow distribution among downstream pipes. This may necessitate the manual adjustment of flow splits, making the conversion process more time-consuming.

While automating the entire conversion process from InfoSWMM to InfoSewer is difficult due to these rules and constraints, the use of CSV and shapefile import and export tools can streamline certain aspects of the process. These tools help in transferring data between different formats and can make the conversion process more manageable. However, a thorough review and adjustment of the model's elements are still required to ensure that the resulting InfoSewer model adheres to its specific rules and produces accurate simulations.

Saturday, November 5, 2022

Importing InfoSWMM and SWMM5 to ICM SWMM Networks

 InfoSWMM_ICM_SWMM_InfoWorks in three minutes youtu.be/e9zq3UHFVWM via

Force Main hydraulic theory and how force mains are simulated in ICM, #SWMM5, #ICM_SWMM and XPSWMM - Emoji View

🚀 Force Main Hydraulics: A Dive into Theory and Simulation 🌊

Mel Meng's recent post is nothing short of enlightening! 🧠✨ Merging the intricacies of Force Main hydraulic theory with real-world simulation in tools like ICM, #SWMM5, #ICM_SWMM, and XPSWMM, Mel offers a comprehensive look at the subject. What stands out is his knack for blending theory with User Experience (UX), the magic of #Python 🐍, and the open-source wonders of #github 🖥️.

🔗 Dive into his insights here: LinkedIn Post

Want a more visual treat? 🎥 Check out this illustrative YouTube video that expands on his blog and code: Watch Now

Stay curious and keep exploring! 🌟🔍📚

Wednesday, September 23, 2020

InfoSWMM Version Numbers and the version of Arc Map they use and which EPA SWMM5 Engine is used for Each InfoSWMM Version

 InfoSWMM Version Numbers 

InfoSWMM Version 14.7  Update 2 for Arc Map 10 to 10.7 and Windows 7/8/8.1/10 - EPA SWMM 5.1.013  11/16/2019  

InfoSWMM Version 14.7  Update 1 for Arc Map 10 to 10.7 and Windows 7/8/8.1/10 - EPA SWMM 5.1.013  04/12/2019    

InfoSWMM Version 14.7  for Arc Map 10 to 10.6 and Windows 7/8/8.1/10 - EPA SWMM 5.1.013  12/30/2018   

InfoSWMM Version 14.6 Update 2 for Arc Map 10.6 and Windows 7/8/8.1/10 - EPA SWMM 5.1.012  8/30/2018   

InfoSWMM Version 14.6 Update 1 for Arc Map 10.6 and Windows 7/8/8.1/10 - EPA SWMM 5.1.012  6/30/2018   

InfoSWMM Version 14.6 for Arc Map 10.6 and Windows 7/8/8.1/10 - EPA SWMM 5.1.012  11/30/2017 

InfoSWMM Version 14.5 Update 10 for Arc Map 10.5 and Windows 7/8/8.1/10 - EPA SWMM 5.1.012  10/7/2017

InfoSWMM Version 14.5 Update 9 for Arc Map 10.5 and Windows 7/8/8.1/10 - EPA SWMM 5.1.012  5/15/2017

InfoSWMM Version 14.5 Update 8 for Arc Map 10.5 and Windows 7/8/8.1/10 - EPA SWMM 5.1.012  4/17/2017

InfoSWMM Version 14.5 Update 7 for Arc Map 10.5 and Windows 7/8/8.1/10 - EPA SWMM 5.1.011  3/29/2017 SH

InfoSWMM Version 14.5 Update 6 for Arc Map 10.5 and Windows 7/8/8.1/10 - EPA SWMM 5.1.011  3/9/2017 SH

InfoSWMM Version 14.5 Update 5 for Arc Map 10.5 and Windows 7/8/8.1/10 - EPA SWMM 5.1.011  12/27/2016 SH

InfoSWMM Version 14.5 Update 4 for Arc Map 10.4 and Windows 7/8/8.1/10  - EPA SWMM 5.1.010  10/07/2016  MC1  SH

InfoSWMM Version 14.5 Update 3 for Arc Map 10.4 and Windows 7/8/8.1/10  - EPA SWMM 5.1.010  9/14/2016 MC1 SH

InfoSWMM Version 14.5 Update 2 for Arc Map 10.4 and Windows 7/8/8.1/10 - EPA SWMM 5.1.010  08/12/2016 MC1

InfoSWMM Version 14.5 Update 1 for Arc Map 10.4 and Windows 7/8/8.1/10  - EPA SWMM 5.1.010  08/05/2016 MC1

InfoSWMM Version 14.5  for Arc Map 10.4 and Windows 7/8/8.1/10   - EPA SWMM 5.1.010  06/07/2016 MC1

InfoSWMM Version 14 SP1 Update 8/9 for Arc Map 10.4  and Windows 7/8/8.1/10 - EPA SWMM 5.1.010  04/25/2016 MC1

InfoSWMM Version 14 SP1 Update 7 for Arc Map 10.4  and Windows 7/8/8.1/10 - EPA SWMM 5.1.010  03/25/2016 MC1

InfoSWMM Version 14 SP1 Update 6 for Arc Map 10.3 and Windows 7/8/8.1/10  - EPA SWMM 5.1.010   03/18/2016 MC1

InfoSWMM Version 14 SP1 for Arc Map 10.3  and Windows 7/8/8.1/10 - EPA SWMM 5.1.010   11/25/2015 MC1

InfoSWMM Version 14 Update 1 for Arc Map 10.3 and Windows 7/8/8.1/10  - EPA SWMM 5.1.009    9/25/2015 MC1

InfoSWMM Version 14 for Arc Map 10.3 and Windows 7/8/8.1/10 - EPA SWMM 5.1.009    8/11/2015

InfoSWMM Version 13 SP1 for Arc Map 10.3  - EPA SWMM 5.1.007     1/10/2015

InfoSWMM Version 13 Update 5 for Arc Map 10.2 - EPA SWMM 5.1.007     10/9/2014

InfoSWMM Version 13 for Arc GIS 10.2- EPA SWMM 5.1.006     09/22/2014

InfoSWMM Version 12 SP1  Update 5 - EPA SWMM 5.0.022     06/12/2014

InfoSWMM Version 12 SP1 for Arc GIS 10.1  - EPA SWMM 5.0.022     10/25/2013

InfoSWMM Version 12    - EPA SWMM 5.0.022      04/21/2011

InfoSWMM Version 11    - EPA SWMM 5.0.022      04/21/2011

InfoSWMM Version 10    - EPA SWMM 5.0.022      10/13/2010

InfoSWMM Version 9.0 for Arc GIS 10.0  - EPA SWMM 5.0.019      08/20/2010

InfoSWMM Version 8.5    - EPA SWMM 5.0.018     11/19/2009

InfoSWMM Version 8 .0 for Arc GIS 9.3-  EPA SWMM 5.0.016      10/19/2009

InfoSWMM Version 7 .0 -  EPA SWMM 5.0.013      03/10/2008

InfoSWMM Version 6 .0 -  EPA SWMM 5.0.010    05/04/2007

InfoSWMM Version 5 .0 -  EPA SWMM 5.0.006      10/10/2005

 InfoSWMM Version 4 .0 -  EPA SWMM 5.0.005      08/17/2005

 InfoSWMM Version 3 .0 -  EPA SWMM 5.0.004      11/30/2004

 InfoSWMM Version 2 .0 -  EPA SWMM 5.0.004      11/30/2004

 InfoSWMM Version 1 .0 -  EPA SWMM 5.0.001      10/26/2004

GitHub code and Markdown (MD) files Leveraging

 To better achieve your goal of leveraging your GitHub code and Markdown (MD) files for your WordPress blog or LinkedIn articles, consider t...