Manage crop product

CLEM.Activities.CropActivityManageProduct

This activity manages a single product produced from a crop.

Each product produced from a crop requires a Manage crop product activity with optional associated crop tasks and crop fees. This is because each product may have a different harvest date and range of tasks involved in preparing and harvesting. As noted in Manage crop activity each Manage crop product could relate to a different plant being grown in a mixed or rotation cropping system, or merely two products from the same crop (e.g. grain and residue).

The following parameters are used to define this activity

This parameter points to one of the defined Crop files added to the simulation tree and currently available for this simulation. This entry is a drop down list of available Crop files.

The name of the crop in the data file is required to locate data and harvest dates from the Crop File.

This parameter points to one of the defined Resource stores of the Resources available for this simulation. This entry is a drop down list of available Animal food stores, Graze food stores, Human food stores or Product stores.

When a Graze food store type is selected to represent pasture the area of this crop (from parent Manage crop) will be used to define any initial pasture biomass specified in the Graze food store type component.

This represents the proportion of the product reported as harvested in the Crop File that is harvested. This allows for inefficiencies in harvesting or even reducing the crop yield when undertaking mixed cropping.

It is recommended that mixed and rotation cropping are considered in the creation of input data is a crop model is being used. This option allows for a reduction of the crop yields provided.

This represents a modification from the area requested by the parent Manage crop such that each rotation crop can have an adjusted area planted. This change in land requirement will cause transactions with the Land resources and is subject to land being available. When a crop area reduction returns land resources it cannot be guaranteed that the land will be available for a future land increase and the other crop my be constrained by area planted.

This feature is not valid if you have selected Use available land from the parent Manage crop and will generate a validation error.

This feature is not valid for mixed cropping style and will generate a validation error.

This parameter determines the number of trees planted per hectare if a tree crop is required, and in turn whether this is a tree crop by providing a value greater than 0.

This parameter will determine what action is taken if there are insufficient resources to perform this activity.

You can report an error and stop the simulation, skip this activity or use the resources available. See What to do when resources are limiting

The following components will add additional functionality to this activity

This activity provides the following units for components: fixed, per kg harvested, per ha and per ha harvested

This activity will handle harvest tasks and you can use Activity fee and Labour requirements below to provide needed resources for harvest. Additional crop tasks (e.g. irrigation and planting) will need Crop task activity and associated fees, labour requirements and Crop harvest timer. You can also use a custom Crop task activity for harvest but you will not include fees and labour here or they will be accounted for twice.

This will add a task associated with the production of this product. Crop tasks can have a Labour requirement and crop fees associated with them. There is no limit to the number of crop tasks and these can be used to identify the use of labour in transaction ledgers and output. Crop tasks include activities such as preparing the field, planting, weeding, irrigating and harvesting each with a number of costs (e.g. seed purchase with planting task).

Any Activity fee will include financial costs based on any specified identifiers and units and may limit the outcomes if supported and OnPartialResourcesAvailableAction set to UseAvailableWithImplications

Any Labour requirement will include labour allocation to perform this activity based on any specified identifiers and units and may limit the outcomes if supported and OnPartialResourcesAvailableAction set to UseAvailableWithImplications.

A Carry limiter added to the simulation tree (anywhere within the Activities holder) will limit the amount of material that can be moved by Cut and carry based activities from the crop to stores in a time step. See Limiters.

This activity is performed during the Get Resources Required event of the setup and time-step events. This is the standard, monthly clock event by which CLEM activities request resources and perform actions based on the resources provided, therefore this activity will compete with most activities in the time-step with their location in the simulation tree determining the order they are processed (this includes activities located on other CLEM and Market components). If this activity relies on another activity having been performed, or other activities rely on this activity in the time-step, ensure it has been performed in the correct order based on it's position in the simulation tree.

The timing and actions ultimately depend upon the harvests provided by the crop input file and any activity-timers used.

The reason this general timer is used is to ensure labour can be allocated between competing tasks (e.g. crop versus herd management).

See also