RHELGAN · PROJECT RESPONSIBILITY MATRIX
Make every water-system interface somebody’s responsibility.
Water projects fail when tanks, treatment, foundations, external networks, electrical connections, commissioning and operations sit between scopes. This matrix is a starting framework for making those boundaries visible.
Responsibility matrix
Use this as the starting allocation — then edit it for the contract.
“RHELGAN”, “project team” and “local works” are not legal responsibility assignments by themselves. The actual quotation, contract, consultant scope and destination requirements must name the responsible parties.
| Interface | Typical starting owner | Control point |
|---|---|---|
| Water demand / service brief | Project team / client | RHELGAN can structure the intake; final demand basis must reflect the programme. |
| Source investigation + water analysis | Project team / appointed local specialists | Required before final source-specific treatment selection. |
| Storage equipment schedule | Defined supply scope | Tank class, material, geometry and accessories confirmed for the project. |
| Storage structural design | Defined per project | Exact responsibility must be stated: equipment design, foundation design and local structural review are separate interfaces. |
| Foundation / civil works | Local project works unless expressly included | Survey, soil, slab / support, drainage, anchoring and site preparation need a named owner. |
| Water treatment process | Defined supply / process scope | Source-water basis, finished-water target, process duty and performance responsibility must be explicit. |
| Pumps + controls | Defined supply scope | Pump duty, motors, control panel, alarms and included instruments are scheduled against the project. |
| External distribution network | Local / project hydraulic design unless expressly included | Pipe network, pressure zones, public mains and building connections require local coordination. |
| Electrical supply + earthing | Local electrical works unless expressly included | Voltage, phase, protection, earthing and connection point must match the destination. |
| Installation | Defined in project schedule | Local installer, supervision, specialist assembly or commissioning roles must be named before order. |
| Commissioning | Defined in project schedule | Functional testing, treatment startup, water-quality verification and records need clear ownership. |
| Statutory / public-health approvals | Responsible local project organisations / professionals | Destination requirements remain project-specific and cannot be assumed by generic product documentation. |
| Operations + water-quality monitoring | End operator / responsible organisation | Sampling, treatment consumables, alarms, maintenance and response procedures require an operating owner. |
| Warranty + spares | Defined supply scope | Covered equipment, warranty conditions, exclusions, spare-parts package and service route are documented at order. |
Four boundaries to close early
These are the interfaces most likely to create gaps.
Tank ↔ foundation
Tank reactions, geometry, support condition, slab / plinth design, anchoring and site drainage need coordinated drawings.
Treatment ↔ source water
The process basis must match representative source-water data and the agreed finished-water requirement.
Pump ↔ network
The selected duty point depends on the external distribution system, levels, losses and peak demand.
Supply ↔ local operation
Spares, consumables, training, water-quality checks and maintenance responsibility must survive beyond project handover.
RHELGAN · PROJECT SCOPE CONTROL