TCR Tool and ECMT – Fusion 2024

Development of TCR Tool and ECMT and migration their data from legacy applications With the Timetable and Capacity Redesign – or ‘TTR for Smart Capacity Management’ – a market-oriented, efficient, digitalised and competitive capacity management process will be introduced to serve both passenger and freight market needs. The program aims to provide the market with more flexibility and promote better cooperation between all involved stakeholders across two phases: Advance Capacity Planning and Timetabling. To achieve these improvements and ensure smooth communication in this complex environment, the timetabling process must be supported by European and national IT systems. The TTR programme is strongly supported by the proposal of the European Commission on the usage of railway infrastructure capacity in the single European railway area. With the change of business processes on the European level, RNE will provide a completely new platform called Digital Capacity Management (DCM) that enables and supports the programme via software products. consists of three main products: • the Temporary Capacity Restrictions Tool (TCR Tool) • the European Capacity Management Tool (ECMT) • the Path Coordination System – Capacity Broker (PCS - CB) The subject of this document is the TCR Tool and ECMT – to be more specific their new major version “Fusion” (final name to be decided). The TCR Tool and ECMT are two different applications, with different governance, code base, database, IT Supplier etc. With the upcoming procurement process, RNE wants to establish a robust, modernized, and user-centric combined product. • TCR Tool (a subset of the current TCR Tool) • Capacity Model (a subset of the current ECMT) • Capacity Supply (a subset of the current ECMT) RNE’s aim is to develop a robust, modular, intuitive, and user-friendly solution, in accordance with the needs of the sector. As such, the product should be based on processes defined by the sector for the management of TCRs and Advance Capacity Planning and should use TAF TAP TSI based messages for automated communication.