Plan water infrastructure with better visibility into cost and tradeoffs.
Nodavect develops optimization-based decision support for produced-water infrastructure. We help planning teams evaluate network investments, routing strategies, capacities, and operating scenarios across interconnected systems.
Infrastructure decisions are interconnected.
Pipeline additions, facility capacities, disposal access, treatment options, storage, and routing decisions affect one another. Nodavect is designed to evaluate these tradeoffs together rather than one asset at a time.
Infrastructure selection
Compare candidate pipelines, capacities, connections, and facility investments against system-wide operating implications.
Flow & routing strategy
Evaluate how produced water can move through existing and candidate infrastructure while respecting capacities and operating constraints.
Scenario comparison
Test alternative forecasts, cost assumptions, infrastructure options, and operating conditions before committing to a plan.
From planning data to a defensible recommendation
A focused Nodavect study can begin with the planning information teams already use.
- Projected water volumes
- Existing network topology
- Candidate pipelines and facilities
- Capacities and operating limits
- Capital and operating cost assumptions
Optimization as a decision-support layer.
The goal is not to replace planners. It is to give them a rigorous way to test more combinations, quantify tradeoffs, and compare a recommended plan with the current planning baseline.
Pressure-test the model on a real planning case.
Nodavect is seeking focused pilot opportunities where an operator or infrastructure planner has a network expansion, routing, or capacity decision that can be evaluated against an existing plan or historical case.
A pilot can help answer questions such as:
- Which candidate connections or pipelines are worth building?
- Where could additional treatment, storage, or disposal capacity create value?
- How should water be routed across the network under projected volumes?
- How sensitive is the recommended plan to assumptions or forecast changes?
Typical output
- Recommended infrastructure decisions
- Illustrative flow allocation across the network
- Capital and operating cost comparison
- Scenario and sensitivity discussion
- Clear comparison with the customer's current planning baseline
Research depth, applied to infrastructure decisions.
Sourabh Choudhary, PhD — Founder
Sourabh holds a PhD in Operations Research from the Georgia Institute of Technology, where his research focused on optimization methods for water-network design and operation. His work combines mathematical modeling, optimization algorithms, and practical decision-support tools for complex infrastructure and industrial systems.
Start with a bounded case and clear data expectations.
Early pilot work should be structured so that the customer knows what information is needed, what will be produced, and how project data will be handled.
Confidential customer data
Project-specific confidentiality and data-handling terms can be established before any sensitive information is transferred.
Focused scope
Pilots can begin with a bounded planning case, including sanitized or historical data where appropriate, before expanding to a broader deployment.
Transparent assumptions
Model inputs, planning assumptions, infrastructure alternatives, and cost drivers are made explicit so recommendations can be reviewed by the planning team.
Decision support, not a black box
Outputs are intended to support engineering and planning judgment with a quantitative comparison of alternatives, rather than replace it.
Have a produced-water planning case worth evaluating?
A historical project, upcoming expansion, or network-capacity question can be a useful starting point for a focused discussion.
Contact Nodavect →