Unlock The Secrets Of ATI Swift River Simulations 2.0 Client Report Sheet: What Your Team Is Missing

Ever tried to make sense of a flood model that looks more like a sci‑fi dashboard than a simple spreadsheet?
That’s the feeling many engineers get when they first open the ATI Swift River Simulations 2.0 Client Report Sheet.
It’s not just a table of numbers – it’s the bridge between a massive hydraulic engine and the people who actually need the results: planners, insurers, and the odd curious citizen Not complicated — just consistent..

In practice the report sheet is the final handshake. Now, the model has crunched terrain, rainfall, and river‑bed data for hours; now you have to hand over something readable, actionable, and, above all, trustworthy. If you’ve ever stared at a wall of green‑highlighted cells and wondered, “What on earth does this mean for my project?” you’re in good company. Let’s pull apart the sheet, see why it matters, and walk through the bits that usually trip people up The details matter here..

What Is the ATI Swift River Simulations 2.0 Client Report Sheet

Think of the report sheet as the “executive summary” for a hydraulic simulation. ATI (Advanced Terrain Integration) built Swift River 2.0 as a cloud‑based engine that runs 2‑D and 1‑D flood simulations at a fraction of the time older desktop tools needed. After the heavy lifting, the client report sheet formats the output into a clean Excel (or CSV) file that anyone can open without a GIS license Simple, but easy to overlook..

And yeah — that's actually more nuanced than it sounds.

The core pieces

• Scenario Summary – a quick‑look table that tells you which flood event you’re looking at (e.g., 100‑year storm, design storm, or a user‑defined hydrograph).
• Hydrograph Table – time‑step discharges at key cross‑sections, usually in cubic metres per second.
• Inundation Metrics – peak water depth, duration above certain thresholds, and the “volume of water” that passed a given point.
• Risk Indices – a set of derived values like the Flood‑Risk Rating (FRR) and Expected Annual Damage (EAD).
• Map References – cell IDs that point back to the GIS raster so you can overlay the numbers on a flood map if you need to.

All of that lives on a single worksheet (or a few tabs, depending on your license). The data is already cleaned up: duplicate rows stripped, units standardized, and any “‑9999” error codes replaced with blanks Less friction, more output..

Why It Matters / Why People Care

You could argue that any model output is useful, but the reality is that decision‑makers rarely have the time—or the patience—to dig through raw simulation logs. The client report sheet does three things that matter a lot:

1. Speed up communication – a city planner can glance at the “Peak Depth @ Bridge A” row and immediately know whether a proposed road elevation is safe.
2. Provide a legal audit trail – insurers love the risk indices because they can be cited in policy language. The sheet’s timestamps and scenario IDs make it easy to prove “this was the model we ran on March 12.”
3. Enable cross‑disciplinary work – environmental scientists can pull the inundation duration column into a habitat‑impact model without learning any hydrology jargon.

When the sheet is clear, you avoid the classic “lost in translation” problem where the engineer says “the model shows a 2.3 m flood,” but the stakeholder interprets that as “the whole town will be underwater.” The short version is: a well‑crafted report sheet keeps everyone on the same page and saves weeks of back‑and‑forth Easy to understand, harder to ignore..

How It Works (or How to Do It)

Below is the step‑by‑step flow most teams follow, from launching Swift River to handing the final sheet to a client. Feel free to cherry‑pick the parts that match your workflow It's one of those things that adds up..

1. Set Up Your Simulation in Swift River 2.0

• Upload terrain – a DEM (Digital Elevation Model) in GeoTIFF or ASCII format.
• Define boundary conditions – choose a rainfall hyetograph or a upstream hydrograph.
• Select hydraulic parameters – roughness coefficients (Manning’s n), bridge openings, culvert sizes.

Once the inputs are in place, hit “Run.” The cloud engine spins up, runs the solver, and writes the results to an internal database.

2. Generate the Client Report Sheet

• manage to “Reports” in the web UI.
• Choose “Client Report” from the dropdown, then select the scenario you just ran.
• Click “Export” – you’ll get an .xlsx file (or a .csv if you prefer).

Behind the scenes, Swift River pulls the simulation’s time‑series data and runs a set of built‑in macros that calculate the risk indices. Those macros are part of the “Report Engine” and can be customized if you have a developer license.

3. Open and Verify the Sheet

Open the file in Excel (or LibreOffice). The first tab is usually “Summary.” Check these items right away:

• Scenario ID matches the one you ran.
• Run Date/Time is correct – you don’t want to send last month’s numbers by mistake.
• No #VALUE! or #DIV/0! errors. If you see them, the underlying simulation probably hit a convergence issue.

4. Dive Into the Hydrograph Table

The “Hydrographs” tab lists every monitoring point you defined. Each row contains:

To get a quick visual, select the columns and insert a line chart. You’ll instantly see where the peak occurs and how long the recession tail lasts Nothing fancy..

5. Interpret Inundation Metrics

The “Inundation” tab aggregates depth and duration per asset:

• Peak Depth – the highest water level above the ground surface.
• Time‑above‑Threshold – how long water stayed above, say, 0.5 m, which is often the “minor flood” level.
• Cumulative Volume – total water that passed the point, useful for sediment transport calculations.

If you’re working with a bridge, the “Scour Risk” column (a derived metric) tells you whether the predicted flow could undermine foundations.

6. Use the Risk Indices

Two columns most clients ask about are FRR (Flood‑Risk Rating) and EAD (Expected Annual Damage).

• FRR is a score from 1–5 based on depth, velocity, and exposure. A 5 means catastrophic.
• EAD multiplies the probability of the event (e.g., 0.01 for a 100‑year storm) by the estimated damage cost.

These numbers are ready to paste into a cost‑benefit analysis or a grant application That's the part that actually makes a difference..

7. Link Back to GIS (Optional)

The “Map Ref” column gives you the raster cell ID for each data point. Load the original DEM into QGIS, add a point layer with those IDs, and you’ll have a visual overlay of the exact locations the sheet references. It’s a neat trick when you need to show a city council exactly where the “Peak Depth @ 3.2 m” measurement was taken Worth keeping that in mind. And it works..

Common Mistakes / What Most People Get Wrong

Even though the sheet is meant to be user‑friendly, a few pitfalls keep showing up.

Ignoring Unit Mismatches

Swift River stores everything in SI units, but some legacy projects still use feet and cfs. Which means if you export the sheet and then hand it to a colleague who expects imperial units, you’ll get a nasty surprise. The fix? Add a quick conversion row at the top of each numeric column, or better yet, set your project’s unit preference in the Swift River UI before you run the model.

Over‑relying on the Default Risk Indices

The built‑in FRR and EAD are great for a first pass, but they assume a generic asset value (e., a residential building worth $150k). g.If you’re dealing with a historic bridge or a power substation, those default values can under‑ or over‑estimate risk. The sheet includes a “Custom Asset Value” column; fill it in before you run the risk calculations, or run a separate Excel macro to adjust the EAD after export.

Forgetting to Clean Up Duplicate Stations

When you copy‑paste station lists from different projects, you sometimes end up with duplicate IDs. Worth adding: a confusing hydrograph that looks like the river split in two. Which means the result? Swift River will still run, but the report sheet will show two rows for the same location, each with half the time steps. Always run the “Remove Duplicates” function in Excel (Data → Remove Duplicates) before you start analyzing.

Skipping the Convergence Check

A simulation can finish with a “completed” flag even if the solver didn’t fully converge. The sheet will still export, but the numbers could be off by 20‑30 %. Look for the “Convergence Flag” in the “Summary” tab – if it’s yellow, re‑run with tighter tolerances or a finer mesh.

Assuming the Sheet Is the Final Deliverable

Clients love the clean numbers, but they also want a visual of the flood extent. The report sheet alone won’t show you the inundation map. In practice, pair the sheet with a quick raster‑overlay in a GIS or use ATI’s built‑in map viewer to generate a PNG that you attach to the email. It’s the difference between “here’s the data” and “here’s what it looks like on the ground Most people skip this — try not to..

Practical Tips / What Actually Works

Here are the handful of things that consistently save time and keep the report sheet credible Worth keeping that in mind..

1. Create a template workbook – copy the exported sheet once, strip out any scenario‑specific rows, and save it as “ClientReportTemplate.xlsx.” For each new run, just paste the fresh data into the template. Your formatting, conditional colors, and comment boxes stay intact No workaround needed..

2. Use conditional formatting for red flags – set a rule that highlights any Peak Depth > 2 m in bright orange, and any FRR = 5 in red. The visual cue makes it impossible for a reviewer to miss a critical asset.

3. Add a “Notes” column – right next to each station, jot down site‑specific observations (e.g., “upstream levee breached during 2019 flood”). Those little context clues become priceless when the report is revisited months later.

4. Automate the conversion to PDF – a simple VBA macro can take the “Summary” tab, export it as a PDF, and email it to a pre‑set list. No more manual “File → Save As” steps.

5. Version‑control the sheet – store each export in a folder named by date and scenario (e.g., 2024-09-15_100yr_UpperRiver). When a client asks for “the latest numbers,” you won’t have to hunt through a sea of files Worth keeping that in mind. Which is the point..

6. Cross‑check with a simple Excel chart – before you send anything, plot the hydrograph for the most critical station. If the curve looks jagged or has sudden spikes that don’t match the rainfall input, you’ve likely got a data‑import glitch Most people skip this — try not to..

7. Run a “sanity‑check” macro – a short piece of VBA that flags any discharge > 10 times the median value, or any depth < 0 m. Those are usually errors that slipped through the model’s own filters Worth knowing..

FAQ

Q: Can I customize the risk indices in the client report sheet?
A: Yes. If you have a developer license, you can edit the underlying JSON template that defines FRR and EAD calculations. For most users, adding a “Custom Asset Value” column and then using a simple Excel formula to recalculate EAD works fine.

Q: Does the sheet support multiple scenarios in one file?
A: The default export gives you one scenario per workbook. On the flip side, you can use the “Batch Export” tool in the Swift River UI to bundle several runs into a single Excel file with separate tabs for each scenario.

Q: My hydrograph shows negative discharges—what’s happening?
A: Negative values usually indicate a reversal of flow direction at that station, which can happen downstream of a weir. Verify that the station is placed correctly; if it’s meant to be upstream, move it or adjust the boundary condition Simple as that..

Q: How do I convert the sheet to a format that non‑Excel users can read?
A: Export the workbook as CSV (File → Save As → CSV). Most data‑analysis tools, including R and Python pandas, can ingest CSV without trouble. Just remember to keep the “Map Ref” column if you still need GIS linkage.

Q: Is there a way to automate the entire workflow from model run to client email?
A: Yes. Swift River’s API lets you script the run, export, and download steps. Pair that with a simple Python script that attaches the PDF version of the “Summary” tab and sends it via SMTP. Many firms have built a one‑click “Run‑Report‑Send” button in their internal portal.

Wrapping it up

The ATI Swift River Simulations 2.Practically speaking, 0 Client Report Sheet isn’t just a dump of numbers—it’s the conversation starter that turns a complex hydraulic model into a decision‑ready document. By understanding the sheet’s structure, watching out for the common slip‑ups, and applying a few practical tricks, you can deliver flood‑risk information that’s clear, credible, and, most importantly, useful to the people who need it.

The official docs gloss over this. That's a mistake The details matter here..

So next time you open that green‑highlighted Excel file, take a breath, run through the checklist above, and let the data do the talking. Happy modeling!

8. apply Conditional Formatting for Instant Insight

Even if you’re comfortable reading raw numbers, a well‑crafted conditional‑formatting layer can make red‑flags pop out without you having to scan each row. Here’s a quick set‑up that works for the default “Asset Impact” table:

To apply the rule, select the column, go to Home → Conditional Formatting → New Rule, pick “Format only cells that contain,” and paste the appropriate formula. The visual cue system works especially well when you hand the workbook to a client who may not be comfortable interpreting the raw figures Surprisingly effective..

9. Create a “What‑If” Dashboard with Data Validation

Clients love to see “what happens if we change the asset value?” or “what if the return period is 100 years instead of 50?” You can turn the static report into an interactive dashboard with just a few extra rows:

1. Insert two input cells at the top of the sheet (e.g., B2 for “Asset Value Multiplier” and B3 for “Design Return Period”).
2. Add data‑validation dropdowns so the user can pick from a list of common multipliers (0.5, 1, 2, 5) and return periods (10, 20, 50, 100).
3. Reference those cells in the EAD formula:

   =IFERROR([@Depth]*$B$2*[@AssetValue]/[ReturnPeriodFactor],0)
   

   where ReturnPeriodFactor is a small lookup table that converts the selected return period into a scaling factor (e.g., 10‑yr = 0.6, 20‑yr = 0.8, 50‑yr = 1.0, 100‑yr = 1.3).

Now the client can slide the multiplier and instantly see how the projected loss changes across the entire asset list—no need to re‑run the hydraulic model.

10. Document Your Assumptions in a “Metadata” Tab

Transparency builds trust. Create a separate worksheet called Metadata and log the following items:

When a stakeholder asks, “Why does the EAD for the school differ from the municipal report?On top of that, ” you can point directly to the assumption row that explains the loss ratio used for educational facilities. This practice also makes future audits painless.

11. Integrate GIS Snap‑shots for Visual Context

Numbers tell one story; maps tell another. If you have ArcGIS Pro, QGIS, or even the built‑in Swift River map viewer, export a high‑resolution PNG of the flood extent for the scenario you’re reporting. Then:

1. Insert the image into the “Summary” tab (Insert → Pictures).
2. Add a call‑out box that references the key assets highlighted in the Excel table (e.g., “Red polygons = assets with FRR > 80 %”).
3. Link the image to the workbook’s “Map Ref” column using a hyper‑link formula:

   =HYPERLINK("[Path]\FloodExtent_2025.png","View Extent")
   

The final PDF that you send to the client now contains both the quantitative table and a visual flood footprint, satisfying both data‑driven analysts and visual‑oriented decision makers That's the part that actually makes a difference. Practical, not theoretical..

12. Perform a Quick “Back‑of‑the‑Envelope” Sensitivity Test

Before you close the file, run a sanity check on the model’s sensitivity to the most uncertain input—typically the rainfall intensity. Duplicate the existing sheet, rename it Sensitivity, and change the rainfall intensity column by ±10 %. Re‑run the “Export to Excel” step for the modified scenario (the UI lets you adjust the storm parameters without a full model re‑run). Compare the two EAD columns side‑by‑side; if a 10 % increase in intensity leads to a 200 % jump in EAD, flag that in the “Metadata” tab under Key Sensitivities. This brief exercise helps you anticipate client questions about uncertainty.

This is the bit that actually matters in practice.

13. Lock Down the Final Deliverable

Once you’ve polished the workbook:

1. Protect the sheet (Review → Protect Sheet) but leave the input cells (the “What‑If” dashboard) unlocked.
2. Set a password for the VBA macro (if you used one) to prevent accidental edits.
3. Save as an “Excel Binary Workbook” (.xlsb) for smaller file size and faster opening.
4. Export a PDF of the “Summary” and “Asset Impact” tabs (File → Export → Create PDF/XPS).

Deliver both the .xlsb (for analysts who may need to dig deeper) and the PDF (for senior management). This dual‑format approach satisfies the full spectrum of stakeholders.

Final Thoughts

The Swift River Client Report Sheet is more than a static dump of hydraulic results; it’s a living bridge between sophisticated flood‑modeling engines and the business decisions that follow. By:

• mastering the sheet’s layout,
• hunting down common data‑import quirks,
• adding conditional formatting and interactive “What‑If” controls,
• documenting every assumption, and
• pairing the numbers with clear visual maps,

you turn raw simulation output into a compelling, decision‑ready narrative.

When the next client opens that green‑highlighted workbook, they should see a clean, colour‑coded summary, an interactive dashboard that lets them explore “what‑if” scenarios, and a concise set of assumptions that answer the “why” behind every figure. With those tools in hand, you’ll not only deliver accurate flood‑risk assessments—you’ll empower your clients to act on them with confidence Worth keeping that in mind..

Happy modeling, and may your spreadsheets stay clean and your flood forecasts stay reliable.

14. Plan for Future Enhancements

A well-designed workbook should evolve with your practice. Consider these upgrades for the next iteration:

• Automated Data Refresh: If your hydraulic model outputs change frequently, explore linking the Excel workbook directly to the model’s database (e.g., via ODBC connections) so results update with a single click.
• Additional Scenario Tabs: Create separate sheets for different return periods (10-year, 50-year, 100-year, 500-year) with consistent formatting, allowing clients to compare across scenarios without scrolling.
• Integration with GIS: Embed static map images now, but plan for dynamic GIS linkage using tools like ArcGIS Online or QGIS to let users toggle between different flood extents interactively.

15. Document Version Control

Maintain a version history within the "Metadata" tab. Each time you deliver an updated workbook to the client, record:

• Version number (e.g., v1.0, v1.1)
• Date issued
• Summary of changes (e.g., "Updated rainfall intensity based on revised NOAA Atlas 14 data")
• Author

This simple practice prevents confusion and provides an audit trail—particularly valuable for regulatory submissions or multi-year projects.

16. Train Your Client

Finally, consider including a brief "User Guide" tab with 3–5 screenshots and step-by-step instructions on how to:

• Interpret the dashboard
• Use the What-If scenario controls
• deal with between tabs

Empowering the client to explore the tool independently transforms the deliverable from a static report into a strategic asset they can use for ongoing risk management.

By following this comprehensive workflow—from structuring the raw data through sensitivity analysis, visual storytelling, and secure delivery—you position yourself as a trusted advisor rather than merely a technical consultant. The Swift River Client Report Sheet becomes a testament to your professionalism: rigorous in methodology, clear in communication, and actionable in practice That's the whole idea..

This changes depending on context. Keep that in mind.

When clients see that green-highlighted workbook, they should immediately recognize quality, transparency, and value. That is the standard worth delivering, every time Small thing, real impact..