Pending: 32013D0503

15.10.2013 EN Official Journal of the European Union L 273/38
(1) Directive 92/65/EEC lays down the animal health requirements governing trade in and imports into the Union of animals, semen, ova and embryos not subject to the animal health requirements laid down in the specific acts of the Union referred to in Annex F thereto.
(2) Varroasis in bees is listed in Annex B to Directive 92/65/EEC. It is caused by ectoparasitic mites of the genusVarroaand has been reported worldwide.
(3) Article 15 of Directive 92/65/EEC provides that, where a Member State considers that its territory or part of its territory is free from one of the diseases listed in in Annex B thereto, it is to submit to the Commission appropriate documentation, on the basis of which a Decision is to be adopted.
(4) Varroasis spreads through movement of bee brood and direct contact between infested adult bees. The latter is only possible within the bee’s fly range. Consequently, only territories where the movement of bee hives and brood can be controlled and which are geographically isolated enough to prevent the migration of bees from the outside can be recognised as disease-free. Moreover, the competent authorities must prove through extended surveillance results that the region is indeed free from varroosis and that, to maintain the status, the introduction of live bees and brood is strictly controlled.
(5) Finland has asked the Commission to recognise the Åland Islands as a part of its territory that is free from varroosis. Article 355(4) of the Treaty on the Functioning of the European Union provides that the provisions of the Treaties are to apply to the Åland Islands in accordance with the provisions set out in Protocol 2 to the Act concerning the conditions of accession of the Republic of Austria, the Republic of Finland and the Kingdom of Sweden.
(6) The Åland Islands are a group of islands situated between the Gulf of Bothnia and the Baltic Sea and they are therefore geographically sufficiently separated from potentially varroosis-infected areas.
(7) Varroosis is a notifiable disease in the Åland Islands and no capped brood and hatched, adult live honey bees can be moved from mainland Finland to the Åland Islands. Finland has for several years observed the island’s bee population. On the basis of that surveillance Finland can now confirm the absence of the disease on the Åland Islands. As a result, that part of the Finnish territory can be considered free from that disease.
(8) The additional guarantees required in trade should therefore be defined, taking into account the measures already put in place by Finland in its national legislation.
(9) To establish the preconditions for the model health certificates for intra-Union movements of live bees between territories of the Union free ofVarroa, an additional certification should be established in the health certificate set out in Part 2 of Annex E to Directive 92/65/EEC. Moreover, the local veterinary unit of the varroosis-free area or areas should be identified with a TRACES Code in accordance with Commission Decision 2009/821/EC(2).
(10) The introduction of live bees into the Union is only authorised under the conditions provided for in Commission Regulation (EU) No 206/2010(3). In addition to the requirements laid down in that Regulation, in order to protect the varroosis-free status of the territories recognised as such, it is appropriate to prohibit the introduction of consignments of queen bees and their accompanying attendants into the Union, where the declared final destination of the consignments is a varroosis-free territory.
(11) The measures provided for in this Decision are in accordance with the opinion of the Standing Committee on the Food Chain and Animal Health,
(a) varroosis is compulsorily notifiable under national law;
(b) regular surveillance is carried out to substantiate the absence of ectoparasitic mites of the genusVarroa.
(a) the commodities originate in another Member State or territory thereof recognised as free from varroasis pursuant to Article 15(2) of Directive 92/65/EEC;
(b) the consignments are accompanied by an health certificate drawn up in accordance with the health certificate set out in Part 2 of Annex E to Directive 92/65/EEC, in which the following information shall be added in Part II.2:‘commodities listed in the fifth column of the table set out in the Annex to Commission Implementing Decision 2013/503/EU coming from Member States or parts thereof recognised as free from varroosis pursuant to Article 15(2) of Directive 92/65/EEC and in which no case of varroosis has been reported during the past 30 days.’
(c) every precaution was taken to avoid contamination with varroosis of the consignments during transport.
1 2 3 4 5
ISO-Code Member State Territory recognised as free from varroasis TRACES CodeLocal Veterinary Unit Commodities the introduction of which is prohibited into the territory listed in the third column
FI Finland Åland islands FI00300 AHVENANMAAN VALTIONVIRASTO Capped brood and hatched, adult live honey bees
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Council Directive 92/65/EEC of 13 July 1992 laying down animal health requirements governing trade in and imports into the Community of animals, semen, ova and embryos not subject to animal health requirements laid down in specific Community rules referred to in Annex A (I) to Directive 90/425/EEC(1), and in particular Article 15(2) thereof,
(1) Directive 92/65/EEC lays down the animal health requirements governing trade in and imports into the Union of animals, semen, ova and embryos not subject to the animal health requirements laid down in the specific acts of the Union referred to in Annex F thereto.
(2) Varroasis in bees is listed in Annex B to Directive 92/65/EEC. It is caused by ectoparasitic mites of the genusVarroaand has been reported worldwide.
(3) Article 15 of Directive 92/65/EEC provides that, where a Member State considers that its territory or part of its territory is free from one of the diseases listed in in Annex B thereto, it is to submit to the Commission appropriate documentation, on the basis of which a Decision is to be adopted.
(4) Varroasis spreads through movement of bee brood and direct contact between infested adult bees. The latter is only possible within the bee’s fly range. Consequently, only territories where the movement of bee hives and brood can be controlled and which are geographically isolated enough to prevent the migration of bees from the outside can be recognised as disease-free. Moreover, the competent authorities must prove through extended surveillance results that the region is indeed free from varroosis and that, to maintain the status, the introduction of live bees and brood is strictly controlled.
(5) Finland has asked the Commission to recognise the Åland Islands as a part of its territory that is free from varroosis. Article 355(4) of the Treaty on the Functioning of the European Union provides that the provisions of the Treaties are to apply to the Åland Islands in accordance with the provisions set out in Protocol 2 to the Act concerning the conditions of accession of the Republic of Austria, the Republic of Finland and the Kingdom of Sweden.
(6) The Åland Islands are a group of islands situated between the Gulf of Bothnia and the Baltic Sea and they are therefore geographically sufficiently separated from potentially varroosis-infected areas.
(7) Varroosis is a notifiable disease in the Åland Islands and no capped brood and hatched, adult live honey bees can be moved from mainland Finland to the Åland Islands. Finland has for several years observed the island’s bee population. On the basis of that surveillance Finland can now confirm the absence of the disease on the Åland Islands. As a result, that part of the Finnish territory can be considered free from that disease.
(8) The additional guarantees required in trade should therefore be defined, taking into account the measures already put in place by Finland in its national legislation.
(9) To establish the preconditions for the model health certificates for intra-Union movements of live bees between territories of the Union free ofVarroa, an additional certification should be established in the health certificate set out in Part 2 of Annex E to Directive 92/65/EEC. Moreover, the local veterinary unit of the varroosis-free area or areas should be identified with a TRACES Code in accordance with Commission Decision 2009/821/EC(2).
(10) The introduction of live bees into the Union is only authorised under the conditions provided for in Commission Regulation (EU) No 206/2010(3). In addition to the requirements laid down in that Regulation, in order to protect the varroosis-free status of the territories recognised as such, it is appropriate to prohibit the introduction of consignments of queen bees and their accompanying attendants into the Union, where the declared final destination of the consignments is a varroosis-free territory.
(11) The measures provided for in this Decision are in accordance with the opinion of the Standing Committee on the Food Chain and Animal Health,
HAS ADOPTED THIS DECISION:

Article 1
The Member States or territories thereof listed in the third column of the table set out in the Annex are recognised as free from varroosis.

Article 2
1. The Member States listed in the Annex shall ensure that in the territories listed in the third column of the table set out in the Annex, the following conditions are complied with:
(a)
varroosis is compulsorily notifiable under national law;
(b)
regular surveillance is carried out to substantiate the absence of ectoparasitic mites of the genusVarroa.
2. The Member States listed in the Annex shall report the results of the surveillance referred to in paragraph 1(b) to the Commission by 31 May each year.
3. The Member States listed in the Annex shall notify, without delay, to the Commission and to the other Member States the detection of ectoparasitic mites of the genusVarroain the territories listed in the third column of the table set out in the Annex.

Article 3
1. The introduction of consignments of the commodities listed in the fifth column of the table set out in the Annex into the territories listed in the third column of that table shall be prohibited.
2. By way of derogation from paragraph 1, the introduction of the commodities listed in the fifth column of the table in the Annex into the territories listed in the third column of that table shall be authorised where the following conditions are complied with:
(a)
the commodities originate in another Member State or territory thereof recognised as free from varroasis pursuant to Article 15(2) of Directive 92/65/EEC;
(b)
the consignments are accompanied by an health certificate drawn up in accordance with the health certificate set out in Part 2 of Annex E to Directive 92/65/EEC, in which the following information shall be added in Part II.2:
‘commodities listed in the fifth column of the table set out in the Annex to Commission Implementing Decision 2013/503/EU coming from Member States or parts thereof recognised as free from varroosis pursuant to Article 15(2) of Directive 92/65/EEC and in which no case of varroosis has been reported during the past 30 days.’
(c)
every precaution was taken to avoid contamination with varroosis of the consignments during transport.

Article 4
1. Member States shall not authorise the introduction of consignments of bees referred to in Article 7(3)(a) of Regulation (EC) No 206/2010 into the Union, where their final destination, as indicated in box references I.9, I.10 or I.12 of the health certificate accompanying the consignments, is a territory listed in the third column of the table set out in the Annex.
2. By way of derogation from paragraph 1 and subject to the health requirements for imports laid down in Regulation (EU) No 206/2010, Member States may authorise the introduction into the Union of the consignments referred to in paragraph 1, provided that their final destination is changed to a territory not listed in the third column of the table set out in the Annex.

Article 5
This Decision is addressed to the Member States.

THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Council Directive 92/65/EEC of 13 July 1992 laying down animal health requirements governing trade in and imports into the Community of animals, semen, ova and embryos not subject to animal health requirements laid down in specific Community rules referred to in Annex A (I) to Directive 90/425/EEC(1), and in particular Article 15(2) thereof,
(1) Directive 92/65/EEC lays down the animal health requirements governing trade in and imports into the Union of animals, semen, ova and embryos not subject to the animal health requirements laid down in the specific acts of the Union referred to in Annex F thereto.
(2) Varroasis in bees is listed in Annex B to Directive 92/65/EEC. It is caused by ectoparasitic mites of the genusVarroaand has been reported worldwide.
(3) Article 15 of Directive 92/65/EEC provides that, where a Member State considers that its territory or part of its territory is free from one of the diseases listed in in Annex B thereto, it is to submit to the Commission appropriate documentation, on the basis of which a Decision is to be adopted.
(4) Varroasis spreads through movement of bee brood and direct contact between infested adult bees. The latter is only possible within the bee’s fly range. Consequently, only territories where the movement of bee hives and brood can be controlled and which are geographically isolated enough to prevent the migration of bees from the outside can be recognised as disease-free. Moreover, the competent authorities must prove through extended surveillance results that the region is indeed free from varroosis and that, to maintain the status, the introduction of live bees and brood is strictly controlled.
(5) Finland has asked the Commission to recognise the Åland Islands as a part of its territory that is free from varroosis. Article 355(4) of the Treaty on the Functioning of the European Union provides that the provisions of the Treaties are to apply to the Åland Islands in accordance with the provisions set out in Protocol 2 to the Act concerning the conditions of accession of the Republic of Austria, the Republic of Finland and the Kingdom of Sweden.
(6) The Åland Islands are a group of islands situated between the Gulf of Bothnia and the Baltic Sea and they are therefore geographically sufficiently separated from potentially varroosis-infected areas.
(7) Varroosis is a notifiable disease in the Åland Islands and no capped brood and hatched, adult live honey bees can be moved from mainland Finland to the Åland Islands. Finland has for several years observed the island’s bee population. On the basis of that surveillance Finland can now confirm the absence of the disease on the Åland Islands. As a result, that part of the Finnish territory can be considered free from that disease.
(8) The additional guarantees required in trade should therefore be defined, taking into account the measures already put in place by Finland in its national legislation.
(9) To establish the preconditions for the model health certificates for intra-Union movements of live bees between territories of the Union free ofVarroa, an additional certification should be established in the health certificate set out in Part 2 of Annex E to Directive 92/65/EEC. Moreover, the local veterinary unit of the varroosis-free area or areas should be identified with a TRACES Code in accordance with Commission Decision 2009/821/EC(2).
(10) The introduction of live bees into the Union is only authorised under the conditions provided for in Commission Regulation (EU) No 206/2010(3). In addition to the requirements laid down in that Regulation, in order to protect the varroosis-free status of the territories recognised as such, it is appropriate to prohibit the introduction of consignments of queen bees and their accompanying attendants into the Union, where the declared final destination of the consignments is a varroosis-free territory.
(11) The measures provided for in this Decision are in accordance with the opinion of the Standing Committee on the Food Chain and Animal Health,
HAS ADOPTED THIS DECISION:
The Member States or territories thereof listed in the third column of the table set out in the Annex are recognised as free from varroosis.
1. The Member States listed in the Annex shall ensure that in the territories listed in the third column of the table set out in the Annex, the following conditions are complied with:
(a)
varroosis is compulsorily notifiable under national law;
(b)
regular surveillance is carried out to substantiate the absence of ectoparasitic mites of the genusVarroa.
2. The Member States listed in the Annex shall report the results of the surveillance referred to in paragraph 1(b) to the Commission by 31 May each year.
3. The Member States listed in the Annex shall notify, without delay, to the Commission and to the other Member States the detection of ectoparasitic mites of the genusVarroain the territories listed in the third column of the table set out in the Annex.
1. The introduction of consignments of the commodities listed in the fifth column of the table set out in the Annex into the territories listed in the third column of that table shall be prohibited.
2. By way of derogation from paragraph 1, the introduction of the commodities listed in the fifth column of the table in the Annex into the territories listed in the third column of that table shall be authorised where the following conditions are complied with:
(a)
the commodities originate in another Member State or territory thereof recognised as free from varroasis pursuant to Article 15(2) of Directive 92/65/EEC;
(b)
the consignments are accompanied by an health certificate drawn up in accordance with the health certificate set out in Part 2 of Annex E to Directive 92/65/EEC, in which the following information shall be added in Part II.2:
‘commodities listed in the fifth column of the table set out in the Annex to Commission Implementing Decision 2013/503/EU coming from Member States or parts thereof recognised as free from varroosis pursuant to Article 15(2) of Directive 92/65/EEC and in which no case of varroosis has been reported during the past 30 days.’
(c)
every precaution was taken to avoid contamination with varroosis of the consignments during transport.
1. Member States shall not authorise the introduction of consignments of bees referred to in Article 7(3)(a) of Regulation (EC) No 206/2010 into the Union, where their final destination, as indicated in box references I.9, I.10 or I.12 of the health certificate accompanying the consignments, is a territory listed in the third column of the table set out in the Annex.
2. By way of derogation from paragraph 1 and subject to the health requirements for imports laid down in Regulation (EU) No 206/2010, Member States may authorise the introduction into the Union of the consignments referred to in paragraph 1, provided that their final destination is changed to a territory not listed in the third column of the table set out in the Annex.
This Decision is addressed to the Member States.
ANNEX
Member States or territories thereof which are recognised as free from varroosis

1 | 2 | 3 | 4 | 5
ISO-Code | Member State | Territory recognised as free from varroasis | TRACES CodeLocal Veterinary Unit | Commodities the introduction of which is prohibited into the territory listed in the third column
FI | Finland | Åland islands | FI00300 AHVENANMAAN VALTIONVIRASTO | Capped brood and hatched, adult live honey bees

Pending: 32013D0034

18.1.2013 EN Official Journal of the European Union L 14/19
(1) On 23 July 2012, the Council recognised that the dramatic changes in Mali required a review of the actions the Union should undertake in order to support the restoration of democratic government and the rule of law throughout the territory of Mali. It requested the High Representative of the Union for Foreign Affairs and Security Policy (HR) and the Commission to make concrete proposals for Union action in a number of areas to respond to the changing situation.
(2) By letter dated 18 September 2012, the President of the Republic of Mali requested Union support with a view to restoring the Malian territorial integrity.
(3) In its Resolution 2071 (2012) on the situation in Mali, adopted on 12 October 2012, the United Nations Security Council, while expressing its grave concern about the consequences of instability in the north of Mali on the region and beyond, and stressing the need to respond swiftly in order to preserve stability across the Sahel region, invited international partners, including the Union, to provide assistance, expertise, training and capacity-building support to the Malian army and security forces.
(4) In its conclusions of 15 October 2012, the Council requested that work on planning a possible Common Security and Defence Policy (CSDP) military mission be pursued and extended as a matter of urgency, in particular by developing a crisis management concept relating to the reorganisation and training of the Malian defence forces, taking account of the conditions necessary for the success of any such mission, which include the full support of the Malian authorities and the definition of an exit strategy.
(5) In its conclusions of 19 November 2012, the Council welcomed the presentation of the Crisis Management Concept by the HR and called on the relevant groups to examine it as a matter of urgency so that it could be approved by the Council in December 2012.
(6) On 10 December 2012, the Council approved a Crisis Management Concept on a possible military CSDP training mission in Mali. The Council emphasised that a mission in Mali would be an essential element in the Union’s comprehensive approach as elaborated in the Strategy for Security and Development in the Sahel.
(7) By letter dated 24 December 2012, the President of the Republic of Mali addressed an invitation letter to the HR welcoming the deployment of an EU military training mission in Mali.
(8) The Political and Security Committee (PSC) should exercise, under the responsibility of the Council and of the HR, political control over the Union military mission, provide it with strategic direction and take the relevant decisions in accordance with the third paragraph of Article 38 of the Treaty on European Union (TEU).
(9) It is necessary to negotiate and conclude international agreements relating to the status of EU units and personnel and to the participation of third States in Union missions.
(10) The operational expenditure arising from this Decision, which has military or defence implications, should be borne by the Member States pursuant to Article 41(2) TEU and in accordance with Council Decision 2011/871/CFSP of 19 December 2011 establishing a mechanism to administer the financing of the common costs of European Union operations having military or defence implications (Athena)(1).
(11) In accordance with Article 5 of the Protocol on the position of Denmark annexed to the TEU and to the Treaty on the Functioning of the European Union (TFEU), Denmark does not participate in the elaboration and implementation of decisions and actions of the Union which have defence implications. Denmark does not participate in the implementation of this Decision and therefore does not participate in the financing of this mission,
(a) training support for the benefit of the MAF;
(b) training and advice on command and control, logistical chain and human resources, as well as training on International Humanitarian Law, protection of civilians and human rights.
(a) up to the level provided in the applicable security of information agreements concluded between the Union and the third State concerned; or
(b) up to the ‘CONFIDENTIEL UE/EU CONFIDENTIAL’ level in other cases.
THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union, and in particular Articles 42(4) and 43(2) thereof,
Having regard to the proposal from the High Representative of the Union for Foreign Affairs and Security Policy,
(1) On 23 July 2012, the Council recognised that the dramatic changes in Mali required a review of the actions the Union should undertake in order to support the restoration of democratic government and the rule of law throughout the territory of Mali. It requested the High Representative of the Union for Foreign Affairs and Security Policy (HR) and the Commission to make concrete proposals for Union action in a number of areas to respond to the changing situation.
(2) By letter dated 18 September 2012, the President of the Republic of Mali requested Union support with a view to restoring the Malian territorial integrity.
(3) In its Resolution 2071 (2012) on the situation in Mali, adopted on 12 October 2012, the United Nations Security Council, while expressing its grave concern about the consequences of instability in the north of Mali on the region and beyond, and stressing the need to respond swiftly in order to preserve stability across the Sahel region, invited international partners, including the Union, to provide assistance, expertise, training and capacity-building support to the Malian army and security forces.
(4) In its conclusions of 15 October 2012, the Council requested that work on planning a possible Common Security and Defence Policy (CSDP) military mission be pursued and extended as a matter of urgency, in particular by developing a crisis management concept relating to the reorganisation and training of the Malian defence forces, taking account of the conditions necessary for the success of any such mission, which include the full support of the Malian authorities and the definition of an exit strategy.
(5) In its conclusions of 19 November 2012, the Council welcomed the presentation of the Crisis Management Concept by the HR and called on the relevant groups to examine it as a matter of urgency so that it could be approved by the Council in December 2012.
(6) On 10 December 2012, the Council approved a Crisis Management Concept on a possible military CSDP training mission in Mali. The Council emphasised that a mission in Mali would be an essential element in the Union’s comprehensive approach as elaborated in the Strategy for Security and Development in the Sahel.
(7) By letter dated 24 December 2012, the President of the Republic of Mali addressed an invitation letter to the HR welcoming the deployment of an EU military training mission in Mali.
(8) The Political and Security Committee (PSC) should exercise, under the responsibility of the Council and of the HR, political control over the Union military mission, provide it with strategic direction and take the relevant decisions in accordance with the third paragraph of Article 38 of the Treaty on European Union (TEU).
(9) It is necessary to negotiate and conclude international agreements relating to the status of EU units and personnel and to the participation of third States in Union missions.
(10) The operational expenditure arising from this Decision, which has military or defence implications, should be borne by the Member States pursuant to Article 41(2) TEU and in accordance with Council Decision 2011/871/CFSP of 19 December 2011 establishing a mechanism to administer the financing of the common costs of European Union operations having military or defence implications (Athena)(1).
(11) In accordance with Article 5 of the Protocol on the position of Denmark annexed to the TEU and to the Treaty on the Functioning of the European Union (TFEU), Denmark does not participate in the elaboration and implementation of decisions and actions of the Union which have defence implications. Denmark does not participate in the implementation of this Decision and therefore does not participate in the financing of this mission,
HAS ADOPTED THIS DECISION:

Mission
Article 1
1. The Union shall conduct a military training mission (EUTM Mali), to provide, in the South of Mali, military and training advice to the Malian Armed Forces (MAF) operating under the control of legitimate civilian authorities, in order to contribute to the restoration of their military capacity with a view to enabling them to conduct military operations aiming at restoring Malian territorial integrity and reducing the threat posed by terrorist groups. EUTM Mali shall not be involved in combat operations.
2. The objective of EUTM Mali shall be to respond to the operational needs of the MAF through the provision of:
(a)
training support for the benefit of the MAF;
(b)
training and advice on command and control, logistical chain and human resources, as well as training on International Humanitarian Law, protection of civilians and human rights.
3. EUTM Mali shall aim at strengthening conditions for proper political control by legitimate civilian authorities of the MAF.
4. The activities of EUTM Mali shall be conducted in close coordination with other actors involved in the support to the MAF, in particular the United Nations (UN) and the Economic Community of West African States (ECOWAS).

Appointment of the EU Mission Commander
Article 2
1. Brigadier General François LECOINTRE is hereby appointed EU Mission Commander.
2. The EU Mission Commander shall exercise the functions of EU Operation Commander and EU Force Commander.

Designation of the Mission Headquarters
Article 3
1. The Mission Headquarters of EUTM Mali shall be located in Mali. It shall perform the functions of both Operational Headquarters and Force Headquarters.
2. The Mission Headquarters shall include a support cell in Brussels.

Planning and launch of EUTM Mali
Article 4
The Decision to launch EUTM Mali shall be adopted by the Council following approval of the Mission Plan and of the Rules of Engagement.

Political control and strategic direction
Article 5
1. Under the responsibility of the Council and of the HR, the PSC shall exercise the political control and strategic direction of EUTM Mali. The Council hereby authorises the PSC to take the relevant decisions in accordance with Article 38 TEU. This authorisation shall include the powers to amend the planning documents, including the Mission Plan, and the Chain of Command. It shall also include the powers to take decisions on the appointment of the subsequent EU Mission Commanders. The powers of decision with respect to the objectives and termination of EUTM Mali shall remain vested in the Council.
2. The PSC shall report to the Council at regular intervals.
3. The PSC shall, at regular intervals, receive reports from the chairman of the EU Military Committee (EUMC) regarding the conduct of EUTM Mali. The PSC may invite the EU Mission Commander to its meetings, as appropriate.

Military direction
Article 6
1. The EUMC shall monitor the proper execution of EUTM Mali conducted under the responsibility of the EU Mission Commander.
2. The EUMC shall, at regular intervals, receive reports from the EU Mission Commander. It may invite the EU Mission Commander to its meetings, as appropriate.
3. The chairman of the EUMC shall act as the primary point of contact with the EU Mission Commander.

Consistency of the Union’s response and coordination
Article 7
1. The HR shall ensure the implementation of this Decision and its consistency with the Union’s external action as a whole, including the Union’s development programmes.
2. Without prejudice to the chain of command, the EU Mission Commander shall receive local political guidance from the Head of the Union Delegation in Bamako in close coordination with the EU coordinator for Sahel.
3. EUTM Mali shall coordinate with Union CSDP mission in Niger (EUCAP SAHEL Niger) with a view to exploring possible synergies.
4. EUTM Mali shall coordinate its activities with Member States’ bilateral activities in Mali, as well as with other international actors in the region, in particular the UN, the African Union (AU), ECOWAS and bilateral actors including the United States and Canada, and with key regional actors.

Participation of third States
Article 8
1. Without prejudice to the decision-making autonomy of the Union and its single institutional framework, and in accordance with the relevant guidelines of the European Council, third States may be invited to participate in EUTM Mali.
2. The Council hereby authorises the PSC to invite third States to offer contributions and to take the relevant decisions on acceptance of the proposed contributions, upon the recommendation of the EU Mission Commander and the EUMC.
3. Detailed arrangements regarding the participation of third States shall be covered by agreements concluded pursuant to Article 37 TEU and in accordance with the procedure laid down in Article 218 TFEU. Where the Union and a third State have concluded an agreement establishing a framework for the latter’s participation in crisis management missions of the Union, the provisions of such an agreement shall apply in the context of EUTM Mali.
4. Third States making significant military contributions to EUTM Mali shall have the same rights and obligations in terms of the day-to-day management of EUTM Mali as Member States taking part in EUTM Mali.
5. The Council hereby authorises the PSC to take relevant decisions on the setting-up of a Committee of Contributors, should third States make significant military contributions.

Status of EU-led personnel
Article 9
The status of EU-led units and personnel, including the privileges, immunities and further guarantees necessary for the fulfilment and smooth functioning of their mission, shall be the subject of an agreement concluded pursuant to Article 37 TEU and in accordance with the procedure laid down in Article 218 TFEU.

Financial arrangements
Article 10
1. The common costs of EUTM Mali shall be administered in accordance with Decision 2011/871/CFSP.
2. The financial reference amount for the common costs of EUTM Mali shall be EUR 12,3 million. The percentage of the reference amount referred to in Article 25(1) of Decision 2011/871/CFSP shall be 50 %, and the percentage for commitment referred to in Article 32(3) of Decision 2011/871/CFSP shall be 70 %.

Release of information
Article 11
1. The HR shall be authorised to release to the third States associated with this Decision, as appropriate and in accordance with the needs of EUTM Mali, EU classified information generated for the purposes of EUTM Mali, in accordance with Council Decision 2011/292/EU of 31 March 2011 on the security rules for protecting EU classified information(2):
(a)
up to the level provided in the applicable security of information agreements concluded between the Union and the third State concerned; or
(b)
up to the ‘CONFIDENTIEL UE/EU CONFIDENTIAL’ level in other cases.
2. The HR shall also be authorised to release to the UN and ECOWAS in accordance with the operational needs of EUTM Mali, EU classified information up to ‘RESTREINT UE/EU RESTRICTED’ level which are generated for the purposes of EUTM Mali, in accordance with Decision 2011/292/EU. Arrangements between the HR and the competent authorities of the UN and ECOWAS shall be drawn up for this purpose.
3. In the event of a specific and immediate operational need, the HR shall also be authorised to release to the host State any EU classified information up to ‘RESTREINT UE/EU RESTRICTED’ level which are generated for the purposes of EUTM Mali, in accordance with Decision 2011/292/EU. Arrangements between the HR and the competent authorities of the host State shall be drawn up for this purpose.
4. The HR shall be authorised to release to the third States associated with this Decision any EU non-classified documents connected with the deliberations of the Council relating to EUTM Mali and covered by the obligation of professional secrecy pursuant to Article 6(1) of the Council’s Rules of Procedure(3).
5. The HR may delegate the powers referred to in paragraphs 1 to 4, as well as the ability to conclude the arrangements referred to in paragraphs 2 and 3 to staff of the European External Action Service and/or to the EU Mission Commander.

Entry into force and termination
Article 12
1. This Decision shall enter into force on the date of its adoption.
2. The mandate of EUTM Mali shall end 15 months after the adoption of the Council Decision to launch EUTM Mali.
3. This Decision shall be repealed as from the date of closure of the Mission Headquarters in accordance with the plans approved for the termination of EUTM Mali, and without prejudice to the procedures regarding the audit and presentation of the accounts of EUTM Mali, laid down in Decision 2011/871/CFSP.

THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union, and in particular Articles 42(4) and 43(2) thereof,
Having regard to the proposal from the High Representative of the Union for Foreign Affairs and Security Policy,
(1) On 23 July 2012, the Council recognised that the dramatic changes in Mali required a review of the actions the Union should undertake in order to support the restoration of democratic government and the rule of law throughout the territory of Mali. It requested the High Representative of the Union for Foreign Affairs and Security Policy (HR) and the Commission to make concrete proposals for Union action in a number of areas to respond to the changing situation.
(2) By letter dated 18 September 2012, the President of the Republic of Mali requested Union support with a view to restoring the Malian territorial integrity.
(3) In its Resolution 2071 (2012) on the situation in Mali, adopted on 12 October 2012, the United Nations Security Council, while expressing its grave concern about the consequences of instability in the north of Mali on the region and beyond, and stressing the need to respond swiftly in order to preserve stability across the Sahel region, invited international partners, including the Union, to provide assistance, expertise, training and capacity-building support to the Malian army and security forces.
(4) In its conclusions of 15 October 2012, the Council requested that work on planning a possible Common Security and Defence Policy (CSDP) military mission be pursued and extended as a matter of urgency, in particular by developing a crisis management concept relating to the reorganisation and training of the Malian defence forces, taking account of the conditions necessary for the success of any such mission, which include the full support of the Malian authorities and the definition of an exit strategy.
(5) In its conclusions of 19 November 2012, the Council welcomed the presentation of the Crisis Management Concept by the HR and called on the relevant groups to examine it as a matter of urgency so that it could be approved by the Council in December 2012.
(6) On 10 December 2012, the Council approved a Crisis Management Concept on a possible military CSDP training mission in Mali. The Council emphasised that a mission in Mali would be an essential element in the Union’s comprehensive approach as elaborated in the Strategy for Security and Development in the Sahel.
(7) By letter dated 24 December 2012, the President of the Republic of Mali addressed an invitation letter to the HR welcoming the deployment of an EU military training mission in Mali.
(8) The Political and Security Committee (PSC) should exercise, under the responsibility of the Council and of the HR, political control over the Union military mission, provide it with strategic direction and take the relevant decisions in accordance with the third paragraph of Article 38 of the Treaty on European Union (TEU).
(9) It is necessary to negotiate and conclude international agreements relating to the status of EU units and personnel and to the participation of third States in Union missions.
(10) The operational expenditure arising from this Decision, which has military or defence implications, should be borne by the Member States pursuant to Article 41(2) TEU and in accordance with Council Decision 2011/871/CFSP of 19 December 2011 establishing a mechanism to administer the financing of the common costs of European Union operations having military or defence implications (Athena)(1).
(11) In accordance with Article 5 of the Protocol on the position of Denmark annexed to the TEU and to the Treaty on the Functioning of the European Union (TFEU), Denmark does not participate in the elaboration and implementation of decisions and actions of the Union which have defence implications. Denmark does not participate in the implementation of this Decision and therefore does not participate in the financing of this mission,
HAS ADOPTED THIS DECISION:

Mission

1. The Union shall conduct a military training mission (EUTM Mali), to provide, in the South of Mali, military and training advice to the Malian Armed Forces (MAF) operating under the control of legitimate civilian authorities, in order to contribute to the restoration of their military capacity with a view to enabling them to conduct military operations aiming at restoring Malian territorial integrity and reducing the threat posed by terrorist groups. EUTM Mali shall not be involved in combat operations.
2. The objective of EUTM Mali shall be to respond to the operational needs of the MAF through the provision of:
(a)
training support for the benefit of the MAF;
(b)
training and advice on command and control, logistical chain and human resources, as well as training on International Humanitarian Law, protection of civilians and human rights.
3. EUTM Mali shall aim at strengthening conditions for proper political control by legitimate civilian authorities of the MAF.
4. The activities of EUTM Mali shall be conducted in close coordination with other actors involved in the support to the MAF, in particular the United Nations (UN) and the Economic Community of West African States (ECOWAS).

Appointment of the EU Mission Commander

1. Brigadier General François LECOINTRE is hereby appointed EU Mission Commander.
2. The EU Mission Commander shall exercise the functions of EU Operation Commander and EU Force Commander.

Designation of the Mission Headquarters

1. The Mission Headquarters of EUTM Mali shall be located in Mali. It shall perform the functions of both Operational Headquarters and Force Headquarters.
2. The Mission Headquarters shall include a support cell in Brussels.

Planning and launch of EUTM Mali

The Decision to launch EUTM Mali shall be adopted by the Council following approval of the Mission Plan and of the Rules of Engagement.

Political control and strategic direction

1. Under the responsibility of the Council and of the HR, the PSC shall exercise the political control and strategic direction of EUTM Mali. The Council hereby authorises the PSC to take the relevant decisions in accordance with Article 38 TEU. This authorisation shall include the powers to amend the planning documents, including the Mission Plan, and the Chain of Command. It shall also include the powers to take decisions on the appointment of the subsequent EU Mission Commanders. The powers of decision with respect to the objectives and termination of EUTM Mali shall remain vested in the Council.
2. The PSC shall report to the Council at regular intervals.
3. The PSC shall, at regular intervals, receive reports from the chairman of the EU Military Committee (EUMC) regarding the conduct of EUTM Mali. The PSC may invite the EU Mission Commander to its meetings, as appropriate.

Military direction

1. The EUMC shall monitor the proper execution of EUTM Mali conducted under the responsibility of the EU Mission Commander.
2. The EUMC shall, at regular intervals, receive reports from the EU Mission Commander. It may invite the EU Mission Commander to its meetings, as appropriate.
3. The chairman of the EUMC shall act as the primary point of contact with the EU Mission Commander.

Consistency of the Union’s response and coordination

1. The HR shall ensure the implementation of this Decision and its consistency with the Union’s external action as a whole, including the Union’s development programmes.
2. Without prejudice to the chain of command, the EU Mission Commander shall receive local political guidance from the Head of the Union Delegation in Bamako in close coordination with the EU coordinator for Sahel.
3. EUTM Mali shall coordinate with Union CSDP mission in Niger (EUCAP SAHEL Niger) with a view to exploring possible synergies.
4. EUTM Mali shall coordinate its activities with Member States’ bilateral activities in Mali, as well as with other international actors in the region, in particular the UN, the African Union (AU), ECOWAS and bilateral actors including the United States and Canada, and with key regional actors.

Participation of third States

1. Without prejudice to the decision-making autonomy of the Union and its single institutional framework, and in accordance with the relevant guidelines of the European Council, third States may be invited to participate in EUTM Mali.
2. The Council hereby authorises the PSC to invite third States to offer contributions and to take the relevant decisions on acceptance of the proposed contributions, upon the recommendation of the EU Mission Commander and the EUMC.
3. Detailed arrangements regarding the participation of third States shall be covered by agreements concluded pursuant to Article 37 TEU and in accordance with the procedure laid down in Article 218 TFEU. Where the Union and a third State have concluded an agreement establishing a framework for the latter’s participation in crisis management missions of the Union, the provisions of such an agreement shall apply in the context of EUTM Mali.
4. Third States making significant military contributions to EUTM Mali shall have the same rights and obligations in terms of the day-to-day management of EUTM Mali as Member States taking part in EUTM Mali.
5. The Council hereby authorises the PSC to take relevant decisions on the setting-up of a Committee of Contributors, should third States make significant military contributions.

Status of EU-led personnel

The status of EU-led units and personnel, including the privileges, immunities and further guarantees necessary for the fulfilment and smooth functioning of their mission, shall be the subject of an agreement concluded pursuant to Article 37 TEU and in accordance with the procedure laid down in Article 218 TFEU.

Financial arrangements

1. The common costs of EUTM Mali shall be administered in accordance with Decision 2011/871/CFSP.
2. The financial reference amount for the common costs of EUTM Mali shall be EUR 12,3 million. The percentage of the reference amount referred to in Article 25(1) of Decision 2011/871/CFSP shall be 50 %, and the percentage for commitment referred to in Article 32(3) of Decision 2011/871/CFSP shall be 70 %.

Release of information

1. The HR shall be authorised to release to the third States associated with this Decision, as appropriate and in accordance with the needs of EUTM Mali, EU classified information generated for the purposes of EUTM Mali, in accordance with Council Decision 2011/292/EU of 31 March 2011 on the security rules for protecting EU classified information(2):
(a)
up to the level provided in the applicable security of information agreements concluded between the Union and the third State concerned; or
(b)
up to the ‘CONFIDENTIEL UE/EU CONFIDENTIAL’ level in other cases.
2. The HR shall also be authorised to release to the UN and ECOWAS in accordance with the operational needs of EUTM Mali, EU classified information up to ‘RESTREINT UE/EU RESTRICTED’ level which are generated for the purposes of EUTM Mali, in accordance with Decision 2011/292/EU. Arrangements between the HR and the competent authorities of the UN and ECOWAS shall be drawn up for this purpose.
3. In the event of a specific and immediate operational need, the HR shall also be authorised to release to the host State any EU classified information up to ‘RESTREINT UE/EU RESTRICTED’ level which are generated for the purposes of EUTM Mali, in accordance with Decision 2011/292/EU. Arrangements between the HR and the competent authorities of the host State shall be drawn up for this purpose.
4. The HR shall be authorised to release to the third States associated with this Decision any EU non-classified documents connected with the deliberations of the Council relating to EUTM Mali and covered by the obligation of professional secrecy pursuant to Article 6(1) of the Council’s Rules of Procedure(3).
5. The HR may delegate the powers referred to in paragraphs 1 to 4, as well as the ability to conclude the arrangements referred to in paragraphs 2 and 3 to staff of the European External Action Service and/or to the EU Mission Commander.

Entry into force and termination

1. This Decision shall enter into force on the date of its adoption.
2. The mandate of EUTM Mali shall end 15 months after the adoption of the Council Decision to launch EUTM Mali.
3. This Decision shall be repealed as from the date of closure of the Mission Headquarters in accordance with the plans approved for the termination of EUTM Mali, and without prejudice to the procedures regarding the audit and presentation of the accounts of EUTM Mali, laid down in Decision 2011/871/CFSP.

Pending: 32012D0757

15.12.2012 EN Official Journal of the European Union L 345/1
(1) Article 12 of Regulation (EC) No 881/2004 of the European Parliament and of the Council of 29 April 2004 establishing a European Railway Agency (Agency Regulation)(2)requires the European Railway Agency (the Agency) to ensure that the technical specifications for interoperability (TSIs) are adapted to technical progress, market trends and social requirements and to propose to the Commission the amendments to the TSIs which it considers necessary.
(2) By Decision C(2010) 2576 of 29 April 2010, the Commission gave the Agency a mandate to develop and review the technical specifications for interoperability with a view to extending their scope to the whole rail system in the Union. Under the terms of that mandate, the Agency was asked to merge and extend the scope of the high-speed TSI and the conventional rail TSI relating to the ‘Traffic Operation and Management’ subsystem. These TSIs were adopted respectively by Commission Decision 2008/231/EC(3), and Commission Decision 2011/314/EU(4).
(3) On 5 September 2011, the Agency issued a recommendation on the merging of the TSI on operation and traffic management for conventional rail and the TSI on operation and traffic management for high-speed rail, the extension of the geographical scope of these TSIs and the transfer of details of the European vehicle number (EVN) to Commission Decision 2007/756/EC(5).
(4) Implementation of the TSI set out in Annex I, and conformity with the relevant points of that TSI, should be determined in accordance with an implementation plan that each Member State is required to update for the lines for which it is responsible.
(5) Rail traffic currently operates under existing national, bilateral, multinational or international agreements. It is important that those agreements do not hinder current and future progress towards interoperability. Therefore a procedure of notification of these agreements by Member States should set up.
(6) Railway vehicles are registered by the bodies that keep the national vehicle registers pursuant to Decision 2007/756/EC, based on Article 33 of Directive 2008/57/EC.
(7) The format of the European vehicle number and the requirement to have it painted on the vehicle are both necessary for identifying the vehicle and should therefore remain in the TSI on operation and traffic management.
(8) To make it easier to understand the national vehicle register and the vehicle registration processes, it is appropriate to transfer the details of the technical codes that are part of the European vehicle number to Decision 2007/756/EC. Decision 2007/756/EC should therefore be amended accordingly.
(9) Via the Committee established in accordance with Article 29 of Directive 2008/57/EC, the Commission must inform the Member States of changes in the lists of codes published by the Agency.
(10) Directive 2008/57/EC defines the ‘operation and traffic management’ subsystem as functional. Consequently, the TSI on operation and traffic management is not assessed when authorising a vehicle to be brought into service but when assessing the safety management systems of railway undertakings and infrastructure managers.
(11) For the sake of clarity and simplicity, it is appropriate not to amend the transitional provisions set out in Articles 3, 5 and 7 of Decision 2011/314/EU.
(12) Decisions 2008/231/EC and 2011/314/EU should be repealed.
(13) The measures provided for in this Decision are in conformity with the opinion of the Committee established in accordance with Article 29(1) of Directive 2008/57/EC,
(a) national agreements between the Member States and railway undertakings or infrastructure managers, agreed on either a permanent or a temporary basis and required by the very specific or local nature of the intended transport service;
(b) bilateral or multilateral agreements between railway undertakings, infrastructure managers or safety authorities which deliver significant levels of local or regional interoperability;
(c) international agreements between one or more Member States and at least one third country, or between railway undertakings or infrastructure managers of Member States and at least one railway undertaking or infrastructure manager of a third country, which deliver significant levels of local or regional interoperability.
(a) The following Article is inserted after Article 1:‘Article 1aAppendix 6 of the Annex of this Decision shall apply from 1 January 2014.’
(b) The Annex is amended in accordance with Annex II to this Decision.
1. INTRODUCTION 9
1.1. Technical scope 9
1.2. Geographical scope 9
1.3. Content of this TSI 9
2. DESCRIPTION OF SUBSYSTEM/SCOPE 9
2.1. Subsystem 9
2.2. Scope 9
2.2.1. Staff and trains 10
2.2.2. Principles 10
2.2.3. Applicability to existing vehicles and infrastructure 11
3. ESSENTIAL REQUIREMENTS 11
3.1. Compliance with the essential requirements 11
3.2. Essential requirements — overview 11
4. CHARACTERISTICS OF THE SUBSYSTEM 15
4.1. Introduction 15
4.2. Functional and technical specifications of the subsystem 15
4.2.1. Specifications relating to staff 15
4.2.1.1. General requirements 15
4.2.1.2. Documentation for drivers 15
4.2.1.2.1 Driver’s Rule Book 15
4.2.1.2.2 Description of the line and the relevant line-side equipment associated with the lines worked over 16
4.2.1.2.2.1 Preparation of the Route Book 16
4.2.1.2.2.2 Modifications to information contained within the Route Book 17
4.2.1.2.2.3 Informing the driver in real time 17
4.2.1.2.3 Timetables 17
4.2.1.2.4 Rolling stock 18
4.2.1.3. Documentation for railway undertaking staff other than drivers 18
4.2.1.4. Documentation for infrastructure manager’s staff authorising train movements 18
4.2.1.5. Safety-related communications between train crew, other railway undertaking staff and staff authorising train movements 18
4.2.2. Specifications relating to trains 18
4.2.2.1. Train visibility 18
4.2.2.1.1. General requirement 18
4.2.2.1.2. Front end 19
4.2.2.1.3. Rear end 19
4.2.2.1.3.1 Passenger trains 20
4.2.2.1.3.2 Freight trains in international traffic 20
4.2.2.1.3.3 Freight trains not crossing a border between Member States 20
4.2.2.2. Train audibility 20
4.2.2.2.1. General requirement 20
4.2.2.2.2. Control 20
4.2.2.3. Vehicle identification 20
4.2.2.4. Safety of passengers and load 20
4.2.2.4.1 Safety of load 20
4.2.2.4.2 Safety of passengers 21
4.2.2.5. Train composition 21
4.2.2.6. Train braking 21
4.2.2.6.1 Minimum requirements of the braking system 21
4.2.2.6.2 Braking performance 21
4.2.2.7. Ensuring that the train is in running order 22
4.2.2.7.1 General requirement 22
4.2.2.7.2 Data required 22
4.2.2.8. Requirements for lineside signal and marker sighting 22
4.2.2.9. Driver vigilance 22
4.2.3. Specifications relating to train operations 22
4.2.3.1. Train planning 22
4.2.3.2. Identification of trains 22
4.2.3.2.1 Format of train running number 23
4.2.3.3. Train departure 23
4.2.3.3.1 Checks and tests before departure 23
4.2.3.3.2 Informing the infrastructure manager of the train’s operational status 23
4.2.3.4. Traffic management 23
4.2.3.4.1 General requirements 23
4.2.3.4.2 Train reporting 23
4.2.3.4.2.1 Data required for train position reporting 23
4.2.3.4.2.2 Predicted hand over time 24
4.2.3.4.3 Dangerous goods 24
4.2.3.4.4 Operational quality 24
4.2.3.5. Data recording 24
4.2.3.5.1 Recording of supervision data outside the train 25
4.2.3.5.2 Recording of supervision data on-board the train 25
4.2.3.6. Degraded operation 25
4.2.3.6.1 Advice to other users 25
4.2.3.6.2 Advice to train drivers 25
4.2.3.6.3 Contingency arrangements 25
4.2.3.7. Managing an emergency situation 26
4.2.3.8. Aid to train crew in the event of an incident or of a major rolling stock malfunction 26
4.3. Functional and technical specifications of the interfaces 26
4.3.1. Interfaces with the infrastructure TSIs 26
4.3.2. Interfaces with the control-command and signalling TSIs 27
4.3.3. Interfaces with the rolling stock TSI 27
4.3.3.1. Interfaces with TSI on locomotives and passenger rolling stock TSI 27
4.3.3.2. Interfaces with TSI on freight wagons 28
4.3.3.3. Interfaces with TSI on high-speed rolling stock 28
4.3.4. Interfaces with the Energy TSI 30
4.4. Operating rules 31
4.5. Maintenance rules 31
4.6. Professional qualifications 31
4.6.1. Professional competency 31
4.6.1.1. Professional knowledge 31
4.6.1.2. Ability to put this knowledge into practice 31
4.6.2. Linguistic competency 32
4.6.2.1. Principles 32
4.6.2.2. Level of knowledge 32
4.6.3. Initial and ongoing assessment of staff 32
4.6.3.1. Basic elements 32
4.6.3.2. Analysis of training needs 33
4.6.3.2.1 Development of the analysis of training needs 33
4.6.3.2.2 Updating the analysis of training needs 33
4.6.3.2.3 Specific elements for train crew and auxiliary staff 33
4.6.3.2.3.1 Infrastructure knowledge 33
4.6.3.2.3.2 Knowledge of rolling stock 33
4.6.3.2.3.3 Auxiliary staff 34
4.7. Health and safety conditions 34
4.7.1. Introduction 34
4.7.2. Deleted 34
4.7.3. Deleted 34
4.7.4. Medical examinations and psychological assessments 34
4.7.4.1. Before appointment: 34
4.7.4.1.1 Minimum content of the medical examination 34
4.7.4.1.2 Psychological assessment 34
4.7.4.2. After appointment 35
4.7.4.2.1 Periodicity of periodic medical examinations 35
4.7.4.2.2 Minimum content of the periodic medical examination 35
4.7.4.2.3 Additional medical examinations and/or psychological assessments 35
4.7.5. Medical requirements 35
4.7.5.1. General requirements 35
4.7.5.2. Vision requirements 36
4.7.5.3. Hearing requirements 36
4.8. Registers of infrastructure and vehicles 36
4.8.1. Infrastructure 36
4.8.2. Rolling stock 36
5. INTEROPERABILITY CONSTITUENTS 36
5.1. Definition 36
5.2. List of constituents 37
6. ASSESSMENT OF CONFORMITY AND/OR SUITABILITY FOR USE OF THE CONSTITUENTS AND VERIFICATION OF THE SUBSYSTEM 37
6.1. Interoperability constituents 37
6.2. Operation and traffic management subsystem 37
6.2.1. Principles 37
7. IMPLEMENTATION 37
7.1. Principles 37
7.2. Implementation guidelines 38
7.3. Specific cases 38
7.3.1. Introduction 38
7.3.2. List of specific cases 38
7.3.2.1. Temporary specific case (T1) Estonia, Latvia and Lithuania 38
7.3.2.2. Temporary specific case (T2) Ireland and United Kingdom 38
Appendix A: ERTMS/ETCS operating rules 38
Appendix B: Other rules enabling a coherent operation 39
Appendix C: Safety related communications methodology 40
Appendix D: Information to which the Railway Undertaking must have access in connection with the route(s) over which he intends to operate 50
Appendix E: Language and communication level 54
Appendix F: 55
Appendix G: 55
Appendix H: 55
Appendix I: 55
Appendix J: Minimum elements relevant to professional qualification for the tasks associated with ‘accompanying trains’ 56
Appendix K: 57
Appendix L: Minimum elements relevant to professional qualification for the task of preparing trains 58
Appendix M: 59
Appendix N: 59
Appendix O: 59
Appendix P: European Vehicle Number and linked alphabetical marking on the bodywork 60
Appendix Q: 62
Appendix R: 62
Appendix S: 62
Appendix T: Braking performance 63
Appendix U: List of open points 64
Appendix V: 64
Appendix W: Glossary 65
(a) indicates its intended scope for the ‘operation and traffic management’ subsystem — Chapter 2;
(b) lays down essential requirements for the subsystem concerned and its interfacesvis-à-visother subsystems — Chapter 3;
(c) establishes the functional and technical specifications to be met by the target subsystem and its interfacesvis-à-visother subsystems. If necessary, these specifications may vary according to the use of the subsystem, for example according to the categories of line, hub and/or rolling stock provided for in Annex I to Directive 2008/57/EC — Chapter 4;
(d) determines the interoperability constituents and interfaces covered by European specifications, including European standards, which are necessary to achieve interoperability within the European rail system — Chapter 5;
(e) states, in each case under consideration, which procedures are to be used in order to assess the conformity or suitability for use of the interoperability constituents — Chapter 6;
(f) indicates the strategy for implementing the TSI. In particular, it is necessary to specify the stages to be completed and the elements that can be applied in order to make a gradual transition from the existing situation to the final situation in which compliance with the TSI must be the norm — Chapter 7;
(g) indicates, for the staff concerned, the professional qualifications and health and safety conditions at work required for the operation and maintenance of the subsystem concerned, as well as for the implementation of the TSI — Chapter 4.
Task Professional Qualifications Medical Requirements
Accompanying a Train 4.6 4.7
Authorising Train movements Mutual recognition Mutual recognition
Train Preparation 4.6 Mutual recognition
Train Despatch Mutual recognition Mutual recognition
Task Professional Qualifications Medical Requirements
Accompanying a Train Mutual recognition Mutual recognition
Authorising Train movements Mutual recognition Mutual recognition
Train Preparation Mutual recognition Mutual recognition
Train Despatch Mutual recognition Mutual recognition
— safety,
— reliability and availability,
— health,
— environmental protection,
— technical compatibility.
Clause Clause Title Safety Reliability & Availability Health Environmental protection Technical compatibility Essential requirements specific to operation and traffic management
1.1.1 1.1.2 1.1.3 1.1.4 1.1.5 1.2 1.3.1 1.3.2 1.4.1 1.4.2 1.4.3 1.4.4 1.4.5 1.5 2.6.1 2.6.2 2.6.3
4.2.1.2 Documentation for drivers X X X
4.2.1.2.1 Rule book X X X
4.2.1.2.2 Route book X X
4.2.1.2.2.1 Preparation of the Route book X
4.2.1.2.2.2 Modification to Information contained within the route book X X
4.2.1.2.2.3 Informing the driver in real time X X X
4.2.1.2.3 Timetables X X X
4.2.1.2.4 Rolling stock X X X
4.2.1.3 Documentation for railway undertaking staff other than drivers X X X
4.2.1.4 Documentation for infrastructure manager’s staff authorising train movements X X X
4.2.1.5 Safety-related communications between train crew, other railway undertaking staff and staff authorising train movements X X X X
4.2.2.1 Train visibility X X X
4.2.2.1.1 General requirement X X X
4.2.2.1.2 Front end X X X
4.2.2.1.3 Rear end X X X
4.2.2.2 Train audibility X X X X
4.2.2.2.1 General requirement X X X
4.2.2.2.2 Control X X
4.2.2.3 Vehicle identification X X X
4.2.2.4 Safety of passengers and load X
4.2.2.5 Train composition X
4.2.2.6 Train braking X X X
4.2.2.6.1 Minimum requirements of the braking system X X X
4.2.2.6.2 Braking performance X X X
4.2.2.7 Ensuring that the train is in running order X X X
4.2.2.7.1 General requirement X X
4.2.2.7.2 Data required X X
4.2.2.8 Requirements for Signal and lineside marker sighting X X
4.2.2.9 Driver vigilance X
4.2.3.1 Train planning X X X
4.2.3.2 Identification of trains X X X
4.2.3.3 Train departure X X
4.2.3.3.1 Checks and tests before departure X X X X
4.2.3.3.2 Informing the Infrastructure Manager of the train’s operational status X X X X
4.2.3.4 Traffic management X X X
4.2.3.4.1 General requirements X X X
4.2.3.4.2 Train reporting X X X
4.2.3.4.2.1 Data required for train position reporting X X
4.2.3.4.2.2 Predicted hand over time X X
4.2.3.4.3 Dangerous goods X X
4.2.3.4.4 Operational quality X X
4.2.3.5 Data recording X X
4.2.3.5.1 Recording of supervision data outside the train X X
4.2.3.5.2 Recording of supervision data on-board the train X X
4.2.3.6 Degraded operation X X X
4.2.3.6.1 Advice to other users X X
4.2.3.6.2 Advice to train drivers X
4.2.3.6.3 Contingency arrangements X X X
4.2.3.7 Managing an emergency situation X X X
4.2.3.8 Aid to train crew in the event of an incident or of a major rolling stock malfunction X
4.4 Operating rules X X
4.6 Professional qualifications X X X
4.7 Health and safety conditions X
— specifications relating to staff,
— specifications relating to trains,
— specifications relating to train operations.
(1) Railway undertaking staff:(a)undertaking the task of driving trains (referred to throughout this TSI as ‘driver’) and forming part of the ‘train crew’,(b)undertaking tasks on-board (other than driving) and forming part of the ‘train crew’,(c)undertaking the task of preparing trains. (a) undertaking the task of driving trains (referred to throughout this TSI as ‘driver’) and forming part of the ‘train crew’, (b) undertaking tasks on-board (other than driving) and forming part of the ‘train crew’, (c) undertaking the task of preparing trains.
(a) undertaking the task of driving trains (referred to throughout this TSI as ‘driver’) and forming part of the ‘train crew’,
(b) undertaking tasks on-board (other than driving) and forming part of the ‘train crew’,
(c) undertaking the task of preparing trains.
(a) undertaking the task of driving trains (referred to throughout this TSI as ‘driver’) and forming part of the ‘train crew’,
(b) undertaking tasks on-board (other than driving) and forming part of the ‘train crew’,
(c) undertaking the task of preparing trains.
(2) Infrastructure manager’s staff undertaking the task of authorising the movement of trains
— Documentation
— Communication
— Qualifications (see point 4.6 and Appendix L)
— Health and safety conditions (see point 4.7)
— one which describes the set of common rules and procedures (taking into account the contents of Appendices A, B and C),
— another which sets out any necessary rules and procedures specific to each infrastructure manager.
— Staff safety and security,
— Signalling and control-command,
— Train operation including degraded mode,
— Traction and rolling stock,
— Incidents and accidents.
— Appendix 1: Manual of communication procedures;
— Appendix 2: Book of Forms.
— the infrastructure manager (or the organisation responsible for the preparation of the operating rules) must provide the railway undertaking with the appropriate information in the infrastructure manager’s operating language,
— the railway undertaking must draw up the initial or updated document;
— if the language chosen by the railway undertaking for the Driver’s Rule Book is not the language in which the appropriate information was originally supplied, it is the responsibility of the railway undertaking to arrange for any necessary translation and/or provide explanatory notes in another language.
— the general operating characteristics,
— indication of rising and falling gradients,
— detailed line diagram.
(a) the general operating characteristics:—type of signalling and corresponding running regime (double track, reversible working, left or right hand running, etc.),—type of power supply,—type of ground-train radio equipment. — type of signalling and corresponding running regime (double track, reversible working, left or right hand running, etc.), — type of power supply, — type of ground-train radio equipment.
— type of signalling and corresponding running regime (double track, reversible working, left or right hand running, etc.),
— type of power supply,
— type of ground-train radio equipment.
— type of signalling and corresponding running regime (double track, reversible working, left or right hand running, etc.),
— type of power supply,
— type of ground-train radio equipment.
(b) indication of rising and falling gradients with their gradient values and location;
(c) detailed line diagram:—names of stations on the line and key locations and their location;—tunnels, including location, name, length, specific information such as the existence of walkways and points of safe egress as well as the location of safe places where evacuation of passengers can take place—essential locations such as neutral sections—permissible speed limits for each track, including, if necessary, differential speeds relating to certain types of train,—the responsible infrastructure manager—means of communication with the traffic management/control centre in normal and degraded mode — names of stations on the line and key locations and their location; — tunnels, including location, name, length, specific information such as the existence of walkways and points of safe egress as well as the location of safe places where evacuation of passengers can take place — essential locations such as neutral sections — permissible speed limits for each track, including, if necessary, differential speeds relating to certain types of train, — the responsible infrastructure manager — means of communication with the traffic management/control centre in normal and degraded mode
— names of stations on the line and key locations and their location;
— tunnels, including location, name, length, specific information such as the existence of walkways and points of safe egress as well as the location of safe places where evacuation of passengers can take place
— essential locations such as neutral sections
— permissible speed limits for each track, including, if necessary, differential speeds relating to certain types of train,
— the responsible infrastructure manager
— means of communication with the traffic management/control centre in normal and degraded mode
— names of stations on the line and key locations and their location;
— tunnels, including location, name, length, specific information such as the existence of walkways and points of safe egress as well as the location of safe places where evacuation of passengers can take place
— essential locations such as neutral sections
— permissible speed limits for each track, including, if necessary, differential speeds relating to certain types of train,
— the responsible infrastructure manager
— means of communication with the traffic management/control centre in normal and degraded mode
— the train identification;
— the train running days (if necessary);
— the stopping points and the activities associated with them
— other timing points;
— the arrival/departure/passing times at each of those points.
— documents describing the Communications Principles (Appendix C);
— the document entitled Book of forms.
— 2 steady red lights, or
— 2 reflective plates of the following shape with white side triangles and red top and bottom triangle:
(a) the vehicles—all vehicles in the train must be in compliance with all the requirements applicable on the routes over which the train will run;—all vehicles on the train must be fit to run at the maximum speed at which the train is scheduled to run;—all vehicles on the train must be currently within their specified maintenance interval and will remain so for the duration (in terms of both time and distance) of the journey being undertaken; — all vehicles in the train must be in compliance with all the requirements applicable on the routes over which the train will run; — all vehicles on the train must be fit to run at the maximum speed at which the train is scheduled to run; — all vehicles on the train must be currently within their specified maintenance interval and will remain so for the duration (in terms of both time and distance) of the journey being undertaken;
— all vehicles in the train must be in compliance with all the requirements applicable on the routes over which the train will run;
— all vehicles on the train must be fit to run at the maximum speed at which the train is scheduled to run;
— all vehicles on the train must be currently within their specified maintenance interval and will remain so for the duration (in terms of both time and distance) of the journey being undertaken;
— all vehicles in the train must be in compliance with all the requirements applicable on the routes over which the train will run;
— all vehicles on the train must be fit to run at the maximum speed at which the train is scheduled to run;
— all vehicles on the train must be currently within their specified maintenance interval and will remain so for the duration (in terms of both time and distance) of the journey being undertaken;
(b) the train—the combination of vehicles forming a train must comply with the technical constraints of the route concerned and be within the maximum length permissible for forwarding and receiving terminals.—the railway undertaking is responsible for ensuring that the train is technically fit for the journey to be undertaken and remains so throughout the journey — the combination of vehicles forming a train must comply with the technical constraints of the route concerned and be within the maximum length permissible for forwarding and receiving terminals. — the railway undertaking is responsible for ensuring that the train is technically fit for the journey to be undertaken and remains so throughout the journey
— the combination of vehicles forming a train must comply with the technical constraints of the route concerned and be within the maximum length permissible for forwarding and receiving terminals.
— the railway undertaking is responsible for ensuring that the train is technically fit for the journey to be undertaken and remains so throughout the journey
— the combination of vehicles forming a train must comply with the technical constraints of the route concerned and be within the maximum length permissible for forwarding and receiving terminals.
— the railway undertaking is responsible for ensuring that the train is technically fit for the journey to be undertaken and remains so throughout the journey
(c) the weight and axle load—the weight of the train must be within the maximum permissible for the section of route, the strength of the couplings, the traction power and other relevant characteristics of the train. Axle load limitations must be respected. — the weight of the train must be within the maximum permissible for the section of route, the strength of the couplings, the traction power and other relevant characteristics of the train. Axle load limitations must be respected.
— the weight of the train must be within the maximum permissible for the section of route, the strength of the couplings, the traction power and other relevant characteristics of the train. Axle load limitations must be respected.
— the weight of the train must be within the maximum permissible for the section of route, the strength of the couplings, the traction power and other relevant characteristics of the train. Axle load limitations must be respected.
(d) the maximum speed of the train—the maximum speed at which the train can run must take into account any restrictions on the route(s) concerned, braking performance, axle load and vehicle type. — the maximum speed at which the train can run must take into account any restrictions on the route(s) concerned, braking performance, axle load and vehicle type.
— the maximum speed at which the train can run must take into account any restrictions on the route(s) concerned, braking performance, axle load and vehicle type.
— the maximum speed at which the train can run must take into account any restrictions on the route(s) concerned, braking performance, axle load and vehicle type.
(e) the kinematic envelope—the kinematic gauge of each vehicle (inclusive of any load) in the train must be within the maximum permissible for the section of route. — the kinematic gauge of each vehicle (inclusive of any load) in the train must be within the maximum permissible for the section of route.
— the kinematic gauge of each vehicle (inclusive of any load) in the train must be within the maximum permissible for the section of route.
— the kinematic gauge of each vehicle (inclusive of any load) in the train must be within the maximum permissible for the section of route.
— the train identification
— the identity of the railway undertaking responsible for the train
— the actual length of the train
— if a train carries passengers or animals when it is not scheduled to do so
— any operational restrictions with an indication of the vehicle(s) concerned (gauge, speed restrictions, etc.)
— information the infrastructure manager requires for the transport of dangerous goods.
— the real time management of trains,
— operational measures to maintain the highest possible performance of the infrastructure in case of delays or incidents, whether actual or anticipated, and
— the provision of information to the railway undertaking(s) in such cases.
(a) provide a means of real time recording of the times at which trains depart from, arrive at or pass appropriate pre-defined reporting points on their networks and the delta-time value;
(b) provide the specific data required in relation to train position reporting. Such information must include:—Train identification—Identity of reporting point—Line on which the train is running—Scheduled time at reporting point—Actual time at reporting point (and whether depart, arrive or pass — separate arrival and departure times must be provided in respect of intermediate reporting points at which the train calls)—Number of minutes early or late at the reporting point—Initial explanation of any single delay exceeding 10 minutes or as otherwise required by the performance monitoring regime—Indication that a report for a train is overdue and the number of minutes by which it is overdue—Former train identification(s), if any—Train cancelled for a whole or a part of its journey. — Train identification — Identity of reporting point — Line on which the train is running — Scheduled time at reporting point — Actual time at reporting point (and whether depart, arrive or pass — separate arrival and departure times must be provided in respect of intermediate reporting points at which the train calls) — Number of minutes early or late at the reporting point — Initial explanation of any single delay exceeding 10 minutes or as otherwise required by the performance monitoring regime — Indication that a report for a train is overdue and the number of minutes by which it is overdue — Former train identification(s), if any — Train cancelled for a whole or a part of its journey.
— Train identification
— Identity of reporting point
— Line on which the train is running
— Scheduled time at reporting point
— Actual time at reporting point (and whether depart, arrive or pass — separate arrival and departure times must be provided in respect of intermediate reporting points at which the train calls)
— Number of minutes early or late at the reporting point
— Initial explanation of any single delay exceeding 10 minutes or as otherwise required by the performance monitoring regime
— Indication that a report for a train is overdue and the number of minutes by which it is overdue
— Former train identification(s), if any
— Train cancelled for a whole or a part of its journey.
— Train identification
— Identity of reporting point
— Line on which the train is running
— Scheduled time at reporting point
— Actual time at reporting point (and whether depart, arrive or pass — separate arrival and departure times must be provided in respect of intermediate reporting points at which the train calls)
— Number of minutes early or late at the reporting point
— Initial explanation of any single delay exceeding 10 minutes or as otherwise required by the performance monitoring regime
— Indication that a report for a train is overdue and the number of minutes by which it is overdue
— Former train identification(s), if any
— Train cancelled for a whole or a part of its journey.
— the provisions as specified in Directive 2008/68/EC of the European Parliament and of the Council(8);
— advice to the driver of the presence and position of dangerous goods on the train;
— information the infrastructure manager requires for transport of dangerous goods;
— determination, in conjunction with the infrastructure manager, of lines of communication and planning of specific measures in case of emergency situations involving the goods.
— supporting systematic safety monitoring as a means of preventing incidents and accidents;
— identifying driver, train and infrastructure performance in the period leading up to and (if appropriate) immediately after an incident or accident, to enable the identification of causes related to train driving or train equipment, and supporting the case for new or changed measures to prevent recurrence;.
— recording information relating to the performance of both the locomotive/traction unit and the person driving.
— the date and time of the recording;
— the precise geographic location of the event being recorded (distance in kilometres from a recognisable location);
— the train identification;
— the identity of the driver.
— in which the railway undertaking is licensed (with regard to on-board recorded data), or
— of the Member State in which the infrastructure is located (with regard to data recorded outside the train).
— the failure of line-side equipment associated with the movement of trains (signalling, points etc.);
— the detection of an overheating axle bearing, where this equipment is provided;
— communication between the train driver and infrastructure manager’s staff authorising train movements.
— the passing of signals at danger or ‘end of movement authority’ without authority;
— application of the emergency brake;
— speed at which the train is running;
— any isolation or overriding of the on-board train control (signalling) systems;
— operation of the audible warning device (horn);
— operation of door controls (release, closure);
— detection by on-board hot axle box detectors, if fitted;
— identity of the cab for which data is being recorded to be checked.
— rolling stock failures (for example, those which could result in substantial traffic disruption, the procedures for rescuing failed trains);
— infrastructure failures (for example, when there has been a failure of the electric power or the conditions under which trains may be diverted from the booked route);
— extreme weather conditions.
— all railway undertakings operating over his infrastructure, or, where appropriate, representative bodies of railway undertakings operating over his infrastructure;
— neighbouring infrastructure managers, as appropriate;
— local authorities, representative bodies of the emergency services (including fire fighting and rescue) at either local or national level, as appropriate.
— collisions,
— fires on train,
— evacuation of trains,
— accidents in tunnels,
— incidents involving dangerous goods,
— derailments.
Reference operation TSI Reference conventional rail infrastructure TSI
Parameter Point Parameter Point
Braking performance 4.2.2.6.2 Longitudinal track resistance 4.2.7.2
Modifications to information contained in the route book 4.1.2.2.2 Operating rules 4.4
Degraded operation 4.2.3.6
Reference operation TSI Reference high speed rail infrastructure TSI
Parameter Point Parameter Point
Staff and trains 2.2.1 Professional competences 4.6
Reference operation TSI Reference control-command and signalling TSI
Parameter Point Parameter Point
Rule book 4.2.1.2.1 Track-side train detection systems 4.2.10
Operating rules 4.4 Operating rules 4.4
Signal and lineside marker sighting 4.2.2.8 Visibility of track-side control-command and signalling objects 4.2.15
Braking performance 4.2.2.6 Train braking performance and characteristics 4.2.2
Train running number 4.2.3.2.1 ETCS DMI 4.2.12
GSM-R DMI 4.2.13
Data recording on-board 4.2.3.5 Interface to data recording for regulatory purposes 4.2.14
Reference operation TSI Reference conventional rail locom. and pass. TSI
Parameter Point Parameter Point
Contingency arrangements 4.2.3.6.3 Rescue coupling 4.2.2.2.4
Train composition 4.2.2.5 Interface with infrastructure: axle load and wheel load 4.2.3.2
Minimum requirements of the braking system 4.2.2.6.1 Braking performance 4.2.4.5
Train visibility 4.2.2.1 External lights 4.2.7.1
Train audibility 4.2.2.2 Horn 4.2.7.2
Signal sighting 4.2.2.8 External visibility 4.2.9.1.3
Optical characteristics of the windscreen 4.2.9.2.2
Internal lighting 4.2.9.1.8
Driver vigilance 4.2.2.9 Driver’s activity control function 4.2.9.3.1
Data recording 4.2.3.5.2 Recording device 4.2.9.6
Reference operation TSI Reference conventional freight wagon TSI
Parameter Point Parameter Point
Rear end 4.2.2.1.3.2 Attachment devices for rear-end signal 4.2.6.3
Rear end 4.2.2.1.3.2 Rear-end signal Annex E
Train composition 4.2.2.5 Gauging 4.2.3.1
Train composition 4.2.2.5 Compatibility with load carrying capacity of lines 4.2.3.2
Contingency arrangements 4.2.3.6.3 Lifting and jacking 4.2.2.2
Train braking 4.2.2.6 Brake 4.2.4
Reference operation TSI Reference high speed rolling stock TSI
Parameter Point Parameter Point
Train composition 4.2.2.5 Minimum braking performance 4.2.4.1
Minimum requirements of the braking system 4.2.2.6.1 Brake system requirements 4.2.4.3
Braking performance 4.2.2.6.2
Braking performance 4.2.2.6.2 Eddy current brakes 4.2.4.5
Braking performance 4.2.2.6.2 Protection of an immobilised train 4.2.4.6
Braking performance 4.2.2.6.2 Brake performance on steep gradients 4.2.4.7
Informing the driver in real time 4.2.1.2.2.3
Requirements for passenger vehicles 4.2.2.4 Access 4.2.2.4
Passenger alarm 4.2.5.3
Emergency exits 4.2.7.1
Front end 4.2.2.1.2 Front and rear lights 4.2.7.4.1
Rear end 4.2.2.1.3 Front and rear lights 4.2.7.4.1
Train audibility 4.2.2.2 horns 4.2.7.4.2
Signal sighting and lineside marker sighting 4.2.2.8 Windscreen and front of the train 4.2.2.7
Driver vigilance 4.2.2.9 Driver’s vigilance device 4.2.7.8
Train composition 4.2.2.5 End couplers and coupling arrangements to rescue trains 4.2.2.2
Contingency arrangements 4.2.3.6.3
Managing and emergency situation 4.2.3.7 Coupler Annex K
Maximum train length 4.2.3.5
Degraded operation 4.2.3.6 Axle bearing health monitoring 4.2.3.3.2
Rolling stock dynamic behaviour 4.2.3.4
Sanding Appendix B (C1) sanding 4.2.3.10
Train crew knowledge of rolling stock functionality 4.2.2.5 Design of train 4.2.1.2
Appendix J Monitoring and diagnostic concepts 4.2.7.10
Contingency arrangements 4.2.3.6.3 End couplers and coupling arrangements to rescue trains 4.2.2.2
Managing an emergency situation 4.2.3.7 coupler Annex K
Degraded operation 4.2.3.6 Emergency measures 4.2.7.1
Managing an emergency situation 4.2.3.7 Fire safety 4.2.7.2
Recording of supervision data on-board the train 4.2.3.5.2 Monitoring and diagnostic concepts 4.2.7.10
Informing the driver in real time 4.2.1.2.2.3 Ballast pick up 4.2.3.11
Train composition 4.2.2.5 Environmental conditions 4.2.6.1
Informing the Infrastructure Manager of the train’s operational status 4.2.3.3.2.
Informing the driver in real time 4.2.1.2.2.3 Crosswind 4.2.6.3
Degraded operation 4.2.3.6
Informing the driver in real time 4.2.1.2.2.3 Maximum pressure variations in tunnels 4.2.6.4
Degraded operation 4.2.3.6
Managing an emergency situation 4.2.3.7 Exterior noise 4.2.6.5
Managing an emergency situation 4.2.3.7 Fire safety 4.2.7.2
Managing an emergency situation 4.2.3.7 Lifting/rescue procedures 4.2.7.5
Recording of supervision data on-board the train 4.2.3.5.2 Particular specification for tunnels 4.2.7.11
Appendix J
Preparation of the route book 4.2.1.2.2.1 Emergency lighting systems 4.2.7.12
Managing an emergency situation 4.2.3.7
Auxiliary staff 4.6.3.2.3.3
Train composition 4.2.2.5 Traction performance requirements 4.2.8.1
Informing the Infrastructure Manager of the train’s operational status 4.2.3.3.2
Informing the Infrastructure Manager of the train’s operational status 4.2.3.3.2 Traction wheel/rail adhesion requirements 4.2.8.2
Degraded operation 4.2.3.6
Description of the line and relevant lineside equipment associated with the lines worked over 4.2.1.2.2
Degraded operation 4.2.3.6 Functional and technical specification related to the electric power supply 4.2.8.3
Description of the line and relevant lineside equipment associated with the lines worked over 4.2.1.2.2
Reference operation TSI Reference conventional rail energy TSI
Parameter Point Parameter Point
Description of the line and the relevant lineside equipment associated with the lines worked over 4.2.1.2.2 Management of power supply 4.4.2
Informing the driver in real time 4.2.1.2.2.3
Modifications to information contained within the route book 4.2.1.2.2.2 Execution of works 4.4.3
Reference operation TSI Reference high speed rail energy TSI
Parameter Point Parameter Point
Staff and trains 2.2.1 Professional competences 4.6
(a) general railway operation with particular emphasis on safety-critical activity:—principles of operation of their organisation’s safety management system;—the roles and responsibilities of the key players involved in interoperable operations;—appreciation of hazards, especially in relation to the risks involving railway operation and electric traction supply. — principles of operation of their organisation’s safety management system; — the roles and responsibilities of the key players involved in interoperable operations; — appreciation of hazards, especially in relation to the risks involving railway operation and electric traction supply.
— principles of operation of their organisation’s safety management system;
— the roles and responsibilities of the key players involved in interoperable operations;
— appreciation of hazards, especially in relation to the risks involving railway operation and electric traction supply.
— principles of operation of their organisation’s safety management system;
— the roles and responsibilities of the key players involved in interoperable operations;
— appreciation of hazards, especially in relation to the risks involving railway operation and electric traction supply.
(b) appropriate knowledge of safety-related tasks in respect to procedures and interfaces for:—lines and line-side equipment;—rolling stock;—the environment. — lines and line-side equipment; — rolling stock; — the environment.
— lines and line-side equipment;
— rolling stock;
— the environment.
— lines and line-side equipment;
— rolling stock;
— the environment.
— the method and principles for applying these rules and procedures;
— the process for the use of line-side equipment and rolling stock, as well as any specific safety-related equipment;
— the principles of the safety management system to avoid the introduction of any undue risk to people and process.
(a) As a minimum this must comprise of the driver being able to:—send and understand all the messages specified in Appendix C to this TSI;—effectively communicate in routine, degraded and emergency situations;—complete the forms associated with the use of the Book of Forms; — send and understand all the messages specified in Appendix C to this TSI; — effectively communicate in routine, degraded and emergency situations; — complete the forms associated with the use of the Book of Forms;
— send and understand all the messages specified in Appendix C to this TSI;
— effectively communicate in routine, degraded and emergency situations;
— complete the forms associated with the use of the Book of Forms;
— send and understand all the messages specified in Appendix C to this TSI;
— effectively communicate in routine, degraded and emergency situations;
— complete the forms associated with the use of the Book of Forms;
(b) Other members of the train crew whose duties require them to communicate with the infrastructure manager on safety-critical matters, must as a minimum, be able to send and understand information describing the train and its operational status.
A. Selection of personnel—evaluation of individual experience and competence;—evaluation of individual competence in the use of any required foreign language(s) or the aptitude to learn them. — evaluation of individual experience and competence; — evaluation of individual competence in the use of any required foreign language(s) or the aptitude to learn them.
— evaluation of individual experience and competence;
— evaluation of individual competence in the use of any required foreign language(s) or the aptitude to learn them.
— evaluation of individual experience and competence;
— evaluation of individual competence in the use of any required foreign language(s) or the aptitude to learn them.
B. Initial professional training—analysis of training needs;—training resources;—training of the trainers. — analysis of training needs; — training resources; — training of the trainers.
— analysis of training needs;
— training resources;
— training of the trainers.
— analysis of training needs;
— training resources;
— training of the trainers.
C. Initial assessment—basic conditions;—assessment programme, including practical demonstration;—qualification of the trainers;—deliver a certificate of competency. — basic conditions; — assessment programme, including practical demonstration; — qualification of the trainers; — deliver a certificate of competency.
— basic conditions;
— assessment programme, including practical demonstration;
— qualification of the trainers;
— deliver a certificate of competency.
— basic conditions;
— assessment programme, including practical demonstration;
— qualification of the trainers;
— deliver a certificate of competency.
D. Competency retention—principles for retention of competency;—methods to be followed;—formalisation of the competency retention process;—assessment process. — principles for retention of competency; — methods to be followed; — formalisation of the competency retention process; — assessment process.
— principles for retention of competency;
— methods to be followed;
— formalisation of the competency retention process;
— assessment process.
— principles for retention of competency;
— methods to be followed;
— formalisation of the competency retention process;
— assessment process.
E. Refresher training—principles for on-going training (including language). — principles for on-going training (including language).
— principles for on-going training (including language).
— principles for on-going training (including language).
— differences in operating practices between infrastructure managers and the risks associated with changing between these;
— the differences between tasks, operating procedures and communication protocols;
— any difference in the ‘operating’ language used by the infrastructure manager’s personnel;
— local operating instructions which may include special procedures or particular equipment to be applied in certain cases, for example a specific tunnel.
— based upon the route information provided by the infrastructure manager and
— in accordance with the process described in point 4.2.1.
— General medical examination;
— Examinations of sensory functions (vision, hearing, colour perception);
— Urine or blood analysis for the detection of diabetes mellitus and other conditions as indicated by the clinical examination;
— Screening for drugs of abuse.
(a) Cognitive:—Attention and concentration,—Memory,—Perceptive capability,—Reasoning,—Communication. — Attention and concentration, — Memory, — Perceptive capability, — Reasoning, — Communication.
— Attention and concentration,
— Memory,
— Perceptive capability,
— Reasoning,
— Communication.
— Attention and concentration,
— Memory,
— Perceptive capability,
— Reasoning,
— Communication.
(b) Psychomotor:—Speed of reaction,—Gestured coordination. — Speed of reaction, — Gestured coordination.
— Speed of reaction,
— Gestured coordination.
— Speed of reaction,
— Gestured coordination.
(c) Behavioural and personality—Emotional self-control,—Behavioural reliability,—Autonomy,—Conscientiousness. — Emotional self-control, — Behavioural reliability, — Autonomy, — Conscientiousness.
— Emotional self-control,
— Behavioural reliability,
— Autonomy,
— Conscientiousness.
— Emotional self-control,
— Behavioural reliability,
— Autonomy,
— Conscientiousness.
— Every 5 years for staff aged up to 40;
— Every 3 years for staff aged between 41 and 62;
— Every year for staff aged over 62.
— General medical examination;
— Examination of sensory functions (vision, hearing, colour perception);
— Urine or blood analysis for the detection of diabetes mellitus and other conditions as indicated by the clinical examination;
— Screening for drugs of abuse where clinically indicated.
— Sudden loss of consciousness;
— Impairment of awareness or concentration;
— Sudden incapacity;
— Impairment of balance or coordination;
— Significant limitation of mobility.
— Aided or unaided distance visual acuity: 0,8 (right eye + left eye — measured separately); minimum of 0,3 for the worse eye;
— Maximum corrective lenses: hypermetropia + 5/myopia — 8. The occupational doctor may allow values outside this range in exceptional cases and after having sought the opinion of an eye specialist;
— Intermediate and near vision: sufficient whether aided or unaided;
— Contact lenses are allowed;
— Normal colour vision: using a recognised test, such as the Ishihara, completed by another recognised test if required;
— Vision field: normal (absence of any abnormality affecting the task to be performed);
— Vision for both eyes: present;
— Binocular vision: present;
— Contrast sensitivity: good;
— Absence of progressive eye disease;
— Lens implants, keratotomies and keratectomies are allowed only on condition that they are checked on a yearly basis or according to a periodicity set by the occupational doctor.
— Hearing good enough to keep a phone conversation going and be able to hear alert tones and radio messages.
— The following values given for information should be taken as guidelines:
— The hearing deficiency must not be higher than 40 dB at 500 and 1 000 Hz;
— The hearing deficiency must not be higher than 45 dB at 2 000 Hz for the ear with the worst air conduction of sound.
— whether the vehicle is constructed from materials which can be hazardous in case of accidents or fire (for example, asbestos);
— total length of the vehicle, including buffers if existing.
(a) the specific human factors issues associated with operating any given line;
(b) the individual operating and safety elements of each line involved; and
(c) whether implementation of the element(s) under consideration is to be:—for all trains on the line, or not,—only for certain lines,—applicable on all lines,—applicable to all trains running on the network — for all trains on the line, or not, — only for certain lines, — applicable on all lines, — applicable to all trains running on the network
— for all trains on the line, or not,
— only for certain lines,
— applicable on all lines,
— applicable to all trains running on the network
— for all trains on the line, or not,
— only for certain lines,
— applicable on all lines,
— applicable to all trains running on the network
(d) the relationship with implementation with the other subsystems (control-command and signalling, rolling stock, etc.).
(a) a railway undertaking or infrastructure manager commences operations,
(b) a renewal or upgrade to the existing operational systems of a railway undertaking or infrastructure manager is introduced,
(c) new or upgraded infrastructure, energy, rolling stock or control-command and signalling subsystems, requiring a corresponding set of operating procedures, are put into service.
(a) Confirmation that any existing systems and processes comply with the requirements of this TSI;
(b) Adaptation of any existing systems and processes to comply with the requirements of this TSI;
(c) New systems and processes arising from implementation of other subsystems;—New/upgraded conventional lines (infrastructure/energy),—New or upgraded ETCS signalling installations, GSM-R radio installations, Hot Axle Box Detectors, … (control-command and signalling),—New rolling stock (rolling stock). — New/upgraded conventional lines (infrastructure/energy), — New or upgraded ETCS signalling installations, GSM-R radio installations, Hot Axle Box Detectors, … (control-command and signalling), — New rolling stock (rolling stock).
— New/upgraded conventional lines (infrastructure/energy),
— New or upgraded ETCS signalling installations, GSM-R radio installations, Hot Axle Box Detectors, … (control-command and signalling),
— New rolling stock (rolling stock).
— New/upgraded conventional lines (infrastructure/energy),
— New or upgraded ETCS signalling installations, GSM-R radio installations, Hot Axle Box Detectors, … (control-command and signalling),
— New rolling stock (rolling stock).
— the provisions apply either permanently (case ‘P’), or temporarily (case ‘T’).
— in temporary cases Member States shall conform with the relevant subsystem either by 2016 (case ‘T1’), or by 2024 (case ‘T2’).
— in the area of points and crossings,
— during braking at speeds less than 20 km/h,
— when at a standstill.
— if there is a risk of SPAD (Signal Passed at Danger), or other serious incident and the application of sand would assist adhesion,
— when starting away, or
— when required to test the sanding equipment on the traction unit. (Testing shall not be undertaken in areas specifically designated in the Infrastructure Register).
— define the nature and structure of the safety-related messages;
— define the methodology for voice transmission of those messages.
— in order to enable the infrastructure manager to draw up the messages and books of forms. These elements shall be addressed to the railway undertaking at the same time as the rules and regulations are made available; for the Infrastructure Manager and the Railway Undertaking to draw up the documents for their staff (Books of Forms), instructions for staff authorising train movements and Appendix 1 to the Driver’s Rule Book ‘Manual of communication procedures’.
— urgent (emergency) verbal messages;
— written orders;
— additional performance messages.
— upon receiving a direct messageTerm confirming that the sent message has been received:receivedTerm used to have the message repeated in the event of poor reception or misunderstandingsay again (+ speak slowly)
— upon reception of a message that has been read-backTerms used to ascertain whether a read-back message exactly matches the sent message:corrector not:error (+ I say again)
— if the message has ended:out
— if break is temporary and does not break the connectionTerm used to keep the other party waiting:wait
— if break is temporary but the connection is brokenTerm used to tell the other party that the communication is going to be broken but will be resumed later on:I call again
— error during transmissionWhen a transmission error is discovered by the sender himself, the sender must request cancellation by sending the following procedure message:error (+ prepare new form…)or:error + I say againand then send the initial message again.
— error during read-backWhen the sender discovers an error whilst the message is being read back to him, the sender shall send the following procedure messages:error + I say againand send the initial message again.
A Alpha
B Bravo
C Charlie
D Delta
E Echo
F Foxtrot
G Golf
H Hotel
I India
J Juliet
K Kilo
L Lima
M Mike
N November
O Oscar
P Papa
Q Quebec
R Romeo
S Sierra
T Tango
U Uniform
V Victor
W Whisky
X X-ray
Y Yankee
Z Zulu
0 Zero
1 One
2 Two
3 Three
4 Four
5 Five
6 Six
7 Seven
8 Eight
9 Nine
— identification and request for instructions;
— transmission of the message itself and termination of the transmission.
— by the staff authorising train movements:train …(number)this is … Signals(name) train …(number)this is … Signals(name)
train …(number)this is … Signals(name)
train …(number)this is … Signals(name)
— by the driver:… Signals(name)this is train …(number) … Signals(name)this is train …(number)
… Signals(name)this is train …(number)
… Signals(name)this is train …(number)
— may be sent or received while running;
— may skip the identification part;
— shall be repeated;
— shall, as soon as possible, be followed by further information.
— if the message concerns an action for which the driver requires a specific authorisation (e.g. passing a signal at danger,…):authorisation…(number) authorisation…(number)
authorisation…(number)
authorisation…(number)
— in all other cases (e.g. proceeding with caution,…):message…(number) message…(number)
message…(number)
message…(number)
— shall be preceded by the identification procedure;
— shall be short and precise (limited wherever possible to information to be communicated and where it applies);
— shall be read back and followed by an acknowledgement of correct read-back, or not
— may be followed by a request for instructions or a request for further information.
— preceded by the identification procedure;
— prepared before sending;
— read back and followed by an acknowledgement of correct read-back, or not.
— provide a common working document used in real-time by the staff authorising train movements and by the drivers;
— provide the driver (especially when working in an unfamiliar or rare environment) with a reminder of the procedure he will required to follow;
— enable traceability of communications.
— a reminder about the utilisation of the Book of Forms;
— an index of ground-originated Procedure Forms;
— an index of driver-originated Procedure Forms, where appropriate;
— the list of situations cross-referencing to which procedure form is to be used;
— a glossary giving the situations to which each procedure form applies;
— the code for spelling out messages (phonetic alphabet etc.).
— by the driver to inform the staff authorising train movements, or
— by the staff authorising train movements to advise the driver
Stage in the communication flow Message element
Reason for passing the information for informationfor action for information for action
for information
for action
Observation There isI sawI hadI hit There is I saw I had I hit
There is
I saw
I had
I hit
Position
—along the line — along the line at …(station name)…(characteristic point)at mile post/kilometre point …(number) at …(station name) …(characteristic point) at mile post/kilometre point …(number)
— along the line
at …(station name)
…(characteristic point)
at mile post/kilometre point …(number)
—in respect to my train — in respect to my train power car …(number)trailer car …(number) power car …(number) trailer car …(number)
— in respect to my train
power car …(number)
trailer car …(number)
Nature—object—person — object — person …(see glossary)
— object
— person
State
—static — static standing onlying onfallen on standing on lying on fallen on
— static
standing on
lying on
fallen on
—moving — moving walkingrunningtowards walking running towards
— moving
walking
running
towards
Location with respect to the tracks
for information
for action
There is
I saw
I had
I hit
— along the line
at …(station name)
…(characteristic point)
at mile post/kilometre point …(number)
— in respect to my train
power car …(number)
trailer car …(number)
— object
— person
— static
standing on
lying on
fallen on
— moving
walking
running
towards
— a listing of terms by subject matter;
— a listing of the terms in alphabetical order.
(a) Need to stop all trains:The need to stop all trains must be transmitted by means of an acoustic signal; if this is not available the following phrase must be used:Emergency, stop all trainsInformation on location or area is, if necessary, specified in the message.In addition, this message is to be quickly complemented, if possible, by the reason, the location of the emergency and the train’s identification:ObstructionOr FireOr…(other reason)on line…at…(name) (km)Driver of train…(number) ObstructionOr FireOr…(other reason)on line…at…(name) (km)Driver of train…(number)
ObstructionOr FireOr…(other reason)on line…at…(name) (km)Driver of train…(number)
ObstructionOr FireOr…(other reason)on line…at…(name) (km)Driver of train…(number)
(b) Need to stop a particular train:Train…(on line/track)(number) (name/number)In this circumstance the name or number of the line or track on which the train is running may be used to complement the message. Train…(on line/track)(number) (name/number)
Train…(on line/track)(number) (name/number)
Train…(on line/track)(number) (name/number)
At…(km)on…line/track(name/number)between…and…(station) (station)Reason…Driver of train…(number)
Level Description
5 —can adapt the way he/she speaks to any interlocutor—can put forward an opinion—can negotiate—can persuade—can give advice — can adapt the way he/she speaks to any interlocutor — can put forward an opinion — can negotiate — can persuade — can give advice
— can adapt the way he/she speaks to any interlocutor
— can put forward an opinion
— can negotiate
— can persuade
— can give advice
4 —can cope with totally unforeseen situations—can make assumptions—can express an argued opinion — can cope with totally unforeseen situations — can make assumptions — can express an argued opinion
— can cope with totally unforeseen situations
— can make assumptions
— can express an argued opinion
3 —can cope with practical situations involving an unforeseen element—can describe—can keep a simple conversation going — can cope with practical situations involving an unforeseen element — can describe — can keep a simple conversation going
— can cope with practical situations involving an unforeseen element
— can describe
— can keep a simple conversation going
2 —can cope with simple practical situations—can ask questions—can answer questions — can cope with simple practical situations — can ask questions — can answer questions
— can cope with simple practical situations
— can ask questions
— can answer questions
1 —can talk using memorised sentences — can talk using memorised sentences
— can talk using memorised sentences
— can adapt the way he/she speaks to any interlocutor
— can put forward an opinion
— can negotiate
— can persuade
— can give advice
— can cope with totally unforeseen situations
— can make assumptions
— can express an argued opinion
— can cope with practical situations involving an unforeseen element
— can describe
— can keep a simple conversation going
— can cope with simple practical situations
— can ask questions
— can answer questions
— can talk using memorised sentences
(a) This Appendix, which must be read in conjunction with points 4.6 and 4.7 is a list of the elements that are deemed to be relevant to the task of accompanying a train on the network.
(b) The expression ‘professional qualification’, when taken within the context of this TSI, refers to those elements that are important to ensuring that operational staff are trained and able to understand and discharge the elements of the task.
(c) Rules and procedures apply to the task being performed and to the person carrying out the task. These tasks may be carried out by any authorised qualified person irrespective of any name, job title or grade used in rules or procedures or by the individual company.
(d) Any authorised qualified person must carry out all rules and procedures related to the task being performed.
(a) General principles of safety management within the railway system, relevant to the task, including interfaces with other subsystems
(b) General conditions relevant to the safety of passengers or cargo and persons on or about the railway track
(c) Conditions of health and safety at work
(d) General principles of security of the railway system
(e) Personal safety including when leaving the train on the running line
(a) Operational procedures and safety rules
(b) Control-command and signalling system
(c) Communications principles and formalised messaging procedure including use of communication equipment
(a) Passenger vehicle interior equipment
(b) Repairing minor defects within the passenger areas of rolling stock, as required by the Railway Undertaking
(a) Operational arrangements (such as the method of train despatch) at individual locations (signalling, station equipment etc.)
(b) Stations at which passengers may alight or join
(c) Local operating and emergency arrangements specific to the line(s) of route
(a) Checks before departure, including brake tests and correct closure of the doors
(b) Departure processes
(c) Communication with passengers especially in relation to circumstances involving passenger safety
(d) Degraded operations
(e) Assess the potential of a defect within the passenger areas and react according to rules and procedures
(f) Protection and warning measures as required by the rules and regulations or in assistance to the driver
(g) Train evacuation and passenger safety especially if they are required to be on or near the line
(h) Communicate with the Infrastructure Manager’s staff when assisting the driver or during an evacuation incident
(i) Report any unusual occurrences concerning the operation of the train, the condition of the rolling stock and the safety of passengers. If required these reports must be made in writing, in the language chosen by the Railway Undertaking.
(a) The expression ‘professional qualification’, when taken within the context of this TSI, refers to those elements that are important to ensuring that operational staff are trained and able to understand and discharge the elements of the task.
(b) Rules and procedures apply to the task being performed and to the person carrying out the task. These tasks may be carried out by any authorised qualified person irrespective of any name, job title or grade used in rules or procedures or by the individual company.
(c) Any authorised qualified person must follow all rules and procedures related to the task being performed.
(a) General principles of safety management within the railway system, relevant to the task, including interfaces with other subsystems
(b) General conditions relevant to the safety of passengers and/or cargo including the carriage of dangerous goods and exceptional loads
(c) Conditions of health and safety at work
(d) General principles of security of the railway system
(e) Personal safety when on or in the vicinity of rail lines
(f) Communications principles and formalised messaging procedure including use of communication equipment
(a) Working of trains in normal, degraded and emergency conditions
(b) Operational procedures at individual locations (signalling, station/depot/yard equipment) and safety rules
(c) Local operating arrangements
(a) Purpose and use of wagon and vehicle equipment
(b) Identification of and arranging for technical inspections
(a) Application of train composition rules, train braking rules, train loading rules etc. to ensure the train is in running order
(b) Understanding of marking and labels on vehicles
(c) Process for determining and making train data available
(d) Communication with train crew
(e) Communication with staff responsible for controlling the movement of trains
(f) Degraded operations especially as it affects the preparation of trains
(g) Protection and warning measures as required by the rules and regulations or local arrangements at the location in question
(h) Actions to be taken in respect to incidents involving the carriage of dangerous goods (where relevant)
23. TEN
80 D-RFC
7369 553-4
Zcs
31. TEN
80 D-DB
0691 235-2
Tanoos
33. TEN
84 NL-ACTS
4796 100-8
Slpss
D and NL stand for the registering Member State as set out in NVR-decision 2007/756/EC, Appendix 6, part 4.
RFC, DB and ACTS stand for the keeper marking as set out in NVR-decision 2007/756/EC, Appendix 6, part 1.
0187 3320 644-7
TEN F-SNCF Ks
0187 3320 644-7
TEN F-SNCF Ks-xy
F-SNCF 61 8720 – 72 021– 7
B10tu
(a) complies with all relevant TSIs which are in force at the moment of placing in service and has been authorised to be placed in service according to Article 22(1) of Directive 2008/57/EC, and
(b) is provided with an authorisation valid in all Member States in accordance with Article 23(1) of Directive 2008/57/EC.
(1) for trains able to run at a maximum speed higher than 200 km/h, in deceleration profile and equivalent response time on level track,;
(2) for train sets or for fixed train compositions, unable to run at a maximum speed higher than 200 km/h, in deceleration (as above in 1) or in brake weight percentage;The IM shall also deliver the requirements in the alternate unit (brake weight percentage or deceleration), if so requested by the RU;
(3) for other trains (variable compositions of trains unable to run at a maximum speed higher than 200 km/h): in brake weight percentage.
Term Definition
Accident As defined in Article 3 of Directive 2004/49/EC.
Authorising the movement of trains The operation of equipment in signalling centres, electric traction current supply control rooms and traffic control centres that permits train movement. This does not include those staff employed by a Railway Undertaking who are responsible for management of resources such as train crew or rolling stock.
Competence The qualification and experience necessary to safely and reliably undertake the task being performed. Experience can be gained as part of the training process.
Dangerous goods As covered by Directive 2008/68/EC
Degraded operation Operation resulting from an unplanned event that prevents the normal delivery of train services.
Despatch (= dispatch) See Train despatch
Driver As defined in Article 3 of Directive 2007/59/EC.
Exceptional loads A load carried on a rail vehicle, for example a container, swap body or other traffic where the rail vehicle size and/or axle loading requires special authority for the movement and/or the application of special conditions of travel for all or part of the journey.
Health and Safety Conditions In the context of this TSI, this refers only to the medical and psychological qualifications required to operate the relevant elements of the subsystem.
Hot axle box An axle box and bearing that has exceeded its maximum designed operating temperature.
Incident As defined in Article 3 of Directive 2004/49/EC.
Length of train Total length of all vehicles over buffers including locomotive(s)
Operating Language The language or languages used in daily operation an Infrastructure Manager and published in his Network Statement, for the communication of operational or safety related messages between the staff of the Infrastructure Manager and the Railway Undertaking.
Passenger Person (other than an employee with specific duties on the train) travelling by train or on railway property before or after a train journey.
Performance monitoring The systematic observation and recording of the performance of the train service and the infrastructure for the purpose of bringing about improvements in the performance of both.
Qualification The physical and psychological suitability for the task together with the required knowledge.
Real time The ability to exchange or process information on specified events (such as arrival at a station, passing a station or departure from a station) on the train’s journey as they occur.
Reporting point A point on the trains schedule where reporting of the arrival, departure or passing time is required.
Route The particular section or sections of line
Safety-critical work Work performed by staff when they control or affect the movement of a vehicle, which could affect the health, and safety of persons.
Staff Employees working for a Railway Undertaking or an Infrastructure Manager, or their contractors, undertaking tasks as specified in this TSI.
Stopping point A location identified in the schedule of a train where the train is planned to stop, usually to carry out a specific activity such as allowing passengers to join and leave the train.
Timetable Document or system that gives details of a train(s) schedule over a particular route.
Timing point A location identified in the schedule of a train where a specific time is identified. This time may be an arrival time, departure time or in the case of a train not scheduled to stop at that location the passing time.
Traction unit A powered vehicle able to move itself and other vehicles to which it may be coupled.
Train A train is defined as (a) traction unit(s) with or without coupled railway vehicles with train data available operating between two or more defined points.
Train despatch The indication to the person driving the train that all station or depot activities are completed and that, as far as the staff responsible are concerned, movement authority has been granted for the train.
Train crew Members of the on-board staff of a train, who are certified as competent and appointed by a Railway Undertaking to carry out specific, designated safety related tasks on the train, for example the driver or the guard.
Train preparation Ensuring that a train is in a fit condition to enter service, that the train equipment is correctly deployed and the formation of the train matches the train’s designated pathway. Train preparation also includes technical inspections carried out prior to the train entering service.
Abbreviation Explanation
AC Alternating current
CCS Control-Command and Signalling
CEN European Committee for Standardisation (Comité Européen de Normalisation)
COTIF Convention Concerning International Carriage by Rail (Convention relative aux Transports Internationaux Ferroviaires)
CR Conventional Rail
dB Decibels
DC Direct Current
DMI Driver Machine Interface
EC European Community
ECG Electro Cardiogram
EIRENE European Integrated Railway Radio Enhanced Network
EN euro-norm
ENE Energy
ERA European Rail Agency
ERTMS European Rail Traffic Management System
ETCS European Train Control System
EU European Union
FRS Functional Requirement Specification
GSM-R Global System for Mobile Communications — Rail
HABD Hot Axle Box Detector
Hz Hertz
IM Infrastructure Manager
INF Infrastructure
OPE Operation and Traffic Management
OSJD Organisation for Cooperation of Railways
PPV/PPW Russian abbreviation for Prawila Polzowaniia Wagonami w mejdunarodnom soobqenii = Rules for use of railway vehicles in international traffic
RST Rolling Stock
RU Railway Undertaking
SMS Safety Management System
SPAD Signal Passed at Danger
SRS System Requirement Specification
TAF Telematic Applications for Freight
TEN Trans-European Network
TSI Technical Specification for Interoperability
UIC International Union of Railways (Union Internationale des Chemins de fer)
VKM Vehicle Keeper Marking
(1) Chapter 1 is amended as follows:(a)The description of the data field 1. ‘European Vehicle Number’ is replaced by the following:‘numeric identification code as defined in Appendix 6’;(b)Footnote (1) is replaced by the following:‘(1)not used’.(c)The description of the data field 2.1 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.(d)The description of the data field 11 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’. (a) The description of the data field 1. ‘European Vehicle Number’ is replaced by the following:‘numeric identification code as defined in Appendix 6’; (b) Footnote (1) is replaced by the following:‘(1)not used’. ‘(1) not used’. (c) The description of the data field 2.1 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’. (d) The description of the data field 11 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.
(a) The description of the data field 1. ‘European Vehicle Number’ is replaced by the following:‘numeric identification code as defined in Appendix 6’;
(b) Footnote (1) is replaced by the following:‘(1)not used’. ‘(1) not used’.
‘(1) not used’.
(c) The description of the data field 2.1 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.
(d) The description of the data field 11 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.
(a) The description of the data field 1. ‘European Vehicle Number’ is replaced by the following:‘numeric identification code as defined in Appendix 6’;
(b) Footnote (1) is replaced by the following:‘(1)not used’. ‘(1) not used’.
‘(1) not used’.
‘(1) not used’.
(c) The description of the data field 2.1 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.
(d) The description of the data field 11 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.
(2) In Chapter 2.1, Links with other registers, the explanation regarding VKMR is replaced by the following:‘VKMR: this register is managed by ERA and OTIF in cooperation (ERA for the EU and OTIF for all non-EU OTIF Member States). The keeper is recorded in the NVR. Appendix 6 specifies other global central registers (such as vehicle type codes, interoperability codes, country codes, etc.) to be managed by a ‘central body’ resulting from cooperation between ERA and OTIF’.
(3) The following Appendix is added:‘Appendix 6PART ‘0’—VEHICLE IDENTIFICATIONGeneral remarksThis appendix describes the European Vehicle Number and linked marking applied in a visible manner on the vehicle to identify it uniquely and in a permanent manner during operation. It does not describe other numbers or markings eventually engraved or fixed in a permanent manner on the chassis or the main components of the vehicle during its construction.European Vehicle number and linked abbreviationsEach railway vehicle receives a number consisting of 12 figures (called European Vehicle Number (EVN)) with the following structure:Rolling stock groupInteroperability capability and vehicle type[2 figures]Country in which the vehicle is registered[2 figures]Technical characteristics[4 figures]Serial number[3 figures]Check digit[1 figure]Wagons00 to 0910 to 1920 to 2930 to 3940 to 4980 to 89[details in part 6]01 to 99[details in part 4]0000 to 9999[details in part 9]000 to 9990 to 9[details in part 3]Hauled passenger vehicles50 to 5960 to 6970 to 79[details in part 7]0000 to 9999[details in part 10]000 to 999Tractive rolling stock and units in a train set in fixed or pre-defined formation90 to 99[details in part 8]0000000 to 8999999[the meaning of these figures is defined by the Member States, eventually by bilateral or multilateral agreement]Special vehicles9000 to 9999[details in part 11]000 to 999In a given country, the 7 digits of technical characteristics and serial number are sufficient to identify uniquely a vehicle inside the groups of hauled passenger vehicles and special vehicles(1).Alphabetical markings complete the number:(a)abbreviation of the country in which the vehicle is registered(details in part 4);(b)Vehicle Keeper Marking(details in part 1);(c)abbreviations of the technical characteristics (details in part 12 for the wagons, part 13 for the hauled passenger vehicles).The European Vehicle Number shall be changed when it does not reflect the interoperability capability or technical characteristics according to this Appendix due to technical modifications of the vehicle. Such technical modifications may require a new placing in service according to Articles 20 to 25 of Directive 2008/57/EC.PART 1 —   VEHICLE KEEPER MARKING1.Definition of the Vehicle Keeper Marking (VKM)A Vehicle Keeper Marking (VKM) is an alphabetic code, consisting of 2 to 5 letters(2). A VKM is inscribed on each rail vehicle, near the European Vehicle Number. The VKM identifies the Vehicle Keeper as registered in a National Vehicle Register.A VKM is unique and valid in all countries covered by this TSI and all countries that enter into an agreement that involves the application of the system of vehicle numbering and VKM as described in this TSI.2.Format of the Vehicle Keeper MarkingThe VKM is representation of the full name or abbreviation of the vehicle keeper, if possible in a recognisable manner. All 26 letters of the Latina alphabet may be used. The letters in the VKM are written in capitals. Letters that do not stand for first letters of words in the keeper’s name may be written in lower case. For checking uniqueness, the letters written in lower case will be taken as written in capitals.Letters may contain diacritical signs(3). Diacritical signs used by these letters are ignored for checking uniqueness.For vehicles of keepers that reside in a country that does not use the Latin alphabet, a translation of the VKM in its own alphabet may be applied behind the VKM separated from it by a slash-sign (‘/’). This translated VKM is disregarded for data-processing purposes.3.Provisions about allocation of Vehicle Keeper MarkingsA vehicle keeper can be issued more than one VKM, in case:—the vehicle keeper has a formal name in more than one language;—a vehicle keeper has good cause to distinguish between separate vehicle fleets within his organisation.A single VKM can be issued for a group of companies:—that belong to single corporate structure (e.g. holding structure);—that belong to a single corporate structure that has appointed and mandated one organisation within this structure to handle all issues on behalf of all others;—that has mandated a separate, single legal entity for handling all issues on their behalf, in which event the legal entity is the keeper.4.Register of Vehicle Keeper Markings and procedure for allocationThe register of VKM is public and updated on a real time basis.An application for a VKM is filed with the applicant’s competent national authority and forwarded to the ERA. A VKM can be used only after publication by the ERA.The holder of a VKM must inform the competent national authority when he ends the use of a VKM, and the competent national authority will forward the information to the ERA. A VKM will then be revoked once the keeper has proved that the marking has been changed on all vehicles concerned. It will not be reissued for 10 years, unless it is reissued to the original holder or at his request to another holder.A VKM can be transferred to another holder, which is the legal successor to the original holder. A VKM stays valid when the VKM’s holder changes his name to a name that does not bear resemblance to the VKM.In case of a change of keeper which entails a change of VKM, the vehicles concerned must be marked with the new VKM within three months from the date of registration of the change of keeper in the National Vehicle Register. In case of inconsistency between the VKM marked on the vehicle and the data registered in the NVR, the NVR-registration supersedes.PART 2Not usedPART 3 —   RULES FOR THE DETERMINATION OF THE CHECK-DIGIT (DIGIT 12)The check-digit is determined in the following manner:—the digits in the even positions of the basic number (counting from the right) are taken at their own decimal value;—the digits in the odd positions of the basic number (counting from the right) are multiplied by 2;—the sum formed by the digits in even position and by all the digits which constitute the partial products obtained from the odd positions is then established;—the unit’s digit of this sum is retained;—the complement required to bring the unit’s digit to 10 forms the check-digit; should this units digit be nought, then the check-digit will also be nought.Examples:1 —Let the basic number be33844796100Multiplication factor212121212126316487186200Sum: 6 + 3 + 1 + 6 + 4 + 8 + 7 + 1 + 8 + 6 + 2 + 0 + 0 = 52The unit’s digit of this sum is 2.The check-digit number will therefore be 8 and the basic number thus becomes the registration number 33 84 4796 100 – 8.2 —Let the basic number be31513320198Multiplication factor212121212126110163402916Sum: 6 + 1 + 1 + 0 + 1 + 6 + 3 + 4 + 0 + 2 + 9 + 1 + 6 = 40The unit’s digit of this sum is 0.The check-digit number will therefore be 0 and the basic number thus becomes the registration number 31 51 3320 198 – 0.PART 4 —   CODING OF THE COUNTRIES IN WHICH THE VEHICLES ARE REGISTERED (DIGITS 3-4 AND ABBREVIATION)The Information relating to third countries is given for information purposes only.CountriesAlphabetical country code(4)Numerical country codeAlbaniaAL41AlgeriaDZ92ArmeniaAM58AustriaA81AzerbaijanAZ57BelarusBY21BelgiumB88Bosnia-HerzegovinaBIH49BulgariaBG52ChinaRC33CroatiaHR78CubaCU(4)40CyprusCYCzech RepublicCZ54DenmarkDK86EgyptET90EstoniaEST26FinlandFIN10FranceF87GeorgiaGE28GermanyD80GreeceGR73HungaryH55IranIR96IraqIRQ(4)99IrelandIRL60IsraelIL95ItalyI83JapanJ42KazakhstanKZ27KyrgyzstanKS59LatviaLV25LebanonRL98LiechtensteinFLLithuaniaLT24LuxembourgL82MacedoniaMK65MaltaMMoldovaMD(4)23MonacoMCMongoliaMGL31MontenegroMNE62MoroccoMA93NetherlandsNL84North KoreaPRK(4)30NorwayN76PolandPL51PortugalP94RomaniaRO53RussiaRUS20SerbiaSRB72SlovakiaSK56SloveniaSLO79South KoreaROK61SpainE71SwedenSE74SwitzerlandCH85SyriaSYR97TajikistanTJ66TunisiaTN91TurkeyTR75TurkmenistanTM67UkraineUA22United KingdomGB70UzbekistanUZ29VietnamVN(4)32PART 5Not usedPART 6 —   INTEROPERABILITY CODES USED FOR WAGONS (DIGITS 1-2)2nd digit1st digit01234567892nd digit1st digitTrack Gaugefixed or variablefixedvariablefixedvariablefixedvariablefixedvariablefixed or variableTrack GaugeWagons conform to TSI WAG(1)including section 7.1.2 and all conditions set out in Appendix C0with axlesNot to be usedwagonsnot to be used(3)PPV/PPW wagons(variable gauge)with axles01with bogieswith bogies12with axleswagonsPPV/PPW wagons(fixed gauge)with axles23with bogieswith bogies3Other wagons4with axles(2)maintenance related wagonsOther wagonsWagons with special numbering for technical characteristics not placed in service inside EUwith axles(2)48with bogies(2)with bogies(2)81st digit2nd digit01234567891st digit2nd digitPART 7 —   INTERNATIONAL TRAFFIC ABILITY CODES USED FOR HAULED PASSENGER VEHICLES (DIGITS 1-2)Domestic trafficTEN(4)and/or COTIF(5)and/or PPV/PPWDomestic traffic or international traffic by special agreementTEN(4)and/or COTIF(5)PPV/PPW2nd digit1st digit01234567895Vehicles for domestic trafficFixed-gauge non-air-conditioned vehicles (including car-carrying wagons)Gauge-adjustable (1435/1520) non-air-conditioned vehiclesNot to be usedGauge-adjustable (1435/1668) non-air-conditioned vehiclesHistorical vehiclesNot to be used(6)Fixed-gauge vehiclesGauge-adjustable (1435/1520) vehicles with change of bogiesGauge-adjustable (1435/1520) vehicles with gauge-adjustable axles6Service vehiclesFixed-gauge air-conditioned vehiclesGauge-adjustable (1435/1520) air-conditioned vehiclesService vehiclesGauge-adjustable (1435/1668) air-conditioned vehiclesCar-carrying wagonsNot to be used(6)7Air-conditioned and pressure-tight vehiclesNot to be usedNot to be usedPressure-tight fixed-gauge air-conditioned vehiclesNot to be usedOther vehiclesNot to be usedNot to be usedNot to be usedNot to be usedPART 8 —   TYPES OF TRACTIVE ROLLING STOCK AND UNITS IN A TRAIN SET IN FIXED OR PRE-DEFINED FORMATION (DIGITS 1-2)The first digit is ‘9’.If the second digit describes the type of tractive stock, following coding is mandatory:CodeGeneral vehicle type0Miscellaneous1Electric locomotive2Diesel locomotive3Electric multiple-unit set (high speed) [power car or trailer]4Electric multiple-unit set (except high speed) [power car or trailer]5Diesel multiple-unit set [power car or trailer]6Specialised trailer,7Electric shunting engine8Diesel shunting engine9Special vehiclePART 9 —   STANDARD NUMERICAL MARKING OF WAGONS (DIGITS 5 TO 8)Part 9 indicates the numerical marking associated to the main technical characteristics of the wagon and it is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA.PART 10 —   CODES FOR THE TECHNICAL CHARACTERISTICS OF THE HAULED PASSENGER STOCK (DIGITS 5-6)Part 10 is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA.PART 11 —   CODES FOR THE TECHNICAL CHARACTERISTICS OF THE SPECIAL VEHICLES (DIGIT 6 TO 8)Part 11 is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA.PART 12 —   LETTER MARKING FOR WAGONS EXCLUDING ARTICULATED AND MULTIPLE WAGONSPart 12 is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA.PART 13 —   LETTER MARKING FOR HAULED PASSENGER STOCKPart 13 is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA. Rolling stock group Interoperability capability and vehicle type[2 figures] Country in which the vehicle is registered[2 figures] Technical characteristics[4 figures] Serial number[3 figures] Check digit[1 figure] Wagons 00 to 0910 to 1920 to 2930 to 3940 to 4980 to 89[details in part 6] 01 to 99[details in part 4] 0000 to 9999[details in part 9] 000 to 999 0 to 9[details in part 3] Hauled passenger vehicles 50 to 5960 to 6970 to 79[details in part 7] 0000 to 9999[details in part 10] 000 to 999 Tractive rolling stock and units in a train set in fixed or pre-defined formation 90 to 99[details in part 8] 0000000 to 8999999[the meaning of these figures is defined by the Member States, eventually by bilateral or multilateral agreement] Special vehicles 9000 to 9999[details in part 11] 000 to 999 (a) abbreviation of the country in which the vehicle is registered(details in part 4); (b) Vehicle Keeper Marking(details in part 1); (c) abbreviations of the technical characteristics (details in part 12 for the wagons, part 13 for the hauled passenger vehicles). — the vehicle keeper has a formal name in more than one language; — a vehicle keeper has good cause to distinguish between separate vehicle fleets within his organisation. — that belong to single corporate structure (e.g. holding structure); — that belong to a single corporate structure that has appointed and mandated one organisation within this structure to handle all issues on behalf of all others; — that has mandated a separate, single legal entity for handling all issues on their behalf, in which event the legal entity is the keeper. — the digits in the even positions of the basic number (counting from the right) are taken at their own decimal value; — the digits in the odd positions of the basic number (counting from the right) are multiplied by 2; — the sum formed by the digits in even position and by all the digits which constitute the partial products obtained from the odd positions is then established; — the unit’s digit of this sum is retained; — the complement required to bring the unit’s digit to 10 forms the check-digit; should this units digit be nought, then the check-digit will also be nought. 1 — Let the basic number be33844796100Multiplication factor212121212126316487186200Sum: 6 + 3 + 1 + 6 + 4 + 8 + 7 + 1 + 8 + 6 + 2 + 0 + 0 = 52The unit’s digit of this sum is 2.The check-digit number will therefore be 8 and the basic number thus becomes the registration number 33 84 4796 100 – 8. Let the basic number be 3 3 8 4 4 7 9 6 1 0 0 Multiplication factor 2 1 2 1 2 1 2 1 2 1 2 6 3 16 4 8 7 18 6 2 0 0 2 — Let the basic number be31513320198Multiplication factor212121212126110163402916Sum: 6 + 1 + 1 + 0 + 1 + 6 + 3 + 4 + 0 + 2 + 9 + 1 + 6 = 40The unit’s digit of this sum is 0.The check-digit number will therefore be 0 and the basic number thus becomes the registration number 31 51 3320 198 – 0. Let the basic number be 3 1 5 1 3 3 2 0 1 9 8 Multiplication factor 2 1 2 1 2 1 2 1 2 1 2 6 1 10 1 6 3 4 0 2 9 16 Countries Alphabetical country code(4) Numerical country code Albania AL 41 Algeria DZ 92 Armenia AM 58 Austria A 81 Azerbaijan AZ 57 Belarus BY 21 Belgium B 88 Bosnia-Herzegovina BIH 49 Bulgaria BG 52 China RC 33 Croatia HR 78 Cuba CU(4) 40 Cyprus CY Czech Republic CZ 54 Denmark DK 86 Egypt ET 90 Estonia EST 26 Finland FIN 10 France F 87 Georgia GE 28 Germany D 80 Greece GR 73 Hungary H 55 Iran IR 96 Iraq IRQ(4) 99 Ireland IRL 60 Israel IL 95 Italy I 83 Japan J 42 Kazakhstan KZ 27 Kyrgyzstan KS 59 Latvia LV 25 Lebanon RL 98 Liechtenstein FL Lithuania LT 24 Luxembourg L 82 Macedonia MK 65 Malta M Moldova MD(4) 23 Monaco MC Mongolia MGL 31 Montenegro MNE 62 Morocco MA 93 Netherlands NL 84 North Korea PRK(4) 30 Norway N 76 Poland PL 51 Portugal P 94 Romania RO 53 Russia RUS 20 Serbia SRB 72 Slovakia SK 56 Slovenia SLO 79 South Korea ROK 61 Spain E 71 Sweden SE 74 Switzerland CH 85 Syria SYR 97 Tajikistan TJ 66 Tunisia TN 91 Turkey TR 75 Turkmenistan TM 67 Ukraine UA 22 United Kingdom GB 70 Uzbekistan UZ 29 Vietnam VN(4) 32 2nd digit1st digit 0 1 2 3 4 5 6 7 8 9 2nd digit1st digit Track Gauge fixed or variable fixed variable fixed variable fixed variable fixed variable fixed or variable Track Gauge Wagons conform to TSI WAG(1)including section 7.1.2 and all conditions set out in Appendix C 0 with axles Not to be used wagons not to be used(3) PPV/PPW wagons(variable gauge) with axles 0 1 with bogies with bogies 1 2 with axles wagons PPV/PPW wagons(fixed gauge) with axles 2 3 with bogies with bogies 3 Other wagons 4 with axles(2) maintenance related wagons Other wagons Wagons with special numbering for technical characteristics not placed in service inside EU with axles(2) 4 8 with bogies(2) with bogies(2) 8 1st digit2nd digit 0 1 2 3 4 5 6 7 8 9 1st digit2nd digit Domestic traffic TEN(4)and/or COTIF(5)and/or PPV/PPW Domestic traffic or international traffic by special agreement TEN(4)and/or COTIF(5) PPV/PPW 2nd digit1st digit 0 1 2 3 4 5 6 7 8 9 5 Vehicles for domestic traffic Fixed-gauge non-air-conditioned vehicles (including car-carrying wagons) Gauge-adjustable (1435/1520) non-air-conditioned vehicles Not to be used Gauge-adjustable (1435/1668) non-air-conditioned vehicles Historical vehicles Not to be used(6) Fixed-gauge vehicles Gauge-adjustable (1435/1520) vehicles with change of bogies Gauge-adjustable (1435/1520) vehicles with gauge-adjustable axles 6 Service vehicles Fixed-gauge air-conditioned vehicles Gauge-adjustable (1435/1520) air-conditioned vehicles Service vehicles Gauge-adjustable (1435/1668) air-conditioned vehicles Car-carrying wagons Not to be used(6) 7 Air-conditioned and pressure-tight vehicles Not to be used Not to be used Pressure-tight fixed-gauge air-conditioned vehicles Not to be used Other vehicles Not to be used Not to be used Not to be used Not to be used Code General vehicle type 0 Miscellaneous 1 Electric locomotive 2 Diesel locomotive 3 Electric multiple-unit set (high speed) [power car or trailer] 4 Electric multiple-unit set (except high speed) [power car or trailer] 5 Diesel multiple-unit set [power car or trailer] 6 Specialised trailer, 7 Electric shunting engine 8 Diesel shunting engine 9 Special vehicle
Rolling stock group Interoperability capability and vehicle type[2 figures] Country in which the vehicle is registered[2 figures] Technical characteristics[4 figures] Serial number[3 figures] Check digit[1 figure]
Wagons 00 to 0910 to 1920 to 2930 to 3940 to 4980 to 89[details in part 6] 01 to 99[details in part 4] 0000 to 9999[details in part 9] 000 to 999 0 to 9[details in part 3]
Hauled passenger vehicles 50 to 5960 to 6970 to 79[details in part 7] 0000 to 9999[details in part 10] 000 to 999
Tractive rolling stock and units in a train set in fixed or pre-defined formation 90 to 99[details in part 8] 0000000 to 8999999[the meaning of these figures is defined by the Member States, eventually by bilateral or multilateral agreement]
Special vehicles 9000 to 9999[details in part 11] 000 to 999
(a) abbreviation of the country in which the vehicle is registered(details in part 4);
(b) Vehicle Keeper Marking(details in part 1);
(c) abbreviations of the technical characteristics (details in part 12 for the wagons, part 13 for the hauled passenger vehicles).
— the vehicle keeper has a formal name in more than one language;
— a vehicle keeper has good cause to distinguish between separate vehicle fleets within his organisation.
— that belong to single corporate structure (e.g. holding structure);
— that belong to a single corporate structure that has appointed and mandated one organisation within this structure to handle all issues on behalf of all others;
— that has mandated a separate, single legal entity for handling all issues on their behalf, in which event the legal entity is the keeper.
— the digits in the even positions of the basic number (counting from the right) are taken at their own decimal value;
— the digits in the odd positions of the basic number (counting from the right) are multiplied by 2;
— the sum formed by the digits in even position and by all the digits which constitute the partial products obtained from the odd positions is then established;
— the unit’s digit of this sum is retained;
— the complement required to bring the unit’s digit to 10 forms the check-digit; should this units digit be nought, then the check-digit will also be nought.
1 — Let the basic number be33844796100Multiplication factor212121212126316487186200Sum: 6 + 3 + 1 + 6 + 4 + 8 + 7 + 1 + 8 + 6 + 2 + 0 + 0 = 52The unit’s digit of this sum is 2.The check-digit number will therefore be 8 and the basic number thus becomes the registration number 33 84 4796 100 – 8. Let the basic number be 3 3 8 4 4 7 9 6 1 0 0 Multiplication factor 2 1 2 1 2 1 2 1 2 1 2 6 3 16 4 8 7 18 6 2 0 0
Let the basic number be 3 3 8 4 4 7 9 6 1 0 0
Multiplication factor 2 1 2 1 2 1 2 1 2 1 2
6 3 16 4 8 7 18 6 2 0 0
2 — Let the basic number be31513320198Multiplication factor212121212126110163402916Sum: 6 + 1 + 1 + 0 + 1 + 6 + 3 + 4 + 0 + 2 + 9 + 1 + 6 = 40The unit’s digit of this sum is 0.The check-digit number will therefore be 0 and the basic number thus becomes the registration number 31 51 3320 198 – 0. Let the basic number be 3 1 5 1 3 3 2 0 1 9 8 Multiplication factor 2 1 2 1 2 1 2 1 2 1 2 6 1 10 1 6 3 4 0 2 9 16
Let the basic number be 3 1 5 1 3 3 2 0 1 9 8
Multiplication factor 2 1 2 1 2 1 2 1 2 1 2
6 1 10 1 6 3 4 0 2 9 16
Countries Alphabetical country code(4) Numerical country code
Albania AL 41
Algeria DZ 92
Armenia AM 58
Austria A 81
Azerbaijan AZ 57
Belarus BY 21
Belgium B 88
Bosnia-Herzegovina BIH 49
Bulgaria BG 52
China RC 33
Croatia HR 78
Cuba CU(4) 40
Cyprus CY
Czech Republic CZ 54
Denmark DK 86
Egypt ET 90
Estonia EST 26
Finland FIN 10
France F 87
Georgia GE 28
Germany D 80
Greece GR 73
Hungary H 55
Iran IR 96
Iraq IRQ(4) 99
Ireland IRL 60
Israel IL 95
Italy I 83
Japan J 42
Kazakhstan KZ 27
Kyrgyzstan KS 59
Latvia LV 25
Lebanon RL 98
Liechtenstein FL
Lithuania LT 24
Luxembourg L 82
Macedonia MK 65
Malta M
Moldova MD(4) 23
Monaco MC
Mongolia MGL 31
Montenegro MNE 62
Morocco MA 93
Netherlands NL 84
North Korea PRK(4) 30
Norway N 76
Poland PL 51
Portugal P 94
Romania RO 53
Russia RUS 20
Serbia SRB 72
Slovakia SK 56
Slovenia SLO 79
South Korea ROK 61
Spain E 71
Sweden SE 74
Switzerland CH 85
Syria SYR 97
Tajikistan TJ 66
Tunisia TN 91
Turkey TR 75
Turkmenistan TM 67
Ukraine UA 22
United Kingdom GB 70
Uzbekistan UZ 29
Vietnam VN(4) 32
2nd digit1st digit 0 1 2 3 4 5 6 7 8 9 2nd digit1st digit
Track Gauge fixed or variable fixed variable fixed variable fixed variable fixed variable fixed or variable Track Gauge
Wagons conform to TSI WAG(1)including section 7.1.2 and all conditions set out in Appendix C 0 with axles Not to be used wagons not to be used(3) PPV/PPW wagons(variable gauge) with axles 0
1 with bogies with bogies 1
2 with axles wagons PPV/PPW wagons(fixed gauge) with axles 2
3 with bogies with bogies 3
Other wagons 4 with axles(2) maintenance related wagons Other wagons Wagons with special numbering for technical characteristics not placed in service inside EU with axles(2) 4
8 with bogies(2) with bogies(2) 8
1st digit2nd digit 0 1 2 3 4 5 6 7 8 9 1st digit2nd digit
Domestic traffic TEN(4)and/or COTIF(5)and/or PPV/PPW Domestic traffic or international traffic by special agreement TEN(4)and/or COTIF(5) PPV/PPW
2nd digit1st digit 0 1 2 3 4 5 6 7 8 9
5 Vehicles for domestic traffic Fixed-gauge non-air-conditioned vehicles (including car-carrying wagons) Gauge-adjustable (1435/1520) non-air-conditioned vehicles Not to be used Gauge-adjustable (1435/1668) non-air-conditioned vehicles Historical vehicles Not to be used(6) Fixed-gauge vehicles Gauge-adjustable (1435/1520) vehicles with change of bogies Gauge-adjustable (1435/1520) vehicles with gauge-adjustable axles
6 Service vehicles Fixed-gauge air-conditioned vehicles Gauge-adjustable (1435/1520) air-conditioned vehicles Service vehicles Gauge-adjustable (1435/1668) air-conditioned vehicles Car-carrying wagons Not to be used(6)
7 Air-conditioned and pressure-tight vehicles Not to be used Not to be used Pressure-tight fixed-gauge air-conditioned vehicles Not to be used Other vehicles Not to be used Not to be used Not to be used Not to be used
Code General vehicle type
0 Miscellaneous
1 Electric locomotive
2 Diesel locomotive
3 Electric multiple-unit set (high speed) [power car or trailer]
4 Electric multiple-unit set (except high speed) [power car or trailer]
5 Diesel multiple-unit set [power car or trailer]
6 Specialised trailer,
7 Electric shunting engine
8 Diesel shunting engine
9 Special vehicle
Rolling stock group Interoperability capability and vehicle type[2 figures] Country in which the vehicle is registered[2 figures] Technical characteristics[4 figures] Serial number[3 figures] Check digit[1 figure]
Wagons 00 to 0910 to 1920 to 2930 to 3940 to 4980 to 89[details in part 6] 01 to 99[details in part 4] 0000 to 9999[details in part 9] 000 to 999 0 to 9[details in part 3]
Hauled passenger vehicles 50 to 5960 to 6970 to 79[details in part 7] 0000 to 9999[details in part 10] 000 to 999
Tractive rolling stock and units in a train set in fixed or pre-defined formation 90 to 99[details in part 8] 0000000 to 8999999[the meaning of these figures is defined by the Member States, eventually by bilateral or multilateral agreement]
Special vehicles 9000 to 9999[details in part 11] 000 to 999
(a) abbreviation of the country in which the vehicle is registered(details in part 4);
(b) Vehicle Keeper Marking(details in part 1);
(c) abbreviations of the technical characteristics (details in part 12 for the wagons, part 13 for the hauled passenger vehicles).
— the vehicle keeper has a formal name in more than one language;
— a vehicle keeper has good cause to distinguish between separate vehicle fleets within his organisation.
— that belong to single corporate structure (e.g. holding structure);
— that belong to a single corporate structure that has appointed and mandated one organisation within this structure to handle all issues on behalf of all others;
— that has mandated a separate, single legal entity for handling all issues on their behalf, in which event the legal entity is the keeper.
— the digits in the even positions of the basic number (counting from the right) are taken at their own decimal value;
— the digits in the odd positions of the basic number (counting from the right) are multiplied by 2;
— the sum formed by the digits in even position and by all the digits which constitute the partial products obtained from the odd positions is then established;
— the unit’s digit of this sum is retained;
— the complement required to bring the unit’s digit to 10 forms the check-digit; should this units digit be nought, then the check-digit will also be nought.
1 — Let the basic number be33844796100Multiplication factor212121212126316487186200Sum: 6 + 3 + 1 + 6 + 4 + 8 + 7 + 1 + 8 + 6 + 2 + 0 + 0 = 52The unit’s digit of this sum is 2.The check-digit number will therefore be 8 and the basic number thus becomes the registration number 33 84 4796 100 – 8. Let the basic number be 3 3 8 4 4 7 9 6 1 0 0 Multiplication factor 2 1 2 1 2 1 2 1 2 1 2 6 3 16 4 8 7 18 6 2 0 0
Let the basic number be 3 3 8 4 4 7 9 6 1 0 0
Multiplication factor 2 1 2 1 2 1 2 1 2 1 2
6 3 16 4 8 7 18 6 2 0 0
Let the basic number be 3 3 8 4 4 7 9 6 1 0 0
Multiplication factor 2 1 2 1 2 1 2 1 2 1 2
6 3 16 4 8 7 18 6 2 0 0
2 — Let the basic number be31513320198Multiplication factor212121212126110163402916Sum: 6 + 1 + 1 + 0 + 1 + 6 + 3 + 4 + 0 + 2 + 9 + 1 + 6 = 40The unit’s digit of this sum is 0.The check-digit number will therefore be 0 and the basic number thus becomes the registration number 31 51 3320 198 – 0. Let the basic number be 3 1 5 1 3 3 2 0 1 9 8 Multiplication factor 2 1 2 1 2 1 2 1 2 1 2 6 1 10 1 6 3 4 0 2 9 16
Let the basic number be 3 1 5 1 3 3 2 0 1 9 8
Multiplication factor 2 1 2 1 2 1 2 1 2 1 2
6 1 10 1 6 3 4 0 2 9 16
Let the basic number be 3 1 5 1 3 3 2 0 1 9 8
Multiplication factor 2 1 2 1 2 1 2 1 2 1 2
6 1 10 1 6 3 4 0 2 9 16
Countries Alphabetical country code(4) Numerical country code
Albania AL 41
Algeria DZ 92
Armenia AM 58
Austria A 81
Azerbaijan AZ 57
Belarus BY 21
Belgium B 88
Bosnia-Herzegovina BIH 49
Bulgaria BG 52
China RC 33
Croatia HR 78
Cuba CU(4) 40
Cyprus CY
Czech Republic CZ 54
Denmark DK 86
Egypt ET 90
Estonia EST 26
Finland FIN 10
France F 87
Georgia GE 28
Germany D 80
Greece GR 73
Hungary H 55
Iran IR 96
Iraq IRQ(4) 99
Ireland IRL 60
Israel IL 95
Italy I 83
Japan J 42
Kazakhstan KZ 27
Kyrgyzstan KS 59
Latvia LV 25
Lebanon RL 98
Liechtenstein FL
Lithuania LT 24
Luxembourg L 82
Macedonia MK 65
Malta M
Moldova MD(4) 23
Monaco MC
Mongolia MGL 31
Montenegro MNE 62
Morocco MA 93
Netherlands NL 84
North Korea PRK(4) 30
Norway N 76
Poland PL 51
Portugal P 94
Romania RO 53
Russia RUS 20
Serbia SRB 72
Slovakia SK 56
Slovenia SLO 79
South Korea ROK 61
Spain E 71
Sweden SE 74
Switzerland CH 85
Syria SYR 97
Tajikistan TJ 66
Tunisia TN 91
Turkey TR 75
Turkmenistan TM 67
Ukraine UA 22
United Kingdom GB 70
Uzbekistan UZ 29
Vietnam VN(4) 32
2nd digit1st digit 0 1 2 3 4 5 6 7 8 9 2nd digit1st digit
Track Gauge fixed or variable fixed variable fixed variable fixed variable fixed variable fixed or variable Track Gauge
Wagons conform to TSI WAG(1)including section 7.1.2 and all conditions set out in Appendix C 0 with axles Not to be used wagons not to be used(3) PPV/PPW wagons(variable gauge) with axles 0
1 with bogies with bogies 1
2 with axles wagons PPV/PPW wagons(fixed gauge) with axles 2
3 with bogies with bogies 3
Other wagons 4 with axles(2) maintenance related wagons Other wagons Wagons with special numbering for technical characteristics not placed in service inside EU with axles(2) 4
8 with bogies(2) with bogies(2) 8
1st digit2nd digit 0 1 2 3 4 5 6 7 8 9 1st digit2nd digit
Domestic traffic TEN(4)and/or COTIF(5)and/or PPV/PPW Domestic traffic or international traffic by special agreement TEN(4)and/or COTIF(5) PPV/PPW
2nd digit1st digit 0 1 2 3 4 5 6 7 8 9
5 Vehicles for domestic traffic Fixed-gauge non-air-conditioned vehicles (including car-carrying wagons) Gauge-adjustable (1435/1520) non-air-conditioned vehicles Not to be used Gauge-adjustable (1435/1668) non-air-conditioned vehicles Historical vehicles Not to be used(6) Fixed-gauge vehicles Gauge-adjustable (1435/1520) vehicles with change of bogies Gauge-adjustable (1435/1520) vehicles with gauge-adjustable axles
6 Service vehicles Fixed-gauge air-conditioned vehicles Gauge-adjustable (1435/1520) air-conditioned vehicles Service vehicles Gauge-adjustable (1435/1668) air-conditioned vehicles Car-carrying wagons Not to be used(6)
7 Air-conditioned and pressure-tight vehicles Not to be used Not to be used Pressure-tight fixed-gauge air-conditioned vehicles Not to be used Other vehicles Not to be used Not to be used Not to be used Not to be used
Code General vehicle type
0 Miscellaneous
1 Electric locomotive
2 Diesel locomotive
3 Electric multiple-unit set (high speed) [power car or trailer]
4 Electric multiple-unit set (except high speed) [power car or trailer]
5 Diesel multiple-unit set [power car or trailer]
6 Specialised trailer,
7 Electric shunting engine
8 Diesel shunting engine
9 Special vehicle
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Directive 2008/57/EC of the European Parliament and of the Council of 17 June 2008 on the interoperability of the rail system within the Community(1), and in particular Article 6(1) thereof,
(1) Article 12 of Regulation (EC) No 881/2004 of the European Parliament and of the Council of 29 April 2004 establishing a European Railway Agency (Agency Regulation)(2)requires the European Railway Agency (the Agency) to ensure that the technical specifications for interoperability (TSIs) are adapted to technical progress, market trends and social requirements and to propose to the Commission the amendments to the TSIs which it considers necessary.
(2) By Decision C(2010) 2576 of 29 April 2010, the Commission gave the Agency a mandate to develop and review the technical specifications for interoperability with a view to extending their scope to the whole rail system in the Union. Under the terms of that mandate, the Agency was asked to merge and extend the scope of the high-speed TSI and the conventional rail TSI relating to the ‘Traffic Operation and Management’ subsystem. These TSIs were adopted respectively by Commission Decision 2008/231/EC(3), and Commission Decision 2011/314/EU(4).
(3) On 5 September 2011, the Agency issued a recommendation on the merging of the TSI on operation and traffic management for conventional rail and the TSI on operation and traffic management for high-speed rail, the extension of the geographical scope of these TSIs and the transfer of details of the European vehicle number (EVN) to Commission Decision 2007/756/EC(5).
(4) Implementation of the TSI set out in Annex I, and conformity with the relevant points of that TSI, should be determined in accordance with an implementation plan that each Member State is required to update for the lines for which it is responsible.
(5) Rail traffic currently operates under existing national, bilateral, multinational or international agreements. It is important that those agreements do not hinder current and future progress towards interoperability. Therefore a procedure of notification of these agreements by Member States should set up.
(6) Railway vehicles are registered by the bodies that keep the national vehicle registers pursuant to Decision 2007/756/EC, based on Article 33 of Directive 2008/57/EC.
(7) The format of the European vehicle number and the requirement to have it painted on the vehicle are both necessary for identifying the vehicle and should therefore remain in the TSI on operation and traffic management.
(8) To make it easier to understand the national vehicle register and the vehicle registration processes, it is appropriate to transfer the details of the technical codes that are part of the European vehicle number to Decision 2007/756/EC. Decision 2007/756/EC should therefore be amended accordingly.
(9) Via the Committee established in accordance with Article 29 of Directive 2008/57/EC, the Commission must inform the Member States of changes in the lists of codes published by the Agency.
(10) Directive 2008/57/EC defines the ‘operation and traffic management’ subsystem as functional. Consequently, the TSI on operation and traffic management is not assessed when authorising a vehicle to be brought into service but when assessing the safety management systems of railway undertakings and infrastructure managers.
(11) For the sake of clarity and simplicity, it is appropriate not to amend the transitional provisions set out in Articles 3, 5 and 7 of Decision 2011/314/EU.
(12) Decisions 2008/231/EC and 2011/314/EU should be repealed.
(13) The measures provided for in this Decision are in conformity with the opinion of the Committee established in accordance with Article 29(1) of Directive 2008/57/EC,
HAS ADOPTED THIS DECISION:

Article 1
1. The technical specification for interoperability (TSI) relating to the ‘operation and traffic management’ subsystem of the rail system in the Union, as set out in Annex I, is hereby adopted.
2. The TSI set out in Annex I to this Decision shall apply to the operation and traffic management subsystem as described in point 2.5 of Annex II to Directive 2008/57/EC.

Article 2
Member States shall notify the following types of agreement to the Commission by 30 June 2014 at the latest, provided they have not already been notified under Commission Decision 2006/920/EC(6), Decision 2008/231/EC or Decision 2011/314/EU:
(a)
national agreements between the Member States and railway undertakings or infrastructure managers, agreed on either a permanent or a temporary basis and required by the very specific or local nature of the intended transport service;
(b)
bilateral or multilateral agreements between railway undertakings, infrastructure managers or safety authorities which deliver significant levels of local or regional interoperability;
(c)
international agreements between one or more Member States and at least one third country, or between railway undertakings or infrastructure managers of Member States and at least one railway undertaking or infrastructure manager of a third country, which deliver significant levels of local or regional interoperability.

Article 3
Each Member State, acting in accordance with Chapter 7 of Annex I to this Decision, shall update the national implementation plans for the TSI, established in accordance with Article 4 of Decision 2006/920/EC, Article 4 of Decision 2008/231/EC and Article 5 of Decision 2011/314/EU.
Each Member State shall forward the updated implementation plan to the other Member States and the Commission by 31 December 2014 at the latest.

Article 4
Decisions 2008/231/EC and 2011/314/EU are hereby repealed with effect from 1 January 2014.

Article 5
Decision 2007/756/EC is hereby amended as follows:
(a)
The following Article is inserted after Article 1:
Appendix 6 of the Annex of this Decision shall apply from 1 January 2014.’
(b)
The Annex is amended in accordance with Annex II to this Decision.

Article 6
1. The Agency shall publish on its website the lists of codes referred in parts 9, 10, 11, 12 and 13 of Appendix 6 of the Annex to Decision 2007/756/EC.
2. The Agency shall keep the lists of codes referred to in paragraph 1 up to date and shall inform the Commission of any changes to those codes. The Commission shall inform the Member States of the evolution of these lists through the Committee established in accordance with Article 29 of Directive 2008/57/EC.

Article 7
This Decision shall apply from 1 January 2014.

Article 8
This Decision is addressed to the Member States.

THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Directive 2008/57/EC of the European Parliament and of the Council of 17 June 2008 on the interoperability of the rail system within the Community(1), and in particular Article 6(1) thereof,
(1) Article 12 of Regulation (EC) No 881/2004 of the European Parliament and of the Council of 29 April 2004 establishing a European Railway Agency (Agency Regulation)(2)requires the European Railway Agency (the Agency) to ensure that the technical specifications for interoperability (TSIs) are adapted to technical progress, market trends and social requirements and to propose to the Commission the amendments to the TSIs which it considers necessary.
(2) By Decision C(2010) 2576 of 29 April 2010, the Commission gave the Agency a mandate to develop and review the technical specifications for interoperability with a view to extending their scope to the whole rail system in the Union. Under the terms of that mandate, the Agency was asked to merge and extend the scope of the high-speed TSI and the conventional rail TSI relating to the ‘Traffic Operation and Management’ subsystem. These TSIs were adopted respectively by Commission Decision 2008/231/EC(3), and Commission Decision 2011/314/EU(4).
(3) On 5 September 2011, the Agency issued a recommendation on the merging of the TSI on operation and traffic management for conventional rail and the TSI on operation and traffic management for high-speed rail, the extension of the geographical scope of these TSIs and the transfer of details of the European vehicle number (EVN) to Commission Decision 2007/756/EC(5).
(4) Implementation of the TSI set out in Annex I, and conformity with the relevant points of that TSI, should be determined in accordance with an implementation plan that each Member State is required to update for the lines for which it is responsible.
(5) Rail traffic currently operates under existing national, bilateral, multinational or international agreements. It is important that those agreements do not hinder current and future progress towards interoperability. Therefore a procedure of notification of these agreements by Member States should set up.
(6) Railway vehicles are registered by the bodies that keep the national vehicle registers pursuant to Decision 2007/756/EC, based on Article 33 of Directive 2008/57/EC.
(7) The format of the European vehicle number and the requirement to have it painted on the vehicle are both necessary for identifying the vehicle and should therefore remain in the TSI on operation and traffic management.
(8) To make it easier to understand the national vehicle register and the vehicle registration processes, it is appropriate to transfer the details of the technical codes that are part of the European vehicle number to Decision 2007/756/EC. Decision 2007/756/EC should therefore be amended accordingly.
(9) Via the Committee established in accordance with Article 29 of Directive 2008/57/EC, the Commission must inform the Member States of changes in the lists of codes published by the Agency.
(10) Directive 2008/57/EC defines the ‘operation and traffic management’ subsystem as functional. Consequently, the TSI on operation and traffic management is not assessed when authorising a vehicle to be brought into service but when assessing the safety management systems of railway undertakings and infrastructure managers.
(11) For the sake of clarity and simplicity, it is appropriate not to amend the transitional provisions set out in Articles 3, 5 and 7 of Decision 2011/314/EU.
(12) Decisions 2008/231/EC and 2011/314/EU should be repealed.
(13) The measures provided for in this Decision are in conformity with the opinion of the Committee established in accordance with Article 29(1) of Directive 2008/57/EC,
HAS ADOPTED THIS DECISION:
1. The technical specification for interoperability (TSI) relating to the ‘operation and traffic management’ subsystem of the rail system in the Union, as set out in Annex I, is hereby adopted.
2. The TSI set out in Annex I to this Decision shall apply to the operation and traffic management subsystem as described in point 2.5 of Annex II to Directive 2008/57/EC.
Member States shall notify the following types of agreement to the Commission by 30 June 2014 at the latest, provided they have not already been notified under Commission Decision 2006/920/EC(6), Decision 2008/231/EC or Decision 2011/314/EU:
(a)
national agreements between the Member States and railway undertakings or infrastructure managers, agreed on either a permanent or a temporary basis and required by the very specific or local nature of the intended transport service;
(b)
bilateral or multilateral agreements between railway undertakings, infrastructure managers or safety authorities which deliver significant levels of local or regional interoperability;
(c)
international agreements between one or more Member States and at least one third country, or between railway undertakings or infrastructure managers of Member States and at least one railway undertaking or infrastructure manager of a third country, which deliver significant levels of local or regional interoperability.
Each Member State, acting in accordance with Chapter 7 of Annex I to this Decision, shall update the national implementation plans for the TSI, established in accordance with Article 4 of Decision 2006/920/EC, Article 4 of Decision 2008/231/EC and Article 5 of Decision 2011/314/EU.
Each Member State shall forward the updated implementation plan to the other Member States and the Commission by 31 December 2014 at the latest.
Decisions 2008/231/EC and 2011/314/EU are hereby repealed with effect from 1 January 2014.
Decision 2007/756/EC is hereby amended as follows:
(a)
The following Article is inserted after Article 1:
Appendix 6 of the Annex of this Decision shall apply from 1 January 2014.’
(b)
The Annex is amended in accordance with Annex II to this Decision.
1. The Agency shall publish on its website the lists of codes referred in parts 9, 10, 11, 12 and 13 of Appendix 6 of the Annex to Decision 2007/756/EC.
2. The Agency shall keep the lists of codes referred to in paragraph 1 up to date and shall inform the Commission of any changes to those codes. The Commission shall inform the Member States of the evolution of these lists through the Committee established in accordance with Article 29 of Directive 2008/57/EC.
This Decision shall apply from 1 January 2014.
This Decision is addressed to the Member States.

TECHNICAL SPECIFICATION FOR INTEROPERABILITY FOR THE ‘OPERATION AND TRAFFIC MANAGEMENT’ SUBSYSTEM

ANNEX ITABLE OF CONTENTS
1. | INTRODUCTION | 9
1.1. | Technical scope | 9
1.2. | Geographical scope | 9
1.3. | Content of this TSI | 9
2. | DESCRIPTION OF SUBSYSTEM/SCOPE | 9
2.1. | Subsystem | 9
2.2. | Scope | 9
2.2.1. | Staff and trains | 10
2.2.2. | Principles | 10
2.2.3. | Applicability to existing vehicles and infrastructure | 11
3. | ESSENTIAL REQUIREMENTS | 11
3.1. | Compliance with the essential requirements | 11
3.2. | Essential requirements — overview | 11
4. | CHARACTERISTICS OF THE SUBSYSTEM | 15
4.1. | Introduction | 15
4.2. | Functional and technical specifications of the subsystem | 15
4.2.1. | Specifications relating to staff | 15
4.2.1.1. | General requirements | 15
4.2.1.2. | Documentation for drivers | 15
4.2.1.2.1 | Driver’s Rule Book | 15
4.2.1.2.2 | Description of the line and the relevant line-side equipment associated with the lines worked over | 16
4.2.1.2.2.1 | Preparation of the Route Book | 16
4.2.1.2.2.2 | Modifications to information contained within the Route Book | 17
4.2.1.2.2.3 | Informing the driver in real time | 17
4.2.1.2.3 | Timetables | 17
4.2.1.2.4 | Rolling stock | 18
4.2.1.3. | Documentation for railway undertaking staff other than drivers | 18
4.2.1.4. | Documentation for infrastructure manager’s staff authorising train movements | 18
4.2.1.5. | Safety-related communications between train crew, other railway undertaking staff and staff authorising train movements | 18
4.2.2. | Specifications relating to trains | 18
4.2.2.1. | Train visibility | 18
4.2.2.1.1. | General requirement | 18
4.2.2.1.2. | Front end | 19
4.2.2.1.3. | Rear end | 19
4.2.2.1.3.1 | Passenger trains | 20
4.2.2.1.3.2 | Freight trains in international traffic | 20
4.2.2.1.3.3 | Freight trains not crossing a border between Member States | 20
4.2.2.2. | Train audibility | 20
4.2.2.2.1. | General requirement | 20
4.2.2.2.2. | Control | 20
4.2.2.3. | Vehicle identification | 20
4.2.2.4. | Safety of passengers and load | 20
4.2.2.4.1 | Safety of load | 20
4.2.2.4.2 | Safety of passengers | 21
4.2.2.5. | Train composition | 21
4.2.2.6. | Train braking | 21
4.2.2.6.1 | Minimum requirements of the braking system | 21
4.2.2.6.2 | Braking performance | 21
4.2.2.7. | Ensuring that the train is in running order | 22
4.2.2.7.1 | General requirement | 22
4.2.2.7.2 | Data required | 22
4.2.2.8. | Requirements for lineside signal and marker sighting | 22
4.2.2.9. | Driver vigilance | 22
4.2.3. | Specifications relating to train operations | 22
4.2.3.1. | Train planning | 22
4.2.3.2. | Identification of trains | 22
4.2.3.2.1 | Format of train running number | 23
4.2.3.3. | Train departure | 23
4.2.3.3.1 | Checks and tests before departure | 23
4.2.3.3.2 | Informing the infrastructure manager of the train’s operational status | 23
4.2.3.4. | Traffic management | 23
4.2.3.4.1 | General requirements | 23
4.2.3.4.2 | Train reporting | 23
4.2.3.4.2.1 | Data required for train position reporting | 23
4.2.3.4.2.2 | Predicted hand over time | 24
4.2.3.4.3 | Dangerous goods | 24
4.2.3.4.4 | Operational quality | 24
4.2.3.5. | Data recording | 24
4.2.3.5.1 | Recording of supervision data outside the train | 25
4.2.3.5.2 | Recording of supervision data on-board the train | 25
4.2.3.6. | Degraded operation | 25
4.2.3.6.1 | Advice to other users | 25
4.2.3.6.2 | Advice to train drivers | 25
4.2.3.6.3 | Contingency arrangements | 25
4.2.3.7. | Managing an emergency situation | 26
4.2.3.8. | Aid to train crew in the event of an incident or of a major rolling stock malfunction | 26
4.3. | Functional and technical specifications of the interfaces | 26
4.3.1. | Interfaces with the infrastructure TSIs | 26
4.3.2. | Interfaces with the control-command and signalling TSIs | 27
4.3.3. | Interfaces with the rolling stock TSI | 27
4.3.3.1. | Interfaces with TSI on locomotives and passenger rolling stock TSI | 27
4.3.3.2. | Interfaces with TSI on freight wagons | 28
4.3.3.3. | Interfaces with TSI on high-speed rolling stock | 28
4.3.4. | Interfaces with the Energy TSI | 30
4.4. | Operating rules | 31
4.5. | Maintenance rules | 31
4.6. | Professional qualifications | 31
4.6.1. | Professional competency | 31
4.6.1.1. | Professional knowledge | 31
4.6.1.2. | Ability to put this knowledge into practice | 31
4.6.2. | Linguistic competency | 32
4.6.2.1. | Principles | 32
4.6.2.2. | Level of knowledge | 32
4.6.3. | Initial and ongoing assessment of staff | 32
4.6.3.1. | Basic elements | 32
4.6.3.2. | Analysis of training needs | 33
4.6.3.2.1 | Development of the analysis of training needs | 33
4.6.3.2.2 | Updating the analysis of training needs | 33
4.6.3.2.3 | Specific elements for train crew and auxiliary staff | 33
4.6.3.2.3.1 | Infrastructure knowledge | 33
4.6.3.2.3.2 | Knowledge of rolling stock | 33
4.6.3.2.3.3 | Auxiliary staff | 34
4.7. | Health and safety conditions | 34
4.7.1. | Introduction | 34
4.7.2. | Deleted | 34
4.7.3. | Deleted | 34
4.7.4. | Medical examinations and psychological assessments | 34
4.7.4.1. | Before appointment: | 34
4.7.4.1.1 | Minimum content of the medical examination | 34
4.7.4.1.2 | Psychological assessment | 34
4.7.4.2. | After appointment | 35
4.7.4.2.1 | Periodicity of periodic medical examinations | 35
4.7.4.2.2 | Minimum content of the periodic medical examination | 35
4.7.4.2.3 | Additional medical examinations and/or psychological assessments | 35
4.7.5. | Medical requirements | 35
4.7.5.1. | General requirements | 35
4.7.5.2. | Vision requirements | 36
4.7.5.3. | Hearing requirements | 36
4.8. | Registers of infrastructure and vehicles | 36
4.8.1. | Infrastructure | 36
4.8.2. | Rolling stock | 36
5. | INTEROPERABILITY CONSTITUENTS | 36
5.1. | Definition | 36
5.2. | List of constituents | 37
6. | ASSESSMENT OF CONFORMITY AND/OR SUITABILITY FOR USE OF THE CONSTITUENTS AND VERIFICATION OF THE SUBSYSTEM | 37
6.1. | Interoperability constituents | 37
6.2. | Operation and traffic management subsystem | 37
6.2.1. | Principles | 37
7. | IMPLEMENTATION | 37
7.1. | Principles | 37
7.2. | Implementation guidelines | 38
7.3. | Specific cases | 38
7.3.1. | Introduction | 38
7.3.2. | List of specific cases | 38
7.3.2.1. | Temporary specific case (T1) Estonia, Latvia and Lithuania | 38
7.3.2.2. | Temporary specific case (T2) Ireland and United Kingdom | 38
Appendix A: | ERTMS/ETCS operating rules | 38
Appendix B: | Other rules enabling a coherent operation | 39
Appendix C: | Safety related communications methodology | 40
Appendix D: | Information to which the Railway Undertaking must have access in connection with the route(s) over which he intends to operate | 50
Appendix E: | Language and communication level | 54
Appendix F: | | 55
Appendix G: | | 55
Appendix H: | | 55
Appendix I: | | 55
Appendix J: | Minimum elements relevant to professional qualification for the tasks associated with ‘accompanying trains’ | 56
Appendix K: | | 57
Appendix L: | Minimum elements relevant to professional qualification for the task of preparing trains | 58
Appendix M: | | 59
Appendix N: | | 59
Appendix O: | | 59
Appendix P: | European Vehicle Number and linked alphabetical marking on the bodywork | 60
Appendix Q: | | 62
Appendix R: | | 62
Appendix S: | | 62
Appendix T: | Braking performance | 63
Appendix U: | List of open points | 64
Appendix V: | | 64
Appendix W: | Glossary | 651. INTRODUCTION1.1. Technical scope
This Technical Specification for Interoperability (hereinafter referred to as ‘TSI’) concerns the ‘operation and traffic management’ subsystem referred to in the list contained in point 1 of Annex II to Directive 2008/57/EC. Further information on this subsystem is provided in Chapter 2 of this Annex.
Where necessary the TSI distinguishes between requirements for conventional and high-speed rail as defined in Annex I, chapter 2.1 of Directive 2008/57/EC.
1.2. Geographical scope
The geographical scope of this TSI is the European rail system in accordance with Article 1 of Directive 2008/57/EC excluding the systems and networks referred to in Article 1(3) of Directive 2008/57/EC.
1.3. Content of this TSI
In accordance with Article 5(3) of Directive 2008/57/EC, this TSI:

(a) | indicates its intended scope for the ‘operation and traffic management’ subsystem — Chapter 2;
(b) | lays down essential requirements for the subsystem concerned and its interfacesvis-à-visother subsystems — Chapter 3;
(c) | establishes the functional and technical specifications to be met by the target subsystem and its interfacesvis-à-visother subsystems. If necessary, these specifications may vary according to the use of the subsystem, for example according to the categories of line, hub and/or rolling stock provided for in Annex I to Directive 2008/57/EC — Chapter 4;
(d) | determines the interoperability constituents and interfaces covered by European specifications, including European standards, which are necessary to achieve interoperability within the European rail system — Chapter 5;
(e) | states, in each case under consideration, which procedures are to be used in order to assess the conformity or suitability for use of the interoperability constituents — Chapter 6;
(f) | indicates the strategy for implementing the TSI. In particular, it is necessary to specify the stages to be completed and the elements that can be applied in order to make a gradual transition from the existing situation to the final situation in which compliance with the TSI must be the norm — Chapter 7;
(g) | indicates, for the staff concerned, the professional qualifications and health and safety conditions at work required for the operation and maintenance of the subsystem concerned, as well as for the implementation of the TSI — Chapter 4.Moreover, in accordance with Article 5(5) of Directive 2008/57/EC, provision may be made for specific cases for each TSI. These are indicated in Chapter 7.
This TSI also comprises, in Chapter 4, the operating and maintenance rules specific to the scope indicated in points 1.1 and 1.2 of this Annex.
2. DESCRIPTION OF SUBSYSTEM/SCOPE2.1. Subsystem
The ‘operation and traffic management’ subsystem is described in point 2.5 of Annex II to Directive 2008/57/EC as:

‘The procedures and related equipment enabling coherent operation of the various structural subsystems, during both normal and degraded operation, including in particular train composition and train driving, traffic planning and management.
The professional qualifications which may be required for carrying out cross-border services.’

2.2. Scope
This TSI applies to the ‘operation and traffic management’ subsystem of infrastructure managers (hereinafter referred to as ‘IM’) and railway undertakings (hereinafter referred to as ‘RU’) related to the operation of trains on the European rail system as defined in chapter 1.2.
2.2.1. Staff and trains
Points 4.6 and 4.7 apply to those staff undertaking the safety-critical tasks of accompanying a train, when this involves crossing a border(s) between states and working beyond any location(s) designated as the ‘frontier’ in the network statement of an infrastructure manager and included in his safety authorisation.
Point 4.6.2 also applies to train drivers as stipulated by point 8 of Annex VI to Directive 2007/59/EC of the European Parliament and of the Council(1). A staff member will not be considered as crossing a border if the activity only involves working as far as any ‘frontier’ locations as described in the first paragraph of this point.
For those staff undertaking the safety-critical tasks of despatching trains and authorising train movements, mutual recognition of professional qualifications and health and safety conditions between Member States will apply.
For those staff undertaking the safety-critical tasks associated with the last preparation of a train before it is scheduled to cross a border(s) and work beyond any ‘frontier’ location(s) as described in the first paragraph of this point, point 4.6 will apply with mutual recognition between Member States of health and safety conditions. A train will not be considered to be a cross border service, if all the vehicles of the train crossing the state border cross it only to the ‘frontier’ location(s) as described in the first paragraph of this point.
This can be summarised in tables 1 and 2:

Table 1

Staff involved with the working of trains that will cross-state borders and proceed beyond the frontier location

Task | Professional Qualifications | Medical Requirements
Accompanying a Train | 4.6 | 4.7
Authorising Train movements | Mutual recognition | Mutual recognition
Train Preparation | 4.6 | Mutual recognition
Train Despatch | Mutual recognition | Mutual recognition

Table 2

Staff working trains that do not cross state borders or do so as far as frontier locations

Task | Professional Qualifications | Medical Requirements
Accompanying a Train | Mutual recognition | Mutual recognition
Authorising Train movements | Mutual recognition | Mutual recognition
Train Preparation | Mutual recognition | Mutual recognition
Train Despatch | Mutual recognition | Mutual recognition2.2.2. Principles
This TSI covers those elements (as set out in Chapter 4) of the ‘operation and traffic management’ subsystem, where principally there are operational interfaces between RU and IM and where there is a particular benefit to interoperability.
RU and IM must ensure that all requirements concerning rules and procedures as well as documentation are met by the establishment of the appropriate processes. The set-up of these processes is a relevant part of RU’s and IM’s safety management system (hereinafter referred to as ‘SMS’) as required by Directive 2004/49/EC of the European Parliament and of the Council(2). The SMS itself is assessed by the relevant national safety authority (hereinafter referred to as ‘NSA’) before granting safety certificate/authorisation.
2.2.3. Applicability to existing vehicles and infrastructure
While the majority of the requirements contained in this TSI relate to processes and procedures, a number also relate to physical elements, trains and vehicles which are important for operation.
The design criteria for these elements are described in the structural TSIs covering subsystems such as rolling stock. In the context of this TSI it is their operational function that is considered.
3. ESSENTIAL REQUIREMENTS3.1. Compliance with the essential requirements
In accordance with Article 4(1) of Directive 2008/57/EC, the European rail system, its subsystems and their interoperability constituents must meet the essential requirements set out in general terms in Annex III to that Directive.
3.2. Essential requirements — overview
The essential requirements cover:

— | safety,
— | reliability and availability,
— | health,
— | environmental protection,
— | technical compatibility.According to Directive 2008/57/EC, the essential requirements may be generally applicable to the whole European rail system or be specific to each subsystem and its constituents.
The following table 3 summarises the correspondence between the essential requirements set out in Annex III to Directive 2008/57/EC and the present TSI.

Table 3

Clause | Clause Title | Safety | Reliability & Availability | Health | Environmental protection | Technical compatibility | Essential requirements specific to operation and traffic management
1.1.1 | 1.1.2 | 1.1.3 | 1.1.4 | 1.1.5 | 1.2 | 1.3.1 | 1.3.2 | 1.4.1 | 1.4.2 | 1.4.3 | 1.4.4 | 1.4.5 | 1.5 | 2.6.1 | 2.6.2 | 2.6.3
4.2.1.2 | Documentation for drivers | | | | | | X | | | | | | | | | X | | X
4.2.1.2.1 | Rule book | | | | | | | | | | | | X | | | X | | X
4.2.1.2.2 | Route book | | | | | | | | | | | | | | | X | | X
4.2.1.2.2.1 | Preparation of the Route book | | | | | | | | | | | | | | | X | |
4.2.1.2.2.2 | Modification to Information contained within the route book | | | | | | | | | | | | | | | X | | X
4.2.1.2.2.3 | Informing the driver in real time | | | | | | | | | | | | | | | X | X | X
4.2.1.2.3 | Timetables | | | | | | | | | | | | | | | X | X | X
4.2.1.2.4 | Rolling stock | | | | | | X | | | | | | | | | X | | X
4.2.1.3 | Documentation for railway undertaking staff other than drivers | | | | | | X | | | | | | | | | X | | X
4.2.1.4 | Documentation for infrastructure manager’s staff authorising train movements | | | | | | X | | | | | | | | | X | X |
4.2.1.5 | Safety-related communications between train crew, other railway undertaking staff and staff authorising train movements | | | | | | X | | | | | | | | | X | X | X
4.2.2.1 | Train visibility | X | | | | | | | | | | | | | | X | | X
4.2.2.1.1 | General requirement | X | | | | | | | | | | | | | | X | | X
4.2.2.1.2 | Front end | X | | | | | | | | | | | | | | X | | X
4.2.2.1.3 | Rear end | X | | | | | | | | | | | | | | X | | X
4.2.2.2 | Train audibility | X | | | | | | | | | | | X | | | X | | X
4.2.2.2.1 | General requirement | X | | | | | | | | | | | | | | X | | X
4.2.2.2.2 | Control | X | | | | | | | | | | | | | | | | X
4.2.2.3 | Vehicle identification | | | | | | X | | | | | | | | | X | | X
4.2.2.4 | Safety of passengers and load | | | | | | | | | | | | | | | X | |
4.2.2.5 | Train composition | | | | | | | | | | | | | | | X | |
4.2.2.6 | Train braking | | X | | | | | | | | | | | | | X | | X
4.2.2.6.1 | Minimum requirements of the braking system | | X | | | | | | | | | | | | | X | | X
4.2.2.6.2 | Braking performance | | X | | | | | | | | | | | | | X | | X
4.2.2.7 | Ensuring that the train is in running order | | X | | | | | | | | | | | | | X | | X
4.2.2.7.1 | General requirement | | | | | | | | | | | | | | | X | | X
4.2.2.7.2 | Data required | | | | | | | | | | | | | | | X | | X
4.2.2.8 | Requirements for Signal and lineside marker sighting | | | | | | | | | | | | | | X | X | |
4.2.2.9 | Driver vigilance | | | | | | | | | | | | | | | X | |
4.2.3.1 | Train planning | | X | | | | | | | | | | | | | | X | X
4.2.3.2 | Identification of trains | | | | | | | | | | | | | | | X | X | X
4.2.3.3 | Train departure | | | | | | | | | | | | | | | X | | X
4.2.3.3.1 | Checks and tests before departure | | X | | | | X | | | | | | | | | X | | X
4.2.3.3.2 | Informing the Infrastructure Manager of the train’s operational status | | X | | | | X | | | | | | | | | | X | X
4.2.3.4 | Traffic management | | | | | | | | | | | | | | | X | X | X
4.2.3.4.1 | General requirements | | | | | | | | | | | | | | | X | X | X
4.2.3.4.2 | Train reporting | | | | | | | | | | | | | | | X | X | X
4.2.3.4.2.1 | Data required for train position reporting | | | | | | | | | | | | | | | X | | X
4.2.3.4.2.2 | Predicted hand over time | | | | | | | | | | | | | | | X | | X
4.2.3.4.3 | Dangerous goods | | | | | | | | | | | | | | | X | X |
4.2.3.4.4 | Operational quality | | | | | | | | | | | | | | | | X | X
4.2.3.5 | Data recording | | | | | | X | | | | | | | | | | X |
4.2.3.5.1 | Recording of supervision data outside the train | | | | | | X | | | | | | | | | | X |
4.2.3.5.2 | Recording of supervision data on-board the train | | | | | | X | | | | | | | | | | X |
4.2.3.6 | Degraded operation | | | | | | | | | | | | | | | X | X | X
4.2.3.6.1 | Advice to other users | | | | | | | | | | | | | | | X | | X
4.2.3.6.2 | Advice to train drivers | | | | | | | | | | | | | | | X | |
4.2.3.6.3 | Contingency arrangements | | | | | | | | | | | | | | | X | X | X
4.2.3.7 | Managing an emergency situation | | | | | | | | | | | | | | | X | X | X
4.2.3.8 | Aid to train crew in the event of an incident or of a major rolling stock malfunction | | | | | | | | | | | | | | | | | X
4.4 | Operating rules | | | | | | | | | | | | | | | X | X |
4.6 | Professional qualifications | | | | | | | | | | | | | | | X | X | X
4.7 | Health and safety conditions | | | | | | | | | | | | | | | X | | 4. CHARACTERISTICS OF THE SUBSYSTEM4.1. Introduction
Taking into account all the relevant essential requirements, the ‘operation and traffic management’ subsystem, as described in point 2.2, covers only the elements specified in this Chapter.
In conformity with Directive 2001/14/EC of the European Parliament and of the Council(3), it is the overall responsibility of the infrastructure manager to provide all the appropriate requirements which must be met by trains permitted to run on its network, taking into account the geographic particularities of individual lines and the functional or technical specifications set out in this Chapter.
4.2. Functional and technical specifications of the subsystem
The functional and technical specifications of the ‘operation and traffic management’ subsystem comprise of the following:

— | specifications relating to staff,
— | specifications relating to trains,
— | specifications relating to train operations.4.2.1. Specifications relating to staff
4.2.1.1. General requirements
This point deals with staff who contributes to the operation of the subsystem by performing safety-critical tasks involving a direct interface between a railway undertaking and an infrastructure manager.

(1) | Railway undertaking staff:(a)undertaking the task of driving trains (referred to throughout this TSI as ‘driver’) and forming part of the ‘train crew’,(b)undertaking tasks on-board (other than driving) and forming part of the ‘train crew’,(c)undertaking the task of preparing trains. | (a) | undertaking the task of driving trains (referred to throughout this TSI as ‘driver’) and forming part of the ‘train crew’, | (b) | undertaking tasks on-board (other than driving) and forming part of the ‘train crew’, | (c) | undertaking the task of preparing trains.
(a) | undertaking the task of driving trains (referred to throughout this TSI as ‘driver’) and forming part of the ‘train crew’,
(b) | undertaking tasks on-board (other than driving) and forming part of the ‘train crew’,
(c) | undertaking the task of preparing trains.
(2) | Infrastructure manager’s staff undertaking the task of authorising the movement of trainsThe areas covered are:

— | Documentation
— | CommunicationIn addition, for the staff as defined in point 2.2.1., this TSI sets out requirements on:

— | Qualifications (see point 4.6 and Appendix L)
— | Health and safety conditions (see point 4.7)4.2.1.2. Documentation for drivers
The railway undertaking operating the train must supply the driver with all the necessary information and documentation required to carry out his duties.
This information must take into account the necessary elements for operation in normal, degraded and emergency situations for the routes to be worked over and the rolling stock used on those routes.
4.2.1.2.1. Driver’s Rule BookAll the necessary procedures for the driver must be included in a document or a computer medium called the ‘Driver’s Rule Book’.
The Driver’s Rule Book must state the requirements for all the routes worked and the rolling stock used on those routes according to the situations of normal operation, degraded operation and in emergency situations which the driver may encounter.
The Driver’s Rule Book must cover two distinct aspects:

— | one which describes the set of common rules and procedures (taking into account the contents of Appendices A, B and C),
— | another which sets out any necessary rules and procedures specific to each infrastructure manager.It must include procedures covering, as a minimum, the following aspects:

— | Staff safety and security,
— | Signalling and control-command,
— | Train operation including degraded mode,
— | Traction and rolling stock,
— | Incidents and accidents.The railway undertaking is responsible for compiling the Driver’s Rule Book.
The railway undertaking must present the Driver’s Rule Book in the same format for the entire infrastructure over which their drivers will work.
The railway undertaking must compile the Driver’s Rule Book in such a way that the driver’s application of all operational rules is enabled.
It must have two appendices:

— | Appendix 1: Manual of communication procedures;
— | Appendix 2: Book of Forms.Predefined messages and forms must remain in the ‘operating’ language of infrastructure manager(s).
The process for preparing and updating the Driver’s Rule Book must include the following steps:

— | the infrastructure manager (or the organisation responsible for the preparation of the operating rules) must provide the railway undertaking with the appropriate information in the infrastructure manager’s operating language,
— | the railway undertaking must draw up the initial or updated document;
— | if the language chosen by the railway undertaking for the Driver’s Rule Book is not the language in which the appropriate information was originally supplied, it is the responsibility of the railway undertaking to arrange for any necessary translation and/or provide explanatory notes in another language.The infrastructure manager must ensure that the content of the documentation provided to the railway undertaking(s) is complete and accurate.
The railway undertaking must ensure that the content of the Driver’s Rule Book is complete and accurate.
4.2.1.2.2. Description of the line and the relevant line-side equipment associated with the lines worked overDrivers must be provided with a description of the lines and the associated line-side equipment for the lines over which they will operate and relevant to the driving task. Such information must be set out in a single document called the ‘Route Book’ (which can either be a traditional document or computer based).
The following is a list of information which must, as a minimum, be provided:

— | the general operating characteristics,
— | indication of rising and falling gradients,
— | detailed line diagram.4.2.1.2.2.1. Preparation of the Route BookThe format of the Route Book must be prepared in the same manner for all the infrastructures worked over by the trains of an individual railway undertaking.
The railway undertaking is responsible for the complete and correct compilation of the Route book (for example, arranging for any necessary translation and/or providing explanatory notes), using the information supplied by the infrastructure manager(s).
The following information must be included (this list is not exhaustive):

(a) | the general operating characteristics:—type of signalling and corresponding running regime (double track, reversible working, left or right hand running, etc.),—type of power supply,—type of ground-train radio equipment. | — | type of signalling and corresponding running regime (double track, reversible working, left or right hand running, etc.), | — | type of power supply, | — | type of ground-train radio equipment.
— | type of signalling and corresponding running regime (double track, reversible working, left or right hand running, etc.),
— | type of power supply,
— | type of ground-train radio equipment.
(b) | indication of rising and falling gradients with their gradient values and location;
(c) | detailed line diagram:—names of stations on the line and key locations and their location;—tunnels, including location, name, length, specific information such as the existence of walkways and points of safe egress as well as the location of safe places where evacuation of passengers can take place—essential locations such as neutral sections—permissible speed limits for each track, including, if necessary, differential speeds relating to certain types of train,—the responsible infrastructure manager—means of communication with the traffic management/control centre in normal and degraded mode | — | names of stations on the line and key locations and their location; | — | tunnels, including location, name, length, specific information such as the existence of walkways and points of safe egress as well as the location of safe places where evacuation of passengers can take place | — | essential locations such as neutral sections | — | permissible speed limits for each track, including, if necessary, differential speeds relating to certain types of train, | — | the responsible infrastructure manager | — | means of communication with the traffic management/control centre in normal and degraded mode
— | names of stations on the line and key locations and their location;
— | tunnels, including location, name, length, specific information such as the existence of walkways and points of safe egress as well as the location of safe places where evacuation of passengers can take place
— | essential locations such as neutral sections
— | permissible speed limits for each track, including, if necessary, differential speeds relating to certain types of train,
— | the responsible infrastructure manager
— | means of communication with the traffic management/control centre in normal and degraded modeThe infrastructure manager must ensure that the content of the documentation provided to the railway undertaking(s) is complete and accurate.
The railway undertaking must ensure that the content of the Route Book is complete and accurate.
4.2.1.2.2.2. Modifications to information contained within the Route BookThe infrastructure manager must advise the railway undertaking of any permanent or temporary modifications to information supplied in accordance with point 4.2.1.2.2.1.
These changes must be grouped by the railway undertaking into a dedicated document or computer medium whose format must be the same for all the infrastructures worked over by the trains of an individual railway undertaking.
The infrastructure manager must ensure that the content of the documentation provided to the railway undertaking(s) is complete and accurate.
The railway undertaking must ensure that the content of the document grouping the modifications to information contained within the Route book is complete and accurate.
4.2.1.2.2.3. Informing the driver in real timeThe infrastructure manager must inform drivers of any changes to the line or relevant lineside equipment that have not been advised as modifications to information for the Route Book as set out in point 4.2.1.2.2.2.
4.2.1.2.3. TimetablesThe provision of train schedule information facilitates the punctual running of trains and assists in service performance.
The railway undertaking must provide drivers with the information necessary for the normal running of the train and as a minimum include:

— | the train identification;
— | the train running days (if necessary);
— | the stopping points and the activities associated with them
— | other timing points;
— | the arrival/departure/passing times at each of those points.Such train running information, which must be based on information supplied by the infrastructure manager, may be provided either electronically or in a paper format.
Presentation to the driver must be consistent across all the lines over which the railway undertaking operates.
4.2.1.2.4. Rolling stockThe railway undertaking must provide the driver with all information relevant to the working of the rolling stock during degraded situations (such as trains requiring assistance). Such documentation must also focus on the specific interface with the infrastructure manager’s staff in these cases.
4.2.1.3. Documentation for railway undertaking staff other than drivers
The railway undertaking must provide all members of his staff (whether on train or otherwise) who undertake safety-critical tasks involving a direct interface with the staff, equipment or systems of the infrastructure manager with the rules, procedures, rolling stock and route specific information it deems appropriate to such tasks. Such information shall be applicable in both normal and degraded operation.
For staff on-board trains, the structure, format, content and process for preparation and updating of such information must be based on the specification set out in Subsection 4.2.1.2 of this TSI.
4.2.1.4. Documentation for infrastructure manager’s staff authorising train movements
All the information necessary to ensure safety-related communication between staff authorising the movement of trains and train crews must be set out in:

— | documents describing the Communications Principles (Appendix C);
— | the document entitled Book of forms.The infrastructure manager must draw up these documents in his operating language.
4.2.1.5. Safety-related communications between train crew, other railway undertaking staff and staff authorising train movements
The language used for safety-related communication between train crew, other railway undertaking staff (as defined in Appendix L) and the staff authorising train movements is the operating language (see glossary) used by the infrastructure manager on the route concerned.
The principles for safety-related communication between train crew and staff responsible for authorising the movement of trains are to be found in Appendix C.
In conformity with Directive 2001/14/EC, the infrastructure manager is responsible for publishing the ‘operating’ language used by his personnel in daily operational use.
Where, however, local practice requires that a second language is also provided for, it is the responsibility of the infrastructure manager to determine the geographic boundaries for its use.
4.2.2. Specifications relating to trains
4.2.2.1. Train visibility
4.2.2.1.1. General requirementThe railway undertaking must ensure that trains are fitted with means of indicating the front and rear of the train.
4.2.2.1.2. Front endThe railway undertaking must ensure that an approaching train is clearly visible and recognisable as such, by the presence and layout of its lit white front-end lights.
The forward facing front-end of the leading vehicle of a train must be fitted with three lights in an isosceles triangle, as shown below. These lights must always be lit when the train is being driven from that end.

The front lights must optimise train detectability (for example, to track workers and those using public crossings) (marker lights), provide sufficient visibility for the train driver (illumination of the line ahead, lineside information markers/boards, etc.) (head lights) by night and during low light conditions and must not dazzle the drivers of oncoming trains.
The spacing, the height above rails, the diameter, the intensity of the lights, the dimensions and shape of the emitted beam in both day and night time operation are defined in the rolling stock TSI(hereinafter referred to as ‘RST TSI’).
4.2.2.1.3. Rear endThe railway undertaking must provide the required means of indicating the rear of a train. The rear end signal must only be exhibited on the rear of the last vehicle of the train. It must be displayed as shown below.

| 4.2.2.1.3.1. Passenger trainsThe rear end indication of a passenger train must consist of 2 steady red lights at the same height above buffer on the transversal axis.
4.2.2.1.3.2. Freight trains in international trafficThe Member State must notify which of the following requirements will apply on the network of its Member State for trains that cross a border between Member States:
Either

— | 2 steady red lights, or
— | 2 reflective plates of the following shape with white side triangles and red top and bottom triangle:The lamps or plates must be on the same height above buffer on the transversal axis. Member States that require 2 reflective plates must also accept 2 steady red lights as train rear end indication.
4.2.2.1.3.3. Freight trains not crossing a border between Member StatesFor freight trains not crossing a border between Member States the train rear end indication is an open point (see Appendix U).
4.2.2.2. Train audibility
4.2.2.2.1. General requirementThe railway undertaking must ensure that trains are fitted with an audible warning device to indicate the approach of a train.
4.2.2.2.2. ControlThe activation of the audible warning device must be possible from all driving positions.
4.2.2.3. Vehicle identification
Each vehicle must have a European Vehicle number to uniquely identify it from any other rail vehicle. This number must be prominently displayed at least on each longitudinal side of the vehicle as specified in Appendix P.
The European Vehicle Number consists of 12 digits; further details are set out in the Decision 2007/756/EC.
It must also be possible to identify operational restrictions applicable to the vehicle.
4.2.2.4. Safety of passengers and load
4.2.2.4.1. Safety of loadThe railway undertaking must make sure that freight vehicles are safely and securely loaded and remain so throughout the journey.
4.2.2.4.2. Safety of passengersThe railway undertaking must ensure that passenger transport is undertaken safely at the departure and during the journey.
4.2.2.5. Train composition
The railway undertaking must define the rules and procedures to be followed by his staff so as to ensure that the train is in compliance with the allocated path.
Train composition requirements must take into account the following elements:

(a) | the vehicles—all vehicles in the train must be in compliance with all the requirements applicable on the routes over which the train will run;—all vehicles on the train must be fit to run at the maximum speed at which the train is scheduled to run;—all vehicles on the train must be currently within their specified maintenance interval and will remain so for the duration (in terms of both time and distance) of the journey being undertaken; | — | all vehicles in the train must be in compliance with all the requirements applicable on the routes over which the train will run; | — | all vehicles on the train must be fit to run at the maximum speed at which the train is scheduled to run; | — | all vehicles on the train must be currently within their specified maintenance interval and will remain so for the duration (in terms of both time and distance) of the journey being undertaken;
— | all vehicles in the train must be in compliance with all the requirements applicable on the routes over which the train will run;
— | all vehicles on the train must be fit to run at the maximum speed at which the train is scheduled to run;
— | all vehicles on the train must be currently within their specified maintenance interval and will remain so for the duration (in terms of both time and distance) of the journey being undertaken;
(b) | the train—the combination of vehicles forming a train must comply with the technical constraints of the route concerned and be within the maximum length permissible for forwarding and receiving terminals.—the railway undertaking is responsible for ensuring that the train is technically fit for the journey to be undertaken and remains so throughout the journey | — | the combination of vehicles forming a train must comply with the technical constraints of the route concerned and be within the maximum length permissible for forwarding and receiving terminals. | — | the railway undertaking is responsible for ensuring that the train is technically fit for the journey to be undertaken and remains so throughout the journey
— | the combination of vehicles forming a train must comply with the technical constraints of the route concerned and be within the maximum length permissible for forwarding and receiving terminals.
— | the railway undertaking is responsible for ensuring that the train is technically fit for the journey to be undertaken and remains so throughout the journey
(c) | the weight and axle load—the weight of the train must be within the maximum permissible for the section of route, the strength of the couplings, the traction power and other relevant characteristics of the train. Axle load limitations must be respected. | — | the weight of the train must be within the maximum permissible for the section of route, the strength of the couplings, the traction power and other relevant characteristics of the train. Axle load limitations must be respected.
— | the weight of the train must be within the maximum permissible for the section of route, the strength of the couplings, the traction power and other relevant characteristics of the train. Axle load limitations must be respected.
(d) | the maximum speed of the train—the maximum speed at which the train can run must take into account any restrictions on the route(s) concerned, braking performance, axle load and vehicle type. | — | the maximum speed at which the train can run must take into account any restrictions on the route(s) concerned, braking performance, axle load and vehicle type.
— | the maximum speed at which the train can run must take into account any restrictions on the route(s) concerned, braking performance, axle load and vehicle type.
(e) | the kinematic envelope—the kinematic gauge of each vehicle (inclusive of any load) in the train must be within the maximum permissible for the section of route. | — | the kinematic gauge of each vehicle (inclusive of any load) in the train must be within the maximum permissible for the section of route.
— | the kinematic gauge of each vehicle (inclusive of any load) in the train must be within the maximum permissible for the section of route.Additional constraints may be required or imposed due to the type of braking regime or traction type on a particular train.
4.2.2.6. Train braking
4.2.2.6.1. Minimum requirements of the braking systemAll vehicles in a train must be connected to the continuous automatic braking system as defined in the TSI Rolling Stock (Commission Decisions 2006/861/EC(4), 2008/232/EC(5)and 2011/291/EU(6)).
The first and last vehicles (including any traction units) in any train must have the automatic brake operative.
In the case of a train becoming accidentally divided into two parts, both sets of detached vehicles must come automatically to a stand as a result of a maximum application of the brake.
4.2.2.6.2. Braking performanceThe infrastructure manager must provide the railway undertaking with the actual performance required. This data shall include, if necessary, conditions of use of braking systems possibly affecting the infrastructure such as magnetic, regenerative and eddy-current brake.
The railway undertaking is responsible for ensuring that the train has sufficient braking performance by providing braking rules for its staff to be followed.
The rules concerning braking performance have to be managed within the infrastructure manager’s and railway undertaking’s safety management system.
Further requirements are specified in Appendix T.
4.2.2.7. Ensuring that the train is in running order
4.2.2.7.1. General requirementThe railway undertaking must define the process to ensure that all safety-related on-train equipment is in a fully functional state and that the train is safe to run.
The railway undertaking must inform the infrastructure manager of any modification to the characteristics of the train affecting its performance or any modification that might affect the ability to accommodate the train in its allocated path.
The infrastructure manager and the railway undertaking must define and keep up to date conditions and procedures for train running in degraded mode.
4.2.2.7.2. Data requiredThe data required for safe and efficient operation and the process by which this data must be forwarded must comprise:

— | the train identification
— | the identity of the railway undertaking responsible for the train
— | the actual length of the train
— | if a train carries passengers or animals when it is not scheduled to do so
— | any operational restrictions with an indication of the vehicle(s) concerned (gauge, speed restrictions, etc.)
— | information the infrastructure manager requires for the transport of dangerous goods.The railway undertaking must ensure that this data is made available to the infrastructure manager(s) prior to the departure of the train.
The railway undertaking must advise the infrastructure manager(s) if a train will not occupy its allocated path or is cancelled.
4.2.2.8. Requirements for lineside signal and marker sighting
The driver must be able to observe lineside signals and markers, and they must be observable by the driver in the situations where the driver needs to respect the signals and markers. The same applies for other types of lineside signs if they are safety related.
Driving cabs must be designed in such a consistent way that the driver is able to easily see the relevant information displayed to him.
4.2.2.9. Driver vigilance
A means of onboard monitoring of driver vigilance is necessary. This shall intervene to bring the train to a stand if the driver does not react within a certain time; the time range is specified in the rolling stock TSIs.
4.2.3. Specifications relating to train operations
4.2.3.1. Train planning
In accordance with Directive 2001/14/EC the infrastructure manager must advise what data is required when a train path is requested.
4.2.3.2. Identification of trains
Each train must be identified by a train running number. The train running number is given by the infrastructure manager when allocating a train path and must be known by the railway undertaking and all infrastructure managers operating the train. The train running number must be unique per network. Changes of train running number during a train journey should be avoided.
4.2.3.2.1. Format of train running numberThe train running number format is defined in the Commission Decision 2012/88/EU of 25 January 2012 on the technical specification for interoperability relating to the control-command and signalling subsystems of the trans-European rail system(7)(hereinafter referred to as ‘CCS TSI’).
4.2.3.3. Train departure
4.2.3.3.1. Checks and tests before departureThe railway undertaking must define the checks and tests to ensure that any departure is undertaken safely (e.g. doors, load, brakes).
4.2.3.3.2. Informing the infrastructure manager of the train’s operational statusThe railway undertaking shall inform the infrastructure manager when a train is ready for access to the network.
The railway undertaking must inform the infrastructure manager of any anomaly affecting the train or its operation having possible repercussions on the train’s running prior to departure and during the journey.
4.2.3.4. Traffic management
4.2.3.4.1. General requirementsTraffic management must ensure the safe, efficient and punctual operation of the railway, including effective recovery from service disruption.
The infrastructure manager must determine procedures and means for:

— | the real time management of trains,
— | operational measures to maintain the highest possible performance of the infrastructure in case of delays or incidents, whether actual or anticipated, and
— | the provision of information to the railway undertaking(s) in such cases.Any additional processes required by the railway undertaking and which affect the interface with the infrastructure manager(s) can be introduced after being agreed with the infrastructure manager.
4.2.3.4.2. Train reporting4.2.3.4.2.1. Data required for train position reportingThe infrastructure manager must:

(a) | provide a means of real time recording of the times at which trains depart from, arrive at or pass appropriate pre-defined reporting points on their networks and the delta-time value;
(b) | provide the specific data required in relation to train position reporting. Such information must include:—Train identification—Identity of reporting point—Line on which the train is running—Scheduled time at reporting point—Actual time at reporting point (and whether depart, arrive or pass — separate arrival and departure times must be provided in respect of intermediate reporting points at which the train calls)—Number of minutes early or late at the reporting point—Initial explanation of any single delay exceeding 10 minutes or as otherwise required by the performance monitoring regime—Indication that a report for a train is overdue and the number of minutes by which it is overdue—Former train identification(s), if any—Train cancelled for a whole or a part of its journey. | — | Train identification | — | Identity of reporting point | — | Line on which the train is running | — | Scheduled time at reporting point | — | Actual time at reporting point (and whether depart, arrive or pass — separate arrival and departure times must be provided in respect of intermediate reporting points at which the train calls) | — | Number of minutes early or late at the reporting point | — | Initial explanation of any single delay exceeding 10 minutes or as otherwise required by the performance monitoring regime | — | Indication that a report for a train is overdue and the number of minutes by which it is overdue | — | Former train identification(s), if any | — | Train cancelled for a whole or a part of its journey.
— | Train identification
— | Identity of reporting point
— | Line on which the train is running
— | Scheduled time at reporting point
— | Actual time at reporting point (and whether depart, arrive or pass — separate arrival and departure times must be provided in respect of intermediate reporting points at which the train calls)
— | Number of minutes early or late at the reporting point
— | Initial explanation of any single delay exceeding 10 minutes or as otherwise required by the performance monitoring regime
— | Indication that a report for a train is overdue and the number of minutes by which it is overdue
— | Former train identification(s), if any
— | Train cancelled for a whole or a part of its journey.4.2.3.4.2.2. Predicted hand over timeThe infrastructure manager must have a process, which enables an indication of the estimated number of minutes of deviation from the scheduled time a train is scheduled to be handed over from one infrastructure manager to another.
This must include information on service disruption (description and location of problem).
4.2.3.4.3. Dangerous goodsThe railway undertaking must define the procedures to supervise the transport of dangerous goods.
These procedures must include:

— | the provisions as specified in Directive 2008/68/EC of the European Parliament and of the Council(8);
— | advice to the driver of the presence and position of dangerous goods on the train;
— | information the infrastructure manager requires for transport of dangerous goods;
— | determination, in conjunction with the infrastructure manager, of lines of communication and planning of specific measures in case of emergency situations involving the goods.4.2.3.4.4. Operational qualityThe infrastructure manager and the railway undertaking must have processes in place to monitor the efficient operation of the all the services concerned.
Monitoring processes must be designed to analyse data and detect underlying trends, both in terms of human error and system error. The results of this analysis must be used to generate improvement actions, designed to eliminate or mitigate against events which could compromise the efficient operation of the network.
Where such improvement actions would have network-wide benefits, involving other infrastructure managers and railway undertakings, they must, subject to commercial confidentiality, be communicated accordingly.
Events that have significantly disrupted operations must be analysed as soon as possible by the infrastructure manager. Where appropriate, and in particular where one of their staff is concerned, the infrastructure manager must invite those railway undertaking(s) involved in the event concerned to participate in the analysis. Where the result of such analysis leads to network improvement recommendations designed to eliminate or mitigate against causes of accidents/incidents, these must be communicated to all relevant infrastructure managers and railway undertakings concerned.
These processes shall be documented and subject to internal audit.
4.2.3.5. Data recording
Data pertaining to the running of a train must be recorded and retained for the purposes of:

— | supporting systematic safety monitoring as a means of preventing incidents and accidents;
— | identifying driver, train and infrastructure performance in the period leading up to and (if appropriate) immediately after an incident or accident, to enable the identification of causes related to train driving or train equipment, and supporting the case for new or changed measures to prevent recurrence;.
— | recording information relating to the performance of both the locomotive/traction unit and the person driving.It must be possible to match recorded data to:

— | the date and time of the recording;
— | the precise geographic location of the event being recorded (distance in kilometres from a recognisable location);
— | the train identification;
— | the identity of the driver.Requirements with regard to storage, periodic evaluation of and access to this data are specified in relevant national laws of the Member State:

— | in which the railway undertaking is licensed (with regard to on-board recorded data), or
— | of the Member State in which the infrastructure is located (with regard to data recorded outside the train).4.2.3.5.1. Recording of supervision data outside the trainAs a minimum, the infrastructure manager must record the following data:

— | the failure of line-side equipment associated with the movement of trains (signalling, points etc.);
— | the detection of an overheating axle bearing, where this equipment is provided;
— | communication between the train driver and infrastructure manager’s staff authorising train movements.4.2.3.5.2. Recording of supervision data on-board the trainAs a minimum, the railway undertaking must record the following data:

— | the passing of signals at danger or ‘end of movement authority’ without authority;
— | application of the emergency brake;
— | speed at which the train is running;
— | any isolation or overriding of the on-board train control (signalling) systems;
— | operation of the audible warning device (horn);
— | operation of door controls (release, closure);
— | detection by on-board hot axle box detectors, if fitted;
— | identity of the cab for which data is being recorded to be checked.4.2.3.6. Degraded operation
4.2.3.6.1. Advice to other usersThe infrastructure manager in conjunction with the railway undertaking(s) must define a process to immediately inform each other of any situation that impedes the safety, performance and/or the availability of the rail network or rolling stock.
4.2.3.6.2. Advice to train driversIn any case of degraded operation associated with the infrastructure manager’s area of responsibility, the infrastructure manager must give formal instructions to drivers on what measures to take in order to safely overcome the degradation.
4.2.3.6.3. Contingency arrangementsThe infrastructure manager in conjunction with all the railway undertakings operating over his infrastructure, and neighbouring infrastructure managers as appropriate, must define, publish and make available appropriate contingency measures and assign responsibilities based on the requirement to reduce any negative impact as a result of degraded operation.
The planning requirements and the response to such events must be proportional to the nature and potential severity of the degradation.
These measures, which must as a minimum include plans for recovering the network to ‘normal’ status, may also address:

— | rolling stock failures (for example, those which could result in substantial traffic disruption, the procedures for rescuing failed trains);
— | infrastructure failures (for example, when there has been a failure of the electric power or the conditions under which trains may be diverted from the booked route);
— | extreme weather conditions.The infrastructure manager must establish and keep updated contact information for key infrastructure manager and railway undertaking staff who may be contacted in the event of service disruption leading to degraded operation. This information must include contact details both during and outside office hours.
The railway undertaking must submit this information to the infrastructure manager and advise the infrastructure manager of any changes to these contact details.
The infrastructure manager must advise all the railway undertaking(s) of any changes to his details.
4.2.3.7. Managing an emergency situation
The infrastructure manager must, in consultation with:

— | all railway undertakings operating over his infrastructure, or, where appropriate, representative bodies of railway undertakings operating over his infrastructure;
— | neighbouring infrastructure managers, as appropriate;
— | local authorities, representative bodies of the emergency services (including fire fighting and rescue) at either local or national level, as appropriate.define, publish and make available appropriate measures to manage emergency situations and restore the line to normal operation.
Such measures shall typically cover:

— | collisions,
— | fires on train,
— | evacuation of trains,
— | accidents in tunnels,
— | incidents involving dangerous goods,
— | derailments.The railway undertaking must provide the infrastructure manager with any specific information in respect to these circumstances, especially in respect to the recovery or re-railing of their trains.
Additionally, the railway undertaking must have processes to inform passengers about on-board emergency and safety procedures.
4.2.3.8. Aid to train crew in the event of an incident or of a major rolling stock malfunction
The railway undertaking must define appropriate procedures to assist the train crew in degraded situations in order to avoid or decrease delays caused by technical or other failures of the rolling stock (for example, lines of communication, measures to be taken in case of evacuation of a train).
4.3. Functional and technical specifications of the interfaces
In the light of the essential requirements set out in Chapter 3, the functional and technical specifications of the interfaces are as follows:
4.3.1. Interfaces with the infrastructure TSIs

Reference operation TSI | | Reference conventional rail infrastructure TSI |
Parameter | Point | Parameter | Point
Braking performance | 4.2.2.6.2 | Longitudinal track resistance | 4.2.7.2
Modifications to information contained in the route book | 4.1.2.2.2 | Operating rules | 4.4
Degraded operation | 4.2.3.6

Reference operation TSI | | Reference high speed rail infrastructure TSI |
Parameter | Point | Parameter | Point
Staff and trains | 2.2.1 | Professional competences | 4.64.3.2. Interfaces with the control-command and signalling TSI

Reference operation TSI | | Reference control-command and signalling TSI |
Parameter | Point | Parameter | Point
Rule book | 4.2.1.2.1 | Track-side train detection systems | 4.2.10
Operating rules | 4.4 | Operating rules | 4.4
Signal and lineside marker sighting | 4.2.2.8 | Visibility of track-side control-command and signalling objects | 4.2.15
Braking performance | 4.2.2.6 | Train braking performance and characteristics | 4.2.2
Train running number | 4.2.3.2.1 | ETCS DMI | 4.2.12
GSM-R DMI | 4.2.13
Data recording on-board | 4.2.3.5 | Interface to data recording for regulatory purposes | 4.2.144.3.3. Interfaces with the rolling stock TSI
4.3.3.1. Interfaces with TSI on locomotives and passenger rolling stock TSI

Reference operation TSI | | Reference conventional rail locom. and pass. TSI |
Parameter | Point | Parameter | Point
Contingency arrangements | 4.2.3.6.3 | Rescue coupling | 4.2.2.2.4
Train composition | 4.2.2.5 | Interface with infrastructure: axle load and wheel load | 4.2.3.2
Minimum requirements of the braking system | 4.2.2.6.1 | Braking performance | 4.2.4.5
Train visibility | 4.2.2.1 | External lights | 4.2.7.1
Train audibility | 4.2.2.2 | Horn | 4.2.7.2
Signal sighting | 4.2.2.8 | External visibility | 4.2.9.1.3
Optical characteristics of the windscreen | 4.2.9.2.2
Internal lighting | 4.2.9.1.8
Driver vigilance | 4.2.2.9 | Driver’s activity control function | 4.2.9.3.1
Data recording | 4.2.3.5.2 | Recording device | 4.2.9.64.3.3.2. Interfaces with TSI on freight wagons

Reference operation TSI | | Reference conventional freight wagon TSI |
Parameter | Point | Parameter | Point
Rear end | 4.2.2.1.3.2 | Attachment devices for rear-end signal | 4.2.6.3
Rear end | 4.2.2.1.3.2 | Rear-end signal | Annex E
Train composition | 4.2.2.5 | Gauging | 4.2.3.1
Train composition | 4.2.2.5 | Compatibility with load carrying capacity of lines | 4.2.3.2
Contingency arrangements | 4.2.3.6.3 | Lifting and jacking | 4.2.2.2
Train braking | 4.2.2.6 | Brake | 4.2.44.3.3.3. Interfaces with TSI on high-speed rolling stock

Reference operation TSI | | Reference high speed rolling stock TSI |
Parameter | Point | Parameter | Point
Train composition | 4.2.2.5 | Minimum braking performance | 4.2.4.1
Minimum requirements of the braking system | 4.2.2.6.1 | Brake system requirements | 4.2.4.3
Braking performance | 4.2.2.6.2
Braking performance | 4.2.2.6.2 | Eddy current brakes | 4.2.4.5
Braking performance | 4.2.2.6.2 | Protection of an immobilised train | 4.2.4.6
Braking performance | 4.2.2.6.2 | Brake performance on steep gradients | 4.2.4.7
Informing the driver in real time | 4.2.1.2.2.3
Requirements for passenger vehicles | 4.2.2.4 | Access | 4.2.2.4
Passenger alarm | 4.2.5.3
Emergency exits | 4.2.7.1
Front end | 4.2.2.1.2 | Front and rear lights | 4.2.7.4.1
Rear end | 4.2.2.1.3 | Front and rear lights | 4.2.7.4.1
Train audibility | 4.2.2.2 | horns | 4.2.7.4.2
Signal sighting and lineside marker sighting | 4.2.2.8 | Windscreen and front of the train | 4.2.2.7
Driver vigilance | 4.2.2.9 | Driver’s vigilance device | 4.2.7.8
Train composition | 4.2.2.5 | End couplers and coupling arrangements to rescue trains | 4.2.2.2
Contingency arrangements | 4.2.3.6.3
Managing and emergency situation | 4.2.3.7 | Coupler | Annex K
Maximum train length | 4.2.3.5
Degraded operation | 4.2.3.6 | Axle bearing health monitoring | 4.2.3.3.2
Rolling stock dynamic behaviour | 4.2.3.4
Sanding | Appendix B (C1) | sanding | 4.2.3.10
Train crew knowledge of rolling stock functionality | 4.2.2.5 | Design of train | 4.2.1.2
Appendix J | Monitoring and diagnostic concepts | 4.2.7.10
Contingency arrangements | 4.2.3.6.3 | End couplers and coupling arrangements to rescue trains | 4.2.2.2
Managing an emergency situation | 4.2.3.7 | coupler | Annex K
Degraded operation | 4.2.3.6 | Emergency measures | 4.2.7.1
Managing an emergency situation | 4.2.3.7 | Fire safety | 4.2.7.2
Recording of supervision data on-board the train | 4.2.3.5.2 | Monitoring and diagnostic concepts | 4.2.7.10
Informing the driver in real time | 4.2.1.2.2.3 | Ballast pick up | 4.2.3.11
Train composition | 4.2.2.5 | Environmental conditions | 4.2.6.1
Informing the Infrastructure Manager of the train’s operational status | 4.2.3.3.2.
Informing the driver in real time | 4.2.1.2.2.3 | Crosswind | 4.2.6.3
Degraded operation | 4.2.3.6
Informing the driver in real time | 4.2.1.2.2.3 | Maximum pressure variations in tunnels | 4.2.6.4
Degraded operation | 4.2.3.6
Managing an emergency situation | 4.2.3.7 | Exterior noise | 4.2.6.5
Managing an emergency situation | 4.2.3.7 | Fire safety | 4.2.7.2
Managing an emergency situation | 4.2.3.7 | Lifting/rescue procedures | 4.2.7.5
Recording of supervision data on-board the train | 4.2.3.5.2 | Particular specification for tunnels | 4.2.7.11
Appendix J
Preparation of the route book | 4.2.1.2.2.1 | Emergency lighting systems | 4.2.7.12
Managing an emergency situation | 4.2.3.7
Auxiliary staff | 4.6.3.2.3.3
Train composition | 4.2.2.5 | Traction performance requirements | 4.2.8.1
Informing the Infrastructure Manager of the train’s operational status | 4.2.3.3.2
Informing the Infrastructure Manager of the train’s operational status | 4.2.3.3.2 | Traction wheel/rail adhesion requirements | 4.2.8.2
Degraded operation | 4.2.3.6
Description of the line and relevant lineside equipment associated with the lines worked over | 4.2.1.2.2
Degraded operation | 4.2.3.6 | Functional and technical specification related to the electric power supply | 4.2.8.3
Description of the line and relevant lineside equipment associated with the lines worked over | 4.2.1.2.24.3.4. Interfaces with the Energy TSI

Reference operation TSI | | Reference conventional rail energy TSI |
Parameter | Point | Parameter | Point
Description of the line and the relevant lineside equipment associated with the lines worked over | 4.2.1.2.2 | Management of power supply | 4.4.2
Informing the driver in real time | 4.2.1.2.2.3
Modifications to information contained within the route book | 4.2.1.2.2.2 | Execution of works | 4.4.3

Reference operation TSI | | Reference high speed rail energy TSI |
Parameter | Point | Parameter | Point
Staff and trains | 2.2.1 | Professional competences | 4.64.4. Operating rules
The rules and procedures enabling coherent operation of new and different structural subsystems intended to be used in the European rail system, and in particular those that are linked directly to the operation of a new control-command and signalling system, must be identical where identical situations exist.
To this end, the operating rules for the European Rail Traffic Management System (ERTMS/ETCS) and for ERTMS/GSM-R radio system are specified in Appendix A.
Other operating rules, which are able to be standardised across the European rail system, will be specified in Appendix B.
4.5. Maintenance rules
Not applicable.
4.6. Professional qualifications
In accordance with point 2.2.1 of this TSI, this point deals with professional and linguistic competency and the assessment process required for staff to attain this competency.
4.6.1. Professional competency
Staff of the railway undertaking and the infrastructure manager must have attained appropriate professional competency to undertake all necessary safety-related duties in normal, degraded and emergency situations. Such competency comprises professional knowledge and the ability to put this knowledge into practice.
Minimum elements relevant to professional qualification for individual tasks can be found in Appendices J and L.
4.6.1.1. Professional knowledge
Taking these appendices into account and dependant on the duties of the individual staff member concerned, the knowledge required will comprise the following:

(a) | general railway operation with particular emphasis on safety-critical activity:—principles of operation of their organisation’s safety management system;—the roles and responsibilities of the key players involved in interoperable operations;—appreciation of hazards, especially in relation to the risks involving railway operation and electric traction supply. | — | principles of operation of their organisation’s safety management system; | — | the roles and responsibilities of the key players involved in interoperable operations; | — | appreciation of hazards, especially in relation to the risks involving railway operation and electric traction supply.
— | principles of operation of their organisation’s safety management system;
— | the roles and responsibilities of the key players involved in interoperable operations;
— | appreciation of hazards, especially in relation to the risks involving railway operation and electric traction supply.
(b) | appropriate knowledge of safety-related tasks in respect to procedures and interfaces for:—lines and line-side equipment;—rolling stock;—the environment. | — | lines and line-side equipment; | — | rolling stock; | — | the environment.
— | lines and line-side equipment;
— | rolling stock;
— | the environment.4.6.1.2. Ability to put this knowledge into practice
The ability to apply this knowledge in routine, degraded and emergency situations will require staff to be fully acquainted with:

— | the method and principles for applying these rules and procedures;
— | the process for the use of line-side equipment and rolling stock, as well as any specific safety-related equipment;
— | the principles of the safety management system to avoid the introduction of any undue risk to people and process.Staff must also possess a general ability to adapt to the different circumstances an individual may encounter.
Railway undertakings and infrastructure managers are required to establish a competence management system to ensure that the individual competency of their staff involved is assessed and maintained. Additionally, training must be provided, as necessary, to ensure that knowledge and skills are kept up to date, especially in relation to weaknesses or deficiencies in system or individual performance.
4.6.2. Linguistic competency
4.6.2.1. Principles
The infrastructure manager and the railway undertaking are required to ensure that their relevant personnel are competent in the use of the communication protocols and principles set out in this TSI.
Where the operating language used by the infrastructure manager differs from that habitually used by the railway undertaking’s personnel, such linguistic and communications training must form a critical part of the railway undertaking’s overall competency management system.
Railway undertaking staff whose duties require them to communicate with staff of the infrastructure manager in connection with safety-critical matters, whether in routine, degraded or emergency situations, must have a sufficient level of knowledge in the operating language of the infrastructure manager.
4.6.2.2. Level of knowledge
The level of knowledge in the infrastructure manager’s language must be sufficient for safety purposes.

(a) | As a minimum this must comprise of the driver being able to:—send and understand all the messages specified in Appendix C to this TSI;—effectively communicate in routine, degraded and emergency situations;—complete the forms associated with the use of the Book of Forms; | — | send and understand all the messages specified in Appendix C to this TSI; | — | effectively communicate in routine, degraded and emergency situations; | — | complete the forms associated with the use of the Book of Forms;
— | send and understand all the messages specified in Appendix C to this TSI;
— | effectively communicate in routine, degraded and emergency situations;
— | complete the forms associated with the use of the Book of Forms;
(b) | Other members of the train crew whose duties require them to communicate with the infrastructure manager on safety-critical matters, must as a minimum, be able to send and understand information describing the train and its operational status.Guidance on the appropriate levels of competency is defined in Appendix E. The level of knowledge for drivers must be at least level 3. The level of knowledge for staff accompanying trains must be at least level 2.
4.6.3. Initial and on-going assessment of staff
4.6.3.1. Basic elements
Railway undertakings and infrastructure managers are required to define the assessment process for their staff.
It is recommended that account be taken of each of the following:

A. | Selection of personnel—evaluation of individual experience and competence;—evaluation of individual competence in the use of any required foreign language(s) or the aptitude to learn them. | — | evaluation of individual experience and competence; | — | evaluation of individual competence in the use of any required foreign language(s) or the aptitude to learn them.
— | evaluation of individual experience and competence;
— | evaluation of individual competence in the use of any required foreign language(s) or the aptitude to learn them.
B. | Initial professional training—analysis of training needs;—training resources;—training of the trainers. | — | analysis of training needs; | — | training resources; | — | training of the trainers.
— | analysis of training needs;
— | training resources;
— | training of the trainers.
C. | Initial assessment—basic conditions;—assessment programme, including practical demonstration;—qualification of the trainers;—deliver a certificate of competency. | — | basic conditions; | — | assessment programme, including practical demonstration; | — | qualification of the trainers; | — | deliver a certificate of competency.
— | basic conditions;
— | assessment programme, including practical demonstration;
— | qualification of the trainers;
— | deliver a certificate of competency.
D. | Competency retention—principles for retention of competency;—methods to be followed;—formalisation of the competency retention process;—assessment process. | — | principles for retention of competency; | — | methods to be followed; | — | formalisation of the competency retention process; | — | assessment process.
— | principles for retention of competency;
— | methods to be followed;
— | formalisation of the competency retention process;
— | assessment process.
E. | Refresher training—principles for on-going training (including language). | — | principles for on-going training (including language).
— | principles for on-going training (including language).4.6.3.2. Analysis of training needs
4.6.3.2.1. Development of the analysis of training needsThe railway undertaking and the infrastructure manager must undertake an analysis of training needs for their relevant staff.
This analysis must set out both scope and complexity and take into account the risks associated with the operation of trains, especially in relation to human capabilities and limitations (human factors) which may come about as a result of:

— | differences in operating practices between infrastructure managers and the risks associated with changing between these;
— | the differences between tasks, operating procedures and communication protocols;
— | any difference in the ‘operating’ language used by the infrastructure manager’s personnel;
— | local operating instructions which may include special procedures or particular equipment to be applied in certain cases, for example a specific tunnel.Guidance on the elements that should be considered can be found in the appendices referred to in point 4.6.1. As appropriate, elements of the training for staff must be put in places which take these into account.
It is possible that due to the type of operation envisaged by a railway undertaking or the nature of the network being run by an infrastructure manager, some of the elements in the appendices referred to in point 4.6.1 will not be appropriate. The analysis of training needs must document those not deemed appropriate and the reasons why.
4.6.3.2.2. Updating the analysis of training needsThe railway undertaking and the infrastructure manager must define a process for reviewing and updating their individual training needs, taking into account issues such as previous audits, system feedback and known changes to rules and procedures, infrastructure and technology.
4.6.3.2.3. Specific elements for train crew and auxiliary staff4.6.3.2.3.1. Infrastructure knowledgeThe railway undertaking must ensure that the on board staff has appropriate knowledge for the relevant infrastructure.
The railway undertaking must define the process by which knowledge of on board staff of the routes worked over is acquired and maintained. This process must be:

— | based upon the route information provided by the infrastructure manager and
— | in accordance with the process described in point 4.2.1.4.6.3.2.3.2. Knowledge of rolling stockThe railway undertaking must define the process for the acquisition and retention of traction and rolling stock knowledge by its train crew.
4.6.3.2.3.3. Auxiliary staffThe railway undertaking must make sure that the auxiliary staff (for example, catering and cleaning) not forming part of the ‘train crew’ is, in addition to their basic instruction, trained to respond to the instructions of the fully trained members of the ‘train crew’.
4.7. Health and safety conditions
4.7.1. Introduction
Staff specified in point 4.2.1 as staff performing safety-critical tasks in accordance with point 2.2 must have appropriate fitness to ensure that overall operational and safety standards are met.
Railway undertakings and infrastructure managers must set up and document the process they put in place to meet the medical, psychological and health requirements for their staff within their safety management system.
Medical examinations as specified in point 4.7.4 and any associated decisions on the individual fitness of staff must be conducted by a recognised occupational doctor.
Staff must not perform safety-critical work whilst vigilance is impaired by substances such as alcohol, drugs or psychotropic medication. Therefore, the railway undertaking and the infrastructure manager must have in place procedures to control the risk that staff attend for work under the influence of such substances, or consume such substances at work.
National rules of the Member State where a train service is operated apply with regard to defined limits of those substances.
4.7.2. Deleted
4.7.3. Deleted
4.7.4. Medical examinations and psychological assessments
4.7.4.1. Before appointment
4.7.4.1.1. Minimum content of the medical examinationMedical examinations must cover:

— | General medical examination;
— | Examinations of sensory functions (vision, hearing, colour perception);
— | Urine or blood analysis for the detection of diabetes mellitus and other conditions as indicated by the clinical examination;
— | Screening for drugs of abuse.4.7.4.1.2. Psychological assessmentThe aim of the psychological assessment is to support the railway undertaking in the appointment and management of staff who have the cognitive, psychomotor, behavioural and personality capabilities to perform their roles safely.
In determining the content of the psychological assessment the psychologist must, as a minimum, take the following criteria into account relevant to the requirements of each safety function:

(a) | Cognitive:—Attention and concentration,—Memory,—Perceptive capability,—Reasoning,—Communication. | — | Attention and concentration, | — | Memory, | — | Perceptive capability, | — | Reasoning, | — | Communication.
— | Attention and concentration,
— | Memory,
— | Perceptive capability,
— | Reasoning,
— | Communication.
(b) | Psychomotor:—Speed of reaction,—Gestured coordination. | — | Speed of reaction, | — | Gestured coordination.
— | Speed of reaction,
— | Gestured coordination.
(c) | Behavioural and personality—Emotional self-control,—Behavioural reliability,—Autonomy,—Conscientiousness. | — | Emotional self-control, | — | Behavioural reliability, | — | Autonomy, | — | Conscientiousness.
— | Emotional self-control,
— | Behavioural reliability,
— | Autonomy,
— | Conscientiousness.If the psychologist omits any of those elements, the respective decision must be justified and documented.
4.7.4.2. After appointment
4.7.4.2.1. Periodicity of periodic medical examinationsAt least one systematic medical examination must be performed:

— | Every 5 years for staff aged up to 40;
— | Every 3 years for staff aged between 41 and 62;
— | Every year for staff aged over 62.Increased periodicity of examination must be set by the occupational doctor if the state of health of the member of the staff requires so.
4.7.4.2.2. Minimum content of the periodic medical examinationIf the worker complies with the criteria required at the examination, which is carried out before practising an occupation, the periodic specialised examinations must include as a minimum:

— | General medical examination;
— | Examination of sensory functions (vision, hearing, colour perception);
— | Urine or blood analysis for the detection of diabetes mellitus and other conditions as indicated by the clinical examination;
— | Screening for drugs of abuse where clinically indicated.4.7.4.2.3. Additional medical examinations and/or psychological assessmentsBesides the periodic medical examination, an additional specific medical examination and/or psychological assessment must be performed where there is reasonable ground for doubting the medical or psychological fitness of a member of staff or reasonable suspicion of use of drugs of abuse or abuse or inappropriate use of alcohol. This would be the case especially after an incident or accident caused by human error on the part of the individual.
The employer must request a medical examination after any sickness absence exceeding 30 days. In suitable cases such an examination can be limited to an assessment by the occupational doctor based on available medical information indicating that the employee’s fitness for work has not been affected.
The railway undertaking and the infrastructure manager must put systems in place to ensure that such additional examinations and assessments are undertaken as appropriate.
4.7.5. Medical requirements
4.7.5.1. General requirements
Staff must not suffer from medical conditions or take medical treatment likely to cause:

— | Sudden loss of consciousness;
— | Impairment of awareness or concentration;
— | Sudden incapacity;
— | Impairment of balance or coordination;
— | Significant limitation of mobility.The following vision and hearing requirements must be met:
4.7.5.2. Vision requirements

— | Aided or unaided distance visual acuity: 0,8 (right eye + left eye — measured separately); minimum of 0,3 for the worse eye;
— | Maximum corrective lenses: hypermetropia + 5/myopia — 8. The occupational doctor may allow values outside this range in exceptional cases and after having sought the opinion of an eye specialist;
— | Intermediate and near vision: sufficient whether aided or unaided;
— | Contact lenses are allowed;
— | Normal colour vision: using a recognised test, such as the Ishihara, completed by another recognised test if required;
— | Vision field: normal (absence of any abnormality affecting the task to be performed);
— | Vision for both eyes: present;
— | Binocular vision: present;
— | Contrast sensitivity: good;
— | Absence of progressive eye disease;
— | Lens implants, keratotomies and keratectomies are allowed only on condition that they are checked on a yearly basis or according to a periodicity set by the occupational doctor.4.7.5.3. Hearing requirements
Sufficient hearing confirmed with tone audiogram, that is:

— | Hearing good enough to keep a phone conversation going and be able to hear alert tones and radio messages.
— | The following values given for information should be taken as guidelines:
— | The hearing deficiency must not be higher than 40 dB at 500 and 1 000 Hz;
— | The hearing deficiency must not be higher than 45 dB at 2 000 Hz for the ear with the worst air conduction of sound.4.8. Registers of infrastructure and vehicles
Due to the characteristics of the registers of infrastructure and vehicles, as defined in Articles 33, 34 and 35 of Directive 2008/57/EC, these registers are not suitable for the particular requirements of the operation and traffic management subsystem. Therefore this TSI specifies nothing in respect of these registers.
However, there is an operational requirement for certain infrastructure related data items to be made available to a railway undertaking and conversely for certain rolling stock related items to be made available to an infrastructure manager, as specified in point 4.8.1 and point 4.8.2. In both cases the data concerned must be complete and accurate.
4.8.1. Infrastructure
The requirements for the rail infrastructure related data items with regard to the operation and traffic management subsystem, and which must be made available to railway undertakings, are specified in Appendix D. The infrastructure manager is responsible for the correctness of the data.
4.8.2. Rolling stock
The following rolling stock related data items must be available to infrastructure managers. The keeper is responsible for the correctness of the data:

— | whether the vehicle is constructed from materials which can be hazardous in case of accidents or fire (for example, asbestos);
— | total length of the vehicle, including buffers if existing.5. INTEROPERABILITY CONSTITUENTS5.1. Definition
According to Article 2(f) of Directive 2008/57/EC, ‘interoperability constituents’ means ‘any elementary component, group of components, subassembly or complete assembly of equipment incorporated or intended to be incorporated into a subsystem, upon which the interoperability of the rail system depends directly or indirectly. The concept of a ‘constituent’ covers both tangible objects and intangible objects such as software’.
5.2. List of constituents
In respect to the operation and traffic management subsystem, there are no interoperability constituents.
6. ASSESSMENT OF CONFORMITY AND/OR SUITABILITY FOR USE OF THE CONSTITUENTS AND VERIFICATION OF THE SUBSYSTEM6.1. Interoperability constituents
As this TSI does not specify any interoperability constituents, no assessment arrangements are discussed.
6.2. Operation and traffic management subsystem
6.2.1. Principles
The operation and traffic management subsystem is a functional subsystem according to Annex II to Directive 2008/57/EC.
In conformity with Articles 10 and 11 of Directive 2004/49/EC, railway undertakings and infrastructure managers must demonstrate compliance with the requirements of this TSI within their safety management system when applying for any new or amended safety certificate or safety authorisation.
The common safety methods on conformity assessment require national safety authorities to set up an inspection regime to supervise and monitor the day to day compliance with the safety management system including all TSIs. It should be noted that none of the elements contained within this TSI require separate assessment by a Notified Body.
Requirements in this TSI that refer to structural subsystems and are listed in the interfaces (point 4.3) are assessed under the relevant structural TSIs.
7. IMPLEMENTATION7.1. Principles
Implementation of this TSI and conformity with the relevant points of this TSI must be determined in accordance with an implementation plan that must be drawn up by each Member State for the lines for which they are responsible.
This plan must take into account:

(a) | the specific human factors issues associated with operating any given line;
(b) | the individual operating and safety elements of each line involved; and
(c) | whether implementation of the element(s) under consideration is to be:—for all trains on the line, or not,—only for certain lines,—applicable on all lines,—applicable to all trains running on the network | — | for all trains on the line, or not, | — | only for certain lines, | — | applicable on all lines, | — | applicable to all trains running on the network
— | for all trains on the line, or not,
— | only for certain lines,
— | applicable on all lines,
— | applicable to all trains running on the network
(d) | the relationship with implementation with the other subsystems (control-command and signalling, rolling stock, etc.).At this time any specific exceptions that may be applicable should be taken into account and documented as part of the plan.
The implementation plan must take into account the various levels of potential for implementation from any of the following events, namely when:

(a) | a railway undertaking or infrastructure manager commences operations,
(b) | a renewal or upgrade to the existing operational systems of a railway undertaking or infrastructure manager is introduced,
(c) | new or upgraded infrastructure, energy, rolling stock or control-command and signalling subsystems, requiring a corresponding set of operating procedures, are put into service.It is commonly understood that the full implementation of all elements of this TSI cannot be complete until the hardware (infrastructure, control–command, etc.) that is to be operated has been harmonised. The guidelines set out in this Chapter must therefore only be seen as an interim phase supporting migration to the target system.
7.2. Implementation guidelines
There are three distinct elements to implementation:

(a) | Confirmation that any existing systems and processes comply with the requirements of this TSI;
(b) | Adaptation of any existing systems and processes to comply with the requirements of this TSI;
(c) | New systems and processes arising from implementation of other subsystems;—New/upgraded conventional lines (infrastructure/energy),—New or upgraded ETCS signalling installations, GSM-R radio installations, Hot Axle Box Detectors, … (control-command and signalling),—New rolling stock (rolling stock). | — | New/upgraded conventional lines (infrastructure/energy), | — | New or upgraded ETCS signalling installations, GSM-R radio installations, Hot Axle Box Detectors, … (control-command and signalling), | — | New rolling stock (rolling stock).
— | New/upgraded conventional lines (infrastructure/energy),
— | New or upgraded ETCS signalling installations, GSM-R radio installations, Hot Axle Box Detectors, … (control-command and signalling),
— | New rolling stock (rolling stock).7.3. Specific cases
7.3.1. Introduction
The following special provisions are permitted in the specific cases below.
These specific cases belong to two categories:

— | the provisions apply either permanently (case ‘P’), or temporarily (case ‘T’).
— | in temporary cases Member States shall conform with the relevant subsystem either by 2016 (case ‘T1’), or by 2024 (case ‘T2’).7.3.2. List of specific cases
7.3.2.1. Temporary specific case (T1) Estonia, Latvia and Lithuania
For the implementation of point 4.2.2.1.3.2 of this TSI, trains which are operated solely on the 1 520 mm gauge network of Estonia, Latvia and Lithuania may use another specified train rear end signal.
7.3.2.2. Temporary specific case (T2) Ireland and United Kingdom
For the implementation of 4.2.3.2.1 of this TSI, Ireland and United Kingdom are using alphanumeric number in the existing systems. The MS set out the requirements and time schedule for the transition from alphanumeric train running numbers to numeric train running numbers in the target system.

(1)
OJ L 315, 3.12.2007, p. 51.
(2)
OJ L 164, 30.4.2004, p. 44.
(3)
OJ L 75, 15.3.2001, p. 29.
(4)
OJ L 344, 8.12.2006, p. 1.
(5)
OJ L 84, 26.3.2008, p. 132.
(6)
OJ L 139, 26.5.2011, p. 1.
(7)
OJ L 51, 23.2.2012, p. 1.
(8)
OJ L 260, 30.9.2008, p. 13.

ERTMS/ETCS operating rules

Appendix AThe operating rules for ERTMS/ETCS and ERTMS/GSM-R are specified in the Technical Document ‘ERTMS operational principles and rules — version 2’ published on the ERA website (www.era.europa.eu).

Other rules enabling a coherent operation

Appendix BA. GENERALReserved
B. STAFF SAFETY AND SECURITYReserved
C. OPERATIONAL INTERFACE WITH SIGNALLING AND COMMAND AND CONTROL EQUIPMENTC1. Sanding
If the train is equipped with manually activated sanding device, the driver shall always be allowed to apply sand but shall avoid it wherever possible:

— | in the area of points and crossings,
— | during braking at speeds less than 20 km/h,
— | when at a standstill.The exceptions to this are

— | if there is a risk of SPAD (Signal Passed at Danger), or other serious incident and the application of sand would assist adhesion,
— | when starting away, or
— | when required to test the sanding equipment on the traction unit. (Testing shall not be undertaken in areas specifically designated in the Infrastructure Register).C2. Activation of Hot Axle Box Detectors
Reserved
D. TRAIN MOVEMENTSD1. Normal conditions
D2. Degraded conditions
Reserved
E. ANOMALIES, INCIDENTS AND ACCIDENTSReserved

Safety related communications methodology

Appendix CINTRODUCTIONThis Appendix sets out the rules for safety-related ground-to-mobile and mobile-to-ground communications applicable to information transmitted or exchanged for safety-critical situations on the interoperable network and in particular to:

— | define the nature and structure of the safety-related messages;
— | define the methodology for voice transmission of those messages.This Appendix is to serve as basis:

— | in order to enable the infrastructure manager to draw up the messages and books of forms. These elements shall be addressed to the railway undertaking at the same time as the rules and regulations are made available; for the Infrastructure Manager and the Railway Undertaking to draw up the documents for their staff (Books of Forms), instructions for staff authorising train movements and Appendix 1 to the Driver’s Rule Book ‘Manual of communication procedures’.The extent to which forms are used and their structure may vary. For some risks the use of forms will be appropriate, whilst for others it will not be appropriate.
In the context of a given risk, the Infrastructure Manager shall decide whether the use of a form is appropriate. A form should only be used if the value of its safety and performance benefits exceeds that of any safety and performance disadvantage.
The Infrastructure Managers must structure his communications protocol in a formalised way and in line with the following 3 categories:

— | urgent (emergency) verbal messages;
— | written orders;
— | additional performance messages.To support the disciplined approach to transmission of these messages a Communications Methodology has been developed.
1. COMMUNICATIONS METHODOLOGY1.1. Elements and principles of the methodology
1.1.1. Standard terminology to be used in the procedures
1.1.1.1. Speech transmission procedure
Term transferring the opportunity to speak to the opposite party:

over
1.1.1.2. Message receiving procedure

— | upon receiving a direct messageTerm confirming that the sent message has been received:receivedTerm used to have the message repeated in the event of poor reception or misunderstandingsay again (+ speak slowly)
— | upon reception of a message that has been read-backTerms used to ascertain whether a read-back message exactly matches the sent message:corrector not:error (+ I say again)1.1.1.3. Communications breaking procedure

— | if the message has ended:out
— | if break is temporary and does not break the connectionTerm used to keep the other party waiting:wait
— | if break is temporary but the connection is brokenTerm used to tell the other party that the communication is going to be broken but will be resumed later on:I call again1.1.1.4. Cancelling a written order
Term used to cancel the written order procedure underway:

cancel procedure …If the message is then subsequently to be resumed, the procedure shall be repeated from the start.
1.1.2. Principles to be applied in the event of error or misunderstanding
To permit the correction of possible errors during communication, the following rules shall be applied:
1.1.2.1. Errors

— | error during transmissionWhen a transmission error is discovered by the sender himself, the sender must request cancellation by sending the following procedure message:error (+ prepare new form…)or:error + I say againand then send the initial message again.
— | error during read-backWhen the sender discovers an error whilst the message is being read back to him, the sender shall send the following procedure messages:error + I say againand send the initial message again.1.1.2.2. Misunderstanding
If one of the parties misunderstands a message he must ask the other party to repeat the message by using the following text:

say again (+ speak slowly)
1.1.3. Word, number, time, distance, speed and date spelling code
To help understanding and expressing messages in different situations, each term must be pronounced slowly and correctly by spelling out any words or names and figures likely to be misunderstood. Examples would be the identifying codes for signals or points.
The following spelling rules shall apply:
1.1.3.1. Spelling out of words and letter groups
The International Phonetic Alphabet shall be used.

A | Alpha
B | Bravo
C | Charlie
D | Delta
E | Echo
F | Foxtrot
G | Golf
H | Hotel
I | India
J | Juliet
K | Kilo
L | Lima
M | Mike
N | November
O | Oscar
P | Papa
Q | Quebec
R | Romeo
S | Sierra
T | Tango
U | Uniform
V | Victor
W | Whisky
X | X-ray
Y | Yankee
Z | ZuluExample:
Points A B= points alpha-bravo.
Signal Number KX 835= signal Kilo X-Ray eight three five.
The Infrastructure Manager may add further letters, along with a phonetic pronunciation for each letter added, if required by the alphabet of the Infrastructure Manager’s operating language(s).
The Railway Undertaking may add further indications about pronunciation, as it deems necessary.
1.1.3.2. Expression of numbers
Numbers shall be spoken digit by digit.

0 | Zero
1 | One
2 | Two
3 | Three
4 | Four
5 | Five
6 | Six
7 | Seven
8 | Eight
9 | NineExample: train 2183 = train two-one-eight-three.
Decimals shall be expressed by the word ‘point’.
Example: 12.50 = one-two-point-five-zero
1.1.3.3. Expression of time
The time shall be given in local time, in plain language.
Example: 10:52 hours = ten fifty-two.
Whilst this is the principle, it would also be acceptable, whenever necessary, for the time to be spelled out digit by digit (one zero five two hours).
1.1.3.4. Expression of distances and speeds
Distances shall be expressed in kilometres and speeds in kilometres per hour.
Miles may be used if that unit is used on the infrastructure concerned.
1.1.3.5. Expression of dates
Dates shall be expressed in the usual manner.
Example: 10 December
1.2. Communications structure
The voice transmission of safety-related messages shall in principle comprise 2 phases as follows:

— | identification and request for instructions;
— | transmission of the message itself and termination of the transmission.The first phase may be cut back or entirely skipped for top priority safety messages.
1.2.1. Rules for identification and requests for instruction
To enable the parties to identify one another, define the operational situation and transmit procedural instructions, the following rules shall apply:
1.2.1.1. Identification
It is very important that at the beginning of each communication, other than very urgent top priority emergency messages, the persons who are going to communicate identify themselves. Drivers identify themselves by train running number and position. For communication between signaller and driver it is the signaller’s lead responsibility to ensure that the right signaller and driver are in communication. This is especially critical when communication is taking place in areas where communications boundaries overlap.
This principle shall apply even after an interruption during transmission.
The following messages shall be used for this purpose by the different parties.

— | by the staff authorising train movements:train …(number)this is … Signals(name) | train …(number)this is … Signals(name)
train …(number)this is … Signals(name)
— | by the driver:… Signals(name)this is train …(number) | … Signals(name)this is train …(number)
… Signals(name)this is train …(number)It should be noted that the identification may be followed by an additional information message giving the staff authoring train movements enough details of the situation to determine precisely the procedure that the driver may subsequently be required to follow.
1.2.1.2. Request for instructions
Every application of a procedure supported by a written order must be preceded by a request for instructions.
The following terms shall be used to request instructions:

prepare procedure …1.2.2. Rules for transmission of written orders and verbal messages
1.2.2.1. Top priority safety messages
Due to their urgent and imperative nature, these messages:

— | may be sent or received while running;
— | may skip the identification part;
— | shall be repeated;
— | shall, as soon as possible, be followed by further information.1.2.2.2. Written Orders
In order to reliably send or receive (at a standstill) the procedural messages contained in the Book of Forms, the following rules shall be followed:
1.2.2.2.1. Message sendingThe form may be completed prior to transmitting the message so that the full text of the message can be sent in one single transmission.
1.2.2.2.2. Message receivingThe receiver of the message must fill in the form contained in the Book of Forms based upon the information given by the sender.
1.2.2.2.3. Read-backAll the predetermined railway messages in the Book of Forms shall be required to be read back. The read-back shall include the message shown in the grey field on the Forms, the ‘report back’ section and any additional or complementary information.
1.2.2.2.4. Acknowledgement of correct read-backEvery read-back message shall be followed by an acknowledgement of conformity or non-conformity given by the sender of the message.

correct
or

error + I say again
followed by a repeat sending of the initial message
1.2.2.2.5. AcknowledgementEvery message received shall be acknowledged positively or negatively as follows:

received
or

negative, say again (+ speak slowly)
1.2.2.2.6. Traceability and verificationA unique identification or authorisation number shall accompany all messages initiated from the ground:

— | if the message concerns an action for which the driver requires a specific authorisation (e.g. passing a signal at danger,…):authorisation…(number) | authorisation…(number)
authorisation…(number)
— | in all other cases (e.g. proceeding with caution,…):message…(number) | message…(number)
message…(number)1.2.2.2.7 Reporting BackEvery message comprising a request to ‘report back’ shall be followed by a ‘report’.
1.2.2.3. Additional messages
Additional messages

— | shall be preceded by the identification procedure;
— | shall be short and precise (limited wherever possible to information to be communicated and where it applies);
— | shall be read back and followed by an acknowledgement of correct read-back, or not
— | may be followed by a request for instructions or a request for further information.1.2.2.4. Information messages with a variable non-predetermined content
Information messages with a variable content shall be:

— | preceded by the identification procedure;
— | prepared before sending;
— | read back and followed by an acknowledgement of correct read-back, or not.2. PROCEDURAL MESSAGES2.1. Nature of the messages
Procedural messages are used to send operational instructions associated with appropriate situations represented in the Driver’s Rule Book.
They comprise the text of the message itself, corresponding to a situation, and a number identifying the message.
If the message requires the recipient to report back, the text of the report is also given.
These messages use predetermined wording prescribed by the Infrastructure Manager in his ‘operating language’ and they are presented in the form of pre-prepared forms in either paper format or in computer medium.
2.2. Forms
Forms are a formalised medium for communicating procedural messages. These messages are generally those associated with degraded working conditions. Typical examples would be the authority for a driver to pass a signal or an ‘end of movement authority’, the requirement to run at reduced speed in a particular area, or to examine the line. There may well be other circumstances that will require the use of such messages.
Their purpose is to:

— | provide a common working document used in real-time by the staff authorising train movements and by the drivers;
— | provide the driver (especially when working in an unfamiliar or rare environment) with a reminder of the procedure he will required to follow;
— | enable traceability of communications.In order to identify the forms, a unique code word or number relating to the procedure shall be developed. This could be based on the potential frequency that a form would be used. If, of all the forms being developed, the likelihood is that the one most often used is the one for passing a signal or EOA at danger, then this one could be numbered 001 and so on.
2.3. Book of Forms
Having identified all the forms to be used, the whole set must be collected into a document or a computer medium called the Book of Forms.
It is a joint document that will be used by the driver and the staff authorising the movement of trains when they communicate with each other. It is important therefore that the book used by the driver and the one used by the staff authorising the movement of trains are constructed and numbered in the same manner.
The Infrastructure Manager is responsible for drawing up the Book of Forms and the forms themselves in his ‘operating language’.
The language to be used when transmitting the messages shall always be the ‘operating language’ of the Infrastructure Manager.
The Book of Forms shall comprise two parts.
The first part contains the following items:

— | a reminder about the utilisation of the Book of Forms;
— | an index of ground-originated Procedure Forms;
— | an index of driver-originated Procedure Forms, where appropriate;
— | the list of situations cross-referencing to which procedure form is to be used;
— | a glossary giving the situations to which each procedure form applies;
— | the code for spelling out messages (phonetic alphabet etc.).The second part contains the Procedure Forms themselves. These must be collected by the RU and given to the driver.
3. ADDITIONAL MESSAGESAdditional messages are information messages used to inform about situations of a rare nature and for which therefore a pre-determined form is considered unnecessary, or related to train running or to the technical condition of the train or the infrastructure, either;

— | by the driver to inform the staff authorising train movements, or
— | by the staff authorising train movements to advise the driverTo make it easier to describe the situations and construct the information messages, message guidelines, a glossary of railway terminology, a descriptive diagram of the rolling stock being employed and a descriptive statement of the infrastructure equipment (track, traction supply, etc.) may be beneficial.
3.1. Guideline structure for messages
These messages may be structured along the following lines:

Stage in the communication flow | Message element
Reason for passing the information | for informationfor action |  | for information |  | for action
 | for information
 | for action
Observation | There isI sawI hadI hit |  | There is |  | I saw |  | I had |  | I hit
 | There is
 | I saw
 | I had
 | I hit
Position |
—along the line | — | along the line | at …(station name)…(characteristic point)at mile post/kilometre point …(number) |  | at …(station name) |  | …(characteristic point) |  | at mile post/kilometre point …(number)
— | along the line
 | at …(station name)
 | …(characteristic point)
 | at mile post/kilometre point …(number)
—in respect to my train | — | in respect to my train | power car …(number)trailer car …(number) |  | power car …(number) |  | trailer car …(number)
— | in respect to my train
 | power car …(number)
 | trailer car …(number)
Nature—object—person | — | object | — | person | …(see glossary)
— | object
— | person
State |
—static | — | static | standing onlying onfallen on |  | standing on |  | lying on |  | fallen on
— | static
 | standing on
 | lying on
 | fallen on
—moving | — | moving | walkingrunningtowards |  | walking |  | running |  | towards
— | moving
 | walking
 | running
 | towards
Location with respect to the tracks | These messages may be followed by a request for instructions.
The elements of the messages are provided in both the language chosen by the Railway Undertaking and in the operating language(s) of the Infrastructure Managers concerned.
3.2. Glossary of Railway Terminology
The Railway Undertaking shall produce a glossary of railway terminology for each network over which his trains operate. It shall supply the terms in regular use in the language chosen by the Railway Undertaking and in the ‘operating’ language of the Infrastructure Manager(s) whose infrastructure is worked over.
The glossary shall be composed of two parts:

— | a listing of terms by subject matter;
— | a listing of the terms in alphabetical order.3.3. Descriptive diagram of the rolling stock
If the Railway Undertaking feels it would benefit his operation a descriptive diagram of the rolling stock used shall be prepared. It shall list the names of the various components that may be the subject of communications with the different Infrastructure Managers concerned and include the common names for the standard terms in the language chosen by the Railway Undertaking and in the ‘operating’ language of the Infrastructure Manager(s) whose infrastructure is worked over.
3.4. Descriptive statement of the characteristics of the infrastructure equipment (track, traction supply, etc.)
If the Railway Undertaking feels it would benefit his operation a descriptive statement of the characteristics of the infrastructure equipment (track, traction supply, etc.) on the route worked over shall be prepared. This shall show the names of the various components that may be the subject of communications with the Infrastructure Manager(s) concerned. It shall include the common names for the standard terms in the language chosen by the Railway Undertaking and in the ‘operating’ language of the Infrastructure Manager(s) whose infrastructure is worked over.
4. TYPE AND STRUCTURE OF VERBAL MESSAGES4.1. Emergency messages
Emergency messages are intended to give urgent operational instructions that are directly linked with the safety of the railway.
To avoid any risk of misunderstanding, messages must always be repeated once.
Classified according to need, the main messages which can be sent are indicated hereafter.
The Infrastructure Manager may, in addition, define other emergency messages according to the needs of his operation.
Emergency messages may be followed by a Written Order (see Subsection 2).
The type of text that goes to form Emergency messages must be included in Appendix 1 ‘Manual of communications procedures’ to the Driver’s Rule Book and in the documentation issued to staff authorising train movements.
4.2. Messages sent either by the ground or the driver

| (a) | Need to stop all trains:The need to stop all trains must be transmitted by means of an acoustic signal; if this is not available the following phrase must be used:Emergency, stop all trainsInformation on location or area is, if necessary, specified in the message.In addition, this message is to be quickly complemented, if possible, by the reason, the location of the emergency and the train’s identification:ObstructionOr FireOr…(other reason)on line…at…(name) (km)Driver of train…(number) | ObstructionOr FireOr…(other reason)on line…at…(name) (km)Driver of train…(number)
ObstructionOr FireOr…(other reason)on line…at…(name) (km)Driver of train…(number)
| (b) | Need to stop a particular train:Train…(on line/track)(number) (name/number)In this circumstance the name or number of the line or track on which the train is running may be used to complement the message. | Train…(on line/track)(number) (name/number)
Train…(on line/track)(number) (name/number)4.3. Messages issued by the driver
Need to cut the traction power supply:

Emergency current isolation
This message is to be quickly complemented, if possible, by the reason, the location of the emergency and the train’s identification:

At…(km)on…line/track(name/number)between…and…(station) (station)Reason…Driver of train…(number)In this circumstance the name or number of the line or track on which the train is running may be used to complement this message.

Information to which the Railway Undertaking must have access in connection with the route(s) over which he intends to operate

Appendix DPART 1. GENERIC INFORMATION REGARDING THE INFRASTRUCTURE MANAGER1.1. Name (s)/Identity of Infrastructure Manager(s)1.2. Country (or Countries)1.3. Brief description1.4. List of general operational rules and regulations (and how to obtain them)PART 2. MAPS AND DIAGRAMS2.1. Geographic map2.1.1. Routes2.1.2. Principal locations (stations, yards, junctions, freight terminals)2.2. Line diagramInformation to be included on diagrams, supplemented as necessary by text. Where a separate station/yard/depot diagram is provided then information on line diagram may be simplified
2.2.1. Indication of distance2.2.2. Identification of running lines, loops, sidings and catch/trap points2.2.3. Connections between running lines2.2.4. Principal locations (stations, yards, junctions, freight terminals)2.2.5. Location and meanings of all fixed signals2.3. Station/Yard/Depot diagrams (N.B. applies only to locations available to interoperable traffic)Information to be identified on location specific diagrams, supplemented as necessary by text
2.3.1. Name of location2.3.2. Location identity code2.3.3. Type of location (passenger terminal, freight terminal, yard, depot)2.3.4. Location and meanings of all fixed signals2.3.5. Identification and plan of tracks, including catch/trap points2.3.6. Identification of platforms2.3.7. Length of platforms2.3.8. Height of platforms2.3.9. Identification of sidings2.3.10. Length of sidings2.3.11. Availability of shore electric supply2.3.12. Distance between the edge of the platform and the centre of the track, parallel to the running surface2.3.13. (For passenger stations) Availability of access for disabled personsPART 3. SPECIFIC LINE SEGMENT INFORMATION3.1. General Characteristics3.1.1. Country3.1.2. Line segment identification code: national code3.1.3. Line segment extremity 13.1.4. Line segment extremity 23.1.5. Times of opening for traffic (times, days, special arrangements for holidays)3.1.6. Lineside indications of distance (frequency, appearance and positioning)3.1.7. Type of traffic (mixed, passenger, freight, …)3.1.8. Maximum permissible speed(s)3.1.9. Any other information which is necessary for safety reasons3.1.10. Specific local operational requirements (including any special staff qualifications)3.1.11. Special restrictions for dangerous goods3.1.12. Special loading restrictions3.1.13. Model of temporary works notice (and way to obtain it)3.1.14. Indication that Line segment is congested (Article 22 of Directive 2001/14/EC)3.2. Specific Technical Characteristics3.2.1. EC verification for Infrastructure TSI3.2.2. Date of putting into service as an interoperable line3.2.3. List of possible specific cases3.2.4. List of possible specific derogations3.2.5. Track gauge3.2.6. Structure gauge3.2.7. Maximum axle load3.2.8. Maximum load per linear metre3.2.9. Transversal track forces3.2.10. Longitudinal track forces3.2.11. Minimum radius of curvature3.2.12. Gradient percentage3.2.13. Gradient location3.2.14. For brake system that does not use wheel-rail adhesion, accepted braking effort3.2.15. Bridges3.2.16. Viaducts3.2.17. Tunnels3.2.18. Comments3.3. Energy subsystem3.3.1. EC verification for Energy TSI3.3.2. Date of putting into service as an interoperable line3.3.3. List of possible specific cases3.3.4. List of possible specific derogations3.3.5. Type of power supply system (e.g. none, overhead, 3rd rail)3.3.6. Power supply system frequency (e.g. AC, DC)3.3.7. Minimum voltage3.3.8. Maximum voltage3.3.9. Restriction related to power consumption of specific electric traction unit(s)3.3.10. Restriction related to the position of Multiple Traction unit(s)s to comply with contact line separation (position of pantograph)3.3.11. How to obtain electrical isolation3.3.12. Contact wire height3.3.13. Permissible contact wire gradient in relation to the track and the variation of the gradient3.3.14. Type of pantographs approved3.3.15. Minimum static force3.3.16. Maximum static force3.3.17. Location of neutral sections3.3.18. Information on operation3.3.19. Lowering of pantographs3.3.20. Conditions applying with regard to regenerative braking3.3.21. Maximum allowable train current3.4. Control-Command and Signalling subsystem3.4.1. EC verification for CCS TSI3.4.2. Date of putting into service as an interoperable line3.4.3. List of possible specific cases3.4.4. List of possible specific derogationsERTMS/ETCS
3.4.5. Level of application3.4.6. Optional functions installed lineside3.4.7. Optional functions required on board3.4.8. Software version number3.4.9. Placing-in-service date of this versionERTMS/GSM-R radio
3.4.10. Optional functions as specified in FRS3.4.11. Version number3.4.12. Placing-in-service date of this versionFor ERTM/ETCS level 1 with infill function
3.4.13. Technical implementation required for rolling stockClass B train protection, control and warning system(s)
3.4.14. National rules for operating class B systems (+ way to obtain them)Line system
3.4.15. Responsible Member State3.4.16. System name3.4.17. Software Version number3.4.18. Placing-in-service date of this version3.4.19. End of period of validity3.4.20. Need for more than one system active simultaneously3.4.21. On-board systemClass B radio system
3.4.22. Responsible Member State3.4.23. System name3.4.24. Version number3.4.25. Placing-in-service date of this version3.4.26. End of period of validity3.4.27. Special conditions to switch over between different class B train protection, control and warning systems3.4.28. Special technical conditions required to switch over between ERTMS/ETCS and Class B Systems3.4.29. Special conditions to switch over between different radio systemsTechnical degraded modes of:
3.4.30. ERTM/ETCS3.4.31. Class B train protection, control and warning system3.4.32. ERTM/GSM-R3.4.33. Class B radio system3.4.34. Lineside signallingSpeed restrictions related to braking performance
3.4.35. ERTM/ETCS3.4.36. Class B train protection, control and warning systemsNational rules for functioning Class B system
3.4.37. National rules linked to braking performance3.4.38. Other national rules, e.g.: data corresponding with UIC leaflet 512 (8th edition of 1.1.79 and 2 Amendments)EMC Susceptibility of infrastructure-side Control-command and signalling
3.4.39. Requirement to be specified according to European Standards3.4.40. Permissibility to use Eddy-current brake3.4.41. Permissibility to use magnetic brake3.4.42. Requirements for technical solutions concerning implemented derogations3.5. Traffic Operation and Management Subsystem3.5.1. EC verification for OPE TSI3.5.2. Date of putting into service as an interoperable line3.5.3. List of possible specific cases3.5.4. List of possible specific derogations3.5.5. Language used for safety-critical communications with infrastructure manager staff3.5.6. Special climatic conditions and associated arrangements

Language and communication level

Appendix EThe oral qualification in a language can be subdivided into five levels:

Level | Description
5 | —can adapt the way he/she speaks to any interlocutor—can put forward an opinion—can negotiate—can persuade—can give advice | — | can adapt the way he/she speaks to any interlocutor | — | can put forward an opinion | — | can negotiate | — | can persuade | — | can give advice
— | can adapt the way he/she speaks to any interlocutor
— | can put forward an opinion
— | can negotiate
— | can persuade
— | can give advice
4 | —can cope with totally unforeseen situations—can make assumptions—can express an argued opinion | — | can cope with totally unforeseen situations | — | can make assumptions | — | can express an argued opinion
— | can cope with totally unforeseen situations
— | can make assumptions
— | can express an argued opinion
3 | —can cope with practical situations involving an unforeseen element—can describe—can keep a simple conversation going | — | can cope with practical situations involving an unforeseen element | — | can describe | — | can keep a simple conversation going
— | can cope with practical situations involving an unforeseen element
— | can describe
— | can keep a simple conversation going
2 | —can cope with simple practical situations—can ask questions—can answer questions | — | can cope with simple practical situations | — | can ask questions | — | can answer questions
— | can cope with simple practical situations
— | can ask questions
— | can answer questions
1 | —can talk using memorised sentences | — | can talk using memorised sentences
— | can talk using memorised sentences

Appendix FNot used
Appendix GNot used
Appendix HNot used
Appendix INot used

Minimum elements relevant to professional qualification for the tasks associated with ‘accompanying trains’

Appendix J1. GENERAL REQUIREMENTS
| (a) | This Appendix, which must be read in conjunction with points 4.6 and 4.7 is a list of the elements that are deemed to be relevant to the task of accompanying a train on the network.
| (b) | The expression ‘professional qualification’, when taken within the context of this TSI, refers to those elements that are important to ensuring that operational staff are trained and able to understand and discharge the elements of the task.
| (c) | Rules and procedures apply to the task being performed and to the person carrying out the task. These tasks may be carried out by any authorised qualified person irrespective of any name, job title or grade used in rules or procedures or by the individual company.
| (d) | Any authorised qualified person must carry out all rules and procedures related to the task being performed.2. PROFESSIONAL KNOWLEDGEAny authorisation requires a successfully passed initial examination and provisions for ongoing assessment and training as described in point 4.6.
2.1. General professional knowledge

| (a) | General principles of safety management within the railway system, relevant to the task, including interfaces with other subsystems
| (b) | General conditions relevant to the safety of passengers or cargo and persons on or about the railway track
| (c) | Conditions of health and safety at work
| (d) | General principles of security of the railway system
| (e) | Personal safety including when leaving the train on the running line2.2. Knowledge of operational procedures and safety systems applied to the infrastructure to be used

| (a) | Operational procedures and safety rules
| (b) | Control-command and signalling system
| (c) | Communications principles and formalised messaging procedure including use of communication equipment2.3. Knowledge of rolling stock

| (a) | Passenger vehicle interior equipment
| (b) | Repairing minor defects within the passenger areas of rolling stock, as required by the Railway Undertaking2.4. Knowledge of the route

| (a) | Operational arrangements (such as the method of train despatch) at individual locations (signalling, station equipment etc.)
| (b) | Stations at which passengers may alight or join
| (c) | Local operating and emergency arrangements specific to the line(s) of route3. ABILITY TO PUT THE KNOWLEDGE INTO PRACTICE
| (a) | Checks before departure, including brake tests and correct closure of the doors
| (b) | Departure processes
| (c) | Communication with passengers especially in relation to circumstances involving passenger safety
| (d) | Degraded operations
| (e) | Assess the potential of a defect within the passenger areas and react according to rules and procedures
| (f) | Protection and warning measures as required by the rules and regulations or in assistance to the driver
| (g) | Train evacuation and passenger safety especially if they are required to be on or near the line
| (h) | Communicate with the Infrastructure Manager’s staff when assisting the driver or during an evacuation incident
| (i) | Report any unusual occurrences concerning the operation of the train, the condition of the rolling stock and the safety of passengers. If required these reports must be made in writing, in the language chosen by the Railway Undertaking.

Appendix KNot used

Minimum elements relevant to professional qualification for the task of preparing trains

Appendix L1. GENERAL REQUIREMENTSThis Appendix, which must be read in conjunction with point 4.6, gives a list of the elements that are deemed to be relevant to the task of preparing a train on the network.

(a) | The expression ‘professional qualification’, when taken within the context of this TSI, refers to those elements that are important to ensuring that operational staff are trained and able to understand and discharge the elements of the task.
(b) | Rules and procedures apply to the task being performed and to the person carrying out the task. These tasks may be carried out by any authorised qualified person irrespective of any name, job title or grade used in rules or procedures or by the individual company.
(c) | Any authorised qualified person must follow all rules and procedures related to the task being performed.2. PROFESSIONAL KNOWLEDGEAny authorisation requires a successfully passed initial examination and provisions for ongoing assessment and training as described in point 4.6.
2.1. General professional knowledge

| (a) | General principles of safety management within the railway system, relevant to the task, including interfaces with other subsystems
| (b) | General conditions relevant to the safety of passengers and/or cargo including the carriage of dangerous goods and exceptional loads
| (c) | Conditions of health and safety at work
| (d) | General principles of security of the railway system
| (e) | Personal safety when on or in the vicinity of rail lines
| (f) | Communications principles and formalised messaging procedure including use of communication equipment2.2. Knowledge of operational procedures and safety systems applied to the infrastructure to be used

| (a) | Working of trains in normal, degraded and emergency conditions
| (b) | Operational procedures at individual locations (signalling, station/depot/yard equipment) and safety rules
| (c) | Local operating arrangements2.3. Knowledge of train equipment

| (a) | Purpose and use of wagon and vehicle equipment
| (b) | Identification of and arranging for technical inspections3. ABILITY TO PUT THE KNOWLEDGE INTO PRACTICE
| (a) | Application of train composition rules, train braking rules, train loading rules etc. to ensure the train is in running order
| (b) | Understanding of marking and labels on vehicles
| (c) | Process for determining and making train data available
| (d) | Communication with train crew
| (e) | Communication with staff responsible for controlling the movement of trains
| (f) | Degraded operations especially as it affects the preparation of trains
| (g) | Protection and warning measures as required by the rules and regulations or local arrangements at the location in question
| (h) | Actions to be taken in respect to incidents involving the carriage of dangerous goods (where relevant)

Appendix MNot used
Appendix NNot used
Appendix ONot used

European Vehicle Number and linked alphabetical marking on the bodywork

Appendix P1. GENERAL PROVISIONS ON THE EUROPEAN VEHICLE NUMBERThe European Vehicle Number is assigned according to the codes as defined in Decision 2007/756/EC, Appendix 6.
The European Vehicle Number shall be changed when it does not reflect the interoperability capability or technical characteristics according to this Appendix due to technical modifications of the vehicle. Such technical modifications may require a new placing in service according to Articles 20 to 25 of Directive 2008/57/EC.
2. GENERAL ARRANGEMENTS FOR EXTERNAL MARKINGSThe capital letters and figures making up the marking inscriptions shall be at least 80 mm in height, in a sans serif font type of correspondence quality. A smaller height may only be used where there is no option but to place the marking on the sole bars.
The marking is put not higher than 2 metres above rail level.
The keeper can add, in letters of larger size than the European Vehicle Number, an own number marking (consisting generally of digits of the serial number supplemented by alphabetical coding) useful in operations. The place where the own number is marked is left to the choice of the keeper; however it must always be possible to distinguish easily the European Vehicle Number from the keeper’s own number marking.
3. WAGONSThe marking shall be inscribed on the wagon bodywork in the following manner:

23. | TEN
80 | D-RFC
7369 553-4
Zcs
31. | TEN
80 | D-DB
0691 235-2
Tanoos
33. | TEN
84 | NL-ACTS
4796 100-8
SlpssWhere in the examples

| D and NL stand for the registering Member State as set out in NVR-decision 2007/756/EC, Appendix 6, part 4.
| RFC, DB and ACTS stand for the keeper marking as set out in NVR-decision 2007/756/EC, Appendix 6, part 1.For wagons whose bodywork does not offer a large enough area for this type of arrangement, particularly in the case of flat wagons, the marking shall be arranged as follows:

0187 | 3320 | 644-7
TEN | F-SNCF | KsWhen one or more index letters with a national definition are inscribed on a wagon, this national marking must be shown after the international letter marking and separated from it by a hyphen as follows:

0187 | 3320 | 644-7
TEN | F-SNCF | Ks-xy4. COACHES AND HAULED PASSENGER STOCKThe number shall be applied to each sidewall of the vehicle in the following manner:

F-SNCF | 61 8720 – 72 021– 7
| B10tuThe marking of the country in which the vehicle is registered and of the technical characteristics are printed directly in front of, behind or under the European Vehicle number.
In case of coaches with driver’s cabin, the European Vehicle number is also written inside the cabin.
5. LOCOMOTIVES, POWER CARS AND SPECIAL VEHICLESThe European Vehicle Number must be marked on each sidewall of the tractive stock in the following manner:
92 10 1108 062-6
The European Vehicle Number is also written inside each cabin of the tractive rolling stock.
6. ALPHABETICAL MARKING OF THE INTEROPERABILITY CAPABILITY‘TEN’: Vehicle which:

(a) | complies with all relevant TSIs which are in force at the moment of placing in service and has been authorised to be placed in service according to Article 22(1) of Directive 2008/57/EC, and
(b) | is provided with an authorisation valid in all Member States in accordance with Article 23(1) of Directive 2008/57/EC.‘PPV/PPW’: Vehicle which complies with PPV/PPW or PGW agreement (inside OSJD States). (original: PPV/PPW: ППВ (Правила пользования вагонами в международном сообщении); PGW: Правила Пользования Грузовыми Вагонами).
Vehicles which are not authorised to be placed in service in all Member States in accordance with Article 23(1) of Directive 2008/57/EC need a marking indicating the Member States where the vehicle is authorised to be placed into service. This marking shall be according to one of the following drawings, where D stands for the Member State who has granted the first authorisation (in the given example, Germany) and F stands for the second authorising MS (in the given example, France). The MS are codified in accordance with Decision 2007/756/EC, Appendix 6, part 4.

Appendix QNot used
Appendix RNot used
Appendix SNot used

Braking performance

Appendix TA. ROLE OF THE INFRASTRUCTURE MANAGERThe IM shall inform the RU about the braking performance required for each route and has to provide information about the route characteristics. The IM has to ensure that the impact of the route characteristics and track-side related margins are included in the required braking performance.
Unless the IM and RU have agreed on another unit to express the braking performance, the required braking performance shall be expressed:

(1) | for trains able to run at a maximum speed higher than 200 km/h, in deceleration profile and equivalent response time on level track,;
(2) | for train sets or for fixed train compositions, unable to run at a maximum speed higher than 200 km/h, in deceleration (as above in 1) or in brake weight percentage;The IM shall also deliver the requirements in the alternate unit (brake weight percentage or deceleration), if so requested by the RU;
(3) | for other trains (variable compositions of trains unable to run at a maximum speed higher than 200 km/h): in brake weight percentage.B. ROLE OF THE RAILWAY UNDERTAKINGThe RU shall ensure that each train satisfies or exceeds the braking performance required by the IM. Therefore the RU shall calculate the braking performance of a train taking into account the train composition.
The RU must take into account the vehicle or train set braking performance determined when placed in service. Rolling Stock-related margins like reliability and availability of the brakes have to be considered. The RU must also take into account the information about route characteristics which affect the train behaviour when tuning the braking performance for stopping and securing a train.
The braking performance resulting from the checking of the actual train (like train composition, brake availability, brake settings) will be used as an input value for any operational rule to be subsequently applied to the train.
C. BRAKING PERFORMANCE NOT ACHIEVEDThe IM has to set up rules to be used if a train does not reach the required braking performance and has to make these rules available to the RUs.
If a train does not reach the braking performance required for the routes the train shall run, the RU has to respect the resulting constraints like speed restriction.

List of open points

Appendix UAPPENDIX B (SEE POINT 4.4 OF THIS TSI)Other rules enabling a coherent operation
POINT 4.2.2.1.3.3Freight trains not crossing a border between Member States
Appendix VNot used

Glossary

Appendix WThe definitions in this glossary refer to the use of terms in this TSI OPE.

Term | Definition
Accident | As defined in Article 3 of Directive 2004/49/EC.
Authorising the movement of trains | The operation of equipment in signalling centres, electric traction current supply control rooms and traffic control centres that permits train movement. This does not include those staff employed by a Railway Undertaking who are responsible for management of resources such as train crew or rolling stock.
Competence | The qualification and experience necessary to safely and reliably undertake the task being performed. Experience can be gained as part of the training process.
Dangerous goods | As covered by Directive 2008/68/EC
Degraded operation | Operation resulting from an unplanned event that prevents the normal delivery of train services.
Despatch (= dispatch) | See Train despatch
Driver | As defined in Article 3 of Directive 2007/59/EC.
Exceptional loads | A load carried on a rail vehicle, for example a container, swap body or other traffic where the rail vehicle size and/or axle loading requires special authority for the movement and/or the application of special conditions of travel for all or part of the journey.
Health and Safety Conditions | In the context of this TSI, this refers only to the medical and psychological qualifications required to operate the relevant elements of the subsystem.
Hot axle box | An axle box and bearing that has exceeded its maximum designed operating temperature.
Incident | As defined in Article 3 of Directive 2004/49/EC.
Length of train | Total length of all vehicles over buffers including locomotive(s)
Operating Language | The language or languages used in daily operation an Infrastructure Manager and published in his Network Statement, for the communication of operational or safety related messages between the staff of the Infrastructure Manager and the Railway Undertaking.
Passenger | Person (other than an employee with specific duties on the train) travelling by train or on railway property before or after a train journey.
Performance monitoring | The systematic observation and recording of the performance of the train service and the infrastructure for the purpose of bringing about improvements in the performance of both.
Qualification | The physical and psychological suitability for the task together with the required knowledge.
Real time | The ability to exchange or process information on specified events (such as arrival at a station, passing a station or departure from a station) on the train’s journey as they occur.
Reporting point | A point on the trains schedule where reporting of the arrival, departure or passing time is required.
Route | The particular section or sections of line
Safety-critical work | Work performed by staff when they control or affect the movement of a vehicle, which could affect the health, and safety of persons.
Staff | Employees working for a Railway Undertaking or an Infrastructure Manager, or their contractors, undertaking tasks as specified in this TSI.
Stopping point | A location identified in the schedule of a train where the train is planned to stop, usually to carry out a specific activity such as allowing passengers to join and leave the train.
Timetable | Document or system that gives details of a train(s) schedule over a particular route.
Timing point | A location identified in the schedule of a train where a specific time is identified. This time may be an arrival time, departure time or in the case of a train not scheduled to stop at that location the passing time.
Traction unit | A powered vehicle able to move itself and other vehicles to which it may be coupled.
Train | A train is defined as (a) traction unit(s) with or without coupled railway vehicles with train data available operating between two or more defined points.
Train despatch | The indication to the person driving the train that all station or depot activities are completed and that, as far as the staff responsible are concerned, movement authority has been granted for the train.
Train crew | Members of the on-board staff of a train, who are certified as competent and appointed by a Railway Undertaking to carry out specific, designated safety related tasks on the train, for example the driver or the guard.
Train preparation | Ensuring that a train is in a fit condition to enter service, that the train equipment is correctly deployed and the formation of the train matches the train’s designated pathway. Train preparation also includes technical inspections carried out prior to the train entering service.

Abbreviation | Explanation
AC | Alternating current
CCS | Control-Command and Signalling
CEN | European Committee for Standardisation (Comité Européen de Normalisation)
COTIF | Convention Concerning International Carriage by Rail (Convention relative aux Transports Internationaux Ferroviaires)
CR | Conventional Rail
dB | Decibels
DC | Direct Current
DMI | Driver Machine Interface
EC | European Community
ECG | Electro Cardiogram
EIRENE | European Integrated Railway Radio Enhanced Network
EN | euro-norm
ENE | Energy
ERA | European Rail Agency
ERTMS | European Rail Traffic Management System
ETCS | European Train Control System
EU | European Union
FRS | Functional Requirement Specification
GSM-R | Global System for Mobile Communications — Rail
HABD | Hot Axle Box Detector
Hz | Hertz
IM | Infrastructure Manager
INF | Infrastructure
OPE | Operation and Traffic Management
OSJD | Organisation for Cooperation of Railways
PPV/PPW | Russian abbreviation for Prawila Polzowaniia Wagonami w mejdunarodnom soobqenii = Rules for use of railway vehicles in international traffic
RST | Rolling Stock
RU | Railway Undertaking
SMS | Safety Management System
SPAD | Signal Passed at Danger
SRS | System Requirement Specification
TAF | Telematic Applications for Freight
TEN | Trans-European Network
TSI | Technical Specification for Interoperability
UIC | International Union of Railways (Union Internationale des Chemins de fer)
VKM | Vehicle Keeper Marking

ANNEX IIThe Annex to Decision 2007/756/EC is amended as follows:

(1) | Chapter 1 is amended as follows:(a)The description of the data field 1. ‘European Vehicle Number’ is replaced by the following:‘numeric identification code as defined in Appendix 6’;(b)Footnote (1) is replaced by the following:‘(1)not used’.(c)The description of the data field 2.1 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.(d)The description of the data field 11 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’. | (a) | The description of the data field 1. ‘European Vehicle Number’ is replaced by the following:‘numeric identification code as defined in Appendix 6’; | (b) | Footnote (1) is replaced by the following:‘(1)not used’. | ‘(1) | not used’. | (c) | The description of the data field 2.1 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’. | (d) | The description of the data field 11 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.
(a) | The description of the data field 1. ‘European Vehicle Number’ is replaced by the following:‘numeric identification code as defined in Appendix 6’;
(b) | Footnote (1) is replaced by the following:‘(1)not used’. | ‘(1) | not used’.
‘(1) | not used’.
(c) | The description of the data field 2.1 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.
(d) | The description of the data field 11 is replaced by the following:‘Member State numeric code as defined in Appendix 6, part 4’.
(2) | In Chapter 2.1, Links with other registers, the explanation regarding VKMR is replaced by the following:‘VKMR: this register is managed by ERA and OTIF in cooperation (ERA for the EU and OTIF for all non-EU OTIF Member States). The keeper is recorded in the NVR. Appendix 6 specifies other global central registers (such as vehicle type codes, interoperability codes, country codes, etc.) to be managed by a ‘central body’ resulting from cooperation between ERA and OTIF’.
(3) | The following Appendix is added:‘Appendix 6PART ‘0’—VEHICLE IDENTIFICATIONGeneral remarksThis appendix describes the European Vehicle Number and linked marking applied in a visible manner on the vehicle to identify it uniquely and in a permanent manner during operation. It does not describe other numbers or markings eventually engraved or fixed in a permanent manner on the chassis or the main components of the vehicle during its construction.European Vehicle number and linked abbreviationsEach railway vehicle receives a number consisting of 12 figures (called European Vehicle Number (EVN)) with the following structure:Rolling stock groupInteroperability capability and vehicle type[2 figures]Country in which the vehicle is registered[2 figures]Technical characteristics[4 figures]Serial number[3 figures]Check digit[1 figure]Wagons00 to 0910 to 1920 to 2930 to 3940 to 4980 to 89[details in part 6]01 to 99[details in part 4]0000 to 9999[details in part 9]000 to 9990 to 9[details in part 3]Hauled passenger vehicles50 to 5960 to 6970 to 79[details in part 7]0000 to 9999[details in part 10]000 to 999Tractive rolling stock and units in a train set in fixed or pre-defined formation90 to 99[details in part 8]0000000 to 8999999[the meaning of these figures is defined by the Member States, eventually by bilateral or multilateral agreement]Special vehicles9000 to 9999[details in part 11]000 to 999In a given country, the 7 digits of technical characteristics and serial number are sufficient to identify uniquely a vehicle inside the groups of hauled passenger vehicles and special vehicles(1).Alphabetical markings complete the number:(a)abbreviation of the country in which the vehicle is registered(details in part 4);(b)Vehicle Keeper Marking(details in part 1);(c)abbreviations of the technical characteristics (details in part 12 for the wagons, part 13 for the hauled passenger vehicles).The European Vehicle Number shall be changed when it does not reflect the interoperability capability or technical characteristics according to this Appendix due to technical modifications of the vehicle. Such technical modifications may require a new placing in service according to Articles 20 to 25 of Directive 2008/57/EC.PART 1 — VEHICLE KEEPER MARKING1.Definition of the Vehicle Keeper Marking (VKM)A Vehicle Keeper Marking (VKM) is an alphabetic code, consisting of 2 to 5 letters(2). A VKM is inscribed on each rail vehicle, near the European Vehicle Number. The VKM identifies the Vehicle Keeper as registered in a National Vehicle Register.A VKM is unique and valid in all countries covered by this TSI and all countries that enter into an agreement that involves the application of the system of vehicle numbering and VKM as described in this TSI.2.Format of the Vehicle Keeper MarkingThe VKM is representation of the full name or abbreviation of the vehicle keeper, if possible in a recognisable manner. All 26 letters of the Latina alphabet may be used. The letters in the VKM are written in capitals. Letters that do not stand for first letters of words in the keeper’s name may be written in lower case. For checking uniqueness, the letters written in lower case will be taken as written in capitals.Letters may contain diacritical signs(3). Diacritical signs used by these letters are ignored for checking uniqueness.For vehicles of keepers that reside in a country that does not use the Latin alphabet, a translation of the VKM in its own alphabet may be applied behind the VKM separated from it by a slash-sign (‘/’). This translated VKM is disregarded for data-processing purposes.3.Provisions about allocation of Vehicle Keeper MarkingsA vehicle keeper can be issued more than one VKM, in case:—the vehicle keeper has a formal name in more than one language;—a vehicle keeper has good cause to distinguish between separate vehicle fleets within his organisation.A single VKM can be issued for a group of companies:—that belong to single corporate structure (e.g. holding structure);—that belong to a single corporate structure that has appointed and mandated one organisation within this structure to handle all issues on behalf of all others;—that has mandated a separate, single legal entity for handling all issues on their behalf, in which event the legal entity is the keeper.4.Register of Vehicle Keeper Markings and procedure for allocationThe register of VKM is public and updated on a real time basis.An application for a VKM is filed with the applicant’s competent national authority and forwarded to the ERA. A VKM can be used only after publication by the ERA.The holder of a VKM must inform the competent national authority when he ends the use of a VKM, and the competent national authority will forward the information to the ERA. A VKM will then be revoked once the keeper has proved that the marking has been changed on all vehicles concerned. It will not be reissued for 10 years, unless it is reissued to the original holder or at his request to another holder.A VKM can be transferred to another holder, which is the legal successor to the original holder. A VKM stays valid when the VKM’s holder changes his name to a name that does not bear resemblance to the VKM.In case of a change of keeper which entails a change of VKM, the vehicles concerned must be marked with the new VKM within three months from the date of registration of the change of keeper in the National Vehicle Register. In case of inconsistency between the VKM marked on the vehicle and the data registered in the NVR, the NVR-registration supersedes.PART 2Not usedPART 3 — RULES FOR THE DETERMINATION OF THE CHECK-DIGIT (DIGIT 12)The check-digit is determined in the following manner:—the digits in the even positions of the basic number (counting from the right) are taken at their own decimal value;—the digits in the odd positions of the basic number (counting from the right) are multiplied by 2;—the sum formed by the digits in even position and by all the digits which constitute the partial products obtained from the odd positions is then established;—the unit’s digit of this sum is retained;—the complement required to bring the unit’s digit to 10 forms the check-digit; should this units digit be nought, then the check-digit will also be nought.Examples:1 —Let the basic number be33844796100Multiplication factor212121212126316487186200Sum: 6 + 3 + 1 + 6 + 4 + 8 + 7 + 1 + 8 + 6 + 2 + 0 + 0 = 52The unit’s digit of this sum is 2.The check-digit number will therefore be 8 and the basic number thus becomes the registration number 33 84 4796 100 – 8.2 —Let the basic number be31513320198Multiplication factor212121212126110163402916Sum: 6 + 1 + 1 + 0 + 1 + 6 + 3 + 4 + 0 + 2 + 9 + 1 + 6 = 40The unit’s digit of this sum is 0.The check-digit number will therefore be 0 and the basic number thus becomes the registration number 31 51 3320 198 – 0.PART 4 — CODING OF THE COUNTRIES IN WHICH THE VEHICLES ARE REGISTERED (DIGITS 3-4 AND ABBREVIATION)The Information relating to third countries is given for information purposes only.CountriesAlphabetical country code(4)Numerical country codeAlbaniaAL41AlgeriaDZ92ArmeniaAM58AustriaA81AzerbaijanAZ57BelarusBY21BelgiumB88Bosnia-HerzegovinaBIH49BulgariaBG52ChinaRC33CroatiaHR78CubaCU(4)40CyprusCYCzech RepublicCZ54DenmarkDK86EgyptET90EstoniaEST26FinlandFIN10FranceF87GeorgiaGE28GermanyD80GreeceGR73HungaryH55IranIR96IraqIRQ(4)99IrelandIRL60IsraelIL95ItalyI83JapanJ42KazakhstanKZ27KyrgyzstanKS59LatviaLV25LebanonRL98LiechtensteinFLLithuaniaLT24LuxembourgL82MacedoniaMK65MaltaMMoldovaMD(4)23MonacoMCMongoliaMGL31MontenegroMNE62MoroccoMA93NetherlandsNL84North KoreaPRK(4)30NorwayN76PolandPL51PortugalP94RomaniaRO53RussiaRUS20SerbiaSRB72SlovakiaSK56SloveniaSLO79South KoreaROK61SpainE71SwedenSE74SwitzerlandCH85SyriaSYR97TajikistanTJ66TunisiaTN91TurkeyTR75TurkmenistanTM67UkraineUA22United KingdomGB70UzbekistanUZ29VietnamVN(4)32PART 5Not usedPART 6 — INTEROPERABILITY CODES USED FOR WAGONS (DIGITS 1-2)2nd digit1st digit01234567892nd digit1st digitTrack Gaugefixed or variablefixedvariablefixedvariablefixedvariablefixedvariablefixed or variableTrack GaugeWagons conform to TSI WAG(1)including section 7.1.2 and all conditions set out in Appendix C0with axlesNot to be usedwagonsnot to be used(3)PPV/PPW wagons(variable gauge)with axles01with bogieswith bogies12with axleswagonsPPV/PPW wagons(fixed gauge)with axles23with bogieswith bogies3Other wagons4with axles(2)maintenance related wagonsOther wagonsWagons with special numbering for technical characteristics not placed in service inside EUwith axles(2)48with bogies(2)with bogies(2)81st digit2nd digit01234567891st digit2nd digitPART 7 — INTERNATIONAL TRAFFIC ABILITY CODES USED FOR HAULED PASSENGER VEHICLES (DIGITS 1-2)Domestic trafficTEN(4)and/or COTIF(5)and/or PPV/PPWDomestic traffic or international traffic by special agreementTEN(4)and/or COTIF(5)PPV/PPW2nd digit1st digit01234567895Vehicles for domestic trafficFixed-gauge non-air-conditioned vehicles (including car-carrying wagons)Gauge-adjustable (1435/1520) non-air-conditioned vehiclesNot to be usedGauge-adjustable (1435/1668) non-air-conditioned vehiclesHistorical vehiclesNot to be used(6)Fixed-gauge vehiclesGauge-adjustable (1435/1520) vehicles with change of bogiesGauge-adjustable (1435/1520) vehicles with gauge-adjustable axles6Service vehiclesFixed-gauge air-conditioned vehiclesGauge-adjustable (1435/1520) air-conditioned vehiclesService vehiclesGauge-adjustable (1435/1668) air-conditioned vehiclesCar-carrying wagonsNot to be used(6)7Air-conditioned and pressure-tight vehiclesNot to be usedNot to be usedPressure-tight fixed-gauge air-conditioned vehiclesNot to be usedOther vehiclesNot to be usedNot to be usedNot to be usedNot to be usedPART 8 — TYPES OF TRACTIVE ROLLING STOCK AND UNITS IN A TRAIN SET IN FIXED OR PRE-DEFINED FORMATION (DIGITS 1-2)The first digit is ‘9’.If the second digit describes the type of tractive stock, following coding is mandatory:CodeGeneral vehicle type0Miscellaneous1Electric locomotive2Diesel locomotive3Electric multiple-unit set (high speed) [power car or trailer]4Electric multiple-unit set (except high speed) [power car or trailer]5Diesel multiple-unit set [power car or trailer]6Specialised trailer,7Electric shunting engine8Diesel shunting engine9Special vehiclePART 9 — STANDARD NUMERICAL MARKING OF WAGONS (DIGITS 5 TO 8)Part 9 indicates the numerical marking associated to the main technical characteristics of the wagon and it is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA.PART 10 — CODES FOR THE TECHNICAL CHARACTERISTICS OF THE HAULED PASSENGER STOCK (DIGITS 5-6)Part 10 is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA.PART 11 — CODES FOR THE TECHNICAL CHARACTERISTICS OF THE SPECIAL VEHICLES (DIGIT 6 TO 8)Part 11 is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA.PART 12 — LETTER MARKING FOR WAGONS EXCLUDING ARTICULATED AND MULTIPLE WAGONSPart 12 is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA.PART 13 — LETTER MARKING FOR HAULED PASSENGER STOCKPart 13 is published on the ERA website (www.era.europa.eu).An application for a new code is filed with the registering entity (as referred to in Decision 2007/756/EC) and sent to the ERA. A new code can be used only after publication by the ERA. | Rolling stock group | Interoperability capability and vehicle type[2 figures] | Country in which the vehicle is registered[2 figures] | Technical characteristics[4 figures] | Serial number[3 figures] | Check digit[1 figure] | Wagons | 00 to 0910 to 1920 to 2930 to 3940 to 4980 to 89[details in part 6] | 01 to 99[details in part 4] | 0000 to 9999[details in part 9] | 000 to 999 | 0 to 9[details in part 3] | Hauled passenger vehicles | 50 to 5960 to 6970 to 79[details in part 7] | 0000 to 9999[details in part 10] | 000 to 999 | Tractive rolling stock and units in a train set in fixed or pre-defined formation | 90 to 99[details in part 8] | 0000000 to 8999999[the meaning of these figures is defined by the Member States, eventually by bilateral or multilateral agreement] | Special vehicles | 9000 to 9999[details in part 11] | 000 to 999 | (a) | abbreviation of the country in which the vehicle is registered(details in part 4); | (b) | Vehicle Keeper Marking(details in part 1); | (c) | abbreviations of the technical characteristics (details in part 12 for the wagons, part 13 for the hauled passenger vehicles). | — | the vehicle keeper has a formal name in more than one language; | — | a vehicle keeper has good cause to distinguish between separate vehicle fleets within his organisation. | — | that belong to single corporate structure (e.g. holding structure); | — | that belong to a single corporate structure that has appointed and mandated one organisation within this structure to handle all issues on behalf of all others; | — | that has mandated a separate, single legal entity for handling all issues on their behalf, in which event the legal entity is the keeper. | — | the digits in the even positions of the basic number (counting from the right) are taken at their own decimal value; | — | the digits in the odd positions of the basic number (counting from the right) are multiplied by 2; | — | the sum formed by the digits in even position and by all the digits which constitute the partial products obtained from the odd positions is then established; | — | the unit’s digit of this sum is retained; | — | the complement required to bring the unit’s digit to 10 forms the check-digit; should this units digit be nought, then the check-digit will also be nought. | | 1 — | Let the basic number be33844796100Multiplication factor212121212126316487186200Sum: 6 + 3 + 1 + 6 + 4 + 8 + 7 + 1 + 8 + 6 + 2 + 0 + 0 = 52The unit’s digit of this sum is 2.The check-digit number will therefore be 8 and the basic number thus becomes the registration number 33 84 4796 100 – 8. | Let the basic number be | 3 | 3 | 8 | 4 | 4 | 7 | 9 | 6 | 1 | 0 | 0 | Multiplication factor | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | | 6 | 3 | 16 | 4 | 8 | 7 | 18 | 6 | 2 | 0 | 0 | | 2 — | Let the basic number be31513320198Multiplication factor212121212126110163402916Sum: 6 + 1 + 1 + 0 + 1 + 6 + 3 + 4 + 0 + 2 + 9 + 1 + 6 = 40The unit’s digit of this sum is 0.The check-digit number will therefore be 0 and the basic number thus becomes the registration number 31 51 3320 198 – 0. | Let the basic number be | 3 | 1 | 5 | 1 | 3 | 3 | 2 | 0 | 1 | 9 | 8 | Multiplication factor | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | | 6 | 1 | 10 | 1 | 6 | 3 | 4 | 0 | 2 | 9 | 16 | Countries | Alphabetical country code(4) | Numerical country code | Albania | AL | 41 | Algeria | DZ | 92 | Armenia | AM | 58 | Austria | A | 81 | Azerbaijan | AZ | 57 | Belarus | BY | 21 | Belgium | B | 88 | Bosnia-Herzegovina | BIH | 49 | Bulgaria | BG | 52 | China | RC | 33 | Croatia | HR | 78 | Cuba | CU(4) | 40 | Cyprus | CY | | Czech Republic | CZ | 54 | Denmark | DK | 86 | Egypt | ET | 90 | Estonia | EST | 26 | Finland | FIN | 10 | France | F | 87 | Georgia | GE | 28 | Germany | D | 80 | Greece | GR | 73 | Hungary | H | 55 | Iran | IR | 96 | Iraq | IRQ(4) | 99 | Ireland | IRL | 60 | Israel | IL | 95 | Italy | I | 83 | Japan | J | 42 | Kazakhstan | KZ | 27 | Kyrgyzstan | KS | 59 | Latvia | LV | 25 | Lebanon | RL | 98 | Liechtenstein | FL | | Lithuania | LT | 24 | Luxembourg | L | 82 | Macedonia | MK | 65 | Malta | M | | Moldova | MD(4) | 23 | Monaco | MC | | Mongolia | MGL | 31 | Montenegro | MNE | 62 | Morocco | MA | 93 | Netherlands | NL | 84 | North Korea | PRK(4) | 30 | Norway | N | 76 | Poland | PL | 51 | Portugal | P | 94 | Romania | RO | 53 | Russia | RUS | 20 | Serbia | SRB | 72 | Slovakia | SK | 56 | Slovenia | SLO | 79 | South Korea | ROK | 61 | Spain | E | 71 | Sweden | SE | 74 | Switzerland | CH | 85 | Syria | SYR | 97 | Tajikistan | TJ | 66 | Tunisia | TN | 91 | Turkey | TR | 75 | Turkmenistan | TM | 67 | Ukraine | UA | 22 | United Kingdom | GB | 70 | Uzbekistan | UZ | 29 | Vietnam | VN(4) | 32 | | 2nd digit1st digit | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 2nd digit1st digit | | | Track Gauge | fixed or variable | fixed | variable | fixed | variable | fixed | variable | fixed | variable | fixed or variable | Track Gauge | | Wagons conform to TSI WAG(1)including section 7.1.2 and all conditions set out in Appendix C | 0 | with axles | Not to be used | wagons | not to be used(3) | PPV/PPW wagons(variable gauge) | with axles | 0 | 1 | with bogies | with bogies | 1 | 2 | with axles | wagons | PPV/PPW wagons(fixed gauge) | with axles | 2 | 3 | with bogies | with bogies | 3 | Other wagons | 4 | with axles(2) | maintenance related wagons | Other wagons | Wagons with special numbering for technical characteristics not placed in service inside EU | with axles(2) | 4 | 8 | with bogies(2) | with bogies(2) | 8 | | | | | | | | 1st digit2nd digit | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 1st digit2nd digit | | Domestic traffic | TEN(4)and/or COTIF(5)and/or PPV/PPW | Domestic traffic or international traffic by special agreement | TEN(4)and/or COTIF(5) | PPV/PPW | 2nd digit1st digit | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 5 | Vehicles for domestic traffic | Fixed-gauge non-air-conditioned vehicles (including car-carrying wagons) | Gauge-adjustable (1435/1520) non-air-conditioned vehicles | Not to be used | Gauge-adjustable (1435/1668) non-air-conditioned vehicles | Historical vehicles | Not to be used(6) | Fixed-gauge vehicles | Gauge-adjustable (1435/1520) vehicles with change of bogies | Gauge-adjustable (1435/1520) vehicles with gauge-adjustable axles | 6 | Service vehicles | Fixed-gauge air-conditioned vehicles | Gauge-adjustable (1435/1520) air-conditioned vehicles | Service vehicles | Gauge-adjustable (1435/1668) air-conditioned vehicles | Car-carrying wagons | Not to be used(6) | 7 | Air-conditioned and pressure-tight vehicles | Not to be used | Not to be used | Pressure-tight fixed-gauge air-conditioned vehicles | Not to be used | Other vehicles | Not to be used | Not to be used | Not to be used | Not to be used | Code | General vehicle type | 0 | Miscellaneous | 1 | Electric locomotive | 2 | Diesel locomotive | 3 | Electric multiple-unit set (high speed) [power car or trailer] | 4 | Electric multiple-unit set (except high speed) [power car or trailer] | 5 | Diesel multiple-unit set [power car or trailer] | 6 | Specialised trailer, | 7 | Electric shunting engine | 8 | Diesel shunting engine | 9 | Special vehicle
Rolling stock group | Interoperability capability and vehicle type[2 figures] | Country in which the vehicle is registered[2 figures] | Technical characteristics[4 figures] | Serial number[3 figures] | Check digit[1 figure]
Wagons | 00 to 0910 to 1920 to 2930 to 3940 to 4980 to 89[details in part 6] | 01 to 99[details in part 4] | 0000 to 9999[details in part 9] | 000 to 999 | 0 to 9[details in part 3]
Hauled passenger vehicles | 50 to 5960 to 6970 to 79[details in part 7] | 0000 to 9999[details in part 10] | 000 to 999
Tractive rolling stock and units in a train set in fixed or pre-defined formation | 90 to 99[details in part 8] | 0000000 to 8999999[the meaning of these figures is defined by the Member States, eventually by bilateral or multilateral agreement]
Special vehicles | 9000 to 9999[details in part 11] | 000 to 999
(a) | abbreviation of the country in which the vehicle is registered(details in part 4);
(b) | Vehicle Keeper Marking(details in part 1);
(c) | abbreviations of the technical characteristics (details in part 12 for the wagons, part 13 for the hauled passenger vehicles).
— | the vehicle keeper has a formal name in more than one language;
— | a vehicle keeper has good cause to distinguish between separate vehicle fleets within his organisation.
— | that belong to single corporate structure (e.g. holding structure);
— | that belong to a single corporate structure that has appointed and mandated one organisation within this structure to handle all issues on behalf of all others;
— | that has mandated a separate, single legal entity for handling all issues on their behalf, in which event the legal entity is the keeper.
— | the digits in the even positions of the basic number (counting from the right) are taken at their own decimal value;
— | the digits in the odd positions of the basic number (counting from the right) are multiplied by 2;
— | the sum formed by the digits in even position and by all the digits which constitute the partial products obtained from the odd positions is then established;
— | the unit’s digit of this sum is retained;
— | the complement required to bring the unit’s digit to 10 forms the check-digit; should this units digit be nought, then the check-digit will also be nought.
| 1 — | Let the basic number be33844796100Multiplication factor212121212126316487186200Sum: 6 + 3 + 1 + 6 + 4 + 8 + 7 + 1 + 8 + 6 + 2 + 0 + 0 = 52The unit’s digit of this sum is 2.The check-digit number will therefore be 8 and the basic number thus becomes the registration number 33 84 4796 100 – 8. | Let the basic number be | 3 | 3 | 8 | 4 | 4 | 7 | 9 | 6 | 1 | 0 | 0 | Multiplication factor | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | | 6 | 3 | 16 | 4 | 8 | 7 | 18 | 6 | 2 | 0 | 0
Let the basic number be | 3 | 3 | 8 | 4 | 4 | 7 | 9 | 6 | 1 | 0 | 0
Multiplication factor | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2
| 6 | 3 | 16 | 4 | 8 | 7 | 18 | 6 | 2 | 0 | 0
| 2 — | Let the basic number be31513320198Multiplication factor212121212126110163402916Sum: 6 + 1 + 1 + 0 + 1 + 6 + 3 + 4 + 0 + 2 + 9 + 1 + 6 = 40The unit’s digit of this sum is 0.The check-digit number will therefore be 0 and the basic number thus becomes the registration number 31 51 3320 198 – 0. | Let the basic number be | 3 | 1 | 5 | 1 | 3 | 3 | 2 | 0 | 1 | 9 | 8 | Multiplication factor | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | | 6 | 1 | 10 | 1 | 6 | 3 | 4 | 0 | 2 | 9 | 16
Let the basic number be | 3 | 1 | 5 | 1 | 3 | 3 | 2 | 0 | 1 | 9 | 8
Multiplication factor | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2 | 1 | 2
| 6 | 1 | 10 | 1 | 6 | 3 | 4 | 0 | 2 | 9 | 16
Countries | Alphabetical country code(4) | Numerical country code
Albania | AL | 41
Algeria | DZ | 92
Armenia | AM | 58
Austria | A | 81
Azerbaijan | AZ | 57
Belarus | BY | 21
Belgium | B | 88
Bosnia-Herzegovina | BIH | 49
Bulgaria | BG | 52
China | RC | 33
Croatia | HR | 78
Cuba | CU(4) | 40
Cyprus | CY |
Czech Republic | CZ | 54
Denmark | DK | 86
Egypt | ET | 90
Estonia | EST | 26
Finland | FIN | 10
France | F | 87
Georgia | GE | 28
Germany | D | 80
Greece | GR | 73
Hungary | H | 55
Iran | IR | 96
Iraq | IRQ(4) | 99
Ireland | IRL | 60
Israel | IL | 95
Italy | I | 83
Japan | J | 42
Kazakhstan | KZ | 27
Kyrgyzstan | KS | 59
Latvia | LV | 25
Lebanon | RL | 98
Liechtenstein | FL |
Lithuania | LT | 24
Luxembourg | L | 82
Macedonia | MK | 65
Malta | M |
Moldova | MD(4) | 23
Monaco | MC |
Mongolia | MGL | 31
Montenegro | MNE | 62
Morocco | MA | 93
Netherlands | NL | 84
North Korea | PRK(4) | 30
Norway | N | 76
Poland | PL | 51
Portugal | P | 94
Romania | RO | 53
Russia | RUS | 20
Serbia | SRB | 72
Slovakia | SK | 56
Slovenia | SLO | 79
South Korea | ROK | 61
Spain | E | 71
Sweden | SE | 74
Switzerland | CH | 85
Syria | SYR | 97
Tajikistan | TJ | 66
Tunisia | TN | 91
Turkey | TR | 75
Turkmenistan | TM | 67
Ukraine | UA | 22
United Kingdom | GB | 70
Uzbekistan | UZ | 29
Vietnam | VN(4) | 32
| 2nd digit1st digit | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 2nd digit1st digit
| | Track Gauge | fixed or variable | fixed | variable | fixed | variable | fixed | variable | fixed | variable | fixed or variable | Track Gauge |
Wagons conform to TSI WAG(1)including section 7.1.2 and all conditions set out in Appendix C | 0 | with axles | Not to be used | wagons | not to be used(3) | PPV/PPW wagons(variable gauge) | with axles | 0
1 | with bogies | with bogies | 1
2 | with axles | wagons | PPV/PPW wagons(fixed gauge) | with axles | 2
3 | with bogies | with bogies | 3
Other wagons | 4 | with axles(2) | maintenance related wagons | Other wagons | Wagons with special numbering for technical characteristics not placed in service inside EU | with axles(2) | 4
8 | with bogies(2) | with bogies(2) | 8
| | | | |
| 1st digit2nd digit | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 1st digit2nd digit
| Domestic traffic | TEN(4)and/or COTIF(5)and/or PPV/PPW | Domestic traffic or international traffic by special agreement | TEN(4)and/or COTIF(5) | PPV/PPW
2nd digit1st digit | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
5 | Vehicles for domestic traffic | Fixed-gauge non-air-conditioned vehicles (including car-carrying wagons) | Gauge-adjustable (1435/1520) non-air-conditioned vehicles | Not to be used | Gauge-adjustable (1435/1668) non-air-conditioned vehicles | Historical vehicles | Not to be used(6) | Fixed-gauge vehicles | Gauge-adjustable (1435/1520) vehicles with change of bogies | Gauge-adjustable (1435/1520) vehicles with gauge-adjustable axles
6 | Service vehicles | Fixed-gauge air-conditioned vehicles | Gauge-adjustable (1435/1520) air-conditioned vehicles | Service vehicles | Gauge-adjustable (1435/1668) air-conditioned vehicles | Car-carrying wagons | Not to be used(6)
7 | Air-conditioned and pressure-tight vehicles | Not to be used | Not to be used | Pressure-tight fixed-gauge air-conditioned vehicles | Not to be used | Other vehicles | Not to be used | Not to be used | Not to be used | Not to be used
Code | General vehicle type
0 | Miscellaneous
1 | Electric locomotive
2 | Diesel locomotive
3 | Electric multiple-unit set (high speed) [power car or trailer]
4 | Electric multiple-unit set (except high speed) [power car or trailer]
5 | Diesel multiple-unit set [power car or trailer]
6 | Specialised trailer,
7 | Electric shunting engine
8 | Diesel shunting engine
9 | Special vehicle
(1) For special vehicles, the number has to be unique in a given country with the first digit and the 5 last digits of the technical characteristics and serial number.
(2) For NMBS/SNCB, the use of an encircled single letter B can be continued.
(3) Diacritical marks are ‘accent-signs’, such as in À, Ç, Ö, Č, Ž, Å etc. Special letters such as Ø and Æ will be represented by a single letter; in tests for uniqueness Ø is treated as O and Æ as A.’

(4) According to the alphabetical coding system described in Appendix 4 to the 1949 convention and Article 45(4) of the 1968 convention on road traffic.
(1) Commission Regulation [TSI WAG as adopted after the revision].
(2) Fixed or variable gauge.
(3) Except for wagons in category I (temperature-controlled wagons), not to be used for new vehicles authorised placed in service.
(4) Compliance with the applicable TSIs, see appendix P, part 5.
(5) Including vehicles, which according to existing regulations carry the digits defined in the present table. COTIF: vehicle compliant with COTIF regulation in force at the moment of placing in service
(6) Excepted for coaches with fixed gauge (56) and adjustable gauge (66) already in service, not to be used for new vehicles

Pending: 32012D0478

17.8.2012 EN Official Journal of the European Union L 219/21
(1) On 1 December 2011, the Council adopted Decision 2011/782/CFSP.
(2) An additional entity should be included in the list of persons and entities subject to restrictive measures set out in Annex I to Decision 2011/782/CFSP,
Name Identifying information Reasons Date of listing
1. Drex Technologies Holding S.A. Registered in Luxembourg under number B77616, formerly established at the following address: 17, rue Beaumont L-1219 Luxembourg. The beneficial owner of Drex Technologies Holding S.A. is Rami Makhlouf, who is listed under EU sanctions for providing financial support to the Syrian regime. 16.8.2012
THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union,
Having regard to Decision 2011/782/CFSP(1), and in particular Article 21(1) thereof,
(1) On 1 December 2011, the Council adopted Decision 2011/782/CFSP.
(2) An additional entity should be included in the list of persons and entities subject to restrictive measures set out in Annex I to Decision 2011/782/CFSP,
HAS ADOPTED THIS DECISION:

Article 1
The entity listed in the Annex to this Decision shall be added to the list set out in Annex I to Decision 2011/782/CFSP.

Article 2
This Decision shall enter into force on the date of its publication in theOfficial Journal of the European Union.

THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union,
Having regard to Decision 2011/782/CFSP(1), and in particular Article 21(1) thereof,
(1) On 1 December 2011, the Council adopted Decision 2011/782/CFSP.
(2) An additional entity should be included in the list of persons and entities subject to restrictive measures set out in Annex I to Decision 2011/782/CFSP,
HAS ADOPTED THIS DECISION:
The entity listed in the Annex to this Decision shall be added to the list set out in Annex I to Decision 2011/782/CFSP.
This Decision shall enter into force on the date of its publication in theOfficial Journal of the European Union.

ENTITY REFERRED TO IN ARTICLE 1

ANNEX
Entity

| Name | Identifying information | Reasons | Date of listing
1. | Drex Technologies Holding S.A. | Registered in Luxembourg under number B77616, formerly established at the following address: 17, rue Beaumont L-1219 Luxembourg. | The beneficial owner of Drex Technologies Holding S.A. is Rami Makhlouf, who is listed under EU sanctions for providing financial support to the Syrian regime. | 16.8.2012

Pending: 32012D0424

24.7.2012 EN Official Journal of the European Union L 196/81
(1) On 1 December 2011, the Council adopted Decision 2011/782/CFSP.
(2) In view of the gravity of the situation in Syria, additional persons and entities should be included in the list of persons and entities subject to restrictive measures set out in Annex I to Decision 2011/782/CFSP,
Name Identifying information Reasons Date of listing
1. Brigadier GeneralSha’afiq Masa Head of Branch 215 (Damascus) of the army's intelligence service. Responsible for the torture of detained opponents. Involved in repressive actions against civilians. 24.7.2012
2. Brigadier GeneralBurhan Qadour Head of Branch 291 (Damascus) of the army's intelligence service. Responsible for the torture of opponents in custody. 24.7.2012
3. Brigadier GeneralSalah Hamad Deputy Head of Branch 291 of the army's intelligence service. Responsible for the torture of opponents in custody. 24.7.2012
4. Brigadier GeneralMuhammad (or: Mohammed) Khallouf (a.k.a. Abou Ezzat) Head of Branch 235, a.k.a. "Palestine" (Damascus) of the army's intelligence service, which is at the centre of the army's apparatus of repression. Directly involved in repression of opponents. Responsible for the torture of opponents in custody. 24.7.2012
5. Major General Riad al-Ahmed Deputy Head of Latakia Branch of the army's intelligence service. Responsible for the torture and murder of opponents in custody. 24.7.2012
6. Brigadier GeneralAbdul Salam Fajr Mahmoud Head of the Bab Tuma (Damascus) Branch of the air force's intelligence service. Responsible for the torture of opponents in custody. 24.7.2012
7. Brigadier GeneralJawdat al-Ahmed Head of the Homs Branch of the air force's intelligence service. Responsible for the torture of opponents in custody. 24.7.2012
8. ColonelQusay Mihoub Head of the Deraa branch of the air force's intelligence service (sent from Damascus to Deraa at the start of demonstrations there). Responsible for the torture of opponents in custody. 24.7.2012
9. ColonelSuhail Al-Abdullah Head of the Latakia Branch of the air force's intelligence service. Responsible for the torture of opponents in custody. 24.7.2012
10. Brigadier GeneralKhudr Khudr Head of the Latakia branch of the General Intelligence Directorate. Responsible for the torture of opponents in custody. 24.7.2012
11. Brigadier GeneralIbrahim Ma’ala Head of branch 285 (Damascus) of the General Intelligence Directorate (replaced Brig. Gen. Hussam Fendi at end 2011). Responsible for the torture of opponents in custody. 24.7.2012
12. Brigadier GeneralFiras Al-Hamed Head of branch 318 (Homs) of the General Intelligence Directorate. Responsible for the torture of opponents in custody. 24.7.2012
13. Brigadier GeneralHussam Luqa Since April 2012, head of the Homs branch of the Political Security Directorate (succeeded Brig. Gen. Nasr al-Ali). Responsible for the torture of opponents in custody. 24.7.2012
14. Brigadier GeneralTaha Taha Site manager of the Latakia branch of the Political Security Directorate. Responsible for the torture of opponents in custody. 24.7.2012
15. Brigadier GeneralNasr al-Ali Since April 2012 manager of the Deraa site of the Political Security Directorate (ex-head of the Homs branch). Responsible for the torture of opponents in custody. 24.7.2012
16. Bassel Bilal Police officer at Idlib central prison; has taken part directly in acts of torture of opponents held in Idlib central prison. 24.7.2012
17. Ahmad Kafan Police officer at Idlib central prison; has taken part directly in acts of torture of opponents held in Idlib central prison. 24.7.2012
18. Bassam al-Misri Police officer at Idlib central prison; has taken part directly in acts of torture of opponents held in Idlib central prison. 24.7.2012
19. Ahmed al-Jarroucheh Date of birth: 1957 Head of the foreign branch of General Intelligence (branch 279). As such, responsible for General Intelligence arrangements in Syrian embassies. He participates directly in the repression implemented by the Syrian authorities against opponents and in particular has responsibility for repression of the Syrian opposition abroad. 24.7.2012
20. Michel Kassouha(a.k.a. Ahmed Salem; a.k.a. Ahmed Salem Hassan) Date of birth: 1 February 1948 Member of the Syrian security services since the early 1970s, he is involved in combating opposition in France and Germany. Since March 2006, has been responsible for public relations of branch 273 of the Syrian General Intelligence Directorate. A longstanding member of the managerial staff, he is close to General Intelligence Directorate head Ali Mamlouk, one of the top security officials of the regime who has been subject to EU restrictive measures since 9 May 2011. He directly supports the regime's repression of opponents and is responsible inter alia for repression of the Syrian opposition abroad. 24.7.2012
21. General Ghassan Jaoudat Ismail Date of birth: 1960Place of origin: Drekish, Tartus region. Responsible for the missions branch of the air force intelligence service, which, in cooperation with the special operations branch, manages the elite troops of the air force intelligence service, who play an important role in the repression conducted by the regime. As such, Ghassan Jaoudat Ismail is one of the military leaders directly implementing the repression of opponents conducted by the regime. 24.7.2012
22. General Amer al-Achi (a.k.a. Amis al Ashi; a.k.a. Ammar Aachi; a.k.a. Amer Ashi) Graduate of the military school of Aleppo, head of the intelligence branch of the air force intelligence service (since 2012), close to Daoud Rajah, Syrian Minister for Defence. Through his role in the air force intelligence service, Amer al-Achi is implicated in the repression of the Syrian opposition. 24.7.2012
23. General Mohammed Ali Nasr (or: Mohammed Ali Naser) Date of birth: around 1964 Close to Maher al-Assad, younger brother of the President. Most of his career has been spent in the Republican Guard. In 2010 he joined the internal branch (or branch 251) of the General Intelligence Directorate which is responsible for combating the political opposition. As one of its senior officers, General Mohammed Ali is directly involved in the repression of opponents. 24.7.2012
24. General Issam Hallaq Air Force Chief of Staff since 2010. Commands air operations against opponents. 24.7.2012
25. Ezzedine Ismael Date of birth: middle of the 1940s (probably 1947).Place of birth: Bastir. Jableh region. Retired general, longstanding member of the managerial staff of the air force intelligence service, of which he became the head in the early 2000s. Was appointed political and security adviser to the President in 2006. As political and security adviser to the Syrian president, Ezzedine Ismael is implicated in the political repression conducted by the regime against the opposition. 24.7.2012
26. Samir Joumaa (a.k.a. Abou Sami) Date of birth: around 1962 For almost 20 years he has been head of the office of Mohammad Nassif Kheir Bek, one of the main security advisers of Bashar al-Assad (and officially deputy to the Vice-President, Farouk al-Sharaa). Samir Joumaa's closeness to Bashar al-Assad and Mohammed Nassif Kheir Bek means that he is implicated in the policy of repression conducted by the regime against its opponents. 24.7.2012
Name Identifying information Reasons Date of listing
1. Drex Technologies S.A. Incorporation date: 4 July 2000Incorporation number: 394678Director: Rami MakhloufRegistered agent: Mossack Fonseca & Co (BVI) Ltd Drex Technologies is wholly owned by Rami Makhlouf, who is listed under EU sanctions for providing financial support to the Syrian regime. Rami Makhlouf uses Drex Technologies to facilitate and manage his international financial holdings, including a majority share in SyriaTel, which the EU has previously listed on the grounds that it also provides financial support to the Syrian regime. 24.7.2012
2. Cotton Marketing Organisation Address: Bab Al-Faraj P.O. Box 729, AleppoTél.: +96321 2239495/6/7/[email protected] Address: Bab Al-Faraj P.O. Box 729, Aleppo Tél.: +96321 2239495/6/7/8 [email protected] www.cmo.gov.sy State-owned company. Provides financial support to the Syrian regime.
Address: Bab Al-Faraj P.O. Box 729, Aleppo
Tél.: +96321 2239495/6/7/8
[email protected]
www.cmo.gov.sy
3. Syrian Arab Airlines (a.k.a. SAA, a.k.a. Syrian Air) Al-Mohafazeh Square, P.O. Box 417, Damascus, SyriaTel: +963112240774 Al-Mohafazeh Square, P.O. Box 417, Damascus, Syria Tel: +963112240774 Public company controlled by the regime. Provides financial support for the regime. 24.7.2012
Al-Mohafazeh Square, P.O. Box 417, Damascus, Syria
Tel: +963112240774
Address: Bab Al-Faraj P.O. Box 729, Aleppo
Tél.: +96321 2239495/6/7/8
[email protected]
www.cmo.gov.sy
Al-Mohafazeh Square, P.O. Box 417, Damascus, Syria
Tel: +963112240774
THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union,
Having regard to Decision 2011/782/CFSP(1), and in particular Article 21(1) thereof,
(1) On 1 December 2011, the Council adopted Decision 2011/782/CFSP.
(2) In view of the gravity of the situation in Syria, additional persons and entities should be included in the list of persons and entities subject to restrictive measures set out in Annex I to Decision 2011/782/CFSP,
HAS ADOPTED THIS DECISION:

Article 1
The persons and entities listed in the Annex to this Decision shall be added to the list set out in Annex I to Decision 2011/782/CFSP.

Article 2
This Decision shall enter into force on the date of its publication in theOfficial Journal of the European Union.

THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union,
Having regard to Decision 2011/782/CFSP(1), and in particular Article 21(1) thereof,
(1) On 1 December 2011, the Council adopted Decision 2011/782/CFSP.
(2) In view of the gravity of the situation in Syria, additional persons and entities should be included in the list of persons and entities subject to restrictive measures set out in Annex I to Decision 2011/782/CFSP,
HAS ADOPTED THIS DECISION:
The persons and entities listed in the Annex to this Decision shall be added to the list set out in Annex I to Decision 2011/782/CFSP.
This Decision shall enter into force on the date of its publication in theOfficial Journal of the European Union.

Persons and entities referred to in Article 1

ANNEX
Persons

| Name | Identifying information | Reasons | Date of listing
1. | Brigadier GeneralSha’afiq Masa | | Head of Branch 215 (Damascus) of the army’s intelligence service. Responsible for the torture of detained opponents. Involved in repressive actions against civilians. | 24.7.2012
2. | Brigadier GeneralBurhan Qadour | | Head of Branch 291 (Damascus) of the army’s intelligence service. Responsible for the torture of opponents in custody. | 24.7.2012
3. | Brigadier GeneralSalah Hamad | | Deputy Head of Branch 291 of the army’s intelligence service. Responsible for the torture of opponents in custody. | 24.7.2012
4. | Brigadier GeneralMuhammad (or: Mohammed) Khallouf (a.k.a. Abou Ezzat) | | Head of Branch 235, a.k.a. “Palestine” (Damascus) of the army’s intelligence service, which is at the centre of the army’s apparatus of repression. Directly involved in repression of opponents. Responsible for the torture of opponents in custody. | 24.7.2012
5. | Major General Riad al-Ahmed | | Deputy Head of Latakia Branch of the army’s intelligence service. Responsible for the torture and murder of opponents in custody. | 24.7.2012
6. | Brigadier GeneralAbdul Salam Fajr Mahmoud | | Head of the Bab Tuma (Damascus) Branch of the air force’s intelligence service. Responsible for the torture of opponents in custody. | 24.7.2012
7. | Brigadier GeneralJawdat al-Ahmed | | Head of the Homs Branch of the air force’s intelligence service. Responsible for the torture of opponents in custody. | 24.7.2012
8. | ColonelQusay Mihoub | | Head of the Deraa branch of the air force’s intelligence service (sent from Damascus to Deraa at the start of demonstrations there). Responsible for the torture of opponents in custody. | 24.7.2012
9. | ColonelSuhail Al-Abdullah | | Head of the Latakia Branch of the air force’s intelligence service. Responsible for the torture of opponents in custody. | 24.7.2012
10. | Brigadier GeneralKhudr Khudr | | Head of the Latakia branch of the General Intelligence Directorate. Responsible for the torture of opponents in custody. | 24.7.2012
11. | Brigadier GeneralIbrahim Ma’ala | | Head of branch 285 (Damascus) of the General Intelligence Directorate (replaced Brig. Gen. Hussam Fendi at end 2011). Responsible for the torture of opponents in custody. | 24.7.2012
12. | Brigadier GeneralFiras Al-Hamed | | Head of branch 318 (Homs) of the General Intelligence Directorate. Responsible for the torture of opponents in custody. | 24.7.2012
13. | Brigadier GeneralHussam Luqa | | Since April 2012, head of the Homs branch of the Political Security Directorate (succeeded Brig. Gen. Nasr al-Ali). Responsible for the torture of opponents in custody. | 24.7.2012
14. | Brigadier GeneralTaha Taha | | Site manager of the Latakia branch of the Political Security Directorate. Responsible for the torture of opponents in custody. | 24.7.2012
15. | Brigadier GeneralNasr al-Ali | | Since April 2012 manager of the Deraa site of the Political Security Directorate (ex-head of the Homs branch). Responsible for the torture of opponents in custody. | 24.7.2012
16. | Bassel Bilal | | Police officer at Idlib central prison; has taken part directly in acts of torture of opponents held in Idlib central prison. | 24.7.2012
17. | Ahmad Kafan | | Police officer at Idlib central prison; has taken part directly in acts of torture of opponents held in Idlib central prison. | 24.7.2012
18. | Bassam al-Misri | | Police officer at Idlib central prison; has taken part directly in acts of torture of opponents held in Idlib central prison. | 24.7.2012
19. | Ahmed al-Jarroucheh | Date of birth: 1957 | Head of the foreign branch of General Intelligence (branch 279). As such, responsible for General Intelligence arrangements in Syrian embassies. He participates directly in the repression implemented by the Syrian authorities against opponents and in particular has responsibility for repression of the Syrian opposition abroad. | 24.7.2012
20. | Michel Kassouha(a.k.a. Ahmed Salem; a.k.a. Ahmed Salem Hassan) | Date of birth: 1 February 1948 | Member of the Syrian security services since the early 1970s, he is involved in combating opposition in France and Germany. Since March 2006, has been responsible for public relations of branch 273 of the Syrian General Intelligence Directorate. A longstanding member of the managerial staff, he is close to General Intelligence Directorate head Ali Mamlouk, one of the top security officials of the regime who has been subject to EU restrictive measures since 9 May 2011. He directly supports the regime’s repression of opponents and is responsible inter alia for repression of the Syrian opposition abroad. | 24.7.2012
21. | General Ghassan Jaoudat Ismail | Date of birth: 1960Place of origin: Drekish, Tartus region. | Responsible for the missions branch of the air force intelligence service, which, in cooperation with the special operations branch, manages the elite troops of the air force intelligence service, who play an important role in the repression conducted by the regime. As such, Ghassan Jaoudat Ismail is one of the military leaders directly implementing the repression of opponents conducted by the regime. | 24.7.2012
22. | General Amer al-Achi (a.k.a. Amis al Ashi; a.k.a. Ammar Aachi; a.k.a. Amer Ashi) | | Graduate of the military school of Aleppo, head of the intelligence branch of the air force intelligence service (since 2012), close to Daoud Rajah, Syrian Minister for Defence. Through his role in the air force intelligence service, Amer al-Achi is implicated in the repression of the Syrian opposition. | 24.7.2012
23. | General Mohammed Ali Nasr (or: Mohammed Ali Naser) | Date of birth: around 1964 | Close to Maher al-Assad, younger brother of the President. Most of his career has been spent in the Republican Guard. In 2010 he joined the internal branch (or branch 251) of the General Intelligence Directorate which is responsible for combating the political opposition. As one of its senior officers, General Mohammed Ali is directly involved in the repression of opponents. | 24.7.2012
24. | General Issam Hallaq | | Air Force Chief of Staff since 2010. Commands air operations against opponents. | 24.7.2012
25. | Ezzedine Ismael | Date of birth: middle of the 1940s (probably 1947).Place of birth: Bastir. Jableh region. | Retired general, longstanding member of the managerial staff of the air force intelligence service, of which he became the head in the early 2000s. Was appointed political and security adviser to the President in 2006. As political and security adviser to the Syrian president, Ezzedine Ismael is implicated in the political repression conducted by the regime against the opposition. | 24.7.2012
26. | Samir Joumaa (a.k.a. Abou Sami) | Date of birth: around 1962 | For almost 20 years he has been head of the office of Mohammad Nassif Kheir Bek, one of the main security advisers of Bashar al-Assad (and officially deputy to the Vice-President, Farouk al-Sharaa). Samir Joumaa’s closeness to Bashar al-Assad and Mohammed Nassif Kheir Bek means that he is implicated in the policy of repression conducted by the regime against its opponents. | 24.7.2012

Entities

| Name | Identifying information | Reasons | Date of listing
1. | Drex Technologies S.A. | Incorporation date: 4 July 2000Incorporation number: 394678Director: Rami MakhloufRegistered agent: Mossack Fonseca & Co (BVI) Ltd | Drex Technologies is wholly owned by Rami Makhlouf, who is listed under EU sanctions for providing financial support to the Syrian regime. Rami Makhlouf uses Drex Technologies to facilitate and manage his international financial holdings, including a majority share in SyriaTel, which the EU has previously listed on the grounds that it also provides financial support to the Syrian regime. | 24.7.2012
2. | Cotton Marketing Organisation | Address: Bab Al-Faraj P.O. Box 729, AleppoTél.: +96321 2239495/6/7/[email protected] | Address: Bab Al-Faraj P.O. Box 729, Aleppo | Tél.: +96321 2239495/6/7/8 | [email protected] | www.cmo.gov.sy | State-owned company. Provides financial support to the Syrian regime. |
Address: Bab Al-Faraj P.O. Box 729, Aleppo
Tél.: +96321 2239495/6/7/8
[email protected]
www.cmo.gov.sy
3. | Syrian Arab Airlines (a.k.a. SAA, a.k.a. Syrian Air) | Al-Mohafazeh Square, P.O. Box 417, Damascus, SyriaTel: +963112240774 | Al-Mohafazeh Square, P.O. Box 417, Damascus, Syria | Tel: +963112240774 | Public company controlled by the regime. Provides financial support for the regime. | 24.7.2012
Al-Mohafazeh Square, P.O. Box 417, Damascus, Syria
Tel: +963112240774

Pending: 32012D0347

30.6.2012 EN Official Journal of the European Union L 171/13
(1) On 14 August 2009, Monsanto Europe SA submitted to the competent authority of the Netherlands an application, in accordance with Articles 5 and 17 of Regulation (EC) No 1829/2003, for the placing on the market of foods, food ingredients, and feed containing, consisting of, or produced from MON 87701 × MON 89788 soybean (‘the application’).
(2) The application also covers the placing on the market of MON 87701 × MON 89788 soybean as present in products other than food and feed containing or consisting of MON 87701 × MON 89788 soybean for the same uses as any other soybean with the exception of cultivation.
(3) In accordance with Article 5(5) and Article 17(5) of Regulation (EC) No 1829/2003, the application includes the data and information required by Annexes III and IV to Directive 2001/18/EC of the European Parliament and of the Council of 12 March 2001 on the deliberate release into the environment of genetically modified organisms and repealing Council Directive 90/220/EEC(2)and information and conclusions about the risk assessment carried out in accordance with the principles set out in Annex II to Directive 2001/18/EC. It also includes a monitoring plan for environmental effects conforming with Annex VII to Directive 2001/18/EC.
(4) On 15 February 2012, the European Food Safety Authority (‘EFSA’) gave a favourable opinion in accordance with Articles 6 and 18 of Regulation (EC) No 1829/2003. It concluded that soybean MON 87701 × MON 89788, as described in the application, is as safe as its non-genetically modified counterpart with respect to potential effects on human and animal health or the environment(3).
(5) In its opinion, EFSA considered all the specific questions and concerns raised by the Member States in the context of the consultation of the national competent authorities as provided for by Article 6(4) and Article 18(4) of that Regulation.
(6) In its opinion, EFSA also concluded that the environmental monitoring plan, consisting of a general surveillance plan, submitted by the applicant is in line with the intended use of the products.
(7) Taking into account those considerations, authorisation should be granted for MON 87701 × MON 89788 soybean and all products containing it or consisting of it and for food and feed produced from it as described in the application (‘the products’). Products other than food and feed produced from MON 87701 × MON 89788 soybean do not fall under the scope of Regulation (EC) No 1829/2003 and are not covered by this authorisation.
(8) A unique identifier should be assigned to each genetically modified organism (‘GMO’) as provided for in Commission Regulation (EC) No 65/2004 of 14 January 2004 establishing a system for the development and assignment of unique identifiers for genetically modified organisms(4).
(9) On the basis of the EFSA opinion, no specific labelling requirements other than those provided for in Article 13(1) and Article 25(2) of Regulation (EC) No 1829/2003, appear to be necessary for foods, food ingredients and feed containing, consisting of, or produced from MON 87701 × MON 89788 soybean. However, in order to ensure the use of the products within the limits of the authorisation provided for by this Decision, the labelling of feed containing or consisting of the GMO and products other than food and feed containing or consisting of the GMO for which authorisation is requested should be complemented by a clear indication that the products in question must not be used for cultivation.
(10) Regulation (EC) No 1830/2003 of the European Parliament and of the Council of 22 September 2003 concerning the traceability and labelling of genetically modified organisms and the traceability of food and feed products produced from genetically modified organisms and amending Directive 2001/18/EC(5), lays down labelling requirements in Article 4(6) for products containing or consisting of GMOs. Traceability requirements for products containing or consisting of GMOs are laid down in paragraphs 1 to 5 of Article 4 and for food and feed produced from GMOs are laid down in Article 5 of that Regulation.
(11) The authorisation holder should submit annual reports on the implementation and the results of the activities set out in the monitoring plan for environmental effects. Those results should be presented in accordance with Commission Decision 2009/770/EC of 13 October 2009 establishing standard reporting formats for presenting the monitoring results of the deliberate release into the environment of genetically modified organisms, as or in products, for the purpose of placing on the market, pursuant to Directive 2001/18/EC of the European Parliament and of the Council(6). The EFSA opinion does not justify the imposition of specific conditions or restrictions for the placing on the market and/or specific conditions or restrictions for the use and handling, including post-market monitoring requirements for the use of the food and feed, or of specific conditions for the protection of particular ecosystems/environment and/or geographical areas, as provided for in point (e) of Article 6(5) and Article 18(5) of Regulation (EC) No 1829/2003.
(12) All relevant information on the authorisation of the products should be entered in the EU register of genetically modified food and feed, as provided for in Regulation (EC) No 1829/2003.
(13) This Decision is to be notified through the Biosafety Clearing-House to the Parties to the Cartagena Protocol on Biosafety to the Convention on Biological Diversity, pursuant to Article 9(1) and point (c) of Article 15(2) of Regulation (EC) No 1946/2003 of the European Parliament and of the Council of 15 July 2003 on transboundary movements of genetically modified organisms(7).
(14) The applicant has been consulted on the measures provided for in this Decision.
(15) The Standing Committee on the Food Chain and Animal Health has not delivered an opinion within the time limit laid down by its Chairman. An implementing act was deemed to be necessary and the chair submitted the draft implementing act to the appeal committee for further deliberation. The appeal committee did not deliver an opinion,
(a) foods and food ingredients containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean;
(b) feed containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean;
(c) MON-877Ø1-2 × MON-89788-1 soybean present in products other than food and feed containing it or consisting of it, for the same uses as any other soybean with the exception of cultivation.
Name : Monsanto Company
Address : 800 N. Lindbergh Boulevard, St Louis, Missouri 63167, UNITED STATES OF AMERICA
(1) Foods and food ingredients containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean.
(2) Feed containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean.
(3) Products other than food and feed containing or consisting of MON-877Ø1-2 × MON-89788-1 soybean for the same uses as any other soybean with the exception of cultivation.
(1) For the purposes of the specific labelling requirements laid down in Article 13(1) and Article 25(2) of Regulation (EC) No 1829/2003, and in Article 4(6) of Regulation (EC) No 1830/2003, the ‘name of the organism’ shall be ‘soybean’.
(2) The words ‘not for cultivation’ shall appear on the label of and in documents accompanying products containing or consisting of MON-877Ø1-2 × MON-89788-1 soybean referred to in points (b) and (c) of Article 2 of this Decision.
— Event specific real time PCR-based method for the quantification of MON-877Ø1-2 × MON-89788-1 soybean,
— validated on seeds by the Community Reference Laboratory established under Regulation (EC) No 1829/2003, published at http://gmo-crl.jrc.ec.europa.eu/statusofdoss.htm
— reference material: AOCS 0809-A and AOCS 0906-A (for MON87701) and AOCS 0906-B and AOCS 906-A (for MON89788) accessible via the American Oil Chemists Society at http://www.aocs.org/tech/crm
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Regulation (EC) No 1829/2003 of the European Parliament and of the Council of 22 September 2003 on genetically modified food and feed(1), and in particular Article 7(3) and Article 19(3) thereof,
(1) On 14 August 2009, Monsanto Europe SA submitted to the competent authority of the Netherlands an application, in accordance with Articles 5 and 17 of Regulation (EC) No 1829/2003, for the placing on the market of foods, food ingredients, and feed containing, consisting of, or produced from MON 87701 × MON 89788 soybean (‘the application’).
(2) The application also covers the placing on the market of MON 87701 × MON 89788 soybean as present in products other than food and feed containing or consisting of MON 87701 × MON 89788 soybean for the same uses as any other soybean with the exception of cultivation.
(3) In accordance with Article 5(5) and Article 17(5) of Regulation (EC) No 1829/2003, the application includes the data and information required by Annexes III and IV to Directive 2001/18/EC of the European Parliament and of the Council of 12 March 2001 on the deliberate release into the environment of genetically modified organisms and repealing Council Directive 90/220/EEC(2)and information and conclusions about the risk assessment carried out in accordance with the principles set out in Annex II to Directive 2001/18/EC. It also includes a monitoring plan for environmental effects conforming with Annex VII to Directive 2001/18/EC.
(4) On 15 February 2012, the European Food Safety Authority (‘EFSA’) gave a favourable opinion in accordance with Articles 6 and 18 of Regulation (EC) No 1829/2003. It concluded that soybean MON 87701 × MON 89788, as described in the application, is as safe as its non-genetically modified counterpart with respect to potential effects on human and animal health or the environment(3).
(5) In its opinion, EFSA considered all the specific questions and concerns raised by the Member States in the context of the consultation of the national competent authorities as provided for by Article 6(4) and Article 18(4) of that Regulation.
(6) In its opinion, EFSA also concluded that the environmental monitoring plan, consisting of a general surveillance plan, submitted by the applicant is in line with the intended use of the products.
(7) Taking into account those considerations, authorisation should be granted for MON 87701 × MON 89788 soybean and all products containing it or consisting of it and for food and feed produced from it as described in the application (‘the products’). Products other than food and feed produced from MON 87701 × MON 89788 soybean do not fall under the scope of Regulation (EC) No 1829/2003 and are not covered by this authorisation.
(8) A unique identifier should be assigned to each genetically modified organism (‘GMO’) as provided for in Commission Regulation (EC) No 65/2004 of 14 January 2004 establishing a system for the development and assignment of unique identifiers for genetically modified organisms(4).
(9) On the basis of the EFSA opinion, no specific labelling requirements other than those provided for in Article 13(1) and Article 25(2) of Regulation (EC) No 1829/2003, appear to be necessary for foods, food ingredients and feed containing, consisting of, or produced from MON 87701 × MON 89788 soybean. However, in order to ensure the use of the products within the limits of the authorisation provided for by this Decision, the labelling of feed containing or consisting of the GMO and products other than food and feed containing or consisting of the GMO for which authorisation is requested should be complemented by a clear indication that the products in question must not be used for cultivation.
(10) Regulation (EC) No 1830/2003 of the European Parliament and of the Council of 22 September 2003 concerning the traceability and labelling of genetically modified organisms and the traceability of food and feed products produced from genetically modified organisms and amending Directive 2001/18/EC(5), lays down labelling requirements in Article 4(6) for products containing or consisting of GMOs. Traceability requirements for products containing or consisting of GMOs are laid down in paragraphs 1 to 5 of Article 4 and for food and feed produced from GMOs are laid down in Article 5 of that Regulation.
(11) The authorisation holder should submit annual reports on the implementation and the results of the activities set out in the monitoring plan for environmental effects. Those results should be presented in accordance with Commission Decision 2009/770/EC of 13 October 2009 establishing standard reporting formats for presenting the monitoring results of the deliberate release into the environment of genetically modified organisms, as or in products, for the purpose of placing on the market, pursuant to Directive 2001/18/EC of the European Parliament and of the Council(6). The EFSA opinion does not justify the imposition of specific conditions or restrictions for the placing on the market and/or specific conditions or restrictions for the use and handling, including post-market monitoring requirements for the use of the food and feed, or of specific conditions for the protection of particular ecosystems/environment and/or geographical areas, as provided for in point (e) of Article 6(5) and Article 18(5) of Regulation (EC) No 1829/2003.
(12) All relevant information on the authorisation of the products should be entered in the EU register of genetically modified food and feed, as provided for in Regulation (EC) No 1829/2003.
(13) This Decision is to be notified through the Biosafety Clearing-House to the Parties to the Cartagena Protocol on Biosafety to the Convention on Biological Diversity, pursuant to Article 9(1) and point (c) of Article 15(2) of Regulation (EC) No 1946/2003 of the European Parliament and of the Council of 15 July 2003 on transboundary movements of genetically modified organisms(7).
(14) The applicant has been consulted on the measures provided for in this Decision.
(15) The Standing Committee on the Food Chain and Animal Health has not delivered an opinion within the time limit laid down by its Chairman. An implementing act was deemed to be necessary and the chair submitted the draft implementing act to the appeal committee for further deliberation. The appeal committee did not deliver an opinion,
HAS ADOPTED THIS DECISION:

Genetically modified organism and unique identifier
Article 1
Genetically modified soybean MON 87701 × MON 89788 is assigned the unique identifier MON-877Ø1-2 × MON-89788-1, as provided for in Regulation (EC) No 65/2004.

Authorisation
Article 2
The following products are authorised for the purposes of Article 4(2) and Article 16(2) of Regulation (EC) No 1829/2003 in accordance with the conditions set out in this Decision:
(a)
foods and food ingredients containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean;
(b)
feed containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean;
(c)
MON-877Ø1-2 × MON-89788-1 soybean present in products other than food and feed containing it or consisting of it, for the same uses as any other soybean with the exception of cultivation.

Labelling
Article 3
1. For the purposes of the labelling requirements laid down in Article 13(1) and Article 25(2) of Regulation (EC) No 1829/2003 and in Article 4(6) of Regulation (EC) No 1830/2003, the ‘name of the organism’ shall be ‘soybean’.
2. The words ‘not for cultivation’ shall appear on the label of and in documents accompanying products containing or consisting of MON-877Ø1-2 × MON-89788-1 soybean referred to in points (b) and (c) of Article 2.

Monitoring for environmental effects
Article 4
1. The authorisation holder shall ensure that the monitoring plan for environmental effects, as set out in point (h) of the Annex, is put in place and implemented.
2. The authorisation holder shall submit to the Commission annual reports on the implementation and the results of the activities set out in the monitoring plan in accordance with Decision 2009/770/EC.

EU register
Article 5
The information set out in the Annex to this Decision shall be entered in the EU register of genetically modified food and feed, as provided for in Article 28 of Regulation (EC) No 1829/2003.

Authorisation holder
Article 6
The authorisation holder shall be Monsanto Company, United States, represented by Monsanto Europe SA, Belgium.

Validity
Article 7
This Decision shall apply for a period of 10 years from the date of its notification.

Addressee
Article 8
This Decision is addressed to Monsanto Europe SA, Avenue de Tervuren/Tervurenlaan 270-272, 1150 Bruxelles/Brussel, BELGIQUE/BELGIË.

THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Regulation (EC) No 1829/2003 of the European Parliament and of the Council of 22 September 2003 on genetically modified food and feed(1), and in particular Article 7(3) and Article 19(3) thereof,
(1) On 14 August 2009, Monsanto Europe SA submitted to the competent authority of the Netherlands an application, in accordance with Articles 5 and 17 of Regulation (EC) No 1829/2003, for the placing on the market of foods, food ingredients, and feed containing, consisting of, or produced from MON 87701 × MON 89788 soybean (‘the application’).
(2) The application also covers the placing on the market of MON 87701 × MON 89788 soybean as present in products other than food and feed containing or consisting of MON 87701 × MON 89788 soybean for the same uses as any other soybean with the exception of cultivation.
(3) In accordance with Article 5(5) and Article 17(5) of Regulation (EC) No 1829/2003, the application includes the data and information required by Annexes III and IV to Directive 2001/18/EC of the European Parliament and of the Council of 12 March 2001 on the deliberate release into the environment of genetically modified organisms and repealing Council Directive 90/220/EEC(2)and information and conclusions about the risk assessment carried out in accordance with the principles set out in Annex II to Directive 2001/18/EC. It also includes a monitoring plan for environmental effects conforming with Annex VII to Directive 2001/18/EC.
(4) On 15 February 2012, the European Food Safety Authority (‘EFSA’) gave a favourable opinion in accordance with Articles 6 and 18 of Regulation (EC) No 1829/2003. It concluded that soybean MON 87701 × MON 89788, as described in the application, is as safe as its non-genetically modified counterpart with respect to potential effects on human and animal health or the environment(3).
(5) In its opinion, EFSA considered all the specific questions and concerns raised by the Member States in the context of the consultation of the national competent authorities as provided for by Article 6(4) and Article 18(4) of that Regulation.
(6) In its opinion, EFSA also concluded that the environmental monitoring plan, consisting of a general surveillance plan, submitted by the applicant is in line with the intended use of the products.
(7) Taking into account those considerations, authorisation should be granted for MON 87701 × MON 89788 soybean and all products containing it or consisting of it and for food and feed produced from it as described in the application (‘the products’). Products other than food and feed produced from MON 87701 × MON 89788 soybean do not fall under the scope of Regulation (EC) No 1829/2003 and are not covered by this authorisation.
(8) A unique identifier should be assigned to each genetically modified organism (‘GMO’) as provided for in Commission Regulation (EC) No 65/2004 of 14 January 2004 establishing a system for the development and assignment of unique identifiers for genetically modified organisms(4).
(9) On the basis of the EFSA opinion, no specific labelling requirements other than those provided for in Article 13(1) and Article 25(2) of Regulation (EC) No 1829/2003, appear to be necessary for foods, food ingredients and feed containing, consisting of, or produced from MON 87701 × MON 89788 soybean. However, in order to ensure the use of the products within the limits of the authorisation provided for by this Decision, the labelling of feed containing or consisting of the GMO and products other than food and feed containing or consisting of the GMO for which authorisation is requested should be complemented by a clear indication that the products in question must not be used for cultivation.
(10) Regulation (EC) No 1830/2003 of the European Parliament and of the Council of 22 September 2003 concerning the traceability and labelling of genetically modified organisms and the traceability of food and feed products produced from genetically modified organisms and amending Directive 2001/18/EC(5), lays down labelling requirements in Article 4(6) for products containing or consisting of GMOs. Traceability requirements for products containing or consisting of GMOs are laid down in paragraphs 1 to 5 of Article 4 and for food and feed produced from GMOs are laid down in Article 5 of that Regulation.
(11) The authorisation holder should submit annual reports on the implementation and the results of the activities set out in the monitoring plan for environmental effects. Those results should be presented in accordance with Commission Decision 2009/770/EC of 13 October 2009 establishing standard reporting formats for presenting the monitoring results of the deliberate release into the environment of genetically modified organisms, as or in products, for the purpose of placing on the market, pursuant to Directive 2001/18/EC of the European Parliament and of the Council(6). The EFSA opinion does not justify the imposition of specific conditions or restrictions for the placing on the market and/or specific conditions or restrictions for the use and handling, including post-market monitoring requirements for the use of the food and feed, or of specific conditions for the protection of particular ecosystems/environment and/or geographical areas, as provided for in point (e) of Article 6(5) and Article 18(5) of Regulation (EC) No 1829/2003.
(12) All relevant information on the authorisation of the products should be entered in the EU register of genetically modified food and feed, as provided for in Regulation (EC) No 1829/2003.
(13) This Decision is to be notified through the Biosafety Clearing-House to the Parties to the Cartagena Protocol on Biosafety to the Convention on Biological Diversity, pursuant to Article 9(1) and point (c) of Article 15(2) of Regulation (EC) No 1946/2003 of the European Parliament and of the Council of 15 July 2003 on transboundary movements of genetically modified organisms(7).
(14) The applicant has been consulted on the measures provided for in this Decision.
(15) The Standing Committee on the Food Chain and Animal Health has not delivered an opinion within the time limit laid down by its Chairman. An implementing act was deemed to be necessary and the chair submitted the draft implementing act to the appeal committee for further deliberation. The appeal committee did not deliver an opinion,
HAS ADOPTED THIS DECISION:

Genetically modified organism and unique identifier

Genetically modified soybean MON 87701 × MON 89788 is assigned the unique identifier MON-877Ø1-2 × MON-89788-1, as provided for in Regulation (EC) No 65/2004.

Authorisation

The following products are authorised for the purposes of Article 4(2) and Article 16(2) of Regulation (EC) No 1829/2003 in accordance with the conditions set out in this Decision:
(a)
foods and food ingredients containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean;
(b)
feed containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean;
(c)
MON-877Ø1-2 × MON-89788-1 soybean present in products other than food and feed containing it or consisting of it, for the same uses as any other soybean with the exception of cultivation.

Labelling

1. For the purposes of the labelling requirements laid down in Article 13(1) and Article 25(2) of Regulation (EC) No 1829/2003 and in Article 4(6) of Regulation (EC) No 1830/2003, the ‘name of the organism’ shall be ‘soybean’.
2. The words ‘not for cultivation’ shall appear on the label of and in documents accompanying products containing or consisting of MON-877Ø1-2 × MON-89788-1 soybean referred to in points (b) and (c) of Article 2.

Monitoring for environmental effects

1. The authorisation holder shall ensure that the monitoring plan for environmental effects, as set out in point (h) of the Annex, is put in place and implemented.
2. The authorisation holder shall submit to the Commission annual reports on the implementation and the results of the activities set out in the monitoring plan in accordance with Decision 2009/770/EC.

EU register

The information set out in the Annex to this Decision shall be entered in the EU register of genetically modified food and feed, as provided for in Article 28 of Regulation (EC) No 1829/2003.

Authorisation holder

The authorisation holder shall be Monsanto Company, United States, represented by Monsanto Europe SA, Belgium.

Validity

This Decision shall apply for a period of 10 years from the date of its notification.

Addressee

This Decision is addressed to Monsanto Europe SA, Avenue de Tervuren/Tervurenlaan 270-272, 1150 Bruxelles/Brussel, BELGIQUE/BELGIË.

(a)   Applicant and authorisation holder

ANNEX
Name | : | Monsanto Company
Address | : | 800 N. Lindbergh Boulevard, St Louis, Missouri 63167, UNITED STATES OF AMERICARepresented by Monsanto Europe SA, Avenue de Tervuren/Tervurenlaan 270-272, 1150 Bruxelles/Brussel, BELGIQUE/BELGIË.
(b) Designation and specification of the products

(1) | Foods and food ingredients containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean.
(2) | Feed containing, consisting of, or produced from MON-877Ø1-2 × MON-89788-1 soybean.
(3) | Products other than food and feed containing or consisting of MON-877Ø1-2 × MON-89788-1 soybean for the same uses as any other soybean with the exception of cultivation.The genetically modified MON-877Ø1-2 × MON-89788-1 soybean, as described in the application, is produced by crosses between soybean containing MON-877Ø1-2 and MON-89788-1 events and expresses the Cry1Ac protein which confers protection against certain lepidopteran pests and CP4 EPSPS protein which confers tolerance to the glyphosate herbicide.
(c) Labelling

(1) | For the purposes of the specific labelling requirements laid down in Article 13(1) and Article 25(2) of Regulation (EC) No 1829/2003, and in Article 4(6) of Regulation (EC) No 1830/2003, the ‘name of the organism’ shall be ‘soybean’.
(2) | The words ‘not for cultivation’ shall appear on the label of and in documents accompanying products containing or consisting of MON-877Ø1-2 × MON-89788-1 soybean referred to in points (b) and (c) of Article 2 of this Decision.(d) Method for detection

— | Event specific real time PCR-based method for the quantification of MON-877Ø1-2 × MON-89788-1 soybean,
— | validated on seeds by the Community Reference Laboratory established under Regulation (EC) No 1829/2003, published at http://gmo-crl.jrc.ec.europa.eu/statusofdoss.htm
— | reference material: AOCS 0809-A and AOCS 0906-A (for MON87701) and AOCS 0906-B and AOCS 906-A (for MON89788) accessible via the American Oil Chemists Society at http://www.aocs.org/tech/crm(e) Unique identifier
MON-877Ø1-2 × MON-89788-1
(f) Information required under Annex II to the Cartagena Protocol on Biosafety to the Convention on Biological Diversity
Biosafety Clearing-House, Record ID: see [to be completed when notified]
(g) Conditions or restrictions on the placing on the market, use or handling of the products
Not required.
(h) Monitoring plan
Monitoring plan for environmental effects conforming with Annex VII to Directive 2001/18/EC.
[Link:plan published on the internet]
(i) Post-market monitoring requirements for the use of the food for human consumption
Not required.
Note:links to relevant documents may need to be modified over time. Those modifications will be made available to the public via the updating of the EU register of genetically modified food and feed.

Pending: 32012D0333

26.6.2012 EN Official Journal of the European Union L 165/72
(1) On 27 December 2001, the Council adopted Common Position 2001/931/CFSP(1).
(2) On 22 December 2011, the Council adopted Decision 2011/872/CFSP updating the list of persons, groups and entities subject to Articles 2, 3 and 4 of Common Position 2001/931/CFSP(2).
(3) In accordance with Article 1(6) of Common Position 2001/931/CFSP, it is necessary to carry out a complete review of the list of persons, groups and entities to which Decision 2011/872/CFSP applies.
(4) This Decision sets out the result of the review that the Council has carried out in respect of the persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply.
(5) The Council has concluded that the persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply have been involved in terrorist acts within the meaning of Article 1(2) and (3) of Common Position 2001/931/CFSP, that a decision has been taken with respect to them by a competent authority within the meaning of Article 1(4) of that Common Position, and that they should continue to be subject to the specific restrictive measures provided for therein.
(6) The list of the persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply should be updated accordingly, and Decision 2011/872/CFSP should be repealed,
1. ABDOLLAHI Hamed (a.k.a Mustafa Abdullahi), born August 11, 1960 in Iran. Passport: D9004878.
2. AL-NASSER, Abdelkarim Hussein Mohamed, born in Al Ihsa (Saudi Arabia), citizen of Saudi Arabia
3. AL YACOUB, Ibrahim Salih Mohammed, born 16.10.1966 in Tarut (Saudi Arabia), citizen of Saudi Arabia
4. ARBABSIAR Manssor (a.k.a. Mansour Arbabsiar), born March 6 or 15, 1955 in Iran. Iranian and US national. Passport: C2002515 (Iran); Passport: 477845448 (USA). National ID no.: 07442833, expiry date 15 March 2016 (USA driving licence).
5. BOUYERI, Mohammed (a.k.a. Abu ZUBAIR, a.k.a. SOBIAR, a.k.a. Abu ZOUBAIR), born 8.3.1978 in Amsterdam (The Netherlands) – member of the "Hofstadgroep"
6. FAHAS, Sofiane Yacine, born 10.9.1971 in Algiers (Algeria) – member of "al-Takfir" and "al-Hijra"
7. IZZ-AL-DIN, Hasan (a.k.a GARBAYA, Ahmed, a.k.a. SA-ID, a.k.a. SALWWAN, Samir), Lebanon, born 1963 in Lebanon, citizen of Lebanon
8. MOHAMMED, Khalid Shaikh (a.k.a. ALI, Salem, a.k.a. BIN KHALID, Fahd Bin Adballah, a.k.a. HENIN, Ashraf Refaat Nabith, a.k.a. WADOOD, Khalid Adbul), born 14.4.1965 or 1.3.1964 in Pakistan, passport No 488555
9. SHAHLAI Abdul Reza (a.k.a Abdol Reza Shala'i, a.k.a. Abd-al Reza Shalai, a.k.a. Abdorreza Shahlai, a.k.a. Abdolreza Shahla'i, a.k.a. Abdul-Reza Shahlaee, a.k.a.Hajj Yusef, a.k.a. Haji Yusif, a.k.a.Hajji Yasir, a.k.a.Hajji Yusif, a.k.a.Yusuf Abu-al-Karkh), born circa 1957 in Iran. Addresses: (1) Kermanshah, Iran, (2) Mehran Military Base, Ilam Province, Iran.
10. SHAKURI Ali Gholam, born circa 1965 in Tehran, Iran
11. SOLEIMANI Qasem (a.k.a Ghasem Soleymani, a.k.a Qasmi Sulayman, a.k.a Qasem Soleymani, a.k.a Qasem Solaimani, a.k.a Qasem Salimani, a.k.a Qasem Solemani, a.k.a Qasem Sulaimani, a.k.a Qasem Sulemani), born March 11, 1957 in Iran. Iranian national. Passport: 008827 (Iran Diplomatic), issued 1999. Title: Major General.
12. WALTERS, Jason Theodore James (a.k.a. Abdullah, a.k.a. David), born 6.3.1985 in Amersfoort (The Netherlands), passport (The Netherlands) No. NE8146378 – member of the "Hofstadgroep"
1. "Abu Nidal Organisation" – "ANO" (a.k.a. "Fatah Revolutionary Council", a.k.a. "Arab Revolutionary Brigades", a.k.a. "Black September", a.k.a. "Revolutionary Organisation of Socialist Muslims")
2. "Al-Aqsa Martyrs' Brigade"
3. "Al-Aqsa e.V."
4. "Al-Takfir" and "Al-Hijra"
5. "Babbar Khalsa"
6. "Communist Party of the Philippines", including "New People's Army" – "NPA", Philippines
7. "Gama'a al-Islamiyya" (a.k.a. "Al-Gama'a al-Islamiyya") ("Islamic Group" – "IG")
8. "İslami Büyük Doğu Akıncılar Cephesi" – "IBDA-C" ("Great Islamic Eastern Warriors Front")
9. "Hamas", including "Hamas-Izz al-Din al-Qassem"
10. "Hizbul Mujahideen" – "HM"
11. "Hofstadgroep"
12. "Holy Land Foundation for Relief and Development"
13. "International Sikh Youth Federation" – "ISYF"
14. "Khalistan Zindabad Force" – "KZF"
15. "Kurdistan Workers' Party" – "PKK", (a.k.a. "KADEK", a.k.a. "KONGRA-GEL‧)
16. "Liberation Tigers of Tamil Eelam" – "LTTE"
17. "Ejército de Liberación Nacional" ("National Liberation Army")
18. "Palestinian Islamic Jihad" – "PIJ"
19. "Popular Front for the Liberation of Palestine" – "PFLP"
20. "Popular Front for the Liberation of Palestine – General Command" (a.k.a. "PFLP – General Command")
21. "Fuerzas armadas revolucionarias de Colombia" – "FARC" ("Revolutionary Armed Forces of Colombia")
22. "Devrimci Halk Kurtuluș Partisi-Cephesi" – "DHKP/C" (a.k.a. "Devrimci Sol" ("Revolutionary Left"), a.k.a. "Dev Sol") ("Revolutionary People's Liberation Army/Front/Party")
23. "Sendero Luminoso" – "SL" ("Shining Path")
24. "Stichting Al Aqsa" (a.k.a. "Stichting Al Aqsa Nederland", a.k.a. "Al Aqsa Nederland")
25. "Teyrbazen Azadiya Kurdistan" – "TAK" (a.k.a. "Kurdistan Freedom Falcons", a.k.a. "Kurdistan Freedom Hawks")
THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union, and in particular Article 29 thereof,
(1) On 27 December 2001, the Council adopted Common Position 2001/931/CFSP(1).
(2) On 22 December 2011, the Council adopted Decision 2011/872/CFSP updating the list of persons, groups and entities subject to Articles 2, 3 and 4 of Common Position 2001/931/CFSP(2).
(3) In accordance with Article 1(6) of Common Position 2001/931/CFSP, it is necessary to carry out a complete review of the list of persons, groups and entities to which Decision 2011/872/CFSP applies.
(4) This Decision sets out the result of the review that the Council has carried out in respect of the persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply.
(5) The Council has concluded that the persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply have been involved in terrorist acts within the meaning of Article 1(2) and (3) of Common Position 2001/931/CFSP, that a decision has been taken with respect to them by a competent authority within the meaning of Article 1(4) of that Common Position, and that they should continue to be subject to the specific restrictive measures provided for therein.
(6) The list of the persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply should be updated accordingly, and Decision 2011/872/CFSP should be repealed,
HAS ADOPTED THIS DECISION:

Article 1
The list of persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply shall be that set out in the Annex to this Decision.

Article 2
Decision 2011/872/CFSP is hereby repealed.

Article 3
This Decision shall enter into force on the day of its publication in theOfficial Journal of the European Union.

THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union, and in particular Article 29 thereof,
(1) On 27 December 2001, the Council adopted Common Position 2001/931/CFSP(1).
(2) On 22 December 2011, the Council adopted Decision 2011/872/CFSP updating the list of persons, groups and entities subject to Articles 2, 3 and 4 of Common Position 2001/931/CFSP(2).
(3) In accordance with Article 1(6) of Common Position 2001/931/CFSP, it is necessary to carry out a complete review of the list of persons, groups and entities to which Decision 2011/872/CFSP applies.
(4) This Decision sets out the result of the review that the Council has carried out in respect of the persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply.
(5) The Council has concluded that the persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply have been involved in terrorist acts within the meaning of Article 1(2) and (3) of Common Position 2001/931/CFSP, that a decision has been taken with respect to them by a competent authority within the meaning of Article 1(4) of that Common Position, and that they should continue to be subject to the specific restrictive measures provided for therein.
(6) The list of the persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply should be updated accordingly, and Decision 2011/872/CFSP should be repealed,
HAS ADOPTED THIS DECISION:
The list of persons, groups and entities to which Articles 2, 3 and 4 of Common Position 2001/931/CFSP apply shall be that set out in the Annex to this Decision.
Decision 2011/872/CFSP is hereby repealed.
This Decision shall enter into force on the day of its publication in theOfficial Journal of the European Union.

List of persons, groups and entities referred to in Article 1

ANNEX1. Persons

1. | ABDOLLAHI Hamed (a.k.a Mustafa Abdullahi), born August 11, 1960 in Iran. Passport: D9004878.
2. | AL-NASSER, Abdelkarim Hussein Mohamed, born in Al Ihsa (Saudi Arabia), citizen of Saudi Arabia
3. | AL YACOUB, Ibrahim Salih Mohammed, born 16.10.1966 in Tarut (Saudi Arabia), citizen of Saudi Arabia
4. | ARBABSIAR Manssor (a.k.a. Mansour Arbabsiar), born March 6 or 15, 1955 in Iran. Iranian and US national. Passport: C2002515 (Iran); Passport: 477845448 (USA). National ID no.: 07442833, expiry date 15 March 2016 (USA driving licence).
5. | BOUYERI, Mohammed (a.k.a. Abu ZUBAIR, a.k.a. SOBIAR, a.k.a. Abu ZOUBAIR), born 8.3.1978 in Amsterdam (The Netherlands) – member of the “Hofstadgroep”
6. | FAHAS, Sofiane Yacine, born 10.9.1971 in Algiers (Algeria) – member of “al-Takfir” and “al-Hijra”
7. | IZZ-AL-DIN, Hasan (a.k.a GARBAYA, Ahmed, a.k.a. SA-ID, a.k.a. SALWWAN, Samir), Lebanon, born 1963 in Lebanon, citizen of Lebanon
8. | MOHAMMED, Khalid Shaikh (a.k.a. ALI, Salem, a.k.a. BIN KHALID, Fahd Bin Adballah, a.k.a. HENIN, Ashraf Refaat Nabith, a.k.a. WADOOD, Khalid Adbul), born 14.4.1965 or 1.3.1964 in Pakistan, passport No 488555
9. | SHAHLAI Abdul Reza (a.k.a Abdol Reza Shala’i, a.k.a. Abd-al Reza Shalai, a.k.a. Abdorreza Shahlai, a.k.a. Abdolreza Shahla’i, a.k.a. Abdul-Reza Shahlaee, a.k.a.Hajj Yusef, a.k.a. Haji Yusif, a.k.a.Hajji Yasir, a.k.a.Hajji Yusif, a.k.a.Yusuf Abu-al-Karkh), born circa 1957 in Iran. Addresses: (1) Kermanshah, Iran, (2) Mehran Military Base, Ilam Province, Iran.
10. | SHAKURI Ali Gholam, born circa 1965 in Tehran, Iran
11. | SOLEIMANI Qasem (a.k.a Ghasem Soleymani, a.k.a Qasmi Sulayman, a.k.a Qasem Soleymani, a.k.a Qasem Solaimani, a.k.a Qasem Salimani, a.k.a Qasem Solemani, a.k.a Qasem Sulaimani, a.k.a Qasem Sulemani), born March 11, 1957 in Iran. Iranian national. Passport: 008827 (Iran Diplomatic), issued 1999. Title: Major General.
12. | WALTERS, Jason Theodore James (a.k.a. Abdullah, a.k.a. David), born 6.3.1985 in Amersfoort (The Netherlands), passport (The Netherlands) No. NE8146378 – member of the “Hofstadgroep”2. Groups and entities

1. | “Abu Nidal Organisation” – “ANO” (a.k.a. “Fatah Revolutionary Council”, a.k.a. “Arab Revolutionary Brigades”, a.k.a. “Black September”, a.k.a. “Revolutionary Organisation of Socialist Muslims”)
2. | “Al-Aqsa Martyrs’ Brigade”
3. | “Al-Aqsa e.V.”
4. | “Al-Takfir” and “Al-Hijra”
5. | “Babbar Khalsa”
6. | “Communist Party of the Philippines”, including “New People’s Army” – “NPA”, Philippines
7. | “Gama’a al-Islamiyya” (a.k.a. “Al-Gama’a al-Islamiyya”) (“Islamic Group” – “IG”)
8. | “İslami Büyük Doğu Akıncılar Cephesi” – “IBDA-C” (“Great Islamic Eastern Warriors Front”)
9. | “Hamas”, including “Hamas-Izz al-Din al-Qassem”
10. | “Hizbul Mujahideen” – “HM”
11. | “Hofstadgroep”
12. | “Holy Land Foundation for Relief and Development”
13. | “International Sikh Youth Federation” – “ISYF”
14. | “Khalistan Zindabad Force” – “KZF”
15. | “Kurdistan Workers’ Party” – “PKK”, (a.k.a. “KADEK”, a.k.a. “KONGRA-GEL‧)
16. | “Liberation Tigers of Tamil Eelam” – “LTTE”
17. | “Ejército de Liberación Nacional” (“National Liberation Army”)
18. | “Palestinian Islamic Jihad” – “PIJ”
19. | “Popular Front for the Liberation of Palestine” – “PFLP”
20. | “Popular Front for the Liberation of Palestine – General Command” (a.k.a. “PFLP – General Command”)
21. | “Fuerzas armadas revolucionarias de Colombia” – “FARC” (“Revolutionary Armed Forces of Colombia”)
22. | “Devrimci Halk Kurtuluș Partisi-Cephesi” – “DHKP/C” (a.k.a. “Devrimci Sol” (“Revolutionary Left”), a.k.a. “Dev Sol”) (“Revolutionary People’s Liberation Army/Front/Party”)
23. | “Sendero Luminoso” – “SL” (“Shining Path”)
24. | “Stichting Al Aqsa” (a.k.a. “Stichting Al Aqsa Nederland”, a.k.a. “Al Aqsa Nederland”)
25. | “Teyrbazen Azadiya Kurdistan” – “TAK” (a.k.a. “Kurdistan Freedom Falcons”, a.k.a. “Kurdistan Freedom Hawks”)

Pending: 32012D0173

27.3.2012 EN Official Journal of the European Union L 89/66
(1) On 17 December 2004, the European Council endorsed the proposals allowing for the establishment of an operations centre and its terms of reference.
(2) On 18 June 2007, the Council approved the Guidelines for Command and Control Structure for the EU Civilian Operations in Crisis Management.
(3) On 7 April 2008, by Decision 2008/298/CFSP(1)the Council amended Decision 2001/80/CFSP of 22 January 2001 on the establishment of the Military Staff of the European Union(2)to specify, inter alia, the tasks of the Military Staff of the European Union (EUMS) in relation to the EU Operations Centre.
(4) On 10 November 2008, the Council adopted Joint Action 2008/851/CFSP(3)establishing operation Atalanta with the purpose of deterring piracy off the Somali coast.
(5) On 15 February 2010, the Council adopted Decision 2010/96/CFSP(4)on an EU military mission to contribute to the training of Somali security forces (EUTM Somalia).
(6) On 14 November 2011, the Council adopted a Strategic Framework for the Horn of Africa to guide the EU’s engagement in the region.
(7) On 1 December 2011, the Council agreed to accelerate planning for the activation of the EU Operations Centre for the Horn of Africa Common Security and Defence Policy (CSDP) missions and operation, in accordance with its terms of reference.
(8) On 16 December 2011, the Council agreed the Crisis Management Concept for the Regional Maritime Capacity Building (RMCB) mission, as a civilian CSDP mission with military expertise.
(9) On 23 January 2012, the Council agreed that the EU Operations Centre should be activated for the Horn of Africa CSDP missions and operation.
(10) The EU Operations Centre should facilitate coordination and improve synergies amongst the Horn of Africa CSDP missions and operation, in the context of the Strategic Framework for the Horn of Africa and in close liaison with the European Union Special Representative (EUSR) for the Horn of Africa.
(11) The EU Operations Centre should be supported by the existing structures of the EUMS, reinforced by the EUTM Somalia Support Element and the Atalanta Liaison Team.
(12) Bearing in mind the requirement to optimise its support for all CSDP missions and operations, the EUMS should provide support to the EU Operations Centre within its means and capabilities,
(a) to provide, using its military expertise and specialised planning expertise, direct support to the Civilian Operations Commander for the operational planning and conduct of the RMCB mission;
(b) to provide support to the EUTM Mission Commander and enhance strategic coordination between EUTM Somalia and the other CSDP mission and operation in the Horn of Africa;
(c) to liaise with Operation Atalanta;
(d) to provide support to the Crisis Management and Planning Directorate (CMPD), at its request, in its strategic planning for the CSDP missions and operation in the Horn of Africa;
(e) to facilitate interaction between the Horn of Africa CSDP missions and operation and the Brussels-based structures;
(f) to facilitate coordination and improve synergies amongst Operation Atalanta, EUTM Somalia, and RMCB, in the context of the Horn of Africa Strategy and in liaison with the European Union Special Representative for the Horn of Africa.
(a) staff provided by the EUMS;
(b) the EUTM Support Element;
(c) the Atalanta Liaison Team;
(d) staff seconded by Member States.
(a) ensuring availability and readiness of the staff, facilities and equipment of the EU Operations Centre;
(b) maintaining, updating and replacing the equipment of the EU Operations Centre;
(c) maintaining the premises used by the EU Operations Centre.
THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union, and in particular Articles 42(4) and 43(2) thereof,
Having regard to the proposal from the High Representative of the Union for Foreign Affairs and Security Policy,
(1) On 17 December 2004, the European Council endorsed the proposals allowing for the establishment of an operations centre and its terms of reference.
(2) On 18 June 2007, the Council approved the Guidelines for Command and Control Structure for the EU Civilian Operations in Crisis Management.
(3) On 7 April 2008, by Decision 2008/298/CFSP(1)the Council amended Decision 2001/80/CFSP of 22 January 2001 on the establishment of the Military Staff of the European Union(2)to specify, inter alia, the tasks of the Military Staff of the European Union (EUMS) in relation to the EU Operations Centre.
(4) On 10 November 2008, the Council adopted Joint Action 2008/851/CFSP(3)establishing operation Atalanta with the purpose of deterring piracy off the Somali coast.
(5) On 15 February 2010, the Council adopted Decision 2010/96/CFSP(4)on an EU military mission to contribute to the training of Somali security forces (EUTM Somalia).
(6) On 14 November 2011, the Council adopted a Strategic Framework for the Horn of Africa to guide the EU’s engagement in the region.
(7) On 1 December 2011, the Council agreed to accelerate planning for the activation of the EU Operations Centre for the Horn of Africa Common Security and Defence Policy (CSDP) missions and operation, in accordance with its terms of reference.
(8) On 16 December 2011, the Council agreed the Crisis Management Concept for the Regional Maritime Capacity Building (RMCB) mission, as a civilian CSDP mission with military expertise.
(9) On 23 January 2012, the Council agreed that the EU Operations Centre should be activated for the Horn of Africa CSDP missions and operation.
(10) The EU Operations Centre should facilitate coordination and improve synergies amongst the Horn of Africa CSDP missions and operation, in the context of the Strategic Framework for the Horn of Africa and in close liaison with the European Union Special Representative (EUSR) for the Horn of Africa.
(11) The EU Operations Centre should be supported by the existing structures of the EUMS, reinforced by the EUTM Somalia Support Element and the Atalanta Liaison Team.
(12) Bearing in mind the requirement to optimise its support for all CSDP missions and operations, the EUMS should provide support to the EU Operations Centre within its means and capabilities,
HAS ADOPTED THIS DECISION:

Activation of the EU Operations Centre
Article 1
1. The EU Operations Centre shall be activated in support of the Common Security and Defence Policy (CSDP) missions and operation in the Horn of Africa, namely Operation Atalanta, EUTM Somalia, and the planned civilian CSDP mission on Regional Maritime Capacity Building (RMCB).
2. The activation of the EU Operations Centre shall be without prejudice to the respective military and civilian chains of command of the missions and the operation, referred to in paragraph 1.

Mandate and tasks
Article 2
1. The EU Operations Centre shall provide support in the field of operational planning and conduct of Operation Atalanta, EUTM Somalia, and the future civilian CSDP mission on Regional Maritime Capacity Building (RMCB), with a view to increasing efficiency, coherence and synergies. In this framework the EU Operations Centre shall help facilitate information exchange and improve coordination and strengthen civil-military synergies.
2. The EU Operations Centre shall perform the following tasks:
(a)
to provide, using its military expertise and specialised planning expertise, direct support to the Civilian Operations Commander for the operational planning and conduct of the RMCB mission;
(b)
to provide support to the EUTM Mission Commander and enhance strategic coordination between EUTM Somalia and the other CSDP mission and operation in the Horn of Africa;
(c)
to liaise with Operation Atalanta;
(d)
to provide support to the Crisis Management and Planning Directorate (CMPD), at its request, in its strategic planning for the CSDP missions and operation in the Horn of Africa;
(e)
to facilitate interaction between the Horn of Africa CSDP missions and operation and the Brussels-based structures;
(f)
to facilitate coordination and improve synergies amongst Operation Atalanta, EUTM Somalia, and RMCB, in the context of the Horn of Africa Strategy and in liaison with the European Union Special Representative for the Horn of Africa.

Head of the EU Operations Centre
Article 3
1. Captain (Navy) Ad VAN DER LINDE is hereby appointed Head of the EU Operations Centre for a period of two years, which may be renewed if the Council so decides.
2. The Head of the EU Operations Centre shall carry out his functions under the political control and strategic direction of the Political and Security Committee (PSC), and, as appropriate, under the military direction of the European Union Military Committee (EUMC).
3. The Head of the EU Operations Centre shall exercise authority over the staff of the EU Operations Centre for all issues related to the mandate and tasks of the EU Operations Centre.
4. The Head of the EU Operations Centre shall be responsible for responding to the requests addressed to the EU Operations Centre by the Civilian Operation Commander, the Operation Commander for Operation Atalanta, the EUTM Mission Commander, and CMPD. He shall ensure the proper functioning of the EU Operations Centre and coordinate the efficient use of its capacities. The final responsibility for operational planning documents and decisions on the conduct of the missions and the operation shall remain respectively with the Civilian Operation Commander, the EUTM Mission Commander, and the Operation Commander for Operation Atalanta.
5. Within the limits of his responsibility, the Head of the EU Operations Centre shall regularly report to EUMC and to PSC.

Staff
Article 4
1. The Human resources of the EU Operations Centre shall comprise:
(a)
staff provided by the EUMS;
(b)
the EUTM Support Element;
(c)
the Atalanta Liaison Team;
(d)
staff seconded by Member States.
2. The human resources put at the disposal of the EU Operations Centre shall cover all military expertise required to implement its mandate and tasks properly on the basis of an implementation plan presented to the PSC and shall be subject to regular review. The precise definition of the expertise required shall be the responsibility of the Head of the EU Operations Centre, in close consultation with the Operation and Mission Commanders, the Civilian Operation Commander, and the EUMS.
3. All staff shall respect the security principles and minimum standards established by Council Decision 2011/292/EU of 31 March 2011 on the security rules for protecting EU classified information(5).

Organisation
Article 5
The EU Operations Centre shall be organised along functional responsibilities corresponding to the requirements of the CSDP missions and operation which it supports.

Support by the EUMS
Article 6
The EUMS shall, within its means and capabilities, provide support to the EU Operations Centre in accordance with its terms of reference through:
(a)
ensuring availability and readiness of the staff, facilities and equipment of the EU Operations Centre;
(b)
maintaining, updating and replacing the equipment of the EU Operations Centre;
(c)
maintaining the premises used by the EU Operations Centre.

Financing
Article 7
1. The staff provided by EUMS shall be financed in accordance with the rules applicable to the EUMS.
2. The staff provided by Member States shall be seconded national experts on free secondment.
3. Travel and other costs not covered by the budgets of the respective CSDP mission and operation shall be borne by the budget of the European External Action Service, subject to the applicable financial rules.

Review
Article 8
The mandate, tasks, functioning and financing of the EU Operations Centre, in the context of the overall EU crisis management structures, shall be reviewed on 24 September 2012 and thereafter at regular intervals. This Decision may be revised as appropriate.

Entry into force and duration
Article 9
This Decision shall enter into force on the date of its adoption.
It shall apply for an initial period of two years.

THE COUNCIL OF THE EUROPEAN UNION,
Having regard to the Treaty on European Union, and in particular Articles 42(4) and 43(2) thereof,
Having regard to the proposal from the High Representative of the Union for Foreign Affairs and Security Policy,
(1) On 17 December 2004, the European Council endorsed the proposals allowing for the establishment of an operations centre and its terms of reference.
(2) On 18 June 2007, the Council approved the Guidelines for Command and Control Structure for the EU Civilian Operations in Crisis Management.
(3) On 7 April 2008, by Decision 2008/298/CFSP(1)the Council amended Decision 2001/80/CFSP of 22 January 2001 on the establishment of the Military Staff of the European Union(2)to specify, inter alia, the tasks of the Military Staff of the European Union (EUMS) in relation to the EU Operations Centre.
(4) On 10 November 2008, the Council adopted Joint Action 2008/851/CFSP(3)establishing operation Atalanta with the purpose of deterring piracy off the Somali coast.
(5) On 15 February 2010, the Council adopted Decision 2010/96/CFSP(4)on an EU military mission to contribute to the training of Somali security forces (EUTM Somalia).
(6) On 14 November 2011, the Council adopted a Strategic Framework for the Horn of Africa to guide the EU’s engagement in the region.
(7) On 1 December 2011, the Council agreed to accelerate planning for the activation of the EU Operations Centre for the Horn of Africa Common Security and Defence Policy (CSDP) missions and operation, in accordance with its terms of reference.
(8) On 16 December 2011, the Council agreed the Crisis Management Concept for the Regional Maritime Capacity Building (RMCB) mission, as a civilian CSDP mission with military expertise.
(9) On 23 January 2012, the Council agreed that the EU Operations Centre should be activated for the Horn of Africa CSDP missions and operation.
(10) The EU Operations Centre should facilitate coordination and improve synergies amongst the Horn of Africa CSDP missions and operation, in the context of the Strategic Framework for the Horn of Africa and in close liaison with the European Union Special Representative (EUSR) for the Horn of Africa.
(11) The EU Operations Centre should be supported by the existing structures of the EUMS, reinforced by the EUTM Somalia Support Element and the Atalanta Liaison Team.
(12) Bearing in mind the requirement to optimise its support for all CSDP missions and operations, the EUMS should provide support to the EU Operations Centre within its means and capabilities,
HAS ADOPTED THIS DECISION:

Activation of the EU Operations Centre

1. The EU Operations Centre shall be activated in support of the Common Security and Defence Policy (CSDP) missions and operation in the Horn of Africa, namely Operation Atalanta, EUTM Somalia, and the planned civilian CSDP mission on Regional Maritime Capacity Building (RMCB).
2. The activation of the EU Operations Centre shall be without prejudice to the respective military and civilian chains of command of the missions and the operation, referred to in paragraph 1.

Mandate and tasks

1. The EU Operations Centre shall provide support in the field of operational planning and conduct of Operation Atalanta, EUTM Somalia, and the future civilian CSDP mission on Regional Maritime Capacity Building (RMCB), with a view to increasing efficiency, coherence and synergies. In this framework the EU Operations Centre shall help facilitate information exchange and improve coordination and strengthen civil-military synergies.
2. The EU Operations Centre shall perform the following tasks:
(a)
to provide, using its military expertise and specialised planning expertise, direct support to the Civilian Operations Commander for the operational planning and conduct of the RMCB mission;
(b)
to provide support to the EUTM Mission Commander and enhance strategic coordination between EUTM Somalia and the other CSDP mission and operation in the Horn of Africa;
(c)
to liaise with Operation Atalanta;
(d)
to provide support to the Crisis Management and Planning Directorate (CMPD), at its request, in its strategic planning for the CSDP missions and operation in the Horn of Africa;
(e)
to facilitate interaction between the Horn of Africa CSDP missions and operation and the Brussels-based structures;
(f)
to facilitate coordination and improve synergies amongst Operation Atalanta, EUTM Somalia, and RMCB, in the context of the Horn of Africa Strategy and in liaison with the European Union Special Representative for the Horn of Africa.

Head of the EU Operations Centre

1. Captain (Navy) Ad VAN DER LINDE is hereby appointed Head of the EU Operations Centre for a period of two years, which may be renewed if the Council so decides.
2. The Head of the EU Operations Centre shall carry out his functions under the political control and strategic direction of the Political and Security Committee (PSC), and, as appropriate, under the military direction of the European Union Military Committee (EUMC).
3. The Head of the EU Operations Centre shall exercise authority over the staff of the EU Operations Centre for all issues related to the mandate and tasks of the EU Operations Centre.
4. The Head of the EU Operations Centre shall be responsible for responding to the requests addressed to the EU Operations Centre by the Civilian Operation Commander, the Operation Commander for Operation Atalanta, the EUTM Mission Commander, and CMPD. He shall ensure the proper functioning of the EU Operations Centre and coordinate the efficient use of its capacities. The final responsibility for operational planning documents and decisions on the conduct of the missions and the operation shall remain respectively with the Civilian Operation Commander, the EUTM Mission Commander, and the Operation Commander for Operation Atalanta.
5. Within the limits of his responsibility, the Head of the EU Operations Centre shall regularly report to EUMC and to PSC.

Staff

1. The Human resources of the EU Operations Centre shall comprise:
(a)
staff provided by the EUMS;
(b)
the EUTM Support Element;
(c)
the Atalanta Liaison Team;
(d)
staff seconded by Member States.
2. The human resources put at the disposal of the EU Operations Centre shall cover all military expertise required to implement its mandate and tasks properly on the basis of an implementation plan presented to the PSC and shall be subject to regular review. The precise definition of the expertise required shall be the responsibility of the Head of the EU Operations Centre, in close consultation with the Operation and Mission Commanders, the Civilian Operation Commander, and the EUMS.
3. All staff shall respect the security principles and minimum standards established by Council Decision 2011/292/EU of 31 March 2011 on the security rules for protecting EU classified information(5).

Organisation

The EU Operations Centre shall be organised along functional responsibilities corresponding to the requirements of the CSDP missions and operation which it supports.

Support by the EUMS

The EUMS shall, within its means and capabilities, provide support to the EU Operations Centre in accordance with its terms of reference through:
(a)
ensuring availability and readiness of the staff, facilities and equipment of the EU Operations Centre;
(b)
maintaining, updating and replacing the equipment of the EU Operations Centre;
(c)
maintaining the premises used by the EU Operations Centre.

Financing

1. The staff provided by EUMS shall be financed in accordance with the rules applicable to the EUMS.
2. The staff provided by Member States shall be seconded national experts on free secondment.
3. Travel and other costs not covered by the budgets of the respective CSDP mission and operation shall be borne by the budget of the European External Action Service, subject to the applicable financial rules.

Review

The mandate, tasks, functioning and financing of the EU Operations Centre, in the context of the overall EU crisis management structures, shall be reviewed on 24 September 2012 and thereafter at regular intervals. This Decision may be revised as appropriate.

Entry into force and duration

This Decision shall enter into force on the date of its adoption.
It shall apply for an initial period of two years.

Pending: 32012D0137

3.3.2012 EN Official Journal of the European Union L 64/29
(1) Directive 90/429/EEC lays down the animal health conditions applicable to intra-Union trade in and imports from third countries of semen of domestic animals of the porcine species. It provides that Member States may authorise importation of such semen only from those third countries which appear on a list drawn up in accordance with the procedure laid down therein and accompanied by an animal health certificate, the model of which must correspond to a specimen drawn up in accordance with that Directive. The animal health certificate is to certify that the semen comes from approved semen collection centres offering the guarantees provided for in Article 8(1) of that Directive.
(2) Commission Decision 2009/893/EC of 30 November 2009 on importation of semen of domestic animals of the porcine species into the Community as regards lists of third countries and of semen collection centres, and certification requirements(2)sets out a list of third countries from which Member States are to authorise imports of semen. That list is established on the basis of the animal health status of those third countries.
(3) Directive 90/429/EEC, as amended by Commission Implementing Regulation (EU) No 176/2012(3), provides for revised animal health requirements for donor animals of the porcine species and semen as regards brucellosis and Aujeszky’s disease.
(4) Council Directive 2002/60/EC of 27 June 2002 laying down specific provisions for the control of African swine fever and amending Directive 92/119/EEC as regards Teschen disease and African swine fever(4)deleted Teschen disease (porcine enterovirus encephalomyelitis) from the list of diseases laid down in Annex I to Council Directive 92/119/EEC of 17 December 1992 introducing general Community measures for the control of certain animal diseases and specific measures relating to swine vesicular disease(5)and consequently by Commission Decision 2008/650/EC of 30 July 2008 amending Council Directive 82/894/EEC on the notification of animal diseases within the Community to include certain diseases in the list of notifiable diseases and to delete porcine enterovirus encephalomyelitis from that list(6)that disease was deleted from the list of the compulsorily notifiable diseases within the Union.
(5) In addition, it is necessary to align certain animal health requirements for imports into the Union of semen of domestic animals of the porcine species to the Terrestrial Animal Health Code of the World Organisation for Animal Health (OIE) in particular as regards country freedom of swine vesicular disease and semen collection centre freedom of tuberculosis and rabies.
(6) Accordingly, the model animal health certificate set out in Part 1 of Annex II to Decision 2009/893/EC should be amended to take account of those amendments made to Directive 90/429/EEC and to delete all references to Teschen disease (porcine enterovirus encephalomyelitis), country freedom of swine vesicular disease and semen collection centre freedom of tuberculosis and rabies.
(7) There are bilateral agreements concluded between the Union and certain third countries containing specific conditions for the imports into the Union of semen of domestic animals of the porcine species. Therefore, where the bilateral agreements contain specific conditions and model animal health certificates for imports, those conditions and models should apply instead of the conditions and the model set out in this Decision.
(8) Switzerland is a third country with an animal health status equivalent to that of the Member States. It is therefore appropriate that semen of domestic animals of the porcine species imported into the Union from Switzerland is accompanied by an animal health certificate drawn up in accordance with the models used for intra-Union trade in such semen set out in Annex D to Directive 90/429/EEC, with the adaptations set out in point 3 of Chapter VIII(B) of Appendix 2 of Annex 11 to the Agreement between the European Community and the Swiss Confederation on Trade in Agricultural Products, as approved by Decision 2002/309/EC, Euratom of the Council, and of the Commission as regards the Agreement on Scientific and Technological Cooperation, of 4 April 2002 on the conclusion of seven Agreements with the Swiss Confederation(7).
(9) In the interest of clarity and consistency of Union legislation, Decision 2009/893/EC should be repealed and replaced by this Decision.
(10) To avoid any disruption of trade, the use of animal health certificates issued in accordance with Decision 2009/893/EC should be authorised during a transitional period.
(11) The measures provided for in this Decision are in accordance with the opinion of the Standing Committee on the Food Chain and Animal Health,
(a) it comes from a third country, or part thereof, listed in Annex I;
(b) it comes from a semen collection centre listed in accordance with Article 8(2) of Directive 90/429/EEC;
(c) it is accompanied by an animal health certificate drawn up in accordance with the model animal health certificate set out in Part 1 of Annex II, and completed in accordance with the explanatory notes set out in Part 2 of that Annex;
(d) it complies with the requirements set out in the animal health certificate referred to in point (c).
(a) are not intended for introduction into the Union; or
(b) are of a lower health status.
ISO code Name of the third country Remarks
CA Canada
CH Switzerland(*1)
NZ New Zealand
US United States
(a) The animal health certificates shall be issued by the competent authority of the exporting third country, in accordance with the model set out in Part 1 of Annex II.If the Member State of destination requires additional certification requirements, attestations to certify that those requirements are fulfilled shall be also incorporated in the original form of the animal health certificate.
(b) The original of the animal health certificate shall consist of a single sheet of paper, or, where more text is required, it must be in such a form that all sheets of paper required are part of an integrated whole and indivisible.
(c) Where the model animal health certificate states that certain statements shall be kept as appropriate, statements which are not relevant, may be crossed out and initialled and stamped by the certifying officer, or completely deleted from certificate.
(d) The animal health certificate shall be drawn up in at least one of the official languages of the Member State of the border inspection post of introduction of the consignment into the European Union and of the Member State of destination. However, those Member States may authorise the certificate to be drawn up in the official language of another Member State, and accompanied, if necessary, by an official translation.
(e) If for the reasons of identification of the items of the consignment (schedule in Box I.28 of the model animal health certificates), additional sheets of paper are attached to the animal health certificate, those sheets of paper shall also be considered as forming part of the original of the animal health certificate by application of the signature and stamp of the certifying officer, on each of the pages.
(f) When the animal health certificate, including additional schedules referred to in (e), comprises more than one page, each page shall be numbered (page number) of (total number of pages), at the end of the page and shall bear the certificate reference number designated by the competent authority on the top of the pages.
(g) The original of the animal health certificate must be completed and signed by an official veterinarian the last working day prior to loading of the consignment for exportation to the European Union. The competent authorities of the exporting third country shall ensure that certification requirements equivalent to those laid down in Council Directive 96/93/EC(1)are followed.The colour of the signature and the stamp of the official veterinarian shall be different to that of the printing on the animal health certificate. This requirement also applies to stamps other than those embossed or watermarks.
(h) The original of the animal health certificate must accompany the consignment until it reaches the border inspection post of introduction into the European Union.
(i) The certificate reference number referred to in Box I.2 and Box II.a of the model animal health certificate must be issued by the competent authority of the exporting third country.
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Council Directive 90/429/EEC of 26 June 1990 laying down the animal health requirements applicable to intra-Community trade in and imports of semen of domestic animals of the porcine species(1), and in particular Article 7(1), Article 9(2) and (3) and Article 10(2) thereof,
(1) Directive 90/429/EEC lays down the animal health conditions applicable to intra-Union trade in and imports from third countries of semen of domestic animals of the porcine species. It provides that Member States may authorise importation of such semen only from those third countries which appear on a list drawn up in accordance with the procedure laid down therein and accompanied by an animal health certificate, the model of which must correspond to a specimen drawn up in accordance with that Directive. The animal health certificate is to certify that the semen comes from approved semen collection centres offering the guarantees provided for in Article 8(1) of that Directive.
(2) Commission Decision 2009/893/EC of 30 November 2009 on importation of semen of domestic animals of the porcine species into the Community as regards lists of third countries and of semen collection centres, and certification requirements(2)sets out a list of third countries from which Member States are to authorise imports of semen. That list is established on the basis of the animal health status of those third countries.
(3) Directive 90/429/EEC, as amended by Commission Implementing Regulation (EU) No 176/2012(3), provides for revised animal health requirements for donor animals of the porcine species and semen as regards brucellosis and Aujeszky’s disease.
(4) Council Directive 2002/60/EC of 27 June 2002 laying down specific provisions for the control of African swine fever and amending Directive 92/119/EEC as regards Teschen disease and African swine fever(4)deleted Teschen disease (porcine enterovirus encephalomyelitis) from the list of diseases laid down in Annex I to Council Directive 92/119/EEC of 17 December 1992 introducing general Community measures for the control of certain animal diseases and specific measures relating to swine vesicular disease(5)and consequently by Commission Decision 2008/650/EC of 30 July 2008 amending Council Directive 82/894/EEC on the notification of animal diseases within the Community to include certain diseases in the list of notifiable diseases and to delete porcine enterovirus encephalomyelitis from that list(6)that disease was deleted from the list of the compulsorily notifiable diseases within the Union.
(5) In addition, it is necessary to align certain animal health requirements for imports into the Union of semen of domestic animals of the porcine species to the Terrestrial Animal Health Code of the World Organisation for Animal Health (OIE) in particular as regards country freedom of swine vesicular disease and semen collection centre freedom of tuberculosis and rabies.
(6) Accordingly, the model animal health certificate set out in Part 1 of Annex II to Decision 2009/893/EC should be amended to take account of those amendments made to Directive 90/429/EEC and to delete all references to Teschen disease (porcine enterovirus encephalomyelitis), country freedom of swine vesicular disease and semen collection centre freedom of tuberculosis and rabies.
(7) There are bilateral agreements concluded between the Union and certain third countries containing specific conditions for the imports into the Union of semen of domestic animals of the porcine species. Therefore, where the bilateral agreements contain specific conditions and model animal health certificates for imports, those conditions and models should apply instead of the conditions and the model set out in this Decision.
(8) Switzerland is a third country with an animal health status equivalent to that of the Member States. It is therefore appropriate that semen of domestic animals of the porcine species imported into the Union from Switzerland is accompanied by an animal health certificate drawn up in accordance with the models used for intra-Union trade in such semen set out in Annex D to Directive 90/429/EEC, with the adaptations set out in point 3 of Chapter VIII(B) of Appendix 2 of Annex 11 to the Agreement between the European Community and the Swiss Confederation on Trade in Agricultural Products, as approved by Decision 2002/309/EC, Euratom of the Council, and of the Commission as regards the Agreement on Scientific and Technological Cooperation, of 4 April 2002 on the conclusion of seven Agreements with the Swiss Confederation(7).
(9) In the interest of clarity and consistency of Union legislation, Decision 2009/893/EC should be repealed and replaced by this Decision.
(10) To avoid any disruption of trade, the use of animal health certificates issued in accordance with Decision 2009/893/EC should be authorised during a transitional period.
(11) The measures provided for in this Decision are in accordance with the opinion of the Standing Committee on the Food Chain and Animal Health,
HAS ADOPTED THIS DECISION:

Subject matter
Article 1
This Decision lays down a list of third countries or parts thereof from which Member States shall authorise imports into the Union of semen of domestic animals of the porcine species.
It also lays down certification requirements for imports of semen into the Union.

Imports of semen
Article 2
1. Member States shall authorise the import of semen provided that it complies with the following conditions:
(a)
it comes from a third country, or part thereof, listed in Annex I;
(b)
it comes from a semen collection centre listed in accordance with Article 8(2) of Directive 90/429/EEC;
(c)
it is accompanied by an animal health certificate drawn up in accordance with the model animal health certificate set out in Part 1 of Annex II, and completed in accordance with the explanatory notes set out in Part 2 of that Annex;
(d)
it complies with the requirements set out in the animal health certificate referred to in point (c).
2. Where specific animal health and certification conditions are laid down in bilateral agreements between the Union and third countries, those conditions shall apply instead of the conditions laid down in paragraph 1.

Conditions concerning the transport of semen to the Union
Article 3
1. The semen referred to in Article 2 shall not be transported in the same container as other consignments of semen that:
(a)
are not intended for introduction into the Union; or
(b)
are of a lower health status.
2. During transport to the Union, semen shall be placed in closed and sealed flasks and the seal shall not be broken during transport.

Repeal
Article 4
Decision 2009/893/EC is repealed.

Transitional provision
Article 5
For a transitional period until 30 November 2012, Member States shall authorise imports of semen from third countries which are accompanied by an animal health certificate issued not later than 31 October 2012 in accordance with the model set out in Part 1 of Annex II to Decision 2009/893/EC.

Applicability
Article 6
This Decision shall apply from 1 June 2012.

Addressees
Article 7
This Decision is addressed to the Member States.

THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Council Directive 90/429/EEC of 26 June 1990 laying down the animal health requirements applicable to intra-Community trade in and imports of semen of domestic animals of the porcine species(1), and in particular Article 7(1), Article 9(2) and (3) and Article 10(2) thereof,
(1) Directive 90/429/EEC lays down the animal health conditions applicable to intra-Union trade in and imports from third countries of semen of domestic animals of the porcine species. It provides that Member States may authorise importation of such semen only from those third countries which appear on a list drawn up in accordance with the procedure laid down therein and accompanied by an animal health certificate, the model of which must correspond to a specimen drawn up in accordance with that Directive. The animal health certificate is to certify that the semen comes from approved semen collection centres offering the guarantees provided for in Article 8(1) of that Directive.
(2) Commission Decision 2009/893/EC of 30 November 2009 on importation of semen of domestic animals of the porcine species into the Community as regards lists of third countries and of semen collection centres, and certification requirements(2)sets out a list of third countries from which Member States are to authorise imports of semen. That list is established on the basis of the animal health status of those third countries.
(3) Directive 90/429/EEC, as amended by Commission Implementing Regulation (EU) No 176/2012(3), provides for revised animal health requirements for donor animals of the porcine species and semen as regards brucellosis and Aujeszky’s disease.
(4) Council Directive 2002/60/EC of 27 June 2002 laying down specific provisions for the control of African swine fever and amending Directive 92/119/EEC as regards Teschen disease and African swine fever(4)deleted Teschen disease (porcine enterovirus encephalomyelitis) from the list of diseases laid down in Annex I to Council Directive 92/119/EEC of 17 December 1992 introducing general Community measures for the control of certain animal diseases and specific measures relating to swine vesicular disease(5)and consequently by Commission Decision 2008/650/EC of 30 July 2008 amending Council Directive 82/894/EEC on the notification of animal diseases within the Community to include certain diseases in the list of notifiable diseases and to delete porcine enterovirus encephalomyelitis from that list(6)that disease was deleted from the list of the compulsorily notifiable diseases within the Union.
(5) In addition, it is necessary to align certain animal health requirements for imports into the Union of semen of domestic animals of the porcine species to the Terrestrial Animal Health Code of the World Organisation for Animal Health (OIE) in particular as regards country freedom of swine vesicular disease and semen collection centre freedom of tuberculosis and rabies.
(6) Accordingly, the model animal health certificate set out in Part 1 of Annex II to Decision 2009/893/EC should be amended to take account of those amendments made to Directive 90/429/EEC and to delete all references to Teschen disease (porcine enterovirus encephalomyelitis), country freedom of swine vesicular disease and semen collection centre freedom of tuberculosis and rabies.
(7) There are bilateral agreements concluded between the Union and certain third countries containing specific conditions for the imports into the Union of semen of domestic animals of the porcine species. Therefore, where the bilateral agreements contain specific conditions and model animal health certificates for imports, those conditions and models should apply instead of the conditions and the model set out in this Decision.
(8) Switzerland is a third country with an animal health status equivalent to that of the Member States. It is therefore appropriate that semen of domestic animals of the porcine species imported into the Union from Switzerland is accompanied by an animal health certificate drawn up in accordance with the models used for intra-Union trade in such semen set out in Annex D to Directive 90/429/EEC, with the adaptations set out in point 3 of Chapter VIII(B) of Appendix 2 of Annex 11 to the Agreement between the European Community and the Swiss Confederation on Trade in Agricultural Products, as approved by Decision 2002/309/EC, Euratom of the Council, and of the Commission as regards the Agreement on Scientific and Technological Cooperation, of 4 April 2002 on the conclusion of seven Agreements with the Swiss Confederation(7).
(9) In the interest of clarity and consistency of Union legislation, Decision 2009/893/EC should be repealed and replaced by this Decision.
(10) To avoid any disruption of trade, the use of animal health certificates issued in accordance with Decision 2009/893/EC should be authorised during a transitional period.
(11) The measures provided for in this Decision are in accordance with the opinion of the Standing Committee on the Food Chain and Animal Health,
HAS ADOPTED THIS DECISION:

Subject matter

This Decision lays down a list of third countries or parts thereof from which Member States shall authorise imports into the Union of semen of domestic animals of the porcine species.
It also lays down certification requirements for imports of semen into the Union.

Imports of semen

1. Member States shall authorise the import of semen provided that it complies with the following conditions:
(a)
it comes from a third country, or part thereof, listed in Annex I;
(b)
it comes from a semen collection centre listed in accordance with Article 8(2) of Directive 90/429/EEC;
(c)
it is accompanied by an animal health certificate drawn up in accordance with the model animal health certificate set out in Part 1 of Annex II, and completed in accordance with the explanatory notes set out in Part 2 of that Annex;
(d)
it complies with the requirements set out in the animal health certificate referred to in point (c).
2. Where specific animal health and certification conditions are laid down in bilateral agreements between the Union and third countries, those conditions shall apply instead of the conditions laid down in paragraph 1.

Conditions concerning the transport of semen to the Union

1. The semen referred to in Article 2 shall not be transported in the same container as other consignments of semen that:
(a)
are not intended for introduction into the Union; or
(b)
are of a lower health status.
2. During transport to the Union, semen shall be placed in closed and sealed flasks and the seal shall not be broken during transport.

Repeal

Decision 2009/893/EC is repealed.

Transitional provision

For a transitional period until 30 November 2012, Member States shall authorise imports of semen from third countries which are accompanied by an animal health certificate issued not later than 31 October 2012 in accordance with the model set out in Part 1 of Annex II to Decision 2009/893/EC.

Applicability

This Decision shall apply from 1 June 2012.

Addressees

This Decision is addressed to the Member States.
ANNEX I
List of third countries or part thereof from which Member States are to authorise imports of semen of domestic animals of the porcine species

ISO code | Name of the third country | Remarks
CA | Canada |
CH | Switzerland(*1) |
NZ | New Zealand |
US | United States |
(*1) The certificate to be used for imports from Switzerland is set out in Annex D to Directive 90/429/EEC, with the adaptations set out in point 3 of Chapter VIII(B) of Appendix 2 of Annex 11 to the Agreement between the European Community and the Swiss Confederation on trade in agricultural products as approved by Decision 2002/309/EC, Euratom.

PART 1

ANNEX II
Model animal health certificate for imports of semen of domestic animals of the porcine species

Part I: Details of dispatched consignment
COUNTRY:
Veterinary certificate to EU
I.1. Consignor
Name
Address
Tel.
I.2. Certificate reference No
I.2.a.
I.3. Central competent authority
I.4. Local competent authority
I.5. Consignee
Name
Address
Postal code
Tel.
I.6. Person responsible for the load in EU
Name
Address
Postal code
Tel.
I.7. Country of origin
ISO code
I.8. Region of origin
Code
I.9. Country of destination
ISO code
I.10 Region of destination
Code
I.11. Place of origin
Name
Address
Postal code
I.12. Place of origin
Name
Address
Postal code
I.13. Place of loading
I.14. Date of departure
I.15. Means of transport
Aeroplane
Ship
Railway wagon
Road vehicle
Other
Identification
Documentary references
I.16. Entry BIP in EU
I.17. I.18. Description of commodity
I.19. Commodity code (HS code)
05 11 99 85
I.20. Quantity
I.21. I.22. Number of packages
I.23. Seal/Container No
I.24. I.25. Commodities certified for:
Artificial reproduction
I.26. For transit through EU to third country
Third country
ISO code
I.27. For import or admission into EU
I.28. Identification of the commodities
Species
(Scientific name)
Breed
Donor identity
Date of collection
Approval number of the centre
Quantity

Part II: Certification
COUNTRY
Porcine semen
II. Health information
II.a. Certificate reference number
II.b.
I, the undersigned, official veterinarian, hereby certify that:
II.1. the exporting country …
(name of exporting country) (2) (1) either [II.1.1. has during the past 12 months been free of foot-and-mouth disease, classical swine fever and African swine fever,
and that no vaccinations have been carried out against any of these diseases during the past 12 months;]
(1) or [II.1.1. is recognised as free of foot-and-mouth disease without vaccination by the World Organisation for Animal Health (OIE) and free of classical swine fever and African swine fever, in accordance with the recommendations laid down in the OIE Terrestrial Animal Health Code;]
II.2. the semen collection centre in which the semen in this consignment was collected:
II.2.1. is approved for export to the Union by the veterinary services of … (name of third country (2)) and complies with the conditions for approval and supervision set out in Chapter I and Chapter II of Annex A to Directive 90/429/EEC;
II.2.2. was, during the period commencing three months prior to the date of collection of the semen in this consignment until the date of its dispatch, situated in an area not restricted due to an outbreak of foot-and-mouth disease, classical swine fever, African swine fever, swine vesicular disease, and vesicular stomatitis;
II.2.3. was, during the period commencing 30 days prior to the date of collection of the semen in this consignment until the date of its dispatch, free from brucellosis and Aujeszky’s disease;
(1) either [II.2.4. contains only animals that have not been vaccinated against Aujeszky’s disease and meet the requirements of Annex B to Directive 90/429/EEC.]
(1)(3) and/or [II.2.4. is a centre in which some or all of the animals have been vaccinated against Aujeszky’s disease using a gE deleted vaccine and meet the requirements of Annex B to Directive 90/429/EEC.]
Conditions for the admission of animals to the semen collection centre
II.3. Prior to be admitted to the semen collection centre, all animals:
II.3.1. were subjected to a period of quarantine of at least 30 days in accommodation specifically approved for the purpose by the competent authority, and where only animals having at least the same health status were present (quarantine accommodation);
II.3.2. prior to entering the quarantine accommodation, were chosen from herds or holdings:
II.3.2.1. which were free of brucellosis in accordance with the Chapter on porcine brucellosis of the Terrestrial Animal Health Code of the World Organisation for Animal Health (OIE);
II.3.2.2. in which no animal vaccinated against foot-and-mouth disease was present in the preceding 12 months;
II.3.2.3. which were not situated in a restricted area defined under the provisions of the national legislation due to an outbreak of foot-and-mouth disease, classical swine fever, African swine fever, swine vesicular disease, vesicular stomatitis and Aujeszky’s disease;
II.3.2.4. in which no clinical, serological, virological or pathological evidence of Aujeszky’s disease was detected in the preceding 12 months;
II.3.3. prior to entering the quarantine accommodation, were not previously kept in any herd of a lower health status than described in II.3.2;
II.3.4. within 30 days prior to entering the quarantine accommodation referred to in point II.3.1, were subjected to the following tests, performed in accordance with international standards, with negative results:
II.3.4.1. as regards brucellosis, a buffered Brucella antigen test (rose Bengal test), or a cELISA or an iELISA;

COUNTRY
Porcine semen
II. Health information
II.a. Certificate reference number
II.b.
II.3.4.2. as regards Aujeszky’s disease,
(1) either [II.3.4.2.1. in the case of non-vaccinated animals, a serum neutralisation test or an ELISA for detecting antibodies to the whole Aujeszky’s disease virus or to its glycoprotein B (ADV-gB) or glycoprotein D (ADV-gD);]
(1) or [II.3.4.2.1. in the case of animals vaccinated with a gE deleted vaccine, an ELISA for detecting antibodies to glycoprotein E (ADV-gE);]
(1) either [II.3.5. were admitted to the centre after all of the animals had reacted with negative result to a buffered Brucella antigen test (rose Bengal test), or a cELISA or an iELISA carried out on samples collected during the last 15 days of the period of quarantine specified in point II.3.1;]
(1) or [II.3.5. were admitted to the centre after not all of the animals had reacted with negative result to a buffered Brucella antigen test (rose Bengal test), or a cELISA or an iELISA carried out on samples collected during the last 15 days of the period of quarantine specified in point II.3.1 and the suspicion of brucellosis was ruled out in accordance with point 1.5 of Chapter I of Annex B to Directive 90/429/EEC;]
II.3.6. were subjected to the following tests for Aujeszky’s disease carried out on samples collected during the last 15 days of the period of quarantine specified in point II.3.1:
(1) either [II.3.6.1. in the case of non-vaccinated animals, a serum neutralisation test or an ELISA for detecting antibodies to the whole Aujeszky’s disease virus or to its glycoprotein B (ADV-gB) or glycoprotein D (ADV-gD);]
(1) or [II.3.6.1. in the case of animals vaccinated with a gE deleted vaccine, an ELISA for detecting antibodies to glycoprotein E (ADV-gE);]
(1) either [II.3.6.2. the tests referred to in point II.3.6.1 were carried out with negative result in each case;]
(1) or [II.3.6.2. the animals that proved positive in a test referred to in point II.3.6.1 were removed immediately from the quarantine accommodation and the competent authority took all necessary measures to ensure that the remaining animals had a satisfactory health status before being admitted to the collection centre in accordance with point II.3;]
II.3.7. All tests were carried out in a laboratory approved by the competent authority;
II.3.8. Animals were only admitted to the semen collection centre with the express permission of the centre veterinarian and all animal movements, entering and exiting the semen collection centre, are recorded;
II.3.9. No animal admitted to the semen collection centre showed any clinical sign of disease on the day of admission; all animals came directly from the quarantine accommodation which, on the day of consignment and during the period of residency of the animals, officially fulfilled the following conditions:
II.3.9.1. it was not situated in a restricted area defined under the provisions of national legislation due to an outbreak of foot-and-mouth disease, classical swine fever, African swine fever, swine vesicular disease, vesicular stomatitis and Aujeszky’s disease;
II.3.9.2. no clinical, serological, virological or pathological evidence of foot-and-mouth disease, classical swine fever, African swine fever, swine vesicular disease, vesicular stomatitis and Aujeszky’s disease had been recorded for the past 30 days.
Compulsory routine tests for animals kept at the semen collection centre
II.4. All animals kept at the semen collection centre are subjected to the following routine tests carried out in a laboratory approved by the competent authority:
II.4.1. as regards brucellosis, a buffered Brucella antigen test (rose Bengal test), or a cELISA or an iELISA;
II.4.2. as regards Aujeszky’s disease,
(1) either [II.4.2.1. in the case of non-vaccinated animals, a serum neutralisation test or an ELISA for detecting antibodies to the whole Aujeszky’s disease virus or to its glycoprotein B (ADV-gB) or glycoprotein D (ADV-gD);]

COUNTRY
Porcine semen
II. Health information
II.a. Certificate reference number
II.b.
(1) or [II.4.2.1. in the case of animals vaccinated with a gE deleted vaccine, an ELISA for detecting antibodies to glycoprotein E (ADV-gE);]
II.4.3. The routine tests referred to in points II.4.1 and II.4.2. are carried out on samples taken in accordance with point 1.2 of Chapter II of Annex B to Directive 90/429/EEC in order to ensure that all animals in the centre have been tested at least once during their stay at that centre and at least every 12 months from the date of admission, if their stay exceeds 12 months;
(1) either [II.4.4. All of the animals have reacted with negative results in the routine tests referred to in points II.4.1 and II.4.2 carried out on samples referred to in point II.4.3.]
(1) or [II.4.4. Not all of the animals have reacted with negative results in the tests referred to in points II.4.1 and II.4.2 carried out on samples referred to in point II.4.3:
(a) the animals which proved positive were isolated,
(b) the semen collected from each animal at the centre since the date of that animal’s last negative test was held in separate storage from semen eligible for export to the European Union which was collected before the animal’s last negative test or after the health status of the centre had been re-established under responsibility of the competent authority of the exporting country.]
Conditions for semen collected at a semen collection centre and intended for export to the Union
II.5. The semen in this consignment was obtained from animals which:
II.5.1. have been resident in … (name of third country (2)) for a minimum period of three months immediately prior to collection;
II.5.2. showed no clinical signs of disease on the day the semen was collected;
II.5.3. had not been vaccinated against foot-and-mouth disease;
II.5.4. satisfy the requirements referred to in point II.3;
II.5.5. have not been allowed to serve naturally;
II.5.6. were kept in semen collection centres which were not situated in a restricted area designated under the provisions of the national legislation relating to foot-and-mouth disease, classical swine fever, African swine fever, swine vesicular disease, vesicular stomatitis and Aujeszky’s disease;
II.5.7. were kept in semen collection centres in which no clinical, serological, virological or pathological evidence of foot-and-mouth disease, classical swine fever, African swine fever, swine vesicular disease, vesicular stomatitis and Aujeszky’s disease has been detected in the 30-day period immediately prior to collection.
II.6. An effective combination of antibiotics, in particular against leptospires, was added to the semen in this consignment after final dilution or to the diluent. In the case of frozen semen, antibiotics were added before the semen was frozen.
II.6.1. The combination of antibiotics referred to in point II.6. produced an effect at least equivalent to the following concentration in the final diluted semen:
(a) not less than 500 μg streptomycin per ml final dilution,
(b) not less than 500 IU penicillin per ml final dilution,
(c) not less than 150 μg lincomycin per ml final dilution,
(d) not less than 300 μg spectinomycin per ml final dilution;
II.6.2. Immediately after the addition of the antibiotics the diluted semen was kept at a temperature of at least 15 °C for a period of not less than 45 minutes.

COUNTRY
Porcine semen
II. Health information
II.a. Certificate reference number
II.b.
II.7. The semen in this consignment:
II.7.1. has been stored as laid down in point 2(d) of Chapter I and point 6(a), (b), (e) and (f) of Chapter II of Annex A to Directive 90/429/EEC prior to dispatch;
II.7.2. is being transported to the country of destination in flasks which were cleaned and disinfected or sterilised before use and which have been sealed prior to dispatch from the approved storage facilities.
Notes
Part I:
Box I.6: Person responsible for the load in EU: this box is to be filled in only if it is a certificate for transit commodity.
Box I.8: Provide the code of the third country as appearing in Annex I to Commission Implementing Decision 2012/XXXX/EU.
Box I.11: Place of origin shall correspond to the semen collection centre of the semen dispatch listed in accordance with Article 8(2) of Directive 90/429/EEC:
http://ec.europa.eu/food/animal/semen_ova/porcine/index_en.htm
Box I.12: Place of destination: this box is to be filled in only if it is a certificate for transit commodity.
Box I.22: Number of packages shall correspond to the number of containers.
Box I.23: Identification of container and seal number shall be indicated.
Box I.26: fill in according to whether it is a transit or an import certificate.
Box I.27: fill in according to whether it is a transit or an import certificate.
Box I.28: Donor identity shall correspond to the official identification of the animal.
Date of collection shall be indicated in the following format: dd/mm/yyyy.
Approval number of the centre shall correspond to the approval number of the semen collection centre where the semen was collected.
Part II:
(1) Delete as necessary.
(2) Countries listed in Annex I to Commission Implementing Decision 2012/XXXX/EU.
(3) This option shall be deleted in case the Member State, or a region thereof, of destination is free of Aujeszky’s disease in accordance with Article 10 of Directive 64/432/EEC, has informed the Commission in accordance with point 4 of Annex C to Directive 90/429/EEC and is listed on the following website: http://ec.europa.eu/food/animal/semen_ova/porcine/index_en.htm
The signature and the stamp must be in a different colour to that of the printing.
Official veterinarian
Name (in capital letters):
Qualification and title:
Date:
Signature:
Stamp:

PART 2

Explanatory notes for the certification

(a) | The animal health certificates shall be issued by the competent authority of the exporting third country, in accordance with the model set out in Part 1 of Annex II.If the Member State of destination requires additional certification requirements, attestations to certify that those requirements are fulfilled shall be also incorporated in the original form of the animal health certificate.
(b) | The original of the animal health certificate shall consist of a single sheet of paper, or, where more text is required, it must be in such a form that all sheets of paper required are part of an integrated whole and indivisible.
(c) | Where the model animal health certificate states that certain statements shall be kept as appropriate, statements which are not relevant, may be crossed out and initialled and stamped by the certifying officer, or completely deleted from certificate.
(d) | The animal health certificate shall be drawn up in at least one of the official languages of the Member State of the border inspection post of introduction of the consignment into the European Union and of the Member State of destination. However, those Member States may authorise the certificate to be drawn up in the official language of another Member State, and accompanied, if necessary, by an official translation.
(e) | If for the reasons of identification of the items of the consignment (schedule in Box I.28 of the model animal health certificates), additional sheets of paper are attached to the animal health certificate, those sheets of paper shall also be considered as forming part of the original of the animal health certificate by application of the signature and stamp of the certifying officer, on each of the pages.
(f) | When the animal health certificate, including additional schedules referred to in (e), comprises more than one page, each page shall be numbered (page number) of (total number of pages), at the end of the page and shall bear the certificate reference number designated by the competent authority on the top of the pages.
(g) | The original of the animal health certificate must be completed and signed by an official veterinarian the last working day prior to loading of the consignment for exportation to the European Union. The competent authorities of the exporting third country shall ensure that certification requirements equivalent to those laid down in Council Directive 96/93/EC(1)are followed.The colour of the signature and the stamp of the official veterinarian shall be different to that of the printing on the animal health certificate. This requirement also applies to stamps other than those embossed or watermarks.
(h) | The original of the animal health certificate must accompany the consignment until it reaches the border inspection post of introduction into the European Union.
(i) | The certificate reference number referred to in Box I.2 and Box II.a of the model animal health certificate must be issued by the competent authority of the exporting third country.
(1)
OJ L 13, 16.1.1997, p. 28.

Pending: 32012D0088

23.2.2012 EN Official Journal of the European Union L 51/1
(1) Commission Decision 2006/679/EC of 28 March 2006 concerning the technical specification for interoperability relating to the control-command and signalling subsystem of the trans-European conventional rail system(2)laid down the technical specifications for interoperability (‘TSI’) relating to the control-command and signalling subsystem of the trans-European conventional rail system.
(2) Commission Decision 2006/860/EC of 7 November 2006 concerning a technical specification for interoperability relating to the control-command and signalling subsystem of the trans-European high speed rail system(3)lays down the TSI relating to the control-command and signalling subsystem of the trans-European high-speed rail system.
(3) The essential requirements for both the conventional and the high-speed networks must be identical, as must their functional and technical specifications, their interoperability constituents and interfaces, and the procedures for assessing the conformity or the suitability for use of the interoperability constituents or the ‘EC’ verification of their control-command and signalling subsystems.
(4) The implementation strategies should remain specific to each type of network and the existing requirements for the conventional trans-European network and for the high-speed trans-European network should remain unchanged. The European railway agency (‘Agency’) was given a framework mandate to perform certain activities.
(5) On 31 January 2011 the Agency gave its recommendation on the technical specification for interoperability relating to the subsystems ‘control-command and signalling’ of the trans-European rail system(4). This Decision is based on that recommendation.
(6) In the interest of clarity, Decisions 2006/679/EC and 2006/860/EC should therefore be replaced by this Decision.
(7) The changes introduced regarding safety requirements (Section 4.2.1 of Annex III) are based on the analysis that the text in the CCS TSIs in force leaves room for interpretations. The introduced changes have no negative impact in the overall safety level.
(8) The fitting of ERTMS/ETCS should be mandatory in the case of new installations or upgrade of the train protection part of a CCS assembly for railway infrastructure projects benefiting from EU financial support. Such fitting should in principle be carried out in the frame of the EU funded project. In certain cases, it is however necessary to grant a derogation to this implementation rule. The scope of such derogation is limited to the implementation strategy of the ‘control-command and signalling TSI’.
(9) The Agency has listed in the technical document ‘List of CCS Class B systems’ the national legacy control-command and signalling systems (‘Class B systems’). Those systems may still be requested on board locomotives and traction units to run on certain lines.
(10) The Class B systems significantly hamper the interoperability of locomotives and traction units but play an important role in maintaining the high level of safety of the trans-European network. For this reason, it is important to avoid creating additional obstacles to interoperability by, for example, altering these national legacy systems or by introducing new systems.
(11) To avoid creating additional obstacles to interoperability, Member States should ensure that the functionality of the legacy Class B systems and their interfaces remain as currently specified, except where modifications are needed to mitigate safety-related flaws in these systems. Member States should also ensure that systems not included in the list of Class B systems do not constitute additional barriers to interoperability.
(12) The availability of the GSM-R frequencies is essential for safe and interoperable railway operations.
(13) Decisions 2006/679/EC and 2006/860/EC should therefore be repealed.
(14) The measures provided for in this Decision are in accordance with the opinion of the Committee, referred to in Article 29(1) of Directive 2008/57/EC,
(a) the list of applicable technical rules;
(b) the conformity assessment and checking procedures to be used for ensuring that the applicable technical rules are indeed applied;
(c) the bodies it appoints for carrying out those conformity-assessment and checking procedures.
— 5 years after the end of the project,
— the time by which the section of the line is connected to another ETCS equipped line.
(1) the second indent under the headline ‘Legislative measures in force’ in Section 1.4 ‘Referenced documents’ of the Annex is replaced by ‘Control-Command and Signalling TSI’;
(2) Section 4.2.3.3.1 is replaced by Annex I to this Decision;
(3) Table 10 in Section 4.3.4 is replaced by Annex II to this Decision.
— Vehicle geometry—The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance ai in Figure 1).—The maximum distance between buffer end and first axle is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance b1in Figure 1). — The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance ai in Figure 1). — The maximum distance between buffer end and first axle is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance b1in Figure 1).
— The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance ai in Figure 1).
— The maximum distance between buffer end and first axle is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance b1in Figure 1).
— The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance ai in Figure 1).
— The maximum distance between buffer end and first axle is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance b1in Figure 1).
— Vehicle design—The minimum axle load in all load conditions is specified in the specification referenced in clause 3.1.7 of Annex A, Index 77 of CCS TSI.—The electrical resistance between the running surfaces of the opposite wheels of a wheelset is specified in the specification referenced in clause 3.1.9 of Annex A, Index 77 of CCS TSI and the method to measure is specified in the same clause.—For electric units equipped with a pantograph, the minimum impedance between pantograph and each wheel of the train is an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI. — The minimum axle load in all load conditions is specified in the specification referenced in clause 3.1.7 of Annex A, Index 77 of CCS TSI. — The electrical resistance between the running surfaces of the opposite wheels of a wheelset is specified in the specification referenced in clause 3.1.9 of Annex A, Index 77 of CCS TSI and the method to measure is specified in the same clause. — For electric units equipped with a pantograph, the minimum impedance between pantograph and each wheel of the train is an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI.
— The minimum axle load in all load conditions is specified in the specification referenced in clause 3.1.7 of Annex A, Index 77 of CCS TSI.
— The electrical resistance between the running surfaces of the opposite wheels of a wheelset is specified in the specification referenced in clause 3.1.9 of Annex A, Index 77 of CCS TSI and the method to measure is specified in the same clause.
— For electric units equipped with a pantograph, the minimum impedance between pantograph and each wheel of the train is an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI.
— The minimum axle load in all load conditions is specified in the specification referenced in clause 3.1.7 of Annex A, Index 77 of CCS TSI.
— The electrical resistance between the running surfaces of the opposite wheels of a wheelset is specified in the specification referenced in clause 3.1.9 of Annex A, Index 77 of CCS TSI and the method to measure is specified in the same clause.
— For electric units equipped with a pantograph, the minimum impedance between pantograph and each wheel of the train is an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI.
— Isolating emissions—The limitations of use of sanding equipment are given in the specification referenced in clause 3.1.4 of Annex A, Index 77 of CCS TSI.—The limitations of use of composite brake blocks are given in the specification referenced in clause 3.1.6 of Annex A, Index 77 of CCS TSI. — The limitations of use of sanding equipment are given in the specification referenced in clause 3.1.4 of Annex A, Index 77 of CCS TSI. — The limitations of use of composite brake blocks are given in the specification referenced in clause 3.1.6 of Annex A, Index 77 of CCS TSI.
— The limitations of use of sanding equipment are given in the specification referenced in clause 3.1.4 of Annex A, Index 77 of CCS TSI.
— The limitations of use of composite brake blocks are given in the specification referenced in clause 3.1.6 of Annex A, Index 77 of CCS TSI.
— The limitations of use of sanding equipment are given in the specification referenced in clause 3.1.4 of Annex A, Index 77 of CCS TSI.
— The limitations of use of composite brake blocks are given in the specification referenced in clause 3.1.6 of Annex A, Index 77 of CCS TSI.
— EMC—The requirements related to electromagnetic compatibility are open points in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI.—The electromagnetic interference limit levels rising from traction currents are an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI. — The requirements related to electromagnetic compatibility are open points in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI. — The electromagnetic interference limit levels rising from traction currents are an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI.
— The requirements related to electromagnetic compatibility are open points in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI.
— The electromagnetic interference limit levels rising from traction currents are an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI.
— The requirements related to electromagnetic compatibility are open points in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI.
— The electromagnetic interference limit levels rising from traction currents are an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI.
— Vehicle geometry—The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.—The minimum distance between two consecutive axles of the train is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.—At the end of a unit intended to be coupled, the minimum distance between end and first axle of the unit is half of the value specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.—The maximum distance between end and first axle is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI (distance b1in Figure 1).—The minimum distance between end axles of a unit is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI. — The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI. — The minimum distance between two consecutive axles of the train is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI. — At the end of a unit intended to be coupled, the minimum distance between end and first axle of the unit is half of the value specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI. — The maximum distance between end and first axle is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI (distance b1in Figure 1). — The minimum distance between end axles of a unit is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
— The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
— The minimum distance between two consecutive axles of the train is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
— At the end of a unit intended to be coupled, the minimum distance between end and first axle of the unit is half of the value specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
— The maximum distance between end and first axle is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI (distance b1in Figure 1).
— The minimum distance between end axles of a unit is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
— The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
— The minimum distance between two consecutive axles of the train is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
— At the end of a unit intended to be coupled, the minimum distance between end and first axle of the unit is half of the value specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
— The maximum distance between end and first axle is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI (distance b1in Figure 1).
— The minimum distance between end axles of a unit is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
— Wheel geometry—Wheel geometry is specified in the clause 4.2.3.5.2.2 of the present TSI.—The minimum wheel diameter (speed dependant) is specified in the specification referenced in clause 3.1.3, Annex A, Index 77 of CCS TSI. — Wheel geometry is specified in the clause 4.2.3.5.2.2 of the present TSI. — The minimum wheel diameter (speed dependant) is specified in the specification referenced in clause 3.1.3, Annex A, Index 77 of CCS TSI.
— Wheel geometry is specified in the clause 4.2.3.5.2.2 of the present TSI.
— The minimum wheel diameter (speed dependant) is specified in the specification referenced in clause 3.1.3, Annex A, Index 77 of CCS TSI.
— Wheel geometry is specified in the clause 4.2.3.5.2.2 of the present TSI.
— The minimum wheel diameter (speed dependant) is specified in the specification referenced in clause 3.1.3, Annex A, Index 77 of CCS TSI.
— Vehicle design—The metal-free space around wheels is an open point in the specification referenced in clause 3.1.3.5, Annex A, Index 77 of CCS TSI.—The characteristics of the wheel material regarding magnetic field is specified in the specification referenced in clause 3.1.3.6, Annex A, Index 77 of CCS TSI. — The metal-free space around wheels is an open point in the specification referenced in clause 3.1.3.5, Annex A, Index 77 of CCS TSI. — The characteristics of the wheel material regarding magnetic field is specified in the specification referenced in clause 3.1.3.6, Annex A, Index 77 of CCS TSI.
— The metal-free space around wheels is an open point in the specification referenced in clause 3.1.3.5, Annex A, Index 77 of CCS TSI.
— The characteristics of the wheel material regarding magnetic field is specified in the specification referenced in clause 3.1.3.6, Annex A, Index 77 of CCS TSI.
— The metal-free space around wheels is an open point in the specification referenced in clause 3.1.3.5, Annex A, Index 77 of CCS TSI.
— The characteristics of the wheel material regarding magnetic field is specified in the specification referenced in clause 3.1.3.6, Annex A, Index 77 of CCS TSI.
— EMC—The requirements related to electromagnetic compatibility are specified in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI.—The electromagnetic interference limit levels rising from the use of eddy current or magnetic track brakes are an open point in the specification referenced in clause 3.2.3 of Annex A, Index 77 of CCS TSI. — The requirements related to electromagnetic compatibility are specified in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI. — The electromagnetic interference limit levels rising from the use of eddy current or magnetic track brakes are an open point in the specification referenced in clause 3.2.3 of Annex A, Index 77 of CCS TSI.
— The requirements related to electromagnetic compatibility are specified in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI.
— The electromagnetic interference limit levels rising from the use of eddy current or magnetic track brakes are an open point in the specification referenced in clause 3.2.3 of Annex A, Index 77 of CCS TSI.
— The requirements related to electromagnetic compatibility are specified in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI.
— The electromagnetic interference limit levels rising from the use of eddy current or magnetic track brakes are an open point in the specification referenced in clause 3.2.3 of Annex A, Index 77 of CCS TSI.
— Vehicle designThe metal-mass of vehicles is an open point in the specification referenced in clause 3.1.7.2 of Annex A, Index 77 of CCS TSI.’
Reference Conventional Rail LOC & PAS TSI Reference Rail CCS TSI
Parameter Clause Parameter Clause
Rolling stock characteristics compatible with train detection system based on track circuits 4.2.3.3.1.1 Vehicle geometryVehicle designIsolating emissionsEMC Specification referenced in Annex A, Index 77 of CCS TSI
Rolling stock characteristics compatible with train detection system based on axle counters 4.2.3.3.1.2 Vehicle geometryWheel geometryVehicle designEMC Specification referenced in Annex A, Index 77 of CCS TSI
Rolling stock characteristics compatible with loop equipment 4.2.3.3.1.3 Vehicle design Specification referenced in Annex A, Index 77 of CCS TSI
Emergency braking command 4.2.4.4.1 On-board ETCS functionality 4.2.2
Emergency braking performance 4.2.4.5.2 Guaranteed train braking performance and characteristics 4.2.2
External visibility 4.2.9.1.3 Visibility of track-side control-command objects 4.2.15’
1. Introduction 11
1.1. Technical scope 11
1.2. Geographical scope 11
1.3. Content of this TSI 11
2. Subsystem definition and scope 11
2.1. Introduction 11
2.2. Scope 11
2.3. Application Levels (ERTMS/ETCS) 12
3. The Essential Requirements for the Control-Command and Signalling Subsystems 12
3.1. General 12
3.2. Specific Aspects of the Control-Command and Signalling Subsystems 13
3.2.1. Safety 13
3.2.2. Reliability and Availability 13
3.2.3. Health 13
3.2.4. Environmental Protection 13
3.2.5. Technical Compatibility 13
3.2.5.1. Engineering Compatibility 14
3.2.5.1.1. Physical environmental conditions 14
3.2.5.1.2. Railway Internal Electromagnetic Compatibility 14
3.2.5.2. Control-Command and Signalling Compatibility 14
4. Characterisation of the Subsystems 14
4.1. Introduction 14
4.2. Functional and technical specifications of the Subsystems 15
4.2.1. Control-Command and Signalling safety characteristics relevant to interoperability 15
4.2.1.1. Safety 16
4.2.1.2. Availability/Reliability 16
4.2.2. On-board ERTMS/ETCS functionality 16
4.2.3. Track-side ERTMS/ETCS functionality 17
4.2.4. Mobile communication functions for railways GSM-R 18
4.2.4.1. Basic communication function 18
4.2.4.2. Voice and operational communication applications 18
4.2.4.3. Data communication applications for ETCS 18
4.2.5. ERTMS/ETCS and GSM-R air gap interfaces 19
4.2.5.1. Radio communications with the train 19
4.2.5.2. Eurobalise communication with the train 19
4.2.5.3. Euroloop communication with the train 19
4.2.6. On-Board Interfaces Internal to Control-Command and Signalling 19
4.2.6.1. ERTMS/ETCS and Class B train protection 19
4.2.6.2. Interface between GSM-R Radio Data Communication and ERTMS/ETCS 19
4.2.6.3. Odometry 20
4.2.7. Track-side Interfaces Internal to Control-Command and Signalling 20
4.2.7.1. Functional interface between RBCs 20
4.2.7.2. RBC/RBC 20
4.2.7.3. GSM-R/track-side ETCS 20
4.2.7.4. Eurobalise/LEU 20
4.2.7.5. Euroloop/LEU 20
4.2.8. Key Management 20
4.2.9. ETCS-ID Management 20
4.2.10. Track-side Train Detection Systems 20
4.2.11. Electromagnetic Compatibility between Rolling Stock and Control-Command and Signalling track-side equipment 21
4.2.12. ERTMS/ETCS DMI (Driver Machine Interface) 21
4.2.13. GSM-R DMI (Driver-Machine Interface) 21
4.2.14. Interface to Data Recording for Regulatory Purposes 21
4.2.15. Visibility of track-side Control-Command and Signalling objects 21
4.2.16. Environmental conditions 21
4.3. Functional and technical specifications of the interfaces to other Subsystems 22
4.3.1. Interface to the Traffic Operation and Management Subsystem 22
4.3.2. Interface to the Rolling Stock Subsystem 22
4.3.3. Interfaces to Infrastructure Subsystem 24
4.3.4. Interfaces to Energy Subsystem 25
4.4. Operating rules 25
4.5. Maintenance rules 25
4.5.1. Responsibility of the manufacturer of equipment 25
4.5.2. Responsibility of the applicant for subsystem verification 26
4.6. Professional competences 26
4.7. Health and safety conditions 26
4.8. Registers 26
5. Interoperability Constituents 26
5.1. Definition 26
5.2. List of interoperability constituents 26
5.2.1. Basic interoperability constituents 26
5.2.2. Grouping of interoperability constituents 26
5.3. Constituents’ performance and specifications 27
6. Assessing the conformity and/or suitability for use of the constituents and verifying the subsystems 31
6.1. Introduction 31
6.1.1. General principles 31
6.1.2. Principles for testing ERTMS/ETCS and GSM-R 31
6.2. Interoperability constituents 32
6.2.1. Assessment procedures for Control-Command and Signalling Interoperability Constituents 32
6.2.2. Modules for Control-Command and Signalling Interoperability Constituents 32
6.2.3. Assessment requirements 33
6.2.4. Special issues 34
6.2.4.1. The on-board ERTMS/ETCS 34
6.2.4.2. The Specific Transmission Module (STM) 35
6.2.4.3. Content of the ‘EC’ Declaration of conformity 35
6.3. Control-Command and Signalling Subsystems 35
6.3.1. Assessment procedures for Control-Command and Signalling Subsystems 35
6.3.2. Modules for Control-Command and Signalling Subsystems 35
6.3.2.1. On-board Subsystem 35
6.3.2.2. Track-side Subsystem 35
6.3.2.3. Conditions for using modules for On-board and Track-side Subsystems 36
6.3.3. Assessment requirements for an On-board Subsystem 36
6.3.4. Assessment requirements for a Track-side Subsystem 38
6.4. Provisions for partial conformity 41
6.4.1. Introduction 41
6.4.2. Assessment of parts of Control-Command and Signalling Subsystems 41
6.4.3. Partial conformity of Control-Command and Signalling Subsystems due to restricted conditions of use of its interoperability constituent(s) 41
7. Implementing the TSI Control-Command and Signalling 42
7.1. Introduction 42
7.2. Generally applicable rules 42
7.2.1. Upgrading or renewing the Control-Command Track-side Subsystem or parts of it 42
7.2.2. Legacy systems 42
7.2.3. Availability of Specific Transmission Modules 42
7.2.4. Additional Class B equipment on a line equipped with Class A 42
7.2.5. Rolling stock with Class A and Class B equipment 43
7.2.6. Conditions for mandatory and optional functions 43
7.2.7. GSM-R specific implementation rules 43
7.2.7.1. Track-side installations: 43
7.2.7.2. On-board installations: 43
7.2.8. Train detection systems specific implementation rules 44
7.2.9. Specific cases 44
7.2.9.1. Introduction 44
7.2.9.2. Belgium 44
7.2.9.3. United Kingdom 45
7.2.9.4. France 45
7.2.9.5. Poland 46
7.2.9.6. Lithuania, Latvia 46
7.2.9.7. Sweden 47
7.2.9.8. Luxembourg 47
7.3. Rules for ERTMS 47
7.3.1. The ERTMS European Deployment Plan 47
7.3.2. ERTMS Track-side Implementation 47
7.3.2.1. Corridors 47
7.3.2.2. Connection to the main European ports, marshalling yards, freight terminals and freight transport areas 48
7.3.2.3. High-speed network 48
7.3.2.4. EU-funded projects 48
7.3.2.5. Notification 48
7.3.2.6. Delays 48
7.3.3. ERTMS – On-board implementation 49
7.3.3.1. High-speed network 49
7.3.4. Specific lines constituting the corridors 50
7.3.5. Main European ports, marshalling yards, freight terminals and freight transport areas 56
1. indicates its intended scope — Chapter 2 (Subsystem Definition and Scope);
2. lays down essential requirements for the Control-Command and Signalling Subsystems and their interfaces vis-à-vis other subsystems — Chapter 3 (The Essential Requirements of the Control-Command and Signalling Subsystems);
3. lays down the functional and technical specifications to be met by the Subsystems and their interfaces with other subsystems — Chapter 4 (Characterisation of the Subsystem);
4. determines the interoperability constituents and interfaces which must be covered by European specifications, including European standards, and which are necessary to achieve interoperability within the trans-European rail system — Chapter 5 (Interoperability Constituents);
5. states, in each case under consideration, which procedures are to be used to assess the conformity or the suitability for use of the interoperability constituents and for the ‘EC’ verification of the subsystems — Chapter 6 (Assessing the Conformity and/or Suitability For Use of the Constituents and Verifying the Subsystems);
6. indicates the strategy for implementing this TSI — Chapter 7 (Implementing the Control-Command and Signalling Subsystems TSI);
7. indicates the professional competences and health and safety conditions at work required for the staff operating and maintaining these subsystems and implementing the TSI — Chapter 4 (Characterisation of the Subsystem).
1. the functions that are essential for the safe control of railway traffic, and that are essential for its operation, including those required for degraded modes(1);
2. the interfaces;
3. the level of performance required to meet the essential requirements.
1. train protection;
2. radio communication;
3. train detection.
1. the Class A radio network;
2. Class A train protection;
3. the interface requirements for train detection systems, to ensure their compatibility with rolling stock.
— a train equipped with Class A on-board train protection for level 2 must be able to operate on that level and on level 1 lines,
— a train equipped with Class A on-board train protection for level 1 need not be equipped with a GSM-R data radio but must already implement all level 2 functions so as to ensure that the mere connection of a GSM-R data radio at a later stage will ensure it is equipped for level 2.
1. Safety;
2. Reliability and Availability;
3. Health;
4. Environmental Protection;
5. Technical compatibility.
1. the Control-Command and Signalling equipment, if subjected to excessive heat or fire, shall not exceed limits for the emission of fumes or gases which are harmful to the environment;
2. the Control-Command and Signalling equipment shall not contain substances which may abnormally contaminate the environment during their normal use;
3. the Control-Command and Signalling equipment shall be subject to the European legislation in force controlling the limits to the emission of and the susceptibility to electromagnetic interference along the boundaries of railway property;
4. the Control-Command and Signalling equipment shall comply with existing regulations on noise pollution;
5. the Control-Command and Signalling equipment shall not give rise to any inadmissible level of vibration which could jeopardise the integrity of the infrastructure (when the infrastructure is in the correct state of maintenance).
1. The first category sets out the general engineering requirements for interoperability namely environmental conditions, internal electromagnetic compatibility (EMC) within the railway boundaries, and installation. These compatibility requirements are defined in this chapter.
2. The second category describes how the Control-Command and Signalling Subsystems have to be applied technically and what functions they have to perform to ensure interoperability. This category is defined in Chapter 4.
3. The third category describes how the Control-Command and Signalling Subsystems have to be operated in order that interoperability is achieved. This category is defined in Chapter 4.
1. Control-Command and Signalling safety characteristics relevant to interoperability (Section 4.2.1)
2. On-board ERTMS/ETCS functionality (Section 4.2.2)
3. Track-side ERTMS/ETCS functionality (Section 4.2.3)
4. Mobile communication functions for railways – GSM-R (Section 4.2.4)
5. ERTMS/ETCS and GSM-R air gap interfaces (Section 4.2.5)
6. On-board interfaces Internal to Control-Command and Signalling (Section 4.2.6)
7. Track-side interfaces Internal to Control-Command and Signalling (Section 4.2.7)
8. Key management (Section 4.2.8)
9. ETCS-ID management (Section 4.2.9)
10. Train detection systems (Section 4.2.10)
11. Electromagnetic compatibility between rolling stock and Control-Command and Signalling track-side equipment (Section 4.2.11)
12. ERTMS/ETCS DMI (driver machine interface) (Section 4.2.12)
13. GSM-R DMI (driver machine interface) (Section 4.2.13)
14. Interface to data recording for regulatory purposes (Section 4.2.14)
15. Visibility of track-side Control-Command and Signalling objects (Section 4.2.15)
16. Environmental conditions (Sections 4.2.16)
1. functions, interfaces and performances of the Control-Command and Signalling On-board Subsystem are standardised, ensuring that every train will react in a predictable way to data received from track-side;
2. for the Control-Command and Signalling Track-side Subsystem, track-to-train and train-to-track communication are fully standardised in this TSI. The specifications referenced in the sections below allow Control-Command and Signalling track-side functionality to be applied in a flexible way, so that it can be optimally integrated into the railway system. This flexibility shall be exploited without limiting the movement of TSI-compliant on-board subsystems.
Subsystem Part Basic parameters
Control-Command and Signalling On-board train protection 4.2.1, 4.2.2, 4.2.5, 4.2.6, 4.2.8, 4.2.9, 4.2.12, 4.2.14, 4.2.16
radio communication 4.2.4, 4.2.5, 4.2.6, 4.2.13, 4.2.14, 4.2.16
Control-Command and Signalling Track-side train protection 4.2.3, 4.2.5, 4.2.7, 4.2.8, 4.2.9, 4.2.15, 4.2.16
radio communication 4.2.4, 4.2.5, 4.2.7, 4.2.16
train detection 4.2.10, 4.2.11, 4.2.16
1. The design, implementation and use of a Control-Command and Signalling On-board or Track-side subsystem shall not export any requirements:(a)across the interface between Control-Command and Signalling On-board and Track-side subsystems in addition to the requirements specified in this TSI;(b)to any other subsystem in addition to the requirements specified in the corresponding TSIs. (a) across the interface between Control-Command and Signalling On-board and Track-side subsystems in addition to the requirements specified in this TSI; (b) to any other subsystem in addition to the requirements specified in the corresponding TSIs.
(a) across the interface between Control-Command and Signalling On-board and Track-side subsystems in addition to the requirements specified in this TSI;
(b) to any other subsystem in addition to the requirements specified in the corresponding TSIs.
(a) across the interface between Control-Command and Signalling On-board and Track-side subsystems in addition to the requirements specified in this TSI;
(b) to any other subsystem in addition to the requirements specified in the corresponding TSIs.
2. The requirements set out in Sections 4.2.1.1 and 4.2.1.2 below shall be respected.
1. setting the train characteristics (e.g. maximum train speed, braking performance);
2. selecting the supervision mode on the basis of information from track-side;
3. performing odometry functions;
4. locating the train in a coordinate system based on Eurobalise locations;
5. calculating the dynamic speed profile for its mission on the basis of train characteristics and of information from track-side;
6. supervising the dynamic speed profile during the mission;
7. providing the intervention function.
1. Communication with the Control-Command and Signalling Track-side Subsystem.(a)Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train);(b)Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train). This functionality is optional on-board unless Euroloop is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);(c)Radio data transmission for radio in-fill. See Annex A 4.2.2.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). This functionality is optional on-board unless radio data transmission for radio in-fill is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);(d)Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). Only mandatory on-board for ERTMS/ETCS Level 2 or ETCS Level 3 applications. (a) Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train); (b) Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train). This functionality is optional on-board unless Euroloop is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points); (c) Radio data transmission for radio in-fill. See Annex A 4.2.2.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). This functionality is optional on-board unless radio data transmission for radio in-fill is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points); (d) Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). Only mandatory on-board for ERTMS/ETCS Level 2 or ETCS Level 3 applications.
(a) Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train);
(b) Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train). This functionality is optional on-board unless Euroloop is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);
(c) Radio data transmission for radio in-fill. See Annex A 4.2.2.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). This functionality is optional on-board unless radio data transmission for radio in-fill is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);
(d) Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). Only mandatory on-board for ERTMS/ETCS Level 2 or ETCS Level 3 applications.
(a) Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train);
(b) Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train). This functionality is optional on-board unless Euroloop is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);
(c) Radio data transmission for radio in-fill. See Annex A 4.2.2.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). This functionality is optional on-board unless radio data transmission for radio in-fill is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);
(d) Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). Only mandatory on-board for ERTMS/ETCS Level 2 or ETCS Level 3 applications.
2. Communicating with the driver. See Annex A 4.2.2.e and Section 4.2.12 (ERTMS/ETCS DMI).
3. Communicating with the STM. See Section 4.2.6.1 (Interface between ERTMS/ETCS and STM). This function includes:(a)managing the STM output;(b)providing data to be used by the STM;(c)managing STM transitions. (a) managing the STM output; (b) providing data to be used by the STM; (c) managing STM transitions.
(a) managing the STM output;
(b) providing data to be used by the STM;
(c) managing STM transitions.
(a) managing the STM output;
(b) providing data to be used by the STM;
(c) managing STM transitions.
4. Managing information about the completeness of the train (train integrity) — mandatory for level 3, not required for level 1 or 2.
5. Equipment health monitoring and degraded mode support. This function includes:(a)initialising the on-board ERTMS/ETCS functionality;(b)providing degraded mode support;(c)isolating the on-board ERTMS/ETCS functionality. (a) initialising the on-board ERTMS/ETCS functionality; (b) providing degraded mode support; (c) isolating the on-board ERTMS/ETCS functionality.
(a) initialising the on-board ERTMS/ETCS functionality;
(b) providing degraded mode support;
(c) isolating the on-board ERTMS/ETCS functionality.
(a) initialising the on-board ERTMS/ETCS functionality;
(b) providing degraded mode support;
(c) isolating the on-board ERTMS/ETCS functionality.
6. Support data recording for regulatory purposes. See Section 4.2.14 (Interface to Data Recording for Regulatory Purposes).
7. Forwarding information/orders and receiving state information from rolling stock:(a)to the DMI. See Section 4.2.12 (ERTMS/ETCS DMI);(b)to/from the train interface unit. See Annex A 4.2.2.f. (a) to the DMI. See Section 4.2.12 (ERTMS/ETCS DMI); (b) to/from the train interface unit. See Annex A 4.2.2.f.
(a) to the DMI. See Section 4.2.12 (ERTMS/ETCS DMI);
(b) to/from the train interface unit. See Annex A 4.2.2.f.
(a) to the DMI. See Section 4.2.12 (ERTMS/ETCS DMI);
(b) to/from the train interface unit. See Annex A 4.2.2.f.
1. locating a specific train in a coordinate system based on Eurobalise locations (levels 2 and 3);
2. translating the information from track-side signalling equipment into a standard format for the Control-Command and Signalling On-board Subsystem;
3. sending movement authorities including track description and orders assigned to a specific train.
1. Communicating with the Control-Command and Signalling On-board Subsystem. This includes:(a)Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train) and Section 4.2.7.4 (Eurobalise/Line-side Electronic Unit (LEU));(b)Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train) and Section 4.2.7.5 (Euroloop/LEU). Euroloop is only relevant in level 1, in which it is optional;(c)Radio data transmission for radio in-fill. See Annex A 4.2.3.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio in-fill is only relevant in level 1, in which it is optional;(d)Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio data transmission is only relevant to levels 2 and 3. (a) Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train) and Section 4.2.7.4 (Eurobalise/Line-side Electronic Unit (LEU)); (b) Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train) and Section 4.2.7.5 (Euroloop/LEU). Euroloop is only relevant in level 1, in which it is optional; (c) Radio data transmission for radio in-fill. See Annex A 4.2.3.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio in-fill is only relevant in level 1, in which it is optional; (d) Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio data transmission is only relevant to levels 2 and 3.
(a) Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train) and Section 4.2.7.4 (Eurobalise/Line-side Electronic Unit (LEU));
(b) Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train) and Section 4.2.7.5 (Euroloop/LEU). Euroloop is only relevant in level 1, in which it is optional;
(c) Radio data transmission for radio in-fill. See Annex A 4.2.3.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio in-fill is only relevant in level 1, in which it is optional;
(d) Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio data transmission is only relevant to levels 2 and 3.
(a) Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train) and Section 4.2.7.4 (Eurobalise/Line-side Electronic Unit (LEU));
(b) Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train) and Section 4.2.7.5 (Euroloop/LEU). Euroloop is only relevant in level 1, in which it is optional;
(c) Radio data transmission for radio in-fill. See Annex A 4.2.3.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio in-fill is only relevant in level 1, in which it is optional;
(d) Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio data transmission is only relevant to levels 2 and 3.
2. Generating information/orders to the on-board ERTMS/ETCS, e.g. information related to closing/opening the air flaps, lowering/raising the pantograph, opening/closing the main power switch, changing from traction system A to traction system B. Implementation of this functionality is optional for track-side.
3. Managing the transitions between areas supervised by different Radio Block Centres (RBCs) (only relevant for levels 2 and 3). See Section 4.2.7.1 (Functional interface between RBCs) and Section 4.2.7.2 (Technical interface between RBCs).
1. ASCI features; Annex A 4.2.4.b;
2. SIM card; Annex A 4.2.4.c;
3. User-to-User Signalling; Annex A 4.2.4.d;
4. location-dependent addressing; Annex A 4.2.4.e.
1. confirmation of high-priority calls; Annex A 4.2.4.h;
2. functional addressing; Annex A 4.2.4.j;
3. presentation of functional numbers; Annex A 4.2.4.k.
1. the physical, electrical and electromagnetic values to be respected to allow safe functioning;
2. the communication protocol to be used;
3. the availability of the communication channel.
1. information from the ‘Handing Over’ RBC to the ‘Accepting’ RBC;
2. information from the ‘Accepting’ RBC to the ‘Handing Over’ RBC.
1. ergonomics (including visibility);
2. ERTMS/ETCS functions to be displayed;
3. ERTMS/ETCS functions triggered by driver input.
1. ergonomics (including visibility);
2. GSM-R functions to be displayed;
3. call-related information outgoing;
4. call-related information incoming.
1. data exchange between the on-board ERTMS/ETCS and the rolling stock recording device;
2. communication protocols;
3. physical interface.
1. the characteristics of retro-reflecting signs to ensure correct visibility;
2. the characteristics of interoperable marker boards.
Interface with Traffic Operation and Management TSI
Reference CCS TSI Reference Traffic Operation and Management TSI
Parameter Clause Parameter Clause
Operating rules (normal and degraded conditions) 4.4 Rule book 4.2.1.2.1
Operating rules 4.4
Visibility of track-side Control-Command and Signalling objects 4.2.15 Signal and line-side marker sighting 4.2.2.8
Train braking performance and characteristics 4.2.2 Braking performance 4.2.2.6
Use of sanding equipment
On-board flange lubrication 4.2.10 Rule book 4.2.1.2.1
Use of composite brake blocks
Interface to Data Recording for Regulatory Purposes 4.2.14 Data recording on-board 4.2.3.5
ETCS DMI 4.2.12 Train running number 4.2.3.2.1
GSM-R DMI 4.2.13 Train running number 4.2.3.2.1
Interface with Rolling Stock TSIs
Reference CCS TSI Reference Rolling Stock TSIs
Parameter Clause Parameter Clause
Compatibility with track-side train detection systems: vehicle design 4.2.10 Rolling stock characteristics to be compatible with train detection systems based on track circuits HS RS TSI
wheelset location 4.2.7.9.2
axle load 4.2.3.2
sanding 4.2.3.10
electrical resistance between wheels 4.2.3.3.1
LOC & PAS TSI 4.2.3.3.1.1
Wagon TSI 4.2.3.2
Rolling stock characteristics to be compatible with train detection systems based on axle counters HS RS TSI
wheelset geometry 4.2.7.9.2
wheels 4.2.7.9.3
LOC & PAS TSI 4.2.3.3.1.2
Wagon TSI 4.2.3.3.1
Rolling stock characteristics to be compatible with loop equipment HS RS TSI None
LOC & PAS TSI 4.2.3.3.1.3
Wagon TSI None
Electromagnetic compatibility between rolling stock and Control-Command and Signalling track-side equipment 4.2.11 Rolling stock characteristics to be compatible with train detection systems based on track circuits HS RS TSI 4.2.6.6.1
LOC & PAS TSI 4.2.3.3.1
Wagon TSI None
Rolling stock characteristics to be compatible with train detection systems based on axle counters HS RS TSI 4.2.6.6.1
LOC & PAS TSI 4.2.3.3.2
Wagon TSI None
Train braking performance and characteristics 4.2.2 Emergency braking performance HS RS TSI
Emergency braking 4.2.4.1
Service braking 4.2.4.4
LOC & PAS TSI
Emergency braking 4.2.4.5.2
Service braking 4.2.4.5.3
Wagon TSI 4.2.4.1.2
Position of Control-Command and Signalling on-board antennas 4.2.2 Kinematic gauge HS RS TSI 4.2.3.1
LOC & PAS TSI 4.2.3.1
Wagon TSI None
Isolation of on-board ERTMS/ETCS functionality 4.2.2 Operating rules HS RS TSI 4.2.7.9.1
LOC & PAS TSI 4.2.12.3
Wagon TSI None
Data interfaces 4.2.2 Monitoring and diagnostic concepts HS RS TSI 4.2.7.10
LOC & PAS TSI 4.2.1.1
Wagon TSI None
Visibility of track-side Control-Command and Signalling objects 4.2.15 External visibilityHead lights HS RS TSI 4.2.7.4.1.1
LOC & PAS TSI 4.2.7.1.1
Wagon TSI None
Driver’s external field of view HS RS TSI
line of sight 4.2.2.6 b
windscreen 4.2.2.7
LOC & PAS TSI
line of sight 4.2.9.1.3.1
windscreen 4.2.9.2
Wagon TSI None
Interface to data recording for regulatory purposes 4.2.14 Recording device HS RS TSI 4.2.7.10
LOC & PAS TSI 4.2.9.6
Wagon TSI None
Commands to rolling stock equipment 4.2.2 Phase separation HS RS TSI 4.2.8.3.6.7
4.2.3 LOC & PAS TSI 4.2.8.2.9.8
Wagon TSI None
Emergency braking command 4.2.2 Emergency braking command HS RS TSI None
LOC & PAS TSI 4.2.4.4.1
Wagon TSI None
Interface with Infrastructure TSI
Reference CCS TSI Reference Infrastructure TSI
Parameter Clause Parameter Clause
Train detection systems (space for installation) 4.2.10 Minimum infrastructure gauge HS 4.2.3
Structure gauge CR 4.2.4.1
Eurobalise communication (space for installation) 4.2.5.2 Minimum infrastructure gauge HS 4.2.3
Structure gauge CR 4.2.4.1
Euroloop communication (space for installation) 4.2.5.3 Minimum infrastructure gauge HS 4.2.3
Structure gauge CR 4.2.4.1
Visibility of track-side Control-Command and Signalling objects 4.2.15 Minimum infrastructure gauge HS 4.2.3
Structure gauge CR 4.2.4.1
Interface with Energy TSI
Reference CCS TSI Reference Energy TSI
Parameter Clause Parameter Clause
Commands to rolling stock equipment 4.2.2 Phase separation sections HS ENE TSI 4.2.21
4.2.3
System separation sections 4.2.22
Phase separation sections CR ENE TSI 4.2.19
System separation sections 4.2.20
1. all maintenance requirements and procedures (including health monitoring, diagnosis of events, test methods and tools and also the required professional competence) necessary for achieving essential requirements and values quoted in the mandatory requirements of this TSI throughout the equipment life-cycle (transport and storage before installation, normal operation, failures, repair work, checking and maintenance, decommissioning, etc.);
2. the health and safety risks that may affect the public and the maintenance staff;
3. the conditions for first line maintenance, i.e. the definition of Line Replaceable Units (LRUs), the definition of approved compatible versions of hardware and software, the procedures for replacing failed LRUs, and the conditions for storing LRUs and for repairing failed LRUs;
4. the checks to be carried out if equipment is subject to exceptional stress (e.g. adverse environmental conditions or abnormal shocks);
5. the checks to be carried out when maintaining equipment other than Control-Command and Signalling equipment and which influences the Control-Command and Signalling Subsystems (e.g. changing the wheel diameter).
1. ensure that the maintenance requirements as described in Section 4.5.1 (Responsibility of the Manufacturer of Equipment) are defined for all components within the scope of this TSI regardless of whether or not they are interoperability constituents;
2. complete the above requirements taking into account the risks arising from interactions between different components of the subsystem and interfaces to other subsystems.
1. Table 5.1.a for the Control-Command and Signalling On-board Subsystem;
2. Table 5.2.a for the Control-Command and Signalling Track-side Subsystem.
1. Table 5.1.b lists the groups of interoperability constituents of the Control-Command and Signalling On-board Subsystem.
2. Table 5.2.b lists the groups of interoperability constituents of the Control-Command and Signalling Track-side Subsystem.
1. in column 3, the functions and interfaces. Note that some interoperability constituents have functions and/or interfaces that are optional;
2. in column 4, the mandatory specifications for the conformity assessment of each function or interface (where applicable) by reference to the relevant section of Chapter 4.
N Interoperability constituent IC Characteristics Specific requirements to be assessed by reference to Chapter 4
1 ERTMS/ETCS on-board Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
On-board ETCS functionality (excluding odometry) 4.2.2
ERTMS/ETCS and GSM-R air gap interfaces 4.2.5
—RBC (levels 2 and 3) — RBC (levels 2 and 3) 4.2.5.1
— RBC (levels 2 and 3)
—Radio in-fill unit (optional level 1) — Radio in-fill unit (optional level 1) 4.2.5.1
— Radio in-fill unit (optional level 1)
—Eurobalise air gap — Eurobalise air gap 4.2.5.2
— Eurobalise air gap
—Euroloop air gap (optional level 1) — Euroloop air gap (optional level 1) 4.2.5.3
— Euroloop air gap (optional level 1)
Interfaces
—STM (implementation of interface K optional) — STM (implementation of interface K optional) 4.2.6.1
— STM (implementation of interface K optional)
—ERTMS/ETCS GSM-R on-board — ERTMS/ETCS GSM-R on-board 4.2.6.2
— ERTMS/ETCS GSM-R on-board
—Odometry — Odometry 4.2.6.3
— Odometry
—Key management system — Key management system 4.2.8
— Key management system
—ETCS ID Management — ETCS ID Management 4.2.9
— ETCS ID Management
—ERTMS/ETCS Driver-Machine Interface — ERTMS/ETCS Driver-Machine Interface 4.2.12
— ERTMS/ETCS Driver-Machine Interface
—Train interface — Train interface 4.2.2
— Train interface
—On-board recording device — On-board recording device 4.2.14
— On-board recording device
Physical environmental conditions 4.2.16
2 Odometry equipment Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
On-board ERTMS/ETCS functionality: only Odometry 4.2.2
Interfaces
—On-board ERTMS/ETCS — On-board ERTMS/ETCS 4.2.6.3
— On-board ERTMS/ETCS
Environmental conditions 4.2.16
3 Interface of External STM Interfaces
—On-board ERTMS/ETCS — On-board ERTMS/ETCS 4.2.6.1
— On-board ERTMS/ETCS
4 GSM-R voice cab radioNote: SIM card, antenna, connecting cables and filters are not part of this interoperability constituent Reliability, Availability, Maintainability, Safety (RAMS)Note: no requirement for safety 4.2.14.5.1
Basic communication functions 4.2.4.1
Voice and operational communication applications 4.2.4.2
Interfaces
—GSM-R air gap — GSM-R air gap 4.2.5.1
— GSM-R air gap
—GSM-R Driver-Machine Interface — GSM-R Driver-Machine Interface 4.2.13
— GSM-R Driver-Machine Interface
Environmental conditions 4.2.16
5 GSM-R ETCS Data only RadioNote: SIM card, antenna, connecting cables and filters are not part of this interoperability constituent Reliability, Availability, Maintainability, Safety (RAMS)Note: no requirement for safety 4.2.14.5.1
Basic communication functions 4.2.4.1
ETCS data communication applications 4.2.4.3
Interfaces
—On-board ERTMS/ETCS — On-board ERTMS/ETCS 4.2.6.2
— On-board ERTMS/ETCS
—GSM-R air gap — GSM-R air gap 4.2.5.1
— GSM-R air gap
Environmental conditions 4.2.16
6 GSM-R SIM card Basic communication functions 4.2.4.1
Environmental conditions 4.2.16
— RBC (levels 2 and 3)
— Radio in-fill unit (optional level 1)
— Eurobalise air gap
— Euroloop air gap (optional level 1)
— STM (implementation of interface K optional)
— ERTMS/ETCS GSM-R on-board
— Odometry
— Key management system
— ETCS ID Management
— ERTMS/ETCS Driver-Machine Interface
— Train interface
— On-board recording device
— On-board ERTMS/ETCS
— On-board ERTMS/ETCS
— GSM-R air gap
— GSM-R Driver-Machine Interface
— On-board ERTMS/ETCS
— GSM-R air gap
N Group of Interoperability constituents Characteristics Specific requirements to be assessed by reference to Chapter 4
1 ERTMS/ETCS on-boardOdometry equipment Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
On-board ERTMS/ETCS functionality 4.2.2
ERTMS/ETCS and GSM-R air gap interfaces 4.2.5
—RBC (levels 2 and 3) — RBC (levels 2 and 3) 4.2.5.1
— RBC (levels 2 and 3)
—Radio in-fill unit (optional level 1) — Radio in-fill unit (optional level 1) 4.2.5.1
— Radio in-fill unit (optional level 1)
—Eurobalise air gap — Eurobalise air gap 4.2.5.2
— Eurobalise air gap
—Euroloop air gap (optional level 1) — Euroloop air gap (optional level 1) 4.2.5.3
— Euroloop air gap (optional level 1)
Interfaces
—STM (implementation of interface K optional) — STM (implementation of interface K optional) 4.2.6.1
— STM (implementation of interface K optional)
—On-board ERTMS/ETCS – GSM-R — On-board ERTMS/ETCS – GSM-R 4.2.6.2
— On-board ERTMS/ETCS – GSM-R
—Key management system — Key management system 4.2.8
— Key management system
—ETCS-ID Management — ETCS-ID Management 4.2.9
— ETCS-ID Management
—ERTMS/ETCS Driver Machine Interface — ERTMS/ETCS Driver Machine Interface 4.2.12
— ERTMS/ETCS Driver Machine Interface
—Train interface — Train interface 4.2.2
— Train interface
—On-board recording device — On-board recording device 4.2.14
— On-board recording device
Physical environmental conditions 4.2.16
— RBC (levels 2 and 3)
— Radio in-fill unit (optional level 1)
— Eurobalise air gap
— Euroloop air gap (optional level 1)
— STM (implementation of interface K optional)
— On-board ERTMS/ETCS – GSM-R
— Key management system
— ETCS-ID Management
— ERTMS/ETCS Driver Machine Interface
— Train interface
— On-board recording device
N Interoperability constituent IC Characteristics Specific requirements to be assessed by reference to Chapter 4
1 RBC Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via Eurobalises, radio in-fill and Euroloop) 4.2.3
ERTMS/ETCS and GSM-R air gap interfaces: only radio communication with train 4.2.5.1
Interfaces
—Neighbouring RBC — Neighbouring RBC 4.2.7.1, 4.2.7.2
— Neighbouring RBC
—ERTMS/ETCS GSM-R track-side — ERTMS/ETCS GSM-R track-side 4.2.7.3
— ERTMS/ETCS GSM-R track-side
—Key management system — Key management system 4.2.8
— Key management system
—ETCS-ID Management — ETCS-ID Management 4.2.9
— ETCS-ID Management
Environmental conditions 4.2.16
2 Radio in-fill unit Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via Eurobalises, Euroloop and level 2/3 functionality) 4.2.3
ERTMS/ETCS and GSM-R air gap interfaces: only radio communication with train 4.2.5.1
Interfaces
—ERTMS/ETCS- GSM-R track-side — ERTMS/ETCS- GSM-R track-side 4.2.7.3
— ERTMS/ETCS- GSM-R track-side
—Key management system — Key management system 4.2.8
— Key management system
—ETCS-ID Management — ETCS-ID Management 4.2.9
— ETCS-ID Management
—Interlocking and LEU — Interlocking and LEU 4.2.3
— Interlocking and LEU
Environmental conditions 4.2.16
3 Eurobalise Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
ERTMS/ETCS and GSM-R air gap interfaces: only Eurobalise communication with train 4.2.5.2
Interfaces
—LEU – Eurobalise — LEU – Eurobalise 4.2.7.4
— LEU – Eurobalise
Environmental conditions 4.2.16
4 Euroloop Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
ERTMS/ETCS and GSM-R air gap interfaces: only Euroloop communication with train 4.2.5.3
Interfaces
—LEU – Euroloop — LEU – Euroloop 4.2.7.5
— LEU – Euroloop
Environmental conditions 4.2.16
5 LEU Eurobalise Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via radio in-fill, Euroloop and level 2 and level 3 functionality) 4.2.3
Interfaces
—LEU – Eurobalise — LEU – Eurobalise 4.2.7.4
— LEU – Eurobalise
Environmental conditions 4.2.16
6 LEU Euroloop Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via radio in-fill, Eurobalise and level 2 and level 3 functionality) 4.2.3
Interfaces
—LEU – Euroloop — LEU – Euroloop 4.2.7.5
— LEU – Euroloop
Environmental conditions 4.2.16
— Neighbouring RBC
— ERTMS/ETCS GSM-R track-side
— Key management system
— ETCS-ID Management
— ERTMS/ETCS- GSM-R track-side
— Key management system
— ETCS-ID Management
— Interlocking and LEU
— LEU – Eurobalise
— LEU – Euroloop
— LEU – Eurobalise
— LEU – Euroloop
N Group of interoperability constituents Characteristics Specific requirements to be assessed by reference to Chapter 4
1 EurobaliseLEU Eurobalise Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via Euroloop and level 2 and level 3 functionality) 4.2.3
ERTMS/ETCS and GSM-R air gap interfaces: only Eurobalise communication with train 4.2.5.2
Environmental conditions 4.2.16
2 EuroloopLEU Euroloop Reliability, Availability, Maintainability, Safety (RAMS) 4.2.14.5.1
Track-side ERTMS/ETCS functionality, (excluding communication via Eurobalise and level 2 and level 3 functionality) 4.2.3
ERTMS/ETCS and GSM-R air gap interfaces: only Euroloop communication with train 4.2.5.3
Environmental conditions 4.2.16
1. assessing the conformity of the interoperability constituents specified in Chapter 5 (see Section 6.2);
2. verifying the subsystems (see Section 6.3).
1. the use of Class B systems;
2. open points in the TSI;
3. derogations pursuant to Article 9 of the Railway Interoperability Directive;
4. specific cases described in Section 7.2.9.
1. rules for the design and installation of the Control-Command and Signalling On-board and the Track-side subsystems;
2. test specifications to prove that the Control-Command and Signalling On-board and Track-side Subsystems comply with the requirements of this TSI and are mutually compatible.
1. shall be consistent with the specifications referenced in this TSI and provide a technical description of functions and performances (e.g. reaction times) where these are relevant for the interaction between on-board and track-side subsystems;
2. shall be submitted in a standard format. See Annex A 4.2.2.c;
3. shall, unless otherwise specified in Annex A 4.2.2.c, cover at least the start of mission, the transition between levels, transition between modes that may be used on the line, the main identified degraded situations, the sending of emergency messages and any other relevant aspects specific to the line.
1. shall make a preliminary publication of the operational test scenarios, allowing all interested parties to comment on the consistency of the test scenarios with the specifications referenced in this TSI and their impact on other implementations or developments. The period for comments shall be defined with each publication and shall not exceed 6 months;
2. if the comments are negative, shall coordinate the efforts of the parties involved, in order to find an agreement, e.g. by changing the operational test scenarios;
3. shall progressively build and make publicly available a database of test scenarios that have successfully passed the step described above and representing the situations which occur in different implementations;
4. shall use the abovementioned data base to assess whether further mandatory test specifications are needed and whether it is necessary to draw up additional engineering rules for the Control-Command and Signalling On-board and Track-side subsystems.
1. either the type-examination procedure (Module CB) for the design and development phase in combination with the production quality management system procedure (Module CD) for the production phase; or
2. the type-examination procedure (Module CB) for the design and development phase in combination with the product verification procedure (Module CF); or
3. the full quality management system with design examination procedure (Module CH1).
1. with reference to Chapter 2 of the ‘Module CB’, ‘EC’-type examination must be carried out through a combination of production type and design type;
2. with reference to Chapter 3 of the ‘Module CF’ (product verification) statistical verification is not allowed, i.e. all interoperability constituents must be individually examined.
1. the requirements stated in Section 6.2.4.1 of this TSI shall be respected for the ‘On-board ERTMS/ETCS’ interoperability constituent;
2. the activities shown in Table 6.1 shall be carried out when assessing the conformity of an interoperability constituent or a group of interoperability constituents as defined in Chapter 5 of this TSI. All verifications shall be carried out by reference to the applicable table in Chapter 5 and the basic parameters indicated there.
Aspect What to assess supporting evidence
Functions, interfaces and performances Check that all mandatory functions, interfaces and performances as described in the basic parameters referenced in the relevant table of Chapter 5 are implemented and that they comply with the requirements of this TSI Design documentation and running of test cases and test scenarios, as described in the basic parameters referenced in the relevant table of Chapter 5
Check which optional functions and interfaces as described in the basic parameters referenced in the relevant table of Chapter 5 are implemented and that they comply with the requirements of this TSI Design documentation and running of test cases and test scenarios, as described in the basic parameters referenced in the relevant table of Chapter 5
Check which additional functions and interfaces (not specified in this TSI) are implemented and that they do not lead to conflicts with implemented functions specified in this TSI Impact analysis
Environment Check compliance with mandatory environmental conditions, where specified in the basic parameters referenced in the relevant table of Chapter 5 Tests, to ensure that the requirements of the basic parameters referenced in the relevant table of Chapter 5 are satisfied
In addition, check that the interoperability constituent functions correctly in the environmental conditions for which it is designed Tests according to the applicant’s specifications
Reliability, Availability, Maintainability, Safety (RAMS) Check compliance with the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5, i.e.:1.respect for quantitative Tolerable Hazard Rates (THRs) caused by random failures;2.the development process is able to detect and eliminate systematic failures. 1. respect for quantitative Tolerable Hazard Rates (THRs) caused by random failures; 2. the development process is able to detect and eliminate systematic failures. 1.Calculations for the THRs caused by random failures, based on supportable sources of reliability data.2.1.The manufacturer’s quality and safety management throughout design, manufacturing and testing conforms to a recognised standard (see Note).2.2.The software development life-cycle, the hardware development life-cycle and the integration of hardware and software have each been undertaken in accordance with a recognised standard (see Note).2.3.The safety verification and validation process has been undertaken in accordance with a recognised standard (see Note) and respects the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5.2.4.The functional and technical safety requirements (correct operation under fault-free conditions, effects of faults and of external influences) are verified in accordance with a recognised standard (see Note).Note: The standard shall satisfy at least the following requirements:1.be widely acknowledged in the railway domain. If this is not the case, the standard will have to be justified and be acceptable to the notified body;2.be relevant for the control of the considered hazards in the system under assessment;3.be publicly available for all actors who want to use it.See Annex A, Table A 3. 1. Calculations for the THRs caused by random failures, based on supportable sources of reliability data. 2.1. The manufacturer’s quality and safety management throughout design, manufacturing and testing conforms to a recognised standard (see Note). 2.2. The software development life-cycle, the hardware development life-cycle and the integration of hardware and software have each been undertaken in accordance with a recognised standard (see Note). 2.3. The safety verification and validation process has been undertaken in accordance with a recognised standard (see Note) and respects the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5. 2.4. The functional and technical safety requirements (correct operation under fault-free conditions, effects of faults and of external influences) are verified in accordance with a recognised standard (see Note). 1. be widely acknowledged in the railway domain. If this is not the case, the standard will have to be justified and be acceptable to the notified body; 2. be relevant for the control of the considered hazards in the system under assessment; 3. be publicly available for all actors who want to use it.
1. respect for quantitative Tolerable Hazard Rates (THRs) caused by random failures;
2. the development process is able to detect and eliminate systematic failures.
1. Calculations for the THRs caused by random failures, based on supportable sources of reliability data.
2.1. The manufacturer’s quality and safety management throughout design, manufacturing and testing conforms to a recognised standard (see Note).
2.2. The software development life-cycle, the hardware development life-cycle and the integration of hardware and software have each been undertaken in accordance with a recognised standard (see Note).
2.3. The safety verification and validation process has been undertaken in accordance with a recognised standard (see Note) and respects the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5.
2.4. The functional and technical safety requirements (correct operation under fault-free conditions, effects of faults and of external influences) are verified in accordance with a recognised standard (see Note).
1. be widely acknowledged in the railway domain. If this is not the case, the standard will have to be justified and be acceptable to the notified body;
2. be relevant for the control of the considered hazards in the system under assessment;
3. be publicly available for all actors who want to use it.
Check that the quantitative reliability target indicated by the applicant is met Calculations
Check compliance with maintenance requirements – Section 4.5.1 Document check
1. respect for quantitative Tolerable Hazard Rates (THRs) caused by random failures;
2. the development process is able to detect and eliminate systematic failures.
1. Calculations for the THRs caused by random failures, based on supportable sources of reliability data.
2.1. The manufacturer’s quality and safety management throughout design, manufacturing and testing conforms to a recognised standard (see Note).
2.2. The software development life-cycle, the hardware development life-cycle and the integration of hardware and software have each been undertaken in accordance with a recognised standard (see Note).
2.3. The safety verification and validation process has been undertaken in accordance with a recognised standard (see Note) and respects the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5.
2.4. The functional and technical safety requirements (correct operation under fault-free conditions, effects of faults and of external influences) are verified in accordance with a recognised standard (see Note).
1. be widely acknowledged in the railway domain. If this is not the case, the standard will have to be justified and be acceptable to the notified body;
2. be relevant for the control of the considered hazards in the system under assessment;
3. be publicly available for all actors who want to use it.
1. which optional and additional functions are implemented;
2. the applicable environmental conditions.
1. the type-examination procedure (Module SB) for the design and development phase in combination with the production quality management system procedure (Module SD) for the production phase; or
2. the type-examination procedure (Module SB) for the design and development phase in combination with the product verification procedure (Module SF); or
3. the full quality management system with design examination procedure (Module SH1).
1. the unit verification procedure (Module SG); or
2. the type-examination procedure (Module SB) for the design and development phase in combination with the production quality management system procedure (Module SD) for the production phase; or
3. the type-examination procedure (Module SB) for the design and development phase in combination with the product verification procedure (Module SF); or
4. the full quality management system with design examination procedure (Module SH1).
1. verification shall demonstrate that the Control-Command and Signalling On-board Subsystem complies with basic parameters when it is integrated into the vehicle;
2. the functionality and performances of interoperability constituents already covered by their EC Declaration of conformity do not require additional verifications.
Aspect What to assess supporting evidence
Use of interoperability constituents Check whether the interoperability constituents to be integrated into the subsystem are all covered by an ‘EC’ Declaration of conformity and a corresponding certificate. Existence and content of documents
Check restrictions on the use of Interoperability Constituents against the characteristics of the subsystem and of the environment Analysis by document check
For interoperability constituents that have been certified against older versions of the CCS TSI, check that the certificate still ensures compliance with the requirements of the TSI currently in force. Impact analysis by document checks
Integration of interoperability constituents in the subsystem Check the correct installation and functioning of the internal interfaces of the subsystem – Basic parameters 4.2.6 Checks according to specifications
Check that additional functions (not specified in this TSI) do not impact the mandatory ones Impact analysis
Check that the values of ETCS IDs are within the allowed range – Basic parameter 4.2.9 Check of design specifications
Integration with rolling stock Check the correct installation of equipment – Basic Parameters 4.2.2, 4.2.4, 4.2.14 and conditions for installation of equipment, as specified by the manufacturer Results of checks (according to specifications referenced in the Basic Parameters and the manufacturer’s installation rules)
Check that the Control-Command and Signalling On-board Subsystem is compatible with the rolling stock environment Document check (certificates of interoperability constituents and possible integration methods checked against characteristics of rolling stock)
Check that parameters (e.g. braking parameters) are correctly configured and that they are within the allowed range Document check (values of parameters checked against characteristics of rolling stock)
Integration with Class B Check that the external STM is connected to on-board ERTMS/ETCS with TSI-compliant interfaces Nothing to test: there is a standard interface already tested at interoperability constituent level. Its functioning has already been tested when checking the integration of interoperability constituents in the subsystem
Check that Class B functions implemented in the on-board ERTMS/ETCS – Basic parameter 4.2.6.1 – create no additional requirements for the Control-Command and Signalling Track-side Subsystem due to transitions Nothing to test: everything has already been tested at interoperability constituent level
Check that separate Class B equipment which is not connected to the on-board ERTMS/ETCS – Basic Parameter 4.2.6.1 – creates no additional requirements for Control-Command and Signalling Track-side Subsystem due to transitions Nothing to test: no interface(8)
Check that separate Class B equipment connected on-board ERTMS/ETCS using (partly) non-TSI compliant interfaces – basic parameter 4.2.6.1 – creates no additional requirements for the Control-Command and Signalling Track-side Subsystem due to transitions. Also check that ERTMS/ETCS functions are not affected Impact analysis
Integration with Control-Command and Signalling Track-side Subsystems Check that Eurobalise telegrams can be read (scope of this test is limited to checking that the antenna has been appropriately installed. The tests already carried out at Interoperability Constituent level should not be repeated) – Basic Parameter 4.2.5 Test using a certified Eurobalise: the ability to read correctly the telegram is the supporting evidence.
Check that Euroloop telegrams (if applicable) can be read – Basic Parameter 4.2.5 Test using a certified Euroloop: the ability to read correctly the telegram is the supporting evidence.
Check that the equipment can handle a GSM-R call for voice and data (if applicable) – Basic Parameter 4.2.5 Test with a certified GSM-R network. The ability to set up, maintain and disconnect a connection is the supporting evidence.
Reliability, Availability, Maintainability, Safety (RAMS) Check that the equipment complies with safety requirements – Basic Parameter 4.2.1 Application of procedures specified in the Common Safety Method
Check that the quantitative reliability target is met – Basic Parameter 4.2.1 Calculations
Check the compliance with requirements about maintenance – Section 4.5.2 Documents check
Integration with Control-Command and Signalling Track-side Subsystems and other subsystems:tests under operational conditions Test the behaviour of the subsystem under as many different operational conditions as reasonably possible (e.g. line gradient, train speed, vibrations, traction power, weather conditions, design of Control-Command and Signalling track-side functionality). The test must be able to verify:1.that odometry functions are correctly performed – basic parameter 4.2.22.that the on-board Control-Command and Signalling Subsystem is compatible with the rolling stock environment – basic parameter 4.2.16These tests must also be such as to increase confidence that there will be no systematic failures.The scope of these tests excludes tests already carried out at earlier stages: tests performed on the interoperability constituents and tests performed on the subsystem in a simulated environment shall be taken into account.Tests under operational conditions are not necessary for on-board GSM-R voice equipment. 1. that odometry functions are correctly performed – basic parameter 4.2.2 2. that the on-board Control-Command and Signalling Subsystem is compatible with the rolling stock environment – basic parameter 4.2.16 Reports of test runs.Note: Indicate in the certificate which conditions have been tested, which standards have been applied and the criteria for considering the tests terminated
1. that odometry functions are correctly performed – basic parameter 4.2.2
2. that the on-board Control-Command and Signalling Subsystem is compatible with the rolling stock environment – basic parameter 4.2.16
1. that odometry functions are correctly performed – basic parameter 4.2.2
2. that the on-board Control-Command and Signalling Subsystem is compatible with the rolling stock environment – basic parameter 4.2.16
1. line characteristics such as gradients, distances, positions of route elements and Eurobalises/Euroloops, locations to be protected, etc;
2. the signalling data and rules to be handled by the ERTMS/ETCS system.
1. Table 6.3 shows the checks that must be carried out to verify a Control-Command and Signalling Track-side Subsystem and the basic parameters that must be respected;
2. functionality and performances that have already been checked at the level of the interoperability constituents do not require additional verification.
Aspect What to assess supporting evidence
Use of interoperability constituents Check that all interoperability constituents to be integrated into the subsystem are covered by an EC declaration of conformity and the corresponding certificate. Existence and content of documents
Check restrictions on the use of interoperability constituents against the characteristics of the subsystem and of the environment Impact analysis by documents check
For interoperability constituents that have been certified against older versions of the Control-Command and Signalling TSI, check that the certificate still ensures compliance with the requirements of the TSI currently in force Impact analysis by comparison of specifications referenced in the TSI and certificates of the interoperability constituents
Use of train detection systems Check that the selected types comply with Control-Command and Signalling TSI requirements – Basic parameters 4.2.10, 4.2.11 Document check
Integration of interoperability constituents in the subsystem Check that the internal interfaces of the subsystem have been installed properly and function properly – Basic parameters 4.2.5, 4.2.7 Checks according to specifications
Check that additional functions (not specified in this TSI) do not impact the mandatory ones Impact analysis
Check that the values of ETCS IDs are within the allowed range – Basic Parameter 4.2.9 Check of design specifications
Integration with infrastructure Check that the equipment has been properly installed – Basic parameters 4.2.3, 4.2.4 and conditions for installation specified by the manufacturer Results of checks (according to specifications referenced in the basic parameters and manufacturer’s installation rules)
Check that the Control-Command and Signalling Track-side subsystem equipment is compatible with the track-side environment Document check (certificates of interoperability constituents and possible methods of integration checked against track-side characteristics)
Integration with track-side signalling Check that all functions required by the application are implemented in accordance with specifications referenced in this TSI – Basic parameter 4.2.3 Document check (applicant’s design specification and certificates of interoperability constituents)
Check the correct configuration of parameters (Eurobalise telegrams, RBC messages, marker boards positions, etc.) Document check (values of parameters checked against characteristics of track-side and of signalling)
Check that the interfaces are correctly installed and function properly. Design verification and tests according to information supplied by the applicant
Check that the Control-Command and Signalling Track-side subsystem operates correctly according to information at the interfaces with track-side signalling (e.g. appropriate generation of Eurobalise telegrams by a LEU or of message by RBC) Design verification and tests according to the information supplied by the applicant
Integration with Control-Command and Signalling On-board Subsystems and with rolling stock Check the GSM-R coverage – Basic Parameter 4.2.4 On-site measurements
Check the compliance of the train detection systems with the requirements of this TSI – Basic Parameter 4.2.10 On-site measurements
Check that the train detection systems comply with the requirements of this TSI – Basic parameters 4.2.10 and 4.2.11 Check evidence from existing installations (for systems already in use); perform tests according to standards for new types
Check that all functions required by the application are implemented in accordance with specifications referenced in this TSI – basic parameters 4.2.3, 4.2.4 and 4.2.5 Reports of tests of the operational scenarios specified in Section 6.1.2 with different certified Control-Command and Signalling On-board Subsystems. The report shall indicate which operational scenarios have been tested, which on-board equipment has been used and whether tests have been performed in laboratories, test lines or real implementation.
Reliability, Availability, Maintainability, Safety (RAMS) Check compliance with safety requirements – Basic Parameter 4.2.1 Application of procedures specified in the Common Safety Method
Check that quantitative reliability targets are respected – Basic Parameter 4.2.1 Calculations
Check the compliance with requirements about maintenance – Section 4.5.2 Document check
Integration with Control-Command and Signalling On-board Subsystems and rolling stock:tests under operational conditions Test the behaviour of the subsystem under such different operational conditions as reasonably feasible (e.g. train speed, number of trains on the line, weather conditions). The test must be able to verify:1.the performance of train detection systems – Basic parameters 4.2.10, 4.2.11,2.that the Control-Command and Signalling Track-side subsystem is compatible with track-side environment – Basic parameter 4.2.16These tests will also increase confidence in the absence of systematic failures.The scope of these tests excludes tests already done in previous steps: tests performed at the level of interoperability constituents and tests performed on the subsystem in a simulated environment shall be taken into account. 1. the performance of train detection systems – Basic parameters 4.2.10, 4.2.11, 2. that the Control-Command and Signalling Track-side subsystem is compatible with track-side environment – Basic parameter 4.2.16 Reports of test runs.Note: Indicate in the certificate which conditions have been tested, which standards have been applied and the criteria for considering the tests terminated.
1. the performance of train detection systems – Basic parameters 4.2.10, 4.2.11,
2. that the Control-Command and Signalling Track-side subsystem is compatible with track-side environment – Basic parameter 4.2.16
1. the performance of train detection systems – Basic parameters 4.2.10, 4.2.11,
2. that the Control-Command and Signalling Track-side subsystem is compatible with track-side environment – Basic parameter 4.2.16
1. the TSI requirements for the part in question have been respected;
2. the TSI requirements already assessed are not prejudiced.
1. The non-implemented function, interface or performance is not required for integrating the interoperability constituent into a subsystem because of specific conditions of use, for example(9):(a)the on-board ERTMS/ETCS interface to STM if the interoperability constituent is intended for installation on vehicles where no external STM is needed;(b)the RBC interface to other RBCs, if the RBC is intended for use in an application where no neighbouring RBCs are planned. (a) the on-board ERTMS/ETCS interface to STM if the interoperability constituent is intended for installation on vehicles where no external STM is needed; (b) the RBC interface to other RBCs, if the RBC is intended for use in an application where no neighbouring RBCs are planned.
(a) the on-board ERTMS/ETCS interface to STM if the interoperability constituent is intended for installation on vehicles where no external STM is needed;
(b) the RBC interface to other RBCs, if the RBC is intended for use in an application where no neighbouring RBCs are planned.
(a) the on-board ERTMS/ETCS interface to STM if the interoperability constituent is intended for installation on vehicles where no external STM is needed;
(b) the RBC interface to other RBCs, if the RBC is intended for use in an application where no neighbouring RBCs are planned.
2. The certificate indicates which functions, interfaces or performance are not implemented and states the corresponding restrictions on the use of the interoperability constituent. This information will make it possible to identify the conditions under which the interoperability constituent can be used and the restrictions that will apply to the interoperability of a subsystem incorporating it.
1. Train protection
2. Radio communication
3. Train detection
1. GSM-R functions and interfaces
2. ERTMS/ETCS functions and interfaces
3. Train detection system compatibility with rolling stock
1. using an STM operating via the standard interface (‘external STM’); or
2. integrated within the ERTMS/ETCS equipment or connected via a non-standard interface; or
3. independently from the ERTMS/ETCS equipment, for example via a system that enables switching between equipment. The Railway Undertaking must then ensure that the transitions between Class A and Class B train protection are carried out in conformity with the requirements of this TSI and with the national rules for the Class B system.
— an ETCS Level 3 Track-side application requires train integrity supervision on board,
— an ETCS Level 1 Track-side application with in-fill requires corresponding in-fill functionality on board if the release speed is set to zero for safety reasons (e.g. protection of danger points),
— when ETCS requires data transmission by radio, the data transmission services of GSM-R must fulfil the ETCS data transmission requirements,
— an on-board assembly, which incorporates a KER STM, may make it necessary to implement the K-interface.
1. installing for the first time the radio part of a Control-Command and Signalling Track-side Subsystem;
2. upgrading the radio part of a Control-Command and Signalling Track-side Subsystem already in service in such a way that it changes the functions or the performance of the subsystem. This does not include the modifications deemed necessary to mitigate safety-related defects in the legacy installation.
1. installing for the first time the radio part of a Control-Command and Signalling On-board Subsystem;
2. upgrading the radio part of a Control-Command and Signalling On-board Subsystem already in service in such a way that it changes the functions or the performance of the subsystem. This does not apply to modifications deemed necessary to mitigate safety-related defects in the legacy installation.
1. upgrading the train detection system;
2. renewing the train detection system, provided that respecting the requirements of this TSI does not imply unwanted modifications or upgrades of other track-side or on-board systems;
3. renewing the train detection system, where this is required by the upgrade or renewal of track-side systems that use information from the train detection system;
4. removing Class B train protection systems (where the train detection and train protection systems are integrated).
Specific case Category Notes
4.2.10   Track-side Train Detection SystemsIndex 77, Section 3.1.2.4:The distance between first and last axle L – (b1+ b2) (Figure 1) is at least 15 000  mm T3 Applicable on HS L1This Specific Case is linked with the use of TVM
4.2.10   Track-side Train Detection SystemsIndex 77, Section 3.1.8:The weight of an isolated vehicle or a trainset is at least 40 t.If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000  mm The weight of an isolated vehicle or a trainset is at least 40 t. If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000  mm T3 Applicable on HS L1, L2, L3, L4This Specific Case is linked with the use of TVM
The weight of an isolated vehicle or a trainset is at least 40 t.
If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000  mm
The weight of an isolated vehicle or a trainset is at least 40 t.
If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000  mm
Specific case Category Notes
4.2.10   Track-side Train Detection SystemsIndex 77, Section 3.1.2.4:The distance between first and last axle L – (b1+ b2) (Figure 1) is at least 15 000  mm T3 Applicable on High-Speed L 1This Specific Case is linked with the use of TVM
4.2.10 –   Track-side Train Detection SystemsIndex 77, Section 3.1.4.1:In addition to the requirements in Section 3.1.4.1, sanding for traction purposes on multiple units:(a)is not permitted ahead of the leading axle below 40 km/h; and(b)is only permitted where it can be demonstrated that at least a further six axles of the multiple unit are beyond the laying position. (a) is not permitted ahead of the leading axle below 40 km/h; and (b) is only permitted where it can be demonstrated that at least a further six axles of the multiple unit are beyond the laying position. T3
(a) is not permitted ahead of the leading axle below 40 km/h; and
(b) is only permitted where it can be demonstrated that at least a further six axles of the multiple unit are beyond the laying position.
4.2.12   ERTMS/ETCS DMI (Driver Machine Interface)Index 51:It is permissible to use an alphanumeric keyboard to enter the train running number if support for alphanumeric train running numbers is required by the technical rule notified for this purpose. T3 This specific case is needed as soon as the open point related to the DMI specification is closed.There is no impact on interoperability
4.2.12   ERTMS/ETCS DMI (Driver Machine Interface)Index 51:It is permissible for the ETCS DMI to display dynamic train speed information in miles per hour (and indicate ‘mph’) when operating on parts of the GB mainline network. T3 This specific case is needed as soon as the open point related to the DMI specification is closed.There is no impact on interoperability
(a) is not permitted ahead of the leading axle below 40 km/h; and
(b) is only permitted where it can be demonstrated that at least a further six axles of the multiple unit are beyond the laying position.
Specific case Category Notes
4.2.10   Track-side Train Detection SystemsIndex 77, Section 3.1.2.4:The distance between first and last axle L – (b1+ b2) (Figure 1) is at least 15 000  mm T3 This Specific Case is linked with the use of TVM
4.2.10   Track-side Train Detection SystemsIndex 77, Section 3.1.9:The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS. The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit). In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS. T3 This specific case may be revised when the open point related to the frequency management for track circuits is closed
The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).
In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS.
4.2.10 –   Track-side Train Detection SystemsIndex 77, Section 3.1.8:The weight of an isolated vehicle or a trainset is at least 40 t.If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000  mm. The weight of an isolated vehicle or a trainset is at least 40 t. If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000  mm. T3 This Specific Case is linked with the use of TVM
The weight of an isolated vehicle or a trainset is at least 40 t.
If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000  mm.
4.2.10 –   Track-side Train Detection SystemsIndex 77, Section 3.1.3.2:Dimension D (Figure 2) is not less than:450 mm independently of the speed Dimension D (Figure 2) is not less than: 450 mm independently of the speed 5 years
Dimension D (Figure 2) is not less than:
450 mm independently of the speed
The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).
In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS.
The weight of an isolated vehicle or a trainset is at least 40 t.
If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000  mm.
Dimension D (Figure 2) is not less than:
450 mm independently of the speed
Specific case Category Notes
4.2.10   Track-side Train Detection SystemsIndex 77, Section 3.1.9:The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS. The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit). In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS. T3 This specific case may be revised when the open point related to the frequency management for track circuits is closed
The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).
In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS.
The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).
In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS.
Specific case Category Notes
4.2.10   Track-side Train Detection SystemsIndex 77, Section 3.1.3.4:The range of the dimension Sh(Figure 2) is not less than 26,25 mm T3 This specific case is needed as long as ČME locomotives operate on Lithuania 1 520  mm network
Specific case Category Notes
4.2.4   Mobile communication functions for railways – GSM-RIndex 65, statement 4.2.3:It is permissible to put in service on-board Control-Command and Signalling Subsystems including 2 Watt GSM-R voice cab radios and ETCS data only radios. The subsystems shall be able to operate in networks with – 82 dBm. P No impact on interoperability
Specific case Category Notes
4.2.10   Track-side Train Detection SystemsIndex 77, Section 3.1.2.4:1.The output of the sanding devices fitted to the vehicle shall not exceed 0,3 l per minute per rail.2.The sanding in the stations identified in the infrastructure register is prohibited.3.The sanding in the area of switches is prohibited.4.For emergency braking, no restrictions shall apply 1. The output of the sanding devices fitted to the vehicle shall not exceed 0,3 l per minute per rail. 2. The sanding in the stations identified in the infrastructure register is prohibited. 3. The sanding in the area of switches is prohibited. 4. For emergency braking, no restrictions shall apply T3
1. The output of the sanding devices fitted to the vehicle shall not exceed 0,3 l per minute per rail.
2. The sanding in the stations identified in the infrastructure register is prohibited.
3. The sanding in the area of switches is prohibited.
4. For emergency braking, no restrictions shall apply
1. The output of the sanding devices fitted to the vehicle shall not exceed 0,3 l per minute per rail.
2. The sanding in the stations identified in the infrastructure register is prohibited.
3. The sanding in the area of switches is prohibited.
4. For emergency braking, no restrictions shall apply
1. installing for the first time the train protection part of a Control-Command and Signalling Track-side Subsystem (with or without a Class B system); or
2. upgrading the existing train protection part of a Control-Command and Signalling Track-side Subsystem, where this would change the functions, performance and/or interoperability-relevant interfaces (air gaps) of the existing legacy system. This does not apply to modifications deemed necessary to mitigate safety-related defects in the legacy installation.
1. installing for the first time the train protection part of a Control-Command and Signalling Subsystem; or
2. upgrading the train protection part of a Control-Command and Signalling Subsystem already in service, where this changes the functions or the performance of the subsystem.
1. the notifications, if needed, referred to in Section 7.3.2.5 were received in time and were comprehensive;
2. the file referred to in Section 7.3.2.6, first paragraph, contains clear evidence that the causes for the delay were beyond the Member State’s control;
3. a competent authority is responsible for coordinating on-board and track-side suppliers and for integrating and testing of products;
4. appropriate use has been made of existing laboratories;
5. evidence is given that appropriate measures have been taken to minimise the additional delay.
1. allowing only ERTMS equipped locomotives to access ERTMS-equipped lines, so that existing national systems can be decommissioned;
2. requesting that new shunting locomotives and/or other new railway vehicles equipped with a driving cab, even if designed exclusively for national service or regional border crossing service, be equipped with ERTMS.
1. installing any new train protection part of a Control-Command and Signalling On-board Subsystem; or
2. upgrading any existing train protection part of a Control-Command and Signalling On-board Subsystem, where this would change the functions, performances and/or interoperability-relevant interfaces of the existing legacy system. This does not apply to modifications deemed necessary to mitigate safety related defects in the legacy system.
Country Freight transport area Date Remark
Belgium Antwerpen 31.12.2015 A link to Rotterdam shall also be provided by 2020.
Gent 31.12.2020
Zeebrugge 31.12.2020
Bulgaria Burgas 31.12.2020 The connection to corridor E implies equipping the Burgas-Sofia section and the Sofia-Vidin-Calafat and Calafat-Curtici sections in Romania (PP22).
Czech Republic Praha 31.12.2015
Lovosice 31.12.2020
Denmark Taulov 31.12.2020 Connecting this terminal implies that the Flensburg-Padborg line is chosen to be an ERTMS equipped link – see corridor B footnote.
Germany Dresden(18) 31.12.2020 By 2020, a direct link between corridor E and corridor F (from Dresden to Hannover) shall also be ensured.
Lübeck 31.12.2020
Duisburg 31.12.2015
Hamburg(19) 31.12.2020
Köln 31.12.2015
München 31.12.2015
Hannover 31.12.2015
Rostock 31.12.2015
Ludwigshafen/Mannheim 31.12.2015
Nürnberg 31.12.2020
Greece Pireás 31.12.2020 The connection to Corridor E implies equipping the Kulata-Sofia section in Bulgaria.
Spain Algeciras 31.12.2020
Madrid 31.12.2020
Pamplona 31.12.2020 Three connections are requested. A connection to Paris via Hendaye, a connection from Pamplona to Madrid and a connection from Pamplona to corridor D via Zaragoza.
Zaragoza 31.12.2020
Tarragona 31.12.2020
Barcelona 31.12.2015
Valencia 31.12.2020
France Marseille 31.12.2020
Perpignan 31.12.2015
Avignon 31.12.2015
Lyon 31.12.2015
Le Havre 31.12.2020
Lille 31.12.2020
Dunkerque 31.12.2020
Paris 31.12.2020 By 2020 the following connections will be provided: (i) Hendaye; (ii) Channel Tunnel; (iii) Dijon; and (iv) Metz via Epernay and Châlons-en-Champagne.
Italy La Spezia 31.12.2020
Genova 31.12.2015
Gioia Tauro 31.12.2020
Verona 31.12.2015
Milano 31.12.2015
Taranto 31.12.2020
Bari 31.12.2020
Padova 31.12.2015
Trieste 31.12.2015
Novara 31.12.2015
Venezia 31.12.2020
Bologna 31.12.2020
Roma 31.12.2020
Luxembourg Bettembourg 31.12.2015
Hungary Budapest 31.12.2015
Netherlands Amsterdam 31.12.2020
Rotterdam 31.12.2015 A link to Antwerpen shall also be provided by 2020.
Austria Graz 31.12.2020
Wien 31.12.2020
Poland Gdynia 31.12.2015
Katowice 31.12.2020
Wrocław 31.12.2015 By 2020 the Wrocław-Legnica line, shall be equipped in order to ensure a direct link to the German border (Görlitz).
Gliwice 31.12.2015
Poznań 31.12.2015
Warszawa 31.12.2015
Portugal Sines 31.12.2020
Lisboa 31.12.2020
Romania Constanța 31.12.2015
Slovenia Koper 31.12.2015
Ljubljana 31.12.2015
Slovakia Bratislava 31.12.2015
United Kingdom Bristol This terminal will be connected as corridor C is extended to the Channel Tunnel.
Reference in Chapter 4 Index number (See Table A 2)
4.1
4.1a 1
4.1b 32
4.1c 3
4.2.1
4.2.1 a 27, 78
4.2.1 b 28
4.2.2
4.2.2.a 14
4.2.2.b 1, 4, 13, 15
4.2.2.c 31, 37
4.2.2.d 18, 20
4.2.2.e 6,
4.2.2.f 7
4.2.3
4.2.3 a 14
4.2.3 b 1, 4, 13, 15
4.2.3 c 31, 37 b, c, d
4.2.3 d 18, 21
4.2.4
4.2.4 a 64, 65
4.2.4 b 66
4.2.4 c 67
4.2.4 d 68
4.2.4 e 73, 74
4.2.4 f 32, 33
4.2,4 g 48
4.2,4 h 69, 70
4.2.4 j 71, 72
4.2.4 k 75, 76
4.2.5
4.2.5 a 64, 65
4.2.5 b 10, 39, 40
4.2.5c 19, 20
4.2.5 d 9, 43
4.2.5 e 16, 50
4.2.6
4.2.6 a 8, 25, 26, 49
4.2.6 b 45
4.2.6 c 46
4.2.6 d 34
4.2.6 e 20
4.2.6 f 44
4.2.7
4.2.7 a 12
4.2.7 b 62, 63
4.2.7 c 34
4.2.7 d 9
4.2.7 e 16
4.2.8
4.2.8 a 11
4.2.9
4.2.9 a 23
4.2.10
4.2.10 a 77 (Section 3.1)
4.2.11
4.2.11 a 77 (Section 3.2)
4.2.12
4.2.12 a 51
4.2.13
4.2.13 a 32, 33, 51
4.2.14
4.2.14 a 5
4.2.15
4.2.15 a 38
Note: specifications indicated as ‘Reserved’ in Table A 2 correspond to the open points listed in Annex G.
Index N Reference Name of Specification Version Notes
1 ERA/ERTMS/003204 ERTMS/ETCS Functional requirement specification 5.0
2 Intentionally deleted
3 UNISIG SUBSET-023 Glossary of terms and abbreviations 2.0.0
4 UNISIG SUBSET-026 System requirement specification 2.3.0
5 UNISIG SUBSET-027 FFFIS Juridical recorder-downloading tool 2.3.0 Note 1
6 UNISIG SUBSET-033 FIS for man-machine interface 2.0.0
7 UNISIG SUBSET-034 FIS for the train interface 2.0.0
8 UNISIG SUBSET-035 Specific transmission module FFFIS 2.1.1
9 UNISIG SUBSET-036 FFFIS for Eurobalise 2.4.1
10 UNISIG SUBSET-037 EuroRadio FIS 2.3.0
11 UNISIG SUBSET-038 Offline key management FIS 2.3.0
12 UNISIG SUBSET-039 FIS for the RBC/RBC handover 2.3.0
13 UNISIG SUBSET-040 Dimensioning and engineering rules 2.3.0
14 UNISIG SUBSET-041 Performance requirements for interoperability 2.1.0
15 ERA SUBSET-108 Interoperability related consolidation on TSI Annex A documents 1.2.0
16 UNISIG SUBSET-044 FFFIS for Euroloop subsystem 2.3.0
17 Intentionally deleted
18 UNISIG SUBSET-046 Radio in-fill FFFS 2.0.0
19 UNISIG SUBSET-047 Track-side-trainborne FIS for radio in-fill 2.0.0
20 UNISIG SUBSET-048 Trainborne FFFIS for radio in-fill 2.0.0
21 UNISIG SUBSET-049 Radio in-fill FIS with LEU/interlocking 2.0.0
22 Intentionally deleted
23 UNISIG SUBSET-054 Assignment of values to ETCS variables 2.1.0
24 Intentionally deleted
25 UNISIG SUBSET-056 STM FFFIS Safe time layer 2.2.0
26 UNISIG SUBSET-057 STM FFFIS Safe link layer 2.2.0
27 UNISIG SUBSET-091 Safety requirements for the technical interoperability of ETCS in levels 1 and 2 2.5.0
28 Reserved Reliability — availability requirements
29 UNISIG SUBSET-102 Test specification for interface ‘K’ 1.0.0
30 Intentionally deleted
31 UNISIG SUBSET-094 Functional requirements for an on-board reference test facility 2.0.2
32 EIRENE FRS GSM-R Functional requirements specification 7
33 EIRENE SRS GSM-R System requirements specification 15
34 A11T6001 12 (MORANE) Radio transmission FFFIS for EuroRadio 12
35 Intentionally deleted
36 a Intentionally deleted
36 b Intentionally deleted
36 c UNISIG SUBSET-074-2 FFFIS STM Test cases document 1.0.0
37 a Intentionally deleted
37 b UNISIG SUBSET-076-5-2 Test cases related to features 2.3.1
37 c UNISIG SUBSET-076-6-3 Test sequences 2.3.1
37 d UNISIG SUBSET-076-7 Scope of the test specifications 1.0.2
37 e Intentionally deleted
38 06E068 ETCS Marker-board definition 2.0
39 UNISIG SUBSET-092-1 ERTMS EuroRadio conformance requirements 2.3.0
40 UNISIG SUBSET-092-2 ERTMS EuroRadio test cases safety layer 2.3.0
41 Intentionally deleted
42 Intentionally deleted
43 UNISIG SUBSET 085 Test specification for Eurobalise FFFIS 2.2.2
44 Reserved Odometry FIS
45 UNISIG SUBSET-101 Interface ‘K’ specification 1.0.0
46 UNISIG SUBSET-100 Interface ‘G’ specification 1.0.1
47 Intentionally deleted
48 Reserved Test specification for mobile equipment GSM-R
49 UNISIG SUBSET-059 Performance requirements for STM 2.1.1
50 UNISIG SUBSET-103 Test specification for Euroloop 1.0.0
51 Reserved Ergonomic aspects of the DMI
52 UNISIG SUBSET-058 FFFIS STM Application layer 2.1.1
53 Intentionally deleted
54 Intentionally deleted
55 Intentionally deleted
56 Intentionally deleted
57 Intentionally deleted
58 Intentionally deleted
59 Intentionally deleted
60 Intentionally deleted
61 Intentionally deleted
62 ReservedUNISIG SUBSET-099 RBC-RBC Test specification for safe communication interface
63 UNISIG SUBSET-098 RBC-RBC Safe communication interface 1.0.0
64 EN 301 515 Global System for Mobile Communication (GSM); Requirements for GSM operation on railways 2.3.0 Note 2
65 TR 102 281 Detailed requirements for GSM operation on railways 1.0.0 Note 3
66 (MORANE) A 01 T 0004 1 ASCI Options for Interoperability 1
67 (MORANE) P 38 T 9001 FFFIS for GSM-R SIM Cards 4.1
68 ETSI TS 102 610 Railway Telecommunication; GSM; Usage of the UUIE for GSM operation on railways 1.1.0
69 (MORANE) F 10 T 6002 FFFS for Confirmation of High-Priority Calls 4
70 (MORANE) F 12 T 6002 FIS for Confirmation of High-Priority Calls 4
71 (MORANE) E 10 T 6001 FFFS for Functional Addressing 4
72 (MORANE) E 12 T 6001 FIS for Functional Addressing 5.1
73 (MORANE) F 10 T6001 FFFS for Location Dependent Addressing 4
74 (MORANE) F 12 T6001 FIS for Location Dependent Addressing 3
75 (MORANE) F 10 T 6003 FFFS for Presentation of Functional Numbers to Called and Calling Parties 4
76 (MORANE) F 12 T 6003 FIS for Presentation of Functional Numbers to Called and Calling Parties 4
77 ERA/ERTMS/033281 Interfaces between CCS track-side and other subsystems 1.0
78 Reserved Safety requirements for ETCS DMI functions
Note 1: only the functional description of information to be recorded is mandatory, not the technical characteristics of the interface.
Note 2: the specifications listed in Section 2.1 of EN 301 515 are mandatory.
Note 3: the change requests (CRs) listed in Tables 1 and 2 of TR 102 281 are mandatory.
No Reference Document name and comments Version
A1 EN 50126 Railway applications — The specification and demonstration of reliability, availability, maintainability and safety (RAMS) 1999
A2 EN 50128 Railway applications — Communication, signalling and processing systems — Software for railway control and protection systems 2001
A3 EN 50129 Railway applications — Communication, signalling and processing systems — Safety related electronic systems for signalling 2003
A4 EN 50159-1 Railway applications — Communication, signalling and processing systems — Part 1 2001
A5 EN 50159-2 Railway applications — Communication, signalling and processing systems — Part 2: Safety related communication in open transmission systems 2001
Open Point Notes
Braking aspects This open point will be solved by ERTMS/ETCS baseline 3. The harmonised braking model is already included for information purposes in Annex A, Table A 2, Index 15.
Index 28 availability Frequent occurrence of degraded situations caused by failures of Control-Command and Signalling equipment will decrease the system safety. To avoid this, minimum reliability/availability requirements that shall be specified.
Index 78 safety requirements for ETCS DMI functions This open point is related to the interface between ETCS on-board and driver, i.e. errors in displaying information and in entering data and commands
Index 51 Ergonomic aspects of the DMI This open point will be solved by ERTMS/ETCS baseline 3. A specification for information purposes already exists.
Minimum wheel diameter for speed greater than 350 km/h See Annex A, Table A 2, Index 77
Minimum axle distance for speed greater than 350 km/h See Annex A, Table A 2, Index 77
Metal and inductive components free space between wheels See Annex A, Table A 2, Index 77This is not an open point for freight wagons
Characteristics of sand applied to tracks See Annex A, Table A 2, Index 77
Vehicle metal mass See Annex A, Table A 2, Index 77
Combination of rolling stock characteristics for the purpose of adequate dynamic shunting impedance See Annex A, Table A 2, Index 77
Electromagnetic interferences (traction current) See Annex A, Table A 2, Index 77
Electromagnetic interferences (electromagnetic fields) See Annex A, Table A 2, Index 77This is not an open point for power systems other than DC
DC and low frequency components of traction current See Annex A, Table A 2, Index 77
Use of magnetic/eddy current brakes See Annex A, Table A 2, Index 77
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Directive 2008/57/EC of the European Parliament and of the Council of 17 June 2008 on the interoperability of the rail system within the Community(1), and in particular the second subparagraph of Article 6(1) thereof,
(1) Commission Decision 2006/679/EC of 28 March 2006 concerning the technical specification for interoperability relating to the control-command and signalling subsystem of the trans-European conventional rail system(2)laid down the technical specifications for interoperability (‘TSI’) relating to the control-command and signalling subsystem of the trans-European conventional rail system.
(2) Commission Decision 2006/860/EC of 7 November 2006 concerning a technical specification for interoperability relating to the control-command and signalling subsystem of the trans-European high speed rail system(3)lays down the TSI relating to the control-command and signalling subsystem of the trans-European high-speed rail system.
(3) The essential requirements for both the conventional and the high-speed networks must be identical, as must their functional and technical specifications, their interoperability constituents and interfaces, and the procedures for assessing the conformity or the suitability for use of the interoperability constituents or the ‘EC’ verification of their control-command and signalling subsystems.
(4) The implementation strategies should remain specific to each type of network and the existing requirements for the conventional trans-European network and for the high-speed trans-European network should remain unchanged. The European railway agency (‘Agency’) was given a framework mandate to perform certain activities.
(5) On 31 January 2011 the Agency gave its recommendation on the technical specification for interoperability relating to the subsystems ‘control-command and signalling’ of the trans-European rail system(4). This Decision is based on that recommendation.
(6) In the interest of clarity, Decisions 2006/679/EC and 2006/860/EC should therefore be replaced by this Decision.
(7) The changes introduced regarding safety requirements (Section 4.2.1 of Annex III) are based on the analysis that the text in the CCS TSIs in force leaves room for interpretations. The introduced changes have no negative impact in the overall safety level.
(8) The fitting of ERTMS/ETCS should be mandatory in the case of new installations or upgrade of the train protection part of a CCS assembly for railway infrastructure projects benefiting from EU financial support. Such fitting should in principle be carried out in the frame of the EU funded project. In certain cases, it is however necessary to grant a derogation to this implementation rule. The scope of such derogation is limited to the implementation strategy of the ‘control-command and signalling TSI’.
(9) The Agency has listed in the technical document ‘List of CCS Class B systems’ the national legacy control-command and signalling systems (‘Class B systems’). Those systems may still be requested on board locomotives and traction units to run on certain lines.
(10) The Class B systems significantly hamper the interoperability of locomotives and traction units but play an important role in maintaining the high level of safety of the trans-European network. For this reason, it is important to avoid creating additional obstacles to interoperability by, for example, altering these national legacy systems or by introducing new systems.
(11) To avoid creating additional obstacles to interoperability, Member States should ensure that the functionality of the legacy Class B systems and their interfaces remain as currently specified, except where modifications are needed to mitigate safety-related flaws in these systems. Member States should also ensure that systems not included in the list of Class B systems do not constitute additional barriers to interoperability.
(12) The availability of the GSM-R frequencies is essential for safe and interoperable railway operations.
(13) Decisions 2006/679/EC and 2006/860/EC should therefore be repealed.
(14) The measures provided for in this Decision are in accordance with the opinion of the Committee, referred to in Article 29(1) of Directive 2008/57/EC,
HAS ADOPTED THIS DECISION:

Article 1
1. The technical specification for interoperability (‘TSI’) relating to the ‘track-side control-command and signalling’ subsystem and ‘on-board control-command and signalling subsystems’ of the trans-European rail system, as set out in Annex III, is adopted.
2. The TSI set out in Annex III to this Decision shall apply to the track-side control-command and signalling subsystem as described in point 2.3 and to the on-board control-command and signalling subsystem as described in point 2.4 of Annex II to Directive 2008/57/EC.

Article 2
1. Member States shall ensure that, whenever a national protection control-command system is requested on board rolling stock to run on a given line or part of the trans-European network, this system is included in the list of Class B systems, having equal legal value as annexes to the TSI.
2. Member States shall ensure that the functionality, performance and interfaces of the Class B systems remain as currently specified, except where modifications are needed to mitigate safety-related flaws in those systems.

Article 3
Each Member State shall notify to the other Member States and to the Commission, with regard to Class B systems and to those issues identified as open points in Appendix G to the TSI adopted by this Decision, within 6 months of the notification of this Decision, the following:
(a)
the list of applicable technical rules;
(b)
the conformity assessment and checking procedures to be used for ensuring that the applicable technical rules are indeed applied;
(c)
the bodies it appoints for carrying out those conformity-assessment and checking procedures.
If these elements have already been notified in the context of Decisions 2006/679/EC and 2006/860/EC this obligation is considered fulfilled.

Article 4
1. The Commission may grant a derogation to the obligation laid down in Section 7.3.2.4 of Annex III concerning the mandatory equipment of lines with the European Train Control System (ETCS) in the context of EU funded projects (Section 7.3.2.4), when signalling is renewed on short (less than 150 km) and discontinuous sections of a line and provided that ETCS is installed before the earlier of these two dates:
—
5 years after the end of the project,
—
the time by which the section of the line is connected to another ETCS equipped line.
2. The Member State concerned shall forward a file concerning the project to the Commission. This file shall contain an economic analysis showing that there is a substantial economic and/or technical advantage in putting ERTMS into service at the earlier of the two dates mentioned in paragraph 1 rather than during the course of the EU-funded project.
3. The Commission shall examine the file sent to it and the measures proposed by the Member State and shall notify the results of its examination to the Committee referred to in Article 29 of Directive 2008/57/EC. If a derogation is granted, the Member State shall ensure that ERTMS is installed before the earlier of the two dates mentioned in paragraph 1.

Article 5
Commission Decision 2011/291/EU of 26 April 2011 concerning a technical specification for interoperability relating to the rolling stock sub-system – ‘Locomotives and Passenger rolling stock’ of the trans-European conventional rail system(5)is amended as follows:
(1)
the second indent under the headline ‘Legislative measures in force’ in Section 1.4 ‘Referenced documents’ of the Annex is replaced by ‘Control-Command and Signalling TSI’;
(2)
Section 4.2.3.3.1 is replaced by Annex I to this Decision;
(3)
Table 10 in Section 4.3.4 is replaced by Annex II to this Decision.

Article 6
The ERA technical document ERTMS/ETCS System Requirement Specification (SRS), document reference ‘subset-026’ in version 3.2.0, dated 22 December 2010, can be used as a basis to tender the equipment of lines with ETCS and to carry out tests, but before the entry into force of the so-called baseline 3, the fitment of trains with baseline 3 cannot be requested.

Article 7
Decisions 2006/679/EC and 2006/860/EC are hereby repealed. Their provisions shall however continue to apply in relation to maintenance of projects authorised in accordance with the TSIs annexed to those Decisions and, unless the applicant requests to apply this Decision, to projects for new, renewed or upgraded subsystems which are at an advanced stage of development or the subject of a contract in course of performance at the date of notification of the present Decision.

Article 8
This Decision shall apply 6 months after its notification to the Member States.

Article 9
This Decision is addressed to the Member States.

THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Directive 2008/57/EC of the European Parliament and of the Council of 17 June 2008 on the interoperability of the rail system within the Community(1), and in particular the second subparagraph of Article 6(1) thereof,
(1) Commission Decision 2006/679/EC of 28 March 2006 concerning the technical specification for interoperability relating to the control-command and signalling subsystem of the trans-European conventional rail system(2)laid down the technical specifications for interoperability (‘TSI’) relating to the control-command and signalling subsystem of the trans-European conventional rail system.
(2) Commission Decision 2006/860/EC of 7 November 2006 concerning a technical specification for interoperability relating to the control-command and signalling subsystem of the trans-European high speed rail system(3)lays down the TSI relating to the control-command and signalling subsystem of the trans-European high-speed rail system.
(3) The essential requirements for both the conventional and the high-speed networks must be identical, as must their functional and technical specifications, their interoperability constituents and interfaces, and the procedures for assessing the conformity or the suitability for use of the interoperability constituents or the ‘EC’ verification of their control-command and signalling subsystems.
(4) The implementation strategies should remain specific to each type of network and the existing requirements for the conventional trans-European network and for the high-speed trans-European network should remain unchanged. The European railway agency (‘Agency’) was given a framework mandate to perform certain activities.
(5) On 31 January 2011 the Agency gave its recommendation on the technical specification for interoperability relating to the subsystems ‘control-command and signalling’ of the trans-European rail system(4). This Decision is based on that recommendation.
(6) In the interest of clarity, Decisions 2006/679/EC and 2006/860/EC should therefore be replaced by this Decision.
(7) The changes introduced regarding safety requirements (Section 4.2.1 of Annex III) are based on the analysis that the text in the CCS TSIs in force leaves room for interpretations. The introduced changes have no negative impact in the overall safety level.
(8) The fitting of ERTMS/ETCS should be mandatory in the case of new installations or upgrade of the train protection part of a CCS assembly for railway infrastructure projects benefiting from EU financial support. Such fitting should in principle be carried out in the frame of the EU funded project. In certain cases, it is however necessary to grant a derogation to this implementation rule. The scope of such derogation is limited to the implementation strategy of the ‘control-command and signalling TSI’.
(9) The Agency has listed in the technical document ‘List of CCS Class B systems’ the national legacy control-command and signalling systems (‘Class B systems’). Those systems may still be requested on board locomotives and traction units to run on certain lines.
(10) The Class B systems significantly hamper the interoperability of locomotives and traction units but play an important role in maintaining the high level of safety of the trans-European network. For this reason, it is important to avoid creating additional obstacles to interoperability by, for example, altering these national legacy systems or by introducing new systems.
(11) To avoid creating additional obstacles to interoperability, Member States should ensure that the functionality of the legacy Class B systems and their interfaces remain as currently specified, except where modifications are needed to mitigate safety-related flaws in these systems. Member States should also ensure that systems not included in the list of Class B systems do not constitute additional barriers to interoperability.
(12) The availability of the GSM-R frequencies is essential for safe and interoperable railway operations.
(13) Decisions 2006/679/EC and 2006/860/EC should therefore be repealed.
(14) The measures provided for in this Decision are in accordance with the opinion of the Committee, referred to in Article 29(1) of Directive 2008/57/EC,
HAS ADOPTED THIS DECISION:
1. The technical specification for interoperability (‘TSI’) relating to the ‘track-side control-command and signalling’ subsystem and ‘on-board control-command and signalling subsystems’ of the trans-European rail system, as set out in Annex III, is adopted.
2. The TSI set out in Annex III to this Decision shall apply to the track-side control-command and signalling subsystem as described in point 2.3 and to the on-board control-command and signalling subsystem as described in point 2.4 of Annex II to Directive 2008/57/EC.
1. Member States shall ensure that, whenever a national protection control-command system is requested on board rolling stock to run on a given line or part of the trans-European network, this system is included in the list of Class B systems, having equal legal value as annexes to the TSI.
2. Member States shall ensure that the functionality, performance and interfaces of the Class B systems remain as currently specified, except where modifications are needed to mitigate safety-related flaws in those systems.
Each Member State shall notify to the other Member States and to the Commission, with regard to Class B systems and to those issues identified as open points in Appendix G to the TSI adopted by this Decision, within 6 months of the notification of this Decision, the following:
(a)
the list of applicable technical rules;
(b)
the conformity assessment and checking procedures to be used for ensuring that the applicable technical rules are indeed applied;
(c)
the bodies it appoints for carrying out those conformity-assessment and checking procedures.
If these elements have already been notified in the context of Decisions 2006/679/EC and 2006/860/EC this obligation is considered fulfilled.
1. The Commission may grant a derogation to the obligation laid down in Section 7.3.2.4 of Annex III concerning the mandatory equipment of lines with the European Train Control System (ETCS) in the context of EU funded projects (Section 7.3.2.4), when signalling is renewed on short (less than 150 km) and discontinuous sections of a line and provided that ETCS is installed before the earlier of these two dates:
—
5 years after the end of the project,
—
the time by which the section of the line is connected to another ETCS equipped line.
2. The Member State concerned shall forward a file concerning the project to the Commission. This file shall contain an economic analysis showing that there is a substantial economic and/or technical advantage in putting ERTMS into service at the earlier of the two dates mentioned in paragraph 1 rather than during the course of the EU-funded project.
3. The Commission shall examine the file sent to it and the measures proposed by the Member State and shall notify the results of its examination to the Committee referred to in Article 29 of Directive 2008/57/EC. If a derogation is granted, the Member State shall ensure that ERTMS is installed before the earlier of the two dates mentioned in paragraph 1.
Commission Decision 2011/291/EU of 26 April 2011 concerning a technical specification for interoperability relating to the rolling stock sub-system – ‘Locomotives and Passenger rolling stock’ of the trans-European conventional rail system(5)is amended as follows:
(1)
the second indent under the headline ‘Legislative measures in force’ in Section 1.4 ‘Referenced documents’ of the Annex is replaced by ‘Control-Command and Signalling TSI’;
(2)
Section 4.2.3.3.1 is replaced by Annex I to this Decision;
(3)
Table 10 in Section 4.3.4 is replaced by Annex II to this Decision.
The ERA technical document ERTMS/ETCS System Requirement Specification (SRS), document reference ‘subset-026’ in version 3.2.0, dated 22 December 2010, can be used as a basis to tender the equipment of lines with ETCS and to carry out tests, but before the entry into force of the so-called baseline 3, the fitment of trains with baseline 3 cannot be requested.
Decisions 2006/679/EC and 2006/860/EC are hereby repealed. Their provisions shall however continue to apply in relation to maintenance of projects authorised in accordance with the TSIs annexed to those Decisions and, unless the applicant requests to apply this Decision, to projects for new, renewed or upgraded subsystems which are at an advanced stage of development or the subject of a contract in course of performance at the date of notification of the present Decision.
This Decision shall apply 6 months after its notification to the Member States.
This Decision is addressed to the Member States.
ANNEX I
‘4.2.3.3.1. Rolling Stock characteristics for the compatibility with train detection systems
The set of rolling stock characteristics for compatibility with train detection target systems are given in clauses 4.2.3.3.1.1, 4.2.3.3.1.2 and 4.2.3.3.1.3. Reference is made to clauses of the specification referenced in Annex A, Index 77 of CCS TSI’
The set of characteristics the rolling stock is compatible with shall be recorded in the rolling stock register as defined in clause 4.8 of this TSI.
4.2.3.3.1.1. ROLLING STOCK CHARACTERISTICS FOR COMPATIBILITY WITH TRAIN DETECTION SYSTEM BASED ON TRACK CIRCUITS
—
Vehicle geometry
—
The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance ai in Figure 1).
—
The maximum distance between buffer end and first axle is specified in the specification referenced in clause 3.1.2 of Annex A, Index 77 of CCS TSI (distance b1 in Figure 1).
—
Vehicle design
—
The minimum axle load in all load conditions is specified in the specification referenced in clause 3.1.7 of Annex A, Index 77 of CCS TSI.
—
The electrical resistance between the running surfaces of the opposite wheels of a wheelset is specified in the specification referenced in clause 3.1.9 of Annex A, Index 77 of CCS TSI and the method to measure is specified in the same clause.
—
For electric units equipped with a pantograph, the minimum impedance between pantograph and each wheel of the train is an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI.
—
Isolating emissions
—
The limitations of use of sanding equipment are given in the specification referenced in clause 3.1.4 of Annex A, Index 77 of CCS TSI.
—
The limitations of use of composite brake blocks are given in the specification referenced in clause 3.1.6 of Annex A, Index 77 of CCS TSI.
—
EMC
—
The requirements related to electromagnetic compatibility are open points in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI.
—
The electromagnetic interference limit levels rising from traction currents are an open point in the specification referenced in clause 3.2.2 of Annex A, Index 77 of CCS TSI.
4.2.3.3.1.2. ROLLING STOCK CHARACTERISTICS FOR COMPATIBILITY WITH TRAIN DETECTION SYSTEM BASED ON AXLE COUNTERS
—
Vehicle geometry
—
The maximum distance between two consecutive axles is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
—
The minimum distance between two consecutive axles of the train is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
—
At the end of a unit intended to be coupled, the minimum distance between end and first axle of the unit is half of the value specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
—
The maximum distance between end and first axle is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI (distance b1 in Figure 1).
—
The minimum distance between end axles of a unit is specified in the specification referenced in clause 3.1.2, Annex A, Index 77 of CCS TSI.
—
Wheel geometry
—
Wheel geometry is specified in the clause 4.2.3.5.2.2 of the present TSI.
—
The minimum wheel diameter (speed dependant) is specified in the specification referenced in clause 3.1.3, Annex A, Index 77 of CCS TSI.
—
Vehicle design
—
The metal-free space around wheels is an open point in the specification referenced in clause 3.1.3.5, Annex A, Index 77 of CCS TSI.
—
The characteristics of the wheel material regarding magnetic field is specified in the specification referenced in clause 3.1.3.6, Annex A, Index 77 of CCS TSI.
—
EMC
—
The requirements related to electromagnetic compatibility are specified in the specification referenced in clauses 3.2.1 and 3.2.2 of Annex A, Index 77 of CCS TSI.
—
The electromagnetic interference limit levels rising from the use of eddy current or magnetic track brakes are an open point in the specification referenced in clause 3.2.3 of Annex A, Index 77 of CCS TSI.
4.2.3.3.1.3. ROLLING STOCK CHARACTERISTICS FOR COMPATIBILITY WITH LOOP EQUIPMENT
—
Vehicle design
The metal-mass of vehicles is an open point in the specification referenced in clause 3.1.7.2 of Annex A, Index 77 of CCS TSI.’
ANNEX II
‘Table 10
Interface with the control-command and signalling subsystem
Reference Conventional Rail LOC & PAS TSI

Reference Rail CCS TSI

Parameter
Clause
Parameter
Clause
Rolling stock characteristics compatible with train detection system based on track circuits
4.2.3.3.1.1
Vehicle geometry
Vehicle design
Isolating emissions
EMC
Specification referenced in Annex A, Index 77 of CCS TSI
Rolling stock characteristics compatible with train detection system based on axle counters
4.2.3.3.1.2
Vehicle geometry
Wheel geometry
Vehicle design
EMC
Specification referenced in Annex A, Index 77 of CCS TSI
Rolling stock characteristics compatible with loop equipment
4.2.3.3.1.3
Vehicle design
Specification referenced in Annex A, Index 77 of CCS TSI
Emergency braking command
4.2.4.4.1
On-board ETCS functionality
4.2.2
Emergency braking performance
4.2.4.5.2
Guaranteed train braking performance and characteristics
4.2.2
External visibility
4.2.9.1.3
Visibility of track-side control-command objects
4.2.15’

1.   INTRODUCTION

ANNEX III
TABLE OF CONTENTS

1. | Introduction | 11
1.1. | Technical scope | 11
1.2. | Geographical scope | 11
1.3. | Content of this TSI | 11
2. | Subsystem definition and scope | 11
2.1. | Introduction | 11
2.2. | Scope | 11
2.3. | Application Levels (ERTMS/ETCS) | 12
3. | The Essential Requirements for the Control-Command and Signalling Subsystems | 12
3.1. | General | 12
3.2. | Specific Aspects of the Control-Command and Signalling Subsystems | 13
3.2.1. | Safety | 13
3.2.2. | Reliability and Availability | 13
3.2.3. | Health | 13
3.2.4. | Environmental Protection | 13
3.2.5. | Technical Compatibility | 13
3.2.5.1. | Engineering Compatibility | 14
3.2.5.1.1. | Physical environmental conditions | 14
3.2.5.1.2. | Railway Internal Electromagnetic Compatibility | 14
3.2.5.2. | Control-Command and Signalling Compatibility | 14
4. | Characterisation of the Subsystems | 14
4.1. | Introduction | 14
4.2. | Functional and technical specifications of the Subsystems | 15
4.2.1. | Control-Command and Signalling safety characteristics relevant to interoperability | 15
4.2.1.1. | Safety | 16
4.2.1.2. | Availability/Reliability | 16
4.2.2. | On-board ERTMS/ETCS functionality | 16
4.2.3. | Track-side ERTMS/ETCS functionality | 17
4.2.4. | Mobile communication functions for railways GSM-R | 18
4.2.4.1. | Basic communication function | 18
4.2.4.2. | Voice and operational communication applications | 18
4.2.4.3. | Data communication applications for ETCS | 18
4.2.5. | ERTMS/ETCS and GSM-R air gap interfaces | 19
4.2.5.1. | Radio communications with the train | 19
4.2.5.2. | Eurobalise communication with the train | 19
4.2.5.3. | Euroloop communication with the train | 19
4.2.6. | On-Board Interfaces Internal to Control-Command and Signalling | 19
4.2.6.1. | ERTMS/ETCS and Class B train protection | 19
4.2.6.2. | Interface between GSM-R Radio Data Communication and ERTMS/ETCS | 19
4.2.6.3. | Odometry | 20
4.2.7. | Track-side Interfaces Internal to Control-Command and Signalling | 20
4.2.7.1. | Functional interface between RBCs | 20
4.2.7.2. | RBC/RBC | 20
4.2.7.3. | GSM-R/track-side ETCS | 20
4.2.7.4. | Eurobalise/LEU | 20
4.2.7.5. | Euroloop/LEU | 20
4.2.8. | Key Management | 20
4.2.9. | ETCS-ID Management | 20
4.2.10. | Track-side Train Detection Systems | 20
4.2.11. | Electromagnetic Compatibility between Rolling Stock and Control-Command and Signalling track-side equipment | 21
4.2.12. | ERTMS/ETCS DMI (Driver Machine Interface) | 21
4.2.13. | GSM-R DMI (Driver-Machine Interface) | 21
4.2.14. | Interface to Data Recording for Regulatory Purposes | 21
4.2.15. | Visibility of track-side Control-Command and Signalling objects | 21
4.2.16. | Environmental conditions | 21
4.3. | Functional and technical specifications of the interfaces to other Subsystems | 22
4.3.1. | Interface to the Traffic Operation and Management Subsystem | 22
4.3.2. | Interface to the Rolling Stock Subsystem | 22
4.3.3. | Interfaces to Infrastructure Subsystem | 24
4.3.4. | Interfaces to Energy Subsystem | 25
4.4. | Operating rules | 25
4.5. | Maintenance rules | 25
4.5.1. | Responsibility of the manufacturer of equipment | 25
4.5.2. | Responsibility of the applicant for subsystem verification | 26
4.6. | Professional competences | 26
4.7. | Health and safety conditions | 26
4.8. | Registers | 26
5. | Interoperability Constituents | 26
5.1. | Definition | 26
5.2. | List of interoperability constituents | 26
5.2.1. | Basic interoperability constituents | 26
5.2.2. | Grouping of interoperability constituents | 26
5.3. | Constituents’ performance and specifications | 27
6. | Assessing the conformity and/or suitability for use of the constituents and verifying the subsystems | 31
6.1. | Introduction | 31
6.1.1. | General principles | 31
6.1.2. | Principles for testing ERTMS/ETCS and GSM-R | 31
6.2. | Interoperability constituents | 32
6.2.1. | Assessment procedures for Control-Command and Signalling Interoperability Constituents | 32
6.2.2. | Modules for Control-Command and Signalling Interoperability Constituents | 32
6.2.3. | Assessment requirements | 33
6.2.4. | Special issues | 34
6.2.4.1. | The on-board ERTMS/ETCS | 34
6.2.4.2. | The Specific Transmission Module (STM) | 35
6.2.4.3. | Content of the ‘EC’ Declaration of conformity | 35
6.3. | Control-Command and Signalling Subsystems | 35
6.3.1. | Assessment procedures for Control-Command and Signalling Subsystems | 35
6.3.2. | Modules for Control-Command and Signalling Subsystems | 35
6.3.2.1. | On-board Subsystem | 35
6.3.2.2. | Track-side Subsystem | 35
6.3.2.3. | Conditions for using modules for On-board and Track-side Subsystems | 36
6.3.3. | Assessment requirements for an On-board Subsystem | 36
6.3.4. | Assessment requirements for a Track-side Subsystem | 38
6.4. | Provisions for partial conformity | 41
6.4.1. | Introduction | 41
6.4.2. | Assessment of parts of Control-Command and Signalling Subsystems | 41
6.4.3. | Partial conformity of Control-Command and Signalling Subsystems due to restricted conditions of use of its interoperability constituent(s) | 41
7. | Implementing the TSI Control-Command and Signalling | 42
7.1. | Introduction | 42
7.2. | Generally applicable rules | 42
7.2.1. | Upgrading or renewing the Control-Command Track-side Subsystem or parts of it | 42
7.2.2. | Legacy systems | 42
7.2.3. | Availability of Specific Transmission Modules | 42
7.2.4. | Additional Class B equipment on a line equipped with Class A | 42
7.2.5. | Rolling stock with Class A and Class B equipment | 43
7.2.6. | Conditions for mandatory and optional functions | 43
7.2.7. | GSM-R specific implementation rules | 43
7.2.7.1. | Track-side installations: | 43
7.2.7.2. | On-board installations: | 43
7.2.8. | Train detection systems specific implementation rules | 44
7.2.9. | Specific cases | 44
7.2.9.1. | Introduction | 44
7.2.9.2. | Belgium | 44
7.2.9.3. | United Kingdom | 45
7.2.9.4. | France | 45
7.2.9.5. | Poland | 46
7.2.9.6. | Lithuania, Latvia | 46
7.2.9.7. | Sweden | 47
7.2.9.8. | Luxembourg | 47
7.3. | Rules for ERTMS | 47
7.3.1. | The ERTMS European Deployment Plan | 47
7.3.2. | ERTMS Track-side Implementation | 47
7.3.2.1. | Corridors | 47
7.3.2.2. | Connection to the main European ports, marshalling yards, freight terminals and freight transport areas | 48
7.3.2.3. | High-speed network | 48
7.3.2.4. | EU-funded projects | 48
7.3.2.5. | Notification | 48
7.3.2.6. | Delays | 48
7.3.3. | ERTMS – On-board implementation | 49
7.3.3.1. | High-speed network | 49
7.3.4. | Specific lines constituting the corridors | 50
7.3.5. | Main European ports, marshalling yards, freight terminals and freight transport areas | 561.1. Technical scope
This TSI concerns the Control-Command and Signalling On-board Subsystem and the Control-Command and Signalling Track-side Subsystem.
1.2. Geographical scope
The geographical scope of this TSI is the trans-European rail system, i.e. the trans-European conventional and high-speed rail systems as set out in points 1 and 2 of Annex I to Directive 2008/57/EC (Railway Interoperability Directive).
1.3. Content of this TSI
In accordance with Article 5(3) of the Railway Interoperability Directive, this TSI:

1. | indicates its intended scope — Chapter 2 (Subsystem Definition and Scope);
2. | lays down essential requirements for the Control-Command and Signalling Subsystems and their interfaces vis-à-vis other subsystems — Chapter 3 (The Essential Requirements of the Control-Command and Signalling Subsystems);
3. | lays down the functional and technical specifications to be met by the Subsystems and their interfaces with other subsystems — Chapter 4 (Characterisation of the Subsystem);
4. | determines the interoperability constituents and interfaces which must be covered by European specifications, including European standards, and which are necessary to achieve interoperability within the trans-European rail system — Chapter 5 (Interoperability Constituents);
5. | states, in each case under consideration, which procedures are to be used to assess the conformity or the suitability for use of the interoperability constituents and for the ‘EC’ verification of the subsystems — Chapter 6 (Assessing the Conformity and/or Suitability For Use of the Constituents and Verifying the Subsystems);
6. | indicates the strategy for implementing this TSI — Chapter 7 (Implementing the Control-Command and Signalling Subsystems TSI);
7. | indicates the professional competences and health and safety conditions at work required for the staff operating and maintaining these subsystems and implementing the TSI — Chapter 4 (Characterisation of the Subsystem).In accordance with Article 5(5) of the Railway Interoperability Directive, provisions for specific cases are indicated in Chapter 7 (Implementing the Control-Command and Signalling Subsystems TSI).
This TSI also sets out, in Chapter 4 (Characterisation of the Subsystems), the operating and maintenance rules which specifically apply to the scope indicated in paragraphs 1.1 and 1.2 above.
2. SUBSYSTEM DEFINITION AND SCOPE2.1. Introduction
The Control-Command and Signalling Subsystems are defined in Annex II to the Railway Interoperability Directive as ‘all the equipment required to ensure safety and to command and control movements of trains authorised to travel on the network’.
The features of the Control-Command and Signalling Subsystems are:

1. | the functions that are essential for the safe control of railway traffic, and that are essential for its operation, including those required for degraded modes(1);
2. | the interfaces;
3. | the level of performance required to meet the essential requirements.2.2. Scope
The Control-Command and Signalling Subsystems TSI specifies only those requirements which are necessary to assure the interoperability of the trans-European rail system and compliance with the essential requirements.
The Control-Command and Signalling Subsystems include the following parts:

1. | train protection;
2. | radio communication;
3. | train detection.The Class A train protection system is ERTMS/ETCS whilst the Class A radio system is GSM-R.
For Class A train detection this TSI specifies only the requirements for the interface with other subsystems.
Class B systems are a limited set of train protection legacy control-command and signalling systems that were in use before 20 April 2001. The list of Class B systems is established in the European Railway Agency technical document ‘List of CCS Class B systems’, ERA/TD/2011-11, version 1.0.
The requirements for the Control-Command and Signalling On-board Subsystem are specified in relation to Class A radio mobiles and train protection.
The requirements for the Control-Command and Signalling Track-side Subsystem are specified in relation to:

1. | the Class A radio network;
2. | Class A train protection;
3. | the interface requirements for train detection systems, to ensure their compatibility with rolling stock.2.3. Application levels (ERTMS/ETCS)
The interfaces specified by this TSI define the means of data transmission to, and (where appropriate) from trains. The ERTMS/ETCS specifications referenced by this TSI provide application levels from which a track-side implementation may choose the means of transmission that meet its requirements.
This TSI defines the requirements for all application levels.
A train equipped with Class A on-board train protection for a given application level must be able to operate on that level and any lower one. As a consequence:

— | a train equipped with Class A on-board train protection for level 2 must be able to operate on that level and on level 1 lines,
— | a train equipped with Class A on-board train protection for level 1 need not be equipped with a GSM-R data radio but must already implement all level 2 functions so as to ensure that the mere connection of a GSM-R data radio at a later stage will ensure it is equipped for level 2.3. THE ESSENTIAL REQUIREMENTS FOR THE CONTROL-COMMAND AND SIGNALLING SUBSYSTEMS3.1. General
The Railway Interoperability Directive requires that the subsystems and the interoperability constituents including interfaces meet the essential requirements set out in general terms in Annex III to the Directive.
The essential requirements are:

1. | Safety;
2. | Reliability and Availability;
3. | Health;
4. | Environmental Protection;
5. | Technical compatibility.The essential requirements for Class A systems are described below.
The requirements for Class B systems are the responsibility of the relevant Member State.
3.2. Specific Aspects of the Control-Command and Signalling Subsystems
3.2.1. Safety
Every project to which this specification is applied shall take the measures necessary to ensure that the level of risk of an incident occurring within the scope of the Control-Command and Signalling Subsystems, is not higher than the objective for the service. For this purpose Commission Regulation (EC) No 352/2009 of 24 April 2009 on the adoption of a common safety method on risk evaluation and assessment as referred to in Article 6(3)(a) of Directive 2004/49/EC of the European Parliament and of the Council(2)(Common Safety Method) applies.
To ensure that the measures taken to achieve safety do not jeopardise interoperability, the requirements of the basic parameter defined in Section 4.2.1 (Control-Command and Signalling safety characteristics relevant to interoperability) shall be respected.
For the ERTMS/ETCS Class A system the safety objective is apportioned between the Control-Command and Signalling On-board and Track-side Subsystems. The detailed requirements are specified in the basic parameter defined in Section 4.2.1 (Control-Command and Signalling safety characteristics relevant to interoperability). This safety requirement must be met together with the availability requirements as defined in Section 3.2.2 (Reliability and Availability).
3.2.2. Reliability and Availability
For the Class A system, the reliability and availability objectives are apportioned between the Control-Command and Signalling On-board and Track-side Subsystems. The detailed requirements are specified in the basic parameter defined in Section 4.2.1 (Control-Command and Signalling safety characteristics relevant to interoperability).
The level of risk shall be monitored as constituents of the subsystem age and wear. The requirements for maintenance stated in Section 4.5 shall be respected.
3.2.3. Health
In accordance with EU regulations and with national regulations that are compatible with the European legislation, care shall be taken to ensure that the materials used in and the design of the Control-Command and Signalling Subsystems do not constitute a health hazard to persons having access to them.
3.2.4. Environmental Protection
In accordance with EU regulations and with national regulations that are compatible with European legislation:

1. | the Control-Command and Signalling equipment, if subjected to excessive heat or fire, shall not exceed limits for the emission of fumes or gases which are harmful to the environment;
2. | the Control-Command and Signalling equipment shall not contain substances which may abnormally contaminate the environment during their normal use;
3. | the Control-Command and Signalling equipment shall be subject to the European legislation in force controlling the limits to the emission of and the susceptibility to electromagnetic interference along the boundaries of railway property;
4. | the Control-Command and Signalling equipment shall comply with existing regulations on noise pollution;
5. | the Control-Command and Signalling equipment shall not give rise to any inadmissible level of vibration which could jeopardise the integrity of the infrastructure (when the infrastructure is in the correct state of maintenance).3.2.5. Technical Compatibility
Technical compatibility includes the functions, interfaces and performances required to achieve interoperability.
The requirements of technical compatibility are subdivided in the following three categories:

1. | The first category sets out the general engineering requirements for interoperability namely environmental conditions, internal electromagnetic compatibility (EMC) within the railway boundaries, and installation. These compatibility requirements are defined in this chapter.
2. | The second category describes how the Control-Command and Signalling Subsystems have to be applied technically and what functions they have to perform to ensure interoperability. This category is defined in Chapter 4.
3. | The third category describes how the Control-Command and Signalling Subsystems have to be operated in order that interoperability is achieved. This category is defined in Chapter 4.3.2.5.1. Engineering Compatibility
3.2.5.1.1. Physical environmental conditions
Control-Command and Signalling equipment shall be capable of operating under the climatic and physical conditions which characterise the area in which the relevant part of the trans-European rail system is located.
The requirements of basic parameter 4.2.16 (Environmental conditions) shall be respected.
3.2.5.1.2. Railway Internal Electromagnetic Compatibility
In accordance with EU regulations and with national regulations that are compatible with the European legislation, the Control-Command and Signalling equipment shall neither interfere with nor be interfered with by other control-command and signalling equipment or other subsystems.
The basic parameter related for electromagnetic compatibility between rolling stock and control-command and signalling track-side equipment is described in Section 4.2.11 (Electromagnetic Compatibility).
3.2.5.2. Control-Command and Signalling Compatibility.
Chapter 4 defines the requirements for the interoperability of the Control-Command and Signalling Subsystems.
In addition, where the Control-Command and Signalling Subsystems are concerned, this TSI ensures technical interoperability between trans-European high-speed rail and conventional rail systems when both are fitted with Class A systems.
4. CHARACTERISATION OF THE SUBSYSTEMS4.1. Introduction
In accordance with the relevant essential requirements, the Control-Command and Signalling Subsystems are characterised by the following basic parameters:

1. | Control-Command and Signalling safety characteristics relevant to interoperability (Section 4.2.1)
2. | On-board ERTMS/ETCS functionality (Section 4.2.2)
3. | Track-side ERTMS/ETCS functionality (Section 4.2.3)
4. | Mobile communication functions for railways – GSM-R (Section 4.2.4)
5. | ERTMS/ETCS and GSM-R air gap interfaces (Section 4.2.5)
6. | On-board interfaces Internal to Control-Command and Signalling (Section 4.2.6)
7. | Track-side interfaces Internal to Control-Command and Signalling (Section 4.2.7)
8. | Key management (Section 4.2.8)
9. | ETCS-ID management (Section 4.2.9)
10. | Train detection systems (Section 4.2.10)
11. | Electromagnetic compatibility between rolling stock and Control-Command and Signalling track-side equipment (Section 4.2.11)
12. | ERTMS/ETCS DMI (driver machine interface) (Section 4.2.12)
13. | GSM-R DMI (driver machine interface) (Section 4.2.13)
14. | Interface to data recording for regulatory purposes (Section 4.2.14)
15. | Visibility of track-side Control-Command and Signalling objects (Section 4.2.15)
16. | Environmental conditions (Sections 4.2.16)All requirements in Section 4.2 (Functional and technical specifications of the Subsystems) to meeting these basic parameters shall be applied to the Class A system.
Requirements for Class B systems and for STMs (which enable the Class A On-board system to operate on Class B infrastructure) are the responsibility of the appropriate Member State.
This TSI is based on the principles of enabling the Control-Command and Signalling Track-side Subsystem to be compatible with TSI compliant Control-Command and Signalling On-board Subsystems. To achieve this goal:

1. | functions, interfaces and performances of the Control-Command and Signalling On-board Subsystem are standardised, ensuring that every train will react in a predictable way to data received from track-side;
2. | for the Control-Command and Signalling Track-side Subsystem, track-to-train and train-to-track communication are fully standardised in this TSI. The specifications referenced in the sections below allow Control-Command and Signalling track-side functionality to be applied in a flexible way, so that it can be optimally integrated into the railway system. This flexibility shall be exploited without limiting the movement of TSI-compliant on-board subsystems.The Control-Command and Signalling functions are classified in categories indicating whether they are optional (O) or mandatory (M). The categories are defined in Annex A 4.1a for ERTMS/ETCS and Annex A 4.1b for GSM-R and these texts also state how the functions are classified.
Annex A 4.1c provides the Glossary of ERTMS/ETCS terms and definitions, which are used in the specifications referred to in Annex A.
According to Section 2.2 (Scope) the Control-Command and Signalling Subsystems include three parts.
The following table indicates which basic parameters are relevant for each subsystem and for each part.

Subsystem | Part | Basic parameters
Control-Command and Signalling On-board | train protection | 4.2.1, 4.2.2, 4.2.5, 4.2.6, 4.2.8, 4.2.9, 4.2.12, 4.2.14, 4.2.16
radio communication | 4.2.4, 4.2.5, 4.2.6, 4.2.13, 4.2.14, 4.2.16
Control-Command and Signalling Track-side | train protection | 4.2.3, 4.2.5, 4.2.7, 4.2.8, 4.2.9, 4.2.15, 4.2.16
radio communication | 4.2.4, 4.2.5, 4.2.7, 4.2.16
train detection | 4.2.10, 4.2.11, 4.2.16With respect to the essential requirements set out in Chapter 3, the functional and technical specifications of the Control-Command and Signalling Subsystems are as follows.
4.2. Functional and technical specifications of the Subsystems
4.2.1. Control-Command and Signalling safety characteristics relevant to interoperability
This basic parameter describes the requirements for the Control-Command and Signalling On-board Subsystem and Track-side subsystem with reference to Section 3.2.1 (Safety) and Section 3.2.2 (Availability and Reliability).
In order to achieve interoperability, when implementing Control-Command and Signalling On-board and Track-side subsystems the following provisions shall be respected:

1. | The design, implementation and use of a Control-Command and Signalling On-board or Track-side subsystem shall not export any requirements:(a)across the interface between Control-Command and Signalling On-board and Track-side subsystems in addition to the requirements specified in this TSI;(b)to any other subsystem in addition to the requirements specified in the corresponding TSIs. | (a) | across the interface between Control-Command and Signalling On-board and Track-side subsystems in addition to the requirements specified in this TSI; | (b) | to any other subsystem in addition to the requirements specified in the corresponding TSIs.
(a) | across the interface between Control-Command and Signalling On-board and Track-side subsystems in addition to the requirements specified in this TSI;
(b) | to any other subsystem in addition to the requirements specified in the corresponding TSIs.
2. | The requirements set out in Sections 4.2.1.1 and 4.2.1.2 below shall be respected.4.2.1.1. Safety
The Control-Command and Signalling On-board and Track-side subsystems shall respect the requirements for ERTMS/ETCS equipment and installations stated in this TSI.
For the hazard ‘exceeding speed and/or distance limits advised to ERTMS/ETCS’ the tolerable rate (THR) is 10– 9h– 1for random failures, for on-board ERTMS/ETCS and for track-side ERTMS/ETCS. See Annex A 4.2.1.a.
To achieve interoperability, the on-board ERTMS/ETCS shall fully respect all requirements specified in Annex A 4.2.1. Nevertheless, less stringent safety requirements are acceptable for track-side ERTMS/ETCS provided that, in combination with TSI-compliant Control-Command and Signalling On-board subsystems, the safety level for the service is met.
Requirements for hazards related to errors at the interface between driver and on-board ERTMS/ETCS are an open point.
4.2.1.2. Availability/Reliability
The Control-Command and Signalling On-board and Track-side subsystems shall respect the requirements stated in this TSI. The availability/reliability requirements are defined in Annex A 4.2.1.b.
The level of risk shall be controlled during the life of the assemblies. The requirements for maintenance stated in Section 4.5 (Maintenance rules) shall be respected.
4.2.2. On-board ERTMS/ETCS functionality
The basic parameter for ERTMS/ETCS on-board functionality describes all of the functions needed to run a train in a safe way. The primary function is to provide automatic train protection and cab signalling:

1. | setting the train characteristics (e.g. maximum train speed, braking performance);
2. | selecting the supervision mode on the basis of information from track-side;
3. | performing odometry functions;
4. | locating the train in a coordinate system based on Eurobalise locations;
5. | calculating the dynamic speed profile for its mission on the basis of train characteristics and of information from track-side;
6. | supervising the dynamic speed profile during the mission;
7. | providing the intervention function.These functions shall be implemented in accordance with Annex A 4.2.2.b and their performance shall conform to Annex A 4.2.2.a.
The requirements for tests are specified in Annex A 4.2.2.c.
The ETCS identities of equipment shall be managed in accordance with Section 4.2.9 (ETCS-ID management).
The main functionality is supported by other functions, to which Annex A 4.2.2.a and Annex A 4.2.2.b also apply, together with the additional specifications indicated below:

1. | Communication with the Control-Command and Signalling Track-side Subsystem.(a)Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train);(b)Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train). This functionality is optional on-board unless Euroloop is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);(c)Radio data transmission for radio in-fill. See Annex A 4.2.2.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). This functionality is optional on-board unless radio data transmission for radio in-fill is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);(d)Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). Only mandatory on-board for ERTMS/ETCS Level 2 or ETCS Level 3 applications. | (a) | Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train); | (b) | Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train). This functionality is optional on-board unless Euroloop is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points); | (c) | Radio data transmission for radio in-fill. See Annex A 4.2.2.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). This functionality is optional on-board unless radio data transmission for radio in-fill is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points); | (d) | Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). Only mandatory on-board for ERTMS/ETCS Level 2 or ETCS Level 3 applications.
(a) | Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train);
(b) | Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train). This functionality is optional on-board unless Euroloop is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);
(c) | Radio data transmission for radio in-fill. See Annex A 4.2.2.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). This functionality is optional on-board unless radio data transmission for radio in-fill is installed track-side in ERTMS/ETCS Level 1 and the release speed is set to zero for safety reasons (e.g. protection of danger points);
(d) | Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.6.2 (Interface between GSM-R Radio Data Communication and ERTMS/ETCS) and Section 4.2.8 (Key Management). Only mandatory on-board for ERTMS/ETCS Level 2 or ETCS Level 3 applications.
2. | Communicating with the driver. See Annex A 4.2.2.e and Section 4.2.12 (ERTMS/ETCS DMI).
3. | Communicating with the STM. See Section 4.2.6.1 (Interface between ERTMS/ETCS and STM). This function includes:(a)managing the STM output;(b)providing data to be used by the STM;(c)managing STM transitions. | (a) | managing the STM output; | (b) | providing data to be used by the STM; | (c) | managing STM transitions.
(a) | managing the STM output;
(b) | providing data to be used by the STM;
(c) | managing STM transitions.
4. | Managing information about the completeness of the train (train integrity) — mandatory for level 3, not required for level 1 or 2.
5. | Equipment health monitoring and degraded mode support. This function includes:(a)initialising the on-board ERTMS/ETCS functionality;(b)providing degraded mode support;(c)isolating the on-board ERTMS/ETCS functionality. | (a) | initialising the on-board ERTMS/ETCS functionality; | (b) | providing degraded mode support; | (c) | isolating the on-board ERTMS/ETCS functionality.
(a) | initialising the on-board ERTMS/ETCS functionality;
(b) | providing degraded mode support;
(c) | isolating the on-board ERTMS/ETCS functionality.
6. | Support data recording for regulatory purposes. See Section 4.2.14 (Interface to Data Recording for Regulatory Purposes).
7. | Forwarding information/orders and receiving state information from rolling stock:(a)to the DMI. See Section 4.2.12 (ERTMS/ETCS DMI);(b)to/from the train interface unit. See Annex A 4.2.2.f. | (a) | to the DMI. See Section 4.2.12 (ERTMS/ETCS DMI); | (b) | to/from the train interface unit. See Annex A 4.2.2.f.
(a) | to the DMI. See Section 4.2.12 (ERTMS/ETCS DMI);
(b) | to/from the train interface unit. See Annex A 4.2.2.f.4.2.3. Track-side ERTMS/ETCS functionality
This Basic parameter describes the ERTMS/ETCS track-side functionality. It contains all ERTMS/ETCS functionality to provide a safe path to a specific train.
The main functionality is:

1. | locating a specific train in a coordinate system based on Eurobalise locations (levels 2 and 3);
2. | translating the information from track-side signalling equipment into a standard format for the Control-Command and Signalling On-board Subsystem;
3. | sending movement authorities including track description and orders assigned to a specific train.These functions shall be implemented in accordance with Annex A 4.2.3.b and their performance shall conform to Annex A 4.2.3.a.
The requirements for tests are specified in Annex A 4.2.3.c.
The ETCS identities of equipment shall be managed in accordance with Section 4.2.9 (ETCS-ID management).
The main functionality is supported by other functions, to which Annex A 4.2.3.a and Annex A 4.2.3.b also apply, together with the additional specifications indicated below:

1. | Communicating with the Control-Command and Signalling On-board Subsystem. This includes:(a)Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train) and Section 4.2.7.4 (Eurobalise/Line-side Electronic Unit (LEU));(b)Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train) and Section 4.2.7.5 (Euroloop/LEU). Euroloop is only relevant in level 1, in which it is optional;(c)Radio data transmission for radio in-fill. See Annex A 4.2.3.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio in-fill is only relevant in level 1, in which it is optional;(d)Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio data transmission is only relevant to levels 2 and 3. | (a) | Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train) and Section 4.2.7.4 (Eurobalise/Line-side Electronic Unit (LEU)); | (b) | Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train) and Section 4.2.7.5 (Euroloop/LEU). Euroloop is only relevant in level 1, in which it is optional; | (c) | Radio data transmission for radio in-fill. See Annex A 4.2.3.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio in-fill is only relevant in level 1, in which it is optional; | (d) | Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio data transmission is only relevant to levels 2 and 3.
(a) | Eurobalise data transmission. See Section 4.2.5.2 (Eurobalise communication with the train) and Section 4.2.7.4 (Eurobalise/Line-side Electronic Unit (LEU));
(b) | Euroloop data transmission. See Section 4.2.5.3 (Euroloop communication with the train) and Section 4.2.7.5 (Euroloop/LEU). Euroloop is only relevant in level 1, in which it is optional;
(c) | Radio data transmission for radio in-fill. See Annex A 4.2.3.d, Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio in-fill is only relevant in level 1, in which it is optional;
(d) | Radio data transmission. See Section 4.2.5.1 (Radio communications with the train), Section 4.2.7.3 (GSM-R/track-side ETCS functionality) and Section 4.2.8 (Key Management). Radio data transmission is only relevant to levels 2 and 3.
2. | Generating information/orders to the on-board ERTMS/ETCS, e.g. information related to closing/opening the air flaps, lowering/raising the pantograph, opening/closing the main power switch, changing from traction system A to traction system B. Implementation of this functionality is optional for track-side.
3. | Managing the transitions between areas supervised by different Radio Block Centres (RBCs) (only relevant for levels 2 and 3). See Section 4.2.7.1 (Functional interface between RBCs) and Section 4.2.7.2 (Technical interface between RBCs).4.2.4. Mobile communication functions for railways GSM-R
This basic parameter describes the radio communication functions. Such functions shall be implemented in the Control-Command and Signalling On-board and Track-side subsystems, according to the specifications indicated below.
4.2.4.1. Basic communication function
The general requirements are specified in Annex A 4.2.4.a.
In addition, the following specifications shall be respected:

1. | ASCI features; Annex A 4.2.4.b;
2. | SIM card; Annex A 4.2.4.c;
3. | User-to-User Signalling; Annex A 4.2.4.d;
4. | location-dependent addressing; Annex A 4.2.4.e.4.2.4.2. Voice and operational communication applications
The general requirements are defined in Annex A 4.2.4.f.
The requirements for tests are specified in Annex A 4.2.4.g.
In addition, the following specifications shall be respected:

1. | confirmation of high-priority calls; Annex A 4.2.4.h;
2. | functional addressing; Annex A 4.2.4.j;
3. | presentation of functional numbers; Annex A 4.2.4.k.4.2.4.3. Data communication applications for ETCS
The general requirements are defined in Annex A 4.2.4.f.
The requirements for tests are specified in Annex A 4.2.4.g.
This functionality is mandatory only in the case of ETCS levels 2 and 3 and radio in-fill applications.
4.2.5. ERTMS/ETCS and GSM-R air gap interfaces
This basic parameter specifies the requirements for the air gap between Control-Command and Signalling Track-side and On-board subsystems and has to be taken into account in conjunction with the requirements for the interfaces between ERTMS/ETCS and GSM-R equipment, as specified in Section 4.2.6 (On-board Interfaces Internal to Control-Command and Signalling) and Section 4.2.7 (Track-side Interfaces Internal to Control-Command and Signalling).
This basic parameter includes:

1. | the physical, electrical and electromagnetic values to be respected to allow safe functioning;
2. | the communication protocol to be used;
3. | the availability of the communication channel.The applicable specifications are listed below.
4.2.5.1. Radio communications with the train
Class A radio communication interfaces shall operate in the GSM-R Band – see Annex A 4.2.5.a.
The protocols shall comply with Annex A 4.2.5.b.
Where radio in-fill is implemented, the requirements stated in Annex A 4.2.5.c shall be respected.
4.2.5.2. Eurobalise communication with the train
Eurobalise communication interfaces shall comply with Annex A 4.2.5.d.
4.2.5.3. Euroloop communication with the train
Euroloop communication interfaces shall comply with Annex A 4.2.5.e.
4.2.6. On-Board Interfaces Internal to Control-Command and Signalling
This Basic Parameter consists of three parts.
4.2.6.1. ERTMS/ETCS and Class B train protection
Where ERTMS/ETCS and Class B train protection functions are installed on-board, the transitions between them can be managed with a standardised interface as specified in Annex A 4.2.6.a.
Annex A 4.2.6.b specifies the K-interface (to allow certain STMs to read information from Class B balises through the ERTMS/ETCS on-board antenna) and Annex A 4.2.6.c the G interface (air gap between ETCS on-board antenna and Class B balises).
Implementation of Interface ‘K’ is optional, but if done it must be in accordance with Annex A 4.2.6.b.
Furthermore, if Interface ‘K’ is implemented, the on-board transmission channel functionality must be able to handle the properties of Annex A 4.2.6.c.
If the transitions between ERTMS/ETCS and Class B train protection on-board are not managed using the standardised interface specified in Annex A 4.2.6.a, steps must be taken to ensure that the method used does not impose any additional requirements on the Control-Command and Signalling Track-side Subsystem.
4.2.6.2. Interface between GSM-R Radio Data Communication and ERTMS/ETCS
The requirements for the interface between the Class A radio and the on-board ERTMS/ETCS functionality are specified in Annex A 4.2.6.d.
Where radio in-fill is implemented the requirements stated in Annex A 4.2.6.e shall be respected.
4.2.6.3. Odometry
The interface between the odometry function and on-board ETCS shall meet the requirements of Annex A 4.2.6.f. This interface contributes to this Basic Parameter only when odometry equipment is supplied as a separate interoperability constituent (see Section 5.2.2, Grouping of interoperability constituents).
4.2.7. Track-side Interfaces Internal to Control-Command and Signalling
This Basic Parameter consists of five parts.
4.2.7.1. Functional interface between RBCs
This interface defines the data to be exchanged between neighbouring RBCs to allow the safe movement of a train from one RBC area to the next:

1. | information from the ‘Handing Over’ RBC to the ‘Accepting’ RBC;
2. | information from the ‘Accepting’ RBC to the ‘Handing Over’ RBC.The requirements are specified in Annex A 4.2.7.a.
4.2.7.2. RBC/RBC
This is the technical interface between two RBCs. The requirements are specified in Annex A 4.2.7.b.
4.2.7.3. GSM-R/track-side ETCS
This is the interface between the Class A radio system and the track-side ETCS functionality. The requirements are specified in Annex A 4.2.7.c.
4.2.7.4. Eurobalise/LEU
This is the interface between Eurobalise and the LEU. The requirements are specified in Annex A 4.2.7.d.
This interface contributes to this basic parameter only when Eurobalise and LEU are supplied as separate interoperability constituents (see Section 5.2.2, Grouping of interoperability constituents).
4.2.7.5. Euroloop/LEU
This is the interface between Euroloop and the LEU. The requirements are specified in Annex A 4.2.7.e.
This interface contributes to this Basic Parameter only when Euroloop and LEU are supplied as separate interoperability constituents (see Section 5.2.2, Grouping of interoperability constituents).
4.2.8. Key Management
This basic parameter specifies requirements for the management of cryptographic keys used for the protection of data transmitted via radio.
The requirements are specified in Annex A 4.2.8.a. Only requirements related to the interfaces of Control-Command and Signalling equipment fall within the scope of this TSI.
4.2.9. ETCS-ID Management
This basic parameter concerns the ETCS-identities (ETCS-IDs) for equipment in Control-Command and Signalling Track-side and On-board Subsystems.
The requirements are specified in Annex A 4.2.9.a.
4.2.10. Track-side Train Detection Systems
This basic parameter specifies the interface requirements between the track-side train detection systems and rolling stock.
The interface requirements to be respected by the train detection systems are specified in Annex A 4.2.10.a.
4.2.11. Electromagnetic Compatibility between Rolling Stock and Control-Command and Signalling track-side equipment
This basic parameter specifies the interface requirements for electromagnetic compatibility between rolling stock and track-side Control-Command and Signalling equipment.
The interface requirements to be respected by the train detection system are specified in Annex A 4.2.11.a
4.2.12. ERTMS/ETCS DMI (Driver Machine Interface)
This basic parameter describes the information provided from ERTMS/ETCS to the driver and entered into the on-board ERTMS/ETCS by the driver. See Annex A 4.2.12.a.
It includes:

1. | ergonomics (including visibility);
2. | ERTMS/ETCS functions to be displayed;
3. | ERTMS/ETCS functions triggered by driver input.4.2.13. GSM-R DMI (Driver-Machine Interface)
This basic parameter describes the information provided from GSM-R to the driver and entered into the GSM-R on-board by the driver. See Annex A 4.2.13.a.
It includes:

1. | ergonomics (including visibility);
2. | GSM-R functions to be displayed;
3. | call-related information outgoing;
4. | call-related information incoming.4.2.14. Interface to Data Recording for Regulatory Purposes
This basic parameter describes:

1. | data exchange between the on-board ERTMS/ETCS and the rolling stock recording device;
2. | communication protocols;
3. | physical interface.See Annex A 4.2.14.a.
4.2.15. Visibility of track-side Control-Command and Signalling objects
This basic parameter describes:

1. | the characteristics of retro-reflecting signs to ensure correct visibility;
2. | the characteristics of interoperable marker boards.See Annex A 4.2.15.a.
In addition, the installation of track-side Control-Command and Signalling objects shall be compatible with the driver’s field of view and the infrastructure requirements.
4.2.16. Environmental conditions
The environmental conditions mandated in the specifications referenced in this TSI shall be respected.
4.3. Functional and technical specifications of the interfaces to other Subsystems
4.3.1. Interface to the Traffic Operation and Management Subsystem

Interface with Traffic Operation and Management TSI
Reference CCS TSI | Reference Traffic Operation and Management TSI
Parameter | Clause | Parameter | Clause
Operating rules (normal and degraded conditions) | 4.4 | Rule book | 4.2.1.2.1
Operating rules | 4.4
Visibility of track-side Control-Command and Signalling objects | 4.2.15 | Signal and line-side marker sighting | 4.2.2.8
Train braking performance and characteristics | 4.2.2 | Braking performance | 4.2.2.6
Use of sanding equipment | | |
On-board flange lubrication | 4.2.10 | Rule book | 4.2.1.2.1
Use of composite brake blocks | | |
Interface to Data Recording for Regulatory Purposes | 4.2.14 | Data recording on-board | 4.2.3.5
ETCS DMI | 4.2.12 | Train running number | 4.2.3.2.1
GSM-R DMI | 4.2.13 | Train running number | 4.2.3.2.14.3.2. Interface to the Rolling Stock Subsystem

Interface with Rolling Stock TSIs
Reference CCS TSI | | Reference Rolling Stock TSIs |
Parameter | Clause | Parameter | | Clause
Compatibility with track-side train detection systems: vehicle design | 4.2.10 | Rolling stock characteristics to be compatible with train detection systems based on track circuits | HS RS TSI |
wheelset location | 4.2.7.9.2
axle load | 4.2.3.2
sanding | 4.2.3.10
electrical resistance between wheels | 4.2.3.3.1
LOC & PAS TSI | 4.2.3.3.1.1
Wagon TSI | 4.2.3.2
Rolling stock characteristics to be compatible with train detection systems based on axle counters | HS RS TSI |
wheelset geometry | 4.2.7.9.2
wheels | 4.2.7.9.3
LOC & PAS TSI | 4.2.3.3.1.2
Wagon TSI | 4.2.3.3.1
Rolling stock characteristics to be compatible with loop equipment | HS RS TSI | None
LOC & PAS TSI | 4.2.3.3.1.3
Wagon TSI | None
Electromagnetic compatibility between rolling stock and Control-Command and Signalling track-side equipment | 4.2.11 | Rolling stock characteristics to be compatible with train detection systems based on track circuits | HS RS TSI | 4.2.6.6.1
LOC & PAS TSI | 4.2.3.3.1
Wagon TSI | None
Rolling stock characteristics to be compatible with train detection systems based on axle counters | HS RS TSI | 4.2.6.6.1
LOC & PAS TSI | 4.2.3.3.2
Wagon TSI | None
Train braking performance and characteristics | 4.2.2 | Emergency braking performance | HS RS TSI |
Emergency braking | 4.2.4.1
Service braking | 4.2.4.4
LOC & PAS TSI |
Emergency braking | 4.2.4.5.2
Service braking | 4.2.4.5.3
Wagon TSI | 4.2.4.1.2
Position of Control-Command and Signalling on-board antennas | 4.2.2 | Kinematic gauge | HS RS TSI | 4.2.3.1
LOC & PAS TSI | 4.2.3.1
Wagon TSI | None
Isolation of on-board ERTMS/ETCS functionality | 4.2.2 | Operating rules | HS RS TSI | 4.2.7.9.1
LOC & PAS TSI | 4.2.12.3
Wagon TSI | None
Data interfaces | 4.2.2 | Monitoring and diagnostic concepts | HS RS TSI | 4.2.7.10
LOC & PAS TSI | 4.2.1.1
Wagon TSI | None
Visibility of track-side Control-Command and Signalling objects | 4.2.15 | External visibilityHead lights | HS RS TSI | 4.2.7.4.1.1
LOC & PAS TSI | 4.2.7.1.1
Wagon TSI | None
Driver’s external field of view | HS RS TSI |
line of sight | 4.2.2.6 b
windscreen | 4.2.2.7
LOC & PAS TSI |
line of sight | 4.2.9.1.3.1
windscreen | 4.2.9.2
Wagon TSI | None
Interface to data recording for regulatory purposes | 4.2.14 | Recording device | HS RS TSI | 4.2.7.10
LOC & PAS TSI | 4.2.9.6
Wagon TSI | None
Commands to rolling stock equipment | 4.2.2 | Phase separation | HS RS TSI | 4.2.8.3.6.7
4.2.3 | LOC & PAS TSI | 4.2.8.2.9.8
Wagon TSI | None
Emergency braking command | 4.2.2 | Emergency braking command | HS RS TSI | None
LOC & PAS TSI | 4.2.4.4.1
Wagon TSI | None4.3.3. Interfaces to Infrastructure Subsystem

Interface with Infrastructure TSI
Reference CCS TSI | Reference Infrastructure TSI
Parameter | Clause | Parameter | | Clause
Train detection systems (space for installation) | 4.2.10 | Minimum infrastructure gauge | HS | 4.2.3
Structure gauge | CR | 4.2.4.1
Eurobalise communication (space for installation) | 4.2.5.2 | Minimum infrastructure gauge | HS | 4.2.3
Structure gauge | CR | 4.2.4.1
Euroloop communication (space for installation) | 4.2.5.3 | Minimum infrastructure gauge | HS | 4.2.3
Structure gauge | CR | 4.2.4.1
Visibility of track-side Control-Command and Signalling objects | 4.2.15 | Minimum infrastructure gauge | HS | 4.2.3
Structure gauge | CR | 4.2.4.14.3.4. Interfaces to Energy Subsystem

Interface with Energy TSI
Reference CCS TSI | Reference Energy TSI
Parameter | Clause | Parameter | | Clause
Commands to rolling stock equipment | 4.2.2 | Phase separation sections | HS ENE TSI | 4.2.21
4.2.3
System separation sections | 4.2.22
Phase separation sections | CR ENE TSI | 4.2.19
System separation sections | 4.2.204.4. Operating rules
The rules for operating a railway service with ERTMS/ETCS are specified in the Traffic Operation and Management TSI.
4.5. Maintenance rules
The maintenance rules of the subsystems covered by this TSI shall ensure that the values quoted in the basic parameters indicated in Chapter 4 are maintained within the required limits throughout the lifetime of the subsystems. However, during preventative or corrective maintenance, the subsystem may not be able to respect the values quoted in the basic parameters; the maintenance rules shall ensure that safety is not prejudiced during these activities.
The entity in charge of the Control-Command and Signalling Subsystems shall set up maintenance rules to achieve the above objectives. To assist with the preparation of these rules, the following requirements shall be respected.
4.5.1. Responsibility of the manufacturer of equipment
The manufacturer of equipment incorporated in the subsystem shall specify:

1. | all maintenance requirements and procedures (including health monitoring, diagnosis of events, test methods and tools and also the required professional competence) necessary for achieving essential requirements and values quoted in the mandatory requirements of this TSI throughout the equipment life-cycle (transport and storage before installation, normal operation, failures, repair work, checking and maintenance, decommissioning, etc.);
2. | the health and safety risks that may affect the public and the maintenance staff;
3. | the conditions for first line maintenance, i.e. the definition of Line Replaceable Units (LRUs), the definition of approved compatible versions of hardware and software, the procedures for replacing failed LRUs, and the conditions for storing LRUs and for repairing failed LRUs;
4. | the checks to be carried out if equipment is subject to exceptional stress (e.g. adverse environmental conditions or abnormal shocks);
5. | the checks to be carried out when maintaining equipment other than Control-Command and Signalling equipment and which influences the Control-Command and Signalling Subsystems (e.g. changing the wheel diameter).4.5.2. Responsibility of the applicant for subsystem verification
The applicant shall:

1. | ensure that the maintenance requirements as described in Section 4.5.1 (Responsibility of the Manufacturer of Equipment) are defined for all components within the scope of this TSI regardless of whether or not they are interoperability constituents;
2. | complete the above requirements taking into account the risks arising from interactions between different components of the subsystem and interfaces to other subsystems.4.6. Professional competences
The manufacturers of the equipment and of the subsystem shall provide information sufficient to define the professional competences required for the installation, final inspection and maintenance of the Control-Command and Signalling Subsystems. See Section 4.5 (Maintenance rules).
4.7. Health and safety conditions
Care shall be taken to ensure health and safety for maintenance and operations staff, in accordance with EU regulations and the national regulations that are compatible with the European legislation.
Manufacturers shall indicate the risks for health and safety that arise from using and maintaining their equipment and subsystems. See Section 4.4 (Operating rules) and Section 4.5 (Maintenance rules).
4.8. Registers
The data to be provided for the registers provided for in Articles 34 and 35 of Directive 2008/57/EC are those indicated in Commission Implementing Decision 2011/665/EU(3)and Commission Implementing Decision 2011/633/EU(4).
5. INTEROPERABILITY CONSTITUENTS5.1. Definition
According to Article 2(f) of the Railway Interoperability Directive, interoperability constituents are ‘any elementary component, group of components, subassembly or complete assembly of equipment incorporated or intended to be incorporated into a subsystem, upon which the interoperability of the rail system depends either directly or indirectly. The concept of a constituent covers both tangible objects and intangible objects such as software.’
5.2. List of interoperability constituents
5.2.1. Basic interoperability constituents
The basic interoperability constituents in the Control-Command and Signalling Subsystems are defined in:

1. | Table 5.1.a for the Control-Command and Signalling On-board Subsystem;
2. | Table 5.2.a for the Control-Command and Signalling Track-side Subsystem.5.2.2. Grouping of interoperability constituents
The functions of basic interoperability constituents may be combined to form a group. This group is then defined by those functions and by its remaining external interfaces. If a group is formed in this way, it shall be considered as an interoperability constituent.

| 1. | Table 5.1.b lists the groups of interoperability constituents of the Control-Command and Signalling On-board Subsystem.
| 2. | Table 5.2.b lists the groups of interoperability constituents of the Control-Command and Signalling Track-side Subsystem.5.3. Constituents’ performance and specifications
For each basic interoperability constituent or group of interoperability constituents, the tables in Chapter 5 describe:

1. | in column 3, the functions and interfaces. Note that some interoperability constituents have functions and/or interfaces that are optional;
2. | in column 4, the mandatory specifications for the conformity assessment of each function or interface (where applicable) by reference to the relevant section of Chapter 4.
Table 5.1.a

Basic interoperability constituents in the Control-Command and Signalling On-board Subsystem

N | Interoperability constituent IC | Characteristics | Specific requirements to be assessed by reference to Chapter 4
1 | ERTMS/ETCS on-board | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
On-board ETCS functionality (excluding odometry) | 4.2.2
ERTMS/ETCS and GSM-R air gap interfaces | 4.2.5
—RBC (levels 2 and 3) | — | RBC (levels 2 and 3) | 4.2.5.1
— | RBC (levels 2 and 3)
—Radio in-fill unit (optional level 1) | — | Radio in-fill unit (optional level 1) | 4.2.5.1
— | Radio in-fill unit (optional level 1)
—Eurobalise air gap | — | Eurobalise air gap | 4.2.5.2
— | Eurobalise air gap
—Euroloop air gap (optional level 1) | — | Euroloop air gap (optional level 1) | 4.2.5.3
— | Euroloop air gap (optional level 1)
Interfaces |
—STM (implementation of interface K optional) | — | STM (implementation of interface K optional) | 4.2.6.1
— | STM (implementation of interface K optional)
—ERTMS/ETCS GSM-R on-board | — | ERTMS/ETCS GSM-R on-board | 4.2.6.2
— | ERTMS/ETCS GSM-R on-board
—Odometry | — | Odometry | 4.2.6.3
— | Odometry
—Key management system | — | Key management system | 4.2.8
— | Key management system
—ETCS ID Management | — | ETCS ID Management | 4.2.9
— | ETCS ID Management
—ERTMS/ETCS Driver-Machine Interface | — | ERTMS/ETCS Driver-Machine Interface | 4.2.12
— | ERTMS/ETCS Driver-Machine Interface
—Train interface | — | Train interface | 4.2.2
— | Train interface
—On-board recording device | — | On-board recording device | 4.2.14
— | On-board recording device
Physical environmental conditions | 4.2.16
2 | Odometry equipment | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
On-board ERTMS/ETCS functionality: only Odometry | 4.2.2
Interfaces |
—On-board ERTMS/ETCS | — | On-board ERTMS/ETCS | 4.2.6.3
— | On-board ERTMS/ETCS
Environmental conditions | 4.2.16
3 | Interface of External STM | Interfaces |
—On-board ERTMS/ETCS | — | On-board ERTMS/ETCS | 4.2.6.1
— | On-board ERTMS/ETCS
4 | GSM-R voice cab radioNote: SIM card, antenna, connecting cables and filters are not part of this interoperability constituent | Reliability, Availability, Maintainability, Safety (RAMS)Note: no requirement for safety | 4.2.14.5.1
Basic communication functions | 4.2.4.1
Voice and operational communication applications | 4.2.4.2
Interfaces |
—GSM-R air gap | — | GSM-R air gap | 4.2.5.1
— | GSM-R air gap
—GSM-R Driver-Machine Interface | — | GSM-R Driver-Machine Interface | 4.2.13
— | GSM-R Driver-Machine Interface
Environmental conditions | 4.2.16
5 | GSM-R ETCS Data only RadioNote: SIM card, antenna, connecting cables and filters are not part of this interoperability constituent | Reliability, Availability, Maintainability, Safety (RAMS)Note: no requirement for safety | 4.2.14.5.1
Basic communication functions | 4.2.4.1
ETCS data communication applications | 4.2.4.3
Interfaces |
—On-board ERTMS/ETCS | — | On-board ERTMS/ETCS | 4.2.6.2
— | On-board ERTMS/ETCS
—GSM-R air gap | — | GSM-R air gap | 4.2.5.1
— | GSM-R air gap
Environmental conditions | 4.2.16
6 | GSM-R SIM card | Basic communication functions | 4.2.4.1
Environmental conditions | 4.2.16
Table 5.1.b

Groups of interoperability constituents in the Control-Command and Signalling On-board Subsystem
This table is an example to show the structure. Other groups are allowed

N | Group of Interoperability constituents | Characteristics | Specific requirements to be assessed by reference to Chapter 4
1 | ERTMS/ETCS on-boardOdometry equipment | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
On-board ERTMS/ETCS functionality | 4.2.2
ERTMS/ETCS and GSM-R air gap interfaces | 4.2.5
—RBC (levels 2 and 3) | — | RBC (levels 2 and 3) | 4.2.5.1
— | RBC (levels 2 and 3)
—Radio in-fill unit (optional level 1) | — | Radio in-fill unit (optional level 1) | 4.2.5.1
— | Radio in-fill unit (optional level 1)
—Eurobalise air gap | — | Eurobalise air gap | 4.2.5.2
— | Eurobalise air gap
—Euroloop air gap (optional level 1) | — | Euroloop air gap (optional level 1) | 4.2.5.3
— | Euroloop air gap (optional level 1)
Interfaces |
—STM (implementation of interface K optional) | — | STM (implementation of interface K optional) | 4.2.6.1
— | STM (implementation of interface K optional)
—On-board ERTMS/ETCS – GSM-R | — | On-board ERTMS/ETCS – GSM-R | 4.2.6.2
— | On-board ERTMS/ETCS – GSM-R
—Key management system | — | Key management system | 4.2.8
— | Key management system
—ETCS-ID Management | — | ETCS-ID Management | 4.2.9
— | ETCS-ID Management
—ERTMS/ETCS Driver Machine Interface | — | ERTMS/ETCS Driver Machine Interface | 4.2.12
— | ERTMS/ETCS Driver Machine Interface
—Train interface | — | Train interface | 4.2.2
— | Train interface
—On-board recording device | — | On-board recording device | 4.2.14
— | On-board recording device
Physical environmental conditions | 4.2.16
Table 5.2.a

Basic interoperability constituents in the Control-Command and Signalling Track-side Subsystem

N | Interoperability constituent IC | Characteristics | Specific requirements to be assessed by reference to Chapter 4
1 | RBC | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via Eurobalises, radio in-fill and Euroloop) | 4.2.3
ERTMS/ETCS and GSM-R air gap interfaces: only radio communication with train | 4.2.5.1
Interfaces |
—Neighbouring RBC | — | Neighbouring RBC | 4.2.7.1, 4.2.7.2
— | Neighbouring RBC
—ERTMS/ETCS GSM-R track-side | — | ERTMS/ETCS GSM-R track-side | 4.2.7.3
— | ERTMS/ETCS GSM-R track-side
—Key management system | — | Key management system | 4.2.8
— | Key management system
—ETCS-ID Management | — | ETCS-ID Management | 4.2.9
— | ETCS-ID Management
Environmental conditions | 4.2.16
2 | Radio in-fill unit | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via Eurobalises, Euroloop and level 2/3 functionality) | 4.2.3
ERTMS/ETCS and GSM-R air gap interfaces: only radio communication with train | 4.2.5.1
Interfaces |
—ERTMS/ETCS- GSM-R track-side | — | ERTMS/ETCS- GSM-R track-side | 4.2.7.3
— | ERTMS/ETCS- GSM-R track-side
—Key management system | — | Key management system | 4.2.8
— | Key management system
—ETCS-ID Management | — | ETCS-ID Management | 4.2.9
— | ETCS-ID Management
—Interlocking and LEU | — | Interlocking and LEU | 4.2.3
— | Interlocking and LEU
Environmental conditions | 4.2.16
3 | Eurobalise | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
ERTMS/ETCS and GSM-R air gap interfaces: only Eurobalise communication with train | 4.2.5.2
Interfaces |
—LEU – Eurobalise | — | LEU – Eurobalise | 4.2.7.4
— | LEU – Eurobalise
Environmental conditions | 4.2.16
4 | Euroloop | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
ERTMS/ETCS and GSM-R air gap interfaces: only Euroloop communication with train | 4.2.5.3
Interfaces |
—LEU – Euroloop | — | LEU – Euroloop | 4.2.7.5
— | LEU – Euroloop
Environmental conditions | 4.2.16
5 | LEU Eurobalise | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via radio in-fill, Euroloop and level 2 and level 3 functionality) | 4.2.3
Interfaces |
—LEU – Eurobalise | — | LEU – Eurobalise | 4.2.7.4
— | LEU – Eurobalise
Environmental conditions | 4.2.16
6 | LEU Euroloop | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via radio in-fill, Eurobalise and level 2 and level 3 functionality) | 4.2.3
Interfaces |
—LEU – Euroloop | — | LEU – Euroloop | 4.2.7.5
— | LEU – Euroloop
Environmental conditions | 4.2.16
Table 5.2.b

Groups of interoperability constituents in the Control-Command and Signalling Track-side Subsystem
This table is an example to show the structure. Other groups are allowed

N | Group of interoperability constituents | Characteristics | Specific requirements to be assessed by reference to Chapter 4
1 | EurobaliseLEU Eurobalise | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
Track-side ERTMS/ETCS functionality (excluding communication via Euroloop and level 2 and level 3 functionality) | 4.2.3
ERTMS/ETCS and GSM-R air gap interfaces: only Eurobalise communication with train | 4.2.5.2
Environmental conditions | 4.2.16
2 | EuroloopLEU Euroloop | Reliability, Availability, Maintainability, Safety (RAMS) | 4.2.14.5.1
Track-side ERTMS/ETCS functionality, (excluding communication via Eurobalise and level 2 and level 3 functionality) | 4.2.3
ERTMS/ETCS and GSM-R air gap interfaces: only Euroloop communication with train | 4.2.5.3
Environmental conditions | 4.2.166. ASSESSING THE CONFORMITY AND/OR SUITABILITY FOR USE OF THE CONSTITUENTS AND VERIFYING THE SUBSYSTEMS6.1. Introduction
6.1.1. General principles
Fulfilment of the essential requirements set out in Chapter 3 of this TSI shall be ensured through compliance with the basic parameters specified in Chapter 4.
This compliance shall be demonstrated by:

1. | assessing the conformity of the interoperability constituents specified in Chapter 5 (see Section 6.2);
2. | verifying the subsystems (see Section 6.3).In certain cases, however, some of the essential requirements may be met by national rules, because of:

1. | the use of Class B systems;
2. | open points in the TSI;
3. | derogations pursuant to Article 9 of the Railway Interoperability Directive;
4. | specific cases described in Section 7.2.9.In such cases, assessment of conformity with those rules shall be carried out under the responsibility of the Member States concerned according to notified procedures.
6.1.2. Principles for testing ERTMS/ETCS and GSM-R
A Control-Command and Signalling On-board Subsystem covered by an ‘EC’ declaration of verification should be able to run on every Control-Command and Signalling Track-side Subsystem covered by an ‘EC’ Declaration of verification, under the conditions specified in this TSI, with no additional verifications.
Achievement of this goal is facilitated by:

1. | rules for the design and installation of the Control-Command and Signalling On-board and the Track-side subsystems;
2. | test specifications to prove that the Control-Command and Signalling On-board and Track-side Subsystems comply with the requirements of this TSI and are mutually compatible.To make the conformity assessment of ERTMS/ETCS and GSM-R equipment more effective and to help achieve the goal mentioned above, each Member State shall make available to the Commission the operational test scenarios for checking the ERTMS/ETCS and GSM-R part of the Control-Command and Signalling Track-side Subsystem and its interaction with the corresponding part of the Control-Command and Signalling On-board Subsystem. The test scenarios in question:

1. | shall be consistent with the specifications referenced in this TSI and provide a technical description of functions and performances (e.g. reaction times) where these are relevant for the interaction between on-board and track-side subsystems;
2. | shall be submitted in a standard format. See Annex A 4.2.2.c;
3. | shall, unless otherwise specified in Annex A 4.2.2.c, cover at least the start of mission, the transition between levels, transition between modes that may be used on the line, the main identified degraded situations, the sending of emergency messages and any other relevant aspects specific to the line.The European Railway Agency:

1. | shall make a preliminary publication of the operational test scenarios, allowing all interested parties to comment on the consistency of the test scenarios with the specifications referenced in this TSI and their impact on other implementations or developments. The period for comments shall be defined with each publication and shall not exceed 6 months;
2. | if the comments are negative, shall coordinate the efforts of the parties involved, in order to find an agreement, e.g. by changing the operational test scenarios;
3. | shall progressively build and make publicly available a database of test scenarios that have successfully passed the step described above and representing the situations which occur in different implementations;
4. | shall use the abovementioned data base to assess whether further mandatory test specifications are needed and whether it is necessary to draw up additional engineering rules for the Control-Command and Signalling On-board and Track-side subsystems.6.2. Interoperability constituents
6.2.1. Assessment procedures for Control-Command and Signalling Interoperability Constituents
Before placing on the market an interoperability constituent and/or groups of interoperability constituents the manufacturer or his authorised representative established within the European Union shall draw up an ‘EC’ declaration of conformity in accordance with Article 13(1) and Annex IV to the Railway Interoperability Directive.
The assessment procedure shall be carried out using one of the modules specified in Section 6.2.2 (Modules for Control-Command and Signalling Interoperability Constituents).
An ‘EC’ declaration of suitability for use is not required for Control-Command and Signalling interoperability constituents, because they have to fully comply with all the relevant basic parameters. This compliance is demonstrated by the ‘EC’ Declaration of conformity and is sufficient for placing them on the market(5).
6.2.2. Modules for Control-Command and Signalling Interoperability Constituents
For assessing interoperability constituents within the Control-Command and Signalling Subsystems, the manufacturer or his authorised representative established within the European Union, may choose:

1. | either the type-examination procedure (Module CB) for the design and development phase in combination with the production quality management system procedure (Module CD) for the production phase; or
2. | the type-examination procedure (Module CB) for the design and development phase in combination with the product verification procedure (Module CF); or
3. | the full quality management system with design examination procedure (Module CH1).In addition, for checking the SIM card Interoperability Constituent, the manufacturer or his representative may choose module CA.
The modules are described in detail in Commission Decision 2010/713/EU of 9 November 2010 on modules for the procedures for assessment of conformity, suitability for use and ‘EC’ verification to be used in the technical specifications for interoperability adopted under Directive 2008/57/EC of the European Parliament and of the Council(6).
The following clarifications apply to the use of some of the modules:

1. | with reference to Chapter 2 of the ‘Module CB’, ‘EC’-type examination must be carried out through a combination of production type and design type;
2. | with reference to Chapter 3 of the ‘Module CF’ (product verification) statistical verification is not allowed, i.e. all interoperability constituents must be individually examined.6.2.3. Assessment requirements
Independently of the selected module:

1. | the requirements stated in Section 6.2.4.1 of this TSI shall be respected for the ‘On-board ERTMS/ETCS’ interoperability constituent;
2. | the activities shown in Table 6.1 shall be carried out when assessing the conformity of an interoperability constituent or a group of interoperability constituents as defined in Chapter 5 of this TSI. All verifications shall be carried out by reference to the applicable table in Chapter 5 and the basic parameters indicated there.
Table 6.1

Aspect | What to assess | supporting evidence
Functions, interfaces and performances | Check that all mandatory functions, interfaces and performances as described in the basic parameters referenced in the relevant table of Chapter 5 are implemented and that they comply with the requirements of this TSI | Design documentation and running of test cases and test scenarios, as described in the basic parameters referenced in the relevant table of Chapter 5
Check which optional functions and interfaces as described in the basic parameters referenced in the relevant table of Chapter 5 are implemented and that they comply with the requirements of this TSI | Design documentation and running of test cases and test scenarios, as described in the basic parameters referenced in the relevant table of Chapter 5
Check which additional functions and interfaces (not specified in this TSI) are implemented and that they do not lead to conflicts with implemented functions specified in this TSI | Impact analysis
Environment | Check compliance with mandatory environmental conditions, where specified in the basic parameters referenced in the relevant table of Chapter 5 | Tests, to ensure that the requirements of the basic parameters referenced in the relevant table of Chapter 5 are satisfied
In addition, check that the interoperability constituent functions correctly in the environmental conditions for which it is designed | Tests according to the applicant’s specifications
Reliability, Availability, Maintainability, Safety (RAMS) | Check compliance with the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5, i.e.:1.respect for quantitative Tolerable Hazard Rates (THRs) caused by random failures;2.the development process is able to detect and eliminate systematic failures. | 1. | respect for quantitative Tolerable Hazard Rates (THRs) caused by random failures; | 2. | the development process is able to detect and eliminate systematic failures. | 1.Calculations for the THRs caused by random failures, based on supportable sources of reliability data.2.1.The manufacturer’s quality and safety management throughout design, manufacturing and testing conforms to a recognised standard (see Note).2.2.The software development life-cycle, the hardware development life-cycle and the integration of hardware and software have each been undertaken in accordance with a recognised standard (see Note).2.3.The safety verification and validation process has been undertaken in accordance with a recognised standard (see Note) and respects the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5.2.4.The functional and technical safety requirements (correct operation under fault-free conditions, effects of faults and of external influences) are verified in accordance with a recognised standard (see Note).Note: The standard shall satisfy at least the following requirements:1.be widely acknowledged in the railway domain. If this is not the case, the standard will have to be justified and be acceptable to the notified body;2.be relevant for the control of the considered hazards in the system under assessment;3.be publicly available for all actors who want to use it.See Annex A, Table A 3. | 1. | Calculations for the THRs caused by random failures, based on supportable sources of reliability data. | 2.1. | The manufacturer’s quality and safety management throughout design, manufacturing and testing conforms to a recognised standard (see Note). | 2.2. | The software development life-cycle, the hardware development life-cycle and the integration of hardware and software have each been undertaken in accordance with a recognised standard (see Note). | 2.3. | The safety verification and validation process has been undertaken in accordance with a recognised standard (see Note) and respects the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5. | 2.4. | The functional and technical safety requirements (correct operation under fault-free conditions, effects of faults and of external influences) are verified in accordance with a recognised standard (see Note). | 1. | be widely acknowledged in the railway domain. If this is not the case, the standard will have to be justified and be acceptable to the notified body; | 2. | be relevant for the control of the considered hazards in the system under assessment; | 3. | be publicly available for all actors who want to use it.
1. | respect for quantitative Tolerable Hazard Rates (THRs) caused by random failures;
2. | the development process is able to detect and eliminate systematic failures.
1. | Calculations for the THRs caused by random failures, based on supportable sources of reliability data.
2.1. | The manufacturer’s quality and safety management throughout design, manufacturing and testing conforms to a recognised standard (see Note).
2.2. | The software development life-cycle, the hardware development life-cycle and the integration of hardware and software have each been undertaken in accordance with a recognised standard (see Note).
2.3. | The safety verification and validation process has been undertaken in accordance with a recognised standard (see Note) and respects the safety requirements described in the basic parameters referenced in the relevant table of Chapter 5.
2.4. | The functional and technical safety requirements (correct operation under fault-free conditions, effects of faults and of external influences) are verified in accordance with a recognised standard (see Note).
1. | be widely acknowledged in the railway domain. If this is not the case, the standard will have to be justified and be acceptable to the notified body;
2. | be relevant for the control of the considered hazards in the system under assessment;
3. | be publicly available for all actors who want to use it.
Check that the quantitative reliability target indicated by the applicant is met | Calculations
Check compliance with maintenance requirements – Section 4.5.1 | Document check6.2.4. Special issues
6.2.4.1. The on-board ERTMS/ETCS
Particular attention shall be given to assessing the conformity of the on-board ERTMS/ETCS interoperability constituent, since it is complex and plays a key role in achieving interoperability.
Regardless of whether module CB or CH1 is chosen, the Notified Body shall check that a specimen of the interoperability constituent has passed the full set of mandatory test sequences referenced in Section 4.2.2 (on-board ERTMS/ETCS functionality) and that these tests were carried out in a laboratory accredited to carry out this type of tests in accordance with Regulation (EC) No 765/2008 of the European Parliament and of the Council of 9 July 2008 setting out the requirements for accreditation and market surveillance relating to the marketing of products and repealing Regulation (EEC) No 339/93(7).
In addition, to increase confidence that the on-board ERTMS/ETCS can be correctly operated with different track-side applications, it is recommended that the on-board ERTMS/ETCS be tested using scenarios from the data base managed by the Agency and which are not part of the mandatory test specifications; see Section 6.1.2 (Principles for testing ERTMS/ETCS and GSM-R). The documentation accompanying the certificate shall indicate the database scenarios against which the interoperability constituent has been checked.
6.2.4.2. The Specific Transmission Module (STM)
Each Member State shall be responsible for verifying that STMs conform to its national requirements.
Verification of the STM interface to the on-board ERTMS/ETCS requires a conformity assessment carried out by a Notified Body.
6.2.4.3. Content of the ‘EC’ Declaration of conformity
The ‘EC’ Declaration of conformity specified in Annex IV to the Railway Interoperability Directive shall include the following details concerning the interoperability constituent:

1. | which optional and additional functions are implemented;
2. | the applicable environmental conditions.6.3. Control-Command and Signalling Subsystems
6.3.1. Assessment procedures for Control-Command and Signalling Subsystems
This chapter deals with the ‘EC’ declaration of verification for the Control-Command and Signalling On-board Subsystem and the ‘EC’ declaration of verification for the Control-Command and Signalling Track-side Subsystem.
At the request of the applicant the Notified Body shall carry an ‘EC’ verification of a Control-Command and Signalling On-board or Track-side Subsystem in accordance with Annex VI to the Railway Interoperability Directive.
The applicant shall draw up the ‘EC’ declaration of verification for the Control-Command and Signalling On-board or Track-side Subsystem in accordance with Article 18(1) and Annex V to the Railway Interoperability Directive.
The content of the ‘EC’ declaration of verification shall conform to Annex V to the Railway Interoperability Directive.
The assessment procedure shall be carried out by using one of the modules as specified in Section 6.3.2 (Modules for Control-Command and Signalling Subsystems).
The ‘EC’ declarations of verification for a Control-Command and Signalling On-board Subsystem and of a Control-Command and Signalling Track-side Subsystem, together with the certificates of conformity, shall be deemed sufficient to ensure that the subsystems are compatible under the conditions specified in this TSI.
6.3.2. Modules for Control-Command and Signalling Subsystems
All modules indicated below are specified in the Decision 2010/713/EU.
6.3.2.1. On-board Subsystem
For verifying the Control-Command and Signalling On-board Subsystem, the applicant may choose either:

1. | the type-examination procedure (Module SB) for the design and development phase in combination with the production quality management system procedure (Module SD) for the production phase; or
2. | the type-examination procedure (Module SB) for the design and development phase in combination with the product verification procedure (Module SF); or
3. | the full quality management system with design examination procedure (Module SH1).6.3.2.2. Track-side Subsystem
For verifying the Control-Command and Signalling Track-side Subsystem, the applicant may choose either:

1. | the unit verification procedure (Module SG); or
2. | the type-examination procedure (Module SB) for the design and development phase in combination with the production quality management system procedure (Module SD) for the production phase; or
3. | the type-examination procedure (Module SB) for the design and development phase in combination with the product verification procedure (Module SF); or
4. | the full quality management system with design examination procedure (Module SH1).6.3.2.3. Conditions for using modules for On-board and Track-side Subsystems
With reference to Section 4.2 of Module SB (type-examination), design review is requested.
With reference to Section 4.2 of Module SH1 (full quality management system with design examination), a type test is required.
6.3.3. Assessment requirements for an On-board Subsystem
Table 6.2 shows the checks that must be carried out when verifying a Control-Command and Signalling On-board Subsystem and the basic parameters that must be respected.
Independently of the module chosen:

1. | verification shall demonstrate that the Control-Command and Signalling On-board Subsystem complies with basic parameters when it is integrated into the vehicle;
2. | the functionality and performances of interoperability constituents already covered by their EC Declaration of conformity do not require additional verifications.
Table 6.2

Aspect | What to assess | supporting evidence
Use of interoperability constituents | Check whether the interoperability constituents to be integrated into the subsystem are all covered by an ‘EC’ Declaration of conformity and a corresponding certificate. | Existence and content of documents
Check restrictions on the use of Interoperability Constituents against the characteristics of the subsystem and of the environment | Analysis by document check
For interoperability constituents that have been certified against older versions of the CCS TSI, check that the certificate still ensures compliance with the requirements of the TSI currently in force. | Impact analysis by document checks
Integration of interoperability constituents in the subsystem | Check the correct installation and functioning of the internal interfaces of the subsystem – Basic parameters 4.2.6 | Checks according to specifications
Check that additional functions (not specified in this TSI) do not impact the mandatory ones | Impact analysis
Check that the values of ETCS IDs are within the allowed range – Basic parameter 4.2.9 | Check of design specifications
Integration with rolling stock | Check the correct installation of equipment – Basic Parameters 4.2.2, 4.2.4, 4.2.14 and conditions for installation of equipment, as specified by the manufacturer | Results of checks (according to specifications referenced in the Basic Parameters and the manufacturer’s installation rules)
Check that the Control-Command and Signalling On-board Subsystem is compatible with the rolling stock environment | Document check (certificates of interoperability constituents and possible integration methods checked against characteristics of rolling stock)
Check that parameters (e.g. braking parameters) are correctly configured and that they are within the allowed range | Document check (values of parameters checked against characteristics of rolling stock)
Integration with Class B | Check that the external STM is connected to on-board ERTMS/ETCS with TSI-compliant interfaces | Nothing to test: there is a standard interface already tested at interoperability constituent level. Its functioning has already been tested when checking the integration of interoperability constituents in the subsystem
Check that Class B functions implemented in the on-board ERTMS/ETCS – Basic parameter 4.2.6.1 – create no additional requirements for the Control-Command and Signalling Track-side Subsystem due to transitions | Nothing to test: everything has already been tested at interoperability constituent level
Check that separate Class B equipment which is not connected to the on-board ERTMS/ETCS – Basic Parameter 4.2.6.1 – creates no additional requirements for Control-Command and Signalling Track-side Subsystem due to transitions | Nothing to test: no interface(8)
Check that separate Class B equipment connected on-board ERTMS/ETCS using (partly) non-TSI compliant interfaces – basic parameter 4.2.6.1 – creates no additional requirements for the Control-Command and Signalling Track-side Subsystem due to transitions. Also check that ERTMS/ETCS functions are not affected | Impact analysis
Integration with Control-Command and Signalling Track-side Subsystems | Check that Eurobalise telegrams can be read (scope of this test is limited to checking that the antenna has been appropriately installed. The tests already carried out at Interoperability Constituent level should not be repeated) – Basic Parameter 4.2.5 | Test using a certified Eurobalise: the ability to read correctly the telegram is the supporting evidence.
Check that Euroloop telegrams (if applicable) can be read – Basic Parameter 4.2.5 | Test using a certified Euroloop: the ability to read correctly the telegram is the supporting evidence.
Check that the equipment can handle a GSM-R call for voice and data (if applicable) – Basic Parameter 4.2.5 | Test with a certified GSM-R network. The ability to set up, maintain and disconnect a connection is the supporting evidence.
Reliability, Availability, Maintainability, Safety (RAMS) | Check that the equipment complies with safety requirements – Basic Parameter 4.2.1 | Application of procedures specified in the Common Safety Method
Check that the quantitative reliability target is met – Basic Parameter 4.2.1 | Calculations
Check the compliance with requirements about maintenance – Section 4.5.2 | Documents check
Integration with Control-Command and Signalling Track-side Subsystems and other subsystems:tests under operational conditions | Test the behaviour of the subsystem under as many different operational conditions as reasonably possible (e.g. line gradient, train speed, vibrations, traction power, weather conditions, design of Control-Command and Signalling track-side functionality). The test must be able to verify:1.that odometry functions are correctly performed – basic parameter 4.2.22.that the on-board Control-Command and Signalling Subsystem is compatible with the rolling stock environment – basic parameter 4.2.16These tests must also be such as to increase confidence that there will be no systematic failures.The scope of these tests excludes tests already carried out at earlier stages: tests performed on the interoperability constituents and tests performed on the subsystem in a simulated environment shall be taken into account.Tests under operational conditions are not necessary for on-board GSM-R voice equipment. | 1. | that odometry functions are correctly performed – basic parameter 4.2.2 | 2. | that the on-board Control-Command and Signalling Subsystem is compatible with the rolling stock environment – basic parameter 4.2.16 | Reports of test runs.Note: Indicate in the certificate which conditions have been tested, which standards have been applied and the criteria for considering the tests terminated
1. | that odometry functions are correctly performed – basic parameter 4.2.2
2. | that the on-board Control-Command and Signalling Subsystem is compatible with the rolling stock environment – basic parameter 4.2.166.3.4. Assessment requirements for a Track-side Subsystem
The purpose of assessments carried out within the scope of this TSI is to verify that the equipment complies with the requirements stated in Chapter 4.
However, for the design of the ERTMS/ETCS part of the Control-Command and Signalling Track-side Subsystem, application-specific information is needed; This should include:

1. | line characteristics such as gradients, distances, positions of route elements and Eurobalises/Euroloops, locations to be protected, etc;
2. | the signalling data and rules to be handled by the ERTMS/ETCS system.This TSI does not cover checks to assess whether the application-specific information is correct:
Regardless of the module chosen:

1. | Table 6.3 shows the checks that must be carried out to verify a Control-Command and Signalling Track-side Subsystem and the basic parameters that must be respected;
2. | functionality and performances that have already been checked at the level of the interoperability constituents do not require additional verification.
Table 6.3

Aspect | What to assess | supporting evidence
Use of interoperability constituents | Check that all interoperability constituents to be integrated into the subsystem are covered by an EC declaration of conformity and the corresponding certificate. | Existence and content of documents
Check restrictions on the use of interoperability constituents against the characteristics of the subsystem and of the environment | Impact analysis by documents check
For interoperability constituents that have been certified against older versions of the Control-Command and Signalling TSI, check that the certificate still ensures compliance with the requirements of the TSI currently in force | Impact analysis by comparison of specifications referenced in the TSI and certificates of the interoperability constituents
Use of train detection systems | Check that the selected types comply with Control-Command and Signalling TSI requirements – Basic parameters 4.2.10, 4.2.11 | Document check
Integration of interoperability constituents in the subsystem | Check that the internal interfaces of the subsystem have been installed properly and function properly – Basic parameters 4.2.5, 4.2.7 | Checks according to specifications
Check that additional functions (not specified in this TSI) do not impact the mandatory ones | Impact analysis
Check that the values of ETCS IDs are within the allowed range – Basic Parameter 4.2.9 | Check of design specifications
Integration with infrastructure | Check that the equipment has been properly installed – Basic parameters 4.2.3, 4.2.4 and conditions for installation specified by the manufacturer | Results of checks (according to specifications referenced in the basic parameters and manufacturer’s installation rules)
Check that the Control-Command and Signalling Track-side subsystem equipment is compatible with the track-side environment | Document check (certificates of interoperability constituents and possible methods of integration checked against track-side characteristics)
Integration with track-side signalling | Check that all functions required by the application are implemented in accordance with specifications referenced in this TSI – Basic parameter 4.2.3 | Document check (applicant’s design specification and certificates of interoperability constituents)
Check the correct configuration of parameters (Eurobalise telegrams, RBC messages, marker boards positions, etc.) | Document check (values of parameters checked against characteristics of track-side and of signalling)
Check that the interfaces are correctly installed and function properly. | Design verification and tests according to information supplied by the applicant
Check that the Control-Command and Signalling Track-side subsystem operates correctly according to information at the interfaces with track-side signalling (e.g. appropriate generation of Eurobalise telegrams by a LEU or of message by RBC) | Design verification and tests according to the information supplied by the applicant
Integration with Control-Command and Signalling On-board Subsystems and with rolling stock | Check the GSM-R coverage – Basic Parameter 4.2.4 | On-site measurements
Check the compliance of the train detection systems with the requirements of this TSI – Basic Parameter 4.2.10 | On-site measurements
Check that the train detection systems comply with the requirements of this TSI – Basic parameters 4.2.10 and 4.2.11 | Check evidence from existing installations (for systems already in use); perform tests according to standards for new types
Check that all functions required by the application are implemented in accordance with specifications referenced in this TSI – basic parameters 4.2.3, 4.2.4 and 4.2.5 | Reports of tests of the operational scenarios specified in Section 6.1.2 with different certified Control-Command and Signalling On-board Subsystems. The report shall indicate which operational scenarios have been tested, which on-board equipment has been used and whether tests have been performed in laboratories, test lines or real implementation.
Reliability, Availability, Maintainability, Safety (RAMS) | Check compliance with safety requirements – Basic Parameter 4.2.1 | Application of procedures specified in the Common Safety Method
Check that quantitative reliability targets are respected – Basic Parameter 4.2.1 | Calculations
Check the compliance with requirements about maintenance – Section 4.5.2 | Document check
Integration with Control-Command and Signalling On-board Subsystems and rolling stock:tests under operational conditions | Test the behaviour of the subsystem under such different operational conditions as reasonably feasible (e.g. train speed, number of trains on the line, weather conditions). The test must be able to verify:1.the performance of train detection systems – Basic parameters 4.2.10, 4.2.11,2.that the Control-Command and Signalling Track-side subsystem is compatible with track-side environment – Basic parameter 4.2.16These tests will also increase confidence in the absence of systematic failures.The scope of these tests excludes tests already done in previous steps: tests performed at the level of interoperability constituents and tests performed on the subsystem in a simulated environment shall be taken into account. | 1. | the performance of train detection systems – Basic parameters 4.2.10, 4.2.11, | 2. | that the Control-Command and Signalling Track-side subsystem is compatible with track-side environment – Basic parameter 4.2.16 | Reports of test runs.Note: Indicate in the certificate which conditions have been tested, which standards have been applied and the criteria for considering the tests terminated.
1. | the performance of train detection systems – Basic parameters 4.2.10, 4.2.11,
2. | that the Control-Command and Signalling Track-side subsystem is compatible with track-side environment – Basic parameter 4.2.166.4. Provisions for partial conformity
6.4.1. Introduction
Pursuant to Article 18(4) of the Railway Interoperability Directive, ‘the Notified Body may issue Intermediate Statement Verifications (ISVs) to cover certain stages of the verification procedure or certain parts of the subsystem’.
As pointed out in Section 2.2 (Scope) of this TSI, the Control-Command and Signalling Subsystems include three parts, which are specified in Section 4.1 (Introduction).
Section 6.4.2 deals with the verification of these parts of the Control-Command and Signalling Subsystems.
Section 6.4.3 deals with the verification of partial conformity of Control-Command and Signalling Subsystems when there are restricted conditions of use of its interoperability constituent(s).
6.4.2. Assessment of parts of Control-Command and Signalling Subsystems
Assessing whether a Control-Command and Signalling Track-side or On-board Subsystem complies with the requirements of this TSI is a process that may be performed in successive steps – one for each of the three parts. At each step, the assessor checks only whether that particular part complies with the TSI requirements.
Regardless of which module is chosen, the Notified Body shall verify that:

1. | the TSI requirements for the part in question have been respected;
2. | the TSI requirements already assessed are not prejudiced.Functions already assessed and unchanged and which are not affected by this step do not need to be checked again.
6.4.3. Partial conformity of Control-Command and Signalling Subsystems due to restricted conditions of use of its interoperability constituent(s) A partial certificate of conformity for an interoperability constituent can be issued even if some function, interface or performance has not been implemented, provided that:

1. | The non-implemented function, interface or performance is not required for integrating the interoperability constituent into a subsystem because of specific conditions of use, for example(9):(a)the on-board ERTMS/ETCS interface to STM if the interoperability constituent is intended for installation on vehicles where no external STM is needed;(b)the RBC interface to other RBCs, if the RBC is intended for use in an application where no neighbouring RBCs are planned. | (a) | the on-board ERTMS/ETCS interface to STM if the interoperability constituent is intended for installation on vehicles where no external STM is needed; | (b) | the RBC interface to other RBCs, if the RBC is intended for use in an application where no neighbouring RBCs are planned.
(a) | the on-board ERTMS/ETCS interface to STM if the interoperability constituent is intended for installation on vehicles where no external STM is needed;
(b) | the RBC interface to other RBCs, if the RBC is intended for use in an application where no neighbouring RBCs are planned.
2. | The certificate indicates which functions, interfaces or performance are not implemented and states the corresponding restrictions on the use of the interoperability constituent. This information will make it possible to identify the conditions under which the interoperability constituent can be used and the restrictions that will apply to the interoperability of a subsystem incorporating it.In any event, the conditions for issuing such certificates with restrictions shall be coordinated between the Notified Bodies and the Agency in a working group set up pursuant to Article 21a(5) of Regulation (EC) No 881/2004 of the European Parliament and of the Council of 29 April 2004 establishing a European Railway Agency (Agency Regulation)(10).
When the interoperability constituent is integrated into a Control-Command and Signalling On-board or Track-side Subsystem, if the missing functions, interfaces, or performances do not allow to assess whether the subsystem fully complies with the requirements of this TSI, only an Intermediate Statement of Verification may be issued. It shall indicate which requirements have been assessed and shall state the corresponding restrictions on the use of the subsystem and its compatibility with other subsystems.
7. IMPLEMENTING THE TSI CONTROL-COMMAND AND SIGNALLING7.1. Introduction
This chapter outlines the strategy and the associated technical measures for implementing the TSI, and in particular the conditions for migrating to Class A systems.
Account must be taken of the fact that the implementation of a TSI occasionally has to be coordinated with the implementation of other TSIs.
7.2. Generally applicable rules
7.2.1. Upgrading or renewing the Control-Command Track-side Subsystem or parts of it
Upgrading or renewing the Control-Command and Signalling Track-side Subsystem may concern any or all of the following:

1. | Train protection
2. | Radio communication
3. | Train detectionThese different parts of the Control-Command and Signalling Track-side Subsystem may therefore be upgraded or renewed separately if interoperability is not jeopardised. The work involved will concern:

1. | GSM-R functions and interfaces
2. | ERTMS/ETCS functions and interfaces
3. | Train detection system compatibility with rolling stockSee Chapter 4.1 (Introduction) for the definition of the basic parameters for each part.
7.2.2. Legacy systems
Member States shall ensure that the functionality of the legacy systems and their interfaces remains unchanged, except where modifications are needed to mitigate safety-related flaws in these systems.
7.2.3. Availability of Specific Transmission Modules
If lines that fall within the scope of this TSI are not equipped with Class A train protection systems, the Member State shall make every effort to ensure the availability of an external Specific Transmission Module (STM) for its legacy Class B train protection system or systems.
In this context, due regard is to be given to ensuring an open market for STMs under fair commercial conditions. If, for technical or commercial reasons(11)the availability of an STM cannot be ensured, the Member State concerned shall inform the Committee of the underlying reasons for the problem and of the mitigation measures that it intends to put into place in order to allow operators — and in particular foreign operators — access to its infrastructure.
7.2.4. Additional Class B equipment on a line equipped with Class A
On a line equipped with ERTMS/ETCS and/or GSM-R, additional Class B equipment may be installed in order to allow the operation of rolling stock not compatible with Class A during the migration phase. Class B equipment may be used on-board as a fallback arrangement for a Class A system. However an infrastructure manager is not entitled to require the interoperable trains running on such a line to have Class B systems on board.
In addition, track-side shall support transitions between Class A and Class B without imposing on the Control-Command and Signalling On-board Subsystem requirements additional to those specified in this TSI.
7.2.5. Rolling stock with Class A and Class B equipment
Rolling stock may be equipped with both Class A and Class B systems to enable operation on several lines.
The Member State concerned may restrict the use of an on-board Class B system on lines where the corresponding system is not installed track-side.
When running on a line which is equipped with both Class A and Class B systems, a train that is also equipped with both Class A and Class B systems may use the Class B systems as a fallback arrangement. This cannot be a requirement for interoperability.
The Class B train protection systems may be implemented:

1. | using an STM operating via the standard interface (‘external STM’); or
2. | integrated within the ERTMS/ETCS equipment or connected via a non-standard interface; or
3. | independently from the ERTMS/ETCS equipment, for example via a system that enables switching between equipment. The Railway Undertaking must then ensure that the transitions between Class A and Class B train protection are carried out in conformity with the requirements of this TSI and with the national rules for the Class B system.7.2.6. Conditions for mandatory and optional functions
Depending on the characteristics of the Control-Command and Signalling Track-side Sub-system and its interfaces with other sub-systems, some track-side functionalities not classified as mandatory may necessarily have to be implemented in certain applications to comply with the essential requirements.
The track-side implementation of national or optional-functions must not prevent the use of that infrastructure by a train that complies only with the mandatory requirements of the On-board Class A system except as required for the following on-board optional functions:

— | an ETCS Level 3 Track-side application requires train integrity supervision on board,
— | an ETCS Level 1 Track-side application with in-fill requires corresponding in-fill functionality on board if the release speed is set to zero for safety reasons (e.g. protection of danger points),
— | when ETCS requires data transmission by radio, the data transmission services of GSM-R must fulfil the ETCS data transmission requirements,
— | an on-board assembly, which incorporates a KER STM, may make it necessary to implement the K-interface.7.2.7. GSM-R specific implementation rules
7.2.7.1. Track-side installations
The fitting of GSM-R is mandatory when:

1. | installing for the first time the radio part of a Control-Command and Signalling Track-side Subsystem;
2. | upgrading the radio part of a Control-Command and Signalling Track-side Subsystem already in service in such a way that it changes the functions or the performance of the subsystem. This does not include the modifications deemed necessary to mitigate safety-related defects in the legacy installation.7.2.7.2. On-board installations
The fitting of GSM-R in rolling stock intended for use on a line including at least one section equipped with Class A interfaces (even if superimposed to a Class B system), is mandatory when:

1. | installing for the first time the radio part of a Control-Command and Signalling On-board Subsystem;
2. | upgrading the radio part of a Control-Command and Signalling On-board Subsystem already in service in such a way that it changes the functions or the performance of the subsystem. This does not apply to modifications deemed necessary to mitigate safety-related defects in the legacy installation.7.2.8. Train detection systems specific implementation rules
In the context of this TSI, train detection system means the equipment installed track-side, which detects the presence or absence of vehicles either on an entire line of route or on a local section of it.
Track-side systems (e.g. interlocking or level crossing control systems) which use information from detection equipment are not considered parts of the train detection system.
This TSI specifies the requirements for the interface with rolling stock only to the extent necessary to ensure compatibility between TSI-compliant rolling stock and the infrastructure.
Implementing a train detection system that is compliant with the requirements of the Control-Command and Signalling Subsystems TSI can be done independently of the installation of ERTMS/ETCS or GSM-R, but can be dependent on the Class B signalling systems or on special requirements, e.g. for level crossing equipment.
The requirements of this TSI relating to train detection systems shall be respected when:

1. | upgrading the train detection system;
2. | renewing the train detection system, provided that respecting the requirements of this TSI does not imply unwanted modifications or upgrades of other track-side or on-board systems;
3. | renewing the train detection system, where this is required by the upgrade or renewal of track-side systems that use information from the train detection system;
4. | removing Class B train protection systems (where the train detection and train protection systems are integrated).In the migration phase care shall be taken to ensure that installing a TSI compliant train detection system has a minimal negative impact on the existing non-TSI compliant rolling stock.
To achieve this, it is recommended that the Infrastructure Manager selects a TSI compliant train detection system that, at the same time, is compatible with the non-TSI compliant rolling stock already operating on that infrastructure.
7.2.9. Specific cases
7.2.9.1. Introduction
The following special provisions are permitted in the specific cases below.
These specific cases belong to two categories: the provisions apply either permanently (case ‘P’) or temporarily (case ‘T’).
In this TSI, temporary case ‘T3’ is defined as temporary cases which will still exist after 2020.
The specific cases set out in Sections 7.2.9.2 to 7.2.9.7 should be read in conjunction with the relevant sections of Chapter 4 and/or specifications referenced there.
The specific cases replace the corresponding requirements set out in Chapter 4.
Where the requirements set out in the relevant section of Chapter 4 are not subject to a specific case, those requirements have not been duplicated in Sections 7.2.9.2 to 7.2.9.7 and continue to apply unmodified.
7.2.9.2. Belgium

Specific case | Category | Notes
4.2.10 Track-side Train Detection SystemsIndex 77, Section 3.1.2.4:The distance between first and last axle L – (b1+ b2) (Figure 1) is at least 15 000 mm | T3 | Applicable on HS L1This Specific Case is linked with the use of TVM
4.2.10 Track-side Train Detection SystemsIndex 77, Section 3.1.8:The weight of an isolated vehicle or a trainset is at least 40 t.If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000 mm | | The weight of an isolated vehicle or a trainset is at least 40 t. | | If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000 mm | T3 | Applicable on HS L1, L2, L3, L4This Specific Case is linked with the use of TVM
| The weight of an isolated vehicle or a trainset is at least 40 t.
| If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000 mm7.2.9.3. United Kingdom

Specific case | Category | Notes
4.2.10 Track-side Train Detection SystemsIndex 77, Section 3.1.2.4:The distance between first and last axle L – (b1+ b2) (Figure 1) is at least 15 000 mm | T3 | Applicable on High-Speed L 1This Specific Case is linked with the use of TVM
4.2.10 – Track-side Train Detection SystemsIndex 77, Section 3.1.4.1:In addition to the requirements in Section 3.1.4.1, sanding for traction purposes on multiple units:(a)is not permitted ahead of the leading axle below 40 km/h; and(b)is only permitted where it can be demonstrated that at least a further six axles of the multiple unit are beyond the laying position. | (a) | is not permitted ahead of the leading axle below 40 km/h; and | (b) | is only permitted where it can be demonstrated that at least a further six axles of the multiple unit are beyond the laying position. | T3 |
(a) | is not permitted ahead of the leading axle below 40 km/h; and
(b) | is only permitted where it can be demonstrated that at least a further six axles of the multiple unit are beyond the laying position.
4.2.12 ERTMS/ETCS DMI (Driver Machine Interface)Index 51:It is permissible to use an alphanumeric keyboard to enter the train running number if support for alphanumeric train running numbers is required by the technical rule notified for this purpose. | T3 | This specific case is needed as soon as the open point related to the DMI specification is closed.There is no impact on interoperability
4.2.12 ERTMS/ETCS DMI (Driver Machine Interface)Index 51:It is permissible for the ETCS DMI to display dynamic train speed information in miles per hour (and indicate ‘mph’) when operating on parts of the GB mainline network. | T3 | This specific case is needed as soon as the open point related to the DMI specification is closed.There is no impact on interoperability7.2.9.4. France

Specific case | Category | Notes
4.2.10 Track-side Train Detection SystemsIndex 77, Section 3.1.2.4:The distance between first and last axle L – (b1+ b2) (Figure 1) is at least 15 000 mm | T3 | This Specific Case is linked with the use of TVM
4.2.10 Track-side Train Detection SystemsIndex 77, Section 3.1.9:The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS. | | The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit). | | In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS. | T3 | This specific case may be revised when the open point related to the frequency management for track circuits is closed
| The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).
| In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS.
4.2.10 – Track-side Train Detection SystemsIndex 77, Section 3.1.8:The weight of an isolated vehicle or a trainset is at least 40 t.If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000 mm. | | The weight of an isolated vehicle or a trainset is at least 40 t. | | If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000 mm. | T3 | This Specific Case is linked with the use of TVM
| The weight of an isolated vehicle or a trainset is at least 40 t.
| If the weight of an isolated vehicle or a trainset is inferior to 90 t, the vehicle should have a system ensuring the shunting which has an electrical basis superior or equal to 16 000 mm.
4.2.10 – Track-side Train Detection SystemsIndex 77, Section 3.1.3.2:Dimension D (Figure 2) is not less than:450 mm independently of the speed | | Dimension D (Figure 2) is not less than: | | 450 mm independently of the speed | 5 years |
| Dimension D (Figure 2) is not less than:
| 450 mm independently of the speed7.2.9.5. Poland

Specific case | Category | Notes
4.2.10 Track-side Train Detection SystemsIndex 77, Section 3.1.9:The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS. | | The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit). | | In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS. | T3 | This specific case may be revised when the open point related to the frequency management for track circuits is closed
| The electrical resistance between the running surfaces of the opposite wheels of a wheelset does not exceed 0,05 Ohm, measured by a voltage between 1,8 VDC and 2,0 VDC (open circuit).
| In addition, the electrical reactance between the running surfaces of the opposite wheels of a wheelset does not exceed f/100 mOhm when f is between 500 Hz and 40 kHz, under a measuring current of at least 10 ARMS and open voltage of 2 VRMS.7.2.9.6. Lithuania, Latvia

Specific case | Category | Notes
4.2.10 Track-side Train Detection SystemsIndex 77, Section 3.1.3.4:The range of the dimension Sh(Figure 2) is not less than 26,25 mm | T3 | This specific case is needed as long as ČME locomotives operate on Lithuania 1 520 mm network7.2.9.7. Sweden

Specific case | Category | Notes
4.2.4 Mobile communication functions for railways – GSM-RIndex 65, statement 4.2.3:It is permissible to put in service on-board Control-Command and Signalling Subsystems including 2 Watt GSM-R voice cab radios and ETCS data only radios. The subsystems shall be able to operate in networks with – 82 dBm. | P | No impact on interoperability7.2.9.8. Luxembourg

Specific case | Category | Notes
4.2.10 Track-side Train Detection SystemsIndex 77, Section 3.1.2.4:1.The output of the sanding devices fitted to the vehicle shall not exceed 0,3 l per minute per rail.2.The sanding in the stations identified in the infrastructure register is prohibited.3.The sanding in the area of switches is prohibited.4.For emergency braking, no restrictions shall apply | 1. | The output of the sanding devices fitted to the vehicle shall not exceed 0,3 l per minute per rail. | 2. | The sanding in the stations identified in the infrastructure register is prohibited. | 3. | The sanding in the area of switches is prohibited. | 4. | For emergency braking, no restrictions shall apply | T3 |
1. | The output of the sanding devices fitted to the vehicle shall not exceed 0,3 l per minute per rail.
2. | The sanding in the stations identified in the infrastructure register is prohibited.
3. | The sanding in the area of switches is prohibited.
4. | For emergency braking, no restrictions shall apply7.3. Rules for ERTMS
7.3.1. The ERTMS European Deployment Plan
This section outlines the strategy (ERTMS European Deployment Plan) for implementing the TSI. It specifies the stages to be completed in order to make a gradual transition from the existing situation to the final situation in which compliance with the TSIs shall be the norm.
The ERTMS European Deployment Plan does not apply to lines located in the territory of a Member State when its rail network is separated or isolated by the sea or separated as a result of special geographical conditions or of different track gauge from the rail network of the rest of the Community.
7.3.2. ERTMS Track-side Implementation
The aim of the ERTMS European Deployment Plan is to ensure that locomotives, railcars and other railway vehicles equipped with ERTMS can gradually have access to an increasing number of lines, ports, terminals and marshalling yards without needing national equipment in addition to ERTMS.
This does not mean that existing Class B systems have to be removed from the lines included in the plan. However, by the date specified in the implementation plan, locomotives, railcars and other railway vehicles equipped with ERTMS must be given access to lines included in the deployment plan without requiring those vehicles to be equipped with a Class B system.
Terminal areas such as ports, or specific lines in a port, which are not equipped with a Class B system fulfil the requirements set out in Section 7.3.2.2 provided railway vehicles are given access to these terminal areas without any requirement as regards equipment with an Automatic Train Protection system being imposed.
A line consisting of two or more tracks shall be considered equipped as soon as two of the tracks are equipped so as to allow traffic in both directions. When there is more than one line on a section of a corridor, at least one of the lines on this section must be equipped and the whole corridor shall be considered equipped as soon as at least one line is equipped over the whole length of the corridor.
7.3.2.1. Corridors
The six corridors described in Section 7.3.4 shall be equipped with ERTMS according to the timetable indicated in that section(12).
7.3.2.2. Connection to the main European ports, marshalling yards, freight terminals and freight transport areas
The ports, marshalling yards, freight terminals and freight transport areas listed in 7.3.5 shall be linked to at least one of the six corridors specified in 7.3.4 at the date and under the conditions specified in 7.3.5.
7.3.2.3. High-speed network
It is mandatory to fit ERTMS/ETCS track-side when:

1. | installing for the first time the train protection part of a Control-Command and Signalling Track-side Subsystem (with or without a Class B system); or
2. | upgrading the existing train protection part of a Control-Command and Signalling Track-side Subsystem, where this would change the functions, performance and/or interoperability-relevant interfaces (air gaps) of the existing legacy system. This does not apply to modifications deemed necessary to mitigate safety-related defects in the legacy installation.It is recommended that ERTMS/ETCS be installed whenever the infrastructure or energy sub-system of a section of line already in service is to be upgraded, renewed or maintained, provided the installation of ERTMS/ETCS on that section of line represents less than 10 % of the total upgrade/renewal/maintenance investment.
7.3.2.4. EU-funded projects
Without prejudice to Sections 7.3.2.1, 7.3.2.2 and 7.3.2.3, in the case of railway infrastructure projects receiving financial support from European Regional Development Funds and/or Cohesion Funds (Council Regulation (EC) No 1083/2006 of 11 July 2006 laying down general provisions on the European Regional Development Fund, the European Social Fund and the Cohesion Fund(13)) and/or the TEN-T funds (Decision No 1692/96/EC of the European Parliament and of the Council(14)) the fitting of ERTMS/ETCS is mandatory when:

1. | installing for the first time the train protection part of a Control-Command and Signalling Subsystem; or
2. | upgrading the train protection part of a Control-Command and Signalling Subsystem already in service, where this changes the functions or the performance of the subsystem.7.3.2.5. Notification
For each corridor section described in 7.3.4, Member States shall either notify to the Commission a detailed timeline for equipping that corridor section with ERTMS or confirm that the corridor section is already equipped. The information shall be notified to the Commission no later than 3 years before the deadline for equipping that corridor section, as specified in 7.3.4.
For each port, marshalling yard, freight terminal or freight transport area listed in 7.3.5, Member States shall notify the specific lines to be used to connect it with one of the corridors listed in 7.3.4. This information shall be notified to the Commission no later than 3 years before the date specified in 7.3.5 and shall indicate the deadline for equipping this port, marshalling yard, freight terminal or freight transport area. If necessary, the Commission may request adjustments, in particular to ensure consistency between equipped lines at the borders. Member States shall either notify to the Commission a detailed timeline for equipping these specific lines with ERTMS or confirm that these specific lines are already equipped. This information shall be notified to the Commission no later than 3 years before the date specified in 7.3.5 and shall indicate the deadline for equipping this port, marshalling yard, freight terminal or freight transport area.
The detailed timelines shall in particular indicate the date by which the tender for equipping of the line will be concluded, the procedures put in place in order to ensure interoperability with the neighbouring countries on the corridor and the main milestones relating to the project. Every 12 months, Member States shall inform the Commission of the progress made in equipping these lines sending an updated timeline.
7.3.2.6. Delays
When a Member State reasonably expects delays in fulfilling the deadlines laid down in this Decision, it shall immediately inform the Commission. It shall send the Commission a file containing a technical description of the project and an up-to-date implementation plan. The file shall also explain the reasons for the delay and shall indicate the corrective measures the Member State has taken.
A deadline extension of no more than 3 years can be granted to a Member State when the delay is due to causes beyond the Member State’s reasonable control such as failure of suppliers or problems regarding the authorisation process due to the absence of appropriate test vehicles. Such an extension can be advocated by a Member State only when the following conditions are fulfilled:

1. | the notifications, if needed, referred to in Section 7.3.2.5 were received in time and were comprehensive;
2. | the file referred to in Section 7.3.2.6, first paragraph, contains clear evidence that the causes for the delay were beyond the Member State’s control;
3. | a competent authority is responsible for coordinating on-board and track-side suppliers and for integrating and testing of products;
4. | appropriate use has been made of existing laboratories;
5. | evidence is given that appropriate measures have been taken to minimise the additional delay.The Commission shall examine the file sent to it and the measures proposed by the Member State and shall notify the result of its examination to the committee referred to in Article 29 of Directive 2008/57/EC.
7.3.3. ERTMS – On-board implementation
New locomotives, new railcars and other new railway vehicles able to run without traction equipped with a driving cab, ordered after 1 January 2012 or put into service after 1 January 2015, shall be equipped with ERTMS.
This requirement does not apply to new shunting locomotives or to other new locomotives, new railcars and other new railway vehicles equipped with a driving cab, if they are designed exclusively for national service or regional border crossing service. Member States may however introduce additional requirements at national level, in particular with a view to:

1. | allowing only ERTMS equipped locomotives to access ERTMS-equipped lines, so that existing national systems can be decommissioned;
2. | requesting that new shunting locomotives and/or other new railway vehicles equipped with a driving cab, even if designed exclusively for national service or regional border crossing service, be equipped with ERTMS.7.3.3.1. High-speed network
It is mandatory to fit ERTMS/ETCS on board when:

1. | installing any new train protection part of a Control-Command and Signalling On-board Subsystem; or
2. | upgrading any existing train protection part of a Control-Command and Signalling On-board Subsystem, where this would change the functions, performances and/or interoperability-relevant interfaces of the existing legacy system. This does not apply to modifications deemed necessary to mitigate safety related defects in the legacy system.7.3.4. Specific lines constituting the corridors

Corridor A – to be equipped by 2015

Corridor B
(15)
Corridor C
(16)
Corridor D
(17)
Corridor E

Corridor F
7.3.5. Main European ports, marshalling yards, freight terminals and freight transport areas

Country | Freight transport area | Date | Remark
Belgium | Antwerpen | 31.12.2015 | A link to Rotterdam shall also be provided by 2020.
Gent | 31.12.2020 |
Zeebrugge | 31.12.2020 |
Bulgaria | Burgas | 31.12.2020 | The connection to corridor E implies equipping the Burgas-Sofia section and the Sofia-Vidin-Calafat and Calafat-Curtici sections in Romania (PP22).
Czech Republic | Praha | 31.12.2015 |
Lovosice | 31.12.2020 |
Denmark | Taulov | 31.12.2020 | Connecting this terminal implies that the Flensburg-Padborg line is chosen to be an ERTMS equipped link – see corridor B footnote.
Germany | Dresden(18) | 31.12.2020 | By 2020, a direct link between corridor E and corridor F (from Dresden to Hannover) shall also be ensured.
Lübeck | 31.12.2020 |
Duisburg | 31.12.2015 |
Hamburg(19) | 31.12.2020 |
Köln | 31.12.2015 |
München | 31.12.2015 |
Hannover | 31.12.2015 |
Rostock | 31.12.2015 |
Ludwigshafen/Mannheim | 31.12.2015 |
Nürnberg | 31.12.2020 |
Greece | Pireás | 31.12.2020 | The connection to Corridor E implies equipping the Kulata-Sofia section in Bulgaria.
Spain | Algeciras | 31.12.2020 |
Madrid | 31.12.2020 |
Pamplona | 31.12.2020 | Three connections are requested. A connection to Paris via Hendaye, a connection from Pamplona to Madrid and a connection from Pamplona to corridor D via Zaragoza.
Zaragoza | 31.12.2020 |
Tarragona | 31.12.2020 |
Barcelona | 31.12.2015 |
Valencia | 31.12.2020 |
France | Marseille | 31.12.2020 |
Perpignan | 31.12.2015 |
Avignon | 31.12.2015 |
Lyon | 31.12.2015 |
Le Havre | 31.12.2020 |
Lille | 31.12.2020 |
Dunkerque | 31.12.2020 |
Paris | 31.12.2020 | By 2020 the following connections will be provided: (i) Hendaye; (ii) Channel Tunnel; (iii) Dijon; and (iv) Metz via Epernay and Châlons-en-Champagne.
Italy | La Spezia | 31.12.2020 |
Genova | 31.12.2015 |
Gioia Tauro | 31.12.2020 |
Verona | 31.12.2015 |
Milano | 31.12.2015 |
Taranto | 31.12.2020 |
Bari | 31.12.2020 |
Padova | 31.12.2015 |
Trieste | 31.12.2015 |
Novara | 31.12.2015 |
Venezia | 31.12.2020 |
Bologna | 31.12.2020 |
Roma | 31.12.2020 |
Luxembourg | Bettembourg | 31.12.2015 |
Hungary | Budapest | 31.12.2015 |
Netherlands | Amsterdam | 31.12.2020 |
Rotterdam | 31.12.2015 | A link to Antwerpen shall also be provided by 2020.
Austria | Graz | 31.12.2020 |
Wien | 31.12.2020 |
Poland | Gdynia | 31.12.2015 |
Katowice | 31.12.2020 |
Wrocław | 31.12.2015 | By 2020 the Wrocław-Legnica line, shall be equipped in order to ensure a direct link to the German border (Görlitz).
Gliwice | 31.12.2015 |
Poznań | 31.12.2015 |
Warszawa | 31.12.2015 |
Portugal | Sines | 31.12.2020 |
Lisboa | 31.12.2020 |
Romania | Constanța | 31.12.2015 |
Slovenia | Koper | 31.12.2015 |
Ljubljana | 31.12.2015 |
Slovakia | Bratislava | 31.12.2015 |
United Kingdom | Bristol | | This terminal will be connected as corridor C is extended to the Channel Tunnel.
(1) Degraded modes are modes of operation designed to deal with faults. They have been taken into account when designing the Control-Command and Signalling Subsystems.
(2)
OJ L 108, 29.4.2009, p. 4.
(3)
OJ L 264, 8.10.2011, p. 32.
(4)
OJ L 256, 1.10.2011, p. 1.
(5) Checking that an Interoperability Constituent is used appropriately is part of the overall EC verification of Control-Command and Signalling On-board and Track-side Subsystems, as explained in 6.3.3 and 6.3.4.
(6)
OJ L 319, 4.12.2010, p. 1.
(7)
OJ L 218, 13.8.2008, p. 30.
(8) In this case, the assessment of the management of transitions shall be according to national specifications.
(9) The procedures described in this Chapter do not prejudice the possibility of grouping constituents together.
(10)
OJ L 164, 30.4.2004, p. 1.
(11) E.g. the feasibility of the external STM concept cannot be technically guaranteed or potential issues relating to the ownership of the intellectual property rights of the Class B systems prevent the timely development of an STM product.
(12) Section 7.3.4 lays down the deadlines for equipping these corridors, with a view to building a consistent ERTMS network step by step. In a number of cases, there are voluntary agreements on an earlier deadline.
(13)
OJ L 210, 31.7.2006, p. 25.
(14)
OJ L 228, 9.9.1996, p. 1.
(15) Without prejudice of the legislation applicable to the trans-European high-speed network, links can be provided through stretches of high-speed lines, provided paths are allocated to freight trains. At least one ERTMS-equipped link will be provided by 2020 between Denmark and Germany (Flensburg-Hamburg or Rødby-Puttgarden) but not necessarily two. The Brenner base tunnel will be equipped with ERTMS once the infrastructure work is completed (target date 2020).
(16) A link between Nancy and Réding will be provided by 2020.
(17) Two additional branches will be equipped by 2020: Montmélian – Grenoble – Valence and Lyon – Valence – Arles – Miramas (left bank of the Rhône).
(18) Germany will do its best to equip the corridor E section from Dresden to the Czech border at an earlier date.
(19) Germany will equip a rail link to Hamburg but the harbour area may be only partly equipped by 2020.

References

ANNEX AFor each reference made in the basic parameters (Chapter 4 of this TSI) the following table indicates the corresponding mandatory specifications, via the Index in Table 2.

Table A 1

Reference in Chapter 4 | Index number (See Table A 2)
4.1
4.1a | 1
4.1b | 32
4.1c | 3
|
4.2.1
4.2.1 a | 27, 78
4.2.1 b | 28
|
4.2.2
4.2.2.a | 14
4.2.2.b | 1, 4, 13, 15
4.2.2.c | 31, 37
4.2.2.d | 18, 20
4.2.2.e | 6,
4.2.2.f | 7
|
4.2.3
4.2.3 a | 14
4.2.3 b | 1, 4, 13, 15
4.2.3 c | 31, 37 b, c, d
4.2.3 d | 18, 21
|
4.2.4
4.2.4 a | 64, 65
4.2.4 b | 66
4.2.4 c | 67
4.2.4 d | 68
4.2.4 e | 73, 74
4.2.4 f | 32, 33
4.2,4 g | 48
4.2,4 h | 69, 70
4.2.4 j | 71, 72
4.2.4 k | 75, 76
|
4.2.5
4.2.5 a | 64, 65
4.2.5 b | 10, 39, 40
4.2.5c | 19, 20
4.2.5 d | 9, 43
4.2.5 e | 16, 50
|
4.2.6
4.2.6 a | 8, 25, 26, 49
4.2.6 b | 45
4.2.6 c | 46
4.2.6 d | 34
4.2.6 e | 20
4.2.6 f | 44
|
4.2.7
4.2.7 a | 12
4.2.7 b | 62, 63
4.2.7 c | 34
4.2.7 d | 9
4.2.7 e | 16
|
4.2.8
4.2.8 a | 11
|
4.2.9
4.2.9 a | 23
|
4.2.10
4.2.10 a | 77 (Section 3.1)
|
4.2.11
4.2.11 a | 77 (Section 3.2)
|
4.2.12
4.2.12 a | 51
|
4.2.13
4.2.13 a | 32, 33, 51
|
4.2.14
4.2.14 a | 5
|
4.2.15
4.2.15 a | 38
Specifications
For the purposes of applying this TSI, all specifications listed in Table A 2 below shall be legally binding in the version indicated in Table A 2. Documents referred to within a specification listed in Table A 2 shall be considered as being for information only, unless otherwise stated Table A 2.
In cases where statements within the specifications listed in Table A 2 contradict the abovementioned provisions, the latter shall take precedence.

Note: | specifications indicated as ‘Reserved’ in Table A 2 correspond to the open points listed in Annex G.
Table A 2

List of mandatory specifications

Index N | Reference | Name of Specification | Version | Notes
1 | ERA/ERTMS/003204 | ERTMS/ETCS Functional requirement specification | 5.0 |
2 | Intentionally deleted | | |
3 | UNISIG SUBSET-023 | Glossary of terms and abbreviations | 2.0.0 |
4 | UNISIG SUBSET-026 | System requirement specification | 2.3.0 |
5 | UNISIG SUBSET-027 | FFFIS Juridical recorder-downloading tool | 2.3.0 | Note 1
6 | UNISIG SUBSET-033 | FIS for man-machine interface | 2.0.0 |
7 | UNISIG SUBSET-034 | FIS for the train interface | 2.0.0 |
8 | UNISIG SUBSET-035 | Specific transmission module FFFIS | 2.1.1 |
9 | UNISIG SUBSET-036 | FFFIS for Eurobalise | 2.4.1 |
10 | UNISIG SUBSET-037 | EuroRadio FIS | 2.3.0 |
11 | UNISIG SUBSET-038 | Offline key management FIS | 2.3.0 |
12 | UNISIG SUBSET-039 | FIS for the RBC/RBC handover | 2.3.0 |
13 | UNISIG SUBSET-040 | Dimensioning and engineering rules | 2.3.0 |
14 | UNISIG SUBSET-041 | Performance requirements for interoperability | 2.1.0 |
15 | ERA SUBSET-108 | Interoperability related consolidation on TSI Annex A documents | 1.2.0 |
16 | UNISIG SUBSET-044 | FFFIS for Euroloop subsystem | 2.3.0 |
17 | Intentionally deleted | | |
18 | UNISIG SUBSET-046 | Radio in-fill FFFS | 2.0.0 |
19 | UNISIG SUBSET-047 | Track-side-trainborne FIS for radio in-fill | 2.0.0 |
20 | UNISIG SUBSET-048 | Trainborne FFFIS for radio in-fill | 2.0.0 |
21 | UNISIG SUBSET-049 | Radio in-fill FIS with LEU/interlocking | 2.0.0 |
22 | Intentionally deleted | | |
23 | UNISIG SUBSET-054 | Assignment of values to ETCS variables | 2.1.0 |
24 | Intentionally deleted | | |
25 | UNISIG SUBSET-056 | STM FFFIS Safe time layer | 2.2.0 |
26 | UNISIG SUBSET-057 | STM FFFIS Safe link layer | 2.2.0 |
27 | UNISIG SUBSET-091 | Safety requirements for the technical interoperability of ETCS in levels 1 and 2 | 2.5.0 |
28 | Reserved | Reliability — availability requirements | |
29 | UNISIG SUBSET-102 | Test specification for interface ‘K’ | 1.0.0 |
30 | Intentionally deleted | | |
31 | UNISIG SUBSET-094 | Functional requirements for an on-board reference test facility | 2.0.2 |
32 | EIRENE FRS | GSM-R Functional requirements specification | 7 |
33 | EIRENE SRS | GSM-R System requirements specification | 15 |
34 | A11T6001 12 | (MORANE) Radio transmission FFFIS for EuroRadio | 12 |
35 | Intentionally deleted | | |
36 a | Intentionally deleted | | |
36 b | Intentionally deleted | | |
36 c | UNISIG SUBSET-074-2 | FFFIS STM Test cases document | 1.0.0 |
37 a | Intentionally deleted | | |
37 b | UNISIG SUBSET-076-5-2 | Test cases related to features | 2.3.1 |
37 c | UNISIG SUBSET-076-6-3 | Test sequences | 2.3.1 |
37 d | UNISIG SUBSET-076-7 | Scope of the test specifications | 1.0.2 |
37 e | Intentionally deleted | | |
38 | 06E068 | ETCS Marker-board definition | 2.0 |
39 | UNISIG SUBSET-092-1 | ERTMS EuroRadio conformance requirements | 2.3.0 |
40 | UNISIG SUBSET-092-2 | ERTMS EuroRadio test cases safety layer | 2.3.0 |
41 | Intentionally deleted | | |
42 | Intentionally deleted | | |
43 | UNISIG SUBSET 085 | Test specification for Eurobalise FFFIS | 2.2.2 |
44 | Reserved | Odometry FIS | |
45 | UNISIG SUBSET-101 | Interface ‘K’ specification | 1.0.0 |
46 | UNISIG SUBSET-100 | Interface ‘G’ specification | 1.0.1 |
47 | Intentionally deleted | | |
48 | Reserved | Test specification for mobile equipment GSM-R | |
49 | UNISIG SUBSET-059 | Performance requirements for STM | 2.1.1 |
50 | UNISIG SUBSET-103 | Test specification for Euroloop | 1.0.0 |
51 | Reserved | Ergonomic aspects of the DMI | |
52 | UNISIG SUBSET-058 | FFFIS STM Application layer | 2.1.1 |
53 | Intentionally deleted | | |
54 | Intentionally deleted | | |
55 | Intentionally deleted | | |
56 | Intentionally deleted | | |
57 | Intentionally deleted | | |
58 | Intentionally deleted | | |
59 | Intentionally deleted | | |
60 | Intentionally deleted | | |
61 | Intentionally deleted | | |
62 | ReservedUNISIG SUBSET-099 | RBC-RBC Test specification for safe communication interface | |
63 | UNISIG SUBSET-098 | RBC-RBC Safe communication interface | 1.0.0 |
64 | EN 301 515 | Global System for Mobile Communication (GSM); Requirements for GSM operation on railways | 2.3.0 | Note 2
65 | TR 102 281 | Detailed requirements for GSM operation on railways | 1.0.0 | Note 3
66 | (MORANE) A 01 T 0004 1 | ASCI Options for Interoperability | 1 |
67 | (MORANE) P 38 T 9001 | FFFIS for GSM-R SIM Cards | 4.1 |
68 | ETSI TS 102 610 | Railway Telecommunication; GSM; Usage of the UUIE for GSM operation on railways | 1.1.0 |
69 | (MORANE) F 10 T 6002 | FFFS for Confirmation of High-Priority Calls | 4 |
70 | (MORANE) F 12 T 6002 | FIS for Confirmation of High-Priority Calls | 4 |
71 | (MORANE) E 10 T 6001 | FFFS for Functional Addressing | 4 |
72 | (MORANE) E 12 T 6001 | FIS for Functional Addressing | 5.1 |
73 | (MORANE) F 10 T6001 | FFFS for Location Dependent Addressing | 4 |
74 | (MORANE) F 12 T6001 | FIS for Location Dependent Addressing | 3 |
75 | (MORANE) F 10 T 6003 | FFFS for Presentation of Functional Numbers to Called and Calling Parties | 4 |
76 | (MORANE) F 12 T 6003 | FIS for Presentation of Functional Numbers to Called and Calling Parties | 4 |
77 | ERA/ERTMS/033281 | Interfaces between CCS track-side and other subsystems | 1.0 |
78 | Reserved | Safety requirements for ETCS DMI functions | |
Note 1: | only the functional description of information to be recorded is mandatory, not the technical characteristics of the interface.
Note 2: | the specifications listed in Section 2.1 of EN 301 515 are mandatory.
Note 3: | the change requests (CRs) listed in Tables 1 and 2 of TR 102 281 are mandatory.
Table A 3

List of mandatory standards
The standards listed in the table below shall be applied in the certification process, without prejudice for the provisions of Chapters 4 and 6 of this TSI.

No | Reference | Document name and comments | Version
A1 | EN 50126 | Railway applications — The specification and demonstration of reliability, availability, maintainability and safety (RAMS) | 1999
A2 | EN 50128 | Railway applications — Communication, signalling and processing systems — Software for railway control and protection systems | 2001
A3 | EN 50129 | Railway applications — Communication, signalling and processing systems — Safety related electronic systems for signalling | 2003
A4 | EN 50159-1 | Railway applications — Communication, signalling and processing systems — Part 1 | 2001
A5 | EN 50159-2 | Railway applications — Communication, signalling and processing systems — Part 2: Safety related communication in open transmission systems | 2001

ANNEX BIntentionally deleted
ANNEX CIntentionally deleted
ANNEX DIntentionally deleted
ANNEX EIntentionally deleted
ANNEX FIntentionally deleted
ANNEX G
OPEN POINTS

Open Point | Notes
Braking aspects | This open point will be solved by ERTMS/ETCS baseline 3. The harmonised braking model is already included for information purposes in Annex A, Table A 2, Index 15.
Index 28 availability | Frequent occurrence of degraded situations caused by failures of Control-Command and Signalling equipment will decrease the system safety. To avoid this, minimum reliability/availability requirements that shall be specified.
Index 78 safety requirements for ETCS DMI functions | This open point is related to the interface between ETCS on-board and driver, i.e. errors in displaying information and in entering data and commands
Index 51 Ergonomic aspects of the DMI | This open point will be solved by ERTMS/ETCS baseline 3. A specification for information purposes already exists.
Minimum wheel diameter for speed greater than 350 km/h | See Annex A, Table A 2, Index 77
Minimum axle distance for speed greater than 350 km/h | See Annex A, Table A 2, Index 77
Metal and inductive components free space between wheels | See Annex A, Table A 2, Index 77This is not an open point for freight wagons
Characteristics of sand applied to tracks | See Annex A, Table A 2, Index 77
Vehicle metal mass | See Annex A, Table A 2, Index 77
Combination of rolling stock characteristics for the purpose of adequate dynamic shunting impedance | See Annex A, Table A 2, Index 77
Electromagnetic interferences (traction current) | See Annex A, Table A 2, Index 77
Electromagnetic interferences (electromagnetic fields) | See Annex A, Table A 2, Index 77This is not an open point for power systems other than DC
DC and low frequency components of traction current | See Annex A, Table A 2, Index 77
Use of magnetic/eddy current brakes | See Annex A, Table A 2, Index 77