Build Lane Summary

Note: Prior to running the Build Lane Summary action, run the Fill Missing Lanes action so that any shipments that came over to the Oracle Transportation Sourcing without an assigned rate lane will get an assigned lane.

Note: Do not run this action if you have manually uploaded your lane summary as running the Build Lane Summary action will replace your existing lane summary.

If you do not capture your shipment history in Oracle Transportation Sourcing, then you can start the truckload rates sourcing process by creating a lane summary. Or, if you already pulled your shipment history in to Oracle Transportation Sourcing via the Build Shipment Set action, then creating a lane summary is your next step. A lane summary summarizes the demand (number of shipments in a time frame) that is expected for a particular lane.

To create a lane summary, run the Build Lane Summary action. This action is accessed via Sourcing > Lane Aggregation > Lane Summary Criteria > Actions > Build Lane Summary.

Building a Lane Summary

1. Select N (No) or Y (Yes) in the Remove Outliers drop-down list.

   Note: This only causes the outliers to be removed when calculating the average distance for the lane. Outlier shipments are still counted towards the demand.

   Note: An outlier is a value whose difference from the mean is more than 3 times the standard deviation. The mean is the arithmetic average.
   
   Let's look at an example. A shipment set has a total of 30 shipments. 29 of those shipments have distance of 1 mile and 1 of those shipments has a distance of 20 miles. Then, the average distance is 1.6 miles and standard deviation for the distance is 3.4 miles. The shipment which travels 20 miles has a difference from the average of 18.4 miles (distance - average). Then, if you take 3 x 3.4 (standard deviation), the result is 10.2 which is the minimum outlier value. Since 18.4 is greater than 10.2, this shipment is considered an outlier.

2. If you want to run the action in the background, accept the default of Yes for the Run Job in Background field. The server can time out while waiting for a result if the action is run in the foreground for a large data set. Hence, for large data sets, you need to run the action in the background.
3. Designate a contact in the Contact ID field if you selected Yes to Run Job in Background. When the action finishes, an email will be sent to the contact. Email notification is the only communication method even if fields are populated for other communication methods. There is no results page so the email notification is the only notification.
4. Click Build Lane Summary to run the action.