TS. Report Fields (Glossary)
Field List
Take care that some fields are reported as averages, not sums.Â
For example, HaulageResult.Distances.Total will give the average cycle time distance, not the total distance travelled.Â
Field Name | Units | Aggregation | Field Description |
---|---|---|---|
ActiveDuration | Hours | Sum | If the Agent is active in a transaction, this field is equal to Duration. See also: Idle Duration. |
ActivityType | Text | - | Indicates Drilling, Mining, or Idle activities |
Agent | Text | - | The Agent that initiated this transaction |
AgentCalendarHours | Hours | Sum | Agent Calendar Hours consumed in this transaction |
AgentGroups | Text | - | When using Loaders as Agents or Drills:
|
AgentQuantityDividedbyCalendarTime.*** | Per Naming | Average | When using Loader as Agent, displays Agent target tonnes/volume divided by the Calendar hours |
AgentRate.DrillMetersPerHour | Meters Per Hour | Average | When using Drills, displays the drill penetration rate |
DestinationBlockType | Text | - | Reads the block type field (Production, Contour, Ramp, Trim, etc) |
DestinationFullName | Text | - | Full name of the material destination |
DestinationLogicRule | Text | - | Destination Rule used to assign the material to the destination. Can be found in Setup > Destination Logic. |
DestinationMutexStockpile.*** | Text | - | See Mutex Fields section below |
DestinationParcel | Text | - | Material type on arrival at destination.Â
|
DestinationRecordNum | Text | - | Unique identifier for each block in the project |
DestinationType | Text | - | See Source Type / Destination Type section below |
Destination.*** | Text | - | See Level Names section below |
Destination.Dumps | Text | - | Destination dump class
|
Destination.Name | Text | - | See Level Names section below |
Destination.Name Part *** | Text | - | See Level Names section below |
Destination.Top | Text | - | Destination dump class
|
Drill Engine Hours | Hours | Sum | Engine hours = calendar hours * availability * utilisation |
DrillHours | Hours | Sum | Direct Hours = calendar hours * availability * utilisation * efficiency * productivity |
Drilling_*** | Per Setup > Drilling Fields | Per Setup > Drilling Fields | Any drilling database field is prefixed "drilling_" |
Duration | Hours | Sum | Calendar hours
|
EndDate | Date/Time | - | End date of the transaction |
FinalDestination.*** | Text | - | See Source Type / Destination Type section below |
FlagCrossed.*** | Text | - |
|
FlagState.*** | Text | - |
|
Fleet | Text | - | Fleet name |
HaulageResult.BridgestoneTKPH | TKPH | Weighted Average on Number of Trips | Bridgestone TKPH value |
HaulageResult.DestinationTerminal | Text | - | Haul Infinity block or node representing the destination |
HaulageResult.Distances.*** | Metres | Weighted Average on Number of Trips | Distances corresponding to each cycle time component |
HaulageResult.FuelBurn.*** | Litres Per Trip | Weighted Average on Number of Trips | Fuel burn corresponding to each cycle time component |
HaulageResult.InstantaneousTruckCount | # | Weighted Average on Number of Trips | Instantaneous truck count on a given haul cycle |
HaulageResult.LoadedElevationChanges.*** | Metres | Weighted Average on Number of Trips | Absolute, Downhill, and Uphill loaded elevation changes for a given haul cycle |
HaulageResult.LoaderIdleRatio | % | Weighted Average on Number of Trips | Loader hang time as a percentage of truck cycle time |
HaulageResult.LoaderPayload | Wet Tonnes | Weighted Average on Number of Trips | Averaged loader bucket payload for the specified truck and material Can be found in Haul Infinity > Setup > Parameters |
HaulageResult.LoaderProductionRate.*** | Per Naming | Weighted Average on Number of Trips | Loader production rates in Tonnes/Volume per hour (Target tonnes/volume divided by actual Loader Hours) |
HaulageResult.Material | Text | - | Haul Infinity material type Can be found in Setup > Haulage Configurations > Haulage Materials |
HaulageResult.MichelinTKPH | TKPH | Weighted Average on Number of Trips | Michelin TKPH value |
HaulageResult.NumberOfPasses | Count | Weighted Average on Number of Trips | Number of swings taken by the loader to fill the truck tray |
HaulageResult.NumberOfTrips | Count | Sum | Number Of Trips = Mined Wet Tonnes/Truck Payload |
HaulageResult.SourceTerminal | Text | - | Haul Infinity block or node representing the source |
HaulageResult.Times.*** | Minutes | Weighted Average on Number of Trips | Productive time corresponding to each cycle time component |
HaulageResult.TruckPayload | Wet Tonnes | Weighted Average on Number of Trips | Truck payload in Wet Tonnes |
HaulageResult.TruckRate.*** | Per Naming | Weighted Average on Number of Trips | Truck production rates in Wet Tonnes, Dry Tonnes, and Bulk Cubic Metres per hour |
HaulageResult.UnloadedElevationChanges.*** | Metres | Weighted Average on Number of Trips | Absolute, Downhill, and Uphill unloaded elevation changes for a given route |
ID | Text | - | Unique ID for each schedule transaction |
IdleDuration | Hours | Sum | If the Agent is idle in a transaction, this field is equal to Duration. See also: Active Duration. |
Loader | Text | - | Loader type |
LoaderEngineHours | Hours | Sum | Engine hours = calendar hours * availability * utilisation |
LoaderHours | Hours | Sum | Direct Hours = calendar hours * availability * utilisation * efficiency * productivity |
Loader.Avails.*** | % | Loader Calendar availability, utilisation, efficiency, productivity value. Direct Utilisation =Â availability * utilisation * efficiency * productivity. Note these are weighted against Loader Hours, not Calendar Hours, as some stockpile reclaim steps consume loader hours but not calendar hours. | |
Mining_* | Per Setup > Mining Fields | Per Setup > Mining Fields | Insitu material properties such as feed tonnes and head grade |
Mining_ProcessStreams_* | Per Setup > Mining Fields | Per Setup > Mining Fields | Product material properties such as recovered tonnes and product grade |
Misc_* | Per Setup > Misc Fields | Per Setup > Misc Fields | Block solid properties such as location, surface area, presplit perimeter, etc |
MutexParcel.*** | Text | - | See Mutex Fields |
NumLoaders | Count | Sum | Num Loaders = Loader Hours/Direct Hours Per Loader |
NumTrucks | Count | Sum | Num Trucks = Truck Hours/Direct Hours Per Truck |
Origin ID | Text | - | Unique ID for each schedule transaction. |
OriginalSource.*** | Text | - | |
Output>*** | Per Setup > Mining Fields | Per Setup > Mining Fields | See Output fields |
Period.*** | Per Naming | - | Time period during which this transaction takes place |
ProcessingStream | Text | - | If the destination is a crusher, this returns the crusher Processing Stream. Can be found in Setup > Crushers |
SourceBlockType | Text | - | Reads the block type field (Production, Contour, Ramp, Trim, etc) |
SourceFullName | Text | - | Full name of the material source |
SourceMutexStockpile.*** | Text | - | See Mutex Fields section below |
SourceParcel | Text | - | Returns material type on mining transactions. Returns hole type on drilling transactions. |
SourceRecordNum | Text | - | Unique identifier for each block in the project. |
SourceType | Text | - | See Source Type / Destination Type section below |
Source.*** | Text | - | See Level Names section below |
Source.NamePart *** | Text | - | See Level Names section below |
Source.OpenPit | Text | - | Source mine class.
|
StartDate | Date/Time | - | Start date of the transaction |
StepLogicRule | Text | - | Step Logic rule used to assign the fleet to the movement. Can be found in Setup > Steps Logic. |
SwellVolume | LCM | Sum | Swell factored volume. Can be found in Setup > Swell Factors. |
Truck | Text | - | Truck type |
TruckEngineHours | Hours | Sum | Engine hours = calendar hours * availability * utilisation |
TruckHours | Hours | Sum | Direct Hours = calendar hours * availability * utilisation * efficiency * productivity |
TruckTotalFuelLiters | Litres | Sum | Total truck fuel litres |
Truck.Avails.*** | % | Truck Calendar availability, utilisation, efficiency, productivity value. Direct Utilisation =Â availability * utilisation * efficiency * productivity. Note these are weighted against Truck Hours, not Calendar Hours, as some stockpile reclaim steps consume truck hours but not calendar hours. |
Original Source/Final Destination
A single schedule transaction (Source + Destination) may be one step in a series of transactions generated by the Steps Logic. "Original Source" and "Final Destination" refer to where the material originated at the beginning of the period and rested at the end of the period, outside of the current transaction.Â
Example:
Destination Logic | Steps Logic | |||
---|---|---|---|---|
Original Source | Final Destination | Step | Source | Destination |
Pit | Crusher | 1 | Pit | ROM |
Pit | Crusher | 2 | ROM | Crusher |
Pit | Crusher | 3 | Pit | Crusher |
Be extremely wary of double-counting when using Original Source/Final Destination fields.
Observe from the above image that filtering by "Final Destination = Crusher" would double-count tonnes passing through the ROM.Â
Source Type/Destination Type
A single schedule transaction (Source + Destination) may be one step in a series of transactions generated by the Steps Logic. See the illustration above.
Field | Value | Condition |
---|---|---|
Source Type | True | Source = Original Source |
Source Type | False | Source <> Original Source |
Destination Type | True | Destination = Final Destination |
Destination Type | False | Destination <> Final Destination |
The "Type" fields can be used to quickly differentiate between Direct (single-step logic) and Auto-Rehandle (multi-step logic) type movements.Â
Output Fields
Output fields display the final products grades when a parcel is dumped in the crusher. Any reporting on final product should be done using the Output fields.Â
To prevent double-counting, always filter by Destination.Dumps = Crushers when reading the Output fields.Â
Output grades are displayed on any transaction where the Final Destination is a crusher (even if the Destination is only the ROM, per Steps Logic).Â
Mutex Fields
Mutex fields (Mutually Exclusive categories) are classification fields that have been created in Tactical Scheduler,
in Reserves tab > Data panel > Parcel Subsets field > gear icon > Mutex Parcel Groups section, and
in Setup tab > Stockpiles step > Stockpile Mutex Subsets.
These are useful for answering questions such as "how many tonnes on all ROM stockpiles" or "how many tonnes of rock type X went to crusher". Under the Mutex groups we can classify different ROM stockpiles together, or different rock types together, and so on.Â
See also:Â TS. Subset Variables.
Level Names
Tactical Scheduler uses Level Names to refer to the hierarchy of locations in pits, dumps, stockpiles and crushers. By default, the level name fields are drawn from the table levels in Setup > Create Tables.Â
This can be a source of confusion, since Dumps, Stockpiles and Crushers levels store different information at different levels in their names.Â
Destination Level | Destination Name Part | Level Number | Dumps | Stockpiles | Crushers |
---|---|---|---|---|---|
Destination.Dumps | Destination.NamePart1 | 0 | "Dumps" | "Stockpiles" | "Crushers" |
Destination.Mine | Destination.NamePart2 | 1 | "Mine1" | "ROM1" | "CR1" |
Destination.Dump | Destination.NamePart3 | 2 | "Dump1" | "WtAvg" | - |
Destination.Lift | Destination.NamePart4 | 3 | "600" | - | - |
Destination.Block | Destination.NamePart5 | 4 | "001" | - | - |
Destination.Top | Destination.NamePart1 | 0 | "Dumps" | "Stockpiles" | "Crushers" |
Destination.Name | Destination.NamePart2 | 1 | "Mine1" | "ROM1" | "CR1" |
Pits
Destination.<Level> returns that level name from the OpenPit database table.
Dumps
Destination.<Level> returns that level name from the Dumps database table.
Stockpiles
Destination.Top returns "Stockpiles" from Level 0.Â
Destination.Name returns the stockpile name from Level 1.Â
Destination.NamePart3 returns
the finger number on FIFO/LIFO stockpiles.
"WtAvg" on weight-averaged stockpiles.
Crushers
Destination.Top returns "Crushers" from Level 0.
Destination.Name returns the crusher name from Level 1.Â
Equivalent Flat Haul
Contact Alastri support to add Equivalent Flat Haul (EFH) as a custom report field to your organisation's specification.
Since there is no industry standard defined calculation for EFH, it is not included in the default reporting fields.