++ :CONTROL-COMMAND--AND--SIGNALLING_lexForm_4
-- :POLARION--WORK--ITEM--OF--TYPE--REFERENCE_lexForm_3
-- :TRAIN--CONTROL--AND--MONITORING--SYSTEM_lexForm_3
++ :APPLICATION--EXECUTION--ENVIRONMENT_lexForm_3
-- :ARCHITECTURE--TRADEOFF--ANALYSIS--METHOD_lexForm_3
++ :AUTOMATIC--TRAIN--OPERATION_lexForm_4
++ :EUROPEAN--GEOSTATIONARY--NAVIGATION--OVERLAY--SERVICE_lexForm_3
-- :SHARED--CYBERSECURITY--SERVICES_lexForm_3
++ :STANDARD--SECURITY--INTERFACE_lexForm_3
-- :SYSTEM--UNDER--CONSIDERATION_lexForm_4
-- :TRAFFIC--MANAGEMENT--SYSTEM_lexForm_5
-- :ADVANCED--SAFE--TRAIN--POSITIONING_lexConcept_2
++ :APPLICATION--EXECUTION--ENVIRONMENT_lexConcept_2
-- :ARCHITECTURE--TRADEOFF--ANALYSIS--METHOD_lexConcept_2
++ :AUTOMATIC--TRAIN--OPERATION_lexConcept_3
++ :BUILDING--BLOCK--CONFIGURATION_lexConcept_2
-- <https://dbpedia.org/property/workItem>
-- <https://en.wikipedia.org/wiki/Work_breakdown_structure>
-- <https://polarion.plm.automation.siemens.com/>
++ :CONTROL-COMMAND--AND--SIGNALLING_lexConcept_3
++ :DISPLAY--COMPUTING--UNIT_lexConcept_5
++ :DISPLAY--COMPUTING--UNIT_lexConcept_6
++ :DISPLAY--HW--CONTROLLER_lexConcept_4
++ :ERA--EXTENDED--CORE--TEAM_lexConcept_2
++ :EUROPEAN--GEOSTATIONARY--NAVIGATION--OVERLAY--SERVICE_lexConcept_2
-- :FUNCTIONAL--APPORTIONMENT_lexConcept_2
++ :INFRASTRUCTURE--MANAGER_lexConcept_3
++ :LAYOUT--ELEMENT--CONTROLLER_lexConcept_7
++ :LAYOUT--ELEMENT--CONTROLLER_lexConcept_8
-- :MANAGEMENT--BY--TRACEABILITY--KANBAN--BASED_lexConcept_2
-- :MDS-----MULTI--DISPLAY--SYSTEM--ALTERNATIVE--NAMING--FOR--TRAIN--DISPLAY--SYSTEM--NOT--YET_lexConcept_7
-- :OMTS-----ON--BOARD--MULTIMEDIA--AND--TELEMATICS--SYSTEM--X2R4--EQUIVALENT--WITH--PASSENGER_lexConcept_7
-- <https://dbpedia.org/page/Arcadia_(engineering)>
-- <https://en.wikipedia.org/wiki/Arcadia_(engineering)>
-- :OPERATIONAL--CAPABILITY_lexConcept_2
-- :PIS-----PASSENGER--INFORMATION--SYSTEM_lexConcept_7
-- :POLARION--WORK--ITEM--OF--TYPE--REFERENCE_lexConcept_2
-- :SHARED--CYBERSECURITY--SERVICES_lexConcept_2
++ :STANDARD--SECURITY--INTERFACE_lexConcept_2
-- :SYSTEM--UNDER--CONSIDERATION_lexConcept_4
-- :TRAFFIC--MANAGEMENT--SYSTEM_lexConcept_4
-- :TRAIN--CONTROL--AND--MONITORING--SYSTEM_lexConcept_2
-- :TRAIN--DISPLAY--SYSTEM--CONTROLLER_lexConcept_5
++ "Accident’ means an unwanted or unintended sudden event or a specific chain of such events which have harmful consequences; accidents are divided into the following categories: collisions; derailments; level crossing accidents; accidents to persons involving rolling stock in motion; fires and others."
-- "‘accident’ means an unwanted or unintended sudden event or a specific chain of such events which have harmful consequences; accidents are divided into the following categories: collisions; derailments; level crossing accidents; accidents to persons involving rolling stock in motion; fires and others; [SOURCE: SPPRAMSS-337 - [Directive (EU) 2016/798] Article 3 Definitions (11) ]"
++ "In the scope of CCS migration, an adaptor is defined as a logical component ensuring compatibility between harmonised SERA and legacy non-SERA components. Its use can be necessary for integrating and operating harmonised SERA components of the System Pillar Reference Architecture in a legacy environment. The purpose of an adaptor is translating information by converting, reducing or enriching data. An adaptor can ingest input from one or multiple components and provide output to one or multiple other components. As a logical component, the adaptor can be implemented in existing legacy systems or in separated to be developed new physical components. Example: An SCI-OP adaptor translates information from a legacy TMS to a harmonised PES and vice versa."
-- "In the scope of CCS migration, an adapter is defined as a logical component ensuring compatibility between harmonised SERA and legacy non-SERA components. Its use can be necessary for integrating and operating harmonised SERA components of the System Pillar Reference Architecture in a legacy environment. The purpose of an adapter is translating information by converting, reducing or enriching data. An adapter can ingest input from one or multiple components and provide output to one or multiple other components. As a logical component, the adapter can be implemented in existing legacy systems or in separated to be developed new physical components. Example: An SCI-OP adapter translates information from a legacy TMS to a harmonised PES and vice versa."
++ "Advanced Safe Train Positioning (ASTP) is a CCS onboard interoperability constituent, separated from the ERTMS/ETCS on-board equipment by fully standardized interfaces with all connected systems. ASTP shall perform functions for safety relevant applications and be the only source of odometry information in the CCS-OB. The main ASTP functionalities interfacing with other onboard systems, are: * provision of Odometry information * identification of all potential virtual Reference Location(s) * provision of 3D kinematic information"
-- "Advanced Safe Train Positioning (ASTP) is a CCS onboard interoperability constituent, separated from the ERTMS/ETCS on-board equipment by fully standardized interfaces with all connected systems. ASTP shall perform functions for safety relevant applications and be the only source of odometry information in the CCS-OB. The main ASTP functionalities interfacing with other onboard systems, are: * provision of Odometry information * identification of all potential virtual Reference Location(s) * provision of 3D kinematic information"
++ "Arc{comment:3}hitecture Analysis & Design Integrated Approach (ARCADIA) is a system and software architecture engineering method based on architecture-centric and model-driven engineering activities. A short description of the method can be found here. Main resources about ARCADIA can be found on the official website: https://www.eclipse.org/capella/arcadia-reference.html ARCADIA uses four layers to develop and model a system: * Operational Analysis - what the users of the system need to accomplish * System Need Analysis{comment:4} - what the system has to accomplish for the user * Logical Architecture - How the system will work to fulfil expectations * Physical Architecture - How the system will be developed and built (image: 3-1-screenshot-20230107-163323.png) Figure {caption:Figure} Figure Four perspectives of Arcadia [Arcadia web : https://www.eclipse.org/capella/arcadia.html ]"
-- "Arc{comment:3}hitecture Analysis & Design Integrated Approach (ARCADIA) is a system and software architecture engineering method based on architecture-centric and model-driven engineering activities. A short description of the method can be found here. Main resources about ARCADIA can be found on the official website: https://www.eclipse.org/capella/arcadia-reference.html ARCADIA uses four layers to develop and model a system: * Operational Analysis - what the users of the system need to accomplish * System Need Analysis{comment:4} - what the system has to accomplish for the user * Logical Architecture - How the system will work to fulfil expectations * Physical Architecture - How the system will be developed and built (image: 3-1-screenshot-20230107-163323.png) Figure {caption:Figure} Figure Four perspectives of Arcadia [Arcadia web : https://www.eclipse.org/capella/arcadia.html ]"
++ "Architecture Tradeoff Analysis Method"
-- "Architecture Tradeoff Analysis Method{comment:4}"
++ "The Area Controller manages areas for the View."
-- "Area Controller The Area Controller manages areas for the View."
-- "Automatic Train Operation is technology for automating the operation of trains. The degree of the automatisation is shown by the Grade of Automatation (GoA). GoA0: train operating on-sight, no automation GoA1: train operating manual, train driver controls starting, stopping, passenger service functions as opening and closing doors and handling emergency. Train protection systems like ETCS L1 in place. GoA2: train operating semi-automatic. Starting and stopping automated using advanced train protection systems like ETCS L2 or 3, driver operates passenger service functions and handles emergencies GoA3: driverless train operation. Starting and stopping automated, service staff operates passenger service functions and handles emergencies GoA4: unattended train operation. All operations are fully automated without any on-train staff"
++ "Device that reads the identity of a person by comparing some attributes of their physiological being or behavioral traits against a sample database. This reader permits the authentication of the actor."
-- "Device that reads the identity of a person by comparing some attribute of their physiological being or behavioral traits against a sample database. This reader permits the authentication of the actor."
-- "Biometric Reader Device that reads the identity of a person by comparing some attribute of their physiological being or behavioral traits against a sample database. This reader permits the authentication of the actor."
++ "Data for a Building Block, see Configuration Update Concept of Transversal."
++ "A BuildingBlock is a logical unit of the system that is bound to a sourceable physical equipment by means of a Basic Data Identifier having: * standardised functionality or aggregates standard functionality it depends on * may have standardised PRAMS requirements (including Tolerable Functional Failure Rate [TFFR] * may have Safety Integrity Levels [SIL] for functions within the system border and Safety Related Application Conditions [SRAC]) * standardised cyber security requirements (including Security Level [SL] based on the security requirements, and Security Related Application Conditions [SRAC]) * may have (on lower levels) standardised interfaces (on all OSI Layers) towards other Building Blocks and/or external systems. One equipment can host several BuildingBlocks (e.g in the case of a MultiObjectController) and may be separately sourceable from different suppliers and capable of being integrated by a third party (integrator). A BuildingBlock is configured by one or more BuildingBlockConfigurations. A BuildingBlock must have an unique identifier called bbId (that could be a technical system or subsystem identifier). The bbIds are assigned by the integrator and are transferred to another physical unit in case of replacement. Each bbId must be unique."
-- "{comment:33} A building block is a sourceable unit of the CCS system (hardware and/or software), having standardised functionality, standardised performance (RAM), standardised safety (including Tolerable Functional Failure Rate [TFFR], Safety Integrity Level [SIL] and Safety Related Application Conditions [SRAC]), standardised security and standardised interfaces towards other building blocks and/or external systems. A building block can also be defined as a standardised module. {comment:158}"
++ "A Hard Key allocated to a dedicated system on a cab. It's designed with a dedicated SIL. It allows a selection from two states and keeps one state as long as it is pressed."
-- "A Hard Key allocated to a dedicated system on a cab. It's designed with a dedicated SIL level. It allows a selection from two states and keeps one state as long as it is pressed."
-- "Button A Hard Key allocated to a dedicated system on a cab. It's designed with a dedicated SIL level. It allows a selection from two states and keeps one state as long as it is pressed."
++ "Electrical device that makes a buzzing noise and is used to provide an audible warning."
-- "Buzzer Electrical device that makes a buzzing noise and is used to provide an audible warning."
++ "The control command and signalling (CCS) system covers signalling, train control, positioning equipment and telecommunications. {comment:1}"
-- "The control command and signalling (CCS) system covers signalling, train control, positioning equipment and telecommunications."
++ "The CCS/TMS Extended ERA Ontology and its derived CCS/TMS Data Model{comment:91} defines the harmonised data language for configuration, communication and diagnostics interfaces within ERJU System Pillar architecture. The Transversal CCS domain is responsible for the specification of the CCS/TMS Data Model in collaboration with * the System Pillar domains, which apply the defined data structures in interface specifications * the Innovation Pillar, which proves the applicability of the data model by incorporating it into flagship program demonstrators."
-- "The CCS/TMS Extended ERA Ontology and its derived CCS/TMS Data Model{comment:91} defines the harmonised data language for configuration, communication and diagnostics interfaces within ERJU System Pillar architecture. The Transversal CCS domain is responsible for the specification of the CCS/TMS Data Model in collaboration with * the System Pillar domains, which apply the defined data structures in interface specifications * the Innovation Pillar, which proves the applicability of the data model by incorporating it into flagship program demonstrators."
++ "A formal request to modify existing software to correct an issue, add new functionality, or comply with updated standards or operational requirements."
-- "PROPOSAL what to change where. Shall normally be linked to an Isse."
++ "Co-operative Shortening of MA is a special procedure between Traffic CS and Train CS to shorten a given Movement Authority."
-- "Co-operative Shortening of MA is a special procedure between Traffic CS and Train CS to shorten a given Movement Authority.{comment:15}{comment:27}{comment:35}"
**++ "Physical Computing Elements and network hardware."
**-- "Physical Computing Elements and network hardware"
**++ "Provides platform-level services (e.g., resource allocation, compartment execution environment)."
**-- "provides platform-level services (e.g., resource allocation, compartment execution environment)."
++ "The Computing Platform provides and manages computing resources and communication resources for functional systems (specialised IO are not included). It contains CP hardware (physical computing element(s) and communication hardware) and CP software (virtualisation environment and platform management). Note: The CP shows an abstract view and may contains several PCEs."
-- "The Computing Platform provides and manage computing resources and communication resources for functional systems (specialised IO are not included). It contains CP hardware (physical computing element(s), communication hardware) and CP software ( virtualisation environment and platform management)."
++ "The (CCS/TMS) Configuration Data refers to a conglomerate of different configuration data required for CCS/TMS systems. These can be broadly classified as SPT2TS-127773 - Application Configuration Data, SPT2TS-127774 - System Configuration Data and SPT2TS-127775 - Software Configuration Data. CCS/TMS Configuration Data is provided via the configuration interface to the CCS/TMS Systems. The configuration data is assumed static within a version and changes occur only when there is a version change or increase, opposite to dynamic data, which may change within a configuration version of the system."
-- "The (CCS/TMS) Configuration Data refers to a conglomerate of different configuration data required for CCS/TMS systems. These can be broadly classified as SPT2TS-127773 - Application Configuration Data and SPT2TS-127774 - System Configuration Data. CCS/TMS Configuration Data is provided via the configuration interface to the CCS/TMS Systems. The configuration data is assumed static within a version and changes occur only when there is a version change or increase, opposite to dynamic data, which may change within a configuration version of the system."
++ "A consist is a rail vehicle or a sequence of coupled rail vehicles."
-- "A consist is a rail vehicle or a sequence of coupled rail vehicles. {comment:11}{comment:46}"
++ "The Controller Unit is a hardware component which embeds logical controller(s). There may be only one Hardware or distributed to several HMI Elements.{comment:54}"
-- "The Controller Unit is a hardware component which embeds logical controller(s). There may be only one Hardware or distributed to several HMI elements."
++ "The Controller Unit is a hardware component which embeds logical controller(s). There may be only one Hardware or distributed to several HMI elements."
-- "Controller Unit The Controller Unit is a hardware component which embeds logical controller(s). There may be only one Hardware or distributed to several HMI elements."
++ "Coupling speed is appropriated speed for a successful coupling. It is determined by the vehicle manufacturer in cooperation with the Railway Undertaking to avoid damages during coupling as well as an unnecessary slow approach.{comment:3}"
-- "Coupling speed is appropriated speed for a successful coupling. It is determined by the vehicle manufacturer in cooperation with the Railway Undertaking to avoid damages during coupling as well as an unnecessary slow approach.{comment:25}{comment:97}{comment:3}"
++ "* The DAC CU is currently not installed in the couplers due to issues related to acceleration and vibration. * DAC CU could manage uncoupling command. * The DAC CU itself should also be standardized, especially concerning the junction interface. Suppliers are currently being consulted to deliver a standardized solution, rather than custom components, to ensure future plug-and-play compatibility. This standardization is essential to ensure safety features are maintained and aligned with SIL2 expectations."
-- "* The DAC CU is currently not installed in the couplers due to issues related to acceleration and vibration. * DAC CU could manage uncoupling command. * The DAC CU itself should also be standardized, especially concerning the junction interface. Suppliers are currently being consulted to deliver a standardized solution, rather than custom components, to ensure future plug-and-play compatibility. This standardization is essential to ensure safety features are maintained and aligned with SIL2 expectations."
++ "The external actor Data Preparation is responsible to prepare (import, validate, and compile) SPT2TS-127779 - Configuration Data for application in CCS Systems. This could be on the IM, RU, Supplier or integrator level. Note: The required engineering data and linked rules for data preparation need to be allocated to this external actor. In addition, the interface between an Engineering Process and a Repository is specified in System Pillar TCCS/CONEMP. Consequently, the output or result of a tool-support engineering process is standardized for the configured CCS/TMS systems."
-- "The external actor Data Preparation is responsible to prepare (import, validate, and compile) SPT2TS-127779 - Configuration Data for application in CCS Systems. This could be on the IM, RU, Supplier or integrator level. Note: The required engineering data and linked rules for data preparation need to be allocated to this external actor. In addition, the interface between an Engineering Process and a Repository is specified in System Pillar TCCS. Consequently, the output or result of a tool-support engineering process is standardized for the configured CCS/TMS systems."
-- "Definition: * The Pass Movement Event Constraint define a point in time that must be reached to trigger the DPSGroupState-Request. * The Pass Movement Event Constraint is only calculated, if there is Movement Event of type PASS (Operational Plan Movement) planned between the calculated Pass Position Constraint and the specific DPSGroup. * The Pass Movement Event Constraint replaces the Pass Position Constraint for a specific DPSGroupState-Request."
++ "Desk Area is a location attribute (left, center...) associated to HMI Element for {comment:55}Display Computing Unit to allocate elements to a View."
-- "Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View."
++ "Desk Area is a location attribute (left, center...) associated to HMI Element for MDS Controller to allocate elements to a View."
++ "Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View."
-- "Desk Area Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View."
++ "The Desk Display Area identifies the desk controlled by MDS (in case of multiple cabins controlled only by one MDS such as locomotive or centralised integration)."
-- "The Desk Display Area identifies the desk controlled by TDS (in case of multiple cabins controlled only by one TDS such as locomotive or centralised integration)."
++ "The Desk Display Area identifies the desk controlled by TDS (in case of multiple cabins controlled only by one TDS such as locomotive or centralised integration)."
-- "A Zone displaying a piece of visual information of particular system and defined by a size (in cells) and an absolute position (x ,y, z axes). It is more commonly named Area in this specification."
-- "{comment:88}A Zone displaying a piece of visual information of a particular system and defined by a size (in cells) and an absolute position (x ,y, z axes). It is more commonly named Area in this specification.{comment:125} The Desk Display Area identifies the desk controlled by TDS (in case of multiple cabins controlled only by one TDS such as locomotive or centralised integration).{comment:204}"
++ "{comment:88}A Zone displaying a piece of visual information of a particular system and defined by a size (in cells) and an absolute position (x ,y, z axes). It is more commonly named Area in this specification.{comment:125} The Desk Display Area identifies the desk controlled by TDS (in case of multiple cabins controlled only by one TDS such as locomotive or centralised integration).{comment:204}"
-- "Desk Display Area A Zone displaying a piece of visual information of particular system and defined by a size (in cells) and an absolute position (x ,y, z axes). It is more commonly named Area in this specification."
++ "Inside a cab, the set of operating controls*, which is dedicated to preferred movements in a given direction (i.e. forward movements, in which visibility from the cab is provided to the driver). Exception: some single cab locomotives are fitted with one single desk, allowing normal movements in both directions. *(set of operating controls: screens, buttons, traction/brake lever, direction controller, radio control, switches, …)"
-- "Inside a cab, the set of operating controls*, which is dedicated to preferred movements in a given direction (i.e. forward movements, in which visibility from the cab is provided to the driver). Exception: some single cab locomotives are fitted with one single desk, allowing normal movements in both directions. *set of operating controls: screens, buttons, traction/brake lever, direction controller, radio control, switches, …"
++ "Inside a cab, the set of operating controls*, which is dedicated to preferred movements in a given direction (i.e. forward movements, in which visibility from the cab is provided to the driver). Exception: some single cab locomotives are fitted with one single desk, allowing normal movements in both directions. *set of operating controls: screens, buttons, traction/brake lever, direction controller, radio control, switches, …"
-- "Inside a cab, the set of operating controls*, which is dedicated to preferred movements in a given direction (i.e. forward movements, in which visibility from the cab is provided to the driver). Exception: some single cab locomotives are fitted with one single desk, allowing normal movements in both directions. *set of operating controls: screens, buttons, traction/brake lever, direction controller, radio control, switches, …Desk"
-- "Desk Inside a cab, the set of operating controls*, which is dedicated to preferred movements in a given direction (i.e. forward movements, in which visibility from the cab is provided to the driver). Exception: some single cab locomotives are fitted with one single desk, allowing normal movements in both directions. *set of operating controls: screens, buttons, traction/brake lever, direction controller, radio control, switches, …Desk"
++ "The Digital Register Infrastructure (DR-I) is a database managing and providing static infrastructure data as central service. The data exchange between Traffic CS and this database is based on the Standard Maintenance Interface SMI-xx (e.g. prepared by EULYNX) via the subsystem Configuration."
-- "The Digital Register Infrastructure (DR-I) is a database managing and providing static infrastructure data as central service. The data exchange between Traffic CS and this database is based on the EULYNX Standard Maintenance Interface SMI-xx via the subsystem Configuration (MDM)."
++ "Computing Hardware that contains {comment:49}a real time operating system, virtualization software and virtual containers for the parallel applications. This hardware shall be generic to be interchangeable.{comment:7}(Software in DCU will be application specific)."
-- "Computing Hardware that contains an real time operating system, virtualization software and virtual containers for the parallel applicactions. This hardware shall be generic to be interchangeable."
++ "Is the interface to the Display Controller and synchronising all status and data informations of all business applications for the Display Units."
-- "Is the interface to the Display HW Controller and synchronising all status and data informations of all business applications for the Display Units."
++ "Glass (LCD) showing pixels without controller."
-- "Display Panel Glass (LCD) showing pixels without controller."
++ "Entity Relationship Model (ER Model or ERM) of entities (Domain Objects) and their relations within the railway Traffic CS domain. Concept: ETPS Specification patterns - Detail, Domain Model, Safety Rules"
-- "ER Model of the objects of the application domain (Traffic CS). Hint: Due to the scope of Traffic CS concepts and specifications, it is located in the Analysis Model. The Design Model is out of interest (left to the supplier) and might have a different Domain Model."
++ "implicit-from-entry-label: Domain Name System"
++ "A Domain Object is an instance of a type of entities from the Domain Model. Entities are part of the Domain Model if they are of interest for Traffic CS. They are usually described by properties which are relevant. Irrelevant properties are not considered. Therefore, it is a model or abstract view on reality. Domain Objects can exist for real-world objects like trains or Trackside Assets and control objects like Movement Permissions."
-- "Object (entity) in the Domain Model."
++ "Waiting time between the arrival and estimated departure time of a train at stop."
-- "Time during which a train is stopped at a Stopping Point, it means the time period between wheel stop and wheel start.{comment:56}"
++ "The emergency treatment is the CCS or TMS decision making tool dealing with trains in relationship to emergency location. The objective is to improve the emergency alarm call in FRMCS using location info allowing immediately to decide about the behavior of trains in or approaching to an area of emergency depending on the positions (topology): trains moving away from the emergency should move on, the MA of trains approaching with enough distance shall switch to an adapted MA (OS or shortened MA / CES), trains approaching with less/not enough distance shall have an unconditional emergency stop (UES).{comment:136}"
-- "The emergency treatment is the CCS or TMS decision making tool dealing with trains in relationship to emergency location. The objective is to improve the emergency alarm call in FRMCS using location info allowing immediately to decide about the behavior of trains in or approaching to an area of emergency depending on the positions (topology): trains moving away from the emergency should move on, the MA of trains approaching with enough distance shall switch to an adapted MA (OS or shortened MA / CES), trains approaching with less/not enough distance shall have an unconditional emergency stop (UES)."
++ "The Engineering Data is the validated data enabling the generation of Configuration Data during product configuration.{comment:146} The Engineering Data (aka Configuration Input Data) is created based on the SPT2TS-125758 - Engineering Input Data but generic (IM-unspecific). Typically, the data are not adapted to cope with specific views demanded by different Consuming Systems. The Engineering Data contains all the base data (i.e., track topology and topography) for deriving the Configuration Data during the compilation process.{comment:147}{comment:145} Besides providing base data for the Configuration Data generation, the Engineering Data shall also cover the needs for the configuration of Consuming Systems (e.g., Parameter Data). The Engineering Data must fulfil engineering rules that are influenced by the requirements of the Configuration Data for the Consuming Systems. The Engineering Data contains only the updated resulting data (i.e., not several variants/versions of the same track) that is needed for the next compiling and provisioning of Configuration Data and operation at a certain point in time in the Consuming Systems.{comment:144}"
-- "The Engineering Data (aka Configuration Input Data) is created based on the SPT2TS-125758 - Engineering Input Data but generic (IM-unspecific). Typically, the data are not adapted to cope with specific views demanded by different Consuming Systems. The Engineering Data contains all the base data (i.e., track topology and topography) for deriving the Configuration Data during the compilation process. Besides providing base data for the Configuration Data generation, the Engineering Data shall also cover the needs for the configuration of Consuming Systems (e.g., Parameter Data). The Engineering Data must fulfil engineering rules that are influenced by the requirements of the Configuration Data for the Consuming Systems. The Engineering Data contains only the updated resulting data (i.e., not several variants/versions of the same track) that is needed for the next compiling and provisioning of Configuration Data and operation at a certain point in time in the Consuming Systems."
++ "Refers to data from Infrastructure Manager (IM) specific digital sources required for engineering, such as: * Track layout (nominal geometry of the respective construction phase * Track Assets (points, signals, train detection elements, etc.) * Properties (speeds, gradients, etc.) * Structures (platform, tunnel, etc.) * Logical data such as trackside train detection sections (if still available) * Acquisition Data * Configuration Data for track objects * Others (placeholder to include other possible data from IM"
-- "Refers to data from Infrastructure Manager (IM) specific digital sources required for engineering, such as: * Track layout (nominal geometry of the respective construction phase * Track Assets (points, signals, train detection elements, etc.) * Properties (speeds, gradients, etc.) * Structures (platform, tunnel, etc.) * Logical data such as trackside train detection sections (if still available) * Acquisition Data * Configuration Data for track objects * Others (placeholder to include other possible data from IM)"
++ "implicit-from-entry-label: ERA Extended Core Team"
++ "Estimated departure time is the predicted time at which a train is expected to start moving. {comment:124}{comment:176} * Note: is there a need to define different times? e.g., published timetable, internal IM/RU working timetable"
-- "Estimated departure time is the predicted time at which a train is expected to start moving. * Note: is there a need to define different times? e.g., published timetable, internal IM/RU working timetable"
++ "implicit-from-entry-label: European Geostationary Navigation Overlay Service"
-- "European Geostationary Navigation Overlay Service, European satellite navigation system"
++ "ETCS - European Train Control System"
-- "European Train Control System (ETCS) is a cab-signalling system that incorporates automatic train protection. (ERA definition)"
++ "Describe the interactions between structural elements by focusing on the exchange of information in a given context and with a time axis. They allow the ordering of information sequences and behaviours of structural elements, but can also be used as a basis for specification tests. Scenarios can be linked to sequence diagrams (SysML wording). Scenarios are suitable to be used for: * Regarding abstractions: operational needs, system analysis, logical architecture, physical architecture * Regarding structural entities: system, subsystem, system element, logical component, actor * Regarding functions: behaviour definition of function (how functions of structural entities exchange data through exchange items) * Regarding other behavioural aspects: pre and post-conditions and invariant as start to end conditions as well as state invariant of the scenario * Regarding purpose: represent, at least, one complete sequence of functional exchanges on a time axis The goal is to visualise system black-box behaviour or system interaction behaviour with actors."
-- "Describe the interactions between structural elements by focusing on the exchange of information in a given context and with a time axis. They allow the ordering of information sequences and behaviours of structural elements, but can also be used as a basis for specification tests. Finally, their constitution, from top to bottom and from right to left, makes it easier to understand the elements described, even for people unfamiliar with an MBSE approach. Scenarios can be linked to sequence diagrams (SysML wording). Scenarios are suitable to be used for the following model elements: * Regarding abstractions: operational analysis, system analysis, logical architecture, physical architecture * Regarding structural entities: system, system element, logical component * Regarding functions: behaviour definition of function (how functions of structural entities exchange data through exchange items) * Regarding other behavioural aspects: pre and post-conditions and invariant as start to end conditions as well as state invariant of the scenario * Regarding purpose: represent, at least, one complete sequence of functional exchanges on a time axis The goal is to visualise system black-box behaviour or system interaction behaviour with actors."
++ "{comment:89} View displayed on more than one Display Panel."
-- "View displayed on more than one Display Panel."
++ "View displayed on more than one Display Panel."
-- "{comment:89} View displayed on more than one Display Panel."
++ "Extended View View displayed on more than one Display Panel."
++ "A button which is not directly managed by MDS."
-- "A button which is not directly managed by TDS."
++ "A button which is not directly managed by TDS."
-- "External Button A button which is not directly managed by TDS."
++ "A FFFIS is the complete definition of an interface between functional or physical entities. The FFFIS includes: - FIS, - Electrical characteristics related to data, - communication protocol, - and including connector and plug. The FFFIS and accompanying documents (e.g. safety analysis) guarantees the interoperability but not the exchangeability of physical entities, see Subset-037 SPT2ARC-1620."
-- "A FFFIS is the complete definition of an interface between functional or physical entities. The FFFIS includes: - FIS, - Electrical characteristics related to data, - communication protocol, - and including connector and plug. The FFFIS and accompanying documents (e.g. safety analysis) guarantees the interoperability but not the exchangeability of physical entities, see Subset-037 SPT2ARC-1620."
++ "Functional apportionment is the clear assignment of functions to subsystems. It is an architectural choice supporting the ability to replace a subsystem of supplier A by a subsystem of supplier B both compliant with a given FIS."
-- "Functional apportionment is the clear assignment of functions to sub-systems. It is an architectural choice supporting the ability to replace a sub-system of supplier A by a subsystem of supplier B both compliant with a given FIS."
++ "A SPPR-3791 - System Requirement which specifies what the system of interest does, i.e. actions or functions that the system of interest must perform. In general, functional requirements capture the required behaviour of the system of interest."
-- "A SPPR-3791 - System Requirement which specifies a function that a system has to do."
++ "A handheld terminal is a portable device used to assist trackside operations. The device communicates with the signalling system and enables an authorised user to manage, such as: * Activating/Deactivating Working areas * Activating/Deactivating Temporary Shunting Areas * Requesting Shunting movements * Requesting movement of Points. The user logs on to the handheld terminal to access functions specific to their role. The use of the handheld terminal is mandatory. Not using the handheld terminal is a fallback scenario which is only permitted in case the terminal is technically unavailable for use. (image: 6-screenshot-20250507-115430-57.png) Image source"
-- "A handheld terminal is a portable device used to assist trackside operations. The device communicates with the Trackside CCS and enables an authorised user to manage:{comment:30} * Working areas * Temporary Shunting Areas * Shunting movements * Points control.{comment:98} The user logs on to the handheld terminal to access functions specific to their role. The use of the handheld terminal is mandatory. Not using the handheld terminal is a fallback scenario which is only permitted in case the terminal is technically unavailable for use.{comment:53}{comment:70} (image: 6-screenshot-20250507-115430-57.png) Image source"
++ "Physical key not part of view. This key can also have a text label or symbol."
-- "Hard Key Physical key not part of view. This key can also have a text label or symbol."
++ "The Hardware Abstraction Interface I2 (Interface 2) provides an abstraction of all technology layers above from the specific hardware used below, enabling easy replaceability of commercial of-the-shelf hardware procurable from a well-sized market of hardware vendors. Note: This is not really an interface, but rather a compatibility list of allowed hardware incl. CPU, memory, etc."
-- "The Hardware Abstraction Interface I2 (Interface 2) provides an abstraction of all technology layers above from the specific hardware used below, enabling easy replace ability of commercial of-the-shelf hardware procurable from a well-sized market of hardware vendors. Note: This is not really an interface, but rather a compatibility list of allowed hardware incl. CPU, memory, etc."
++ "An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key..."
-- "HMI Element An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key..."
++ "Human-System Integration, an interdisciplinary approach that aims at optimising in an early development stage the global system performance by designing solutions adapted for both human and technical system. HSI studies integrates work from multiple human centred domains - process analysis, both qualitative and quantitative, ergonomics, safety, suitability, habitability, skill analysis, training."
-- "Human-System Integration, an interdisciplinary approach that aims at optimizing in an early development stage the global system performance by desgining solutions adapted for both human and technical system. HSI studies integrates work from multiple human centered domains - process analysis, both qualitative and quantitatve, ergonomics, safety, survivability, habitability, skill analysis, training. HSI typically help define user interfaces and lead to workitem SPPR-2246 - Application Condition or SPPR-2244 - Safety related application conditions ."
++ "Incident means any occurrence, other than an accident or serious accident, affecting the safety of railway operations"
-- "‘incident’ means any occurrence, other than an accident or serious accident, affecting the safety of railway operations; SPPRAMSS-337 - [Directive (EU) 2016/798]"
++ "Is a high-level representation of the information needed to describe and/or operate a system. It focuses on concepts, their relationships, and their properties."
-- "An information model is formal documentation for data management. It is a guide to the implementation and use of data."
++ "Infrastructure Data is a detailed digital representation of the railway network that contains all infrastructure related information necessary for planning and performing railway operations, such as infrastructure characteristics, location and details of Field Elements, etc. The Infrastructure Data is static and remains unchanged until intended infrastructure updates occur. Infrastructure data is provided by the RINF represented by ERA ontology to be extended."
-- "Infrastructure Data is a detailed digital representation of the railway network that contains all infrastructure related information necessary for planning and performing railway operations, such as infrastructure characteristics, location and details of Field Elements, etc. The Infrastructure Data is static and remains unchanged until intended infrastructure updates occur."
++ "Infrastructure manager means any body or firm responsible in particular for establishing, managing and maintaining railway infrastructure, including traffic management and control-command and signalling; the functions of the infrastructure manager on a network or part of a network may be allocated to different bodies or firms."
-- "Infrastructure Manager{comment:161}"
++ "Infrastructure Manager{comment:161}"
++ "It contains the minimum software which is needed to start up the FS Compartment and provide a functionality to install the BBC(SW-x) for the FS. This is the BBC (InSW). The initial FS compartment is necessary for remote load of the SW packages which are needed for the operative running mode of the FS compartment."
-- "It contains the minimum software which is needed to start up the FS Compartment and provide a bootloader functionality. This is the BBC (BL) . The bootloader functionality is necessary for remote load of the SW packages which are needed for the operative running mode of the FS compartment."
++ "An Instance is a specific realisation of any entity."
-- "An Instance is a specific realization of any entity."
++ "A shared boundary between two systems or between a system and an actor, that interchange exchange items."
-- "A shared boundary between two systems, that interchange exchange items."
++ "Interlocking is a set of signaling devices which physically materializes, in the area of action of a switch post (junction, crossing of tracks, etc.) throught mechanical, and / or electrical solutions . It allows train movement if the safety conditions have been met regarding train maneuver and signal control devices. (double. needs to be deleted)"
++ "Interlocking is a set of signaling devices which physically materializes, in the area of action of a switch post (junction, crossing of tracks, etc.) throught mechanical, and / or electrical solutions . It allows train movement if the safety conditions have been met regarding train maneuver and signal control devices."
-- "Interlocking is a set of signaling devices which physically materializes, in the area of action of a switch post (junction, crossing of tracks, etc.) throught mechanical, and / or electrical solutions . It allows train movement if the safety conditions have been met regarding train maneuver and signal control devices. (double. needs to be deleted)"
++ "The Internal Button is a button which is managed directly by MDS."
-- "The Internal Button is a button which is managed directly by TDS."
++ "The Internal Button is a button which is managed directly by TDS."
-- "Internal Button The Internal Button is a button which is managed directly by TDS."
++ "Polarion workitem type: Issue. A problem description to be solved in the specification. Can also be an open question, or a generic question, or a point on an agenda."
-- "A problem description to be solved in the specification. Can also be an open question, or a generic question, or a point on an agenda."
++ "Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches."
-- "Key Controller Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches."
++ "Hard Key located close to a Display Area allowing soft key technology."
-- "Lateral Key Hard Key located close to a Display Area allowing soft key technology."
++ "The Layout Controller manages the Layout for an Area."
-- "Layout Controller The Layout Controller manages the Layout for an Area."
++ "The Layout Element Controller manages Layout Elements of a Layout. It knows how to present itself and how to react on events."
-- "The Layout Element Controller manages {comment:90}Layout Elements of a Layout. It knows how to present itself and how to react on events."
++ "The Layout Element Controller manages {comment:90}Layout Elements of a Layout. It knows how to present itself and how to react on events."
-- "Layout Element Controller The Layout Element Controller managesLayout Elements of a Layout. It knows how to present itself and how to react on events."
++ "The Layout Engine is an application and supplier specific piece of software, able to generate any View based on application specific needs."
-- "The Layout Engine is a generic piece of software able to generate any View based on Areas, Layouts and Layout Elements as defined in a configuration."
-- "The Layout Engine is an {comment:86}generic application and supplier specific piece of software, able to generate any View based on application specific needs. Areas, Layouts and Layout Elements as defined in a {comment:91}configuration."
++ "The Layout Engine is an {comment:86}generic application and supplier specific piece of software, able to generate any View based on application specific needs. Areas, Layouts and Layout Elements as defined in a {comment:91}configuration."
-- "Layout Engine The Layout Engine is a generic piece of software able to generate any View based on Areas, Layouts and Layout Elements as defined in a configuration."
**++ "Layout is a list of Layout Elements which is displayed in an area."
**-- "Layout is a list of layout elements which is displayed in an area."
++ "Layout is a list of Layout Elements which is displayed in an area."
-- "Layout Layout is a list of layout elements which is displayed in an area."
++ "LCDF - Last Coupler Detection Function"
-- "- determination of the last one, e-coupler coppled, uncoppled ready or not for coupling, standardize for a SIL2 sensor;"
++ "Device that converts an electrical audio signal into a corresponding sound."
-- "Loudspeaker Device that converts an electrical audio signal into a corresponding sound."
++ "In an M-out-of-N configuration, a functional system consists of N redundant replicas, out of which at least M must be functioning correctly for the overall functional system to operate."
-- "In an M-out-of-N configuration, a functional system consists of N redundant replicas, out of which at least M must be functionating correctly for the overall functional system to operate."
++ "Manual route setting refers to the historical process of manually configuring and establishing train routes within the railway network. This involves selecting and activating specific track paths that trains will follow during their journey. Manual route setting is typically carried out by railway operators or dispatchers in the event that automatic route setting fails. This concept will be replaced in the target system of SERA by Movement Permission, see here: SPT2TRAFFIC-7866 - Movement Permission"
-- "Manual route setting refers to the process of manually configuring and establishing train routes within the railway network. This involves selecting and activating specific track paths that trains will follow during their journey. Manual route setting is typically carried out by railway operators or dispatchers in the event that automatic route setting fails. {comment:45}"
++ "The Microphone Controller manages states and signals of Microphone."
-- "Microphone Controller The Microphone Controller manages states and signals of Microphone."
++ "Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker."
-- "Microphone Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker."
++ "A Movement Permission is a discrete domain object within the ETPS that defines and secures the operational path of a train. It replaces the traditional split between route setting, signalling, and train control by integrating them into one unified concept. Key characteristics: · Geometric Extent: The MP specifies a linear, contiguous section of track (running path) that a train is permitted to occupy, including mandatory safety margins (Risk Buffers, Risk Paths) to prevent collisions. · Basis for Movement Authority: An MP provides the trackside foundation from which an ETCS Movement Authority (MA) is derived and transmitted to the train. · Dynamic & Risk-Based: Unlike fixed interlocking routes, an MP can start and end at any topological point and is defined according to operational needs and real-time safety checks rather than static rules. · Lifecycle: MPs are created upon request, checked against topology and safety conditions, granted, supervised, and continuously updated (extended, shortened, upgraded, or removed). · Integration: By merging route protection and movement granting, the MP enables efficient infrastructure use, reduces unnecessary locking of track elements, and supports flexible, automated operations. Movement Permission is not just an “allowance to proceed” but a dynamic, safety-checked allocation of infrastructure to a specific train movement, forming the essential prerequisite for issuing a Movement Authority in ETCS."
-- "Movement Permissions (MPs) are stored within the trackside safety system. A Movement Permission is an extent of track reserved within the trackside safety system for a particular Train Object to move. A Movement Permission includes all conditions under which the movement of the Train Object can be performed safely. A Movement Permission always refers to exactly one Train Object. A Movement Permission is distinct from a Movement Authority, which is sent from the trackside safety system to the ETCS On-Board."
++ "Articles 13 and 14 of Interoperability Directive define the cases where national rules (NRs) can be notified ant the procedure of notification of national rules by Member States. The applicable national rules (NRs) for vehicle authorisation are recorded in IT tool RDD. In particular, rules for ETCS and GSM-R are listed in section 12 “On-board control command and signaling” in the parameters list defined in Commission Regulation (EU) 2015/2299. The relevant NRs for fixed installation including Control Command and Signaling trackside subsystem have to be notified through SRD tool (i.e. https://www.era.europa.eu/domains/registers/srd_en)"
-- "Articles 13 and 14 of Interoperability Directive define the cases where national rules (NRs) can be notified ant the procedure of notification of national rules by Member States. The applicable national rules (NRs) for vehicle authorisation are recorded in IT tool RDD. In particular, rules for ETCS and GSM-R are listed in section 12 “On-board control command and signaling” in the parameters list defined in Commission Regulation (EU) 2015/2299. The relevant NRs for fixed installation including Control Command and Signaling trackside subsystem have to be notified through SRD tool."
++ "An operational capability is an ability, expected of one or more operational entities. The operational capability provides a service contributing to fulfilling a high-level goal to which one or more operational entities should contribute, and which is likely to influence system definition or usage. It is characterised by a set of operational processes and scenarios describing more precisely the conditions for performing the operational activities that contribute to it. Operational capabilities are similar to use cases. They describe the application of the system from the point of view of the user/operational entity."
-- "An operational capability is an ability given by a group of processes."
++ "The I0 is the sum of all operational interfaces used from Functional Systems (as eg. an RBC) to communicate with other Functional Systems (as eg. an IXL). Examples for these set of interfaces are the Eulynx Interfaces (SCI-xx) or interfaces like Euroradio or TSI-standardised interfaces."
-- "The I0 is the sum of all operational interfaces used from Functional Systems (as eg. an RBC) to communicate with other Functional Systems (as eg. an IXL). Examples for these set of interfaces are the Eulynx Interfaces (SCI-xx) or interfaces like Euroradio or TSI-standardized interfaces."
++ "The Operational Plan is the result of the planning process performed by TMS. An Operational Plan will be issued by the TMS for any operationally relevant activity. This comprises all movements of Physical Train Units incl. shunting operations (Operational Movement), restrictions due to e.g., infrastructure maintenance and construction works, and warning measures during restrictions."
-- "The Operational Plan is the result of the planning process performed by TMS. An Operational Plan will be issued by the TMS for any operationally relevant activity. This comprises all movements of Physical Train Units{comment:86} incl. shunting operations (Operational Movement), restrictions due to e.g., infrastructure maintenance and construction works, and warning measures during restrictions."
++ "Operational requirements are operational needs which an operational procedure and its design has to fulfil. It is a need issued in the context of the operational analysis and may qualify some operational actor, actor property, activity or scenario."
-- "Operational requirements are requirements which an operational procedure and its design has to fulfil. It is a requirement issued in the context of the operational analysis and may qualify some operational actor, actor property, activity or scenario."
++ "Properties of a given piece of track, impacting operations. Non-exhaustive list: * Air tightness * Axle load/Line category * Load type restrictions (e.g. hazardous material, passenger) * Loading gauge restrictions * Low adhesion * Switchable neutral section * Operating regime * Driveability Hint: This includes a track closure. The driveability parameter can be train (category) specific. * Driving on sight * Local Operation Area Hint: A Local Operation Area is meant to be the technical possibility to implement a Temporary Shunting Area via this restriction toolset. * Modes/accepted GoA level * Speed Hint: The Static Speed Profile is not subject of this scenario, only temporary restrictions. * Overhead current restrictions (including restart of operations after a blackout, with not enough power for all trains to start simultaneously) * Prohibitions of usage of brakes * Sanding * Traction type * Wind vulnerability The following track properties are considered to be static properties, which will not be managed with dynamic restrictions, but via the static infrastructure data (Digital Map/Digital Register): * Big Metal Masses * Non-stopping area * Powerless area * Radio hole * Tunnel Stopping Are"
-- "Properties of a given piece of track, impacting operations. Non-exhaustive list: * Air tightness * Axle load/Line category * Load type restrictions (e.g. hazardous material, passenger) * Loading gauge restrictions * Low adhesion * Switchable neutral section * Operating regime * Driveability Hint: This includes a track closure. The driveability parameter can be train (category) specific. * Driving on sight * Local Operation Area Hint: A Local Operation Area is meant to be the technical possibility to implement a Temporary Shunting Area via this restriction toolset. * Modes/accepted GoA level * Speed Hint: The Static Speed Profile is not subject of this scenario, only temporary restrictions. * Overhead current restrictions (including restart of operations after a blackout, with not enough power for all trains to start simultaneously) * Prohibitions of usage of brakes * Sanding * Traction type * Wind vulnerability The following track properties are considered to be static properties, which will not be managed with dynamic restrictions, but via the static infrastructure data (Digital Map/Digital Register): * Big Metal Masses * Non-stopping area * Powerless area * Radio hole * Tunnel Stopping Are"
++ "This interface is used to manage (monitor, control, diagnose, configure) the virtual computing environments."
-- "This interface is used to manage (monitor, control, diagnose, configure) the virtual computing environments. It only exists if a Virtualisation Interface is present. OI is part of I1."
++ "Overlapped is the word used to describe two different objects refering, at least partially, to the same physical part of the track. For example, if a Movement Permission Extent is overlapping a Level Crossing, it means that at least some part of the Movement Permission extent goes over the outer limits of the Level Crossing. The technical description is as follows: Object A is overlapped by Object B (or vice versa) if the following condition is TRUE for at least one LinearElementSection in Object A: { The starting point of the LinearElementSection from Object A is between the starting and ending point of at least one LinearElementSection in Object B with the same LinearElement ID } OR { The ending point of the LinearElementSection from Object A is between the starting and ending point of at least one LinearElementSection B with the same LinearElement ID } OR { The starting point of at least one LinearElementSection from Object B is between the starting and ending point of the LinearElementSection from Object A with the same LinearElement ID }"
-- "Overlapped is the word used to describe two different objects refering, at least partially, to the same physical part of the track. For example, if a Movement Permission Extent is overlapping a Level Crossing, it means that at least some part of the Movement Permission extent goes over the outer limits of the Level Crossing. The technical description is as follows: Object A is overlapped by Object B (or vice versa) if the following condition is TRUE for at least one LinearElementSection in Object A: { The starting point of the LinearElementSection from Object A is between the starting and ending point of at least one LinearElementSection in Object B with the same LinearElement ID } OR { The ending point of the LinearElementSection from Object A is between the starting and ending point of at least one LinearElementSection B with the same LinearElement ID } OR { The starting point of at least one LinearElementSection from Object B is between the starting and ending point of the LinearElementSection from Object A with the same LinearElement ID }"
++ "A patch is a small software update that fixes bugs, security vulnerabilities, or minor issues. It corresponds to the PATCH version in Semantic Versioning (SEMVER), indicating backward-compatible without adding new features (e.g. SPPRAMSS-15261 - Error correction, system improvements, unexpected system behavior)."
-- "A patch is a small software update that fixes bugs, security vulnerabilities, or minor issues. It corresponds to the PATCH version in Semantic Versioning (SEMVER), indicating backward-compatible error corrections without adding new features."
++ "The Plan Execution System is a subsystem of Traffic CS which is responsible for: * processing the Operational Plans provided by the TMS, which are based on the Operating State of the railway within the Area of Control and * providing the Operating State within the Area of Control received from Trackside Protection System towards the TMS."
-- "The Plan Execution System is a subsystem of Traffic CS which is responsible for: * processing the Operational Plans provided by the TMS, which are based on the Operating State of the railway within the Area of Control and * providing the Operating State within the Area of Control received from Trackside Protection System towards the TMS."
++ "Set of interrelated or interacting activities that use inputs to deliver an intended result. * Processes require a purpose and outcome, all processes have at least one activity. * A process defines “WHAT” is to be done, without specifying “HOW” each task is performed."
-- "Set of interrelated or interacting activities that use inputs to deliver an intended result. * Processes require a purpose and outcome, all processes have at least one activity. * A process defines “WHAT” is to be done, without specifying “HOW” each task is performed."
++ "Railway requirements are epics, visions, needs or user stories coming from stakeholders as their concrete vision (who, what, why). It can be formulated in a few sentences and has not a strict form criteria. These can be translated to more precise operational requirements during analysis processes in case they describe operational epics for the business target picture of an operational area (like CCS or energy). The can be freely formulated but should follow the writing patterns of epics and user stories. They should be specific enough to be assigned to exactly one System Pillar task."
-- "Railway requirements are epics, visions, needs or user stories coming from stakeholders as their concrete vision (who, what, why). It can be formulated in a few sentences and has not a strict form criteria. These can be translated to precise operational requirements during analysis processes in case they describe operational epics for the business target picture of an operational area (like CCS or energy). The can be freely formulated but should follow the writing patterns of epics and user stories. They should be specific enough to be assigned to exactly one System Pillar task."
++ "Railway undertaking means any public or private under taking licensed according to this Directive, the principal business of which is to provide services for the transport of goods and/or passengers by rail with a requirement that the undertaking ensure traction; this also includes under takings which provide traction only;"
++ "The Reader Controller manages states and failures of the Biometric Reader and/or the RFID Reader."
-- "The Reader Controller manages states and failures of the Biometric Readerand/or the RFID Reader."
-- "Reader Controller The Reader Controller manages states and failures of the Biometric Readerand/or the RFID Reader."
++ "The concept of reliability centred maintenance is defined in SPPRAMSS-11144 - [IEC 60300-3-11:2009]. Reliability-centered maintenance (RCM) is a concept of maintenance planning to ensure that systems continue to do what their users require in their present operating context. Successful implementation of RCM will lead to increase in cost effectiveness, reliability, machine uptime, and a greater understanding of the level of risk that the organization is managing."
-- "The concept of reliability centred maintenance is defined in SPPRAMSS-11144 - [IEC 60300-3-11:2009]. Reliability-centered maintenance (RCM) is a concept of maintenance planning to ensure that systems continue to do what their users require in their present operating context. Successful implementation of RCM will lead to increase in cost effectiveness, reliability, machine uptime, and a greater understanding of the level of risk that the organization is managing."
++ "Remote control device is a type of electronic device for radio based control of traction units. It allows the train driver to pilot the engine without being present in the cabin. (image: 4-screenshot-20250411-100143-3.png)"
-- "Remote control device is a type of electronic device for radio based control of traction units. It allows the train driver to pilot the engine without being present in the cabin. {comment:92}{comment:93} (image: 4-screenshot-20250411-100143-3.png) {comment:94}"
++ "A Replica is a specific realisation of any entity in a cluster of peers used for composite fail safety and/or availability. Replicas of the same entity always run in distinct Compartments deployed to distinct Computing Elements."
-- "A Replica is a specific realization of any entity in a cluster of peers used for composite fail safety and/or availability. Replicas of the same entity always run in distinct Compartments deployed to distinct Computing Elements."
++ "Radio Frequency Identification (RFID) refers to a wireless system comprised of two components: tags and readers. The reader is a device that has one or more antennas that emit radio waves and receive signals back from the RFID tag. This reader permits the authentication of the actor."
-- "RFID Reader Radio Frequency Identification (RFID) refers to a wireless system comprised of two components: tags and readers. The reader is a device that has one or more antennas that emit radio waves and receive signals back from the RFID tag. This reader permits the authentication of the actor."
++ "The Safe Train Extent represents the extent of the track that may be occupied by a connected train. It is calculated from train-side information (Confirmed Rear End and Max Safe Front End derived from the ETCS Position Report) and track-side information (track vacancy proving sections like track circuits or axle counters), taking into account the most recent information available from these train- and track-side information sources. Remarks: * The Safe Train Extent for a train will be updated when new information becomes available. * For a moving train, it is likely that the train will move outside the Safe Train Extent between update"
-- "The Safe Train Extent represents the extent of the track that may be occupied by a connected train. It is calculated from train-side information (Confirmed Rear End and Max Safe Front End derived from the ETCS Position Report) and track-side information (track vacancy proving sections like track circuits or axle counters), taking into account the most recent information available from these train- and track-side information sources. Remarks: * The Safe Train Extent for a train will be updated when new information becomes available. * For a moving train, it is likely that the train will move outside the Safe Train Extent between update"
++ "The aim of introducing Safety Platform Independence Interface I5 (Interface 5), is to be able to implement platform independent Safe Functional Applications (up to SIL4) i.e., applications, based on a generalised abstraction between the application logic and the system interfaces, that will run unchanged on different platform implementations."
-- "The aim of introducing Safety Platform Independence Interface I5 (Interface 5), is to be able to implement platform independent Safe Functional Applications (up to SIL4) i.e., applications, based on a generalized abstraction between the application logic and the system interfaces, will run unchanged on different platform implementations."
++ "An implementation, as part of an automation control system, either a host device, embedded device, network device or software application on a host device, which realizes subsystem functions, implements security capabilities and consisting of a physical encasing, computing capabilities and network communication, and interfacing to the Shared Cybersecurity Services. Examples of CCS secure components are object controller, trackside cabinet, IXL rack, ATO-OB, OBU, ATO-TS, IXL/RBC combination, shared cybersecurity services, security proxy for legacy devices, …) Examples of components which are not meeting the definition of a Secure Component are components with no network communication, e.g. directly connected sensors or displays."
++ "The SERA Phase is a deployment phase, which starts when the SERA Target - comprising all SERA Enablers (refer to SERA Enablers list in Glossary) - is ready (i.e. tested and approved) for implementation (rollout) in projects. The key SERA Enabler will be the moving block with the DTCC safety principle (either implemented with GSL or CBTC based solutions){comment:1258} based on the harmonized operation concept and related rule set. In this context the trackside infrastructure is equipped for moving block (allowing TDD reduction) enabling degraded modes and mixed fleet operation (i.e. parallel movement of equipped and non-equipped trains with or w/o safe train length and integrity). Core elements for rollout of the SERA Target are the subsystems ETPS and PES (ATO-TS optional) plus the related process interfaces SCI between them and to the adjacent systems like: * TMS * Operators Workplace * Object Controllers. Additionally, also adjacent auxiliary systems and related interfaces SDI, SMI, SSI plus related tools (e.g. for engineering, testing, simulation) must be available as well. For example, these auxiliary systems are: * Central services, which provide supporting functions for operation of the core systems: configuration, maintenance and digital register-infrastructure, security, communication."
-- "The SERA Phase is a deployment phase, which starts when the SERA Target - comprising all SERA Enablers (refer to SERA Enablers list in Glossary) - is ready (i.e. tested and approved) for implementation (rollout) in projects. The key SERA Enabler will be the moving block with the DTCC safety principle (either implemented with GSL or CBTC based solutions){comment:1258} based on the harmonized operation concept and related rule set. In this context the trackside infrastructure is equipped for moving block (allowing TDD reduction) enabling degraded modes and mixed fleet operation (i.e. parallel movement of equipped and non-equipped trains with or w/o safe train length and integrity). Core elements for rollout of the SERA Target are the subsystems ETPS and PES (ATO-TS optional) plus the related process interfaces SCI between them and to the adjacent systems like: * TMS * Operators Workplace * Object Controllers. Additionally, also adjacent auxiliary systems and related interfaces SDI, SMI, SSI plus related tools (e.g. for engineering, testing, simulation) must be available as well. For example, these auxiliary systems are: * Central services, which provide supporting functions for operation of the core systems: configuration, maintenance and digital register-infrastructure, security, communication."
++ "Serious accident means any train collision or derailment of trains resulting in the death of at least one person or serious injuries to five or more persons or extensive damage to rolling stock, the infrastructure or the environment, and any other accident with the same consequences which has an obvious impact on railway safety regulation or the management of safety; ‘extensive damage’ means damage that can be immediately assessed by the investigating body to cost at least EUR 2 million in total."
-- "‘serious accident’ means any train collision or derailment of trains resulting in the death of at least one person or serious injuries to five or more persons or extensive damage to rolling stock, the infrastructure or the environment, and any other accident with the same consequences which has an obvious impact on railway safety regulation or the management of safety; ‘extensive damage’ means damage that can be immediately assessed by the investigating body to cost at least EUR 2 million in total; [SOURCE: SPPRAMSS-337 - [Directive (EU) 2016/798] Article 3 Definitions (12) ]"
++ "The{comment:65} Service Function Configuration System is used to configure BuildingBlockConfigurations on BuildingBlocks consistently according to an explicit dependency tree. If a new Top-Level version is chosen in a distribution job the difference of the dependency trees are calculated. The installation runs through different steps, such as Preloading, Deactivation of incompatible (safe) BuildingBlockConfigurations, Activation (Installation) and Commit.It includes a small safe function called SafeConfigurationAuthority (SCA). The details are described in Logical Concept for Configuration (SMI V3)."
-- "The{comment:65} Service Function Configuration System is used to configure BuildingBlockConfigurations on BuildingBlocks consistently according to an explicit dependency tree. If a new Top-Level version is chosen in a distribution job the difference of the dependency trees are calculated. The installation runs through different steps, such as Preloading, Deactivation of incompatible (safe) BuildingBlockConfigurations, Activation (Installation) and Commit.It includes a small safe function called SafeConfigurationAuthority (SCA). The details are described in Logical Concept for Configuration (SMI+)."
++ "A collection of standard security interfaces (SSIs) of central security functions accessible for all Secure Components in the automation solution. The realization of the Shared Cybersecurity Services (SCS) implements the requirements of the Secure Component Specification as they are considered as Secure Components as well. The interfaces from Secure Components to Shared Cybersecurity Service are identified by SSI-<service name>. The Shared Cybersecurity Services implementations are identified by SCS-<service name>."
-- "SCS - Shared Cybersecurity Services"
++ "Shunting movement refers to the process of moving railway vehicles (such as locomotives, passengers carriages, or freight wagons) within a rail yard or between tracks, typically for the purpose of assembling trains, repositioning vehicles, or preparing them for departure. Shunting movements are essential for the efficient management of rail operations. Shunting movements can be classified into two categories: supervised shunting and unsupervised shunting. See also reference SPLI-1040 - SHUNTING MOVEMENT and SPLI-1796 - Shunting movement"
-- "Shunting movement refers to the process of moving railway vehicles (such as locomotives, passengers carriages, or freight wagons) within a rail yard or between tracks, typically for the purpose of assembling trains, repositioning vehicles, or preparing them for departure. Shunting movements are essential for the efficient management of rail operations. Shunting movements can be classified into two categories: supervised shunting and unsupervised shunting.{comment:10}{comment:32}{comment:99}{comment:62}"
++ "Context-dependent key which consists of a Hard Key with an associated label on the Display Area. When using a soft key technology, the driver action is done via the Hard Key adjacent to the label."
-- "Soft Key Context-dependent key which consists of a Hard Key with an associated label on the Display Area. When using a soft key technology, the driver action is done via the Hard Key adjacent to the label."
++ "Stakeholder requirements are precise requirements of stakeholders for the system of interest. They are derived from stakeholder needs (e.g. railway requirements and the operational analysis) and provide the stakeholder-oriented view of what the system of interest shall achieve."
-- "Stakeholder requirements are precise requirements of stakeholders for the system of interest. They are derived from railway requirements and the operational analysis."
-- "Individual or organisation having a right, share, claim, or interest in a system or in its possession of characteristics that meet their needs and expectations. Note: In the Europe's Rail context, the list of stakeholders is defined by the members of the System Pillar Steering group and their delegates or speakers."
++ "Standard Security Interface as defined by EULYNX / System Pillar"
++ "Subsystems are along systems with standard interfaces on System Level 5. Not to be confused with subsystems in the TSI / interoperability directive. A subsystem is a part of a system, which is not refined any further during the specification task(The term subsystem is used in this document following the referenced architecting standards, it does not correspond to the subsystem definition as in the Interoperability Directive.). It represents a leaf element in the hierarchy of systems-of-systems. A subsystem is defined by the following characteristics: * For each subsystem exists a set of specification documents, that allows a supplier to build that subsystem, ideally without the need for further documentation. * The level of strictness of the specification can be variable: * Interoperable specification: Strict standardisation of all interface aspects that are needed for to systems to fulfil a defined set of operational capabilities together on runtime. * Interchangeable specification: Standardisation of all interface aspects that are needed to exchange one of the systems with the lowest reasonable integration effort. * Core standardisation specification: An interoperable standardisation that defines a guaranteed minimum of interoperability, but allows and gives room for specific and perhaps incompatible extensions that are only used, when all involved systems have them. * Guideline: A recommended specification that can be used as a whole, or can be used partly or changed. * A subsystem can be implemented as software only, as hardware only, as a mixture of both depending on the strictness of the specification (the specification can leave that aspect open). * Each subsystem can be individually tendered to a supplier * Each subsystem can be built individually by a supplier * Each subsystem must be integrated into a system, which includes all necessary test, verification, certification and validation activities."
-- "Subsystems are along systems with standard interfaces on System Level 5. Not to be confused with subsystems in the TSI / interoperability directive. A subsystem is a part of a system, which is not refined any further during the specification task(The term subsystem is used in this document following the referenced architecting standards, it does not correspond to the subsystem definition as in the Interoperability Directive.). It represents a leaf element in the hierarchy of systems-of-systems. A subsystem is defined by the following characteristics: * For each subsystem exists a set of specification documents, that allows a supplier to build that subsystem, ideally without the need for further documentation. * The level of strictness of the specification can be variable: * Interoperable specification: Strict standardisation of all interface aspects that are needed for to systems to fulfil a defined set of operational capabilities together on runtime. * Interchangeable specification: Standardisation of all interface aspects that are needed to exchange one of the systems with the lowest reasonable integration effort. * Core standardisation specification: An interoperable standardisation that defines a guaranteed minimum of interoperability, but allows and gives room for specific and perhaps incompatible extensions that are only used, when all involved systems have them. * Guideline: A recommended specification that can be used as a whole, or can be used partly or changed. * A subsystem can be implemented as software only, as hardware only, as a mixture of both depending on the strictness of the specification (the specification can leave that aspect open). * Each subsystem can be individually tendered to a supplier * Each subsystem can be built individually by a supplier * Each subsystem must be integrated into a system, which includes all necessary test, verification, certification and validation activities."
++ "Physical component which allows a selection of 2 to N states and keeps the state until its position is changed."
-- "Switch Physical component which allows a selection of 2 to N states and keeps the state until its position is changed."
++ "System capabilities define the need to the system of interest to satisfy its stakeholders including how the system capabilities relate to each other and how they relate to actors. It describes the high-level behaviour of a system and its interaction with other involved entities, resulting in a specific, observable outcome. This capability signifies the system's expected ability in delivering services that represents an operational objective. Essentially, a system capability defines a context for system usage, characterised by a set of exchanges scenarios that outline the conditions under which system functions contribute to achieving the objective. Traditional approaches like the ARCADIA method describe system capabilities from the system's perspective. However, we've opted to deviate from this method, focusing on an actor's perspective similar to use cases to suit our needs better. This deviation aims to create a stronger distinction between capability and function and ensure compatibility with SysML. The actor-oriented approach allows the capability to be documented from the perspective of those interacting with the system, enhancing clarity in defining system objectives and functionality. For example, rather than solely focusing on the system's technical aspects, we assess how the system's capabilities meet the needs and objectives of the users or external entities, ensuring comprehensive alignment with stakeholder goals."
-- "Describes the high-level behaviour of a system and its interaction with other involved entities, resulting in a specific, observable outcome. This capability signifies the system's expected ability in delivering services that represents an operational objective. Essentially, a system capability defines a context for system usage, characterised by a set of exchanges scenarios that outline the conditions under which system functions contribute to achieving the objective. Traditional approaches like the ARCADIA method describe system capabilities from the system's perspective. However, we've opted to deviate from this method, focusing on an actor's perspective similar to use cases to suit our needs better. This deviation aims to create a stronger distinction between capability and function and ensure compatibility with SysML. The actor-oriented approach allows the capability to be documented from the perspective of those interacting with the system, enhancing clarity in defining system objectives and functionality. For example, rather than solely focusing on the system's technical aspects, we assess how the system's capabilities meet the needs and objectives of the users or external entities, ensuring comprehensive alignment with stakeholder goals."
++ "The System Configuration data refers{comment:112} to the static data set required to configure systems with primary information before being put into operation. These data are elaborated as SPT2TS-127829 - Parameter Data"
-- "The System Configuration data refers to the static data set required to configure systems with primary information before being put into operation. These data are elaborated as SPT2TS-127829 - Parameter Data"
[...] specify, from the supplier’s perspective, what characteristics, attributes, and functional and performance requirements the system is to possess in order to satisfy stakeholder requirements. As far as constraints permit, the requirements should not imply any specific implementation.
-- "System requirements are precise functional or non-functional requirements for the system of interest that are derived from system analysis or system architecture. They are recursively used on system level and subsystem level, where a subsystem is specified as system.{comment:108}"
++ "The defined scope of components and its interrelation the security analysis and security specifications are made for. The system under consideration is defined in Security Architecture. The red rectangle displays the scope. These are the components in the system under consideration (SuC)."
++ "System under Consideration (from SPPRAMSS-334 - [EN 50129:2018/AC:2019-04])"
-- "The defined scope of components and its interrelation the security analysis and security specifications are made for. The system under consideration is defined in Security Architecture. The red rectangle displays the scope. These are the components in the system under consideration (SuC)."
++ "System under Consideration [SOURCE: SPPRAMSS-4697 - [EN IEC 62443-3-2:2020]]"
-- "System under Consideration (from SPPRAMSS-334 - [EN 50129:2018/AC:2019-04])"
++ "Arrangement of system elements, that together exhibit a stated behaviour or meaning that the individual constituents do not. According to ISO 15288 a system is “a combination of interacting elements organised to achieve one or more stated purposes. “. In terms of this document, a system in black box view is furthermore defined by: * interfaces to actors outside the system, defining the system boundary * at least one function allocated to it A system in white box view can be further refined into (exclusive or): * into a more granular systems, hence making itself to a system of systems * into subsystems on the lowest level of system of systems refinement In both cases, a system is a conceptual entity that aggregates the properties of its constituents but is not the element that defines the properties itself. A system is hence subject to the emerging properties of its constituents. Usage context definitions of term „system“: * Constituent system: according to ISO 21839, a system that forms part of a system of systems * System of interest: according to ISO 21839, a system whose life cycle or properties are under consideration in a given context"
-- "Arrangement of system elements, that together exhibit a stated behaviour or meaning that the individual constituents do not. According to ISO 15288 a system is “a combination of interacting elements organised to achieve one or more stated purposes. “. In terms of this document, a system in black box view is furthermore defined by: * interfaces to actors outside the system, defining the system boundary * at least one function allocated to it A system in white box view can be further refined into (exclusive or): * into a more granular systems, hence making itself to a system of systems * into subsystems on the lowest level of system of systems refinement In both cases, a system is a conceptual entity that aggregates the properties of its constituents but is not the element that defines the properties itself. A system is hence subject to the emerging properties of its constituents. Usage context definitions of term „system“: * Constituent system: according to ISO 21839, a system that forms part of a system of systems * System of interest: according to ISO 21839, a system whose life cycle or properties are under consideration in a given context"
++ "Controller which manages the states and failures of a Touch Panel."
-- "Controller which manages the states and failures of a {comment:92}Touch Panel."
++ "Controller which manages the states and failures of a {comment:92}Touch Panel."
-- "Touch Controller Controller which manages the states and failures of a Touch Panel."
++ "Hardware detecting where the finger touches the panel. Sometimes called Touch Display as well."
-- "Hardware detecting where the finger touches the panel."
++ "Traffic Management System is used to manage the operation of the railway system and to ensure efficient recovery when unexpected traffic disruptions occur."
-- "Traffic Management System (double, needs to be deleted)"
-- "Traffic Management System is used to manage the operation of the railway system and to ensure efficient recovery when unexpected traffic disruptions occur."
++ "Train Control and Monitoring System"
-- "implicit-from-entry-label: Train Control and Monitoring System"
++ "The TDS Controller interacts with systems (CCS, TCMS,CVR...) and manages the Desk Display Area."
-- "TDS Controller is the same as the Display Manager in the new architecture of MDS."
++ "The TDS Controller interacts with systems (CCS, TCMS,CVR...) and manages the {comment:96}Display Area. Check if other TDS Controller still remains. TDS Controller is the same as the Display Manager."
-- "The TDS Controller interacts with systems (CCS, TCMS,CVR...) and manages the Desk Display Area."
++ "The TDS Controller interacts with system (CCS, TCMS,CVR) and manages the Desk Display Area."
-- "The TDS Controller interacts with systems (CCS, TCMS,CVR...) and manages the {comment:96}Display Area. Check if other TDS Controller still remains. TDS Controller is the same as the Display Manager."
++ "Train Display System Controller The TDS Controller interacts with system (CCS, TCMS,CVR) and manages the Desk Display Area."
-- "The TDS Controller interacts with system (CCS, TCMS,CVR) and manages the Desk Display Area."
++ "Train joining is an operational procedure that involves the process of combining two or more separate consists into a single train, possible anywhere on the network. This operation is typically planned in advance as part of the operational plan, whether short-term or long-term."
-- "Train joining is an operational procedure{comment:96} that involves the process of combining two or more separate consists into a single train,{comment:77} possible anywhere on the network. This operation is typically planned in advance as part of the operational plan, whether short-term or long-term.{comment:22} {comment:38} {comment:60}"
++ "The Train Length Master (TLM) is the OTL device located in the driving cab. It is in charge of collecting from all the OTLs{comment:12} information related to the train length. For each OTL, the Train Length Master is expected to receive: * Couplers status of the wagon * Consist ID * Wagon Length It is important to highlight that the couplers status identifies if that node is on the head or in the tail of the train. How the OTL recognizes the couplers status is linked to the LCDF function embedded in the DAC. A similar solution can be implemented in case of classical couplers adoption. Moreover, the TLM shall: * calculate the train length by summing the single lengths received * store the composition of the train by using the vehicle IDs received * store the HoT and the EoT by identifying the IDs of the OTL which have one free coupler The last task of the TLM is to send the information to the TLMF. This list of information is described in [2]. It is trivial that all these information will be managed on channel A and channel B."
-- "The Train Length Master (TLM) is the OTL device located in the driving cab. It is in charge of collecting from all the OTLs{comment:12} information related to the train length. For each OTL, the Train Length Master is expected to receive: * Couplers status of the wagon * Consist ID * Wagon Length It is important to highlight that the couplers status identifies if that node is on the head or in the tail of the train. How the OTL recognizes the couplers status is linked to the LCDF function embedded in the DAC. A similar solution can be implemented in case of classical couplers adoption. Moreover, the TLM shall: * calculate the train length by summing the single lengths received * store the composition of the train by using the vehicle IDs received * store the HoT and the EoT by identifying the IDs of the OTL which have one free coupler The last task of the TLM is to send the information to the TLMF. This list of information is described in [2]. It is trivial that all these information will be managed on channel A and channel B."
++ "Ensuring that a train is in a fit condition to enter service, that the train equipment is correctly deployed and the train composition matches the train's designated route(s). Train preparation also includes technical inspections carried out prior to the train entering service."
-- "Train preparation: Process for ensuring that a train is in a fit condition to enter service, that the train equipment is correctly deployed, and the train composition matches the train's designated route(s). It includes the coupling or decoupling of vehicles, connecting, or disconnecting of pipes, services, cabling, and the indication of a rear end signal. Train preparation also includes brake configuration setting and the inspections, tests, and checks before departure. Note: The movement to get a vehicle in or out of the train composition is a shunting movement."
++ "Train Splitting is an operational procedure that involves the process of separating a train into two or more consists, possible anywhere on the network and normally based on the operational plan as planned splitting. Specific procedures of the Railway Undertaking describe (vehicles specific, e.g., closing of flaps, protection covering against snow) details to perform the splitting. Unplanned splitting needs the communication with the signaller."
-- "Train Splitting is an operational procedure that involves the process of separating a train into two or more consists,{comment:90} possible anywhere on the network and normally based on the operational plan{comment:21}{comment:37} as planned splitting. Specific procedures of the Railway Undertaking describe (vehicles specific, e.g., closing of flaps, protection covering against snow){comment:31} details to perform the splitting. Unplanned splitting needs the communication with the signaller.{comment:57}"
++ "An unplanned speed restriction refers to a temporary reduction in the maximum allowable speed for movements on a specific section of railway track that is not part of the regular operational plan. This restriction may be implemented due to unforeseen circumstances.{comment:1}"
-- "An unplanned speed restriction refers to a temporary reduction in the maximum allowable speed for movements on a specific section of railway track that is not part of the regular operational plan.{comment:101} This restriction may be implemented due to unforeseen circumstances.{comment:1}{comment:20}{comment:51}"
++ "The unsupervised movement is not under the supervision of the CCS system. So, there is no Movement Authority like OS or FS. During this type of movement the Signaller and Driver have the responsibility for ensuring the safety and control of the train in the absence of the supervision by the CCS system."
-- "The unsupervised movement is not under the supervision of the CCS system. During this type of movement the Signaller and Driver have {comment:19} the responsibility for{comment:17} ensuring the safety and control of{comment:18} the train in the absence of the supervision by the CCS system."
++ "Vehicle Data is a detailed definition of the static train/vehicle characteristics used for the parametrisation of the CCS on-board. The parametrisation variables include but are not limited to train data, braking curves and coefficients, operation of service brake, unique ID (NID_ENGINE), operated ETCS levels, odometry system settings, network / bus settings, distance between balise antenna and front end, available traction systems, operated track condition functions, displayed information on DMI, etc.{comment:35}Vehicle data is provided by the ERATV/ RDV represented by ERA ontology to be extended."
-- "Vehicle Data is a detailed definition of the static train/vehicle characteristics i.e., Braking and Traction efforts, rolling coefficients, of the train, wagons, locomotives used for railway operations.{comment:35}"
++ "Vehicle{comment:53} Keeper/Supplier Gateway * The VK/SU gateway is different from FDFT backend according to SPT4DAC-179 - Missing cross-reference. * The VK/SU gateway is dedicated to forward data from the vehicles to the FDFT backends. * The VK/SU gateway is controlled by the FCI, in order to forward data to the right stakeholders at the right time."
-- "Vehicle{comment:53} Keeper/Supplier Gateway * The VK/SU gateway is different from FDFT backend according to SPT4DAC-179 - Missing cross-reference. * The VK/SU gateway is dedicated to forward data from the vehicles to the FDFT backends. * The VK/SU gateway is controlled by the FCI, in order to forward data to the right stakeholders at the right time."
++ "The View Controller aggregates the View, the output devices and the controller of each input device."
-- "The View Controller aggregates the View, the output devices and the controller of each input device. {comment:94}"
++ "The View Controller aggregates the View, the output devices and the controller of each input device. {comment:94}"
-- "View Controller The View Controller aggregates the View, the output devices and the controller of each input device."
++ "Aggregation of Areas{comment:52} required for systems (CCS, TCMS, CVR...). A View can represent Areas of different systems at the same time."
-- "Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can represent Areas of different systems at the same time."
++ "Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can represent Areas of different systems at the same time."
-- "View Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can represent Areas of different systems at the same time."
-- "A view is a filter that restricts the set of data types to a subset that is of interest in the context of a use case. Filtering is by discipline and spatially."
++ "The Virtualisation Interface I3 (Interface 3) is used to provide a standardised interface above the virtualisation layer so that applications or higher platform layers are independent of a specific implementation of the computing hardware."
-- "The Virtualization Interface I3 (Interface 3) is used to provide a standardized interface above the virtualisation layer so that applications or higher platform layers are independent of a specific implementation of the computing hardware."
++ "* Work items examples: “A requirement”, or “a function”, or “a concept aspect” * Work items are objects in the “engineering database” (ALM) that represent the result of a design step. * The structure of the work items is defined by the SEMP process definition documents (overview in the maps) * The master-engineering database is the ALM System (currently Polarion) which contains all work items and their links."