Task 2: CCS

Task 2 CCS: Domain Architecture and Release Coordination

The Task is coordinating the CCS harmonization work and the design of the CCS architecture as well as the release of outcomes. The coordination shall ensure timely, complete, coherent and correct input of EU-Rail to CCS harmonization activities, including those related to the change requests to the CCS TSI.

Task 2 OD and Traffic CS work plan and collaboration

The operational harmonization domain is the starting point for the system engineering process in Task 2. The work of the domain connects the needs of the stakeholders to the design process of the operational processes of the future, including the definition of all performance, safety, and efficiency targets.

The operational processes that are designed by the domain will be used to derive the functionality by the system domains. They will also be used to check the completeness and correctness of already existing technical specifications that were created bottom up.

It is the task of the domain to integrate the stakeholder needs of RU and IM into the operational design in a way that allows to harmonize CCS procedures in the interoperable interactions and to harmonize CCS products according to the harmonization scope of the System Pillar.

Task 2 CCS: Domain Traffic Control and supervision

The domain Traffic CS is a core element of the overall CCS functionality. Therefore, the progress with regards to the description of the functionality, the final alignment about interfaces and the interior architecture is a key activity of the System Pillar. The domain now goes into the phase of concrete specification of system and interfaces, requiring a tight collaboration with Task 2 OD.

Task 2 CCS: Domain Train Control and supervision

The Train CS domain is responsible for the onboard CCS system including, besides the ETCS vehicle equipment, also the additional components and functions like ATO (GoA 2), and others from the on board perspective. Close alignment with the work on communication is required to define the interface between FRMCS and the Train CS system.

Task 2 CCS: Domain Computing Environment

The overall task of the computing environment domain is to find solutions to simplify software installation, hardware configuration and life-cycle processes such as upgrades, updates, or replacements with different software products. These solutions can include standardized API(s) related to the runtime environment and/or hardware on which CCS applications are hosted.

Task 2 CCS: Domain Trackside Assets Control & Supervision

The Trackside CS domain is responsible for the specification of the sub systems controlling the trackside objects like points, track vacancy detection, level crossings and others. With this a unified interface between the Traffic CS system and the object controller should ensure the interchangeability between both components.

Task 2 CCS: Domain Transversal Systems

The Transversal Systems domain and its three subdomains provide systems, standard protocols, and data structures for functionalities that are needed on network level and for engineering use cases. The domain responsibilities comprise the definition of engineering and asset data, functional network topologies (maps) and harmonized graphical representation, the provision of asset condition data and technical intervention management, Harmonised Diagnostics for CCS Systems Trackside and Onboard as well as the CCS Configuration Management Trackside and Onboard.