Skip to main content
Get in touch
At the ConfluenceIndependent applied research

The models exist. Making them work as one defensible decision system is the problem.

Integrated water-resources modeling, built so that provenance, uncertainty, and assumptions survive all the way to the decision.

01The problem

Integration is the constraint, not modeling capacity

Water-resources management is rarely limited by the absence of a model, but by how badly independently built models, datasets, scales, and assumptions combine into something a decision can rest on.

01
Fragmented ownership
Models are built independently by the specialists who understand them best, then asked to interoperate through spreadsheets and file handoffs that preserve none of their structure.
02
Incompatible semantics
The same term means different things across disciplines. Demand, storage, loss, and reuse are each specific to whoever defined them, and those definitions rarely travel with the numbers.
03
Scale mismatch
Daily against monthly, reach against basin, parcel against region. Reconciling resolution is treated as a preprocessing chore rather than an analytical decision.
04
Flattened uncertainty
Ranges collapse to point values at every boundary crossing. By the time analysis reaches a decision-maker, the confidence quantified upstream has been quietly discarded.
05
Lost provenance
Six months after a recommendation, no one can reconstruct which assumption, which dataset version, or which model run produced a specific number.
06
Integration latency
When re-running a connected analysis costs weeks, teams ask fewer questions. The real loss is not the delay but the analyses never attempted and the dependencies never found.

Changed information does not propagate through connected systems, so knowledge gaps and unrecognized dependencies stay hidden until after the decision is made.

02The approach

Shared foundations around independently owned science

The answer is not one model to replace the others. It is a shared foundation that specialist models can connect through while their authors retain scientific control.

01
Shared semantics
Common definitions and versioned data contracts, so a quantity means the same thing on both sides of a handoff.
02
Retained ownership
Domain specialists keep authorship and scientific control of their own models. Integration is a contract to meet, not a takeover.
03
Explicit uncertainty
Uncertainty crosses boundaries as a first-class property rather than collapsing into a single number at each step.
04
Provenance and lineage
Every output traces back to its inputs, assumptions, source documentation, and the model version that produced it.
05
Versioned evidence
Planning versions are preserved rather than overwritten, so past decisions stay reconstructible in the context that produced them.
06
Auditable workflows
The path from evidence to recommendation is inspectable by someone who was not in the room when it was built.
Read the full approachIncludes the implemented foundation
05The record

Peer-reviewed, and cited

The integration argument is made by someone who has published the underlying science, not only written about it.

13

Peer-reviewed articles

419

Citations

11

h-index

11

i10-index

Google Scholar, August 2026

Most recent

  • Morphodynamics of anabranching structures in the Peruvian Amazon River

    Earth Surface Processes and Landforms · 2025

  • Identifying critical source areas of non-point source pollution to enhance water quality: Integrated SWAT modeling and multi-variable statistical analysis

    Water Research · 2024

  • Hydrogeomorphology of the origin of the Amazon River, the confluence between the Marañón and Ucayali rivers

    Earth Surface Processes and Landforms · 2024

Selected venues

  • Proceedings of the National Academy of Sciences
  • Nature Communications
  • Water Research
  • Water Resources Research
  • Journal of Geophysical Research: Oceans
  • Advances in Water Resources
  • Remote Sensing
Contact

Two useful conversations

Whether that is a joint proposal, a model that needs to talk to three others, or a long-range planning problem that has outgrown its spreadsheet — say which and the reply will be more useful.

Start a conversation
Research collaboration
Joint proposals, co-authored work, shared datasets, model interoperability, or a program that needs an integration layer. Also the right choice for institutions weighing how this capability might sit alongside existing teams.
Technical engagement
Water demand and supply modeling, long-range scenario planning, hydraulic and coastal analysis, geospatial and machine-learning work, or decision-support software for utilities, agencies, and engineering firms.