lexicon
type: Lexicon
description: This is an example lexicon
description: Ceci est un exemple de lexique @fr
language: en
publisher: ERJU-SP
source: None
subject: Rail transport
subject: Category:Rail infrastructure
subject: RAILWAY--INFRASTRUCTURE subjConcept
version info: v251007
entry: 1D reference frame
entry: 3D reference frame
entry: ESC
entry: 4-2-17-1---ETCS--SYSTEM--COMPATIBILITY label
entry: A location marker is a marker border on the trackside to indicate a potential En...
entry: A mission is a train movement for a certain purpose without changing the train c...
entry: A perception that has a direct influence on the staff member. The perception can...
entry: A segments is an area of the infrastructure, on which missions are performed. Ro...
entry: Absolute position reference frame
entry: Accident
entry: Accuracy
entry: Actor
entry: Adaptability
entry: Adapted product
entry: Adaptor
entry: Add Train
entry: Advanced Protection System APS
entry: ASTP
entry: ADVANCED--SAFE--TRAIN--POSITIONING--ASTP label
entry: ADVANCED--SAFE--TRAIN--POSITIONING label
entry: (AFARP) - As far as reasonably practicable
entry: Allocation Area
entry: Allocation Body
entry: Allocation process
entry: Allocation
entry: An ETCS stop marker is a trackside marker board that signals:
entry: Analysis
entry: Angular rate
entry: Answer.
entry: ASFA
entry: ANUNCIO--DE--SENALES--Y--FRENADO--AUTOMATICO label
entry: Applicant
entry: Application Condition
entry: Application Configuration Data
entry: Application Configuration.
entry: AEE
entry: APPLICATION--EXECUTION--ENVIRONMENT label
entry: Application Guideline
entry: AL
entry: APPLICATION--LAYER label
entry: ALM
entry: APPLICATION--LIFECYCLE--MANAGEMENT label
entry: API
entry: APPLICATION--PROGRAMMING--INTERFACE label
entry: ARCADIA
entry: ARC--HITECTURE--A--NALYSIS--AND--D--ESIGN--I--NTEGRATED--A--PPROACH label
entry: ARCT
entry: ARCHITECTURE--AND--RELEASE--COORDINATION--TEAM label
entry: ATAM
entry: ARCHITECTURE--TRADEOFF--ANALYSIS--METHOD label
entry: AWC
entry: ARCHITECTURE--WORKING--CIRCLE label
entry: Area Controller
entry: AoC
entry: AREA--OF--CONTROL label
entry: Arrival Datetime Change
entry: AFARP
entry: AS--FAR--AS--REASONABLY--PRACTICABLE label
entry: AsBo
entry: ASSESSMENT--BODY label
entry: Assessment.
entry: ASAM MDF
entry: ASSOCIATION--FOR--STANDARDISATION--OF--AUTOMATION--AND--MEASURING--SYSTEMS-----MEASUREMENT--DATA--FORMAT label
entry: ATO Automatic Train Operation AoC Area of Control CCS Control Command and Signal...
entry: AV
entry: ATO--AVAILABLE label
entry: EG
entry: ATO--ENGAGED label
entry: Attitude reference frame

1D reference frame
type: LexicalEntry
type: MultiwordExpression
canonical form: 1D reference frame
sense: 1D--REFERENCE--FRAME lexSense

1D--REFERENCE--FRAME lexConcept
type: LexicalConcept
definition: It is a one-dimensional reference frame attached to the vehicle where the ASTP is installed. On the plan of the carriage floor, it is defined by the origin represented by the ASTP reference point (refer to definition D21.1 2.1.1.1.1) and a x axis following the track centreline and oriented toward one end of the vehicle. The end of the vehicle used as the reference for the orientation of the x axis is defined by static configuration (e.g., side A or side B of the vehicle). This reference frame is fixed, it doesn’t change with either the train configuration, or the train movement. This reference frame is defined by static parameters represented by the ASTP reference point location and the orientation of the x axis in the vehicle. This 1D reference frame is used by the ASTP to express along the track centre line, the position, the speed, and the acceleration of the carriage where the ASTP is installed.

1D reference frame
type: Form

3D reference frame
type: LexicalEntry
type: MultiwordExpression
canonical form: 3D reference frame
sense: 3D--REFERENCE--FRAME lexSense

3D--REFERENCE--FRAME lexConcept
type: LexicalConcept
definition: It is a three-dimensional reference frame attached to the vehicle where the ASTP is installed. It is defined by the carriage frame by a right trihedron. The origin is the ASTP reference point (refer to definition D21.1 2.1.1.1.1). On the plan defined by the carriage floor, the x axis is the carriage longitudinal axis oriented toward one end of the vehicle (same direction as the x axis 1D reference frame), y axis is the orthogonal to the carriage longitudinal axis oriented to the left, z axis the orthogonal to the carriage floor oriented up. This reference frame is fixed, it doesn’t change with either the train configuration, or train movement. The 3D reference frame is used by the ASTP to express the velocity and acceleration of the vehicle where the ASTP is installed.

3D reference frame
type: Form

ESC
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: 4-2-17-1---ETCS--SYSTEM--COMPATIBILITY label
canonical form: ESC

4-2-17-1---ETCS--SYSTEM--COMPATIBILITY lexConcept
type: LexicalConcept
definition: ETCS System Compatibility (ESC) is the recording of technical compatibility between ETCS on-board and the trackside parts ETCS of the CCS subsystems within an area of use. Each ESC Type identifies the set of ESC checks (e.g. document check, lab or track test, …) applicable for a section or group of sections within an area of use. It is possible to use the same ESC type for cross border infrastructure and for different national infrastructures. The results of the ESC checks for an on-board unit on the Interoperability Constituent level or subsystem level, including findings and conditions arising, are recorded in the ESC Check Report. ‘Representative configuration’ means a configuration on the basis of which test results can be achieved, which are valid for various configurations of the same certified ETCS on-board interoperability constituent or of a certified on-board subsystem. These results shall also be equivalent for various configurations of a certified ETCS trackside subsystem. For ESC checks at ETCS on-board Interoperability Constituent level the following is to be observed: (1) The ESC Interoperability Constituent Statement records the ESC results of the ETCS On-board Interoperability Constituent to the ESC Type(s) that is valid regardless of the specific configuration of the ETCS on-board Interoperability Constituent. This document shall be produced by the on-board supplier. The template provided in Appendix C.2 or C.6 shall be used. (2) The ESC Interoperability Constituent Statement shall include the summary of the findings and conditions of the ESC Check Report(s) on the results of the ESC checks passed (defined in one or more ESC Type), which are valid independently from the specific configuration parameters of the on-board Interoperability Constituent and can therefore be used in every applicable specific on-board CCS subsystem level. (3) The ESC Interoperability Constituent Statement shall include the list of ESC checks performed for the ESC Type(s). …

4.2.17.1. ETCS System Compatibility
type: Form

ESC
type: Form

A location marker is a marker border on the trackside to indicate a potential En...
type: LexicalEntry
type: MultiwordExpression
canonical form: A location marker is a marker border on the trackside to indicate a potential En...
sense: A--LOCATION--MARKER--IS--A--MARKER--BORDER--ON--THE--TRACKSIDE--TO--INDICATE--A--POTENTIAL--EN lexSense

A--LOCATION--MARKER--IS--A--MARKER--BORDER--ON--THE--TRACKSIDE--TO--INDICATE--A--POTENTIAL--EN lexConcept
type: LexicalConcept
definition: A location marker is a marker border on the trackside to indicate a potential End of Authority (EoA).

A location marker is a marker border on the trackside to indicate a potential En...
type: Form

A mission is a train movement for a certain purpose without changing the train c...
type: LexicalEntry
type: MultiwordExpression
canonical form: A mission is a train movement for a certain purpose without changing the train c...
sense: A--MISSION--IS--A--TRAIN--MOVEMENT--FOR--A--CERTAIN--PURPOSE--WITHOUT--CHANGING--THE--TRAIN--C lexSense

A--MISSION--IS--A--TRAIN--MOVEMENT--FOR--A--CERTAIN--PURPOSE--WITHOUT--CHANGING--THE--TRAIN--C lexConcept
type: LexicalConcept
definition: A mission is a train movement for a certain purpose without changing the train characteristics or direction until the mission has reached its destination.

A mission is a train movement for a certain purpose without changing the train c...
type: Form

A perception that has a direct influence on the staff member. The perception can...
type: LexicalEntry
type: MultiwordExpression
canonical form: A perception that has a direct influence on the staff member. The perception can...
sense: A--PERCEPTION--THAT--HAS--A--DIRECT--INFLUENCE--ON--THE--STAFF--MEMBER---THE--PERCEPTION--CAN lexSense

A--PERCEPTION--THAT--HAS--A--DIRECT--INFLUENCE--ON--THE--STAFF--MEMBER---THE--PERCEPTION--CAN lexConcept
type: LexicalConcept
definition: A perception that has a direct influence on the staff member. The perception can be: * acoustic (image: 4-screenshot-20250930-144931-19.png) * visual (image: 5-screenshot-20250930-144931-20.png) * olfactory (image: 6-screenshot-20250930-144931-21.png) * gustatory (image: 7-screenshot-20250930-144931-22.png) * haptic (image: 8-screenshot-20250930-144931-23.png)

A perception that has a direct influence on the staff member. The perception can...
type: Form

A segments is an area of the infrastructure, on which missions are performed. Ro...
type: LexicalEntry
type: MultiwordExpression
canonical form: A segments is an area of the infrastructure, on which missions are performed. Ro...
sense: A--SEGMENTS--IS--AN--AREA--OF--THE--INFRASTRUCTURE--ON--WHICH--MISSIONS--ARE--PERFORMED---RO lexSense

A--SEGMENTS--IS--AN--AREA--OF--THE--INFRASTRUCTURE--ON--WHICH--MISSIONS--ARE--PERFORMED---RO lexConcept
type: LexicalConcept
definition: A segments is an area of the infrastructure, on which missions are performed. Routes are set to protect segments. A segment usually * starts at a Stop Marker, Location Marker, Shunting Signal or at the train front end AND * ends at the following Stop Marker, Location Marker, Shunting Signal, Protection Signal, Marker Goard "Stop for Shunting Movements" or buffer sto

A segments is an area of the infrastructure, on which missions are performed. Ro...
type: Form

Absolute position reference frame
type: LexicalEntry
type: MultiwordExpression
canonical form: Absolute position reference frame
sense: ABSOLUTE--POSITION--REFERENCE--FRAME lexSense

ABSOLUTE--POSITION--REFERENCE--FRAME lexConcept
type: LexicalConcept
definition: Train front end position expressed with absolute geo coordinate system using a 3 D reference frame (e.g., Long, Lat, Alt, WGS84, ETRS89…).

Absolute position reference frame
type: Form

Accident
type: LexicalEntry
type: Word
canonical form: Accident
sense: ACCIDENT lexSense

ACCIDENT lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: ‘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) ]

Accident
type: Form

Accuracy
type: LexicalEntry
type: Word
canonical form: Accuracy
sense: ACCURACY lexSense

ACCURACY lexConcept
type: LexicalConcept
definition: The difference between true and estimated values with a defined probability.

Accuracy
type: Form

Actor
type: LexicalEntry
type: Word
canonical form: Actor
sense: ACTOR lexSense

ACTOR lexConcept
type: LexicalConcept
definition: An actor is an entity external to the system under consideration, which can be either a human or a technical system. Actors interact with the system through interfaces. This definition is applicable to system actor, logical actor, and physical actor.

Actor
type: Form

Adaptability
type: LexicalEntry
type: Word
canonical form: Adaptability
sense: ADAPTABILITY lexSense

ADAPTABILITY lexConcept
type: LexicalConcept
definition: Adaptability refers to the ability to adjust a system in response to changes in its environment or changes of requirements. It involves a broader concept of flexibility and resilience, encompassing not only modifications to the system itself but also its capacity to accommodate evolving needs or external factors. An adaptable system can respond effectively to new technologies, market demands, user expectations, or regulatory changes.

Adaptability
type: Form

Adapted product
type: LexicalEntry
type: MultiwordExpression
canonical form: Adapted product
sense: ADAPTED--PRODUCT lexSense

ADAPTED--PRODUCT lexConcept
type: LexicalConcept
definition: In System Pillar context, an "adapted" product uses some of the SP compliant specifications, but not all. Its system behavior is not completely compliant to System Pillar specification. The adaption is done, to make current national products future ready (later connection or upgrade to SP compliant systems)

Adapted product
type: Form

Adaptor
type: LexicalEntry
type: Word
canonical form: Adaptor
sense: ADAPTOR lexSense

ADAPTOR lexConcept
type: LexicalConcept
definition: 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.

Adaptor
type: Form

Add Train
type: LexicalEntry
type: MultiwordExpression
canonical form: Add Train
sense: ADD--TRAIN lexSense

ADD--TRAIN lexConcept
type: LexicalConcept
definition: Add a completely new train journey or add a new train journey to an existing train journey

Add Train
type: Form

Advanced Protection System APS
type: LexicalEntry
type: MultiwordExpression
canonical form: Advanced Protection System APS
sense: ADVANCED--PROTECTION--SYSTEM--APS lexSense

ADVANCED--PROTECTION--SYSTEM--APS lexConcept
type: LexicalConcept
definition: Advanced Protection System APS{comment:230} The Advanced Protection System is based the train-centric approach using Full Moving block principles with the overall objective to engineer high capacity, low cost, high reliability signalling systems. APS dissolves the conventional separation of RBC and interlocking functionality and uses a more generic and simplified safety logic by abandoning the route concept and the accompanying static engineering processes. By emphasising the safety logic, the dependency on country specific operational processes is reduced. A new term is ETPS "European Train Protection System".

Advanced Protection System APS
type: Form

ASTP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ADVANCED--SAFE--TRAIN--POSITIONING--ASTP label
canonical form: ASTP

ADVANCED--SAFE--TRAIN--POSITIONING--ASTP lexConcept
type: LexicalConcept
definition: 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)
type: Form

ASTP
type: Form

ASTP
type: Acronym
type: LexicalEntry
acronym for: ADVANCED--SAFE--TRAIN--POSITIONING label
canonical form: ASTP

ADVANCED--SAFE--TRAIN--POSITIONING lexConcept
type: LexicalConcept
definition: Advanced Safe Train Positioning

Advanced Safe Train Positioning
type: Form

ASTP
type: Form

(AFARP) - As far as reasonably practicable
type: LexicalEntry
type: MultiwordExpression
canonical form: (AFARP) - As far as reasonably practicable
sense: AFARP-----AS--FAR--AS--REASONABLY--PRACTICABLE lexSense

AFARP-----AS--FAR--AS--REASONABLY--PRACTICABLE lexConcept
type: LexicalConcept
definition: "As far as reasonably practicable" means that the action shall be undertaken until either the requirement is met, or the actors involved in the definition, review and approval of the work item conclude that further effort to resolve open issues is unlikely to bring an equivalent measurable benefit to the overall solution.

(AFARP) - As far as reasonably practicable
type: Form

Allocation Area
type: LexicalEntry
type: MultiwordExpression
canonical form: Allocation Area
sense: ALLOCATION--AREA lexSense

ALLOCATION--AREA lexConcept
type: LexicalConcept
definition: The area in the trackside which shall be free of operational conflict(s) for the execution of an operational need (movement or other). In other words, it is the area in the trackside that shall be reserved to an operational movement. The safety system shall not allow an SPT2OD-6043 - Missing cross-reference to be allocated to conflicting movement(s) or conflicting operational need(s). (image: diagram_20231213-1048.28106.mxg.svg) {comment:64} Note as a representation, SPT2OD-6043 - Missing cross-reference is equivalent to the combined Danger Zone(s) of the underlying assets over the area in which it is intended to next perform a train movement, possibly including flank protection and overlap areas (to be discussed at a later stage).

Allocation Area
type: Form

Allocation Body
type: LexicalEntry
type: MultiwordExpression
canonical form: Allocation Body
sense: ALLOCATION--BODY lexSense

ALLOCATION--BODY lexConcept
type: LexicalConcept
definition: An Allocation Body is an independent organization responsible for train path allocation to Railway Undertakings and other Applicants; this includes the designation of individual paths and the assessment of their availability. In most cases, the AB is the same organization as the Infrastructure Manager. But if the rail operator is not independent from the Infrastructure Manager, then path allocation must be carried out, according to Directive 2012/34/EU, by an independent Allocation Body.

Allocation Body
type: Form

Allocation process
type: LexicalEntry
type: MultiwordExpression
canonical form: Allocation process
sense: ALLOCATION--PROCESS lexSense

ALLOCATION--PROCESS lexConcept
type: LexicalConcept
definition: The process by which capacity is granted to an Applicant by the Infrastructure Manager or relevant capacity Allocation Body; this capacity is available for the duration of the working timetable period only.

Allocation process
type: Form

Allocation
type: LexicalEntry
type: Word
canonical form: Allocation
sense: ALLOCATION lexSense

ALLOCATION lexConcept
type: LexicalConcept
definition: Allocation means the allocation of railway infrastructure capacity by an infrastructure manager

Allocation
type: Form

An ETCS stop marker is a trackside marker board that signals:
type: LexicalEntry
type: MultiwordExpression
canonical form: An ETCS stop marker is a trackside marker board that signals:
sense: AN--ETCS--STOP--MARKER--IS--A--TRACKSIDE--MARKER--BOARD--THAT--SIGNALS lexSense

AN--ETCS--STOP--MARKER--IS--A--TRACKSIDE--MARKER--BOARD--THAT--SIGNALS lexConcept
type: LexicalConcept
definition: An ETCS stop marker is a trackside marker board that signals: * a potential End of Authoritiy (EoA) * to signal the place where a driver has to stop the train

An ETCS stop marker is a trackside marker board that signals:
type: Form

Analysis
type: LexicalEntry
type: Word
canonical form: Analysis
sense: ANALYSIS lexSense

ANALYSIS lexConcept
type: LexicalConcept
definition: Qualitative assessment of requirements, issues, etc.

Analysis
type: Form

Angular rate
type: LexicalEntry
type: MultiwordExpression
canonical form: Angular rate
sense: ANGULAR--RATE lexSense

ANGULAR--RATE lexConcept
type: LexicalConcept
definition: It is the angular speed of the rotational angles of the attitude.

Angular rate
type: Form

Answer.
type: LexicalEntry
type: Word
canonical form: Answer.
sense: ANSWER lexSense

ANSWER lexConcept
type: LexicalConcept
definition: Answers a Question. Questions and answers are used for Q&A or FAQ documents. If you have an open question in your project, use "Issue"

Answer.
type: Form

ASFA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ANUNCIO--DE--SENALES--Y--FRENADO--AUTOMATICO label
canonical form: ASFA

ANUNCIO--DE--SENALES--Y--FRENADO--AUTOMATICO lexConcept
type: LexicalConcept
definition: Anuncio de Señales y Frenado Automático (ASFA; "Announcement of Signals and Automatic Braking"); Is an Automatic Protetion System which is widely used on the Spanish rail network. It consists of a mechanism that stops a train if the driver does not properly heed signals.

Anuncio de Señales y Frenado Automático
type: Form

ASFA
type: Form

Applicant
type: LexicalEntry
type: Word
canonical form: Applicant
sense: APPLICANT lexSense

APPLICANT lexConcept
type: LexicalConcept
definition: Applicant means a railway undertaking or an international grouping of railway undertakings or other persons or legal entities, such as competent authorities under Regulation (EC) No 1370/2007 and shippers, freight forwarders and combined transport operators, with a public-service or commercial interest in procuring infrastructure capacity;

Applicant
type: Form

Application Condition
type: LexicalEntry
type: MultiwordExpression
canonical form: Application Condition
sense: APPLICATION--CONDITION lexSense

APPLICATION--CONDITION lexConcept
type: LexicalConcept
definition: Application conditions are specific conditions imposed on external entities that interact with the system under consideration. They are also precise requirements about the environment and use of the system under consideration in its application. The following list contains examples for application conditions: * skills of maintenance people that need{comment:24} to be trained * operators of the system * requirements about the physical environment * maintenance processes ("exported constraint, relevant for users"). * physical needs * temperatures of server rooms * engineering rules * precautions in installation and testing * rules and methods for maintenance and fault-finding * safety-related ones (SRAC) and RAM-related ones (RAM RAC) Note: Application Conditions shall not be used to export requirements to another system or subsystem. If something is expected from another level 3 system or subsystem, it shall first go through ARC domain who will derive it.{comment:111} This ensures clear entry points for subsystems, improve completeness of analysis by considering the big picture when more than one sub-system is involved. Addtional note: External should be more specific in the frame of System Pillar. This could be external to system level 2 (so external to CCS and TMS etc.). This to avoid having subsystems (system level 3 and higher) exporting requirements to each other instead of having them clearly defined at global system with appropriate system analysis. In the context of System Pillar, "external" has to be understood as "external to CCS system" for tasks/domains, system level or analysis phase (OA, SA, LA or PA). {comment:33}

Application Condition
type: Form

Application Configuration Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Application Configuration Data
sense: APPLICATION--CONFIGURATION--DATA lexSense

APPLICATION--CONFIGURATION--DATA lexConcept
type: LexicalConcept
definition: The Application configuration refers to use case-specific data for the Consuming Systems for a specific application. These can be detailed as SPT2TS-127776 - Infrastructure data i.e., Track edges, Track geometry, Track properties, Segment Profiles, etc. and SPT2TS-127777 - Vehicle data i.e., Braking and Traction efforts, Rolling coefficients, etc.

Application Configuration Data
type: Form

Application Configuration.
type: LexicalEntry
type: MultiwordExpression
canonical form: Application Configuration.
sense: APPLICATION--CONFIGURATION lexSense

APPLICATION--CONFIGURATION lexConcept
type: LexicalConcept
definition: Set of combined Features (which are child workitems).

Application Configuration.
type: Form

AEE
type: Acronym
type: LexicalEntry
acronym for: APPLICATION--EXECUTION--ENVIRONMENT label
canonical form: AEE

APPLICATION--EXECUTION--ENVIRONMENT lexConcept
type: LexicalConcept
definition: The Application Execution Environment refers to the combination of Runtime Environment and Safety Framework. Previous definition: The Application Execution Environment refers to the combination of Runtime Environment and Safety Environment.

APPLICATION--EXECUTION--ENVIRONMENT lexConcept 2
type: LexicalConcept
definition: The Application Execution Environment refers to the combination of Runtime Environment and Safety Environment. The safety environment is excluded for the basic integrity applications

Application Execution Environment
type: Form

AEE
type: Form

AEE
type: Form

Application Guideline
type: LexicalEntry
type: MultiwordExpression
canonical form: Application Guideline
sense: APPLICATION--GUIDELINE lexSense

APPLICATION--GUIDELINE lexConcept
type: LexicalConcept
definition: Defining procedural requirements for Railway Operators

Application Guideline
type: Form

AL
type: Acronym
type: LexicalEntry
acronym for: APPLICATION--LAYER label
canonical form: AL

APPLICATION--LAYER lexConcept
type: LexicalConcept
definition: The Application Layer refers to the functions provided by the Functional Systems. These functions are implemented as Tasks within Functional Applications. Previous definition: The Application Layer contains Functional Applications that constitute Functional Systems.

APPLICATION--LAYER lexConcept 2
type: LexicalConcept
definition: The Application Layer contains Functional Applications that constitute Functional Systems.

Application Layer
type: Form

AL
type: Form

AL
type: Form

ALM
type: Acronym
type: LexicalEntry
acronym for: APPLICATION--LIFECYCLE--MANAGEMENT label
canonical form: ALM

APPLICATION--LIFECYCLE--MANAGEMENT lexConcept
type: LexicalConcept
definition: Application Lifecycle Management

Application Lifecycle Management
type: Form

ALM
type: Form

API
type: Acronym
type: LexicalEntry
acronym for: APPLICATION--PROGRAMMING--INTERFACE label
canonical form: API

APPLICATION--PROGRAMMING--INTERFACE lexConcept
type: LexicalConcept
definition: Application Programming Interface

Application Programming Interface
type: Form

API
type: Form

ARCADIA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ARC--HITECTURE--A--NALYSIS--AND--D--ESIGN--I--NTEGRATED--A--PPROACH label
canonical form: ARCADIA

ARC--HITECTURE--A--NALYSIS--AND--D--ESIGN--I--NTEGRATED--A--PPROACH lexConcept
type: LexicalConcept
definition: 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)hitecture (A)nalysis and (D)esign (I)ntegrated (A)pproach
type: Form

ARCADIA
type: Form

ARCT
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ARCHITECTURE--AND--RELEASE--COORDINATION--TEAM label
canonical form: ARCT

ARCHITECTURE--AND--RELEASE--COORDINATION--TEAM lexConcept
type: LexicalConcept
definition: Architecture and Release Coordination Team

Architecture and Release Coordination Team
type: Form

ARCT
type: Form

ATAM
type: Acronym
type: LexicalEntry
acronym for: ARCHITECTURE--TRADEOFF--ANALYSIS--METHOD label
canonical form: ATAM

ARCHITECTURE--TRADEOFF--ANALYSIS--METHOD lexConcept
type: LexicalConcept
definition: Architecture Tradeoff Analysis Method

Architecture Tradeoff Analysis Method
type: Form

ATAM
type: Form

AWC
type: Acronym
type: LexicalEntry
acronym for: ARCHITECTURE--WORKING--CIRCLE label
canonical form: AWC

ARCHITECTURE--WORKING--CIRCLE lexConcept
type: LexicalConcept
definition: Architecture Working Circle

Architecture Working Circle
type: Form

AWC
type: Form

Area Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Area Controller
sense: AREA--CONTROLLER lexSense

AREA--CONTROLLER lexConcept
type: LexicalConcept
definition: The Area Controller manages areas for the View.

AREA--CONTROLLER lexConcept 2
type: LexicalConcept
definition: The Area Controller manages areas for the View.

AREA--CONTROLLER lexConcept 3
type: LexicalConcept
definition: The Area Controller manages areas for the View.

AREA--CONTROLLER lexConcept 4
type: LexicalConcept
definition: The Area Controller manages areas for the View.

AREA--CONTROLLER lexConcept 5
type: LexicalConcept
definition: The Area Controller manages areas for the View.

AREA--CONTROLLER lexConcept 6
type: LexicalConcept
definition: The Area Controller manages areas for the View.

AREA--CONTROLLER lexConcept 7
type: LexicalConcept
definition: The Area Controller manages areas for the View.

AREA--CONTROLLER lexConcept 8
type: LexicalConcept
definition: Area Controller The Area Controller manages areas for the View.

Area Controller
type: Form

AoC
type: Acronym
type: LexicalEntry
acronym for: AREA--OF--CONTROL label
canonical form: AoC

AREA--OF--CONTROL lexConcept
type: LexicalConcept
definition: The Area of Control is the topologically limited extent and the infrastructural Trackside Assets in this geographical extent. The term is used here for defining the technical and operational responsibility of a Trackside Subsystem.

Area of Control
type: Form

AoC
type: Form

Arrival Datetime Change
type: LexicalEntry
type: MultiwordExpression
canonical form: Arrival Datetime Change
sense: ARRIVAL--DATETIME--CHANGE lexSense

ARRIVAL--DATETIME--CHANGE lexConcept
type: LexicalConcept
definition: Change in the arrival time of a train in a station, either by arriving earlier or later than planned

Arrival Datetime Change
type: Form

AFARP
type: Acronym
type: LexicalEntry
acronym for: AS--FAR--AS--REASONABLY--PRACTICABLE label
canonical form: AFARP

AS--FAR--AS--REASONABLY--PRACTICABLE lexConcept
type: LexicalConcept
definition: Denote that an action shall be done until the cost to do so does not justify the benefit of doing it.

As far as reasonably practicable
type: Form

AFARP
type: Form

AsBo
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ASSESSMENT--BODY label
canonical form: AsBo

ASSESSMENT--BODY lexConcept
type: LexicalConcept
definition: From DIRECTIVE (EU) 2016/797 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 11 May 2016 on the interoperability of the rail system within the European Union: (42) ‘conformity assessment body’ means a body that has been notified or designated to be responsible for conformity assessment activities, including calibration, testing, certification and inspection; a conformity assessment body is classified as a ‘notified body’ following notification by a Member State; a conformity assessment body is classified as a ‘designated body’ following designation by a Member State;

Assessment Body
type: Form

AsBo
type: Form

Assessment.
type: LexicalEntry
type: Word
canonical form: Assessment.
sense: ASSESSMENT lexSense

ASSESSMENT lexConcept
type: LexicalConcept
definition: Quantitative assessment of requirements, issues, etc.

Assessment.
type: Form

ASAM MDF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ASSOCIATION--FOR--STANDARDISATION--OF--AUTOMATION--AND--MEASURING--SYSTEMS-----MEASUREMENT--DATA--FORMAT label
canonical form: ASAM MDF

ASSOCIATION--FOR--STANDARDISATION--OF--AUTOMATION--AND--MEASURING--SYSTEMS-----MEASUREMENT--DATA--FORMAT lexConcept
type: LexicalConcept
definition: Association for Standardisation of Automation and Measuring Systems - Measurement Data Format

Association for Standardisation of Automation and Measuring Systems - Measurement Data Format
type: Form

ASAM MDF
type: Form

ATO Automatic Train Operation AoC Area of Control CCS Control Command and Signal...
type: LexicalEntry
type: MultiwordExpression
canonical form: ATO Automatic Train Operation AoC Area of Control CCS Control Command and Signal...
sense: ATO--AUTOMATIC--TRAIN--OPERATION--AOC--AREA--OF--CONTROL--CCS--CONTROL--COMMAND--AND--SIGNAL lexSense

ATO--AUTOMATIC--TRAIN--OPERATION--AOC--AREA--OF--CONTROL--CCS--CONTROL--COMMAND--AND--SIGNAL lexConcept
type: LexicalConcept
definition: ATO | Automatic Train Operation AoC | Area of Control | CCS | Control Command and Signaling CI/CD | Continuous Integration / Continuous Deployment CMS | Capacity Management system CPU | Central Processing Unit CTC | Centralized traffic control CVSS | Common Vulnerability Scoring System | DBMS | Database Management System DDOS | Distributed Denial of Service DEV | Development DLP | Data loss prevention DNS | Domain Name System DR | Disaster Recovery-Plan | EDA | Event-driven architecture ELK | Elasticsearch, Logstash, Kibana | FAM | Fixed asset mgmt | HMI | Human Machine Interface HTTP | Hypertext Transfer Protocol | IRM | Information Rights Management | OS | Operating system OR | Operational Requirements | NTMS | Neighborhood TMS | MD5 | Message Digest Method 5 MITM | Man-in-the-middle attack MS | Microservices MVCC | Multi-version concurrency control | PES | Plan Execution System PIS | Passenger Information System POS | Path Order System PROD | Production | QA | Quality Assurance{comment:128} | RAID | Redundant Array of Independent Disks RAM | Random Access Memory RBAS | Role Based Access Control REST | Representational State Transfer RIM | Rail Infrastructure Manager ROC | Rail Operating Company RT | Real Time RU | Rail Undertakings | SAD | System Architecture Description SCI-OP | Standard Communications Interface – Operational Plan SEMP | System Engineering Management Plan SOAP | Simple Object Access Protocol SoC | Separation of Concerns SSL | Secure Sockets Layer | TAF | Telematics Applications for Freight TAP | Telematics Applications for Passenger Services TCR | Temporary Capacity Restrictions TLS | Transport Layer Security TMSTPS | Traffic Management SystemTrain Protection System TSI | Technical Specification for Interoperability | UML | Unified Modeling Language | WAF | Web Application Firewall WSDL | Web Services Description Language | XFN | Cross functional

ATO Automatic Train Operation AoC Area of Control CCS Control Command and Signal...
type: Form

AV
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ATO--AVAILABLE label
canonical form: AV

ATO--AVAILABLE lexConcept
type: LexicalConcept
definition: When it is in AV State, the ATO-OB is ready for operation and it is waiting for the ATO Engagement Conditions to be fulfilled.

ATO Available
type: Form

AV
type: Form

EG
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ATO--ENGAGED label
canonical form: EG

ATO--ENGAGED lexConcept
type: LexicalConcept
definition: When it is in EG State, the ATO-OB is responsible for driving the train controlling brake and traction according to the computed ATO Operational Speed Profile.

ATO Engaged
type: Form

EG
type: Form

Attitude reference frame
type: LexicalEntry
type: MultiwordExpression
canonical form: Attitude reference frame
sense: ATTITUDE--REFERENCE--FRAME lexSense

ATTITUDE--REFERENCE--FRAME lexConcept
type: LexicalConcept
definition: It describes the orientation of a rigid body with respect to a fixed coordinate system by determining the rotational angles, yaw-pitch-roll. On the plan defined by the carriage floor, the roll axis is the carriage longitudinal axis oriented toward the train front end, pitch axis is the orthogonal to the carriage longitudinal axis oriented to the left, yaw axis is the orthogonal to the carriage floor oriented up. Angles are absolute values using as references the horizontal plan to determine the pitch and roll angles, the direction to the north to determine the yaw.

Attitude reference frame
type: Form

Attribute
type: LexicalEntry
type: Word
canonical form: Attribute
sense: ATTRIBUTE lexSense

ATTRIBUTE lexConcept
type: LexicalConcept
definition: Attribute is an inherent property or characteristic of an entity that can be distinguished quantitatively or qualitatively by human or automated means

Attribute
type: Form

Authentication
type: LexicalEntry
type: Word
canonical form: Authentication
sense: AUTHENTICATION lexSense

AUTHENTICATION lexConcept
type: LexicalConcept
definition: The process to verify the identity of communicating peers.

Authentication
type: Form

Authorised User
type: LexicalEntry
type: MultiwordExpression
canonical form: Authorised User
sense: AUTHORISED--USER lexSense

AUTHORISED--USER lexConcept
type: LexicalConcept
definition: A system user with write access, who can configure the system

Authorised User
type: Form

ATIP
type: Acronym
type: LexicalEntry
acronym for: AUTOMATED--TRACK--INSPECTION--PROGRAM label
canonical form: ATIP

AUTOMATED--TRACK--INSPECTION--PROGRAM lexConcept
type: LexicalConcept
definition: Automated Track Inspection Program (by Federal Railroad Administration (USA))

Automated Track Inspection Program
type: Form

ATIP
type: Form

Automatic Conflict Solution
type: LexicalEntry
type: MultiwordExpression
canonical form: Automatic Conflict Solution
sense: AUTOMATIC--CONFLICT--SOLUTION lexSense

AUTOMATIC--CONFLICT--SOLUTION lexConcept
type: LexicalConcept
definition: Solves conflicts based on algorithms. May use optimisation functions.

Automatic Conflict Solution
type: Form

ADM
type: Acronym
type: LexicalEntry
acronym for: AUTOMATIC--DRIVING--MODULE label
canonical form: ADM

AUTOMATIC--DRIVING--MODULE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Automatic Driving Module

Automatic Driving Module
type: Form

ADM
type: Form

APE
type: Acronym
type: LexicalEntry
acronym for: AUTOMATIC--PLAN--EXECUTION label
canonical form: APE

AUTOMATIC--PLAN--EXECUTION lexConcept
type: LexicalConcept
definition: This is the adaptation of the existing concept of Automatic Route Setting (ARS) as defined in (SPLI-1455 - Automatic route setting system) irrespective of how the routes/paths are set. Concept is being currently developed under topic 72 (2 subtopics planned, one for manual and another one for automatic activation/deactivation of routes/paths) and will need support and advice from Traffic CS to see how it matches the new concept of routes defined by Traffic CS.

Automatic Plan Execution
type: Form

APE
type: Form

APM
type: Acronym
type: LexicalEntry
acronym for: AUTOMATIC--PROCESSING--MODULE label
canonical form: APM

AUTOMATIC--PROCESSING--MODULE lexConcept
type: LexicalConcept
definition: Automatic Processing Module

Automatic Processing Module
type: Form

APM
type: Form

ASO
type: Acronym
type: LexicalEntry
acronym for: AUTOMATIC--SHUNTING--OPERATION label
canonical form: ASO

AUTOMATIC--SHUNTING--OPERATION lexConcept
type: LexicalConcept
definition: Automatic Shunting Operation

Automatic Shunting Operation
type: Form

ASO
type: Form

ATO
type: Acronym
type: LexicalEntry
acronym for: AUTOMATIC--TRAIN--OPERATION label
canonical form: ATO

AUTOMATIC--TRAIN--OPERATION lexConcept
type: LexicalConcept
definition: Automatic Train Operation

AUTOMATIC--TRAIN--OPERATION lexConcept 2
type: LexicalConcept
definition: Automatic Train Operation

AUTOMATIC--TRAIN--OPERATION lexConcept 3
type: LexicalConcept
definition: 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

Automatic Train Operation
type: Form

ATO
type: Form

ATO
type: Form

ATO
type: Form

availability, <of a product>
type: LexicalEntry
type: MultiwordExpression
canonical form: availability, <of a product>
sense: AVAILABILITY--<OF--A--PRODUCT> lexSense

AVAILABILITY--<OF--A--PRODUCT> lexConcept
type: LexicalConcept
definition: Ability of an item to be in a state to perform a required function under given conditions at a given instant of time or over a given time interval, assuming that the required external resources are provided [SOURCE: IEC 60050-821: FDIS2016, 821-05-82, modified] Source: SPPRAMSS-349 - [EN 50126-1:2017]

availability, <of a product>
type: Form

Availability
type: LexicalEntry
type: Word
canonical form: Availability
sense: AVAILABILITY lexSense

AVAILABILITY lexConcept
type: LexicalConcept
definition: Availability: property of being accessible and usable on demand by an authorized entity (source: ISO 27000-2018 )

Availability
type: Form

BKP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: BACKUP--AND--RESTORE label
canonical form: BKP

BACKUP--AND--RESTORE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Backup and restore

Backup and restore
type: Form

BKP
type: Form

Backwards Compatibility
type: LexicalEntry
type: MultiwordExpression
canonical form: Backwards Compatibility
sense: BACKWARDS--COMPATIBILITY lexSense

BACKWARDS--COMPATIBILITY lexConcept
type: LexicalConcept
definition: Backwards compatibility is a design or software feature that allows a product, system, or software application to remain compatible with earlier versions or older hardware. In the context of software, it means that a newer version of a program can still run and interact with files, data, or systems that were created using previous versions of that software. This ensures that users can upgrade to the latest version without losing access to their existing data or needing to make significant changes to their workflows. It's a valuable feature that enhances user convenience and reduces disruptions when technology evolves. Backward compatibility for hardware, also known as "hardware backward compatibility," refers to the ability of a newer piece of hardware to work seamlessly with older hardware components or peripherals, such as connectors, interfaces, or accessories. In the context of hardware, backward compatibility typically ensures that the new hardware can accommodate and interact with devices or components that were designed for older hardware specifications. Hardware backward compatibility is important for user convenience, cost savings, and reducing the need for immediate updates to all associated hardware components when a single component is upgraded. It often requires the inclusion of older ports or connectors on newer hardware or the development of adapters or converters to bridge the compatibility gap between old and new technologies.

Backwards Compatibility
type: Form

Baseline
type: LexicalEntry
type: Word
canonical form: Baseline
sense: BASELINE lexSense

BASELINE lexConcept
type: LexicalConcept
definition: Sets of specifications or work products at specific points in time that have been formally reviewed and agreed on. Notes: - Pay attention that, in the context of System Pillar (and use of Polarion), several kinds of baselines exist: Polarion Document Baseline, Polarion Project Baseline, Polarion Collection Baseline and System Pillar Release (treated in the Configuration Management Plan ){comment:218} - This definition is a general definition. Another definition exists in glossary imported from the Subset-23. : SPLI-772 - BASELINE {comment:348}

Baseline
type: Form

basic ASTP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: BASIC--ADVANCED--SAFE--TRAIN--POSITIONING--BASIC--ASTP label
canonical form: basic ASTP

BASIC--ADVANCED--SAFE--TRAIN--POSITIONING--BASIC--ASTP lexConcept
type: LexicalConcept
definition: Basic Advanced Safe Train Positioning (Basic ASTP) is a new CCS-OB interoperability constituent providing Odometry functionality with to be defined performance and availability targets. Basic ASTP shall perform this function primarily for ERTMS/ETCS on-board equipment via a standardised FFFIS compliant interface, but could be used for other applications on the train.

basic Advanced Safe Train Positioning (basic ASTP)
type: Form

basic ASTP
type: Form

Basic Brake Test -
type: LexicalEntry
type: MultiwordExpression
canonical form: Basic Brake Test -
sense: BASIC--BRAKE--TEST lexSense

BASIC--BRAKE--TEST lexConcept
type: LexicalConcept
definition: Basic Brake Test -

Basic Brake Test -
type: Form

BIL
type: Acronym
type: LexicalEntry
acronym for: BASIC--INTEGRITY--LEVEL label
canonical form: BIL

BASIC--INTEGRITY--LEVEL lexConcept
type: LexicalConcept
definition: Integrity attribute for safety-related functions with a TFFR higher than (less demanding) 10−5.h−1 or for non-safety-related functions.

Basic Integrity Level
type: Form

BIL
type: Form

I4
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: BASIC--INTEGRITY--PLATFORM--INDEPENDENCE--INTERFACE label
canonical form: I4

BASIC--INTEGRITY--PLATFORM--INDEPENDENCE--INTERFACE lexConcept
type: LexicalConcept
definition: The Basic Integrity Platform Independence Interface I4 (Interface 4) is used to perform a basic integrity platform independence with the applications. In other words, this API is an interface limited to non-safety functionalities between runtime environment and applications.

Basic Integrity Platform Independence Interface
type: Form

I4
type: Form

BBC (DR)
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: BBC--DR label
canonical form: BBC (DR)

BBC--DR lexConcept
type: LexicalConcept
definition: Building Block Configuration which contains the deployment rules for the FS.

BBC--DR lexConcept 2
type: LexicalConcept
definition: Building Block Configuration which contains the deploy rules for the FS.

BBC (DR)
type: Form

BBC (DR)
type: Form

BBC (InSW)
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: BBC--INSW label
canonical form: BBC (InSW)

BBC--INSW lexConcept
type: LexicalConcept
definition: Building Block Configuration which contains the initial software for the Initial FS Compartment.

BBC (InSW)
type: Form

BBC (InSW)
type: Form

BBC (SW-x)
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: BBC--SW-X label
canonical form: BBC (SW-x)

BBC--SW-X lexConcept
type: LexicalConcept
definition: Building Block Configuration which contains software and/or data which is part of an FS Compartment. The quantity of BBCs - BBC(SW-1), BBC(SW-2), .. - depends on the concrete solution of the FS.

BBC (SW-x)
type: Form

BBC (SW-x)
type: Form

Binary Executable File
type: LexicalEntry
type: MultiwordExpression
canonical form: Binary Executable File
sense: BINARY--EXECUTABLE--FILE lexSense

BINARY--EXECUTABLE--FILE lexConcept
type: LexicalConcept
definition: A Binary Executable File is a platform-specific file that contains compiled code in a machine-readable binary format, which can be directly executed by a computer’s processor

Binary Executable File
type: Form

Biometric Reader
type: LexicalEntry
type: MultiwordExpression
canonical form: Biometric Reader
sense: BIOMETRIC--READER lexSense

BIOMETRIC--READER lexConcept
type: LexicalConcept
definition: 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.

BIOMETRIC--READER lexConcept 2
type: LexicalConcept
definition: 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.

BIOMETRIC--READER lexConcept 3
type: LexicalConcept
definition: 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.

BIOMETRIC--READER lexConcept 4
type: LexicalConcept
definition: 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.

BIOMETRIC--READER lexConcept 5
type: LexicalConcept
definition: 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.

BIOMETRIC--READER lexConcept 6
type: LexicalConcept
definition: 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.

BIOMETRIC--READER lexConcept 7
type: LexicalConcept
definition: 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 lexConcept 8
type: LexicalConcept
definition: 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.

Biometric Reader
type: Form

Black Box Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Black Box Data
sense: BLACK--BOX--DATA lexSense

BLACK--BOX--DATA lexConcept
type: LexicalConcept
definition: SW configuration data content format that is supplier specific. The payload is not standardized for this case, therefore it is "black box" and being distributed as non transparent payload.

Black Box Data
type: Form

Black channel
type: LexicalEntry
type: MultiwordExpression
canonical form: Black channel
sense: BLACK--CHANNEL lexSense

BLACK--CHANNEL lexConcept
type: LexicalConcept
definition: Black Channel is formally defined into EN 61748-3-3 chapter 3.1.1.2 as "communication channel without available evidence of design or validation according to IEC 61508 series". More in general, a black channel refers to a communication channel where the characteristics of the communication system are not fully known or trusted, and therefore, safety mechanisms are implemented within the safety-related system itself to ensure reliable and safe data transmission. Essentially, it treats the communication system as a "black box" and relies on safety protocols and error detection/correction mechanisms within the communicating devices to mitigate potential communication failures. Black channel concept application and related safety measures are widely reported into CEI EN 61748-3-3.

Black channel
type: Form

Block / Unblock
type: LexicalEntry
type: MultiwordExpression
canonical form: Block / Unblock
sense: BLOCK-- --UNBLOCK lexSense

BLOCK-- --UNBLOCK lexConcept
type: LexicalConcept
definition: Commands from Signaller (and in some situations also from Maintainer) to set or remove inhibition of the following track elements among others: * occupation of a track section (that could be disturbed/failed) * sending of MA from a specific signal/SMB * movement of a movable element (points, derailers, LXs, bascule bridges, etc) * route setting (that could include track sections, movable elements and signals/SMBs within the route){comment:147}

Block / Unblock
type: Form

Brake De-icing -
type: LexicalEntry
type: MultiwordExpression
canonical form: Brake De-icing -
sense: BRAKE--DE-ICING lexSense

BRAKE--DE-ICING lexConcept
type: LexicalConcept
definition: Brake De-icing -

Brake De-icing -
type: Form

Brake Monitoring -
type: LexicalEntry
type: MultiwordExpression
canonical form: Brake Monitoring -
sense: BRAKE--MONITORING lexSense

BRAKE--MONITORING lexConcept
type: LexicalConcept
definition: Brake Monitoring -

Brake Monitoring -
type: Form

Brake Pipe -
type: LexicalEntry
type: MultiwordExpression
canonical form: Brake Pipe -
sense: BRAKE--PIPE lexSense

BRAKE--PIPE lexConcept
type: LexicalConcept
definition: Brake Pipe -

Brake Pipe -
type: Form

BBC
type: Acronym
type: LexicalEntry
acronym for: BUILDING--BLOCK--CONFIGURATION label
canonical form: BBC

BUILDING--BLOCK--CONFIGURATION lexConcept
type: LexicalConcept
definition: Data for a Building Block, see Configuration Update Concept of Transversal.

BUILDING--BLOCK--CONFIGURATION lexConcept 2
type: LexicalConcept
definition: A BuildingBlockConfiguration (BBC) is a node on a layer within the configuration dependency tree. It must be uniquely identifiable within the system as bbcId. On the lower levels of the dependency trees the bbcIds are assigned by the supplier - for example by imprinting the structure of configurable items into a sourceable physical unit. A BBC may contain a configurationFile artifact and dependencies to other BBCs. One Building BlockConfiguration (BBC) has exactly one configuration.json file (and an additional configurationSafe.json if it is a safe BBC). BBCs that itself have no further dependencies in their configuration.json file are the Lowest Updatable Units (LUU - can be updated on its own). BBCs that are updatable must provide a corresponding configurationFile (payload). BBCs that are updatable need an endpoint described in the "configuration.json" file. That BBC endpoint can be accessed using a protocol capable of file transfer (e.g. opc ua).

Building Block Configuration
type: Form

BBC
type: Form

BBC
type: Form

Building Block Manifest
type: LexicalEntry
type: MultiwordExpression
canonical form: Building Block Manifest
sense: BUILDING--BLOCK--MANIFEST lexSense

BUILDING--BLOCK--MANIFEST lexConcept
type: LexicalConcept
definition: The Building Block Manifest is a document that describes a Building Block configuration. For more details see the description for SPT2TS-123463 - BuildingBlockConfiguration "configuration.json" document .

Building Block Manifest
type: Form

BB
type: Acronym
type: LexicalEntry
acronym for: BUILDING--BLOCK label
canonical form: BB

BUILDING--BLOCK lexConcept
type: LexicalConcept
definition: 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.

Building Block
type: Form

BB
type: Form

Button
type: LexicalEntry
type: Word
canonical form: Button
sense: BUTTON lexSense

BUTTON lexConcept
type: LexicalConcept
definition: 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.

BUTTON lexConcept 2
type: LexicalConcept
definition: 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.

BUTTON lexConcept 3
type: LexicalConcept
definition: 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.

BUTTON lexConcept 4
type: LexicalConcept
definition: 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.

BUTTON lexConcept 5
type: LexicalConcept
definition: 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.

BUTTON lexConcept 6
type: LexicalConcept
definition: 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.

BUTTON lexConcept 7
type: LexicalConcept
definition: 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 lexConcept 8
type: LexicalConcept
definition: 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.

Button
type: Form

Buzzer
type: LexicalEntry
type: Word
canonical form: Buzzer
sense: BUZZER lexSense

BUZZER lexConcept
type: LexicalConcept
definition: Electrical device that makes a buzzing noise and is used to provide an audible warning.

BUZZER lexConcept 2
type: LexicalConcept
definition: Electrical device that makes a buzzing noise and is used to provide an audible warning.

BUZZER lexConcept 3
type: LexicalConcept
definition: Electrical device that makes a buzzing noise and is used to provide an audible warning.

BUZZER lexConcept 4
type: LexicalConcept
definition: Electrical device that makes a buzzing noise and is used to provide an audible warning.

BUZZER lexConcept 5
type: LexicalConcept
definition: Electrical device that makes a buzzing noise and is used to provide an audible warning.

BUZZER lexConcept 6
type: LexicalConcept
definition: Electrical device that makes a buzzing noise and is used to provide an audible warning.

BUZZER lexConcept 7
type: LexicalConcept
definition: Electrical device that makes a buzzing noise and is used to provide an audible warning.

BUZZER lexConcept 8
type: LexicalConcept
definition: Buzzer Electrical device that makes a buzzing noise and is used to provide an audible warning.

Buzzer
type: Form

C-DAS - Connected Driver Advisory System
type: LexicalEntry
type: MultiwordExpression
canonical form: C-DAS - Connected Driver Advisory System
sense: C-DAS-----CONNECTED--DRIVER--ADVISORY--SYSTEM lexSense

C-DAS-----CONNECTED--DRIVER--ADVISORY--SYSTEM lexConcept
type: LexicalConcept
definition: C-DAS - Connected Driver Advisory System

C-DAS - Connected Driver Advisory System
type: Form

C-Type Train - Vehicles with [c]ommon brake control in accordance with (separate...
type: LexicalEntry
type: MultiwordExpression
canonical form: C-Type Train - Vehicles with [c]ommon brake control in accordance with (separate...
sense: C-TYPE--TRAIN-----VEHICLES--WITH-- C OMMON--BRAKE--CONTROL--IN--ACCORDANCE--WITH--SEPARATE lexSense

C-TYPE--TRAIN-----VEHICLES--WITH-- C OMMON--BRAKE--CONTROL--IN--ACCORDANCE--WITH--SEPARATE lexConcept
type: LexicalConcept
definition: C-Type Train - Vehicles with [c]ommon brake control in accordance with SPT2ARC-4747 (separate control of dynamic and train air brake is not possible for ATO-OB). Typically, this term includes EMUs, DMUs, railbuses or electric railcars.

C-Type Train - Vehicles with [c]ommon brake control in accordance with (separate...
type: Form

CVR-OB
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CABIN--VOICE--RADIO--ON-BOARD label
canonical form: CVR-OB

CABIN--VOICE--RADIO--ON-BOARD lexConcept
type: LexicalConcept
definition: Cabin Voice Radio On-Board

Cabin Voice Radio On-Board
type: Form

CVR-OB
type: Form

Capability Meaning
type: LexicalEntry
type: MultiwordExpression
canonical form: Capability Meaning
sense: CAPABILITY--MEANING lexSense

CAPABILITY--MEANING lexConcept
type: LexicalConcept
definition: For the purposes of this document, a capability, in the framework of CMS, is considered as an interaction between processes, stakeholders and (IT) tools as illustrated in figure 5:

Capability Meaning
type: Form

Capability
type: LexicalEntry
type: Word
canonical form: Capability
sense: CAPABILITY lexSense

CAPABILITY lexConcept
type: LexicalConcept
definition: The ability of a system in performing a specific functionality

Capability
type: Form

CMS
type: Acronym
type: LexicalEntry
acronym for: CAPACITY--MANAGEMENT--SYSTEM label
canonical form: CMS

CAPACITY--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: Capacity Management system

Capacity Management system
type: Form

CMS
type: Form

CM
type: Acronym
type: LexicalEntry
acronym for: CAPACITY--MANAGEMENT label
canonical form: CM

CAPACITY--MANAGEMENT lexConcept
type: LexicalConcept
definition: In the railway context, capacity management refers to the strategic planning and operational control measures implemented to effectively manage the available resources and infrastructure of a railway system in order to meet the demand for transportation services. It involves assessing, optimizing, and maximizing the capacity of various components within the railway system, such as tracks, stations, trains, and associated facilities.

Capacity Management
type: Form

CM
type: Form

Capacity Planning
type: LexicalEntry
type: MultiwordExpression
canonical form: Capacity Planning
sense: CAPACITY--PLANNING lexSense

CAPACITY--PLANNING lexConcept
type: LexicalConcept
definition: Capacity Planning is an instrument to determining the total theoretically available capacity supply (max. number of journeys per direction) and compare it to demand. Capacity can be requested from long term to short term (ad hoc slot ordering). Capacity planning supports the planning along all-time horizons (strategic to short term).

Capacity Planning
type: Form

Capacity Plan
type: LexicalEntry
type: MultiwordExpression
canonical form: Capacity Plan
sense: CAPACITY--PLAN lexSense

CAPACITY--PLAN lexConcept
type: LexicalConcept
definition: The capacity plan comprises any planned capacity usage (traffic and construction works) at any point in time during the planning period. The aim is a consistent and conflict free capacity plan.

Capacity Plan
type: Form

Capacity Production
type: LexicalEntry
type: MultiwordExpression
canonical form: Capacity Production
sense: CAPACITY--PRODUCTION lexSense

CAPACITY--PRODUCTION lexConcept
type: LexicalConcept
definition: Capacity production is the implementation of the operational plan. Capacity production begins when the train starts its scheduled mission and ends with when it ends.

Capacity Production
type: Form

Capacity Restriction
type: LexicalEntry
type: MultiwordExpression
canonical form: Capacity Restriction
sense: CAPACITY--RESTRICTION lexSense

CAPACITY--RESTRICTION lexConcept
type: LexicalConcept
definition: Capacity restriction is a temporary full or partial unavailability of network infrastructure due to construction works, maintenance, inspection works or due to environmental influences and disruptions.

Capacity Restriction
type: Form

Capacity waste means:
type: LexicalEntry
type: MultiwordExpression
canonical form: Capacity waste means:
sense: CAPACITY--WASTE--MEANS lexSense

CAPACITY--WASTE--MEANS lexConcept
type: LexicalConcept
definition: * Paths are ordered without proper need, allocated and modified after allocation so that other ROCs cannot sensibly make use of them * Allocated paths are changed by RIMs after allocation due to the impact of TCRs by RIMs (same one allocating the path or another one on a different network) * An unnecessary number of paths are not allocated or are cancelled by RIMs due to poor alignment of several planned TCRs * Paths are not allocated or are cancelled by RIMs due to planned TCRs at times when little or no work is actually being carried out * Paths are not allocated or are cancelled by RIMs due to planned TCRs that were cancelled * Paths are not usable (or re-usable) due to the changes being communicated too late (i.e., due to paths being cancelled too late, TCRs cancelled, etc.)

Capacity waste means:
type: Form

Capacity-friendly behaviour means:
type: LexicalEntry
type: MultiwordExpression
canonical form: Capacity-friendly behaviour means:
sense: CAPACITY-FRIENDLY--BEHAVIOUR--MEANS lexSense

CAPACITY-FRIENDLY--BEHAVIOUR--MEANS lexConcept
type: LexicalConcept
definition: * A path confirmed is a commitment from both ROC and RIM, which should be kept after it has been allocated and accepted * Ordering capacity only when the market need for it need has been confirmed (ROC) * Give back the capacity as soon the market need changes, or other external requirements are known (ROC) * Defining the capacity for TCRs in a way that no more capacity than necessary is blocked – in dialogue between ROCs and RIMs * Planning the majority of TCRs and their impact to paths before path allocation (RIM) * Reducing TCRs in operational timetable to the minimum and planning their impact to paths/trains as early as possible (RIM) * Stabilising TCR planning - avoiding TCR cancellations that lead to a double loss of business, as well as massive re-planning of scheduled TCRs, which results in high efforts in operational planning (RIM)

Capacity-friendly behaviour means:
type: Form

Capacity
type: LexicalEntry
type: Word
canonical form: Capacity
sense: CAPACITY lexSense

CAPACITY lexConcept
type: LexicalConcept
definition: The total overall capability of the infrastructure that can be utilised by traffic or by maintenance. Capacity may apply to specific geographic sectors like stations or lines. Capacity usage must be requested, which results in capacity demand.

Capacity
type: Form

C2P
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CAPELLA2POLARION label
canonical form: C2P

CAPELLA2POLARION lexConcept
type: LexicalConcept
definition: The Capella2Polarion bridge is used to synchronise Capella model elements with Polarion work items. These work items have the prefix C2P in the name to indicate the specific purpose. More information can be found in here https://github.com/DSD-DBS/capella-polarion.

Capella2Polarion
type: Form

C2P
type: Form

CAPEX
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CAPITAL--EXPENDITURES label
canonical form: CAPEX

CAPITAL--EXPENDITURES lexConcept
type: LexicalConcept
definition: Capital Expenditures or Capital Expenses

Capital Expenditures
type: Form

CAPEX
type: Form

Carriage front end
type: LexicalEntry
type: MultiwordExpression
canonical form: Carriage front end
sense: CARRIAGE--FRONT--END lexSense

CARRIAGE--FRONT--END lexConcept
type: LexicalConcept
definition: It is represented by a point on the carriage floor along the longitudinal axis. This point is the most forward element belonging to the carriage. Its absolute position is expressed in a geocoordinate reference frame. It is used in the case the ASTP is not installed in the first vehicle.

Carriage front end
type: Form

Categorisation of national migration phases for a single country
type: LexicalEntry
type: MultiwordExpression
canonical form: Categorisation of national migration phases for a single country
sense: CATEGORISATION--OF--NATIONAL--MIGRATION--PHASES--FOR--A--SINGLE--COUNTRY lexSense

CATEGORISATION--OF--NATIONAL--MIGRATION--PHASES--FOR--A--SINGLE--COUNTRY lexConcept
type: LexicalConcept
definition: | LEGACY phase | ADAPTION phase | HARMONISATION phase | SERA CCS phase Description | No SP specification used in national propducts | Some SP specifications are used in national bespoke products, which show partly SPRA compliant behavior. This is especially done to connect them to future harmonized products, or to upgrade them to later harmonized products. | First fully harmonized products are available in Europe, and are procured "as is", together with the introduction of the harmonized operational processes that fit to them. Then more and more harmonized products are available. First full pilot lines with harmonized products are built. | A "core" of the harmonized architecture is defined and mandatory (by law, or because national bespoke solutions are not any more available in the market or not affordable for the architecture core). Railway Tasks | Define national requirements for bespoke products and installations. Optimisation of national products in "small steps". | Organize, negotiate and execute the integration of harmonized interfaces into national products | Buy harmonized products from the shelf for new lines, and procure also their connection to installed legacy systems. Introduce harmonized processes on the new lines. Perhaps upgrade old lines (optionally). | Buy all core products of the harmonized architecture from the shelf. And some preferred optional harmonized products (e.g. Tools). System Pillar Support | none | Provide first stable harmonized interface specifications and system requirement specifications | Provide and maintain operational rulebooks and system specification, (as recommendations, along STIP process). | Provide and maintain operational rulebooks and system specification, (as recommendations, along STIP process). Supplier Support | Provide and support national bespoke products installation projects and maintenance | Adapt national bespoke products plattforms early and perhaps partly to first harmonized SP specifications | Provide harm…

Categorisation of national migration phases for a single country
type: Form

CBM
type: LexicalEntry
type: Word
canonical form: CBM
sense: CBM lexSense

CBM lexConcept
type: LexicalConcept
definition: condition-based maintenance preventive maintenance based on the assessment of physical condition Note 1 to entry: The condition assessment may be by operator observation, conducted according to a schedule, or by condition monitoring (192-06-28 SPPRAMSS-4462 - condition monitoring, <of an item> ) of system parameters. [SOURCE: IEC 60050-192:2015, 192-06-07]

CBM
type: Form

CCF
type: LexicalEntry
type: Word
canonical form: CCF
sense: CCF lexSense

CCF lexConcept
type: LexicalConcept
definition: Common Cause Failures: failures of multiple items, which would otherwise be considered independent of one another, resulting from a single cause Note 1 to entry: Common cause failures can also be "common mode failures" (IEV 192-03-19). Note 2 to entry: The potential for common cause failures reduces the effectiveness of system redundancy. [SOURCE: IEC 60050-192:2015, 192-03-18]

CCF
type: Form

CCS Deployment
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS Deployment
sense: CCS--DEPLOYMENT lexSense

CCS--DEPLOYMENT lexConcept
type: LexicalConcept
definition: CCS Deployment refers to one physical deployment of a CCS System, that is uniquely identifiable with bbId, bbcId and bbcVersion. A CCS Deployment consists of the CCS hardware running the BBCs that are defined in a Top-Level BuildingBlockConfiguration (BBC) and its dependencies.

CCS Deployment
type: Form

CCS Evolution Path
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS Evolution Path
sense: CCS--EVOLUTION--PATH lexSense

CCS--EVOLUTION--PATH lexConcept
type: LexicalConcept
definition: A (CCS) Evolution Path, is a standardised upgrade process (extensions, enhancements, and error corrections) of the CCS architecture. The evolution process shall respect the need for sufficient stability, i.e. periods for sufficient return of investment for developed products and installed systems.

CCS Evolution Path
type: Form

CCS Feature (for MIG)
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS Feature (for MIG)
sense: CCS--FEATURE--FOR--MIG lexSense

CCS--FEATURE--FOR--MIG lexConcept
type: LexicalConcept
definition: A CCS Feature is a cohesive piece of system functionality.{comment:9} It can be at the top level of the system of interest, in which case it is equivalent to the concept of System Capability, or it can be at a lower level, in which case it is to be considered as a sub-feature of a higher-level feature.

CCS Feature (for MIG)
type: Form

CCS Feature
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS Feature
sense: CCS--FEATURE lexSense

CCS--FEATURE lexConcept
type: LexicalConcept
definition: A CCS Feature is a main/top-level function on System Level 3 for CCS. Examples: ATO GoA2, Cold Movement Detection, C-DAS Mixable onboard features (M/O means mandatory/optional) Feature(s) | M/O | Comment/Constrain/Condition/Version/Subfeature ETCS (ATP/ATO GoA1), only radio based | M | Compatibilty matrix onboard/trackside System Versions: Like today in TSI22. Assumption about phased out SV for the target system later on: Will be analysed in migration team. Inclusion of GSM-R in target architecture: To be analysed by MIG team with COM team, current TSI discussions to be included. ATO GoA 2,3 or 4 | O | RTO | O | Absolute Continuous Train Positioning | O | Option: Capabal to use trackside augmentation information (like EGNOS or map information) Train Integrity Information | O | Mandatory, if no trackside train detection exists Reliable train length information | O | Mandatory, if no trackside train detection exists Cold movement detection | O | DAC | O | C-DAS | O | Standard diagnostic interface | O | TMS onboard user interface | O | Fallback/light ATP system | O | To be discussed. Idependent and simplified mode or system that has minimal dependecies/maximized availability and allows safe rudimentory traffic in most degraded modes or for special vehicles Mixable trackside features in scope (M/O means mandatory/optional) Feature(s) | M/O | Comment/Constrain/Condition/Version/Subfeature ETCS onboard (ATP/ATO GoA1) | M | Radio based ETCS without lineside signals (no support for "overlay" installations. ATO GoA 2,3 or 4 | O | RTO | O | Postioning Augmentation Information | O | EGNOS, onboard map service Trackside Train detection | O | Mandatory, if trains/train units have no train-integrity, position reporting and reliable length information. Could be block sensors, geometric positions or point sensors. Onboard/trackside sensors can exist in parallel. DAC Control Applications | O | C-DAS Service | O | TMS services for onboard | O | e.g. request shunting route or possessi…

CCS Feature
type: Form

CCS Manifest
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS Manifest
sense: CCS--MANIFEST lexSense

CCS--MANIFEST lexConcept
type: LexicalConcept
definition: The CCS Manifest is a document that describes a CCS deployment configuration. For more details see the description for SPT2TS-123463 - BuildingBlockConfiguration "configuration.json" document .

CCS Manifest
type: Form

CCS System
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS System
sense: CCS--SYSTEM lexSense

CCS--SYSTEM lexConcept
type: LexicalConcept
definition: The control command and signalling (CCS) system covers signalling, train control, positioning equipment and telecommunications. {comment:1}

CCS System
type: Form

CCS-OB
type: LexicalEntry
type: Word
canonical form: CCS-OB
sense: CCS-OB lexSense

CCS-OB lexConcept
type: LexicalConcept
definition: Control-Command and Signalling - On Board

CCS-OB
type: Form

CCS-TRK
type: LexicalEntry
type: Word
canonical form: CCS-TRK
sense: CCS-TRK lexSense

CCS-TRK lexConcept
type: LexicalConcept
definition: Control-Command and Signalling - Track-side

CCS-TRK
type: Form

CCS/TMS Extended ERA Ontology (CCS/TMS Data Model)
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS/TMS Extended ERA Ontology (CCS/TMS Data Model)
sense: CCS TMS--EXTENDED--ERA--ONTOLOGY--CCS TMS--DATA--MODEL lexSense

CCS TMS--EXTENDED--ERA--ONTOLOGY--CCS TMS--DATA--MODEL lexConcept
type: LexicalConcept
definition: 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.

CCS/TMS Extended ERA Ontology (CCS/TMS Data Model)
type: Form

CEF Transport
type: LexicalEntry
type: MultiwordExpression
canonical form: CEF Transport
sense: CEF--TRANSPORT lexSense

CEF--TRANSPORT lexConcept
type: LexicalConcept
definition: Connecting Europe Facility Transport, funding tool of the European Commission

CEF Transport
type: Form

CPU
type: Acronym
type: LexicalEntry
acronym for: CENTRAL--PROCESSING--UNIT label
canonical form: CPU

CENTRAL--PROCESSING--UNIT lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Central Processing Unit

CENTRAL--PROCESSING--UNIT lexConcept 2
type: LexicalConcept
definition: Central Processing Unit

Central Processing Unit
type: Form

CPU
type: Form

CPU
type: Form

CTC
type: Acronym
type: LexicalEntry
acronym for: CENTRALIZED--TRAFFIC--CONTROL label
canonical form: CTC

CENTRALIZED--TRAFFIC--CONTROL lexConcept
type: LexicalConcept
definition: Centralized traffic control

Centralized traffic control
type: Form

CTC
type: Form

CA
type: Acronym
type: LexicalEntry
acronym for: CERTIFICATE--AUTHORITY label
canonical form: CA

CERTIFICATE--AUTHORITY lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Certificate Authority

Certificate Authority
type: Form

CA
type: Form

Certification body
type: LexicalEntry
type: MultiwordExpression
canonical form: Certification body
sense: CERTIFICATION--BODY lexSense

CERTIFICATION--BODY lexConcept
type: LexicalConcept
definition: Certification body means a body, responsible for the certification of entities in charge of maintenance or for certification of the entity or organization that fulfill maintenance functions referred to in points (b), (c) or (d) of Article 14(3) of Directive (EU) 2016/798, or parts of those functions

Certification body
type: Form

CCM
type: Acronym
type: LexicalEntry
acronym for: CHANGE--CONTROL--MANAGEMENT label
canonical form: CCM

CHANGE--CONTROL--MANAGEMENT lexConcept
type: LexicalConcept
definition: Change Control Management

Change Control Management
type: Form

CCM
type: Form

CR
type: Acronym
type: LexicalEntry
acronym for: CHANGE--REQUEST label
canonical form: CR

CHANGE--REQUEST lexConcept
type: LexicalConcept
definition: A formal request to modify existing software to correct an issue, add new functionality, or comply with updated standards or operational requirements.

CHANGE--REQUEST lexConcept 2
type: LexicalConcept
definition: Change Request

Change Request
type: Form

CR
type: Form

CR
type: Form

Changeability
type: LexicalEntry
type: Word
canonical form: Changeability
sense: CHANGEABILITY lexSense

CHANGEABILITY lexConcept
type: LexicalConcept
definition: Changeability refers to the ease with which a system can be modified or customized to meet specific requirements or adapt to new circumstances. It encompasses both minor changes, such as configuration adjustments, and more substantial modifications, such as adding or removing sub-systems.

Changeability
type: Form

claim, claims
type: LexicalEntry
type: MultiwordExpression
canonical form: claim, claims
sense: CLAIM--CLAIMS lexSense

CLAIM--CLAIMS lexConcept
type: LexicalConcept
definition: General notion to express that a track extent is used by or reserved for an object. For instance, a Movement Permission would claim its full track extent, including any Points in a certain position. Or a Usage Restriction Area claims its extent so that it cannot be used in a conflicting way (higher speed, for instance). A track extent consequently can only be used, if there is not any conflicting claim. This notion is more general and implementation-independent than lock which already somehow suggests a boolean flag and tempts to assume that there can only be one claim.

claim, claims
type: Form

Class A / B system
type: LexicalEntry
type: MultiwordExpression
canonical form: Class A / B system
sense: CLASS--A-- --B--SYSTEM lexSense

CLASS--A-- --B--SYSTEM lexConcept
type: LexicalConcept
definition: ERMTS is considered being a class A system whereas national legacy non-ERTMS systems are known as class B systems. In the frame of the migration to the future, harmonised CCS architecture based on harmonised operating rules, ERTMS systems based on earlier baselines are also treated as a kind of Class B system.

Class A / B system
type: Form

Class
type: LexicalEntry
type: Word
canonical form: Class
sense: CLASS lexSense

CLASS lexConcept
type: LexicalConcept
definition: An object is an instance of a class and a class is an object type.

Class
type: Form

CMD - Cold Movement Detector
type: LexicalEntry
type: MultiwordExpression
canonical form: CMD - Cold Movement Detector
sense: CMD-----COLD--MOVEMENT--DETECTOR lexSense

CMD-----COLD--MOVEMENT--DETECTOR lexConcept
type: LexicalConcept
definition: CMD - Cold Movement Detector

CMD - Cold Movement Detector
type: Form

COSMA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CO-OPERATIVE--SHORTENING--OF--MA label
canonical form: COSMA

CO-OPERATIVE--SHORTENING--OF--MA lexConcept
type: LexicalConcept
definition: 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
type: Form

COSMA
type: Form

CCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: COMMAND--CONTROL--SYSTEM--TSI label
canonical form: CCS

COMMAND--CONTROL--SYSTEM--TSI lexConcept
type: LexicalConcept
definition: Command Control System TSI

Command Control System TSI
type: Form

CCS
type: Form

COTS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: COMMERCIAL--OFF-THE-SHELF label
canonical form: COTS

COMMERCIAL--OFF-THE-SHELF lexConcept
type: LexicalConcept
definition: Commercial Off The Shelf (COTS) components and modules are assemblies, modules or parts designed for commercial applications for which the item manufacturer or vendor solely establishes and controls the specifications for performance, configuration, and reliability (including design, materials, processes, and testing) without additional requirements imposed by users and external organisations.

Commercial Off-the-Shelf
type: Form

COTS
type: Form

CBO
type: Acronym
type: LexicalEntry
acronym for: COMMON--BUSINESS--OBJECTIVE label
canonical form: CBO

COMMON--BUSINESS--OBJECTIVE lexConcept
type: LexicalConcept
definition: A generic target or high level objective defining the mandate of the System Pillar. They are derived by tasks and domains and are not created by them. They can be formulated freely.

COMMON--BUSINESS--OBJECTIVE lexConcept 2
type: LexicalConcept
definition: Common Business Objective

Common Business Objective
type: Form

CBO
type: Form

CBO
type: Form

CSM-RA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: COMMON--SAFETY--METHOD--FOR--RISK--EVALUATION--AND--ASSESSEMENT label
canonical form: CSM-RA

COMMON--SAFETY--METHOD--FOR--RISK--EVALUATION--AND--ASSESSEMENT lexConcept
type: LexicalConcept
definition: ‘common safety method for Risk evaluation and Assessement’ {comment:95} means the methods describing the assessment of safety levels and achievement of safety targets and compliance with other safety requirements; SPPRAMSS-619 - [CSM RA + (EU) No 1136/2015]

Common safety method for Risk evaluation and Assessement
type: Form

CSM-RA
type: Form

CVSS
type: Acronym
type: LexicalEntry
acronym for: COMMON--VULNERABILITY--SCORING--SYSTEM label
canonical form: CVSS

COMMON--VULNERABILITY--SCORING--SYSTEM lexConcept
type: LexicalConcept
definition: Common Vulnerability Scoring System

Common Vulnerability Scoring System
type: Form

CVSS
type: Form

CS
type: Acronym
type: LexicalEntry
acronym for: COMMUNICATION--SESSION label
canonical form: CS

COMMUNICATION--SESSION lexConcept
type: LexicalConcept
definition: The process of initiating and terminating an dialogue between Trackside (RBC) and On-board via data radio.{comment:155} This communication session is maintained a maximum time of 5 minutes in case of failed re-connection attempts. Note that it is a different concept to SPP-28485 - Missing cross-reference.

Communication Session
type: Form

CS
type: Form

CER
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: COMMUNITY--OF--EUROPEAN--RAILWAY--AND--INFRASTRUCTURE--COMPANIES label
canonical form: CER

COMMUNITY--OF--EUROPEAN--RAILWAY--AND--INFRASTRUCTURE--COMPANIES lexConcept
type: LexicalConcept
definition: Community of European Railway and Infrastructure Companies

Community of European Railway and Infrastructure Companies
type: Form

CER
type: Form

CEE
type: Acronym
type: LexicalEntry
acronym for: COMPARTMENT--EXECUTION--ENVIRONMENT label
canonical form: CEE

COMPARTMENT--EXECUTION--ENVIRONMENT lexConcept
type: LexicalConcept
definition: The Compartment Execution Environment refers to the combination of Physical Computing Element and Virtualisation Environment.

Compartment Execution Environment
type: Form

CEE
type: Form

CP
type: AbbreviatedForm
type: LexicalEntry
label: Comp
abbreviation for: COMPARTMENT label
canonical form: CP
canonical form: Comp

COMPARTMENT lexConcept
type: LexicalConcept
definition: A Compartment is a consistent, integrated entity comprising exactly one Runtime Environment Instance, at most one Safety Environment Replica, and Task Replicas of its respective Functional Applications. It can be deployed on either a Physical or a Virtual Computing Element. Previous definition: A Compartment is a consistent, integrated entity comprising exactly one Runtime Environment Instance, Safety Environment Task Replicas of at most one Safety Environment, and Functional Application Task Replicas of its respective Functional Applications. It can be deployed on either a Physical or a Virtual Computing Element.

COMPARTMENT lexConcept 2
type: LexicalConcept
definition: A Compartment{comment:4} is a consistent, integrated entity comprising exactly one Runtime Environment Instance, Safety Environment Task Replicas of at most one Safety Environment, and Functional Application Task Replicas of its respective Functional Applications. It can be deployed on either a Physical or a Virtual Computing Element.

Compartment
type: Form

CP
type: Form

Comp
type: Form

Competent Authority
type: LexicalEntry
type: MultiwordExpression
canonical form: Competent Authority
sense: COMPETENT--AUTHORITY lexSense

COMPETENT--AUTHORITY lexConcept
type: LexicalConcept
definition: Competent authority means any public authority or group of public authorities of a Member State or Member States which has the power to intervene in public passenger transport in a given geographical area or any body vested with such authority

Competent Authority
type: Form

Competent Local Authority
type: LexicalEntry
type: MultiwordExpression
canonical form: Competent Local Authority
sense: COMPETENT--LOCAL--AUTHORITY lexSense

COMPETENT--LOCAL--AUTHORITY lexConcept
type: LexicalConcept
definition: Competent local authority means any competent authority whose geographical area of competence is not national

Competent Local Authority
type: Form

Complete Train Cancellation
type: LexicalEntry
type: MultiwordExpression
canonical form: Complete Train Cancellation
sense: COMPLETE--TRAIN--CANCELLATION lexSense

COMPLETE--TRAIN--CANCELLATION lexConcept
type: LexicalConcept
definition: Completely cancel the train journey and remove the train from the Forecast calculations

Complete Train Cancellation
type: Form

Component Exchange
type: LexicalEntry
type: MultiwordExpression
canonical form: Component Exchange
sense: COMPONENT--EXCHANGE lexSense

COMPONENT--EXCHANGE lexConcept
type: LexicalConcept
definition: A connection between two components that allows them to convey functional exchange and their exchange items. In the System Pillar component exchange is used as SPPR-2601 - Interface.

Component Exchange
type: Form

CE
type: Acronym
type: LexicalEntry
acronym for: COMPUTING--ELEMENT label
canonical form: CE

COMPUTING--ELEMENT lexConcept
type: LexicalConcept
definition: The Computing Element provides physical or virtual compute resources.

Computing Element
type: Form

CE
type: Form

CEnv
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: COMPUTING--ENVIRONMENT label
canonical form: CEnv

COMPUTING--ENVIRONMENT lexConcept
type: LexicalConcept
definition: A computing environment encompasses the hardware, software, network resources, and services that enable the deployment, operation, and management of applications or services. Computing environment includes the application execution environment and the computing platform.

Computing Environment
type: Form

CEnv
type: Form

CPHW
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: COMPUTING--PLATFORM--HARDWARE label
canonical form: CPHW

COMPUTING--PLATFORM--HARDWARE lexConcept
type: LexicalConcept
definition: Physical Computing Elements and network hardware.

Computing Platform Hardware
type: Form

CPHW
type: Form

CPSW
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: COMPUTING--PLATFORM--SOFTWARE label
canonical form: CPSW

COMPUTING--PLATFORM--SOFTWARE lexConcept
type: LexicalConcept
definition: Provides platform-level services (e.g., resource allocation, compartment execution environment).

Computing Platform Software
type: Form

CPSW
type: Form

CP
type: Acronym
type: LexicalEntry
acronym for: COMPUTING--PLATFORM label
canonical form: CP

COMPUTING--PLATFORM lexConcept
type: LexicalConcept
definition: 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.

Computing Platform
type: Form

CP
type: Form

Concept Aspect
type: LexicalEntry
type: MultiwordExpression
canonical form: Concept Aspect
sense: CONCEPT--ASPECT lexSense

CONCEPT--ASPECT lexConcept
type: LexicalConcept
definition: A{comment:122} content for sketching concepts regarding analysis purposes which is linked to requirements.

Concept Aspect
type: Form

CONUSE
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CONCEPT--HOW--TO--USE--THE--SYSTEM label
canonical form: CONUSE

CONCEPT--HOW--TO--USE--THE--SYSTEM lexConcept
type: LexicalConcept
definition: Concept how to use the system

Concept how to use the system
type: Form

CONUSE
type: Form

CONEMP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CONCEPT--OF--EMPLOYMENT label
canonical form: CONEMP

CONCEPT--OF--EMPLOYMENT lexConcept
type: LexicalConcept
definition: Concept of Employment

Concept of Employment
type: Form

CONEMP
type: Form

CONOPS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CONCEPT--OF--OPERATIONS label
canonical form: CONOPS

CONCEPT--OF--OPERATIONS lexConcept
type: LexicalConcept
definition: Concept of Operations

Concept of Operations
type: Form

CONOPS
type: Form

Conceptual Data Model
type: LexicalEntry
type: MultiwordExpression
canonical form: Conceptual Data Model
sense: CONCEPTUAL--DATA--MODEL lexSense

CONCEPTUAL--DATA--MODEL lexConcept
type: LexicalConcept
definition: The conceptual data model is the information model of the railway system. It captures domain knowledge by defining concepts that describe the railway system. The model includes relations between concepts.

Conceptual Data Model
type: Form

Conceptual Glossary
type: LexicalEntry
type: MultiwordExpression
canonical form: Conceptual Glossary
sense: CONCEPTUAL--GLOSSARY lexSense

CONCEPTUAL--GLOSSARY lexConcept
type: LexicalConcept
definition: Container of concepts, typically class model illustrating a lexical definition, incl. relationships between concepts. May also be imported or authored by the project. Conceptual glossaries are referred to by lexcial glossaries.

Conceptual Glossary
type: Form

condition monitoring, <of an item>
type: LexicalEntry
type: MultiwordExpression
canonical form: condition monitoring, <of an item>
sense: CONDITION--MONITORING--<OF--AN--ITEM> lexSense

CONDITION--MONITORING--<OF--AN--ITEM> lexConcept
type: LexicalConcept
definition: obtaining information about physical state or operational parameters Note 1 to entry: Condition monitoring is used to determine when preventive maintenance may be required. Note 2 to entry: Condition monitoring may be conducted automatically during operation or at planned intervals. Note 3 to entry: Condition monitoring methods include: vibration analysis, tribology and thermography. [SOURCE: IEC 60050-192:2015, 192-06-28]

condition monitoring, <of an item>
type: Form

Conditional Emergency Stop CES
type: LexicalEntry
type: MultiwordExpression
canonical form: Conditional Emergency Stop CES
sense: CONDITIONAL--EMERGENCY--STOP--CES lexSense

CONDITIONAL--EMERGENCY--STOP--CES lexConcept
type: LexicalConcept
definition: Conditional Emergency Stop CES Conditional Emergency Stop is the emergency stop triggered by a shortened MA (no TR Mode) using message 15.

Conditional Emergency Stop CES
type: Form

CI
type: Acronym
type: LexicalEntry
acronym for: CONFIDENCE--INTERVAL label
canonical form: CI

CONFIDENCE--INTERVAL lexConcept
type: LexicalConcept
definition: The position, speed, acceleration interval within which the ASTP assumes the true train position, speed, acceleration is, with a defined probability.

Confidence Interval
type: Form

CI
type: Form

Confidentiality
type: LexicalEntry
type: Word
canonical form: Confidentiality
sense: CONFIDENTIALITY lexSense

CONFIDENTIALITY lexConcept
type: LexicalConcept
definition: Property that information is not made available or disclosed to unauthorized individuals, entities, or processes (source: ISO 27000-2018 )

Confidentiality
type: Form

Config Item
type: LexicalEntry
type: MultiwordExpression
canonical form: Config Item
sense: CONFIG--ITEM lexSense

CONFIG--ITEM lexConcept
type: LexicalConcept
definition: The name of a template that is used for System Pillar results

Config Item
type: Form

Configuration Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Configuration Data
sense: CONFIGURATION--DATA lexSense

CONFIGURATION--DATA lexConcept
type: LexicalConcept
definition: 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.

Configuration Data
type: Form

CI
type: Acronym
type: LexicalEntry
acronym for: CONFIGURATION--ITEM label
canonical form: CI

CONFIGURATION--ITEM lexConcept
type: LexicalConcept
definition: A configuration item refers to any resource within a system that needs to be managed and controlled in order to support the delivery of products or services. It can be an unchangeable item such as a software (provided by the originator it remains unchanged until installation), or it can be a changeable item such as a parametrisation file (provided by the originator it may be changed by a third party before installation). Configuration items are typically identified, documented, and tracked throughout their lifecycle to ensure proper control, maintenance, and change management. They are often part of a configuration management system or database, which helps in organizing and managing the configuration items and their relationships. The purpose of managing configuration items is to have a clear understanding of the resources that make up a system, their interdependencies, and their characteristics. This enables effective control, planning, and decision-making, particularly in areas such as asset management, change management, and problem resolution.

Configuration item
type: Form

CI
type: Form

Configuration Management Concept
type: LexicalEntry
type: MultiwordExpression
canonical form: Configuration Management Concept
sense: CONFIGURATION--MANAGEMENT--CONCEPT lexSense

CONFIGURATION--MANAGEMENT--CONCEPT lexConcept
type: LexicalConcept
definition: The Configuration Management Concept is a solution oriented description of the Configuration Management Process: it defines all the technical solutions needed for the concrete implementation of the Configuration Management Process.

Configuration Management Concept
type: Form

Configuration Management Process
type: LexicalEntry
type: MultiwordExpression
canonical form: Configuration Management Process
sense: CONFIGURATION--MANAGEMENT--PROCESS lexSense

CONFIGURATION--MANAGEMENT--PROCESS lexConcept
type: LexicalConcept
definition: The Configuration Management Process captures all concrete activities along the complete configuration management chain: from the Building Block realisation (by the Building Block Supplier(s)), to the integration into a specific System Instance (by the Integrator(s)), to the distribution to the field (by the Operator), and the actual activation (going into operation) in the field (it includes also on a train). The Configuration Management Process is a solution agnostic term that collects all activities needed for the Configuration Management.

Configuration Management Process
type: Form

Configuration Management
type: LexicalEntry
type: MultiwordExpression
canonical form: Configuration Management
sense: CONFIGURATION--MANAGEMENT lexSense

CONFIGURATION--MANAGEMENT lexConcept
type: LexicalConcept
definition: Configuration Management refers to the management of all Configuration Items of a physical instance of a System (e.g. trains or trackside CCS). From a process point of view, it covers activities along the complete chain, from the Building Block Supplier(s) to the Integrators, the Operator, and the actual Deployment being operational.

Configuration Management
type: Form

CREP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CONFIGURATION--REPOSITORY label
canonical form: CREP

CONFIGURATION--REPOSITORY lexConcept
type: LexicalConcept
definition: The Configuration Repository System is a repository to store SPT2TS-127779 - Configuration Data. Repositories could access other repositories to add missing items recursively. For this reason, different repositories can exist {comment:40} on the operator level (IM/RU) storing the SPT2TS-127776 - Infrastructure data or SPT2TS-127777 - Vehicle data and it could be also on the level of the integrator/ supplier storing SPT2TS-127775 - Software Configuration Data. Note: The Configuration Repository is also referred to as "Digital Registry", in the context of single source of truth for CCS/TMS subsystem configuration data. However, the term "Digital Registry" is avoided since it collides with different meanings and expectations within the overall architecture (e.g. DR for runtime operations, which is not the case here). Note: According to the Logical Concept for Configuration (SMI V3), the BuildingBlockConfigurations (BBC, data item) must conform to the directory structure or REST API structure defined in configuration logical concept, including structure, (intransparent) payload and configuration.json and configurationSafe.json according to the schema defined.

Configuration Repository
type: Form

CREP
type: Form

Configuration View
type: LexicalEntry
type: MultiwordExpression
canonical form: Configuration View
sense: CONFIGURATION--VIEW lexSense

CONFIGURATION--VIEW lexConcept
type: LexicalConcept
definition: The configuration view exposes map data that{comment:1} fit the purpose of a given use case, e.g. ATO, TMS, ETCS L2/3 and delivers the information for the configuration of the subsystems that realise the use case.

Configuration View
type: Form

Configuration
type: LexicalEntry
type: Word
canonical form: Configuration
sense: CONFIGURATION lexSense

CONFIGURATION lexConcept
type: LexicalConcept
definition: Refers to an allocation of systems with MDS units. This allocation could be selected and applied by the MDS (Display Manager). For each vehicle type there is a specific configuration of business applications that use the MDS. A generic configuration is only possible inside one vehicle type to describe the maximum number of involved applications.

Configuration
type: Form

Conflict
type: LexicalEntry
type: Word
canonical form: Conflict
sense: CONFLICT lexSense

CONFLICT lexConcept
type: LexicalConcept
definition: A conflict is any difference between the operational plan and the forecast, regardless of any actual need for intervention to resolve it.

Conflict
type: Form

Connection Change
type: LexicalEntry
type: MultiwordExpression
canonical form: Connection Change
sense: CONNECTION--CHANGE lexSense

CONNECTION--CHANGE lexConcept
type: LexicalConcept
definition: Change the time and/or location of a connecting train

Connection Change
type: Form

Considered Fleet Type
type: LexicalEntry
type: MultiwordExpression
canonical form: Considered Fleet Type
sense: CONSIDERED--FLEET--TYPE lexSense

CONSIDERED--FLEET--TYPE lexConcept
type: LexicalConcept
definition: type of rolling stock regarding a certain usecas, for example cargo trains, passenger trains, high speed passenger trains

Considered Fleet Type
type: Form

Considered Track Type
type: LexicalEntry
type: MultiwordExpression
canonical form: Considered Track Type
sense: CONSIDERED--TRACK--TYPE lexSense

CONSIDERED--TRACK--TYPE lexConcept
type: LexicalConcept
definition: type of track regarding a certain usecase, for example cargo line, high speed line, regional line

Considered Track Type
type: Form

Consist
type: LexicalEntry
type: Word
canonical form: Consist
sense: CONSIST lexSense

CONSIST lexConcept
type: LexicalConcept
definition: A consist is a rail vehicle or a sequence of coupled rail vehicles.

Consist
type: Form

Consolidated Glossary
type: LexicalEntry
type: MultiwordExpression
canonical form: Consolidated Glossary
sense: CONSOLIDATED--GLOSSARY lexSense

CONSOLIDATED--GLOSSARY lexConcept
type: LexicalConcept
definition: A SPPR-5436 - Lexical Glossary is called consolidated if all contained items are not contradictory nor ambiguous toward other glossaries of System Pillar. All possible ambiguities are resolved by means of context information added to the definitions. A consolidated glossary provides a safe basis for the context underlying its namespace. This supports efficient communication in expert groups. See SPPR-5313 - Consolidate the glossary items.

Consolidated Glossary
type: Form

Constraint
type: LexicalEntry
type: Word
canonical form: Constraint
sense: CONSTRAINT lexSense

CONSTRAINT lexConcept
type: LexicalConcept
definition: Constraints are requirements that limit the solution space beyond what is necessary to meet the given functional requirements and quality (or non-functional) requirements. Constraints should be classified according to its nature: Technical, Legal, Organisational, Stakeholders, Cultural, Enviromental - e.g. Project Requirements and SEMP related rules are organisational constraints -. 'Constraint' for requirement management (this definition) is not strictly the same as a model element 'constraint' used in Capella modelling, which is a "limitation of applicabilty of a design workitem" within a specific model view or perspective. See also from SPPR-2205 - P9.6 Explain engineering content with helper workitems : "A Constraint is typically linked to model elements like processes or functional chains. It limits limits the applicability of something or defines conditions for something."

Constraint
type: Form

Context model
type: LexicalEntry
type: MultiwordExpression
canonical form: Context model
sense: CONTEXT--MODEL lexSense

CONTEXT--MODEL lexConcept
type: LexicalConcept
definition: A context model is a window to the underlying comprehensive linked set of data types. The context model prescribes the content of a view. A context model is platform-independent, i.e. not designed with a particular technology in mind.

Context model
type: Form

CI/CD
type: Acronym
type: LexicalEntry
acronym for: CONTINUOUS--INTEGRATION-- --CONTINUOUS--DEPLOYMENT label
canonical form: CI/CD

CONTINUOUS--INTEGRATION-- --CONTINUOUS--DEPLOYMENT lexConcept
type: LexicalConcept
definition: Continuous Integration / Continuous Deployment

Continuous Integration / Continuous Deployment
type: Form

CI/CD
type: Form

CCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CONTROL--COMMAND--AND--SIGNALING label
canonical form: CCS

CONTROL--COMMAND--AND--SIGNALING lexConcept
type: LexicalConcept
definition: Control Command and Signaling

Control Command and Signaling
type: Form

CCS
type: Form

CCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CONTROL--COMMAND--AND--SIGNALLING label
canonical form: CCS

CONTROL--COMMAND--AND--SIGNALLING lexConcept
type: LexicalConcept
definition: Control, Command and Signalling

Control, Command and Signalling
type: Form

CCS
type: Form

CCS OB
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CONTROL-COMMAND--AND--SIGNALLING-----ONBOARD label
canonical form: CCS OB

CONTROL-COMMAND--AND--SIGNALLING-----ONBOARD lexConcept
type: LexicalConcept
definition: CCS OB refers to the SPLI-372 - On-board control-command and signalling part of the SPLI-83 - Control-Command and Signalling

Control-Command and Signalling - Onboard
type: Form

CCS OB
type: Form

CCS TRK
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CONTROL-COMMAND--AND--SIGNALLING-----TRACKSIDE label
canonical form: CCS TRK

CONTROL-COMMAND--AND--SIGNALLING-----TRACKSIDE lexConcept
type: LexicalConcept
definition: CCS TRK refers to the SPLI-375 - Trackside control-command and signalling part of the SPLI-83 - Control-Command and Signalling.

Control-Command and Signalling - Trackside
type: Form

CCS TRK
type: Form

CCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CONTROL-COMMAND--AND--SIGNALLING label
canonical form: CCS

CONTROL-COMMAND--AND--SIGNALLING lexConcept
type: LexicalConcept
definition: Control-Command and Signalling

CONTROL-COMMAND--AND--SIGNALLING lexConcept 2
type: LexicalConcept
definition: Control-Command and Signalling

CONTROL-COMMAND--AND--SIGNALLING lexConcept 3
type: LexicalConcept
definition: Control-Command and Signalling

Control-Command and Signalling
type: Form

CCS
type: Form

CCS
type: Form

CCS
type: Form

Controller Unit
type: LexicalEntry
type: MultiwordExpression
canonical form: Controller Unit
sense: CONTROLLER--UNIT lexSense

CONTROLLER--UNIT lexConcept
type: LexicalConcept
definition: 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}

CONTROLLER--UNIT lexConcept 2
type: LexicalConcept
definition: 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 lexConcept 3
type: LexicalConcept
definition: 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 lexConcept 4
type: LexicalConcept
definition: 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 lexConcept 5
type: LexicalConcept
definition: 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 lexConcept 6
type: LexicalConcept
definition: 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 lexConcept 7
type: LexicalConcept
definition: 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 lexConcept 8
type: LexicalConcept
definition: 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.

Controller Unit
type: Form

Coordination
type: LexicalEntry
type: Word
canonical form: Coordination
sense: COORDINATION lexSense

COORDINATION lexConcept
type: LexicalConcept
definition: Coordination means the process through which the infra structure manager and applicants will attempt to resolve situations in which there are conflicting applications for infrastructure capacity.

Coordination
type: Form

CBV
type: Acronym
type: LexicalEntry
acronym for: CORE--BUSINESS--VOCABULARY label
canonical form: CBV

CORE--BUSINESS--VOCABULARY lexConcept
type: LexicalConcept
definition: Core Business Vocabulary

Core Business Vocabulary
type: Form

CBV
type: Form

corrective maintenance
type: LexicalEntry
type: MultiwordExpression
canonical form: corrective maintenance
sense: CORRECTIVE--MAINTENANCE lexSense

CORRECTIVE--MAINTENANCE lexConcept
type: LexicalConcept
definition: Maintenance carried out after fault detection to effect restoration Note 1 to entry: Corrective maintenance of software invariably involves some modification. [SOURCE: IEC 60050-192:2015, 192-06-06]

corrective maintenance
type: Form

CBA
type: Acronym
type: LexicalEntry
acronym for: COST--BENEFIT--ANALYSIS label
canonical form: CBA

COST--BENEFIT--ANALYSIS lexConcept
type: LexicalConcept
definition: Cost Benefit Analysis

Cost Benefit Analysis
type: Form

CBA
type: Form

Coupling Speed
type: LexicalEntry
type: MultiwordExpression
canonical form: Coupling Speed
sense: COUPLING--SPEED lexSense

COUPLING--SPEED lexConcept
type: LexicalConcept
definition: 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
type: Form

XFN
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: CROSS--FUNCTIONAL label
canonical form: XFN

CROSS--FUNCTIONAL lexConcept
type: LexicalConcept
definition: Cross functional

Cross functional
type: Form

XFN
type: Form

Cross-Acceptance
type: LexicalEntry
type: Word
canonical form: Cross-Acceptance
sense: CROSS-ACCEPTANCE lexSense

CROSS-ACCEPTANCE lexConcept
type: LexicalConcept
definition: Status{comment:1393} achieved by a product that has been accepted by one authority to the relevant standards and is acceptable to other authorities without the necessity for further assessment, see [IEC 60050-821:2017,{comment:1335} 821-12-15].

Cross-Acceptance
type: Form

CSM-ALSP
type: LexicalEntry
type: Word
canonical form: CSM-ALSP
sense: CSM-ALSP lexSense

CSM-ALSP lexConcept
type: LexicalConcept
definition: Common Safety Methods for assessing the safety level and the safety performance of railway operators [SOURCE: RECOMMENDATION ERA1219 OF THE EUROPEAN UNION AGENCY FOR RAILWAYS]

CSM-ALSP
type: Form

CST
type: LexicalEntry
type: Word
canonical form: CST
sense: CST lexSense

CST lexConcept
type: LexicalConcept
definition: ‘common safety targets’ (CSTs) means the minimum safety levels that are to be reached by the system as a whole, and where feasible, by different parts of the Union rail system (such as the conventional rail system, the high-speed rail system, long railway tunnels or lines solely used for freight transport); SPPRAMSS-337 - [Directive (EU) 2016/798]

CST
type: Form

customer
type: LexicalEntry
type: Word
canonical form: customer
sense: CUSTOMER lexSense

CUSTOMER lexConcept
type: LexicalConcept
definition: a customer is an entity who buys and owns railway equipments and services from manufacturers (also called supplier) or engineering companies (e.g. Rus, IMs).

customer
type: Form

CVR (TRD Display)
type: LexicalEntry
type: MultiwordExpression
canonical form: CVR (TRD Display)
sense: CVR--TRD--DISPLAY lexSense

CVR--TRD--DISPLAY lexConcept
type: LexicalConcept
definition: The display associated to this system is called TRD (Train Radio Display) in UIC-612. The ergonomics of this system is also defined in UIC-612-4.The TRD is located on the left side of the cab according to UIC-612-0, EN 16186-2 (chapter 7.21).The SIL is SIL0 (Basic Integrity).Information is presented on demand when triggered by the driver or when external actors (passenger, traffic agent,etc.) call the driver. Current communication between CVR and TRD is supplier-specific? To facilitate the deployment of the MDS solution, a migration to a generic communication used also by other systems should be considered.

CVR--TRD--DISPLAY lexConcept 2
type: LexicalConcept
definition: The display associated to this system is called TRD (Train Radio Display) in UIC-612. The ergonomics of this system isalso defined in UIC-612-4.The TRD is located on the left side of the cab according to UIC-612-0, EN 16186-2 (chapter 7.21).The SIL is SIL0 (Basic Integrity).Information is presented on demand when triggered by the driver or when external actors (passenger, traffic agent,etc.) call the driver. Current communication between CVR and TRD is supplier-specific? To facilitate the deployment of the MDS solution, a migration to a generic communication used also by other systems should be considered.

CVR (TRD Display)
type: Form

DAC - Digital Automatic Coupling
type: LexicalEntry
type: MultiwordExpression
canonical form: DAC - Digital Automatic Coupling
sense: DAC-----DIGITAL--AUTOMATIC--COUPLING lexSense

DAC-----DIGITAL--AUTOMATIC--COUPLING lexConcept
type: LexicalConcept
definition: DAC - Digital Automatic Coupling

DAC - Digital Automatic Coupling
type: Form

DAC CU
type: LexicalEntry
type: MultiwordExpression
canonical form: DAC CU
sense: DAC--CU lexSense

DAC--CU lexConcept
type: LexicalConcept
definition: * 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.

DAC CU
type: Form

Danger Point
type: LexicalEntry
type: MultiwordExpression
canonical form: Danger Point
sense: DANGER--POINT lexSense

DANGER--POINT lexConcept
type: LexicalConcept
definition: The location beyond the End of Movement Authority that can be reached by the front of the train without creating a hazardous situation. /ETCS/ - SUBSET-023

Danger Point
type: Form

Danger Zone
type: LexicalEntry
type: MultiwordExpression
canonical form: Danger Zone
sense: DANGER--ZONE lexSense

DANGER--ZONE lexConcept
type: LexicalConcept
definition: The area in the trackside in which the track path shall be uninterrupted and unobstructed at the time a train runs over it.{comment:101} (image: diagram_20231212-1333.02592.mxg.svg) Note as a representation, it has the dimensions of the trackside asset (within its boundaries).

Danger Zone
type: Form

DAS - Driver Advisory System
type: LexicalEntry
type: MultiwordExpression
canonical form: DAS - Driver Advisory System
sense: DAS-----DRIVER--ADVISORY--SYSTEM lexSense

DAS-----DRIVER--ADVISORY--SYSTEM lexConcept
type: LexicalConcept
definition: DAS - Driver Advisory System

DAS - Driver Advisory System
type: Form

DAS-OB - Driver Advisory System On Board
type: LexicalEntry
type: MultiwordExpression
canonical form: DAS-OB - Driver Advisory System On Board
sense: DAS-OB-----DRIVER--ADVISORY--SYSTEM--ON--BOARD lexSense

DAS-OB-----DRIVER--ADVISORY--SYSTEM--ON--BOARD lexConcept
type: LexicalConcept
definition: DAS-OB - Driver Advisory System On Board

DAS-OB-----DRIVER--ADVISORY--SYSTEM--ON--BOARD lexConcept 2
type: LexicalConcept
definition: DAS-OB - Driver Advisory System On Board

DAS-OB - Driver Advisory System On Board
type: Form

Data Class
type: LexicalEntry
type: MultiwordExpression
canonical form: Data Class
sense: DATA--CLASS lexSense

DATA--CLASS lexConcept
type: LexicalConcept
definition: A data class is a structure that defines the data and their elementary properties.

Data Class
type: Form

DLP
type: Acronym
type: LexicalEntry
acronym for: DATA--LOSS--PREVENTION label
canonical form: DLP

DATA--LOSS--PREVENTION lexConcept
type: LexicalConcept
definition: Data loss prevention

Data loss prevention
type: Form

DLP
type: Form

Data Model Layer
type: LexicalEntry
type: MultiwordExpression
canonical form: Data Model Layer
sense: DATA--MODEL--LAYER lexSense

DATA--MODEL--LAYER lexConcept
type: LexicalConcept
definition: Note: informelle Gruppierung im Modell (analog zur RCA tiers), für Kommunikation/Verständnis A data model layer offers a view of the information as needed by, and as limited by a functional domain such as topology, geometry, signalling, gauge, etc.

Data Model Layer
type: Form

PREP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DATA--PREPARATION label
canonical form: PREP

DATA--PREPARATION lexConcept
type: LexicalConcept
definition: 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.

Data Preparation
type: Form

PREP
type: Form

DBMS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DATABASE--MANAGEMENT--SYSTEM label
canonical form: DBMS

DATABASE--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: Database Management System

Database Management System
type: Form

DBMS
type: Form

Decision
type: LexicalEntry
type: Word
canonical form: Decision
sense: DECISION lexSense

DECISION lexConcept
type: LexicalConcept
definition: A decision is a single action intended to make a modification the operational plan.

DECISION lexConcept 2
type: LexicalConcept
definition: Link to workitems / documents, that shall be decided. Is assigned to the coregroup conveners.

Decision
type: Form

Decommissioning
type: LexicalEntry
type: Word
canonical form: Decommissioning
sense: DECOMMISSIONING lexSense

DECOMMISSIONING lexConcept
type: LexicalConcept
definition: Withdrawing systems or components from service and dismantle it

Decommissioning
type: Form

Definition Earliest Time Constraint for Pass Event - MP Limit Marker:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition Earliest Time Constraint for Pass Event - MP Limit Marker:
sense: DEFINITION--EARLIEST--TIME--CONSTRAINT--FOR--PASS--EVENT-----MP--LIMIT--MARKER lexSense

DEFINITION--EARLIEST--TIME--CONSTRAINT--FOR--PASS--EVENT-----MP--LIMIT--MARKER lexConcept
type: LexicalConcept
definition: Definition Earliest Time Constraint for Pass Event - MP Limit Marker: * The Earliest Time Constraint for a Pass Event defines the point in time that must be reached according to the scheduled departure time for that Pass Event. * This constraint prevents MP requests from being send too early and MP Extends from being requested longer than necessary, which could otherwise lead to incorrect train sequencing (for example, if a train is running earlier than scheduled).

Definition Earliest Time Constraint for Pass Event - MP Limit Marker:
type: Form

Definition Earliest Time Constraint for Stop Event - MP Limit Marker:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition Earliest Time Constraint for Stop Event - MP Limit Marker:
sense: DEFINITION--EARLIEST--TIME--CONSTRAINT--FOR--STOP--EVENT-----MP--LIMIT--MARKER lexSense

DEFINITION--EARLIEST--TIME--CONSTRAINT--FOR--STOP--EVENT-----MP--LIMIT--MARKER lexConcept
type: LexicalConcept
definition: Definition Earliest Time Constraint for Stop Event - MP Limit Marker: * The Earliest Time Constraint for a Stop Event defines the point in time that must be reached according to the scheduled departure time for that Stop Event. * This constraint prevents MP requests from being send too early and MP Extends from being requested longer than necessary, which could otherwise lead to incorrect train sequencing (for example, if a train is running earlier than scheduled).

Definition Earliest Time Constraint for Stop Event - MP Limit Marker:
type: Form

Definition Earliest Time Constraint Pass Event :
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition Earliest Time Constraint Pass Event :
sense: DEFINITION--EARLIEST--TIME--CONSTRAINT--PASS--EVENT lexSense

DEFINITION--EARLIEST--TIME--CONSTRAINT--PASS--EVENT lexConcept
type: LexicalConcept
definition: Definition Earliest Time Constraint Pass Event for STA Request:{comment:99}{comment:101} * The Earliest Time Constraint Pass Event is an additional constraint, which is only calculated, if there is Movement Event of type Pass (Operational Plan Movement) between the STA and the calculated Pass Position Constraint. * The Earliest Time Constraint Pass Event is needed to not trigger the STA Request too early in case of a Pass Event between the STA and the calculated Pass Position Constraint. * The Earliest Time Constraint Pass Event defines a point in time that must be reached to trigger the STA Request. Triggering of STA Request: * The Earliest Time Constraint Pass Event and the Pass Position Constraint for a specific STA Request do apply simultaneously. This means that both constraints need to be resolved to trigger the STA Request. * If there are multiple Movement Events of type Stop or Pass planned between the calculated Pass Position Constraint and the specific STA, only the one closest to the specific STA will be used; the others are not relevant. This is because the closest Movement Event is assumed to have the most accurate scheduled time for the specific STA.

Definition Earliest Time Constraint Pass Event :
type: Form

Definition Earliest Time Constraint Stop Event:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition Earliest Time Constraint Stop Event:
sense: DEFINITION--EARLIEST--TIME--CONSTRAINT--STOP--EVENT lexSense

DEFINITION--EARLIEST--TIME--CONSTRAINT--STOP--EVENT lexConcept
type: LexicalConcept
definition: Definition Earliest Time Constraint Stop Event for STA Request: * The Earliest Time Constraint Stop Event is an additional constraint, which is only calculated, if there is Movement Event of type Stop (Operational Plan Movement) between the STA and the calculated Pass Position Constraint. * The Earliest Time Constraint Stop Event is needed to not trigger the STA Request too early in case of a Stop Event between the STA and the calculated Pass Position Constraint. * The Earliest Time Constraint Stop Event defines a point in time that must be reached to trigger the STA Request. Triggering of STA Request: * The Earliest Time Constraint Stop Event and the Pass Position Constraint for a specific STA Request do apply simultaneously. This means that both constraints need to be resolved to trigger the STA Request. * If there are multiple Movement Events of type Stop or Pass planned between the calculated Pass Position Constraint and the specific STA, only the one closest to the specific STA will be used; the others are not relevant. This is because the closest Movement Event is assumed to have the most accurate scheduled time for the specific STA.

Definition Earliest Time Constraint Stop Event:
type: Form

Definition of Blocking Element:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of Blocking Element:
sense: DEFINITION--OF--BLOCKING--ELEMENT lexSense

DEFINITION--OF--BLOCKING--ELEMENT lexConcept
type: LexicalConcept
definition: Definition of Blocking Element: * A Blocking Element is an element on the specified track path over which the MP shall not be extended.{comment:29}{comment:54} * A Blocking Elements are of type Switchable Trackside Asset, TrainObject, Unresolved Trackbound Object, Restriction Area, Stop Event, Pass Event or Maximum MP length * If one of the named objects is a Blocking Element for a MP Limit Marker depends on the state of the element and/or the planned activities in the Operational Plan.

Definition of Blocking Element:
type: Form

Definition of Earliest Time Constraint:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of Earliest Time Constraint:
sense: DEFINITION--OF--EARLIEST--TIME--CONSTRAINT lexSense

DEFINITION--OF--EARLIEST--TIME--CONSTRAINT lexConcept
type: LexicalConcept
definition: Definition of Earliest Time Constraint: * The Earliest Time Constraint is an additional constraint, which is only calculated, if there is Movement Event of type STOP or PASS (Operational Plan Movement) between the STA and the calculated Pass Position Constraint. * The Earliest Time Constraint is needed to not trigger the STA Request to early in case of STOP or PASS Event between the STA and the calculated Pass Position Constraint Triggering of STA Request: * The Earliest Time Constraint defines a point in time that must be reached to trigger the STA Request. * The Earliest Time Constraint and the Pass Position Constraint for a specific STA Request do apply simultaneously. This means that both constraints need to be resolved to trigger the STA Request. * If there are multiple Movement Events of type STOP or PASS planned between the calculated Pass Position Constraint and the specific STA, only the one closest to the specific STA will be used; the others are not relevant. This is because the closest Movement Event is assumed to have the most accurate scheduled time for the specific STA

Definition of Earliest Time Constraint:
type: Form

Definition of Max Length Constraint - MP Limit Marker:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of Max Length Constraint - MP Limit Marker:
sense: DEFINITION--OF--MAX--LENGTH--CONSTRAINT-----MP--LIMIT--MARKER lexSense

DEFINITION--OF--MAX--LENGTH--CONSTRAINT-----MP--LIMIT--MARKER lexConcept
type: LexicalConcept
definition: Definition of Max Length Constraint - MP Limit Marker: If the MP Limit Marker is located further away than the maximum possible length of the MP (based on the position of the Train Object), the MP shall be requested with the maximum allowable length. As the Train Object moves, the MP Limit Marker can also be adjusted accordingly. A minimum distance for shifting the MP Limit Marker can be established for this purpose. It is assumed that the maximum possible length of the MP Extent (Movement Permission Path Segment) corresponds to the maximum length of the ETCS Movement Authority, which may be limited by factors such as the number of possible gradients.

Definition of Max Length Constraint - MP Limit Marker:
type: Form

Definition of MP Limit Marker Constraint:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of MP Limit Marker Constraint:
sense: DEFINITION--OF--MP--LIMIT--MARKER--CONSTRAINT lexSense

DEFINITION--OF--MP--LIMIT--MARKER--CONSTRAINT lexConcept
type: LexicalConcept
definition: Definition of MP Limit Marker Constraint: * An MP Limit Marker Constraint describes a constraint to be resolved before shifting the MP Limit Marker to its next position * Before the MP Limit Marker can be shifted to its next position the constraints of the current Blocking Element have to be resolved * An MP Limit Marker Constraint can be of type: Pass Position Constraint, Earliest Time Constraint, Driveability Constraint, Overlap Constraint, Max Length Constraint

Definition of MP Limit Marker Constraint:
type: Form

Definition of MP Limit Marker:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of MP Limit Marker:
sense: DEFINITION--OF--MP--LIMIT--MARKER lexSense

DEFINITION--OF--MP--LIMIT--MARKER lexConcept
type: LexicalConcept
definition: Definition of MP Limit Marker: * The MP Limit Marker defines the position on the track path to which the next MP, including its Risk Buffer shall be extended upon request. * The MP Limit Marker is always shifted to the next Blocking Element along the track path specified in the Operational Plan Movement as soon as all MP Limit Marker Constraints have been resolved. * The shift of the MP limit marker to the next position serves as the trigger for PES to send the corresponding MP Request.

Definition of MP Limit Marker:
type: Form

Definition of MP Request Constraint:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of MP Request Constraint:
sense: DEFINITION--OF--MP--REQUEST--CONSTRAINT lexSense

DEFINITION--OF--MP--REQUEST--CONSTRAINT lexConcept
type: LexicalConcept
definition: Definition of MA Request Constraint - MP Limit Marker: The MA Request Constraint is used for the initial MP Request of a starting up train (SoM). PES shall wait for the MA Request sent by the train (ETCS-OBU) and forwarded by ETPS before sending its MP Request to ETPS{comment:33}

Definition of MP Request Constraint:
type: Form

Definition of Overlap Constraint Restriction Area - MP Limit Marker:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of Overlap Constraint Restriction Area - MP Limit Marker:
sense: DEFINITION--OF--OVERLAP--CONSTRAINT--RESTRICTION--AREA-----MP--LIMIT--MARKER lexSense

DEFINITION--OF--OVERLAP--CONSTRAINT--RESTRICTION--AREA-----MP--LIMIT--MARKER lexConcept
type: LexicalConcept
definition: Definition of Overlap Constraint Restriction Area - MP Limit Marker: If an Restriction Area is a Blocking Element depends on the type of the specified Usage Restriction(s). * An overlap of the requested, restricted MP is allowed if e.g. the Usage Restrictions is of type “speed restriction” or “on-sight restriction * The MP Limit Marker position shall end in front of the URA if e.g. a Usage Restrictions of type “possession” or “non-stopping area” is specified.

Definition of Overlap Constraint Restriction Area - MP Limit Marker:
type: Form

Definition of Overlap Constraint Train Object - MP Limit Marker:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of Overlap Constraint Train Object - MP Limit Marker:
sense: DEFINITION--OF--OVERLAP--CONSTRAINT--TRAIN--OBJECT-----MP--LIMIT--MARKER lexSense

DEFINITION--OF--OVERLAP--CONSTRAINT--TRAIN--OBJECT-----MP--LIMIT--MARKER lexConcept
type: LexicalConcept
definition: Definition of Overlap Constraint Train Object - MP Limit Marker: If another Train Object is a Blocking Element depends on type of activity specified in Movement Event of Operational Plan Movement. * An extent and overlap of the requested, restricted MP with another Train Object shall be allowed for joining or meeting activities (entry into occupied section). * The MP Limit Marker position shall end in front of the Train Object if no such Movement Event is specified in the Operational Plan Movement

Definition of Overlap Constraint Train Object - MP Limit Marker:
type: Form

Definition of Overlap Constraint Unresolved Trackbound Object - MP Limit Marker:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of Overlap Constraint Unresolved Trackbound Object - MP Limit Marker:
sense: DEFINITION--OF--OVERLAP--CONSTRAINT--UNRESOLVED--TRACKBOUND--OBJECT-----MP--LIMIT--MARKER lexSense

DEFINITION--OF--OVERLAP--CONSTRAINT--UNRESOLVED--TRACKBOUND--OBJECT-----MP--LIMIT--MARKER lexConcept
type: LexicalConcept
definition: Definition of Overlap Constraint Unresolved Trackbound Object - MP Limit Marker: If another UTO is a Blocking Element depends on the UTO creation reason, and the type of activity specified in Movement Event of Operational Plan Movement. * An extent and overlap of the requested, restricted MP with another UTO shall be allowed for joining or meeting activities (entry into occupied section). * The MP Limit Marker position shall end in front of UTO if no such Movement Event is specified in the Operational Plan Movement * UTO creation reasons: Further details can be added in a later version of this document.

Definition of Overlap Constraint Unresolved Trackbound Object - MP Limit Marker:
type: Form

Definition of Pass Position Constraint - MP Limit Marker:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of Pass Position Constraint - MP Limit Marker:
sense: DEFINITION--OF--PASS--POSITION--CONSTRAINT-----MP--LIMIT--MARKER lexSense

DEFINITION--OF--PASS--POSITION--CONSTRAINT-----MP--LIMIT--MARKER lexConcept
type: LexicalConcept
definition: Definition of Pass Position Constraint - MP Limit Marker: * The Pass Position Constraint defines the latest track position the train must pass for the constraint to be considered resolved. * The Pass Position Constraint prevents MP requests from being send too early and MP Extends from being requested longer than necessary (for example, when departure times of Stop and Pass Events are reached and the next required STAs are already in the required drivability state).

Definition of Pass Position Constraint - MP Limit Marker:
type: Form

Definition of Pass Position Constraint for STA Request:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of Pass Position Constraint for STA Request:
sense: DEFINITION--OF--PASS--POSITION--CONSTRAINT--FOR--STA--REQUEST lexSense

DEFINITION--OF--PASS--POSITION--CONSTRAINT--FOR--STA--REQUEST lexConcept
type: LexicalConcept
definition: Definition of Pass Position Constraint for STA Request: * The Pass Position Constraint defines the latest track position the train must pass at which PES must send the STA Request, so that the train can receive a MP over that STA without the need to drive into the braking curves of a current, already existing MP. Triggering of STA Request: * The Pass Position Constraint indicates where the first attempt to send the STA Request is made. If the STA is allocated e.g. by another Train Object at this point in time, then the STA Request is not send, it is queued by PES and executed once the STA is no longer allocated.{comment:21}{comment:46}

Definition of Pass Position Constraint for STA Request:
type: Form

Definition of Reserved STA Path:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definition of Reserved STA Path:
sense: DEFINITION--OF--RESERVED--STA--PATH lexSense

DEFINITION--OF--RESERVED--STA--PATH lexConcept
type: LexicalConcept
definition: Definition of Reserved STA Path: * The Reserved STA Path indicates that the drivability state of the reserved STAs can only be requested for the corresponding Train Object. Logic of Reserved STA Path : * The Reserved STA Path is extended all the way up to and over the STA which shall be requested after the following conditions are satisfied: * Pass Position Constraint and Earliest Time Constraint for the corresponding STA are resolved. * The path between the Train Object and the said STA is clear of other trains or other Reserved STA Paths. * The Reserved STA Path shall have at least the extent of the current MP (including Risk Buffer) but may extend beyond the current MP (including Risk Buffer) in the direction of travel. * The Reserved STA Path shall have the same rear end as the current MP. * The Reserved STA Path shall not overlap with the Reserved STA Path of another Train Object. Triggering of STA Request: * The STA Request shall be triggered, as soon as the Reserved STA Path overlaps with the corresponding STA.

Definition of Reserved STA Path:
type: Form

Definition.
type: LexicalEntry
type: Word
canonical form: Definition.
sense: DEFINITION lexSense

DEFINITION lexConcept
type: LexicalConcept
definition: Glossary entry. See: Definitions

Definition.
type: Form

Definiton of Driveability Constraint - MP Limit Marker:
type: LexicalEntry
type: MultiwordExpression
canonical form: Definiton of Driveability Constraint - MP Limit Marker:
sense: DEFINITON--OF--DRIVEABILITY--CONSTRAINT-----MP--LIMIT--MARKER lexSense

DEFINITON--OF--DRIVEABILITY--CONSTRAINT-----MP--LIMIT--MARKER lexConcept
type: LexicalConcept
definition: Definiton of Driveability Constraint - MP Limit Marker: The Driveability Constraint is resolved if the needed STA is in the required driveability state.

Definiton of Driveability Constraint - MP Limit Marker:
type: Form

Degraded Mode
type: LexicalEntry
type: MultiwordExpression
canonical form: Degraded Mode
sense: DEGRADED--MODE lexSense

DEGRADED--MODE lexConcept
type: LexicalConcept
definition: "Degraded Mode" in railway operations refers to defined procedures applied when one or more safety-critical technical systems (such as signalling, train detection, level crossings, automatic train protection, or communication systems) are unavailable or functioning abnormally. In such situations, normal operational processes are replaced by alternative or emergency procedures that require dedicated fall back solutions (technically) {comment:117}or mainly trained personnel to manually initiate, execute, and monitor train movements, thereby temporarily assuming responsibilities normally fulfilled by technology. The goal is to sustain railway operations at an acceptable level of safety until full technical functionality is restored. Degraded Mode does not include ad hoc operational deviations (such as rerouting trains for non-technical reasons) but specifically addresses failures or constraints in technical systems essential for safe operation. All measures are to be thoroughly documented and communicated, and operations in degraded mode are to be minimized in time and extent due to inherently increased risk."{comment:157}

Degraded Mode
type: Form

delete - CCS Configuration Manifest
type: LexicalEntry
type: MultiwordExpression
canonical form: delete - CCS Configuration Manifest
sense: DELETE-----CCS--CONFIGURATION--MANIFEST lexSense

DELETE-----CCS--CONFIGURATION--MANIFEST lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: delete - CCS Configuration Manifest

delete - CCS Configuration Manifest
type: Form

Deliverable
type: LexicalEntry
type: Word
canonical form: Deliverable
sense: DELIVERABLE lexSense

DELIVERABLE lexConcept
type: LexicalConcept
definition: An input or output of a task that crosses the process boundaries. Any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project. (e.g. Requirement Specification)

Deliverable
type: Form

Demand
type: LexicalEntry
type: Word
canonical form: Demand
sense: DEMAND lexSense

DEMAND lexConcept
type: LexicalConcept
definition: A Demand on the SCI-SCMD interface is a message from a client to ETPS which asks ETPS for a certain task where the client (usually the Signaller) or the designated procedure takes over responsibility. Therefore, certain safety checks can be overridden.{comment:1327} The Demand always follows a Request{comment:1328} on the SCI-SCMD interface where ETPS had found that overridable safety checks would be violated. After a confirmation of the Signaller that he takes over responsibility, this Request then becomes a Demand and will be granted/executed. A Demand shall not be used for regular operation.

Demand
type: Form

Departure Datetime Change
type: LexicalEntry
type: MultiwordExpression
canonical form: Departure Datetime Change
sense: DEPARTURE--DATETIME--CHANGE lexSense

DEPARTURE--DATETIME--CHANGE lexConcept
type: LexicalConcept
definition: Change in the departure time of a train in a station, either by departing earlier or later than planned

Departure Datetime Change
type: Form

Deployment
type: LexicalEntry
type: Word
canonical form: Deployment
sense: DEPLOYMENT lexSense

DEPLOYMENT lexConcept
type: LexicalConcept
definition: rollout

Deployment
type: Form

Design Safety Case
type: LexicalEntry
type: MultiwordExpression
canonical form: Design Safety Case
sense: DESIGN--SAFETY--CASE lexSense

DESIGN--SAFETY--CASE lexConcept
type: LexicalConcept
definition: The Design Safety Case gives evidence to the design for a product or application done in Phase 1 to 5. The Design Safety Case will: * fulfil the requirements of Phase 4 (including validation report) and integrated in a modular architecture in Phase 5, * define the SuC and its interfaces and must comply thereby to a harmonised reference architecture (e.g. "System Pillar Reference Architecture"): * functional allocation, * interfaces description, * standardised tests activities (e.f. test benches, procedures), * allocation of safety requirements (e.g. TFFR, SRAC) * be presented to the ISA for a first statement, * be reused for further generic product safety cases or generic/specific safety cases, * evolve along the whole lifecycle of the SuC design, * cover the Safety Management topics in the EU-Rail Standardisation and TSI Input Plan (STIP).

Design Safety Case
type: Form

DeBo
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DESIGNATED--BODY label
canonical form: DeBo

DESIGNATED--BODY lexConcept
type: LexicalConcept
definition: From DIRECTIVE (EU) 2016/797 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 11 May 2016 on the interoperability of the rail system within the European Union: (42) ‘conformity assessment body’ means a body that has been notified or designated to be responsible for conformity assessment activities, including calibration, testing, certification and inspection; a conformity assessment body is classified as a ‘notified body’ following notification by a Member State; a conformity assessment body is classified as a ‘designated body’ following designation by a Member State;

Designated Body
type: Form

DeBo
type: Form

Desk Area
type: LexicalEntry
type: MultiwordExpression
canonical form: Desk Area
sense: DESK--AREA lexSense

DESK--AREA lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: Desk Area is a location attribute (left, center...) associated to HMI Element for MDS Controller to allocate elements to a View.

DESK--AREA lexConcept 3
type: LexicalConcept
definition: Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View.

DESK--AREA lexConcept 4
type: LexicalConcept
definition: Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View.

DESK--AREA lexConcept 5
type: LexicalConcept
definition: Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View.

DESK--AREA lexConcept 6
type: LexicalConcept
definition: Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View.

DESK--AREA lexConcept 7
type: LexicalConcept
definition: Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View.

DESK--AREA lexConcept 8
type: LexicalConcept
definition: Desk Area Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View.

Desk Area
type: Form

Desk Display Area
type: LexicalEntry
type: MultiwordExpression
canonical form: Desk Display Area
sense: DESK--DISPLAY--AREA lexSense

DESK--DISPLAY--AREA lexConcept
type: LexicalConcept
definition: 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).

DESK--DISPLAY--AREA lexConcept 2
type: LexicalConcept
definition: 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).

DESK--DISPLAY--AREA lexConcept 3
type: LexicalConcept
definition: 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).

DESK--DISPLAY--AREA lexConcept 4
type: LexicalConcept
definition: 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).

DESK--DISPLAY--AREA lexConcept 5
type: LexicalConcept
definition: 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.

DESK--DISPLAY--AREA lexConcept 6
type: LexicalConcept
definition: {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 lexConcept 7
type: LexicalConcept
definition: 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.

DESK--DISPLAY--AREA lexConcept 8
type: LexicalConcept
definition: 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.

Desk Display Area
type: Form

Desk
type: LexicalEntry
type: Word
canonical form: Desk
sense: DESK lexSense

DESK lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: 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 lexConcept 3
type: LexicalConcept
definition: 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 lexConcept 4
type: LexicalConcept
definition: 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 lexConcept 5
type: LexicalConcept
definition: 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 lexConcept 6
type: LexicalConcept
definition: 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 lexConcept 7
type: LexicalConcept
definition: 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 lexConcept 8
type: LexicalConcept
definition: 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

Desk
type: Form

Development Partnership
type: LexicalEntry
type: MultiwordExpression
canonical form: Development Partnership
sense: DEVELOPMENT--PARTNERSHIP lexSense

DEVELOPMENT--PARTNERSHIP lexConcept
type: LexicalConcept
definition: Contract between IM or RU and one of more suppliers about developing product(s) or (sub)systems as a collaboration

Development Partnership
type: Form

DEV
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DEVELOPMENT label
canonical form: DEV

DEVELOPMENT lexConcept
type: LexicalConcept
definition: Development

Development
type: Form

DEV
type: Form

Deviation Detection
type: LexicalEntry
type: MultiwordExpression
canonical form: Deviation Detection
sense: DEVIATION--DETECTION lexSense

DEVIATION--DETECTION lexConcept
type: LexicalConcept
definition: Comparing the operational plan with the real-time status to detected operational deviations. Deviations have already happened and may only be mitigated but not solved.

Deviation Detection
type: Form

Deviation
type: LexicalEntry
type: Word
canonical form: Deviation
sense: DEVIATION lexSense

DEVIATION lexConcept
type: LexicalConcept
definition: A deviation is any difference between the operational plan and the actual state of traffic; unlike a conflict, deviations may only be mitigated but not solved.

Deviation
type: Form

Data source
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DEVICE--OR--SYSTEM--ISSUING--THE--DATA label
canonical form: Data source

DEVICE--OR--SYSTEM--ISSUING--THE--DATA lexConcept
type: LexicalConcept
definition: Device or System issuing the data. In the case of individual vehicles issue of the data is done by the CCU or an ED. In the case of a train, it is done by the CCU of the leading consist. In the case of the data source being a land side system, it would be an FDFT backend.

Device or System issuing the data.
type: Form

Data source
type: Form

Diagnostics
type: LexicalEntry
type: Word
canonical form: Diagnostics
sense: DIAGNOSTICS lexSense

DIAGNOSTICS lexConcept
type: LexicalConcept
definition: Diagnostics is the assessment{comment:1} of health and performance of an asset or a group of assets. Furthermore, the diagnostic system also provides all information of single components in the field like: software version, parametrisation file version, firmware version, hardware version, manufacturer part number, manufacturer serial number,{comment:35} ID in the field (e.g. NID_ENGINE), cumulated hours in operation, IP address, etc. All this data is being used for analysis purposes.

DIAGNOSTICS lexConcept 2
type: LexicalConcept
definition: Diagnostics is the assessment of health and performance of an asset or a group of assets. Furthermore, the diagnostic system also provides all information of single components in the field like: software version, parametrisation file version, firmware version, hardware version, manufacturer part number, manufacturer serial number, ID in the field (e.g. NID_ENGINE), cumulated hours in operation, IP address, etc. The latter is being used for analysis purposes.{comment:168} {comment:131}

Diagnostics
type: Form

Diagram.
type: LexicalEntry
type: Word
canonical form: Diagram.
sense: DIAGRAM lexSense

DIAGRAM lexConcept
type: LexicalConcept
definition: Stores a diagram, slide, or picture.

Diagram.
type: Form

Diffuse operational state
type: LexicalEntry
type: MultiwordExpression
canonical form: Diffuse operational state
sense: DIFFUSE--OPERATIONAL--STATE lexSense

DIFFUSE--OPERATIONAL--STATE lexConcept
type: LexicalConcept
definition: Detailed granular information about a subsystems that by themselves are not enough to implement a procedure in normal operation . E.g. track position of a starting train, pre-defined failure state of a trackside asset, etc.

Diffuse operational state
type: Form

DAC
type: Acronym
type: LexicalEntry
acronym for: DIGITAL--AUTOMATED--COUPLING label
canonical form: DAC

DIGITAL--AUTOMATED--COUPLING lexConcept
type: LexicalConcept
definition: Digital Automated Coupling

DIGITAL--AUTOMATED--COUPLING lexConcept 2
type: LexicalConcept
definition: Digital Automated Coupling

Digital Automated Coupling
type: Form

DAC
type: Form

DAC
type: Form

Digital Continuity
type: LexicalEntry
type: MultiwordExpression
canonical form: Digital Continuity
sense: DIGITAL--CONTINUITY lexSense

DIGITAL--CONTINUITY lexConcept
type: LexicalConcept
definition: Digital continuity means that the transformation of information from the single source of truth all the way to production maps is fully automated, robust and without manual processing steps. Secondly, new storage technologies, computing platforms, communication protocols will come into fashion and the data model shouldn't prevent future users to adopt such technical innovations.

Digital Continuity
type: Form

DR-I
type: Acronym
type: LexicalEntry
acronym for: DIGITAL--REGISTER-----INFRASTRUCTURE label
canonical form: DR-I

DIGITAL--REGISTER-----INFRASTRUCTURE lexConcept
type: LexicalConcept
definition: 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.

Digital Register - Infrastructure
type: Form

DR-I
type: Form

DR-V
type: Acronym
type: LexicalEntry
acronym for: DIGITAL--REGISTER-----VEHICLE label
canonical form: DR-V

DIGITAL--REGISTER-----VEHICLE lexConcept
type: LexicalConcept
definition: Digital Register - Vehicle

Digital Register - Vehicle
type: Form

DR-V
type: Form

Direct Brake -
type: LexicalEntry
type: MultiwordExpression
canonical form: Direct Brake -
sense: DIRECT--BRAKE lexSense

DIRECT--BRAKE lexConcept
type: LexicalConcept
definition: Direct Brake -

Direct Brake -
type: Form

Direct Track Possession / Occupancy
type: LexicalEntry
type: MultiwordExpression
canonical form: Direct Track Possession / Occupancy
sense: DIRECT--TRACK--POSSESSION-- --OCCUPANCY lexSense

DIRECT--TRACK--POSSESSION-- --OCCUPANCY lexConcept
type: LexicalConcept
definition: Physical occupation of a train to a network or part of the network

Direct Track Possession / Occupancy
type: Form

DG MOVE
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DIRECTORATE-GENERAL--FOR--MOBILITY--AND--TRANSPORT label
canonical form: DG MOVE

DIRECTORATE-GENERAL--FOR--MOBILITY--AND--TRANSPORT lexConcept
type: LexicalConcept
definition: Directorate-General for Mobility and Transport

Directorate-General for Mobility and Transport
type: Form

DG MOVE
type: Form

DG RTD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DIRECTORATE-GENERAL--FOR--RESEARCH--AND--INNOVATION label
canonical form: DG RTD

DIRECTORATE-GENERAL--FOR--RESEARCH--AND--INNOVATION lexConcept
type: LexicalConcept
definition: Directorate-General for Research and Innovation

Directorate-General for Research and Innovation
type: Form

DG RTD
type: Form

DR
type: Acronym
type: LexicalEntry
acronym for: DISASTER--RECOVERY-PLAN label
canonical form: DR

DISASTER--RECOVERY-PLAN lexConcept
type: LexicalConcept
definition: Disaster Recovery-Plan

Disaster Recovery-Plan
type: Form

DR
type: Form

Dispatching
type: LexicalEntry
type: Word
canonical form: Dispatching
sense: DISPATCHING lexSense

DISPATCHING lexConcept
type: LexicalConcept
definition: Dispatching is the sum of actions intended to make modifications the operational plan.

Dispatching
type: Form

Display Computing Unit
type: LexicalEntry
type: MultiwordExpression
canonical form: Display Computing Unit
sense: DISPLAY--COMPUTING--UNIT lexSense

DISPLAY--COMPUTING--UNIT lexConcept
type: LexicalConcept
definition: 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).

DISPLAY--COMPUTING--UNIT lexConcept 2
type: LexicalConcept
definition: 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.

DISPLAY--COMPUTING--UNIT lexConcept 3
type: LexicalConcept
definition: 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.

DISPLAY--COMPUTING--UNIT lexConcept 4
type: LexicalConcept
definition: 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.

DISPLAY--COMPUTING--UNIT lexConcept 5
type: LexicalConcept
definition: 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.

DISPLAY--COMPUTING--UNIT lexConcept 6
type: LexicalConcept
definition: 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.

Display Computing Unit
type: Form

Display Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Display Controller
sense: DISPLAY--CONTROLLER lexSense

DISPLAY--CONTROLLER lexConcept
type: LexicalConcept
definition: The part of the display that is assuring the safe display of the requested information on the screen, related to time, place, duration and colour.

Display Controller
type: Form

Display HW Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Display HW Controller
sense: DISPLAY--HW--CONTROLLER lexSense

DISPLAY--HW--CONTROLLER lexConcept
type: LexicalConcept
definition: The part of the display that is assuring the safe display of the requested information on the screen, related to time, place, duration and colour.

DISPLAY--HW--CONTROLLER lexConcept 2
type: LexicalConcept
definition: The part of the display that is assuring the safe display of the requested information on the screen, related to time, place, duration and colour.

DISPLAY--HW--CONTROLLER lexConcept 3
type: LexicalConcept
definition: The part of the display that is assuring the safe display of the requested information on the screen, related to time, place, duration and colour.

DISPLAY--HW--CONTROLLER lexConcept 4
type: LexicalConcept
definition: The part of the display that is assuring the safe display of the requested information on the screen, related to time, place, duration and colour.

Display HW Controller
type: Form

Display Manager
type: LexicalEntry
type: MultiwordExpression
canonical form: Display Manager
sense: DISPLAY--MANAGER lexSense

DISPLAY--MANAGER lexConcept
type: LexicalConcept
definition: Is the interface to the Display Controller and synchronising all status and data informations of all business applications for the Display Units.

DISPLAY--MANAGER lexConcept 2
type: LexicalConcept
definition: Is the interface to the Display HW Controller and synchronising all status and data informations of all business applications for the Display Units.

DISPLAY--MANAGER lexConcept 3
type: LexicalConcept
definition: Is the interface to the Display HW Controller and synchronising all status and data informations of all business applications for the Display Units.

DISPLAY--MANAGER lexConcept 4
type: LexicalConcept
definition: Is the interface to the Display HW Controller and synchronising all status and data informations of all business applications for the Display Units.

DISPLAY--MANAGER lexConcept 5
type: LexicalConcept
definition: Is the interface to the Display HW Controller and synchronising all status and data informations of all business applications for the Display Units.

Display Manager
type: Form

Display Panel
type: LexicalEntry
type: MultiwordExpression
canonical form: Display Panel
sense: DISPLAY--PANEL lexSense

DISPLAY--PANEL lexConcept
type: LexicalConcept
definition: Glass (LCD) showing pixels without controller.

DISPLAY--PANEL lexConcept 2
type: LexicalConcept
definition: Glass (LCD) showing pixels without controller.

DISPLAY--PANEL lexConcept 3
type: LexicalConcept
definition: Glass (LCD) showing pixels without controller.

DISPLAY--PANEL lexConcept 4
type: LexicalConcept
definition: Glass (LCD) showing pixels without controller.

DISPLAY--PANEL lexConcept 5
type: LexicalConcept
definition: Glass (LCD) showing pixels without controller.

DISPLAY--PANEL lexConcept 6
type: LexicalConcept
definition: Glass (LCD) showing pixels without controller.

DISPLAY--PANEL lexConcept 7
type: LexicalConcept
definition: Glass (LCD) showing pixels without controller.

DISPLAY--PANEL lexConcept 8
type: LexicalConcept
definition: Display Panel Glass (LCD) showing pixels without controller.

Display Panel
type: Form

DDOS
type: Acronym
type: LexicalEntry
acronym for: DISTRIBUTED--DENIAL--OF--SERVICE label
canonical form: DDOS

DISTRIBUTED--DENIAL--OF--SERVICE lexConcept
type: LexicalConcept
definition: Distributed Denial of Service

Distributed Denial of Service
type: Form

DDOS
type: Form

DistributionJob "distribution-job.json" document
type: LexicalEntry
type: MultiwordExpression
canonical form: DistributionJob "distribution-job.json" document
sense: DISTRIBUTIONJOB-- DISTRIBUTION-JOB-JSON --DOCUMENT lexSense

DISTRIBUTIONJOB-- DISTRIBUTION-JOB-JSON --DOCUMENT lexConcept
type: LexicalConcept
definition: A DistributionJob is defines the time and conditions when one or more CCS deployments with the same homologation receive their software configuration update (preload and activation). Examples for conditions when the distribution-job is started are approvals from a train-driver, or someone from operation or a GOA4 system that need to approve the configuration update within the preloading and activation time windows. The distribution-job.json document references the Top Level BuildingBlockConfiguration (BBC), that has recursive dependency tree. The distribution-job is defined within a distribution-job.json document that is validated by the distribution-job.schema.json.

DistributionJob "distribution-job.json" document
type: Form

DM - Digital Map
type: LexicalEntry
type: MultiwordExpression
canonical form: DM - Digital Map
sense: DM-----DIGITAL--MAP lexSense

DM-----DIGITAL--MAP lexConcept
type: LexicalConcept
definition: DM - Digital Map

DM - Digital Map
type: Form

Document Author
type: LexicalEntry
type: MultiwordExpression
canonical form: Document Author
sense: DOCUMENT--AUTHOR lexSense

DOCUMENT--AUTHOR lexConcept
type: LexicalConcept
definition: Document Author is the document generator and belongs to a specific task/domain. See role SPPR-5408 - Document Author

Document Author
type: Form

Domain Data Model
type: LexicalEntry
type: MultiwordExpression
canonical form: Domain Data Model
sense: DOMAIN--DATA--MODEL lexSense

DOMAIN--DATA--MODEL lexConcept
type: LexicalConcept
definition: A domain data model is the information package needed by a professional discipline and the associated subsystems such as TMS, time tabling, ATO, ETCS signalling.

Domain Data Model
type: Form

Domain Model
type: LexicalEntry
type: MultiwordExpression
canonical form: Domain Model
sense: DOMAIN--MODEL lexSense

DOMAIN--MODEL lexConcept
type: LexicalConcept
definition: 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

Domain Model
type: Form

DNS
type: Acronym
type: LexicalEntry
acronym for: DOMAIN--NAME--SYSTEM label
canonical form: DNS

DOMAIN--NAME--SYSTEM lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Domain Name System

DOMAIN--NAME--SYSTEM lexConcept 2
type: LexicalConcept
definition: Domain Name System

Domain Name System
type: Form

DNS
type: Form

DNS
type: Form

Domain Object
type: LexicalEntry
type: MultiwordExpression
canonical form: Domain Object
sense: DOMAIN--OBJECT lexSense

DOMAIN--OBJECT lexConcept
type: LexicalConcept
definition: 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.

Domain Object
type: Form

Driveability (or Drivability)
type: LexicalEntry
type: MultiwordExpression
canonical form: Driveability (or Drivability)
sense: DRIVEABILITY--OR--DRIVABILITY lexSense

DRIVEABILITY--OR--DRIVABILITY lexConcept
type: LexicalConcept
definition: The degree of smoothness and steadiness of acceleration of a vehicle.

Driveability (or Drivability)
type: Form

DAS-OB
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DRIVER--ADVISORY--SYSTEM--ON--BOARD label
canonical form: DAS-OB

DRIVER--ADVISORY--SYSTEM--ON--BOARD lexConcept
type: LexicalConcept
definition: Driver Advisory System On Board

Driver Advisory System On Board
type: Form

DAS-OB
type: Form

DMI
type: Acronym
type: LexicalEntry
acronym for: DRIVER--MACHINE--INTERFACE label
canonical form: DMI

DRIVER--MACHINE--INTERFACE lexConcept
type: LexicalConcept
definition: Driver Machine Interface

Driver Machine Interface
type: Form

DMI
type: Form

ABD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DRIVING--IN--ABSOLUTE--BRAKING--DISTANCE label
canonical form: ABD

DRIVING--IN--ABSOLUTE--BRAKING--DISTANCE lexConcept
type: LexicalConcept
definition: The extension of the movement authority of a following train considers the rear of the Safe Train Extent of a preceding train as an absolute limit that shall not be passed – the speed and braking capacity of the preceding train are neglected.{comment:3}{comment:21} (image: 1-screenshot-20240904-140007.png)

Driving in Absolute Braking Distance
type: Form

ABD
type: Form

RBD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DRIVING--IN--RELATIVE--BRAKING--DISTANCE label
canonical form: RBD

DRIVING--IN--RELATIVE--BRAKING--DISTANCE lexConcept
type: LexicalConcept
definition: The extension of the movement authority of a following train is derived from the Safe Train Extent of the preceding train considering also speed and braking capacity of the preceding train. The distance between both trains during motion can be shorter than driving in Absolute Braking Distance, increasing the rail operation efficiency.{comment:8}{comment:22} (image: 1-screenshot-20240904-140007.png)

Driving in Relative Braking Distance
type: Form

RBD
type: Form

Driving Strategy Change
type: LexicalEntry
type: MultiwordExpression
canonical form: Driving Strategy Change
sense: DRIVING--STRATEGY--CHANGE lexSense

DRIVING--STRATEGY--CHANGE lexConcept
type: LexicalConcept
definition: Change the driving strategy from the defined list (energy efficient, reduce maximum speed, etc..)

Driving Strategy Change
type: Form

Driving Strategy
type: LexicalEntry
type: MultiwordExpression
canonical form: Driving Strategy
sense: DRIVING--STRATEGY lexSense

DRIVING--STRATEGY lexConcept
type: LexicalConcept
definition: How to drive the train as a combination of acceleration, braking, cruising and coasting (Energy efficient, reduced maximum speed, Maximal Coasting, Minimum Time Train Control, etc..)

Driving Strategy
type: Form

Dual control = Control that requires the approval by two authorised individuals...
type: LexicalEntry
type: MultiwordExpression
canonical form: Dual control = Control that requires the approval by two authorised individuals...
sense: https://glossaries.ontorail.org/LEX_SP-DEFS/lex_sp-defs-251007#DUAL--CONTROL--%3D--CONTROL--THAT--REQUIRES--THE--APPROVAL--BY--TWO--AUTHORISED--INDIVIDUALS_lexSense

https://glossaries.ontorail.org/LEX_SP-DEFS/lex_sp-defs-251007#DUAL--CONTROL--%3D--CONTROL--THAT--REQUIRES--THE--APPROVAL--BY--TWO--AUTHORISED--INDIVIDUALS_lexConcept
type: LexicalConcept
definition: Dual control = Control that requires the approval by two authorised individuals in order to be performed.

Dual control = Control that requires the approval by two authorised individuals...
type: Form

Dual Trackside Signalling Strategy
type: LexicalEntry
type: MultiwordExpression
canonical form: Dual Trackside Signalling Strategy
sense: DUAL--TRACKSIDE--SIGNALLING--STRATEGY lexSense

DUAL--TRACKSIDE--SIGNALLING--STRATEGY lexConcept
type: LexicalConcept
definition: Installing and running both class B signalling system and ETCS on the same track

Dual Trackside Signalling Strategy
type: Form

Dwell time
type: LexicalEntry
type: MultiwordExpression
canonical form: Dwell time
sense: DWELL--TIME lexSense

DWELL--TIME lexConcept
type: LexicalConcept
definition: Waiting time between the arrival and estimated departure time of a train at stop.

Dwell time
type: Form

Dynamic Brake -
type: LexicalEntry
type: MultiwordExpression
canonical form: Dynamic Brake -
sense: DYNAMIC--BRAKE lexSense

DYNAMIC--BRAKE lexConcept
type: LexicalConcept
definition: Dynamic Brake -

Dynamic Brake -
type: Form

Dynamic Business Rules
type: LexicalEntry
type: MultiwordExpression
canonical form: Dynamic Business Rules
sense: DYNAMIC--BUSINESS--RULES lexSense

DYNAMIC--BUSINESS--RULES lexConcept
type: LexicalConcept
definition: All defined rules related to the journey dynamics, e.g. Maximum waiting time of a connecting train

Dynamic Business Rules
type: Form

DTCC
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: DYNAMIC--TRAIN-CENTRIC--CONTROL label
canonical form: DTCC

DYNAMIC--TRAIN-CENTRIC--CONTROL lexConcept
type: LexicalConcept
definition: Dynamic Train-Centric Control permits movement ending at any location on the track (as long as this movement is allowed by the set of Safety Rules), a capability that is fundamentally restricted under current block-based signalling principles. Dynamic Train-Centric Control combines route protection and train control features. Based on the operational plan obtained from the TMS, Traffic CS will allocate a Movement Permission for the designated train and determine the Movement Authority for the designated train. This is different from the current approach where train authorisations are determined for predefined routes that have been set by an IXL.

Dynamic Train-Centric Control
type: Form

DTCC
type: Form

E-coupler
type: LexicalEntry
type: Word
canonical form: E-coupler
sense: E-COUPLER lexSense

E-COUPLER lexConcept
type: LexicalConcept
definition: Regarding the LCDF, the determination logic for the last coupled unit is still under discussion, particularly whether the e-coupler is coupled, uncoupled, ready or not for coupling — with the goal of standardizing the logic for a SIL2 sensor.

E-coupler
type: Form

EARS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EASY--APPROACH--TO--REQUIREMENTS--SYNTAX label
canonical form: EARS

EASY--APPROACH--TO--REQUIREMENTS--SYNTAX lexConcept
type: LexicalConcept
definition: SPPR-3560 - Easy approach to requirements syntax (EARS)

Easy Approach to Requirements Syntax
type: Form

EARS
type: Form

EB - Emergency Brake
type: LexicalEntry
type: MultiwordExpression
canonical form: EB - Emergency Brake
sense: EB-----EMERGENCY--BRAKE lexSense

EB-----EMERGENCY--BRAKE lexConcept
type: LexicalConcept
definition: EB - Emergency Brake

EB - Emergency Brake
type: Form

ECM
type: LexicalEntry
type: Word
canonical form: ECM
sense: ECM lexSense

ECM lexConcept
type: LexicalConcept
definition: Entity in charge of maintenance (‘ECM’) means an entity in charge of the maintenance of a vehicle, and registered as such in a vehicle register referred to in Article 47 of Directive (EU) 2016/797 The maintenance of vehicles is defined in the Article 14 of Directive (EU) 2016/798. In particular, the four functions of ECMs are described in the Article 14 (3): (a) a management function to supervise and coordinate the maintenance functions referred to in points (b) to (d) and to ensure the safe state of the vehicle in the railway system; [editorial edition : ECM 1 in this document] (b) a maintenance development function responsible to manage the maintenance documentation, including the configuration ation management, based on design and operational data as well as on performance and return on experience; [editorial edition : ECM 2 in this document] (c) a fleet-maintenance management function to manage the vehicle's removal for maintenance and its return to operation after maintenance; [editorial edition : ECM 3 in this document] (d) a maintenance delivery function to deliver the required technical maintenance of a vehicle or parts of it, including the release to service documentation. [editorial edition : ECM 4 in this document] The entity in charge of maintenance shall carry out the management function itself, but may outsource the maintenance functions referred to in points (b) to (d), or parts thereof, to other contracting parties such as maintenance workshops.

ECM
type: Form

ECN - Ethernet Consist Network
type: LexicalEntry
type: MultiwordExpression
canonical form: ECN - Ethernet Consist Network
sense: ECN-----ETHERNET--CONSIST--NETWORK lexSense

ECN-----ETHERNET--CONSIST--NETWORK lexConcept
type: LexicalConcept
definition: ECN - Ethernet Consist Network

ECN - Ethernet Consist Network
type: Form

Ecoupler
type: LexicalEntry
type: Word
canonical form: Ecoupler
sense: ECOUPLER lexSense

ECOUPLER lexConcept
type: LexicalConcept
definition: 13:49 in red (2x400V battery charger compatibility magnetic in test

Ecoupler
type: Form

EWAN
type: Acronym
type: LexicalEntry
acronym for: EGNOS--WIDE--AREA--NETWORK label
canonical form: EWAN

EGNOS--WIDE--AREA--NETWORK lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: EGNOS Wide Area Network

EGNOS Wide Area Network
type: Form

EWAN
type: Form

ELK
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ELASTICSEARCH--LOGSTASH--KIBANA label
canonical form: ELK

ELASTICSEARCH--LOGSTASH--KIBANA lexConcept
type: LexicalConcept
definition: Elasticsearch, Logstash, Kibana

Elasticsearch, Logstash, Kibana
type: Form

ELK
type: Form

EPCIS
type: Acronym
type: LexicalEntry
acronym for: ELECTRONIC--PRODUCT--CODE--INFORMATION--SERVICES label
canonical form: EPCIS

ELECTRONIC--PRODUCT--CODE--INFORMATION--SERVICES lexConcept
type: LexicalConcept
definition: Electronic Product Code Information Services

Electronic Product Code Information Services
type: Form

EPCIS
type: Form

Element
type: LexicalEntry
type: Word
canonical form: Element
sense: ELEMENT lexSense

ELEMENT lexConcept
type: LexicalConcept
definition: Any physical component that is part of the infrastructure composition (switches, tracks, signals)

Element
type: Form

Emergency train treatment
type: LexicalEntry
type: MultiwordExpression
canonical form: Emergency train treatment
sense: EMERGENCY--TRAIN--TREATMENT lexSense

EMERGENCY--TRAIN--TREATMENT lexConcept
type: LexicalConcept
definition: 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}

Emergency train treatment
type: Form

EMPA
type: LexicalEntry
type: Word
canonical form: EMPA
sense: EMPA lexSense

EMPA lexConcept
type: LexicalConcept
definition: An EMPA ...

EMPA
type: Form

End Occupancy Location
type: LexicalEntry
type: MultiwordExpression
canonical form: End Occupancy Location
sense: END--OCCUPANCY--LOCATION lexSense

END--OCCUPANCY--LOCATION lexConcept
type: LexicalConcept
definition: The location point where the infrastructure element (track, signal, switch, etc..) occupation has ended

End Occupancy Location
type: Form

End Occupancy Time
type: LexicalEntry
type: MultiwordExpression
canonical form: End Occupancy Time
sense: END--OCCUPANCY--TIME lexSense

END--OCCUPANCY--TIME lexConcept
type: LexicalConcept
definition: The timestamp where the infrastructure element (track, signal, switch, etc..) occupation has ended

End Occupancy Time
type: Form

EoL
type: Acronym
type: LexicalEntry
acronym for: END--OF--LIFE label
canonical form: EoL

END--OF--LIFE lexConcept
type: LexicalConcept
definition: In system design, the term "End of Life" refers to the stage in the lifecycle of a system or product when it is no longer considered viable, functional, or supported. It marks the point at which the system or product is no longer actively maintained, developed, or sold by the manufacturer or service provider.

End of Life
type: Form

EoL
type: Form

EoM
type: Acronym
type: LexicalEntry
acronym for: END--OF--MISSION label
canonical form: EoM

END--OF--MISSION lexConcept
type: LexicalConcept
definition: End of Mission.

End of Mission
type: Form

EoM
type: Form

EoS
type: Acronym
type: LexicalEntry
acronym for: END--OF--SUPPORT label
canonical form: EoS

END--OF--SUPPORT lexConcept
type: LexicalConcept
definition: In system engineering, "End of Support" refers to the point in the lifecycle of a system or software product when the manufacturer or service provider discontinues providing technical support, maintenance, and updates for the product. It signifies the end of the official assistance and resources available from the provider to address issues, fix bugs, or offer guidance to users of the system.

End of Support
type: Form

EoS
type: Form

E-2-E
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: END-TO-END label
canonical form: E-2-E

END-TO-END lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: End-to-End

End-to-End
type: Form

E-2-E
type: Form

Engineering data
type: LexicalEntry
type: MultiwordExpression
canonical form: Engineering data
sense: ENGINEERING--DATA lexSense

ENGINEERING--DATA lexConcept
type: LexicalConcept
definition: 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}

ENGINEERING--DATA lexConcept 2
type: LexicalConcept
definition: The Engineering Data as part of the SPT2TS-2040 - CCS/TMS Extended ERA Ontology (CCS/TMS Data Model) contains all the base data (i.e.,{comment:19} track topology, track geometry, track asset configuration) for compiling the next version(s) of use case-specific Domain Data. The standardized Engineering Data comprehensively covers the data needs for the SERA in the scope of the System Pillar (i.e. radio-based ETCS only). Specific data needed for migration is out of the scope of SPT2TS-2040 - CCS/TMS Extended ERA Ontology (CCS/TMS Data Model).

ENGINEERING--DATA lexConcept 3
type: LexicalConcept
definition: Engineering data are measurements, design data and derived data that parametrise the railway system, i.e. configuration information.

Engineering data
type: Form

EET
type: Acronym
type: LexicalEntry
acronym for: ENGINEERING--ENVIRONMENT--TEAM label
canonical form: EET

ENGINEERING--ENVIRONMENT--TEAM lexConcept
type: LexicalConcept
definition: Engineering Environment Team

Engineering Environment Team
type: Form

EET
type: Form

Engineering Input Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Engineering Input Data
sense: ENGINEERING--INPUT--DATA lexSense

ENGINEERING--INPUT--DATA lexConcept
type: LexicalConcept
definition: 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

ENGINEERING--INPUT--DATA lexConcept 2
type: LexicalConcept
definition: Refers to data for 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 * Train specific data like ETCS Braking curves * Any other data required for CCS/TMS system configuration

Engineering Input Data
type: Form

Engineering View
type: LexicalEntry
type: MultiwordExpression
canonical form: Engineering View
sense: ENGINEERING--VIEW lexSense

ENGINEERING--VIEW lexConcept
type: LexicalConcept
definition: The engineering view exposes the configuration information that was used to build, test and release the railway system. This constitutes the as-planned situation.

Engineering View
type: Form

ECS
type: Acronym
type: LexicalEntry
acronym for: ENTERPRISE--CYBERSECURITY--SERVICES label
canonical form: ECS

ENTERPRISE--CYBERSECURITY--SERVICES lexConcept
type: LexicalConcept
definition: A collection of enterprise security interface (ESI) implementations of central security and IT communication functions in a back-office environment. Examples are Security Incident and Event Management System (SIEM), Intrusion Detection System, PKI Certificate Authority, Corporate Directory, Asset Management, DNS. These services are typically accessible for the automation network via controlled communication paths (e.g. DMZ). The interfaces of the Shared Cybersecurity Services to the Enterprise Services are identified by ESI-<Service name>. Note: Enterprise Shared Services are typically 3rd-party components not dedicated to the rail environment. Therefore the realization of the Enterprise Shared Services may use other security requirements than the Secure Component Specification. Recommended security specification are ISO 27033, ISO 27034, NIST 800-53, and/or IEC 62443-4-2. Note: Enterprise Shared Services and Shared Cybersecurity Services are separated by the IT/OT border (e.g. by a DMZ).

Enterprise Cybersecurity Services
type: Form

ECS
type: Form

ERP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ENTERPRISE--RESSOURCE--MANAGEMENT label
canonical form: ERP

ENTERPRISE--RESSOURCE--MANAGEMENT lexConcept
type: LexicalConcept
definition: Enterprise Ressource Management

Enterprise Ressource Management
type: Form

ERP
type: Form

ESS
type: Acronym
type: LexicalEntry
acronym for: ENTERPRISE--SECURITY--SERVICES label
canonical form: ESS

ENTERPRISE--SECURITY--SERVICES lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Enterprise Security Services

Enterprise Security Services
type: Form

ESS
type: Form

ERA - European Railway Agency
type: LexicalEntry
type: MultiwordExpression
canonical form: ERA - European Railway Agency
sense: ERA-----EUROPEAN--RAILWAY--AGENCY lexSense

ERA-----EUROPEAN--RAILWAY--AGENCY lexConcept
type: LexicalConcept
definition: ERA - European Railway Agency

ERA - European Railway Agency
type: Form

EECT
type: Acronym
type: LexicalEntry
acronym for: ERA--EXTENDED--CORE--TEAM label
canonical form: EECT

ERA--EXTENDED--CORE--TEAM lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: ERA Extended Core Team

ERA--EXTENDED--CORE--TEAM lexConcept 2
type: LexicalConcept
definition: ERA Extended Core Team

ERA Extended Core Team
type: Form

EECT
type: Form

EECT
type: Form

ERG - Euro Radio Gateway
type: LexicalEntry
type: MultiwordExpression
canonical form: ERG - Euro Radio Gateway
sense: ERG-----EURO--RADIO--GATEWAY lexSense

ERG-----EURO--RADIO--GATEWAY lexConcept
type: LexicalConcept
definition: ERG - Euro Radio Gateway

ERG - Euro Radio Gateway
type: Form

ERJU Hazard Database
type: LexicalEntry
type: MultiwordExpression
canonical form: ERJU Hazard Database
sense: ERJU--HAZARD--DATABASE lexSense

ERJU--HAZARD--DATABASE lexConcept
type: LexicalConcept
definition: ERJU Hazard Database. A collection existing hazard lists of known hazards and accidents which is initiated and maintained by ERJU's PRAMS domain with the aim to provide a harmonized set of hazards/accidents.

ERJU Hazard Database
type: Form

Error correction
type: LexicalEntry
type: MultiwordExpression
canonical form: Error correction
sense: ERROR--CORRECTION lexSense

ERROR--CORRECTION lexConcept
type: LexicalConcept
definition: Error corrections are a type of evolutions, covered by the Evolution management process. Several types of error correction at building block level can occur: * error correction of the TSI, because it is incorrect (curently not covered by the Evolution Management process). * error correction of the specification, because it is not compliant with the TSI. * error correction of the specification, because it is incorrect * error correction of the source code, because it is not implementing correctly the specification i.e. "deviating from intended functions and/or performance". Error corrections are basically defined in: * SPPRAMSS-4525 - [Directive 2016/797] (Article 16) and * SPPRAMSS-328 - [TSI CCS + (EU) 2023/1695] (section 6.5 Management of errors and 7.2.10 ) More details are defined in SPPRAMSS-14396 - Error correction.

Error correction
type: Form

ERTMS - European Rail Traffic Management System
type: LexicalEntry
type: MultiwordExpression
canonical form: ERTMS - European Rail Traffic Management System
sense: ERTMS-----EUROPEAN--RAIL--TRAFFIC--MANAGEMENT--SYSTEM lexSense

ERTMS-----EUROPEAN--RAIL--TRAFFIC--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: ERTMS - European Rail Traffic Management System

ERTMS - European Rail Traffic Management System
type: Form

EUG
type: Acronym
type: LexicalEntry
acronym for: ERTMS--USERS--GROUP label
canonical form: EUG

ERTMS--USERS--GROUP lexConcept
type: LexicalConcept
definition: ERTMS Users Group

ERTMS Users Group
type: Form

EUG
type: Form

ATO-TS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ERTMS ATO--TRACKSIDE label
canonical form: ATO-TS

ERTMS ATO--TRACKSIDE lexConcept
type: LexicalConcept
definition: ERTMS/ATO Trackside (ATO-TS) is the ERTMS/ATO trackside subsystem. ERTMS/ATO provides a set of non-safety functions related to speed control, accurate stopping, door opening and closing, and other functions traditionally assigned to a driver, while the safety of operation is still ensured by ETCS with regards to the speed and distance limits and also by other safe systems.

ERTMS/ATO Trackside
type: Form

ATO-TS
type: Form

Essential Function
type: LexicalEntry
type: MultiwordExpression
canonical form: Essential Function
sense: ESSENTIAL--FUNCTION lexSense

ESSENTIAL--FUNCTION lexConcept
type: LexicalConcept
definition: Function or capability that is required to maintain health, safety, the environment (HSE) and availability for the equipment under control (definition from IEC 62443-4-2) Note: Essential functions include, but are not limited to, the safety instrumented function (SIF), the control function and the ability of the operator to view and manipulate the equipment under control. The loss of essential functions is commonly termed loss of protection, loss of control and loss of view respectively. In some industries additional functions such as history may be considered essential. In the context of the ERJU System Pillar all systems in scope provide functionality as defined in "Essential functions". Note: IEC 63452 definition: All functions needed to operate the railway system, such as per example traffic control, speed control, traction/brake control,...

ESSENTIAL--FUNCTION lexConcept 2
type: LexicalConcept
definition: Function or capability that is required to maintain health, safety, the environment (HSE) and availability for the equipment under control (definition from IEC 62443-4-2) Note: Essential functions include, but are not limited to, the safety instrumented function (SIF), the control function and the ability of the operator to view and manipulate the equipment under control. The loss of essential functions is commonly termed loss of protection, loss of control and loss of view respectively. In some industries additional functions such as history may be considered essential. In the context of the ERJU System Pillar all systems in scope provide functionality as defined in "Essential functions". Note: IEC 63452 definition: All functions needed to operate the railway system, such as per example traffic control, speed control, traction/brake control,...

Essential Function
type: Form

Estimated departure time
type: LexicalEntry
type: MultiwordExpression
canonical form: Estimated departure time
sense: ESTIMATED--DEPARTURE--TIME lexSense

ESTIMATED--DEPARTURE--TIME lexConcept
type: LexicalConcept
definition: 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
type: Form

Estimated Distance
type: LexicalEntry
type: MultiwordExpression
canonical form: Estimated Distance
sense: ESTIMATED--DISTANCE lexSense

ESTIMATED--DISTANCE lexConcept
type: LexicalConcept
definition: It is expressed as the distance along the track centreline between a reference location and the estimated train front end position.

Estimated Distance
type: Form

Estimated Train Front End Position
type: LexicalEntry
type: MultiwordExpression
canonical form: Estimated Train Front End Position
sense: ESTIMATED--TRAIN--FRONT--END--POSITION lexSense

ESTIMATED--TRAIN--FRONT--END--POSITION lexConcept
type: LexicalConcept
definition: The position the ERTMS/ETCS localisation on-board equipment estimates the train front end is at, with the highest probability according to the physical characteristics of the train and to the localisation working conditions. Also referred to as “Estimated Position” SUBSET-023.

Estimated Train Front End Position
type: Form

ETCS (CCD display)
type: LexicalEntry
type: MultiwordExpression
canonical form: ETCS (CCD display)
sense: ETCS--CCD--DISPLAY lexSense

ETCS--CCD--DISPLAY lexConcept
type: LexicalConcept
definition: The display associated to this system is called CCD (Control Command Display) in UIC-612. The functionalities and the ergonomics of this system are standardised in the subset 026 and ERA DMI 15560.The CCD display is located in front of the driver according to UIC-612-0, EN 16186-2 (chapter 7.21). According to subset 091, some THR are related to the DMI and involve THR equivalent to SIL2. Information of ETCS are mandatory when train is in motion. It could be debatable if this is also the case at standstill. There is a proposal for standardisation communication between ETCS and MDS known as Subset-121. {comment:153}

ETCS--CCD--DISPLAY lexConcept 2
type: LexicalConcept
definition: The display associated to this system is called CCD (Control Command Display) in UIC-612. The functionalities and theergonomics of this system are standardised in the subset 026 and ERA DMI 15560.The CCD display is located in front of the driver according to UIC-612-0, EN 16186-2 (chapter 7.21).According to subset 091, some THR are related to the DMI and involve THR equivalent to SIL2.Information of ETCS are mandatory when train is in motion. It could be debatable if this is also the case at standstill. Communication between ETCS and MDS is standardised in subset 121.

ETCS (CCD display)
type: Form

ETP-OB - European Train Protection On-Board
type: LexicalEntry
type: MultiwordExpression
canonical form: ETP-OB - European Train Protection On-Board
sense: ETP-OB-----EUROPEAN--TRAIN--PROTECTION--ON-BOARD lexSense

ETP-OB-----EUROPEAN--TRAIN--PROTECTION--ON-BOARD lexConcept
type: LexicalConcept
definition: ETP-OB - European Train Protection On-Board Note: ETP-OB equivalent with ETCS-OB

ETP-OB - European Train Protection On-Board
type: Form

EUSPA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EU--AGENCY--FOR--THE--SPACE--PROGRAMME label
canonical form: EUSPA

EU--AGENCY--FOR--THE--SPACE--PROGRAMME lexConcept
type: LexicalConcept
definition: EU Agency for the Space Programme

EU Agency for the Space Programme
type: Form

EUSPA
type: Form

EUG - ERTMS Users Group
type: LexicalEntry
type: MultiwordExpression
canonical form: EUG - ERTMS Users Group
sense: EUG-----ERTMS--USERS--GROUP lexSense

EUG-----ERTMS--USERS--GROUP lexConcept
type: LexicalConcept
definition: EUG - ERTMS Users Group

EUG - ERTMS Users Group
type: Form

COM
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPEAN--COMMISSION label
canonical form: COM

EUROPEAN--COMMISSION lexConcept
type: LexicalConcept
definition: European Commission

European Commission
type: Form

COM
type: Form

CENELEC
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPEAN--COMMITTEE--FOR--ELECTROTECHNICAL--STANDARDIZATION label
canonical form: CENELEC

EUROPEAN--COMMITTEE--FOR--ELECTROTECHNICAL--STANDARDIZATION lexConcept
type: LexicalConcept
definition: European Committee for Electrotechnical Standardization

European Committee for Electrotechnical Standardization
type: Form

CENELEC
type: Form

CEN
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPEAN--COMMITTEE--FOR--STANDARDIZATION label
canonical form: CEN

EUROPEAN--COMMITTEE--FOR--STANDARDIZATION lexConcept
type: LexicalConcept
definition: European Committee for Standardization

European Committee for Standardization
type: Form

CEN
type: Form

EDDP
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--DAC--DELIVERY--PROGRAM label
canonical form: EDDP

EUROPEAN--DAC--DELIVERY--PROGRAM lexConcept
type: LexicalConcept
definition: European DAC Delivery Program

European DAC Delivery Program
type: Form

EDDP
type: Form

EGNOS
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--GEOSTATIONARY--NAVIGATION--OVERLAY--SERVICE label
canonical form: EGNOS

EUROPEAN--GEOSTATIONARY--NAVIGATION--OVERLAY--SERVICE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: European Geostationary Navigation Overlay Service

EUROPEAN--GEOSTATIONARY--NAVIGATION--OVERLAY--SERVICE lexConcept 2
type: LexicalConcept
definition: European Geostationary Navigation Overlay Service, European satellite navigation system

European Geostationary Navigation Overlay Service
type: Form

EGNOS
type: Form

EGNOS
type: Form

EI#7
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPEAN--INSTRUCTION--7 label
canonical form: EI#7

EUROPEAN--INSTRUCTION--7 lexConcept
type: LexicalConcept
definition: Authorisation to start after preparing a movement.{comment:132}

European Instruction 7
type: Form

EI#7
type: Form

EI
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--INSTRUCTION label
canonical form: EI

EUROPEAN--INSTRUCTION lexConcept
type: LexicalConcept
definition: {comment:129}{comment:150}A European Instruction is an instruction issued by the Signaller to the Driver to ensure safe operation when this cannot be provided by the signalling system. A European Instruction will state for example: - which train it is issued to - the time and date it was issued - location of train (if relevant) - location of issuer - a clear, precise, unambiguous instruction - a Unique Identification. The EI precises speed, special conditions for train movement and other requests for safe operations.

European Instruction
type: Form

EI
type: Form

EPF
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--PASSENGERS --FEDERATION label
canonical form: EPF

EUROPEAN--PASSENGERS --FEDERATION lexConcept
type: LexicalConcept
definition: European Passengers' Federation

European Passengers' Federation
type: Form

EPF
type: Form

EIM
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPEAN--RAIL--INFRASTRUCTURE--MANAGERS label
canonical form: EIM

EUROPEAN--RAIL--INFRASTRUCTURE--MANAGERS lexConcept
type: LexicalConcept
definition: European Rail Infrastructure Managers

European Rail Infrastructure Managers
type: Form

EIM
type: Form

ERRAC
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--RAIL--RESEARCH--ADVISORY--COUNCIL label
canonical form: ERRAC

EUROPEAN--RAIL--RESEARCH--ADVISORY--COUNCIL lexConcept
type: LexicalConcept
definition: European Rail Research Advisory Council

European Rail Research Advisory Council
type: Form

ERRAC
type: Form

ERTMS
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--RAIL--TRAFFIC--MANAGEMENT--SYSTEM label
canonical form: ERTMS

EUROPEAN--RAIL--TRAFFIC--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: European Rail Traffic Management System

European Rail Traffic Management System
type: Form

ERTMS
type: Form

ERDS
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--RAILWAY--DATA--SPACE label
canonical form: ERDS

EUROPEAN--RAILWAY--DATA--SPACE lexConcept
type: LexicalConcept
definition: European Railway Data Space

European Railway Data Space
type: Form

ERDS
type: Form

ERTMS
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--RAILWAY--TRAFFIC--MANAGEMENT--SYSTEM label
canonical form: ERTMS

EUROPEAN--RAILWAY--TRAFFIC--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: European Railway Traffic Management System (ERTMS) is a single European signalling and speed control system that ensures interoperability of the national railway systems, reducing the purchasing and maintenance costs of the signalling systems as well as increasing the speed of trains, the capacity of infrastructure and the level of safety in rail transport. ERTMS comprises of the European Train Control System (ETCS), i.e. a cab-signalling system that incorporates automatic train protection, the Global System for Mobile communications for Railways (GSM-R) and operating rules. (ERA definition)

EUROPEAN--RAILWAY--TRAFFIC--MANAGEMENT--SYSTEM lexConcept 2
type: LexicalConcept
definition: European Railway Traffic Management System (ERTMS) is a single European signalling and speed control system that ensures interoperability of the national railway systems, reducing the purchasing and maintenance costs of the signalling systems as well as increasing the speed of trains, the capacity of infrastructure and the level of safety in rail transport. (ERA definition)

European Railway Traffic Management System
type: Form

ERTMS
type: Form

ERTMS
type: Form

ESC
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--SECURITIES--COMMITTEE label
canonical form: ESC

EUROPEAN--SECURITIES--COMMITTEE lexConcept
type: LexicalConcept
definition: European Securities Committee

European Securities Committee
type: Form

ESC
type: Form

ESA
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--SPACE--AGENCY label
canonical form: ESA

EUROPEAN--SPACE--AGENCY lexConcept
type: LexicalConcept
definition: European Space Agency

European Space Agency
type: Form

ESA
type: Form

ESO
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--STANDARDIZATION--ORGANIZATION label
canonical form: ESO

EUROPEAN--STANDARDIZATION--ORGANIZATION lexConcept
type: LexicalConcept
definition: European Standardization Organization

European Standardization Organization
type: Form

ESO
type: Form

ESIF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPEAN--STRUCTURAL--AND--INVESTMENT--FUNDS label
canonical form: ESIF

EUROPEAN--STRUCTURAL--AND--INVESTMENT--FUNDS lexConcept
type: LexicalConcept
definition: European Structural and Investment Funds

European Structural and Investment Funds
type: Form

ESIF
type: Form

ETSI
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--TELECOMMUNICATIONS--STANDARDS--INSTITUTE label
canonical form: ETSI

EUROPEAN--TELECOMMUNICATIONS--STANDARDS--INSTITUTE lexConcept
type: LexicalConcept
definition: European Telecommunications Standards Institute

European Telecommunications Standards Institute
type: Form

ETSI
type: Form

ETPS
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--TRACKSIDE--PROTECTION--SYSTEM label
canonical form: ETPS

EUROPEAN--TRACKSIDE--PROTECTION--SYSTEM lexConcept
type: LexicalConcept
definition: The Trackside Protection System is the core system of Traffic CS, implementing the safety critical functions. The Trackside Protection System controls all Trackside Assets Control and Supervision (TACS) connected to ETPS, for example points, level crossings, and manages Movement Permissions for trains, whilst maintaining the safety of the railway.

European Trackside Protection System
type: Form

ETPS
type: Form

ETM
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--TRAFFIC--MANAGEMENT label
canonical form: ETM

EUROPEAN--TRAFFIC--MANAGEMENT lexConcept
type: LexicalConcept
definition: European traffic management

European traffic management
type: Form

ETM
type: Form

ETCS
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--TRAIN--CONTROL--SYSTEM label
canonical form: ETCS

EUROPEAN--TRAIN--CONTROL--SYSTEM lexConcept
type: LexicalConcept
definition: ETCS - European Train Control System

EUROPEAN--TRAIN--CONTROL--SYSTEM lexConcept 2
type: LexicalConcept
definition: European Train Control System (ETCS) is a cab-signalling system that incorporates automatic train protection (ERA definition). ETCS in the frame of SERA will support the following Levels: * L2 with fixed train detection (classic L2 with trackside detection (track circuits, axle-counters, …)) * L2 with hybrid train detection (virtual fixed or moving blocks with trackside detection (axle-counters, …)) – formerly known as Hybrid L3 * L2 with virtual fixed or moving blocks and train integrity (no trackside detection) – formerly known as pure L3

European Train Control System
type: Form

ETCS
type: Form

ETCS
type: Form

ETF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPEAN--TRANSPORT--WORKERS --FEDERATION label
canonical form: ETF

EUROPEAN--TRANSPORT--WORKERS --FEDERATION lexConcept
type: LexicalConcept
definition: European Transport Workers' Federation

European Transport Workers' Federation
type: Form

ETF
type: Form

ENISA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPEAN--UNION--AGENCY--FOR--CYBERSECURITY label
canonical form: ENISA

EUROPEAN--UNION--AGENCY--FOR--CYBERSECURITY lexConcept
type: LexicalConcept
definition: European Union Agency for cybersecurity

European Union Agency for cybersecurity
type: Form

ENISA
type: Form

ERA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPEAN--UNION--AGENCY--FOR--RAILWAYS label
canonical form: ERA

EUROPEAN--UNION--AGENCY--FOR--RAILWAYS lexConcept
type: LexicalConcept
definition: European Union Agency for Railways

European Union Agency for Railways
type: Form

ERA
type: Form

EVN
type: Acronym
type: LexicalEntry
acronym for: EUROPEAN--VEHICLE--NUMBER label
canonical form: EVN

EUROPEAN--VEHICLE--NUMBER lexConcept
type: LexicalConcept
definition: European Vehicle Number

European Vehicle Number
type: Form

EVN
type: Form

JU
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPE S--RAIL--JOINT--UNDERTAKING label
canonical form: JU

ERJU
type: Acronym
type: LexicalEntry
acronym for: EUROPE S--RAIL--JOINT--UNDERTAKING label
canonical form: ERJU

EUROPE S--RAIL--JOINT--UNDERTAKING lexConcept
type: LexicalConcept
definition: Organisation being tasked with the standardisation in the railway domain at European level.

EUROPE S--RAIL--JOINT--UNDERTAKING lexConcept 2
type: LexicalConcept
definition: (Europe’s Rail) Joint Undertaking

EUROPE S--RAIL--JOINT--UNDERTAKING lexConcept 3
type: LexicalConcept
definition: Europe’s Rail Joint Undertaking

Europe’s Rail Joint Undertaking
type: Form

ERJU
type: Form

JU
type: Form

ERJU
type: Form

EU-Rail
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EUROPE S--RAIL label
canonical form: EU-Rail

EUROPE S--RAIL lexConcept
type: LexicalConcept
definition: Europe's Rail

Europe's Rail
type: Form

EU-Rail
type: Form

EVC - European Vital Computer
type: LexicalEntry
type: MultiwordExpression
canonical form: EVC - European Vital Computer
sense: EVC-----EUROPEAN--VITAL--COMPUTER lexSense

EVC-----EUROPEAN--VITAL--COMPUTER lexConcept
type: LexicalConcept
definition: EVC - European Vital Computer

EVC - European Vital Computer
type: Form

EDA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EVENT-DRIVEN--ARCHITECTURE label
canonical form: EDA

EVENT-DRIVEN--ARCHITECTURE lexConcept
type: LexicalConcept
definition: Event-driven architecture

Event-driven architecture
type: Form

EDA
type: Form

Evolution
type: LexicalEntry
type: Word
canonical form: Evolution
sense: EVOLUTION lexSense

EVOLUTION lexConcept
type: LexicalConcept
definition: Evolution is the process of gradually developing, refining or improving parts of the System Pillar Harmonized Operational Processes respectively the System Pillar Reference Architecture (SPRA).

EVOLUTION lexConcept 2
type: LexicalConcept
definition: Evolution refers to the gradual development and refinement of a system over time, through a process of adaptation and improvement. Evolution is often driven by the need to to improve system reliability , efficiency, or other key metrics, while addressing new or changing needs and challenges.

Evolution
type: Form

Evolvability
type: LexicalEntry
type: Word
canonical form: Evolvability
sense: EVOLVABILITY lexSense

EVOLVABILITY lexConcept
type: LexicalConcept
definition: Evolvability is the ability to easily adapt to new technologies or to extend the functionality of the CCS system without the involvement of the original supplier.{comment:429}

Evolvability
type: Form

Exchange item
type: LexicalEntry
type: MultiwordExpression
canonical form: Exchange item
sense: EXCHANGE--ITEM lexSense

EXCHANGE--ITEM lexConcept
type: LexicalConcept
definition: Element transferred through an interface, which can be either energy, matter, and/or information. A exchange item carries elements with the same transport conditions, simultaneously with the same non-functional properties.

Exchange item
type: Form

Exchange scenario
type: LexicalEntry
type: MultiwordExpression
canonical form: Exchange scenario
sense: EXCHANGE--SCENARIO lexSense

EXCHANGE--SCENARIO lexConcept
type: LexicalConcept
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.

Exchange scenario
type: Form

Exchangeability
type: LexicalEntry
type: Word
canonical form: Exchangeability
sense: EXCHANGEABILITY lexSense

EXCHANGEABILITY lexConcept
type: LexicalConcept
definition: Exchangeability is the ability to replace a sub-system from supplier A by a subsystem from supplier B without affecting other sub-systems or the overall system/subsystem and with a reasonable integration effort and/or certification effort. Different to interchangeability, exchangeability does not specify physical characteristics of subsystem. {comment:1413}

Exchangeability
type: Form

Exchanged Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Exchanged Data
sense: EXCHANGED--DATA lexSense

EXCHANGED--DATA lexConcept
type: LexicalConcept
definition: Data interchanged between at least two entities (in this case, data generated and processed by the IMs).

Exchanged Data
type: Form

Exclusive MP Area (EMPA)
type: LexicalEntry
type: MultiwordExpression
canonical form: Exclusive MP Area (EMPA)
sense: EXCLUSIVE--MP--AREA--EMPA lexSense

EXCLUSIVE--MP--AREA--EMPA lexConcept
type: LexicalConcept
definition: Within an EMPA, at most one MP is allowed.

Exclusive MP Area (EMPA)
type: Form

Existing Railway System
type: LexicalEntry
type: MultiwordExpression
canonical form: Existing Railway System
sense: EXISTING--RAILWAY--SYSTEM lexSense

EXISTING--RAILWAY--SYSTEM lexConcept
type: LexicalConcept
definition: Existing rail system means the infrastructure composed of lines and fixed installations of the existing rail network as well as the vehicles of all categories and origins traveling on that infrastructure

Existing Railway System
type: Form

Extended View
type: LexicalEntry
type: MultiwordExpression
canonical form: Extended View
sense: EXTENDED--VIEW lexSense

EXTENDED--VIEW lexConcept
type: LexicalConcept
definition: View displayed on more than one Display Panel.

EXTENDED--VIEW lexConcept 2
type: LexicalConcept
definition: {comment:89} View displayed on more than one Display Panel.

EXTENDED--VIEW lexConcept 3
type: LexicalConcept
definition: View displayed on more than one Display Panel.

EXTENDED--VIEW lexConcept 4
type: LexicalConcept
definition: Extended View View displayed on more than one Display Panel.

Extended View
type: Form

External Button
type: LexicalEntry
type: MultiwordExpression
canonical form: External Button
sense: EXTERNAL--BUTTON lexSense

EXTERNAL--BUTTON lexConcept
type: LexicalConcept
definition: A button which is not directly managed by MDS.

EXTERNAL--BUTTON lexConcept 2
type: LexicalConcept
definition: A button which is not directly managed by MDS.

EXTERNAL--BUTTON lexConcept 3
type: LexicalConcept
definition: A button which is not directly managed by TDS.

EXTERNAL--BUTTON lexConcept 4
type: LexicalConcept
definition: A button which is not directly managed by TDS.

EXTERNAL--BUTTON lexConcept 5
type: LexicalConcept
definition: A button which is not directly managed by TDS.

EXTERNAL--BUTTON lexConcept 6
type: LexicalConcept
definition: A button which is not directly managed by TDS.

EXTERNAL--BUTTON lexConcept 7
type: LexicalConcept
definition: A button which is not directly managed by TDS.

EXTERNAL--BUTTON lexConcept 8
type: LexicalConcept
definition: External Button A button which is not directly managed by TDS.

External Button
type: Form

I1
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EXTERNAL--DIAGNOSTIC--CONFIGURATION--AND--IT--SECURITY--INTERFACE--S label
canonical form: I1

EXTERNAL--DIAGNOSTIC--CONFIGURATION--AND--IT--SECURITY--INTERFACE--S lexConcept
type: LexicalConcept
definition: The external Diagnostic, Configuration and IT Security Interface I1 (Interface 1) comprises communication-based interfaces between rail systems and central infrastructure components such as diagnostics, IT-security services and remote update.

External Diagnostic, Configuration and IT Security Interface(s)
type: Form

I1
type: Form

ESPR
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: EXTERNAL--SP--RELEASE label
canonical form: ESPR

EXTERNAL--SP--RELEASE lexConcept
type: LexicalConcept
definition: External SP Releases are delivered outside of the EU-RAIL program. These releases are delivered publicly to the sector for feedback on CR's (see EU Rail and Harmonisation Document), to ERA for TSI updates, to the Standardisation{comment:319} bodies and to RU's and IM's to perform call of tender. It is expected that these releases are mature releases with the maturity demonstrated, for instance thanks to demonstrators in Innovation Pillar.

External SP Release
type: Form

ESPR
type: Form

fail-safe [821-01-10]
type: LexicalEntry
type: MultiwordExpression
canonical form: fail-safe [821-01-10]
sense: FAIL-SAFE-- 821-01-10 lexSense

FAIL-SAFE-- 821-01-10 lexConcept
type: LexicalConcept
definition: able to enter or remain in a safe state in the event of a failure

fail-safe [821-01-10]
type: Form

fail-safe
type: LexicalEntry
type: Word
canonical form: fail-safe
sense: FAIL-SAFE lexSense

FAIL-SAFE lexConcept
type: LexicalConcept
definition: able to enter or remain in a safe state in the event of a failure [SOURCE: IEC 60050-821:2017 , 821-01-10]

FAIL-SAFE lexConcept 2
type: LexicalConcept
definition: able to enter or remain in a safe state in the event of a failure [821-01-10 ]

fail-safe
type: Form

failure cause
type: LexicalEntry
type: MultiwordExpression
canonical form: failure cause
sense: FAILURE--CAUSE lexSense

FAILURE--CAUSE lexConcept
type: LexicalConcept
definition: set of circumstances that leads to failure Note 1 to entry: A failure cause may originate during specification, design, manufacture, installation, operation or maintenance of an item. [SOURCE: IEC 60050.192:2015, 192-03-11]

failure cause
type: Form

failure mode
type: LexicalEntry
type: MultiwordExpression
canonical form: failure mode
sense: FAILURE--MODE lexSense

FAILURE--MODE lexConcept
type: LexicalConcept
definition: Manner in which failure occurs. Note 1 to entry: A failure mode may be defined by the function lost or other state transition that occurred. [SOURCE: IEC 60050-192:2015, 192-03-17]

failure mode
type: Form

failure rate [821-12-21]
type: LexicalEntry
type: MultiwordExpression
canonical form: failure rate [821-12-21]
sense: FAILURE--RATE-- 821-12-21 lexSense

FAILURE--RATE-- 821-12-21 lexConcept
type: LexicalConcept
definition: limit of the ratio of the conditional probability that the instant of time, T, of a failure of a product falls within a given time interval (t, t + Δt) and the duration of this interval, Δt, when Δt tends towards zero, given that the item is in an up state at the start of the time interval Note 1 to entry: For applications where distance travelled or number of cycles of operation is more relevant than time then the unit of time can be replaced by the unit of distance or cycles, as appropriate. Note 2 to entry: The term “failure rate” is often used in the sense of “mean failure rate” defined in IEV 192-05-07. [SOURCE: IEC 62278:2002, 3.14, modified]

failure rate [821-12-21]
type: Form

failure rate
type: LexicalEntry
type: MultiwordExpression
canonical form: failure rate
sense: FAILURE--RATE lexSense

FAILURE--RATE lexConcept
type: LexicalConcept
definition: limit of the ratio of the conditional probability that the instant of time, T, of a failure of a product falls within a given time interval (t, t + Δt) and the duration of this interval, Δt, when Δt tends towards zero, given that the item is in an up state at the start of the time interval Note 1 to entry: For applications where distance travelled or number of cycles of operation is more relevant than time then the unit of time can be replaced by the unit of distance or cycles, as appropriate. Note 2 to entry: The term “failure rate” is often used in the sense of “mean failure rate” defined in IEV 192-05-07. [IEC 60050-821, 821-12-21]

FAILURE--RATE lexConcept 2
type: LexicalConcept
definition: limit of the ratio of the conditional probability that the instant of time, T, of a failure of a product falls within a given time interval (t, t + Δt) and the duration of this interval, Δt, when Δt tends towards zero, given that the item is in an up state at the start of the time interval Note 1 to entry: For applications where distance travelled or number of cycles of operation is more relevant than time then the unit of time can be replaced by the unit of distance or cycles, as appropriate. Note 2 to entry: The term “failure rate” is often used in the sense of “mean failure rate” defined in IEV 192-05-07. [821-12-21][IEC 62278:2002, 3.14, modified]

failure rate
type: Form

failure
type: LexicalEntry
type: Word
canonical form: failure
sense: FAILURE lexSense

FAILURE lexConcept
type: LexicalConcept
definition: loss of ability to perform as required Note 1 to entry: A failure of an item is an event that results in a fault of that item: see "fault" (IEV 192-04-01). Note 2 to entry: Qualifiers, such as catastrophic, critical, major, minor, marginal and insignificant, can be used to categorize failures according to the severity of consequences, the choice and definitions of severity criteria depending upon the field of application. Note 3 to entry: Qualifiers, such as misuse, mishandling and weakness, can be used to categorize failures according to the cause of failure. [SOURCE: IEC 60050-192:2015, 192-03-01]

failure
type: Form

fault, <of an item>
type: LexicalEntry
type: MultiwordExpression
canonical form: fault, <of an item>
sense: FAULT--<OF--AN--ITEM> lexSense

FAULT--<OF--AN--ITEM> lexConcept
type: LexicalConcept
definition: inability to perform as required, due to an internal state Note 1 to entry: A fault of an item results from a failure, either of the item itself, or from a deficiency in an earlier stage of the life cycle, such as specification, design, manufacture or maintenance. See latent fault (192-04-08).{comment:215} Note 2 to entry: Qualifiers, such as specification, design, manufacture, maintenance or misuse, may be used to indicate the cause of a fault. Note 3 to entry: The type of fault may be associated with the type of associated failure, e.g. wear-out fault and wear-out failure. Note 4 to entry: The adjective “faulty” designates an item having one or more faults. [SOURCE: IEC 60050-192:2015, 192-04-01]

fault, <of an item>
type: Form

fault correction time
type: LexicalEntry
type: MultiwordExpression
canonical form: fault correction time
sense: FAULT--CORRECTION--TIME lexSense

FAULT--CORRECTION--TIME lexConcept
type: LexicalConcept
definition: part of active corrective maintenance time taken to perform fault correction [SOURCE: IEC 60050-192:2015,192-07-14]

fault correction time
type: Form

fault detection time
type: LexicalEntry
type: MultiwordExpression
canonical form: fault detection time
sense: FAULT--DETECTION--TIME lexSense

FAULT--DETECTION--TIME lexConcept
type: LexicalConcept
definition: DEPRECATED: undetected fault time time interval between failure and detection of the resulting fault [SOURCE: IEC 60050-192:2015,192-07-11]

fault detection time
type: Form

fault localization time
type: LexicalEntry
type: MultiwordExpression
canonical form: fault localization time
sense: FAULT--LOCALIZATION--TIME lexSense

FAULT--LOCALIZATION--TIME lexConcept
type: LexicalConcept
definition: DEPRECATED: fault location time part of active corrective maintenance time taken to complete fault localization

fault localization time
type: Form

fault tree
type: LexicalEntry
type: MultiwordExpression
canonical form: fault tree
sense: FAULT--TREE lexSense

FAULT--TREE lexConcept
type: LexicalConcept
definition: logic diagram showing the faults of sub items, external events, or combinations thereof, which cause a predefined, undesired event [SOURCE: IEC 60050-192:2015, 192-11-07]

fault tree
type: Form

FDFT: Full Digital Freight Train
type: LexicalEntry
type: MultiwordExpression
canonical form: FDFT: Full Digital Freight Train
sense: FDFT---FULL--DIGITAL--FREIGHT--TRAIN lexSense

FDFT---FULL--DIGITAL--FREIGHT--TRAIN lexConcept
type: LexicalConcept
definition: FDFT: Full Digital Freight Train : designates the rolling stock operated according to FDFTO

FDFT: Full Digital Freight Train
type: Form

FCI
type: Acronym
type: LexicalEntry
acronym for: FDFTO--CENTRAL--INSTANCE label
canonical form: FCI

FDFTO--CENTRAL--INSTANCE lexConcept
type: LexicalConcept
definition: FDFTO Central Instance

FDFTO Central Instance
type: Form

FCI
type: Form

feature/function proposed by the system which is not available AND which has no...
type: LexicalEntry
type: MultiwordExpression
canonical form: feature/function proposed by the system which is not available AND which has no...
sense: FEATURE FUNCTION--PROPOSED--BY--THE--SYSTEM--WHICH--IS--NOT--AVAILABLE--AND--WHICH--HAS--NO lexSense

FEATURE FUNCTION--PROPOSED--BY--THE--SYSTEM--WHICH--IS--NOT--AVAILABLE--AND--WHICH--HAS--NO lexConcept
type: LexicalConcept
definition: feature/function proposed by the system which is not available AND which has no solution/procedure that can bypass. Restrictions are related to open CRs, which often should be "translated" in an understandable manner for the customer (baseline user), and sometimes form an operational point of view, testing point of view etc...

feature/function proposed by the system which is not available AND which has no...
type: Form

Feature
type: LexicalEntry
type: Word
canonical form: Feature
sense: FEATURE lexSense

FEATURE lexConcept
type: LexicalConcept
definition: Characteristic of a system in a product line that distinguishes it from other systems in the product line. Those characteristics express either stakeholder-visible variability or implementation variability. Note: In feature-based product line engineering, features express differences among member products. A characteristic common to all member products in the product line is usually not modelled as a feature. Features in railway is everything what can be different when moving between A and B. Variation type / Dependency | Description (image: 5-screenshot-20241129-173318-7.png) | A mandatory features is implicitly selected if its parent feature is selected. (image: 6-screenshot-20241129-173318-8.png) | Only one group of alternative features is possible under a parent node. Exactly one feature has to be selected from a group if the parent feature is selected. The other alternative feature are automatically excluded. (image: 7-screenshot-20241129-173318-9.png) | The optional features are not belonging to each other (building not a group of similar features). If at least one of the optional features is selected the parent node is selected as well. (image: 8-screenshot-20241129-173318-10.png) | Only one group of or features is possible under a parent node and 0..n features can be selected. If at least one of the or features is selected the parent node is selected as well. In principal optional features and or features are equivalent. The only difference is that optional features do not belong to each other and or features are a group of similar features.

Feature
type: Form

FRA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: FEDERAL--RAILROAD--ADMINISTRATION--USA label
canonical form: FRA

FEDERAL--RAILROAD--ADMINISTRATION--USA lexConcept
type: LexicalConcept
definition: Federal Railroad Administration (USA)

Federal Railroad Administration (USA)
type: Form

FRA
type: Form

FFFIS - Form Fit Functional Interface Specification
type: LexicalEntry
type: MultiwordExpression
canonical form: FFFIS - Form Fit Functional Interface Specification
sense: FFFIS-----FORM--FIT--FUNCTIONAL--INTERFACE--SPECIFICATION lexSense

FFFIS-----FORM--FIT--FUNCTIONAL--INTERFACE--SPECIFICATION lexConcept
type: LexicalConcept
definition: In contrast to an FIS (Functional Interface Specification), FFFIS describes not only the functional requirements for an interface, but also its complete, specific design. An FFFIS has the requirement that all devices with an interface developed according to it are interchangeable. "FF - Form Fit" is a classification of interchangeable parts which are identical in shape, fit and function and are therefore interchangeable with one another. An FFFIS is therefore a clear description of an interface between devices or modules.

FFFIS - Form Fit Functional Interface Specification
type: Form

FFFIS - Form-Fit Functional Interface Specification
type: LexicalEntry
type: MultiwordExpression
canonical form: FFFIS - Form-Fit Functional Interface Specification
sense: FFFIS-----FORM-FIT--FUNCTIONAL--INTERFACE--SPECIFICATION lexSense

FFFIS-----FORM-FIT--FUNCTIONAL--INTERFACE--SPECIFICATION lexConcept
type: LexicalConcept
definition: FFFIS - Form-Fit Functional Interface Specification

FFFIS - Form-Fit Functional Interface Specification
type: Form

FFFIS
type: LexicalEntry
type: Word
canonical form: FFFIS
sense: FFFIS lexSense

FFFIS lexConcept
type: LexicalConcept
definition: Form, Fit and Function Interface Specification{comment:216}

FFFIS
type: Form

FIS - Functional Interface Specification
type: LexicalEntry
type: MultiwordExpression
canonical form: FIS - Functional Interface Specification
sense: FIS-----FUNCTIONAL--INTERFACE--SPECIFICATION lexSense

FIS-----FUNCTIONAL--INTERFACE--SPECIFICATION lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: FIS - Functional Interface Specification

FIS-----FUNCTIONAL--INTERFACE--SPECIFICATION lexConcept 2
type: LexicalConcept
definition: Functional requirements and description of an interface. This clarifies also the functional apportionment and related safety requirements of the two sub-systems of the interface.

FIS-----FUNCTIONAL--INTERFACE--SPECIFICATION lexConcept 3
type: LexicalConcept
definition: FIS - Functional Interface Specification

FIS - Functional Interface Specification
type: Form

FAM
type: Acronym
type: LexicalEntry
acronym for: FIXED--ASSET--MGMT label
canonical form: FAM

FIXED--ASSET--MGMT lexConcept
type: LexicalConcept
definition: Fixed asset mgmt

Fixed asset mgmt
type: Form

FAM
type: Form

FB
type: Acronym
type: LexicalEntry
acronym for: FIXED--BLOCK label
canonical form: FB

FIXED--BLOCK lexConcept
type: LexicalConcept
definition: A block in which the extremities of the block sections are at fixed locations. The signalling allows a train to move from one block to the next, normally only when the block ahead is clear.

Fixed Block
type: Form

FB
type: Form

FVB
type: Acronym
type: LexicalEntry
acronym for: FIXED--VIRTUAL--BLOCK label
canonical form: FVB

FIXED--VIRTUAL--BLOCK lexConcept
type: LexicalConcept
definition: A Fixed Virtual Block is a Fixed Block where the limits are virtual and do not necessarily correspond to train detection boundaries.

Fixed Virtual Block
type: Form

FVB
type: Form

FA
type: Acronym
type: LexicalEntry
acronym for: FLAGSHIP--AREA label
canonical form: FA

FLAGSHIP--AREA lexConcept
type: LexicalConcept
definition: Flagship Area

Flagship Area
type: Form

FA
type: Form

Fleet
type: LexicalEntry
type: Word
canonical form: Fleet
sense: FLEET lexSense

FLEET lexConcept
type: LexicalConcept
definition: All the vehicles of the railway company

Fleet
type: Form

FMECA
type: LexicalEntry
type: Word
canonical form: FMECA
sense: FMECA lexSense

FMECA lexConcept
type: LexicalConcept
definition: failure modes, effects and criticality analysis quantitative or qualitative method of analysis that involves failure modes and effects analysis together with a consideration of the probability of the failure mode occurrence and the severity of the effects Note 1 to entry: The term "fault mode, effects and criticality analysis" in IEC 60050-191:1990 (now withdrawn; replaced by IEC 60050-192:2015) is deprecated, since a fault (192-04-01) is a state and cannot logically have a mode, whereas a failure mode (192-03-17) is a change of state. [SOURCE: IEC 60050-192:2015, 192-11-06] Note 2 to entry: FMEA is a systematic method of evaluating an item or process to identify the ways in which it might potentially fail, and the effects of the mode of failure upon the performance of the item or process and on the surrounding environment and personnel. Failure modes may be prioritized according to their importance. The prioritization can be based on a ranking of the severity alone, or this can be combined with other measures of importance. When failure modes are prioritized, the process is referred to as failure modes, effects and criticality analysis (FMECA).

FMECA
type: Form

Forecast
type: LexicalEntry
type: Word
canonical form: Forecast
sense: FORECAST lexSense

FORECAST lexConcept
type: LexicalConcept
definition: The forecast displays the future state of traffic. It based on the current operational state. The forecast projects the current operational plan into the future. A forecast for each train run under consideration of mutual train influence is processed (train run time, section run time, minimal section run time, detailed topology, headways and train sequence, circulation, connection, etc.).

Forecast
type: Form

FFF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: FORM--FIT--AND--FUNCTION label
canonical form: FFF

FORM--FIT--AND--FUNCTION lexConcept
type: LexicalConcept
definition: Form, Fit and Function

Form, Fit and Function
type: Form

FFF
type: Form

FFFIS
type: Acronym
type: LexicalEntry
acronym for: FORM--FIT--FUNCTION--INTERFACE--SPECIFICATION label
canonical form: FFFIS

FORM--FIT--FUNCTION--INTERFACE--SPECIFICATION lexConcept
type: LexicalConcept
definition: Form Fit Function Interface Specification

Form Fit Function Interface Specification
type: Form

FFFIS
type: Form

FFFIS
type: Acronym
type: LexicalEntry
acronym for: FORM--FIT--FUNCTIONAL--INTERFACE--SPECIFICATION label
canonical form: FFFIS

FORM--FIT--FUNCTIONAL--INTERFACE--SPECIFICATION lexConcept
type: LexicalConcept
definition: 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.

FORM FIT FUNCTIONAL INTERFACE SPECIFICATION
type: Form

FFFIS
type: Form

FM
type: Acronym
type: LexicalEntry
acronym for: FOUNDING--MEMBERS label
canonical form: FM

FOUNDING--MEMBERS lexConcept
type: LexicalConcept
definition: Founding Members

Founding Members
type: Form

FM
type: Form

FP - Flagship Projects
type: LexicalEntry
type: MultiwordExpression
canonical form: FP - Flagship Projects
sense: FP-----FLAGSHIP--PROJECTS lexSense

FP-----FLAGSHIP--PROJECTS lexConcept
type: LexicalConcept
definition: FP - Flagship Projects

FP - Flagship Projects
type: Form

FPMH
type: LexicalEntry
type: Word
canonical form: FPMH
sense: FPMH lexSense

FPMH lexConcept
type: LexicalConcept
definition: Failures Per Million Hours{comment:96}

FPMH
type: Form

FPMK
type: LexicalEntry
type: Word
canonical form: FPMK
sense: FPMK lexSense

FPMK lexConcept
type: LexicalConcept
definition: Failures Per Million Kilometres{comment:97}

FPMK
type: Form

FRMCS - Future Railway Mobile Communication System
type: LexicalEntry
type: MultiwordExpression
canonical form: FRMCS - Future Railway Mobile Communication System
sense: FRMCS-----FUTURE--RAILWAY--MOBILE--COMMUNICATION--SYSTEM lexSense

FRMCS-----FUTURE--RAILWAY--MOBILE--COMMUNICATION--SYSTEM lexConcept
type: LexicalConcept
definition: FRMCS - Future Railway Mobile Communication System

FRMCS - Future Railway Mobile Communication System
type: Form

FS - Full Supervision Mode in ETCS
type: LexicalEntry
type: MultiwordExpression
canonical form: FS - Full Supervision Mode in ETCS
sense: FS-----FULL--SUPERVISION--MODE--IN--ETCS lexSense

FS-----FULL--SUPERVISION--MODE--IN--ETCS lexConcept
type: LexicalConcept
definition: FS - Full Supervision Mode in ETCS{comment:26}

FS - Full Supervision Mode in ETCS
type: Form

FSA : FDFTO System Authority
type: LexicalEntry
type: MultiwordExpression
canonical form: FSA : FDFTO System Authority
sense: FSA-----FDFTO--SYSTEM--AUTHORITY lexSense

FSA-----FDFTO--SYSTEM--AUTHORITY lexConcept
type: LexicalConcept
definition: FSA : FDFTO System Authority

FSA : FDFTO System Authority
type: Form

FSO : FDFTO system organization
type: LexicalEntry
type: MultiwordExpression
canonical form: FSO : FDFTO system organization
sense: FSO-----FDFTO--SYSTEM--ORGANIZATION lexSense

FSO-----FDFTO--SYSTEM--ORGANIZATION lexConcept
type: LexicalConcept
definition: FSO : FDFTO system organization

FSO : FDFTO system organization
type: Form

FTA
type: LexicalEntry
type: Word
canonical form: FTA
sense: FTA lexSense

FTA lexConcept
type: LexicalConcept
definition: fault tree analysis deductive analysis using fault trees Note 1 to entry: See also fault tree (192-11-07 SPPRAMSS-4464 - fault tree ). [SOURCE: IEC 60050-192:2015, 192-11-08]

FTA lexConcept 2
type: LexicalConcept
definition: The Fault Tree Analysis (FTA) deals with the identification and investigation of conditions and influencing variables that lead to or contribute to the occurrence or potentially possible occurrence of a defined main event. For the Fault Tree Analysis, this event is usually the blocking or impairment of system performance, safety or other important operational features

FTA
type: Form

Full Backwards Compatibility
type: LexicalEntry
type: MultiwordExpression
canonical form: Full Backwards Compatibility
sense: FULL--BACKWARDS--COMPATIBILITY lexSense

FULL--BACKWARDS--COMPATIBILITY lexConcept
type: LexicalConcept
definition: Full backward compatibility, also known as "complete backward compatibility," refers to a situation in which a newer version of software, hardware, or a system is not only compatible with the previous version but also ensures compatibility with all previous versions and features without exceptions. In other words, any software, data, or hardware that worked with older versions will work seamlessly and without any issues with the new version. With full backward compatibility, users can transition to the latest version with confidence, knowing that they won't encounter any incompatibilities or disruptions. This level of compatibility often requires careful design and testing to ensure that all legacy functionalities and components are supported and function correctly in the newer version.

Full Backwards Compatibility
type: Form

Full Brake Test -
type: LexicalEntry
type: MultiwordExpression
canonical form: Full Brake Test -
sense: FULL--BRAKE--TEST lexSense

FULL--BRAKE--TEST lexConcept
type: LexicalConcept
definition: Full Brake Test -

Full Brake Test -
type: Form

FDFTO
type: Acronym
type: LexicalEntry
acronym for: FULL--DIGITAL--FREIGHT--TRAIN--OPERATIONS label
canonical form: FDFTO

FULL--DIGITAL--FREIGHT--TRAIN--OPERATIONS lexConcept
type: LexicalConcept
definition: Full Digital Freight Train Operations

Full Digital Freight Train Operations
type: Form

FDFTO
type: Form

FTE
type: Acronym
type: LexicalEntry
acronym for: FULL--TIME--EQUIVALENT label
canonical form: FTE

FULL--TIME--EQUIVALENT lexConcept
type: LexicalConcept
definition: Full Time Equivalent

Full Time Equivalent
type: Form

FTE
type: Form

function checkout time
type: LexicalEntry
type: MultiwordExpression
canonical form: function checkout time
sense: FUNCTION--CHECKOUT--TIME lexSense

FUNCTION--CHECKOUT--TIME lexConcept
type: LexicalConcept
definition: part of active maintenance time taken to complete function checkout [SOURCE: IEC 60050-192:2015,192-07-16]

function checkout time
type: Form

FAT
type: Acronym
type: LexicalEntry
acronym for: FUNCTIONAL--APPLICATION--TASK label
canonical form: FAT

FUNCTIONAL--APPLICATION--TASK lexConcept
type: LexicalConcept
definition: A Functional Application Task implements part of the functionality provided by a Functional Application. Depending on its role in the overall function provided by the Functional Application, it has a specific SIL assigned (in-line with total FA SIL definition). It may run replicated in multiple Compartments as FA Task Replicas.

Functional Application Task
type: Form

FAT
type: Form

FA
type: Acronym
type: LexicalEntry
acronym for: FUNCTIONAL--APPLICATION label
canonical form: FA

FUNCTIONAL--APPLICATION lexConcept
type: LexicalConcept
definition: A Functional Application is a comprehensive set of self-contained software functions, assumed to be provided as one product by a single vendor. Depending on its role in the overall function provided by the Functional System, it has a specific SIL (BIL up to SIL4) assigned (in-line with total FS SIL definition).

Functional Application
type: Form

FA
type: Form

Functional apportionment
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional apportionment
sense: FUNCTIONAL--APPORTIONMENT lexSense

FUNCTIONAL--APPORTIONMENT lexConcept
type: LexicalConcept
definition: 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
type: Form

FBS
type: Acronym
type: LexicalEntry
acronym for: FUNCTIONAL--BREAKDOWN--STRUCTURE label
canonical form: FBS

FUNCTIONAL--BREAKDOWN--STRUCTURE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Functional Breakdown Structure

Functional Breakdown Structure
type: Form

FBS
type: Form

Functional Chain
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Chain
sense: FUNCTIONAL--CHAIN lexSense

FUNCTIONAL--CHAIN lexConcept
type: LexicalConcept
definition: Is an ordered set of references to functions and the SPPR-2047 - Functional Exchange that link them, describing one possible path among all the paths forming the data-flow. Functional chains are used to describe the system behaviour in a particular usage context, to contribute to one or more SPPR-2583 - System Capability.{comment:95} Each reference to a function or exchange inside the chain can be qualified by an expectation in the context of the chain (the value that an exchange item or a function attribute should take, for example). Furthermore: A functional chain also specifies constraints or expectations of precedence or anteriority via oriented sequence links. A set of functions and sequence links is a sequence. Control nodes can be defined between the sequence links, to express the parallelism or alternative between several sequences of functions, or, also the iteration or condition of a sequence to be realised. ARCADIA talks only about a functional chain from system level onwards, in operational analysis, it is still called operational process, the methodology is the same for both, therefore no further distinction is made.

Functional Chain
type: Form

Functional Exchange
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Exchange
sense: FUNCTIONAL--EXCHANGE lexSense

FUNCTIONAL--EXCHANGE lexConcept
type: LexicalConcept
definition: A connection between two functions or two components that allows them to convey exchange items.

Functional Exchange
type: Form

FIS
type: Acronym
type: LexicalEntry
acronym for: FUNCTIONAL--INTERFACE--SPECIFICATION label
canonical form: FIS

FUNCTIONAL--INTERFACE--SPECIFICATION lexConcept
type: LexicalConcept
definition: Functional Interface Specification

Functional Interface Specification
type: Form

FIS
type: Form

FRS/FIS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: FUNCTIONAL--REQUIREMENT--SPECIFICATION FUNCTIONAL--INTERFACE--SPECIFICATION label
canonical form: FRS/FIS

FUNCTIONAL--REQUIREMENT--SPECIFICATION FUNCTIONAL--INTERFACE--SPECIFICATION lexConcept
type: LexicalConcept
definition: Functional Requirement Specification/Functional Interface Specification

Functional Requirement Specification/Functional Interface Specification
type: Form

FRS/FIS
type: Form

FRS
type: Acronym
type: LexicalEntry
acronym for: FUNCTIONAL--REQUIREMENTS--SPECIFICATION label
canonical form: FRS

FUNCTIONAL--REQUIREMENTS--SPECIFICATION lexConcept
type: LexicalConcept
definition: Functional Requirements Specification

Functional Requirements Specification
type: Form

FRS
type: Form

Functional requirement
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional requirement
sense: FUNCTIONAL--REQUIREMENT lexSense

FUNCTIONAL--REQUIREMENT lexConcept
type: LexicalConcept
definition: 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.

Functional requirement
type: Form

FSDR
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: FUNCTIONAL--SYSTEM--DEPLOYMENT--RULES label
canonical form: FSDR

FUNCTIONAL--SYSTEM--DEPLOYMENT--RULES lexConcept
type: LexicalConcept
definition: The Functional System Deployment Rules comprises all necessary information for deploying the respective Functional System onto specific approved Compartment Execution Environment(s). These deployment rules are compiled as part of the FS integration process and are part of each integrated, tested and qualified/approved Functional System along with its FS Compartments and all necessary approval documentation.

Functional System Deployment Rules
type: Form

FSDR
type: Form

FS
type: Acronym
type: LexicalEntry
acronym for: FUNCTIONAL--SYSTEM label
canonical form: FS

FUNCTIONAL--SYSTEM lexConcept
type: LexicalConcept
definition: A Functional System is a comprehensive set of self-contained Compartments, assumed to be provided as one product by a single vendor. Depending on its overall function, it has a specific SIL assigned.

Functional System
type: Form

FS
type: Form

Functional Topology
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Topology
sense: FUNCTIONAL--TOPOLOGY lexSense

FUNCTIONAL--TOPOLOGY lexConcept
type: LexicalConcept
definition: The 'Functional Topology' is part of railway infrastructure and defines different functional elements like Signals, Points, etc.

Functional Topology
type: Form

Function
type: LexicalEntry
type: Word
canonical form: Function
sense: FUNCTION lexSense

FUNCTION lexConcept
type: LexicalConcept
definition: A function is a transformation of inputs into outputs which is purpose-oriented and pays towards a higher goal of a system. All possible input and output values are defined by the exchange items allocated to the functional exchanges of the function. Consequently, when the inputs to the system change, the transformations within the system modify the outputs accordingly. They can be available in a range of system states and therefore change its behaviour based on the current state of inputs. The structure of functions does not have to reflect any possible implementation and does not have to follow an object decomposition paradigm, as would be followed normally by software engineers implementing one or more systems. In addition, each function is continuously performed by the system or system actors. They are not created, called and terminated. Functions are allocated to the system or to the system actors. Each function is allocated to one or multiple functional requirements, defining “what” the function is doing. The expected characteristics of functions are then specified via non-functional requirements, which define the “how” (how safe, how accurate, how fast, how reliable, etc.) the function is performing the transformation.

Function
type: Form

Funktional team
type: LexicalEntry
type: MultiwordExpression
canonical form: Funktional team
sense: FUNKTIONAL--TEAM lexSense

FUNKTIONAL--TEAM lexConcept
type: LexicalConcept
definition: A Functional team includes the role owners of the same role. It organizes the work allocation and overall results for that role, including the workflows and working methods. The name of the functional team has a “-F” at the end. The functional teams form a matrix to the organisational units of the SP. If an organisational unit has more persons with the same role, one of them can be delegated to the functional team as a "speaker". Functional teams organise themselves internally. From "outside" (SP processes) the team is addressedaddressed as one actor. The worksplit in the functional teams is decided in the team. The functional teams act with the responsibilities and tasks defined by the role it represents. The functional team is lead and moderated by the participant from System Level 1/ (mostly people from the engineering services, see role allocation table). Functional teams decide in consensus, or escalate to the coregroup. Example for the functional Team “REQ-F”

Funktional team
type: Form

FRMCS
type: Acronym
type: LexicalEntry
acronym for: FUTURE--RAILWAY--MOBILE--COMMUNICATION--SYSTEM label
canonical form: FRMCS

FUTURE--RAILWAY--MOBILE--COMMUNICATION--SYSTEM lexConcept
type: LexicalConcept
definition: Future Railway Mobile Communication System

FUTURE--RAILWAY--MOBILE--COMMUNICATION--SYSTEM lexConcept 2
type: LexicalConcept
definition: Future Railway Mobile Communication System

Future Railway Mobile Communication System
type: Form

FRMCS
type: Form

FRMCS
type: Form

FVA - Functional Vehicle Adapter
type: LexicalEntry
type: MultiwordExpression
canonical form: FVA - Functional Vehicle Adapter
sense: FVA-----FUNCTIONAL--VEHICLE--ADAPTER lexSense

FVA-----FUNCTIONAL--VEHICLE--ADAPTER lexConcept
type: LexicalConcept
definition: FVA - Functional Vehicle Adapter

FVA - Functional Vehicle Adapter
type: Form

FWSI
type: LexicalEntry
type: Word
canonical form: FWSI
sense: FWSI lexSense

FWSI lexConcept
type: LexicalConcept
definition: ‘fatalities and weighted serious injuries (FWSIs)’ means a measurement of the consequences of significant accidents combining fatalities and serious injuries, where 1 serious injury is considered statistically equivalent to 0,1 fatalities;{comment:98} SPPRAMSS-347 - [2009/460/EC]

FWSI
type: Form

GASC
type: LexicalEntry
type: Word
canonical form: GASC
sense: GASC lexSense

GASC lexConcept
type: LexicalConcept
definition: Generic Application Safety Case;SPPRAMSS-334 - [EN 50129:2018/AC:2019-04] {comment:99},SPPRAMSS-335 - [EN 50126-2:2017]

GASC
type: Form

GW
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: GATEWAY label
canonical form: GW

GATEWAY lexConcept
type: LexicalConcept
definition: GW - Gateway

Gateway
type: Form

GW
type: Form

GCU
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: GENERAL--CONTRACT--OF--USE label
canonical form: GCU

GENERAL--CONTRACT--OF--USE lexConcept
type: LexicalConcept
definition: General Contract of Use

General Contract of Use
type: Form

GCU
type: Form

GASC
type: Acronym
type: LexicalEntry
acronym for: GENERIC--APPLICATION--SAFETY--CASE label
canonical form: GASC

GENERIC--APPLICATION--SAFETY--CASE lexConcept
type: LexicalConcept
definition: Generic Application Safety Case (from SPPRAMSS-334 - [EN 50129:2018/AC:2019-04])

Generic Application Safety Case
type: Form

GASC
type: Form

GPSC
type: Acronym
type: LexicalEntry
acronym for: GENERIC--PRODUCT--SAFETY--CASE label
canonical form: GPSC

GENERIC--PRODUCT--SAFETY--CASE lexConcept
type: LexicalConcept
definition: Generic Product Safety Case (from SPPRAMSS-334 - [EN 50129:2018/AC:2019-04])

Generic Product Safety Case
type: Form

GPSC
type: Form

GSL
type: Acronym
type: LexicalEntry
acronym for: GEOMETRIC--SAFETY--LOGIC label
canonical form: GSL

GEOMETRIC--SAFETY--LOGIC lexConcept
type: LexicalConcept
definition: The Geometric Safety Logic is a safety logic which is train-oriented, in contrast to traditional block-oriented safety logic. In train-oriented safety logic, direct train information is evaluated, where block-oriented safety logic, indirect information of an occupation is used. That greatly simplifies the safety logic as it has not to make complicated mapping from occupations to trains.

GEOMETRIC--SAFETY--LOGIC lexConcept 2
type: LexicalConcept
definition: Geometric Safety Logic is a generic safety logic implementation independent from the specific where the paths reserved for train movements can start and end at any geometric location on the railway track. This is in contrast to a more traditional route-based signaling system, where the paths reserved for train movements start and end at fixed, pre-determined locations (e.g. route origin and destination).

Geometric Safety Logic
type: Form

GSL
type: Form

GSL
type: Form

GNSS
type: Acronym
type: LexicalEntry
acronym for: GLOBAL--NAVIGATION--SATELLITE--SYSTEM label
canonical form: GNSS

GLOBAL--NAVIGATION--SATELLITE--SYSTEM lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Global Navigation Satellite System

Global Navigation Satellite System
type: Form

GNSS
type: Form

GCU
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: GLOBAL--POSITIONING--SYSTEM label
canonical form: GCU

GLOBAL--POSITIONING--SYSTEM lexConcept
type: LexicalConcept
definition: Global Positioning System

Global Positioning System
type: Form

GCU
type: Form

GAD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: GNSS--AUGMENTATION--DISSEMINATION--SYSTEM label
canonical form: GAD

GNSS--AUGMENTATION--DISSEMINATION--SYSTEM lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: GNSS Augmentation Dissemination system

GNSS Augmentation Dissemination system
type: Form

GAD
type: Form

GA-OB
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: GNSS--AUGMENTATION--ON-BOARD label
canonical form: GA-OB

GNSS--AUGMENTATION--ON-BOARD lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: GNSS Augmentation On-Board

GNSS Augmentation On-Board
type: Form

GA-OB
type: Form

GA-TS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: GNSS--AUGMENTATION--TRACKSIDE label
canonical form: GA-TS

GNSS--AUGMENTATION--TRACKSIDE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: GNSS Augmentation TrackSide

GNSS Augmentation TrackSide
type: Form

GA-TS
type: Form

GPSC
type: LexicalEntry
type: Word
canonical form: GPSC
sense: GPSC lexSense

GPSC lexConcept
type: LexicalConcept
definition: Generic Product Safety Case; SPPRAMSS-334 - [EN 50129:2018/AC:2019-04] {comment:100},SPPRAMSS-335 - [EN 50126-2:2017]

GPSC
type: Form

GoA
type: Acronym
type: LexicalEntry
acronym for: GRADE--OF--AUTOMATION label
canonical form: GoA

GRADE--OF--AUTOMATION lexConcept
type: LexicalConcept
definition: GoA - Grade of Automation

Grade of Automation
type: Form

GoA
type: Form

Granularity
type: LexicalEntry
type: Word
canonical form: Granularity
sense: GRANULARITY lexSense

GRANULARITY lexConcept
type: LexicalConcept
definition: The granularity characterises the level of modularity of a system. The more subsystems a system is composed of, the higher its granularity.

Granularity
type: Form

Granularization
type: LexicalEntry
type: Word
canonical form: Granularization
sense: GRANULARIZATION lexSense

GRANULARIZATION lexConcept
type: LexicalConcept
definition: The granularization refers to system engineering activity aiming at defining granularity.

Granularization
type: Form

GSM-R - Global System for Mobile Communications – Railways
type: LexicalEntry
type: MultiwordExpression
canonical form: GSM-R - Global System for Mobile Communications – Railways
sense: GSM-R-----GLOBAL--SYSTEM--FOR--MOBILE--COMMUNICATIONS-----RAILWAYS lexSense

GSM-R-----GLOBAL--SYSTEM--FOR--MOBILE--COMMUNICATIONS-----RAILWAYS lexConcept
type: LexicalConcept
definition: GSM-R - Global System for Mobile Communications – Railways

GSM-R - Global System for Mobile Communications – Railways
type: Form

HHT
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: HANDHELD--TERMINAL label
canonical form: HHT

HANDHELD--TERMINAL lexConcept
type: LexicalConcept
definition: 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

Handheld terminal
type: Form

HHT
type: Form

Hard Key
type: LexicalEntry
type: MultiwordExpression
canonical form: Hard Key
sense: HARD--KEY lexSense

HARD--KEY lexConcept
type: LexicalConcept
definition: Physical key not part of view. This key can also have a text label or symbol.

HARD--KEY lexConcept 2
type: LexicalConcept
definition: Physical key not part of view. This key can also have a text label or symbol.

HARD--KEY lexConcept 3
type: LexicalConcept
definition: Physical key not part of view. This key can also have a text label or symbol.

HARD--KEY lexConcept 4
type: LexicalConcept
definition: Physical key not part of view. This key can also have a text label or symbol.

HARD--KEY lexConcept 5
type: LexicalConcept
definition: Physical key not part of view. This key can also have a text label or symbol.

HARD--KEY lexConcept 6
type: LexicalConcept
definition: Physical key not part of view. This key can also have a text label or symbol.

HARD--KEY lexConcept 7
type: LexicalConcept
definition: Physical key not part of view. This key can also have a text label or symbol.

HARD--KEY lexConcept 8
type: LexicalConcept
definition: Hard Key Physical key not part of view. This key can also have a text label or symbol.

Hard Key
type: Form

I2
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: HARDWARE--ABSTRACTION--INTERFACE label
canonical form: I2

HARDWARE--ABSTRACTION--INTERFACE lexConcept
type: LexicalConcept
definition: 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.

Hardware Abstraction Interface
type: Form

I2
type: Form

HL
type: Acronym
type: LexicalEntry
acronym for: HARDWARE--LAYER label
canonical form: HL

HARDWARE--LAYER lexConcept
type: LexicalConcept
definition: The Hardware Layer contains the actual Physical Computing Elements providing the compute resources to the platform.

Hardware Layer
type: Form

HL
type: Form

HW
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: HARDWARE label
canonical form: HW

HARDWARE lexConcept
type: LexicalConcept
definition: Hardware refers to the physical components of a computer system or electronic device. It encompasses all the tangible parts that can be seen and touched, such as the central processing unit (CPU), memory modules, storage devices (hard drive, solid-state drive), possible input/output devices (e.g. keyboard, mouse, monitor, etc), motherboard, graphics card, sound card, and various other components that make up a computation unit or electronic device. Hardware is responsible for executing and processing instructions and data, providing the necessary functionality for software to run and perform tasks.

Hardware
type: Form

HW
type: Form

Harmonisation
type: LexicalEntry
type: Word
canonical form: Harmonisation
sense: HARMONISATION lexSense

HARMONISATION lexConcept
type: LexicalConcept
definition: Harmonisation includes the options TSI specification (Annex A or Application Guide), Standardisation via ESO, or agreed System Pillar Publication.

Harmonisation
type: Form

HDDI
type: Acronym
type: LexicalEntry
acronym for: HARMONISED--DIAGNOSTIC--DATA--INTERFACE label
canonical form: HDDI

HARMONISED--DIAGNOSTIC--DATA--INTERFACE lexConcept
type: LexicalConcept
definition: The purpose of HDDI is to ensure the compatibility of use-case specific data generated by different systems, suppliers and/or in different European countries to improve railway asset management and togenerate sustainable benefits for all stakeholders. Each UC HDDI specification is generated for the specificuse case. * The harmonisation ensures the comparability of railway asset diagnostic data. * HDDI can be implemented at different levels in the diagnostic data chain depending on the specific use case (UC). The harmonised diagnostic data consists of asset related data: * The measurement data of the parameters of the use case specific railway component or system. * The diagnostic data represent the time-dependent condition of the intended asset component or system. * The specified meta-data needed to generate the diagnostic information. * The specified diagnostic outcome for asset management. * The harmonised diagnostic data interface is a standardised method for how the intended data is provided to the data user.The HDDI-specification must include the definition of the data provider, the data user, as well as the syntax for the data transfer.

Harmonised Diagnostic Data Interface
type: Form

HDDI
type: Form

HERD
type: Acronym
type: LexicalEntry
acronym for: HARMONISED--EUROPEAN--RAILWAY--DIAGNOSTICS label
canonical form: HERD

HARMONISED--EUROPEAN--RAILWAY--DIAGNOSTICS lexConcept
type: LexicalConcept
definition: ERJU System Pillar Task 5: Harmonised European Railway Diagnostics

Harmonised European Railway Diagnostics
type: Form

HERD
type: Form

Harmonization
type: LexicalEntry
type: Word
canonical form: Harmonization
sense: HARMONIZATION lexSense

HARMONIZATION lexConcept
type: LexicalConcept
definition: Act or process to make something consistent or compatible. Harmonizing the railway system can include all kinds of technical systems, operations and processes.

Harmonization
type: Form

Harmonized interchangeable product ("modular" product).
type: LexicalEntry
type: MultiwordExpression
canonical form: Harmonized interchangeable product ("modular" product).
sense: HARMONIZED--INTERCHANGEABLE--PRODUCT-- MODULAR --PRODUCT lexSense

HARMONIZED--INTERCHANGEABLE--PRODUCT-- MODULAR --PRODUCT lexConcept
type: LexicalConcept
definition: A harmonized product is interchangeable, if it implements ALL and ONLY harmonized SPRA interfaces together with the harmonized system behavior, which is only parametrizable, but not customizable in terms of software behavior with propietary customisation features.

Harmonized interchangeable product ("modular" product).
type: Form

Harmonized product
type: LexicalEntry
type: MultiwordExpression
canonical form: Harmonized product
sense: HARMONIZED--PRODUCT lexSense

HARMONIZED--PRODUCT lexConcept
type: LexicalConcept
definition: A product is harmonized only if it adapts all availabe harmonized interfaces of the System Pillar Refernce Architecture (SPRA) on all interface types (system interface, user interface, physical interface) and the correlating system behaviour (=stateful reaction on input interfaces/events on state changes/output interfaces). A harmonized product could have customized additional optional interfaces and system behavior, if the system can be used in the harmonized way without making use of them.

Harmonized product
type: Form

Hazard
type: LexicalEntry
type: Word
canonical form: Hazard
sense: HAZARD lexSense

HAZARD lexConcept
type: LexicalConcept
definition: Condition that could lead to an accident Note 1 to entry: The equivalent definition in [IEC 60050-903:2013, 903-01-02] refers to "harm" instead of "accident". Note 2 to entry: A Hazard sits at the boundary of the system under consideration. [ ERA-REC-116-2015-GUI]

HAZARD lexConcept 2
type: LexicalConcept
definition: Condition that could lead to an accident Note 1 to entry: The equivalent definition in [IEC 60050-903:2013, 903-01-02] refers to "harm" instead of "accident". Note 2 to entry: A Hazard sits at the boundary of the system under consideration. [ ERA-REC-116-2015-GUI]

HAZARD lexConcept 3
type: LexicalConcept
definition: A problemativ situation that can occure with a system.

Hazard
type: Form

HAZOP
type: LexicalEntry
type: Word
canonical form: HAZOP
sense: HAZOP lexSense

HAZOP lexConcept
type: LexicalConcept
definition: A hazard and operability study (HAZOP) is a structured and systematic examination of a complex planned or existing process or operation in order to identify and evaluate problems that may represent risks to personnel or equipment. The intention of performing a HAZOP is to review the design to pick up design and engineering issues that may otherwise not have been found. The technique is based on breaking the overall complex design of the process into a number of simpler sections called 'nodes' which are then individually reviewed. It is carried out by a suitably experienced multi-disciplinary team (HAZOP) during a series of meetings. The HAZOP technique is qualitative, and aims to stimulate the imagination of participants to identify potential hazards and operability problems. Structure and direction are given to the review process by applying standardised guide-word prompts to the review of each node. [SOURCE: Wikipedia Hazard and operability study - Wikipedia]

HAZOP lexConcept 2
type: LexicalConcept
definition: A hazard and operability study (HAZOP) is a structured and systematic examination of a complex planned or existing process or operation in order to identify and evaluate problems that may represent risks to personnel or equipment. The intention of performing a HAZOP is to review the design to pick up design and engineering issues that may otherwise not have been found. The technique is based on breaking the overall complex design of the process into a number of simpler sections called 'nodes' which are then individually reviewed. It is carried out by a suitably experienced multi-disciplinary team (HAZOP) during a series of meetings. The HAZOP technique is qualitative, and aims to stimulate the imagination of participants to identify potential hazards and operability problems. Structure and direction are given to the review process by applying standardised guide-word prompts to the review of each node.

HAZOP
type: Form

Heading.
type: LexicalEntry
type: Word
canonical form: Heading.
sense: HEADING lexSense

HEADING lexConcept
type: LexicalConcept
definition: Chapter title. This is no normal wokitem type, cannot be commented, etc. Is automatically created in documents when a heading is entered.

Heading.
type: Form

Headway Distance
type: LexicalEntry
type: MultiwordExpression
canonical form: Headway Distance
sense: HEADWAY--DISTANCE lexSense

HEADWAY--DISTANCE lexConcept
type: LexicalConcept
definition: Safe distance between two running trains

Headway Distance
type: Form

High level BuildingBlocks
type: LexicalEntry
type: MultiwordExpression
canonical form: High level BuildingBlocks
sense: HIGH--LEVEL--BUILDINGBLOCKS lexSense

HIGH--LEVEL--BUILDINGBLOCKS lexConcept
type: LexicalConcept
definition: Due to the dependency concept the BuildingBlocks can form units of unlimited size. The recursive dependency tree can have any depth. Every level of the dependency tree links to the next level - that allows to assign clear responsibilities for each of the levels. As an example a BuildingBlock "area" might refer to a number of "interlocking interiors" and "filedelements" in its next downstream dependency level. The Top-Level BuildingBlockConfiguration is the root where all dependencies start from.

High level BuildingBlocks
type: Form

HMI Component
type: LexicalEntry
type: MultiwordExpression
canonical form: HMI Component
sense: HMI--COMPONENT lexSense

HMI--COMPONENT lexConcept
type: LexicalConcept
definition: A Secure Component with a human machine interface. Examples of HMI Components are PC Workstation, tablet device, smart phone, device with touch screen,... Exemptions: embedded components without a screen, e.g. with push buttons and LEDs.

HMI Component
type: Form

HMI Element
type: LexicalEntry
type: MultiwordExpression
canonical form: HMI Element
sense: HMI--ELEMENT lexSense

HMI--ELEMENT lexConcept
type: LexicalConcept
definition: An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key...

HMI--ELEMENT lexConcept 2
type: LexicalConcept
definition: An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key...

HMI--ELEMENT lexConcept 3
type: LexicalConcept
definition: An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key...

HMI--ELEMENT lexConcept 4
type: LexicalConcept
definition: An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key...

HMI--ELEMENT lexConcept 5
type: LexicalConcept
definition: An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key...

HMI--ELEMENT lexConcept 6
type: LexicalConcept
definition: An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key...

HMI--ELEMENT lexConcept 7
type: LexicalConcept
definition: An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key...

HMI--ELEMENT lexConcept 8
type: LexicalConcept
definition: HMI Element An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key...

HMI Element
type: Form

HOF Hazard
type: LexicalEntry
type: MultiwordExpression
canonical form: HOF Hazard
sense: HOF--HAZARD lexSense

HOF--HAZARD lexConcept
type: LexicalConcept
definition: Hazard whose cause is related to human and organisational (HOF) factors. These harzards are managed by means of the "HOF Hazard" Work Item.

HOF Hazard
type: Form

HOF
type: LexicalEntry
type: Word
canonical form: HOF
sense: HOF lexSense

HOF lexConcept
type: LexicalConcept
definition: Human and Organisational Factors

HOF lexConcept 2
type: LexicalConcept
definition: Human and Organisational Factors

HOF lexConcept 3
type: LexicalConcept
definition: Human and Organisational Factors

HOF
type: Form

Holder of the vehicle type authorization
type: LexicalEntry
type: MultiwordExpression
canonical form: Holder of the vehicle type authorization
sense: HOLDER--OF--THE--VEHICLE--TYPE--AUTHORIZATION lexSense

HOLDER--OF--THE--VEHICLE--TYPE--AUTHORIZATION lexConcept
type: LexicalConcept
definition: Holder of the vehicle type authorization means the natural or legal person that has applied for and received the vehicle type authorization, or its legal successor

Holder of the vehicle type authorization
type: Form

Homologation
type: LexicalEntry
type: Word
canonical form: Homologation
sense: HOMOLOGATION lexSense

HOMOLOGATION lexConcept
type: LexicalConcept
definition: In the railway context, *homologation* refers to the formal approval process that ensures a railway system, component, or piece of equipment meets all relevant safety, technical, and regulatory standards before it can be put into operation. This process involves rigorous testing, certification, and validation by authorized bodies to confirm that the railway elements, such as trains, signaling systems, and infrastructure, comply with national and international standards. The process typically includes a series of assessments, including safety, interoperability, performance, and environmental impact evaluations, before final approval is granted for commercial use. This term is used as a "generic" term that covers any aspect related to certification, assessment, authorisation, approval, acceptance.

Homologation
type: Form

HBD
type: Acronym
type: LexicalEntry
acronym for: HOT--BOX--DETECTOR label
canonical form: HBD

HOT--BOX--DETECTOR lexConcept
type: LexicalConcept
definition: Hot Box Detector

Hot Box Detector
type: Form

HBD
type: Form

HTTP endpoint
type: LexicalEntry
type: MultiwordExpression
canonical form: HTTP endpoint
sense: HTTP--ENDPOINT lexSense

HTTP--ENDPOINT lexConcept
type: LexicalConcept
definition: The HTTP endpoint is a Secure Component using HTTP communication (client and server).

HTTP endpoint
type: Form

HOF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: HUMAN--AND--ORGANISATIONAL--FACTORS label
canonical form: HOF

HUMAN--AND--ORGANISATIONAL--FACTORS lexConcept
type: LexicalConcept
definition: Human and Organisational Factors (HOF) are at the heart of safety operations and management. They even play a key role in both Operational Safety and Occupational Safety.

Human and Organisational Factors
type: Form

HOF
type: Form

HOF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: HUMAN--AND--ORGANIZATIONAL--FACTORS label
canonical form: HOF

HUMAN--AND--ORGANIZATIONAL--FACTORS lexConcept
type: LexicalConcept
definition: Human and Organizational Factors can lead to application conditions.

Human and Organizational Factors
type: Form

HOF
type: Form

HMI
type: Acronym
type: LexicalEntry
acronym for: HUMAN--MACHINE--INTERFACE label
canonical form: HMI

HUMAN--MACHINE--INTERFACE lexConcept
type: LexicalConcept
definition: Human Machine Interface

HUMAN--MACHINE--INTERFACE lexConcept 2
type: LexicalConcept
definition: Graphical component to interact with a user e.g., by train graph.

HUMAN--MACHINE--INTERFACE lexConcept 3
type: LexicalConcept
definition: The Human Machine Interface is a physical interface permitting an interaction between a human and the system control. The purpose of this interface is to allow effective operation by the human (ie: acknowledgement for a function) permitting to the machine (computer) to adapt simultanously the behaviour of the control command.

Human Machine Interface
type: Form

HMI
type: Form

HMI
type: Form

HSI
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: HUMAN-SYSTEM--INTEGRATION label
canonical form: HSI

HUMAN-SYSTEM--INTEGRATION lexConcept
type: LexicalConcept
definition: 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
type: Form

HSI
type: Form

Hybrid Train Detection
type: LexicalEntry
type: MultiwordExpression
canonical form: Hybrid Train Detection
sense: HYBRID--TRAIN--DETECTION lexSense

HYBRID--TRAIN--DETECTION lexConcept
type: LexicalConcept
definition: Hybrid Train Detection is a type of train detection which uses fixed (pre-configured) virtual blocks for the separation of trains which are able to send train integrity confirmation in the position report, while a limited installation of trackside train detection is used for the separation of trains which are not able to send integrity confirmation, as well as for the handling of degraded situations.

Hybrid Train Detection
type: Form

HTTP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: HYPERTEXT--TRANSFER--PROTOCOL label
canonical form: HTTP

HYPERTEXT--TRANSFER--PROTOCOL lexConcept
type: LexicalConcept
definition: Hypertext Transfer Protocol

Hypertext Transfer Protocol
type: Form

HTTP
type: Form

IAM
type: Acronym
type: LexicalEntry
acronym for: IDENTITY--ACCESS--MANAGEMENT label
canonical form: IAM

IDENTITY--ACCESS--MANAGEMENT lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Identity Access Management

Identity Access Management
type: Form

IAM
type: Form

Identity
type: LexicalEntry
type: Word
canonical form: Identity
sense: IDENTITY lexSense

IDENTITY lexConcept
type: LexicalConcept
definition: An identity acts as an address where algorithms can retrieve detailed information about an object or struct.

Identity
type: Form

Impersonation
type: LexicalEntry
type: Word
canonical form: Impersonation
sense: IMPERSONATION lexSense

IMPERSONATION lexConcept
type: LexicalConcept
definition: Impersonation, in terms of behavior, involves a person or entity imitating or mimicking the actions, mannerisms, or characteristics of another individual or entity. In the context on how this definition is to be understood, a newer system would behave exactly like an older version system of itself, allowing it to interact with older systems/subsystems transparently, by behaving exactly like the older version expected by them. From a software perspective, the different impersonations a system can take could be implemented as independent modules, which would reduce the complexity of each module implementing an specific impersonation, and also limit the side effects of changes or bugs in one module to the others. It could also facilitate the addition of a new version of a system, while still keeping the former version of the system available in a transparent way.

Impersonation
type: Form

Implementation Requirements
type: LexicalEntry
type: MultiwordExpression
canonical form: Implementation Requirements
sense: IMPLEMENTATION--REQUIREMENTS lexSense

IMPLEMENTATION--REQUIREMENTS lexConcept
type: LexicalConcept
definition: define how a system is to be built in terms of specific technology. These may be specific requirements from the customer about a solution that they require or they may be legislative requirements.

Implementation Requirements
type: Form

In the Staff responsible mode (SR) the mission is performed on sight and with ou...
type: LexicalEntry
type: MultiwordExpression
canonical form: In the Staff responsible mode (SR) the mission is performed on sight and with ou...
sense: IN--THE--STAFF--RESPONSIBLE--MODE--SR--THE--MISSION--IS--PERFORMED--ON--SIGHT--AND--WITH--OU lexSense

IN--THE--STAFF--RESPONSIBLE--MODE--SR--THE--MISSION--IS--PERFORMED--ON--SIGHT--AND--WITH--OU lexConcept
type: LexicalConcept
definition: In the Staff responsible mode (SR) the mission is performed on sight and with out a Movement authority (MA). Training info: DMI-Symbol: (image: 1-screenshot-20250930-143742-12.png) The ETCS on board unit observes in SR: * the high speed according due thenational value (in Germany 40 km/h) * if necessary permanently lower speeds (if balises are equipped SR is offered, if * Override + EOA was used * if no valid position of the vehicle could be determined The mission can be upgraded ot OS or FS, if a valid position has been determined.

In the Staff responsible mode (SR) the mission is performed on sight and with ou...
type: Form

In this document, the abbreviations "IM" for Infrastructure manager" and "RU" fo...
type: LexicalEntry
type: MultiwordExpression
canonical form: In this document, the abbreviations "IM" for Infrastructure manager" and "RU" fo...
sense: IN--THIS--DOCUMENT--THE--ABBREVIATIONS-- IM --FOR--INFRASTRUCTURE--MANAGER --AND-- RU --FO lexSense

IN--THIS--DOCUMENT--THE--ABBREVIATIONS-- IM --FOR--INFRASTRUCTURE--MANAGER --AND-- RU --FO lexConcept
type: LexicalConcept
definition: In this document, the abbreviations "IM" for Infrastructure manager" and "RU" for Railway Undertaking are used due to their widespread use in the rail sector. The equivalents terms are "RIM" for Rail Infrastructure Managers" and "ROC" for Railway Operating Company. CMS | Capacity Management System CBO | Common Business Objectives CCS | Command Control Signalling ETMN | European Traffic Management Network RIM | (Rail) Infrastructure Manager IM | Rail Infrastructure Manager ROC, RU | Rail Operating Company, Railway Undertaking TMS | Traffic Management System XS - S - M – L - XL | Extra Small - Small – Medium – Large – Extra Large TCC | IM Traffic Control Center TCR | Temporary Capacity Restriction ETM Network | European Traffic Management Network short – medium – long | Referring to implementation period in sub-chapter “Summary Assessment of Feasibility”

In this document, the abbreviations "IM" for Infrastructure manager" and "RU" fo...
type: Form

Incident Impact Management
type: LexicalEntry
type: MultiwordExpression
canonical form: Incident Impact Management
sense: INCIDENT--IMPACT--MANAGEMENT lexSense

INCIDENT--IMPACT--MANAGEMENT lexConcept
type: LexicalConcept
definition: Managing the recovery from incidents to normal state of operations.

Incident Impact Management
type: Form

Incident
type: LexicalEntry
type: Word
canonical form: Incident
sense: INCIDENT lexSense

INCIDENT lexConcept
type: LexicalConcept
definition: Incident means any occurrence, other than an accident or serious accident, affecting the safety of railway operations

INCIDENT lexConcept 2
type: LexicalConcept
definition: ‘incident’ means any occurrence, other than an accident or serious accident, affecting the safety of railway operations; SPPRAMSS-337 - [Directive (EU) 2016/798]

Incident
type: Form

ISA
type: Acronym
type: LexicalEntry
acronym for: INDEPENDENT--SAFETY--ASSESSOR label
canonical form: ISA

INDEPENDENT--SAFETY--ASSESSOR lexConcept
type: LexicalConcept
definition: The role is defined in "Table G.4 — Role specification for Independent Safety Assessor" of SPPRAMSS-335 - [EN 50126-2:2017]

Independent Safety Assessor
type: Form

ISA
type: Form

Indirect Brake -
type: LexicalEntry
type: MultiwordExpression
canonical form: Indirect Brake -
sense: INDIRECT--BRAKE lexSense

INDIRECT--BRAKE lexConcept
type: LexicalConcept
definition: Indirect Brake -

Indirect Brake -
type: Form

Indirect Track Possession / Occupancy
type: LexicalEntry
type: MultiwordExpression
canonical form: Indirect Track Possession / Occupancy
sense: INDIRECT--TRACK--POSSESSION-- --OCCUPANCY lexSense

INDIRECT--TRACK--POSSESSION-- --OCCUPANCY lexConcept
type: LexicalConcept
definition: Part of the infrastructure that is not directly occupied by a train, but contains a buffer area for example between the train and signal.

Indirect Track Possession / Occupancy
type: Form

Indivisible for deployment
type: LexicalEntry
type: MultiwordExpression
canonical form: Indivisible for deployment
sense: INDIVISIBLE--FOR--DEPLOYMENT lexSense

INDIVISIBLE--FOR--DEPLOYMENT lexConcept
type: LexicalConcept
definition: When a set of CCS features must be included in full for any given deployment (e.g. migration plateau, SP release, migration target etc.).{comment:112}

Indivisible for deployment
type: Form

Information model
type: LexicalEntry
type: MultiwordExpression
canonical form: Information model
sense: INFORMATION--MODEL lexSense

INFORMATION--MODEL lexConcept
type: LexicalConcept
definition: 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.

Information model
type: Form

IRM
type: Acronym
type: LexicalEntry
acronym for: INFORMATION--RIGHTS--MANAGEMENT label
canonical form: IRM

INFORMATION--RIGHTS--MANAGEMENT lexConcept
type: LexicalConcept
definition: Information Rights Management

Information Rights Management
type: Form

IRM
type: Form

Infrastructure Capacity
type: LexicalEntry
type: MultiwordExpression
canonical form: Infrastructure Capacity
sense: INFRASTRUCTURE--CAPACITY lexSense

INFRASTRUCTURE--CAPACITY lexConcept
type: LexicalConcept
definition: Infrastructure capacity means the potential to schedule train paths requested for an element of infrastructure for a certain period

Infrastructure Capacity
type: Form

Infrastructure data
type: LexicalEntry
type: MultiwordExpression
canonical form: Infrastructure data
sense: INFRASTRUCTURE--DATA lexSense

INFRASTRUCTURE--DATA lexConcept
type: LexicalConcept
definition: 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
type: Form

IM
type: Acronym
type: LexicalEntry
acronym for: INFRASTRUCTURE--MANAGER label
canonical form: IM

INFRASTRUCTURE--MANAGER lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: Infrastructure Manager{comment:161}

INFRASTRUCTURE--MANAGER lexConcept 3
type: LexicalConcept
definition: Infrastructure Manager

Infrastructure Manager
type: Form

IM
type: Form

IM
type: Form

Infrastructure
type: LexicalEntry
type: Word
canonical form: Infrastructure
sense: INFRASTRUCTURE lexSense

INFRASTRUCTURE lexConcept
type: LexicalConcept
definition: A section of the railway network (distance on the network between two points)

Infrastructure
type: Form

Initial FS Comp
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: INITIAL--FS--COMPARTMENT label
canonical form: Initial FS Comp

INITIAL--FS--COMPARTMENT lexConcept
type: LexicalConcept
definition: 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.

Initial FS Compartment
type: Form

Initial FS Comp
type: Form

IPSE
type: Acronym
type: LexicalEntry
acronym for: INNOVATION--PILLAR--SYSTEM--EXPERTS label
canonical form: IPSE

INNOVATION--PILLAR--SYSTEM--EXPERTS lexConcept
type: LexicalConcept
definition: Innovation Pillar System Experts

Innovation Pillar System Experts
type: Form

IPSE
type: Form

IP
type: Acronym
type: LexicalEntry
acronym for: INNOVATION--PILLAR label
canonical form: IP

INNOVATION--PILLAR lexConcept
type: LexicalConcept
definition: Innovation Pillar

Innovation Pillar
type: Form

IP
type: Form

Innovative solutions
type: LexicalEntry
type: MultiwordExpression
canonical form: Innovative solutions
sense: INNOVATIVE--SOLUTIONS lexSense

INNOVATIVE--SOLUTIONS lexConcept
type: LexicalConcept
definition: The article 10 of the INFRA TSI shall be taken into account regarding innovative solutions for maintenance, upgrading and renewal of infrastructure.

Innovative solutions
type: Form

INS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: INSTANCE label
canonical form: INS

INSTANCE lexConcept
type: LexicalConcept
definition: An Instance is a specific realisation of any entity.

Instance
type: Form

INS
type: Form

Integration
type: LexicalEntry
type: Word
canonical form: Integration
sense: INTEGRATION lexSense

INTEGRATION lexConcept
type: LexicalConcept
definition: Integration is to combine current and/or new systems with a known behaviour to a larger system with a target behaviour. For any country migrating or upgrading their system(s) ‘integration’ is an important consideration to ensure the whole railway operates in a safe and reliable manner.

Integration
type: Form

Integrity
type: LexicalEntry
type: Word
canonical form: Integrity
sense: INTEGRITY lexSense

INTEGRITY lexConcept
type: LexicalConcept
definition: Integrity: property of accuracy and completeness (source: ISO 27000-2018 )

Integrity
type: Form

Interchangeability
type: LexicalEntry
type: Word
canonical form: Interchangeability
sense: INTERCHANGEABILITY lexSense

INTERCHANGEABILITY lexConcept
type: LexicalConcept
definition: Interchangeability is the ability to replace a subsystem from supplier A by a sub-system from supplier B without affecting other sub-systems or the overall system/subsystem and with a lowest reasonable integration effort{comment:1295} and without any need for recertification. Interchangeability is related also to the physical characteristics of sub-systems.

Interchangeability
type: Form

Interface adaption (in a national product pair)
type: LexicalEntry
type: MultiwordExpression
canonical form: Interface adaption (in a national product pair)
sense: INTERFACE--ADAPTION--IN--A--NATIONAL--PRODUCT--PAIR lexSense

INTERFACE--ADAPTION--IN--A--NATIONAL--PRODUCT--PAIR lexConcept
type: LexicalConcept
definition: An SPP-2228 - Missing cross-reference in a national product describes the development effort to change an existing product interface to a harmonized interface, which normally needs to be done at least on two sides. The SPP-2228 - Missing cross-reference leads to an SPP-2325 - Adapted product.

Interface adaption (in a national product pair)
type: Form

Interface
type: LexicalEntry
type: Word
canonical form: Interface
sense: INTERFACE lexSense

INTERFACE lexConcept
type: LexicalConcept
definition: An interface is the link between different building blocks. Inside a building block there can be only "proprietary interfaces". {comment:1429}With an interface the sub-systems of different suppliers{comment:1296} can be combined.

INTERFACE lexConcept 2
type: LexicalConcept
definition: A shared boundary between two systems or between a system and an actor, that interchange exchange items.

Interface
type: Form

IXL
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: INTERLOCKING label
canonical form: IXL

INTERLOCKING lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: 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
type: Form

IXL
type: Form

Internal Button
type: LexicalEntry
type: MultiwordExpression
canonical form: Internal Button
sense: INTERNAL--BUTTON lexSense

INTERNAL--BUTTON lexConcept
type: LexicalConcept
definition: The Internal Button is a button which is managed directly by MDS.

INTERNAL--BUTTON lexConcept 2
type: LexicalConcept
definition: The Internal Button is a button which is managed directly by MDS.

INTERNAL--BUTTON lexConcept 3
type: LexicalConcept
definition: The Internal Button is a button which is managed directly by TDS.

INTERNAL--BUTTON lexConcept 4
type: LexicalConcept
definition: The Internal Button is a button which is managed directly by TDS.

INTERNAL--BUTTON lexConcept 5
type: LexicalConcept
definition: The Internal Button is a button which is managed directly by TDS.

INTERNAL--BUTTON lexConcept 6
type: LexicalConcept
definition: The Internal Button is a button which is managed directly by TDS.

INTERNAL--BUTTON lexConcept 7
type: LexicalConcept
definition: The Internal Button is a button which is managed directly by TDS.

INTERNAL--BUTTON lexConcept 8
type: LexicalConcept
definition: Internal Button The Internal Button is a button which is managed directly by TDS.

Internal Button
type: Form

Internal Publication
type: LexicalEntry
type: MultiwordExpression
canonical form: Internal Publication
sense: INTERNAL--PUBLICATION lexSense

INTERNAL--PUBLICATION lexConcept
type: LexicalConcept
definition: Any work product that is not required to be submitted in order to complete a process, phase, or project. An input or output of a task that does not cross the process boundaries.

Internal Publication
type: Form

ISPR
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: INTERNAL--SP--RELEASE label
canonical form: ISPR

INTERNAL--SP--RELEASE lexConcept
type: LexicalConcept
definition: Internal SP Releases are internal to EU-RAIL program. These releases are delivered to the Innovation Pillar for the sake of setting up maturity demonstrators inline with the tentative future CCS architectures.

Internal SP Release
type: Form

ISPR
type: Form

UITP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: INTERNATIONAL--ASSOCIATION--OF--PUBLIC--TRANSPORT label
canonical form: UITP

INTERNATIONAL--ASSOCIATION--OF--PUBLIC--TRANSPORT lexConcept
type: LexicalConcept
definition: The International Association of Public Transport

International Association of Public Transport
type: Form

UITP
type: Form

IEC
type: Acronym
type: LexicalEntry
acronym for: INTERNATIONAL--ELECTROTECHNICAL--COMMISSION label
canonical form: IEC

INTERNATIONAL--ELECTROTECHNICAL--COMMISSION lexConcept
type: LexicalConcept
definition: International Electrotechnical Commission

International Electrotechnical Commission
type: Form

IEC
type: Form

ISO
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: INTERNATIONAL--ORGANIZATION--FOR--STANDARDIZATION label
canonical form: ISO

INTERNATIONAL--ORGANIZATION--FOR--STANDARDIZATION lexConcept
type: LexicalConcept
definition: International Organization for Standardization

International Organization for Standardization
type: Form

ISO
type: Form

UIC
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: INTERNATIONAL--UNION--OF--RAILWAYS label
canonical form: UIC

INTERNATIONAL--UNION--OF--RAILWAYS lexConcept
type: LexicalConcept
definition: International union of railways

International union of railways
type: Form

UIC
type: Form

UIP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: INTERNATIONAL--UNION--OF--WAGON--KEEPERS label
canonical form: UIP

INTERNATIONAL--UNION--OF--WAGON--KEEPERS lexConcept
type: LexicalConcept
definition: International Union of Wagon Keepers

International Union of Wagon Keepers
type: Form

UIP
type: Form

IoT
type: Acronym
type: LexicalEntry
acronym for: INTERNET--OF--THINGS label
canonical form: IoT

INTERNET--OF--THINGS lexConcept
type: LexicalConcept
definition: Internet of Things

Internet of Things
type: Form

IoT
type: Form

Interoperability
type: LexicalEntry
type: Word
canonical form: Interoperability
sense: INTEROPERABILITY lexSense

INTEROPERABILITY lexConcept
type: LexicalConcept
definition: Interoperability means the ability to allow the safe and uninterrupted movement of trains that accomplish the specified levels of performance.Reference to the TSI (European Regulation) would be good to understand the importance (double. needs to be deleted)

INTEROPERABILITY lexConcept 2
type: LexicalConcept
definition: Interoperability means the ability to allow the safe and uninterrupted movement of trains that accomplish the specified levels of performance, see [Subset-023] SPT2ARC-1619 and [IOP-Dir 2016/797] SPT2ARC-1617 so that a train is able to run across different Infrastructure Managers (IM) networks, and that an IM network and that an infrastructure network{comment:1394} is able to interact with trains of different Railway Undertakings, using systems/sub-systems from different origins. Interoperability between subsystems is defined to achieve a similar unrestricted safe and uninterrupted interaction between subsystems.

Interoperability
type: Form

IDPS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: INTRUSION--DETECTION--AND--PREVENTION--SYSTEM label
canonical form: IDPS

INTRUSION--DETECTION--AND--PREVENTION--SYSTEM lexConcept
type: LexicalConcept
definition: An Intrusion Detection and Prevention System (IDPS) is a network security solution designed to monitor, detect, and prevent unauthorized access, misuse, or malicious activity on a computer network

Intrusion Detection and Prevention System
type: Form

IDPS
type: Form

Issue.
type: LexicalEntry
type: Word
canonical form: Issue.
sense: ISSUE lexSense

ISSUE lexConcept
type: LexicalConcept
definition: 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.

ISSUE lexConcept 2
type: LexicalConcept
definition: 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.

Issue.
type: Form

JSON-LD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: JAVASCRIPT--OBJECT--NOTATION--+FOR--LINKED--DATA label
canonical form: JSON-LD

JAVASCRIPT--OBJECT--NOTATION--+FOR--LINKED--DATA lexConcept
type: LexicalConcept
definition: JavaScript Object Notation for Linked Data

JavaScript Object Notation for Linked Data
type: Form

JSON-LD
type: Form

JP
type: Acronym
type: LexicalEntry
acronym for: JOURNEY--PROFILE label
canonical form: JP

JOURNEY--PROFILE lexConcept
type: LexicalConcept
definition: JP - Journey Profile

Journey Profile
type: Form

JP
type: Form

JWT
type: Acronym
type: LexicalEntry
acronym for: JSON--WEB--TOKEN label
canonical form: JWT

JSON--WEB--TOKEN lexConcept
type: LexicalConcept
definition: JSON Web Token is an Internet standard for creating data with signature and/or encryption whose payload holds JSON that asserts some number of claims.

JSON Web Token
type: Form

JWT
type: Form

Juridical recorder
type: LexicalEntry
type: MultiwordExpression
canonical form: Juridical recorder
sense: JURIDICAL--RECORDER lexSense

JURIDICAL--RECORDER lexConcept
type: LexicalConcept
definition: collecting and storing juridical data (e.g. {comment:8}JRU data: SUBSET-027, possibly very similar data is also sufficient)

Juridical recorder
type: Form

Keeper
type: LexicalEntry
type: Word
canonical form: Keeper
sense: KEEPER lexSense

KEEPER lexConcept
type: LexicalConcept
definition: Keeper means the natural or legal person that, being the owner of a vehicle or having the right to use it, exploits the vehicle as a means of transport and is registered as such in a vehicle register referred to in Article 47

Keeper
type: Form

Key Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Key Controller
sense: KEY--CONTROLLER lexSense

KEY--CONTROLLER lexConcept
type: LexicalConcept
definition: Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.

KEY--CONTROLLER lexConcept 2
type: LexicalConcept
definition: Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.

KEY--CONTROLLER lexConcept 3
type: LexicalConcept
definition: Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.

KEY--CONTROLLER lexConcept 4
type: LexicalConcept
definition: Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.

KEY--CONTROLLER lexConcept 5
type: LexicalConcept
definition: Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.

KEY--CONTROLLER lexConcept 6
type: LexicalConcept
definition: Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.

KEY--CONTROLLER lexConcept 7
type: LexicalConcept
definition: Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.

KEY--CONTROLLER lexConcept 8
type: LexicalConcept
definition: Key Controller Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.

Key Controller
type: Form

Kinematic data
type: LexicalEntry
type: MultiwordExpression
canonical form: Kinematic data
sense: KINEMATIC--DATA lexSense

KINEMATIC--DATA lexConcept
type: LexicalConcept
definition: Set of data including speed, acceleration, attitude or angular rate of the train.

Kinematic data
type: Form

L&P
type: LexicalEntry
type: MultiwordExpression
canonical form: L&P
sense: L--AND--P lexSense

L--AND--P lexConcept
type: LexicalConcept
definition: LOC & PAS, Locomotive & Passenger TSI

L&P
type: Form

Lateral Key
type: LexicalEntry
type: MultiwordExpression
canonical form: Lateral Key
sense: LATERAL--KEY lexSense

LATERAL--KEY lexConcept
type: LexicalConcept
definition: Hard Key located close to a Display Area allowing soft key technology.

LATERAL--KEY lexConcept 2
type: LexicalConcept
definition: Hard Key located close to a Display Area allowing soft key technology.

LATERAL--KEY lexConcept 3
type: LexicalConcept
definition: Hard Key located close to a Display Area allowing soft key technology.

LATERAL--KEY lexConcept 4
type: LexicalConcept
definition: Hard Key located close to a Display Area allowing soft key technology.

LATERAL--KEY lexConcept 5
type: LexicalConcept
definition: Hard Key located close to a Display Area allowing soft key technology.

LATERAL--KEY lexConcept 6
type: LexicalConcept
definition: Hard Key located close to a Display Area allowing soft key technology.

LATERAL--KEY lexConcept 7
type: LexicalConcept
definition: Hard Key located close to a Display Area allowing soft key technology.

LATERAL--KEY lexConcept 8
type: LexicalConcept
definition: Lateral Key Hard Key located close to a Display Area allowing soft key technology.

Lateral Key
type: Form

Layout Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Layout Controller
sense: LAYOUT--CONTROLLER lexSense

LAYOUT--CONTROLLER lexConcept
type: LexicalConcept
definition: The Layout Controller manages the Layout for an Area.

LAYOUT--CONTROLLER lexConcept 2
type: LexicalConcept
definition: The Layout Controller manages the Layout for an Area.

LAYOUT--CONTROLLER lexConcept 3
type: LexicalConcept
definition: The Layout Controller manages the Layout for an Area.

LAYOUT--CONTROLLER lexConcept 4
type: LexicalConcept
definition: The Layout Controller manages the Layout for an Area.

LAYOUT--CONTROLLER lexConcept 5
type: LexicalConcept
definition: The Layout Controller manages the Layout for an Area.

LAYOUT--CONTROLLER lexConcept 6
type: LexicalConcept
definition: The Layout Controller manages the Layout for an Area.

LAYOUT--CONTROLLER lexConcept 7
type: LexicalConcept
definition: The Layout Controller manages the Layout for an Area.

LAYOUT--CONTROLLER lexConcept 8
type: LexicalConcept
definition: Layout Controller The Layout Controller manages the Layout for an Area.

Layout Controller
type: Form

Layout Element Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Layout Element Controller
sense: LAYOUT--ELEMENT--CONTROLLER lexSense

LAYOUT--ELEMENT--CONTROLLER lexConcept
type: LexicalConcept
definition: The Layout Element Controller manages Layout Elements of a Layout. It knows how to present itself and how to react on events.

LAYOUT--ELEMENT--CONTROLLER lexConcept 2
type: LexicalConcept
definition: The Layout Element Controller manages Layout Elements of a Layout. It knows how to present itself and how to react on events.

LAYOUT--ELEMENT--CONTROLLER lexConcept 3
type: LexicalConcept
definition: The Layout Element Controller manages Layout Elements of a Layout. It knows how to present itself and how to react on events.

LAYOUT--ELEMENT--CONTROLLER lexConcept 4
type: LexicalConcept
definition: The Layout Element Controller manages Layout Elements of a Layout. It knows how to present itself and how to react on events.

LAYOUT--ELEMENT--CONTROLLER lexConcept 5
type: LexicalConcept
definition: The Layout Element Controller manages Layout Elements of a Layout. It knows how to present itself and how to react on events.

LAYOUT--ELEMENT--CONTROLLER lexConcept 6
type: LexicalConcept
definition: 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 lexConcept 7
type: LexicalConcept
definition: The Layout Element Controller manages Layout Elements of a Layout. It knows how to present itself and how to react on events.

LAYOUT--ELEMENT--CONTROLLER lexConcept 8
type: LexicalConcept
definition: Layout Element Controller The Layout Element Controller managesLayout Elements of a Layout. It knows how to present itself and how to react on events.

Layout Element Controller
type: Form

Layout Element
type: LexicalEntry
type: MultiwordExpression
canonical form: Layout Element
sense: LAYOUT--ELEMENT lexSense

LAYOUT--ELEMENT lexConcept
type: LexicalConcept
definition: Every element to be shown on the screen like button, speed gauge, video stream, symbol and text with their characteristics (size, position, type, colour, associated icon, etc.)

LAYOUT--ELEMENT lexConcept 2
type: LexicalConcept
definition: Every element to be shown on the screen like button, speed gauge, video stream, symbol and text with their characteristics (size, position, type, colour, associated icon, etc.)

LAYOUT--ELEMENT lexConcept 3
type: LexicalConcept
definition: Every element to be shown on the screen like button, speed gauge, video stream, symbol and text with their characteristics (size, position, type, colour, associated icon, etc.)

LAYOUT--ELEMENT lexConcept 4
type: LexicalConcept
definition: Every element to be shown on the screen like button, speed gauge, video stream, symbol and text with their characteristics (size, position, type, colour, associated icon, etc.)

LAYOUT--ELEMENT lexConcept 5
type: LexicalConcept
definition: Every element to be shown on the screen like button, speed gauge, video stream, symbol and text with their characteristics (size, position, type, colour, associated icon, etc.)

Layout Element
type: Form

Layout Engine
type: LexicalEntry
type: MultiwordExpression
canonical form: Layout Engine
sense: LAYOUT--ENGINE lexSense

LAYOUT--ENGINE lexConcept
type: LexicalConcept
definition: The Layout Engine is an application and supplier specific piece of software, able to generate any View based on application specific needs.

LAYOUT--ENGINE lexConcept 2
type: LexicalConcept
definition: The Layout Engine is an application and supplier specific piece of software, able to generate any View based on application specific needs.

LAYOUT--ENGINE lexConcept 3
type: LexicalConcept
definition: The Layout Engine is an application and supplier specific piece of software, able to generate any View based on application specific needs.

LAYOUT--ENGINE lexConcept 4
type: LexicalConcept
definition: The Layout Engine is an application and supplier specific piece of software, able to generate any View based on application specific needs.

LAYOUT--ENGINE lexConcept 5
type: LexicalConcept
definition: 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--ENGINE lexConcept 6
type: LexicalConcept
definition: 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 lexConcept 7
type: LexicalConcept
definition: 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--ENGINE lexConcept 8
type: LexicalConcept
definition: 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 Engine
type: Form

Layout
type: LexicalEntry
type: Word
canonical form: Layout
sense: LAYOUT lexSense

LAYOUT lexConcept
type: LexicalConcept
definition: Layout is a list of Layout Elements which is displayed in an area.

LAYOUT lexConcept 2
type: LexicalConcept
definition: Layout is a list of Layout Elements which is displayed in an area.

LAYOUT lexConcept 3
type: LexicalConcept
definition: Layout is a list of Layout Elements which is displayed in an area.

LAYOUT lexConcept 4
type: LexicalConcept
definition: Layout is a list of Layout Elements which is displayed in an area.

LAYOUT lexConcept 5
type: LexicalConcept
definition: Layout is a list of Layout Elements which is displayed in an area.

LAYOUT lexConcept 6
type: LexicalConcept
definition: Layout is a list of Layout Elements which is displayed in an area.

LAYOUT lexConcept 7
type: LexicalConcept
definition: Layout is a list of layout elements which is displayed in an area.

LAYOUT lexConcept 8
type: LexicalConcept
definition: Layout Layout is a list of layout elements which is displayed in an area.

Layout
type: Form

LCDF
type: LexicalEntry
type: Word
canonical form: LCDF
sense: LCDF lexSense

LCDF lexConcept
type: LexicalConcept
definition: LCDF - Last Coupler Detection Function

LCDF lexConcept 2
type: LexicalConcept
definition: - determination of the last one, e-coupler coppled, uncoppled ready or not for coupling, standardize for a SIL2 sensor;

LCDF
type: Form

LCO & PAS
type: LexicalEntry
type: MultiwordExpression
canonical form: LCO & PAS
sense: LCO--AND--PAS lexSense

LCO--AND--PAS lexConcept
type: LexicalConcept
definition: L&P, Locomotive & Passenger TSI

LCO--AND--PAS lexConcept 2
type: LexicalConcept
definition: L&P, Locomotive & Passenger TSI

LCO & PAS
type: Form

Legacy system
type: LexicalEntry
type: MultiwordExpression
canonical form: Legacy system
sense: LEGACY--SYSTEM lexSense

LEGACY--SYSTEM lexConcept
type: LexicalConcept
definition: A legacy system is a system built without using SERA system specifications. It can use Class A or Class B train protection, e.g. interlocking with national light signals or interlocking with national ETCS L2 implementation without SERA operational rules.

Legacy system
type: Form

LoS
type: Acronym
type: LexicalEntry
acronym for: LETTER--OF--SUPPORT label
canonical form: LoS

LETTER--OF--SUPPORT lexConcept
type: LexicalConcept
definition: Letter of Support

Letter of Support
type: Form

LoS
type: Form

LX
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: LEVEL--CROSSING label
canonical form: LX

LEVEL--CROSSING lexConcept
type: LexicalConcept
definition: Any level intersection between a road or passage and a railway, as recognised by the infrastructure manager and open to public or private users. There are different types of Level Crossings. A level crossing can be equipped with a protective system to warn users about approaching trains. Warning devises can be a combination of e.g. lights, bells and barriers.{comment:133}{comment:152}

Level Crossing
type: Form

LX
type: Form

Lexical Glossary
type: LexicalEntry
type: MultiwordExpression
canonical form: Lexical Glossary
sense: LEXICAL--GLOSSARY lexSense

LEXICAL--GLOSSARY lexConcept
type: LexicalConcept
definition: either imported from outside the project or authored inside the project, lexical glossaries are the containers for lexical entiries and abbreviations. A lexical glossary is first consolidated by its glossary author in its own scope, i.e. its definitions shall not be redundant with each other. It is then consolidated towards other glossaries. This glossary is then called SPPR-5441 - Missing cross-reference. Lexical glossaries are the source of the lexical definitons and abbreviations referred to in SPPR-5434 - Refering document.

Lexical Glossary
type: Form

LRU
type: Acronym
type: LexicalEntry
acronym for: LINE--REPLACEABLE--UNIT label
canonical form: LRU

LINE--REPLACEABLE--UNIT lexConcept
type: LexicalConcept
definition: Line Replaceable Unit

Line Replaceable Unit
type: Form

LRU
type: Form

LOC & PAS
type: LexicalEntry
type: MultiwordExpression
canonical form: LOC & PAS
sense: LOC--AND--PAS lexSense

LOC--AND--PAS lexConcept
type: LexicalConcept
definition: Locomotives and Passenger TSI

LOC--AND--PAS lexConcept 2
type: LexicalConcept
definition: Locomotives and Passenger TSI

LOC--AND--PAS lexConcept 3
type: LexicalConcept
definition: Locomotives and Passenger TSI

LOC--AND--PAS lexConcept 4
type: LexicalConcept
definition: Locomotives and Passenger TSI

LOC--AND--PAS lexConcept 5
type: LexicalConcept
definition: Locomotives and Passenger TSI

LOC--AND--PAS lexConcept 6
type: LexicalConcept
definition: Locomotives and Passenger TSI

LOC & PAS
type: Form

LOC-OB - Localisation On-Board
type: LexicalEntry
type: MultiwordExpression
canonical form: LOC-OB - Localisation On-Board
sense: LOC-OB-----LOCALISATION--ON-BOARD lexSense

LOC-OB-----LOCALISATION--ON-BOARD lexConcept
type: LexicalConcept
definition: LOC-OB - Localisation On-Board

LOC-OB - Localisation On-Board
type: Form

Local operation
type: LexicalEntry
type: MultiwordExpression
canonical form: Local operation
sense: LOCAL--OPERATION lexSense

LOCAL--OPERATION lexConcept
type: LexicalConcept
definition: Local operation of a movable element refers to operation physically/onsite done by Field Force not involving Trackside CCS and neither using a centralised panel (TMS) nor a local pannel nor a handheld terminal. The alternative to the local operation would be a "remote" operation from a centralised panel (TMS) or a local pannel or a handheld terminal. Currently the use of local is undestood as a "planned" operation while the use of "manual" would imply an "unplanned" operation.

Local operation
type: Form

Localisation Information
type: LexicalEntry
type: MultiwordExpression
canonical form: Localisation Information
sense: LOCALISATION--INFORMATION lexSense

LOCALISATION--INFORMATION lexConcept
type: LexicalConcept
definition: Set of spatial values referenced to the rail network, and kinematic variables referenced to the train unit, that provide the train front end position of the train in a specific point of the network and its dynamic behaviour from its speed, acceleration, and orientation values.

Localisation Information
type: Form

Localisation
type: LexicalEntry
type: Word
canonical form: Localisation
sense: LOCALISATION lexSense

LOCALISATION lexConcept
type: LexicalConcept
definition: Determines the position of the train within the track network, using for example topological coordinates.

Localisation
type: Form

Location Marker
type: LexicalEntry
type: MultiwordExpression
canonical form: Location Marker
sense: LOCATION--MARKER lexSense

LOCATION--MARKER lexConcept
type: LexicalConcept
definition: A Harmonised trackside ETCS marker board defined in EN 16494/2015 ( 2 ) is used to identify a potential EOA, e.g. the end of a block section. ERTMS User Group defines a ETCS location Marker: * To be used to unambiguously identify an EOA which does not protect a safety-critical location. It is up to IM to decide whether an ETCS Location Marker can be used instead of an ETCS Stop Marker where no safety critical point needs to be protected. * To be used to identify specific locations on the track where the train shall stop when running without MA if the driver has received specific instruction from the signaller. * To be used to mark the location up to which the driver needs to confirm that the line is clear (e.g. for TAF function) To be used to mark the location up to which the driver has to drive under his/her responsibility before a possible MA in FS/OS is received. (image: 9-screenshot-20251001-151744-6.png)

Location Marker
type: Form

Logging
type: LexicalEntry
type: Word
canonical form: Logging
sense: LOGGING lexSense

LOGGING lexConcept
type: LexicalConcept
definition: is the activity of keeping a list of events that occur in a computer system, events such as problems, errors, or just information on current operations. [https://en.wikipedia.org/wiki/Logging_(computing)]

Logging
type: Form

Logical Component
type: LexicalEntry
type: MultiwordExpression
canonical form: Logical Component
sense: LOGICAL--COMPONENT lexSense

LOGICAL--COMPONENT lexConcept
type: LexicalConcept
definition: An abstraction of a system that performs the system functions without imposing restrictions on implementation. Logical components are also only connected via FIS and not via FFFIS interfaces.

Logical Component
type: Form

Logical Function
type: LexicalEntry
type: MultiwordExpression
canonical form: Logical Function
sense: LOGICAL--FUNCTION lexSense

LOGICAL--FUNCTION lexConcept
type: LexicalConcept
definition: A SPPR-2598 - Function derived during logical architecture by splitting a system function.

Logical Function
type: Form

logistic delay
type: LexicalEntry
type: MultiwordExpression
canonical form: logistic delay
sense: LOGISTIC--DELAY lexSense

LOGISTIC--DELAY lexConcept
type: LexicalConcept
definition: delay, excluding administrative delay, incurred for the provision of resources needed for a maintenance action to proceed or continue. [SOURCE: IEC 60050-192:2015, 192-07-13]

logistic delay
type: Form

Loudspeaker
type: LexicalEntry
type: Word
canonical form: Loudspeaker
sense: LOUDSPEAKER lexSense

LOUDSPEAKER lexConcept
type: LexicalConcept
definition: Device that converts an electrical audio signal into a corresponding sound.

LOUDSPEAKER lexConcept 2
type: LexicalConcept
definition: Device that converts an electrical audio signal into a corresponding sound.

LOUDSPEAKER lexConcept 3
type: LexicalConcept
definition: Device that converts an electrical audio signal into a corresponding sound.

LOUDSPEAKER lexConcept 4
type: LexicalConcept
definition: Device that converts an electrical audio signal into a corresponding sound.

LOUDSPEAKER lexConcept 5
type: LexicalConcept
definition: Device that converts an electrical audio signal into a corresponding sound.

LOUDSPEAKER lexConcept 6
type: LexicalConcept
definition: Device that converts an electrical audio signal into a corresponding sound.

LOUDSPEAKER lexConcept 7
type: LexicalConcept
definition: Device that converts an electrical audio signal into a corresponding sound.

LOUDSPEAKER lexConcept 8
type: LexicalConcept
definition: Loudspeaker Device that converts an electrical audio signal into a corresponding sound.

Loudspeaker
type: Form

LR
type: LexicalEntry
type: Word
canonical form: LR
sense: LR lexSense

LR lexConcept
type: LexicalConcept
definition: LR is a collective term for L2 and L3 in the new CCS TSI 2022 (not yet officially issued) B4 R1.

LR
type: Form

LTM - Loop Transmission Module
type: LexicalEntry
type: MultiwordExpression
canonical form: LTM - Loop Transmission Module
sense: LTM-----LOOP--TRANSMISSION--MODULE lexSense

LTM-----LOOP--TRANSMISSION--MODULE lexConcept
type: LexicalConcept
definition: LTM - Loop Transmission Module

LTM - Loop Transmission Module
type: Form

LWG - Localisation Working Group
type: LexicalEntry
type: MultiwordExpression
canonical form: LWG - Localisation Working Group
sense: LWG-----LOCALISATION--WORKING--GROUP lexSense

LWG-----LOCALISATION--WORKING--GROUP lexConcept
type: LexicalConcept
definition: LWG - Localisation Working Group

LWG - Localisation Working Group
type: Form

MooN
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: M-OUT-OF--N label
canonical form: MooN

M-OUT-OF--N lexConcept
type: LexicalConcept
definition: 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.

M-out-of N
type: Form

MooN
type: Form

MACMT
type: LexicalEntry
type: Word
canonical form: MACMT
sense: MACMT lexSense

MACMT lexConcept
type: LexicalConcept
definition: mean active corrective maintenance time expectation of the active corrective maintenance time [SOURCE: IEC 60050-192:2015, 192-07-22]

MACMT
type: Form

MAD
type: LexicalEntry
type: Word
canonical form: MAD
sense: MAD lexSense

MAD lexConcept
type: LexicalConcept
definition: mean administrative delay. Expectation of the administrative delay. [SOURCE: IEC 60050-192:2015,192-07-26]

MAD
type: Form

maintainability, <of an item>
type: LexicalEntry
type: MultiwordExpression
canonical form: maintainability, <of an item>
sense: MAINTAINABILITY--<OF--AN--ITEM> lexSense

MAINTAINABILITY--<OF--AN--ITEM> lexConcept
type: LexicalConcept
definition: Ability to be retained in, or restored to, a state to perform as required, under given conditions of use and maintenance Note 1 to entry: Given conditions would include aspects that affect maintainability, such as: location for maintenance, accessibility, maintenance procedures and maintenance resources. [SOURCE: IEC 60050-192:2015, 192-01-27] Source: SPPRAMSS-349 - [EN 50126-1:2017]

maintainability, <of an item>
type: Form

Maintainability
type: LexicalEntry
type: Word
canonical form: Maintainability
sense: MAINTAINABILITY lexSense

MAINTAINABILITY lexConcept
type: LexicalConcept
definition: Ability to be retained in, or restored to, a state to perform as required, under given conditions of use and maintenance [EN50126], see SPT2ARC-1616, see also SPPRAMSS-3540 - maintainability, <of an item> .{comment:1297}

Maintainability
type: Form

Maintainer
type: LexicalEntry
type: Word
canonical form: Maintainer
sense: MAINTAINER lexSense

MAINTAINER lexConcept
type: LexicalConcept
definition: The Maintainer is an operational actor. He is in charge of maintaining a system in a operational state. To do so, he can monitor, diagnose, repair, update and configure the system. The main tasks of this actor are: configure displays in the cab, diagnose issues of a system, repair a system and update a system.

MAINTAINER lexConcept 2
type: LexicalConcept
definition: The Maintainer is an operational actor. He is in charge of maintaining a system in a operational state. To do so, he can monitor, diagnose, repair, update and configure the system. The main tasks of this actor are: configure displays in the cab, diagnose issues of a system, repair a system and update a system.

Maintainer
type: Form

MO
type: Acronym
type: LexicalEntry
acronym for: MAINTENANCE--OPERATOR label
canonical form: MO

MAINTENANCE--OPERATOR lexConcept
type: LexicalConcept
definition: Maintenance Operator is the person in charge of applying the maintenance documents containing the maintenance constraints to repare the train if a default occurs, detected in commercial service, during tests or during train preparation. It role is also to apply preventive maintenance to improve the commercial service.

Maintenance Operator
type: Form

MO
type: Form

MITM
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: MAN-IN-THE-MIDDLE--ATTACK label
canonical form: MITM

MAN-IN-THE-MIDDLE--ATTACK lexConcept
type: LexicalConcept
definition: Man-in-the-middle attack

Man-in-the-middle attack
type: Form

MITM
type: Form

Management by traceability (KANBAN based)
type: LexicalEntry
type: MultiwordExpression
canonical form: Management by traceability (KANBAN based)
sense: MANAGEMENT--BY--TRACEABILITY--KANBAN--BASED lexSense

MANAGEMENT--BY--TRACEABILITY--KANBAN--BASED lexConcept
type: LexicalConcept
definition: A trace (nodes/work items and their links) is a graph that works out one issue (e.g. one requirement) in the most efficient, complete and fast way, down to its operational and system implementation (image: 1-image10.png)

Management by traceability (KANBAN based)
type: Form

MC
type: Acronym
type: LexicalEntry
acronym for: MANAGEMENT--COMPARTMENT label
canonical form: MC

MANAGEMENT--COMPARTMENT lexConcept
type: LexicalConcept
definition: The management compartment provides the deployment, configuration and monitoring services through the standardised interfaces. The details will be specified in the future documents.

Management Compartment
type: Form

MC
type: Form

Manual Route Setting
type: LexicalEntry
type: MultiwordExpression
canonical form: Manual Route Setting
sense: MANUAL--ROUTE--SETTING lexSense

MANUAL--ROUTE--SETTING lexConcept
type: LexicalConcept
definition: 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
type: Form

Manufacturer
type: LexicalEntry
type: Word
canonical form: Manufacturer
sense: MANUFACTURER lexSense

MANUFACTURER lexConcept
type: LexicalConcept
definition: The company or organization creating a component, product or system.

Manufacturer
type: Form

Master Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Master Data
sense: MASTER--DATA lexSense

MASTER--DATA lexConcept
type: LexicalConcept
definition: Master data represents "data about the business entities that provide context for business transactions".

Master Data
type: Form

MPE
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: MAXIMUM--PERMISSIBLE--MEASUREMENT--ERROR label
canonical form: MPE

MAXIMUM--PERMISSIBLE--MEASUREMENT--ERROR lexConcept
type: LexicalConcept
definition: Maximum Permissible Measurement Error

Maximum Permissible Measurement Error
type: Form

MPE
type: Form

Maximum Stopping Time
type: LexicalEntry
type: MultiwordExpression
canonical form: Maximum Stopping Time
sense: MAXIMUM--STOPPING--TIME lexSense

MAXIMUM--STOPPING--TIME lexConcept
type: LexicalConcept
definition: Maximum allowed time for a train to wait on the platform according to the defined business rules

Maximum Stopping Time
type: Form

Maximum Waiting Time
type: LexicalEntry
type: MultiwordExpression
canonical form: Maximum Waiting Time
sense: MAXIMUM--WAITING--TIME lexSense

MAXIMUM--WAITING--TIME lexConcept
type: LexicalConcept
definition: The maximum time a train can wait for another train to arrive in order to take the passengers aboard

Maximum Waiting Time
type: Form

MBSE - Model-based System Engineering
type: LexicalEntry
type: MultiwordExpression
canonical form: MBSE - Model-based System Engineering
sense: MBSE-----MODEL-BASED--SYSTEM--ENGINEERING lexSense

MBSE-----MODEL-BASED--SYSTEM--ENGINEERING lexConcept
type: LexicalConcept
definition: MBSE - Model-based System Engineering

MBSE - Model-based System Engineering
type: Form

MDBF
type: LexicalEntry
type: Word
canonical form: MDBF
sense: MDBF lexSense

MDBF lexConcept
type: LexicalConcept
definition: Mean Distance Between Failures [SOURCE: Wikipedia Mean Distance Between Failure – Wikipedia]

MDBF
type: Form

MDBSF
type: LexicalEntry
type: Word
canonical form: MDBSF
sense: MDBSF lexSense

MDBSF lexConcept
type: LexicalConcept
definition: Mean Distance Between Service Failures [SOURCE: Wikipedia Mean Distance Between Failure – Wikipedia]

MDBSF
type: Form

MDCM - Multi-Dimensional Configuration Management
type: LexicalEntry
type: MultiwordExpression
canonical form: MDCM - Multi-Dimensional Configuration Management
sense: MDCM-----MULTI-DIMENSIONAL--CONFIGURATION--MANAGEMENT lexSense

MDCM-----MULTI-DIMENSIONAL--CONFIGURATION--MANAGEMENT lexConcept
type: LexicalConcept
definition: MDCM - Multi-Dimensional Configuration Management

MDCM - Multi-Dimensional Configuration Management
type: Form

MDS - Multi Display System; alternative naming for Train Display System, not yet...
type: LexicalEntry
type: MultiwordExpression
canonical form: MDS - Multi Display System; alternative naming for Train Display System, not yet...
sense: MDS-----MULTI--DISPLAY--SYSTEM--ALTERNATIVE--NAMING--FOR--TRAIN--DISPLAY--SYSTEM--NOT--YET lexSense

MDS-----MULTI--DISPLAY--SYSTEM--ALTERNATIVE--NAMING--FOR--TRAIN--DISPLAY--SYSTEM--NOT--YET lexConcept
type: LexicalConcept
definition: MDS - Multi Display System; alternative naming for Train Display System, not yet in current architecture references.

MDS-----MULTI--DISPLAY--SYSTEM--ALTERNATIVE--NAMING--FOR--TRAIN--DISPLAY--SYSTEM--NOT--YET lexConcept 2
type: LexicalConcept
definition: MDS - Multi Display System; alternative naming for Train Display System, not yet in current architecture references.

MDS-----MULTI--DISPLAY--SYSTEM--ALTERNATIVE--NAMING--FOR--TRAIN--DISPLAY--SYSTEM--NOT--YET lexConcept 3
type: LexicalConcept
definition: MDS - Multi Display System; alternative naming for Train Display System, not yet in current architecture references.

MDS-----MULTI--DISPLAY--SYSTEM--ALTERNATIVE--NAMING--FOR--TRAIN--DISPLAY--SYSTEM--NOT--YET lexConcept 4
type: LexicalConcept
definition: MDS - Multi Display System; alternative naming for Train Display System, not yet in current architecture references.

MDS-----MULTI--DISPLAY--SYSTEM--ALTERNATIVE--NAMING--FOR--TRAIN--DISPLAY--SYSTEM--NOT--YET lexConcept 5
type: LexicalConcept
definition: MDS - Multi Display System; alternative naming for Train Display System, not yet in current architecture references.

MDS-----MULTI--DISPLAY--SYSTEM--ALTERNATIVE--NAMING--FOR--TRAIN--DISPLAY--SYSTEM--NOT--YET lexConcept 6
type: LexicalConcept
definition: MDS - Multi Display System; alternative naming for Train Display System, not yet in current architecture references.

MDS - Multi Display System; alternative naming for Train Display System, not yet...
type: Form

MTBF
type: Acronym
type: LexicalEntry
acronym for: MEAN--TIME--BETWEEN--FAILURE label
canonical form: MTBF

MEAN--TIME--BETWEEN--FAILURE lexConcept
type: LexicalConcept
definition: Mean time between failure

Mean time between failure
type: Form

MTBF
type: Form

MD5
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: MESSAGE--DIGEST--METHOD--5 label
canonical form: MD5

MESSAGE--DIGEST--METHOD--5 lexConcept
type: LexicalConcept
definition: Message Digest Method 5

Message Digest Method 5
type: Form

MD5
type: Form

Methodology
type: LexicalEntry
type: Word
canonical form: Methodology
sense: METHODOLOGY lexSense

METHODOLOGY lexConcept
type: LexicalConcept
definition: A collection of related processes, methods, and tools.{comment:408}

Methodology
type: Form

Method
type: LexicalEntry
type: Word
canonical form: Method
sense: METHOD lexSense

METHOD lexConcept
type: LexicalConcept
definition: A technique for performing a task. Method is a grouping of guidance, modelling{comment:72} language, rules, techniques and patterns. Different methods may be available for the same task. It defines the “HOW” of each task. (In this context, the words “method,” “technique,” “practice,” and “procedure” are often used interchangeably.) At any level, process tasks are performed using methods. {comment:407}

Method
type: Form

MFDT
type: LexicalEntry
type: Word
canonical form: MFDT
sense: MFDT lexSense

MFDT lexConcept
type: LexicalConcept
definition: mean fault detection time [SOURCE: SPPRAMSS-3539 - [EN 61703: 2016]]

MFDT
type: Form

Microphone Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Microphone Controller
sense: MICROPHONE--CONTROLLER lexSense

MICROPHONE--CONTROLLER lexConcept
type: LexicalConcept
definition: The Microphone Controller manages states and signals of Microphone.

MICROPHONE--CONTROLLER lexConcept 2
type: LexicalConcept
definition: The Microphone Controller manages states and signals of Microphone.

MICROPHONE--CONTROLLER lexConcept 3
type: LexicalConcept
definition: The Microphone Controller manages states and signals of Microphone.

MICROPHONE--CONTROLLER lexConcept 4
type: LexicalConcept
definition: The Microphone Controller manages states and signals of Microphone.

MICROPHONE--CONTROLLER lexConcept 5
type: LexicalConcept
definition: The Microphone Controller manages states and signals of Microphone.

MICROPHONE--CONTROLLER lexConcept 6
type: LexicalConcept
definition: The Microphone Controller manages states and signals of Microphone.

MICROPHONE--CONTROLLER lexConcept 7
type: LexicalConcept
definition: The Microphone Controller manages states and signals of Microphone.

MICROPHONE--CONTROLLER lexConcept 8
type: LexicalConcept
definition: Microphone Controller The Microphone Controller manages states and signals of Microphone.

Microphone Controller
type: Form

Microphone
type: LexicalEntry
type: Word
canonical form: Microphone
sense: MICROPHONE lexSense

MICROPHONE lexConcept
type: LexicalConcept
definition: Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker.

MICROPHONE lexConcept 2
type: LexicalConcept
definition: Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker.

MICROPHONE lexConcept 3
type: LexicalConcept
definition: Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker.

MICROPHONE lexConcept 4
type: LexicalConcept
definition: Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker.

MICROPHONE lexConcept 5
type: LexicalConcept
definition: Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker.

MICROPHONE lexConcept 6
type: LexicalConcept
definition: Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker.

MICROPHONE lexConcept 7
type: LexicalConcept
definition: Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker.

MICROPHONE lexConcept 8
type: LexicalConcept
definition: Microphone Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker.

Microphone
type: Form

MS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: MICROSERVICES label
canonical form: MS

MICROSERVICES lexConcept
type: LexicalConcept
definition: Microservices

Microservices
type: Form

MS
type: Form

MID - Mission Data
type: LexicalEntry
type: MultiwordExpression
canonical form: MID - Mission Data
sense: MID-----MISSION--DATA lexSense

MID-----MISSION--DATA lexConcept
type: LexicalConcept
definition: MID - Mission Data

MID - Mission Data
type: Form

Migration Plateau
type: LexicalEntry
type: MultiwordExpression
canonical form: Migration Plateau
sense: MIGRATION--PLATEAU lexSense

MIGRATION--PLATEAU lexConcept
type: LexicalConcept
definition: A Migration Plateau is a plateau used as target for a migration process.{comment:11}{comment:13}

Migration Plateau
type: Form

Migration Strategies
type: LexicalEntry
type: MultiwordExpression
canonical form: Migration Strategies
sense: MIGRATION--STRATEGIES lexSense

MIGRATION--STRATEGIES lexConcept
type: LexicalConcept
definition: The typical expected international timing of the harmonisation phase from international perspective is, that there will be early providers/early birds, and late providers/late birds. Since the reference architecture consists of different systems, the railways can also apply different migration strategies to different systems (image: 1-diagram_20240626-1851.56163.mxg.svg)

Migration Strategies
type: Form

Migration
type: LexicalEntry
type: Word
canonical form: Migration
sense: MIGRATION lexSense

MIGRATION lexConcept
type: LexicalConcept
definition: Migration is the national or company specific process of converting existing CCS/TMS systems including operational processes to corresponding systems and processes of the harmonized System Pillar Reference Architecture (SPRA).

MIGRATION lexConcept 2
type: LexicalConcept
definition: Migration is the process or act of migrating (move from one part of something to another). In the context of CCS and TMS, migrating is the process of changing from the existing national CCS and TMS systems, currently in use in different European countries or on different infrastructures and moving to the target CCS and TMS architecture with Harmonised Operating Processes.

Migration
type: Form

Milestone SP Release
type: LexicalEntry
type: MultiwordExpression
canonical form: Milestone SP Release
sense: MILESTONE--SP--RELEASE lexSense

MILESTONE--SP--RELEASE lexConcept
type: LexicalConcept
definition: Milestone{comment:293} releases are local to the domain or working group responsible for creating the document and does not need the approval of the configuration manager.{comment:292} The Lead Configuration manager should be informed. These can be interpreted as incremental changes to major releases. Each incremental baseline could be the introduction, update or removal of a feature or section of a document or model. Baselines are “minor” baselines (ex 2.1, 2.2...) .{comment:294}{comment:408} Milestone SP Releases are often created specifically for review and auditing purposes. They serve as evidence of adherence to System Pillar practices and are created according to local and global task and project milestones.

Milestone SP Release
type: Form

Minimum Circulation Time
type: LexicalEntry
type: MultiwordExpression
canonical form: Minimum Circulation Time
sense: MINIMUM--CIRCULATION--TIME lexSense

MINIMUM--CIRCULATION--TIME lexConcept
type: LexicalConcept
definition: Time taken to end the arrived journey, change crew, turn around, set the information of the new journey, start a new journey for the arrived train

Minimum Circulation Time
type: Form

MIN_DWELL_TIME
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: MINIMUM--DWELL--TIME label
canonical form: MIN_DWELL_TIME

MINIMUM--DWELL--TIME lexConcept
type: LexicalConcept
definition: Minimum allowed value of dwell time, defined for each Stopping Point included in the Journey Profile, to be considered by the ATO-OB before departure. The minimum dwell time is applied during normal or degraded operation to aid service recovery.

Minimum dwell time
type: Form

MIN_DWELL_TIME
type: Form

Minimum Stopping Time
type: LexicalEntry
type: MultiwordExpression
canonical form: Minimum Stopping Time
sense: MINIMUM--STOPPING--TIME lexSense

MINIMUM--STOPPING--TIME lexConcept
type: LexicalConcept
definition: Minimum allowed time for a train to wait on the platform according to the defined business rules

Minimum Stopping Time
type: Form

MOT
type: Acronym
type: LexicalEntry
acronym for: MINISTRY--OF--TRANSPORTATION label
canonical form: MOT

MINISTRY--OF--TRANSPORTATION lexConcept
type: LexicalConcept
definition: Ministry of Transportation

Ministry of Transportation
type: Form

MOT
type: Form

Mission - The mission is a set of tasks defined by the RU to be performed by a D...
type: LexicalEntry
type: MultiwordExpression
canonical form: Mission - The mission is a set of tasks defined by the RU to be performed by a D...
sense: MISSION-----THE--MISSION--IS--A--SET--OF--TASKS--DEFINED--BY--THE--RU--TO--BE--PERFORMED--BY--A--D lexSense

MISSION-----THE--MISSION--IS--A--SET--OF--TASKS--DEFINED--BY--THE--RU--TO--BE--PERFORMED--BY--A--D lexConcept
type: LexicalConcept
definition: Mission - The mission is a set of tasks defined by the RU to be performed by a Driver or a Consist. A Mission can be dedicated to a Driver or a Consist.

Mission - The mission is a set of tasks defined by the RU to be performed by a D...
type: Form

Mission Assignment
type: LexicalEntry
type: MultiwordExpression
canonical form: Mission Assignment
sense: MISSION--ASSIGNMENT lexSense

MISSION--ASSIGNMENT lexConcept
type: LexicalConcept
definition: SPT2OD-4976 - Missing cross-reference refers to the portion of a SPT2OD-4965 - Missing cross-reference SPT2OD-4977 - Missing cross-reference which is assigned to a SPT2OD-4967 - Missing cross-reference

Mission Assignment
type: Form

MCC
type: Acronym
type: LexicalEntry
acronym for: MISSION--CONTROL--CENTRE label
canonical form: MCC

MISSION--CONTROL--CENTRE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Mission Control Centre

Mission Control Centre
type: Form

MCC
type: Form

MCX
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: MISSION--CRITICAL--SERVICES label
canonical form: MCX

MISSION--CRITICAL--SERVICES lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Mission Critical Services

Mission Critical Services
type: Form

MCX
type: Form

Mission Profile - The Mission Profile is the packet containing the Mission
type: LexicalEntry
type: MultiwordExpression
canonical form: Mission Profile - The Mission Profile is the packet containing the Mission
sense: MISSION--PROFILE-----THE--MISSION--PROFILE--IS--THE--PACKET--CONTAINING--THE--MISSION lexSense

MISSION--PROFILE-----THE--MISSION--PROFILE--IS--THE--PACKET--CONTAINING--THE--MISSION lexConcept
type: LexicalConcept
definition: Mission Profile - The Mission Profile is the packet containing the Mission

Mission Profile - The Mission Profile is the packet containing the Mission
type: Form

MLD
type: LexicalEntry
type: Word
canonical form: MLD
sense: MLD lexSense

MLD lexConcept
type: LexicalConcept
definition: mean logistic delay. Expectation of the logistic delay. [SOURCE: IEC 60050-192:2015,192-07-27]

MLD
type: Form

MBSE
type: Acronym
type: LexicalEntry
acronym for: MODEL--BASED--SYSTEM--ENGINEERING label
canonical form: MBSE

MODEL--BASED--SYSTEM--ENGINEERING lexConcept
type: LexicalConcept
definition: Model based System Engineering

Model based System Engineering
type: Form

MBSE
type: Form

Modularity
type: LexicalEntry
type: Word
canonical form: Modularity
sense: MODULARITY lexSense

MODULARITY lexConcept
type: LexicalConcept
definition: The target of modularity means, that only harmonized interchangeable products should be developed.

MODULARITY lexConcept 2
type: LexicalConcept
definition: Modularity is used in this document as a general term for partinioning{comment:1395} a system/sub-system/module in sub-systems/modules.

MODULARITY lexConcept 3
type: LexicalConcept
definition: The property of a system being composed of a coherent whole of single, independent building blocks or modules.

Modularity
type: Form

Monitoring data
type: LexicalEntry
type: MultiwordExpression
canonical form: Monitoring data
sense: MONITORING--DATA lexSense

MONITORING--DATA lexConcept
type: LexicalConcept
definition: The entity in charge of maintenance shall, either directly or via the keeper provide information to the railway undertakings and infrastructure managers operating the vehicles, keepers, manufacturers, holders of vehicles authorizations and holders of the type authorization of vehicles, subsystems or components, as most appropriate and shall in particular, inform them of exceptional maintenance findings beyond wear and tear.

Monitoring data
type: Form

Monitoring
type: LexicalEntry
type: Word
canonical form: Monitoring
sense: MONITORING lexSense

MONITORING lexConcept
type: LexicalConcept
definition: continuous supervision of the system condition for diagnostic or prognostic purposes.

Monitoring
type: Form

Movable element detection / detected
type: LexicalEntry
type: MultiwordExpression
canonical form: Movable element detection / detected
sense: MOVABLE--ELEMENT--DETECTION-- --DETECTED lexSense

MOVABLE--ELEMENT--DETECTION-- --DETECTED lexConcept
type: LexicalConcept
definition: Refers to the position of a movable trackside element (see SPP-26712 - Movable trackside element) verified/confirmed by the Trackside CCS (Interlocking). For example, points/derailers can be detected right/left (direct or diverging) and Level Crossings can be detected "closed" (protected) or "open" (non-protected / with restrictions).{comment:151}

Movable element detection / detected
type: Form

Movable elements are:
type: LexicalEntry
type: MultiwordExpression
canonical form: Movable elements are:
sense: MOVABLE--ELEMENTS--ARE lexSense

MOVABLE--ELEMENTS--ARE lexConcept
type: LexicalConcept
definition: Movable elements are: * points, derailers and crossings * movable bridges * railway turntables and transfer table

Movable elements are:
type: Form

Movable trackside element
type: LexicalEntry
type: MultiwordExpression
canonical form: Movable trackside element
sense: MOVABLE--TRACKSIDE--ELEMENT lexSense

MOVABLE--TRACKSIDE--ELEMENT lexConcept
type: LexicalConcept
definition: Refers to points, derailers/catch points, LXs, bascule bridges, etc that can be operated to a specific position/direction normally between 2 possibilities. Position/direction refers to for example left/right in case of points.{comment:148}

Movable trackside element
type: Form

Movement Permission Extent
type: LexicalEntry
type: MultiwordExpression
canonical form: Movement Permission Extent
sense: MOVEMENT--PERMISSION--EXTENT lexSense

MOVEMENT--PERMISSION--EXTENT lexConcept
type: LexicalConcept
definition: A Movement Permission Extent is a linear contiguous stretch of track that is reserved for the movement of a train. The Movement Permission Extent and the available Risk Buffer are translated to an authorisation (e.g. Movement Authority) according to the /ETCS/ - SUBSET-026 that is transmitted to the train. The Movement Permission Extent is part of the Movement Permission.

Movement Permission Extent
type: Form

MP
type: Acronym
type: LexicalEntry
acronym for: MOVEMENT--PERMISSION label
canonical form: MP

MOVEMENT--PERMISSION lexConcept
type: LexicalConcept
definition: 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 Permission
type: Form

MP
type: Form

ETCS L2MB
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: MOVING--BLOCK label
canonical form: ETCS L2MB

MB
type: Acronym
type: LexicalEntry
acronym for: MOVING--BLOCK label
canonical form: MB

MOVING--BLOCK lexConcept
type: LexicalConcept
definition: Moving block is a concept where Movement Authorities can end at any location on the track. The Safe Train Extent of each train moves with that train based on its reported position and train integrity status and is not constrained to fixed block locations.

MOVING--BLOCK lexConcept 2
type: LexicalConcept
definition: The term moving block is part of the ETCS Level 2 Moving Block Principle, which is a signalling concept placing emphasis on a largely independent signalling from the physical infrastructure. A moving block is defined by a block bounded by the confirmed rear end and the confirmed rear end of the preceding train (case 1, Figure 1) or, if closer, the beginning of the next fixed block (case 2, Figure 2). Such fixed blocks are delimited by TTDs e.g. around points and may for efficiency reasons still be used on ETCS L2MB lines. (image: 2-Def_MovingBlock1.png) Figure {caption:Figure} Case 1 Definition of Moving Block Figure {caption:Figure} Case 2 Definition of Moving Block (incl. TTDs)) The confirmed rear end of the preceding train is what releases the track behind it and in most cases delimits the moving block. It is established from the safe train length, represented by the distance between the estimated train front end position and the min safe rear end of the train [SUBSET-026 Baseline 4], if derived from a train position report with confirmed train integrity.

MOVING--BLOCK lexConcept 3
type: LexicalConcept
definition: Moving block is based on the principle of spacing trains in absolute braking distance. In a moving block system, the rear end of a train is considered as a moving danger point to be protected against a following train. Positions of the trains are either given by trackside or trainside localisation euqipment.

Moving Block
type: Form

MB
type: Form

ETCS L2MB
type: Form

MRT
type: LexicalEntry
type: Word
canonical form: MRT
sense: MRT lexSense

MRT lexConcept
type: LexicalConcept
definition: expectation of the (mean) repair time [SOURCE: IEC 60050-192:2015, 192-07-21] Note 1: MRT = fault localization time + fault correction time + function checkout time according SPPRAMSS-3539 - [EN 61703: 2016]

MRT
type: Form

MTBF
type: LexicalEntry
type: Word
canonical form: MTBF
sense: MTBF lexSense

MTBF lexConcept
type: LexicalConcept
definition: mean operating time between failures expectation of the duration of the operating time between failures Note 1 to entry: Mean operating time between failures should only be applied to repairable items. For non-repairable items, see mean operating time to failure (192-05-11) SPPRAMSS-4040 - MTTF . [SOURCE: IEC 60050-192:2015, 192-05-13]

MTBF
type: Form

MTBSF
type: LexicalEntry
type: Word
canonical form: MTBSF
sense: MTBSF lexSense

MTBSF lexConcept
type: LexicalConcept
definition: mean operating time between service failures Note 1 to entry: Service failures should be defined as one of the failures severity levels. These failures are understood as failures with operational impact. For example failures for which the safety reaction is application of the service brake. Note 2 to entry: Abbreviation is not yet defined in any CEN/CENELEC railway standard but is often used by railway operators and infrastructure managers.

MTBSF
type: Form

MTD
type: LexicalEntry
type: Word
canonical form: MTD
sense: MTD lexSense

MTD lexConcept
type: LexicalConcept
definition: mean technical delay [SOURCE: SPPRAMSS-349 - [EN 50126-1:2017] Annex B.4]

MTD
type: Form

MTTFF
type: LexicalEntry
type: Word
canonical form: MTTFF
sense: MTTFF lexSense

MTTFF lexConcept
type: LexicalConcept
definition: mean operating time to first failure expectation of the operating time to first failure Note 1 to entry: See also operating time to first failure (192-05-02). Note 2 to entry: For non-repairable items, the MTTFF is also the MTTF. [SOURCE: IEC 60050-192:2015, 192-05-12]

MTTFF
type: Form

MTTF
type: LexicalEntry
type: Word
canonical form: MTTF
sense: MTTF lexSense

MTTF lexConcept
type: LexicalConcept
definition: mean operating time to failure expectation of the operating time to failure Note 1 to entry: In the case of non-repairable items with an exponential distribution of operating times to failure (i.e. a constant failure rate) the MTTF is numerically equal to the reciprocal of the failure rate. This is also true for repairable items if after restoration they can be considered to be "as-good-as-new". Note 2 to entry: See also operating time to failure (192-05-01) SPPRAMSS-4441 - operating time to failure, <of an item> . [SOURCE: IEC 60050-192:2015, 192-05-11]

MTTF
type: Form

MTTR
type: LexicalEntry
type: Word
canonical form: MTTR
sense: MTTR lexSense

MTTR lexConcept
type: LexicalConcept
definition: mean time to restoration - expectation of the time to restoration deprecated: mean time to repair, mean time to recovery Note 1 to entry: IEC 60050-191:1990 (now withdrawn; replaced by IEC 60050-192:2015) defined the term ”mean time to recovery” as a synonym, but restoration and recovery are not synonyms. Note 2 to entry: MTTR = MFDT + MAD + MLD + MTD + MRT according SPPRAMSS-3539 - [EN 61703: 2016] [SOURCE: IEC 60050-192, 192-07-23, modified: Note 2 to entry added.]

MTTR
type: Form

Multi Display System Unit
type: LexicalEntry
type: MultiwordExpression
canonical form: Multi Display System Unit
sense: MULTI--DISPLAY--SYSTEM--UNIT lexSense

MULTI--DISPLAY--SYSTEM--UNIT lexConcept
type: LexicalConcept
definition: The{comment:9} Multi Display System Unit consists of the generic Display Computing Unit, the Display Controller and the Touch Display (Touch Panel).

MULTI--DISPLAY--SYSTEM--UNIT lexConcept 2
type: LexicalConcept
definition: The Multi Display System Unit consists of the generic display computing unit, the Display HW controller and the Touch Display (Touch Panel).

Multi Display System Unit
type: Form

MDS
type: Acronym
type: LexicalEntry
acronym for: MULTI--DISPLAY--SYSTEM label
canonical form: MDS

MULTI--DISPLAY--SYSTEM lexConcept
type: LexicalConcept
definition: MDS - Multi Display System

Multi Display System
type: Form

MDS
type: Form

MVCC
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: MULTI-VERSION--CONCURRENCY--CONTROL label
canonical form: MVCC

MULTI-VERSION--CONCURRENCY--CONTROL lexConcept
type: LexicalConcept
definition: Multi-version concurrency control

Multi-version concurrency control
type: Form

MVCC
type: Form

MILS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: MULTIPLE--INDEPENDENT--LEVELS--OF--SECURITY--OR--SAFETY label
canonical form: MILS

MULTIPLE--INDEPENDENT--LEVELS--OF--SECURITY--OR--SAFETY lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Multiple Independent Levels of Security or Safety

Multiple Independent Levels of Security or Safety
type: Form

MILS
type: Form

Narrow Interfaces
type: LexicalEntry
type: MultiwordExpression
canonical form: Narrow Interfaces
sense: NARROW--INTERFACES lexSense

NARROW--INTERFACES lexConcept
type: LexicalConcept
definition: narrow interfaces TBD

Narrow Interfaces
type: Form

National development
type: LexicalEntry
type: MultiwordExpression
canonical form: National development
sense: NATIONAL--DEVELOPMENT lexSense

NATIONAL--DEVELOPMENT lexConcept
type: LexicalConcept
definition: A "national development" of product functionality creates SPP-2222 - Missing cross-reference.

National development
type: Form

NIP
type: Acronym
type: LexicalEntry
acronym for: NATIONAL--IMPLEMENATION--PLAN label
canonical form: NIP

NATIONAL--IMPLEMENATION--PLAN lexConcept
type: LexicalConcept
definition: In 2016, the EC also asked the EU Member States to establish the so-called “National Implementation Plans” (NIPs) in which they have to describe their actions to comply with the relevant standard for ERTMS, i.e. CCS TSI 2016/919. The CCS TSI regulates the implementation of fully interoperable 'control-command and signalling' subsystems. The NIPs have to fulfil two conditions, i.e. they must cover a period of at least 15 years and they must be updated every 5 years. In addition, they have to contain the following information: (image: 1-screenshot-20230616-124455.png)

National Implemenation Plan
type: Form

NIP
type: Form

National Safety Authority definition 1
type: LexicalEntry
type: MultiwordExpression
canonical form: National Safety Authority definition 1
sense: NATIONAL--SAFETY--AUTHORITY--DEFINITION--1 lexSense

NATIONAL--SAFETY--AUTHORITY--DEFINITION--1 lexConcept
type: LexicalConcept
definition: National safety authority means a safety authority as defined in point (7) of Article 3 of Directive (EU) 2016/798

National Safety Authority definition 1
type: Form

National Safety Authority definition 2
type: LexicalEntry
type: MultiwordExpression
canonical form: National Safety Authority definition 2
sense: NATIONAL--SAFETY--AUTHORITY--DEFINITION--2 lexSense

NATIONAL--SAFETY--AUTHORITY--DEFINITION--2 lexConcept
type: LexicalConcept
definition: National safety authority means the national body entrusted with the tasks regarding railway safety in accordance with this Directive [ 2016 / 798 ]or any body entrusted by several Member States with those tasks in order to ensure a unified safety regime

National Safety Authority definition 2
type: Form

NTCC
type: Acronym
type: LexicalEntry
acronym for: NATIONAL--TRAFFIC--CONTROL--CENTRE label
canonical form: NTCC

NATIONAL--TRAFFIC--CONTROL--CENTRE lexConcept
type: LexicalConcept
definition: National Traffic Control Centre

National Traffic Control Centre
type: Form

NTCC
type: Form

nTMS
type: Acronym
type: LexicalEntry
acronym for: NATIONAL--TRAFFIC--MANAGEMENT--SYSTEM label
canonical form: nTMS

NATIONAL--TRAFFIC--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: National Traffic Management System

National Traffic Management System
type: Form

nTMS
type: Form

NTC
type: Acronym
type: LexicalEntry
acronym for: NATIONAL--TRAIN--CONTROL label
canonical form: NTC

NATIONAL--TRAIN--CONTROL lexConcept
type: LexicalConcept
definition: NTC - National Train Control

National Train Control
type: Form

NTC
type: Form

NLES
type: Acronym
type: LexicalEntry
acronym for: NAVIGATION--LAND--EARTH--STATION label
canonical form: NLES

NAVIGATION--LAND--EARTH--STATION lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Navigation Land Earth Station

Navigation Land Earth Station
type: Form

NLES
type: Form

NB Rail
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: NB-RAIL--ASSOCIATION label
canonical form: NB Rail

NB-RAIL--ASSOCIATION lexConcept
type: LexicalConcept
definition: The NB-Rail Association is an international non-profit organization of the Third-Party Conformity Assessment Body (Notified Body (NoBo), Designated Body (DeBo), Assessment Body (AsBo), Entity in Charge of Maintenance – Certification Body (ECM-CB)) in the European railway sector. The association is installed to support and to complement the activities of NB-Rail coordination group.

NB-Rail Association
type: Form

NB Rail
type: Form

NTMS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: NEIGHBORHOOD--TMS label
canonical form: NTMS

NEIGHBORHOOD--TMS lexConcept
type: LexicalConcept
definition: Neighborhood TMS

Neighborhood TMS
type: Form

NTMS
type: Form

Neighbouring Traffic CS
type: LexicalEntry
type: MultiwordExpression
canonical form: Neighbouring Traffic CS
sense: NEIGHBOURING--TRAFFIC--CS lexSense

NEIGHBOURING--TRAFFIC--CS lexConcept
type: LexicalConcept
definition: Neighbouring Traffic CS is located geographically adjacent to current Traffic CS territory. Neighbouring Traffic CS enables handing over or accepting a train going to/coming from current Traffic CS.{comment:17}

Neighbouring Traffic CS
type: Form

NAC
type: Acronym
type: LexicalEntry
acronym for: NETWORK--ACCESS--CONTROL label
canonical form: NAC

NETWORK--ACCESS--CONTROL lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Network Access Control

Network Access Control
type: Form

NAC
type: Form

Network Component
type: LexicalEntry
type: MultiwordExpression
canonical form: Network Component
sense: NETWORK--COMPONENT lexSense

NETWORK--COMPONENT lexConcept
type: LexicalConcept
definition: A device that facilitates IP data flow between devices, or restricts the flow of data, but may not directly interact with a control process. Examples of Network Components are network switches, LAN/WAN routers, firewalls, data diodes and VPN endpoints. Excluded from this definition are media converters, transceivers and bridges with no routing, switching or filtering capabilities. Such devices are not affected by this specification.

Network Component
type: Form

Network Statement
type: LexicalEntry
type: MultiwordExpression
canonical form: Network Statement
sense: NETWORK--STATEMENT lexSense

NETWORK--STATEMENT lexConcept
type: LexicalConcept
definition: Network statement means the statement which sets out in detail the general rules, deadlines, procedures and criteria for charging and capacity-allocation schemes, including such other information as is required to enable applications for infrastructure capacity.

Network Statement
type: Form

Network
type: LexicalEntry
type: Word
canonical form: Network
sense: NETWORK lexSense

NETWORK lexConcept
type: LexicalConcept
definition: Network means the entire railway infrastructure managed by an infrastructure manager;

Network
type: Form

Non-European Railway
type: LexicalEntry
type: MultiwordExpression
canonical form: Non-European Railway
sense: NON-EUROPEAN--RAILWAY lexSense

NON-EUROPEAN--RAILWAY lexConcept
type: LexicalConcept
definition: IM and / or RU of a country that is no member of the European Union

Non-European Railway
type: Form

Non-functional requirement
type: LexicalEntry
type: MultiwordExpression
canonical form: Non-functional requirement
sense: NON-FUNCTIONAL--REQUIREMENT lexSense

NON-FUNCTIONAL--REQUIREMENT lexConcept
type: LexicalConcept
definition: A SPPR-3791 - System Requirement which specifies the key system characteristics that determine how well the system performs duties and to define measurable criteria for evaluating a system function's effectiveness. They are often referred to as the performance targets and "quality attributes" of a system, which includes "-ilities," encompassing characteristics like safety, reliability, usability, serviceability, upgradeability, manufacturability, stability, portability, and more. They are essential to any specification as they emphasize measurable, quantitative criteria over vague qualitative descriptions, thereby ensuring the overall system's verifiability. They are pecified without imposing unnecessary design constraints or prescribing specific solutions., like the system-wide non-functional characteristic such as weight, reliability, or durability However, they can specifiy imposed specific limitations or restriction on how the system (or component, entity) is realised to define a clear solution or implementation (rather than simply guiding design choices).

Non-functional requirement
type: Form

Non-Repudiation
type: LexicalEntry
type: Word
canonical form: Non-Repudiation
sense: NON-REPUDIATION lexSense

NON-REPUDIATION lexConcept
type: LexicalConcept
definition: Non-Repudiation: ability to prove the occurrence of a claimed event or action and its originating entities (source: ISO 27000-2018 )

Non-Repudiation
type: Form

Non-Trackbound Object
type: LexicalEntry
type: MultiwordExpression
canonical form: Non-Trackbound Object
sense: NON-TRACKBOUND--OBJECT lexSense

NON-TRACKBOUND--OBJECT lexConcept
type: LexicalConcept
definition: A Non-Trackbound Object is not limited to the railway track (e.g. e.g., construction equipment, track worker)

Non-Trackbound Object
type: Form

normal/regular operation
type: LexicalEntry
type: MultiwordExpression
canonical form: normal/regular operation
sense: NORMAL REGULAR--OPERATION lexSense

NORMAL REGULAR--OPERATION lexConcept
type: LexicalConcept
definition: desired state of operation of a system/component/equipment, i.e. absence of faults.

normal/regular operation
type: Form

NB-Rail
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: NOTIFIED--BODIES--FOR--INTEROPERABILITY--IN--THE--RAILWAY--SECTOR label
canonical form: NB-Rail

NOTIFIED--BODIES--FOR--INTEROPERABILITY--IN--THE--RAILWAY--SECTOR lexConcept
type: LexicalConcept
definition: Notified bodies for interoperability in the railway sector

Notified bodies for interoperability in the railway sector
type: Form

NB-Rail
type: Form

NoBo
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: NOTIFIED--BODY label
canonical form: NoBo

NOTIFIED--BODY lexConcept
type: LexicalConcept
definition: From DIRECTIVE (EU) 2016/797 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 11 May 2016 on the interoperability of the rail system within the European Union: (42) ‘conformity assessment body’ means a body that has been notified or designated to be responsible for conformity assessment activities, including calibration, testing, certification and inspection; a conformity assessment body is classified as a ‘notified body’ following notification by a Member State; a conformity assessment body is classified as a ‘designated body’ following designation by a Member State;

Notified Body
type: Form

NoBo
type: Form

NNTR
type: Acronym
type: LexicalEntry
acronym for: NOTIFIED--NATIONAL--TECHNICAL--RULES label
canonical form: NNTR

NOTIFIED--NATIONAL--TECHNICAL--RULES lexConcept
type: LexicalConcept
definition: 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)

Notified national technical rules
type: Form

NNTR
type: Form

NP - No Power Mode in ETCS
type: LexicalEntry
type: MultiwordExpression
canonical form: NP - No Power Mode in ETCS
sense: NP-----NO--POWER--MODE--IN--ETCS lexSense

NP-----NO--POWER--MODE--IN--ETCS lexConcept
type: LexicalConcept
definition: NP - No Power Mode in ETCS

NP - No Power Mode in ETCS
type: Form

NRV
type: LexicalEntry
type: Word
canonical form: NRV
sense: NRV lexSense

NRV lexConcept
type: LexicalConcept
definition: ‘national reference value (NRV)’ means a reference measure indicating, for the Member State concerned, the maximum tolerable level for a railway risk category; SPPRAMSS-347 - [2009/460/EC]

NRV
type: Form

NSA
type: LexicalEntry
type: Word
canonical form: NSA
sense: NSA lexSense

NSA lexConcept
type: LexicalConcept
definition: National Safety Authority

NSA
type: Form

NTP - National Train Protection
type: LexicalEntry
type: MultiwordExpression
canonical form: NTP - National Train Protection
sense: NTP-----NATIONAL--TRAIN--PROTECTION lexSense

NTP-----NATIONAL--TRAIN--PROTECTION lexConcept
type: LexicalConcept
definition: NTP - National Train Protection

NTP - National Train Protection
type: Form

Object Name
type: LexicalEntry
type: MultiwordExpression
canonical form: Object Name
sense: OBJECT--NAME lexSense

OBJECT--NAME lexConcept
type: LexicalConcept
definition: An object name is a string that helps humans identity an object and that may reveal meaningful information about the object.

Object Name
type: Form

ODO
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ODOMETRY label
canonical form: ODO

ODOMETRY lexConcept
type: LexicalConcept
definition: This term represents the odometry functionality as specified in the CCS TSI 2023. According to the glossary (SUBSET-23, TSI 2023): Odometry is the process of measuring the train’s movement along the track. Used for speed measurement and distance measurement.

Odometry
type: Form

ODO
type: Form

OE - Operational Execution
type: LexicalEntry
type: MultiwordExpression
canonical form: OE - Operational Execution
sense: OE-----OPERATIONAL--EXECUTION lexSense

OE-----OPERATIONAL--EXECUTION lexConcept
type: LexicalConcept
definition: OE - Operational Execution

OE - Operational Execution
type: Form

OMS - Online Monitoring System
type: LexicalEntry
type: MultiwordExpression
canonical form: OMS - Online Monitoring System
sense: OMS-----ONLINE--MONITORING--SYSTEM lexSense

OMS-----ONLINE--MONITORING--SYSTEM lexConcept
type: LexicalConcept
definition: OMS - Online Monitoring System NOTE : OMS is both trackside and on-board.

OMS - Online Monitoring System
type: Form

OMTS - On Board Multimedia & Telematics System (X2R4, equivalent with Passenger...
type: LexicalEntry
type: MultiwordExpression
canonical form: OMTS - On Board Multimedia & Telematics System (X2R4, equivalent with Passenger...
sense: OMTS-----ON--BOARD--MULTIMEDIA--AND--TELEMATICS--SYSTEM--X2R4--EQUIVALENT--WITH--PASSENGER lexSense

OMTS-----ON--BOARD--MULTIMEDIA--AND--TELEMATICS--SYSTEM--X2R4--EQUIVALENT--WITH--PASSENGER lexConcept
type: LexicalConcept
definition: OMTS - On Board Multimedia & Telematics System (X2R4, equivalent with Passenger Information System)

OMTS-----ON--BOARD--MULTIMEDIA--AND--TELEMATICS--SYSTEM--X2R4--EQUIVALENT--WITH--PASSENGER lexConcept 2
type: LexicalConcept
definition: OMTS - On Board Multimedia & Telematics System (X2R4, equivalent with Passenger Information System)

OMTS-----ON--BOARD--MULTIMEDIA--AND--TELEMATICS--SYSTEM--X2R4--EQUIVALENT--WITH--PASSENGER lexConcept 3
type: LexicalConcept
definition: OMTS - On Board Multimedia & Telematics System (X2R4, equivalent with Passenger Information System)

OMTS-----ON--BOARD--MULTIMEDIA--AND--TELEMATICS--SYSTEM--X2R4--EQUIVALENT--WITH--PASSENGER lexConcept 4
type: LexicalConcept
definition: OMTS - On Board Multimedia & Telematics System (X2R4, equivalent with Passenger Information System)

OMTS-----ON--BOARD--MULTIMEDIA--AND--TELEMATICS--SYSTEM--X2R4--EQUIVALENT--WITH--PASSENGER lexConcept 5
type: LexicalConcept
definition: OMTS - On Board Multimedia & Telematics System (X2R4, equivalent with Passenger Information System)

OMTS-----ON--BOARD--MULTIMEDIA--AND--TELEMATICS--SYSTEM--X2R4--EQUIVALENT--WITH--PASSENGER lexConcept 6
type: LexicalConcept
definition: OMTS - On Board Multimedia & Telematics System (X2R4, equivalent with Passenger Information System)

OMTS - On Board Multimedia & Telematics System (X2R4, equivalent with Passenger...
type: Form

OB
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ON-BOARD label
canonical form: OB

ON-BOARD lexConcept
type: LexicalConcept
definition: On-Board

ON-BOARD lexConcept 2
type: LexicalConcept
definition: OB - On-board

On-Board
type: Form

OB
type: Form

OB
type: Form

Onboard Strategy
type: LexicalEntry
type: MultiwordExpression
canonical form: Onboard Strategy
sense: ONBOARD--STRATEGY lexSense

ONBOARD--STRATEGY lexConcept
type: LexicalConcept
definition: strategy of equipping and upgrading the trains with onboard communication units and additional technology as localisation, train integrity etc.

Onboard Strategy
type: Form

One CCU-based external position is not yet determined.
type: LexicalEntry
type: MultiwordExpression
canonical form: One CCU-based external position is not yet determined.
sense: ONE--CCU-BASED--EXTERNAL--POSITION--IS--NOT--YET--DETERMINED lexSense

ONE--CCU-BASED--EXTERNAL--POSITION--IS--NOT--YET--DETERMINED lexConcept
type: LexicalConcept
definition: One CCU-based external position is not yet determined.

One CCU-based external position is not yet determined.
type: Form

Online Monitoring System On Board
type: LexicalEntry
type: MultiwordExpression
canonical form: Online Monitoring System On Board
sense: ONLINE--MONITORING--SYSTEM--ON--BOARD lexSense

ONLINE--MONITORING--SYSTEM--ON--BOARD lexConcept
type: LexicalConcept
definition: The On Board part of the Online Monitoring System as defined in SUBSET-149

Online Monitoring System On Board
type: Form

OPC UA endpoint
type: LexicalEntry
type: MultiwordExpression
canonical form: OPC UA endpoint
sense: OPC--UA--ENDPOINT lexSense

OPC--UA--ENDPOINT lexConcept
type: LexicalConcept
definition: The OPC UA endpoint is a Secure Component using OPC UA communication (client and server).

OPC UA endpoint
type: Form

OCORA
type: Acronym
type: LexicalEntry
acronym for: OPEN--CCS--ON-BOARD--REFERENCE--ARCHITECTURE label
canonical form: OCORA

OPEN--CCS--ON-BOARD--REFERENCE--ARCHITECTURE lexConcept
type: LexicalConcept
definition: OCORA - Open CCS On-board Reference Architecture

Open CCS On-board Reference Architecture
type: Form

OCORA
type: Form

OSI layer
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: OPEN--SYSTEM--INTERACTION--MODEL label
canonical form: OSI layer

OPEN--SYSTEM--INTERACTION--MODEL lexConcept
type: LexicalConcept
definition: Open System Interaction Model, aka OSI 7 System Layer model

Open System Interaction Model
type: Form

OSI layer
type: Form

Operating Rules
type: LexicalEntry
type: MultiwordExpression
canonical form: Operating Rules
sense: OPERATING--RULES lexSense

OPERATING--RULES lexConcept
type: LexicalConcept
definition: Operating rules are entendend to inhance railway safety. They cover responsibilities, functionality of signalling equipment, procedures for safe train movement, handling incidents and accidents and other topics that are related to railway safety..

Operating Rules
type: Form

Operating State
type: LexicalEntry
type: MultiwordExpression
canonical form: Operating State
sense: OPERATING--STATE lexSense

OPERATING--STATE lexConcept
type: LexicalConcept
definition: The Operating State is the logical real-time representation of the actual state of the physical railway system in the Area of Control (e.g. information about the currently operating Train Units, the occupation of tracks, or the settings of Field Elements). The knowledge about the Operating State enables TMS to keep itself current with the operational situation in the Area of Control and to recognise deviations from an Operational Plan during execution. Further, it allows for identifying upcoming or existing conflicts between Operational Plans and developing appropriate countermeasures.

OPERATING--STATE lexConcept 2
type: LexicalConcept
definition: The operating state describes the current state of production: * how trains move * where trains are * which route is set in control system * status of assets This information is based on inputs from control systems.

OPERATING--STATE lexConcept 3
type: LexicalConcept
definition: The operating state describes the current state of production: * how trains move * where trains are * which route is set in control system * status of assets This information is based on inputs from control systems.

Operating State
type: Form

OS
type: Acronym
type: LexicalEntry
acronym for: OPERATING--SYSTEM label
canonical form: OS

OPERATING--SYSTEM lexConcept
type: LexicalConcept
definition: Operating system

Operating system
type: Form

OS
type: Form

operating time to failure, <of an item>
type: LexicalEntry
type: MultiwordExpression
canonical form: operating time to failure, <of an item>
sense: OPERATING--TIME--TO--FAILURE--<OF--AN--ITEM> lexSense

OPERATING--TIME--TO--FAILURE--<OF--AN--ITEM> lexConcept
type: LexicalConcept
definition: operating time accumulated from the first use, or from restoration, until failure Note 1 to entry: See also operating time (192-02-05) SPPRAMSS-4080 - operating time . [SOURCE: IEC 60050-192:2015, 192-05-01]

operating time to failure, <of an item>
type: Form

operating time
type: LexicalEntry
type: MultiwordExpression
canonical form: operating time
sense: OPERATING--TIME lexSense

OPERATING--TIME lexConcept
type: LexicalConcept
definition: Time interval for which an item is in an operating state Note 1 to entry: The duration of operating time may be expressed in units appropriate to the item concerned, e.g. calendar time, operating cycles, distance run, etc., and the units should always be clearly stated. [SOURCE: IEC 60050-192:2015, 192-02-05]

operating time
type: Form

Operation and Traffic Management
type: LexicalEntry
type: MultiwordExpression
canonical form: Operation and Traffic Management
sense: OPERATION--AND--TRAFFIC--MANAGEMENT lexSense

OPERATION--AND--TRAFFIC--MANAGEMENT lexConcept
type: LexicalConcept
definition: The procedures and related equipment permitting coherent operation of the various structural subsystems, during both normal and degraded operation, including in particular train composition and train driving, traffic planning and management.

Operation and Traffic Management
type: Form

Operational Activity
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Activity
sense: OPERATIONAL--ACTIVITY lexSense

OPERATIONAL--ACTIVITY lexConcept
type: LexicalConcept
definition: On operational activity is one step in an operational process, that has inputs and outputs. The activity describes what and how the operational entity the operational activity is allocated to is doing.

Operational Activity
type: Form

Operational Capability
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Capability
sense: OPERATIONAL--CAPABILITY lexSense

OPERATIONAL--CAPABILITY lexConcept
type: LexicalConcept
definition: 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.

Operational Capability
type: Form

OpsCON
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: OPERATIONAL--CONCEPTS label
canonical form: OpsCON

OPERATIONAL--CONCEPTS lexConcept
type: LexicalConcept
definition: Operational concepts (How system should function)

Operational concepts
type: Form

OpsCON
type: Form

Operational Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Data
sense: OPERATIONAL--DATA lexSense

OPERATIONAL--DATA lexConcept
type: LexicalConcept
definition: Operational Data refers to real-time information generated from daily operations and activities related to the functioning of railway systems, reflecting the current status of operations (e.g. locked position of a switch). Operational data is exchanged between CCS/TMS systems via Standard Communication Interfaces (SCI-xx). Note: while Operational Data can be related to infrastructure or vehicle configuration data, it is clearly separated from SPT2TS-127779 - Configuration Data . {comment:74}

Operational Data
type: Form

Operational Entity/Actor
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Entity/Actor
sense: OPERATIONAL--ENTITY ACTOR lexSense

OPERATIONAL--ENTITY ACTOR lexConcept
type: LexicalConcept
definition: A person or organisation performing an operational activity.

Operational Entity/Actor
type: Form

Operational Epics
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Epics
sense: OPERATIONAL--EPICS lexSense

OPERATIONAL--EPICS lexConcept
type: LexicalConcept
definition: Operational epics refer to large-scale initiatives or projects that are focused on improving the operational aspects of a business or organization. Unlike user epics, which typically address customer or user needs, operational epics are aimed at enhancing internal processes, systems, or infrastructure to optimize efficiency, productivity, and overall performance. Operational epics often involve cross-functional collaboration and may span multiple departments or teams within an organization. They are typically strategic in nature and aligned with the overall goals and objectives of the organization. Examples of operational epics could include implementing a new supply chain management system, revamping the customer support process, or optimizing the IT infrastructure to improve data security and accessibility. The use of epics in operational contexts helps break down complex initiatives into manageable units, allowing for better planning, resource allocation, and tracking of progress. By focusing on operational improvements, organizations can streamline their workflows, reduce costs, and enhance the overall effectiveness of their operations.

Operational Epics
type: Form

OHT
type: Acronym
type: LexicalEntry
acronym for: OPERATIONAL--HARMONIZATION--TEAM label
canonical form: OHT

OPERATIONAL--HARMONIZATION--TEAM lexConcept
type: LexicalConcept
definition: Operational Harmonization Team

Operational Harmonization Team
type: Form

OHT
type: Form

Operational harmonization
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational harmonization
sense: OPERATIONAL--HARMONIZATION lexSense

OPERATIONAL--HARMONIZATION lexConcept
type: LexicalConcept
definition: An operational topic (process, actor, defintion, ...) is considered harmonized if a description is provided in the SP context that fulfills: * This description is exhaustive, delimited and precise. There is no remaining "open space and freedom". The scope is clearly defined. Existing gaps are clearly identified. Statements are formulated unambiguously, if necessary in a formal form. {comment:98} * A set of variants and parameters, if necessary, are part of the description. * The description has been agreed by both Railway and Industry stakeholdes. This consens is especially defined under the light of project rework and domain standardisaton: * The description is agreed by the railways stakeholders of system Pillar as fitting their need, i.e. all their needs are fullfilled by the available variants and parameters without having again a solution discussion or check. * This description is agreed by the industry stakeholdes as 1:1 implementable, without having to reopen again the ambiguity discussion

Operational harmonization
type: Form

Operational Hazard
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Hazard
sense: OPERATIONAL--HAZARD lexSense

OPERATIONAL--HAZARD lexConcept
type: LexicalConcept
definition: Hazard whose cause is related to a failure in the application of an operational scenario/procedure (e.g. hazard due to operator or signaler or driver error) and/or to external events. These hazards are managed by means of "Operational Hazard" Work Item.

OPERATIONAL--HAZARD lexConcept 2
type: LexicalConcept
definition: Hazard whose cause is related to a failure in the application of an operational scenario/procedure (e.g. hazard due to operator or signaler or driver error) and/or to external events. These hazards are managed by means of "Operational Hazard" Work Item.

OPERATIONAL--HAZARD lexConcept 3
type: LexicalConcept
definition: A problematic situation that can occure with a process design.

Operational Hazard
type: Form

I0
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: OPERATIONAL--INTERFACE label
canonical form: I0

OPERATIONAL--INTERFACE lexConcept
type: LexicalConcept
definition: 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.

Operational Interface
type: Form

I0
type: Form

Operational Mission Segment
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Mission Segment
sense: OPERATIONAL--MISSION--SEGMENT lexSense

OPERATIONAL--MISSION--SEGMENT lexConcept
type: LexicalConcept
definition: SPT2OD-5097 - Missing cross-reference refers to the portion of an SPT2OD-4977 - Missing cross-referencewhich represents the path on the railway track which is to be used for an immediate SPT2OD-4965 - Missing cross-reference movement and/or a related SPT2OD-4978 - Missing cross-reference .

Operational Mission Segment
type: Form

Operational Mission
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Mission
sense: OPERATIONAL--MISSION lexSense

OPERATIONAL--MISSION lexConcept
type: LexicalConcept
definition: SPT2OD-4977 - Missing cross-reference refers to the complete operational journey planned from one initial position on the railway network to a final position on the railway network. Most commonly this can be exemplified by the commercial journey starting at a central station, passing through many regional stations before ending at a final central station somewhere else on the railway network. One SPT2OD-4977 - Missing cross-reference may have many SPT2OD-4978 - Missing cross-reference and may be assigned to the responsibility of one or more SPT2OD-4967 - Missing cross-reference along the way.

Operational Mission
type: Form

Operational Movement
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Movement
sense: OPERATIONAL--MOVEMENT lexSense

OPERATIONAL--MOVEMENT lexConcept
type: LexicalConcept
definition: An Operational Movement is part of the Operational Plan, and consist of a timetable or train service specifying when and where particular events are to take place. Some of these events could be a commercial stop, a run through over certain location or even a change of train composition or a handover to another Traffic Management System. The most simple way of representation of such timetable is in a tabular form indicating station or run through location, and arrival and departure time. More events could be associated a certain stations or locations depending on the Railway Undertaking needs. The Operational Movement is defined in such a way that the final user (passenger or freight company) knows if a particular timetable suits his/her needs.

Operational Movement
type: Form

Operational Plan
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Plan
sense: OPERATIONAL--PLAN lexSense

OPERATIONAL--PLAN lexConcept
type: LexicalConcept
definition: 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.

OPERATIONAL--PLAN lexConcept 2
type: LexicalConcept
definition: Analogous to the capacity plan, the operational plan supplies the train and traffic control and all other components with the operational train data. The operational plan is fed from the active timetable buffer and contains all trains (from the timetable buffer) that are currently in their operational time window. The operational plan is the result of various influences (decisions from dispatching, map data, etc.). It is updated every single minute.

Operational Plan
type: Form

OR
type: Acronym
type: LexicalEntry
acronym for: OPERATIONAL--REQUIREMENTS label
canonical form: OR

OPERATIONAL--REQUIREMENTS lexConcept
type: LexicalConcept
definition: Operational Requirements

Operational Requirements
type: Form

OR
type: Form

Operational Requirement
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Requirement
sense: OPERATIONAL--REQUIREMENT lexSense

OPERATIONAL--REQUIREMENT lexConcept
type: LexicalConcept
definition: 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 Requirement
type: Form

Operational Risk.
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Risk.
sense: OPERATIONAL--RISK lexSense

OPERATIONAL--RISK lexConcept
type: LexicalConcept
definition: Value and mitigation for a operational hazard

Operational Risk.
type: Form

Operational State
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational State
sense: OPERATIONAL--STATE lexSense

OPERATIONAL--STATE lexConcept
type: LexicalConcept
definition: Dynamic state of all Domain Objects of the Domain Model of Traffic CS. The Operational State of ETPS reflects its view onto the managed objects, and updates on the Operational State are communicated to neighbour systems in Traffic CS like PES.

Operational State
type: Form

Operational Stop
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Stop
sense: OPERATIONAL--STOP lexSense

OPERATIONAL--STOP lexConcept
type: LexicalConcept
definition: SPT2OD-4978 - Missing cross-reference refer to the operational activities undertaken along, and in relation to, an SPT2OD-4977 - Missing cross-reference . Most commonly this can be exemplified by the station stops within a planned commercial journey for the entry/exit of passengers.

Operational Stop
type: Form

Operational track properties
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational track properties
sense: OPERATIONAL--TRACK--PROPERTIES lexSense

OPERATIONAL--TRACK--PROPERTIES lexConcept
type: LexicalConcept
definition: 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

Operational track properties
type: Form

OPE
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: OPERATIONAL--TSI label
canonical form: OPE

OPERATIONAL--TSI lexConcept
type: LexicalConcept
definition: Operational TSI

Operational TSI
type: Form

OPE
type: Form

Operative FS Comp
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: OPERATIVE--FS--COMPARTMENT label
canonical form: Operative FS Comp

OPERATIVE--FS--COMPARTMENT lexConcept
type: LexicalConcept
definition: It contains the complete SW packages (BBCs) which represent in total the FS Compartment for the operative running mode. These are the BBC(SW-x).

Operative FS Compartment
type: Form

Operative FS Comp
type: Form

O-IF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: OPERATOR--INTERFACE label
canonical form: O-IF

OPERATOR--INTERFACE lexConcept
type: LexicalConcept
definition: Operator Interface

Operator Interface
type: Form

O-IF
type: Form

Opex
type: LexicalEntry
type: Word
canonical form: Opex
sense: OPEX lexSense

OPEX lexConcept
type: LexicalConcept
definition: Operational Expenditures

Opex
type: Form

OI
type: Acronym
type: LexicalEntry
acronym for: ORCHESTRATION--INTERFACE label
canonical form: OI

ORCHESTRATION--INTERFACE lexConcept
type: LexicalConcept
definition: This interface is used to manage (monitor, control, diagnose, configure) the virtual computing environments.

Orchestration Interface
type: Form

OI
type: Form

Overlapped
type: LexicalEntry
type: Word
canonical form: Overlapped
sense: OVERLAPPED lexSense

OVERLAPPED lexConcept
type: LexicalConcept
definition: 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
type: Form

Override
type: LexicalEntry
type: Word
canonical form: Override
sense: OVERRIDE lexSense

OVERRIDE lexConcept
type: LexicalConcept
definition: A procedure in specific degraded situations (for example in the case of loss of communication session or a failed trackside element (signal/MB, track circuit, failed point, etc)), when railways allow a train to pass its End of Movement Authority or an authorised location or a location that will trip the train. The driver must not use the Override procedure unless authorised by trackside personnel / Signaller. The OB has to fulfill certain conditions for the Override to be available in the DMI, these conditions are stated in Subset-026 section 5.8.2.1 and ERA_ERTMS_015560 (DMI specs) Table 34.

Override
type: Form

Parameter Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Parameter Data
sense: PARAMETER--DATA lexSense

PARAMETER--DATA lexConcept
type: LexicalConcept
definition: Parameter Data define the system configuration data required for national and supplier-specific operative environments. A notable example of such data are ETCS national values. ETCS national values may be required for migration purposes and shall be replaced by SERA standardised values in the target system.{comment:34}

Parameter Data
type: Form

Partial Train Cancelation
type: LexicalEntry
type: MultiwordExpression
canonical form: Partial Train Cancelation
sense: PARTIAL--TRAIN--CANCELATION lexSense

PARTIAL--TRAIN--CANCELATION lexConcept
type: LexicalConcept
definition: Cancel parts of the train journey. E.g., Train 00715 Interlaken - Spiez - Bern - Olten - Basel -> Interlaken - Spiez - Bern

Partial Train Cancelation
type: Form

PIS
type: Acronym
type: LexicalEntry
acronym for: PASSENGER--INFORMATION--SYSTEM label
canonical form: PIS

PASSENGER--INFORMATION--SYSTEM lexConcept
type: LexicalConcept
definition: Passenger Information System

Passenger Information System
type: Form

PIS
type: Form

Passenger Information Time
type: LexicalEntry
type: MultiwordExpression
canonical form: Passenger Information Time
sense: PASSENGER--INFORMATION--TIME lexSense

PASSENGER--INFORMATION--TIME lexConcept
type: LexicalConcept
definition: The duration of the platform change announcement

Passenger Information Time
type: Form

Passenger transfer
type: LexicalEntry
type: MultiwordExpression
canonical form: Passenger transfer
sense: PASSENGER--TRANSFER lexSense

PASSENGER--TRANSFER lexConcept
type: LexicalConcept
definition: Passenger transfer is the process where a passenger enters, leaves or switches from one train to another.

Passenger transfer
type: Form

Patch
type: LexicalEntry
type: Word
canonical form: Patch
sense: PATCH lexSense

PATCH lexConcept
type: LexicalConcept
definition: 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).

Patch
type: Form

POS
type: Acronym
type: LexicalEntry
acronym for: PATH--ORDER--SYSTEM label
canonical form: POS

PATH--ORDER--SYSTEM lexConcept
type: LexicalConcept
definition: Path Order System

Path Order System
type: Form

POS
type: Form

Pay Load Type
type: LexicalEntry
type: MultiwordExpression
canonical form: Pay Load Type
sense: PAY--LOAD--TYPE lexSense

PAY--LOAD--TYPE lexConcept
type: LexicalConcept
definition: The contents loaded in a train. e.g., Dangerous goods is a type of the payload

Pay Load Type
type: Form

PER
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: PERCEPTION label
canonical form: PER

PERCEPTION lexConcept
type: LexicalConcept
definition: PER - Perception

Perception
type: Form

PER
type: Form

performance < of an item >
type: LexicalEntry
type: MultiwordExpression
canonical form: performance < of an item >
sense: PERFORMANCE--<--OF--AN--ITEM--> lexSense

PERFORMANCE--<--OF--AN--ITEM--> lexConcept
type: LexicalConcept
definition: Performance is the ability of all technical and operational functions, in a specific operational context, to deliver a pre-defined and agreed level of service of the system and/or vehicle in operation. With the addition (and further clarification) that: The minimum level of performance is determined and influenced by technical and operational aspects on system, vehicle and operational level, such as but not limited to: reliability, availability, maintainability, safety, security, human factors, quality, mission profile, environment, environmental conditions and laws and regulations. This means the scope and boundaries (span of control) of performance need to be defined clearly. This also stresses why the inclusion of the principles of the RAM Policy to the ERJU activities for PRAMS, is of high importance.

performance < of an item >
type: Form

PRAMSS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: PERFORMANCE--RELIABILITY--AVAILABILITY--MAINTAINABILITY--SAFETY--AND--SECURITY label
canonical form: PRAMSS

PERFORMANCE--RELIABILITY--AVAILABILITY--MAINTAINABILITY--SAFETY--AND--SECURITY lexConcept
type: LexicalConcept
definition: Performance, reliability, availability, maintainability, safety and security

Performance, reliability, availability, maintainability, safety and security
type: Form

PRAMSS
type: Form

Performance requirement
type: LexicalEntry
type: MultiwordExpression
canonical form: Performance requirement
sense: PERFORMANCE--REQUIREMENT lexSense

PERFORMANCE--REQUIREMENT lexConcept
type: LexicalConcept
definition: A performance requirement is a non-functional requirement associated with corresponding functional requirement and defines how well a particular function has to perform – they are the constraints on that function.

Performance requirement
type: Form

PFH
type: LexicalEntry
type: Word
canonical form: PFH
sense: PFH lexSense

PFH lexConcept
type: LexicalConcept
definition: average frequency of a dangerous failure per hour average frequency of a dangerous failure of an E/E/PE safety related system to perform the specified safety function over a given period of time NOTE 1 The term “probability of dangerous failure per hour” is not used in this standard but the acronym PFH has been retained but when it is used it means “average frequency of dangerous failure [h]". NOTE 2 From a theoretical point of view, the PFH is the average of the unconditional failure intensity, also called failure frequency, and which is generally designated w(t). It should not be confused with a failure rate (see Annex B of IEC 61508-6). NOTE 3 When the E/E/PE safety-related system is the ultimate safety layer, the PFH should be calculated from its unreliability F(T)=1-R(t) (see “failure rate” above). When it is not the ultimate safety-related system its PFH should be calculated from its unavailability U(t) (see PFD above). PFH approximations are given by F(T)/T and 1/MTTF in the first case and 1/MTBF in the second case. NOTE 4 When the E/E/PE safety-related system implies only quickly repaired revealed failures then an asymptotic failure rate λas is quickly reached. It provides an estimate of the PFH. [EN 61508-4:2010 - §3.6.19]

PFH lexConcept 2
type: LexicalConcept
definition: probability of dangerous failure per hour [EN 61508-4:2010]

PFH lexConcept 3
type: LexicalConcept
definition: probability of dangerous failure per hour [SOURCE: EN 61508-4:2010]

PFH
type: Form

PCE
type: Acronym
type: LexicalEntry
acronym for: PHYSICAL--COMPUTING--ELEMENT label
canonical form: PCE

PHYSICAL--COMPUTING--ELEMENT lexConcept
type: LexicalConcept
definition: The Physical Computing Element refers to the physical device providing compute resources.

Physical Computing Element
type: Form

PCE
type: Form

Physical Link
type: LexicalEntry
type: MultiwordExpression
canonical form: Physical Link
sense: PHYSICAL--LINK lexSense

PHYSICAL--LINK lexConcept
type: LexicalConcept
definition: Means of communication/transport relating to the hosting of physical components, used as a medium by exchanges between behavioural components.

Physical Link
type: Form

PIS - Passenger Information System
type: LexicalEntry
type: MultiwordExpression
canonical form: PIS - Passenger Information System
sense: PIS-----PASSENGER--INFORMATION--SYSTEM lexSense

PIS-----PASSENGER--INFORMATION--SYSTEM lexConcept
type: LexicalConcept
definition: PIS - Passenger Information System

PIS-----PASSENGER--INFORMATION--SYSTEM lexConcept 2
type: LexicalConcept
definition: PIS - Passenger Information System

PIS-----PASSENGER--INFORMATION--SYSTEM lexConcept 3
type: LexicalConcept
definition: PIS - Passenger Information System

PIS-----PASSENGER--INFORMATION--SYSTEM lexConcept 4
type: LexicalConcept
definition: PIS - Passenger Information System

PIS-----PASSENGER--INFORMATION--SYSTEM lexConcept 5
type: LexicalConcept
definition: PIS - Passenger Information System

PIS-----PASSENGER--INFORMATION--SYSTEM lexConcept 6
type: LexicalConcept
definition: PIS - Passenger Information System

PIS - Passenger Information System
type: Form

PES
type: Acronym
type: LexicalEntry
acronym for: PLAN--EXECUTION--SYSTEM label
canonical form: PES

PLAN--EXECUTION--SYSTEM lexConcept
type: LexicalConcept
definition: 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.

Plan Execution System
type: Form

PES
type: Form

PE
type: Acronym
type: LexicalEntry
acronym for: PLAN--EXECUTION label
canonical form: PE

PLAN--EXECUTION lexConcept
type: LexicalConcept
definition: Plan Execution

Plan Execution
type: Form

PE
type: Form

Plateau
type: LexicalEntry
type: Word
canonical form: Plateau
sense: PLATEAU lexSense

PLATEAU lexConcept
type: LexicalConcept
definition: A Plateau is a consistent requirement subset of the System Pillar Reference Architecture (SPRA) to be defined by the System Pillar domains. It can be used for market tenders in a specific timeframe and is recommended by and agreed across the sector. In the context of system engineering, a "plateau" refers to a distinct stage or phase within the system development lifecycle (SDLC) where progress or development remains relatively stable or flat for a period of time. It is characterized by a temporary pause or leveling off in the advancement or evolution of the system being developed.

PLATEAU lexConcept 2
type: LexicalConcept
definition: In the context of system engineering, a "plateau" refers to a distinct stage or phase within the system development lifecycle (SDLC) where progress or development remains relatively stable or flat for a period of time. It is characterized by a temporary pause or leveling off in the advancement or evolution of the system being developed. During a plateau, the system or project may have reached a certain level of functionality, maturity, or completion. It can be seen as a natural phase in the development process, where the initial rapid progress slows down, and further enhancements or major changes are temporarily put on hold. This can occur for various reasons, such as: * Technical Stability: The system has achieved a stable and functioning state, meeting the primary objectives or requirements defined for that particular stage of development. The focus during this phase may shift towards fine-tuning, optimization, and bug fixing. * Resource Allocation: The allocation of resources, including personnel, time, and budget, may be temporarily redirected to other areas of priority. This can result in a pause in major advancements for the system on the plateau. * Stakeholder Evaluation: Stakeholders may require time to evaluate and provide feedback on the current state of the system before proceeding to the next phase. This evaluation period can lead to a plateau in development activities. * Planning and Preparation: The system engineering team may use the plateau phase to plan and prepare for the next stage of development. This includes conducting feasibility studies, conducting risk assessments, gathering requirements, or developing a roadmap for future enhancements or releases. While plateaus can be a temporary slowdown in the system development process, they can also provide opportunities for reflection, evaluation, and strategic decision-making. During this phase, system engineers and stakeholders can assess the current state of the system, address any outstanding issu…

Plateau
type: Form

Platform Change Time
type: LexicalEntry
type: MultiwordExpression
canonical form: Platform Change Time
sense: PLATFORM--CHANGE--TIME lexSense

PLATFORM--CHANGE--TIME lexConcept
type: LexicalConcept
definition: Time for a passenger to move from the planned arrival platform to the new arrival platform

Platform Change Time
type: Form

Platform Change
type: LexicalEntry
type: MultiwordExpression
canonical form: Platform Change
sense: PLATFORM--CHANGE lexSense

PLATFORM--CHANGE lexConcept
type: LexicalConcept
definition: A change in the arrival/ departure platform. E.g., Train 00175 arrival in Bern platform 3 -> Train 00175 arrival in Bern platform 7

Platform Change
type: Form

PM
type: Acronym
type: LexicalEntry
acronym for: PLATFORM--MANAGEMENT label
canonical form: PM

PLATFORM--MANAGEMENT lexConcept
type: LexicalConcept
definition: The platform management manages the computing platform resources and is a part of the Computing Platform software.

Platform Management
type: Form

PM
type: Form

PWITD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: POLARION--WORK--ITEM--OF--TYPE--DEFINITION label
canonical form: PWITD

POLARION--WORK--ITEM--OF--TYPE--DEFINITION lexConcept
type: LexicalConcept
definition: Polarion Work Item of Type Definition

Polarion Work Item of Type Definition
type: Form

PWITD
type: Form

PWITR
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: POLARION--WORK--ITEM--OF--TYPE--REFERENCE label
canonical form: PWITR

POLARION--WORK--ITEM--OF--TYPE--REFERENCE lexConcept
type: LexicalConcept
definition: Polarion Work Item of Type Reference

Polarion Work Item of Type Reference
type: Form

PWITR
type: Form

Portability
type: LexicalEntry
type: Word
canonical form: Portability
sense: PORTABILITY lexSense

PORTABILITY lexConcept
type: LexicalConcept
definition: Function by considering the ability for one function to be ported from one technology to another technology. The property that allows migrating a software from one concrete computing platform implementation to another concrete computing platform implementation.

Portability
type: Form

PR
type: Acronym
type: LexicalEntry
acronym for: POSITION--REPORT label
canonical form: PR

POSITION--REPORT lexConcept
type: LexicalConcept
definition: {comment:131}The "Position Report" (PR) is a structured message sent from the train’s On-board (OBU) to the trackside CCS such as the RBC). This report communicates the current position of the train, including its precise location, direction, speed, and other relevant status information. The Position Report allows the trackside system to continuously track the train’s progress, ensure safety, and allocate new movement authorities accordingly. Position Reports are fundamental to ETCS because they enable accurate, real-time management of train movements without relying on trackside detection equipment.

Position Report
type: Form

PR
type: Form

PMAT
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: PRAMSS--MANAGEMENT--AND--ASSURANCE--TEAM label
canonical form: PMAT

PRAMSS--MANAGEMENT--AND--ASSURANCE--TEAM lexConcept
type: LexicalConcept
definition: PRAMSS Management & Assurance Team

PRAMSS Management & Assurance Team
type: Form

PMAT
type: Form

PRAMS
type: LexicalEntry
type: Word
canonical form: PRAMS
sense: PRAMS lexSense

PRAMS lexConcept
type: LexicalConcept
definition: Performance, reliability, availability, maintainability, safety

PRAMS
type: Form

Presentation Logic
type: LexicalEntry
type: MultiwordExpression
canonical form: Presentation Logic
sense: PRESENTATION--LOGIC lexSense

PRESENTATION--LOGIC lexConcept
type: LexicalConcept
definition: The presentation logic controls the flow (dialogue sequence) and layout elements of the User interface using system specific layouts based on generic layout elements. The presentation logic may also include data validation

PRESENTATION--LOGIC lexConcept 2
type: LexicalConcept
definition: The presentation logic controls the flow (dialogue sequence) and layout elements of the User interface using system specific layouts based on generic layout elements. The presentation logic may also include data validation

PRESENTATION--LOGIC lexConcept 3
type: LexicalConcept
definition: The presentation logic controls the flow (dialogue sequence) and layout elements of the User interface using system specific layouts based on generic layout elements. The presentation logic may also include data validation

PRESENTATION--LOGIC lexConcept 4
type: LexicalConcept
definition: The presentation logic controls the flow (dialogue sequence) and layout elements of the User interface using system specific layouts based on generic layout elements. The presentation logic may also include data validation

PRESENTATION--LOGIC lexConcept 5
type: LexicalConcept
definition: The presentation logic controls the flow (dialogue sequence) and layout elements of the User interface using system specific layouts based on generic layout elements. The presentation logic may also include data validation

Presentation Logic
type: Form

Procedure
type: LexicalEntry
type: Word
canonical form: Procedure
sense: PROCEDURE lexSense

PROCEDURE lexConcept
type: LexicalConcept
definition: A procedure is a set of instructions for completing a single task or activity within a process. A process is a series of tasks/activities that produce an outcome. In other words, a procedure is the execution of a pre-defined process by means of pre-defined rules.

Procedure
type: Form

Process Framework
type: LexicalEntry
type: MultiwordExpression
canonical form: Process Framework
sense: PROCESS--FRAMEWORK lexSense

PROCESS--FRAMEWORK lexConcept
type: LexicalConcept
definition: A process framework refers to a structured and systematic approach for designing, documenting, and managing processes within an organisation for a defined scope.{comment:402}

Process Framework
type: Form

Process Task
type: LexicalEntry
type: MultiwordExpression
canonical form: Process Task
sense: PROCESS--TASK lexSense

PROCESS--TASK lexConcept
type: LexicalConcept
definition: An atomic activity that is included within a process. It is used when the work in the Process is not broken down to a finer level of Process detail. Action intended to contribute to the achievement of one or more outcomes of a process.

Process Task
type: Form

Process-System harmonisation dependency
type: LexicalEntry
type: MultiwordExpression
canonical form: Process-System harmonisation dependency
sense: PROCESS-SYSTEM--HARMONISATION--DEPENDENCY lexSense

PROCESS-SYSTEM--HARMONISATION--DEPENDENCY lexConcept
type: LexicalConcept
definition: The process-system harmonisation dependency decribes the fact, that in the highly automated CCS processes, which form a mixed sequence of actor actions and system function activation, the integration of a single not harmonized process action or a single not harmonized functional system behaiour already leads to a non harmonized system behaviour demanding for non harmonized operational process steps. Or in other words: A specific process depends on a specific system functionality and vice versa. Therefore harmonising one side in a specific way is only possible by harmonising the other side in a specific way. (image: 2-diagram_20240622-2035.38937.mxg.svg)

Process-System harmonisation dependency
type: Form

Process
type: LexicalEntry
type: Word
canonical form: Process
sense: PROCESS lexSense

PROCESS lexConcept
type: LexicalConcept
definition: 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.

Process
type: Form

PdM
type: Acronym
type: LexicalEntry
acronym for: PRODUCT--DATA--MANAGEMENT label
canonical form: PdM

PRODUCT--DATA--MANAGEMENT lexConcept
type: LexicalConcept
definition: Product data management (PDM) is the name of a business function within product lifecycle management (PLM) that denotes the management and publication of product data.[1] In software engineering, this is known as version control. The goals of product data management include ensuring all stakeholders share a common understanding, that confusion during the execution of the processes is minimized, and that the highest standards of quality controls are maintained. PDM should not be confused with product information management (PIM).

Product data Management
type: Form

PdM
type: Form

Production view
type: LexicalEntry
type: MultiwordExpression
canonical form: Production view
sense: PRODUCTION--VIEW lexSense

PRODUCTION--VIEW lexConcept
type: LexicalConcept
definition: The production view is an information model that is restricted to the needs of a given use case. It is designed to allow data delivery to consumers using a given technology.

Production view
type: Form

PROD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: PRODUCTION label
canonical form: PROD

PRODUCTION lexConcept
type: LexicalConcept
definition: Production

Production
type: Form

PROD
type: Form

Prognostics
type: LexicalEntry
type: Word
canonical form: Prognostics
sense: PROGNOSTICS lexSense

PROGNOSTICS lexConcept
type: LexicalConcept
definition: {comment:7} {comment:53}is the ability to predict an impeding failure of a system based on the current system conditions [ISBN-13: ‎978-0849398797]. Prognosis technologies typically use measured or inferred features, as well as data-driven and/or physics-based models, to predict the condition of the system at some future time [DOI: 10.1002/9780470117842].

Prognostics
type: Form

PMO
type: Acronym
type: LexicalEntry
acronym for: PROJECT--MANAGEMENT--OFFICE label
canonical form: PMO

PROJECT--MANAGEMENT--OFFICE lexConcept
type: LexicalConcept
definition: Project Management Office

Project Management Office
type: Form

PMO
type: Form

Project Milestone.
type: LexicalEntry
type: MultiwordExpression
canonical form: Project Milestone.
sense: PROJECT--MILESTONE lexSense

PROJECT--MILESTONE lexConcept
type: LexicalConcept
definition: The planning hierarchy is Release>Project Milestone>Work Package>Task

Project Milestone.
type: Form

Properties Topology
type: LexicalEntry
type: MultiwordExpression
canonical form: Properties Topology
sense: PROPERTIES--TOPOLOGY lexSense

PROPERTIES--TOPOLOGY lexConcept
type: LexicalConcept
definition: The 'Properties Topology' is part of railway infrastructure and defines different properties for a section of track like speed limit, traction system etc.

Properties Topology
type: Form

QoS - Quality of Service
type: LexicalEntry
type: MultiwordExpression
canonical form: QoS - Quality of Service
sense: QOS-----QUALITY--OF--SERVICE lexSense

QOS-----QUALITY--OF--SERVICE lexConcept
type: LexicalConcept
definition: QoS - Quality of Service

QoS - Quality of Service
type: Form

QA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: QUALITY--AND--ASSURANCE label
canonical form: QA

QUALITY--AND--ASSURANCE lexConcept
type: LexicalConcept
definition: Quality and Assurance

Quality and Assurance
type: Form

QA
type: Form

Quality attribute
type: LexicalEntry
type: MultiwordExpression
canonical form: Quality attribute
sense: QUALITY--ATTRIBUTE lexSense

QUALITY--ATTRIBUTE lexConcept
type: LexicalConcept
definition: Quality attribute is a realized non-functional requirement used to evaluate the performance of a system

Quality attribute
type: Form

Quality
type: LexicalEntry
type: Word
canonical form: Quality
sense: QUALITY lexSense

QUALITY lexConcept
type: LexicalConcept
definition: Within the scope of the System Pillar, quality is the act of assuring compliance to established procedures, standards, requirements, rules and/or guidelines. In essence, it is the act of complying with the workflow decided and established by EET with support and feedbacks from System/Pillar tasks/domains. As a result, the term quality by itself holds no significance within the scope of this plan; it gains meaning only when associated with governing conventions and procedures.

Quality
type: Form

Question.
type: LexicalEntry
type: Word
canonical form: Question.
sense: QUESTION lexSense

QUESTION lexConcept
type: LexicalConcept
definition: Entry in a FAQ or Q&A list. Description holds answer. If there are many answers then workitems of type "Answer" can be linked.

Question.
type: Form

Quick Brake Release -
type: LexicalEntry
type: MultiwordExpression
canonical form: Quick Brake Release -
sense: QUICK--BRAKE--RELEASE lexSense

QUICK--BRAKE--RELEASE lexConcept
type: LexicalConcept
definition: Quick Brake Release -

Quick Brake Release -
type: Form

RAT
type: Acronym
type: LexicalEntry
acronym for: RADIO--ACCESS--TECHNOLOGY label
canonical form: RAT

RADIO--ACCESS--TECHNOLOGY lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Radio Access Technology

Radio Access Technology
type: Form

RAT
type: Form

RBC
type: Acronym
type: LexicalEntry
acronym for: RADIO--BLOCK--CENTRE label
canonical form: RBC

RADIO--BLOCK--CENTRE lexConcept
type: LexicalConcept
definition: Radio Block Centre is a computer-based system that elaborates messages to be sent to the train on basis of information received from external trackside systems and on basis of information exchanged with the on-board subsystems. The main objective of these messages is to provide movement authorities to allow the safe movement of trains on the Railway infrastructure area under the responsibility of the RBC. The interoperability requirements for the RBC are mainly related to the data exchange between the RBC and the on-board subsystem. (subset26-2)

RADIO--BLOCK--CENTRE lexConcept 2
type: LexicalConcept
definition: Radio Block Centre is a computer-based system that elaborates messages to be sent to the train on basis of information received from external trackside systems and on basis of information exchanged with the on-board subsystems. The main objective of these messages is to provide movement authorities to allow the safe movement of trains on the Railway infrastructure area under the responsibility of the RBC. The interoperability requirements for the RBC are mainly related to the data exchange between the RBC and the on-board subsystem. (subset26-2)

Radio Block Centre
type: Form

RBC
type: Form

RBC
type: Form

RC
type: Acronym
type: LexicalEntry
acronym for: RADIO--CONNECTION label
canonical form: RC

RADIO--CONNECTION lexConcept
type: LexicalConcept
definition: Often referred in the specifications as "safe radio connection" or "safe connection" is the connection between an On-board and an RBC and its management is contained in the EURORADIO specifications. The indication statuses of the safe radio connection are: “No Connection”, “Connection Lost/Set-Up failed”, “Connection Up”. The national/default values for the supervision of the safe radio connection are T_NVCONTACT and M_NVCONTACT. Note that it is a different concept to SPP-28486 - Missing cross-reference.{comment:154}

Radio Connection
type: Form

RC
type: Form

RFID
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: RADIO--FREQUENCY--IDENTIFICATION label
canonical form: RFID

RADIO--FREQUENCY--IDENTIFICATION lexConcept
type: LexicalConcept
definition: Radio Frequency Identification

Radio Frequency Identification
type: Form

RFID
type: Form

RCM-DX
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: RAIL--CONDITION--MONITORING-----DATA--EXCHANGE label
canonical form: RCM-DX

RAIL--CONDITION--MONITORING-----DATA--EXCHANGE lexConcept
type: LexicalConcept
definition: Rail Condition Monitoring – Data Exchange

Rail Condition Monitoring – Data Exchange
type: Form

RCM-DX
type: Form

RIM
type: Acronym
type: LexicalEntry
acronym for: RAIL--INFRASTRUCTURE--MANAGER label
canonical form: RIM

RAIL--INFRASTRUCTURE--MANAGER lexConcept
type: LexicalConcept
definition: Rail Infrastructure Manager

Rail Infrastructure Manager
type: Form

RIM
type: Form

RNE
type: Acronym
type: LexicalEntry
acronym for: RAIL--NET--EUROPE label
canonical form: RNE

RAIL--NET--EUROPE lexConcept
type: LexicalConcept
definition: Rail Net Europe

Rail Net Europe
type: Form

RNE
type: Form

ROC
type: Acronym
type: LexicalEntry
acronym for: RAIL--OPERATING--COMPANY label
canonical form: ROC

RAIL--OPERATING--COMPANY lexConcept
type: LexicalConcept
definition: Rail Operating Company

Rail Operating Company
type: Form

ROC
type: Form

RASCOP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: RAIL--STANDARDISATION--COORDINATION--PLATFORM--FOR--EUROPE label
canonical form: RASCOP

RAIL--STANDARDISATION--COORDINATION--PLATFORM--FOR--EUROPE lexConcept
type: LexicalConcept
definition: Rail Standardisation Coordination Platform for Europe

Rail Standardisation Coordination Platform for Europe
type: Form

RASCOP
type: Form

RU
type: Acronym
type: LexicalEntry
acronym for: RAIL--UNDERTAKINGS label
canonical form: RU

RAIL--UNDERTAKINGS lexConcept
type: LexicalConcept
definition: Rail Undertakings

Rail Undertakings
type: Form

RU
type: Form

RNE TIS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: RAILNETEUROPE--TRAIN--INFORMATION--SYSTEM label
canonical form: RNE TIS

RAILNETEUROPE--TRAIN--INFORMATION--SYSTEM lexConcept
type: LexicalConcept
definition: RailNetEurope Train Information System

RailNetEurope Train Information System
type: Form

RNE TIS
type: Form

Railway Infrastructure
type: LexicalEntry
type: MultiwordExpression
canonical form: Railway Infrastructure
sense: RAILWAY--INFRASTRUCTURE lexSense

RAILWAY--INFRASTRUCTURE lexConcept
type: LexicalConcept
definition: Railway infrastructure means the items listed in Annex I [of DIRECTIVE 2012/34/EU OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 21 November 2012 establishing a single European railway area (recast)

Railway Infrastructure
type: Form

RMR
type: Acronym
type: LexicalEntry
acronym for: RAILWAY--MOBILE--RADIO label
canonical form: RMR

RAILWAY--MOBILE--RADIO lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Railway Mobile Radio

Railway Mobile Radio
type: Form

RMR
type: Form

Railway Requirement
type: LexicalEntry
type: MultiwordExpression
canonical form: Railway Requirement
sense: RAILWAY--REQUIREMENT lexSense

RAILWAY--REQUIREMENT lexConcept
type: LexicalConcept
definition: 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 Requirement
type: Form

RU
type: Acronym
type: LexicalEntry
acronym for: RAILWAY--UNDERTAKING label
canonical form: RU

RAILWAY--UNDERTAKING lexConcept
type: LexicalConcept
definition: 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;

RAILWAY--UNDERTAKING lexConcept 2
type: LexicalConcept
definition: Railway Undertaking

Railway Undertaking
type: Form

RU
type: Form

railway vehicle
type: LexicalEntry
type: MultiwordExpression
canonical form: railway vehicle
sense: RAILWAY--VEHICLE lexSense

RAILWAY--VEHICLE lexConcept
type: LexicalConcept
definition: A single item suitable for circulation on wheels on railway lines, e.g., wagon or traction unit

railway vehicle
type: Form

Railway
type: LexicalEntry
type: Word
canonical form: Railway
sense: RAILWAY lexSense

RAILWAY lexConcept
type: LexicalConcept
definition: The term "railway" is used to represent railway infrastructure managers, railway undertakings, vehicle owners and all other possible combinations of the rolling stock and infrastructure owning and operating companies.

Railway
type: Form

RAM
type: Acronym
type: LexicalEntry
acronym for: RANDOM--ACCESS--MEMORY label
canonical form: RAM

RANDOM--ACCESS--MEMORY lexConcept
type: LexicalConcept
definition: Random Access Memory

Random Access Memory
type: Form

RAM
type: Form

RIMS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: RANGING--AND--INTEGRITY--MONITORING--STATIONS label
canonical form: RIMS

RANGING--AND--INTEGRITY--MONITORING--STATIONS lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Ranging and Integrity Monitoring Stations

Ranging and Integrity Monitoring Stations
type: Form

RIMS
type: Form

Rationale.
type: LexicalEntry
type: Word
canonical form: Rationale.
sense: RATIONALE lexSense

RATIONALE lexConcept
type: LexicalConcept
definition: Reasons why another workitem WAS designed this way

Rationale.
type: Form

RBD
type: LexicalEntry
type: Word
canonical form: RBD
sense: RBD lexSense

RBD lexConcept
type: LexicalConcept
definition: reliability block diagram logical, graphical representation of a system showing how reliability of its sub items (represented by blocks) and combinations thereof, affect reliability of the system [SOURCE: IEC 60050-192:2015, 192-11-03]

RBD lexConcept 2
type: LexicalConcept
definition: A Reliability Block Diagram (RBD) is a graphical representation of the successful operation of a system. It shows the logical connection of the (functional) components (represented by blocks), which is required for the successful operation of the system. Consequently, an RBD is equivalent to a logical equation of Boolean variables and the probability calculations primarily refer to constant values of the success/failure probabilities of a block.

RBD
type: Form

Reaction Time
type: LexicalEntry
type: MultiwordExpression
canonical form: Reaction Time
sense: REACTION--TIME lexSense

REACTION--TIME lexConcept
type: LexicalConcept
definition: In semi automatic conflict solution, the Dispatcher can decline the executed dispatching measure and override it

Reaction Time
type: Form

Reader Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Reader Controller
sense: READER--CONTROLLER lexSense

READER--CONTROLLER lexConcept
type: LexicalConcept
definition: The Reader Controller manages states and failures of the Biometric Reader and/or the RFID Reader.

READER--CONTROLLER lexConcept 2
type: LexicalConcept
definition: The Reader Controller manages states and failures of the Biometric Reader and/or the RFID Reader.

READER--CONTROLLER lexConcept 3
type: LexicalConcept
definition: The Reader Controller manages states and failures of the Biometric Reader and/or the RFID Reader.

READER--CONTROLLER lexConcept 4
type: LexicalConcept
definition: The Reader Controller manages states and failures of the Biometric Reader and/or the RFID Reader.

READER--CONTROLLER lexConcept 5
type: LexicalConcept
definition: The Reader Controller manages states and failures of the Biometric Reader and/or the RFID Reader.

READER--CONTROLLER lexConcept 6
type: LexicalConcept
definition: The Reader Controller manages states and failures of the Biometric Reader and/or the RFID Reader.

READER--CONTROLLER lexConcept 7
type: LexicalConcept
definition: The Reader Controller manages states and failures of the Biometric Readerand/or the RFID Reader.

READER--CONTROLLER lexConcept 8
type: LexicalConcept
definition: Reader Controller The Reader Controller manages states and failures of the Biometric Readerand/or the RFID Reader.

Reader Controller
type: Form

RT
type: Acronym
type: LexicalEntry
acronym for: REAL--TIME label
canonical form: RT

REAL--TIME lexConcept
type: LexicalConcept
definition: Real Time

Real Time
type: Form

RT
type: Form

Real-Time Conflict Detection
type: LexicalEntry
type: MultiwordExpression
canonical form: Real-Time Conflict Detection
sense: REAL-TIME--CONFLICT--DETECTION lexSense

REAL-TIME--CONFLICT--DETECTION lexConcept
type: LexicalConcept
definition: Determine the difference between the operational plan and the forecast. Conflicts predicted to occur in the future but may be solved before they happen. Conflicts arise from the impact of deviations.

Real-Time Conflict Detection
type: Form

Rearview system
type: LexicalEntry
type: MultiwordExpression
canonical form: Rearview system
sense: REARVIEW--SYSTEM lexSense

REARVIEW--SYSTEM lexConcept
type: LexicalConcept
definition: The Rearview system permits to see the states of the doors at standstill. The ergonomics of this system is supplier specific; no norm or standard specify it. Two displays are used for the rearview system. Two options exist for the position of the displays : one on the left side of the cab and the other on the right side of the cab (left doors vs. right doors), or the two displays side by side on the left or on the right side of the cab. The SIL associated to this system is SIL0 (Basic Integrity). Images from cameras are only displayed at standstill. Current communication between Rearview system and its displays is supplier specific. To facilitate the deployment of the MDS solution, a migration to a generic communication used also by other systems should be considered.

REARVIEW--SYSTEM lexConcept 2
type: LexicalConcept
definition: The Rearview system permits to see the states of the doors at standstill. The ergonomics of this system is supplierspecific; no norm or standard specify it. Two displays are used for the rearview system. Two options exist for the position of the displays : one on the left side ofthe cab and the other on the right side of the cab (left doors vs. right doors), or the two displays side by side on the left or on the right side of the cab. The SIL associated to this system is SIL0 (Basic Integrity). Images from cameras are only displayed at standstill. Current communication between Rearview system and its displays is supplier specific. To facilitate the deployment of the MDS solution, a migration to a generic communication used also by other systems should be considered.

Rearview system
type: Form

RAID
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: REDUNDANT--ARRAY--OF--INDEPENDENT--DISKS label
canonical form: RAID

REDUNDANT--ARRAY--OF--INDEPENDENT--DISKS lexConcept
type: LexicalConcept
definition: Redundant Array of Independent Disks

Redundant Array of Independent Disks
type: Form

RAID
type: Form

Ref. Loc.
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: REFERENCE--LOCATION label
canonical form: Ref. Loc.

REFERENCE--LOCATION lexConcept
type: LexicalConcept
definition: The reference location on the track which the train based distance reading refers to. It is used as a common location reference between the ERTMS/ETCS on-board and trackside equipment (according to the "Reference Location" definition in SUBSET-023, TSI 2023).

Reference Location
type: Form

Ref. Loc.
type: Form

Reference.
type: LexicalEntry
type: Word
canonical form: Reference.
sense: REFERENCE lexSense

REFERENCE lexConcept
type: LexicalConcept
definition: Hyperlink and/or copy of an external document. See: References

Reference.
type: Form

Refering document
type: LexicalEntry
type: MultiwordExpression
canonical form: Refering document
sense: REFERING--DOCUMENT lexSense

REFERING--DOCUMENT lexConcept
type: LexicalConcept
definition: any system pillar document, but for glossaries, written by a document author or read by a document reader. The document contains System Pillar Work-items, but for definitions and concepts. The export of a document may contain a table of definitions generated out of the definitions refered to in the document.

Refering document
type: Form

RTCC
type: Acronym
type: LexicalEntry
acronym for: REGIONAL--TRAFFIC--CONTROL--CENTRE label
canonical form: RTCC

REGIONAL--TRAFFIC--CONTROL--CENTRE lexConcept
type: LexicalConcept
definition: Regional traffic control centre

Regional traffic control centre
type: Form

RTCC
type: Form

RINF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: REGISTER--OF--INFRASTRUCTURE label
canonical form: RINF

REGISTER--OF--INFRASTRUCTURE lexConcept
type: LexicalConcept
definition: The Register of Infrastructure. (RINF) comprehensively describes the static rail network characteristics and capabilities. It contains network parameters for each subsystem or part subsystem.

REGISTER--OF--INFRASTRUCTURE lexConcept 2
type: LexicalConcept
definition: The Register of Infrastructure comprehensively describes the static rail network characteristics and capabilities. It contains network parameters for each subsystem or part subsystem.

REGISTER--OF--INFRASTRUCTURE lexConcept 3
type: LexicalConcept
definition: The Register of Infrastructure. (RINF) comprehensively describes the static rail network characteristics and capabilities. It contains network parameters for each subsystem or part subsystem.

Register of Infrastructure
type: Form

RINF
type: Form

RINF
type: Form

RINF
type: Form

RINF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: REGISTERS--OF--INFRASTRUCTURE label
canonical form: RINF

REGISTERS--OF--INFRASTRUCTURE lexConcept
type: LexicalConcept
definition: Registers of Infrastructure

Registers of Infrastructure
type: Form

RINF
type: Form

RA
type: Acronym
type: LexicalEntry
acronym for: REGISTRATION--AUTHORITY label
canonical form: RA

REGISTRATION--AUTHORITY lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Registration Authority

Registration Authority
type: Form

RA
type: Form

Regulatory authorities
type: LexicalEntry
type: MultiwordExpression
canonical form: Regulatory authorities
sense: REGULATORY--AUTHORITIES lexSense

REGULATORY--AUTHORITIES lexConcept
type: LexicalConcept
definition: Under European Union legislation, each Regulatory Body (RB) has the task to oversee the application of Community rules and act as an appeal body in case of disputes. DIRECTIVE 2012/34/EU, Article 55: 'Each Member State shall establish a single national regulatory body for the railway sector. Without prejudice to paragraph 2, this body shall be a stand-alone authority which is, in organizational, functional, hierarchical and decision- making terms, legally distinct and independent from any other public or private entity. It shall also be independent in its organization, funding decisions, legal structure and decision- making from any infrastructure manager, charging body, allocation body or applicant. It shall furthermore be functionally independent from any competent authority involved in the award of a public service contract.' Thus it shall ensure that charges set by the Infrastructure Manager comply with Chapter II of 2001/14/EU and are non-discriminatory. The RB oversees negotiations between applicants and the IM and intervenes when the requirements of 2001/14 are likely to be contravened. Applicants have the right to appeal to the RB if they believe that they have been unfairly treated, discriminated against or are in any other way aggrieved. In particular, they may appeal against decisions adopted by the IM (or where appropriate the Railway Undertaking) concerning: a) the network statement; b) criteria contained within it; c) the allocation process and its outcome; d) the charging scheme; e) level or structure of infrastructure fees which it is, or may be, required to pay; f) arrangements for access.

Regulatory authorities
type: Form

Relative position
type: LexicalEntry
type: MultiwordExpression
canonical form: Relative position
sense: RELATIVE--POSITION lexSense

RELATIVE--POSITION lexConcept
type: LexicalConcept
definition: The Train front end position expressed with a distance from a reference location in a 1D reference frame.

Relative position
type: Form

Release.
type: LexicalEntry
type: Word
canonical form: Release.
sense: RELEASE lexSense

RELEASE lexConcept
type: LexicalConcept
definition: A package of documents (polarion collection) released by a domain at a certain time

Release.
type: Form

reliability, <of an item>
type: LexicalEntry
type: MultiwordExpression
canonical form: reliability, <of an item>
sense: RELIABILITY--<OF--AN--ITEM> lexSense

RELIABILITY--<OF--AN--ITEM> lexConcept
type: LexicalConcept
definition: Ability to perform as required, without failure, for a given time interval, under given conditions. Note 1 to entry: The time interval duration can be expressed in units appropriate to the item concerned, e.g. calendar time, operating cycles, distance run, etc. Note 2 to entry: Given conditions include aspects that affect reliability, such as: mode of operation, stress levels, environmental conditions, and maintenance. Note 3 to entry: Reliability can be quantified using measures defined in Section 192-05, Reliability related concepts: measures. [SOURCE: IEC 60050-192:2015, 192-01-24] Source: SPPRAMSS-349 - [EN 50126-1:2017]

reliability, <of an item>
type: Form

RAMS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: RELIABILITY--AVAILABILITY--MAINTAINABILITY--AND--SAFETY label
canonical form: RAMS

RELIABILITY--AVAILABILITY--MAINTAINABILITY--AND--SAFETY lexConcept
type: LexicalConcept
definition: Reliability, Availability, Maintainability and Safety

Reliability, Availability, Maintainability and Safety
type: Form

RAMS
type: Form

RCM
type: Acronym
type: LexicalEntry
acronym for: RELIABILITY--CENTRED--MAINTENANCE label
canonical form: RCM

RELIABILITY--CENTRED--MAINTENANCE lexConcept
type: LexicalConcept
definition: 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.

Reliability Centred Maintenance
type: Form

RCM
type: Form

Reliable Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Reliable Data
sense: RELIABLE--DATA lexSense

RELIABLE--DATA lexConcept
type: LexicalConcept
definition: Reliable Data refers to a typical characteristic of data which satisfies the qualities of being trustworthy/low probability of incorrect information/low fault rate of the information, current (not obsolete), complete, and accurate. The attribute “reliable” is not limited or coupled exclusively to safety-related functions since a sufficient level of quality is also required to guarantee a good performance, high availability, and reliability of non-safe functions such as realised by ATO or TMS. Hence, the data quality attribute ‘Reliable’ means safety-related or non-safety-related data that satisfies the Consuming System’s data quality requirements.

Reliable Data
type: Form

Remaining Dwell Time
type: LexicalEntry
type: MultiwordExpression
canonical form: Remaining Dwell Time
sense: REMAINING--DWELL--TIME lexSense

REMAINING--DWELL--TIME lexConcept
type: LexicalConcept
definition: The amount of time left before a train resume moving.

Remaining Dwell Time
type: Form

Remote Control Device
type: LexicalEntry
type: MultiwordExpression
canonical form: Remote Control Device
sense: REMOTE--CONTROL--DEVICE lexSense

REMOTE--CONTROL--DEVICE lexConcept
type: LexicalConcept
definition: 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
type: Form

RTO
type: Acronym
type: LexicalEntry
acronym for: REMOTE--TRAIN--OPERATIONS label
canonical form: RTO

REMOTE--TRAIN--OPERATIONS lexConcept
type: LexicalConcept
definition: Remote Train Operations

Remote Train Operations
type: Form

RTO
type: Form

Remote Train Operation
type: LexicalEntry
type: MultiwordExpression
canonical form: Remote Train Operation
sense: REMOTE--TRAIN--OPERATION lexSense

REMOTE--TRAIN--OPERATION lexConcept
type: LexicalConcept
definition: The Remote Train Operation (RTO) system is an operational entity. It provides the status of the train in terms of remote driving: stand-alone, monitored, observed and controlled. Depending on this status, the MDS can change the active configuration of the cab displays. In addition to provide input to the MDS, the RTO may require a specific view on a display. If so, the interface between the RTO and the MDS will be the same as for the other systems described below.

REMOTE--TRAIN--OPERATION lexConcept 2
type: LexicalConcept
definition: The Remote Train Operation (RTO) system is an operational entity. It provides the status of the train in terms of remote driving: stand-alone, monitored, observed and controlled. Depending on this status, the MDS can change the active configuration of the cab displays. In addition to provide input to the MDS, the RTO may require a specific view on a display. If so, the interface between the RTO and the MDS will be the same as for the other systems described below.

Remote Train Operation
type: Form

Renewal
type: LexicalEntry
type: Word
canonical form: Renewal
sense: RENEWAL lexSense

RENEWAL lexConcept
type: LexicalConcept
definition: Renewal means any major substitution work on a subsystem or part of it which does not change the overall performance of the subsystem;

Renewal
type: Form

REP - Repository
type: LexicalEntry
type: MultiwordExpression
canonical form: REP - Repository
sense: REP-----REPOSITORY lexSense

REP-----REPOSITORY lexConcept
type: LexicalConcept
definition: REP - Repository

REP - Repository
type: Form

REP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: REPLICA label
canonical form: REP

REPLICA lexConcept
type: LexicalConcept
definition: 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.

Replica
type: Form

REP
type: Form

REST
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: REPRESENTATIONAL--STATE--TRANSFER label
canonical form: REST

REPRESENTATIONAL--STATE--TRANSFER lexConcept
type: LexicalConcept
definition: Representational State Transfer

Representational State Transfer
type: Form

REST
type: Form

Request
type: LexicalEntry
type: Word
canonical form: Request
sense: REQUEST lexSense

REQUEST lexConcept
type: LexicalConcept
definition: A Request on the SCI-CMD or SCI-SCMD{comment:1276} interface is a message from a client to ETPS which asks ETPS for a certain task. ETPS will perform a number of safety checks and if at least one fails, the Request is rejected, otherwise it is granted and executed.

Request
type: Form

Requirement set
type: LexicalEntry
type: MultiwordExpression
canonical form: Requirement set
sense: REQUIREMENT--SET lexSense

REQUIREMENT--SET lexConcept
type: LexicalConcept
definition: A requirement set can contain all relevant requirements for a given entity (enterprise/operational entity/system/subsystem). Usually this is captured in a requirements document and/or a baseline in a database.

Requirement set
type: Form

Requirement
type: LexicalEntry
type: Word
canonical form: Requirement
sense: REQUIREMENT lexSense

REQUIREMENT lexConcept
type: LexicalConcept
definition: A requirement is the result of a formal transformation of one or more needs or parent requirements into an agreed-to obligation for an entity to perform some function or possess some characteristic within specified constraints with acceptable risk. They are written as formal textual “shall” statements in a structured, natural language what an entity must achieve.

Requirement
type: Form

Restriction of use
type: LexicalEntry
type: MultiwordExpression
canonical form: Restriction of use
sense: RESTRICTION--OF--USE lexSense

RESTRICTION--OF--USE lexConcept
type: LexicalConcept
definition: feature/function proposed by the system which is not available AND which has no...feature/function proposed by the system which is not available AND which has no solution/procedure that can bypass. Restrictions are related to open CRs, which often should be "translated" in an understandable manner for the customer (baseline user), and sometimes form an operational point of view, testing point of view etc...

Restriction of use
type: Form

Retrofit
type: LexicalEntry
type: Word
canonical form: Retrofit
sense: RETROFIT lexSense

RETROFIT lexConcept
type: LexicalConcept
definition: Addition of new technology or features to older systems. For trains it could be adding an ETCS onboard unit to a class B equipped train.

Retrofit
type: Form

Reusability
type: LexicalEntry
type: Word
canonical form: Reusability
sense: REUSABILITY lexSense

REUSABILITY lexConcept
type: LexicalConcept
definition: The property of a sub-system to be integrated without any modification inside various CCS possibly deployed in different operation contexts. This is related to "cross acceptance" as defined in [EN50129]:{comment:1336} 3.1.7. {comment:1298}

Reusability
type: Form

RFID Reader
type: LexicalEntry
type: MultiwordExpression
canonical form: RFID Reader
sense: RFID--READER lexSense

RFID--READER lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: 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 lexConcept 3
type: LexicalConcept
definition: 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 lexConcept 4
type: LexicalConcept
definition: 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 lexConcept 5
type: LexicalConcept
definition: 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 lexConcept 6
type: LexicalConcept
definition: 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 lexConcept 7
type: LexicalConcept
definition: 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 lexConcept 8
type: LexicalConcept
definition: 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.

RFID Reader
type: Form

risk, <of a hazard>
type: LexicalEntry
type: MultiwordExpression
canonical form: risk, <of a hazard>
sense: RISK--<OF--A--HAZARD> lexSense

RISK--<OF--A--HAZARD> lexConcept
type: LexicalConcept
definition: combination of the probability of occurrence of accident and the severity of that accident Note 1 to entry: In French, the term “risque” also denotes the potential source of harm, in English “hazard” (see 903-01-02) SPPRAMSS-4044 - Hazard . [SOURCE: IEC 60050-903:2013, 903-01-07, modified — <of a hazard> has been added and "harm" has been replaced with "accident"]

risk, <of a hazard>
type: Form

risk analysis
type: LexicalEntry
type: MultiwordExpression
canonical form: risk analysis
sense: RISK--ANALYSIS lexSense

RISK--ANALYSIS lexConcept
type: LexicalConcept
definition: systematic use of available information to identify hazards and to estimate the risk [Source: IEC 60050-903:2013, 903-01-08]

risk analysis
type: Form

risk assessment
type: LexicalEntry
type: MultiwordExpression
canonical form: risk assessment
sense: RISK--ASSESSMENT lexSense

RISK--ASSESSMENT lexConcept
type: LexicalConcept
definition: overall process comprising a risk analysis and a risk evaluation [Source: IEC 60050-903:2013, 903-01-10]

risk assessment
type: Form

Risk Buffer
type: LexicalEntry
type: MultiwordExpression
canonical form: Risk Buffer
sense: RISK--BUFFER lexSense

RISK--BUFFER lexConcept
type: LexicalConcept
definition: The Risk Buffer is a linear contiguous stretch of track that serves as the overrun protection to avoid an accident e.g. if the train brakes do not perform as well as expected and as a safety buffer in the event of a rollback of a chased train. It is part of a Movement Permission. A Risk Buffer exists if there is a Danger Point or project-specific safety margin greater than zero.

Risk Buffer
type: Form

risk evaluation
type: LexicalEntry
type: MultiwordExpression
canonical form: risk evaluation
sense: RISK--EVALUATION lexSense

RISK--EVALUATION lexConcept
type: LexicalConcept
definition: procedure based on the risk analysis to determine whether the tolerable risk has been achieved [Source: IEC 60050-903:2013, 903-01-09]

risk evaluation
type: Form

Risk Path
type: LexicalEntry
type: MultiwordExpression
canonical form: Risk Path
sense: RISK--PATH lexSense

RISK--PATH lexConcept
type: LexicalConcept
definition: A Risk Path is one potential path (a linear contiguous stretch of track) by which a non-permitted vehicle movement could result in a flank collision with a vehicle moving along the Movement Permission Extent. A Movement Permission can contain zero or more Risk Paths.

RISK--PATH lexConcept 2
type: LexicalConcept
definition: The Risk Path is one potential path by which a non-permitted vehicle movement could result in a flank collision with a vehicle moving along the Movement Permission extent. The Risk Path starts at each end of the relevant Fouling Section in the extent of the Movement Permission (including the Risk Buffer, if not opted out by other configuration) and is limited through a sufficient method for providing flank protection. For instance, a Switchable Track Asset or Movement Permission could be used for limiting the Risk Path. The Risk Path is defined as a Contiguous Track Area.

Risk Path
type: Form

Risk.
type: LexicalEntry
type: Word
canonical form: Risk.
sense: RISK lexSense

RISK lexConcept
type: LexicalConcept
definition: Value of damage and mitigation for a hazard.

Risk.
type: Form

RNE Glossary
type: LexicalEntry
type: MultiwordExpression
canonical form: RNE Glossary
sense: RNE--GLOSSARY lexSense

RNE--GLOSSARY lexConcept
type: LexicalConcept
definition: Narrow definition: the maximum number of trains which can be planned to move in both directions over a specified section of track in a 24hour period. General definition: the totality of potential train paths that can be accommodated on a railway line or a network

RNE Glossary
type: Form

Road Traffic (DRAFT)
type: LexicalEntry
type: MultiwordExpression
canonical form: Road Traffic (DRAFT)
sense: ROAD--TRAFFIC--DRAFT lexSense

ROAD--TRAFFIC--DRAFT lexConcept
type: LexicalConcept
definition: Any traffic on a railway track level crossing other than railway traffic.

Road Traffic (DRAFT)
type: Form

Roadmap
type: LexicalEntry
type: Word
canonical form: Roadmap
sense: ROADMAP lexSense

ROADMAP lexConcept
type: LexicalConcept
definition: Visualization of a specific plan

Roadmap
type: Form

RBAS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ROLE--BASED--ACCESS--CONTROL label
canonical form: RBAS

ROLE--BASED--ACCESS--CONTROL lexConcept
type: LexicalConcept
definition: Role Based Access Control

Role Based Access Control
type: Form

RBAS
type: Form

Role
type: LexicalEntry
type: Word
canonical form: Role
sense: ROLE lexSense

ROLE lexConcept
type: LexicalConcept
definition: A role is described by a set of responsibilities. Roles are used to define the responsibilities of tasks, ensuring that individuals or a group of people perform their assign tasks and contribute to their successful execution.

Role
type: Form

Roll Away
type: LexicalEntry
type: MultiwordExpression
canonical form: Roll Away
sense: ROLL--AWAY lexSense

ROLL--AWAY lexConcept
type: LexicalConcept
definition: An unintended and non-powered movement of the train in a direction, which conflicts with the current position of the direction controller in the active desk. Reference: Glossary of Terms and Abbreviation. SUBSET-023. Issue 4.0.0

Roll Away
type: Form

Rolling Stock - Generic term referring to the train subsystem which includes the...
type: LexicalEntry
type: MultiwordExpression
canonical form: Rolling Stock - Generic term referring to the train subsystem which includes the...
sense: ROLLING--STOCK-----GENERIC--TERM--REFERRING--TO--THE--TRAIN--SUBSYSTEM--WHICH--INCLUDES--THE lexSense

ROLLING--STOCK-----GENERIC--TERM--REFERRING--TO--THE--TRAIN--SUBSYSTEM--WHICH--INCLUDES--THE lexConcept
type: LexicalConcept
definition: Rolling Stock - Generic term referring to the train subsystem which includes the propulsion and braking devices. It possibly includes the TCMS subsystem

Rolling Stock - Generic term referring to the train subsystem which includes the...
type: Form

Route Change
type: LexicalEntry
type: MultiwordExpression
canonical form: Route Change
sense: ROUTE--CHANGE lexSense

ROUTE--CHANGE lexConcept
type: LexicalConcept
definition: To change the assigned network of the train, including a change in the assigned stops. E.g., planned journey: Interlaken -> Spiez -> Bern -> Basel ...... New Plan: Spiez -> Zurich -> Basel

Route Change
type: Form

Route in railway operations and CCS
type: LexicalEntry
type: MultiwordExpression
canonical form: Route in railway operations and CCS
sense: ROUTE--IN--RAILWAY--OPERATIONS--AND--CCS lexSense

ROUTE--IN--RAILWAY--OPERATIONS--AND--CCS lexConcept
type: LexicalConcept
definition: A "route" refers in railway operations and the context of Control Command and Signalling (CCS) to a specific path through the railway network that is set or authorised for a train to move from a defined starting point to a defined end point. This path is ensured to be free of conflicting train movements, with all points (switches) and signals set accordingly to allow the train to pass safely. In the CCS context, the route includes: * The successive track sections or blocks * Configured points set and locked for the intended movement * Required flank or protection measures active * All other conflicting movements prevented by interlocking or CCS logic Routes are fundamental to safe train movement and are established by the signalling system before a train is allowed to proceed. This concept of route will be replaced in the target system of SERA by Movement Permission, see here: SPT2TRAFFIC-7866 - Movement Permission{comment:153}

Route in railway operations and CCS
type: Form

RU - Railway Undertaking.
type: LexicalEntry
type: MultiwordExpression
canonical form: RU - Railway Undertaking.
sense: RU-----RAILWAY--UNDERTAKING lexSense

RU-----RAILWAY--UNDERTAKING lexConcept
type: LexicalConcept
definition: RU - Railway Undertaking.

RU - Railway Undertaking.
type: Form

Rule.
type: LexicalEntry
type: Word
canonical form: Rule.
sense: RULE lexSense

RULE lexConcept
type: LexicalConcept
definition: Design principle that shall used in a certain area. Is used to avoid the need of Rationals for every design element.

Rule.
type: Form

RTE
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: RUNTIME--ENVIRONMENT label
canonical form: RTE

RUNTIME--ENVIRONMENT lexConcept
type: LexicalConcept
definition: The Runtime Environment refers to the software needed to provide the services of the Runtime Layer in a single Compartment.

Runtime Environment
type: Form

RTE
type: Form

RL
type: Acronym
type: LexicalEntry
acronym for: RUNTIME--LAYER label
canonical form: RL

RUNTIME--LAYER lexConcept
type: LexicalConcept
definition: The Runtime Layer refers to the system services (e.g., application and computing resource orchestration, monitoring of the Functional Applications and the Application Execution Environment, tracing and logging, communication services that are not related to safety, security means incl. authentication, encryption, key storage, etc.) and the communication stack for information exchange between Functional Applications running on the same Computing Environment and with external entities. It may also include an operating system.

Runtime Layer
type: Form

RL
type: Form

S-Type Train - Vehicles with independently ([s]eparately) controlled dynamic and...
type: LexicalEntry
type: MultiwordExpression
canonical form: S-Type Train - Vehicles with independently ([s]eparately) controlled dynamic and...
sense: S-TYPE--TRAIN-----VEHICLES--WITH--INDEPENDENTLY-- S EPARATELY--CONTROLLED--DYNAMIC--AND lexSense

S-TYPE--TRAIN-----VEHICLES--WITH--INDEPENDENTLY-- S EPARATELY--CONTROLLED--DYNAMIC--AND lexConcept
type: LexicalConcept
definition: S-Type Train - Vehicles with independently ([s]eparately) controlled dynamic and train air brakes as an EN/UIC-brake system in accordance with SPT2ARC-4746 - Missing cross-reference , chapter 5.4. Typically, a locomotive hauling a train consisting of coaches.

S-Type Train - Vehicles with independently ([s]eparately) controlled dynamic and...
type: Form

SCA
type: Acronym
type: LexicalEntry
acronym for: SAFE--CONFIGURATION--AUTHORITY label
canonical form: SCA

SAFE--CONFIGURATION--AUTHORITY lexConcept
type: LexicalConcept
definition: Safe Configuration Authority, see Configuration Update Concept of Transversal.

Safe Configuration Authority
type: Form

SCA
type: Form

safe state [821-12-49]
type: LexicalEntry
type: MultiwordExpression
canonical form: safe state [821-12-49]
sense: SAFE--STATE-- 821-12-49 lexSense

SAFE--STATE-- 821-12-49 lexConcept
type: LexicalConcept
definition: condition which continues to preserve safety [SOURCE: IEC 62425:2007, 3.1.42]

safe state [821-12-49]
type: Form

safe state
type: LexicalEntry
type: MultiwordExpression
canonical form: safe state
sense: SAFE--STATE lexSense

SAFE--STATE lexConcept
type: LexicalConcept
definition: condition which continues to preserve safety [Source: IEC 60050-821, 821-12-49]

SAFE--STATE lexConcept 2
type: LexicalConcept
definition: condition which continues to preserve safety [821-12-49][IEC 62425:2007, 3.1.42]

safe state
type: Form

STE
type: Acronym
type: LexicalEntry
acronym for: SAFE--TRAIN--EXTENT label
canonical form: STE

SAFE--TRAIN--EXTENT lexConcept
type: LexicalConcept
definition: 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

Safe Train Extent
type: Form

STE
type: Form

Safe Train Length Determination
type: LexicalEntry
type: MultiwordExpression
canonical form: Safe Train Length Determination
sense: SAFE--TRAIN--LENGTH--DETERMINATION lexSense

SAFE--TRAIN--LENGTH--DETERMINATION lexConcept
type: LexicalConcept
definition: Function of ETCS Level 3.

Safe Train Length Determination
type: Form

SET
type: Acronym
type: LexicalEntry
acronym for: SAFETY--ENVIRONMENT--TASK label
canonical form: SET

SAFETY--ENVIRONMENT--TASK lexConcept
type: LexicalConcept
definition: A Safety Environment Task implements part of the functionality provided by a Safety Environment. Depending on its role in the overall function provided, it has a specific SIL assigned (in-line with total SE SIL definition). It may run replicated in multiple Compartments as SE Task Replicas.

Safety Environment Task
type: Form

SET
type: Form

SE
type: Acronym
type: LexicalEntry
acronym for: SAFETY--ENVIRONMENT label
canonical form: SE

SAFETY--ENVIRONMENT lexConcept
type: LexicalConcept
definition: The Safety Environment refers to the software needed to provide the services of the Safety Layer in one single Compartment. Previous definition: The Safety Environment refers to all Safety Environment Tasks needed for a Functional System.

SAFETY--ENVIRONMENT lexConcept 2
type: LexicalConcept
definition: The Safety Environment refers to all Safety Environment Tasks needed for a Functional System.

Safety Environment
type: Form

SE
type: Form

SE
type: Form

SF
type: Acronym
type: LexicalEntry
acronym for: SAFETY--FRAMEWORK label
canonical form: SF

SAFETY--FRAMEWORK lexConcept
type: LexicalConcept
definition: The Safety Framework refers to all Safety Environment Replicas needed for a Functional System. Previous definition: new term

Safety Framework
type: Form

SF
type: Form

SL
type: Acronym
type: LexicalEntry
acronym for: SAFETY--LAYER label
canonical form: SL

SAFETY--LAYER lexConcept
type: LexicalConcept
definition: The Safety Layer implements all the technical safety principles related to fulfilling the requirements of EN 50126, EN 50716 (formerly 50128)%3CmxGraphModel%3E%3Croot%3E%3CmxCell%20id%3D%220%22%2F%3E%3CmxCell%20id%3D%221%22%20parent%3D%220%22%2F%3E%3CmxCell%20id%3D%222%22%20value%3D%22Physical%20Computing%26lt%3Bbr%26gt%3BElement%26amp%3Bnbsp%3B%22%20style%3D%22rounded%3D0%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3BfillColor%3D%23D6D6D6%3BfontColor%3D%23333333%3BstrokeColor%3D%23666666%3B%22%20vertex%3D%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x%3D%22-130%22%20y%3D%22410%22%20width%3D%22240%22%20height%3D%2260%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell%20id%3D%223%22%20value%3D%22Core%22%20style%3D%22rounded%3D0%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3BfillColor%3D%23cac5d3%3B%22%20vertex%3D%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x%3D%22-120%22%20y%3D%22438%22%20width%3D%2240%22%20height%3D%2225%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell%20id%3D%224%22%20value%3D%22Memory%22%20style%3D%22rounded%3D0%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3BfillColor%3D%23cac5d3%3B%22%20vertex%3D%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x%3D%2250%22%20y%3D%22440%22%20width%3D%2250%22%20height%3D%2225%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell%20id%3D%225%22%20value%3D%22%22%20style%3D%22rounded%3D0%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3BgradientColor%3Dnone%3Bglass%3D0%3Bshadow%3D0%3BfillStyle%3Dhatch%3BstrokeWidth%3D0.3%3BfillColor%3D%23404040%3B%22%20vertex%3D%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x%3D%22-220%22%20y%3D%22404%22%20width%3D%22370%22%20height%3D%2272%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell%20id%3D%226%22%20value%3D%22I3%22%20style%3D%22ellipse%3BwhiteSpace%3Dwrap%3Bhtml%3D1%3BfillColor%3D%23a0522d%3BfontColor%3D%23ffffff%3BstrokeColor%3D%236D1F00%3B%22%20vertex%3D%221%22%20parent%3D%221%22%3E%3CmxGeometry%20x%3D%22-23.61%22%20y%3D%22305.5%22%20width%3D%2255%22%20height%3D%2220%22%20as%3D%22geometry%22%2F%3E%3C%2FmxCell%3E%3CmxCell%2…

Safety Layer
type: Form

SL
type: Form

I5
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: SAFETY--PLATFORM--INDEPENDENCE--INTERFACE label
canonical form: I5

SAFETY--PLATFORM--INDEPENDENCE--INTERFACE lexConcept
type: LexicalConcept
definition: 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.

Safety Platform Independence Interface
type: Form

I5
type: Form

Safety principles are binding guidelines and conditions to respect for safe trai...
type: LexicalEntry
type: MultiwordExpression
canonical form: Safety principles are binding guidelines and conditions to respect for safe trai...
sense: SAFETY--PRINCIPLES--ARE--BINDING--GUIDELINES--AND--CONDITIONS--TO--RESPECT--FOR--SAFE--TRAI lexSense

SAFETY--PRINCIPLES--ARE--BINDING--GUIDELINES--AND--CONDITIONS--TO--RESPECT--FOR--SAFE--TRAI lexConcept
type: LexicalConcept
definition: Safety principles are binding guidelines and conditions to respect for safe train movement. Details described here: S2 Harmonisation operational Safety Principles (image: 9-screenshot-20250930-145656-24.png)

Safety principles are binding guidelines and conditions to respect for safe trai...
type: Form

SASC
type: LexicalEntry
type: Word
canonical form: SASC
sense: SASC lexSense

SASC lexConcept
type: LexicalConcept
definition: Specific Application Safety Case; SPPRAMSS-334 - [EN 50129:2018/AC:2019-04] ,SPPRAMSS-335 - [EN 50126-2:2017] {comment:104}

SASC
type: Form

Scalability
type: LexicalEntry
type: Word
canonical form: Scalability
sense: SCALABILITY lexSense

SCALABILITY lexConcept
type: LexicalConcept
definition: Scalability refers to the ability of a system/sub-system to handle an increasing workload or expand its capacity without significantly impacting performance, efficiency, or cost.

Scalability
type: Form

Schema meta-model
type: LexicalEntry
type: MultiwordExpression
canonical form: Schema meta-model
sense: SCHEMA--META-MODEL lexSense

SCHEMA--META-MODEL lexConcept
type: LexicalConcept
definition: A data schema is implemented in a known language such as XSD/XML or JSON schema. This allows a computer program to parse data that are known to conform to this specific schema. The schema documents the semantics of data entities so that an intelligent reader can interpret the information in the data. Such a schema can be represented as a meta-model.

Schema meta-model
type: Form

SCV-OB - Signal Converter-On-board
type: LexicalEntry
type: MultiwordExpression
canonical form: SCV-OB - Signal Converter-On-board
sense: SCV-OB-----SIGNAL--CONVERTER-ON-BOARD lexSense

SCV-OB-----SIGNAL--CONVERTER-ON-BOARD lexConcept
type: LexicalConcept
definition: SCV-OB - Signal Converter-On-board

SCV-OB - Signal Converter-On-board
type: Form

secondary functions
type: LexicalEntry
type: MultiwordExpression
canonical form: secondary functions
sense: SECONDARY--FUNCTIONS lexSense

SECONDARY--FUNCTIONS lexConcept
type: LexicalConcept
definition: "Value analysis defines a “basic function” as anything that makes the product work or sell. A function that is defined as “basic” cannot change. Secondary functions, also called “supporting functions”, described the manner in which the basic function(s) were implemented. Secondary functions could be modified or eliminated to reduce product cost."

secondary functions
type: Form

SecRACs = Security Related Application Conditions. These application conditions...
type: LexicalEntry
type: MultiwordExpression
canonical form: SecRACs = Security Related Application Conditions. These application conditions...
sense: https://glossaries.ontorail.org/LEX_SP-DEFS/lex_sp-defs-251007#SECRACS--%3D--SECURITY--RELATED--APPLICATION--CONDITIONS---THESE--APPLICATION--CONDITIONS_lexSense

https://glossaries.ontorail.org/LEX_SP-DEFS/lex_sp-defs-251007#SECRACS--%3D--SECURITY--RELATED--APPLICATION--CONDITIONS---THESE--APPLICATION--CONDITIONS_lexConcept
type: LexicalConcept
definition: SecRACs = Security Related Application Conditions. These application conditions need to be fulfilled to fulfill the approved level of security. SecRACs are defined in TS 50701 (draft: IEC 63452).

SecRACs = Security Related Application Conditions. These application conditions...
type: Form

SecRAC
type: LexicalEntry
type: Word
canonical form: SecRAC
sense: SECRAC lexSense

SECRAC lexConcept
type: LexicalConcept
definition: security-related application condition [SOURCE: CLC/TS 50701:2023]

SecRAC
type: Form

Secure Communication
type: LexicalEntry
type: MultiwordExpression
canonical form: Secure Communication
sense: SECURE--COMMUNICATION lexSense

SECURE--COMMUNICATION lexConcept
type: LexicalConcept
definition: defines an integrity-protected and optionally encrypted channel between two entities. Security is achieved by using TLS 1.3 or OPC UA Secure Conversation.

Secure Communication
type: Form

Secure Component
type: LexicalEntry
type: MultiwordExpression
canonical form: Secure Component
sense: SECURE--COMPONENT lexSense

SECURE--COMPONENT lexConcept
type: LexicalConcept
definition: 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.

Secure Component
type: Form

SSL
type: Acronym
type: LexicalEntry
acronym for: SECURE--SOCKETS--LAYER label
canonical form: SSL

SECURE--SOCKETS--LAYER lexConcept
type: LexicalConcept
definition: Secure Sockets Layer

Secure Sockets Layer
type: Form

SSL
type: Form

STS
type: Acronym
type: LexicalEntry
acronym for: SECURE--TIME--SYNCHRONISATION label
canonical form: STS

SECURE--TIME--SYNCHRONISATION lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Secure Time Synchronisation

Secure Time Synchronisation
type: Form

STS
type: Form

SIEM
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: SECURITY--INFORMATION--AND--EVENT--MANAGEMENT label
canonical form: SIEM

SECURITY--INFORMATION--AND--EVENT--MANAGEMENT lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Security Information and Event Management

Security Information and Event Management
type: Form

SIEM
type: Form

SOC
type: Acronym
type: LexicalEntry
acronym for: SECURITY--OPERATION--CENTRE label
canonical form: SOC

SECURITY--OPERATION--CENTRE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Security Operation Centre

Security Operation Centre
type: Form

SOC
type: Form

Segment Profile
type: LexicalEntry
type: MultiwordExpression
canonical form: Segment Profile
sense: SEGMENT--PROFILE lexSense

SEGMENT--PROFILE lexConcept
type: LexicalConcept
definition: A Segment Profile is a one-dimensional object that describes a single and consecutive section of track and corresponds to the Track Centreline of that section of track. A Segment Profile has a Start Point and an End Point, which correspond to the boundary points of the section of Track Centreline of that Segment Profile. A Segment Profile defines a set of static infrastructure data required by different on-board applications like ATO, Perception, Localisation, APM. The Segment Profile is part of Application Configuration Data. These data are derived from Infrastructure Data according to the interface data structure requirements of the consumers.

Segment Profile
type: Form

SEMP Link Rule.
type: LexicalEntry
type: MultiwordExpression
canonical form: SEMP Link Rule.
sense: SEMP--LINK--RULE lexSense

SEMP--LINK--RULE lexConcept
type: LexicalConcept
definition: Defines how certain Polarion workitems shall be linked. See: SPPROCESS/SEMP Annex D Processes/SEMP Link Rules overview

SEMP Link Rule.
type: Form

SEMP Process.
type: LexicalEntry
type: MultiwordExpression
canonical form: SEMP Process.
sense: SEMP--PROCESS lexSense

SEMP--PROCESS lexConcept
type: LexicalConcept
definition: Defines a process in the SEMP. See: SEMP Processes

SEMP Process.
type: Form

SEMP Role Allocation.
type: LexicalEntry
type: MultiwordExpression
canonical form: SEMP Role Allocation.
sense: SEMP--ROLE--ALLOCATION lexSense

SEMP--ROLE--ALLOCATION lexConcept
type: LexicalConcept
definition: Name of the person who has a certan role in a certain team. See: Tracker search for role allocations

SEMP Role Allocation.
type: Form

Sensitivity points
type: LexicalEntry
type: MultiwordExpression
canonical form: Sensitivity points
sense: SENSITIVITY--POINTS lexSense

SENSITIVITY--POINTS lexConcept
type: LexicalConcept
definition: Sensitivity points are any modeled values under a given individual quality attribute that are significantly affected by a change to the architecture

Sensitivity points
type: Form

SoC
type: Acronym
type: LexicalEntry
acronym for: SEPARATION--OF--CONCERNS label
canonical form: SoC

SEPARATION--OF--CONCERNS lexConcept
type: LexicalConcept
definition: Separation of Concerns

Separation of Concerns
type: Form

SoC
type: Form

SERA Enablers
type: LexicalEntry
type: MultiwordExpression
canonical form: SERA Enablers
sense: SERA--ENABLERS lexSense

SERA--ENABLERS lexConcept
type: LexicalConcept
definition: The development of the SERA Target functionality is a long-term process. In this process standalone functional units so-called "SERA Enablers" are developed belonging to the SERA Target system. Individual SERA Enablers might be suitable for early rollout in legacy projects, which still use national specifications and legacy systems. Therefore, SERA Enablers are standalone subsystems having standardized interfaces, which are specified, developed, tested and approved according to the needs of the SERA Target. If needed, adapters can be used to integrate them in legacy systems (part of migration strategy). Currently identified SERA Enablers are: * Object controllers with SP Standard interfaces (partially based on EULYNX) * PES and ETPS with SP Standard interfaces (i.e. SCI process interfaces and service interfaces SDI, SMI and SSI) * Central services with SP Standard interfaces (i.e. service interfaces SDI, SMI and SSI), which provide supporting functions for operation of SERA systems: configuration, maintenance and digital register-infrastructure, security, communication. * TMS with SP Standard interfaces (i.e. SCI-OP process interface and service interfaces SDI, SMI and SSI) * FRMCS for radio communication, replacing GSM-R * Safe train integrity and train length information of rolling stock, enabling safe traffic control for mixed traffic * ATO-TS ( for ATO GoA1/2) with SP Standard interfaces (i.e. SCI process interfaces and service interfaces SDI, SMI and SSI), based on harmonized operation concept and related rules

SERA Enablers
type: Form

SERA Phase
type: LexicalEntry
type: MultiwordExpression
canonical form: SERA Phase
sense: SERA--PHASE lexSense

SERA--PHASE lexConcept
type: LexicalConcept
definition: 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.

SERA Phase
type: Form

SERA Pre-Phase
type: LexicalEntry
type: MultiwordExpression
canonical form: SERA Pre-Phase
sense: SERA--PRE-PHASE lexSense

SERA--PRE-PHASE lexConcept
type: LexicalConcept
definition: The SERA Pre-Phase is a deployment phase, which starts when the first SERA Enablers (belonging to the SERA Target; see SERA Enablers list in Glossary) are ready for implementation (rollout) in projects, where legacy subsystems can be replaced already by equivalent SERA Subsystems. Such projects still use national specifications and legacy systems. This approach forms a significant part of the overall migration strategy towards SERA. As a sample this might comprise the early introduction of certain SERA Enablers like object controllers having SP Standard interfaces (based on EULYNX) in combination with legacy system components (supporting legacy L2/FB/FVB principles; optional ATO GoA2). This allows early benefitting - during the long-term SERA Development process - from their advantages (e.g. performance increase and cost reduction) and ensures protection of investment The gradual rollout of those SERA Enablers is part of the migration path towards the later SERA Phase and its target system. SERA Enablers in this pre-phase must be functional units of reasonable size and standalone testable and approved - e.g. like an SERA ready object controller unit. Related migration use cases and concepts are specified in separate SP Documents.

SERA Pre-Phase
type: Form

Serious Accident
type: LexicalEntry
type: MultiwordExpression
canonical form: Serious Accident
sense: SERIOUS--ACCIDENT lexSense

SERIOUS--ACCIDENT lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: ‘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) ]

Serious Accident
type: Form

Service Facility
type: LexicalEntry
type: MultiwordExpression
canonical form: Service Facility
sense: SERVICE--FACILITY lexSense

SERVICE--FACILITY lexConcept
type: LexicalConcept
definition: Service facility means the installation, including ground area, building and equipment, which has been specially arranged, as a whole or in part, to allow the supply of one or more services referred to in points 2 to 4 of Annex II of DIRECTIVE 2012/34/EU OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 21 November 2012 establishing a single European railway area (recast).

Service Facility
type: Form

SFCS
type: Acronym
type: LexicalEntry
acronym for: SERVICE--FUNCTION--CONFIGURATION--SYSTEM label
canonical form: SFCS

SERVICE--FUNCTION--CONFIGURATION--SYSTEM lexConcept
type: LexicalConcept
definition: 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).

Service Function Configuration System
type: Form

SFCS
type: Form

SFC
type: Acronym
type: LexicalEntry
acronym for: SERVICE--FUNCTION--CONFIGURATION label
canonical form: SFC

SERVICE--FUNCTION--CONFIGURATION lexConcept
type: LexicalConcept
definition: The Service Function Configuration (SFC) is the implementation of the Configuration Management System. The SFC is a central location technical system that is responsible for managing the BuildingBlock Configurations. Each BuildingBlock deployment is managed by exactly one SFC.

Service Function Configuration
type: Form

SFC
type: Form

SFDS
type: Acronym
type: LexicalEntry
acronym for: SERVICE--FUNCTION--DIAGNOSTIC--SYSTEM label
canonical form: SFDS

SERVICE--FUNCTION--DIAGNOSTIC--SYSTEM lexConcept
type: LexicalConcept
definition: The{comment:66} Service Function Diagnostic aggregates and manages all cascaded diagnostic systems connected to it in one consistent OPC UA namespace.{comment:84} The details are described in the Generic Diagnostic Concept.

Service Function Diagnostic System
type: Form

SFDS
type: Form

SFD
type: Acronym
type: LexicalEntry
acronym for: SERVICE--FUNCTION--DIAGNOSTICS label
canonical form: SFD

SERVICE--FUNCTION--DIAGNOSTICS lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Service Function Diagnostics

Service Function Diagnostics
type: Form

SFD
type: Form

Services
type: LexicalEntry
type: Word
canonical form: Services
sense: SERVICES lexSense

SERVICES lexConcept
type: LexicalConcept
definition: Services are one of the two key components of economics, the other being goods. A service is a type of economic activity (or series of activities) that is of a more or less intangible nature, is not stored and does not result in ownership. Normally (but not necessarily) it takes place in interactions between the customer and service employees and /or systems of the service provider, provided as solutions to customer problems. Examples of services include the transfer of goods, such as the postal service delivering mail, and the use of expertise or experience, such as a person visiting a doctor. Services include the provision of what is necessary for maintenance of thing or operation, assistance and advice. RNE dictionary

Services
type: Form

SCS
type: Acronym
type: LexicalEntry
acronym for: SHARED--CYBERSECURITY--SERVICES label
canonical form: SCS

SHARED--CYBERSECURITY--SERVICES lexConcept
type: LexicalConcept
definition: 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>.

Shared Cybersecurity Services
type: Form

SCS
type: Form

SSS
type: Acronym
type: LexicalEntry
acronym for: SHARED--SECURITY--SERVICE label
canonical form: SSS

SHARED--SECURITY--SERVICE lexConcept
type: LexicalConcept
definition: Shared Security Service {comment:7}

Shared Security Service
type: Form

SSS
type: Form

SRU
type: Acronym
type: LexicalEntry
acronym for: SHOP--REPLACEABLE--UNIT label
canonical form: SRU

SHOP--REPLACEABLE--UNIT lexConcept
type: LexicalConcept
definition: Shop Replaceable Unit

Shop Replaceable Unit
type: Form

SRU
type: Form

Shunting composition:
type: LexicalEntry
type: MultiwordExpression
canonical form: Shunting composition:
sense: SHUNTING--COMPOSITION lexSense

SHUNTING--COMPOSITION lexConcept
type: LexicalConcept
definition: Shunting composition: A traction unit coupled or not to a set of vehicles and intended to be moved under shunting conditions without train data.

Shunting composition:
type: Form

Shunting Movement
type: LexicalEntry
type: MultiwordExpression
canonical form: Shunting Movement
sense: SHUNTING--MOVEMENT lexSense

SHUNTING--MOVEMENT lexConcept
type: LexicalConcept
definition: 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
type: Form

SIS
type: Acronym
type: LexicalEntry
acronym for: SIGNAL--IN--SPACE label
canonical form: SIS

SIGNAL--IN--SPACE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Signal In Space

Signal In Space
type: Form

SIS
type: Form

SIL - Safety Interity Level
type: LexicalEntry
type: MultiwordExpression
canonical form: SIL - Safety Interity Level
sense: SIL-----SAFETY--INTERITY--LEVEL lexSense

SIL-----SAFETY--INTERITY--LEVEL lexConcept
type: LexicalConcept
definition: SIL - Safety Interity Level

SIL - Safety Interity Level
type: Form

SOAP
type: Acronym
type: LexicalEntry
acronym for: SIMPLE--OBJECT--ACCESS--PROTOCOL label
canonical form: SOAP

SIMPLE--OBJECT--ACCESS--PROTOCOL lexConcept
type: LexicalConcept
definition: Simple Object Access Protocol

Simple Object Access Protocol
type: Form

SOAP
type: Form

SERA-CCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: SINGLE--EUROPEAN--RAILWAY--AREA-----COMMAND--CONTROL--AND--SIGNALING label
canonical form: SERA-CCS

SINGLE--EUROPEAN--RAILWAY--AREA-----COMMAND--CONTROL--AND--SIGNALING lexConcept
type: LexicalConcept
definition: For the railway sector, EU policy focuses on the main goal of establishing a single European railway area, an EU-wide system of railway networks which would allow the expansion of the rail sector based on * competition, * technical harmonization and * joint development of cross-border connections [see Building the single European railway area]. To this end, the EU aims to: * open and restructure the rail market * increase competitiveness by creating a level playing field for companies * develop infrastructure to ensure interoperability * improve efficiency in infrastructure use and safety * ensure fair prices for consumers{comment:5} SERA-CCS is understood to consist of those SERA objectives which are relevant for CCS (technical/operational target). It is defined by the following capabilities: * Provides Independence between Infrastructure Managers (IM) and Railway Undertakings (RU) or Vehicle Owners (VO): * No track access restriction or extra costs for a compliant RU/VO fleet/services accessing a given IM infrastructure compliant with SERA-CCS. * Non discriminatory access to IM services and capacity allocation across SERA-CCS IMs for compliant RU/VO fleet/services. * Ensures interoperability, which is the ability to allow the safe and uninterrupted movement of trains that accomplish the specified levels of performance across different infrastructure networks (IMs) and the ability that an infrastructure network is able to interact with trains of different RUs/VOs. * Ensures Harmonized Operations, based on: * Radio-based CAB Signalling, * Automatic Train{comment:1} Operation (ATO), * Single licensing for Drivers and Signalers across SERA-CCS. * Provides Backwards Compatibility: * Compatibility is considered to be achieved for a particular combination of on-board and trackside when the on-board is able to run a normal service on that trackside. The expression “train is running a normal service” shall be understood as “a train not penalized because of a reduction of p…

Single European Railway Area - Command Control and Signaling
type: Form

SERA-CCS
type: Form

SERA
type: Acronym
type: LexicalEntry
acronym for: SINGLE--EUROPEAN--RAILWAY--AREA label
canonical form: SERA

SINGLE--EUROPEAN--RAILWAY--AREA lexConcept
type: LexicalConcept
definition: Defining the fundamental design principles and process for adopting a functional architecture for rail as a system, with a focus on CCS, CMS and TMS supporting the implementation of the SERA (Single European Railway Area)

Single European Railway Area
type: Form

SERA
type: Form

SESAR
type: Acronym
type: LexicalEntry
acronym for: SINGLE--EUROPEAN--SKY--ATM--RESEARCH label
canonical form: SESAR

SINGLE--EUROPEAN--SKY--ATM--RESEARCH lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Single European Sky ATM Research

Single European Sky ATM Research
type: Form

SESAR
type: Form

Skip Stop
type: LexicalEntry
type: MultiwordExpression
canonical form: Skip Stop
sense: SKIP--STOP lexSense

SKIP--STOP lexConcept
type: LexicalConcept
definition: Remove a planned stop

Skip Stop
type: Form

Soft Key
type: LexicalEntry
type: MultiwordExpression
canonical form: Soft Key
sense: SOFT--KEY lexSense

SOFT--KEY lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: 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 lexConcept 3
type: LexicalConcept
definition: 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 lexConcept 4
type: LexicalConcept
definition: 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 lexConcept 5
type: LexicalConcept
definition: 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 lexConcept 6
type: LexicalConcept
definition: 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 lexConcept 7
type: LexicalConcept
definition: 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 lexConcept 8
type: LexicalConcept
definition: 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.

Soft Key
type: Form

Software Configuration Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Software Configuration Data
sense: SOFTWARE--CONFIGURATION--DATA lexSense

SOFTWARE--CONFIGURATION--DATA lexConcept
type: LexicalConcept
definition: The Software Configuration data refers to executable binary files from suppliers which are usually required to install software on the systems. Software Configuration Data is provided via configuration interface to the CCS/TMS Systems.{comment:73}

Software Configuration Data
type: Form

SW
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: SOFTWARE label
canonical form: SW

SOFTWARE lexConcept
type: LexicalConcept
definition: Software is software that encompasses both : the operating system and the computer application that runs the computer. They are both essential for the operation of a device.

Software
type: Form

SW
type: Form

SP - System Pillar
type: LexicalEntry
type: MultiwordExpression
canonical form: SP - System Pillar
sense: SP-----SYSTEM--PILLAR lexSense

SP-----SYSTEM--PILLAR lexConcept
type: LexicalConcept
definition: SP - System Pillar

SP - System Pillar
type: Form

SC2.x
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: SPECIFIC--CONTRACT--FOR--LOT--2--OF--YEAR--X label
canonical form: SC2.x

SPECIFIC--CONTRACT--FOR--LOT--2--OF--YEAR--X lexConcept
type: LexicalConcept
definition: This refers to the ERJU contracts for SP signed every year; SC2.1 for the first year of developmeent and so on. The SP domains are part of the "Lot 2" in the overall ERJU project (e.g. IP, SP).

Specific Contract for Lot 2 of year x
type: Form

SC2.x
type: Form

Specific national product functionality
type: LexicalEntry
type: MultiwordExpression
canonical form: Specific national product functionality
sense: SPECIFIC--NATIONAL--PRODUCT--FUNCTIONALITY lexSense

SPECIFIC--NATIONAL--PRODUCT--FUNCTIONALITY lexConcept
type: LexicalConcept
definition: The set of functions of a national specific product, including system behavior on electronic or analog system and user interfaces

Specific national product functionality
type: Form

SPT1-railway System - Common business Objectives (rev. 63268)
type: LexicalEntry
type: MultiwordExpression
canonical form: SPT1-railway System - Common business Objectives (rev. 63268)
sense: SPT1-RAILWAY--SYSTEM-----COMMON--BUSINESS--OBJECTIVES--REV---63268 lexSense

SPT1-RAILWAY--SYSTEM-----COMMON--BUSINESS--OBJECTIVES--REV---63268 lexConcept
type: LexicalConcept
definition: SPT1-railway System - Common business Objectives (rev. 63268)

SPT1-railway System - Common business Objectives (rev. 63268)
type: Form

SRAC.
type: LexicalEntry
type: Word
canonical form: SRAC.
sense: SRAC lexSense

SRAC lexConcept
type: LexicalConcept
definition: Safety related application condition.

SRAC.
type: Form

SRD
type: LexicalEntry
type: Word
canonical form: SRD
sense: SRD lexSense

SRD lexConcept
type: LexicalConcept
definition: Single Rules Database [SOURCE: ERA, https://www.era.europa.eu/domains/registers/srd_en ]

SRD
type: Form

SRS
type: LexicalEntry
type: Word
canonical form: SRS
sense: SRS lexSense

SRS lexConcept
type: LexicalConcept
definition: System Requirement Specifications

SRS
type: Form

STAS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STA--SECTION label
canonical form: STAS

STA--SECTION lexConcept
type: LexicalConcept
definition: One of the 1..n driveable paths within a Switchable Trackside Assets.

STA Section
type: Form

STAS
type: Form

Stakeholder Requirement
type: LexicalEntry
type: MultiwordExpression
canonical form: Stakeholder Requirement
sense: STAKEHOLDER--REQUIREMENT lexSense

STAKEHOLDER--REQUIREMENT lexConcept
type: LexicalConcept
definition: 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 Requirement
type: Form

Stakeholder.
type: LexicalEntry
type: Word
canonical form: Stakeholder.
sense: STAKEHOLDER lexSense

STAKEHOLDER lexConcept
type: LexicalConcept
definition: Characterizes a stakeholder

Stakeholder.
type: Form

SCI-CMD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARD--COMMUNICATION--INTERFACE-----COMMAND label
canonical form: SCI-CMD

STANDARD--COMMUNICATION--INTERFACE-----COMMAND lexConcept
type: LexicalConcept
definition: Standard Communication Interface - Command

Standard Communication Interface - Command
type: Form

SCI-CMD
type: Form

SCI-IO
type: Acronym
type: LexicalEntry
acronym for: STANDARD--COMMUNICATION--INTERFACE-----INPUT--OUTPUT label
canonical form: SCI-IO

STANDARD--COMMUNICATION--INTERFACE-----INPUT--OUTPUT lexConcept
type: LexicalConcept
definition: Standard Communication Interface - Input Output

Standard Communication Interface - Input Output
type: Form

SCI-IO
type: Form

SCI-LC
type: Acronym
type: LexicalEntry
acronym for: STANDARD--COMMUNICATION--INTERFACE-----LEVEL--CROSSING label
canonical form: SCI-LC

STANDARD--COMMUNICATION--INTERFACE-----LEVEL--CROSSING lexConcept
type: LexicalConcept
definition: Standard Communication Interface - Level Crossing

Standard Communication Interface - Level Crossing
type: Form

SCI-LC
type: Form

SCI-LS
type: Acronym
type: LexicalEntry
acronym for: STANDARD--COMMUNICATION--INTERFACE-----LIGHT--SIGNAL label
canonical form: SCI-LS

STANDARD--COMMUNICATION--INTERFACE-----LIGHT--SIGNAL lexConcept
type: LexicalConcept
definition: Standard Communication Interface - Light Signal

Standard Communication Interface - Light Signal
type: Form

SCI-LS
type: Form

SCI-P
type: Acronym
type: LexicalEntry
acronym for: STANDARD--COMMUNICATION--INTERFACE-----POINTS label
canonical form: SCI-P

STANDARD--COMMUNICATION--INTERFACE-----POINTS lexConcept
type: LexicalConcept
definition: Standard Communication Interface - Points

Standard Communication Interface - Points
type: Form

SCI-P
type: Form

SCI-SCMD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARD--COMMUNICATION--INTERFACE-----SAFETY-RELEVANT--COMMAND label
canonical form: SCI-SCMD

STANDARD--COMMUNICATION--INTERFACE-----SAFETY-RELEVANT--COMMAND lexConcept
type: LexicalConcept
definition: Standard Communication Interface - Safety-relevant Command

Standard Communication Interface - Safety-relevant Command
type: Form

SCI-SCMD
type: Form

SCI-TWS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARD--COMMUNICATION--INTERFACE-----TRACKWORKER--SAFETY--SYSTEM label
canonical form: SCI-TWS

STANDARD--COMMUNICATION--INTERFACE-----TRACKWORKER--SAFETY--SYSTEM lexConcept
type: LexicalConcept
definition: Standard Communication Interface - Trackworker Safety System

Standard Communication Interface - Trackworker Safety System
type: Form

SCI-TWS
type: Form

SCI-TDS
type: Acronym
type: LexicalEntry
acronym for: STANDARD--COMMUNICATION--INTERFACE-----TRAIN--DETECTION--SYSTEM label
canonical form: SCI-TDS

STANDARD--COMMUNICATION--INTERFACE-----TRAIN--DETECTION--SYSTEM lexConcept
type: LexicalConcept
definition: Standard Communication Interface - Train Detection System

Standard Communication Interface - Train Detection System
type: Form

SCI-TDS
type: Form

SCI
type: Acronym
type: LexicalEntry
acronym for: STANDARD--COMMUNICATION--INTERFACE label
canonical form: SCI

STANDARD--COMMUNICATION--INTERFACE lexConcept
type: LexicalConcept
definition: SCI defines generic unified communication protocol to ensure interoperability between different railway signalling subsystems (e.g., interlocking, signals, points, level crossings).

Standard Communication Interface
type: Form

SCI
type: Form

SCI-OP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARD--COMMUNICATIONS--INTERFACE-----OPERATIONAL--PLAN label
canonical form: SCI-OP

STANDARD--COMMUNICATIONS--INTERFACE-----OPERATIONAL--PLAN lexConcept
type: LexicalConcept
definition: Standard Communications Interface – Operational Plan

Standard Communications Interface – Operational Plan
type: Form

SCI-OP
type: Form

SDI-DS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARD--DIAGNOSTIC--INTERFACE-----DIAGNOSTIC--SYSTEM label
canonical form: SDI-DS

STANDARD--DIAGNOSTIC--INTERFACE-----DIAGNOSTIC--SYSTEM lexConcept
type: LexicalConcept
definition: Standard Diagnostic Interface – Diagnostic System

Standard Diagnostic Interface – Diagnostic System
type: Form

SDI-DS
type: Form

SDI-WTMS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARD--DIAGNOSTIC--INTERFACE-----WAYSIDE--TRAIN--MONITORING--SYSTEMS label
canonical form: SDI-WTMS

STANDARD--DIAGNOSTIC--INTERFACE-----WAYSIDE--TRAIN--MONITORING--SYSTEMS lexConcept
type: LexicalConcept
definition: Standard interface for diagnostic data exchange between infrastructure manager and industry supplier.

Standard Diagnostic Interface – Wayside Train Monitoring Systems
type: Form

SDI-WTMS
type: Form

SDI
type: Acronym
type: LexicalEntry
acronym for: STANDARD--DIAGNOSTIC--INTERFACE label
canonical form: SDI

STANDARD--DIAGNOSTIC--INTERFACE lexConcept
type: LexicalConcept
definition: Standard Diagnostic Interface as defined by EULYNX / System Pillar

Standard Diagnostic Interface
type: Form

SDI
type: Form

Standard Interfaces
type: LexicalEntry
type: MultiwordExpression
canonical form: Standard Interfaces
sense: STANDARD--INTERFACES lexSense

STANDARD--INTERFACES lexConcept
type: LexicalConcept
definition: TODO: Add definition for standard interfaces

Standard Interfaces
type: Form

SMI
type: Acronym
type: LexicalEntry
acronym for: STANDARD--MAINTENANCE--INTERFACE label
canonical form: SMI

STANDARD--MAINTENANCE--INTERFACE lexConcept
type: LexicalConcept
definition: Standard Maintenance Interface as defined by EULYNX / System Pillar

Standard Maintenance Interface
type: Form

SMI
type: Form

SSI
type: Acronym
type: LexicalEntry
acronym for: STANDARD--SECURITY--INTERFACE label
canonical form: SSI

STANDARD--SECURITY--INTERFACE lexConcept
type: LexicalConcept
definition: Standard Security Interface as defined by EULYNX / System Pillar

STANDARD--SECURITY--INTERFACE lexConcept 2
type: LexicalConcept
definition: Standard Security Interface

Standard Security Interface
type: Form

SSI
type: Form

SSI
type: Form

STIP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARDISATION--AND--TSI--INPUT--PLAN label
canonical form: STIP

STANDARDISATION--AND--TSI--INPUT--PLAN lexConcept
type: LexicalConcept
definition: The Europe’s Rail (EU-Rail) Standardisation and TSI Input Plan (STIP) is a collection of all outputs from EU-Rail (Innovation and System Pillar) which contribute to the goal of harmonisation of the railway system. The harmonisation topics are categorised in technical domains and described by the foreseen harmonisation channel (TSI, EN standards, SP document), the time horizon as well as dependencies with existing regulations, standards, and R&I activities.

Standardisation and TSI Input Plan
type: Form

STIP
type: Form

SDI-OC
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARDISED--INTERFACE--FOR--DIAGNOSTICS--OF--OBJECT--CONTROLLERS label
canonical form: SDI-OC

STANDARDISED--INTERFACE--FOR--DIAGNOSTICS--OF--OBJECT--CONTROLLERS lexConcept
type: LexicalConcept
definition: Standardised interface for diagnostics - specifically for Object Controllers - to enable communication with the central service function Diagnostics

Standardised interface for diagnostics of Object Controllers
type: Form

SDI-OC
type: Form

SDI-Traffic CS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARDISED--INTERFACE--FOR--DIAGNOSTICS--OF--TRAFFIC--CS--SYSTEMS label
canonical form: SDI-Traffic CS

STANDARDISED--INTERFACE--FOR--DIAGNOSTICS--OF--TRAFFIC--CS--SYSTEMS lexConcept
type: LexicalConcept
definition: Standardised interface for diagnostics - specifically for Traffic CS systems - to enable communication with the central service function Diagnostics

Standardised interface for diagnostics of Traffic CS systems
type: Form

SDI-Traffic CS
type: Form

SMI-OC
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARDISED--INTERFACE--FOR--MAINTENANCE--OF--OBJECT--CONTROLLERS label
canonical form: SMI-OC

STANDARDISED--INTERFACE--FOR--MAINTENANCE--OF--OBJECT--CONTROLLERS lexConcept
type: LexicalConcept
definition: Standardised interface for maintenance - specifically for Object Controllers - to enable communication with the central service function Maintenance

Standardised interface for maintenance of Object Controllers
type: Form

SMI-OC
type: Form

SMI-Traffic CS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: STANDARDISED--INTERFACE--FOR--MAINTENANCE--OF--TRAFFIC--CS--SYSTEMS label
canonical form: SMI-Traffic CS

STANDARDISED--INTERFACE--FOR--MAINTENANCE--OF--TRAFFIC--CS--SYSTEMS lexConcept
type: LexicalConcept
definition: Standardised interface for maintenance - specifically for Traffic CS systems - to enable communication with the central service function Maintenance

Standardised interface for maintenance of Traffic CS systems
type: Form

SMI-Traffic CS
type: Form

standard/routine operation
type: LexicalEntry
type: MultiwordExpression
canonical form: standard/routine operation
sense: STANDARD ROUTINE--OPERATION lexSense

STANDARD ROUTINE--OPERATION lexConcept
type: LexicalConcept
definition: operational production processes that routinely occur in the day-to-day of an operational railway network, both non-degraded operations and routine degraded operations. Standard/routine operation apply to all operational categories - i.e. All GoA levels,

standard/routine operation
type: Form

Standstill
type: LexicalEntry
type: Word
canonical form: Standstill
sense: STANDSTILL lexSense

STANDSTILL lexConcept
type: LexicalConcept
definition: Standstill is when the train’s speed is detected as 0 km/h by the onboard system, within the accuracy and limits of the system’s detection capabilities. In context of door closing procedure there is also the limit at or below 3 km/h and no un-commanded propulsion is available. This harmonises the intent of both TSIs: it acknowledges the LOC&PAS practical threshold (due to system tolerances) but defaults to the CCS zero-movement criterion when safety functions are involved.

Standstill
type: Form

Start Occupancy Location
type: LexicalEntry
type: MultiwordExpression
canonical form: Start Occupancy Location
sense: START--OCCUPANCY--LOCATION lexSense

START--OCCUPANCY--LOCATION lexConcept
type: LexicalConcept
definition: The location point where the infrastructure element (track, signal, switch, etc..) occupation has started

Start Occupancy Location
type: Form

Start Occupancy Time
type: LexicalEntry
type: MultiwordExpression
canonical form: Start Occupancy Time
sense: START--OCCUPANCY--TIME lexSense

START--OCCUPANCY--TIME lexConcept
type: LexicalConcept
definition: The timestamp where the infrastructure element (track, signal, switch, etc..) occupation has started

Start Occupancy Time
type: Form

State Machine
type: LexicalEntry
type: MultiwordExpression
canonical form: State Machine
sense: STATE--MACHINE lexSense

STATE--MACHINE lexConcept
type: LexicalConcept
definition: Collection of states connected by transitions.

State Machine
type: Form

State Transition
type: LexicalEntry
type: MultiwordExpression
canonical form: State Transition
sense: STATE--TRANSITION lexSense

STATE--TRANSITION lexConcept
type: LexicalConcept
definition: A change of state toward itself or toward another state. A transition is characterised by a trigger which can be an event or a boolean condition.

State Transition
type: Form

State
type: LexicalEntry
type: Word
canonical form: State
sense: STATE lexSense

STATE lexConcept
type: LexicalConcept
definition: An observable and measurable attribute used to characterise a behaviour of an entity during which some invariant condition holds. States can be applied to elements such as actors, systems or subsystems.

State
type: Form

Static (or semi-static) data
type: LexicalEntry
type: MultiwordExpression
canonical form: Static (or semi-static) data
sense: STATIC--OR--SEMI-STATIC--DATA lexSense

STATIC--OR--SEMI-STATIC--DATA lexConcept
type: LexicalConcept
definition: Static (or semi-static) data refers to information or data that remains unchanged or constant over time. It is data that does not require frequent updates or modifications. Static data typically includes reference data, constants, configuration settings, or any other data that remains consistent throughout the operation of a system or application. This type of data is often used as a foundation or reference point for various processes or calculations within a system. Static data is generally stored in a read-only format and is not subject to frequent modifications or user interactions. This is often data that requires a homologation process before it can be applied on a system going in operation. However, it can also include data that does not require a homologation like IP-address, security patches, etc. Example of statical data: software, firmware, parametrisation file, data related to the topology stored in an interlocking, braking curves stored in the ETCS on-board, etc.

Static (or semi-static) data
type: Form

Steep incline - A steep incline is such incline in which the holding brake force...
type: LexicalEntry
type: MultiwordExpression
canonical form: Steep incline - A steep incline is such incline in which the holding brake force...
sense: STEEP--INCLINE-----A--STEEP--INCLINE--IS--SUCH--INCLINE--IN--WHICH--THE--HOLDING--BRAKE--FORCE lexSense

STEEP--INCLINE-----A--STEEP--INCLINE--IS--SUCH--INCLINE--IN--WHICH--THE--HOLDING--BRAKE--FORCE lexConcept
type: LexicalConcept
definition: Steep incline - A steep incline is such incline in which the holding brake force is not sufficient to maintain the train stationary.

Steep incline - A steep incline is such incline in which the holding brake force...
type: Form

Steep Slope - A steep slope is such slope in which the holding brake force is no...
type: LexicalEntry
type: MultiwordExpression
canonical form: Steep Slope - A steep slope is such slope in which the holding brake force is no...
sense: STEEP--SLOPE-----A--STEEP--SLOPE--IS--SUCH--SLOPE--IN--WHICH--THE--HOLDING--BRAKE--FORCE--IS--NO lexSense

STEEP--SLOPE-----A--STEEP--SLOPE--IS--SUCH--SLOPE--IN--WHICH--THE--HOLDING--BRAKE--FORCE--IS--NO lexConcept
type: LexicalConcept
definition: Steep Slope - A steep slope is such slope in which the holding brake force is not sufficient to maintain the train stationary

Steep Slope - A steep slope is such slope in which the holding brake force is no...
type: Form

STIP Milestone.
type: LexicalEntry
type: MultiwordExpression
canonical form: STIP Milestone.
sense: STIP--MILESTONE lexSense

STIP--MILESTONE lexConcept
type: LexicalConcept
definition: Standardisation and TSI Input Plan Milestone

STIP Milestone.
type: Form

STM interface
type: LexicalEntry
type: MultiwordExpression
canonical form: STM interface
sense: STM--INTERFACE lexSense

STM--INTERFACE lexConcept
type: LexicalConcept
definition: Interface of the Specific Transition Module of a train

STM interface
type: Form

SMB
type: Acronym
type: LexicalEntry
acronym for: STOP--MARKER--BOARD label
canonical form: SMB

STOP--MARKER--BOARD lexConcept
type: LexicalConcept
definition: {comment:130}{comment:177}A Harmonised trackside ETCS marker board defined in EN 16494/2015 is a fixed, clearly recognisable trackside sign that indicates the location where a driver has to stop the train, if running without an MA. Further purpose defined by ERTMS Users Group: * To be used to unambiguously identify an EOA which must not be overpassed without authorisation by the signaller and which may protect one or a group of safety-critical points such as a point switch, a conflicting route, an entrance of a station, junctions, etc. * To be used to identify specific location on the track the train shall not overpass when an MA is not available, unless the driver has received a specific authorisation by the signaller. * To be used to mark the location up to which the driver needs to confirm that the line is clear (e.g. for TAF function). To be used to mark the location up to which the driver has to drive under his/her responsibility before a possible MA in FS/OS is received. (image: 8-screenshot-20251001-151620-5.png)

Stop Marker Board
type: Form

SMB
type: Form

Stopping Location
type: LexicalEntry
type: MultiwordExpression
canonical form: Stopping Location
sense: STOPPING--LOCATION lexSense

STOPPING--LOCATION lexConcept
type: LexicalConcept
definition: A stopping location (see also stopping point SPLI-1805 - Stopping point ) in ETCS Level 2 is the operational or electronic location where a train must stop, which can be defined by the EoA, a Stop Marker Board, buffer stop, other signals or operational situations (e. g. wrong path/point) or a platform-specific marker. The specific type chosen and its relation to the actual stopping action depends on operational context and infrastructure. ETCS ensures the train never passes its defined EoA, which may be set according to these physical or operational markers to match the scenario. In ETCS Level 2 railway operations, a "stopping location" is a precisely defined location where a train must come to a controlled standstill according to operational or signaling requirements. The stopping point can relate to different types of end locations or markers, such as: * End of Movement Authority (EoA):** The EoA is the furthest point up to which a train is authorized to move, transmitted electronically to the train via ETCS. It is a dynamic safe limit but not always a physically visible location. The EoA serves as a crucial stopping point, particularly in signal-controlled or cab-signaling sections. * Stop Marker Board (z. B. ETCS Stop Marker):** This is a physical sign on the track indicating where the train must stop. In ETCS operations, such boards are used at locations like platform ends or station entries where a precise physical stop is required. They serve as a visual reference and may coincide with the EoA or be separately enforced under operational rules. * Buffer Stops:** Buffer stops are physical barriers at the end of tracks, typically in terminal stations. The stopping point is set at a safe distance before the buffer stop, defined either by an operational instruction or by a marker. In ETCS, an EoA is placed in front of the buffer stop to ensure safe braking. * Platform Stops with Orientation Markers:** At platforms, stopping points may be designated by physical boa…

Stopping Location
type: Form

STPA
type: LexicalEntry
type: Word
canonical form: STPA
sense: STPA lexSense

STPA lexConcept
type: LexicalConcept
definition: System Theoretic Process Analysis [Source: J3187:202305]

STPA lexConcept 2
type: LexicalConcept
definition: A Systems-Theoretic Process Analysis (STPA) is a hazard analysis technique based on control and system theory rather than the reliability theory underlying most existing hazard analysis techniques with the same goals as any hazard analysis technique, that is, to accumulate information about how hazards can occur.

STPA
type: Form

Struct
type: LexicalEntry
type: Word
canonical form: Struct
sense: STRUCT lexSense

STRUCT lexConcept
type: LexicalConcept
definition: A struct is a named and organised structure for storing a set of coherent information items. It is a class without methods.

Struct
type: Form

Sub-system (sometimes called “Building Block”)
type: LexicalEntry
type: MultiwordExpression
canonical form: Sub-system (sometimes called “Building Block”)
sense: SUB-SYSTEM--SOMETIMES--CALLED-- BUILDING--BLOCK lexSense

SUB-SYSTEM--SOMETIMES--CALLED-- BUILDING--BLOCK lexConcept
type: LexicalConcept
definition: Sub-systems are along ARCADIA systems on System Level 5. Not to be confused with sub-systems in the TSI / interoperability directive. In the TSI / interoperability directive context a sub-system shall be regarded as a interoperability constituent{comment:1505} A sub-system is a part of a system, which is not split into smaller entities. It represents a leaf element in the hierarchy of systems-of-systems. Physically speaking, a sub-system is either a piece of hardware plus software, or just a piece of software. A sub-system is a source able unit of the CCS system, in particular: * a sub-system can be individually tendered to a supplier, * a sub-system can be built individually by a supplier, * a sub-system must be integrated into a system, which includes all necessary test, verification, certification and validation activities depending on the level of harmonisation. The harmonisation of the sub-system’s features is to be defined according to the requested level: * Functional Apportionment, * Interoperability, * Exchangeability, or * Interchangeability.

Sub-system (sometimes called “Building Block”)
type: Form

Substitution [in the framework of maintenance]
type: LexicalEntry
type: MultiwordExpression
canonical form: Substitution [in the framework of maintenance]
sense: SUBSTITUTION-- IN--THE--FRAMEWORK--OF--MAINTENANCE lexSense

SUBSTITUTION-- IN--THE--FRAMEWORK--OF--MAINTENANCE lexConcept
type: LexicalConcept
definition: Substitution in the framework of maintenance’ means any replacement of components by parts of identical function and performance in the framework of preventive or corrective maintenance

Substitution [in the framework of maintenance]
type: Form

Subsystem
type: LexicalEntry
type: Word
canonical form: Subsystem
sense: SUBSYSTEM lexSense

SUBSYSTEM lexConcept
type: LexicalConcept
definition: 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.

Subsystem
type: Form

Supplier
type: LexicalEntry
type: Word
canonical form: Supplier
sense: SUPPLIER lexSense

SUPPLIER lexConcept
type: LexicalConcept
definition: The term "supplier" is used in this document for product suppliers and integration service providers according to IEC 62443-2-4.

SUPPLIER lexConcept 2
type: LexicalConcept
definition: The company or organization providing a component, product or system.

Supplier
type: Form

Supply Chain
type: LexicalEntry
type: MultiwordExpression
canonical form: Supply Chain
sense: SUPPLY--CHAIN lexSense

SUPPLY--CHAIN lexConcept
type: LexicalConcept
definition: IACSs are typically composed of products and services integrated and tested to work together. Each of these products and services is provided to the asset owner by an organization (which may include the asset owner) that is generally referred to as a supplier. Each supplier often has suppliers of its own, and each of these second level suppliers may have suppliers of its own. This cascading of suppliers is referred to as the supply chain. (from IEC 62443-2-1, Org 1.6).

Supply Chain
type: Form

Supporting Information
type: LexicalEntry
type: MultiwordExpression
canonical form: Supporting Information
sense: SUPPORTING--INFORMATION lexSense

SUPPORTING--INFORMATION lexConcept
type: LexicalConcept
definition: Information not directly translatable into localisation information but needed to provide the desired output. This information will be used by internal ASTP processes to enable, improve, or validate localisation information.

Supporting Information
type: Form

Support.
type: LexicalEntry
type: Word
canonical form: Support.
sense: SUPPORT lexSense

SUPPORT lexConcept
type: LexicalConcept
definition: Used for support issues in Polarion

Support.
type: Form

SBB
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: SWISS--FEDERAL--RAILWAYS label
canonical form: SBB

SWISS--FEDERAL--RAILWAYS lexConcept
type: LexicalConcept
definition: Swiss Federal Railways

Swiss Federal Railways
type: Form

SBB
type: Form

Switch
type: LexicalEntry
type: Word
canonical form: Switch
sense: SWITCH lexSense

SWITCH lexConcept
type: LexicalConcept
definition: Physical component which allows a selection of 2 to N states and keeps the state until its position is changed.

SWITCH lexConcept 2
type: LexicalConcept
definition: Physical component which allows a selection of 2 to N states and keeps the state until its position is changed.

SWITCH lexConcept 3
type: LexicalConcept
definition: Physical component which allows a selection of 2 to N states and keeps the state until its position is changed.

SWITCH lexConcept 4
type: LexicalConcept
definition: Physical component which allows a selection of 2 to N states and keeps the state until its position is changed.

SWITCH lexConcept 5
type: LexicalConcept
definition: Physical component which allows a selection of 2 to N states and keeps the state until its position is changed.

SWITCH lexConcept 6
type: LexicalConcept
definition: Physical component which allows a selection of 2 to N states and keeps the state until its position is changed.

SWITCH lexConcept 7
type: LexicalConcept
definition: Physical component which allows a selection of 2 to N states and keeps the state until its position is changed.

SWITCH lexConcept 8
type: LexicalConcept
definition: Switch Physical component which allows a selection of 2 to N states and keeps the state until its position is changed.

Switch
type: Form

SAD
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--ARCHITECTURE--DESCRIPTION label
canonical form: SAD

SYSTEM--ARCHITECTURE--DESCRIPTION lexConcept
type: LexicalConcept
definition: System Architecture Description

System Architecture Description
type: Form

SAD
type: Form

System Capability
type: LexicalEntry
type: MultiwordExpression
canonical form: System Capability
sense: SYSTEM--CAPABILITY lexSense

SYSTEM--CAPABILITY lexConcept
type: LexicalConcept
definition: 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.

System Capability
type: Form

System Computing Unit
type: LexicalEntry
type: MultiwordExpression
canonical form: System Computing Unit
sense: SYSTEM--COMPUTING--UNIT lexSense

SYSTEM--COMPUTING--UNIT lexConcept
type: LexicalConcept
definition: This is the business application, ETCS, TCMS or Cabin Voice Radio that is sending the information to be viewed on a display.

System Computing Unit
type: Form

System Configuration Data
type: LexicalEntry
type: MultiwordExpression
canonical form: System Configuration Data
sense: SYSTEM--CONFIGURATION--DATA lexSense

SYSTEM--CONFIGURATION--DATA lexConcept
type: LexicalConcept
definition: 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

System Configuration Data
type: Form

System Context
type: LexicalEntry
type: MultiwordExpression
canonical form: System Context
sense: SYSTEM--CONTEXT lexSense

SYSTEM--CONTEXT lexConcept
type: LexicalConcept
definition: Describes the system relationships and environment that exist around a system.

System Context
type: Form

SDLC
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--DEVELOPMENT--LIFE--CYCLE label
canonical form: SDLC

SYSTEM--DEVELOPMENT--LIFE--CYCLE lexConcept
type: LexicalConcept
definition: The System Development Life Cycle (SDLC) is a structured approach or methodology used in system engineering to guide the creation, deployment, and maintenance of systems. It provides a systematic framework for managing and controlling the entire process of building a system, from inception to retirement. The SDLC provides a structured approach to system development, ensuring that all necessary activities are carried out in a logical and controlled manner. It helps in managing risks, controlling costs, and delivering high-quality systems that meet stakeholder expectations.

System Development Life Cycle
type: Form

SDLC
type: Form

SEMP
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--ENGINEERING--MANAGEMENT--PLAN label
canonical form: SEMP

SYSTEM--ENGINEERING--MANAGEMENT--PLAN lexConcept
type: LexicalConcept
definition: System Engineering Management Plan

System Engineering Management Plan
type: Form

SEMP
type: Form

System Function
type: LexicalEntry
type: MultiwordExpression
canonical form: System Function
sense: SYSTEM--FUNCTION lexSense

SYSTEM--FUNCTION lexConcept
type: LexicalConcept
definition: A SPPR-2598 - Function derived during system analysis.

System Function
type: Form

System Hazard
type: LexicalEntry
type: MultiwordExpression
canonical form: System Hazard
sense: SYSTEM--HAZARD lexSense

SYSTEM--HAZARD lexConcept
type: LexicalConcept
definition: Hazard whose cause is related to a failure of one of the technical system functions/components. These hazards are managed by means of the "Hazard" Work Item.

SYSTEM--HAZARD lexConcept 2
type: LexicalConcept
definition: Hazard whose cause is related to a failure of one of the system functions/components. These hazards are managed by means of the "Hazard" Work Item.

System Hazard
type: Form

System Levels of the System Pillar
type: LexicalEntry
type: MultiwordExpression
canonical form: System Levels of the System Pillar
sense: SYSTEM--LEVELS--OF--THE--SYSTEM--PILLAR lexSense

SYSTEM--LEVELS--OF--THE--SYSTEM--PILLAR lexConcept
type: LexicalConcept
definition: The system of systems approach is used inside the System Pillar to recursively refine the structure of the architecture down to the level of subsystems. The following figure shows the decomposition of a system of systems on one consistent example spanning 5 layers of refinement. Level 5 is the actual subsystem layer and is visually integrated into the bottom layer in the following figure to be able to show the relationship to logical components. (image: 1-screenshot-20221229-202431.png) Figure {caption:Figure}: System Level 1-5 combined view

System Levels of the System Pillar
type: Form

SoS
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--OF--SYSTEMS label
canonical form: SoS

SYSTEM--OF--SYSTEMS lexConcept
type: LexicalConcept
definition: According to ISO 21839, a system of systems is set of systems that interact to provide a unique capability that none of the constituent systems can accomplish on its own. A system of systems in our understanding at least comprises two constituent systems. A system of systems itself can be nested as a constituent system in a larger system of systems, i.e. system of systems can span multiple levels recursively.{comment:1}

System Of Systems
type: Form

SoS
type: Form

SPC
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--PILLAR--COREGROUP label
canonical form: SPC

SYSTEM--PILLAR--COREGROUP lexConcept
type: LexicalConcept
definition: System Pillar Coregroup

System Pillar Coregroup
type: Form

SPC
type: Form

System Pillar deliverables
type: LexicalEntry
type: MultiwordExpression
canonical form: System Pillar deliverables
sense: SYSTEM--PILLAR--DELIVERABLES lexSense

SYSTEM--PILLAR--DELIVERABLES lexConcept
type: LexicalConcept
definition: The main output documents of the System Pillar are described in Systems Engineering Management Plan - Annex L List of System Pillar Deliverables.{comment:68}

System Pillar deliverables
type: Form

SPDT
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--PILLAR--DOMAIN--TEAM label
canonical form: SPDT

SYSTEM--PILLAR--DOMAIN--TEAM lexConcept
type: LexicalConcept
definition: System Pillar Domain Team

System Pillar Domain Team
type: Form

SPDT
type: Form

SPRA
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--PILLAR--REFERENCE--ARCHITECTURE label
canonical form: SPRA

SYSTEM--PILLAR--REFERENCE--ARCHITECTURE lexConcept
type: LexicalConcept
definition: System Pillar Reference Architecture

System Pillar Reference Architecture
type: Form

SPRA
type: Form

System Pillar Release
type: LexicalEntry
type: MultiwordExpression
canonical form: System Pillar Release
sense: SYSTEM--PILLAR--RELEASE lexSense

SYSTEM--PILLAR--RELEASE lexConcept
type: LexicalConcept
definition: A "System Pillar Release" is a baseline covering whole or part of the deliverables identified for the System Pillar project. See the SPPR-9687 - Definition of System Pillar Releases {comment:349}for more information.

System Pillar Release
type: Form

SPSG
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--PILLAR--STEERING--GROUP label
canonical form: SPSG

SYSTEM--PILLAR--STEERING--GROUP lexConcept
type: LexicalConcept
definition: System Pillar Steering Group

System Pillar Steering Group
type: Form

SPSG
type: Form

SP
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--PILLAR label
canonical form: SP

SYSTEM--PILLAR lexConcept
type: LexicalConcept
definition: System Pillar

System Pillar
type: Form

SP
type: Form

SRS
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--REQUIREMENTS--SPECIFICATION label
canonical form: SRS

SYSTEM--REQUIREMENTS--SPECIFICATION lexConcept
type: LexicalConcept
definition: System Requirements Specification

System Requirements Specification
type: Form

SRS
type: Form

System Requirement
type: LexicalEntry
type: MultiwordExpression
canonical form: System Requirement
sense: SYSTEM--REQUIREMENT lexSense

SYSTEM--REQUIREMENT lexConcept
type: LexicalConcept
definition: System requirements are precise functional or non-functional requirements for the system of interest. They are derived from the system analysis and architecture or stakeholder requirements and provide the technology-oriented view of how the system of interest shall achieve the stakeholder requirements. Except from SPPR-10493 - ISO/IEC/IEEE 29148:2018: "[...] 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."{comment:108}

System Requirement
type: Form

SuC
type: Acronym
type: LexicalEntry
acronym for: SYSTEM--UNDER--CONSIDERATION label
canonical form: SuC

SYSTEM--UNDER--CONSIDERATION lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: System under Consideration (from SPPRAMSS-334 - [EN 50129:2018/AC:2019-04])

SYSTEM--UNDER--CONSIDERATION lexConcept 3
type: LexicalConcept
definition: System under Consideration [SOURCE: SPPRAMSS-4697 - [EN IEC 62443-3-2:2020]]

System under consideration
type: Form

SuC
type: Form

SuC
type: Form

Systems
type: LexicalEntry
type: Word
canonical form: Systems
sense: SYSTEMS lexSense

SYSTEMS lexConcept
type: LexicalConcept
definition: In the context of MDS, these are operational entities that require a human-machine interface. There are several systems in a cab. In this chapter, it is proposed to present the main systems considered in this paper in order to find the characteristic to be analysed from perspective of MDS. So descriptions of ETCS, TCMS, CVR and Rearview systems are given below and give an overview of their current situation. Other systems exist, such as Electronic Timetable Display, and should also be considered. However, it is assumed that the characteristics of the systems analysed would remain applicable to the other systems. An exhaustive analysis should be carried out to be sure of the relevance of this proposal. So far, the following characteristics have been considered: ergonomics, location in the cab, SIL requirements, when visibility is required, interface between the system and the driver's display.

SYSTEMS lexConcept 2
type: LexicalConcept
definition: In the context of MDS, these are operational entities that require a human-machine interface. There are several systems in a cab. In this chapter, it is proposed to present the main systems considered in this paper in order to find thecharacteristic to be analysed from perspective of MDS. So descriptions of ETCS, TCMS, CVR and Rearview systemsare given below and give an overview of their current situation. Other systems exist, such as Electronic TimetableDisplay, and should also be considered. However, it is assumed that the characteristics of the systems analysed wouldremain applicable to the other systems. An exhaustive analysis should be carried out to be sure of the relevance of thisproposal. So far, the following characteristics have been considered: ergonomics, location in the cab, SIL requirements,when visibility is required, interface between the system and the driver's display.

Systems
type: Form

System
type: LexicalEntry
type: Word
canonical form: System
sense: SYSTEM lexSense

SYSTEM lexConcept
type: LexicalConcept
definition: 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

System
type: Form

T2OD - Task 2: Operational Design Domain
type: LexicalEntry
type: MultiwordExpression
canonical form: T2OD - Task 2: Operational Design Domain
sense: T2OD-----TASK--2---OPERATIONAL--DESIGN--DOMAIN lexSense

T2OD-----TASK--2---OPERATIONAL--DESIGN--DOMAIN lexConcept
type: LexicalConcept
definition: Task 2: Operational Design Domain can be abbreviated as 'T2OD'.

T2OD - Task 2: Operational Design Domain
type: Form

TAP - Telematics Application for Passenger Service
type: LexicalEntry
type: MultiwordExpression
canonical form: TAP - Telematics Application for Passenger Service
sense: TAP-----TELEMATICS--APPLICATION--FOR--PASSENGER--SERVICE lexSense

TAP-----TELEMATICS--APPLICATION--FOR--PASSENGER--SERVICE lexConcept
type: LexicalConcept
definition: TAP - Telematics Application for Passenger Service

TAP - Telematics Application for Passenger Service
type: Form

target picture
type: LexicalEntry
type: MultiwordExpression
canonical form: target picture
sense: TARGET--PICTURE lexSense

TARGET--PICTURE lexConcept
type: LexicalConcept
definition: The following are considered minimum characteristics (baseline) for the targeted solution: * Operational production processes directly related to the railway traffic commercial production are harmonised. This includes ETCS related processes, processes for securing and releasing railway lines/areas to/from maintenance and commissioning, operating through and recovering from degraded (non-regular) operations, reacting to and managing emergency situations (from operational perspective). * Railway system operates ETCS L2, without signals. * Railway system operates EULYNX type equipment.

target picture
type: Form

Target System
type: LexicalEntry
type: MultiwordExpression
canonical form: Target System
sense: TARGET--SYSTEM lexSense

TARGET--SYSTEM lexConcept
type: LexicalConcept
definition: the target architecture of the signalling system as a whole

Target System
type: Form

T
type: Acronym
type: LexicalEntry
acronym for: TASK label
canonical form: T

TASK lexConcept
type: LexicalConcept
definition: A Task implements part of the functionality provided by a Functional Application. Depending on its role in the overall function provided by the Functional Application, it has a specific SIL assigned (in-line with total FA SIL definition). It may run replicated in multiple Compartments as Task Replicas. Previous definition: A Functional Application Task implements part of the functionality provided by a Functional Application. Depending on its role in the overall function provided by the Functional Application, it has a specific SIL assigned (in-line with total FA SIL definition). It may run replicated in multiple Compartments as FA Task Replicas.

TASK lexConcept 2
type: LexicalConcept
definition: The planning hierarchy is Release>Project Milestone>Work Package>Task

Task
type: Form

T
type: Form

TCMS (TDD display)
type: LexicalEntry
type: MultiwordExpression
canonical form: TCMS (TDD display)
sense: TCMS--TDD--DISPLAY lexSense

TCMS--TDD--DISPLAY lexConcept
type: LexicalConcept
definition: The display associated to this system is called TDD (Technical and Diagnostic Display) in UIC-612. The ergonomics of this system is also defined in UIC-612-3.The TDD is located on the right side of the cab according to UIC-612-0, EN 16186-2 (chapter 7.21). Depending of the configuration of the train, the SIL associated to TDD could be SIL2 (when safety related information are only displayed on TDD) or SIL0 / Basic Integrity (when safety related information is presented on TDD and also with safe lights in cab). According to EN 16186-3 (table B.2), if existing, some information is mandatory for high speed class 1 trains. Otherwise, other information is optional. Current communication between TCMS and TDD is supplier-specific. To facilitate the deployment of the MDS solution, a migration to a generic communication used also by other systems should be considered.

TCMS--TDD--DISPLAY lexConcept 2
type: LexicalConcept
definition: The display associated to this system is called TDD (Technical and Diagnostic Display) in UIC-612. The ergonomics ofthis system is also defined in UIC-612-3.The TDD is located on the right side of the cab according to UIC-612-0, EN 16186-2 (chapter 7.21).Depending of the configuration of the train, the SIL associated to TDD could be SIL2 (when safety related informationare only displayed on TDD) or SIL0 / Basic Integrity (when safety related information is presented on TDD and also withsafe lights in cab).According EN 16186-3 (table B.2), if existing, some information is mandatory for high speed class 1 trains. Otherwise,other information is optional.Current communication between TCMS and TDD is supplier-specific. To facilitate the deployment of the MDS solution, a migration to a generic communication used also by other systems should be considered.

TCMS (TDD display)
type: Form

TCO
type: LexicalEntry
type: Word
canonical form: TCO
sense: TCO lexSense

TCO lexConcept
type: LexicalConcept
definition: Total Cost of Ownership

TCO
type: Form

TC
type: Acronym
type: LexicalEntry
acronym for: TECHNICAL--COMMITTEE label
canonical form: TC

TECHNICAL--COMMITTEE lexConcept
type: LexicalConcept
definition: Technical Committee

Technical Committee
type: Form

TC
type: Form

technical delay
type: LexicalEntry
type: MultiwordExpression
canonical form: technical delay
sense: TECHNICAL--DELAY lexSense

TECHNICAL--DELAY lexConcept
type: LexicalConcept
definition: delay incurred in performing auxiliary technical actions associated with, but not part of, the maintenance action EXAMPLE Rendering the equipment safe (such as immobilising, cooling, isolation and grounding). [SOURCE: IEC 60050-192:2015,192-07-15]

technical delay
type: Form

TD
type: Acronym
type: LexicalEntry
acronym for: TECHNICAL--DOCUMENT label
canonical form: TD

TECHNICAL--DOCUMENT lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Technical Document

Technical Document
type: Form

TD
type: Form

TRL
type: Acronym
type: LexicalEntry
acronym for: TECHNICAL--READINESS--LEVELS label
canonical form: TRL

TECHNICAL--READINESS--LEVELS lexConcept
type: LexicalConcept
definition: TRL 1: Basic Principles Observed TRL 2: Technology Concept and/or Application Formulated TRL 3: Experimental Proof of Concept TRL 4: Technology Validated in Laboratory TRL 5: Technology Validated in Relevant Environment TRL 6: Technology Demonstrated in Relevant Environment TRL 7: System Prototype Demonstration in Operational Environment TRL 8: System Complete and Qualified Through Test and Demonstration TRL 9: Actual System Proven in Operational Environment

Technical readiness levels
type: Form

TRL
type: Form

TSI
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TECHNICAL--SPECIFICATION--FOR--INTEROPERABILITY label
canonical form: TSI

TECHNICAL--SPECIFICATION--FOR--INTEROPERABILITY lexConcept
type: LexicalConcept
definition: Technical Specification for Interoperability

Technical Specification for Interoperability
type: Form

TSI
type: Form

TSI
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TECHNICAL--SPECIFICATIONS--FOR--INTEROPERABILITY label
canonical form: TSI

TECHNICAL--SPECIFICATIONS--FOR--INTEROPERABILITY lexConcept
type: LexicalConcept
definition: Technical Specifications for Interoperability

Technical Specifications for Interoperability
type: Form

TSI
type: Form

Technical user
type: LexicalEntry
type: MultiwordExpression
canonical form: Technical user
sense: TECHNICAL--USER lexSense

TECHNICAL--USER lexConcept
type: LexicalConcept
definition: A technical user is either a software process or device

Technical user
type: Form

TOBA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TELECOM--ON-BOARD--ARCHITECTURE label
canonical form: TOBA

TELECOM--ON-BOARD--ARCHITECTURE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Telecom On-Board Architecture

Telecom On-Board Architecture
type: Form

TOBA
type: Form

TAF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TELEMATIC--APPLICATIONS--FOR--FREIGHT label
canonical form: TAF

TELEMATIC--APPLICATIONS--FOR--FREIGHT lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Telematic Applications for Freight

Telematic Applications for Freight
type: Form

TAF
type: Form

TAP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TELEMATIC--APPLICATIONS--FOR--PASSENGER label
canonical form: TAP

TELEMATIC--APPLICATIONS--FOR--PASSENGER lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Telematic Applications for Passenger

Telematic Applications for Passenger
type: Form

TAP
type: Form

TAF/TAP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TELEMATICS--APPLICATIONS--FOR--FREIGHT PASSENGER--SERVICES label
canonical form: TAF/TAP

TELEMATICS--APPLICATIONS--FOR--FREIGHT PASSENGER--SERVICES lexConcept
type: LexicalConcept
definition: Telematics Applications for Freight/Passenger Services

Telematics Applications for Freight/Passenger Services
type: Form

TAF/TAP
type: Form

TAF
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TELEMATICS--APPLICATIONS--FOR--FREIGHT label
canonical form: TAF

TELEMATICS--APPLICATIONS--FOR--FREIGHT lexConcept
type: LexicalConcept
definition: Telematics Applications for Freight

Telematics Applications for Freight
type: Form

TAF
type: Form

TAP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TELEMATICS--APPLICATIONS--FOR--PASSENGER--SERVICES label
canonical form: TAP

TELEMATICS--APPLICATIONS--FOR--PASSENGER--SERVICES lexConcept
type: LexicalConcept
definition: Telematics Applications for Passenger Services

Telematics Applications for Passenger Services
type: Form

TAP
type: Form

TCR
type: Acronym
type: LexicalEntry
acronym for: TEMPORARY--CAPACITY--RESTRICTIONS label
canonical form: TCR

TEMPORARY--CAPACITY--RESTRICTIONS lexConcept
type: LexicalConcept
definition: Temporary Capacity Restrictions

Temporary Capacity Restrictions
type: Form

TCR
type: Form

Temporary Shunting Area (TShA)
type: LexicalEntry
type: MultiwordExpression
canonical form: Temporary Shunting Area (TShA)
sense: TEMPORARY--SHUNTING--AREA--TSHA lexSense

TEMPORARY--SHUNTING--AREA--TSHA lexConcept
type: LexicalConcept
definition: Temporary Shunting Area (TShA) A temporary shunting area is an interlocked area{comment:15} temporarily set up to allow shunting operations. A temporary shunting area is always under the responsibility of a Shunting area manager. (OR.DEF.161 - Banedanmark)

Temporary Shunting Area (TShA)
type: Form

TO
type: Acronym
type: LexicalEntry
acronym for: TERMINAL--OPERATOR label
canonical form: TO

TERMINAL--OPERATOR lexConcept
type: LexicalConcept
definition: Terminal operator

Terminal operator
type: Form

TO
type: Form

Test Case
type: LexicalEntry
type: MultiwordExpression
canonical form: Test Case
sense: TEST--CASE lexSense

TEST--CASE lexConcept
type: LexicalConcept
definition: Set of test inputs, conditions, and expected results developed to verify compliance with a specific system requirement.

Test Case
type: Form

Testability
type: LexicalEntry
type: Word
canonical form: Testability
sense: TESTABILITY lexSense

TESTABILITY lexConcept
type: LexicalConcept
definition: A sub-system that is designed for testability will be ready to show that it fulfils the requirements needed by the overall system. Testability is not an attribute of the sub-system/module itself but has to be designed into architecture and interfaces.{comment:1299}

Testability
type: Form

Text.
type: LexicalEntry
type: Word
canonical form: Text.
sense: TEXT lexSense

TEXT lexConcept
type: LexicalConcept
definition: Used for any type of sketching, non-papers, protocols, etc.

Text.
type: Form

The destination is a location, where
type: LexicalEntry
type: MultiwordExpression
canonical form: The destination is a location, where
sense: THE--DESTINATION--IS--A--LOCATION--WHERE lexSense

THE--DESTINATION--IS--A--LOCATION--WHERE lexConcept
type: LexicalConcept
definition: The destination is a location, where * the train changes its direction * the train characteristics are changed * the mission ends by a verbal or written order * a problem with the vehicle or the infrastructure obstructs further movement

The destination is a location, where
type: Form

The driver is an operational actor. He is in charge of (un)preparing and driving...
type: LexicalEntry
type: MultiwordExpression
canonical form: The driver is an operational actor. He is in charge of (un)preparing and driving...
sense: THE--DRIVER--IS--AN--OPERATIONAL--ACTOR---HE--IS--IN--CHARGE--OF--UN--PREPARING--AND--DRIVING lexSense

THE--DRIVER--IS--AN--OPERATIONAL--ACTOR---HE--IS--IN--CHARGE--OF--UN--PREPARING--AND--DRIVING lexConcept
type: LexicalConcept
definition: The driver is an operational actor. He is in charge of (un)preparing and driving trains. The main tasks of this actor are: activate/deactivate the cab, activate/deactivate systems, configure displays on the cab and operate systems.

THE--DRIVER--IS--AN--OPERATIONAL--ACTOR---HE--IS--IN--CHARGE--OF--UN--PREPARING--AND--DRIVING lexConcept 2
type: LexicalConcept
definition: The driver is an operational actor. He is in charge of (un)preparing and driving trains. The main tasks of this actor are: activate/deactivate the cab, activate/deactivate systems, configure displays on the cab and operate systems.

The driver is an operational actor. He is in charge of (un)preparing and driving...
type: Form

The set of all traces together is called a “model”.
type: LexicalEntry
type: MultiwordExpression
canonical form: The set of all traces together is called a “model”.
sense: THE--SET--OF--ALL--TRACES--TOGETHER--IS--CALLED--A-- MODEL lexSense

THE--SET--OF--ALL--TRACES--TOGETHER--IS--CALLED--A-- MODEL lexConcept
type: LexicalConcept
definition: The set of all traces together is called a “model”.

The set of all traces together is called a “model”.
type: Form

The Start of Mission (SoM) is the ETCS-start. The driver prepares with the SoM t...
type: LexicalEntry
type: MultiwordExpression
canonical form: The Start of Mission (SoM) is the ETCS-start. The driver prepares with the SoM t...
sense: THE--START--OF--MISSION--SOM--IS--THE--ETCS-START---THE--DRIVER--PREPARES--WITH--THE--SOM--T lexSense

THE--START--OF--MISSION--SOM--IS--THE--ETCS-START---THE--DRIVER--PREPARES--WITH--THE--SOM--T lexConcept
type: LexicalConcept
definition: The Start of Mission (SoM) is the ETCS-start. The driver prepares with the SoM the train for the mission. Training info: The SoM starts with the activation of the cab. Required input for the SoM is: * Driver Id * Train running number * ETCS-Level and RBC contact * Train data SoM is completed by pressing "Start" in the DMI (image: 1-screenshot-20250930-144308-14.png)

The Start of Mission (SoM) is the ETCS-start. The driver prepares with the SoM t...
type: Form

The term "railway" is the common definition of Infra managers, undertakings and...
type: LexicalEntry
type: MultiwordExpression
canonical form: The term "railway" is the common definition of Infra managers, undertakings and...
sense: THE--TERM-- RAILWAY --IS--THE--COMMON--DEFINITION--OF--INFRA--MANAGERS--UNDERTAKINGS--AND lexSense

THE--TERM-- RAILWAY --IS--THE--COMMON--DEFINITION--OF--INFRA--MANAGERS--UNDERTAKINGS--AND lexConcept
type: LexicalConcept
definition: The term "railway" is the common definition of Infra managers, undertakings and vehicle owners in this document.

The term "railway" is the common definition of Infra managers, undertakings and...
type: Form

The term "railway" refers to the definition of the "asset owner" of IEC 62443-2-...
type: LexicalEntry
type: MultiwordExpression
canonical form: The term "railway" refers to the definition of the "asset owner" of IEC 62443-2-...
sense: THE--TERM-- RAILWAY --REFERS--TO--THE--DEFINITION--OF--THE-- ASSET--OWNER --OF--IEC--62443-2 lexSense

THE--TERM-- RAILWAY --REFERS--TO--THE--DEFINITION--OF--THE-- ASSET--OWNER --OF--IEC--62443-2 lexConcept
type: LexicalConcept
definition: The term "railway" refers to the definition of the "asset owner" of IEC 62443-2-1.

The term "railway" refers to the definition of the "asset owner" of IEC 62443-2-...
type: Form

The train characteristics include the mandatory information on the technical cha...
type: LexicalEntry
type: MultiwordExpression
canonical form: The train characteristics include the mandatory information on the technical cha...
sense: THE--TRAIN--CHARACTERISTICS--INCLUDE--THE--MANDATORY--INFORMATION--ON--THE--TECHNICAL--CHA lexSense

THE--TRAIN--CHARACTERISTICS--INCLUDE--THE--MANDATORY--INFORMATION--ON--THE--TECHNICAL--CHA lexConcept
type: LexicalConcept
definition: The train characteristics include the mandatory information on the technical characteristics of trains. Trainingsinfo: Train characertistics could be: * Length (train) * Weight (train) * Locomotive class * vmax * Braking percentage / Brake weight * Automatic Train Protection * Differences from standard dimensions * Oversized vehicles (OBVs) * Route class

The train characteristics include the mandatory information on the technical cha...
type: Form

3GPP
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: THIRD--GENERATION--PARTNERSHIP--PROJECT label
canonical form: 3GPP

THIRD--GENERATION--PARTNERSHIP--PROJECT lexConcept
type: LexicalConcept
definition: Third Generation Partnership Project

Third Generation Partnership Project
type: Form

3GPP
type: Form

Threat landscape
type: LexicalEntry
type: MultiwordExpression
canonical form: Threat landscape
sense: THREAT--LANDSCAPE lexSense

THREAT--LANDSCAPE lexConcept
type: LexicalConcept
definition: Threat landscape is used in this document as synonym for threat environment. Threat environment (definition from CENELEC TS 50701, IEC PT 63452) environment summary of information about threats, such as threat sources, threat vectors and trends, that have the potential to adversely impact a defined target (for example a company, facility or SuC)

Threat landscape
type: Form

TI Train integrity
type: LexicalEntry
type: MultiwordExpression
canonical form: TI Train integrity
sense: TI--TRAIN--INTEGRITY lexSense

TI--TRAIN--INTEGRITY lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: TI Train integrity

TI Train integrity
type: Form

Timeframe
type: LexicalEntry
type: Word
canonical form: Timeframe
sense: TIMEFRAME lexSense

TIMEFRAME lexConcept
type: LexicalConcept
definition: amount of years for a certain level of equipment or migration phase

Timeframe
type: Form

Timestamp
type: LexicalEntry
type: Word
canonical form: Timestamp
sense: TIMESTAMP lexSense

TIMESTAMP lexConcept
type: LexicalConcept
definition: The date and time formatted in YYYY-MM-DD hh:mm:ss.SSSZ as per ISO 8601{comment:74}

Timestamp
type: Form

Timetable
type: LexicalEntry
type: Word
canonical form: Timetable
sense: TIMETABLE lexSense

TIMETABLE lexConcept
type: LexicalConcept
definition: Document or system that gives details of a train(s) schedule over a particular route (OPE TSI appendix J) This definition can be completed by the RNE definition: ' A schedule listing the times at which certain events, such as arrivals and departures at a transport station, are expected to take place. The timetable defines all planned train and rolling-stock movements which will take place on the relevant infrastructure during the period for which it is in force. Example: “annual timetable” (“yearly timetable” is incorrect)’

Timetable
type: Form

TIMS - Train Integrity Management System
type: LexicalEntry
type: MultiwordExpression
canonical form: TIMS - Train Integrity Management System
sense: TIMS-----TRAIN--INTEGRITY--MANAGEMENT--SYSTEM lexSense

TIMS-----TRAIN--INTEGRITY--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: TIMS - Train Integrity Management System

TIMS - Train Integrity Management System
type: Form

TL Train length
type: LexicalEntry
type: MultiwordExpression
canonical form: TL Train length
sense: TL--TRAIN--LENGTH lexSense

TL--TRAIN--LENGTH lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: TL Train length

TL Train length
type: Form

TLS endpoint
type: LexicalEntry
type: MultiwordExpression
canonical form: TLS endpoint
sense: TLS--ENDPOINT lexSense

TLS--ENDPOINT lexConcept
type: LexicalConcept
definition: The TLS endpoint is a Secure Component using TLS-protected communication (client and server).

TLS endpoint
type: Form

TO BE REUSED
type: LexicalEntry
type: MultiwordExpression
canonical form: TO BE REUSED
sense: TO--BE--REUSED lexSense

TO--BE--REUSED lexConcept
type: LexicalConcept
definition: The degree of smoothness and steadiness of acceleration of a vehicle.

TO BE REUSED
type: Form

Tool Requirement.
type: LexicalEntry
type: MultiwordExpression
canonical form: Tool Requirement.
sense: TOOL--REQUIREMENT lexSense

TOOL--REQUIREMENT lexConcept
type: LexicalConcept
definition: Used to store issues for the optimisation of Polarion

Tool Requirement.
type: Form

Tool
type: LexicalEntry
type: Word
canonical form: Tool
sense: TOOL lexSense

TOOL lexConcept
type: LexicalConcept
definition: An instrument that, when applied to a particular method, can enhance the efficiency of the task, provided it is applied properly and by somebody with proper skills and training.{comment:409}

Tool
type: Form

TWG
type: Acronym
type: LexicalEntry
acronym for: TOPICAL--WORKING--GROUP label
canonical form: TWG

TOPICAL--WORKING--GROUP lexConcept
type: LexicalConcept
definition: Topical Working Group

Topical Working Group
type: Form

TWG
type: Form

Touch Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Touch Controller
sense: TOUCH--CONTROLLER lexSense

TOUCH--CONTROLLER lexConcept
type: LexicalConcept
definition: Controller which manages the states and failures of a Touch Panel.

TOUCH--CONTROLLER lexConcept 2
type: LexicalConcept
definition: Controller which manages the states and failures of a Touch Panel.

TOUCH--CONTROLLER lexConcept 3
type: LexicalConcept
definition: Controller which manages the states and failures of a Touch Panel.

TOUCH--CONTROLLER lexConcept 4
type: LexicalConcept
definition: Controller which manages the states and failures of a Touch Panel.

TOUCH--CONTROLLER lexConcept 5
type: LexicalConcept
definition: Controller which manages the states and failures of a Touch Panel.

TOUCH--CONTROLLER lexConcept 6
type: LexicalConcept
definition: Controller which manages the states and failures of a {comment:92}Touch Panel.

TOUCH--CONTROLLER lexConcept 7
type: LexicalConcept
definition: Controller which manages the states and failures of a Touch Panel.

TOUCH--CONTROLLER lexConcept 8
type: LexicalConcept
definition: Touch Controller Controller which manages the states and failures of a Touch Panel.

Touch Controller
type: Form

Touch Panel
type: LexicalEntry
type: MultiwordExpression
canonical form: Touch Panel
sense: TOUCH--PANEL lexSense

TOUCH--PANEL lexConcept
type: LexicalConcept
definition: Hardware detecting where the finger touches the panel. Sometimes called Touch Display as well.

TOUCH--PANEL lexConcept 2
type: LexicalConcept
definition: Hardware detecting where the finger touches the panel. Sometimes called Touch Display as well.

TOUCH--PANEL lexConcept 3
type: LexicalConcept
definition: Hardware detecting where the finger touches the panel.

TOUCH--PANEL lexConcept 4
type: LexicalConcept
definition: Hardware detecting where the finger touches the panel.

TOUCH--PANEL lexConcept 5
type: LexicalConcept
definition: Hardware detecting where the finger touches the panel.

Touch Panel
type: Form

Track Change
type: LexicalEntry
type: MultiwordExpression
canonical form: Track Change
sense: TRACK--CHANGE lexSense

TRACK--CHANGE lexConcept
type: LexicalConcept
definition: To change the assigned track to a train while maintaining the same journey stops

Track Change
type: Form

Track elements are movable elements, track sections, level crossings.
type: LexicalEntry
type: MultiwordExpression
canonical form: Track elements are movable elements, track sections, level crossings.
sense: TRACK--ELEMENTS--ARE--MOVABLE--ELEMENTS--TRACK--SECTIONS--LEVEL--CROSSINGS lexSense

TRACK--ELEMENTS--ARE--MOVABLE--ELEMENTS--TRACK--SECTIONS--LEVEL--CROSSINGS lexConcept
type: LexicalConcept
definition: Track elements are movable elements, track sections, level crossings.

Track elements are movable elements, track sections, level crossings.
type: Form

Track Topology
type: LexicalEntry
type: MultiwordExpression
canonical form: Track Topology
sense: TRACK--TOPOLOGY lexSense

TRACK--TOPOLOGY lexConcept
type: LexicalConcept
definition: The 'Track Topology' is part of the railway infrastructure and defines the tracks and connections that allow trains to travel from one track to the next.

Track Topology
type: Form

Trackbound Object
type: LexicalEntry
type: MultiwordExpression
canonical form: Trackbound Object
sense: TRACKBOUND--OBJECT lexSense

TRACKBOUND--OBJECT lexConcept
type: LexicalConcept
definition: A Trackbound Object is composed of one or several railway vehicles that are physically linked together, that can only move on the railway track.

Trackbound Object
type: Form

TACS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TRACKSIDE--ASSETS--CONTROL--AND--SUPERVISION label
canonical form: TACS

TRACKSIDE--ASSETS--CONTROL--AND--SUPERVISION lexConcept
type: LexicalConcept
definition: The scope of the system Trackside assets control and supervision is the layer with trackside assets and respective objects controllers. The system is responsible for the control and supervision of the trackside assets to ensure safe track usage as required by the system Traffic Control and Supervision. The system supports diagnostic, maintenance and security functions as required by the system Transversal CCS.

Trackside Assets Control and Supervision
type: Form

TACS
type: Form

Trackside Assets
type: LexicalEntry
type: MultiwordExpression
canonical form: Trackside Assets
sense: TRACKSIDE--ASSETS lexSense

TRACKSIDE--ASSETS lexConcept
type: LexicalConcept
definition: All technical systems and products that are necessary for safe train operation from infrastructure perspective that are not located in the train.

Trackside Assets
type: Form

TA
type: Acronym
type: LexicalEntry
acronym for: TRACKSIDE--ASSET label
canonical form: TA

TRACKSIDE--ASSET lexConcept
type: LexicalConcept
definition: Trackside Assets are elements on or near the track which are used to monitor (using sensors) and/or control (using actuators) the movement of vehicles through the railway network to provide a safe route through the railway network. They can be switchable or non-switchable and are controlled by the actors Trackside Asset Control and Supervision.

Trackside Asset
type: Form

TA
type: Form

TTD
type: Acronym
type: LexicalEntry
acronym for: TRACKSIDE--TRAIN--DETECTION label
canonical form: TTD

TRACKSIDE--TRAIN--DETECTION lexConcept
type: LexicalConcept
definition: Trackside Train Detection is a system which determines the occupancy status of TTD sections. TTD section may be a Track Circuit or an Axle Counting system section. EULYNX synonym for TTD section: Track Vacancy Proving Section (TVPS)

Trackside Train Detection
type: Form

TTD
type: Form

traction unit
type: LexicalEntry
type: MultiwordExpression
canonical form: traction unit
sense: TRACTION--UNIT lexSense

TRACTION--UNIT lexConcept
type: LexicalConcept
definition: A powered railway vehicle able to move itself and other railway vehicles to which it may be coupled

TRACTION--UNIT lexConcept 2
type: LexicalConcept
definition: Traction Unit -

traction unit
type: Form

Tradeoff points
type: LexicalEntry
type: MultiwordExpression
canonical form: Tradeoff points
sense: TRADEOFF--POINTS lexSense

TRADEOFF--POINTS lexConcept
type: LexicalConcept
definition: Tradeoff points are architectural elements that affect different quality attributes simultaneously or architectural element to which multiple quality attributes are sensitive.

Tradeoff points
type: Form

TCCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TRAFFIC--CONTROL--AND--COMMAND--SYSTEM label
canonical form: TCCS

TRAFFIC--CONTROL--AND--COMMAND--SYSTEM lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Traffic Control and Command System

Traffic Control and Command System
type: Form

TCCS
type: Form

Traffic CS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TRAFFIC--CONTROL--AND--SUPERVISION label
canonical form: Traffic CS

TRAFFIC--CONTROL--AND--SUPERVISION lexConcept
type: LexicalConcept
definition: Traffic Control and Supervision is the CSS Trackside System in charge of the control and supervision of the Railways Traffic. It includes ETCS Trackside and ATO Trackside.

Traffic Control and Supervision
type: Form

Traffic CS
type: Form

TMS
type: Acronym
type: LexicalEntry
acronym for: TRAFFIC--MANAGEMENT--SYSTEM label
canonical form: TMS

TRAFFIC--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: Traffic Management System

TRAFFIC--MANAGEMENT--SYSTEM lexConcept 2
type: LexicalConcept
definition: 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 lexConcept 3
type: LexicalConcept
definition: Traffic Management System

Traffic Management System
type: Form

TMS
type: Form

TMS
type: Form

TMS
type: Form

Traffic Management
type: LexicalEntry
type: MultiwordExpression
canonical form: Traffic Management
sense: TRAFFIC--MANAGEMENT lexSense

TRAFFIC--MANAGEMENT lexConcept
type: LexicalConcept
definition: Traffic management shall ensure the safe, efficient and punctual operation of the railway, including effective recovery from service disruption. The infrastructure manager shall determine procedures and means for: — the real time management of trains, — operational measures to maintain the highest possible performance of the infrastructure in case of delays or incidents, whether actual or anticipated, and — the provision of information to the railway undertaking(s) in such cases. Any additional processes required by the railway undertaking and which affect the interface with the infrastructure manager(s) may be introduced after being agreed with the infrastructure manager.

Traffic Management
type: Form

Traffic Monitoring
type: LexicalEntry
type: MultiwordExpression
canonical form: Traffic Monitoring
sense: TRAFFIC--MONITORING lexSense

TRAFFIC--MONITORING lexConcept
type: LexicalConcept
definition: The monitoring of railway traffic involves systematically keeping track of (or supervising) and collecting information concerning parameters such as: train location, train speed, train direction. It uses uses graphical systems. The main graphic screens of these systems show two kinds of diagrams: train tracks and train schedules. Train track diagrams indicate the actual layout of railway tracks, signals, stations, and so on. They indicate the current position of trains, the condition of signals, the direction of switches, and so on, using simplified drawings of actual railway tracks and signals. To notify operators of this information, the color of tracks and signals are displayed, and a train's number is displayed in text that dynamically changes according to supervisory data. Train schedule diagrams consist of lines which correspond to the movements of trains, train numbers for each train line, and horizontal lines which show the positions of stations. They are presented as charts that illustrate train movements in actual time depicted along a horizontal axis.

Traffic Monitoring
type: Form

Train Activate
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Activate
sense: TRAIN--ACTIVATE lexSense

TRAIN--ACTIVATE lexConcept
type: LexicalConcept
definition: Activate a deactivated train

Train Activate
type: Form

Train composition:
type: LexicalEntry
type: MultiwordExpression
canonical form: Train composition:
sense: TRAIN--COMPOSITION lexSense

TRAIN--COMPOSITION lexConcept
type: LexicalConcept
definition: Train composition: Train composition is the sequence of vehicles in a train. This means both the formation of vehicles within a train and their specific vehicle characteristics.

Train composition:
type: Form

Train Consist Change
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Consist Change
sense: TRAIN--CONSIST--CHANGE lexSense

TRAIN--CONSIST--CHANGE lexConcept
type: LexicalConcept
definition: Add and/or remove wagons from the train or any other attribute in the train consist

Train Consist Change
type: Form

TCMS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TRAIN--CONTROL--AND--MANAGEMENT--SYSTEM label
canonical form: TCMS

TRAIN--CONTROL--AND--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: TCMS - Train Control & Management System

Train Control & Management System
type: Form

TCMS
type: Form

TCMS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TRAIN--CONTROL--AND--MONITORING--SYSTEM label
canonical form: TCMS

TRAIN--CONTROL--AND--MONITORING--SYSTEM lexConcept
type: LexicalConcept
definition: Train Control and Monitoring System

Train Control and Monitoring System
type: Form

TCMS
type: Form

Train crew
type: LexicalEntry
type: MultiwordExpression
canonical form: Train crew
sense: TRAIN--CREW lexSense

TRAIN--CREW lexConcept
type: LexicalConcept
definition: Members of the on-board staff of a train, who are certified as competent and appointed by a railway undertaking to carry out specific, designated safety related tasks on the train, for example the driver or the guard.

Train crew
type: Form

Train Deactivate
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Deactivate
sense: TRAIN--DEACTIVATE lexSense

TRAIN--DEACTIVATE lexConcept
type: LexicalConcept
definition: Deactivate an active/ standby train

Train Deactivate
type: Form

Train Dispatcher: A Train Dispatcher is an Infrastructure Manager operator that...
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Dispatcher: A Train Dispatcher is an Infrastructure Manager operator that...
sense: TRAIN--DISPATCHER---A--TRAIN--DISPATCHER--IS--AN--INFRASTRUCTURE--MANAGER--OPERATOR--THAT lexSense

TRAIN--DISPATCHER---A--TRAIN--DISPATCHER--IS--AN--INFRASTRUCTURE--MANAGER--OPERATOR--THAT lexConcept
type: LexicalConcept
definition: Train Dispatcher: A Train Dispatcher is an Infrastructure Manager operator that acts from a workstation in the Control Room in order to direct and facilitate the movement of trains over an assigned territory, which is usually part, or all, of a railroad operating division. The dispatcher is also responsible for cost effective movement of trains and other on-track railroad equipment to optimize physical (trains) and human resource (crews) assets.”

Train Dispatcher: A Train Dispatcher is an Infrastructure Manager operator that...
type: Form

Train dispatch
type: LexicalEntry
type: MultiwordExpression
canonical form: Train dispatch
sense: TRAIN--DISPATCH lexSense

TRAIN--DISPATCH lexConcept
type: LexicalConcept
definition: The indication to the person driving the train that all station or depot activities are completed and that, as far as the staff responsible are concerned, movement authority has been granted for the train.

Train dispatch
type: Form

Train Display System Controller
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Display System Controller
sense: TRAIN--DISPLAY--SYSTEM--CONTROLLER lexSense

TRAIN--DISPLAY--SYSTEM--CONTROLLER lexConcept
type: LexicalConcept
definition: The TDS Controller interacts with systems (CCS, TCMS,CVR...) and manages the Desk Display Area.

TRAIN--DISPLAY--SYSTEM--CONTROLLER lexConcept 2
type: LexicalConcept
definition: 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 lexConcept 3
type: LexicalConcept
definition: The TDS Controller interacts with system (CCS, TCMS,CVR) and manages the Desk Display Area.

TRAIN--DISPLAY--SYSTEM--CONTROLLER lexConcept 4
type: LexicalConcept
definition: Train Display System Controller The TDS Controller interacts with system (CCS, TCMS,CVR) and manages the Desk Display Area.

Train Display System Controller
type: Form

Train Display System (TDS)
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Display System (TDS)
sense: TRAIN--DISPLAY--SYSTEM--TDS lexSense

TRAIN--DISPLAY--SYSTEM--TDS lexConcept
type: LexicalConcept
definition: Train Display System (TDS) The Train Display System is the train cab display system that comprises and manages one or more displays on the driver desk and a driver interface. It is composed of at least one display with the associated input devices, at least one loudspeaker and at least one Train Display System Controller. It offers a standardised communication interface to systems that need driver interaction.

Train Display System (TDS)
type: Form

Train Display System Unit
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Display System Unit
sense: TRAIN--DISPLAY--SYSTEM--UNIT lexSense

TRAIN--DISPLAY--SYSTEM--UNIT lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Train Display System Unit

Train Display System Unit
type: Form

TDS
type: Acronym
type: LexicalEntry
acronym for: TRAIN--DISPLAY--SYSTEM label
canonical form: TDS

TRAIN--DISPLAY--SYSTEM lexConcept
type: LexicalConcept
definition: The Train Display System is the train cab display system that comprises and manages one or more displays on the driver desk and a driver interface. It is composed of at least one display with the associated input devices, at least one loudspeaker and at least one Display Manager. It offers a standardised communication interface to systems that need driver interaction.

TRAIN--DISPLAY--SYSTEM lexConcept 2
type: LexicalConcept
definition: The Train Display System is the train cab display system that comprises and manages one or more displays on the driver desk and a driver interface. It is composed of at least one display with the associated input devices, at least one loudspeaker and at least one Display Manager. It offers a standardised communication interface to systems that need driver interaction.

TRAIN--DISPLAY--SYSTEM lexConcept 3
type: LexicalConcept
definition: The Train Display System is the train cab display system that comprises and manages one or more displays on the driver desk and a driver interface. It is composed of at least one display with the associated input devices, at least one loudspeaker and at least one Train Display System Controller. It offers a standardised communication interface to systems that need driver interaction.

TRAIN--DISPLAY--SYSTEM lexConcept 4
type: LexicalConcept
definition: The Train Display System is the train cab display system that comprises and manages one or more{comment:131} displays on the driver desk and a driver interface. It is composed of at least one display with the associated input devices, at least one loudspeaker and at least one Train Display System Controller. It offers {comment:93}a standardised communication interface to systems that need driver interaction.

TRAIN--DISPLAY--SYSTEM lexConcept 5
type: LexicalConcept
definition: The Train Display System is the train cab display system that comprises and manages one or more displays on the driver desk and a driver interface. It is composed of at least one display with the associated input devices, at least one loudspeaker and at least one Train Display System Controller. It offers a standardised communication interface to systems that need driver interaction.

TRAIN--DISPLAY--SYSTEM lexConcept 6
type: LexicalConcept
definition: TDS - Train Display System

Train Display System
type: Form

TDS
type: Form

TDS
type: Form

TDS
type: Form

TDS
type: Form

TDS
type: Form

Train Driver
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Driver
sense: TRAIN--DRIVER lexSense

TRAIN--DRIVER lexConcept
type: LexicalConcept
definition: Train driver means a person capable and authorized to drive trains, including locomotives, shunting locomotives, work trains, maintenance railway vehicles or trains for the carriage of passengers or goods by rail in an autonomous, responsible and safe manner.

Train Driver
type: Form

Train dynamic data
type: LexicalEntry
type: MultiwordExpression
canonical form: Train dynamic data
sense: TRAIN--DYNAMIC--DATA lexSense

TRAIN--DYNAMIC--DATA lexConcept
type: LexicalConcept
definition: Train axles, train length, train size and train wagons are considered train dynamic data.

Train dynamic data
type: Form

Train front end
type: LexicalEntry
type: MultiwordExpression
canonical form: Train front end
sense: TRAIN--FRONT--END lexSense

TRAIN--FRONT--END lexConcept
type: LexicalConcept
definition: It is represented by a point on the carriage floor along the longitudinal axis. This point is the most forward element belonging to the engine with regards to the train orientation.  For the absolute position it is expressed in a geocoordinate reference frame . Note: if the ASTP is not installed in the first vehicle, the absolute position is given from carriage front end where the ASTP is installed.  For the 1D train front end position it is derived from the bogie pin 1D position by adding the distance between the bogie pin and the train front end. Rationale: Thanks to the absolute positioning of the ASTP and the Map Data, the absolute position of the bogie is determined. From this absolute position the bogie pin 1D position can be derived. Note the absolute error between the bogie and the train front end, and the bogie and the train front end on the track centreline is negligible (less than 0,02cm for curve with a radius of 150m).

Train front end
type: Form

Train Integrity Monitoring
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Integrity Monitoring
sense: TRAIN--INTEGRITY--MONITORING lexSense

TRAIN--INTEGRITY--MONITORING lexConcept
type: LexicalConcept
definition: Onboard monitoring system that makes sure that during a train ride the train is still complete and has not accidentally split. Function of ETCS Level 3

Train Integrity Monitoring
type: Form

Train Joining
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Joining
sense: TRAIN--JOINING lexSense

TRAIN--JOINING lexConcept
type: LexicalConcept
definition: 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
type: Form

TLM
type: Acronym
type: LexicalEntry
acronym for: TRAIN--LENGTH--MASTER label
canonical form: TLM

TRAIN--LENGTH--MASTER lexConcept
type: LexicalConcept
definition: 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.

Train Length Master
type: Form

TLM
type: Form

TLMF
type: Acronym
type: LexicalEntry
acronym for: TRAIN--LENGTH--MERGING--FUNCTION label
canonical form: TLMF

TRAIN--LENGTH--MERGING--FUNCTION lexConcept
type: LexicalConcept
definition: The Train Length Merging Function (TLMF) receives information from TLM-A and TLM-B.{comment:23} The main task of the TLMF consists of comparing the information received. If the both paths are sending coherent information, then the TLMF shall forward the data to the ETCS-OB. At least following checks are required: * Train length A (TLM-A) is equal to Train length B (TLM-B){comment:22} * List of vehicle IDs on path A is equal to List of vehicle IDs on path B * (optional) HoT A and EoT A correspond to HoT B and EoT B Once the checks are passed for the first time, during the train inauguration, the TLMF shall send the train length to the ETCS-OB and then starting a continuous monitoring of the information consistency. The TLMF shall inform the ETCS-OB when the train length information is no more available (e.g., the information is not coming from one channel, there is a misalignment between the two channels, etc.) and shall stop the monitoring when a reset takes place (e.g., end of mission).

Train Length Merging Function
type: Form

TLMF
type: Form

Train Object
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Object
sense: TRAIN--OBJECT lexSense

TRAIN--OBJECT lexConcept
type: LexicalConcept
definition: Train Object is the object needed by the ETPS to manage the Communication with an ETCS Equipped train.{comment:84}{comment:85}

Train Object
type: Form

Train Path
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Path
sense: TRAIN--PATH lexSense

TRAIN--PATH lexConcept
type: LexicalConcept
definition: Train path means the infrastructure capacity needed to run a train between two places over a given period.

Train Path
type: Form

Train Position Report
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Position Report
sense: TRAIN--POSITION--REPORT lexSense

TRAIN--POSITION--REPORT lexConcept
type: LexicalConcept
definition: The term Train Position Report refers to either Position Report packet (packet number 0) or Position Report based on two balise groups packet (packet number 1) according to /ETCS/ - SUBSET-026, chapter 7.

Train Position Report
type: Form

Train preparation
type: LexicalEntry
type: MultiwordExpression
canonical form: Train preparation
sense: TRAIN--PREPARATION lexSense

TRAIN--PREPARATION lexConcept
type: LexicalConcept
definition: 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 lexConcept 2
type: LexicalConcept
definition: 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 preparation
type: Form

TRN
type: Acronym
type: LexicalEntry
acronym for: TRAIN--RUNNING--NUMBER label
canonical form: TRN

TRAIN--RUNNING--NUMBER lexConcept
type: LexicalConcept
definition: A number under which the train is operated.

TRAIN--RUNNING--NUMBER lexConcept 2
type: LexicalConcept
definition: A number under which the train is operated. Reference: Glossary of Terms and Abbreviation. SUBSET-023. Issue 4.0.0

Train Running Number
type: Form

TRN
type: Form

Train Sequence Change
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Sequence Change
sense: TRAIN--SEQUENCE--CHANGE lexSense

TRAIN--SEQUENCE--CHANGE lexConcept
type: LexicalConcept
definition: Change in the train sequence among the other trains on the network

Train Sequence Change
type: Form

Splitting
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TRAIN--SPLITTING label
canonical form: Splitting

TRAIN--SPLITTING lexConcept
type: LexicalConcept
definition: 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
type: Form

Splitting
type: Form

Train Standby
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Standby
sense: TRAIN--STANDBY lexSense

TRAIN--STANDBY lexConcept
type: LexicalConcept
definition: Change the status of a train to standby (on hold until the train run starts)

Train Standby
type: Form

TTLS
type: Acronym
type: LexicalEntry
acronym for: TRAIN--TIME--LOCATION--SERVICE label
canonical form: TTLS

TRAIN--TIME--LOCATION--SERVICE lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: Train Time Location Service

Train Time Location Service
type: Form

TTLS
type: Form

Train true acceleration
type: LexicalEntry
type: MultiwordExpression
canonical form: Train true acceleration
sense: TRAIN--TRUE--ACCELERATION lexSense

TRAIN--TRUE--ACCELERATION lexConcept
type: LexicalConcept
definition: The real signed acceleration of the train along the track centreline. It is expressed using the 1D reference frame defined by the bogie reference frame.

Train true acceleration
type: Form

Train true position
type: LexicalEntry
type: MultiwordExpression
canonical form: Train true position
sense: TRAIN--TRUE--POSITION lexSense

TRAIN--TRUE--POSITION lexConcept
type: LexicalConcept
definition: The real position of the train front-end along the track centreline. It is expressed using the 1D reference frame defined by the bogie reference frame or a geocoordinate reference frame .

Train true position
type: Form

Train true speed
type: LexicalEntry
type: MultiwordExpression
canonical form: Train true speed
sense: TRAIN--TRUE--SPEED lexSense

TRAIN--TRUE--SPEED lexConcept
type: LexicalConcept
definition: The real absolute speed of the train along the track centreline. It is expressed using the 1D reference frame defined by the bogie reference frame.

Train true speed
type: Form

Train-centric Track Occupancy
type: LexicalEntry
type: MultiwordExpression
canonical form: Train-centric Track Occupancy
sense: TRAIN-CENTRIC--TRACK--OCCUPANCY lexSense

TRAIN-CENTRIC--TRACK--OCCUPANCY lexConcept
type: LexicalConcept
definition: With train-centric approach the trackside focus is on representing a railway vehicle with an extent in a topology rather than on representing anonymous occupancy states of fixed sizes reported by TTD systems as in today's conventional block-centric signaling systems. In other words, the term "train-centric" refers to a "train-oriented" view of the trackside system about the track occupation caused by a railway vehicle, e.g., an ETCS-equipped train. This view is achieved by fusion of localisation information from both train and trackside. A train-centric track occupancy determination is based primarily on localisation information received from the railway vehicle, e.g., from trains sent via ETCS Train Position Reports. The trackside system will also take into account additional trackside localisation information if available such as Trackside Train Detection (TTD) inputs, for example to: * Adjust the trackside view of track occupancy by train, based on clear TTD sections at the front or rear of the train * Detect movement of non-communicating railway vehicles, e.g., trains/wagons not equipped with ETCS and trains equipped with ETCS that have lost communication * Handle degraded situations, such as loss of train integrity.

Train-centric Track Occupancy
type: Form

Train
type: LexicalEntry
type: Word
canonical form: Train
sense: TRAIN lexSense

TRAIN lexConcept
type: LexicalConcept
definition: Eurostat/ITF/UNECE definition: one or more railway vehicles hauled by one or more locomotives or rail-cars, or one rail-car traveling alone, running under a given number or specific designation from an initial fixed point to a terminal fixed point. (A light engine, i.e. a locomotive traveling on its own, is not considered to be a train.) UNISIG definition for ERTMS: a traction unit (vehicle from where a train is operated) with or without coupled railway vehicles or a train set of vehicles with train data available. General definition: one or more railway vehicles capable of being moved. It may consist of a locomotive (sometimes more than one) to provide power with various unpowered vehicles attached to it. It may consist of a multiple unit, i.e. several vehicles formed into a fixed formation or set, which carry their own power and do not require a locomotive. A train may be only a locomotive running light (deadheading) to a point elsewhere on the railway. A train may carry passengers, freight or, rarely nowadays, both.

TRAIN lexConcept 2
type: LexicalConcept
definition: The train is an operational entity that provides informations to MDS such as cab is active, train in motion or at standstill. The train is involved in the following tasks: activate/deactivate the cab and configure displays on the cab.

TRAIN lexConcept 3
type: LexicalConcept
definition: The train is an operational entity that provides informations to MDS such as cab is active, train in motion or at standstill. The train is involved in the following tasks: activate/deactivate the cab and configure displays on the cab.

Train
type: Form

TEN-T
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TRANS-EUROPEAN--TRANSPORT--NETWORK label
canonical form: TEN-T

TRANS-EUROPEAN--TRANSPORT--NETWORK lexConcept
type: LexicalConcept
definition: Trans-European Transport Network based on EU-Regulation No 1315/2013

Trans-European Transport Network
type: Form

TEN-T
type: Form

Transport Layer Security [TLS]
type: LexicalEntry
type: MultiwordExpression
canonical form: Transport Layer Security [TLS]
sense: TRANSPORT--LAYER--SECURITY-- TLS lexSense

TRANSPORT--LAYER--SECURITY-- TLS lexConcept
type: LexicalConcept
definition: TLS is normally implemented on top of TCP in order to encrypt Application Layer protocols such as HTTP, FTP, SMTP and IMAP, although it can also be implemented on UDP, DCCP and SCTP as well (e.g. for VPN and SIP-based application uses). This is known as Datagram Transport Layer Security (DTLS) and is specified in RFCs 6347, 5238 and 6083.

Transport Layer Security [TLS]
type: Form

TLS
type: Acronym
type: LexicalEntry
acronym for: TRANSPORT--LAYER--SECURITY label
canonical form: TLS

TRANSPORT--LAYER--SECURITY lexConcept
type: LexicalConcept
definition: Transport Layer Security

Transport Layer Security
type: Form

TLS
type: Form

TCCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TRANSVERSAL--CCS--DOMAIN label
canonical form: TCCS

TRANSVERSAL--CCS--DOMAIN lexConcept
type: LexicalConcept
definition: Transversal CCS domain

Transversal CCS domain
type: Form

TCCS
type: Form

TRD - Train Data
type: LexicalEntry
type: MultiwordExpression
canonical form: TRD - Train Data
sense: TRD-----TRAIN--DATA lexSense

TRD-----TRAIN--DATA lexConcept
type: LexicalConcept
definition: TRD - Train Data

TRD - Train Data
type: Form

Basic parameters
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: TSI--CCS--2023-----4-1-1---BASIC--PARAMETERS label
canonical form: Basic parameters

TSI--CCS--2023-----4-1-1---BASIC--PARAMETERS lexConcept
type: LexicalConcept
definition: In accordance with the relevant essential requirements, the Control-Command and Signalling Subsystems are characterised by the following basic parameters: (1) Control-Command and Signalling reliability, availability and safety characteristics relevant to interoperability (point 4.2.1); (2) On-Board ETCS functionality (point 4.2.2); (3) Trackside ETCS functionality (point 4.2.3); (4) Mobile communication functions for railways RMR (point 4.2.4); (5) RMR, ETCS and ATO air gap interfaces (point 4.2.5); (6) On-Board Interfaces Internal to Control-Command and Signalling (point 4.2.6); (7) Trackside Interfaces Internal to Control-Command and Signalling (point 4.2.7); (8) Key Management (point 4.2.8); (9) ETCS-ID Management (point 4.2.9); (10) Trackside Train Detection Systems (point 4.2.10); (11) Electromagnetic Compatibility between Rolling Stock and Control-Command and Signalling trackside equipment (point 4.2.11); (12) ETCS DMI (Driver-Machine Interface) (point 4.2.12); (13) RMR DMI (Driver-Machine Interface) (point 4.2.13); (14) Interface to Data Recording for Regulatory Purposes (point 4.2.14); (15) Trackside Control-Command and Signalling objects (point 4.2.15); (16) Construction of equipment used in CCS subsystems (point 4.2.16); (17) ETCS and Radio System Compatibility (point 4.2.17); (18) On-Board ATO functionality (point 4.2.18); (19) Trackside ATO functionality (point 4.2.19); (20) Technical documentation for Maintenance (point 4.2.20).

TSI CCS 2023 - 4.1.1. Basic parameters
type: Form

Basic parameters
type: Form

TSI
type: LexicalEntry
type: Word
canonical form: TSI
sense: TSI lexSense

TSI lexConcept
type: LexicalConcept
definition: ‘technical specification for interoperability’ (TSI) means a specification adopted in accordance with Directive (EU) 2016/797 by which each subsystem or part of a subsystem is covered in order to meet the essential requirements and ensure the interoperability of the Union rail system; SPPRAMSS-337 - [Directive (EU) 2016/798]

TSI
type: Form

TTD - Trackside Train Detection
type: LexicalEntry
type: MultiwordExpression
canonical form: TTD - Trackside Train Detection
sense: TTD-----TRACKSIDE--TRAIN--DETECTION lexSense

TTD-----TRACKSIDE--TRAIN--DETECTION lexConcept
type: LexicalConcept
definition: TTD - Trackside Train Detection

TTD - Trackside Train Detection
type: Form

Unconditional Emergency Stop UES
type: LexicalEntry
type: MultiwordExpression
canonical form: Unconditional Emergency Stop UES
sense: UNCONDITIONAL--EMERGENCY--STOP--UES lexSense

UNCONDITIONAL--EMERGENCY--STOP--UES lexConcept
type: LexicalConcept
definition: Unconditional Emergency Stop UES Unconditional Emergency Stop is the immediately executed stop triggered by message 16 and TR Mode applying emergency brake.

Unconditional Emergency Stop UES
type: Form

UML
type: Acronym
type: LexicalEntry
acronym for: UNIFIED--MODELING--LANGUAGE label
canonical form: UML

UNIFIED--MODELING--LANGUAGE lexConcept
type: LexicalConcept
definition: Unified Modeling Language

Unified Modeling Language
type: Form

UML
type: Form

UNIFE
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: UNION--DES--INDUSTRIES--FERROVIAIRES--EUROPEENNES label
canonical form: UNIFE

UNION--DES--INDUSTRIES--FERROVIAIRES--EUROPEENNES lexConcept
type: LexicalConcept
definition: Union des Industries Ferroviaires Européennes

Union des Industries Ferroviaires Européennes
type: Form

UNIFE
type: Form

UNISIG
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: UNION--INDUSTRY--OF--SIGNALLING label
canonical form: UNISIG

UNION--INDUSTRY--OF--SIGNALLING lexConcept
type: LexicalConcept
definition: Union Industry of Signalling

Union Industry of Signalling
type: Form

UNISIG
type: Form

UNITEL
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: UNION--INDUSTRY--OF--TELECOMMUNICATIONS label
canonical form: UNITEL

UNION--INDUSTRY--OF--TELECOMMUNICATIONS lexConcept
type: LexicalConcept
definition: Union Industry of Telecommunications

Union Industry of Telecommunications
type: Form

UNITEL
type: Form

UNISIG - Union Industry of Signalling
type: LexicalEntry
type: MultiwordExpression
canonical form: UNISIG - Union Industry of Signalling
sense: UNISIG-----UNION--INDUSTRY--OF--SIGNALLING lexSense

UNISIG-----UNION--INDUSTRY--OF--SIGNALLING lexConcept
type: LexicalConcept
definition: UNISIG - Union Industry of Signalling

UNISIG - Union Industry of Signalling
type: Form

Unplanned speed restriction
type: LexicalEntry
type: MultiwordExpression
canonical form: Unplanned speed restriction
sense: UNPLANNED--SPEED--RESTRICTION lexSense

UNPLANNED--SPEED--RESTRICTION lexConcept
type: LexicalConcept
definition: 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}

Unplanned speed restriction
type: Form

UTOE
type: Acronym
type: LexicalEntry
acronym for: UNRESOLVED--TRACKBOUND--OBJECT--EXTENT label
canonical form: UTOE

UNRESOLVED--TRACKBOUND--OBJECT--EXTENT lexConcept
type: LexicalConcept
definition: Unresolved Trackbound Object Extent is the extent of the track that may be occupied by a railway vehicle not associated to a Train Object, i.e. it cannot be directly associated to a Safe Train Extent.

Unresolved Trackbound Object Extent
type: Form

UTOE
type: Form

UTO
type: Acronym
type: LexicalEntry
acronym for: UNRESOLVED--TRACKBOUND--OBJECT label
canonical form: UTO

UNRESOLVED--TRACKBOUND--OBJECT lexConcept
type: LexicalConcept
definition: Unresolved Trackbound Object is the object needed by ETPS to manage occupancies of track areas where track vacancy is not proven and that cannot be associated to a Train Object{comment:83}

Unresolved Trackbound Object
type: Form

UTO
type: Form

Unsupervised movement
type: LexicalEntry
type: MultiwordExpression
canonical form: Unsupervised movement
sense: UNSUPERVISED--MOVEMENT lexSense

UNSUPERVISED--MOVEMENT lexConcept
type: LexicalConcept
definition: 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.

Unsupervised movement
type: Form

Updateability
type: LexicalEntry
type: Word
canonical form: UPDATEABILITY lexForm
sense: UPDATEABILITY lexSense