Introduction

This document provides a guide on how to configure transportation-related policies in the One Network system.

Configuring Transportation Related Policies

1. Log on to the One Network system.
2. Navigate to Transportation > Policies. Three options are available: Tracking Event Policies, Execution Policies, and Distance Policies.
   

Configuring Tracking Event Policies

1. Navigate to Transportation > Policies > Tracking Event Policies.
2. The Tracking Event Policies page is displayed. There are two tabs at the top of the screen: Movement Events and Shipment Events. The Movement Events tab lists tracking events that are available at the movement level, and the Shipment Events tab lists the tracking events that are available at the shipment level.
   
   
   

3. To display the tracking events in the list of available tracking events at the movement level and shipment level, set the checkboxes under the Active column by each required tracking event.

   This will be the list of tracking events shown when the user selects the Create Tracking Event button on the Movement Tracking or Shipment Tracking screen.

   
   
   

   The One Network system comes with a group of predefined tracking events.

4. Click New to see the list of system-provided tracking events. 
5. Open the Create Movement Evt Config page or the Create Shipment Evt Config page. 

6. From the Event Type drop-down list, select Standard Event Type.

   The field next to this will then have a drop down list of the system-provided tracking events. When selecting one of these events from the drop down list, the fields for this event will be displayed if they are required by the system or not. If a field is required by the system, the user cannot make it optional. To configure the field to be displayed or not, select or deselect the check box for that field name under the Active column.

   For a system-provided tracking event, the user can define if they want a non-required field to be required by selecting the checkbox next to that field name under the Required column.

   The user can configure the fields for a tracking event by Partner Type. To define the Partner Type, select one of the options from the Target Groups field drop-down list.

   The user can create custom tracking events and configure the required and optional fields for different partners. These custom tracking events are meant to be information only, and they will not execute any business logic when selecting an event.

7. To create a custom tracking event, click New.
   
   

   The Create Movement Evt Config page is displayed. If you click New from the Shipment tab, the Create Shipment Evt Config page is displayed.

   
   
   

8. From the Event Type drop-down list, select the Custom Event Type, and enter a name for the custom tracking event in the text field next to the drop-down list. 
9. From the Target Groups drop-down list, define who can view and operate on this custom tracking event. Options include "My Organization", "Carrier Partners", "Customer Partners", "Supplier Partners", "Carrier and Customer Partners", "Carrier and Supplier Partners", "Customer and Supplier Partners", "All Partners", and "All". 
10. Select the required fields for this custom tracking event by clicking the respective check box under the Active column. For required fields, click the necessary fields under the Required column.

11. Click Submit to create the custom tracking event.
    
    

    A movement or shipment tracking event can be configured to raise an Exception Request in response to that event occurring. These Exception Requests can then be used by the Transportation Controlling Organization and the carrier to capture details that justify the deviation from the standard, expected process.

    Exceptions are events that occur based on which carrier requests an exemption, so that the carrier is not penalized accordingly. To associate an Exception with a movement or shipment event, the user must create an Exception Code and then associate that code with a specific movement or shipment tracking event under the Tracking Event Policies page. Once that tracking event is submitted by the carrier, the associated Exception will be raised to check whether the hub can approve or deny the carrier's exception request. An Exception can go through various states, which include: Pending, Approved, Denied, Deferred, and Appealed. Once a carrier Exception is raised, it will start in the Pending state. The Hub can approve or deny the Exception which will move it to the Approved or Denied state. Denied Exceptions can be viewed by the carrier, who can appeal the denied Exception – these appealed Exceptions would move to the Appealed state. Exceptions are viewed by the carrier on his dashboard using the Exception Request Summary portlet. A hub can defer looking at the Exception until a later time – these deferred Exceptions would be moved to the Deferred state.

12. To create an Exception Code, navigate to Administration > Codes > Exception Codes.
    
    
    
13. On the Exception Codes page, enter the name for the exception in the Exception Code Name field and click Add.
    
    
    
14. To associate an Exception Code with a tracking event, navigate to Transportation > Policies > Tracking Event Policies.
15. To define a tracking event to raise an Exception Request when that event occurs, select the checkbox for Debrief Exception for the specific event and enter the Exception Code under the Exception Code column. 

16. Click Save to save this setting. This can be defined for a tracking event at the movement level using the related tab, or at the shipment level by using its related tab.
    
    
    

    When this exception-defined tracking event is added by the carrier, an exception will be raised. The hub can view these exceptions by navigating to Tools > Exceptions > Pending. The hub can also view exceptions by state by navigating to Tools > Exceptions > State Summary or by navigating to Tools > Exceptions > Search Exceptions.

    
    
    

    For pending exceptions, the hub can either approve the exception, deny it, or defer it to a later time. The carrier has a similar view of these exceptions and can view exceptions that the hub denied. The carrier can appeal denied exceptions. The hub can see these exceptions under the Appealed state.

    The following screenshot shows a pending exception that was raised when the carrier added a delayed tracking event at the movement level. Select the link exception number under the Detail column to go to the details of the exception in order to perform an action.

    
    
    

    On the Exception Details page, the Hub can select an action such as Approve or Deny. The Hub can also add a comment that can be viewed by the carrier by using the Add button in the Comments section. To save the comment, click Add Comment, which is at the bottom of the page.

    
    
    

17. After you complete one of the actions, the state of the exception will change accordingly.
    

Configuring Execution Policies

1. To configure execution policies, click Transportation > Policies > Execution Policies.

2. The Execution Policies page is displayed.
   
   
   

   On the Execution Policies page, if Allow Delivery only after Pickup is set, a pick-up action has to occur on a movement or shipment prior to performing a Delivered or Ready for Delivery action.

3. To set this policy, click the Allow Delivery only after Pickup checkbox and click Update. A success message is displayed.
    
   
   
4. With this policy set, if the user tries to perform a Delivered or Ready for Delivery action prior to a pickup action, the system will display an error message stating "Delivery/Delivery Ready action cannot be performed without Pickup action".

Configuring Distance Policies

1. To configure distance policies, click Transportation > Policies > Distance Policies.

2. The Distance Policies page is displayed.
   
   
   

   The Distance Polices page allows the user to customize the distance calculations for the system to use based on shipment and movement characteristics. For example, the user can add rules to specify that all hazardous shipments should use practical route mileage, even when the default mileage is computed using the shortest route. At the top of the page, the default settings are defined. These are required fields. The fields include: Default Distance Source, such as "PC Miler" or "Mile Maker", Default Distance Type, such as "Practical" or "Shortest", and Default Location Basis, such as "City-State, "Zip/Postal", or Lat-Long".

   PC Miler and Mile Maker are third-party tools that the system uses to calculate postal-code-to-postal-code distances in the United States, Canada and Mexico.

   
   
   

   Under the Distance Policy Overrides section, the user can set override settings based on equipment, commodity code, "From (Country)", "To (Country)", hazard class, "Over Dimension" (Y/N) and "Over Weight" (Y/N), followed by the corresponding Distance Source, Type, and Location Basis.

3. To create a Distance Policy Override setting, click the Add link and enter information in each of the required fields.

   Editable fields are marked with a pencil symbol.

   For each of these override settings, the user also needs to specify its priority. Priority numbers must be unique (for example, 1, 2, 3, and so on, with 1 being treated as the highest priority). If multiple overrides apply, the system uses the one with the highest priority. Not all of these settings need to be entered. The user may leave any setting blank.

   
   
   

4. Once the information is entered, click Save to save the default and override settings.