The IQQM CropMod2 replicates the water requirements for a cropped area. This is a process-based model which allows you simulate a farmer’s decision on the area to plant in each season and evapotranspiration of the different crop types, and generates a demand based on the maintenance of a target soil moisture level. You can also simulate rice irrigation by specifying ponding behaviour and return flows.

Configuring generic crop settings

Before configuring an IQQM CropMod2 Demand model on a Water User node, you must specify crop factors for the entire scenario using Edit » Crop Parameters.... Crop factors defined in this way are accessible for each water user node.

The method for defining crop factors is based on FAO 56 which divides the growth period of every crop into four developmental stages based generally on water requirements. These stages are:

Initial (or establishment) stage - occurs between planting and when there is approximately 10% ground cover. Water requirements are quite low and constant;
Crop development (or vegetative) stage - sees a rapid increase in the amount of water required by the crop until there is generally about 70% to 80% ground cover and maximum rooting depth is achieved;
Mid-season (or flowering) stage - requires the maximum amount of water in the life of the crop; and
Late (or yield and/or ripening) stage - there is an approximate halving of water requirement as the crop ripens, reaches maturity and is harvested.

The Configure Crop Parameters window (Figure 1) and the parameters required for each crop type are described in Table 1.

Figure 1. Configure Crop Parameters

Table 1. Crop Model - Crop parameters

Parameter	Type	Description
Crop Name	text	Reference name for crop
Repeats	integer	The growth pattern and duration is repeated by the specified number. For example a growth season of 5 months when repeated by a factor of 3 will have a growth period of 15 months.
Ponded		When ticked the crop mix in the water user node for this crop type requires input for targets for minimum and maximum pond level. Levels are used as targets to irrigate and drain area as occurs for rice.
Crop coefficients		Coefficients that define the straight lines connecting the four growth stages for the crop water requirements
Initial		Coefficient at start of the initial phase
Development		Coefficient at end of the initial phase and start of development phase
Mid-Season		Coefficient at end of the development phase and start of Mid-Season phase
Late-season		Coefficient at end of the Mid-Season phase and start of Late-Season phase
Maturity		Coefficient at end of the Late-Season phase
Number of growing days	days	Number of days within each stage of crop growth.
Losses		Crop factor editor window (Figure 2)

Figure 2. Crop factor Editor

Planted Area tab

This tab (Figure 3) broadly defines the area to be used and the proportions between the primary and secondary crops. The parameters that must be defined are described in Table 2. The Primary crop planting decision date refers to the day when the water user decides the area of crop(s) to plant in the primary season. This should be before the Start Date of any specified primary crop, otherwise the area initially planted will be based on the primary crop decision from the previous year. The start date of the crop is specified in the Crop mix tab. Similarly, the Secondary crop planting decision date is the day when the water user decides the area of crop(s) to plant in the secondary season. As per the primary season, this should be before the Start Date of any specified secondary crops.

Figure 3. Water User node (IQQM CropMod2, Planted Area)

Table 2. Crop Model - Planting Area parameters

Parameter	Units	Description
Maximum irrigable area	ha	Maximum area that can be planted
Maximum area for primary crop	ha	This is the maximum area that can be used in a simulation for all crops nominated as primary. A primary crop is one that is grown during the primary season, where there may be more than one crop type grown. This area cannot exceed the Maximum irrigable area
Maximum area for secondary crop	ha	This is the maximum area to be used in a simulation for all crops nominated as "winter". A secondary crop is one that is grown during the winter months, which is defined in the crop mix (winter). This area cannot exceed the Maximum Irrigable Area.

Soil tab

This tab (Figure 4) defines soil inputs. There are individual stores for each crop type. Areas that are not being cropped are referred to as fallow, and are simulated using two soil layers. Fallow area occurs between cropping seasons or during the irrigation season if the maximum developed area is not planted. At the end of a cropping season, the soil moisture of the crop area and fallow areas are merged. Table 3 provides a description of the parameters. Refer to the Source Scientific Reference Guide for more information.

Figure 4. Water User node (IQQM CropMod2, Soil)

Table 3. Crop Model - Soil parameters

Parameter	Units	Description
Maximum available soil moisture	mm	Depth of soil moisture available to the crop (field capacity). A soil moisture level of 0 represents the wilting point and the default settings will try to maintain a soil moisture level of half the field capacity.
Upper soil moisture depth of Fallow	mm	Depth of the upper soil moisture store for fallow areas. The lower soil store depth is equal to the Maximum available soil moisture less Upper soil moisture depth. Upper soil moisture store cannot be greater than the depth of the Maximum available soil moisture. The upper store is depleted by evaporation and the lower store, by the seepage rate. Water can move from the upper store to the lower store at the Infiltration Rate.
Infiltration rate from upper Fallow to lower Fallow	mm/d	The maximum rate of water movement from the upper soil moisture store to the lower moisture store. The actual infiltration rate is the product of this rate and the ratio of upper fallow moisture to upper fallow moisture capacity.
Seepage	mm/d	The maximum rate at which water drains from the lower soil moisture store when the area is not irrigated (fallow). Soil moisture will be depleted by the product of this rate with the ratio of actual soil moisture to maximum soil moisture.
Fallow factor	%	Crop factor for fallow ground. One value is used throughout the year. This factor is applied to the evaporation rate to determine the loss rate from the upper fallow area.

Climate tab

This tab defines four parameters (Table 4) for climatic data.

Table 4. Crop Model - Climate parameters

Tab	Units	Description
Evaporation	mm	The model uses pan evaporation with crop factors to calculate evapotranspiration volumes. Pan evaporation may be input as monthly averages or daily data and entered as either a time series or referenced to another Source scenario. See .
Average Evaporation	mm	Enter average daily pattern for reference crop evapotranspiration. The daily average is used to forecast crop demand. If no average evap data is added then an average for each day of the year (ie. 365 day pattern) is derived from the time series data. See
Rainfall	mm	The model uses rainfall data to replenish soil moisture. Excess runoff can be re-used by the water user node. Rainfall may be input as monthly averages or daily data entered as either a time series or referenced to another Source scenario. See .

You can specify four parameters for rainfall data in the Rain data tab (Figure 5 & Table 5).

Figure 5. Water User node (IQQM CropMod2, Climate, Rain data)

Table 5. Crop Model - Climate parameters (Rain data)

Parameter	Units	Description
Crop interception loss	mm	The depth of rainfall intercepted by the vegetative cover of the crop. Effective rainfall onto crops is the actual rainfall less this interception loss.
Fallow interception loss	mm	The depth of rainfall intercepted in fallow area.
Expected usable rainfall in primary growing season	mm	Depth of usable rainfall available for use by a crop during the primary growing season. Usable rainfall is actual rainfall less allowance for runoff and interception losses. This value is used when calculating the area to be planted at the primary growing season decision date if the volume risk function method is used.
Expected usable rainfall in secondary growing season	mm	Depth of usable rainfall available for use by a crop during the secondary growing season. Usable rainfall is actual rainfall less allowance for runoff and interception losses. This value is used when calculating the area to be planted at the secondary growing season decision date if the volume risk function method is used.

Risk tab

At the start of an irrigation season, each water user node decides on how much area is to be planted (and thus irrigated). This is determined by the Decision Date for the primary and secondary season. This calculation uses a relationship referred to as the farmer’s risk function. In the IQQM crop model, farmer’s risk is modelled in two different ways: an area-based approach and a volume-based one. For the former, the function relates available resource to planted area. For the latter, the function relates current the available resource to expected available resource. The expected available resource is then divided by the calculated average crop requirement to determine the planted area. Refer to the Source Scientific Reference Guide for more information.

For both area and volume based risk functions, you must specify the wet, average and dry periods. The model interpolates between these values based on an index of current conditions. For the area based method, the model automatically calculates the index based on soil moisture. For the volume based method, the index is calculated based on the defined inflow data as follows:

Inflow time series - Load the time series data if the risk function type is volume (Figure 6); or
Median prior 6-Monthly Inflow - Long term average inflows are entered as a monthly pattern. The volume based risk function uses an inflow index based on the supplied time series data. The index compares the total inflow from the time series file in the preceding 183 day period to the long term average for the same period.

Selecting the risk function type, and then clicking on either the Primary Crop or Secondary Crop button opens the Farmers Risk dialog (Figure 7).

Figure 6. Water User node (IQQM CropMod2, Risk)

Figure 7. Farmers' risk functions

Efficiency tab

This describes a number of parameters that can result in the water requirement being scaled up (Figure 8). Additional extractions are required if there is a practice of applying excess irrigation, with the excess being captured and returned to the water user storage. Additional extractions are also required if losses occur prior to delivery of extractions to the crop. The water user efficiency tab then allows these values to be scaled down. The default crop configuration values are zero, and hence if not defined, changing the water user efficiency parameters will have no effect.

Figure 8. Water User node (IQQM CropMod2, Efficiency)

The parameters are:

Irrigation return factor - Allows you to scale the on farm return factor defined through crop configuration. These two parameters combined, result in an increase in the volume ordered with the additional volume being available for returning to the water user storage;
On farm loss factor - Allows you to scale the on farm loss factor defined through crop configuration. On-farm loss represents the percentage of water that is diverted from the river and passes the irrigators meter, but doesn’t make it to the cropped area and doesn’t reappear at any other point. An on farm loss will result in the volume ordered being increased and is applied after the irrigation return factor; and
On farm escape factor - Allows you to scale the on farm escape factor defined through crop configuration. On-farm escape represents the percentage of diversions that is lost prior to being applied to crops however this flow returns to the river system at a confluence node. An on farm escape will result in the volume ordered being increased and is applied after the irrigation return factor and the on farm loss factor.

Return flow tab

Return drainage water is surplus drainage water from irrigation or from rainfall runoff. This water can be redirected into the on farm storage or otherwise can be returned to the river via a confluence node. This is shown in Figure 9. The various parameters are shown in Table 6.

Figure 9. Water User node (IQQM CropMod2, Return flow)

Table 6. Crop Model - Return Flow parameters

Parameter	Units	Description
Rainfall runoff scaling factor	%	The IQQM crop model includes a default rainfall runoff model and the scaling factor can be used to scale the runoff up or down. This factor should only be changed from 1.0 after careful thought, as it can impact irrigation demand calculations. If a factor greater than 1.0 is used runoff increases and infiltration is reduced. Similarly, if a factor less than 1.0 is used, runoff decreases and infiltration is increased.
Irrigation return water recycling efficiency	%	This defines the percentage of irrigation return water that can be either pumped into the water user storage for re-use (subject to storage and pumping constraints) or directed back to the river. You determine the proportion that is diverted to the storage through the ‘harvestable return flow’ parameter for the storage.
Rainfall runoff recycling efficiency	%	Percentage of rainfall runoff that can either be pumped into the water user storage for re-use or directed back to the river. As per irrigation recycling, the proportion that is directed to the storage is dependent on the ‘harvestable return flow’ parameter for the storage.
Tile Drainage (TD) parameters		The tile drainage function allows drainage to be defined in terms of a regression relationship with rainfall and irrigation. The amount of tile drainage is estimated as TD (mm/d) = TD coefficient+TD rainfall factor•sum of previous 30 days rainfall (mm)+TD irrigation factor•sum of previous 30 days irrigation

Crop mix tab

This tab (Figure 10) defines the proportions and timings of different crops planted in the defined area.

Figure 10. Water User node (IQQM CropMod2, Crop mix)

Browser not supported