✅ Released


2.1.4 - 01/17/23

Core

LP Control Tower - Stop Status

Enhanced Route visibility through colored-coded "Stop Statuses". The statuses will allow an LP Delivery Manager to quickly understand the progress of a route and any issues that may arise at the individual stops. The different Status possibilities are:

  • En Route
  • Arrived
  • Completed
  • Incomplete
  • Partial


LP Control Tower - Revoke Timer

Fixed issue where the revoke timer for some deliveries will show as 0 min, even though the delivery had been recently assigned. This issue was only affecting the visibility of an accurate revoke timer and was not affecting the actual time that LPs have to assign a driver.


Fixes and Improvements

  • Updated the MDP Bot to Include the following Delivery States:
    • Arrived for Pickup
    • Arrived for Delivery
  • Labels Updated to Display Individual Container Weight


2.1.3 - 01/12/23 

Reporting

Enhancements

General stability improvements and performance enhancements related to loading times in CORE's Reporting tab. Unused reports were archived to improve capacity consumption as part of a Data-Cleanup initiative.


Fixes and Improvements

  • Delivery Date/Time Updated to Match Backend Returned Object
  • LP Configuration Error Message

2.1.2 01/10/23

Core

Map New Role to 'Driver' Role

New contract drivers have their own mapping that needed to be mapped to the existing "Driver" role in OneRail's staging and UAT environments so testing could be done before enabling these drivers in OneRail's production environment.


Risk Calculation Enhancement

Enables users to receive a more frequently calculated Risk factor in the different stages of the delivery process. The Risk formula has been strengthened to support multiple calculations depending on the status of the delivery, while continuously accounting for the time consumed by that specific SLA.



Consolidated Pickups in Routes

Users will now have better visualization of routes in the Control Tower. They will be able to see the IDs for all the orders being picked at the same location or at the same geographical stop. This will enhance tracking and overall visibility for users that utilize the Routing feature.


Reporting

Enhancements

General stability improvements and performance enhancements related to loading times in CORE's Reporting tab. Unused reports were archived to improve capacity consumption as part of a Data-Cleanup initiative.


Cost Per Stop Routes Report

Client specific reporting has been updated to calculate the cost of the route per each unique delivery location instead of the cost per each unique delivery. The report now calculates and outputs the cost of the route based on the individual delivery location regardless of how many deliveries are being fulfilled to that location.


Integrations

Pickup and Dropoff Accessorials Now Available for LPs 

Pickup and Dropoff Accessorials have now been mapped in LP transform and can be passed to LPs after configuration with each LP integration. The flag is currently off in Production.


Fixes and Performance Improvements

  • Auto-Revoked Orders Not Resetting to 'Draft' Status
  • 'Draft' Pickup Task Removed from "Control Tower"
  • Combined Certificates for MySQL Single Server
  • Improved Error Handling for Delivery API
  • Database Performance Improvements
  • Fixed Order ID Link Redirect from Control Tower
  • General enhancements to improve reports
  • Mobile (ORD) Improvements - Version 19.1



? Coming Soon


Core

LP Ranking Enhancements

OneRail's algorithm to calculate the best Logistic Provider (LP) for delivery selection has several enhancements coming up:


  1. The current implementation of how data is fetched for LP ranking is calculating deliveries that are in terminal states as 'in flight'. Deliveries in these states are now excluded from the calculation. Additionally, the calculation used for SLA Met was updated to only look at completed deliveries in SLA time.
  2. The calculation is being updated to only reference 'Final Mile' delivery modes when weighting and selecting an LP.


LP Control Tower - Stop Status

Enhanced Route visibility through colored-coded "Stop Statuses". The statuses will allow an LP Delivery Manager to quickly understand the progress of a route and any issues that may arise at the individual stops. The different Status possibilities are:

  • En Route
  • Arrived
  • Completed
  • Incomplete
  • Partial


LP Control Tower - Revoke Timer

Fixed issue where the revoke timer for some deliveries will show as 0 min, even though the delivery had been recently assigned. This issue was only affecting the visibility of an accurate revoke timer and was not affecting the actual time that LPs have to assign a driver.


LP Control Tower - Driver Interactions

Users will have the ability to click/hover on the Driver's avatar on the map and obtain information about the specific driver:

  • Driver Name
  • Vehicle 
  • Number of Deliveries Assigned
  • Phone Number

GeoFencing for Locations

Locations will have a 0.25-mile geofence to better track when a Driver arrives at a location, how long the driver is at the pickup location and the delivery location, and determine if a driver is in a Market.  This includes the following "Location" types:

  • When a driver's geolocation is within 0.25 miles of the geofence of the pickup location, the order's status will be changed from 'En Route to Pickup' to 'Arrived for Pickup'. 
  • When a driver is in the 'Arrived for Pickup' status and their geolocation moves outside of 0.25 miles from the pickup location, the order's status is changed to 'En route to delivery'.
  • When a driver's geolocation is within 0.25 miles of the geofence of the dropoff location, the order's status will be changed from 'En Route to Delivery' to 'Arrived for Delivery'. 
  • When a driver is in the 'Arrived for Delivery' status and their geolocation moves outside of 0.25 miles from the dropoff location, the order's status is changed to 'Delivered'. 


Contact Email Address to Locations Information

Contact email addresses can be added to individual locations.


Email Notification When "Long Wait At Pickup" Exception is Triggered

When the exception "Long Wait at Pickup" is logged at a location, a notification will be sent to the contact email address (if there is one) for that location to inform. This was requested by a specific client for them to be alerted of what order and the item(s) are impacted so that they can remedy these issues internally.


Create Orders with Accessorials

When creating an order through the "Add Order" form, accessorials will be added to orders providing better insight into what is required to complete this delivery.


Fixes and Improvements

  • Redirect LP Ranking to the new Cosmos microservice library.
  • Update Orders Endpoint to Use new Microservice