Thematic Network on Intelligent freight Transport Systems

1

• Thematic Network on Intelligent freight Transport
  Systems

Ronald Jorna
2
Contents of presentation

• THEMIS Mission Statement
• THEMIS objectives
• How will the industry benefit from ITS?
• What can THEMIS offer?
• Achievements to date
• How to get involved in THEMIS?
• THEMIS Network partners
• Contact details

2
3
THEMIS

• THEMIS is a Thematic Network of industry and
  research professionals, that looks at the place
  of Freight Transport within the European
  Intelligent Transport Systems (ITS).

3
4

• Contributing to the development of Intelligent
  Freight Transport Systems
• in Europe
• Creating a network of relevant parties
• Disseminating relevant information

4
5

• Better forecast of Estimated Time of Arrival
  (ETA)
• Improved information on real time, actual and
  statistical traffic information in freight
  transport
• Better co-operation across modes
• resulting in
• higher efficiency
• reduced costs
• better customer service

5
6

• Clustering
• Overview of relevant 4th and 5th FP projects
  (GROWTH, IST, TEN TELECOM)
• Identification of relevant aspects of projects
  (mode, systems, functions, actors covered,
  architecture, TMS/FTMS integration, etc.)
• Two clustering reports submitted, third report in
  progress

6
7

• Working Groups
• WG1 State of the art of Traffic Management
  environment (actors, functionality, information)
• WG2 State of the art of freight transport and
  ICT and the need for Traffic Management
  information
• WG3 Freight Functional Framework
• Identification of business cases

7
8

• Architecture
• Review of previous architecture projects
• Identification of relevant aspects (mode,
  functions, actors, type of architecture covered)
• Report and spreadsheet (on website)
• Standardisation
• Review of standardisation procedures and bodies
• Overview of relevant (pre)standards
• Identification of areas for future action
• First deliverable submitted

8
9

• Participate in Clustering meetings
• Participate in Concertation meetings
• Participate in Working Groups
• Make use of Electronic information means
• Become Associated Member

9
10

• Advantages
• Continuous up-to-date through electronic media
• Invitations for clustering and concertation
  meetings
• Free of charge
• How to register?
• Send e-mail to ronald.jorna_at_ecorys.com
• Leave business card at registration desk.

11
ECORYS/NEI Transport Ronald Jorna phone
31-10-4538796 fax [phone] e-mail
ronald.jorna_at_ecorys.com http//themis-network.or
g
11
12

• A Thematic Network is
• an activity initiated by the European Commission
• to co-ordinate ongoing activities for research,
  development and deployment
• to provide a forum for dissemination and
  concertation activities among all parties
  involved.

13
Source DG TREN
14

• Recommending how to link different ICT systems
• Traffic Management Systems with Freight Transport
  Management Systems
• Traffic Management Systems across modes (where
  relevant for freight transport)
• Freight Transport Management Systems along the
  transport chain

15
(No Transcript)
16
CLUSTERING (T2.3)
Working Group 1 (T2.4) Description of Traffic
Management environment
Working Group 2 (T2.5) Description of Freight
Transport environment
Current status of standardisation (T3.3)
Existing system architectures (T3.1)
Business cases for integrated systems
NETWORK MANAGEMENT (WP1, T2.1)
Working Group 3 Architecture Framework (T3.2)
Working group 3 Detailed design (T3.2)
Implementation scenarios (T4.1)
Standardisation proposals (T4.3)
Framework feasibility (T3.4)
Business case feasibility (T3.4)
Recommendation future work (T4.4)
Identification of gaps/ missing links (T4.2)
CONCERTATION (T2.2)
NETWORKING AND DISSEMINATION (WP5)
17

• Users
• Shippers, forwarders, transport companies,
  terminal operators
• Providers
• System providers, service providers
• Authorities
• Traffic Information Centres, infrastructure
  operators, customs, control authorities, policy
  makers
• Other 5FP projects and networks
• DG TREN, DG INFOSOC

18

• Clustering/concertation meetings
• Every 6 months information exchange with users,
  providers, authorities and relevant 5FP project
  representatives
• Electronic means
• Website www.themis-network.org
• Electronic newsletter
• Ad hoc meetings with interesting initiatives
• Private market, EU funded projects, conferences,
  workshops, etc.

19
To co-ordinate 4th and 5th framework Programme
projects and national projects related to freight
transport and traffic management
20
To interact with all relevant parties in the
field of traffic management and/or freight
transport management
21
To analyse certain issues in more detail for
further discussion in clustering and/or
concertation meetings
Working Group activities
Working Group 1 Traffic Management information
and data gathering to support intermodal freight
Working Group 2 ICT for developing information
support and for intermodal transport solutions
Working Group 3 Synthesis of a common intermodal
architecture framework taking account of TMS
22
To inform all relevant parties in an effective
and efficient way
Information sources
Deliverable downloads
Electronic discussion forum
Electronic newsletter
Website
23

• D1 State of the art of TMS and ICT for IFT
• D2 Inventory of RTD projects in the field of TMS
  and IFT information systems on national and EU
  level
• D3 Proposal for a feasible, user driven, system
  architecture to combine TMS and intermodal
  freight operation aspects
• D4 Specification of needs for further
  standardisation aiming at interoperable ICT
  applications for IFT
• D5 Recommendations for future work, supported by
  all relevant parties in the IFT sector
• D6 Overall dissemination activities report
• D7 THEMIS final report

24
To bring together relevant on-going EU and
national projects, to synthesise their results
and provide co-ordination of their activitities.
Objective

• inventory and monitoring projects (4/5 FP,
  national)
• building excel database
• 6-monthly meetings with relevant projects and
  parties.

Approach

• living database
• continuously updated deliverable
• clustering meetings

Output
Continuous, with meetings every 6 months.
Timing
25
To provide a state of the art overview of Traffic
Management Systems for all modes (road, rail,
waterborne, air).
Objective

• describe TMS per mode of transport in a
  descriptive, non-technical way, identify
  differences/similarities
• Describe potential for integration with FTMIS and
  with TMS in other modes
• Provide business cases for potential integration.

Approach

• section on TMS in Deliverable 1
• detailed business cases

Output
May 2001 focus on integration of TMS with
FTMIS Nov. 2002 focus on integration across
modes.
Timing
26
To provide a state of the art overview of ICT in
freight transport for all modes (road, rail,
waterborne, air) and identify user needs for TMS
and FTMIS across the chain.
Objective

• describe ICT in freight transport in a
  descriptive, non-technical way, identify
  differences/similarities
• Describe potential for integration with TMS and
  integration across the (intermodal) chain
• Provide business cases for potential integration.

Approach

• section on FTMIS in Deliverable 1
• detailed business cases

Output
May 2001 focus on integration of FTMIS with
TMS Nov. 2002 focus on integration of FTMIS
across chain.
Timing
27
To combine results of WG1 and WG2 into examples
of existing or potential cases of integration of
TMS and/or FTMIS.
Objective

• Global description of practical cases, either
  existing or potential
• More details of cases are added in course of the
  project, including architecture elements
• Assessing the feasibility of the business cases.

Approach

• Around 10 detailed business cases
• Business cases will be element of Deliverable 1.

Output
May 01 focus on integration of TMS with
FTMIS Nov. 02 focus on integration of FTMIS
across chain focus on
integration of TMS across modes.
Timing
28
To provide a technical description of the system
architecture of the business cases
Objective

• Based on global description of business cases,
  construct system architecture for business cases
  on functional level and DFDs
• Apply framework for detailed analysis of bus.
  cases.
• Use bus. cases to validate framework

Approach

• Deliverable 1 Detailed description of business
  cases.

Output
Aug 01 draft architecture of bus. cases
finished (D1) Sept. 03 final architecture of
bus. cases finished (D1).
Timing
29
To develop the outlines of a (intermodal)
framework integrating FTMIS and TMS
Objective

• Constructing generic system architectures for
  freight (1) and traffic (1 or 4), Ie. a high
  level funct. framework
• Expand framework with DFDs
• Apply framework for detailed analysis of bus.
  cases.
• Draw conclusion on need for and how to achieve
  framework

Approach

• Deliverable 3 Proposal for system architecture
• 2 or 5 system architectures on THEMIS website.

Output
Aug 01 draft architecture finished
(D3) March 03 final architecture finished (D3).
Timing
30
To review previous system architecture proposals
and relevant work. To relate such past
initiatives to the work of the THEMIS network.
Objective

• Identify relevant architecture projects from the
  past, both for freight and traffic, identify main
  characteristics
• Matching freight architectures with CEN and
  traffic architectures with other frameworks
• Build Excel database to categorise projects.

Approach

• Report on existing system architecture
  initiatives
• Excel database of arch. projects on THEMIS
  website.

Output
May 01 report finished and first version
database After May 01 regular updates of
database.
Timing
31
To review the current status of standardisation
proposals and achievements in the field of
(intermodal) freight transport and discover gaps
and necessary activities.
Objective

• Identification of areas in which standardisation
  is useful
• Identification of standardisation
  bodies/procedures
• Identification of status of (pre)standards
• Draw conclusions on gaps/necessary activities

Approach

• Internal reports presenting a review of current
  status of standardisation in (intermodal) freight
  transport.

Output
April 01 internal report Sept. 02 internal
report
Timing
32
To assess the feasibility (technical and
economic) of the generic architecture proposed in
WG3.
Objective

• For the generic architecture
• - identify likely developments
• - identify impact of development on
  implementation
• - use the results of the business cases to
  assess the
• frameworks feasibility

Approach

• Internal report with the assessment of the
  frameworks feasibility.

Output
Nov 01/March 04 internal report
Timing
33
To assess the feasibility (technical and
economic) of the business cases.
Objective

• For each business case
• - identify existing and future technological
  capabilities
• - examine potential costs and benefits

Approach

• Internal report with the assessment of the
  feasibility of the business cases.

Output
Aug 01/March 03/Sept. 03 internal report
Timing
34
To develop likely scenarios for the
implementation of interoperable ICT applications,
both for the business cases and for the generic
system architecture.
Objective

• For each business case and the generic
  architecture
• - identify likely developments
• - identify impact of development on
  implementation
• - develop one or more implementation
  scenarios for
• each business case and generic architecture

Approach

• Input to business case description (D1)
• Internal report describing scenarios for
  interoperable ICT applications.

Output
Aug 01/March 03 impl. scenarios for business
cases Nov 01/March 04 impl. scenarios for gen.
architecture.
Timing
35
To provide input for standardisation proposals.
Objective

• Analyse results of previous workpackages and draw
  conclusions on need for standardisation
• Use clustering/concertation meeting for
  validation
• Interviews with key actors (CEN, ISO, etc.)

Approach

• Deliverable D4 Needs for further standardisation
  in order to realise interoperable ICT
  applications in (intermodal) freight transport

Output

• March 02 version 1
• March 04 final version

Timing
36
To identify gaps and missing links for truly
integrated interoperable ICT applications in
(intermodal) freight transport.
Objective

• Analyse results of previous WPs and draw
  conclusions on gaps and missing links
• Use clustering/concertation meeting for
  validation
• Interviews with key actors

Approach

• Internal report identifying gaps and missing
  links for truly integrated ICT applications in
  (intermodal) freight transport.

Output
Nov 01 draft internal report March 04
final internal report.
Timing
37
To give direction to the EU and other network
participants concerning future activities.
Objective
Based on the architecture framework, its
feasibility, the gaps and missing links,
recommendations in the form of further research,
implementation schemes, demonstrator projects and
regulations will be made.
Approach

• Deliverable 5 Report with a set of
  recommendations for future work, supported by all
  relevant parties in the (intermodal) freight
  transport sector.

Output

• March 02 version 1
• March 04 final version

Timing
38
To interact with all relevant parties in the
field of traffic management and/or freight
transport management