Open topic with navigation

You are here: Setup Schedule > About > Material Flow > Haulage > Importing Haulage from an Existing Scenario
GEOVIA MineSched

|  | Print

# Importing Haulage from an Existing Scenario

When you open a scenario in MineSched 9.0 that was created in MineSched 8.0, 7.1, or 7.0, the haulage route definitions in the existing scenario are imported.

In versions of MineSched before 9.0:

- haulage routes were defined using Surpac string files
- you could define multiple strings, and strings with multiple segments, for the ramps and benches of each haulage route
- you could assign only one haulage route to each material movement rule

When the scenario was run, for each block, MineSched would use the ramp haul path strings and bench haul path strings of the haulage route that returned the shortest distance from source to destination.

In MineSched 9.0 and later:

- haulage routes can be defined using a geometry from a range of source files
- every haulage route must be a single complete path (from the source to the destination, and back)
- you can assign multiple haulage routes to each material movement rule

The shortest haulage distance is still calculated and used for each block. However, instead of selecting strings or segments of a single haulage route, MineSched selects the shortest route from a selection of routes.

When you open a MineSched 8.0, 7.1, or 7.0 scenario in MineSched 9.0, the function of each ramp and bench in your haulage route definitions remains the same. However, the layout of the haulage information is different. For each segment of each ramp string that was part of the existing scenario, an individual haulage route is created in MineSched 9.0.When you open an existing scenario that contains haulage definitions:

- the haulage geometry is imported to MineSched in ramp and bench haulage collections
- the ramp and bench geometry is then combined to create a haulage route for every combination of ramp and bench geometry
- the haulage routes that are created are associated with the appropriate material movement

Note: For scenarios that have multiple strings, or strings with multiple segments, defined for haulage, the Haulage column of the Material Movement data grid is filled with the name of each haulage route created from the strings and segments.

- the velocity associated with the existing haulage routes is imported and applied to the new haulage routes

Note: In MineSched 9.0, changes in velocity for ramp haulage paths are defined at distances along the path and not at points in the ramp segments. When the velocities are imported, the point coordinates are used to calculate the distance along the path at which the velocity change occurs, and the distance is displayed in the Velocities data grid.

- the truck definitions are imported

Note: Truck definitions do not change in MineSched 9.0.

### Example

In an existing scenario with a haulage route called HAUL_TO_PIT defined using the file haulage.str which contains ramp geometry in strings 1, 2, and 5, and bench geometry in strings 10 and 11, the following is imported to MineSched 9.0:

- ramp collection HAUL_TO_PIT_imported, containing a line for each segment in string 1
- ramp collection HAUL_TO_PIT-2_imported, containing a line for each segment in 2
- ramp collection HAUL_TO_PIT-5_imported, containing a line for each segment in string 5
- bench collection bench_HAUL_TO_PIT_imported, containing a line for each segment in string 10
- bench collection bench_HAUL_TO_PIT-11_imported, containing a line for each segment in string 11

Haulage routes are then created by combining the ramp and bench collections. In this example, the following haulage routes are created:

- HAUL_TO_PIT, which uses ramp collection HAUL_TO_PIT_imported, to define the full and empty ramp paths, and uses bench collections bench_HAUL_TO_PIT_imported and bench_HAUL_TO_PIT-11_imported, to define the bench paths.
- HAUL_TO_PIT-2, which uses ramp collection HAUL_TO_PIT-2_imported, to define the full and empty ramp paths, and uses bench collections bench_HAUL_TO_PIT_imported and bench_HAUL_TO_PIT-11_imported, to define the bench paths.
- HAUL_TO_PIT-5, which uses ramp collection HAUL_TO_PIT-5_imported, to define the full and empty ramp paths, and uses bench collections bench_HAUL_TO_PIT_imported and bench_HAUL_TO_PIT-11_imported, to define the bench paths.

The material movement rule, in the Material movement data grid, references HAUL_TO_PIT, HAUL_TO_PIT-2, and HAUL_TO_PIT-5, so when the scenario is run all three haulage routes are used. This means that there should be no change in values for the haulage results.

Tip: You can use wildcard expressions when you associate haulage routes with material movement rule. For this example, to make the haulage column of the Material Movement data grid and material movement reports easier to read, you could replace HAUL_TO_PIT, HAUL_Y_PIT-2, and HAUL_TO_PIT-5 with HAUL_TO_PIT*.

### See also

- Open an Existing Scenario
- Haulage Routes
- Truck Types
- Material Movement

Open topic with navigation