{
  "url": "https://openlegislation.uk/eu-decision-2002-731/annex/division-5/division-5.2",
  "json_url": "https://openlegislation.uk/eu-decision-2002-731/annex/division-5/division-5.2.json",
  "legislation": "eudn/2002/731",
  "legislation_title": "Commission Decision of 30 May 2002 concerning the technical specification for interoperability relating to the control-command and signalling subsystem of the trans-European high-speed rail system referred to in Article 6(1) of Council Directive 96/48/EC (notified under document number C(2002) 1947) (Text with EEA relevance) (2002/731/EC)",
  "legislation_url": "https://openlegislation.uk/eu-decision-2002-731",
  "path": "annex/division/5/division/5.2",
  "kind": "division",
  "number": "5.2",
  "heading": "GROUPING OF INTEROPERABILITY CONSTITUENTS",
  "text": "The control-command interoperability constituents defined in Tables 5.1 and 5.2 may be combined to form a larger unit. The group is then defined by the functions of the integrated interoperability constituents and the remaining inter-faces on the outside of the group. The groups are defined in Tables 5.1 and 5.2. Each group has to be supported by European specifications. A group so formed is then to be considered as an interoperability constituent.\nThe declaration of conformity for an interoperability constituent requires that each of its interfaces referred to in Table 5 is supported by one or more European specifications. The specifications concerned will be referenced by Annex A. As long as a European specification is not available to support an interface given in Table 5, this interoperability constituent cannot be supported by a declaration of conformity. Therefore the interoperability constituent concerned shall be integrated into a group of interoperability constituents for which a declaration of conformity is then possible.\nTable 5.1a\nBasic interoperability constituents in the on-board control-command assembly\nDefinition of safety platform a building block (generic product, independent of the application) made of hardware and base software (firmware and/or operating system and/or support tools), which can be used for building more complex systems (generic applications, i.e. classes of applications). Its safety acceptance and approval shall be carried out on the basis of a ‘generic product’ (i.e. independent of the application) safety case, as specified by standard ENV 50129.\nAn asterisk (*) indicates that initially a European standard for the interface will not be available.\nModule H2 can be applied only when a sufficient degree of confidence in the ERTMS technologies exists through return of experience from commercial installations.\n1\n2\n2a\n3\n4\n5\n6\nGroup No\nInter-operability constituent (IC)\nRemarks\nControl-command interfaces\nInterfacing TSI subsystems\nCharacteristics to be assessed by reference to Annex A\nModule\n1\nERTMS/ETCS on-board\n(Part of the UNISIG grouping of on-board ICs)\n(a) *Odometry\n(b) External STM\n(c) ERTMS/GSM-R on-board\n(d) *Safety information recorder\n(e) Euroloop (trackside)\n(f) Eurobalise (trackside)\nRolling stock (see section 4.2 TSI control-command)\n0a, 1, 2, 3, 4a, 5, 6, 7, 9, 10, 12a, 12b, 13, 17, 18\nH2 or B with D or B with F\n2\nSafety platform on-board\n(Part of the UNISIG grouping of on-board ICs)\nNot applicable\nNot applicable\n1, 2a, 2b\nH2 or B with D or B with F\n3\nSafety information recorder\n(Part of the UNISIG grouping of on-board ICs)\n(a) *ERTMS/ETCS on-board\n(b) *ERTMS/GSM-R on-board\n(c) Safety information downloading tool (not being a control-command IC).\nOperational issue: recording of safety information\n0, 1, 2, 3, 4a, 9, 13b\nH2 or B with D or B with F\n4\nOdometry\n(Part of the UNISIG grouping of on-board ICs)\n*ERTMS/ETCS on-board\nRolling stock (see section 4.2 TSI control-command)\n0a, 1, 2, 3, 4a, 8, 13c, 17, 18\nH2 or B with D or B with F\n5\nExternal STM\nInterfaces only\nERTMS/ETCS on-board\nRolling stock (see section 4.2 TSI control-command)\n0a, 1, 2, 3, 4a, 6\nH2 or B with D or B with F\n6\nERTMS/GSM-R on-board\nIncluding radio MMI\n(a) ERTMS/ETCS on-board\n(b) ERTMS/GSM-R trackside\n(c) *Safety information recorder\nRolling stock (see section 4.2 TSI control-command)\nand operational issues:\nradio operational requirements,\ndrivers cab ergonomics,\noperational rules,\noperational language,\nrecording of safety information.\n0b, 2, 3, 4a, 11, 12c, 13a, 17\nH2 or B with D or B with F\nTable 5.1b\nGroups of interoperability constituents in the on-board CC assembly\nThis table is an example to show the structure. Other groups may be proposed.\nModule H2 can be applied only when a sufficient degree of confidence in the ERTMS technologies exists through return of experience from commercial installations.\n1\n2\n2a\n3\n4\n5\n6\nGroup number\nBasic inter-operability constituents (Basic ICs)\nRemarks\nCC interfaces\nInterfacing TSI subsystems\nCharacteristics to be assessed by reference to Annex A\nModule\n1\n(a) Safety platform on-board\n(b) ERTMS/ETCS on-board\n(c) Safety information recorder\n(d) Odometry\n(UNISIG grouping of on-board ICs)\n(a) External STM\n(b) ERTMS/GSM-R on-board\n(c) Euroloop (trackside)\n(d) Eurobalise (trackside)\n(e) Safety information downloading tool\nRolling stock (see section 4.2 TSI control-command)\nand operational issues:\nradio operational requirements,\ndriver's cab ergonomics,\noperational rules,\noperational language,\nrecording of safety information.\n0a, 1, 2, 3, 4a, 5, 6, 7, 8, 9, 10, 12a, 12b, 13, 17, 18\nH2 or B with D or B with F\nTable 5.2a\nBasic interoperability constituents in the trackside CC assembly\nAn asterisk (*) indicates that initially a European standard for the interface will not be available.\nModule H2 can be applied only when a sufficient degree of confidence in the ERTMS technologies exists through return of experience from commercial installations.\n1\n2\n2a\n3\n4\n5\n6\nNumber\nInter-operability constituent (IC)\nRemarks\nCC interfaces\nInterfacing TSI subsystems\nCharacteristics to be assessed by reference to Annex A\nModule\n1\nERTMS/ETCS trackside\n(RBC)\n(a) ERTMS/ETCS trackside (neighbour RBC)\n(b) ERTMS/GSM-R trackside\n0a, 1, 2, 3, 4a, 5, 14a, 14d, 18\nH2 or B with D or B with F\n2\nEurobalise\n(a) ERTMS/ETCS on-board\n(b) LEU (Eurobalise)\nInfrastructure\n0a, 1, 2, 3, 4a, 12a, 14b\nH2 or B with D or B with F\n3\nEuroloop\n(Part of the UNISIG grouping of trackside ICs)\n(a) ERTMS/ETCS on-board\n(b) *LEU (Euroloop)\nInfrastructure\n0a, 1, 2, 3, 4a, 12b, 14c\nH2 or B with D or B with F\n4\nLEU (Eurobalise)\nInterface C and coding strategy only\nEurobalise (trackside)\n0a, 1, 2, 3, 4a, 12a, 14b\nH2 or B with D or B with F\n5\nLEU (Euroloop)\n‘Interface C’ and coding strategy only (Part of the UNISIG grouping of trackside ICs)\n*Euroloop (trackside)\n0a, 1, 2, 3, 4a, 12b, 14c\nH2 or B with D or B with F\n6\nSafety platform trackside\nNot applicable\nNot applicable\n1, 2a, 2b\nH2 or B with D or B with F\nTable 5.2b\nGroups of interoperability constituents in the trackside CC assembly\nThis table is an example to show the structure. Other groups may be proposed.\nModule H2 can be applied only when a sufficient degree of confidence in the ERTMS technologies exists through return of experience from commercial installations.\n1\n2\n2a\n3\n4\n5\n6\nGroup number\nBasic interoperability constituents (basic ICs)\nRemarks\nCC interfaces\nInterfacing TSI subsystems\nCharacteristics to be assessed by reference to Annex A\nModule\n1\n(a) Safety platform trackside\n(b) Eurobalise\n(c) LEU (Eurobalise)\nERTMS/ETCS on-board\nInfrastructure\n0a, 1, 2, 3, 4a, 12a\nH2 or B with D or B with F\n2\n(a) Safety platform trackside\n(b) Euroloop\n(c) LEU (Euroloop)\nERTMS/ETCS on-board\nInfrastructure\n0a, 1, 2, 3, 4a, 12b\nH2 or B with D or B with F",
  "extent": "E+W+S+N.I.",
  "status": null,
  "version": "current",
  "annotations": [
    {
      "type": "footnote",
      "label": "f1",
      "text": "Definition of safety platform a building block (generic product, independent of the application) made of hardware and base software (firmware and/or operating system and/or support tools), which can be used for building more complex systems (generic applications, i.e. classes of applications). Its safety acceptance and approval shall be carried out on the basis of a ‘generic product’ (i.e. independent of the application) safety case, as specified by standard ENV 50129."
    }
  ],
  "outstanding_effects": [],
  "provenance": {
    "source": "legislation.gov.uk",
    "source_url": "https://www.legislation.gov.uk/eudn/2002/731/annex/division/5/division/5.2",
    "retrieved_at": "2026-11-01T15:18:30.359571+00:00"
  },
  "licence": "Open Government Licence v3.0",
  "licence_url": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
  "attribution": "Contains public sector information licensed under the Open Government Licence v3.0. Source: legislation.gov.uk, The National Archives."
}