All ideas

This is a very serious issue, if you accidently move an area, SmartTools will then double count that area next time you import it into Flow

When designing storage features in FLOW there is no current way of getting the storage for ponds to look correct to my knowledge graphically. It would be beneficial if you could import your base and top-of-pond strings directly from PDS and state ...

One page formal print out summarising the manhole, pipe and storage structure volumes within the SW network. This is often requested during planning stages of developments.

Include facility to quick save using Ctrl+S - it works in most other commonly used software so it's almost a reflex action for most users, and saves so much aggravation over lost work!

The flow through pond storage option allows the user to select a side slope, depth and base area. It can then predict the bank-top area of that structure. The user can also adapt the shape of the pond/basin in Flow and Live Design and these update...

when a foul sewer is simulated within flow, the software assumes a blockage within the network. This is not very useful when trying to design a network that just drains under normal circumstances. The current work around suggested by Causeway is v...

Clients are requesting we provide COBie information for drainage systems - it would be useful to have the ability to embed COBie data into the drainage model and export it for others to use. This is likely to be a more suitable feature in Flow but...

To allow an approximate overall attenuation volume when using oversized pipes or manholes, allowing a total possible volume with links and nodes could be useful for reporting purposes