Intermodality and Interoperability around the Baltic Sea

1
Intermodality and Interoperability around the
Baltic Sea
WP3 Workshop Interbaltic Creation of the
assumptions of the pilot case demonstration
concerning implementation of intermodal supply
chain planning toolbox Hamburg 21- 22 March 2007
2
Intermodality and Interoperability around the
Baltic Sea

• AGENDA
• Part I Utilization of the intermodal planning
  system
• The application for planning intermodal transport
  chains
• Main user roles
• 2.1. TCM Office
• 2.2. Logistics Service Providers
• 2.3. Customers
• 3. Planning Process
• 4. Reference Data
• 5. Register provider services
• 6. Build transport network
• 7. Pre-calculation of routes in transport
  networks
• 8. Register Customer Service
• 9. Customer Booking
• 10. Handle provider bookings
• Summary
• Part II Demonstration scope and planning

WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
3
Intermodality and Interoperability around the
Baltic Sea
Part I Utilization of the intermodal planning
system
WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
4
Intermodality and Interoperability around the
Baltic Sea
Application for planning intermodal transport
chains
The application is delivered for planning of
intermodal transport chains. With this tool we
are able to create network of possible transport
connections and choose the best alternative
route for the Customer and create a complete
transport chain with estimated schedule and costs.
Application for planning intermodal transport
chains
5
Intermodality and Interoperability around the
Baltic Sea
Main user roles of the application for planning
intermodal transport chains
Users
TCM Office
Service Providers
Customers
System Administrators
6
Intermodality and Interoperability around the
Baltic Sea
TCM Office

• TCM Office thats the main role in the planning
  system they are 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.
• From the planning point of view it doesnt matter
  who is a TCM office.

LSP
Freight Integrator
Authority
Shipper
TCM Office
7
Logistics 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
Sea shipping company
Road transport company
Message broker
Air transport company
Application for planning intermodal transport
chains
WWW
Other services
Ports
Insurance company
Logistics provider - warehousing
8
Intermodality and Interoperability around the
Baltic Sea
Customers
These users are the customers of TCM Office and
they want 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 an electronic messages. Sometimes
the TCM enters the information for the customer.
When doing 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
9
(No Transcript)
10
Intermodality and Interoperability around the
Baltic Sea
Reference Data
Before the planning process can start. System has
to be provided with some 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

11
Intermodality and Interoperability around the
Baltic Sea
Register Provider Services
Logistics service provider is registering its
services in the system. The service later will be
used 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.
12
Intermodality and Interoperability around the
Baltic Sea
Register Service Provider
The registered services should be filled with all
required information during planning process

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

13
Intermodality and Interoperability around the
Baltic Sea
Build 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 very specific place like
Port in Gdansk for example and also in more
general location like city or country. Chain
templates can have many alternative routes with
different transport modes. Different routes are
presented graphically on the screen.
14
Intermodality and Interoperability around the
Baltic Sea
Build 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.
15
Intermodality and Interoperability around the
Baltic Sea
Pre-Calculation of Routes in Transport Templates
In this stage a TCM Office creates a
precalculation with 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
16
Pre-Calculation of Routes in Transport Templates
We can have different alternatives for the
customer and present him precalculation for all
of them.
Comparing pre-calculation
17
Intermodality and Interoperability around the
Baltic Sea
Register Customer Service
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
18
Customer booking
This is a stage where finally we 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
19
Customer booking
Checking and entering the load units
Load unit hierarchy E.g. Pallets in Containers
20
Intermodality and Interoperability around the
Baltic Sea
Customer booking
Transport chain details
21
Handle Provider Bookings
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 re-plan the chain.
Provider booking request and confirmation
22
Summary

• We have 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

23
Intermodality and Interoperability around the
Baltic Sea
Part II Demonstration scope and planning
WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
24
Intermodality and Interoperability around the
Baltic Sea

• - Input from WP4 -
• NECL (North East Cargo Link)
• What are the exact planning requirements?
• Objectives
• Time horizon (strategic/tactical/operational)
• Focus (infrastructure/services)
• Level of detail
• Portal requirements?
• Handle transport outside corridor
• Critical mass ( users/providers in catchment
  area)
• Phase (planning/execution)
• Critical Material flow information flow (TT)
• Free capacity / available volumes (AT Kearney)
• Available information?
• Services
• Duration/price tables
• Cost/pricing

WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
25
Intermodality and Interoperability around the
Baltic Sea

• - Input from Questionnaires -
• Questionnaires feedback
• GVZ
• Focus Infrastructure
• Region Baltic
• Type Logistics locations
• Remarks -
• Lahti
• Focus Services (on request)
• Region Finland
• Type All
• Remarks No price information
• Szczecin
• Focus Services (on request)
• Region NW Poland
• Type SSS, terminals/warehouses
• Remarks Detailed timing?
• Banverket

WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
26
Intermodality and Interoperability around the
Baltic Sea
Seafood
Step 1 Identification of 3 corridors
NECL
Asia corridor
WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
27
Intermodality and Interoperability around the
Baltic Sea
Step 2a Structure of corridor 1 NECL
NECL
Rail
Rail
SSS
SSS
SSS
Rail
Rail
WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
28
Intermodality and Interoperability around the
Baltic Sea
Seafood
Step 2b Structure of corridor 2 Seafood
Rail
Rail
Rail
Rail
SSS
SSS
SSS
Rail
Rail
Rail
Rail
WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
29
Intermodality and Interoperability around the
Baltic Sea
Step 2c Structure of corridor 3 Asia corridor
Rail
Rail
SSS
Rail
Asia corridor
SSS
Rail
Rail
Comparison of deep sea route with transsiberian
route
Deap sea shipping
WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
30
Intermodality and Interoperability around the
Baltic Sea
narvik bodo
Step 3 Potential hubs catchment areas
trondheim
turku kotka kasko hamina
sundsvall
karlskrona karlshamn trelleborg
klaipeda ventspils
hamburg luebeck rostock
szczecin gdynia gdanisk
WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
31
Intermodality and Interoperability around the
Baltic Sea
Ban- verket
Step 4 Information suppliers
Lahti
NECLA
AED
FDT
Gda
TuT (Ham)
Szcz
ILIM
GVZ
Wismar
WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
32
Intermodality and Interoperability around the
Baltic Sea

• Responsibilities
• (support indicated by ltgt)
• AED
• Rail services in Latvia/Lithuania and connections
  to Russia ltFDTgt
• Short sea services Latvia/Lithuania ltSSS
  Promotion Centergt
• Banverket
• Rail services Sweden ltRail Operatorsgt
• GVZ
• Rail services from Luebeck ltTZL, Hamburg Hafen
  Marketing gt
• ILIM
• Cesar portal (U.I.R.R.) for rail services ltFKgt
• Lahti
• Case leader Asia corridor ltFDTgt
• Rail services Finland
• Short sea services Finland ltSSS Promotion Center,
  WP4gt
• Port Authority of Szczecin
• 3 most important rail operators in Poland ltILIMgt
• Short sea services Poland ltSSS Promotion Centergt

Partners collecting information on rail services
will also collect information on related -
terminal services - shunting services - pre/on
carriage by road
Also to be included are (in specific case)
services that are under development but not yet
available
No price information will be collected, as the
pilot demonstration will focus on lead time
WP3 Workshop Interbaltic Hamburg 21- 22 March 2007
33
Intermodality and Interoperability around the
Baltic Sea

• Steps to take
• 30/3-Case scope definition by case owners
• Definition of catchment area (origin,
  destination)
• Selection of hubs (ports, inland hubs)
• Identification of cargo owner(s), potential cargo
  volume
• Selection of load unit type, (if applicable)
  transport equipment
• 6/4-Guideline by ILIM
• Prepare easy-to-use guideline on scope,
  information collection and data entry (incl.
  formats)
• Populate the system with basic reference
  information
• GoToMeeting session on 10th April 1000-1200 to
  demonstrate guideline
• Start information collection in April
• Establish contacts as from 30/3 for data
  collection
• Start actual collection and input as from 9/4 (3
  weeks)
• Continuous quality control helpdesk
• 30/4-Evaluation end of April
• Readjusting demonstration planning and selection
  of presented case for workshop in June
• Second step in information collection in May
• Complete collection of all information

WP3 Workshop Interbaltic Hamburg 21- 22 March 2007