The “Common Business Objectives” and the “Operational Vision” are documents that were decided in the System Pillar Steering Group in November 2022. They gave the direction and task for all specification work in the System Pillar. Specification in this release is directly or indirectly derived from these main policies.

Link to the zip file: Core group

This release contains the documents produced by System Pillar Engineering Environment Team (EET):

• the System Engineering Management Plan, including modelling guidelines
• the Requirements Management Plan
• the Quality Management Plan
• the Configuration Management Plan
• References and Glossary Guidelines

with their annexes and appendix, and

• list of documents types with their templates that need to be used in System Pillar documents.. These documents outline the processes and methods to be used within System Pillar for the creation of models and deliverables.

Link to the zip file: EET

This release contains different types of documents from the System Pillar PRAMS Domain. The first set of documents, defined as “internal”, refers to artefacts that are defined by the PRAMS and intended to be used within System Pillar Domains activities. The second set of documents, defined as “external”, refers to artefacts which aim at enabling an efficient deployment of the System Pillar Reference Architecture. They will be used by stakeholders developing the building block or integrating systems developed according to the System Pillar set of specifications. This release includes new versions of documents produced during SC2.3 contract with extended scope as well as new documents during SC2.4. 

Link to the zip file: PRAMS

The release is implementing the requirements from EU regulations and directives (NIS2, CSA, CRA, RED) and international standards (ISO 27001, IEC 62443, CENELEC TS 50701 / IEC PT 63452). This simplifies achieving compliance to these standards significantly. The requirements are implemented by four main specifications (Secure Component Specification, Secure Communication Specification, Shared Cybersecurity Services Specification, Secure Program Requirements) and seven supporting documents.

Link to the zip file: Security

The goals assigned to the System Pillar Task 1 are:

• Conduct an as-is analysis of the railway system, considering operational, functional, logical & physical assets,
• Identify the pain points for selected operational interaction processes and derive a requirement set reflecting the Common Business Objectives,
• Specify the high-level Business Process Architecture and Operational Design (Organisational needs, Generic automation needs, …) for the (to-be) Railway System,
• Assess migration roadmap of the Tasks 2…n regarding overall Business Process Architecture and Operational Design consistency
• Assign high-level input requirements to lower-level tasks,
• Define requirements for reduction of total cost of ownership.

The Task 1 release is made of reports based on Architecture modeling with Arcadia methods and Capability analysis.

Link to the zip file: Task 1 Railway Architecture

The ARC domain release is made of deliverables from two activities: architecture coordination and release coordination.

Link to the zip file: Task 2 ARC

The documents included in this release are primarily intended for experts with knowledge of the system under consideration, particularly regarding the System Specification.
For an introduction to Traffic CS, please refer to the SPP-28757 – Traffic CS – System Concept V1.5.

Link to the zip file: Task 2 Traffic CS

This SP release contains EU-Rail Trackside Asset Specification, which are a subset of EULYNX Baseline Set 4 Release 4 (SP/EULYNX BL4R4). 

EU-Rail and EULYNX have published a common documentation release EU-Rail Trackside Asset Specification (SP/EULYNX BL4R4). This release has been prepared in close collaboration with the European rail control-command and signalling (CCS) sector under the organisation of EU-Rail System Pillar, bringing the Trackside Assets part of the EULYNX development under technical authority of the EU-Rail System Pillar.

The EU-Rail Trackside Asset Specification is a documentation update release within the EULYNX Baseline Set 4, continuing the development based on previous releases. The primary focus of this release is to incorporate remaining feedback from the industry and reach a stable maturity level on those limited topics were this was not yet fully reached in the previous releases. The release is fully integrated into the EU-Rail System Pillar. All specifications related to trackside assets and transversal functions are applicable for both the current EULYNX architecture and the future rail target architecture, agreed in the framework of the EU-Rail System Pillar, therefore published as a single set of specifications under a common publication by EULYNX and EU-Rail, delivering in total 25 specification documents. The EU-Rail System Pillar takes the role of the technical authority for the documents of the common publication and will ensure their maintenance.

Link to the zip file: Task 2 Trackside Assets

The Train CS domain release covers the topics:

• Multiple Display Concept
• On board modularity and upgradability
• Basic advanced safe train positioning: General system requirements and architecture
  

Link to the zip file: Task 2 Train CS

The present release establishes a coherent technical baseline for the Transversal CCS System (TCCS) under Europe’s Rail, aligned with EN 50126-1 and the SEMP process. It anchors on the ERA CCS/TMS Ontology and the TCCS System Definition, then specifies system requirements for Service Function Diagnostics (SFD), the Configuration Repository, and Service Function Configuration (SFC), complemented by SMI v2→v3 change requests.
A suite of interface specifications—including SDI (Standard Diagnostics Interface) models (XX/DS/GEN/ P), SMI v3 (Standard Maintenance Interface), and the REPO interface formalises data models, protocols, and cryptographic/traceability mechanisms, enabling secure, orchestrated configuration and semantically harmonised diagnostics (OPC UA). The E2E data process (Phases 1–4: preparation, supplier configuration, integration, distribution) operationalises these specifications within CONEMP’s lifecycle asset management concept; the Catalogue of Symbols contains UI visualisation on the same semantic backbone. 

Link to the zip file: Task 2 Transversal

This release provides the system analysis of the Computing Environment. The analysis aims at understanding the system under consideration and its objectives comprehensively. The document will also discuss the scope of the system, including its objectives and the actors or entities involved. 

Link to the zip file: Task 2 Computing Environment

The content of the release of the task 3 CMS/TMS domain for the period 2024-2025 consists of six documents: 

• T3-Interface Specification TMSCCS 

• T3-System Concept_CMS-TMS_HarmScope 

• T3-DCM Messages Specification 

• T3-CMS TMS Variant Analysis Version 2 

• T3-System Concept_CMS-TMS_Federated Model 

• T3 – Federated model – GAP Analysis 

In addition, the following documents can be used to have a wider picture of the context of CMS/TMS and retrieve more information about the Domain scope. These documents support a deeper understanding of the deliverables described above.  

• T3-SystemArchitecture Description 

• T3-CMSRequirements 

• T3-TMSRequirements 

• T3-OperationalEntitiesActorsRole 

• T3-OperationalProcesses 

• T3-SystemConcept

   

• T3-SystemDefinition 

Link to the zip file: Task 3 TMS CMS

This release from Task 4 (DAC/FDFTO) contains a proposal for implementation of a second channel for Train Length and Integrity on freight trains; as well as the description of a concept FDFTO Central Instance to manage and coordinate the software release and data exchange on DAC-equipped trains.

Link to the zip file: Task 4 DAC

Task 5 HERD (Harmonised European Railway Diagnostics) aims to create harmonised diagnostic data use cases and provide guidelines for standardised data exchange, enabling continuous condition monitoring for integrated asset management. 

This work is summarised in the attached document.

Link to the zip file: Task 5 Harmonized Diagnostics