Events are discretely triggered at a certain thresholds of activity

Events are triggered by the accumulation of activity until a threshold is reached, such as a maintenance event or recruitment of new operators. They are similar to Variable components but occur only after a cumulative quantum of the Time Based Input. Common examples are maintenance costs where a maintenance task is triggered by the number of hours or tonnes or km's the truck accumulates.

There are three inputs required for an Event:

  • The Event Rate (per event)

  • The Event Frequency (the threshold)

  • The Activity (to accumulate)

These inputs will be used to determine the number of times the Activity will reach the Event Frequency threshold and trigger the Event Rate.

There are two two optional inputs:

  • The Starting Balance

  • The max number of event triggers

If the starting balance is used it is assumed events will have already occurred given the provided frequency. The remaining balance will be added to the activity for period 1.


A common example of event costs are maintenance costs that occur at

The example below is for a 18000 km service where $930 is incurred every 18000 km travelled. For the periods shown the was no event in the first period and one event in each of the following two periods. The Event Activity accumulates forward through the periods until the frequency threshold is reached.

Last updated