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
version info: v231204
entry: AB Allocation Body
entry: accident
entry: actor variant
entry: Adaptability
entry: ADCARP something
entry: ADM - Automatic Driving Module
entry: (AFARP) - As far as reasonably practicable
entry: ALM
entry: Analysis
entry: Answer.
entry: APM - Automatic Processing Module
entry: Appliation (along EN 50126)
entry: Application Condition.
entry: Application Configuration.
entry: Application Guideline
entry: Application Layer
entry: Application
entry: Architectural Concept
entry: ARCT
entry: Area Controller The Area Controller manages areas for the View.
entry: Area of Use
entry: ASFA
entry: ASO
entry: Assessment.
entry: ATO - Automatic Train Operation
entry: ATO Automatic Train Operation CCS Control Command and Signaling CI/CD Continuous...
entry: ATO
entry: Authentication
entry: Authorisation, Re-authorisation, Safety acceptance
entry: Automatic Conflict Solution
entry: availability, <of a product>
entry: AWC
entry: Backwards Compatibility
entry: Basic Integrity Platform Independence Interface (I4)
entry: Behavioural Component Exchange
entry: Behavioural exchange
entry: Behavioural Port
entry: Biometric Reader Device that reads the identity of a person by comparing some at...
entry: Black Box View
entry: Building Block Configuration Manifest
entry: Building Block Configuration
entry: BB
entry: Building block
entry: Building Strategy Concept
entry: Building Strategy
entry: Button A Hard Key allocated to a dedicated system on a cab. It's designed with a...
entry: Buzzer Electrical device that makes a buzzing noise and is used to provide an au...
entry: C-DAS - Connected Driver Advisory System
entry: Capability Meaning
entry: capacitor
entry: Capacity Plan and Decision Processing
entry: Capacity waste means:
entry: Capacity-friendly behaviour means:
entry: Capella viewpoint
entry: CAPEX
entry: CBA
entry: CBM
entry: CBO
entry: CCF
entry: CCM
entry: CCS - Command Control Signalling
entry: CCMS
entry: CCS Configuration Management System
entry: CCS Configuration Manifest
entry: CCS Configuration
entry: CCS Deployment
entry: CCS Evolution Path
entry: CCS Feature
entry: CCS System

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

AB--ALLOCATION--BODY lexConcept
type: LexicalConcept
definition: AB Allocation Body

AB Allocation Body
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; [SOURCE: SPPRAMSS-337 - [Directive (EU) 2016/798] Article 3 Definitions (11) ]

accident
type: Form

actor variant
type: LexicalEntry
type: MultiwordExpression
canonical form: actor variant
sense: ACTOR--VARIANT lexSense

ACTOR--VARIANT lexConcept
type: LexicalConcept
definition: An actor variant is an deviation to an existing actor regarding function deployment. It arises in two cases: * An additional (unusual) function is deployed to the actor variant. * A common actor function is removed and deployed to another actor or to a system. Identification of actor variants is a precondition for harmonisation of operational processes.

actor variant
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

ADCARP something
type: LexicalEntry
type: MultiwordExpression
canonical form: ADCARP something
sense: ADCARP--SOMETHING lexSense

ADCARP--SOMETHING lexConcept
type: LexicalConcept
definition: Add, Change, Delete, Approve, Release, Decide and Publish

ADCARP something
type: Form

ADM - Automatic Driving Module
type: LexicalEntry
type: MultiwordExpression
canonical form: ADM - Automatic Driving Module
sense: ADM-----AUTOMATIC--DRIVING--MODULE lexSense

ADM-----AUTOMATIC--DRIVING--MODULE lexConcept
type: LexicalConcept
definition: ADM - Automatic Driving Module

ADM - Automatic Driving Module
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

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

ALM lexConcept
type: LexicalConcept
definition: Application Lifecycle Management

ALM
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

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

APM - Automatic Processing Module
type: LexicalEntry
type: MultiwordExpression
canonical form: APM - Automatic Processing Module
sense: APM-----AUTOMATIC--PROCESSING--MODULE lexSense

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

APM - Automatic Processing Module
type: Form

Appliation (along EN 50126)
type: LexicalEntry
type: MultiwordExpression
canonical form: Appliation (along EN 50126)
sense: APPLIATION--ALONG--EN--50126 lexSense

APPLIATION--ALONG--EN--50126 lexConcept
type: LexicalConcept
definition: Describes the sum of: The system, its needed environment and its form of usage (other systems, processes), and the system life-cycle.

Appliation (along EN 50126)
type: Form

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

APPLICATION--CONDITION lexConcept
type: LexicalConcept
definition: Requirement about the environment and use of the target system, e.g. skills of maintenance people that ned to be trained or requirements about the physical environment. ("exported constraint, relevant for users").

APPLICATION--CONDITION lexConcept 2
type: LexicalConcept
definition: An Application Condition is a requirement for the environment of a system in its application. Concretely these can be for example requirements concerning the skills of the users, temperatures in a data center, or maintenance processes that need to be established.

Application Condition.
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

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

Application Layer
type: LexicalEntry
type: MultiwordExpression
canonical form: Application Layer
sense: APPLICATION--LAYER lexSense

APPLICATION--LAYER lexConcept
type: LexicalConcept
definition: contains functional applications.

Application Layer
type: Form

Application
type: LexicalEntry
type: Word
canonical form: Application
sense: APPLICATION lexSense

APPLICATION lexConcept
type: LexicalConcept
definition: An application in SP context is the resulting situation of a system beeing used in a specific environment by specific actors. In short - Application = System + Processes + Actors + Environment.

Application
type: Form

Architectural Concept
type: LexicalEntry
type: MultiwordExpression
canonical form: Architectural Concept
sense: ARCHITECTURAL--CONCEPT lexSense

ARCHITECTURAL--CONCEPT lexConcept
type: LexicalConcept
definition: The architectural process comprises four steps, each dealing with a separate concern. The general concept implements the architecture recommendations from the System Pillar report [SPREP, page 11] for a function-based architecture and a layered architecture approach. Both concepts can be realised with the architectural principles described herein.These steps are described in detail in the following chapters. * Operational analysis (OA): identify the operational process needs that are to be supported by the technical systems.{comment:4} This analysis should focus as purely as possible on the processes and ideally does not take any specific technical system architecture into account. The operational analysis is usually performed on an abstraction layer above the topmost system in the systems of systems hierarchy and performed only once. See Chapter 5.6 * System analysis (SA): identify the needs of the system of interest. This step does not design a specific technical solution but captures the needs for the future system. It hence represents a statement of work and not a finished piece of engineering. It is used to rationalize the decision, which operational processes will be performed by the system of interest, and which will be not (these processes then mostly will be either performed by other systems or by human actors and defined as operating rules). System analysis is performed recursively: * Once for the topmost system of systems, deriving the initial need from the operational analysis * Multiple times for each system of system decomposition step, deriving the system needs of the lower level of decomposition from the higher level of decomposition * Logical architecture (LA): design a solution to the system needs based on solution concepts and architectural concepts. Split the system functions based on solution concepts (e.g. absolute positioning vs reference point based localisation, moving blocks, fixed blocks or hybrid) so that it becomes clear, how and by whic…

Architectural Concept
type: Form

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

ARCT lexConcept
type: LexicalConcept
definition: Architecture and Release Coordination Team

ARCT
type: Form

Area Controller The Area Controller manages areas for the View.
type: LexicalEntry
type: MultiwordExpression
canonical form: Area Controller The Area Controller manages areas for the View.
sense: AREA--CONTROLLER--THE--AREA--CONTROLLER--MANAGES--AREAS--FOR--THE--VIEW lexSense

AREA--CONTROLLER--THE--AREA--CONTROLLER--MANAGES--AREAS--FOR--THE--VIEW lexConcept
type: LexicalConcept
definition: Area Controller The Area Controller manages areas for the View.

Area Controller The Area Controller manages areas for the View.
type: Form

Area of Use
type: LexicalEntry
type: MultiwordExpression
canonical form: Area of Use
sense: AREA--OF--USE lexSense

AREA--OF--USE lexConcept
type: LexicalConcept
definition: ...

Area of Use
type: Form

ASFA
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ASFA
canonical form: ASFA

ASFA 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.

ASFA
type: Form

ASFA
type: Form

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

ASO lexConcept
type: LexicalConcept
definition: Automatic Shunting Operation

ASO
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

ATO - Automatic Train Operation
type: LexicalEntry
type: MultiwordExpression
canonical form: ATO - Automatic Train Operation
sense: ATO-----AUTOMATIC--TRAIN--OPERATION lexSense

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

ATO - Automatic Train Operation
type: Form

ATO Automatic Train Operation CCS Control Command and Signaling CI/CD Continuous...
type: LexicalEntry
type: MultiwordExpression
canonical form: ATO Automatic Train Operation CCS Control Command and Signaling CI/CD Continuous...
sense: ATO--AUTOMATIC--TRAIN--OPERATION--CCS--CONTROL--COMMAND--AND--SIGNALING--CI CD--CONTINUOUS lexSense

ATO--AUTOMATIC--TRAIN--OPERATION--CCS--CONTROL--COMMAND--AND--SIGNALING--CI CD--CONTINUOUS lexConcept
type: LexicalConcept
definition: ATO | Automatic Train Operation | 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 | PE | Plan Execution PIS | Passenger Information System POS | Path Order System PROD | Production | QA | Quality and Assurance | 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 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 TMS | Traffic Management 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 CCS Control Command and Signaling CI/CD Continuous...
type: Form

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

ATO lexConcept
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

ATO
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. (source: SPPRAMSS-1705 - [UNISIG Subset-146] )

Authentication
type: Form

Authorisation, Re-authorisation, Safety acceptance
type: LexicalEntry
type: MultiwordExpression
canonical form: Authorisation, Re-authorisation, Safety acceptance
sense: AUTHORISATION--RE-AUTHORISATION--SAFETY--ACCEPTANCE lexSense

AUTHORISATION--RE-AUTHORISATION--SAFETY--ACCEPTANCE lexConcept
type: LexicalConcept
definition: The provision by an independent body of written assurance (a certificate) that the product, service or system in question complies with specific requirements e.g., is compliant to TSI-CCS

Authorisation, Re-authorisation, Safety acceptance
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

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

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

AWC lexConcept
type: LexicalConcept
definition: Architecture Working Circle

AWC
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

Basic Integrity Platform Independence Interface (I4)
type: LexicalEntry
type: MultiwordExpression
canonical form: Basic Integrity Platform Independence Interface (I4)
sense: BASIC--INTEGRITY--PLATFORM--INDEPENDENCE--INTERFACE--I4 lexSense

BASIC--INTEGRITY--PLATFORM--INDEPENDENCE--INTERFACE--I4 lexConcept
type: LexicalConcept
definition: Interface I4 provides a platform independence API for functional applications in the non-safety area.

Basic Integrity Platform Independence Interface (I4)
type: Form

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

BEHAVIOURAL--COMPONENT--EXCHANGE lexConcept
type: LexicalConcept
definition: exchange between behavioural components

Behavioural Component Exchange
type: Form

Behavioural exchange
type: LexicalEntry
type: MultiwordExpression
canonical form: Behavioural exchange
sense: BEHAVIOURAL--EXCHANGE lexSense

BEHAVIOURAL--EXCHANGE lexConcept
type: LexicalConcept
definition: implemented as component exchange: interaction between two behavioural physical components or logical components, through their behavioural ports

Behavioural exchange
type: Form

Behavioural Port
type: LexicalEntry
type: MultiwordExpression
canonical form: Behavioural Port
sense: BEHAVIOURAL--PORT lexSense

BEHAVIOURAL--PORT lexConcept
type: LexicalConcept
definition: Connection point of one or more behavioural exchanges allocated to a logical or physical component, by specifying what the component can provide (output port) and what it must perform (input port) (original definition may be not that accurate).

Behavioural Port
type: Form

Biometric Reader Device that reads the identity of a person by comparing some at...
type: LexicalEntry
type: MultiwordExpression
canonical form: Biometric Reader Device that reads the identity of a person by comparing some at...
sense: BIOMETRIC--READER--DEVICE--THAT--READS--THE--IDENTITY--OF--A--PERSON--BY--COMPARING--SOME--AT lexSense

BIOMETRIC--READER--DEVICE--THAT--READS--THE--IDENTITY--OF--A--PERSON--BY--COMPARING--SOME--AT lexConcept
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 Device that reads the identity of a person by comparing some at...
type: Form

Black Box View
type: LexicalEntry
type: MultiwordExpression
canonical form: Black Box View
sense: BLACK--BOX--VIEW lexSense

BLACK--BOX--VIEW lexConcept
type: LexicalConcept
definition: The black box view hides structural decomposition of a system. In black box view, it cannot be differentiated between systems that are further refined into a system of systems or into subsystems.

Black Box View
type: Form

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

BUILDING--BLOCK--CONFIGURATION--MANIFEST lexConcept
type: LexicalConcept
definition: The Building Block (BB) Configuration Manifest is a file used to describe the configuration items of a BB Configuration. The BB Configuration Manifest file lists all configuration items of a specific building block, it is a generic definition (before integration in its environment) of the building block of a specific supplier. Note: the actual BB Configuration Items are not part of the BB Configuration Manifest, they are only referenced in the BB Configuration Manifest file.

Building Block Configuration Manifest
type: Form

Building Block Configuration
type: LexicalEntry
type: MultiwordExpression
canonical form: Building Block Configuration
sense: BUILDING--BLOCK--CONFIGURATION lexSense

BUILDING--BLOCK--CONFIGURATION lexConcept
type: LexicalConcept
definition: The Building Block Configuration is an exhaustive, unambiguous set (configuration items and BB manifest file) of all Configuration Items required to operate one instance of a Building Block. It includes default values for all parameters. As a consequence the Building Block Configuration can only be related to the "Generic Application" or "Generic Product" from CENELEC.

Building Block Configuration
type: Form

BB
type: Acronym
type: LexicalEntry
acronym for: Building block
canonical form: BB

BUILDING--BLOCK lexConcept
type: LexicalConcept
definition: {comment:33} A building block is a sourceable unit of the CCS system (hardware and/or software), having standardised functionality, standardised performance (RAM), standardised safety (including Tolerable Functional Failure Rate [TFFR], Safety Integrity Level [SIL] and Safety Related Application Conditions [SRAC]), standardised security and standardised interfaces towards other building blocks and/or external systems. A building block can also be defined as a standardised module. {comment:158}

BUILDING--BLOCK lexConcept 2
type: LexicalConcept
definition: A Building Block is a sourceable unit of the CCS System (hardware and/or software), having standardised functionality, standardised PRAMS requirements (including Tolerable Functional Failure Rate [TFFR], Safety Integrity Level [SIL] 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]), standardised interfaces (on all OSI Layers) towards other Building Blocks and/or external systems. Building Blocks are exchangeable and migrateable, without impacting other Building Blocks. Building Blocks are separately sourceable from different suppliers and capable of being integrated by a third party.

Building block
type: Form

BB
type: Form

Building Strategy Concept
type: LexicalEntry
type: MultiwordExpression
canonical form: Building Strategy Concept
sense: BUILDING--STRATEGY--CONCEPT lexSense

BUILDING--STRATEGY--CONCEPT lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

Building Strategy Concept
type: Form

Building Strategy
type: LexicalEntry
type: MultiwordExpression
canonical form: Building Strategy
sense: BUILDING--STRATEGY lexSense

BUILDING--STRATEGY lexConcept
type: LexicalConcept
definition: processus allowing to regroup physical components into consistent sub-collection in terms of industral development concerns and a strategy point of view

Building Strategy
type: Form

Button A Hard Key allocated to a dedicated system on a cab. It's designed with a...
type: LexicalEntry
type: MultiwordExpression
canonical form: Button A Hard Key allocated to a dedicated system on a cab. It's designed with a...
sense: BUTTON--A--HARD--KEY--ALLOCATED--TO--A--DEDICATED--SYSTEM--ON--A--CAB---IT S--DESIGNED--WITH--A lexSense

BUTTON--A--HARD--KEY--ALLOCATED--TO--A--DEDICATED--SYSTEM--ON--A--CAB---IT S--DESIGNED--WITH--A lexConcept
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 A Hard Key allocated to a dedicated system on a cab. It's designed with a...
type: Form

Buzzer Electrical device that makes a buzzing noise and is used to provide an au...
type: LexicalEntry
type: MultiwordExpression
canonical form: Buzzer Electrical device that makes a buzzing noise and is used to provide an au...
sense: BUZZER--ELECTRICAL--DEVICE--THAT--MAKES--A--BUZZING--NOISE--AND--IS--USED--TO--PROVIDE--AN--AU lexSense

BUZZER--ELECTRICAL--DEVICE--THAT--MAKES--A--BUZZING--NOISE--AND--IS--USED--TO--PROVIDE--AN--AU lexConcept
type: LexicalConcept
definition: Buzzer Electrical device that makes a buzzing noise and is used to provide an audible warning.

Buzzer Electrical device that makes a buzzing noise and is used to provide an au...
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

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

capacitor
type: LexicalEntry
type: Word
canonical form: capacitor
sense: CAPACITOR lexSense

CAPACITOR lexConcept
type: LexicalConcept
definition: implicit-from-entry-label: capacitor

capacitor
type: Form

Capacity Plan and Decision Processing
type: LexicalEntry
type: MultiwordExpression
canonical form: Capacity Plan and Decision Processing
sense: CAPACITY--PLAN--AND--DECISION--PROCESSING lexSense

CAPACITY--PLAN--AND--DECISION--PROCESSING lexConcept
type: LexicalConcept
definition: Processing the capacity plan along with the current decisions to generate an updated operational plan. Capacity plan is mapped to daily topology. Sectional runtime is re-calculated for the new operational plan. Every single second a new operational plan will be processed.

Capacity Plan and Decision Processing
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

Capella viewpoint
type: LexicalEntry
type: MultiwordExpression
canonical form: Capella viewpoint
sense: CAPELLA--VIEWPOINT lexSense

CAPELLA--VIEWPOINT lexConcept
type: LexicalConcept
definition: A viewpoint is the tailoring of a capella diagram: * It has a specific purpose * It follows some diagram rules, that enforce this purpose * It is exported from Capella to Polarion in graphical form with a pre-defined filter

Capella viewpoint
type: Form

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

CAPEX lexConcept
type: LexicalConcept
definition: Capital Expenditures or Capital Expenses

CAPEX
type: Form

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

CBA lexConcept
type: LexicalConcept
definition: Cost Benefit Analysis

CBA
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

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

CBO lexConcept
type: LexicalConcept
definition: Common Business Objective

CBO
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

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

CCM lexConcept
type: LexicalConcept
definition: Change Control Management

CCM
type: Form

CCS - Command Control Signalling
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS - Command Control Signalling
sense: CCS-----COMMAND--CONTROL--SIGNALLING lexSense

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

CCS - Command Control Signalling
type: Form

CCMS
type: Acronym
type: LexicalEntry
acronym for: CCS Configuration Management System
canonical form: CCMS

CCS--CONFIGURATION--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: The CCS Configuration Management System is a central location technical system that is responsible for managing the CCS configurations of a defined set of CCS deployments. Each CCS deployment is managed by exactly one CCS Configuration Management System.

CCS Configuration Management System
type: Form

CCMS
type: Form

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

CCS--CONFIGURATION--MANIFEST lexConcept
type: LexicalConcept
definition: The CCS Configuration Manifest is a file used to describe (metadata) the configuration items of a CCS Configuration. The CCS Configuration Manifest file lists all building blocks of a specific CCS instance deployment, it is an overarching definition of the specific CCS instance deployment. By means of the CCS Configuration Manifest the integrity of a specific CCS instance deployment can be ensured. Note: the actual CCS Configuration Items are not part of the CCS Configuration Manifest, they are only referenced in the CCS Configuration Manifest file.

CCS Configuration Manifest
type: Form

CCS Configuration
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS Configuration
sense: CCS--CONFIGURATION lexSense

CCS--CONFIGURATION lexConcept
type: LexicalConcept
definition: The CCS Configuration is an exhaustive, unambiguous description (all configuration items and an overarching CCS manifest file) of all building blocks necessary to operate a physical instance of a CCS System, approved (in line with the CENELEC process) for deployment to a specific CCS Instance (identified via an identifier, for instance the already existing NID_ENGINE, or other identifier already in use) and authorised to either operate on specific Railway Networks (identified via unique Railway Network Identifiers) or to be part of a specific Railway Network. The CCS Configuration is used for distribution of statical or semi-statical data (update data packet). It does not cover dynamic operational data like Moving Authority (for ETCS) or Journey Profiles (for ATO). The CCS Configuration is intended for CCS building blocks being present in multiple units, either close to infrastructure elements (e.g. CCS trackside instance and related signalling components like object controller) or CCS components on-board a train. It is not the aim to use CCS configuration management process (and the related CCS Configuration) for the update orchestration of large cloud based virtual machine environments (installed in data centres). For the latter there are more suitable solutions from the IT industry. It is not a prerequisite that CCS building blocks need to stay in operation when activating / installing a CCS Configuration (however, this is allowed). These components could shut down / restart, basically go out of operation, or remain in operation. The main sources for the CCS Configuration (configuration items and overarching CCS manifest file) content are the Building Block Suppliers and the Integrator (as described in the TCCS Configuration - High Level Concept document), accordingly the CCS Configuration content (and the related Configuration Management process) is restricted to what these roles are capable to provide. The Operator will only enrich the CCS Configuration with de…

CCS Configuration
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 also recognised with a unique identifier. A CCS Deployment consists of the CCS hardware running a specific CCS Configuration.

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
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 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.

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 Data Model
type: LexicalEntry
type: MultiwordExpression
canonical form: CCS/TMS Data Model
sense: CCS TMS--DATA--MODEL lexSense

CCS TMS--DATA--MODEL lexConcept
type: LexicalConcept
definition: The CCS/TMS Data Model{comment:91} defines the harmonised language to generate and transport the Domain Data at System Pillar interfaces. The Transversal CCS Subdomain 1 (SD1) 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 demonstrators.

CCS/TMS Data Model
type: Form

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

CCS lexConcept
type: LexicalConcept
definition: Control-Command and Signalling

CCS
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

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

CENELEC lexConcept
type: LexicalConcept
definition: European Committee for Electrotechnical Standardization

CENELEC
type: Form

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

CEN lexConcept
type: LexicalConcept
definition: European Committee for Standardization

CEN
type: Form

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

CER lexConcept
type: LexicalConcept
definition: Community of European Railway and Infrastructure Companies

CER
type: Form

Change Request.
type: LexicalEntry
type: MultiwordExpression
canonical form: Change Request.
sense: CHANGE--REQUEST lexSense

CHANGE--REQUEST lexConcept
type: LexicalConcept
definition: PROPOSAL what to change where. Shall normally be linked to an Isse. See SPPR-2210 - Manage change request links

Change Request.
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

CI Common Interface
type: LexicalEntry
type: MultiwordExpression
canonical form: CI Common Interface
sense: CI--COMMON--INTERFACE lexSense

CI--COMMON--INTERFACE lexConcept
type: LexicalConcept
definition: CI Common Interface

CI Common Interface
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

Clean code has an important implication of the project’s success as clean code i...
type: LexicalEntry
type: MultiwordExpression
canonical form: Clean code has an important implication of the project’s success as clean code i...
sense: CLEAN--CODE--HAS--AN--IMPORTANT--IMPLICATION--OF--THE--PROJECT S--SUCCESS--AS--CLEAN--CODE--I lexSense

CLEAN--CODE--HAS--AN--IMPORTANT--IMPLICATION--OF--THE--PROJECT S--SUCCESS--AS--CLEAN--CODE--I lexConcept
type: LexicalConcept
definition: Clean code has an important implication of the project’s success as clean code is more efficient and reduces potential bugs. The following code guidelines should be followed: * Readability: Readable code is easy to follow and optimizes space and time * Conventions: Follow conventions will structure the code in a better way and reduces unnecessary lines of code - less code is less complexity. * Indentation: Proper indentation is very important to increase the readability. * Design Principles: Resolves common problems in a very structured way. * Documentation: The code should be properly commented for understanding easily. Especially for microservices, the following guidelines should be followed: * Software components should be built as independent stateless services. * All business logic in a service should be encapsulated with the data upon which it acts. * There should be no direct access to a database from outside a service. Any and all access to a database should be accomplished by invoking a service specifically implemented to do so. * Each service should publish an interface that enables access to its data and functionality by other services. Furthermore, the system follows the 12-factor-app methodology: * Codebase: One codebase tracked in revision control; many deploys. * Dependencies: Explicitly declare and isolate dependencies. * Config: Store config in the environment. * Backing services: Treat backing services as attached resources. * Build, release, run: Strictly separate build and run stages. * Processes: Execute the app as one or more stateless processes. * Port binding: Export services via port binding. * Concurrency: Scale out via the process model. * Disposability: Maximize robustness with fast startup and graceful shutdown. * Dev/prod parity: Keep development, staging, and production as similar as possible. * Logs: Treat logs as event streams. * Admin processes: Run admin/management tasks as one-off processes.

Clean code has an important implication of the project’s success as clean code i...
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

CMS Capacity Management System
type: LexicalEntry
type: MultiwordExpression
canonical form: CMS Capacity Management System
sense: CMS--CAPACITY--MANAGEMENT--SYSTEM lexSense

CMS--CAPACITY--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: CMS Capacity Management System

CMS Capacity Management System
type: Form

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

CMS lexConcept
type: LexicalConcept
definition: CMS Central modelling services

CMS
type: Form

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

CM lexConcept
type: LexicalConcept
definition: Capacity Management. 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.

CM
type: Form

Common Business Objective.
type: LexicalEntry
type: MultiwordExpression
canonical form: Common Business Objective.
sense: COMMON--BUSINESS--OBJECTIVE lexSense

COMMON--BUSINESS--OBJECTIVE lexConcept
type: LexicalConcept
definition: Generic target of the System Pillar.

Common Business Objective.
type: Form

Common standard properties of workitems
type: LexicalEntry
type: MultiwordExpression
canonical form: Common standard properties of workitems
sense: COMMON--STANDARD--PROPERTIES--OF--WORKITEMS lexSense

COMMON--STANDARD--PROPERTIES--OF--WORKITEMS lexConcept
type: LexicalConcept
definition: * Title: The name of the work item * Description/design: The description of the work item = the design. The description is work item type specific (e.g., a class description for an exchange object). * Type: One of the types in the next chapter, like “operational problem analysis”, “operational requirement”, “System Function” or “logical component” * State: Work items and link types have a sequence of states, they runs through while a trace is worked out. The minimal set of states is * Suspect: Because of trace changes potentially not any more valid (to be checked) * Configuration: (Multiple choice list) Every work item is part of one or more “configurations”. Configurations can be releases, or certain versions of an architecture (for scalability or migration) * Assignment: Every work item shall be assigned to a person or team. It is the role of a functional team to assign unassigned work items when the author is not sure where to assign. The “unassigned” work items are forming the work que for a functional team. * Priority * Due date/finished on * System Level: Every work item has one of the following System levels: “1/2”, “3”, “4”, “5”. The levels are needed to make the right team assignment choices. Example for some requirements: * Requirement “The ATO GoA 4 operational capability shall allow to move trains without driver” – this requirement has System Level 1/2 because CCS, TMS and DAC are involved. Therefore, the modelling service needs to break it down it. * “The ATP operational capability shall allow safe train ahead distances that are shorter than the breaking distance of the following train” – this requirement has System Level 3 because several elements of CCS are involved. * “The maintenance process of an object controller shall be possible via remote operations as far as economically viable” – this requirement has system level 4, the Trackside Asset CS domain will resolve it. * Rationale: The reason for the design (description) * Comments: All historical w…

Common standard properties of workitems
type: Form

Commonality
type: LexicalEntry
type: Word
canonical form: Commonality
sense: COMMONALITY lexSense

COMMONALITY lexConcept
type: LexicalConcept
definition: Commonality is the set of reusable features (interface, functionality, performance, environment insertion, etc.) that a module or a building block is made of. {comment:178}

Commonality
type: Form

Communication Mean
type: LexicalEntry
type: MultiwordExpression
canonical form: Communication Mean
sense: COMMUNICATION--MEAN lexSense

COMMUNICATION--MEAN lexConcept
type: LexicalConcept
definition: a medium that support interaction between operational entities/actors

Communication Mean
type: Form

Complex Requirement
type: LexicalEntry
type: MultiwordExpression
canonical form: Complex Requirement
sense: COMPLEX--REQUIREMENT lexSense

COMPLEX--REQUIREMENT lexConcept
type: LexicalConcept
definition: A complex requirement is a requirement in which a combination of the main five patterns occurs. The complexity increases with the number of concurrent combinations.

Complex Requirement
type: Form

Component
type: LexicalEntry
type: Word
canonical form: Component
sense: COMPONENT lexSense

COMPONENT lexConcept
type: LexicalConcept
definition: {comment:35} A component is used to structure functionality within building blocks. It implements and encapsulates one or more behaviors (business logic) and exposes services via defined interfaces to other components.{comment:159}

Component
type: Form

Computing Environment
type: LexicalEntry
type: MultiwordExpression
canonical form: Computing Environment
sense: COMPUTING--ENVIRONMENT lexSense

COMPUTING--ENVIRONMENT lexConcept
type: LexicalConcept
definition: Refers to an environment, that allows building and running Functional Applications. It comprises of hardware and software (i.e., the Runtime Environment and the necessary tools for development, testing, integration, etc.)

Computing Environment
type: Form

Computing Platform
type: LexicalEntry
type: MultiwordExpression
canonical form: Computing Platform
sense: COMPUTING--PLATFORM lexSense

COMPUTING--PLATFORM lexConcept
type: LexicalConcept
definition: synonym for the Computing Environment

Computing Platform
type: Form

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

COM lexConcept
type: LexicalConcept
definition: European Commission

COM
type: Form

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

CONCEPT--ASPECT lexConcept
type: LexicalConcept
definition: For sketching concepts.

Concept Aspect.
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

Concept
type: LexicalEntry
type: Word
canonical form: Concept
sense: CONCEPT lexSense

CONCEPT lexConcept
type: LexicalConcept
definition: A concept is a definition of a term together with its relationship to other terms. So e.g. the term “train unit” together with the directed relationship “runs on” towards another term “track” forms the concept: “Train unit runs on track”.

Concept
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

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

CONEMP lexConcept
type: LexicalConcept
definition: Concept of Employment

CONEMP
type: Form

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

CONFIDENTIALITY lexConcept
type: LexicalConcept
definition: Confidentiality, in the context of computer systems, allows only authorised users to access protected data using specific mechanisms to ensure confidentiality and safeguard data from harmful intrusion. (source: SPPRAMSS-1705 - [UNISIG Subset-146] )

Confidentiality
type: Form

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

CONFIGURATION--DATA lexConcept
type: LexicalConcept
definition: The Configuration Data refers to use case-specific data for the Consuming Systems for a specific application. These can be broadly classified as Trackside Configuration Data and Train Configuration Data. Configuration Data. Being application-specific, they can be further detailed as Map Data (incl. On-Board Map Data), Segment Profiles, and Parameter Data. As a part of the configuration process, the Consuming Systems need to get the required Configuration Data from TCCS Services. The Configuration Data is static and does not change during the validity period of a Configuration Data version. Potential updates of Configuration Data will be realised by a centralised provisioning process, including activation of the new Configuration Data version.

Configuration Data
type: Form

Configuration Item
type: LexicalEntry
type: MultiwordExpression
canonical form: Configuration Item
sense: CONFIGURATION--ITEM lexSense

CONFIGURATION--ITEM lexConcept
type: LexicalConcept
definition: part of the system that must be enginereed, produced or bought, duplicated as much as it is used in the system and assembled with others in order to build a copy of the system

Configuration Item
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 CCS 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 CCS System. 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 CCS Deployment being operational (it includes also on a train).

Configuration Management
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: Description of a collection of model elements, either available or unavailable in a given context. A context can be a mode, a state or a combination of both.

Configuration
type: Form

Configure/administer content platform, define/moderate/train ACDARP process/prin...
type: LexicalEntry
type: MultiwordExpression
canonical form: Configure/administer content platform, define/moderate/train ACDARP process/prin...
sense: CONFIGURE ADMINISTER--CONTENT--PLATFORM--DEFINE MODERATE TRAIN--ACDARP--PROCESS PRIN lexSense

CONFIGURE ADMINISTER--CONTENT--PLATFORM--DEFINE MODERATE TRAIN--ACDARP--PROCESS PRIN lexConcept
type: LexicalConcept
definition: Configure/administer content platform, define/moderate/train ACDARP process/principles/guideline, define quality criteria/dod, surveil quality/dod, define top-level content targets, moderate content break-down process, check target fulfilment

Configure/administer content platform, define/moderate/train ACDARP process/prin...
type: Form

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

CONOPS lexConcept
type: LexicalConcept
definition: Concept of Operations

CONOPS
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

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: Limitation of applicabilty of a design workitem

Constraint.
type: Form

Content Exchange Concept
type: LexicalEntry
type: MultiwordExpression
canonical form: Content Exchange Concept
sense: CONTENT--EXCHANGE--CONCEPT lexSense

CONTENT--EXCHANGE--CONCEPT lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

Content Exchange Concept
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

context
type: LexicalEntry
type: Word
canonical form: context
sense: CONTEXT lexSense

CONTEXT lexConcept
type: LexicalConcept
definition: The ARCADIA method applies to the design of complex and critical systems, and more generally architectures that are subject to multiple functional and non-functional constraints, including software, electronic, electrical architectures, and industrial processes. It defines a set of practices that guides needs analysis and design to meet an operational requirement. At the same time it is adaptable to the processes and constraints linked to various types of life cycles such as bottom-up approach, application reuse, incremental, iterative and partial development.

context
type: Form

CCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Control, Command and Signalling
canonical form: CCS

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

Control, Command and Signalling
type: Form

CCS
type: Form

Controller Unit The Controller Unit is a hardware component which embeds logical...
type: LexicalEntry
type: MultiwordExpression
canonical form: Controller Unit The Controller Unit is a hardware component which embeds logical...
sense: CONTROLLER--UNIT--THE--CONTROLLER--UNIT--IS--A--HARDWARE--COMPONENT--WHICH--EMBEDS--LOGICAL lexSense

CONTROLLER--UNIT--THE--CONTROLLER--UNIT--IS--A--HARDWARE--COMPONENT--WHICH--EMBEDS--LOGICAL lexConcept
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 The Controller Unit is a hardware component which embeds logical...
type: Form

“Control” something
type: LexicalEntry
type: MultiwordExpression
canonical form: “Control” something
sense: CONTROL --SOMETHING lexSense

CONTROL --SOMETHING lexConcept
type: LexicalConcept
definition: Define/derive deliverables and targets, break down and assign work, define process/leads, supervise timing, check results, organize approval and decision process

“Control” something
type: Form

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

CONUSE lexConcept
type: LexicalConcept
definition: Concept how to use the system

CONUSE
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

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

CR lexConcept
type: LexicalConcept
definition: Change Request

CR
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

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

CSM-RA 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]

CSM-RA
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-OB - Cabin Voice Radio On-Board
type: LexicalEntry
type: MultiwordExpression
canonical form: CVR-OB - Cabin Voice Radio On-Board
sense: CVR-OB-----CABIN--VOICE--RADIO--ON-BOARD lexSense

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

CVR-OB - Cabin Voice Radio On-Board
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
type: LexicalEntry
type: Word
canonical form: DAC
sense: DAC lexSense

DAC lexConcept
type: LexicalConcept
definition: Digital Automated Coupling

DAC
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

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

DATA--AND--DATA--CLASS lexConcept
type: LexicalConcept
definition: element of an exchange item. their content is described by a data class that can be shared by other data. A data class is a structure that defines the data and their elementary properties/attributes

Data and Data Class
type: Form

Data Center
type: LexicalEntry
type: MultiwordExpression
canonical form: Data Center
sense: DATA--CENTER lexSense

DATA--CENTER lexConcept
type: LexicalConcept
definition: A facility to house Functional Applications and data in one geographical location. It is typically implemented as network of centrally aggregated computing and storage resources that enable the delivery of shared applications and data.

Data Center
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

DCM Digital Capacity Management
type: LexicalEntry
type: MultiwordExpression
canonical form: DCM Digital Capacity Management
sense: DCM--DIGITAL--CAPACITY--MANAGEMENT lexSense

DCM--DIGITAL--CAPACITY--MANAGEMENT lexConcept
type: LexicalConcept
definition: DCM Digital Capacity Management

DCM Digital Capacity Management
type: Form

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

DECISION lexConcept
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.
type: LexicalEntry
type: Word
canonical form: Definition.
sense: DEFINITION lexSense

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

DEFINITION lexConcept 2
type: LexicalConcept
definition: ARCADIA (Architecture Analysis & Design Integrated Approach) is a system and software architecture engineering method based on architecture-centric and model-driven engineering activities. Main resources about ARCADIA can be found on the official websites: https://www.eclipse.org/capella/arcadia-reference.html (image: 1-screenshot-20230107-163323.png)

Definition.
type: Form

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

DELIVERABLE lexConcept
type: LexicalConcept
definition: Any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project. (Source: ISO 24765:2017 3.1098) (e.g. Requirement Specification)

Deliverable
type: Form

Dependencies among applications
type: LexicalEntry
type: MultiwordExpression
canonical form: Dependencies among applications
sense: DEPENDENCIES--AMONG--APPLICATIONS lexSense

DEPENDENCIES--AMONG--APPLICATIONS lexConcept
type: LexicalConcept
definition: Application dependencies occur when applications rely on one another to provide their function(s).

Dependencies among applications
type: Form

Deploy applications on computing platforms
type: LexicalEntry
type: MultiwordExpression
canonical form: Deploy applications on computing platforms
sense: DEPLOY--APPLICATIONS--ON--COMPUTING--PLATFORMS lexSense

DEPLOY--APPLICATIONS--ON--COMPUTING--PLATFORMS lexConcept
type: LexicalConcept
definition: Installation of a copy of an application on a single computing platform instance.

Deploy applications on computing platforms
type: Form

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

DEPLOYMENT lexConcept
type: LexicalConcept
definition: rollout

Deployment
type: Form

“Design” something
type: LexicalEntry
type: MultiwordExpression
canonical form: “Design” something
sense: DESIGN --SOMETHING lexSense

DESIGN --SOMETHING lexConcept
type: LexicalConcept
definition: Create content along the rules given by all "control" and "manage" roles, moderate review and approval process

“Design” something
type: Form

Desk Area Desk Area is a location attribute (left, center...) associated to HMI...
type: LexicalEntry
type: MultiwordExpression
canonical form: Desk Area Desk Area is a location attribute (left, center...) associated to HMI...
sense: DESK--AREA--DESK--AREA--IS--A--LOCATION--ATTRIBUTE--LEFT--CENTER---ASSOCIATED--TO--HMI lexSense

DESK--AREA--DESK--AREA--IS--A--LOCATION--ATTRIBUTE--LEFT--CENTER---ASSOCIATED--TO--HMI lexConcept
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 Desk Area is a location attribute (left, center...) associated to HMI...
type: Form

Desk Display Area A Zone displaying a piece of visual information of particular...
type: LexicalEntry
type: MultiwordExpression
canonical form: Desk Display Area A Zone displaying a piece of visual information of particular...
sense: DESK--DISPLAY--AREA--A--ZONE--DISPLAYING--A--PIECE--OF--VISUAL--INFORMATION--OF--PARTICULAR lexSense

DESK--DISPLAY--AREA--A--ZONE--DISPLAYING--A--PIECE--OF--VISUAL--INFORMATION--OF--PARTICULAR lexConcept
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 A Zone displaying a piece of visual information of particular...
type: Form

Desk Inside a cab, the set of operating controls*, which is dedicated to preferr...
type: LexicalEntry
type: MultiwordExpression
canonical form: Desk Inside a cab, the set of operating controls*, which is dedicated to preferr...
sense: DESK--INSIDE--A--CAB--THE--SET--OF--OPERATING--CONTROLS*--WHICH--IS--DEDICATED--TO--PREFERR lexSense

DESK--INSIDE--A--CAB--THE--SET--OF--OPERATING--CONTROLS*--WHICH--IS--DEDICATED--TO--PREFERR lexConcept
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 Inside a cab, the set of operating controls*, which is dedicated to preferr...
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

Development Task
type: LexicalEntry
type: MultiwordExpression
canonical form: Development Task
sense: DEVELOPMENT--TASK lexSense

DEVELOPMENT--TASK lexConcept
type: LexicalConcept
definition: * Take spec, build system * Usually starts on CENELEC P5 * Bottom of CENELEC “V”

Development Task
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

Device
type: LexicalEntry
type: Word
canonical form: Device
sense: DEVICE lexSense

DEVICE lexConcept
type: LexicalConcept
definition: Device{comment:36} A physical entity performing a predefined (set of) task(s). It consists of software integrated on a hardware.

Device
type: Form

DG MOVE
type: LexicalEntry
type: MultiwordExpression
canonical form: DG MOVE
sense: DG--MOVE lexSense

DG--MOVE lexConcept
type: LexicalConcept
definition: Directorate-General for Mobility and Transport

DG MOVE
type: Form

DG RTD
type: LexicalEntry
type: MultiwordExpression
canonical form: DG RTD
sense: DG--RTD lexSense

DG--RTD lexConcept
type: LexicalConcept
definition: Directorate-General for Research and Innovation

DG RTD
type: Form

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

DIAGNOSTICS lexConcept
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.

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

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

Display Panel Glass (LCD) showing pixels without controller.
type: LexicalEntry
type: MultiwordExpression
canonical form: Display Panel Glass (LCD) showing pixels without controller.
sense: DISPLAY--PANEL--GLASS--LCD--SHOWING--PIXELS--WITHOUT--CONTROLLER lexSense

DISPLAY--PANEL--GLASS--LCD--SHOWING--PIXELS--WITHOUT--CONTROLLER lexConcept
type: LexicalConcept
definition: Display Panel Glass (LCD) showing pixels without controller.

Display Panel Glass (LCD) showing pixels without controller.
type: Form

Distribution Job
type: LexicalEntry
type: MultiwordExpression
canonical form: Distribution Job
sense: DISTRIBUTION--JOB lexSense

DISTRIBUTION--JOB lexConcept
type: LexicalConcept
definition: Distribution Job is the complete configuration data packet that is finally provided to the building blocks. The Distribution Job contains the metadata required for the distribution of a CCS Configuration. In addition to linking a referenced CCS Manifest to a CCS Vehicle Identifier or a CCS Trackside Identifier, it also includes information like distribution date / time, activation location, etc. This metadata will be evaluated by central location system (centrally located: typically a CCS configuration management system) and different distributed systems (distributed in the field: e.g. on-board) involved in the distribution process.

Distribution Job
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

DMI - Driver Machine Interface
type: LexicalEntry
type: MultiwordExpression
canonical form: DMI - Driver Machine Interface
sense: DMI-----DRIVER--MACHINE--INTERFACE lexSense

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

DMI - Driver Machine Interface
type: Form

Document Exchange
type: LexicalEntry
type: MultiwordExpression
canonical form: Document Exchange
sense: DOCUMENT--EXCHANGE lexSense

DOCUMENT--EXCHANGE lexConcept
type: LexicalConcept
definition: Document exchange is the act of sharing an exported document with people outside the document authoring group (domain task).

Document Exchange
type: Form

Document Generation and Management
type: LexicalEntry
type: MultiwordExpression
canonical form: Document Generation and Management
sense: DOCUMENT--GENERATION--AND--MANAGEMENT lexSense

DOCUMENT--GENERATION--AND--MANAGEMENT lexConcept
type: LexicalConcept
definition: Document Generation is the collection of information/workitems,{comment:3} and its following updating/review, within a single document having a specific scope and foreseen by the Documents Management Plan.{comment:4} The document generation shall be executed by the task that is in charge of the document (as foreseen by the Documents Management Plan). Templates from SP-Central Modelling Service shall be used (80 Templates ).{comment:27}

Document Generation and Management
type: Form

Documents Publication
type: LexicalEntry
type: MultiwordExpression
canonical form: Documents Publication
sense: DOCUMENTS--PUBLICATION lexSense

DOCUMENTS--PUBLICATION lexConcept
type: LexicalConcept
definition: Documents Publication is the creation of a document baseline and subsequent exportation in a defined exchangeable format (pdf, doc). {comment:5}

Documents Publication
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 Data
type: LexicalEntry
type: MultiwordExpression
canonical form: Domain Data
sense: DOMAIN--DATA lexSense

DOMAIN--DATA lexConcept
type: LexicalConcept
definition: Domain Data as part of the SPT2TS-2040 - CCS/TMS Data Model is a use-case-specific representation of information following the specific needs of affected systems and their functionalities implementing the use case. Domain data are a tailored and potentially transformed subset of Engineering Data. {comment:20}

Domain Data
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

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

EARS lexConcept
type: LexicalConcept
definition: Easy Approach to Requirements Syntax

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

ECMT European Capacity Management Tool
type: LexicalEntry
type: MultiwordExpression
canonical form: ECMT European Capacity Management Tool
sense: ECMT--EUROPEAN--CAPACITY--MANAGEMENT--TOOL lexSense

ECMT--EUROPEAN--CAPACITY--MANAGEMENT--TOOL lexConcept
type: LexicalConcept
definition: ECMT European Capacity Management Tool

ECMT European Capacity Management Tool
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

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

EDDP lexConcept
type: LexicalConcept
definition: European DAC Delivery Program

EDDP
type: Form

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

EECT lexConcept
type: LexicalConcept
definition: ERA Extended Core Team

EECT
type: Form

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

EGNOS lexConcept
type: LexicalConcept
definition: European Geostationary Navigation Overlay Service, European sattellite navigation system

EGNOS
type: Form

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

EIM lexConcept
type: LexicalConcept
definition: European Rail Infrastructure Managers

EIM
type: Form

EoL
type: Acronym
type: LexicalEntry
acronym for: End of Life
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

EoS
type: Acronym
type: LexicalEntry
acronym for: End of Support
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

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

ENGINEERING--DATA lexConcept
type: LexicalConcept
definition: The Engineering Data as part of the SPT2TS-2040 - 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 Data Model.

ENGINEERING--DATA lexConcept 2
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

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 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

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

ENISA lexConcept
type: LexicalConcept
definition: European Union Agency for cybersecurity

ENISA
type: Form

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

EPF lexConcept
type: LexicalConcept
definition: European Passengers' Federation

EPF
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

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

ERA lexConcept
type: LexicalConcept
definition: European Union Agency for Railways

ERA
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

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

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

ERHD
type: Form

ERJU
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: ERJU
canonical form: ERJU

ERJU lexConcept
type: LexicalConcept
definition: Europe’s Rail Joint Undertaking

ERJU
type: Form

ERJU
type: Form

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

ERRAC lexConcept
type: LexicalConcept
definition: European Rail Research Advisory Council

ERRAC
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

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 label
type: LexicalEntry
type: MultiwordExpression
label: 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.
canonical form: 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 lexForm
sense: 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 lexSense

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 lexConcept
type: LexicalConcept
definition: (ERA definition)

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 lexForm
type: Form
written rep: 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.

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

ERTMS 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)

ERTMS lexConcept 2
type: LexicalConcept
definition: European Rail Traffic Management System

ERTMS
type: Form

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

ESA lexConcept
type: LexicalConcept
definition: European Space Agency

ESA
type: Form

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

ESC lexConcept
type: LexicalConcept
definition: European Securities Committee

ESC
type: Form

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

ESIF lexConcept
type: LexicalConcept
definition: European Structural and Investment Funds

ESIF
type: Form

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

ESO lexConcept
type: LexicalConcept
definition: European Standardization Organization

ESO
type: Form

Essential Function: function or capability that is required to maintain health,...
type: LexicalEntry
type: MultiwordExpression
canonical form: Essential Function: function or capability that is required to maintain health,...
sense: ESSENTIAL--FUNCTION---FUNCTION--OR--CAPABILITY--THAT--IS--REQUIRED--TO--MAINTAIN--HEALTH lexSense

ESSENTIAL--FUNCTION---FUNCTION--OR--CAPABILITY--THAT--IS--REQUIRED--TO--MAINTAIN--HEALTH lexConcept
type: LexicalConcept
definition: Essential Function: function or capability that is required to maintain health, safety, the environment and availability for the equipment under control Note 1 to the entry: 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.

Essential Function: function or capability that is required to maintain health,...
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 and availability for the equipment under control Note 1 to the entry: 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.

Essential Function
type: Form

ETA Estimated Time of Arrival
type: LexicalEntry
type: MultiwordExpression
canonical form: ETA Estimated Time of Arrival
sense: ETA--ESTIMATED--TIME--OF--ARRIVAL lexSense

ETA--ESTIMATED--TIME--OF--ARRIVAL lexConcept
type: LexicalConcept
definition: ETA Estimated Time of Arrival

ETA Estimated Time of Arrival
type: Form

ETCS - European Train Control System
type: LexicalEntry
type: MultiwordExpression
canonical form: ETCS - European Train Control System
sense: ETCS-----EUROPEAN--TRAIN--CONTROL--SYSTEM lexSense

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

ETCS - European Train Control System
type: Form

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

ETCS lexConcept
type: LexicalConcept
definition: European Train Control System (ETCS) is a cab-signalling system that incorporates automatic train protection. (ERA definition)

ETCS 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

ETCS
type: Form

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

ETF lexConcept
type: LexicalConcept
definition: European Transport Workers' Federation

ETF
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

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

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

ETSI lexConcept
type: LexicalConcept
definition: European Telecommunications Standards Institute

ETSI
type: Form

EU Regulations
type: LexicalEntry
type: MultiwordExpression
canonical form: EU Regulations
sense: EU--REGULATIONS lexSense

EU--REGULATIONS lexConcept
type: LexicalConcept
definition: ...

EU Regulations
type: Form

EU-RailGoverning Board
type: LexicalEntry
type: MultiwordExpression
canonical form: EU-RailGoverning Board
sense: EU-RAILGOVERNING--BOARD lexSense

EU-RAILGOVERNING--BOARD lexConcept
type: LexicalConcept
definition: EU-RailGoverning Board Final decision body, where a decisions are adopted a majority of at least 55% of the votes

EU-RailGoverning Board
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

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

EUG lexConcept
type: LexicalConcept
definition: ERTMS Users Group

EUG
type: Form

ERTMS
type: Acronym
type: LexicalEntry
acronym for: European Railway Traffic Management System
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. (ERA definition)

European Railway Traffic Management System
type: Form

ERTMS
type: Form

ERJU
type: Acronym
type: LexicalEntry
acronym for: Europe’s Rail Joint Undertaking
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
type: Form

ERJU
type: Form

EU-Rail
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Europe's Rail
canonical form: EU-Rail

EUROPE S--RAIL lexConcept
type: LexicalConcept
definition: Europe's Rail

Europe's Rail
type: Form

EU-Rail
type: Form

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

EUSPA lexConcept
type: LexicalConcept
definition: EU Agency for the Space Programme

EUSPA
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

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: Collection of elements brought together during one interaction or one exchange between functions or components (such as data, signal, flows ...). A exchange item carries elements with the same transport conditions, simultanuously with the same non-functional properties.

Exchange item
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. Exchangeability and interchangeability are related to the physical characteristics of sub-systems whereas interoperability is related to interactions between sub-systems (e.g. also between STM and ETCS on-board there is interoperability).

Exchangeability
type: Form

Extended View View displayed on more than one Display Panel.
type: LexicalEntry
type: MultiwordExpression
canonical form: Extended View View displayed on more than one Display Panel.
sense: EXTENDED--VIEW--VIEW--DISPLAYED--ON--MORE--THAN--ONE--DISPLAY--PANEL lexSense

EXTENDED--VIEW--VIEW--DISPLAYED--ON--MORE--THAN--ONE--DISPLAY--PANEL lexConcept
type: LexicalConcept
definition: Extended View View displayed on more than one Display Panel.

Extended View View displayed on more than one Display Panel.
type: Form

External Button A button which is not directly managed by TDS.
type: LexicalEntry
type: MultiwordExpression
canonical form: External Button A button which is not directly managed by TDS.
sense: EXTERNAL--BUTTON--A--BUTTON--WHICH--IS--NOT--DIRECTLY--MANAGED--BY--TDS lexSense

EXTERNAL--BUTTON--A--BUTTON--WHICH--IS--NOT--DIRECTLY--MANAGED--BY--TDS lexConcept
type: LexicalConcept
definition: External Button A button which is not directly managed by TDS.

External Button A button which is not directly managed by TDS.
type: Form

External Diagnostic, Logging, Orchestration and IT Security Interface(s) (I1)
type: LexicalEntry
type: MultiwordExpression
canonical form: External Diagnostic, Logging, Orchestration and IT Security Interface(s) (I1)
sense: EXTERNAL--DIAGNOSTIC--LOGGING--ORCHESTRATION--AND--IT--SECURITY--INTERFACE--S--I1 lexSense

EXTERNAL--DIAGNOSTIC--LOGGING--ORCHESTRATION--AND--IT--SECURITY--INTERFACE--S--I1 lexConcept
type: LexicalConcept
definition: Interface I1 provides communication-based interfaces between rail systems and central infrastructure components as diagnostics, logging, Orchestration and IT-security services.

External Diagnostic, Logging, Orchestration and IT Security Interface(s) (I1)
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 [SOURCE: IEC 60050-192:2015,192-07-18]

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

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

FA lexConcept
type: LexicalConcept
definition: Flagship Area

FA
type: Form

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

FDFTO lexConcept
type: LexicalConcept
definition: Full Digital Freight Train Operations

FDFTO
type: Form

feature summary
type: LexicalEntry
type: MultiwordExpression
canonical form: feature summary
sense: FEATURE--SUMMARY lexSense

FEATURE--SUMMARY lexConcept
type: LexicalConcept
definition: The ARCADIA method: * Covers all structured engineering activities, from capturing customer operational needs to system integration verification validation (IVV); * Takes into account multiple engineering levels and their effective collaboration (system, subsystem, software, hardware, etc.); * Integrates co-engineering with specialty engineering (safety, security, performance, interfaces, logistics ...) and IVV; * Provides the ability not only to share descriptive models but also to collaboratively validate properties of the definition and the architecture; * Is field-tested in full-scale industrial applications, and is currently deployed on dozens of major projects in several countries and divisions of Thales.

feature summary
type: Form

Feature.
type: LexicalEntry
type: Word
canonical form: Feature.
sense: FEATURE lexSense

FEATURE lexConcept
type: LexicalConcept
definition: High Level description of system functionality. Are bundled by different "Variants".

Feature.
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: 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.

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: Fit Form Function Interface Specification

FFFIS lexConcept 2
type: LexicalConcept
definition: Form Fit Function Interface Specification

FFFIS
type: Form

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

FFF lexConcept
type: LexicalConcept
definition: Fit, Form and Function

FFF
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: 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 2
type: LexicalConcept
definition: FIS - Functional Interface Specification

FIS - Functional Interface Specification
type: Form

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

FIS lexConcept
type: LexicalConcept
definition: Functional Interface Specification

FIS
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 lexConcept 2
type: LexicalConcept
definition: Failure modes and effects analysis (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

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

FM lexConcept
type: LexicalConcept
definition: Founding Members

FM
type: Form

Follow a trace
type: LexicalEntry
type: MultiwordExpression
canonical form: Follow a trace
sense: FOLLOW--A--TRACE lexSense

FOLLOW--A--TRACE 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: 2-image2.png) Figure {caption:Figure}: Trace for a CBO requirement (red point in the middle) in an ALM System System Levels are just “areas of team responsibilities” for working on parts of the graph * System Level 1 / 2 = teams … = Work item detail level … * System Level 3 = teams … = Work item detail level … * System Level 4 = teams … = Work item detail level … * System Level 5 = teams … = Work item detail level … Assigning a work item to a System Level just means: Assigning them to a team. No good idea: Design every System Level with everything that a real-world system would need. Systems on Level 1-4 are no real-world systems, they just structure the work assignment. Trace Example – just one “branch”: The reality is not puristic, it is like a “neuron-mesh” A. SL2: Requirement “High, scalable, and flexible transport capacity” >> B. SL3: Process “efficient ATP for high density lines” >> C. SL4: Requirement “Precise and frequent localisation” in the train >> D. SL3: Architecture (functions) for a high- performance localisation System >> E. SL5: Interface requirements to deliver a map to the train >> F. SL5: Requirement that Traffic CS delivers a reliable map >> …. Think in “good complete traces”, and do not “fill all System Levels” (!) --> It is just important that “traces are complete, good and correct”, with work items assigned to the right team level --> What System Levels are NOT for: Being the basic scheme for everything * Creating a break-down element on every System Level --> this does not work and requires too much effort * Exception: The work item “system” is broken down on every level, but for example interfaces or logical components only exist in System Level 5) When do we need “completion” on System Levels? Sometimes it is necessary. Example 1: Safety…

Follow a trace
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

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

FRMCS lexConcept
type: LexicalConcept
definition: Future Railway Mobile Communication System

FRMCS
type: Form

FRS/FIS
type: LexicalEntry
type: Word
canonical form: FRS/FIS
sense: FRS FIS lexSense

FRS FIS lexConcept
type: LexicalConcept
definition: /Functional Requirement Specification/Functional Interface Specification

FRS/FIS
type: Form

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

FRS lexConcept
type: LexicalConcept
definition: Functional Requirements Specification

FRS
type: Form

FS - Fulling Supervision Mode in ETCS
type: LexicalEntry
type: MultiwordExpression
canonical form: FS - Fulling Supervision Mode in ETCS
sense: FS-----FULLING--SUPERVISION--MODE--IN--ETCS lexSense

FS-----FULLING--SUPERVISION--MODE--IN--ETCS lexConcept
type: LexicalConcept
definition: FS - Fulling Supervision Mode in ETCS

FS - Fulling Supervision Mode in ETCS
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

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

FTE lexConcept
type: LexicalConcept
definition: Full Time Equivalent

FTE
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

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

Functional Application Downtime
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Application Downtime
sense: FUNCTIONAL--APPLICATION--DOWNTIME lexSense

FUNCTIONAL--APPLICATION--DOWNTIME lexConcept
type: LexicalConcept
definition: The time during which a Functional Application is unavailable, offline or not operational until it is started again and is operational afterwards (irrespective of whether this downtime has consequences on other Functional Applications or rail operation as a whole).

Functional Application Downtime
type: Form

Functional Application
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Application
sense: FUNCTIONAL--APPLICATION lexSense

FUNCTIONAL--APPLICATION lexConcept
type: LexicalConcept
definition: A comprehensive set of self-contained software functions, assumed to be provided as one product by a single vendor. A functional application could consist of: * 1..n software functions and * a generic (deployment) configuration. Note that runtime environment is not part of the functional application, even if it is sometimes (not always) exchanged within the same step as the application is changed.

Functional Application
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 sub-systems. It is an architectural choice supporting the ability to replace a sub-system of supplier A by a subsystem of supplier B both compliant with a given FIS.

Functional apportionment
type: Form

Functional Chain
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Chain
sense: FUNCTIONAL--CHAIN lexSense

FUNCTIONAL--CHAIN lexConcept
type: LexicalConcept
definition: Specific organisation of functions and functional exhcanges, forming one path among the set of all possible paths of system data flows. It describes either an expected behaviour of the system in a given context, or expresses non-functional properties on the path (such as latency, criticality, confidentiality, redundancy ...)

Functional Chain
type: Form

Functional Exchange
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Exchange
sense: FUNCTIONAL--EXCHANGE lexSense

FUNCTIONAL--EXCHANGE lexConcept
type: LexicalConcept
definition: possible flow of exchange items between 2 functions through their respectives functions

Functional Exchange
type: Form

Functional Port
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Port
sense: FUNCTIONAL--PORT lexSense

FUNCTIONAL--PORT lexConcept
type: LexicalConcept
definition: Connection point of one or more functional exchanges allocated to a function, by specifying what the function can provide (output port) and what it must perform (input port) (original definition may be not that accurate).

Functional Port
type: Form

Functional Requirements
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Requirements
sense: FUNCTIONAL--REQUIREMENTS lexSense

FUNCTIONAL--REQUIREMENTS lexConcept
type: LexicalConcept
definition: Functional Requirements specify the functions of the system. What the system has to do in order to achieve the Operational Requirement. They capture and define the sub-purposes of the overall system purpose (given in the operational requirements). Since Functional Requirements specify the functions of the system that are best described as a verb-noun phrase that defines an action on an object.

Functional Requirements
type: Form

FS
type: Acronym
type: LexicalEntry
acronym for: Functional System
canonical form: FS

FUNCTIONAL--SYSTEM lexConcept
type: LexicalConcept
definition: A Functional System consists of the Functional Application (see above) plus the Runtime Environment (see below) but without Hardware. The purpose to exclude HW is to address a painpoint from today regarding HW exchange..

Functional System
type: Form

FS
type: Form

Functional Team
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional Team
sense: FUNCTIONAL--TEAM lexSense

FUNCTIONAL--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 addressed 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” (image: 1-Bild_2.png) (image: 2-Grafik_1.png)

Functional Team
type: Form

Functionality
type: LexicalEntry
type: Word
canonical form: Functionality
sense: FUNCTIONALITY lexSense

FUNCTIONALITY lexConcept
type: LexicalConcept
definition: ...

Functionality
type: Form

Function
type: LexicalEntry
type: Word
canonical form: Function
sense: FUNCTION lexSense

FUNCTION lexConcept
type: LexicalConcept
definition: A function transforms several one or more input values to several one or more output values according to the function’s behaviour. The function’s behaviour is defined by one or multiple functional requirements, defining “what” the function is doing. Additional non-functional requirements attached to the function define the quality attributes of “how” (how safe, how accurate, how fast, how reliable, etc.) the function is performing the transformation. Some non-functional requirements, e.g., on weight constraints or physical dimension constraints), will also be allocated to subsystems.

FUNCTION lexConcept 2
type: LexicalConcept
definition: action, operation or service fulfilled by the system, or by an actor interacting with the system

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

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

Generic workflow types
type: LexicalEntry
type: MultiwordExpression
canonical form: Generic workflow types
sense: GENERIC--WORKFLOW--TYPES lexSense

GENERIC--WORKFLOW--TYPES lexConcept
type: LexicalConcept
definition: * Assignment workflow: Unassigned, rejected, or unlinked work items are assigned to a team based on the work item type and system level (done by a functional team, see [2]) * Derivation workflow: The standard workflow, where work items are resolved along the mandatory trace (along the workflow rules), work is moving from team to team, or from team collaboration to team collaboration * Trace change workflow: A change in a trace is analysed up to the highest work item again (done by modelling service, all work items get “suspect”), and from there all derivations are checked, resolved, and approved again (derivation workflow). * Uplink workflow: A set of traces is “connected” to another set. This typically happens, when “external contributions” are imported (e.g. a team that proposes the interfaces of a subsystem). The connection links are created as proposals. For all new connection links a trace change workflow is executed. Redundancies are analysed and eliminated, what again triggers trace change workflows. * Trace analysis workflow: Progress and trace consistency are analysed and reported by the modelling service These workflows are assigned by the team or person, where the triggering work item is assigned to. The trace analysis is done by the modelling service on a frequent basis.

Generic workflow types
type: Form

GoA - Grade of Automation
type: LexicalEntry
type: MultiwordExpression
canonical form: GoA - Grade of Automation
sense: GOA-----GRADE--OF--AUTOMATION lexSense

GOA-----GRADE--OF--AUTOMATION lexConcept
type: LexicalConcept
definition: GoA - Grade of Automation

GoA - Grade of Automation
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

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

Ground footprint
type: LexicalEntry
type: MultiwordExpression
canonical form: Ground footprint
sense: GROUND--FOOTPRINT lexSense

GROUND--FOOTPRINT lexConcept
type: LexicalConcept
definition: The ground footprint of an object moving on the earth is defined as the projection of its volume on the earth ground. Note: This defintion is applicable for collission detection between two ground vehicles moving on the same level.

Ground footprint
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

GSM-R / FRMCS
type: LexicalEntry
type: MultiwordExpression
canonical form: GSM-R / FRMCS
sense: GSM-R-- --FRMCS lexSense

GSM-R-- --FRMCS lexConcept
type: LexicalConcept
definition: Future Railway Mobile Communication System

GSM-R / FRMCS
type: Form

GUI Graphical User Interface
type: LexicalEntry
type: MultiwordExpression
canonical form: GUI Graphical User Interface
sense: GUI--GRAPHICAL--USER--INTERFACE lexSense

GUI--GRAPHICAL--USER--INTERFACE lexConcept
type: LexicalConcept
definition: GUI Graphical User Interface

GUI Graphical User Interface
type: Form

GW - Gateway
type: LexicalEntry
type: MultiwordExpression
canonical form: GW - Gateway
sense: GW-----GATEWAY lexSense

GW-----GATEWAY lexConcept
type: LexicalConcept
definition: GW - Gateway

GW - Gateway
type: Form

Hard Key Physical key not part of view. This key can also have a text label or s...
type: LexicalEntry
type: MultiwordExpression
canonical form: Hard Key Physical key not part of view. This key can also have a text label or s...
sense: HARD--KEY--PHYSICAL--KEY--NOT--PART--OF--VIEW---THIS--KEY--CAN--ALSO--HAVE--A--TEXT--LABEL--OR--S lexSense

HARD--KEY--PHYSICAL--KEY--NOT--PART--OF--VIEW---THIS--KEY--CAN--ALSO--HAVE--A--TEXT--LABEL--OR--S lexConcept
type: LexicalConcept
definition: Hard Key Physical key not part of view. This key can also have a text label or symbol.

Hard Key Physical key not part of view. This key can also have a text label or s...
type: Form

Hardware Abstraction Interface (I2)
type: LexicalEntry
type: MultiwordExpression
canonical form: Hardware Abstraction Interface (I2)
sense: HARDWARE--ABSTRACTION--INTERFACE--I2 lexSense

HARDWARE--ABSTRACTION--INTERFACE--I2 lexConcept
type: LexicalConcept
definition: Interface I2 provides an abstraction of all technology layers above from the specific hardware used below, enabling easy replaceability of commercial of-the-shelf hardware.

Hardware Abstraction Interface (I2)
type: Form

Hardware Layer
type: LexicalEntry
type: MultiwordExpression
canonical form: Hardware Layer
sense: HARDWARE--LAYER lexSense

HARDWARE--LAYER lexConcept
type: LexicalConcept
definition: Contains the actual Hardware, i.e. the physical and electronic parts of a computer or other piece of equipment.

Hardware Layer
type: Form

Hardware unavailability
type: LexicalEntry
type: MultiwordExpression
canonical form: Hardware unavailability
sense: HARDWARE--UNAVAILABILITY lexSense

HARDWARE--UNAVAILABILITY lexConcept
type: LexicalConcept
definition: Related to hardware defects (unexpected).

Hardware unavailability
type: Form

HW
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Hardware
canonical form: HW

HARDWARE lexConcept
type: LexicalConcept
definition: The physical and electronic parts of a computer or other piece of equipment.

Hardware
type: Form

HW
type: Form

Hardwired connection
type: LexicalEntry
type: MultiwordExpression
canonical form: Hardwired connection
sense: HARDWIRED--CONNECTION lexSense

HARDWIRED--CONNECTION lexConcept
type: LexicalConcept
definition: A means of communication using a discrete wired interface between the communication peers. Having a 0/1 or -1/0/1 logic per wire.

Hardwired connection
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

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

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

HFI Activities
type: LexicalEntry
type: MultiwordExpression
canonical form: HFI Activities
sense: HFI--ACTIVITIES lexSense

HFI--ACTIVITIES lexConcept
type: LexicalConcept
definition: HFI Activities are conducted to optimise the effectiveness and efficiency of human performance by fully considering the human contribution to system performance. Human Performance is the observable and measurable behaviour that occurs in job and task situations, the extent to which goals such as speed, accuracy, quality and other criteria are met by people in their work environments. The focus is on the ability of operators and maintainers to meet system performance requirements, including reliability and maintainability, under the conditions in which the system is employed.

HFI Activities
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 user interface. Examples of HMI Components are PC Workstation, tablet device, smart phone, device with touch screen,...

HMI Component
type: Form

HMI Element An HMI Element is a physical component that interacts with the drive...
type: LexicalEntry
type: MultiwordExpression
canonical form: HMI Element An HMI Element is a physical component that interacts with the drive...
sense: HMI--ELEMENT--AN--HMI--ELEMENT--IS--A--PHYSICAL--COMPONENT--THAT--INTERACTS--WITH--THE--DRIVE lexSense

HMI--ELEMENT--AN--HMI--ELEMENT--IS--A--PHYSICAL--COMPONENT--THAT--INTERACTS--WITH--THE--DRIVE lexConcept
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 An HMI Element is a physical component that interacts with the drive...
type: Form

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

HOF lexConcept
type: LexicalConcept
definition: Human and Organizational Factors (lead to workitem SPPR-2246 - Application Condition and perhaps SPPR-2244 - SRAC)

HOF
type: Form

Horizontal integration
type: LexicalEntry
type: MultiwordExpression
canonical form: Horizontal integration
sense: HORIZONTAL--INTEGRATION lexSense

HORIZONTAL--INTEGRATION lexConcept
type: LexicalConcept
definition: Integration of different Functional Applications, running on the same or different computing platform(s).

Horizontal integration
type: Form

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

HRM lexConcept
type: LexicalConcept
definition: Holistic Requirements Model

HRM
type: Form

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

HSI lexConcept
type: LexicalConcept
definition: Human-System Integration, an interdisciplinary approach that aims at optimizing in an early development stage the global system performance by desgining solutions adapted for both human and technical system. HSI studies integrates work from multiple human centered domains - process analysis, both qualitative and quantitatve, ergonomics, safety, survivability, habitability, skill analysis, training. HSI typically help define user interfaces and lead to workitem SPPR-2246 - Application Condition or SPPR-2244 - SRAC .

HSI
type: Form

Human Factors
type: LexicalEntry
type: MultiwordExpression
canonical form: Human Factors
sense: HUMAN--FACTORS lexSense

HUMAN--FACTORS lexConcept
type: LexicalConcept
definition: Human factors issues include anything that affects human performance, particularly those factors that may cause or contribute to human error. The main human factors areas include: * Individual (physical size, personal preferences, cognitive skills, attitudes, background) * Organisation (culture, work pattern, communications, supervision, training) * Job (design of equipment, rules and procedures, tools, signage, environment) The purpose of human factors is to minimise safety risk from the possibility of human error by: * ensuring human characteristics are accounted for in the design (or re-design) of new and existing systems and equipment * identifying the issues which may cause or contribute to human errors * conducting activities and applying controls to reduce likelihood and consequences.

Human Factors
type: Form

HMI
type: Acronym
type: LexicalEntry
acronym for: Human Machine Interface
canonical form: HMI

HUMAN--MACHINE--INTERFACE lexConcept
type: LexicalConcept
definition: Graphical component to interact with a user e.g., by train graph.

HUMAN--MACHINE--INTERFACE lexConcept 2
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

I AM ONLY AN EXAMPLE
type: LexicalEntry
type: MultiwordExpression
canonical form: I AM ONLY AN EXAMPLE
sense: I--AM--ONLY--AN--EXAMPLE lexSense

I--AM--ONLY--AN--EXAMPLE lexConcept
type: LexicalConcept
definition: AFARP - As far as reasonably practicable. Denote that an action shall be done until the cost to do so does not justify the benefit of doing it.

I AM ONLY AN EXAMPLE
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

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

IEC lexConcept
type: LexicalConcept
definition: International Electrotechnical Commission

IEC
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

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

IM lexConcept
type: LexicalConcept
definition: Infrastructure Manager

IM
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; SPPRAMSS-337 - [Directive (EU) 2016/798]

incident
type: Form

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

INCOSE lexConcept
type: LexicalConcept
definition: International Council on Systems Engineering

INCOSE
type: Form

Infrastructure Manager Operational Area of Control defines the region under the...
type: LexicalEntry
type: MultiwordExpression
canonical form: Infrastructure Manager Operational Area of Control defines the region under the...
sense: INFRASTRUCTURE--MANAGER--OPERATIONAL--AREA--OF--CONTROL--DEFINES--THE--REGION--UNDER--THE lexSense

INFRASTRUCTURE--MANAGER--OPERATIONAL--AREA--OF--CONTROL--DEFINES--THE--REGION--UNDER--THE lexConcept
type: LexicalConcept
definition: Infrastructure Manager Operational Area of Control defines the region under the responsability of only one Infrastructure Manager

Infrastructure Manager Operational Area of Control defines the region under the...
type: Form

IM
type: Acronym
type: LexicalEntry
acronym for: Infrastructure Manager
canonical form: IM

INFRASTRUCTURE--MANAGER lexConcept
type: LexicalConcept
definition: Infrastructure Manager

Infrastructure Manager
type: Form

IM
type: Form

Input documents
type: LexicalEntry
type: MultiwordExpression
canonical form: Input documents
sense: INPUT--DOCUMENTS lexSense

INPUT--DOCUMENTS lexConcept
type: LexicalConcept
definition: * Input documents” are for example * Imported documents that are stored as “unstructured” content in the ALM in the first step (no work items created already) * Unstructured documents that are step by step converted to documents with structured work items * A model or model sketch from another modelling system, that is not compliant or convertible to SP modelling method/system, created as input document with concrete Polarion work items in the status “proposal”. These are seen as input sketches and are added manually into the SP modelling system using the correct method and modelling process * ALM documents in which new work items are created in a free structure and sequence (workflow designed in the domains) * Input documents are not used as formal deliverable (because they are created manually and may not contain all work items in a certain scope), but they can be used as background documentation. * The differentiation of input and output documents allows to create input documents along the needs of the workflows – having “things at one place where the team is currently working” – without the constraint to structure or “sort” it as a formal output (image: 1-screenshot-20221230-141047.png)

Input documents
type: Form

Instance of a Computing platform/Computing Environment
type: LexicalEntry
type: MultiwordExpression
canonical form: Instance of a Computing platform/Computing Environment
sense: INSTANCE--OF--A--COMPUTING--PLATFORM COMPUTING--ENVIRONMENT lexSense

INSTANCE--OF--A--COMPUTING--PLATFORM COMPUTING--ENVIRONMENT lexConcept
type: LexicalConcept
definition: Refers to all specific instances of RTE and Hardware required to run a specific Functional Application

Instance of a Computing platform/Computing Environment
type: Form

Integration Task
type: LexicalEntry
type: MultiwordExpression
canonical form: Integration Task
sense: INTEGRATION--TASK lexSense

INTEGRATION--TASK lexConcept
type: LexicalConcept
definition: * Combine elements, validate/test whole system behaviour, implement/commission * Right side of CENELEC “V”

Integration Task
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 lexConcept 2
type: LexicalConcept
definition: See SPT2CE-244 - Horizontal integration and SPT2CE-245 - Vertical integration

Integration
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 without any integration effort (lowest reasonable integration effort) and without any need for recertification. Exchangeability and interchangeability are related to the physical characteristics of sub-systems whereas interoperability is related to interactions between subsystems (e.g. also between STM and ETCS on-board there is interoperability).

Interchangeability
type: Form

Interface
type: LexicalEntry
type: Word
canonical form: Interface
sense: INTERFACE lexSense

INTERFACE lexConcept
type: LexicalConcept
definition: With an interface the sub-systems of different suppliers are combined.

INTERFACE lexConcept 2
type: LexicalConcept
definition: Based on ISO/IEC 2382, a shared boundary between two systems or subsystems, defined by various characteristics pertaining to the functions, physical signal exchanges, and other characteristics.

INTERFACE lexConcept 3
type: LexicalConcept
definition: a means provided or required by components for an interaction between them or with actors

Interface
type: Form

IXL
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Interlocking
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 The Internal Button is a button which is managed directly by TDS...
type: LexicalEntry
type: MultiwordExpression
canonical form: Internal Button The Internal Button is a button which is managed directly by TDS...
sense: INTERNAL--BUTTON--THE--INTERNAL--BUTTON--IS--A--BUTTON--WHICH--IS--MANAGED--DIRECTLY--BY--TDS lexSense

INTERNAL--BUTTON--THE--INTERNAL--BUTTON--IS--A--BUTTON--WHICH--IS--MANAGED--DIRECTLY--BY--TDS lexConcept
type: LexicalConcept
definition: Internal Button The Internal Button is a button which is managed directly by TDS.

Internal Button The Internal Button is a button which is managed directly by TDS...
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. (e.g. Viewpoint)

Internal Publication
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 networks (IMs) and that an infrastructure network is able to interact with trains of different Railway Undertakings, using systems/sub-systems from different origins. Exchangeability and interchangeability are related to the physical characteristics of sub-systems whereas interoperability is related to interactions between subsystems (e.g. also between STM and ETCS on-board there is interoperability).

Interoperability
type: Form

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

IPSE lexConcept
type: LexicalConcept
definition: Innovation Pillar System Experts

IPSE
type: Form

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

ISO lexConcept
type: LexicalConcept
definition: International Organization for Standardization

ISO
type: Form

Issue.
type: LexicalEntry
type: Word
canonical form: Issue.
sense: ISSUE lexSense

ISSUE lexConcept
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

JP - Journey Profile
type: LexicalEntry
type: MultiwordExpression
canonical form: JP - Journey Profile
sense: JP-----JOURNEY--PROFILE lexSense

JP-----JOURNEY--PROFILE lexConcept
type: LexicalConcept
definition: JP - Journey Profile

JP - Journey Profile
type: Form

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

JU lexConcept
type: LexicalConcept
definition: (Europe’s Rail) Joint Undertaking

JU
type: Form

Key Controller Controller which manages states and failures of Hard Keys (intern...
type: LexicalEntry
type: MultiwordExpression
canonical form: Key Controller Controller which manages states and failures of Hard Keys (intern...
sense: KEY--CONTROLLER--CONTROLLER--WHICH--MANAGES--STATES--AND--FAILURES--OF--HARD--KEYS--INTERN lexSense

KEY--CONTROLLER--CONTROLLER--WHICH--MANAGES--STATES--AND--FAILURES--OF--HARD--KEYS--INTERN lexConcept
type: LexicalConcept
definition: Key Controller Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.

Key Controller Controller which manages states and failures of Hard Keys (intern...
type: Form

Lateral Key Hard Key located close to a Display Area allowing soft key technolog...
type: LexicalEntry
type: MultiwordExpression
canonical form: Lateral Key Hard Key located close to a Display Area allowing soft key technolog...
sense: LATERAL--KEY--HARD--KEY--LOCATED--CLOSE--TO--A--DISPLAY--AREA--ALLOWING--SOFT--KEY--TECHNOLOG lexSense

LATERAL--KEY--HARD--KEY--LOCATED--CLOSE--TO--A--DISPLAY--AREA--ALLOWING--SOFT--KEY--TECHNOLOG lexConcept
type: LexicalConcept
definition: Lateral Key Hard Key located close to a Display Area allowing soft key technology.

Lateral Key Hard Key located close to a Display Area allowing soft key technolog...
type: Form

Layout Controller The Layout Controller manages the Layout for an Area.
type: LexicalEntry
type: MultiwordExpression
canonical form: Layout Controller The Layout Controller manages the Layout for an Area.
sense: LAYOUT--CONTROLLER--THE--LAYOUT--CONTROLLER--MANAGES--THE--LAYOUT--FOR--AN--AREA lexSense

LAYOUT--CONTROLLER--THE--LAYOUT--CONTROLLER--MANAGES--THE--LAYOUT--FOR--AN--AREA lexConcept
type: LexicalConcept
definition: Layout Controller The Layout Controller manages the Layout for an Area.

Layout Controller The Layout Controller manages the Layout for an Area.
type: Form

Layout Element Controller The Layout Element Controller managesLayout Elements o...
type: LexicalEntry
type: MultiwordExpression
canonical form: Layout Element Controller The Layout Element Controller managesLayout Elements o...
sense: LAYOUT--ELEMENT--CONTROLLER--THE--LAYOUT--ELEMENT--CONTROLLER--MANAGESLAYOUT--ELEMENTS--O lexSense

LAYOUT--ELEMENT--CONTROLLER--THE--LAYOUT--ELEMENT--CONTROLLER--MANAGESLAYOUT--ELEMENTS--O lexConcept
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 The Layout Element Controller managesLayout Elements o...
type: Form

Layout Engine The Layout Engine is a generic piece of software able to generate...
type: LexicalEntry
type: MultiwordExpression
canonical form: Layout Engine The Layout Engine is a generic piece of software able to generate...
sense: LAYOUT--ENGINE--THE--LAYOUT--ENGINE--IS--A--GENERIC--PIECE--OF--SOFTWARE--ABLE--TO--GENERATE lexSense

LAYOUT--ENGINE--THE--LAYOUT--ENGINE--IS--A--GENERIC--PIECE--OF--SOFTWARE--ABLE--TO--GENERATE lexConcept
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 The Layout Engine is a generic piece of software able to generate...
type: Form

Layout Layout is a list of layout elements which is displayed in an area.
type: LexicalEntry
type: MultiwordExpression
canonical form: Layout Layout is a list of layout elements which is displayed in an area.
sense: LAYOUT--LAYOUT--IS--A--LIST--OF--LAYOUT--ELEMENTS--WHICH--IS--DISPLAYED--IN--AN--AREA lexSense

LAYOUT--LAYOUT--IS--A--LIST--OF--LAYOUT--ELEMENTS--WHICH--IS--DISPLAYED--IN--AN--AREA lexConcept
type: LexicalConcept
definition: Layout Layout is a list of layout elements which is displayed in an area.

Layout Layout is a list of layout elements which is displayed in an area.
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

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

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

Logial Component
type: LexicalEntry
type: MultiwordExpression
canonical form: Logial Component
sense: LOGIAL--COMPONENT lexSense

LOGIAL--COMPONENT lexConcept
type: LexicalConcept
definition: conceptual element being part of the system, contributing to its behaviour, by interacting with other logical components and logical actors

Logial Component
type: Form

Logical actor
type: LexicalEntry
type: MultiwordExpression
canonical form: Logical actor
sense: LOGICAL--ACTOR lexSense

LOGICAL--ACTOR lexConcept
type: LexicalConcept
definition: external entity (human, system, ...) interacting with the logical components of the system of interest through their interfaces

Logical actor
type: Form

Logical Architectur Concept
type: LexicalEntry
type: MultiwordExpression
canonical form: Logical Architectur Concept
sense: LOGICAL--ARCHITECTUR--CONCEPT lexSense

LOGICAL--ARCHITECTUR--CONCEPT lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

Logical Architectur Concept
type: Form

Logical Component
type: LexicalEntry
type: MultiwordExpression
canonical form: Logical Component
sense: LOGICAL--COMPONENT lexSense

LOGICAL--COMPONENT lexConcept
type: LexicalConcept
definition: An aggregation of logical functions that together fulfil a very specific task. Logical components are not yet allocated to a specific location kind (trackside or onboard) nor do they have any physical properties or requirements (like space requirements, permitted temperature ranges, etc.). Logical components are also only connected via FIS and not via FFFIS interfaces. Logical components or part of their logical functions are allocated to subsystems to define the subsystem behaviour.

Logical Component
type: Form

Logical Functional Chain
type: LexicalEntry
type: MultiwordExpression
canonical form: Logical Functional Chain
sense: LOGICAL--FUNCTIONAL--CHAIN lexSense

LOGICAL--FUNCTIONAL--CHAIN lexConcept
type: LexicalConcept
definition: an ordered collection of behavioural exchanges transmitting one or several logical functional exchanges

Logical Functional Chain
type: Form

Logical Function
type: LexicalEntry
type: MultiwordExpression
canonical form: Logical Function
sense: LOGICAL--FUNCTION lexSense

LOGICAL--FUNCTION lexConcept
type: LexicalConcept
definition: A function derived during logical architecture by splitting a system function.

Logical Function
type: Form

Logical/Physical Relationsships
type: LexicalEntry
type: MultiwordExpression
canonical form: Logical/Physical Relationsships
sense: LOGICAL PHYSICAL--RELATIONSSHIPS lexSense

LOGICAL PHYSICAL--RELATIONSSHIPS lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

Logical/Physical Relationsships
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 Device that converts an electrical audio signal into a corresponding...
type: LexicalEntry
type: MultiwordExpression
canonical form: Loudspeaker Device that converts an electrical audio signal into a corresponding...
sense: LOUDSPEAKER--DEVICE--THAT--CONVERTS--AN--ELECTRICAL--AUDIO--SIGNAL--INTO--A--CORRESPONDING lexSense

LOUDSPEAKER--DEVICE--THAT--CONVERTS--AN--ELECTRICAL--AUDIO--SIGNAL--INTO--A--CORRESPONDING lexConcept
type: LexicalConcept
definition: Loudspeaker Device that converts an electrical audio signal into a corresponding sound.

Loudspeaker Device that converts an electrical audio signal into a corresponding...
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

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] SPT2ARC-1616 .

Maintainability
type: Form

Maintenance Costs
type: LexicalEntry
type: MultiwordExpression
canonical form: Maintenance Costs
sense: MAINTENANCE--COSTS lexSense

MAINTENANCE--COSTS lexConcept
type: LexicalConcept
definition: Costs for maintaining the railway system

Maintenance Costs
type: Form

MO
type: Acronym
type: LexicalEntry
acronym for: Maintenance Operator
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

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

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

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

MBSE lexConcept
type: LexicalConcept
definition: Model based System Engineering

MBSE
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
type: LexicalEntry
type: MultiwordExpression
canonical form: MDS - Multi Display System
sense: MDS-----MULTI--DISPLAY--SYSTEM lexSense

MDS-----MULTI--DISPLAY--SYSTEM lexConcept
type: LexicalConcept
definition: MDS - Multi Display System

MDS - Multi Display System
type: Form

methodology
type: LexicalEntry
type: Word
canonical form: methodology
sense: METHODOLOGY lexSense

METHODOLOGY lexConcept
type: LexicalConcept
definition: The ARCADIA method is used to identify functional chains, their overlapping scenarios and desired performance, along with their support by the architecture. * Starting with the first level of system analysis, they ensure traceability throughout the process definition and check each proposed architectural design against expected performance and constraints. * The non-functional properties expected from the system solution are also formalized in 'viewpoints'. Each viewpoint captures constraints that the system should face or meet (feared events, security threats, latency expectations, product line or reuse constraints, power consumption or cost issues, and more). * Then the architecture model is automatically analyzed to verify that it meets these constraints, thanks to dedicated expert rules (performance computation, resource consumption, safety or security barriers, etc.). This analysis can be done very early in the development cycle, detecting design issues as soon as possible ("early validation"). As a summary, the approach to characterization by views (or "viewpoints") cross-checks that the proposed architecture is capable of providing the required functions with the desired level of performance, security, dependability, mass, scalability, environments, mass, interfaces, etc. ensuring the consistency of engineering decisions, because all engineering stakeholders share the same engineering information, and can apply his/her own views and checks to them, so as to secure the common definition.

methodology
type: Form

Method
type: LexicalEntry
type: Word
canonical form: Method
sense: METHOD lexSense

METHOD lexConcept
type: LexicalConcept
definition: Method is a grouping of guidance, modelling{comment:72} language, rules, techniques and patterns. Different methods may be available for the same task (e.g. Define stakeholders)

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 The Microphone Controller manages states and signals of Mi...
type: LexicalEntry
type: MultiwordExpression
canonical form: Microphone Controller The Microphone Controller manages states and signals of Mi...
sense: MICROPHONE--CONTROLLER--THE--MICROPHONE--CONTROLLER--MANAGES--STATES--AND--SIGNALS--OF--MI lexSense

MICROPHONE--CONTROLLER--THE--MICROPHONE--CONTROLLER--MANAGES--STATES--AND--SIGNALS--OF--MI lexConcept
type: LexicalConcept
definition: Microphone Controller The Microphone Controller manages states and signals of Microphone.

Microphone Controller The Microphone Controller manages states and signals of Mi...
type: Form

Microphone Device that translates sound vibrations from the air into electronic...
type: LexicalEntry
type: MultiwordExpression
canonical form: Microphone Device that translates sound vibrations from the air into electronic...
sense: MICROPHONE--DEVICE--THAT--TRANSLATES--SOUND--VIBRATIONS--FROM--THE--AIR--INTO--ELECTRONIC lexSense

MICROPHONE--DEVICE--THAT--TRANSLATES--SOUND--VIBRATIONS--FROM--THE--AIR--INTO--ELECTRONIC lexConcept
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 Device that translates sound vibrations from the air into electronic...
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

Migrateability / Scalability
type: LexicalEntry
type: MultiwordExpression
canonical form: Migrateability / Scalability
sense: MIGRATEABILITY-- --SCALABILITY lexSense

MIGRATEABILITY-- --SCALABILITY lexConcept
type: LexicalConcept
definition: The property of a system to allow changes to one or multiple building blocks, without affecting other building blocks or the overall system.{comment:144}

Migrateability / Scalability
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.

Migration Plateau
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 replacing or converting parts of existing legacy CCS/TMS operational processes or systems to corresponding parts of the System Pillar Harmonized Operational Processes respectively the System Pillar Reference Architecture (SPRA).{comment:1}

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

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

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

Mode&State Concept
type: LexicalEntry
type: MultiwordExpression
canonical form: Mode&State Concept
sense: MODE--AND--STATE--CONCEPT lexSense

MODE--AND--STATE--CONCEPT lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

Mode&State Concept
type: Form

Mode Machine
type: LexicalEntry
type: MultiwordExpression
canonical form: Mode Machine
sense: MODE--MACHINE lexSense

MODE--MACHINE lexConcept
type: LexicalConcept
definition: a collection of modes connected by transitions

Mode Machine
type: Form

Mode Transition
type: LexicalEntry
type: MultiwordExpression
canonical form: Mode Transition
sense: MODE--TRANSITION lexSense

MODE--TRANSITION lexConcept
type: LexicalConcept
definition: A change of mode toward itself or toward another mode. A transition is characterised by a trigger which can be a boolean condition applied on certain model elements, such as functional exchanges.

Mode Transition
type: Form

Model synchronisation
type: LexicalEntry
type: MultiwordExpression
canonical form: Model synchronisation
sense: MODEL--SYNCHRONISATION lexSense

MODEL--SYNCHRONISATION lexConcept
type: LexicalConcept
definition: * There are two types of synchronisations: * A copy of all MBSE models is stored in the ALM. The copied work items can be part of the ALM workflow or can be approved, decided, commented and linked in the ALM. * Synchronisation between “mother LA/PA” and “daughter LA/PA” in the MBSE platform. These are done to split architecting work to different teams. * Example (start situation for the SP): (image: 1-Picture_1.png)

Model synchronisation
type: Form

Mode
type: LexicalEntry
type: Word
canonical form: Mode
sense: MODE lexSense

MODE lexConcept
type: LexicalConcept
definition: Kind of system behaviour that is expected in given usage conditions. Modes can be applied to elements such as actors and components.

Mode
type: Form

Modularity
type: LexicalEntry
type: Word
canonical form: Modularity
sense: MODULARITY lexSense

MODULARITY lexConcept
type: LexicalConcept
definition: Modularity is used in this document as a general term for dividing a system/sub-system/module in sub-systems/modules.

MODULARITY lexConcept 2
type: LexicalConcept
definition: The property of a system being composed of a coherent whole of single, independent building blocks or 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

Module
type: LexicalEntry
type: Word
canonical form: Module
sense: MODULE lexSense

MODULE lexConcept
type: LexicalConcept
definition: {comment:34} A module is a sourceable unit of the CCS system (hardware and/or software), having full defined functionality, interface, performance, safety. {comment:180}

Module
type: Form

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

MOE lexConcept
type: LexicalConcept
definition: Measure of Effectiveness (that the system performs as required). Characteristics: * Relates to performance * Objective * Simple to state * Testable * Complete * Clear * States any time dependency * States any environmental conditions * Can be measured quantitatively (if required, may be measured statistically or as a probability) * Easy to measure * Select only MoEs that measure the degree to which the desired outcome is achieved * Use the same MoEs to measure more than one condition when appropriate * Structure so that they have measurable, collectible, and relevant indicators * Write as statements (not questions) * Maximize clarity

MOE
type: Form

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

MOP lexConcept
type: LexicalConcept
definition: Measure of Performance. (one aspect of MOE)

MOP
type: Form

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

MOTBF 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]

MOTBF
type: Form

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

MOT lexConcept
type: LexicalConcept
definition: Ministry of Transportation

MOT
type: Form

Moving Block
type: LexicalEntry
type: MultiwordExpression
canonical form: Moving Block
sense: MOVING--BLOCK lexSense

MOVING--BLOCK lexConcept
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

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 time between failure

MTBF lexConcept 2
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

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

NIP
type: Acronym
type: LexicalEntry
acronym for: National Implemenation Plan
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

NB-Rail
type: LexicalEntry
type: Word
canonical form: NB-Rail
sense: NB-RAIL lexSense

NB-RAIL lexConcept
type: LexicalConcept
definition: Notified bodies for interoperability in the railway sector

NB-Rail
type: Form

Network Component
type: LexicalEntry
type: MultiwordExpression
canonical form: Network Component
sense: NETWORK--COMPONENT lexSense

NETWORK--COMPONENT lexConcept
type: LexicalConcept
definition: An implementation of data networking functions as switching, routing, filtering or tunneling. Examples of Network Components are network switches, routers, firewalls, data diodes and VPNs

Network Component
type: Form

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

NFF lexConcept
type: LexicalConcept
definition: No Fault Found

NFF
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 Requirements
type: LexicalEntry
type: MultiwordExpression
canonical form: Non-functional Requirements
sense: NON-FUNCTIONAL--REQUIREMENTS lexSense

NON-FUNCTIONAL--REQUIREMENTS lexConcept
type: LexicalConcept
definition: Non-Functional Requirements are constraints on the system that define how well something is to be done or how it is to be done which fall into three categories:{comment:66} * Performance Requirements SPPR-4175 - Performance Requirements ; * System Requirements SPPR-4177 - System Requirements ;{comment:65} * Implementation Requirements SPPR-4180 - Implementation Requirements . These categories are derived from consideration of the essential relationships with the Operational{comment:31} and Functional Requirements and ensure the completeness and consistency of the requirements model (It is these essential relationships between the functionally-based requirements and constraint-based requirements that make the Holistic Requirements Model so useful).

Non-functional Requirements
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

NOTIF-IT
type: LexicalEntry
type: Word
canonical form: NOTIF-IT
sense: NOTIF-IT lexSense

NOTIF-IT lexConcept
type: LexicalConcept
definition: The database for Notified National Rules. Has been replaced by SRD: Single Rule Database [SOURCE: ERA, https://www.era.europa.eu/domains/registers/srd_en ]

NOTIF-IT
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 lexConcept 2
type: LexicalConcept
definition: National Safety Authority

NSA
type: Form

NTC - National Train Control
type: LexicalEntry
type: MultiwordExpression
canonical form: NTC - National Train Control
sense: NTC-----NATIONAL--TRAIN--CONTROL lexSense

NTC-----NATIONAL--TRAIN--CONTROL lexConcept
type: LexicalConcept
definition: NTC - National Train Control

NTC - National Train Control
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

[OAB] [Entities/actors]
type: LexicalEntry
type: MultiwordExpression
canonical form: [OAB] [Entities/actors]
sense: OAB -- ENTITIES ACTORS lexSense

OAB -- ENTITIES ACTORS lexConcept
type: LexicalConcept
definition: Capella Viewpoint. Purpose: displays the sub-entities and actors of an entity. Rule: contains at least 1 operational entity Rule: May contain operational actors Rule: contains no operational activities Filter: TBD

[OAB] [Entities/actors]
type: Form

[OAB] [Process Involvement]
type: LexicalEntry
type: MultiwordExpression
canonical form: [OAB] [Process Involvement]
sense: OAB -- PROCESS--INVOLVEMENT lexSense

OAB -- PROCESS--INVOLVEMENT lexConcept
type: LexicalConcept
definition: Capella Viewpoint. Purpose: For a process p, displays the activities it involves and the entities or actors they are allocated to. Rule0: There is one and only one [OAB][ProcessInvolvement] per process Rule1: At least each leaf activity/actor hosting the an activity of p shall be displayed on the diagram. Rule2: Structure Entities, defined as containing the activity or actors or rule 1, may be displayed (Author's decision). If so, the diagram shall remain clear even if exported on A4 protrait. Rule3: Contains at least 1 operational entity, at least 2 actitivies. Rule4: The diagram forbids entities or actors that do not allocate any activity of the process it describes Filter: TBD

[OAB] [Process Involvement]
type: Form

[OAB]
type: LexicalEntry
type: Word
canonical form: [OAB]
sense: OAB lexSense

OAB lexConcept
type: LexicalConcept
definition: placeholder

[OAB]
type: Form

[OAIB] [Operational Process]
type: LexicalEntry
type: MultiwordExpression
canonical form: [OAIB] [Operational Process]
sense: OAIB -- OPERATIONAL--PROCESS lexSense

OAIB -- OPERATIONAL--PROCESS lexConcept
type: LexicalConcept
definition: Capella Viewpoint. Purpose: displays the activities of a process. Rule: contains at least 2 operational activity Rule: each activity has an interaction with another activity Filter: TBD

[OAIB] [Operational Process]
type: Form

OB - On-board
type: LexicalEntry
type: MultiwordExpression
canonical form: OB - On-board
sense: OB-----ON-BOARD lexSense

OB-----ON-BOARD lexConcept
type: LexicalConcept
definition: OB - On-board

OB - On-board
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

objectives
type: LexicalEntry
type: Word
canonical form: objectives
sense: OBJECTIVES lexSense

OBJECTIVES lexConcept
type: LexicalConcept
definition: ARCADIA is a structured engineering method to identify and check the architecture of complex systems. It promotes collaborative work among all stakeholders during many of the engineering phases of the system. It allows iterations during the definition phase that help the architects to converge towards satisfaction of all identified needs. Even if textual requirements are kept as a support for part of customer need capture, ARCADIA favors functional analysis as the major way to formalize the need and solution behavior. This includes operational, functional and non-functional aspects, along with resulting definition of the architecture, based on – and justified against – this functional analysis. ARCADIA is based on the following general principles * All engineering stakeholders share the same language, method set of engineering artifacts and information, description of the need and the product itself as a shared model; * Each set of constraints (e.g. safety, performance, cost, mass, etc.) is formalized in a "viewpoint" against which each candidate architecture will be checked; * Architecture verification rules are established and the model is challenged against them, so as to check that architecture definition meets expectations, as early as possible in the process; * Co-engineering between the different levels of engineering is supported by the joint development of models. Models of various levels of the architecture and trade-offs are deduced, validated and/or connected with each other. The ARCADIA method is tooled through Capella, a modeling tool that meets full-scale deployment constraints in an operational context. Capella is available free of charge from the engineering community under open source.

objectives
type: Form

[OCB] [Involvement]
type: LexicalEntry
type: MultiwordExpression
canonical form: [OCB] [Involvement]
sense: OCB -- INVOLVEMENT lexSense

OCB -- INVOLVEMENT lexConcept
type: LexicalConcept
definition: Capella Viewpoint. Purpose: displays the operational entities and actors involved in an operational capability- and only that Rule: contains 1 and only 1 capability Rule: contains at least on 1 entity or actor Filter: show entities * Yes: Hide Communication Means * No: Hide Involvement Links * Yes: Hide Operational Capabiltiy Extends * Yes: Hide Operational Capabiltiy Includes * Yes: Hide Operational Capabiltiy Generatlizations * Yes: Hide Property Values * Yes: Hide Diagram Title Blocks * Yes: Hilde Element Title Blocks

[OCB] [Involvement]
type: Form

[OCB] [Structure]
type: LexicalEntry
type: MultiwordExpression
canonical form: [OCB] [Structure]
sense: OCB -- STRUCTURE lexSense

OCB -- STRUCTURE lexConcept
type: LexicalConcept
definition: Capella Viewpoint. Purpose: displays the hierachy of operational capabilities - and only that Rule: contains only capabilities and their relationships, no entities Rule: organised as a tree (folder like) Filter: * Yes: Hide Communication Means * Yes: Hide Involvement Links * TBD: Hide Operational Capabiltiy Extends * TBD: Hide Operational Capabiltiy Includes * TBD: Hide Operational Capabiltiy Generatlizations * Yes: Hide Property Values * Yes: Hide Diagram Title Blocks * Yes: Hilde Element Title Blocks

[OCB] [Structure]
type: Form

OCORA - Open CCS On-board Reference Architecture
type: LexicalEntry
type: MultiwordExpression
canonical form: OCORA - Open CCS On-board Reference Architecture
sense: OCORA-----OPEN--CCS--ON-BOARD--REFERENCE--ARCHITECTURE lexSense

OCORA-----OPEN--CCS--ON-BOARD--REFERENCE--ARCHITECTURE lexConcept
type: LexicalConcept
definition: OCORA - Open CCS On-board Reference Architecture

OCORA - Open CCS On-board Reference Architecture
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

[OES] [Operational Process] [scenario]
type: LexicalEntry
type: MultiwordExpression
canonical form: [OES] [Operational Process] [scenario]
sense: OES -- OPERATIONAL--PROCESS -- SCENARIO lexSense

OES -- OPERATIONAL--PROCESS -- SCENARIO lexConcept
type: LexicalConcept
definition: Capella Viewpoint. Purpose: Display the selected sequence of activities, interactions and related dependencies in a swimlane diagram Rule: Each activity is deployed to an entity or an actor. Rule: Each activity has at least one input and one output interaction. Filter: TBD selected path/sequence

[OES] [Operational Process] [scenario]
type: Form

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

OHT lexConcept
type: LexicalConcept
definition: Operational Harmonization Team

OHT
type: Form

OMS - On-board Monitoring System
type: LexicalEntry
type: MultiwordExpression
canonical form: OMS - On-board Monitoring System
sense: OMS-----ON-BOARD--MONITORING--SYSTEM lexSense

OMS-----ON-BOARD--MONITORING--SYSTEM lexConcept
type: LexicalConcept
definition: OMS - On-board Monitoring System

OMS - On-board Monitoring System
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

[OPD] [Operational Process] [logic]
type: LexicalEntry
type: MultiwordExpression
canonical form: [OPD] [Operational Process] [logic]
sense: OPD -- OPERATIONAL--PROCESS -- LOGIC lexSense

OPD -- OPERATIONAL--PROCESS -- LOGIC lexConcept
type: LexicalConcept
definition: Capella viewpoint Purpose: Show all activities of operational process with their data flow (interactions) and control flow. Rule: Each activity has at least one input and one output interaction. Filter: TBD

[OPD] [Operational Process] [logic]
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 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

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 one or more inputs, and one or more outputs. The activity describes what and how the operational entity the operational activity is allocated to is doing.

OPERATIONAL--ACTIVITY lexConcept 2
type: LexicalConcept
definition: A step or function of an operational process, done by actors that might need to use the system to reach certain objectives.

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 given by a group of processes.

OPERATIONAL--CAPABILITY lexConcept 2
type: LexicalConcept
definition: ability of an operational entity to provide a service

Operational capability
type: Form

Operational Concepts
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Concepts
sense: OPERATIONAL--CONCEPTS lexSense

OPERATIONAL--CONCEPTS lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

Operational Concepts
type: Form

Operational Costs
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Costs
sense: OPERATIONAL--COSTS lexSense

OPERATIONAL--COSTS lexConcept
type: LexicalConcept
definition: Costs for operating the railway system

Operational Costs
type: Form

Operational Design
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Design
sense: OPERATIONAL--DESIGN lexSense

OPERATIONAL--DESIGN lexConcept
type: LexicalConcept
definition: The operational Design, a synonym for operational analysis, includes the output workitems of all processes in the SEMP Process Group 02, which are for example operational... capabilities, processes, actor descriptions, requirements, hazards and risks. The operational design workitems are used for the System Pillar deliverable documents of the ORS (see SPPR-1848 )

Operational Design
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 lexConcept 2
type: LexicalConcept
definition: Denotes an entity of the real world (such as another system, device, group or organisation ...) involved in operational activities to which the system of interest or stakeholders must contribute. An actor is a type of operational entity (usually human and indivisible).{comment:1}

Operational Entity/Actor
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: A problematic situation that can occure with a process design.

Operational Hazard.
type: Form

Operational Interaction
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Interaction
sense: OPERATIONAL--INTERACTION lexSense

OPERATIONAL--INTERACTION lexConcept
type: LexicalConcept
definition: exchange between operational activities

Operational Interaction
type: Form

Operational Mission (deprecated)
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Mission (deprecated)
sense: OPERATIONAL--MISSION--DEPRECATED lexSense

OPERATIONAL--MISSION--DEPRECATED lexConcept
type: LexicalConcept
definition: A high-level operational objective. A drive or a goal that is assumed by a collection of operational entity, in order to {comment:2}reach specific objectives.

Operational Mission (deprecated)
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 Process
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Process
sense: OPERATIONAL--PROCESS lexSense

OPERATIONAL--PROCESS lexConcept
type: LexicalConcept
definition: An ordered (time or information) flow of operational activities.

OPERATIONAL--PROCESS lexConcept 2
type: LexicalConcept
definition: Specific organisation of activities and interactions, forming one path to fulfil an operational capability, within the set of all possible paths of operational data flows. It describes either an expected behaviour of one or several operational entities in a given context, or expresses non-functional properties on the path (such as latency, criticality, confidentiality, redundancy ...).

Operational Process
type: Form

Operational requirement
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational requirement
sense: OPERATIONAL--REQUIREMENT lexSense

OPERATIONAL--REQUIREMENT lexConcept
type: LexicalConcept
definition: A requirement issued in the context of the operational analysis process group. May qualify some operational actor, actor property, activity, scenario.

OPERATIONAL--REQUIREMENT lexConcept 2
type: LexicalConcept
definition: Something a process design has to fulfil.

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 Role
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Role
sense: OPERATIONAL--ROLE lexSense

OPERATIONAL--ROLE lexConcept
type: LexicalConcept
definition: Collection of consistent activities that can be realised by one of several operational entities/actors, and should be considered as a whole. It's a means of structuring those activities and sharing them between several operational entities/actors.

Operational Role
type: Form

Operational Scenario
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational Scenario
sense: OPERATIONAL--SCENARIO lexSense

OPERATIONAL--SCENARIO lexConcept
type: LexicalConcept
definition: dynamic and time-ordered interaction between operational elements: operational entities / actors or operational activities

Operational Scenario
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/System relationships
type: LexicalEntry
type: MultiwordExpression
canonical form: Operational/System relationships
sense: OPERATIONAL SYSTEM--RELATIONSHIPS lexSense

OPERATIONAL SYSTEM--RELATIONSHIPS lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

Operational/System relationships
type: Form

Operator Specific Add-On
type: LexicalEntry
type: MultiwordExpression
canonical form: Operator Specific Add-On
sense: OPERATOR--SPECIFIC--ADD-ON lexSense

OPERATOR--SPECIFIC--ADD-ON lexConcept
type: LexicalConcept
definition: ...

Operator Specific Add-On
type: Form

Operator
type: LexicalEntry
type: Word
canonical form: Operator
sense: OPERATOR lexSense

OPERATOR lexConcept
type: LexicalConcept
definition: An institution operating a system through its life-cycle, in context of the document usually an Infrastructure Manager or Train Operator.

Operator
type: Form

Opex
type: LexicalEntry
type: Word
canonical form: Opex
sense: OPEX lexSense

OPEX lexConcept
type: LexicalConcept
definition: Operational Expenditures

Opex
type: Form

OpsCON
type: LexicalEntry
type: Word
canonical form: OpsCON
sense: OPSCON lexSense

OPSCON lexConcept
type: LexicalConcept
definition: Operational concepts (How system should function)

OpsCON
type: Form

ORS Operational Requirement Specification
type: LexicalEntry
type: MultiwordExpression
canonical form: ORS Operational Requirement Specification
sense: ORS--OPERATIONAL--REQUIREMENT--SPECIFICATION lexSense

ORS--OPERATIONAL--REQUIREMENT--SPECIFICATION lexConcept
type: LexicalConcept
definition: The Operational Requirement Specification consists of a document bundle published by System Pillar's OA (SPPR-4033 ) as depicted in Diagram SPPR-3655 - Sub-processes of the operational analysis and their work-products. (TBD: detail while defining the documents created in Process SPPR-2240 - P2.5 Operational Design (System Level 2-3) )

ORS Operational Requirement Specification
type: Form

OSI layer
type: LexicalEntry
type: MultiwordExpression
canonical form: OSI layer
sense: OSI--LAYER lexSense

OSI--LAYER lexConcept
type: LexicalConcept
definition: Open System Interaction Model, aka OSI 7 System Layer model

OSI layer
type: Form

PCS Path Coordination System
type: LexicalEntry
type: MultiwordExpression
canonical form: PCS Path Coordination System
sense: PCS--PATH--COORDINATION--SYSTEM lexSense

PCS--PATH--COORDINATION--SYSTEM lexConcept
type: LexicalConcept
definition: PCS Path Coordination System

PCS Path Coordination System
type: Form

PER - Perception
type: LexicalEntry
type: MultiwordExpression
canonical form: PER - Perception
sense: PER-----PERCEPTION lexSense

PER-----PERCEPTION lexConcept
type: LexicalConcept
definition: PER - Perception

PER - Perception
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

Performance Requirements
type: LexicalEntry
type: MultiwordExpression
canonical form: Performance Requirements
sense: PERFORMANCE--REQUIREMENTS lexSense

PERFORMANCE--REQUIREMENTS lexConcept
type: LexicalConcept
definition: are associated with{comment:33} corresponding Functional Requirements and define how well a particular function has to perform – they are the constraints on that function.{comment:24}

Performance Requirements
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

Physical Architecture Concept
type: LexicalEntry
type: MultiwordExpression
canonical form: Physical Architecture Concept
sense: PHYSICAL--ARCHITECTURE--CONCEPT lexSense

PHYSICAL--ARCHITECTURE--CONCEPT lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

Physical Architecture Concept
type: Form

(physical) Behavioural Component
type: LexicalEntry
type: MultiwordExpression
canonical form: (physical) Behavioural Component
sense: PHYSICAL--BEHAVIOURAL--COMPONENT lexSense

PHYSICAL--BEHAVIOURAL--COMPONENT lexConcept
type: LexicalConcept
definition: constituent part of the system, responsible of performing a subset of functions allocated to the system, by interacting with other behavioural components and external actors

(physical) Behavioural Component
type: Form

(Physical) Behavioural Port
type: LexicalEntry
type: MultiwordExpression
canonical form: (Physical) Behavioural Port
sense: PHYSICAL--BEHAVIOURAL--PORT lexSense

PHYSICAL--BEHAVIOURAL--PORT lexConcept
type: LexicalConcept
definition: port of behavioural component

(Physical) Behavioural Port
type: Form

Physical Exchange
type: LexicalEntry
type: MultiwordExpression
canonical form: Physical Exchange
sense: PHYSICAL--EXCHANGE lexSense

PHYSICAL--EXCHANGE lexConcept
type: LexicalConcept
definition: an ordered collection of physical link transmitting behavioural exchanges

Physical Exchange
type: Form

(physical) Host component
type: LexicalEntry
type: MultiwordExpression
canonical form: (physical) Host component
sense: PHYSICAL--HOST--COMPONENT lexSense

PHYSICAL--HOST--COMPONENT lexConcept
type: LexicalConcept
definition: physical component, (ressource) hosting behavioural components

(physical) Host component
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

Physical Port
type: LexicalEntry
type: MultiwordExpression
canonical form: Physical Port
sense: PHYSICAL--PORT lexSense

PHYSICAL--PORT lexConcept
type: LexicalConcept
definition: connection point of one or more physical links allocated to a host component, by specifying how the component can be connected to the others or external actors

Physical Port
type: Form

Physical Scenario
type: LexicalEntry
type: MultiwordExpression
canonical form: Physical Scenario
sense: PHYSICAL--SCENARIO lexSense

PHYSICAL--SCENARIO lexConcept
type: LexicalConcept
definition: scenario between actors and physical behavioural component

Physical Scenario
type: Form

Physical / Building Strategy relationships
type: LexicalEntry
type: MultiwordExpression
canonical form: Physical / Building Strategy relationships
sense: PHYSICAL-- --BUILDING--STRATEGY--RELATIONSHIPS lexSense

PHYSICAL-- --BUILDING--STRATEGY--RELATIONSHIPS lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

Physical / Building Strategy relationships
type: Form

Plateau
type: LexicalEntry
type: Word
canonical form: Plateau
sense: PLATEAU lexSense

PLATEAU lexConcept
type: LexicalConcept
definition: A Plateau is a sector-wide aligned consistent and recommended requirement subset of the System Pillar Harmonized Operational Processes respectively the System Pillar Reference Architecture (SPRA) to be defined by the System Pillar domains and to be used for market tenders in a specific timeframe.

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

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

PMAT lexConcept
type: LexicalConcept
definition: PRAMSS Management & Assurance Team

PMAT
type: Form

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

PMO lexConcept
type: LexicalConcept
definition: Project Management Office

PMO
type: Form

PWITD
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Polarion Work Item of Type Definition
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
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

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

PRAMSS lexConcept
type: LexicalConcept
definition: Performance, reliability, availability, maintainability, safety and security

PRAMSS
type: Form

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

PRAMS lexConcept
type: LexicalConcept
definition: Performance, reliability, availability, maintainability, safety

PRAMS lexConcept 2
type: LexicalConcept
definition: Performance, Reliability, Availability, Maintainability, Safety

PRAMS
type: Form

Process Task
type: LexicalEntry
type: MultiwordExpression
canonical form: Process Task
sense: PROCESS--TASK lexSense

PROCESS--TASK lexConcept
type: LexicalConcept
definition: Action intended to contribute to the achievement of one or more outcomes of a process.

Process Task
type: Form

Process
type: LexicalEntry
type: Word
canonical form: Process
sense: PROCESS lexSense

PROCESS lexConcept
type: LexicalConcept
definition: A set of interrelated or interacting set of cohesive process tasks that transforms inputs into outputs. The Processes require a purpose and outcome, all processes have at least one process task. (Source: ISO9001 and ISO 15288, 4.1.30)

Process
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

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

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

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

RBC
type: Acronym
type: LexicalEntry
acronym for: Radio Block Centre
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
type: Form

RBC
type: Form

Railway Requirement.
type: LexicalEntry
type: MultiwordExpression
canonical form: Railway Requirement.
sense: RAILWAY--REQUIREMENT lexSense

RAILWAY--REQUIREMENT lexConcept
type: LexicalConcept
definition: Epic/User Story coming from stakeholders as their concrete vision. Who, what, why. Not strict form criteria. Formulated in 3-5 sentences. Is translated to precise operational requirements during the design process.

Railway Requirement.
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

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

RASCOP lexConcept
type: LexicalConcept
definition: Rail Standardisation Coordination Platform for Europe

RASCOP
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

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

RBC 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)

RBC
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

Reader Controller The Reader Controller manages states and failures of the Biome...
type: LexicalEntry
type: MultiwordExpression
canonical form: Reader Controller The Reader Controller manages states and failures of the Biome...
sense: READER--CONTROLLER--THE--READER--CONTROLLER--MANAGES--STATES--AND--FAILURES--OF--THE--BIOME lexSense

READER--CONTROLLER--THE--READER--CONTROLLER--MANAGES--STATES--AND--FAILURES--OF--THE--BIOME lexConcept
type: LexicalConcept
definition: Reader Controller The Reader Controller manages states and failures of the Biometric Readerand/or the RFID Reader.

Reader Controller The Reader Controller manages states and failures of the Biome...
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

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

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
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

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

Relocate rail applications
type: LexicalEntry
type: MultiwordExpression
canonical form: Relocate rail applications
sense: RELOCATE--RAIL--APPLICATIONS lexSense

RELOCATE--RAIL--APPLICATIONS lexConcept
type: LexicalConcept
definition: Stop and uninstall an application instance on one computing platform instance and deploy the same application to another computing platform instance. During the relocation process, all or certain functions of the application may be unavailable.

Relocate rail applications
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

Requirement statement
type: LexicalEntry
type: MultiwordExpression
canonical form: Requirement statement
sense: REQUIREMENT--STATEMENT lexSense

REQUIREMENT--STATEMENT lexConcept
type: LexicalConcept
definition: A requirement statement 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 quality within specified constraints with acceptable risk. Requirements are formal textual “shall” statements that communicate in a structured, natural language what an entity must do to realise the intent of the needs from which they were transformed. (Source: https://portal.incose.org/commerce/store?productId=INCOSE-GUIDEWRITINGREQ)

Requirement statement
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.

Reusability
type: Form

RFID Reader Radio Frequency Identification (RFID) refers to a wireless system co...
type: LexicalEntry
type: MultiwordExpression
canonical form: RFID Reader Radio Frequency Identification (RFID) refers to a wireless system co...
sense: RFID--READER--RADIO--FREQUENCY--IDENTIFICATION--RFID--REFERS--TO--A--WIRELESS--SYSTEM--CO lexSense

RFID--READER--RADIO--FREQUENCY--IDENTIFICATION--RFID--REFERS--TO--A--WIRELESS--SYSTEM--CO lexConcept
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 Radio Frequency Identification (RFID) refers to a wireless system co...
type: Form

RIM Railway Infrastructure Manager
type: LexicalEntry
type: MultiwordExpression
canonical form: RIM Railway Infrastructure Manager
sense: RIM--RAILWAY--INFRASTRUCTURE--MANAGER lexSense

RIM--RAILWAY--INFRASTRUCTURE--MANAGER lexConcept
type: LexicalConcept
definition: RIM Railway Infrastructure Manager

RIM Railway Infrastructure Manager
type: Form

RIS Railway Infrastructure System
type: LexicalEntry
type: MultiwordExpression
canonical form: RIS Railway Infrastructure System
sense: RIS--RAILWAY--INFRASTRUCTURE--SYSTEM lexSense

RIS--RAILWAY--INFRASTRUCTURE--SYSTEM lexConcept
type: LexicalConcept
definition: RIS Railway Infrastructure System

RIS Railway Infrastructure System
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 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.
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
type: LexicalEntry
type: Word
canonical form: RNE
sense: RNE lexSense

RNE lexConcept
type: LexicalConcept
definition: Rail Net Europe

RNE
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

ROC Railway Operating Company
type: LexicalEntry
type: MultiwordExpression
canonical form: ROC Railway Operating Company
sense: ROC--RAILWAY--OPERATING--COMPANY lexSense

ROC--RAILWAY--OPERATING--COMPANY lexConcept
type: LexicalConcept
definition: ROC Railway Operating Company

ROC Railway Operating Company
type: Form

Role.
type: LexicalEntry
type: Word
canonical form: Role.
sense: ROLE lexSense

ROLE lexConcept
type: LexicalConcept
definition: Role assigned to a actor

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

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

RTO lexConcept
type: LexicalConcept
definition: Remote Train Operations

RTO
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

(Running) Instance of an application
type: LexicalEntry
type: MultiwordExpression
canonical form: (Running) Instance of an application
sense: RUNNING--INSTANCE--OF--AN--APPLICATION lexSense

RUNNING--INSTANCE--OF--AN--APPLICATION lexConcept
type: LexicalConcept
definition: A single copy of an application running on a single computing platform instance. Running two copies of the software on the same computing platform instance, counts as two application instances.

(Running) Instance of an application
type: Form

RTE
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Runtime Environment
canonical form: RTE

RUNTIME--ENVIRONMENT lexConcept
type: LexicalConcept
definition: Refers to a software that acts as intermediary by providing a generalized abstraction of the underlying hardware and software and enabling communication and data management for distributed applications. It consists of the Runtime Layer and the Safety Layer.

Runtime Environment
type: Form

RTE
type: Form

Runtime Layer
type: LexicalEntry
type: MultiwordExpression
canonical form: Runtime Layer
sense: RUNTIME--LAYER lexSense

RUNTIME--LAYER lexConcept
type: LexicalConcept
definition: Refers to the system services (e.g., application and computing resource orchestration, monitoring of the Functional Applications and the platform itself, 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

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

RU lexConcept
type: LexicalConcept
definition: Railway Undertaking

RU
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

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

Safety Layer
type: LexicalEntry
type: MultiwordExpression
canonical form: Safety Layer
sense: SAFETY--LAYER lexSense

SAFETY--LAYER lexConcept
type: LexicalConcept
definition: Contains all functions related to fault tolerance (e.g., composite fail safety, voting mechanisms, redundancy mechanisms for availability) needed to enable that Functional Applications up to SIL4 can run on the Computing Environment.

Safety Layer
type: Form

Safety Platform Independence Interface (I5)
type: LexicalEntry
type: MultiwordExpression
canonical form: Safety Platform Independence Interface (I5)
sense: SAFETY--PLATFORM--INDEPENDENCE--INTERFACE--I5 lexSense

SAFETY--PLATFORM--INDEPENDENCE--INTERFACE--I5 lexConcept
type: LexicalConcept
definition: Interface I5 provides a safe (upto SIL4) platform independence API for functional applications.

Safety Platform Independence Interface (I5)
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

Scenario
type: LexicalEntry
type: Word
canonical form: Scenario
sense: SCENARIO lexSense

SCENARIO lexConcept
type: LexicalConcept
definition: dynamic interaction between elements like the system and the actors, components or between functions

Scenario
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

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

Sectional Runtime Calculation
type: LexicalEntry
type: MultiwordExpression
canonical form: Sectional Runtime Calculation
sense: SECTIONAL--RUNTIME--CALCULATION lexSense

SECTIONAL--RUNTIME--CALCULATION lexConcept
type: LexicalConcept
definition: Every train has a sectional minimal runtime depending on path, vehicle capabilities, rolling stock and driving strategy. Considering these inputs, a minimal runtime calculation for every single can carry out.

Sectional Runtime Calculation
type: Form

Secure Communication
type: LexicalEntry
type: MultiwordExpression
canonical form: Secure Communication
sense: SECURE--COMMUNICATION lexSense

SECURE--COMMUNICATION lexConcept
type: LexicalConcept
definition: efining an encrypted channel between two entities using TLS1.3

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 the rail automation system, which comprises system components, such as host devices, embedded devices, network devices or software applications, that implement security capabilities and consisting of a physical encasing, computing capabilities and network communication. Interfacing to SharedSecurity Services Examples of CCS secure components are object controller, trackside cabinet, IXL rack, ATO-OB, OBU, ATO-TS, IXL/RBC combination,…)

Secure Component
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: 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 Requirements Types
type: LexicalEntry
type: MultiwordExpression
canonical form: SEMP Requirements Types
sense: SEMP--REQUIREMENTS--TYPES lexSense

SEMP--REQUIREMENTS--TYPES lexConcept
type: LexicalConcept
definition: * Common Business Objectives (CBO): High level objectives defining the mandate of the System Pillar. They are derived by Tasks and domains. They are not created in the Tasks and Domains. They can be formulated freely;{comment:48} * Railway Requirements: are operational epics that formulate concrete visions and user stories 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 shall be specific enough to be assigned to exactly one System Pillar Task;{comment:49} * Operational Requirements: Are precise requirements that the Operational Analysis shall fulfil. {comment:24}They include PRAMSS and other non functional requirements; * Functional System Requirements: {comment:7}they are system requirements that the System Analysis, Logical Architecture or Subsystem Architecture shall fulfil and specify the functions of the System;{comment:14} * Non-Functional System Requirements: Are precise {comment:15}requirements that the System Analysis, Logical Architecture or Subsystem Architecture{comment:8} shall fulfil. They include PRAMSS and other non functional requirements.{comment:19} * Application Conditions + SRAC definitions: are precise requirements that the {comment:25}environment of the System In Use shall fulfill. They include physical needs, skill levels of maintenance personal, temperatures of server rooms, engineering rules, etc. The SRAC{comment:58} are specific application conditions relevant to safety.

SEMP Requirements Types
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

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

SEMP lexConcept
type: LexicalConcept
definition: System Engineering Management Plan

SEMP
type: Form

SERA-CCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: SERA-CCS
canonical form: SERA-CCS

SERA-CCS lexConcept
type: LexicalConcept
definition: SERA-CCS{comment:3} Single European Railway Area - Command Control and Signaling: 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 …

SERA-CCS
type: Form

SERA-CCS
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; [SOURCE: SPPRAMSS-337 - [Directive (EU) 2016/798] Article 3 Definitions (12) ]

serious accident
type: Form

Service unavailability
type: LexicalEntry
type: MultiwordExpression
canonical form: Service unavailability
sense: SERVICE--UNAVAILABILITY lexSense

SERVICE--UNAVAILABILITY lexConcept
type: LexicalConcept
definition: The unavailability of a service provided by a Functional Application, as seen by a user of this service (e.g., another Functional Application)

Service unavailability
type: Form

Shared Security Services
type: LexicalEntry
type: MultiwordExpression
canonical form: Shared Security Services
sense: SHARED--SECURITY--SERVICES lexSense

SHARED--SECURITY--SERVICES lexConcept
type: LexicalConcept
definition: A collection of standardized interfaces of central security functions accessible for all Secure Components. Examples of shared security services are TIME, IAM, PKI, LOG, SWU, BKP, INV, IDS and SIEM.

Shared Security Services
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

(SIL2) Hazard mitigation
type: LexicalEntry
type: MultiwordExpression
canonical form: (SIL2) Hazard mitigation
sense: SIL2--HAZARD--MITIGATION lexSense

SIL2--HAZARD--MITIGATION lexConcept
type: LexicalConcept
definition: Safety requirement regarding activities for lowering the effect of a hazard. It reduces the damage to people, property, and the environment by lowering the frequency, damping the consequences. Unlike a safety invariant, a mitigation may not be enforced in a predictable fashion, for instance because it addresses hazards that cannot be influenced by they system themselves. For instance, trespassers on the track cannot be influenced by the railway system. A mitigation can be a realized by * fault detection (hazard will be detected), typically this needs additional activities * failure reaction (after detection the hazard will be excluded), typically this needs additional activities * SRAC safety application condition (hazard will be avoided principly)

(SIL2) Hazard mitigation
type: Form

(SIL4) Safety Invariant
type: LexicalEntry
type: MultiwordExpression
canonical form: (SIL4) Safety Invariant
sense: SIL4--SAFETY--INVARIANT lexSense

SIL4--SAFETY--INVARIANT lexConcept
type: LexicalConcept
definition: Safety invariants are safety requirements typically designed to address SIL4 hazards. Safety invariants defining conditions or properties critical to avoid such a SIL4 hazrard. The safety invariant shall be maintained true at any time during operations so that the system does not enter into a hazardous state or condition. Safety invariants shall be constantly monitored and predictably enforced during operations. * Predictably enforced means that the system shall, by design, avoid to enter conditions deviating from the invariant. The acknowledge execution principle is normally applied (e.g., a train enters a switch only after the switch move to position is acknowledged as safey finished). As such, Invariants are often used in formal methods to validate the system design. They may also be input to fault tree analysis, or other safety assessment techniques to ensure the robustness and reliability of systems towards defects. * Continuously monitored means that the invariant fulfillment shall be measured continuously or frequently enough to detect deviations early enough to mitigate them effitciently. Deviations shall lead to a immediate corrective actions to prevent accidents or failures (safety reaction).

(SIL4) Safety Invariant
type: Form

Situation
type: LexicalEntry
type: Word
canonical form: Situation
sense: SITUATION lexSense

SITUATION lexConcept
type: LexicalConcept
definition: A logical combination of modes and states using logical operations (AND, OR, NOT) representing the superposition of modes and states occurring simultaneously at a given moment.

Situation
type: Form

Soft Key Context-dependent key which consists of a Hard Key with an associated l...
type: LexicalEntry
type: MultiwordExpression
canonical form: Soft Key Context-dependent key which consists of a Hard Key with an associated l...
sense: SOFT--KEY--CONTEXT-DEPENDENT--KEY--WHICH--CONSISTS--OF--A--HARD--KEY--WITH--AN--ASSOCIATED--L lexSense

SOFT--KEY--CONTEXT-DEPENDENT--KEY--WHICH--CONSISTS--OF--A--HARD--KEY--WITH--AN--ASSOCIATED--L lexConcept
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 Context-dependent key which consists of a Hard Key with an associated l...
type: Form

SW
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Software
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

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

SPC lexConcept
type: LexicalConcept
definition: System Pillar Coregroup

SPC
type: Form

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

SPDT lexConcept
type: LexicalConcept
definition: System Pillar Domain Team

SPDT
type: Form

Specification task
type: LexicalEntry
type: MultiwordExpression
canonical form: Specification task
sense: SPECIFICATION--TASK lexSense

SPECIFICATION--TASK lexConcept
type: LexicalConcept
definition: * Result: specification for an artifact * Usually ends on CENELEC P4 * Left side of the CENELEC “V”

Specification task
type: Form

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

SPSG lexConcept
type: LexicalConcept
definition: System Pillar Steering Group

SPSG
type: Form

SR Authorisation
type: LexicalEntry
type: MultiwordExpression
canonical form: SR Authorisation
sense: SR--AUTHORISATION lexSense

SR--AUTHORISATION lexConcept
type: LexicalConcept
definition: SR Authorisation

SR Authorisation
type: Form

SRAC.
type: LexicalEntry
type: Word
canonical form: SRAC.
sense: SRAC lexSense

SRAC lexConcept
type: LexicalConcept
definition: Safety related application condition.

SRAC lexConcept 2
type: LexicalConcept
definition: Safety related application conditions are SPPR-2246 - Application Condition relevant for the safety of the application.

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 lexConcept 2
type: LexicalConcept
definition: System Requirements Specification

SRS
type: Form

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

SSI lexConcept
type: LexicalConcept
definition: Standard Security Interface

SSI
type: Form

Stakeholder needs
type: LexicalEntry
type: MultiwordExpression
canonical form: Stakeholder needs
sense: STAKEHOLDER--NEEDS lexSense

STAKEHOLDER--NEEDS lexConcept
type: LexicalConcept
definition: These needs are taken into account for the definition of the System of interest. Note: In the Europe's Rail context, stakeholder needs are defined by valid input channels, which are - Decided SP Common Business Objectives as the top-level of the requirement tree, - Requirements proposed by any party and approved in the SP decision process according to SP governance.

Stakeholder needs
type: Form

Stakeholder
type: LexicalEntry
type: Word
canonical form: Stakeholder
sense: STAKEHOLDER lexSense

STAKEHOLDER lexConcept
type: LexicalConcept
definition: Someone who is entitled to express needs for the system of interest. Note: In the Europe's Rail context, the list of stakeholders is defined by the members of the System Pillar Steering group and their delegates or speakers.

STAKEHOLDER lexConcept 2
type: LexicalConcept
definition: Characterizes a stakeholder

Stakeholder
type: Form

Standard Interfaces
type: LexicalEntry
type: MultiwordExpression
canonical form: Standard Interfaces
sense: STANDARD--INTERFACES lexSense

STANDARD--INTERFACES lexConcept
type: LexicalConcept
definition: Add definition for standard interfaces

Standard Interfaces
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 processes that routinely occur in the day-to-day of an operational railway network, from which are not crated by the degradation of an equipment. Standard/routine operation apply to all operational categories - i.e. All GoA levels,

standard/routine operation
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 a boolean condition applied on certain model elements, such as functional exchanges.

State Transition
type: Form

State
type: LexicalEntry
type: Word
canonical form: State
sense: STATE lexSense

STATE lexConcept
type: LexicalConcept
definition: Behavioural characteristics of the system or physical conditions imposed by the environment. States can be applied to elements such as actors and components.

State
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

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 Process (Activity)
type: LexicalEntry
type: MultiwordExpression
canonical form: Sub Process (Activity)
sense: SUB--PROCESS--ACTIVITY lexSense

SUB--PROCESS--ACTIVITY lexConcept
type: LexicalConcept
definition: Set of cohesive tasks of a process

Sub Process (Activity)
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 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

Subsystem
type: LexicalEntry
type: Word
canonical form: Subsystem
sense: SUBSYSTEM lexSense

SUBSYSTEM lexConcept
type: LexicalConcept
definition: Subsystems are along ARCADIA 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. Some non-functional requirements (e.g. weight const…

Subsystem
type: Form

SuC
type: LexicalEntry
type: Word
canonical form: SuC
sense: SUC lexSense

SUC lexConcept
type: LexicalConcept
definition: System under Consideration [SOURCE: SPPRAMSS-4697 - [EN IEC 62443-3-2:2020]]

SuC
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

Switch Physical component which allows a selection of 2 to N states and keeps th...
type: LexicalEntry
type: MultiwordExpression
canonical form: Switch Physical component which allows a selection of 2 to N states and keeps th...
sense: SWITCH--PHYSICAL--COMPONENT--WHICH--ALLOWS--A--SELECTION--OF--2--TO--N--STATES--AND--KEEPS--TH lexSense

SWITCH--PHYSICAL--COMPONENT--WHICH--ALLOWS--A--SELECTION--OF--2--TO--N--STATES--AND--KEEPS--TH lexConcept
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 Physical component which allows a selection of 2 to N states and keeps th...
type: Form

sw
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Switch
canonical form: sw

SWITCH lexConcept
type: LexicalConcept
definition: Switch

SWITCH lexConcept 2
type: LexicalConcept
definition: a switch is a device that opens or closes electrical circuits.

SWITCH lexConcept 3
type: LexicalConcept
definition: a switch is a device that opens or closes electrical circuits.

SWITCH lexConcept 4
type: LexicalConcept
definition: Electrical switch. Closes or opens a circuit.

Switch
type: Form

sw
type: Form

(System) Actor
type: LexicalEntry
type: MultiwordExpression
canonical form: (System) Actor
sense: SYSTEM--ACTOR lexSense

SYSTEM--ACTOR lexConcept
type: LexicalConcept
definition: Actors are entities outside the system (either humans or other technical systems) that interact with the system.

SYSTEM--ACTOR lexConcept 2
type: LexicalConcept
definition: external entity (human, system, ...) interacting with the system of interest through its interfaces

(System) Actor
type: Form

System Analysis Concept
type: LexicalEntry
type: MultiwordExpression
canonical form: System Analysis Concept
sense: SYSTEM--ANALYSIS--CONCEPT lexSense

SYSTEM--ANALYSIS--CONCEPT lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

System Analysis Concept
type: Form

System and Innovation Programme Board
type: LexicalEntry
type: MultiwordExpression
canonical form: System and Innovation Programme Board
sense: SYSTEM--AND--INNOVATION--PROGRAMME--BOARD lexSense

SYSTEM--AND--INNOVATION--PROGRAMME--BOARD lexConcept
type: LexicalConcept
definition: System and Innovation Programme Board advises the Executive Director on project and programme management of the JU including interaction between the two pillars as well as change management and conflicts, supported by the System Pillar Core Group

System and Innovation Programme Board
type: Form

System Capability
type: LexicalEntry
type: MultiwordExpression
canonical form: System Capability
sense: SYSTEM--CAPABILITY lexSense

SYSTEM--CAPABILITY lexConcept
type: LexicalConcept
definition: A System capability is a service an actor requires from the system to fulfil its business goals. System capabilities are realised by exploiting one or multiple Functions, usually in a chain of functions. System capabilities in terms of this document are very similar to Use cases and the theory behind it.

SYSTEM--CAPABILITY lexConcept 2
type: LexicalConcept
definition: Ability of the system to provide a service that support the realisation of high-level operational objectives (including the contribution of the system to an operational capability).

System Capability
type: Form

SDLC
type: Acronym
type: LexicalEntry
acronym for: System Development Life Cycle
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

System Function
type: LexicalEntry
type: MultiwordExpression
canonical form: System Function
sense: SYSTEM--FUNCTION lexSense

SYSTEM--FUNCTION lexConcept
type: LexicalConcept
definition: A function derived during system analysis.

System Function
type: Form

System Levels
type: LexicalEntry
type: MultiwordExpression
canonical form: System Levels
sense: SYSTEM--LEVELS lexSense

SYSTEM--LEVELS lexConcept
type: LexicalConcept
definition: 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
type: Form

System mission (deprecated)
type: LexicalEntry
type: MultiwordExpression
canonical form: System mission (deprecated)
sense: SYSTEM--MISSION--DEPRECATED lexSense

SYSTEM--MISSION--DEPRECATED lexConcept
type: LexicalConcept
definition: high-level objective of the system

System mission (deprecated)
type: Form

System Of Systems
type: LexicalEntry
type: MultiwordExpression
canonical form: System Of Systems
sense: SYSTEM--OF--SYSTEMS lexSense

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.

System Of Systems
type: Form

System Pillar Core Group
type: LexicalEntry
type: MultiwordExpression
canonical form: System Pillar Core Group
sense: SYSTEM--PILLAR--CORE--GROUP lexSense

SYSTEM--PILLAR--CORE--GROUP lexConcept
type: LexicalConcept
definition: System Pillar Core Group Manages the common business objectives and deliverables from the Tasks

System Pillar Core Group
type: Form

System Pillar Deliverables (“output documents”)
type: LexicalEntry
type: MultiwordExpression
canonical form: System Pillar Deliverables (“output documents”)
sense: SYSTEM--PILLAR--DELIVERABLES-- OUTPUT--DOCUMENTS lexSense

SYSTEM--PILLAR--DELIVERABLES-- OUTPUT--DOCUMENTS lexConcept
type: LexicalConcept
definition: Deliverables are “output documents” that are automatically or manually created and exported from the engineering database (ALM) in the predefined structure of the SP deliverable templates List of deliverables per subsystem (System Level 5). ORS is done for System Level 3, and then tailored for the subsystems (especially CONEMP processes are done only on System Level 5). System specific Operational Requirement Specification (ORS) D2.1 As-Is analysis D2.2 Referred CBO and railway requirements D2.3 Problem analysis and derived process improvements D2.4 Application categories D2.5 Operational requirements (incl. non-functional and process requirements) D2.6 Operational entities and actor D2.7 Operational capabilities D2.8 PRAMSS targets, strategies and indicators D2.9 Operational processes D2.10 Operational hazards and risks D2.11 Rule books for all actors D2.12 The concept for the operational migrationFunctional Requirement Specification (FRS) D3.1 System definition D3.2 Detailed system actor descriptions and roles D3.3 System capabilities D3.4 Functional chains and sequences per capability D3.5 Function specification D3.6 Functional hazards and risksSystem requirement Specification (SRS) D4.1 Architecture of systems of the next level (if standardized) D4.2 Functional allocation to logical components D4.3 Physical architecture D4.4 Technical and physical hazards and risks D4.5 The technical migration strategy is defined D4.6 System requirements and interface specification, incl. legacy adpaters D4.7 Non-functional System requirementsApplication specification (ARS) D5.1 Release and Implementation Configurations D5.2 Application conditions, CSM/CST, HSI Plan D5.3 Application/life cycle/usage guideline/rules D5.4 Engineering and maintenance guideline/rules D5.5 Validation and test specificationValidation and test specification (VRS) D6.1 Model checking specification D6.2 Simulation/test environment specification D6.3 Simulation/test/validation cases and dataStandardisatio…

System Pillar Deliverables (“output documents”)
type: Form

System Pillar Steering Group
type: LexicalEntry
type: MultiwordExpression
canonical form: System Pillar Steering Group
sense: SYSTEM--PILLAR--STEERING--GROUP lexSense

SYSTEM--PILLAR--STEERING--GROUP lexConcept
type: LexicalConcept
definition: System Pillar Steering Group monitoring the progress of the System Pillar

System Pillar Steering Group
type: Form

System Pillar Unit Chairs the System Pillar Core Group
type: LexicalEntry
type: MultiwordExpression
canonical form: System Pillar Unit Chairs the System Pillar Core Group
sense: SYSTEM--PILLAR--UNIT--CHAIRS--THE--SYSTEM--PILLAR--CORE--GROUP lexSense

SYSTEM--PILLAR--UNIT--CHAIRS--THE--SYSTEM--PILLAR--CORE--GROUP lexConcept
type: LexicalConcept
definition: System Pillar Unit Chairs the System Pillar Core Group

System Pillar Unit Chairs the System Pillar Core Group
type: Form

System Requirements
type: LexicalEntry
type: MultiwordExpression
canonical form: System Requirements
sense: SYSTEM--REQUIREMENTS lexSense

SYSTEM--REQUIREMENTS lexConcept
type: LexicalConcept
definition: define the constraints that affect the whole or a significant proportion of the system and include: * Physical Attributes: * System Style * System Size * System Weight * The 'RAMI' properties: * System Reliability * System Availability * System Maintainability * System Interoperability

System Requirements
type: Form

System Requirement.
type: LexicalEntry
type: MultiwordExpression
canonical form: System Requirement.
sense: SYSTEM--REQUIREMENT lexSense

SYSTEM--REQUIREMENT lexConcept
type: LexicalConcept
definition: A System Requirement defines a capability of a linked system. It represents a task for designers an validators.

System Requirement.
type: Form

System/Logical Relationsships
type: LexicalEntry
type: MultiwordExpression
canonical form: System/Logical Relationsships
sense: SYSTEM LOGICAL--RELATIONSSHIPS lexSense

SYSTEM LOGICAL--RELATIONSSHIPS lexConcept
type: LexicalConcept
definition: (image: 1-screenshot-20230102-140337.png)

System/Logical Relationsships
type: Form

System
type: LexicalEntry
type: Word
canonical form: System
sense: SYSTEM lexSense

SYSTEM lexConcept
type: LexicalConcept
definition: According to ISO 15288 a system is “a combination of interacting elements organized 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 * at least one system capability that the system delivers as a service to the actors 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. Example: The system “onboard CCS” does not define the properties of this system itself, the properties emerge from the combined properties of the subsystems “ETCS core”, “Onboard localization” and “Onboard map” (examples only). 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 lexConcept 2
type: LexicalConcept
definition: Subject of interest of the engineering activities described by ARCADIA, which is also an organized collection of elements working as a whole.

System
type: Form

TAF/TAP TSI Technical Specification for Interoperability relating to Telematics...
type: LexicalEntry
type: MultiwordExpression
canonical form: TAF/TAP TSI Technical Specification for Interoperability relating to Telematics...
sense: TAF TAP--TSI--TECHNICAL--SPECIFICATION--FOR--INTEROPERABILITY--RELATING--TO--TELEMATICS lexSense

TAF TAP--TSI--TECHNICAL--SPECIFICATION--FOR--INTEROPERABILITY--RELATING--TO--TELEMATICS lexConcept
type: LexicalConcept
definition: TAF/TAP TSI Technical Specification for Interoperability relating to Telematics Applications for Freight/Passenger Services

TAF/TAP TSI Technical Specification for Interoperability relating to Telematics...
type: Form

TAF/TAP
type: LexicalEntry
type: Word
canonical form: TAF/TAP
sense: TAF TAP lexSense

TAF TAP lexConcept
type: LexicalConcept
definition: Telematics Applications for Freight/Passenger Services

TAF/TAP
type: Form

Tailoring of requirement breakdown
type: LexicalEntry
type: MultiwordExpression
canonical form: Tailoring of requirement breakdown
sense: TAILORING--OF--REQUIREMENT--BREAKDOWN lexSense

TAILORING--OF--REQUIREMENT--BREAKDOWN lexConcept
type: LexicalConcept
definition: SoS engineering can go wrong (quite often) if done in an overengineered and abstract way. If every artefact is created on every System Level (e.g. 5-7 levels and types or requirements that are broken down), the workload is artificially multiplied without need, and this policy is not creating a really good work split. To avoid this, every work process uses a tailoring approach which means * “Copy” (reference) things from a higher level, if possible like they are * Break up and translate through the levels that you really need, and not more. * Be sure that the right requirements are broken down to System Level 5 specification and to support concept definition in projects and manage the system, its performance and standards management. * Operational rulebooks include all that is needed. * Support design phases in managing requirement allocation, interfaces managements, testing planning. Engineering rules are complete and fulfilling the requirements * Support integration phase supporting data analysis, simulation process, anomaly resolution Programs can fail (cost, duration, time to market) because of too long and intense workout on System Level 1-4 (overengineered analytical architecting) without getting to real implementation specification and questions. If for example a high level requirement coming from the stakeholders can be addressed directly to System Level 5 without risk, this should be done. This is a (workflow) “tailoring” decision to be taken in the functional teams. Wrong approach: Breakdown every work item on every level. Right approaches: * Specific workflow tailoring, and * Generic workflow tailoring “Specific (workflow) tailoring” (intelligent work assignment per work item) = Single work items are only assigned on levels, where work is really needed (image: 1-image1.png) Second example for specific workflow tailoring: Two different process break downs * Op. process “Emergency stop of a train”, splits up “untailored” into work assignments… * System level…

Tailoring of requirement breakdown
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 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

Task.
type: LexicalEntry
type: Word
canonical form: Task.
sense: TASK lexSense

TASK lexConcept
type: LexicalConcept
definition: The planning hierarchy is Release>Project Milestone>Work Package>Task

Task.
type: Form

TCMS - Train Control & Management System
type: LexicalEntry
type: MultiwordExpression
canonical form: TCMS - Train Control & Management System
sense: TCMS-----TRAIN--CONTROL--AND--MANAGEMENT--SYSTEM lexSense

TCMS-----TRAIN--CONTROL--AND--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: TCMS - Train Control & Management System

TCMS - Train Control & Management System
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

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

TCR--TEMPORARY--CAPACITY--RESTRICTION lexConcept
type: LexicalConcept
definition: TCR Temporary Capacity Restriction

TCR Temporary Capacity Restriction
type: Form

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

TC lexConcept
type: LexicalConcept
definition: Technical Committee

TC
type: Form

TDS - Train Display System
type: LexicalEntry
type: MultiwordExpression
canonical form: TDS - Train Display System
sense: TDS-----TRAIN--DISPLAY--SYSTEM lexSense

TDS-----TRAIN--DISPLAY--SYSTEM lexConcept
type: LexicalConcept
definition: TDS - Train Display System

TDS - Train Display System
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

Temporary Shunting Area (TShA) A temporary shunting area is an interlocked area...
type: LexicalEntry
type: MultiwordExpression
canonical form: Temporary Shunting Area (TShA) A temporary shunting area is an interlocked area...
sense: TEMPORARY--SHUNTING--AREA--TSHA--A--TEMPORARY--SHUNTING--AREA--IS--AN--INTERLOCKED--AREA lexSense

TEMPORARY--SHUNTING--AREA--TSHA--A--TEMPORARY--SHUNTING--AREA--IS--AN--INTERLOCKED--AREA 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) A temporary shunting area is an interlocked area...
type: Form

TEN-T
type: LexicalEntry
type: Word
canonical form: TEN-T
sense: TEN-T lexSense

TEN-T lexConcept
type: LexicalConcept
definition: Trans-European Transport Network based on EU-Regulation No 1315/2013

TEN-T
type: Form

Term Status Description Operating state draft The operating state describes the...
type: LexicalEntry
type: MultiwordExpression
canonical form: Term Status Description Operating state draft The operating state describes the...
sense: TERM--STATUS--DESCRIPTION--OPERATING--STATE--DRAFT--THE--OPERATING--STATE--DESCRIBES--THE lexSense

TERM--STATUS--DESCRIPTION--OPERATING--STATE--DRAFT--THE--OPERATING--STATE--DESCRIBES--THE lexConcept
type: LexicalConcept
definition: Term | Status | Description Operating state | draft | The operating state describes the current state of production: * how trains move* where trains are* which route is set in control system* status of assetsThis information is based on inputs from control systems. Capacity | draft | 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 Restriction | draft | 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 Planning | draft | 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 Plan | draft | 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 Production | draft | 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. Conflict | draft | A conflict is any difference between the operational plan and the forecast, regardless of any actual need for intervention to resolve it. Dispatching | draft | Dispatching is the sum of actions intended to make modifications the operational plan. Deviation | draft | 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. Decision | dra…

Term Status Description Operating state draft The operating state describes the...
type: Form

Test Case.
type: LexicalEntry
type: MultiwordExpression
canonical form: Test Case.
sense: TEST--CASE lexSense

TEST--CASE lexConcept
type: LexicalConcept
definition: Defines a setup for a test run

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 not designed for testability will not 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.

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 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 "Trace" for a work item chain/tree/graph
type: LexicalEntry
type: MultiwordExpression
canonical form: The "Trace" for a work item chain/tree/graph
sense: THE-- TRACE --FOR--A--WORK--ITEM--CHAIN TREE GRAPH lexSense

THE-- TRACE --FOR--A--WORK--ITEM--CHAIN TREE GRAPH lexConcept
type: LexicalConcept
definition: * A Trace is a chain of all linked work items (a “directed graph” of nodes and links), that resolve all dependencies of a single work item * Example trace (in this case a “simple tree of nodes”, but can also be more complex): * A common business objective is solved by * a list of operational capabilities and requirements which are implemented in * a list of operational processes which need * a list of system capabilities and functions which are allocated in * logical components that are implemented in * physical subsystems which have * a list of precisely defined interfaces and * engineering rules.. * A trace is valid if all derivations are complete and correct. * A trace is complete if all dependencies are resolved by specified and verified work items (down to the implementation of detailed operational rulebooks and system handbooks, engineering rules and FFFiS interface specifications) * The overall specification is complete when all objectives, operational capabilities, and operational requirements are resolved by complete traces. * Example of the trace of one requirement (red node) down to functions, processes and components (other colours) (image: 1-Grafik_1780564629.png)

The "Trace" for a work item chain/tree/graph
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

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

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

TLS lexConcept
type: LexicalConcept
definition: Transport Layer Security (source: SPPRAMSS-1705 - [UNISIG Subset-146] )

TLS
type: Form

TMS Daily Topology
type: LexicalEntry
type: MultiwordExpression
canonical form: TMS Daily Topology
sense: TMS--DAILY--TOPOLOGY lexSense

TMS--DAILY--TOPOLOGY lexConcept
type: LexicalConcept
definition: Exact physical and topological description of the current state of railway infrastructure on a daily basis.

TMS Daily Topology
type: Form

TMS Traffic Management System
type: LexicalEntry
type: MultiwordExpression
canonical form: TMS Traffic Management System
sense: TMS--TRAFFIC--MANAGEMENT--SYSTEM lexSense

TMS--TRAFFIC--MANAGEMENT--SYSTEM lexConcept
type: LexicalConcept
definition: TMS Traffic Management System

TMS Traffic Management System
type: Form

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

TMS lexConcept
type: LexicalConcept
definition: Traffic Management System (double, needs to be deleted)

TMS lexConcept 2
type: LexicalConcept
definition: Traffic Management System

TMS
type: Form

to interface (verb)
type: LexicalEntry
type: MultiwordExpression
canonical form: to interface (verb)
sense: TO--INTERFACE--VERB lexSense

TO--INTERFACE--VERB lexConcept
type: LexicalConcept
definition: To exchange information with another peer using a mutually agreed structure and flow of communication.

to interface (verb)
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

Topology Master Data Validation & Import
type: LexicalEntry
type: MultiwordExpression
canonical form: Topology Master Data Validation & Import
sense: TOPOLOGY--MASTER--DATA--VALIDATION--AND--IMPORT lexSense

TOPOLOGY--MASTER--DATA--VALIDATION--AND--IMPORT lexConcept
type: LexicalConcept
definition: Checks Master Data/Topology according to safety rules. To ensure high quality Master Data the validation process checks the data against inconsistent and prove it on rightness.

Topology Master Data Validation & Import
type: Form

Touch Controller Controller which manages the states and failures of a Touch Pan...
type: LexicalEntry
type: MultiwordExpression
canonical form: Touch Controller Controller which manages the states and failures of a Touch Pan...
sense: TOUCH--CONTROLLER--CONTROLLER--WHICH--MANAGES--THE--STATES--AND--FAILURES--OF--A--TOUCH--PAN lexSense

TOUCH--CONTROLLER--CONTROLLER--WHICH--MANAGES--THE--STATES--AND--FAILURES--OF--A--TOUCH--PAN lexConcept
type: LexicalConcept
definition: Touch Controller Controller which manages the states and failures of a Touch Panel.

Touch Controller Controller which manages the states and failures of a Touch Pan...
type: Form

Track footprint
type: LexicalEntry
type: MultiwordExpression
canonical form: Track footprint
sense: TRACK--FOOTPRINT lexSense

TRACK--FOOTPRINT lexConcept
type: LexicalConcept
definition: The track Footprint of an object is defined for a specific track. It is the perpendicular projection of this object's ground footprint on the track center line. Notes: The definition corresponds to UNISIG's occupancy, without consideration fix-block / moving block. This definition is weak for intersections of two vehicles near points, where the width of vehicles has to be considered (e.g. with a fouling point indicator near the track) and for level crossings, because the road users are not associated with the rail track.

Track footprint
type: Form

TACS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Trackside Assets Control and Supervision
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

Trade-space factor
type: LexicalEntry
type: MultiwordExpression
canonical form: Trade-space factor
sense: TRADE-SPACE--FACTOR lexSense

TRADE-SPACE--FACTOR lexConcept
type: LexicalConcept
definition: "trade-space factors" represent the different factors/characteristics defining the solution space/alternatives. From this trade-off playspace containing set of good/acceptable solutions, we will need to identify the optimal one (i.e. "best" trade-off).

Trade-space factor
type: Form

TMS
type: Acronym
type: LexicalEntry
acronym for: Traffic Management System
canonical form: TMS

TRAFFIC--MANAGEMENT--SYSTEM lexConcept
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
type: Form

TMS
type: Form

Traffic Manager Operational Area of Control defines the region under the respons...
type: LexicalEntry
type: MultiwordExpression
canonical form: Traffic Manager Operational Area of Control defines the region under the respons...
sense: TRAFFIC--MANAGER--OPERATIONAL--AREA--OF--CONTROL--DEFINES--THE--REGION--UNDER--THE--RESPONS lexSense

TRAFFIC--MANAGER--OPERATIONAL--AREA--OF--CONTROL--DEFINES--THE--REGION--UNDER--THE--RESPONS lexConcept
type: LexicalConcept
definition: Traffic Manager Operational Area of Control defines the region under the responsability of only one Traffic Manager

Traffic Manager Operational Area of Control defines the region under the respons...
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 Display System Controller The TDS Controller interacts with system (CCS, T...
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Display System Controller The TDS Controller interacts with system (CCS, T...
sense: TRAIN--DISPLAY--SYSTEM--CONTROLLER--THE--TDS--CONTROLLER--INTERACTS--WITH--SYSTEM--CCS--T lexSense

TRAIN--DISPLAY--SYSTEM--CONTROLLER--THE--TDS--CONTROLLER--INTERACTS--WITH--SYSTEM--CCS--T lexConcept
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 The TDS Controller interacts with system (CCS, T...
type: Form

Train Display System (TDS) The Train Display System is the train cab display sys...
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Display System (TDS) The Train Display System is the train cab display sys...
sense: TRAIN--DISPLAY--SYSTEM--TDS--THE--TRAIN--DISPLAY--SYSTEM--IS--THE--TRAIN--CAB--DISPLAY--SYS lexSense

TRAIN--DISPLAY--SYSTEM--TDS--THE--TRAIN--DISPLAY--SYSTEM--IS--THE--TRAIN--CAB--DISPLAY--SYS 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) The Train Display System is the train cab display sys...
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 Running Number
type: LexicalEntry
type: MultiwordExpression
canonical form: Train Running Number
sense: TRAIN--RUNNING--NUMBER lexSense

TRAIN--RUNNING--NUMBER lexConcept
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

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” something
type: LexicalEntry
type: MultiwordExpression
canonical form: “Train” something
sense: TRAIN --SOMETHING lexSense

TRAIN --SOMETHING lexConcept
type: LexicalConcept
definition: Create Training material, provide training, support trained people

“Train” something
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

TCCS
type: AbbreviatedForm
type: LexicalEntry
abbreviation for: Transversal CCS domain
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

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 lexConcept 2
type: LexicalConcept
definition: Technical Specifications for Interoperability

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

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

TWG lexConcept
type: LexicalConcept
definition: Topical Working Group

TWG
type: Form

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

UIC lexConcept
type: LexicalConcept
definition: International union of railways

UIC
type: Form

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

UIP lexConcept
type: LexicalConcept
definition: International Union of Wagon Keepers

UIP
type: Form

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

UITP lexConcept
type: LexicalConcept
definition: The International Association of Public Transport

UITP
type: Form

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

UNIFE lexConcept
type: LexicalConcept
definition: Union des Industries Ferroviaires Européennes

UNIFE
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

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

UNISIG lexConcept
type: LexicalConcept
definition: Union Industry of Signalling

UNISIG
type: Form

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

UNITEL lexConcept
type: LexicalConcept
definition: Union Industry of Telecommunications

UNITEL
type: Form

Updateability
type: LexicalEntry
type: Word
canonical form: Updateability
sense: UPDATEABILITY lexSense

UPDATEABILITY lexConcept
type: LexicalConcept
definition: Updateability refers to the ability of a system to receive and incorporate updates or patches, e.g. to address security vulnerabilities. Updates are often provided to improve the performance of the system, stability, or security without introducing significant changes to its functionality.

Updateability
type: Form

Upgradeability
type: LexicalEntry
type: Word
canonical form: Upgradeability
sense: UPGRADEABILITY lexSense

UPGRADEABILITY lexConcept
type: LexicalConcept
definition: Upgradeability refers to the ability of a system to undergo significant enhancements or improvements in terms of its features, functionality, or performance. Upgrades typically involve the installation of a newer version or release of the system that offers new capabilities or improved performance compared to the previous version.

Upgradeability
type: Form

Uplinking
type: LexicalEntry
type: Word
canonical form: Uplinking
sense: UPLINKING lexSense

UPLINKING lexConcept
type: LexicalConcept
definition: To handle deviated new designs or new/changed external inputs the whole “engineering” has to be understood as * Work items with type, versions, and state * Their links with versions, link roles and state The engineering database is in the end a “directed graph” with “nodes” (work items) and links (graph just indicated in the picture):{comment:13} (image: 3-image3.png) The basic principle for continuous integration using an ALM+MBSE system is based on the mathematical process of “adding a directed graph to another directed graph which can overlap in certain nodes”. This is called “Uplinking” in the System Pillar. Existing graph (e.g. ALM master database) New graph fragment (external contribution) (image: 1-screenshot-20221229-210015.png) “Merging these graphs” ="uplinking" (of conceptual, requirement and modelling work items) is the most feared job to do in system engineering when done manually. A strong system support is necessary. This merge can happen when * A daughter-system graph is “uplinked” to the mother-system (master) graph * An external contribution is integrated (perhaps again and again) * An external editor was used to edit elements in the mater database (e.g. ALM= master database, MBSE-Tool = editor for a part of the work items) * A bottom-up process is faster (domain team) then the top-down process (Level 3) * The architecture teams is faster concerning functional design then the operational design team with the process design. Or both are fast then the requirement feedback from the migration team is coming. * Etc. A lot of isolated (time, team, engineering tool) asynchronous designs will occur in the System Pillar. They lead to these synchronization needs: (image: 2-screenshot-20221229-210015.png) This does not mean, that “synchronization” is the standard choice to integrate work. The preferred choice is top-down design and working in the same system whenever possible. But synchronization will anyway be needed very often. The sync process of these int…

Uplinking
type: Form

UI
type: Acronym
type: LexicalEntry
acronym for: User Interface
canonical form: UI

USER--INTERFACE lexConcept
type: LexicalConcept
definition: User Interface refers to a hardware or software device that allows a user to interact with a computer product. The interaction is into the graphical environment in which the user of an application, software or website navigates.

User Interface
type: Form

UI
type: Form

Validator Finding.
type: LexicalEntry
type: MultiwordExpression
canonical form: Validator Finding.
sense: VALIDATOR--FINDING lexSense

VALIDATOR--FINDING lexConcept
type: LexicalConcept
definition: Result of a validation

Validator Finding.
type: Form

Variant
type: LexicalEntry
type: Word
canonical form: Variant
sense: VARIANT lexSense

VARIANT lexConcept
type: LexicalConcept
definition: A Variant is a subset of features

Variant
type: Form

Vertical integration
type: LexicalEntry
type: MultiwordExpression
canonical form: Vertical integration
sense: VERTICAL--INTEGRATION lexSense

VERTICAL--INTEGRATION lexConcept
type: LexicalConcept
definition: Integration of an Functional Application with the IT platform, or a middleware with a hardware.

Vertical integration
type: Form

View Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can r...
type: LexicalEntry
type: MultiwordExpression
canonical form: View Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can r...
sense: VIEW--AGGREGATION--OF--AREAS--REQUIRED--FOR--SYSTEMS--CCS--TCMS--CVR------A--VIEW--CAN--R lexSense

VIEW--AGGREGATION--OF--AREAS--REQUIRED--FOR--SYSTEMS--CCS--TCMS--CVR------A--VIEW--CAN--R lexConcept
type: LexicalConcept
definition: View Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can represent Areas of different systems at the same time.

View Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can r...
type: Form

View Controller The View Controller aggregates the View, the output devices and...
type: LexicalEntry
type: MultiwordExpression
canonical form: View Controller The View Controller aggregates the View, the output devices and...
sense: VIEW--CONTROLLER--THE--VIEW--CONTROLLER--AGGREGATES--THE--VIEW--THE--OUTPUT--DEVICES--AND lexSense

VIEW--CONTROLLER--THE--VIEW--CONTROLLER--AGGREGATES--THE--VIEW--THE--OUTPUT--DEVICES--AND lexConcept
type: LexicalConcept
definition: View Controller The View Controller aggregates the View, the output devices and the controller of each input device.

View Controller The View Controller aggregates the View, the output devices and...
type: Form

View
type: LexicalEntry
type: Word
canonical form: View
sense: VIEW lexSense

VIEW lexConcept
type: LexicalConcept
definition: A view is a filter that restricts the set of data types to a subset that is of interest in the context of a use case. Filtering is by discipline and spatially.

View
type: Form

Virtual Block
type: LexicalEntry
type: MultiwordExpression
canonical form: Virtual Block
sense: VIRTUAL--BLOCK lexSense

VIRTUAL--BLOCK lexConcept
type: LexicalConcept
definition: ...

Virtual Block
type: Form

Virtualisation Interface (I3)
type: LexicalEntry
type: MultiwordExpression
canonical form: Virtualisation Interface (I3)
sense: VIRTUALISATION--INTERFACE--I3 lexSense

VIRTUALISATION--INTERFACE--I3 lexConcept
type: LexicalConcept
definition: Interface I3 provides the API to virtualized hardware through functions such as virtualisation, separation and "containerisation"

Virtualisation Interface (I3)
type: Form

Virtualisation Layer
type: LexicalEntry
type: MultiwordExpression
canonical form: Virtualisation Layer
sense: VIRTUALISATION--LAYER lexSense

VIRTUALISATION--LAYER lexConcept
type: LexicalConcept
definition: Contains mechanisms like a hypervisor to allow different systems with a safety and runtime layer to run concurrently on the same pool of Hardware underneath.

Virtualisation Layer
type: Form

VLAN - Virtual Local Area Network
type: LexicalEntry
type: MultiwordExpression
canonical form: VLAN - Virtual Local Area Network
sense: VLAN-----VIRTUAL--LOCAL--AREA--NETWORK lexSense

VLAN-----VIRTUAL--LOCAL--AREA--NETWORK lexConcept
type: LexicalConcept
definition: VLAN - Virtual Local Area Network

VLAN - Virtual Local Area Network
type: Form

White Box View
type: LexicalEntry
type: MultiwordExpression
canonical form: White Box View
sense: WHITE--BOX--VIEW lexSense

WHITE--BOX--VIEW lexConcept
type: LexicalConcept
definition: The white box view reveals structural decomposition of a system. In case of the terminology of this document, it can be differentiated between systems that are refined into a system of systems or into subsystems.

White Box View
type: Form

Wider System of Interest
type: LexicalEntry
type: MultiwordExpression
canonical form: Wider System of Interest
sense: WIDER--SYSTEM--OF--INTEREST lexSense

WIDER--SYSTEM--OF--INTEREST lexConcept
type: LexicalConcept
definition: The set of all operational entities defining then scope of the operational analysis.

Wider System of Interest
type: Form

Wireless Component
type: LexicalEntry
type: MultiwordExpression
canonical form: Wireless Component
sense: WIRELESS--COMPONENT lexSense

WIRELESS--COMPONENT lexConcept
type: LexicalConcept
definition: A Secure Component with a wireless communication interface. Examples of Wireless Components are handheld devices, WLAN access points and WLAN/5G routers and modems.

Wireless Component
type: Form

Work Item Comment
type: LexicalEntry
type: MultiwordExpression
canonical form: Work Item Comment
sense: WORK--ITEM--COMMENT lexSense

WORK--ITEM--COMMENT lexConcept
type: LexicalConcept
definition: Work Item Comment

Work Item Comment
type: Form

Work item editor
type: LexicalEntry
type: MultiwordExpression
canonical form: Work item editor
sense: WORK--ITEM--EDITOR lexSense

WORK--ITEM--EDITOR lexConcept
type: LexicalConcept
definition: * The basic system and workflow management tool is the ALM system (currently Polarion). * The ALM offers different frontend types to create/edit/change work items (document editors, database frontends, graphical design, etc.) * Additional editors (like graphical modelling tools for ARCADIA and SysML) can be used to edit elements of the engineering database in the ALM System (synchronized data) as far as a synchronisation software is available (see chapter data management)

Work item editor
type: Form

Work Item
type: LexicalEntry
type: MultiwordExpression
canonical form: Work Item
sense: WORK--ITEM lexSense

WORK--ITEM lexConcept
type: LexicalConcept
definition: Work Item{comment:1}{comment:2}

WORK--ITEM lexConcept 2
type: LexicalConcept
definition: * ork items examples: “A requirement”, or “a function”, or “a concept aspect” * Work items are objects in the “engineering database” (ALM) that represent the result of a design step. * The structure of the work items is defined by the SEMP process definition documents (overview in the maps), that also make use of modelling standards like ARCADIA or SysML * The master-engineering database is the ALM System (currently Polarion) which contains all work items and their links.

Work Item
type: Form

Work Package.
type: LexicalEntry
type: MultiwordExpression
canonical form: Work Package.
sense: WORK--PACKAGE lexSense

WORK--PACKAGE lexConcept
type: LexicalConcept
definition: The planning hierarchy is Release>Project Milestone>Work Package>Task

Work Package.
type: Form

Work Product
type: LexicalEntry
type: MultiwordExpression
canonical form: Work Product
sense: WORK--PRODUCT lexSense

WORK--PRODUCT lexConcept
type: LexicalConcept
definition: An artefact associated with the execution of a process. (Source: ISO 24765:2017 3.4611)

Work Product
type: Form

Workflow and workflow rules
type: LexicalEntry
type: MultiwordExpression
canonical form: Workflow and workflow rules
sense: WORKFLOW--AND--WORKFLOW--RULES lexSense

WORKFLOW--AND--WORKFLOW--RULES lexConcept
type: LexicalConcept
definition: * A workflow describes the rules (processes) how a “trace” shall be created step by step. * A workflow includes a set of rules that define, how * work items must be broken down and linked (link rules) * work item types must be resolved * certain work item types are assigned to certain teams in the organisation * Every work item, that is not compliant to a workflow is marked as invalid * There are optional workflow steps in a workflow. E.g. a requirement can be directly resolved by multiple functions (that are always explained with a rational attribute) without having a “solution concept” work item, which is optional.

Workflow and workflow rules
type: Form

Workflow Prioritisation strategy to be decided per area
type: LexicalEntry
type: MultiwordExpression
canonical form: Workflow Prioritisation strategy to be decided per area
sense: WORKFLOW--PRIORITISATION--STRATEGY--TO--BE--DECIDED--PER--AREA lexSense

WORKFLOW--PRIORITISATION--STRATEGY--TO--BE--DECIDED--PER--AREA lexConcept
type: LexicalConcept
definition: In general, there are two directions for prioritisation, which are “horizontal” or “vertical” * Horizontal prioritisation means for example “which of all operational capabilities do we break down first down to their operational processes (just the next derivation step per capability)” * Vertical prioritisation means for example “which operational capability do we resolve down to the physical architecture before we start to resolve the next * capability” (image: 1-Grafik_1.png) * Both prioritisation methods are mixed to reach two targets in parallel: a) Use the capacity of all teams in parallel with different roles (vertical prioritisation), b) get a more and more full picture top-down (horizontal prioritisation). * A “mix” can for example be: “At first only all operational capabilities for standard train movements (no shunting etc.) and only the processes related to ETCS Level R without ATO are traced down to the physical architecture in the first step”. For the prioritisation these aspects are important: * As much as possible early usable results shall be created (year by year). * Example 1 (“bottom-up”): All traces, that lead to the EULYNX interfaces shall be resolved and approved fast. EULYNX interfaces should be standardized soon. * This means to import and resolve all traces, and to connect all interfaces to the overall architecture “upwards” (connecting workflow) * Example 2 (“top-down”): All traces for DAC shall be resolved fast, but there are not so much complete (resolved) traces to import in terms of processes and architecture. All operational capabilities and operational requirements for DAC need to be created and broken down and resolved down to the implementation (=vertical prioritisation). * Important decisions shall be decided early as a basis for all work * Example 3: (“horizontal prioritisation”): The process standardisation scope and depth shall be decided as early as possible. This means to create all operational capabilities, derive them town to …

Workflow Prioritisation strategy to be decided per area
type: Form

Workflow step (on step in a workitem trace)
type: LexicalEntry
type: MultiwordExpression
canonical form: Workflow step (on step in a workitem trace)
sense: WORKFLOW--STEP--ON--STEP--IN--A--WORKITEM--TRACE lexSense

WORKFLOW--STEP--ON--STEP--IN--A--WORKITEM--TRACE lexConcept
type: LexicalConcept
definition: A workflow step includes some of the following actions * “Create a trace”: The work item on the “top/start” of a trace is created based on external decisions. These are typically * Steering group decisions about system capabilities, common business objectives, improvement targets or problem descriptions, operational requirements, new safety requirements, etc. (see chapter below). * Technical regulations * “Derive” a work item: A team that is responsible for a derivation step in a trace for work items of a specific type looks for all unresolved work items and derives the resolving work items that are part of the own team scope. E.g., an ARC team sees unresolved actions in an operational process an derives all needed system requirements and functions that need to be worked out. * “Propose” a work item: A team or person receives (assignment) a work item with the status “proposed” from another team, that wants to resolve a dependency. E.g., an OD team designed an action in an operational process and “proposes” (“push”) a system requirement to an ARC team. * “Design / engineer / work out” a work item: The content of the work item is worked out. (e.g. an operational process with all actions) * “Break down” (“dependencies defined/delegated”) a work item: All necessary next work items are derived (as proposals) and linked. * “Resolve” a work item: All necessary next/downwards work items are derived, linked, designed, approved and resolved. E.g., all system functions to fulfil (resolve) an operational requirement are completed. * “Assign” a work item: The work item is assigned to a team or person that shall design it. * “Uplink” a work item. A “free floating” (not linked top-down, completely unlinked, or currently invalid) work item (e.g. coming from a bottom-up process or external contributor) is linked “upwards” to a “traced/valid” work item as if it had been derived from it before (e.g. a process is linked ex post to a capability). This is only done if this new link is re…

Workflow step (on step in a workitem trace)
type: Form

Workstep "workitem check"
type: LexicalEntry
type: MultiwordExpression
canonical form: Workstep "workitem check"
sense: WORKSTEP-- WORKITEM--CHECK lexSense

WORKSTEP-- WORKITEM--CHECK lexConcept
type: LexicalConcept
definition: * Is the workitem content correct and without inner contradictions? * Does the workitem content fit to the wokitem type? * Are all standard or custom workitem fields filled? * Does the workitem content implement the demands coming to it by existing links? * Do all mandatory links exist and are they completely fulfilling their role? Does the content fit to them? E.g. a system requirements can be implemented by a function... but it needs to be completely implemented and not partly.

Workstep "workitem check"
type: Form

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

Building block
type: LexicalEntry
type: MultiwordExpression
canonical form: Building block
sense: BUILDING--BLOCK lexSense

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

Control, Command and Signalling
type: LexicalEntry
type: MultiwordExpression
canonical form: Control, Command and Signalling
sense: CONTROL--COMMAND--AND--SIGNALLING lexSense

End of Life
type: LexicalEntry
type: MultiwordExpression
canonical form: End of Life
sense: END--OF--LIFE lexSense

End of Support
type: LexicalEntry
type: MultiwordExpression
canonical form: End of Support
sense: END--OF--SUPPORT lexSense

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

European Railway Traffic Management System
type: LexicalEntry
type: MultiwordExpression
canonical form: European Railway Traffic Management System
sense: EUROPEAN--RAILWAY--TRAFFIC--MANAGEMENT--SYSTEM lexSense

Europe’s Rail Joint Undertaking
type: LexicalEntry
type: MultiwordExpression
canonical form: Europe’s Rail Joint Undertaking
sense: EUROPE S--RAIL--JOINT--UNDERTAKING lexSense

Europe's Rail
type: LexicalEntry
type: MultiwordExpression
canonical form: Europe's Rail
sense: EUROPE S--RAIL lexSense

Functional System
type: LexicalEntry
type: MultiwordExpression
canonical form: Functional System
sense: FUNCTIONAL--SYSTEM lexSense

Hardware
type: LexicalEntry
type: Word
canonical form: Hardware
sense: HARDWARE lexSense

Human Machine Interface
type: LexicalEntry
type: MultiwordExpression
canonical form: Human Machine Interface
sense: HUMAN--MACHINE--INTERFACE lexSense

Infrastructure Manager
type: LexicalEntry
type: MultiwordExpression
canonical form: Infrastructure Manager
sense: INFRASTRUCTURE--MANAGER lexSense

Interlocking
type: LexicalEntry
type: Word
canonical form: Interlocking
sense: INTERLOCKING lexSense

Maintenance Operator
type: LexicalEntry
type: MultiwordExpression
canonical form: Maintenance Operator
sense: MAINTENANCE--OPERATOR lexSense

National Implemenation Plan
type: LexicalEntry
type: MultiwordExpression
canonical form: National Implemenation Plan
sense: NATIONAL--IMPLEMENATION--PLAN lexSense

Polarion Work Item of Type Definition
type: LexicalEntry
type: MultiwordExpression
canonical form: Polarion Work Item of Type Definition
sense: POLARION--WORK--ITEM--OF--TYPE--DEFINITION lexSense

Polarion Work Item of Type Reference
type: LexicalEntry
type: MultiwordExpression
canonical form: Polarion Work Item of Type Reference
sense: POLARION--WORK--ITEM--OF--TYPE--REFERENCE lexSense

Radio Block Centre
type: LexicalEntry
type: MultiwordExpression
canonical form: Radio Block Centre
sense: RADIO--BLOCK--CENTRE lexSense

Reliability, Availability, Maintainability and Safety
type: LexicalEntry
type: MultiwordExpression
canonical form: Reliability, Availability, Maintainability and Safety
sense: RELIABILITY--AVAILABILITY--MAINTAINABILITY--AND--SAFETY lexSense

Runtime Environment
type: LexicalEntry
type: MultiwordExpression
canonical form: Runtime Environment
sense: RUNTIME--ENVIRONMENT lexSense

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

Software
type: LexicalEntry
type: Word
canonical form: Software
sense: SOFTWARE lexSense

Switch
type: LexicalEntry
type: Word
canonical form: Switch
sense: SWITCH lexSense

System Development Life Cycle
type: LexicalEntry
type: MultiwordExpression
canonical form: System Development Life Cycle
sense: SYSTEM--DEVELOPMENT--LIFE--CYCLE lexSense

Trackside Assets Control and Supervision
type: LexicalEntry
type: MultiwordExpression
canonical form: Trackside Assets Control and Supervision
sense: TRACKSIDE--ASSETS--CONTROL--AND--SUPERVISION lexSense

Traffic Management System
type: LexicalEntry
type: MultiwordExpression
canonical form: Traffic Management System
sense: TRAFFIC--MANAGEMENT--SYSTEM lexSense

Transversal CCS domain
type: LexicalEntry
type: MultiwordExpression
canonical form: Transversal CCS domain
sense: TRANSVERSAL--CCS--DOMAIN lexSense

User Interface
type: LexicalEntry
type: MultiwordExpression
canonical form: User Interface
sense: USER--INTERFACE lexSense

Polarion Workitem
type: LexicalConcept
subclass of: ContextConcept

ARCADIA Method
type: LexicalConcept
subclass of: ContextConcept

Railway Infrastructure
type: LexicalConcept
subclass of: ContextConcept