EnWater Design
FlowPlan project framework

FlowPlan › Framework

FlowPlan Framework

FlowPlan is EnWater Design’s structured project framework for developing water, wastewater, reuse and residuals work from defined requirements through planning, design, sourcing, delivery and verification. It can be applied to a new project, an existing system, a defined advisory scope or a specific technical assignment.

It keeps outcomes, information needs, decision criteria and technical requirements connected as the work develops, so each stage builds on a confirmed project basis.

Overview

FlowPlan provides a consistent decision structure across studies, process design, diagnostics and project support. It can be used from the beginning of a project or applied to a defined part of an existing assignment.

FlowPlan modules are named process and supporting-system building blocks used to connect diagnostic findings, process routes, design duties and delivery requirements. Their selection and configuration remain specific to the project and do not prescribe a fixed supplier or equipment package.

Requirements and constraints are confirmed before technical routes are compared.
Information reviews and diagnostics are selected to support defined decisions.
Relevant module families are identified, sequenced and developed into clear project requirements.
Decisions and verification criteria remain connected through delivery and operation.

Where FlowPlan is applied

FlowPlan can be used across new plants, upgrades, reuse programmes, residuals work and defined technical assignments. The same framework connects the project basis, required information, system configuration and delivery requirements.

Project basis

Project definition & planning

Establishes the required outcomes, constraints, system boundaries and decisions the work must support.

Connected to: scope definition, systems planning and project-stage requirements.

Information basis

Diagnostics & evidence

Defines the site information, checks and performance criteria needed to compare routes on a common basis.

Connected to: data review, sampling, process assessment and reuse evaluation.

Technical development

Process & system configuration

Develops the relevant FlowPlan module families for treatment, reuse, residuals, utilities, controls and monitoring into a coordinated project basis.

Connected to: route comparison, module mapping, process mapping, solution design and phasing.

Project progression

Delivery & verification

Prepares technical scope and procurement requirements, then keeps acceptance criteria visible through commissioning and early operation.

Connected to: supplier engagement, design review, performance testing and optimisation.

How FlowPlan works in practice

FlowPlan uses four linked stages. A project may enter at a different point depending on its starting condition, but the same decision structure is maintained.

Stage 1

Define outcomes & constraints

Confirm the project boundary, required water and residuals outcomes, capacity, operating constraints and schedule before routes are compared.

  • • Project basis and scope boundary.
  • • Target performance and acceptance requirements.
  • • Regulatory, client, operating and funding requirements.

Stage 2

Confirm information & diagnostics

Identify information gaps and complete the targeted reviews or checks needed to confirm flows, loads, process conditions, risks and reuse potential.

  • • Flow, load and variability review.
  • • Process, residuals, odor and operating assessment.
  • • Reuse, source-control and site-constraint checks.

Stage 3

Configure modules & project routes

Compare viable routes, select and sequence the relevant FlowPlan modules, and define the connected residuals, utility, control and monitoring requirements for the selected direction.

  • • Module selection, sequence and route alternatives.
  • • Defined duties, connections and performance criteria.
  • • Footprint, integration and phasing requirements.

Stage 4

Prepare & support delivery

Develop the selected route into supplier-ready requirements and retain the design basis through proposal review, commissioning and performance confirmation.

  • • Design basis, Terms of Reference and technical scope.
  • • Proposal comparison and responsibility notes.
  • • Commissioning, acceptance and monitoring requirements.

Explore FlowPlan in more detail

The framework is applied through focused FlowPlan areas. Each area can be used on its own or combined with others according to the assignment.

Start with the area that matches the current project need. The common framework keeps the work connected without requiring every area on every assignment.

Develop the route

Configure processes & systems

Compare viable routes, select and sequence the relevant FlowPlan modules, and define their duties, connections, performance criteria and site requirements.

Prepare delivery

Define requirements & verification

Prepare the supplier scope, project-stage deliverables, commissioning basis and performance checks.

How a FlowPlan engagement is structured

The four stages above can be developed through six detailed engagement steps. Not every assignment requires all six; the relevant steps are selected according to the starting point and required output.

FlowPlan engagement step

Scope & Decision Basis

Confirm the required outcomes, system boundary, known constraints, available information and decisions the work must support.

Each step supports one or more of the four linked FlowPlan stages.

Connected outputs

Typical inputs & checks

  • Project information review
  • Outcome and constraint confirmation
  • Existing-system and site review
  • Information-gap check

Activities used at this step to confirm the basis and develop the work.

Technical outputs

  • Project basis summary
  • Scope boundary and responsibility notes
  • Initial information plan
  • Decision and acceptance criteria

Outputs can be scaled to the assignment and required project stage.

Start with the project need.

Bring the available project information, known constraints and required outcome. FlowPlan can begin with a new project, an existing-system review, a reuse target, a capacity requirement, a residuals issue or a defined technical assignment.