- OTM SIG · Networking Solutions in OTM Al Drummond, Oracle to 6.3 and Beyond

<Insert Picture Here>

Networking Solutions in OTM Al Drummond, Oracle

to 6.3 and Beyond

© 2009 Oracle Corporation – Proprietary and Confidential

Safe Harbor Statement

• The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

to 6.3 and Beyond


Multi-Tier Vision Statement • Objective

• Replace the current multi-tier solution with a more robust solver that makes cost based routing decisions for orders across multiple itineraries – taking into account • carrier capacities and commitments • Location capacities • Schedules (voyage and ground)

• Provide ability to route through a network of cross docks and pools

without placing limitations on number and sequence of cross docks and pools.

• Ability to perform staged planning

• Ability to plan order movements across legs – grouping of order movements and sequence of processing the groups


Topics to be Covered

• Networks and Multi-Tier • Business Applications of Networks • Network Modeling Flexibility • New Objects to Configure • Roadmap


NETWORKS AND MULTI-TIER


Multi-tier

• Multi-Tier is a new Order Routing Method that works with both networks and itineraries • Itineraries are an enumerative way of describing paths for an

order to take. (Pre- 6.3) • Networks are a shortcut to model multiple pathways in a very

simple manner. (New in 6.3)

• The combination of Networks and Multi-Tier provides a very powerful tool to solve routing problems.

to 6.3 and Beyond


Network Planning • The new OTM Network capability supports

• Multiple pathways through multiple “through points”. • Determination of best path in combination with other freight

that is flowing through the network. (Synergistic Routing) • Ability to view alternative pathways and “route” orders through

specific “through points”.

• Networking was made possible through the multi-tier enhancement in 6.3 that split the planning process into 2 components. • Path selection of orders and generation of Order Movements • Bulk Plan of Order Movements

• The 2 step process can “pause” after the first step if desired. • This is a prerequisite for “continuous” or “staged” planning.


Order Management in 6.3 • Bulk Plan of Order Releases

• Bulk Plan straight to shipments (Traditional Method) • Bulk Plan of Order Release – create Order Movements only

• Allows creation of OM on all legs at one time. • Example : An order that uses a network with many

sequential “hops” over several days. • Allows planning of OM on a timely basis.

• Plan next day’s shipments now • Hold off planning following day’s shipments until all OM are

known. • Routing

• Allows Show Routing Options – By Path • Allows Routing Constraints to be added to orders. • Order Movements inherit these constraints. • Order constrains can be added by an ADA rule. • Can search for orders by the Routing Constraints


New Action – Build Shipments Show Network Routing Options


New Action – Build Shipments Show Network Routing Options

Expand each result to show leg details.


BUSINESS APPLICATIONS OF NETWORKS


Applications of Network

• Unidirectional – Dispersion of freight from one or more sources to multiple

destinations through an expanding “tree” type network. – Optimization of inbound freight through consolidation and

multi-stop across multiple modes.

• Bidirectional – Facilities support multiple flows at the same time. – Ability to model multiple unidirectional networks regardless of

direction on one large network. – First and Last Mile Order Movements can be combined into

one shipment with capabilities for both pickup and delivery in the same shipment.


Unidirectional Examples

• Consolidated shipments through a network to distribution hubs. • Dispersion by multiple LTL shipments. • Dispersion by Parcel.

• Inbound to facilities by different modes. • Different Paths depending on Order Time Window

• Intermodal or Truck • Different collection points depending on consolidation

opportunities

Only 1 flow is shown on the following diagrams for illustration purposes.. In 6.3, multiple flows are more likely and can be modeled in 1 network.


Appliance Distribution Network

Factory

X Dock and DC

Local Delivery Region

Example of Flow of Goods through Network to One Distribution Region

Columbia, SC

Columbus, OH

Indianapolis, IN

Des Moines, IA

Jackson, MS

Atlanta, GA

Oklahoma City, OK

Amana, IA Clyde, OH

Tulsa, OK

Ft. Smith, AR

Flows will change as additional DCs are delivering orders.

Stoves

Refrigerators

Dryers Washing Machines

50 Customers in NC Each Customer gets One of each appliance.


Last Mile Multi-stop Delivery Shipments Appliance Distribution Case from Columbia, SC to North Carolina Destinations

Capacity Limits Are used for Shipment Building Of Order Movements.

Palmetto Delivery Service has 2 – 28 ft City Box Trucks Daily Swamp Fox Trucking has 3 – 22 ft Straight Trucks Daily

Delivery Routes


Parcel Distribution from Macon Hub

Inbound Line Haul


Supports Kewill Inbound Line Haul

Parcel Delivery Shipments

Kewill Registered Origin


Inbound to Central DC Scenario

Rail Ramp

Rail Ramp

Kankakee DC

BNSF S Seattle Ramp

BNSF Cicero Ramp

Rail Ramp

Rail Ramp

Rail Ramp

Rail Ramp

Rail Ramp

BNSF Hobart Ramp

San Diego Mfg

Full Truckload

BNSF Corwith Ramp

Chehalis Mfg

Rail Ramp

CSXT Boston Ramp

CSXT Chicago BPA Ramp

CSXT Savannah Ramp

Natick Mfg

Full Truckload

Full Truckload

CSXT Chicago C59 Ramp Rail Ramp

CSXT Philadelphia Ramp

Trenton Mfg

Full Truckload

USSAV Port

Kokomo Mfg

Full Load – Truck, Intermodal, Ocean

Rail Ramp

Factory

Rail Ramp

Destination

Cross Dock

Port



Rail Ramp

Kankakee DC Tacoma Mfg

Seattle Hub

San Bernardino Hub

BNSF S Seattle Ramp

BNSF Cicero Ramp

Rail Ramp

Rail Ramp

Rail Ramp

Rail Ramp

BNSF San Bernardino Ramp

St Louis Hub

Riverside Mfg Pomona Mfg

LTL LTL

LTL

BNSF Corwith Ramp

Renton Mfg

LTL

Rail Ramp

Boston Mfg

CSXT Boston Ramp


Nashua Mfg

LTL

LTL

Quincy Mfg

Jackson Hub

Mobile Mfg

LTL

LTL

LTL via Collection Point – Truck or Intermodal



Rail Ramp

Rail Ramp

Kankakee DC Tacoma Mfg

Seattle Hub

San Bernardino Hub

BNSF S Seattle Ramp

BNSF Cicero Ramp

Rail Ramp

Rail Ramp

Rail Ramp

Rail Ramp

Rail Ramp

Rail Ramp

BNSF Hobart Ramp


St Louis Hub

San Diego Mfg

Riverside Mfg Pomona Mfg

LTL LTL

LTL

Full Truckload

BNSF Corwith Ramp

Renton Mfg

LTL

Chehalis Mfg

Rail Ramp

Boston Mfg

CSXT Boston Ramp


CSXT Savannah Ramp

Nashua Mfg

Natick Mfg

LTL

LTL

Full Truckload

Full Truckload

Quincy Mfg

CSXT Chicago C59 Ramp Rail Ramp

CSXT Philadelphia Ramp

Trenton Mfg

Full Truckload

USSAV Port

Kokomo Mfg

Jackson Hub

Mobile Mfg

LTL

LTL

Combined Full Load and LTL


Bidirectional Examples

• Consolidated shipments through a network to distribution hubs. • Dispersion by multiple P & D Shipments.

• Blended Networks • Choice of Rail Intermodal and Highway for full truckload direct

within same network. • Common P&D with choice of Rail Intermodal and internal

highway network for internal traffic between cross dock facilities.


Butte 331 231

380

450 770

Seattle

Minneapolis

Chicago

Segment of Network for P and D Consolidation Problem

1000

641

Minot

620

481

Seattle Chicago P&D Line Haul Line Haul Line Haul Line Haul P&D Monday Tuesday Wednesday Thursday Friday Monday Monday Friday Thursday Wednesday Tuesday Monday

Orders from Seattle Locations to Chicago Locations each day Orders from Chicago Locations to Seattle Locations each day

Sequence Numbers

1000

Pickups

Pickups

Deliveries

Deliveries


Seattle Area P & D Shipments

Inbound Line Haul

North Side P&D

South Side P&D Outbound Line Haul

Deliveries

Pick Ups

Stops 1-5

Stops 6-8

Starts at terminal

Ends at terminal


Example Stops for P&D


NETWORK MODELING FLEXIBILITY


Network Modeling Capabilities

• Great Flexibility in the approach and design of networks. • Variations in operation can be accommodated by simple

changes in the design of the network. • Large networks can be modeled based on simple hub and

spoke diagrams. • Example is an LTL network • Example is an Intermodal Network that is modeled as a

collection of O-D pairs with scheduled service modeled by a Ground Service.


Multiple Designs for Time Differentiated Mode Selection

• Case 2 - Independent Pickup by mode • Intermodal with multi-stop Pickup. • Truck direct with multi-stop Pickup.

• Case 1 – Consolidated Pickup • Intermodal between Hubs • Truck Direct between Hubs

Designs shown are simple cases with one pickup region and one destination region. Some simple designs could be enumerated in 6.2 with multiple itineraries. Case 2 However, more complicated options will require the power of the network.


Intermodal vs Truck – Time Based Decision

Kankakee DC

Rail Ramp

Rail Ramp


San Diego Mfg Riverside Mfg

Pomona Mfg

BNSF Willow Springs Ramp

Chicago Hub

BNSF $2,000 – 2 D 20 H

Time Sensitive Orders – Require Truck 1) San Diego Mfg to Rockford 2) Riverside Mfg to South Bend 3) Pomona Mfg to Kankakee Non Time Sensitive Orders – Intermodal OK 4) San Diego Mfg to Kankakee 5) Riverside Mfg to Rockford 6) Pomona Mfg to South Bend

Rockford DC

South Bend DC

San Diego Mfg Riverside Mfg

Case 2


Intermodal vs Truck – Time Based Decision

Kankakee DC

San Bernardino Hub

Rail Ramp

Rail Ramp


San Diego Mfg

Riverside Mfg

Pomona Mfg

BNSF Willow Springs Ramp

Chicago Hub

Time Sensitive Orders – Require Truck 1) San Diego Mfg to Rockford 2) Riverside Mfg to South Bend 3) Pomona Mfg to Kankakee Non Time Sensitive Orders – Intermodal OK 4) San Diego Mfg to Kankakee 5) Riverside Mfg to Rockford 6) Pomona Mfg to South Bend

Rockford DC

South Bend DC

Case 1


Network Modeling

It all starts with a sketch!

Modeling a network of hubs and spokes is as easy as it is to draw the network. First get the operational diagrams. (Hubs) Then decide how the network will operate. (Spokes)


LTL Trucking Network






Coutts

Denver

Butte

Salt Lake City

Winnepage

Calgary

Ohlahoma City

Blaine

Des Moines

Vancouver

331

421 521

253

381

621

423

231

333 623 233

850 380

450

582

820

770

650

422

724 455

Albuquerque

San Bernardino

Seattle

Sacramento

Minneapolis

281

283

680

Pembina

Chicago

Detroit

Toronto

Indianapolis

St Louis

LTL Network - Hubs and Spokes – OTM Schematic

Garland

El Paso

San Ysidro

Laredo

722

720

652

654 580

452

382

384 470 420

424

350

520

453

451

525

627 651

335 251

735

641

Minot

Kansas City

620

481

490

601


Rail Intermodal Operational Diagram


Rail Intermodal Network is Modeled by O-D Pairs

Seattle

Stockton

San Bernardino

Denver

Houston

Alliance

New Orleans

Spokane Chicago Cicero

Billings

St Paul

Birmingham

East St Louis Memphis

Omaha

Hobart

Los Angeles

Portland Chicago Corwith

Phoenix

Schedules to Chicago From Originating Ramps Kansas City


NEW OBJECTS TO CONFIGURE


New Objects and Definitions

• Path Finding • Network • Network Leg • Leg Consolidation Group • Routing Constraint

• Shipment Building • Multi-stop Logic Scenario Overrides • Leg Classification

to 6.3 and Beyond


Network – On Itinerary Leg

The itinerary can contain more than 1 leg each with a network.

Itinerary Provides Geography

Itinerary Leg Contains Network


Network

Two Places to Configure The maximum number Of “hops”

to 6.3 and Beyond


Network Detail – Joins Network to Network Legs

If Network Legs are created by CSV, you can name them with a naming convention. If Network Legs are created by UI, the ID will be a number.


Network Leg (Line Haul Example)

Attributes of the Network Leg – Line Haul Source and Destination - For Line Haul, these represent the terminals. Source and Destination Roles – Required for source and destination locations. Mode, Service Provider, Equipment – Profiles provided Expected Cost and Expected Service time Equipment Assignment Type – Optimize or No Equipment Leg Consolidation ID – instructions on how the resulting OM will build shipments.


Network Detail – Delivery Legs

Naming convention is critical to management of network legs.

Example: Source _ Destination _ Type of leg _ Carrier _ Equipment


Network Leg (Delivery Example)

Attributes of the Network Leg - Delivery Source and Source Role - For Delivery, this is the delivering terminal or hub. Destination Region (No Role Required) - This is a the geography of the delivery area. (Can be a list of locations, list of zip codes, list of states, list of countries) Mode, Service Provider, Equipment – Can Specify Service Provider and Equipment Expected Cost and Expected Service time Equipment Assignment Type – Optimize and No Equipment Leg Consolidation ID – instructions on how the resulting OM will build shipments.


Leg Consolidation Group Line Haul Delivery Leg Unidirectional Pickup Bidirectional Pickup

Attributes of Leg Consolidation Group ID – This is used to group order movements that should be planned together and also to create different groups to prevent order movements from being planned together. Sequencing Factor – Typically increased from source to destination Multi-stop Logic Scenario – Allows user to specify the parameters of multi-stop as they may be unique to each leg. Also allows user to shut off multi-stop when not needed.


Routing Constraints

OR

OM


New Routing Constraint

Allows use to specify locations to visit or not visit during the travel through the network. Options are expressed by use of the sequence number. For visiting, can specify must visit a location during transit. For visiting, can specify must visit one or more locations in a specific order. The same sequence number for 2 locations is an “either condition”.

to 6.3 and Beyond


Multi-stop Logic Scenario Overrides

Multi-stop Logic config has moved from a global parameter to a leg parameter Though the use of the Multi-stop Logic Scenario Overrides on the Leg Consolidation Group.


Leg Classifications

The use of Leg Classifications has changed from 6.2 to 6.3. Leg Classifications are used to specify order constraints for specify types of legs. Order release contains the Leg Classification and the constraint Network leg contains the Leg Classification For Example: Order 1234 must be delivered by Carrier Red Star Network delivery Legs must have “Leg Classification” DELIVERY LEG. Order Constraints for Leg Classification must have a Leg Classification DELIVERY LEG and a specified Service Provider RED STAR.


ROADMAP

Reminder: Everything in this presentation is for future releases and is not available today.


OR to OMs Actions Ocean Related Re-use Equipment Staged Planning Capacity

to 6.3 and Beyond

Documents

- OTM SIG · Networking Solutions in OTM Al Drummond, Oracle to 6.3 and Beyond