Compliance Checking

HydraStorm continuously checks every pipe against the design criteria you've configured in Project Settings. Results are summarized in the Compliance column of the results grid, on the Compliance sheet of the Excel export, and inline on the profile view via colored markers.

Criteria Checked

CriterionSource SettingPass Condition
Min VelocityMin Full-Flow Velocity (fps)Velocity at design flow ≥ minimum
Max VelocityMax Full-Flow Velocity (fps)Velocity at design flow ≤ maximum
Min SlopeMinimum Pipe SlopePipe slope ≥ minimum
Min Pipe CoverMinimum Pipe Cover (ft)Ground − pipe crown ≥ minimum
Max Pipe CoverMaximum Pipe Cover (ft)Ground − pipe crown ≤ maximum
Min DiameterMinimum Pipe DiameterPipe diameter ≥ minimum
HGL CoverHGL Cover (design) / Check HGL CoverGround − HGL ≥ required cover
Capacity(implicit)Design flow ≤ full-pipe capacity

Each pipe receives a per-criterion Pass / Fail / N/A status. N/A applies when the criterion does not apply (e.g., pipe cover for an above-ground pipe, or HGL cover when no rim is set).

Status in the Results Grid

The Compliance column shows P/N where P is the count of passing criteria and N is the count of applicable criteria. 5/5 means full compliance; 3/5 indicates two failures. Hover for a tooltip listing the failing criteria.

Excel Compliance Sheet

The export bundles a Compliance sheet with two tables:

  • Per-criterion summary — total passes, failures, N/A across the whole network
  • Per-pipe detail — one row per pipe per failing criterion with the actual vs required value

This is the sheet to attach to AHJ submission packages — it self-documents the design's adherence to your selected design standard.

Profile View Markers

Pipes failing one or more criteria are flagged with a small warning glyph at their downstream endpoint on the profile view. Click the glyph to see the failing criteria.

Configuring Criteria

All criteria values come from Project Settings. When a design standard is applied to a project, HydraStorm prompts you with a checklist of values that differ from the standard's published criteria — accept the suggestions to align with the municipality's published values.

Tip: The Check Storm uses its own CheckHglCover value, which is typically more relaxed than the design storm. Many jurisdictions allow HGL at ground for the check storm but require freeboard for the design storm.

Disabling Individual Checks

Project Settings → Calculation lists a per-project Check: ... toggle for each of the criteria above (Min Velocity, Max Velocity, HGL Cover, Min Slope, Min Pipe Cover, Max Pipe Cover), each set to Enabled or Disabled. Disabling a check removes it from the Comply column and the compliance count entirely — it isn't just hidden, it's not evaluated, so it also drops out of the Excel Compliance sheet.

Use a network-wide disable for a criterion your jurisdiction genuinely doesn't enforce (e.g., no minimum velocity requirement). For a one-off accepted violation on a specific pipe, prefer acknowledging the individual failure instead (below) — disabling the whole check network-wide would hide real violations elsewhere in the network, while acknowledging keeps the audit trail on just that pipe.

Project Settings Calculation tab showing the per-check Enabled/Disabled toggles
Project Settings Calculation tab showing the per-check Enabled/Disabled toggles

Acknowledged Failures

Sometimes a failure is acceptable (e.g., an outfall pipe that intentionally exceeds max velocity into a stilling basin). Right-click a pipe with a failing check — in the profile view or the results grid — and choose Acknowledge Check Failures... to open a dialog listing every failing check for the pipe. Check the ones you've reviewed and accept, and enter a note explaining why the failure is acceptable. Clicking OK with a checked row that has no note blocks the dialog and lists which rows still need one; once accepted, the note is saved with the project and shown in the compliance tooltip. Uncheck a row to withdraw an acknowledgment.

An acknowledged failure still shows as a failure in the Comply column, but colored amber rather than red, and it no longer counts as non-compliant in summary counts. A pipe with only acknowledged failures (no unacknowledged ones) shows amber; any remaining unacknowledged failure keeps the row red. Acknowledgment applies to both the design and check storm results for that check.

'Acknowledge Check Failures' dialog showing the failures grid with Ack checkboxes and a required note field
"Acknowledge Check Failures" dialog showing the failures grid with Ack checkboxes and a required note field