Resource Fields
In Client > Resources tab, each resource has a set of fields.
The field set:
-
Defines the resource’s periodic availability, utilisation, and efficiency.
-
These fields influence the resource’s total operating time within the period – as well as its actual production rate used on a task within the period.
-
-
Defines the resource’s periodic rate factor.
-
This modifies its global or site-specific production rate across each period.
-
The field values are stored within the active calendar’s periods.
You manage a resource's set of fields in Client > Resources tab.
Time usage model
A resource includes a time usage model. It contains a series of fields that determine how the resource uses the time allocated to it within each period. A field is a measure of performance, such as the percent of the resource’s allocated time during which it’s available for use.
To define the rostered hours allocated to each resource, go to Rosters.
Fields
|
Field |
Description |
|---|---|
|
Availability |
The percentage of allocated/rostered time that the resource is operational or ready for use. An availability percentage below 100% could account for downtime, such as shift changes and repairs. |
|
Utilisation |
The percentage of allocated/rostered time that the resource is actively used to perform its assigned activities. Even if a resource is available, it might not always be in operation. Lower values may reflect operational delays or environmental constraints. |
|
Efficiency |
The percentage of how effectively the resource performs its assigned activities. It could be influenced by factors like fuel consumption, operator skill, and mechanical condition. |
Let’s say that Shovel1 has 10 rostered hours within a period. Of that time, it must be idle for 1 hour, accounting for shift changes and other idle time. In that case, its periodic availability should be 90%.
Calculating the actual allocated operating time
Availability, utilisation, and efficiency determine the total operating hours that can be allocated to a resource within a period. To calculate this, the software takes the rostered time and multiplies it by period’s time usage factors.
The calculation works like this:
Effective Utilisation = (Availability × Utilisation × Efficiency)
Operating Hours = Rostered Hours × Effective Utilisation
For example, in a given weekly period, a resource is rostered 40 hours:
-
Availability = 90% → 40 × 0.90 = 36 hours
-
Utilisation = 95% → 36 × 0.95 = 34.2 hours
-
Efficiency = 96% → 34.2 × 0.96 = 32.83 hours
Other fields
Other fields in the Resources table, which can affect how a resource’s actual production rate is calculated per period, are detailed below.
|
Field |
Description |
|---|---|
|
Rate Factor |
A factor applied to the resource’s nominal production rate for a specific period. It determines the entered rate, which is used to calculate the actual production rate. Refer to Production rate factor below for more details. |
|
Minimum Rate |
Depending on whether you’ve enabled variable dig rates (refer to Site Config > General and Calendar Settings), the software can reduce the production of a resource in an attempt to achieve quality objectives within a period. This property sets the lowest percentage at which a resource’s production can be produced. This value defaults to the setting in Config > Resources but can be adjusted per period. |
|
Resource Period Value |
Shown if you’ve enabled Resource Period Value in Site Config > Define site-level resources (and about and production rates). This property defines a periodic value per period. Depending on your needs, the value could represent the resource’s’ periodic production rate. These values can be referenced in the expression to determine the resource’s site-wide production rates (if used). |
Production rate factor
Each resource has a periodic production rate factor. It adjusts the nominal rate to derive the entered rate:
Entered Rate = Base Rate × Rate Factor
Depending on your setup, the base rate may be:
-
The nominal (global) production rate, or
-
A site-specific production rate (which overrides the nominal rate if defined in Site Config > Resources
Example – using the nominal rate
Nominal/global rate: 3,500 t/h
|
Resource Field |
P1 |
P2 |
P3 |
P4 |
|---|---|---|---|---|
|
Rate Factor |
90% |
80% |
70% |
100% |
|
Nominal Rate |
3,500 t/h |
3,000 t/h |
3,000 t/h |
3,000 t/h |
|
Entered Rate |
3,150 t/h |
2,800 t/h |
2,450 t/h |
3,000 t/h |
An example of how the rate factor uses the nominal rate to determine the entered rate. In this case, there is no site-specific override. An orange cell indicates that the nominal rate for that period was overridden. The rate considers any overrides (refer to Client > Build schedule using Gantt Chart (Gantt tab)) to determine the given period’s entered rate.
Example – using a site-specific rate
If a resource has a site-specific rate (defined in Site Config > Resources), the rate factor uses this (rather than the nominal one) to determine the entered rate.
|
Resource Field |
P1 |
P2 |
P3 |
P4 |
|---|---|---|---|---|
|
Rate Factor |
90% |
80% |
70% |
100% |
|
Nominal Rate |
3,500 t/h |
3,000 t/h |
3,000 t/h |
3,000 t/h |
|
Site-Specific Rate |
2,900 t/h |
2,800 t/h |
2,800 t/h |
2,900 t/h |
|
Entered Rate |
2,610 t/h |
2,240 t/h |
1,960 t/h |
2,900 t/h |
An example of how the rate factor uses the site-specific production rate to determine the entered rate.
In this case, the nominal rate isn’t used at all to determine the entered rate
More information
For further details on how production rates are configured and used—including nominal, site-specific, and actual rates—refer to Define site-level resources (and about and production rates).