Beruflich Dokumente
Kultur Dokumente
Declaration:
I/We hereby declare that this document is based on my/our personal experiences and / or experiences
of my/our team members. To the best of my/our knowledge, this document does not contain any material
that infringes the copyrights of any other individual or organization including the customers of Infosys.
Target users: Everyone who wish to know basics of Transportation and Transportation Management.
Keywords: Planning and Management Functions, Environment Concepts, Shipping, Routing, Deliveries,
Table of Contents
1 | Infosys®
1. TRANSPORTATION MANAGEMENT – INTRODUCTION ................................................................................... 4
2 | Infosys®
4.4 SCHEDULE NUMBERS: ...............................................................................................................................................8
4.5 DATA INTERFACES:....................................................................................................................................................8
4.6 SHIPMENT AND CALCULATIONS: ..................................................................................................................................8
6. REFERENCES: ............................................................................................................................................... 10
3 | Infosys®
1. Transportation Management – Introduction
1.1 Transportation:
“Transportation is a process of moving people or goods from one place to another” For
instance, to travel from one place to another we need transport. In the same way to carry finished
goods we need transport.
The word transportation is derived from Latin word Trans (to carry).
Advantages of Transportation:
Shipment Scheduling
Routing
Freight Cost Management
Shipment Tracking
Parcel Management
3.3 Orders:
Transportation’s main input is Orders. It has a single origin/destination pair. Orders
enter into transportation in two ways i.e. by downloading them from your order processing
system by calling Order interface program or by using orders user-view. The information is
divided into three groups.
3.3.1 Order Status: Basically orders go through different processing stages starting
when they are placed and ending when they reach back to the system. Order status
5 | Infosys®
shows what has been done to the order. It also has the information on how the order
will be handled in the next subsequent stages.
3.3.2 Splitting Units: It is the process of splitting the order into two or more orders and
each of them is called a split. An order is spitted because of its huge size that cannot
be fit in a full truckload.
3.3.3 Incomplete Orders: We can configure transport to accept or reject incomplete
orders.
3.4 Items:
They are the type of freights that are passed into transport via order interface. Items and
their attributes are defined in the Item Master user-view. Orders that enter into user-view are
entered with commodities. An unlimited number of items can be defined.
6 | Infosys®
3.8 Delivery Times and Appointments:
An order’s delivery time is decided based on its appointment time or earliest and latest-
delivery time. If the order has both of them, then the appointment time is used by default. If an
order has only the appointment time, then the earliest and latest delivery time is defined as
follows
Early Delivery Time = Appointment time – Appointment Range Early
Latest Delivery Time = Appointment Time + Appointment Range Early
4.2 Plan:
Here we create a case by filling the daily plan and store the plan definitions in the
database and execute by using Case Build Function. The plan includes information about the
Orders that include Carrier resources availability, Scenario Parameters values and Start date
and time. The orders that are scheduled in the plan are determined by horizon and load start
dates, schedule number, order group, delivery and departure horizon dates. Order before the
7 | Infosys®
horizon can also be included in the plan but remain unscheduled unless they are the part of
rolled load.
4.3 Scenario:
This is the combination of rules that are used for solving case. These are set by
transportation planners and several times they are reused. For example, if we set one scenario
for weekdays deliveries and another scenario for weekend deliveries that will enable us to set
two separate groups providing a way to adjust the amount of traffic that we have in weekdays
and weekends. The system can automatically update the delivery and departure horizons to
account for Saturdays and Sundays when pickups are not allowed.
8 | Infosys®
trailer building module to determine which shipment has overlapping departure windows and
place them on the same trailer.
9 | Infosys®
5.5 Carrier Commitment and Availability:
This feature enables load to the vehicles based on their availability and
commitment. Here Carrier commitment is the minimum number of vehicles promised to the
shipper and Carrier availability is the maximum number of vehicles available for a particular
lane. The transportation solution uses minimum number of vehicles promised but not exceeds
the maximum number for that particular lane.
5.6 Crossdocking:
This feature is an intermediate freight point. Once the load reaches this point,
it is unloaded and then stored for a time period and then it is loaded back into another trailer
and at last it reaches the destination. This feature as two parts: 1. To-Crossdock trips and From-
Crossdock trips. Here the To-Crossdock – Delivery can occur at any point of the trip whereas
the From-Crossdock – Pickup must the starting point of the trip.
6. References:
1. www.dot.ca.gov – Transportation Management Plan Guidelines
2. http://en.wikipedia.org – Transportation _Management System
3. www.planning.dot.gov – The Transportation Planning Process
10 | Infosys®
4. www.ops.fhwa.dot.gov – Developing and Implementing Transportation Management
Plan
5. www.townofchapelhill.org – Guide for Transportation Management Plan Development
6. www.tdot.state.tn.us – Transportation Management Plan Workbook
11 | Infosys®