Question & Answer
Question
Pool Point Routes in Optimization
Answer
Pool Point Routes in Optimization
You can use the optimizer to manage orders and shipmentsthat will be delivered to or from a pool point.
Pool Point Configuration
You can use thefollowing features of Sterling TMS to configureyour pool point facilities:
- Pre-Define Pool Options
When you set up your Sterling TMS configurationyou can specify that you plan to optimize shipments that are beingrouted through pool points. You set the Pre-Define PoolOptions setting on the Planning page in Step 1 of ShipperConfiguration.
When you create or update each order Sterling TMS determinesthe pool point routing options. When you submit these orders to theoptimizer the run takes less time because the optimizer does nothave to search for the pool point routing options.
- Locations
When you define your locations in Sterling TMS you can specifythat these are pool point facilities. You can then define the areaof service transit times and other attributes of the pool pointfacility.
Sterling TMS takesinto account the shipping and receiving calendar rules to determinethe hours of operation for a pool point location:
- Outbound pool points
- The optimizer is planning the delivery from the origin to thepool point. Sterling TMS usesthe receiving hours in the location operational calendar.
- Inbound pool points
- The optimizer is planning the delivery from the pool point tothe final destination. Sterling TMS uses the shippinghours in the location operational calendar.
For more information about setting up locationssee the IBM? SterlingTransportation Management System ShipperConfiguration Guide.
Pool Point Options in an Optimization Run
Whenyou define each optimization run you can specify how you want theoptimizer to group orders together that are being picked up or deliveredat a pool point location.
You define the Pool PointOption setting on the Shipping Data tabof the Optimization Parameters page.
When you define the PoolPoint Option for an optimization run you can select thefollowing settings:
- Ignore Pool Points
The optimizer does not group orders based on a pool point originor destination. This is the default value.
- Origins Only
The optimizer groups orders together that are being pickedup at the same pool point facility
- Destinations Only
The optimizer groups orders together that are being deliveredto the same pool point facility.
Additional Notes for Pool Points
The followingnotes provide information and tips for using pool points in your optimizationprocess:
- The optimizer only routes orders through a pool point if it reducesthe cost. If using a pool point would increase the cost the optimizerroutes the order through the original origin or destination.
- The optimizer only considers pool point locations that are ownedby your shipper organization. The optimizer does not consider locationsthat are owned by a customer supplier or third party.
- The optimizer will take into account the stop priority for a poolpoint location when it builds a multi-stop truckload route. For exampleyou might define a pool point location and specify that it must bethe first delivery stop on the route.
- When you define a pool point location you can specify which modesare supported for pickups or deliveries at that location. When theoptimizer builds shipments that are routed through a pool point theoptimizer will only select modes that are supported at the pool point.
- The optimizer does not support the routing of shipments throughlocations that are only a cross-dock. The optimizer will only processlocations that are a pool point or are both a pool point and cross-dockfacility.
- The optimizer can only route each shipment through one pool point.A single optimization run cannot create a route that uses pool pointsas both the origin and destination. The optimizer will consider aninbound pool point as an alternate pickup location for the linehaulleg. It will also consider an outbound pool point as an alternatedestination location for the linehaul leg.
Was this topic helpful?
Document Information
Modified date:
08 December 2018
UID
ibm10753929