In TransVirtual there is the ability to setup Linehaul Routes which are a set of pre-defined routes that any Linehaul freight may take.
Linehaul Routes are typically depot to depot runs and are created using zone list data from the below field:
The zone list being used can be found and changed under Configuration > General > Global Setup, on General tab, go to Zone Directory Mapping section.
If changing to a new list, do so with caution!
To see the Linehaul Routes page, go to Configuration > General > Linehaul Routes, this article will detail how to setup the Linehaul Routes.
This will additionally limit the available linehaul route combinations on the users mobile application to those configured when setup.
1. To add a new rule, first go to linehaul route page as shown below.
2. Now click on Add Route button, a popup for create a new route will display as shown below.
3. Select a Zone from and a Zone To and then click the Save button to create this Route.
4. The Route will appear in the Route table list as shown below.
You can import a Linehaul Route list using the Import Route Table List option seen when creating a new Route. If importing a list, you will need the below columns in your csv file:
The zones specified in the file should match what are listed in your Route/Scan/Agent Zone List.
5. Once you have created a Linehaul Route, click on it and you will see the settings for it appear on the right side of the page as shown below.
Route Detail
This section is used to configure the Route, to do it refer below steps.
a. Route Name: This is the name applied to the Route. The name should be reflective of the from and to zones for this Route.
b. Headport From and Headport To: These shouldn't need to be changed as they are populated when you create the Route. However, if required, you can change the values in these fields to be the from and to zones for the Route.
c. Valid Headport Scan Locations: This section is used to apply a series of Headport scan locations that are valid for this Route.
For Example: Any freight going from Brisbane > Melbourne may stop in at Sydney and get scanned and processed there before heading to Melbourne. Adding Sydney as a valid Headport scan means that when Linehaul freight travelling from Brisbane > Melbourne, gets scanned at Sydney, the user scanning at Sydney will not get an error of possible misdirected freight.
1. This concept will only work if the below setting is enabled in the global setup page as shown below.
To go to Global Setup page, click on Configuration > General > Global Setup and refer scanning section.
2. Once you enable this setting, any mobile users scanning freight at a location other than those listed as valid headport scan locations will receive a message on their device to say the freight may be misdirected. This is handy to ensure freight does not accidentally travel in an incorrect direction.
3. The Headport locations that display for this field will be derived from the below list as shown below.
To see the Zone Directory Mapping section, refer global setup page and scroll down the page and see the Zone Directory Mapping section.
d. Valid Agent Scan Locations: This setting is used to specify what agent scan locations are valid for this Route. Typically speaking, an agent of yours will only operate out of the one depot/headport.
For Example: In the above screenshot,
Matt Agent Services operates out of Singleton and NSW. Setting Matt Agent Carrier as a Valid Agent Scan Location means that when a user for this agent scans some Linehaul freight travelling from Brisbane > Sydney, they will not receive a misdirect message on their device. If another agent user from another location was to scan this Linehaul freight, they would receive a misdirect error message. This field is similar to the Valid Headport Scan locations field in that it allows you to specify allowable scan locations for this Linehaul Route - anything scanned outside of the valid scan locations will receive an error message.
The values that appear in this field are the agent names in your account.
Setting up a Linked Linehaul Route
1. The above section has detailed how to create a standard Linehaul Route. There is also the ability in this page to create a Linked Linehaul Route which is an 'over-arching' Linehaul leg containing smaller Linehaul legs.
For Example: You may have Linehaul leg of Brisbane > Perth. For this leg however, the actual journey that is taken may be Brisbane > Sydney, then Sydney > Melbourne, then Melbourne > Adelaide, then Adelaide to Perth.
Creating a Linked Linehaul Route is way to create one overall Leg that encompasses smaller legs within; doing so means that any included legs are valid scan locations that ensure freight is travelling in the right directions.
To do this the setup is much the same as the above method.
2. Click on the Add Route button and a pop-up for create a new route will display as shown below.
3. Select the Zone From and Zone To with the help of drop-down button.
4. Click on the Toggle button in Yes position to link the linehaul route as shown above, and then click on Save button to save the changes.
5. Once you completed above steps, the Route will then create and appear in the list with a Y in the Link section as shown below.
6. Now click on the newly added route, the detail of that route will be display on the right side of the screen as shown below.
7. At the bottom of the page, there is the ability to Add Route Link as shown below.
8. Click on the
Add Route Link, a pop-up for
Create a new route link will display as shown below.
9. Using the drop-down, select any existing Linehaul Routes that form a leg of this linked Linehaul Route and then click on
Save button to create and add.
10. Once you completed above step, then you will see the added leg appear in the Route Links grid as shown below.
11. In the above screenshot,
Brisbane >
Sydney is now a leg or part of
Sydney >
Perth. You could then add in the other legs that form part of the
Sydney to
Perth journey.
Transit Times and Transit Time Details
For information on how to set these sections up please refer
here to be directed to the Transit Times article.