One calibrated model.
Four layers built on it.

Everything Hydrocycle offers derives from a single hydraulic model of a drainage network and the surface above it.
Each layer takes the layer below as its input.
When the model is updated for a new basin, a resized pipe or a new development, every layer above it updates too.
Layer 1: Drainage Model · Delivered

What it is. A detailed, coupled 1D/2D hydraulic model of the drainage network and the surface above it. The 1D part describes flow inside pipes, manholes and channels. The 2D part describes water moving across streets and land. Because the two are coupled, water that exceeds pipe capacity appears on the surface where it would actually flow.
Built from. The network's survey and as-built records, terrain data and rainfall records.
Evolving. The model is refined against recorded storms and field observations as they occur.
Delivers. A detailed model, built by our engineers, at one of two scales. A city-wide model typically takes 6 to 18 months of specialist work and is commissioned once by the municipality or utility that owns the network.
A sub-basin model covers the area around specific assets and can be commissioned by an asset owner, lender or insurer. Every layer above reuses the model, under the terms agreed with whoever commissioned it.
For. Engineers and network owners.
Layer 2: Planning Scenarios · Delivered

What it is. Engineering options tested on the model before anything is built: a larger pipe, a detention basin, a blue roof, an infiltration well.
Built from. Layer 1, plus the design option to be tested.
Delivers. For each option, the change in flood depth, extent and arrival time, and the size at which the measure is needed. Available from the day the model is delivered, priced per scenario.
For. Engineers, developers and property owners.
Layer 3: FloodOS · In development

What it is. Live rainfall from radar and gauges, plus sensor data, run through the model during a storm.
Built from. Layers 1 and 2, plus live data feeds.
Designed to deliver. A forecast by street: which street, how deep, how many minutes until arrival. A six-level readiness scale, with a playbook that assigns a task, an owner and a deadline at each level.
Dynamic. Each storm FloodOS runs will be recorded and fed back into the model, so the system refines itself over time.
For. Emergency teams and control rooms; later, insurers and property owners, for warnings ahead of a storm.
Layer 4: Risk Data · Roadmap

What it is. Flood depth and arrival time for every property inside a modelled area, from the same model. No separate model has to be built.
Built from. Layer 1 results for storms of different severity, aggregated by building footprint. Historical storms can be used for backtesting.
Delivers. API and file delivery for credit and underwriting systems, a building-level index, and site reports.
For. Lenders, insurers and property owners.
How it gets built. With design partners, starting with a scoped pilot on one city or portfolio.
Coverage. Risk Data will not depend on a city-wide model. Where none exists, we build a smaller model of the sub-basin around the assets in question.
The network data comes from the network records, which property owners can request, or from our field survey. Claims records, storm and flood history and local observations are used to check and refine the model.
City-wide model completed today: Herzliya, Israel.