| Table of Contents |
|---|
Overview
Haul Infinity has the ability to use actual travel time data captured by Fleet Management Systems in the Cycle Time calculations. Please note that Haul Infinity does not directly connect to an FMS database; the data must be imported into HI in a prescribed format. Haul Infinity requires spatial waypoint data as well as a lookup table that contains the travel times between FMS waypoints.
...
Importing FMS Waypoints
FMS points must be modelled as Waypoint nodes inside of Haul Infinity. The easiest option to import FMS points is to use Haul Infinity's Import > Nodes from CSV.
...
The schema for the waypoint import CSV is outlined below.
...
Header Name | Field Description |
|---|---|
POINT_NAME | FMS Point Name |
X | X co-ordinate of FMS point |
Y | Y co-ordinate of FMS point |
Z | Z co-ordinate of FMS point |
Node Type | Node Type of FMS Point (Waypoint) |
...
The calibration table contains the actual travel time data from the FMS database. Before importing the calibration file, it is essential to review the data to ensure that it is in the correct format. The schema for the calibration file is shown below.
...
Header Name | Field Description |
|---|---|
PRIMARYMACHINECLASSNAME | Truck Model - must match truck types defined in Haul Infinity |
START_POSITION_NAME | Starting FMS point name |
END_POSITION_NAME | End FMS point name |
DURATION | The travel time between the start and end FMS points, in seconds |
STATE | State of Truck -Full/Empty |
...
Haul Infinity uses the imported FMS waypoints in conjunction with the lookup table (".cali" file) which contains the travel times between the FMS points. As Haul Infinity encounters FMS waypoints along a haul segment, it will refer to the lookup table to see what is the furthermost FMS point it can "jump/hop" to. This process is repeated until the destination is reached. In the image below, the lookup table contains the travel time data for FMS_P1 → FMS_P2 and FMS_P2 → FMS_P3. Thus in both cases, the biggest "jump/hop" is one. For segments where FMS travel time data exists, the calculated segment times will be replaced with the FMS actual times. The overridden first principal times will be displayed in the Overridden Time column in the Segments tab. For segments where there is no available FMS data, the calculated time based on first principals will be used. In the example below, the time between FMS_P3 → FMS_P4 and onwards, will be calculated using first principals.
...
...
Note that in the .cali file, the duration is specified in Seconds and in the actual outputs in the Segments tab, it gets converted to Minutes.
If a time existed between FMS_P1 and FMS_P6 within the lookup table, Haul Infinity will use this time over the FMS_P1 → FMS_P2 and FMS_P2 → FMS_P3 times, as this is the biggest "jump/hop" it can make. The individual segment times between FMS_P1 and FMS_P6 will then be prorated based on the length of each segment.
...