Delta Hydro Engineers (Pty) Ltd The Flood Specialists

Custom Software

Modelling Platform Customisation

Extensions, scripting, and automation on top of commercial hydraulic modelling platforms. Let your modellers spend time on analysis, not on button-clicking.

Integration Scoped project

Examples

  • Batch-running HEC-RAS across a grid of design events and post-processing outputs to GIS-ready rasters
  • Automating MIKE scenario setup from a project template — one configuration file instead of a manual sequence
  • EPANET calibration scripts that run permutations and track convergence without a human at the keyboard
  • Wrapping a commercial modelling engine in a repeatable CLI so CI can run the regression suite

Who it’s for

Modellers who know their platform well and hit its UI limits every project. The engine is fine; the manual wrapper around it eats days. We script the wrapper so the engine does what it’s good at and your modellers stop repeating themselves.

What you get

  • Python or command-line automation around your existing modelling platform.
  • A documented CLI or library your team can call from their own scripts.
  • Example runs covering the workflows you wanted to automate.
  • Source code, licensed to you.

How we work

Modelling-platform customisation is scoped project work — the problem is usually well-defined (“run this permutation set without manual input”) and finite. We scope, build, validate against a baseline run your modellers trust, and hand over.

  1. Baseline. We watch or recreate the manual workflow on a real example and record the outputs. This is the reference for validation.
  2. Automate. We write the automation and confirm its outputs match the baseline to an agreed tolerance.
  3. Validation pass. Your modellers run the automation on a different project; we fix the edge cases that surface.
  4. Handover. Documented CLI/library, run examples, and a brief.

Stack & interoperability

  • Platforms we have worked with: HEC-RAS, MIKE suite (via exported command-line runs and native APIs where available), EPANET, SWMM, QGIS.
  • Scripting: Python (most common), PowerShell for Windows-only pipelines, plain batch where appropriate.
  • Tested under: the platform versions your team actually runs. We confirm versions up front and do not implicitly upgrade you.

What this is not

  • Not a modelling engine. We do not replace your commercial platform; we make it easier to use.
  • Not a guarantee of vendor-independent scripting. Some platforms only allow partial automation; we will be explicit about limits up front.

Related consulting services

Request a scoped proposal