Natural hazards detection (area)

Description

It shall be possible to model areas where technical systems for natural hazard detection are installed. These systems may generate alarms and trigger reactions in an Integrated Traffic Management System.

Background

The railML use case working group "ITMS" discussed about the requirements for modelling natural hazard detection systems in their meeting on October 9, 2020 (see [https://www.railml.org/en/event-reader/railml-is-itms-telco-2020-10-09.html]).

The solution should be generic for any kind of natural hazards (sand, rocks, avalanche, camels, reindeer...).

Links

• Forum discussion:
  • Christian Rahmig, 18.01.2021: [https://www.railml.org/forum/index.php?t=msg&th=791&start=0&]
• Trac tickets:
  • #422 (closed)
• Wiki documentation:
  • use case "Integrated Traffic Management System" (ITMS): [https://wiki3.railml.org/wiki/UC:IS:IntegratedTMS], [https://wiki3.railml.org/wiki/UC:TT:IntegratedTMS]

Proposed solution in railML 3.2

A new functional infrastructure element <detector> shall be introduced with the following attributes:

• @detects describes the type of hazard to be detected by the detector (open enumeration list: "avalanche", "sand", "reindeer", ...)
• @linkedWith allows to link the detector with a <restrictionArea> that defines a certain operational reaction on the detected hazard, e.g. "noStopping".

Further, it is discussed whether to introduce <protectionSystem> as a new functional infrastructure element. It can be used to model e.g. fences along the track. Attributes:

• @protectsAgainstHazard specifies the hazard for which the protection system has been build.

The timetable, rollingstock and further dimensions of natural hazard detection still need to be analysed.