European Train Control System

From Infogalactic: the planetary knowledge core
(Redirected from ETCS)
Jump to: navigation, search
ETCS "Eurobalise" transceiver, installed between rails, provides information to ETCS trains.

The European Train Control System (ETCS) is a signalling, control and train protection system designed to replace the many incompatible safety systems currently used by European railways, especially on high-speed lines.

ETCS requires standard trackside equipment and a standard controller within the train cab. In its final form, all lineside information is passed to the driver electronically, removing the need for lineside signals which, at high speed, could be almost impossible to see or assimilate.

The need for ETCS stems from European Union (EU) Directive 96/48 about the interoperability of high-speed trains, followed by Directive 2001/16 extending the concept of interoperability to the conventional rail system. ETCS specifications have become part of, or are referred to, the technical specification for interoperability for (railway) control-command systems, which is a piece of European legislation managed by the European Railway Agency. It is a legal requirement that all new, upgraded or renewed tracks and rolling stock in the European railway system should adopt ETCS, possibly keeping legacy systems for backward compatibility. Many networks outside the EU have also adopted ETCS, generally for high-speed rail projects.

ETCS is specified at four different levels:

  • Level 0: ETCS-compliant locomotives or rolling stock interact with lineside equipment that is non-ETCS compliant.
  • Level 1: ETCS is installed on lineside (possibly superimposed with legacy systems) and on board; spot transmission of data from track to train via ETCS balises
  • Level 2: Same as level 1, but ETCS data transmission is continuous; the currently used data carrier is GSM-R
  • Level 3: Same as level 2, but train location and train integrity supervision no longer rely on trackside equipment such as track circuits or axle counters

History

The European railway network grew from separate national networks with little more in common than standard gauge. Notable differences include voltages, loading gauge, couplings, signalling and control systems. By the end of the 1980s there were 14 national standard train control systems in use across the EU, and the advent of high-speed trains showed that signalling based on lineside signals is insufficient.[citation needed]

Both factors led to efforts to reduce the time and cost of cross-border traffic. On 4 and 5 December 1989, a working group including Transport Ministers resolved a master plan for a trans-European high-speed rail network, the first time that ETCS was suggested. The Commission communicated the decision to the European Council, which approved the plan in its resolution of 17 December 1990. This led to a resolution on 91/440/EEC as of 29 July 1991, which mandated the creation of a requirements list for interoperability in high-speed rail transport.[1] The rail manufacturing industry and rail network operators had agreed on creation of interoperability standards in June 1991.[2] Until 1993 the organizational framework was created to start technical specifications that would be published as TSI standards (Technical Specifications for Interoperability). The mandate for TSI was resolved by 93/38/EEC.[1] In 1995 a development plan first mentioned the creation of the European Rail Traffic Management System.[2]

The specification was written in 1996 in response to EU Council Directive 96/48/EC99[1] of 23 July 1996 on interoperability of the trans-European high-speed rail system. First the European Railway Research Institute was instructed to formulate the specification and about the same time the ERTMS User Group was formed from six railway operators that took over the lead role in the specification. The standardisation went on for the next two years and it was felt to be slow for some industry partners – 1998 saw the formation of UNISIG (Union of Signalling Industry), including Alstom, Ansaldo, Bombardier, Invensys, Siemens and Thales which were to take over the finalisation of the standard.[2] In July 1998 SRS5a (System Requirement Specification 5a) documents were published that formed the baseline for technical specifications. UNISIG provided for corrections and enhancements of the baseline specification leading to the "Class P" specification in April 1999.[citation needed]

The baseline specification has been tested by six railways since 1999 as part of the European Rail Traffic Management System[3] The railway companies defined some extended requirements that were included to ETCS (e.g. RBC-Handover and track profile information) leading to the Class 1 Version 2.0.0 specification of ETCS that was published in April 2000. Further specification continued through a number of drafts until UNISIG published the SUBSET-026 defining the current implementation of ETCS signalling equipment – this Class 1 Version 2.2.2 was accepted by the European Commission in decision 2002/731/EEC as mandatory for high-speed rail and in decision 2004/50/EEC as mandatory for conventional rail. The SUBSET-026 is defined from eight chapters where chapter seven defines the ETCS language and chapter eight describes the balise telegram structure of ETCS Level 1.[2] Later UNISIG published the corrections as SUBSET-108 also known as Class 1 Version 2.2.2 "+" that was accepted in decision 2006/679/EEC.[citation needed]

The earlier ETCS specification contained a lot of optional elements that limited interoperability. The Class 1 specifications were revised in the following year leading to Version 2.3.0 document series that was made mandatory by the European Commission in decision 2007/153/EEC on 9 March 2007. Annex A describes the technical specifications on interoperability for high-speed (HS) and conventional rail (CR) transport. Using Version 2.3.0 a number of railway operators started to deploy ETCS on a large scale, for example the Italian Sistema Controllo Marcia Treno is based on Level 1 balises. Further development concentrated on compatibility specification with the earlier "Class B" systems leading to specifications like EuroZUB that continued to use the national rail management on top of Eurobalises for a transitional period. Following the experience in railway operation the ERA (European Railway Agency) published a revised specification Class 1 Version 2.3.0 D ("debugged") that was accepted by the European Commission in July 2008.[citation needed]

The final ETCS (later called Baseline 2) is divided into nine[clarification needed] equipment and functional levels. The definition of the level depends on how the route is equipped and the way in which information is transmitted to the train. The movement authority (“permission to proceed”) and the corresponding route information are transmitted to the train and displayed in the cab ("cab signalling"). A vehicle fitted with complete ERTMS/ETCS equipment (EuroCab) and functionality can operate on any ETCS route without any technical restrictions.[citation needed]

While some countries switched to ETCS, German and French railway operators had already introduced a modern type of train control system so they would gain no benefit. Instead ideas were introduced on new modes like "Limited Supervision" (known at least since 2004[4]) that would allow for a low-cost variant, a new and superior model for braking curves, a cold movement optimisation and additional track description options. These ideas were compiled into a "baseline 3" series by the ERA, published as a Class 1 Version 3.0.0 proposal on 23 December 2008. The first consolidation (3.1.0) of the baseline 3 proposal was published by ERA on 26 February 2010[5] and the second consolidation (3.2.0) on 11 January 2011.[6] The specification GSM-R Baseline 0 was published as Annex A to the baseline 3 proposal on 17 April 2012.[7] At the same time a change to Annex A of baseline 2 (2.3.0d) was proposed to the European Commission that includes GSM-R baseline 0 allowing ETCS 3.3.0 trains to run on ETCS 2.3.0d tracks.[8][9] The baseline 3 proposal was accepted by the European Commission with decision 2012/88/EU on 25. January 2012 [10] and the update for ETCS 3.3.0 and the extension for ETCS 2.3.0d were accepted by the European Commission with decision 2012/696/EU on 6. November 2012.[11]

The ERA work programme concentrated on the refinement of the test specification SRS 3.3.0 that was to be published in July 2013.[12] In parallel the GSM-R specification was to be extended into a GSM-R baseline 1 until the end of 2013.[12] The German Deutsche Bahn has since announced equipping at least the TEN Corridors running on older tracks to be using either Level 1 Limited Supervision or Level 2 on high-speed sections. Current work continues on Level 3 definition with low-cost specifications (compare ERTMS Regional) and the integration of GPRS into the radio protocol to increase the signalling bandwidth as required in shunting stations. The specifications # 2 (ETCS baseline 3 and GSM-R baseline 0) were published as recommendations SRS 3.4.0 and ETCS 3.4.0 by the ERA in May 2014 for submission to the Railway Interoperability and Safety Committee in a meeting in June 2014.[13][14] The SRS 3.4.0 was accepted by the European Commission with the amending decision 2015/14/EU on 5. January 2015.[15]

Stakeholders such as Deutsche Bahn have opted for a streamlined development model for ETCS – DB will assemble a database of change requests (CRs) to be assembled by priority and effect in a CR-list for the next milestone report (MRs) that shall be published on fixed dates through ERA (European Railway Agency). The SRS 3.4.0 from Q2 2014 matches with the first MR1 from this process, the further steps were planned for the MR2 to be published in Q4 2015 (including SRS 3.5.0) and the MR3 to be published in Q3 2017 (possibly SRS 3.6.0). Each specification will be commented on and handed over to the RISC (Railway Interoperability and Safety Committee) for subsequent legalization in the European Union.[16]

In December 2015 the ERA published the Baseline 3 Release 2 (B3R2) series including GSM-R Baseline 1. The B3R2 is publicly named to be not an update to the previous Baseline 3 Maintenance Release 1 (B3MR1).[17] The notable change is the inclusion of EGRPS (GPRS with mandatory EDGE support) in the GSM-R specification, corresponding to the new Eirene FRS 8 / SRS 16 specifications. Additionally B3R2 includes the ETCS Driver Machine Interface and the SRS at version 3.5.0.[18]

Deployment planning

The development of ETCS has matured to a point that cross-border traffic is possible and some countries have announced a date for the end of older systems. The first contract to run the full length of a cross-border railway was signed by Germany and France in 2004 on the high-speed line from Paris to Frankfurt, including LGV Est. The connection opened in 2007 using ICE3MF, to be operational with ERTMS trains by 2016.[19] The Netherlands, Germany, Switzerland and Italy have a commitment to open Corridor A from Rotterdam to Genoa for freight by the start of 2015. Switzerland has announced in 2011 that it will switch from its national ZUB/Signum to ETCS Level 1 for conventional rail by enabling L1 LS packets on its transitional Euro-ZUB balises during 2017.[20]

Denmark has decided to drop its older ATC, which will reach its end of life between 2015 and 2020, switching the network of 2100 km to ETCS. The S-Bane network in Copenhagen will use the Siemens TrainGuard system. Two suppliers will equip the rest of the country to Level 2 with an option for Level 3 (ERTMS Regional) in rural parts. Implementation will be between 2014 and 2018.[21] Denmark will be the first to introduce GPRS support on its network by 2017.[22][23] Hence Banedanemark is driving this development with other ERTMS users in Europe[23] which has led to the inclusion in B3R2 in late 2015.[18]

Germany will start replacing all its PZB and LZB systems in 2015, to be finished by 2027.[24] Deutsche Bahn has expressed a commitment to keep the Baseline-3 specification backward compatible starting at least with SRS 3.5.0 which is due in 2015 according to the streamlined MR2 process, with the first MR1 adding requirements from its tests in preparation for the switch to ETCS (for example better frequency filters for the GSM-R radio equipment).[16] During 2014 it was planned to use a dual equipment for the four main freight corridors to comply with the EC 913/2010 regulation. Further testing showed that a full ETCS system can increase capacity by 5-10% leading into a new concept "Zukunft Bahn" to accelerate the deployment, presented in December 2015.[25] The overall cost reduction of about half a billion euro may be reinvested to complete the switch to ERTMS which may take about 15 years.[25] For the initial years Deutschebahn hopes to get financing from the federal level to occur after the next German federal elections in 2017.[26][27]

Non-European countries also are starting to deploy ERTMS/ETCS, including Algeria, China, India, Kazakhstan, Korea, Libya, Mexico, New Zealand, and Saudi Arabia.[28] Australia will switch to ETCS on some dedicated lines starting in 2013.[29]

Alternative implementations

The ETCS standard has listed a number of older ATC as Class B systems where the older line side signals can be read using a Specific Transmission Module (STM) and the Class B signals are fed to a new ETCS onboard safety control system for partial supervision. In practice an alternative transition scheme is used where an older ATC is rebased to use Eurobalises. This leverages the fact that a Eurobalise can transmit multiple information packets and the reserved national datagram (packet number 44) can encode the signal values from the old system in parallel with ETCS datagram packets. The older train-born ATC system is equipped with an additional Eurobalise reader that converts the datagram signals. This allows for a longer transitional period where the old ATC and Eurobalises are attached on the sleepers until all trains have a Eurobalise reader. The newer ETCS compliant trains can be switched to an ETCS operation scheme by a software update of the onboard train computer.[30]

In Switzerland a replacement of the older Integra-Signum magnets and ZUB 121 magnets to Eurobalises in the Euro-Signum plus EuroZUB operation scheme is under way. All trains had been equipped with Eurobalise readers and signal converters until 2005 (generally called "rucksack"). The general operation scheme will be switched to ETCS by 2017 with an allowance for older trains to run on specific lines with EuroZUB until 2025.[31]

Croco + TBL + ETCS balises at the same signal

In Belgium the TBL 1 crocodiles were complemented with Eurobalises in the TBL 1+ operation scheme. The TBL 1+ definition allowed for an additional speed restriction to be transmitted to the train computer already. Likewise in Luxembourg the Memor II (using crocodiles) was extended into a Memor II+ operation scheme. In the Netherlands the national ATB-EG system has been upgraded with Eurobalises in the ATB-NG system. All lines running across the border of these Benelux countries will be switched to ETCS by 2020 and the core network will be switched to ETCS by 2030.[30]

In Berlin the old mechanical train stops on the local S-Bahn rapid transit system are replaced by Eurobalises in the newer ZBS train control system. Unlike the other systems it is not meant to be transitional for a later ETCS operation scheme. The signalling centres and the train computer use ETCS components with a specific software version, manufacturers like Siemens point out that their ETCS systems can be switched for operating on ETCS, TBL, or ZBS lines.[30]

Levels of ETCS

Level 0

Level 0 applies when an ETCS-fitted vehicle is used on a non-ETCS route. The trainborne equipment monitors the maximum speed of that type of train. The train driver observes the trackside signals. Since signals can have different meanings on different railways, this level restricts drivers to one railway. If the train has left a higher level ETCS, it might be limited in speed globally by the last balises encountered.

Level 1

ETCS Level 1 schematic

Level 1 is a cab signalling system that can be superimposed on the existing signalling system, leaving the fixed signal system (national signalling and track-release system) in place. Eurobalise radio beacons pick up signal aspects from the trackside signals via signal adapters and telegram coders (Lineside Electronics Unit – LEU) and transmit them to the vehicle as a movement authority together with route data at fixed points. The on-board computer continuously monitors and calculates the maximum speed and the braking curve from these data. Because of the spot transmission of data, the train must travel over the Eurobalise beacon to obtain the next movement authority. In order for a stopped train to be able to move (when the train is not stopped exactly over a balise), there are optical signals which show permission to proceed. With the installation of additional Eurobalises ("infill balises") or a EuroLoop between the distant signal and main signal, the new proceed aspect is transmitted continuously. The EuroLoop is an extension of the Eurobalise over a particular distance which basically allows data to be transmitted continuously to the vehicle over cables emitting electromagnetic waves. A radio version of the EuroLoop is also possible.

For example, in Denmark and Sweden the meanings of single green and double green are contradictory. Drivers have to know the difference (already with traditional systems) to drive beyond the national borders safely. In Sweden, the ETCS Level 1 list of signal aspects are not fully included in the traditional list, so there is a special marking saying that such signals have slightly different meaning.[32]

Deployment

In Croatia, Croatian Railways deployed Level 1 on the VinkovciTovarnik line in 2012.[33]

In Hungary, the BudapestHegyeshalom and ZalacsébHodoš lines are equipped with Level 1.[citation needed]

In Poland, Level 1 was installed in 2011 on the CMK high-speed line between Warsaw and Katowice-Kraków, to allow speeds to be raised from 160 km/h (99 mph) to 200 km/h (124 mph), and eventually to 250 km/h (155 mph).[34] The CMK line, which was built in the 1970s, was designed for a top speed of 250 km/h but was not operated above 160 km/h due to lack of cab signalling. The ETCS signalling on the CMK was certified on 21 November 2013,[35] allowing trains on the CMK to operate at 200 km/h (124 mph).[36]

In Slovakia, the system has been deployed as part of the BratislavaKošice mainline modernisation program, currently between Bratislava (east of Bratislava-Rača station) and Nové Mesto nad Váhom, with the rest of the line to follow. The current implementation is limited to 160 km/h due to limited braking distances between the control segments.[citation needed]

In northeast China, Level 1 is deployed on the Beijing–Tianjin Intercity Rail line.

In Auckland, New Zealand, the first true ETCS Level 1 system in the Southern Hemispehere was commissioned on 29 April 2014 for KiwiRail by Siemens Rail Automation, in conjunction with the introduction of the ETCS-compliant AM class electric multiple units.[37] Implementation in Adelaide, SA is planned for mid/late 2014.[citation needed]

Limited Supervision

The ETCS Corridor A will mostly be using Level 1 Limited Supervision.

Limited Supervision mode allows the ETCS cab computer to disregard some information in comparison to the traditional Full Supervision mode. Formally this is possible for all ETCS levels but it is most commonly used with Level 1 – specifically the ETCS equipment is only used to control the safety restrictions while the communication of a Movement Authority is left to other systems. This allows older tracks to be rebuilt by adding ETCS L1LS equipment where Movement Authority is derived from the existing lineside equipment or radioed by GSM-R. Studies have shown that ETCS L1LS has the same capacity as plain Level 1 for half the cost which has led to railway operators pushing for the inclusion of Limited Supervision into the ETCS standard (Version 3.0.0+).

Limited Supervision mode was proposed by RFF/SNCF (France) based on a proposal by SBB (Switzerland). Several years later a steering group was announced in spring 2004. After the UIC workshop on 30 June 2004 it was agreed that UIC should produce a FRS document as the first step. The resulting proposal was distributed to the eight administrations that were identified: ÖBB (Austria), SNCB/NMBS (Belgium), BDK (Denmark), DB (Germany), RFI (Italy), CFR (Romania), Network Rail (UK) and SBB (Switzerland). After 2004 German Deutsche Bahn took over the responsibility for the change request.[38]

In Switzerland the Ministry of Transport BAV announced in August 2011 that beginning with 2018 the Eurobalise-based EuroZUB/EuroSignum signalling will be switched to Level 1 Limited Supervision.[39] High-speed lines are already using ETCS Level 2. The north-south corridor will be switched to ETCS by 2015 according to international contracts regarding the TEN-T Corridor-A from Rotterdam to Genoa (European backbone).[40]

Level 2

ETCS Level 2 schematic
Radio Block Centre (RBC)

Level 2 is a digital radio-based system. Movement authority and other signal aspects are displayed in the cab for the driver. Apart from a few indicator panels it is therefore possible to dispense with trackside signalling. However, the train detection and the train integrity supervision still remain in place at the trackside. Train movements are monitored continually by the radio block centre using this trackside-derived information. The movement authority is transmitted to the vehicle continuously via GSM-R together with speed information and route data. The Eurobalises are used at this level as passive positioning beacons or "electronic milestones". Between two positioning beacons the train determines its position via sensors (axle transducers, accelerometer and radar). The positioning beacons are used in this case as reference points for correcting distance measurement errors. The on-board computer continuously monitors the transferred data and the maximum permissible speed.

Deployment

In July 2009 the European Commission announced that ETCS is mandatory for all EU funded projects that include new or upgraded signalling, and GSM-R is required when radio communications are upgraded.[41] Level 2 installations in Switzerland, Italy, the Netherlands, Germany, France, Sweden, and Belgium are operational.[42]

In Switzerland, ETCS Level 2 is installed on the Mattstetten-Rothrist new line, a high-speed line opened in 2004 between Bern and Zürich for train speeds of 200 km/h (124 mph) whose ETCS Level 2 installation was the pioneering ETCS installation in Switzerland. Technical problems with the new ETCS technology caused ETCS operation to be put off past the planned starting date of December 2004, and ETCS Level 2 operation was fully implemented in March 2007.[43]

In Belgium, ETCS Level 2 is installed on the LGV 3 and LGV 4 high-speed lines.

In Denmark, plans were announced in December 2008 for the conversion of its entire national network to Level 2. This was necessitated by the near obsolete nature of parts of its network. The total cost of the project is estimated at €3.3bn, with conversion beginning in 2009 and projected for completion in 2021.[44]

In Italy, Level 2 is used on the Rome–Naples high-speed line opened in December 2005.

In Spain, Level 2 was commissioned on the Madrid-Barcelona high-speed rail line in October 2011, allowing the speed to be raised to 310 km/h (193 mph) with Madrid-Barcelona travel times reduced to 2 hours 30 minutes.[45]

In Sweden, the Bothnia Line was inaugurated in August 2010 using Level 2.

In Hungary Level 2 is under construction in the Kelenföld-Székesfehérvár line as a part of a full reconstruction, and planned to be ready before 2015.

In Poland, Level 2 has been installed as part of a major upgrading of the 346 km Warsaw-Gdańsk-Gdynia line which reduced Warsaw - Gdańsk travel times from 5 hours to 2 hours 39 minutes in December 2015.[46] Level 2 has been installed on line E30 between Legnica – Węgliniec – Bielawa Dolna on the German border [47] and is being installed on the Warsaw-Łódź line.[48]

In Turkey, Level 2 is installed on the Ankara–Konya high-speed line designed for 250 km/h (155 mph).[49] The new 306 kilometres (190 mi) high-speed line has reduced Ankara-Konya travel times from 10-1/2 hours to 75 minutes.[50]

In China, Level 2 is deployed on the 1,000 km Wuhan–Guangzhou High-Speed Railway.[51]

In Wales, Level 2 began to be used by passenger trains on the Cambrian Line in October 2010; this is a trial before wider deployment across Great Britain.[52] In 2013, a Network Rail class 97/3 locomotive with Hitachi's Level 2 onboard equipment successfully completed demonstration tests.[53]

In Libya, Ansaldo STS was awarded a contract in July 2009 to install Level 2.[54]

In Israel ETCS Level 2 will begin replacing PZB in 2018. Three separate bids are being issued in 2016 for this purpose (one contract each will be awarded for track-side infrastructure, rolling-stock integration, and GSM-R equipment).[55]

Level 3

ETCS Level 3 schematic

With Level 3, ETCS goes beyond pure train protection functionality with the implementation of full radio-based train spacing. Fixed train detection devices (GFM) are no longer required. As with Level 2, trains find their position themselves by means of positioning beacons and via sensors (axle transducers, accelerometer and radar) and must also be capable of determining train integrity on board to the very highest degree of reliability. By transmitting the positioning signal to the radio block centre it is always possible to determine which point on the route the train has safely cleared. The following train can already be granted another movement authority up to this point. The route is thus no longer cleared in fixed track sections. In this respect Level 3 departs from classic operation with fixed intervals: given sufficiently short positioning intervals, continuous line-clear authorisation is achieved and train headways come close to the principle of operation with absolute braking distance spacing (“moving block”). Level 3 is currently under development. Solutions for reliable train integrity supervision are highly complex and are hardly suitable for transfer to older models of freight rolling stock. Some kind of End-of-train device is needed.

ERTMS Regional

A variant of Level 3 is ERTMS Regional, which has the option to be used with virtual fixed blocks or with true moving block signalling. It is possible to use train integrity supervision, or by accepting limited speed and traffic volume to lessen the effect and probability of colliding with detached rail vehicles. ERTMS Regional has lower commissioning and maintenance costs since trackside train detection devices are not routinely used, and is suitable for lines with low traffic volume.[56][57] These low-density lines usually have no automatic train protection system today, and thus will benefit from the added safety.

As a pilot, the railway between Malung and Borlänge (West Dalarna Line) in Sweden is operating with ERTMS Regional, in full operation from February 2012. In November 2010 demonstration runs were started using ERTMS Regional, attended by foreign visitors, for example from Network Rail.

GNSS-2

Instead of using fix-data balises to detect train location there may be "virtual balises" based on satellite navigation and Differential GPS as it was researched by the UIC (GADEROS/GEORAIL) and ESA (RUNE/INTEGRAIL).[58] The introduction depends on the future functionality of the EGNOS-supported Galileo satellite system. Experiences in the LOCOPROL project show that real balises are still required in railway stations, junctions, and other areas where greater positional accuracy is required. The successful usage of satellite navigation in the GLONASS-based Russian ABTC-M block control has triggered the creation of the ITARUS-ATC system that integrates Level 2 RBC elements – the manufacturers Ansaldo STS and VNIIAS aim for certification of the ETCS compatibility of this system.[59]

Ansaldo STS has come to lead the UNISIG workgroup on GNSS integration into ERTMS.[60] There is a pilot project "ERSAT" running since 2013 on 50 km of track of the Cagliari–Golfo Aranci Marittima railway on Sardinia.[61] The proposed Shift²Rail project will integrate Galileo satellites as soon as they come operational in 2014/2015 to test the EGNOS services providing "virtual balises" that meet SIL4 safety of life criteria.[61]

Train-borne equipment EVC and STM

European trains will be fitted with an ERTMS on-board system composed of a computer (EVC) and its peripheries, as the ERTMS system is deployed on rail networks throughout Europe. At this moment only certain corridors have been fitted for ERTMS. Trains running on these lines must therefore be equipped to run on both ERTMS lines and classic lines, which still rely on national (Class B) systems. Such a dual system is called a Eurocab. A STM (Specific Transmission Module) is a key element within the Eurocab. The STM handles the national Class B Automatic Train Protection Systems like PZB, Memor, ATB.

Operation modes in ETCS

Modes during a cab change under ETCS Level 2

Full supervision

  • Front – the locomotive pulls the train, ETCS has all required information
  • Propelling – the locomotive pushes the train, ETCS must be aware that the front portion of the train will enter the block before the locomotive

Partial supervision

  • Unfitted – the line is not fitted with ETCS: the system will only observe master speed limit and train protection is left to older systems
  • Post Trip – the train overpassed the order to stop, full braking will be executed
  • On Sight – on-sight ride
  • Staff Responsible – the driver was granted permission to pass faulty signals
  • Banking – the engine is helping a train by pushing it
  • Lost – lack of information from trackborne ETCS equipment

Multiworking

  • Non Leading – second locomotive with its own driver
  • Sleeping – second locomotive controlled from the leading one
  • Rear Integrity – a locomotive at the train's rear controls its integrity (for Level 3)
  • Transport – dead locomotive being transported

Shunting

  • Shunting – shunting

On/off modes

  • Start Up – power up self test
  • Data Entry – driver enters data regarding the train (weight, length, Vmax)
  • Power Off – shutdown

Failures

  • System Failure – trainborne ETCS equipment detected its failure
  • System Isolation – driver disconnected ETCS

ETCS test laboratories

Three ETCS test laboratories work together to bring support to the industry:

To be a reference laboratory ERA is requesting the laboratories to be accredited ISO17025.

ETCS corridors

Based on the proposal for 30 TEN-T Priority Axes and Projects during 2003, a cost/benefit analysis was performed by the International Union of Railways (UIC), presented in December 2003.[62] This identified ten rail corridors covering about 20% of the TEN network that should be given priority in changing to ETCS, and these were included in decision 884/2004/EC by the European Commission.[63]

In 2005 the UIC combined the axes into the following ERTMS/ETCS Corridors, subject to international development contracts:[64][65]

  • Corridor A: Rotterdam – Duisburg – Basel – Genoa
  • Corridor B: Naples – Bologna – Innsbruck – Munich – Berlin – Stockholm
  • Corridor C: Antwerp – Strasbourg – Basel/Antwerp – Dijon – Lyon
  • Corridor D: Valencia – Barcelona – Lyon – Turin – Milan – Trieste – Ljubljana – Budapest
  • Corridor E: Dresden – Prague – Vienna – Budapest – Constanta
  • Corridor F: Aachen – Duisburg – Hanover – Magdeburg – Berlin – Poznań – Warsaw – Belarus

The Trans-European Transport Network Executive Agency (TEN-T EA) publishes ERTMS funding announcements showing the progress of trackside equipment and onboard equipment installation.[66]

  • Corridor A gets trackside equipment January 2007 – December 2012 (2007-DE-60320-P German section Betuweroute – Basel), June 2008 – December 2013 (2007-IT-60360-P Italian section). The Betuweroute in the Netherlands is already using Level 2 and Switzerland will switch to ETCS in 2015.
  • Corridor B, January 2007 – December 2012 (2007-AT-60450-P Austrian part), January 2009 – December 2013 (2009-IT-60149-P Italian section Brenner – Verona).
  • Corridor C, May 2006 – December 2009 (2006-FR-401c-S LGV-Est).
  • Corridor D, January 2009 – December 2013 (2009-EU-60122-P Valencia – Montpellier, Torino – Ljubljana/Murska).
  • Corridor E, June 2008 – December 2012 (2007-CZ-60010-P Czech section), May 2009 – December 2013 (2009-AT-60148-P Austrian section via Vienna).
  • Corridor F, January 2007 – December 2012 (2007-DE-60080-P Aachen – Duisburg/Oberhausen).

Corridor A has two routes in Germany – the double track east of the Rhine (rechte Rheinstrecke) will be ready with ETCS in 2015 (Emmerich, Oberhausen, Duisburg, Düsseldorf, Köln-Kalk, Neuwied, Oberlahnstein, Wiesbaden, Darmstadt, Mannheim, Schwetzingen, Karlsruhe, Offenburg, Basel), while the upgrade of the double track west of the Rhine (linke Rheinstrecke) will be postponed.

Corridor F will be developed in accordance with Poland as far as it offers ETCS transport: Frankfurt – Berlin – Magdeburg will be ready in 2012, Hanover to Magdeburg – Wittenberg – Görlitz in 2015. At the other end Aachen to Oberhausen will be ready in 2012, the missing section from Oberhausen to Hanover in 2020. The other two corridors are postponed and Germany chooses to support the equipment of locomotives with STMs to fulfill the requirement of ETCS transport on the corridors.[24]

Future

GSM is no longer being developed outside of GSM-R, the manufactures have committed to supplying GSM-R till at least 2030. The ERA is considering what action is needed to smoothly transition to a successor system.[67]

See also

References

  1. 1.0 1.1 1.2 Directive 96/48/EC99 of 23 July 1996 amending Council Directive 96/48/EC on the interoperability of the trans-European high-speed rail system and Directive 2001/16/EC of the European Parliament and of the Council on the interoperability of the trans-European conventional rail system
  2. 2.0 2.1 2.2 2.3 Lua error in package.lua at line 80: module 'strict' not found.|
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. SBB, Walter von Andrian: ETCS L1 LS und Geschwindigkeitsüberwachung bei den SBB. In: Eisenbahn-Revue International, Heft 11/2011, ISSN 1421-2811, S. 543
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. http://www.ertms.com/deployment-maps/deployment-world-map.aspx
  29. http://www.ertms.com/news/ertms-news/australia-embraces-ertms.aspx
  30. 30.0 30.1 30.2 Lua error in package.lua at line 80: module 'strict' not found.
  31. [1]
  32. The City Tunnel (Malmö) has ETCS Level 1 signals as a preparation for ETCS Level 1 installation
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. UIC ERTMS Implementation Maps
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Dziennik Baltycki, 'Pociagi Gdynia-Warszawa 160 km/h?'http://www.dziennikbaltycki.pl/artykul/724293,pociagi-gdyniawarszawa-160-kmh-rusza-ostatni-etap-modernizacji-szyciej-pojedziemy-w-2015,id,t.html
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. http://galileo.uic.asso.fr/pages/gaderos.html
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. 61.0 61.1 Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.

External links