...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
RU 🇷🇺
...
To understand the relationship between Loaders, Fleets and Agents, see also TS. Schedule Logic Overview.
| Table of Contents |
|---|
Overview
Loaders
| Tip |
|---|
A Loader is a tool that expends hours to deplete blocks. |
When, where, and how much it digs is determined by the Agent targets and Fleet assignments.
...
Some users may wish to exclusively link one Agent with one Loader (for reasons discussed in TS. Schedule Logic Overview). This can be done by ticking the Use as Agent option in the loader definition.
...
More detailed explanation on Use as Agent option for Loaders is given below.
Fleets
Fleets provide a means to switch between different truck-and-loader groups for given times, locations, materials and destinations.
Fleets deplete equipment in the order that they are listed.
Fleets are triggered by Agents via the Steps Logic.
Agents
| Tip |
|---|
An Agent is an entity that picks blocks, on behalf of one or more diggers. It reads the dependencies to get available blocks, and the incentives to rank them, then picks the highest ranked block. An Agent will continue to pick blocks during a period until stopped by Dependencies or Constraints. |
The output of a schedule is a list of schedule transactions which the Agents populates by selecting blocks to mine in sequence.
During each Scheduling Period, Agents choose blocks to be mined from the pit in the following order:
...
Schedule Transactions
To understand the relationship between Agents, Fleets and Loaders, the schedule transaction process needs to be reviewed.
| Tip |
|---|
A scheduled transaction is defined as moving an amount of material between a source and destination with a specific truck and loader. |
The basic steps in this process are reviewed below.
An Agent uses the user-defined Dependencies and Incentives to generate a ranked list of blocks to be mined.
With the highest ranked blocked selected, an Agent goes through the Destination Logic until it finds a rule that meets all of the criteria.
Once an Agent knows the source, material and destination, then it uses the Step Logic to look up the step(s) and fleet(s) for the transaction
The Step Logic rule will contain one or more "steps" from the original source to the final destination. Each "step" will be associated with a fleet.
An Agent goes through each "step" and picks the relevant loader/truck pairing with available hours remaining from the associated fleet.
The Agent queries Haul Infinity for a cycle time for the given source, material, destination, truck, and loader. Hours are then depleted at the dig rate for the specified truck and material.
This process is repeated for all the "steps" associated with the Step Logic rule.
...
Agents and Fleets logics
As an Agent executes schedule transactions, Fleets are triggered in the Step Logic component of the transaction. By default, the relationship between Agents and Fleets is a many-to-many meaning the Agent has access to multiple Fleets and a Fleet is able to be accessed by multiple Agents.
...
The configuration of the Fleets "Loader-Truck" pairings determines what Loader an Agent assigns to a movement. If a fleet comprises of multiple line items in its "Loader-Truck" pairings, then the Agent will deplete hours from the equipment in the order they are listed.
...
If there is one line item that contains multiple loader types and trucks, then there is no precedence, and the Agent will cycle the through the equipment in a round robin fashion.
...
Utilise the EX123 until it runs out of CAT785D hours
Utilise the SHV123 until it runs out of CAT785D hours
Utilise the LDR123 on all remaining truck hours
Once a Loader has been assigned to a movement, then its hours are depleted at the dig rate for the specified truck and material.
Loader as Agent
Sometimes we may wish to establish a one-to-one relationship between an Agent and a loader type so that an Agent can only ever represent one loader type, and a loader type can only be represented by one Agent.
Checking the Use as Agent option for a loader type establishes this relationship and results in a (bold, blue) linked Fleet and linked Agent being automatically added to the project whose name match that of the loader type.
...
The "Loader-Truck" Pairings of the automatically generated Fleet can only incorporate the loader type that it is mapped to. Mixed loader types are not allowed and you will be presented with an error which will prevent you from moving forward if this is detected.
...
| Info |
|---|
When using a Loader as Agent, the Enforced Matched Rates option overrides the Loader Rate with the Agent Rate (the Calendar overrides Haul Infinity in this case). A Loader as Agent in Optimised Products mode may return Overflow if the Agent Rate is higher than Loader Rate, since "1x loader target" is higher than "1x loader capacity". |
Using Product Optimisation short-cuts the capacity and time usage constraints, resulting in Infeasible Solution and Overflow warnings respectively.Раздел документации на русском языке 🇷🇺