This deliverable has the objective to define a mathematical model for an optimised real-time management of railway traffic under Moving Block (MB). The formulated real-time traffic management model contains: i) a core module for the detection and the sub-optimal resolution of track occupation conflicts under MB and ii) a non-vital module for providing early-warning predictions of potentially hazardous MB traffic situations. The proposed real-time traffic management model includes a mathematical translation of requirements and constraints identified for both MB signalling within WP2 (namely deliverables D2.1 and D2.2) and the GNSS localisation and train integrity devices within WP3 (i.e. deliverables D3.1 – D3.3). An extensive literature review on real-time traffic management models and algorithms shows that so far research efforts have mainly focused on fixed-block and distance-to-go railway operations. Significant gaps still exist in the modelling of MB train operations, despite an increasing number of research works on MB signalling technology is observed since year 2003. A modelling gap analysis is here performed which indicates the need of enhancing existing real-time traffic management algorithms to better align them to the MB concept in terms of infrastructure representation and speed-headway functional dependency. To this end, the RECIFE-MILP real-time traffic management algorithm is enhanced. On one hand a finer infrastructure discretisation is implemented to offer a more suitable track representation under moving block which no longer uses fixed block sections. On the other hand, two different speed levels (namely maximum speed and scheduled speed) are introduced enabling a speed-dependent headway computation in either nominal or delayed traffic scenarios, thereby overcoming the limitation of speed-independent headways, typical of fixed-block traffic rescheduling models. A non-vital early-warning prediction model of hazardous MB traffic conditions is also proposed which includes a short- and a medium-term hazard identification method. In the short-term, potentially hazardous MB traffic condition are identified as violations of safety-critical threshold values of design variables relating to MB train operations (e.g. driving reaction times), the GNSS system (e.g. GNSS error or latency) and/or the GSM-R layer (e.g. MA communication delay). Safety-critical thresholds of the different design variables are identified by means of an extensive sensitivity analysis which uses a Stochastic Activity Network built for MB within WP2. In the medium-term warnings of potentially hazardous MB conditions are instead triggered whenever RECIFE-MILP detects track occupation conflicts in geographical areas with limited GNSS and/ or GSM-R signal availability, such as deep valleys or tunnels. The defined models contribute to the definition of an optimised automated Traffic Management System for Moving Block which can also support traffic dispatchers in preventively avoiding the occurrence of potentially dangerous MB traffic conditions. @en

This deliverable contains the output of the activities performed for Task 4.3 “Guidelines on integrated traffic management architectures for safe and optimised moving-block operations” of the EC Shift2Rail PERFORMINGRAIL project. A real-time model for Moving Block traffic conflict detection and resolution is mathematically specified based on the formulation introduced in Deliverable D4.1. A mathematical formulation of the RECIFE-MILP rescheduling tool extended for Moving Block rail operations is reported together with a detailed description of the objective function and constraints. The proposed MB traffic conflict detection and resolution model is then verified for a given network layout and compared to the original RECIFE-MILP formulation for fixed-block to assess modelling and performance impacts of introduced MB constraints. A validation has successively investigated the applicability and effectiveness of the proposed MB traffic management algorithm by testing it on two real railway networks in France (Gonesse junction and a portion on the Paris-Le Havre line) for different traffic scenarios. The validation experiment shows that with respect to fixed-block, Moving block can reduce delay propagation especially: i) for junctions where trains are not stopping, ii) in denser peak-hour traffic and iii) when train rerouting decisions are taken. A detailed description is the provided for the early-warning MB hazard prediction modules introduced in PERFORMINGRAIL Deliverable D4.1. A specification of input/output data and main functionalities is reported together with practical examples illustrating the usefulness of those modules in mitigating potential MB safety risks in the short and medium term. A functional TMS architecture is then defined for a safe and optimised real-time management of MB traffic operations. Guidelines are outlined for the different functional TMS modules, specifying input/output data, main functionalities and interactions with other components within and without the TMS. A set of recommendations is eventually provided to support both science and the industry in further development and implementation of functional modules and an advanced TMS architecture for MB rail traffic. Recommendations particularly refer to novel modules introduced in PERFORMINGRAIL, namely the MB conflict detection and resolution and the early-warning MB hazard prediction models. In addition, indications are given for further development and practical implementation of the proposed functional TMS architecture for safe and optimised MB railway operations. The main highlighted points regard the need of interfacing current Traffic Monitoring systems with satellite-based train location systems as the removal of track-side train detection will compromise the use of existing train describers. That also leads to then necessity of the TMS architecture to include proposed modules for early-warning hazard prediction to mitigate safety risks which can arise for MB in locations with compromised GNSS or GSM-R signal availability. Another essential recommendation refers to data interface standardisation to enable seamless communication among functional modules within the TMS and with external supporting systems.@en