Advisory stream › Process & Treatment Systems
Once the treatment route is confirmed, it must be converted into a defined process and system scope. We develop the design basis, process sizing, equipment duties, system boundaries and performance requirements needed for coordinated design, procurement and delivery.
Overview
A confirmed treatment route is not yet a design scope. We develop the balances, sizing criteria, equipment duties, coordination requirements and acceptance basis needed to progress into engineering and supplier engagement.
How it works
A confirmed route still requires documented design assumptions, operating cases, system boundaries and performance requirements. We convert it into a coordinated process scope with defined balances, sizing criteria, equipment duties, system connections and acceptance requirements.
Design basis & process sizing
Establish flows, loads, balances, operating cases, design margins and equipment duties for the required process conditions.
System boundaries & coordination
Define the process, utility, civil, electrical and control requirements that connect each package to the wider system.
Design documentation & acceptance
Typical triggers
Outputs for the next project stage
We develop confirmed treatment routes into coordinated process and system scopes. The work covers design criteria, process sizing, equipment duties, system boundaries, documentation requirements and the performance basis for procurement and delivery.
Each scope applies the design process to a different system duty. Select a system to see the design basis, coordination requirements and performance criteria we define.
What we define
Develop the confirmed liquid-treatment route into a coordinated design basis with defined balances, sizing criteria, equipment duties and operating requirements.
These examples show how a confirmed treatment route is developed into defined process and system outputs for the next project stage.
Typical output
Establish the operating cases, balances, sizing criteria and design margins needed to define each process duty.
Typical output
Define how process packages connect to utilities, civil works, electrical systems, controls and the wider site.
Typical output
Prepare the process information and equipment requirements needed at the agreed level of design definition.
Typical output
Define the operating ranges, performance requirements, commissioning checks and evidence needed for acceptance.
Tip: swipe/scroll to browse. Use these as starting points, scope is tailored to the scheme and procurement context.
If you have a confirmed treatment route, the next step is to develop it into a defined process and system scope. We can establish the design criteria, balances, equipment duties, system boundaries, control requirements and acceptance basis needed for the next project stage.
Recurring gaps that affect process definition, system coordination and acceptance.
When flows, loads, operating cases and margins are not documented, equipment can be sized against different assumptions and package requirements begin to diverge. Establish the design basis, balances and equipment duties before detailed selection or procurement.
Process packages cannot be integrated reliably when utility, civil, electrical, control and access requirements are left implicit. Record package boundaries and connection requirements so each discipline and supplier works from the same basis.
When operating ranges, commissioning checks and required evidence are not agreed early, performance can be interpreted differently during final verification. Define the performance and acceptance basis as part of the design scope.
