OPTIRAILS II

1
OPTIRAILS II
THEMIS Clustering meeting Optirails II
project Dick Mans Brussels November 20, 2001
2
Overview

• Introduction
• Partners
• Focus Scope
• Workplan current status
• Optirails architecture main actors
• Business models example
• Traffic information
• Freight management information
• Integration traffic and freight information

3
Introduction

• Optimisation of Traffic through ERTMS/ETML
• Fifth Framework project
• UIC and EC DG TREN - Transport/Energy
• Two year project, started in May 2000

4
Partners

• Systra (F)
• Halcrow group (UK)
• Scanrail (DK)
• FS (I)
• Trademco (GR)
• CFF/SBB (CH)
• SCNF (F)
• CSEE (F)
• RENFE (S)

• EPFL (CH)
• STERIA (F)
• TIFSA (S)
• SWEDERAIL (SW)
• TRANSURB (B)
• VTT (FN)
• NEI (NL)

5
ERTMS/ETML

• European Rail Traffic Management System (ERTMS)
• European Traffic Management Layer (ETML)
• Levels of response time in rail traffic
  management
• Level 1 Timetables (12/6 months)
• Level 2 Short notices (30 days)
• Level 3 Contingencies (1 day before)
• Level 4 real time (few hours) OPTIRAILS
• Level 5 reactive planning

0PTIRAILS
6
Focus scope

• FOCUS
• The development and functional validation of an
  international rail traffic management system.
• SCOPE
• The main objective is to create trans-European
  traffic management facilities devoted to
  international traffic.

7
Workplan current status

• Functional requirement specification (finished)
• Cost-benefit analysis (finished)
• System requirements specification
• Functional demonstrator (finished)

8
Main actors

• Infrastructure Managers (IM)
• Train Operating Companies (TOC)
• One Stop Shop (OSS)

9
Optirails Architecture

• Four options
• Off-line data monitoring
• Centralised information supply
• Negotiated path assembly
• Problem detection and solving

10
Business models

• Step 1 Monitoring model (reporting)
• Step 2 Information model (answers)
• Step 3 Advising Model (advices)
• Step 4 Supervision model (recommendations)
• Step 5 Managerial model (directives)

11
Example

• Train from the Netherlands to Italy delayed in
  the Netherlands.
• Current situation in Italy aggregated delay
• With Optirails delay solved in Germany, no delay
  in Italy

12
Traffic information

• Train position information (OF211)
• Delay information (OF115)
• Information about actual status of the rail
  network (OF212)
• Information about a planned reduction in
  infrastructure (OF216)

13
Freight information

• Actual train load of freight train (OF124)
• Planned routes for the freight trains (OF213)
• Estimated times of arrival (OF218)

14
Integration traffic and freight

• Several obstacles
• Work involved in integrating national system with
  Optirails
• Standardised UIC catalogue of messages not yet
  implemented in many countries
• Some information is sensitive
• End users have contracts with TOC, not IM.