Bridging Decades: Reading InfoSewer Report RPT Output for ICM InfoWorks in 2030+
Helping across the full stormwater spectrum: SWMM (50+ yrs), InfoSWMM/ESRI (20 yrs), InfoWorks ICM (15 yrs), & Autodesk AEC Collection (5 yrs) Grandpa (10 yrs)
May 26, 2025
As we move closer to 2030 or sooner, some engineers face a unique challenge: accessing and interpreting InfoSewer output from projects dating back to 2001–2025. With ESRI’s ArcMap retired and Autodesk sunsetting InfoSewer, running the software is no longer an option. Fortunately, there’s a solution. By leveraging Ruby code, you can extract critical data from archived InfoSewer OUT folder files, specifically the steady-state and EPS (extended period simulation) report files. This workaround, inspired by one of our Stellar Solution Engineers, [Tim Medearis], enables you to summarize loads and flows and generate CSV sections for use as observed-predicted data in ICM InfoWorks. Here’s how to bridge the past with the future and keep your historical sewer models useful for the sake of model result comparisons.
Historical sewer data from 2005–2025 isn’t just a relic; it’s vital for compliance, infrastructure upgrades, and validating new models in ICM InfoWorks. Whether you’re assessing past performance for regulatory audits or planning retrofits, these outputs provide a baseline. However, with InfoSewer obsolete, accessing this data is a hurdle. While ICM Ruby and ODIC code can read IEDB folder DBF files, they don’t reveal InfoSewer’s original answers. This Ruby script fills that gap, ensuring engineers can leverage decades-old insights without recreating models from scratch. As mentioned, this will be impossible in 2030 or sooner depending on ESRI and its sunsetting of ArcMap.
The Ruby script targets InfoSewer’s OUT folder, specifically the steady-state (.rpt) and EPS (.eps) report files. It parses these files to extract key metrics: node loads, link flows, and system performance data. The script then makes a structured CSV file, formatted for direct import into ICM InfoWorks as observed-predicted data. Prerequisites are minimal: you need the archived OUT folder and a basic ICM UI Ruby environment. Unlike ICM’s ODIC native tools, which focus on DBF and CSV files, this script unlocks the exact results InfoSewer produced, preserving the integrity of historical simulations.
Ruby InfoSewer RPT Prompt
Ruby InfoSewer RPT Prompt
Ruby Puts Statement Output for Nodes and LInks Stats from the InfoSewer Simulation Run
Ruby Puts Statement Output for Nodes and Links Stats from the InfoSewer Simulation Run
Ruby Puts Statement Output for CSV for Observed Predicted Graphs in ICM InfoWorks
Ruby Puts Statement Output for CSV for Observed Predicted Graphs in ICM InfoWorks
Where is the code? 01 InfoWorks ICM/01 Ruby/02 SWMM/0014 - InfoSewer to ICM Comparison Tools on the Innovyze GitHub
01 InfoWorks ICM/01 Ruby/02 SWMM/0014 - InfoSewer to ICM Comparison Tools
ui.script Read InfoSewer Steady State Report File,rb and ui.script Read InfoSewer Steady State Report File.md