Lane Summary Criteria

This page is accessed via Sourcing > Lane Aggregation > Lane Summary Criteria.

A lane summary summarizes the demand (number of shipments in a time frame) that is expected for a particular lane. The lane summary is built based on the lane summary criteria which you specify on this page. Once you specify the lane summary criteria, you can view the resulting lane summary via the View Lane Summary action. For LTL shipments, run the LTL Lane Summary Report instead.

The Lane Summary Criteria page defines the effective dates of the lane as well as the number of time periods within that time frame. For example, if your effective date range spans one year and you have defined a time period size of 7 (days), then that translates to 52 time periods (i.e., weeks). If you enter a value of 1 in the First Time Period field, this indicates that the first time period included in the lane summary is week #1. You can select a value greater than 1 (e.g., '5' for week #5).

Creating a Lane Summary Criteria

• Enter a Lane Summary ID.

Constraints

1. Enter a Begin Date and End Date.
2. Select a Shipment Type. Options are TL, Ocean, or LTL.
   
   The shipment type is important because it tells Oracle Transportation Sourcing whether to treat this shipment as a TL, Ocean, or LTL shipment. This is particularly important when creating the lane summary since a lane summary for Ocean has different options than a lane summary for TL. For example, since you can create your own transport modes, Oracle Transportation Sourcing needs to map the user-created transport mode of Truck Load to the Sourcing shipment type of TL.
3. Enter a Saved Query ID to eliminate certain shipments from consideration.
   
   The Saved Query ID field allows you to limit data by anything in the sourcing shipment (p_shipment) table. This query can only be created using the New icon. You should never create this query using one of the OTM finder pages. If you need to query tables besides the Sourcing p_shipment table, then you must use a sub-query within the query against the shipment table.

   Note: The saved query focuses on the p_shipment (instead of the shipment table for the shipment set criteria). For example, a saved query like where p_shipment.num_stops>2 will work in this context.

4. Enter a Service Provider Profile ID.
5. Enter a Mode Profile ID.
6. Optionally, select the Bid By Equipment Reference Unit check box to take the Equipment Reference Unit ID into consideration while building the lane summary. A unique lane including an equipment reference unit is as follows: for TL mode xLane ID and ERU ID, for LTL mode xLane ID, NMFC, and ERU ID, and for Ocean mode ERU ID.
7. Optionally, select the Bid By Equipment Group check box to take the Equipment Group ID into consideration while building the lane summary. This check box is only available for TL mode. It is no relevant for LTL mode and ocean mode uses equipment group profile instead.
8. Enter a Equipment Group Profile ID. Equipment group profile is only available for the transport modes of TL and ocean. It is not relevant for the transport mode of LTL and so does not appear for LTL shipments.

Note: In projects and bid rounds for ocean shipments, the equipment group specified on the constraint set must match the equipment group used in the lane summary for the matching lane. If the equipment does not match, then the carrier will see an error when uploading the bid response. This is a result of how Oracle Transportation Sourcing aggregates demand specifically for each equipment group; there is no equipment group conversion factor for ocean.

Prevent Bad Lanes

Sourcing shipments can cover a wide variety of lanes which can be grouped into geography hierarchies. For a particular sourcing project, you will want to standardize the demand into a preferred geo-hierarchy. You can specify a desired geo hierarchy profile ID on the shipment set criteria to eliminate bad lanes from being assigned to shipments. A bad lane is a lane that does not match the desired geo hierarchy profile.

When a shipment with a bad lane is copied into Oracle Transportation Sourcing, the system looks for an existing lane based on the ranking in the desired geo hierarchy profile and then associates the existing lane with the shipment. If no existing lane is found, then the system creates a new lane for the shipment based on the “best” source and destination geography specified on the lane summary.

In order to prevent bad lanes, both a shipment set criteria and a lane summary criteria must exist. The desired geo hierarchy profile specified on the shipment set criteria determines what existing lanes to reuse; while the desired source geo hierarchy and desired destination geo hierarchy specified on the lane summary criteria determines the geo-hierarchy of the newly created lane.

1. Enter a Desired Source Geo Hierarchy ID.
2. Enter a Desired Destination Geo Hierarchy ID.

Summary Statistics

1. Enter a Time Period Size.
2. Enter a value in the First Time Period field.
3. Enter a Shipment Set ID. By doing so, the lanes represented in this summary are the distinct set of lanes referenced by the shipments in that shipment set.
4. Click Save for each shipment set you specify.
5. Click Finished to save the lane summary criteria.