Demand Tree

 WEAP uses a hierarchical structure to disaggregate water demand data. You can easily adapt this structure to the nature of your problem and data availability. A hypothetical example of a multilevel demand structure is shown on the right.

The first level corresponds to the demand sites (from the Schematic created on the Schematic View). Below this, you can create as many levels as you wish. For example, South City is broken down into single and multifamily, and further by end use, while West City has no disaggregation. WEAP is flexible in allowing you to enter aggregated data initially, and to refine the demand projections later as more detailed data becomes available or necessary.

Examples of disaggregation:

You can organize the demand tree along the lines of the available data. For example, under the agricultural sector, the irrigation area for each crop can be identified at the subsector level. One level down, the percentage of each irrigation technique in each crop may be assigned at the end-use level. Another equally valid way to organize the agriculture sector would be to identify irrigation districts at the subsector level and the crops grown within the irrigation districts at the end-use level.