Country, programme owner and procurement/funding pathway
RHELGAN · PROJECT AUTHORITY CENTRE
Move from product interest to a controlled project specification.
Turn a programme requirement into an auditable supply package across housing, WASH, water, power, health, education, community infrastructure and recovery while keeping local engineering, donor requirements, installation and operations visible.
01 · PROJECT INPUTS
Define the conditions before the exact system is released.
These inputs are deliberately upstream of model selection so the product does not dictate the brief.
Population, household count or facility user demand
Housing / WASH / water / health / education / community building mix
Climate, hazards, site access and logistics constraints
Water source, wastewater pathway and daily demand assumptions
Power source, critical loads, backup strategy and electrical standard
Accessibility, safeguarding, public-health and local code requirements
Manufacturing phasing, freight, storage, installation and handover responsibilities
02 · EVIDENCE CONTROL
Keep project claims attached to what the evidence actually proves.
Generic declarations, outdated catalogues or unrelated certificates should not be carried into a project as exact-system evidence.
Exact building/system technical datasheets and material schedules
Structural/fire/public-health evidence applicable to the selected system
Water, sanitation and treatment evidence tied to the exact equipment
Power/generator certification and exact component documentation
Factory QA, inspection, packing and traceability plan
Warranty, manuals, critical spares and operator training scope
Donor/agency/local statutory requirements recorded separately from product evidence
03 · CAD / DRAWING REGISTER
Planning references are not exact-system construction drawings.
Every drawing/model status stays visible so consultants know what can be used now and what only exists after configuration or project-specific design.
| Resource | Status | Purpose |
|---|---|---|
| Programme / community concept / planning layout | Public planning | Early scope, interface and consultant coordination only. |
| Generic technical reference / typical detail | Public planning | Explains system logic without representing an exact supplied configuration. |
| Exact-system GA / dimensional drawing | Exact-system | Issued only after the quoted system/configuration is known. |
| Native CAD / DWG / DXF | Verify availability | Availability and revision must be confirmed against the exact supplied system. |
| BIM / Revit / IFC object | Verify availability | Only described as BIM where a genuine verified native model exists. |
| Foundation / fixing / setting-out drawing | Project-specific | Depends on site/building conditions, local engineering and the selected system. |
| Services / electrical / controls interface | Project-specific | Coordinates the supplied system with local power, data, water, drainage or controls. |
04 · SPECIFICATION STARTER
Write the project around performance, interfaces and evidence.
These clauses are a project-planning structure, not a substitute for local professional specifications or exact-system documentation.
Programme outcomes and design population
Building and infrastructure performance criteria
Climate/resilience and hazard requirements
Water/WASH demand and service interfaces
Power and backup-power architecture
Accessibility and safeguarding interfaces
Documentation, QA and inspection requirements
Packing, freight, site receiving and phased rollout
Installation / commissioning / operator responsibility matrix
05 · TENDER / RFP SCHEDULE
Ask bidders for the same controlled information.
A consistent schedule makes technical comparison easier and reduces hidden assumptions.
Programme brief and destination
Site/masterplan information
Required buildings/infrastructure quantities
Performance and evidence requirements
Utility/service assumptions
Required drawings/submittals
Manufacturing/inspection programme
Packing and logistics strategy
Warranty, spares, manuals and training
06 · OPERATIONS & HANDOVER
Specify how the system will be maintained after delivery.
Maintenance, spares, records and inspection should be defined before purchase, especially for remote or high-use projects.
Asset register by building/system
Routine WASH and water-system inspection
Generator/power maintenance schedule
Consumables and critical spare-parts register
Cleaning, hygiene and public-health routines
Defect logging and warranty escalation
Operator manuals / competency records
Periodic review against changing programme demand
DOWNLOADABLE PROJECT RESOURCE
Carry the authority pack into the project file.
Export the current project-control structure, then replace planning statements with exact project/system information as the design develops.