Modelling Lineside Electronic Units (ETCS L1)

Background

For including ETCS Level 1 in the railML 3 data model, the need for modelling Lineside Electronic Units (LEU) was discussed. In particular, the following requirements have been collected:

  1. An infrastructure element for the LEU is needed.
  2. A LEU should be able to connect with one or more signals.
  3. A LEU should be able to connect with one or more balise groups.
  4. A LEU should be able to connect with one or more balises.
  5. A LEU should be able to connect with one or more euroloops.
  6. The signal aspects to be evaluated by the LEU should be provided.
  7. For each signal aspect to be evaluated by the LEU, the relevant route should be provided
  • target signal of the movement authority
  • required position of passed switches
  • signals between start and target signal of the route (optional)

Proposed solution railML 3.3

  • Introduce a new functional infrastructure element \\linesideElectronicUnitIS within its container \\linesideElectricUnitsIS.
  • Define repeatable child element \\linesideElectronicUnitIS\connectedToSignal with attribute @ref to link from LEU to signal. linesideElectronicUnitIL shall refer with one element [0..*] to SignalIL/hasLamp [#548 (comment 9679)]
  • Define repeatable child element \\linesideElectronicUnitIS\connectedToBaliseGroup with attribute @ref to link from LEU to balise group.
  • Define repeatable child element \\linesideElectronicUnitIS\connectedToBalise with attribute @ref to link from LEU to (single) balise.
  • Define repeatable child element \\linesideElectronicUnitIS\connectedToEuroloop with attribute @ref to link from LEU to euroloop.
  • Introduce a new interlocking element \\linesideElectronicUnitIL with child element \\refersTo to link \\linesideElectronicUnitIS.
  • Define repeatable child element \\linesideElectronicUnitIL\evaluatesSignalAspect with attribute @ref to link a signal aspect that shall be evaluated by the LEU.
Edited by CO Onto