Resource pricing

CLEM.Resources.ResourcePricing

Sets the price and transaction units for a given resource.

Any number of activities and reports will require the current financial value of a resource. Rather than assign this value with multiple activities, resource pricing is provided in a one location where the Resource type is defined. This means any activity can find and even modify the current price of the resource.

Not only is the value of a resource required, but we also need a description of how the resource is purchased and sold. For example, hay may be measured in kg, but transactions happen in 20 kg bales with the price set per bale.

Pricing a resource is performed by adding a Resource pricing component immediately below the Resource type. Separate versions of this component can be provided if different purchase and sale prices are needed.

Animal (including ruminants) pricing is provided by a special components (see Animal pricing).

The following parameters are used to define this activity

A packet is an amount of this resource that is bought and sold as a trade unit. The units of measure of the resource (e.g. kg, each, litres) are provided with the Resource type. This value determines how many resource units are in a packet. You can think of a packet as a box, bale, tonne, or any other grouping of a resource that is used for sales and purchases. All transactions with this resource will honour trading in these packets.

This switch determines whether transactions can only be performed using whole packets.

The price of a packet of this resource

The type of pricing to apply. The following options are available as the PurchaseOrSalePricingStyleType

This applies the same price to both purchases and sales

This represents a purchase price

This represents a sale price

The following components will add additional functionality to this component

This component respects all Timers allowing you to provide a number of different prices (i.e. multiple Resource pricing components) that will be used at different times during your simulation depending upon their associated timers. The range of timers available allows complex rules regarding pricing to be included in your simulation. A warning will be given if no current pricing is available when needed by an activity. The first Resource pricing in the list that is currently successful based on the associated timers will be used by an activity.

Example of timers and pricing. See sensibility process resource

See also