Skip to content

Design check

Results tab, Design check. It reads the whole run and returns what is wrong with the model, ranked, with a locate link on every finding.

The design check: findings grouped and ranked, each with a locate link, and suggested next steps ordered by what to fix first.

Structural, no run needed: connectivity, links pointing at missing nodes, nodes that cannot reach an outfall, adverse (uphill) slopes, near-flat and very steep pipes, over-deep manholes.

Hydraulic, from the run:

FindingWhy it matters
FloodingWater is leaving the system at that node
SurchargePeak level reached the rim, without spilling
d/D at or above 1No spare capacity
d/D at or above 0.9Approaching capacity
Velocity below self-cleansingSolids deposit - septicity, odour, blockage
Velocity above scouringErosion risk, usually over-steep gradient
d/D under 0.1 at peakPossibly oversized

Thresholds follow the model’s unit system: 0.6 m/s in a metric model, 2.0 ft/s in a US one.

Below the summary is an ordered list of what to do. The order is deliberate, and it is ordered by what invalidates what:

  1. Connectivity first. Flow that cannot reach an outfall makes every downstream result meaningless.
  2. Then slope. An adverse slope distorts the whole hydraulic grade line.
  3. Then flooding, checked for whether it is genuine under-capacity or an inflow error.
  4. Then sizing.

A model that cannot drain is not worth resizing. That is why “fix drainage” always comes before “resize conduits”.

Engineers instinctively treat undersized pipes as the problem. Oversized foul sewers are also a defect: at low fill the velocity drops below self-cleansing, solids settle, and you get septicity and hydrogen sulphide. The check flags both directions, and the tension between capacity and velocity is usually the actual design problem.

The design check appears in the printed report as grouped findings with the worst elements named, plus the same next steps - so the analysis travels with the model rather than living only on screen.