An input path is a list of database records that represents the mining sequence for a resource. For each record in the input path, the following information must also be specified:
• | The percentage to schedule; |
• | The percentage of the next activity to ; and |
• | The destination (optional). |
In addition to database records, the input path may also contain in path delays. These are delays that will occur after particular records have been scheduled and they must therefore be defined in the input path rather than the roster, roster exceptions or period delays. Examples of in path delays include dead heading, planned maintenance and blasting. For an in path delay, the following information must be specified:
• | The delay duration in calendar hours. |
Input paths are stored as and the same path can therefore be used for many different resources or scenarios in your project.