Routing Structure Overview

Routing Structure Explained

The routing structure defines the organization of container movements within a load. Each element in the hierarchy contributes to tracking, visibility, and billing accuracy, providing clarity on how container activity is organized and tracked throughout its life cycle.

Key Components

• Load
  A Load represents the full life cycle of a container, encompassing all moves from pickup to final delivery.

• Container Move
  A complete movement assigned to a driver.
  Example: Pick Container + Drop Container = 1 Container Move.

• Event
  An individual action within a container move.
  Example: If a driver picks up a container and drops it at the yard, this is counted as two separate events within one move.

• LEG
  The leg is the segment between two events, representing the active travel portion of a move.

• Status
  A timestamped record of specific stages within an event.
  Examples: Start, Arrived, Departed

Routing Hierarchy

The routing structure in PortPro follows a clear hierarchy, designed to provide visibility into every step of a container’s movement. Recent updates also introduce new terminology and expanded data fields to enhance clarity and operational insight. The hierarchy of routing components is structured as follows:

Container Move  
 └── Event        
    └── Status

The structure of routing in PortPro is organized as follows:

• Container Move
  The overall assignment given to a driver.
  • Event
    A defined action within the container move (e.g., Pickup, Delivery).
    • Status
      The timestamp capturing the driver’s interaction with the event (e.g., Arrived, Departed).

Terminology Updates and New Features

With the latest routing update, several naming conventions and new data points have been introduced:

• Pick Up Location
  Previously labeled as "Port." Now refers to the location associated with the Pickup Container event.

• Delivery Location
  Previously labeled as "Consignee." Now refers to the location associated with the Deliver Container event.

• Start Status
  Displays the exact time and date when the driver initiates the event in the mobile app.
  

• Arrived Status
  Captures when the driver arrives at the designated location.

• Departed Status
  Captures when the driver leaves the location.

Key Data Points

• Driver Pay
  Displays projected pay for the leg. This field is editable. Updates made here are reflected automatically in the Driver Pay tab. A rate source icon indicates whether the value is system-derived (e.g., Driver Pay Rates) or manually updated.

• Duration (Between Legs)
  Shows the time elapsed between the Departed status of one event and the Arrived status of the next event.

• Distance
  Displays the mileage between the locations of consecutive events.

• Duration at Location
  Measures how long the driver remained at a specific location, calculated between the Arrived and Departed statuses—useful for tracking detention.