This is an example lexicon
Ceci est un exemple de lexique
accident
‘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) ]
actor variant
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.
Adaptability
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.
ADCARP something
Add, Change, Delete, Approve, Release, Decide and Publish
ADM - Automatic Driving Module
(AFARP) - As far as reasonably practicable
"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.
Allocation Body
Analysis
Qualitative assessment of requirements, issues, etc.
Answer.
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"
ASFA
Anuncio de Señales y Frenado Automático (ASFA; "Announcement of Signals and Automatic Braking"); Is an Automatic Protetion System which is widely used on the Spanish rail network. It consists of a mechanism that stops a train if the driver does not properly heed signals.
Anuncio de Señales y Frenado Automático
APM - Automatic Processing Module
Appliation (along EN 50126)
Describes the sum of: The system, its needed environment and its form of usage (other systems, processes), and the system life-cycle.
Application Condition.
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").
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 Configuration.
Set of combined Features (which are child workitems).
Application Guideline
Defining procedural requirements for Railway Operators
Application Layer
contains functional applications.
ALM
Application Lifecycle Management
Application
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.
Architectural Concept
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 which steps the inputs to a system function are converted to the outputs. This step does not yet define an architecture and does not refer to technical solution concepts like ETCS or ATO. As the system under consideration is still a blackbox, the logical architecture still leaves the question open, what subsystem structure is the to be used (e.g. very modular subsystems vs. bigger subsystems or combined HW/SW subsystems vs. SW-modules on a common platform). This step is performed once, before the subsystem architecture shall be derived. * Subsystem architecture (SSA): design the final set of tenderable subsystems and integrate all necessary non-functional requirements. This step integrates all considerations on the intended structure of subsystems and interfaces (down to FFFIS) as well as all open technical aspects into a consistent architectural definition.{comment:3}
ARCT
Architecture and Release Coordination Team
AWC
Architecture Working Circle
Area Controller The Area Controller manages areas for the View.
Area of Use
AFARP
Denote that an action shall be done until the cost to do so does not justify the benefit of doing it.
As far as reasonably practicable
ASO
Automatic Shunting Operation
Assessment.
Quantitative assessment of requirements, issues, etc.
ATO - Automatic Train Operation
ATO Automatic Train Operation CCS Control Command and Signaling CI/CD Continuous...
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
Authentication
The process to verify the identity of communicating peers. (source: SPPRAMSS-1705 - [UNISIG Subset-146] )
Authorisation, Re-authorisation, Safety acceptance
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
Automatic Conflict Solution
Solves conflicts based on algorithms. May use optimisation functions.
ATO
Automatic Train Operation
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
availability, <of a product>
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]
Backwards Compatibility
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.
Basic Integrity Platform Independence Interface (I4)
Interface I4 provides a platform independence API for functional applications in the non-safety area.
Behavioural Component Exchange
exchange between behavioural components
Behavioural exchange
implemented as component exchange: interaction between two behavioural physical components or logical components, through their behavioural ports
Behavioural Port
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).
Biometric Reader Device that reads the identity of a person by comparing some at...
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.
Black Box View
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.
Building Block Configuration Manifest
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
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.
{comment:33} A building block is a sourceable unit of the CCS system (hardware and/or software), having standardised functionality, standardised performance (RAM), standardised safety (including Tolerable Functional Failure Rate [TFFR], Safety Integrity Level [SIL] and Safety Related Application Conditions [SRAC]), standardised security and standardised interfaces towards other building blocks and/or external systems. A building block can also be defined as a standardised module. {comment:158}
A 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
Building Strategy Concept
(image: 1-screenshot-20230102-140337.png)
Building Strategy
processus allowing to regroup physical components into consistent sub-collection in terms of industral development concerns and a strategy point of view
Button A Hard Key allocated to a dedicated system on a cab. It's designed with a...
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.
Buzzer Electrical device that makes a buzzing noise and is used to provide an au...
Buzzer Electrical device that makes a buzzing noise and is used to provide an audible warning.
C-DAS - Connected Driver Advisory System
Capability Meaning
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:
capacitor
implicit-from-entry-label: capacitor
CMS
Capacity Management system
Capacity Management System
In the railway context, capacity management refers to the strategic planning and operational control measures implemented to effectively manage the available resources and infrastructure of a railway system in order to meet the demand for transportation services. It involves assessing, optimizing, and maximizing the capacity of various components within the railway system, such as tracks, stations, trains, and associated facilities.
Capacity Management
Capacity Plan and Decision Processing
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 Planning
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
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
Capacity production is the implementation of the operational plan. Capacity production begins when the train starts its scheduled mission and ends with when it ends.
Capacity Restriction
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 waste means:
* 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-friendly behaviour means:
* 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
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.
Capella viewpoint
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
CAPEX
Capital Expenditures or Capital Expenses
Capital Expenditures
CBM
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]
CCF
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]
CCS - Command Control Signalling
CCMS
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
CCS Configuration Manifest
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
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 definitions in terms of point in time and other operationally significant parameters for the activation.
CCS Deployment
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 Evolution Path
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 Feature
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 possession by driver Support for 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
CCS System
The control command and signalling (CCS) system covers signalling, train control, positioning equipment and telecommunications.
CCS-OB
Control-Command and Signalling - On Board
CCS-TRK
Control-Command and Signalling - Track-side
CCS/TMS Data Model
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.
CEF Transport
Connecting Europe Facility Transport, funding tool of the European Commission
CPU
Central Processing Unit
CTC
Centralized traffic control
CCM
Change Control Management
PROPOSAL what to change where. Shall normally be linked to an Isse. See SPPR-2210 - Manage change request links
Change Request
Change Request.
Changeability
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.
Class A / B system
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
An object is an instance of a class and a class is an object type.
Clean code has an important implication of the project’s success as clean code i...
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.
CMD - Cold Movement Detector
CMS Central modelling services
CBO
Generic target of the System Pillar.
Common Business Objective
Common Business Objective.
Common Instance
Common Interface
Common standard properties of workitems
* 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 work/review comments to a work item incl. Answer/reaction * Approvers: Experts that are asked to confirm / object to the correctness of a work item
CVSS
Common Vulnerability Scoring System
Commonality
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}
Communication Mean
a medium that support interaction between operational entities/actors
CER
Community of European Railway and Infrastructure Companies
Complex Requirement
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.
Component
{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}
Computing Environment
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 Platform
synonym for the Computing Environment
Concept Aspect.
For sketching concepts.
CONUSE
Concept how to use the system
CONEMP
Concept of Employment
CONOPS
Concept of Operations
Conceptual Data Model
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 Glossary
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.
Concept
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”.
condition monitoring, <of an item>
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]
Confidentiality
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] )
Configuration Data
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.{comment:140}
Configuration Item
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 Management Concept
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 Process
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
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 View
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
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.
Configure/administer content platform, define/moderate/train ACDARP process/prin...
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
Conflict
A conflict is any difference between the operational plan and the forecast, regardless of any actual need for intervention to resolve it.
Considered Fleet Type
type of rolling stock regarding a certain usecas, for example cargo trains, passenger trains, high speed passenger trains
Considered Track Type
type of track regarding a certain usecase, for example cargo line, high speed line, regional line
Consolidated Glossary
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.
Constraint.
Limitation of applicabilty of a design workitem
Content Exchange Concept
Context model
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
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.
CI/CD
Continuous Integration / Continuous Deployment
CCS
Control Command and Signaling
Control, Command and Signalling
Control-Command and Signalling
Controller Unit The Controller Unit is a hardware component which embeds logical...
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.
“Control” something
Define/derive deliverables and targets, break down and assign work, define process/leads, supervise timing, check results, organize approval and decision process
corrective maintenance
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]
CBA
Cost Benefit Analysis
XFN
Cross functional
CSM-ALSP
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-RA
‘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]
CST
‘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]
customer
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).
CVR-OB - Cabin Voice Radio On-Board
DAC - Digital Automatic Coupling
DAS - Driver Advisory System
Data and Data Class
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 Center
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.
DLP
Data loss prevention
Data Model Layer
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.
DBMS
Database Management System
Decision
A decision is a single action intended to make a modification the operational plan.
Link to workitems / documents, that shall be decided. Is assigned to the coregroup conveners.
Decommissioning
Withdrawing systems or components from service and dismantle it
Definition.
Glossary entry. See: Definitions
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)
Deliverable
An input or output of a task that crosses the process boundaries. Any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project. (e.g. Requirement Specification)
Dependencies among applications
Application dependencies occur when applications rely on one another to provide their function(s).
Deploy applications on computing platforms
Installation of a copy of an application on a single computing platform instance.
Deployment
rollout
“Design” something
Create content along the rules given by all "control" and "manage" roles, moderate review and approval process
Desk Area Desk Area is a location attribute (left, center...) associated to HMI...
Desk Area Desk Area is a location attribute (left, center...) associated to HMI Element for TDS Controller to allocate elements to a View.
Desk Display Area A Zone displaying a piece of visual information of particular...
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 Inside a cab, the set of operating controls*, which is dedicated to preferr...
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
Development Partnership
Contract between IM or RU and one of more suppliers about developing product(s) or (sub)systems as a collaboration
Development Task
* Take spec, build system * Usually starts on CENELEC P5 * Bottom of CENELEC “V”
DEV
Development
Deviation Detection
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
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.
Device
Device{comment:36} A physical entity performing a predefined (set of) task(s). It consists of software integrated on a hardware.
Diagnostics
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.
Diagram.
Stores a diagram, slide, or picture.
DAC
Digital Automated Coupling
DCM
Digital Capacity Management
Digital Continuity
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.
DG MOVE
Directorate-General for Mobility and Transport
DG RTD
Directorate-General for Research and Innovation
Disaster Recovery-Plan
Dispatching
Dispatching is the sum of actions intended to make modifications the operational plan.
Display Panel Glass (LCD) showing pixels without controller.
DDOS
Distributed Denial of Service
Distribution Job
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.
DM - Digital Map
DMI - Driver Machine Interface
Document Exchange
Document exchange is the act of sharing an exported document with people outside the document authoring group (domain task).
Document Generation and Management
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}
Documents Publication
Documents Publication is the creation of a document baseline and subsequent exportation in a defined exchangeable format (pdf, doc). {comment:5}
Domain Data Model
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
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}
DNS
Domain Name System
Driveability (or Drivability)
The degree of smoothness and steadiness of acceleration of a vehicle.
Dual Trackside Signalling Strategy
Installing and running both class B signalling system and ETCS on the same track
EARS
Easy Approach to Requirements Syntax
EB - Emergency Brake
ECN - Ethernet Consist Network
ELK
Elasticsearch, Logstash, Kibana
EoL
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
EoS
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
Engineering Data
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 are measurements, design data and derived data that parametrise the railway system, i.e. configuration information.
Engineering Input Data
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 View
The engineering view exposes the configuration information that was used to build, test and release the railway system. This constitutes the as-planned situation.
ERA - European Railway Agency
EECT
ERA Extended Core Team
ERG - Euro Radio Gateway
ERHD
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.
ERTMS - European Rail Traffic Management System
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)
EUG
ERTMS Users Group
Essential Function: function or capability that is required to maintain health,...
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, 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.
ETA
Estimated Time of Arrival
ETCS - European Train Control System
ETP-OB - European Train Protection On-Board
EUSPA
EU Agency for the Space Programme
EU Regulations
EU-RailGoverning Board
EU-RailGoverning Board Final decision body, where a decisions are adopted a majority of at least 55% of the votes
EUG - ERTMS Users Group
ECMT
European Capacity Management Tool
COM
European Commission
CENELEC
European Committee for Electrotechnical Standardization
CEN
European Committee for Standardization
EDDP
European DAC Delivery Program
EGNOS
European Geostationary Navigation Overlay Service, European satellite navigation system
European Geostationary Navigation Overlay Service
EPF
European Passengers' Federation
EIM
European Rail Infrastructure Managers
ERRAC
European Rail Research Advisory Council
ERTMS
European Rail Traffic Management System
European Railway Traffic Management System (ERTMS) is a single European signalling and speed control system that ensures interoperability of the national railway systems, reducing the purchasing and maintenance costs of the signalling systems as well as increasing the speed of trains, the capacity of infrastructure and the level of safety in rail transport. ERTMS comprises of the European Train Control System (ETCS), i.e. a cab-signalling system that incorporates automatic train protection, the Global System for Mobile communications for Railways (GSM-R) and operating rules. (ERA definition)
European Railway Traffic Management System (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
ESC
European Securities Committee
ESA
European Space Agency
ESO
European Standardization Organization
ESIF
European Structural and Investment Funds
ETSI
European Telecommunications Standards Institute
ETCS
European Train Control System (ETCS) is a cab-signalling system that incorporates automatic train protection. (ERA definition)
European Train Control System (ETCS) is a cab-signalling system that incorporates automatic train protection (ERA definition). ETCS in the frame of SERA will support the following Levels: * L2 with fixed train detection (classic L2 with trackside detection (track circuits, axle-counters, …)) * L2 with hybrid train detection (virtual fixed or moving blocks with trackside detection (axle-counters, …)) – formerly known as Hybrid L3 * L2 with virtual fixed or moving blocks and train integrity (no trackside detection) – formerly known as pure L3
European Train Control System
ETF
European Transport Workers' Federation
ENISA
European Union Agency for cybersecurity
ERA
European Union Agency for Railways
ERJU
Organisation being tasked with the standardisation in the railway domain at European level.
(Europe’s Rail) Joint Undertaking
Europe’s Rail Joint Undertaking
EU-Rail
Europe's Rail
EVC - European Vital Computer
EDA
Event-driven architecture
Evolution
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 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.
Evolvability
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}
Exchange item
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.
Exchangeability
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).
Extended View View displayed on more than one Display Panel.
External Button A button which is not directly managed by TDS.
External Diagnostic, Logging, Orchestration and IT Security Interface(s) (I1)
Interface I1 provides communication-based interfaces between rail systems and central infrastructure components as diagnostics, logging, Orchestration and IT-security services.
fail-safe [821-01-10]
able to enter or remain in a safe state in the event of a failure
fail-safe
able to enter or remain in a safe state in the event of a failure [SOURCE: IEC 60050-821:2017 , 821-01-10]
able to enter or remain in a safe state in the event of a failure [821-01-10 ]
failure cause
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 mode
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 rate [821-12-21]
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
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]
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
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]
fault, <of an item>
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 correction time
part of active corrective maintenance time taken to perform fault correction [SOURCE: IEC 60050-192:2015,192-07-14]
fault detection time
DEPRECATED: undetected fault time time interval between failure and detection of the resulting fault [SOURCE: IEC 60050-192:2015,192-07-11]
fault localization time
DEPRECATED: fault location time part of active corrective maintenance time taken to complete fault localization [SOURCE: IEC 60050-192:2015,192-07-18]
fault tree
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]
feature summary
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.
High Level description of system functionality. Are bundled by different "Variants".
FFFIS - Form-Fit Functional Interface Specification
FFFIS
Form, Fit and Function Interface Specification
FFF
Form, Fit and Function
FIS - Functional Interface Specification
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.
FAM
Fixed asset mgmt
Flagship Area
FMECA
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).
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).
Follow a trace
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 analysis for “Assure that all CCS processes are safe” * All operational processes need to be listed and analysed on System level 3 (OA) * Out of this all traces have to be analysed to understand the hazards and risks But this does not mean that this is also done for System Level 1,2, or 4. Just the operational design team in Task 2 has to do this. Example 2: Systems on System Level 5 (“standard products”) * Complete description how to install and use them (processes) * Complete functional description * Complete system and interface description How to follow “traces” Following a trace means to break down work items more and more. Every breakdown is not necessarily “homogenous”. One breakdown step (indicative): (image: 1-screenshot-20221229-205247.png) A break down step follows this workflow (for the assigned team) * Assess if work item is accepted and makes sense. If not, reject and forward work item to a functional team * Analyse, work out, and refine a work item; change status when finished * Draft and link the derived work items, set status to “proposed” * Propose their assignment to a team * Assigned team accepts or forwards the derived work item to a functional team. How do traces start, how to reach “completeness”? A. New traces start from * Any input of the stakeholders * Common Business Objectives (CBO) * A System Level 2/3 mission and the needed operational capabilities, derived operational scenarios and their operational requirements * Any input inside of the System Pillar team – if a backward linking to CBO or operational missions/capabilities is possible or stakeholder (steering group) agree Completeness is reached if for all of these (decided) inputs a trace down to the implementation exists with a valid trace. B. A trace is valid if * …it is connected up to a decided demand (A.) * …it is connected down to an implementation in operational processes and System Level 5. * … all links between work items of the trace are valid (correct derivation) The status of all traces will be visible at any time via the ALM.
Forecast
The forecast displays the future state of traffic. It based on the current operational state. The forecast projects the current operational plan into the future. A forecast for each train run under consideration of mutual train influence is processed (train run time, section run time, minimal section run time, detailed topology, headways and train sequence, circulation, connection, etc.).
Form Fit Function Interface Specification
A FFFIS is the complete definition of an interface between functional or physical entities. The FFFIS includes: - FIS, - Electrical characteristics related to data, - communication protocol, - and including connector and plug. The FFFIS and accompanying documents (e.g. safety analysis) guarantees the interoperability but not the exchangeability of physical entities, see Subset-037 SPT2ARC-1620.
FORM FIT FUNCTIONAL INTERFACE SPECIFICATION
Founding Members
FP - Flagship Projects
FPMH
Failures Per Million Hours{comment:96}
FPMK
Failures Per Million Kilometres{comment:97}
FRMCS - Future Railway Mobile Communication System
FS - Fulling Supervision Mode in ETCS
FTA
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]
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
Full Backwards Compatibility
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.
FDFTO
Full Digital Freight Train Operations
FTE
Full Time Equivalent
function checkout time
part of active maintenance time taken to complete function checkout [SOURCE: IEC 60050-192:2015,192-07-16]
Functional Application Downtime
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
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 apportionment
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 Chain
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 Exchange
possible flow of exchange items between 2 functions through their respectives functions
FIS
Functional Interface Specification
Functional Port
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).
FRS/FIS
Functional Requirement Specification/Functional Interface Specification
FRS
Functional Requirements Specification
Functional Requirements
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.
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
Functional Team
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)
Functionality
Function
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.
action, operation or service fulfilled by the system, or by an actor interacting with the system
Funktional team
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”
FRMCS
Future Railway Mobile Communication System
FVA - Functional Vehicle Adapter
FWSI
‘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]
GASC
Generic Application Safety Case;SPPRAMSS-334 - [EN 50129:2018/AC:2019-04] {comment:99},SPPRAMSS-335 - [EN 50126-2:2017]
Generic workflow types
* 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.
GoA - Grade of Automation
GPSC
Generic Product Safety Case; SPPRAMSS-334 - [EN 50129:2018/AC:2019-04] {comment:100},SPPRAMSS-335 - [EN 50126-2:2017]
Granularity
The granularity characterises the level of modularity of a system. The more subsystems a system is composed of, the higher its granularity.
Granularization
The granularization refers to system engineering activity aiming at defining granularity.
GUI
Graphical User Interface
Ground footprint
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.
GSM-R - Global System for Mobile Communications – Railways
GW - Gateway
Hard Key Physical key not part of view. This key can also have a text label or s...
Hard Key Physical key not part of view. This key can also have a text label or symbol.
Hardware Abstraction Interface (I2)
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 Layer
Contains the actual Hardware, i.e. the physical and electronic parts of a computer or other piece of equipment.
Hardware unavailability
Related to hardware defects (unexpected).
The physical and electronic parts of a computer or other piece of equipment.
Hardware
Hardwired connection
A means of communication using a discrete wired interface between the communication peers. Having a 0/1 or -1/0/1 logic per wire.
Harmonisation
Harmonisation includes the options TSI specification (Annex A or Application Guide), Standardisation via ESO, or agreed System Pillar Publication.
Harmonization
Act or process to make something consistent or compatible. Harmonizing the railway system can include all kinds of technical systems, operations and processes.
Hazard
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]
A problemativ situation that can occure with a system.
HAZOP
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]
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.
Heading.
Chapter title. This is no normal wokitem type, cannot be commented, etc. Is automatically created in documents when a heading is entered.
HFI Activities
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.
HMI Component
A Secure Component with a human user interface. Examples of HMI Components are PC Workstation, tablet device, smart phone, device with touch screen,...
HMI Element An HMI Element is a physical component that interacts with the drive...
HMI Element An HMI Element is a physical component that interacts with the driver: Buzzer, Display Panel, loudspeaker, Hard Key...
HOF
Human and Organizational Factors (lead to workitem SPPR-2246 - Application Condition and perhaps SPPR-2244 - SRAC)
HRM
Holistic Requirements Model
Horizontal integration
Integration of different Functional Applications, running on the same or different computing platform(s).
HSI
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 .
Human Factors
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.
HMI
Human Machine Interface
Graphical component to interact with a user e.g., by train graph.
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.
HTTP
Hypertext Transfer Protocol
Identity
An identity acts as an address where algorithms can retrieve detailed information about an object or struct.
Impersonation
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.
Implementation Requirements
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.
Incident Impact Management
Managing the recovery from incidents to normal state of operations.
incident
‘incident’ means any occurrence, other than an accident or serious accident, affecting the safety of railway operations; SPPRAMSS-337 - [Directive (EU) 2016/798]
IRM
Information Rights Management
Infrastructure Manager Operational Area of Control defines the region under the...
Infrastructure Manager Operational Area of Control defines the region under the responsability of only one Infrastructure Manager
Infrastructure Manager
IPSE
Innovation Pillar System Experts
Input documents
* 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)
Instance of a Computing platform/Computing Environment
Refers to all specific instances of RTE and Hardware required to run a specific Functional Application
Integration Task
* Combine elements, validate/test whole system behaviour, implement/commission * Right side of CENELEC “V”
Integration
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.
See SPT2CE-244 - Horizontal integration and SPT2CE-245 - Vertical integration
Interchangeability
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).
Interface
With an interface the sub-systems of different suppliers are combined.
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.
a means provided or required by components for an interaction between them or with actors
IXL
Interlocking is a set of signaling devices which physically materializes, in the area of action of a switch post (junction, crossing of tracks, etc.) throught mechanical, and / or electrical solutions . It allows train movement if the safety conditions have been met regarding train maneuver and signal control devices. (double. needs to be deleted)
Interlocking is a set of signaling devices which physically materializes, in the area of action of a switch post (junction, crossing of tracks, etc.) throught mechanical, and / or electrical solutions . It allows train movement if the safety conditions have been met regarding train maneuver and signal control devices.
Interlocking
Internal Button The Internal Button is a button which is managed directly by TDS...
Internal Publication
Any work product that is not required to be submitted in order to complete a process, phase, or project. An input or output of a task that does not cross the process boundaries.
UITP
The International Association of Public Transport
International Association of Public Transport
INCOSE
International Council on Systems Engineering
IEC
International Electrotechnical Commission
ISO
International Organization for Standardization
UIC
International union of railways
UIP
International Union of Wagon Keepers
Interoperability
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 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).
Issue.
A problem description to be solved in the specification. Can also be an open question, or a generic question, or a point on an agenda.
JP - Journey Profile
Key Controller Controller which manages states and failures of Hard Keys (intern...
Key Controller Controller which manages states and failures of Hard Keys (internal and Lateral Key) and switches.
Lateral Key Hard Key located close to a Display Area allowing soft key technolog...
Lateral Key Hard Key located close to a Display Area allowing soft key technology.
Layout Controller The Layout Controller manages the Layout for an Area.
Layout Element Controller The Layout Element Controller managesLayout Elements o...
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 Engine The Layout Engine is a generic piece of software able to generate...
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 Layout is a list of layout elements which is displayed in an area.
Lexical Glossary
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.
LOC-OB - Localisation On-Board
Localisation
Determines the position of the train within the track network, using for example topological coordinates.
Logial Component
conceptual element being part of the system, contributing to its behaviour, by interacting with other logical components and logical actors
Logical actor
external entity (human, system, ...) interacting with the logical components of the system of interest through their interfaces
Logical Architectur Concept
Logical Component
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 Functional Chain
an ordered collection of behavioural exchanges transmitting one or several logical functional exchanges
Logical Function
A function derived during logical architecture by splitting a system function.
Logical/Physical Relationsships
logistic delay
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]
Loudspeaker Device that converts an electrical audio signal into a corresponding...
Loudspeaker Device that converts an electrical audio signal into a corresponding sound.
LR is a collective term for L2 and L3 in the new CCS TSI 2022 (not yet officially issued) B4 R1.
LTM - Loop Transmission Module
LWG - Localisation Working Group
MACMT
mean active corrective maintenance time expectation of the active corrective maintenance time [SOURCE: IEC 60050-192:2015, 192-07-22]
MAD
mean administrative delay. Expectation of the administrative delay. [SOURCE: IEC 60050-192:2015,192-07-26]
maintainability, <of an item>
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
Ability to be retained in, or restored to, a state to perform as required, under given conditions of use and maintenance [EN50126] SPT2ARC-1616 .
Maintenance Costs
Costs for maintaining the railway system
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
MITM
Man-in-the-middle attack
Management by traceability (KANBAN based)
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)
Master Data
Master data represents "data about the business entities that provide context for business transactions".
MBSE - Model-based System Engineering
MDBF
Mean Distance Between Failures [SOURCE: Wikipedia Mean Distance Between Failure – Wikipedia]
MDBSF
Mean Distance Between Service Failures [SOURCE: Wikipedia Mean Distance Between Failure – Wikipedia]
MDCM - Multi-Dimensional Configuration Management
MDS - Multi Display System
MTBF
Mean time between failure
MD5
Message Digest Method 5
Methodology
A collection of related processes, methods, and tools.
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.
Method
A technique for performing a task. Method is a grouping of guidance, modelling{comment:72} language, rules, techniques and patterns. Different methods may be available for the same task. It defines the “HOW” of each task. (In this context, the words “method,” “technique,” “practice,” and “procedure” are often used interchangeably.) At any level, process tasks are performed using methods.
MFDT
mean fault detection time [SOURCE: SPPRAMSS-3539 - [EN 61703: 2016]]
Microphone Controller The Microphone Controller manages states and signals of Mi...
Microphone Controller The Microphone Controller manages states and signals of Microphone.
Microphone Device that translates sound vibrations from the air into electronic...
Microphone Device that translates sound vibrations from the air into electronic signals and scribes them to a recording medium or over a loudspeaker.
Microservices
MID - Mission Data
Migrateability / Scalability
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}
Migration Plateau
A Migration Plateau is a plateau used as target for a migration process.{comment:11}{comment:13}
Migration
Migration is the national or company specific process of converting existing CCS/TMS systems including operational processes to corresponding systems and processes of the harmonized System Pillar Reference Architecture (SPRA).
Migration 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.
MOT
Ministry of Transportation
Mission Assignment
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
MLD
mean logistic delay. Expectation of the logistic delay. [SOURCE: IEC 60050-192:2015,192-07-27]
Mode&State Concept
Mode Machine
a collection of modes connected by transitions
Mode Transition
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.
MBSE
Model based System Engineering
Model synchronisation
* 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)
Mode
Kind of system behaviour that is expected in given usage conditions. Modes can be applied to elements such as actors and components.
Modularity
Modularity is used in this document as a general term for dividing a system/sub-system/module in sub-systems/modules.
The property of a system being composed of a coherent whole of single, independent building blocks or modules.
Module
{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}
MOE
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
MOP
Measure of Performance. (one aspect of MOE)
MOTBF
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]
Moving Block
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.
MRT
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]
MTBSF
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.
MTD
mean technical delay [SOURCE: SPPRAMSS-349 - [EN 50126-1:2017] Annex B.4]
MTTFF
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]
MTTF
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]
MTTR
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.]
MVCC
Multi-version concurrency control
Narrow Interfaces
narrow interfaces TBD
NIP
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
NSA
National Safety Authority
NTMS
Neighborhood TMS
Network Component
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
NFF
No Fault Found
Non-European Railway
IM and / or RU of a country that is no member of the European Union
Non-functional Requirements
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).
normal/regular operation
desired state of operation of a system/component/equipment, i.e. absence of faults.
NOTIF-IT
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 ]
NB-Rail
Notified bodies for interoperability in the railway sector
NP - No Power Mode in ETCS
NRV
‘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]
NTC - National Train Control
NTP - National Train Protection
[OAB] [Entities/actors]
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] [Process Involvement]
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]
placeholder
[OAIB] [Operational Process]
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
OB - On-board
Object Name
An object name is a string that helps humans identity an object and that may reveal meaningful information about the object.
objectives
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.
[OCB] [Involvement]
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] [Structure]
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
OCORA - Open CCS On-board Reference Architecture
OE - Operational Execution
[OES] [Operational Process] [scenario]
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
OMS - On-board Monitoring System
Onboard Strategy
strategy of equipping and upgrading the trains with onboard communication units and additional technology as localisation, train integrity etc.
[OPD] [Operational Process] [logic]
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
OSI layer
Open System Interaction Model, aka OSI 7 System Layer model
Open System Interaction Model
Operating Rules
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 state
The operating state describes the current state of production: * how trains move * where trains are * which route is set in control system * status of assets This information is based on inputs from control systems.
Operating system
operating time to failure, <of an item>
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
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]
Operational Activity
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.
A step or function of an operational process, done by actors that might need to use the system to reach certain objectives.
Operational capability
An operational capability is an ability given by a group of processes.
ability of an operational entity to provide a service
OpsCON
Operational concepts (How system should function)
Operational Concepts
Operational Costs
Costs for operating the railway system
Operational Design
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 Entity/Actor
A person or organisation performing an operational activity.
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}
OHT
Operational Harmonization Team
Operational harmonization
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 Hazard.
A problematic situation that can occure with a process design.
Operational Interaction
exchange between operational activities
Operational Mission (deprecated)
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 Segment
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
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 Plan
Analogous to the capacity plan, the operational plan supplies the train and traffic control and all other components with the operational train data. The operational plan is fed from the active timetable buffer and contains all trains (from the timetable buffer) that are currently in their operational time window. The operational plan is the result of various influences (decisions from dispatching, map data, etc.). It is updated every single minute.
Operational Process
An ordered (time or information) flow of operational activities.
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 Requirements
Operational requirement
A requirement issued in the context of the operational analysis process group. May qualify some operational actor, actor property, activity, scenario.
Something a process design has to fulfil.
Operational Risk.
Value and mitigation for a operational hazard
Operational Role
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 Scenario
dynamic and time-ordered interaction between operational elements: operational entities / actors or operational activities
Operational Stop
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/System relationships
Operator Specific Add-On
Operator
An institution operating a system through its life-cycle, in context of the document usually an Infrastructure Manager or Train Operator.
Opex
Operational Expenditures
ORS Operational Requirement Specification
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) )
PIS
Passenger Information System
PCS
Path Coordination System
POS
Path Order System
PER - Perception
performance < of an item >
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.
PRAMSS
Performance, reliability, availability, maintainability, safety and security
Performance Requirements
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}
PFH
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]
probability of dangerous failure per hour [EN 61508-4:2010]
probability of dangerous failure per hour [SOURCE: EN 61508-4:2010]
Physical Architecture Concept
(physical) Behavioural Component
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 Port
port of behavioural component
Physical Exchange
an ordered collection of physical link transmitting behavioural exchanges
(physical) Host component
physical component, (ressource) hosting behavioural components
Physical Link
means of communication/transport relating to the hosting of physical components, used as a medium by exchanges between behavioural components
Physical Port
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 Scenario
scenario between actors and physical behavioural component
Physical / Building Strategy relationships
Plan Execution
Plateau
A Plateau is a consistent requirement subset of the System Pillar Reference Architecture (SPRA) to be defined by the System Pillar domains. It can be used for market tenders in a specific timeframe and is recommended by and agreed across the sector. In the context of system engineering, a "plateau" refers to a distinct stage or phase within the system development lifecycle (SDLC) where progress or development remains relatively stable or flat for a period of time. It is characterized by a temporary pause or leveling off in the advancement or evolution of the system being developed.
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 issues or challenges, and plan for future iterations or developments. It's important for system engineers to effectively manage plateaus by maintaining clear communication with stakeholders, ensuring proper documentation, and utilizing the time and resources available to refine and improve the system before progressing to the next stage of development.
PWITD
Polarion Work Item of Type Definition
PWITR
Polarion Work Item of Type Reference
Portability
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.
PMAT
PRAMSS Management & Assurance Team
PRAMS
Performance, reliability, availability, maintainability, safety
Process Framework
A process framework refers to a structured and systematic approach for designing, documenting, and managing processes within an organisation for a defined scope.
Process Task
An atomic activity that is included within a process. It is used when the work in the Process is not broken down to a finer level of Process detail. Action intended to contribute to the achievement of one or more outcomes of a process.
Process
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.
Production view
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.
PROD
Production
PMO
Project Management Office
Project Milestone.
The planning hierarchy is Release>Project Milestone>Work Package>Task
QoS - Quality of Service
Quality and Assurance
Question.
Entry in a FAQ or Q&A list. Description holds answer. If there are many answers then workitems of type "Answer" can be linked.
RBC
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
RIM
Rail Infrastructure Manager
RNE
Rail Net Europe
ROC
Rail Operating Company
RASCOP
Rail Standardisation Coordination Platform for Europe
Rail Undertakings
Railway Infrastructure Manager
RIS
Railway Infrastructure System
Railway Operating Company
Railway Requirement.
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 Undertaking
Railway
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.
RAM
Random Access Memory
Rationale.
Reasons why another workitem WAS designed this way
RBD
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]
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.
Reader Controller The Reader Controller manages states and failures of the Biome...
Reader Controller The Reader Controller manages states and failures of the Biometric Readerand/or the RFID Reader.
Real Time
Real-Time Conflict Detection
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.
RAID
Redundant Array of Independent Disks
Reference.
Hyperlink and/or copy of an external document. See: References
Refering document
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.
Release.
A package of documents (polarion collection) released by a domain at a certain time
reliability, <of an item>
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]
RAMS
Reliability, Availability, Maintainability and Safety
Reliable Data
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.
Relocate rail applications
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.
RTO
Remote Train Operations
REP - Repository
REST
Representational State Transfer
Requirement statement
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)
Retrofit
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.
Reusability
The property of a sub-system to be integrated without any modification inside various CCS possibly deployed in different operation contexts.
RFID Reader Radio Frequency Identification (RFID) refers to a wireless system co...
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.
risk, <of a hazard>
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 analysis
systematic use of available information to identify hazards and to estimate the risk [Source: IEC 60050-903:2013, 903-01-08]
risk assessment
overall process comprising a risk analysis and a risk evaluation [Source: IEC 60050-903:2013, 903-01-10]
risk evaluation
procedure based on the risk analysis to determine whether the tolerable risk has been achieved [Source: IEC 60050-903:2013, 903-01-09]
Risk.
Value of damage and mitigation for a hazard.
Road Traffic (DRAFT)
Any traffic on a railway track level crossing other than railway traffic.
Roadmap
Visualization of a specific plan
RBAS
Role Based Access Control
Role.
Role assigned to a actor
Roll Away
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
RU - Railway Undertaking.
Rule.
Design principle that shall used in a certain area. Is used to avoid the need of Rationals for every design element.
(Running) Instance of an application
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.
RTE
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
Runtime Layer
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{comment:2} for information exchange between Functional Applications running on the same Computing Environment and with external entities. It may also include an operating system.
safe state [821-12-49]
condition which continues to preserve safety [SOURCE: IEC 62425:2007, 3.1.42]
safe state
condition which continues to preserve safety [Source: IEC 60050-821, 821-12-49]
condition which continues to preserve safety [821-12-49][IEC 62425:2007, 3.1.42]
Safe Train Length Determination
Function of ETCS Level 3.
Safety Layer
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.{comment:1}
Safety Platform Independence Interface (I5)
Interface I5 provides a safe (upto SIL4) platform independence API for functional applications.
SASC
Specific Application Safety Case; SPPRAMSS-334 - [EN 50129:2018/AC:2019-04] ,SPPRAMSS-335 - [EN 50126-2:2017] {comment:104}
Scalability
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.
Scenario
dynamic interaction between elements like the system and the actors, components or between functions
Schema meta-model
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.
SCV-OB - Signal Converter-On-board
secondary functions
"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."
SecRAC
security-related application condition [SOURCE: CLC/TS 50701:2023]
Sectional Runtime Calculation
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.
Secure Communication
efining an encrypted channel between two entities using TLS1.3
Secure Component
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,…)
SSL
Secure Sockets Layer
SEMP Link Rule.
Defines how certain Polarion workitems shall be linked. See: SEMP Link Rules overview
SEMP Process.
Defines a process in the SEMP. See: SEMP Processes
SEMP Requirements Types
* 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 Role Allocation.
Name of the person who has a certan role in a certain team. See: Tracker search for role allocations
SoC
Separation of Concerns
serious accident
‘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) ]
Service unavailability
The unavailability of a service provided by a Functional Application, as seen by a user of this service (e.g., another Functional Application)
Shared Security Services
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.
SIL - Safety Interity Level
(SIL2) Hazard mitigation
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)
(SIL4) Safety Invariant
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).
SOAP
Simple Object Access Protocol
SERA-CCS
For the railway sector, EU policy focuses on the main goal of establishing a single European railway area, an EU-wide system of railway networks which would allow the expansion of the rail sector based on * competition, * technical harmonization and * joint development of cross-border connections [see Building the single European railway area]. To this end, the EU aims to: * open and restructure the rail market * increase competitiveness by creating a level playing field for companies * develop infrastructure to ensure interoperability * improve efficiency in infrastructure use and safety * ensure fair prices for consumers{comment:5} SERA-CCS is understood to consist of those SERA objectives which are relevant for CCS (technical/operational target). It is defined by the following capabilities: * Provides Independence between Infrastructure Managers (IM) and Railway Undertakings (RU) or Vehicle Owners (VO): * No track access restriction or extra costs for a compliant RU/VO fleet/services accessing a given IM infrastructure compliant with SERA-CCS. * Non discriminatory access to IM services and capacity allocation across SERA-CCS IMs for compliant RU/VO fleet/services. * Ensures interoperability, which is the ability to allow the safe and uninterrupted movement of trains that accomplish the specified levels of performance across different infrastructure networks (IMs) and the ability that an infrastructure network is able to interact with trains of different RUs/VOs. * Ensures Harmonized Operations, based on: * Radio-based CAB Signalling, * Automatic Train{comment:1} Operation (ATO), * Single licensing for Drivers and Signalers across SERA-CCS. * Provides Backwards Compatibility: * Compatibility is considered to be achieved for a particular combination of on-board and trackside when the on-board is able to run a normal service on that trackside. The expression “train is running a normal service” shall be understood as “a train not penalized because of a reduction of performance or safety”. * {comment:2}The full functionality of any old version shall always be available in any new version of SERA-CCS * Enables significantly lower life cycle costs having easy Upgradability, Scaleability, Adaptability and Changeability of Hardware and Software components/systems/subsystems * Consists of a Modular Architecture, both trackside and onboard: * Trackside and Onboard architecture are designed to allow for separate replacements/upgrades of individual sub-systems with reasonable integration effort. * Enables Interchangeability of hardware and software components/systems/subsystems across suppliers * The modular architecture shall also allow for situations where the replacement/upgrade of individual components from different suppliers is needed. {comment:4}
Single European Railway Area - Command Control and Signaling
Situation
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.
Soft Key Context-dependent key which consists of a Hard Key with an associated l...
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.
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
SP - System Pillar
SP Plateau? Plateau Release? Plateau Specification?
Specification task
* Result: specification for an artifact * Usually ends on CENELEC P4 * Left side of the CENELEC “V”
SR Authorisation
SRAC.
Safety related application condition.
Safety related application conditions are SPPR-2246 - Application Condition relevant for the safety of the application.
SRD
Single Rules Database [SOURCE: ERA, https://www.era.europa.eu/domains/registers/srd_en ]
SRS
System Requirement Specifications
Stakeholder needs
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
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.
Characterizes a stakeholder
SCI-OP
Standard Communications Interface – Operational Plan
Standard Interfaces
Add definition for standard interfaces
SSI
Standard Security Interface
standard/routine operation
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,
State Machine
collection of states connected by transitions
State Transition
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
Behavioural characteristics of the system or physical conditions imposed by the environment. States can be applied to elements such as actors and components.
STIP Milestone.
Standardisation and TSI Input Plan Milestone
STM interface
Interface of the Specific Transition Module of a train
STPA
System Theoretic Process Analysis [Source: J3187:202305]
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.
Struct
A struct is a named and organised structure for storing a set of coherent information items. It is a class without methods.
Sub Process (Activity)
Set of cohesive tasks of a process
Sub-system (sometimes called “Building Block”)
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.
Subsystem
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 constraints or physical dimension constraints) will be allocated to subsystems.
SuC
System under Consideration [SOURCE: SPPRAMSS-4697 - [EN IEC 62443-3-2:2020]]
Support.
Used for support issues in Polarion
Switch Physical component which allows a selection of 2 to N states and keeps th...
Switch Physical component which allows a selection of 2 to N states and keeps the state until its position is changed.
Switch
a switch is a device that opens or closes electrical circuits.
Electrical switch. Closes or opens a circuit.
(System) Actor
Actors are entities outside the system (either humans or other technical systems) that interact with the system.
external entity (human, system, ...) interacting with the system of interest through its interfaces
System Analysis Concept
System and Innovation Programme Board
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
SAD
System Architecture Description
System Capability
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.
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).
SDLC
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
SEMP
System Engineering Management Plan
System Function
A function derived during system analysis.
System Levels
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 mission (deprecated)
high-level objective of the system
System Of Systems
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 Pillar Core Group
System Pillar Core Group Manages the common business objectives and deliverables from the Tasks
SPC
System Pillar Coregroup
System Pillar Deliverables (“output documents”)
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 dataStandardisation and CCM documentation D7.1 Standardisation packages and publications D7.2 External quality and experience monitoring for the standard is set up D7.2 External change management documentation
SPDT
System Pillar Domain Team
SPSG
System Pillar Steering Group monitoring the progress of the System Pillar
System Pillar Steering Group
System Pillar Unit Chairs the System Pillar Core Group
System Requirements Specification
System Requirements
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 Requirement.
A System Requirement defines a capability of a linked system. It represents a task for designers an validators.
System/Logical Relationsships
System
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
Subject of interest of the engineering activities described by ARCADIA, which is also an organized collection of elements working as a whole.
Tailoring of requirement breakdown
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 1/2: Define generic roles of CCS and TMS in this case * System Level 3 TMS: Define TMS process for it * System Level 3 CCS: Define generic roles and basic information flow of Level 4 CCS Systems for it * …. * System Level 4/5 Traffic CS: …. * System Level 4/5 Train CS: … * … * Operational process “Reset object controller” shall be tailored into these work assignments * System Level 1/2: Skipped * System Level 3: Delegate interface coordination to Traffic CS / Trackside Asset CS * System Level 4/5 Traffic CS: Define process for the remote reset * System Level 4/5 Traffic CS: Define process for the local OC reset * System Level 4/5 Trackside Asset CS: Define process for the remote OC reset * System Level 4/5 Trackside Asset CS: Define process for the local OC reset Consequence: With specific workflow tailoring, the analytical system levels are incomplete (see table above). “Generic (Workflow) Tailoring” = Certain work item types are worked out only on certain layers Example: Examples: | CBO | Requirements | Operational Processes | Logical Components System Level 1/2 | X | X | Business process | System Level 3/4 | | X | X | System Level 5 | | X | X | XCoordination of “tailoring” is the main role of all “functional teams” (see chapter later in the document). A good tailoring fulfils the following requirements * Work is parallelized early and in a precise way (independent work) * No “dummy” work items just for the sake of symmetric work item break downs in the system of systems * The derivation process does not “block” everything because of sequential working dependencies * The level of details of the specification is always only as good as needed on System Level 1-4 (analytical clarification = work preparation) so that the teams working on System Level 5 know what to do. * A domain team on System Level 5 – the real specification level – can concentrate on its local work functions, engineering rules, and the collaboration with other domain teams concerning concrete interfaces * A task level architecture team (ARC, OD, MIG) just focusses on the role to provide all needed specifications (especially requirements, process definitions, functional allocation) that enables the work on System Level 5 Team - without already creating too much design “Tailoring” is the work to dynamically assign work items to the system level that shall work on them. A tailoring process is executed by a functional team. The typical workflow for tailoring is * An “inbox” (automated workflow, state driven) for new/changed work items is automated (e.g. inbox for new requirements, or for a proposal of process design change) * Some work items can be assigned automatically by rules (generic tailoring) * Else: The responsible person (role owner in the functional team) checks (evtl. discusses) the new work item * The new work item is assigned to a system level and team. This happens to all types of inputs and changes. Conclusions: * Do only the minimal needed work on System Level 1-4, needed to get good Level 5 specifications, rulebooks, etc. * Apply a generic tailoring to avoid that everybody is working on the same things * Design a workflow that assigns work items dynamically to the right level.
TAP - Telematics Application for Passenger Service
target picture
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 System
the target architecture of the signalling system as a whole
Task.
TCMS - Train Control & Management System
TCO
Total Cost of Ownership
TDS - Train Display System
Technical Committee
technical delay
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]
TAF/TAP TSI
Technical Specification for Interoperability relating to Telematics Applications for Freight/Passenger Services
Technical Specification for Interoperability relating to Telematics...
TSI
Technical Specification for Interoperability
Technical Specifications for Interoperability
TAF/TAP
Telematics Applications for Freight/Passenger Services
TAF
Telematics Applications for Freight
TAP
Telematics Applications for Passenger Services
TCR
Temporary Capacity Restrictions
Temporary Capacity Restriction
Temporary Shunting Area (TShA) A temporary shunting area is an interlocked area...
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)
Term Status Description Operating state draft The operating state describes the...
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 | draft | A decision is a single action intended to make a modification the operational plan. Forecast | draft | The forecast displays the future state of traffic. It based on the current operational state. The forecast projects the current operational plan into the future. A forecast for each train run under consideration of mutual train influence is processed (train run time, section run time, minimal section run time, detailed topology, headways and train sequence, circulation, connection, etc.). Operational Plan | draft | Analogous to the capacity plan, the operational plan supplies the train and traffic control and all other components with the operational train data. The operational plan is fed from the active timetable buffer and contains all trains (from the timetable buffer) that are currently in their operational time window. The operational plan is the result of various influences (decisions from dispatching, map data, etc.). It is updated every single minute. Master Data | draft | Master data represents "data about the business entities that provide context for business transactions".
Test Case.
Defines a setup for a test run
Testability
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.
Text.
Used for any type of sketching, non-papers, protocols, etc.
The set of all traces together is called a “model”.
The "Trace" for a work item chain/tree/graph
* 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)
Timeframe
amount of years for a certain level of equipment or migration phase
TIMS - Train Integrity Management System
TLS
Transport Layer Security (source: SPPRAMSS-1705 - [UNISIG Subset-146] )
TMS Daily Topology
Exact physical and topological description of the current state of railway infrastructure on a daily basis.
to interface (verb)
To exchange information with another peer using a mutually agreed structure and flow of communication.
Tool Requirement.
Used to store issues for the optimisation of Polarion
Tool
The term Tools refers to all supplier specific applications required to develop, test, integrate, deploy, diagnose and maintain FA Tasks, Functional Applications, Functional Systems and/or Systems of Systems. It may also include applications needed for the the virtualisation and/or hardware layer.
An instrument that, when applied to a particular method, can enhance the efficiency of the task, provided it is applied properly and by somebody with proper skills and training.
TWG
Topical Working Group
Topology Master Data Validation & Import
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.
Touch Controller Controller which manages the states and failures of a Touch Pan...
Touch Controller Controller which manages the states and failures of a Touch Panel.
Track footprint
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.
TACS
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
Trackside Assets
All technical systems and products that are necessary for safe train operation from infrastructure perspective that are not located in the train.
Trade-space factor
"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).
TMS
Traffic Management System
Traffic Management System (double, needs to be deleted)
Traffic Management System is used to manage the operation of the railway system and to ensure efficient recovery when unexpected traffic disruptions occur.
Traffic Manager Operational Area of Control defines the region under the respons...
Traffic Manager Operational Area of Control defines the region under the responsability of only one Traffic Manager
Train Dispatcher: A Train Dispatcher is an Infrastructure Manager operator that...
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 Display System Controller The TDS Controller interacts with system (CCS, T...
Train Display System Controller The TDS Controller interacts with system (CCS, TCMS,CVR) and manages the Desk Display Area.
Train Display System (TDS) The Train Display System is the train cab display sys...
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 Integrity Monitoring
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 Running Number
A number under which the train is operated. Reference: Glossary of Terms and Abbreviation. SUBSET-023. Issue 4.0.0
Train-centric Track Occupancy
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” something
Create Training material, provide training, support trained people
TEN-T
Trans-European Transport Network based on EU-Regulation No 1315/2013
Trans-European Transport Network
Transport Layer Security [TLS]
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
TCCS
Transversal CCS domain
TRD - Train Data
‘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]
TTD - Trackside Train Detection
UML
Unified Modeling Language
UNIFE
Union des Industries Ferroviaires Européennes
UNISIG
Union Industry of Signalling
UNITEL
Union Industry of Telecommunications
UNISIG - Union Industry of Signalling
Updateability
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.
Upgradeability
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.
Uplinking
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 integration steps is the same. All integration work (conceptual level, system models, requirements, etc.) is about this merging process. The following things can happen: * A new node (work item) is added and linked to 0-n{comment:14} old nodes * An old node is changed or deleted or relinked in another way The indirect effect of such a change/add process can be * In a “trace” (chain of work items) links can get{comment:15} “suspect” if earlier links or nodes were changed (through partially-automated impact analysis) * New workflows are triggered by new work item states. If a new node is created with the state “draft”, it is because of this assigned by a tailoring process in a certain way. To add the new fragment{comment:16} to the exiting master database (can only be done efficiently with automated ALM systems) the following work steps are executed * Convert contribution to graph structure (work items/links), check consistency * Analyse and assess new contribution * Perhaps adapt/change contribution before synchronisation * Create difference to master database automatically * Assess difference and indirect impacts * Replace/link fragment in database (fully or partially) or revoke it * Check and analyse the new state of the master database Simplification of synchronization * Assigned designated areas to be designed only in certain teams/tools/places (only connecting links to be synchronized) * Check separated designs together frequently to avoid large deviations How often synchronize/integrate? * Best: Directly work on the master model (possible with ALM, performance problems with MBSE tools) * Second best: Do the sync/integration very frequently (daily, weekly, or monthly) * Worst: do it once in 6 months --> Risk of unsolvable incompatibility and lost work is increased Conclusion: * We need a very efficient and sophisticated tool support for the synchronization/integration process * The integration/synchronization process will create large efforts in the Modelling Service Team The concrete rules, when and how “uplinking” is done, are defined in chapter 20.
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
Validator Finding.
Result of a validation
Variant
A Variant is a subset of features
Vertical integration
Integration of an Functional Application with the IT platform, or a middleware with a hardware.
View Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can r...
View Aggregation of Areas required for systems (CCS, TCMS, CVR...). A View can represent Areas of different systems at the same time.
View Controller The View Controller aggregates the View, the output devices and...
View Controller The View Controller aggregates the View, the output devices and the controller of each input device.
View
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.
Virtual Block
Virtualisation Interface (I3)
Interface I3 provides the API to virtualized hardware through functions such as virtualisation, separation and "containerisation"
Virtualisation Layer
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.
VLAN - Virtual Local Area Network
WAF
Web Application Firewall
WSDL
Web Services Description Language
White Box View
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.
Wider System of Interest
The set of all operational entities defining then scope of the operational analysis.
Wireless Component
A Secure Component with a wireless communication interface. Examples of Wireless Components are handheld devices, WLAN access points and WLAN/5G routers and modems.
Work Item Comment
Work item editor
* 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
Work Item{comment:1}{comment:2}
* 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 Package.
Work Product
An artefact associated with the execution of a process.
Workflow and workflow rules
* 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 Prioritisation strategy to be decided per area
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 operational processes, and assess every process impact on the later grade of standardisation of products. * Example 4 (“horizontal + vertical prioritisation”): The functional allocation and ambition in the logical architecture shall be decided as early as possible. For this, all operational capabilities need to be derived down to the logical architecture, and every logical component needs to be designed concerning the external dependencies that it has for other logical components (e.g. delegation of safety requirements from one to other components get only visible with the deep dive in the functional design).
Workflow step (on step in a workitem trace)
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 really needed to resolve the traced work item in a correct way. Afterwards, the following “change action” is executed. * “Change a work item or link in an existing trace”: Because of a change of a work item or link in a trace the trace gets invalid in some parts(has “suspect links”). It must be reassured that the derivation process in all directions of the trace is correct, or otherwise further work items need to be adapted until all work items are resolved again. E.g., a system requirement lead to 5 system functions that are needed. One system function cannot be implemented. Therefore, all 5 derivations need to be reworked and perhaps all functions need to be deleted and the resolving process starts again. Other example for a suspect link: A function was derived from a requirement. Later the requirement is changed, and the link gets automatically suspect because it is not clear if the function is still implementing the requirement. * “Approve” a work item (see chapter below). An approval step is done in the ALM on work item level by experts based on their knowledge. The group of approvers is assigned depending on the work item type and content. A single approver agrees with an approval that a work item is correctly derived, designed, and broken. Approvals are done per single work items like requirements, concept paragraphs or operational requirements. Approval sessions are typically done for a selected set of work items. * “Decide a deliverable”. When all work items for a certain work area / release are resolved and approved, a document is generated for a formal decision process (e.g. an interface specification or a rulebook). * The typical sequence of actions in a work step is * Pull a work item or check proposed work items * Design the work item * Resolve the work item * Assign resolving work items to a team or person
Workstep "workitem check"
* 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.
Polarion Workitem
ARCADIA Method
Railway Infrastructure