Inbound Shipment Bulk

Planning

Will Shook
OTM Senior Analyst
Ingersoll Rand
 Agenda
• Ingersoll Rand
• Business Case
• Solution
• High level process flows
• Business Benefit
• Existing configuration
• Configuration
• Lessons Learned
• Q&A

3
 Family of Brands

4
 Business Case
• In early 2019 Ingersoll Rand implemented Inbound transportation for select
US suppliers shipping to US facilities. Supplier orders entered in OTM are
auto planned and manually approved for tender. Consolidation opportunity
is missed through manual execution.
• The Business expectation is that OTM consolidate multiple orders in a once
daily bulk plan. The capability of multi-stop TL should exist with
consideration of loading time.
• A method to measure cost savings of consolidation and multi-stop TL is
needed.
• Pool consolidation, parcel, and multi-delivery are not in scope.

5
 Solution

• Modify Parameter set (Multistop Config) to allow multi-stop shipments.

• Modify the existing order create agent to not auto plan all order releases
and add Calculate Direct Cost.
• Create a standard loading activity time and maintenance process for
supplier locations.
• Modify the Inbound Bill of Lading for multi-stop TL.
• Verify and test multi-pickup TL EDI 204 with participating carriers.
• Create a scheduled job for the bulk plan.

6
 High Level process flow

Supplier creates an BOL generated to

As is process state order release using
the rapid order
Order release is auto
planned
Planner review and
executes tender
Carrier
Acceptance
Yes Inbound supplier
release screen

No

Supplier creates an BOL generated to

Order release
order release using
To be process state the rapid order
release screen
Is LPD < 2 days? No participates in the
schedlued bulk plan
Inbound supplier

Yes Yes

Order release is auto Planner review and Carrier

planned executes tender Acceptance

No

7
Business Benefit

• Reduced planner interaction with planned shipments

• Reduced cost through order consolidation and multi-stop shipments
• Direct cost capture for reporting
• Multi-stop Bill of Lading unique to each supplier
• Increased visibility to short cycle orders

8
Existing configuration not modified
• Supplier order entry process
• Itinerary – Utilized an existing multi-stop OB itinerary with pool capability,
matching equipment, and regions.
• Rates – Utilized rate cost in the as is process state.
• Commitment allocation
• Planner shipment and order release queries
• Tender process

9
Configuration – Parameter Set
Non default values utilized
• BULK PLAN
– USE RATE PREFERENCE - 2.Preferred Rates If Available
• CONTAINER OPTIMIZATION
– CONTAINER OPT CONFIG ID - INB_CONTAINER_OPTIMIZATION
– PERFORM ORDER BUNDLE SPLITTING USING CONTAINER OPT – TRUE
• MULTISTOP
– MULTISTOP CONFIG ID - INB_MS_CONFIG
• SERVICE PROVIDER ASSIGNMENT
– APPLY COMMITMENT ON THE MOST SPECIFIC LANE – TRUE
– PLAN SHIPMENTS WITH CARRIER COMMITMENT – TRUE
• SERVICE TIME
– MINIMIZE WAIT TIME IN SERVICE TIME CALCULATION – TRUE
• SHIPMENT PLANNING
– ALLOW DIFFERENT RATE RECORDS FOR SPLIT ORDERS – TRUE
– ALLOW DIFFERENT RATE SERVICES FOR SPLIT ORDERS – TRUE

10
Configuration – Parameter Set

INB_CONTAINER_OPTIMIZATION
Non default values utilized

• CONTAINER OPTIMIZATION ALGORITHM

– USE 3D BASED LOAD CONFIGURATION – TRUE
• CONTAINER OPTIMIZATION LOAD PLACEMENT
– LOAD CONFIG MULTISTOP MIXING RULE - 0.No mixing allowed
• CONTAINER OPTIMIZATION METRICS
– WEIGHT AND VOLUME METRIC – TRUE

11
Configuration – Parameter Set
INB_MS_CONFIG
Non default values utilized
• GENERAL
– MULTISTOP MAX DISTANCE BETWEEN DELIVERIES – 1.00 mi
– MULTISTOP MAX DISTANCE BETWEEN PICKUPS – 250 mi
– MULTISTOP MAX TIME BETWEEN DELIVERIES - 0D 0M
– MULTISTOP MAX TIME BETWEEN PICKUPS - 1D 0M
• MULTISTOP STOP CONSTRAINTS
– MAXIMUM DELIVERY STOPS ALLOWED - 1
– MAXIMUM PICKUP STOPS ALLOWED - 3
– MAXIMUM STOPS ALLOWED - 4

12
Configuration – Rate Offering
• Total All Stops and Pickup Stops count modified to carrier capability.
• Low Stop and High Stop values modified to match total stops.

13
Configuration – Order Create Agent
• Modified to allow auto plan for
short cycle orders (same or next day).

• Added Calculate Direct Cost to

populate values in the order release
table.

14
Configuration – Location Activity Time

• Activity Time Definition applied to the supplier location

15
Configuration – Supplier creation and
modification

• Alteryx supplier creation files were

updated with the
LOCATION_ACTIVITY_TIME_DEF
table to include a standard time.
• An agent was created to detect
user removal of the Location
Activity Time and replace with the
standard time.

16
Configuration – Supplier creation and
modification
• A scheduled job was created to pickup
any supplier location added without an
Activity time and add the standard time.

17
Configuration - Multi-stop BOL
• The BOL is configured using BI Publisher. Changes were required to identify
the pickup stop number, stop piece count and stop weight.

18
Configuration – Scheduled Job
• The Inbound bulk plan runs once daily
to include all regions and order releases
up to 7 days in the future.

19
EDI 204
• Multi-stop pickup was a new feature not used in outbound scenarios.
Testing was required to verify carriers could read the S5 segment 02
element “PL” indicating a partial load.
Example: S5*1*PL~
• During testing we found our previous OB 204 reported all weight and piece
counts at stop one. For multi-pickup this value was misleading and moved
to a text message in NTE segment.
Example: NTE*BOL*Total Weight: 8520 LB Total Count: 28~
• Further development was required to send cumulative values in the out xml
at the stop level for mapping to the S5 segment.

20
Lessons Learned
• Turning auto plan off lead to missed same day shipments and adhoc bulk
plans created delays.
A correction was made to the order create agent to auto plan same day
and next day shipments.
• Supplier access to modify calendars created planning failures after deleting
activities and adding invalid times.
Supplier access to modify calendars was removed.
• Bulk Planned shipments auto tendered without an agent action.
Work flow parameter ATA_SOURCE_FOR_AUTO_SECURE_RESOURCE
contained an invalid entry and the value was change to null.

21
22