Aqua Design

Advisory stream › Process & System Design

Process & System Design Advisory

Late design changes derailing delivery? Connection point mismatches discovered at installation? Unclear performance criteria causing disputes? We take confirmed scheme directions and engineer them into vendor-ready scopes, with sizing basis, boundary registers, FEED-style packs, and performance specifications that protect delivery without late surprises or re-interpreted intent.

Outcome-led scope Coordination points & connections Performance checks Vendor-ready documentation
Start an enquiry View project examples

Overview

Process design succeeds when the scope is engineered early, not after vendors have priced unclear scope notes. We convert scheme directions into buildable packages with sizing basis, boundary clarity, and performance review requirements so the next party can move without guesswork.

Typical deliverables we produce: sizing basis & design margins, boundary registers & connection requirements, FEED-style documentation packs, performance specifications & verification protocols, and vendor-ready technical requirements.

How it works

From scheme intent to vendor-ready documentation

Design problems are usually discovered at integration: where sizing assumptions were never documented, where scope boundaries were assumed rather than defined, and where performance criteria were left to be agreed later. We convert scheme directions into engineered packages, with sizing basis, boundary registers, and verification protocols, so the next party can price, integrate and commission without ambiguity.

Sizing & engineering basis

Convert scheme intent into engineered sizing, flows, loads, peaks, design margins, and equipment duty definitions that keep performance stable under site operating variability.

Handoff & connection clarity

Define every coordination point between processes, utilities, and site systems, so integration happens without rework or late discoveries at installation and commissioning.

Verification & close-out

FEED-style documentation packs: PFDs, P&ID intent, datasheets, and general arrangement concepts.
Performance specifications: target ranges, test protocols, and information requirements for close-out.
Vendor scope boundaries: where plant responsibility ends and package responsibility begins.

Typical triggers

  • Vendors pricing unclear scope notes, with different sizing assumptions creating incompatible quotes.
  • Connection point mismatches discovered at installation because boundaries were never formally registered.
  • Commissioning disputes over performance review because criteria were left vague or interpreted differently.
  • Late design changes adding cost and schedule risk because scope wasn't engineered before procurement.

Outputs you can hand to vendors

  • Sizing basis: design flows, loads, peaks, margins, and equipment duty definitions.
  • Handoff register: process, utility, civil, and vendor scope boundaries all registered.
  • Performance specifications: what must be proven at commissioning, and how.

Services & Capabilities

We provide process and system design advisory from sizing basis definition through to vendor-ready documentation packs, helping you engineer treatment sequence scopes, boundary registers, FEED-style deliverables, and performance specifications that protect delivery without late surprises.

Design routes & capabilities

These are design routes, not service packages. We use them to structure engineering scopes from treatment sequences through to utilities and automation, defining coordination points and performance review requirements.

Tip: click a route to see the focus areas.

Focus areas

Treatment sequence engineering

Convert a confirmed process scheme into sized, documented engineering with clear coordination points, so vendors price the same scope and commissioning has a defined performance basis.

Design flow and load cases: average, peak, storm, and future growth scenarios.
Process boundary register: flow/load/quality at each unit boundary across the process sequence.
Equipment duty definition: pumps, blowers, mixers, dosing, and mechanical scope.
Performance specifications: commissioning checks and information requirements for close-out.

Project configurations & snapshots

These configurations show how process design scopes are set out as vendor-ready packages, so suppliers can price, integrate, and commission without ambiguity or missing information.

Snapshot

Sizing basis & design margins pack

A documented sizing basis that vendors and engineers can work from, with flows, loads, peaks, and design margins that protect performance under site operating variability.

  • Design flow/load cases including peak, storm, and future growth
  • Process and hydraulic margins defined before equipment selection
  • Equipment duty definitions: pumps, blowers, mixers, and dosing systems

Snapshot

Handoff register & connection pack

Define every coordination point across processes, utilities, and site systems, so integration happens at the right time, without late discoveries or boundary disputes.

  • Process boundary register: flow/load/quality at each unit boundary
  • Utility connections: power, water, drainage, chemical delivery, ventilation
  • Vendor scope boundaries: where each package begins and ends

Snapshot

FEED-style documentation package

Produce the documentation level that vendors can price and commission, PFDs, P&ID intent, equipment datasheets, and layout concepts that eliminate ambiguity from procurement.

  • Process flow diagrams with mass/energy balances where relevant
  • Equipment datasheets and technical specifications
  • General arrangement concepts: layout, access, and maintainability

Snapshot

Performance specification & verification protocol

Define what must be proven at commissioning, with target ranges, test protocols, and information requirements, so close-out is based on facts, not assumptions or re-interpreted intent.

  • Performance criteria: effluent quality, process stability, operational readiness
  • Commissioning test protocols: step-by-step checks aligned to target ranges
  • Handover requirements: deliverables, operator guidance, O&M documentation, and completion

Tip: swipe/scroll to browse. Use these as starting points, scope is tailored to the scheme and procurement context.

Get in touch , engineer your process scope

If you have a confirmed scheme direction that needs to be engineered into a vendor-ready scope, or a design pack that is not clear enough to procure from, we can help you produce the sizing basis, boundary registers, and performance specifications that protect delivery.

Helpful inputsconfirmed scheme intent, known design flows and loads, existing documentation (process reports, vendor information), and procurement timeline.
If relevantcoordination constraints with existing plant, specific vendor packages already procured, commissioning milestones, and any known gaps in current documentation.
Contact us Explore project pathways
Quick enquiry

Common Patterns

Practical patterns we see repeatedly in process and system design advisory engagements.

Unclear scope notes produce incompatible quotes

When vendors price from different assumptions, quote comparisons are meaningless and scope gaps emerge at integration. Engineer the sizing basis and boundary register before procurement, so every vendor prices the same scope with the same boundaries.

Assumed scope boundaries become disputed boundaries

Coordination points that are not formally registered tend to be re-interpreted by each party, leading to rework at installation and disputes at commissioning. Define scope boundaries explicitly in the design pack so there is no room for assumption.

Performance criteria left vague become close-out disputes

If performance criteria are not defined before commissioning starts, what constitutes success becomes a negotiation. Set target ranges, test protocols, and information requirements in the design pack, so close-out is based on agreed facts, not re-interpreted intent.