Ingen lysbildetittel

1
Intermodality and Interoperability around the
Baltic Sea
InterBaltic Final Conference A future transport
Policy for the Baltic Sea region Klaipéda, 20
21 November 2007
Demonstration of software tool for intermodal
transport planning Instytut Logistyki i
Magazynowania / Institute of Logistics and
Warehousing
2
AGENDA

• Software presentation
• Deployment plan
• Live Demo of the toolbox

3
PLANNING NEEDS

• Many transport routes
• Many service providers
• Different timetables
• Different schedules
• Different costs
• Different quality
• Needs for
• Coordination
• Management
• Maintanance

4
System for planning intermodal transport chains

• The ability to create all possible transport
  network connections
• The ability to choose best route for a customer
  by using optimisation algorithms
• The possibility to pre-verify transport chain
  with estimated schedule and costs

5
PLANNING PROCESS
Service Provider
Customer
Planning Operator
transport network planning
shipment planning
Register provider services
Register customer booking
Build transport network
Plan transport chain
Pre-calculation and register customer services
Handle provider bookings
customer agreement
Planning Operator
Planning Operator
Planning Operator
6
PLANNING PROCESS
3. Establish Customer Relationships
4. Shipment Planning
Register Customer Services
Customer Booking
Provider Bookings
Register Customer Booking
Plan Transport
Provider Services
Build Transport Network
Register Provider Services
Customer Booking
Transport Planned
Customer Service
2. Network Planning
1. Transport Configuration
7
PLANNING PROCESS- EXECUTION EXTENSION -
Transport Documentation
5. Transport Execution
Plan Transport
Provider Bookings
Transport Execution Monitoring
Transport executed
Transport Planned
Deviation Management
Deviation managed
Deviations
Invoices Payments
Invoices
6. Invoice and Payments
8
Main user roles of the application for planning
intermodal transport chains
Users
TCM Office
Service Providers
Customers
System Administrators
9
TCM office

• the main role in the planning system,
• responsible for planning of transport chains.
• TCM Office can be a shipper, freight integrator,
  it can be a lead logistics provider (a logistics
  service provider integrating other services), but
  it can also be an authority (port,
  infrastructure, port authority) aiming to analyse
  potential logistics links. Logistics service
  providers can build transport chains based on
  their own services and other service providers.

LSP
Freight Integrator
Authority
Shipper
TCM Office
10
SERVICE PROVIDERS
This role is dedicated to all the companies,
organisations whose services are necessary to
plan a transport chain. Sometimes the TCM enters
the information for the logistics service
providers.
Rail transport company
Road transport company
Sea shipping company
Message broker
Air transport company
Application for planning intermodal transport
chains
WWW
Other services
Ports
Insurance company
Logistics provider - warehousing
11
CUSTOMERS

• Users that are the customers of TCM Office and
  they need to move goods from A to B.
• They have access to the system where they can
  enter their requests for transport. They can do
  it manually or by sending electronic messages.
  Sometimes the TCM enters the information for the
  customer.
• When conducting planning based on lead-time and
  scheduled provider services, we can only plan
  individual shipments (not transport templates)
  since timetables produce different results based
  on the pick-up time.

Message broker
Application for planning intermodal transport
chains
Customer A
Customer B
WWW
12
MAIN FUNCTIONS
Application for planning intermodal transport
chains
Core
Network management

• Customer booking in-take
• Shipment scheduling
• Booking monitor

• Routes schedules
• Provider Services
• Logistics templates
• Pre-calculations
• Customer services

• Reference data
• Application adm./config.
• User adm./config.

• Limited messaging
• Logging

13
MAIN FUNCTIONS - Potential extension towards
execution -
Application for planning intermodal transport
chains
Core

• Estimated cost
• Actual cost
• Invoiced cost
• Claims handling

Network management

• Customer booking in-take
• Shipment scheduling
• Booking monitor
• Tracking tracing
• Event management
• Deviation management

• Routes schedules
• Provider Services
• Logistics templates
• Pre-calculations
• Customer services

• Reference data
• Application adm./config.
• User adm./config.

• Messaging
• Logging

14
REFERENCE DATA

• Before the planning process can start the system
  has to be provided with basic data which are
• Locations
• Companies (customers, service providers and TCM
  offices)
• Transport means types
• Transport means
• Cargo Units
• Measurement units
• Unit types
• Service Categories
• Currencies

15
REFERENCE DATA
Register Locations
Register Companies
Locations

• Registered Once
• Reusable
• Reduced risk for errors

Register Routes
Companies
Routes
Register Transport Means Types
Register Transport Means
Transport Means
Transport Means Types
Register Service Categories
Service Categories
Register Transport Units
Transport Units
Register Currencies
Currencies
16
PROVIDER SERVICES REGISTRATION
Logistics service provider is registering its
services in the system. The service will be used
later for planning transport chains. For the
scheduled (line-oriented) services it is possible
to enter the timetables. If no timetables are
available we may use the estimated duration of a
service.
17
PROVIDER SERVICES REGISTRATION
The registered services should be filled with all
required information during planning process

• Prices or cost estimates (if available)
• Schedule / Duration
• Required document exchange (not required during
  planning)
• Contract documents

18
PROVIDER SERVICES REGISTRATION-COSTS-
19
PROVIDER SERVICES REGISTRATION-DATA EXCHANGE-
20
PROVIDER SERVICES REGISTRATION-TIMING-
21
PROVIDER SERVICES REGISTRATION - Timing
Underlying voyage structures -
Multiple scheduled services, independent of
its modality
Vessel details
22
BUILDING TRANSPORT NETWORK

• Network planning is done by the users of TCM
  Office in the system
• and it is based on the available provider
  services.
• The result of the network planning are the chain
  templates.
• Chain templates can start in a very specific
  place like Port in Gdansk
• and also in more general location like a city or
  country.
• Chain templates can have many alternative routes
  with different transport modes.
• Different routes are presented graphically on
  the screen.

23
BUILDING TRANSPORT NETWORK

• Chain templates can also have a hierarchical
  structure.
• One chain template can use another as one leg of
  the transport chain.
• TCM offices can operate in different geographical
  regions.
• For instance we can have TCM office specializing
  with transport goods
• from far East to Europe.
• And we can have a TCM office operating just in
  Europe.
• Both of them can be a customer to each other.

24
Pre-Calculation of Routes in Transport Templates
In this stage a TCM Office creates a
precalculation with the help of the
existing chain templates or it can be done adhoc
using provider services directly. The transport
chain template pre-calculated costs is proposed
to the customer. If the customer agrees to the
quotation given based on the pre-calculation then
the TCM can pack that transport chain template
as a customer service.
Creating a transport chain
25
CUSTOMER SERVICE REGISTRATION
Customer service is a registered agreement
between customer and TCM office. It is based on
the previously made transport chain template and
pre-calculation. It has an agreed validity
period and price per unit.
Customer service
26
CUSTOMER SERVICE REGISTRATION
Customer service is a registered agreement
between customer and TCM office. It is based on
the previously made transport chain template and
pre-calculation. It has an agreed validity
period and price per unit.
Customer service
27
CUSTOMER BOOKING
This is a stage where we finally start planning
real shipments. The shipment planning is
triggered by incoming customer bookings, which
are the door-to-door transport orders. They can
be sent by electronic messages or entered
manually into the system. Customer bookings may
have connection to the existing customer
services. If they dont have it then TCM office
has to built the transport chain from scatch.
Customer booking
28
CUSTOMER BOOKING
Checking and entering the load units
Load unit hierarchy E.g. Pallets in Containers
29
CUSTOMER BOOKING
For chain used
Y
N
Use of LT template or spot operation
Use template?
Select logistics template
Select services for spot operation
30
CUSTOMER BOOKING
Transport chain details
31
PROVIDER BOOKING HANDLING
In the last stage of planning the TCM office has
to confirm transport of shipment with all
service providers along the whole chain. When
this is done the planning process is finished. If
some of the service is not confirmed TCM office
should reschedule or try to find alternative
services and replan the chain.
Provider booking request and confirmation
32
SUMMARY

• There are three different roles in the
  application for planning intermodal transport
  chains - Customer, Service Provider, TCM Office

• It does not matter who is the TCM Office from the
  planning point of view Shipper, Freight
  Integrator, Logistics Service Provider, or
  Authority

• System must be populated with basic data before
  the planning process begin (units, transport
  means, locations, )

• Service providers may enter their services to the
  system by themselves with prices/costs and
  detailed schedules

• TCM Office can create chain templates which are
  helpful with transport planning there is no need
  to start a transport chain from scratch every time

• Customer service is an agreement between customer
  and TCM office with certain price and period

• Customers provides transport orders to the system
  (Customer booking)

• Before transport starts TCM office confirms all
  the provider bookings for the whole transport
  chain

33
Customizations

• The following final customizations have been
  delivered
• Hierarchical locations
• Service compatibility
• Semi automatic building of chains
• Load units compatibility
• Intermodal route planning
• Use of compatibilities in planning

34
Customization requirements- Hierarchical
location codes -
Locode Hamburg
Continent Country Locode Zipcode
Terminal
Terminal Hamburg Sea Terminal
Terminal Hamburg Rail Terminal
Hamburg
Hamburg
Shunting service
Hamburg Rail Terminal
Hamburg Sea Terminal
Short sea service
Rail service
35
Customization requirements- Load unit
compatibility -
Load unit Type Container_to_wagon
11 subtype
11 subtype
Load unit Type Container
Load unit Type Wagon
e.g. 41 conversion factor
Terminal service
Road service
Rail service
36
Customization requirements- Load unit
compatibility -
Load unit Type Container_to_wagon
11 subtype
11 subtype
Load unit Type Container
Load unit Type Wagon
e.g. 41 conversion factor
Terminal service
Road service
Rail service
Load unit Type Container
Load unit Type Wagon
Load unit Type Container_ to_wagon
37
Customization requirements- Intermodal route
planning -
Step 1 Find the best (1st) shortest path
38
Customization requirements- Intermodal route
planning -
Step 2 Disable main corridor of non-road
services using the same modality between hubs
39
Customization requirements- Intermodal route
planning -
Step 3 Find next (2nd) best alternative using
another main non-road corridor
40
Customization requirements- Intermodal route
planning -
Step 4 Disable main corridor of non-road
services
41
Customization requirements- Intermodal route
planning -
Step 5 Find next (3rd) best alternative using
another main non-road corridor
42
NECL
Rail
Rail
SSS
SSS
SSS
Rail
Rail
43
NECL Network- Chain 1 -
44
NECL Network- Chain 2 -
44
45
NECL Network- Chain 3 -
46
Seafood corridor
Rail
Rail
Rail
Rail
SSS
SSS
SSS
Rail
Rail
Rail
Rail
47
Seafood Network - Chain 1 -
48
Seafood Network - Chain 2 -
49
Seafood Network - Chain 3 -
50
Asia corridor
Rail
Rail
SSS
SSS
Deap sea shipping To DE To PL
51
Asia network
52
Intermodality and Interoperability around the
Baltic Sea
InterBaltic Final Conference A future transport
Policy for the Baltic Sea region Klaipéda, 20
21 November 2007
Deployment Plan of software tool for intermodal
transport planning Instytut Logistyki i
Magazynowania / Institute of Logistics and
Warehousing