Technologies        
  Hauptmenu
 
    Introduction
    Database
    -  Technologies
  -  Projects
    Calendar
    Discussions
    Contact & Links
    Imprint & Disclaimer
    Sitemap
 
 


     
 
Content
 
back to list go back to technology list      previous previous technology  next technology  next

   Driving advice systems in suburban operation  evaluated  
Driving advice systems are on-board tools giving recommendations to drivers for a more energy efficient driving style. In suburban operation the main saving strategy is coasting, i.e. switching off traction as early as possible before stations.
Technology field: Energy efficient driving
close main section General information
  close sub-section Description
   

Principle

The driving pattern, e.i. the speed over time diagram, has a considerable influence on the energy consumed by a train on a given trip. For given restrictions (timetable, stops, speed restrictions on the way and installed traction power) a shortest time driving strategy can be determined, which is basically given by

  • Full acceleration up to maximum speed given either by speed limit or by maximum traction power
  • Speed holding at maximum speed until train has to start braking
  • Braking at the latest possible point in order to come to a stop when reaching the station

Time tables usually include a recovery time added to the minimal running time to allow for short delays. This recovery time is normally between 5 and 12% of the minimal running time.

This recovery time allows to apply different driving strategies which save energy in comparison with the shortest time driving strategy. Depending on their experience and skill, many drivers have always used timetable buffers to apply a more energy efficient driving style. Today, driving advice systems (DAS) exist that calculate (and continuously update) the optimum driving strategy much more exactly than any driver could. They are based on train positioning (GPS, Galileo or other), train, track and timetable data as well as algorithms to calculate driving recommendations.

The situation in suburban networks

In suburban service, good saving effects can be achieved by coasting only. In contrast to driving advice systems in main line operation, a continuous calculation of the optimal train speed on the remaining trip to the next station is not reasonable, given the short average distance between stations in local networks. Driving advice systems for local networks can therefore be limited to giving coasting recommendations, telling the driver when to shut off the traction motors in order to reach the station on time. Usually a suburban DAS only foresees one coasting phase directly before the next stop but no intermediate coasting on the way (as may occur for DAS in main line operation).

Components of a DAS

A DAS requires essentially the following on-board components:

  • Storage medium storing all the relevant data for an individual trip (infrastructure data, vehicle data, time table)
  • Information system monitoring driving time and train position
  • Computer unit using the above data to determine driving strategies and display them to the driver

Several issues have to be resolved in a satisfying manner in order for DAS to be operable, reliable and safe:

Train positioning

Train position is essential for the calculation of driving recommendations. For driving advice systems on main lines a number of methods for train positioning exist. In suburban networks the wheel impulse counters (odometers) are usually sufficient. They count the number of revolutions of several driven axles. In order to correct errors caused by wheel slippage the position is updated at regular stops in stations. This method is very accurate in local operation due to frequent updating in stations.

Data supply

A DAS requires different classes of data to be updated in different time intervals:

  • Permanent data: Vehicle data
  • Long-term data: Track data base (to be updated annually)
  • Mid-term data: Time table
  • Short-term data: Data on temporary low-speed sections (to be updated daily or even in real-time), future options may include actual weather and track conditions as well.

The Siemens Metromiser

Siemens and the Technical University Berlin have developed the Metromiser, a driving advice system for for light-rail, suburban and metro systems. The algorithms were partly taken from earlier projects at University of South Australia at Adelaide. The Metromiser consists of two components: an off board timetable optimiser (TTO) and an on-board unit (OBU):

  • The timetable optimiser is an off-board based software program (running on Windows NT) checking the energy efficiency of timetables. Using basic data (acceleration, rolling behaviour of the train, topology, passenger flows etc) it draws up a new energy-optimised timetable fitting in with the existing running schedule of the railway network.
  • The on-board unit converts the data into driving recommendations such as: “make full use of permitted speed”, “coast” or “brake”. The OBU has learning capacity: the specific rolling qualities of the individual vehicle (which may differ even within one vehicle class) are recorded and used for the calculation of further recommendations.

All data are stored on-board on a flash disk. They are automatically updated via a W-LAN at several stations.

open main section General criteria
close main section Environmental criteria
  open sub-section Impacts on energy efficiency:
  Energy efficiency potential for single vehicle: > 10%
  Energy efficiency potential throughout fleet: > 5%
  Other environmental impacts: neutral
close main section Economic criteria
  close sub-section Vehicle - fix costs: low
    Siemens negotiates the price for the introduction of Metromiser system in a network on a case-to-case basis. The on-board units are cheap, main cost factors are the tailored character of the implementation (track data has to be manually entered into the system) and the development costs of the software.
  Vehicle - running costs: significant reduction
    If an automated and radio based data supply and updating is in place, additional operating costs are almost negligible.
  Infrastructure - fix costs: low
    There are generally no major infrastructure measures needed. However, a data supply infrastructure to update on-board data is required.
  Infrastructure - running costs: unchanged
    (no details available)
  Scale effects: medium
   

Hardware

The price of the on-board units will show certain, but no major scale effects, if DAS become a wide-spread application.

Software development

Major scale effects in mid-term.

  Amortisation: 2 - 5 years
    Siemens guarantees an amortisation of the Metromiser within a maximum of 3 years.
no data available Application outside railway sector (this technology is railway specific)
close main section Overall rating
  close sub-section Overall potential: very promising
  Time horizon: mid-term
    Both the algorithms and the technological implementation of DAS for suburban operation have reached a mature stage. First in-service testing have proven technical and operational feasibility. Energy savings are lower than theoretically predicted but still very high. There has been reiterated interest on part of many operators world-wide but the eventual introduction meets various barriers such as variable acceptance by drivers and scepticism about the effectiveness and payback of the system. Even so, technical obstacles are generally smaller than in main line operation and the diffusion of DAS into suburban operation seems likely in mid to long term.
References / Links:  Baier 2001;  Linder 2000
Attachments:
Related projects:
Contact persons:
 date created: 2002-10-09
 
 
© UIC - International Union of Railways 2003
 
Aktionmenu
 
 Your contribution
   add technology
 Views of this page
   show overview
   show evaluation
   show details
 Print options
   print data sheet
   print screen
 Help
   Evaluation briefing
   Technology list
    French - German