TS Destinations, Steps & Constraints

Review the material transport rules.

Destination Logic

Destination Logic describes the resting place of material at the end of the period.

Sample Destination Logic.

Each rule lists the destinations for transactions that match its filter criteria:

• Period Filters may differentiate pre- and post- plant commissioning.
• Agent Filters may differentiate autonomous and crewed tipheads.
• Source Filters may differentiate ore and waste destinations by pit.
• Code Filters may differentiate destinations by some custom logic.

When an Agent generates a new schedule transaction, it reads through the Destination Logic list from top to bottom, and applies the first rule that satisfies all filters. This means that if two rules have overlapping conditions, only the first rule will ever execute for that set of conditions.

Overlapping Rules

Advanced users may occasionally create "nested" destination rules. This means a list of two or three rules with successively broader conditions, so that if the first condition is missed, then the second condition is evaluated, and so on.

Nested destination logic rules.

Note that each nested rule must contain ALL destinations for the nominated sources.You cannot spread the destinations across multiple rules, since only one rule is evaluated at a time. 

Tips

• Rules can be copied by holding down the Control key and dragging on the clipboard icon.
• Rules can be archived and shared via the save/import icons in the top right of the form.

Steps Logic

Steps Logic has two potential uses:

1. Convert a single schedule transaction into one or more final transactions (steps).
2. Assign the fleet to each final transaction.

For example. the schedule transaction "Pit to Crusher" can be split into "80% direct tip, 20% rehandle" with a different fleet for each movement.

Sample Steps Logic.

Each rule lists the Steps for transactions that match its filter criteria:

• Period Filters may differentiate changes in movement pathways.
• Agent Filters may differentiate autonomous and crewed fleets.
• Source Filters may differentiate ex-pit from rehandle fleets.
• Destination Filters may differentiate trucks that can use the overpass, or fit in the crusher bin. 

Note that the Destination Filter is only used to evaluate schedule transactions. To deactivate a destination, remove references to it from the Destination Logic.

Tips

• Between the pit and the waste dump, there is one (100%) pathway, trafficked by the production fleet.
• Between the stockpile and the crusher there is one (100%) pathway, trafficked by the rehandle fleet.
• Between the pit and the crusher there may be: 
  • One (60%) direct tip pathway, trafficked by the production fleet.
  • One (40%) stockpile pathway, trafficked by the production fleet.
  • One (40%) rehandle pathway, trafficked by the rehandle fleet. 
• If you type a field name (ie. myRatio)  instead of a number (ie. 40%) then this adds a row to the Calendar to change the ratios by period. 
• Rules can be copied by holding down the Control key and dragging on the clipboard icon.
• Rules can be archived and shared via the save icon and import icon in the top right of the form.

These rules can be used to split movement across multiple pathways and multiple fleets. 

Constraints

An Agent continues picking blocks in a period until halted by Dependencies, Fleet exhaustion, or Constraints on movement. 

Sample constraints.

An Agent action may be limited by the following constraints:

• Standard Constraint: limits the material sent to destinations from specified areas. (The Agent may still mine and send the material to alternative destinations.)
• Source Constraint: limits the material mined at the source, in the form of a Calendar table by pit, stage or bench. 
• Bench Advance Constraint: limits the vertical advance between the lowest elevation in the last period and the lowest elevation in the current period. 
• Drill Standard Constraint: limits drilling in one area. 
• Drill Source Constraint: limits drilling in multiple areas, in the form of a Calendar table by pit, stage or bench. 
• Agent Assignments: creates a table of loader assignment limits for each pit, stage or bench. (This option requires Loaders as Agents in order to be useful.)

If two constraints have overlapping conditions, the Agent will stop at the first limit.