Proceedings 2002/2003 - IRSE
Proceedings 2002/2003 - IRSE
Proceedings 2002/2003 - IRSE
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
EUROCAB AND THE DRIVER MMI – AN INTRODUCTION TO THE TECHNOLOGY 43<br />
Document Name Reference Version Normative/<br />
Number Number Informative<br />
ERTMS/ETCS Functional Requirements Specification (FRS) — 4.29 Normative<br />
ERTMS/ETCS System Requirements Specification (SRS) SUBSET-026 2.2.2 Normative<br />
FFFIS for Eurobalise SUBSET-036 2.0.0 Normative<br />
Euroradio FIS SUBSET-037 2.0.0 Normative<br />
Euroradio FFFIS Class 1 requirements SUBSET-052 2.0.0 Normative<br />
Specific Transmission Module FFFIS SUBSET-035 2.0.0 Normative<br />
Dimensioning and Engineering rules SUBSET-040 2.0.0 Normative<br />
Performance Requirements for Interoperability SUBSET-041 2.0.0 Normative<br />
FFFIS Juridical Recorder Downloading Tool SUBSET-027 2.0.0 Normative<br />
FIS for the Train Interface SUBSET-034 2.0.0 Normative<br />
FIS for the Man-Machine Interface SUBSET-033 2.0.0 Normative<br />
ERTMS Driver Machine Interface Part I Ergonomic V21.doc 12/04/2000 Informative<br />
arrangement of ERTMS/ETCS Information<br />
ERTMS Driver Machine Interface Part III Data entry Procedure V11.doc 12/04/2000 Informative<br />
ERTMS Driver Machine Interface Part IV Symbols V06.doc 12/01/2000 Informative<br />
ERTMS Driver Machine Interface Part V Audible information V08ns.doc 27/03/2000 Informative<br />
ERTMS Driver Machine Interface Part VI Specific Transmission V04.doc 27/03/2000 Informative<br />
Modules<br />
Table 1: Relevant Specifications for ERTMS/ETCS Onboard Subsystem<br />
For the ERTMS/ETCS system, which is the<br />
technical system required by the TSI in order to<br />
achieve interoperability, the technical specifications<br />
were issued by the UNISIG industry group at the<br />
beginning of 2000, and were adopted by the<br />
European railways and the European signalling<br />
industry in a ceremony on 25th April 2000 in Madrid.<br />
The core document of these specifications is the<br />
System Requirement Specification (SRS) 4 . The SRS<br />
has undergone a debugging process since then,<br />
leading to a revised version 2.2.2 5 which is now<br />
referenced in the TSI and which is, together with the<br />
other ERTMS/ETCS specification documents,<br />
mandatory for implementation of the system.<br />
Table 1 shows the main documents relevant to<br />
implementation of the ERTMS ETCS onboard<br />
subsystem. The Functional Requirement Specification<br />
(FRS), being a functional specification, does<br />
not specify any technical solutions and is therefore<br />
only marginally relevant when implementing a<br />
system, and the SRS is the key document for this. It<br />
describes the architecture and functionality of the<br />
system and the ETCS language, and it is the source<br />
for all other documentation. Although it is a<br />
specification for the whole system, it includes the<br />
onboard subsystem. The SRS is accompanied by a<br />
set of supplementary specifications, such as<br />
performance requirements etc, and by interface<br />
specifications. There are two kinds of these:<br />
Functional Interface Specifications (such as the FIS<br />
for the Man-Machine Interface) which specify only<br />
the logical interface, and Form-Fit-Functional<br />
Interface Specifications (such as the FFFIS for<br />
Eurobalise) which prescribe physical features of the<br />
interface as well. All the above specifications are<br />
mandatory, but this is not the case for the ergonomic<br />
layout of the DMI, which is specified in the ERTMS<br />
Driver Machine Interface Specifications (parts I-VI).<br />
It must be emphasised that the specifications<br />
govern only those features of the system that are<br />
relevant to interoperability. This means that features<br />
that do not affect interoperability (e.g. diagnosis) are<br />
not described, and are at the discretion of the<br />
manufacturer.<br />
ERTMS/ETCS ONBOARD<br />
ARCHITECTURE AND FUNCTIONALITY<br />
ERTMS/ETCS is an ATC system with an onboard<br />
and a trackside part, and there is a clear<br />
interoperability requirement between these even if<br />
they are supplied by different manufacturers.<br />
Therefore the interfaces between onboard and<br />
trackside subsystems, and also the partition of<br />
system functionality between onboard and<br />
trackside, must be specified very thoroughly. On the<br />
other hand the concept of interoperability includes<br />
specifying only to the extent that interoperability is<br />
affected. This leads to a system concept different<br />
from what was discussed at the start of the history<br />
of ETCS, when a concept of exchangeability of<br />
components was on the table. The actual<br />
ERTMS/ETCS specifications are based on a blackbox<br />
concept, with clearly defined functionality and<br />
interfaces but with maximum freedom to design<br />
onboard and trackside equipment.<br />
Figure 1 shows the ERTMS/ETCS system<br />
architecture. The onboard subsystem is depicted in<br />
the upper part. As mentioned above, the onboard<br />
subsystem is a black box with the following<br />
interfaces:<br />
• Train Interface (TIU) – eg to brakes, traction<br />
control, air conditioning, etc.<br />
• Driver MMI.