DELIVERABLES PUBLISHED BY THE PROJECT
D4.3 SAFE IMU SENSOR AND DATA FDE FOR LOC-OB DESCRIPTION DOCUMENT
This document briefly explains what an IMU is, what types of IMUs exist, which errors can be found in them and how can be minimized and which fault detection techniques could be employed.D3.2_LOC-OB Preliminary Hazard Analysis
This document provides a preliminary safety analysis of the LOC-OB system, identifying hazards, accessing the severity of the potential accidents and identifying safeguards for reducing the risks associated with the hazards.
DownloadD3.1 LOC-OB System context analysis and RAMS Plan
This deliverable aims at defining and coordinating the
RAMS objectives and activities of CLUG 2.0 for the LOC-OB system.
DownloadD4.10 ON BOARD DIGITAL MAP DEFINITION AND INTERFACES
The digital map interfaces with three LOC-OB functions: Initialisation
and Start of Mission, Track selectivity, and Along-track localisation. In
continuation of CLUG (1)’s initial digital map definition and interface, this CLUG 2.0 D4.10
document reflects a first definition and Interface Control Document (ICD) compatible
with the CLUG 2.0 WP4 prototyped algorithms and within SBB’s and SMO’s rail
context.
D4.5 EUROBALISE READER SENSOR AND DATA FDE FOR LOC-OB DESCRIPTION DOCUMENT
This document briefly explains what a “Balise Reader” is, which
errors can be found in them, and why no fault-detection techniques need to be
employed in a positioning system which uses data from the Balise Reader.
D4.4 Speed sensor and data FDE for LOC-OB description document
This document briefly explains what a Speed Sensor is, which errors can be found in them, and which fault detection techniques could be employed. Furthermore, it provides a list of criteria for a preferable sensor selection.D2.4 LOC-OB System Requirements
The purpose of this deliverable is to define a set of requirements defining an onboard localisation equipment (a final product and not a demonstrator) derived from the information available in the D2.1, D2.2 and D2.3.DownloadD2.2. Start of Mission and Track Selectivity
The objective of this deliverable is to describe and analyse
the operational scenarios in order to derive constraints and recommendations
for the localisation on-board unit specifically for Start of Mission and Track
Selectivity. Therefore, operational scenarios are described from todays’
perspective with focus on localisation challenges during Start of Mission and
with regards to Track Selectivity. For this purpose, a set of operational
scenarios that are potentially challenging for the future localisation onboard
system is defined. The environmental conditions (e.g., tunnel) and operations
(e.g., standstill, acceleration) defined in CLUG (1) are referenced in the
operational scenarios.
DownloadD2.1 Operational Needs and System Capabilities of LOC-OB System
The main objective of this deliverable is to
analyse operational needs and operational context to derive the system
capabilities needed of a train on-board localisation system. It also targets to
specify a set of high-level user requirements for a localisation system that
fulfils the operational needs of its railway users. These high-level user
requirements are the basis for the system definition, design and evaluation.
DownloadD2.3 LOC-OB System Definition and Operational Context
This deliverable focuses on the system
architecture and the operational context of the LOC-OB component. The
complexity of the on-board CCS strongly influences design decisions for a
common architecture. CLUG promotes a modular approach that enables functional
isolation of all subsystems. A common communication bus allows the blocks to
exchange information. To provide the
operational context, the
proposed CLUG architecture is compared with the
existing ETCS solution and the proposals of preceding projects. A system under
consideration is then defined to identify the functional interfaces between the
LOC-OB component and its users and supporting systems.
Download
